PCT 1090229

Specification
For
SCADA Standard
Pr9834
Document No: Pr9834
Revision No: 2
Last Review Date: 26/10/2016
Next Review Date: 26/10/2018
Pr9834 - SCADA Standard
Documents Details:
This document is only valid on the day it was printed.
Version Review
Revision Reviewed by Approved by Date approved Revision type
0.1 21/12/2010 Draft for Review
0.2 9/2/2011 Draft for Review
0.3 17/6/2011 Issued for Use
0.4 15/7/2011 General Revisions
1.0 T.Stewart A.Schoenmaker 6/04/2016 Finalisation of review and uploading to
Written Direction
2.0 J.Duncan 26/10/2016 Technical review for next project application
Written Direction Control

Document Sponsor Infrastructure Technical Standards Committee
Document Author (Owner) Manager Capital Delivery, SIS
Subject Matter Expert Control Systems Engineer, Network Operations
References Refer to Section 3 of this document
Document No: Pr9834
Revision No: 2
Contents
1. Purpose......................................................................................................................... 8
2. Scope............................................................................................................................ 8
3. References.................................................................................................................... 8
3.1. General.................................................................................................................8
3.2. Applicable Legislation and Regulation.................................................................. 9
3.3. Codes of Practice (ratified by Legislation)............................................................. 9
3.4. Codes of Practice (not ratified by Legislation)....................................................... 9
3.5. International and Australian Standards................................................................. 9
4. Definitions/Abbreviations.............................................................................................9
5. Common Display Elements........................................................................................ 10
5.1. Colours............................................................................................................... 10
5.1.1 Custom Colours...................................................................................... 10
5.1.2 Trend Pen Colours.................................................................................. 11
5.1.3 System Colours.......................................................................................11
5.2. Symbols and Icons............................................................................................. 12
5.2.2 Alarm Boundary and Alarm Icon..............................................................13
5.2.3 Analog Display and Analog Display with Label........................................ 13
5.2.4 Button Display with Label........................................................................ 14
5.2.5 Button..................................................................................................... 15
5.2.6 Digital Display with Label........................................................................ 15
5.2.7 Setpoint Display with Label..................................................................... 15
5.3. Pipes.................................................................................................................. 16
5.3.2 Main Sewage Flow..................................................................................16
5.3.3 Minor Sewage Flow................................................................................ 16
5.3.4 Chemical Flow........................................................................................ 16
5.3.5 Air Flow...................................................................................................16
5.3.6 Service Water Flow................................................................................. 17
5.4. Fonts.................................................................................................................. 17
5.4.3 Header Selection.................................................................................... 17
5.4.4 Page Title................................................................................................17
5.4.5 Tab Selection.......................................................................................... 17
5.4.6 Device Overview Title............................................................................. 18
5.4.7 Point Label..............................................................................................18
5.4.8 Point Status............................................................................................ 18
Document No: Pr9834
Revision No: 2

5.4.9 Trend Title...............................................................................................18
5.4.10 Trend Label.............................................................................................18
5.4.11 Trend Main..............................................................................................19
5.4.12 Trend Traces.......................................................................................... 19
5.4.13 Alarms and Events.................................................................................. 19
5.4.14 Notes...................................................................................................... 19
6. Alarming...................................................................................................................... 21
6.2. Alarm Displays....................................................................................................21
6.3. Filtering...............................................................................................................21
6.3.1 Quick Filters............................................................................................21
6.3.2 Advanced Filters..................................................................................... 22
6.4. Alarm Priorities................................................................................................... 22
6.4.1 Alarm Priority Responses........................................................................22
6.4.3 Alarm List Colours...................................................................................22
7. Trending...................................................................................................................... 23
7.2. Historic Trends................................................................................................... 23
7.3. Current Trends....................................................................................................24
7.4. Pre-configured Trends........................................................................................ 24
7.5. Trend Points....................................................................................................... 24
8. Historic Archiving and Database Backup................................................................. 24
8.1. Historic Archiving................................................................................................ 24
8.1.3 Archiving Folder...................................................................................... 26
8.2. Database Backup............................................................................................... 26
9. Database Structure..................................................................................................... 26
9.2. Folder Structure.................................................................................................. 26
9.2.3 ~Config Folder........................................................................................ 27
9.2.4 Common Folder...................................................................................... 27
9.2.5 Plant Folder............................................................................................ 27
9.2.6 Major Area.............................................................................................. 27
9.2.7 Sub Area.................................................................................................27
9.2.8 Equipment Group (if required)................................................................. 27
9.2.9 Device.....................................................................................................28
10. Displays.......................................................................................................................28
10.1. Display Hierarchy................................................................................................28
10.1.3 Layer 2 – Area Section Overview............................................................ 29
10.1.4 Layer 3 – Sub-Area Plant Equipment Group Overview............................ 30
This document may not, in whole or part, be copied, photocopied, reproduced Page iv
or translated without prior consent from the CEO, Unitywater.
Printed copies are uncontrolled.
Document No: Pr9834
Revision No: 2

10.1.5 Layer 4 – Device Faceplate.....................................................................31
10.2. Navigation.......................................................................................................... 32
10.2.1 Page Header...........................................................................................32
10.3. Standard Pages.................................................................................................. 33
10.3.1 Server Management................................................................................33
10.3.2 System Management.............................................................................. 34
10.3.3 Historic Archiving and Database Backup Basic Interface.........................35
10.3.4 Disabled Alarms......................................................................................35
10.3.5 Tag Database......................................................................................... 35
10.3.6 Logged on Users.....................................................................................36
10.3.7 Changed Control Points.......................................................................... 36
10.3.8 Power Distribution Page..........................................................................37
10.3.9 UPS........................................................................................................ 37
10.3.10 Communication Page............................................................................. 37
10.3.11 Alarm Page............................................................................................ 38
10.3.12 Event Page............................................................................................ 38
10.3.13 Trend Page............................................................................................ 38
11. Security....................................................................................................................... 39
11.2. Users.................................................................................................................. 39
11.3. User Groups....................................................................................................... 39
11.3.4 Field Staff/Management.......................................................................... 39
11.3.5 STP Operator..........................................................................................39
11.3.6 Senior Operator...................................................................................... 40
11.3.7 Commissioning Engineer........................................................................ 40
11.3.8 SCADA Administrator..............................................................................40
11.3.9 Super-User............................................................................................. 40
11.3.10 Summary Table of ClearSCADA Security Group Privileges.................... 40
12. Operator Workstation Displays..................................................................................42
12.1. ViewX Clients..................................................................................................... 42
12.2. WebX Clients...................................................................................................... 42
List of Tables
Table 1 - Custom Colour Definitions.................................................................................10
Table 2 - Colour Definitions of Trend Pens...................................................................... 11
Table 3 - Alarm Icons in Decreasing Category................................................................. 13
This document may not, in whole or part, be copied, photocopied, reproduced Page v
Document No: Pr9834
Revision No: 2

