SA-000-R-11143 Rev T01 4300 Handbook of Bolts and Bolted JointsSpec 31.10.2008

Sultanate of Oman
Ministry of Transport and Communications

Development of Salalah International Airport
Main Contract 5
Project Specification
Civil Works - 4300 Control and Monitoring Systems
Special Specification
October 2008
Sultanate of Oman
Ministry of Transport and Communications
Development of Salalah International Airport
Main Contract 5
Project Specification
Civil Works - 4300 Control and Monitoring Systems
October 2008
Report no. SA-000-R-11143

Issue no. T01
Date of issue 31.10.2008
Prepared FRA
Checked KWM
Approved STJ/NIER
Main Contract 5 - Project Specification 1
Civil Works - 4300 Control and monitoring systems
Table of Contents
4300 Control and monitoring systems 3
4301 General 3
4301.1 Scope 3
4301.2 Interfaces 3
4301.3 References 3
4301.4 Design basis 4
4301.5 Functional requirements and materials 4
4301.6 Documentation in tender 5
4301.7 Shop drawings 6
4301.8 Installation and execution 8
4301.9 Testing and commissioning 8
4301.10 As-built documentation 8
4301.11 Operation and maintenance 12
4301.12 Training 12
4302 Architecture of CMS 13
4302.1 General 13
4302.8 Training 16
4303 Hardware requirements 16
4303.1 General 16
4303.8 Training 20
P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

000-R-11143_Rev T01_4300_Control and Monitoring Systems_Spec Spec_31.10.2008.DOC .
4304 Human machine interface (HMI) 20

4304.1 General 20
4304.9 Training 26
4305 Additional requirements 26
4305.1 General 26
4305.7 Documentation 28
4305.9 Training 28
Revision Log 29

4300 Control and monitoring systems
4301 General
4301.1 Scope
This document specifies basic requirements for the various control and
monitoring systems (abbreviated CMS) that control and monitor technical
systems in the airport.
The document applies to all CMS which include a SCADA functionality, with
the exception of the following ones:
• The Airport SCADA system
• Building Management Systems (BMS)
The requirements in this document shall be applicable for each individual CMS
in conjunction with the specific reqirements for this system. In case of
discrepancies, the specific requirements for the individual CMS shall apply.
4301.2 Interfaces
Each CMS shall exchange data with other IT based systems for operation and
maintenance. The communication with these other systems shall take place
through the Airport Community Network, ACN. These interfaces are specified
in the following sections of this document. They include but are not limited to
the following:
• An interface to the Airport SCADA system for overall monitoring of

various technical systems in the airport.
• A general Internet interface which provides read-only access for internet
browsers to access displays and lists.
• An interface to the Storage Area Network (SAN) for backup of
configuration and acquired data.
4301.3 References
The design, workmanship, materials and equipment, testing and documentation
associated with this work shall comply with the latest issue, including all

amendments, of the appropriate Omani, British and European Standard

Specifications. Particularly relevant references are:
Number Title
BS EN ISO 9241 Ergonomic requirements for office work with visual display
terminals (VDTs)
BS EN ISO 11064 Ergonomic design of control centres
EN 60617 Graphical symbols for diagrams
BS EN 61000-6, part 1 - 4 Electromagnetic Compatibility (EMC) - Generic standards
BS EN 61131 Programmable controllers
IEEE 802.1q GVRP and VLAN Tagging
IEEE 802.3-2005 LAN/MAN CSMA/CD Access Method
IETF RFC 2131 Dynamic Host Configuration Protocol (DHCP)
IETF RFC 1305 Network Time Protocol (NTP)
4301.4 Design basis

Each CMS shall be designed as a powerful tool for operation and maintenance
of the particular technical system which it controls and monitors. It shall
provide the facilities required by the different categories of users, for example
operation personnal, maintenance personnel and management.
The CMS shall be designed with high realibility and high availability.
Unavailabilities because of equipment faults and maintenance activities shall be
limited to values that are acceptable for the operation of the respective technical
system in the airport environment.
4301.5 Functional requirements and materials
Scope of supply
The scope of supply shall include all deliverables - hardware, software and
services - which are necessary for the implementation of a fully functioning
CMS. This includes, but is not limited to, all deliverables described in this
document.
User licenses for all used software shall be provided by the Contractor.
The contractor shall supply spare parts for two years of operation. Refer to
section 4301.6.
General quality requirements

The CMS shall be based on a combination of hard- and software products
which has been proven in practice in comparable applications.

All hard- and software products shall be based on state-of-the-art components

and functional principles, and they shall be manufactured by internationally
recognised companies with a proven record of quality and service in the GCC
countries.
Manufacturerers which have no proven record of quality and service in the

GCC countries may be accepted if is can be documented to the satisfaction of
the Engineer that they have such a record in at least five (5) other countries.
The Engineer has the right to reject hard- and software products, including
combinations of such products that, in his opinion, do not satisfy the above-
mentioned requirements or criteria.
If one or more manufacturers should introduce new versions of hard- and

software products that form part of the CMS, the Contractor shall deliver the
latest proven versions of these hard- and software products in order to ensure
that the solution is state-of-the-art at commissioning time.
Facilities for service

