City of Orillia

City of Orillia

SCADA System HMI Programming Standard

Water and Wastewater SCADA System

December 20, 2018 VERSION 1.1 - Final

City of Orillia SCADA System HMI Programming Standard December 2018

Table of Contents

1.0 GENERAL ............................................................................................................... 1

1.1 GLOSSARY ..................................................................................................................... 1 1.2 ABBREVIATIONS ............................................................................................................ 1 1.3 HMI SYSTEM UPDATES....................................................................................................... 2

2.0 HMI APPLICATION ................................................................................................. 2

2.1 PROFICY IFIX .................................................................................................................. 2 2.2 INSTALLATION DEFAULTS .................................................................................................... 2

2.2.1 Application Settings (SCU) ....................................................................................... 2 2.2.1.1 Path Structure ............................................................................................................... 3 2.2.1.2 Alarm Services .............................................................................................................. 3 2.2.1.3 Security ......................................................................................................................... 4 2.2.1.4 Tasks.............................................................................................................................. 4 2.2.1.5 Alarm Area Database ................................................................................................... 5

2.3 SYSTEM CONFIGURATION .................................................................................................... 5 2.3.1 User-Defined Variables ............................................................................................ 5 2.3.2 Visual Basic Scripting ................................................................................................ 5

2.4 SUPPORTING INSTALLS ........................................................................................................ 5 2.4.1 IGS Server .................................................................................................................. 5 2.4.2 iFIX SIMS.................................................................................................................... 5 2.4.3 Proficy Historian ....................................................................................................... 5 2.4.4 WIN911 ...................................................................................................................... 5

2.5 SECURITY .......................................................................................................................... 5 2.6 HISTORICAL LOGGING......................................................................................................... 5

3.0 DATABASE TAG STRUCTURE.................................................................................. 6

3.1 ANALOG TAGS .................................................................................................................. 7 3.2 DIGITAL TAGS.................................................................................................................... 7

3.2.1 Status Tags ................................................................................................................ 8 3.2.2 Alarm Tags ................................................................................................................ 9

4.0 GRAPHICS ............................................................................................................ 10

4.1 COLOURS ........................................................................................................................ 10 4.1.1 Device Status & Icon Alarming .............................................................................. 10

4.2 MAIN OVERVIEW SCREEN ................................................................................................. 12 4.3 HEADER AND NAVIGATION BANNER................................................................................... 12

4.3.1 Process Buttons ....................................................................................................... 12 4.3.2 Trends / Statistics Button ........................................................................................ 12 4.3.3 Alarm Button .......................................................................................................... 13 4.3.4 Additional Buttons and Features .......................................................................... 13

4.4 SYSTEM DISPLAY SECTION................................................................................................. 13 4.4.1 Process Display Screens........................................................................................... 13 4.4.2 Pop-Ups ................................................................................................................... 14

4.4.2.1 Analog Device Pop-up................................................................................................ 14 4.4.2.2 Maintain Commanded Valve Pop-up ........................................................................ 15 4.4.2.3 Analog Commanded Valve Pop-up ........................................................................... 16 4.4.2.4 Maintain Commanded Motor Pop-up ....................................................................... 17 4.4.2.5 VFD Commanded Motor Pop-up ............................................................................... 18

5.0 ALARMS ............................................................................................................... 19

5.1 ALARM AREAS................................................................................................................. 19 5.2 ALARM SUMMARY SCREEN ............................................................................................... 19

- i -


5.3 ALARM ACKNOWLEDGEMENT............................................................................................ 20 5.3.1 Alarm Summary Colours......................................................................................... 20 5.3.2 Banner Summary Colours ....................................................................................... 21

6.0 TRENDING ............................................................................................................ 21

6.1 TREND SCREEN ................................................................................................................ 21

7.0 SECURITY ............................................................................................................. 22

8.0 NETWORK AND COMMUNICATIONS ................................................................... 23

9.0 SUBMITTALS ........................................................................................................ 31

10.0 OIT DEVELOPMENT.............................................................................................. 31

11.0 TEST DOCUMENTATION ...................................................................................... 32

List of Figures

