Anda di halaman 1dari 61

NIOEC-SP-70-08(2)

DOCUMENT CODE NO. OF PAGES: 58


DISCIPLAN
PLAN/PRJ/SUB UNIT PHASE DOCUMENT TYPE SERIAL NO. REV. NO. DATE
E
NIOEC 000 EG IN SP 7008 A0 APRIL, 2007

NATIONAL IRANIAN OIL REFINING & DISTRIBUTION COMPANY


NATIONAL IRANIAN OIL ENGINEERING
& CONSTRUCTION COMPANY

NIOEC SPECIFICATION
FOR

PROCESS CONTROL SYSTEM


(PCS)

SECOND EDITION

APRIL , 2007

THIS STANDARD IS THE PROPERTY OF NATIONAL IRANIAN OIL ENGINEERING & CONSTRUCTION COMPANY. IT IS CONFIDENTIAL AND ALL
RIGHTS RESERVED TO THE OWNER. NEITHER WHOLE NOR ANY PART OF THIS DOCUMENT MAY BE DISCLOSED TO ANY THIRD PARTY,
REPRODUCTED, STORED IN ANY RETRIEVAL SYSTEM OR TRANSMITTED IN ANY FORM OR BY ANY MEANS WITHOUT THE PRIOR WRITTEN
CONSENT OF THE NATIONAL IRANIAN OIL ENGINEERING & CONSTRUCTION COMPANY
APRIL, 2007 NIOEC-SP-70-08 (2)

1
APRIL, 2007 NIOEC-SP-70-08 (2)

REVISION INDEX

REV. REV. REV.


1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5
PAGE REV. PAG PAGE
PAGE E

1 26 51 76
2 27 52 77
3 28 53 78
4 29 54 79
5 30 55 80
6 31 56 81
7 32 57 82
8 33 58 83
9 34 59 84
10 35 60 85
11 36 61 86
12 37 62 87
13 38 63 88
14 39 64 89
15 40 65 90
16 41 66 91
17 42 67 92
18 43 68 93
19 44 69 94
20 45 70 95
21 46 71 96
22 47 72 97
23 48 73 98
24 49 74 99
25 50 75 100

NOTES:
1) THIS SHEET IS A RECORD OF ALL REVISIONS TO THIS SPECIFICATION.
2) REMARKS RELATED TO EACH REVISION SHOW A BRIEF DESCRIPTION. THESE REMARKS SHALL BE
INTERPRETED IN CONJUNCTION WITH THE REVISED TEXT MARKED BY REVISION NUMBERS.
3) WHEN APPROVED EACH REVISION SHALL BE CONSIDERED AS A PART OF THE ORIGINAL
DOCUMENT.
4) NUMBER OF PAGES EXCLUDES THIS SHEET AND THE COVER SHEET.

5
4
3
2
1
0 APRIL, 2007 ASHRAFNIA ORDOOBADI FARZAM SAJEDI
REV. DATE PREPARED CHECKED APPROVED AUTHORIZED

2
APRIL, 2007 NIOEC-SP-70-08 (2)

CONTENTS: PAGE NO.


1. SCOPE.............................................................................................................................................4
2. REFERENCES ...............................................................................................................................4
3. UNITS..............................................................................................................................................6
4. DEFINITIONS AND TERMINOLOGY .....................................................................................6
5. ABBREVIATIONS ........................................................................................................................8
6. PRODUCT HISTORY...................................................................................................................8
7. CERTIFICATION AND APPROVALS ......................................................................................8
8. GENERAL SYSTEM REQUIREMENTS...................................................................................9
8.1 Electrical Power............................................................................................................................9
8.2 Environmental Data.....................................................................................................................9
8.3 Ingress Protection and Hazardous Area Classification ............................................................9
8.4 Electromagnetic Interference......................................................................................................9
9. SYSTEM DESCRIPTION.............................................................................................................9
9.1 Configuration................................................................................................................................9
9.2 PCS Architecture........................................................................................................................10
9.2.1 Automation System .................................................................................................................10
9.2.2 Use of Standard Products .......................................................................................................10
9.2.3 Software Revision....................................................................................................................10
9.2.4 Integrity of PCS.......................................................................................................................11
9.2.5 Reliability of PCS ....................................................................................................................11
9.2.6 Availability of PCS ..................................................................................................................11
9.2.7 PCS Redundancy.....................................................................................................................12
9.2.8 PCS Diagnostics.......................................................................................................................12
9.2.9 Scalability of PCS ....................................................................................................................13
9.2.10 PCS System Backup ..............................................................................................................13
9.2.11 PCS Battery back-up ............................................................................................................14
9.2.12 PCS Connectivity...................................................................................................................14
9.2.13 PCS Interface With Third Party Subsystems.....................................................................14
9.2.14 PCS Spare Capacity ..............................................................................................................14
9.2.15 PCS Performance and Sizing ...............................................................................................14
9.3 System Cabinets Mechanical and Electrical Design .............................................................17
9.3.1 Mechanical Design...................................................................................................................17
9.3.2 Marshalling Cabinets...................................................................................................17
9.3.3 Electrical Design......................................................................................................................18
9.3.4 Power Distribution Cabinet.........................................................................................20
9.3.5 System Electronic Modules Design and Construction ..............................................20
9.3.6 Cabinet and Station Grounding.............................................................................................21
9.3.7 Cabinet Smoke Detectors.............................................................................................21
9.3.8 Physical Installation of Foundation Fieldbus Devices .........................................................21
9.3.9 Power Supply Requirements ..................................................................................................21
9.4 Equipment Maintenance............................................................................................................21
9.5 Inputs and Outputs ....................................................................................................................22
9.5.1 Traditional Input and Output................................................................................................22
9.5.3 Manual Input ...........................................................................................................................22
9.5.4 HART I/O.................................................................................................................................22
9.6 System Communication .............................................................................................................22
9.7 Control and Data Handling.......................................................................................................22
9.7.1 Calculations..............................................................................................................................22
9.7.2 Regulatory Control ................................................................................................................22

1
APRIL, 2007 NIOEC-SP-70-08 (2)
9.7.3 Algorithms................................................................................................................................23
9.7.4 Input Scanning.........................................................................................................................23
9.7.5 Control Loop Execution Frequency ......................................................................................23
9.7.6 Output Functions.....................................................................................................................23
9.7.7 Setpoint Clamps.......................................................................................................................23
9.7.8 Windup protection .................................................................................................................23
9.7.9 Sequential Control...................................................................................................................24
9.7.10 Sequence Language ...............................................................................................................24
9.7.11 Auto-tuning ............................................................................................................................24
9.7.12 Fuzzy Logic Control & Algorithms .....................................................................................24
9.7.13 Control Execution Monitoring............................................................................................24
9.7.14 Predictive Maintenance Diagnostics....................................................................................24
9.7.15 Loop Performance Monitoring ............................................................................................25
9.7.16 Process Simulation ................................................................................................................25
9.8 Configuration and Database .....................................................................................................25
9.8.1 Configuration...........................................................................................................................25
9.8.2 Configuration Tool..................................................................................................................25
9.8.3 Tag Parameters .......................................................................................................................26
9.8.4 Engineering Units....................................................................................................................26
9.8.5 Data Base, Reporting and Modification Utilities..................................................................26
9.8.6 System Access ..........................................................................................................................27
9.9 Operator and Engineering Stations..........................................................................................27
9.9.1 General .....................................................................................................................................27
9.9.2 Operator Stations ....................................................................................................................27
9.9.3 Engineering Stations ...............................................................................................................27
9.9.4 Monitors ...................................................................................................................................28
9.9.5 Display Hardcopy....................................................................................................................28
9.9.6 Printers.....................................................................................................................................28
9.10 Displays and Graphics .............................................................................................................28
9.10.1 Updating Capability..............................................................................................................28
9.10.2 Displays and Graphics Access..............................................................................................28
9.10.3 Hierarchical Displays............................................................................................................28
9.10.4 Paging .....................................................................................................................................28
9.10.5 Invalid Values ........................................................................................................................28
9.10.6 Faceplates...............................................................................................................................29
9.10.7 System and Diagnostic Displays...........................................................................................29
9.10.8 Graphics .................................................................................................................................30
9.11 Alarm and Message Handling.................................................................................................31
9.11.1 Categorizing Messages..........................................................................................................31
9.11.2 Operator Actions ...................................................................................................................32
9.11.3 Engineer Actions ...................................................................................................................32
9.11.4 Process Alarm Initiation.......................................................................................................32
9.11.5 System Alarm Initiation........................................................................................................33
9.11.6 Process and System Alarms History Retention ..................................................................33
9.11.7 Process and System Alarms Audible Annunciation...........................................................33
9.11.8 Process and System Alarms Visible Annunciation.............................................................33
9.12 Diagnostics ................................................................................................................................33
9.13 Data Historization ....................................................................................................................34
9.14 Trend Displays..........................................................................................................................35
9.15 Reports ......................................................................................................................................36
9.16 Availability................................................................................................................................36
9.17 External Interface ....................................................................................................................37

2
APRIL, 2007 NIOEC-SP-70-08 (2)
9.17.1 Serial Interface - Subsystems ...............................................................................................37
9.17.2 OPC Interface........................................................................................................................37
9.18 Engineering Tools.....................................................................................................................37
9.19 Embedded Advanced Control Tools.......................................................................................37
9.20 Management Information System ..........................................................................................38
9.21 Maintenance Planning and Scheduling System.....................................................................38
9.22 Plant Start Up and Shutdown Monitoring System ...............................................................38
9.23 Automatic Start-up Sequence System ....................................................................................38
9.24 Auto Tuner................................................................................................................................39
9.25 Special Requirements............................................................................................................39
9.25.1 Multi-variable Constrained Model Predictive Control (MPC).........................................39
9.25.2 Virtual Sensors and Quality Estimation .............................................................................40
9.25.3 Control Simulation................................................................................................................40
10. NAMEPLATES ..........................................................................................................................40
11. PAINTING AND RUST PREVENTION.................................................................................41
11.1 Paint Specification....................................................................................................................41
11.2 Paint Colour..............................................................................................................................41
11.3 Special Requirements...............................................................................................................41
11.4 Surface Treatment....................................................................................................................41
12. DOCUMENTATION .................................................................................................................41
12.1 General ......................................................................................................................................41
12.2 Design Documents ....................................................................................................................41
12.3 On line Documentation ............................................................................................................41
13. INSPECTIONS AND TESTING ..............................................................................................41
13.1 General ......................................................................................................................................41
13.2 Factory Acceptance Test (FAT) ..............................................................................................42
13.3 Test Completion........................................................................................................................42
14. INSTALLATION, START UP AND COMMISSIONING ....................................................43
14.1 Installation ................................................................................................................................43
14.2 Checks .......................................................................................................................................43
14.3 Power up....................................................................................................................................43
14.4 SAT ............................................................................................................................................43
14.5 Commissioning .........................................................................................................................43
14.6 Test Equipment ........................................................................................................................43
14.7 Documents.................................................................................................................................43
15. SPARES PARTS SUPPLY........................................................................................................44
15.1 Construction, Pre-commissioning and Commissioning Spare Parts...................................44
15.2 Spare Parts for Two Years of Operation ...............................................................................44
15.3 Maintenance Tools ...................................................................................................................44
16. TRAINING .................................................................................................................................44
17. GUARANTEES ..........................................................................................................................44
APPENDIX I.....................................................................................................................................46
MAINTENANCE PLANNING AND SCHEDULING SYSTEM................................................46
APPENDIX II ...................................................................................................................................55
PLANT START UP AND SHUTDOWN MONITORING SYSTEM .........................................55
APPENDIX III..................................................................................................................................57
VENDOR’S DOCUMENT SUPPLY (VDC) .................................................................................57

3
APRIL, 2007 NIOEC-SP-70-08 (2)

1. SCOPE
This specification defines NIOEC’s minimum requirements for the design, manufacture, test and
inspection of Process Control System (PCS).
Deviations from this specification will only be permitted on obtaining written approval from
NIOEC.

2. REFERENCES
Throughout this specification the following dated and undated standards and codes are referred to.
These referenced documents shall, to the extent specified herein, form a part of this specification.
For undated references, the latest edition of the referenced document (including any supplements
and amendments) applies. For dated references, the edition cited applies.
The applicability of changes in the dated references that occur after the cited date shall be mutually
agreed upon by NIOEC and the vendor /contractor.

BASEEFA (BRITISH APPROVALS SERVICE FOR ELECTRICAL


EQUIPMENT FOR FLAMMABLE ATMOSPHERES)

CENELEC (COMITÉ EUROPÉEN DE NORMALISATION


ELECTROTECHNIQUE)

EEC (EUROPEAN ECONOMIC COMMUNITY)

EMC- Directive 89/336/EEC “Electromagnetic Compatibility”

EN (EUROPEAN STANDARDS)

EN 55022 “Specification For Limits And


Measurement Of Radio
Interference Characteristics Of
Information Technology
Equipment”
FM (FACTORY MUTUAL)

IEEE (INSTITUTE OF ELECTRICAL & ELECTRONICS ENGINEERS)

IEEE C37.90.1: IEEE C37.90.1: “Surge Withstand Capability


(SWC) Tests”
IEC (INTERNATIONAL ELECTRO-TECHNICAL COMMISSION)

IEC 60751 “Industrial Platinum Resistance


Thermometer Sensors”
IEC 61000-4-2,
IEC 61000-4-3, “Electromagnetic Compatibility
IEC 61000-4-4 (EMC)”
IEC 61499-1, “Function Blocks For Industrial
IEC 61499-2 Process Measurement And
Control Systems”

4
APRIL, 2007 NIOEC-SP-70-08 (2)
IEC 61158-2 "Foundation Fieldbus Standard
For Use In Industrial Control
Systems - Physical Layer
Specification And Service
Definition”
IEC 61131-3 “Sequential Function Charts”
IEC 60332 “Test On Electric Cables Under
Fire Conditions”

IEC 60529 “Classification Of Degree Of


Protection Provided By
Enclosures”

IEC 60068 “Basic Environmental Testing


Procedures”
IEC-1000-4: “Electromagnetic Compatibility
For Industrial Process
Measurement And Control
Equipment”
IEC-60-605: “Equipment Reliability Testing”

ISO (INTERNATIONAL STANDARD ORGANISATION)


ISO 9000 “Quality Systems”
ISA (INSTRUMENTATION, SYSTEM, AUTOMATION SOCIETY OF
AMERICA)
ISA - S 5.1: ISA - S 5.1: “Instrument Symbols And
Identifications”

ISA - S 5.2: ISA - S 5.2: “Binary Logic Diagrams For


Process Operations”
ISA - S 5.3: ISA - S 5.3: “Graphic Symbols For
Distributed Control/Shared
Display Instrumentation, Logic
And Computer Systems”
ISA - S 5.4: ISA - S 5.4: “Instrument Loop Diagrams”

ISA RP 55-1: ISA RP 55-1: “Hardware Testing Of Digital


Process Computers”
ISA- S18.1: ISA- S18.1: “Annunciator Sequences And
Specification”
ISA- S50.1 ISA- S50.1 “Compatibility Of Analogue
Signals For Electronic Industrial
Process Instruments”

LCIE (LABORATORIE CENTRAL DES INDUSTRIES


ELECTRICQUES)

NFPA (NATIONAL FIRE PROTECTION ASSOCIATION)

NFPA 70 “National Electrical Code”

5
APRIL, 2007 NIOEC-SP-70-08 (2)
NIOEC SP (NIOEC SPECIFICATIONS)
NIOEC -SP-70-01 “Specification For
Instrumentation”

NIOEC-SP-00-10 “Specification For Units”

PTB (PHYSIKALISCH TECHNISCHE BUNDESANSTALT)

TIA (TELECOMMUNICATION INDUSTRY ASSOCIATION)


TIA/EIA-485 “Electrical Characteristics Of
Generators And Receivers For
Use In Balanced Digital
Multipoint Systems”
U.S. Military U.S. MILITARY HANDBOOK
HNBK
U.S. Military U.S. Military Handbook -217 “Reliability Prediction Of
Handbook -217 Electronic Equipment”