The scope of supply shall include such hard- and software facilities for service
as are necessary for maintenance and further development. These facilities
include but are not limited to:
• Hard- and software tools for diagnosis of hard- and software problems,
including portable service terminals if required.
• Hard- and software tools for programming/configuration of CMS functions
such as:
- Automatic functions for control and monitoring
- Functions of Human Machine Interface
Configuration control
The Contractor shall establish a system of procedures for control of the CMS
configuration, both hard- and software. The configuration control system shall
fulfil the following requirements:
• Identification of all hard- and software items.

• Control of changes in accordance with well documented procedures.
• Ensure that all hard- and software items are in a known state.
• Reporting and handling of faults and deficiencies.
• Prevent the use of unapproved components
The configuration control system shall be described in the Contract Documents.
4301.6 Documentation in tender

The Contractor shall submit the following information in his Tender:

• Overall and detailed configuration diagrams of the CMS and its

subsystems.
• Functional descriptions of CMS and subsystems.
• Specification of scope of supply including hardware, software and
services.
• Manufacturer's literature describing the hard- and software products that
make up the CMS solution.
• Documentation of the suitability of the system solution for the specific
application, including information on reference installations.
• List of proposed spare parts, with prices, for two years of operation. This
list shall provide the basis for the contractual agreement on supply of spare
parts as mentioned above in section 4301.5 Scope of supply.
4301.7 Shop drawings

The Contractor shall prepare a system description which provides a precise and
exhaustive definition of the scope of delivery, and of how the Contractor will
implement the CMS and fulfil all the requirements of the Contract concerning
structure, function, implementation methods, used products, documentation,
control/test, maintenance and training.
The system description shall include a definite specification of the interfaces to

other equipment and systems. The Contractor shall check the interfaces
described in the Tender Documents and correct discrepances, if any.
The Contractor shall not commence the implementation works - procurement,

programming and configuration - before having received the Engineer's
acceptance of the system description. The Engineer's acceptance does not
relieve the Contractor of his responsibility for a fully functioning CMS in
accordance with the Specifications and the related documents
The system description shall include, but not be limited to the following
information:
• Hardware:
- Configuration drawings for the entire CMS and for its partial systems.
- Comprehensive scope of supply, structured according to partial
systems.
- Mechanical specifications for all equipment (dimensions, mounting
and environmental specifications).
- Specifications concerning electrical installations of all equipment
(cable types, power supply, earthing).
- Principle circuit diagrams for electrical connections between the CMS
and sensors/actuators, including switching between local operation
and remote operation by the CMS.

- Use of tag numbering system (please refer to document no. AL-000-

H-13012) for numbering of system parts, signals and variables.
- Guidelines for labelling.
- Revised P&I diagrams, revised signal data base.
- Drawings and specifications for cabinets, panels, switches etc.
• Functions and software:

- Functional descriptions for the entire CMS and for the partial systems.
- Description of standard software functions.
- Description of objects for data acquisition, automatic control and
presentation.
- Description of Human-Machine Interface (HMI) including
presentation, issuing of commands, alarm handling and selection of
displays.
- Description of display hierarchy, general display layout and symbols
for objects.
- Description of process control functions: Monitoring, interlocking,
analogue regulation, sequence control, etc.
- Description of procedures for monitoring and testing of the internal
functions of the CMS.
• Other information:
- A detailed time schedule for implementation, including links to
activities performed by others which can influence and be influenced
by the Contractor's work.
- Guidelines for system documentation, including numbering of
documents.
- The scope of system documentation
- Specification of system for configuration control.
- Regulation prices for changes of scope of supply.
The system description shall be bound and indexed, and it shall be sufficiently
comprehensive and well-structured that it can be used by a person without
previous knowledge of the CMS.
The system description shall be continuously updated during design and

implementation, and it shall be included in the as-built documentation of the
system.

4301.8 Installation and execution

Refer to the Section "4000 Mechanical and Electrical Works - General
requirements and furthermore special specifications for technical installations
in the airport.
4301.9 Testing and commissioning

Refer to the Section "4000 Mechanical and Electrical Works - General
requirements".
The following additional requirements shall apply to the Site Acceptance Test
(SAT):
Signal test
• Before the start of the SAT of the installed CMS, a complete signal test
shall be carried out.
• The signal test shall apply to all CMS I/O signals, from the connections to
the CMS I/O units (terminal blocks for parallel signals, connectors for
serial signals) to the field units (sensors and actuators).
• During the signal test the signals shall be disconnected from the CMS I/O
units. Refer to Section 4305.2 below, sub-section "Facilities for test of I/O
signals"
Test of reserve capacities

• The SAT shall include tests which prove that the specified reserve
capacities are available under load conditions which can be expected
during operation.
• If the load conditions during SAT do not permit a realistic test of the
reserve capacities, then the test shall be repeated at a later stage during
integration test or operation.
4301.10 As-built documentation
General requirements
The documentation for the CMS shall be in accordance with the Section 3000,
Mechanical and Electrical Works - General requirements, with the following
supplementing requirements:
• The as-built documentation shall provide the Employer with all

