MQ SP I 7012 3 PDF

Power and Water Utility Company for Jubail and Yanbu (MARAFIQ) Master Specification: MQ-SP-I-7012-3
Project Name: Date: 14 Jan 2011

Contract Number: Page: 1 of 56
Revision: 1
SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS
This specification has been revised as indicated below and described in the revision record on the following
page. Please destroy all previous revisions.
Revision Date Originator's Reviewed/Checked By Pages

No. Name & Initials Name & Initials
A 8/30/2010 Cory A. Haynes Vincent E. Mezzano 56
0 11/04/2010 Cory A. Haynes Anna M. Pham 56
1 1/14/2011 Cory A. Haynes Anna M. Pham 56
APPROVALS SIGNATURES DATE
Lead Engineer Thomas B. Robinson

Project Manager: Russell Shulz
Client Approval:
ISSUED FOR : Construction X Other Approved

Revision: 1
Record of Revisions
Revision Date Description
No.
A 8/30/2010 Issued for Approval, Table of Contents Only
0 11/04/2010 Issued for Review/Approval
1 1/14/2011 Issued Approved

Revision: 1
TABLE OF CONTENTS
Section
1.0 SCOPE ........................................................................................................................................................7

1.1 Purpose.........................................................................................................................................7
1.2 Objectives.....................................................................................................................................7
1.3 Scope of Supply and Responsibility ..........................................................................................7
2.0 REFERENCES ..........................................................................................................................................8
2.1 Codes and Standards ..................................................................................................................8
2.2 Project Specifications and Drawings ........................................................................................9
2.3 Conflicts .....................................................................................................................................10
3.0 DEFINITIONS AND ABREVIATIONS...............................................................................................10
3.1 Definitions ..................................................................................................................................10
3.2 Abbreviations ............................................................................................................................10
4.0 ENVIRONMENTAL CONDITIONS ...................................................................................................11
4.1 Design Temperature .................................................................................................................11
4.2 Design Sound Pressure Levels (Noise)....................................................................................12
5.0 SYSTEM OVERVIEW...........................................................................................................................12
5.1 Conceptual System Architecture.............................................................................................12
5.2 Topology.....................................................................................................................................13
6.0 SYSTEM FUNCTIONALITY ...............................................................................................................13
6.1 General - Programming ...........................................................................................................13
6.2 Installation .................................................................................................................................14
6.3 Technology.................................................................................................................................15
6.4 Open System ..............................................................................................................................15
6.5 Redundancy ...............................................................................................................................16
6.6 Telemetry ...................................................................................................................................17
6.7 Third Party System Communications ....................................................................................17
6.8 Sequence of Event Reporting...................................................................................................18
7.0 SYSTEM SIZING AND LOADING .....................................................................................................18
7.1 General Guidelines and Spares Philosophy...........................................................................18
7.2 Processor Sizing ........................................................................................................................18
Revision: 1
7.3 Memory Sizing ..........................................................................................................................18

8.0 HARDWARE SPECIFICATIONS .......................................................................................................19
8.1 AC and DC Power and Grounding Specifications................................................................19
8.2 Solar Panel Units.......................................................................................................................19
8.3 System Communications Specifications .................................................................................19
8.4 RTU’s Process Interface...........................................................................................................20
8.5 RTU I/O......................................................................................................................................21
8.6 RTU Control Functions............................................................................................................22
8.7 Logic Functions .........................................................................................................................22
8.8 RTU Communications..............................................................................................................23
8.9 RTU Information Storage and Retrieval ...............................................................................23
8.10 RTU Scan Rates ........................................................................................................................23
8.11 RTU Time Tagging and Synchronization ..............................................................................24
8.12 RTU Mathematical Functions .................................................................................................24
8.13 RTU Configuration...................................................................................................................24
8.14 Intelligent Field Instruments ...................................................................................................25
8.15 Contact (Digital) Input Subsystem .........................................................................................25
8.16 Analog Output Subsystem .......................................................................................................26
8.17 Contact (Digital) Output Subsystem.......................................................................................26
8.18 Pulse Accumulator Subsystem ................................................................................................27
8.19 RTU MMI ..................................................................................................................................27
8.20 RTU Point Count ......................................................................................................................28
8.21 RTU Power Supply Subsystem................................................................................................28
8.22 Calibration.................................................................................................................................28
8.23 Remote I/O Interface ................................................................................................................28
8.24 AC Contact Output I/O Modules............................................................................................29
8.25 DC Low Power Contact Output I/O Modules .......................................................................29
8.26 AC Contact Input I/O Modules...............................................................................................30
8.27 DC Contact Input I/O Modules...............................................................................................30
8.28 Frequency Input I/O Modules.................................................................................................31
8.29 Analog Output I/O Modules ....................................................................................................32
8.30 Analog Input I/O Modules .......................................................................................................32
8.31 Thermocouple (mV) I/O Modules...........................................................................................32
8.32 RTD I/O Modules......................................................................................................................32
8.33 Control Processor .....................................................................................................................33
Revision: 1
8.34 Watch Dog Module ...................................................................................................................34

8.35 Operator Stations......................................................................................................................34
8.36 Peripherals.................................................................................................................................35
8.37 Cabinet, Console Specification ................................................................................................36
8.38 Equipment Noise and EMI Specification...............................................................................38
9.0 SOFTWARE SPECIFICATIONS.........................................................................................................39
9.1 System Operating Software .....................................................................................................39
9.2 Engineering / Configuration Software ...................................................................................39
9.3 Control Processor Software.....................................................................................................42
9.4 Operator Station Software.......................................................................................................44
9.5 Trending.....................................................................................................................................47
9.6 Reports and Logs ......................................................................................................................47
10.0 SYSTEM PERFORMANCE..................................................................................................................47
10.1 System Availability ...................................................................................................................47
10.2 System Reliability .....................................................................................................................47
10.3 Performance Specifications .....................................................................................................48
10.4 On Line Replacement ...............................................................................................................48
10.5 System Diagnostics....................................................................................................................48
10.6 System Clock and Synchronization ........................................................................................49
11.0 DRAWINGS, DOCUMENTATION AND DATA REQUIREMENTS ............................................49
11.1 Design Drawings........................................................................................................................49
11.2 Design Interface ........................................................................................................................50
11.3 Supplier Documents..................................................................................................................50
11.4 System Logs ...............................................................................................................................51
11.5 Requirements with Proposal....................................................................................................52
11.6 After Kick Off Meeting ............................................................................................................53
11.7 As Built.......................................................................................................................................54
11.8 Electronic Documentation .......................................................................................................54
12.0 INSPECTIONS AND TEST...................................................................................................................54
12.1 Factory Acceptance Test (FAT) ..............................................................................................54
12.2 Site Acceptance Test (SAT) .....................................................................................................55
12.3 Sustained Performance Test (SPT).........................................................................................55
13.0 MAINTENANCE MATERIALS...........................................................................................................56
Revision: 1
13.1 Recommended Service and Spare Parts List.........................................................................56

13.2 Maintenance Training ..............................................................................................................56
13.3 Maintenance Service.................................................................................................................56
Revision: 1
1.0 SCOPE
1.1 Purpose
A. This specification defines the minimum requirements of Supervisory Control and

Data Acquisition Systems (SCADA) for the Power and Water Utility Company for
Jubail and Yanbu (MARAFIQ) Projects located at the existing COMPANY
complexes at Jubail Industrial City and Yanbu Industrial City, in the Kingdom of
Saudi Arabia Scope of Specification.
B. This document covers the SCADA hardware, software, and functional requirements
for projects.
1.2 Objectives
A. The intent is that a standardized approach be used by the SCADA suppliers,

COMPANY and CONTRACTOR in regards to new SCADA Systems hardware and
software as defined in this specification.
1.3 Scope of Supply and Responsibility
A. The SCADA SUPPLIER shall accept total responsibility for the overall system as
specified. This includes, but not limited to; system design, site survey, procurement,
management, progress reporting, fabrication, assembly, configuration, programming,
graphics and reports/logs building, documentation, integration, factory testing,
packing, shipping, receiving, warehousing, installation at site, interfacing, site
testing, commissioning and any other requirements defined in this specification, the
material requisition or contract documents for a fully functional, operable, reliable
and maintainable system.
B. The SCADA SUPPLIER shall provide the correct and timely submittal of all
required engineering data and documentation as required by the material requisition
or contract document.
C. CONTRACTOR shall provide the correct and timely submittal of all required
engineering data and requests for information for use by SCADA SUPPLIER to
perform the work.
D. In the event of conflict within this specification, the SCADA SUPPLIER shall
request a written clarification. All exceptions to the specification must be in writing,
and shall reference the section/paragraph.
E. The SCADA SUPPLIER shall provide comprehensive detailed functional design

specifications describing all aspects in the SCADA SYSTEM SUPPLIER scope of
supply.
Revision: 1
F. Refer to the roles and responsibility matrix for details of compliance required by the
SCADA SUPPLIER, CONTRACTOR and other parties.
G. All 3rd party hardware components / equipment (i.e. OTS computer / server
equipment, Ethernet switches, etc.) to be provided by SCADA SYSTEM SUPPLIER
as integral components of the SYSTEM shall be approved by COMPANY prior to
purchase.
2.0 REFERENCES
2.1 Codes and Standards
A. The SCADA System shall be designed in accordance with the following codes,
standards, and regulations. Except as modified by the requirements specified herein
or the details of the drawings, work included in this specification shall conform to the
applicable provisions of these publications. Revisions (or editions) of codes,
standards and specifications in effect at the inception of the project shall apply for the
duration of the work.
B. American Gas Association (AGA)
 Report 3 : Orifice Flow Calculations
C. International Electrotechnical Commission (IEC)
 IEC 73 : Specification for color of indicator lights, push-buttons, annunciators

and digital readouts
 IEC 79 : Electrical equipment for use in hazardous locations
 IEC 529 : Degrees of Protection of Enclosures
 IEC 617 : Graphic Symbols for Electronic Diagrams
 IEC 60364-4-41 : Low Voltage Electrical Installations
 IEC 61508 : Programmable Electronic Safety Systems
 IEC 61131-3 : Programmable Controllers - Part 3: Programming Languages
D. Institute of Electrical and Electronics Engineers (IEEE)
 IEEE 488 : Standard Digital Interface for Programmable Instruments
 IEEEE 802.3 : Standard for CSMA/CD Media Access Control (‘Ethernet’)

Revision: 1
E. International Society of Automation (ISA)
 ISA 5.1 : Instrumentation, Symbols and Identification.
 ISA 5.2 : Binary Logic Diagrams for Process Operations.
 ISA 5.3 : Graphic Symbols for Distributed Control/Shared Display

Instrumentation, Logic and Computer Symbols
 ISA-18.1 : Annunciator Sequences and Specifications
 ISA-18.2 : Management of Alarm Systems for the Process Industries
 ISA 50.02 : Fieldbus Standard for Use in Industrial Control Systems
 ISA 71.04 : Environmental Conditions for Process Measurement and Control
 ISA 88 : Batch Control
F. ISO : International Organization for Standardization

 IS0 9000 : Quality Systems
G. NEMA : National Electrical Manufacturers Association
 NEMA ICS-6 - Enclosures for Industrial Controls and Systems
