National Oil Corporation: Rev Date Description Checked Approved

NATIONAL OIL CORPORATION
GENERAL ENGINEERING SPECIFICATION
GES J.21
PROGRAMMABLE LOGIC CONTROLLERS
Rev Date Description Checked Approved

0 1999 Issued for Implementation DL
Compiled by Teknica (UK) Ltd

GENERAL ENGINEERING SPECIFICATION GES J.21
PROGRAMMABLE LOGIC CONTROLLERS Page 2 of 35
Rev 0 1999
INDEX
SEC TITLE PAGE
1.0 SCOPE OF SPECIFICATION 4
1.1 Introduction 4
1.2 Other NOC Specifications 4
2.0 DEFINITIONS 5
2.1 Technical 5
2.2 List of Abbreviations 6
2.3 Contractual 6
3.0 DESIGN 7
3.1 Codes and Standards 7

3.2 Environmental Conditions 8
3.3 Noise Limits 8
3.4 Hazardous Area Classification 8
3.5 Electromagnetic Interference 9
3.6 Electrical Interference 9
3.7 System Availability 9
3.8 Guidelines for System Selection 9
3.9 Input/Output Modules 10
3.10 CPU and Memory 12
3.11 Power Supplies 14
3.12 Applications Software 15
3.13 Man Machine Interface 17
3.14 System Security 17
3.15 Systems Interfacing and Communications 18
3.16 Expansion and Sparage 19
3.17 Bid Format 20
4.0 MATERIALS 20
4.1 General 20
4.2 Printed Circuit Boards 21
5.0 MANUFACTURE 21
5.1 Cabinets and Enclosures 21

5.2 Earthing 22
5.3 Wiring and Terminations 22
5.4 Identification and Tagging 22
6.0 SITE PREPARATION AND INSTALLATION 22
6.1 Installation 22
Rev 0 1999
SEC TITLE PAG
7.0 INSPECTION 23
7.1 Procedures 23
7.2 Planning 23
7.3 Progress Monitoring 23
7.4 Quality Assurance 24
7.5 Software 24
7.6 Visual Inspection 25
8.0 TESTING 25
8.1 Test Procedures 25

8.2 Factory Acceptance Testing 26
8.3 Site Acceptance Testing 29
9.0 DOCUMENTATION 29
9.1 Introduction 29
9.2 Schedules and Reports 30
9.3 Data and Calculations 31
9.4 Drawings 31
9.5 Final Records, Documents and Manuals 31
9.6 Hazardous Area Certificates 32
10.0 PRIOR TO SHIPMENT 33
10.1 Paintings and Coatings 33

10.2 Spares 33
10.3 Packing and Storage 33
10.4 Shipping 34
10.5 Service Support 34
10.6 Warranty 34
DATA SHEETS (2)

Rev 0 1999
1.0 SCOPE OF SPECIFICATION
1.1 Introduction
1.1.1 This specification covers the minimum requirements for design, manufacture, inspection, testing,
installation and documentation of Programmable Logic Controller (PLC) based systems for non-safety,
control applications. Typical applications envisaged are pump control, valve control, motor
loading/unloading, process package control, etc. This specification does not address the specific
requirements for the use of PLC's for such safety critical applications such as Emergency Shutdown, Fire
and Gas systems and the burner management systems.
1.1.2 This specification applies to equipment for refineries, onshore oil and gas installations, and processing
facilities, including items purchased either directly or as a part of a package. The PLC may be a stand
alone controller or part of a network.
1.1.3 The Vendor/Contractor shall comply fully with the provisions laid down in this specification. Any
exception must be authorised in writing by the Owner.
In the event of any conflict between this specification or with any of the applicable codes and standards, the
Vendor/Contractor shall inform the Owner in writing and receive written clarification before proceeding
with the work.
1.1.4 This General Engineering Specification will form part of the Purchase Order/Contract.
1.2 Other NOC Specifications
The following additional NOC Specifications are an integral part of this specification and any exceptions
shall be approved in advance by the Owner.
GES A.06 Site Data
GES B.01 Central Control Buildings
GES C.54 Commissioning of Micropressor Based Instrument Systems
GES J.12 Indoor Control Panels and Cabinets
GES J.16 Instrument Cable and Cabling
GES J.17 Earthing of Instrument Systems
GES J.19 Annunciators
GES L.07 A.C. Uninterruptable Power Supplies (UPS)
GES L.35 Electrical Equipment in Hazardous Areas
GES X.06 Factory Coatings for Electrical Equipment and Instruments