information necessary for operation, maintenance and further development
of the CMS.
• The scope and quality of the as-built documentation shall be such that it
provides all information required for the re-creation of the CMS, if it
should be destroyed, for example by fire.
• The as-built documentation for a CMS shall be structured as follows:

- System description
- Hardware documentation
- Functional descriptions and instructions
- Software documentation
- Test documentation
The above-mentioned parts of the as-built documentation are described in the

following sections.
The Engineer shall have the right to require changes to the submitted
documentation, including supplementing material, if he deems scope or quality
of the submitted material to be insufficient as required in the Contract
Documents.
All documents/drawings shall be submitted in digital form and on paper in

binders. The paper copies shall be clear and easy to read. Every binder shall be
provided with a clear marking on the back, an index and numbered tabs in
accordance with the index. All documentation on paper shall as a minimum be
supplied in three copies.
System description
The system description (see Section 4301.7) shall be updated so that it
describes the CMS as built.
Hardware documentation
The hardware documentation shall include but not be limited to the following:
• Description of the hardware configuration. If the hardware configuration is

located in more than one equipment cabinet or in more that one room, then
the description shall be structured accordingly.
• Principle diagrams that provide an overview of the parts of the CMS and
their functional relations.
• Drawings of equipment cabinets, panels, junctions boxes etc. with
indication of the placement of the individual components. The Contractor
shall make complete control schematic drawings for all control panels
including internal wiring.
• Cable and interconnection drawings showing cable ID, cable type, cable
path and the termination points for the cable/conductor.
• Drawings showing lightning protection, potential equalisation and
earthing.
• Description of the individual components with the same terminology as
used in the system desription and in the rest of the documentation.
• Documentation of the entire signal path for all input/output signals - from
the monitored/controlled equipment (terminal block in equipment cabinet
or junction box) to the input/output units of the CMS.

Symbols, designations and tag numbering shall be consequent on all drawings.

Tag numbers shall be in accordance with Document No. AL-000-H-13012.
Functional descriptions and instructions

The documentation shall include but not be limited to documents and drawings
that describe the following:
• Functions for control, monitoring and data acquisition.

• P&I diagrams.
• Functions for operation, maintenance and fault diagnosis.
• Operational instructions for each hardware unit describing how it
functions, how it shall be used in the CMS, and its possible fault states.
• Instruction for fault diagnosis and rectification for each hardware unit..
The instruction shall describe all known faults and provide information on
how they can be identified and how they can be rectified. It shall comprise
all necessary information, including circuit diagrams, specification of
necessary measuring equipment etc.
• Maintenance instruction for each unit with specification of the
maintenance required to ensure its correct function.
Software documentation
Software shall be delivered on a suitable data medium (CD-ROM, magnetic
tape or other as agreed with the Engineer) with a description of the contents and
an installation instruction.
The installation instruction shall as a minimum provide an instruction on how

to install the software item with the specification of operating systems,
programming languages and development tools used.
Version numbers shall be indicated.
The software items in the CMS shall be classified as either standard software or
user software:
• Standard software is defined as standard software products which are used

for different applications.
• User software is defined as programs and configurations which have been
developed especially for the CMS in question.
Requirements to standard software:

For each standard program the following documentation shall be provided:
• Documentation of data file structures

• Installation instruction for all standard programs with detailed description

of how data files are installed.
• A functional description which describes the purpose of the program and
its functionalities, including error handling.
• Specification of input and output data, inclusive data formats and other
relevant information.
• Description of how the program is related to other programs and of how it
is executed.
Requirements to user software

The Contractor shall submit source code for all programs and all configurations
which have been developed specifically for the CMS. The source code shall be
provided with comments at such a level that a programmer with knowledge of
the programming language or the development system can correct
programming or configuration errors and make modifications.
The Contractor shall also submit documentation of configuration and user

instructions for automatisation programs, objects and data bases. All screen
displays, all graphic objects and all windows for entering operator commands
shall be documented with display copies and explanations. All adjustable
parameters (for example limit values and time delays) shall be documented in
parameter lists.
Automatisation programs that are based on Function Block Diagram (FBD) or

Ladder Diagram (LD) shall be documented in graphic form.
The functional relationships between the programs in the different parts of the
CMS (PLCs, servers, operator stations etc.) shall be documented.
The documentation of the software configuration shall be provided with cross

references to the documentation of the hardware configuration so that the user
obtains a comprehensive documentation of the entire information path, from the
field equipment to the data base and the screen display.
The documentation of the HMI interface shall include but not be limited to:
• Screen displays and objects:

- Copies of all screen displays with description of all functions.
Screen displays shall be identified by tag numbers.
- For each screen display the contractor shall submit a list of the objects
on the display with tag number and type of each object.
• Alarms, with tag numbers and attributes.
• Other objects of the HMI interface, with tag numbers.

Test documentation
The documentation shall include the documentation of the tests according to
section 4301.9.
4301.11 Operation and maintenance

Refer to Section 4000, Mechanical and Electrical Works - General
requirements.
4301.12 Training
The training programme shall ensure that the Employer's operating and
maintenance personnel are capable of executing their tasks efficiently and
reliably.
Training shall be conducted by personnel employed by the Contractor, familiar