H. NFPA : National Fire Protection Association
 NFPA 70 - National Electrical Code
 NFPA 496 - Purged Enclosures for Electrical Equipment Quality Assurance Test
2.2 Project Specifications and Drawings
A. All equipment and accessories covered by this specification shall comply with all
Project Specifications and Drawings listed herein.
B. MARAFIQ Standards and Specifications
Specification No. Title

MQ-SP-I-7010 Safety Instrumented Systems (SIS)
MQ-SP-I-7012-1 Process Controls - DCS
MQ-SP-I-7012-2 Process Controls - PLC
Revision: 1
MQ-SP-I-7016 Control Panels

MQ-SP-I-7017 Fire and Gas Detection System
MQ-SP-T-7811 Fiber Optic Cable
MQ-SP-E-6001 Electrical Design
MQ-SP-E-6009 Uninterruptible Power Supplies
MQ-SP-E-6018 Low Voltage Power and Control Cable
2.3 Conflicts
A. In the event of conflict within this specification, the SCADA Supplier shall request a
written clarification. All exceptions to the specification and conflicts with the
existing system installation must be in writing, and shall reference the
section/paragraph.
3.0 DEFINITIONS AND ABREVIATIONS
3.1 Definitions
A. Terms used in this document are defined as follows:
SCADA SUPPLIER Supplier of SCADA SYSTEM equipment purchased by

CONTRACTOR.
COMPANY Power and Water Utility Company for Jubail and Yanbu
(MARAFIQ) or designated representative.
CONTRACTOR Other Engineering, Procurement and Construction contractor
responsible for one or more of the plants / facilities associated with
the MARAFIQ projects.
SYSTEM Refers to the SCADA System as specified in this document.
3.2 Abbreviations
ADC Analog to Digital Conversion
CPU Central Processing Unit
CRT Cathode Ray Tube
CSMA/CD Carrier Sense Multiple Access with Collision Detection
DCS Distributed Control System
FAT Factory Acceptance Test

Revision: 1
HART Highway Addressable Remote Transmitter
HMI Human Machine Interface
I/O Input/Output
LAN Local Area Network
LED Light Emitting Diode
LCD Liquid Crystal Display
MMI Man Machine Interface
MTU Master Terminal Unit
RAM Random Access Memory
RTU Remote Terminal Unit
PLC Programmable Logic Controller
PSU Power Supply Unit
SAT Site Acceptance Test
SER Sequence of Event Recording
SIS Safety Instrumented Systems
UPS Uninterruptible Power Supply
4.0 ENVIRONMENTAL CONDITIONS
4.1 Design Temperature
A. SCADA Systems shall normally be installed and operated in an air conditioned

environment which will be maintained at the following conditions:
 21 ºC ± 3 ºC and 50% ± 10% Relative Humidity

Revision: 1
B. SCADA Supplier standard equipment shall be fully operational so as to perform per

specifications at any air temperature range from 5 to 40 ºC in all the Control Rooms,
Operator Shelters and Field Auxiliary Rooms, and a relative humidity range of 40 to
60 percent non-condensing. The SCADA SYSTEM shall have no failures when
operated at 50 ºC room temperature and relative humidity of 95% for a 4 hour period
(in case of air-condition loss). SCADA System Supplier shall specify any
environment limitations to the Company.
C. The SCADA System Supplier equipment installed in local control panels / field
control cabins shall meet the design temperature at the following conditions:
 9.0 to 50.0 ºC and 22 to 95 % Relative Humidity
D. The SCADA System Supplier shall include a “High temperature” option for
equipment to meet this requirement.
E. For components exposed to the sun the surface design temperature shall be 85 ºC.
4.2 Design Sound Pressure Levels (Noise)
A. The maximum acceptable sound pressure level for each piece of equipment installed
in the Control Rooms shall be 60 dBA measured at a distance of 1 meter lateral from
the source and 1.5 meter vertical from floor with a sound level meter using the “A-
weighted” sound level scale. Sound level measurement shall be based on tests carried
out per IEC standards.
5.0 SYSTEM OVERVIEW
5.1 Conceptual System Architecture
A. The SCADA system architecture shall be based on a client/server computer network,

using industry standard operating systems, networks, and protocols. The system shall
allow for the distribution of system functions across the network to enhance
flexibility and performance.
B. The scope of supply for the SCADA system shall include, but not be limited to, the
following major items of equipment. The inclusion of this list is not intended to limit
the supply in any way. The vendor is required to supply a complete, functioning
system.
 Microprocessors
 Workstations
 Remote Terminal Units (RTU’s)
 Software
Revision: 1
 Modems
 I/O points
 Training
5.2 Topology
A. The topology of a SCADA system varies with the project application. The system
can be as simple as gathering Sea Water Flow Date or Natural Gas Distribution Grid
Data or wellhead data in production fields and transmitting that data to a control
center.
B. The SCADA System can be very complex and include production flow line data,
control of transmission pipelines, control of pump and compressor stations and
control of production treating facilities. SCADA systems are often used to monitor
pipelines and pipeline compression stations as well as off shore production
platforms.
C. The SCADA vendor shall provide a topology drawing showing all the components of
the proposed system.
6.0 SYSTEM FUNCTIONALITY
6.1 General - Programming
A. SCADA Systems shall be user programmable in a high-level control language. The

system shall not require interruption of normal process operation to perform
programming functions. A separate programming station, for example an engineering
workstation or personal computer based software, shall normally be provided for
editing of source code, compilation, linking, and loading.
B. Programs shall be capable of being loaded into the system or stored on removable
disks for loading at a future date. Programs shall be able to load values, for example
set points and tuning constants into control algorithms; set control modes; turn on
and off discrete I/O, send messages to operators, print reports, and otherwise
manipulate essentially all system variables. In addition, programs shall have normal
capabilities for calculations, loops, and GO TO subroutines. The System shall allow
interruption of normal program execution to handle unusual conditions regardless of
normal program execution. At least three levels of interrupts shall be provided to
handle routine, alert, and emergency conditions.
Revision: 1
C. Systems shall incorporate provisions for debugging of programs, for example single
stepping and display of intermediate values. Scheduling of programs shall be
supported on a periodic basis (time based), event driven, and upon demand. Priority
levels shall be supported to ensure critical programs are completed, unless supplier
can guarantee all programs will complete within their scheduled execution times. If
large, complicated programs are required, consideration shall be given to dedication
of specific hardware for tasks, for example a single computing module, to minimize
possibility of accidental program interaction. Online program changes shall be
supported, with minimal program execution suspension. If continuous program
execution is required, special attention may be needed to design and evaluate
switchover techniques, within the Supplier’s capabilities, to load updated programs.
System shall be capable of being programmed by user for custom applications.
D. System configuration procedures shall be accessible by means of security password.

Security password shall be user configurable. User definable access levels with
assignable privileges shall be provided.
6.2 Installation
A. Efficiency of performing engineering work shall be considered when locating the

engineering station. This may require a location near operations, but separate enough
to ensure a quiet area with sufficient space for manuals, documentation, and drawings
that accompany many engineering activities.
B. Operator consoles shall be designed around ease of access to all devices on the
console and on how many operators the console has to accommodate. Once this is
established, console furniture can be arranged such that the most important devices
are within easy reach.
C. Empty console bays or desktops shall be provided for auxiliary equipment, for
example radios, telephones, hardwired pushbuttons, and annunciators.
D. Furniture shall have shelves or drawers for documentation, for example operator
logbooks and manuals.
E. Printers shall be located such that noise of printer will not be a distraction. A remote
location is acceptable in many cases, as printer output is for record purposes only and
is not an operating tool.
F. Support facilities to ensure reliable operation of the SCADA system are critical to
safe operation of the process. Such support facilities include UPS, redundant HVAC
with equipment to remove corrosive gases, and fire protection systems.
G. Central I/O shall be considered if the distance from control center to the field
instruments is short or the number of signals is small.
Revision: 1
H. Purging shall not be used to meet electrical area classification. Indoor rack mount
equipment shall be suitable for operation with minimal air conditioning. It is
acceptable for operator console and workstation equipment to require tighter control
of environmental conditions than rack mount equipment.
I. Field mounted I/O devices shall be suitable for all outdoor conditions expected,
without need for auxiliary heating, cooling, or air filtration.
J. SCADA system equipment shall be suitable for withstanding occasional exposure to

H2S, SO2, dust, and other contaminants due to air conditioning system failure, plant
upsets, open doors, and other causes. Air filtration shall be provided to reduce
concentration of corrosive gases, for example H2S, SO2, and Cl2, for equipment
protection.
K. Filtering of corrosive gases shall be capable of reducing intake concentrations to the

ISA 71.04 severity level designation appropriate for the electronic instruments to be
housed. Filtration system required to meet these levels shall be economically
evaluated against other types of protection for instruments, for example coatings for
electronic circuitry. Electronic control system shall be installed in accordance with
manufacturer’s recommendations.
L. The vendor, if required by MARAFIQ, shall provide the RTU’s mounted, complete
and ready for operation within a protective shelter.
6.3 Technology
A. SCADA system hardware and firmware (excluding application software) supplied as

part of this specification shall be the latest revision level available at the time of issue
of the purchase order. Supplied equipment shall be ‘field proven’ and the vendor
shall supply sufficient information to support the field proven status of the system.
6.4 Open System
A. Openness is defined as the ability of the system to be easily integrated with upper
level computers with minimum development of application programs to interface
with the SCADA system.
B. Data transferred from the system to a database on the plant information network will
be used for plant analysis and for reporting to maintenance personnel, process
engineering, management and others.
C. The SCADA system shall be connected with upper level computers using available
standard proven interfaces. Storage modules for historical data shall be interfaced
with information on the upper level network so that historical data and files can be
transferred to the upper level computer database without loading the real time
network of the SCADA system.
Revision: 1
D. The storage modules shall have a high security operating system to prevent
unauthorized users from accessing the database.
E. The real time SCADA network shall interface to the upper level computers by a
router type module. The module shall have high throughput to transfer data between
control module and upper level computers.
F. The interface module shall have sufficient security measures to prevent unauthorized
users from accessing the system database.
G. The system shall be capable of interfacing with a third party acquisition package that
will collect data from various systems in the plant.
6.5 Redundancy
A. A single point failure anywhere in the system shall not negate the operator’s ability to
monitor and control the process. Single point failure anywhere in the system shall not
result in the loss of a control loop. The system shall function by switching over to
backup modules to accomplish control. Monitoring-only points shall be an exception.
B. Controller modules and associated I/O modules shall be provided in redundant

configuration. This will provide uninterrupted control in the event of a loss of a
single module. Monitoring-only, points input modules shall not be provided in
redundant configuration. Transfer to the secondary device shall be automatic and
bump-less. The system shall provide the operators with an appropriate alarm
message.
C. Controller cabinet power supplies shall be supplied in redundant configuration. These

shall also be provided with a battery backup, sized to provide power for at least 30
minutes. This will facilitate operations to initiate an orderly shutdown if needed.
D. Switch back to repaired equipment shall be possible only after a complete diagnostic
to determine that the module is in healthy condition and ready to resume normal
function.
E. Means shall be provided to switch over to redundant equipment by manual means.

