NIOEC-SP-70-24(0)

DOCUMENT CODE NO. OF PAGES: 18

PLAN/PRJ/SUB UNIT PHASE DISCIPLANE DOCUMENT TYPE SERIAL NO. REV. NO. DATE
NIOEC 000 EG IN SP 7024 A0 DECEMBER 2017

NATIONAL IRANIAN OIL REFINING & DISTRIBUTION COMPANY

NATIONAL IRANIAN OIL ENGINEERING
& CONSTRUCTION COMPANY

NIOEC SPECIFICATION
FOR

SUPERVISORY CONTROL AND DATA

ACQUISITION SYSTEM
(SCADA)

FIRST EDITION

DECEMBER 2017

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.
 DECEMBER, 2017 NIOEC-SP-70-24 (0)

IN THE NAME OF GOD

FOREWORD

By their very nature, technical Specifications are continuously subject to modifications and
revisions. To strengthen their merit and usefulness, continuous improvements, addendum, deletion
of disparate information and consequently provision of updated revisions are to be made in order
to ascertain that such Specifications meet the current requirements, inclusive of Iranian Petroleum
Standards (IPS) and the recognized and acceptable national and international Standards, as well as
the optimal codes and practices based on the accumulated in-house know-how and plant
knowledge and experiences.

However, in reality, due to several reasons, not to mention the complexity of the matter, the
ultimate goal of continuous direct embedment of the required changes on the relevant
Specifications may be far reaching. Therefore, in the interim periods between the officially issued
revisions, the required changes will appear in other documents related to the engineering and
design work of the ongoing projects.

In response to the initiative of the Design and Engineering Directorate, and considering that the
task of the execution of several important and mega projects for the realization of the new oil
refineries, pipelines and oil terminals as well as improvements of the existing facilities, has been
assigned to NIOEC, it was decided to update the NIOEC Specifications and to issue new official
revisions.

The Design and Engineering Directorate was itself entrusted to carry out this important task, and
as such by forming several special technical committees, working in close co-operation and
cohesion and sharing their expertise and knowledge, the updated and revised NIOEC
Specifications were successfully prepared and complied.

These Specifications are intended to be used for Oil Refineries, Distribution Depots, Oil
Terminals, Pipelines and Pump Stations within NIOEC's projects, and have been proven to be of
high value for such purposes. It must however be appreciated that these Specifications represent
the minimum requirements and should in no way be interpreted as a restriction on the use of better
procedures, engineering and design practices or materials.

We encourage and highly appreciate the users and other clear sighted and experts to send their
comments on the Specifications to the Design and Engineering Director of NIOEC for evaluation
and approval.
 DECEMBER, 2017 NIOEC-SP-70-24 (0)

REVISION INDEX
REV. REV. REV. REV.
PAGE 1 2 3 4 5 PAGE
1 2 3 4 5 PAGE 1 2 3 4 5 PAGE 1 2 3 4 5
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) WHEN APPROVED EACH REVISION SHALL BE CONSIDERED AS A PART OF THE ORIGINAL DOCUMENT.
3) NUMBER OF PAGES EXCLUDES THIS SHEET AND THE COVER SHEET.

5
4
3
2
1
0 DECEMBER 2017 A. MOGHADAM G.R. MOHSENI M.R. FARZAM M. KARGARNAJAFI

REV. DATE PREPARED CHECKED APPROVED AUTHORIZED

 DECEMBER, 2017 NIOEC-SP-70-24 (0)

CONTENTS: PAGE NO.