Table 4 - Standard Font Attributes.................................................................................... 20
Table 5 – Alarm Priorities.................................................................................................. 22
Table 6 - Alarm List Colours..............................................................................................23
Table 7 - Default Compression Settings........................................................................... 24
Table 8 - Top Menu Bar Elements..................................................................................... 33
Table 9 - ClearSCADA Security Group Privileges............................................................ 41
List of Figures
Figure 1 - Document Hierarchy........................................................................................... 8
Figure 2 - System Colour Palette...................................................................................... 12
Figure 3 - Alarm Boundary with Alarm Icon..................................................................... 13
Figure 4 - Analog Display.................................................................................................. 14
Figure 5 -Analog Display with Label................................................................................. 14
Figure 6 - Button Display with Label.................................................................................14
Figure 7 - Control Window.................................................................................................14
Figure 8 - Confirmation Window....................................................................................... 14
Figure 9 - Button................................................................................................................ 15
Figure 10 - Digital Display with Label............................................................................... 15
Figure 11 - Setpoint Display with Label............................................................................ 15
Figure 12 - Control Window...............................................................................................15
Figure 13 - Confirmation Window..................................................................................... 16
Figure 14 - Main Sewage Flow...........................................................................................16
Figure 15 - Minor Sewage Flow......................................................................................... 16
Figure 16 - Chemical Flow................................................................................................. 16
Figure 17 - Air Flow............................................................................................................16
Figure 18 - Service Water Flow......................................................................................... 17
Figure 19 - Example Header Selection Font..................................................................... 17
Figure 20 - Example Page Title Font................................................................................. 17
Figure 21 - Example Tab Selection Font........................................................................... 17
Figure 22 - Example Device Overview Title Font..............................................................18
Figure 23 - Example Point Label Font...............................................................................18
Figure 24 - Example Point Status Font............................................................................. 18
Figure 25 - Example Trend Title Font................................................................................18
Figure 26 - Example Trend Label Font..............................................................................18
Figure 27 - Example Trend Label Font..............................................................................19
This document may not, in whole or part, be copied, photocopied, reproduced Page vi
Document No: Pr9834
Revision No: 2

Figure 28 - Example Trend Trace Font..............................................................................19
Figure 29 - Example Alarms and Events Font.................................................................. 19
Figure 30 - Example Notes Font........................................................................................ 19
Figure 31 – Alarm Page..................................................................................................... 21
Figure 32 - Historic Settings..............................................................................................25
Figure 33 - Event Journal Settings....................................................................................25
Figure 34 - Example Database Hierarchy......................................................................... 28
Figure 35 - Example of a layer 1 display........................................................................... 29
Figure 38 - Example of layer device faceplate..................................................................32
Figure 36 - Example Top Menu Bar...................................................................................32
Figure 36 - Server Management Display........................................................................... 33
Figure 38 - System Management Display......................................................................... 34
Figure 39 - Historic Archiving and Database Backup Basic Interface............................ 35
Figure 40 - Disabled Alarm List......................................................................................... 35
Figure 41 - Tag Database................................................................................................... 36
Figure 42 - Logged on Users List......................................................................................36
Figure 43 - Changed Control Points................................................................................. 37
This document may not, in whole or part, be copied, photocopied, reproduced Page vii
Document No: Pr9834
Revision No: 2
1. Purpose
1.0.1 Unitywater has produced a set of specifications for the supply, development
and implementation of SCADA and PLC systems for its Sewage Treatment Plants
(STPs). The purpose of these specifications is to provide the document users with
clear directions of Unitywater’s requirements and to encourage standardisation.
1.0.2 These specifications have been developed to align with Unitywater’s Water
Supply and Sewerage Reticulation Telemetry SCADA system where appropriate and
with due regard for the international ASM Consortium Guidelines – Effective Operator
Display Design. The figure below shows the structure of this document set.
Figure 1 - Document Hierarchy
SYSTEM DEVICE TYPE SCADA HISTORIAN AND

ARCHITECTURE SPECIFICATIONS STANDARDS REPORTING
SPECIFICATION (SCHNEIDER OR SPECIFICATION SPECIFICATION
SIEMENS)
IMPLEMENTATION
SPECIFICATION
2. Scope
2.0.1 This Specification details the standards to be followed within the SCADA
system. Required Colours and Font types that are to be used are detailed.
Requirements of common symbols and icons that form part of the common SCADA
library are detailed.
2.0.2 The required structure of the SCADA system, including displays and
navigation as well as the underlying database structure is detailed. Requirements of
display of information to the SCADA operator, including alarm information, trends and
standard displays are detailed.
2.0.3 Security is an important consideration for all SCADA implementations and the
required security measures to be implemented are detailed.
3. References
3.1. General
Document Number Title
Pr9833 SCADA and PLC Architecture (formerly UWDMDR-D-TS-0001)
UWDMDR-D-TS-0002 Unitywater Treatment Plant PLC & SCADA Specifications –

Device Type Specification (Schneider PLC)
Pr9834 SCADA Standard Specification (formerly UWDMDR-D-TS-0003) - this
This document may not, in whole or part, be copied, photocopied, reproduced Page viii of 42
Document No: Pr9834
Revision No: 2

Document
Pr9846 SCADA and PLC Historian and Reporting Specification (formerly
UWDMDR-D-TS-0004)
Pr9845 SCADA and PLC – Implementation Specification (formerly UWDMDR-
D-TS-0005)
Pr9844 SCADA and PLC Device Type (Siemens PLC) (formerly UWDMDR-D-
TS-0006)
Pr9835 Electrical Installation at Treatment Plants (formerly UWDSTD-E-TS-

0001)
Pr8843 Unitywater Major Projects Specification for Drawing, Document

and Equipment Tag Numbering
ASM Consortium
Guidelines Effective Operator Display Design 2008
3.2. Applicable Legislation and Regulation

Not applicable.
3.3. Codes of Practice (ratified by Legislation)

Not applicable.
3.4. Codes of Practice (not ratified by Legislation)

Not applicable.
3.5. International and Australian Standards

Not applicable.
4. Definitions/Abbreviations
Term Definition
ASM Abnormal Situation Management
ICS Industrial Control System
Integrator Person/entity responsible for the supply, installation and
commissioning of the control system
PLC Programmable Logic Controller – An Industrial computer used for
automation of electromechanical processes
SCADA Supervisory Control And Data Acquisition
SNMP Simple Network Management Protocol - Application layer protocol
providing network management services
SMS Short Message Service
SOE Standard Operating Environment
UPS Uninterruptible Power Supply
UW Unitywater
This document may not, in whole or part, be copied, photocopied, reproduced Page ii of 42
Document No: Pr9834
Revision No: 2
5. Common Display Elements

5.1. Colours
5.1.1 Custom Colours

5.1.1.1 Custom Colours can be defined in ClearSCADA. The colour of a specific item
or state is then referenced to a custom colour definition, ensuring consistency is
maintained across the project with respect to common colours.
5.1.1.2 The custom colours are stored in a Custom Colour folder located at
~Config.Colours. The following table lists the custom colours that are to be used
Table 1 - Custom Colour Definitions
Application Colour Name RGB Code Flash? Sample
Device – Comms Fault Magenta (255, 0, 255) No
Device – Comms Fault Magenta (255, 0, 255) Yes
Unacknowledged
Sewage Device - Wheat (245, 222, 179) No
Stopped
Sewage Device - Brown (153, 5, 0) No
Running/Active
Service Water Device Light Green (144, 238, 144) No
– Stopped
Service Water Device - Dark Green (0, 100, 0) No
Running/Active
Chemical Device – Light Magenta (255, 183, 255) No
Stopped
Chemical Device - Magenta (255, 0, 255) No
Running/Active
Air Device - Stopped Light Blue (129, 129, 255) No
Air Device - Dark Blue (0, 0, 139) No
Running/Active
Low Alarm Cyan (0, 255, 255) No
Low Unacked Alarm Cyan (0, 255, 255) Yes
Medium Alarm Light Orange (255, 155, 0) No
Medium Unacked Light Orange (255, 155, 0) Yes
Alarm
High Alarm Yellow (255, 255, 0) No
High Unacked Alarm Yellow (255, 255, 0) Yes
Critical Alarm Red (255, 0, 0) No
Critical Unacked Alarm Red (255, 0, 0) Yes
Cleared Unacked Green (0, 204, 0) No
Alarm (All Categories)
Mimic – Text Selected White (255, 255, 255) No
Mimic – Text Black (0, 0, 0) No
Deselected
Background – Level 1 Beige (240, 240, 240) No
Mimic
Mimic
This document may not, in whole or part, be copied, photocopied, reproduced Page iii of 42
Document No: Pr9834
Revision No: 2

