SCADA SOFTWARE, HARDWARE & STANDARDS

PROCEDURES

PALM BAY UTILITIES DEPARTMENT

PREPARED FOR:

PALM BAY UTILITIES DEPARTMENT

250 OSMOSIS DRIVE SE

PALM BAY, FLORIDA 32909

PREPARED BY:

3790 DIXIE HIGHWAY NE, SUITE D

PALM BAY , FLORIDA 32905

JUNE 2016

PBU2091 . 01L

ATTACHMENT A

SCADA Software, Hardware & Standards Procedures

Palm Bay Utilities Department

PBU2091. 01L i June 2016

TABLE OF CONTENTS

TABLE OF CONTENTS ......................................................................................................................... i

LIST OF TABLES ................................................................................................................................. iii

1.0 INTRODUCTION

1.1 Purpose

1.2 Facilities

1.3 City Standardization

1.3.1 Software

1.3.2 Hardware

1.4 Standards Criteria

2.0 TAGS

2.1 Definition

2.2 Naming Conventions

2.3 Addressing Convention

2.4 Analog Scaling

2.5 Alarms

2.6 Interlocks

2.7 Trends

2.7.1 Value Recording Intervals

2.8 Tag Creation

2.8.1 Analog Tag

2.8.2 Digital Tag

2.8.3 Trend Tag

2.8.4 Analog Alarm Tag

2.8.5 Digital Alarm Tag

3.0 GRAPHICS

3.1 Definition

3.2 Graphic Display Characteristics

3.3 Navigation

3.4 New Screens and Levels

3.5 Color Guidelines

3.5.1 Color Definitions

3.5.2 Function Color Definitions

3.6 Faceplates (“ Supergenies”)

3.6.1 VFD

3.6.2 Analog Valve

3.6.3 PID

3.6.4 Discrete Motor

3.6.5 Discrete Valve/ Gate

3.6.6 Analog

3.6.7 Flow Meter

3.6.8 Data Entry

3.7 Use of Genies and Supergenies

3.8 Tool Tips and Help Pages

PBU2091. 01L ii June 2016

4.0 INDICATIONS AND SCAN TIMES

4.1 Definition

4.2 Equipment MODE Naming Convention ( LOCAL -OOS -COMP)

4.2.1 LOCAL

4.2.2 OOS (Out -of -Service)

4.2.3 COMP (Computer)

4.2.4 MANUAL

4.2.5 AUTO

4.3 Communication Failures

4.4 Alarm Scan Time

4.5 Page Scan Times

5.0 SECURITY

5.1 User Permissions

6.0 REPORTS

6.1 Background

6.2 Logged Values

6.3 Report Format

6.4 Report Scheduling

7.0 SOFTWARE VERSION

8.0 PROCEDURES REVISION HISTORY

8.1 General

8.2 Revision History

APPENDIX A – SAMPLE SCADA SCREENS

PBU2091. 01L iii June 2016

LIST OF TABLES

Table 1 -1. PBUD Facilities Listing

Table 2 -1. Tag Naming Convention

Table 2 -2. Alarm Categories

Table 2 -3. Standard Recording Intervals

Table 2 -4. Analog Tag Parameters

Table 2 -5. Digital Tag Parameters

Table 2 -6. Trend Tag Parameters

Table 2 -7. Analog Alarm Tag Parameters

Table 2 -8. Digital Alarm Tag Parameters

Table 3 -1. HMI RGB Color Scheme

Table 3 -2. Function Color Definitions

PBU2091. 01L 1 June 2016

1.0 INTRODUCTION

1.1 Purpose

The purpose of the SCADA Software, Hardware & Standards Procedures manual is to formulate a City -wide , long -term SCADA strategy to reduce operational costs by implementing programming standards that will streamline maintenance and operation activities.

The City’s SCADA system was implemented over time on a site -by -site basis. Different programmers worked on the system without a written set of guidelines in place. The result was a SCADA system and looked and functioned differently at each of the facilities.

The purpose of this guideline is to establish a set of standards for new projects so that graphics, colors, naming conventions, and functionality are consistent throughout the system. A consistent set of standards will help facilitate operations and maintenance by having all look and operate in a similar manner.

These guidelines are designed to be a “working document ” with revisions made at periodic intervals as needed to incorporate changes with new software versions, integration with other software systems, and include new functionality as requested by the users.

1.2 Facilities

The SCADA system presently connects all of PBUD’s facilities, including the treatment plants, lift stations, remote pump stations, and water wells. A summary of the facilities and the approximate date

SCADA technology was installed has been provided below.

Table 1 -1. PBUD Facilities Listing

Facility SCADA Installation Date

North Regional Wastewater Treatment Plant (WWTP) 2003

North Regional Water Reclamation Facility ( WRF)

2005 – Main Plant

1999 – Reclaim High Service Pumps

2009 – Disk Filters

North Regional Lime Softening Water Treatment Plant ( WTP) 2012

North Regional Reverse Osmosis Water Treatment Plant (RO WTP) 2006

South Regional Water Treatment Plant (SRWTP) 2004

Aquifer Storage and Recovery Well (ASR) 2005

Nash Water Re -Pump Facility 2007

Raw Water Wells 2007

Sanitary Lift Stations – Standard Install 1993 to Present

Sanitary Lift Stations – Data Flow Systems 2012

PBU2091. 01L 2 June 2016

1.3 City Standardization

1.3.1 Software