U.S. Military U.S. Military Handbook -472 “Maintainability Prediction”


Handbook -472
UL (UNDERWRITERS’ LABORATORIES)

3. UNITS
International System of Units (SI) shall be used in accordance with NIOEC-SP-00-10, unless
otherwise specified.

4. DEFINITIONS AND TERMINOLOGY


This section contains definitions for the terms as they are used in this document.
Advanced Control: Multi-variable, constraint and optimizing controls will be labelled advanced
controls. Controls that fall into this category will be those that are supervisory in nature, i.e., they
normally, but not always, output to the set points of other control loops rather than to the valves
directly.
Auto Sense: Capability by the system to automatically detect and recognize any hardware upon
addition to or removal from the system without user intervention.
Auxiliary System: A control and/or monitoring system that is stand-alone, performs a specialized
task, and communicates with the automation system.
Call Up Time: The time between when the operator initially enters a display request and when all
objects, lines, values (good or invalid), trends and other parts of the display have been fully
presented to the operator.
Configurable: The capability to select and connect standard hardware modules to create a system;
or the capability to change functionality or sizing of software functions by changing parameters
without having to modify or regenerate software.
Configuration: The physical installation of hardware modules to satisfy system requirements; or
the selection of software options to satisfy system requirements.

6
APRIL, 2007 NIOEC-SP-70-08 (2)

Cycle: The scanning of inputs, execution of algorithms and transmission of output values to
devices.
Dead band: The range through which an input signal may be varied without initiating an action or
observable change in output signal.
Discrete Control: Control where inputs, algorithms, and, outputs are based on logical (yes or no)
values.
Equipment or System: Process Control System (hardware/software)
Faceplate: A graphic element that mimics the front panel of an analogue controller instrument,
hardwired push-button or switch. The same is true for the graphical representation on the Operator
Interface
Factory Acceptance Test (FAT): The final test at the vendor's facility of the integrated system
being purchased.
Fieldbus Foundation: An independent, non-profit organization established to support
standardization of the ISA/IEC Foundation Fieldbus standard.
Foundation Fieldbus: A Fieldbus that conforms to all Fieldbus Foundation specifications.
Foundation Fieldbus Segment: Grouping of Foundation Fieldbus devices connected to the
automation system through an H1 interface module.
Foundation Fieldbus Trunk: Main path of a Foundation Fieldbus. The trunk line connects the
system H1 module to power supply / power conditioning assembly.
Foundation Fieldbus Spur: A spur branches off the Foundation Fieldbus trunk.
Function Block Application Process: Fieldbus Foundation specification defining the plant or
factory applications that perform one or more automatic monitoring and control functions.
H1: Wiring which connects Foundation Fieldbus devices used for control applications such as
temperature, level, and flow control. Devices can be powered directly from the Foundation Fieldbus
and will operate on existing wiring that was previously used for 4-20 mA devices.
Invalid Value: The state of a tag value which indicates that the quantity being measured or
calculated is out-of-range, not measurable or calculable.
Logs: Files or printouts of information in chronological order.
Mode: Control block operational condition, such as manual, automatic, or cascade.
Module: An assembly of interconnected components that constitute an identifiable device,
instrument, or piece of equipment. A module can be disconnected, removed as a unit, and replaced
with a spare. It has definable performance characteristics that permit it to be tested as a unit.
OPC (Object Linking and Embedding for Process Control): Software application which allows
bi-directional real time data flow between two separate applications. These applications may be
running on the same or on separate servers.
Operational Data: The statistical data such as alarm limits, tuning parameters, and clamping
values, as opposed to process data such as input values, output values and setpoints.
Operator Station: A station used by an operator to perform the functions required to monitor and
control his assigned units.
Plant Area: The designated points (inputs, outputs, and calculated values) that belong to a
geographic or functional section of a plant.
Plug and Play: The ability of hardware equipment to automatically identify itself to the system.
When the equipment is powered up it is automatically assigned a unique identity without the need
to set any dip switches.
Point: A process variable derived from an input signal or calculated in a process calculation.
Profibus: Open bus system, standardized in the German DIN 19 245.
Purchaser: In cases where this specification is part of a direct order, Purchaser shall mean the National
Iranian Oil Engineering and Construction Company. Where this specification forms part of contract
documents, Purchaser shall mean the Contractor. In references to inspection by Purchaser, when this

7
APRIL, 2007 NIOEC-SP-70-08 (2)
specification forms part of contract documents, this shall be construed to mean that NIOEC shall also have
the right of inspection.
Redundant Configuration: A system/subsystem configuration that provides automatic switchover,
in the event of a failure, without loss of a system function.
Regulatory Control: The functions of process measurement, control algorithm execution, and final
control device manipulation that provide closed loop control of a plant process.
Reliability: The probability that the system or component will perform its intended function for a
specified period of time.
Self-Diagnostic: The capability of an electronic device to monitor its own status and indicate faults
that occur within the device.
Supervisory Control: Higher level control functions that interface with regulatory controllers and
other automation system equipment to provide for integrated control.
System Access Restriction: Access control by key lock, password or other equivalent method.
System Alarm: Alarm that occurs as a result of an automation system hardware or software fault.
System Operating Software: The vendor's standard software that performs the basic functions of
the system.
Tag: A collection of attributes that specify either a control loop or a process variable, or a
measured input, or a calculated value, or some combination of these, and all associated control and
output algorithms. Each tag is unique.
Tag ID: The unique alphanumeric code assigned to inputs, outputs, equipment items, and control
blocks. The tag ID might include the plant area identifier.
Station: A set of electronic equipment including, at a minimum, one PC, one monitor and one
keyboard.

5. ABBREVIATIONS
EMI: Electromagnetic Interference
ESD: Emergency Shut Down
FAT: Factory Acceptance Test
FSD: Functional Specification Document
ILD: Instrument Loop Diagram
MOV: Motor Operated Valve
MTBF: Mean Time Between Failures
PC: Personal Computer
PCS: Process Control System
RFI: Radio Frequency Interference
SAT: Site Acceptance Test
SOE: Sequence of Events
UPS: Un-interruptible Power Supply

6. PRODUCT HISTORY
Equipment shall be of the same model and design as used in similar plants and operating/ambient
conditions with at least three (3) years of satisfactory operational history.
7. CERTIFICATION AND APPROVALS
The equipment shall bear CE marking in accordance with EMC- Directive 89/336/EEC, and the
conformity certificates shall be provided.

8
APRIL, 2007 NIOEC-SP-70-08 (2)
The VENDOR shall also submit certificates/records of type test approval of the system, based on
recognised national or international standards, which for CENLEC regulations shall be LCIE, TUV,
PTB, BASEEFA and for NEC regulations shall be FM or UL.

8. GENERAL SYSTEM REQUIREMENTS


8.1 Electrical Power
The equipment will be powered from dual redundant Un-interruptible Power Supplies (UPS). The
UPS will provide 230 VAC ± 2%, 50 Hz ± 1%. However all system modules shall be capable of
operating during voltage variations up to ± 10% and frequency variations up to ± 5%.
The battery back up will be capable of sustaining all components of the system for a period of at
least 30 minutes in the event of total power loss.

8.2 Environmental Data


Indoor temperature and humidity (RH) will be 22 °C ± 4°C and 40% to 70% respectively and
shipping and storage conditions will be considered as -20 °C to 85 °C and 0% to 100%.
However, as a minimum the following operating conditions shall not degrade the continuous
operation of the system:
o Min/max temperature: 5°C to 40 °C
o Min/max humidity: 20% to 90% RH non-condensing
o Suspended Solids are dust and sand.
Allowable indoor noise level shall be 55 dBA, measured at one meter from equipment in question.

8.3 Ingress Protection and Hazardous Area Classification


Control and rack rooms shall be considered as non-hazardous areas. Both control and rack rooms
will be air-conditioned and pressurized.
Indoor stations and system cabinets shall conform to IEC-60529, IP 42, as a minimum.
Electrical accessories, cabling and junction boxes in hazardous areas will normally be of
intrinsically safe construction and execution suitable for NEC Class I, Division I, and Group C (IEC
Zone I, Group II B) locations. Where intrinsically safety equipment is not available, suitable
explosion-proof equipment to suit the Area Classification shall be employed.

8.4 Electromagnetic Interference


Equipment shall meet all electromagnetic compatibility requirements of the IEC 61000-4-2, 61000-
4-3, and 61000-4-4 standards.
Each element of the PCS must function without introducing intolerable electromagnetic
disturbances to other items or being susceptible to electromagnetic influences from other systems.
Emission limits generally comply with the relevant requirements of BS-6527 for Class B
equipment, and Susceptibility performance shall generally comply with the relevant requirements of
IEC 1000-4. All equipment comprising the PCS shall be designed in such a way as to ensure
immunity to interference from VHF and UHF hand portable transceivers operating in the range 150
MHz to 470 MHz with a power output of 1 Watt (RMS) held at 300 mm from any equipment
forming part of the PCS.

9. SYSTEM DESCRIPTION
9.1 Configuration
Configuration of the system and the specifics quantities of hardware will be specified in the specific
project documents.

9
APRIL, 2007 NIOEC-SP-70-08 (2)
9.2 PCS Architecture

9.2.1 Automation System


Although NIOEC encourages the use and application of modern technologies in its projects,
however such approach to the new findings and technologies must be based on a sound and safe
engineering and design practice. As such, taking into account the unsatisfactory performance of
fieldbus technology on control loops, especially critical loops and those requiring fast response
times, the automation system architecture shall be based on a hybrid of fieldbus technology and the
conventional DCS, whereby generally the control loops shall be handled by the DCS and the
monitoring loops shall be performed via the fieldbus equipment. The system shall make use of
OLE/OPC for interconnectivity of multiple systems from different suppliers, compact packaging
with flexible DIN rail mounting, field or rack room mountable control and I/O subsystem.
The system shall be based on an integrated, hierarchical distributed architecture with shared
displays such that in combining operator interfaces, process controllers and input/output modules it
shall provide an operating integrated system effective at the loop, unit and plant control levels.
Information hierarchy shall be incorporated in fixed, variable and customized format displays. The
communication shall be such that any bit of information in any part of the plant, connected to the
system, shall be available on any operator station. Each station shall be capable of taking over the
function of a failed station.
The PCS shall have the capability for the operator to assume manual control of any or all of the
control loops.
The operation of the PCS shall include, but not be limited, to the following:
• Control Configuration.
• Database.
• Hierarchical Displays.
• Historisation.
• Real time and Historical Trending.
• Automatic Diagnostics and Fault Reporting.
• Documentation.
Configuration of the system shall be carried out through Engineering Stations to facilitate on- line
system configuration and debugging capability. The Engineering functions shall include system
configuration, data base management, graphic display generation, report generation management
and utility program access. The functions shall be soft/hard lock protected.
Real time dual redundant LAN and associated communication hardware shall be used to transfer
date between various PCS components. TCP/IP shall be provided to link the PCS to the hierarchy of
management suite.

9.2.2 Use of Standard Products


The system shall consist of manufacturer's standard hardware, field proven systems software, and
firmware that can be configured to meet the stated requirements. Vendor's standard system
operating software shall not be modified to meet any of the Purchaser's requirements.

9.2.3 Software Revision


All software, exclusive of application software, shall be the most recent revision that is applicable
to the system hardware at the time of the hardware freeze date as defined in the contract or purchase
order.

10
APRIL, 2007 NIOEC-SP-70-08 (2)
Software design shall be such that future revisions or updates of the system operating software will
not affect the successful operation of the system.

The system shall allow for upgrading of system operating software on all redundant modules of the
system without the necessity of shutting down the process, without losing the operator interface,
and without the loss of access to any control function.
Application software shall not require modifications in order to be able to run under new releases of
the system operating software. Any new release of system software shall be backward compatible
with files created using the previous software releases.

9.2.4 Integrity of PCS


The PCS shall maintain a high availability figure with a high level of integrity. This shall be
achieved by:
• The use of high reliability components,
• The use of hardware redundancy where specified,
• Provision of routine and/or automatic testing and diagnostics,
• Simple fault indication and module replacement repairs.

9.2.5 Reliability of PCS


The supplied equipment must be designed for the maximum reliability and the minimal downtime.
The system shall have a high degree of tolerance to hardware malfunctions, software and operator
miss-keying. Any fault, which develops, shall have its effect localised from that part of the system.
The required reliability shall be achieved through a fault tolerant design, advanced diagnostics and
state of the art redundancy schemes. The system shall be designed such that all key elements of the
system, including storage devices, communication modules, interfaces and media, power supplies
and other major system elements are provided in automatic dual redundant configurations.
Automatic switch over between the redundant modules/cards/components shall be incorporated into
the system design. Switch over between redundancies shall be transparent to the system, however it
shall be reported to the operator stations. Status of data network, node and modules shall be
displayed on the station monitors. Failure of either of the networks or associated communication
modules shall not interfere with the closed loop control functions.
It shall be possible to replace the malfunctioning redundant parts without system disruption or
power off.

9.2.6 Availability of PCS


The availability of the equipment shall be in excess of 99.5 % and shall include all equipment as
supplied by the VENDOR. For calculation purposes the equipment supplied by others shall be
assumed to have an availability of 100%.
The VENDOR shall supply availability calculations based on MIL-HDBK-217E based on a
minimum configuration of the following items:
• All controllers associated with process monitoring and control is operational with no more than
a single l/O module failure.
• All control functions available.
• At least one VDU and one functional keyboard operational per operator station.
• At least one printer operational.
Mean time between failures shall be applied as required to ensure that the entire control cell
(excluding field equipment) is a minimum of 99.5% available, based on a MTTR of 4 hours. The
MTBF and coefficient of availability rating is inclusive of both hardware and software functions as
a system. The PCS supplier shall supply documentation describing the method and identifying the
data used in calculating the MTBF and coefficient of availability.
The VENDOR shall detail the MTBF for the total PCS and the method used to achieve the MTTR.

11
APRIL, 2007 NIOEC-SP-70-08 (2)
Any module with an MTBF of less than 10,000.0 hours shall be clearly identified by the VENDOR.

9.2.7 PCS Redundancy


In order to meet the required system availability, redundant and/or fault tolerant technology shall be
incorporated.
The following equipment shall be redundant as a minimum:
1) Controllers and associated I/O modules
Complete one to one redundancy is required with full duplication of control modules and I/O
modules in control loops. If requested, the fully duplicated equipment must allow mounting in
separate cabinets to minimise common cause failures. It shall also be possible to have redundant
control modules that share a single set of I/O. Identical, standard hardware must be used for all
redundancy schemes.
Redundant control modules shall simultaneously and synchronously execute a control scheme. The
modules shall continuously monitor the health of each other. When the need for a switchover is
established by the redundancy software the redundant controller must immediately become active
with no software transfer necessary at the time of control transfer to re-establish control. The
switchover time from the main to the standby module shall be less than 10 msec. Process control
shall continue to be executed in the non-failed unit.
When a module is replaced the new module must automatically initialise, receive the current
database from the primary module and pick up in synchronous execution as a secondary module in
the redundant relationship. This shall take place without user action for any of the steps.
2) Communication Network
The network, including fiber optic cabling shall be dual redundant. On line redundant real time
LAN and the redundant associated communication hardware shall have switchover time from the
main to the standby of less than 100 msec.
3) Power supply
All internal system 24 VDC power supplies shall be dual redundant.
4) Mass Storage Devices
5) H1 Cards
The following equipment shall be provided in “mutually backed-up” configuration on an
operational group basis.
1) Operator Station
Identical stations shall be provided with one-for-one backup, independently communicating with
the control system. Operator stations need to be supplied such that the failure of one network card
or connection does not cause the station to lose communication with the network.
2) System Data Base

9.2.8 PCS Diagnostics


a) General
The system shall continuously check itself and report any malfunction, hardware or software, in any
part of the system. Clear diagnostic messages and alarming shall be available on the station displays
indicating tag address, nature and severity of the defect and time and date.
All system electronic modules shall have built in status indicators to facilitate rapid fault detection
and maintenance work.
The activation of any back up module to maintain the system operation integrity shall be completely
transparent to the operator. However diagnostic messages shall be sent to the operators via station
displays.