Figure 1 – Proficy iFIX Path Configuration ................................................................................... 3 Figure 2 – Proficy iFIX Alarm Queue Configuration .................................................................... 4 Figure 3 – Proficy iFIX Task Configuration ................................................................................... 4 Figure 4 – Proficy iFIX Analog Input Tag ...................................................................................... 7 Figure 5 – Proficy iFIX Digital Input Tag ....................................................................................... 8 Figure 6 – Proficy iFIX Digital Alarm Tag ..................................................................................... 9 Figure 7 - Pump Colour Legend................................................................................................... 10 Figure 8 - Valve Colour Legend ................................................................................................... 11 Figure 9 - Analog Colour Legend ................................................................................................ 11 Figure 10 – Main Overview Screen ............................................................................................. 12 Figure 11 – Process Screen Example – Low Lift Pumps .............................................................. 13 Figure 12 – Analog Device Pop-up.............................................................................................. 14 Figure 13 – Maintain Commanded Valve Pop-up ...................................................................... 15 Figure 14 – Analog Commanded Valve Pop-up ......................................................................... 16 Figure 15 – Maintain Commanded Motor Pop-up .................................................................... 17 Figure 16 – VFD Commanded Motor Pop-up ............................................................................. 18 Figure 17 – Alarm Summary Screen ............................................................................................ 20 Figure 18 - Alarm Summary Colours ........................................................................................... 20 Figure 19 - Alarm Banner Colours ............................................................................................... 21 Figure 20 – Trend Screen ............................................................................................................. 22 Figure 21 – IGS Driver Configuration – Channel Setup ............................................................. 23 Figure 22 – IGS Driver Configuration – Channel Setup ............................................................. 24 Figure 23 – IGS Driver Configuration – Channel Setup ............................................................. 25 Figure 24 – IGS Driver Configuration – Channel Setup ............................................................. 26 Figure 25 – IGS Driver Configuration – Device Setup ................................................................ 27 Figure 26 – IGS Driver Configuration – Device Setup ................................................................ 28 Figure 27 – IGS Driver Configuration – Device Setup ................................................................ 29 Figure 28 – IGS Driver Configuration – Device Setup ................................................................ 30 Figure 29 – IGS Driver Configuration .......................................................................................... 31

- ii -


Revision History

Version By Comments Date 1.0 Eramosa Engineering Inc. Draft – Initial release for review 20/06/18 1.1 Eramosa Engineering Inc. Final – Updated with comments

from the City. 20/12/18

- iii -


1.0 GENERAL

The City of Orillia (The City) has standardized on the use of GE Proficy s iFIX version 5.5 software for the SCADA (Supervisory Control and Data Acquisition) development and runtime environments. From time to time the City may upgrade the version of iFIX which does not relieve the intention of this standard should a feature change in a new version. The SCADA system provides operators with a means of monitoring and controlling plant operations.

This document is a guideline to the structure and documentation of process displays. The purpose of this document and standards in general is to establish guidelines for a consistent approach to programming. The consistency of development will enable:

i. Maximum re-use of programs that will provide consistency across all City facilities; ii. Programming by consultants and system integrators;

iii. Reduce time to troubleshoot programs; and, iv. More confidence and usability of operator workstations.

Display screens are to provide the operator with the key process information without having a screen that is ‘cluttered . This will facilitate operator response to emergency situations where the key information can be viewed easily.

1.1 GLOSSARY

HMI – Human Machine Interface

A human machine interface (HMI) is typically a graphic application that resides on an industrial computer, operator interface terminal, and laptop or computer tower. The application is capable of interacting with the programmable logic controller with the result of process automation, equipment control, alarming, data collection and data display. For the City of Orillia Water and Wastewater System, the HMI is specifically referring to the system wide SCADA that is operated in the main control centers using GE iFIX.

RPU or PAC or PLC – Remote Processing Unit Programmable Automation Controller or Programmable Logic Controller

A remote processing unit or programmable logic controller is a digital computer used for automation of industrial processes. Unlike general-purpose computers, the RPU or PLC is designed for multiple input and output arrangements, extended temperature ranges, immunity to electrical noise, and resistance to vibration and impact.

OIT – Operator Interface Terminal

An operator interface terminal is a specific computer machine which generally only has use as a human machine interface terminal. The operator interface terminal generally takes the form of a touch screen computer, but may have a keyboard and mouse as well. For the City of Orillia Water and Wastewater System, the OIT is considered the site specific local SCADA controls installed on a GE QuickPanel touch screen.