The current SCADA application is GE Proficy iFIX and GE Proficy Historian. GE Proficy iFIX is the user interface to the SCADA system and is comprised of graphic screens which are used for monitoring and controlling the pump stations and treatment plants. Some versions of the iFIX software are “view only nodes” which enables the user the ability to monitor but have no control capability. Generally, only plant operators have the ability to control the processes. The Historian software is used for archiving data such as equipment runtimes, continuous process data (analog signals such as levels, pressures, and flows) and alarm logs.

I/O Server Connectivity . The servers are connected using a fiber optic cable.

Communication Protocols . The SCADA servers at North Regional and South Regional communicate via the Ethernet protocol.

1.3.2 Hardware

The City has standardized computer hardware to Dell products. The current hardware employed by the SCADA system is distributed throughout the utility system:

South Regional RO Water Treatment Plant . The SCADA Servers and Historian Server reside in the SRWTP operations room.

North Regional Lime Softening Water Treatment Plant . The SCADA servers reside in the Lime

Softening WTP lab room. The lift station network ( non -Data Flow system) also communicate to these servers via the Master Radio in the water tower.

North Regional Wastewater Treatment Plant . The WWTP only has a view node which is located in the lab room.

PLC / RTU communication protocols . PLCs/RTUs communicate to each other and to the

SCADA software using the Modbus RTU protocol.

1.4 Standards Criteria

In order to make the SCADA system consistent across PBUD’s system, the following items need to be standardized:

Tags . Tags are names that assigned to data registers and objects within iFIX. Tags can be linked to PLC addresses as well as internal registers within iFIX. Tags are used for naming physical inputs and outputs, internall y calculated values, and objects within iFIX. All data and objects within iFIX have an associated tag.

Graphics . Graphics are the visual representation of the SCADA system to the user. Graphics include the representation of individual pieces of equipment and how they are connected in the treatment process. Graphics also include the display of system values ( levels, flows, pressures, etc.) and equipment status ( running, alarm, etc.). In addition, the system navigation ( how a user moves from one display page to another) is part of the graphics.

Indications and Scan Times . Indications are status information for the operator and are used to show the current control mode of the equipment ( local/ remote, manual/ auto) as well as if there are any alarms. Scan Times are used to set how often alarms are processed and graphical

PBU2091. 01L 3 June 2016 displays updated with status changes in the process system. These scan times are usually set to update once per second, but can be adjusted if necessary.

Security . System security is implemented through the use of a user login name and password.

Varying degrees of monitoring and control capability is assigned to each user through their login name. Control of the system is granted to operations staff, while other staff may only be granted permission to only view the system.

Reports . Reports are queries into the SCADA database and can be used to download and log information such as pump runtimes.

Software Version . The versions of the iFIX that are presently used vary depending on the when the original installations occurred. The installations used the latest version of iFIX that was available at the time, however, the previous installations were not updated at the same time so that all installations were operating on the same software version. The plan going forward will be to keep all software versions consistent across the SCADA network.

PBU2091. 01L 4 June 2016

2.0 TAGS

2.1 Definition

Tags are names that assigned to data registers and objects within iFIX. Tags can be linked to PLC addresses as well as internal registers within iFIX. Tags are used for naming physical inputs and outputs, internally calculated values, and objects within iFIX. All data and objects within iFIX have an associated tag. Tags need to follow a standardized naming convention so that they are consistent throughout the SCADA network. Standardized tags also help to troubleshoot issues within iFIX if a standard format is used across all SCADA installations.

2.2 Naming Conventions

HMI tags will follow the standard set forth in the “Software Tag Format Guidelines” document, and will be strictly adhered to for proper HMI operation (in particular, for genies and supergenies in GE Proficy). PLC programs will use this same tag naming standard. There are five (5) sections for a standard HMI tag, separated by an underscore (_).

Table 2 -1. Tag Naming Convention

Position 1st 2nd 3rd 4th 5th

Format => < Site Designation>_ < Process Group>_ < Device/ Equipment>_ < Item Number>_ < Function>

Max Charac ters 4 8 3 3 none

Refer to “Software Tag Format Guidelines” document for a complete description of Software Tag

Guidelines and examples.

2.3 Addressing Convention

For equipment requiring SCADA control, an address will be provided by the PLC to communicate with the HMI. Output addresses and values shall not be directly addressed by the HMI. For example, a manual start of a pump initiated by the HMI will not be directly written to the Start output of the PLC but rather a manual start bit will be set by the HMI is processed by the PLC program, ensuring all requirements are met before starting equipment. All commands to the PLC will be a latch command by the HMI with the PLC program unlatching the bit upon seeing the change.

2.4 Analog Scaling

All analog scaling will be performed within the PLC. The Raw Zero and Raw Full Scal e of each of the analog HMI tags will be the same, making PLC program troubleshooting easier.

PBU2091. 01L 5 June 2016

2.5 Alarms

All digital and analog alarms will be assigned an alarm category based on the City’s specification, or City

Personnel will assign the desired alarm categories. An additional alarm category (“ Events”) allows the

City to track specific events for troubleshooting purposes. The following categories shall be used:

Table 2 -2. Alarm Categories

Ala rm

Category Descr ipti on

Color Indi cation

Active, not acknow ledged

Active, Acknowledged

Non -active, not acknowledged Disabled

1 High Priority Analog

Alarms

Black text, red background

White text, black background Black text, grey background

White text, transparent background

2 Low Priority Analog

Alarms

Black text , yellow background

White text, black background Black text, grey background

