Every sequence must be divided into different “steps” each of them must have a numeric or

alphanumeric label. During the sequence execution, on the concerned graphic pages, it must be
indicated which step of the sequence is being executed at that moment. On the state of the
sequence, the following indications must be given on the screen boards and on the printer:
· Sequence running
· Sequence interrupted with the indication of the step where the interruption took place and
the cause which determined the interruption.
· Sequence finished
· These indications are valid for any sequence (start, normal stop and emergency (trip) stop).
d. Before starting an automatic sequence, Control System must check that all devices to be
managed would be ready to work; otherwise the sequence won't be started and a list of
abnormal conditions will be given to operator. This is the concept of “Preconditions” to be
fulfilled before starting a sequence. For all the sequences, a list of “preconditions to start” will be
given in FD document. It is important to be noted that these preconditions shall be checked by
logic before the sequence start. If all the preconditions will not be verified, the start command
will not be enabled (both on the graphic and in the logic). Preconditions which don’t represent
LARSEN & TOUBRO LIMITED
Page :13/130

CDQ TECHNOLOGY
T1680 80 I FD 201_2
trip conditions will no more be checked once the sequence has been started (except in case
different prescription is given in the Functional Description); on the contrary, if one or more
precondition represent a trip also, they will be found listed, in the FD, in the trip conditions list.
For each sequence, one or more graphic pages dedicated to Preconditions shall be prepared.
The verified preconditions will be indicated in green colour, those not verified will be indicated in
red. Once all preconditions will be verified, the indication “ready to sequence start” will be
displayed on Preconditions graphic page as well as on operation graphic page near the
sequence “start” button; this last feature could be done also animating the “START” indication
on sequence start button: it will be green (and button enabled) if Preconditions are all verified, or
it will be grey (and button not enabled – so nothing happens in the logic if START button is
pressed on graphic) in case at least one Precondition is not verified. In this case, anyway, the
indication “Preconditions Missing” will be displayed near the start button. This indication will not
be shown in case the sequence is running. It will be possible to “by-pass” some precondition, if
indicated in Functional Description; in this case, a push button “BY PASS” will be placed near
the precondition provided with this feature. In case the by-pass is active, the relevant indication
on the push button will be red blinking. This event shall also activate an alarm.
e. If an abnormal condition occurs after a sequence is started, the Control System will operate as
follows:
· If the problem represents a trip condition, the running sequence will be stopped, an alarm
will be generated and the trip sequence will be started
· If the problem does not represent trip condition, and occurs to a step already executed, only
an alarm will be generated, but the sequence will proceed
· If the problem does not represent trip condition, and occurs to the step in execution or to a
next one, an alarm will be generated and the sequence will be stopped
f. For all the sequences a graphic page must be prepared, showing all the sequence steps in the
order they take place. For each step the conditions (transition) for advancing with steps
(reaching of a limit stop, passed time etc.) shall be shown; each step shall be indicated with a
different colour code depending on the step status, as follows:
· white: step not executed
· yellow: step ongoing
· green: step already executed
· red: step where the sequence got interrupted
g. All tags collected from field or calculated by Control System shall be shown on Control system
graphics.
LARSEN & TOUBRO LIMITED
Page :14/130

CDQ TECHNOLOGY
T1680 80 I FD 201_2
h. The logic shall be made in such a way that for all parameters, thresholds, timer presets, etc (all
numeric values representing an input in the logic, not calculated by the same or not collected
from field or from other control systems via network connection) settable tags shall be used.
Constant values directly written in the PLC application program are not allowed. The logic shall
also foresee minimum and maximum preset for each of the above parameters. This means that,
once these max and min thresholds will be suitably set, it will not be possible to set preset
values out of the range (in order to avoid dangerous values). Whatever preset exceeding the
min and max thresholds will be “saturated” to one of the thresholds itself.
i. The distribution on I/Os on various I/O boards shall be done in such a way that for multiple or
stand-by equipment, different I/O boards must be used for different devices of stand by group.
As an example, two stand by pumps (or combustion air blowers) I/Os will be wired to different
cards, in order to minimize the possibilities of complete group fault due to a single I/O card. This
rule shall be applied to the whole plant (including process units not directly treated in the present
specification).
j. The alarm level settings shall be adjustable from the HMI, in engineering units, by privileged
access.