FMD Section 7 Programmer Reference

WCDPS DWTF SCADA Improvement Project SCADA O&M Manual Section 7 Programmers Reference
June 2010
Section 7 Programmers Reference
Ver: 1.0
7-1
June 2010
Section 7 Programmers Reference Table of Contents
7.0
Programmers Reference ................................................................................................. 7-4
7.1 DEVELOPERS TOOLS AND APPLICATIONS.................................................................................................. 7-4 7.1.1 PLCs ................................................................................................................................................ 7-4 7.1.2 HMI ................................................................................................................................................. 7-4 7.1.3 Additional Tools .............................................................................................................................. 7-4 7.2 PLC PROGRAMMING STANDARDS............................................................................................................. 7-4 7.2.1 General ............................................................................................................................................ 7-4 7.2.2 Programming Guidelines ................................................................................................................ 7-5 7.2.3 PLC Program Structure .................................................................................................................. 7-6 7.3 PLC MODULES ....................................................................................................................................... 7-11 7.3.1 Analog Motor Device .................................................................................................................... 7-11 7.3.2 Analog Input Device ...................................................................................................................... 7-14 7.3.3 Discrete Motor Device .................................................................................................................. 7-18 7.3.4 Open/Close for Valve Control ....................................................................................................... 7-21 7.3.5 Signal Conditioning Block (Digital Input) .................................................................................... 7-24 7.3.6 Lead/Lag Control Block ................................................................................................................ 7-24 7.3.7 Process Variable Selection Subroutine ......................................................................................... 7-25 7.4 HMI MODULE DOCUMENTATION ........................................................................................................... 7-26 7.4.1 General .......................................................................................................................................... 7-26 7.4.2 DWTF Baseline SCADA Application ............................................................................................ 7-26 7.4.3 Communication Settings ................................................................................................................ 7-39 7.4.4 Screens .......................................................................................................................................... 7-51 7.4.5 Devices .......................................................................................................................................... 7-62 7.5 SYSTEM ADMINISTRATION ...................................................................................................................... 7-88 7.5.1 System Startup ............................................................................................................................... 7-88 7.5.2 System Shutdown ........................................................................................................................... 7-88 7.5.3 Backup and Restore Operations .................................................................................................... 7-88 7.6 SYSTEM ACCESS AND USER SECURITY ................................................................................................... 7-89 7.6.1 User Administration ...................................................................................................................... 7-89 7.6.2 Password Security ......................................................................................................................... 7-89 7.6.3 Password Access Rights ................................................................................................................ 7-90
Appendix A: PSTPCP Programming Structure ................................................................... A-1 Appendix B: I/O List ............................................................................................................... B-1
Ver: 1.0
7-2
June 2010
List of Tables
Table 1: Initial Program Files ..................................................................................................... 7-7 Table 2: Process Program Files................................................................................................... 7-7 Table 3: Data Table Structure ..................................................................................................... 7-9 Table 4: Data Table Breakdown ............................................................................................... 7-10 Table 5: Analog Motor Device Module Input Parameters........................................................ 7-13 Table 6: Analog Motor Device Module Output Parameters ..................................................... 7-13 Table 7: Analog Input Device Module Input Parameters ......................................................... 7-16 Table 8: Analog Input Device Module Output Parameters ...................................................... 7-17 Table 9: Discrete Motor Device Module Input Parameters ...................................................... 7-20 Table 10: Discrete Motor Device Module Output Parameters ................................................. 7-21 Table 11: Discrete Motor Device Module Input Parameters .................................................... 7-23 Table 12: Discrete Valve Device Module Output Parameters .................................................. 7-24 Table 13: SCADA System Security Configuration .................................................................. 7-39 Table 14: SCADA Header and Navigation Screen Elements ................................................... 7-53 Table 15: Analog Transmitter Graphic Properties .................................................................... 7-62 Table 16: Analog Transmitter Pop-Up Properties .................................................................... 7-63 Table 17: Analog Transmitter Tagnames ................................................................................. 7-65 Table 18: Constant Speed Motor Graphic Properties ............................................................... 7-66 Table 19: Constant Speed Motor Pop-Up Proerties .................................................................. 7-68 Table 20: Constant Speed Motor Tagnames ............................................................................. 7-70 Table 21: VFD Motor Graphic Properties ................................................................................ 7-71 Table 22: VFD Motor Pop-Up Properties ................................................................................. 7-72 Table 23: VFD Motor Tagnames .............................................................................................. 7-75 Table 24: Discrete Gate Valve Graphic Properties ................................................................... 7-77 Table 25: Discrete Gate Valve Pop-Up Properties ................................................................... 7-78 Table 26: Discrete Gate Valve Tagnames ................................................................................ 7-81 Table 27: Modulating Valve/Gate Graphic Properties ............................................................. 7-82 Table 28: Modulating Valve/Gate Pop-Up Properties .............................................................. 7-84 Table 29: Modulating Valve/Gate Tagnames ........................................................................... 7-87 Table 30: Security Group Definitions ....................................................................................... 7-90 Revision Control:
Version 1.0 Date June 2010 Author Kevin Donovan QA/QC Juan Stein Description of Revisions Submittal for Owner Review
Ver: 1.0
7-3
June 2010
7.0
7.1
ProgrammersReference
DevelopersToolsandApplications
7.1.1 PLCs The tools and applications used for designing, configuring, and programming the AllenBradley PLC5s and MicroLogix PLCs are RSLogix-5, RSLogix500, RSLinx and RSLogix Emulate-5 Software. PLC program logic written under the SCADA Improvements project follow a standard and consistent structure as described in the PLC Programming section below. 7.1.2 HMI The tools and applications used for designing, configuring, and programming the SCADA System HMI graphics is GEs Proficy iFIX 5.0. This software provides a database and graphic tools for development of equipment symbols and process display for equipment monitoring and control. Standard objects (faceplates) have been developed to provide a consistent user experience. The HMI Programming section of this document provides detail information on HMI configuration. 7.1.3 AdditionalTools Additional tools and applications used in the system design, configuration and programming are GEs iHistorian, Proficy Change Management, and Proficy Web Portal; IntraVue, WIN-911 and Paragon. Software version information is provided in the Equipment Manuals. Configuration of these programs has been provided using the default parameters available with these products. Additional customization and development of these products may be undertaken in the future.
7.2
PLCProgrammingStandards
7.2.1 General A standard programming approach must be adhered to when working on the DWTF PLCs. A consistent programming approach will: Enable re-use of program routines; Make it easier to troubleshoot programs; Provide for a shorter development cycle; Provide greater flexibility to incorporate future modifications; Provide improved confidence in the automatic control functions; Provide clarity; and Enable consistency between projects (i.e., across process areas and facilities).
Ver: 1.0
7-4
June 2010
This section defines the PLC logic components to be provided, and how the PLC programs must be structured. It is the owners and consultants responsibility to follow the software standards and this PLC module development guideline. It is recognized that under certain circumstances it may be necessary to deviate from the prescribed conventions and guidelines. In these cases, the consultant is to obtain approval for the deviation before beginning work. In order to provide consistency and reliability, all programmable controllers must be programmed in the same format and structure, according to the WCDPSs guidelines and standards. Before any programming begins, the consultant must develop detail control narratives based on approved process narratives. Control narratives are to be reviewed and approved by the WCDPS prior to the commencement of software development WCDPSs primary concern is that the consultant, in designing, programming and implementing the software, assures that a safe, reliable and effective engineering solution is provided in accordance with the programming standards defined. WCDPS is the owner of all software developed by the consultant and therefore owns all rights for its use and distribution. 7.2.2 ProgrammingGuidelines Where applicable, all programming shall adhere to the guidelines outlined in the following subsections. 7.2.2.1 ProgrammingStructure Routines shall be created to group similar logic and avoid repetitive tasks. The use of indexed arrays shall be avoided. The use of constants and jumps shall be minimized. Simplicity, clarity and structure are of the utmost importance. The programmer shall not over-complicate logic to decrease scan time or improve performance. In the event that communication to the processor is lost, logic shall be provided to allow setting of any data or outputs to a safe state. InputsandOutputsto/fromtheController Discrete field input devices, such as two-state level switches, pressure switches and valve position switches, provide a binary (0 or 1) status to the PLC. The status is represented by the absence or presence of voltage (either a 24 VDC or 120 VAC signal). If a voltage is present on the input, the state is
7.2.2.2
Ver: 1.0
7-5
June 2010
considered to be High (Binary 1), whereas the absence of a voltage indicates a Low (Binary 0). Discrete input devices can only detect one state. For instance, a tank level is either high or not high. The programmer shall not assume a low tank level if the high level switch is not made. If detection of opposite states is required (e.g., tank level low), two discrete field devices must be employed. AlarmHandling Alarms shall be suppressed during start-up or shutdown of a device or a process where those alarm conditions are irrelevant during these periods. All analog alarm conditions are to be defined in the PLC and are to be passed from the PLC to the SCADA system through dedicated discrete signals. This means that the PLC will detect the alarm condition and set a bit that will be mapped to an output to SCADA. The advantage of this is that alarm conditions are defined in one place and are easy to maintain. If the alarm conditions (i.e., range checks) are defined within the SCADA system, they may need to be updated on multiple workstations. The alarm monitoring strategy is to ensure that the SCADA system provides sufficient alarm details for remote diagnosis of problems. Alarms must be conditioned so that they are generated only when valid. For instance, low flow alarms should be masked if a pump is off and the flow is directly tied to the operation of that pump. If the system is generating a lot of unnecessary nuisance alarms, operators will often miss the important ones. This situation must be avoided. All alarms shall latch in alarm state until acknowledged with the exceptions of alarms which are driven solely by self curing process changes such as under voltage (power failure), seal water low pressure, or low suction pressure. Software interlocks shall be included in order to disable equipment operation when a hardwired field alarm occurs. Debounce timers shall be applied to all field generated alarms.
7.2.2.3
7.2.3 PLCProgramStructure The following subsections describe how the PLC program files and database is defined within a program. Refer to Appendix A PSTPCP Programming Structure for an example of the program structure used for PSTPCP (Primary Sludge Transfer Pump Control Panel).
Ver: 1.0
7-6
June 2010
7.2.3.1 ProgramFiles
1: Program files will always begin with the following three files:
Table 1: Initial Program Files
File#
Title
LogicDescription
File 2 File 3 File 4
SYS Main INPUTS OUTPUTS
General Mapping of Input Image Table to Internal Registers. Mapping of Internal Register to Output Image Table.
2: Groups of files related by process. The group will begin with a Main File pertaining to the Files and should not contain more than 100 rungs, approximately.
File# Title Table 2: Process Program Files LogicDescription
File 5 File 6 File 7 File 8 File 9 File 10 File 11 File 12
MAIN1 MAIN2 MAIN3 MAIN4 MAIN5 AERA1-1* AERA1-2* AERA1-3*
Call Process Area 1 Sub Programs Call Process Area 2 Sub Programs Call Process Area 3 Sub Programs Call Process Area 4 Sub Programs Call Process Area 5 Sub Programs Process Area 1 Sub Programs - Control logic for first set of equipment in process area 1 Process Area 1 Sub Programs - Control logic for next set of equipment in process area 1 Process Area 1 Sub Programs - Control logic for next set of equipment in process area 1
File 29 File 30 File 31 File 32
AERA1-20* AERA2-1* AERA2-2* AERA2-3*
Process Area 1 Sub Programs - Control logic for next set of equipment in process area 1 Process Area 2 Sub Programs - Control logic for first set of equipment in process area 2 Process Area 2 Sub Programs - Control logic for next set of equipment in process area 2 Process Area 2 Sub Programs - Control logic for next set of equipment in process area 2
File 49 File 50
AERA2-20* AERA3-1*
Process Area 2 Sub Programs - Control logic for next set of equipment in process area 2 Process Area 3 Sub Programs - Control logic for first set of equipment in process area 3
Ver: 1.0
7-7
June 2010
File#
Title
LogicDescription
File 51 File 52
AERA3-2* AERA3-3*
Process Area 3 Sub Programs - Control logic for next set of equipment in process area 3 Process Area 3 Sub Programs - Control logic for next set of equipment in process area 3
File 109
AERA5-20*
Process Area 5 Sub Programs - Control logic for next set of equipment in process area 5 Load setpoints on first scan of the program Verification and Alarming for I/O cards Verification and Alarming for I/O cards Verification and Alarming for I/O cards
FIRST SCAN R0S1** R0S2** R0S3**
File 150
R0Sx**
Verification and Alarming for I/O cards
* The title should reflect the equipment it will control (i.e., RAS PMP for Return Activated Sludge Pump, INF VLV, for Influent Valve, etc.). ** The title should reflect the rack and slot of the I/O card.
Ver: 1.0
7-8
June 2010
This type of grouping will make it easier to remove all logic for one process out of a PLC and will facilitate finding a particular rung of logic. 7.2.3.2 DataTableStructure
The files in the Data Table are organized by function as follows:

Table 3: Data Table Structure
File
Type
Description
O0 I1 S2 B3 T4 C5 R6 N7 F8 N9 N10 N11 N12 N13 T14 T15 N16 N17 F18 F19 BT20
Outputs Inputs Status Bit Timer Counter Control Integer Float Integer Integer Integer Integer Integer Timer Timer Integer Integer Float Float BlockXfr
N21
Integer
N22
Integer
N23
Integer
PLC Field Outputs PLC Field Inputs PLC Processor Status General Usage General Usage General Usage General Usage General Usage General Usage Interface Comm. HMI Command Bits and Setpoints* Control Logic File* Control Logic File extra* Undefined* Control Timers* Control Timers extra Undefined* Undefined* Control Floating Points* Control Floating Points extra (For scaled input values and other Analog values)* Block Transfer Control Blocks (PLC-5 only) 1 Word per BTR or BTW same configuration for each Input Card same configuration for each Output Card Block Transfer Read/Write Data - Analog Card 1 (PLC-5 only) OR Remote IO Data Analog Card 1 Block Transfer Read/Write Data - Analog Card 2 (PLC-5 only) OR Remote IO Data Analog Card 2 Block Transfer Read/Write Data - Analog Card 3 (PLC-5 only) OR Remote IO Data Analog Card 3
Ver: 1.0
7-9
June 2010
File
Type
Description
N29
Block Transfer Read/Write Data - Analog Card 9 (PLC-5 only) OR Remote IO Data Analog Card 9 PD30 PID PID Instruction Control Block MG31 Message Message Instruction Control Block *See Table 4 for a breakdown of the mapping. From the above list, the following files are used to bring data to and from the PLC: I: Input O: Output N10 N21-29 from the I/O Rack to the I/O Rack from HMI from Analog cards (one file dedicated to each input or output card)
Integer
Mapping is used to organize related data and provides a means to isolate an entire layer of control hierarchy when necessary. The data from the above files are to be mapped into the appropriate internal registers in files N11 through F19. N11 through F19 are to be used to develop control logic. The registers within are divided into a grid pattern, which is laid out in Table 4 below.
N10: N11:
Table 4: Data Table Breakdown N12: N13: T14: T15: N16: N17: F18: (extra) (spare) (extra) (spare) (spare)
F19: Description (extra)
0-9 1019 2029 3039
0-9 1019 2029 3039
0-9 10-19 20-29 30-39
0-9 10-19 20-29 30-39
0-9 1019 2029 3039
0-9 10-19 20-29 30-39
0-9 10-19 20-29 30-39
0-9 10-19 20-29 30-39
0-9 1019 2029 3039
0-9 10-19 20-29 30-39
General Area Major Device #1 Major Device #2 Major Device #3
Each block in Table 4 is 10 words long. The 10-word group always pertains to a General Area or a Major Device. Then, each word within the group pertains to an individual part of the area or a component/subcomponent of a Major Device. Bits within these words are used for the same function, where applicable. The raw data of any analog channel is scaled its process area sub program as the first step of logic for any analog. If a scaling instruction is not available, the raw data of any Analog channel will be scaled using the following equation: RAW * [((MAX-MIN) / 4095) + MIN]
Ver: 1.0
7-10
June 2010
7.3
PLCModules
7.3.1 AnalogMotorDevice The Analog Motor subroutine is typically used for devices with variable speed drives such as pumps, conveyors, centrifuges, etc. The control strategy for these devices is PID closed loop. In this strategy, an analog setpoint and process variable feedback are compared by a PID function that updates a control variable based on the calculated error of the comparison. The analog setpoint (speed setpoint, process variable setpoint) is input by the operator at the SCADA. Devices programmed with the subroutine have the physical (field) inputs and outputs, as well as the virtual (SCADA) inputs and outputs.
Inputs from Field Mode Auto Status VFD Power Status Running Status Failed Analog Process Variable Indication Analog Control Variable Indication (Speed) Outputs to Field Command Start Analog Control Variable (Speed)
Inputs from SCADA Request SCADA Manual Mode Request SCADA Auto Mode Request Start Request Stop Request Alarm Reset Request Running Hours Setpoint SCADA Auto Process Setpoint Setpoint SCADA Manual Process Setpoint
Analog Device Subroutine
Outputs to SCADA Mode Remote Mode SCADA Manual Mode SCADA Auto Status Running Status Stopped Status Faulted Setpoint PID PSP Upper Clamp Setpoint PID PSP Lower Clamp Setpoint PID CV Lower Clamp Alarm Uncommanded Start Alarm Uncommanded Stop Alarm Fail to Start Alarm Fail to Stop Alarm Fail to Reach Setpoint
Ver: 1.0
7-11
June 2010
The Analog Motor Device subroutine provides the following functions: 7.3.1.1 Status indication (Running / Stopped / Alarm) Mode indication (Off / Hand / SCADA Manual / SCADA Auto) Start and stop of the motor (In SCADA Manual / In SCADA Auto) Speed control (In SCADA Manual / In SCADA Auto) Speed indication Virtual device alarm generation PID loop control Overview
When an analog motor device is selected in the field to be in Remote mode, an input is provided from the SCADA to the device module routine to indicate whether the device is in SCADA Manual or SCADA Auto mode. In SCADA Manual mode, the device can be started and stopped via the SCADA. In SCADA Auto mode, the device is automatically started and stopped based on specific process conditions. The start output command from the device module is a maintained contact. To control the speed of the device, a PID function block is used within the subroutine. In SCADA Manual mode, the operator can directly adjust the speed output of the motor from SCADA by making adjustments to the manual speed setpoint. In SCADA Auto mode, the speed of the device is automatically controlled based on an auto process variable setpoint. This auto setpoint relates to an associated process variable such as flow, level or density. In this mode, the difference between the auto process setpoint entered in SCADA and the process variable feedback is continuously evaluated by the enhanced PID function, which adjusts the speed output (control variable). The SCADA Manual and SCADA Auto start and stop logic and speed control for the motor is a major part of the device routine. Permissives must be in place in order for the motor to be started and stopped. The following virtual (software generated) alarms are configured for an analog motor device routine: Fail to Start Occurs if the running status for the motor is not received after a certain amount of time has elapsed since the request to start either in auto or manual mode was made. Fail to Stop Occurs if the stopped status for the motor is not received after a certain amount of time has elapsed since the request to stop either in auto or manual mode was made. Uncommanded Start Occurs if the running status for the motor is received in the absence of a request to start either in auto or manual mode.
Ver: 1.0
7-12
June 2010
7.3.1.2
Uncommanded Stop Occurs if the stopped status for the motor is received in the absence of a request to stop either in auto or manual mode. Fail to Reach Setpoint Occurs if the analog setpoint (i.e., speed, process variable) is not achieved within a certain amount of time. AnalogMotorDeviceModuleInputParameters
The following table summarizes the PLC addressing and tagnames used for parameters input into the Analog Motor Device Module. The example uses the RAS Pump #1, Secondary Clarifier #1, 03_Z_RASP1010. This module will be the same for all analogs motor devices.
Table 5: Analog Motor Device Module Input Parameters Description Tagname PLCAddress SCADA
RAS Pump VFD No. 1 Request to Start RAS VFD Pump No. 1 SCADA Manual Start Command from HMI RAS Pump VFD No. 1 Latched Run Request RAS VFD No. 1 Alarm Acknowledge 7.3.1.3
Not Applicable 03_X_RASP1010_S Not Applicable 03_X_RASP1010_AK
N11:50/13 N10:53/1 N11:72/11 N10:50/7
No Yes No Yes
AnalogMotorDeviceModuleOutputParameters
The following table summarizes the PLC addressing and tagnames used for parameters output from the Analog Motor Device Module. The example uses the RAS Pump #1, Secondary Clarifier #1, 03_Z_RASP1010. This module will be the same for all Analog Motor Devices.
Table 6: Analog Motor Device Module Output Parameters Description Tagname PLCAddress SCADA
RAS Pump VFD No. 1 In Auto RAS VFD Pump No. 1 SCADA Mode (1=SCADA AUTO) (0=SCADA MANUAL) RAS Pump VFD No. 1 Alarm(s) Present RAS Pump VFD No. 1 Power RAS Pump VFD No. 1 Available for Operation RAS Pump VFD No. 1 Running RAS Pump VFD No. 1 Speed Control PID Process Variable RAS Flow Signal Valid RAS Pump VFD No. 1 Speed Control PID Setpoint RAS Pump VFD No. 1 Speed Control PID Process Variable
03_Z_RASP1010_A
N11:70/6
Yes
03_X_RASP1010_SA 03_N_RASP1010A_F 03_J_RASP1010 Not Applicable 03_N_RASP1010_R Not Applicable Not Applicable Not Applicable Not Applicable
N10:53/0 N11:50/15 N11:70/5 N11:50/14 N11:70/7 N7:0 N11:21/14 PD30:0.SPS N7:0
Yes Yes Yes No Yes No No No No
Ver: 1.0
7-13
June 2010
Description RAS Pump VFD No. 1 Speed Control PID in Manual RAS Pump VFD No. 1 Speed Control PID Output RAS Pump VFD No. 1 Speed Control PID Prop. Gain RAS Pump VFD No. 1 Speed Control PID Integral Gain RAS Pump VFD No. 1 Speed Control PID Derivative Gain RAS Pump VFD No. 1 Fail to Start RAS Pump VFD No. 1 Fail to Stop RAS Pump VFD No. 1 Uncommanded Start RAS Pump VFD No. 1 Uncommanded Stop RAS Pump VFD No. 1 Speed Deviation RAS Pump VFD No. 1 Fail (from VFD) RAS Flowmeter Interlock Active RAS VFD Power Interlock Active RAS Low Flow Interlock Active
Tagname
PLCAddress
SCADA
Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable 03_S_RASP1010_FS 03_S_RASP1010_FP 03_N_RASP1010_US 03_N_RASP1010_UP 03_S_RASP1010_SD 03_N_RASP1010_F 03_N_RASP1010_I1 03_N_RASP1010_I3 03_N_RASP1010_I4
PD30:0/AM N7:1 PD30:0.KC PD30:0.TI PD30:0.TD N11:51/8 N11:51/9 N11:51/11 N11:51/12 N11:51/13 N11:51/7 N11:22/0 N11:22/2 N11:22/3
No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
7.3.2 AnalogInputDevice The Analog Input Device Subroutine is used to further condition and evaluate the mapped analog inputs from the relevant BTW/BTR subroutine. This routine has the physical (field) inputs, as well as the virtual (SCADA) inputs and outputs. Specifically, the device module has the following functions: Signal validation and limit clamping Scaling from raw counts to engineering units Analog Alarming
Ver: 1.0
7-14
June 2010
Inputs from Field Analog Input Indication
Outputs to Field None
Inputs from SCADA Alarm Reset HiHi Alarm Reset Hi Alarm Alarm Reset Lo Alarm Alarm Reset Lo Lo Alarm Alarm Reset Out of Range Low Alarm Alarm Reset Out of Range High Alarm
Analog Input Subroutine
Outputs to SCADA Status Analog Value Scaled Setpoint Hi Hi Alarm Setpoint Hi Alarm Setpoint Lo Alarm Setpoint Lo Lo Alarm Setpoint Maximum Engineering Units Setpoint Minimum Engineering Units Alarm Hi Hi Alarm Hi Alarm Lo Alarm Lo Lo Alarm Out of Range Hi Alarm Out of Range Lo
7.3.2.1
Overview
The device module performs analog signal validation to ensure that the value of the raw analog input is within an acceptable range. If the value is not within the out of range low and high limits set, signal clamping (at the high or low end) is applied to the value. The analog signal will be scaled from raw counts to engineering units in the device module. Analog alarms are generated when a measured value has exceeded or fallen below a defined range. The following analog alarms are included in the Analog Input subroutine: High-High (HIHI): An analog condition that is much greater than the normal operating process conditions High (HI): An analog condition that is greater than the normal operating process conditions.
7-15
Ver: 1.0
June 2010
Low (LO): An analog condition that is lower than the normal operating process conditions. Low-Low (LOLO): An analog condition that is much lower than the normal operating conditions. Rate of Change: Analog signal measured is changing at a rate greater than normal. Out of Range High: Analog input that has its physical 4-20 mA representation out-of-bounds high. This typically indicates a failed field device. Out of Range Low: Analog input that has its physical 4-20 mA representation out of-bounds low. This typically indicates a failed field device.
Analog alarms are programmed such that the alarm setpoints are a certain percentage of the full range of the associated transmitter. Debounce timers and reset deadbands are programmed to prevent nuisance alarms. Default alarm setpoints and reset deadband values are stored in PLC registers. 7.3.2.2 AnalogInputDeviceModuleInputParameters
The following table summarizes the PLC addressing and tagnames used for parameters input into the Analog Device Module. The example uses the PST #7 Bay 1&2 Collector Current 02_I_PTK07011. This module will be the same for all analogs.
Table 7: Analog Input Device Module Input Parameters Description Tagname PLC Address SCADA
PST #7 Bay 1&2 Collector Current Level ORH Alarm Reset PST #7 Bay 1&2 Collector Current Level ORL Alarm Reset PST #7 Bay 1&2 Collector Current Level ROC Alarm Reset PST #7 Bay 1&2 Collector Current Level HI HI Alarm Reset PST #7 Bay 1&2 Collector Current Level HI Alarm Reset PST #7 Bay 1&2 Collector Current Level Low Alarm Reset PST #7 Bay 1&2 Collector Current Level Low Low Alarm Reset PST #7 Bay 1&2 Collector Current Level ORL Limit PST #7 Bay 1&2 Collector Current Level ORH Limit PST #7 Bay 1&2 Collector Current Level Min Span
Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable Not Applicable 02_I_PTK07011_OL_LIM 02_I_PTK07011_OH_LIM 02_I_PTK07011_MIN_SPAN
B3:30/0 B3:30/1 B3:30/2 B3:30/3 B3:30/4 B3:30/5 B3:30/6 F18:31 F18:32 F18:33
No No No No No No No Yes Yes Yes
Ver: 1.0
7-16
June 2010
Description
Tagname
PLC Address
SCADA
PST #7 Bay 1&2 Collector Current Level Max Span PST #7 Bay 1&2 Collector Current Level High High Limit PST #7 Bay 1&2 Collector Current Level High Limit PST #7 Bay 1&2 Collector Current Level Low Limit PST #7 Bay 1&2 Collector Current Level Low Low Limit PST #7 Bay 1&2 Collector Current Level Final Value PST #7 Bay 1&2 Collector Current Level High High Deadband Calculation PST #7 Bay 1&2 Collector Current Level Hi Deadband Calculation PST #7 Bay 1&2 Collector Current Level Low Deadband Calculation PST #7 Bay 1&2 Collector Current Level Low Low Deadband Calculation 7.3.2.3
02_I_PTK07011_MAX_SPAN F18:34 02_I_PTK07011_HH_LIM 02_I_PTK07011_H_LIM 02_I_PTK07011_L_LIM 02_I_PTK07011_LL_LIM 02_I_PTK07011 02_I_PTK07011_HH_DBD 02_I_PTK07011_H_DBD 02_I_PTK07011_L_DBD 02_I_PTK07011_LL_DBD F18:35 F18:36 F18:37 F18:38 F19:30 F19:32 F19:34 F19:35 F19:36
Yes Yes Yes Yes Yes Yes No No No No
AnalogInputDeviceModuleOutputParameters
The following table summarizes the PLC addressing and tagnames used for parameters output from the Analog Device Module. The example uses the Primary Tank #7 Bay 1&2 Collector Current, 02_I_PTK07011. This module will be the same for all analogs. Process conditions may dictate that some of the alarms are unnecessary. The PLC code allows the programmer to enable/disable alarms in the PLC by using the Alarm Enable bit within the module. The Alarm Enable bit is sent to the HMI and used to display/hide alarm setpoints. This will allow the generic display of alarms and also allow the alarm to be added to the system easily through one bit within the PLC. No rework is required in the HMI.
Table 8: Analog Input Device Module Output Parameters Description Tagname PLC Address SCADA
PST #7 Bay 1&2 Collector Current ORH Alarm Reset from SCADA PST #7 Bay 1&2 Collector Current ORL Alarm Reset from SCADA PST #7 Bay 1&2 Collector Current HIHI Alarm Reset from SCADA PST #7 Bay 1&2 Collector Current Hi Alarm Reset from SCADA
02_I_PTK07011_OH_AK N10:90/0 02_I_PTK07011_OL_AK N10:90/1
Yes Yes Yes Yes
02_I_PTK07011_HH_AK N10:90/3 02_I_PTK07011_H_AK N10:90/4
Ver: 1.0
7-17
June 2010
Description
Tagname
PLC Address
SCADA
PST #7 Bay 1&2 Collector Current Low Alarm Reset from SCADA PST #7 Bay 1&2 Collector Current Low Low Alarm Reset from SCADA PST #7 Bay 1&2 Collector Current Level ORH Alarm Active PST #7 Bay 1&2 Collector Current Level ORL Alarm Active PST #7 Bay 1&2 Collector Current Level High High Alarm Active PST #7 Bay 1&2 Collector Current Level High Alarm Active PST #7 Bay 1&2 Collector Current Level Low Alarm Active PST #7 Bay 1&2 Collector Current Level Low Low Alarm Active PST #7 Bay 1&2 Collector Current Level Alarms Present PST #7 Bay 1&2 Collector Current Level Signal Valid PST #7 Bay 1&2 Collector Current Signal Error Detected PST #7 Bay 1&2 Collector Current Level Scan Status PST #7 Bay 1&2 Collector Current Level ORH Alarm Enable PST #7 Bay 1&2 Collector Current Level ORL Alarm Enable PST #7 Bay 1&2 Collector Current Level HiHi Alarm Enable PST #7 Bay 1&2 Collector Current Level Hi Alarm Enable PST #7 Bay 1&2 Collector Current Level Low Alarm Enable PST #7 Bay 1&2 Collector Current Level LowLow Alarm Enable 7.3.3 DiscreteMotorDevice
02_I_PTK07011_L_AK 02_I_PTK07011_LL_AK 02_I_PTK07011_ORH 02_I_PTK07011_ORL 02_I_PTK07011_HH 02_I_PTK07011_H 02_I_PTK07011_L 02_I_PTK07011_LL 02_I_PTK07011_F 02_I_PTK07011_VLD 02_I_PTK07011_ERR 02_I_PTK07011_SCAN 02_I_PTK07011_OH_AE 02_I_PTK07011_OL_AE 02_I_PTK07011_HH_AE 02_I_PTK07011_H_AE 02_I_PTK07011_L_AE 02_I_PTK07011_LL_AE
N10:90/5 N10:90/6 N11:90/0 N11:90/1 N11:90/3 N11:90/4 N11:90/5 N11:90/6
Yes Yes Yes Yes Yes Yes Yes Yes
N11:90/10 Yes N11:90/14 Yes N11:90/15 Yes N11:91/0 N11:91/1 N11:91/2 N11:91/4 N11:91/5 N11:91/6 N11:91/7 Yes Yes Yes Yes Yes Yes Yes
Single-speed pumps, conveyors, grinders, generators, mixers, etc. are examples of devices that have discrete motors. This routine has the physical (field) inputs and outputs, as well as the virtual (SCADA) inputs and outputs.
Ver: 1.0
7-18
June 2010
Inputs from Field Mode Remote Status Running Status Fault
Outputs to Field Command Start
Inputs from SCADA Request SCADA Manual Mode Request SCADA Auto Mode Request Start Request Stop Request Alarm Reset Status Stopped Status Faulted
Discrete Device Motor Controls
Outputs to SCADA Mode SCADA Manual Mode SCADA Auto Status Running Status Faulted while Running Status Faulted while Stopped Status General Alarm Alarm Uncommanded Start Alarm Uncommanded Stop Alarm Fail to Start Alarm Fail to Stop
The Discrete Motor Device routine provides the following functions: 7.3.3.1 Status indication (Running / Stopped / Alarm) Mode indication (Hand / SCADA Manual / SCADA Auto) Start and stop of the motor (SCADA Manual / SCADA Manual) Virtual device alarm generation Overview
When a discrete motor device is selected in the field to be in Remote mode, an input is provided from the SCADA to the device module routine to indicate whether the device is in SCADA Manual or SCADA Auto mode. In SCADA Manual mode, the device can be
Ver: 1.0
7-19
June 2010
started and stopped via the SCADA. In SCADA Auto mode, the device is automatically started and stopped based on a specific process condition. For example, a pumps start/stop may be controlled by the level in a tank. To place the device into SCADA Auto mode devices ready to operate permissive must be true. The SCADA Manual and SCADA Auto start and stop logic for the motor is a major part of the device routine. Start permissives must be in place in order for the motor to be started. The start output command from the device module is a maintained contact. The following virtual (software generated) alarms are configured for a discrete motor device: Fail to Start: Occurs if the running status for the motor is not received after a certain amount of time has elapsed since the request to start either in SCADA Auto or SCADA Manual mode was made. Fail to Stop: Occurs if the stopped status for the motor is not received after a certain amount of time has elapsed since the request to stop either in SCADA Auto or SCADA Manual mode was made. Uncommanded Start: Occurs if the running status for the motor is received in the absence of a request to start either in SCADA Auto or SCADA Manual mode. Uncommanded Stop: Occurs if the stopped status for the motor is received in the absence of a request to stop either in SCADA Auto or SCADA Manual mode. DiscreteMotorDeviceModuleInputParameters
7.3.3.2
The following table summarizes the PLC addressing and tagnames used for parameters input into the Discrete Motor Device Module. The example uses the PST #7 Bay 1&2 Collector, 02_ PTK07011.
Table 9: Discrete Motor Device Module Input Parameters PLC Description Tagname Address SCADA
PST #7 Bay 1&2 Collector Auto Status PST #7 Bay 1&2 Collector SCADA-Auto Mode Select From HMI PST #7 Bay 1&2 Collector Alarms Present PST #7 Bay 1&2 Collector Device Available For Operation PST #7 Bay 1&2 Collector SCADAManual Run Request From HMI PST #7 Bay 1&2 Collector SCADA-Auto Run Request PST #7 Bay 1&2 Collector Request To Run PST #7 Bay 1&2 Collector Run Request Latched Bit
02_Z_PTK07011_R 02_X_PTK07011_SA 02_N_PTK07011_F Not Applicable 02_X_PTK07011_MS Not Applicable Not Applicable Not Applicable
N11:20/0 N10:20/2 N11:22/7
Yes Yes Yes
N11:22/15 No N10:20/0 B3:12/5 N11:22/9 Yes No No
N11:22/10 No
Ver: 1.0
7-20
June 2010
Description
Tagname
PLC Address
SCADA
PST #7 Bay 1&2 Collector Alarm Acknowledge From HMI 7.3.3.3
02_X_PTK07011_AK
N10:20/1
Yes
DiscreteMotorDeviceModuleOutputParameters
The following table summarizes the PLC addressing and tagnames used for parameters outputs into the Discrete Motor Device Module. The example uses the PST #7 Bay 1&2 Collector, 02_ PTK07011. Process conditions may dictate that some of the alarms are unnecessary. The PLC code allows the programmer to enable/disable alarms in the PLC by using the Alarm Enable bit within the module. The Alarm Enable bit is sent to the HMI and used to display/hide alarm setpoints. This will allow the generic display of alarms and also allow the alarm to be added to the system easily through one bit within the PLC. No rework is required in the HMI.
Table 10: Discrete Motor Device Module Output Parameters PLC Description Tagname Address SCADA
PST #7 Bay 1&2 Collector In Starting Mode PST #7 Bay 1&2 Collector Running PST #7 Bay 1&2 Collector In Starting Mode PST #7 Bay 1&2 Collector In Running Mode PST #7 Bay 1&2 Collector In Stopping Mode PST #7 Bay 1&2 Collector Fail To Start PST #7 Bay 1&2 Collector Fail To Stop PST #7 Bay 1&2 Collector Uncommanded Start PST #7 Bay 1&2 Collector Uncommanded Stop PST #7 Bay 1&2 Collector Trip Status PST #7 Bay 1&2 Collector Overtorque Status PST #7 Bay 1&2 Collector Overload Status PST #7 Bay 1&2 Collector Underload Status 7.3.4 Open/CloseforValveControl
Not Applicable 02_N_PTK07011_R Not Applicable Not Applicable Not Applicable 02_N_PTK07011_FS 02_N_PTK07011_FP 02_N_PTK07011_US 02_N_PTK07011_UP 02_W_PTK07011_T 02_W_PTK07011_H 02_W_PTK07011_HH 02_W_PTK07011_L
N11:20/13 N11:20/5 N11:20/13 N11:20/14 N11:20/15 N11:21/0 N11:21/1 N11:21/2 N11:21/3 N11:21/4 N11:21/5 N11:21/6 N11:21/7
No Yes No No No Yes Yes Yes Yes Yes Yes Yes Yes
Devices such as valves and gates that have two positions (opened and closed) are categorized as discrete valves. The module has been programmed for discrete valves,
Ver: 1.0
7-21
June 2010
which require maintained open/close output commands. This routine has the physical (field) inputs and outputs, as well as the virtual (SCADA) inputs and outputs.
Inputs from Field Mode Remote Status Opened Status Closed Outputs to Field Command Open Command Close
Inputs from SCADA Request SCADA Manual Mode Request SCADA Auto Mode Request Open Request Close Request Alarm Reset Status General Alarm
Open/Close Valve Control
Outputs to SCADA Mode Hand Mode Remote Mode SCADA Manual Mode SCADA Auto Status Opened Status Closed Status Intermediate Status Faulted while Opened Status Faulted while Closed Alarm Uncommanded Open Alarm Uncommanded Close Alarm Fail to Open Alarm Fail to Close Alarm Unknown Position
This subroutine provides the following functions: 7.3.4.1 Status indication (Opened / Closed / Alarm) Mode indication (Hand / Remote / SCADA Manual / SCADA Auto) Open and close of the valve (In SCADA Manual / In SCADA Auto) Virtual device alarm generation. Overview
When a discrete valve device is selected in the field to be in Remote mode, an input is provided from the SCADA to the device module routine to indicate whether the device is
Ver: 1.0
7-22
June 2010
in SCADA Manual or SCADA Auto mode. In SCADA Manual mode, the device can be opened and closed via the SCADA. In SCADA Auto mode, the device is automatically opened and closed based on a specific process condition. For example, a tank outlet valve open/close may be controlled by the level in the tank. To place the device into SCADA Auto mode no alarm conditions can be active and the devices ready to operate permissive must be true. The open/close command outputs from the device module are momentary pulses. The pulse is high once the command to open or close the valve is initiated and remains high until the open/close status feedback is received. The SCADA Manual and SCADA Auto open and close logic for the valve is a major part of the device subroutine. Permissives must be in place in order for the valve to be opened and closed. The following virtual (software generated) alarms are configured for a discrete valve: Fail to Open: Occurs if the opened status for the valve is not received after a certain amount of time has elapsed since the request to open either in SCADA Auto or SCADA Manual mode was made. Fail to Close: Occurs if the closed status for the valve is not received after a certain amount of time has elapsed since the request to close either in SCADA Auto or SCADA Manual mode was made. Uncommanded Open: Occurs if the opened status for the valve is received in the absence of a request to open either in SCADA Auto or SCADA Manual mode. Uncommanded Close: Occurs if the closed status for the valve is received in the absence of a request to close either in SCADA Auto or SCADA Manual mode. Unknown Position: Occurs when physically impossible conditions are indicated such as valve is both opened and closed at the same time, or is neither opened nor closed at the same time (except during valve travel).
The following table summarizes the PLC addressing and tagnames used for parameters input into the Discrete Motor Device Module. The example uses the PST #7 Bay 1&2 Collector, 02_ PTK07011.
Table 11: Discrete Motor Device Module Input Parameters PLC Description Tagname Address SCADA
Scum Gate Operator No. 1 in Auto (virtual) Scum Gate SCADA Mode From HMI (1=SCADA AUTO) (0=SCADA MANUAL) Scum Gate Operator Alarms Present Scum Gate Operator Available for Operation Scum Gate SCADA Manual Open
03_Z_CLAR1100_R
N11:65/7
Yes
03_X_CLAR1100_SA 03_N_CLAR1100_F Not Applicable 03_X_CLAR1100_O
N10:65/1 N11:65/8 N11:65/9 N10:65/2
Yes Yes No Yes
Ver: 1.0
7-23
June 2010
Description
Tagname
PLC Address
SCADA
Command from HMI Scum Gate Operator No. 1 Request to Open Scum Gate Operator No. 1 Gate Opened Scum Gate Operator No. 1 Latched Open Request Scum Gate Alarm Acknowledge from HMI 7.3.4.2
Not Applicable 03_N_CLAR1100_O Not Applicable 03_X_CLAR1100_AK
N11:65/15 No N11:71/0 Yes B3:8/0 N10:65/0 No Yes
DiscreteValveDeviceModuleOutputParameters
The following table summarizes the PLC addressing and tagnames used for parameters outputs into the Discrete Motor Device Module. The example uses the PST #7 Bay 1&2 Collector, 02_ PTK07011.
Table 12: Discrete Valve Device Module Output Parameters PLC Description Tagname Address SCADA
Scum Gate Fail to Open Scum Gate Fail to Close Scum Gate Uncommanded Open Scum Gate Uncommanded Close Scum Gate Unknown Position
03_N_CLAR1100_FO 03_N_CLAR1100_FC 03_N_CLAR1100_UO 03_N_CLAR1100_UC 03_N_CLAR1100_UZ
N11:65/0 N11:65/1 N11:65/2 N11:65/3 N11:65/4
Yes Yes No No No
7.3.5 SignalConditioningBlock(DigitalInput) Each digital input block includes: Debounce Timers Mapping to an internal PLC Register to be used within the PLC Program and in the HMI Block Ability to place the block on/off scan Ability to manually override the signal.
The corresponding library file is Discrete Signal Conditioning Block PLC Module. PC5. 7.3.6 Lead/LagControlBlock The Lead/Lag Control Block consists of the following functions: Two modes of operation for a two-pump pair: alternating starts and lead pump select. Automatic rotation if the lead pump becomes unavailable for automatic operation.
There are no alarms associated with this subroutine.
Ver: 1.0
7-24
June 2010
The corresponding library file is Lead_Lag Duty PLC Module. PC5. 7.3.7 ProcessVariableSelectionSubroutine The Process Variable Selection Subroutine provides the following function: Allows the selection between two process variables (e.g., 2 level transmitters) Automatic switching of process variable used if the operator-selected device becomes unavailable.
Alarms associated with this block are generated by the Analog Input Block for the specific process instrument. The corresponding library file is Process Variable Selection PLC Module. PC5.
Ver: 1.0
7-25
June 2010
7.4 HMIModuleDocumentation
7.4.1 General The SCADA System provides operators with the means of monitoring and controlling plant operations. The Wayne County, Downriver Waste Water Treatment Plant (DWTF) has standardized on the use of Proficy iFIX 5.0 for its SCADA development and runtime environments and on the ABR RS Linx 7.0 Driver for communication between iFIX and the DWTF PLCs (Allen-Bradley PLC-5s and MicroLogix 1500s). 7.4.2 DWTFBaselineSCADAApplication The DWTF Baseline SCADA Application provides a starting point for the Owners staff and consultants working on the DWTF SCADA system. This application contains all system level scripts, sample screens, HMI Modules and application setup parameters for the existing SCADA application. 7.4.2.1 Scripting
The Baseline Application uses scripting for internal application management only. The following is a list of SCADA functionality provided through scripting: Security management Network connectivity Alarm management Pop-up linking Screen navigation
Mathematical calculations, device or process control, unit conversion and scaling of analog values are provided only in the PLCs. 7.4.2.2 ApplicationSettings
The following subsections define the Proficy iFIX application settings. These settings will be used for all HMI application development at DWTF. These settings can be found in the Workspace Application by selecting the following: Workspace -> User Preferences There are several tabs that allow configuration of both the Workspace (Development Mode) and the Runtime Mode.
Ver: 1.0
7-26
June 2010
The General tab has the following options selected:
Ver: 1.0
7-27
June 2010
The Automation Error Defaults tab has the following options selected:
Ver: 1.0
7-28
June 2010
The Shape Preferences tab has the following options selected:
Ver: 1.0
7-29
June 2010
The Picture Preferences tab has the following options selected:
Ver: 1.0
7-30
June 2010
The Chart Preferences tab has the following options selected:
Ver: 1.0
7-31
June 2010
The Drawing Options tab has the following options selected:
Ver: 1.0
7-32
June 2010
The Environment Protection tab has the following options selected:
Ver: 1.0
7-33
June 2010
The Background StartUp tab has the following options selected:
Ver: 1.0
7-34
June 2010
The StartUp Pictures tab has the following options selected:
Ver: 1.0
7-35
June 2010
The Change Management tab has the following options selected:
Ver: 1.0
7-36
June 2010
7.4.2.3 7.4.2.3.1
AlarmConfiguration AlarmAreas
iFIX uses an Alarm Summary object to display a real-time list of active alarms and events or messages. Alarms are used to report conditions that require various levels of response by operations including those conditions that require immediate attention, while events are non-critical occurrences that do not necessitate a response and are generated to allow for future troubleshooting and to provide a record of operational conditions. Due to the large volume of events that normally occur in the DWTF, the Alarm Summary object displays alarms only; thus, avoiding the possibility of overlooking potentially dangerous process conditions. Within the Alarm Summary object, operators can view, acknowledge, and filter alarms as needed. The Alarm Summary object contains the following categories of information: Acknowledged/Unacknowledged Time of alarm Date of alarm Tag name Description Alarm area Priority Present state or value AlarmSummaryObject
7.4.2.3.2
Alarms are grouped into areas representing physical or functional sections of the DWTF. The iFIX application provides default alarm areas; however the areas can be modified and new areas can be added as the SCADA System is expanded. Alarm areas allow for filtering of alarms to display alarms from any individual area or a group of alarm areas. The alarm summary screen has check boxes located to the right side of the alarm summary to allow filtering of alarms based on a process area. Alarm priority and status within an Alarm Summary object can easily be distinguished by the established custom alarm color scheme. The text color of an alarm is based on the alarms status (i.e., acknowledged/unacknowledged), and the background color based on alarm priority. The background color of Priority 1 Alarms is red, for Priority 2 Alarms yellow, and Priority 3 Alarms blue. The foreground, or text color, is set to black for unacknowledged alarms and grey for acknowledged alarms. Alarm priorities are defined as follows: Priority 1 Alarm (High): highest priority
Ver: 1.0
7-37
June 2010
Priority 2 Alarm (Medium): medium priority Priority 3 Alarm (Low): low priority AlarmAcknowledgement
7.4.2.3.3
Alarms can be acknowledged by double-clicking the alarm in the Alarm Summary object. After alarm acknowledgement, a checkmark will appear in the Alarm Summarys (Ack) column adjacent to the acknowledged alarm. iFIX utilizes alarm synchronization; thus after acknowledgement of an alarm on any view node, all other view nodes will also indicate acknowledgement of the alarm. When the process condition for an acknowledged alarm returns to a normal range, the alarm will automatically be removed from the Alarm Summary on all nodes. Multiple alarms can be acknowledged at the same time by right-clicking the Alarm Summary object and selecting Acknowledge Page or Acknowledge All, thereby acknowledging all alarms matching the objects alarm filter. Alternatively, all alarms on a single page can be acknowledged by clicking an Acknowledge Page push button, which activates an Acknowledge Alarm script. The Acknowledge Page button is located on the right side of the alarm screen. 7.4.2.4 HistoricalLoggingConfiguration
The DWTF system utilizes Proficy Historian for data collection. Tags are individually configured for collection through the database block. 7.4.2.4.1 ChartObjects
iFIX charts can be configured to show any number of data trends or pens simultaneously, and multiple charts can be shown on the same screen. Line styles, colors, widths, and markers can be used to help distinguish between data trends. Although there is no limit to the number of pens that can be shown, chart pens are limited to eight (8). For process areas with dozens of data points that require trending, Chart Groups are used. Chart Groups allow the SCADA developer to define groups of data points that should be trended together. These Chart Groups can be applied to a chart at run-time by using VBA Scripting and command buttons. For example, clicking a command button labeled Pump Flows should apply the relevant Chart Group to the chart. By applying the Chart Group, all pen values represent data points in the selected Chart Group. Several recommendations are identified as follows: Avoid dark colors for trend screen background Avoid high-contrast pen colors Use descriptive trend screen titles Display appropriate engineering units Group trends by relative process interaction
Ver: 1.0
7-38
June 2010
Group consumable items on a chart related to the process Repeat trends on several charts as needed
These recommendations are all relevant to the needs of the Wayne County DWTF and are all supported by iFIX. A number of pre-configured trend screens has been developed. An additional user defined configurable trend is provided to allowing ad hoc trending. The pre-configured trend screens have the screen name displayed at the top of the screen and control buttons at the bottom of the trend to select the trend duration (1 hour/4 hours/8 hours/24 hours) back-and-forward buttons, and a calendar to select a date. 7.4.2.5 SecurityConfiguration
The SCADA System uses three (3) security groups, as defined below.
GroupLevel Table 13: SCADA System Security Configuration GroupName GroupDescription
1 2 3
Administrators Operators Guest
Admin Group for IT (full access) Operator group with access to regular equipment Group required for default security
The System Integrator/Consultant should consult with SCADA System Administrator for security configurations prior to starting HMI development. 7.4.3 CommunicationSettings The Process Database is the underlying communication layer for the Proficy iFIX SCADA applications. The SCADA System uses an ABR I/O Driver and Allen-Bradley RSLinx to communicate with the PLCs. 7.4.3.1 ABRI/ODriver
The ABR I/O driver is a GE Fanuc version 7.x I/O driver that provides the interface and communications protocol between Allen-Bradley process hardware and the process control software. GE Fanuc version 7.x drivers incorporate the following attributes: OLE Automation technology FIX integration Event-driven architecture OLE for Process Control compliance.
Ver: 1.0
7-39
June 2010
The following graphic illustrates the configuration used for SCADA System development.
The driver communicates to the PLCs through the RSLinx interface.
Ver: 1.0
7-40
June 2010
7.4.3.1.1
RSLinx
RSLinx is a complete 32-bit product family that links Allen-Bradley networks and devices to Microsoft Windows applications, including device programming and configuration applications for RSLogix, iFIX, data acquisition applications using Microsoft Office, Web pages, or Visual Basic. RSLinx also incorporates advanced data optimization techniques and contains a set of diagnostics. RSLinx is an OPC Data Access Compliant Server and a DDE server. 7.4.3.2 7.4.3.2.1 ProficyiFIX ProcessDatabase
The item address can be specified for the database block in the Process Database I/O Address setting. ABR I/O addresses typically consist of the device name and the data block element. The I/O address is specific to the driver. This field is not case sensitive. ABR I/O addresses have the following format: DEVICE_NAME:ADDRESS [:BIT] or DEVICE_NAME:ADDRESS.MNEMONIC Where: DEVICE_NAME - Is the name of the field device or process hardware from which data is to be collected. This name must match the device name in the driver configuration file. ADDRESS - Is a register in the device. This address matches the address defined by a data block, such as N7:3. BIT - Is a specific digital point in the register. This entry is only necessary for digital database blocks. The driver accepts bit entries of 0 to 15. Note: for a PLC 3, bits values range from 0 to 7 and 10 to 17. MNEMONIC - Is a particular field in a data structure. Each mnemonic may return an analog or digital value and is analog and digital sensitive.
Ver: 1.0
7-41
June 2010
The following figure shows a typical database tag configuration.
7.4.3.3
TagTypes
The following subsections define the tag types used when developing the Proficy iFIX Process Database. 7.4.3.3.1 DiscreteInputsandOutputs
Digital Input (DI) Blocks can be used for reading and writing digital type tags and can also be configured for alarming. The SCADA Application uses the Digital Input Block for reading, writing and alarming purposes.
Ver: 1.0
7-42
June 2010
This Basic Tab configuration of the Digital Input Block is shown below. I/O Addressing is described in later Sections.
Ver: 1.0
7-43
June 2010
The Alarms Tab describes how a typical Digital Input, with alarming is defined. The Enable Alarming is checked in the Alarm Options Box and the Close is checked on the Alarm Type Box. Alarm Priority and alarms areas are also defined here.
Ver: 1.0
7-44
June 2010
For points in the Process Database that require an output, the Enable Output is checked on the Advanced Tab.
Ver: 1.0
7-45
June 2010
Historian data collection configuration is performed through the Proficy Historian tab.
7.4.3.3.2
AnalogInputsandOutputs
Analog Input (AI) Blocks are used for reading and writing analog type tags and can also be configured for alarming. The SCADA Application uses the Analog Input Block for reading, writing and alarming purposes. There is no signal conditioning performed in the Database Block, all scaling is performed in the PLC. Engineering Units are specified in the AI Block for display on the Analog Device Pop-up.
Ver: 1.0
7-46
June 2010
This Basic Tab configuration of the Analog Input Block is shown below. I/O Addressing is described in later Sections.
Ver: 1.0
7-47
June 2010
The Alarms Tab describes how a typical Analog Input with alarming is defined but is not used. The PLC compares analog values against alarm setpoints, and produces discrete alarm values where required.
Ver: 1.0
7-48
June 2010
For points in the Process Database that require an output, the Enable Output is checked on the Advanced Tab.
Ver: 1.0
7-49
June 2010
Historian data collection configuration is performed through the Proficy Historian tab.
Ver: 1.0
7-50
June 2010
7.4.4 Screens All Proficy iFIX screens are sized for a monitor resolution of 1024 x 768 pixels. The Baseline Application consists of a main splash screen, a navigation bar, process screens and device pop-up screens. 7.4.4.1 GeneralScreenLayout
All screens, except the DWTF overview screen, consist of three regions: Screen Header and Navigation located at the top of the screen System Display located in between the screen header and alarm banner Alarm Banner located at the bottom of the screen.
The navigation banner is named WayneCountyBanner.grf.
Ver: 1.0
7-51
June 2010
7.4.4.2
MainSplashScreen
The main splash screen consists of an overview of the DWTF. The overview screen displays process flows, wetwell elevations, major process equipment status, and other key performance indicators.
7.4.4.3
SCADAHeaderandNavigation
The SCADA Header and Navigation Bar is always present when browsing process screens. The following illustration depicts the SCADA Header and Navigation Bar.
Ver: 1.0
7-52
June 2010
The following table describes each of the SCADA Header and Navigation Screen elements.
Table 14: SCADA Header and Navigation Screen Elements ScreenElement Description Animations
Previous screen button
Forward screen button
Home navigation button Main alarm screen button Security Print screen button
Touch moves back to last screen viewed. Holds the last 10 screens viewed Touch moves to the next screen. Holds the last 10 screens viewed Touch displays main system splash screen Touch displays facility main alarm screen Touch allows user to login/logout of system Touch opens a printer pop-up and prints the current screen N/A
Name of current process area screen displayed System date and time Current Logged in User Process Area Menu
N/A N/A Touch displays a drop down menu that shows what screens are available for the process area
Ver: 1.0
7-53
June 2010
7.4.4.3.1
MenuNavigation
The drop-down menu provides navigation similar to Microsoft Windows-based applications such as Word. Each process area menu button, when activated, displays a drop-down menu that shows screens available for that particular process area. The drop-down menu allows for two-tier navigation. The first tier for Influent Pump Station is provided below:
In general, each of the drop-down menus has navigation to the Overview Screen associated with the process area, detailed process screens, setpoints screen, and trends screens. A second level is associated with the drop-down menu, allowing the operator to drill down to a more specific screen within a series of screens. This allows the drop-down menu to be more manageable and display less information and requires less space. The following depicts an example of navigation to the second level of the drop-down menu:
Ver: 1.0
7-54
June 2010
7.4.4.4
SystemDisplayScreens
The System Display Screens form the central content of the SCADA application. All screens used to control hardware, enter setpoint information and view statistical information appear on a process screen within the system display area. The general naming convention for the process area screens are as follows: Process Overview Screen: DWTF_ + {Process Area Abbreviation} + _00X Process Detail Screens: DWTF _ + {Process Area Abbreviation} + _10X Process Setpoint Screens: DWTF _ + {Process Area Abbreviation} + _20X Process Trend Screens: DWTF _ + {Process Area Abbreviation} + _30X
Ver: 1.0
7-55
June 2010
7.4.4.5
AlarmScreen
The Plant Area screen displays all facility alarms. The screen allows filtering of Process Area Alarms by selecting the check boxes on the right hand side of the Alarm Display.
Ver: 1.0
7-56
June 2010
7.4.4.6
SetpointScreen
The following is a sample setpoint screen. Ranges and current analog readings for the associated setpoints are provided for the user to view during setpoint entry.
Ver: 1.0
7-57
June 2010
7.4.4.7
TrendScreen
The trend screen is shown below. All trend screens use this format.
Ver: 1.0
7-58
June 2010
7.4.4.8
PLCHealthOverviewScreen
A PLC Health Overview Screen is indicates the current health status of the DWTF PLCs.
Ver: 1.0
7-59
June 2010
A details button is available for each PLC, generating a pop-up that provides more detailed information about the PLC health status. A sample PLC health pop-up is shown below.
Ver: 1.0
7-60
June 2010
7.4.4.9 ProcessPipingColorsScreen
A Process Piping Colors Screen shows the color format used on the HMI screens. Note that any deviation from these standards, or the use of additional colors not identified below, must be approved by the County prior to proceeding with development of the HMI graphics.
Ver: 1.0
7-61
June 2010
7.4.5 Devices The following subsections detail HMI Modules developed in conjunction with PLC Modules to allow for common programming throughout the DWTF for common devices. 7.4.5.1 AnalogInputModule
The graphic for an analog transmitter is depicted in the illustration below.
The animation properties of the analog transmitter graphic are described in the table below.
Table 15: Analog Transmitter Graphic Properties GraphicElement Animation
Box around Value and Color104 (0,192,192) Normal Units Bright Magenta (255,0,255) High Out of Range, Lo Out of Range Bright Yellow (255,255,0) High Alarm, Low Alarm Red (255,0,0) HiHi Alarm, LoLo Alarm #### Analog transmitter value. DATAD Analog transmitter engineering units. Derived from analog transmitter tag definition
Ver: 1.0
7-62
June 2010
The analog transmitter pop-up is depicted below.
The animation properties of the analog pop-up are as follows:

Table 16: Analog Transmitter Pop-Up Properties GraphicElement Animation
Analog transmitter tagname. This is passed to the pop-up through a Tag Group Display (TGD) File. Analog transmitter tagname comment field. Provides a description of the device. This parameter is passed to the pop-up through a TGD file. Analog transmitter bar graph. Shows low and high engineering unit scales. Shows high-high, high, low and low-low alarm setpoints. Analog transmitter value. .
Ver: 1.0
7-63
June 2010
GraphicElement
Animation
An alarm reset button acknowledges the alarms in the display and sends an alarm reset command to the PLC. The Alarm Summary shows alarms associated with the device. Alarm comment is grayed out if the alarm is not active. Alarm comment text is black and the background flashes based on alarm priority when there is an unacknowledged alarm; and the background is solid based on alarm priority if there is an acknowledged and active alarm. The tags in the pop-up are populated by using a Tag Group Display (TGD) file. The TGD file associated with the pop-up is detailed below. The symbol indicates the name used on the pop-up. The substitution is the actual tagname tied to the point in the database.
Note: The substitution tags would change based on the device/instrument.
Ver: 1.0
7-64
June 2010
The following is a list of read/write tags associated with the device and pop-up.
Tagname Table 17: Analog Transmitter Tagnames Description
Analog Value Span Maximum Span Minimum High Alarm Present High Alarm Reset from SCADA High High Alarm Present High High Alarm Reset from SCADA Low Low Alarm Reset from SCADA Low Alarm Present Low Low Alarm Present Low Alarm Reset from SCADA Out of Range High Alarm Present Out of Range High Reset from SCADA Out of Range Low Alarm Present Out of Range Low Reset from SCADA High High Alarm Limit High Alarm Limit Low Alarm Limit Low Low Alarm Limit Units Critical Alarm Instrument Description High Alarm Enabled High High Alarm Enabled Low Alarm Enabled Low Low Alarm Enabled Instrument Tagname
Read/Write Status
Read Read Read Read Read/Write Read Read/Write Read/Write Read Read Read/Write Read Read/Write Read Read/Write Read Read Read Read Read Read Read Read Read Read Read Read
ANALOGCURRENTVALUE ANALOGEGUMAXIMUM ANALOGEGUMINIMUM ANALOGHIALARM ANALOGHIALARMRES ANALOGHIHIALARM ANALOGHIHIALARMRES ANALOGHLOWLOWALARMRES ANALOGLOALARM ANALOGLOLOALARM ANALOGLOWALARMRES ANALOGOUTOFRANGEHIALARM ANALOGOUTOFRANGEHIALARMRES ANALOGOUTOFRANGELOALARM ANALOGOUTOFRANGELOWALARMRES ANALOGVALUEALARMHIHILIMIT ANALOGVALUEALARMHILIMIT ANALOGVALUEALARMLOLIMIT ANALOGVALUEALARMLOLOLIMIT ANALOGVALUEEGUDESCRIPTION CRITICALALARM DESCRIPTION HIALARMAENABLE HIHIALARMAENABLE LOALARMAENABLE LOLOALARMAENABLE TAGNAME
Ver: 1.0
7-65
June 2010
7.4.5.2
ConstantSpeedMotor
The Constant Speed Motor HMI Module is used with the Constant Speed Motor PLC Module. This Device is used for constant speed motors with On/Off capability (now speed control). The graphic symbol for a constant speed motor is depicted below.
The animation properties are described in the table below.