White text, transparent background

3 Analog Events Not displayed Not displayed Not displayed Not displayed

11 High Priority Digital

Alarms

Black text, red background

White text, black background Black text, grey background

White text, transparent background

12 Low Priority Digital

Alarms

Black text, yellow background

White text, black background Black text, grey background

White text, transparent background

13 Digital Events Not displayed Not displayed Not displayed Not displayed

Discrete alarms sent from the PLC to the HMI may be configured with a delay timer in the PLC to remove nuisance alarms.

Analog alarms will be created and configured in the HMI in order to utilize the alarm features and capabilities of the HMI GE Proficy software. The setpoints for analog alarms (HI, HI -HI, LOW, LO -LO) will also be set in the HMI (not the PLC).

2.6 Interlocks

There is a distinct difference between “ALARMS” and “INTERLOCKS”. Analog alarms will be created and configured in the HMI in order to utilize the alarm features and capabilities of the HMI GE Proficy software ( as stated above). However, interlocks ( discrete or analog), which are intended to stop equipment regardless of Operator interaction, will not be configured through the HMI. Interlocks will be configured and controlled in the PLC or hard -wired directly to the equipment being controlled. This allows the interlocks to still operate properly even if there is a loss of communication between the PLC and HMI.

If there is an active interlock (equipment is stopped/ interlocked) then the PLC will communicate an interlocked state bit to the HMI for display.

PBU2091. 01L 6 June 2016

If there is an analog value that creates an interlock when it reaches a certain value AND needs to be configurable by Operators, then that value is operator adjustable on the HMI and sent to the PLC.

2.7 Trends

All specified analog and digital values will be trended in GE Proficy . This includes levels, flows, totalized flows, valve positions, temperatures, pressures, analyzer values, runtimes, equipment statuses and

Proportional Integral Derivative ( PID ) parameters. Trend data shall be retained as long as possible sometimes up to 18 months), based on server storage size and the level of importance of the information.

2.7.1 Value Recording Intervals

The table below indicates the time intervals at which data can be trended . These intervals may be changed as needed depending on sever storage size and level of importance of information.

Table 2 -3. Standard Recording Intervals

Value Interval

Speed 10s

Position 10s

Analytical 10s

Level 10s

Pressure 10s

Flow 10s

Discrete Change of State (event based)

PBU2091. 01L 7 June 2016

2.8 Tag Creation

2.8.1 Analog Tag

Table 2 -4. Analog Tag Parameters

Name /Field Input

Variable Tag Name Tag name using Software Tag Format Guidelines convention

Cluster Name The cluster used by the Palm Bay Utilities Department, PBUD

I/O Device Name Name of the device entered in I/O Device Form

Address Address of the tag

Data Type Analog values shall be type REAL in the HMI

Raw Zero Scale The zero scale of the PLC tag

Raw Full Scale The full scale of the PLC tag

Eng Zero Scale Since scaling in the PLC, this number is the same as Raw Zero Scale

Eng Full Scale Since scaling in the PLC, this number is the same as Raw Full Scale

Eng Units One of the standard units as applicable

Format The default format for display of the tag, can be overwritten on graphic display

Deadband N/A. This field will be left blank.

Comment An informative and brief comment explaini ng the nature of the tag

PBU2091. 01L 8 June 2016

2.8.2 Digital Tag

Digital tags will follow similar guidelines to analog tags. However, scaling parameters, engineering units, and format will be excluded.

Table 2 -5. Digital Tag Parameters

Name /Field Input

Variable Tag Name Tag name using Software Tag Format Guidelines convention

Cluster Name The cluster used by the Palm Bay Utilities Department, PBUD

I/O Device Name Name of the device entered in I/O Device Form

Address Address of the tag

Data Type DIGITAL

Raw Zero Scale This field will be left blank.

Raw Full Scale This field will be left blank.

Eng Zero Scale This field will be left blank.

Eng Full Scale This field will be left blank.

Eng Units This field will be left blank.

Format This field will be left blank.

Deadband This field will be left blank.

Comment An informative and brief comment explaining the nature of the tag

PBU2091. 01L 9 June 2016

2.8.3 Trend Tag

Table 2 -6. Trend Tag Parameters

Name /Field Input

Trend Tag Name Tag name using Software Tag Format Guidelines convention

Cluster Name The cluster used by the Palm Bay Utilities Department, PBUD

Expression Tag variable to be trended will be entered here

Trigger Not used. This field will be left blank

Sample Period 10 second sample period will be normally selected. 10s

Type Periodic trending will be selected. TRN_ PERIODIC

File Name Not used. This field will be left blank

Storage Method Not used. This field will be left blank

No. Files Not used. This field will be left blank

Time 00:00:00

Period 1st

Comment An informative and brief comment explaining the nature of the tag

PBU2091. 01L 10 June 2016

2.8.4 Analog Alarm Tag

Table 2 -7. Analog Alarm Tag Parameters

Name /Field Input

Alarm Tag Name Tag name using Software Tag Format Guidelines convention

Cluster Name The cluster used by the Palm Bay Utilities Department, PBUD

Alarm Name

The name of the physical device associated with the alarm ( maximum of 79 characters). This property is optional, GE Proficy only uses it when details of the alarm are displayed on the screen or logged to a device.

Variable Tag The analog variable ( tag) that triggers the alarm ( maximum of 79 characters).

Setpoint An analog variable tag or base value that determines if a deviation alarm is to be triggered. This property is optional. If you do not specify a setpoint, it will default to 0 (zero).