b) On-line Diagnostics
The system must include comprehensive on-line diagnostics with the following minimum features:

12
APRIL, 2007 NIOEC-SP-70-08 (2)
Redundant Control Module processors shall perform calculations in parallel and synchronised
manner, so that switching from main processor to backup cause no interruption to analogue or
digital output signal and without any data loss.
The built-in diagnostics shall include a mechanism to validate the calculation results of redundant
processors before sending the calculation results to field devices. Validation shall incorporate a
function to check for any difference in the calculation results of the redundant processors. If such
error occurs, the built-in diagnostic function shall determine which calculation was invalid and
select the processor output with the correct calculation. Vendor shall clearly describe how his
system architecture supports this requirement.
Control Module processors shall utilize Error Correction Code (ECC) on the main memory to
reduce errors that may be caused by main memory (RAM).
Real-time network shall utilize CRC and frame length check as minimum precaution for securing
real-time data transfer.
System alarms initiated by the self-diagnostics functions must alert the operator at the Operator
Station within 3 seconds. System alarms and diagnostic displays must be available for all operator
stations.
The on-line diagnostic program shall consist of a malfunctions check program that will alert the
operator upon the detection of a fault. This shall be a unique and separate system from plant alarms.
The self-diagnostics shall, as a minimum, detect a fault or malfunction in the following:
• Real-time network diagnostics which shall include, as minimum, errors due to wrong address,
wrong frame length, and response wait time-over, other side busy, and receive data check sum
error, network configuration error, and communication timer error. Real-time LAN shall include
error counters;
• Power supplies and fans;
• All PCS cards (controllers. Processors, hardwired analogue and digital I/Os, etc.);
• Printers;
• Control Module CPU ROM Sum Check Error;
• Control Module algorithm execution error;
• Calculation function execution error;
• On-line/offline downloads error;
• Recovery Message;
• Third party system communication error, and link failure;
• Redundant Control Module database difference among processors;
• Instantaneous AC power supply failure/recovery to the Control Module;
• Diagnostics shall cover hardware, software and firmware of the PCS.

9.2.9 Scalability of PCS


The PCS shall be modular such that an easy expansion from a small system to a large system can be
made if necessary. The VENDOR shall describe the future expansion philosophy of the installed
system in terms of limits of capability and ease of implementation. The description shall include the
expansion aspects of control, man-machine interfaces, system database, applications, operating
system, hardware and communications.

9.2.10 PCS System Backup


The entire control software shall be backed up; this includes vendor software, control database,
user-built programs, source code, data files, schematics and so forth.
Back up must be possible on commercially available media. To recover from an outage, any
component of the system must be able to be re-loaded from bulk memory (hard disks).
All the system-related software including engineering tools, application programs, standard and
optional packages that are included in the scope of supply shall be delivered with the system on
magnetic or optical media.

13
APRIL, 2007 NIOEC-SP-70-08 (2)
9.2.11 PCS Battery back-up
All volatile memory devices within the system shall be provided with memory power supply battery
back- up. The battery back up shall have a minimum capacity of 72 hours and shall be independent
of the PCS UPS system at the UPS downtime. The PCS shall monitor the status of the its dc power
distribution system in order to alert the operator of the malfunctions.
Power failure to a control module for less than 72 hours shall not require the down load of the
control module.
Each Operator stations shall be loaded from its own bulk memory automatically when power is
recovered.

9.2.12 PCS Connectivity


The PCS shall be able to be connected with upper level computers and networks using Ethernet
with TCP/IP protocol.

9.2.13 PCS Interface With Third Party Subsystems


Dedicated control and monitoring systems for third party subsystems such as PLCs, Tank Gauging
etc., shall be interfaced to the PCS, and will be controlled and monitored by the operators.
Sub-systems shall be interfaced via serial link RS-232/422/485 using MODBUS RTU protocol/
Ethernet Interface/OPC. The vendor shall have interface ports that support serial links/Ethernet link
at the Control Module level and shall provide the driver software.
The PCS shall perform memory mapping of the sub-system, and achieve seamless integration
between the PCS database and sub-system.

9.2.14 PCS Spare Capacity


The spare capacity shall allow on site development and modification without major changes to the
hardware, software and system configuration.
No more than 70% of the available memory and 70% of the available storage disc shall be utilised
during normal PCS operation.
Each system shall be supplied with 10% spare for all elements of the system configuration,
including application software, graphics, history, reports, and trends. Fitted and wired spare of 10%
for each I/O type and control capability in the base system shall be installed. The base system is
defined as the quantity of hardware and software needed to meet the project requirements.
Communication networks within the automation system shall include a ten percent (10%) fitted and
wired spare hardware and unused node addresses. System expansion requirements shall be in
accordance with the project procurement documents. System expansion shall be achievable without
shutting down the regulatory controllers not directly involved with the expansion.
The communication network shall utilize automatic network self-addressing technology (plug-and-
play), which automatically assigns unique new controller addressing when a new device is
connected to the control network.

9.2.15 PCS Performance and Sizing

a) General
The control response period shall be used as the measure of PCS performance. The control system
can perform proportional, integral, derivative (PID) control using any combination of hardware and
software. Functions (e.g. signal selectors, summers, calculation blocks, etc.) associated with
controllers shall not increase the control response period.
In case of licensed process units, the maximum allowable control response period shall basically
follow the process licensors operational requirements. However following figures are the minimum
requirements if no special requirements are specified by the licensors.

14
APRIL, 2007 NIOEC-SP-70-08 (2)

Maximum control response period (msec)


Process Category

Flow, PRESSURE, DIFFERENTIAL 300


PRESSURE

Temperature 1000

Level 1000

Designated Fast Process Control Loops 150

All Others (Analysis, Density, pH, Etc) 1000

* Shorter control response periods may be required for certain control services (e.g.
compressor anti-surge, reactor temperature, etc.). Multi-variable advanced process
control may be implemented with longer control response periods.

In general, the shorter the control response period, the better the control performance. Control
response periods longer than those listed above may degrade performance and affect unit
operability.
NOTES: 1- The criteria shown in the above table are typical requirements if there are no
requirements on such special requirement where applicable. The maximum allowable control
response period shall basically follow to the process licensors operational requirements.

b) PID Equation Form


The PID controller equation should be of the form in which the derivative action is only based on
the change in process variable. Those forms of the PID equation in which the derivative action is
based on the change in error (and derivative is used) cause the controller output to spike when the
operator changes the set point.

c) Controller Set point Tracking


Controller set point should track their respective process variables while in manual mode. For
cascade loops, the output of each primary controller should track the set point of its respective
secondary controller when the secondary controller is not in cascade mode. All primary controllers
should also revert to manual mode when their associated secondary controllers are not in cascade
mode. This allows the controller output tracking to take effect, thereby facilitating bumpless
transfer when cascade is re-established. Proper configuration of tracking allows operators to change
the mode of any controller from manual to automatic or from local automatic to cascade without
causing a process disturbance.

d) Controller Central Processing Unit Capacity


The control system Central Processing Unit(s) (CPU) shall include sufficient capacity to permit
50% of the slowest controllers at 1000 ms to be changed to 300 ms. Changes to the
execution/acquisition rate may be required during process unit operation.
This requirement is in addition to other provision for spare capacity in the control system. The
system shall have a standard feature to give the user the freedom to select some control and
sequencing functions to be executed at system’s fastest execution rates.

15
APRIL, 2007 NIOEC-SP-70-08 (2)

e) Indicator performance
Indicator data acquisition rate shall be used as a measure of performance. Indicator data acquisition
rate is defined as the total time the control system takes to read the process data from the input
processor and conditions it for visual display.
For initial system sizing and configuration, an acquisition rate of 2 seconds shall be used. Where
indicated data is used in control scheme, the acquisition rate shall follow the controller execution
rate listed elsewhere in this Specification.
f) Scanning
The PCS shall scan all data-points at least once every second. All calculated points associated with
a scanned data-point shall be computed at that data-points scan rate. No pulses shall be lost to
totalisers between scans.
g) Alarm/Event Handling
All alarms and events shall be guaranteed to be displayed and printed at the relevant control room
within 2 seconds of occurring at the field equipment. Alarm/event acceptance shall be complete
within 1 second of acceptance action by the operator.
The PCS shall be capable of handling up to 100 alarm and events per second without affecting
alarm event or display handling.
Each PCS cabinet equipment shall be capable of buffering one event per data-point up to a
maximum of 100 per equipment when all changes cannot be transmitted completely or a
communications failure occurs to the control room operator stations.
h) Displays
Call up time to bring full display with all information of a standard operation display shall be within
two seconds. All dynamic data including historical trends embedded in graphic displays shall be
presented on the monitor within the call up time.
All operational displays and customised graphics shall have a data refresh rate of 1 second and all
other facilities shall have an initiation response time within 2 seconds of the request being made i.e.
reports and logs.

i) PCS System Boot Up After Power Failure


All nodes on the real-time network shall boot up from self-contained database without dependence
on other nodes.
Control Modules shall detect power failure/recovery and perform immediate power fail/recover
processing and set the control algorithm status to certain defined conditions.
All Control Modules and nodes connected on the real time process LAN network shall boot up
automatically upon power source recovery. Each Control Module or node on the network shall have
its own database stored inside it, which will enable it to boot up independently without loading the
database from other nodes or servers on the network.
Operator stations and historisation platform shall boot up automatically to the level where all its
functions are in operation. User log in and password shall not be required during the boot up
process. Boot up shall take place automatically upon switching on the power source.

j) PCS Loading
The equipment shall be designed so that under full load conditions, the loading of Processing shall
be less than 80%, and that of the Memory shall fall below 70%.
Network load in normal operating condition shall not exceed 50%. This load shall be calculated
based on the conditions of "No alarm status" and "All operator displays are continuously updated
at one-second cycle with 50 dynamic data per display" occurring simultaneously.

k) PCS Performance Guarantee

16
APRIL, 2007 NIOEC-SP-70-08 (2)
The performance figures shall be maintained by the PCS at all times independent of system loading.
The VENDOR shall provide typical and guaranteed figures for the system offered and the
equipment shall be guaranteed for satisfactory performance at all operating conditions specified by
the PURCHASER.

9.3 System Cabinets Mechanical and Electrical Design

9.3.1 Mechanical Design


• Internal layout of cabinets shall be designed to provide unimpeded access to all electronic
modules, power distribution switches, fuses and terminals and field cable termination areas.
• Internal framework shall be designed to provide rigid and secure mountings for module racks,
power distribution and field cable termination areas.
• Framework shall be braced as required to resist vibration movement.
• Cabinet assembly shall utilise nuts and bolts of adequate size and strength to suit the
application. Self tapping screws and pop rivets shall not be used.
• Individual cabinet sections shall match accurately with those adjacent in terms of location
holes, overall dimensions and finish.
• Neoprene rubber seals shall be used to seat all doors and side panels.
• Each cabinet shall be designed as free standing units with side walls.
• Cabinets shall be constructed in sections for transportation. Each cabinet section shall be
provided with removable, lifting eyes for handling. Group lifts shall employ lifting frames.
• Cabinets shall be plinth mounted. Plinths shall be drilled for mounting by M12 (minimum)
bolts. Plinths shall be removable for installation.
• Access shall be by means of 135 degree hinged doors to each cabinet at front and back.
• Cable entries shall be via the bottom of the cabinets from an under floor void. Cables shall be
adequately clamped and supported to minimise strain on connectors, associated termination’s
and equipment.
• Each cabinet section and console shall include a pocket for cabinet layout and termination
drawings. Cabinets shall have adequate internal lighting.
• Ventilation
a) Full heat gain calculations for each cabinet and console type shall be provided.
b) Ventilation requirements shall be arranged to avoid the creation of local hot spots. Forced
ventilation systems shall be fitted to the stations and cabinets where necessary. All ventilation
intakes shall be filtered.
c) Forced ventilation systems shall consist of twin paralleled systems each rated at 100% duty.
Each system shall be fed from the cabinet/console power supply via its own dedicated fuses,
contact breakers and thermostats. Fan failure shall annunciate at the operator stations.
d) Forced ventilation systems shall be fitted with the maximum noise level of 55 dBA.

9.3.2 Marshalling Cabinets


• General
The requirements for marshalling cabinets shall be as follows:
a) PCS Marshalling Cabinets shall provide the facility for terminating all input/output field cables.
The cabinets shall house the Vendor's standard field termination assemblies; these shall be located
at the rear of the cabinets. I.S. Isolators, receivers and their associated Intrinsic Safety (I.S.)
isolators shall be provided by the Vendor and included within the PCS Marshalling Cabinets.
Interconnecting cables between the system cabinets and marshalling cabinets shall also be within
vendor’s scope of supply.
b) Intrinsically safe signals

17
APRIL, 2007 NIOEC-SP-70-08 (2)
All incoming and outgoing field cables shall terminate on the terminals of I.S. Isolators in the cabinet.
Cable shields shall be grounded at the cabinet via exclusive terminals. The vendor shall also provide
I.S. Isolators.
c) Non Intrinsically Safe signals
All incoming and outgoing field cables shall terminate on feed through type fused terminals
Multi-core cables shall be used to interconnect the cabinet to PCS cabinets.
d) All field cables shall be multi cores individually or overall screened twisted pairs, armoured and
overall sheath type. Cable screens shall be terminated in the Marshalling Cabinets. All cables shall
be identified and suitably tagged with polarity indication.
• Categories
PCS Marshalling Cabinets shall be sub-divided and segregated into the following categories and
types:
a) Analogue circuits by process unit and IS/non-IS type signals.
b) Digital circuits by process unit and IS/non-IS type signals.

9.3.3 Electrical Design


a) All field termination areas (screw terminals) shall be readily accessible via key lockable doors.
b) All spare module locations shall have blanking plates fitted to the racks. Spare input and output
module locations shall be fully wired to spare terminals
c) Cableways
• Cable trays, wire-ways and tie-bars shall be supplied to separately support field and cabinet
wiring. Wire-ways for field and cabinet wiring shall not be filled to greater than 50% of their
total capacity). Each cable entry, cable tray and wire-way for field cables shall be sized taking
into account the number and diameters of field cables to be installed and allowance for
utilisation of spare capacity. As a general rule, cable trays shall be sized for a single layer of
cables and to take into account future use of spare l/O capacity.
• The layout of cabinets shall provide for unrestricted routing for incoming and outgoing cables
between cable entry and terminations.
• Cable trays shall be of slotted electrolytic zinc plated steel construction free from all burrs and
sharp edges. Securing bolt head shall not damage wiring.
• Wire-ways shall be of the vented flame resistant low smoke, low toxicity type. Removable
covers shall be provided.
• Cable tie-bars material of construction shall be of stainless steel.
d) Wiring
• Cabinet/console wiring shall be flame-retardant volt grade, stranded conductors.
• Wiring shall be sized according to service. Maximum current per conductor and conductor
bundles shall be 90% of the cable manufacturer’s allowable current rating at maximum soak test
temperature.
• Wiring colour code shall be Live – Brown, Neutral- Blue for 230 Vac Feeders, Positive – Red,
Negative- Black for DC Feeders, Electrical Dirty Earth – Green, Electrical Clean Instrument
Earth - Green and yellow, and Electrical IS Instrument Earth - Green and Yellow with light blue
banding.
• Each wire shall have identifying markers, using sleeve or plastic ferrules at all terminal points,
showing terminal number and appropriate instrument tag number.
• All wiring to terminals shall be individually and alpha-numerically identified with respect to
the terminals.
• Wiring shall be routed in such a way that it will not impede maintenance work such as card
removal etc.
• Cables within wire-ways shall be secured with plastic ties to prevent spilling when covers are
removed.