Mimic
Flow - Main Sewage Brown (255, 220, 160) No
Flow - Minor Sewage Tumbleweed (255, 255, 200) No
Flow - Air Dark Blue (157, 157, 255) No
Flow – Chemical Magenta (255, 215, 255) No
Flow - Service Water Dark Green (170, 240, 170) No
Symbol Outlines Brown (150, 75, 0) No
Vessels Peru (205, 133, 63) No
Process Variables Black (0, 0, 0) No
Setpoint Background White (255, 255, 255) No
Process Variable No
White (255, 255, 255)
Background
Labels Black (0, 0, 0) No
5.1.2 Trend Pen Colours

5.1.2.1 The following colours have been chosen for use in displaying trend pens as
they are clearly distinguishable from each other. When defining trends, the colours
for the trend pens should be chosen from the table below in the first instance. If
specific trend pen colours that are not listed in the table below are used, the trend
pen colours need to be chosen so that all pens on a trend are clearly distinguishable
from each other.
Table 2 - Colour Definitions of Trend Pens
Application Colour Name RGB Code Sample
Trend Pen Colour 1 Black (0, 0, 0)
Trend Pen Colour 2 Red (255, 0, 0)
Trend Pen Colour 3 Green (0, 128, 0)
Trend Pen Colour 4 Blue (0, 0, 255)
Trend Pen Colour 5 Magenta (255, 0 ,255)
Trend Pen Colour 6 Orange (255, 102, 0)
Trend Pen Colour 7 Brown (153, 51, 0)
Trend Pen Colour 8 Cyan (0, 255, 255)
Trend Pen Colour 9 Violet (128, 0, 128)
Trend Pen Colour 10 Yellow (255, 255, 0)
Trend Pen Colour 11 Bright Green (0, 255, 0)
5.1.3 System Colours

5.1.3.1 System colours are used by the ClearSCADA system to indicate certain
states of items. System colours are defined in ClearSCADA’s colour palette and are
only used to indicate that state, unlike custom colours that can be used anywhere in
the system.
5.1.3.2 System colours can be viewed and changed by right-clicking on an item in the
Database Explorer and selecting the ‘Colour Palette’ menu option. Although
ClearSCADA allows different colour palettes to be defined at different levels of the
database hierarchy, the Unitywater standard requires that only a single colour palette
at the system level is ever modified.
5.1.3.3 The colour palette definitions are to be set to their default values, as shown
below.
Figure 2 - System Colour Palette
This document may not, in whole or part, be copied, photocopied, reproduced Page iv of 42
Document No: Pr9834
Revision No: 2
5.2. Symbols and Icons

5.2.1 For descriptions and graphical representations of the standard process
equipment symbols and icons, please refer to the relevant Device Type Specification.
Common symbols used throughout the system, often being embedded in the process
equipment faceplates, are described below.
5.2.2 Alarm Boundary and Alarm Icon

5.2.2.1 The Alarm Boundary and Alarm Icon shall be used together to indicate the
This document may not, in whole or part, be copied, photocopied, reproduced Page v of 42
Document No: Pr9834
Revision No: 2

highest alarm state for a particular object. Unacknowledged alarms of any priority are
a higher state than Acknowledged alarms of any priority. For example, an object with
a Low Unacknowledged alarm and a Critical Acknowledged alarm both active would
display the Low Unacknowledged indication.
5.2.2.2 The Alarm Boundary shall be a rectangle surrounding the entire object. The
Alarm Icon shall be located in the top left hand corner of the alarm boundary.
Figure 3 - Alarm Boundary with Alarm Icon
5.2.2.3 The colour of the Alarm Boundary and Alarm Icon shall be as per Table 2-1
Custom Colour Definitions. The shape of the Alarm Icon shall be as displayed in the
table below. If there are no active alarms for the object then the alarm border and
alarm icon shall be hidden. Unacknowledged cleared alarms will not be indicated by
the alarm boundary or alarm icon.
Table 3 - Alarm Icons in Decreasing Category
Highest Active Alarm Icon
Critical Alarm
High Alarm
Medium Alarm
Low Alarm
5.2.3 Analog Display and Analog Display with Label

5.2.3.1 The Analog Display, Analog Display with Label and Analog Display with point
colour are used to indicate analog process values within the system. These symbols
are used to display values including the correct units that provide feedback from the
system and cannot be modified by the SCADA operator. The standard ClearSCADA
display menu shall be displayed if the rectangle containing the analog value is clicked
This document may not, in whole or part, be copied, photocopied, reproduced Page vi of 42
Document No: Pr9834
Revision No: 2

on. The Analog displays are shown below.
Figure 4 - Analog Display
Figure 5 -Analog Display with Label
5.2.4 Button Display with Label

5.2.4.1 The button display with Label is used to control a digital point within the
SCADA system.
Figure 6 - Button Display with Label
5.2.4.2 When the rectangle displaying the current state of the point is clicked, the
standard ClearSCADA display menu is displayed. When the button with the tool icon
is clicked, a control window for the point is displayed. The desired state of the point
from the provided drop down menu can be changed and ‘OK’ selected to change the
state of the point. If the ‘Cancel’ button is selected, the point will remain unchanged.
Figure 7 - Control Window
5.2.4.3 If the value of the point is changed and the ‘OK’ button pressed, a
confirmation window will be presented to users with ‘Confirm Actions’ selected in their
user configuration. To proceed with the selected control the ‘Yes’ button on the
confirmation window must be pressed. If the No button is pressed, the window is
closed and the point remains unchanged.
Figure 8 - Confirmation Window
5.2.5 Button
5.2.5.1 A Button is used to control a digital point to a value of 1. A Button is shown
This document may not, in whole or part, be copied, photocopied, reproduced Page vii of 42
Document No: Pr9834
Revision No: 2

below.
Figure 9 - Button
5.2.6 Digital Display with Label

5.2.6.1 A Digital Display with Label is used to represent the two states of a digital
point with text descriptions. The standard ClearSCADA display menu shall be
displayed if the rectangle displaying the current point state is clicked on. The Digital
Display with Label is shown below.
Figure 10 - Digital Display with Label
5.2.7 Setpoint Display with Label

5.2.7.1 The Setpoint Display with Label is used to control an analog point within the
SCADA system.
Figure 11 - Setpoint Display with Label
5.2.7.2 It displays the current value of the setpoint including the correct units. When
the rectangle displaying the current value of the point is clicked, the standard
ClearSCADA display menu is displayed. When the button with the tool icon is clicked,
a control window for the point is displayed. The desired value of the point from the
provided drop down menu can be changed and ‘OK’ selected to change the value of
the point. Entered values must be within the range indicated in brackets to the right of
the input text box. If the ‘Cancel’ button is selected, the point will remain unchanged.
Figure 12 - Control Window
5.2.7.3 If the value of the point is changed and the ‘OK’ button pressed, a
confirmation window will be presented to users with ‘Confirm Actions’ selected in their
user configuration. To proceed with the selected control the ‘Yes’ button on the
confirmation window must be pressed. If the ‘No’ button is pressed, the window is
closed and the point remains unchanged
This document may not, in whole or part, be copied, photocopied, reproduced Page viii of 42
Document No: Pr9834
Revision No: 2

Figure 13 - Confirmation Window
5.3. Pipes
5.3.1 All piping shall be depicted by one of two pipe styles described below. A solid
line shall be used to depict all piping with no shading or other three dimensional
effects. The colour of the piping shall indicate the process material conveyed by the
pipe.
5.3.2 Main Sewage Flow

5.3.2.1 The main sewage flow shall be depicted by a solid line of 5.00 point width.
The colour of the main sewage flow shall be as detailed in section 2.1.1 Custom
Colours.
Figure 14 - Main Sewage Flow
5.3.3 Minor Sewage Flow