1. SCOPE .........................................................................................................................................3
2. REFERENCES ...........................................................................................................................3
3. UNITS ..........................................................................................................................................4
4. ABBREVIATIONS .....................................................................................................................5
5. PRODUCT HISTORY ...............................................................................................................5
6. CERTIFICATION AND APPROVALS...................................................................................5
7. UTILITY AND ENVIRONMENTAL REQUIREMENTS ....................................................5
7.1. Electrical Power ...................................................................................................................5
7.2. Environmental Data ............................................................................................................6
7.3. Ingress Protection and Hazardous Area Classification ...................................................6
7.4. Electromagnetic Interference .............................................................................................6
8. SYSTEM DESIGN REQUIREMENTS ....................................................................................6
8.1. Design Principles..................................................................................................................6
8.2. Hardware ..............................................................................................................................7
8.3. Software ................................................................................................................................7
8.4. OPC Client and Server Interface .......................................................................................7
8.5. Capacity ................................................................................................................................8
8.6. Performance .........................................................................................................................8
8.7. SCADA Redundancy ...........................................................................................................8
8.8. SCADA System Backup ......................................................................................................8
8.9. SCADA Interface with Third Party Subsystems ..............................................................9
8.10. SCADA Diagnostics.............................................................................................................9
8.11. TIME TAGGING ................................................................................................................9
8.12. CONFIGURATION ............................................................................................................9
9. COMMUNICATIONS .............................................................................................................10
10. CABINET ..................................................................................................................................10
11. CABLING ..................................................................................................................................10
12. DOCUMENTATION ...............................................................................................................11
12.1. Introduction.........................................................................................................................11
12.2. Design Documents ...............................................................................................................11
13. INSPECTIONS AND TESTING .............................................................................................11
13.1. General.................................................................................................................................11
13.2. Factory Acceptance Test (FAT).........................................................................................11
13.3. Tests Records ......................................................................................................................13
14. INSTALLATION, START UP AND COMMISSIONING ...................................................14
14.1. Installation ...........................................................................................................................14
14.2. Checks ..................................................................................................................................14
14.3. Power up ..............................................................................................................................14
14.4. SAT.......................................................................................................................................14
14.5. On Site Supervision ............................................................................................................14
14.6. Commissioning ....................................................................................................................14
14.7. Test Equipment ...................................................................................................................14

1
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
14.8. Documents ...........................................................................................................................14
15. SPARES PARTS SUPPLY ......................................................................................................15
15.1. Pre-commissioning and Commissioning Spare Parts ......................................................15
15.2. Spare Parts for Two Years of Operation ..........................................................................15
15.3. Maintenance Tools ..............................................................................................................15
16. TRAINING ................................................................................................................................15
17. PACKING AND SHIPMENT .................................................................................................15
18. GUARANTEES.........................................................................................................................16
APPENDIX I: VENDOR’S DOCUMENT SUPPLY (VDS) ........................................................17
APPENDIX I: VENDOR’S DOCUMENT SUPPLY (VDS) (Coun.) ..........................................18

2
 DECEMBER, 2017 NIOEC-SP-70-24 (0)

1. SCOPE
This specification defines NIOEC’s minimum requirements for a Supervisory Control and Data
Acquisition (SCADA) system.
Deviations from this specification will only be permitted on obtaining written approval from
NIOEC.
Resolution on cases not explicitly stipulated in this Specification, or on cases where conflicts may
arise among the requirements of the referenced IPS and the international standards, shall be made
through written consent and approval of NIOEC.

2. REFERENCES
The following standards, codes, and specifications, to the extent specified hereinafter, shall
constitute a part of this NIOEC Specification. Latest edition of the undated referenced documents
and the cited edition of the dated references shall apply. The applicability of changes made to the
dated references, after the cited date shall be mutually agreed upon between NIOEC and the Vendor
/Contractor.

API (AMERICAN PETROLEUM INSTITUTE)

API STD 1164 “Pipeline SCADA Security”

EN (EUROPEAN STANDARDS)
EN 55022 “Information Technology Equipment – Radio Disturbance
Characteristics – Limits and Methods of Measurement”
EU (EUROPEAN UNION)
EMC- Directive 2014/30/EU “European Union EMC Directive”

IEC (INTERNATIONAL ELECTRO-TECHNICAL COMMISSION)

