City of Crescent City, CA SCADA Standards Version 1.1 ...crescentcity.org/docs/rfp/P17270_Crescent City SCADA Standards-v… · operation, some displayed variables will not normally

City of Crescent City, CA

SCADA Standards

Version 1.1

December 2017

Westin Technology Solutions, LLC | we-inc.com | p. 414.289.7960

CITY OF CRESCENT CITY SCADA STANDARDS | DECEMBER 2017

Asset Data Standards Document 2 Westin Technology Solutions, LLC | we-inc.com | p. 414.289.7960

916.889.8600

Table of Contents

1.0 Introduction.................................................................................................................................... 1

1.1 Purpose of SCADA Design Standards ..................................................................................................................1

1.2 Referenced Industry Standards ..............................................................................................................................1

1.3 List of Abbreviations and Acronyms .................................................................................................................... 2

1.4 Tag and I/O Requirements ..................................................................................................................................... 3

1.4.1 Tag Numbering ............................................................................................................................................... 3

1.4.2 General Functionality ..................................................................................................................................... 4

2.0 Hardware and Integration .......................................................................................................... 5

2.1 General Requirements ............................................................................................................................................. 5

2.2 Panel Construction ................................................................................................................................................... 5

2.3 Instrumentation ......................................................................................................................................................... 8

3 Networks and Communications .............................................................................................. 10

3.1 General ...................................................................................................................................................................... 10

3.2 Network Hardware Components ......................................................................................................................... 11

3.3 Structured Cabling ................................................................................................................................................. 13

4 SCADA – PLC Hardware and Software .................................................................................. 17

4.1 General Requirements ........................................................................................................................................... 17

4.2 Hardware Requirements ....................................................................................................................................... 17

4.2.1 PLC – ControlLogix ....................................................................................................................................... 18

4.2.2 RTU – CompactLogix .................................................................................................................................... 19

4.2.3 Alternate RTU - MicroLogix - Replacement of Existing RTU ..............................................................20

4.2.4 RTU RIO - CompactLogix ........................................................................................................................... 21

4.2.5 Alternate RTU RIO – Point IO .....................................................................................................................22

4.3 Software Requirements .........................................................................................................................................23

4.4 Control Logic Requirements ................................................................................................................................23

5 SCADA - HMI Hardware and Software ................................................................................. 26

5.1 Introduction .............................................................................................................................................................26

5.2 Hardware Requirements .......................................................................................................................................26

5.3 Software Requirements .........................................................................................................................................29

5.4 Historian Requirements .........................................................................................................................................30

5.5 Application Security ...............................................................................................................................................30

5.6 Graphical Requirements ........................................................................................................................................ 31

5.6.1 General Screen Properties .......................................................................................................................... 31


Asset Data Standards Document 3 Westin Technology Solutions, LLC | we-inc.com | p. 414.289.7960

916.889.8600

5.6.2 Standard Colors and Text ...........................................................................................................................35

5.6.3 Standard Equipment Objects .....................................................................................................................38

5.6.4 Process and Control Displays .....................................................................................................................39

5.6.5 Popup Displays ..............................................................................................................................................39

5.6.6 Alarm Management .................................................................................................................................... 40

5.6.7 Data Log Models .......................................................................................................................................... 44

6 Submittals .................................................................................................................................... 44

6.1 General Requirements .......................................................................................................................................... 44

7 Testing Requirements ............................................................................................................... 44

7.1 General Requirements .......................................................................................................................................... 44

7.2 FAT - Factory Acceptance Test ........................................................................................................................... 46

7.3 ORT - Operational Readiness Test .................................................................................................................... 46

7.4 PAT - Performance Acceptance Test ................................................................................................................ 48

8 Training ........................................................................................................................................ 48

8.1 City’s Responsibility ............................................................................................................................................... 48

8.2 Contractor’s Responsibility .................................................................................................................................. 49

APPENDIX A – EXAMPLES of WWTP HMI SCREENS ..................................................................... 52

APPENDIX B – EXAMPLE POPUP SCREENS ..................................................................................... 59

APPENDIX C – MISCELLANEOUS SYMBOLS ................................................................................... 64

DOCUMENT REVISION HISTORY

Version Date Author Quality Control Description of Revisions

0.0 Norman

Anderson Draft Version

1.0 10/4/17 Bill

Wisnewski

Jason

Glaskin-Clay

Finalize Draft Version for

Review

1.1 12/1/17 Bill

Wisnewski

Jason

Glaskin-Clay Update based on Client Review

comments


Asset Data Standards Document 1 Westin Technology Solutions, LLC | we-inc.com | p. 414.289.7960 1

1.0 Introduction

1.1 Purpose of SCADA Design Standards

These standards provide minimum requirements for the design and construction of Crescent City (City) water

and wastewater SCADA projects. The purpose of this document is to establish conventions and standards

used in the selection of instrumentation, hardware, programming, and configuration of control systems to

ensure uniformity across all City SCADA systems. The City reserves the right to approve changes based on

site and project specific design requirements.

1.2 Referenced Industry Standards

Unless otherwise noted, the latest version of the following standards shall be used for the design and

construction of City SCADA systems:

1. Cisco/Rockwell Converged Plantwide Ethernet (CPwE) Design and Implementation Guide.

2. Institute of Electrical and Electronics Engineers (IEEE).

i. Standards as applicable for design and implementation.

3. International Society of Automation (ISA):

i. 5.1, Instrumentation Symbols and Identification.

ii. 5.4, Instrument Loop Diagrams.

iii. 18.2, Management of Alarm Systems for the Process Industries and related technical reports.

iv. 50.1, Compatibility of Analog Signals for Electronic Industrial Process Instruments.

v. 20.00.01, Specification Forms for Process Measurement and Control Instruments.

vi. IEC62443 (ISA-99), Industrial Automation and Control System Security.

vii. 101, Human-Machine Interfaces.

4. National Electrical Manufacturers Association (NEMA).

i. Standards as applicable for design and implementation.

5. National Fire Protection Association (NFPA):

i. 70 – National Electrical Code.

ii. 70E - Standard for Electrical Safety in the Workplace.

iii. 820 – Standard for Fire Protection in Wastewater Treatment and Collection Facilities.

6. National Institute of Standards and Technology:

i. SP-800 series.

7. Telecommunications Industry Association (TIA); Electronics Industry Association (EIA):

i. 492, Specifications for Optical Waveguide Fibers.

ii. 568, Commercial Building Telecommunications Cabling Standard.

iii. 569, Commercial Building Standards for Telecommunications Pathways and Spaces.

iv. 607, Commercial Building Grounding and Bonding Requirements for Telecommunications.

8. Underwriters Laboratory, Inc.

i. 508, Standards for Safety, Industrial Control Equipment.

ii. Component specific standards as applicable.



1.3 List of Abbreviations and Acronyms

AI/AO Analog Input/Analog Output

CAD Computer Aided Design

CCTV Closed Circuit Television

City City of Crescent City

CPU Central Processing Unit

DI/DO Digital Input/Digital Output

DIN Deutsche Institute fuer Normung

FDT Factory Demonstration Test

GUI Graphical User Interface

HMI Human-Machine Interface

I&C Instrumentation and Control

I/O Input/Output

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronics Engineers, Inc.

IP Internet Protocol

ISA Instrument Society of America

LAN Local Area Network

NFPA National Fire Protection Association

O&M Operations and Maintenance

OIT Operator Interface Terminal

OOS Out of Service

P&ID Piping and Instrumentation Diagram

PAT Performance Acceptance Test

PCN Process Control Narrative

PLC Programmable Logic Controller

RTU Remote Terminal Unit

SCADA Supervisory Control and Data Acquisition

VPN Virtual Private Network

WAN Wide Area Network



1.4 Tag and I/O Requirements

General: Data tags shall be used to provide numerical values, discrete status indications, and text strings for

display, and command functions within the SCADA graphics. Tag data configured within the internal tag

database can be mapped to tags within the PLCs, or configured as internal tags. Internal tags are tags whose

data value is stored in the tag database and not linked to external devices.

1.4.1 Tag Numbering

SCADA tag numbering shall be as follows for design and implementation for either analog or digital

functions:

FAC_TAG_UPXX_BFN

e.g., RTU1_FIT2601_AH

FAC Facility or Equipment Identifier (8 characters/digits max): Obtain facility identifier

from the City for each facility.

TAG Instrument Tag (4 characters max): This is the instrument or control loop tag as

indicated on the P&IDs or Field Tag. Follow ISA designation from Table 1 in ISA

Standard 5.1.

UP Unit Process Designator (2 digits max): The SCADA process data shall be organized

by unit process (UP). For process numbers not identified by the Engineer, an approved

Unit Process Number shall be obtained from the City.

XX Loop Number (2 digits max): This is the loop number indicated on the P&IDs and

field device tag.

BFN Block function or Clarifying Abbreviation (4 characters max): In some cases a block

function is required to further identify the block or I/O point, e.g. the tag for a pH

controller setpoint would be FAC_UP_TAG_X_Y_Z_PHSP

The following is a listing of example approved Block Function/Clarifying

Abbreviation examples and is not all inclusive. Obtain City approval for other

necessary descriptions:

A = Alarm Status. Followed by additional descriptor, e.g.,

H=High, L=Low as required.

CDTF = Current Day Total Flow

ET = Elapsed Time

ETR = Elapsed Time Reset

FA = Fault or Fail

FTC = Fail to Close

FTO = Fail to Open

FTR = Fail to Run

FTS = Fail to Stop

LEAD = Lead operation

MCL = Manual Close

MOP = Manual Open

MSSP = Manual Speed Set Point

MRUN= Manual Run



MSTP = Manual Stop

OFS = Out of Service

OPND = Opened

OVL = Overload

PH = pH

PHSP = pH Set Point

RST = Reset

S = Speed

SP = Set Point

Z = Position

ZSP = Position Set Point

1.4.2 General Functionality

A. All signals connected to PLC I/O modules shall be transmitted to the local server and operator

interfaces via Ethernet connection. Display variables on appropriate HMI displays. Display

status for discrete variables such as ON/OFF/FAIL status for motors and OPEN/CLOSE/FAIL

status for valves. Display value, and totalizer value when appropriate, for analog variables such

as process variables, Set points, drive speeds, and valve positions. To prevent clutter and to ease

operation, some displayed variables will not normally appear on displays but will be accessible

through easily identifiable point-and-click targets. Runtime and totalizer counters are an

example of variables that might not normally appear and displayed on appropriate graphic

screens and operator interfaces. Display shall be in engineering units. High and low alarms for

analog signals shall be displayed on the appropriate graphic screens. In general, all analog

process variables shall be trended. Specific analog signals shall also be transmitter to the local

digital chart recorder for secondary display and logging.

B. All alarms shall be displayed with time and date stamp and logged in the historian.

C. At intervals appropriate for the variable being trended, place the current value of analog

variable, along with a time and date stamp, into a historical trend file for that variable. Display

the trend on selectable HMI screens with appropriate scaling and units.

D. All pumps, trains, blowers, and miscellaneous equipment RUN times shall be calculated and

updated in the PLC system and transmitted to local and remote operator interfaces.

E. All timer settings, set points, and miscellaneous adjustments will be determined during

application software development or plant startup. All settings and adjustments shall be easily

made through the local or remote operator interface.

F. Provide bumpless PID control for all Manual to Auto and Auto to Manual transitions as follows:

i. Manual to Auto