5.3.3.1 All minor sewage flows shall be depicted by a solid line of 3.00 point width.
The colour of minor sewage flows shall be as detailed in section 2.1.1 Custom
Colours.
Figure 15 - Minor Sewage Flow
5.3.4 Chemical Flow

5.3.4.1 All chemical flows shall be depicted by a solid line of 3.00 point width. The
colour of chemical flows shall be as detailed in section 2.1.1 Custom Colours.
Figure 16 - Chemical Flow
5.3.5 Air Flow

5.3.5.1 All air flows shall be depicted by a solid line of 3.00 point width. The colour of
air flows shall be as detailed in section 2.1.1 Custom Colours.
Figure 17 - Air Flow
This document may not, in whole or part, be copied, photocopied, reproduced Page ix of 42
Document No: Pr9834
Revision No: 2
5.3.6 Service Water Flow

5.3.6.1 All service water flows shall be depicted by a solid line of 3.00 point width.
The colour of minor process flows shall be as detailed in section 2.1.1 Custom
Colours.
Figure 18 - Service Water Flow
5.4. Fonts
5.4.1 Text is used in many places throughout the SCADA system. The font styles
are chosen to be easily readable without dominating or cluttering the displays.
Different font styles are defined for different text applications to allow easy
recognition of information type by SCADA users.
5.4.2 The different pre-defined Font styles are explained in the following sections,
with a summary table at the end.
5.4.3 Header Selection

5.4.3.1 The Header Selection Font is used in the header menu bar for each of the
menu options.
Figure 19 - Example Header Selection Font
5.4.4 Page Title

5.4.4.1 The Page Title Font is used at the top of each page.
Figure 20 - Example Page Title Font
5.4.5 Tab Selection

5.4.5.1 The Tab Selection font is used for Tab headings. This includes the
Alarms/Events Table Footer and Faceplates.
Figure 21 - Example Tab Selection Font
This document may not, in whole or part, be copied, photocopied, reproduced Page x of 42
Document No: Pr9834
Revision No: 2

5.4.6 Device Overview Title
5.4.6.1 The Device Overview Title font is used at the top of each Device Overview.
Figure 22 - Example Device Overview Title Font
5.4.7 Point Label

5.4.7.1 The Point Label font is used on the left of point displays to indicate to the
SCADA operator the function of the point that is displayed. The Point Label is used in
the Analog Display, Button Display, Button Inhibit, Button Reset, Digital Display and
Setpoint Display Symbols.
Figure 23 - Example Point Label Font
5.4.8 Point Status

5.4.8.1 The Point Status font is used where the status of a point is indicated with
Text. The Point Status font is used in the Analog Display, Button Display, Button
Inhibit, Button Reset, Digital Display and Setpoint Display symbols.
5.4.8.2 The colour of the point status font will vary depending on the quality of the
connected point. The colour will change to the colour defined in the Colour Palette for
the current quality of the connected point.
Figure 24 - Example Point Status Font
5.4.9 Trend Title

5.4.9.1 The Trend Title font is used for the title that appears above Trends. Its
Orientation and Alignment are not able to be set.
Figure 25 - Example Trend Title Font
5.4.10 Trend Label

5.4.10.1 The Trend Label font is used to Label the Y Axis of Trends. Its Orientation,
Alignment and Colour are not able to be set.
Figure 26 - Example Trend Label Font
This document may not, in whole or part, be copied, photocopied, reproduced Page xi of 42
Document No: Pr9834
Revision No: 2
5.4.11 Trend Main

5.4.11.1 The Trend Main font is used to Label the scaling of the trend axes, as well as
labelling the X axis and other text annotated on trends. Its Orientation, Alignment and
Colour are not able to be set.
Figure 27 - Example Trend Label Font
5.4.12 Trend Traces

5.4.12.1 The Trend Traces font is used to indicate the details of each trace at the
bottom of trends. No attributes are able to be modified. The colour of the text will be
the same as the pen colour of the trace it represents.
Figure 28 - Example Trend Trace Font
5.4.13 Alarms and Events

5.4.13.1 The Alarms and Events font is used in the Alarms and Events tables. This
includes on the Alarms and Events tabs on the Information Section of the page
footer, as well as the standard ClearSCADA Alarms and Events pages.
Figure 29 - Example Alarms and Events Font
5.4.14 Notes
5.4.13.1 The Notes font is used in the Notes tab on the Information Section of the page
footer.
Figure 30 - Example Notes Font
This document may not, in whole or part, be copied, photocopied, reproduced Page xii of 42
Document No: Pr9834
Revision No: 2
Pr9834 - SCADA and PLC Standard

Table 4 - Standard Font Attributes
Application Family Height Orientation Style Vertical Horizontal Colour Sample
Alignment Alignment
Header Arial 10 pt. Left to Right Bold Centre Centre Black RGB(0,0,0) Header
Selection Selection
Site Overview Arial 20 pt. Left to Right Bold Centre Centre RGB(71, 71, 71) Site Overview
Title Title
Tab Selection Arial 10 pt. Left to Right None Centre Centre White RGB(255, 255, Tab Selection
255)
Device Arial 16 pt. Left to Right Bold Centre Left White RGB(255, 255, Device
Overview Title 255) Overview Title
Device Arial 10 pt. Left to Right Bold Centre Left White RGB(255, 255, Device
Overview 255) Overview
Description Description
Point Label Arial 10 pt. Left to Right None Centre Left Black RGB(0,0,0) Point Label
Point Status Arial 10 pt. Left to Right None Centre Centre Variant dependant on Point Status
point quality
Trend Title Arial 12 pt. - Bold - - Black RGB(0,0,0) Trend Title
Trend Label Arial 12 pt. - Bold - - - (Black RGB(0,0,0)) Trend Label
Narrow
Trend Main Arial 10 pt. - None - - - (Black RGB(0,0,0)) Trend Main
Narrow
Trend Traces - - - - - - As per Trend Colour
Table
Alarms / Events - - - - - - See custom Colours Alarms /
Table Font (Tahoma (10 pt.) Table Events Table
) Font
Notes Arial 10 pt. Left to Right None Top Left Black RGB(0,0,0) Notes
This document may not, in whole or part, be copied, photocopied, reproduced or translated without prior consent Page xiii of 42
from the CEO, Unitywater.
Document No: Pr9834
Revision No: 2
6. Alarming
10.1.1 The standard ClearSCADA alarms and events functionality is used for
processing alarms and events. Specialised displays have been developed for SCADA
operators to view and manage alarms and events.
6.2. Alarm Displays

6.2.1 A specialised Alarm page has been developed which provides separate
panes for critical and non-critical alarms and easy access to quick filters. The alarm
page will display all alarms in the system unless filters have been applied. Where a
ViewX client has multiple monitors, it is expected that one monitor will normally
display the alarm page.
6.2.2 Functionality shall be provided to acknowledge all non-critical alarms in the
same area as the selected non-critical alarm. From the Alarm page, Critical alarms
shall only be able to be acknowledged individually.
Figure 31 – Alarm Page
6.3. Filtering
6.3.1 Quick Filters
6.3.2.1 Quick filters are provided on the Alarm page. These allow easy application of
filters to only display alarms related to specific areas. Quick Filters are compounding,
meaning that subsequent filters will only display alarms that are also displayed by the
higher level filter. The Quick Filter options provided are:
a. Major Area;
b. Sub Area;
c. Filter Reset – This will remove all active filters.
This document may not, in whole or part, be copied, photocopied, reproduced Page xiv of 42
Document No: Pr9834
Revision No: 2