with the system supplied, experienced and trained in developing and
implementing instructional courses.
The Contractor shall submit information on the training programme for

approval prior to shipment of the equipment. This submittal shall include a
course outline, time required, course schedule, sample workbook and
information on the qualifications of the instructors.
The Contractor shall supply a workbook on each course available to every

person taking the courses listed herein. The workbook shall be of sufficient
detail, so that at a later date, a trainee could review in detail the major topics of
the course.
The training shall be conducted in English, and this also applies to the
workbook and all other training material.
The training programme shall commence during the Time for Completion and
shall be completed before the date of issuing the Taking-Over Certificate.
The training times shall be scheduled and co-ordinated with the Engineer so as
not to affect the Employer’s ability to effectively operate the equipment.
Training of operators
The operator training programme shall cover all relevant functions for the
respective system. It shall include but not be limited to the following subjects:
• System overview
• System components
• System start-up
• Operator access facilities
• Control functions
• Data presentation
• Modification of reports, graphs, etc

• Operator reporting facilities
Training of maintenance personnel

The maintenance training programme shall be developed for personnel that
possess electronics maintenance and repair experience and a general knowledge
of computer systems, but shall not assume any familiarity with the specific
hardware furnished.
The maintenance training programms shall include but not be limited to the
following subjects:
• System architecture and layout
• Hardware components
• Module switch settings (configuration switches)
• I/O modules, field instrumentation
• Power supplies
• Data highway principles
• Program connection/interaction
• PLC programming and diagnostic techniques
• PC and operator station familiarisation and maintenance
• General troubleshooting
• System disassembly/reassembling
• Component replacement
• Diagnostic programs
4302 Architecture of CMS

4302.1 General
If nothing else is specified for the specific CMS, the CMS shall have a
decentralised architecture with the following elements:
• PLCs/controllers which are connected to field equipment by parallel or

serial signals.
• CMS servers
• Operator stations and printers
The above-mentioned elements communicate with each others through the
Airport Community Network (ACN).
This section specifies requirements to the architecture.
Servers in data centres

If the absence of alternative specifications for the particular CMS, the CMS
servers shall be placed in data centres established by other contractors.

Each data centre is established in cooperation between Main Contracts:
• The physical facilities are established by the Main Contractor in charge of

the building where the data centre is located. They include building
facilities, equipment racks, secured power supply and physical data
connections.
• The IT functionalities are established by Main Contract 6.
In each airport (Salalah respective Muscat) there will be established two data
centres at two separate locations. If a CMS is implemented with a doubled
server configuration the two servers shall be located in two different data
centres.
The servers in the data centres shall comply with the following requirements:
• The servers shall be suitable for installation in 19" rack.

• Each server shall be equipped with two independent power supplies.
• Each server shall be equipped with three network adapters type 1000base-
T.
Interface to Airport Community Network, ACN

Each CMS shall be provided with an interface for serial communication with
the ACN. The interface shall be through copper (Cat 6, RJ45 connectors) or
fibre optics (ST connector, single mode) as specified for the particular CMS.
The ACN is established in cooperation between Main Contracts:
• The physical connections (outlets and cabling) are established by the Main
Contractor in charge of the respective building.
• The network connectivity is established by Main Contract 6.
The physical connection shall be via a socket outlet (RJ45 or ST) provided by
the Main Contractor in charge of the respective building. This socket is referred
to in the following as the ACN socket.
The Contractor shall establish the data connection to the ACN socket, including
the patch cable to the ACN socket. He shall specify the location of each ACN
socket for the Main Contractor in charge of the respective building.
The ACN supports transmission speeds of 10/100/100Mbit/s as required by the

CMS. The ACN recognizes automatically the transmission speed used by each
specific system.
Time synchronisation
The internal clock of the CMS shall be synchronised with the central master
clock of the airport by communication through the ACN. The synchronisation
shall be effected by the standard network time protocol "NTP".

The Contractor shall deliver all necessary software drivers for synchronisation
of the CMS.
Historical data base

Historical data shall be stored in an SQL compliant data base in non-volatile
memory.
The scope of historical data to be stored shall be in accordance with the

requirements for the specific technical system. The following data shall be
stored in the historical data base:
• Event list as specified in section 4304.2.

• Time series of analogue data as specified for the CMS. Examples of time
series:
- Variation over time of water level in a pump sump
- Variation of consumption over time (for example hourly values of
power consumption).
There shall be remote on-line read-only access to the historical data base
through the ACN. The interface to this functionality shall be equivalent to that
of Microsoft Access.
Backup and restore

The CMS shall be provided with user-friendly facilities for creation of backup
copies of configuration and operational data on a removeable medium, such as
writeable CD-ROM.
The CMS shall be provided with user-friendly facilities for restore of backup
data.
The backup and restore facilities shall include SCADA, PLC and OPC
applications.
The CMS shall also be provided with user-friendly facilities for backup of the
above-mentioned data in the Storage Area Network (SAN), and for restore of
these backup data. The SAN, which will be established by Main Contractor 6,
is a common storage network for the airport.
The SAN will provide a separate virtual storage area for each CMS server. The
access to the storage area will be based on SQL.
The CMS server shall be provided with a separate network adapter (RJ45
socket) for connection to the SAN. The SAN supports transmission speeds of
10/100/1000Mbit/s as required by the CMS server.

