CS-12 SCADA STANDARD SPECIFICATIONS

January 2024

Rev. 4 ii

VERSION CONTROL

Issue Revision No Date Issued Description Reviewed by

1 0 September 2019 Ini)al Release Arcadis

2 1 September 2020 Version 1.1 Opera)ons Group

3 2 June 2021 Version 1.2 Opera)ons Group

4 3 March 2022 Version 1.3 Opera)ons Group

5 4 January 2024 Version 1.4 Opera)ons Group iii

CONTENTS

Abbrevia)ons & Acronyms ........................................................................................................................................... viii

1 Purpose & Overview

1.1 Nomenclature and Tagging

1.2 Document Updates

1.3 Integrator Qualifications

2 SCADA So5ware Management Procedures

2.1 Asset Management Software

2.2 SCADA So5ware Versions

3 SCADA Hardware Standards

4 SCADA Control Panel Standards

4.1 Control Panels

5 SCADA Applica)on Programming Standards for PLC, OIT, and DCS

5.1 So5ware Registration

5.2 So5ware Versions

5.3 So5ware Development Licensing

5.4 PLC and OIT Software

5.5 Computer Opera)ng System Software

5.6 File Synchroniza)on Software

5.7 Virtual Machine Software

5.8 Programming and Configura)on Standards

6 SCADA Human Machine Interface (HMI) Software

6.1 HMI Workshop Specification

6.2 HMI Alarm Configura)on Specification

6.3 HMI Configura)on Specification

7 High-Performance Human Machine Interface (HMI) Applica)on Programming

8 SCADA Data Historiza)on And Archiving Standards

8.1 Historian Software

8.2 Report Software

9 SCADA Network and Network Hardware Standards

9.1 Network Hardware

9.2 Network Cable and Wiring

9.3 Network Designer Guidance

iv

9.4 Network Tes)ng and Startups

10 SCADA Cybersecurity and Networking Monitoring Standards

10.1 Cybersecurity Implementation

10.2 Network Monitoring and Intrusion Detec)on System (IDS)

10.3 ICS Network Penetra)on Tes)ng and Cybersecurity Vulnerability Assessment

11 Specifications

11.1 Input / Output List

11.2 Process Control Narrative

12 Design, Review, Acceptance, and Change Management

12.1 Design SubmiBal Requirements

12.2 Design Review Requirements

13 Drawings

13.1 Loop Drawings

13.2 Design Document Drawing Set Format and Title Block

13.3 Network Diagram Drawings

13.4 P&ID Drawings

13.5 PLC Panel Drawings

13.6 Instrument Installa)on and Moun)ng Details Drawings

14 Factory and Site Testing

14.1 Factory Acceptance Testing

14.2 Start-up and Field Testing

15 SCADA Documentation

15.1 Opera)on and Maintenance Documentation

15.2 Record Document

16 Design/Build Projects

16.1 Requirements of a Project

17 SCADA Equipment Guidelines for Water Treatment Plant Processes

17.1 Requirements of a Project

v

TABLES

Table 1 Firmware, So5ware, and Opera)ng System Version Table

Table 2 Designer Selec)on Guide for PLCs

Table 3 Panel Types

Table 4 Standards for Signal and Power Conduit Separation

Table 5 Terminal Blocks

Table 6 Insula)on Wire Colors for 120 VAC

Table 7 Insula)on Wire Colors for Low Voltage (Typically 24 VAC/DC or less)

Table 8 Insula)on Wire Colors for Other Connections

Table 9 PLC I/O Signal Type

Table 10 UPS Type Summary

SPECIFICATIONS

Specifica)on 1. Integrator Qualifications

Specifica)on 2. SCADA Change and Asset Management Procedure

Specifica)on 3. Programmable Logic Controller (PLC) (Large Form Factor)

Specifica)on 4. Programmable Logic Controller (PLC) (Mid Form Factor)

Specifica)on 5. Programmable Logic Controller (PLC) (Small Form Factor)

Specifica)on 6. Ethernet / IP Taps

Specifica)on 7. Modbus Gateway (PLC)

Specifica)on 8. Operator Interface Terminal (OIT)

Specifica)on 9. Distributed Control System (DCS) Controller

Specifica)on 10. SCADA Server

Specifica)on 11. Thick Client Workstation

Specifica)on 12. Industrial PC

Specifica)on 13. Computer Monitor

Specifica)on 14. Wall Mount Monitor

Specifica)on 15. Thin Client Workstation

Specifica)on 16. Modbus Gateway (DCS) vi

Specifica)on 17. SCADA Control Panels

Specifica)on 18. Surge Protection

Specifica)on 19. Power Supplies

Specifica)on 20. Main and Branch Circuit Breakers

Specifica)on 21. Selector Switches, PushbuBons, and Indica)ng Lights

Specifica)on 22. Control Relay

Specifica)on 23. Time Delay Relay

Specifica)on 24. Intrinsic Barriers

Specifica)on 25. Current Isolator

Specifica)on 26. Fiber Patch Panel (Panel Mount)

Specifica)on 27. UPS (Panel Mount)

Specifica)on 28. UPS (Rack Mount)

Specifica)on 29. UPS (Area)

Specifica)on 30. Instrument Cable Wire

Specifica)on 31. Programmable Logic Controllers (PLC)

Specifica)on 32. Operator Interface Terminals (OIT)

Specifica)on 33. Distributed Control System (DCS)

Specifica)on 34. HMI Workshop

Specifica)on 35. HMI Alarm Configuration

Specifica)on 36. HMI Configuration

Specifica)on 37. SCADA Trending Configuration

Specifica)on 38. Rack Enclosure

Specifica)on 39. Rack-Mount Console KVM Switch with LCD

Specifica)on 40. Root Network Switch

Specifica)on 41. Fanout Ethernet Switch

Specifica)on 42. Router

Specifica)on 43. Firewall or Security Appliance

Specifica)on 44. Firewall or Security Appliance

Specifica)on 45. Data Diodes

Specifica)on 46. Fiber Patch Panel (Rack Mount)