6.3.2 Advanced Filters
6.3.2.1 Advanced filtering capability for each embedded alarm list is provided through
the default ClearSCADA filtering functionality. Advanced filters are managed via
the ‘Filter Window’ provided by ClearSCADA.
6.3.2.2 The filter window is accessible by right clicking on the desired alarm list and
selecting the ‘Filter’ option from the displayed menu. Custom Advanced Filters set
via the Filter Window apply only to the Alarm List that is selected, and can only be
removed using the Filter Window.
6.4. Alarm Priorities

6.4.1.1 Four alarm priorities have been established to allow SCADA operators to
easily distinguish and appropriately action the different severities of alarms within
the system. The four alarm priorities are:
Table 5 – Alarm Priorities
Priority Description
400 Critical
300 High
200 Medium
100 Low
6.4.1 Alarm Priority Responses

6.4.2.1 Critical Alarms require an operator to take action immediately regardless of
the time of day. All Critical priority alarms shall be configured to page to the on call
operator via a Redirection action on the root folder of the ClearSCADA database.
6.4.2.2 High Alarms require an operator to take action relatively quickly, but an
immediate response is not required.
6.4.2.3 Medium Alarms may require an operator to take action at some point in the
future.
6.4.2.4 Low Alarms need to be brought to the operator’s attention and may need
further investigation. This typically includes a change in system or plant status.
6.4.2.5 Cleared alarms that have not been acknowledged remain visible in the alarm
lists until they are acknowledged.
6.4.3 Alarm List Colours

6.4.3.1 The relevant alarm colour shall be used to colour the Alarm Lists.
Unacknowledged alarms shall have black text on a coloured background.
Acknowledged alarms shall have the text colour set to the alarm colour. The table
below indicates how each type of alarm will appear in the alarm list.
This document may not, in whole or part, be copied, photocopied, reproduced Page xv of 42
Document No: Pr9834
Revision No: 2

Table 6 - Alarm List Colours
Alarm Type Foreground Background Flashing Sample
Low Active UnAck Black Light Blue No Low
Low Cleared UnAck Black Light Blue No Low
Low Active Acked Light Blue Black No Low
Low Acked with Response Light Blue Dark Grey No Low
Medium Active UnAck Black Orange No Medium
Medium Cleared UnAck Black Orange No Medium
Medium Active Acked Orange Black No Medium
Medium Acked with Response Orange Dark Grey No Medium
High Active UnAck Black Yellow No High
High Cleared UnAck Black Yellow No High
High Active Acked Yellow Black No High
High Acked with Response Yellow Dark Grey No High
Critical Active UnAck Black Red No Critical
Critical Cleared UnAck Black Red No Critical
Critical Active Acked Red Black No Critical
Critical Acked with Response Red Dark Grey No Critical
7. Trending
7.1 The built in trending functionality of ClearSCADA will be utilised. ClearSCADA provides
three different trend types – Historic Trends, Current Trends and Pre-configured
trends.
7.2. Historic Trends

7.2.1 All points with the historic feature enabled are able to be displayed on a historic
trend. Historic trends can be accessed by selecting ‘Display Historic Trend’ from a
points display menu. Note that this selection is only available on points that have their
‘historic’ feature enabled.
7.2.2 A historic trend will show a single trace of the selected point on a trend axis. Historic
values of the point can be viewed, as far back as history for the point exists within the
ClearSCADA system.
7.3. Current Trends

7.3.1 A current trend can be displayed for any point in the system. Current trends
can be accessed by selecting ‘Display Current Trend’ from a points display menu.
This document may not, in whole or part, be copied, photocopied, reproduced Page xvi of 42
Document No: Pr9834
Revision No: 2

7.3.2 A current trend will show a single trace of the selected point on the trend axis.
On opening the current trend, only the current value of the point will be displayed
against the current time. Subsequent values of the point will continue to be displayed
on the current trend, and will continue to be trended until the current trend is closed.
All of the stored data displayed on a current trend is lost as soon the current trend is
closed.
7.4. Pre-configured Trends

7.4.1 A preconfigured trend is a definable object in the ClearSCADA database.
Multiple traces can be defined to be displayed on a single trend axis. Colours of the
individual traces shall be set as described in section 5.1.2Trend Pen Colours. Pre-
configured trends shall be defined for all processes as required.
7.5. Trend Points

7.5.1 Both Analog and Digital points can be trended by the system. The default
compression settings for analog and digital tags are shown below. In some instances
the default compression settings will not provide an appropriate level of detail or will
not result in appropriate disk usage for trend data storage. In these instances
appropriate compression settings are to be chosen.
Table 7 - Default Compression Settings

Trend Type Enabled Significant Significant Minimum
Change Type Change Value Interval
Analog Yes Percentage of 0.5 1 second
Span
Digital No
8. Historic Archiving and Database Backup

8.1. Historic Archiving
8.1.1 Historic Data Archiving is important in the SCADA system to reduce required
disk storage and improve system performance. Deleting old data is also important to
maintain disk storage requirements. Archived data can easily be copied from the
server to another location, able to be mounted back on to the server if the data is
required to be viewed in the future.
8.1.2 Archiving Settings
8.1.2.1 ClearSCADA archiving settings are defined in the configuration settings of the
server.
8.1.2.2 Historic Data shall be enabled, with the value of ‘keep online for’ set to 105
weeks. Archiving of historic data shall be enabled, with the ‘Archive after’ value set to
12 weeks.
8.1.2.3 Event Journal shall also be enabled, with the value of ‘keep online for’ set to
27 weeks. Archiving of the event journal shall be enabled, with the ‘Archive after’
value set to 4 weeks.
8.1.2.4 These settings will result in all historical data being available for at least 2
This document may not, in whole or part, be copied, photocopied, reproduced Page xvii of 42
Document No: Pr9834
Revision No: 2

years and all event journal data being available for at least half a year. Data older
than this shall be automatically removed from the system, but can be viewed by
mounting archives.
8.1.2.5 After data has been made available for archiving (12 weeks for historical data,
4 weeks for event journal), it can no longer be modified or deleted manually. After this
time however, it can be archived for future use.
Figure 32 - Historic Settings
Figure 33 - Event Journal Settings
8.1.3 Archiving Folder

8.1.3.1 There shall be a history archiving folder located at ~Config.Backups.History
Archiving. This folder shall contain an archive history object named ‘Archive’ that
This document may not, in whole or part, be copied, photocopied, reproduced Page xviii of 42
Document No: Pr9834
Revision No: 2

performs the archiving. This object shall be set up to archive data to C:\Archive on
the Primary and Secondary servers.
8.1.3.2 Even after the data has been deleted, the archive containing the data can be
mounted to allow viewing of the data as if it were still part of the historic files. When
the mounted archive is no longer needed to be viewed, it must be dismounted.
Mounting and Dismounting can be performed from the Historic Archiving and
Database Backup Basic Interface located on the System Management page. For
further information, refer to section 8 Historic Archiving and Database Backup Basic
Interface.
8.2. Database Backup

8.2.1 The Database shall be automatically backed up on a daily basis. The
database backups folder is located at ~Config.Backups.Database Backup.
8.2.2 A script in the database backups folder shall perform the backup of the
database files. The backups shall be stored at C:\ClearSCADA\Database\Backups
directory on the server hard drive. Any Database Backups more than 31 days old
shall be automatically deleted to conserve disk space.
8.2.3 In addition to the automatic Database Backup, a manual Database Backup
can be performed. A button is provided on the System Management page for this
purpose, see section 9.3 System Management. Any manual database backups will
be stored in the same location and will automatically deleted after 31 days
9. Database Structure
9.1.1 The naming of the Database objects shall conform to the standard detailed below.
The standard has been developed to provide short and meaningful names so that
users of the system can quickly and easily identify every piece of equipment referred to
in the SCADA system.
9.2. Folder Structure

