Guide-Introduction To Batch Processing With S88-Hallam-ICS
Guide-Introduction To Batch Processing With S88-Hallam-ICS
Introduction to
The standard was originally created in 1995 by the SP88 committee and updated in 2010 to include
the following parts:
• ANSI/ISA S88.00.02.2001 Batch Control Part 2: Data Structures and Guidelines for Languages
• ANSI/ISA S88.00.03 Batch Control Part 3: General and site recipe models and representation
The S88 standard provides a design philosophy to manufacturing processes. Using S88 enables
system designers to simplify changes to the process, reuse program modules, significantly decrease
time to market, simplify documentation and validation activities, and lower the cost of automating
your process.
Relationships
S88 breaks the process down into separate modules that relate to one another. These relationships
are described using E-R diagrams (Entity – Relationship Diagrams). The following section describes
the definitions of the diagrams used in this paper.
Process Example
In our example we will use the following equipment to produce a batch of media needed for a phar-
maceutical product
Recipe Model
The amount of detail required in a recipe depends greatly on who is reading the recipe. An R&D
group may be concerned about specific properties and procedures to create a product, but may not
care about the specific equipment used to execute the recipe. A site engineering group may need to
the type of equipment needed but may not need to know exactly which equipment is needed for each
batch. Operators will need to know the materials, procedures, and the exact equipment needed to
produce each individual batch.
To include all the information required by everybody in an organization in a single recipe becomes
overwhelming and cumbersome to maintain. To resolve this problem S88 include four types of reci-
pes: general recipe, site recipe, master recipe, and control recipe.
General Recipe
• Processing information
• No equipment listed
• Can be used for planning or investment decisions or activities
Site Recipe
• Site-Specific information
• In local language
• Based on local raw materials
• Considers sire storage constraints
Master Recipe
• Process cell-specific information
• Dependent upon equipment types or classes
• Required in any S88-aware solution to be template for control
recipes
Control Recipes
• Equipment specific information
• Batch-specific information: batch ID, batch size, raw material
used, processing steps
General Recipe
The general recipe is used at the company level and defines raw materials and their quantities
as well as the process required to produce the product. The general recipe does not take into
account the requirement to make the product at any particular site or any of the variations from
local sources of raw materials. Often a general recipe will come from R&D for a particular prod-
uct and can be used at various sites throughout the enterprise.
Site Recipe
The site recipe, as its name suggest contain more detailed information regarding a specific site,
the general equipment at that site and local raw materials. Site recipes may differ from site to
site based on geographical locations. For example two site recipes may be created for a site in
Germany and another in the U.S. The site recipe in Germany would be written in German while
the site recipe for the U.S. would be written in English.
Local ingredients may result in differences in site recipes as well. Two sites producing the same
ice cream product may need to make adjustments to their site recipes because of the differ-
ence in fat content in the local supply of milk.
Master Recipe
The master recipe is the also the template for the control recipe and is the recipe used regard-
ing S88 aware software such as FactoryTalk Batch. The master recipe will depend on specific
equipment types or classes. Quantities of specific materials may be called out. It may contain
product-specific information used for scheduling, such as equipment requirements.
A master recipe is required to generate the control recipe as it is the template for the control
recipe.
Control Recipe
The control recipe is usually created by the S88 aware software from the master recipe. It is
used to direct the activities of a specific batch. It may include information such as batchID,
batch size, characteristics of raw materials on site, and the actual equipment to be used. When
an operator is following a recipe to produce a batch it is the control recipe they are using.
Most S88 aware software start managing recipe from the master recipe level and in our exam-
ple going forward that is where we will begin as well.
Procedure
The procedure is the highest level in the hierarchy and is required if the batch requires more
than one unit (a unit is a major piece of equipment used to process the batch) to make the
batch. It contains the general strategy for making the batch and is created using an ordered set
of Unit Procedures.
In some situations a procedure level isn’t required because processing only occurs in a single
unit, but to be consistent, it is often desirable to create a procedure level for recipe regardless
of the number of units required. We will create a procedure called SF38 Growth Media that
will contain the unit procedures we need to make the media and transfer it to the destination
reactor.
Unit Procedure
The unit procedure is created using an ordered set of operations carried out on a single unit.
S88 requires that only one unit procedure may run on unit at a time. A batch cannot be pro-
cessed on one unit then transferred to another, then back again within the same unit proce-
dure. S88 does allow multiple unit procedure to run at the same time, but the must run on
different units.
For example a batch cannot run a unit procedure to make media while at the same time run a
unit procedure to CIP the same vessel. In our example we will create one unit procedure called
Make Media.
Operations
An operation is an ordered set of phases that are executed on single unit. The S88 standard
encourages the design engineer to create the operation boundaries at points in the process
where the process can be safely suspended. The standard assumes that only one operation
will be executed at a time.
This is often difficult to accomplish without making the operations extremely complicated. For
example, it is frequently required to run an agitator and a TCM module to maintain temperature
during the entire processing time. While it is possible to include these phases in each individ-
ual operation, it is often desirable to break them out into their own operation and run them in
parallel at the unit procedure level. In our example we will create two operations: Make Media
and Transfer Media.
Phases
The phase is the smallest module in the procedural model. It is usually the level that links to
the equipment model and the devices controlling the equipment. Phases perform unique, ba-
sic, and generally independent functions. Examples of phases could be heat, pressurize, mix,
transfer, recirculate, charge, or react.
Often S88 aware software will allow the designer to give phases “multiple personalities” using
something known as control strategies. For example, instead of simply pressurizing a vessel
the equipment may be capable of several different types of pressure control. It may be able
to pressurize to a setpoint, or pressurize to setpoint using a ramp and soak profile, or instead
of pressurizing pull a vacuum. Perhaps instead of pressurizing to a setpoint, all that is needed
is to open the vessel to the atmosphere. The designer could create separate phases for each
of these functions but it is often convenient for to create a single phases with multiple control
strategies to accomplish each task.
Example Recipe
Using our example system described above let’s put together a sample master recipe using all
the whole procedure model.
Physical Model
The other half of the S88 standard defines the physical model or the equipment layer. The physical
model defined in S88 is broken into seven blocks: Enterprise (Company), Site, Area, Process Cell,
Unit, Equipment Module, and Control Module.
Enterprise
The enterprise level refers to the company.
Site
The site level refers to the plant manufacturing the product. A company may have multiple sites
producing the same products. Generally sites are determined by geography, but that doesn’t
mean two sites cannot be physically adjacent.
Area
The area level refers section within a site. Not every area in a site must be associated with
the site, especially if the area doesn’t have anything to do with batch control. For example
the administration area in the site most likely doesn’t need to be included. However, process
areas can be included such as media prep, buffer prep, cell culture, and purification could be
designated as areas.
Process Cell
The process cell also referred to as a “process train” includes all the equipment required to
produce a batch. A process cell may contain more than one train, but a train cannot breach the
boundaries of a process cell.
A process cell may process more than one batch at a time, and batch need not use all of the
equipment in the process cell.
Unit
Most batching activities are focused around the unit. A unit is a piece of equipment where one
or more major processing activities take place. Generally they include equipment such as re-
actors, mixing vessels, or CIP skids. The do not include storage tanks or holding vessels. One
way to help determine if a piece of equipment should be considered a unit is to decide whether
you need it to run a recipe. All recipes require a unit to execute them. Storage tanks will gen-
erally be acquired by another unit and used in its recipe.
Some things to keep in mind about units is that they can only operate on one batch at a time.
They can only execute a single unit procedure at a time. They generally hold the entire or a
portion of the batch and perform some processing to add value to the batch.
It is helpful to consider CIP (Clean In Place) skids a unit and treat CIP activities similar to
batching activities. Technically CIP activities are not a batch process because a product is not
produced, but CIP can be recipe driven and the S88 standards and rules can be made to apply
to the CIP activities.
Control Module
The control module is model of a specific device such as a valve or pump. Control modules
may contain other control modules but this can get confusing when trying to distinguish be-
tween a control module and equipment module. The control module should be a single entity
and is the direct connection to the input and outputs to the actual device. The modules often
contain automatic and manual modes, simulation functions, the ability to set permissives and
interlocks, and process alarms.
Equipment Module
The equipment module is a collection of control modules. The equipment module should pro-
vide a finite list of commands and perform a define set of functions. The idea is that your recipe
should not command each control module individually but the equipment will drive the control
module based on the requested commands.
The advantage of grouping control modules into functional groups is that the detail in con-
trolling each device is abstracted by the equipment module layer.
An example would be the outlet line in our example system shown in figure 8. It is displayed
again below for convenience.
The outlet line equipment module might contain the following control modules: XV-510030, PU-
510056, XV-510034, XV-510035, XV-510036, XV-510037.
The module then could provide the following functions:
• Idle – All valve closed and pump de-activated
• Recirculate – XV-510030 and PU-510056 is energized to recirculate the material
• Transfer to BRX-2000 – XV-510030, PU-510056, XV-510034, and XV-510035 is energize
• Transfer to BRX-3000 – XV-510030, PU-510056, XV-510034, and XV-510036 is energize
• Transfer to BRX-4000 – XV-510030, PU-510056, XV-510034, and XV-510037 is energize
The phase logic called by the batch control system would then simply take ownership of the
equipment module and issue the transfer to BRX-3000 command or recirculate command. The
phase logic doesn’t need to know which control modules are needed to execute the command
because the equipment module takes care of that.
Another big advantage of this architecture is that the commands to the equipment modules
can be common to all equipment modules of a similar type. That is to say all the outlet lines
may have the same set of commands so from the phase’s point of view it doesn’t matter which
module it is work with, the logic is the same.
The differences in the outlet lines from unit to unit are handled by the equipment module and
abstracted to the phase logic commanding it.
Technically input devices, flow meter, or level meter for example, are control modules as well,
but it can be beneficial not to include them in the equipment module definition unless it makes
sense to do so. It makes sense to include pressure in a pressure equipment module that also
includes valves and a controller to manipulate pressure, but level may be on its own and used
by several separate equipment modules and phase. It can be difficult where to place these
types of devices, and sometimes it is best to include them with the unit definition.
The next step is to group the control modules into functional groups. The outlet line is pretty
straight forward in our example. However, the inlet lines where the material additions occur
can be problematic. It may seem like a good idea to group all of the inlet valves together as
an equipment module, but this can sometimes make controlling transfers from the source tank
difficult. If situations like a WFI loop where the material is supplied to several vessels as a utility
and several vessels can draw on that utility simultaneously then creating a separate EM for
material makes sense. When the material is coming from a storage tank where only a single
transfer can occur at a time, it is best to include the all of the control modules in the outlet line
of the source tank. The equipment modules for our example:
Idle
In the idle state the phase is not running and is waiting for the start command to transition into
running.
Running
The running state is the normal operating state for the phase. From the running state the recipe
phase may issue a hold, stop, or abort command to transition the phase to handle an abnormal
condition. The phase may also run to a normal completion, then transition to a complete state.
Complete
The phase transitions to complete after running through its normal operation. The phase is now
waiting for a reset command to return the idle state.
Holding
The phase receives a hold command while in the running state and executes separate logic
to place the appropriate equipment into a held condition. Once the holding logic completes the
state machine automatically transitions to the held state.
Restarting
The phase receives a restart command while in the held state and executes separate logic to
restart the phase to safely return to the running state.
Stopping
The phase receives a stop command and executes the stopping logic. After the stopping logic
completes the state machine automatically transitions to the stopped state. A stop command
can be issued while the state machine is in running, holding, held, or restarting. Generally the
stop command is used to cleanly bring the phase to safe stop, and return the equipment to
a recoverable state. It can also be used with phases that do not have a clear stopping point.
Agitation frequently requires an external stop command to bring the phase to an end.
Aborting
The phase receives an abort command and executes the aborting logic. After the aborting logic
completes the state machine automatically transitions to the aborted state. Similar to the stop-
ping state the command can be issued during the running, holding, held, or restarting states.
Abort can be used to bring the phase to an immediate stop. Operators usually need to manually
manipulate the equipment to bring back into a useable condition.
Resetting
The phase receives a reset command while in the completed, stopped, or aborted states and
executes logic to reset the phase. After the resetting phase completes phase automatically
returns to the idle state, waiting for the run command to begin again.
CLICK HERE
What’s Next
We hope you will find this Guide to Batch Processing with S88 helpful. For further assistance, please
reach out to the process controls experts at Hallam-ICS.
www.hallam-ics.com/control-and-automation-systems
1-800-287-0800
References
Parshall, Jim and Lamb, Larry. Applying S88 Batch Control from a User’s Perspective ISA, 2006. Print
Parshall, Jim and Lamb, Larry. www.BatchControl.com Batch Control.com LLC
Introduction To Batch Processing with S88 - GUIDE 20
www.Hallam-ICS.com
Connecticut | 363 Main Street, Suite 303, Middletown, CT 06457 | Tel: 860-788-6815 | Fax: 802-658-1457
Massachusetts | 575 West St., Suite 220, Mansfield, MA 02048 | Tel: 508-821-9759 | Fax: 508-821-9739
New York | 107 Hermes Rd., Suite 130, Malta, NY 12020 | Tel: 518-289-5582 | Fax: 802-658-1457
North Carolina | 3801 Lake Boone Trail, Suite 100, Raleigh, NC 27607 | Tel: 919-821-4145 | Fax: 919-821-4147
Vermont | 38 Eastwood Drive, Suite 200, So. Burlington, VT 05403 | Tel: 802-658-4891 | Fax: 802-658-1457