Standard Control System Manual

FLS Automation
Standard Control System Manual
FLS/FLSA STANDARDISATION GROUP
The steering committee members are:
· Bjarne Jørgen Ytting FLS
· Egon Kæreby Pedersen FLS
· Bent Jørgensen FLS
· Søren Eikers FLSA

· Henning Bernberg FLSA
Sand mill
Gear unit
Sand mill
Gear unit Clinker
Silo
Separator
2 3
Cement
Raw meal silo
silo
5 Cement mill
3 4 Gear unit
1 2
Raw mill

04-Apr-2002 Version 01 – Revision 00 page 1 of 63
FLS Automation
Table of Contents
1. INTRODUCTION...................................................................................................................................... 4
1. DESCRIPTION OF PHASES FOR A TYPICAL PROJECT ............................................................... 5

1.1.1 ....................................................................................................................................................... 5
1.1.2 Signing of contract......................................................................................................................... 5
1.1.3 Start-up meeting............................................................................................................................. 5
1.1.3.1.1 Basic principles for data communication ...................................................................................... 5
1.1.3.1.2 Data communication matrix .......................................................................................................... 5
1.1.4 PLC-freeze..................................................................................................................................... 6
1.1.5 Preliminary I/O list ........................................................................................................................ 6
1.1.6 Finalise design freeze date ............................................................................................................. 6
1.1.7 Design basis freeze (I/O and interlock freeze) ............................................................................... 6
1.1.7.1 I/O freeze............................................................................................................................................. 6
1.1.7.2 Interlock freeze.................................................................................................................................... 7
1.1.7.3 Data communication for sub-systems.................................................................................................. 7
1.1.8 FAT................................................................................................................................................ 7
2. DIVISION OF DEPARTMENTS AND GROUPS .................................................................................. 8
3. FLS / FLSA MODULES............................................................................................................................ 9
4. SUB-SYSTEMS........................................................................................................................................ 10
4.1 EXAMPLE OF LOCAL CONTROL PLC NODES, ON PROFIBUS ................................................................ 10
4.2 EXAMPLE OF COMMUNICATION LAYOUT FOR SIEMENS S7.................................................................. 11
4.3 PROGRAM EXAMPLE .......................................................................................................................... 14
4.4 GENERAL FOR CONTROLLOGIX AND SLC 5/04.................................................................................. 15
4.5 COMMUNICATION LAYOUT ................................................................................................................ 15
4.6 DATA FILES........................................................................................................................................ 15
4.7 NODE DEFINITIONS AND MEMORY LAYOUT ........................................................................................ 15
4.8 PRINCIPLE OF RECEIVING DATA .......................................................................................................... 16
4.9 PRINCIPLE OF SENDING DATA ............................................................................................................. 16
4.10 WATCHDOG FUNCTION ...................................................................................................................... 16
4.11 GENERAL PLC FAULT ........................................................................................................................ 16
4.12 SUB PLC PROGRAM........................................................................................................................... 17
4.13 DATA SHEET SUB PLC TO MAIN PLC ............................................................................................... 19
4.14 DATA SHEET MAIN PLC TO SUB PLC ............................................................................................... 20
5. ECS / SDR................................................................................................................................................. 21
5.1 DEPARTMENT COMMANDS ................................................................................................................. 21
5.1.1 Emergency stop............................................................................................................................ 22
5.2 ALARM PHILOSOPHY .......................................................................................................................... 22
5.2.1 Alarms on analog signals ............................................................................................................. 22
5.2.2 Alarms on digital signals.............................................................................................................. 23
5.3 MIMIC COLOURS ................................................................................................................................ 24
5.4 MIMIC LAYOUT, TYPICAL................................................................................................................... 25
6. PLC AND I/O CABINET LAYOUT ...................................................................................................... 27
6.1 STANDARD CABINET LAYOUT “ACEDOC” ....................................................................................... 27
6.1.1 Cabinets ....................................................................................................................................... 27
6.1.2 General layout.............................................................................................................................. 27
6.1.3 Three basic cabinet layouts:......................................................................................................... 27
6.1.4 Terminal block marking:.............................................................................................................. 28
6.1.5 Emergency Stop/Plant Stop: ........................................................................................................ 29
6.1.6 Incoming cable fixation: .............................................................................................................. 29
6.1.7 Miscellaneous: ............................................................................................................................. 30
6.2 TERMINAL BLOCK ASSIGNMENT ......................................................................................................... 39

FLS Automation
6.3 FLS DESCRIPTION OF TERMINAL LAYOUT .......................................................................................... 49
7. FA TEST PROCEDURE......................................................................................................................... 50
7.1 WIRING CHECK .................................................................................................................................. 50
7.2 WIRING INSULATION TEST .................................................................................................................. 50
7.3 VISUAL INSPECTION .......................................................................................................................... 50
7.3.1 Checklist ...................................................................................................................................... 50
7.3.2 Punch List .................................................................................................................................... 50
7.4 PREPARATION FOR TEST..................................................................................................................... 50
7.5 SYSTEM FUNCTIONAL TEST ............................................................................................................... 51
7.5.1 Hardware Test.............................................................................................................................. 51
7.5.1.1 Visual Inspection by FLS.................................................................................................................. 51
7.5.1.2 I/O Test ............................................................................................................................................. 51
7.5.1.3 Operator Stations............................................................................................................................... 51
7.5.2 Operator Stations - User Interface ............................................................................................... 51
7.5.2.1 Mimics are verified for:..................................................................................................................... 51
7.5.2.2 Printing facilities are verified for: ..................................................................................................... 51
7.5.2.3 Alarms are checked for:..................................................................................................................... 51
7.5.3 Other Tests................................................................................................................................... 52
7.5.3.1 Autonomous systems.......................................................................................................................... 52
7.5.4 Functional Test ............................................................................................................................ 52
7.5.4.1 Programme functional test................................................................................................................. 52
7.5.4.2 Programme functional test, Alarms ................................................................................................... 52
7.5.4.3 Network............................................................................................................................................. 52
7.5.5 Software simulation of I/Os ......................................................................................................... 52
7.5.6 Test Documents ........................................................................................................................... 52
7.5.7 Checklists..................................................................................................................................... 53
7.5.7.1 Hardware Checklist ........................................................................................................................... 53
7.5.7.2 System Checklist ............................................................................................................................... 53
8. DATA EXCHANGE BETWEEN FLS AND FLSA .............................................................................. 56
8.1 DIVISION OF RESPONSIBILITY FOR DATA EXCHANGE ........................................................................... 56
8.1.1 Model 1........................................................................................................................................ 56
8.1.2 Model 2........................................................................................................................................ 56
8.1.3 Model 3........................................................................................................................................ 57
8.2 EDOC DATA EXCHANGE WITH SMARTTOOLS .................................................................................... 58
8.2.1 Import .......................................................................................................................................... 58
8.2.2 EdocSiIO ..................................................................................................................................... 58
8.2.3 EdocXTIO ................................................................................................................................... 59
8.3 EXPORT ............................................................................................................................................. 59
8.3.1 EdocSiIO ..................................................................................................................................... 59
8.3.2 EdocSig........................................................................................................................................ 60
8.3.3 EdocSiTe ..................................................................................................................................... 60
9. SUPPLY OF FLSA DOCUMENTATION TO FLS.............................................................................. 62
9.1 DEFINITIONS ...................................................................................................................................... 62
9.2 SUPPLY OF “A” DOCUMENTATION TO FLS......................................................................................... 62
9.3 SUPPLY OF DOCUMENTATION "B" TO FLS ......................................................................................... 63