9.2.1 The database structure shall incorporate the asset naming convention
detailed in Pr8843 Unitywater Major Projects Specification for Drawing, Document
and Equipment Tag Numbering and integrate with the convention developed for
Unitywater’s Water Supply and Sewerage Reticulation Telemetry SCADA system.
9.2.2 The Database shall be structured as follows:
 ~Config
 Common
 Plant
o Major Area
 Sub Area
 Equipment Group (if Required)
o Device
9.2.3 ~Config Folder

9.2.3.1 The ~Config folder shall contain all of the standard colour definitions,
symbols, templates, users and other system objects that are used in the
implementation of the SCADA project. The ~Config folder shall exist in the root group
of the database, and shall not be modified by the System Integrator without
This document may not, in whole or part, be copied, photocopied, reproduced Page xix of 42
Document No: Pr9834
Revision No: 2

authorisation from Unitywater.
9.2.3.2 If site specific symbols, templates or other objects are required then a ~Config
folder shall be created underneath the Plant folder (same level as Major Area) with a
similar structure to the main ~Config folder.
9.2.4 Common Folder

9.2.4.1 The Common folder shall contain other system objects such as alarm mimics
and server management related objects used in the implementation of the SCADA
project. The common folder shall exist in the root group of the database.
9.2.5 Plant Folder

9.2.5.1 The Plant folder shall exist in the root group of the database along with the
~Config and Common folders. The Plant folder shall have a six letter name. The first
three letters shall be based on the location of the treatment plant, e.g. KAW for
Kawana STP. The last three letters shall always be STP for Sewage Treatment Plant.
Thus, the plant folder for the Kawana treatment plant shall be named KAWSTP.
9.2.6 Major Area

9.2.6.1 The Major Area Folder name shall be the abbreviated version of the Major
Area as described in Pr8843 Unitywater Major Projects Specification for Drawing,
Document and Equipment Tag Numbering, prefixed by major the major area number
and a space. Only Major areas that contain equipment shall be included in the
project.
Examples of a major area of plant include Inlet Works (1 NLT), Biological Treatment
(3 BITR) and Chemical Dosing (5 CHEM).
9.2.7 Sub Area

9.2.7.1 The Sub Area Folder name shall be the name of the Sub Area as described in
Pr8843 Unitywater Major Projects Specification for Drawing, Document and
Equipment Tag Numbering, prefixed by the sub area number and a space. If an
abbreviation of the Sub Area is provided in the Drawing and Document Numbering
system then the abbreviation shall be used, otherwise the full English description
shall be used. Only Sub areas that contain equipment shall be included in the project.
Examples of a sub-area of plant include ‘1 Screening’, ‘2 Grit Removal’ and ‘4
Effluent Pump Station’.
9.2.8 Equipment Group (if required)

9.2.8.1 For certain groups of equipment, it is logical to group equipment at a further
degree of granularity than the sub area. In these instances an Equipment Group shall
be used. All devices in an equipment group will have a common first digit of their
sequence numbers, and this digit will be the folder name. Typical examples of this
would be for multiple Balance Tanks or Clarifiers, each Tank would have its own
equipment group database folder.
9.2.9 Device
9.2.9.1 There shall be a device template instance or folder for every major piece of
equipment. The name of the instance or folder shall be the major equipment item tag
name. A folder shall only be used where there is more than one template instance
This document may not, in whole or part, be copied, photocopied, reproduced Page xx of 42
Document No: Pr9834
Revision No: 2

associated with that item of equipment, for example a pressure switch directly
associated with a pump.
9.2.9.2 Equipment common to a number of pieces of major equipment will be
instantiated at the same level as the Device Folders. An example would be a
common blower header pressure instantiated at the same level as multiple blower
device folders, with each blower and the associated local discharge over pressure
switch instantiated within the blower device folder.
Figure 34 - Example Database Hierarchy
10. Displays
10.1. Display Hierarchy
10.1.1 Each display depicting process equipment shall be implemented as one of the
layers described below. Common pages, such as dedicated trend displays and
diagnostic utilities, shall have dedicated pages that are accessed outside of the
process display hierarchy described below.
10.1.2 Layer 1 – Plant Overview
10.1.2.1 Layer 1 displays provide an overview of the complete plant. Major plant
process values, such as flows between major sections of the plant, shall be shown.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxi of 42
Document No: Pr9834
Revision No: 2

Indication of the current highest priority alarm state of each major section of plant
shall be provided. Navigation shall be provided to each major section of plant by a
single click on its depiction on the Layer 1 Display. There shall be a single Layer 1
display for each plant.
This display shall consist of a ‘Mimics’ folder at the root level of the plant folder,
containing ‘Overview’ and ‘Overview Content’ mimics, generally as per the ‘Mimics’
folder of template ‘StandardMimics’.
Figure 35 - Example of a layer 1 display
10.1.3 Layer 2 – Area Section Overview

10.1.3.1 Layer 2 displays provide an overview of an area of the plant. This
corresponds to a Major Area in Pr8843 Unitywater Major Projects Specification for
Drawing, Document and Equipment Tag Numbering, and hence the Major Area in the
Database Hierarchy. Examples of an area of plant include Inlet Works (INLT), Biological
Treatment (BITR) and Chemical Dosing (CHEM).
10.1.3.2 Where there are equipment groups contained in an Area, the Area display
shall be an overview of the equipment groups. Indication of the current highest priority
alarm state for each equipment group of plant shall be provided. Navigation shall be
provided to each equipment group of plant by a single click on its depiction on the Layer
2 Display. The Layer 2 display shall display animated representations of major pieces of
equipment and process values. Minor pieces of equipment shall not be displayed.
10.1.3.3 Where there are no equipment groups contained in an Area, the Area display
will be a detailed representation of the Area. Every piece of equipment shall be displayed
with full animation.
10.1.3.4 There shall be a single layer 2 display in each of the area database folders, in
the ‘Mimics’ sub-folder. Navigation to each Layer 2 Display shall be provided from the
drop down menu accessed from the ‘Area’ button on the Page Header.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxii of 42
Document No: Pr9834
Revision No: 2

Generally, each Major Area folder would be instanciated as an instance of the
‘StandardMimics’ template, then converted to a Group to create the required ‘Mimics’
folder.
10.1.4 Layer 3 – Sub-Area Plant Equipment Group Overview
10.1.4.1 Layer 3 displays provide detailed information about all equipment within a sub-
area of the plant. Layer 3 displays shall show each piece of equipment in an area with
full animation. Additionally, the representation of each piece of equipment shall allow
direct navigation to the Layer 4 Faceplate display for that piece of equipment.
10.1.4.2 There shall be a single layer 3 display in each of the equipment group
database folders, in the “Mimics” sub-folder. Navigation to each Layer 3 Display shall be
provided from the drop down menu accessed from the ‘Sub-Area’ button on the Page
Header.
Generally, each Sub-area folder would be instanciated as an instance of the
‘StandardMimics’ template to create the required ‘Mimics’ sub-folder.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxiii of 42
Document No: Pr9834
Revision No: 2

10.1.5 Layer 4 – Device Faceplate
10.1.5.1 Layer 4 displays shall be faceplate popups that provide all available
information about a specific piece of equipment and provide device control as detailed in
the relevant Device Type Specification.
10.1.5.2 When a device faceplate is accessed, it will appear within an inset window,
which can be repositioned on the screen as desired by the SCADA operator. Multiple
device faceplates can be accessed simultaneously, and positioned on the screen to
allow all to be viewed simultaneously.
10.1.5.3 All device faceplates are to initially be displayed in the same position on the
screen and be of the same width. To achieve this, the inset position shall be configured
with the following settings:
a. Left – 5%
b. Top – 5%
c. Width – 20%
d. Height – 0%
10.1.5.4 These settings will result in the device faceplate being initially displayed 5% of
the page width in from the left hand side of the screen and 5% of the page height in from
the top of the screen. The width of the device faceplate will be 20% of the width of the
screen and the height of the device faceplate will be as required to maintain the
proportions of the device faceplate.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxiv of 42
Document No: Pr9834
Revision No: 2