The network connection from the CMS server to the SAN will be established
by Main Contractor 6.

Refer to Section 4301.6 above.




Operation and maintenance

4302.8 Training
4303 Hardware requirements

4303.1 General
The following requirements shall apply to the CMS hardware if nothing else
has been specified for the specific CMS.
Cabinets
The CMS equipment shall be mounted in painted steel enclosures with lockable
doors.
The enclosures shall provide cable access by the use of cable glands.
The enclosures shall provide a degree of protection that is suitable for the
environment where it is to be installed. Enclosures placed indoors shall provide
minimum IP 42 ingress protection according to BS EN 60529.

Equipment enclosures placed in air conditioned rooms shall be rated for a

maximum ambient temperature of +30oC.
Equipment enclosures which are provided with ventilation in order to prevent

excessive heat build-up shall be equipped with monitoring of the ventilation
function.
A clear copy of certified and stamped As-built drawings shall be placed in a

dedicated compartment or pocket inside each enclosure.
Labelling
Each enclosure shall be labelled with its tag number in accordance with
Document Nr. AL-000-H-13012.
If an enclosure contains more than one functional unit, then each functional unit
within the enclosure shall be labelled with its tag number in accordance with
Document Nr. AL-000-H-13012. The functional units that shall be individually
labelled include but are not limited to: PLCs/controllers, I/O units, switches and
routers, power supplies, fuses, and other components defined in Document Nr.
AL-000-H-13012, Appendix 6.
External labels shall have letters not less than 10 mm in height and internal
labels not less than 6 mm. The labels shall be of coloured laminated plastic, and
the letters shall be black in colour on a white background. The external labels
shall be fixed with stainless steel non-pointed self tap screws to the individual
doors. The internal labels shall be fixed with rivets, screws or permanent
adhesive as suitable.
Each terminal block and each individual terminal shall be individually labelled.
A cable that connects two enclosures shall be labelled within each enclosure
with a permanent tag or a self-adhesive label.
The labelling shall be in accordance with the as-built documentation.
The labelling shall be approved by the Engineer.
Operator stations
Visualisation and issuing of commands shall be carried out at operator stations
as specified for the specific CMS. An operator station shall, if nothing else has
been specified, comprise the following parts:
• A client computer (PC or other type) with network connection to CMS

server.
• A specified number of LCD colour monitors, minimum 19" in diagonal,
resolution minimum 1600 * 1200 pixels, SVGA.
• A keyboard with pointing device (mouse or equivalent).

• Stereo loudspeakers with connection to sound card in PC.

• All other parts and features required for a fully functioning, ergonomically
satisfactory operator station.
Supply voltage shall be 240VAC.
Printers
Each CMS shall be provided with a specified number of printers for printout of
screen pictures, reports etc. If no alternative requirements have been specified
the following specifications shall apply:
• Colour laser printer with network connection to CMS server.

• Colours shall be compatible with those of LCD colour monitors.
• Resolution: Minimum 600 dpi * 600 dpi.
• Paper format A3/A4. Minimum 200 sheets in tray.
• Printing speed: Minimum 25 pages/min.
• Supply voltage: 240VAC
Furniture for operator

The Contractor shall provide furniture for the HMI equipment. The furniture
shall be of good quality office standard subject to the acceptance of the
Engineer. The following furniture items shall be included:
• One (1) terminal table for the operator station. Width * Depth = ca. 1.8m *
0.9m, height adjustable.
• Two (2) office chairs on wheels
• One (1) table or cabinet for support of the printer/copier (only if necessary
for elevation of printer/copier to normal working height for a standing
person). Dimensions to be agreed with the Engineer.
Serviceability
The CMS hardware shall be of modular design with plug-in I/O modules,
function modules and communication modules so that hardware faults can be
remedied by simple exchange of defective modules.
The CMS shall be provided with self-diagnosis facilities which indicate the
location of faults in order to facilitate repair. This applies in particular to the
following:
• I/O modules for connection of process signals

• Fuses in internal power supply of input/output units and other parts of
CMS
• Communication links between parts of CMS. This also applies to loss of
redundancy in communication links.

It shall be possible to exchange faulty I/O modules without interrupting supply

voltage
Facilities for test of I/O signals

The I/O units of the CMS shall be provided with facilities as described below
for indpendent testing of
• The signal path from the I/O unit to the field equipment (sensors and
actuators)
• The information path from the I/O unit to the CMS memory and the
operator station.
It shall be possible to disconnect the signal path to the field equipment from the
I/O unit without interference in the permanent cable installation.
Serial I/O signals (for example fieldbus) shall be connected to the I/O unit
through a connector so that they can be easily disconnected for signal test.
Parallel I/O signals shall be connected to a terminal block at the I/O unit. The
terminal block shall comprise disconnection terminals with test plugs at both
sides.
Electromagnetic compatibility, EMC