FLS Automation
1. Introduction
It has been decided that a general design manual for process control systems should
be written. The general design manual should be a thorough detailed basis for the
project manuals written by FLSA, in co-operation with FLS in connection with
new projects. Hereby, it should not be necessary to discuss general control
principals when starting a new project. The project manual forms the basis of all
project work with FLSA. Therefore, the manual should be the first step in any
project co-operation.
Unless there are contractual specific requirements differing from the general
design manual, the general design manual is to be used as basis for the project
manual.
A work group and a managing group should co-operate, update and maintain the
design manual.

FLS Automation
1. Description of phases for a typical project
1.1.1
Time schedule for a typical project w = working weeks

0 w1 w5 w7 w8 w 14 w 30 w 34 w 37
Signing of Start-up PLC-freeze Preliminary Finalise design Design basic Shipping

FAT Packing
contract meeting I/O-list freeze date freeze
1.1.2 Signing of contract

Before signing the contract a detailed scope of supply is defined with number of I/O’s,
number of controlled units, number of PLC’s, number of operator stations, servers,
printers, network system etc. and a total price has been agreed upon.
An overall time schedule for the project has been agreed upon. (If a split of the freezing
dates is possible, the number of possible splits are defined in the overall time schedule).
Variations (changes) are handled according to the FLS/FLSA general agreement for
control systems.
1.1.3 Start-up meeting

Before starting any design a start-up meeting is held. At this meeting a detailed time
schedule for the project is discussed and agreed upon. Similar the division of
departments is agreed upon at this start up meeting.
The basic design criteria are discussed and agreed upon. (Special client requirements are
clarified, any deviation from the FLSA-standard panel layout is clarified, interface to
local control systems, exact edition of FLS Key to Interlock to be used in the project is
agreed upon, etc).
1.1.3.1.1 Basic principles for data communication

The basic principles for the data communication to the sub-systems are agreed upon,
node numbers for each sub-system is selected by FLSA. The dates for forwarding and
returning data communication sheets from the suppliers of the sub-systems are agreed
upon.
1.1.3.1.2 Data communication matrix

A data communication matrix in digital format including a user instruction is prepared
by FLSA; FLS forwards a copy to each supplier of sub-systems.

FLS Automation
1.1.4 PLC-freeze
The number of PLC-panels is agreed upon based on a preliminary I/O list and the
number of PLC’s for each department are frozen.
As each PLC basically contains only the central rack with CPU-unit, communication
module, power supply and if space available, some analogue I/O’s, FLSA can start
design and purchase of the PLC-panels after the PLC-freeze date. FLS will inform
FLSA about numbers of standard terminal blocks (analog blocks) required in each of the
PLC-panels.
1.1.5 Preliminary I/O list

A preliminary I/O list in digital format for one department is forwarded to FLSA. After
receiving the preliminary I/O list FLSA checks the readability of the list.
A revised edition of the preliminary I/O list in digital format with PLC-addresses, etc. is
returned to FLS, after receiving the revised edition FLS will check the readability of the
list.
The purpose of this exercise is to check the conformity in the data formats used by FLS
and FLSA.
1.1.6 Finalise design freeze date

A meeting is held to confirm/or correct the planned dates for design basis freeze, FAT-
test and shipping. This meeting should be held at least 6 weeks before the planed Design
basis freeze date.
1.1.7 Design basis freeze (I/O and interlock freeze)
1.1.7.1 I/O freeze

The number and types of standard terminal blocks for each department are
agreed upon (motors, dampers, valves, field instruments, etc,).
If agreed in the start up meeting the I/O freeze could be split into 2 or 3 freeze-
dates, each covering a number of departments.
FLSA can start design and purchase of the I/O-panels after the I/O-freeze date
based on the signal lists that are nearly final. The numbers of actual I/O’s are
compared to the contractual number of I/O’s and a deviation list is made for the
plus/minus account.
Changes caused by FLS after the I/O freeze will delay the design and
manufacture of the I/O-panels. Changes will be priced according to agreed Unit
price for I/O-changes after I/O freeze as defined in the FLS/FLSA general
agreement for control systems, (variations).

FLS Automation
1.1.7.2 Interlock freeze

The final interlock diagrams, signal lists and flow sheets for each department are
handed over to FLSA.
If agreed at the start-up meeting the interlock freeze could be split into 2 or 3
freeze-dates, each covering a number of departments.
Changes caused by FLS after the interlock freeze will delay the programming.
Changes will be priced according to agreed Unit price for Interlock-changes
after interlock- freeze as defined in the FLS/FLSA general agreement for control
systems (variations).
1.1.7.3 Data communication for sub-systems
All suppliers of sub-systems have returned a digital copy of the data

communication matrix for each sub-system to FLSA filled in with the data as
indicated in the user instruction.
Changes caused by FLS after the interlock freeze will delay the programming,
changes will be priced according to agreed Unit price for I/O-changes after
interlock- freeze as defined in the FLS/FLSA general agreement for control
systems (variations).
1.1.8 FAT
The purpose of the Factory Acceptance Test is that FLSA shall demonstrate to FLS that
the PLC-program acts as described in the FLS-interlock diagrams. Before starting the
FAT-test FLSA states that the total system is completed according to the FLS interlock
diagrams.
Further the FAT-test gives FLS the possibility to check the overall function of the FLS-
interlocking.

FLS Automation
2. Division of departments and groups

Considering the operators later use of the system, it is very important that the ECS
departments are placed appropriately. Most likely the PLC programmer and the operator
will have different perceptions as to the term department. Below examples of division
are given:
1. A raw mill with two mills will physical typically be placed in two PLC’s.
PLC 1 with joint raw material transport to both mills and mill no. 1.
PLC 2 with joint transportation of manufactured goods to silo from both mills
and mill no. 2.
The above mentioned should logically be divided as follows:
ECS department 1. Raw material transportation to mills.

