PEG/PEC/04 Page 1 of 22 Rev 0
PEG/PEC/04 Page 1 of 22 Rev 0
PEG/PEC/04 Page 1 of 22 Rev 0
CONTENTS
SECTION SUBJECT
1. PURPOSE
2. SCOPE
3. REFERENCES
4. GUIDELINES
1. PURPOSE
The purpose of this guideline is to provide guidance in good practice for the
specification of batch control software.
2. SCOPE
The guideline is in two main sections. The first section summarises the models
and terminology that form the first part of the evolving batch control standards.
The second section provides guidance in the implementation of batch control
systems.
The guideline does not attempt to be exhaustive in its treatment of the subject, but
to provide a checklist of the important aspects. Complete explanations and further
information can be found in the references provided.
3. REFERENCES
4. GUIDELINES
The models and terminology provide a common language for the definition of batch
control systems. They are summarised from Reference 1 which documents the
work done by the ISA SP88 committee. References 4 and 5 provide further
information on batch control.
Process
consists of
ordered set
Process
Stage
consists of
ordered set
Process
Operation
consists of
ordered set
Process
FigureA1c t-i oProcess
n Model
1. Process Stage
2. Process Operation
3. Process Action
May contain
Enterprise
May
contain
May contain
Site
May
contain
May contain
Area
May contain
Process
Cell
Must contain
Unit
May contain
Equipment
Module May
contain
May contain
Control
Module May
contain
1. Enterprise Level
2. Site Level
3. Area Level
5. Unit Level
6. Equipment Module
This section describes the three types of control (basic, procedural, coordination)
typically needed in batch manufacturing.
1. Basic Control
2. Procedural Control
Procedure
consists of
ordered set
Unit
Procedure
consists of
ordered set
Operation
b) Unit Procedure
c) Operation
d) Phase
3. Coordination Control
Equipment entities are formed by the addition of control functionality to the bottom
four levels of the physical model (see Figure 2). This addition is achieved in Figure
4 by mapping the procedural control model to the physical equipment model to
achieve the functionality of the process model. The resultant four equipment
entities are: process cells, units, equipment modules and control modules
The control functionality possible in the different equipment entities can be basic,
procedural or coordination in type.
Procedural Physical
Control Model (Lower Process
Model Four Levels) Model
Resulting
Procedural
Equipment Process
Elements provides process Functionality
combined functionality
with a to carry out a
Process
Procedure(s) Process
Cell(s)
provides process
combined functionality
with a to carry out a
Unit Process
Unit(s)
Procedure(s) Stage
provides process
combined functionality
with a to carry out a
Process
Operation(s) Unit(s)
Operation
Process
combined Action
with an
Equipment
Phase(s)
Module(s) provides process
functionality
to carry out a
A recipe is an entity that contains the minimum set of information that uniquely
defines the manufacturing requirements for a specific product.
includes Product-specific
General Recipe
processing information
May be
transformed into
includes
Site Recipe Site-specific information
May be
transformed into
is the
basis for
Batch ID,batch size,in process
includes
Control Recipe operator and/or system
generated information
1. Header
2. Formula
The formula includes process inputs (raw material and resource data),
process parameters (eg. temperature, pressure, time , etc) and process
outputs (product and by-product data).
3. Equipment Requirements
4. Recipe Procedure
The recipe procedure defines the strategy for accomplishing a process. The
general and site recipe procedures are structured using the levels described
in the process model since these levels allow the process to be described in
non-equipment specific terms (see Figure 6). The master and control recipe
procedures are structured using the procedural elements of the procedural
control model, since these procedural elements have a relationship to
equipment (see Figure 8).
is an ordered may be an
set of ordered set of
is an ordered may be an
set of ordered set of
General Recipe
Process Recipe
Operation Operation
is an ordered may be an
set of ordered set of
Figure 7 shows the separation between the control recipe procedure and equipment
LRQA/PEGPEC04.PEG UNCONTROLLED COPY FORSTER WHEELER ENERGY LTD
PREPARATION OF FOSTER WHEELER ENERGY LTD PEG/PEC/04
BATCH CONTROL PROCESS GUIDELINES PAGE 11
SPECIFICATIONS PROCESS ENGINEERING REV 0
control. The control recipe procedure must contain at least one procedural element
which is the recipe procedure. Equipment control must also contain at least one
procedural element that provides the linkage needed to operate the physical
equipment. For the example shown in Figure 7, this is assumed to be the
equipment phase.
The procedural elements shown in the centre of Figure 7 are those that are part of
the procedural control model. These procedural elements may exist as part of
either the control recipe procedure or equipment control, as long as the control
recipe procedure and equipment control each contain at least one procedural
element. Also, as with other models, the procedural control model is collapsible, ie
levels may be left out for a specific application.
Recipe
Procedure
Procedure
Unit
Procedure
consists of
ordered set
Operation
consists of
ordered set
Equipment
Phase
Phase
The extraction of data related to one or more batches is called a batch report. The
extraction and ordering of the data in a report may vary based on the intended
recipient of the batch report.
Resources such as equipment are assigned to a batch or a unit as they are needed
to complete or to continue required processing. Allocation is a form of
coordination control that makes these assignments. When more than one
candidate for allocation exists a selection algorithm will be used as a basis for
choosing the resource. When more than one request for a single resource is made,
arbitration is needed to determine which requester will be granted the resource.
1. Modes
2. States
Examples of states for equipment entities include : on, off, closed, open,
failed, travelling, tripped, 35% open and available.
Equipment entities and procedural elements may change state. This change
can occur if the conditional logic requirements for the change are met by
internal logic or by an external command such as one generated by another
procedural element or by an operator. Examples of commands applicable to
procedural elements are start, stop, hold, restart, abort, reset, pause,
resume.
Production
Recipe Planning and Production
Scheduling Information
Management
Management
Process
Management
Unit
Supervision
Process
Control
General
Recipe
General Recipe
Procedural Element
Manage Site
Recipe
General
Recipe
Procedural
Site Element
Recipe Information
Master Recipe
Information
Process
Management
Production Production
Recipe Management Planning and Information
Scheduling Management
Manage Process
Cell Resources
Batch and
Resource Process Cell
Information Information
Process Production
Management Information
Management
Manage Unit
Resources
Batch and
Resource Unit
Information Information
Production
Unit Information
Supervision Management
Execute Collect
Data Data
Phases
Commands
and Status Data
Information
Execute Basic
Control
4.2 Implementation
This section provides further information and advice for applying the models and
terminology introduced in Section 4.1.
Process and control engineering is needed at the general and site recipe levels to
describe procedures, process stages, and process actions and at the master recipe
level to describe procedures, unit procedures, operations, and phases.
Process and control engineering also includes the development and revision of the
phases that are used in the Recipe Management control activity to define the
recipe. As far as possible, equipment phases should be designed such that any
reasonable functionality of a unit can be expressed in terms of equipment phases.
They should generally not be tailored to a set of known recipes. Then, new
recipes can in most cases be written by referencing existing equipment phases.
The development and revision of phases is an ongoing activity that provides
ongoing support to the batch manufacturing facilities. This activity is the result of
the ongoing drive for continuous improvement and the periodic addition of new
process technology.
Processing Equipment
Considerations Considerations
Define/Select Define/Select
Procedural Elements Equipment Elements
to Match to Match
Equipment Entities Procedural Entities
Specific Scheduling/
Product Recipe Path Arbitration
Requirements Constraints
Manufacture
of Batch
Recipes can be constructed using these procedural elements and specific product
information. The equipment entities are arranged into a path that is determined by
scheduling and taking into account arbitration constraints. The combination of the
results of these activities provides a framework within which a batch of material
can be manufactured.
Each procedural level has a number of recommended formats for use in describing
procedural elements as shown in Table 2. The selection of the most appropriate
format will depend on such factors as control complexity and concurrency, the
method of software implementation and client preference.
Procedure List 1
Gantt-Chart 1
Flow Chart 3 (App. 4.1)
Operation List 1
Sequential Function Chart 1
Flow Chart 3 (App. 4.1)
An event which occurs outside the normal or desired behaviour of batch control is
commonly called an exception. The methods of handling exceptions should be
defined early in project. Of particular importance is the consideration of the actions
to be taken on power failure and then on its later restoration.
The control aspects are often finalised late in a project after the equipment design
has been completed. Subsequently, if the control is complex, such as is the case
with full batch control, the control system is often on the critical path.
Measures that can be taken to diminish the risks associated with late delivery of
the system are: