Electrical, Instrumentation, Monitoring and Control Systems Guidelines for Specifications LMW 8.2 S008 ACTEW Water a business name owned by ACTEW Corporation Limited ABN 86 069 381 960.
Table Of Contents 1. Objective... 3 2. Scope... 3 3. Definitions... 3 4. References... 5 5. General... 6 5.1. Document Structure... 6 5.2. Approval Status during Development... 7 5.3. Specification Templates (Under Development)... 7 6. Specification... 8 6.1. Definitions of Specification Sub-Headings... 10 6.1.1. Standard logic:... 10 6.1.2. Tag name prefix:... 10 6.1.3. Location:... 10 6.1.4. Parent asset:... 10 6.1.5. General Description:... 10 6.1.6. ity:... 11 6.1.7. Drawings:... 11 6.1.8. Operator Interfaces:... 12 6.1.9. Operating modes:... 14 6.1.10. Automatic Sequences:... 15 6.1.11. Hard-wired interlocks:... 17 6.1.12. Software interlocks:... 17 6.1.13. Parameters, Alarms and Trends:... 17 6.1.14. Data Reporting:... 38 6.1.15. Control Source:... 39 6.1.16. References:... 39 A. Specification - EXAMPLES... 40 4 Apr 2007 4 2 of 43
4 Apr 2007 4 3 of 43
1. OBJECTIVE The aim of this document is to establish guidelines for the development of Process, System and Equipment Specifications for implementation within ActewAGL Treatment Branch Plant Control and SCADA Systems. Adherence to these guidelines will ensure a uniform standard of Specifications; in particular, appearance, format and content requirements. Adherence to these guidelines will also allow the Specifications to be maintained for the life of the processes, systems and equipment by ensuring that additions and other amendments can be integrated into existing functional specifications. 2. SCOPE These guidelines shall apply to Process, System and Equipment Specifications relating to ActewAGL Treatment Branch Plant Control and SCADA Systems. 3. DEFINITIONS The following abbreviations and definitions are used within these guidelines: Approved Quality Procedure LMWQCC SCADA FOIP HMI Approved by the Principal s Representative. Existing management system procedure, instruction, standards or specifications established by ActewAGL Treatment Branch Lower Molonglo Water Quality Control Centre. Supervisory Control And Data Acquisition. A primary means used to remotely monitor and control industrial processes, predominately from a central control room. Field Operator Interface Panel. A secondary means used to remotely monitor and control industrial processes, predominately closer to the equipment in the field. Human Machine Interface. A means used to remotely monitor and control industrial processes. This could be applied to both SCADA and FOIP. 4 Apr 2007 4 4 of 43
LCS Instrument Loop Local Control Station. A local means to control the equipment, usually located in the immediate vicinity of the related item and commonly consisting of push buttons/lamps/dials, etc An instrument loop consists of all items, cabling or pipe work used to measure, transmit, indicate or process an electrical or pneumatic analogue signal. An instrument loop generally consists of all items linked by a single current, voltage or pneumatic loop. For the purposes of simplicity the term instrument loop terminology may, however, also be extended to cover discrete digital signal control devices which do not relate to a single specific instrument loop or primary equipment item; i.e. Common pressure switch, flow switch, etc. Each instrument loop is identified as per ActewAGL Treatment Branch Quality Procedure TB 8.1 P601 (3.1.3) with reference to TB 8.1 P601 T3. Plant Equipment Item Each major item of plant equipment is identified as per ActewAGL Treatment Branch Quality Procedure TB 8.1 P601 (3.1.2) with reference to TB 8.1 P601 T3. Asset Hierarchy Essentially this procedure states that each item of equipment shall be uniquely identified according to its location and function. An ordered and structured list of plant equipment and instrument loops, with their equipment and loop numbers, arranged into a systematic hierarchy to bring together the various processes and systems within those processes by which the plant functions as a whole. 4 Apr 2007 4 5 of 43
4. REFERENCES ActewAGL Treatment Branch Electrical, Instrumentation, Monitoring and Control System Standards LMW 8.02 S001 Basis of Design LMW 8.02 S006 PLC/RTU Programming Guidelines LMW 8.02 S007 Citect Programming Guidelines ActewAGL Treatment Branch Quality System Procedures 199551 Treatment Identification and Registration of Plant Assets Instruction. TB 8.?? P??? Plant Control and SCADA Systems Software Management & Control TB 8.?? P??? Identification of Plant Control and SCADA Systems Software Miscellaneous EIP RF R007 EIP Report ACTEWAGL Logic Systems Review Phase 2, Specification Guidelines 4 Apr 2007 4 6 of 43
5. GENERAL The purpose of a Specification is to define the requirements of a control and SCADA system with enough clarity to allow a programmer to develop the PLC/RTU application program and the Operator Interface for the facility being controlled. A secondary purpose is to provide maintenance and operational personnel with a clear statement of the role played by each item of the plant and how each item within a system interacts with the other items. 5.1. Document Structure The structure of the Specification is based on the ActewAGL Treatment Branch Asset Hierarchy. A brief overview of the Asset Hierarchy as applicable to the Specification is detailed below: Level 1: Example: LMWQCC Level 2: Plant/Facility Major Processes (grouped by Plant/Facility) Example: Primary Treatment, Tertiary Treatment, Solids Management processes at LMWQCC Level 3: Systems (grouped by Major Process) Example: Backwash Water Supply, Waste Backwash Water systems within the Tertiary Treatment Process Level 4: Individual Items Of Equipment Or Instrument Loops (grouped by System) Example: 5301PU, 5302PU Backwash Supply Pumps, part of the Backwash Water Supply System Each plant/facility, major process, functional system and individual item of equipment and instrument loop shall have a functional specification developed. At the plant/facility and major process level the functional specification will normally be an overview description of the plant/facility or major process and will also identify each of the lower level major processes or functional systems respectively that constitute that grouping. 4 Apr 2007 4 7 of 43
Similarly, at the functional system level, the functional specification shall describe the operation and role of that system in the higher-level process, to which it belongs. The functional specification for each individual item of equipment and instrument loop shall describe in detail all aspects of the operation of that particular equipment item or instrument loop. The specific data and information requirements for each level of Specification are detailed in Section 6 of this document. Further to the requirements of Section 6, an extra component is included in the plant/facility level functional specification to identify the revision status and/or date of issue of the Plant s Asset Hierarchy used for the Specification. In addition to the plant/facility, major process, system and individual equipment/instrument loop components of the ActewAGL Treatment Branch asset hierarchy, the ActewAGL Treatment Branch Specification also includes an ActewAGL Treatment Branch Standards component (at Level 2). This component describes the standard equipment and instrument loop control and SCADA functionality to be applied in the plant control and SCADA systems. The ActewAGL Treatment Plant s Specification shall consist of a number of individual files residing in a common directory (e.g. LMWQCC on Jeeves /LMFunc-Spec). The filenames used shall be as defined by the ActewAGL Treatment Branch Operations & Process Manager based on established practice. The Specification files shall be written in Microsoft Word format. All references to Standard Logic, Sites, Systems, Processes and Equipment (as defined in the Asset Hierarchy) shall be hyperlinked to the appropriate document (refer Attachment A for examples). 5.2. Approval Status during Development During development, all approved text shall be coloured auto (black on a white background, white on a black background). Text submitted for approval shall be coloured blue. Other colours may be applied to text under development, these colours and their usage is not defined. 5.3. Specification Templates (Under Development) ActewAGL is currently developing blank functional specification templates. When available, these will be issued to the functional specification developer so that consistent format/styles are adopted. Until these documents are issued, the functional specification shall use the same formatting styles contained within the examples in Attachment A. 4 Apr 2007 4 8 of 43
6. FUNCTIONAL SPECIFICATION The Specification shall be contained in the descriptive text and tables following the site, process, system and equipment item/instrument loop headings. The information in the specification shall be divided into the following sections using the following subheadings. The detail required is dependant on the aspect being described. The ticks ( ) show the sub-headings required for the various aspects (site, process, system, equipment item/instrument loop). The asterisk (*) indicates where a sub-heading should be included only where required for the particular application. For instance, there may be specific Data Archiving requirement at the site level such as plant throughput or plant availability. Where a required sub-heading has no meaning for that particular level, include the sub-heading with a note that it is Not Applicable. Equipment item - static is for use with items with structure but without plant process control system connections e.g. tanks & channels. Any value within a configurable table cell that is not applicable is not to be left blank, but shall be marked by the symbol -. If an entire row is not applicable, then the row is to be deleted. There is to be a top-level document, defined by the Site/Plant asset hierarchy labelling scheme, (e.g. WWG Googong Water Treatment Plant) linking all the separate documents forming the complete functional specification. See the following example: 4 Apr 2007 4 9 of 43
Sub-headings Site Process System Instrument Loop Equipment Item Equipment Item - Static Level 1 2 3 4 4 4 Standard logic: - - - Tag name prefix: - - - Location: Parent asset: - General description: ity: ** Drawings: * * - Operator interfaces: - Operating modes: - - Automatic sequences: - - Hard-wired interlocks: - - - Software interlocks: - - - Parameters, Alarms and Trends: - - Data reporting: * * * - Control source: - - - - 4 Apr 2007 4 10 of 43
References: * Indicates information is required only where applicable. ** refer O&M manuals for description of functionality The Specification is not limited to the use of the above sub-headings, however, where additional headings are proposed, ActewAGL Treatment Branch shall first approve this. Where multiple systems or equipment items/instrument loops have similar or identical functionality then the functional specification of all system parts shall be fully described. 6.1. Definitions of Specification Sub-Headings A guide to the required content of each of the above elements is provided below. Under each table, extra text may be inserted, where required, to clarify/describe a unique item/process. Examples are displayed in the attachment section. 6.1.1. Standard logic: Indicate if Standard logic functionality is used throughout the Site, Process or System. This section shall provide a link to the ActewAGL Treatment Branch PLC Logic Standards. 6.1.2. Tag name prefix: Identify the prefix to tag names to be used to identify variables in the PLC/RTU programming and the SCADA. Tag names shall be the same for both the PLC/RTU and Citect and be based on the current plant identification systems. 6.1.3. Location: Provide a basic description of where the item is physically located. 6.1.4. Parent asset: List the parent asset of the item, including asset number/identifier and description as defined within the asset master register. 4 Apr 2007 4 11 of 43
6.1.5. General Description: Provide a basic description of the process, system or item/loop including physical description and type, where applicable. If a drive is not started by Direct On Line (D.O.L.) method, then define its method of starting: Eg. Soft Starter or Variable Speed Drive 6.1.6. ity: Describe the role that the process, system or item/loop plays within the plant including process related inputs and outputs. List any nonstandard local controls and indicators. At a system level (Level 3) or above, provide a description and summary of functionality. 6.1.7. Drawings: List the process or electrical drawings applicable to this process, system or unit, including P&I diagrams, networks, schematics, termination drawings, etc. Drawing number and description should correlate with the actual drawing details and attributes recorded within the Drawing Management System (DMS). Refer to Attachment A for worked examples. Drawing type Drawing description Drawing number P&I Diagram/s Description?????-???? Network/s?????-???? Description?????-???? Etc. Schematic/s?????-???? Description?????-???? Etc. IO connection/s Description Description Etc.?????-?????????-?????????-???? 4 Apr 2007 4 12 of 43
6.1.8. Operator Interfaces: Describe, in tabular and text format, the interface display requirements that the Operator needs for the safe and efficient control of this process, system or unit. The standard Operator Interface functionality is defined in LMW 8.2 S007 Citect Configuration Guidelines. SCADA project SCADA page(s) Standard SCADA pop-up used SCADA project 1 name Page 1 name Page 2 name Page 3 name Etc. SCADA project 2 name (if applicable) Page 1 name Page 2 name Etc. FOIP location(s) FOIP page(s) Standard FOIP pop-up used????cp brief description Page 1 name????cp brief description Page 2 name????cp brief description (if applicable) Etc. Page 1 name 4 Apr 2007 4 13 of 43
Location of local controls and indicators 1 st location 2 nd location Refer to Attachment A for worked examples. Description of local controls and indicators brief description of item 1 brief description of item 2 etc brief description of item 1 brief description of item 2 etc E-stop functionality Standard / Shunt trip Standard / Shunt trip 4 Apr 2007 4 14 of 43
6.1.9. Operating modes: Define, in tabular and text format, the operation modes of the process or item/loop, the default operating mode/state and the conditions under which the operating mode/state will be changed. The standard modes of control are defined in LMW 8.2 S001 Basis of Design. Level 3 (System) Mode Description Definition Mode 1 Provide a basic description of the mode List conditions that define the mode Mode 2 Provide a basic description of the mode List conditions that define the mode Mode 3 Provide a basic description of the mode List conditions that define the mode Mode 4 Provide a basic description of the mode List conditions that define the mode Etc. Etc. Etc. Level 4 (Instrument Loop/Equipment Items) Instrument loop Default mode Manual available Automatic available Cascade available Offline available Calibrate available Manual / Auto / Cascade Drives/Valves Default mode Local manual available Remote manual available Automatic available Offline available Local manual / RemoteManual / Auto 4 Apr 2007 4 15 of 43
6.1.10. Automatic Sequences: Identify all automatic sequences this unit performs or takes part in including start permissives, startup sequence, running sequence, shutdown sequence, emergency shutdown sequence, etc. Each item/equipment that is relevant is to be individually referenced, not referred to a generic group of equipment. E.g. do not use Start all lime sludge pumps. Instead, use Start : 1234PU Lime Sludge Pump 1, 1235PU Lime Sludge Pump 2, 1236PU Lime Sludge Pump 3, 1237PU Lime Sludge Pump 4 and 1238PU Lime Sludge Pump 5. Each automatic sequence shall be documented at the appropriate Level : Level 3 (System) where complex system wide sequences control multiple items/loops. Level 4 (Instrument Loop/Equipment Items) where a sequence involves a small number of items/loops that work to support a primary item of equipment. Eg. A pump and its related control valve. The recommended sequence step layout uses a Major step and minor step as follows: Step 0.00 may be used when the Mode is not active. Permissives should start at 0.01. Each separate cycle within each mode should start at 1.01, 2.01, 3.01, etc. The sub-step (i.e. a, b, c, etc) is not part of the sequence, but is used to assist in reading of this document. It is only used on a step with many conditions. MODE 1 SEQUENCES Mode 1 permissives 0.01. Step description. 0.02. Step description: a. Sub-step description, and b. Sub-step description, and c. Sub-step description. 0.03. Step description: a. Sub-step description, or 4 Apr 2007 4 16 of 43
b. Sub-step description. 0.04. Step description. 0.05. Etc. Mode 1 cycle 1 sequence 1.01 Step description. 1.02 Step description: a. Sub-step description, and b. Sub-step description, and c. Sub-step description. 1.03 Step description: a. Sub-step description, and b. Sub-step description. Mode 1 cycle 2 sequence 2.01 Step description. 2.02 Step description: a. Sub-step description, and b. Sub-step description, and c. Sub-step description. 4 Apr 2007 4 17 of 43
2.03 Step description: a. Sub-step description, and b. Sub-step description. 2.04 Step description. 2.05 Etc. The majority of sequences occur at either an equipment or system level, however in some instances a sequence may exist at a process or site level (eg. plant start-up or shutdown sequences) and should be documented at the appropriate level (i.e. Level 1 or 2). Where there are multiple Automatic sequences for a particular system (eg. Filter DAF sequence, Filter Backwash Sequence), each shall be clearly distinguished through the use of a unique title and description (refer template). 6.1.11. Hard-wired interlocks: Define all process related hard-wired interlocks. Refer Attachment A for examples. 6.1.12. Software interlocks: Define all software interlocks. Refer Attachment A for examples. 6.1.13. Parameters, Alarms and Trends: Define any parameters, alarms and trends in tabular format with the default values that shall be used on the first PLC scan. Where applicable, Standard alarms are to be provided for Loops, Drives and Valves. The tables below shall be used in the functional specification and shall not be modified unless ActewAGL gives approval. All rows that are not applicable to the particular item shall be deleted. Refer to Attachment A for worked examples. An introductory sentence may be provided to outline non-standard, relevant information, further to that contained within the table. Refer to Attachment A for worked examples. 4 Apr 2007 4 18 of 43
6.1.13.1. Definition of Alarms Alarms shall be given one of five categories: 1. High (H) - alarms that need immediate attention. 2. Medium (M) - alarms that may interfere with the normal operation of the plant. 3. Low (L) - alarms that are of low importance and do not interfere with the running of the plant. 4. Events (E) - alarms that are not displayed on the alarms page. They appear on the summary page only. Includes events such as pumps starting and stopping. 5. Off-Normal (O) - alarms that are not displayed on the alarms page. They appear on the off-normal alarms page only. Off-normal alarms are for equipment that is not in the normal operating mode. 6.1.13.2. Field inputs Define whether field inputs (inputs that are physically wired to the PLC) that generate an alarm, deliver an active high or active low signal. Typically, most inputs are active high, i.e. a signal is received when the condition is true, e.g. the PLC receives a signal when the pump is running. However, some inputs are wired using a fail-safe method (active low), i.e. a signal is absent when the condition is true, e.g. the PLC loses a signal when an intruder is detected. This method provides additional signal reliability by attracting attention to an input failure, possibly caused by several factors, including; signal power failure, rodent interference or poor wiring. This information is only required for alarms based on direct field inputs, and may be left blank for all other alarms that are internally generated within the PLC. 6.1.13.3. Alarm Triggers An alarm may be generated when a Variable becomes either:, False or some other additional condition/s. The alarm may also have a delay before it is generated. Level 3 (System) Parameters 4 Apr 2007 4 19 of 43
Parameter description Minimum setting Maximum setting Default value Parameter 1 description?? units?? units?? units Parameter 2 description?? units?? units?? units Parameter 3 description?? units?? units?? units Etc.?? units?? units?? units Alarms Variable Field input active low Alarm triggers Alarm 1 description / False / List of combination of conditions initiating alarm Alarm 2 description / False / List of combination of conditions initiating alarm Alarm 3 description / False / List of combination of conditions initiating alarm Etc. / False / List of combination of conditions initiating alarm PLC Alarm delay (sec) Visible on HMI Alarm priority H/M/L/E/O/- H/M/L/E/O/- H/M/L/E/O/- H/M/L/E/O/- Control from HMI Additional notification Note 1: For Alarm Priority, the non-abbreviated description shall be provided in the functional specification document eg. High / Medium / Low / Event / Off-Normal. Refer to Attachment A for worked examples. 4 Apr 2007 4 20 of 43
Level 4 (INSTRUMENT LOOP) Instrument Loop configuration Description Type Process range From Process range To Engineering units Alarm deadband Input?? -?? ma or V / Comms units?? /-?? /- / RTD Type, Class / Virtual / 24 vdc Output?? -?? ma or V / Comms units?? /-?? /- / RTD Type, Class / Virtual / 24 vdc Extended loop parameter 1/ parameter 2 / Etc. Virtual units?? /-?? /- Refer to Attachment A for worked examples. Parameters Parameter description Minimum setting Maximum setting Default Value Visible on HMI Control from HMI Calibrate mode time remaining Yes No Automatic set-point Yes Process Variable Yes (Yes)* Cascade set-point Yes No 4 Apr 2007 4 21 of 43
Controller Output Yes No Manual Output Yes Yes Low Low alarm setting Yes Low alarm setting Yes High alarm setting Yes High High alarm setting Yes Safe value of controller output when Set to?? % / Hold last / loop faulted - No Safe value of controller output when offline Safe value of Analog Output when output module faulted Cut-in 1 Cut-out 1 Cut-in 2 Cut-out 2 Cut-in 3 Cut-out 3 PID Proportional gain Set to?? % / Hold last / - Set to?? % / Hold last / - No No Yes Yes Yes Yes Yes Yes No 4 Apr 2007 4 22 of 43
PID Integral (repeats/second or seconds/repeat) PID Derivative Auxiliary parameter 1 * Process Variable may only be set when the loop is in Calibrate mode. No No Additional information may be inserted here as required, e.g. Extended loop description of parameters or any complex calculations, eg. Cascade set-point, etc. Alarms Low Low alarm Low alarm High alarm High High alarm Variable Not in default mode (Replace default mode with either: Manual, Auto or Cascade) Field input active low Alarm triggers / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm PLC alarm delay (sec) Alarm priority (note (note (note (note Off normal Calibrate mode Off normal Additional notification 4 Apr 2007 4 23 of 43
Variable Field input active low Alarm triggers PLC alarm delay (sec) Alarm priority Offline mode Off normal Additional notification Faulted Event Open wire (note Under range Over range Sample failed (note (note (note IO module fault Medium Loop power supply failed / List of combination of conditions initiating alarm Auxiliary alarm 1 / False / List of combination of conditions initiating alarm (note H/M/L/E/O/- Note 1: For Alarm Priority, the non-abbreviated description shall be provided in the functional specification document eg. High/Medium/Low/Event/Off-Normal/-. Refer Attachment A for worked examples. Level 4 EQUIPMENT ITEM DRIVE 4 Apr 2007 4 24 of 43
Parameters Current Parameter description VSD Frequency Minimum setting Maximum setting Default Value?? Visible on HMI Drive reversible Yes Loadshed enabled No Restore delay preset (sec)?? No Restore delay time remaining (sec) Maximum no. of starts/hr No. of starts remaining within the hour No. of starts/hr time remaining till reset Restart delay preset (sec) Restart delay time remaining (sec) Duty set???? list equip that forms part of the duty set Default duty allocation 1 / 2 / 3 / 4 / 5 / 6 No Yes Yes Yes No Yes Yes No Yes No Control from HMI 4 Apr 2007 4 25 of 43
Parameter description Minimum setting Maximum setting Default Value Duty rotation type Cyclic (every?? operations) / Timed (Day, Time) VSD Contactor Reclosure Delay?? Visible on HMI No No Control from HMI Thermal capacity used Yes Auxiliary parameter 1?? Full listings of parameter settings for VSD s, E3 s, etc to be contained in O&M. Refer to Attachment A for worked examples. Alarms Variable Not in default mode (Replace default mode with either: Local manual, Remote manual or Auto) Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority Off normal Offline mode H/M/L/E/O/- Running Event Additional notification Faulted Event Available False Off normal 4 Apr 2007 4 26 of 43
Variable Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority E-stop lockout CB closed False Off normal Reversing / False Event Interlocked Event Startup sequence failed / List of combination of conditions initiating alarm Shutdown sequence failed Discrepancy trip Thermal overload Thermistor trip CB protective trip / List of combination of conditions initiating alarm If told to run and no running status; or if told to stop and still has running status 2 Additional notification 4 Apr 2007 4 27 of 43
CB residual trip Variable Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority E-stop shunt trip High Low flow / List of combination of conditions initiating alarm Seal failed High discharge pressure Under speed Low suction pressure Low discharge pressure / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm Additional notification 4 Apr 2007 4 28 of 43
Over speed Variable Field input active low Alarm triggers / List of combination of conditions initiating alarm PLC Alarm delay (sec) Alarm priority Load shed active Event No. of starts/hr exceeded Low IO module fault Medium Auxiliary alarm 1 / False / List of combination of conditions initiating alarm H/M/L/E/O/- Smart Motor Protection Test trip Shear pin failed Current imbalance Comms failed Comms idle SMP3/E3/SMC/Micom/- Additional notification 4 Apr 2007 4 29 of 43
Variable Non volatile memory fault Hardware fault Thermistor input trip RTD input Jam protection Stall protection Underload Ground fault Phase loss Thermal overload Field input active low Alarm triggers / List of combination of conditions initiating alarm PLC Alarm delay (sec) Alarm priority Additional notification 4 Apr 2007 4 30 of 43
RTD input Auxiliary alarm 2 Variable Advanced method of starting VSD / Soft-starter fault VSD warning Shear pin failed Jam protection Stall protection Underload Earth fault Field input active low Alarm triggers / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm VSD / Soft starter / List of combination of conditions initiating alarm PLC Alarm delay (sec) Alarm priority H/M/L/E/O/- H/M/L/E/O/- H/M/L/E/O/- Additional notification 4 Apr 2007 4 31 of 43
Phase loss Thermal overload VSD in local Variable VSD comms failed Auxiliary alarm 3 Field input active low Alarm triggers / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm PLC Alarm delay (sec) Alarm priority H/M/L/E/O/- H/M/L/E/O/- Additional notification Note 1: For Alarm Priority, the non-abbreviated description shall be provided in the functional specification document eg. High/Medium/Low/Event/Off-Normal/-. Refer to Attachment A for worked examples. 4 Apr 2007 4 32 of 43
VALVE Parameters Parameter description Safe analog output position when output module faulted Remote analog manual position set point Safe position when offline Safe position when faulted Software interrupter times Duty set Minimum setting Maximum setting Default Value Set to?? % / Hold last / - Set to?? % / Hold last / - Set to?? % / Hold last / - Set to?? % / Hold last / - Move for?? secs then stop for?? secs list equip that forms part of the duty set Visible on HMI Default duty allocation 1 / 2 / 3 / 4 / 5 / 6 /- No Duty rotation type Cyclic (every?? operations) / Timed (Day, Time) Auxiliary parameter 1 No Yes No No No No No Control from HMI Yes 4 Apr 2007 4 33 of 43
Alarms Variable Not in default mode (Replace default mode with either: Local manual, Remote manual or Auto) Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority Off normal Additional notification Offline mode Off normal Closing Event Opening Event Faulted Event Available False Off normal E-stop lockout (note CB closed False H/M/L/E/O/- Fully opened Event Fully closed Event 4 Apr 2007 4 34 of 43
Failed to open Failed to close Variable Field input active low Alarm triggers If told to open and fully opened status has not been reached. If told to close and fully closed status has not been reached. PLC Alarm delay (sec)???? Alarm priority (note (note Additional notification Position loop fault (note Thermal overload Thermistor trip Monitor relay fault (In Local or faulted) / False / List of combination of conditions initiating alarm (note (note H/M/L/E/O/- Interlocked Event Discrepancy trip If told to open and no opening status; If told to close and no closing status; or if told to stop and still has opening or closing status. 2 (note 4 Apr 2007 4 35 of 43
Variable Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority Additional notification CB protection trip (note CB residual trip (note Battery low Low Startup sequence failed Shutdown sequence failed / List of combination of conditions initiating alarm / List of combination of conditions initiating alarm (note (note IO module fault Medium Auxiliary alarm 1 / False / List of H/M/L/E/O/- combination of conditions initiating alarm Note 1: For Alarm Priority, the non-abbreviated description shall be provided in the functional specification document eg. High/Medium/Low/Event/Off-Normal/-. Refer to Attachment A for worked examples. 4 Apr 2007 4 36 of 43
OTHER MISCELLANEOUS ITEMS Parameters Parameter description Main incomer Non Essential Supply present Auxiliary parameter 1 Auxiliary parameter 2 Alarms Main incomer Variable Main incomer Non Essential Supply present Minimum Maximum Default Value setting setting Field input active low Alarm triggers PLC Alarm delay (sec) Visible on HMI Alarm priority (note Control from HMI Additional notification Supply A CB protection trip (note Supply A CB closed False Event Supply B CB protection trip (note Supply B CB closed False Event Busbar under volts (note 4 Apr 2007 4 37 of 43
Variable Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority Additional notification Circuit breaker 1 protective trip (note Circuit breaker 1 closed False Event Circuit breaker 2 protective trip (note Circuit breaker 2 closed False Event Supply equipment comms fault (note MCC fault (note Not in default mode (Replace default mode with either: Local manual, Remote manual or Auto) Off normal Non essential CB protection trip (note Non essential CB closed False Event Non essential CB contactor closed False Event Supply faulted (note Supply 1 under volts (note 4 Apr 2007 4 38 of 43
Variable Field input active low Supply 2 under volts Alarm triggers PLC Alarm delay (sec) Alarm priority (note Additional notification Lighting control Not in default mode (Replace default mode with either: Local manual, Remote manual or Auto) Off normal Other UPS general fault (note UPS line fault (note UPS battery fault (note Intruder detected (note Fire detected (note Chlorine leak 1 / False / List of combination of conditions initiating alarm (note 4 Apr 2007 4 39 of 43
Chlorine leak 2 Variable PLC to PLC comms failed Citect server to server comms failed FDIO comms failed DeviceNet comms failed Site comms failed Field input active low Alarm triggers / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm PLC Alarm delay (sec) Alarm priority (note (note (note (note (note (note Additional notification 4 Apr 2007 4 40 of 43
Variable Field input active low Alarm triggers PLC Alarm delay (sec) Alarm priority Site power failed (note Auxiliary alarm 1 Auxiliary alarm 2 / False / List of combination of conditions initiating alarm / False / List of combination of conditions initiating alarm H/M/L/E/O/- H/M/L/E/O/- Additional notification 6.1.14. Data Reporting: Define any data reporting requirements in tabular format. Where applicable, standard drive and valve maintenance statistics shall be provided. Standard drive statistics: Hours Run, Hours Available, Number of Starts (FWD/REV), Hours Faulted, % Utilisation, % Availability, Average Current, Number of Faults and Fault History. Standard valve statistics: Number of Operations, Hours Operated, Hours Available, Hours Faulted, % Utilisation, % Availability, Number of Faults and Fault History. The tables below shall be used in the functional specification and shall not be modified unless ActewAGL gives approval. All rows that are not applicable to the particular item shall be deleted. Refer to Attachment A for worked examples. Averaging type Description Rolling /?? hours Value 4 Apr 2007 4 41 of 43
Description Value Averaging sample rate?? sec /?? min Totaliser 1 period Start and end times Totaliser 1 engineering units Unit of measurement Totaliser 2 period Start and end times Totaliser 2 engineering units Unit of measurement Data Warehouse Reporting requirements Maintenance statistics Standard drive statistics Standard valve statistics Special reporting requirements Detail requirements Operational statistics Report period Daily / monthly / other Averaging type is rolling Averaging sample rate?? sec /?? min Minimum value (with time) Maximum value (with time) Percentile?? th Totaliser Totaliser engineering units Unit of measurement Production or Consumption Ratio Define units of comparison Refer to Attachment A for worked examples. 6.1.15. Control Source: Identify the location of the I/O devices and the controlling PLC/RTU. PLC/RTU FDIO MCC 4 Apr 2007 4 42 of 43
????PC????TC????MC 6.1.16. References: List the references that will provide additional information to guide the programmer. Eg. Existing O&M manuals or third party operational documentation, etc. ATTACHMENTS A. FUNCTIONAL SPECIFICATION - EXAMPLES A typical vertical slice through the LMWQCC Specification will be provided upon request. This will be provided to illustrate the application of these Guidelines and shows the format, content and wording required in the development of the Specification. 4 Apr 2007 4 43 of 43