1. Maintain current operating status on transition. If Auto mode calls device to stop

then stop or maintain stop and if Auto mode calls device to run then run or maintain

run.

2. For modulating devices, maintain the last control variable output. Allow automatic

control to commence from the last manual value.

ii. Auto to Manual

1. Maintain last operational status from Auto. If running then maintain running and

if stopped them maintain stopped.

2. Maintain last control variable output for modulating and adjustable variable

devices.



G. Provide nuisance alarm suppression by conditioning alarm signals. For example, disable all but

selected alarms when power is off, and include startup delays, momentary excursion delays, and

contact bounce delays. Suppress dysfunctional alarms during and immediately following power

outages. Suppress alarms such as low flow or low pressure in situations when equipment is

turned off or not running. Suppress alarms when operational set points or controller outputs are

below low flow alarms.

H. Coordinate critical alarms requiring remote notification with the City during construction.

Configure remote notification software to notify City personnel of critical alarms. Coordinate

contact information and alarm message with City during construction.

I. It is the responsibility of the design engineer or integrator to determine additional monitoring

and control functions required to support specific Facility processes for a given project.

2.0 Hardware and Integration

2.1 General Requirements

A. Provide equipment compatible with the City’s existing SCADA system to ensure proper

communications and data transfer. Components listed in this section are based on the latest

manufacturer’s models and specifications at the time the standard was developed. Provide the

manufacturer’s equivalent state of the art model at the time of construction for each item specified.

B. Use products of a single manufacturer of the same series device to achieve standardization.

C. Provide nameplates and service legends for all panels and components and provide stainless steel

tags for all field devices.

D. All components used shall be UL listed or recognized for their intended use and bear the appropriate

UL mark.

E. Number and tag each wire with machine printed heat shrink wire tags. Numbers shall match panel

drawings and include field device tag number where applicable.

F. Grounding:

1. Ground all devices and instrumentation in accordance with manufacturer’s instructions, the

National Electrical Code, and IEEE 142-2007 Recommended Practice for Grounding of

Industrial and Commercial Power Systems.

2. Furnish separate copper bus bars for signal and shield ground connections.

3. Furnish and install door grounding kit for enclosures.

4. Ground all DIN Rail.

5. Ground surge suppressors with the shortest possible ground conductor length.

6. Ground bus bars at a single ground point.

7. All grounding systems shall be tested by the 3-point fall of potential test in accordance with

ANSI/IEEE Standard 81, or approved equivalent testing, and documented. Documentation

shall include all test apparatus information and provide results in both tabular and graphical

formats.

2.2 Panel Construction

A. Design and Fabricate all control panels in accordance with UL 508A. All panels shall bear the

UL listing mark for enclosures stating, “Listed Enclosed Industrial Control Panel” per UL 508A.

B. Assemble and test all control panels at the factory. Notify City of factory testing a minimum of

4 weeks in advance to allow the City the opportunity to witness testing.



C. All wiring in panels shall be in duct type wireway or a flexible protective sleeve where wireway

is not practical. All wire shall be terminated to a terminal block. The use of wire nuts or similar

connections are prohibited.

D. All panel components shall be rated for the maximum and minimum expected temperature of

the control enclosure. Provide calculations showing that all components meet the maximum

expected control panel temperature including solar heat gains. Appropriate cooling and heating

methods shall be provided as required.

E. All outdoor panels shall be NEMA 4X white painted 304 Stainless Steel. All indoor panels

shall be NEMA 4X 304 Stainless Steel for process areas or NEMA 12 painted steel for non-

process areas. All panels shall be provided with the appropriate quantity of corrosion-inhibiting

vapor capsules.

F. Lighting: Door switched LED lighting with protective lighting cover, 120Vac.

G. Receptacles: Duplex DIN Rail mounted type manufactured by Allen-Bradley, Weidmuller, or

Phoenix Contact.

H. All enclosures shall be equipped with Lockable 3-point latching system that maintains enclosure

NEMA rating without the use of clamps.

I. Enclosure manufacturers:

a. Hoffman

b. Rittal

c. Hammond

d. Approved Equal

J. Control Panel General Equipment; select all exact component types as required for the

application:

a. Circuit Breakers:

i. UL 489 Listed.

ii. DIN Rail Mounting.

iii. Manufacturers:

1. Allen-Bradley; 1489-A series

2. Schneider Electric/Square D; Multi 9 Series

3. Phoenix Contact

4. Weidmuller

5. Approved Equal

b. Terminal Block:

i. Screw Compression Clamp.

ii. Single level

iii. Provide 20 percent spare installed terminal block

iv. Rated for minus 55 to 110 degree C

v. DIN Rail Mounting

vi. Label all terminal block with appropriate numbers

vii. Rated 600Vac

viii. Manufacturers:

1. Allen-Bradley

2. Phoenix Contact

3. Entrelec

4. Schneider Electric/Square D

5. Approved Equal



c. Control Relays:

i. Plug-in socket type

ii. DIN Rail Mounted

iii. LED Indicator

iv. Push-to-test type

v. Rated for minus 25 to 40 degree C

vi. Provide hold-down clips

vii. Manufacturers:

1. Allen-Bradley

2. Turck

3. Phoenix Contact

4. Schneider Electric/Square D

5. Approved Equal

d. Enclosure Surge Suppression:

i. IP 20 DIN Rail Mounted

ii. Pluggable surge device with base socket

iii. Grounded via DIN Rail

iv. LED indication where available

v. UL 1449 Listed

vi. Provide surge suppression for:

1. Incoming power connections

2. Analog signal lines

3. Communication signal lines

vii. Manufacturers:

1. Phoenix Contact

2. Weidmuller

3. Emerson/Edco

4. Approved Equal

e. Outdoor Surge Suppression:

i. NEMA 4X Enclosure

ii. UL 1449 Listed

iii. LED Indication where available

iv. Provide surge suppression for all field 2, 3, and 4-wire instrumentation

v. Manufacturers:

1. Phoenix Contact

2. Weidmuller

3. Emerson/Edco

4. Approved Equal

f. Power Supplies:

i. IP20 DIN Rail Mounted.

ii. Provide separate power supplies to power panel components and field devices.

iii. UL 508 Listed

iv. Manufacturers:

1. Phoenix Contact

2. Allen-Bradley

3. Schneider-Electric

4. Sola/Hevi-Duty

5. Approved Equal



g. Uninterruptible Power Supply (UPS):

i. 24Vdc Input/Output UPS with separately mounted battery

ii. UL508 Listed

iii. Minimum Backup Runtime: 10 minutes, if site has backup generator

30 minutes, if no backup generator

iv. DIN Rail Mounted

v. Manufacturers:

1. PULS

2. Phoenix Contact

3. Weidmuller

4. Approved Equal

2.3 Instrumentation

The CONTRACTOR shall purchase and install instrumentation equipment as standardized below. The

equipment aligns with what the City currently utilizes. Exact models shall be determined during design:

a. Liquid Level

i. Pressure

1. Rosemount

2. Siemens

3. Foxboro

4. Approved Equal

ii. Radar

1. Vega

2. Siemens

3. Approved Equal

iii. Ultrasonic

1. Siemens SITRAN LU

2. Endress Hauser FMU95 S

3. Approved Equal

iv. Submersible

1. Endress and Hauser

2. Keller

3. Approved Equal

b. Pressure Indicating and Differential Transmitters

i. Rosemount

ii. Siemens

iii. Foxboro

iv. Approved Equal

c. Pressure Switches

i. Ashcroft B-Series

ii. Ametek

iii. Wika

iv. Approved Equal

d. Pressure Gauges

i. Ashcroft

ii. Ametek

iii. Wika

iv. Approved Equal



e. Flow Meters

i. Insertion electromagnetic flow meters are the preferred choice for clean low

turbidity water applications and clamp-on ultrasonic type are preferred for dirty

water applications where suitable. Full bore electromagnetic flow tubes shall be

used for all other applications including chemical feed lines.

ii. Electromagnetic

1. Foxboro

2. Siemens

3. ABB

4. Approved Equal

iii. Ultrasonic

1. GE AT868

2. Siemens

3. Approved Equal

iv. Insertion Electromagnetic

1. McCrommeter FPI

2. Approved Equal

f. Chemical Metering Pumps

i. Prominent

ii. Pulsatron

iii. Approved Equal

g. Chlorine Analyzers

i. Prominent

ii. Approved Equal

h. Hach Transmitters

i. Hach SC200 or SC1000 depending on number of elements

ii. Approved Equal

i. pH Element

i. Prominent – pH sensor

ii. Approved Equal

j. Dissolved Oxygen

i. Hach LDO

ii. Approved Equal

k. Oxidation Reduction Potential

i. Hach pHD – ORP sensor

ii. Approved Equal

l. Turbidity Sensor

i. Swann Analytical.

ii. Approved Equal

m. Motor Operated Valves

i. Beck Actuators

ii. Auma Actuators

iii. Approved Equal


Asset Data Standards Document 1

0

Westin Technology Solutions, LLC | we-inc.com | p. 414.289.7960 10

n. Total Suspended Solids (High and Low) and NTU

i. Hach Solitax

ii. Approved Equal

o. Sludge Blanket Monitor

i. Cerlic CAT microP

ii. Approved Equal

3 Networks and Communications

3.1 General

A. Digital communications between controllers, operator workstations, and smart field components

(such as intelligent MCCs, Remote IO (RIO), Generators, Automatic Transfer switches, and

packaged control systems) shall be via Ethernet. The Ethernet protocol utilized shall be

compatible with the facility PLC system without the need for converter modules or specialized

third-party communications equipment.

B. Design networks for fault tolerance and for management utilizing SNMP. All general in plant

networks shall be a Gigabit Ethernet fiber optic ring topology utilizing a proprietary ring

protocol or using RSTP with appropriate portfast port designations to allow for fast recovery

following a link failure. Configure all ports to match speed and negotiation of connected

equipment.

C. Design of network systems shall include IP address and VLAN assignments coordinated with

the City and existing City infrastructure. ACL rules and required TCP/IP ports shall be

determined to ensure proper communications and security between facilities.

D. Facilities shall communicate across the City’s Wide Area Network (WAN) via City radio

communications, Digital Cellular, or Metro-Ethernet connections. Coordinate required

communications for each specific site with the City.

E. Network components specified shall be based on the state of the art during design and

construction. Contractor shall provide the latest state of the art hardware available during the

submittal process, and shall upgrade features as necessary to meet functional requirements.

Network components listed outline the minimum requirements for each component.

F. Provide surge suppression for network connected equipment located in vulnerable locations

such as connections between buildings or near AC power lines. Provide adequate separation or

shielding between communications cabling and other types of cable systems that could interfere

with communications.

G. The following outlines the minimum requirements for facility network systems:

a. IP Address and VLAN assignment and configuration for all network connected

components.

b. Network switch, router, and firewall configuration for in-facility and City WAN

communications including VPNs and QoS.

c. Fault tolerant and high availability design and implementation.

d. Network management including incorporation into the City SCADA network

management software.

e. Undefined usage switch ports should be assigned to VLAN 666, which has no virtual

connectivity.



1


3.2 Network Hardware Components

Select network components to meet requirements of each facility for proper communications and security in

accordance with Industry Standards. The following lists an outline of general components to be used within

the SCADA system. Additional types of components may be required such as layer 3 switches and routers

and should be selected as required utilizing the current City’s IT department guidelines and

manufacturers similar to those listed below.

A. Industrial Network Media Converter:

a. Function: Convert fiber optic Ethernet signal 100BASE-FX to copper 10/100BASE

TX. Used to extend connections from a local managed switch where copper

connections are impractical.

b. Support Fiber Optic Type Specified

c. Fiber Optic Connector: SC or LC

d. Power: 24Vdc

e. IP 20 enclosure

f. Temperature rating: 0 to 60 degrees C

g. UL 508 Listed

h. DIN Rail mounted

i. Manufacturers:

1. N-Tron

2. Hirschmann


4. Approved Equal

B. Industrial Network Layer 2 Switch, Ethernet, DIN Rail:

a. Function: Network communications between PLCs, Ethernet connected field

components, and HMIs within a facility.

b. Minimum of 2 Gigabit SFP ports and 6 RJ-45 ports. Select SFP modules as required.

Provide ports as required including a minimum of 2 spare ports.

c. Support 10/100/1000 BASE-TX and Gigabit fiber Ethernet for backbone

communications.

d. Layer 2 software

e. Supports SNMP, IEEE 802.1D, IEEE 802.1Q, Multicast IGMP, IEEE 802.3x

f. Proprietary ring structure and RSTP capabilities

g. Power: 24Vdc.

h. IP 20 Enclosure

i. Temperature rating: 0 to 60 degrees C

j. UL 508 Listed

k. DIN Rail Mounted



2


l. Manufacturers:

1. N-Tron 700 Series

2. Hirschmann RS20 series


4. Approved Equal

C. Industrial Network Layer 2 Switch, Ethernet, Rackmount:

a. Function: Network communication backbone switch for process control located in 19-

inch rack used for process control communications within a facility.

b. Provide network switching for a minimum of 24 ports within a single chassis.

c. Minimum of 2 Gigabit SFP ports and 22 RJ-45 ports. Select SFP modules as required.


d. Support 10/100/1000 BASE-TX and Gigabit fiber Ethernet for backbone

communications.

e. Layer 2 software

f. Supports SNMP, IEEE 802.1D, IEEE 802.1Q, Multicast IGMP, IEEE 802.3x

g. Proprietary ring structure and RSTP capabilities

h. Power: 120Vac

i. IP 20 Enclosure

j. Temperature rating: 0 to 60 degrees C

k. UL 60950 Listed

l. 19-inch rack mounted

m. Manufacturers:

1. N-Tron 7000 Series

2. Hirschmann Mach 1000 series

3. Cisco IE 3010

4. Approved Equal

D. Workgroup Switch, Ethernet, Rackmount:

a. Function: Network communication switch for communications outside of the process

control system or between facilities.

b. Provide network switching for a minimum of 24 ports within a single chassis.

c. Minimum of 2 Gigabit SFP ports and 22 RJ-45 ports. Select SFP modules as required.


d. Support 10/100/1000 BASE-TX and Gigabit fiber Ethernet for backbone

communications

e. Layer 2 software

f. Supports SNMP, IEEE 802.1D, IEEE 802.1Q, Multicast IGMP, IEEE 802.3x

g. RSTP, Link Aggregation capabilities

h. Stackable

i. Power: 120Vac



3


j. IP 20 Enclosure

k. Temperature rating: 0 to 50 degrees C

l. UL 60950 Listed

m. 19-inch rack mounted

n. Manufacturers:

1. Cisco 2960 series

2. Dell

3. HP

4. Approved Equal

3.3 Structured Cabling

A. General:

Provide structured cabling system for each facility as required to support communications at the

facility. Structured cabling systems include all copper and fiber optic communications cabling

as well as network equipment enclosures, racks, and patching equipment.

B. Floor Mounted Rack Enclosures:

a. Racks Type: ANSI EIA 19-inch, 45U tall with required depth supported on both sides

by vertical wire management system. Securely anchor racks to the floor with

manufacturer’s anchor kit.

b. Material: Black powder coated Aluminum with steel EIA rails.

c. Doors: Front and back double hinged, lockable, vented door assemblies.

d. Cabling Sections: Aluminum rack cabling section, including formed assembly, lockable

cable rings and assembly hardware.

e. 19-inch EIA rack mountable shelves for supporting equipment as required.

f. Provide nameplate for each rack with appropriate name/tag number.

g. Provide air flow baffles between racks to increase air movement.

h. Provide cable management cage to accommodate front to back rack wiring. Provide

hooks and rings for cable management. Use Velcro cable ties to secure cables.

i. Provide vertical PDUs for racks to support all equipment plus spare.

j. Provide electrical surge protective devices and grounding for component protection.

k. Manufacturers:

i. APC

ii. Ortronics

iii. Hoffman

iv. Dell

v. Approved Equal

C. Wall Mounted Rack Enclosures:

a. Racks Type: ANSI EIA 19-inch, minimum 12U tall with overall height and depth as

required.

b. Material: Black powder coated Aluminum with steel EIA rails.



4


c. Doors: Four side access with solid front door. Double hinged to allow front and rear

access to equipment.

d. 120Vac fan assembly.

e. Cabling Sections: Aluminum rack cabling section, including formed assembly, lockable

cable rings and assembly hardware.

f. 19-inch EIA rack mountable shelves for supporting equipment as required.

g. Provide nameplate for each rack with appropriate name/tag number.

h. Provide cable management accessories. Use Velcro cable ties to secure cables.

i. Provide vertical PDUs for racks to support all equipment plus spare.

j. Provide electrical surge protective devices and grounding for component protection.

k. Manufacturers:

i. APC

ii. Ortronics

iii. Hoffman

iv. Approved Equal

D. Rack Mounted UPS Systems:

a. Function: Provides backup power and power regulation for rack-mounted server and

network components and peripherals.

b. Mounting: Suitable for 19-inch rack mounting or floor mounting required.

c. Size: As required for connected load, 1.5 kVA minimum. Coordinate feeder breaker

size with the City.

d. Backup:

i. Minimum 10 minutes at full load for facilities with a back-up generator.

ii. Minimum 30 minutes at full load for facilities with no back-up generator.

e. Warranty: 1 year

f. UL Listed

g. UPS Technology: Line Interactive

h. Surge Suppression: Manufacturer Standard

i. 1 RJ-45 Ethernet, monitoring. Integrate into the SCADA system

j. Software: Manufacturer standard software installed on servers and workstations to

provide “soft shutdown” of computer hardware

k. Provide power cables as required

l. Manufacturers:

i. APC

ii. Powerware

iii. Liebert

iv. Approved Equal

E. Category 6/5e Communication Cabling:

a. Provide CAT 6/5e cables for Ethernet communications as required. Provide with

appropriate RJ-45 connectors that securely mate into associated equipment and jacks.



5


b. Provide cables meeting flame propagation test requirements of UL 723.

c. Provide plenum/riser listed cables as required.

d. Provide cables in accordance with ANSI/TIA/EIA-568-B.2 6/5e and ETL verified.

e. Provide cables conforming to applicable UL/NEC ratings. CMR, CMX-Outdoor rated.

f. Shielding:

i. MCCs/VFDs or other high noise installations: Shielded.

ii. All other locations: Unshielded.

g. Sunlight and Oil Resistant PVC or PVDF outer jacket.

h. Insulation: FEP – Fluorinated Ethylene Propylene.

i. Maximum Operating Voltage: 300 or 600 Vrms as required by installation.

j. Manufacturer:

i. Belden DataTuff

ii. Approved equal

F. Fiber Optic Cabling:

a. Comply with TIA/EIA 568

b. Rating: UL Listed OFNR, minimum

c. Fiber:

i. Multimode: 50/125 micron, OM3, multimode. Laser optimized for gigabit

performance.

ii. Singlemode: 9/125 micron

d. Type:

i. Direct equipment connections: Breakout, tight-buffered.

ii. All other installations: Distribution, gel free, loose tube or tight-buffered.

e. Fiber Count

i. 4 fibers per breakout cable, minimum

ii. 12 fibers per distribution cable, minimum

f. All Dielectric Construction: No electrically conductive components in fiber optic cable

are allowed.

g. Helically Wound: Buffered fibers helically wound; approximately 5 turns per meter.

h. Distribution Strength Member: Fiberglass epoxy rod, aramid fiber, Kevlar.

i. Protective Covering:

i. UV, Water, and Fungus resistant

ii. PVC or Fluoropolymer

j. Continuous and free from holes, splices, blisters, and other imperfections.

k. Minimum Bend Radius:

i. Short term Under Tension: 20 times cable diameter

ii. Long term Without Tension: 15 times cable diameter

l. Manufacturer:

i. Corning

ii. Optical Cable Corporation

iii. Approved Equal



6


G. Fiber Optic Connectors:

a. Provide in accordance with requirements of TIA/EIA 568.

b. Pull Strength: 0.2 N minimum

c. Ferrule: Ceramic with factory-polished fiber stub

d. Durability: Sustain minimum 500 mating cycles without violating other requirements

e. Ferrules: Free floating low loss ceramic

f. Polarizing key on duplex connector systems

g. Attenuation: Maximum of 0.5 dB per connector pair

h. Connector Type: SC for multimode and LC for single mode or as required to match

component mating connector

i. Manufacturers:

i. Corning

ii. Ortronics

iii. Approved Equal

H. KVM Console:

a. Function: Provides local viewing and control of rack mounted servers.

b. Integrated rackmount Keyboard, LCD Monitor, and mouse.

c. Provide console KVM, installation kit, and required cables for a completely functional

console KVM system.

d. 19-inch rack mountable

e. 1 U mounting height

f. Display:

i. Wide Screen: 17-inch TFT LCD, 16:9, minimum

ii. Resolution: 1920 x 1080, minimum

iii. Support resolutions down to 640 x 480

iv. Contrast Ratio: 500:1 minimum

v. Brightness: 250 cd/m2

vi. Viewing Angle: 140 x 120 degrees (H x V)

vii. 16 million colors

g. Keyboard/Mouse:

i. Notebook type with number pad

ii. Touchpad mouse

h. Interfaces: 8 ports, minimum

i. Warranty: 3 years

j. Manufacturer:

i. StarTech

ii. Samsung

iii. Approved Equal



7


I. Cable Management:

a. Provide Cable management documentation for all telecommunications, fiber optic, data

communications, network and telephone circuits and components provided for each

facility. As a minimum include the following:

i. All Field cabling, and cable routing

ii. Fiber Optic Patch Panel Layouts

iii. All network connected devices

iv. All jacks and outlets

v. Develop a cable and fiber numbering system based on Facility and source and

destination. Use this numbering system and include detailed cable and

connection schedule.

4 SCADA – PLC Hardware and Software


A. Provide equipment similar to and compatible with the City’s existing WWTP SCADA system for

SCADA system standardization.

B. SCADA controls shall be integrated utilizing Rockwell FactoryTalk with the licenses for the latest

version supplied as part of the construction effort.

C. Rockwell FactoryTalk licenses must be provided with sufficient tags with at least 30% spare tags.

D. Coordinate all network addressing for components with the City.

E. Install server, historian, operator workstation and other SCADA software on separate virtual

machines to reduce hardware requirements, but maintaining a clean configuration for each server

and application to allow for simple migration, backup, and recovery.

4.2 Hardware Requirements

A. Provide equipment similar to and compatible with the City’s existing WWTP SCADA system to

ensure proper system standardization, communications, and data transfer.

B. Provide all PLC system components, end-caps, cables, and additional ancillary equipment required

for a completely functional PLC system.

C. PLC systems shall be based on the following family of products:

1. Process Control, Monitoring and Polling PLCs:

Allen-Bradley ControlLogix

2. Process Remote I/O:

Allen-Bradley ControlLogix without a CPU module

3. New RTU Systems:

Allen-Bradley CompactLogix

4. New RTU RIO Systems:

Allen-Bradley CompactLogix without a CPU module

5. Replacement RTU Systems:

Allen-Bradley CompactLogix or MicroLogix

6. Replacement RTU RIO Systems:



8


Allen-Bradley CompactLogix without a CPU module or Point IO

D. PLC I/O

1. Facilities shall be designed with decentralized I/O to limit long runs of buried copper cables.

Fiber optic Ethernet communications shall be used to extend communications to remote I/O

systems.

2. Provide each PLC with at least 20 percent with a minimum of 2 points of installed spare I/O

for each I/O type, including the necessary terminal blocks, interposing relays, and surge

protection. Pre-wire all I/O to enclosure terminal blocks for field wiring terminations.

Spare I/O is in addition to I/O provided for planned future additions.

3. Provide at least 20% with a minimum of 2 spare slots in each PLC chassis to accommodate

future I/O cards. If the number of spare slots required exceeds the PLC chassis capacity

then provide subpanel space and wireway to accommodate a future chassis. Provide empty

DIN rail space required to accommodate future terminal block to support the spare slots.

4. Use separate I/O modules for parallel controlled equipment such as multiple high service

pumps. Pumps should be split across multiple I/O cards such that the failure of a single I/O

card does not impact the operation of all pumps.

5. Provide interposing relays for all discrete outputs.

4.2.1 PLC – ControlLogix

Provide complete microprocessor-based programmable device plug-in power supply, communications, and

I/O modules for process control and monitoring. Provide all components as necessary for a complete system.

1. Chassis:

Type: Allen-Bradley ControlLogix series, 1756-A series

i. Number of Slots: Sufficient for the number of modules required, including spares,

plus the required number of empty slots. The minimum chassis size is 7 slots.

Provide RIO chassis as required.

ii. Provide covers for empty slots – 1756-N2

2. Power Supply Modules:

Type: Allen-Bradley ControlLogix series, 1756-PA72 or 1756-PA75

i. Input Voltage: 85- 265 Vac

ii. Quantity: One for each processor chassis and one for each expansion I/O chassis.

Include sufficient capacity to power future expansion of all spare (empty) chassis

slots.

3. Processor (CPU):

Module: Allen-Bradley ControlLogix 5570, 1756-L7 series

i. Supports 128,000 discrete and 4000 analog I/O.

ii. Supports up to 500 controller connections.

iii. USB communication port, minimum.

iv. Memory: As required for application, 2 MB minimum

v. Not required for remote I/O applications

4. Network Communications Modules:

Module: Allen-Bradley ControlLogix, 1756-EN2T

i. Ethernet and Fast Ethernet, 100 Mbps.

ii. RJ-45 copper Ethernet connection

iii. Supports 128 TCP connections

iv. USB communication port



9


5. Discrete Input, ac (DI):

Module: Allen-Bradley ControlLogix IO, 1756-IA16I

i. Voltage: 120Vac

ii. Points per Modules: 16, isolated

6. Discrete Output, ac (DO):

Module: Allen-Bradley ControlLogix IO, 1756-OA16I

i. Voltage: 120Vac

ii. Points per Module: 16, isolated

7. Analog Input (AI):

Module: Allen-Bradley ControlLogix IO, 1756-IF8

i. Signal: 4 to 20 mA at 24V dc

ii. Points per Module: 8, non-isolated, differential or single-ended

8. Analog Output (AO):

Module: Allen-Bradley ControlLogix IO, 1756-OF4


ii. Points per Module: 4, non-isolated, single-ended

4.2.2 RTU – CompactLogix

Provide complete microprocessor-based programmable device, power supply, communications, and

I/O modules for process control and monitoring that are DIN rail mountable. Provide all

components as necessary for a complete system.

1. Processor (CPU):

Module: Allen-Bradley CompactLogix 5370, 1769-L3 series

i. Supports up to 256 Ethernet/IP nodes and 120 TCP connections

ii. 2 Ethernet/IP ports, USB communication port, minimum

iii. Memory: As required for application, 1 MB minimum


Type: Allen-Bradley CompactLogix 5370, 1769-PA series

i. Input Voltage: 120/220 Vac

ii. Quantity: One for each processor chassis and one for each expansion I/O chassis


Module: Allen-Bradley Compact IO, 1769-IA16

i. Voltage: 120Vac

ii. Points per Modules: 16, non-isolated

or

Module: Allen-Bradley Compact IO, 1769-IA8I

i. Voltage: 120Vac



Module: Allen-Bradley Compact IO, 1769-OA16

i. Voltage: 100/240Vac

ii. Points per Module: 16, non-isolated

or

Module: Allen-Bradley Compact IO, 1769-OW8I

i. Voltage: Relay



0




Module: Allen-Bradley Compact IO, 1769-IF4I

i. Signal: 4 to 20 mA at 24V dc, also can be configured for voltage

ii. Points per Module: 4, isolated, differential or single-ended

or

Module: Allen-Bradley Compact IO, 1769-IF8




Module: Allen-Bradley Compact IO, 1769-OF4CI


ii. Points per Module: 4, non-isolated, differential

or

Module: Allen-Bradley Compact IO, 1769-OF8C



4.2.3 Alternate RTU - MicroLogix - Replacement of Existing RTU

This is an alternate option for RTU replacement, only if it fits into the space requirements of an existing RTU

enclosure and a CompactLogix L3 system will not. This can also be used as an upgrade for an existing

MicroLogix installation in the WWTP.

Provide complete microprocessor-based programmable device with power supply, communications, and I/O

for process control and monitoring that are DIN rail mountable. Provide all components as necessary for a

complete system.

1. Processor (CPU):

Controller: Allen-Bradley MicroLogix 1100, 1763-L16 series

Alternate Controller: Allen-Bradley MicroLogix 1400, 1766-L32 series


ii. Communication ports: Isolated combination RS-232/485 (Channel 0)

Ethernet port (Channel 1)


iv. Built-in Real-Time Clock

v. Input Voltage: 120/220 Vac

vi. MLx1100 IO points: 10 digital inputs

6 digital outputs

2 analog voltage inputs

maximum IO expansion 4 modules

vii. MLx1400 IO points: 20 digital inputs

12 digital outputs

4 analog voltage inputs

2 analog voltage outputs

maximum IO expansion 7 modules


Module: Allen-Bradley MicroLogix Expansion IO, 1762-IA8

i. Voltage: 120Vac



1



3. Discrete Output (DO):

Module: Allen-Bradley MicroLogix Expansion IO, 1769-OA8

i. Voltage: 120Vac


or

Module: Allen-Bradley MicroLogix Expansion IO, 1769-OW8

iii. Voltage: Relay

iv. Points per Module: 8, non-isolated


Module: Allen-Bradley MicroLogix Expansion IO, 1762-IF4




Module: Allen-Bradley MicroLogix Expansion IO, 1769-OF4



4.2.4 RTU RIO - CompactLogix

Provide complete IO extension banks with plug-in power supply, communications, and I/O modules for

process control and monitoring that are DIN rail mountable. Provide all components as necessary for a

complete system.

1. Communications:

Module: Allen-Bradley CompactLogix, 1769-AENT


ii. 2 Ethernet/IP ports, USB communication port, minimum



Type: Allen-Bradley CompactLogix 5370, 1769-PA series

i. Input Voltage: 120/220 Vac

ii. Quantity: One for each processor chassis and one for each expansion I/O chassis


Module: Allen-Bradley Compact IO, 1769-IA16

i. Voltage: 120Vac


or

Module: Allen-Bradley Compact IO, 1769-IA8I

i. Voltage: 120Vac




2



Module: Allen-Bradley Compact IO, 1769-OA16

i. Voltage: 100/240Vac


or

Module: Allen-Bradley Compact IO, 1769-OW8I

i. Voltage: Relay



Module: Allen-Bradley Compact IO, 1769-IF4I


ii. Points per Module: 4, isolated, differential or single-ended

or

Module: Allen-Bradley Compact IO, 1769-IF8




Module: Allen-Bradley Compact IO, 1769-OF4CI


ii. Points per Module: 4, non-isolated, differential

or

Module: Allen-Bradley Compact IO, 1769-OF8C



4.2.5 Alternate RTU RIO – Point IO

This is an alternate option for RTU RIO replacement, only if it fits into the space requirements of an existing

RTU enclosure and a CompactLogix system will not.

Provide complete microprocessor-based programmable device plug-in power supply, communications, and

I/O modules for process control and monitoring that are DIN rail mountable. Provide all components as

necessary for a complete system.

1. Adapter:

Type: Allen-Bradley Point IO, 1734-AENT

i. 1 Ethernet/IP port, minimum

ii. Input Voltage: 24 Vdc at 10 amps

iii. Expansion IO Capacity: 63 module maximum


Module: Allen-Bradley Point IO, 1734-IE8C

i. Mounting Base Assembly: 1743-TB (includes 1734-MB & 1734-RTB)

ii. Signal: 4 to 20 mA at 24V dc

iii. Points per Module: 8, non-isolated


Module: Allen-Bradley Point IO, 1734-OE4C

i. Mounting Base Assembly: 1743-TB (includes 1734-MB & 1734-RTB)

ii. Signal: 4 to 20 mA at 24V dc.

iii. Points per Module: 4, non-isolated.



3


4.3 Software Requirements

A. All PLC new installation system components requiring programming and configuration shall be

compatible with Rockwell RSLogix 5000 and Studio 5000 applications.

B. For existing PLC, RTU, or RIO replacement, in order to meet existing space restrictions, system

components requiring programming and configuration may be compatible with Rockwell RSLogix

500 applications as an alternate option, with City approval.

C. All programming and configuration shall be done in the RSLogix 500, RSLogix 5000 or Studio

5000 version and revision as specified by the City.

4.4 Control Logic Requirements

All control logic is performed within the PLC. Programs are organized in a logical manner and broken into

subroutines for greater organization and to aid in troubleshooting. General program organization will include

a MainRoutine which calls all associated subroutines for the application and controls the sequence of

execution.

The Standard Add-On Instructions (AOIs) utilized by the WWTP ControlLogix applications should be reused

in any new ControlLogix program development for the City.

Each of the WWTP Standard AOIs are identified with the following information:

• AOI Name

• AOI Description

• Functional description

• Current version information

• WWTP PLC where is has been used (in green as a reference to better understand its usage)



4


The following is a list of Standard AOIs utilized by the WWTP ControlLogix applications:

AFC - Adjustable Frequency Controller

Controls the start/stop and speed control of a VFD controlled device.

Monitors and controls device status’, interlocks, run time data (see ETM AOI)

and the delay setpoint, alarm state, acknowledgement, and inhibit functions

for the following alarms conditions – Drive fault, Out-of-Range Low

(OORLAlm), Out-of-Range High (OORHAlm), Maintenance Required

(MntAlm)

Version: Edited 8/13/2008 by NAPA/mscoggins

(ACP2001 – Influent Pumps, ACP4001, APC7001)

AnaAlm - Analog Alarm

Scales the raw analog input into engineering units and controls the setpoints,

alarm state, acknowledgement, and inhibit functions for the following alarm

conditions - Hi-High (HHAlm), High (HAlm), Low (LAlm), Lo-Low