Figure 38 - Example of layer device faceplate
10.2. Navigation
10.2.1 Page Header

10.2.1.1 The header of all displays shall be a common menu bar which will provide
navigation throughout the system. An example menu bar with a description of each of
its elements is displayed below.
Figure 36 - Example Top Menu Bar
This document may not, in whole or part, be copied, photocopied, reproduced Page xxv of 42
Document No: Pr9834
Revision No: 2
Table 8 - Top Menu Bar Elements

Identifier Item Description
A Back Button Navigates to the previously viewed display.
Next Button Navigates to the display that was viewed prior to the back button
B
being pressed
C Home Button Navigates to the Plant Overview
Area
Displays a Hierarchical Navigation Menu for all of the Layer 2
D Navigation
Overview Displays.
Button
Sub-Area
Displays a Hierarchical Navigation Menu for all of the Layer 3
E Navigation
Overview Displays.
Button
Overview
F Navigation Navigates between adjacent Layer 2 or Layer 3 Overview Displays.
Buttons
System Button Displays a Navigation Menu for system displays, including Server
G Management, System Management, Power Distribution and
Communications
Reports
H Displays a Menu for accessing available Reports
Button
Alarms Button Displays a Menu of Alarm Views, including Current Alarms, Alarm
I
History, Event History and Disabled Alarms
J User Button Displays a Menu to access Login, Logout and Change Password
Current User
K Displays the name of the user that is currently logged in
Display
Current Time
L Displays the current time of the system
Display
M Print Button Displays the print menu to print the current Overview Display.
Help Button Displays the Legend Popup. The drop down menu provides links to
Manuals and Specifications, option to select between Tag,
N
Description and None to be displayed for devices on mimics and
ViewX help.
10.3. Standard Pages
10.3.1 Server Management

10.3.1.1 The server management page displays the status of the ClearSCADA
servers, including main status, CPU usage and memory usage of servers.
Figure 36 - Server Management Display
This document may not, in whole or part, be copied, photocopied, reproduced Page xxvi of 42
Document No: Pr9834
Revision No: 2
10.3.2 System Management

10.3.2.1 The system management display shall provide control and monitoring of
certain portions of the ClearSCADA system. The top section of the display shall
contain an interface to some historic archiving and database backup functionality as
well as user management. The bottom section of the screen shall contain a tabbed
interface which provides an interface to various lists. Refer to further detail below.
Figure 38 - System Management Display
10.3.3 Historic Archiving and Database Backup Basic Interface
This document may not, in whole or part, be copied, photocopied, reproduced Page xxvii of 42
Document No: Pr9834
Revision No: 2

10.3.3.1 An ‘archive’ button shall be provided that will archive all history and events
that are older than 4 weeks. This functionality will not normally be required, as an
archive will be performed automatically by the system at the start of each month.
10.3.3.2 ‘Mount’ and ‘Dismount’ buttons that shall be provided that allow previously
archived data that has been removed from the server to be re-mounted and
subsequently dismounted from the system.
Figure 39 - Historic Archiving and Database Backup Basic Interface
10.3.4 Disabled Alarms

10.3.4.1 The ‘Disabled Alarms’ tab shall provide a list of all alarms in the system that
are currently disabled.
Figure 40 - Disabled Alarm List
10.3.5 Tag Database

10.3.5.1 The ‘Tag Database’ tab shall provide a list of all tags defined within the
system. This list shall be able to be filtered.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxviii of 42
Document No: Pr9834
Revision No: 2

Figure 41 - Tag Database
10.3.6 Logged on Users

11.3.6.1 The ‘Logged on Users’ tab shall provide a list of all users that are currently
logged in to the system, excluding the super user account.
Figure 42 - Logged on Users List
10.3.7 Changed Control Points

10.3.7.1 The ‘Changed Control Points’ tab shall provide a list of all control points that
have been modified, including the time of the modification and the user that
performed the modification.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxix of 42
Document No: Pr9834
Revision No: 2

Figure 43 - Changed Control Points
10.3.8 Power Distribution Page

10.3.8.1 The site power distribution shall be depicted on the power distribution page.
Multiple pages with navigation links between them may be required to neatly and
clearly display all of the required devices, particularly if there are multiple incoming
mains power connections to the plant. Where state information of power distribution
elements is available to the SCADA system, this shall be animated on the display.
These devices include phase failure relays, circuit breakers, generators, power
meters, DC power supplies and UPS.
10.3.8.2 The power distribution is to depict both the Low Voltage and Extra Low
Voltage distribution systems. The status of all individual switchboard phase failure
relays shall be displayed, in a single-line diagram type format indicating sub-mains
connections where applicable. The status of all power meters shall be displayed on
this page.
10.3.8.3 Generally a symbol with only critical information displays shall be depicted on
the power distribution page with each device symbol linking to a popup page for all
device details.
10.3.9 UPS
10.3.9.1 Each UPS on site is to be depicted on the power distribution page. Selected
UPS Data, gathered via SNMP, is to be displayed in real-time and trended for
historical reference. Required data includes Voltage and Current of each phase of
UPS feed and UPS supply, power of each UPS supply phase, UPS state (including
bypass, mains healthy, on battery, etc.), UPS battery charge.
10.3.10 Communication Page

10.3.10.1 A communications page is to be provided which indicates the connections
between all devices on any communications bus. Multiple communications pages
with navigation links between them may be required to neatly and clearly display all
of the required devices.
10.3.10.2 Asset details and communication health status of all devices shall be depicted
as a minimum.
10.3.10.3 Ethernet switches shall have the following information available as a minimum
This document may not, in whole or part, be copied, photocopied, reproduced Page xxx of 42
Document No: Pr9834
Revision No: 2

via SNMP protocol:
 Switch overall status – online, power supply status, date and time, firmware
version;
 Port status of each port with bandwidth utilization where available;
 Link down alarms for all ports connected to other network switches via fibre or
copper cables.
10.3.10.4 The status for each PLC shall be displayed and alarmed where appropriate
including CPU running/stopped/fault status, PLC clock, hot standby status including
primary/standby/offline status.
10.3.10.5 The status of each Remote I/O rack shall be displayed and alarmed where
appropriate including the communications status.
10.3.10.6 A hyperlink shall be provided to the web page of any devices that have
remote web configuration or monitoring capability.
10.3.10.7 The current time of devices on site, where available, shall be displayed. Any
site time synchronisation controls shall be available to users with sufficient security
access.
10.3.11 Alarm Page

10.3.11.1 For details on the Alarm page please refer to section 4.1 Alarm Displays
earlier in this document.
10.3.12 Event Page

10.3.12.1 An Event page shall be provided that provides smart filtering capabilities. In
addition to pre-defined filters, advanced filtering is required. Advanced filters shall be
able to be saved by users as a favourite and re-used.
10.3.12.2 The minimum pre-defined filters to be available include:
a. Area;
b. Sub-area;
c. Equipment Group;
d. Site;
e. Device;
f. Severity;
g. State;
h. Time;
i. Suppression;
j. Action;
k. User.
10.3.13 Trend Page

10.3.13.1 A standard trend page shall be used for displaying pre-configured and custom
trends. All displayed data shall be laid out in a neat and easy to read manner.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxxi of 42
Document No: Pr9834
Revision No: 2