18
APRIL, 2007 NIOEC-SP-70-08 (2)
• Wiring of different signal levels shall be adequately segregated in accordance with the
appropriate standards and codes. Field termination side of terminal banks shall be reserved for
field cabling only Field cabling shall occupy dedicated cable trays and wire-ways.
• Power cables shall be separated at least 300 mm from all signal cables. Vendor shall take care to
avoid electrical interfaces.
• Plugs and sockets shall have nameplates on the mounting plate identifying their number.
e) Power Distribution
• Power distribution shall be divided into individually protected branch circuits
• Branch circuit protection device shall be a circuit breaker. Time-current characteristic shall be
such that the upstream protection device shall not operate for a fault in the branch circuit.
• Each module/component in cabinets requiring AC power shall have its own circuit breaker
within the cabinet.
• Each DC power supply unit, within the cabinets, stations etc., shall have its own AC and DC
circuit breakers.
• For further distribution of cabinet DC power supply to electronic cards/modules, such as
controllers, with built in fuse protection, isolating switches shall be provided.
• Branch circuit disconnect switch is required for branch circuits protected by fuses. Switch shall
be connected ahead of the fuse.
• Each console, printer, annunciator shall have dedicated circuit breaker.
• Analogue inputs and outputs shall be fused at the marshalling cabinet terminals when the 24
VDC loop power is not supplied through the I/O card.
• All field I/O’s in a non I.S. installation shall have the ability to disconnect power to each field
instrument individually at the marshalling panel by means of a fused terminal or a disconnect
terminal. This is to enable the removal of an individual instrument for maintenance.
• All digital outputs shall be fused at the marshalling panel terminals.
f) Terminals
• Terminals shall be selected according to field and panel conductor size and rating. Terminals
shall be Screw type, Klippon or equivalent. Wire ends shall have crimp-on vinyl self insulating,
locking type lugs.
• Medium duty, 300-600 Volts rating barrier type, non-hygroscopic material type terminal blocks
shall be provided.
• Terminals shall be either tinned or silver plated and terminal numbers shall be clearly identified.
• Terminals shall be so located that they are easily accessible.
• Adequate space and/or barriers shall be provided to facilitate easy maintenance work.
• Terminal blocks shall be mounted on channels with a minimum of 25-mm spacers between
cannel and mounting surface.
• Separation between the terminal rows shall be 200-mm minimum.
• Terminal blocks shall be mounted vertically.
• Different signal levels shall run on different terminal rows and shall be physically segregated by
space or barriers.
• The relevant signal level on any terminal row shall be clearly marked on the terminals.
• Terminals shall be individually identified alpha-numerically. Banks of terminals shall be
labelled as to service. Field cabling shall govern terminal grouping i.e., terminals shall be
arranged to accommodate the field cables in sequential rows.
• Spare terminal rail space shall be provided such that the prepared and equipped spare capacity
within the corresponding cabinet/bay can be fully utilised. As a minimum, 20% spare space
shall be provided on each rail for future field cable terminals. All field cable cores and screens
shall be terminated on terminals.
• Only one conductor shall be terminated in each side of a terminal. All Looping shall be by
means of jumper bars.

19
APRIL, 2007 NIOEC-SP-70-08 (2)
• Protective covers shall be provided over all power distribution terminals to reduce the
likelihood of accidental short-circuits and contact by maintenance personnel. Appropriate and
clear identification and warning labels shall be provided.
• Terminals shall be so arranged that all incoming and outgoing cables have a minimum straight
length of 150 mm from the point of entry.

9.3.4 Power Distribution Cabinet


The Vendor shall provide a power distribution cabinet in the equipment room. The cabinets shall be
installed separate from UPS panel. The cabinet shall receive UPS power and distribute the same to
the PCS and ESD equipment. Within the cabinet, the incoming ac supply shall have a main circuit
breaker. The distribution of power shall be by means of a dedicated and individual circuit
protection/isolation device for each power user. The cabinet face shall have voltage, frequency and
current indicators for as and dc type supplies. 20% spare protection/isolation devices and terminals
shall be provided.

9.3.5 System Electronic Modules Design and Construction


• Design and construction of electronic assemblies shall be modular. Full account shall be made
of the necessity for speedy location and replacement of defective parts with the minimum
amount of dismantling or removal of associated equipment.
• High density packaging techniques shall be employed throughout the design.
• Modules shall be identified as to type. Module identification shall be clear and wear resistant.
• Modules shall be robustly constructed and incorporate mounting frames affording protection
and ease of rack location. Printed circuit boards shall be high quality, copper clad, reinforced
fibreglass type. All printed circuits boards shall be suitably coated with a coating type, which
has proven to be effective in the protecting of circuits and components against corrosion and
fungus growth.
• All electric materials shall be designed and manufactured using non-hygroscopic, non-nutrient
materials in order to reduce fungus growth susceptibility. Wiring insulation materials shall be
resistant to fungus growth.
• Modules shall be secured within racks. Rack connections shall be by plug-in DIN 416 type
two part connectors or equivalent.
• Back-of-rack connections shall be by screw and clamp type terminal or a reliable two part
conned incorporating a locking device.
• The modules shall be identical in size and in appearance.
• Each module shall be housed in a metal case to prevent physical damage from handling or
dust.
• Exposed plug-in contacts on printed circuit boards shall be gold plated to prevent corrosion.
Contacting of dissimilar metals shall be avoided to prevent galvanic corrosion.
• All modules must be rated for operation within 0-60°C and 0-95% relative humidity.
• The modules shall be grouped together in racks to form the control system. The racks shall
provide the communication mechanism to fully integrate the modules and facilitate
intercommunication between racks.
• Each slot shall be identical and able to accept any module. Modules shall be connected to the
backplane using high quality, gold-plated, industry grade pin connectors; card edge connectors
shall not be used in the racks.
• It shall be possible to remove and reinsert the modules under power with no damage to the
rack or modules and without removing any external wiring or cables. The rack and modules
shall provide a physical keying mechanism to prevent incorrect module insertion during
system operation.

20
APRIL, 2007 NIOEC-SP-70-08 (2)
• To simplify installation and maintenance, the modules shall be designed for front access only,
with all user functions, diagnostics and cabling available from the module fronts.
• The racks shall be mounted in industrial type cabinets.

9.3.6 Cabinet and Station Grounding


In general AC Safety ground and instrumentation circuit ground shall conform to NEC, Article 250
with due consideration to the following requirements:
• The following earthing points, for connection by others, shall be provided:
a) Panel steelwork - electrical “dirty” earth - 2 off M12 brass studs per cabinet/console section.
b) Clean earth - electrically insulated copper bus bar of 75mm2 minimum, separated from the
cabinet/console steelworks by 25-mm minimum. 2 off M10 brass earth studs to be provided at
each end of the bars.
c) IS earth - electrically insulated copper bus bar of 75 mm 2 minimum, separated from
cabinet/console steelworks by 25 mm minimum. 2 off M10 brass earth studs to be provided at
each end of the bars.
• All cabinet/console internal fabrication and racks shall be earth-bonded together.
• Each earthing stud and bus bar shall be permanently and durably labelled as to its service.

9.3.7 Cabinet Smoke Detectors


Cabinets containing power consuming devices such as system cabinets, etc. shall be equipped with
smoke detectors to be connected to PCS and annunciated at relevant operator stations.

9.3.8 Physical Installation of Foundation Fieldbus Devices

The relevant requirements of FOUNDATION™ Fieldbus standards shall be followed.


In addition, the limit of the devices resident on H1 network shall conform to the classification of
FOUNDATION FIELDBUS END USER ADVISORY COUNCIL.
Each field device shall be connected to the segment via a “short circuit “proof junction box

9.3.9 Power Supply Requirements


All power supplies for field controllers shall be dual redundant. Power conditioning and isolation
shall be performed at each module to eliminate potential for ground loops. Power distribution shall
be performed in a manner such that any single power supply failure will not cause loss of operation
of any module.
Separate isolated power supplies shall be used for system power and field loop power.

9.4 Equipment Maintenance


Control configuration in the controllers shall be stored in flash memory providing an infinite storage
time. Controller memory stored by batteries is not permitted.
The equipment shall use standardized, modular, plug-in construction so that any module may be
easily removed from the system and replaced without breaking or making I/O connections.
The system shall be provided with modular components that make it easy to install and maintain.
When these modules are inserted into the enclosures the redundant power and redundant
communication network connections shall be made. Failure or removal of any physical component
will not affect the modules at the same or higher levels. All I/O modules and redundant controllers
must be installable under power.

21
APRIL, 2007 NIOEC-SP-70-08 (2)
9.5 Inputs and Outputs

9.5.1 Traditional Input and Output


For control loop applications, which Foundation Fieldbus or Profibus field devices may prove
unsatisfactory or impractical, traditional I/O shall be used. PCS vendor shall design and include
within the system the required traditional I/O interface cards and the associated controllers.

a)Transmitter Failure Detection


Analogue 4-20 mA input cards shall be capable of differentiating between an out of range
measurement signal and a failed transmitter signal.
The control system vendor shall coordinate with the Contractor to determine what field device
failure alarm levels have been selected (such as NAMUR NE 43 engl. compliant transmitters).
Upon detection of either high or low transmitter failure alarm signal, the control system shall
generate a critical alarm (visual and audible).

9.5.3 Manual Input


The system shall be capable of accepting manual entry inputs into a tag type configured for such
manual entry.
Manual inputs may be of Analogue values or Digital values type.
Tags receiving analogue and digital manual inputs shall be treated as any other analogue or digital
tag with regard to availability to historization, trending, calculation and controller blocks, and high
level language programs.

9.5.4 HART I/O


The system shall be capable of supporting HART inputs and outputs.

9.6 System Communication


The PCS communications system shall employ a fully redundant industrial Fast Ethernet Network
for interface to all PCS controllers, Operating Stations, Engineering Stations and Control System
Servers. No point of failure should result in communication loss between any and all network
resident devices. The Ethernet Network system shall employ TCP/IP communications to all
network resident devices with a minimum bandwidth of 100Mbit/sec.
Continuous communications diagnostics shall alarm a failure in the minimum of time and switch to
the redundant communications automatically. Any communication errors shall be available to be
logged to any station in the system. Communication system status/performance shall be made
available to any station in the system.
Nodes on the control network shall be synchronized across the entire network to within +/- one
millisecond.

9.7 Control and Data Handling

9.7.1 Calculations
Algorithm calculations shall be performed in floating point engineering units or other such
equivalent methods that do not require scaling.

9.7.2 Regulatory Control


All control processors must be able to have direct peer-to-peer communications between all other
control processors

22
APRIL, 2007 NIOEC-SP-70-08 (2)
9.7.3 Algorithms
Standard Foundation Fieldbus software algorithms shall be available to perform regulatory control
functions. These process control functions shall be performed by predefined algorithms with
configurable parameters.
Standard Foundation Fieldbus control algorithms shall be identical regardless of whether they reside
in system controllers or the H1 field devices.

9.7.4 Input Scanning


Controllers and Foundation Fieldbus devices shall scan inputs at a sufficient frequency to provide
freshly sampled data for each control loop execution cycle.

9.7.5 Control Loop Execution Frequency


It shall be possible to select the execution frequency of each control loop regardless of execution in
the system controller or field device. The following selections shall be available:
• One second
• One half (1/2) of a second
• One quarter (1/4) of a second
The maximum allowable control response period shall follow the requirements of paragraph
9.2.15.a.

9.7.6 Output Functions


The following Foundation Fieldbus output functions shall be supplied as standard configurable
items and shall be the same regardless of execution in the system controller or field device:
• Linear
• Linear with clamping (high and low restricted)
• Non-linear characterization
• Rate of change limits

9.7.7 Setpoint Clamps


Upper and lower clamps on all setpoints shall be available.

9.7.8 Windup protection


Control functions that include integral action shall provide windup protection. Windup protection
shall inhibit the integral action when the control block output is constrained by conditions such as:
• Output at high or low limits of span,
• Output at high or low clamps,
• Output is connected to the setpoint of a secondary controller which is clamped,
• Output tracking is active,
• Output is not connected to any valid device or algorithm.
Requirement for “Output tracking is active” does not apply if the primary controller is connected to
a secondary controller which is not currently in cascade mode, or if a controller loses
communication with the output module due to hardware failure.
When windup protection is active, this status shall be clearly visible to the operator in a standard
faceplate display, and shall set a parameter that is accessible to graphic displays and application
programs.
Control functions and computational functions shall include the ability to propagate the windup
parameter through multilevel control strategies.

23
APRIL, 2007 NIOEC-SP-70-08 (2)
9.7.9 Sequential Control
The system shall be capable of performing the following sequential control without any
modifications to the standard configuration software.

9.7.10 Sequence Language


A structured, IEC 61131-3 compliant high-level control programming language shall be available
and shall conform to the following specifications:
• It shall provide the necessary facilities for real-time control of sequential processes.
• It shall have access to process control and other database information.
• It shall be possible to modify the program logic while other sequences are active.

9.7.11 Auto-tuning
An auto-tuning facility shall be available in the automation system. It shall be:

• Applicable to processes with slow and fast dynamics


• Used with self-regulating and integrating processes
• Immune to noise and process load disturbances

This auto-tuning facility shall allow tuning of PID and fuzzy logic control blocks whether they
reside in the controller or the Fieldbus device. An easy-to-use graphical interface shall be provided
for auto-tuning.

9.7.12 Fuzzy Logic Control & Algorithms


The control system shall support functionality to implement single input-single output and multiple
input-single output control strategies using fuzzy logic algorithms as an alternative to PID
algorithms for use in processes with difficult, widely varying processes which require non-linear
action to provide adequate control.
It shall be possible to implement these fuzzy logic class algorithms using the same standard
engineering tools as would be used for PID controllers.
It shall be possible to execute these fuzzy logic algorithms and compute new outputs as fast as once
every 100 ms.
The fuzzy logic algorithm shall execute in an optionally redundant control system processor as
opposed to a station for purposes of availability.
The system should preferably allow configuration using fuzzy logic control. This capability, if
provided, shall be standard in the system and shall not require any additional software modules. It
shall be possible to use the auto-tuning facility to tune loops implemented using fuzzy logic.

9.7.13 Control Execution Monitoring


The system shall provide a mechanism to view control strategies as defined in the configuration
while they execute in real-time as well as the real-time input and output values. When a tag is
selected, the operator should be able to press a single button to view the control strategy. No
additional configuration shall be necessary to provide this functionality.

9.7.14 Predictive Maintenance Diagnostics


The system shall have the capability to perform predictive maintenance and shall be able to capture
and performance diagnostics data that are embedded in intelligent field devices. Likewise, the
performance degradation of control valves shall be captured through on-line diagnostics using
intelligent valve positioners communicating over Foundation Fieldbus digital wiring.

24
APRIL, 2007 NIOEC-SP-70-08 (2)
9.7.15 Loop Performance Monitoring
The automation system shall monitor all active control loops and set a flag upon detecting
degradation in any loop performance or upon detecting an abnormal condition in a measurement,
actuator, or control block.
The following conditions shall be flagged:

• Bad I/O. The block process variable is bad, uncertain, or limited.


• Limited control action. A downstream condition exists that limits the control action taken by
the block.
• Mode not normal. The actual mode of the block does not match the normal mode configured
for the block.

A variability index shall be calculated for each loop. This index shall be used to quantify the
following and present the results graphically: loop utilization; bad, uncertain and limited
measurement status; control action limitation; and process variability. Excessive variability shall be
automatically flagged.

This capability shall be a standard feature of the system. No additional configuration shall be
required to add it. The system shall automatically detect when new control modules are added or
deleted in the configuration and activate loop performance monitoring.

9.7.16 Process Simulation


A simulation facility shall be available, if specifically required in the project specification, with
built-in process modelling tools and shall comprise a complete process simulation environment. In
this environment, the process configuration shall be observed and analyzed.

This facility shall run on a stand alone PC and shall emulate the controller I/O and process. It shall
be able to simulate up to 8 controllers at the same time.

During training activities, a training tool shall be available to capture and record all trainee actions
in a session report. The report shall contain information such as the scenario name used,
malfunction name(s) used, and event log messages. It shall become part of the documentation for
the employee’s performance during the training.

9.8 Configuration and Database

9.8.1 Configuration
a) Engineering Station
It shall be possible to install more than one engineering station in a system.

Only one engineering station shall be necessary to perform all traditional and Foundation Fieldbus
configuration, database generation, and editing. However, it shall also be possible to use multiple
engineering stations simultaneously for configuration, database generation and editing.

The automation system shall use a single, global configuration database to be shared by all
components of the system. User shall not be required to enter the same data or configuration more
than once.