(LLAlm), Out-of-Range Low (OORLAlm), Out-of-Range High (OORHAlm),

and Rate-of-Change (ROCAlm)


(ACP2001, ACP4001, APC7001)

DigAlm - Digital Alarm

Controls the delay setpoint, alarm state, acknowledgement, and inhibit

functions for a discrete input alarm signal.

Version: Edited 8/13/2007 by NAPA/ZMAO

(ACP2001, ACP4001, APC7001, APC7201)

ETM - Equipment Elapsed Time/Runtime

Monitors device run status to calculate and store the following values – Total,

Last Total, Non-resettable Total, Day Total, Last Day Total, Start Total, Last

Start Total, Non-resettable Start Total, Day Start Total, Last Day Start Total,

and Maintenance Hour setpoint.


(ACP2001, ACP4001, APC7001, APC7201)

GateEMTT - EMTT Gate HOR Control

Monitors and controls the open/close functions via analog valve position

inputs and outputs, interlocks, HOR mode, Out-of-Service status, and the

delay setpoint, alarm state, acknowledgement, and inhibit functions for the

following alarms conditions – Position Failure (PFT) and Out-of-Range Low

(OORLAlm)


(APC7001)

IQ_AOI_DigitalAlarm - none

Digital Alarm AOI which is called by the GateEMTT AOI

Version: Edited 3/19/2008

(APC7001)



5


IQ_AOI_PIDE - none

Enhanced PID instruction in function block format which is called by the

IQ_AOI_StdPID AOI

Version: Edited 12/12/2007 by NAPA/tbertram

(ACP4001)

IQ_AOI_StdPID - none

Handles the in and out data to interface with the IQ_AOI_PIDE AOI


(ACP4001)

MtrHOR - Fixed Speed Motor With HOR/HOA Control

Monitors and controls the start/stop, interlocks, HOR/HOA mode, Out-of-

Service status, run time data (see ETM AOI) and the delay setpoint, alarm

state, acknowledgement, and inhibit functions for the following alarms

conditions – Motor Lockout (MLO), Control Time-out (CTO), and Fault

(Fault)


(ACP2001, ACP4001, APC7001, APC7201)

MtrL - Locally Controlled Motor

Monitors and controls the Out-of-Service status, run time data (see ETM AOI)

and the delay setpoint, alarm state, acknowledgement, and inhibit functions

for the following alarms conditions – Fault (Fault) and Maintenance Required

(MntAlm)

Version: Edited 12/3/2007 by NAPA/zmao

(ACP2001, ACP4001, APC7001, APC7201)

StdPID - Standard PID Function

Standard PID instruction in ladder logic format


(ACP4001, APC7001)

TCtr - Convert Preset and Timing the Run Cmd

Convert the timer preset entered from SCADA to milliseconds for the

following Timers:

- Interval between equipment starts

- Run Duration 1

- Run Duration 2

- Run Duration 3

- Delay between starts for Equipment 1 and 2

- Delay between starts for Equipment 2 and 3

- First Cycle Starts


(ACP4001, APC7001)

Total - Analog Totalizer

An analog input is sampled every second and divided by a selected time base

(seconds, minutes, hours, or days) to calculate and store the following data –

Day Total, Cumulative Total, Last Cumulative Total, Last Day Total, and

Total Max Value

Version: Edited 8/17/2007 by NAPA/ZMAO

(ACP2001, ACP4001, APC7001)



6


VlvEMTI - Motor Operated Valve Control

Local-OFF-Remote Motor Operated Discrete Valve Control Module monitors

and controls the open/close functions via discrete inputs and outputs,

interlocks, HOR mode, Out-of-Service status, and the delay setpoint, alarm


conditions – Position Failure (PFT) and Control Time Out (CTOAlm)


(ACP4001, APC7001)

VlvEMTT - EMTT Valve HOR Control

Local-OFF-Remote Electric Multi-turn Throttle Control Module monitors and

controls the open/close functions via analog valve position inputs and outputs,

interlocks, HOR mode, Out-of-Service status, and the delay setpoint, alarm


conditions – Position Failure (PFT) and Out-of-Range Low (OORLAlm)


(ACP4001)

VOL - Liquid Volume in a Container

Calculate the liquid volume of a rectangular or cylindrical container, in cubic

feet, based on an analog level transmitter, the number of containers, container

width, container length, container height, and container radius. (Zero width

and length if cylindrical container: Zero radius if container is rectangular)

Vol = # of containers * Level *(Width * Length + π * Radius2)


(ACP4001)

5 SCADA - HMI Hardware and Software

5.1 Introduction

This standard presents the system-wide, graphic display requirements for the SCADA System. For the

sake of clarity, the generic graphic displays described in this standard are presented as individual

frames/screens as might be used in an HMI. The HMI software shall support all displays and operator

activities described in this standards document.

The City has standardized on the FactoryTalk View SE HMI platform.

5.2 Hardware Requirements

The following hardware specifications indicate minimum quality and components at the time the

standard was adopted. Provide manufacturer’s latest state of the art model capable of providing high

performance operation of the SCADA system and meeting the intent of the minimum requirements

listed below. Select exact opinions to exceed the minimum requirements of all software installed on a

given machine.



7


A. SCADA server hardware and OS (Primary and Backup where applicable)

Utilizing Windows OS and Hyper-V.

The following is a listing of potential VM sessions for the SCADA HMI servers:

• FactoryTalk License Server

• Factory Talk Server

• Alarm Server

• AD Server

• Remote Access Gateway

• NTP Server

B. Large Screen Flat Panel Displays

Note: Component specified herein is based on the state of the art during standard adoption. Provide

the latest state of the art hardware available during the submittal process, and upgrade features as

necessary.

The following specifications outline the minimum requirements for each Wall Display.

1. Function: Provide viewing of multiple source inputs

2. Mounting: Wall mounting with swingout wall mount and cable management

3. Screen Size: 42-inch, Widescreen (16:9), minimum

4. Resolution: 1920 x 1080 pixels native

5. Contrast Ratio: 8,000,000: 1, minimum

6. LED Backlight

7. Audio: Stereo (2-channel) audio speakers

8. Power: 120Vac

9. Energy Star Compliant

10. Interface Ports:

i. Ethernet RJ-45

ii. (4) HDMI

iii. (1) PC Input, D-sub

iv. USB Port

v. Component Input

vi. Composite Input

vii. RF Input

11. Manufacturers:

i. Samsung

ii. Vizio

iii. Sharp-Aquos

iv. Approved Equal

C. Flat Panel Displays

Note: Component specified herein is based on the state of the art during standard adoption. Provide the

latest state of the art hardware available during the submittal process, and upgrade features as necessary.

The following specifications outline minimum requirements for each Display:

1. Function: Provide viewing of SCADA client

2. Mounting: Wall or base mounting as required for desktop mounting

3. Screen Size: 27-inch, Widescreen (16:9), minimum

4. Resolution: 1920 x 1080 pixels native



8


5. Brightness: 350 cd/m2

6. Contrast Ratio: 2,000,000: 1, dynamic, minimum

7. Backlight: LED

8. Power: 120Vac

9. Energy Star Compliant

10. Interface Ports:

i. VGA

ii. DVI-D (HDCP)

iii. HDMI

iv. USB Port

11. 3-year warranty

12. Manufacturers:

i. Dell

ii. Hewlett-Packard (HP)

iii. Samsung

iv. Approved Equal

D. SCADA Operator and Engineering Workstation



All Operator and Engineering workstations will consist of the following minimum components:

1. CPU

a) Processor: Core i7, 3.6 GHz, minimum

b) RAM: 8 GB minimum

c) Hard drive: 500 GB minimum

d) Power: 120Vac

e) Energy Star Compliant

f) Interface Ports:

i. VGA

ii. DVI-D (HDCP), 2 port minimum

iii. HDMI, 2 port minimum

iv. USB Port, 4 port minimum

g) 3-year warranty

h) Manufacturers:

i. Dell

ii. Hewlett-Packard (HP)

iii. Samsung

iv. Approved Equal

2. Displays

See Section 5.2 item C above for details

3. Wireless Keyboard and Mouse

a) Connectivity: Wireless

b) Interface: USB Nano receiver

c) Keyboard

i. Low-profile keys

ii. Adjustable keyboard height

iii. Numeric keypad

iv. 12 Function keys, minimum



9


d) Mouse

i. On/Off button

ii. 3-button with scroll wheel

iii. Optical tracking

e) 3-year warranty

f) Manufacturers:

iv. Dell

v. Microsoft

vi. Logitech

vii. Approved Equal

4. Speakers

a) Connection Type: Analog stereo (3.5 mm)

b) Power Rating (RMS): 3 watt minimum

c) Frequency Response: 150 Hz to 20 kHz

d) Audio Controls (Speaker): Volume + Power

e) Manufacturers:

i. Dell

ii. Bose

iii. Logitech

iv. Approved Equal

E. Local Operator Interface Terminals (OIT)



All OITs will be an Allen-Bradley PanelView Plus 7 terminal with a 10” display (2711P-T10C21D8S).

The following specifications outline the minimum requirements for each OIT:

1. Operator Input: Touch screen

2. Display Type: Color TFT LCD

3. Display Size, diagonal: 10.4 inch

4. Aspect Ratio: 4:3

5. USB Ports: 1 USB Type 2.0 (Type A) to support removable flash drive for storage

6. Ethernet Ports: 1 10/100 Base-T, minimum

7. Input Power: 24 Vdc

5.3 Software Requirements

The FactoryTalk View Site Edition (SE) HMI platform will consist of at least the following software:

• FactoryTalk View SE Server with RSLinx

• FactoryTalk Historian SE

• FactoryTalk View Studio

• FactoryTalk View SE Client

• Hyper-V

• Alarm Notification Software (i.e. Win-911or other approved equal)



0


5.4 Historian Requirements

The Historian system needs to be scalable and economical. It must have the ability to store discrete and analog

tags data. The following list identifies the minimum requirements:

• Must be scalable, since the initial number of tags will be small and will grow as the system expands to

include other areas

• Must be accessible from multiple locations

• Ability to define data resolution for each individual tag to trigger data capture into historian

• Ability to store discrete (bit) tags that can be used as a trigger for other functions (i.e. data capture,

calculations, etc.)

• Function as the repository for multiple Utility data sources

o Water SCADA System

o WWTP SCADA System

o Collection SACDA System

o Laboratory data (LIMS)

o Handheld data collection devices

• Ability to easily export data to Microsoft Excel or other programs. Ideally would like to access tags directly

from Microsoft Excel or Access.

• Provide easy development of dashboards and various process optimization models

5.5 Application Security

The Factory Talk platform includes various options for implementing system security. The security

implemented for Crescent City’s Wastewater SCADA system is currently separate from any Microsoft

Windows security settings.

The current general security policy settings in the Factory Talk application are as follows:

Figure 1 - FT Security Policy Properties

The foundation for the implementation of security is based on the creation of user groups within the

Factory Talk application. Each individual who is to have access to the SCADA system has a security

configuration created within the Factory Talk application. This configuration is then assigned to a user

group. Each user group is then configured to allow or not allow access to each of the 16 specific

security codes (A to P) or default * security code allowing access to all users.



1


User Groups will include:

• Administrators (Areas A-P)

o Access to all functions within the SCADA system

o Ability to change passwords and permissions

o Ability create users and user groups

• Supervisors (Areas A-P)

o Access to all application graphical pages and functions

o No application permissions to modify or change the application