1.2 ABBREVIATIONS

GB Gigabyte HMI Human Machine Interface IGS Industrial Gateway Server I/O Input/Output IP Internet Protocol LAN Local Area Network MB Megabyte

- 1 -


O&M Operation and Maintenance PAC Programmable Automation Controller PLC Programmable Logic Controller SCADA Supervisory Control and Data Acquisition SIM Software Improvement Module SCU System Configuration Utility TGD Tag Group Definition VB Visual Basic VFD Variable Frequency Drive

1.3 HMI System Updates

The City’s standard usage for graphics, tagging, configuration, and scripting is to be used for all projects. The City currently has separate applications for the Water Filtration Plant and Wastewater Treatment Centre. Responsibilities of any party performing programming updates to the HMI system at any City facility include but are not limited to the following;

i. Obtain permission from the City including the operation supervisor before any modifications are made;

ii. Complete updates using development licenses owned by the system integrator / programmer;

iii. Adhere to the standards as documented and contained within the application; iv. Test the modifications whenever possible offline from the main system prior to

deployment on the City’s live system; v. Distribute the application for graphics, tags, and other updates to all servers and

workstations; vi. Update the historian with new tags where applicable; and, vii. Update the MS-Excel based reports where applicable.

2.0 HMI APPLICATION

2.1 PROFICY iFIX

The City has standardized on the use of GE s Proficy iFIX software as their Human Machine Interface (HMI). The HMI is the software that graphically displays data provided by the PLCs in the network. It does not typically automatically control any of the process directly, but rather it serves as a point of access for operation and human interaction with the system. The process will still function without the HMI running as all control is located in the PLC/RPU programming. The HMI is required for monitoring/alarming and response to changes in the system.

The release version will change over the lifespan of this standard. However at the initial release of the standard the current Proficy iFIX release is version 5.8, and is the version referred to in this document.

2.2 Installation Defaults

2.2.1 Application Settings (SCU)

The System Configuration Utility (SCU) is used to configure iFIX program settings such as program and file location, network configuration, alarming, database and I/O driver startup, and external program execution.

- 2 -


2.2.1.1 Path Structure

When selecting the paths, ensure proper layout as defined below in Figure 1. The file structure organizes the paths into System Files, and HMI Files.

For the Base path, accept the default destination C:\Program Files (x86)\Proficy\Proficy iFIX folder for the destination of the HMI program files.

Figure 1 --- Proficy iFIX Path Configuration

2.2.1.2 Alarm Services

The Default Alarm Services to be enabled on SCADA nodes are listed below.

i. Alarm Summary Service; ii. Alarm History Service; iii. Alarm File Service; iv. Alarm Network Service; and, v. Alarm Startup Queue Service.

The default Alarm Queue configuration should be modified to prevent overflows of the alarm buffers on the SCADA servers. This is modified under the Queue Configuration under Advanced settings of the Alarm Configuration as shown below. Change the default value of 200 to a value twice the amount of the total alarm tags in a single database when using redundant servers. The integrator should adjust this setting as required to maximize the alarm queue whenever possible.

- 3 -


Figure 2 --- Proficy iFIX Alarm Queue Configuration

2.2.1.3 Security

Security is to be enabled on all nodes. Refer to Section 7.0 for details on the system s security configuration.

2.2.1.4 Tasks

The programs in the Task list on SCADA nodes have task lists as shown below.

Figure 3 --- Proficy iFIX Task Configuration

These programs are:

i. IOCNTRL.exe; ii. WSACTASK.exe; iii. HTC.exe; iv. IHFIXCOLLECTOR.exe; v. FIXBACKGROUNDSERVER.exe; vi. ALMUSERQ.exe (WIN911 Install Folder); and, vii. WORKSPACE.exe;

- 4 -


2.2.1.5 Alarm Area Database

Alarm Areas allow for the grouping of alarm tags into separate facilities, process areas and equipment.

2.3 System Configuration

2.3.1 User-Defined Variables

Globally defined variables are stored in the User.fxg file. The Consultants, Integrators, Programmers, etc. are not to create new variables in this file. Some screens may contain locally stored variables, and the creation and alteration of these must be approved by The City.

2.3.2 Visual Basic Scripting

Scripting is used for such things as navigation, animation, and enabling of graphic items. Refer to the template application for pre-configured scripting.