All parts of the CMS shall function correctly in the EMC environment where
they are located.
All parts of the CMS shall comply with the general EMC requirements in
Section 4000, Electrical Installations - Special Specification.






Operation and maintenance

4303.8 Training
4304 Human machine interface (HMI)

4304.1 General
The HMI shall be designed in accordance with the requirements for operation
and maintenance of the specific CMS and the monitored/controlled technical
system.
The HMI shall comply with the following general requirements if nothing else
has been specified in the requirements for the specific CMS.
General functional requirements

The HMI shall be optimised for the following tasks:
• During normal operation: Overview and evaluation of operation.

• In fault situations: Fault diagnosis, continuation of operation with the
constraints imposed by the fault.
The HMI shall be organised in an ergonomically suitable way with overview

displays and detail displays, and with user-friendly navigation between
displays.
The HMI shall enable the different categories of users to carry out their
respective tasks in an optimal manner. It shall provide each user category with
the information and functionalities required for its respective tasks.
The HMI shall display all adjustable parameters for monitoring and control
functions executed by the CMS. This includes but is not limited to delay times,
limit values, controller settings etc.
User categories
The different categories of users and their authorization profiles shall be
defined in accordance with the specifics of the respective systems. As a
minimum the following categories shall be defined:
• Operator in charge of operation of the technical system.

• Operator in charge of maintenance of the technical system.

• Super User who can perform configuration works on the CMS, such as
editing of displays, alarms, limit values etc.
• System Administrator who has access to all functions of the CMS. For
smaller CMS the authorization profile of the System Administrator may be
identical with that of the Super User.
Information and functionalities which are not required for a specific user
category shall not be provided for users of this category. This applies in
particular to the users in charge of operation of the technical system. They shall
only have access to pictures and messages which are relevant for their tasks,
and they shall not be burdened with unnecessary information used by other user
categores.
User authorization, logging in

Each CMS shall be provided with a function for managing user authorizations
in accordance with the requirement of the organisational set-up for operation
and maintenance of the specific CMS.
It shall be possible for the System Administrator to define and change an

authorization profile for each user.
When a user commences work at an operator station, he shall log in with his
personal ID code and password, and the system then assigns his authorization
profile to his operator station.
The system shall be able to log out automatically if there has not been any
activity at the operator station for a predefined time.
Alarm management
Alarms shall be generated automatically in response to faults or critical events
in the system, plant or equipment being controlled or monitored.
Alarms shall be presented to the operator with the following information:
• Time and date

• Object (name), tag-number
• Alarm level
• Alarm text, minimum 30 characters
• Link to additional information
Alarms/alarm text shall be informative and consistent, and the alarm handling
shall be simple and shall assist the operator in reacting fast and correct
especially in critical situations.
System diagnostic alarms indicating system failures and non-operational

conditions shall be annunciated in the alarm list marked as "System alarm".

Alarms shall be indicated at the graphical display at all levels and be presented
in the alarm list.
Alarms and associated operator messages shall be operator changeable,

depending on operator authority.
Alarm texts and additional information shall be easy to edit. The text shall be
stored in a separate file, which can be edited without disturbing the running
system. The Engineer shall approve the alarm texts before commissioning.
All alarms shall be visible on all relevant graphic display by a change of colour
of the related symbol or text.
An un-acknowledged alarm shall be indicated by blinking red colour. When

acknowledged, the alarm indication shall shift to steady red.
Active, acknowledged alarms shall alert the operator at selectable intervals by

blinking or through other operator messages. The alert interval shall be operator
selectable under operator authority control.
For further invocation of the operator, it shall be possible to attach a visual

signal and an audible signal or file to each and every alarm.
It shall be possible to silence the audible alarm from the alarm dialog box
depending on operator authorities.
All alarms shall be stored in a database. A search and sort facility shall be
available in the alarm list.
Alarms shall be printed out on request only.
Alarm priorities
Each alarm shall be provided with an indication of its priority. The alarm
priorities shall indicate the sequence in which the operator should handle the
alarms. The priority of each alarm shall be indicated clearly in the alarm list.
The priority of an upcoming alarm shall be reflected in the audible signal which
alerts the operator.
There shall be minimum three alarm priorities: 1, 2 and 3.
The Contractor shall develop an alarm priority concept according to the

requirements of the specific controlled system, and he shall assign priorities to
all alarms according to this concept.
The priority of an alarm shall be determined on the basis of the following

criteria:
• The potential consequences of the alarm state.

• The required reaction time for handling of the alarm state.
The above-mentioned criteria may be supplemented by other relevant criteria.
Alarm suppression
It shall be possible for an operator to suppress individual alarms, for example
false alarms from faulty sensors.
The suppression of an alarm shall be recorded as an event, and there shall be

pre-configured reports which show all suppressed alarms.
It shall also be possible for the operator to suppress alarms with low priorities
temporarily.
Secondary alarms shall be suppressed automatically
A secondary alarm is an alarm which arises as a direct consequence of another

