MOL Group: Technical Specification Instrumentation

SLOVNAFT a.s.
R&M Division
MOL Group
TECHNICAL SPECIFICATION
INSTRUMENTATION
Requirements for Field-Installed Bus Systems
MGS-S-REF-I-28
Rev 1.01.00
This document is property of MOL Group. The use is only allowed with the written permission of MOL Group.
SLOVNAFT a.s. MGS-S-REF-I-28
R&M Division
TECHNICAL SPECIFICATION - INSTRUMENTATION Rev.: 1.01.00
28 Requirements for Field-Installed Bus Systems Date: 01.05.2016
Page/Pages: 2/4
Release list
Rev. Date Description Edited Verified Approved

0.00.00 11.11.2010 General review
1.00.00 30.11.2011 General issue Kocsmárszki L.pallagi
1.01.00 Z. Stanová R. Kopálek Head of
1.5.2016 Review
Maintenance
This document is property of MOL Group. The use is only allowed with the written permission of MOL Group
R&M Division
Contents
Release list ................................................................................................................................................................... 2

Book breakdown ........................................................................................................................................................... 4
Rev 1.01.00 3/4

R&M Division
Book breakdown
Description Identifier Rev.

Requirements for Field-Installed Bus Systems MGS-S-REF-I-28 1.01.00
Requirements for Foundation Fieldbus Systems MGS-S-REF-I-28.1 1.00.00
Wireless communication between field device and control system MGS-S-REF-I-28.2 1.00.00
4/4 Rev 1.01.00

SLOVNAFT a.s.
R&M Division
MOL Group
INSTRUMENTATION
28. Requirements for Field-Installed Bus Systems

1. Requirements for Foundation Fieldbus Systems
MGS-S-REF-I-28.1
Rev 1.00.00
SLOVNAFT a.s. MGS-S-REF-I-28.1
R&M Division
TECHNICAL SPECIFICATION - INSTRUMENTATION Rev.: 1.00.00
28 Requirements for Field-Installed Bus Systems Date: 30.11.2011
1 Requirements for Foundation Fieldbus Systems Page/Pages: 2/14
Release list

0.00.00 03.31, 2004 Issue of documentation Szabó Viszkai
Gabriel Zuzana
0.00.01 11.11. 2010 General review
Kulcsár Stanová
Gabriel Zuzana
1.00.00 30.11. 2011 General issue
Kulcsár Stanová
This document is property of MOL Group. The use is only allowed with the written permission of MOL Group
R&M Division
Contents
Release list ................................................................................................................................................................... 2

1 General .................................................................................................................................................................. 4
1.1 Deviations ..................................................................................................................................................... 4
1.2 Fieldbus types accepted in MOL Group refineries ....................................................................................... 4
2 Requirements of use Foundation fieldbus ............................................................................................................. 4
2.1 Terms and abbreviations .............................................................................................................................. 4
2.2 Requirements of FFB design ........................................................................................................................ 5
2.3 Requirements of FFB hardware ................................................................................................................... 7
2.4 Requirements and configuration guidelines of FFB software ....................................................................... 9
2.5 Requirements on master controller (host system) ...................................................................................... 11
2.6 The most important conditions of the use of an FFB device ...................................................................... 12
2.7 Special and additional requirements in documentation by use of FFB ...................................................... 12
2.8 Factory Acceptance Test and Pre-commissioning checks ......................................................................... 13
2.9 Relevant standards and guidelines ............................................................................................................ 14
Rev 1.00.00 3/14

R&M Division
1 General
In addition to systematizing bus-based field communication networks, this specification sets forth the basic design
requirements applicable to the field-installed bus network Foundation Fieldbus, to be observed during the
development of the functional specification. The technical implements of field bus networks are being developed at
a fast rate, requiring frequent revisions of this documentation.
In addition to observing this specification, system engineers shall also use the necessary reference books and
standards for design work.
1.1 Deviations
The applicable Project Specification may contain deviations from or changes to this document.
Deviations from the contents of this specification and the Project Specification shall be permissible only on the
basis of prior written approval by MOL Group.
The specified solutions shall be in conformance with the specification system, standards and requirements of the
applicable project documentation.
1.2 Fieldbus types accepted in MOL Group refineries

The application of Foundation Fieldbus and 4-20mA+HART communication is accepted. The decision about used
communication method is right of MOL Group. Any other communication types can be applied only with prior
written approval of MOL Group.
Requirements of use HART Communication
Bi-directional digital communication between master (remote) and slave (field) devices.
Digital communication also possible with the transmission of analogue signals through twisted pair wires
transferring 4-20 mA signals.
Multi-drop communication can also be established between master and slave with the omission of 4-20 mA signal
transmission for
communication with 15 slave devices, using short addresses;
using a higher number of slave devices at slow scanning rate.
HART communication is not used at MOL Group for process control purposes. Its field of application is restricted to
the transmission of diagnostic information from maintenance management systems based on digital
communication superposed on 4-20 mA analogue signals to the Central Maintenance Management System.
2 Requirements of use Foundation fieldbus

2.1 Terms and abbreviations
Foundation Fieldbus System (abbreviation: FFB)
Foundation Fieldbus is an open, integrated, bi-directional, serial line, multi-drop digital communication
system installed between field instruments and the process control system.
Card H1 interconnects field measurement instruments, actuators and I/O terminals at 31.25 kbit/sec digital
communication rate.
The Foundation Fieldbus H1 technology comprises a physical layer, a communication layer and a user
layer. The so-called three blocks of the user layer are: source block - device name, manufacturer, serial
number; converter block - calibration date & time, sensor type; function block - analogue/digital
input/output, PID controller, etc.
Host device
The term “host” applies to the process control system of the DCS in the case of conventional DCS systems
and to the smart master controller controlling the communication between the segments of the network and
performing process control functions at the higher level in the case of systems based on bus-type
communication.
Interoperability
means that several Foundation Fieldbus devices (transmitters, control valves, controllers) are able to
operate in the same system without losing a single on of the functions designed for these devices
independently of their make.
A distinction must be made between the interoperability of field devices and the interoperability of the field
devices and system controller (Host Interoperability Support Test).
4/14 Rev 1.00.00

R&M Division
Point-to-point connection
Each segment contains only two devices. A safe and conservative, but uneconomic solution.
Spur topology
Individual spur lines connected to a trunk line. A topology used for installations in low density and lightly
congested units
Tree structure
Spur groups branch off from the trunk cable of the segment in junction boxes.
This design is recommended in cases of Retrofit installations, High density of fieldbus devices in a
particular area and High Speed Ethernet (HSE) is being used
„Daisy chain” topology
The segment (trunk) cable is connected in loops from device to device, not allowing on-line maintenance. A
design not applicable in refineries.
FFB coupler
A FOUNDATION fieldbus device coupler or isolated device coupler (where applicable) is located where the
trunk (home run) is connected to the various device spurs. It is typically the location of one of the
terminators (associated with a segment), and the location of spur short circuit protection.
Basic diagnostics
Failures caused by any field device, communication or controller (host) shall be brought to the attention of
the operator at the operator station and – upon its existence – facilities shall be available for forcing the
controller into manual mode in a configurable manner.
Advanced diagnostics
This shall provide for the on-line determination of device performances – such as accuracy of valve
positions, number of valve strokes, hysteresis, friction of valve stem seal gland, etc. – without the removal
of field devices.
Technological diagnostics
This is to monitor on-line the functioning of individual devices directly connected to process system.
2.2 Requirements of FFB design
2.2.1 Segment network topology

Mixed (FFB + analog 4-20 mA) control loops must not be implemented
The fieldbus installation shall use tree, spur, or combined topology.
In case of tree topology, maximum spur and FF cable lengths must be taken into consideration for
installation. Only one single device can be connected to a spur with short-circuit protection. This is the
topology selected for refinery applications.
In case of spur topology, Spurs shall be connected to current-limiting connections (30 mA, or as
appropriate for the device on a particular spur) to the bus as this provides short-circuit protection.
In case of combined tree & spur topology maximum allowable cable lengths must taken into consideration
for application and no additional spur may branch off from a spur.
Daisy chain topology is not accepted.
2.2.2 Provision of segment spares

The network and the segments shall include 25% hardware spares and 70% non-scheduled time reserve for non-
deterministic communication in order to retain local extension potentials. 1 sec macro-cycle period shall be the
basis for the provision of spares, unless required otherwise by the applicable project specification.
2.2.3 Scheduling of function block execution cycles

The respective MOL Group standard specifies the so-called control execution cycles for control loops are specified
in MGS-M-REF-I-6.1 & MGS-S-REF-I-6.1.
Rev 1.00.00 5/14

R&M Division
2.2.4 Segment reliability

2.2.4.1 Criticality of control loops
Criticality Result of value of number of device certification of software
class failure of lost loops on one supplement interoperability version
a single production respective
element segment.
Class1 shutdown exceeds one single, by same independent retain without
of the ten (10) independent vendor (off-line) tests change during
entire million US operation
process dollars
unit
Class2 shutdown exceeds One or two* by same independent retain without
of the one vendor (off-line) tests change during
entire hundred operation
process thousand
unit US dollars
Class3 will not no loss Three various - Changes may
cause unit may accrue control vendors be effected
shutdown valves during
operation
Class4 - - 12 Elements - - Changes may
(measuring be effected
instruments) during
of the operation
process
monitoring
system
* if the second loop is not independent in respect of unit shutdown
2.2.4.2 MOL Group requirements on methods for risk management