9.8.2 Configuration Tool


A configuration tool shall be provided to generate or modify database and configuration data.

a) Configuration Audit trail

25
APRIL, 2007 NIOEC-SP-70-08 (2)
The system shall have the capability of collecting and monitoring revision information for any item
in the configuration database.
The system shall document who made the change and when the change was made.
Differences between two versions of the configuration shall be viewed in either text or graphical
formats.
The system shall provide the ability to roll back a single item or the entire database to a previous
revision.
The functionality of version control shall not require any configuration.
It shall be possible to print configuration change histories for any item in the configuration database
b) Configuration Displays

Configuration displays shall be provided to aid in system configuration. All displays and tags will
reside in one global database shared by the entire system. No data mapping between systems shall
be allowed.

9.8.3 Tag Parameters


All tags shall be defined with at least the following parameters:
• Tag ID
• Tag descriptor
• Tag type
• Alarm requirements
Tag IDs shall be unique throughout the system; and access to all tag parameters for configuration
shall be available directly by tag ID.
The system shall provide the capability to define free-format alphanumeric descriptors for each
state of a multi-state device. Four states shall be allowed for each multi-state device (for example,
open, closed, in-between, and fault for an MOV).

9.8.4 Engineering Units


Each analogue input, output, and control block shall be assigned an engineering unit designation. It
shall be possible to automatically display this designation with the value when the input, output, or
algorithm is accessed.
It shall be possible for engineering units in the H1 field devices to be different than engineering
units in the other modules of the system. In these situations the conversion of engineering units
shall be performed automatically.

9.8.5 Data Base, Reporting and Modification Utilities


a) The data base shall be SQL based type.
b) Global Search Utility
Utilities shall be provided for global searching of the database. These utilities shall be under system
access control.
c) Cross Reference Listings
The system shall be capable of generating listings containing the following fields:
• Tag ID
• Tag descriptor
• Point type
• Hardware address
It shall be possible to perform the following functions on the above list:
• Sort alphanumerically by any field,
• Filter by any field,
• Print, display and store to media.
The above listings shall be available for all devices in the system.

26
APRIL, 2007 NIOEC-SP-70-08 (2)
If a failure is detected in any backup equipment, the operator shall be notified and the failure shall
be logged.

9.8.6 System Access


Access to automation system functions shall be restricted using passwords. It shall be possible to
define single users with selectable access privileges. It shall also be possible to define groups of
users. All users within each group shall have the same privileges. It shall also be possible to limit a
user to particular areas of the plant.
At a minimum, the following access privileges shall be available:
• Operate
• Tune
• Download
• Plant Area
• System Administrator
• The automation system passwords shall be global for the entire database.

9.9 Operator and Engineering Stations

9.9.1 General
Failure of any component shall not cause the failure of more than one station.
Each operator and engineering station shall have access to, either directly or through a network, an
electronic log, as well as optional printer for logging alarms, system events and other information.

9.9.2 Operator Stations


• Each operator station shall be capable of being operated in a standalone mode with access to
all graphic displays and their functions.
• User configurable buttons or screen targets to select operational functions or displays with a
single entry shall be provided. It shall be possible to change control assignments to allow
control of any plant area from any operator station by using the appropriate access password.
• It shall be possible to connect two monitors to the same station processor. Both monitors shall
be driven from a single keyboard and mouse and shall act as one large monitor. No special
user training shall be required. Without any special configuration, user shall be able to select
an item on one screen and drag it to the other screen.
• The two-monitor station shall also allow user configurable layouts. It shall be possible to
dedicate either one or both monitors to the operator interface. Additionally, it shall be possible
to use the second monitor to view other applications without occluding the operator process
graphics and displays.
• The real-time tag database shall be capable of updating all tags in a period no greater than 1
second.

• Each station shall have access to a minimum of two printers, of which at least one should be a
colour printer.

• The operator interface software shall be capable of acting as a Dynamic Data Exchange (D-
DE) or OLE (Object Linking and Embedding) for Process Control (OPC) client or server to
share real-time data with DDE or OPC compliant applications.

9.9.3 Engineering Stations


• Any display and data configured from any engineering station shall be globally available to
any engineering station or operator station on the control network.

27
APRIL, 2007 NIOEC-SP-70-08 (2)
• Each engineering station shall be capable of being operated in a standalone mode with access
to all graphic displays and their functions.
• A QWERTY keyboard shall be provided with each engineering station.
• Removable storage media shall be provided at each engineering station.
• Configuration and on-line operation should be password-protected with at least three levels
of security (Engineering/configuration, supervisor, and operator) to avoid inadvertent
changes.

9.9.4 Monitors
Monitors for operator stations shall be LCD type with 21 inches nominal in diagonal measurement,
with 1024 x 768 resolutions.

9.9.5 Display Hardcopy


The capability to generate a hardcopy of any active display shall be available.
The system shall support both full colour and black and white copies for all displays.
It shall be possible to connect up to four monitors to a single video copier or printer.

9.9.6 Printers
Laser printers shall be supplied and supported.

9.10 Displays and Graphics

9.10.1 Updating Capability


All displays and graphics that show real time data shall be automatically updated when the display
or graphic is on a screen. Updates shall not require operator initiation.
Data update time shall be as follows:
• Updating screen information – 1 sec or less
• New display with fresh data – 2 sec or less
• Response to operator actions – 1 sec or less

9.10.2 Displays and Graphics Access


Operators shall be able to easily access specific displays and graphics by pressing dedicated
function keys or screen targets, selecting from a list of displays in directories or menus, or by typing
display or graphic names.
Any graphic display configured from any operator station shall be globally available to all other
operator stations.

9.10.3 Hierarchical Displays


It shall be possible to move between related displays and graphics of different detail levels or of the
same detail level with a maximum of two operator actions.

9.10.4 Paging
It shall be possible to cycle through a predefined series of displays with a maximum of one operator
action.

9.10.5 Invalid Values


Special indication shall be used to indicate that a value is invalid.

28
APRIL, 2007 NIOEC-SP-70-08 (2)
9.10.6 Faceplates
Faceplates shall show dynamic process and status information about a single control loop and shall
permit an operator to change control parameter values or mode for the loop.
The system shall automatically provide default faceplates for each tag. User shall not be required to
configure a faceplate detail display for each tag or control module.
Faceplates shall be defined to pop-up when the appropriate location on a process graphic is selected
with the mouse.
Faceplates shall display the following information as applicable:
• Tag ID.
• Tag descriptor.
• Process input, setpoint, and output values displayed numerically with engineering units.
• Process input, setpoint, and output in bar graph representation.
• Auto/manual mode and remote/local setpoint status.
• Visual indication for alarm status.
• Symbolic and alphanumeric indication of discrete states both for two state devices and multi-
state devices.
It shall be possible to perform the following control actions from a faceplate:
• Change control block mode.
• Change setpoint and other operator settable parameters.
• Issue commands to multi-state devices
• Adjust outputs in manual mode
Single faceplates shall be provided for control and indication of multi-state devices. For example, a
motor operated valve shall indicate open, closed, intermediate position, and fault.
First out trap in a series of interlocks/permissive for discrete control devices shall be displayed by
description on the operator interface.

9.10.7 System and Diagnostic Displays


a) Communication System Status Displays
Standard displays shall show the operational status of the communication system. The
communication parameters of each module connected to the communication system (on-line, off-
line, failed, primary failed, backup failed) shall be shown.
b) Self-Diagnostic Tests Results Displays
On-line displays shall indicate the results of self-diagnostic tests. Failure diagnosis shall be
sufficiently specific to indicate which printed circuit boards, modules, or devices are at fault. The
displays shall be designed to help maintenance and engineering personnel diagnose faults in the
system and communications paths. Each category of diagnostic display shall be organized
hierarchically.
c) Redundant Path error displays
Communications diagnostic displays shall show errors for each of the redundant paths.
d) Event Capturing
All events generated by the system shall be captured and electronically logged chronologically to
the event database on a hard disk on one or more designated stations. Events shall be time-stamped
by the event generator. Events and their associated time stamp are passed to the event handler for
capture.
It shall be possible to retrieve and sort events by time (ascending or descending order) or by type.
The Operator shall be able to filter the events on certain criteria such as time, tag name, area name,
or any specific event. Events and the historical trend information for a control tag shall be
integrated into a single view.
All events shall be time stamped at the point of origin. Events generated in the controller shall be
time-stamped in the controller. Those generated in the station shall be time stamped in the station.
Print on demand shall be included for all views possible with the event viewer application.

29
APRIL, 2007 NIOEC-SP-70-08 (2)

9.10.8 Graphics
a) General
A standard utility shall be provided to generate and modify user-defined colour dynamic graphics.
The utility shall have the capability to make a copy of an existing graphic in order to build a new
graphic that is similar. It shall use the same tag IDs that are used in the process database to access
real-time variables from any database. No intermediate index numbers or addressing shall be
required. It shall be subject to system access protection.
The system shall provide the facility to place a new graphic in service without interrupting an
operator's ability to control the plant.
The system shall make it possible to scan images and use them in a graphic display to help an
operator easily identify the process parameters being operated. Dynamic information shall easily be
added to the images.
All control, monitoring, and status attributes of any tag shall be displayable on graphics. For
analogue points this requirement includes measurement, setpoint, alarm limits, and output. For
digital points this requirement includes input and output status. Status information includes: alarm
status, control mode, and control status.
Numeric data shall be configurable on an individual basis. If the decimal point is not used, it shall
be suppressed.
Each state of a multi-state device shall be indicated by a unique foreground/background colour
combination.
It shall be possible for inactive alarm or status messages to be invisible to the operator.
Symbolic representation of data on the graphics shall be performed by colour changes (foreground
and background independently), and flashing in any combination.
Users shall be able to create symbols and store them in a permanent library. The graphic builder
utility shall have facilities to maintain this library with version control.
A screen target that calls up other displays shall be configurable.
There should not be a limitation of the number of graphic display pages that can be configured on a
single operating station
All control parameters shall be accessible through the graphic display. Navigation through the
displays should be easy and intuitive. One overview graphic display per process unit shall be
provided in order to quickly access the detailed graphics- Viewing of information in real-time shall
include all remote setpoint; whether calculated or not.
All loop controllers shall have faceplates. These faceplates shall allow easy access to tuning
variables, trending, setpoint values (both local and remote), alarm settings, auto/manual,
remote/local, and percent output-
Pop-up functions (faceplates, trends, reports etc.) should allow large amounts of detailed
information to be quickly accessed without extensive clutter on a process graphic.

The PCS output display for all control valves shall be configured such that it is readily apparent to
the operator how the output must be changed to manually open or close the valve. Configuration
such that an indication of 0% output is dosed and 100% is open regardless of valve failure action, or
other labelling methods, may be used.
Each Graphic display shall include not more than 50 live data for ease of operator interaction.
Each display shall have its own number and descriptive title clearly displayed in the display. For an
easy and fast call up of a graphic display, each graphic display of the unit shall be represented by an
assigned function key on the operator keyboard. Each station shall be able to support at least 100
graphic displays.

30
APRIL, 2007 NIOEC-SP-70-08 (2)
b) Call up of Graphic displays
Operator shall be able to call Graphic displays using any one of the following procedures:
• Entering the unique Graphic display number.
• Referring to an index display and selecting by cursor.
• Selecting the particular assigned function key on the keyboard.
c) Operation of Graphic displays
Each symbol representing an instrument shall be a touch/cursor target on the graphic
display, i.e. by selecting or touching the target, the operator shall be able to:
• Call the target Point /Loop relevant Group, Detail or Trend display.
• Perform Loop manipulation, via a dedicated purpose designed part of the
screen, such as loop parameter change, Auto/Manual change, interaction with
the final control element etc.
Process lines shall enter the display on the left and leave the display on the right.
Service and source/destination address shall be clearly shown for each line.
It shall be possible, by selecting the source or destination addresses to move to the
relevant preceding or following graphic displays.
d) Presentation of live data
Each display shall include live data such as process variables, set points, control outputs, on/off status
of rotating equipment, open /close status of valves, alarms.
Live data shall be refreshed in less than 1 second.
Indication of measurements and set points shall be in numerical format in relevant units.
Status signals shall be shown by descriptive format such as ON, OFF, OPEN, CLOSE and/or by colour
change.
Alarms and invalid values shall be clearly indicated and prompted to alert the operator.
Date and time shall be indicated in every screen continuously.

9.11 Alarm and Message Handling

9.11.1 Categorizing Messages


a) General
Process and designated system alarms shall be annunciated, displayed and stored in electronic
history files. Normal plant operator actions, events and normal system actions and events shall not
be alarmed; however, they shall be stored in history files if designated. Alarms shall have the
capability of being configured at the unit or control point level.
Alarms and messages shall be grouped to allow the user to readily identify and respond to alarms
and conditions (e.g., in priority sequence) in his area of responsibility.
For any process alarm, it shall be possible, by no more than one operator action, for an operator to
access a display from which he may take corrective action.
The five highest priority alarms shall be displayed in descending order of priority.

Alarm functions shall be implemented using the data acquisition and shared processing equipment
of the control system. All alarms shall be visually and audibly indicated and shall be connected to
event logging facilities.
b) Critical Alarms
These alarms are considered to be of high importance and are associated with a process condition or
a special circumstance that requires immediate operator action. Examples are shutdown pre -alarms,
shutdown alarms, and critical equipment alarms.

31
APRIL, 2007 NIOEC-SP-70-08 (2)
Alarms in this category require a unique display and audible tone to clearly distinguish them from
non critical alarms. Critical alarms shall be distinguished from other alarms by a unique colour,
grouping, or graphical display on the PCS and/or displayed on a separate, "back lighted-nameplate"
annunciator panel located above or adjacent to the operator station.

c) Non-Critical Alarms
This category alarm is generally for services not associated with a shutdown function or critical
equipment protection.

Process and designated system alarms shall be annunciated, displayed and stored in electronic
history files. Normal plant operator actions, events and normal system actions and events shall not
be alarmed; however, they shall be stored in history files if designated.
Alarms shall have the capability of being configured at the unit or control point level.
Alarms and messages shall be grouped to allow the user to readily identify and respond to alarms
and conditions (e.g., in priority sequence) in his area of responsibility.
For any process alarm, it shall be possible, by no more than one operator action, for an operator to
access a display from which he may take corrective action.
The five highest priority alarms shall be displayed in descending order of priority.

9.11.2 Operator Actions


It shall be possible to store all operator actions that affect process control parameters or alarm
acknowledgment in history files, including:
• Inhibit/enable alarm,
• Change mode of controllers,
• Change setpoint of controllers,
• Changes to alarm limits,
• Changes to tuning parameters.

9.11.3 Engineer Actions


Engineer actions that change the control and monitoring of the process shall be stored in history
files. These actions shall include the following:
• Placing stations and devices on-line or off-line.
• Download of point configurations.

9.11.4 Process Alarm Initiation


It shall be possible to initiate process alarms by configuring alarm attributes of any process I/O
point or any automation system point calculated from process I/O or system calculation.
To minimize analogue input "chattering" (a point going in and out of an alarm condition rapidly)
there shall be configurable dead band parameters, on an individual alarm basis. These shall include:
• On delay time
• Enable delay time
• Off delay time
• Alarm Hysterisis
User specific alarms can be added to any tag in the system. User specific alarms can utilize any
parameter, perform calculations, etc. To determine unique alarm conditions.
For analogue tags, the configurable triggers for process alarms shall include:
• Process variable high limit exceeded
• Process variable high-high limit exceeded
• Process variable low limit exceeded
• Process variable low-low limit exceeded

32
APRIL, 2007 NIOEC-SP-70-08 (2)
• Process variable rate-of-change high
• Process variable deviation from set point
• Process variable invalid value
For digital tags, the configurable triggers for process alarms shall change of state
Twelve alarm priorities level should be made available. Each priority should be user configurable
for a unique priority name, horn sound, and colour annunciation on graphic displays.
A list of inhibited alarms shall be available to be displayed and printed.

9.11.5 System Alarm Initiation


All devices connected to the automation system communication network shall be monitored for
failures. A system alarm shall be generated for each failure detected.