Table 18: Constant Speed Motor Graphic Properties GraphicElement Animation
Pump Body
Inner Triangle
Device Mode
Device State
Green (0,255,0) Stopped Red (255,0,0) Running Green Blinking (0,255,0) Stopped and Faulted Red Blinking (255,0,0) Running and Faulted Black (0,0,0) Local Blue (0,0,255) SCADA Auto White (255,255,255) SCADA Manual L Local A SCADA Auto M SCADA Manual S Stopped R Running I Inhibited
Ver: 1.0
7-66
June 2010
The associated pop-up is shown below:
Ver: 1.0
7-67
June 2010
The animation properties of the constant speed motor pop-up are as follows:
Table 19: Constant Speed Motor Pop-Up Proerties GraphicElement Animation
Motor: 02_PSP01001
Description: PST #1 Sludge Pump
Constant Speed Motor Tagname. This is passed to the pop-up through a TGD File. Constant Speed Motor comment field. Provides a description of the device. This parameter is passed to the pop-up through a TGD file. SCADA Mode Selection. If SCADA Manual mode is active, the Manual button is greyed out. If SCADA Auto mode is active, the auto button will be greyed out. Sends SCADA Auto and SCADA Manual requests to the PLC. SCADA Manual selection. If the motor is currently started, the start button will be greyed out. If the motor is currently stopped, the stop button will be greyed out. If the motor is in SCADA Auto mode, both start and stop buttons are greyed out. Sends SCADA Manual start and stop requests to the PLC. Control Status text box shows the following indications: 1) Local 2) SCADA Auto 3) SCADA Manual Device Status text box shows the following indications: 1) Running 2) Stopped 3) Inhibited This text is displayed if a Process Interlock is inhibiting the device from operating in SCADA Auto or SCADA Manual
Ver: 1.0
7-68
June 2010
GraphicElement
Animation
Pump Body: 1) Green (0,255,0) Stopped 2) Red (255,0,0) Running 3) Green Blinking (0,255,0) Stopped and Faulted 4) Red Blinking (255,0,0) Running and Faulted Alarm Reset button acknowledges the alarms in the display and sends an alarm reset command to the PLC. The Alarm Summary shows alarms associated with the device. Alarm comment is greyed out if alarm is not active. Alarm comment text is black and background flashes based on alarm priority when there is an unacknowledged alarm or the background is solid based on alarm priority if there is an acknowledged alarm. Details expansion button. Graphic objects below this button are normally not visible. Clicking this button will expand the device pop-up window to show additional details. The Process Interlocks shows Process Interlocks that will cause the device to be locked out of SCADA Auto or SCADA Manual operation. Comment is greyed out if interlock is not active. Comment text is black and background flashes if the interlock is active.
Ver: 1.0
7-69
June 2010
The tags in the pop-up are populated by using a Tag Group Display (TGD) file. The TGD file associated with the pop-up is detailed below. The symbol indicates the name used on the pop-up. The substitution is the actual tagname tied to the point in the database.
The following is a list of read/write tags associated with the device and pop-up:
Table 20: Constant Speed Motor Tagnames Tag
02_X_PBL01001_AK 02_X_PBL01001_SA 02_Z_PBL01001_R 02_T_PBL01001_H 02_N_PBL01001_A 02_N_PBL01001_F 02_N_PBL01001_FS 02_N_PBL01001_FP 02_Z_PBL01001_S 02_Z_PBL01001_O 02_N_PBL01001_R 02_X_PBL01001_MS 02_N_PBL01001_US 02_N_PBL01001_UP
Description
Alarm Reset from the HMI Device in Remote Auto/Remote Manual Control Panel 3 position selector switch Auto Position Hardwired-Device Alarm Trip High Temp Hardwired-Device Alarm Fail Alarms Present Software Alarm Fail to Start Software Alarm Fail to Stop Control Panel 3 position selector switch Hand Position Control Panel 3 position selector switch Off Position Equipment Running Status Start/Stop Device from the HMI Software Alarm Uncommanded Start Software Alarm Uncommanded Stop
Read/Write Status
Read/Write Read Read Read Read Read Read Read Read Read Read Read/Write Read Read
Ver: 1.0
7-70
June 2010
7.4.5.3
VFDMotor
The VFD Motor Module is used with the VFD Motor PLC Module. It is used for motors with a speed output and speed feedback. This device allows up to 5 hard-wired alarms and up to 5 process interlocks. The graphic symbol for a VFD Motor is depicted below