Redundant Controller Required
Redundant H1 Interface Required
Redundant Power Supplies Required
DC Power Supply Battery Capacity Required - 30 minutes minimum
Redundant Power Conditioners Required
Field Backup LAS Required
Control in Valve Positioner Preferred for simple loops
Control in Transmitter Only for Cascade Primary
Control in Host Required for Complex Loops
Valve / Segment Criticality Ranking Required
Maximum Devices per Segment 12 (default unless otherwise noted in following
section)
Maximum Valves per Segment 2 (default unless otherwise noted in following
section)
Repeaters Requires Project Lead Engineer approval
Network/Segment Shorting: A shorted network/segment or power supply failure shall send valves to their
designated failure position, regardless of the device hosting the PID algorithm.
Transmitter Assignment: In normal practice the same segment shall include the transmitter of primary
process variable and its associated valve.
6/14 Rev 1.00.00

R&M Division
Multiple Process Variables: Multiple measurements used to provide a calculated differential shall be
assigned to a common segment with the differential calculation performed in one of the transmitters as they
typically have a lower „load‟ than an output device.
Redundant uninterrupted power supply of segments, suppression of electrical noises and over-voltages,
recovery of correct signal shapes by means of repeaters and termination elements.
Provision of redundant communication between the controller and the host system in order to ensure high
availability for operator control & intervention.
Short-circuit protection of segments and individual circuits.
Additional redundancy requirements (field application of LAS, use of redundant controllers, etc.) will be
defined in the applicable project specification.
2.2.5 Handling of failures

All final control elements shall have a configured fail-state on loss of segment communication.
The invalid status of a reading may be handled also as a logic input, with the logic function resulting in a change of
the control mode.
The design of final control elements shall provide also the management of segment communication failures. Two
failure statuses shall be distinguished for control valves and designed in the course of configuration:
Configured failure statuses may include
open and closed end positions
hold last position
directed percentage open
Configuration may also provide for communication failures and events (e.g. no reading received by the controller,
valve position reset also by logic or diagnostic function, etc.).
The configured fault-state value shall be 0% (closed) for fail closed and 100% (open) for fail open valves unless
process conditions require a specific position.
Mechanical
The Fault-state Time can be configured to a minimum of 5s (or any user-selected time). This will hold the last value
(valve position) for that time period during a communication failure, and thereby increases plant availability by
providing an opportunity to reestablish communications.
2.2.6 Device diagnostics

Use of permanently installed diagnostic capabilities are required that shall be able to provide key information on the
ability of the device to measure or control the process.
2.3 Requirements of FFB hardware
2.3.1 Components of Foundation Fieldbus segments

Power supply unit feeding 24VDC redundantly to all devices on any particular segment (ensuring minimum
9V supply voltage even at the furthest component of the segment).
A conditioning unit for each redundant power supply unit, ensuring the segregation of several segments fed
by the same power supply unit and preventing the short-circuit of any segment effecting other segments.
Intrinsically safe barriers (analogue circuit barriers shall not be used).
Wire termination component pairs (resistance-capacitance members) ensuring good quality communication
signal shapes and preventing the reflection of signals. Field termination components shall be installed in
junction boxes.
Repeaters isolating segment-sections from each other electrically, allowing the use of longer lines and an
increase in the number of elements on each segment.
Trunk and spur cables shall be connected in Foundation Fieldbus junction boxes to FF-based wiring
blocks. Wiring blocks shall provide short-circuit protection for spurs.
Redundant H1 connection cards and controllers shall be installed for each FF segment. Redundant pairs
shall not be installed on the same chassis. When redundant H1 cards are used, the primary and secondary
cards shall not be installed on the same chassis.
Redundant segment scheduler (LAS) modules shall be installed.
Rev 1.00.00 7/14

R&M Division
2.3.2 FF cable types

Impedance Attenuation
Type Meters* Resistance Description
Ohm (dB/km)
A 1900 100 22 3 Individually shielded pairs
Multiple pairs with overall
B 1200 100 56 5
shield
Multiple pairs with no
C 400 Unknown 132 8
shield
Multi-conductor, no
D 200 Unknown 20 8
pairing
* This value means the total segment length with homerun and all spurs. Class C and D designs are not accepted.
Additional requirements:
Ten percent (10%) spare pairs should be provided for all multipair Fieldbus segment trunk cables, with a
minimum of one spare pair.
The length of individual spurs shall be 1 to 120m, unless required otherwise by other specifications. FISCO
standard allows maximum 30 m length.
Spur cables shall be individually shielded twisted pair type.
The ratings & parameters (conductor resistance, screen resistance, attenuation and inductance) of the
cables used shall comply with FFB standards as stated in FF-844. Other cable parameters shall follow the
requirements of MOL Group cable selection rules.
Cable laying and design requirements shall comply with the respective MOL Group specifications.
Cables for FF installations shall be labeled Type ITC (16 Gauge) and shall be installed in trays or conduits.
Fieldbus cables have to be unique in color (shall be orange or yellow) and can be easily distinguished from
conventional 4–20 mA cable.
2.3.3 Power, grounding of FF circuits. Lightning protection

Power
FFB power supplies should be redundant, load sharing and output current limiting, and provide facilities for
monitoring faults and failures. They shall be fed by dual DC bulk supply sources or by a redundant feed
arrangement (not on a single fuse). Wiring polarity shall be maintained throughout the segment design and
installation.
Grounding
The shield/screen of an FF cable shall be grounded at one single point (end).
Instrument earth shall be connected to ground only in the marshalling cabinet.
The FFB cable shield shall be kept isolated from the safety grounding system except where specifically designated
connections are required.
Instrument signal conductors shall not be used as an earth/ground. If an instrument safety earth/ground is required,
it shall be made through a separate conductor. The conductor may be in the same cable as the instrument signal
conductors and shield, but shall be located outside the shield within this cable.
Shielding:
There are four shielding options (Classes A – D) described in FFB guideline AG-181:
Class A: single point shielding
Class B: multipoint shielding
Class C: combined
Class D: multipoint shielding using capacitive coupling
Class A is recommended. The instrument shield is terminated at the Host (fieldbus power supply) end of the
network and is not connected to ground at any other place.
Some device I/O shields, such as grounded thermocouples on temperature multiplexers, may require grounding
separately from the fieldbus shield. Using Class B design is preferred in areas where there is equipotential
grounding assured.
In case of Class C design the instrument shield is terminated at the Host (fieldbus power supply) end of the
network in the marshalling cabinet and is connected to ground at field devices with isolating device couplers. It is
commonly used for IS spurs on a high-power trunk.
8/14 Rev 1.00.00

R&M Division
Class D design is not accepted.

If a multiple trunk (home run) cables go to a field junction box, do not attach the cable shield wires from different
networks together.
Terminators:
All terminators located in the field shall be installed in a junction box. Terminators should not be installed in the
Fieldbus devices.
FFB segments require EXACTLY two terminators, one at each end of the trunk (home run) cable. The terminator is
comprised of an RC network that provides 100 Ω impedance.
Repeaters:
Repeaters shall not be used without prior approval by MOL Group.
Couplers
Only registered FFB device couplers or isolated device couplers shall be applied.
Lightning/surge protection
The devices used for lightning/surge protection shall be selected so as to avoid any influence on or change in FF
signals and short-circuit protection. A surge rating of 1 kA for an 8/20 µS wave shape should be adequate.
2.3.4 Design and installation of intrinsically safe segments

Intrinsically safe segments must be designed in compliance with the protection required by the respective
hazardous area classification.
The next intrinsically safe solutions are accepted:
1. Entity model (as guideline AG-181)
2. FISCO model (as guideline AG-181)
3. Field barrier box
4. FISCO model with application of field barriers
2.4 Requirements and configuration guidelines of FFB software

Specification books MGS-M-REF-I-6, MGS-M-REF-I-6.1, MGS-S-REF-I-6 & MGS-S-REF-I-6.1 as the basis,
may/shall be supplemented in the applicable project specification with the following:
2.4.1 Instrument and block identifiers

Description in accordance with the tag number of instruments (according to P&ID symbols). Each FFB
device must have a unique physical device tag. It must retained the tag in its memory when disconnected.
The device tag shall be used for the device diagnostic alarm faceplate.
FF block name: Each FF-based device contains a number of blocks and each must enable identification.
Identifiers shall include the tag number of the device and the distinguishing marks of the respective block-
function. Each block shall use the field device tag name for its main descriptive name. In the event a device
has more than one identical block (for example, 2 analog input signals) they shall be uniquely identified,
E.g.: PT 313_AI - analogue input,
PT 313_PID - controller,
PT 313_AI_1 - analogue input No. 1
Control Strategy/Module Naming Convention
Each Fieldbus control strategy or module will be named as shown on the P&ID. The primary loop function
block used for operator interface (AI or PID) will share the module name.
2.4.2 Control Functionality Location

A control design philosophy guideline shall be developed for each FF-based automation project.
When single field control loops are selected, each element comprising a control loop shall be installed on
the same segment. If this is not possible, then the control function must be installed in the host controller.
When single loop PID control is implemented in the field device, the PID function block shall be located in
the final control element.
In the case of cascade control all elements and function blocks must be on the same segment. The
primary controller shall be installed in the measurement device and the secondary controller in the final
control element. If their installation in the same segment is not possible, then the primary controller shall be
installed in the host computer.
Complex control loops shall be executed in the host controller
Rev 1.00.00 9/14

R&M Division
Design philosophy of control function location shall be specified by designer in a Functional Design Study
or Project specification and shall be approved by Client.
2.4.3 Requirements of control functions

Controllers shall provide auto/cascade/manual modes and local/remote setpoint adjustment.
Controllers shall include initialization functions.
Floating point method shall be used for calculations.
Controllers shall include anti-wind-up protection.
The system shall provide features for the simple presentation of the control structure configured.
The system shall provide for the performance monitoring of measurement and control loops.
2.4.4 FF functional blocks

Any function blocks that are supported by Fieldbus Foundation Guidelines (see section 2.9.) are applicable.
2.4.5 Invalid data