9.11.6 Process and System Alarms History Retention


All alarms shall be stored in history files with the capability to archive these to removable media.
Capability shall be provided to recall these alarms in visible display lists and printed lists according
to selectable filtering options.

9.11.7 Process and System Alarms Audible Annunciation


All alarms for a process area may be assigned to any station at configuration time. All alarms shall
be displayed on the station(s) designated. The audible alarm shall be user configurable for different
tones or patterns. The system shall have an adjustable volume control. The system shall use global
alarm acknowledgement allowing a single acknowledgement from any station to acknowledge that
alarm on all stations and to silence the audible alarm.

9.11.8 Process and System Alarms Visible Annunciation


Alarms shall cause visible display annunciation at, and only at, a Station configured for those
alarms. The annunciation shall occur within 2 seconds of detecting the initiating event. It shall be
possible to acknowledge process alarms only from a Station configured for those alarms. It shall be
possible for an operator to acknowledge any alarm configured at his Station by no more than two
actions. An alarm shall be acknowledgeable only if it is shown on a visible display.
Active Process Alarms Summary, there shall be a summary display of active process alarms.
Accessing this alarm summary display from any other display shall require no more than one
operator action. This display shall show all process alarms currently in alarm condition. Visible
display of any alarm shall not clear unless the alarm is acknowledged; and the item initiating the
alarm has returned to normal condition.
System shall display all alarms in an alarm summary. Multi-page displays may be used. If so, it
shall be possible to page forward or backward by a single operator action. The display shall list
alarms in tabular format in order of occurrence with the most recent at the top.

9.12 Diagnostics
On-line and off-line diagnostics shall be provided to assist in system maintenance and
troubleshooting. Diagnostics shall be provided for every major system component and peripheral.
This shall include segment as well as device diagnostics and firmware diagnostics in the devices. If
diagnostics do not exist for particular peripheral devices (for example printers and terminals,) the
system must detect and provide an error indication for the failure of these devices.
It shall be possible to configure, monitor, and troubleshoot Foundation Fieldbus devices and HART
devices from the control room. The automation system shall be capable of storing calibration
information and device status history for each field device. It shall also be possible for the
automation system to upload field device configuration changes implemented in the field. Once the
configuration information is stored in the automation system, it shall be possible to download it to
any other similar device, whether a new or replacement device.

33
APRIL, 2007 NIOEC-SP-70-08 (2)
Existing signal wiring shall be used to pass field device data to the diagnostic utility. This shall not
degrade the operation of the system in any way.
It shall be possible to remotely access the system by modem for troubleshooting purposes. User
shall have the capability to disable this feature without disconnecting the modem.

The system shall be supplied with a complete asset management system including:
• Dynamic Error Band – An overall valve/actuator/instrument response to input signal changes.
• Drive Signal – A plot of input versus the drive signal
• Output Signal – A plot of the travel versus the drive signal of a digital valve controller and the
output pressure signal versus the drive signal of the digital transducer
• Step Response – A tool to review response to input signal changes. Dead time, stroking time,
overshoot, and response time can all be determined from this curve.
• Valve Signature – A plot of actuator travel versus actuator pressure. It is used for operational
analysis of the valve and actuator operation, independent of the instrument. Comparison of this
curve to the original factory curve can uncover deterioration in performance.
The system shall provide an audit trail and automatically generate a historical record. Events
recorded in the audit trail shall include device configuration records, as found/as left tests and
diagnostic information. Records shall be tied to plant location and to a specific device. It shall be
possible to view records for an entire plant or for a single device.

9.13 Data Historization


a) All process variable values, controller set point values, and controller output values shall be
stored digitally in non-volatile memory or hard drive within the control system equipment, or in
auxiliary systems communicating with the control system. No distinction shall be made between
direct process variables (e.g. flow, temperature, pressure, level, etc.) or indirect calculated process
variables (e.g. velocity, density, ratio, concentration, etc.). The stored information is used for the
following purposes:

• Determination of plant material balances,


• Trend analysis of equipment performance,
• Troubleshooting and analysis of malfunctions,
• Monitoring the day to day operation.
b) The actual (uncompensated) measured process variable values shall also he saved, when process
variable values are modified by the control system to compensate for process conditions.
c) For the purpose of trouble shooting and analysis of malfunctions, the ability to retrieve and
display the actual instantaneous sampled process data, rather than the averaged or
maximum/minimum values, is essential.
d) All process variables, controller setpoints and controller outputs shall be sampled and the
instantaneous values shall be stored at intervals of five seconds or less. Storage capacity shall be
sufficient to store process variable data, controller setpoint data, and controller output data for at
least the immediately previous 7 day period. Only "lossless" data compression techniques may be
used during this period. The control system equipment shall be able to access and display the stored
data at the operator station console and/or other console on demand at any time. The control system
equipment shall be capable of selecting for display the instantaneous values stored in any 1 hour
period within the 7 days of data. Stored data shall not be erased by display. Update of data shall be
on a point-by-point basis to ensure that the immediately previous 7 days of data are available at any
time. When data compression techniques are an integral feature of the historical data storage
package, the data discrimination delta value shall be set to the minimum setting.

34
APRIL, 2007 NIOEC-SP-70-08 (2)
e) Storage capacity that is capable of retaining daily averages and weekly averages of the process
variable values for a period of one year shall also be provided. The control system equipment shall
be able to access and display the stored data at (lie operator station console and/or other console on
demand at any time.

f) Data stored for historical review shall be accessible in grouped trend display format. The
grouping of the process variables shall be logical with respect to the process. Configuration of trend
displays shall have the capability for operators to set up additional trend displays of selected
variables for specific troubleshooting activities. Different colours shall be used for each variable
trended. Additional trend display capacity shall be available for at least 10 percent of the historical
trend display groups.
g) The control system must be capable of archiving historical data onto removable media.

A configurable, real time and historical data collection package shall be available to support
trending, logging, and reporting. The automation system shall be able to support multiple historian
packages. It shall be possible to collect historical parameters on multiple stations providing
historical backup capability. It shall be possible to supply redundant on-line storage media.
On-line process point collection and storage shall not require any additional configuration other that
the normal module configuration. It shall be possible to enable data historization for each module
within its standard configuration.
The historian shall be capable of collecting continuous history for up to 20,000 parameters.
Historical data must be available to remote desktop PC’s, using standard, off-the-shelf viewing and
analysis software, including Microsoft Excel and Access
The historian shall be integrated into control strategy configuration, such that a separate historian
configuration database does not need to be maintained. Each control strategy would maintain its
own historical configuration information. When a new control strategy is created and downloaded,
it shall include the history definition and the history definition is downloaded to the historian.

9.14 Trend Displays


Every operator station shall provide viewing for real-time and historical trend information. Data
collected in any historian package shall be available to all stations. The system must support
centralizing historical collection.
The system shall support user defined sets of trends so that commonly viewed historical
information can be defined in trends once and easily accessed by selecting a pre-configured screen
target incorporated in the graphic display. There should be no practical limit to the number of
trends that can be defined. Each trend shall support up to 6 separate trends. Selection of points to be
trended shall be menu driven.
Both historical and real-time trend information shall be integrated into a single trend within a trend
window, with seamless movement between the two. In the event that the screen is scrolled to the
left, then historical values will be recalled from historical data files. Scrolling the trend far enough
to the right will result in current real-time data being displayed as it is collected.
Zoom in/out and moving forwards and backwards in time shall be possible with no more than two
operator actions. A mechanism for selecting a location on the trend, such as a hairline cursor and
reading the digital values of the trends at that point in time shall be provided.
Comprehensive analysis capabilities shall be included. Each trend of a graph may have different
time references, and may be moved vertically, amplified, or compressed. In addition, an individual
trend can be shifted in time to compare to trends at other points in time. It shall be possible to
compare a single tag at two different time intervals on the same trend.
Viewing the correct historical data for a control tag should be easily accomplished from the
operator interface. A button on each tag faceplate shall call up historical data for that tag.
Continuous and event data shall be able to be combined into a single view. Only the appropriate
events for the trends displayed in the trend shall be shown. For example, if the PV of a loop is

35
APRIL, 2007 NIOEC-SP-70-08 (2)
being trended, all events about the loop shall also be displayed. This shall include any of the events
listed in Diagnostics, Alarm and Events such as operator changes to loop SP or tuning changes to
gain or loop alarms.
Each loop controller shall have a trending display for tuning. This tuning display shall show the
loop controller tuning values and include the capability to change the loop controller tuning values
while trending. Different colours shall be used for each parameter trended. The minimum controller
parameters trended shall be:

• Setpoint
• Process variable
• Controller output signal
Trending intervals shall be user selectable between 0.25 seconds to 5 seconds. The overall trend
display must show as a minimum between 1 minute and 20 minutes of trending per following table:

Sample Interval Minimum Duration of Screen Trend

0.25 seconds (4 times per second) 1 minute


0.5 seconds (2 limes per second) 2 minutes

1 second (1 time per second)


4 minutes

2 seconds (0.5 times per second) 8 minutes

5 seconds (0.2 times per second) 20 minutes

9.15 Reports
A reporting utility shall be provided. It shall be possible to use any variable in the system or the
history files in a report. It shall be possible for all reports to be displayed on a station screen as well
as printed on a report printer. Hourly, daily, monthly, end-of-month, quarterly and yearly reports
shall be supported. Reports shall be printed and/or saved to disk when a process event occurs. It
shall be possible to activate a report in the following manner:
• Upon demand (operator request)
• Scheduled (shift, daily and monthly)
• Upon event occurrence
It shall be possible to transfer data via standard off-the-shelf software tools to generic report writers.

9.16 Availability
A single failure anywhere in the segment shall not result in the loss of regulatory control to more
control loops than those associated with a single process input/output/H1 card. Failure of any single
device shall not affect the ability of the system to communicate with other devices in the system.
Switchover shall not disrupt any system functions.
Redundant equipment and software shall be continuously monitored for errors. All modules shall be
diagnosed on-line. Errors shall be alarmed with an error message identifying the failed module.

36
APRIL, 2007 NIOEC-SP-70-08 (2)

9.17 External Interface

9.17.1 Serial Interface - Subsystems


The following capabilities shall be available for communicating with subsystems:
• RS-232C, RS-422, and RS-485 with full and half-duplex operation, and at 19200, 38400,
57600, 115200 baud rates.
• IEEE 802.3 "Ethernet" protocol at 10 MBPS, with TCP/IP
• MODBUS is to be configured in a master-slave relationship, with the automation system as the
master and the auxiliary system as the slave.
• Serial interface shall mount into any available slot in the controller I/O rack. The controller shall
automatically sense the serial interface and present the applicable configuration options. There
shall be no need to set up any dipswitches.

9.17.2 OPC Interface


The automation system shall be able to communicate bi-directionally with auxiliary systems using
OPC. The OPC interface shall be configured in a client-server relationship with the automation
system as a client and the auxiliary system as the server.

9.18 Engineering Tools


This section specifies Software tools that shall be available to assist with the initial engineering and
long-term maintenance of the system. These tools do not need to be an integrated part of the system.
Capability shall be provided to configure all tag parameters and write high-level language programs
off-line on PC based computers. It shall be possible to download the configuration and program
files created on a PC to the automation system.
An interactive editor for building and maintaining a configuration database shall be provided. This
editor shall be capable of reading database files that are compatible with the following software
packages:
• Microsoft Access.
• Microsoft Excel.
• Microsoft SQL.
It shall be possible to exchange data with other third party software that are compatible with the
Microsoft Windows operating system.
The automation system shall be able to collect data from system’s data servers automatically and
enter it in a Microsoft Excel spreadsheet. The live data shall be dynamically linked into a particular
Excel cell and continue to update automatically based on changes in the operating process. Data
integrity of a particular piece of data shall be indicated through the use of a quality status indicator.

9.19 Embedded Advanced Control Tools


This section specifies embedded advanced control tools that shall be available to assist with process
optimization, increased performance, and reduced variability of process. These tools do not need to
be an integrated part of the system.

• The tools shall enable the automation system to perform the following:
• Optimize control and steady state objectives by continuously calculating the best move
sequence for each manipulated variable and on-line process performance monitoring of
continuous, batch, and semi-batch processes,
• Identifying under-performing loops and abnormal operating conditions with completely
automated process-monitoring software,

37
APRIL, 2007 NIOEC-SP-70-08 (2)
• Tuning PID and Fuzzy logic control blocks, as well as simulating process response to
recommended tuning parameters,
• Include Fuzzy logic control in the same engineering environment as the automation system’s
PID-based control,
• Solving small but difficult multivariable control problems, which have been handled with
complex PID-based control, with a model predictive control block,
• Simulating a controller in a single PC for control strategy development and testing.

The software shall provide the operators with accurate information about the process and
equipment's current performance as well as validated information relating to performance
economics such as cost of poor performance and inefficiency.
The software shall be able to provide model based, performance monitoring and optimization
designed to achieve optimal plant performance by continuously adjusting operating conditions in
reaction to changing process conditions.

9.20 Management Information System


The system shall be able to yield management information as may be required in a particular
project. Depending on the magnitude of the specific plant, the management information system may
be built-in within the system or it may be a third party system, to which the system shall be able to
feed the data.
The system shall include such data and reports as:
• Refinery material balance including Daily average, daily and monthly accumulation of feed and
product summary
• Chemical Consumption summary including shift report, daily averages and monthly
accumulation
• Lab. analysis report
• Refinery Utility balance including daily averages and monthly accumulation.

9.21 Maintenance Planning and Scheduling System


The system shall be able to fulfil the requirements as stipulated in Appendix I of this specification.

9.22 Plant Start Up and Shutdown Monitoring System


The system shall be able to fulfil the requirements as stipulated in Appendix II of this specification.

9.23 Automatic Start-up Sequence System


The system shall be able to perform automatic sequences of start-up or shut-down if required in a
specific project.
The PCS shall be able to perform automatic start-up and shutdown system for production processes,
so that start-up and shutdown sequences could be automated quickly, in spite of the demanding
operating conditions.
The system shall be able to reduce operators' workloads at the time of plant start-up and shutdown
and relieve the operators from making manual adjustments to the PCS, achieving:
• A drastic reduction of PCS manipulations,
• PCS monitoring time reduction,
• Lowering power consumption and heat steam energy as the result of stabilized operations and
minimized operation time,
• Elimination of problems caused by operator errors.

The system shall therefore fulfill the following objectives:

38
APRIL, 2007 NIOEC-SP-70-08 (2)
1) Easy-to-understand sequence programs could be created.
The sequence programs must be written in user friendly flow chart format. For easy visual
confirmation of the progress through each sequence, icons in the chart shall change color as specific
steps in the sequence are completed.
2) Operators could build an entire programming system by themselves.
No special skills shall be required to build a sequence program system. Operators should be able to
easily incorporate their operation know-how in the system. Operation know-how can be
standardized and shared among the operators.
3) The know-how of expert operator's could be handed on to less experienced operators.
4) Operator workloads shall be reduced.

9.24 Auto Tuner


As part of the standard control system architecture it shall be possible to automatically identify
process dynamics, employ one of various tuning algorithms, calculate new tuning parameters, and
update a controller with those new parameters.
The auto tuner shall be completely integrated into the control system and as such require no
communications interface configuration of any kind to connect with the PCS system.
The auto tuner shall employ an advanced means of identifying process dynamics such as relay
oscillation. Manual step testing shall not be required.
It shall be possible to implement any of the following tuning algorithms once process dynamics
have been identified:
• Ziegler-Nichols - PI
• Lambda - PI
• Lambda - Averaging Level
• Lambda - Smith predictor
• Internal Model Control – PID
It shall be possible to examine controller robustness using calculated tuning parameters graphically
through the use of a plot of gain margin vs. phase margin.
It shall be possible to select the proper tuning algorithm for a given application based on a simple
text description of the process and the user’s desired response.
It shall be possible to use the auto tuner to automatically configure and implement a fuzzy logic
controller based on the same identification techniques and tools used for the PID algorithm.

9.25 Special Requirements


Provision of the following non-mandatory requirements by the vendors is preferred by the
Purchaser and as such, any vendor fulfilling the requirements will place his proposal in a more
advantageous position in Purchaser’s evaluation of his proposal.

