Municipality Moves SCADA System from Desktop Computers to Terminal Services

Transcription

1 Municipality Moves SCADA System from Desktop Computers to Terminal Services Standards Certification Education & Training Publishing Conferences & Exhibits Speakers: Bosko Bob Loncar 2014 ISA Water / Wastewater and Automatic Controls Symposium August 5-7, 2014 Orlando, Florida, USA

2 Presenter Halton Region 15+ Years of Experience in Automation SCADA Programmer Halton Region (Ontario, Canada) Water/Wastewater, Energy Private Consultants and Public Sector end users SCADA Standards Halton Region (Ontario) Niagara Region (Ontario) Haldimand County (Ontario) City of Orlando Jefferson Parish (LA) Aug 5-7, 2014 Orlando, Florida, USA 2

3 Presentation Outline Typical SCADA Network The drivers for switching to Terminal Services Fallback Strategy Conclusion Aug 5-7, 2014 Orlando, Florida, USA 3

4 Halton s Typical SCADA Network TCP/IP Network Redundant Windows based SCADA I/O servers 15 redundant pairs Centralized Historian Servers 1 water 1 wastewater Windows OS based SCADA view nodes 80 workstations Operator Interface Terminals Non standard OS Specialized software for development of screens Aug 5-7, 2014 Orlando, Florida, USA 4

5 Original Network Diagram Aug 5-7, 2014 Orlando, Florida, USA 5

6 Business case for switching 2000 hours for application deployment per year Licensing cost Hardware cost Remote site bandwidth Control room enhancements Casual user support Increased control at remote facilities Security increased without local OS Aug 5-7, 2014 Orlando, Florida, USA 6

7 Deployment Benefits Original deployment workflow was time consuming 1. Compress current application from relevant server 2. Copy current application to working machine 3. Update application 4. Compress updated application 5. Copy updated application to Primary Server 6. Archive current (and two legacy) applications on Primary Server 7. Shutdown HMI Software with System Management Console 8. Uncompress updated application 9. Restart server 10. Repeat steps 5-9 for secondary server and all workstations Aug 5-7, 2014 Orlando, Florida, USA 7

8 Deployment Benefits New deployment workflow Deploy primary server as before Deploy Terminal server same as primary server No need to deploy for view nodes since they are thin clients Aug 5-7, 2014 Orlando, Florida, USA 8

9 Licensing Costs License conversion from workstation to thin client Deployment of additional view nodes doesn t require additional licenses for HMI software Use concurrent licensing More expensive per license, but Don t need one for each view node Aug 5-7, 2014 Orlando, Florida, USA 9

10 Bandwidth reduction for remote sites Tag values are not constantly being updated Only need data when an operator is connected Only screenshots updates and mouse clicks are transferred, not tag values Aug 5-7, 2014 Orlando, Florida, USA 10

11 Control room enhacements Multi-monitor units are possible Need license for each screen One mouse and keyboard Unique setup at each plant is possible Alarms on one screen System overview on another Trends Aug 5-7, 2014 Orlando, Florida, USA 11

12 Casual user support Auditors and project managers Can now get access through the terminal service server No need for local HMI software installation No need to tie up licenses until required Aug 5-7, 2014 Orlando, Florida, USA 12

13 Increased control at remote facilities Traditional pumping stations had dedicated OITs Separate software package for screen development Screens can get stale Only monitor local station Touch screen thin clients Updated through terminal services server No need for additional software or development Aug 5-7, 2014 Orlando, Florida, USA 13

14 Fallback Strategy Redundancy is key One traditional workstation per system If the terminal services server fails, the workstation continues to work through IO server Need to be updated any time application is updated Aug 5-7, 2014 Orlando, Florida, USA 14

15 New network configuration Aug 5-7, 2014 Orlando, Florida, USA 15

16 Conclusion Great benefits to the Region Allows more frequent application updates Saves time (money) when doing updates Decreased bandwidth Operator sees very little difference Aug 5-7, 2014 Orlando, Florida, USA 16