Important: FFB specifications no longer support flagging an out-of-range condition as uncertain.
Data shall NOT be invalidated in the following case:
Readings are outside the measuring range (overflow & underflow).
Data shall be invalidated in the following cases:
Readings are impossible to measure or calculate.
Values are invalidated by the application program.
The error of the measuring instrument invalidates the reading.
2.4.6 Alarms & events

Criticality for alarm functions installed in FF-based devices should be managed in compliance with MGS-M-
REF-I-6.1 & MGS-S-REF-I-6.1.
Alarms shall be handled in the DCS system together with the timestamps of the respective devices.
FF devices shall output alarms to the DCS system in the case of faulty communication, malfunctions and
device failures.
All status alarms should also be transmitted to the computer-based maintenance system for repair by the
maintenance personnel.
2.4.7 Operator display

Data from conventional and FF-based devices shall be displayed identically on dynamic graphic screens.
Overloading operators with information, slower updating cycles of system operation consoles must be avoided in
spite of the extra information supplied by FF-based devices, i.e. operators shall receive only information directly
related to the technological process controlled.
Information of maintenance systems shall be accessible independently from operator displays.
The status of each process data shall be displayed as additional information. The system shall display the statuses
of all connected communication systems. It shall display in on-line mode and hierarchic structure the results of self-
diagnostics and the diagnostic results of system components.
2.4.8 Software revisions

Provisions shall be made to enable the upgrading of the system software without shutting down the process and
losing operator control and intervention capabilities.
The existing application software shall be functional also on new system software versions, i.e. any new version of
the system software shall be compatible in retroactive manner with the files developed/generated with the previous
system software.
2.4.9 System configuration tools

A common configuration tool shall be provided for the conventional and FF-based systems. The same configuration
module shall be used both for the host device and in the field.
The system shall include configuration display screens in order to facilitate configuration activities. A distributed
common database shall contain the display screens and the control loop identifiers.
The system database shall provide copying facilities for the simple execution of identical tasks and/or functions.
10/14 Rev 1.00.00

R&M Division
The system shall provide for the simultaneous link-up and use of more than one engineering workstations.
The in-house program languages of suppliers shall not be used for the execution of control functions.
Data import & export: The host device & database shall provide configuration capabilities for importing and
exporting the data of function blocks and modules. The applicable import and export file format are: Microsoft
Excel, text, Microsoft Access, SQL.
The host device shall be capable of downloading data (function, scheduling, initialization) in the function block of
the respective FF element.
2.4.10 Requirements of Link Active Scheduler

The Master and Primary Backup Link Active Scheduler (LAS) shall reside in the host control system in redundant
H1 cards. An additional backup LM Link Master (B/U LAS) shall be configured for all networks and shall reside in
the network device with the lowest field node address. The Backup LAS should be placed in a separate device that
does not have controlling functions. Each network shall be configured for automatic fail-over to the Back-up LAS in
the event of Master LAS failure. There can be one or more backup LAS‟s on a fieldbus network, in addition to the
main LAS. Only one LAS is active on an H1 fieldbus network.
2.5 Requirements on master controller (host system)

The design of the control system shall also satisfy the requirements of the MOL Group standard on DCS system
automatic switch-over to redundant systems elements
power supply unit redundancy
failure of one device not to cause the failure of more than one control loop
failure of a single element not to cause communications failure, etc.)
Furthermore the host system shall provide
FF based solutions for DCS functions
Function block compatibility
Configuration environment
The system shall provide on-line & off-line configuration facilities and their multi-user application. The FF
based engineering, configuration, maintenance and operating features shall form an integral part of the
complete (conventional or HART-based) system.
Remote setting of field instruments from the host system
System error recognition & system maintenance
o Log the load of all buses and the common bus communications failure.
o Log all system failures & errors.
o Switch between the statuses of FF devices and document these actions.
o Follow up the installation of new devices and mirror old configuration data in new devices.
Data validation
Notify operators of FF configuration errors by means of event logging.
Redundant segment design in power supply, communication scheduling and interconnection with the host
system (H1 card).
Interoperability with field devices intended to be used
The certificate verifying the result of the FF-569 test must be known prior to host selection. Requirements
on the FFB system HIST test
o All control systems – to which the FFB system is connected – shall have successful HIST test, and
test report.
o It shall be registered by the Fieldbus Foundation Organisation.
o It shall support all the possibilities described in the “Host Feature Supported” list.
On-line creation & modification of FF control strategy
Automatic recognition of devices on any segment
Automatic macro-cycle generation & optimization
Simulation of field devices in order to allow complete control loop tests even without segments and field
devices.
Rev 1.00.00 11/14

R&M Division
For safety reasons, the maintenance workstation and functions must be installed on separate servers but
made accessible from operator stations.
2.6 The most important conditions of the use of an FFB device

All devices connected to the FFB shall have a successful test report and be registered by the Fieldbus
Foundation Organization. This test procedure is shown in the Section FD-210 “Interoperability Tester
User‟s Guide” of the standard.
The test report shall contain general information on the device (manufacturer, model, type, revision, serial
number, Device ID), the function blocks tested (e.g. AI, PID etc.), data on the physical layer (e.g. Type.
111), data of the device description (DD).
The information on the shipment datasheet of the FFB device, the data of the test report and the data of the
DD (Device Description) files shall be adequate.
All devices connected to the FFB shall have an electronics or auxiliary devices (Fault Disconnect
Electronic: FDE) that disconnect the FFB device in case of failure.
2.7 Special and additional requirements in documentation by use of FFB