9.25.1 Multi-variable Constrained Model Predictive Control (MPC)


It shall be possible to implement multi-variable control strategies, within the confines of the control
system engineering environment, which are based upon algorithms that use an explicit process
model to compute a manipulated variable profile that will optimize control over a future time
interval.
This model predictive control algorithm shall be able to penalize and act upon predicted future
errors while simultaneously respecting multiple constraint and disturbance variables.
The system shall use of standard control system applications to fully identify a multi-variable
process, construct a process model, verify the model, generate a controller, simulate the controller
and commission the controller.
It shall be possible to implement such MPC control strategies without the need for external
communications interfaces, watchdog timers, network connections, or data mapping between the
control system layer and a supervisory control layer.

39
APRIL, 2007 NIOEC-SP-70-08 (2)
The MPC algorithm shall be executed in smaller applications (4 manipulated variables or less) as
fast as once per second. The MPC algorithm shall execute in an optionally redundant control system
processor as opposed to a station for purposes of availability.
The MPC algorithm shall be capable of maximizing or minimizing a selected process input until
one manipulated variable approaches its limit.
It shall be possible to construct the process model without the requirement to interface to an
external process historian.

9.25.2 Virtual Sensors and Quality Estimation


It shall be possible, within the confines of the control system engineering environment, to create
mathematical models using neural network or similar technology for the purpose of monitoring and
predicting process parameters in real-time that are difficult or impossible to measure directly.
This virtual sensor model shall be capable of performing the following:
• Accepting at least 16 input parameters to be correlated with sample or analyzer values to
produce a single output.
• Updating at least as fast as once per second.
• Executing in an optionally redundant control system processor as opposed to a station for
purposes of availability.
• Executing in an optionally redundant control system processor as opposed to a station for
purposes of availability.
It shall be possible to construct the virtual sensor model without the requirement to interface to an
external process historian, and to implement such virtual sensors without the need for external
communications interfaces, watchdog timers, network connections, or data mapping between the
control system layer and a supervisory computing layer.

9.25.3 Control Simulation


The system shall copy logic and control algorithms running in the control system processor and
execute that copy in a standard Windows PC for the purposes of testing, de-bugging, and operator
training.
It shall be possible to construct, execute, test, de-bug, control and logic on a standard Windows PC
and later move that configuration to the actual on-line control system without need to re-configure.
The system shall be able to alter the speed of control execution (faster or slower than real-time)
when executing the simulated control on a PC to
It shall be possible to connect the simulated control (via OPC) to a dynamic process simulation
application for control studies and operator training.
The system shall also be able to construct entire simulation systems (including full engineering and
operator interface capability on multiple stations) and simulate all control/logic, without the
requirement for control system hardware and I/O.

10. NAMEPLATES
Each cabinet, module, station, peripheral included in Vendor’s scope of supply shall have
its individual nameplate as follows:
• Nameplates shall be plastic type with a glossy black laminated surface and opaque white base
• Nameplates for outdoor equipment shall be stainless steel
• Nameplates shall be securely fixed at both ends with stainless steel screws
• Nameplate size, characters and character format shall be submitted for Purchaser’s review and
approval
• English lettering shall be used

40
APRIL, 2007 NIOEC-SP-70-08 (2)
Vendor’s mark and nameplate shall also be required for each station, cabinet and rack containing
manufacturer’s name, manufacturing date and production number. Material and format shall be the
same as other nameplates discussed above.
Each station and cabinet shall have both front and rear side nameplates.

11. PAINTING AND RUST PREVENTION


11.1 Paint Specification
The VENDOR shall paint each item in accordance with the paint specification agreed with the
PURCHASER prior to hardware manufacturing commencing.

11.2 Paint Colour


The paint colour shall be approved by the PURCHASER at the commencement of manufacture.

11.3 Special Requirements


If the Vendor’s paint specification and colours are not acceptable to the PURCHASER then the
PURCHASER will advise the VENDOR of the required paint specification and colours.

11.4 Surface Treatment


Surfaces to be painted shall be dry and free from burrs, weld spatter, flux dirt, dust, oil and any other
foreign matter before any paint is applied.
All parts of the equipment shall be rust proofed adequately.

12. DOCUMENTATION
12.1 General
The documentation to be supplied with the equipment shall be sufficient to operate, maintain, repair
and re configure the hardware and software throughout the operational lifetime of the system.
Document types are specified in Appendix III; Vendor Documents Schedule (VDS).

12.2 Design Documents


The VENDOR shall produce a Functional Design Specification as his first activity prior to any
construction commencing unless agreed by the PURCHASER. The Functional Design Specification
shall detail fully the equipment offered, hardware details, and software configuration and programs
and test procedures and shall be approved by the PURCHASER.
The VENDOR shall produce unique drawings and documents for those items on the VDS, which
are identified as for PURCHASER approval. The VENDOR may submit standard drawings and
documents for other category items on the VDS.

12.3 On line Documentation


It is recommended that a copy of vendor documentation related to the system maintenance and
configuration reside within the engineering station.

13. INSPECTIONS AND TESTING


13.1 General
The system shall be fully tested and inspected at Vendor’s shop to ensure satisfactory operation
before packing and shipping. A schedule for inspection and testing shall be detailed in the
manufacturing quality Plan. The Purchaser’s inspectors will witness the tests.

41
APRIL, 2007 NIOEC-SP-70-08 (2)
13.2 Factory Acceptance Test (FAT)
a) General
The VENDOR shall submit test procedures for Purchaser’s approval prior to the FAT.
The VENDOR shall satisfactorily test the Equipment prior to the Factory Acceptance Tests, and
submit test procedures to Purchaser prior to the FAT.
The VENDOR shall notify the PURCHASER a minimum of 30 days in advance of his intention to
carry out tests so that arrangements can be made to witness the event.
For FAT, the VENDOR shall make available time, space and assistance to ensure the
PURCHASER is given all possible assistance.
VENDOR shall provide all goods, materials and services for all the tests and shall provide all test
equipment required to test out the equipment and to simulate all field inputs, outputs and serial links
and monitor all output operations.
FAT shall be as complete as practicable with all interfacing equipment available from other
systems, and shall be a detailed function test covering all stages of the equipment's operation.
b) Unit Tests
All controls shall be checked during the test for correct operations and a full functional test shall be
carried out to confirm compliance with the specification.
All faults discovered shall be rectified at the Vendor’s cost and the affected system offered for re-
test.
The tests shall comprise the following tests as a minimum:
• Visual, mechanical and electrical inspection of all equipment for conformance to drawing and
specification.
• Hardware testing e.g. ADC calibration, switching, and automatic redundancy checks etc.
• Power supply testing for load and switching.
• RFI and EMI tests.
• Database checking.
• Functional loop checks for 100% of the controllers, I/O modules and field termination
assemblies. The system final database shall be used for these tests.
• CPU and memory maximum loading capacity checks.
• Factory as-built documentation shall also be checked.
c) System Software Tests
The PCS software tests shall comprise the following tests as a minimum:
• Functional tests of the operating system, i.e. setpoint, control changes.
• Configuration tests of the standard system i.e. alarm limit changes etc.
• Functional tests of all utility programs.
• Functional tests of all VENDORS supplied application software.
• Functional tests of communication with all third party equipment.
d) Performance Tests
The performance tests shall comprise the following tests as a minimum.
System response tests to confirm that the performance requirements of specification are met, i.e.,
display call up times, scanning times, alarm handling and process load.
System integration tests to confirm all functions are operational and dependency between functions
is present.

13.3 Test Completion


On completion of satisfactory PURCHASER witnessed factory acceptance tests the VENDOR shall
collate all test results for signature and approval and issue the necessary certificates.

42
NIOEC-SP-70-08 (2)
APRIL, 2007

14. INSTALLATION, START UP AND COMMISSIONING


14.1 Installation
Purchaser will install the equipment at site under the supervision of VENDOR specialists.

14.2 Checks
VENDOR specialists shall be responsible to check that the following minimum requirements have
been fulfilled:
• Correct installation of cabinets and stations.
• Replacement of equipment in cabinets and station removed for transportation.
• Connection and installation of all system cables and internal cable connections.
• Connection of all power and earthing cables and resistance checks.

14.3 Power up
Vendor specialists shall power up the system and check that following requirements have been
completed:
All Vendors standard hardware, software and diagnostics checks have been completed, including all
processor failure mode, redundancy, security access and restart procedures.
Communication checks have run with data transmission corruption being acceptable within the
Vendor’s published specification.

14.4 SAT
The VENDOR shall submit SAT Test Procedures for Purchaser’s approval prior to the Test. Vendor
specialists shall then perform Site Acceptance Test (SAT) for Purchaser’s approval. Full functional
test shall be carried out at this stage.
The VENDOR shall specify the need for any special test equipment and site support
required for installation and commissioning.

14.5 Commissioning
Vendor may be required to provide a site-based specialist to assist the Purchaser with the following
activities during commissioning:
• Operator guidance.
• Loop tuning.
• Control loop configuration amendments.
• Resolve system faults.
• Vendor shall confirm in his quotation, his commitments to render the above-mentioned.

14.6 Test Equipment


The VENDOR shall specify the need for any special test equipment and site support
required for installation and commissioning.

14.7 Documents
The VENDOR shall provide agreed as-built documents and drawings following site
commissioning.

43
APRIL, 2007 NIOEC-SP-70-08 (2)
15. SPARES PARTS SUPPLY
15.1 Construction, Pre-commissioning and Commissioning Spare Parts
VENDOR shall recommend the spares for construction, pre-commissioning,
commissioning and construction allowance, which will be purchased together with the
equipment, and include the cost of spares in the quotation.

15.2 Spare Parts for Two Years of Operation


VENDOR shall recommend the spares required for 2 years of operation and provide a
price list.
PURCHASER may purchase the spares listed in Vendor’s recommended spare part list
after review. Validity of spare parts proposal shall be 12 months.

15.3 Maintenance Tools


If the supplied equipment requires special maintenance tools, the VENDOR shall include
in his proposal a price list for one complete set of such special tools. PURCHASER may
purchase the tools in a similar manner to spares as indicated in Section 15.2.

16. TRAINING
VENDORS shall be required to provide training as follows:
• Training of Operators to overtake System operation
• Training of Technicians to perform System maintenance work
• Training of Engineers to be in charge of System configuration (hardware and
software) and advanced system maintenance work
Operators will normally be trained at site while the Technicians and Engineers are to be
dispatched to Vendor’s works to receive their respective training.

17. GUARANTEES
Vendors shall guarantee that he is able to support and supply spare parts for the supplied
hardware, software and firmware for at least 10 years from the date of shipment.
Completion of commissioning does not end Vendor's involvement: Vendor shall be able to provide
support either by telephone or site attendance, and where appropriate, modems shall be provided,
with client authorization, to permit remote connection to the equipment or the operator interface to
diagnose problems and make adjustments.
Vendor shall be in a position to offer system maintenance contract services to:

• Debug and trouble-shoot the software.


• Install software upgrades.
• Periodically back-up the database and graphics screens.
• Check and clean the hardware.
• Make adjustments identified by the operations staff to further optimize the system.
• Provide advice and assistance.

44
APRIL, 2007 NIOEC-SP-70-08 (2)
If the VENDOR believes that parts of the system will be withdrawn from sale after 10
years, he shall provide a statement detailing the equipment to be withdrawn, the timing
and how updated parts can replace the withdrawn parts.
The Vendor shall also guarantee that the equipment supplied is free from fault in design,
workmanship and material, and is of adequate design and proper material to fulfil
satisfactorily the specified operating conditions.
Should any failure or defect in design, material, workmanship or operating
characteristics develop under the start-up and commissioning periods or during the first
12 months of operation, but not later than 24 months from the date of shipment, the
Vendor shall make all required repairs, alterations or replacements of the defective
equipment, free of charge, and shall pay transportation fees involved to and from
NIOEC’s site.

45
APRIL, 2007 NIOEC-SP-70-08 (2)

APPENDIX I
MAINTENANCE PLANNING AND SCHEDULING SYSTEM
1. GENERAL

This specification defines the minimum functional requirements for the Maintenance Planning and
Scheduling System, which shall, according to the requirements of the project specifications and the
size of the PCS and the maintenance data, be carried out within the PCS or shall be carried out
within a third party package, acquiring its data from the PCS database.

2. BASIC FUNCTIONS

The Maintenance Planning and Scheduling System shall provide the means to manage maintenance
history and maintenance schedule of the main rotary machinery.
The system shall use a database of the items of the rotary machinery to store the related
maintenance data including run/stop status, which will be input from the PCS and maintenance date,
past maintenance reports/notes and that shall be entered by the maintenance personnel in every
maintenance cycle.
Upon request of the maintenance personnel, the system shall display and report maintenance history
of the required items or forecast their next maintenance dates based on the said data base. However
when the system detects any equipment whose maintenance date has expired, the system shall
automatically send a message to the plant operator of the relevant unit via PCS console to notify
him of maintenance requirement of the equipment.

The system shall mainly have four display functions as follows:


2.1 MAINTENANCE RECORDS UPDATE FUNCTION
Maintenance records of the recent maintenance work for each equipment shall be added or edited
through this display. The records shall consist of the maintenance date, type and the comments for
each maintenance job.
2.2 MAINTENANCE FORECASTING FUNCTION
This display shall enable the maintenance personnel to specify the items whose next expected
maintenance date is to be forecasted.
Based on the planned maintenance interval the expected maintenance date for each item shall be
automatically calculated. The next maintenance date can also be modified by the personnel if
required.

46
APRIL, 2007 NIOEC-SP-70-08 (2)

2.3 MAINTENANCE HISTORY DISPLAY FUNCTION


Through this display the personnel shall be able to specify the items whose maintenance records in
the past are to be shown on the display.
2.4 EQUIPMENT IDENTIFICATION DATA UPDATE FUNCTION
This display shall enable the maintenance personnel to edit, add or delete the equipment
identification data for each equipment.
Passwords shall be incorporated so that only the authorized persons shall be allowed to change the
equipment identification data.

3. DATA STRUCTURE
3.1 Data Type
Following data shall be held in the system:
• Equipment Identification Data
• Maintenance Scheduling and Forecasting Data
• Maintenance Records
The system shall store, update and delete these date in accordance with the requirements of the
maintenance personnel
3.1.1 Equipment Identification data
This data shall consist of a unique Item number for each equipment and the following subsidiary
data:
• Unit Name
• Item Number
• Service
• Equipment Type
• Equipment Driver
• Rated Power
• Installation Date

• On-line Signal Tag Name


• Run/Stop Status
• On-Line Signal Availability
• Run/Stop Status Auto Update

47
APRIL, 2007 NIOEC-SP-70-08 (2)
3.1.2 Maintenance Scheduling and Forecasting Data
This data shall be provided as follows:
• Maintenance Cycle.
• Last Maintenance Date.
• Expected Maintenance Date based on Maintenance Cycle.
• Scheduled Maintenance Date specified by maintenance personnel.
• Running Time calculated by the system.
• Number of Days until the Next Maintenance Date from the Current date.
3.1.3 Maintenance Records (Last 30 Records)
The last 30 records of maintenance shall constitute the maintenance records and include the
following:
• Maintenance Date
• Maintenance Type
• Comments for each maintenance work
3.2 Configuration of Data word
The following data word configuration shall be foreseen:
3.2.1 Equipment Identification Data
Data Number of Characters
UNIT NAME 4
ITEM NUMBER 8
SERVICE 20
EQUIPMENT TYPE 5
EQUIPMENT DRIVER 8
RATED POWER FLOATING
INSTALLATION DATE DATE
ON LINE SUGNAL TAG NAME 8
RUN STOP STATUS 4
ON LINE SIGNAL AVAILABILITY 4
RUN/STOP STATUS AUTO UPDATE 4

3.2.2 Maintenance Scheduling and Forecasting Data

Data Number of Characters

Maintenance Cycle(Day) 4

48
APRIL, 2007 NIOEC-SP-70-08 (2)
Last Maintenance Date Date

Expected Maintenance Date Date

Scheduled Maintenance Date Date

Running Time (Day) 4