High High

The value used as the triggering condition for a high high alarm (maximum of 10 characters). The high high alarm becomes active when the value of the variable tag exceeds this value for the duration of the high high delay period.

High High Delay The delay period for High High Alarms. The alarm will only activate if its triggering condition is met for the duration of this period.

High

The value used as the triggering condition for a high alarm (maximum of 10 characters). The high alarm becomes active when the value of the variable tag exceeds this value for the duration of the high delay period.

High Delay The delay period for High Alarms. The alarm will only activate if its triggering condition is met for the duration of this period.

Low

The value used as the triggering condition for a Low Alarm (maximum of 10 characters). A Low

Alarm becomes active when the value of the Variable Tag drops below this value and remains there for the duration of the Low Delay period.

Low Delay The delay period for Low Alarms. The alarm will only activate if its triggering condition is met for the duration of this period.

Low Low

The value used as the triggering condition for a Low Low Alarm (maximum of 10 characters). A Low

Low Alarm becomes active when the value of the Variable Tag drops below this value and remains there for the duration of the Low Low Delay period.

Low Low Delay The delay period for Low Low Alarms. The alarm will only activate if its triggering condition is met for the duration of this period.

Deviation

The value used as the triggering condition for a Deviation Alarm ( maximum of 10 characters). A

Deviation Alarm is activated when the value of the Variable Tag remains outside the deviation range determi ned by the Setpoint) for the duration of the Deviation Delay period. This property is optional.

If you do not specify a deviation, no Deviation Alarm is activated.

Rate

By dividing this value by the alarm period, GE Proficy determines the “maximum rate” at which the value of the variable tag can change (maximum of 10 characters). At each Scan Time, GE Proficy checks the value of the tag. If its rate of change is greater than the maximum rate, a Rate of Change

Alarm is triggered.

Deadband The value that Variable Tag must return to before the Deviation Alarm becomes inactive maximum of 10 characters).

Format

The display format of the value (of the variable) when it is displayed on a graphics page, written to a file or passed to a function ( that expects a string) ( maximum of 10 characters). This property is optional. If you do not specify a format, the format defaults to the format specified for Variable tag.

PBU2091. 01L 11 June 2016

Category The alarm category number or label (maximum of 10 characters). This property is optional. If you do not specify a category, the alarm defaults to Category 0.

Help

The name of the graphics page that displays when the AlarmHelp() function is called (maximum of

64 characters). This property is optional. If you do not specify a help page, no actio n occurs when the AlarmHelp() function is called.

Comment Any useful comment ( maximum of 48 characters).

PBU2091. 01L 12 June 2016

2.8.5 Digital Alarm Tag

Table 2 -8. Digital Alarm Tag Parameters

Name /Field Input

Alarm Tag

Name

The name of the alarm ( maximum of 79 characters). The name must be unique to the cluster. Tag name using HMI standard tag naming convention

Cluster Name The cluster used by the Palm Bay Utilities Department, PBUD

Alarm Name The name of the physical device associated with the alarm ( maximum of 79 characters). Optional. GE

Proficy only uses it when details of the alarm are displayed on the screen or logged to a device.

Alarm Desc The description of the alarm (maximum of 254 characters). This can include variable data. Optional. GE

Proficy only uses it when details of the alarm are displayed on the screen or logged to a device.

Variable Tag A The digital variables ( tags) that trigger the alarm (maximum of 79 characters). You can configure digital alarms to activate based on the state of one or two digital variables. If you only use one variable to trigger the alarm, use the Var Tag A field. Variable Tag B

Category Alarm category number or label (maximum of 16 characters). This property is optional. Default

Category 0.

Help The alarm category number or label (maximum of 16 characters). This property is optional. If you do not specify a category, the alarm defaults to Category 0.

Delay

The alarm delay period. A digital alarm becomes active when the state of the triggering condition remains true for the duration of the delay period. The active alarm has an ON time of when the state became true. This property is optional.

Comment Any useful comment ( maximum of 48 characters).

PBU2091. 01L 13 June 2016

3.0 GRAPHICS

3.1 Definition

Graphics are the visual representation of the SCADA system to the user. Graphics include the representation of individual pieces of equipment and how they are connected in the treatment process.

Graphics also include the display of system values ( levels, flows, pressures, etc.) and equipment status running, alarm, etc.). In addition, the system navigation ( how a user moves from one display page to another) is part of the graphics.

3.2 Graphic Display Character istics

The OWS is intended to be a graphical representation of the current state of the plant. Using a variety of graphical objects and color -coding, an operator can instantly assess the current state of the plant they are monitoring. The features of the graphics screens enable a user -friendly interface to be both aesthetically pleasing and functional, but an emphasis will be placed on transferring the current logic states in the PLC to a human operator. Where possible, depiction of systems in “3d” will be used for aesthetic reasons. But, when needed or the display area is not available for such aesthetics, a “2d” approach will be used to display process operation, equipment status, and function. Graphics are developed and displayed using 1080p screen resolution and 65,536 colors. Objects that do not have I/O associated with them, and are not primary to the process or philosophy of the control theory, are not displayed in the graphics. Equipment will be identified to the level required by operations; this is to eliminate wasted graphical display space to label equipment already known to operations staff.