Specifica)on 47. NAS Device vii

Specifica)on 48. Cellular Router

Specifica)on 49. Fiber Op)c Cable

Specifica)on 50. Ethernet Cable

Specifica)on 51. Ethernet Cable RJ45 Jack

Specifica)on 52. SCADA Networking Tes)ng and Startups

Specifica)on 53. Cybersecurity Implementa)on for SCADA Projects

Specifica)on 54. Control Strategy Format Example

Specifica)on 55. Factory Acceptance Testing

Specifica)on 56. OAD

APPENDICES

Appendix 12-A SCADA Nomenclature and Tagging Guide

Appendix 12-B Sample PLC and Local Panel/Drawings

Appendix 12-C SCADA Applica)on Programming Samples

Appendix 12-D Sample I/O List

Appendix 12-E Sample P&ID Drawings

Appendix 12-F Sample Record I/O List

Appendix 12-G Sample Record Instrument List

Appendix 12-H Sample Plant-wide Control System Network and Ova)on Demo/Revised Diagrams

Appendix 12-I Sample Loop Diagrams

Appendix 12-J Sample Instrumenta)on Details

Appendix 12-K Sample Work Ac)vity Registra)on Form (WARF)

Appendix 12-L Alarm Management Philosophy and Priori)za)on viii

ABBREVIATIONS & ACRONYMS

°C degrees Celsius

°F degrees Fahrenheit μm micrometer

A Ampere

AC alterna)ng current

AC-DC alterna)ng current-direct current

ACL access control list

AES Advanced Encryp)on Standard

AI/AO Analog Input/Analog Output

ANSI American Na)onal Standards Institute

AOI Add-On Instructions

AV Antivirus

AWG American Wire Gauge

AWIA America’s Water Infrastructure Act of 2018

BCC Back-up Control Center

BEMS Business Enterprise Management Systems

BGP Border Gateway Protocol

BODR Basis of Design Report

BOYD Bring Your Own Device

BVD Bi-Directional Forwarding Detection

CAD Computer Aided Design

CCTV Closed Circuit Television cd/m² candelas per square meter

CI Cri)cal Infrastructure

CIP Common Industrial Protocol

CIS Center For Internet Security

CISO Chief Informa)on Security Officer

COTS Commercial-off-the-shelf

CPU Central processing unit

CS Construc)on Standard ix

CSF Cybersecurity Framework

CSI Construc)on Specifica)on Institute

CSMA/CD Carrier Sense Mul)ple Access / Collision Detec)on DA Deluxe Analog

DBA Database Administrator

DC Direct Current

DCOMM digital communication

DCS Distributed Control System

DD Deluxe Digital

DHCP Dynamic Host Configura)on Protocol

DHS Department of Homeland Security

DI/DO Digital Input/Digital Output

DIN Deutsches Ins)tut für Normung

DLR device-level ring

DMZ Demilitarized Zone

DNS Domain Name Servers

DoS Denial-of-Service

DP Deluxe Packed

DRP Disaster Recovery Plan

DVD digital versa)le disc

DVI digital video interface

DVMRP Distance Vector Mul)cast Rou)ng Protocol

DWSD Department of Water and Sewage

EIA Electronic Industries Alliance

EIGRP Enhanced IGRP

ELC Ethernet Link Controller

EMI Electromagnetic Interference

ENDA External Non-Disclosure Agreements

EOL End Of Life

EWS Engineering Workstation

FAT Factory Acceptance Test(ing) x

FBD Func)on Block Diagram

FDT Factory Demonstra)on Test(ing)

FI flow indicator

FIC flow indicator and controller

FO fiber optic

FPP Fiber Patch Panel

FT AssetCentre Factory Talk AssetCentre monitors your factory automa)on system and provides centralized tools to minimize down)me

FTSP FactoryTalk Services Platform

FX two strand op)c fibre

GB gigabyte

Gbps gigabytes per second

GFI Ground Fault Circuit

GHz gigahertz

GLWA Great Lakes Water Authority

GRE Generic Rou)ng Encapsulation

GRWIC Grid Router WAN Interface Cards

GUI Graphical User Interface

HARDW hardwired

HART Highway Addressable Remote Transducer

HDMI High-Defini)on Mul)media Interface

HMI Human Machine Interface

HPHMI High Performance Human-Machine Interface

HR Human Resource

HSR High Availability Seamless Redundancy

Hz hertz

I&C Instrumenta)on and Control

I/O input/output

IAB Integrated Architecture Builder

IACS Industrial Automa)on and Control Systems

ICS industrial control system

IDS Intrusion Detec)on System

IEC International Electrotechnical Commission

IEEE Ins)tute of Electrical and Electronics Engineers, Inc.

xi

IGMPv3 Mul)cast Internet Group Management Protocol inch

IP internet protocol

IPS Intrusion Protec)on System

IPSec Internet Protocol Security

IR Incident Response

IRT Incident Response Team

ISA Interna)onal Society of Automation

IS-IS Intermediate System-to-Intermediate System

ISO International Standardization Organization

IT Informa)on Technology kHz kilohertz km kilometer kVA kilovolt amperes kW kilowatt

LA Long Analog

LAN Local Area Network lbf spec 50

LC Lucent connector

LD Long Digital

LED Light EmiQng Diode

LI level indicator

LIC level indicator and controller

LP Long Packed mA DC millamps direct current

MA RELAY maintained ac)on of the contact mA milliampere

MB megabyte

Mbps megabytes per second

MFA Multi-Factor Authentication mHz megahertz

MO RELAY momentary ac)on of the contact

MRP Media Redundancy Protocol ms millisecond xii

MSG Message Instruction

MT/s Mega Transfers per second

MTW machine tool wire

NAS Network ABached Storage

NEC Na)onal Electrical Code

NEMA Na)onal Electrical Manufacturers Association

NFPA Na)onal Fire Protec)on Association

NIC Network Interface Controller

NIST Na)onal Ins)tute of Standards and Technology nm Newton meter

NTS Note to Specifier

NTP Network Time Protocol

O&M opera)on and maintenance

