[Discussion] Do you think a framework for building and implementing a (simple) SCADA is needed?

[zenithie]

I hear a lot of people talking about the annoyance of price estimates (meaning they don't get a clear, transparent price from the beginning) and the costly engineering that seems to never end.

Do you think that a step-by-step, clear process and course of action from A to Z would be beneficial for companies?

And I'm not talking here about SCADA software, like Ignition.

I'm talking about using Ignition to build and implement a fully working SCADA solution, customized to your company BUT you know the price and the methods that will be used (it's a replicable framework to get similar results for multiple companies - and the results would be a SCADA solution without the headaches of the unknown prices and engineering characteristics).

Do you think the industrial space could use something like that?

[BevanWeiss]

I don't think this is possible.

Going from no SCADA to having SCADA is an engineering project.  And one of not insignificant effort.

There is no magic formula ahead of time to work out the exact pricing (or effort) involved to perform this task.

There are 'engineering estimates' that are available, but against these are quite subjective.

There is no one 'true cost' for such a project until after it has been delivered and you can just add up the costs that were incurred.

I'm not even sure how you would propose to do the design of such a SCADA system.  It's essentially a software development process, and there are numerous methodologies used for that.. would you adopt a Waterfall paradigm, or an Agile approach?  Each have different risk profiles, and cost factors.

Obviously the Agile approach is the new cool-kid, so you'd have to go with that.. and perhaps even the Scrum approach.. so you'll have sprints, and stand up Scrum meetings.. but how long will the Sprint windows be.. that choice has cost impacts.. and how frequently will Scrum meetings be held..

The reason that SCADA projects end up with cost overruns is because people don't adequately document the requirements upfront.  It's the same issue with general software engineering.  Cost overruns in the IT space are the norm, and are almost always from poorly executed requirements definitions.

Conclusion:

There is no 'one size fits all' SCADA.  So there is 'no one size fits all' SCADA design. So there is 'no one size fits all' SCADA delivery pricing.