• Maintenance (Areas A-B)

o Acknowledge Alarms

o Access to all functions within the SCADA system

o Enable/Disable Alarms

o Alarm set points

o Modify process set points

• All other users (*)

o Access to view graphics

There are no runtime secured commands. Specific properties can be controlled using action groups and

assigning user groups to the appropriate action group

Figure 2 - Action Group Example

5.6 Graphical Requirements

5.6.1 General Screen Properties

Within the visible area of the screen, the graphics will be divided into two parts. There will be a top bar

across the width of the screen dedicated to screen title and navigation. The bulk of the screen area falls

below the top bar and is reserved for specific process display screens. The top bar is for navigation and

will always be visible.

Example graphic screens from the City’s WWTP are provided in Appendix A. Default starting graphic

shall be a welcome screen including a legend of standard conventions and colors. In general, the



2


graphic display layout must contain the following:

• Login/Logout controls

• Operator name

• Date and Time

• Facility Name and location

• Navigation Symbols/Icons

• Display area

The following graphic display settings shall be used:

• Resolution: 1280 X 934 designed to fit on 1280 X 1024 screens with taskbar showing.

• Security code

o B for screens with set points adjustments

o B for all pop ups

o B for screens with control functions

o * for all other screens

Figure 3 - Display Settings Properties



3


Figure 4 - Display Settings Behavior

The process graphic displays are built in a hierarchical structure, which allows the operator to view the

animated process graphics without the need to know the name of the display. Navigation in and around

the displays is accomplished by using a pointing device such as a mouse or trackball to “click” on the

object where more information is desired.

Graphic displays shall be schematic diagrams which use text, numbers, symbols, colors, and lines to

portray the processes and equipment controlled and/or monitored by the SCADA. In addition, the

graphic displays shall provide the operator with a convenient method of exercising control over water

production and distribution processes and equipment. The display system shall be capable of presenting

all information from the real-time, historical, and archived databases. The display subsystem shall take

full advantage of the graphics features of the hardware.

As an example, from a graphic depicting one of the geographical sub-area map displays, one would find

the desired facility icon and click on it, calling up the Facility (Station Screen) graphic display. The

Facility graphic display will show more specific process information and equipment within that area and

have animation and data displays to indicate current field status of equipment and data. Next, one may

choose a more specific piece of equipment to monitor by selecting it. The Control Pop-up graphic

display will show more detail for that specific piece of equipment and allow control. The following

diagram gives a pictorial representation of a generic hierarchical structure implemented throughout the

application. Each level of graphics shows more specific process information. A button on the

navigation toolbar shall be linked to the Main Menu and Process Overview graphic displays, thereby

allowing the user to quickly return to the top of the hierarchy from any process graphic display in the

system.



4


Figure 5 - Graphic Hierarchy

The following lists the general graphical configurations, general requirements for each graphic, and the

minimum required graphic screens. Appendix A includes an example of each of the screens described

below:

• 01-Welcome:

o Welcome screen shown on initial login.

o Include general legend for the system conventions.

• 02-Main Menu:

o Navigation buttons for every screen in the system

o Provide button to turn tag displays On/Off for equipment and instruments

o Include button to help file and develop help file

• 03-Communication Status

o Overview Network Diagram showing PLC communication status

o Clicking PLC targets brings up RSLinx Diagnostic Counters

o The status (normal/failed) of the SCADA computers and Local Area Network (LAN) equipment

shall be depicted in a graphic analogous to the Overview and Detailed Site/Equipment graphics

• 04-Alarm Summary / Banner

o Overview of system alarms and ability to sort and acknowledge

o Ability to view past alarms and logs

o Use FT Built-in alarm summary and log viewer objects

o Use FT Built-in alarm and event banner

• 05-Custom Trends

o Allows operator to develop custom trends of any system variables

o Use FT built-in trend utility



5


• 05-Historical trends

o Pre-built trends of critical system variables brought up by one click

o Calls Trend Templates through action buttons

• 06-Diagnostics

o Displays the status of each PLC module and point

o Each module has a popup to display point status using faceplates with passed parameters

• 06-Polling

o Monitors and controls polling for systems with remote facilities

o Allow polling of remote RTUs to be enabled/disabled

o Show communication status and current station being polled

o Provide display of communication success percentage

o Allow operator to adjust polling rate for each site

• 07 through 39 – Process Displays

o Individual displays of each major process area with P&ID layout

o Navigation to connected processes using pipe arrows

o Pop ups for individual equipment control and PID tuning

o Access to process control setpoints

• 40-Power Monitoring

o Utility and Generator Status monitoring

o Button to launch Power Monitoring program

5.6.2 Standard Colors and Text

The following lists the standard colors referenced within the Factory Talk application for the different

colors of backgrounds, text, and objects. Each color is referenced by its Red/Green/Blue (RGB) color

number and HEX value to identify the color referenced.

Color Red

RGB Color #

Green

RGB Color #

Blue

RGB Color # Hex

Black 0 0 0 00000000

White 255 255 255 00FFFFFF

Red 255 0 0 000000FF

Yellow 255 255 0 0000FFFF

Light Yellow 255 255 128 0080FFFF

Green 0 255 0 0000FF00

Blue 0 136 200 00C88800

Dark Blue 0 208 208 00D0D000

Cyan 0 255 255 00FFFF00

Purple 255 0 255 00FF00FF

Gray 192 192 192 00C0C0C0

Dark Gray 128 128 128 00808080



6


Alarm Colors and Text:

Font Arial, Regular 10

Condition Text Background

Normal Dark Gray Gray

Alarm Black Flashing Red/White *

Unacknowledged (cleared) Black Light Yellow

*Flashing rate is 2 seconds

Analog Display Colors (Global Numeric Displays):


Condition Text Background

Normal Yellow Black

Alarm Black Yellow

Out of Service White Blue

Alarm Inhibit Yellow Dark Gray

Equipment Status Labels (Global Text Objects):


Status Type Text

Alarm / Ready / Stopped Red

On / Available / Medium Green

Out of Service Blue

Control Status Light Blue

Mode Status / Warnings Yellow



7


Equipment States (Global Equipment Objects):

Equipment State Text Condition Value

Ready Red 0

Running Green 1

Out of Service Blue 2

Motor Lockout Red Flashing* 3

Alarm Yellow Flashing* 4

*Flashing rate is 1 second



8


5.6.3 Standard Equipment Objects

The following is a listing of common system objects to be used for similar type equipment as graphic displays

are developed. Color conventions for these graphics should match those outlined for equipment states under

the color subsection noted above. Color should be applied to all moving components such as motors as

shown in the example graphics in the appendix:

Vertical Turbine Pumps

Submersible Pumps

Centrifugal Pumps

Sludge Pump

General Motor

Flow Control Valve

Blower

Mixer

Chemical Feed Pump

Chemical Storage Tank

Flow Meter

Exhaust Fan:

Piping: All piping shall be FT standard color in color and utilize appropriate fitting graphics at all joints.

Piping size shall be scaled to meet the requirements for each specific process graphic.

Every attempt shall be made to keep piping and graphic sizes the same and consistent across all graphics to

the highest extent possible.



9


5.6.4 Process and Control Displays

Process and control displays will contain space for the header information, basic navigation, critical data

parameters and main process equipment information. Process screens are laid out in P&ID format with color

used primarily for status indication. Control or Set point displays are in table format to provide a clear view

of the associated set point and its value. Set point displays are accessed from a corresponding process display

to ensure set points are adjusted for the correct process.

Header Area:

The Header area provides a method for main screen navigation through use of buttons to main menu and

overview displays. The Header also contains the City logo which is clickable back to the welcome screen.

The Header contains information such as time and date and operator login information. The Header includes

the name of the facility and name of the process currently displayed.

Process Information Area:

The main process information area is the most dynamic area of the graphics as the information will change

based on the process area selected from the main menu. This series of screens provide all status information

for the facility. Control functions are integrated into popup screens accessed through targets on specific

equipment and setpoints on specific setpoint screens using navigation buttons for access.

Information is shown in the process area using analog indicators and global equipment objects. Information is

passed to these global objects using passed parameters to allow standardization of graphics and indicators.

5.6.5 Popup Displays

Popups shall provide the capability of executing control actions through the graphic display. Operators shall

be able to execute control actions from the popup display page for that specific device or function.

Popup templates other than what is included in the Appendix, shall require the City’s approval.

Control Display graphics shall include but not be limited to the following:

• Pump information

o Tag Name

o Description o Auto/Manual status

o Out of service selection and indication

o Status (Running/Stop)

o Control (Auto/Manual, Start/Stop)

o Control (VFD Percentage – If Applicable)

o Monitoring (Runtime Hours, Power, Amps)

o Alarm Setpoints

o Interlock Control

• Valve information

o Tag Name

o Description

o Auto/Hand

o Status (Open/Close, Percent Open – If Applicable)

o Control (Auto/Open/Close)

o General Alarm



0


• Analog information

o Tag Name

o Description

o Out of Service selection

o Status (i.e. Pressure Value, Minimum and Maximum Range)

o Alarm Setpoints (Hi, Hi-Hi, Lo, Lo-Lo)

o Alarm Activation Timer (Hi, Hi-Hi, Lo, Lo-Lo) o Out of Range Alarms

o Rate of Change Alarm

o Deadband

o Drift

o Override Value

o Individual inhibit and reset for all alarms

• PID Controller

o Tag Name

o Description

o Auto/Manual Control

o Process Variable and Set point

o Setpoint Adjustment

o Control Variable Adjustment o Tuning Parameter popup

The displays shall be a moveable popup display. The system shall provide the capability of executing control

actions through these popup graphic displays. Operators shall be able to execute control actions from the

schematic diagram page for that device or function.

The device control actions (Open/Close, Start/Stop etc.) by operators shall involve the use of popup menus to

prompt for the selection of various commands to be executed by the SCADA system.

Confirmations shall be required when a value, state, action, etc. is modified.

After a selection is made, it shall be automatically cancelled if it is not executed within a preset time.

The operation of the field device shall be confirmed by status change information on the display (e.g., on a

schematic station display, the symbol and color of the equipment changes).

5.6.6 Alarm Management

Consistent handling of alarms is very important to ensure operations personnel are completely aware of the

situation that caused the alarm so that the proper corrective action may be taken promptly. The following

paragraphs describe requirements for alarm management.

5.6.6.1. GENERAL Alarms are defined as:

• a warning that a process variable has passed a defined limit and is approaching a value that is

undesirable, unsafe, or both

• a problem annunciated via a visual indication, a message, an audible sound, or a combination of these

indicators



1


Events are defined as:

• an alert to facility status, information about operating modes, all considered within normal operations

• a record of status changes logged for possible analysis

Alarm Management Philosophy

• Under normal conditions, there should be no alarms

• Operators are shown only alarms they can act upon

• Alarms alert operations to situations hazardous to personal safety or regulatory compliance (High

Priority)

• Alarms identify deviations with potential financial loss (Medium Priority)

• Alarms require operator action

Alarm Processing:

• All field alarms shall be generated in the PLC and reported to the SCADA as well as the local HMI or

OIT at the LCP level.

• Once received by the SCADA, the SCADA software must be capable of categorizing each alarm by

area. Areas can then be assigned to one or more workstations.

Alarm Presentation:

• Displays shall be provided to list all control and communication system alarms.

• Alarm summary displays shall list all current alarms in reverse chronological order, i.e., most recent on

top.