Analog values are to be depicted textually as a standard; for example, tank levels. Graphical depictions of gauges are not used where graphic space is limited; text will be the preferred method of representation. When space is available or when it is believed to be an asset to the interface, analog values will also be displayed as part of fill animation. To use the aforementioned example, it would be appropriate to show a depiction of a tank and have fill animation show its current level, as well as a text readout of the level. Units will be displayed adjacent to the text readout. Where several related analog variables are located on a single display , they should be displayed as a group; for example, process value and setpoint on a PID controller.

Process graphics will contain an abbreviated alarm summary listing recent system or plant -wide alarm occurrences. It will be possible for more alarms to be active than can be displayed on the abbreviated alarm summary. Therefore, an Alarm Summary graphic has been created to allow all of the active alarms to be displayed.

Process graphics that contain alarms will display the alarms as text located next to the piece of equipment the alarm represents or as a “lens” animation with static text. Text alarms will only be visible when the alarm state is active, and will become invisible when the alarm state is inactive. The “ lens” alarm indication will be visible at all times with the lens changing colors when the alarm is active.

3.3 Navigation

The Main page directs the user to the designated Level 1 (Plant Overview) screens. The MENU, ALARMS, and TOP PANEL screens are designated Level 1 and linked on the Main Page. On new screens a navigation bar will be available to view any child windows in the case of Level 1 pages, or parent Windows in the case of Level 2 pages. All sibling windows will also be linked in the navigation bar.

PBU2091. 01L 14 June 2016

3.4 New Screens and Levels

The following are examples of screens which have the indicated levels.

Level 1: Overview, Odor Control, Wet Wells and Pumps, Ethernet Network Communications.

Level 2: Influent, Grit Basin, Grit Handling, Sludge/ Scum and Pumps, Clarifiers .

3.5 Color Guidelines

3.5.1 Color Definitions

The color guidelines for the HMI will follow those outlined in the specifications using a RGB Color

Scheme .

Table 3 -1. HMI RGB Color Scheme

Color Red # Green # Blue #

Black 0 0 0

Blue 0 0 255

Brown 144 48 32

Cyan 0 224 224

Green on grey or adjacent to other 0 160 0

Green text on black background 0 208 0

Grey background 208 208 208

Orange 255 112 0

Purple 128 0 208

Red 255 0 0

White 255 255 255

Yellow 255 255 0

The darker green is perceived well against the grey background or next to other colors. The City prefers to use this green on symbols for pumps, motors, and the like. The lighter green is easier to perceive when reading text on a black background and the City would like to use it for any words or text that appears in that setting.

PBU2091. 01L 15 June 2016

3.5.2 Function Color Definitions

Table 3 -2. Function Color Definitions

Tag Function Inscripti on(s ) Equipment

Color

Text

Color Background indicating analog value> < none> White Black setpoint> < none> Black White manipulated value> < none> Black White

Wastewater Indicated Analog Value> < none> Blue Black

Sludge Indicated Analog Value> < none> Brown Black

Hypochlorite Indicated Analog Value> < none> Orange Black

ORP Indicated Analog Value> < none> Orange Black

NaOH Indicated Analog Value> < none> Purple Black pH Indicated Analog Value> < none> Purple Black valve/ gate in transit> INTRANSIT Yellow

LEAD LEAD Cyan Black

LAG LAG Purple Black

ON ON Green

OFF OFF Red

OPENED OPENED Green Green

CLOSED CLOSED Red Red

RUNNING RUNNING Green Green

RUNNING < with alarm> RUNNING Green/ White

Flashing Green

STOPPED STOPPED Red Red

STOPPED < with alarm> STOPPED Red/ White

Flashing Red

FAIL FAIL Red Red

HIGH HIGH Red Red

LOW LOW Red Red

HAND HAND Yellow Black

LOCAL LOCAL Yellow Black

OUT OF SERVICE OOS Red Black

COMP COMP Green Black

MANUAL MANUAL Yellow Black

AUTO AUTO Cyan Black

3.6 Faceplates (“ Supergenies”)

When certain equipment is selected, a popup faceplate (“Supergenie” in GE Proficy terms) will appear that gives more specific information related to the equipment as well as opportunity for Operator control.

Security can be assigned to certain control operations so that only an Operator with sufficient permissions will be able to make changes.

PBU2091. 01L 16 June 2016

3.6.1 VFD

The VFD faceplate shows whether the equipment is in LOCAL or COMP ( Computer) at the field control panel and if it is in

MANUAL or AUTO at the HMI. It allows the

Operator to set the manual speed setpoint and indicates the actual speed feedback, runtime hours, and status. When in COMP at the field control panel, the Operator can select AUTO/MANUAL at the HMI. When in

MANUAL, then the Operator can select to

START or STOP the equipment. If applicable, a PID Control button allows the operator to view the PID settings.

3.6.2 Analog Valve

The analog valve faceplate shows whether the equipment is in LOCAL or COMP

Computer) at the field control panel and if it is in MANUAL or AUTO at the HMI. It allows the operator to set the manual position setpoint and indicates the actual position feedback. When in COMP and MANUAL, the

Operator can set the manual position setpoint. If applicable, a PID Control button allows the Operator to view the PID settings.

PBU2091. 01L 17 June 2016

3.6.3 PID

The PID faceplate displays applicable information for tuning of a PID a loop. The Process Value (PV), Setpoint ( SP), and Controlled Variable ( Output, CV) are trended on the graph. The Setpoint can be adjusted with a slider ( yellow slider on the right hand side of faceplate). An Operator with sufficient privileges can adjust the tuning parameters ( Gain, Integral or Reset Time, and Derivative Time).

