Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
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.
1 Purpose .................................................................................................................. 7
2 Interpretation ......................................................................................................... 7
2.1 Order of Precedence ................................................................................................. 8
4 Definitions............................................................................................................ 10
6 PLC ....................................................................................................................... 13
6.1 PLC hardware layout ............................................................................................... 13
6.2 PLC Software Layout .............................................................................................. 13
6.3 PLC Software .......................................................................................................... 13
6.4 PLC IP Address....................................................................................................... 13
6.5 PLC Naming Conventions ....................................................................................... 14
6.5.1 PLC Program File ............................................................................................ 14
6.5.2 PLC Program................................................................................................... 14
6.5.3 PLC Functional Group ..................................................................................... 15
6.5.4 PLC Hunter Water Function Block.................................................................... 15
6.5.5 Control Module ................................................................................................ 16
6.5.6 PLC Program Variable ..................................................................................... 16
6.5.7 PLC Program Structure.................................................................................... 17
6.6 PLC Code ............................................................................................................... 18
6.7 Project Specific Code .............................................................................................. 18
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.
8 SCADA ................................................................................................................. 24
8.1 SCADA Software ..................................................................................................... 24
8.2 SCADA Database Structure .................................................................................... 24
8.3 SCADA Point Naming Convention and Site Structure .............................................. 26
8.4 SCADA Template Configuration .............................................................................. 26
8.4.1 Common Templates ........................................................................................ 26
8.4.2 Non-commissioned Equipment ........................................................................ 28
8.5 SCADA Mimic/Screen Development ........................................................................ 28
8.5.1 Symbol Display Mimics .................................................................................... 28
8.5.2 Device Popup Mimics ...................................................................................... 29
8.5.3 Site Overview Mimics ...................................................................................... 29
8.6 SCADA Site Configuration ....................................................................................... 29
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.
9 HMI ....................................................................................................................... 33
9.1 HMI Software .......................................................................................................... 33
9.2 HMI Programming ................................................................................................... 33
9.2.1 Main Menu Page ............................................................................................. 34
9.2.2 HMI Plant Overview Page ................................................................................ 35
9.2.3 5.2.3 HMI Plant Status Page ............................................................................ 35
9.2.4 HMI Plant Power Supply Page ......................................................................... 37
9.2.5 HMI VSD Page ................................................................................................ 38
9.2.6 HMI Alarm Page .............................................................................................. 39
11 COMMUNICATIONS ............................................................................................. 42
11.1 Network Assets ................................................................................................... 42
11.1.1 NextG/ Licensed Digital Radio ..................................................................... 42
11.1.2 900MHz point to point digital radio ............................................................... 42
11.1.3 450MHz Analog UHF/Radio ......................................................................... 42
11.2 Telemetry - Treatment Plants.............................................................................. 42
11.3 DNP3 .................................................................................................................. 42
11.4 PLC to RTU communications ............................................................................... 43
11.5 PLC to remote device communications ................................................................ 44
11.6 Peer-to-Peer communications.............................................................................. 44
11.6.1 Radio Network ............................................................................................. 44
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.
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.
APPENDICIES
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.
This document describes Hunter Water requirements for the configuration and programming of the
SCADA and Automation systems. The scope includes:
PLC
RTU
SCADA
HMI
2 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.
'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.
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.
The document owner of this STS is the Hunter Water Manager Asset Management.
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.
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.
4 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 Product Included on a list prepared by Hunter Water of approved products and
services
HO Head Office
Non Standard Refers to code that does not exist within the Hunter Water Automation and
Control Library
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.
5 General Requirements
Legislative Requirements
o Australian federal, state and local government legislation
o Codes of Practice
Standards
The relevant Commonwealth and New South Wales (NSW) legislation and Local Council Requirements
shall apply to all SCADA and automation equipment supplied to and operated by Hunter Water.
The Designer, Manufacturer, Supplier, and Installer shall be familiar with the requirements of:
The Work Health and Safety (WHS) Act, NSW, 2011 (WHS Act),
Work Health and Safety Regulation, NSW, 2011 (WHS Regulation) and
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.
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.
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.
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.
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.
6 PLC
Remote (outside treatment plant or pumping station) downloading or modification of the program
configuration of a PLC is not permitted
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.
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
An example of code layout is provided in Appendix B Sample PLC Code Layout
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.
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.
PLC program file name is to conform to the naming convention described below:
Burwood Beach WWTW, equipment name/number is STBUR. PLC file names will be:
o STBUR.sta
o STBUR.dtx
o STBUR.stu
Mayfield 2 WWPS, equipment name/number is SSMAY460. PLC file names will be:
o SSMAY460.sta
o SSMAY460.dtx
o SSMAY460.stu
Hunter Water will provide the equipment name/number.
The PLC project name shall use <Facility Equipment Number) format as described above.
The comment field of the PLC project shall display the first line as <Facility Name>. Subsequent lines
may describe any particular feature of that project or shall be left blank.
Examples:
o STBUR o SSMAY460
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.
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.
All Function Blocks within HWACL use the following naming convention:
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.
Control Modules represent a single entity built up of sensors, actuators and control equipment. A Control
Module may represent:
A software object, which is used for regulatory control or other control functions, e.g. a PID loop,
a timer or a counter.
PLC variable names are available on the P&ID.
Where a Function Block of a control module is created, the following naming convention shall be used:
PLC variable names shall use the Control Module names identified on the P&ID .
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.
All variables created are to include a detailed description of their functions. This includes both exposed
and internal Function Block variables. This comment should also include applicable engineering units,
where applicable.
For Booleans, this comment shall indicate the state of the variable when its value is 1 (TRUE)
Where a variable is from physical I/O, the DDT element naming shall use names as referenced in the
electrical drawing set. All all letters in the variable name are in upper case.
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.
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
Treatment Plant PLC Functional View Pumping Station PLC Functional View
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.
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:
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
o Structured Text
o Sequential function chart
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.
Display all required inputs and outputs required for code debugging
Internal naming shall meet the requirements of STS 550
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
For custom Function Blocks, the following naming convention shall be used:
CST_<Function Name>
o Example: CST_ABC
6.8 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:
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.
Digital alarms generated/received by the PLC must be assigned to the correct DNP3 class within the
RTU.
The DNP3 class is dictated by the priority of the alarm.
Prior to programming, a copy of the existing PLC Code shall be requested from Hunter Water.
During the project, operational circumstances may require Hunter Water to modify the existing PLC Code.
Should this occur, Hunter Water:
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.
Where an M340 is used in a pumping station, the station code will be backed up on the SD Card in the
front of the processor.
The SD Card does not automatically backup process data. The backup of process data must ensure the
plant control resumes in a safe manner. Where a new PLC is required, all %MWi values are to be reset to
zero before being restored from the backed up process data
Process data is to be backed up to the SD Card every 4 hours. Where SCADA process values exist, they
will take precedent over the values stored on the SD Card.
Prior to modifying, a copy of the existing SCADA configuration shall be requested from Hunter Water.
During the project, operational circumstances may require Hunter Water to modify the existing SCADA
Code. Should this occur, Hunter Water:
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.
Shall provide to the programmer the modified existing SCADA Code and description and/or
screen shots of the modifications.
6.11 Security
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.
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.
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
For the RTU files provided with the HWACL, the following naming convention will be adopted
<Equipment Number>.rtu
<Equipment Number>.uif
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.
7.5 DNP3
Class Class Description Event Type Event Buffer Size Poll Rate
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.
8 SCADA
Hunter Water has developed a Standard Coding Library. Refer to Section 6.6 for details.
to ensure standardised programming of the SCADA system,
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.
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.
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.
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>
Table 3: SCADA Full Point Names
<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 Pump 1
instance
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.
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.
SCADA common templates fulfil a variety of SCADA only functions. Many of which are used in site
template creation. e.g. A standard mimic title bar. The specific use of these common templates is defined
in the following sections.
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.
<Template Name>.<Point>
Table 4: Equipment Template Names
<Template The name of the name of the SCADA template object as well as the name HUNTER
Name> of the PLC Function Block WATER_DOL_PUMP
<Point> The name of the device attributes or database point within the template that Auto
refers to the appropriate PLC variable
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.
<Equipment The name of the instanced equipment template used as part of the site Pump 1
Instance>
<Point> The name of the device attributes or database point within the template Auto
that refers to the appropriate PLC variable
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.
Where only partial equipment has been permanently installed or allocated (in preparation for a future
expansion), the following applies:
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.
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.
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
After instancing a Hunter Water site template to develop a new site, the following configurations are
required to ensure that all functionality is available.
The outstation object (RTU.Outstation) of a new site instance must be configured in order to match the
on-site hardware configuration. The following information supplied by Hunter Water must be configured:
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.
Data is required within the new site instance in order for the titlebar to function correctly as follows:
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.
All points within the SCADA site that are associated with points in the PLC shall be populated with an
Equipment Number. Equipment Numbers for the point listing shall be provided by Hunter Water.
The Equipment Number configuration is found on the Identification tab of the properties of each point.
Global sections of the SCADA database configuration need to be updated to allow navigation to and from
the site to be consistent with all other sites. The following is required:
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.
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:
Low 3 Enabled
Medium 2 Enabled
All points within the SCADA site that are configured with an alarm shall include Action Text.
The Action Text configuration can be found on the Alarm tab of the properties of each point.
Action Text for the point listing shall be 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.
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.
The Alarm View must be configured with the mimic or popup where the alarm is displayed.
The Alarm View configuration can be found on the Alarm tab of the properties of each point.
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 All points that are associated with points in the PLC must have an Equipment Number
configured. This also includes the site Equipment Number.
Action Text
o All points that are configured with an alarm must have Action Text configured.
Network Links
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.
o The Default View for each point must be the overview for the site where the point is located.
Hydraulic View
o Each site must be configured with a Hydraulic View if applicable.
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.
9 HMI
Hunter Water uses HMIs throughout the network. When using a HMI or remote terminal, the following
must be adhered to
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.
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.
The Menu page displays buttons used to navigate to other graphics pages for plant equipment.
The buttons on the Main Menu page are arranged in three groups, Plant, Power Monitoring and 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.
The Plant Overview page is s a quick reference page that displays the current general status and load of
all individual plant motor driven equipment.
Each item of equipment has a fault, ready and running status as well as load information.
The Plant Overview page has indication for each of the following general conditions of each drive:
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.
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.
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.
The Power Supply page displays power supply real-time readings of current, voltage, power, power factor
and harmonic distortion. No actions are available on this 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.
The VSD page below illustrates the typical setup for a Hunter Water VSD.
The VSD page displays general information about the VSD and the motor, Digital I/O, VSD status and
fault history.
On the Device Overview page indication is as follows
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.
The Alarms page is a standard in built System Error Log page. It will display in built system faults as well
as configured faults for each item of plant equipment.
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.
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.
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.
Where devices act in a duty/standby arrangement, the I/O for each device is to be connected to
different I/O cards
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.
11 COMMUNICATIONS
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
Preferred telemetry systems are summarised below:
Use of NextG requires Approval. Hunter Water will provide a SIM card for use in the modem when NextG
is used.
Use of licensed digital radios requires Approval.
Use 900MHz radio for communication between sites and instruments. Use of 900MHz radio requires
Approval.
Hunter Water is phasing out the use of the 459MHz Analog UHF/Radio network.
New sites shall not use this radio system.
At existing site upgrades, the radio system is to be replaced and decommissioned.
11.3 DNP3
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.
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.
Hunter Water supports a number of protocols for devices communicating with the PLC. These protocols
are listed below:
Ethernet
Modbus serial/TCP
When a site initiates a peer communications, the data is sent out onto the network but rather than being
sent to the drop number of SCADA, its sent to the drop number of the peer site. Everything on the one
repeater hears the data but only the destination outstation will reply.
HO SCADA communicates with sites that have NextG installed directly via SCADApack DNP routing.
Where radio and NextG technologies are not available, use alternative technologies are requried to
provide peer to peer communication. e.g. Microwave or point to point radio systems.
The use of these technologies is defined on a case by case basis and 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.
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.
13 Document Control
Next
Approval Approved
Version Date Author Details of change Scheduled
Date By
Review
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 Final Stakeholder Review 18 Dec 14 PRC Nov 16
Complete
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.
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.
The functional module has the following aspect when imported. It can be used in any of the programming
languages included by Unity, even though it has been specifically designed for use with the FBD
language.
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).
HIRAW (Int): High range of the CHIN input signal.
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.
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.
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.
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.
Function Block Layout this applies to project specific code creation and functional project code
Code neat and logically arranged Header separates the code into functional sections
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.
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.
Comments on each section Comments, where appropriate, can be placed to the right of the 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.
The HMI configuration panel is accessed by the 2 corner method. Pressing and holding on 2 corners will
bring up the display shown below. This page is used for setting up HMI project configuration and general
display attributes. Eg. IP address, screen brightness etc.
Hardware devices are configured using the general configuration screen. This includes the HMI
configuration, Project name, IP address etc.
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.
MCC devices connected via Ethernet are added (Tesys T, VSD, Power Meter)
The master Reference Variables are created in folders (one for each type of template page). These
Reference Variables have no real address. Real variables data is passed to these Reference Variables
when the relevant template 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.
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.
Equipment variables are created in drive specific folders and with the same variable names as the
Reference Variables folder names. They are external variables with real address locations.
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.
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.
Master Template pages are configured as part of the graphics Base Panels pages configuration.
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.
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.
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.
There are 2 types of alarms, System Fault alarms and configured alarms. System Faults are auto
generated by the HMI as inbuilt functions for hardware faults (eg. communications errors).
All configured alarms are setup up in the Real Variables configuration. There is only 1 alarm group
AlarmGroup1
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.
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.