Mark Buskell
Member
It seems to me that SCADA packages are fine for displaying pretty graphics and being able to run some types of data acquistions.
My company is getting more requests for SCADA packages like RSView.
Then they come along and want huge databases, reporting, scheduling, etc.
My view so far is it you need a lot of Visual Basic routines that must be used then SCADA packages are not the way to go.
Some possible new customers have been burned with custom packages and having to pay high upgrades every time they need a change. They feel that going to SCADA packages will give them more control and they themselves will be able to modify the program if need be.
I have no problem with Visual Basic and interfacing to Allen-Bradley controllers, but to take a VB program that has thousands of lines and be expected to convert it to SCADA, the cost would be mighty high.
My company is getting more requests for SCADA packages like RSView.
Then they come along and want huge databases, reporting, scheduling, etc.
My view so far is it you need a lot of Visual Basic routines that must be used then SCADA packages are not the way to go.
Some possible new customers have been burned with custom packages and having to pay high upgrades every time they need a change. They feel that going to SCADA packages will give them more control and they themselves will be able to modify the program if need be.
I have no problem with Visual Basic and interfacing to Allen-Bradley controllers, but to take a VB program that has thousands of lines and be expected to convert it to SCADA, the cost would be mighty high.