IEC 61000-4 “Electromagnetic Compatibility (EMC)”
IEC 61499-1 “Function Blocks- Part 1: Architecture”
IEC 61499-2 “Function Blocks- Part 2: Software Tool Requirements”
IEC 61158-2 "Industrial Communication Networks- Field bus Specification,
Part 2: Physical Layer Specification and Service Definition”
IEC 61131-3 “Programmable Controllers- Part 3: Programming Language”
IEC 60332 “Test On Electric and Optical Fibre Cables under Fire
Conditions”
IEC 60529 “Degree of Protection Provided By Enclosures (IP Code)”
IEC 60068 “Basic Environmental Testing Procedures”
IEC 60605 “Equipment Reliability Testing”
IEC TR 62380 “Reliability Data Handbook– Universal Model for Reliability
Prediction of Electronics Components, PCBs and Equipment”

3
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
IEEE (INSTITUTE OF ELECTRICAL & ELECTRONICS ENGINEERS)
IEEE C37.90.1 “Surge Withstand Capability (SWC) Tests for Relays and
Relay System Associated With Electric Power Apparatus”

ISA (INSTRUMENTATION, SYSTEM, AUTOMATION SOCIETY OF AMERICA)

ISA 5.1 “Instrument Symbols and Identifications”
ISA 5.2 “Binary Logic Diagrams For Process Operations”
ISA 5.3 “Graphic Symbols For Distributed Control/Shared Display
Instrumentation, Logic and Computer Systems”
ISA 5.4 “Instrument Loop Diagrams”
ISA 18.1 “Annunciator Sequences and Specification”

ISO (INTERNATIONAL STANDARD ORGANISATION)

ISO 9000 “Quality Management Systems”

NFPA (NATIONAL FIRE PROTECTION ASSOCIATION)

NFPA 70 “National Electrical Code”

NIOEC SP (NIOEC SPECIFICATIONS)

NIOEC-SP-70-01 “Specification for Instrumentation”
NIOEC-SP-70-21 “Specification for Programmable Logic Controllers (PLC)”
NIOEC-SP-00-10 “Specification for Units”
NIOEC-SP-70-05 “Specification for Instrumentation Control Cables, Cable
Trays, Conduits, Junction Boxes And Cable Glands”
NIOEC-SP-70-54 “Specification for Telecommunication Cables”

TIA (TELECOMMUNICATION INDUSTRY ASSOCIATION)

TIA -485 “Electrical Characteristics of Generators and Receivers for
Use in Balanced Digital Multipoint Systems”

U.S. MIL HDBK (U.S. MILITARY HANDBOOK)

MIL-HDBK-217 “Reliability Prediction of Electronic Equipment”
MIL-HDBK-472 “Maintainability Prediction”

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

4
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
4. ABBREVIATIONS
CPU: Central Processing Unit
I/O: Input/ Output
MTBF: Mean Time Between Failures
MTTR: Mean Time To Repair
MTU: Master Terminal Unit
OPC: Object Linking and Embedding for Process Control
PC: Personal Computer
PLC: Programmable Logic Controller
RTU: Remote Terminal Unit
SAT: Site Acceptance Test
SCADA: Supervisory Control and Data Acquisition System
SOE: Sequence of Events
UPS: Un-interruptible Power Supply
VDU: Visual Display Unit

5. 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.

6. CERTIFICATION AND APPROVALS

The equipment shall bear CE marking in accordance with EMC-Directive 2014/30/EU, and the
conformity certificates shall be provided.
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.

7. UTILITY AND ENVIRONMENTAL REQUIREMENTS

7.1. Electrical Power
The central equipment shall be powered from dual redundant Un-interruptible Power Supplies
(UPS). The UPS shall 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 backup 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.
For remote equipment, electrical power supply shall be provided from commercial power with
adequate battery back-up. If the equipment be installed in remote areas with no electrical
supply, vendor shall design and supply reliable solar panel based power supplies with adequate
battery back-up on obtaining written approval from NIOEC.

5
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
7.2. Environmental Data
Indoor temperature and humidity (RH) will be 23 C ± 3C and 30% to 65% respectively and
shipping and storage conditions will be considered as -20 C to 65 C and 0% to 100%.
However, as a minimum the following operating conditions shall not degrade the continuous
operation of the System:
 Min/max temperature: 0C to 40 C
 Min/max humidity: 20% to 90% RH non-condensing
 Suspended Solids as dust and sand.