10.3.13.2 The trend name shall be displayed at all time. A legend shall be provided
detailing the tag name and displayed pen colour of each pen on the trend.
10.3.13.3 Axis details shall be displayed on the Axes of the trend.
11. Security
11.1 The security of the SCADA system shall be managed by providing an
individual user account for every person requiring access to the SCADA system. A
number of User Groups shall be configured, each with specific SCADA privileges
assigned. Each user account shall be assigned to at least one user group, resulting in
each user having access restricted to the privileges allowed for the groups that the
user is a member of.
11.2. Users
11.2.1 Each user that is to have access rights to a SCADA project shall have an
individual user account configured in ClearSCADA. All user accounts shall
authenticate with the Unitywater SCADA Domain.
11.2.2 Each user is required to complete and submit a SCADA User Request form,
once approved Unitywater shall create the local ClearSCADA user and SCADA
Domain user accounts.
11.2.3 All user objects in ClearSCADA shall reside in the ~Config.System.Users
folder.
11.3. User Groups
11.3.1 Consistent User Groups shall be established in each ClearSCADA project to
maintain the consistency of security access across SCADA projects. There shall be
six user groups defined. The required six user groups are:
a. Field Staff/Management;
b. STP Operator;
c. Senior STP Operator;
d. Commissioning Engineer;
e. SCADA Administrator;
f. Install Root (Admin).
11.3.2 The roles of the user groups are explained in the following sections. A
summary table of specific ClearSCADA rights assigned to each group is also
included.
11.3.3 All user group objects in ClearSCADA are to reside in the
~Config.System.User Groups folder.
11.3.4 Field Staff/Management

11.3.4.1 Field Staff and Management have view access of the SCADA system as well
as data acquisition privileges. This allows data analysis and fault investigation via
data export and report creation and scheduling, as well as real time monitoring of the
system.
11.3.5 STP Operator
This document may not, in whole or part, be copied, photocopied, reproduced Page xxxii of 42
Document No: Pr9834
Revision No: 2

11.3.5.1 General STP operators have limited operational control of the system. This
includes full view and data analysis privileges, ability to acknowledge alarms and
control rights for selected device controls and selected setpoints.
11.3.6 Senior Operator
11.3.6.1 Senior STP Operators shall have full operational control of the system. This
includes full view and data analysis privileges, ability to acknowledge and disable
alarms, control rights for all device controls and setpoints, and ability to create
reports.
11.3.7 Commissioning Engineer
11.3.8.1 Commissioning Engineers shall have operational control of the system as well
as the ability to modify the ClearSCADA configuration. They shall not have the ability
to modify historical entries in the system.
11.3.8 SCADA Administrator
11.3.8.1 SCADA Administrators shall have full control of the system and the
ClearSCADA configuration. This includes full device control, setpoint modification,
alarm management, database modifications and configuration folder modifications.
11.3.9 Super-User
11.3.9.1 The Super-User account user is a built-in ClearSCADA user and has full
control and configuration rights for the user. The super user logon should never be
used once the initial database import has been completed. Instead, appropriate
logons shall be assigned to the SCADA Administrator group.
11.3.10 Summary Table of ClearSCADA Security Group Privileges
11.3.10.1 Table 8 - ClearSCADA Security Group Privileges outlines security privileges

for ClearSCADA.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxxiii of 42
Document No: Pr9834
Revision No: 2

Table 9 - ClearSCADA Security Group Privileges
R B C O Ac R M E R P T A M V D D D S D E M C S S
e r o v kn V e a di et r u n o al is is is w ia x a o e y
a o nt er ow i m n t ri o n n di id a a a it g cl n nf c st
d w r ri led e o u N e m e ot fy at bl bl bl c n u a ig u e
s ol d ge w v al ot v ot Li at H e e e e h o si g u ri m
e e/ Al A e R e e e m e is H P A C Li st v e re ty A
R ar l A e s D it H to is oi la o n ic e E d
el ms a la di at s is ry to nt r nt e s C x m
e r r re a to ry s m r o cl in
a m m ct ry s ol nt C
s s s io s r o
e n ol nt
r
ol
Field
  
Staff/Management
STP Operator     
Senior STP
              
Operator
Commissioning             
Engineer
SCADA                         
Administrator
This document may not, in whole or part, be copied, photocopied, reproduced or translated without prior consent from the CEO, Page xxxiv of 42
Unitywater.
Document No: Pr9834
Revision No: 2
12. Operator Workstation Displays

12.1. ViewX Clients
12.1.1 Operator Workstations shall have the ViewX client installed on them. They
shall be configured using the ‘Configure Connections’ application to connect to the
relevant ClearSCADA primary and standby servers.
12.1.2 Operator Workstations may have multiple monitors connected. For these
workstations it is expected that one monitor will have the full alarm list visible most of
the time. The operator shall be able to use this screen to view other pages if desired,
that is, the system shall not prevent the operator from navigating away from the full
alarm list. Navigation anywhere in the system will be available on each screen of a
multiple monitor system independently. There will be no automatic yoking of screen
displays to each other.
12.2. WebX Clients

12.2.1 The servers shall be configured to support WebX connections. WebX allows a
ClearSCADA client connection to be made to the server using a web browser. These
connections will typically be made by operations management personnel from remote
locations, i.e. not at the treatment plant.
12.2.2 WebX shall be configured to only allow Secure HTTP (HTTPS, port 443)
connections.
This document may not, in whole or part, be copied, photocopied, reproduced Page xxxv of 42

PCT 1090229

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PCT 1090229

Încărcat de

Drepturi de autor:

Formate disponibile

Specification

Pr9834 - SCADA Standard

Written Direction Control

Pr9834 - SCADA Standard

Pr9834 - SCADA Standard

Pr9834 - SCADA Standard

Pr9834 - SCADA Standard

Pr9834 - SCADA Standard

Pr9834 - SCADA Standard

SYSTEM DEVICE TYPE SCADA HISTORIAN AND

UWDMDR-D-TS-0002 Unitywater Treatment Plant PLC & SCADA Specifications –

Pr9834 - SCADA Standard

Pr9835 Electrical Installation at Treatment Plants (formerly UWDSTD-E-TS-

Pr8843 Unitywater Major Projects Specification for Drawing, Document

3.2. Applicable Legislation and Regulation

3.3. Codes of Practice (ratified by Legislation)

3.4. Codes of Practice (not ratified by Legislation)

3.5. International and Australian Standards

Pr9834 - SCADA Standard

5. Common Display Elements

5.1.1 Custom Colours

Pr9834 - SCADA Standard

5.1.2 Trend Pen Colours

5.1.3 System Colours

Pr9834 - SCADA Standard

5.2. Symbols and Icons

5.2.2 Alarm Boundary and Alarm Icon

Pr9834 - SCADA Standard

5.2.3 Analog Display and Analog Display with Label

Pr9834 - SCADA Standard

Figure 4 - Analog Display

Figure 5 -Analog Display with Label

5.2.4 Button Display with Label

Figure 7 - Control Window

Pr9834 - SCADA Standard

5.2.6 Digital Display with Label

Figure 10 - Digital Display with Label

5.2.7 Setpoint Display with Label

Figure 11 - Setpoint Display with Label

Figure 12 - Control Window

Pr9834 - SCADA Standard

5.3.2 Main Sewage Flow

Figure 14 - Main Sewage Flow

5.3.3 Minor Sewage Flow

Figure 15 - Minor Sewage Flow

5.3.4 Chemical Flow

Figure 16 - Chemical Flow

5.3.5 Air Flow

Figure 17 - Air Flow

Pr9834 - SCADA Standard

5.3.6 Service Water Flow

Figure 18 - Service Water Flow

5.4.3 Header Selection

Figure 19 - Example Header Selection Font

5.4.4 Page Title

Figure 20 - Example Page Title Font

5.4.5 Tab Selection

Figure 21 - Example Tab Selection Font

Pr9834 - SCADA Standard

Figure 22 - Example Device Overview Title Font

5.4.7 Point Label

5.4.8 Point Status

Figure 24 - Example Point Status Font