• Alarm summary displays shall be configured such that no alarms are lost due to a full buffer.

• The system shall prevent an alarm overflow event from occurring.

• The SCADA shall automatically generate the alarm summary displays. These displays shall be called

up from any display via the alarm pushbutton by authorized City personnel.

• The reserved alarm window on every graphic display will display the most recent 3 alarms

(acknowledged/unacknowledged) in reverse chronological order. The format shall be consistent with

the alarm summary display format. If no alarms exist, this window will be blank.

• Alarms for each piece of equipment shall be determined during the graphics development workshops

for each specific project.

5.6.6.2. GENERAL ALARM DISPLAY CONFIGURATION Each alarm shall occupy one line.

Alarm colors shall follow the color conventions shown in Section 5.5.2.

Paging shall be in reverse chronological order with the most recent alarms on page one.

Each alarm descriptor, as a minimum, shall include the following:

• Event Time (/MM/DD/YYYY HH:MM: SS) – 24-hour duration

• Area (Process)

• Alarm Name (Tag Name)

• Message (Point Description)

• Condition (i.e. Hi Hi)

• Priority

• Alarm State (i.e. In Alarm, Unacknowledged)

Authorized City personnel must have the capability of arranging these fields in any format. The format will

then remain consistent throughout the alarm summary display.



2


5.6.6.3. ALARM SUMMARY DISPLAY Only current active alarm and return-to-normal conditions shall be listed.

If new area(s) of responsibility are assigned, or existing area(s) of responsibility are deleted, then the alarm

summary display shall be automatically reassembled to reflect those changes.

All alarms shall carry their associated color to the Alarm Summary pages.

The Alarm Summary displays shall be called up from any display via the ALARM pushbutton.

SCADA system alarms (i.e. computers, peripherals, modems, etc.) shall be displayed on the alarm summary

display as well as in the reserved alarm window on the bottom of the graphic display. How these alarms are

configured for viewing will be determined during the detailed design. When the alarm summary display is on

an HMI, it will use the entire display area except for the top bar area. The reserved alarm window on the

bottom will not exist when the alarm summary display is the active window.

5.6.6.4. ALARM AREAS Alarm areas are defined by user groups and include:

• Operations (OP), which includes alarms specific to process operations

• Maintenance (MX), which includes alarms specific to equipment performance monitoring

• SCADA Support (SS), which includes alarms specific to SCADA system component monitoring, such

as PLCs, HMIs, network communications, etc.

• Analytical Testing (AT), which includes alarms specific to process pilots, testing and start-up situations

5.6.6.5. ALARM PRIORITY Alarms are assigned a priority based on the following definitions:

• High: potential hazardous or permit compliance condition, requiring immediate response

• Medium: potential performance deviation, requiring prompt attention

• Low: alert to abnormal condition, requiring acknowledgement

• Event: record of monitored events

5.6.6.6. ALARM/EVENT PRESENTATION Alarms are presented primarily in the Alarm Summary Display or Alarm Banner in other displays. Alarms

may also generate visual notification on equipment graphics. Refer to Section 5.5.2 for alarm presentation

colors.

Alarms are filtered by area into separate displays, Operations alarms is the default display in the alarm view

node. Maintenance and System Support alarms reside in their own displays that may be called by the

operator.

5.6.6.7. REMOTE ALARM NOTIFICATION (CALL OUT) The SCADA system shall be capable of remote alarm notification through a variety of media including

telephone, pager and email. Remote alarm notification will be in operation 24 hours per day, every day of the

year. The system will be capable of scheduling call-out responsibility by shifts with a seven-day schedule.

The remote alarm notification will be capable of speaking the alarm condition. The system shall be configured

for remote alarm acknowledgement; however, remote control through the remote alarm notification system

will not be allowed.



3


5.6.6.8. HISTORICAL ALARMS Historical alarm display must have the same format as the alarm summary display.

All alarms shall be logged to a historical alarm file and stored on mass storage media. Archiving of the

alarms shall be in reverse chronological order.

It shall be possible to retrieve the alarm by tag name, area or function. Retrieved alarm displays shall have the

same format as alarm summary displays.

Historical alarms shall be sortable by a minimum of two variables (user selectable).

5.6.6.9. ALARM ACTIONS The SCADA system shall be capable of directly disabling/enabling alarm points in the point of origin.

When the occurrence of one or more alarms causes the audible alarm to sound at one or more stations, it shall

be possible to configure the system so that each alarm can be either muted from all stations or one station at a

time.

The audible alarm shall remain silent until another unacknowledged alarm in the appropriate area is detected

by the system.

5.6.6.10. ALARM ACKNOWLEDGEMENT Unacknowledged alarms shall be distinguished from acknowledged alarms using color and messaging

conventions.

Unacknowledged returns-to-normal shall be distinguished from unacknowledged alarms using color and

messaging conventions.

Unacknowledged return to normal alarms shall remain in the alarm summary display.

Both unacknowledged and unacknowledged returns-to-normal shall flash in the alarm summary display and

the reserved alarm window at the bottom of the graphic display.

To acknowledge an alarm, the operator shall use one of the following procedures:

• Acknowledge an individual alarm on the current page of Alarm Summary display by selecting a line

and depressing the single acknowledge pushbutton

• Acknowledge highlighted alarms on the current page of the Alarm Summary display by selecting

multiple alarms and depressing the multiple acknowledge pushbutton

Acknowledge all alarms on the current page of Alarm Summary display by depressing the all acknowledge

pushbutton. Upon acknowledgement, the symbols and messages associated with the alarm shall stop flashing

on all displays upon which they appear.

Acknowledging all alarms appearing on a display page by an "all acknowledge button” shall not also

acknowledge additional alarms on associated (but not displayed) pages of the display.

Acknowledged returns-to-normal shall be automatically cleared from the alarm summary display and the

reserved alarm window at the bottom of the graphic display.



4


5.6.7 Data Log Models

Data log models are configured for all major logging variables and analog variables and are stored in local

files unless otherwise noted. The following lists the main Data Log Models developed for all variables:

Analog variable Log Model:

• Log all analog variables

• Trigger Interval: 10 seconds

• Start new file daily

Daily Totalizer Log Model:

• Log daily totalizer for all analog variables and runtimes (yesterday’s total)

• Trigger Interval: Daily On-Demand via event

• Database: ODBC coordinated with City

VFD Log Model:

• Log amps and speed feedback for each VFD

• On change Trigger: 0.1 change in percent of variable, maximum of every 1 second

• Heartbeat check every 5 minutes

• Start new file daily

6 Submittals


All HMI screen layouts, symbols, and pop-up displays need to be submitted to the City for review and

approval during the design process, prior to replication to multiple instances.

All PLC/RTU programs need to be submitted to the City for review and approval for adherence to

programming standards.

7 Testing Requirements


CONTRACTOR to perform testing on integrated systems at key stages in the process. At a minimum,

Factory Acceptance Testing (FAT), Operational Readiness Testing (ORT) and Performance Acceptance

Testing (PAT) shall be performed. Staging Testing may be added at City or Engineer’s discretion.

All testing, commissioning, and acceptance work shall be covered by a “test plan” which must be prepared for

all SCADA projects.

Test planning is a continuous process which begins during design and continues throughout the testing period.

The City requires a test plan to be prepared as part of the design process. Thereafter, the plan will be refined

according to individual contract requirements.

The test plan will outline the responsibility and involvement of all parties involved in the project for all tests.

The updated test plan is required to be submitted, reviewed by, and accepted by relevant City staff at least two

(2) weeks prior to the commencement of any tests.

The City will not permit testing to commence until the test plan is approved.



5


The test plan will contain all testing to be performed as a part of the project including factory and onsite tests.

The test plan will address all individual devices, equipment, system’s hardware and software components, and

control functions. The test plan shall ensure that no components remain untested.

Each test shall be specific to the item of equipment or system to be tested. Test plans shall identify specific

equipment or tag number device or control station to be manipulated or observed during the test procedure

and the specific results to be observed or obtained. Test plans shall also be specific as to support systems

required to complete the test work, temporary systems required during the test work, subcontractors' and

manufacturers' representatives to be present, and expected test duration.

The test plan will contain copies of any test reports/sheets to be used. Specific test reports must be prepared

for testing every device, control loop, and at each stage (e.g. Factory Acceptance, Pre-commissioning,

Commissioning, and Performance Testing).

The test plan shall contain a description of any impacts and/or disruption to existing operations and show how

existing operations are to be maintained. All outages and equipment operations associated with

commissioning shall be identified and estimated outage times determined.

A detailed schedule shall be included in the test plan indicating where and when testing will be carried out

and by whom.

On the SCADA portion of a project, one person from the City shall be appointed as a commissioning team

coordinator. Likewise, consultants and contractors shall appoint one person. Together these persons will lead

the commissioning team and the team will be responsible for the entire commissioning and acceptance

process. In addition to the coordinators, the team will be comprised of key individuals from the City. The

team shall call upon resources of their respective organizations to carry out specific tests where necessary.

Commissioning personnel shall not be changed without the approval of the City.

All equipment/manufacturer representatives who attend site for commissioning shall be fully qualified to

conduct the necessary work. Contractors and consultants shall ensure that properly trained representatives are

made available.

The consultant and contractor's entire testing/commissioning team shall be available at the site of the work

during the times agreed upon in the testing plan, and shall be available within 8 hours notice at all other times.

The testing and commissioning team shall at all times be equipped and ready to provide for emergency

repairs, adjustments, and corrections to the equipment.

Test procedures described within the test plan shall describe an overall plan for testing and provide a

description of the system test configuration including required test equipment and any simulation techniques.

The procedures shall be a detailed step by step checklist which will be followed during system testing

including check off blanks and signature locations at the completion of each major functional section.

The contractor shall provide all testing records and documents. Calibration documentation shall include

identification (by make, manufacturer, model, and serial number) of all test equipment, date of original

calibration, subsequent calibrations, calibration method, and test laboratory.

Equipment and system documentation, as a minimum, shall include the date of test, equipment number or

system name, nature of test (performance or operational), test objectives, test results, and test instruments

employed for the test. A record file shall be provided for each system and item of equipment.

Copies of test reports for each phase of the FAT shall be submitted to the City at the completion of each

phase. All testing, commissioning, and performance test reports shall be compiled into one document and the

original signed copies submitted to the City for record purposes at completion of all testing.



6


7.2 FAT - Factory Acceptance Test

Prior to system deployment, inspect, test, and document that the entire SCADA system is complete and ready

for implementation at the City facilities. This testing will verify that the system configuration meets the

operational and functional requirements of the system. The FAT will be conducted and documented in an

unwitnessed format by the contractor prior to scheduling the witnessed FAT with the City. The FAT will be

performed at the Contractor’s facility or other location as approved by the City in advance.

Some level of simulation will be required, since the system will not be connected to any field devices. This

simulation will control PLC/RTU inputs based on the status of system outputs and a normally expected

response. This simulation must allow for the interruption of the normally expected response to create alarm

conditions, in order to demonstrate the functionality of the system alarms.

The FAT test plan will include step-by-step procedures for testing of the complete system including at least

the following:

• System boot-up

• Switching between primary and back-up servers

• VM failure and recovery

• Operator log-in and log-out process and verify logging as an event

• Communication status, diagnostics, and recovery from failure

• PLC/RTU status, diagnostics, and recovery from failure

• Discrete device status, control, data, and alarms

• Analog device status, setpoint, control, data, and alarms