3.2.3 Maintenance Records Data


Data Number of Characters
Maintenance Date Date type Data
Comments on each maintenance 250
Work

4. DETAILS OF THE FUNCTIONS


Maintenance personnel shall be able to interface with the Maintenance Planning and Scheduling
System through a dedicated console. There shall be a menu tree to enable the personnel to enter the
system functions. When the system started, it shall prompt the personnel with a message to enter the
main password. Upon entering the correct password, the main menu screen, shall be displayed for
the selection of the functions. Incorrect entry of the password shall prompt a message to enter the
password again. However after three consecutive incorrect entries the system shall revert to the last
display. It is to be noted that as explained in section 2.4 above, when the Maintenance personnel
selects the Equipment Data Update function at the main menu, the system shall ask for another
password before starting the required function. Incorrect entry of this password shall be dealt with
in a similar manner to that of the main password.

4.1Maintenance Record Edit/Append Function

4.1.1 Data Displayed


The following data shall be displayed for this function:
• Unit Name
• Item Number
• Service
• Equipment Type

49
APRIL, 2007 NIOEC-SP-70-08 (2)
• Equipment Driver
• Rated Power
• Installation Date
• Last Maintenance Date
• Running Time
• Maintenance Date
• Comments for each maintenance work

4.1.2 Functional Requirements


Upon selection of either Edit or Append functions on a dedicated menu, the maintenance personnel
shall be prompted to enter Item number. If the Item number is found, the system shall fill in the
data, as indicated in para. 4.1.1, except for Maintenance date. The system shall prompt the
personnel to enter the Maintenance date. The system shall then display the following display
operation:

4.1.2.1 Edit Function


If a record of the specified Maintenance date is not found among the stored data, the system shall
then display a seek failure message and prompt the personnel to enter the date again.
If the specified record is found, the system shall then display the data to allow the personnel to edit
the existing Comments.
Upon selection of the End key the system shall require the confirmation of the personnel to update
and store the edited data in the database and then shall return to the beginning of this function.
4.1.2.2 Append Function
The specified Maintenance date shall be checked in the following manner and new data shall be
appended as follows:
a) New Maintenance date earlier than or Equal to Last Maintenance date.
Consequence:
• Invalid entry, warning message
b) New Maintenance Date Later than Current date.
Consequence:
• Invalid input date, warning message

c) New Maintenance date earlier than or Equal to Current date But Later than Last Maintenance
date.
Consequences:
• Last Maintenance date—> New Maintenance date

50
APRIL, 2007 NIOEC-SP-70-08 (2)
• Running time—> Initialized
• Personnel can enter the new Comments

4.2 Maintenance Forecasting/Scheduling Function


4.2.1The following data shall be displayed in this function:
• Unit Name
• Item Number
• Service
• Running Time
• Next Maintenance Date
• Number of Days Until the next Maintenance date

• Last Maintenance Date


• Expected Maintenance Date
• Scheduled Maintenance Date
• Run/Stop Status
• On-Line Signal Availability
• Run/Stop Status Auto Update
Next Maintenance date shall be initially set to the Expected Maintenance date. When Scheduled
maintenance date is specified. Next Maintenance date shall be set to Scheduled Maintenance date.

4.2.2 The Menu


A dedicated menu shall be made available for this function, which shall be used for Maintenance
date forecasting. Scheduled Maintenance date and Run/Stop status and Run/Stop status auto update
shall be changed through this menu.
4.2.3 Calculation of Maintenance date
Upon selection of Maintenance Forecasting function, the system shall calculate Expected
Maintenance date of the required equipment as follows:

Expected Maintenance Date =

(Current Date+ Maintenance Cycle)- (Running Time from Last Maintenance Date)

Running Time shall be calculated once per hour for all the items according to the Run/Stop Status.
For items with dedicated on line On/Off signals, it shall be possible to specify whether Run/Stop
Status shall be automatically updated in accordance with the on-line On/Off signal, by setting
Run/Stop Status auto update flag to Yes or No.

51
APRIL, 2007 NIOEC-SP-70-08 (2)
4.2.4 Functional Requirements
The display shall provide the facility to retrieve maintenance forecasting information and/or
Scheduled Maintenance date.
4.2.4.1 Items subject to Maintenance within specified period:
When this mode is selected, the system shall display the items to undergo maintenance within the
period specified by the personnel on the screen. Items with expired Maintenance date shall also be
displayed.
4.2.4.2 Items with expired Maintenance date:
When this mode is selected, the system shall display the list of the items with expired Maintenance
date.
4.2.4.3 All items of the selected unit
Upon selection of this mode, the system shall ask for Unit name. Then the system shall display the
Maintenance forecasting item list for all items in the specified unit.
4.2.4.4 Scheduled maintenance date input and update the system shall, upon selection of this mode,
ask the personnel to input Unit name. Then the system shall display the list of all the items of the
specified unit and allow the personnel to specify the Scheduled maintenance date. The Scheduled
maintenance date specified in this display shall be used as the Next maintenance date instead of
Expected maintenance date.
After selecting the End key the system shall require confirmation of the personnel whether to store
the specified Scheduled maintenance date.
4.2.4.5 Run/Stop status input the system shall, upon selection of this mode, prompt the personnel to
input the Unit name.
The system shall then display the list of the all items in the unit and allow the personnel to specify
the Run/Stop status and Run/Stop status auto update.
If Run/Stop status auto update is set to "Yes" for any equipment whose on-line signal availability is
"Yes", then the Run/Stop status shall be determined by on-line On/Off signal and the manual input
of the status shall be ignored. After selecting the End key the system shall require confirmation of
the personnel whether to store the specified maintenance date.
4.2.4.6 Print out
Through the display, the personnel shall be able to request the system to print more detailed
information on printers.
All the information and data in the system shall be printable through individual/group listing.
4.3 Maintenance History Display Function
4.3.1 Data Displayed
The following data shall be displayed for this function:

52
APRIL, 2007 NIOEC-SP-70-08 (2)
• Unit Name
• Item Number
• Service
• Equipment Type
• Equipment Driver
• Rated Power
• Installation Date

• Maintenance Date
• Comments for each maintenance work
4.3.2 Functional Requirements
Through a dedicated display, maintenance personnel shall be able to inspect the previous
maintenance records.
After the personnel selects, on the display, how many of the latest records are to be displayed and
enters the Item number at the prompt, all the pertaining data as listed in paragraph 4.3.1 shall be
displayed.
4.4 Equipment Identification Data Update function
4.4.1 Data Displayed
The following data shall be displayed for this function:
• Unit Name
• Item Number
• Service
• Equipment Type
• Equipment Driver
• Rated Power
• Installation Date
• Maintenance Cycle
• Run/Stop Status
• Maintenance Date
• On-line Signal Availability
• On-line Signal Tag Name

4.4.2 Menu Format


There shall be three modes in this function, i.e. Edit, Append and Delete mode.

53
APRIL, 2007 NIOEC-SP-70-08 (2)
4.4.3 Functional Requirements
4.4.3.1 Edit Mode
Upon entering Item number for any equipment, the system shall display all related information. The
displayed data, except for Item number, can then be modified by the personnel on the screen.
After selecting the End key the system shall require confirmation of the personnel whether to store
the specified date. If confirmed, the system shall overwrite the data, otherwise the system shall
return to the Menu.
4.4.3.2 Append Mode
In this mode a display shall be used so that the personnel can add a new equipment identification
data.
After selecting the End key the system shall require confirmation of the personnel whether to store
the specified date. If confirmed, the system shall store the data. Otherwise the system shall return to
the Menu.
A warning message shall be initiated if the specified Item number already exists in the stored data
and shall not store the specified data.
Adequate data file spare capacity shall be foreseen for the Append function.
4.4.3.3 Delete Mode
When the Item number is entered at the prompt, the system shall fill in the rest of the data.. Then
the system shall prompt the personnel to decide whether the system should delete the specified data.

4.5 System Messages


4.5.1 Normal Operation Messages
This message shall be initiated by the system when the maintenance data file has been added,
updated or deleted to indicate that the system has carried out the required operations normally.
4.5.2 Error Messages
The system shall issue this message whenever an incorrect datum is entered by maintenance
personnel.
4.5.3 Message to Plant Operators
When the system detects any equipment whose maintenance date has expired in the course of
maintenance date calculation, the system shall automatically send a message to the plant operator of
the relevant unit via PCS console to notify him of maintenance requirement of the equipment.

54
APRIL, 2007 NIOEC-SP-70-08 (2)

APPENDIX II
PLANT START UP AND SHUTDOWN MONITORING SYSTEM
1. GENERAL

This specification defines the minimum functional requirements for the Plant Start Up and Shut Down
Monitoring System.

2. BASIC FUNCTION

The Plant Start Up and Shut Down Monitoring System provides the means to overview the plant
operational status through graphic displays showing simplified process flow diagrams and indicating
Run/Stop or On/Off status of main equipment. The displays shall be available in PCS consoles of
each control room for the relevant process units. These displays can, if so requested, be available as
a whole in the centralized console(s) located in the Management Information centre.
3. MONITORING DISPLAYS

Operational status of the equipment shall be indicated by colour coding the equipment symbols on
the graphic displays. The system is intended to monitor the status of the main process pumps, main
compressors and fired heaters. Each equipment service shall be provided with Run/Stop indication
and Auto/Manual mode selection. When on Auto mode, the system shall use on line signals to
indicate Run/Stop status. When on Manual mode the status shall be indicated in accordance with the
Run/Stop status entered by Operators.
Equipment with no on-line signals to PCS shall only use the Manual mode.

The Auto/Manual modes shall be selected via PCS displays.

4. Colour Coding
The proposed colour coding for the displays shall be as follows:
• Equipment symbols
Run or On: Blue
Stop or Off: Red
• Equipment item number
Red : Manual mode
Blue : Auto mode
• Towers or Vessels

55
APRIL, 2007 NIOEC-SP-70-08 (2)
Green with yellow outline
• Process lines
Green
• Others
White
5. CRITERIA FOR STATUS INDICATION
The following criteria shall govern the indication of Run/Stop status.
5.1 Run/Stop status shall be indicated in accordance with online On/Off signal or on-line process
signal or manual input. The extent of the application of the status monitoring system and the actual
signal to be used will be defined in the project specifications.
5.2 Upon selection of Auto mode for the equipment services with on-line signals, the following rules
shall be applied for determination of Run/Stop status:

a) For the equipment services with on-line process signal, Run status shall be indicated when the
signal value is above the Start Limit. This limit shall be changeable for each signal. However, as a
default this limit shall be 5% of the instrument range of on-line process signal. In case multiple on-line
process signals are used for a equipment service, Run status shall be indicated when one of the process
signals exceeds the Start Limit. Stop status shall be indicated when all the signals fall below their
respective limit values.
In case of Bad process signals, i.e. "BAD PV", the system shall display an appropriate error message
on CRT and re-set to the Manual mode.
a) For the equipment services with on-line On/Off signals and multiple equipment items. Run
status shall be indicated when one or more of the on-line On/Off signals become "On".
b) For the equipment services with Manual mode input only, the system shall not permit to change
the mode to "Auto".
c) Manual entry of the operational status shall be carried out through PCS consoles.

6. LAYOUT OF THE SYSTEM MENU

The system shall have two types of displays:


• System Menu
• Monitoring Displays
All monitoring displays shall originate from the Menu display and return to the Menu upon request.

56
APRIL, 2007 NIOEC-SP-70-08 (2)

APPENDIX III
VENDOR’S DOCUMENT SUPPLY (VDC)
DOCUMEN
DOCUMENTS
DOCUMENTS AFTER TS AFTER
DESCRIPTION WITH
PURCHASE ORDER FINALISAT
QUOTATION
ION
QUANT
ITY
QUANTITY ISSUE AND QUANTITY
TYPE PURPOSE TYPE AND TYPE
1. GENERAL
1.3 CATALOGUES 4C
2. SHIPPING INFORMATION 4C FI 2C 2C+1R
2.1 NET & GROSS WEIGHTS 4C FI 2C 2C+1R
2.2 MEASUREMENTS 4C FI 2C 2C+1R
2.3 PACKING, KNOCKDOWN AND FI 2C 2C+1R
TRANSPORTATION PROCEDURES

3. SCHEDULES
3.1 DESIGN WORK SCHEDULE 4C FI 2C 2C+1R
3.2. MANUFACTURING SCHEDULE 4C FI 2C 2C+1R
3.3 DOCUMENT SUBMISSION SCHEDULE FI 2C 2C+1R
3.4 TEST AND INSPECTION SCHEDULE FI 2C 2C+1R
3.5 SHIPPING SCHEDULE FI 2C 2C+1R

4. REPORTING
4.1 STATUS REPORTS FI
4.2 TEST AND INSPECTION REPORTS FA 2C 2C+1R

5. SPARE PARTS AND SPECIAL


TOOLS
5.1 COMMISSIONING SPARE PARTS LIST 4C FI 2C 2C+1R
5.2 OPERATIONAL 2-YEARS SPARE LIST 4C FI 2C 2C+1R

6. INSTRUCTIONS AND MANUALS


6.1 TEST & INSPECTION PROCEDURE FA 2C 2C+1R
6.2 INSTALLATION INSTRUCTIONS FI 2C 2C+1R
6.3 OPERATION & MAINTENANCE FI 2C 2C+1R
INSTRUCTIONS
6.4 INSTRUCTIONS FOR STORAGE AT SITE FI 2C 2C+1R
6.5 SYSTEM FUNCTION MANUALS FI 2C 2C+1R
6.6 OPERATOR STATION MANUALS FI 2C 2C+1R
6.7 ENGINEERING STATION MANUALS
7. DRAWINGS AND DOCUMENTS

57
APRIL, 2007 NIOEC-SP-70-08 (2)
7.1 DRAWING & DOCUMENT LIST FA 2C 2C+1R
7.2 POWER CONSUMPTION LIST AND 4C FI 2C 2C+1R
HEAT DISSIPATION
7.3 POWER SUPPLY & DISTRIBUTION FA 2C 2C+1R
DRAWINGS
7.4 DIMENSIONAL DRAWINGS 4C FI 2C 2C+1R
7.5 SYSTEM CONFIGURATION 4C FA 2C 2C+1R
7.6 FOUNDATION DESIGN BASE AND 4C FA 2C 2C+1R
ANCHORING DETAILS
7.7 GROUNDING SYSTEM FA 2C 2C+1R
7.8 NAMEPLATE LIST FA 2C 2C+1R
7.9 PRELIMINARY SYSTEM PLOT 4C FA 2C 2C+1R
PLAN IN CONTROL ROOM &
EQUIPMENT ROOM
7.10 MTBF FIGURES 4C FA 2C 2C+1R
7.11 HARDWARE SPECIFICATION 4C FA 2C 2C+1R
7.12 INTERNAL & EXTERNAL LAYOUT 4C FA 2C 2C+1R
DRAWINGS
7.13 INTER WIRING DRAWINGS 4C FA 2C 2C+1R
7.14 TERMINAL ARRANGEMENT 4C FA 2C 2C+1R
DRAWINGS
7.15 WIRING CONNECTION LIST 4C FI 2C 2C+1R
7.16 INTERCONNECTION DRAWINGS 4C FI 2C 2C+1R
BETWEEN EQUIPMENT IN CONTROL
ROOM AND EQUIPMENT ROOM
7.17 I/O ASSIGNMENT LIST 4C FA 2C 2C+1R
7.18 DETAILED LOOP DRAWINGS 4C FA 2C 2C+1R
INCLUDING FIELD INSTRUMENTS
(TRANSMITTERS, CONTROL VALVES, ETC.)
7.19 GRAPHIC DISPLAYS DIAGRAMS 4C FA 2C 2C+1R
7.20 INTERLOCK DIAGRAMS 4C FA 2C 2C+1R
7.21 SOFTWARE SPECIFICATION 4C FA 2C 2C+1R
INCLUDING APPLICATION SOFTWARE

ABBREVIATIONS:
C: COPIES
R: REPRODUCIBLE
FI: FOR PURCHASER’S INFORMATION
FA: FOR PURCHASER’S APPROVAL

58

Anda mungkin juga menyukai