Rev 0 1999
2.0 DEFINITIONS
2.1 Technical
The technical terms used in this specification are defined as follows:
Disable
To disconnect a logic coil or a discrete input or an output from its normal control and force an input or an
output to the `off' state.
Enable
To re-establish normal control of a disabled logic coil or discrete output.
I/O (Input/Output)
PLC system inputs or outputs connected to field elements.
Ladder Diagram
Diagram that expresses the user-programmed logic in the conventional relay format symbology.
Logic Element
Normally Open (NO) on Normally Closed (NC) contact, timer, counter, coil etc. in a ladder logic diagram.
Local I/O
Any input or output module which is directly connected to the CPU ( See also Remote I/O).
Programmable Logic Controllers
Programmable logic controllers are microprocessor based solid state systems which are programmed to
operate in a particular manner in response to external inputs. PLC's can be used in place of relay systems
or for proportional, integral, and derivative (P&ID) control in specific applications.
Programming Unit
A programming unit is a dedicated device that allows an interface to the PLC for development, start-up and
trouble shouting.
Remote I/O
Any input or output which is linked to the CPU via a multiplexer or a serial link and located some distance
from the CPU.
Programme Scan Time
The time taken for the PLC to execute a series of programme instructions is called a programme. Note that
this is the definition of programme scan time which is different from the complete scan time. The latter
includes scanning inputs and outputs, updating I/O tables, diagnostics as well scanning serial I/O's.
Rev 0 1999
2.2 List of Abbreviations
CCR Central Control Room

CPU Central Processing Unit
DCS Distributed Control System
EMI Electro Magnetic Interference
FAT Factory Acceptance Testing
HVAC Heating Ventilation and Air Conditioning
I/O Input/Output
LED Light Emitting Diode
MTBF Mean Time Between Failures
MTTR Mean Time to Repair
PCB Printed Circuit Board
P&ID Process and Instrument Diagram
PID Proportional, Integral, Derivative
PLC Programmable Logic Controller
QA/QC Quality Assurance/Quality Control
SAT Site Acceptance Testing
SCADA Supervisory Control and Data Acquisition
UPS Uninterruptable Power Supply
VDU Visual Display Unit
2.3 Contractual
The commercial terms used in this specification are defined as follows:
Owner
The oil and gas company, an associate or subsidiary, who is the end user of the equipment and facilities.
Vendor
The company supplying the equipment and material.
Contractor
The main Contractor for a defined piece of work.
Sub-Contractor
A company awarded a contract by a contractor to do part of the work awarded to the Contractor.
Inspection Authority
The organisation representing the Owner or Vendor/Contractor that verifies that the equipment and
facilities have been designed, constructed, inspected and tested in accordance with the requirements of this
specification and the Purchase Order/Contract.
Inspector
A qualified individual representing the Owner, Vendor/Contractor or the assigned Inspection Authority,
who verifies that the equipment and facilities have been designed, constructed, inspected and tested in
accordance with this requirements of this specification and the Purchase Order/Contract.
3.0 DESIGN
Rev 0 1999
PLC system design shall conform to, be engineered, tested and installed in accordance with the following
code and standards.
3.1 Codes and Standards
American Petroleum Institution (API)
API 554 Process Instrumentation of Control
British Standards Institution (BSI)
BS 5345 Parts 1-8 Code of Practice for Selection, Installation and Maintenance of Electrical
Apparatus in Explosive Atmospheres
BS 5515 Code of Practice for Documentation of Computer Based Systems
BS EN 61000 Part 4.1 Electromagnetic Compatibility for (EMC) - Testing and Measurement
Techniques - Overview of Immunity Tests - Basis EMC Publication
BS 5760 Reliability of Systems, Equipment and Components
Part 2 - Guide to Assessment of Reliability

Part 3 - Reliability of Constructed or Manufactured Products, Systems,
Equipments and Components - Guide to Reliability Practices
Examples
Part 7 - Guide to Fault Tree Analysis
Part 8 - Guide to Assessment of Reliability of Systems Containing
Software
BS 7671 Requirements for Electrical Installations
Electronic Industries Association (EIA)/CCITT Recommendations.
V24/RS 232E Interface Between Data Terminal Equipment and Circuit Terminating
Equipment Employing Serial Binary Data Interchange
RS 422 Electrical Characteristics of Balanced Voltage Digital Interface Circuits
V28/RS 485 Electrical Characteristics for Generators and Receivers for use in Balanced
Digital Multipoint Systems
International Electrotechnical Commission (IEC)
IEC 60068 Part 1 Environmental Testing - General and Guidance
IEC 60529 Degrees of Protection Provided by Enclosures (IP Code)
IEC 60617 Part 12 - Graphical Symbols for Diagrams - Binary Logic Elements
IEC 61000 Part 4.3 - Electromagnetic Compatibility (EMC) - Testing and Measurement
Techniques - Field Immunity Test- Radiated, Radio Frequency and
Electromagnetic
IEC 61131 Part 1 Programmable Controllers - General Information
Instrument Society of America (ISA)
ISA S 5.1 Instrumentation Symbols and Identifications

Rev 0 1999
ISA S 5.2 Binary Logic Diagrams for Process Operations
ISA S 5.3 Graphics Symbols for Distributed Control/Shared Display Instrumentation,

Logic and Computer Systems
ISA S 18.1 Annunciators - Sequences and Specifications
International Standards Organisation (ISO)
ISO 9001 Quality Systems - Model for QA in Design/Development, Production,

Installation and Servicing
ISO 9003 Quality Systems - Model for QA in Final Inspection and Testing
3.2 Environmental Conditions
3.2.1 The PLC equipment will be installed in a desert location of high ambient temperature and humidity
conditions. The atmosphere is expected to be dusty and corrosive and may contain traces of hydrogen
sulphide. The equipment supplied shall comply with GES A.06.
3.2.2 The PLC equipment shall be installed in an air conditioned environment. However the PLC system shall be
expected to function upon the failure of the HVAC system when the temperature can fall to 32°F (0°C) or
rise to 122°F (50°C). Under these conditions the relative humidity can rise to 100%. Prior to installation
the equipment may be stored under the environmental conditions which shall be advised in the Purchase
Order/Contract.
3.2.3 The Vendor/Contractor shall supply a list of similar sites where his equipment has continued to function in
the last 2 years.
3.2.4 Where necessary, a cooling fan with a fan failure detection alarm on the PLC system and a repeated alarm
in the control room shall be provided.
3.3 Noise Limits
3.3.1 Equipment supplied shall not produce a noise of more than 30 dBa. The noise limits specified shall apply
to all items of equipment including ventilation fans. The noise shall be measured at a distance of 3 feet (1
metre) from the equipment casing or at the operator's work-station. Where required acoustic enclosures or
hoods shall be provided to reduce the noise level to an acceptable level.
3.4 Hazardous Area Classification
3.4.1 Control room shall be classified as a safe area (unclassified) during normal operating conditions.
3.4.2 Field equipment connected to the PLC system shall be selected, installed and maintained BASEEFA (or
CENELEC) certified Intrinsically Safe for use in Zone 1 Hazardous Area, Gas Group IIA/IIB, Temperature
classification T6. These zone classification categories and the type of protection have been assumed,
however the detailed project specific specification shall state the type of hazard and type of protection
required.
3.5 Eletromagnetic Interference
The system shall be immune to electromagnetic interference as defined in BS EN 61000 severity level
Class 3.
3.6 Electrical Interference

Rev 0 1999
The PLC system shall meet the EMC surge resistance requirements of IEC-61000 Part 4.3.
3.7 System Availability
3.7.1 The availability of the complete PLC system (all modules and subsystems included) shall be specified on
project specific basis but shall nevertheless be in excess of 99.95% for process and machinery control
applications and 99.995% or better for safety related critical applications.
3.7.2 The Vendor/Contractor shall perform detailed availability calculations stating all data sources and all
assumptions made. The Vendor/Contractor shall apply a weighting system to arrive at meaningful
availability figures based on an 8 hours MTTR figure.
3.7.3 The method of calculation shall be based on BS 5760.
3.8 Guidelines for System Selection
3.8.1 Relays systems shall be used for only small systems with simple logic, and therefore shall be considered
only under the following circumstances:
1) where the logic is simple and the system has less than 12 I/O;
2) where significant future changes to the system are not foreseen;
3) where the system does not need serial interfacing to other computer systems, e.g. DCS
system;
4) analogue inputs are not to be handled;
5) where the system is an extension to an existing system, or where 6) it is
desirable that the technology be the same as existing systems.
3.8.2 The use of micro type PLC's shall be avoided for reliability and maintenance reasons.
3.8.3 Where possible the type of PLC used shall be standardised for the entire facility or plant. Separate PLC's
shall be used for separate production trains.
3.8.4 The PLC shall be of proven design and shall have been in use for similar duties for at least 3 years.
Vendor/Contractor shall provide details of all such similar duties where the PLC has been successfully
used.
3.8.5 The Owner shall provide the Vendor/Contractor with a brief overall functional description of the plant.
This description shall include adequate information for the Vendor/Contractor to be able to propose the
correct type of PLC system and the correct system configuration. Owner shall specify the details of
certification required.
3.8.6 The Owner shall provide to the Vendor/Contractor an overall control function and control system
description. Such description may be either supplemented by or replaced by flow charts, functioning
charts, logic diagrams, input/output schedule, cause and effect charts and P&ID's.
3.8.7 If the PLC is being supplied as part of a package the document format, presentation details and symbols
shall be agreed with the Owner.
3.9 Input/Output Modules
3.9.1 General
(a) Vendor/Contractor shall indicate in his bid if using isolated I/O's leads to the loss of nominal I/O
capacity.
(b) Vendor/Contractor shall also advise the largest and the minimum wire size the module terminal
Rev 0 1999
blocks can accommodate. The wire size range shall be at least 12 AWG (2.5 mm2) for digital and
16 AWG (1.5 mm2) for analogue terminals. Analogue terminal connections shall include one
shielded wire connection per loop.
(c) It shall be possible to mix all types of I/O modules in any given rack, irrespective of their voltage
level.
(d) The number of points per I/O module shall be specified by the Vendor/Contractor. Rack space
availability, and the maximum output current per point/module allowed.
(e) The wetting voltage levels of powered contacts shall be specified on per project basis by the
Owner.
(f) I/O's shall be galvanically isolated from each other and from the CPU to prevent fault on the field
wiring being transmitted to other channels and the CPU. Transient voltage isolation for discrete
I/O shall be a minimum of 1000 Volts RMS, common mode.
(g) All I/O circuits shall be designed so that accidental connections of 1000V AC/DC to discrete I/O
field terminals for an unlimited time shall not destroy any component in the I/O circuits other than
the circuits to which the voltage was applied.
(h) It shall be possible to remove and replace the I/O module without damage and without any field or
internal (e.g. CPU) disconnections. Vendor/Contractor shall state in his offer, if it is possible to
remove and replace I/O modules without removing power from the PLC or other field devices or
disrupting the operation of the PLC in any way except for the functions associated with the
module being replaced.
(i) It shall not be possible to insert an I/O module and on-line activate it into an incorrect slot.
Modules shall be provided with means of being locked in positively in their slots.
(j) Shorting or grounding the field wires connected to any I/O modules shall not damage the module
itself.
(k) Field I/O wiring shall be connected to the I/O rack, via integral compression screw type terminals.
If separate terminal cabinets are required these shall be supplied by the Vendor/Contractor.
(l) The status of the I/O's shall be indicated on the I/O modules using LED's.
(m) All inputs and outputs shall be individually fused or employ current limiting circuitry. Outputs
shall not be powered from the PLC internal power supply. Indication of I/O fuse blown shall be at
the front of the I/O module. Fuses shall be readily accessible for maintenance (i.e. without
removing the I/O modules) and their replacement shall not result in any disruption to the system.
All I/O fuses shall be of the same dimensions.
Rev 0 1999
(n) The I/O's shall assume Owner defined state upon the following failures;
Power failure to the CPU or I/O 's.

Failure of the CPU or the I/O's.
Physical removal of the I/O module or a blown fuse in the I/O module.
The loss of communication between CPU and I/O module.
Failure modes such as hold last value shall be defined by the Vendor/Contractor in conjunction
with the Owner.
(o) Intrinsically safe loops may be specified to provide hazard protection in line with the hazardous
area classification requirements.
(p) Intrinsically safe loops shall be implemented by means of safety barriers and certified transmitters,
except where the PLC system has been certified as being intrinsically safe by an approved body.
Galvanically isolated barriers are preferred.
(q) Wherever possible, the safety barriers shall be mounted within the I/O termination cabinets.
Intrinsically safe loops shall have segregated terminations, and shall be run in dedicated wiring
channels.
3.9.2 Digital Inputs
(a) Digital inputs shall include input signal conditioning and shall be capable of accepting voltage or
volt free contact signals.
(b) Digital input signals shall be conditioned by a low pass filter, to reduce the effect of noise and
contact bounce.
(c) A minimum of 600 VDC opto-isolation shall be provided between each input signal and the CPU.
(d) Frequency (pulse) inputs shall have an input resistance of 1 megohm minimum and be capable of
handling high speed pulses of up to 50,000 Hz.
3.9.3 Digital Outputs
(a) The use of interposing relays shall be considered for outputs where larger currents need to be
switched or where the inrush current would lead to a blown fuse or where the leakage current
would prevent the change of output signal.
(b) Discrete output circuits shall incorporate resistor/capacitor suppressors where necessary, e.g. for
solenoid valves.
(c) Discrete outputs that drive solid state devices e.g. annunciator points shall be provided with dry
relay contacts. Current load resistors with solid state outputs are not acceptable for this duty.
3.9.4 Analogue Inputs
(a) All analogue inputs shall have the following features:
Accuracy better than 0.1% of range of all inputs.

Minimum 12 bit resolution.
Common made noise rejection of at least 80dB.
Normal made noise rejection of at least 45dB.
Signal filtering.
Fuse protection or protection from inadvertent grounds.
Measured variable out of range detection.
Rev 0 1999
Over range clamping.
CPU/Module communications indicator.
Calibration adjustments.
(b) Thermocouple and RTD input shall be provided with the following facilities:
Support for thermocouples type J, K and T (Field Selectable).

Automatic cold junction compensation.
Open thermocouple detection.
Overall accuracy of at least 1°F (0.5°C).
Support for 3 or 4 wire RTD.
Linearisation to a stipulated standard.
Communications to CPU OK indicator.
3.9.5 Analogue Outputs
(a) Analogue outputs shall have at least 10 bits resolution (12 bits resolution is preferred) i.e accuracy
shall be at least 0.5 percent.
(b) Analogue output shall provide a 4 to 20 mA DC signal and shall be capable of operating loops up
to 550 ohms resistance minimum. The use of other signal levels such as 0-5 V DC or 1-5V DC
shall be subject to approval by the Owner.
3.9.6 Remote I/O
(a) Consideration shall be given to the use of remote I/O's where long cabling runs are involved.
Remote I/O network shall be secure and capable of communicating to I/O modules over twisted
pair, fibre optics, or co-axial cable of distances of a least 1000 feet (300m).
(b) When remote I/O's are considered the following factors shall be taken into account: maximum
distance limitation, communication cable type, number of slave nodes and redundant
communication links.
(c) The use of redundant communication links shall be decided by the Vendor/Contractor and
approved by the Owner and these links shall be routed via geographically different paths.
(d) Communication driver software/firmware shall continuously monitor and check the status of
communications link and associated I/O. Communications status indicator shall be provided on the
face plate of each associated module.
(e) Remote I/O cabinets shall incorporate their own power supplies.
3.9.7 Special I/O's
The use of special I/O's such as intelligent I/O's (e.g. high speed counters, P&ID controllers, programme
module type, servo controller type) shall be subject to approval by the Owner.
3.10 CPU and Memory
3.10.1 The processor shall be modular and removable for maintenance, and shall be electrically isolated from
associated I/O components.
3.10.2 The CPU module shall be fitted with healthy, communications active, remote I/O active, CPU running,
module failure and battery O.K. indications as minimum. It shall also have battery backed up real time
clock.
3.10.3 The number of ports required on the CPU shall be specified by the Vendor/Contractor in conjunction with
Rev 0 1999
the Owner and shall take into account communications with remote I/O channels, future requirements,
programming devices such as IBM compatible PC, operator interface devices, peer to peer networking and
higher level e.g. DCS/SCADA interfacing.
3.10.4 The selected CPU speed shall be such that the scan time is not exceeded by that required for the
application. The total scan time shall be agreed with the Owner. Unless otherwise stated the processor
shall be capable of scanning and updating the I/O and executing user defined discrete logic a minimum of
10 times per second and analogue functions a minimum of 4 times per second.
3.10.5 When combining discrete and analogue functions in one processor, the net processor execution time
increase due to the analogue functions shall be taken into consideration.
3.10.6 A real time clock with a minimum of 10 millisecond resolution shall be provided for time tagging events,
rate calculations and other time dependent functions.
3.10.7 The instruction set for the CPU shall include as a minimum ladder or Boolean logic or preferably both,
normally open and closed contacts of digital inputs, outputs, internal control relays, timers (increments to
be stated) counters and integral maths functions using both integers and real numbers. Facilities shall also
include IF-THEN-ELSE programming and median select and median deviation functions for analogue
input voting. Other functions such as PID control shall be specified, if required, on a project basis.
3.10.8 A manual reset push-button shall be provided to initiate the restart of the system after shutdown, e.g. on
total power failure. Operation of the reset push-button shall put the system in a known safe state from
which the PLC or operator can start-up any shutdown equipment. Manual reset push-buttons shall be
provided with a guard to prevent accidental operation.
3.10.9 The executive memory shall be unaffected by power failure or switching off the PLC and this memory shall
be of the non-volatile type. The type of memory supplied (RAM, EPROM, EEPROM) shall be dictated by
the application and this shall be approved by the Owner.
3.10.10 Battery backed up RAM type memory shall be used if there is requirement for the programs to be modified
and debugged by the Owner, otherwise EPROM shall be used. Flash RAM type of memory shall be used if
there is a requirement for frequent changes to be implemented over a modem for equipment located in
geographically isolated environment.
3.10.11 If the application program can not be kept in EPROM then the following requirements shall apply for the
battery:
Battery shall only supply the memory when the main power is off.
Battery shall be replaceable on-line without corruption or loss of memory.
Battery low indication light with remote alarm shall be provided.
Processor shall retain its memory for a minimum of 6 months.
Battery shall have a shelf life of 5 years or longer.
Battery shall be rechargeable type.
3.10.12 Batteries supplied with the PLC system shall be monitored in the user programme and an alarm raised when
the voltage level dips below a given figure.
3.11 Power Supplies
3.11.1 Main Power Supply
(a) The Owner shall supply the external AC UPS and shall detail the characteristics of the supply on
project specific basis. The PLC system Vendor/Contractor shall supply termination, isolation and
protection equipment within his panel. PLC systems for critical applications shall be supplied by
Rev 0 1999
two independent feeders. Fault on one feeder or local power supply shall not affect the other
feeder. An alarm shall be fitted and connected to the display on the monitoring system (PLC, DCS
etc.) diagnostic display to alert the operator of the failure. Separate transformers and power
supplies shall be used for CPU power and powering I/O's.
(b) Power supplies shall be replaceable on-line without disrupting the process and without impacting
PLC control capability.
(c) The Vendor/Contractor shall co-ordinate with the Owner to ensure that discrimination can be
achieved between the external UPS (if used) and the PLC protective devices. The
Vendor/Contractor shall provide time/current co-ordination curves showing that faults on the
downstream circuit will not affect the upstream operation.
The Owner shall specify the type of UPS used. This may be a true UPS driving it's output
continuously from an inverter or the type that switched between line and inverter during a power
failure.
(d) LED visual indicators shall be provided for the condition of the power supply and its fuses for the
PLC system rack power supply.
(e) The responsibility for the use of dual redundant power supplies for I/O's shall be with the Owner.
(f) The sizing of auxiliary DC power supplies used to power I/O field points shall take into account
such factors as temperature de-rating, future spare I/O's including analogue I/O's. In any event a
minimum of 20% and a normal maximum of 50% spare capacity shall be provided after the
following factors have been taken into account:
Specified configuration (CPU, I/O cards etc.).

Sparage (including installed spares).
Loading of all modules at maximum load.
(g) PLC system power supplies other than I/O power supplies shall have 100% excess capacity. Each
power supply shall be connected by it's own externally accessible internal fuse or miniature circuit
breaker (MCB). It shall be possible to replace the fuses or MCB's without having to remove the
power supplies. The use of MCB's is preferred over the use of fuses. MCB's shall be double-pole
with indicator for fault detection. Protection on the output side of the power supply shall be
provided by a current limiting circuitry.
(h) On larger systems, an additional power outlet shall be installed on the outside of the cabinet. This
outlet shall also be fed from the PLC CPU power circuit. The power outlet shall be either fused
with a fast blow fuse or circuit breaker or wired on it own circuit so that power to the PLC is
uninterrupted. The external power outlet shall also be labelled "To be Used Only for Programming
Equipment". Additionally, a data circuit plug output (serial port) with a cover shall also be
provided.
Rev 0 1999
(i) System power supplies shall also have over temperature protection, integral fuse protection and
status LED to indicate power supply faults. In addition, each power supply shall have an alarm
contact to indicate the presence of a fault.
(j) A convenience outlet similar to the one described in (h) above next to the CPU shall be provided
to power the programming equipment. This outlet shall be powered from the same circuit as the
PLC CPU. The outlet shall be labelled "To be Used Only for Programming Equipment".
3.12 Applications Software
3.12.1 Programming Unit
(a) Handheld programmable terminals with limited functions and scan facilities shall be avoided.
Unless otherwise stated a portable or permanent programming unit shall be provided for each PLC
system. The programming unit shall be capable of at least:
Monitoring and altering the status of PLC inputs and outputs.

Monitoring the operation of the PLC programme.
Modifying the PLC programme.
Producing records of PLC programmes on disc or other stipulated media as well as
printout with comments.
Programming in off-line (not in the RUN mode) and on-line mode.
(b) An IBM compatible PC based system shall be used for programming the PLC unit. If such a unit is
proposed then it shall not require any special BIOS, or any other special card or board or a special
operating system. The latest stable version of the operating system and other software is very
strongly preferred.
(c) The Vendor/Contractor shall state in his bid, if an upgrade to the executive programme due to
additional features, enhancements and corrections can be implemented on site or the circuit board
has to be returned to the Vendor/Contractor's factory.
(d) When sizing the PLC memory the Vendor/Contractor shall provide detailed breakdown of
executive memory, scratch pad, system status, input data table, output data table, internal bits,
registers and user programme area.
(e) It shall be possible to connect or disconnect the programming device without the need to energise
or de-energise the PLC or the programming unit.
(f) The programming unit shall be capable of making a backup of the CPU onto a 3.5" diskette or
onto an internal hard drive.
3.12.2 Programming
(a) PLC programming shall be performed by the Vendor/Contractor unless otherwise specified by the
Owner. Contracting out the PLC programming to third parties shall be subject to the Owner's
approval.
(b) Software changes shall be carried out preferably off-line, tested and then down loaded into the
running application. Off-line programming software shall include the run emulation capability for
testing and trouble shooting of the application programme. PLCs shall also have on-line editing
capability so that modifications to the ladder logic may be made without stopping the processor.
(c) Only relay ladder logic shall be used for programming. However, it is recognised that depending
upon application, other programming formats may have distinct advantages. Other programming
techniques e.g. Boolean logic symbols may be used subject to the Owner's approval. The use of
Rev 0 1999
programming languages such as C and PASCAL for applications other than the graphics
generation shall require the Owner's approval.
(d) Programming software shall be user friendly, shall be the latest stable revision available at the time
of order and shall as a minimum contain the following facilities:
Enter, display and edit relay ladder logic.

Generate, list and printout of ladder programmes, memory contents, configurations cross
reference tables and annotations.
Display on-line data changes.
Manually force Input/Output and provide states display and status printout of the same.
Display system diagnostics/fault statuses.
Ability to import and export the PLC database in a standard industry format.
(e) The programming software shall be capable of monitoring the real-time status of data/memory
locations whilst the CPU is scanning the application programme.
(f) Unless a different programme methodology is specified by the Owner, the methodology specified
in this section shall apply.
(g) Segregated sub-routines for standardised control e.g. MOV control, pump start/stop etc. shall be
developed and used. Identical logic structures, modules and elements (with the exception of tag
numbers) shall be used for parallel trains.
(h) Similar groupings of data and features shall be kept together i.e. a structured programming
technique shall be adopted. Example of such groupings are:
Unit conversion factors - at the start of programme.

Common data calculations.
Common internal coils.
Equipment control.
External system interface data blocks.
(i) Simple programming techniques shall be aimed for. Complex functions shall be kept to a
minimum and shall only be used where justified and approved by the Owner. These shall be fully
documented.
(j) Continuous e.g. PID control on PLC shall only be used with the Owner's permission.
Configuration for PID shall be using user-friendly fill-in-the-blanks type of technique. Any
additional programming shall be avoided.
(k) A keylock mode-selected switch on the CPU module shall prevent memory modification from any
outside source. Other functions or equivalent functions selected by keylock shall include
programme/Run/Lock/Unlock.
(l) All programming including all I/O and internal addresses shall have alphanumeric tag names and
descriptors. Comment blocks shall include a cross reference to the source binary logic drawing
number. Programming shall also allow on-screen comments for a functional description of an
application programme.
Rev 0 1999
(m) The relay ladder logic numbering system used shall be decided by the Vendor/Contractor. The
order of preference is Sheet and Line Numbering System, Sequential Numbering System and PLC
Address System. The last one shall be avoided if at all possible.
(n) The software used shall have the ability to compare two programmes and flag the differences.
(o) Vendor/Contractor shall state in his bid if the programming terminal provides a display of all
system diagnostics states.
(p) Vendor/Contractor shall advise in his bid, any limitations of his system, with respect to tagging.
3.13 Man Machine Interface
3.13.1 The type of Man Machine Interface employed shall be approved by the Owner.
3.13.2 The type and number of graphic displays (static or dynamic) shall be prepared by the Vendor/Contractor
using the project P&IDs as the base document and approved by the Owner.
3.13.3 If external annunicator is specified then this annunciator shall meet the requirements of GES J.19.
3.13.4 If the PLC VDU is to be utilised for alarm handling purposes, it shall mimic as close as possible the
facilities provided by a conventional annunciator.
3.13.5 Logging reporting and trending requirements shall be specified by the Owner and logs, reports and trends
shall be programmed in the PLC by the Vendor/Contractor.
3.14 System Security
(a) The system shall incorporate both keylock and password protection against unauthorised access.
(b) The system shall incorporate comprehensive self-diagnostics so that all permanent and transient
faults are identified, located, alarmed and reported. All diagnostics shall be performed
automatically on-line and without disturbing the process or reducing the reliability of the PLC.
(c) PLC on-line diagnostics shall included the following:
1. Testing of all spare boards in the systems.

2. Testing board states at a minimum frequency of once per minute.
3. Checking the I/O board configuration and setting the main chassis alarm if boards are
missing or faulty.
4. Checking the I/O boards for faults, including fuse failures and if detected, turn on fault
LED on the board.
5. Performance diagnostics on the communication processor and cables which handle I/O
board communication.
(d) PLC diagnostics on its main processor shall include the following:
1. Diagnostics on the processor and the floating point (FP) unit performed continuously in
the back ground.
2. Random Access Memory (RAM) diagnostics also performed in the back ground.
3. Microprocessor on the main processor board checked for proper response before
application programme execution.
Rev 0 1999
4. Verification of the control programme check sum.
5. Continuous running of the Universal Asynchronous Receiver Transmitter (UART)

diagnostics.
6. Continuously checking of the check sum of all programme read-only memories (ROM's)
on the main processor.
7. Verification of the redundant processor programmes (if applicable) as good and current.
8. Power-up diagnostics performed on the main and back-up processor (if applicable).
(e) CPU shall shut down in the event of the following:
Operating system PROM error.

RAM address error.
Start-up processor test error.
Watchdog timeout.
(f) A single error shall not cause any output to go to an unpredicted state.
(g) For each type of PLC employed, the Vendor/Contractor shall detail in his bid, how the various
types of errors (diagnostics, programming, processor, communication, internal clock, parity, I/O
image register etc.) are generated or combined together and what means are available for the
operator to view these.
(h) On loss of power the PLC outputs shall go to their predictable specified state in an orderly
manner. Unless stated otherwise upon restoration of power the CPU shall automatically restart to
the state it was in before the power failed. On restart the CPU shall verify that the programme and
I/O status have been correctly recalled. If an error is detected, the CPU shall shutdown.
(i) Fault alarms shall be generated when the I/O modules fail, or for serially coded digital signals,
when an error is reported or transmission failed. Open circuit (burn out), short circuit and out of
range detection shall be provided for thermocouple and RTD inputs. Also out of range shall be
monitored for all 4-20 mA inputs, alarming when the current is less than 3.8 mA or greater than 21
mA.
3.15 Systems Interfacing and Communications
3.15.1 The information to be transferred to and from the DCS shall include, but not be limited to:
System alarms and status.

Discrete I/O status.
Analogue I/O values.
3.15.2 The speed of transmission shall be such that any change in I/O state which is displayed on the DCS VDU
shall be displayed within 4 seconds from the time the change in state took place.
Rev 0 1999
3.15.3 Unless otherwise specified by the Owner, serial communication with other systems e.g DCS or SCADA for
logging and reporting shall be by standard single serial interfaces (RS 232, RS 422 or RS 485) using an
industry standard protocol (e.g. MODBUS RTU). Reference is made to the Data Sheet attached to this
specification. The Vendor/Contractor shall complete these sheets for each PLC external link. Unless
otherwise stated the Vendor/Contractor shall be responsible for linking up to all external digital systems.
The links shall be transparent between the two systems and user friendly. The Vendor/Contractor shall be
responsible for developing any additional functionalities required to implement these features.
3.15.4 Serial communication shall include error checking mechanisms as well as diagnostics, parity, loop back
checking, Cyclic Redundancy Check (CRC) and auto recovery of nodes.
3.15.5 Parallel hardwired interfaces shall be used where an executive action follows the transfer of data, e.g. alarm
accept and reset of an annunciator panel. Potential free contacts or opto-isolators shall be used for isolation
between systems.
3.15.6 Communication protocol can be master slave type. Any requirements for peer to peer communications
shall be decided upon by the Owner. Network traffic loading shall not exceed 50% of the total capacity for
deterministic networks e.g. token ring or token passing type of networks and 30% for non-deterministic
networks such as Ethernet type of networks.
3.15.7 PLC networks shall incorporate a facility for detecting and preventing an uncontrolled transmission by a
node.
3.15.8 LED's on the PLC communications module shall include active communications port, communication OK,
and Transmit/Receive status.
3.15.9 It shall be possible to make communication connections and disconnections without interrupting or
jeopardising system operation.
3.16 Expansion and Sparage
3.16.1 At least 20% fully wired spare capacity shall be provided within each system. This shall apply to
marshalling cabinets, terminations, and I/O modules. These spares shall be additional to and separate from,
those required for normal operation.
3.16.2 At least 5% fully wired spare capacity shall be allowed for project development. Allowing for this an
additional 20% spare capacity shall still be available at the end of the project design stage.
3.16.3 The Vendor/Contractor shall state the method used to estimate the memory size taking into account spare
memory for future use. The spare memory at the time of shipment shall be at least 50% of the total
memory after all software has been loaded.
3.16.4 10% spare relay bases shall be provided.
3.16.5 All wiring and system cables shall include 20% spare capacity for post commissioning modifications. All
installed spare I/O modules shall be wired to spare terminal points.
3.16.6 The additional spare I/O when installed and commissioned shall have no effect on the system performance
whatsoever.
3.16.7 All cores of incoming field cables shall be terminated. Spare cores shall be provided in the system cables
and connectors and terminated as far as the I/O rack. These shall be available as future spares but shall be
grounded to the clean earth.
3.16.8 The Vendor/Contractor shall provide details of recommended spares for commissioning, two years
operation and for insurance (as applicable).
Rev 0 1999
3.16.9 Insurance spares are those specific spare parts which although acknowledged to have a long life or a very
small chance of failure would cause prolonged shutdown of equipment because of the long delivery of a
replacement part.
3.16.10 Any spares recommendations shall be sufficient to support required system availability requirements. The
Vendor/Contractor shall detail the expected usage of spares for the first year of operation.
3.16.11 When future plant expansion is specified, the operator work-stations (if supplied) shall be capable of
monitoring the complete plant including future facilities without the need for additional hardware (such as
memory, power supplies, processors). In order to size these units, unless otherwise specified the
Vendor/Contractor shall allow a 30% future expansion capability for database and display requirements.
3.16.12 In addition to installed spares, the system (including spares) shall be designed with 20% spare space
available in racks, cabinets, etc.
3.17 Bid Format
3.17.1 Any deviation from this specification shall be indicated in the Vendor/Contractor's bid, on a point by point
basis, referenced to the relevant section of this specification. Where alternatives exist which offer a better
solution, then these shall be offered as options to the Vendor/Contractor's main proposal and must comply
with the specification, otherwise these shall not be offered. The benefits of such options shall be clearly
stated.
3.17.2 The Vendor/Contractor shall provide a "List of Exceptions" with reasons for deviations. If no such list is
provided with the bid it shall be assumed that the equipment proposed meets all requirements of the
specification and attachments to the enquiry document.
3.17.3 The Vendor/Contractor, shall provide in his bid, a rack layout diagram showing slot allocation including
spares slots taken up by the system components e.g. dual card power supplies, double width cards, and the
number available to the end user. Configuration details of each and every rack shall be recorded in the bid.
3.17.4 The Vendor/Contractor shall supply the following information in the bid and at the end of FAT for
inclusion in the PLC manuals.
1) the amount of spare processing power available and the system response time;
2) spare memory capacity available for the addition of programmes and data;
3) spare data base capacity. The number of tagged items that may be added to the system in
the future;
4) power supply capacity, which shall be sized to accommodate any future expansion.
4.0 MATERIALS
4.1 General
4.1.1 All materials and components shall be new and of the highest quality. Should any material or component
prove unsatisfactory during manufacture or testing, it shall be rejected not withstanding any previous
certification, satisfactory testing or examinations. Prototype products under development are not
acceptable.
4.1.2 The Vendor/Contractor shall have an effective system of part numbering for all replaceable parts. The part
number shall completely define the part, including the components of which it is made.
4.2 Printed Circuit Boards
4.2.1 Printed circuit boards shall be of industrial quality and shall be provided with guide rails and means for
secure locking in place and shall be capable of being replaced whilst in service.
Rev 0 1999
4.2.2 PCB mounting shall be vibration proof.
4.2.3 Board design shall prevent damage to board if inserted incorrectly.
4.2.4 All LED's or visual indicators which are installed on PCB's within modules shall be mechanically protected
(i.e. by a transparent cover), and if possible be labelled externally.
4.2.5 All boards shall be tropicalised, all edge connectors shall be gold plated and all major PCB components
shall be clearly labelled.
5.0 MANUFACTURE
5.1 Cabinets and Enclosures
5.1.1 Cabinets, enclosures and marshalling cabinets shall comply with the requirements of the GES J.12.
Single cabinet or enclosure overall dimensions shall not exceed; length 13 ft (4 m), height 7¼ ft (2210
mm), width 47¼ in (1200 mm). If a longer cabinet is required to house the PLC equipment, then a
shipping brake in the cabinet or enclosure shall be provided.
5.1.2 Spare space shall be left for any future equipment e.g. power supplies, racks, cables etc. Mounting holes
for such equipment shall be pre-drilled and tapped.
5.1.3 The layout of the PLC system cabinet shall be approved by the Owner. Special attention shall be paid by
the Vendor/Contractor to provide adequate working and maintenance clearances. The design shall take into
account the combined effect of ambient temperatures and heat generated from power sources.
5.1.4 The CPU and its power supply shall be located in the I/O rack at the top of the cabinet for adequate heat
dissipation, ventilation and for a reasonable working height for maintenance.
5.1.5 The Vendor/Contractor shall notify the Owner if forced ventilation is required in which case back-up fans
and dual air filters shall be provided by the Vendor/Contractor. Intake shall be through the lower section
and exhaust through the upper section.
5.1.6 The cooling of components by natural convection is preferred, but if fan assisted cooling is necessary, then
fan failure and cabinet temperature alarms shall be fitted. The alarm shall be initiated from a 100 ohm
Platinum RTD mounted directly above the CPU and wired into an analogue input module.
5.1.7 All cabinets, including termination cabinets, shall be clearly marked to indicate that they form part of a
PLC system and shall be lockable. All cabinets shall have identical keys.
5.1.8 Internal cabinet components (with the exception of terminal rails) shall not be mounted less than 10 inch
(250 mm) from the floor of the cabinet.
5.1.9 Cabinet environmental protection shall be to a minimum of IP 54. Ventilated enclosures may be supplied
to IP 51.
5.1.10 Any additional requirements e.g. a robust pull out tray for notebook PC, may be specified by the Owner on
per project specific basis.
5.1.11 Unless otherwise specified, laminated plastic quick reference charts shall be permanently attached to the
inside of the PLC front door. The charts shall clarify proper module or PCB placement, and assist in the
interpretation of the status indicators.
5.1.12 All pushbuttons, lamps, switches etc. shall be heavy duty, derated, industrial type and dust tight. Lamp
Rev 0 1999
socket bulbs shall be long life de-rated for the service.
5.2 Earthing
System grounding shall take into account PLC manufacturer's recommendations and shall comply with the
requirements of specification GES J.17. Any contradiction between these shall be resolved during the
detail design stage.
5.3 Wiring and Terminations
5.3.1 Wiring and terminations shall comply with the requirements of GES J.12.
5.3.2 Wiring passing through metal walls or partitions shall be protected by correctly fitting grommets or bushes.
5.3.3 All input/output terminals shall include "knife type" (Weidmuller SAKR type) or equal terminals to
facilitate system testing. Wiring for thermocouple cable shall be routed direct to the PLC input module,
bypassing any terminal strip. In the event that terminal blocks are required for the thermocouple input
wiring, the link material shall be of the same material as the T/C wire.
5.3.4 DC power shall be distributed via Weidmuller AFT PO44/A or equivalent type fuse terminals within the
panel in such a manner that each user, circuit or system may be individually isolated.
5.3.5 Discrete input field devices shall be wired so that they switch the 'live' side of the line. Discrete outputs
shall be switched from the 'live' side of the line.
5.3.6 I/O wiring for each process train (including duty/standby equipment) shall be terminated on separate I/O
modules. If racks are required to be powered down for replacing an I/O module, then each process train
shall be terminated in separate racks in order to facilitate on-line maintenance.
5.3.7 On large spread networked systems, temporary telephone links shall be provided.
5.4 Identification and Tagging
5.4.1 The requirements of GES J.12 shall apply.
5.4.2 Each type of PLC module, equipment and enclosure (including junction boxes), forming part of the PLC
system shall be clearly and uniquely identified by means of permanent external labelling. In addition each
PLC module shall clearly indicate the designated field signal range and type of signal e.g. 120 VAC Digital
Output.
6.0 SITE PREPARATION AND INSTALLATION
6.1 Installation
6.1.1 The requirements of Section 3.4. of GES C.54 shall apply.
6.1.2 Areas of high vibration and electrical noise shall be avoided. Stand alone (non-panel mounted) PLC's shall
be installed at convenient height for inspection and maintenance. The termination cabinets shall normally
be installed before the PLC system, so that field cables can be pulled and terminated.
7.0 INSPECTION
7.1 Procedures
Rev 0 1999
7.1.1 The inspection requirements are covered by the document "General Conditions of Purchase" which forms
part of the Purchase Order/Contract. Additional requirements are given below.
7.1.2 All inspection activities to be performed including any special requirements shall be agreed with the Owner
and shall be incorporated within the agreed Quality Control Plan provided by the Vendor/Contractor.
7.1.3 The Vendor/Contractor shall allow the Inspector free access to all areas of manufacture, fabrication,
assembly and testing.
7.1.4 The Vendor/Contractor always has the responsibility to provide adequate quality control and inspection of
equipment and materials. Any inspection by the Owner or his Inspector shall not relieve the vendor of these
responsibilities or those under his warranty.
7.1.5 The Vendor/Contractor shall demonstrate to the satisfaction of the Owner that his Quality Control Plan will
be such as to ensure close agreement between the performance of random production samples and those
submitted for certification.
7.1.6 The Vendor/Contractor shall provide a project team for the full duration of the project, including site
activities unless otherwise agreed with the Owner. The core members of the team shall work exclusively
on the project. The extent of involvement of specialist personnel who are only required for specific tasks
shall be clearly stated in the bid. This team shall be co-ordinated by an experienced project manager. The
Vendor/Contractor shall submit CVs for approval of prospective project manager and lead software and
hardware engineers.
7.2 Planning
7.2.1 Vendor/Contractor shall provide estimated duration of the major activities presented in a network format,
with his bid.
7.2.2 Following order placement, the Vendor/Contractor shall submit, within 2 weeks, a programme of
engineering activities (bar chart format and network) including early, late and freeze dates of activities and
information requirements for approval by the Owner. Key milestones shall be highlighted.
7.2.3 Vendor/Contractor shall identify all project specific software together with development plan.
7.2.4 The Vendor/Contractor shall submit a list of documents that he requires from the Owner in order to fulfil
his contractual obligations. This list shall also detail the latest date by which these documents are required.
7.3 Progress Monitoring
The Vendor/Contractor shall include for the monitoring of progress on a continuous basis for the duration
of the project. Progress measurement method shall be presented for approval by the Owner 2 weeks after
commitment. Regular meetings shall be convened (a minimum of one per month) to discuss progress,
information flow and outstanding activities. The Vendor/Contractor shall prepare and issue minutes of
these meetings within 3 days of the meeting.
7.4 Quality Assurance
7.4.1 The Vendor/Contractor shall maintain an effective quality system that complies with Project requirements
as well as those of ISO 9000/1 and ISO 9003.
7.4.2 The Vendor/Contractor shall supply a preliminary quality manual with the offer with a project specific
Quality Plan after order placement.
7.4.3 The Quality Plan shall also include monitoring performance of sub-contractor's work. The approved
Quality Plan shall be the control document for the performance of the work. The Quality Plan shall include
references to the quality manual.
Rev 0 1999
7.4.4 The Vendor/Contractor shall submit for the Owner's approval inspection requirements summaries for every
item in the scope of supply. The Owner shall have the right to witness the Vendor/Contractor's QA/QC
operating on all equipment during design, fabrication, assembly and testing.
7.4.5 The carrying out of the quality control shall be the Vendor/Contractor's responsibility. However the Owner
reserves the right to ensure that the agreed procedures are being followed. The Vendor/Contractor shall be
submitted to internal audits by the Owner to ensure that an efficient QA programme is established and
complied with and that non-conformances discovered during audits are promptly corrected.
7.4.6 The number of audits/monitoring period is not fixed and the Vendor/Contractor shall agree with the Owner
the frequency of these audits before order placement.
7.4.7 Software quality procedures shall contain the following minimum information:
Company policy on QA.

Departmental procedures and working practices.
Documentation and media control.
Design and programming standards.
Fault tolerant features.
Design review and audit frequency.
Verification and validation.
Test and integration strategy.
Defect recording and analysis.
7.5 Software
7.5.1 All software packages shall be identified by revision and date. Only software identified as such shall be
loaded.
7.5.2 A complete record shall be kept of all software errors and corrections carried out during the development
and testing of the system. The software problem log shall be maintained, recording the description of the
problem, any diagnostic and supporting data, software modules affected and the corrective action taken.
7.5.3 Media (e.g. diskette) handling procedures shall be developed to ensure that only the official media are used
for the test, that they are protected against unauthorised modification. At least 2 sets shall be kept and
regularly updated in case of damage to one set. At the end of the test the Owner shall retain two sets for his
own purposes including the source code listing.
Rev 0 1999
7.6 Visual Inspection
7.6.1 The system shall be inspected to ensure that it is assembled and completed in accordance with the latest
approved drawings. The drawings shall include specifications, assemblies, wiring, logic, general
arrangements and single line power drawings.
7.6.2 An inventory check shall be carried out to verify the existence of all parts, modules, cables, interface
equipment and other associated equipment covered by the Purchase Order/Contract. Check list sheets shall
be used to check off the items.
7.6.3 Visual inspection shall include checks on the following items:
the standard and finish of components and assemblies including structures and paintwork;
the overall dimensions, fixing points and lifting points;
the rigidity of cabinets and frameworks;
that trunking, wiring and wiring supports do not obstruct access to individual devices for removal
or adjustment;
that devices that generate heat, e.g. power supplies, are adequately ventilated;
that terminals and wiring are segregated and protected and meet safety and hazardous area
requirements;
that wiring and trunking is sized, coloured and identified in accordance with the specification;
that the earthing is in accordance with the specification;
that all modules (including spares) are present and correctly keyed and located;
that all major items are correctly labelled;
that all chassis, modules, wiring, are correctly labelled and that warning labels are in place;
that all fuses and other protection devices are correctly labelled and set to the specified values;
that all configurations e.g. rack, dip switch settings etc. correspond to the configuration diagrams
or configuration programme.
8.0 TESTING
8.1 Test Procedures
8.1.1 The Vendor/Contractor shall submit the FAT procedure for the Owner's approval at least eight (8) weeks
before the commencement of FAT. The Vendor/Contractor shall give a four (4) weeks notice of
availability of equipment for testing.
8.1.2 The Vendor/Contractor shall supply all labour, materials, consumables, test equipment, simulation devices
and office facilities complete with fax and telephone facilities for the duration of the FAT.
8.1.3 The Vendor/Contractor shall connect all system components and complete his own inspection and testing
before advising the Owner that the system is available for FAT.
8.1.4 Simulation equipment shall be provided to simulate all inputs/outputs, e.g. transmitters, valves and
annunciator panels. Unless otherwise stated in the Purchase Order/Contract computer based simulation
equipment, e.g. PCs shall be used for the simulation of serial communication devices, and digitally coded
transmitters.
8.1.5 The test procedures shall include for a heat soak and RFI immunity tests as detailed in Section 8.2 of this
specification and Section 8.2 of GES J.12. Both tests shall be witnessed by the Owner or his
representative.
8.1.6 All tests shall be carried out using the latest approved I/O schedule and functional logic drawings, and
cause and effect charts.
8.1.7 All test results shall be logged onto test cards. Each test card contained in the test procedure shall have the
Rev 0 1999
following minimum information on it:
Test number and title.

Test objective.
Test procedure.
Check list.
Comments.
Fault report.
Reservations/further action.
Time and date.
Space for various witnesses signatures.
8.1.8 A separate log of all faults starting from the commencement of FAT up to delivery at site shall be
maintained and shall become part of the test documentation.
8.1.9 The Vendor/Contractor shall issue revised documentation and drawings to cover any changes made as a
result of testing. Such documentation and drawing shall be issued "As Shipped".
8.1.10 Test procedures shall include tests to demonstrate the correct operation of all applications software.
8.1.11 Communications Testing
(a) The Vendor/Contractor shall submit for approval a detailed test procedures for testing the various
PLC interfaces. This document shall incorporate sufficient tests to demonstrate that the equipment
complies with all specifications and documentation. This tests shall also, as far as possible, test the
functionality of individual systems databases and file transfers when integrated as an overall
system.
(b) The document shall take account the need to demonstrate the function of every aspect of the
systems under conditions as close to operating conditions as possible. As a minimum the tests
shall include basic link operation, verification, resilience, performance and test for fault tolerance
where implemented. Tests shall be included to verify the system response to power failures and
auto restart. Tests shall be included to prove that the communication system can handle the
maximum system load and fault is tolerant. The procedures shall define how these aspects of the
system shall be tested.
(c) The document shall clearly include all the system simulations and tests to be carried out, how the
tests are to be performed, list test apparatus, suppliers and documentation required.
(d) The test procedures shall also include detailed information on communication port settings,
communication card switch setting, communication cable wiring diagram and software issue
statuses.
8.2 Factory Acceptance Testing
8.2.1 The entire system hardware including I/O modules and, software shall be subjected to a series of tests
witnessed by the Owner, his Inspectors and if specified as such, by the Owners plant maintenance
personnel, at the Vendor/Contractor's premises before shipment.
Rev 0 1999
8.2.2 Electrical and Continuity Tests
The following electrical and continuity tests shall be carried out:
AC short to the ground.

AC live wiring continuity.
AC neutral wiring continuity.
Continuity of different types of earths.
8.2.3 Input/Output Testing
(a) Wiring tagging and termination shall be checked and physical 'pull' tested, without stressing the
wire, to check that crimping and termination has been carried out properly.
(b) Inputs and outputs shall be tested one at a time.
(c) Where the termination cabinets are provided by the PLC system Vendor/Contractor, the I/O tests
shall be carried out from the termination cabinets.
(d) Digital input devices shall be simulated by switches. Analogue input devices shall be simulated
by current sources.
(e) Digital output devices shall be simulated by lamps or LEDs. Analogue output devices shall be
simulated by resistors set at the field device maximum impedance and current.
(f) Each digital input shall be checked by operating the simulation switches and checking that the
correct module input lamp is illuminated. The correct address and bit location shall also be
checked.
(g) Analogue inputs, if used, shall be checked for the correct addressing and digitised value. The
value shall be checked at 0%, 25%, 50%, 75% and 100% of full scale. Alarm and trip initiation
shall be checked for all analogue inputs.
(h) All software logic/application programmes shall be checked against binary logic diagrams and
dynamically tested and verified for proper sequence and functionality. The dynamic test will
involve physically simulating all inputs and outputs in their proper operational sequence, and on
power up verify that the application programme logic is executed properly.
(i) Digital outputs shall be set by software "forcing" the output and checking that the correct
simulation lamp is illuminated, using the input simulation panel to indicate the output.
(j) Analogue outputs shall be checked by the software "forcing" of an output, with the output value
being set digitally in the output address. The value shall be checked at 0%, 25%, 50%, 75% and
100% of full scale, and the output milliameter checked for the correct value.
(k) Loops shall normally be tested one at a time, but interrelated loops shall be checked as a complete
system.
(l) All external communication links shall be fully functionally tested as per Section 8.1.2 of this
Specification. The cable used to test the links shall be the same length the actual site cable unless
the Vendor/Contractor can demonstrate otherwise that this is not necessary.
Rev 0 1999
8.2.4 Heat Soak Test
(a) The heat soak test shall not be carried out until visual inspection and preliminary tests are
complete, and the Owner is satisfied that the Vendor/Contractor's tests have been carried out
satisfactorily.
(b) The serial number of all removable modules shall be noted before the commencement of the heat
soak test.
(c) All cabinet doors shall be closed and all cabinet entries, e.g., gland plates, blanked off to simulate
installed conditions.
(d) Any forced ventilation shall be in operation throughout the heat soak test.
(e) The equipment shall be set to simulate the maximum operational load, i.e., with all I/O set at their
maximum current.
(f) The following temperatures shall be recorded during the test:
ambient temperature of the heated enclosure;

the maximum temperature at selected points within the system.
(g) The temperature of the heated enclosure shall be cycled between 120°F (50°C) and factory
ambient at least four times during a 48-hour period.
(h) Owner specified random checks shall be made prior, during and on completion of the heat test.
All defects shall be recorded and defective equipment replaced.
(i) The extent of further testing shall with agreed with the Owner and will depend on the type and the
extent of the failures. The Owner reserves the right to request for a complete retest.
(j) Sample insulation checks shall be carried on wiring insulation at a test voltage not exceeding 250
V AC and shall be carried out after the heat test. Equipment which may be damaged by the
insulation check shall be disconnected. Any circuits having an insulation resistance of less than
10 megohms shall be rejected.
8.2.5 System Checks
(a) All features of the PLC system shall be checked; this shall include items such as system behaviour
following power failure, operation under adverse conditions, system diagnostics, programming
features, control sequences and interlocks.
(b) Sample checks shall be carried out with the system AC Supply set to each specified extreme
(normally ± 10%).
(c) The forced ventilation failure alarm shall be checked (if forced ventilation is fitted).
(d) The system response on card removal and re-insertion shall be checked.
(e) The system response isolation of a single power supply shall be checked.
(f) Where applicable, the system response on failure of a processor watchdog timer shall be checked.
(g) The functionalities of the spare I/O modules shall be checked by substituting these for the
operational ones.
Rev 0 1999
(h) The Vendor/Contractor shall carry out a running check of the processor loadings and spare
memory capacity.
8.2.6 EMC Compatibility Tests
The Vendor/Contractor shall provide testing to confirm that the equipment will operate properly when
energised and subjected to an electromagnetic field from a radiating source as per BS EN 61000 Part 4.1
(IEC 61000) severity class 3. The performance of the system shall not be degraded or impaired.
8.3 Site Acceptance Testing
8.3.1 The requirements for operability tests and site tests are outlined in sections 3.4.3 and 3.4.4 of GES C.54.
8.3.2 Depending upon the system size and complexity, additional SAT may be required to be carried out by the
Vendor/Contractor. The SAT procedure shall be supplied by the Vendor/Contractor and approved by the
Owner.
8.3.3 All actual field inputs shall be actuated and the results observed on the MMI and if required on the
programming device.
8.3.4 All field inputs shall be simulated to activate outputs and the correct operation of all final control elements
shall be checked. Such final elements shall include solenoid valves, motor starting etc.
8.3.5 All features of the PLC system shall be tested to ensure proper operation. These shall include system
behaviour following power failure, system diagnostics, programming features, redundant modules.
8.3.6 After all SAT has been completed the Vendor/Contractor may be required to conduct a training session to
familiarise the process personnel responsible for the PLC with its operational features.
8.3.7 Other tests may be specified by the Owner as required.
8.3.8 At the completion of both FAT and SAT and commissioning, "As-Built" copies of the programme diskette
shall be produced to reflect programming changes implemented during testing.
9.0 DOCUMENTATION
9.1 Introduction
9.1.1 This section covers the documentation required for the design selection, fabrication, inspection and testing
for the PLC systems.
9.1.2 Documents shall be transmitted to the Owner in both hardcopy format and in 3.5" diskette format.
9.1.3 All logic diagrams shall use logic symbols in accordance with ISA S5.2. The use of other symbols, shall
require Owner's approval.
9.1.4 The following documentation shall be supplied as a minimum to the Vendor/Contractor by the Owner:
- Piping and Instrumentation Diagrams (if required).
- An I/O schedule of all instruments by tag number.
- Cause and Effect Diagrams.
- Binary Logic Diagrams or Process Description.

Rev 0 1999
- Specification for the data to be transmitted to other devices.
9.1.5 The detailed list of documents that are required is included with the Purchase Order/Contract. However, as
a minimum the following documents shall be provided by the Vendor/Contractor in addition to those
specified in Section 9.1 of GES J.12:
- System software listings, fully annotated with all embedded address tag names, address
descriptors, rung comments and network calculations.
- An index of the system database including tag names, descriptors and initial values.
- I/O and internal memory element allocations and cross references.
- Narratives describing the operation and sequence of each network.
- Data on processor loading, spare memory capacity, spare data base capacity and spare power
supply capacity.
- General Arrangement drawings for the system cabinets, consoles and peripherals.
- System block diagram.
- Heat emission calculations.
- Power requirements.
- System cable schedule.
- System interconnection drawings.
- Quality manual.
- Bill of materials.
- System test procedures and dossier.
9.2 Schedules and Reports
9.2.1 The Vendor/Contractor shall submit with his tender a preliminary quality control plan as per Section 7.4 of
this specification.
9.2.2 The Vendor/Contractor shall supply a schedule showing documents for review and approval, proposed
Sub-Contractors and material procurement, and a production/fabrication programme.
9.2.3 The Vendor/Contractor shall incorporate any revisions agreed with the Owner during the enquiry review
stage and submit revised tender documentation for approval.
9.2.4 Monthly reports shall be submitted by the Vendor/Contractor detailing design, procurement, production
and documentation activities.
9.3 Data and Calculations
9.3.1 The Vendor/Contractor shall supply with his tender completed Data Sheets containing all the relevant
information necessary for appraisal of the proposal by the Owner.
9.3.2 All calculations shall be carried out in clear and logical manner. Where conditions involve the use of
formulae or methods not specified in the applicable reference, the source of these formulae or methods
Rev 0 1999
shall be clearly referenced.
9.3.3 Computer calculations will only be acceptable if all input is shown, together with calculated values of
intermediate terms and factors and options chosen, as well as final calculated dimensions, constants or
other values and the computer program has been validated to the satisfaction of the Owner.
9.3.4 Calculations and drawings that are interdependent shall be presented for appraisal together.
9.3.5 Vendor/Contract shall prepare power consumption and heat emission calculations and issue them for
approval to the Owner to enable sizing of the UPS and HVAC systems.
9.4 Drawings
9.4.1 The drawings listed with the Purchase Order/Contract shall be sent by the Vendor/Contractor to the Owner
and/or the Inspection Authority for review and approval.
9.4.2 General arrangement drawings shall be to scale and show the relative location and main dimensions of all
components including elevations and orientations, lifting lugs, nameplates and supports.
9.5 Final Records, Documents and Manuals
9.5.1 Two copies of the Data Dossier shall be supplied, and shall be a record of the manufacturing process. The
contents of the Data Dossier shall be agreed with the Owner but as a minimum shall include:
- general arrangement drawings and bill of material;

- system drawings;
- the Quality Control Plan;
- hazardous area certificates;
- test procedures, and test certificate;
- non-conformity records;
- approvals by the Inspection Authority;
- Certificate of Conformity;
- Owner's Release Certificates.
9.5.2 Six (6) copies of the Installation, Operations and Maintenance Manual (IOM) shall be specifically compiled
for the equipment supplied. A compendium of manufacturer's data for a range of like products is not
acceptable. The IOM shall contain the following:
- a detailed description of the equipment and process measurements and controls;

- the master document list and certified copies of key drawings and documents;
- packing, shipping and site preservation instructions;
- installation instructions;
- pre-commissioning and commissioning procedures;
- start up, operating and shutdown procedures;
- set point values for all instruments;
- list of special tools;
- spare parts ordering information;
- copy of all the configuration programmes and re-programming/configuration procedures.
9.5.3 The part of the IOM relating to the operation and maintenance of the PLC shall contain as a minimum the
following sections:
(a) Overview and General Information: This section shall include the main index, brief description of
the PLC with a system block diagram, the PLC system design philosophy (e.g. failure modes) and
any modification history.
(b) System Start-up and Shutdown Procedures: This section shall include system start-up and
Rev 0 1999
shutdown procedures and list of control setpoints and parameters (if any).
(c) Communications: This section shall include a block diagram showing data communication
overview, network information, list of available reference manuals and cabling and connection
information (pinout, jumpering, shielding requirements, dip switch settings).
(d) Input/Output and Logic Sub-systems: This section shall contain the following information:
I/O and logic sub-systems overview.

I/O cross reference list.
Programme structure overview.
Annotated programme file listing.
Device memory allocation listing.
Programme backup procedure.
List of available reference manuals.
General information e.g. software version, dip switch settings, jumper
configuration, electrostatic damage prevention etc.
(e) Operator Interface: This section shall contain the following:
Overview of the operator's interface.

System screen layout and listing.
Operator keyboard function description.
(f) Reference Documents: This section shall contain equipment manufactures product Data Sheets
together with an index.
9.6 Hazardous Area Certificates
System and device certificates covering the use of the PLC with instruments in hazardous areas shall be
supplied by the Vendor/Contractor.
Rev 0 1999
10.0 PRIOR TO SHIPMENT
10.1 Painting and Coatings
10.1.1 Painting and protective coatings shall take into account the methods of transport to be used.
10.1.2 Surface preparation, painting and painting materials shall be in accordance with GES X.06.
10.1.3 The Vendor/Contractor's standard painting and coating systems may be acceptable subject to Owner's
approval, provided they are equal to or better than the Owner's standards specified in GES X.06 and are
equally suitable for the site environmental conditions specified in GES A.06.
10.2 Spares
The Vendor/Contractor shall submit with his proposal a list of recommended spares for start-up and two
year's operation for review by Owner.
10.3 Packing and Storage
10.3.1 This section describes the minimum requirements for the preservation and protection of the MIS equipment
during the sea and land transportation and storage prior to installation.
10.3.2 The probable storage period will be specified in the order/enquiry and will extend from the time to despatch
to the time of unpacking at site. If the storage period is not stated, a minimum period of 24 months shall be
assumed. Packing to be suitable for sea freight.
10.3.3 The cabinets and cabinet components shall be securely packaged such that they are protected against
external damage during transit.
10.3.4 Cabinets or panels shall be crafted in moisture-proof sealed crates containing a desiccant for seagoing
shipment.
10.3.5 All components with moving or sensitive parts shall be removed from the cabinet prior to shipping, and
shall be suitably packed and shipped separately from the cabinet.
10.3.6 All loose electronic circuit boards and components shall be packaged in sealed, moisture-proof bags. If any
of the electronic circuit boards contain electrostatic sensitive components they shall be packed in
conductive bags with warning labels.
10.3.7 All modules shall be removed from swing frames and shall be suitably packed and shipped separately from
the cabinet.
10.3.8 Swing frames shall be secured so as to prevent their accidental opening, due to vibration, etc. during transit.
10.3.9 The Vendor/Contractor shall ensure that heavy items of equipment, e.g. power supplies, which are
adequately supported during transit.
10.3.10 All loose cables, tubing, etc., which are disconnected for ease of shipment shall be securely tied back and
identified.
10.3.11 Where multiple crates or packages are used, then each shall be individually numbered and the number
clearly marked on the outside of the crate or package. a packing list relating the crate or package number to
the contents shall accompany the consignment.
10.3.12 All open cable entry parts shall be protected by plastic plugs.
10.3.13 The equipment shall be crated to allow movement by forklift, rollers, crane slings, or skidding. The packing
Rev 0 1999
or crating shall provide proper equipment protection, with consideration given to the site environmental
conditions. The Vendor/Contractor's own recommendations shall be considered in this respect.
10.3.14 The crates shall be clearly marked by a warning label together with appropriate symbol indicating the
nature of the contents and balance points. The crates shall be marked to indicate the balance point. The
weight of each crate shall be marked on at least two sides both, in kilogrammes and pounds, in painted
numerals at least 3 inches (75mm) in height.
10.4 Shipping
The panels shall not leave the Vendor/Contractor's works for shipment until the release has been signed by
the Owner's Inspector.
10.5 Service Support
10.5.1 The Vendor/Contractor shall identify in his bid the recommended maintenance and service organisation
nearest the installation site and shall provide details of suitable support related personnel services available
at that location.
10.5.2 The Vendor/Contractor shall also detail in his bid training courses available (at site or at
Vendor/Contractor's works) and their location for personnel who will operate and maintain the MIS system
at site.
10.5.3 The Vendor/Contractor shall provide compatible spares for at least 10 years from product withdrawal. The
Vendor/Contractor shall notify in writing of any product withdrawal at least six months prior to date of
withdrawal.
10.6 Warranty
10.6.1 The Vendor/Contractor shall warrant all materials and services supplied, against any defect, for a minimum
period of 12 months after commissioning or 24 months from the date of delivery to the site, whichever is
the shorter period, or for the period stipulated in the Purchase Order/Contract.
10.6.2 Should any item be found defective, the Vendor/Contractor shall be responsible for all costs associated
with restoring the equipment to the standard specified in the Purchase Order/Contract. The
Vendor/Contractor shall undertake to carry out the repair or replacement in an expeditious manner.
10.6.3 The terms and conditions of this Warranty shall be additional to any other requirements specified in the
Purchase Order/Contract.
10.6.4 Hardware and software warranty shall be provided for a period of one year after successful completion of
the SAT and sustained performance test or 2 years from delivery to site whichever is sooner.
10.6.5 Any software remedial action during the normal warranty period shall carry a further one year warranty.
However, the total period shall not exceed a period of three years from takeover.
10.6.6 Acceptance of the system by the Owner shall not release the Vendor/Contractor of any warranties,
responsibilities or obligations to furnish equipment and materials in accordance with this specification.
10.6.7 The Vendor/Contractor shall state in his bid if the warranty is valid for direct purchase only or whether it
can be transferred to the Owner.
10.6.8 The Vendor/Contractor shall state the warranty coverage period if it is other than 24 hours all year around
basis.
10.6.9 Notwithstanding any maintenance or license agreement between the Vendor/Contractor and the Owner, the
Vendor/Contractor shall make available to the Owner a secure copy of all source codes for the lifetime of
Rev 0 1999
the plant. The source code shall be kept in a safe at the Vendor/Contractor's offices and in the event of the
failure the Vendor/Contractor shall be expected to supply this to the Owner free of charge.
10.6.10 The Vendor/Contractor shall provide a quotation for an extended on-site warranty/on-site maintenance
contract.
DATA SHEET No.
PLC - INPUT / OUTPUT SCHEDULE

P.O. / CONTRACT No.
CLIENT
PLANT LOCATION SHEET 1 of 1
SERVICE ITEM No. No. of UNITS
1 VENDOR / CONTRACTOR
2 Notes
3 Input or Output
4 Circuit Tag Number
5
6 Category 1
7 Type 2
8
9 Field Powered 3
10 Intrinsically Safe
11 Signal Line Monitored 4
12
13 Range & Units 5
14 Set Points LOW
15 Status or Alarm HIGH 6
16 Alarm (Input State)
17 A Status
18 S Trip
19 S Totalise
20 I Logic
21 G Calculate
22 N Print
23 M
24 E Voltage
25 N
26 T Control
27 Repeat on
28
29
30
31 Termination Drawing
32 Loop Drawing
33
34
35 Remarks
36
37 Notes: 1. CATEGORY SPECIFY CONTACT STATE, NORMALLY OPEN OR NORMALLY CLOSED
38 2. TYPE SPECIFYS ANALOGUE OR DIGITAL, INPUT OR OUTPUT
39 3. FIELD POWERED MEANS THAT LOOP POWER SUPPLY IS EXTERNAL TO PLC
40 4. MONITORED MEANS THAT SIGNAL LINE IS MONITORED FOR FAULT CONDITIONS
41 5. RANGE AND UNITS, APPLICABLE TO ANALOGUE SIGNALS ONLY E.G. 4 to 20mA = 0 to 200 GPM
42 6. STATUS OR ALARM SETPOINT LEVEL OF ANALOGUE INPUT SIGNAL E.G. HIGH ALARM AT 15 mA LOW ALARM AT 6mA
43
44
45
Revision No./Date
Prepared by/Date
Authorised by/Date
Purpose
(C) 1999 NATIONAL OIL CORPORATION. The information on this sheet may be used only for the purpose for which it is supplied by NOC.
K:\nocspecs\SPECIFICATIONS\j-series\j-21\dj2101r0.xls Sheet1
DATA SHEET No.
DATA INTERFACES AND PROTOCOL

P.O. / CONTRACT No.
CLIENT
PLANT LOCATION SHEET 1 of 1
SERVICE ITEM No. No. of UNITS
1 VENDOR / CONTRACTOR
2
3 Interface Data Remarks
4 Data source device
5 Model number
6 Data destination device
7 Model number
8 Data base I.D.
9 Protocol / synchronous / asynchronous
10 Version No.
11 Protocol commands / functions
12 Electrical connections RS 232 / 422 / 485 etc.
13 Single / multi-drop
14 Master slave / peer to peer
15 Transmission media
16 Copper / Co-axial / fibre optic
17 Baud rate
18 Number of data bits
19 Number of start bits
20 Number of stop bits
21 Parity type / method
22 Address of source device
23 Comms board / port device
24 Comms board / port number
25 Maximum distances between devices
26 Buffer size
27 Length of message
28 Type of handshake
29 Comms card switches
30 Comms cable wiring diagram
31 Double buffering required
32 Source / target registers
33 Specific protocol requirements e.g. set flags for new data etc.
34 after reading, 16 or 32 bit
35 data, single / double precision
36 IEEE 64 bit floating point etc.
37 Data blocking details
38 Link master
39 Level of redundancy
40 Protocol deficiency / limitations
41 Remarks / comments
42
43
44
45
Revision No./Date
Prepared by/Date
Authorised by/Date
Purpose
(C) 1999 NATIONAL OIL CORPORATION. The information on this sheet may be used only for the purpose for which it is supplied by NOC.
K:\nocspecs\SPECIFICATIONS\j-series\j-21\dj2102r0.xls Sheet1

National Oil Corporation: Rev Date Description Checked Approved

Uploaded by

Copyright:

Available Formats

National Oil Corporation: Rev Date Description Checked Approved

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

National Oil Corporation: Rev Date Description Checked Approved

Uploaded by

Copyright:

Available Formats

NATIONAL OIL CORPORATION

GENERAL ENGINEERING SPECIFICATION

PROGRAMMABLE LOGIC CONTROLLERS

Rev Date Description Checked Approved

Compiled by Teknica (UK) Ltd

SEC TITLE PAGE

1.0 SCOPE OF SPECIFICATION 4

3.1 Codes and Standards 7

5.1 Cabinets and Enclosures 21

6.0 SITE PREPARATION AND INSTALLATION 22

8.1 Test Procedures 25

10.0 PRIOR TO SHIPMENT 33

10.1 Paintings and Coatings 33

DATA SHEETS (2)

1.2 Other NOC Specifications

GES A.06 Site Data

GES B.01 Central Control Buildings

GES C.54 Commissioning of Micropressor Based Instrument Systems

GES J.12 Indoor Control Panels and Cabinets

GES J.16 Instrument Cable and Cabling

GES J.17 Earthing of Instrument Systems

GES J.19 Annunciators

GES L.07 A.C. Uninterruptable Power Supplies (UPS)

GES L.35 Electrical Equipment in Hazardous Areas

GES X.06 Factory Coatings for Electrical Equipment and Instruments

The technical terms used in this specification are defined as follows:

To re-establish normal control of a disabled logic coil or discrete output.

PLC system inputs or outputs connected to field elements.

Programmable Logic Controllers

Programme Scan Time

CCR Central Control Room

The commercial terms used in this specification are defined as follows:

The company supplying the equipment and material.

The main Contractor for a defined piece of work.

3.1 Codes and Standards

American Petroleum Institution (API)

API 554 Process Instrumentation of Control

British Standards Institution (BSI)

BS 5515 Code of Practice for Documentation of Computer Based Systems

BS 5760 Reliability of Systems, Equipment and Components

Part 2 - Guide to Assessment of Reliability

BS 7671 Requirements for Electrical Installations

Electronic Industries Association (EIA)/CCITT Recommendations.

RS 422 Electrical Characteristics of Balanced Voltage Digital Interface Circuits

International Electrotechnical Commission (IEC)

IEC 60068 Part 1 Environmental Testing - General and Guidance

IEC 60529 Degrees of Protection Provided by Enclosures (IP Code)

Instrument Society of America (ISA)

ISA S 5.1 Instrumentation Symbols and Identifications

ISA S 5.2 Binary Logic Diagrams for Process Operations

ISA S 5.3 Graphics Symbols for Distributed Control/Shared Display Instrumentation,

ISA S 18.1 Annunciators - Sequences and Specifications

International Standards Organisation (ISO)

ISO 9001 Quality Systems - Model for QA in Design/Development, Production,

3.2 Environmental Conditions

3.3 Noise Limits

3.4 Hazardous Area Classification

3.5 Eletromagnetic Interference