ECS department 2. Raw mill 1.
ECS department 3. Raw mill 2.
ECS department 4. Joint transportation to silo.
2. Many plants have a PLC, which deals with various equipment such as plant air
and water treatment. If parts of the equipment logically belong to another
department, such as rotary blowers to airlifts for kiln feeding, the rotary blowers
should be controlled from the same department as the rest of the kiln feeding.
There should be no doubt that a start in one ECS department must not under any
circumstances start a group in any other ECS department than the one selected,
all though a group may have been selected in another ECS department.
It is of great importance that the above mentioned is observed from the
beginning, as it is almost impossible to change once installed. Therefore there
should be an agreement between those involved on this issue as early in the
process as possible.

FLS Automation
3. FLS / FLSA modules

During the start-up meeting the basic design criteria are discussed and agreed upon.
Exact edition of,
- Key to Interlockings, version x

- E-Doc,version x
- FLSA – ACESYS, version x
- Interlocking Diagrams / SmartInterlockings, version x
- Type of I/O lists
to be used in the project is agreed upon.
Responsible for the FLS / FLSA modules:
· Ole Bak FLS
· Bent Ljungmann Petersen FLS
· Finn Kousgaard Poulsen FLSA

· Poul Nielsen FLSA

FLS Automation
4. Sub-Systems
4.1 Example of Local control PLC nodes, on Profibus
PLC REF DESIGNATION NODE I/O COMMENTS

LOCAL
PLC
INPUT OUTPUT
531CS001 CEMENT MILL 1
Spare 11
531LQ100A01 Mill lubrication 12 I96-I127 Q96-Q127
531WF010A01 Dosax feed Clinker 13 I96-I127 Q96-Q127
531WF020A01 Dosax feed Gypsum 14 I96-I127 Q96-Q127
531WF030A01 Dosax feed Additive 15 I96-I127 Q96-Q127
532CS001 CEMENT MILL 2

Spare 11
532LQ100A01 Mill lubrication 12 I96-I127 Q96-Q127
481WF060A01 Bad clinker 13 I96-I127 Q96-Q127
532WF010A01 Dosax feed Clinker 14 I96-I127 Q96-Q127
532WF020A01 Dosax feed Gypsum 15 I96-I127 Q96-Q127
532WF030A01 Dosax feed Additive 16 I96-I127 Q96-Q127

FLS Automation
4.2 Example of communication layout for Siemens S7
Input
Handshake constant "1" send from Bridge PLC please check program example
I 96.0 FC100
I 96.1 Start status bits
I 101.7 End status bits
I 102.0 IW 102 Start status word
I 127.7 IW 126 End status word

Output
Handshake constant "1" send to Bridge PLC set bit "1" after each cycle, please
Q 96.0 check program example FC100
Q 96.1 Power supply fault
Q 96.2 I/0 rack fault Start digital outputs
Q 96.3 Spare fault
Q 96.4 Spare fault
Q 96.5 Start status bit
Q 101.7 End command bits
Q 102.0 QW 102 Start command word
Q 127.7 QW 126 End command word

FLS Automation
Datalayout between Bridge PLC and DP slave PLC

Plant: MISR Cement Co. (Qena)
Data from Bridge PLC
I/Q Receive No.
I 96.0 1 Handshake constant "1" from Bridge PLC please check program example
I 96.1 2 Start databits from Bridge PLC
I 96.2 3
I 96.3 4
I 96.4 5
I 96.5 6
I 96.6 7
I 96.7 8
I 97.0 9
I 97.1 10
I 97.2 11
I 97.3 12
I 97.4 13
I 97.5 14
I 97.6 15
I 97.7 16
I 98.0 17
I 98.1 18
I 98.2 19
I 98.3 20
I 98.4 21
I 98.5 22
I 98.6 23
I 98.7 24
I 99.0 25
I 99.1 26
I 99.2 27
I 99.3 28
I 99.4 29
I 99.5 30
I 99.6 31
I 99.7 32
I 100.0 33
I 100.1 34
I 100.2 35
I 100.3 36
I 100.4 37
I 100.5 38
I 100.6 39
I 100.7 40
I 101.0 41
I 101.1 42
I 101.2 43
I 101.3 44
I 101.4 45
I 101.5 46
I 101.6 47
I 101.7 48 End
IW 102 1 Start Datawords from Bridge PLC
IW 104 2
IW 106 3
IW 108 4
IW 110 5
IW 112 6
IW 114 7
IW 116 8
IW 118 9
IW 120 10
IW 122 11
IW 124 12

FLS Automation
Data to Bridge PLC
I/Q Send No.

Q 96.0 1 Handshake constant "1" send from Bridge PLC please check program example
Q 96.1 2 Power supply fault
Q 96.2 3 Loss of Rack fault
Q 96.3 4 Spare fault
Q 96.4 5 Spare fault
Q 96.5 6 Start Databits to Bridge PLC
Q 96.6 7
Q 96.7 8
Q 97.0 9
Q 97.1 10
Q 97.2 11
Q 97.3 12
Q 97.4 13
Q 97.5 14
Q 97.6 15
Q 97.7 16
Q 98.0 17
Q 98.1 18
Q 98.2 19
Q 98.3 20
Q 98.4 21
Q 98.5 22
Q 98.6 23
Q 98.7 24
Q 99.0 25
Q 99.1 26
Q 99.2 27
Q 99.3 28
Q 99.4 29
Q 99.5 30
Q 99.6 31
Q 99.7 32
Q 100.0 33
Q 100.1 34
Q 100.2 35
Q 100.3 36
Q 100.4 37
Q 100.5 38
Q 100.6 39
Q 100.7 40
Q 101.0 41
Q 101.1 42
Q 101.2 43
Q 101.3 44
Q 101.4 45
Q 101.5 46
Q 101.6 47
Q 101.7 48 End
QW 102 1 Start Datawords to Bridge PLC
QW 104 2
QW 106 3
QW 108 4
QW 110 5
QW 112 6
QW 114 7
QW 116 8
QW 118 9
QW 120 10
QW 122 11
QW 124 12
QW 126 13 End

FLS Automation
4.3 Program Example

In order to check the DP communication, Power and Rack fault, FLS-Automation offers
FC 100 and OB 81 and OB 86 check Project example Qena_Sub_PLCX
FC100 DP communication OK

