[Info-vax] OpenVMS versus Windows/GE Telemetry Control Systems.

[Bob Gezelter]

On Thursday, January 10, 2013 11:08:35 PM UTC-5, cyberun... at gmail.com wrote:
> I work for a large Water Utility. Our SCADA Telemetry Control System uses Alpha Servers. Management wants to scrap OpenVMS and go with a SCADA System by GE called iFix that runs on Windows. I'm told that HP can't be trusted to continue with OpenVMS and they may discontinue the Itanium Machines. Also, it's too hard to find VMS Experts in the work force. Also, I'm told that the industry is moving from OpenVMS to Windows everywhere. 
> 
> 
> 
> Can I please have your thoughts concerning my predicament?
> 
> 
> 
> Thanks.

Cyberrun,

There are multiple questions here.

OpenVMS is still an HP product, with officially committed support dates. The Alpha hardware is still usable, and supported through various channels (e.g., Nemonix). I would not worry about the short and intermediate term support issues. Long term, I would at the least, want to move to an Itanium system.

The Windows arguments are far less clear. Each Windows version has a life of a handful of years, and longevity IS an issue. In that world, system lifespans are often presumed to be three to five years. Older hardware is often a problem for new software releases, and newer hardware is often not supportable on older software releases. With these lifecycles, sparing hardware can, and often is, far more of a challenge than those in the OpenVMS community are used to.

Proficiency, security, and uptime are also critical issues. While there may be a plentiful supply of those who "know" Windows, the depth of what constitutes "Windows" knowledge is often far shallower than in the OpenVMS world. The answer "Just wipe it out and start over" is unacceptable in the OpenVMS world, in the Windows world it is commonplace. When one equalizes the proficiency levels and depth of knowledge, the "gap" quickly shrinks, both in cost and availability.

Windows systems also have had extensive security problems requiring ongoing patches. Adopting Windows means adopting its patching requirements.

Overall, it depends upon your current SCADA environment. Is it locally developed, or supported by a vendor? If locally developed, do you have complete sources? What are the true costs of each of the alternatives? I have seen quite a few cases where the "savings" never materialized and the costs of the new system were far higher than projected. Additionally, any change in SCADA system should look at the security implications, one does not want to install a system which will then increase one's vulnerability to outside interference.

- Bob Gezelter, http://www.rlgsc.com