PBU2091. 01L 18 June 2016

3.6.4 Discrete Motor

The discrete motor faceplate shows whether the equipment is in LOCAL or

COMP ( Computer) at the field control panel and if it is in MANUAL or AUTO at the HMI. It indicates the runtime hours and status ( Running, Off, Fail to Start/Stop, etc.). When in COMP at the field control panel, the Operator can select AUTO or

MANUAL. If it is in MANUAL they can select to start or stop the equipment.

3.6.5 Discrete Valve/ Gate

The discrete valve faceplate shows whether the equipment is in LOCAL or COMP

Computer) at the field control panel and if it is in MANUAL or AUTO at the HMI. It indicates the position status ( Open , Close, etc.). When in COMP at the field control panel, the Operator can select AUTO or

MANUAL. If is in MANUAL they can select to open or close the valve or gate.

PBU2091. 01L 19 June 2016

3.6.6 Analog

The analog faceplate shows the trended value along with high high, high , low and low -low alarm levels.

A bar graph on the side shows the current value with the alarm levels for an easy to read graphical representation. Operators can adjust the various alarm levels by selecting them and entering the desired value.

PBU2091. 01L 20 June 2016

3.6.7 Flow Meter

The flow meter faceplate is similar to the analog faceplate except it adds a totalized flow at the bottom, which can be reset.

PBU2091. 01L 21 June 2016

3.6.8 Data Entry

Clicking on an analog setpoint brings up a keypad for data entry. The type and format of the data entry format will be determined by the calling function or Supergenie.

3.7 Use of Genies and Supergenies

The flexibility and modularity of Genies and Supergenies shall be utilized to ease development and allow for future expansion of the GE Proficy project. In order to leverage the full potential of these tools, the Software Tag Format Standard conventions must be strictly followed.

3.8 Tool Tips and Help Pages

Tool tips will be available on buttons and setpoints to indicate their function. A help button will appear on pages that will show a popup page that describes the function of the current page.

PBU2091. 01L 22 June 2016

4.0 INDICATIONS AND SCAN TIMES

4.1 Definition

Indications are status information for the operator and are used to show the current control mode of the equipment ( local/remote, manual/auto) as well as if there are any alarms. Scan Times are used to set how often alarms are processed and graphical displays updated with status changes in the process system. These scan times are usually set to update once per second, but can be adjusted if necessary .

4.2 Equipment MODE Naming Convention ( LOCAL -OOS -COMP)

The state of the device/equipment mode is displayed on the SCADA HMI as “LOCAL”, “ OOS”, MANUAL”, or “AUTO”.

4.2.1 LOCAL

This indicates that a field device is controlled ‘locally’ at the field device via start/stop or open/close pushbuttons or local device -mounted interface module (VFD ‘HIM’ module) in the field. The device’s mode control switch (i.e. HOA, HA, LOR, LR, LOC, LC, etc.) would be in the ‘H’ (Hand) or ‘L’ (LOCAL) position. When the device is in this mode, then there is NO control capability from the PLC for interlocks, starting/stopping, etc.

4.2.2 OOS ( Out -of -Service)

Status for equipment identifies any or all of the following:

Motor Disconnect OPEN

Power to Panel OFF

HOA switch in OFF Position

4.2.3 COMP ( Computer)

This indicates that a device is controlled via the PLC. The device’s mode control switch (i.e. HOA, HA, LOR, LR, LOC, LC, etc.) would be in the ‘A’ (Auto), ‘R’ (REMOTE), or ‘C’ (Computer) position.When the device is in this mode, then the PLC has control and the PLC/HMI control of the device is then either in

MANUAL or AUTO mode.

A pushbutton on the HMI screen allows the operator to ‘toggle’ between AUTO and MANUAL modes only when the devices HOA switch is in the COMP position)

4.2.4 MANUAL

The use of the term MANUAL is very specific, meaning the device’ s HOA switch is in the ‘A’ position

AND the PLC mode is also in MANUAL for this device/ equipment. MANUAL mode means that an

Operator has the capability ( from the HMI local SCADA system) to command a device to start/stop, open/ close, etc.

4.2.5 AUTO

The use of the term AUTO is very specific, meaning the device’ s HOA switch is in the ‘A’ position AND the PLC mode is also in AUTO for this device/ equipment. AUTO mode means that the PLC has full control of whether the equipment/ device starts/ stops, opens/ closes, etc. When in AUTO mode, then

PBU2091. 01L 23 June 2016 control of the device is entirely through the PLC logic. A Plant Operator cannot control the device in this mode, except for set -points of PID loops, limits, etc. In order for an Operator to take control of the device/equipment, then the Operator must first put the device into MANUAL mode.

4.3 Communication Failures

The communication between the PLC and HMI will be constantly monitored. Indications on the HMI

Communication screen as well as HMI alarms are designed to alert Operators to any failures.

4.4 Alarm Scan Time

The “[ Alarm] ScanTime” is located in the Citect. ini file. This parameter determines the rate at which alarms are scanned and processed. A value of 500 (the default value) indicates that GE Proficy tries to process the alarms every 500ms. However, if GE Proficy cannot read all the alarm data from the I/O device within 500ms, the alarms are processed at a slower rate. For example, if it takes 800ms to read all the alarm data from the I/O device, GE Proficy processes the alarms every 800ms.

If the alarm scan time is increased, the Alarms Server uses less CPU (because it does not need to process the alarm records as often). The amount of data read from the I/O device is also reduced so that other processes (Trends, Reports, and the current page) get their I/O device data more quickly.