OAD Operational Availability Demonstration

ODBC Open Database Connectivity

OIT Operator Interface Terminals

OOS Out of Service

OPC Open PlaRorms Communications

OPH Ova)on Process Historian

OS Opera)ng System

OSPF Open Shortest Path First

OT Opera)ons Technology

OTDR op)cal )me-domain reflectometer

P&ID Piping and Instrumenta)on Diagram

PAT Performance Acceptance Test

PC personal computer

PCAP packet capture

PCB ProSo5 Configura)on Builder

PCN Process Control Narrative

PcoIP PC over IP

PD Packed Digital

PDF portable document format

PDS ProSo5 Discovery Service xiii

PERA Purdue Enterprise Reference Architecture

PF power factor

PI pressure indicator

PID propor)onal, integral and deriva)ve [control]

PII Personal Iden)fiable Information

PIM SM Protocol Independent Mul)cast sparse mode (

PL Performance Level

PLC Programmable Logic Controller

POC Point Of Contact

PRP Parallel Redundancy Protocol

PS Pump Station

PSI pounds per square inch

PVC polyvinylchloride

QC quality control

QWERTY keyboard design for La)n-script alphabets

RAID Redundant Array of Inexpensive Disks

RAM Random-Access Memory

RDIMM registered memory is a type of memory chip

RDP Remote Desktop Protocols

REP resilient ethernet protocol

RFI Request for Interpretation

RIO Remote I/O

RJ registered jack

RMS Root-Mean-Squared

ROS Remote Operating Station

RSA Rivest–Shamir–Adleman encryption

RTU remote terminal unit

RU rack unit

SAT Site Acceptance Test(ing)

SATA Solid-State or Serial ATA

SCADA Supervisory Control & Data Acquisition

SCC System Control Center

SCRM Supply Chain Risk Management

SD secure digital xiv

SDMS SCADA Document Management System

SFP Small Form-Factor Pluggable

SHA Secure Hash Algorithm

SLA Service Level Agreement

SME Subject MaBer Expert

SNMP Simple Network Management Protocol

SOC Security Opera)ons Center

SPG single point ground

SSD Solid State Drive

SSH Secure Shell

SSL Secure Sockets Layer

SSM PIM Source-Specific Multicast

TB terabyte

TCP Transmission Control Protocol

TCP/IP Transmission Control Protocol/Internet Protocol

THD total harmonic distortion

TI temperature indicator

TIC temperature indicator and controller

UDP User Datagram Protocol

UL Underwriters Laboratories

UPS Uninterrup)ble Power Supply

USB universal serial bus

VAC volts alterna)ng current

VDC volts direct current

VLAN Virtual Local Area Network

VPN Virtual Private Network

W watt

WAN Wide Area Network

WARF Work Authoriza)on Request Form

Vrms Voltage, root mean square

WSMA Web Services Management Agent

WTP Water Treatment Plant

CS-12 SCADA STANDARD SPECIFICATIONS 1

1 PURPOSE & OVERVIEW

This document provides guidance to designers and includes por)ons of specifica)on language (“snippets”) specifically created for the Great Lakes Water Authority (GLWA) to standardize the design, installa)on, configura)on, and execu)on of Supervisory Control & Data Acquisi)on (SCADA) work for GLWA’s water treatment plants, elevated and ground storage tank hydraulics, water and collec)on distribu)on system pump sta)on processes and control philosophy in accordance with standard prac)ces of water projects. This includes specifica)ons for components, instruments, hardware, so5ware, and so5ware programming used for the design and implementa)on of SCADA systems and associated communica)on networks. The contents of this document also pertain to any expansion or upgrades performed on the exis)ng SCADA systems at the five GLWA water treatment plants. This document is intended for use by Design Engineers, in-house design engineers, and other en))es responsible for preparing changes or addi)ons to the SCADA system. This manual is not a biddable design specifica)on and should not be used as such.

Standardiza)on is a technique which has been used by industry for many years because it provides a number of benefits including improved buying power, increased quality, reduced spare parts inventory, simplified/reduced training requirements, streamlined troubleshoo)ng, and beBer overall performance because plant staff is more likely to understand the opera)on and maintenance requirements of the equipment they are working with. These guidelines, standards, and procedures have been developed in order to promote greater uniformity among the various design and construc)on projects prepared for GLWA.

Adoption of these standards and their supplication is the responsibility of each individual Design Engineer and should be reviewed early in any project efforts. As such, the Design Engineer should confirm with GLWA that the specifica)ons herein are those to be followed. Due to con)nuously evolving technologies and preferences, the items contained in the guidelines outlined in this sec)on should be reviewed early during each project to confirm the contents s)ll reflect the preferred choices and represent the latest models/technology

This document is a living manuscript, and the information contained within will be updated semiannually by GLWA.

1.1 Nomenclature and Tagging

Refer to Appendix 12-A, SCADA Nomenclature, and Tagging Guide.

1.2 Document Updates

This document and any revisions to it are managed wholly by the GLWA. The Design Engineer is responsible to coordinate with the GLWA to confirm the Design Engineer has the latest version available. Updates to this document may be made on an as-needed basis only on approval by the GLWA and updated by GLWA.

1.3 Integrator Qualifications

Any work that is to be performed on GLWA’s SCADA/Automa)on system is required to be by an en)ty mee)ng the

GLWA’s Integrator Qualifica)on requirements as detailed in this Sec)on. The Design Engineer is responsible for specifying Integrator qualifica)ons requirements in the design documents. The

CS-12 SCADA STANDARD SPECIFICATIONS 2

Design Engineer should carefully review and modify these Integrator qualifica)on requirements in associa)on with the project scope and in coordina)on with GLWA to assure GLWA receives the highest quality integra)on services.

1.3.1 Specification

Notes to the Design Engineer:

• The specifica)on provided below is the minimum requirement. The Design Engineer should add any addi)onal integrator qualifica)ons related to the project scope as required.

• Specifica)on ar)cle A.1.c is applicable to all projects with PLC controllers. The Design Engineer should modify this statement if necessary.