All documents listed below shall be prepared and submitted to end-user in electronic format.
Instrumentation system drawing shall show:
all network elements, communication lines, data stores (memories) and operator interfaces shall be shown
in this drawing.
Segment drawings shall show:
o Software data – network name (controller tagname, card/port positions, function blocks.
o Segment topology (segment trunk & spur line lengths, cable types, junction box positions,
connection points, power supply unit, repeater, IS barrier, termination element, spare capacity &
signal conditioner positions).
o All devices with their tag numbers and cables with their identifiers.
o Circuit parameters (device voltages, current ratings, device polarities).
o Macro-cycle period.
o Criticality of control loops connected to each segment and segment loads.
o Device used as back-up LAS.
Segment installation drawings shall show the exact installed locations of devices in the process unit with
related cable lengths.
Field instrument specifications
Original instrument specification datasheets shall be supplemented with the specification of
o the requirements of input/output function blocks, control requirements (control execution cycles,
LAS functions, algorithm definitions) and diagnostic functions (detector failure, impulse line
plugging, valve diagnostics, etc.),
o Device Description (DD), Common File Format (CFF), indicating revision & release numbers,
o minimum operating voltages, maximum current consumption values, function block execution rates,
polarity sensitivities, requirement for interoperability test.
Piping & Instrumentation (P&ID) Diagrams
No standard exists currently in respect of symbols to be used for FF-based instrumentation, therefore
instrument engineering contractor and client must agree in the system of symbols to be used during the
design phase.
The following items should be identified preferably:
o FF-based instruments,
o System components running each control function,
o Functional interconnection of FF-based elements,
o Control execution cycles,
o Location of segment scheduler.
Loop drawings
Due to the elimination of point-to-point connections, loop drawings will be replaced by segment drawings.
Tabulated instrumentation list
12/14 Rev 1.00.00

R&M Division
It shall indicate which elements are FF-based as well as the FF types implemented, software versions and
function blocks.
Descriptions of standard control functions
These shall include applicable parameters, descriptions of block operations, conditions of controlling
detected errors, failures and malfunctions.
The system of numbering cables (the cable schedule) will change, several devices will be connected by a
single cable, therefore segments numbers or segments descriptions should be used preferably for cable
identification.
2.8 Factory Acceptance Test and Pre-commissioning checks

Written report of the following tests shall be generated and attached to the segment documentation.
2.8.1 Factory Acceptance Test

The requirements set forth below are only supplements for the tasks required for factory acceptance tests in
Specification MOL Group Refinery Standards Books MGS-M-REF-I-6.1 & MGS-S-REF-I-6.1.
The testing of FFB based devices requires at least one of the devices to be available for testing.
Minimum scope of tests:
1. FF-based device test (e.g. Interoperability),
2. Control strategy verification,
3. Back-up LAS function,
4. Device relocation from one segment to another.
The next detailed test protocol for FFB systems is recommended by MOL Group Refining. In case of performing
different protocol by vendor it shall be managed according to MGS-M-REF-I-13.1 & MGS-S-REF-I-13.1.
a. FF-based device test

Functional test: Testing of interconnection with host computer (plug and play test, function block tests).
Calibration test: temperature transmitter RTD/TC selection, zero/span setting of pressure & differential
pressure transmitters, valve positioner adjustment.
Verification of correct data transfer between device and host computer.
Verification of correct communication of transmitted data.
Verification of data uniformity on device, host computer and operator display.
Manual stroking of valves from operator consoles, etc.
b. Verification of control strategy

Verify correctness of measurement ranges and engineering units both in AI function block and
transducer block as well as on individual loop diagrams, graphic displays and trends.
Simulate 50% of measured value and verify on system elements.
Verify appearance of measured values at pre-defined graphic display locations.
Verify appearance of trend values at pre-defined graphic display locations.
Verify appearance of defined alarms on the alarm screens and maintenance workstation.
Check whether the AO blocks of valves are in CAS mode.
Check whether the PIC blocks are in MAN mode.
Adjust valve positions through individual valve display screens.
c. Network/segment verification
Verify uniformity of software/firmware versions in host and FF devices.
Verify correctness & uniformity of software versions in H1 cards.
Check communication and macro-cycle periods of all segments.
Check correct functioning of segment elements (H1 cards, power supply units, signal conditioners, etc.)
and whether eventual failed elements are reported in the error log of the system.
Verify system recovery after segment shorting.
Measure current consumption of segments.
Verify operation of back-up LAS function.
Rev 1.00.00 13/14

R&M Division
Check communication loads of segments.

Check stable operation of segments for 12 hours by means of bus monitor.
2.8.2 Checking of Fieldbus loops before pre-commissioning

Cable tests:
Measure cable resistance and capacitance between:
conductors,
conductors and shields,
conductors and ground, and
shield and ground.
Segment powers supply units and signal conditioners must be disconnected from cables during the above
tests.
Verify segment voltages:
At power supply unit output,
On H1 card,
On individual devices.
Oscilloscope and Fieldbus Monitor tests:
Signal flows running on segments shall be tested.
Good signal levels range from 0.8 to 1.2 volts. Verify the correct slope of leading & trailing edges and the
defined levelness of peaks for signal waveforms.
The shape of signal waveforms allows conclusions to be made with respect to lack or surplus of
termination elements and longer than required trunk & spur cable lengths.
2.9 Relevant standards and guidelines

Definition FFB physical layer: IEC 61158-2 and ANSI/ISA 50.02, Part 2
Electrical equipment in explosive environment: IEC-79-4
Electrical equipment in explosive environment: IEC 79-11, Part 11
Electrical equipment in explosive environment. General requirements: CENELEC EN50020, 1997.
Intrinsically safe protection
Electrical equipment in explosive environment. General requirements: CENELEC EN50039, Edition 1982.
Intrinsically safe electrical systems
Installation of electrical equipment in explosive atmosphere: IEC 79-14, Edition 1984
FFB System Engineering Guidelines - current last review
o FFB Engineering Guidelines, AG-181
o FFB 31.25 kbit/s Wiring and Intallation, AG-140
o FFB 31.25 kbit/s Intrinsically safe systems, AG-163
o Host Interoperability Support Test FF-569
o System architecture FF-581
o Function blocks (standard, advanced, improved, additional, flexible) FF-890-894
o Transducer blocks FF-902-904
o Fieldbus Power Supply Test Specification FF-831
o FFB cable test FF-844
14/14 Rev 1.00.00

SLOVNAFT a. s.
R&M Division
MOL Group
INSTRUMENTATION
28. Requirements for Field-Installed Bus System

2. Wireless communication between field device and control system
MGS-S-REF-I-28.2
Rev 1.00.00
SLOVNAFT a. s. MGS-M-REF-I-28.2
R&M Division
TECHNICAL SPECIFICATION - INSTRUMENTATION Rev.: Rev 1.00.00
28 Requirements for Field-Installed Bus System Date: 01.05.2016
2 Wireless communication between field device and control system Page/Pages: 2/20
Release list

1.00.00 25.11.2014 Issued for Wireless A. Pozsgai R.Batha
1.00.00 01.05.2016 Issued SN version Z. Stanová R. Kopálek Head of

Maintenance
R&M Division
Contents
Release list ................................................................................................................................................................... 2

Wireless communication between field device and control system ............................................................................. 4
1 Overview ................................................................................................................................................................ 4
2 Deviations .............................................................................................................................................................. 4
3 References for Wireless Industrial Communication .............................................................................................. 4
4 Abbreviation ........................................................................................................................................................... 4
5 Field communications accepted in MOL Group refineries .................................................................................... 5
6 Regulation of wireless communication .................................................................................................................. 6
7 General requirements of industrial wireless system architecture .......................................................................... 6
8 Security requirements ........................................................................................................................................... 7
9 Spare capacity and expansion of wireless system:............................................................................................... 8
10 Planning and design consideration of industrial wireless network ................................................................. 8
11 Requirements of wireless field device .......................................................................................................... 10
12 Installation requirements of industrial wireless network ............................................................................... 13
13 Test of industrial wireless network................................................................................................................ 13
14 Operational requirements of industrial wireless network .............................................................................. 15
15 Requirements for batteries ........................................................................................................................... 16
16 Appendix: ...................................................................................................................................................... 17
Rev:. 1.00.00 3/20

R&M Division
WIRELESS COMMUNICATION BETWEEN FIELD DEVICE AND CONTROL SYSTEM
1 Overview
This specification addresses the design principles and best practices regarding the designing, secure
implementation, testing and operation of wireless industrial field communication networks based on the
industrial standards. This specification details the decision to use wireless field communication versus to
use traditional hard wired system. The wireless field device shall be only used for indication of process
variables on Integrated Control System (ICS) and to connect devices to Field Instrumentation
Maintenance System (FIMS) by using wireless connection. The wireless field device shall not be used
for control purpose and as any part of Safety Instrumented System.
The scope of this specification are wireless field devices based on ISA100, Wireless HART wireless field
communications and connected wireless network elements (Access Point, repeater, Gateways etc.) in
order to connect them to Integrated Control System (ICS). Other wireless technologies and application
exist (e.g. Mobile Worker, wireless remote video monitoring, wireless personnel tracking, asset tracking
etc.) that may be integrated into the ICS, but they are out of scope of this specification.
In addition to systematizing wireless field communication, this specification sets forth the basic design
requirements applicable to the wireless field-communications, to be observed during the development of
the functional specification.
2 Deviations
The applicable Project Specification may contain deviations from or changes to this document.
Deviations from the contents of this specification and the Project Specification shall be permissible only
on the basis of prior written approval by MOL PLC.
The specified solutions shall be in conformance with the specification system, standards and
requirements of the applicable project documentation.
3 References for Wireless Industrial Communication

• IEEE Std 802.15.4
Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate
Wireless Personal Area Networks (LR-WPAN).
• ISA 100.11a or ISA 100 Wireless
Industrial communication networks. Fieldbus specifications. Wireless systems for industrial
automation: process control and related applications
• Wireless HART
Industrial communication networks - Fieldbus specifications - WirelessHART communication
network and communication profile
• IEC 61158-x
Industrial communication networks – Fieldbus specifications
• IEEE Std 802.11 [ISO/IEC 8802-11]
Wireless LAN Medium Access Control (MAC) Sublayer and Physical Layer Specifications
(WLAN)
4 Abbreviation
• AP: Access Point
• BER: Bit Error Rate
• CF: Capability File
• DD: Device Description
4/20 Rev.: 1.00.00

R&M Division
• EIRP: Equivalent Isotropic Radiated Power. Computed quantity which cannot be measured
directly. It is equal to the product of the total radiated antenna power multiplied by the antenna
gain.
• FIMS: Field device Maintenance System
• ICS: Integrated Control System
• ISA100.11a: ISA100.11a is a wireless sensor network protocol standard developed by the
International Society of Automation.
• ISM band: industrial, scientific and medical bands: 2.4 GHz band: 2.4000–2.4835 GHz and 5.8
GHz band: 5.725 to 5.875 GHz are supported range
• LOS: Line of Sight
• LR-WPAN: Low Rate-Wireless Personal Area Network
• PER: Packet Error Rate, PER (%) = Number of lost packets/Number of transmitted packets × 100
• QoS. Quality of Service
• RF: Radio Frequency
• RSS/RSSI: Received Signal Strength indicator is a measurement of the power present in a
received radio signal
• RSQI: Receive Signal Quality Index
• SNR: Signal-to-Noise Ratio (SNR = Received Power - Chanel Noise)
• TCO: Total Cost of Ownership
• Update Rate: The user specified interval at which a wireless field device (sensor, transmitter) will
detect a measurement and transmit the measurement to the Gateway (i.e. sample rate).
• Wi-Fi: Wireless Fidelity refers to wireless networks that use the IEEE 802.11 standard and
operates 2,4 GHz and 5 GHz bands.
• WISN: Wireless Industrial Sensor Network
• WLAN: Wireless Local Area Network
• WPN: Wireless Plant Network
5 Field communications accepted in MOL Group refineries

The field communications are grouped according to the physical layers and transmission media:
Wire media (voltage/current mode, power/no power via the bus, intrinsically/not intrinsically safe,
twisted-pair/coaxial)
Optical media (dual/single fiber mode)
Radio media or wireless (Radio Frequency: RF)
Wireless communications
Wireless communication is the transfer of information over a distance without the use of electrical and/or
optical conductors (wires or fiber optic cables).
The industrial wireless communications shall support the one of the following ISM bands (applicable to
the wireless field network and wireless field devices):
2.4 GHz ISM (2.4 GHz radio band: 2.4000–2.4835 GHz supported range)
5 GHz ISM (5.8 GHz radio band: 5.725 to 5.875 GHz supported range)
Within the ISM band, 2.4GHz band and the 5 GHz band communications are used in the following
standards and supported in MOL Group Refineries:
Wireless Industrial Sensor Network (WISN): IEEE 802.15.4 is a selforganizing, selfhealing
mesh used in Low Power and Low Rate (250 kb/s).
The following standard and specification are supported in MOL Group Refineries:
• IEC/PAS-62734 (ISA 100.11a or ISA100 Wireless)
• IEC/PAS-62591(WirelessHART)
Rev:. 1.00.00 5/20

R&M Division
Wireless Plant Network (WPN): IEEE 802.11b/g/n (2,4 GHz WiFi) and IEEE 802.11a/na (5 GHz
WLAN) are used for a with higher transmission power level and with a higher data
communication rate.
Preconditions to use wireless field communication for connection of wireless field devices
Wireless field devices are not allowed to use for control purpose (closed control loop, PID
controller) and in a Safety Instrumented System.
The decision to use the wireless field device versus the traditional wired solution shall be based
on lifecycle cost analysis as results of Total Cost of Ownership (TCO) consideration with regard
to the applicability constrains.
TCO generally should consist the following of three life cycle phases for time period of 15 years:
• Procurement (C0: engineering & design, investment, deployment as implementation,
installation, integration, FAT, commissioning, SAT, documentation, training, initial spares etc.)
• Operations (Ki: general maintenance, repair, software/hardware upgrade, management of
change (MoC), backup, parts replacement (cards, battery), spare parts, HVAC (heating,
ventilating, and air conditioning), audit, training, cost of downtime, etc.)
Note: The wired solution should be calculated with 200 m multi-cable and 60 m individual cable.
The built in spare parts shall be 10 % and extendibility shall be 20 %.
TCO calculation form:
Where:
Cost of procurement
Cost of operation
n Last year of lifecycle
r Weighted Average Cost of Capital (WACC)
The Vendor shall attached the TCO calculation of wireless field communication solution and the
traditional wired solution in order to prove the proposed solution is reasonable.
Deviations from applying of TCO calculation for wireless field communication shall be permissible
only on the basis of prior written approval by MOL PLC or special requirements of Project
Specification.
6 Regulation of wireless communication

The wireless field device shall comply with European Radio equipment and Telecommunications
Terminal Equipment (R&TTE) Directive: 1999/5/EC)
The wireless field device shall comply with EMC directive 89/336/EEC
The wireless field device shall include CE Mark
The wireless field device shall be RF Certified according to ETSI EN 300328, ETSI EN 301893
In the lack of individual licensing obligation no protection against interference may be granted to
radio use. Station without individual licensing may not claim protection against harmful
interference from other radio stations and shall not cause harmful interference to radio stations of
primary wireless services which has individual licensing (protection against interference is
granted)
Even when exemption from individual licensing is granted, the technical norms of band use shall
be adhered to, with special regard to the limitation of power specified for radiation.
The Vendor of wireless device shall have the responsibility to get the certification of product
based on licensing and/or registration procedure from the relevant regulatory body (NCA)
The settings of maximum transmit power shall be set channel by channel according to regulations
of National Communications Authority (NCA), because the maximum transmit powers and the
antenna gain of wireless device are higher than the allowed maximum EIRP according to NCA’s
regulations.
7 General requirements of industrial wireless system architecture