Allowable indoor noise level shall be 55 dBA, measured at one meter from equipment in
question.

7.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. Local panels located in hazardous area, where
no air-conditioning is practicable, shall only be pressurized.
Indoor stations and System cabinets shall conform to IEC 60529, IP 42, as a minimum.
Outdoor equipment shall be watertight to IEC 60529, IP 65 as a minimum. Large size outdoor
local panels, for which IP 65 may not be applicable, shall be pressurized.
Electrical accessories, cabling and junction boxes in hazardous areas shall normally be of
intrinsically safe construction and execution suitable according to hazardous area classification.

7.4. Electromagnetic Interference

Equipment shall meet all electromagnetic compatibility requirements of the IEC 61000-4.

8. SYSTEM DESIGN REQUIREMENTS

8.1. Design Principles
Each of RTUs and MTU shall be designed to achieve a high level of availability, reliability and
safety in operation. The design shall be ‘fail safe’ such that failure of any component shall
result in all functions affected by the failure defaulting to a defined safe state. It shall be fault-
tolerant such that the failure of any single component within the overall system shall not affect
the ability of the remaining healthy components in the system to continue to operate normally
and for its functionality to remain available.
Essential functionality that required for the continued overall operation of the RTU/MTU shall
be tolerant to single component failures. This may be achieved, for example, by using
redundant hot/standby arrangements or by automatically re-distributing the functionality over
the remaining operational components so that loss of any one component does not result in the
loss of any functionality.
The system shall continuously monitor its own health and produce alarms for all detected
failures. There shall be no case in which undetected failures could occur anywhere within the
overall RTU or MTU.
The enclosures and the equipment which is mounted in cabinets shall be designed to facilitate
ease of maintenance, particularly fault-finding and replacement of components, e.g.
replacement of rack mounted circuit cards. As far as possible, and consistent with safe
operation, it shall be possible to ‘hot swap’ components such as I/O cards.

6
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
The equipment shall be robust, suitable for the operating environment in which it is installed
and require minimal maintenance.
Each sub-system within the RTU/MTU shall be designed to meet an overall availability of at
least 99.95 percent based on a Mean Time to Repair (MTTR) of 4 hours.
Availability calculations shall be according to MIL-HDBK-217E or IEC TR 62380 based on a
minimum configuration of the following items:
 All controllers are operational with no more than a single I/O module failure.
 All control functions available.
 All modules shall have an MTBF of more than 10,000 hour.

8.2. Hardware
The design of all RTU equipment shall be such as to ensure satisfactory operation in an
electrically hostile environment typical of high voltage electrical installations, as RTUs are to
be installed at Cathodic Protection Stations where there exist Electrical panels/feeders.
The RTU/MTU equipment shall be of rack mounted modular construction. All computer
equipment shall be supplied with a real-time multi-tasking operating system which conforms to
a recognized industry standard and not unique to one manufacturer. Interconnecting cables
shall be made via substantial, secure plugs and sockets, which shall be mounted in accessible
positions and clearly labelled.
Each functional module in MTU/RTU shall be a self-contained I/O device. The module shall
contain all the hardware and firmware required to provide the specific functions for which it is
designed. So, adding a module to an existing MTU/RTU becomes as simple as plugging it in
and wiring it to the Client's control panel. All racks of I/O signal modules shall be completely
expandable for accommodating future possible instrument signals.
All RTU's contain two required base modules: the power supply module and the optical fibre
interface module. Both of these modules shall be redundant. MTU and RTU's shall be smart;
capable of accomplishing fast local scans of the instrumentation measurements.

8.3. Software
The software shall be of modular construction, developed using structured design. Techniques
are written in a commonly used programming language, where possible, standard library
software shall be utilized. The Supplier shall identify all standard proprietary software and any
software specially developed for the project.
The application software shall ensure the secure execution of RTU/MTU functions.

8.4. OPC Client and Server Interface