• Specifica)on ar)cle A.1.d iden)fies the project as a “bid” type. The Design Engineer should modify this statement if project is not a public bid.

• The Design Engineer should consider adding specific manufacturer training cer)fica)ons for SCADA and

Historian plaRorm so5ware and/or PLC, Ova)on and OIT, HMI so5ware programming and configura)on to integrator qualifica)ons.

• This specifica)on is wriBen for the qualifica)ons of the process control system integrator.

Specifica)on 1. Integrator Qualifications

X.X QUALITY ASSURANCE

A. Qualifications:

1. PROCESS CONTROL SYSTEM INTEGRATOR:

a. Shall be financially sound with at least eight years of con)nuous experience in designing, supplying, programming, implemen)ng, and suppor)ng SCADA systems for water treatment plants, and pump sta)ons comparable to the SCADA system specified for this Project, rela)ve to hardware, so5ware, cost, and complexity.

b. Shall have record of successful programming and integra)on projects. Upon OWNER’s request, submit record of experience for at least five projects, each with the following informa)on: project name, owner name and contact informa)on, name and contact informa)on for contractor, name and contact informa)on for engineer or architect, and contract value of process control systems Work for which INTEGRATOR was responsible.

[NTS: SELECT BETWEEN ARTICLES ‘C’ AND/OR ‘D’ AS PER THE CONTROLLER REQUIREMENTS FOR THE

PROJECT]

Specification

CS-12 SCADA STANDARD SPECIFICATIONS 3

c. Shall be regularly engaged in design and installa)on of similar system and subsystems in water

& wastewater industry, and shall meet the following qualifica)ons:

1) Presents proof of member status as a Rockwell Automa)on Solu)ons Partner, Level

Integrator including Process Program recogni)on, or a Rockwell Automa)on Recognized

System Integrator, level Integrator including Process Program recognition.

2) Assigns to this project personnel trained on general process instrumenta)on, along with the specific computers, controllers, and proposed so5ware. As it applies, their training program shall have been administered by the PLC controller manufacturer.

3) Provides references from projects specifically for FactoryTalk AssetCentre implementation.

4) Maintains a service facility with a staff capable of design, fabrica)on, installa)on, programming, and tes)ng the distributed control system and its components and has the capacity to respond to on-site issues.

d. Shall be regularly engaged in design and installa)on of similar system and subsystems in water industry, and shall meet the following qualifica)ons:

1) Presents proof of Emerson Ova)on DCS System Integration.

2) Assigns to this project personnel trained on general process instrumenta)on, along with the specific computers, controllers, and proposed so5ware. As it applies, their training program shall have been administered by the DCS manufacturer.

3) Provides references from projects specifically for complete Emerson Ova)on DCS.

4) Maintains a service facility with a staff capable of design, fabrica)on, installa)on, programming, and tes)ng the distributed control system and its components and has the capacity to respond to on-site issues.

e. Shall have at the )me of Bid experienced engineering and technical staff capable of designing, supplying, programming, configuring, implemen)ng, and suppor)ng the SCADA system and complying with submiBal and training requirements of the Contract Documents.

1) Staff assigned to this Project shall have completed manufacturer cer)fied training course for the specific HMI and Historian plaRorm so5ware required in this Contract.

2) Staff assigned to this Project shall have completed manufacturer cer)fied training course for the specific PLC and OIT hardware and so5ware required in this Contract.

3) Staff assigned to this Project shall have completed manufacturer cer)fied training course for the specific DCS system required in this Contract.

4) Upon OWNER’s request, submit training class cer)ficates of comple)on and resume of staff assigned to this Project.

d. Shall be capable of training opera)ons and maintenance personnel in SCADA system applica)ons, and in opera)ng, programming, and maintaining the SCADA system.

f. Supply and support system so5ware packages of fully developed and field-proven standardized designs that are not a highly unique, custom, or one-of-a-kind systems.

g. Shall have UL 508 approved panel shop or employ UL approval panel shop (excluded are Emerson Ovation

Cabinets from UL approved).

CS-12 SCADA STANDARD SPECIFICATIONS 4

h. Supply and support system hardware components and so5ware packages of fully developed and field-proven standardized designs that are not a highly unique, custom, or one-of-a-kind systems.

i. Possess a thorough, working knowledge of water treatment,, elevated and ground storage tank hydraulics, and water distribu)on and collec)on system pump sta)on processes and control philosophy in accordance with standard prac)ces of the water and wastewater industry.

j. Possess,maintain, and perform failure repor)ng, analysis, and correc)ons of a documented program failure.

End of Specification

CS-12 SCADA STANDARD SPECIFICATIONS 5

2 SCADA SOFTWARE MANAGEMENT PROCEDURES

2.1 Asset Management Software

Asset Management so5ware is used to monitor and manage all assets in the SCADA system. SCADA system assets include Programmable Logic Controllers (PLCs), Operator Interface Terminals (OITs), Ethernet Switches, SCADA

Clients, SCADA Servers, and Historians. Asset Management so5ware is standardized by GLWA. If a project requires any changes or updates to the Asset Management so5ware, the Design Engineer shall coordinate with the GLWA to identify Asset Management software manufacturer and version numbers necessary to maintain GLWA’s current programs and include these requirements in the project documents if relevant to the project scope.

If the project design includes hardware or so5ware addi)ons that will increase the asset quan)ty above the licensed amount, the Design Engineer should include a license upgrade to the exis)ng system in the project design.

2.1.1 Specification

• Most of the SCADA system so5ware used by GLWA at the water treatment plants (WTPs) are either managed using Emerson Ova)on Developer Studio or by the FactoryTalk AssetCentre.

Specifica)on 2. SCADA Change and Asset Management Procedure

X.X SCADA CHANGE AND ASSET MANAGEMENT PROCEDURE

A. General:

1. GLWA have a change and asset management process in place for the WTP SCADA system and for revision control of the WTP SCADA files (applica)on code, firmware, and OS/SCADA vendor software).