2.4 Supporting Installs

2.4.1 IGS Server

Within The City s Water and Wastewater system, the Industrial Gateway Server (IGS) is configured as the I/O server for all PLC connections in the SCADA network. Refer to Section 8.0 for details on the IGS server configuration.

2.4.2 iFIX SIMS The latest Software Improvement Modules (SIMs) and service packs (SPs) are to be installed prior to development and when issues are noted.

2.4.3 Proficy Historian

Proficy Historian is used for all historical trending and data reporting in the SCADA system.

2.4.4 WIN911

WIN911 is used for alarm callouts in the SCADA system. WIN911 will notify operations if there are any alarms present that have been configured to call out.

2.5 Security

HMI security is configured through the SCU. Database tags that are only adjustable by authorized users with predetermined access level rights have security areas assigned to those tags. The security groups to which those authorized users belong have particular security areas assigned to them allowing those users to access the tags.

2.6 Historical Logging

Logging of analog values is accomplished through the use of Proficy Historian and the historical collectors. The logging of values shall have a default interval per tag type. The City should be consulted on a project by project basis to confirm logging intervals. The following information provides a guideline for the historical logging setup;

i. Flow totals shall have a default interval of 6 hours;

- 5 -


ii. Equipment runtimes shall have a default interval of 6 hours; iii. Instantaneous instrument values shall be logged every 30 seconds; and, iv. Alarm and event data shall be logged on change of states.

3.0 DATABASE TAG STRUCTURE

The following tag types are to be used when developing the iFIX Database Tags. Analog tags are used to read and write integer or floating point values such as well levels or alarm setpoints. Digital tags are used to read and write discrete data such as start/stop values or alarm conditions.

There are limits to the number of characters available for the “Description” field of all tag types. This limit is 40 characters (including spaces). When more than 40 characters are required the description should not be truncated rather short forms of wording should be used to continue to convey the intention of the equipment description.

For the tag naming convention the City has in general consistency with each fragments identifying the site code, equipment type (major and minor) and attribute definition. Programmers should adhere to this existing convention and in the absence of a specific fragment such as for new sites and processes consult with the City for their desired preference.

- 6 -


3.1 Analog Tags

The only analog block type used in the process database is the AI tag. AA tags are not used since alarming is handled at the PLC level, not the HMI. Writable analog tags are AI tags with Output Enabled, making AR blocks unnecessary. The database does use AR blocks currently, but are not necessary going forward.

The figure below provides an example of an AI tag and the minimum required fields to be filled in under the basic tab (Description, Driver, I/O Address, Signal Conditioning, Hardware Options, Scan Settings, and Engineering Units).

Figure 4 – Proficy iFIX Analog Input Tag

3.2 Digital Tags

There are two types of digital tag in the database: DI blocks and DA blocks. The DI type is used to perform status and read/write functions, and the DA block is for alarm tags only. DI blocks with Output Enabled are used to write data to the PLC/RPU instead of using DR blocks.

- 7 -


3.2.1 Status Tags

Status tags include examples such as start and stop, running status, and manual/auto status tags. The tags requiring output to the PLC will be Output Enabled. Tags used only for status feedback will not be Output Enabled. These tags will have event messaging enabled and alarming disabled. Figure 5 below illustrates an example of a DI tag.

Figure 5 --- Proficy iFIX Digital Input Tag

- 8 -


3.2.2 Alarm Tags

All tags that are to appear as alarms in the Alarm Summary will be DA tags. Figure 6 below illustrates an example of a DA tag.

Figure 6 – Proficy iFIX Digital Alarm Tag

- 9 -


4.0 GRAPHICS

The City has developed standardized graphics to provide consistency throughout the HMI screens in all of their facilities. This will allow for ease of use and simplicity of information conveyance. The graphics are to be based upon the Process and Instrumentation Drawings (P&IDs) for representation of the process. The template HMI application contains examples to be used in a cut and paste manner for development of process screen graphics with minor modifications needed to the tag linking as the application requires.

4.1 Colours

Standard colours are chosen to provide distinction in the information being provided by the HMI. Colours give users indication at a glance of important statuses, alarm conditions, modes of operation etc. such that at a glance an operator will be notified of the operating state of each piece of equipment or device. The colours and symbols should be followed for new development.

4.1.1 Device Status & Icon Alarming