alarm, in the following referred to as the primary alarm. A primary alarm may
for example be an alarm for power failure in a distribution panel which supplies
a number of electric motors through Motor Control Centres (MCCs). In case of
a power failure, each MCC will activate an alarm, and these alarms, which are
direct consequences of the primary alarm, are considered to be secondary
alarms.
Only one alarm - the primary alarm - shall be shown, whereas the secondary
alarms shall be suppressed. This makes it easier for the operator to identify the
original cause of the alarms, and it also reduces his workload in the alarm
situation, because he only has to acknowledge the primary alarm.
Automatic suppression of secondary alarms presupposes that the secondary

alarm conditions disappear together with the condition which causes the
primary alarm. If this is not the case - for example if one of the above-
mentioned MCCs unexpectedly fails permanently during the power failure -
then the state of the automatically suppressed alarm shall be changed
automatically to active, unacknowledged.
In some situations the automatic suppression of secondary alarms may be

undesirable, and therefore it shall be possible to enable and disable this
functionality by operator commands.
Suppressed alarms shall be indicated at the respective component icons by an

unobtrusive graphical element, for example a small red dot.
The Contractor shall define and implement logic for suppression of all
secondary alarms. This includes but shall not be limited to all alarms that arise
as a direct consequence of failures of the electric power supply, both global
failures (for example a failure of the power supply from the public power
network) and local failures (for example failure of a secondary power generator
or a Main Switching Board).

The logic for suppression shall be configured in a user-friendly high-level

language so that it can be modified and developed further by a Super User
without specialist programming knowledge.
Event list
Alarms and other events shall be logged in an event list which shall be stored
on non-volatile memory. The scope of events to be logged includes but shall
not be limited to:
• Changes of alarm status (emergence, acknowledgment, disapperance,

suppression by operator).
• All changes of binary variables that are presented in process displays, for
example:
- Control signals to controlled units.

- Feedback signals from controlled units.
- Monitoring signals, for example fault indications.
- Transgression of limit values for analogue measurements
- Status changes of automatic programs, for example activation of an
automatic sequence program or transition from one program step to
the next one.
- Commands from operator stations, for example for opening or closing
a remotely operated motor valve, or for change of a set point.
- Login and logout by users.
Each event shall be logged with a time stamp, and the events shall be displayed
in correct time sequence according to the time stamp.
The CMS shall be provided with a user friendly facility for automatic
generation of extracts from the event list according to a combination of various
criteria, for example time interval, alarm priority, tag number etc.
It shall be possible for the operator to copy a part of an event list, or an extract
of an event list, into a Microsoft Excel worksheet.
The event list shall be stored in the historical data base. See Section 4302.2.
Report generator
The CMS shall be provided with a report generator for automatic generation of
preconfigured reports on the basis of acquired data in the historical data base. It
shall be possible to activate the report generation by an operator command or
automatically based on a time schedule.
It shall be possible to save the generated reports in the historical data base,
either by an operator command or automatically if specified for the respective
report type.

The report generator shall have access to all data in the historical data base, and
it shall be able to perform calculations on the data. It shall be able to produce
reports with a combination of tables, curves, bar graphs etc. It shall be possible
for an operator to configure reports.
The scope of supply shall include such reports as are required for the operation
and maintenance of the specific technical system. Particular specifications of
reports will be provided in the specifications for each particular technical
system.
Web server
Each CMS shall be provided with a web server with connection to the ACN
which enables remote clients with standard internet browsers to read on-line
and stored data in the CMS.
The web server shall display all process displays and lists accessible at an
operator station. It shall be possible to navigate between displays in the same
way as at an operator station.
It shall not be possible to use the web server for issuing of commands.
Access to process displays through the web server shall be password protected
with the same operator categories categories of operators and their
authorization profiles as apply at an operator station. Refer to the Section "User
categories" above.
Access to the web server shall as a general rule be limited to computers

connected directly to the ACN. External Internet access may be enabled if
required, for example for service purposes. External Internet access shall only
be possible from computers with predefined IP addresses, and the Contractor
shall provide suitable safeguards against unauthorised access and hacking.


The requirements in the following paragraphs shall apply in addition to the
requirements specified above in Section 4301.7.
The Contractor shall implement the Human Machine Interface in cooperation

with the Employer and the Engineer. The Contractor shall take the initiative in
this process and he shall actively acquire the necessary information.
The Contractor shall prepare his proposal of the Human Machine Interface for
clarification. The proposal shall provide a complete and unambiguous basis for
the implementation works. It shall include but not be limited to the display
hierarchy, layout of the various display categories, navigation methods,

specifications of objects and the associated graphical symbols, colours, names,

abbreviations etc.
The Contractor shall present his proposal for clarification and acceptance at a
series of meetings with the Engineer, and there shall be a clarification meeting
every 14 days during the clarification period. At least five working days before
each clarification meeting the Contractor shall provide the Engineer with the
documents to be discussed at the meeting and the minutes of the previous
meeting.
The HMI proposal shall be a part of the system description as described above
in Section 4301.7.




4304.9 Training
4305 Additional requirements

4305.1 General
This section specifies additional requirements to those specified in the
preceding sections.
Monitoring of execution of commands

The CMS shall monitor by feedback signals, that commands from the CMS to
controlled units are executed correctly. This applies for example to controlled
motors (start/stop) or switching valves (open/closed).