Table 21: VFD Motor Graphic Properties GraphicElement Animation
Pump Body
Inner Triangle
Device Mode
Device State
Green (0,255,0) Stopped Red (255,0,0) Running Green Blinking (0,255,0) Stopped and Faulted Red Blinking (255,0,0) Running and Faulted Black (0,0,0) Local Blue (0,0,255) SCADA Auto White (255,255,255) SCADA Manual L Local A SCADA Auto M SCADA Manual S Stopped R Running I Inhibited
Ver: 1.0
7-71
June 2010
The associated pop-up is as follows:
The animation properties of the VFD motor pop-up are as follows:

Table 22: VFD Motor Pop-Up Properties Graphic Element Animation
VFD Motor Tagname. This is passed to the popup through a TGD File. VFD Motor comment field, which provides a description of the device. This parameter is passed to the pop-up through a TGD file.
Ver: 1.0
7-72
June 2010
Graphic Element
Animation
SCADA Mode Selection. If SCADA Manual mode is active, the Manual button is greyed out. If SCADA Auto mode is active, the Auto button will be greyed out. Sends SCADA Auto and SCADA Manual requests to the PLC. SCADA Manual selection. If the motor is currently started, the start button will be greyed out. If the motor is currently stopped, the stop button will be greyed out. If the motor is in SCADA Auto mode, both start and stop buttons are greyed out. Sends SCADA Manual start and stop requests to the PLC. Control Status text box shows the following indications: 1) Local 2) SCADA Auto 3) SCADA Manual Device Status text box shows the following indications: 1) Running 2) Stopped 3) Inhibited SCADA Manual setpoint. When the motor is in SCADA Manual mode, allows the operator to set the motor speed. When the valve is in SCADA Auto mode, allows the operator enter the setpoint to which the motor should be controlled. This text is displayed if a Process Interlock is inhibiting the device from operating in SCADA Auto or SCADA Manual VFD Speed Indication. This is visible only when the motor is in operation. Pump Body: 1) Green (0,255,0) Stopped 2) Red (255,0,0) Running 3) Green Blinking (0,255,0) Stopped and Faulted 4) Red Blinking (255,0,0) Running and Faulted
Ver: 1.0
7-73
June 2010
Graphic Element
Animation
Alarm Reset button acknowledges the alarms in the display and sends an alarm reset command to the PLC. The Alarm Summary shows alarms associated with the device. Alarm comment is greyed out if alarm is not active. Alarm comment text is black and background flashes based on alarm priority when there is an unacknowledged alarm or the background is solid based on alarm priority if there is an acknowledged alarm. Details expansion button. Graphic objects below this button are normally not visible. Clicking this button will expand the device pop-up window to show additional details. Details on the PID control for the motor speed of the device.
The Process Interlocks shows Process Interlocks that will cause the device to be locked out of SCADA Auto or SCADA Manual operation. Comment is greyed out if interlock is not active. Comment text is black and background flashes if the interlock is active.
Ver: 1.0
7-74
June 2010
Table 23: VFD Motor Tagnames Tagname
03_X_RASP1010_AK 03_Z_RASP1010_A 03_F_CLAR1070_SP 03_S_RASP1010_PD 03_N_RASP1010_F 03_N_RASP1010A_F 03_S_RASP1010_FS 03_S_RASP1010_FP 03_S_RASP1010_PI 03_S_RASP1010_SP
Description
Alarm Reset from the HMI Control Panel 3 position selector switch Auto Position Auto PID Setpoint to PLC PID Loop PID Loop Derivative Hard-wired alarm Failed Alarms Present Software Alarm Fail to Start Software Alarm Fail to Stop PID Loop Integral Manual Setpoint to PLC
Read/Write Status
Read/Write Read Read Read Read Read Read Read Read Read/Write
Ver: 1.0
7-75
June 2010
Tagname
03_S_RASP1010_Y 03_N_RASP1010_I1 03_N_RASP1010_I3 03_N_RASP1010_I4 03_S_RASP1010_PP 03_N_RASP1010_R 03_X_RASP1010_SA 03_X_RASP1010_SA12 03_S_RASP1010 03_S_RASP1010_SD 03_S_RASP1010_OH 03_S_RASP1010_OL 03_X_RASP1010_S 03_N_RASP1010_US 03_N_RASP1010_UP
Description
PID Loop Output Process Interlock Process Interlock Process Interlock PID Loop Proportional Equipment Running Status Device in SCADA Auto/SCADA Manual Device in SCADA Auto1/SCADA Auto2 Equipment VFD Speed Value Software Alarm Speed Deviation Software Alarm Speed ORH Software Alarm Speed ORL Start/Stop Device from HMI Software Alarm Uncommanded Start Software Alarm Uncommanded Stop
Read/Write Status
Read Read Read Read Read Read Read/Write Read/Write Read Read Read Read Read/Write Read Read
Ver: 1.0
7-76
June 2010
7.4.5.4
DiscreteValve/Gate
The Discrete Valve/Gate HMI Module will be used with the Discrete Valve/Gate PLC Module. It is used for valves which can be either opened or closed with open and closed limit switches. This Device allows up to 5 hard-wired alarms and up to 5 process interlocks. The graphic symbol for a discrete valve is depicted below