Wireless system architecture in the unit of refineries:
6/20 Rev.: 1.00.00

R&M Division
The industrial wireless system consists wireless field device using WISN and WPN which can be:
• Wireless field device (wireless sensor, transmitter, adapter, repeater)
• Wireless network component (wireless Access Point/ Gateway)
The WISN shall be a self-configuring and self-healing mesh network.
The WISN shall support a mix of wireless field device types and update rates.
The WISN and WPN architecture shall be capable of supporting both wireless and wired media to
connect the wireless network to the wired network (e.g. Process Control Network).
The industrial wireless network architecture shall have an IP-compatible network layer and
support for tunneling, i.e., transporting other protocols through the wireless network
The industrial wireless network architecture shall support the system management of all wired
and wireless communication devices
The infrastructure of industrial wireless network shall be scalable and support the following
topologies:
• Point to Point
• Star
• Redundant Star
• Mesh
• Star-Mesh (combination of star and mesh wireless segment)
• Infrastructure Mesh (combination of the WISN and WPN as backbone/backhaul network to
provide a plant-wide coverage.)
The infrastructure of industrial wireless network to be deployed shall support at minimum the
following wireless networks:
• Wireless Industrial Sensor Network based on:
ISA 100.11a or ISA 100 Wireless
WirelessHART)
• Wireless Plant Network based on:
IEEE 802.11b/g/n (2,4 GHz WLAN)
IEEE 802.11a/na (5 GHz WLAN)
The infrastructure of industrial wireless network shall be easily extensible: a new wireless device
can automatically join the network. Automatic device joining and network formation enables
system configuration with minimal need for personnel with specialized radio frequency (RF) skills
or tools.
Self-organizing network shall support the redundant communications from wireless field device to
Host system (ICS with redundant Process Control Network connection) via redundant Access
Point and redundant Gateway.
The industrial wireless network shall support a minimum of 2000 industrial wireless devices
operating at a minimum average update rate of 10 seconds using sufficient number of Access
Points and Gateways to connect to Host System.
The industrial wireless network shall support wireless devices (wireless sensor, transmitters)
operating at update rates of 1 second as minimum, but as additional feature of configuring the
same at update rates from1, 5, 10, 30 or 60 seconds to one hour shall also be available.
The industrial wireless network architecture shall be secure, including data integrity, encryption,
data authenticity, replay protection, and delay protection
8 Security requirements
Mechanisms for protecting the industrial wireless network shall be implemented.
• Encryption: Data communicator shall have least 128-bit encryption.
• Authentication: Only wireless field devices authenticated by the System Manager and/or
Security Manager can join and exchange data.
• Integrity: End-to-end basis data integrity and transport security shall be provided.
Key Management: All wireless devices shall have a join key that acts as a password that the
device uses to authenticate it to the network.
Rev:. 1.00.00 7/20

R&M Division
9 Spare capacity and expansion of wireless system:

The wireless system as part of ICS shall be supplied with minimum 10% built in hardware spare
capacity and 20% expandability at mechanical completion for all elements of the system
configuration, furthermore including application software, graphics, history, reports, and trends. In
addition, the system shall have 40% spare performance (e.g., communication idle time) to
execute all required communication including diagnostic information as well.
The capacity and spare capacity of wireless Gateway shall be considered. At a minimum, each
process unit should have its own wireless Gateway with spare capacity. Each wireless Gateway
shall have at minimum 40% spare capacity.
The plant wide WISN network as part of ICS system shall support a minimum of 40 pcs wireless
infrastructure nodes (AP, Gateway) in order to provide cost-effective links between remotely
located WISN segment and cover the plant area.
Spare parts shall be available for a minimum period of 10 years after warranty period for all
equipment supplied by the Vendor. In the event of non-availability of spares due to fast
obsolescence of hardware and software, the vendor shall arrange to upgrade/ replace the
equipment with equivalent or higher hardware and software.
10 Planning and design consideration of industrial wireless network

Planning of industrial wireless network:
Identification of the wireless field devices and their connection requirements (e.g
transmission/update rate, reliability) Note: Does not oversample in order to maximize the battery
lifetime.
The wireless field device with the wireless connection shall be classified according to ISA100
Class
Considering requirements of wireless field devices with regards for outdoor and remote locations,
the preliminary industrial wireless network topology
Determination of the industrial wireless network topologies:
• To determine the locations, size, dimensions of required signal coverage area and performance
of industrial wireless network
• To select the most appropriate industrial wireless network topology regarding the following
preferences:
Table-1: Topology consideration
Topology: Redundant Infrastructure
Star Mesh Star-Mesh
Supported function: Star Mesh
Deterministic Yes Yes No Moderate Yes
Low latency Yes Yes No Moderate Yes
Redundant route (multi-path) No Yes Yes Yes Yes
Long Battery Life Yes Yes No Moderate Yes
Coverage No No Yes Yes Yes
Installation Yes Yes Yes No Yes
Trouble-Shooting Yes Yes Moderate Moderate No
Note: An infrastructure mesh eliminates the requirement for cabling from the APs or wireless routers to
wired ports on switches, or for cabling between APs.
The transmission quality of the industrial wireless network should be determined by transmission
latency, jitter and loss.
To minimize the number of hops to the Gateway in order to reduce latency.
To determine the optimal number and distribution of wireless devices sized to support the
infrastructure mesh or wireless network coverage required.
To determine the wireless and wired elements (AP, Gateway, Repeaters) and how they can be
integrated into the Integrated Control System (location of wired LAN access) including time
synchronization.
Wireless network design (RF)
To ensure the all wireless applications with regards to power levels, RF spectrum usage, and
encryption shall be compliance with government regulation.
8/20 Rev.: 1.00.00

R&M Division
Wireless (RF) Site Survey’s with spectrum scans shall be performed before RF design of wireless
network in order to reveal problems such as interference (e.g. by radar), obstructions.
The RF bands with the assigned channel (frequency channel hopping pattern) to be used shall be
verified and approved by the MOL.
The new industrial wireless networks shall be designed to coexist with other existing wireless
networks. Strong interference sources must be addressed (removed, avoided, or minimized)
before the installation.
To determine RF power level settings according to the location of deployment with regards
allowed maximum EIRP according to NCA’s regulations.
Coexisting capability (e.g. channel-hopping, DSSS: direct-sequence, spread spectrum, low
transmit power) with other RF sources using ISM radio band shall be taken into account.
Requirements of Wireless (RF) Site Survey:

Wireless Site Survey is not required (condition shall be confirmed with the site plan):
• Outdoor installation, topology with up to two hops, good line-of-sight, and sufficient height of
antennas ensuring the clear zone with no obstacles
Wireless Site Survey is required:
• Communication between control room (indoors) and site (outdoors).
• At least one wireless device is located in a shielded enclosure such as a basement or
prefabricated building.
• Wireless devices are mounted on moving objects.
• There is another 2.4/5 GHz wireless network (e.g., WiFi) near the communication path.
To visually evaluate the site to check the line-of-sight of wireless communication paths, how to
install wireless field devices, how to feed power to AP, and how to layout the communication
paths to the Host System (ICS) system.
Arrange point-to-point mesh in various locations to measure the RF propagation ability in the site.
Received Signal Strength Indicator (RSSI) can serve as an indicator of the RF environment.
The conditions of deployment shall be verified as following:
• Any obstructions that may enter and leave the coverage areas
• Material compositions of all the coverage areas in a site
• Installation limitations for the antennas, APs, and cabling
• Environmental characteristics of the site
All planned wireless device locations shall be physically verified
During the site survey, considerations such as weather extremes, lightning, physical security, and
local regulations need to be taken into account.
To conduct an RF spectrum analysis on the 2.4 GHz and 5 GHz ISM band to detect any potential
RF interference.
To determine the practical EIRP range of the radio in the given environment with regards the
allowed EIRP range.
Link budget analysis should be conducted for each wireless field devices with regards PER < 1%
requirement. (receive sensitivity: -96 - 90 dBm or less, acceptable range of RSSI: -70 dBm to -25
dBm, including 10-15 dB fade margin). Sensitivity threshold or low RSSI threshold should be
define.
The Packet Error Rate shall not be higher than 15 % as design intent.
Spectrum analysis of the site shall be carried out to detect any wireless systems already in place
The existing deployed wireless networks shall be verified
Report shall be provided for wireless applications spectrum usage
To evaluate various of antenna choices (antenna type: normal omni-directional antenna (2 dBi),
high-gain antenna (6 dBi), to optimize performance
To find the best locations of planned wireless device with regards to mounting and power
requirements
The assigned locations of all wireless field devices, network components to be installed shall be
physically tested and verified
Wireless devices (instruments, network components) selection shall be verified to meet the
requirements
Rev:. 1.00.00 9/20

R&M Division
Wireless field network site planning:

To find the best position of wireless field devices to minimize obstructions between
interconnected devices (wireless sensor, wireless transmitters, wireless network component: AP,
Gateway) for maintaining line of sight or near line of sight improves the wireless link performance.
The wireless field device should have clear Line of Sight (LOS) and shall be mounted at least 2
meters above the ground
The number of hops shall be minimized to the wireless Gateway in order to reduce latency and
insufficient communications.
A wireless mesh network shall ensure multiple communication pathways with regards its reliability
To place the wireless field devices less than 500 meters from one another. The range varies
depending on the environment, line of sight, transmit power settings, antenna type, and antenna
gain.
The process environment should be classified to the following obstruction classes with the
allowed distance between wireless field devices:
• Class A: Clear Line of Site. The antenna for the device is mounted above obstructions and the
angle of the terrain change is less than 5 degrees. Examples: tank farm, pipeline
• Class B: Light Obstruction: lots of space between and above makes for good RF propagation.
Examples: Area with few buildings, machines and low dense piping
• Class C: Medium Obstruction: lots of space between equipment and infrastructure. Area with
many buildings, machines and dense piping
• Class D: Heavy Obstruction: heavy density plant environment. Inside of the plan surrounded by
metal equipment, machines and high dense piping.
The expected wireless communication distance:
• Class A: 200-500 m
• Class B: 150-200 m
• Class C: 75-150 m
• Class D: 30-75 m
The Wireless Access Point should be installed about 2 m above the rooftop of the control building
in order to ensure clear LOS wireless connection and LAN connection to Integrated Process
Control System as well.
In such cases, the line of sight is limited or there are obstructions with reflected waves Wireless
Repeater/routing device should be used. The Wireless Repeater/routing device should be placed
near the top of highest tower of the plan in order to ensure clear LOS connection between
wireless field devices and Access Point.
Remote antenna should be used to eliminate the effect of obstructions on site.
The hazardous location requirements shall be considered (ATEX, IP classification)
Limitation the number of devices connected between the Process Control Network and the
wireless field device to prevent time delays.
11 Requirements of wireless field device

General requirements:
The wireless field devices shall be fully compliance with used wireless network standard and shall
have certification about successfully performed interoperability test, shall be approved.
All wireless field devices shall directly be connected to the WISN.
The wireless field device shall support the following antenna types:
• Dual-band omni-directional antenna
• 2 dBi 2.4 GHz 60° corner antenna
• 6 dBi 5.8 GHz 30° directional antenna
• Remote antenna with lightning arrestor
All wireless field devices shall transmit and receive wireless network packets and perform the
basic functions necessary to support network formation and maintenance.
All wireless field devices shall be able to source and sink packets and be capable of routing
packets on behalf of other devices in the network.
10/20 Rev.: 1.00.00

R&M Division
Where surge protection is deemed necessary (e.g. location of AP with areas of high lightning
incidence, or where large inductive loads are started and stopped), surge protection should be
provided.
Online download of a software upgrade to a wireless field device from a Host System (ICS) shall
be supported.
If the wireless field device is located in a hazardous area, the wireless field device shall have the
appropriate approvals (e.g. ATEX: Class I, Zone 2; Ex nA IIC T4 or Ex ia IIC T4 ).
The wireless field devices shall be housed in a rugged aluminum-alloy casing that meets IP 66
and certification.
The wireless field device shall be rated to operate under the following conditions:
• Operating Temperature: -40° to +75°C
• Transportation and Storage Temperature: -40° to +7 5° C
• Operating Humidity: 0-100% non-condensing
Wireless Access Point requirements:

Wireless AP allows wireless field devices to connect to Gateway(s) or provides a bridge between the
wireless filed network and the wireless or wired infrastructure backbone/backhaul network.
Note: The wireless Access Point and the Gateway can be integrated or separate equipment.
Wireless AP shall support ISA100.11a / Wireless HART self-organizing, self-healing mesh
network.
Wireless AP shall support routing and non-routing ISA100.11a / WirelessHART field devices
Wireless AP shall have ability to configure wireless field device on the same wireless network at
different update rates
Wireless AP shall have capable of Built-in wireless field device redundancy for assured
communications
Wireless AP shall support end-to-end industrial security with industry standard 128-bit encryption
Wireless AP shall support firmware upgrades and configuration over the air.
Wireless AP shall have antenna diversity for wireless field devices access point improving
reliability and range
Wireless Gateway requirements:

Wireless network component that routes packets from a wireless network (directly or through a
wireless Access Point) to Host System (ICS) with another network, typically a wired Process Control
Network (or LAN).
Note: The wireless Access Point and the Gateway can be integrated or separate equipment.
Each wireless field device requires its own dedicated wireless Gateway or multiple Gateways.
Wireless Gateway shall be a bridge (transmitting data, process value, device status, alert,
diagnostic information etc.) between the wireless field network and the Host System (ICS).
Wireless Gateway shall have capability for System Management (controls the wireless
communication of wireless field devices, configures the wireless field devices, and provides the
database function)
Wireless Gateway shall have capability for Security Management of wireless field network
(wireless device authentication, encryption management)
Wireless Gateway shall have capability for configuration of wireless network components and
wireless field devices.
Wireless Gateway shall be connected to the upper network system using one of the following
interface:
• Ethernet 100BASE-TX metal cable
• Ethernet 100BASE-FX fiber optic cable
• Wireless LAN (IEEE802.11a/b/g/n)
• Serial communication (RS-485)
Support the Modbus/RTU, Modbus/TCP, EtherNet/IP, or OPC-DA protocol.
Host System (ICS) connection to Gateway shall be redundant.
The wireless network architecture shall support redundant Gateway with redundant path (e.g.
duocast) to wireless field device and the switch over time shall be less than 1 second without any
data losses of wireless network
Rev:. 1.00.00 11/20

R&M Division
Uninterruptible Power Supply (UPS) shall be used to power the Gateway.

Wireless Gateway shall be controlled, configured and diagnose via an user interface.
The Wireless Gateway shall support that the I/O channel of wireless field device can be assigned
to Function Block (e.g. AI, AO) of one controller as virtual wireless process I/O card in order to be
part of the control strategy. The control strategies can integrate both value (PV) and status
(bad_PV) on supported wireless connection from wireless field device.
The Gateway shall support Field device Tool/Device Type Manager (FDT/DTM) communication
interface request (communication DTM).
Wireless field instrument requirements:

Wireless field instrument is a wireless field device which have a similar basic capability as traditional
hard wired field instrument with additional capability to connect to Wireless Field Network. Wireless
field instrument detects a measurement and transmits the measurements to the Wireless Gateway
through another wireless field device (as routing device or repeater) or Wireless Access Point.
For the purpose of operation, maintenance of intelligent wireless field device it should have the
minimum following capability: configuring, calibrating, monitoring, advanced diagnostics
A Device Description (DD) / Capability File (CF) of wireless field device shall be provided to allow
the Host System (ICS) to access all of the capabilities, parameters as device status, process data
measurements, device diagnostics, multi-variable measurements and device configuration
information in a digital format installed in the wireless field device.
Wireless field devices shall generate alerts, due to miscommunication, misoperation (diagnostics)
or failure.
Self-checking feature shall continuously monitor the operation to identify and report sensor or
device parameters that are out of specification.
The integration of wireless field device into Host System (ICS) shall be supported as following:
• Offline and online configuration of Wireless field devices shall be provided from Host System
(ICS)
• Parameters of wireless field device shall be integrated into control environment of Host System
(ICS)
• Wireless field device alarms and events shall be integrated within the alarm summary and
event journal of Host System (ICS) system.
The wireless field device shall be capable to route the wireless communication between other
wireless field devices and Access Point as Wireless Router.
Wireless field instrument shall be located within the wireless communication range are within the
line of sight of each other.
Wireless Diagnostic Adaptor requirements:

The Wireless Diagnostic Adaptor shall be a screw-in or easily installed device into an existing
hard wired field device with diagnostic.
The Wireless Diagnostic Adaptor shall not impact the 4-20 mA loop of the wired device (low
voltage drop).
The Wireless Diagnostic Adaptor shall be powered by 4-20 mA loop (without any disturbance)
and/or by battery pack.
The use of Wireless Diagnostic Adaptor shall not degrade the ATEX rating of loop.
The Wireless Diagnostic Adaptor shall have 1 second to 60 minutes update rate.
The Wireless Diagnostic Adaptor shall access the performance information (ex. Valve Signature,
PVST, etc.), calibration information, diagnostics information (device health status), device
configuration parameters
The Wireless Diagnostic Adaptor shall transmit Process variable and diagnostic data.
The Wireless Diagnostic Adaptor shall support process alert.
The Wireless Diagnostic Adaptor shall allow the HART device configuration from Field Devieation
Maintenance System: AMS or FDM.
12/20 Rev.: 1.00.00

R&M Division
12 Installation requirements of industrial wireless network

Each wireless field device shall be assigned to the related wireless Access Point / Gateway
assigned to the given process unit, that manages the specific wireless field network.
The sufficient selection of antenna types, gain, and power settings is required for any successful
industrial wireless network installation and operation. Note: The antenna with higher gain than
necessary or setting power levels higher than necessary may cause multipath fading which
degrades the network performance.
Antennas shall be installed vertically. Antennas shall be at least 0,3 – 1 m away from mounting
piping or plumbing.
The sufficient Signal-to-Noise Ratio (SNR: Received Power – Channel Noise) shall be provided
for the receiver to achieve a specified level of reliability in terms of Bit Error Rate (BER) or PER
(Packet Error Rate).
Documentation shall be provided on the range of the wireless field device, power requirements,
and the designated frequencies of operation for each device.
Recommended alarm settings of wireless field device shall be allowed in accordance to the
needs of the system.
Interoperability limits for the wireless field device should be defined specifically stating the
devices that could be replaced and any associated problems that might be associated with the
replacement.
Security measures / devices, such as passwords or security codes shall be provided to protect
the wireless field device from unauthorized modification or use.
The vendor-configured settings or manufacture default configuration shall be documented to
ensure the reconfiguration due to replacement of wireless field device.
The security measures associated with the industrial wireless network segment (encryption
devices, password protection, etc.) shall be documented and configuration control options shall
be identified that enable varying of the security level of the device.
Interference rejection shall be demonstrated and reported
The battery (power module) should not be installed on any wireless field device until the related
Wireless Gateway is installed and functioning properly
13 Test of industrial wireless network

Factory Acceptance Test (FAT) requirements:
The FAT should be conducted in accordance with the FAT planning. These tests should show
that all the functions perform correctly.
The Vendor shall perform their own standard internal test before the FAT, and present its
certification to the Client. Vendor’s internal test shall include a complete system check,
supplemented with the hardware, software and control functions of all the subsystems.
The results of FAT should be documented, stating the test cases, the test results, and whether
the objectives and criteria of the test criteria have been met. If there is a failure during test, the
reasons for the failure should be documented and analyzed and the appropriate corrective action
should be implemented.
The tests shall be performed at the manufacturer’s premises (Factory Acceptance Test: FAT),
and shall be repeated after the assembly work and deployment has been completed at the user’s
premises (Site Acceptance Test: SAT).
Ten weeks before the tests, Vendor shall hand over the detailed description of the standard tests
(FAT protocols) to the Client, as well as the program and the schedule of the tests. The Vendor
shall provide one copy of an as-built documentation on the system as the attachment to the test
protocol. Client shall approve the FAT protocols.
The FAT protocol shall consist the test procedure and test acceptance criteria.
The Vendor shall perform the FAT with the Client present.
The system Vendor shall provide suitable testing devices, testing systems and qualified
personnel to proceed with the tests according to schedule. Protocol shall be prepared of each
test.
Rev:. 1.00.00 13/20

R&M Division
The participation of the representatives of the Client shall not in any way release the system
Vendor from their guarantee responsibilities regarding material quality, installation, production
and operability.
The vendor shall remove or disable all software artifacts that are not required for the operation
and maintenance of the device prior to the Factory Acceptance Test (FAT).
The Vendor shall ensure that the systems have had a minimum of a 48-hour burn-in.
The Vendor shall perform an interference rejection test and supply the results with an explanation
of the results.
The vendor shall verify compatibility of the wireless field device with other devices with which the
device must interface.
To add one of each type of wireless field device to the network and verify proper connectivity.
To perform sensitivity test: The wireless field device should be separated in which the received
signal strength (RSS) at the receiver is at its minimum while packet error rate (PER) remains at
0%. The IEEE 802.15.4 standard specifies that a compliant device shall be capable of achieving
a sensitivity of -85 dBm or better.
To verify connectivity between the wireless Gateway and the host system (ICS) application and
an integration test shall be carried out.
To test in dense highly radio reflective environments in order to prove the wireless connectivity
the reliability and immunity to reflection.
To perform coexistence test operating on the unlicensed 2.4 GHz ISM band in a coexistence
environment with several kind of wireless devices (eg. cell phones, Wireless handheld
computers, Wireless local area networks (802.11.a/b/g/ac), 802.15.1 (Bluetooth), Zigbee, RF
Identification (RFID) bar code readers etc.
Requirements of Device Integration Test:

Device Integration Testing verifies that the selected wireless field devices and wireless network
components are truly compatible with the Host (ICS) system (and software revision) selected and
with each other. Sufficient operation time should be allowed to ensure stability of all devices. Monitor
stable operation for a minimum of 12 hours. Stable means no unexplained errors observed
The minimum subjects of device integration test:
The correct hardware and software version of the wireless field device are represented in the
Host system DD/CF library.
The default parameter settings from the factory and what needs to be modified for the specific
project
To check that the relevant wireless communication parameters (RF channel selection, EIRP) are
correct and that the update rate has been set for each wireless device. To check the quality of
wireless communication by the wireless KPI (PER).
Procedure of downloading, calibration and setup shall be checked.
Checking of FIMS (EDDL, FDT/DTM or Asset Management) interfaces are available, and correct
operation. To verify each wireless field device can be properly accessed and configured via the
FIMS solution.
Testing of the diagnostic alert/alarms and Host system display or handle alerts/alarms (especially
multiple alerts/alarms)
Transfer and display of data from wireless field devices to the Faceplate, HMI graphic display and
historian.
Site Acceptance Test (SAT) requirements:

The SAT shall be based on written SAT plan/procedure
The SAT shall verify that the installed system meets the specified requirements.
To verify the installed infrastructure of industrial wireless network.
To verify industrial wireless network communication
To verify the correct configuration of industrial wireless network components
(AP/Gateway/repeaters).
Wireless Connectivity Test:

To verify that all wireless devices are connected, pass the following Wireless Connectivity Test:
14/20 Rev.: 1.00.00

R&M Division
To verify the sufficient connection of AP and Gateway to HOST system (ICS).

To verify the device is joining the network within a reasonable time period (> 15 min)
To verify each wireless field device is reporting to the correct AP/Gateway and each AP/Gateway
is connected into the correct host system (ICS). To report the connection summary. To lists all of
the wireless field devices with wireless network disconnection and alarms
For industrial wireless field communication equipment, tests during SAT are to be conducted to
demonstrate that RF transmission does not cause failure of any equipment of ICS and does not
fail its self as a result of electromagnetic interference during expected operating conditions.
Verify that network diagnostics indicate the device has proper bandwidth. The AP/Gateway
should have an indication.
RSS shall be measured and documented at the wireless field device is suggested to be
sensitivity plus 15 dBm link margin (typically: from -70 dBm to -67 dBm) while verify the
BER/PER.
Signal-to-Noise Ratio (SNR) shall be measured and documented at the wireless field device in
order to achieve a specified level of reliability in terms of BER or PER. The minimum SNR at the
wireless field device should be at least 25 dB to provide a safety margin and minimize
retransmissions.
Wireless connection quality shall be checked and statistic shall be made (RSS, SNR, BER, PER).
Note: recommended RSS and SNR parameters that should be maintained in the wireless
coverage area shall be defined by the Vendor of wireless field device (eg. minimum RSS of -67
dBm, minimum SNR of 25 dB). To list all wireless connections with a poor or unacceptable signal
quality.
To verify the wireless field device reliability is 99% or greater. Statistics may need to be reset and
recertified to remove any anomalies incurred during startup and not indicative of long term
performance. Allow at least 2 hours for the network to gather new network statistics.
To perform site Device Integration Test (see at the FAT requirements).
Loop check of wireless field devices:

The traditional concept of loop checking (as used with 4-20 mA and/or FF devices) can be
applied for the basic functionality of the wireless field device. The minimum subjects of wireless
field device loop test:
The correct database population shall be checked by comparison with the relevant detail design
documents (tagname, description associated faceplate, HMI etc.).
To verify the appropriate scale, engineering unit and input characterization are configured as
needed in the AI and the output direction in AO function block. Furthermore to verify the correct
state of DI/DO function block.
To verify faceplates and all HMI elements for connected wireless field devices.
Simulate a process variable equal to 0%, 50% and 100% of the scale and verify on the faceplate.
To prepare SAT report and signoff with customer.
14 Operational requirements of industrial wireless network

General operational requirements
Using the industrial wireless network management, users shall be capable of configuring the
infrastructure nodes, provision them and monitor key network parameters.
The wireless network management should provide a visual representation of the mesh network, i.e.
showing the connection and the status of the connection between various infrastructure nodes.
The wireless field network should support the following network management options:
Plant should manage all devices associated to the network, i.e. minimum 2000 devices, through a
single network management application.
Management application should allow users to easily add, edit and delete wireless field device to
the system.
Wireless connection quality shall be checked continuously based on:
• Receive Signal Strength Index (RSSI): received signal strength in dBm
• Receive Signal Quality Index (RSQI): A value of 1-63 indicates a poor signal, 64-127 a fair
signal, 128-191 a good signal, and 192-255 an excellent signal.
Rev:. 1.00.00 15/20

R&M Division
• Transmit Fail Ratio (TxFailRatio)

• Hop count
• Bit Error Rate (BER) is commonly used for evaluating the performance of field wireless devices.
BER is measured by checking which bits are received incorrectly during the communication of
predetermined bit patterns.
• Packet Error Rate (PER) is the ratio of incorrectly received packets to the whole packets
transmitted. PER is the most fundamental index for evaluating wireless communication in plant
sites.
• System reliability, delay time for a packet to travel from a field wireless device to the host
system
The wireless field equipment shall be periodically listed that require battery replacement and/or
have battery level less than 50%.
Long term management for the coexistence of different applications shall be established
15 Requirements for batteries

Wireless field device shall have long battery life (3 to 10 years) according to the following table:
Table-2: Expected battery life
Update Rate (sec):
1 sec 5 sec 10 sec 30 sec or >
Ambient Temperature
0 °C 4 years 10 years 10 years 10 years
Note: If the wireless field device is used as router device (repeater) the battery life may be
reduced.
The estimated lifetime of batteries or battery replacement period for each field wireless device
shall be provided.
The wireless field device shall provide predictable power management to ensure uptime and
optimize maintenance
The Vendor shall provide spare batteries for each wireless field device which are required for two
years continuous operation.
Batteries cells should be assembled by a manufacturer into a battery pack to ensure safe
handling and transportation.
Battery pack should be designed for the process environment with mechanical properties that
provide drop protection and operation over normal process temperatures expected for devices.
Battery pack should prevent a depleted cell being introduced in circuit with a charged cell, which
can cause unintended electrical currents and heat.
Battery pack shall prevent intended and unintended short-circuiting that could lead to heat or
spark.
Battery pack should provide ease of replacement. Battery replacement should take minimal time
and training.
Battery pack shall be intrinsically safe and not require removal of the wireless field device for
replacement. Note: The opening of battery pack is not allowed on site.
If the battery pack does not have Ex protection, transmitter enclosure shall not be opened when
an explosive gas atmosphere is present.
Vendors may provide energy harvesting options as alternatives to batteries that may include
solar, thermal, vibration, and wind solutions.
16/20 Rev.: 1.00.00

R&M Division
16 Appendix:
Appendix A.: Check list of SAT
NOT
Item Description OK Note
OK
1. Check the Wireless Gateway
1.1 Identification Check:
Wireless Gateway Tag:
Description:
Wireless Network ID:
Join key (x-x-x-x):Type:
1.2 Wireless field device Check:

Vendor:
Model:
Revision:
Serial no.:
Status (Unprovisioned/Joining/Provisioning/Joined/Rejected):
1.3 Power Supply Check:

Check the redundant Power Supply of Gateway
1.4 Host Connection Check:
Check the redundant connection to Host System (ICS):
Ethernet:
• MODBUS/TCP check
• OPC check
Serial (RS-485/RS-232):
• MODBUS/RTU
Fiber Optics:
Wi-Fi:
1.5 Check the connection to Access Point side
1.6 Check the correct time and date settings
1.7 Check the system Alarm status of Wireless Gateway
1.8 Check the wireless field device commissioning into related Gateway
and then into Host System (ICS)
1.9 Check the wireless Gateway Capacity/wireless network size.
Gateway Capacity (wireless device):
Joined wireless field device:
Spare capacity (%):
1.10 Wireless Network Security Check:
2. Check the Access Point

2.1 Identification Check:
Wireless Access Point Tag:
Description:
2.1 Wireless field device Check:

Type:
Vendor:
Model:
Hardware Revision:
Software Revision:
Serial no.:
Status:
IP6 Address:
2.3 Connectivity Status Check:

RSSI: dBm
Rev:. 1.00.00 17/20

R&M Division
NOT
OK
SNR: dB or
RSQI: No/Poor/Fair/Good/Excellent
Transmit Fail Ratio (TxFailRatio):
Bit Error Rate (BER):
Packet Error Rate (PER):
RF Chanel Configuration Check:
Routing: (Enabled/Disabled)
Maximum Hops:
Enabled Channel:
11 / 12 / 13 / 14 / 15 / 16 / 17 / 18 / 19 / 20 / 21 / 22 / 23 / 24 / 25
3. Check the wireless field device

3.1 Identification Check: off-line
Wireless field device Tag:
Description:
3.2 Wireless field device Check: off-line

Type:
Vendor/Manufacturer:
Model:
Hardware Revision:
Software Revision:
Serial no.:
Status:
IP6 Address:
Power Source (Line, Battery):
Routing: Routing/Non-Routing
3.3 Power Supply Check: off-line

Type (Lithium Battery / Loop Powered / Energy Harvesting):
Intrinsically Safe (Yes/No):
Field Replaceable (Yes/No):
Power Supply Status:
Power Supply Voltage:
Battery Level (%):
3.4 Device Integrity Check: off-line
Device File Checking:
Capability File (CF) File:
CF Revision:
Device Description (DD) File:
DD Revision:
Checking of FIMS (EDDL, FDT/DTM or Asset Management)
interfaces are available, and correct operation.
• Device Configuration Interface
• Device Calibration Interface
• Device Diagnostic Interface
• Device Diagnostic Alarm on the Alarm Summary
3.5 Configuration Data Review: off-line
Review of factory default configurations:
Check the basic setup:
AI / MAI FB Configuration Check:
• Signal conversion: direct, indirect, square root
• Filtering:
AO FB:
• Output Scale:
• Output Direction: Direct, Reverse:
• OP Hi limit:
18/20 Rev.: 1.00.00

R&M Division
NOT
OK
• OP Low limit:
• OP Rate of Change limit:
3.6 Commissioning of wireless field device to AP and Gateway
3.7 Connectivity Status Check: on-line
Antenna Type (Omnidirection/High Gain/Directional)
Operating Frequency (GHz):
Connection Type (Direct/Routed):
If Routed, Number of Available Neighbors:
RSSI: dBm
SNR: dB or
RSQI: No/Poor/Fair/Good/Excellent
Transmit Fail Ratio (TxFailRatio):
Bit Error Rate (BER):
Packet Error Rate (PER):
RSSI threshold: dBm
High PER threshold: %
Low Battery threshold: days
3.8 Channel status Check: on-line
Offline/Inactive/OOS/Auto/Manual
Update Rate (sec/min):
3.9 I/O Check: on-line
Type:
Number of Leads (2/3/4/-wire):
Engineering Unit:
Scale Low:
Scale High:
PV 0%: EU
PV 50% EU
PV100% EU
AO 0% mA
AO 50% mA
AO 100% mA
3.10 Process Alarm Check: on-line
PV LoLo: Deadband: Priority:
PV Lo: Deadband: Priority:
PV Hi: Deadband: Priority:
PV HiHi: Deadband: Priority:
3.11 Security Check:
Setup and/or review the Write Protect setting
4. Check the HMI and Faceplate
4.1 Check the existence of the primary associated HMI display. on-line
Call the primary associated HMI display.
Name of the primary associated HMI display:
4.2 Dynamo indication check: on-line
Check the dynamo on the operator interface related to wireless field
device.
Check the dynamo field on the graphic HMI display
Check the alarm coding of dynamo on graphic HMI display
4.3 Faceplate indication check on-line
Check that information on the faceplate matches the wireless
module data detailed in the FDS
Call the faceplate from the related Dynamo element
Check the displayed information of faceplate
• Tagname
• Description
• PV
• PV Scale
• Alarm indication
• Unit name
Rev:. 1.00.00 19/20

R&M Division
NOT
OK
Check the operation with the faceplate
Check the Navigation from the faceplate
• Primary associated HMI display
• Detail display
• Alarm display + alarm acknowledgement function
• Trend display
Detail display check on-line
Call the faceplate and navigate to the related Detail picture
On the Detail picture change the high and low alarm limits and
enable or disable alarms
Module functionality check on-line
Check the module properties and functions according to the FDS
requirements
• Simulate PV and check the actions
• Simulate BAD_PV and check the actions
20/20 Rev.: 1.00.00

MOL Group: Technical Specification Instrumentation

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MOL Group: Technical Specification Instrumentation

Uploaded by

Copyright:

Available Formats

SLOVNAFT a.s.

Requirements for Field-Installed Bus Systems

Rev. Date Description Edited Verified Approved

Release list ................................................................................................................................................................... 2

Rev 1.01.00 3/4

Description Identifier Rev.

4/4 Rev 1.01.00

28. Requirements for Field-Installed Bus Systems

Rev. Date Description Edited Verified Approved

Release list ................................................................................................................................................................... 2

Rev 1.00.00 3/14

1.2 Fieldbus types accepted in MOL Group refineries

2 Requirements of use Foundation fieldbus

4/14 Rev 1.00.00

2.2 Requirements of FFB design

2.2.1 Segment network topology

2.2.2 Provision of segment spares

2.2.3 Scheduling of function block execution cycles

Rev 1.00.00 5/14

2.2.4 Segment reliability

2.2.4.2 MOL Group requirements on methods for risk management

6/14 Rev 1.00.00

2.2.5 Handling of failures

2.2.6 Device diagnostics

2.3 Requirements of FFB hardware

2.3.1 Components of Foundation Fieldbus segments

Rev 1.00.00 7/14

2.3.2 FF cable types

2.3.3 Power, grounding of FF circuits. Lightning protection

8/14 Rev 1.00.00

Class D design is not accepted.

2.3.4 Design and installation of intrinsically safe segments

2.4 Requirements and configuration guidelines of FFB software

2.4.1 Instrument and block identifiers

2.4.2 Control Functionality Location

Rev 1.00.00 9/14

2.4.3 Requirements of control functions

2.4.4 FF functional blocks

2.4.5 Invalid data

2.4.6 Alarms & events

2.4.7 Operator display

2.4.8 Software revisions

2.4.9 System configuration tools

10/14 Rev 1.00.00

2.4.10 Requirements of Link Active Scheduler

2.5 Requirements on master controller (host system)

Rev 1.00.00 11/14

2.6 The most important conditions of the use of an FFB device

2.7 Special and additional requirements in documentation by use of FFB

12/14 Rev 1.00.00

2.8 Factory Acceptance Test and Pre-commissioning checks

2.8.1 Factory Acceptance Test

a. FF-based device test

b. Verification of control strategy

Rev 1.00.00 13/14

Check communication loads of segments.

2.8.2 Checking of Fieldbus loops before pre-commissioning

2.9 Relevant standards and guidelines

14/14 Rev 1.00.00

28. Requirements for Field-Installed Bus System

Rev. Date Description Edited Verified Approved

1.00.00 01.05.2016 Issued SN version Z. Stanová R. Kopálek Head of