2. The Design Engineer shall meet all the requirements set in the GLWA change management process and shall coordinate with GLWA the effort to add addi)onal assets to the SCADA Asset Management system.

B. The change management process for modifica)on to a part of the control system shall mainly cons)tute of the following steps:

1. The Design Engineer reques)ng the change shall submit a Work Authoriza)on Request Form (WARF, refer to Sample 12-K to GLWA SCADA Automa)on Administrator.

2. The SCADA Automa)on Administrator shall review the WARF and either approve or reject the suggested change. If the SCADA Automa)on Administrator approves the changes then the latest version of the

So5ware Infrastructure to be changed shall be checked out to the person/organiza)on who submiBed the WARF. If the SCADA Automa)on Administrator rejects the proposed changes, the Design Engineer is required to modify the WARF for future reconsideration.

3. The GLWA SCADA Automa)on Administrator shall check out the latest version of the So5ware

Infrastructure to the person/organiza)on who submiBed the WARF. At this point, no changes should be

CS-12 SCADA STANDARD SPECIFICATIONS 6

made to this specific piece of so5ware unless there is an emergency situa)on where changes may be needed to protect the GLWA plant processes, equipment or personnel.

4. GLWA’s SCADA Automa)on Administrator shall put the following notes in the checkout documenta)on:

a. Person/Organiza)on so5ware infrastructure is checked out to and contact information.

b. Associated WARF Number

c. An)cipated Check-In Date

5. The Design Engineer (person/organiza)on) doing the work associated with the WARF and other Contract

Documents shall make the required modifica)on to the so5ware infrastructure. Once the modifica)on is complete and ready for installa)on onsite the person/organiza)on making the change shall no)fy

GLWA’s SCADA Automa)on Administrator to schedule the work onsite Control.

6. Control So5ware Infrastructure Verifica)on & Acceptance: A5er the so5ware infrastructure has been commissioned onsite the modifica)on shall be verified for proper opera)on by the verifica)on process outlined in the WARF and any other applicable documents (such as any contract drawings and specifica)ons). A5er the so5ware infrastructure modifica)on has been verified and accepted it shall be checked back into as a final change in the FT AssetCentre (or Emerson Ova)on System Database) and the final WARF form will be submiBed..

7. The final WARF form will include the revision number of the so5ware infrastructure, included with the following notes:

a. Person/Organiza)on who made the so5ware infrastructure modification.

b. Detailed Descrip)on of the modifica)ons made as part of this version. Including the purpose of change.

c. Associated WARF Number

C. Product and Manufacturer:

1. Not Applicable.

CS-12 SCADA STANDARD SPECIFICATIONS 7

2.2 SCADA So5ware Versions

GLWA has standardized on the specific SCADA so5ware and firmware versions shown in Table 1 below. All so5ware associated with configura)on and development of the various aspects of the SCADA system is required to match exis)ng GLWA so5ware manufacturers and versions. Use of firmware and so5ware version numbers not listed in the table shall not be allowed without wriBen approval from GLWA.

Upgrades to a so5ware version number shall not be allowed without wriBen approval from GLWA. Prior to a version upgrade, the Design Engineer is responsible for verifying exis)ng firmware and so5ware version numbers with GLWA and for coordina)ng with the so5ware manufacturer to confirm compa)bility of upgrades with

GLWA’s exis)ng systems. If GLWA approves a specific so5ware version upgrade, the Design Engineer shall include in the project scope of work the upgrade of all approved so5ware in the SCADA system to the new version in order to maintain consistency throughout the SCADA system.

Table 1 Firmware, So5ware, and Opera)ng System Version Table

ControlLogix 5570 Series 31.05 For redundant systems

ControlLogix 5580 Series 32.00.00 For non-redundant systems

CompactLogix 5380 Series 32.00.00

Logix Data Server FactoryTalk Linx 6.00

PanelView Plus 7 FactoryTalk View ME 11.00

Ova)on Model OCR3000 Ova)on 3.8

Servers OS Windows Server 2019

Worksta)ons OS Windows 10

SCADA Process Historian Emerson Ova)on Process

Historian 3.7.1

Enterprise Historian OSIso5 PI Historian

FactoryTalk AssetCentre 9.00

Antivirus

Report So5ware

Remote Alarm No)fica)on Software

CAD So5ware AutoCAD 2018, or latest version approved by GLWA

Centralized Deployment

Comments Version Product

CS-12 SCADA STANDARD SPECIFICATIONS 8

THIS PAGE INTENTIONALLY LEFT BLANK

CS-12 SCADA STANDARD SPECIFICATIONS 9

3 SCADA HARDWARE STANDARDS

3.1.1 Programmable Logic Controller (PLC) and Input and Output Modules

The SCADA system uses programmable logic controllers for process monitoring, control, and automa)on. The PLC consists of a chassis, power supply, processor, and various communication and input/output (I/O) modules. A chassis with all components except the processor referred to as a Remote I/O (RIO), may be used when physical layout warrants it or if the volume of I/O modules becomes too large for one panel.

Refer to Appendix 12-A, SCADA Nomenclature and Tagging Guide, for PLC Naming Convention.

3.1.1.1 Specification:

• The Design Engineer is responsible for selec)ng the appropriate PLC form factor as needed. Table 2 presents a summary of the criteria for selec)on:

Table 2 Designer Selec)on Guide for PLCs

Required for cri)cal processes

Form Factor

I/O Count User Memory

Requirements

Rungs of Logic

Addi)onal Considerations

Large Greater than 100

OR

Greater then 2 megabyte (MB OR)

Greater then 1000

OR

Required for cri)cal processes

Required for redundant processors

Mid 50 – 100

OR

1 MB – 2 MB

OR

100 – 1000

OR

Small Less than 50

OR

Less than 1 MB

OR

Less than 100

OR

Use when small I/O count and only monitoring is required

Specifica)on 3. Programmable Logic Controller (PLC) (Large Form Factor)

X.X PROGRAMMABLE LOGIC CONTROLLER (PLC) (LARGE FORM FACTOR)

1. The PLC shall be a modular type with discrete and analog I/O capabili)es, as well as Ethernet communications.