FLS Automation
4.4 General for ControlLogix and SLC 5/04
This manual contains information about communication between FLSA main PLC’s and
Sub-PLC’s from other suppliers, using Data Highway network (DH+). Main PLC’s are
Allen Bradley type ControlLogix, and Sub-PLC’s are Allen Bradley type SLC 5/04.
4.5 Communication Layout
For each Sub-PLC 10 integer words are allocated for receiving data and 10 words for
sending data. The first two words in each block are predefined for sending digital
information (32 bits), followed by eight integer variables for analog information.
4.6 Data files

For the communication purpose 4 integer files are defined:
N211 = Receiving data

N212 = Copy of received data (Work data)
N213 = Sending data (Work data)
N214 = Copy of send data
Main PLC Sub PLC

N214:x - N213:x - ® N211:000 - N212:000 -
N214:(x+9) N213:(x+9) N211:009 N212:009
N212:x - N211:x - ¬ N213:000 - N214:000 -
N212:(x+9) N211:(x+9) N213:009 N214:009
x = Sub PLC no. * 10
4.7 Node definitions and memory layout

The layout is allocated for 15 Sub-PLC’s with the following DH+ addresses and memory
layout.
PLC DH + Address Main PLC

destination
Main PLC 10 (decimal) / 12 (octal)
Sub PLC #1 11 (decimal) / 13 (octal) N211:010-019
… … …

FLS Automation
4.8 Principle of receiving data

Data from the Main PLC will be received in memory area N211:000-009. The received
data are copied to N212:000-009, which is the working area in the Sub-PLC. If data are
not received within 30 seconds, the working area (N212:000-009) will be cleared (see
section 4.10 Watchdog function).
4.9 Principle of sending data

Data to be transmitted from the Sub PLC to the Main PLC are stored in N213:000-009.
When data are send a copy is made to the memory area N214:000-009.
The request for sending data is trigged by any change in the digital data (the two first word
in the data block). If the data in N213:000/N214:000 or N213:001/N214:001 are not equal,
a transfer is executed. If the data have not been sent within 5 seconds trigged by change in
the digital data bits, the data are send anyway to insure that the analog signal are transferred
at least every 5 seconds.
4.10 Watchdog function

The first bit in the data block received from the main PLC is a watchdog bit, and will
always be low. The Sub PLC will force the bit high. If the watchdog bit has been high for
30 seconds (meaning that no data have been received from the main PLC), the data area
containing the data from the Main PLC will be cleared (set to 0).
The first bit in the data block from the Sub PLC to the Main PLC is also allocated for
watchdog function. The only thing to be done in the Sub PLC is to insure that the bit is
constant low.
4.11 General PLC fault

The second bit in the data block sent from the Sub PLC to the Main PLC must contain
relevant PLC fault (battery fault etc.). This bit will be used to animate a digital alarm on the
MMI.

FLS Automation
4.12 Sub PLC program

FLS Automation

FLS Automation
4.13 Data sheet Sub PLC to Main PLC
Plant TamDiep
Comm. direction Sub PLC ® Main PLC Date
Sub PLC no. xx Decimal / xx Octal Rev.
Sub PLC Ref. Init.
Sub PLC Name
Address Tagcode Description
N213:000/00 Watchdog bit (constant low)
N213:000/01 General PLC fault (1=OK)
N213:000/02
N213:000/03
N213:000/04
N213:000/05
N213:000/06
N213:000/07
N213:000/08
N213:000/09
N213:000/10
N213:000/11
N213:000/12
N213:000/13
N213:000/14
N213:000/15
N213:001/00
N213:001/01
N213:001/02
N213:001/03
N213:001/04
N213:001/05
N213:001/06
N213:001/07
N213:001/08
N213:001/09
N213:001/10
N213:001/11
N213:001/12
N213:001/13
N213:001/14
N213:001/15
N213:002
N213:003
N213:004
N213:005
N213:006
N213:007
N213:008
N213:009

FLS Automation
4.14 Data sheet Main PLC to Sub PLC
Plant TamDiep
Comm. direction Main PLC ® Sub PLC Date
Sub PLC no. xx Decimal / xx Octal Rev.
Sub PLC Ref. Init.
Sub PLC Name
Address Tagcode Description
N211:000/00 Watchdog bit (constant low)
N211:000/01
N211:000/02
N211:000/03
N211:000/04
N211:000/05
N211:000/06
N211:000/07
N211:000/08
N211:000/09
N211:000/10
N211:000/11
N211:000/12
N211:000/13
N211:000/14
N211:000/15
N211:001/00
N211:001/01
N211:001/02
N211:001/03
N211:001/04
N211:001/05
N211:001/06
N211:001/07
N211:001/08
N211:001/09
N211:001/10
N211:001/11
N211:001/12
N211:001/13
N211:001/14
N211:001/15
N211:002
N211:003
N211:004
N211:005
N211:006
N211:007
N211:008

FLS Automation
5. ECS / SDR
Manuals for FLS Automation products are to be found at:
http://www.flsadev.dk
Username: FLSmidth
Password:
5.1 Department commands
The following commands are all issued from the common task bar shown on top of each
screen on the ECS-Opstation and is only logical “1” in one PLC cycle.
Department Select (of highlighted group, from task bar)

Select a highlighted Group can result in two different statuses either “Interlocked” or
“Accepted”.
Interlocked means that a group or start interlocking is not fulfilled, and “Accepted” means
the Group is ready to start.
If the Group shows “Interlocked”, which means that a group or start interlock or group
interlock is not fulfilled, then the operator can get the information of the reason by clicking
on the small interlock icons underneath the Group status field for further information.
Department Start Command

If a Group is “Accepted” the drives associated to the Group will get a start command.
Department Stop Command

If a running Group is “Selected to stop” the drives associated to the Group will get a stop
command, when clicking on the “Stop” icon.

FLS Automation
Department Quick Stop Command

If a Group is “Selected to stop” the drives associated to the Group will get a stop command,
when clicking on the “ Quick Stop” icon.
The drives will stop immediately with disabled “Delayed stop timers” and leave the motors
in “Stopped”.
Department Master Stop

If a running Group gets a “Master stop”, then all the drives that are running will get a stop
command, but leave the Group and motors, after they are stopped, in “Auto selected”. Then
if the operator wants to start again from the situation he had before, he simply presses the
start icon and the department will come up running as before the shut down.
Department Alarm Silence

Alarm Silence makes the alarm beep on the computer silence and changes the flash red
symbol on the ECS-system into steady red.
The alarm symbol remains red even if the alarm disappears, one has to make an alarm reset
before the alarm symbol can change from red to normal colour.
Department Alarm Reset

