Professional Documents
Culture Documents
TRIM: HW2009-2368/2/31/.001
This Standard Technical Specification was developed by Hunter Water Corporation to be used for the
design, construction/installation and/or maintenance of facilities that are, or are to become, the property
of Hunter Water Corporation. It is intended that this Standard Technical Specification be used in
conjunction with various other standard and project specific drawings and design requirements as
defined by Hunter Water Corporation for each particular project.
Hunter Water Corporation does not consider this Standard Technical Specification suitable for use for
any other purpose or in any other manner. Use of this Standard Technical Specification for any other
purpose or in any other manner is wholly at the user's risk.
Hunter Water Corporation makes no representations or warranty that this Standard Technical
Specification has been prepared with reasonable care and does not assume a duty of care to any
person using this document for any purpose other than stated.
In the case of this document having been downloaded from Hunter Water Corporation's website;
- Hunter Water Corporation has no responsibility to inform you of any matter relating to the accuracy of
this Standard Technical Specification which is known to Hunter Water Corporation at the time of
downloading or subsequently comes to the attention of Hunter Water Corporation.
- This document is current at the date of downloading. Hunter Water Corporation may update this
document at any time.
Copyright in this document belongs to Hunter Water Corporation
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 1 of 62
TRIM: HW2009-2368/2/31/.001
Purpose .................................................................................................................. 7
Interpretation ......................................................................................................... 7
2.1
3.2
3.3
Definitions............................................................................................................ 10
Legislative Requirements................................................................................. 11
5.1.2
Standards ........................................................................................................ 11
5.2
5.3
Contractors ............................................................................................................. 11
5.4
5.5
PLC ....................................................................................................................... 13
6.1
6.2
6.3
6.4
PLC IP Address....................................................................................................... 13
6.5
6.5.2
PLC Program................................................................................................... 14
6.5.3
6.5.4
6.5.5
6.5.6
6.5.7
6.6
6.7
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 2 of 62
6.8
Alarms .................................................................................................................... 19
6.9
Analog Alarms......................................................................................................... 19
6.9.1
6.10
6.10.1
6.10.2
6.10.3
SCADA Code............................................................................................... 20
Security ............................................................................................................... 21
6.11.1
6.11.2
PLC ............................................................................................................. 21
6.11.3
SCADA ........................................................................................................ 21
7.2
7.3
6.11
TRIM: HW2009-2368/2/31/.001
7.4
7.5
DNP3 ...................................................................................................................... 23
7.5.1
7.5.2
SCADA ................................................................................................................. 24
8.1
8.2
8.3
8.4
8.4.2
8.5
8.5.2
8.5.3
8.6
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 3 of 62
Telemetry Configuration................................................................................... 29
8.6.2
8.6.3
8.6.4
8.7
Alarm ...................................................................................................................... 30
8.7.1
8.7.2
Views .............................................................................................................. 32
8.8
TRIM: HW2009-2368/2/31/.001
Commissioning........................................................................................................ 32
HMI ....................................................................................................................... 33
9.1
9.2
9.2.2
9.2.3
9.2.4
9.2.5
9.2.6
10.2
10.2.1
10.3
11 COMMUNICATIONS ............................................................................................. 42
11.1
11.1.1
11.1.2
11.1.3
11.2
11.3
DNP3 .................................................................................................................. 42
11.4
11.5
11.6
Peer-to-Peer communications.............................................................................. 44
11.6.1
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 4 of 62
TRIM: HW2009-2368/2/31/.001
11.6.2
11.6.3
FIGURES
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 5 of 62
TRIM: HW2009-2368/2/31/.001
APPENDICIES
Appendix A.
Appendix B.
Appendix C.
Appendix D.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 6 of 62
TRIM: HW2009-2368/2/31/.001
Purpose
This document describes Hunter Water requirements for the configuration and programming of the
SCADA and Automation systems. The scope includes:
PLC
RTU
SCADA
HMI
All work shall comply with this standard using the software packages and versions as defined by Hunter
Water.
Hunter Water shall not be bound to check any documents or software code submitted for errors,
omissions or compliance with the requirements of the specification or standards.
All code produced for Hunter Water remains the property of Hunter Water. Hunter Water retains the right
to refuse the use of code due to any non-conformance.
Interpretation
For the purposes of this Standard Technical Specification, except where the context requires otherwise:
'Drawings' means the drawings detailing the work involved in the particular project in hand.
Include means including but not limited to, and is used to provide clarification or examples of the
type and nature of items intended
'Specification' means the Specification detailing the work involved in the particular project in hand.
Code means the software programs related to the particular project in hand.
Standards means applicable industry standards include the Australian Standards (AS),
Australian / New Zealand Standards (AS/NZS), American National Standards Institute (ANSI) and
ISO Standards (ISO)
'Standard Technical Specifications' means the Hunter Water Corporation technical specifications.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 7 of 62
TRIM: HW2009-2368/2/31/.001
'Standard Code' means the Hunter Water Corporation standard code libraries.
Headings are for the convenience of the reader and shall not be used in the interpretation of this
Standard Technical Specification.
Specific requirements, including those in the Specification or Drawings, take precedence over general
requirements.
Unless the context requires otherwise any expression such as "give notice", "submit", "approval", or
"directed" means give notice to, submit to, approval by, or directed by the person nominated by the
Principal or Purchaser.
Approval does not imply acceptance of responsibility by Hunter Water for compliance with this technical
specification. Unless approval has been issued in writing approval has not been granted.
Failure to comply with the requirements of this specification or any referred documentation may result in
rejection. Where equipment and / or manufacture are rejected, notice will be given by Hunter Water in
writing. All associated rectification work shall be completed by the Contractor at their cost.
2.1
Order of Precedence
Specific requirements, including those in project specifications or Standard Drawings take precedence
over this Standard Technical Specification. Any deviation from this Standard Technical Specification shall
be approved in writing on a case by cases basis by Hunter Waters Document Owner.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 8 of 62
3
3.1
TRIM: HW2009-2368/2/31/.001
The document owner of this STS is the Hunter Water Manager Asset Management.
3.2
Any request for a variation to STS550 shall be made in accordance with the change management
process in Hunter Water Asset Standards Management Plan.
The Document Owner shall approve in writing the issue of any updated version of STS550.
3.3
Contractor Responsibilities
Ensure that all; works carried out complies with relevant Hunter Water standards. Where a non
compliance is required, approval shall be obtained from the STS Document Owner.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 9 of 62
TRIM: HW2009-2368/2/31/.001
Definitions
Where the following term, abbreviation or expression occurs in this STS, it is defined as follows, unless
the context implies otherwise:
Term / Abbreviation / Expression
Definition
Approved
Approved Product
Automation
Directed
HO
Head Office
HWACL
HWPCL
HWSCL
Hunter Water
Indicated
Non Standard
Refers to code that does not exist within the Hunter Water Automation and
Control Library
PLC
Proprietary
RTU
SCADA
Telemetry
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 10 of 62
TRIM: HW2009-2368/2/31/.001
General Requirements
5.1
Legislative Requirements
o
Codes of Practice
Standards
The Work Health and Safety (WHS) Act, NSW, 2011 (WHS Act),
Work Health and Safety Regulation, NSW, 2011 (WHS Regulation) and
Key aspects of these legislative requirements are provided in STS 600 General Mechanical
Requirements, Section 5.1.
5.1.2 Standards
Any Standards relevant to SCADA and automation equipment supplied to and operated by Hunter Water
shall apply, including specific Standards or suites of applicable Standards referenced in STS500.
5.2
Quality Accreditation
Any SCADA and automation equipment should be designed, manufactured, and where practicable,
installed and commissioned by an organisation with a quality management system accredited as
compliant with ISO 9001:2008 Quality management systems Requirements.
5.3
Contractors
Use only contractors listed on the Hunter Water Approved Contractors List available on the Hunter Water
Corporations website on www.hunterwater.com.au.
5.4
Use only equipment and materials listed on the Hunter Water Approved Products and Manufacturers List
-Electrical available on the Hunter Water website:
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 11 of 62
TRIM: HW2009-2368/2/31/.001
www.hunterwater.com.au
All materials and equipment used shall be from items stocked within Australia and shall be from local
suppliers within the Newcastle region who provide support services for their products.
Where items are described by reference to a trade brand name or catalogue number, such a description
is intended to indicate the type, quality, appearance and method of construction required. An item of a
similar or equal standard may be incorporated in the works, subject to written Approval.
5.5
Computer Equipment
Computers used for software development shall have adequate and current anti-virus software and all
operating system security patches shall be within 2 weeks of manufacturers release.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 12 of 62
TRIM: HW2009-2368/2/31/.001
PLC
Remote (outside treatment plant or pumping station) downloading or modification of the program
configuration of a PLC is not permitted
6.1
For treatment plants, the PLC hardware will be selected to meet the site / project requirements.
For pumping stations, the standard PLC hardware used is detailed within the Hunter Water drawing sets
and is available from Hunter Water upon request.
6.2
Have a comment block placed at the beginning of each page. It will contain section name, code
designer name, date, version number and an overview of code operation
Have each functional area on the page separated by a header (comment block) that contains the
name of the functional area and is to be equal in width to the code being produced as a minimum
Where code requires additional comments, comments are to be placed above the area of code
where appropriate
Have variable names displayed in full, blocks and interconnecting lines not overlapping
6.3
PLC Software
Use the Current version of Unity Pro. Where a later version of Unity Pro is released during the term of a
contract, and this new version has been released for a minimum of three calendar months, then at the
time of final commissioning the latest version shall be used.
6.4
PLC IP Address
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 13 of 62
6.5
TRIM: HW2009-2368/2/31/.001
Examples:
Burwood Beach WWTW, equipment name/number is STBUR. PLC file names will be:
o
STBUR.sta
STBUR.dtx
STBUR.stu
Mayfield 2 WWPS, equipment name/number is SSMAY460. PLC file names will be:
o
SSMAY460.sta
SSMAY460.dtx
SSMAY460.stu
STBUR
o
Project Name
o
SSMAY460
o
Project Comment:
o
Project Name
Project Comment:
Mayfield 2 WWPS
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 14 of 62
TRIM: HW2009-2368/2/31/.001
System - contains I/O mapping and communications routines between the PLC and other devices
Process Area Process Area is the top logical level for the treatment process. It contains the
following hierarchical levels: Cells, Units, Equipment Modules and Control Modules
Cell
(Inlet Works)
Unit
(Screenings)
Equipment
(Screen Conveying 1)
Control Module
(Screen Conveyor 1)
Inlet Works contains Inflow Balance Tank, Screenings, and Grit Removal Units.
The Screenings Unit contains equipment modules such as Screen Conveyor 1 and Screen
Conveyor 2.
Screen Conveyor 1 contains the basic control modules such as sensors and motors.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 15 of 62
TRIM: HW2009-2368/2/31/.001
A software object, which is used for regulatory control or other control functions, e.g. a PID loop,
a timer or a counter.
Example: MF1203
For Water and Waste Water Pumping Stations, the P&ID tag number is not available. Use the same
naming convention, replacing the P&ID tag number with an appropriate 4 digit number.
Example: MV1234 is the PLC variable name for Variable Speed Drive 1234.
The function of Control Module pins shall be identified in the Control Module Function Block.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 16 of 62
TRIM: HW2009-2368/2/31/.001
Where an internal variable without a physical connection to the block is used, the variable is to be
addressed using the Function Block name as the reference. If the name is more than one word, the
Function Block name shall be written as a single word with the first letter of each wrd un upper case.
Example: MV0001.SpeedReference
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 17 of 62
6.6
TRIM: HW2009-2368/2/31/.001
PLC Code
Hunter Water has a Standard Code Library (HWSCL) to standardised PLC programming and SCADA. All
code within this library shall be made available on request.
The library has two sections:
A list of the Function Blocks and templates within the library and the above files can be requested from
Hunter Water at:
ithelp@hunterwater.com.au
The HWPCL contains all mapped addresses between the PLC,RTU and SCADA. For treatment plants,
this must be filled out and provided to Hunter Water.
All PLC Function Blocks (except communications blocks) are matched to a corresponding template in
SCADA. The documentation provided with each block will detail its corresponding template.
All Function Blocks are Read Only. Read Only is provided for debugging only. Read Only programs are
not provided as a basis for programming of additional blocks.
An example of the type of information that will be provided by Hunter Water is available in Appendix A
Example PLC Function Block Documentation
6.7
Function Blocks may be developed if the required code does not exist within the HWSCL. As a minimum:
The first routine in each block shall be structured text. This routine shall be called Main and shall
contain revision history for the block as well as detailed block information (as per block
documentation). It shall not to contain code.
The new Function Block may contain Function Blocks from the default unity library. Where code
is required from an existing Hunter Water Function Block, the code will be made available. The
Hunter Water Function Block is not to be used inside a new Function Block.
The code will only use the following IEC61131 programming formats listed below. These formats
are presented in order of usage preference.
o
Function Block
Structured Text
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 18 of 62
TRIM: HW2009-2368/2/31/.001
Display all required inputs and outputs required for code debugging
Separated by a header that contains the name of the functional area and comments on
the code operation
Function Block comment shall briefly describe the Function Block operation
All variables within the Function Block are to include comments describing the operation of the
variable. . The comment should indicate the operation of the state of the variable. For example,
1 = healthy
Documentation shall use the template provided in Appendix A Example PLC Function Block
Documentation
CST_<Function Name>
o
6.8
Example: CST_ABC
Alarms
Alarm categories are defined for the asset type by Hunter Water and shall be confirmed during the
development of the PLC program.
WWPS alarms defined below are provided for example only:
6.9
Analog Alarms
Alarms shall not be generated off set points within the PLC.
The analog value is mapped to the RTU and passed to the SCADA system where the alarms are
generated.
Alarms must be place within DNP3 classes as appropriate.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 19 of 62
TRIM: HW2009-2368/2/31/.001
Should inform the programmer prior to modification of the existing PLC Code to minimise
interruption to the development of the new PLC Code.
Shall provide to the programmer the modified existing PLC Code and description and/or screen
shots of the modifications.
Should inform the programmer prior to modification of the existing SCADA Code to minimise
interruption to the development of the new SCADA Code.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 20 of 62
TRIM: HW2009-2368/2/31/.001
Shall provide to the programmer the modified existing SCADA Code and description and/or
screen shots of the modifications.
6.11 Security
6.11.1 Function Blocks
All code blocks within the HWACL are password protected and are Read Only
6.11.2 PLC
A Hunter Water 81.3 key is required for physical access to the PLC.
6.11.3 SCADA
Keys to access the SCX SCADA servers shall be issued on an as needs basis and shall be returned
upon project completion.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 21 of 62
TRIM: HW2009-2368/2/31/.001
7.1
For treatment plants, the RTU hardware will be arranged to meet the site requirements.
For Pump Stations, the standard RTU hardware layout is in the Hunter Water Standard Drawings. These
drawings are available from Hunter Water upon request. These drawings should be used as a reference
for hardware configuration of non Pump Station sites.
7.2
RTU Software
7.3
RTU Code
Hunter Water shall provide two files that contain the full set of mapped addresses and two ISaGRAF
applications.
Where backup control is required, it must be enabled through the site parameter table within the
core functional group of the PLC.
The HWPCL contains all mapped addresses between the PLC,RTU and SCADA
7.4
<Equipment Number>.rtu
<Equipment Number>.uif
RTU Addressing
The RTU configuration file will be provided as part of the HWACL. The RTU requires an IP address and a
DNP address provided by Hunter Water
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 22 of 62
7.5
TRIM: HW2009-2368/2/31/.001
DNP3
DNP3 supports several data types, e.g. binary input and analog input, and the corresponding events,
e.g. binary input change and analog change.
Class Description
Analogs are used for information only
Event Type
Poll Rate
Buffered
N/A
4h
Unsolicited
1,000
30 min
Buffered
1,000
2h
Buffered
10
30 min
In addition:
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 23 of 62
TRIM: HW2009-2368/2/31/.001
SCADA
Hunter Water has developed a Standard Coding Library. Refer to Section 6.6 for details.
to ensure standardised programming of the SCADA system,
8.1
SCADA Software
The ClearSCADA application shall be maintained at not less than the first service release of the current
major version.
Following the release of a new major version is released, Hunter Water is unlikely to upgrade until the first
Service Pack of that major version is released.
Additional service releases (for the current major version) will be installed if required by Hunter Water to
address bug fixes or to add new functionality that may be present in the service release.
8.2
The SCADA database structure is defined to ensure all database objects are managed within the
appropriate location. The main database is HO SCADA which monitors the whole network. For HO
SCADA, refer to the following table:
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 24 of 62
TRIM: HW2009-2368/2/31/.001
Description
~Config
~Config.Comms
~Config.Colours
~Config.Database Queries
~Config.Redirections
~Config.Reports
Database-wide reports
~Config.Schedules
~Config.Settings
~Config.Symbols
Mimic symbols
~Config.Templates
Database templates
~Config.Templates.Common
~Config.Templates.Equipment
~Config.Templates.Proc
~Config.Templates.Zone
Site templates
~Config.Users
Database users
~General Information
Bulk Distribution
Bulk Source
Coalfields
Dungog Shire
East Lakes
Newcastle
Not Commissioned
Port Stephens
Weather Monitoring
West Lakes
Worker Duress
WTP
WWTW
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 25 of 62
8.3
TRIM: HW2009-2368/2/31/.001
The SCADA site structure (treatment plants) is to reflect the program structure of the PLC.
A standard table of descriptors is provided in Appendix D Variable Descriptors table. This table is to be
used for the creation of object names as detailed below.
SCADA sites (treatment plants) are created by instancing a site template inside the appropriate zone
group. Site templates are developed using approved equipment templates and reflect the program
structure of the PLC.
All full point names within SCADA require the following naming convention:
<Zone>.<Site>.<Equipment>.<Point>
Definition
Example
<Zone>
Newcastle
<Site>
The name of the site and the name of the site template instance
Sandgate 2 WWPS
<Equipment>
The name of the device on site and the name of the equipment template
instance
Pump 1
<Point>
Auto
This structure (from <Site> down) can be found within the HWACL.
Additionally, the - group contains points which are not displayed on a SCADA Mimic except via the
provided additional list. Any points added to the site instance must be added to these - groups.
8.4
SCADA equipment templates are created and configured to match an appropriate PLC Function Block.
Site templates are then developed using a combination of equipment templates and additional common
(SCADA only) templates for further SCADA functionality.
Development of new SCADA Templates requires Approval.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 26 of 62
TRIM: HW2009-2368/2/31/.001
<Template Name>.<Point>
Definition
Example
<Template
Name>
The name of the name of the SCADA template object as well as the name
of the PLC Function Block
HUNTER
WATER_DOL_PUMP
<Point>
The name of the device attributes or database point within the template that
refers to the appropriate PLC variable
Auto
Any animated symbols, popups, faceplates, or other Mimics for the equipment template are to
be added to this Graphics instance
A - group
o
Any points in the template which are not displayed on a popup or faceplate are to be located
within this group
Any Mimics developed must adhere to standards outlined in Section 8.5 SCADA Mimic/Screen
Development.
Property overrides for the new template shall be limited and only where appropriate.
Name
Definition
Example
<Template
Name>
HUNTER
WATER_ZONE_WWPS
<Equipment
Instance>
The name of the instanced equipment template used as part of the site
Pump 1
<Point>
The name of the device attributes or database point within the template
that refers to the appropriate PLC variable
Auto
Additional points that are required in the site template are to be added to the - group of each equipment
instance.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 27 of 62
TRIM: HW2009-2368/2/31/.001
A blank mimic named Custom Content where the Document Content property is property
overridden in the template
A trend object named Standard Trends, configured with traces Hunter Water deems to be
standard for the site template
Any Mimics developed must adhere to standards outlined in Section 8.5 SCADA Mimic/Screen
Development.
Property overrides for the new template shall be limited and only where appropriate.
The device and device indication is to be provided on the template in the correct position
All points are to be tested and commissioned as far as practical and then placed Out of Service.
Notes added to SCADA to detail expected availability dates for the device where possible.
Where equipment has been provisioned for but not installed, the following applies:
The device and device indication is to be provided on the template in the correct position
Notes added to SCADA device object to explain that this device is for future provisioning.
8.5
Colours shall be referenced to existing SCADA colour objects (~Config.Colours), where possible.
If the symbol or display contains functionality upon click, it must have a black outline or border if
clicking on the object results in anything other than a standard object menu.
Tahoma font.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 28 of 62
TRIM: HW2009-2368/2/31/.001
Colours shall be referenced to existing SCADA colour objects (~Config.Colours) where possible
Tahoma font
The Display mimic from the Graphics.Titlebar instance must be embedded at the top of the
page.
All items (except the sky and ground in a background layer) on the screen must have functional
significance. Only objects or devices that are monitored are to be displayed.
General site status displays are to be located to the left of the screen, animated symbols in the
centre, and the Graphics.Custom Content mimic embedded to the right of the screen (the
custom content mimic can be resized in the template to match the available space).
Tahoma font
8.6
After instancing a Hunter Water site template to develop a new site, the following configurations are
required to ensure that all functionality is available.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 29 of 62
TRIM: HW2009-2368/2/31/.001
Configure the Equipment Number (Identification tab) for the site instance object as provided by
Hunter Water. e.g. the Sandgate 2 WWPS template instance object.
Configure the Hydraulic View object (under Graphics.Titlebar) with a link to the hydraulic
overview object as provided by Hunter Water.
Configure the upstream and downstream network sites associated with the site (as provided by
Hunter Water) by populating the Upstream and Downstream string arrays (under
Graphics.Titlebar) with full names of the Overview Mimics for those sites.
The hydraulic symbol for the site (Graphics.Hydraulic) shall be embedded on the hydraulic
overview and displayed to align with other sites both horizontally and vertically, if applicable.
The main menu ($Root.Default) needs to be updated to provide navigation to the site. Configure
the advanced pick-action menu on the appropriate menu button to include a navigation hyperlink
to the overview (Graphics.Overview) of the new site. Ensure sites in the same graphical location
are grouped. E.g. Sandgate; and ensure the menu is displayed alphabetically.
8.7
Alarm
SCADA alarms are standard per device. Alarm and event severities shall be as defined in the template.
Hunter Water shall define alarm severities used for developing new templates. Alarm severities are:
Delayed Low
Delayed Medium
Delayed High
Low
Medium
High
Critical
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 30 of 62
TRIM: HW2009-2368/2/31/.001
If the severity of an alarm is deemed to be one of those that are delayed, the following extra configuration
must be completed once per point:
Direction: Either
When the severity of an alarm is configured, if the object is a DNP3 point, this will dictate the DNP3 class
the point is to be configured with. The following table shows the relationship between SCADA alarm
severity and DNP3 class data that is required.
Table 5: SCADA Alarms
SCADA Alarm Severity
RTU Event
Delayed Low
Enabled
Delayed Medium
Enabled
Delayed High
Enabled Unsolicited
Low
Enabled
Medium
Enabled
High
Enabled Unsolicited
Critical
Enabled Unsolicited
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 31 of 62
TRIM: HW2009-2368/2/31/.001
8.7.2 Views
All points within the SCADA site that are configured with an alarm shall be configured with an Alarm View
and a Default View.
8.7.2.2
Default View
The Default View (inherited from the containing group) must be an overview for the site where the point is
located.
The Default View configuration can be found on the Group tab of the properties of the containing group
object.
8.8
Commissioning
The following items, at minimum, are required before the SCADA site can be moved from the Not
Commissioned group
Equipment Numbers
o
Action Text
o
All upstream and downstream links for a site must be configured if applicable.
Views
o
The Alarm View for each point must be mimic or popup where the alarm is displayed.
The Default View for each point must be the overview for the site where the point is located.
Hydraulic View
o
All points that are configured with an alarm must have Action Text configured.
Network Links
o
All points that are associated with points in the PLC must have an Equipment Number
configured. This also includes the site Equipment Number.
Menu Navigation
o
Menus on the SCADA system must be configured to appropriately provide navigation to the
site.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 32 of 62
TRIM: HW2009-2368/2/31/.001
HMI
Hunter Water uses HMIs throughout the network. When using a HMI or remote terminal, the following
must be adhered to
9.1
Hunter Water has a working HMI project that should to be used as a basis for the creation of all
HMI screens. This HMI project can be provided upon request.
HMI Software
9.2
HMI Programming
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 33 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 34 of 62
TRIM: HW2009-2368/2/31/.001
Ready Green lamp indicates ready (inputs to the TesysT or VSD combined with the internal
status of the TesysT or VSD), Grey indicates not ready.
Note: Ready does not indicate that the drive is ready to start. It is a hardware indication that the field
input wiring to the TesysT or VSD is on AND the TesysT or VSD controllers are ready. It is not an
indication that the drive is ready for a PLC start.
9.2.3 5.2.3
The Plant Status page displays the IDEA cycle setup and settings, the IDEA cycle state and the analogue
instrument readings. Settings cannot be changed and are for display purposes only.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 35 of 62
TRIM: HW2009-2368/2/31/.001
The IDEA cycle setup has 2 modes (day or night). The current mode is indicated by a green
lamp.
The preset times for the cycle stages are shown for each mode and add up to 180 minutes.
The IDEA cycle shows the current plant state with a green lamp.
The analogs group displays the reading of each instrument in as a number from 0-10000 (value sent to
SCADA).
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 36 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 37 of 62
TRIM: HW2009-2368/2/31/.001
The fault history section shows the last 3 faults along with the time and date when they occurred.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 38 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 39 of 62
TRIM: HW2009-2368/2/31/.001
Figure 9: Control Network shows a typical layout of the SCADA and Control Network.
The green and red Ethernet networks are separate networks.
The green line represents SCADA domain communications connection.
The red line represents the Controls Network connection. Devices that can be controlled such as Drives,
Motor Starters, I/Os, are connected to a PLC Ethernet Module via Connexium switches. The PLC
communicates to the SCADA servers via a second and separate Ethernet Module / Port.
At some larger sites, the use of Fibre Optic Connectivity into the SCADA WAN may be used.
As some sites us of Analogue or Digital radio connectivity is used to connect into the SCADA WAN.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 40 of 62
TRIM: HW2009-2368/2/31/.001
The I/O for each device is to be connected as a minimum to different I/O cards.
Where practical, I/O should be connected to a separate rack that does not share a common
power supply with the I/O
If control is carried out over Ethernet (Intelligent Motor Control Centre), each device must be
connected to a separate switch/router.
Communications to the local plant SCADA servers from the PLC is over Modbus TCP
Communications to the HO SCADA servers from the PLC is via a SCADAPack RTU that acts as
a protocol converter/gateway.
CAT 5e STP cable is to be used outside the communications cabinet where interference is
possible For example from variable speed drives
Daisy chaining of Ethernet enabled devices is not permitted. For example variable speed
drives
All structured Optical Fibre cable on existing sites shall be OM1 compliant. For new greenfield
sites the Optical Fibre cable shall be OM3 compliant.OM1 and OM3 cabling shall never be
mixed at any site. This includes Optical Fibre patch leads.
Where devices act in a duty/standby arrangement, the I/O for each device is to be connected to
different I/O cards
CAT 5e STP cable is to be used outside the communications cabinet where interference is
possible For example from variable speed drives
Daisy chaining of Ethernet enabled devices is not permitted. For example variable speed
drives
Communications to the SCADA servers from the PLC is via a SCADAPack RTU that acts as a
protocol converter/gateway.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 41 of 62
TRIM: HW2009-2368/2/31/.001
11 COMMUNICATIONS
11.1 Network Assets
Hunter Water maintains a variety of assets at remote sites. These assets require telemetry systems for
communication to HO SCADA. Remote site assets include:
Pump stations
Reservoirs
Flow Meters
Rain Gauges
In the event of failure of the primary link, communication automatically switches to the secondary link.
11.3 DNP3
Use DNP3 for communication between the RTU and SCADA.
This communication is defined in the HWPCL.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 42 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 43 of 62
TRIM: HW2009-2368/2/31/.001
Ethernet
Modbus serial/TCP
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 44 of 62
TRIM: HW2009-2368/2/31/.001
12 Related Documents
In addition to STS550, all work shall comply with the details as defined in the Hunter Water Corporations
relevant additional Standards.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 45 of 62
TRIM: HW2009-2368/2/31/.001
13 Document Control
Version
Date
Author
Details of change
0.1
25 Oct 13
D Griffin
Final Draft
0.2
01 Nov 13
G Paterson
Format to Corporate
Standard
1.0
26 Feb 14
G Paterson
Approval
Date
Approved
By
Next
Scheduled
Review
18 Dec 14
PRC
Nov 16
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 46 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 47 of 62
TRIM: HW2009-2368/2/31/.001
A.1.1 INPUTS
ICHIN (Int): Input signal. Normally corresponds to a value in raw data coming from the
input/output peripherals.
CHFAILURE (Bool): Indicates, to the block, whether the input channel associated with the CHIN
input has failed (1) or not (0).
HIPV (Real): Maximum permissible value of the measurements high range, in engineering units
(PV output), corresponding to the maximum value (configured in the HIRAW input) of the CHIN
input. Used as the high range by default if the high range has not been modified from the
monitoring subsystem (AINPUT1_CFG.CHIPV).
LOPV (Real): Minimum permissible value of the measurements low range, in engineering units
(PV output), corresponding to the minimum value (configured in the LORAW input) of the CHIN
input. Used as the low range by default if the high range has not been modified from the
monitoring subsystem (AINPUT1_CFG.CLOPV).
EXTPVEN (Bool): Makes it possible to configure the block to accept an analog input in
Engineering Units (EXTPV) when the signals value is 1, or to use the input in raw data (CHIN)
when the signal is set to 0.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 48 of 62
TRIM: HW2009-2368/2/31/.001
A.1.2 OUTPUTS
PV (Real): Calculated measurement value, normally in engineering units. The table below details the
manner in which the block calculates the measurement based on the value of the inputs and of the
AINPUT_ST and AINPUT1_CFG inputs/outputs:
If the calculations resulting value is less than AINPUT1_CFG.CUTOFFPV (and the signal comes from the
CHIN input), the PV output is set to match theAINPUT1_CFG.CLOPV input/output.
A.1.3 INPUTS/OUTPUTS
AINPUT1_ST (AINPUT1_ST_DDT): Provides the necessary data for monitoring the state of the
analog input signal and configuring its simulation when required.
Struct AINPUT1_ST_DDT
End Struct
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 49 of 62
TRIM: HW2009-2368/2/31/.001
End Struct
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 50 of 62
TRIM: HW2009-2368/2/31/.001
SC (AINPUT1_SC_DDT): Provides the most common data required to monitor the analog input
state from the sequential control.
Struct AINPUT1_SC_DDT
End Struct
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 51 of 62
TRIM: HW2009-2368/2/31/.001
Comments to Left
Comment Block
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 52 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 53 of 62
TRIM: HW2009-2368/2/31/.001
Comment Block
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 54 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 55 of 62
TRIM: HW2009-2368/2/31/.001
MCC devices connected via Ethernet are added (Tesys T, VSD, Power Meter)
Page 56 of 62
TRIM: HW2009-2368/2/31/.001
The Reference Variables include strings, digitals and analogs. They are internal variables to the HMI and
used on the Master Template pages.
Typical Reference Variable folders
Each Reference Variable is configured so that the relevant real Equipment Variable can be substituted
into the Reference Variable when the page is opened. The value of Parameter 1 replaces %s in the
reference string. Refer to Page open section for explanation of Parameter 1.
This resultant variable name equals the final real variable name. When the page is opened, the real
Equipment Variable will be displayed.
Eg. If Reference_Variable_Tesys.Name = SSP then
Tesys_SSP.AverageCurrent will be displayed.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 57 of 62
TRIM: HW2009-2368/2/31/.001
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 58 of 62
TRIM: HW2009-2368/2/31/.001
A Master Template page contains all the relevant data for a specific type of device (TesysT, VSD or
Power Meter). It has a mixture of text, digital and analog data.
All variable text or data is configured using the Reference Variables (master internal variable names).
These include title, indication lamps, analog data, fault history with date and time etc.
Typical Tesys T Master Template page
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 59 of 62
TRIM: HW2009-2368/2/31/.001
Fault history is read from the device as a number. This number is converted to text for display. Refer to
Fault List section for details of faults.
Fault history also uses scripts to read various addresses that make up the date and time for the fault in
order to display it in the correct format on the screen. Scripts are configured in Panel Actions as part of
the Master Template page
Main menu
Plant Overview
Plant Status
The Main Menu and Plant Overview pages allow the selection of equipment pages. The button
configuration for each item of equipment has all the Master Template page setup data to allow the Real
Variables data to be passed to all the Reference Variables locations on the page when the page is
opened.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 60 of 62
TRIM: HW2009-2368/2/31/.001
Selecting the Spiral Sieve Screen button the switch settings page is displayed. On this page the String
Set function is used to load strings into Reference Variables. These Reference Variables are used to
pass values to the templates and to create the references to the specific hardware devices.
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 61 of 62
TRIM: HW2009-2368/2/31/.001
Description
Descriptor
Description
Auto
OL
Electrical Overload
AVL
Available
Open
Command to open
CB
Circuit Breaker
Opened
CF
Common Fault
PB
Pushbutton
CLK
Clock
PV
Process Variable
Close
Command to close
RECL
Recloser
Closed
Remote
Remote Control
DTY
REV
Reverse
ERR
Error
RST
Reset
ES
Emergency Stop
Run
Run command
FDB
Feedback
Running
FLT
Fault
SEC
Seconds
FS
Flow Switch
SP
Set point
FTSP
Fail to Stop
SPD
Speed
FTST
Fail to Start
SID
FWD
Forward
Start
Start
HHS
Status
Status
Hi
High
STB
HRS
Hours
Stop
Stop Command
HS
High Sensor
Stopped
Stop Status
HTY
Test
HV
High Voltage
TX
Transformer
ITL
Interlock
Trip
Trip
JF
Jog Forward
TRQ
Torque
JR
Jog Reverse
UL
Under load
LIT
Volts
Voltage
LKS
LLS
Lo
Low
Local
Local Control
LS
Limit Switch
LV
Low Voltage
Man
MIN
Minutes
Warning This document is current at time of printing or downloading. It may be reviewed and amended prior to the noted
review date at the discretion of Hunter Water Corporation.
Version: 1.0
Date Approved: 181214
Page 62 of 62