2. Remote input/output modules shall be provided as shown and specified.

3. Discrete input modules shall have 16 points per module and shall accept an input of 115 volts alterna)ng current (VAC), 60 hertz (Hz). They shall be isolated channel to channel. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

CS-12 SCADA STANDARD SPECIFICATIONS 10

4. Discrete output modules shall be relay type, have 16 points per module, and they shall have a current capacity of 2 A con)nuous per point at 115 VAC, 60 Hz. They shall be isolated channel to channel. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

5. Analog input modules shall have eight channels per module. They shall be isolated channel to channel and electrical current based (4-20 milliamperes [mA]). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

6. Analog output modules shall have eight channels per module. They shall be isolated channel to channel and electrical current based (4-20mA). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

7. Analog input modules with Highway Addressable Remote Transducer (HART) capability shall have eight channels per module. They shall be isolated channel to channel and electrical current based (4-20mA) with HART capability. A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

8. Each PLC system shall be configured to support the quan)ty of input/output signals required for the given control panel as specified in the Input-Output List and as shown. Spare I/O cards, which are provided to meet the required Spare I/O quan)ty iden)fied in the Input/Output List, shall be installed in the chassis and wired to field terminals. These spare I/O cards shall be provided in addi)on to the spare parts to be furnished in accordance with the Contract Documents.

9. Power supplies shall be adequately sized to accommodate the PLC’s en)re I/O capacity, including spares.

10. Provide isola)on transformers and other power normaliza)on devices to protect against over voltage and frequency distor)on characteris)cs where frequent power failures are common.

B. The PLC system shall have the following features and capabilities:

1. The unit shall use 4 to 20 mA DC analog signals and 120VAC discrete signals, unless otherwise specified.

2. The PLC system shall perform the following functions:

a. Accept analog input signals and discrete input signals ac)vated by contact closure to meet interface requirements.

b. Provide analog output signals and discrete output signals ac)vated by dry contact closure as required to meet interface requirements.

c. Communicate with devices over Ethernet/IP communica)on protocol to perform the func)ons shown and specified. Provide communica)on modules/ports of type and quan)ty as required.

d. Respond to interroga)ons for data and receive downloaded program changes and opera)ng parameter changes from operator or engineering worksta)on.

e. Errors and/or failures shall be indicated locally by Light EmiQng Diode (LED) and reported at the HMI. Mul)ple-bit errors shall cause immediate processor halt. Error diagnos)c tables shall be user accessible and provide clear and accurate descrip)ons of PLC system and process level errors.

CS-12 SCADA STANDARD SPECIFICATIONS 11

3. The processor shall be programmed using ladder logic, func)on block, sequen)al func)on chart, and structured text.

4. The process controller, in conjunc)on with I/O modules, shall perform all system level opera)ons, system and data table monitoring and maintenance, alarm detec)on, propor)onal, integral and deriva)ve (PID) control, user program execu)ons, network request and response handling.

5. The processor shall have the following features:

a. User Memory: 2 MB minimum.

b. Conformal Coating.

c. Built-in universal serial bus (USB) port for programming, configuration, firmware update, and on-line edits.

d. Nonvola)le memory storage.

6. The unit shall have a real-)me clock to provide )me reference for processor and system operations.

7. The unit shall have watchdog )mers for monitoring system so5ware opera)ons to detect hardware malfunc)on or a non-produc)ve loop (stall condi)on).

8. The processor shall perform basic arithme)c opera)ons using floa)ng-point data.

9. The CPU shall func)on as a stand-alone unit which performs all of the func)ons described herein completely independent from the func)oning of the Operator Interface, HMI or other central processing units (CPUs), (e.g., a failure of the Operator Interface, Worksta)ons or other CPU(s) shall not impact data acquisi)on, control, scaling, alarm checking, or communica)on func)ons of a given CPU).

10. Outputs shall have the capability of being "latched," so they are reten)ve through a power interruption.

C. Product and Manufacturer: Provide the following:

1. ControlLogix 5570 Series Controller as manufactured by Allen Bradley for redundant applications.

2. ControlLogix 5580 Series Controller as manufactured by Allen Bradley for non-redundant applications.

3. Copper Media Communica)on Module: 1756-EN2TR, as manufactured by Allen-Bradley.

4. Fiber Media Communica)on Module: 1756-EN2F, as manufactured by Allen-Bradley

CS-12 SCADA STANDARD SPECIFICATIONS 12

Specifica)on 4. Programmable Logic Controller (PLC) (Mid Form Factor)

X.X PROGRAMMABLE LOGIC CONTROLLER (PLC) (MID FORM FACTOR)

1. The PLC shall be a modular type with discrete and analog I/O capabili)es, as well as Ethernet communications.

2. Remote input/output modules shall be provided as shown and specified.

3. Discrete input modules shall have 16 points per module and shall accept an input of 115 VAC, 60 Hz. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

4. Discrete output modules shall have 16 points per module, and they shall have a current capacity of 2 A con)nuous per point at 115 VAC, 60 Hz. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

5. Analog input modules shall have eight channels per module. They shall be electrical current based (4-

20mA). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

6. Analog output modules shall have eight channels per module. They shall be electrical current based

(4-20mA). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

7. Each PLC system shall be configured to support the quan)ty of input/output signals required for the given control panel as specified in the Input-Output List and as shown. Spare I/O cards, which are provided to meet the required Spare I/O quan)ty iden)fied in the Input/Output List, shall be installed in the chassis and wired to field terminals. These spare I/O cards shall be provided in addi)on to the spare parts to be furnished in accordance with the Contract

Documents.

8. Power supplies shall be adequately sized to accommodate the PLC’s en)re I/O capacity, including spares.

9. Provide isola)on transformers and other power normaliza)on devices to protect against over voltage and frequency distor)on characteris)cs where frequent power failures are common.

B. The PLC system shall have the following features and capabilities:

1. The unit shall use 4 to 20 mA DC analog signals and 120VAC discrete signals, unless otherwise specified.

2. The PLC system shall perform the following functions:

a. Accept analog input signals and discrete input signals ac)vated by contact closure to meet interface requirements.

b. Provide analog output signals and discrete output signals ac)vated by dry contact closure as required to meet interface requirements.

CS-12 SCADA STANDARD SPECIFICATIONS 13

c. Communicate with devices over Ethernet/IP communica)on protocol to perform the func)ons shown and specified. Provide communica)on modules/ports of type and quan)ty as required.

d. Respond to interroga)ons for data and receive downloaded program changes and opera)ng parameter changes from operator or engineering worksta)on.

e. Errors and/or failures shall be indicated locally by Light EmiQng Diode (LED) and reported at the

HMI. Mul)ple-bit errors shall cause immediate processor halt. Error diagnos)c tables shall be user accessible and provide clear and accurate descrip)ons of PLC system and process level errors.

3. The processor shall be programmed using ladder logic, func)on block, sequen)al func)on chart, and structured text.

4. The process controller, in conjunc)on with I/O modules, shall perform all system level opera)ons, system and data table monitoring and maintenance, alarm detec)on, PID control, user program execu)ons, network request and response handling.

5. The processor shall have the following features:

a. User Memory: 1 MB minimum.

b. Conformal Coating.

c. Built-in USB port for programming, configura)on, firmware update, and on-line edits.

d. Nonvola)le memory storage.

6. The unit shall have a real-time clock to provide time reference for processor and system operations.

7. The unit shall have watchdog )mers for monitoring system so5ware opera)ons to detect hardware malfunc)on or a non-produc)ve loop (stall condi)on).

8. The processor shall perform basic arithme)c opera)ons using floa)ng-point data.

9. The CPU shall func)on as a stand-alone unit which performs all of the func)ons described herein completely independent from the func)oning of the Operator Interface, HMI or other CPUs, (e.g., a failure of the Operator Interface, Worksta)ons or other CPU(s) shall not impact data acquisi)on, control, scaling, alarm checking, or communica)on func)ons of a given CPU).

10. Outputs shall have the capability of being "latched," so they are reten)ve through a power interruption.

C. Product and Manufacturer: Provide the following:

1. CompactLogix 5380 Series Controller as manufactured by Allen Bradley.

2. Communica)on Module: 5069-AEN2TR, as manufactured by Allen-Bradley.

CS-12 SCADA STANDARD SPECIFICATIONS 14

Specifica)on 5. Programmable Logic Controller (PLC) (Small Form Factor)

X.X PROGRAMMABLE LOGIC CONTROLLER (PLC) (SMALL FORM FACTOR)

1. The PLC shall be a modular type with discrete and analog I/O capabili)es, as well as Ethernet communications.

2. Remote input/output modules shall be provided as shown and specified.

3. Discrete input modules shall have 16 points per module and shall accept an input of 115 VAC, 60 Hz. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

4. Discrete output modules shall have 16 points per module, and they shall have a current capacity of 2 A con)nuous per point at 115 VAC, 60 Hz. A maximum of 12 points per module shall be used for a given project. A minimum of four points shall remain available to GLWA for future use. If a module requiring a voltage other than 115 VAC must be used, interposing relays shall be provided.

5. Analog input modules shall have eight channels per module. They shall be electrical current based (4-

20mA). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

6. Analog output modules shall have eight channels per module. They shall be electrical current based

(4-20mA). A maximum of 6 channels per module shall be used for a given project. A minimum of two channels shall remain available to GLWA for future use.

7. Each PLC system shall be configured to support the quan)ty of input/output signals required for the given control panel as specified in the Input-Output List and as shown. Spare I/O cards, which are provided to meet the required Spare I/O quan)ty iden)fied in the Input/Output List, shall be installed in the chassis and wired to field terminals. These spare I/O cards shall be provided in addi)on to the spare parts to be furnished in accordance with the Contract Documents.

8. Power supplies shall be adequately sized to accommodate the PLC’s en)re I/O capacity, including spares.

9. Provide isola)on transformers and other power normaliza)on devices to protect against over voltage and frequency distor)on characteris)cs where frequent power failures are common.

B. The PLC system shall have the following features and capabilities:

1. The unit shall use 4 to 20 mA DC analog signals and 120VAC discrete signals, unless otherwise specified.

2. The PLC system shall perform the following functions:

a. Accept analog input signals and discrete input signals ac)vated by contact closure to meet interface requirements.

b. Provide analog output signals and discrete output signals ac)vated by dry contact closure as required to meet interface requirements.

c. Communicate with devices over Ethernet/IP communica)on protocol to perform the func)ons shown and specified. Provide communica)on modules/ports of type and quan)ty as required.

CS-12 SCADA STANDARD SPECIFICATIONS 15

d. Respond to interroga)ons for data and receive downloaded program changes and opera)ng parameter changes from operator or engineering worksta)on.

e. Errors and/or failures shall be indicated locally by Light EmiQng Diode (LED) and reported at the

HMI. Mul)ple-bit errors shall cause immediate processor halt. Error diagnos)c tables shall be user accessible and provide clear and accurate descrip)ons of PLC system and process level errors.

3. The processor shall be programmed using ladder logic, func)on block, sequen)al func)on chart, and structured text.

4. The process controller, in conjunc)on with I/O modules, shall perform all system level opera)ons, system and data table monitoring and maintenance, alarm detec)on, PID control, user program execu)ons, network request and response handling.

5. The processor shall have the following features:

a. User Memory: 0.6 MB minimum.

b. Conformal Coating.

c. Built-in USB port for programming, configura)on, firmware update, and on-line edits.

d. Nonvola)le memory storage.

6. The unit shall have a real-)me clock to provide )me reference for processor and system operations.

7. The unit shall have watchdog )mers for monitoring system so5ware opera)ons to detect hardware malfunc)on or a non-produc)ve loop (stall condi)on).

8. The processor shall perform basic arithmetic operations using floating-point data.

9. The CPU shall function as a stand-alone unit which performs all of the functions described herein completely independent from the functioning of the Operator Interface, HMI or other CPUs, (e.g., a failure of the Operator Interface, Workstations or other CPU(s) shall not impact data acquisition, control, scaling, alarm checking, or communication functions of a given CPU).