Alarm Reset makes the alarm disappear, when the fault has been corrected.
Alarm reset is only operational after an Alarm Silence.
5.1.1 Emergency stop

When emergency stop, Hardwired, is activated from the CCR, the voltage from all
digital outputs is cut off in the individual PLC department.
Stop function category 1, safety category B.
5.2 Alarm philosophy
5.2.1 Alarms on analog signals
Limit value monitoring.

The module monitors the measured value for over range and underflow, and for up to four
alarm limits:
High High
High
Low
Low Low
As soon as there is an over range or an underflow, an alarm message is generated. The

message can be released or blocked separately for each limit value.
If one of the above limit values is exceeded, then the module generates an alarm
message and sets the corresponding module flag.

FLS Automation
5.2.2 Alarms on digital signals.
MMI Presentation:
The following symbols are a part of the FLSA standard library for use with digital
alarms.
The above shown symbols are changing colour according to status of the process. These
symbols are used on the process flow pictures clicking with the right hand mouse on the
text or symbol will bring up a faceplate for the alarm e.g.:
Pre-warning (High 1, Low 1) is generated in the PLC system.

High 1, Low 1 are always a pre-warning.
Alarm (High 2, Low 2) is generated in the PLC system.

High 2, Low 2 are always alarms.

FLS Automation
5.3 Mimic colours
Static colours
Oil/Gas flow Orange

Water flow Light blue
Material flow Blue
Static symbols Shade of Grey
Text Beige
Background Black/Blue
Dynamic status colours:
FLS Standard Terms FLS standard Colours:

Text FLS
STOPPED STOPPED Brown
SELECTED (for start) SELECTED Yellow
START ACKN. AUTO START Olive Brown/Green
RUNNING RUNNING Green
GROUP SELECTED FOR STOP STOP SELECTED Green-flash
GROUP IN STOP MODE STOPPING Light Green
NOT READY (not ACKN.) NOT READY Red-flash
NOT READY (ACKN.) NOT READY Red
MCC FAULT (not ACKN.) MCC FAULT Red-flash
MCC FAULT (ACKN.) MCC FAULT Red
RETURN FAULT (not ACK.) RET. FAULT Red-flash
RETURN FAULT (ACK.) RET. FAULT Red
FAULT (not ACKN.) FAULT Red-flash
ACKNOWLEDGED FAULT FAULT Red
LOCAL (not RUNNING) LOCAL STOP White
LOCAL RUN LOCAL RUN White-flash
SAFETY INTERLOCK SAFETY Rosa
DYNAMICLY NOT UPDATED NOT UPDATED Purple
Colour coding.

FLS Automation
5.4 Mimic layout, typical.

FLS Automation

FLS Automation
6. PLC and I/O cabinet layout

6.1 Standard cabinet layout “ACEDOC”
The FLS/FLSA Standardisation Group has outlined following standard on cabinet layout:
6.1.1 Cabinets
All cabinets will be of the same size, 2100x1200x500 mm (HxWxL), where H includes
a 100 mm base frame.
1) Make: Rittal
2) Type: TS8205
3) Colour: RAL 7032. Base frame: RAL 7022.
4) Each cabinet will be supplied with side covers.
5) Cabinet will be supplied with Rittal’s standard handle/lock, unless otherwise
specified.
6.1.2 General layout

1) The upper part of the mounting plate is reserved for the I/O hardware, power
supplies etc.
2) Below the hardware, auxiliary terminals and other devices for power distribution
will be located.
3) The lower part of the mounting plate is reserved for terminal blocks to where field
connections are made.
4) Side mounting plates are used for emergency stop blocks, incoming power block and
bus patch boxes.
6.1.3 Three basic cabinet layouts:

1) One cabinet with 10 analog blocks (X5).
a. 10 X5 blocks is the maximum for one cabinet.
b. The X5 block is for analogue signals, 16 AI and 4 AO.
c. The block X5.0 is predefined for power distribution to the X5 blocks.
2) One cabinet with 10 digital blocks (X6).
a. 10 X6 blocks is the maximum for one cabinet.
b. The X6 block is for digital signals, 16 DI and 8 DO.

FLS Automation
c. The X6 block has a version for DC supply and a version for AC supply.
d. The block X6.0 is predefined for power distribution to the other X6
blocks.
3) One cabinet with 4 unit/motor blocks (X7).
a. 4 X7 blocks are the maximum for one cabinet.
b. The X7 block is for unit/motor control.
One X7 block is designed to handle 16 motors; i.e. maximum 64 motors
in same cabinet.
c. The block X7.0 is predefined for power distribution to the other X7
blocks.
d. The X7 block has 4 versions:
1 DO and 3 DI with DC supply.
1 DO and 3 DI with AC supply.
1 DO and 4-5 DI with DC supply.
1 DO and 4 to 5 DI with AC supply.
Combination of X5, X6 & X7 blocks can be made in the same cabinet for minor process
departments.
The blocks X0, X1, X2 & X3 are dedicated for internal power distribution.
6.1.4 Terminal block marking:

Example for X5
X5.xx:n z where X5 is the terminal block type (analog)
where xx is the terminal block number (01…10)
where n is the signal terminal number (1…16 for analog
input; 17…24 for analog output)
where z is terminal extension (+/- for dc voltage and FE
for functional earth connection)
(Refer to Appendix A, -X5.x)
Example for X6
X6.xx:n z where X6 is the terminal block type (digital)
where xx is the terminal block number (01…10)
where n is the signal terminal number (1…16 for digital
input; 17…24 for digital output)
where z is terminal extension (+/- for dc voltage, L/N for

FLS Automation
ac voltage and FE for functional earth connection)

(Refer to Appendix A, -X6.x).
Example for X7
X7.xx.yy:n where X7 is the terminal block type (unit/motor)
where xx is the terminal block number (01…04);
where yy is the unit/motor terminal block section
(01…16);
where n is the signal terminal number (+ -, 1…4 for 3
digital inputs, 1 digital output, dc voltage);
where n is the signal terminal number (+ -, 1…6 for 5
digital inputs, 1 digital output dc voltage);
where n is the signal terminal number (L N, 1…4 for 3
digital inputs, 1 digital output ac voltage);
where n is the signal terminal number (L N, 1…6 for 5
digital inputs, 1 digital output ac voltage);
(Refer to Appendix B, -X7.x).
6.1.5 Emergency Stop/Plant Stop:

1) The X4 block is used for emergency stop control and supervision.
2) The block has input for 8 field emergency stops, 2 channels for remote cabinets with
emergency stop inputs, and outputs for 8 emergency stop commands to cabinets
without emergency stop inputs.
3) X4 blocks can be linked together in groups of 8 if more inputs and outputs are needed.
All field inputs and remote channels are supervised with a separate contact function
connected to the last slot in the I/O rack. This last input card (DI) is only used for
emergency stop supervision, and internal cabinet supervisions.
4) For sub-cabinets, terminal block type 4.9 will be installed.
6.1.6 Incoming cable fixation:

1) For cabling to X5: 10 multicable clamps mounted on a single rail near cabinet
bottom.
2) For cabling to X6: 10 multicable clamps mounted on a single rail near cabinet
bottom.
3) For cabling to X7: 64 multicable clamps mounted on a double rail near cabinet
bottom.

FLS Automation
6.1.7 Miscellaneous:
1) Cabinet lighting can be installed.
Basic installation, i.e. circuit breaker, terminals and wiring will always be prepared.

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation
Standard panel layout with Allen Bradley CLX PLC.

FLS Automation
6.2 Terminal block assignment
Wiring is divided into the following blocks:
X0 Incoming power supply and supply to the next cabinet.

X1 Distribution of AC power supply.
X2 Distribution of DC power supply to control circuits.
X3 Distribution of AC power supply to control circuits.
X4.x Emergency stop circuits.
Terminal 1 - 8 are used for field connection of emergency stop push buttons.
Wires are connected at top and middle level.
Terminal 11 & 12 are used for field connection from next cabinet emergency
stop push buttons. Wires are connected at top and middle level.
Terminal 20 is used for connection from next X4 block emergency stop push
buttons. Wires are connected at top and middle level.
Terminal 21 & 22 are used for field connection to next cabinet emergency stop
orders. The 2 terminals are preferred for cabinets with push buttons, but can also
be used for auxiliary cabinets. Wires are connected at top and bottom level.
Terminal 23 - 29 are used for field connection to auxiliary cabinet emergency
stop orders. Wires are connected at top and bottom level.
Terminal 30 is used for connection to next X4 block emergency stop order.
Wires are connected at top and middle level. If no next X4 block is needed, the
terminal can be used for field connection to auxiliary cabinet emergency stop
order.
Terminal 31 & 32 are in remote cabinets/next X4 blocks, used for field/internal
connection of collected push buttons to previous cabinet/block. Wires are
connected at top and bottom level.
Terminal 33 & 34 are in remote cabinets/next X4 blocks, used for field/internal
connection of common stop order from previous cabinet/block . Wires are
connected at top and bottom level.
Terminal 35 & 36 are used for field connection from next cabinet OLM/Surge
supervision. Wires are connected at top and bottom level.
Terminal 37 & 38 are only used on X4.9 blocks.
Terminal 39 – 58 are used for internal connection of the emergency stop
circuits.
X4.9 Emergency stop circuits.
Terminal 21 is used for field connection to next cabinet emergency stop orders.
Wires are connected at top and bottom level.

FLS Automation
Terminal 33 & 34 are used for field connection of common stop order from
previous cabinet. Wires are connected at top and bottom level.
Terminal 35 & 36 are used for field connection from next cabinet OLM/Surge
Terminal 37 & 38 are used for field connection to previous cabinet OLM/Surge
Terminal 39 – 42 are used for internal connection of the emergency stop
circuits.
X5.0 Power distribution to X5 blocks.

X5.x Analogue signal distribution, each block with 16 inputs and 4 outputs.
Terminal 0 and 31…34 are used for internal wiring.
X6.x Digital signal distribution, each block with 16 inputs and 8 outputs.
Terminal 0 and 31…34 are used for internal wiring.
X7.x Unit signals distribution, each block with 16 units.
Unit .00 is used for internal wiring.
X20 24VDC supply distribution to OLM.
Emergency stop X4.x

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation

FLS Automation
6.3 FLS description of terminal layout
Terminal block type X7 (unit/motor) standard connection:
Example.: Motor block 01, motor 03:
X7.01.03.+ + (Supply for digital inputs: Ready, local start, return etc.)
X7.01.03.- - (0 ref. for digital output: Command)
X7.01.03.1 C31 (Command)
X7.01.03.2 C41 (Unit/Motor Ready)
X7.01.03.3 C51 (Local start)
X7.01.03.4 C61 (Return)
If interface with 4 or 5 inputs is used, the following may be:
X7.01.03.5 C71 (Overload)

X7.01.03.6 C81 (Test Position)
Other signal combinations/descriptions may occur, but connection will be as above with
the Command (digital output) on terminal .1, and the inputs in logical order (alphabetic).
If a reversible motor starter is connected it will occupy 2 motor terminal blocks,

meaning that direction 1- and common signals will be connected to the first motor
terminal block, and direction 2 signals to the following.
Example:
X7.01.04.1 C32 (Command 2)

X7.01.04.3 C52 (Local Start 2)
X7.01.04.4 C62 (Return 2)
Special applications with limit/torque switches may require the use of 3 consecutive
motor terminal blocks.
Units typically interfaced with X7 are: Motors, Dampers (reversible motor starter), EP-
filters (rectifiers and rapping) etc.
Units, which include motor driven parts typically interfaced with X6 are:
Feeders (Dosax-, Pfister-, Schenck-), Compressors, Actuators etc.

FLS Automation
7. FA Test Procedure
FLSA shall conduct tests to verify that the functional operation of all systems and
equipment meets the requirements from FLS.
The test shall as a minimum conduct the following:
Wiring Check
By panel manufacturer
Wiring Insulation Test
Visual Inspection
By FLSA
Hardware Test
System Functional Test By FLS and FLSA
7.1 Wiring Check

The wiring is checked by conductivity test, or visually, where applying conductivity test
equipment could damage electronic devices.
7.2 Wiring Insulation Test

Main circuitry is tested applying 3…4 times the rated voltage. Where needed,
components are disconnected during insulation test.
7.3 Visual Inspection
7.3.1 Checklist
A checklist shall document the results of visual inspections.
7.3.2 Punch List

A punch list resumes items that did not pass the visual inspections.
The following visual inspections shall be performed:
Workmanship of wiring;
Location of components;
Adequacy component supports;
Tightness of all components;
Nameplates and wire tags;
Electrical wiring and terminal block layouts, using the latest or as-built system
drawings;
7.4 Preparation for test

Before the test is initiated as much as possible of the entire control system is assembled
and all communications are operational.

FLS Automation
7.5 System Functional Test

The system functional test is divided into separate activities.
7.5.1 Hardware Test
7.5.1.1 Visual Inspection by FLS

Using the FLSA Inspection Sheets and punch lists FLS can comment to these by
agreeing or adding items hereto.
7.5.1.2 I/O Test

