Professional Documents
Culture Documents
Distributed Control System: Eni S.p.A
Distributed Control System: Eni S.p.A
FUNCTIONAL SPECIFICATION
20149.EQP.STA.FUN
FOREWORD
TABLE OF CONTENTS
1. GENERAL ..................................................................................................................................4
1.1 Scope .........................................................................................................................................4
1.2 Normative references...............................................................................................................4
2. FUNCTIONAL NORMATIVE REQUIREMENTS .......................................................................7
2.1. Definitions .................................................................................................................................7
2.2. Symbols and abbreviations.....................................................................................................7
2.3. Operative environment ............................................................................................................8
2.4. Functional Requirements ........................................................................................................8
2.5 Limits, exclusions and clarifications ...................................................................................24
2.6 Ergonomics.............................................................................................................................25
2.7 Safety.......................................................................................................................................25
2.8 Non repetitive functional requirements ...............................................................................25
2.9 Requirements for Quality Management and Assurance ....................................................26
2.10. Additional requirement for review ........................................................................................26
2.11 Documentation .......................................................................................................................27
1. GENERAL
1.1 Scope
This specification sets out the minimum requirements for the design, fabrication and
testing of a Distributed Control System for hydrocarbons production and treatment plants.
For all the aspects not covered by this specification, reference is made to the applicable
normative references and to the project technical documentation, and in particular to:
• Technical Data Sheet (T.D.S)
2.1. Definitions
Reference is made to normative references listed in paragraph 1.2 for definitions and
terminology.
Man/machine local interface unit connected to a peripheral unit for processing data
for the visual display of process parameters and plants associated logic.
• Acquisition data remote terminal unit (RTU)
Section of the system monitored by one or more operators’ stations (or operator's
local video terminals) through a data communication line, acting as interface with
the plant and able to execute logic for the local control.
• Front End Processor (FEP)
Intermediate unit able to commute signals and messages between the stations of
the system and stations of external systems.
• Distribuited Control System (DCS)
Section of the system made by hardware and software integration able to operate
autonomously in conformity with the requirements of the system configuration.
• Communication lines
Physical connections among the units of the system for communications and data
exchange.
• Communication protocol
• Seismic effects
• Electromagnetic influences
• Mechanical stresses and vibrations (including violent impacts and harmonic type
vibrations which could occur in the normal operation service)
• Self-diagnostic
• Electric supply
• Marshalling cabinets
All the system, however, shall be designed taking into account the following
characteristics:
• Electromagnetic compatibility with outside interference towards the system and
vice versa
• Modularity and flexibility such to permit the adaptation of the system to restrains
given by the plant and allow its future extension
• High availability through the utilisation of reliable components and stand-by units
for the equipment
• Integration of the automation and safety functions (for a system complete with
ESD "Emergency Shut Down")
• Data Base and application software easily configurable with guided and interactive
procedures
• Operative keyboard
• DVD-RW
When required, the operator's station shall include also a panel or a console, with lamps
and push buttons for the signals and the activation of the emergency sequences, and a
configuration station.
The operator's interface shall be provided at least, in its configuration, with the possibility
to insert an additional operative station and a printer to connect directly to the data line of
the system.
It shall be designed such that a single back-up station shall be able to guarantee the
whole operability of the system for off service or non-operability of the normally operating
one.
From the operator's station it shall be possible to access all the data of the plant suitably
grouped in video pages displayed on a colour monitor.
The system shall be supplied with software suitable for graphic pages construction on
which shall be visualized line, process equipments and relevant instrumentation in
graphic format.
The minimum required information should be the followings:
• Analog variable measure indication
• Alarms pages
In these pages, the display of the alarm state of a variable shall be automatic with an
optical and an acoustical indication.
Suitable summary pages shall be programmed with the indication of the last 10
alarms, in order of occurrence.
The following information shall be displayed for each alarm:
− Day, hour, minutes and seconds of occurrence
− Identification tag of the Data Base point relevant to the alarm signal
− Alarm type
The priority levels and the characteristics needed for their configuration shall be
indicated in the Technical Data Sheet.
• Synoptic pages
They display graphically the process lines and the equipment with the relevant
instrumentation. Each of them shall be organised to display at least:
− Measure value for each analogue variable
These new applications and technologies carry out new traffic type including: voice,
video, storage, interprocess communication, warranted traffic
2.4.2.6 Interface units with the supervision system (Front End Processor communication)
The communication system shall be able to interface with a SCADA System with a
dedicated protocol by means of FEP.
The FEP shall have two independent redundant units having the function of gateway for
supervisory and control functions digital, analog and numeric type (regulator set point).
• Maximum period of time with lack of power, which does not total or partial shut
down of the system cards
The power supply circuits, properly equipped with switches, circuit breakers and fuses to
guarantee the selectivity of the performances and the insulation, shall be provided for all
the components and units of the control system.
The power supply to the most important units, as the operator's station, the control units,
CPU and I/O, shall be backed-up.
• Diagnostic software
• Application software
If not otherwise required, each single software area shall be freely developed, provided
that the achievement of the functional requirements is guaranteed.
• Verify the state of the electronics at the level of each single card and module
• Address failure and malfunctions messages for a clear and univocal identification
of the interested element
In addition, the following software shall be provided:
• On-line diagnostic
This software shall operate continuously on all the parts on-line of the system. It
shall have, as primary objective, the detection of operation anomalies, the
evaluation of their gravity, the transmission of suitable alarm messages to the
operator, and the implementation of suitable actions, as: exclusion of the fault
equipment, commutation on the back-up equipment (if any), re-addressing of the
functions on other peripheral units, etc.
The diagnostic software, in addition to the detection of all the critical failures in the
system, shall configure dedicated messages to be transmitted to the maintenance
remote units.
They shall also configure messages relevant to anomalies, malfunctions and
failure in the monitored plant's equipment (fault signals from power suppliers,
cards, barriers, solenoid valves, etc.).
• Off-line diagnostic
This software is applied to the units off-line from the system and the other
equipment. Its scope is to detect the reasons of the failure or the defect in the sub-
system. A system of diagnostic programmes, which will allow testing all the
components of the system, both one by one and as a complex, shall be provided
for each sub-system. They shall be resident or can be loaded from floppy disk.
• Equipment management
• Command management
• Reports generation
• Filing
The characteristics of these functions are described here below:
b) Control functions
The standard controls shall be the following:
• P, I, D, PI, PID
• PID with advanced control
• Ramp
• On/Off control
• Discrepancy alarms
• Auto/Man control with bias
• Report control
c) Calculation functions
Calculations shall be carried out on analogue and digital points and shall generate
calculated analogue or digital type points.
The analogue calculations shall be carried out with a basic period configurable
independently from the other calculations and from the acquisition period of the
points giving a contribution, which shall be of the analogue acquired, standard and
non standard calculated, types.
• Calculation of the rate as per Codes and standards referred to the project
• Real-time average values on a maximum of 6 contemporaneous measurements
• The 4 arithmetical operations between two measures or between a measure and a
constant value
• Real-time summation of several measures
• Operating period (hours) of a plant's element
• Count of the time period of events for measures, summations and alarms,and on
Hourly/Daily/Weekly/Monthly basis for:
• Average, maximum and minimum value of a measure
• Integral of a measure
• Accumulation in the time of a measure.
d) Alarm Management
When not otherwise required, the management of the alarms shall be organised
as follows:
• Detection of the alarm state
• Management of alarms
• Print of the alarms
• Visual display of the alarms
• Alarms file
The alarms shall be recorded and managed in dedicated data base according to
the following functions:
• Alarm page or logging: area in which the alarms and the manual operation are
chronologically recorded and notified to the operator.
• Historical file: memory area that stored alarm status, events, commands enabled
on visualization (for tag, for type of point, for time base)
• To show five alarm prior categories (ESD, F&G, Critical type, Process normal type,
Diagnostic type) aim to arrange and printing chronological alarms summary.
Management of alarms
The alarm conditions shall be notified to the operators by visual display and print,
as per ISA 18.1.
Alarm filing
It consists in the implementation of a file for alarms acknowledged by the operator,
but still active. This file shall be ordered by time and continuously updated by the
issue or cancellation of the alarm states. It shall be displayed on the monitor of the
operator.
f) Command management
The system shall manage the transmission of instructions towards the field
interface units. These instructions shall be activated from the operative keyboard
or video punters modifying in the Data Base of the system the state corresponding
to the outlet digital signal.
The success of the instruction shall be verified through the control of the final
state.
g) Reports generation
The reports acquire the values from Data Base and historical applications they
shall be based on continuous current data, discrete data, sequential data, and
historical or calculated data. The reports may be printed or developed on request,
or developed by events as an alarm Tag, or developed by daily/weekly/monthly
automatic programmed alarm, or developed as by turn over end, day end week
end predefined time.
h) Filings
The system shall provide a series of filing functions for the acquired points. These
functions shall be essentially of two types:
• Historical type filing
It allows keeping in the system memory, for a defined period, the history of a
certain number of points in the Data Base
• Filing of events
It allows memorising a window of samples for a certain period before and after an
event as, for instance, the intervention of an acquired or calculated digital
b) Operative functions under request by the operator for the management of the plant
• Pages display
A dedicated page with the alarms in a specific area of the plant can be displayed.
The alarms, displayed by date and still active, shall be acknowledged by acting on
a specific push buttons.
The operator can utilise an instruction for the display of alarms already
acknowledged but still active (starting from the memo recent).
• Print-outs
• Video pages
• Files
• Application software
The characteristics, which all the service configurations of the system have in common,
shall be:
− Menu organisation on several levels with data insertion guided and monitored on-
line
− Operative continuity of the system during the phase of data insertion and/or
modification, by acting on a support structure, which shall update the operative
structure of the system only after the data congruence control
− It shall be possible to modify the control software at the level of the single unit,
leaving the interested joint on-line
The peculiar characteristics for each configuration function are described here below:
• Database
The system shall be equipped with on line configurator that allows it to add, to modify,
to erase any point (analog, digital, equipment) acquired, sent and calculated without
the necessity to reload the whole configuration of the system and without impact on
file recording.
It shall be provided control and safety function such to alert the operator in the event
of erasing of point utilized in calculation, display or necessary to determining the
status of the other points.
• Print-outs
The configuration, modification or deletion of all the printouts of the system shall be
feasible. The printouts shall be obtained with programmes written in high-level
language, which allows both to print in different formats the information relevant to the
points of the Data Base (tags, descriptions, value/states, measurement units) and to
refer to the filed data.
• Video pages
The addition, modification or deletion of video pages shall be feasible.
The execution of these operations, totally protected by programming mistakes, shall
not interfere with the on-line functions of the process.
The protection shall be at different level both for the graphic type and the compilation
and animation functions of the graphic pages managed directly from the operator's
station. Interactive graphic procedures shall be utilised for the functions of graphic
and/or semi-graphic configuration.
The operator shall be able to draw, modify and/or delete directly on the monitor the
graphic parts and to abilitate, replace and/or eliminate the existing video pages.
The functions of configuration of the video pages shall make possible the preparation
and updating of:
− Historic file, to memorise on file tapes the history of the Data Base points.
− Event file, to memorise a window of samples in a certain time period before and
after an event (process, acquired or calculated).
• Application software programmes
As application software programmes, are intended those entire specific functions
(calculation or not) necessary to the system to satisfy completely the requirements for
the management of the plant and not provided in the standard calculation section.
In order to answer to these necessities, the system shall manage two different types
of application programmes:
Each of the above functions may be executed with the system still on-line with no
interference with any of the running functions.
For the generic type application programmes, in addition, the configurator shall carry
out congruence controls to verify the exclusion of interference with other programmes
(overlapped records of data, conflictuality, execution priority levels).
The following aspects shall be also taken into account, in function of the characteristics
of the plant to be controlled, defined in the project documents:
2.5.1 Interconnections
Whenever required, the Distributed Control System shall be supplied complete with all
the cables for the interconnections of the interface boards with the electric equipment
and packages, for the transmission of the field signals.
2.6 Ergonomics
The architecture of the system, the assembly and the layout of the equipment shall
reflect the ergonomics criteria and requirements stated in the normative references (ISO
6385) and shall provide to the operators the maximum level of operability and
functionality.
The layout and the interfaces of the equipment (keyboards, printers, monitor and
facilities) shall facilitate the intervention of the operator on the various video stations with
simple movements.
Any signalling and control facility, installed on the front of the boards, shall be positioned
so that the correct identification and operability by the users is guaranteed.
2.7 Safety
All the safety requirements indicated in the Rules and Laws for the prevention of
accidents of the country where the plant is installed shall be applied.
The separation of the conductors in accordance with their typology, as listed here below,
and the different level of voltage shall be taken into account in the implementation of
electric circuits:
• Power and auxiliary a.c. and d.c. supply
• Instruments supply
• To read all the Data Base and write freely in the area allocated to the non-standard
calculated points (analogue and digital)
• To define own areas in the local Data Base to be used as temporary areas for the
calculations
• Mechanical tests
• Electric tests
• Functional tests
• Hardware inspections
• Software review
• Wiring test
• Performance test
When necessary, the execution procedures shall be indicated in the Inspection Data
Sheet (I.D.S.) enclosed to the project specification.
The control system shall pass with positive results the test indicated by the Rules and
listed in the Inspection Data Sheet, and which shall be carried out in conformity wit the
Contractor's procedures, approved and officially accepted by the Company.
2.11 Documentation
• List of the executed inspections and tests, and description of the procedures and
utilised instruments
The final documentation, with the exception of catalogues and publications provided by
the Contractor and sub-Contractors (if any), shall include the following data:
• Name of the Contractor
• Operative instructions
• Maintenance instructions
The inclusion of the description and the drawings in catalogues or publications provided
by the Contractor will be accepted, provided that:
• The catalogues (or publications) shall contain all the data and the requested
information in their final form
• The catalogues (or publications) shall be relevant to the supplied types and the
materials, object of the supply, are clearly identified among those shown in the
document
The documentation submitted to the Company's approval shall be included in the final
documentation, in the revision approved by the Company.