This shall be an engineering function and shall be protected by key-lock or password.
F. HMI/MMI redundancy is achieved by providing multiple operator stations that are

functionally stand alone devices, with each station capable of duplicating the
functionality of any other station in the system.
Revision: 1
6.6 Telemetry
A. Data telemetry between data acquisition equipment and the control center employs
various media including fiber optics, telephone lines with dial up modems,
microwave and radio frequency communications. The vendor shall recommend a
cost-effective telemetry of data pending project specific requirements.
6.7 Third Party System Communications
A. Some of the commonly encountered subsystems to which the SCADA system may
establish digital communication links are as follows:
 Vibration Monitoring Systems (VMS)
 Compressor Control Systems (CCS)
 PLCs
 Burner Management Systems (BMS)
 Safety Instrumented Systems
 Fin-Fan Vibration Monitoring Systems (FFVMS)
 Smart Electrical Devices
 Management Information System (MIS)
 Turbine Governor Control Systems
 Loading Weigh Scale
B. Interfaces between the SCADA and auxiliary equipment systems shall use standard
products that are compliant with industry standard protocols.
C. Use of modems to convert from one standard to another shall be minimized, and if
required shall be approved by MARAFIQ.
D. Where redundant communication links and modems are required, the modems shall
also be redundant.
E. It shall be possible to set any data as ‘READ only’ to avoid inadvertent changing of
data from SCADA.
Revision: 1
F. SCADA communication to the MIS, plant networks and other non-control computer
systems shall be designed to ensure that any failure in the external systems; request
for information; or network loading problem will not impact the performance or
availability of the SCADA System.
6.8 Sequence of Event Reporting
A. Process alarms and system faults shall be time and date stamped and recorded in
memory for 30 days. If specified, the system shall be able to log discrete and analog
inputs that are configured as alarms or shutdowns. The first out alarm and all
subsequent alarms shall be time tagged in the order they occur with a minimum
resolution of 100 ms. The vendor shall provide a utility to support logging, buffering,
reporting and printing.
7.0 SYSTEM SIZING AND LOADING
7.1 General Guidelines and Spares Philosophy
A. The system shall be supplied with at least 20 percent spare capacity. This spare
capacity shall be equally distributed throughout the system. The spare capacity
requirement applies to all elements in the system including hardware, application
software, graphics, history, trends, reports, and number of data base points.
B. The system shall be capable of expansion by adding additional nodes, consoles and
workstations. This addition shall be performed on-line without shutting down the
system.
7.2 Processor Sizing
A. Processor shall be sized to meet the project requirements in the form of available
slots or algorithms, displays, points and addresses plus 10 percent to allow for project
growth. In addition there shall be 20 percent capacity for future growth.
7.3 Memory Sizing
A. Memory shall be sized so that after the application program is loaded, 50 percent
spare memory is available.
Revision: 1
8.0 HARDWARE SPECIFICATIONS
8.1 AC and DC Power and Grounding Specifications
A. The vendor shall provide the power modules for supplying power to the chassis. The
chassis power modules shall be redundant with internal automatic transfer and
provided with a battery backup. The batteries shall be sized to provide power for at
least 30 minutes based on full load. This will provide enough time for the operating
personnel to initiate an orderly shutdown. An alarm indication shall be provided to
alert operating personnel on loss of power. Each power supply in a redundant
configuration shall be capable of supplying full load. The two power supplies shall be
supplied from two independent sources of outside power.
B. AC safety ground and Instrument signal ground shall conform to NEC. AC safety
ground bus shall be directly connected to the equipment cabinets. The vendor shall
provide a grounding schematic, showing all grounds and ground buses.
8.2 Solar Panel Units
A. When power is not available at remote locations, solar cells with batteries and battery
charger shall be provided. The SCADA system vendor shall size the solar panel units
for continuous operation at the required current and voltage levels.
8.3 System Communications Specifications
A. Redundant system bus networks shall interconnect all components of the system and
serve as the data communication line and provide automatic switchover to backup.
The computer interface shall allow digital computers to access and place information
on the system network. Each device shall time share system network that carries data
to and from various devices. Data transmission shall employ integrity checking.
B. Control information (process variable, set point, and output) shall be stored at a point
within the system such that system network failure does not result in loss of control.
System shall periodically check operation of devices on the network. If an error is
detected and not correctable, system shall go to preprogrammed failure state on
affected control loops. An alarm shall be generated at operator station. Type and
location of failure shall be indicated on operator station display and on system alarm
printer. System shall have self-diagnosis to board level with a system diagnostic
display at operator station. System data link shall be able to communicate updated
information between consoles and control devices, even if a majority of values are
rapidly changing. Communication shall continue without degradation of speed or
accuracy.
C. I/O interface communications shall use standard RS-232, RS-422, RS-485 or other
applicable protocols in accordance with the project specific requirements.
D. When radio communications are used for data telemetry the vendor shall apply to the
local authorities for the appropriate VHF or UHF frequency.
Revision: 1
E. Antenna for radio communications data telemetry shall be highly directional dish
type with open grid reflector provided complete with support tower and transmission
line. The SCADA vendor shall do a preliminary site survey for interference and to
determine optimum antenna locations.
8.4 RTU’s Process Interface
A. The Remote Terminal Unit (RTU) shall work with the SCADA system by way of
appropriate telecommunications links to provide the functionality of the complete
system. Each RTU shall be capable of operating as a stand-alone unit to provide local
monitoring and control.
B. The RTU shall be self-contained units capable of collecting field data and providing
for control output by way of communications and operator interfaces.
C. The primary objective of the RTU shall be to provide the basic data acquisition
functions required and to enable remote control from the Master Terminal Unit
(MTU).
D. Secondary objectives shall be to:
 Use the processing capability of the RTU to reduce the processing load of the
MTU
 Enable a comprehensive assessment of the status of the station at which the RTU
is connected
 Provides a basis for expansion and additional functionality in the future
 Provide data on field device operations to assist with maintenance
E. The RTU basic functionality shall include:
 Data acquisition
 Control
 Logic functions
 Communications
 Operator Interface
 Mathematical functions
 Historical storage (limited)

Revision: 1
 Optional functions that may be included are:
 Dial-up communications functions
 Inter RTU communications capability
F. The selected vendor’s standard equipment range may include functions that are not
specifically mentioned in this standard. In such a case, the vendor shall be required to
assume the responsibility for the inclusion of those items that are required for the
correct and successful operation of the delivered system.
G. The RTU shall acquire analog and digital field data (data acquisition) from signal
lines connected to module terminations. The RTU shall accept all input signals
without the need for preconditioning, including data transferred through serial links
with other specific computers, for example a flow computer.
H. The RTU shall permit the storage of acquired data (in RAM buffers) and the
transmission of the buffer data to the MTU.
8.5 RTU I/O
A. Analog inputs, for example pressure and temperature shall be supplied as inputs to
the RTU. Normally these inputs shall be represented by a 4 - 20 mA current, relative
to the primary process measurement.
B. The facility shall be provided for displaying and setting the equation constraints at
the RTU local operator interface.
C. The capability to calculate for non-linear current inputs (non-linear scaling) shall also
be provided in the RTU.
D. The digital input system of the RTU shall normally accept voltage-free contact
closures at a digital input module of the RTU. There are two types of status inputs:
 Single status inputs (normally associated with alarms) involve only a single
monitored point and have only two states: zero or 1. The alarm condition may be
initiated by either the closure of normally open contacts or the opening of
normally closed contacts.
 Double status inputs shall compare two (2) status inputs for certain devices, for
example remotely operated valves having open, closed, and transient states. The
double status data processing shall process the four conditions (00, 01, 10, 11) of
such devices. The open and closed states (01, 10) shall initiate an event
condition. The transient state (00) shall not cause an alarm unless the state exists
for longer than a predefined time, independently set for each device. In the case
of large valves the transient state may last for about two minutes.
Revision: 1
8.6 RTU Control Functions
A. The RTU shall provide the facility for an operator to select and control equipment
and facilities. The equipment control sequences shall be in accordance with the
select-check back-execute sequence, which the operator shall not be able to bypass.
B. The RTU shall be capable of providing the following types of control:
 Open (On)/Close (Off) Control (Digital Output)
 Setpoint Control
C. The analog outputs may be derived from analog signals stored in memory or be
received from the local operator interface.
8.7 Logic Functions
A. The RTU shall be capable of performing logic functions in terms of:
 Grouping, communing and deriving of alarms
 Interlocking logic
 ESD control logic
 SCADA SYSTEM control logic
B. It shall be possible to distribute the inputs to different input modules to carry out
these functions.
C. Interlocking Logic is the means to minimize the risk of incorrect operation or

incorrect sequence of operations shall be included within the RTU as a logical
interlocking function.
D. If an I/O module is non-operational and an input signal from it is required as an input

to an interlocking expression, then the release of the interlocking output shall be
inhibited, that is the control function shall be inhibited. The operator shall be able to
override such inhibit signals but only after taking action to specifically acknowledge
alarms generated as a result of the incomplete input to the interlocking expression.
E. Safety Instrumented Systems means to automatically apply a control (close)

command to remotely operated valves shall be implemented within the RTU. The
algorithm and logical inputs proposed to confirm the SIS function shall be subject to
MARAFIQ approval.
Revision: 1
8.8 RTU Communications
A. The RTU shall support both internal and external communications functions.
B. The communications network internal to the RTU shall be designed and implemented
in such a way that the passing of data and commands between modules shall not be
prevented by the failure of any module directly involved in the communication
exchange. In addition, the internal network shall not become overloaded under the
heaviest traffic possible in an RTU ultimate expansion configuration.
C. The MTU shall initiate communications with a selected RTU by the addressing
function. Each RTU shall recognize its own unique address and shall have the
capability of being assigned any address within a range of possible addresses. It shall
be possible to address all or a selected number of RTUs from the MTU so that global
or broadcast messages may be sent.
D. Outgoing lines shall have surge protection and these barriers shall be supplied and
integrated in the RTU.
8.9 RTU Information Storage and Retrieval
A. The RTU system shall include database management and support facilities to enable
applications software access to database items and to facilitate database building and
modification.
B. The RTU database shall reside in a file system and a real-time memory (RAM)
resident database. Some information may be extracted from data files and maintained
in shared memory regions to improve system performance.
C. The database shall include all data that is normally obtained by system data
acquisition, for example program, calculated or operator entered data, historical and
logs data.
D. Non-volatile memory shall be supported to enable retention of data during power

down or system restart periods.
E. Access to the real-time database in which the I/O point values and attributes are
stored, shall be by way of an interface subroutine supplied as part of the system.
8.10 RTU Scan Rates
A. The local scan rates for individual I/O modules shall be able to achieve the time-
tagging resolution and system performance requirements.
B. The consideration of scan times shall include the acquisition of data, processing and
updating of the database.
Revision: 1
C. The overall system scan period shall be defined as the time for polling all RTU’s and
reporting all points (not including retries and time-outs) and shall be less than 30 s
for the system (radio, cables, leased lines). Report by exception techniques shall be
incorporated in the design to further reduce the total polling time.
8.11 RTU Time Tagging and Synchronization
A. The MTU system shall have the ability to attach to each digital event signal a time
tag to enable recording of the occurrence with a resolution of at least one second.
8.12 RTU Mathematical Functions
A. The RTU shall include mathematical functionality as follows:
 Linear conversion to engineering units
 Non-linear conversion to engineering units
 Input filtering
 Logical (Boolean) operations