This test is performed by randomly selecting 10% of all digital and analog inputs
and outputs for each process area.
FLS marks the signals to be spot-checked in the signal list.
The test has passed if no signal fails.
If one or more signals fail FLS is entitled to carry out a full test where all inputs
and outputs are checked one by one.
The test is performed from the terminals in I/O cabinet to the operator station,
where possible – otherwise to PLC level.
7.5.1.3 Operator Stations

Operator stations are tested to verify that monitors, keyboards and printers are
performing properly.
7.5.2 Operator Stations - User Interface
7.5.2.1 Mimics are verified for:

¡ Correctness and logical lay out;
¡ Update time.
7.5.2.2 Printing facilities are verified for:

¡ Correct printer configuration;
¡ Example on report set up.
7.5.2.3 Alarms are checked for:

¡ Acknowledge and reset
¡ Alarm suppression
¡ Department allocation
¡ Timestamp
¡ Type

FLS Automation
7.5.3 Other Tests
7.5.3.1 Autonomous systems

Autonomous systems or sub-PLCs must be linked to the main control system
during test in order to verify proper communication; controls handled in the sub-
PLC are not part of this test.
If the autonomous system for practical reasons cannot be present for test, an
identical sub-PLC including identical software will be used.
7.5.4 Functional Test
7.5.4.1 Programme functional test

Programme functional test is performed to verify that the all functions in the
programme fulfil the specification.
This is done by checking the system functionality against the interlocking
diagrams on which the program logically is based.
¡ Motors will be started and stopped in local mode.
¡ Motor groups are started and stopped in central mode.
¡ Interlocks are checked.
¡ Control loops are checked.
7.5.4.2 Programme functional test, Alarms

¡ Digital alarms are checked by triggering the input for the specific alarm.
¡ Analog alarms are checked by triggering the alarm limit specified for the
specific alarm.
¡ System alarms are tested to verify that the system-generated alarms pertaining
to the operating system are properly alarmed.
7.5.4.3 Network
¡ Network redundancy and change over functionality is verified.
7.5.5 Software simulation of I/Os

The use of an I/O simulation package will be used unless other requirements are stated.
7.5.6 Test Documents

The two following pages refer to the ‘Factory Acceptance Test Document’ and ‘Factory
Acceptance Test Document, List of exceptions’ shall be filled in immediately after
completion of the test and signed.
It is recommended that the names of the test personnel appear after <Date> and <the
premises> in the first page.

FLS Automation
7.5.7 Checklists
7.5.7.1 Hardware Checklist

See Appendix A
7.5.7.2 System Checklist

See Appendix B

FLS Automation
<System name> for <Plant name, country>
FACTORY ACCEPTANCE TEST DOCUMENT