Table 24: Discrete Gate Valve Graphic Properties GraphicElement Animation
Valve Body
Valve Hat
Device Mode
Device State
Green (0,255,0) Closed Red (255,0,0) Open Yellow (255,255,0) Intermediate Position Green Blinking (0,255,0) Closed and Faulted Red Blinking (255,0,0) Open and Faulted Yellow Blinking (255,255,0) Intermediate Position and Faulted Black (0,0,0) Local Blue (0,0,255) SCADA Auto White (255,255,255) SCADA Manual L Local A SCADA Auto M SCADA Manual C Closed O Open I Intermediate
Ver: 1.0
7-77
June 2010
The animation properties of the discrete valve pop-up are as follows:

Table 25: Discrete Gate Valve Pop-Up Properties GraphicElement Animation
Discrete Valve Tagname. This is passed to the popup through a TGD File Discrete Valve comment field which provides a description of the device. This parameter is passed to the pop-up through a TGD file.
Ver: 1.0
7-78
June 2010
GraphicElement
Animation
SCADA Mode Selection. If SCADA Manual mode is active, the Manual button is greyed out. If SCADA Auto mode is active, the Auto button will be greyed out. Sends SCADA Auto and SCADA Manual requests to the PLC. SCADA Manual selection. If the valve is currently open, the open button will be greyed out. If the valve is currently closed, the close button will be greyed out. If the valve is in SCADA Auto mode, both open and close buttons are greyed out. Sends SCADA Manual open and close requests to the PLC. Control Status text box shows the following indications: 1) Local 2) SCADA Auto 3) SCADA Manual Device Status text box shows the following indications: 1) Open 2) Intermediate 3) Closed This text is displayed if a Process Interlock is inhibiting the device from operating in SCADA Auto or SCADA Manual Valve Body: 1) Green (0,255,0) Closed 2) Red (255,0,0) Open 3) Yellow (255,255,0) Intermediate 4) Green Blinking (0,255,0) Closed and Faulted 5) Red Blinking (255,0,0) Open and Faulted 6) Yellow Blinking (255,255,0) Intermediate and Faulted Alarm Reset button acknowledges the alarms in the display and sends an alarm reset command to the PLC. The Alarm Summary shows alarms associated with the device. Alarm comment is greyed out if alarm is not active. Alarm comment is text is black and background flashes based on alarm priority when there is an unacknowledged alarm or the background is solid based on alarm priority if there is an acknowledged alarm.
Ver: 1.0
7-79
June 2010
GraphicElement
Animation
Details expansion button. Graphic objects below this button are normally not visible. Clicking this button will expand the device pop-up window to show additional details.
Ver: 1.0
7-80
June 2010
Table 26: Discrete Gate Valve Tagnames Tag
03_X_CLAR1000_AK 03_Z_CLAR1000_R 03_N_CLAR1000_T 03_W_CLAR1000_Z 03_N_CLAR1000_F 03_N_CLAR1000_FS 03_N_CLAR1000_FP 03_N_CLAR1000_R 03_X_CLAR1000_SA 03_X_CLAR1000_S 03_N_CLAR1000_US 03_N_CLAR1000_UP
Description
Alarm Reset from the HMI Control Panel 3-position selector switch Auto Position Hardwired Device Alarm Hardwired Device Alarm Hardwired Device Alarm Software Alarm Fail to Start Software Alarm Fail to Stop Equipment Running Status Device in SCADA Auto/SCADA Manual Start/Stop Device from the HMI Software Alarm Uncommanded Start Software Alarm Uncommanded Stop
Read/Write Status
Read/Write Read Read Read Read Read Read Read Read/Write Read/Write Read Read
Ver: 1.0
7-81
June 2010
7.4.5.5
ModulatingValve/Gate
The Modulating Valve/Gate HMI Module is used with the Modulating Valve/Gate PLC Module. This type of valve has a position transmitter and is able to open/close to any value between 0% and 100%. This device allows up to 5 hard-wired alarms and up to 5 process interlocks to be associated with it. The graphic symbol for a discrete valve is depicted below.

Table 27: Modulating Valve/Gate Graphic Properties GraphicElement Animation
Valve Body
Valve Hat
Device Mode
Device State
Green (0,255,0) Closed Red (255,0,0) Open Yellow (255,255,0) Intermediate Position Green Blinking (0,255,0) Closed and Faulted Red Blinking (255,0,0) Open and Faulted Yellow Blinking (255,255,0) Intermediate Position and Faulted Black (0,0,0) Local Blue (0,0,255) SCADA Auto White (255,255,255) SCADA Manual L Local A SCADA Auto M SCADA Manual C Closed O Open I Intermediate
Ver: 1.0
7-82
June 2010
Ver: 1.0
7-83
June 2010
The animation properties of the modulating valve pop-up are as follows:

Table 28: Modulating Valve/Gate Pop-Up Properties GraphicElement Animation
The Modulating Valve/Gate Tagname. This is passed to the pop-up through a TGD file. Modulating Valve comment field which provides a description of the device. This parameter is passed to the pop-up through a TGD file. SCADA Mode Selection. If SCADA Manual mode is active, the Manual button is greyed out. If SCADA Auto mode is active, the Auto button will be greyed out. Sends SCADA Auto and SCADA Manual requests to the PLC. SCADA Manual selection. When the valve is in SCADA Manual mode, allows the operator to set the valve position. When the valve is in SCADA Auto mode, allows the operator enter the setpoint to which the valve should be controlled. Control Status text box shows the following indications: 1) Local 2) SCADA Auto 3) SCADA Manual Device Status text box shows the following indications: 1) Open 2) Intermediate 3) Closed This text is displayed if a Process Interlock is inhibiting the device from operating in SCADA Auto or SCADA Manual
Ver: 1.0
7-84
June 2010
GraphicElement
Animation
Valve Body: 1) Green (0,255,0) Closed 2) Red (255,0,0) Open 3) Yellow (255,255,0) Intermediate 4) Green Blinking (0,255,0) Closed and Faulted 5) Red Blinking (255,0,0) Open and Faulted 6) Yellow Blinking (255,255,0) Intermediate and Faulted Alarm Reset button acknowledges the alarms in the display and sends an alarm reset command to the PLC. The Alarm Summary shows alarms associated with the device. Alarm comment is greyed out if alarm is not active. Alarm comment is text is black and background flashes based on alarm priority when there is an unacknowledged alarm or the background is solid based on alarm priority if there is an acknowledged alarm. Details expansion button. Graphic objects below this button are normally not visible. Clicking this button will expand the device pop-up window to show additional details. The Process Interlocks shows Process Interlocks that will cause the device to be locked out of SCADA Auto or SCADA Manual operation. Comment is greyed out if interlock is not active. Comment text is black and background flashes if the interlock is active.
Ver: 1.0
7-85
June 2010
GraphicElement
Animation
Details on the PID control for the valve position of the device.
Ver: 1.0
7-86
June 2010
Table 29: Modulating Valve/Gate Tagnames Tagname
03_N_CLAR1040_MN 03_N_CLAR1040_MX 03_Z_CLAR1040_D 03_F_CLAR1020_D 03_X_CLAR1040_AK 03_Z_CLAR1040_R 03_F_CLAR1020_SP 03_Z_CLAR1040_PD 03_N_CLAR1040_F 03_Z_CLAR1040_PI 03_Z_CLAR1040_SP 03_Z_CLAR1040_OH 03_Z_CLAR1040_OL 03_Z_CLAR1040_Y 03_Z_CLAR1040_PP
Description
Hardwired Device Alarm Hardwired Device Alarm Hardwired Device Alarm Hardwired Device Alarm Alarm Reset from the HMI Control Panel 3-position selector switch Auto Position SCADA Auto1 (Flow) Control Setpoint PID Loop Derivative Device Failed PID Loop Integral SCADA Manual Position Setpoint Out Of Range High Alarm Out Of Range High Low PID Loop Output PID Loop Proportional
Read/Write Status
Read Read Read Read Read/Write Read Read/Write Read Read Read Read/Write Read Read Read Read
Ver: 1.0
7-87
June 2010
Tagname
03_X_CLAR1040_SA 03_Z_CLAR1040 03_X_CLAR1040_SA12
Description
Device in SCADA Auto/SCADA Manual Valve Position Readback Signal Device in SCADA Auto1/SCADA Auto2
Read/Write Status
Read/Write Read Read/Write
7.5
SystemAdministration
7.5.1 SystemStartup The SCADA System is designed to run 24/7 and is configured to auto start all required applications and services when the server start button is pressed. It is unlikely that the entire SCADA System will be stopped and require a complete restart. If required, each server will require starting in the following order: the Domain server should be started first followed by the SCADA servers, Terminal Servers, Historian Server, Web Server and Backup Server. Routers will reboot when power is applied and intervention is not required. 7.5.2 SystemShutdown To shut down the entire SCADA System the DWTF equipment should be running in local mode. Servers may be shut down in reverse order from the sequence stated in the section above. A more likely event is individual servers will require reboot after software upgrades or maintenance. In this case the system components may be shut down when necessary. The impact of individual server shutdown is described below. Shutting down the domain server prevents any additional users from logging-in Shutting down a single terminal server disconnects the terminal server session for users logged in to the Terminal Server and requires the user to log on to the remaining running terminal server Shutting down one of the redundant SCADA servers will cause the running server to become Active (if previously on Standby) and will have no effect on system performance. Shutting down the Historian server will stop data collection in the historian. SCADA server collectors will continue to capture historical data and will forward these data to the Historian when it is returned to service.
7.5.3 BackupandRestoreOperations Backup of system graphics, database and PLC programs are provided either manually or through Proficy Change Management. PLC logic files are manually backed up to the file server. A shortcut to the file directory is available on the file server desktop. The user copies and pastes the PLC programs from the local workstation (maintenance laptop) to the file server.
Ver: 1.0
7-88
June 2010
HMI graphic changes are made directly to Terminal Server 1 and copied to Terminal Server 2. The user selects the PIC file from the iFIX directory on Terminal Server 1 and copies the PIC file into the same directory on Terminal Server 2. It is necessary to perform this copy-and-paste step for all Thin Clients to access identical graphics when logged into either Terminal Server. HMI graphic changes must also be manually copied to all Thick Client machines. A backup of the iFIX application files (TGD and GRF files) should also be stored on the file server. iFIX database changes are made to the logical database of the SCADA servers and are automatically synchronized between the redundant SCADA Servers. A backup of the logical database (PDB file) should also be stored on the file server.
7.6
SystemAccessandUserSecurity
7.6.1 UserAdministration SCADA System users are added and removed through the Domain Server. The SCADA System uses Microsoft security for establishing user profiles and permissions, and user administration functions are documented in the Microsoft Administrator help files. The SCADA System user names follow the WCDPS naming standard. The SCADA System user security is also managed through the iFIX application. Users are assigned to user groups, e.g., administrator or operator, and iFIX read/write privileges are assigned via iFIX. Instructions for adding users, deleting users, changing user profiles, etc. are provided in the iFIX documentation. 7.6.2 PasswordSecurity The SCADA System provides built-in security to prevent unauthorized control actions to DWTF process equipment. The SCADA System includes three user levels; each with a varying degree of access. 1. Guest: allows user to view and navigate graphic displays 2. Operator: allows user to perform guest functions and make operational changes including equipment commands, alarm acknowledgement and set point changes 3. Administrator: allows user to perform guest and operator functions and modify system graphic displays and database. The SCADA System workstations log-out after a period of inactivity. This action prevents a thin client workstation from being left logged-on and unattended. Workstations automatically time out the Operator and Administrator and revert to the GUEST security level after a period of inactivity. Note: Some workstations will also automatically log off the entire SCADA System if inactive for a period of time.
Ver: 1.0
7-89
June 2010
Passwords can be set to expire or not expire. The SCADA System default setting requires users to change their password every 30 days. Some users have been established with passwords that never expire. There are no specific rules surrounding acceptable passwords; however, common practice is to use a mix of upper and lower case and numbers in a password. The workstation will prompt the user when to change a password and provides notification a few days ahead of the password expiration date. 7.6.3 PasswordAccessRights The DWTF SCADA System utilizes three (3) security groups as defined above and repeated in the table below.
GroupLevel GroupName Table 30: Security Group Definitions GroupDescription
1 2 3
Administrators Operators Guest
Admin Group for IT (full access) Operator group with access to regular equipment Group required for default security
Guest level provides view-only of the main overview screen and process area screens. Equipment pop-ups displays and alarm screens are restricted. Operator level provides full access to DWTF operations screens including equipment pop-ups, alarm screens, setpoint screens and trend screens. Administrator level provides access the iFIX Workspace, remote SCADA System access via Wireless Access Points and WAN devices with designated laptop computers only. o Connections to external networks including the SCADA wireless networks, business networks, and the Internet is limited to Administrator-level access with SCADA laptop computers only. o A Web server provides access to the Web Portal. Administrative-level users may also access the Web Portal application, resident within a Demilitarized Zone (DMZ) on the SCADA System network.
Ver: 1.0
7-90
June 2010
Appendix A:
PSTPCP Programming Structure
Ver: 1.0
7-A1
June 2010
Appendix A PSTPCP Programming Structure