The City shall be responsible for the configuration of the Alarm Server scan timing.

4.5 Page Scan Times

The Page Scan Time defines how often the graphics page is updated at runtime. The Page scan time also determines the rate of execution of the While page shown events (i.e. the command( s) which are executed while the page is displayed at runtime).

Select the “Default” check box to use the default page scan time (as set using the [Page] ScanTime parameter in Citect.ini); otherwise, leave it blank, and enter (or select) another value in the field below.

For example, if a page scan time of 200 milliseconds is entered, GE Proficy will try to update the page every 200 milliseconds, and any While page shown events are executed every 200 milliseconds.

Pages scan times shall be set as “Default”.

PBU2091. 01L 24 June 2016

5.0 SECURITY

5.1 User Permissions

User permissions can protect sensitive pieces of equipment from being controlled in a manner not specified by the City (i.e. PID loop parameters). The City will determine all user roles and privileges to ensure proper function of the current GE Proficy program with security in place for values in the system.

6.0 REPORTS

6.1 Backgr ound

The City will specify the types of reports needed for the system. Typical reports include daily and monthly flow totals and chemical application. MIN, MAX and AVERAGE aggregate functions can be performed on most reported values.

6.2 Logged Values

As noted in the trending section, trend tags will be logged by the Historian server in specified intervals with a specified deadband to avoid logging repeated data. The trend tags will allow for backfilling in case of a failure with the Historian server. City Personnel will configure the Historian for logging these values.

6.3 Report Format

Report formats shall remain consistent throughout the specified reports with similar parameter names and color schemes.

6.4 Report Scheduling

The Historian server can be set up to generate reports through the interface but can also create reports at scheduled intervals and store them at a configured file location. The City will determine the reports that shall be automatically generated and the storage location of those reports. The naming convention of the stored report files will also be determined by the City.

7.0 SOFTWARE VERSION

New applications will be developed and implemented in the version and service pack of GE Proficy

SCADA software as determined by the City prior to the com mencement of each project.

PBU2091. 01L 25 June 2016

8.0 PROCEDURES REVISION HISTORY

8.1 General

Revisions to the SCADA Software, Hardware & Standards Procedures shall be documented in this section.

8.2 Revision History

June 2016 – SCADA Software, Hardware & Standards Procedures document created.

PBU2091. 01L 26 June 2016

APPENDIX A – SAMPLE SCADA SCREENS

T

Y!

CD w O' T m

O W mC) W O yZa - Im v n 0 np m; 0y y m f0 n (n (n - n ( n E E,<

0. a Q y

NNIn 3- 0 frtD s( j) m N O

0000 3

f) ( f) U) U) O n n n n cn

N m m

ND

rt a O

Zmm

D

ON W m C