This document is signed between the representative of the Buyer:
<Buyer's name>
(Buyer's name)
and the representative of FLS Automation A/S (the Seller) to certify that the following items:
<list of items>
ordered according to the Buyer's purchase order ref.: <Buyer's ref.>

and the Seller's order confirmation ref.: <FLSA ref.>
was tested on: <Date> at the premises of <the premises>
During the test, the Buyer has examined each item to verify it's compliance with the agreed
specifications. The Buyer has searched for and not found any reason to refuse, and with the
exceptions notified and enclosed to this FACTORY ACCEPTANCE TEST DOCUMENT,
the Buyer accepts the tested functions of the equipment to perform properly.
After verified correction of the enclosed exceptions, the Buyer shall hereby accept the
equipment as ready for packing and shipping.
This document does not relieve the Seller from any obligation of guarantee stated in the
Sellers order confirmation above.
<Location>, <date>
___________________________ ____________________________
For the Seller For the Buyer

FLS Automation
<System name> for <Plant name, country>
FACTORY ACCEPTANCE TEST DOCUMENT

List of exceptions
This List of Exceptions is part of the FACTORY ACCEPTANCE TEST DOCUMENT signed
by the Buyer:
<Buyer's name>
(Buyer's name)
and the representative of FLS Automation A/S (the Seller), and shall be understood as the
commitment of any of the parties (Seller/Buyer) noticed as the responsible party to remedy
each of the exceptions observed and listed below:
OBSERVATION OF THE EXCEPTION OF: REMEDY BY: COMPLETED ON

SELLER/BUYER
<Location>, <date>
____________________________ __________________________
For the Seller For the Buyer

FLS Automation
8. Data exchange between FLS and FLSA

This document describes how the data exchange should be carried out between FLS and
FLSA, in order to let FLS and FLSA have the full benefit of the two projecting tools
used (Edoc and Smart-Tools).
The document has been divided into two parts. The first part briefly describes the
placement of responsibility for data exchange. The second part consists of two sections,
describing the layout for de various exchange databases.
The data exchange is done in dBase file format, as it is the approved industrial standard.
8.1 Division of responsibility for data exchange
There are three models for exchanging data.
8.1.1 Model 1
FLS is responsible for: Signal code information

Tagging of PLC cabinet terminals
Connection of signal codes to PLC cabinet
terminal blocks.
FLSA is responsible for: Layout for information on PLC cabinet terminals

I/O-address information
Connection of I/O-addresses for PLC cabinet
terminal blocks.
8.1.2 Model 2
FLSA is responsible for: I/O-address information

Connection of signal codes to I/O-addresses
Information on PLC cabinet terminals
Connection of I/O-addresses for PLC cabinet
terminal blocks.

FLS Automation
8.1.3 Model 3

Information on PLC cabinet terminals
I/O-address information
Connection of signal codes to I/O-addresses
Connection of I/O-addresses to PLC cabinet
terminal blocks.
Model 1 is preferred. Model 1 reduces the workload for both groups

involved and allows for independence. Furthermore, both parties are also
independent as regards time.
It will be decided during the first kick-off meeting, which model should be
used for the project.

FLS Automation
8.2 EDOC Data exchange with Smarttools

In the EDOC system it is possible can import or export different information to or from
the system. This is done from the menu in the ‘Documents’ form:
Import: Import – Smarttools
Export: Export - Smarttools
8.2.1 Import
Two different imports can be made into EDOC depending on the information to be
imported. The two import files are EdocSiIO and EdocXTIO.
These import files can be in either Microsoft Excel format (with the extension ‘xls’) or
in Dbase format (with the extension ‘dbf’).
The first row in the files has to contain the field names and they must be spelled in the
way shown below.
8.2.2 EdocSiIO
This file can be used for importing connections between tag-signals and PLC terminals
or PLC addresses or both.
Field Required Type Size Description
Itemno X Text 18 Tagcode (with or without succeding
signalcode)
Signaltype (X) Text 6 Signalcode (required if this is not part
of the Itemno (tagcode))
PLCID X Text 7 PLC name/code
CabinetID (X) Text 12 Cabinet name/code (required if no
address is written)
RackID (X) Text 3 Rack code/number (required if no
address is written)
CardID (X) Text 4 PLC card number (slot number)
(required if no address is written)
Address (X) Text 10 PLC Address (required if no cabinet,
rack and card is written)
Subport (X) Numbe Integer PLC card terminal number (required if
r no address is written)

FLS Automation
8.2.3 EdocXTIO
This file can be used for importing connections between X-terminals and PLC-
terminals.
Field Required Type Size Description
PLC X Text 25 PLC name/code
Cabinet X Text 12 Cabinet name/code
XRow X Text 20 X-Row name
XTerm X Text 12 X-terminal name
Rack X Text 5 Rack code/number
Card X Text 5 PLC card number (slot number)
Term X Numbe Integer PLC card terminal number
r
Address X Text 25 PLC Address
8.3 Export
Three different exports can be made from EDOC depending on the information to be
exported. The three export files are EdocSiIO, EdocSig and EdocSiTe.
These export files can be in either Delimited text format (with the extension ‘txt’ and
delimitor ‘;’) or in Dbase format (with the extension ‘dbf’).
The first row in the files contains the field names as shown below.
8.3.1 EdocSiIO
This file can be used for exporting connections between tag-signals and PLC terminals
or PLC addresses or both.
Field Type Size Description
Itemno Text 18 Tagcode
Signaltype Text 6 Signalcode
PLCID Text 7 PLC name/code
CabinetID Text 12 Cabinet name/code
RackID Text 3 Rack code/number
CardID Text 4 PLC card number (slot number)
Address Text 10 PLC Address
Subport Number Integer PLC card terminal number

FLS Automation
8.3.2 EdocSig
This file is used for exporting information about signals with alarms.
Parent Text 18 Tagcode (same as Itemno)
Templatetype Text 20 Not used
Descript Text 22 Tag description
Purpose Text 22 Signal purpose
Subdepart Text 7 Department
IOType Text 5 Signal type (DI / DO / AI / AO / …)
IONode Text 12 Not used
Indicator Text 1 N: No indication or recording on CS
Y: Indication on CS
Recorder Text 3 No of hours to record (ie. ‘24h’) (Blank = no
recording)
ElRange Text 20 Electrical range (normally 4 to 20 mA, written:
‘4-20 mA’)
PhyRanMin Text 10 Physical range, minimum
PhyRanMax Text 10 Physical range, maximum
PhyRanUnit Text 15 Physical range, unit
AILLTime Number Double Alarm/Indication low-low - timedelay
AILLLim Text 20 Alarm/Indication low-low - limit
AILTime Number Double Alarm/Indication low – timedelay
AILLim Text 20 Alarm/Indication low – limit
AIHTime Number Double Alarm/Indication high – timedelay
AIHLim Text 20 Alarm/Indication high – limit
AIHHTime Number Double Alarm/Indication high-high – timedelay
AIHHLim Text 20 Alarm/Indication high-high – limit
RevDate Date - Date of last change
RevVer Text 2 Revision
RevInit Text 10 Initials of person making last change
8.3.3 EdocSiTe
This file is used for exporting information about signals with corresponding X-
terminals.
CTName Text 22 Cabinet name
CTGroup Text 8 X-Row
CTTeName Text 15 X-Terminal

FLS Automation
Responsible for the Data Exchange between

FLS and FLSA:
· Søren Juhl Jensen FLS
· Torben Johan Krejberg FLS
· Henrik Sass Lauritsen FLSA

· Jens Christian Mikkelsen FLSA

FLS Automation
9. Supply of FLSA documentation to FLS

9.1 Definitions
For FLS the FLSA documents are external instructions, which only deals with one group
of FLSA equipment. The document is placed in one or several folders; there are two
kinds of documents:
· “A” Documents are the documentation necessary for installation, operation and
maintenance of equipment. This is typical documentation elaborated and generated
by FLSA (documentation for panels, layout of bus cabling, installation instructions,
etc), however it can also be documentation from one or more of FLSA's sub-
suppliers.
· “B” Documents are the documentation that is needed for FLS/FLSA specialists on
site. Typically this is valuable documentation from FLSA's sub-suppliers such as
repair manuals for QCX - spectrometer.
Programme documentation is normally regarded as “B” documents; FLS will accept
the program documentation in one preliminary copy for installation and
commissioning and one preliminary "electronic file" file copy.
9.2 Supply of “A” documentation to FLS

In the supply agreement between FLS and FLSA it is stated how many copies of “A”
documentation FLSA are to supply.
FLSA registers each document with a 7.000000 serial number.

The FLS-EE co-ordinator shall be contacted for approving each registration.
FLSA supplies every document with a front page, summarising the contents of the
document and gives every documentation page an identification stating the placement of
the document, facilitating an unambiguous reference to the documentation page from
other documentation.
FLSA will be in charge of copying the agreed number of copies and places every copy in
a folder with the appropriate 7.000000 no.
One folder is marked "original" and floppy disk, or CD ROM, is placed in a plastic
pocket inside the folder.
The FLS purchaser in charge will receive the agreed number of copies of each document
from FLSA.
The FLS purchaser in charge registers the documentation as received and delivers both
originals and copies of the documentation to the FLS-EE co-ordinator.

FLS Automation
The FLS-EE co-ordinator will see to the reporting into the MCS system prior to the
forwarding of the documentation to REP for dispatch and filing of the original
document.
After commissioning FLSA delivers as-build reports to the FLS EE co-ordinator

regarding the program documentation and other documentation in the same number of
copies as previously sent.
FLS is held responsible for corrections of filed originals. If the corrections have been
extensive, FLS may request for a complete, new documentation.
FLS may request to receive the program documentation in a complete number of copies
where contractually obligated.
9.3 Supply of documentation "B" to FLS
· FLSA shall supply the same number of copies of the documentation "B" together
with the equipment as received from the FLSA-sup-supplier. The documents shall
be packed in the original packing together with the equipment.
· Documentation "B" is not a part of the official documentation and is not registered
in FLS's introduction registration system.


Standard Control System Manual - v01r00

Uploaded by

Document Information

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

Standard Control System Manual - v01r00

Uploaded by

Copyright:

Available Formats

FLS Automation

FLS/FLSA STANDARDISATION GROUP

The steering committee members are:

· Bjarne Jørgen Ytting FLS

· Egon Kæreby Pedersen FLS

· Bent Jørgensen FLS

· Søren Eikers FLSA