The system shall have capabilities of acting as an OPC client as well as an OPC server. As an
OPC Client, the system must be able to collect data from third party OPC data collection
servers. As an OPC Server, the software system must be able to share the data and information
it manages with other third party programs.
The software system shall support an OPC Data Acquisition and Alarm and Events interface in
both client and server modes. In the server mode, OPC aware applications (clients) should be
able to access data managed by the system. The OPC client interface shall support the use of
third party OPC device communication servers. The OPC server interface should allow for

7
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
point information collected and maintained by the software system to be sent to OPC
applications requesting the data.
The OPC client should allow for browsing of available OPC servers and the published points.

8.5. Capacity
The Vendor shall provide capacity and technical details of the following:
 CPUs
 Memory (all types)
 Real time clock
 Communication port data rates and format (all types)
The RTU/MTU shall be designed, delivered and commissioned with sufficient capacity for
performing the requirements of this specification and the specific operational data required at
the specific site, as determined by the site survey process, and in agreement with the Client’s
Representative.
No more than 70% of the available memory and solid state disc shall be utilized during normal
system operation.
The spare capacity shall allow on site development and modification without major changes to
the hardware, software and System configuration. Approximately 10% spare input/output
capacity shall be provided. These spare facilities shall be fully fitted and prewired.
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 which shall be 30% as minimum.
System expansion shall be achievable without shutting down the regulatory controllers not
directly involved with the expansion.

8.6. Performance
The RTU shall process all information required to be transmitted to the Master Station (MTU),
and the SCADA, and have it available for transmitting within one second. The RTU shall be
capable of handling all alarms and status changes occurring during occurrence of a fault on
electrical power supply.

8.7. SCADA 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:
 CPU
 Power Supply
 Communication Interface Module

8.8. SCADA 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.

8
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
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
safely protected flash memory devices magnetic or optical media.

8.9. SCADA 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 SCADA, 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 or other industry standard. The vendor shall have interface ports that
support serial links/Ethernet link at the Control Module level and shall provide the driver
software.
The SCADA shall perform memory mapping of the sub-system, and achieve seamless
integration between the SCADA database and sub-system.

8.10. SCADA Diagnostics

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.

8.11. TIME TAGGING

Certain status signals may be configured for local time tagging to be applied at the RTUs.
These events shall be reported to the master station (MTU) with a time tag embedded in the
message. The Vendor shall provide details of the following:
a) Time tagging resolution at the RTU/MTU
b) Method of synchronizing the RTU's real time clock to the master clock
c) Method of transmitting time tag information with event data to the master station (MTU)
d) Means of selecting events for time tagging and the maximum number definable at each
RTU
e) Method of handling overflow of SOE data at the RTU

8.12. CONFIGURATION
All RTU/MTU configuration data shall be held in alterable non-volatile memory so that the
RTU can re-initialize itself automatically. Vendor shall state the method by which
configuration data is loaded into the RTU/MTU. The preferred method is by downloading the
configuration data from the master station. If this is not a standard feature of the Vendor’s
product, it may be offered as an option.

9
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
If the RTUs are configured on site, Vendor shall describe how this is achieved and shall
include any equipment required for this function in their offer.
The master station database shall be kept updated with the current configuration data for each
RTU. Vendor shall state how this is achieved.