10. Outputs shall have the capability of being "latched," so they are reten)ve through a power interruption.

C. Product and Manufacturer: Provide the following:

1. CompactLogix 5380 Series Controller, Model 5069-L306ER, as manufactured by Allen Bradley.

2. Communica)on Module: 5069-AEN2TR, as manufactured by Allen-Bradley.

3.1.2 PLC Communica)on Hardware

3.1.2.1 Ethernet / IP Taps

Ethernet / internet protocol (IP) Taps provide a high-performance network solu)on with full support for device-level ring (DLR) topologies using Ethernet/IP protocol. Use these taps reduces overall cost and simplifies networks by replacing unmanaged network switches. The Design Engineer is recommended to use these Ethernet/IP Taps when applicable in the project design.

3.1.2.1.1 Specification:

CS-12 SCADA STANDARD SPECIFICATIONS 16

• When a fiber/ethernet communica)on network that is specific to a process area and configured in a ring topology, the Design Engineer shall use Ethernet/IP Taps generally known as E-Taps. The Design Engineer is responsible for coordina)ng and specifying the configura)on of E-Taps (fiber to fiber, fiber to ethernet, ethernet to ethernet, etc.).

• The GLWA has standardized on using one type of fiber-op)c cable connector, type Lucent connector (LC), for the SCADA networks. The fiber-op)c cable connector type is part of the fiber-op)c cable specification. If design constraints force the use of a different type connector other than LC, using other type connector(s) is described in this document in Sec)on 9.2, Cable and Wiring. Update reference in specifica)on ar)cle below denoted as “NTS” to reflect loca)on in actual design document.

Specifica)on 6. Ethernet / IP Taps

X.X ETHERNET / IP TAPS

1. Ethernet / IP Taps shall be provided at loca)ons shown and specified to create a ring communica)on network for PLCs or remote I/Os.

2. Provide hardware quan)ty required to meet func)onal requirements of system as shown and specified.

B. Features:

1. Ports:

a. One (1) Copper port. [NTS: MODIFY QUANTITY AS REQUIRED]

b. Two (2) fiber ports. [NTS: MODIFY QUANTITY AS REQUIRED]

2. Fiber Port features:

a. Type: 100Base-FX (type of two strand fiber).

b. Accepts 62.5 / 125 micrometer (μm) and 50 /125 μm mul)mode fiber.

c. Wavelength: 1310 Nanometers (nm) no cap

d. Connector type: LC

3. Power Supply: 24VDC (volts direct current)

4. Current Consump)on: 260 mA at 24VDC.

5. Ambient Conditions:

a. Temperature of opera)on: -13°F to +140°F (degrees Fahrenheit)

b. Humidity: 5% to 95 % Noncondensing

6. Hardware shall comply with the following:

a. IEEE 802.3u.

b. UL Listed

7. Hardware shall be compa)ble with PLC hardware provided.

C. Product and Manufacturer: Provide the following:

1. 1783-ETAP2F, as manufactured by Allen-Bradley.

CS-12 SCADA STANDARD SPECIFICATIONS 17

3.1.2.2 Modbus Gateway (PLC)

The Modbus Gateway is an in-chassis communica)on gateway which allows PLC controllers to communicate with Modbus end devices. The gateway supports both Master and Slave func)ons with easy-to-use configura)on and management func)onality. The Design Engineer is recommended to use these Modbus

Gateways when applicable in the project design.

3.1.2.2.1 Specification:

• Modbus gateways are recommended for communica)on between PLCs and instruments that do not offer

HART protocol. Where possible, the Ethernet based Modbus Transmission Control Protocol/Internet

Protocol (TCP/IP) shall be provided as the preferred communica)on link. If not available, Modbus serial shall be used. Where HART protocol is available, provide HART capable analog input modules as specified elsewhere in this standard.

Specifica)on 7. Modbus Gateway (PLC)

X.X MODBUS GATEWAY (PLC)

1. Provide a single-slot gateway suppor)ng Modbus TCP and/or Modbus remote terminal unit (RTU) as needed.

2. Gateway shall provide status informa)on, accessible through the controller tags.

3. Gateway shall have ability to read data at both bit-level or register-level.

B. Features:

1. Supports both client (Master) and server (Slave) capabilities.

a. Client: Transmits Modbus Func)on Codes 1, 2, 3, 4, 5, 6, 7, 15, and 16

b. Server: Accepts Modbus Func)on Codes 1, 2, 3, 4, 5, 6, 8, 15, 16, 17, 22 and 23

2. User-definable module data memory mapping of up to 10,000 16-bit registers.

3. Uses Add-On Instruc)ons (AOI) for data transfer between module and processor.

4. Supports ProSo5 Configura)on Builder (PCB) and Discovery Service (PDS) software.

5. Local LED display on module for status and diagnos)cs information.

6. Supports nonvola)le flash memory to store configura)on for easy disaster recovery option.

7. Supports CIPconnect-enabled network configura)on and diagnos)cs monitoring.

CS-12 SCADA STANDARD SPECIFICATIONS 18

3.1.3 Operator Interface Terminal (OIT) or Remote Operator Station (ROS)

The installa)on of a touch screen Operator Interface Terminal (OIT) or an Ova)on Remote Operator Sta)on (ROS) needs to be preferred, based on the design of the overall control systems network architecture. A OIT will mostly be used for local control panels containing a PLC this will allow for graphical monitoring and control of the connected equipment. For example, OITs are recommended when local controls are desired or required for a given process, but not needed for applica)ons that require monitoring only as monitored data will already report back to the Plants Overall Ova)on system. ROS can be installed in PLC panels when mul)ple 3rd party equipment is installed in the local panel or area and is communicated back to the Plants Overall Ova)on system via a 3rd party network switch. The Designer or Consultant shall ul)mately be responsible for coordina)ng with GLWA for approval to determine whether an OIT or ROS is required for a given PLC panel.

Refer to…