The following figure shows the default colours and their definitions.

Figure 7 - Pump Colour Legend

- 10 -


Figure 8 - Valve Colour Legend

Figure 9 - Analog Colour Legend

- 11 -


4.2 Main Overview Screen

The main overview screen is displayed on system start up. The main overview screen is to be representative of the entire plant. From this screen there are links to access the various process areas within the specific Treatment Plant within The City. Minimal information is relayed on this screen showing very broadly, critical flows and other information to the plant. For example if the facility has a wet well with multiple pumps, only one (1) pump graphic will be used to relay if any of the pumps are running. When a process area is selected, a further detailed process screen of that particular area is displayed detailing all of the process feedback available to operations. This process area screen consists of the following three (3) sections:

i. Header and Navigation Banner; ii. System Display Screen; and,

iii. Alarm Summary Banner.

The following figure provides an example of a main overview screen.

Figure 10 – Main Overview Screen

4.3 Header and Navigation Banner The Header and Navigation Banner are always present when browsing process screens for a particular facility. Typical elements for this section include:

4.3.1 Process Buttons

Process buttons across the Header list the process areas associated with the plant and a direct link to that area when clicked on. When new processes are added the header navigation bar is required to be updated.

4.3.2 Trends / Statistics Button

Trends/Statistics button to display a link to operator configurable trends and plant statistics page (showing important information regarding the plant readings).

- 12 -


4.3.3 Alarm Button

Alarm button provides the user with access to a full page alarm summary. The alarm summary is user configurable during runtime to allow alarm filtering on specific process areas, equipment and instrumentation, and by severity (priority level).

4.3.4 Additional Buttons and Features

i. Security Button for user login/logout and display of current user logged in; and, ii. System date and time.

4.4 System Display Section

The system display section forms the central content of the application. All screens used to display process information, device pop-ups, control hardware, enter setpoint information, and view statistical information appear in this section.

4.4.1 Process Display Screens

The layout for process display screens should be according to the P&ID drawings, or as appropriate for the information being processed. Generally, process inputs come from the left side of the screen and outputs go to the right side of the screen.

As a general guideline, the amount of information on a process display screen should be in the range of 30 to 60 information points. An information point is an analog value, an alarm or message, device symbol, or bar graph symbol. Exceptions to this guideline will likely occur for more complex processes.

Figure 11 --- Process Screen Example --- Low Lift Pumps

- 13 -


4.4.2 Pop-Ups

The device pop-ups are standard graphics and should be identical across new City Wastewater and Water applications. There is a pop-up associated for each device driver found within the PLC coding standards. They should initially appear on the left side of the screen, ensuring minimal coverage of the screen. Pop-up windows may be moved by the operator. Each device in the field is to be interfaced through use of the standard popups.

The use of tag group files reduces the number of graphic files required for pop-ups. Instead of unique pop-up graphics for each controllable device, one common pop-up is used for all similar devices. These pop-ups use tag group files to map unique database tags to the generic graphic items they contain.

4.4.2.1 Analog Device Pop-up

The Analog Device pop-up contains:

i. The tag name and description of the transmitter at the top; ii. Current analog value;

iii. Operator adjustable setpoints including HIHI, HI, LO, LOLO limits; iv. All Alarms, HIHI, HI, LO, LOLO alarm and signal error enables; and, v. Calibration mode.

Figure 12 --- Analog Device Pop-up

- 14 -


4.4.2.2 Maintain Commanded Valve Pop-up

The Maintain Commanded Valve pop-up contains:

i. The tag name and description of the device at the top;

ii. Opened/Closed/Transition status;

iii. Current mode status (Local or SCADA Manual/Automatic);

iv. Open/Close control;

v. Manual/automatic mode selection; and,

vi. Alarm Enables.

Figure 13 --- Maintain Commanded Valve Pop-up

- 15 -


4.4.2.3 Analog Commanded Valve Pop-up

The Analog Commanded Valve pop-up contains:


ii. Opened/Closed/Transition status;


iv. Open/Close/Stop control;

v. Position Feedback;

vi. Manual Position control;

vii. Manual/automatic mode selection; and,

viii. Alarm Enables

Figure 14 --- Analog Commanded Valve Pop-up

- 16 -


4.4.2.4 Maintain Commanded Motor Pop-up

The Maintained Commanded Motor pop-up contains:


ii. Running status;


iv. Start/stop control;

v. Manual/automatic mode selection;

vi. Total runtime;

vii. Start Request status; and,

viii. Alarm Enables.

Figure 15 --- Maintain Commanded Motor Pop-up

- 17 -


4.4.2.5 VFD Commanded Motor Pop-up

The VFD Commanded Motor pop-up contains:


ii. Running status;


iv. Speed feedback value;

v. Start/stop control and speed setpoint entry;

vi. Manual/automatic mode selection;

vii. Total runtime;

viii. Start Request status; and,

ix. Alarm Enables.

Figure 16 --- VFD Commanded Motor Pop-up

- 18 -


5.0 ALARMS

All field alarms are generated in the PLC and polled by the HMI. Once received by the HMI, the alarm will be displayed on various alarm screens including the device popups as well as the overall alarm summary screen. Alarms are to be shown separately from events.

5.1 Alarm Areas

Alarm Areas are used to group alarms into Plant Alarms which display on the Alarm Summary, and into WIN911 alarms which appear on the WIN911 Alarm Summary. These alarm areas will then be used to provide the necessary filtering between the alarm screens.

5.2 Alarm Summary Screen

The alarm summary screen will list all current alarms in reverse chronological order (i.e. most recent at top of screen). There is also the ability to filter alarms based on facility, process area and/or equipment.

Each alarm will occupy one line of the alarm screen and will include the following minimum information:

i. Date In (Year, Month Day);

ii. Date Last (Year, Month Day);

iii. Time In (Hour, Minute, Second);

iv. Time Last (Hour, Minute, Second);

v. Active/Acknowledged;

vi. Tag Name;

vii. Tag Description; and,

viii. Tag Value.

- 19 -


Figure 17 --- Alarm Summary Screen

5.3 Alarm Acknowledgement

To acknowledge alarms, the operator will use one of the following procedures:

i. Acknowledge an individual alarm on the Main Alarm Screen by double-clicking the alarm;

ii. Acknowledge all alarms shown on the current page of the Main Alarm Screen by right-clicking the alarm summary and selecting Acknowledge All . A confirmation window will appear asking if you re sure you want to acknowledge all alarms with the options of either Yes or No; and,

iii. Acknowledge an alarm on a device pop-up by depressing the ALARM RESET pushbutton.

Upon acknowledgement, the symbols and messages associated with the alarm will stop flashing on all displays upon which they appear, such as graphic symbols and pop-ups. Acknowledged return-to-normal alarms will be automatically cleared from the alarm screen.

5.3.1 Alarm Summary Colours

Figure 18 - Alarm Summary Colours

i. In Alarm Unacknowledged : Flashing Red; ii. Not In Alarm Unacknowledged : Flashing Red; and, iii. In Alarm Acknowledged : Solid White.

- 20 -


5.3.2 Banner Summary Colours

Figure 19 - Alarm Banner Colours

i. In Alarm Unacknowledged : Flashing Red; ii. Not In Alarm Unacknowledged : Flashing Green; and, iii. In Alarm Acknowledged : Solid Yellow.

6.0 TRENDING

iFIX provides the capability for the user to view any trend point real time or historical on a horizontal scale (from left to right). All historical trend values are to be linked to and created from the information stored in the Proficy Historian database.

6.1 Trend Screen

The trend screen will have a legend that provides the following minimum information:

i. Plot line colour;

ii. Tag Name;

iii. Tag Description;

iv. Tag Value; and,

v. Tag Units.

The trend display will have the following minimum information:

i. Trend Title;

ii. Date/Time on the horizontal axis; and,

iii. Tag Range on the vertical axis.

The trends will be configured to provide the following features:

i. Real time trend duration should be configurable for spans ranging up to a selectable maximum;

ii. Ability via the pointer to pick out an individual trended data point at a specific time and have the system display the value at the time; and,

iii. Pushbuttons will reside on the trend screen to allow scrolling through time and range with the capability of zooming into any period of time and data range for any given trended data point.

- 21 -


Figure 20 – Trend Screen

7.0 SECURITY

The log-in function will restrict access to process control and system features. Access will be restricted according to access group. Security must be applied across the HMI system accordingly to inhibit access to buttons, popups, setpoint adjustments, trend data etc. as outlined below. Each user for a given facility is to be assigned a unique username and password. The default groups are defined as follows:

Guest o Access to log-in window. o Access to view displays including alarm page (without the ability to

acknowledge alarms) and pre-configured reports. o No access to process control functions.

Operator o Access to view displays including alarm page and pre-configured reports. o Access to viewing and configuring trend and group displays. o Access to all process control functions and alarm acknowledgement.

Supervisor/System Technician o Access to view displays including alarm page and pre-configured reports. o Access to viewing and configuring trend and group displays. o Access to all process control functions and alarm acknowledgement including

tuning parameters such as process and chemical setpoints.

System Administrator o Access to all aspects of workstation software management including process

control functions, display viewing, display creation, workstation set-up, network management, passwords and database editing.

Other security areas will be determined on a project by project basis. The assigning of specific security access levels to individual users is to be determined during system implementation and Operations should be consulted.

- 22 -


8.0 NETWORK AND COMMUNICATIONS

Network handshaking is to be established between the HMI and each PLC to confirm communication. Handshaking will involve a status bit turned on by iFIX and turned off by the PLC, which will be used for PLC verification, and the seconds value of the PLC clock for HMI verification. A communication alarm is then annunciated at the PLC level and HMI level following a time delay of no activity. The IGS driver resides on each SCADA node and is the software that communicates with the PLCs in the network. The following section explains how to configure the IGS driver to connect to the PLCs and the HMI.

Figure 21 --- IGS Driver Configuration --- Channel Setup

When IGS --- Configuration is initially opened without a driver file already setup, the above figure is shown. To begin setting up the driver to connect to a PLC the user must click on the Click to add a channel area, shown highlighted.

- 23 -



When the above window appears, the channel name must be entered.

- 24 -



Next, the device driver that will be assigned to the channel must be defined. In line with the City s standard of Allen-Bradley Logix based processors, the highlighted selection is chosen.

- 25 -



Following through the setup the above noted window is then displayed. The network card to be used must be selected. If default is left selected, the operating system will choose the network adapter automatically.

- 26 -


Figure 25 --- IGS Driver Configuration --- Device Setup

Once the channel has been configured, the individual PLCs must be setup to finalize the IGS configuration. By clicking on the Click to add a device shown above in blue text, this window will appear.

- 27 -



Next, the device model must be selected from the drop down list. Working with the City s standards which are to use the Allen-Bradley Logix base controllers, the ControlLogix 5500 or CompactLogix 5300 is to be chosen.

- 28 -



Next, the device ID must be entered. This ID is the PLC IP address, which needs to be input in a specific format as seen above. The , 0, 1 following the IP address represent the rack number and slot number in which the Ethernet card is found.

- 29 -



The above noted window appears next and here the Protocol Type must be selected using the drop down list, select Physical Blocking mode. The City s PLC programming standard is designed to primarily use User-defined Data Types. Because of this, Physical Blocking mode is the method best suited for optimized HMI to PLC polling.

- 30 -


Figure 29 --- IGS Driver Configuration

When finished, a version of the above window will be displayed. Save the file under the PDB file of the iFIX install path with the matching node name of the HMI.

9.0 SUBMITTALS

The following submittals must be made to the City at the end of the project:

Provide all software associated with the HMI licensing in the City’s name and on original storage media and packaging.

One (1) iFIX project file for each HMI programmed to include all databases, graphics, VB scripting, and other configuration files necessary for the full and complete system to operate.

The City has standardized on an open, readily available, and widely supported HMI platform from GE known as Proficy iFIX. All software developed for The City is considered to be the property of The City upon completion and as a result all configuration files, passwords, and other necessary files are to be turned over to the City.

10.0 OIT DEVELOPMENT

Depending on the facility or a given project the City may elect to include a local operator display. The City has currently standardized on the hardware platform for their local displays as GE QuickPanel Views. The process screens, graphics, alarming, tag creation, animation, etc. as described in this document applies to the development of the OITs. All graphics and configuration is to mimic the HMI development in look and feel so as to maintain standardization across the platforms and allow for a uniform interaction for operations regardless of where they are accessing the system from.

- 31 -


11.0 TEST DOCUMENTATION

Adhere to the City’s software factory acceptance test and software site acceptance test templates. Develop the test documentation from these templates for the specific requirements of the project.

- 32 -

Documents

City of Orillia