If a command from the CMS does not cause the intended change of the state of
the controlled unit within a predefined time, then this failure shall be indicated
by an alarm which provides an identification of the unit in question.
Reaction to power interruption

In case of a temporary interruption of the power supply to the CMS, or a part of
the CMS, the CMS, respectively the afflicted part of the CMS, shall restart
automatically.
The automatic restart shall take place in a correct manner without erroneous
functions such as false alarms or erroneous output signals.
In case of an interruption of the power supply to a part of the CMS, the rest of
the CMS shall continue to function correctly with the constraints imposed by
the power failure.
Reserve capacities
Bottlenecks
Every element of the CMS, which can become a bottleneck during operation,
shall not be utilized for more than 60% of its maximal capacity at any time
during operation.
The maximum capacity shall be understood as the maximum utilization which

is possible without compromising system performance.
Some examples of elements which can become a bottleneck are:

• Processor
• RAM memory
• Function executed by a program or sub-program
• Subsystem including hard- and software
• Data communication channel
Hard disk capacity

Hard disk storage shall not be utilized to more than 40% of its maximum
storage capacity.
Reserve signal positions

Each I/O unit for parallel I/O signals shall be provided with reserve positions
for connection of extra I/O signals. For each type of I/O signal, the reserve
capacity shall be either 20 % of the foreseen number of signals or two signals,
whichever number is greater.
The reserve positions shall be ready for connection of signals. They shall be
provided with disconnection terminals as mentioned above in the Section
4303.2 "Facilities for test of I/O signals", and with all internal wiring.

Expansion of signal numbers to 200%

The CMS configuration shall have extra capacity for expansion of the numbers
of parallel I/O signals of each type to 200% of the foreseen number of signals
of the respective type.
Such an expansion shall be possible by addition of additional I/O modules, and

upgrading of internal power supplies if required, but it shall not require
expansion of existing processors, RAM, hard disks, communication links and
standard software.
The expansion of signal numbers shall be possible in the following two ways,
or in a combination of them:
• By expansion of the number of I/O units to 200% of the foreseen number,

with the same number of I/O signals in each unit.
• By the same number of I/O units as foreseen, with an expansion of the
numbers of I/O signals in each I/O unit to 200% of the foreseen number of
signals of each type.




4305.7 Documentation

4305.9 Training

Revision Log
Date Issue Description
31.10.2008 T01 Issued for Tender


SA-000-R-11143 Rev T01 4300 Handbook of Bolts and Bolted JointsSpec 31.10.2008

Hochgeladen von

Dokumentinformationen

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

SA-000-R-11143 Rev T01 4300 Handbook of Bolts and Bolted JointsSpec 31.10.2008

Hochgeladen von

Copyright:

Verfügbare Formate

Sultanate of Oman

Ministry of Transport and Communications

Report no. SA-000-R-11143

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

4304 Human machine interface (HMI) 20

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

4300 Control and monitoring systems

• An interface to the Airport SCADA system for overall monitoring of

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

amendments, of the appropriate Omani, British and European Standard

4301.4 Design basis

4301.5 Functional requirements and materials

General quality requirements

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

All hard- and software products shall be based on state-of-the-art components

Manufacturerers which have no proven record of quality and service in the

If one or more manufacturers should introduce new versions of hard- and

Facilities for service

• Identification of all hard- and software items.

The configuration control system shall be described in the Contract Documents.

4301.6 Documentation in tender

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

• Overall and detailed configuration diagrams of the CMS and its

4301.7 Shop drawings

The system description shall include a definite specification of the interfaces to

The Contractor shall not commence the implementation works - procurement,

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

- Use of tag numbering system (please refer to document no. AL-000-

• Functions and software:

The system description shall be continuously updated during design and

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

4301.8 Installation and execution

4301.9 Testing and commissioning

Test of reserve capacities

4301.10 As-built documentation

• The as-built documentation shall provide the Employer with all

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

The above-mentioned parts of the as-built documentation are described in the

All documents/drawings shall be submitted in digital form and on paper in

• Description of the hardware configuration. If the hardware configuration is

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

Symbols, designations and tag numbering shall be consequent on all drawings.

Functional descriptions and instructions

• Functions for control, monitoring and data acquisition.

The installation instruction shall as a minimum provide an instruction on how

Version numbers shall be indicated.

• Standard software is defined as standard software products which are used

Requirements to standard software:

• Documentation of data file structures

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

• Installation instruction for all standard programs with detailed description

Requirements to user software

The Contractor shall also submit documentation of configuration and user

Automatisation programs that are based on Function Block Diagram (FBD) or

The documentation of the software configuration shall be provided with cross

• Screen displays and objects:

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

4301.11 Operation and maintenance

Training shall be conducted by personnel employed by the Contractor, familiar

The Contractor shall submit information on the training programme for

The Contractor shall supply a workbook on each course available to every

P:\61400\3_DOC\10_Tender_Doc\02_SA\CRN_55_MC 5_Civil & Building Works Salalah\Final\31.10.2008\03_Specifications\Civil Works\SA-

• Operator reporting facilities

Training of maintenance personnel