SCADA Standards - Section 500 Software Programming Guidelines
Contents
1. 9 6 4 Exception Reporting eite tee te pea stars taste 9 504 PROCESS DISPLAYS e aeaaea ea aaaea aean a ara eeraa Aa a e aae Aaa aaea aa a Aaa a ahaa daa aAa aan RAN doo cd A nada n Rn d nn 10 T STANDARD REQUIREMENT e a tet E od bo a N dae ea E E eee ded Rata 10 Tite ETE AANE abil ENAT BE ATONE ce Mie lib E N E 10 E E 10 Be WERSIONS A AEE eerie thine EN EEEE A bbb tad hte RM LL ehe Lo fercula este oh les Aaa Polar oii tad tura cL A 10 GRAPHIC COLOURS 10 5 GRAPHIC COLOUR RGB STANDARDS ccscunssaitaveccvacntnadsvaaivcecancucssdivacacddadtusassataveccanauauabtnanaavedvadavasnimasacdscuaauss 11 67 PROGRAMMING 5 22 12 Et E 12 0 2 esteem da c b at e ec nta tita 12 Sip E gt 4 N E 12 64 v 12 12 6 67 DA E TA epe cedo per 12 Popp WIDdOWS u fens 19 6 8 Graphic Display Structure Pra ente ern BER er e DUREE edes 13 EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 2 of 23 If this printout is2. 15 o0 o BueDak o o EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 11 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 6 Programming 6 1 Displays Process Overview System Help Features Screens Menu Pop up Control Process Area Alarm Panels for Graphics Subpicture Field Equipment Login Subpicture Lower Level Details Graphics As Needed 6 2 Screen Layout 1 screens must contain a title bar across the top 2 The title bar must display a Name of the graphic display b date time d access icons to i plant overview ii alarm summary iii operator log in iv system features menu 3 The main menu bar must be accessible at all times in order to navigate to appropriate screens 6 3 Texi 1 Font style and size should be suited to the graphic display Preferred font styles are plain such as Simplex or Arial with a minimum point size of 10 6 4 Animation 1 For rotating equipment animation can be used on some occasions Generally animation is distracting and may hinder recognition of other important information such as flashing symbols Therefore animation should be used sparingly Any propos
3. erreur annnm asas aaa a aaa aa aas 24446 23 IECIT 23 2 LAKE HURON AND ELGIN AREA PRIMARY WATER SUPPLY CONFIGURATION 5 23 3 ST THOMAS SCADA CONFIGURATION REQUIREMENTS c0c0ccccccceeeeeeeeececcceseceeeeeseceeesueuaueaueeeseseuaeaueeseeeeeeeeas 23 4 APAM SCADA CONFIGURATION REQUIREMENTS eeeeeerenennne eeenetennn nennt nn sts esas sd as aside dadas nnda 23 5 CENTRAL ELGIN SCADA CONFIGURATION 5 23 EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 3 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 501 General Software Programming Requirements 1 General 1 The overall objective of the software programming standards is to ensure that all modifications are consistent with the overall software design and architecture 2 As much as possible all software subroutines should be based on the existing Joint Board standard modules 2 Hardware Redundancy 1 Atthe Elgin Area WTP and the Lake Huron WTP the facility SCADA s
4. E E oan tua 16 RUDO eet ennt etui 16 1 3 Backup Local Data Storage sse nennen then nne nnns stantu inns inn nnn nnn nnns 16 25 SHORT ERM DATA GOPUEGTIGON 5 iit tota eventi ee b a a feni emet ise dep seme DXX 16 C EA EOCENE mE 16 4 LONG TERM DATA COLLECTION SQL DATA 17 5 PRE GONFIG RED REPORTS ire ir e oss aad esa de ev eec edi a e cene de iai NE Laa 17 6 DATA QUERY TOOLUIITS 5i isset eoru es cet e ees A Xa E REP TRN RO E 17 507 PAGING SOFTWARE CONFIGURATION sos nass ossa 19 A 19 2 ALARM PRIORITIES VS a steterit eter steterit ener eter eren 19 PAGING ALGORITHM icc Ae E E 19 508 VERSION CONTROL SOFTWARE
5. 2 The purpose of this document is to establish standards that will a Determine what information needs to be stored with version control in the SDMS 3 Uniformly applied principles of version control software will help operators respond appropriately to abnormal situations 2 PLC Software Program Version Control Rockwell Asset Centre 1 All current and previous PLC software programs must be stored on the SDMS server Asset Centre for access across the network be maintenance staff 2 When any programming changes are implemented the software programmer must place a copy of the most recent version on the SDMS server at the end of each day 3 The software must be configured to automatically once per week search the network and collect the most recent copies of the PLC programs for storage If any copies are more recent than those previously stored on the SDMS server then an alarm must be generated and issued to the SCADA Maintenance staff 3 Facility SCADA Documentation Version Control 1 The Asset Centre software is also to be used for storing and managing versions of the SCADA documentation including the following Process Narratives amp Software Programming Requirements documents SCADA User Manual SCADA Maintenance Manual Excel spreadsheets of panel listings SCADA ACAD drawings related to control wiring control panels plus other components oococmp 4 SCADA Domain Controller Configuration 1 The SCADA Domain C
6. qaaa qaas aaa 20 E 20 2 PLC SOFTWARE PROGRAM VERSION 20 3 FACILITY SCADA DOCUMENTATION VERSION CONTROL anann nannan nnne 20 4 SCADA DOMAIN CONTROLLER 20 509 SCADA TERMINAL SERVICES SOFTWARE 21 Ws ese TTL HET 21 2 CONFIGURATION REQUIREMENTS ccccccecesesesesesecececeseseeeeeeeseseseseeeeeseeeeeeeeeseeeeeseeeseeeeeeeseeeeeeeseeeseeeseeeeeeeeeeeees 21 3 PORTABLE COMPUTER CONFIGURATION REQUIREMENTS s seseseseseceeeseeeeeseseeeeeeeseeeeeseseseeeeeeeeeeeeeeeeeeeeeeeeeees 21 510 REGIONAL WATER SUPPLY WEB SITE SOFTWARE CONFIGURATION seen nnn 22 dE dd T eme 22 2 CONFIGURATION REQUIREMENTS cccccceceseseseceseceseseseeeseeeseseseeeseeeseseeeseseeeseeeeeeeseeeeeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeees 22 511 DATA BACKUP SOFTWARE CONFIGURATION
7. 4 Additional program standards are as follows a Use the status of any field input only once at the beginning of the ladder to drive the status of a logic relay bit or register word point Rungs that perform this translation of all field inputs form the top section of the ladder Logic points are then used in all later rungs rather than the field inputs b Use only logic points in the second section of the ladder This section contains the rungs that form the actual control logic c Use logic points to drive the field outputs in the third section of the ladder Place any field output coil as an output in only 1 rung d Place all checks for device response together with a timer for each Certain controllers have a built in function to do feedback checks so this section may not be necessary e Group all registers words and relays bits that are of interest to monitoring personnel in sequential blocks This includes setpoints timer limits tuning constants and status flags This simplifies the transfer of this data to supervisory systems Maintain the translated field inputs as per B above in separate block s from other data Use constants in the code only where it is unlikely they will ever be changed Layout I O points having functions for successive devices in identical consecutive blocks For example group the start stop outputs for all low lift pumps in similar order and in adjacent terminals Avoid latches Avoid jum
8. Equipment Runtimes 9 Flows 10 Flows 10 Chemical Usage 11 Storm Report 11 Equipment Run Times 12 CT Report 12 Storm Event 13 Genset 13 Chlorination 3 The monthly reports data to include all parameters indicated on the daily reports For all analog values calculated daily min max avg 4 The yearly reports data to include all parameters indicated on the monthly reports For all analog values calculated monthly min max avg 5 The annual report data shall be a consolidated report of the 12 monthly reports including all of the parameters EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 17 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades SCADA Standards Section 500 Software Programming Guidelines Version 8 6 Data Query Tool Kits Provide pre configured SQL queries to access the historical analog data and dump it into an Excel spreadsheet The query to contain the following selectable parameters Start Year Month Day Hour Minute End Year Month Day Hour Minute Parameter 1 Tag name Parameter 2 Tag name Parameter 3 Tag name Parameter 4 Tag name Parameter 5 Tag name Parameter 6 Tag name Parameter 7 Tag name Parameter 8 Tag name Parameter 9 Tag name Parameter 10 Tag name Provide pre configured SQL queries to access the h
9. for hot standby will have consecutive node addresses to allow for proper operation in the event of a system failure 3 TCP IP Local Area Network Wide Area Network 1 Each device on the local area network or wide area network will have a unique address There will typically be two distinct SCADA LANs in each facility with one being used primarily for PLC to PLC communications and SCADA to PLC communications while the second will be integrated with the wide area network and allow for remote data monitoring and data manipulation between remote sites This configuration will limit unnecessary traffic on the wide area network to minimize costs incurred with charges that are based upon traffic Typically speeds on the local area network will be greater that with the wide area network and will have a higher level of reliability 4 Network Configuration 1 Program all network equipment to enable the required VLAN S layers of Quality of Service firewall routing and network redundancy 2 The network programming to include the implementation of the OPC server for each switch and hub then transferring 10 key parameters per device into the SCADA Server database Also include an overview graphic for each plant and each group of remote sites that indicates the current network performance and status This includes monitoring the network switches at all of the remote sites 3 For the firewalls routers and switches provide a table of the following par
10. more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 6 9 Balt Graphis cesset ude ta 19 7 BIGTURES E O a a a e a a ES a a a 13 mM DIOTE UVENE ONON EEE EEEE AEE E EEE A A EAE A E EE 13 PINEN 2 e e tee a tie eee b ee a ae ase EN 13 8 2 Display Configuration Listings essent nnne nennen inns nennen nnns 13 505 ALARM MANAGEMENT cVannncE P saa coge nv ko Run cOUa gran rrQu QU COS 14 diss GENERAL CIE 14 2 AUVARM MANAGEMENT NER 14 3 GOMMUNIGATION ALARMS 5 2 exire re ee y Te ds cete vtae ve rece sapra ieedres agama ENT CIRCE 14 ALARMIDISPEAYS AND EOGS exei ai eve ca eee eua aee ch s ch adduct os e ve eae ras et e tene 14 5 CAEARMOPRIORITIES s Ie nra Ete RERO e 14 6 TALARM GROUPS ii M 15 VRBE RPANESIPSRRRERRRRRRRERRRRIEUUEIREERR 15 506 HISTORICAL OPERATING DATA MANAGEMENT cernens naa 442a aaa Eo 044 16 T SO TANDARD REQUIREMENUT 5232 270 eet arre et e eee Pee coerente eae et eta ebd e aata teret ess 16
11. Alarm Priorities vs Paging All alarms that are priority 1 2 and 3 must be paged Refer to the process narratives and software programming requirements documents for the number of alarms to be paged 3 Paging Algorithm The alarm pages are to be text messages issued by a dial up telephone connection that communicate to cellular phones with text messaging 2 The text messages must be the same messages that are displayed on the SCADA system 3 The alarm to be unlatched in the WIN911 software such that acknowledging the alarm in the SCADA software also acknowledges that alarm within the paging software Therefore the WIN911 alarms are to be based on the unacknowledged alarm bits 4 General alarms must be paged to three recipients with 15 minute delays between escalation of pages 5 MOE adverse event alarms are to also be paged directly to one selected recipient EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 19 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 508 Version Control Software Configuration Asset Centre 1 General 1 This document provides the specification details to be included in all construction contracts that provide control systems or equipment that generate alarms
12. CADA COmQUIGLIs cere a ud uda 5 3 TCP IP LOCAL AREA NETWORK WIDE AREA NETWORK cccccccccesseeeeccecececaeaeceeceeeeeeceeueseeseeecaeaueaeeeeeeaeeaea 5 NETWORK CONFIGURATION 5 si aust intet ccu dd c eu rea onde a Cas v dea n deu dus e du dad d a d ed d a duds a t d a d d 5 503 PLG SOPT WARE A PEDE 6 STANDARD REQUIBEMENT T ei ie cete eee a ce re need t oae reete 6 a den Pee eee e ev e e i t e etie ee ete dee et heces den tete teet 6 I E a le e E S 6 2 APPEIGCATIONU 2 dee Pew t eee e ede a aa e bn eee aera pede et ete deae seeded 6 EE 6 ek Anica ener de e necne Nineteen Ande d eei tete Adee 6 4 DOCUMENTATION 7 41 Program LIStingSis deno cine dne ce Cate eon gene dica deren cep aka eave ave 7 4 2 bee nce die 7 b PROGRAMMING meiu aai a Dea ul dad E A T SE 7 Bel Memory OrganiZation ite ee LV TE 7 SIANENO Jui EPIRI PE 8 5 3 RHepresentallor thes ee eet estet De a ese dr d eee esi t len 9 Ec TTC PS 9 6 XGOMMUNIGATIONS s 2 AER a erra cer ER YER ELA ER tae dene ove eut va Eta ode eva ea rv EA crt wwt devtaveresen 9 651 2AddresseSd c ou eee be re E d e e e TA 9 6 2 AGOMMON eU d es 9 6 3 Time Synchronization
13. Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 Elgin Lake Huron SCADA Upgrades SCADA Standards Section 500 Software Programming Guidelines Version Date Description of Revision January 2011 As Recorded October 2013 As Recorded As Recorded Updates to Sections 505 and 506 Added Section 512 EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 1 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 Elgin Lake Huron SCADA Upgrades SCADA Standards Section 500 Software Programming Guidelines Table of Contents 501 GENERAL SOFTWARE PROGRAMMING REQUIREMENTG cccccesssssssseecesesensssesnceceeseenanssceceeseseess 4 1 GENERA P 4 25 CHARDWARE REDUNDANGN s 25 1 er eis e o tet ae Um ced Lo oe 4 502 NETWORK COMMUNICATION CONFIGURATION eeeeeee eene n enne menn nana aem erasa aenea asas masas asma ara 5 Ds GENERAL isi n 5 LGP P ADDRESSES Pel dev od cu deu cu cuu eon cu 5 2h PEG cr 5 2 2 S
14. View platform No control functions shall be included on the graphics to minimize the cyber security issues The data on the server must be updated every 5 minutes integrators must submit valid reports to RWS to review prior to implementing them into VantagePoint to be viewed on the website as well as the local Vantagepoint servers running at the appropriate plant Reports may include Daily Monthly yearly equipment runtimes flow pressure or turbidity values EA LH SCADA Standards 500 v6 doc The only actual version of this document is the web site not a printed version 22 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 BONAM ONA on gt ai 511 Data Backup Software Configuration General This document provides the specification details to be included in all construction contracts that provide control systems or equipment that generate alarms Uniformly applied principles of an offsite data backup will minimize the risk of loss of electronic information Lake Huron and Elgin Area Primary Water Supply Configuration Requirements The Lake Huron and Elgin Area Primary Water Supply data backup server is located at the London Museum This server must back up key data on the Lake Huron WTP computers on a nightly basis This server must back u
15. ach point For real I O the list must also show the hardware address Programming 5 1 Memory Organization 1 PLC memory shall be organized into three major sections a Registers b Control c Communication 2 Each section should contain memory for expansion up to the overall limit defined in the technical specifications for the PLC Within each section the memory should be further organized into logical blocks as shown in the Memory Partition Table 3 Registers EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 7 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 a I O should be organized in the same hierarchy as used for program structure For PLC s in which I O point numbering is not restricted to a pattern the I O should be assigned to addresses within the I O register section The I O register should be split by type of I O analog inputs analog outputs digital inputs and digital outputs for similar devices should be put in the same order of address b For PLC s in which I O point numbering is restricted to a pattern the assignment of addresses may be partially predetermined As much as possible follow the considerations for organization given in the preceding parag
16. ameters as well as the configuration file in an organized text file Connected device name and description Interface Port Speed 10 vs 100 Duplex half vs full Media FX vs OTP VLAN s Pruned VLAN s Quality of Service Priority sco coococop EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 5 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 1 1 1 2 1 3 3 1 PLC Programming 1 503 PLC Software Standard Requirement 1 1 Introduction This document is a guideline to the structure and documentation of PLC programs PLC shall be used as a common term for both RPU and RTU 1 2 Purpose The purpose of this document is to establish standards for a consistent approach to programming Consistency will enable a maximum re use of programs b reduced time to troubleshoot programs c more confidence and usability of PLC based control systems Application This standard applies to all PLC s which contain custom programs General PLC programming is to include system signals for monitoring the health of the communication link detecting the PLC faults alarming I O points failure AC power failed errors during tasks execution etc All of them shall be assigned as c
17. ator down alarm 2 Level 2 alarms require top priority operator attention caution and action Level 2 alarms are defined as those involving a Personal safety of the operator eg fire gas detectors etc b Computer and PLC failures computer redundancy failures etc c Intrusion alarms d Spill alarms in which the natural environment could be impacted eg loading panel chemical spill e Potential asset damage due to flooding EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 14 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 f Reservoir water storage levels as overflows can impact the natural environment or cause flooding g Power failure UPS utility and battery alarms 3 Level 3 alarms are those associated with critical regulatory instruments and therefore require immediate operator attention Level 3 alarms have the potential to either be or escalate to an Adverse Water Quality Incident AWQI reportable to the Ministry of the Environment MOE or may have regulatory monitoring or other impacts The Operator must intervene and take corrective action The Operator must enter into the logbook when the alarm occurred why and what actions they took 4 Level 4 alarms have the potential to im
18. by facility 3 Allalarms are displayed on a separate HMI Alarm Log graphic which can be sorted by facility This includes approximately 7 days of alarm history EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 16 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 4 Long Term Data Collection SQL Data Storage 1 analog and discrete parameters related to regulatory compliance as well as any relevant information must be collected into the SCADA SQL database There is no actual historian Transaction Manager is used to poll plc data tables directly Data is stored in plc memory until Transaction Manager polls the data and stores it to the SQL database 2 n general analog parameters are to be stored as per the following Parameter Time Period Calculation Facility Flows 5minutes Min Max Avg valueforeach period Chlorine Residual 5minutes Man Max Avg valueforeach period _ Turbidity 5minutes Min Max Avg valueforeachperod ReservoirLevels 5minutes Instantaneous value for each period Equipment Run Times Snapshot at end of each period Other Flows Instantaneous value for each period Vin Max Avg value for each period 3 All r
19. coloured according to the following table Status Condition Normal Condition Warning Condition including Out of Service Hed Alarm Condition Yellow Flashing Warning Condition with an unacknowledged alarm Red Flashing Alarm Condition with an unacknowledged alarm EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 10 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 1 Colours may be used to represent the contents of piping and tankage on the operator displays The following table lists the standards for colours for contents Colour Material Carried Stored Raw Water Potable Water Raw Sewage Sludge Scum or Waste Holding WTP Effluent Chemicals Digester or Natural Gas General use borders and outlines and Text Air 5 Graphic Colour RGB Standards 1 In an effort to ensure colour consistency the following table defines the colour according to the Microsoft standard Colour Name Red R Green G Blue B Red 35 0 1 9 Green 0 2 2355 0 Bue Dak J 0 2 20 Jp 190 Bue 1 1 0o o 25 Yellow 0 0 0 0 1 25 2355 9 Magenta 25 9 1 235 Grey Medium Grey Light Oane 25 3 9 Bl OO E308 Bom
20. cument provides the specification details to be included in all construction contracts that provide control systems or equipment that generate alarms It should also be used in design as a guideline to what alarms need to be brought into the control system The purpose of this document is to establish standards that will a determine information that needs to be alarmed b prioritize alarm information given to operators Uniformly applied principles of alarming will help operators respond appropriately to abnormal situations Alarm Management When a field alarm occurs the alarm is latched in software for safety reasons The associated device will not be restarted until the alarm is cleared In order for the alarm to be acknowledged and eliminated two events must occur The field condition creating the alarm must be corrected and the alarm must be acknowledged by the operator either at the PLC or SCADA workstation Power interruptions do not lock out pumps in software Communication Alarms Communication links are monitored for failure and when a failure is detected an alarm will appear on the operator workstation All points associated with stations using the failed communications link will not be alarmed until such time that the communications link is restored This will result in a lesser level of nuisance alarms A communication link failure should be addressed immediately and therefore should be configured as a Level 1 alarm The co
21. d PLC clock shall be accessible from the Operator Workstation Alarm times will be synchronized where a time stamp is required for alarms that are recorded during communication failures 6 4 Exception Reporting Where information is reported over networks on an exception basis the default exception limits shall be as follows a Digital values Upon change of state b Analogvalues flow 196 of range level 296 of range d pressure 296 of range e temperature 296 of range f quality or analysis 296 of range g other 396 of range 2 lfinformation is communicated on exception as well as on polled or timed basis the possibility may exist that the most up to date information may not always be received Control applications should only use unambiguous communications or be able to reduce conflicts to an acceptable level At a minimum control communications require one or more of the following a Repeated messages b Time and date stamping at the point of transmission c Tighter time synchronization EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 9 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 504 Process Displays 1 Standard Requirement 1 1 General 1 This document is a guideline to the structure and
22. documentation of process displays 2 The purpose of this document is to establish standards for a consistent approach to programming Consistency will enable a maximum re use of programs b reduced time to troubleshoot programs c more confidence and usability of operator workstations 2 Application 1 This standard applies to all SCADA Server Terminal Server Web Server VantagePoint and the related operator workstation configurations 3 Versions 1 Each graphic display when updated will automatically be recorded in the AssetCentre thus can be queried 4 Graphic Colours 1 The SCADA system is detailed on several graphic displays each representing a distinct part of the process Each process screen is designed to appear as similar to the actual layout of the system or process as possible Standard ISA symbology is used to represent equipment such as pumps valves and transmitters 2 Colours are used to represent the status es of various pieces of equipment or their components on the operator displays and their current use 3 Forthe ALARM condition indicators the background of the indicator block must be red and the fonts must be amber in order to highlight the ALARM condition The following table lists some standard colour conventions Red Equipmentisin ALARM condition O 1 Values and units appear at various locations on the screen to represent current flows levels and pressures They are to be
23. ed use of animation to be identified to the Joint Board for their approval 6 5 Icons 1 Icons should resemble field equipment to make recognition easier All symbols must be based on the Joint Board library Label each icon with the equipment number 2 Icons incorporate the colour and alarm conventions The colour convention including rules for using flashing to indicate unacknowledged alarms is given in the graphic colours standard 3 Provide each icon with access to its corresponding pop up window 6 6 Pushbuttons 1 Use pushbuttons to call up menus trends and other displays EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 12 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 6 7 Pop up Windows 1 Pop up windows should initially appear on the left side of the screen ensuring minimal coverage of the screen Pop up windows may be moved and sized by the operator Pop up windows will contain a the name and description of the equipment or item on the top b current status e g running off opened closed enabled disabled manual automatic cascade alarm normal current conditions e g speed position electrical current current alarms and acknowledge function controls e g start stop open close setpoint e
24. egulatory min max avg data stored in SQL is calculated over a period of 5 mins utilizing the plc 1s poll time 4 All alarm events are also to be logged in MSSql The information includes Alarm Tag Alarm Description Time Date of Alarm Alarm Value Alarm threshold values Alarm Label units o c oococp 5 Pre Configured Reports 1 Daily Monthly and Annual Reports per facility are required for MOE compliance All new equipment being integrated to SCADA must be evaluated for relevance to a report whether compliance or otherwise 2 The daily report data generally includes the following parameters All revisions upgrades must be reviewed and accepted by the Joint Board prior to implementation a All analog data should be provided to a trend within the HMI b All analog data shall have a min max avg value calculated within the plc utilizing the datalog subroutine code The min max avg data will be calculated in the reports displayed in Vantagepoint c To date reports included within Vantagepoint for Huron WTP and Elgin Area WTP are as follows Huron WTP Elgin WTP 1 Raw Water Quality 1 Raw Water Quality 2 Flocculation Turbidity 2 Flash Mix Water Quality 3 Settled Water Quality 3 Settled Water Quality 4 Treated Water 4 Treated Water Pressure 5 Filtered Water 5 Treated Water Quality 6 Suction Conduit Water Quality 6 Filtered Water Quality 7 Chemicals 7 Filtered Water Process Details 8 Particle Counts 8 Particle Counts 9
25. ents 1 The portable tablets must be configured for accessing the SCADA Terminal Services Server via the wireless network within the plants EA LH SCADA Standards 500 v6 doc The only actual version of this document is the web site not a printed version 21 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 ok 510 Regional Water Supply Web Site Software Configuration General This document provides the specification details to be included in all construction contracts that provide control systems VantagePoint Part of the Rockwell Automation FactoryTalk View platform is utilized to provide a public web site which enables the secondary and tertiary water operators to monitor the Primary Water Supply SCADA system It allows viewing of the SCADA screens as well as pre configured reports The VantagePoint Server for the website is located at Museum London Configuration Requirements The intent of the website is to enable various external water users to monitor the Lake Huron and Elgin Area SCADA systems using a web based application All remote facility and plant process area overview graphics on the SCADA Servers must be ported over to the SCADA Web Server located at museum London which utilizes VantagePoint which is part of the Rockwell Automation FactoryTalk
26. fficiently evaluate system performance 1 3 Backup Local Data Storage 1 For all remote facilities provide a local data backup system which can store 7 days of historical operating data 2 Continuously log locally all regulatory parameters plus other values to be specified by the Joint Board 2 Short Term Data Collection 1 In general short term data collection includes analog instrument readings and related field device inputs All of these are continuously monitored by their respective PLC The following table defines the typical parameters and typical HMI poll times The following data is stored locally on the primary HMI Server as a dat file A new file is created each day at midnight and the date is prefixed to the dat For example 01012013 dat Jan 01 2013 In Plant Parameters Parameter Poll Time General Field DI General Field AI Remote Facility Parameters Parameter Poll Time General Field DI General Field Al 2 The selected parameters are to be stored in the SCADA HMI Historical Logging with the following settings Discrete values are only Report by Exception and time stamped when a change in state occurs Analog Parameter Logger Time Period Deadband Other Analogs 3 Alarm Logging 1 All alarms are logged separately from process events in separate alarm log files for review by management 2 Allactive alarms are displayed on a separate HMI Active Alarms graphic which can provide sorting
27. he back up requirements are equal to those specified for the Primary Water Supply SCADA Systems EA LH SCADA Standards 500 v6 doc The only actual version of this document is the web site not a printed version 23 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 512 Software and Files Review 1 General 1 This document provides the specific software and miscellaneous documentation files that all integrators must have full knowledge of prior to bidding or doing work on the RWS SCADA control system 2 The following list includes software and documentation files that must be considered in all construction contracts associated with the RWS control system PLC programming software RSLogix 5000 v15 or v16 depending on location of Contrologix PLC PLC programming software RSLogix 500 for compactlogix RSLinx Classic RSLinx Enterprise RSNetworx for Devicenet and Controlnet FactoryTalkView Studio 5 00 00 CPR9 VantagePoint Ver 3 1 7105 0 Used for Web Portal Reports and HMI Overview Screens Process Narrative SCADA User Manual 10 Software Programming Requirements EA LH SCADA Standards 500 v6 doc The only actual version of this document is the web site not a printed version 24 of 23 If this printout is more than 24 hours old check web site for a more c
28. ing and control The preferred language is ladder logic whenever possible 7 The software programming standard is to be based on the library of process control programs capable of controlling specific unit processes The process control library shall contain function blocks subroutines or modules which can be used extensively in order to simplify software implementation and maintenance The process control library consists of at least the following functions as a minimum a Remote Local control operation of all connected equipment using the device I O standard modules b Alternating pumps based on duty cycle or failure c Alarm detection and annunciation c w Acknowledge Reset and Test Pushbuttons functions d Interface with local HMI or keyboard display e Program Flow Control Proportional P Proportional plus Integral PI Proportional plus Integral plus Derivative PID f Lead Lag module to dampen analog signal g Averager Totalizer Integrator Calculator Comparator etc h Accept and store field data from field device i Time and date stamping critical alarms EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 6 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 8 10
29. istorical alarm log and dump the data into an Excel spreadsheet The query to contain the following selectable parameters Start Year Month Day Hour Minute End Year Month Day Hour Minute gt e7oDa900D Alarm Priority Parameter 1 Tag name Parameter 2 Tag name Parameter 3 Tag name Parameter 4 Tag name Parameter 5 Tag name Parameter 6 Tag name Parameter 7 Tag name Parameter 8 Tag name Parameter 9 Tag name Parameter 10 Tag name EA LH SCADA Standards 500 v8 doc If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 The only actual version of this document is the web site not a printed version 18 of 23 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 507 Paging Software Configuration General 1 This section is only applicable for the SCADA Systems of St Thomas Central Elgin and APAM 2 This document provides the specification details to be included in all construction contracts that provide control systems or equipment that generate alarms It should also be used in design as a guideline to what alarms need to be paged 3 The purpose of this document is to establish standards that will a Determine information that needs to be paged b Identify how paging will be programmed 4 Uniformly applied principles of alarm paging will help operators respond appropriately to abnormal situations 2
30. mmunication link alarms must include links related to field devices connecting using a fieldbus Remote I O racks PLC SCADA servers SCADA workstations and all other server Any points associated with a remote station that are deemed to be critical or top level alarms may have local date and time stamping installed This information can then be fed into the SCADA system for recording In plant communication network will be less susceptible to failure therefore only very critical points associated with these PLC s to have local date and time stamping for alarming Communication link failures should not affect the operation of system totalizers such as runtimes and flow totals All totalized values will be maintained within their associated PLC such that a communication link failure will not adversely affect the accumulated sum Alarms shall be stored historically for archiving purposes Alarm Displays and Logs Alarms originating from field contacts or generated by software shall be displayed at the local and main SCADA workstations Alarms shall have a configurable option to be logged on a printer The time and date of occurrence shall be displayed and logged if configured for printing as well as the time of acknowledgement and return to normal Alarms should be stored in history files for a minimum time period of one year Alarm Coding Level 1 alarms are critical alarms that are paged off the site In this case this includes only the oper
31. n order to simplify scaling of analog values the preference is to do scaling only in the field I O filter 2 Data manipulations such as summation and subtraction for displays or historical data will be done in the PLC 6 6 1 Addresses 1 1 1 1 software Communications Each node on a PLC communications network must have a unique address on that network Node addresses shall be chosen to integrate into existing networks and conform to the existing Coding System Standard Nodes shall be assigned in consecutive node addresses PLC s in hot standby shall have the same node address as their primary PLC 6 2 Control Control and monitoring should continue without disruption in the event of communication failures Where control functions rely on information affected by communications failure a safe mode of control shall be provided Design of software should seek to reduce the amount of messages transferred between PLC s to the minimum Store Date and Time for certain alarm points such that upon restoration of communication this information can be relayed to a SCADA computer Any process control setpoints shall be updated upon restoration of communication 6 3 Time Synchronization All nodes on a PLC communications network shall have internal clocks synchronized periodically to a master clock Synchronization shall provide any required time and date stamping accuracy to within one second of the master clock Master clock an
32. ntries mode selection manual automatic cascade enable disable details button to access data page with detailed information about the equipment or item future Local Remote handswitch indicator 2o ooo 6 8 Graphic Display Structure 1 The displays will be interconnected in a hierarchy structure In addition interconnection will be provided for process streams continued on other process graphics 6 9 Bar Graphs 1 Use bar graphs to show important measurements such as reservoir levels 7 Pictures and Sub Pictures 1 All window control i e task bar shall be hidden from operator access When a new picture is launched the previous picture with all associated sub pictures shall be closed at the same time Redundant pictures and sub pictures shall not be hidden 8 Documentation 8 1 Screen Print 1 The method of documentation for graphic displays is to print a colour copy of the graphic display and list the display configuration 8 2 Display Configuration Listings 1 A print of all configuration listings is required for each operator workstation EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 13 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 505 Alarm Management General This do
33. on Sound Operator Display Background Colour High frequency pulse High frequency pulse Low frequency pulse Yellow Alarm characters are black EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 15 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 506 Historical Operating Data Management 1 Standard Requirement 1 1 General 1 This document provides guidelines on the specification details to be included in all construction contracts that provide SCADA systems with historical storage capability As well this document covers the generation of reports from within the SCADA system It should also be used in design as a guideline to what information is historically archived and what information is to be made available for system reports 1 2 Purpose 1 The purpose of this document is to establish standards that will a determine information that needs to be archived b determine the frequency that information will be archived determine the reports that will be available on archived information d determine the storage system for information to be archived 2 Uniformly applied principles of archiving and reporting will help management and operators to use information obtained by the SCADA system to more e
34. ontroller must be configured to enable the ASSET CENTRE to locate the various components on the network EA LH SCADA Standards 500 v6 doc The only actual version of this document is the web site not a printed version 20 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 509 SCADA Terminal Services Software Configuration General 1 This document provides the specification details to be included in all construction contracts that provide control systems or equipment that generate alarms 2 Uniformly applied principles of remote monitoring and control will help operators respond appropriately to abnormal situations 2 Configuration Requirements 1 The intent of the SCADA Terminal Services Server is only to enable staff to monitor and control the SCADA system using tablets within the plant 2 All graphics on the SCADA Servers are available to the Terminal Services Server so that operations staff utilizing the portable tablets within the plants can monitor and control the process via the wireless LAN WAN installed across the facility 3 Access to the server must include password security 4 The server must be configured for a minimum of three levels of users a Monitoring Only b Limited Control c Full Control 3 Portable Computer Configuration Requirem
35. p key data on the Elgin Area WTP computers on a nightly basis The following plant SCADA Server files are to be backed up a Historical Trend Files b Historical Alarm Files The following plant SCADA Historian files are to be backed up a SQL database records b SQL configuration The following SDMS server files are to be backed up a PLC programs b SCADA Server configurations c Network equipment configurations On a monthly basis triggered manually by staff the software must execute a full backup of the following computers at each plant a SCADA Servers b SCADA Historian c SDMS Server d Terminal Services Server St Thomas SCADA Configuration Requirements The St Thomas data backup server is located at the St Thomas City Hall This server must back up key data on the St Thomas SCADA computers on a nightly basis The back up requirements are equal to those specified for the Primary Water Supply SCADA Systems APAM SCADA Configuration Requirements The APAM SCADA data backup server is located at the Malahide offices This server must back up key data on the APAM SCADA computers on a nightly basis The back up requirements are equal to those specified for the Primary Water Supply SCADA Systems Central Elgin SCADA Configuration Requirements The Central Elgin SCADA data backup server is located at the 450 Sunset Dr St Thomas corporate offices This server must back up key data on the Central Elgin SCADA computers on a nightly basis T
36. pact CT monitoring potential regulatory impact or contractual performance obligations Level 4 alarms also include alarms related to water quality monitoring instruments that are not regulatory but could have a potential impact on process eg raw and settled water turbidity Level 4 alarms require operator attention and possible corrective action or additional monitoring 5 Level 5 alarms require operator attention and are defined as those that may cause the immediate shutdown of equipment such as a motor overload condition hot backup failure safety shutdown high high level temperature flow etc This generally includes the analog High High High Low and Low Low alarm limits These alarms indicate the potential for large equipment damage major cleanup or possible process obstruction Chemical tank levels are also Level 5 alarms 6 Level 6 alarms are communication failures These are segregated in a separate group so they are easy to sort when needed 7 Level 7 alarms include those that require operator attention as soon as possible but do not result in the immediate shutdown of equipment Examples are failure of auxiliary systems instrument air lubrication system heating cooling ventilation system backup instrument uncommanded start stop of equipment equipment failure to start stop lockout etc 8 Level 8 is for process events not alarms to differentiate the events from alarms and allow filtering and sorting of alarm
37. ps Avoid drum sequencers Label every register word relay bit and rung with a name or comment Don t sacrifice program clarity and simplicity to achieve higher execution speed and smaller code size All PLC programs shall conform to IEC 1131 and IEC 848 In addition the programs written for critical or hazardous applications shall conform to CAN CSA Q396 Quality Assurance Program for the Development of Software Used in Critical Applications Each control program shall be identified by its version number Vx x and its name The location of each copy of the program shall be recorded Documentation 4 1 Program Listings 1 All applications programs shall be listed in the control language used by the hardware running the program The listings should show the compiled control language if a compiler is required to convert the program into a runtime version The entire program shall be annotated Each I O derived value register and coil subroutine and object shall be identified by a descriptor Values of tuning parameters and constants shall be included 4 2 Parameter Listings 1 5 All parameters used in application programs shall be listed These lists include I O lists for controllers historical data bases and operator stations Software addresses for I O and derived values shall be included for controllers that allow addresses to be used in applications programs The list shall show the software address and descriptor for e
38. raph 4 Control a Logic for control should be organized according to object composition b Logic for the watchdog timer and system clock should be located first in this section if they are not part of system software or hardware 5 Communications a Blocks of memory should be allocated for communication with other intelligent devices For communication with an operator station a separate block or blocks should be set up for an alarm and event array The alarm and event array may be split into separate blocks one for alarms and one for events Even if alarms are also used for control they should be copied to the alarm block Separation of alarms is useful for testing alarm reporting separate from control logic b Within the communication section separate blocks should be set up for communication to minimize the number of messages needed to communicate data Typically this means that a block for analog values a block for receipt of operator commands and a block for setpoints and other parameters should be set up A block for communication to and from other PLC s may need to be separate from the operator station interface blocks in order for fast communications Memory Partition Table Block Function Collaborator VO Registers Analog Input ProcessControl Analog Output jProcessContol O Digital Input jProcessContol Dig
39. ritical alarms for immediate attention 2 The PLC programming logic consists of three 3 blocks The first block completes the mapping of the input signals to software equivalents Next is the process control program and the last block consists of the PLC HMI Interface mapping 3 The field input output block performs the following functions a For all DI where required a 1 2 second debounce timer is included b Forall the raw values are converted to engineering units C All DI Al DO and AO are mapped to bits which are then used throughout the PLC software d The internal bits are used to map into the PLC HMI interface table where possible 4 The PLC HMI interface table within the PLC program collects and consolidates all I O that must communicate between the PLC and the HMI software This translator mapping table shall be the only location that the HMI or other PLC s communicate with the PLC program 5 n some situations values are communicated directly between PLC s or between a PLC and its related field bus Ethernet serially connected field devices Provide separate I O interface tables for each communication interface 6 The process control program where appropriate shall use either Ladder Diagram Boolean and Math Operators Modules Function Blocks or a combination thereof for programming sequential or digital logic Programs shall be executed under multi tasking environment with appropriate priority monitor
40. s by staff For further clarification an event is defined as a state change of a field DI that has not been previously defined as an alarm Therefore an event might be a pump start pump stop valve open valve close etc Alarm conditions from auxiliary systems that are essential to the functioning of the control system or process equipment instrument air supply systems and equipment lubrication systems for example should also be monitored for critical alarms The Level 1 6 are considered to be High Priority Alarms and therefore when they occur the HMI graphics should indicate this condition using RED Level 7 is considered to be a WARNING and therefore the HMI graphics should indicate this condition using YELLOW Level 8 is considered simply a process event and therefore is not highlighted on the graphics When Level 6 Communication Alarms occurs the graphics must also indicate that the values displayed are not necessarily accurate because communication has been lost 6 Alarm Groups 1 All alarms must be organized by alarm groups Each remote site must be a separate alarm group and each plant area must be a separate alarm group 2 In order to also have separate MOE warning and MOE alarm groups the one field alarm must be configured as two SCADA database points with one point organized by the area alarm group and the other point organized as the MOE alarm or warning group 7 Alarm Matrix Alarm Level Operator Workstati
41. talOuput ProcessContro Control Re ew pei Watchdog Timer and Clock Process Control Other Control ProcessContro Communications Operator Interface Operator Interface Operator Interface Operator Interface Operator Interface Other PLC s 5 2 Objects 1 Where possible the program shall make use of standard objects or subroutines Standard objects may come from the standard library of objects or if not available there then created for the application Objects created for an application are to be submitted to the Joint Board for consideration as a standard object 2 Standard object list a 2 State Device b 3 State Device c Variable Speed Device d Digital Input e Analog Input f Flow Input g PID Control Station h Timer i Counter EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 8 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 1 1 Sequencing Scheduling Lead Lag Control Block Totalizer Averaging J Rath 5 3 Representation The control logic should present all control actions directly and avoid using the same address or block of addresses for multiple uses 5 4 Scaling I
42. urrent version Printed 1 18 2011
43. ystems consist of redundant ControLogix PLC and redundant SCADA Servers The software configurations to include hot standby switching upon a hardware failure with no impact on the historical data collection or real time control EA LH SCADA Standards 500 v8 doc The only actual version of this document is the web site not a printed version 4 of 23 If this printout is more than 24 hours old check web site for a more current version Printed 1 18 2011 Elgin Lake Huron SCADA Upgrades Section 500 Software Programming Guidelines SCADA Standards Version 8 502 Network Communication Configuration 1 General 1 This document is a standard specification for a communications protocol to be used by the various SCADA Systems It should be used as a guideline when installing new systems that must communicate over a LAN local area network or a WAN wide area network 2 TCP IP Addresses 2 1 PLC 1 Each node on a PLC communications network must have a unique address on that network Node addresses shall be chosen to integrate into existing networks Nodes shall be assigned in consecutive node addresses PLC s in hot standby shall have duplicate node addresses to allow for continuous data collection in the event of a PLC failure 2 2 SCADA Computers 1 Each SCADA Computer located on either the local area network or wide area network shall have a node address that allows it to be integrated into the existing network SCADA computers configured
Download Pdf Manuals
Related Search