B. Other general mathematical functions to enable the stand-alone capability of the RTU
shall be, as a minimum:
 Arithmetic operations
 Absolute values
 Averaging
 Positive differences
 Integrated values
 Maximum
 Minimum
 Indications from values within limits and outside limits
8.13 RTU Configuration
A. The RTU shall be microprocessor based programmable units with both ROM and
RAM memory.
Revision: 1
B. Ideally, all RTUs shall be modular and from the same supplier model product line
with identical capabilities, differing only in size. However, this does not exclude the
possibility of providing alternative and differently configured models particularly in
consideration of power consumption in the case of less complex RTUs located away
from main power sources, for example remotely-operated wellhead panels. The RTU
shall be designed and function so that no single point of failure shall cause a control
malfunction.
C. Safety barriers (if required) shall be defined as part of the RTU system.
8.14 Intelligent Field Instruments
A. The RTU shall have the capability to interface with intelligent field instruments. The
interface shall, at least, be capable of communicating with field instrumentation
employing the HART (Highway Addressable Remote Transmitter protocol).
B. The vendor shall describe the functionality, characteristics and method of

implementation of the interface and the protocols supported or proposed to be
supported by the analog input subsystem.
C. The analog input subsystem shall be comprised of analog multiplexers and Analog to
Digital Converters (ADC). The multiplexers shall provide scaling, filtering, transient
protection and switching of the analog input signals to the ADC. The ADCs shall
receive the analog signals from the multiplexer and convert them to digital
representation.
D. The input ranges to the analog input subsystem shall be flexible and include as a
minimum, the following:
 4 to 20 mA
 -5 to +5 V
 -10 to +10 V
 Digital field bus signals
8.15 Contact (Digital) Input Subsystem
A. The contact input subsystem shall provide the functionality to monitor normally open
and normally closed, voltage-free contacts to indicate status information.
B. The contact input subsystem shall include:
 The contact wetting supply voltage source
 The input modules connecting to the field wiring

Revision: 1
 The RTU logic and memory buffers to process status changes
 Contact debounce filtering
C. The contact input subsystem shall support:
 Detection of momentary changes of state
 Detection of permanent changes of state
 Optical isolation of inputs
8.16 Analog Output Subsystem
A. The analog output subsystem (for setpoint adjustment) shall provide a 4 - 20 mA

current output at the RTU by way of Digital to Analog Converters (DAC) in response
to commands received from the MTU and RTU common logic subsystem.
B. The select-check-operate control sequence shall be available for setpoint adjustment

and included in the RTU control functionality.
C. The DAC resolution shall be at least 12 bits with an accuracy of 0.1 percent of full
range.
8.17 Contact (Digital) Output Subsystem
A. The contact output subsystem shall provide for the operation of auxiliary relays or
other devices to control plant equipment. Control output via maintained and pulse
duration contact closures shall be provided.
B. Control functions shall use the select-check-operate control sequence and the contact
output subsystem shall recognize two commands associated with device control:
 Select for control
 Control after select
C. A select-for-control command shall cause the RTU to select, verify and arm the drive
circuits for the selected output, but not energize the output (relay). A selection
verification message shall then be transmitted to the MTU.
D. A control-after-select command received after a select-for-control command shall

cause the RTU to energize the previously selected output for a predefined time
period. Any command other than the expected control-after-select shall cause the
RTU to disarm and reset the drive circuits and cancel the selection. In addition, if the
control-after-select is not received within a predefined time period, the RTU shall
automatically disarm and reset the drive circuits, thereby canceling the selection.
Revision: 1
E. It shall not be possible for the RTU to energize an output that has not been selected
for control nor shall it be possible to select more than one output with a single control
command, with the exception of predefined sequential controls, for example
emergency shutdown control.
F. The duration of each contact closure shall be pre-selectable and all contacts shall be
voltage free.
G. The contact outputs shall be rated for 30 V dc and 1 A current to suit a 24 V dc

supply. If ratings in excess of this are required, auxiliary relays shall be provided.
H. In case of power failure, output state is to remain unchanged. When power is

restored, output state is to remain unchanged. If an RTU is reset, the outputs shall not
change state.
8.18 Pulse Accumulator Subsystem
A. The pulse accumulator subsystem shall provide the RTU with the capability to count
and store pulses from external sources. Each pulse accumulator, when provided, shall
use one digital input, and counter values shall be converted to at least a 32 bit
floating value, to be stored in preparation for transmission as a count value.
Accumulator values shall be converted to, and accessible as, engineering units at the
RTU.
B. Pulse accumulation shall be performed over a predefined (programmable) time

period with an end of period reset or, alternatively, continuous counting with rollover
when the maximum count is reached.
C. The vendor shall state the maximum accumulator pulse count rate capability of the
RTUs provided.
8.19 RTU MMI
A. The vendor shall provide built in color type PCs in the form of ‘laptop’ or ‘notebook’
type personal computers providing display and keyboard facilities and printer ports
for use with the remotely located RTUs.
B. The units shall be configured with sufficient hard disk storage and memory devices
to enable all functions to be performed without loading additional data from separate
media. The functions shall include:
 MMI operating functions
 System diagnostics
 RTU database modifications

Revision: 1
C. The type and configuration of these units shall be subject to MARAFIQ approval.
8.20 RTU Point Count
A. Each RTU shall be capable of being expanded in the field for each point type by the
addition of cards or modules. The steps necessary to completely implement the RTU
expansion shall be clearly described in the documentation.
B. These RTUs shall be intelligent devices capable of communicating via modem over a
radio link. The RTU shall be able to calculate AGA Report 3 orifice flow
calculations and transmit data to the Central Control Room.
8.21 RTU Power Supply Subsystem
A. RTUs shall operate on a nominal 24V dc power supply. Differing voltage levels
required by the RTU circuitry shall be derived within the RTU by the power supply
subsystem.
8.22 Calibration
A. When the system includes a Smart Tank Gauging system or other smart instruments
it shall be possible to calibrate these instruments from the operator station.
8.23 Remote I/O Interface
A. The use of remote I/O can reduce both cable volumes at the processor location and
the average length of connecting cable per I/O point. The degree to which these
benefits can be realized depends on the physical arrangement of equipment in the
plant. A logical use of remote I/O would be to locate I/O modules in motor control
centers.
B. Communications with remote I/O shall be by means of coaxial or fiber optic cable,
and shall occur at a speed high enough to adequately support system operations.
C. Requirements for Remote I/O shall be part of the purchase order. The purchase order
will provide details as to the quantity, type and location of remote I/O. Remote I/O
modules shall be provided with redundant communication links and communication
interface modules.
D. Communication links shall comply with vendor recommendation. Vendor shall

recommend cable and connector type and model and installation techniques to be
followed. The communication links shall be provided with proper diagnostics to
monitor the health of communication. Status lights shall indicate the status of the link
module. Single failure shall not cause loss of remote I/O communication. Failures
shall be capable of being logged for future analysis.
Revision: 1
8.24 AC Contact Output I/O Modules
A. Capacity per I/O module shall be 8, 16, or 32 independent channels. Output channel
status shall be indicated via LEDs (one per channel). Isolation shall be 600 V ac
between any combination of input, output, and ground. Manufacturer shall provide
design data. Output switch (output channels) shall comply with the following:
 Voltage range. 79 V ac to 132 V ac
 Nominal voltage. 120 V ac, 50/60 Hz
 Current. 2 A (minimum) per channel, 12 A (maximum) per module
 Off state leakage. 3 mA (maximum)
 Inrush current:
 Overload sensing provided
 24 A peak 10 ms (1/2 cycle)
 12 A RMS 20 ms (1 cycle)
 3.5 A RMS for 1 s
 Short circuits that result in greater than 50 A peak current will damage module.
If 50 A current is possible; external fusing shall be provided
 Holding current. No minimum required
 On state voltage drop. 0.4 V @ 1 A
 Automatic restart from overloads. Approximately 1 s after overload sensed