Sample PLC Program Layout PSTPCP Primary Sludge Transfer Pumps PLC PROGRAM FILES 1: Program files will always begin with the following three files. File # File 2: File 3: File 4: Title Logic Description General Mapping of Input Image Table to Internal Registers. Mapping of Internal Register to Output Image Table.
System Main Inputs Outputs
2: Groups of Files related by process. The group will begin with a Main File pertaining to that Files should not contain more than 100 rungs, approximately. File 5: File 6: File 7: File 8: File 9: File 10: File 11: File 12: File 13: File 14: File 15: File 16: File 17: File 18: SOLIDSMAIN Not Used Not Used Not Used Not Used SOLIDSPMP1 (Logic for Primary Solids Pump #1) SOLIDSFLO1 (Logic for Primary Solids Pump #1 Flowmeter Signal) SOLIDSLEV1 (Logic for Primary Solids Tank #1 Level Transmitter Signal) SOLIDSPMP2 (Logic for Primary Solids Pump #2) SOLIDSFLO2 (Logic for Primary Solids Pump #2 Flowmeter Signal) SOLIDSLEV2 (Logic for Primary Solids Tank #2 Level Transmitter Signal) LEVELSELCT (Level Transmitter Selection for Pump Control) SOLIDSDUTY (Pump Duty Table Logic) SOLIDSRUN (Pump Start/Stop Logic
File 110: First Scan File 111-150: Rack Layouts This type of grouping will make it easier to remove all logic for one process out of a PLC and will facilitate finding a particular rung of logic.
Ver: 1.0
7-A2
June 2010
DATA TABLE STRUCTURE

N10: N11:
Appendix A Table 1: PLC Data Table Structure N12: N13: T14: T15: N16: N17: F18: (extra) (spare) (extra) (spare) (spare)
F19: Description (extra)
0-9 1019 2129 3139 1.
0-9 10-19 21-29 31-39
0-9 10-19 21-29 31-39
0-9 10-19 21-29 31-39
0-9 1019 2129 3139
0-9 10-19 21-29 31-39
0-9 10-19 21-29 31-39
0-9 10-19 21-29 31-39
0-9 2049 5079 80109
0-9 20-49 50-89 80109
General Area Pump 1, Tank 1, Flowmeter 1 Pump 2, Tank 2, Flowmeter 2 Chemical Meters
Primary Solids Pump #1 Data Table (P-00410)
The first word is the field information transfer to SCADA (For Pump #1 it is N11:10). Each bit within the word is assigned identically for all pumps. Spare bits are utilized for non-standard information for the pump. The second word is the transfer of all software generated alarms from the PLC to SCADA (For Pump #1 it is N11:11). Each bit within the word is assigned identically for all pumps. Spare bits are utilized for non-standard information for the pump. The third word contains all of the SCADA commands to the PLC. (For Pump #1 it is N11:14)
Appendix A Table 2: Primary Solids Pump #1 Data Table PLC Address Tagname Description
N11:10/0 N11:10/1 N11:10/2 N11:10/3 N11:10/4 N11:10/5 N11:10/6 N11:10/7 N11:10/8 N11:10/9 N11:10/10 N11:10/11 N11:10/12 N11:10/13 N11:10/14 N11:10/15 N11:11/0 N11:11/1
04_Z_00410C_A 04_Z_00410B_A 04_Z_00410A_A
04_N_00410_R 04_N_00410_F
04_X_00410_S 04_X_00410_P 04_X_00410_STR 04_X_00410_RUN 04_X_00410_STP 04_X_00410_FST 04_X_00410_FSP
Pri. Solids Pump #1 Auto Status Final Value Pri. Solids Pump #1 Off Status Final Value Pri. Solids Pump #1 Hand Status Final Value Spare Spare Pri. Solids Pump #1 Running Status Final Value Pri. Solids Pump #1 Fail Final Value Spare Spare Spare Spare Pri. Solids Pump #1 Start PB Status Final Value Pri. Solids Pump #1 Stop PB Status Final Value Pri. Solids Pump #1 in Starting Mode Final Value Pri. Solids Pump #1 in Running Mode Final Value Pri. Solids Pump #1 in Stopping Mode Final Value Pri. Solids Pump #1 Fail to Start Latched Alarm Pri. Solids Pump #1 Fail to Stop Final Value
Ver: 1.0
7-A3
June 2010
PLC Address
Tagname
Description
N11:11/2 N11:11/3 N11:11/4 N11:11/5 N11:11/6 N11:11/7 N11:11/8 N11:11/9 N11:11/10 N11:11/11 N11:11/12 N11:11/13 N11:11/14 N11:11/15 N11:14/0 N11:14/1 N11:14/2 N11:14/3 N11:14/4 N11:14/5 N11:14/6 N11:14/7 N11:14/8 N11:14/9 N11:14/10 N11:14/11 N11:14/12 N11:14/13 N11:14/14 N11:14/15 2.
04_X_00410_FST 04_X_00410_FSP 04_X_00410_UST 04_X_00410_USP
04_G_00410_A 04_G_00410_M 04_G_00410A_S 04_G_00410A_P 04_G_00410B_S 04_G_00410B_P
Pri. Solids Pump #1 Fail to Start Latched Alarm Pri. Solids Pump #1 Fail to Stop Final Value Pri. Solids Pump #1 Uncommanded Start Latched Alarm Pri. Solids Pump #1 Uncommanded Stop Latched Alarm Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Pri. Solids Pump #1 Auto Mode Selected Pri. Solids Pump #1 Duty Select Pri. Solids Pump #1 Remote Manual Run Request Pri. Solids Pump #1 Remote Manual Stop Request Pri. Solids Pump #1 Remote Auto Run Request Pri. Solids Pump #1 Remote Auto Stop Request Pri. Solids Pump #1 Acknowledge Alarms Pri. Solids Pump #1 Alarms Present Pri. Solids Pump #1 Request to Run Pri. Solids Pump #1 Request to Stop Pri. Solids Pump #1 Minimum Off Time
04_G_00410_S 04_G_00410_P
Pri. Solids Pump #1 Standby Pump 04_G_00410_AVAIL Pri. Solids Pump #1 Pump Available for Operation
Primary Solids Tank #1 Data Table (L-04001)
N11:12/0 N11:12/15 All level transmitter alarms transmitted to SCADA (Order is the same for all analog instruments). F18:30 F18:39 All level transmitter analog data to be displayed on the SCADA (Order is the same for all analog instruments). F19:30 F19:39 PLC Calculated Points to SCADA
Ver: 1.0
7-A4
June 2010
Appendix A Table 3: Primary Solids Tank #1 Data Table
PLC Address N11:12/0 N11:12/1 N11:12/2 N11:12/3 N11:12/4 N11:12/5 N11:12/6 N11:12/7 N11:12/8 N11:12/9 N11:12/13 N11:12/14 N11:12/15 F18:30 F18:31 F18:32 F18:33 F18:34 F18:35 F18:36 F18:37 F18:38 F18:39 F19:30 F19:31 F19:32 F19:33 F19:34 F19:35 F19:36 F19:37 F19:38 F19:39 3.
Tagname 04_L_04001_ORH 04_L_04001_ORL 04_L_04001_ROC 04_L_04001_HH 04_L_04001_H 04_L_04001_L 04_L_04001_LL 04_L_04001A_H 04_L_04001A_L 04_L_04001_T 04_L_04001_ERR_L 04_L_04001_VLD 04_L_04001_ERR 04_L_04001_COND 04_L_04001_ORL_LIM 04_L_04001_ORH_LIM 04_L_04001_MIN_SPAN 04_L_04001_MAX_SPAN 04_L_04001_HH_LIM 04_L_04001_H_LIM 04_L_04001_L_LIM 04_L_04001_LL_LIM 04_L_04001 04_L_04001_HH_DBD 04_L_04001_H_DBD 04_L_04001_L_DBD 04_L_04001_LL_DBD
Description Pri. Solids Tank #1 Level ORH Alarm Pri. Solids Tank #1 Level ORL Alarm Pri. Solids Tank #1 Level ROC Alarm Pri. Solids Tank #1 Level High High Alarm Pri. Solids Tank #1 Level High Alarm Pri. Solids Tank #1 Level Low Alarm Pri. Solids Tank #1 Level Low Low Alarm Pri. Solids Tank #1 Level Switch High Alarm Pri. Solids Tank #1 Level Switch Low Alarm Pri. Solids Tank #1 Trans Trouble Status Alarm Pri. Solids Tank #1 Signal Error Latched Alarm Pri. Solids Tank #1 Level Signal Valid Pri. Solids Tank #1 Signal Error Detected Pri. Solids Tank#1 Level Input Conditioning Pri. Solids Tank#1 Level ORL Limit Pri. Solids Tank#1 Level ORH Limit Pri. Solids Tank#1 Level Min Span Pri. Solids Tank#1 Level Max Span Pri. Solids Tank#1 Level High High Limit Pri. Solids Tank#1 Level High Limit Pri. Solids Tank#1 Level Low Limit Pri. Solids Tank#1 Level Low Low Limit Spare Pri. Solids Tank #1 Level Final Value Pri. Solids Tank #1 Level High High Deadband HiHi with Deadband Pri. Solids Tank #1 Level Hi Deadband Pri. Solids Tank #1 Level Low Deadband Pri. Solids Tank #1 Level Low Low Deadband Spare Spare Spare
Primary Solids Pump Flowmeter #1 Data Table (F-04007)
N11:13/0 N11:13/15 All transmitter alarm signals transmitted to SCADA (Order is the same for all analog instruments). F18:20 F18:29 All transmitter analog data to be displayed on SCADA (Order is the same for all analog instruments). F19:20 F19:29 PLC Calculated Points to SCADA
Ver: 1.0
7-A5
June 2010
Appendix A Table 4: Primary Solids Pump Flowmeter #1 Data Table PLC Address Tagname Description
N11:13/0 N11:13/1 N11:13/2 N11:13/3 N11:13/4 N11:13/5 N11:13/6 N11:13/14 N11:13/15 F18:20 F18:21 F18:22 F18:23 F18:24 F18:25 F18:26 F18:27 F18:28 F18:29 F19:20 F19:21 F19:22 F19:23 F19:24 F19:25 F19:26 F19:27 F19:28 F19:29 4.
04_F_04007_ORH 04_F_04007_ORL 04_F_04007_ROC 04_F_04007_HH 04_F_04007_H 04_F_04007_L 04_F_04007_LL 04_F_04007_VLD 04_F_04007_ERR
Pri. Solids Pump #1 Flow ORH Alarm Active Pri. Solids Pump #1 Flow ORL Alarm Active Pri. Solids Pump #1 Flow ROC Alarm Active Pri. Solids Pump #1 Flow High High Alarm Active Pri. Solids Pump #1 Flow High Alarm Active Pri. Solids Pump #1 Flow Low Alarm Active Pri. Solids Pump #1 Flow Low Low Alarm Active Pri. Solids Pump #1 Flow Signal Valid Pri. Solids Pump #1 Flow Signal Error Detected Pri. Solids Pump#1 Flowmeter Flow Input 04_F_04007_COND Conditioning 04_F_04007_ORL_LIM Pri. Solids Pump #1 Flowmeter Flow ORL Limit 04_F_04007_ORH_LIM Pri. Solids Pump #1 Flowmeter Flow ORH Limit 04_F_04007_MIN_SPAN Pri. Solids Pump #1 Flowmeter Flow Min Span 04_F_04007_MAX_SPAN Pri. Solids Pump #1 Flowmeter Flow Max Span Pri. Solids Pump #1 Flowmeter Flow High High 04_F_04007_HH_LIM Limit 04_F_04007_H_LIM Pri. Solids Pump #1 Flowmeter Flow High Limit 04_F_04007_L_LIM Pri. Solids Pump #1 Flowmeter Flow Low Limit Pri. Solids Pump #1 Flowmeter Flow Low Low 04_F_04007_LL_LIM Limit 04_F_04007 Pri. Solids Pump #1 Flowmeter Flow Final Value Pri. Solids Pump #1 Flowmeter High High Deadband Calculation HiHI with Deadband Pri. Solids Pump #1 Flowmeter Hi Deadband Calculation Spare Pri. Solids Pump #1 Flowmeter Low Deadband Calculation Spare Pri. Solids Pump #1 Flowmeter LowLow Deadband Calculation Spare
04_F_04007_HH_DBD
04_F_04007_H_DBD
04_F_04007_L_DBD
04_F_04007_LL_DBD
Primary Solids Pump #2 Data Table (P-00411)
The first word is the field information transfer to SCADA (for Pump #2 it is N11:20). The second word is the transfer of all software generated alarms from the PLC to SCADA (for Pump #2 it is N11:21).
Ver: 1.0
7-A6
June 2010
The third word contains all of the SCADA commands to the PLC (for Pump #2 it is N11:24).
Appendix A Table 5: Primary Solids Pump #2 Data Table PLC Address Tagname Description
N11:20/0 N11:20/1 N11:20/2 N11:20/3 N11:20/4 N11:20/5 N11:20/6 N11:20/7 N11:20/8 N11:20/9 N11:20/10 N11:20/11 N11:20/12 N11:20/13 N11:20/14 N11:20/15 N11:21/0 N11:21/1 N11:21/2 N11:21/3 N11:21/4 N11:21/5 N11:21/6 N11:21/7 N11:21/8 N11:21/9 N11:21/10 N11:21/11 N11:21/12 N11:21/13 N11:21/14 N11:21/14 N11:24/0 N11:24/1 N11:24/2 N11:24/3 N11:24/4 N11:24/5 N11:24/6
04_Z_00411C_A 04_Z_00411B_A 04_Z_00411A_A
04_N_00411_R 04_N_00411_F
04_X_00411_S 04_X_00411_P 04_X_00411_STR 04_X_00411_RUN 04_X_00411_STP 04_X_00411_FST 04_X_00411_FSP 04_X_00411_UST 04_X_00411_USP
04_G_00411_A 04_G_00411_M 04_G_00411A_S 04_G_00411A_P 04_G_00411B_S 04_G_00411B_P
Pri. Solids Pump #2 Auto Status Final Value Pri. Solids Pump #2 Off Status Final Value Pri. Solids Pump #2 Hand Status Final Value Spare Spare Pri. Solids Pump #2 Running Status Final Value Pri. Solids Pump #2 Fail Status Final Value Spare Spare Spare Spare Pri. Solids Pump #2 Start PB Status Final Value Pri. Solids Pump #2 Stop PB Status Final Value Pri. Solids Pump #2 in Starting Mode Final Value Pri. Solids Pump #2 in Running Mode Final Value Pri. Solids Pump #2 in Stopping Mode Final Value Pri. Solids Pump #2 Fail to Start Final Value Pri. Solids Pump #2 Fail to Stop Final Value Pri. Solids Pump #2 Uncommanded Start Final Value Pri. Solids Pump #2 Uncommanded Stop Final Value Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Spare Pri. Solids Pump #2 Auto Mode Selected Pri. Solids Pump #2 Duty Select Pri. Solids Pump #2 Remote Manual Run Request Pri. Solids Pump #2 Remote Manual Stop Request Pri. Solids Pump #2 Remote Auto Run Request Pri. Solids Pump #2 Remote Auto Stop Request Pri. Solids Pump #2 Acknowledge Alarms
Ver: 1.0
7-A7
June 2010
PLC Address
Tagname
Description
N11:24/7 N11:24/8 N11:24/9 04_G_00411_S N11:24/10 04_G_00411_P N11:24/11 N11:24/12 N11:24/13 N11:24/14 N11:24/15 04_G_00411_AVAIL 5.
Pri. Solids Pump #2 Alarms Present Spare Pri. Solids Pump #2 Request to Run Pri. Solids Pump #2 Request to Stop Pri. Solids Pump #2 Minimum Off Time Spare Spare Pri. Solids Pump #2 Standby Pump Pri. Solids Pump #2 Pump Available for Operation
Primary Solids Tank #2 Data Table (L-04002)
N11:22/0 N11:22/15 All level transmitter alarm signals transmitted to SCADA (Order is the same for all analog instruments). F18:50 F18:59 All level transmitter analog data to be displayed on SCADA (Order is the same for all analog instruments). F19:30 F19:39 PLC Calculated Points to SCADA
Appendix A Table 6: Primary Solids Tank #2 Data Table PLC Address Tagname Description
N11:22/0 N11:22/1 N11:22/2 N11:22/3 N11:22/4 N11:22/5 N11:22/6 N11:22/7 N11:22/8 N11:22/9 N11:22/13 N11:22/14 N11:22/15 F18:50 F18:51 F18:52 F18:53 F18:54 F18:55 F18:56 F18:57 F18:58
04_L_04002_ORH 04_L_04002_ORL 04_L_04002_ROC 04_L_04002_HH 04_L_04002_H 04_L_04002_L 04_L_04002_LL 04_L_04002A_H 04_L_04002A_L 04_L_04002_T 04_L_04002_ERR_L 04_L_04002_VLD 04_L_04002_ERR 04_L_04002_COND 04_L_04002_ORL_LIM 04_L_04002_ORH_LIM 04_L_04002_MIN_SPAN 04_L_04002_MAX_SPAN 04_L_04002_HH_LIM 04_L_04002_H_LIM 04_L_04002_L_LIM 04_L_04002_LL_LIM
Pri. Solids Tank #2 Level ORH Alarm Pri. Solids Tank #2 Level ORL Alarm Pri. Solids Tank #2 Level ROC Alarm Pri. Solids Tank #2 Level High High Alarm Pri. Solids Tank #2 Level High Alarm Pri. Solids Tank #2 Level Low Alarm Pri. Solids Tank #2 Level Low Low Alarm Pri. Solids Tank #2 Level Switch High Alarm Pri. Solids Tank #2 Level Switch Low Alarm Pri. Solids Tank #2 Trans Trouble Status Alarm Pri. Solids Tank #2 Signal Error Latched Alarm Pri. Solids Tank #2 Level Signal Valid Pri. Solids Tank #2 Signal Error Detected Pri. Solids Tank #2 Level Input Conditioning Pri. Solids Tank #2 Level ORL Limit Pri. Solids Tank #2 Level ORH Limit Pri. Solids Tank #2 Level Min Span Pri. Solids Tank #2 Level Max Span Pri. Solids Tank #2 Level High High Limit Pri. Solids Tank #2 Level High Limit Pri. Solids Tank #2 Level Low Limit Pri. Solids Tank #2 Level Low Low Limit
Ver: 1.0
7-A8
June 2010
PLC Address
Tagname
Description
F18:59 F19:50 F19:51 F19:52 F19:53 F19:54 F19:55 F19:56 F19:57 F19:58 F19:59 6.
04_L_04002 04_L_04002_HH_DBD 04_L_04002_H_DBD 04_L_04002_L_DBD 04_L_040021_LL_DBD
Spare Pri. Solids Tank #2 Level Final Value Pri. Solids Tank #2 Level High High Deadband HiHi with Deadband Pri. Solids Tank #2 Level Hi Deadband Pri. Solids Tank #2 Level Low Deadband Pri. Solids Tank #2 Level LowLow Deadband Spare Spare Spare
Primary Solids Pump Flowmeter #2 Data Table (F-04008)
N11:23/0 N11:23/15 All transmitter alarm signals transmitted to SCADA (Order is the same for all analog instruments). F18:40 F18:49 All transmitter analog data to be displayed on SCADA (Order is the same for all analog instruments). F19:40 F19:49 PLC Calculated Points to SCADA
Appendix A Table 7: Primary Solids Pump Flowmeter #2 Data Table PLC Address Tagname Description
N11:23/0 N11:23/1 N11:23/2 N11:23/3 N11:23/4 N11:23/5 N11:23/6 N11:23/14 N11:23/15 F18:40 F18:41 F18:42 F18:43 F18:44 F18:45 F18:46 F18:47 F18:48
04_F_04007_ORH 04_F_04007_ORL 04_F_04007_ROC 04_F_04007_HH 04_F_04007_H 04_F_04007_L 04_F_04007_LL 04_F_04007_VLD 04_F_04007_ERR
Pri. Solids Pump #1 Flow ORH Alarm Active Pri. Solids Pump #1 Flow ORL Alarm Active Pri. Solids Pump #1 Flow ROC Alarm Active Pri. Solids Pump #1 Flow High High Alarm Active Pri. Solids Pump #1 Flow High Alarm Active Pri. Solids Pump #1 Flow Low Alarm Active Pri. Solids Pump #1 Flow Low Low Alarm Active Pri. Solids Pump #1 Flow Signal Valid Pri. Solids Pump #1 Flow Signal Error Detected Pri. Solids Pump#1 Flowmeter Flow Input 04_F_04007_COND Conditioning 04_F_04007_ORL_LIM Pri. Solids Pump #1 Flowmeter Flow ORL Limit 04_F_04007_ORH_LIM Pri. Solids Pump #1 Flowmeter Flow ORH Limit 04_F_04007_MIN_SPAN Pri. Solids Pump #1 Flowmeter Flow Min Span 04_F_04007_MAX_SPAN Pri. Solids Pump #1 Flowmeter Flow Max Span Pri. Solids Pump #1 Flowmeter Flow High High 04_F_04007_HH_LIM Limit 04_F_04007_H_LIM Pri. Solids Pump #1 Flowmeter Flow High Limit 04_F_04007_L_LIM Pri. Solids Pump #1 Flowmeter Flow Low Limit 04_F_04007_LL_LIM Pri. Solids Pump #1 Flowmeter Flow Low Low
Ver: 1.0
7-A9
June 2010
PLC Address
Tagname
Description
Limit F18:49 F19:40 F19:41 F19:42 F19:43 F19:44 F19:45 F19:46 F19:47 F19:48 F19:49 7. 04_F_04007 Pri. Solids Pump #1 Flowmeter Flow Final Value Pri. Solids Pump #1 Flowmeter High High Deadband Calculation HiHi with Deadband Pri. Solids Pump #1 Flowmeter Hi Deadband Calculation Spare Pri. Solids Pump #1 Flowmeter Low Deadband Calculation Spare Pri. Solids Pump #1 Flowmeter Low Low Deadband Calculation Spare
04_F_04007_HH_DBD
04_F_04007_H_DBD
04_F_04007_L_DBD
04_F_04007_LL_DBD
General Points for the Process
F18:10 F18:20 Primary Solids Pump Start and Stop Levels N11:16 Duty Selection
Appendix A Table 8: General Points for the Process PLC Address Tagname Description
F18:10 F18:11 F18:12 F18:13 N11:16/0 N11:16/1 N11:16/2
04_L_04001A_LVL 04_L_04001B_LVL 04_L_04001C_LVL
Pri. Solids Pumps Duty Pump Start Level Pri. Solids Pumps Duty Pump Stop Level Pri. Solids Pumps Standby Pump Start Level Pri. Solids Pumps Standby Pump Stop Level Pri. Solids Pump #1 Duty Selected Final Value Pri. Solids Pump #2 Duty Selected Final Value Pri. Solids Pumps Alternate Duty Sel Final Value
Ver: 1.0
7-A10
June 2010
Appendix B:
I/O List
Ver: 1.0
7-B1

FMD Section 7 Programmer Reference

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

FMD Section 7 Programmer Reference

Diunggah oleh

Hak Cipta:

Format Tersedia

WCDPS DWTF SCADA Improvement Project SCADA O&M Manual Section 7 Programmers Reference

Section 7 Programmers Reference

Section 7 Programmers Reference Table of Contents

Programmers Reference ................................................................................................. 7-4

File 2 File 3 File 4

SYS Main INPUTS OUTPUTS

File 5 File 6 File 7 File 8 File 9 File 10 File 11 File 12

MAIN1 MAIN2 MAIN3 MAIN4 MAIN5 AERA1-1* AERA1-2* AERA1-3*

File 29 File 30 File 31 File 32

AERA1-20* AERA2-1* AERA2-2* AERA2-3*

File 69 File 70 File 71 File 72

AERA3-20* AERA4-1* AERA4-2* AERA4-3*

File 89 File 90 File 91 File 92

AERA4-20* AERA5-1* AERA5-2* AERA5-3*

File 110 File 111 File 112 File 113

FIRST SCAN R0S1** R0S2** R0S3**

Verification and Alarming for I/O cards

The files in the Data Table are organized by function as follows:

F19: Description (extra)

0-9 1019 2029 3039

0-9 1019 2029 3039

0-9 10-19 20-29 30-39

0-9 10-19 20-29 30-39

0-9 1019 2029 3039

0-9 10-19 20-29 30-39

0-9 10-19 20-29 30-39

0-9 10-19 20-29 30-39

0-9 1019 2029 3039

0-9 10-19 20-29 30-39

General Area Major Device #1 Major Device #2 Major Device #3

Analog Device Subroutine

Not Applicable 03_X_RASP1010_S Not Applicable 03_X_RASP1010_AK

N11:50/13 N10:53/1 N11:72/11 N10:50/7

N10:53/0 N11:50/15 N11:70/5 N11:50/14 N11:70/7 N7:0 N11:21/14 PD30:0.SPS N7:0

Yes Yes Yes No Yes No No No No

Inputs from Field Analog Input Indication

Outputs to Field None

Analog Input Subroutine

No No No No No No No Yes Yes Yes

Yes Yes Yes Yes Yes Yes No No No No

02_I_PTK07011_OH_AK N10:90/0 02_I_PTK07011_OL_AK N10:90/1

Yes Yes Yes Yes

02_I_PTK07011_HH_AK N10:90/3 02_I_PTK07011_H_AK N10:90/4

N10:90/5 N10:90/6 N11:90/0 N11:90/1 N11:90/3 N11:90/4 N11:90/5 N11:90/6

Yes Yes Yes Yes Yes Yes Yes Yes

Inputs from Field Mode Remote Status Running Status Fault

Outputs to Field Command Start

Discrete Device Motor Controls

N11:20/0 N10:20/2 N11:22/7

Yes Yes Yes

N11:22/15 No N10:20/0 B3:12/5 N11:22/9 Yes No No

PST #7 Bay 1&2 Collector Alarm Acknowledge From HMI 7.3.3.3

No Yes No No No Yes Yes Yes Yes Yes Yes Yes Yes

Open/Close Valve Control

03_X_CLAR1100_SA 03_N_CLAR1100_F Not Applicable 03_X_CLAR1100_O

N10:65/1 N11:65/8 N11:65/9 N10:65/2

Yes Yes No Yes

Not Applicable 03_N_CLAR1100_O Not Applicable 03_X_CLAR1100_AK

N11:65/15 No N11:71/0 Yes B3:8/0 N10:65/0 No Yes

03_N_CLAR1100_FO 03_N_CLAR1100_FC 03_N_CLAR1100_UO 03_N_CLAR1100_UC 03_N_CLAR1100_UZ

N11:65/0 N11:65/1 N11:65/2 N11:65/3 N11:65/4

There are no alarms associated with this subroutine.

The General tab has the following options selected:

The Shape Preferences tab has the following options selected:

FIRST SCAN R0S1 R0S2 R0S3**