9. COMMUNICATIONS
The RTU shall be designed and equipped to communicate with the master station via the optical
fibre communication link. As a minimum, the remote communications interface (used in
transferring data between RTU's and MTU through optical fibre media) shall support TCP/IP
protocol. The Vendor shall provide details of the communication protocols supported by their
system. The Contractor is responsible for providing all necessary equipment required to achieve
such connections.
The protocol used by the Master Station to interrogate the RTU shall feature positive confirmation
to the RTU that information transmitted by the RTU has been received by the Master Station. The
RTU shall keep a copy of each set of data that it attempts to transmit until positive confirmation of
its delivery to the MTU is received.
Where available, the Contractor shall provide dedicated optical fibre link between the RTUs and
Master Stations (MTUs). Otherwise, the Contractor shall provide standard communication
equipment to provide communication link over the Owner’s communications network.
The Vendor shall state what arrangements of communications links the equipment can support.
The communication interface shall support redundant communication links between RTUs and
MTUs and have the ability to automatically change to a healthy link if one link should fail.
The Master Station (MTU) shall communicate with upper systems like Control System, Leak
Detection System etc via a dedicated Industrial Ethernet card (TCP/IP protocol) or Serial port
utilizing OPC to yield all required information for those systems. In order to present information to
Owner's SCADA which may be installed at a same or a far location in relation to MTU, provision
for both standard serial link and optical fibre link module shall be taken in MTUs.
The telemetry system shall utilize open industry non licensed standard communications protocol
that will permit interface with other equipment that may not be supplied by the same manufacture.
Protocols that are proprietary and closed ended will not be acceptable. Upon request by the end
user, the system Vendor shall provide, to the owner, documentation describing the supplied
communications protocol so that it may be used in future telemetry additions to insure interface-
ability of other third party RTUs and or PLCs.
The PLC system shall allow local or remote configuration or RTU troubleshooting without the need
to be onsite. The system protocol shall support remote upload and down load file transfers between
the master unit and associated RTUs.

10. CABINET
NIOEC-SP-70-14 shall be followed.

11. CABLING
NIOEC-SP-70-05 and NIOEC-SP-70-54 shall be followed.

10
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
12. DOCUMENTATION
12.1. Introduction
The documentation to be supplied with the equipment shall be sufficient to operate, maintain,
repair and reconfigure the hardware and software throughout the operational lifetime of the
System. Document types are specified in Appendix I; 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 Client. 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 Client.
The Vendor shall produce unique drawings and documents for those items on the VDS, which
are identified as for Client approval. The Vendor may submit standard drawings and
documents for other category items on the VDS.
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 on solid state
media.

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 Client’s inspectors will witness the tests.

13.2. Factory Acceptance Test (FAT)

13.2.1. Introduction
The tests shall demonstrate the functional integrity of all hardware and software. Client’s
assigned inspectors shall inspect the performance of all tests and they shall have access right
to all facilities involved in the manufacturing of the equipment purchased under this
specification. The vendor shall maintain and/or replace any hardware or modify the
software, if the specified functions are not satisfactorily performed in Factory Acceptance
Test on the Client’s inspector judgment. A detailed factory test procedure shall be submitted
in the bid proposal by Vendor and shall be agreed upon before starting the test. Vendor shall
provide all necessary personnel and test equipment to perform the tests as and when required
with the costs included in the bid price and separately indicated.
13.2.2. The Basic Goals
 To confirm proper design and implementation, demonstrating to the Client’s inspector that
the system meets the Client’s specifications.
 To establish that the system performs properly under load and under conditions of stress.
 To confirm proper system configuration and organization. This may involve; setting
program priorities (for example, which program runs first when several should be run),
interconnection of system modules, etc.

11
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
 To look for unanticipated interaction between modules, such as; those which might be
caused by two programs inadvertently sharing the same memory location for different
data.
13.2.3. Quality Assurance Tests
 Quality control shall be as per manufacturer’s quality control standard to assure the good
performance of components/ modules used in the system.
 The sampling procedure for the tests will be defined by Clients assigned inspectors.
 The Vendor shall perform all routine tests on the modules in the system or a subsystem
prior to power-up of the system.
 Functional tests for the system may be performed as a rehearsal for the Factory
Acceptance Test at this stage.
Structural tests shall be performed to find defects in isolation and concentrates on missing
paths, wrong paths, and wrong actions within and between software modules. These tests
shall be performed by Vendor’s engineers and programmers intimately involved in the
design and implementation of the system and inspected by Client’s representative.
Functional and structural tests are both required to prove that a control system works
correctly. Structural tests shall be done as the software modules are coded, whereas function
tests shall be performed after the system or the major subsystem is integrated. The final
testing of the total system shall be functional.

13.2.4. Procedures for Factory Acceptance Test

 The factory acceptance tests shall be performed when all the application software and data
bases have been coded and installed and the structural tests of individual modules have
been successfully completed.
 The testing shall be performed with simulation system.
 The Client’s assigned inspector will perform this phase of the test and shall be applied to
all hardware and software of the system. The necessary workmanship and co-operation
shall be provided by the Vendor, in addition to all measuring instruments. All the
subsystems shall be interconnected as per-actual interconnecting configuration in the field.
13.2.5. Requirements of Final Factory Acceptance Test
The following paragraphs describe requirements for testing to be performed by Vendor and
witnessed by the Client’s assigned inspectors. Client’s inspectors shall have the right to
perform any test, request for repeat of performing of any test, or request for additional test as
included in the Vendor’s approved proposal test procedure.
13.2.5.1. Visual and Mechanical Tests
Client’s inspectors will carry out visual and mechanical testing principally to assure;
correct, proper, and good workmanship of the equipment.
13.2.5.2. Functional tests
When all procedures mentioned heretofore has been met, as a minimum, and all utility
programs loaded, testing shall proceed preferably with the following steps:
First, the ability of the system to correctly read the field inputs must be confirmed.
Secondly, these inputs shall be manipulated, preferably by appropriate signal sources
connected to the input terminals, and proper operation of the interlock levels checked.

12
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
The ability of the operator to access the system will be very important at the computational
safety level. The interlocks at this level which may have multiple operating modes shall be
tested separately.
The proper operation on the regulatory level shall be checked by suitable tester and by
changing the set-points and other directives, through the operator interface.
Outputs to files for logging and reporting shall be tested; the logging and reporting
programs themselves may be tested later, independently, after it is confirmed that the data
received from the logic are correct.
All process and equipment failure must be simulated and tested during this period, since
many failure conditions are difficult and/or time consuming to simulate when the system
is connected to the actual process for the field acceptance test.
13.2.5.3. Test plan schedule
 The Vendor shall submit the test plan at a suitable time before starting of the test. The
test plan shall demonstrate the properly execution of the functions, features,
performance, and reliability of the system. The tests shall avoid non relevant duplication
and shall provide greatest coverage with fewer test cases.
 Plans are required for both structural and functional tests. The plans should specify the
sequence in which a module or a function is to be tested, the required inputs and the
anticipated results.
 The plan for the structural test shall cover all possible paths of logic in a module, and an
appropriate subset or combinations of the logic paths, by the Vendor’s designer and
programmers’ judgment.
 Client’s representative shall witness all structural tests performed on the modules at any
stage of manufacturing. Therefore, the test plan shall be suitably timed, to enable the
Client’s representative to take part in the tests.

13.3. Tests Records

Each test carried out shall be formally recorded. Any deficiency or problem found in
equipment shall be corrected by the Vendor and exactly recorded. Any changes in
configuration, software or data shall be clearly recorded in test log books.
13.3.1. Performance Test
 After completion of tests mentioned here-above, the entire system shall be remained
energized for 72 hours continuously, with hands-off the system. The system performance
for given simulated I/O shall be observed during these 72 hours.
 Any malfunction of any kind shall be noted as observations in the Final Acceptance Test
report and submitted to the Client for decisions.
13.3.2. Configuration Documentation
All the latest changes in programs and data-bases, as performed during acceptance test shall
be transferred to solid state drive (four copies). Two copies shall be shipped separately by
express mail to Client and two other copies shall be shipped with the system.

13.3.3. Final Conclusion of Tests

The Client’s assigned inspectors shall sign all factory acceptance test (FAT) reports and log
books and consequently issue a certificate of shipment on satisfactory completion of

13
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
witnessing tests. Vendor shall properly pack the system according to shipping instructions
and packaging specifications furnished to him by Client and forward all equipment to the
Client’s site.

14. INSTALLATION, START UP AND COMMISSIONING

14.1. Installation
Client 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 all vendor standard hardware,
software and communication.

14.4. SAT
Vendor specialists shall perform Site Acceptance Test (SAT) for Client’s approval. Full
functional test shall be carried out at this stage.

14.5. On Site Supervision

The Contractor shall provide experienced personnel to supervise, perform, and coordinate the
installation, adjustment, testing, and start-up of the SCADA system. The personnel shall be
present on-site as required to affect a complete and operating system.

14.6. Commissioning
Vendor may be required to provide a site-based specialist to assist the Client during
commissioning.

14.7. Test Equipment

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

14.8. Documents
The Vendor shall provide agreed as-built documents and drawings following site
commissioning.

14
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
15. SPARES PARTS SUPPLY
15.1. Pre-commissioning and Commissioning Spare Parts
Vendor shall recommend the spares for pre-commissioning and commissioning 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 two years of operation and provide a price
list. Client 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.

16. TRAINING
Vendors shall provide training courses for Client 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 workshop to receive their respective training.

17. PACKING AND SHIPMENT

The Vendor shall be entirely responsible for the adequacy of the packing for shipment and storage
on site.
During loading the vendor shall witness the loading and bracing to satisfy himself that all
reasonable precautions have been taken to prevent damage occurs during transit.
Preparation for shipment and packing will be subject to inspection and rejection by Client's
inspectors. All costs occasioned by such rejection shall be to the account of the vendor.
The vendor shall comply with the preservation and packing specification and the marking,
documentation and dispatch instructions after satisfactory completion of all tests and inspections.
The vendor shall take all precautions deemed necessary for protection during shipment and
additionally during storage in a marine environment including the following:
A desiccant shall be provided inside all enclosures to prevent damage by high humidity.
The vendor shall supply a recommended procedure for long-term storage (up to 12 months) with the
quotation.
Equipment shall be suitably packed including any dismantling, transit fastening and bracing
necessary to prevent distortion or damage during shipment.
Each individual carton or box shall be marked with the equipment tag number on the top and side of
the carton.

15
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
Vendor shall submit in details, the packing specification and the relevant standards for Client's
approval.
No items of equipment shall be shipped without the Client's prior approval.

18. GUARANTEES
Vendor shall guarantee to support and supply spare parts for the supplied hardware, software and
firmware for at least 10 years from the date of shipment.
If it is expected that parts of the system will be withdrawn from sale after 10 years, Vendor 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.

16
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
APPENDIX I

VENDOR’S DOCUMENT SUPPLY (VDS)

Documents Documents
Documents After
With After
Purchase Order
DESCRIPTION Quotation Finalisation
Quantity Issue Quantity Quantity
Type Purpose and 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 Transportation FI 2C 2C+1R
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 Instructions FI 2C 2C+1R
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

7.1. Drawing & Document List FA 2C 2C+1R
7.2. Power Consumption List and Heat Dissipation 4C FI 2C 2C+1R
7.3. Power Supply & Distribution Drawings FA 2C 2C+1R
7.4. Dimensional Drawings 4C FI 2C 2C+1R
7.5. System Configuration 4C FA 2C 2C+1R

17
 DECEMBER, 2017 NIOEC-SP-70-24 (0)
APPENDIX I

VENDOR’S DOCUMENT SUPPLY (VDS) (Coun.)

Documents Documents
Documents After
With After
Purchase Order
DESCRIPTION Quotation Finalisation
Quantity Issue Quantity Quantity
Type Purpose and Type and Type
7.6. Foundation Design Base and Anchoring Details 4C FA 2C 2C+1R
7.7. Grounding System FA 2C 2C+1R
7.8. Nameplate List FA 2C 2C+1R
7.9. Preliminary System Plot Plan In Control Room 4C FA 2C 2C+1R
& 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 Drawings 4C FA 2C 2C+1R
7.13. Inter Wiring Drawings 4C FA 2C 2C+1R
7.14.Terminal Arrangement Drawings 4C FA 2C 2C+1R
7.15. Wiring Connection List 4C FI 2C 2C+1R
7.16. Interconnection Drawings Between Equipment 4C FI 2C 2C+1R
in Control Room and Equipment Room
7.17. I/O Assignment List 4C FA 2C 2C+1R
7.18. Detailed Loop Drawings Including Field 4C FA 2C 2C+1R
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 Including Application 4C FA 2C 2C+1R
Software

ABBREVIATIONS:
C: Copies
R: Reproducible
FI: For Client’s Information
FA: For Client’s Approval

18