8.25 DC Low Power Contact Output I/O Modules
A. Output module shall have capacity for 8, 16, or 32 independent channels. LEDs (one
per channel) shall indicate output channel status. Isolation shall be as follows:
 Output to ground: 600 V ac
 Output pair to output pair: 600 V ac (between adjacent pairs of channels, each
pair of channels share a common return
B. Output switch with external source shall comply with the following:
Revision: 1
 Applied voltage: 60 V dc (maximum)
 Load current: 0.5 A (maximum)
 Shorted load duration: Indefinite (duty cycle current limit on overload)
 On state current limit: 0.75 A (typical)
 Off state leakage current: 1.0 mA (maximum)
C. Output switch with internal source shall comply with the following:
 Source resistance: 660 Ω (nominal)
 Off state leakage current: 0.5 mA (maximum)
8.26 AC Contact Input I/O Modules
A. I/O module capacity shall be 8, 16, or 32 independent channels. LEDs (1 per

channel) shall indicate input channel status. Input shall comply with the following:
 On state voltage: 79 V ac to 132 V ac
 Off state voltage: 0 V ac to 20 V ac
 Current: 2.2 mA (typical) at 20 V ac to 132 V ac
B. Source resistance limits shall be as follows:
 On state: 1 kΩ (maximum) at 79 V ac
 Off state: 100 kΩ(minimum) at 132 V ac
C. Isolation shall be as follows:
 Input to ground: 600 V ac
 Input to input: 600 V ac
D. Filter time shall be configurable 4, 8, 16, or 32 ms.
8.27 DC Contact Input I/O Modules
A. Input capacity shall be 8, 16, or 32 independent channels. LEDs (1 per channel) shall
indicate input channel status. Isolation shall be as follows:
Revision: 1
 Input to ground: 600 V ac
 Input pair to input pair: 600 V ac (Channels are paired and share common return.
Isolation is between pairs of channels)
B. Filter time shall be configurable 4, 8, 16, or 32 ms. Contact sensor input range (each
channel) with contact open (off) or closed (on) shall be as follows:
 Open circuit voltage: 24 V dc ±10 percent
 Short circuit current: 2.5 mA (maximum)
 On state resistance: 1 kΩ (maximum)
 Off state resistance: 100 kΩ (minimum)
C. Voltage monitor input shall comply with the following:
 On state voltage: 15 V dc to 130 V dc
 Off state voltage: 0 V dc to 5 V dc
 Current: 2.2 mA (typical) at 5 V dc to 130 V dc
D. Voltage monitor source resistance limits shall comply with the following:
 On state: 1 kΩ (maximum) at 15 V dc.
 Off state: 100 kΩ (minimum) at 130 V dc.
8.28 Frequency Input I/O Modules
A. Input module capacity shall be 4, 8, 16, or 32 independent channels. Input voltage

range (redundant) shall be 26 V dc to 42 V dc. Input frequency shall be a minimum:
 3 Hz for conversion time of 0.5 s and 1.0 s.
 5 Hz for conversion time of 0.2 s.
 10 Hz for conversion time of 0.1 s.
B. Maximum input frequency shall be 12.5 kHz. Input resistance shall be 10 kΩ.
Revision: 1
8.29 Analog Output I/O Modules
A. Output module capacity shall be 4, 8, or 16 isolated and independent channels.

Output range (each channel) shall be 0 to 20.4 mA dc. Maximum output load shall be
735 Ω. Compliance voltage shall be 18.6 V (nominal) at 20 mA dc at I/O field
terminals. Rated mean accuracy shall be 0.05 percent of span.
B. Settling time shall be 100 ms to settle within 1 percent band of steady state for 10 to
90 percent input step changes. Linearity error shall be 0.025 percent of span
(monotonic). Resolution shall be minimum 12 bits.
8.30 Analog Input I/O Modules
A. Input module capacity shall be 8, 16, or 32 isolated and independent channels. Input
range (each channel) shall be 0 to 20.4 mA dc. Rated mean accuracy shall be 0.05
percent of span. Isolation shall be 600 V ac between any channel and ground or
between a given channel and any other channel.
8.31 Thermocouple (mV) I/O Modules
A. Input module capacity shall be 8, 16, or 32 isolated and independent channels and 1
isolated reference junction compensation channel. Input range shall be 10.5 to
71.41875 mV dc. Rated mean accuracy of mV channels shall be 0.035 percent of
span (0.028 mV). Input open circuit voltage shall be 0.25 V dc.
B. Typical thermocouple types shall be B, E, J, K, R, S, T, N, and other milli-volt

signals. Isolation shall be 600 V ac between any channel and ground or between a
given channel and any other channel.
8.32 RTD I/O Modules
A. Input capacity shall be 8, 16, or 32 isolated and independent channels. Input range
(each channel) shall be 0 to 320 Ω. Rated mean accuracy shall be 0.025 percent of
span (0.08 Ω). Input connections shall support two, three, or four wire variable
resistance temperature sensors.
B. Typical resistance temperature sensors shall be copper, platinum or nickel. Input

voltage range (redundant) shall be 26 to 42 V dc. Isolation shall be 600 V ac between
any channel and ground or between a given channel and any other channel.
Revision: 1
8.33 Control Processor
A. Control processor shall be redundant and provide automatic switchover to backup.

Control components shall be distributed throughout the system in a way that failure
of one controller does not affect performance of the remaining system components.
Control processor shall be housed in an industrial enclosure. Controllers shall be
designed to minimize probability of more than one control loop being disabled at any
time. Removal of a faulty control processor and its replacement with a good
controller shall not require shutdown of other parts of system. Adequate checks shall
be included in processors to ensure that erroneous data is not used for control
manipulation. Control processor scan rate shall be suitable for process application.
B. SCADA systems that require the highest possible up time shall have a hot standby
(redundant) processor scheme to provide for a fault tolerant system. This scheme
shall have bump-less transfer, transparent to the process and, except for annunciation,
transparent to the operator. Transfer between any system redundant elements shall be
annunciated. The preferred redundant scheme is to have the entire program memory
transfer from the primary controller to the standby controller. The redundancy
scheme should also be transparent to the user application program. Processor failure
has to be detected by appropriate processor cross checking or by means of a
watchdog timer that times both set and reset transactions from the processor that it is
watching. It shall be possible for the operator to exchange the processor primary and
backup assignments. Automatic exchange once per day or once per shift would be
desirable.
C. If communication between I/O modules and control module fails, output shall
automatically change to user defined value. I/O module shall match process signal
type. If specified, module shall have ‘smart’ capability. System shall be certified non-
incendive by Factory Mutual (FM), Underwriters Laboratories (UL), or other
certified approval agency. Where area classification or local regulations dictate,
system shall be designed and certified as intrinsically safe. If specified, I/O system
shall be redundant. I/O module contamination shall be Class G3 (harsh) in
accordance with ANSI/ISA 71.04.
D. System cycle time is defined as the time elapsed between a change in state at a
corresponding output based on a change of state of an input, and shall consider
program execution, scan time and output action time. Maximum system cycle time
shall be as short as practical, but shall not exceed 0.5 s.
E. The vendor shall provide controller memory that meets the requirements of the
application software and the overall system performance specifications.
Revision: 1
F. On line changes means that the program can be edited while the SCADA system is
operating. The program checks the syntax of each command as it is entered, and does
not attempt to execute the command until the syntax is correct. The program is not
compiled. This approach, as opposed to generating and compiling the program in a
separate computer and then loading and executing the compiled code, tends to reduce
development time and to simplify trouble shooting and maintenance. System shall
support online modification of configurations and updating of system software
without:
 Interruption of controls (other than directly affected points)
 Requiring system shutdown
G. Interconnection of controllers and auxiliary functions shall be easily modifiable after

system is operational. Configuration shall be capable of being performed on a
personal computer or engineer workstation without the remainder of the system.
Configuration shall be stored on disk or tape, with capability of downloading to
remainder of system later. Capability of copying and modifying an existing
configuration shall be included to allow similar loop configurations to be done
quickly. Reconfiguration (add, delete, or change) shall be possible with system in
operation, with no interference to loops not being reconfigured.
H. The SCADA system shall be capable of remote shutdown of monitored equipment.

The system operator shall have the ability to shutdown a pump, compressor, treating
facility or to close or open a valve that is normally controlled by a local RTU or
SCADA SYSTEM. This override of local control shall be password protected.
8.34 Watch Dog Module
A. Watch dog circuits shall be provided to monitor the timely execution of application
programs. This circuit shall reset the application program when a runaway software
process hangs the system. Noise or an electrical spike sometimes causes this software
hang up.
8.35 Operator Stations
A. Operator stations shall be provided with at least one 17- inch, high resolution CRT
with touch screen, keyboard, mouse or track ball and disk drives.
B. The functions available through the use of a touch screen shall be available through
the keyboard.
C. Operator stations shall be provided with an Ack key for acknowledging alarms. A set
of at least 12 configurable keys shall be provided.
D. Operator keyboard shall be provided with the following dedicated keys:

Revision: 1
 Set-point and output ramping - fast and slow
 Auto and Manual mode switching
 Configurable single buttons for calling up designated displays
 Means to call up alarm displays
E. The SCADA system shall have the ability to communicate over a LAN with other
intelligent devices, for example PLCs, a central computer, or DCS. The vendor shall
provide the communication port required, based on the distribution of these
intelligent devices and the distance between them.
F. Hard drives shall be provided integral to the operator station. Hard drives shall have
the capacity to store system software, operating program, configuration data, process
information, graphs, standard displays, trend program, and historical data. Hard
drives shall not be essential for normal control of process once the system loading
has been accomplished. Two removable media, CD-ROM and Zip drives shall be
provided to load system programs and to backup application program, and
configuration data.
G. Workstations shall be provided with sufficient memory based on the requirements

outlined in the purchase specification. Memory shall be sized to accommodate future
expansion capability of at least 50 percent.
H. Monitors shall have a minimum 640 x 480 pixels, and shall have high-resolution
color capable of displaying mixed alphanumeric and graphic information. It is of
prime importance that the operational displays present the exact status of the plant
under control.
I. Vendor shall provide pointing devices (mouse, track ball) for each operator
workstation.
J. The audible alarm device shall have a minimum of three discernible tones. The tones
shall be assignable depending on alarm priority, or the kind of alarms, for example
process alarms, operation error, and diagnostic alarm.
K. Operator station interface to the SCADA system shall be redundant and pending
password access level, shall provide access to all system devices.
8.36 Peripherals
A. The alarm printer shall log the process and system alarm messages as and when they
occur, and also the alarm history for each shift of operation or on demand from
operator console. Print out shall show as a minimum the tag, the process variable,
description, date and time of occurrence, time of acknowledgment and time of return
to normal.
Revision: 1
B. The logging printer shall provide the following facilities:
 Printing of hourly, shift and daily log
 Report printing on operator request
C. Color screen copiers shall be provided with the system. Copying shall be
accomplished by a single push button operation associated with the screen involved.
The screen copier shall be able to print any screen displayed on any workstation.
Video copiers shall be selectable from any console. Once a copy has been initiated, it
shall be possible to change the screen display without affecting the copy operation
that is, the copier shall have buffer storage for at least two full screens.
D. If specified, an engineering console will require a minimum of one printer. The type
and number required shall be listed in the purchase order.
E. The sequence of events (SOE) recorder is a high performance PC with the

appropriate application and utility software to capture and store data for future
analysis. The vendor shall provide a printer that meets the application requirements
of the SOE recorder. This printer may be a dedicated printer or a system printer if
permitted by the project specifications.
F. Modems shall be provided when telephone lines are available for data transmission
from remote locations. Modems shall have automatic dialup feature. Redundant
modems shall be provided when the data is considered critical in the project
specifications.
8.37 Cabinet, Console Specification
A. Industrial enclosures shall house control loop I/O interface modules and electronics
for performing analog-to-digital and digital-to-analog conversion, multiplexing, and
signal processing. Power supplies shall be mounted near top of cabinets above all
processor equipment.
B. Cabinets shall normally be designed for cable entry through the bottom. Top entry
may be required if a computer floor is not provided. In either case, panduit shall be
furnished to route field wiring from cable entry point to termination panels. 120 V ac
wiring shall be routed in metal panduit or flex metal conduit. Exceptions shall be
carefully evaluated and subject to MARAFIQ approval. Termination panels, if
mounted in I/O rack, shall be a minimum of 0.3 m above bottom of cabinet.
Equipment within
Revision: 1
C. I/O racks shall be arranged in a logical manner for efficient maintenance and
construction. Layouts shall be subject to MARAFIQ approval. If available as a
standard option, sealed I/O rack design shall be specified for maximum dust
protection. Tagging and nameplates shall be specified to facilitate maintenance. Care
shall be taken to review system diagnostic messages to confirm legend on nameplates
and tagging is consistent. Wiring shall be adequately spaced such that any single wire
can be removed from its terminal without disturbing other wire terminations and
without resorting to supplier specific tools, that is, it shall be possible to remove wire
by hand with standard tools. Use of high-density terminal panels shall be subject to
MARAFIQ approval. Wire ducts shall not exceed 50 percent fill. Terminals for low
voltage (50 V or less) signals shall be large enough to accommodate two 1.6 mm
diameter wires. Terminals for 110 V ac (or higher) I/O wiring shall be large enough
to accommodate two 2.75 mm diameter wires. Exceptions to this requirement shall
be carefully considered and shall be subject to MARAFIQ approval. If field cables
with individually shielded pairs are used provision shall be provided on termination
panel or in I/O rack for termination of each shield. Copper ground bus shall be
installed in termination I/O rack.
D. Equipment within an I/O cabinet shall be arranged in a logical fashion for efficient
maintenance and installation. Layouts shall be subject to MARAFIQ approval.
E. Wiring shall be adequately spaced such that any single wire can be removed from its
terminal without disturbing other wire terminations and without resorting to special
tools. Wire ducts shall not be more than 50 percent full. Wiring, both signal and
power wiring shall conform to NEC.
F. Power for the SCADA system shall be provided from UPS. If the SCADA vendor
provides the UPS, the UPS cabinets shall match other system cabinets in size, color
and structure.
G. The vendor shall supply consoles with operator stations, printers, bulk storage media
and I/O devices as called for in the purchase order.
H. Operator consoles shall consist of at least three operator stations or as specified in the
purchase order. Operator stations shall have a keyboard, track ball or mouse and
touch screen as input devices. Each operator and engineering station shall have
access to a printer for logging alarms, system event logs and printing reports.
I. Each system shall be provided with at least one engineering station. The engineering
station shall provide the capability to configure and program all devices within the
system including:
 Configuring all I/O devices, controllers, data storage devices and computing
devices
 Building displays
Revision: 1
 Programming for user generated computer language
 Debugging
 Configuring and building the data base, logic functions, control loops, indicating
points, tuning
 Loops and trouble shooting
J. Each console shall be provided with at least one printer. The engineering station shall
be provided with a printer. The number of printers required shall be stated in the
purchase order. Printers shall be high speed, high quality and quiet in operation. They
shall be laser printers. Printers shall be able to:
 Record time of occurrence and type of alarm
 Perform logging functions
 Record changes in controller status
 Print graphics, trend data, and data base information
 Print screen display
8.38 Equipment Noise and EMI Specification
A. Operators in control rooms shall be assumed to be using hand held radios with
wattage rating of 5 W. Equipment shall be designed to operate such that there shall
be no degradation of performance when these radios are used within 3 m of
equipment.
B. Errors caused by RFI shall not exceed 0.1 percent of span for exposure to a field
strength of 10 V/m over a frequency range of 10 - 1000 MHz.
C. The system shall be provided with provisions for protection against system errors and
hardware damage resulting from electrical transients on power or signal wiring.
These include those generated by switching large electrical loads, power line faults
and lightning induced surges on power or signal cables.
D. The noise level for equipment shall be limited to 60 dBA.
E. Noise measurements shall be based on tests carried out in accordance with

MARAFIQ standards.
Revision: 1
9.0 SOFTWARE SPECIFICATIONS
9.1 System Operating Software
A. Software configuration and programming shall be possible from a personal computer,

as well as from an operator or engineer workstation.
B. System shall be able to test for syntax errors and test run programs for actual
operation.
C. The elements of a good database require that a well-established tagging convention

be followed and maintained. The system shall support an at least twelve-character
tag name with a combination of alpha and numerical characters.
D. Instrument tags on the P&ID and on the instrument index shall match the database as
closely as possible.
E. A point descriptor shall be used to describe the point’s application and shall be well
coordinated with operation personnel. The system shall support a descriptor with 32
characters.
F. Tag IDs shall be unique to the system and access to all tag parameters for
configuration shall be available by tag ID.
G. Each tag number shall have an associated engineering unit assigned to it. The
engineering unit assignment shall be well established at the beginning of a project.
Engineering unit descriptors shall have a minimum of eight alphanumeric characters.
The engineering unit descriptor shall be displayed when the Tag No. is called upon
the screen.
9.2 Engineering / Configuration Software
A. The system shall meet the application standards of IEEE 488 and 802.3.
B. The system shall be provided with a database configurator that can configure the
system either using a personal computer or from the engineering workstation.
C. All the configuration functions shall be performed using this software to generate the
database and the standard displays for the entire system.
D. Some of the desirable features of the configurator are listed below:
 A facility to cut, copy and paste shall be provided. This feature facilitates
creating multiple points that have similar parameters, except for change of tag
name, point address, descriptors, range, and alarm set-points. This ‘template’,
once defined, can be used over and over again to build points that are similar.
Revision: 1
 Revisions to database shall automatically update all modules and tags.
 All configurations shall follow validation procedures.
 Any invalid configuration data shall be flagged and affected parameters

indicated.
 It shall be possible to revise database on-line without having to stop the process.
 Means shall be provided to prevent invalid configuration changes from affecting

the process.
 Configuration data shall be verified and the point shall be placed on manual or
inactive mode to prevent any invalid data which might affect operations.
 Configuration data shall be saved on both removable and non-removable media

for backup purposes.
 Redundant on-line storage shall be provided for configuration files.
 Changes to a control block / loop in a control module shall not affect other
control loops in the module.
E. Offline configuration shall have the applicable features of online configuration.
F. Remote engineering and configuration shall be possible for anyone with the proper
access level and appropriate software loaded on their PC or computer.
G. The system software shall be provided with a utility, which shall have as a minimum
the following features:
 Ability to search the database and provide information
 Provide a cross-reference listing of the database containing tag id, tag descriptor,
point type, and hardware address
 Provide an alphanumerical sort of the database by any field
 Print, display and save to any media
 Ability to save and restore database
H. A database editor shall be provided. The editor shall have the following features:
 It shall be possible to modify or generate a database using the editor

Revision: 1
 It shall be user friendly and intuitive and employ fill-in-the-blank type screens
 The system shall provide a step by step guide for completing the information
required to complete the database
 It shall be possible at the beginning of a project to build the database in a

personal computer using a commercially available database such as Microsoft
Access and later download it to the system using a converter
I. The system shall be provided with the capability to build custom graphic displays to
present data to operations in a pictorial fashion. A custom graphic display shall have
the ability to present process and control schematics, alphanumeric text, and real time
data and face plates all in one page.
J. The system shall have the capability to build at least 400 graphic pages.
K. Operator shall be able to operate the control strategies, change set points, mode and
outputs.
L. The system shall be provided with a utility to build and modify custom displays using
graphical user interface (GUI) and conversational type programs. Building and
modifying graphics shall be an engineer’s function and shall be keylock or password
protected.
M. It shall be possible to build graphics with at least 300 dynamics parameters in one
display (PV, set-point, and output) without impacting update time.
N. Graphic displays shall be updated at least every four seconds. Simpler graphics with
less data shall be updated faster.
O. The color coding for, for example display line, process variable, text and output, shall
be user configurable.
P. Process data shall be displayed in both graphical and bar graph format. The height of
the bar shall be configurable on an individual tag basis.
Q. A standard set of commonly used symbols in refinery, petrochemical and power

plants shall be available from a menu template.
R. The system shall support self-documentation, including printed organizational

summaries, in a convenient manner. The project design shall include documentation
in a form that can be easily updated by the plant. Tabular data in a common form, for
example spreadsheet or database formats, is desirable. Loop sheets shall be required
for control loops and circuits with multiple functions that are linked. Transfer of
documentation information to other packages, for example CAD drawings and
databases is desirable. The objective is single point entry for changes, with self-
synchronization of all other documentation.
Revision: 1
9.3 Control Processor Software
A. The SCADA system controls shall be capable of performing all required control
functions. As a minimum, loop controllers shall be capable of P, PI, or continuous
proportional, integral, and derivative (PID) control, batch control, logic control, and
user programmable control. Non-linear and self-tuning capabilities shall be
configurable for each loop. Tuning adjustments for controllers shall be readily
accessible at operator station. Each controller shall be capable of serving as primary
or secondary controller in a cascade loop. Controller parameters shall be updated
each time a block is processed by the CPU. Cycle time shall be selected as required.
Control system shall be capable of processing entire control loop within 1/2 s.
Auxiliary functions shall be available for performing functions such as ratio, bias,
square root, summing, and linearizing of thermocouple signals. Controllers shall be
capable of maintaining regular scan time while performing adjustments to all control
loops, logic sequences, and programs configured.
B. Controllers shall have capacity for standard proportional, integral, and derivative
control modes. Modes shall be available individually or in combination. Cascade and
ratio from other controllers or inputs shall be supported, preferably via software links
rather than hardwire. Controllers shall have provisions for limiting reset windup in
primary controller and higher-level cascade controllers. Output, set point, and
integral limits shall be provided. Adaptive gain algorithms and self-tuning shall be
available. Balanced and bump-less transfer between control modes (cascade,
automatic, and manual) and between control schemes, for example override control,
shall be provided. Override control shall prevent windup of non-selected controller(s)
such that quick transfer and response is provided if non-selected controller(s) need to
assume control. Control capabilities shall be available as software configuration
within controller, without requiring custom programming. Available algorithm set
shall be investigated, considering process requirements to confirm their suitability.
C. Controllers shall have capacity for performing interlocking, counting, and

sequencing. These functions shall be configured through use of, for example ‘AND’,
‘OR’, and logic gates. Logic gates shall be discrete I/O; operator inputs; and outputs
of other logic gates. Logic gates shall be combinable into series and parallel
configurations. Ladder logic or Boolean logic programming capability shall be an
acceptable substitute for logic gates. Logic functions on numeric values, for example
analog, accumulation, pulse rate, numeric, and tuning constants shall be supported,
for example comparisons (‘greater than’, ‘less than’, ‘greater than or equal’ and
‘within ‘x’ of’) with adjustable dead-band.
Revision: 1
D. Batch programming shall comply with ISA 88. If required by process, controllers
shall have capability of performing batch control. In this mode, controllers shall be
programmable to perform sequential steps to control process. Such steps shall consist
of both continuous PID control and discrete logic functions. Programming shall be
able to adjust parameters, for example set points, ranges and modes, for continuous
PID algorithms as process moves from step to step. At the same time, programming
shall have ability to actuate on/off outputs based on discrete inputs, analog inputs,
and program step. In addition, system shall be able to store multiple ‘recipes’.
Selection of a recipe by operator shall set up, for example, controller with proper set
points and sequencing for that recipe. Timers shall be provided. Timers shall support
timing of, for example steps and actions, and triggering of alarms and events upon
time-out. Reporting shall be supported. Report generation shall be periodic (time
based), event driven, and upon demand. Reports shall include historical and current
values. Standard report formats shall be provided, with a ‘free format’ report option
included. System shall allow for debugging of programs by supporting at least single-
step execution and switchable statements that are executed only if a specific DEBUG
flag is set.
E. The following list of instructions shall be available to develop the application

program:
 Math instructions: add, subtract, divide, multiply, and square root. These
functions shall be available for real numbers and integers
 Relay logic: These shall include N.C., N.O., transitional contacts, standard relay
coil and latched relay coil
 Timers and counters: on delay, off delay timers, up and down counters. Time
base shall be from tenths of seconds to hundreds of hours
 Comparison elements: greater than, less than, equal to, not equal
 Data manipulation: bit rotate left, bit rotate right, bit shift left, bit shift right,
BCD to binary, binary to BCD
 Advanced functions: matrix compare, matrix and, or, table to register move,
register to table move
 Control algorithm: PID, lead-lag
 Program statements: jump to, label, and skip

Revision: 1
9.4 Operator Station Software
A. System network and console data rate shall be such that operator initiated control
changes take effect in the control processor within 1 s. Display data shall be updated
at least every 5 s. The system shall operate such that operators can access displays
needed with a minimum of requests (keystrokes).
B. Graphical design shall be intuitive and shall follow a site or plant standard in use of
colors, shapes and responses to operator actions. Such standardization enhances
operator efficiency and positively affects safe operation of system, particularly
during upset conditions when quick scanning of information and response is
essential.
C. Screen keys (or targets) shall be provided to transfer control loops bumplessly
between automatic and manual. Additional keys shall be available for access to
adjustable control parameters: setpoint, output, ratio, and bias. Keys assigned to
parameters not configured for a loop shall be disabled during control of that loop.
D. Keys shall be provided to ramp selected control parameter positive or negative. It

shall also be possible to directly enter a new value for selected control parameter
without ramping through intermediate values. Changes to a parameter shall appear on
display as they occur.
E. Additional keys shall be provided as necessary to access various displays, interrogate

system status, and operate auxiliary peripherals.
F. Pressing of illegal keys during any operation shall be ignored or shall indicate an
error condition on display. Data entry that will inadvertently alter control loop
configuration procedures shall be accessible by means of a security password.
G. As a minimum, the following displays shall be available at operator stations:
 Measured variable, set point, and output shall be displayed for selected control
loops. Each loop shall have adjustable alarm limits. If a limit is exceeded, a
visual and audible alarm shall be generated, with the loop in alarm clearly
identified on display.
 Group displays shall provide detailed information on a selected group of

variables. Groups shall include controlled and indicated variables. Data
displayed shall include variable identification, analog and alphanumeric
indication of process variable value, process upper and lower absolute and
deviation limits, and, if applicable, control mode, set point value, and output
value. Control of a selected loop shall be possible from display, with the loop
selected clearly indicated on display.
Revision: 1
 Individual detail display shall provide detailed information for a selected block.
This display shall contain the same information as the group display, with
additional alphanumeric data pertinent to the loop selected, for example
configuration information.
 Real time trend data for any variable shall be available for display, including
process dynamics. Range of variable shall be displayed in alphanumeric with
trend plot. It shall be possible to display at least three trend plots simultaneously.
Display shall be updated as new process values are obtained.
H. The system shall be able to create and store a library of custom graphic symbols.
Touchscreen, mouse or trackball shall create graphics. System shall be capable of
printing configuration of logic built into graphics.
I. Control system shall be capable of providing process variable high and low limits,
deviation from set-point limits, and output high and low limits. Limit values shall be
adjustable at operator station. Exceeding an absolute or deviation limit shall result in
both audible and visual alarms. Alarm condition shall be immediately indicated to
operator, regardless of display being viewed at time of alarm. Operator station shall
have a button for acknowledgment of an alarm condition. Alarm acknowledgment
shall cause flashing video to cease, but alarm indication shall remain as steady
inverted video or red until alarm condition is corrected. Alarm history and current
alarm summary shall as a minimum show last 100 alarms in chronological order.
Alarms shall be sorted by sequence, priority, or status. If specified, alarm sequence of
events capability with 100 ms resolution shall be provided. System shall inform
operator of malfunctions before they become ‘fatal’. For example, if system has
redundant 24 V dc power supplies, each of the power supplies shall have a status
input to system such that failure of a power supply can be sensed and repaired while
redundant supply maintains system operation. System shall have alarm capabilities to
notify operator of process upsets. Notification shall be made on CRT. In addition,
other direct indication, for example back light keyboard keys, is desirable. Screen
call up shall require only single actions, for example one keystroke or one touch
target, to access critical operating screens. System shall be capable of sustaining
standard operation during process upsets in spite of large number of alarms generated
and output adjustments required. Consoles shall continue to enable operators to view
and control process with minimal slowdown (for example a factor of two but in no
case longer than 5 s response to change screens) by system while logging all alarms
and updating all changing values.
J. Visual alarm shall appear on the displays indicating group or particular loop in alarm,
as configured. Alarm indication shall consist of group or loop alphanumeric
identification displayed as flashing inverted video or flashing red. Visual alarm shall
be generated if any process variable exceeds absolute or deviation limits. If loop in
alarm is accessed, visual alarm indication shall continue on display and remain until
alarm condition is corrected.
K. Audible alarms shall be solid state, pulsating type, installed in operator station.
Revision: 1
L. System shall permit establishment of alarm priorities to guide operator quickly to the
most urgent alarm condition. Alarms shall be capable of being suppressed based on
alarm priority.
M. A printer shall be included to record time of occurrence and type of each alarm on
system. Alarm shall be individually configurable to print on specified basis of
priority. System files shall include alarm history such that data on alarm occurrences
is readily available to operator.
N. The SCADA system shall provide for abnormal conditions occurring either within
the system or in a sub-system. In particular the following events shall be handled:
 Alarm clearing before acknowledgment
 Printer breakdowns
 Alarm avalanches (flood)
O. The system shall be able to assemble data and to print various kinds of standard
reports, all of which shall be available on demand via a single keystroke. The system
shall provide the following basic types of reports as a minimum:
 Event lists
 Operator action reports
 Custom reports with fixed or variable formats, or both
P. The above reports shall be able to use real time data, historical data, trend data or
calculated data generated or stored on any node in the system or any connected
device to the system, for example PLCs, supervisory computer or process computers.
Logging functions shall be capable of being initiated by the operator on demand, or
on a predefined schedule. All points in the system shall be available for logging. A
logging report function shall be available on the operator workstation to enable the
engineer to make free-format reports of text and data that may be printed on a printer
connected to the operator workstation. The report types shall be:
 On demand
 At a predefined time (for example hourly, shift or daily)
 Event triggered
 Real time events with six hours worth of data to help in diagnosing shutdown
incidents. These reports shall be stored on separate files from historical and trend
data
Revision: 1
Q. Events shall be capable of being historized, and subsequently recalled for logging or
display purposes. In the event of a printer failure, the system shall provide an
alternative path for printing or maintain the events in the console print buffer and
alert the operator. In any case the alternative print path shall be readily accessible and
print out the data without loss.
9.5 Trending
A. System shall be capable of real-time and historical trends. Trends shall display tag
name, engineering units, span, and alarm status. Control points shall be controllable
from their trend display. At least three points shall be trended on the same plot,
distinguished by different colors. Multiple plots shall be displayed on the same
screen. Trends shall have scroll feature to display value and time at a selected point,
as well as adjustable time base and measurement span. Historical trend data shall be
stored by system for display at a later time. System shall as a minimum have capacity
to trend all points with a 15 s resolution for 96 hours. All points (including associated
set points and outputs) shall be trended. ‘Windowing’ shall be provided to allow
display of a trend as part of an active graphic display. Variables to be stored shall be
selectable at operator station. Stored data shall be available for display at any time in
same manner as real time trend display. There shall be no interference between
historical data storage and real-time trend data display. Historical trend data shall be
available at computer interface.
9.6 Reports and Logs
A. The report function shall allow the user to define fixed or free format logs, define
periodic execution and to select the output device. The fixed format logs shall report
current and historical data and display the information on any operator or engineer’s
station. The report generator shall have the ability to specify report generation on
demand or on a time schedule basis. It shall be possible to define the output device
(printer, or CRT storage media).
10.0 SYSTEM PERFORMANCE
10.1 System Availability
A. The control system, when in a redundant processor configuration, shall have an

availability requirement of 99.99 percent when a MTTR of less than 60 minutes is
assumed. The vendor shall demonstrate that the system has this availability. Single
point component failure shall not result in loss of availability of the control system.
10.2 System Reliability
A. Supplier shall provide a listing of the failure modes of the SCADA system and the
impact of such failure on the system performance. The MTBF and MTTR numbers
for the system shall be provided.
Revision: 1
10.3 Performance Specifications
A. The Supplier shall provide a system that will meet the following performance
specification:
 Each operator station shall have access to 2000 tags
 Each operator station shall have access to 200 user-defined graphics
 All displays and graphics when accessed, including fully active dynamic
elements shall be complete within 4 s
 The frequency update for real time data shall be at least once every 4 s
 Historical data display shall occur within 5 s of call up
10.4 On Line Replacement
A. All system components shall be easily removed and replaced. I/O modules and
redundant modules and devices shall be removable with the power on, without
disturbing field wiring or other wiring not directly associated with the item being
removed.
10.5 System Diagnostics
A. Supplier shall provide a diagnostic program for off-line testing of all devices in the
system.
B. The system shall be provided with continuous on-line self diagnostics to monitor the
state of all the nodes and communication cables in the system including:
 Control processors
 Communication processors
 Input / output modules
 Operator workstations
 Engineering workstations
 Communication cables
 All peripherals
C. Each diagnostic shall be capable of recognizing the following operational states:

Revision: 1
 On-line: Normal and fault restricted operation
 Active: Fault restricted operation, standby state, test state
 Inactive: Failed state identifying nature of failure, turned off state, physical
removal from the system.
D. Device diagnostics shall be available showing the status of all devices in the system.
As a minimum the following shall be included:
 System status display showing network devices and their health
 Status of all communication systems showing each device and the

communication path (primary active or secondary active, cable A or cable B in
service)
 the detailed loading status of each device or cable
E. Diagnostic displays shall be provided for each module in the system. It shall be
possible to use these in trouble shooting the system. An on-line help screen shall be
provided, which shall provide an interpretation of the error codes, and diagnostic
messages.
10.6 System Clock and Synchronization
A. The SCADA system clock shall be synchronized with the network clock and all
devices on the network, to ensure synchronous communications in the transmission
and reception of data and control characters.
11.0 DRAWINGS, DOCUMENTATION AND DATA REQUIREMENTS
Documentation of the complete system shall be provided in accordance with, but not limited to, the
general requirements in this specification and as listed in the material requisition document.
11.1 Design Drawings
A. Prior to start of hardware fitting out the SCADA System Supplier shall submit
relevant drawings for review and approval in accordance with the Drawing and Data
Commitment Form.
B. After completion of FAT the SCADA System Supplier shall issue a complete set of
updated drawings reflecting any modifications made during the FAT.
C. Final as built documents shall be submitted by SCADA System Supplier after

incorporating field modifications up to Contractor turnover of the SYSTEM.
Revision: 1
11.2 Design Interface
A. The SCADA System Supplier shall develop / define the system configuration with
input from Contractor. Configuration definition shall be provided to Contractor /
Company for review and comment.
B. Contractor shall supply via electronic means to SCADA System Supplier information
to configure the I/O databases. The minimum information to be provided by
Contractor will include tag names, service descriptions, I/O type, engineering units,
scale ranges, alarm settings and trip points, IS loop and special power requirements.
As necessary the Contractor shall provide to the SCADA System Supplier P & IDs,
cabling interconnection drawings, logic diagrams or cause & effect charts, and
control building layouts showing equipment positions and cable routing, etc.
C. SCADA System Supplier shall supply electronic files of the configured databases for
importing by Contractor into the instrument index database.
11.3 Supplier Documents
A. The SCADA System Supplier shall furnish all drawings, documents, data and
software required to accurately define the design of the SCADA System.
B. As a minimum the following shall be provided:
 Supplier document index
 Spare part requirements
 Catalog data
 Quality plan
 Manufacturing plan / schedule
 Inspection and testing plan
 Test data / records
 List of materials
 Overall system block diagram
 Interface block diagram
 Dimensional outline drawings

Revision: 1
 Location / equipment layouts
 Physical wiring diagrams
 List of cables
 Power and earthing distribution diagrams / schedules
 Heat dissipation and power consumption
 Certificates of compliance
 Mean Time between undisclosed failure & disclosed failures data
 Installation, operation and maintenance manuals
 System loading calculations
 System availability calculations
 Functional design specifications
 Engineering manual containing all application configuration and operating data
 FAT documentation (procedure / test records)
 SAT documentation (procedure / test records)
 Standard software manuals (original CD’s of system software and licenses)
 Electronic back-up of system configuration and application programming
11.4 System Logs
A. A system log (punch list) shall be maintained once system integration starts and
through FAT. The log shall indicate all problems noted by date, type of problem and
action taken to correct the problem. The system shall not be released for shipment
prior to the clearing of all log items.
B. A system log (punch list) shall be maintained once system integration starts at site to
mechanical completion. The log shall indicate all problems noted by date, type of
problem and action taken to correct the problem. The system shall not be accepted by
Company prior to the clearing of all log items.
Revision: 1
11.5 Requirements with Proposal
A. SCADA System Supplier shall include the following in his technical proposal:
 Project execution plan for manufacturing, testing, site survey and installation
(tie-in to existing system both hardware and software):
 Organization chart
 Preliminary Schedule - preliminary project schedule for the proposed system

identifying major milestones including equipment design, manufacture, testing
and delivery. The schedule should include all SCADA System Supplier,
Contractor and Company activities critical to the proper management of the
work. The schedule should also identify dates for information to be supplied by
Contractor
 Communications
 Location of project execution
 Reporting
B. A list of conflicts / exceptions / deviations referenced to the relevant paragraphs of

this specification and all referenced specifications, codes and standards which are
part of this specification, if applicable.
C. List of concerns and / or optional proposals.
D. Itemized list of equipment separated by unit or area.
E. Technical literature and product specifications on the equipment such as network

switches, servers, workstations, printers, logic solvers (including available standard
algorithms, libraries and templates), I/O cards, archive devices, communications
subsystem, etc. included in the proposal.
F. System block/architecture diagram including interfaces to equipment not supplied by

the SCADA System Supplier.
G. Commitment to supply drawings and data required by Contractor, complete with

dates for submittal.
H. FDS Contents page/format.
I. Preliminary equipment layout drawings with dimensions.
J. Proposed termination cabinet design and layout.

Revision: 1
K. General grounding and power requirements.
L. Standard software capability.
M. Details and costs of software options that may be applicable to this project.
N. Details and costs of software licensing requirements.
O. List of standard pre-configured serial link software packages which are available to
interface with the DCS.
P. Price list of commissioning and start-up spares and also a spares list for two years
continuous operation.
Q. Price list of consumables such as disks, printer paper and accessories, tapes, etc.
required for 12 months operation.
R. The procedure and length of time required for repair and/or replacement of parts.
S. Power requirements of all the users and also the heat dissipation of consoles and
equipment cabinets.
T. Suppliers quality control procedures for inspection and testing of all parts, assemblies
and complete system, including procedures for thermal cycling, inspection and
testing of the parts, circuit boards, assemblies of the entire system.
U. Reliability and Availability calculations. Field experience data is preferred.
V. Details of diagnostics and fault reporting including any covert faults which are not
expected to be revealed by the automatic test facility and diagnostics.
W. Details of suitable training courses, their duration's, schedule and associated costs for
the following levels of personnel: engineer; maintenance technician, operator.
Availability for On-site training After Order
X. Complete cabling, wiring and schematic drawings.
Y. System Operating, Maintenance and Engineering manual.
Z. Power and grounding plan.
11.6 After Kick Off Meeting
A. Specifications for all interfaces and programs. Fabrication drawings showing

dimensional detail for cabinets and consoles.
Revision: 1
B. Drawing showing equipment location, terminal panel location, power entry point,
and breaker location.
C. A system startup procedure describing the sequence of events for powering and
commissioning the system. Provide a boot up procedure for fast system recovery in
case of system lockup or loss of power.
11.7 As Built
A. After Commissioning the Unit, Contractor shall provide marked-up database,

cabling, wiring and schematic drawings for Seller to update as final “As Built”.
11.8 Electronic Documentation
A. All hardware and software manuals
B. Two copies of the database in electronic form
12.0 INSPECTIONS AND TEST
12.1 Factory Acceptance Test (FAT)
A. The Factory Acceptance Test (FAT) shall be designed to demonstrate the complete
integration and function of the SCADA System according to the requirements of the
specifications. All SCADA System shall be subjected to a factory acceptance test at
the vendor’s facility. MARAFIQ or its affiliate Engineers will witness the test. Prior
to FAT, the vendors shall have completed their own check for hardware and software
functionality and integrity. Seller shall submit FAT procedures and schedules twelve
(12) weeks prior to the FAT for review and approval. Seller shall provide all
necessary test and simulation equipment. Contractor shall reserve the right to
witness all testing.
B. Test records and results shall be kept and subject to review by Contractor at any time.
In any event, these records shall be submitted to Owner eight (8) weeks after FAT.
C. Terminal, wiring and equipment labeling shall be verified to match with wiring
diagrams and drawings. Prior to the FAT, the system shall be fully operable and
fully tested by Seller.
D. Seller shall demonstrate the operation of diagnostic and maintenance functions

provided with the system. Errors shall be simulated to demonstrate the capability of
the system to detect and report errors.
Revision: 1
E. Seller shall correct all discrepancies found during the FAT. Contractor may require
the suspension of the FAT until any such discrepancy has been corrected. After the
discrepancy has been corrected, Seller shall repeat the procedure or perform any
other testing required to verify correct operation of the system and that the
discrepancy has been corrected.
F. Any suspension or retesting that may be imposed due to discrepancies shall not
constitute a change. Seller shall document all discrepancies and verification of
correct operation. Unless otherwise agreed, all discrepancies shall be corrected prior
to shipment of the system. Seller shall update all affected documentation to reflect
the system at the completion of FAT.
G. The FAT shall also include a test of the communication between the DCS and the
SCADA System as well as the complete functionality of the DCS HMI. This test
shall be conducted at the SCADA System integrator’s facility.
12.2 Site Acceptance Test (SAT)
A. The Site Acceptance Test (SAT) procedure and schedule shall be derived from the
FAT procedure. The SAT procedure shall be prepared by Seller and presented
twelve (12) weeks prior to the SAT. The SAT shall also verify any interfaces that
could not be verified during the FAT. Seller shall propose in the quotation the
representation planned for the SAT.
12.3 Sustained Performance Test (SPT)
A. The objective of the SPT is to determine the long term stability and availability of the
SCADA SYSTEM under normal operating conditions. It will also verify the ability
of the SCADA System to report any and all malfunctions in an easy to understand
manner and Seller's ability to diagnose and fix any problem in a timely manner. The
test commences when the SCADA SYSTEM assumes a portion as specified by
Contractor. Contractor will conduct the SPT over a sustained period of 30
consecutive days (or longer under agreed conditions). The criteria for success will
include at least 99.9% availability (in the standard statistical sense) and not more than
one hardware and/or software failure during the 30-day period.
B. A failure is defined as any occurrence preventing full utilization of the SCADA

System. Availability will not be affected, and the SPT will be temporarily suspended
in case of any failure caused by Owner supplied equipment or services.
Revision: 1
13.0 MAINTENANCE MATERIALS
13.1 Recommended Service and Spare Parts List
A. Seller shall provide with the quotation a recommended list of one (1) year start-up
spares and two (2) years operating spares. The spare parts list shall:
 Identify the part number and description of the item. Associated major
equipment part is recommended for.
 Source of the part including third party suppliers and availability in Indonesia
 Price of part
 Lead time for part
B. Spare parts shall be guaranteed available for the period specified. Any spare parts
used by Seller during the warranty period shall be replenished at Seller's expense.
13.2 Maintenance Training
A. Seller shall provide recommended maintenance training quotation.
B. This requirement shall be quoted only for large and/or complex SCADA System that
are tightly integrated with the DCS or PLCs that perform specialized control.
13.3 Maintenance Service
A. Seller shall provide a recommended long-term maintenance/service agreement

quotation for on-site maintenance service.
B. Any maintenance/service proposal shall identify the qualifications of servicemen,

types of services provided, limitations and restrictions with regards to the work
performed, requirements for special tools, parts, any other special requirements, etc.

MQ SP I 7012 3 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MQ SP I 7012 3 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Power and Water Utility Company for Jubail and Yanbu (MARAFIQ) Master Specification: MQ-SP-I-7012-3

Project Name: Date: 14 Jan 2011

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

Revision Date Originator's Reviewed/Checked By Pages

APPROVALS SIGNATURES DATE

Lead Engineer Thomas B. Robinson

ISSUED FOR : Construction X Other Approved

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

A 8/30/2010 Issued for Approval, Table of Contents Only

0 11/04/2010 Issued for Review/Approval

1 1/14/2011 Issued Approved

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

1.0 SCOPE ........................................................................................................................................................7

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

7.3 Memory Sizing ..........................................................................................................................18

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

8.34 Watch Dog Module ...................................................................................................................34

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

13.1 Recommended Service and Spare Parts List.........................................................................56

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

A. This specification defines the minimum requirements of Supervisory Control and

A. The intent is that a standardized approach be used by the SCADA suppliers,

1.3 Scope of Supply and Responsibility

E. The SCADA SUPPLIER shall provide comprehensive detailed functional design

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

2.1 Codes and Standards

B. American Gas Association (AGA)

 Report 3 : Orifice Flow Calculations

C. International Electrotechnical Commission (IEC)

 IEC 73 : Specification for color of indicator lights, push-buttons, annunciators

 IEC 79 : Electrical equipment for use in hazardous locations

 IEC 529 : Degrees of Protection of Enclosures

 IEC 617 : Graphic Symbols for Electronic Diagrams

 IEC 60364-4-41 : Low Voltage Electrical Installations

 IEC 61508 : Programmable Electronic Safety Systems

 IEC 61131-3 : Programmable Controllers - Part 3: Programming Languages

D. Institute of Electrical and Electronics Engineers (IEEE)

 IEEE 488 : Standard Digital Interface for Programmable Instruments

 IEEEE 802.3 : Standard for CSMA/CD Media Access Control (‘Ethernet’)

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

E. International Society of Automation (ISA)

 ISA 5.1 : Instrumentation, Symbols and Identification.

 ISA 5.2 : Binary Logic Diagrams for Process Operations.

 ISA 5.3 : Graphic Symbols for Distributed Control/Shared Display

 ISA-18.1 : Annunciator Sequences and Specifications

 ISA-18.2 : Management of Alarm Systems for the Process Industries

 ISA 50.02 : Fieldbus Standard for Use in Industrial Control Systems

 ISA 71.04 : Environmental Conditions for Process Measurement and Control

 ISA 88 : Batch Control

F. ISO : International Organization for Standardization

G. NEMA : National Electrical Manufacturers Association

 NEMA ICS-6 - Enclosures for Industrial Controls and Systems

H. NFPA : National Fire Protection Association

 NFPA 70 - National Electrical Code

2.2 Project Specifications and Drawings

B. MARAFIQ Standards and Specifications

Specification No. Title

SPECIFICATION - PROCESS CONTROLS - SCADA SYSTEMS

MQ-SP-I-7016 Control Panels

3.0 DEFINITIONS AND ABREVIATIONS

A. Terms used in this document are defined as follows:

SCADA SUPPLIER Supplier of SCADA SYSTEM equipment purchased by

ADC Analog to Digital Conversion