Ol l0 { ny 15 1y 3 g°

W T c r o W sj-c yA mN m v O vA acW - Iv W N v

Fo 3 r C

Im3v pm IVcO 1n m2 ry p

NA:,, 4

At g r0

Op mwp DO xOi TOi {' 0 NA N

Tm h N

W op T3vlw o A rNn o 00

O O O r rt s m

3c -

CDN

1Z m 3n o o 0 3D m( AD0Oj T: a rN

CD

3Z

A- L

O O

A 7Z o ni a 0

T+ D = c 3 10

A oA m in w is 3 w

M

D

3 D 3

D

WT

0 0 O

3 m N

N0 chi m

Zcd N jp 3 w

O yv00 C

OW ZpO 3 2

0,C O n

O o W ( D O A j

N Ln ' N Jr C m

N m " n v - nG) a - Un m _ rt Co p 9n r•

NZ

0 o MR o N

DDT' ' am 0) 1 cA p 3Z O o Zm 3 Z MG) m- n

@ . rE j pl D ON NO

6N NO V -

n< DO mN 3

OMET N aZ CT( D GM Zm

1M, 3 OF

0mn 0 Etl1 Z

Ali cnm yO m W cn U)

0l D j- Do (/1 ( A zM

0 nO r m c D m n 0oM CD ( A rt

A v- L

CD

ro ( n= A mV W o i i

T<0 N ( D

N° 0 CD A TO

c ' p m m ( n rt m nNT OmA

O) n N T W

QO

r nr! t0 ap n<0 aO T

O® aN o=C n3 2

O N A 0 nu

0 0

T

W ` O ADO CD N

iccO a m m - i 1- 1 ' - n c c m W m

W91 m w WOAD n A Ca w m

0) CL W r W nO < kD 1m Z fl-w c7 C ItO O n r'

0- 3 acn o- L T-?

cn W a-Lt m N cn t0

100 Tw mNp m0 mp j 3 n

T

Q tt a, N ry: ONO NVT Al

N Z

TO

CD

0N V!

T//

VJ

Z

V V

CD

m l(.09,ni m0 -L on-L m mN mO 0( DID 0 3

9' goo W w N w C) C nC p n

O Ip N ( li v ui 7 n0 m c

ID

o my co

O

TO

p a Ao cn mO NN c"=DN CD o C

Np n fA fA 3 ci 8 to— p N m o mrn o c=ip

C) m mV

LL D

0) m0 A

N Q o

CS

C3 p ci N w

Q= fD e Z

I

C _ I Fldufe Rio Process • r _ I & High Service Pump

8uilang F re Generalel

8 Fuel Storage I _ t - Future- F — — — — ffil, Future

TSr — — - -i— — — Cc=_gasnizr . 4 i FutnreFl-_

I? Conlact1 BasinI H%F Cnlonle Inl I I . .. . -

I

1 i furtire8ut hFn SUxac

I --- •

EEP INJECTION ® ® •

MONITORING

C

MAI

r

N

O H

06 0

LL

r

LL

N l0 r...

U) w

F-

Z J Q

LL

W W

F- W j Q

0 0 Z W J W m LL

H IX

Q

V]

0 W z Fj a J

LL

w X i- w

Q

0 0 z w

J LV

m LL

H 0' d

CL

C. 4 TF'

0 _

N

T p W Z H Q J

LL

W W f- W a

0 0Z LLj LV

J LV

Co LL

H

E

Tn N

O m m m r r r r r r

W N rn

0o o o a Z

C

CD

i m O 3 N m CO Co C C co

4t

C G n m3 T O

Tj mm v

I

II

II JI J ll 1 J1J JI) 1111i11J1 ° li°tit° ti arr

JII III J J, / iJJ JJI J1, 1111111) I tit a r l ta+ rlt i'' r co

QL

I C-

R

VVVVV • VV'' JJ

co CD a

I I I J IIII JIIII ll l ilii lllrrll111°,- I J J II J IJI Ili li > > 1 1°

JJII I JJI % JII J lllli j 1 11 1111111'

1 °°° Ir, 1,'

Jl JJ IIII/ JJJII fill! Ali l ill i))

i) )111 I J J JJ JJJ JI IIfill li it lr)>>)

I llll a0I J J J J III JJ Il !III

1 li JJ f 1 J 1 1)

1111 ' 3IIII J

Jl JIJI llI 1 i1iJi ifiti)) ) 1111 °'; yI J J J J III JII lJlll liiiii Jirtij j

l) 11 , I JJ

I I III J JII J Jl 1 ili i iij s) llil

11N O i N

0 O cQ O N ail v N - J Qp lI

N N A T fD fn i ui n Vl fn N

II J

I JJJ JJJJ

Ill ii1 i! J1J II Il JJ 1 a

III II lIl 111 iiJ JJ1 JI J III I J 11 i

JI lllll' IJJ JJ1 11 ' 111111

1 11 w o' àp 6 T ' V

TAD

1! lrrrrrrrrr rrrJrr 4 I 1 ! !! rr rrr I Ir

J ! l rrlrrrrrr J'

I o m r!!

rr rr rCD a rrr r i/ Ir, 1' hr° Ir, I

IJI JJJJJI11jI !!! !! rrrrrrrrr , 1J lilt, 1111,,/ 1, JJ11/,, 1l it // III J % I i J J lI 1111 j !!! r1 r rrrrJ }

I r, t / I l /

I IlI ll J JJI J 1 rll rrrlrrr! . C

CDo v +, V' s

N O m N O n 00 v Q> N A l

CD

cn

S ° N DCn l

J I I/ I III llI j >>!> I

JJ rllrlr!

lIl III I >> l JJ I!

J

J r1 i rr l /

II J III IIJJ J J

lll CD n(

4;I N jCf) N NQi cn N soTo A' m N 03 O = N

C) C O T N

T /-

1 T' I G) CD

J

J JI itI1J Ill j JJ1J JrJJI 1 llrj J1 / l1 III J1I 1 1t t I ;

E' nr1i! IlI lI J IlI JJJ1 . rrr ttt/ rl!!

rlrrlrrr r rJJJ, rf1{f,', 1lrr rrr r',,°, lilt, rL

I j I J I l l I

11 r! !1! rrr , J I J J/ l

I I1j/ 111 jJ1 >> 1 1111 1111 11, rr !

JJJi,,;' r J

J I f l 111J 1111! tr rrrrr;: 0 y Ij j jjjIr 1 11! filar rJrrr I J

J J l J J II j1II 1 Jj1r1111!!lirrr irr , cn c 4

CD 0

a o O $'

CA) a

D

0 J0 n yp

P kw 0.

o kk 2 @ f= 0 QCA J o= k CL

CL 3 13Z3« 7

qk3 R # w0iEm3 c c z 0 7 2

O n E

SOU su E g k 2

0 BCL

qi[L m o _._. W o

CO)

cO G

WT

C bo D co

N a a

4t y

C o 0

CO) v

N a' Q

R n

O ear

O O rL

ID 0

C C C 0 M.

ca fD

C) r c Q1 CD

A 03

4 , re i

H

0-

CD

na:A F5 P

CDD. cu "a dL

9_ 3

MI

i

IIIIII IIIIIIIIIIIIIIIIIII

O

CA

D

CL

v n

1+

C

Z W

O 0 C - 1 N n

Q- rt

II IIIIIIIIIIIIIIIIIIIIIIII

OOP,

D D

A ' _

Q rL

AMWM cn v - C. m

2 2 c O O oD D w

O O ( D

C.

r V fnn llrinn anlirlrplu uuplu ., II ' dd r ii illlIIIIIIIIII r 14 n i

N r r z s

3 u

L 0 m o0 r m

Mz Ov Zz vvD Q°

W

Z M i I]

W n

R 01 a Vn a00 = 00

C-

M

Mo o m M z z m

Al

3 zi l; u

G) m c i fittt ftitti`ff t' if ifti t ft Ìt Ott tfttt, fftt ftiifi ftttii`' fftlf` tfj i' tttf

4 ' afti' fi t

1i

IL

i # s