• Verify the status of every alarm on the Alarm Summary screen and on the process screens

• Verify all operator actions are logged as Events and can be viewed

7.3 ORT - Operational Readiness Test

Prior to the start-up test period and PAT, inspect, test, and document that the entire Process Instrumentation

and Control System (PICS) is ready for operation:

Unit Process and Component Inspections and Tests:

a. Check PICS for proper installation, calibration, and adjustment on a loop-by-loop and

component-by-component basis.

b. Provide space on forms for signoff by PICS subcontractor.

c. Use loop status report to organize and track inspection, adjustment, and calibration of each

loop and include the following:

1. Project name.

2. Loop number.

3. Tag number for each component.

4. Checkoffs/Signoffs for Each Component:

i. Tag/identification.

ii. Installation.

iii. Termination wiring.

iv. Calibration/adjustment

5. Checkoffs/Signoffs for the Loop

i. Field Device Signals Transmitted to the PLCs are Operational:

Received/sent, processed, adjusted.



7


d. Component calibration sheet for each active field component (except simple hand

switches, lights, gauges, and similar items) include the following:

1. Project name.

2. Loop number.

3. Component tag number or PLC register address.

4. Component code number for field device elements.

5. Manufacturer for field device elements.

6. Model number/serial number for field device elements.

7. Summary of Functional Requirements, for Example:

i. Indicators and recorders, scale and chart ranges.

ii. Transmitters/converters, input and output ranges.

iii. Computing elements’ function.

iv. Controllers, action(direct/reverse) and control modes (P&ID).

v. Switching elements, unit range, differential (fixed/adjustable), reset

(auto/manual).

8. Calibrations, for Example, but not Limited to:

i. Analog Devices: Actual inputs and outputs at 0, 25, 50, 75, and 100

percent of span, rising and falling.

ii. Other Field Devices: Actual trip points and reset points.

iii. Controllers: Mode settings (P&ID).

iv. Actual inputs or outputs of 0, 25, 50, 75, and 100 percent of span, rising

and falling.

v. Space for comments.

9. Maintain loop status reports, valve adjustment sheets, and component calibration

sheets at site and make them available to Engineer at all times.

10. Test and calibrate all fiber optic data links. Document that the dB links are within

specified limits and the data communication is error free at specified baud rates.

11. These inspections and tests will be spot checked by Engineer.

12. Engineer reviews loop status sheets and component calibration sheets and spot-

check their entries periodically, and upon completion of ORT. Correct deficiencies

found.



8


7.4 PAT - Performance Acceptance Test

Once ORT has been completed and facility has been started up, perform a witnessed PAT on the complete

PICS to demonstrate that it is operating as required by the Contract Documents. Demonstrate each required

function on a paragraph-by-paragraph, loop-by-loop, and site-by-site basis.

Loop-specific and non-loop-specific tests same as required for FAT, except that the entire installed PICS

tested using actual process variables and all functions demonstrated.

Perform local and manual tests for each loop before proceeding to remote and automatic modes.

Where possible, verify test results using visual confirmation of process equipment and actual process variable.

Unless otherwise directed, exercise and observe devices supplied by others, as needed to verify correct signals

to and from such devices and to confirm overall system functionality. Test verification by means of

disconnecting wires or measuring signal levels is acceptable only where direct operation of facility equipment

is not possible.

Provide updated versions of the following documentation available to the Engineer at site, both before and

during tests.

• One copy of submittals applicable to the equipment to be tested

• One copy of the Drawings and Specifications together with addenda and applicable change orders

• Make one copy of all O&M manuals

Specialty Equipment: For certain components or systems provided under this section, but not manufactured

by PICS Subcontractor, provide services of qualified manufacturer’s representative during installation, start-

up, demonstration testing, and City training.

Instruments shall be tested at 0 percent, 25 percent, 50 percent, 75 percent, and 100 percent of scale through

wired and wireless communications to the PLC and to the HMI insofar as is practical and not to put effluent

or water quality at risk.

8 Training

The requirements for training as specified in this section shall be organized by the Contractor into a training

program meeting the standards set out in this specification.

8.1 City’s Responsibility

The City will provide a list of personnel which are required to receive training and instruction.

The City will pay the City’s staff for all costs associated with demonstrations and training, including all time,

travel, lodgings, etc. The City reserves the right to deduct the cost of any cancellations or repeat sessions

necessary, as a result of any actions or omissions of the Contractor, from any monies due to the Contractor

under this Contract.



9


8.2 Contractor’s Responsibility

The Contractor shall provide training of the City’s personnel by persons retained by the Contractor

specifically for the purpose, in the proper operation and maintenance of the equipment and systems installed

under the contract.

1. The Contractor shall provide on-the-job training of the City’s personnel for equipment as specified.

The training sessions shall be conducted by qualified, experienced (2 years minimum), and licensed

where necessary, factory-trained representatives of the various equipment manufacturers. Training

shall include instruction of operation personnel in system operation and instruct instrumentation,

electricians and electronics technicians in preventative maintenance and normal maintenance up to

major repair.

2. The Contractor shall submit the following information to the City. The material shall be reviewed and

accepted by the City no later than three (3) weeks prior to delivery of the training.

a) Lesson plans for each training session to be conducted. In addition, training manuals, handouts,

visual aids and other reference materials shall be included.

b) Date, time, and subject of each training session and qualifications of individuals to be conducting

the training.

c) Concurrent classes will not be allowed in training schedule.

3. The Contractor shall conduct training sessions for the City’s operation and maintenance personnel to

instruct the staff on the proper operation, care and maintenance of the equipment and systems

installed under the contract. Training shall take place at the site of the work and under the conditions

as specified. Vendor operation and maintenance manuals shall be available to City’s personnel at

least thirty (30) days prior to the date scheduled for the individual training session.

4. Field training sessions shall take place at the site of the equipment. The Contractor shall provide a

training facility with a capacity for at least ten (10) persons for classroom training.

5. Formal written lesson plans shall be prepared for each training session. Lesson plans shall contain an

outline of the material to be presented along with a description of visual aids to be utilized during the

session.

a) Each plan shall contain a time allocation for each subject.

b) One complete set of originals of the lesson plans, training manuals, handouts, visual aids and

reference material shall be the property of the City and shall be properly bound for proper

organization and easy reproduction in an identical manner to the Operation and Maintenance

Manual.

c) The Contractor shall furnish ten (10) copies of necessary training manuals, handouts, visual aids

and reference materials at least one (1) week prior to each training session.

d) All submittals in electronic format as well as printed copies.

6. Each training session shall be comprised of time spent both in the classroom and the field. Each

training session shall cover the following topics for each item of equipment or system:

a) Familiarization

b) Safety

c) Operation

d) Troubleshooting

e) Preventive maintenance

f) Corrective maintenance

g) Parts

h) Local representatives

i) Operation and Maintenance manuals



0


7. The City may record themselves or retain the services of a commercial video-recording service to

record each training session. After recording, the material may be edited and supplemented with

professionally produced graphics to provide a permanent record. The Contractor shall advise all

manufacturers providing training sessions that the material may be video-recorded and that the City

may use such recordings for its own purposes without limit.

8. As a minimum, the Contractor shall execute the training requirement in the follow manner:

a) Training shall be conducted in conjunction with the operational testing and commissioning

periods.

b) Classes shall be scheduled such that classroom sessions are interspersed with field instruction in

logical sequence.

c) The Contractor shall arrange to have the training conducted on consecutive days, with no more

than four (4) hours of classes scheduled for any one day.

d) The Contractor shall take attendance. The attendance sheet shall be submitted to the City for

their records.

9. As a minimum, classroom equipment training for operations personnel will include:

a) Using slides and drawings, discuss the equipment specific location and an operational overview.

b) Purpose and function of the equipment.

c) A working knowledge of the operating theory of the equipment.

d) Start-up, shutdown, normal operation, and emergency operation procedures, including a

discussion on system integration and electrical interlocks, if any.

e) Identify and discuss safety items and procedures.

f) Routine preventative maintenance of the equipment and ancillary components.

g) Operator detection, without test instruments, of specific equipment trouble symptoms.

h) Required equipment exercise procedures and intervals.

10. As a minimum, hands-on equipment training for operations personnel will include:

a) Identify location of equipment and review the purpose

b) Identifying instrumentation

c) Location of primary element

d) Location of instrument readout

e) Discuss purpose, basic operation and information interpretation

f) Discuss, demonstrate, and perform standard operating procedures and round checks

g) Discuss and perform the preventative maintenance activities

h) Discuss and perform start-up and shutdown procedure

i) Identify and review safety items and perform safety procedures, if feasible.

j) Review, demonstrate and train Operation staff on the SCADA HMI system to show and explain

how the control of the equipment is carried out and how to identify control problem(s).

11. Classroom equipment training for the maintenance and repair personnel will include:

a) Theory of operation

b) Description and function of equipment

c) Start-up and shutdown procedures

d) Normal and major repair procedures

e) Equipment inspection and trouble shooting procedure including the use of applicable test

instruments and the “pass” and “no pass” test instrument readings

f) Routine and long-term calibration procedures

g) Safety procedures

h) Preventative maintenance



1


12. Hands-on equipment training for Maintenance and repair personnel shall include:

a) Locate and identify equipment components

b) Review the equipment function and theory of operation

c) Review normal repair procedures

d) Perform start-up and shutdown procedures

e) Review and perform the safety procedures

f) Perform City’s-approved practice maintenance and repair job(s), including mechanical and

electrical adjustments and calibration and trouble shooting equipment problems.

g) Review and use equipment manufacturer’s manual in the hands-on training.

h) Demonstrate and train Maintenance staff on replacement of the CPU, network interface units,

network communication modules, power supply, controllers, I/O cards, etc.

i) Review, demonstrate and train Maintenance staff on the SCADA HMI, PLC and OIT program

logic and stepping through the program from beginning to the end to show and explain how the

control of the equipment is carried out and how to identify/resolve programming / control

problem(s).



2


APPENDIX A – EXAMPLES of WWTP HMI SCREENS

Per Section 5.5.1, the following WWTP screenshots are included in this Appendix:

• Screen 01 Welcome

• Screen 02 Main Menu

• Screen 03 Communication Status

• Screen 04 Alarm Summary

• Screen 04 Alarm Banner

• Screen 05 Trends – Custom

• Screen 05 Trends – Historical

• Screen 06 PLC Diagnostics

• Screen 07 Liquid Stream

• Screen 08 Solids Stream

• Screen 40 Power Monitoring

• Screen 98 Flow Totalizers



3


Screen 01 – Welcome

Screen 02 – Menu



4


Screen 03 – Communication Status

Screen 04 – Alarm Summary



5


Screen 04 – Alarm Banner

Screen 05 – Trend – Custom



6


Screen 05 – Trend - Historical

Screen 06 – PLC Diagnostics



7


Screen 07 – Liquid Stream

Screen 08 – Solids Stream



8


Screen 40 – Power Monitoring

Screen 98 – Flow Totalizers



9


APPENDIX B – EXAMPLE POPUP SCREENS



0


HOA_gt HOA_mov

HOA_ss HOA_VFD



1


Maintenance Reset Digital Alarm SP

PID-Popup PID-Tune



2


PID- Trend

Analog Alarm SP Equipment Runtime



3


1756-IA16I Module Status 1756-OA16 Module Status

1756-IF8 Module Status 1756-OF4 Module Status



4


APPENDIX C – MISCELLANEOUS SYMBOLS



5


Global Objects