Ref Batch Management

Toc G-1
IM 33S01B30-01E
CS 1000/CS 3000
Reference
Batch Management
CONTENTS
17th Edition : Jul.14,2008-00
IM 33S01B30-01E 17th Edition
PART-G Batch Management
G1. Overview of Batch Management .......................................................... G1-1
G1.1 ISA S88.01 and Batch Management ............................................................. G1-2
G1.2 What is a Recipe? ......................................................................................... G1-5
G1.3 Hierarchy of Procedure ................................................................................ G1-9
G1.4 Application Capacity .................................................................................. G1-12
G2. Recipe Management ............................................................................. G2-1
G2.1 Master Recipes ............................................................................................. G2-2
G2.1.1 Header ........................................................................................... G2-3
G2.1.2 Procedure....................................................................................... G2-9
G2.1.3 Formula ........................................................................................ G2-15
G2.1.4 Equipment Requirements ............................................................. G2-24
G2.1.5 Handling Master Recipe File ......................................................... G2-26
G2.2 Recipe Group and Train.............................................................................. G2-28
G2.3 Common Block ........................................................................................... G2-33
G2.4 Engineering of Unit Common Block .......................................................... G2-43
G2.4.1 Engineering on System View ........................................................ G2-45
G2.4.2 Engineering on Recipe View ......................................................... G2-47
G2.5 Recipe View................................................................................................. G2-51
G2.6 Recipe Data Backup ................................................................................... G2-62
G3. Process Management ........................................................................... G3-1
G3.1 Batch Execution Management ..................................................................... G3-2
G3.2 Recipe Setup ............................................................................................... G3-17
G3.3 Batch-Related Messages............................................................................ G3-28
G3.4 Batch Result Data ....................................................................................... G3-31
G3.5 Duplicating Control Recipe ........................................................................ G3-40
G3.6 Exporting Formulas .................................................................................... G3-46
G3.6.1 Exporting Formulas Manually ....................................................... G3-47
G3.6.2 Exporting Formulas Automatically ................................................. G3-53
G3.7 Security Settings of Process Management ............................................... G3-55
G3.8 Dual-Redundancy ....................................................................................... G3-62
IM 33S01B30-01E
Toc G-2
10th Edition : Dec.18,2003-00
G3.9 Batch Related Trend Management ............................................................. G3-67
G3.9.1 Batch Related Trend File .............................................................. G3-68
G3.9.2 Batch-Related Trend Window ....................................................... G3-76
G4. Unit Supervision under Batch Management........................................ G4-1
G4.1 Nonresident Unit Instrument ........................................................................ G4-2
G4.2 Operation....................................................................................................... G4-5
G5. Production Planning and Scheduling Interface .................................. G5-1
G5.1 Overview of Production Planning and Scheduling Interface ..................... G5-2
G5.2 Schedule Expansion..................................................................................... G5-4
G5.3 File Format of Fixed Schedule File............................................................... G5-8
G6. Production Information Management .................................................. G6-1
G6.1 Overview of Production Control Information Management ........................ G6-2
G7. Product-Related Windows ................................................................... G7-1
G7.1 Architecture of Product-Related Windows.................................................. G7-2
G7.2 Product Overview Window........................................................................... G7-8
G7.2.1 Elements of Product Overview Window ........................................ G7-10
G7.2.2 Dialog Boxes Extended from Product Overview Window .............. G7-15
G7.3 Product Control Window ............................................................................ G7-35
G7.3.1 Elements of Product Control Window............................................ G7-37
G8. Engineering when Connecting Multiple Projects................................ G8-1
G8.1 Connecting CS 3000 and CS 1000................................................................ G8-6
G8.1.1 Engineering of the Upper-Level Project (CS 3000) .......................... G8-7
G8.1.2 Engineering of the Lower-Level Project (CS 1000) ........................ G8-14
G8.2 Unilateral Connection between CS 3000s ................................................. G8-19
G8.2.1 Engineering of the Upper-Level Project (CS 3000) ........................ G8-20
G8.2.2 Engineering of the Lower-Level Project (CS 3000) ........................ G8-27
G8.3 Bilateral Connection between CS 3000s.................................................... G8-32
G8.3.1 Common Engineering ................................................................... G8-35
G8.3.2 Engineering of Recipe Group in which the Self Project Becomes
the Upper-Level Project ................................................................ G8-37
G8.3.3 Engineering of Recipe Group in which the Self Project Becomes
the Lower-Level Project ................................................................ G8-43
G8.4 Connecting CS 3000 and CS ...................................................................... G8-47
G8.4.1 Engineering of the Upper-Level Project (CS 3000) ........................ G8-48
G8.4.2 Engineering of the Lower-Level Project (CS) ................................ G8-55
<G1. Overview of Batch Management> G1-1
IM 33S01B30-01E
G1. Overview of Batch Management
This chapter gives an overview of Batch Management.
G1-2 <G1.1 ISA S88.01 and Batch Management>
IM 33S01B30-01E
G1.1 ISA S88.01 and Batch Management
The ISA SP88 is a working group for international standard on Batch Control under
the ISA (Instrument Society of America) in the U.S.. One of the publications they put
together is Batch Control Part 1: models and terminology, which was published in
1997 as IEC/61512-1.
This section describes the relationship between ISA S88.01 and Batch Management.
Physical Model
In ISA S88.01, a Physical Model (equipment support model) comprised of 7 levels is
defined. With CS 1000/CS 3000 Batch Management, the system can be hierarchically
constructed in a manner different from the actual physical hierarchy by using unit instru-
ments, operations and control blocks (PID blocks, etc.) that correspond to units, equipment
modules (equipment) and control modules (instrument), respectively.
G010101E.EPS
ISA S88.01 Physical Model Batch Management
Train
Recipe group
Unit instrument
Regulatory control block
SEBOL
Sequence table
Logic chart
SFC block (operation)
Enterprise
Site
Area
Process Cell
Unit
Equipment Module
Control Module
Figure Physical Model and Batch Management
<G1.1 ISA S88.01 and Batch Management> G1-3
IM 33S01B30-01E
Control Activity Model
To control batch manufacturing, a Management Activity Model consisting of 7 activities is
defined in ISA S88.01as follows. Unit supervision occupies a position of supervising pro-
cess management.
G010102E.EPS
Production planning
and scheduling
Production information
management
Recipe management (*1)
Process management
Unit supervision (*2)
Process Control
(Function block)
Scopes of Batch Management
Personnel and
Environmental Protection
(*3) (*4)
Figure Control Activity Model and Batch Management
*1: The recipe management defined in ISA S88.01 includes General Recipe, Site Recipe, Master Recipe and Control
Recipe. Batch Management functions supports Master Recipe and Control Recipe.
*2: Unit supervision is included in the FCS basic control functions. Unit supervision can be operated by itself without being
combined with the Batch Management Recipe Management and process management.
*3: The Batch Management uses the production planning and scheduling interface as an interface between the Process
Management and the Production Planning and Scheduling.
*4: The Batch Management uses an OPC interface as an interface between the Process Management and the Production
Information Management.
G1-4 <G1.1 ISA S88.01 and Batch Management>
IM 33S01B30-01E
Procedural Control Model
In a batch process, operating procedures and manufacturing procedures are changed
according to the product to be made. The S88 Procedural Control Model indicated below is
a hierarchical representation of these procedures. With Batch Management, phases and
other levels below them are assigned to SEBOL, sequence tables, and logic charts and
operations are executed by the SFC blocks, based on the ISA S88.01 model. Unit proce-
dures are executed by the unit instruments to perform overall control of the operations.
G010103E.EPS
Blending
Reaction
Process
Procedure
Unit Procedure
Operation
Initialization
Charge of catalyst
Component A
Initialization
Sequence
Table
G010103E.EPS
Component B
Logic chart
Phase
SEBOL
Charge A
Heating
Procedure
Unit Procedure
Operation
Phase
ISA S88.01 Batch Management
Figure Procedural Control Model and Batch Management
<G1.2 What is a Recipe?> G1-5
IM 33S01B30-01E
G1.2 What is a Recipe?
The recipes controlled in Batch Management prescribe the manufacturing proce-
dures, parameters and units used in producing a particular product.
Types of Recipes
In the ISA SP88.01, recipes are divided into four types as shown in the diagram below,
depending on what needs to be done and which resources are required to manufacture the
product.
Of these, the CS Batch 1000/CS Batch 3000 handles master recipes and control recipes.
The Process Management handles control recipes and the Recipe Management handles
master recipes.
G010201E.EPS
General Recipe
Site Recipe
Master Recipe
Control Recipe
Recipe management
Process management
Figure Types of Recipes
G1-6 <G1.2 What is a Recipe?>
IM 33S01B30-01E
General Recipe
General recipes do not specify a plant to be used. Instead, they deal with production plans
and other activities that involve a company as a whole. Thus, quantities handled in formu-
las are defined primarily by a development group (researchers, etc.) in a testing lab or at a
pilot plant. The purpose of general recipes is to separate general descriptions regarding the
chemical processing, manufacturing processing, and processes required to manufacture
the product, from specific information on the plant and units. By doing this, those who
develop general recipes can do so without knowledge of the specific units. The Batch
Management does not handle general recipes.
Site Recipe
Site recipes contain information that have been changed to match the conditions at a
specific manufacturing site and are necessary for long-term production schedules at the
site level. The site refers to a physical, geographical or logical entity as determined by each
company. As is the case with general recipes, Batch Management does not handle site
recipes.
Master Recipe
Master recipes are the modified recipes for meeting plant conditions. With the Batch
Management, the components in a master recipe are specified as absolute quantities.
When using a master recipe as a control recipe, actual parameters must be determined in
accordance with the unit used to process the batch and the batch size executed by the unit.
With Batch Management, master recipes are handled by the Recipe Management.
Control Recipe
Control recipes clarify the items required for producing a specified batch of a particular
product. Control recipes contain detailed information necessary for minute-by-minute
operation of the plant. The detailed information provided by a control recipe has been
modified to account for the quality of actual raw materials and the actual equipment used.
With Batch Management, control recipes are handled by the Process Management.
<G1.2 What is a Recipe?> G1-7
IM 33S01B30-01E
Structure of Recipe
In general, a single recipe consists of the following items:
Header
Equipment
requirements
Procedure
Other
information
Formula
Recipe
G010202E.EPS
Figure Structure of Recipe
Header
Indicates information used to manage recipes such as recipe name, version and date/time
of creation.
Procedure
The procedure specifies procedure for manufacturing a product in process production.
Procedures prescribe the order of actions that should be taken for a specific purpose or the
manufacturing procedures and control methods in a given batch process, and are de-
scribed in the SFC (Sequence Function Chart).
Formula
The formula is a set of parameters used to manufacture the product defined by the recipe
procedure. These parameters define the values of process variables and the types and
quantities of components.
Equipment Requirements
The equipment requirements define conditions for units and other equipment necessary for
manufacturing a product.
Other Information
Information excluded from the other parts of the recipe that supports the batch process falls
into this category. This information includes laws and regulations to comply with, product
safety information, process flows, packaging, labeling, etc.
G1-8 <G1.2 What is a Recipe?>
IM 33S01B30-01E
Recipes and Unit Recipes
A recipe is composed of unit recipes to run on a particular unit, and a common block that
stores data for use in a recipe. A unit is in a one-to-one relationship with a particular unit if a
product is transferred form one unit to another before it its finished.
The diagram below shows the relationship between units and unit recipes.
The unit recipe of Batch Management contains a recipe unit procedure that runs on a
particular unit. Formulas are not owned by a unit recipe but located in the common block, or
a shared areas, so that they can be referenced/set by every recipe unit procedure.
G010203E.EPS
Recipe
Unit recipe 1
Recipe unit procedure
Unit recipe 2
Unit recipe 3
Shared area
(Common block)
Formula
Unit 1
Unit instrument
Unit 2
Unit instrument
Unit 3
Unit instrument
Figure Units and Unit Recipes
<G1.3 Hierarchy of Procedure> G1-9
IM 33S01B30-01E
G1.3 Hierarchy of Procedure
In a batch process, operating procedures and manufacturing procedures are changed in
order as products are made. These procedures have a hierarchical structure and can be
broken down as shown in the diagram below. The operations at each hierarchical level are
executed sequentially or in parallel.
The functions used to execute sequence procedures are provided by the corresponding
process management, unit instrument, operation, SEBOL, sequence table block, and logic
chart blocks.
G010301E.EPS
Procedure
Control action
Control step
Phase
Operation
Unit procedure
procedure
control action
control step
(Corresponding functions)
phase
operation
unit procedure
Process management
SEBOL
Sequence table
Logic chart
Operation
Unit instrument
Figure Procedure Model
G010302E.EPS
Recipe Procedure Master Recipe Recipe Unit Procedure Equipment Operation Phase
Polymerize 1
Dry PVC 3
Recover PVC 2
Preparation 1
React 3
Charge 2
Add Catalyst 1
Heat to 55 3
Add VCM 2
Add VCM 4
Sequence
Table
Logic Chart
Make PVC
SEBOL
Recipe Management Unit Supervision
Figure Hierarchy of Procedure
G1-10 <G1.3 Hierarchy of Procedure>
IM 33S01B30-01E
Recipe Procedure
A recipe procedure reflects the relationships among the equipment entities (units). Recipe
procedure determines the order of recipe unit procedure execution.
Recipe Unit Procedure
A recipe unit procedure is a unit procedure controlled as a recipe. Recipe unit procedure
determines the process procedures and control methods corresponds to an equipment
entity (unit).
When a part of manufacturing methods vary with processes, a recipe unit procedure may
be applied. Thus this part of manufacturing methods may be defined as a recipe unit
procedure and downloaded to an FCS. Then this procedure can be executed by a unit
instrument.
Operation
An operation defines a process sequence for switching the running status from one to the
other based on chemical or physical process changes.
An operation may be started from a recipe unit procedure. Generally speaking, in a con-
tinuous process, one unit only requires one operation to be executed in a unit instrument. In
a batch process, multiple operations may be required to run in one unit instrument as the
operating sequence.
Some of the basic operations in a batch process are not specific to a recipe but can be
shared.
In the following example, the cleaning sequence is a shared operation.
G010303E.EPS
Recipe unit procedure B
Initialization B
Cleaning
Charge B
2
3
1
Cleaning
sequence
Recipe unit procedure A
Operations specific to the unit
Initialization A
Cleaning
Charge A
2
3
1
Initialization A
sequence
Charge A
sequence
Initialization B
sequence
Charge B
sequence
Operation can be shared
Operations specific to the unit
Figure An Example of Operation
<G1.3 Hierarchy of Procedure> G1-11
IM 33S01B30-01E
Phase
In an operation, a phase refers to a processing or operation that is associated with a
process event.
Normally, a phase is determined in consideration of the discontinuation point of a process
in a logical sense or the point of a process where operator intervention is practicable in
view of safety.
For the sequences that enable a phase to run, the set of operating steps is selected in such
a manner that the requirements for repetitive operation and external factors are fulfilled.
For example, the following phases are selected for use with an operation, such as a charge
sequence or reaction sequence.
Operation Phase
Charge sequence Charge of component A
Charge of component B
Agitation
Charge of component C
Reaction sequence Heating
Charge of component D
Thermal insulation
Discharge sequence Cooling
Transfer
G010304E.EPS
Figure An Example of Operations and Corresponding Phases
Some applications may treat a process over an extended period of time as a phase for
operational or managerial reasons, or use a phase to ensure a certain period of time for
parameters to be changed.
Control Step
A control step is the lowest-level processing used to state operating actions or events in a
phase with which the operator is especially concerned.
A control step contains instructions that directly act upon the manipulation of a final control
element. Normally, this manipulation is stated using a control instruction.
For example, just as the user uses a batch-oriented language to state charge of compo-
nent A in charge sequence, the user can use control instructions to state the desired
control step, as shown below:
Phase Control Step
Charge of component A Open charge valve A
Wait until amount of charge reaches B kg
Close charge valve A
G010305E.EPS
Figure An Example of Phases and Corresponding Control Steps
In the actual description of control instructions using SEBOL, a sequence table, or a logic
chart, one control instruction may be represented by a single statement or it may require
multiple statements.
These instructions for the control steps are given in such a manner that they directly asso-
ciate with the specific actions or manipulations of equipment modules or units.
G1-12 <G1.4 Application Capacity>
IM 33S01B30-01E
G1.4 Application Capacity
This section describes application capacities for different types of batch manage-
ment function.
Application Capacities for Recipe Management
Maximum Number of Master Recipes
The table below shows application capacities for the recipe management function:
Table Application Capacities for Recipe Management Function
Item Max.
Number of recipe group/project 16
Number of master recipes/recipe group 1000
Number of unit recipes/master recipe 32
Number of Path menu/master recipe 64
G010401E.EPS
Number of defining a formula/master recipe 30000
Application Capacities for Process Management
Maximum Number of Control Recipes
The table below shows application capacities for the process management function:
Table Application Capacities for Process Management Function
Item Max.
Number of server stations/recipe group 2
Number of client stations/recipe group 14
Number of trains/recipe group 16
Number of Path/train 64
Number of control recipes/recipe group 999
Number of control recipes/project 999
Number of control unit recipes/project 4000
Number of common blocks/project 1000
Number of common blocks/master recipe 256
Number of common data items/common block 256 (*1)
Data check pattern/common block 255
G010402E.EPS
Number of unit recipes Number of control recipes x 8
*1: This figure assumes the entire array as 1. The data area size is less than 32 Kbytes. The array is up to two dimensions
(999, 999) and the total sum of array elements is 10000 or less.
<G1.4 Application Capacity> G1-13
IM 33S01B30-01E
Number of ACTIVE Control Recipes by Type
There are three types of the process management function with different capacities, i.e.
they support different number of ACTIVE control recipes, to match the scale and complexity
of different plants. The number of ACTIVE control recipes refers to a total sum of the control
recipes whose recipe status is other than RESERVED or COMPLETE. The table below
shows the number of ACTIVE control recipes for each type:
Table Number of ACTIVE Control Recipes by Type
Type classification Number of ACTIVE control recipes
Type A 4 or less
Type B 10 or less
Type C 999 or less
G010403E.EPS
SEE ALSO
For the recipe status, see the following:
Control Recipe Statuses in G3.1, Batch Execution Management
Number of ACTIVE Control Recipes by Type
There are three types of the process management function with different capacities, i.e.
they support different number of ACTIVE control recipes, to match the scale and complexity
of different plants. The number of ACTIVE control recipes refers to a total sum of the control
recipes whose recipe status is other than RESERVED or COMPLETE. The table below
shows the number of ACTIVE control recipes for each type:
Table Number of ACTIVE Control Recipes by Type
Type A 10 or less
Type B 50 or less
Type C 999 or less
G010404E.EPS
Table Number of ACTIVE Control Recipes by Type (For Entry Class)
Type A 4 or less
Type B 10 or less
Type C 999 or less
G010405E.EPS
SEE ALSO
For the recipe status, see the following:
Control Recipe Statuses in G3.1, Batch Execution Management
11th Edition : Oct.28,2004-00
Blank Page
<G2. Recipe Management> G2-1
IM 33S01B30-01E
G2. Recipe Management
This chapter explains the master recipes created by Recipe Management.
What is Recipe Management?
Recipe management is positioned at the same level as the production planning and sched-
uling and the production information management in the system hierarchy, and it interfaces
with the process management. The recipe management categorizes recipes and allows the
user to create and modify master recipes.
G020001E.EPS
Production planning
and scheduling
Production information
management
Recipe management
Process management
Unit supervision
Process Control
(Function block)
Scope of this chapter
Figure Positioning of Recipe Management
G2-2 <G2.1 Master Recipes>
IM 33S01B30-01E
G2.1 Master Recipes
Master recipes can be created using the Recipe Builder and the Recipe Procedure
Builder. This section explains the structure and components of a master recipe.
Structure of Master Recipe
A master recipe is composed of the following components.
G020101E.EPS
Header Equipment requirements Formula Procedure
Master recipe
Figure Structure of Master Recipe
Header
Defines the management information of the recipe such as the name and version of the
recipe, and the date when the recipe was created.
Procedure
Defines the procedure for manufacturing the specified product in the processes; coded as
a sequential function chart (SFC).
The procedures may be created via master recipe are recipe unit procedure and recipe
procedure.
Formula
Defines the parameters used in the procedure for manufacturing the specified product. The
parameters include process values and the type and quantity of the component.
Equipment Requirements
Define the equipment units required for manufacturing the product by specifying the unit
names. Equipment Requirements can be defined with train names-Path names or unit
names.
<G2.1 Master Recipes> G2-3
IM 33S01B30-01E
G2.1.1 Header
The header contains the basic information required for managing the recipe, such as
the recipe name, version, and date of creation. Data values set in the header are
displayed in the Recipe Header dialog box opened from the Product Overview
window or Product Control window.
Unit Recipe Formula Equipment Requirement (Train-Path) Equipment Requirement (Unit)
Recipe Builder [Pjt:MYPJT Gr:RG01 Rcp:RCP0001 File:RcpHead.edf]
Recipe Comment
File Edit View Tools Window Help
Recipe Comment
Recipe Header
Recipe RECIPE01
Create Date 1998/08/05 17:01
Comment PRODUCT-A RECIPE.
Description This recipe is for Product-A
This recipe has two parts for two units
The recipe for unit 2 is started by the recipe for unit 1.
The reaction process requires manual charge of the additive,
prepare the additive before the process starts.
Product Name Product-A
Version No. 1
Version Date 1998/08/05 17:01
Creator Name CENTUM
G020102E.EPS
Ready
Message
Figure Recipe Header Tab
SEE ALSO
For the Recipe Header dialog box, see the following:
Recipe Header Dialog Box in G7.2.2, Dialog Boxes Extended from Product Overview Window
Create New Recipe Group
When creating a recipe header, if the recipe group for the recipe has not been created, a
warning dialog box appears.
Recipe Builder
G020115E .EPS
The Reference Project Directory is unspecified or incorrect
OK
Figure Warning Message Box
To create a new recipe group, select BATCH folder on System View, then choose [File] -
[Create New] - [Recipe group].
The newly created recipe group needs to be configured on Process Management Builders.
IM 33S01B30-01E
Header Definitions
Defining Recipe Header
After a recipe is created on Recipe View, the data values of the recipe header can be set.
The data values in the header are set in the Recipe Header tab on the Recipe Builder
window. The table below lists the data items in the Recipe Header tab.
Table Header Data
Data Item Description Data Type
Recipe Name The name of the recipe CHR16
Recipe Creation Date The date when the recipe was created U32
Recipe Comment The comment for the recipe CHR64
Recipe Description The description for the recipe CHR805
Product Name The name of the product manufactured by the recipe CHR32
Version Number The version number of the recipe CHR16
Version Date The date when the Version Number setting was modified last U32
Author The person who modified the recipe last CHR32
Approved by The person who approved the recipe last CHR32
Approval Date The date when the recipe was approved last U32
Master Recipe Status The master recipe status CHR16
Engineering Unit The engineering unit of the recipe CHR8
Recipe Standard Size The unit requirement of the recipe F64
Maximum Production Quantity The maximum production quantity of the recipe F64
Minimum Size of Recipe The minimum production quantity of the recipe F64
Security Level The security level of the recipe U8
Recipe Download Mode The download mode of the recipe
Recipe Start Mode The start mode of the recipe
CHR8
CHR8
G020103E.EPS
F64: 64-bit double-precision floating point real number
U32: 32-bit integer without a sign
U8: 8-bit integer without a sign
CHRn: Text string data with n characters
CHRnm: Text string data with n characters on row m
Recipe Name
The name set for a recipe newly created in the recipe view window is displayed. To change
the recipe name, enter up to 16 alphanumeric characters or eight double-byte characters.
Recipe Creation Date
The date when the recipe was created in the recipe view window is set.
Recipe Comment
The comment set for a recipe newly created in the recipe view window is displayed. To
change the recipe comment, enter up to 64 alphanumeric characters or 32 double-byte
characters.
IM 33S01B30-01E
Recipe Description
Enter a description for a recipe such as operation methods on up to five lines. Each of
these lines can contain up to 80 alphanumeric characters or 40 double-byte characters.
Product Name
Enter up to 32 alphanumeric characters or 16 double-byte characters for the name of a
product manufactured according to a recipe.
Version Number
Version Number is used to control the modification of recipe. When a recipe is modified, a
version number will be added automatically.
If the recipe revision number is not under automatic management, the revision number
needs to be manually entered when the recipe is revised. If the revision number is under
the automatic management, users do not set the revision number.
When the recipe revision number is under the automatic management, the recipe revision
number is increased by one whenever recipe build is performed even though the recipe
build fails. The upper limit of the revision number is 100,000,000, when reaches the limit,
the revision number restarts from 1.
When copying a recipe on Recipe View, or when importing a recipe from the recipe builder,
the copied or the imported recipe has the same revision number of the original recipe.
IMPORTANT
If the revision number is under the automatic management, when run download/build the
recipe on Recipe View or on Procedure Builder, the recipe builder should be closed. When
download/build a recipe on Recipe View or on Procedure Builder without closing the recipe
builder, a build error will occur. However, download/build on Recipe Builder has no such
problem.
When set a recipes revision number under the automatic management, if the existing
revision number was set with the R3.02 or earlier software release, the revision number
under the automatic management is processed as follows.
If the revision number is a natural number of alphanumeric character string, this
number will be based for increment.
If the revision number is an alphanumeric character string but not a natural number,
the existing revision number will be cleared and the increment of new revision number
will be started from 1.
SEE ALSO
For more information about recipe revision number automatic management, see the following:
Create New -Project in File Menu of Recipe View in G2.5, Recipe View
IM 33S01B30-01E
Version Date
The date when the Version Number setting was modified last is set. The date cannot be set
by user.
Author
The name of the user who logged on is set by default. The name may be modified accord-
ingly.
Approved by
Setting is enabled when Master Recipe Status is changed to Approved. The name of the
user who logged on is set by default. The name may be modified accordingly.
When status of the master recipe is changed to [Not Approved], the approver name in
[Approved by] item is reset.
Approval Date
The date when Master Recipe Status is changed to Approved is set.
When status of the master recipe is changed to [Not Approved], the date in [Approval Date]
item is reset.
Master Recipe Status
The setting is Approved or Not Approved. Modification is allowed also on a recipe whose
Master Recipe Status is Approved.
When status of the master recipe is changed from [Approved] to [Not Approved], the
approver name in [Approved by] item and the date in [Approval Date] item are reset.
G020104E.EPS
Creation of new recipe
(Approved by and Approval Date=blanks;
Version Number=1)
Not
Approved
Approved
Cancellation of approval
(Approved by and
Approval Date
settings are reset.)
Approval
(Approved by and
Approval Date are set)
Modification of approved recipe
(Approved by Approval Date,
and Version Number settings are kept)
Figure Master Recipe Status
IM 33S01B30-01E
Engineering Unit Symbol
Set an engineering unit symbol for use in manufacture.
Recipe Standard Size
Set a standard size for a recipe. The CS Batch 1000/CS Batch 3000 does not have the
scaling function supporting the recipe standard size.
Maximum Production Quantity
Set a maximum quantity of products to be manufactured according to a recipe. The CS
Batch 1000/CS Batch 3000 does not have the scaling function supporting the maximum
production quantity.
Minimum Production Quantity
Set a minimum quantity of products to be manufactured according to a recipe. The CS
Batch 1000/CS Batch 3000 does not have the scaling function supporting the minimum
production quantity.
Security Level
Define the security level from 1 to 8 for the recipe. Downloading a control recipe or starting
a command is restricted by the security level. The default setting is security level 4.
SEE ALSO
For more information about security levels of recipe, see the following:
G3.7, Security Settings of Process Management
Recipe Download Mode
Select from the three modes: MAN, AUT, and TIME.
MAN: The recipe is downloaded to FCSs manually.
AUT: The recipe is downloaded to FCSs automatically upon completion of its
setup.
TIME: The recipe is downloaded to FCSs automatically at a time specified by the
production planning and scheduling function.
Recipe Start Mode
MAN: The recipe is started manually.
AUT: The recipe is started automatically upon completion of its downloading to
FCSs.
TIME: The recipe is started automatically at a time specified by the production
planning and scheduling function.
IM 33S01B30-01E
Data Items in Common Block
The following data items exist in a system-fixed common block, SYSRCM, and hence their
values can be displayed in a graphic window by referring to them using a SEBOL program
or using the batch ID as the key:
Recipe Name (RECIPE)
Engineering Unit (RCP_UNIT)
Recipe Standard Size (RCP_SIZE)
Maximum Size of Recipe (RCP_MAX)
Minimum Size of Recipe (RCP_MIN)
Recipe Download Mode (LOADMODE)
Recipe Start Mode (STRTMODE)
SEE ALSO
For details of system-fixed common blocks, see the following:
System-Fixed Common Block in G2.3, Common Block
IM 33S01B30-01E
G2.1.2 Procedure
The procedure is coded as an SFC and defines the procedure for manufacturing a product.
In the recipe management, the procedures are divided into Recipe Procedures and Recipe
Unit Procedures.
Recipe Procedure
Recipe procedure determines the order and relationships of recipe unit procedures. Each
step of a recipe procedure can be assigned with a recipe unit procedure.
A recipe unit procedure can not be executed from the step of the recipe procedure, so that
assigning a recipe unit procedure to a recipe procedure step can be omitted.
A recipe unit procedure can be executed by a SEBOL command in an operation, it can also
started from an operation and monitoring window.
G020105E.EPS
Unit
#1
#2
#3 #4
#5
Reaction B
Initialize
Charge
Reaction A
Mixture
1
2
3 4
5
Unit Procedure for Unit #1
Figure A Recipe Procedure
Recipe Procedure SFC
The differences of a recipe procedure and a unit procedure in unit instrument are as fol-
lows:
The first step can be a wait step
A step number of a recipe procedure can be different from the number of the recipe
unit procedure assigned to the step.
The transition condition, if scripted, is ignored during transition.
IM 33S01B30-01E
Defining a Recipe Procedure
When implementing a recipe procedure, the recipe procedure should be created first in
Recipe View. After creating the recipe, the recipe procedure can be edited on Procedure
builder.
Describing a recipe procedure is much similar to describing a unit procedure. However,
each step of the recipe procedure shall be defined with a unit recipe.
When defining the recipe is completed, the comment for the unit recipes defined to the
steps will be automatically set.
G020106E.EPS
Ready X=03,Y=01
Procedure Builder [Pjt:MYPJT Gr:RG01 Rcp:RCP0001 File:RcpPT01.edf]
No.
ATTR OUT
01 Initialize
02 Charge
03 Reaction A
Mixture
04 Reaction B
05
File Edit View Draw Tool Window Help
Figure Procedure Builder
SEE ALSO
For more information about creating recipe procedures, see the following:
G2.5, Recipe View
For more information about editing recipe procedures, see the following:
F6, Editing SFC
IM 33S01B30-01E
Recipe Unit Procedure
A recipe contains a unit procedure for each equipment entity (a unit). A recipe unit proce-
dure defines the sequence of operations to be completed in each unit. Up to 32 unit proce-
dures can be defined in each recipe.
Each step of a recipe unit procedure can be assigned with an operation.
The operations and the function blocks called by the operations can be generated on the
Control Drawing Builder or the Function Block Overview Builder.
The figure below shows an example of recipe unit procedure.
G020107E.EPS
Unit
#1
#2
#3 #4
#5
Supply additive Agitate
Initialize
Charge
Heat-up
Discharge
Cleaning
End
1
2
3 4 5
6
7
8
Unit Procedure for Unit #1
Figure A Recipe Unit Procedure
IM 33S01B30-01E
Defining a Recipe Unit Procedure
A recipe unit procedure can be defined on Procedure Builder.
Describing a recipe unit procedure is much similar to describing a unit procedure.
Each step of the recipe unit procedure shall be defined with an operation in the same FCS
for the procedure.
Procedure Builder [Pjt:MYPJT Gr:RG01 Rcp:RCP0001 File:RcpPT01.edf]
No.
ATTR OUT
01 Initialize
02 Charge
03 Heat-up 04 Supply additive
06 Discharge
07 Cleaning
05 Agitate
08 End
File Edit View Draw Tool Window Help
G020108E.EPS
Ready X=03,Y=01
Message
Figure Recipe Unit Procedure Builder
SEE ALSO
For more information about editing recipe unit procedures, see the following:
F6, Editing SFC
IM 33S01B30-01E
Defining Unit Recipes
Unit Recipe Comment, Unit Recipe Download Mode, Unit Recipe Start Mode
Define the actions of a unit procedure in the unit recipe.
The unit recipe can be set in the Unit Recipe tab of the Recipe Builder window. The follow-
ing items need to be set:
UnitRcpNo. Unit Recipe Comment Unit Recipe Download Mode Unit Recipe
1 UNIT1 Manual Manual
2 UNIT2 Manual Manual
3 Manual Manual
4 Manual Manual
5 Manual Manual
6 Manual Manual
7 Manual Manual
8 Manual Manual
Unit Recipe
Comment
File Edit View Tool Window Help
Unit Recipe
Comment
Recipe Header
G020109E.EPS
Ready
Message
Figure Unit Recipe Tab
Unit Recipe Comment
In this box, type the comment of up to 24 alphanumeric characters or twelve double-byte
characters for the unit recipe.
Unit Recipe Download Mode
MAN: The unit recipe is downloaded to FCSs manually.
AUT: The unit recipe is downloaded to FCSs automatically upon
completion of its setup.
TIME: The unit recipe is downloaded to FCSs automatically at a time
specified by the production planning and scheduling function.
IM 33S01B30-01E
Unit Recipe Start Mode
MAN: The unit recipe is started manually.
AUT: The unit recipe is started automatically upon completion of its
downloading to FCSs.
TIME: The unit recipe is started automatically at a time specified by the
production planning and scheduling function.
Download Destination of Recipe Unit Procedure
Each unit procedure in a unit recipe can be downloaded to a unit instrument (non-resident),
which then carries out the actions defined in the downloaded unit procedure.
The unit instrument where the recipe is downloaded may be created on the Control Draw-
ing Builder or on the Function Block Overview Builder.
Operation3
Operation2
G020110E.EPS
HIS
Download
FCS
Unit instrument (non-resident)
Operation1
Figure Download Destination of Recipe Unit Procedure
TIP
There are two types of unit instruments, resident type and non-resident type. A resident type unit instru-
ment may have a fixed procedure while a non-resident unit instrument does not. Thus, a recipe unit
procedure may only be downloaded to a non-resident type unit instrument in which no procedure is
resided.
IM 33S01B30-01E
G2.1.3 Formula
A formula, as defined in ISA S88.01, is a category of recipe information including the
process parameters. When setting up a recipe, the formula is downloaded and
stored in the common block in the FCS.
Formula and Common Block
There are two types of common blocks : user-defined common blocks and system-fixed
common blocks. The user-defined common blocks can be further deviled into three catego-
ries in accordance with their usage.
For the whole recipe (common to all units).
For a group of units (unit common block).
For a group of operations (operation common block).
The common blocks to be specified in the formula are user-defined common blocks. When
a recipe is set up, the user-defined common blocks specified in the formula and the sys-
tem-fixed common blocks are copied to the control recipe as part of the master recipe.
A common block can be accessed from an operation, SEBOL program, or operation and
monitoring window by using the batch ID as the key.
Common blocks can share a data area for all the unit recipes within the same recipe.
Hence, a common block is useful for sharing the same data among multiple sequences
and exchanging data between unit recipes.
The formula can be set so as to modify the default values of data in common blocks. Also,
the data values in common blocks can be modified when setting up a recipe by opening the
Formula dialog box. The data changes made when setting up the recipe are effective only
for the current production.
G020111E.EPS
HIS
Recipe
Formula
FCS
Unit instrument
Setting Referencing
Operation
Common blocks Common blocks
Download data to the
specified common blocks
via formula.
specifies
common
blocks
Figure Download of Formula
SEE ALSO
For details on batch ID, see the following:
Batch ID (Batch Identifier) in G3.2, Recipe Setup
For details on common blocks, see the following:
G2.3, Common Block
IM 33S01B30-01E
Unit Common Block and Operation Common Block
It will be more convenient for engineering or for operating and monitoring if designating a
common block and its array data to a specific unit or operation block. With unit common
block, the following features become available.
The formula data can be displayed in hierarchies on HIS, i.e., only the formula data
specific to the designated unit or operation can be displayed.
A common block can be treated as a parameter in unit recipe, and it is easier when
defining a formula or handling a block name.
IM 33S01B30-01E
Defining a Formula
Defining Formula
Set the formula in the Formula tab of the Recipe Builder. To configure unit common block or
to configure operation common block, the editing mode switching button on Recipe View
can be used. Before setting the formula, the common blocks to be specified must be
created in System View. If any one of the common blocks specified in the formula does not
exist in the HIS, an error occurs when the recipe is set up. The following items need to be
set for the formula.
SEE ALSO
For more information about unit common block and operation common block, see the following in the
later part of this chapter:
Editing Unit Common Block
No. Common Block Data Item Array1 Array2 Value Display
1 CHARGE SC1SV 0 0 20 Display at Recipe Setup and in
3 REACT1 R11SV 0 0 100 Display at Recipe Setup and in
4 R120SV 0 0 20 Display at Recipe Setup and in
5 R130SV 0 0 50 Display at Recipe Setup and in
Common Block
CHARGE: CHAR
REACT1: REAC
REACT2: REAC
REACT3: REAC
REACT4: REAC
SYSPCM01: #01
SYSPCM02: #02
SYSPCM03: #03
SYSPCM04: #04
SYSPCM05: #05
SYSPCM06: #06
SYSPCM07: #07
SYSPCM08: #08
SYSPCM09: #09
Recipe Header
G020112E.EPS
Ready
Message
Position: Line 1 Column 2
2 SCMAIN1 0 0 80 Display at Recipe Setup and in Common block name
is CHARGE.
Common block name
is REACT1.
Unit Common Block Edit Mode switching button
Figure Formula Tab
IM 33S01B30-01E
Common Block
Specify the name of a user-defined common block or system-fixed common block. If this
specification is omitted, the common block name on the previous row will be used.
When designating a common block without designating the data items, all the data items of
the common block will be taken by the formula. The default values specified on Common
Block Builder will be used as initial values.
Moreover, when a reference project is specified in the property sheet of the project in
Recipe View, the contents of the common blocks defined in Common Block Builder for the
project can be used. The details are shown as follows.
1. Choose [Get Common Blocks..] from [Tool] menu on Recipe Builder. A dialog box for
selecting a common block will appear.
2. Choose a common block name on the dialog box, the block will be used for holding
data in the formula. From the contents defined for common blocks, the data items that
the existing formula does not have, will be set to the formula.
Data Item
Specify the data item name, which must be defined in the common block using the Com-
mon Block Builder.
When a reference project is specified in the property sheet of the project in Recipe View,
the data items defined in Common Block Builder for the project can be used. The details
are shown as follows.
1. Specify a common block name for the formula on Recipe Builder.
2. Select the line the common block name is defined.
3. Choose [Get Items] from [Tool] menu on Recipe Builder. Then all data items defined in
Common Block Builder for the project will be set into the formula.
TIP
Multiple common block data items can be set to formula all together. In the above procedure step 3,
select multiple lines of data items, then choose [Get Items] from [Tools] menu on Recipe Builder, thus all
the data items will be set to the formula except the data items that the formula already have.
Array 1 and Array 2
If the data item specified is not an array, the default settings can be use. By default, Array 1
and Array 2 are set to zeros. If the data item specified is an array, the number of array
elements need to be specified.
IM 33S01B30-01E
Value
When initial value is different from the default setting in the common block, the value can be
set here. The data values can also be modified when setting up the recipe.
When entering a value of a datum, the data type is irrelevant to the [Data Type] specified on
the common block builder. However, entering a value to the datum with the type of [Result
Data], restriction may be applied to prevent from erroneous entry.
Do the following settings may apply the restriction on entering value to the datum with the
type of [Result Data].
1. On recipe builder, choose [Formula Settings] from [Tools] menu. A Formula Settings
dialog box displays.
Cancel To Default OK
G020118E.EPS
Protected data items when acquiring
Unit Common Block Information
Editing Result Data
Allowed
Not Allowed
Value
Display
Comment
Title
Formula Settings
Figure Formula Settings Dialog Box
2. On the Formula Settings dialog box, choose the option [Not Allowed] for the field of
[Editing Result Data].
IM 33S01B30-01E
Display
Specify whether to display the data items when setting up the recipe and in the Formula
dialog box. Select from NO, DATA, and AUTO. AUTO can be set for up to 512 data items
per recipe.
NO: The data item is not displayed when setting up the recipe or in the
Formula dialog box.
DATA: The data item is not displayed when setting up the recipe, but is
displayed in the Formula dialog box.
AUTO: The data item is displayed when setting up the recipe and in the
Formula dialog box.
The display status for data items in the Formula dialog box can also be specified in the
Common Block Builder. If data items are set not to be displayed using the Common Block
Builder, they will not be displayed in the Formula dialog box.
Note that if AUTO is specified for data items using the Recipe Builder, they will be displayed
in the Formula dialog box regardless of the settings in the Common Block Builder.
Comment
Type a comment of up to 16 alphanumeric characters or double-byte eight characters.
When a reference project is specified in the property sheet of the project in Recipe View,
the comment defined in Common Block Builder for the project can be used.
Select the data items for reflecting the comment. Then choose [Get Comments of Items]
from [Tool] menu on Recipe Builder. The comments defined in Common Block Builder will
be set into the formula.
Title
The title name can be defined for the formula dialog box when setting up a recipe. Up to 16
alphanumeric or 8 double-byte characters can be used.
When displaying the formula dialog with a title, the common block name and the data item
name should not be specified. If the common block name or data item name is specified,
the common block name or data item name will be displayed instead of displaying the title.
And the setting for Display should be AUTO.
IM 33S01B30-01E
Editing Unit Common Block
When editing the Formula tab, to configure a unit common block or to configure an opera-
tion common block can be switched.
Switching the editing mode can be performed by choosing [Unit Common Block Edit Mode]
on [Edit] menu of Recipe View or by clicking the Unit Common Block Edit Mode button on
Recipe View.
G020116E.EPS
Ready
UnitRcpNo.
UnitRcpNo.
No. UnitRcpNo. Operation Name Tag/Generic Operation ID Common Block Data Item Array 1 Array2
Message
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
1
2
0
0
0
0
0
1
1
1
1
1
1
1
1
2
2
2
2
0
0
0
0
0
0
0
1
1
2
2
3
3
0
0
1
1
CHARGE
REACT1
COMB01
COMB11
COMB12
COMB13
COMB01
COMB11
OP1011
OP1012
UGEN01
OP2011
1
2
3
1
Tag
Tag
Generic
Tag
SC1SV
SCMAIN1
R11SV
R120SV
R130SV
PICSV
TICSV
SETV1
ACTV1
SETV2
ACTV2
MV1
MV2
PICSV
TICSV
SETV1
ACTV1
Unit Recipe Formula Equipment Requirement (Train-Path) Equipment Requirement (Unit) Recipe Header
Unit Common Block Edit Mode switching button
Figure Switching Editing Mode of Formula Tab
Switching the editing mode of formula tab, the columns for defining unit recipe number,
operation name, tag and generic names and operation ID will be added.
By defining these items, a common block can be used as unit common block or an opera-
tion common block. By designating the unit common block, the part of the formula only for
the unit recipe running in the formula dialog box can be extracted and displayed.
IM 33S01B30-01E
Configuration Items of Formula in Unit Common Block Edit Mode
The configuration items of Formula in Unit Common Block Edit Mode are shown in the
following figure.
G020117E.EPS
Formula
No. UnitRcpNo. Operation Name Tag/Generic Operation ID Common Block Data Item
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
1
2
CHARGE
REACT1
COMB01
COMB02
COMB03
COMB04
COMB01
COMB02
OP1011
OP1012
UGEN01
OP2011
1
2
3
1
Tag
Tag
Generic
Tag
SC1SV
SCMAIN1
R11SV
R120SV
R130SV
PICSV
TICSV
SETV1
ACTV1
SETV2
ACTV2
MV1
MV2
PICSV
TICSV
SETV1
ACTV1
Common block configuration
for whole recipe
for a designated unit
for a designated unit
for a designated operation
for a designated operation
Unit recipe 1
Unit recipe 2
Unit recipe n
Common
Figure Configuration Items of Formula in Unit Common Block Edit Mode
The formula of a common block in Unit Common Block Edit Mode is scripted in the follow-
ing order.
Common block configuration for whole recipe (Common)
The configuration is the same as not in Unit Common Block Edit Mode.
Configuration for unit recipe 1
Configuration for unit recipe 2
:
:
Configuration for unit recipe n
IM 33S01B30-01E
Get Unit Common Blocks
The common blocks used by a unit (unit common blocks) or the common blocks used by an
operation (operation common blocks) can be collected all together, and automatically
entered to the configuration area of Formula.
To get the unit common blocks, choose [Get Unit Common Blocks] task on [Tools] menu of
the recipe builder.
When getting the unit common blocks by this way, all the information in the configuration
area of the formula will be erased before the collected blocks are entered. However, the
configuration of the formula for common part will be intact. Moreover, it is necessary to
define the unit common blocks and operation common blocks on unit common block
builder and to define unit recipe procedure on recipe procedure builder before performing
Get Unit Common Blocks.
SEE ALSO
For more information about unit common block builder, see the following:
Configuring Unit Common Block and Operation Common Block in G2.3, Common Block
For more information about how to define recipe unit procedure, see the following:
Defining a Recipe Unit Procedure in Recipe Unit Procedure in G2.1.2, Procedure
Protected Data Items when Acquiring Unit Common Block Information
When acquiring the unit common block information for the first time, the items of Value,
Display, Comment and Title are all set with the data obtained from the common block.
When acquiring the unit common block information for the second time, the data of the
above items are overwritten by the data obtained from the unit common block (by default
action).
However, with the following settings, the data of the above data items can be protected
from overwritten by the obtained unit common block information.
1. On recipe builder, choose [Formula Settings] from [Tools] menu. A Formula Settings
dialog box displays.
Cancel To Default OK
G020119E.EPS
Protected data items when acquiring
Unit Common Block Information
Editing Result Data
Allowed
Not Allowed
Value
Display
Comment
Title
Formula Settings
Figure Formula Settings Dialog Box
2. On the Formula Settings dialog box, check the items to be protected from the obtained
unit common block information.
IM 33S01B30-01E
G2.1.4 Equipment Requirements
Equipment requirements constrain the choice of the equipment that will eventually be used
to implement the procedure for manufacturing the products. There two types configura-
tions, Train-Path and Unit for defining the Equipment Requirements.
Defining Equipment Requirements Train
Train Name, Path Name
When using train or path for equipment requirements configuration, the train or the path
needs to be configured first on the Train Builder. When a train or a path is defined here for
equipment requirements, the unit and the unit recipe previously assigned to the train or the
path will be set for equipment requirements.
A wildcard (*) can be used for specifying a train or a path. When the wildcard (*) is used, all
the trains and all the paths defined in the recipe group can be used. However, a wildcard
character can be used at the end of the string of a Train Name or a Path Name.
SEE ALSO
For details of Train and Path, see the following:
G2.2, Recipe Group and Train
Train Name
LINE1: Train1
LINE2: Train2
Recipe Header
G020113E.EPS
Ready
Message
No. Train Name Path Name
1 LINE1 PASS1
2 PASS2
3 PASS3
4 LINE2 *
5
6
7
8
9
Figure Equipment Requirements (Train-Path) Tab
IM 33S01B30-01E
Defining Equipment Requirements Unit
Unit
The equipment requirements indicate equipment units to be used for manufacturing the
product. Unit name can be specified if the train and path are not used. In the equipment
requirements, the names of the units, i.e., the tag names of the non-resident unit instru-
ment blocks created on the Control Drawing Builder or on the Function Block List Builder
may be specified as the unit names for the unit recipe. Up to 16 units can be set for each
unit procedure and each recipe may contain up to 32 unit recipes.
When setting up a recipe, the unit name for equipment requirements needs to be selected
from the menu. If hyphen (-) is set as the unit name, it stands for a dynamic assignment.
Dynamic assignment allows operator to specify the unit name before the unit recipe starts.
A dynamic assignment can be specified for the second and subsequent unit recipes.
If the unit names are left blank (all units 1 to 16), the direct unit name specification for the
during the recipe setup.
SEE ALSO
For details of dynamic unit assignment, see the following:
Dynamic Unit Assignment in G3.2, Recipe Setup
Unit Recipe Formula (Train-Path)
G020114E.EPS
Unit1
UT0101
UT0102
UT0103
UT0201
UT0202
Recipe Header
UnitRcpNo. Unit Recipe Comment Unit1 Unit2 Unit3
1 UNIT RECIPE1 UT0101 UT0102
2 UNIT RECIPE2 - UT0201 UT0202
3 UNIT RECIPE3
4
5
6
7
8
Equipment Requirement (Unit)
Ready
Message
Direct specification
Select from unit menu
Figure Equipment Requirements (Unit) Tab
IM 33S01B30-01E
G2.1.5 Handling Master Recipe File
The File menu in the Recipe Builder window and Recipe Procedure Builder window
contains the following commands for handling a master recipe file:
Saving a File
Save
Saves the new master recipe or saves the changes you made in an existing master recipe,
without checking the contents.
Save As...
Use this command to save a currently opened master recipe file as a different master
recipe file (*.sva). The file is saved under the specified name and in the specified location
without checking the contents.
Build
Build
Saves the new master recipe or saves the changes you made in an existing master recipe,
and checks the contents. If no error is found, the master recipe file to be downloaded to the
master server is created. The master recipe is saved regardless of whether there is an
error.
Download
Download
Use this command after the master recipe file is created correctly by the Build command.
Selecting Download opens a dialog box for downloading the master recipe file to the
master server.
TIP
The master server is defined for each recipe group using the Process Management Configuration Builder
and Recipe Builder.
IM 33S01B30-01E
External File Recipe Builder
In Recipe Builder, files can be handled as follows.
Default
Using [Create Default File] on [Tool] menu may create a default file. Otherwise, the system
default file will be used when opening a default file.
Import
The builder file (*.edf) and the file saved in a different name (*.sva) can be imported.
In Recipe Builder, the data for Recipe Header, Unit Recipe, Formula, Equipment Require-
ments (Train-Path) and Equipment Requirements (Unit) can all be imported.
Import CS Source File
The master recipe source file (*.s) created in CS Batch can be imported.
Import Formula
An eternal file can be imported for the contents configured on Formula tab. Only the CSV
format file (*.csv) can be imported.
Export Formula
The contents configured on Formula tab can exported into an external file in CSV format
(*.csv). Only the configured contents can be exported.
External File Recipe Procedure Builder
In Recipe Procedure Builder, files can be handled as follows.
Default
Using [Create Default File] on [Tool] menu may create a default file. Otherwise, the system
default file will be used when opening a default file.
Import
The builder file (*.edf), the file saved in a different name (*.sva) and the text file (*.txt) can
be imported.
Export
The contents can exported to an external file in text format (*.txt).
Import CS Source File
The master recipe source file (*.s) created in CS Batch can be imported.
G2-28 <G2.2 Recipe Group and Train>
IM 33S01B30-01E
G2.2 Recipe Group and Train
Recipe group and train are implemented for controlling the control recipes.
Recipe Group
Recipe Group Number, Recipe Group Comment, Recipe Comment
Recipes are managed in units called recipe groups. Up to 16 recipe groups can be used.
Recipe groups are divided into equipment units and product line units when used. Dividing
recipes into groups makes it easier to manage the recipes and prevents wrong recipes
unrelated to the production from being downloaded by mistake.
Since master recipes and control recipes are managed in recipe groups, there are no
recipes that belong to more than one recipe group. The diagram below shows how recipes
are positioned in recipe groups:
G020201E.EPS
Project
Master recipe Control recipe
Recipe group 1
Master recipe Control recipe
Recipe group 16
Figure Structure of Recipe Groups
Creating Recipe Groups
The recipe of the group 1 exists by default. A new recipe group can be created via the
System View.
When creating a recipe group, the dialog box to set the group number and comment
appears.
Recipe group number
Set the group number in the range of 1 to 16.
Recipe group comment
Define the recipe comment with up to 32 single-byte or 16 double-byte characters.
IMPORTANT
You must enter a recipe group comment to create a recipe group.
<G2.2 Recipe Group and Train> G2-29
IM 33S01B30-01E
Train
A train stands for a bunch of physical devices and equipment entities applied in the recipe
group.
Based on the train, the units can be grouped. When defining a train, the control recipes are
managed in recipe group and train.
When using train to manage the equipment requirements, the combinations of units in a
train (path) may be set beforehand and then assigned.
When omitting the train configuration, the equipment requirements will use the unit name
specified for each unit recipe.
The relationship of recipe group and train is shown as follows.
G020202E.EPS
Recipe Group1
UNIT-A1
UNIT-A2
UNIT-A3
Train A
UNIT-B1
UNIT-B2
UNIT-B3
Train B
UNIT-C1
UNIT-C2
UNIT-C3
Train C
Recipe Group
1 to 16
Figure Recipe Group and Train
IM 33S01B30-01E
Defining a Train
Train, Train Comment
Up to 16 trains can be defined in a recipe group.
Path
G020203E.EPS
Train Builder [Pjt:MYPJT Gr:RG01 File:TrainName.edf]
Ready
Train
Train
No. Train1 Train Comment
01 TRAIN1 TRAIN1
02 TRAIN2 TRAIN2
03
04
05
06
07
08
09
Message
Figure Train Builder (Train Tab)
Train
Up to 16 alphanumeric capital characters can be used to define a train name. Hyphen
[-] can also be used, however, the train name must be started by an alphabet. The
train names in the recipe group should not be identical.
Train Comment
Up to 24 alphanumeric or 12 double-byte characters can be used for defining the train
comment.
<G2.2 Recipe Group and Train> G2-31
IM 33S01B30-01E
Path
Similar as a train stands for a bunch of physical devices, a path stands for a group of units
assigned for the implemented unit recipe.
A path structure is a group of units connected in sequence or in parallel for implementing
the recipe. In a path, each unit recipe is assigned with a unit name.
When setting up a recipe, by selecting train or path, the pre-set unit recipe and unit can be
assigned.
The units used for the path can be defined on Train Builder. By setting the train name and
path name on the Equipment Requirements tab of Recipe Builder, the train or the path can
be selected during the recipe setup.
The relationship of train and path is shown as follows.
G020204E.EPS
UNIT-A1
UNIT-A2
UNIT-A3 UNIT-B3
UNIT-A4 UNIT-B4
Unit Recipe#1
Unit Recipe#2
Unit Recipe#3
Unit Recipe#4
Path A Path B
Train
Figure Relationship of Train and Path
IM 33S01B30-01E
Defining Paths
Train, Path, Path Comment, Unit Recipe1 to 32
Up to 64 paths can be defined for one train.
Path
G020205E.EPS
Train Builder [Pjt:MYPJT Gr:RG01 File:TrainName.edf]
Ready
Train
Train
No. Train Path Path Comment Unit Recipe1 Unit Recipe
01 TRAIN1 PATH1-1 Path1-1 UT0101 UT0201
02 PATH1-2 Path1-2 UT0101 UT0202
03 PATH1-3 Path1-3 UT0101 UT0203
04 TRAIN2 PATH2-1 Path2-1 UT0102 UT0201
05
06
07
08
09
Message
Figure Train Builder (Path Tab)
Train
A train name can be selected on Train tab. When train name is omitted, the train used
in the previous row will be used.
Path
Path name can be defined with up to 16 capital case alphanumeric characters and a
hyphen (-). However, the path name must be started with an alphabet letter. The path
names in a train can not be identical.
Path Comment
Up to 24 alphanumeric or 12 double-byte characters can be used for defining the path
comment.
Unit Recipe 1 - 32
The name of units assigned for each unit recipe can be defined.
A tag list of the non-resident unit instruments defined in the project will display. If the
unit name consists a hyphen (-) then perform dynamic unit assignment. The dynamic
unit assignment may designate a unit before the execution of the unit recipe. Dynamic
unit assignment may be applied to the unit recipes from the second.
SEE ALSO
For more information about dynamic unit assignment, see the following:
<G2.3 Common Block> G2-33
IM 33S01B30-01E
G2.3 Common Block
Common block is used to hold the processing data of recipes, unit recipes as well
as operations. Common means this block holds the shared data for all unit recipes
under the same recipe. Thus, the data in the common block may be shared by differ-
ent operations and the data may be used as intermediate signal for data exchange
among unit recipes.
Common Block and Formula
In a formula, the common block for the control recipe is required to be specified. There are
two types of common block, system-specific common block and user-defined common
block. The common block may be specified in formula is user-defined type. During the
recipe setup, the user-defined common block data items are copied together with the
system-fixed common block to the control recipe as part of the master recipe. Downloading
the recipe and the unit recipe will also download the common blocks to the FCS as part of
the recipe.
Thus, the common blocks required for the control recipe must be predefined on the com-
mon block builders. The initial set value of user-defined common block may be changed via
formula during the recipe setup.
Common Block Configuration
There are two types of common block, system-fixed common block and user-defined
common block. User-defined common block may be numbered from 1 to 949 while system-
fixed common block is numbered from 950 to 1000.
Up to 256 data items may be defined to one common block.
G020301E.EPS
.
.
.
.
.
.
Common Block
Common Block Number 1000
User-defined common block
System-fixed common block
Figure Common Block Configuration
G2-34 <G2.3 Common Block>
IM 33S01B30-01E
System-Fixed Common Block
There are two types of system-fixed common block, system-fixed common block for recipe
and system-fixed common block for unit recipe.
System-fixed common block has block name and data items. The block names of system-
fixed common blocks can not be used for user-defined common blocks.
For system-fixed common blocks, only the comment text for the data items can be changed
by user.
System-fixed common block is indispensable for the Process Management running on an
HIS. So that, it is required to download the common block configuration generated on
builders to the HIS before recipe setup. To download to HIS, choose [COMMON_BLOCK]
folder inside the [BATCH] folder on folder tree of System View, then click [Download Com-
mon Block] on [Load] menu of System View.
IM 33S01B30-01E
System-Fixed Common Blocks for Recipe
The system-fixed common block for recipe administrates the management information of
whole recipe, its number is fixed at 950. Its block name is SYSRCM.
The following table shows a list of data item of the system-fixed common block for recipe.
Table Data Item List - System-fixed Common Block for Recipe
G020302E.EPS
Item Name Description Data type Security level
RECIPEGR Recipe group number I16 4
RECIPE Recipe name CHR16 4
BATCHID Batch ID CHR16 4
STATUS Recipe status CHR8 1
MODE Recipe mode CHR8 8
MAXPART Unit recipe number I16 4
RSVTIME Reserved data and time U32 4
TRAIN Name of train CHR16 4
PATH Path name CHR16 4
PLANT Plant name CHR8 4 (*1)
MASTER Basic recipe number CHR16 4
SYSTEM1 Original recipe batch ID CHR16 4
SYSTEM2 System code 2 CHR16 1 (*1)
LOADMODE Download mode CHR8 4
STRTMODE Start mode CHR8 4
USER1 User code 1 CHR16 1
STRTIME Date and time execution are started U32 4
ENDTIME Date and time execution are ended U32 4
STRSTIME Scheduled time to start execution U32 1
ENDSTIME Scheduled time to end execution U32 1
FORMAT Batch-report format CHR16 1
SCHEDULE Scheduled value CHR16 1
OPECOMNT Operator comment CHR16 4 (*1)
DMYCOMNT Dummy comment CHR16 6 (*1)
MESSAGE Maximum number of message I16 4 (*1)
SCHEDTIME Rescheduled time and date U32 4
RP_TREND [4] Acquired trend window name CHR16 1
RCP_SIZE Standard recipe size F64 4
RCP_MAX Maximum recipe size F64 4
RCP_MIN Minimum recipe size F64 4
RCP_UNIT Recipe engineering unit CHR16 4
*1: System reserved
IM 33S01B30-01E
System-Fixed Common Blocks for Unit Recipe
The system-fixed common block for unit recipe corresponds to each unit recipe and admin-
istrates the information of the unit recipe. The system-fixed common block for unit recipe
may be numbered from 951 to 982, and the block names are fixed at SYSPCM01 to
SYSPCM32. 01 to 32 stands for the unit recipe numbers. For example, the system-fixed
common block name for unit recipe #1 is SYSPCM01.
The following table shows a list of data item of the system-fixed common block for unit
recipe.
Table Data Item List - System-fixed Common Block for Unit Recipe
Item Name Description Data type Security level
STATUS Unit recipe status CHR8 1
LOADMODE Download mode CHR8 4
STRTMODE Start mode CHR8 4
PARTNO Unit recipe number I16 4
MODE Unit recipe mode CHR8 8
UNITNAME Assigned unit name CHR16 4
STRTIME Date and time execution are started U32 4
ENDTIME Date and time execution are ended U32 4
STRSTIME Scheduled time to start execution U32 1
ENDSTIME Scheduled time to end execution U32 1
FORMAT Batch-report format CHR16 1
SCHEDULE Scheduled value CHR16 1
RP_TREND [4] Acquired trend window name CHR16 1
RP_TGWID Reference pattern display window name CHR16 1 (*1)
RP_TGREF Reference pattern file name CHR16 1 (*1)
G020303E.EPS
*1: System reserved
Date and Time Format
When setting the execution scheduler, the date and time entered to the common block date
and time data item should obey the following format.
YYMMDDHHMM
G020304E.EPS
Minute
Hour
Day
Month
Year(Last Two Digits)
Example:
For 13:30 September 14th, 2001
Enter: 0109141330
IM 33S01B30-01E
User-Defined Common Block
A user may define user-defined common blocks as desired. User-defined common blocks
consist of three types, common block for the whole recipe (common to all units), common
block for a designated unit or common block for a designated operation. The common
block for a designated unit is called unit common block and the common block for a desig-
nated operation is called operation common block. A user-defined common block can be
created on System View, the common block data items can be defined on Common Block
Builder.
Create a New User-Defined Common Block
Common Block Number, Common Block Name, Common Block Comment
Select the COMMON_BLOCK folder in the left pane of the system view. Then select Create
New -> Common Block from the File menu. A dialog box for creating a new common block
displays. On the dialog box, the common block number, common block name and common
block comment may be defined. The dialog box for creating a new common block is as
follows.
Cancel
G020305E.EPS
Create new common block
Generation target Detailed Setting
Common Block Name REACTOR
Common Block Comment REACTOR COMMON BLOCK
OK
Figure Example of the Dialog Box for Creating a New Common Block
Common Block Number
Common block number may be set from 1 to 949. The number 950 to 1000 are
reserved for the system-fixed common blocks, can not be used for user-defined
common blocks.
Common Block Name
Common block name may be set using up to 8 alphanumeric characters and under-
score [_], however, it must begin with an alphabet letter. The block names reserved for
system-fixed common blocks (SYSRCM, SYSPCM01 to SYSPCM32) can not be
used.
Common Block Comment
Common block name may be defined using up to 24 alphanumeric characters or 12
double-byte characters.
The files RDT0001 to RDT0949 will be created corresponding the creation of the user-
defined common blocks.
IM 33S01B30-01E
Common Block Data Array Elements
Array Number Correspondence
On Detailed Setting tab of Create new common block dialog box, the common block array
data elements can be defined with the following settings.
No Correspondence
Unit Recipe Number
Operation ID
By defining the array elements to the common block data item, the item will be linked by
either unit recipe number or operation ID. For the common block data items that do not hold
array data, this definition is invalid. For the common block data items that only hold one-
dimensional array data, only one array element, Array1, can be defined. Array2 becomes
invalid.
Cancel
G020306E.EPS
Create new common block
Generation target Detailed Setting
No Correspondence
OK
Array 1
No Correspondence
Array 2
Figure Detailed Setting Tab of Create New Common Block Dialog Box
Defining Common Block Data Item
Defining Common Block Data Item
On the Common Block Builder, the following items need to be defined.
Data Item
Up to 8 capital case alphanumeric characters and the underscore [_] can be used for
defining a name of data. However, the name must begin with an alphabet letter.
Data type
Specify the data format. The following data types are available for use with common
blocks. However, no data status is assigned to common blocks.
I16: 16-bit signed integer
I32: 32-bit signed long integer
F32: 32-bit single-precision floating-point real number
F64: 64-bit double-precision floating-point real number
CHR2-16: character string data with 2 to 16 bytes of characters
IM 33S01B30-01E
Array1, Array2
If the array element is not applied, the default settings may be used, i.e., the array1
and array2 are left as zeros.
When the array is required, array1 may be defined between 1 and 999 if the array is
one-dimensional, while the array2 is left as zero. The total arrayed elements (array1 x
array2) should be less than 10,000. The maximum buffer size for array data is 32
Kbytes.
Comment
Specify data item comment with up to 16 single-byte characters or 8 double-byte
characters.
Data check method
Select from Entry, No Entry or Entry with Acknowledgment. When Entry or Entry with
Acknowledgment is selected, the high/low limit values may be specified. If [Entry with
Acknowledgement] is checked, when entering a datum, a dialog box displays prompt-
ing the user for the password to confirm the entered datum.
Double Authentication
Activates or deactivates the double authenticated confirmation dialog box for data
entry.
Engineering unit symbol
Specify the engineering unit symbol to be appended to the data.
Security level
Specify the data security level from 1 to 8. Operations allowed for the specified secu-
rity level are those specified in the Security Builder.
Entry Method
Specifies the data entry method. The entry method include Direct Input, Menu Label,
Menu Data and Menu Number. The Menu Label input uses character type data, while
the Menu Number input uses integer type data.
When the entry method is defined as Menu Label, Menu Data or Menu Number, the
definition may be carried out by selecting a value from the displayed menu.
Display Format
Specify the data display format in the window. The default display format varies
depending on the data type.
For data of I16 and I32 types, the default is 7 (7 digits for the integer section).
For data of F32 and F64 types, the default is 7.1 (7 digits for the whole string and 1
digit for the fraction section after decimal point).
The number of digits for CHR* data corresponds to the length of character string
indicated by *.
Display, Yes/No
Specify whether or not to display data items in the formula dialog box.
The display status for data items in the formula dialog box can also be specified in the
Recipe Builder. Regardless of settings in the Common Block Builder, data items are
displayed during the recipe setup and in the formula dialog box if such a setting has
been made using the Recipe Builder.
Data Category
Specify the category that the data belongs. Data Category may be selected from
Setpoint Value, Parameter, and Result Data.
Initial value
This initial value is used when a recipe is created. In the case of array data, the same
value is set for all elements. The number of digits is not checked.
High limit value/low limit value
Specify the high limit and low limit value for entered data. The high/low limits can be
defined only when Data check method is defined as Entry or Entry with Acknowledg-
ment.
IM 33S01B30-01E
Configuring Unit Common Block and Operation Common Block
Tag Name, Generic Name, Common Block 1 to 4
A unit common block or an operation common block can be configured on the unit common
block builder. After configuring a common block for a unit, or after configuring a common
block for an operation, the following operations become available.
Run [Get all common blocks] when defining a formula on Recipe View.
When displaying common block data in the formula dialog box, data of the designated
common block can be extracted for display.
Starting Unit Common Block Builder
Select [BATCH] folder from folder tree of System View, and then click a file named
[UnitCommonBlk] in client area. The unit common block builder starts.
Operation Operation generic name
G020307E.EPS
Unit Common Block Builder - [Pjt:MYPJT File:UnitCommonBlk.edf]
Ready
Tag Name
UT101
UT102
UT103
UT201
UT202
UT203
UT301
UT302
UT303
UT401
Unit
No. Tag Name Common Block1 Common Block2 Common Block3 Common Block4
Message
1
2
3
4
5
6
UT101
UT201
UT301
UT302
UT303
UT401
COMB01
COMB01
COMB01
COMB01
COMB01
COMB01
COMB02
COMB02
COMB02
COMB02
Figure Unit Common Block Builder
Components of Unit Common Block Builder Window
There are three tabs, [Unit], [Operation] and [Operation generic name], in unit common
block builder window.
Unit Tab
Unit instruments and the common blocks to be used by the unit instruments can be
defined on this tab. Four common blocks can be assigned to one unit instrument.
Operation Tab
Operations and the common blocks to be used by the operations can be defined on
this tab. Four common blocks can be assigned to one operation.
Operation Generic Name Tab
When an operation is shared, the common blocks used by the operation can be
defined. Four common blocks can be assigned to one operation.
IM 33S01B30-01E
Access to Common Block
The SEBOL functions for accessing common blocks are listed as follows.
Access to Common Block Data
The following built-in functions may be used to access the common block data:
lcmread
This function is used when reading the I16 and I32 type common block data.
dcmread
This function is used when reading the F32 and F64 type common block data.
ccmread
This function is used when reading the CHR2-16 type common block data.
SEE ALSO
For details on syntax of lcmread, dcmread and ccmread statements, see the following:
Reading Common Block Data in H1.6.1, Accessing Common Block Data
Setting Common Block Data
The following built-in functions may be used for setting common block data:
cmwrite
This function is used when setting the numeric type and character string type common
block data.
SEE ALSO
For details on syntax of cmwrite statement , see the following:
Writing Common Block Data in H1.6.1, Accessing Common Block Data
IM 33S01B30-01E
Access to Common Block Data by Specifying Batch ID
The following built-in functions may be used to access the common block data by specify-
ing its batch ID:
lcmreadbid
This function is used when reading the I16 and I32 type common block data.
dcmreadbid
This function is used when reading the F32 and F64 type common block data.
ccmreadbid
This function is used when reading the CHR2-16 type common block data.
SEE ALSO
For details on syntax of lcmreadbid, dcmreadbid and ccmreadbid statements, see the following:
Reading Common Block Data (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
Setting Common Block Data by Specifying Batch ID
The following built-in functions may be used for setting common block data:
cmwritebid
This function is used when setting the numeric type and character string type common
block data.
SEE ALSO
For details on syntax of cmwritebid statement , see the following:
Writing Common Block Data (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
<G2.4 Engineering of Unit Common Block> G2-43
IM 33S01B30-01E
G2.4 Engineering of Unit Common Block
Common blocks consist of system-fixed common blocks and user-defined common
blocks. Furthermore, a user-defined common block can be for the whole recipe (unit
common) or for a specific unit or a specific operation. Thus the common block for a
specific unit is referred to as Unit Common Block while the common block for a
specific operation is referred to as Operation Common Block.
In this chapter, the implementation and engineering of the unit common blocks and
operation common blocks are explained. Hereinafter, both unit common blocks and
operation common blocks are referred to as unit common blocks unless to distin-
guish the two types of common blocks is necessary.
TIP
A batch process can be operated and monitored without using the unit common blocks or operation
common blocks. However, with the unit common blocks and operation common blocks, the relationship
between a unit, an operation and a formula is clearer, so that it is more convenient for operating and
monitoring the batch process. And it is also convenient for batch project engineering.
G2-44 <G2.4 Engineering of Unit Common Block>
IM 33S01B30-01E
Flow of Unit Common Block Engineering
Unit common block engineering works are performed on both System View and Recipe
View. In the following figure, the engineering workflow is illustrated.
G020401E.EPS
Engineering on System View
Engineering on Recipe View
Defining Unit Instrument
Defining Generic Names for the Operations
in the Unit Instrument
Defining Operation
Defining Common Blocks
Defining Array Elements of Common Blocks
Defining Unit Common Block
Defining Operation Name
Defining Equipment Requirement Unit Name
Acquiring Unit Common Block Information
End Unit Common Block Engineering
Start Unit Common Block Engineering
Figure Flow of Unit Common Block Engineering
IM 33S01B30-01E
G2.4.1 Engineering on System View
In this section, engineering works using System View are explained. Engineering on
System View consists of the following engineering works.
Defining unit instrument, defining generic names for the operations in the unit instru-
ment and defining operation
Defining common blocks and defining array elements of common blocks
Defining unit common block
Defining unit instrument, defining generic name for the operation in the
unit instrument and defining operation
Unit instruments and operations can be defined on the Control Drawing Builder. The
operation generic names are defined on Function Block Detail Builder in a non-resident unit
instrument. If the operation generic name is not required, defining the operation generic
name becomes unnecessary.
Tag generic
Function Block Detail Builder - [Pjt:MYPJT Stn:FCS0101 Draw:DR0001 File:UT101.edf - Generic name definition]
G020402E.EPS
Edit Window Generic name definition
Operation generic
name
Operation generic name
1
2
3
4
5
6
Operation generic name Tag Name No.
Ready
OPGEN1
OPGEN2
OPGEN3
OPGEN4
OPSFC01
OPSFC02
OPSFC03
OPSFC04
Position: Line 4 Column 2 Change
Figure Defining Generic Names for the Operations in the Unit Instrument
Defining Common Blocks, Defining Array Elements of Common Blocks
Common blocks can be defined on Common Block Builder. Create a new user-defined
common block on System View, then define the data items of the common block on Com-
mon Block Builder. Common block array elements can be defined on the Detailed Setting
tab on common block properties sheet after creating the common block. The common
block array elements can be defined when the common block is newly created or later.
SEE ALSO
For more information about defining common blocks, see the following:
User-Defined Common Block in G2.3, Common Block
IM 33S01B30-01E
Defining Unit Common Block
Unit common block can be defined on Unit Common Block Builder. Though when to define
the unit common block is not important, it is convenient to select the unit common block
from a list if defining the tag name of the non-resident unit instrument and tag name of the
operation with the common block name in accordance with the procedure illustrated in the
figure Flow of Engineering.
SEE ALSO
For more information about defining unit common blocks, see the following:
Configuring Unit Common Block and Operation Common Block in G2.3, Common Block
IM 33S01B30-01E
G2.4.2 Engineering on Recipe View
In this section, engineering works using Recipe View are explained. Engineering on Recipe
View consists of the following engineering works. There is no requirement to perform the
works in a fixed order.
Acquiring All Unit Common Blocks
On the Recipe Procedure Builder of Recipe View, a name can be defined for an operation.
Ready X=05,Y=02
Procedure Builder - [Pjt:MYPJT Gr:RG01 Rcp:RCP0001 File:RcpPT01.edf]
No.
ATTR OUT
01 First
03 Heating 04 Heating
08
05 Add Additive 06
Message
File Edit View Draw Tools Window Help
This procedure consists of
additive related steps. 02 Charge
G020403E.EPS
Cancel OK
Step Attribute
2
Charge
2
OPGEN2
Step
Comment
Operation ID
Operation Name
Initial Step
Step Information
Operation Definition
Generic Name Tag Name
Figure Defining an Operation Name
On Equipment Requirements (Unit) tab of Recipe Builder, the tag name of unit instrument
can be defined.
SEE ALSO
For more information about Equipment Requirements, see the following:
Defining Equipment Requirements Unit in G2.1.4, Equipment Requirements
IM 33S01B30-01E
Acquiring Unit Common Block Information
When engineering on System View, such as defining operation name, defining equipment
requirement unit name are completed, acquiring whole unit common block information can
be performed.
By acquiring unit common block information, the common blocks used by the recipe will be
automatically defined into formula. The common blocks which have not been defined as
unit common block (i.e. the common blocks are not linked to units or operations) need to be
defined into formula manually.
SEE ALSO
For more information about acquiring unit common block information, see the following:
Editing Unit Common Block in G2.1.3, Formula
Processes of Acquiring Unit Common Block Information
When acquiring unit common block information is performed, the following processes take
place to the defined units.
1. When acquiring unit common block information is performed, the unit common blocks
whose tag names are defined in the Equipment Requirements (Unit Name), the
information of the unit common blocks will be taken into formula.
2. To find operation name and distinguish it between the tag name and generic name in
the unit recipe procedure, then pick up the operation ID.
When the operation name is indicated by a tag name:
If a unit common block is defined to correspond to the tag name, the unit common
block information will be acquired and put into the formula.
When the operation name is indicated by a generic name:
If a unit common block is defined to correspond to the generic name, the unit common
block information will be acquired and put into the formula. If not defined, the operation
name can be acquired from unit name or generic name. After defining a unit common
block to correspond to the operation name, the unit common block information will be
acquired and put into the formula.
3. When putting the acquired unit common block information in the formula, the data
items names are also acquired from the unit common block. If the array elements are
defined for an array, the elements defined with item names will be acquired and put
into the formula.
TIP
When acquiring unit common block information, the unit recipe procedure file is accessed. To define
operation name on the Unit Recipe Procedure Builder, it is necessary to click [Save] to store the
defined contents in the file.
When acquiring unit common block information, many builder files are accessed when acquiring is
started. When any of the builder files is modified, the acquiring unit common block information should
be performed again.
IM 33S01B30-01E
An Illustration of Acquiring Unit Common Block Information
An illustration of acquiring unit common block information is shown as follows.
G020404E.EPS
Tag Name Common Block 1 Common Block 2 Common Block Common Block 4
Tag Name Common Block 1 Common Block 2 Common Block Common Block 4
Generic Name Common Block 1 Common Block 2 Common Block Common Block 4
UT001
UT002
COM1
COM4
COM2
COM5
COM3
Unit Tab
Unit Common Block Builder
OPSFC1
OPSFC2
COM1
COM3
COM2
COM4 COM5
Operation Tab
GEN_A
GEN_B
COMA
COMD
COMB
COME
COMC
Creating New Common Block Dialog Box
(Common Block Properties)
Array 1 Array 2
COM1
COM2
Unit Recipe Number
No Correspondence
Operation ID
No Correspondence
Common Block
Name
Detailed Setting Tab
Function Block Detail Builder
Defining Unit Instrument Generic
Name
Operation
Generic Name
Tag Name
UT002
GEN001
GEN002
OPHWT
OPSFC2
Engineering on
System View
Engineering on
Recipe View
Recipe Builder
UnitRcpNo. Unit Recipe Comment Unit 1 Unit 2 Unit 3 Unit
1
2
UT001
UT002
UT011 UT021
Equipment Requirements (Unit) Tab
UnitRcpNo. Operation Name Tag/Generic Operation ID Common Block Data Item Array1 Array 2
2 0
0
0
2
0
0
0
0
0
0
1
0
0
0
COM4
COM5
COM1
COM2
COM3
COM4
COM5
OPSFC1
GEN002
1
1
Tag
Generic
ITEM1
ITEM2
ITEM1
ITEM2
Formula Tab
1
2
3
Operation Name : GEN002
Operation ID : 1
Tag Name /
Generic Name : Generic Name
Operation Name : OPSFC1
Operation ID : 2
Tag Name /
Generic Name : Tag Name
Operation Name : OPSFC1
Operation ID : 1
Tag Name /
Generic Name : Tag Name
Recipe Procedure Step Attribute
Recipe Procedure Builder
(B3) (B4)
(C5) (B2) (A2)
(A1) (C2)
(C4)
(C3)
(C1) (B1)
Figure An Illustration of Acquiring Unit Common Block Information
IM 33S01B30-01E
Acquiring unit common block information undergoes the following processes in each unit
recipe. An example of Unit Recipe Number 2 is explained as follows.
1. On Equipment Requirements (Unit) tab, unit recipe number 2 corresponds to the unit
UT002 is acquired. (A1)
2. The COM4, COM5 parameters of UT002 unit are acquired from the settings on unit
common block builder, then put into formula. (A2)
3. The operation OPSFC1 of UT002 unit is acquired from recipe procedure, then put into
formula. (B1)
4. The COM1, COM2 parameters of OPSFC1 operation are acquired from the settings
on unit common block builder, then put into formula.(B2)
If the arrays are defined, open the corresponding data items in the common block.
Then import the required data items to the formula in accordance with definitions of
the arrays. (B3)(B4)
5. The other operation GEN002 is acquired from recipe procedure, then put into formula.
(C1)
6. Search for the generic name parameters of the operation with generic name of
GEN002 from the settings on the unit common block builder. If the GEN002 param-
eters are defined, the parameters will be acquired and put into formula. Then move to
the next operation. However, in this instance, GEN002 does not have generic param-
eters defined in the builder. (C2)
7. If the above step (step 6) can not find the generic parameters, the generic name
settings for the unit instrument should be manually inspected. In this instance, an
operation OPSFC2 defined for GEN002 generic name can be found.(C3)
8. Re-access the operation parameters COM2,COM4 and COM5 of OPSFC2 on the
common block builder, then import the definitions into the formula.(C4)(C5)
The above processes will be repeated until all units are completed.
<G2.5 Recipe View> G2-51
IM 33S01B30-01E
G2.5 Recipe View
The builders for creating recipe group, master, recipe procedure and recipe unit
procedure and the related menus are provided in Recipe View.
Start Recipe View
Click Windowss [Start] button, and click [Programs], [YOKOGAWA CENTUM], then
[Recipe View]. The Recipe View can be started as shown below.
G020501E.EPS
Recipe View [CS 3000] - RCP0001
Ready
Name Type Recipe Name Modified Date Comment
RcpHead Recipe Header RECIPE01 1999/10/22 00... Polymerization Column
RcpRp Recipe Procedure RECIPE01 1999/10/22 00...
RcpT01 Unit Recipe RECIPE01 1999/10/22 00... Polymerization Column
RcpT02 Unit Recipe RECIPE01 1999/10/22 00...
File Edit View Load Project Tools Help
BKBRcpView
MYPJT
RG01
RCP0001
RCP0002
RCP0003
RG02
-
-
-
+
Figure Recipe View
G2-52 <G2.5 Recipe View>
IM 33S01B30-01E
File Menu of Recipe View
File Menu
The [File] menu of the recipe view window contains the following commands.
Create New Project
Name, Comment, Directory, Computer Name To Store Database, Reference Project Directory
When the BKB RcpView folder is selected in the left pane of the window, clicking [Create
New] and then [Project...] from the [File] menu opens the Create New Project dialog box
(see below).
In this dialog box, specify the name, comment, and directory of the new project and the
name of the computer in which the project database is to be stored. A recipe project should
be created within a project folder created on System View.
Cancel OK
G020502E.EPS
New Project
...
MYPJT
C:\CS3000\ENG\BKProject
...
Reference Project Directory
C:\CS3000\ENG\BKProject
Name
Comment:
Directory
Computer Name To Store Database
Figure New Project Dialog Box
When a project is first created on Recipe View. The project folder will be automatically
added to [CTMRMNG] as the name for sharing. Moreover, when a project is created, a
recipe group is automatically created.
IMPORTANT
When the project is deleted from System View, or when creating the second project, the
name for sharing will not be added automatically. It is necessary to manually add a name
for sharing for the project to [CTMRMNG].
When creating two or more projects on Recipe View, it is necessary to delete the name for
sharing of the existing project and add a new name for sharing into [CTMRMNG] manually.
To set a share name to a project folder, log on to Windows using the Administrators privi-
lege.
IM 33S01B30-01E
Name
Select the project name of the project you created in the System View window. If the
Recipe Builder is installed in the same personal computer with the system generation
function and a project has already been created in the System View window, that
project name is displayed.
Comment
Type a comment of up to 24 characters for the project.
Directory
Set the directory for holding the project designated in [Name] item. The path to the
folder of the project created in the System View window not including the folder of the
project is set by default.
The Recipe folder will be created in the project folder specified in this box.
Computer Name To Store Database
This need not be set usually. However, if you map a sharing drive for or specify an-
other personal computer whose share name is set as the storage location of the
master recipe data, type in this box the name of the computer in which the database
should be stored.
Reference Project Directory
The path of the directory for the current project created on System View can be
entered here. After specifying the referenced project, the tags of common blocks or
unit instruments can be referenced.
When the recipe project is accessed by more than two computers, the Reference
Project Directory can be specified as follows. CS 1000 is a name for sharing.
\\<Computer Name>\CS1000\eng\BKProject\<Project Name>
Example:
If the computer name is HIS0124, and the project name is MYPJT, the Reference
Project Directory can be specified as follows.
\\HIS0124\CS1000\eng\BKProject\MYPJT
Automatic Management of Recipe Version
Check this option can automatically manage the recipe version of master recipe.
When the recipe revision number is under the automatic management, the recipe
revision number and revision date are automatically set to the recipe header on the
recipe builder. With automatic management of master recipe revision number, linking
a control recipe and its master recipe becomes possible. However, with or without the
automatic recipe revision number management is valid for the whole project.
When the recipe revision number is under the automatic management, user cannot
changed the recipe revision number and revision date that automatically set to the
recipe header.
SEE ALSO
For more information about recipe revision number and revision date in the recipe header, see the
following:
Version Number in Header Definitions in G2.1.1, Header
Version Date in Header Definitions in G2.1.1, Header
IM 33S01B30-01E
Create New Recipe Group
Recipe Group Number, Comment, Load Destination Server Name
When a project folder is selected in the left pane of the window, clicking [Create New] and
then [Recipe group...] from the [File] menu opens the New Recipe Group dialog box (see
below).
In this dialog box, specify the group number and comment of the new recipe group and the
name(s) of the server(s) in which the master recipes should be loaded.
Cancel OK
G020503E.EPS
New Recipe Group
Recipe group number
Comment
1
HIS0124
Load Destination Server Name 1
Load Destination Server Name 2
Figure New Recipe Group Dialog Box
Recipe group Number
Type or select a recipe group number from 1 to 16.
Comment
Type a comment of up to 24 alphanumeric characters for the recipe group.
Load Destination Server Name 1 and Load Destination Server Name 2
The computer name used as master server where the master recipe to be down-
loaded can be specified here. The server stations can be configured on Process
Management Configuration Builder.
The computers (HIS) specified in these boxes will be the server where the master
recipes to be downloaded. If the names of the server stations defined in Process
Management Configuration Builder are changed, the Load Destination Server Name
setting should also be changed accordingly on the property sheet of recipe group.
IM 33S01B30-01E
Create New Subgroup
Subgroup Name
Up to 1000 master recipes can be created in each recipe group. These master recipes can
be further categorized into sub-groups. Sub-groups only seen in the recipe view window.
First, select a recipe group folder in the left pane of the window. Next, click [Create New]
and then [Subgroup] from the [File] menu. The New Subgroup dialog box (see below)
appears. In this dialog box, specify the subgroup name.
Cancel OK
G020504E.EPS
New Subgroup
Subgroup Name
Figure New Subgroup Dialog Box
Subgroup Name
Type the subgroup name of up to 16 characters.
Up to 5 levels of nesting subgroups may be created.
Create New Recipe
Recipe Number, Recipe Name, Comment
First, select a recipe group folder in the left pane of the window. Next, click [Create New]
and then [Recipe] from the [File] menu.
The New Recipe dialog box (see below) appears. In this dialog box, specify the recipe
number, recipe name and comment. When a project is created, a recipe group is automati-
cally created. The recipe number, recipe name and comment can be set on the New
Recipe dialog box shown as follow.
Cancel OK
G020505E.EPS
New Recipe
Recipe Number
Recipe Name
1
RECIPE01
Comment
Figure New Recipe Dialog Box
Recipe Number
Type or select a recipe number from 1 to 1000.
Recipe Name
Type the recipe name of up to 16 characters.
Comment
Type a comment of up to 64 characters for the recipe.
IM 33S01B30-01E
Create New Recipe Procedure
Recipe, Comment
First, select a recipe folder from the directory tree. Then click [Create New] [Recipe
Procedure] from the [File] menu. The [New Recipe Procedure] dialog box will appear.
After specifying a recipe procedure, the number and comment for the recipe procedure will
be displayed in this dialog box. A [New Recipe Procedure] dialog box is shown as follows.
Cancel OK
G020506E.EPS
New Recipe Procedure
Recipe
RECIPE01
Comment
Figure New Recipe Procedure Dialog Box
Create New Unit Recipe
Recipe, Unit, Comment
First, select a recipe folder in the left pane of the window. Next, click [Create New] and then
[Unit Recipe] from the [File] menu.
The New Unit Recipe dialog box (see below) appears. In this dialog box, specify the unit
recipe number and comment.
Cancel OK
G020507E.EPS
New Unit Recipe
Recipe
Unit
RECIPE01
2
Comment
Figure New Unit Recipe Dialog Box
Recipe
The name of the master recipe set when the recipe was created, is displayed and
cannot be changed.
Unit
Type or select a recipe number from 1 to 32 corresponding to the unit recipe or equip-
ment requirements.
Comment
Type a comment of up to 24 characters for the unit recipe.
IM 33S01B30-01E
Open
Use this command to open a file. Depending on the selected file, the Recipe Builder or
Recipe Procedure Builder starts running.
Delete
Deletes the selected folders or files.
The master recipe may be removed from the Recipe View by [Delete] command. However,
the master recipe still exists in the master server. The following operations may remove the
master recipe from the master server. Choose [Master Download] - [Delete Group and
Load] or choose [Download] - [Delete Group and Load] on [Load] menu.
Properties...
Opens the Properties sheets for a selected file or folder.
Print Master Recipe
Opens a dialog box for printing master recipes. In the dialog box, select the range of master
recipes to be printed and click [Start]. You can also set the header and footer.
TIP
The printer must be set up in Windows.
Exit
Quits Recipe View.
IM 33S01B30-01E
Edit Menu of Recipe View
Edit Menu
The [Edit] menu of Recipe View contains the following commands.
Cut
Use this command to move files and folders. The Cut command registers the folders and
files selected in the window, in the clipboard buffer. These folders and files including their
contents will be moved when the destination is selected and the Paste command is used.
Copy
Use this command to copy files and folders. The Copy command registers the folders and
files selected in the window, in the clipboard buffer. These folders and files including their
contents will be copied when the destination is selected and the Paste command is used.
Paste
Copies or moves the files and folders registered in the clipboard buffer to a folder selected
in the window.
Select All
Selects all files listed in the right pane of the window.
IM 33S01B30-01E
View Menu of Recipe View
View Menu
The [View] menu of Recipe View contains the following commands.
Toolbar
Switches whether or not to display the toolbar.
Status Bar
Switches whether or not to display the status bar.
Message Display Area
Switches whether or not to display the message box at the bottom of the window.
Large Icon
Displays the files in the right box of the window as large icons.
Small Icon
Displays the files in the right box of the window as small icons.
List
Displays the files in the right box of the window as a list of file names.
Details
Displays the files in the right box of the window as a list of file names together with the file
types and the dates modified last.
Refresh
While you are working with the Recipe Builder or Procedure Builder, the recipe view win-
dow may not display the most recent information. Clicking [Refresh] from the [View] menu
updates the displayed contents of the window.
IM 33S01B30-01E
Load Menu of Recipe View
Load Menu
The [Load] menu of Recipe View contains the following commands.
Master Download
Master Download contains the following commands
Load
From the directory tree, choose a file group of a project, of a recipe group or of a
recipe unit. A master recipe, which has been checked, can be downloaded to the
server station for the selected group. However, multiple master recipes can not be
downloaded together.
Delete Group and Load
recipe unit. The existing master recipe of the selected file group can be deleted from
HIS and then a master recipe, which has been checked, can be downloaded for the
selected group. After downloading, the master recipes removed from server station
will no longer exist in the HIS.
Download
Download contains the following commands
Load
recipe unit. Click [Save] may check the master recipe for the selected group. If the
check gives a good result, the checked master recipe will be downloaded to server
station. However, multiple master recipes can not be selected together.
Delete Group and Load
recipe unit. Click [Save] may check the master recipe for the selected group. If the
check gives a good result, the existing master recipe of the selected file group can be
deleted from HIS and then the checked master recipe will be downloaded. After
downloading the master recipes removed from server station will no longer exist in the
HIS.
Project Menu of Recipe View
Project Menu
The [Project] menu of Recipe View contains the following commands.
Open Project...
Use this command to display an existing recipe project file.
Clicking [Open Project...] from the [Project] menu opens a dialog box. Select a project to be
displayed in Recipe View window.
Close Project...
Hides the selected recipe project file from the recipe view window. Although the project is
not displayed in the window, it is not deleted.
IM 33S01B30-01E
Tool Menu of Recipe View
Tool Menu
The [Tool] menu of Recipe View contains the following items for recipe data backup.
SEE ALSO
To backup the recipe data on Recipe View can be performed in the same procedure for project data
backup on System View. For more information about project data backup on System View, see the
following:
F1.6, Project Data Backup
Set Backup
A dialog box for backup settings displays.
Start Backup
A dialog box for recipe data backup displays.
Audit Trail DB Viewer
Starts Audit Trail DB Viewer so that the database for logging edition and modification
history can be viewed.
SEE ALSO
For more information about Audit Trail Database Viewer, see the following:
P7.4.1, Audit Trail Database Viewer
Help Menu of Recipe View
Help Menu
The [Help] menu of Recipe View contains the following options.
How To Use On-line Manual
Opens a dialog box of instructions on how to use the on-line Reference Manual.
Reference Index
Displays the index of the Reference Manual, IM 33S01B30-01E.
Version Information
Opens a dialog box showing what software is installed and the version of the software.
Builder Definition Items...
Displays a list of settings in Recipe View window.
G2-62 <G2.6 Recipe Data Backup>
IM 33S01B30-01E
G2.6 Recipe Data Backup
With recipe data backup, the data loss damage caused by disk crash can be pre-
vented. Recipe data backup can be performed when closing Recipe View or other
times.
SEE ALSO
To backup the recipe data on Recipe View can be performed in the same procedure for project data
backup on System View. For more information about project data backup on System View, see the
following. When reading chapter F1.6, Project Data Backup replace System View with Recipe View:
F1.6, Project Data Backup
Backup Files
Performing recipe data backup, the following files are duplicated for backup.
All files under the folder of CS 1000 or CS 3000 installed folder\eng\BKProject\Project
Name\recipe\
<G3. Process Management> G3-1
IM 33S01B30-01E
G3. Process Management
This chapter explains control recipes created with Process Management.
What is Process Management ?
Process Management is used to manage batch execution in accordance with batch opera-
tions. The recipe status, batch unit with its batch ID, batch process results and batch
related messages are managed under Process Management.
Recipes that may be handled by Process Management are control recipes. Process Man-
agement is positioned amid Recipe Management, Production Planing and Scheduling,
Production Information Management and Unit Supervision. Moreover it has interfaces with
all the above control activities. The position of Process Management is shown in the dia-
gram below:
G030001E.EPS
Process Management
Unit Supervision
Process Control
(Function Block)
Explained in this chapter
Production Planing
and Scheduling
Production Information
Management
Recipe Management
Figure Position of Process Management
G3-2 <G3.1 Batch Execution Management>
IM 33S01B30-01E
G3.1 Batch Execution Management
Batch Execution Management performs sequential and synchronous control over a
control recipe that encompasses more than one unit. The diagram below shows the
flow of a batch, from the creation of control recipes to completion of their execution:
G030101E.EPS
Master recipe
Control recipe
(RESERVED)
Control recipe
(LOG)
Control recipe
(READY)
Control recipe
(ACTIVE)
Control recipe
(LOG)
Control recipe
(COMPLETE)
Control recipe
(COMPLETE)
HIS
FCS
Recipe setup
Start of
execution
Completion of
execution
Completion of
execution
Downloading Uploading
Delation
Figure Flow of Batch
<G3.1 Batch Execution Management> G3-3
IM 33S01B30-01E
Batch Modes
There are certain modes of control recipes in which the recipe status and unit recipe status
may be determined automatically. The two types of mode are as follows:
Download mode: Prescribes the download action for a control recipe.
Start mode: Prescribes the start action for a recipe or unit recipe.
Recipe Download Mode
MAN:
The recipe is downloaded to FCSs manually.
AUT:
The recipe is downloaded to FCSs automatically upon completion of its setup.
TIME:
The recipe is downloaded to FCSs automatically at a time specified by the production
planning and scheduling functions.
Unit Recipe Download Mode
MAN:
The unit recipe is downloaded to FCSs manually.
AUT:
The unit recipe is downloaded to FCSs automatically upon completion of its setup.
TIME:
The unit recipe is downloaded to FCSs automatically at a time specified by the production
planning and scheduling functions.
Recipe Start Mode
MAN:
The recipe is started manually.
AUT:
The recipe is started automatically upon completion of its downloading to FCSs.
TIME:
The recipe is started automatically at a time specified by the production planning and
scheduling functions.
Unit Recipe Start Mode
MAN:
The unit recipe is started manually.
AUT:
The unit recipe is started automatically upon completion of its downloading to FCSs.
TIME:
The unit recipe is started automatically at a time specified by the production planning and
scheduling functions.
Note Points on Batch Mode
The batch mode is specified on the Recipe Builder. Changes on batch mode after the
recipe setup are regarded as invalid.
When a unit recipe start mode is AUT, and when the unit assigned to the unit recipe has
been used by other unit recipe, the unit recipe auto-start will result in an error. In this case,
to start the unit recipe may be performed on batch related windows.
IM 33S01B30-01E
Control Recipe Statuses
The control recipe statuses include recipe status and unit recipe status. The recipe status
indicates the overall status of a control recipe. By contrast, the unit recipe status indicates
the status of a unit recipe. The status of a given recipe changes in conjunction with the
status of the unit recipe contained in the recipe.
Recipe Statuses
The status of a recipe which is converted as a control recipe is managed according to the
flow of recipe status transition as shown in the diagram below:
G030102E.EPS
Master recipe
Reserve
LOAD UP_LOAD
RESERVED READY ACTIVE
ABORTED
LOG COMPLETE
DELETED
START
END
ABORT ABORT
ABORT
Control recipe
DELETE
DELETE DELETE
Figure Transition of Recipe Statuses
IM 33S01B30-01E
RESERVED
Indicates that the recipe setup ended successfully and the required recipe is reserved.
When recipe setup ends successfully, the recipe status becomes RESERVED. The
unit recipe status becomes ASSIGNED if unit is already assigned; the status be-
comes NO ASSIGNED if unit is not assigned.
READY
Indicates the downloaded recipe is waiting for execution (start). Transition to READY
takes place when shared sections of the recipe are downloaded successfully.
ACTIVE
Indicates that the recipe is running. Transition to ACTIVE takes place when a recipe
is started.
LOG
Indicates that the result data are being uploaded (Data Logging). When the statuses
of all unit recipes are either LOG or COMPLETE, the recipe status changes to
LOG. Transition to LOG takes place only when at least one or more of the unit
recipe statuses become LOG.
COMPLETE
Indicates that all recipes are completed successfully. Transition to COMPLETE takes
place when all unit recipes statuses become COMPLETE.
ABORTED
When the statuses of all unit recipes are either ABORTED or COMPLETE, the
recipe status changes to ABORTED. Transition to ABORTED takes place only
when at least one or more unit recipes statuses become ABORTED.
DELETED
Indicates that a control recipe may be deleted. Since the control recipe itself disap-
pears, there is no moment in which the control recipe is actually in the DELETED
status. Transition to this DELETED status may take place only when the recipe
status is either RESERVED, ABORTED or COMPLETE.
IM 33S01B30-01E
Unit Recipe Statuses
A recipe which is converted as a control recipe manages the unit recipe statuses according
to the flow of unit recipe status transition as shown in the diagram below:
G030103E.EPS
Control recipe
ABORT ABORT
ABORT
NO -
ASSIGN
ASSIGNED READY ACTIVE
ABORTED
LOG COMPLETE
UNIT
ASSIGN LOAD START UP_LOAD
CANCEL
END
Figure Transition of Unit Recipe Statuses
NOASSIGN
Indicates that the unit recipe is assigned with a unit. Transition to NOASSIGN takes
place when unit is not yet assigned or when dynamic unit assignment is being carried
out or failed. Transition to NOASSIGN also occurs if the assigned unit is canceled.
ASSIGNED
Indicates that unit recipe is assigned to a unit. Transition to ASSIGNED takes place
when the unit assignment ends successfully.
READY
Indicates that unit recipe is downloaded and waiting for execution (start). Transition to
READY takes place when the unit recipe downloading ends successfully.
LOG
Indicates that the result data are being uploaded (Data Logging). Transition to LOG
takes place when the execution of a unit recipe is completed. Since the unit recipe
does not have uploading function, the unit recipe status transit from LOG to other
status immediately.
COMPLETE
Indicates that the unit recipe is completed successfully. Transition to COMPLETE
takes place when uploading is completed or the unit recipe ends successfully.
ABORTED
Indicates that the unit recipe is aborted. Transition to ABORTED takes place when
the unit recipe execution is forcibly stopped.
IM 33S01B30-01E
Status Change Commands
The recipe status can be changed as desired by issuing a status change command. Status
change commands may be issued from the batch related windows or a SEBOL program.
There are two types of status change commands: commands for recipes and commands
for unit recipes.
The table below shows a list of status change commands. The text of a status may be
changed via a command can be defined in the STATUS data item of the system-specific
common block.
Table Table of Status Change Commands
Status Change Command Status Character String
Target of Command Source of Command
Recipe Unit Recipe
Operating/Monitoring
Window
SEBOL
RESERVE command - App. - App. App.
ASSIGN command - - App. App. App.
LOAD command - App. App. App. App.
CANCEL command CANCEL - App. App. App.
START command START App. App. App. App.
UP_LOAD command - App. App. N/A N/A
GATHER command - App. - App. N/A
ABORT command ABORT App. App. App. App.
END command END App. App. App. App.
DELETE command - App. - App. N/A
G030104E.EPS
App.: Can be specified.
N/A: Cannot be specified.
-: Cannot be used as a status change command.
RESERVE Command to Setup
The RESERVE command is used to perform recipe setup. (Using DELETE command may
cancel a reserved recipe).
Normally, the unit names are assigned at the stage of recipe setup but if the unit to be used
are not yet determined, the setup can be done without unit assignment. In this case, specify
a hyphen (-) instead of a unit name.
The RESERVE command enables recipe setup via the batch related windows or a SEBOL
program. When executing recipe setup using a SEBOL (rpreserve) command, the name of
the unit used must be specified beforehand in the equipment requirements of the master
recipe.
IM 33S01B30-01E
LOAD Command to Download
The control recipe can be downloaded to the FCS using the LOAD command. Download-
ing is carried out in two steps: downloading the shared section of a recipe (Header), then
downloading the individual unit recipes.
When the LOAD command is issued, downloading is performed automatically for the unit
recipes whose download mode is AUT.
The LOAD command may be issued on batch related windows or a SEBOL program. In the
case of directing a download using SEBOL, it is possible to download the specified unit
recipes in the same recipe (urload) or download unit recipes specified by batch ID
(urloadbid).
SEE ALSO
For details of downloading recipe using SEBOL, see the following in the later part of this chapter:
Recipe Download from SEBOL
CANCEL Command to Cancel the Unit Assignment
A unit assigned to the unit recipe may be canceled by CANCEL command.
The unit assignment may be canceled as many time as desired until the unit recipe start.
However, downloading the shared section of a recipe (Header) cannot be canceled.
Upon receipt of the CANCEL command, the system deletes the unit assignment in the
FCS, causing the status of the unit recipe to NOASSIGN.
When the CANCEL command is issued using SEBOL program, it can also cancel the unit
assignment to any of the unit recipes of the same batch.
ASSIGN Command to Dynamically Assign a Unit
The unit assignment to a unit recipe may be performed by ASSIGN command.
To distinguish this unit assignment from the unit assignment carried out during recipe
setup, this assignment is referred as the dynamic unit assignment.
When using SEBOL program to perform dynamic unit assignment, the unit recipes of the
same batch may be assigned.
SEE ALSO
For details on dynamic unit assignment, see the following:
IM 33S01B30-01E
START Command to Start
The START command starts the execution of a recipe. There are two types of START
commands: the command to start recipe and the command to start unit recipe. Each type
of these commands is a separate command, so that issuing a command to start recipe
does not send a command to start unit recipe.
A command to start unit recipe is by no means of starting the assigned unit. When issuing a
command to start unit recipe, if the assigned unit is ready for use, a command to change
the status (PSTART command) is sent to the unit to start. If the unit is in use with another
batch, the command to start unit recipes will result in an error. In this case, the command to
start unit recipes may be re-issued when the unit becomes ready for use.
The START command can be issued from the batch related windows or a SEBOL program.
When the START command is issued using a SEBOL program, it is possible to start execu-
tion of the unit recipes in the same batch as well as other recipes and unit recipes by
specifying their batch IDs.
UP_LOAD Command to Upload
After execution is completed, the result data from the control recipe in the FCS may be
gathered by issuing an UP_LOAD command.
Since uploading is performed automatically by the system, it cannot be started from the
batch related windows or from SEBOL program. When the unit recipe ends successfully,
the UP_LOAD command is automatically sent to the unit recipe. When the uploading ends
successfully, the unit recipe in the FCS will be automatically removed.
GATHER Command to Gather Result Data
The result data can be gathered from the control recipe in the FCS by issuing the GATHER
command.
Different from the UP_LOAD command which is automatically gathering result data, the
GATHER command is used to gather the result data at an arbitrary moment. Normally, the
result data are gathered prior to uploading. Also, a GATHER command does not change
the recipe status.
ABORT Command to Abort
A running control recipe may be forcibly terminated by issuing the ABORT command.
When a recipe unit procedure ends with abnormality, the ABORT command to terminate
the unit recipe is automatically issued.
There are two types of ABORT commands: the command to abort recipe and the command
to abort unit recipe. When issuing a command to abort a recipe, an ABORT command is
also sent to abort all relevant unit recipes.
The ABORT command may be issued from the batch windows or a SEBOL program. When
an ABORT command is issued from a SEBOL program, it is possible to abort unit recipes
in the same batch as well as other recipes and unit recipes by specifying their batch IDs.
IM 33S01B30-01E
END Command to End
A recipe changes to the execution completed status when an END command is issued.
If any unit recipe is downloaded to the FCS, the unit recipe will be removed.
This command is also applied to remove the unit recipes that are not completed or even not
started.
DELETE Command to Delete Control Recipes
A designated control recipe may be deleted by issuing a DELETE command.
A DELETE command may delete the designated control recipe and all relevant unit reci-
pes, and the corresponding batch ID will be removed from the product overview window.
The DELETE command is valid only when the control recipe is in RESERVED, COM-
PLETE or ABORTED status.
IM 33S01B30-01E
Command to Change Status Using SEBOL
The SEBOL built-in functions may be applied in the operation started from the unit recipe to
manipulate the applicable unit recipes in the recipe. The table below shows a list of meth-
ods that may be applied using SEBOL:
Table Unit Recipe Manipulation Using SEBOL
Function Change in unit recipe status Manipulation method
Dynamic assignment of units NOASSIGNASSIGNED urassign built-in function
Download ASSIGNEDREADY urload built-in function
Start READYACTIVE Set START in SYSPCMnn.STATUS (*1)
Abort NOASSIGNABORTED
ASSIGNEDABORTED
READYABORTED
ACTIVEABORTED
LOGABORTED
Set ABORT in SYSPCMnn.STATUS
End NOASSIGNCOMPLETE
ASSIGNEDCOMPLETE
READYCOMPLETE
Set END in SYSPCMnn.STATUS
Unit cancel ASSIGNEDNOASSIGN
READYNOASSIGN
Set CANCEL in SYSPCMnn.STATUS
G030105E.EPS
*1: SYSPCMnn is a kind of fixed system common block defined for each unit recipe. nn is the unit recipe number. When the
unit recipe number is a single-digit value, it requires to add a leading zero, such as SYSPCM01.
Using cmwrite command may input the desired status text directly to the STATUS data item
of the system-specific common block provided for each unit recipe instead of using START,
ABORT, DELETE and CANCEL commands to transit status.
When the unit recipe executing the built-in functions urassign, urload or cmwrite and
completed successfully, it only means the commands are accepted by the process man-
agement function. It does not mean the unit recipe has applied the built-in functions to the
corresponding unit.
After the executing the built-in functions, it may be necessary to use ccmread command to
check the STATUS item of the common block of the unit recipe to check the current status
so as to confirm the result of execution of the built-in functions, or to check by SEBOL
accordingly.
SEE ALSO
For more information about syntax of cmwrite, see the following:
Writing Common Block Data in H1.6.1, Accessing Common Block Data
For more information about syntax of ccmread, see the following:
Reading Common Block Data in H1.6.1, Accessing Common Block Data
For more information about syntax of urassign and urload, see the following:
Dynamic Assignment of Units and Download Operations in H1.6.2, Manipulating Unit Recipes
IM 33S01B30-01E
Command to Change Status Using SEBOL by Specifying a Batch ID
The SEBOL built-in functions may be applied in the operation started from the unit recipe to
manipulate the applicable unit recipes in the recipe by specifying a Batch ID. The table
below shows a list of methods that may be applied using SEBOL:
Table Unit Recipe Operations Using SEBOL by Specifying a Batch ID
Function Change in unit recipe status Manipulation method
Dynamic assignment of units NOASSIGNASSIGNED urassignbid built-in function
Download ASSIGNEDREADY urloadbid built-in function
Start READYACTIVE Set START in SYSPCMnn.STATUS (*1)
Abort NOASSIGNABORTED
ASSIGNEDABORTED
READYABORTED
ACTIVEABORTED
LOGABORTED
Set ABORT in SYSPCMnn.STATUS
End NOASSIGNCOMPLETE
ASSIGNEDCOMPLETE
READYCOMPLETE
Set END in SYSPCMnn.STATUS
Unit cancel ASSIGNEDNOASSIGN
READYNOASSIGN
Set CANCEL in SYSPCMnn.STATUS
G030106E.EPS
*1: SYSPCMnn is a kind of fixed system common block defined for each unit recipe. nn is the unit recipe number. When the
unit recipe number is a single-digit value, it requires to add a leading zero, such as SYSPCM01.
Using cmwritebid command may input the desired status text directly to the STATUS data
item of the system-specific common block provided for each unit recipe instead of using
START, ABORT, DELETE and CANCEL commands to transit status.
When the unit recipe executing the built-in functions urassignbid, urloadbid or cmwritebid
and completed successfully, it only means the commands are accepted by the process
management function. It does not mean the unit recipe has applied the built-in functions to
the corresponding unit.
After the executing the built-in functions, it may be necessary to use ccmreadbid command
to check the STATUS item of the common block of the unit recipe to check the current
status so as to confirm the result of execution of the built-in functions, or to check by
SEBOL accordingly.
SEE ALSO
For more information about syntax of ccmreadbid, see the following:
Reading Common Block Data (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
For more information about syntax of cmwritebid, see the following:
Writing Common Block Data (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
For more information about syntax of urassignbid and urloadbid, see the following:
Manipulating Unit Recipes (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
IM 33S01B30-01E
Deleting Control Recipes
When a command to delete control recipe is issued, all the unit recipes related to the
specified control recipe will be deleted, and the corresponding batch ID will be removed
from the product overview window. This command is valid only when the control recipe is in
RESERVED, COMPLETE or ABORTED status.
There are two ways to delete control recipes, as shown below:
Manual Deletion
Delete the recipe by specifying the batch ID from the product overview window.
Automatic Deletion
Maximum Number of COMPLETE Recipes, COMPLETE Recipe Attribute
Specify the maximum number of COMPLETE recipes for each recipe group. When the
number of control recipes executed (COMPLETE) exceeds the maximum number speci-
fied, the executed recipes are automatically deleted in First-In-First-Out order.
When COMPLETE recipe and ABORTED recipe is selected as the attribute for COM-
PLETE recipe via the Process Management Configuration Builder, the control recipes with
recipe status ABORTED will treated as COMPLETE recipes and also be deleted in the
same manner as COMPLETE control recipes. When select the DELETED recipes, the
ABORTED recipes are not included.
The maximum number of COMPLETE recipes is specified for each recipe group via the
Process Management Configuration Builder. A value from 1 to the maximum number of
control recipes can be specified. The default value is No and there is no maximum num-
ber specification. COMPLETE recipes can be stored up to the maximum number of control
recipes specified. In this case, since the auto-deletion is not defined, the stored number of
recipes may reach to the limit, and the new recipe can not be setup. It is recommended to
delete the obsolete recipes for setting up new recipe.
IM 33S01B30-01E
Recipe Download from SEBOL
A batch report can be output by BkbRecpReq command in SEBOL.
How to use SEBOL BkbRecpReq command to output a batch report is detailed as follows.
Define the BkbRecpReq command in Sequence
Message Request Function Builder.
Send the Sequence Message Request (RQ) from SEBOL.
Read the definition in Sequence
Execute the BkbRecpReq command.
Download the recipe.
G030107E.EPS
Example of SEBOL description
...
request RQ,1
...
Example of definition in Sequence
Message Request Function Builder
F BkbRecpReq -d 1.UT101.ITEM01
The processing enclosed by dashed lines
is performed automatically.
Figure Recipe Download Using SEBOL BkbRecpReq Command
BkbRecpReq Command Arguments for Recipe Download
BkbRecpReq command has the following arguments. They are used with the two main
options (-d, -dm) and behave differently. Before and after the options (-d, -dm), at least one
space character is required.
BkbRecpReq -d <Recipe Group Number>.<Tag Name>.<Item Name>
BkbRecpReq -dm <Recipe Group Number>.<Tag Name>.<Item Name>
Option -d
When using BkbRecpReq command with -d option, the station is started by this
command (the station where the sequence message request is defined).
IMPORTANT
The HIS that runs the BkbRecpReq command with -d option should be a server or a
client station in the same recipe group that the batch report belongs to.
The sequence message request for downloading the batch report should be defined
on only one station, either a server or a client station in the recipe group. If two stations
are defined with the same requests, when using BkbRecpReq command with -d
option, the same recipes are downloaded twice from the two stations and system
alarm occurs.
IM 33S01B30-01E
Option -dm
When using BkbRecpReq command with -dm option, the station started by this
command must be a master server station. Thus all server stations where the se-
quence message request is defined download the designated batch reports upon this
command.
IMPORTANT
The HIS that runs the BkbRecpReq command with -dm option must be a master
server station. The batch reports to be downloaded must belong to the same recipe
group that the master server belongs to.
The sequence message requests for downloading the batch report can be defined on
all server stations, but the sequence requests defined in backup server and client
stations are ignored.
TIP
For one recipe group, up to two servers can be defined, one is master server while the other is backup
server. If only one server is defined for the recipe group, that server becomes master server.
Recipe Group Number
The number of the recipe group that the batch downloading belongs to needs to be
specified.
Tag Name and Item Name
The unit instrument tag name and item name that holding the batch ID need to be
specified. The data type of the item is CHR16.
Before running BkbRecpReq command, the tag name, item name and batch ID must
be stored into the above items.
IMPORTANT
When specify the array type item as the argument, only the item name needs to be speci-
fied, no need to specify the array elements. If the data item is a one-dimensional array, the
element [1] is used, while if the data item is a two-dimensional array, the element [1,1] is
used.
Example:
When specifying a two-dimensional array item as the argument, while the batch ID is stored
in ITEM[1,1], in this case, specify ITEM as the argument.
IM 33S01B30-01E
Operation at Errors
If an error occurs while the BkbRecpReq command is used to download a recipe from
SEBOL, the following operations will be performed;
If a download error occurs, for instance because a batch ID in a status other than
RESERVED is specified, a system alarm will be generated on all the server stations/
client stations within the recipe group.
If an error other than a download error occurs, for instance because a nonexistent tag
or item name is specified, a system alarm will not be generated.
<G3.2 Recipe Setup> G3-17
IM 33S01B30-01E
G3.2 Recipe Setup
In process management, control recipes used for the actual manufacturing of prod-
ucts are derived from master recipes created through recipe management. A series
of work steps to produce control recipes is called recipe setup.
The flow of recipe setup is shown in the diagram below. The recipe setup may be
performed from the recipe setup dialog box or from a SEBOL program. The recipe
setup can also be performed using the production planning and scheduling func-
tions.
G030201E.EPS
Master Recipe 1
Recipe Group 1
2
3
Recipe setup
Control Recipe 1
(Batch ID)
Batch ID,
Train,
Path,
Formula,
Unit Name
Figure Flow of Recipe Setup
G3-18 <G3.2 Recipe Setup>
IM 33S01B30-01E
Items to be Set during Recipe Setup
The items to be set during recipe setup is indicated below. If an error occurs during recipe
setup, the control recipe will not be created.
Selection of Master Recipe
Select a recipe to be executed by referring to the recipe group name and master recipe
name.
Affixing a Batch Identifier
The process management function affixes a batch ID as identification code to each control
recipe. The batch ID is definitely required for control recipe. There are two ways to set the
batch ID: through manual entry by the user and through automatic assignment by the
system.
Unit Assignment
When train and path are configured in equipment requirements on Recipe Builder, the train
or a path can be designated. After choosing a train or a path, the unit specified in the path
configured on the Train Builder will be assigned to the unit recipe.
When train or path is not implemented, each unit recipe will assigned with a unit.
However, when operating a real plant, there are cases that the unit corresponds to the unit
recipe is uncertain at the stage of recipe setup. In these cases, the unit assignment may be
performed during the recipe execution. This kind of assignment is referred as dynamic unit
assignment. The dynamic unit assignment may be applied to the second and subsequent
unit recipes.
A fixed unit is required to be assigned to the first unit recipe.
Change of Formula
The formula set in the master recipe can be changed only for the current batch. During
recipe setup, whether the formula is within the range of the high and low limits specified on
the Common Block Builder is checked.
Determination of Control Recipe
Set up the recipe after the checking of the above settings completed successfully. The
control recipe will be created upon completion of the recipe setup.
IM 33S01B30-01E
Recipe Setup by SEBOL
Recipe setup may be performed via the recipe setup dialog box or from a SEBOL program.
When setup is performed from a SEBOL, the built-in function rpreserve() may be used with
selected master recipe and batch ID.
When the rpreserve() is executed, a request for recipe setup is output to the HIS. The
process management function creates a control recipe from the master recipe. When the
control recipe is created, the recipe changes to RESERVED status.
G030202E.EPS
HIS
Recipe setup request
Execute rpreserve()
FCS
Process management functions SEBOL
Master recipe
Control recipe
Reserve
RESERVED
Figure Recipe Setup by SEBOL
SEE ALSO
For the syntax of rpreserve statement, see the following:
H1.6.3, Reserving Recipes
Main Causes of Error for Recipe Setup by SEBOL
When an improper master recipe or batch ID is specified, the error could not be detected by
SEBOL, so that a system alarm may be generated when HIS is running the SEBOL pro-
gram. The recipe setup error occurs in the following cases:
The specified recipe group number or the specified master recipe does not exist in
master server.
The specified batch ID already exists in the recipe groups of the master server.
The units of each unit recipe do not have unique names. (Dynamic assignment [-] is
irrelevant)
The batch ID has been duplicated in the Process Management Configuration Builder.
The maximum number allowed for setting up process control recipes is exceeded.
IM 33S01B30-01E
Note Points on Recipe Setup by SEBOL
When the master server for the relevant recipe group is not found, recipe setup can
not be executed. The system alarms related to recipe setup will not occur either.
The batch ID specified by SEBOL has higher priority than the batch ID specified on
the Process Management Configuration Builder.
To start recipe download automatically, specify AUT as the unit recipe download
mode. While to start recipe download by operator, specify MAN as the unit recipe
download mode.
To start recipe automatically after download, specify AUT as the unit recipe start
mode. While to start recipe after download by operator, specify MAN as the unit
recipe start mode.
During recipe setup, parameters such as charge quantities cannot be changed. The
parameters in the formula defined on the Recipe Builder are applied.
The name of the unit for unit recipe #1 is required to be specified beforehand in the
master recipe as part of equipment requirements. The unit dynamic assignment
cannot be applied to unit recipe #1. If this unit name is not specified, the recipe setup
will fail and the HIS will generate a system alarm.
For unit recipe #2 and after, the unit dynamic assignment may be applied for assigning
unit names.
IM 33S01B30-01E
Batch ID (Batch Identifier)
Batch ID
The batch ID is used as batch identifier (Batch Identification Code) to identify each recipe. A
batch ID may be set as a data item (BATCHID) of the specific system common block. The
batch ID may be used to call up the related operation and monitoring windows or to search
for a specific alarm message. The specifications for batch ID are given below:
Data type:
CHR16
Applicable characters:
A to Z (upper-case only), 0 to 9, -
The first character of Batch ID must be an alphabet letter.
Applicable recipe:
Control recipe
Applicable scope:
All control recipes managed by the process management function
Constraints:
All recipes of all recipe groups under the management of master server should have
unique batch ID. Unit names must not be used.
There are two ways to affix batch ID at the stage of recipe setup. The two methods are
described as follows:
Manual Input by User
The user may enter a batch ID on user recipe setup dialog box at the time of recipe setup.
The system checks the length of character string and duplication. All recipes of all recipe
groups under the management of master server are searched for the check.
IM 33S01B30-01E
Batch ID Affixed by System
The system automatically affixes an ID which is unique within the given recipe group.
Specify the format of a batch ID to be affixed, in the Process Management Configuration
Builder.
System-generated batch ID descriptors
%nG:
Recipe group number defined during recipe setup
(leading zero may be omitted; n is a 1- or 2-digit number)
%nY:
Recipe setup date in YYMMDD (year, month and day) format ( n is a 1-to 6-digit
number)
%nM:
Recipe setup date in MMDD (month and day) format ( n is a 1- to 4-digit number)
%nD:
Recipe setup date in DD (day) format ( n is a 1- or 2-digit number)
%nT:
Recipe setup time ( n is a 1- to 4-digit number)
%nN[t]:
numerical increment [reset time span: 00 to 23 hours]
(leading zero is not omitted; n is a 1- to 9-digit number); Reset value is 1.
%nS:
Input upper-case letters ( n is the length of character string in single byte)
Character:
Fixed character string (A to Z, 0 to 9, -) in upper-case
Example of Formats
BA-%4N BA-0001 to BA-9999
%6Y%2N 98090101 to 98090199
%2G-%4N 01-0001 to 01-9999
%2N-%4S 01-**** to 99-****
Note Points on Batch ID Affixed by System
When input character string (%nS) is specified, it is required to enter a character string
when **** is prompt for entry, only the input string is displayed.
A numerical increment takes place when a recipe setup dialog box is displayed on the
screen. Canceling the recipe setup will prevent the numerical increment for the batch ID.
Note that with multiple recipe setup dialog boxes displayed on one or more HISs, canceling
the recipe setup may not prevent the numerical increment for the batch ID.
If the batch ID already exists, numeric increment continues until a unique ID is found. The
batch ID check is performed on all recipe groups managed by the master server.
IM 33S01B30-01E
Referencing the Batch ID after Completion of the Recipe Setup
RESERVED Batch ID Setting Destination Tag Name, RESERVED Batch ID Setting Destination Data
Item Name
After completion of the recipe setup, the batch ID of a control recipe with the status of
RESERVED, and the unit name of the starting unit recipe are set to the data item
RP_QUEUE[] of a unit instrument with a specified tag name. RP_QUEUE[ ] of a data item
name can be changed.
If the number of batch IDs and the unit names queued exceeds the number of the
RP_QUEUE[] array elements, the excessive batch IDs and unit names will not be stored. In
addition, if the recipe status changes from RESERVED to READY, batch IDs and unit
names will be deleted from RP_QUEUE[].
The tag name and item name used to set the batch ID and unit instrument name may be
specified on the Process Management Configuration Builder. The specified data item name
and the tag name must be unique for each recipe group.
In addition, the data item configured on the Process Management Configuration Builder
should be created to the unit instrument.
G030203E.EPS
Y1 BA-0001 BA-0002 BA-0003
Y2 UNIT-A1 UNIT-B2 UNIT-C3
X1 X2 X3 to X10
RP_QUEUE [ 10,2 ]
Data item
Batch ID, and name of starting unit
Control recipe
(RESERVED)
Unit instrument
Figure Example of Array Data
X1 to X10: Queuing order
Y1: Batch ID
Y2: Name of starting unit
IM 33S01B30-01E
Data Item Definition on Unit Instrument
The data item for holding the batch ID and starting unit recipe for which the control recipe is
in RESERVED status needs to be defined on the unit instrument. The details of the user-
defined data items on the unit instrument are given below:
Data Item Name
Use the name of the data item for RESERVED batch ID specified on the Process
Management Configuration Builder
Data type
CHR16
Array Element 1
10
Array Element 2
2
Display Format
16
Referencing Batch ID to be Executed
By creating the user-defined data item BIDQUEUE[] for the unit instrument, the batch ID
with the unit recipe status of READY will be set to BIDQUEUE[]. When executing multiple
recipe unit procedures on one unit instrument, BIDQUEUE[] can be referenced to confirm
the next batch ID to be executed.
If the number of batch IDs queued exceeds the number of the BIDQUEUE[] array ele-
ments, the excessive batch IDs will be deleted from BIDQUEUE[] in a FIFO manner. In
addition, the start of the unit recipe will delete the executed batch IDs from the batch IDs to
be executed.
Data Item Definitions on the Unit Instrument
The data item for holding batch IDs needs to be defined on the unit instrument. The details
of the user-defined data items on the unit instrument are given below:
Data item name
BIDQUEUE
Data type
CHR16
Array element 1
10
Array element 2
0
Display format
16
IM 33S01B30-01E
Unit Assignment
Unit assignment refers to designating for running a unit recipe. The unit assignment is
performed during the recipe setup. There are two ways to assign a unit to a unit recipe,
Train-Path designation and Direct designation.
Train-Path Designation
The train and path for unit assuagement can be defined on equipment requirements (train-
path) in Recipe Builder. When setting up a recipe, the defined trains or paths can be se-
lected. The unit defined in the selected path will be assigned to the unit recipe.
In Train Builder, the names of units can be defined into a path.
Direct Designation
Direct designation can be applied by designating from a menu or by enter a name directly.
Select from a Menu
The names of units for unit recipes can be predefined on equipment requirements
(Unit Name) in Recipe Builder. The definition is based on each unit recipe. During
recipe setup, one of the defined unit names can be selected from the menu. If a
hyphen (-) is used for the unit name, it stands for a dynamic assignment.
Direct Name Entry
If the name of a unit for running the unit recipe is not defined on equipment require-
ments (Unit Name) in Recipe Builder, a name of a unit can be entered directly for
running the unit recipe during the recipe setup.
IM 33S01B30-01E
Dynamic Unit Assignment
The dynamic unit assignment means, after a recipe starts, to assign a unit for running the
given unit recipe. If the user changes the name of the unit already assigned by dynamic
unit assignment, the information of the assigned unit name will be lost.
The dynamic unit assignment is applied in the following situations:
unit to be assigned are not yet determined (NOASSIGN);
the name of a unit already assigned (ASSIGNED) needs to be changed; or
the name of a unit for a unit recipe that has already been downloaded (READY) needs
to be changed.
The dynamic unit assignment is valid only for the unit recipes which are not running.
If the dynamic unit assignment is issued from the HIS after unit recipe downloading, the
existing units will be removed and the dynamically assigned units will take over.
The dynamic unit assignment may be performed on the product-related windows or by a
SEBOL program.
When the dynamic unit assignment is performed on a product-related window, the product
control window or the equipment requirement dialog box may be used.
When the dynamic unit assignment is performed by a SEBOL program, assignment for a
unit recipe (urassign) within the same batch is possible. Assignment with batch ID
(urassignbid) is also possible.
SEE ALSO
For more information about syntax of urassign, see the following:
Dynamic Assignment of Units and Download Operations in H1.6.2, Manipulating Unit Recipes
For more information about syntax of urassignbid, see the following:
Manipulating Unit Recipes (Batch ID Specification) in H1.6.4, Built-In Functions with Batch ID
IM 33S01B30-01E
Example of Dynamic Unit Assignment
The diagram below shows an example of dynamic unit assignment:
G030204E.EPS
UNIT-A1
UNIT-A2
UNIT-A3
UNIT-A4 UNIT-B4
Unit recipe #1
Unit recipe #2
Unit recipe #3
Unit recipe #4
Figure An Example of Dynamic Unit Assignment
In this example, unit recipes #1 to #3 already have UNIT-A1 to UNIT-A3 assigned to them
at the time of recipe start. When UNIT-A3 is executed, the dynamic unit assignment is used
to select either UNIT-A4 or UNIT-B4 to be used for running unit recipe #4.
Note Points on Dynamic Unit Assignment
Dynamic unit assignment is not allowed for the starting unit recipe (unit recipe #1).
If an error occurs during dynamic unit assignment after downloading the unit recipe,
unit cancellation occurs, resulting in the cancellation of the downloaded unit recipes.
If the dynamic unit assignment is issued from the HIS after downloading unit recipes,
the downloaded unit recipes will be canceled. Then the dynamic unit assignment and
downloading will be performed.
The downloading is performed, in this case, only when the recipe download mode and
the unit recipe download mode are both set as AUT.
G3-28 <G3.3 Batch-Related Messages>
IM 33S01B30-01E
G3.3 Batch-Related Messages
Batch-related messages may be gathered by all HISs on the control bus.
To gather messages from unit instruments, the names of units for recipe execution,
and those of FCSs including the unit instruments must be specified within the
operation and monitoring scope for the HIS-logged user.
SEE ALSO
For the batch-related messages generated by the FCS or HIS and batch-related system alarm messages,
see the following:
Operating Messages (IM 33S02H10-01E)
<G3.3 Batch-Related Messages> G3-29
IM 33S01B30-01E
Grouping Batch-Related Messages
Batch related messages, alarms and events generated by unit instruments or unit function
blocks, can be grouped according to each batch ID by Process Management during recipe
execution.
Alarms and events generated by the FCS during recipe execution or operation records
generated by the HIS are grouped with the batch IDs used as threads and stored as a
batch journal in the HIS historical message file. Such alarms and events are all stored in
the historical message file, regardless of the operation and monitoring scope for the HIS-
logged user.
Messages displayed in the process alarm window and the operator guide window are
within the operation and monitoring scope for the HIS-logged user.
G030301E.EPS
Process alarm window
Process alarm
(Batch ID)
Operator guide window
Operator guide
message
(Batch ID)
Historical message
report window
Historical message
(Batch ID)
Historical
message
save file
HIS
Message processing
FCS
Unit instrument Recipe Function block
Batch report
Batch journal
Figure Grouping Batch-Related Messages
G3-30 <G3.3 Batch-Related Messages>
IM 33S01B30-01E
Equalizing Batch-Related Messages
The HIS message processing function equalizes all batch-related messages generated
during the recipe execution to store them in the historical message save file. The batch-
related messages can be searched for by the batch ID in the Historical Message Report
window.
Messages are displayed in the Process Alarm window and the Operator Guide window
according to the operation and monitoring privilege level specified for the HIS-logged user.
FCS
G030302E.EPS
Control bus
HIS HIS HIS HIS
Process
management
function
Master server
Process
management
function
Backup server
Process
management
function
Client
Equalizing the messages generated
on the FCS
Equalizing the historical messages
Figure Equalizing Messages
<G3.4 Batch Result Data> G3-31
IM 33S01B30-01E
G3.4 Batch Result Data
The formulas and batch journals recorded during the recipe execution are organized
based on each batch ID to be gathered as batch result data. The gathered data can
be printed out or saved into a file using the batch report package (batch report).
FCS
G030401E.EPS
Control bus
HIS
Batch report
Production management information
Historical
message file
Batch journal Formula
Control recipe
(LOG)
Figure Batch Result Data Acquisition
G3-32 <G3.4 Batch Result Data>
IM 33S01B30-01E
Formula Gathering
The result data recorded during the recipe execution are gathered for each batch. The
batch result data gathered include formulas specified in the control recipe.
Data Gathering Definition
A common block must be created beforehand for storing data gathered as the batch result
data. The created common block must be specified as a formula when master recipe is
created.
To store data in the common block during the recipe execution, copy the data into the
common block at an arbitrary timing using a SEBOL program. The copied data is gathered
as the result data.
Destination of the Gathered Formula
The recipe result data is gathered for each batch ID in the server station in charge of
process management. The gathered data is then stored in the control recipe file.
Gathering Method
Data is gathered either at the time of recipe uploading upon completion of the recipe
execution or using a customized batch report program.
Data is gathered in one of the following manners:
Automatic gathering
Data is gathered either at the time of recipe uploading when the recipe status is LOG.
Manual gathering
The result data is gathered when the batch report is started in the product overview
window or the product control window. If the data is gathered by this method more
than once, the data gathered last is stored as the result data.
G030402E.EPS
Master recipe
Control recipe
(RESERVED)
Control recipe
(LOG)
Control recipe
(READY)
Control recipe
(ACTIVE)
Control recipe
(LOG)
Control recipe
(COMPLETE)
Control recipe
(COMPLETE)
HIS
FCS
Recipe setup
Start of
execution
Completion of
execution
Completion of
execution
Deletion
Figure Flow of Batch
IM 33S01B30-01E
Starting/Ending Date and Time
The data item STRTIME (starting date and time) and ENDTIME (ending date and time) are
reserved for the system-specific common block for recipe as well as the system-fixed
common block for unit recipes. The batch starting/ending data and time are automatically
set to the items accordingly. The table below describes how these data items are set:
Table Settings for Starting/Ending Date and Time
Type Item Name Meaning
Recipe STRTIME (Starting date and time) Date and time the recipe started
(Date and time the recipe status became ACTIVE)
ENDTIME (Ending date and time) Date and time the recipe ended
(Date and time the recipe status became either LOG or ABORTED)
Unit recipe STRTIME (Starting date and time) Date and time the unit recipe started
(Date and time the unit recipe status became ACTIVE)
ENDTIME (Ending date and time) Date and time the unit recipe ended
(Date and time the unit recipe status became either LOG or ABORTED)
G030403E.EPS
Batch Report Auto-Printout
Batch-Report Automatic Operation Printing, Batch-Report File Name Setting, Batch-Report
Output Setting, Printer Name for Batch-Report
When a recipe execution is completed or a unit recipe execution is completed, the batch
report may be printed out automatically. The batch report auto-printout is carried out in the
master server station. For batch report auto-printout, the following settings are required.
TIP
To perform batch report auto-printout, the Report Package is required to be installed in the server station.
If the backup server is used, the Report Package is required to be installed in the backup server station
too.
Batch-Report Automatic Operation Printing
Enable or disable Batch Report Auto-Printout can be specified. This can be set on Process
Management Definition tab of Process Management Configuration builder. Batch Report
Auto-Printout is not enable by default.
Batch-Report File Name Setting
A file name for archiving the report needs to be designated. The file name can be desig-
nated on Process Management Definition tab of Process Management Configuration
builder. The naming method can be selected between [Date and Time] and [Batch ID, Date
and Time]. By default, the naming method is [Batch ID, Date and Time].
Batch-Report Output Setting
The destination for outputting the batch report can be specified. The destination for output-
ting the batch report can be specified on Recipe Group tab of Process Management Con-
figuration builder. There are two options for selection, [Output to file or printer] and [Output
to file only]. By default, [Output to file or printer] is selected.
IM 33S01B30-01E
Printer Name for Batch-Report
When print the batch report to a printer other than the default printer defined on Windows,
the printer name can be specified. Specifying the printer name can be performed with
Report Package.
SEE ALSO
For more information about specifying a printer name with Report Package, see the following:
Details of the Report Printout Command Script in M5.3.2, Defining Report Printout
Setting Printout Format
To print out a batch report automatically, the report format (report file) needs to be defined.
The report format may be specified for each recipe on the formula tab on the Recipe
Builder.
Table Common Block Data Items for Batch Report
G030404E.EPS
Recipe
Type Common Block Name.Data Item Name Meaning
SYSRCM. FORMAT
SYSPCMxx.FORMAT(xx = 01 to 32) Unit Recipe
Auto-printout at the end
of recipe.
Auto-printout at the end
of unit recipe.
IM 33S01B30-01E
Output Batch Report Using SEBOL
A batch report can be output by BkbRecpReq command in SEBOL.
How to use SEBOL BkbRecpReq command to output a batch report is detailed as follows.
Define the BkbRecpReq command in Sequence
Send the Sequence Message Request (RQ) from SEBOL.
Read the definition in Sequence
Execute the BkbRecpReq command.
Output the batch report.
G030405E.EPS
Example of SEBOL description
...
request RQ,1
...
Example of definition in Sequence
Message Request Function Builder
F BkbRecpReq -r 1.UT101.ITEM01
The processing enclosed by dashed lines
is performed automatically.
Figure Output Batch Report Using SEBOL BkbRecpReq Command
BkbRecpReq Command Arguments for Outputting Batch Report
BkbRecpReq command has the following arguments. They are used with the three main
options (-r, -rm, -rc) and behave differently. Before and after the options (-r, -rm, -rc), at
least one space character is required.
BkbRecpReq -r <Recipe Group Number>.<Tag Name>.<Item Name>
BkbRecpReq -rm <Recipe Group Number>.<Tag Name>.<Item Name>
BkbRecpReq -rc <Recipe Group Number>.<Tag Name>.<Item Name>
IM 33S01B30-01E
Option -r
When using BkbRecpReq command with -r option, the master server outputs the
batch report defined on the Process Management Configuration Builder of the station
started by this command (the station where the sequence message request is de-
fined).
IMPORTANT
The HIS that runs the BkbRecpReq command with -r option should be a server or a
The sequence message request for outputting the batch report should be defined on
only one station, either a server or a client station in the recipe group. If two stations
are defined with the same requests, when using BkbRecpReq command with -r
option, the same reports are printed twice from the two stations.
The following settings need to be defined on the Process Management Configuration
builder for running BkbRecpReq command with -r option.
Batch-report file name setting (Date and Time/BatchID, Date and Time)
Batch-report output setting (Output to file only/Output to file and printer)
Printer name for Batch-report
Option -rm
When using BkbRecpReq command with -rm option, the station started by this com-
mand must be a master server station. Thus all server stations where the sequence
message request is defined output the designated batch reports upon this command.
IMPORTANT
The HIS that runs the BkbRecpReq command with -rm option must be a master
server station. The batch reports to be output must belong to the same recipe group
that the master server belongs to.
The sequence message requests for outputting the batch report can be defined on all
server stations, but the sequence requests defined in backup server and client sta-
tions are ignored.
builder for running BkbRecpReq command with -rm option.
Printer name for Batch-report
TIP
For one recipe group, up to two servers can be defined, one is master server while the other is backup
server. If only one server is defined for the recipe group, that server becomes master server.
IM 33S01B30-01E
Option -rc
When using BkbRecpReq command with -r option, the station started by this com-
mand (the station where the sequence message request is defined) outputs the batch
report to the default printer. For outputting the batch report on other stations, the
output destinations need to be defined on Process Management Configuration
builder.
IMPORTANT
The HIS that runs the BkbRecpReq command with -rc option should be a server or a
The sequence message request for outputting the batch report should be defined on
only one station, either a server or a client station in the recipe group. If two stations
are defined with the same requests, when using BkbRecpReq command with -rc
option, the same reports are printed twice from the two stations.
For running BkbRecpReq command with -rc option in client HIS stations, the report
package is required to be installed in these HIS stations. Moreover, for getting the
information regarding to the batch report and report format, the recipe system com-
mon block (SYSRCM), the unit recipe system common block (SYSPCMnn) and batch
report format file (FORMAT) need to be downloaded to the HISs.
builder for running BkbRecpReq command with -r option.
IM 33S01B30-01E
Recipe Group Number
The number of the recipe group that the batch report belongs to needs to be specified.
Tag Name and Item Name
The unit instrument tag name and item name that holding the batch ID and recipe
group number need to be specified. The data type of the item is CHR16. If the data
item is an array type, the unit recipe number and batch ID are held as indicated in the
following table
Table Data Item Usage
Nonarray One-Dimensional Array Two-Dimensional Array
Batch ID
Unit Recipe Number
G030406E.EPS
ITEM ITEM[1]
ITEM[2]
ITEM[1,1]
ITEM[1,2] 0 (fixed)
Before running BkbRecpReq command, the tag name, item name and batch ID must
be stored into the above items. When setting a 0 as unit recipe number, all reports in
the recipe will be printed out.
IMPORTANT
When specify the array type item as the argument, only the item name needs to be speci-
fied, no need to specify the array elements. If the data item is a one-dimensional array, the
element [1] and element [2] are used, while if the data item is a two-dimensional array, the
element [1,1] and element [1,2] are used.
Example:
When specifying a two-dimensional array item as the argument, while the batch ID is
stored in ITEM[1,1] and the unit recipe number is stored in ITEM[1,2], in this case, specify
ITEM as the argument.
IM 33S01B30-01E
Gathering the Batch Journal
Messages generated in the FCS or HIS during batch execution are saved in the historical
message save files on all HISs as a batch journal with batch ID attached. The gathered
messages can be retrieved by batch ID in the historical message report.
The historical message file gathers messages in a rotary format; that is, when the historical
file becomes full, new messages are written over the oldest messages which are thus
deleted.
Batch Journal
A batch journal is a collection of messages generated during the recipe execution. Alarm
messages generated on the FCS and operation record messaged generated on the HIS
during the recipe execution are gathered in the historical message save file on the HIS with
a batch ID attached. Messages generated on units and from operations used on the units
by the recipe execution are also gathered.
Classification of Target Messages
The target messages classified by the source of message are shown below:
Batch-related messages
Batch-related messages generated during the execution a batch can be retrieved
using the batch ID as a search key.
Batch-related messages include batch-related process messages and batch-related
operation record messages.
Unit-related messages
Unit-related messages generated during the execution of a unit procedure can be
retrieved using the batch ID as a search key. Unit-related messages vary depending
on the operation and monitoring scope specified for the user group in the HIS security
functions. If the unit executing the unit procedure is outside the operation and monitor-
ing scope, the messages related to that unit cannot be retrieved by batch ID.
Unit-related messages include unit-related process messages and unit-related opera-
tion record messages.
G3-40 <G3.5 Duplicating Control Recipe>
IM 33S01B30-01E
G3.5 Duplicating Control Recipe
A control recipe of a completed batch can be copied as a new control recipe for a
new batch. The copied recipe can be set up for execution. The copied recipe can
keep the tuning parameters of the original formula (Control Recipe). The source
recipe for duplication is referred to as Original Recipe while the duplicated recipe is
referred to as Copied Recipe.
Procedure of Duplicating Control Recipe
A copied recipe can be duplicated from an original recipe in the following procedure.
G030501E.EPS
Control Recipe
(RESERVED)
Control Recipe
(COMPLETE)
Recipe Setup
Recipe Setup
Control Recipe
(ACTIVE)
Downloading
Start Execution End Execution
Control Recipe
(RESERVED)
Control Recipe
(COMPLETE)
Control Recipe
(ACTIVE)
Downloading
Start Execution End Execution
Master Recipe
Tuning the
copied recipe
Original Recipe
(Copied Recipe)
Copied Recipe
Duplicating
Copy the initial parameters
from master recipe to control recipe
Figure Procedure of Duplicating Control Recipe
<G3.5 Duplicating Control Recipe> G3-41
IM 33S01B30-01E
Adding a Batch ID
A batch ID can be automatically added to the copied recipe. On process management
builder, to automatically add a batch ID can be specified. However, an arbitrary batch ID
can be added manually during duplicating the recipe.
SEE ALSO
For more information about adding batch ID, see the following:
Batch ID Affixed by System in Batch ID (Batch Identifier) in G3.2, Recipe Setup
Displaying Batch ID of Original Recipe
The batch ID of the original recipe is kept in the data item SYSTEM1 of the system fixed
common block (SYSRCM) where the copied control recipe is applied. The batch ID of the
original recipe is indicated in the formula dialog box.
Adding a Recipe Name
When duplicating a recipe, a name can be added to the copied recipe. The default name is
the same name of the original recipe.
IM 33S01B30-01E
Data can be Passed from Original Recipe to Copied Recipe
When duplicating a recipe, some formula data in the original recipe are passed to the
copied recipe, some are not. The formula data in the copied recipe are as follows.
Table Recipe System Common Block of Copied Recipe
G030502E.EPS
Common Block Description Item Data
Recipe
System Common Block
(SYSRCM)
Batch ID
Recipe name
Recipe status
Reserved date and time
BATCHID
RECIPE
STATUS
RSVTIME
A defined ID
The same name as the original
recipe
RESERVED
Batch ID of
original recipe
Date and time of
execution started
Date and time of
execution ended
Scheduled date and time
of execution start
Scheduled date and time
of execution end
Date and time of
rescheduling
Others
0
0
0
0
0
Same as original recipe
Batch ID of
original recipe
Date and time when the recipe
was created
SYSTEM1
STRTIME
ENDTIME
STRSTIME
ENDSTIME
SCHDTIME
Others
Table Unit Recipe System Common Block of Copied Recipe
G030503E.EPS
Common Block Description Item Data
Unit Recipe
SystemCommon Block
(SYSPCM01 - SYSPCM32)
Recipe status STATUS When UNITNAME
is (-), STATUS=NOASSIGN;
When UNITNAME
is not (-), STATUS= ASSIGNED
Date and time of
execution started
STRTIME 0
Date and time of
execution ended
ENDTIME 0
Scheduled date and
time of execution start
STRSTIME 0
Scheduled date and
time of execution end
ENDSTIME 0
Others Others Same as original recipe
Table User-Defined Common Block of Copied Recipe
G030504E.EPS
Common Block Data Description
User-Defined
Common Blocks
Set Values
Parameters
User can specify to copy the actual settings in original
recipe or to copy the initial settings in master recipe.
Settings
IM 33S01B30-01E
Copy Result Data
Result Data when Copying/Exporting Control Recipe
When duplicating a control recipe, users need to specify whether to copy the Result Data
(*1) in the original recipe into the copied recipe or to copy the initial settings in master
recipe into the copied recipe. This can be specified on the dialog box for copying control
recipe. On Process Management Builder, the default setting of the dialog box can be
specified. The initial setting is not copying the actual settings as the default on the dialog
box. Both copying recipe and exporting formula dialog boxes are affected by the setting on
Process Management Builder.
*1: The [Result Data] stand for setting on the Data Type item of Common Block Builder.
G030505E.EPS
Ready
3 SYSRCM.BATCHID
4 SYSRCM.SYSTEM1
5 SYSRCM.STRTIME
6 SYSRCM.ENDTIME
7 SYSRCM.LOADMODE
8 SYSRCM.STRTMODE
RESERVED batch ID setting destination tag name UT0001
RESERVED batch ID setting destination data item name RP_QUEUE
Batch-report output setting output to file and printer
Printer name for Batch-report \\SVRDR\CANON LASER SHOT LBP
Result data when copying/exporting control recipe Not included
Message
Process management configuration builder - [Pjt:MYPJT File:BatchCnf.edf]
Recipe group1 Recipe group2 Process Managem
This setting is valid for both control recipe copy and
formula export dialog boxes.
Figure Process Management Configuration Builder
IMPORTANT
The option of copying result data on the process management configuration builder is
relevant to the default setting on exporting result data on exporting formula dialog box. This
dialog box displays when manually exporting a formula. This option is also relevant to the
setting for exporting the result data when automatically exporting a formula.
SEE ALSO
For more information about manually exporting a formula, see the following:
G3.6.1, Exporting Formulas Manually
For more information about automatically exporting a formula, see the following:
G3.6.2, Exporting Formulas Automatically
IM 33S01B30-01E
Status of Original Recipe
Duplicating control recipe can be performed regardless of the original recipe status. How-
ever, when the control recipe is not in RESERVED or COMPLETED status, the data exist
in a FCS such as set values, actual control recipe settings and parameters are not avail-
able for copying. In this case, using a data acquisition command to collect the FCS data,
then duplicating the control recipe may copy the actual settings to the copied recipe.
Clicking the gather recipe result data button on product overview window can send a data
acquisition command.
Procedure of Duplicating Control Recipe
The procedure of duplicating control recipe is as follows.
1. On Product Overview window, choose the control recipe for duplicating (the original
recipe), then click the [Control Recipe Copy Dialog Box] button. A dialog box appears
as follows.
G030506E.EPS
.RO 1 Product Overview Recipe Group 1
4/4
1 RECIPE01 RESERVED 01-0011 01-0008
3 RECIPE01 COMPLETE 01-0009 00/06/23 15:18 00/06/23 18:18
4 RECIPE01 COMPLETE 01-0008 00/06/23 09:26 00/06/23 12:31
No. RECIPE STATUS BATCH ID ORIGIN BATCH ID START TIME END TIME
READY
Reset
RECIPE01 Recipe Group 1
ORIGIN BATCH ID 01-0009
01-0012
RECIPE01
BATCH ID
RECIPE
Copy Result Data
Copy
Gather Recipe Result Data
Control Recipe Copy Dialog Box
Product Overview Window
Figure Product Overview Window and Control Recipe Copy Dialog Box
2. Enter a new batch ID as required. If the actual settings of the control recipe need to be
copied, check the option mark [Copy Result Data]. If the mark is not checked, the
initial settings in the master recipe will be used.
3. Click [Copy] button on the Copy Control Recipe dialog box, then a confirmation dialog
appears.
4. Click [OK] button, the selected control recipe will be duplicated.
IM 33S01B30-01E
IMPORTANT
1. If not copying the actual settings from the original control recipe to the copied recipe,
the settings in the master recipe with the same recipe name will be copied to the
copied recipe. In the case that a master recipe is modified after loading to control
recipe, the discrepancies take place between the two recipes. Thus, when duplicating
the control recipe while copying the settings in the master recipe, error may occur.
When this phenomenon occurs, an error-message dialog box may appear while
duplicating the recipe. Therefore, the control recipe is not correctly duplicated.
The following messages may appear in the error-message dialog box.
Can not find the master recipe with the same name of the designated control
recipe.
The common block specified in the control recipe cannot be found.
The data item designated in the control recipe cannot be found.
2. When duplicating a control recipe using the release R2.20 or previous versions,
the batch ID of the original recipe is not displayed in formula.
3. When a CENTUM CS project is connected using multiple project connection pack-
ages, the control recipe can not be duplicated.
G3-46 <G3.6 Exporting Formulas>
IM 33S01B30-01E
G3.6 Exporting Formulas
It is possible to export the formula of the control recipe selected by the user as a
CSV format file. Formulas can be exported in two ways. The formulas can either be
exported manually from the Product Overview window, or they can be exported
automatically when a batch is completed or the command to gather result data
(GATHER) is issued.
Run export
(Exported manually)
For general-purpose
CSV
Format File
For general-purpose For Recipe Builder
Exported automatically
CSV
Format File
CSV
Format File
Exporting Formula Exporting Formula
Master Recipe
Control Recipe
(RESERVED)
Control Recipe
(LOG)
Control Recipe
(READY)
Control Recipe
(ACTIVE)
Control Recipe
(LOG)
Control Recipe
(COMPLETE)
Control Recipe
(COMPLETE)
HIS
FCS
Recipe Setup
Start of
execution
Completion
of execution
Completion
of execution
Deletion
G030601E.EPS
Figure Exporting Formula
<G3.6 Exporting Formulas> G3-47
IM 33S01B30-01E
G3.6.1 Exporting Formulas Manually
It is possible to export the formula of a control recipe manually from the Product
Overview window. This section explains the types of CSV files that can be exported
manually and the operations involved in exporting formulas.
Types of CSV Files that can be Exported
With manual export, it is possible to export two types of CSV files, general-purpose export
files and export files for Recipe Builder.
Which type of file you want to export can be specified when performing export tasks.
General-Purpose Export File
A general-purpose export file is used to save tuned formulas as a file or to analyze formula
data.
Export File for Recipe Builder
An export file for Recipe Builder is used to import data required to create master recipes in
Recipe Builder.
IM 33S01B30-01E
Data that can be Exported
Different data is exported depending on the type of export file. The data exported in each
type of export file is explained below.
Data Exported into a General-Purpose Export File
The following data items are output to a general-purpose export file.
Common Block Name, Data Item, Array 1, Array 2, Value, Display, Comment, Title
IMPORTANT
Common Block Data
All data items of a common block used in a formula are output to a CSV file. Even
when only the name of a common block is entered in the Formula tab of the master
recipe, the limit of records is 30000, all data items of the common block are exported
to the CSV file.
Since a record contains more than one data items thus when exporting the data to the
CSV file, the total number of data items may exceeds the 30000, which is the limit of
the CSV file. When importing the data from the CSV file to the recipe builder, the
exceeded part will be lost.
System-Fixed Common Block
The data items of a system-fixed common block are exported as well, regardless of
whether or not the system-fixed common block is defined in the formula in Recipe
Builder.
Sorting Order of Data Items
The sorting order of data items in the row direction in a CSV file is different from the
order of definitions on Recipe Builder.
Unit Common Block
Even if a unit common block is defined in the formula of the original master recipe
corresponds to the control recipe (defined with unit common block editing mode), the
unit number and operation name are not output to a CSV file. The data entered in the
normal formula, not in the unit common block editing mode, is output to the CSV file.
IM 33S01B30-01E
Data Exported to Export Files for Recipe Builder
The following data items are output to an export file for Recipe Builder.
Unit Recipe No., Operation Name, Tag/Generic Name, Operation ID, Common Block
Name, Data Item, Array 1, Array 2, Value, Display, Comment, Title
IMPORTANT
Common Block Data
Of the common block, only data items defined in the Formula tab of Recipe Builder
are output to a CSV file.If only the name of a common block is defined, only the
common block name is exported, and the data item, arrays, and value are not in-
cluded in the exported data.
Sorting Order of Data Items
The sorting order of data items in the row direction in a CSV file is the same as the
order of definitions in Recipe Builder.
Unit Common Block
Definitions of a unit common block (defined in the unit common block editing mode),
such as the unit recipe number, operation name, tag/generic name, and operation ID,
are also output to a CSV file.
Title Line
The title line defined in the Formula tab of Recipe Builder is also output to a CSV file.
IM 33S01B30-01E
Exporting Result Data
When a formula is exported to a CSV file, data items whose data type is setting value or
parameter are automatically exported. The user must specify whether or not to export
data items whose data type is result data, however. This specification can be made in the
Formula Export dialog box displayed when exporting the formula. The default setting is not
to export result data in the Formula Export dialog box. This default setting can be changed
in Process Management Configuration Builder.
G030602E.EPS
Ready
3 SYSRCM.BATCHID
4 SYSRCM.SYSTEM1
5 SYSRCM.STRTIME
6 SYSRCM.ENDTIME
7 SYSRCM.LOADMODE
8 SYSRCM.STRTMODE
Automatically Generate Formula Export File No
Create Batch-Related Trend CSV File No
Create Batch-Related Trend Binary File No
Message
This setting is valid for both control recipe copy and
formula export dialog boxes.
IMPORTANT
The setting of whether or not to export result data in Process Management Configuration
Builder is used as the default setting of whether or not to copy result data in the Control
Recipe Copy dialog box as well. Moreover, whether or not to export result data when
exporting a formula automatically is also determined by this setting.
SEE ALSO
For how to copy a control recipe, see the following:
G3.5, Duplicating Control Recipe
For how to export formulas automatically, see the following:
G3.6.2, Exporting Formulas Automatically
IM 33S01B30-01E
Recipe Status of Recipes whose Formulas are Exported
Formulas can be exported regardless of the recipe status. However, if the recipe is not in
the RESERVED or COMPLETE status, the setting values, result data, and parameters
existing in an FCS cannot be exported directly. In this case, use the command to gather
result data to acquire each item of the FCS data, and then export the formula; it is possible
to create a CSV file that reflects each data item in the FCS. Click the GATHER button in the
Product Overview window in order to send the command to gather result data.
Storage Location of Exported CSV Files
Exported CSV files are saved in the following folder in the master server.
The storage location of each CSV file cannot be changed, however.
CS 1000/CS 3000 installation top folder\HIS\recipe\Formula
By setting a shared folder name for this folder, it can be accessed from other stations. The
folder can be referenced from other stations using the following access path:
\\Master Server Computer Name\CTMRECP\Formula
Moreover, under the Test Function environment, CSV files are created in the following
folder of the project station:
Project top folder\TestMaster\Master Server Station Name\recipe\Formula
CSV File Name
When exporting a formula, the default file name batch ID.csv is assigned to a CSV file.
This file name can be changed to any desired name when exporting the formula.
Deleting CSV Files
Exported CSV files are not automatically deleted by the system. CSV files must be deleted
by the user.
IM 33S01B30-01E
Procedure for Exporting Formulas
A formula can be exported according to the following procedure.
1. Select a recipe in the Product Overview window, and click the Formula Export Dialog
Box button. The Formula Export dialog box is displayed.
4/4
3 RECIPE01 COMPLETE 01-0009 00/06/23 15:18 00/06/23 18:18
4 RECIPE01 COMPLETE 01-0008 00/06/23 09:26 00/06/23 12:31
READY
G030603E.EPS
BATCH ID 01-0009 Master Server HIS0124
\\BATCH1\CTMRECP\Formula
01-0009.CSV
Save in
File name
Export Result Data
Export File Type
For General Purpose For Recipe Builder
Reset
Export
Formula Export Dialog Box button
Formula Export Dialog Box
Gather Recipe Result Data button
Figure Product Overview Window and Formula Export Dialog Box
2. Enter a CSV file name as required. To export the result data of the recipe as well,
check the [Export Result Data] check box. If this check box is unchecked, the result
data is not exported.
3. Select the type of export file. [For General Purpose] has been selected by default.
4. Click the [Export] button in the Formula Export dialog box. The formula of the selected
recipe is exported.
IMPORTANT
When connecting to CENTUM CS with multiple projects connected, formula export cannot
be performed.
IM 33S01B30-01E
G3.6.2 Exporting Formulas Automatically
It is possible to export a formula automatically when a batch is completed (the
recipe status of a control recipe is LOG) or the command to gather result data is
issued from the Product Overview window via the specification made in Process
Management Configuration Builder. Only general-purpose export files can be ex-
ported automatically.
SEE ALSO
For more information about general-purpose export files, see the following:
Specification of Automatic Export in Process Management Configura-
tion Builder
Automatically Generate Formula Export File
To export a file automatically when a batch is completed (the recipe status of a control
recipe is LOG) or the command to gather result data is executed, specify [Yes] in [Automati-
cally Generate Formula Export File] in the Recipe Group tab of Process Management
Configuration Builder. [No] has been selected by default.
Exporting Result Data
Data items whose data type is setting value or parameter are automatically output to a CSV
file. However, whether or not to export data items whose data type is result data must be
specified in Process Management Configuration Builder.
To export result data, specify [Included] in [Result data when copying/exporting control
recipe] in the Recipe Group tab of Process Management Configuration Builder. [Not in-
cluded] has been selected by default.
IMPORTANT
The setting of whether or not to export result data in Process Management Configuration
Builder is also used as the default setting of whether or not to copy result data in the Con-
trol Recipe Copy dialog box that appears when copying a control recipe, as well as in the
Formula Export dialog box that appears when manually exporting a formula.
SEE ALSO
For how to copy a control recipe, see the following:
G3.5, Duplicating Control Recipe
For how to export formulas manually, see the following:
IM 33S01B30-01E
Storage Location of Automatically Exported Files
Automatically exported CSV files are saved in the following folder in master server. The
storage location of each CSV file cannot be changed, however.
CS 1000/CS 3000 installation top folder\HIS\recipe\Formula
By setting a shared folder name for this folder, it can be accessed from other stations. The
folder can be referenced from other stations using the following access path:
\\Master Server Computer Name\CTMRECP\Formula
Moreover, under the Test Function environment, CSV files are created in the following
folder of the project station:
Project top folder\TestMaster\Master Server Station Name\recipe\Formula
Names of Automatically Exported Files
The name of an automatically exported file is fixed as batch ID_00.csv. It is not possible to
change the names of automatically exported files.
Deleting Automatically Exported Files
Automatically exported CSV files are deleted when the control recipe of the corresponding
batch ID is deleted.
<G3.7 Security Settings of Process Management> G3-55
IM 33S01B30-01E
G3.7 Security Settings of Process Management
The security settings of the HIS basically dictate the process management security
settings. This section describes the security settings specific to process manage-
ment. Security settings for process management should be specified for formula
data, control recipes, and user authentication.
Security Settings for Formula Data
Whether or not a user logged on to the HIS can access formula data is determined by the
privilege level of the user and the access level of the formula data.
The access level is a number in the range from 1 to 8 indicating the level of security re-
quired in order to write to/read from formula data.
The access level is determined by the recipe security level defined for each recipe and
the data security level defined for each data item of a common block.
Flow of Allowing/Prohibiting Access
The figure below shows the flow of determining whether user access to formula data is
allowed or prohibited.
G030701E.EPS
Access Levels Users privilege levels
Access is allowed or prohibited
Recipe security levels Data security levels
Figure Flow of Allowing/Prohibiting Access to Formula Data
G3-56 <G3.7 Security Settings of Process Management>
IM 33S01B30-01E
Determining Access Level
The recipe security level can be defined in the Recipe Header tab of Recipe Builder. The
recipe security level can be set to a level from 1 to 8.
The data security level, on the other hand, should be defined for each data item of a com-
mon block in Common Block Builder. The data security level can be set to a level from 1 to
8.
Note that the security levels of data items in a system-fixed common block are fixed for
individual data items.
The access level is determined by the recipe and data security levels.
The table below shows how the access level is determined by two types of security levels.
Table Access Levels Determined by Recipe Security Levels and Data Security Levels
Access Levels
(cannot be changed)
G030702E.EPS
Recipe security level
Data security level
1
2
3
4
5
6
7
8
1
1
1
4
1
2
3
8
1
1
2
4
1
2
3
8
1
2
2
4
1
2
3
8
2
2
2
4
1
2
3
8
4
4
4
4
1
4
4
8
6
6
6
6
5
6
6
8
7
7
7
7
6
7
7
8
8
8
8
8
8
8
8
8
1 2 3 4 5 6 7 8
IM 33S01B30-01E
Determining whether to Allow/Prohibit Access by Access Levels and Privi-
lege Levels
The system provides three privilege levels, S1, S2, and S3. It is possible to add seven
privilege levels U1 to U7 to Security Builder as necessary. The privilege levels U1 to U7 are
referred to as user-defined privilege levels.
It is not allowed to change operation and monitoring privileges for the three privilege levels,
S1, S2, and S3. The operation and monitoring privileges for the privilege levels S1, S2, and
S3 are fixed in the system. The operation and monitoring privileges for the user-defined
privilege levels U1 to U7, however, can be changed in Security Builder.
Whether or not a user can access formula data is determined based on the access level
and the users privilege level. The table below shows the relationship between different
access levels and privilege levels.
Table Allowing/Prohibiting Access by Access Levels and User Privilege Levels
G030703E.EPS
Monitoring formula data Operating formula data Access Levels
1
2
3
4
5
6
7
8
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
N
Y
N
N
N
N
N
N
N
Y
Y
N
N
Y
N
N
N
Y
Y
Y
N
Y
Y
N
N
Y
Y
Y
N
Y
Y
N
N
S1 S2 S3 U1 to U7 S1 S2 S3 U1 to U7
Users privilege level
Fixed in the system
(cannot be changed)
Fixed in the system
(cannot be changed)
User-defined privilege levels (can be changed
in the Item Operation tab of Security Builder)
Y: Allowed
N: Prohibited
IM 33S01B30-01E
Security Settings for Control Recipes
Whether or not a user logged on to the HIS can access a control recipe is determined by
the users privilege level and the security level of the recipe.
Flow of Allowing/Prohibiting Access
The figure below shows the flow of determining whether user access to a control recipe is
allowed or prohibited.
G030704E.EPS
Recipe security levels Users privilege levels
Access is allowed or prohibited
Figure Flow of Allowing/Prohibiting Access to a Control Recipe
Determining whether to Allow/Prohibit Access by Security Levels of Reci-
pes and Privilege Levels
The security level of a recipe can be defined in the Recipe Header tab of Recipe Builder.
Recipe security levels 1 to 8 are available.
The system provides three privilege levels, S1, S2, and S3. It is possible to add seven
privilege levels U1 to U7 to Security Builder as necessary. Privilege levels U1 to U7 are
referred to as user-defined privilege levels.
It is not allowed to change operation and monitoring privileges for the three privilege levels,
S1, S2, and S3. The operation and monitoring privileges for privilege levels S1, S2, and S3
are fixed in the system. The operation and monitoring privileges for the user-defined privi-
lege levels, U1 to U7, on the other hand, can be changed in Security Builder.
Whether or not a user can access a control recipe is determined based on the recipe
security level and the users privilege level. The table below shows the relationship be-
tween different recipe security levels and privilege levels.
Table Allowing/Prohibiting Access by Recipe Security Levels and User Privilege Levels
Fixed in the system
(cannot be changed)
Y: Allowed
N: Prohibited
User-defined privilege levels
(can be changed in the Tag view tab of Security Builder)
Fixed in the system
(cannot be changed)
G030705E.EPS
Monitoring control recipes Operating control recipes
Recipe
security level
1
2
3
4
5
6
7
8
Y
Y
Y
Y
Y
N
N
N
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
N
N
N
N
N
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
N
Y
N
N
Y
Y
Y
Y
N
Y
N
N
S1 S2 S3 U1 to U7 S1 S2 S3 U1 to U7
Users privilege level
IM 33S01B30-01E
Operating and Monitoring Control Recipes Protected by Security Settings
The items shown below are protected by security settings when monitoring control recipes:
Displaying a recipe in the Recipe List dialog box
Displaying the Recipe Header dialog box
Displaying the Formula dialog box
Printing batch reports
The items shown below are protected by security settings when operating control recipes:
Reserving a recipe
Downloading a recipe
Starting a recipe
Deleting a recipe
Acquiring recipe result data
Equalizing a recipe
Copying a control recipe
Exporting a formula
Displaying the Procedure window
Displaying the Operator Memo dialog box
IM 33S01B30-01E
Security Protection by User Authentication
It is possible to prevent illegal access and operational mistakes by authenticating a user
when the user enters a formula or performs an operation on a control recipe, such as
reserving a recipe or downloading a recipe. The Password Required for Confirmation
dialog box and the Double Authenticated Confirmation dialog box are provided as means of
authenticating a user.
SEE ALSO
For information about the Password Required for Confirmation dialog box, see the following:
Confirmation with Password Dialog Box in Password in F9.1, User
For information about the Double Authenticated Confirmation dialog box, see the following:
Double Authenticated Confirmation Dialog Box in Password in F9.1, User
User Authentication with the Password Required for Confirmation Dialog
Box
In the Password Required for Confirmation dialog box, the user is required to enter the
password again, thereby allowing to confirm again that the user is authorized to perform
the desired operation, such as entering a formula.
G030706E.EPS
Temp. = 98.0 ?
Name :
Password:
Reason :
TANAKA
********
Figure Password Required for Confirmation Dialog Box
The Password Required for Confirmation dialog box can be used according to the following
procedure.
1. Specify [Entry with Acknowledgment] in the Data check method field of Common
Block Builder.
2. Click the [Security Policy Setting] button in the General tab of the HIS Utility. This
button can only be operated by users with the Windows administrator privilege level.
When this button is clicked, the Security Policy Setting dialog box appears.
3. Enable the [Password Required for Confirmation] check box in the Security Policy
Setting dialog box.
IM 33S01B30-01E
User Authentication with the Double Authenticated Confirmation Dialog
Box
The Double Authenticated Confirmation dialog box is used to determine whether a certain
operation is allowed or prohibited though confirmation by two users, i.e., the user logged on
to the HIS and another user. This is useful when granting a permission to perform certain
crucial operations, such as entering an important formula or downloading a recipe.
There is no difference in the privilege levels of users entered in [Name1] and [Name2] in
the Double Authenticated Confirmation dialog box. As long as the user name entered in
[Name2] in the Double Authenticated Confirmation dialog box is different from the one
entered in [Name1] and other than those provided by default (OFFUSER, ONUSER, and
ENGUSER), double authentication can be made by either user.
G030707E.EPS
Load 01-0033 OK ?
Name1 :
Password:
Reason :
TANAKA
********
Name2 :
Password:
Reason :
Figure Double Authenticated Confirmation Dialog Box
The Double Authenticated Confirmation dialog box can be used according to the following
procedure.
1. Specify [Entry with Acknowledgment] in the Data check method field of Common
Block Builder.
2. Specify [Yes] in the Double Authentication field of Common Block Builder.
To specify double authentication for recipe operations such as reservation and down-
load of a recipe, specify double authentication for STATUS for a data item of common
block SYSRCM (system-fixed common block for recipe) or SYSPCMnn (system-fixed
common block for unit recipe).
3. Click the [Security Policy Setting] button in the General tab of the HIS Utility. This
button can only be operated by users with the Windows administrator privilege level.
When this button is clicked, the Security Policy Setting dialog box appears.
4. Enable the [Password Required for Confirmation] check box in the Security Policy
Setting dialog box.
G3-62 <G3.8 Dual-Redundancy>
IM 33S01B30-01E
G3.8 Dual-Redundancy
Process Management can perform operation and monitoring on multiple HISs. The
clienr/server configuration can be established among the HISs installed with Pro-
cess Management. The user may operate or monitor the same data from any HIS
console without considering where the recipe data resides. The server may be set to
master server or backup server.
<G3.8 Dual-Redundancy> G3-63
IM 33S01B30-01E
Setup Server and Client Stations
Server Station, Client Station
The definitions on the names of server and client stations on the basis of a recipe group
may be defined on the Process Management Configuration Builder.
Ethernet
HIS
HIS
FCS
G030801E.EPS
Server #1 Server #2
Control bus
HIS
Client
Figure Server and Client Station Configuration
Server Station
On a server station control recipes can be created. Sever station provides the processes
requested from client stations as well as from itself.
For one recipe group, up to two servers can be defined. If only one server station is de-
fined, this server station will be the master server. When two server stations are defined,
one will be the master server while the other will be the backup server.
Server station controls the data of common blocks, master recipes, recipe procedures and
recipe unit procedures. The following files are downloaded to a server station.
Process Management Files
Common Block Files
Trains
Product Controls
Master Recipes
Client Station
On a client station, recipes can be operated and monitored by referencing the data in the
server station. For one recipe group, up to 14 clients can be defined.
In a client station, recipe group may not reside. If no client station is defined, the recipe can
be operated and monitored by server station.
The following files are downloaded to a client station.
Process Management Files
Product Controls
IM 33S01B30-01E
Basic Concept on Control Recipes
Process management is designed to retain active control recipes in an FCS.
The user can set the download mode or start mode to AUT so that a control recipe may be
downloaded to the FCS at the completion of reservation (recipe setup).
Note Points on Server and Client Stations
No changes can be made online to the names of server or client stations. To change
the station name, the user must download the new name changed on Process Man-
agement Configuration Builder to HIS and restart the HIS.
If an HIS station is booted for a recipe group for which two server stations are desig-
nated, both of them are set to the standby mode. In the dialog box to switch server
stations, select the corresponding server station from the two eligible server stations
to set the selected server station to the run mode.
For a recipe group for which only one server station is designated, the HIS station is
always set to the run mode when booted.
<G3.8 Dual-Redundancy> G3-65
IM 33S01B30-01E
Equalizing Control Recipe among Servers
Up to two HISs may be designated for each recipe group as server stations. However,
during the running of process management function, the two HISs do not work as a server
together, but rather, one function as a master server and the other as a backup server.
If two stations are designated as servers, control recipes are equalized between these two
server stations.
The control recipes are equalized by each recipe group.
Equalizing control recipe is performed automatically when the recipe setup (RE-
SERVED) or batch execution (LOG) is complete.
If a formula is modified after batch setup but before recipe downloading, or after
execution (COMPLETE), the modified data are equalized.
Switching Backup Server to Master Server or vice versa can be performed manually
for each recipe group.
IMPORTANT
For the recipe groups that do not have backup server or when the backup server fails, the
recipe groups are not equalized between servers. When the failed backup server recovers,
the failed equalization tasks are not performed automatically. If a recipe is modified or
executed during the backup server failure, the recipe can not be used when the backup
server is switched to master server.
Running of Control Recipe
After recipe setup, the formula data are stored in the control recipe in the HIS. When
downloading the recipe, the formula data are downloaded to the common blocks in FCS.
When batch is complete (control recipe status becomes LOG), the formula data in the
common blocks are uploaded to the HIS.
G030802E.EPS
Master
Recipe
HIS Master Server
FCS
Recipe Setup
Start End
End
Control
Recipe
(RESERVED)
Control
Recipe
(LOG)
Control
Recipe
(COMPLETE)
HIS Backup Server
End
Download
Equalize Equalize
Upload
Delete
Control
Recipe
(RESERVED)
Control
Recipe
(LOG)
Control
Recipe
(COMPLETE)
Control
Recipe
(COMPLETE)
Control
Recipe
(LOG)
Control
Recipe
(READY)
Control
Recipe
(ACTIVE)
Figure Running of Control Recipe
IM 33S01B30-01E
Manually Equalizing Control Recipe
Control recipe can be manually equalized using the EQUALIZE function on the Product
Overview window. By this operation the equalization can be performed even when the
recipe only exists in the master server but not in the backup server.
Actions when Server is Abnormal
When master server fails, the unit recipe downloaded to the FCS may complete its execu-
tion without effect. But the succeeding unit recipe can not start and the result data gather-
ing can not be performed.
When two stations are used as servers, manually switching the backup server to master
server may continue the process. Server switching may be carried out on the server switch-
ing dialog box of the product control window.
The following methods may be used to continue the process.
Starting the Succeeding Unit Recipe
The running unit recipe can complete its procedures even when the master server fails.
However, upon completion of the current unit recipe, the succeeding unit recipe cannot be
downloaded due to the unavailability of control recipes on the failed server. At this moment,
no system alarm occurs. To report this processing suspension to the HIS, write a SEBOL
program for monitoring the unit recipe execution.
The succeeding unit recipe may be started manually using start command START.
Gathering the Result Data
When server fails before gathering the result data, the data can not be gathered, so that the
unit recipe will be kept in LOG status.
To gather the result data, manually execute the GATHER command after the master server
has returned to its normal state. The unit recipe is still in LOG status even when gathering
completed.
Executing the END command may transit the status from LOG to COMPLETE.
<G3.9 Batch Related Trend Management> G3-67
IM 33S01B30-01E
G3.9 Batch Related Trend Management
Batch related trend management is a function used to link the process management
of a batch and the trend function of the HIS in order to output trend data related to
the batch to a file and display it in the Trend window of the HIS.
By linking a batch and the trend function of the HIS, it becomes possible to output
the trend file acquired by the HIS when the batch is completed or the command to
gather result data is issued. This output file is referred to as a batch related trend
file. This file makes it possible to externally store the trend data related to the batch.
Moreover, by using a batch related trend file, it is possible to display a trend graph of
the process data related to the batch in the Trend window of the HIS. This Trend
window associated with the batch is called the Batch-Related Trend window.
IMPORTANT
Batch-related trend files will not be created if an ICS of CENTUM CS is the recipe server in
the multiple project connection.
G030901E.EPS
TRTANK Tank A -Expert Trend Viewer
100% 00:04:20
10:00 10:01 10:02 10:03 10:04
12/03/2000
FIC001. PV
Inlet flow
(100.0%)
( 0.0%)
1
1
FIC002. PV
Outlet flow
2
2
LIC100. PV
Level
3
3
TIC100. PV
Temp A
4
4
TIC200. PV
Temp B
5
5
6
6
7
7
8
8
80.0
60.0
40.0
20.0
0.0
100.0
72.1 M3/H
53.3 M3/H
3.8 M
25.7 DEGC
14.1 DEGC
1 Sec.
1 Sec.
10 Sec.
1 min.
1 min.
0.0 0.0 0.0 0.0 0.0
1 2 3 4 5
6 7 8
100.0 100.0 10.0 100.0 100.0 10:02:20 Sampling
Period
1
2
Ready
File Edit Display
Trend Data Acquisition
Trend Display
Process Management
Standard Operation and
Monitoring Function
For external
storage
For displaying the trend
of a completed batch
Batch related
trend file
(CSV format)
File creation function
Association with a batch ID
Extraction of data according to the
batch execution time
Trend Data
File
Batch related
trend file
(binary format)
The batch is
executed
After a batch is
completed
Figure Batch Related Trend Management
G3-68 <G3.9 Batch Related Trend Management>
IM 33S01B30-01E
G3.9.1 Batch Related Trend File
A batch related trend file can be generated automatically when the batch is com-
pleted or the command to gather result data is issued by specifying it in the builder
in advance. There are two file format types for batch related trend files, batch
related trend CSV file and batch related trend binary file.
A batch related trend CSV file is used to externally store the trend data related to the
batch. A batch related trend binary file is used to display the Batch-Related Trend
window.
Units of Batch Related Trend Data Acquisition
Batch related trend data can be acquired for each unit, unit recipe, and recipe. Trend
acquisition pens are assigned to batch related trend files according to these acquisition
units.
For each unit
Specified to acquire trend data for each device related to a unit.
For each unit recipe
Specified to acquire the same trend data when any unit instrument is used. It can also
be specified to acquire trend data for each unit recipe.
For each recipe
Specified to acquire trend data covering multiple unit recipes while executing a batch.
Number of Batch Related Trend Files
It is possible to assign up to four HIS Trend windows for each acquisition unit. A batch
related trend file is created for each Trend window.
Up to four Trend windows per unit
Up to four Trend windows per unit recipe
Up to four Trend windows per recipe
IM 33S01B30-01E
Definitions Necessary to Create Batch Related Trend Files
The following items must be defined in order to create a batch related trend file:
Specification of creating a batch related trend file
Assignment of trend acquisition pens
Association of a batch with a trend function
Specification of Creating a Batch Related File
Create Batch-Related Trend CSV File, Create Batch-Related Trend Binary File
Whether or not to output a batch related trend file when the batch is completed or the
command to gather result data is issued can be specified in the Recipe Group tab of
Process Management Configuration Builder.
It is possible to specify whether or not to create a batch related trend CSV file and a binary
file. It is also possible to create a batch related trend CSV file in such a way that data can
be stored for a long period of time.
G030902E.EPS
Ready
3 SYSRCM.BATCHID
4 SYSRCM.SYSTEM1
5 SYSRCM.STRTIME
6 SYSRCM.ENDTIME
7 SYSRCM.LOADMODE
8 SYSRCM.STRTMODE
Automatically Generate Formula Export File No
Create Batch-Related Trend CSV File No
Create Batch-Related Trend Binary File No
Message
Specify your choices here.
Specification to create a batch related trend CSV file
Select either No, Yes, or Long-term. No has been selected by default.
Specification to create a batch related trend binary file
Select either No or Yes. No has been selected by default.
IM 33S01B30-01E
Assignment of Trend Acquisition Pens
Assign the process data whose trend is to be displayed to pens in Trend Acquisition Pen
Assignment Builder of the HIS, the master server of the recipe. Pens must be assigned for
each acquisition unit of batch related trend data.
TIP
A batch related trend file is created for each Trend window.
Association of a Batch with a Trend Function
A batch should be associated with a trend function in order to link the process management
of the batch and the trend function of the HIS. This association can be made by associating
a Trend window name in the HIS with a unit instrument or common block for each acquisi-
tion unit of batch related trend data. The table below lists the data acquisition units to be
associated and their specification locations and items.
Table Association between Batches and Trends
G030903E.EPS
Data acquisition unit Specified location Specified item
For each unit
For each recipe
A user-defined data item of the unit
instrument
RP_TREND[1] to RP_TREND[4] (*1)
A data item of the system-fixed
common block SYSPCMnn for the unit
recipe RP_TREND[1] to RP_TREND[4]
A data item of the system-fixed common
block SYSRCM for the recipe
RP_TREND[1] to RP_TREND[4]
Trend window name
Trend window name
Trend window name
*1: The data items of unit instruments RP_TREND[1] to RP_TREND[4] are user-defined data items. The data type must be
CHR16. Batch-related trend data files will not be created for each unit if these data items are not defined.
IMPORTANT
The batch-related trend data files will not be created if the data item RP_TREND[ ] is
null.
If data acquisition is specified for both units and unit recipes, a batch related trend file
is created for each of them.
Note that even when the association between a batch and a trend function is changed
(i.e., changing the window name for data item RP_Trend[ ]) after the completion of a
batch, the batch related trend file for the corresponding batch is not affected.
IM 33S01B30-01E
Batch Related Trend CSV Files
A batch related trend CSV file output for each batch ID that contains the trend data ex-
tracted according to the batch ID and batch execution time from the trend data acquired
from the HIS, the master server of the recipe.
Trend Formats of Batch Related Trend CSV Files
A batch related trend CSV file can be created using the following trend formats:
Continuous-Rotary type
Batch-Stop type
Batch-Rotary type
Trend acquired by other HIS
Batch Execution Time and Association with Trend Data
The batch execution time can be obtained from the execution start date/time and execution
end date/time shown in the table below. The trend data acquired within this batch execution
time is output as a batch related trend CSV file.
Table Batch Execution Time
G030904E.EPS
Specified unit Acquisition time
For each unit
For each recipe
Obtained from the following data items of the system-fixed common block
SYSPCMnn for the unit recipe.
STRTIME (execution start date/time)
ENDTIME (execution end date/time)
SYSPCMnn for the unit recipe.
SYSRCM for the recipe.
IM 33S01B30-01E
Support for Long-Term Data Storage
There are two types of HIS trends, a normal trend and a trend supporting long-term data
storage. A batch related trend CSV file can acquire not only the normal trend data, but also
data for a long-term data storage file. Whether or not to set up a batch related trend CSV
file to support long-term data storage can be specified in the Recipe Group tab of Process
Management Configuration Builder. The table below shows how to make the file support
long-term data storage.
Table Operations Performed on a Long-Term Data Storage File
G030905E.EPS
Specification in Process
Management
Configuration Builder
Number of sampling
points from the
start time to the end time
Operation
Create a file that
supports long-term
data storage
Do not create a file that
supports long-term data
storage
More than 2880 points
More than 2880 points
2880 points or less
2880 points or less
It is possible to acquire all the data from the
start to end times of a recipe/unit recipe.
It is possible to acquire 2880 data items
before the end time of the recipe/unit recipe.
IMPORTANT
Once a file is set up to support long-term data storage, a large amount of data is processed
when a batch is completed or the command to gather result data is issued. As a result, the
the PC may be overloaded temporarily.
Storage Location of Batch Related Trend CSV Files
Batch related trend CSV files are stored in the following location of the HIS, the master
server of the recipe.
System installation destination directory\his\recipe\Trend
Names of Batch Related Trend CSV Files
The names of batch related trend CSV files are automatically assigned as follows accord-
ing to the batch ID, unit recipe No., and acquisition unit.
BatchID_UnitRcpNo_DetailID.csv
BatchID: Batch ID
UnitRcpNo: Unit recipe number (00 to 32)
DetailID: Acquisition unit
For each unit (U1 to U4)
For each unit recipe (P1 to P4)
For each recipe (R1 to R4)
IM 33S01B30-01E
Batch Related Trend Binary File
A batch related trend binary file is output in binary format for each batch ID that contains
trend data acquired by the HIS, the master server of the recipe. A batch related trend binary
file is used to display the Batch-Related Trend window for an already completed batch.
Trend Format of Batch Related Trend Binary Files
Use the batch-stop type trend format for batch related trend binary files.
Note that the maximum number of data items that can be placed in a batch-stop type file is
2880. Specify a trend acquisition period so that the number of data points acquired from
the batch start to end is no more than 2880.
Batch Execution Time and Association with Trend Data
While the batch execution time determines the range of trend data output to a batch related
trend CSV file, the batch execution time is not used for batch related trend binary files. For
this reason, to acquire trend data in the range determined by the batch execution time for a
batch related trend binary file, it is necessary to define the start and end of the trend acqui-
sition explicitly using the batch-stop type trend format with SEBOL or similar.
IM 33S01B30-01E
Timing of Batch-Related Trend Data File Creation
Batch-related trend data files are created automatically at the following timings:
When the recipe status changes to LOG
A batch-related trend data file is created for each recipe when the recipe status
changes to LOG.
When the unit recipe status changes to LOG
A batch-related trend data file is created for each unit instrument and unit recipe when
the unit recipe status changes to LOG.
When the command to gather result data of a recipe (GATHER) is issued
A batch-related trend data file is created for each unit instrument, unit recipe and
recipe if the command to gather result data is issued while the recipe status is ACTIVE
or ABORTED.
Table Batch-Related Trend Data File Created when the GATHER Command Is Issued
G030906E.EPS
Recipe status Unit recipe status Acquisition unit Created files
There are unit recipes
whose status is ACTIVE.
There are no unit recipes
whose status is ACTIVE.
When the status of a unit
recipe becomes ABORTED
during execution
When the status of a unit
recipe becomes ABORTED
before it is executed
Unit instrument
Unit recipe
Recipe
Unit instrument
Unit recipe
Recipe
Unit instrument
Unit recipe
Recipe
Unit instrument
Unit recipe
Recipe
Operating (RUNNING)
unit instruments
Unit recipes whose
status is ACTIVE
Recipe
Recipe
Operating (ABORTED)
unit instruments
Operating (ABORTED)
unit recipes
Recipe
Recipe
Trend time recorded
From when the status of the
unit instrument becomes
RUNNING to when the
GATHER command is issued
unit recipe becomes ACTIVE
to when the GATHER
command is issued
Form when the status of the
recipe becomes ACTIVE to
when the GATHER command
is issued
Form when the status of the

when the GATHER command
is issued
From when the status of the unit
instrument becomes RUNNING
to when it becomes ABORTED
From when the status of the unit
when it becomes ABORTED

ACTIVE
ACTIVE
ABORTED
ABORTED
IM 33S01B30-01E
IMPORTANT
If the trend format is of the batch type, and a recipe reuses the same trend as another
unit recipe whose status has just become COMPLETE, the trend data acquired so far
may be deleted. To use a trend of the same batch type continuously, it is necessary to
delay the acquisition start time of the trend, or delay the start time of a unit using
SEBOL or similar (approximately five seconds).
If the trend format is of the batch type, and the same trend is reused before the com-
mand to gather result data is issued when the status of a recipe or unit recipe is
ABORTED, the trend data acquired so far is deleted.
If the status of a recipe or unit recipe becomes ABORTED, the corresponding batch
related trend file is not created. Issue the command to gather result data before the
time of the continuous trend advances or the batch trend is reused in order to create
the batch related trend file.
A batch related trend file created by issuing the command to gather result data is
replaced with the latest batch related trend file when the recipe or unit recipe has
normally been completed.
Deleting Batch Related Trend Files
An automatically created batch related trend file (CSV file/binary file) is deleted if the
control recipe for the corresponding batch ID is deleted.
IM 33S01B30-01E
G3.9.2 Batch-Related Trend Window
The Batch-Related Trend window has a function for displaying trends related to a
batch in the Trend window of the HIS, using the definitions in the batch related trend
file and the batch related trend binary file. This section explains the Batch-Related
Trend window in detail.
Calling the Batch-Related Trend Window
The Batch-Related Trend window can be called from the Product Overview window. Per-
form the following operation in order to call the Batch-Related Trend window.
1. Select a recipe in the Product Overview window, and then click the button for calling
the Trend Window Selection dialog box. The Trend Window Selection dialog box
appears.
4/4
3 RECIPE01 COMPLETE 01-0009 02/06/16 15:18 02/06/16 18:18
4 RECIPE01 COMPLETE 01-0008 02/06/16 09:26 02/06/16 12:31
READY
G030907E.EPS
01-0009 Recipe Group 1
Relation Unit
UT1001
Unit Recipe No.
Unit Name
No. Trend Window Comment
1 TG0101 Block:01 Group:01
2
3
4
Button for calling the Trend
Window Selection dialog box
Trend Window Selection Dialog Box
Figure Product Overview window and Trend Window Selection Dialog Box
IM 33S01B30-01E
2. Select either a unit, unit recipe, or recipe from the [Relation] pull-down menu.
If a unit is specified in [Relation]
Select a unit name from the [Unit Name] pull-down menu. It is not required to specify
anything in the [Unit Recipe No.] text box.
If a unit recipe is specified in [Relation]
Select a unit recipe number from the [Unit Recipe No.] pull-down menu. It is not
required to specify anything in the [Unit Name] text box.
If a recipe is specified in [Relation]
It is not required to specify anything in the [Unit Recipe No.] and [Unit Name] text
boxes.
3. When [Relation], [Unit Recipe No.] and [Unit Name] are specified in the Trend Window
Selection dialog box, a list of the corresponding Batch-Related Trend windows ap-
pears. Double-click the name of the trend window you want to display from the list.
The Batch-Related Trend window appears.
Different trend window names and comments are displayed in the Trend Window
Selection dialog box depending on whether the displayed Batch-Related Trend
windows are for a batch currently being executed or for a batch that has already been
completed. The table below shows the differences.
Table Display of Trend Window Names and Comments in the Trend Window Selection Dialog Box
G030908E.EPS
Trend Window Comment
Batch-Related Trend windows of
a batch currently being executed
Batch-Related Trend windows of
an already completed batch
Names of trend windows currently
defined in the HIS
Display color: Cyan
Names of trend windows defined in the
HIS when the batch was completed
Display color: White
Trend window comments
currently defined in the HIS
Display color: White
No display
IM 33S01B30-01E
Batch Related Trend for a Batch being Executed and Batch Related
Trend for an Already Completed Batch
When the Batch-Related Trend window is called, the window displays either the batch
related trend for a batch currently being executed or for a batch already completed, de-
pending on the recipe status of the batch.
The Batch-Related Trend window for a batch that is currently being executed acquires and
displays the trend data in real time according to the trend definitions in the HIS.
The Batch-Related Trend window for an already completed batch displays the data in the
batch related trend file (batch related trend binary file). The batch related trend for a com-
pleted batch can only be displayed via the batch related trend file created at the completion
of the batch.
The following rules determine whether the Batch-Related Trend window for a batch being
executed or an already completed batch is displayed when the Batch-Related Trend
window is called.
The Batch-Related Trend window appears for a batch currently being executed if the
recipe status is RESERVED to LOG, or the unit recipe status is NO ASSIGNED to
LOG.
The Batch-Related Trend window appears for an already completed batch if the
recipe status/unit recipe status is COMPLETE or ABORTED.
A batch related trend binary file may not have been created at the moment when the
recipe status/unit recipe status switches from LOG to COMPLETE or immediately
after the command to gather result data is issued, meaning that it is not available for
displaying the completed batch trend. In this case, the Batch-Related Trend window
appears for a batch currently being executed.
When the recipe status/unit recipe status is ABORTED, the Batch-Related Trend
window appears for a completed batch if the batch related trend binary file for display-
ing the completed batch has already been created by issuing the command to gather
result data. The Batch-Related Trend window appears for a batch being executed if
the batch related trend binary file for displaying the completed batch has not been
created.
IM 33S01B30-01E
HIS on which Batch Related Trend Management Runs
The batch related trend management runs on an HIS which is the master server of a
recipe. Under normal circumstances, the Batch-Related Trend window can only be dis-
played on an HIS that is the master server of a recipe.
Perform the following operation in order to display the Batch-Related Trend window on an
HIS which is a backup server of a recipe or a client.
1. Define the same trend as the recipe master server HIS in a backup server or client.
Assign the same trend acquisition pen to the same Trend window name as the recipe
master server HIS.
2. Check the [Show Batch-Related Trend Window] check box in the Process Manage-
ment tab of the HIS Setup window. This check box is unchecked (Do not Show) by
default.
This setting is ignored by an HIS which is the master server of the recipe.
Blank Page
<G4. Unit Supervision under Batch Management> G4-1
IM 33S01B30-01E
G4. Unit Supervision under Batch
Management
This chapter explains Unit Supervision with which the unit recipes created in Batch
Management is executed.
Position of Unit Supervision
Unit Supervision is implemented in a unit instrument or operations. The unit instrument
executes the unit procedure, from which the operation is executed. The unit instrument is
available in two types: a resident unit and a nonresident unit.
G040001E.EPS
Process Management
Unit Supervision
Process Control
(Function Blocks)
Production Planning
and Scheduling
Management
Recipe Management
Figure Position of Unit Supervision
Resident Unit
The resident unit instrument has its specific unit procedure. The resident unit instrument is
used when the same manufacturing procedure is fixed. The resident unit instrument can be
called up from the unit recipe.
The resident unit instrument can be used independently from Batch Management.
Nonresident Unit
The nonresident unit instrument does not have its specific unit procedure. Therefore, the
recipe unit procedure created in Recipe Management is used as a unit procedure for the
nonresident unit instrument. The recipe unit procedure uses the operation created in Unit
Supervision. The nonresident unit instrument is used in combination with Batch Manage-
ment.
SEE ALSO
For the details of unit supervision, see the following:
D6, Unit Supervision
G4-2 <G4.1 Nonresident Unit Instrument>
IM 33S01B30-01E
G4.1 Nonresident Unit Instrument
A recipe unit procedure is executed in a nonresident unit instrument. The behavior
of the nonresident unit instrument is explained below.
Unit Recipe and Unit Instrument
The nonresident unit instrument executes the recipe unit procedure in the unit recipe. No
procedures always exist in the nonresident unit instrument. When a unit recipe is down-
loaded to the FCS, its recipe unit procedure is downloaded to the unit instrument. Opera-
tions are started in the unit instrument according to the recipe unit procedure. When the
recipe unit procedure is completed, it is removed from the unit instrument.
G040101E.EPS
Unit recipe
Internal temperature = 120 C
Agitation start time = 1999.05.10 20:15:05
Elapsed time for agitation = 2 h
Agitation error :
Totalized process value = 2391 M3
Unit instrument data
Initialization
Charging A
Heating
1
2
3
Unit procedure
Initialization
Charging A
Heating
2
3
1
Unit instrument
Operation
Operation
Operation
Figure Unit Recipe and Unit Instrument
Nonresident Unit Instrument Model Names
The model names of nonresident unit instruments are given below.
UTAS-N Analog non-resident unit instrument
UTPB-N Non-resident unit instrument with five-pushbutton switch
UTSW-N Non-resident unit instrument with three-pushbutton switch
<G4.1 Nonresident Unit Instrument> G4-3
IM 33S01B30-01E
Starting the Unit Instrument
With the nonresident unit instrument, unit procedures cannot be started by issuing a status
change command to the unit instrument. Unit procedures are started with a START com-
mand issued from the recipe or unit recipe.
System Fixed Data Items Used in Process Management
When the nonresident unit instrument operates under the control of Process Management,
the data are set in the unit instrument data items shown in the table below at the time the
unit instrument starts (when the recipe unit procedure starts). After the unit instrument is
started, even if the values of formula data (common blocks) are changed, they are not
reflected in the unit instrument data.
The data set in the unit instrument when the unit instrument started will be cleared after
execution of the unit instrument is completed (when the status of the unit instrument be-
comes END).
Table Data Items Used by the Process Management
Data item name Data name Data type Entry Default
G040102E.EPS
No: Entry not possible
BATCHID Batch ID CHR*16 No null
USER1 User code 1 CHR*16 No null
RECIPEGR Recipe group number I16 No 0
RECIPE Recipe name CHR*16 No null
PARTNO Unit recipe number I16 No 0
G4-4 <G4.1 Nonresident Unit Instrument>
IM 33S01B30-01E
User Definable Data Items may be Applied to Process Management
Among the user definable data items that may be used with the unit instrument, the follow-
ing items are provided with unique features.
Reserved Batch ID (RP_QUEUE)
For the Reserved Batch ID, the reserved recipe's batch ID and the first queued unit name
are stored. The Reserved Batch ID may be used when using SEBOL to download a recipe
or start a recipe.
When using Reserved Batch ID, it is required to define the array data item for the unit
instrument, and to specify the destination tag name and data items to be set to the Re-
served Batch ID on the Process Management Configuration Builder for each recipe group.
The Reserved Batch IDs are stored in the order of the reservation data and time. The
earlier Reserved Batch IDs correspond to the smaller array element numbers. If the num-
ber of reserved batch IDs is greater than the number of the array elements when setup the
recipe, the later batch IDs and unit names will not be reserved. Furthermore, the batch ID
and unit name whose status changes from RESERVED to READY will be deleted.
The reserved batch ID may be defined on the Unit Instrument Data Item Builder shown as
follows.
Data Item Name: RP_QUEUE (may be modified)
Data Type: CHR16
Array1: 10
Array2: 2
Display Format: 16
To be Executed Batch ID (BIDQUEUE)
For the To be Executed Batch ID (BIDQUEUE), the unit recipe whose status changed to
READY is stored.
To store the batch ID of a unit recipe with the status of READY, array data items must be
defined on the unit instrument.
If the number of the batch IDs stored exceeds that of the array elements, the batch IDs will
be deleted in FIFO manner. Furthermore, the executed batch IDs will be deleted in FIFO
manner upon start of the unit recipe execution.
The To be Executed Batch ID may be defined on the unit instrument data item definition
builder as follows.
Data Item Name: BIDQUEUE
Data Type: CHR16
Array1: 10
Array2: 0
Display Format: 16
<G4.2 Operation> G4-5
IM 33S01B30-01E
G4.2 Operation
Operations created in Unit Supervision can be used as the operations started from
recipe unit procedures.
Common Block Access from an Operation
Operations started from a unit instrument, which is operating under the control of Process
Management, can access formulas (common blocks) with SEBOL scripts in an operation.
And formulas can be read and the statistical data can be stored by the operation.
Operation ID
An operation ID can be specified for the operation on the Recipe Procedure Builder. When
the same operation is started from the recipe unit procedure for several times, the step
from which it was called can be identified by using the operation ID.
Start of Unit Recipe
In the case of a recipe that uses multiple unit instruments, the unit procedure for the next
unit instrument can be started with SEBOL scripts in an operation.
What can be Done from an Operation
Recipes can be set up or started or recipe unit procedures can be started with SEBOL
scripts in an operation.
Blank Page
<G5. Production Planning and Scheduling Interface> G5-1
IM 33S01B30-01E
G5. Production Planning and Scheduling
Interface
This chapter explains the production planning and scheduling interface which
serves as the interface between Production Planning and Scheduling and Process
Management.
What is Production Planning and Scheduling Interface?
Production Planning and Scheduling provides schedule planning to Process Management.
A production planning and scheduling interface is used to exchange information between
Production Planning and Scheduling and Process Management activities. By introducing a
production planning and scheduling interface, Process Management can run a recipe in
accordance with the production planning and scheduling information. The production
planning and scheduling interface is included in Process Management package.
G050001E.EPS
Process Management
Unit Supervision
Process Control
(Function Blocks)
Production Planning
and Scheduling
Interface
Production Planning
and Scheduling
Recipe Management
Management
Figure Position of the Production Planning and Scheduling Interface
TIP
The CS Batch 1000/CS Batch 3000 does not include Production Planning and Scheduling. The schedul-
ing package to be used with Production Planning and Scheduling must be purchased separately.
G5-2 <G5.1 Overview of Production Planning and Scheduling Interface>
IM 33S01B30-01E
G5.1 Overview of Production Planning and
Scheduling Interface
The production planning and scheduling interface is used for exchanging informa-
tion between Process Management and Production Planning and Scheduling.
Overview of Production Planning and Scheduling Interface
The following explains an overview of production planning and scheduling interface.
Schedule Expansion
The schedule expansion function can be used to call a Process Management based on the
fixed schedule created with the Production Planning and Scheduling. With Process Man-
agement, the recipe is automatically set up and executed according to the recipe name,
batch ID and scheduled time for execution start defined in the fixed schedule file.
Batch Progress Information
The batch journal which provides batch progress information can be acquired via the OPC
interface. With Production Planning and Scheduling, highly practical scheduling can be
achieved by reflecting the messages acquired from the batch journal.
TIP
The CS Batch 1000/CS Batch 3000 does not include the OPC interface. To use the OPC interface, the
Exaopc OPC interface package (for installation on an HIS) or the Exaopc OPC interface package is
required.
Conditions for Combining the Elements of Production Planning and
Scheduling
The following conditions must be met when implementing Production Planning and Sched-
uling.
The computer on which the Production Planning and Scheduling is used must be
connected via the Ethernet to the HIS in which Process Management is installed.
Process Management operates in accordance with the schedule created with Produc-
tion Planning and Scheduling.
Process Management uses the batch ID created by Production Planning and Sched-
uling.
The schedule of a recipe cannot be changed once its execution has started.
Process Management can execute a recipe for which scheduling has not been set by
Production Planning and Scheduling.
The time used for scheduling is based on the system time of the HIS.
<G5.1 Overview of Production Planning and Scheduling Interface> G5-3
IM 33S01B30-01E
Production Planning and Scheduling Included System Configuration
The figure below shows a system configuration that contains Production Planning and
Scheduling, Production Planning and Scheduling Interface and Process Management.
Server and client stations can be registered for each recipe group with Process Manage-
ment. The communication destination of Production Planning and Scheduling can be either
a server station or a client station. To communication with multiple server stations or client
stations, all HISs can be specified as communication destinations in Production Planning
and Scheduling.
Ethernet
HIS
FCS
G050101E.EPS
Server #1
Control bus
Supervisory computer
HIS
Server #2
HIS
Client
Production Planning
and Scheduling
Process Management
Production Planning
and Scheduling
Interface
Process Management
Production Planning
and Scheduling
Interface
Process Management
Production Planning
and Scheduling
Interface
Figure Production Planning and Scheduling Included System Configuration
G5-4 <G5.2 Schedule Expansion>
IM 33S01B30-01E
G5.2 Schedule Expansion
The schedule expansion is used to set up the recipe in accordance with the informa-
tion in the fixed schedule file transmitted from Production Planning and Scheduling.
Overview of the Schedule Expansion
Production Planning and Scheduling interface performs schedule expansion in accordance
with the information in the fixed schedule file transmitted from Production Planning and
Scheduling. The schedule expansion executes recipe setup when the specified time
arrives.
Recipe setup is executed in the order described in the fixed schedule file. When the setup
of one recipe is completed, a new executing recipe is added to the Product Overview
window.
Fixed Schedule File
The fixed schedule file resides in the HIS where Process Management is installed. The
fixed schedule file is stored in the location given below under the name of BcsResult.dt.
C:\CS1000\his\save\BatchSchd\(*1)
C:\CS3000\his\save\BatchSchd\(*2)
*1: This is the default location in the CS 1000.
*2: This is the default location in the CS 3000.
This file can be accessed from another computer using \\computer name\CTMSCHD\.
CTMSCHD is the name of a shared folder.
Information for a maximum of 50 batches can be written in the fixed schedule file.
The fixed schedule file is updated each time when a file is transmitted from Production
Planning and Scheduling. When schedule expansion is completed, the file size changes to
0.
<G5.2 Schedule Expansion> G5-5
IM 33S01B30-01E
Precautionary Notes Concerning the Schedule Expansion
Precautions that must be observed when executing the schedule expansion are explained
below.
Recipes are set up in the order they are stored in the fixed schedule file. Therefore, it
is necessary to sort the recipes in the order of scheduled time for execution start.
When automatically starting a recipe or unit recipe using the schedule expansion,
specify the batch mode for the recipe or unit recipe as TIME.
Even when an executing recipe is created after the scheduled time for execution start
has passed, the recipe will be executed if the elapsed time is less than 5 minutes. If an
executing recipe is created after 5 minutes or more have elapsed since the scheduled
time for execution start, the recipe will not be started automatically. In this case,
manually start the recipe from the Product Overview window.
When schedule information for 51 recipes or more have been stored in the fixed
schedule file, schedule expansion will be performed only for the first 50 recipes. There
will be no schedule expansion executed for the 51st recipe and thereafter.
The scheduled time for execution start uses GMT time. Therefore, the scheduled time
for execution start must be converted into the GMT time with the schedule expansion.
Process Management performs automatic start based on the scheduled time for
execution start and the system clock of the HIS.
If the recipe group number in the fixed schedule file is outside the operation and
monitoring scope of the HIS performing the recipe setup, the setup for the correspond-
ing recipes will not be performed.
When a schedule is transmitted to the HIS from Production Planning and Scheduling,
recipe setup will be performed in the HIS within one minute.
The time required for each recipe setup depends on the number of formulas used in
the control recipe. Also, if there are many batches set in the fixed schedule file, it will
take longer time for all recipe setups to be completed.
For the fixed schedule file to be transmitted to the HIS from the supervisory computer,
the HIS user account must be registered on the supervisory computer side so that the
supervisory computer can access the HIS.
G5-6 <G5.2 Schedule Expansion>
IM 33S01B30-01E
Error Handling During Schedule Expansion
When an error occurs during schedule expansion, a system alarm is generated in the HIS.
This system alarm will not send to Production Planning and Scheduling. When multiple
recipes are specified in the fixed schedule file, schedule expansion for the next recipe will
be executed even if an error has occurred during the schedule expansion for the current
recipe. The following explains the causes of errors that may occur during schedule expan-
sion.
Protocol error in the fixed schedule file
Recipe group number error
Recipe name search error
Changed the schedule for a recipe which has already been downloaded
Changed the schedule for a recipe which has already been started
Changed the schedule for a recipe whose execution has already been completed
Identical Batch ID (*1)
Maximum number of reserved recipes exceeded
Error during recipe setup
Batch ID not found when deleting the schedule
*1: An error of identical batch ID maybe caused by rescheduling the same recipe that already setup. Or to rescheduling a
recipe that already setup but the formula is modified after setup.
If rescheduling a recipe with a new recipe name and unit name, the error of identical batch ID does not occur.
Other causes of errors that may occur during recipe setup include duplicate batch IDs,
common block name or data item name not found, or data set by the formula exceeding the
range of upper and lower limit values specified in the Common Block Builder.
<G5.2 Schedule Expansion> G5-7
IM 33S01B30-01E
Redoing the Schedule Expansion
Schedule information can be changed for a recipe once the schedule expansion has been
executed and setup completed. The schedule for a recipe can be changed in two ways: the
schedule items may be changed, or setup is performed again after deleting the executing
recipe.
A recipe can be set up again only when the recipe status is RESERVED. If the recipe
status has already changed to READY or progressed further, changes can no longer be
made to the schedule if they require re-setup.
When schedule expansion has been done again, the display order in the product overview
window will lose agreement with the batch order in the fixed schedule file. Also, in the
second schedule expansion, the formula cannot be changed. To change the formula,
create an executing recipe using a different batch ID, then delete the executing recipe
which is no longer necessary.
Redoing the Schedule Expansion by Deleting the Executing Recipe and
Performing the Setup Again
When modifying the following items, schedule expansion must be performed again after
deleting the executing recipe. The executing recipe can be deleted if the recipe status is
RESERVED.
Recipe group number
Batch ID
Recipe name
Train Name
Unit name for the unit recipe number 1
When the recipe group number or the batch ID has been modified, the executing recipe
with the old batch ID must be deleted. If the executing recipe is not deleted, the executing
recipe with the old batch ID will remain in the product overview window. To delete an
executing recipe, specify request code D in the fixed schedule file or perform a DELETE
operation from the product overview window.
When changing the recipe name, a train name or unit name for the unit recipe number 1,
the executing recipe is automatically deleted after which recipe setup is performed again.
Redoing the Schedule Expansion to Make Modifications without Deleting
the Executing Recipe
Modifications can be made without deleting the existing executing recipe if the recipe status
is RESERVED, READY, or ACTIVE and the unit recipe status is NOASSIGN, AS-
SIGN, or READY. The following items can be modified without deleting the executing
recipe:
Unit name for the unit recipe number 2 and thereafter
Scheduled time for execution start
Scheduled time for execution end
Schedule value
Schedule expansion cannot be repeated for the executing recipes whose execution has
already been completed (COMPLETE) or forcibly terminated (ABORTED). If schedule
expansion is attempted for these recipes, an error will occur.
An error will occur if the scheduled time for execution start is changed for a recipe whose
execution has already been started. Similarly, an error will occur if the scheduled time for
execution start is changed for a unit recipe whose execution has already been started.
G5-8 <G5.3 File Format of Fixed Schedule File>
IM 33S01B30-01E
G5.3 File Format of Fixed Schedule File
The fixed schedule file consists of the header, data and footer sections. The data
section is further divided into the schedule section and the formula section.
Structure of Fixed Schedule File
The following shows the structure of a fixed schedule file.
G050301E.EPS
.
.
.
Header section
Data section
Footer section
Schedule section
ScheduleResult <Creation date and time>
$NUMBER <Total number of recipes>
$SCHEDULE
Recipe for batch 1
Unit recipe
$FORMULA
$END
$SCHEDULE
Recipe for batch 2
Unit recipe
$FORMULA
$END
$SCHEDULE
Recipe for batch n
Unit recipe
$FORMULA
$END
$COMPLETE
Formula section
Figure Structure of a Fixed Schedule File
<G5.3 File Format of Fixed Schedule File> G5-9
IM 33S01B30-01E
Schedule File Protocol
The elements of the file are described with character strings, numeric characters, control
symbol, date and time, and delimiter symbol.
Character String
The character codes used in character strings are based on the Shifted JIS.
Control Symbol
The control symbol is $. The character string that begins with the control character has a
special meaning.
Add $ at the beginning, then specify GMT time using hexadecimal notation. GMT time
indicates time expressed in total seconds from 00:00:00, January 1, 1970
G050308E.EPS
1999.5.8 18:12:32
Convert to total number of seconds counted
from 00:00:00 of Jan,1st 1970 GMT.
Convert the number into hexadecimal
926154752
0x37340000
Delimiter Symbol
Tab <tab> is used to delimit the data items.
End of Line Symbol
CR+LF is used to indicate end of line.
Comment Symbol
The comment symbol is %. The character string that begins with the comment symbol is
interpreted as a comment line.
IM 33S01B30-01E
Format of the Header Section
The format and constituents of the header section are explained below.
G050302E.EPS
ScheduleResult <Creation date and time>
$NUMBER <Total number of recipes>
<Creation date and time> Specifies the date and time the schedule file was created.
<Total number of recipes> Specifies the number of recipes in the data section.
ScheduleResult
ScheduleResult is the file identifier.
$NUMBER
$NUMBER is the control terminology indicating the total number of recipes.
IM 33S01B30-01E
Format of the Schedule Section
The constituents of the schedule are explained below.
G050303E.EPS
$SCHEDULE<Request code>
<Recipe group number-recipe name><Batch ID><Train name><Schedule value>
<Scheduled time for execution start><Scheduled time for execution end><*>
<Unit recipe number><Unit name><Schedule value><Scheduled time for execution start>
<Scheduled time for execution end>
<Unit recipe number><Unit name><Schedule value><Scheduled time for execution start>
.
.
.
<Request code> Specifies whether to set the schedule using the schedule
expansion faction or delete the schedule.
E: Set schedule
D: Delete executing recipe
When the request code is omitted, the operation is interpreted as
Set schedule.
<Recipe group number-recipe name>
Specifies the recipe group number to be executed and the master
recipe name.
<Batch ID> Specifies the batch ID to be appended to the executing recipe during
recipe setup.
<Train name> Specifies the name of the train for execution. If train is not used, (*)
can be specified.
<Schedule value> Specifies the production amount for the recipe or unit recipe
determined by the schedule.
<Scheduled time for execution start>
Specifies the date and time the processing of the recipe or unit recipe
is scheduled to start. The scheduled time for execution start is
specified by GMT time expressed in hexadecimal notation preceded
by a $.
Specifies the date and time the processing of the recipe or unit recipe
is scheduled to end. The scheduled time for execution end is |
specified by GMT time expressed in hexadecimal notation preceded
by a $. The scheduled time for execution end is used as a guideline
for operation and will not be used in the process management function.
<Unit recipe number>
Specifies the unit recipe number for the unit recipe used in the
equipment requirement.
<Unit name> Specifies the unit name used in the unit recipe.
<*> Specifies asterisk (*).
IM 33S01B30-01E
$SCHEDULE
The control terminology indicating the start of the schedule section.
Recipe Schedule Information
The information contained in <Recipe group number-recipe name> through <Scheduled
time for execution end><*> is called recipe schedule information. One set of recipe sched-
ule information is defined for each recipe.
Unit Recipe Schedule Information
The series of information contained in <Unit recipe number> through <Scheduled time for
execution end> is called unit recipe schedule information. Unit recipe schedule information
is specified for the number of unit recipes used in one recipe.
Unit recipe schedule information can be omitted. If unit recipe schedule information is
omitted, the unit name specified at the top of the equipment requirement defined in the
master recipe is assigned.
Information Set in the Common Block
When recipe setup is completed, the values set in the schedule section are written to the
data items in the system fixed common blocks. The data item names for the common
blocks where the schedule information is set are given in the table below.
Table Common Block Data Item Names to be Set
G050304E.EPS
Recipe group number SYSRCM RECIPEGR I16
Item Classification Common block name Item name Data type
Unit recipe
Recipe
Schedule value
Scheduled time for
execution end
Scheduled time for
execution start
Unit name SYSPCMnn (*2) UNITNAME CHR16
Time of rescheduling (*1) SYSRCM SCHDTIME U32
Schedule value SYSRCM SCHEDULE CHR16
Scheduled time for
execution end
Scheduled time for
execution start
Batch ID SYSRCM BATCHID CHR16
Train name SYSRCM TRAIN CHR16
Recipe name SYSRCM RECIPE CHR16
SYSRCM STRSTIME U32
U32 ENDSTIME SYSRCM
U32 STRSTIME SYSPCMnn (*2)
U32 ENDSTIME SYSPCMnn (*2)
CHR16 SCHEDULE SYSPCMnn (*2)
*1 The value is set when schedule expansion is performed again with the same batch ID
*2 nn: unit recipe number
IM 33S01B30-01E
Format of the Formula Section
When the formula section is specified, a value can be set in a user definable common block
used in the executing recipe. In the formula section, up to 1,000 data can be set per one
recipe. The format and constituents of the formula section are explained below.
G050305E.EPS
$FORMULA
#<Common block name 1>
<Common block data item name 11><Value for item 11>
.
.
#<Common block name 2>
.
.
#<Common block name n>
<Common block data item name n1><Value for item n1>
<Common block data item name n2><Value for item n2>
.
.
<Common block data item name nm><Value for item nm>
$END
<Common block name> Specifies the common block name that sets the data.
The common block names can be specified in any order.
<Common block data item name>
When the common block data item is an array element,
a data value is specified for each array element.
Two-dimensional element: Common block data item
name [X,Y]
One-dimensional element: Common block data item
name [X]
<Item value> If the item value is a numeric value, it can also be
specified in exponential format.
$FORMULA
$FORMULA is the control terminology indicating the start of the formula section. When the
formula is omitted, $FORMULA need not be specified.
$END
$END is the control terminology indicating the end of the formula section or the schedule
section. $END is necessary even if the formula section is omitted.
IM 33S01B30-01E
Format of the Footer Section
The format and constituents of the footer section are explained below.
G050306E.EPS
$COMPLETE
$COMPLETE
$COMPLETE is the control terminology indicating the end of the schedule file. $COM-
PLETE cannot be omitted. If there is no footer section, the schedule file is identified as an
incomplete file and recipe setup will not be performed.
IM 33S01B30-01E
Specification Example of the Fixed Schedule File
A specification example of the fixed schedule file is given below.
G050307E.EPS
ScheduleResult $37340000
$NUMBER3
%
%***Schedule expansion1_there is a formula section***
$SCHEDULE E
1-RCP0001 BATCH-0101 * 110.5 $37341930 $37345134 *
1 UNIT01 38.4 $37341930 $3734228F
2 UNIT02 128.5 $37342998 $373431EE
$FORMULA
#SYSRCM
USER1 PRODUCT-A
USER2 LOT-1099
#COMM0001
USER01 Catalyst A
USER02 100.6
USER03[10,9] 28.6
#COMM0002
USER01 Charging A
USER02 200.5
$END
%
%***Schedule expansion2_there is no formula section***
$SCHEDULE E
2-RCP0777 BATCH-0201 * 490.6 $37356AB0 $3735A2B4 *
1 UNIT03 38.4 $37356AB0 $3735740F
2 UNIT04 128.5 $37357B18 $3735836E
$END
%
%***Schedule expansion3_schedule deleted***
$SCHEDULE D
1-RCP0001 BATCH0102
$END
$COMPLETE
Blank Page
<G6. Production Information Management> G6-1
IM 33S01B30-01E
G6. Production Information Management
This chapter explains Production Information Management.
What is Production Information Management?
Production Information Management is positioned at the same level as Recipe Manage-
ment and Production Planning and Scheduling. The OPC interface is used for the interface
with Process Management, Unit Supervision and function blocks. Production Information
Management is used to acquire, save, process and report information related to the manu-
facturing of product.
G060001E.EPS
Process Management
Unit Supervision
Process Control
(Function Blocks)
OPC interface
Production Planning
and Scheduling
Management
Recipe Management
Figure Position of Production Information Management
TIP
The CS Batch 1000/CS Batch 3000 does not include the OPC interface.
To use the OPC interface, the Exaopc OPC interface package (for installation on an HIS) or the Exaopc
OPC interface package is required.
G6-2 <G6.1 Overview of Production Control Information Management>
IM 33S01B30-01E
G6.1 Overview of Production Control Information
Management
This section gives an overview of Production Control Information Management.
Information that can be Acquired as Production Control Information
The following information can be acquired as production control information.
Product List Information
The batch ID, recipe status, unit recipe status and other information regarding the recipe
currently being executed can be acquired.
Batch Statistical Data
The recipe header, formula and other information regarding the recipe that has been
already executed can be acquired from Process Management.
Batch Journal
The alarms and operation record messages generated during batch execution are saved to
the historical message report file with a batch ID appended to each alarm/message. The
saved historical messages can be acquired using the batch ID as the key.
Interface Used in Production Information Management
The OPC interface is used for the interface between Production Information Management
and Process Management. Production control information can be acquired by combining
the OPC interface and report package or CENTUM data access library.
SEE ALSO
For more information about the report package, see the following:
M5, Report
For more information about the CENTUM data access library, see the following:
CENTUM Data Access Library (IM 33S02T10-01E)
<G7. Product-Related Windows> G7-1
IM 33S01B30-01E
G7. Product-Related Windows
The operation and monitoring of the recipe management are carried out via the
Graphic windows and message windows as well as specific product-related win-
dows. Product-related windows are the windows mainly for the operation and moni-
toring of control recipes. This chapter explains product-related windows.
G7-2 <G7.1 Architecture of Product-Related Windows>
IM 33S01B30-01E
G7.1 Architecture of Product-Related Windows
Architecture of product-related windows is explained as follows.
Architecture of Product-Related Windows
There are two types of product-related windows: the Product Overview windows and the
Product Control windows.
Dialog boxes that can be called up from the product-related windows include the server
switching dialog box, the recipe list dialog box, the recipe setup dialog box, the recipe
header dialog box, recipe procedure window, recipe unit procedure window, the formula
dialog box, the equipment requirement dialog box, and the operator memorandum dialog
box.
The figure below shows the relationship between the product-related windows and the
dialog boxes called up from them:
Windows can be Opened from Product Overview Window
Among the product related windows, the windows that can be opened from product over-
view window are illustrated as follows.
G070101E.EPS
Formula
dialog box
Operator
Memo
dialog box
Recipe
List
dialog box
Recipe
Setup
dialog box
Control
Recipe Copy
dialog box
Formula
Export
dialog box
Trend Window
Selection
dialog box
Recipe
Header
dialog box
Recipe
Procedure
window
Unit Recipe
Procedure
window
Equipment
Requirement
dialog box
Unit Formula
dialog box
Operation
Formula
dialog box
Unit-SFC
window
Operation-
SFC
window
Train
Selection
dialog box
SEBOL
window
Server
Switch
dialog box
Product
Overview
Window
Product
Control
Window
Figure Windows can be Opened from Product Overview Window
<G7.1 Architecture of Product-Related Windows> G7-3
IM 33S01B30-01E
Windows can be Opened from Product Control Window
Among the product related windows, the windows that can be opened from product control
window are illustrated as follows.
Formula
Equipment
Requirement
Operator
Memo
Recipe
Header
Unit Recipe
Procedure
Unit Formula
Operation
Formula
Unit-SFC
Operation-
SFC
G070106E.EPS
SEBOL
Product
Control
Window
Product
Overview
Window
Figure Windows can be Opened from Product Control Window
IM 33S01B30-01E
Displays in Navigator Window
The product-related windows are positioned at the same level in the hierarchy as the user-
defined windows and the system windows. The Product Control windows labelled with
batch ID may be found under the directory of the product overview window. When a recipe
applied with train is defined, under the product overview window, a product overview
window with train name can be found.
Control recipes with status of RESERVED, READY, ACTIVE, and ABORTED are displayed
as product control windows in the navigator window, while those with recipe status of
COMPLETED are not displayed. The figure below is an example of displays in Navigator
window.
G070102E.EPS
Navigator \PRODUCT\.RO 1\.RO 1.TRAIN1
Product Overview
USER
SYSTEM
Name Comments Type
.RM 1 . 001-0010.TRAIN1 Product Control Product Control
Def
.RO 1
.RO 1.TRAIN1
.RM 1.001-0010.TR
.RO 1.TRAIN2
.RM 1.001-0020.TR
.RO 2
.RM 2.002-0020
.RM 2.002-0025
PRODUCT
Figure Navigator Window
IM 33S01B30-01E
Product-Related Window Icons Displayed in Navigator Window
The icons for product-related windows displayed in Navigator window are as follows.
G070103E.EPS
Product Overview window
Product Control window
Figure Product-Related Window Icons Displayed in Navigator Window
The Product Control windows icons are displayed with a batch ID attached in the Navigator
window after recipe reservation.
Color of Icons
The colors of the product control windows icons depend on the recipe status as follows:
RESERVED: White
READY: White
ACTIVE: Cyan
ABORTED: Magenta
The Product Overview windows icons are always displayed in white.
IM 33S01B30-01E
Windows may be Extended from Product-Related Windows
The Graphic windows and message windows may be extended from product-related
windows. For message windows, batch ID may be used as thread.
To call up the Graphic windows from the Product Control windows, and to call up the
Product Overview windows and the Product Control windows from the Graphic windows,
objects must be created.
The following illustration shows how to extend windows from the product-related windows.
G070104E.EPS
Product Control
window
Graphic window
Operation Guide
Message window
Historical Message
Report window
Process Alarm
window
Product Overview
window
(Batch Journal)
Using a selected batch
ID as filtering
condition
Using a selected
batch ID as thread
to call up
Using a selected
batch ID as thread
to call up
Specifying a batch ID
for call up
Using a selected object
to call up
Using the call button
to call up
Figure Windows may be Extended from Product-Related Windows
IM 33S01B30-01E
Windows Extension when Setting up Recipe
The windows are extended as follows when setup recipe.
G070105E.EPS
Product Overview
Window
Recipe List dialog box
Recipe Setup
dialog box
Select master recipe
Define a batch ID
Define a formula
Define the equipment requirement
Figure Windows Extension when Setting up Recipe
G7-8 <G7.2 Product Overview Window>
IM 33S01B30-01E
G7.2 Product Overview Window
Product Overview window may display the control recipe list.
What is Product Overview Window
Product Overview window may display the control recipes categorized in the recipe groups
(or trains). The operation commands for each control recipe may be performed via the
Product Overview window. Up to eight data items of the system fixed common block may
be displayed on the Product Overview window. The items to be displayed in the Product
Overview window may be specified on the Process Management Configuration Builder for
each recipe group.
An example of Product Overview window display is shown as follows.
G070201E.EPS
4/4
3 RECIPE01 COMPLETE 01-0009 00/06/23 15:18 00/06/23 18:18
4 RECIPE01 COMPLETE 01-0008 00/06/23 09:26 00/06/23 12:31
READY
Up to eight data
items of common
block can be
displayed.
Figure Product Overview Window
<G7.2 Product Overview Window> G7-9
IM 33S01B30-01E
Calling up Product Overview Windows
A Product Overview window may be called up by following methods.
Calling up from Name Input Dialog Box
The Product Overview window may be called up from the name input dialog box by enter-
ing the following script.
.RORecipeGroupNumber {.Train Name} {Display Size} {=Display Position}
{ }: Omissible
: Space
SEE ALSO
For details on display size and display position, see the following:
Calling up Windows by Entering Names in E2.5.1, Directly Calling up Operation and Monitoring
Windows
Calling up from Other Windows
The Product Overview window may be called up from the Product Control windows and the
Graphic windows.
IM 33S01B30-01E
G7.2.1 Elements of Product Overview Window
A Product Overview window consists of toolbar and items.
Toolbar of Product Overview Window
From the toolbar on the Product Overview window, recipe setup, data display of control
recipe and recipe operation may be performed.
G070202E.EPS
Figure Product Overview Window Toolbar
Buttons on the Product Overview window toolbar have the following functions.
G070203E.EPS
Outputting the window image of the currently displayed Product Overview window.
G070204E.EPS
Displaying the recipe header dialog box of the selected recipe.
G070205E.EPS
Displaying the recipe procedure window for the selected recipe. If the selected recipe is not
defined with a recipe procedure, the first recipe procedure window will be displayed.
G070206E.EPS
Displaying the formula dialog box of the selected recipe.
G070207E.EPS
Displaying the equipment requirements dialog box of the selected recipe.
G070208E.EPS
Displaying the operator memorandum dialog box of the selected recipe.
G070209E.EPS
Displaying the recipe list for recipe setup.
G070210E.EPS
Downloading the selected recipe to FCS.
IM 33S01B30-01E
G070211E.EPS
Starting the selected recipe.
G070212E.EPS
Printout the actual results of the selected recipe if the batch report function is defined.
G070213E.EPS
Delete the selected control recipe from both FCS and HIS. Both the control recipe and the
related unit recipes are deleted. However, if the control recipe is running (ACTIVE), this
button can not be operated.
G070214E.EPS
Start data acquisition of actual results.
G070215E.EPS
Equalizing the control recipe between master server and backup server. Normally, the
equalization is carried out automatically.
G070252E.EPS
Displaying the dialog box for copying control recipe.
G070253E.EPS
Displaying the dialog box for exporting formulae.
G070254E.EPS
Opening the dialog box for choosing a trend window to display the batch related trend.
G070216E.EPS
Displaying the train selection dialog box.
G070217E.EPS
Displaying the server switching dialog box.
IM 33S01B30-01E
Display Items on Product Overview Window
Product Overview Window Display Data
Up to eight data items of the system fixed common block (SYSRCM) may be displayed on
Product Overview window. The items to be displayed may be specified on the Process
Management Configuration Builder for each recipe group.
The following items are displayed as default.
Recipe name
Recipe status
Batch ID
Color Corresponds to Recipe Status
The color of recipe status characters varies with recipe status changes. The colors are
shown as follows.
RESERVED: White
READY: White
ACTIVE: Cyan
LOG : Cyan
COMPLETE: Green
ABORTED: Magenta
Abnormal Status Display
When a recipe is in abnormal status, the recipe name is marked by * . The color of *
represents specific status.
Yellow
The control recipe is not yet copied to the backup server successfully. After recipe
setup, during the course of copying the control recipe to the backup server, the yellow
* mark may temporarily display until the copy complete.
Normally, the control recipe is copied automatically, but it can also be copied manually
through the equalization operation in the product overview window.
Red
The control recipe does not exist in the master server.
Magenta
The control recipe does not exist in FCS.
IM 33S01B30-01E
Sorting Display Items
Click either of the sort buttons in the Product Overview window to select the order in which
the lines are displayed. The lines are sorted according to the button clicked.
4/4
3 RECIPE01 COMPLETE 01-0009 00/06/23 15:18 00/06/23 18:18
4 RECIPE01 COMPLETE 01-0008 00/06/23 09:26 00/06/23 12:31
Ready
G070218E.EPS
Sort buttons
Figure Sort Buttons in the Product Overview Window
When a sort button is clicked, the lines will be sorted according to the following rules;
If the same character string is found on several lines, those lines will be sorted accord-
ing to No.
If a cursor is displayed on a line, it will remain displayed on the same line after sorting
as well.
If a recipe is reserved, the sorting will be performed once again after the completion of
reservation.
If a recipe is deleted, the sorting will be performed once again after the completion of
deletion.
If STATUS is selected, the list will be sorted in the order of state transition matrix.
If the recipe status changes after sorting by STATUS, the sorting will be performed
once again at the time of change.
If a user-defined data item is changed, the sorting will not be performed anew.
IM 33S01B30-01E
Customize Tool Buttons of Product Overview Window
Vary with window size, tool-button size and CRT resolution, the tool-buttons on the product
overview window may be displayed differently. By customizing the tool buttons of the
product overview window, only the required buttons can be displayed on HIS.
TIP
If a button is not displayed on the window, consequently the corresponding task of the button cannot
be activated from the window either. For an example, if the [formula dialog box] call button is not
displayed on the window, the formula dialog box cannot be called from the window.
The layout of tool buttons as well as the separator of the buttons is not changed by show or hide of
the buttons.
Customize Too Buttons
The procedure for customizing the tool buttons of product overview window is as follows.
1. On Process Management tab of HIS Setup window, click [Product overview Settings]
button, Product Overview Settings window displays.
Cancel OK
G070255E.EPS
Customize Tool Buttons
Recipe Header Dialog Box
Procedure Window
Formula Dialog Box
Equipment Requirement Dialog Box
Operator Memo Dialog Box
Recipe List Dialog Box
Download Recipe
Start Recipe
Print Batch Report of the Recipe
Delete Recipe
Gather Recipe Result Data
Equalize Recipe
Trend Selection Dialog Box
Train Selection Dialog Box
Server Switch Dialog Box
Product Overview Settings
Figure Product Overview Settings Dialog Box
SEE ALSO
For more information about HIS Setup window, see the following:
E7.3, HIS Setup Window
2. In the product overview Settings dialog box, with the check marks of the buttons, show
or hide the tool buttons can be defined. If the button is checked, it is shown in the
product overview window, otherwise, not shown. By default, all the check marks are
checked thus all the tool buttons are shown in the window.
IM 33S01B30-01E
G7.2.2 Dialog Boxes Extended from Product Overview Window
The dialog boxes may be extended from Product Overview window are explained in
this chapter.
Recipe Header Dialog Box
An example of recipe header dialog box display is as follows.
G070219E.EPS
Recipe RECIPE01
Comment test1
Description This is a recipe for Product-A
This recipe has two parts for two units
The recipe for unit 2 is started by the recipe for unit 1.
The reaction process requires manual charge of the additive,
prepare the additive before the process starts.
Product Name Product-A
Version No. 1
Version Date 09/10/98 7:48:31 PM
Creator Name CENTUM
Create Date 09/11/98 9:10:15 AM
Approval Name YOKOGAWA
Master Recipe Status Approved
Engineering units kg
Normal Size 1000.0
Maximum Size 1200.0
Minimum Size 800.0
Security Level 1
Load Mode MAN
Start Mode MAN
Figure Recipe Header Dialog Box
Display Items on Recipe Header Dialog Box
The items defined on the Recipe Builder are displayed on the recipe header dialog box.
IM 33S01B30-01E
Procedure Window
Procedure window contains a recipe procedure window and a recipe unit procedure win-
dow. If the recipe procedure is already defined, the recipe procedure window can be
opened from product overview window. If the recipe procedure is not yet defined or if there
is only one unit recipe, the recipe procedure window of the first recipe procedure will be
displayed.
The recipe unit procedure running status may be displayed in the procedure window. The
dynamic running status of the unit recipe is reflected by the color change of SFC actions.
Recipe Procedure Window
Clicking an action item in recipe procedure window, the recipe unit procedure window will
be displayed. The recipe procedure window does not close when the displayed procedure
ends its execution.
G070220E.EPS
.RP 1.01-0009.0 Recipe Procedure 01-0009 Recipe Group 1 TRAIN1
Ready
UNIT A1
RECIPE : RECIPE01 STATUS : RESERVED
BATCH ID : 01-0009
1
UNIT B1 2
UNIT C3 3
UNIT D2 4
Figure Recipe Procedure Window
IM 33S01B30-01E
Recipe Unit Procedure Window
Clicking an action item in recipe unit procedure window will not open an operation window.
Moreover, when the displayed unit recipe execution is completed, the recipe procedure
window does not close by itself.
G070221E.EPS
.RP 1.01-0009.1 Recipe Procedure 01-0009 Recipe Group 1 TRAIN1
Ready
Initialize
RECIPE : RECIPE01 No.1 STATUS : ASSIGNED
BATCH ID : 01-0009 PART No. : 1
OPERATION : OP001 OPID : 2
1
Charge 2
Heat-up 3
Discharge 4
Cleaning 5
End 6
Figure Recipe Unit Procedure Window
IM 33S01B30-01E
Displaying Unit Formula Together with Procedure
The unit formula dialog can be displayed together with procedure when the procedure
dialog is displayed. The cursor is positioned at the SFC step to indicate its correspondence
with the formula dialog.
Displaying unit formula together with procedure can be specified on Process Management
tab in HIS Setup window, by check the option [Display with Procedure together].
After checking the option [Display with Procedure together], the procedure dialog and the
formula dialog behave as follows.
When displaying unit procedure dialog, the unit formula dialog is displayed together.
When displaying unit recipe procedure dialog, the operation formula dialog is dis-
played together.
SEE ALSO
For more information about Process Management tab on HIS Setup window, see the following:
E7.3.17, Process Management Tab
G070251E.EPS
Unit Common Block1
Unit Common Block2
Unit Common Block3
Unit Common Block4
PICSV Pressure [ 1]
TICSV Temperature [ 1]
01-0001 COMB01 Unit Common Block1
01-0001 Unitrecipe1 Recipe Group 1
.RP 1.01-0009.0 Recipe Procedure 01-0009 Recipe Group 1 T
Ready
UNIT A1
RECIPE : RECIPE01 STATUS
BATCH ID : 01-0009
1
UNIT B1 2
UNIT C3 3
UNIT D2 4
Figure Displaying Unit Formula Together with Procedure
IM 33S01B30-01E
Toolbar
Operating the buttons on the toolbar of the procedure window, the size of displayed proce-
dure may be enlarged or reduced.
G070222E.EPS
Figure Toolbar Displayed on Procedure Window
The buttons on the toolbar have the following functions.
G070223E.EPS
Since only five lines of procedure may be displayed, this button is provided to scroll the
display for the next five lines of the running step. If the running step has less than five lines,
the display starts from the first line of the procedure instead of the first line of the step.
However, this button does not scroll the display horizontally. If the step being displayed is
beyond the display horizontally, user may manually move the scroll bar of the window after
click this button.
TIP
The procedure display does not automatically scroll to follow the advances of the steps.
G070224E.EPS
This button returns the procedure display to standard size when the procedure display is in
reduced size.
G070225E.EPS
This button reduces the procedure display to 2/3 of standard size when the procedure
display is in standard size.
G070247E.EPS
Clicking this button, Unit-SFC window displays.
Clicking this button after choosing a step on recipe procedure window, the SFC (unit
procedure) window for the selected step displays.
If no step is being selected (cursor is not pointing at any step) while this button is
clicked, the first step in the Unit SFC window displays. To deselect a step, push [ESC]
key.
Clicking this button after choosing a step on unit recipe procedure window, the SFC/
SEBOL (operation) window for the selected step displays. Double clicking the step
can also open the SFC/SEBOL (operation) window of the step without clicking this
button.
If no step is being selected (cursor is not pointing at any step) while this button is
clicked, the Unit SFC window corresponds to the unit recipe procedure displays. To
deselect a step, push [ESC] key.
IM 33S01B30-01E
G070243E.EPS
Clicking this button on toolbar, the Formula dialog box displays.
If this button is clicked when no unit recipe displayed in recipe procedure window is
selected, a dialog box of the formula for the whole recipe will be displayed.
If this button is clicked when a unit recipe displayed in recipe procedure window is
selected, a formula dialog box of the selected unit will be displayed.
If this button is clicked when no operation recipe displayed in unit recipe procedure
window is selected, a dialog box of the formula for the whole unit will be displayed.
If this button is clicked when an operation recipe displayed in unit recipe procedure
window is selected, a formula dialog box of the selected operation will be displayed.
G070248E.EPS
When this button is pressed (Active Step Display Mode), at the moment of control step
changes, the unit formula dialog or the operation formula dialog corresponds to the step
automatically displays.
Moreover, the SFC window for displaying action steps is automatically scrolled for indicat-
ing the step changes of the running procedure.
When opening the procedure window, the state of this tool button is as follows.
When the option Displaying Unit Formula Together with Procedure is checked;
Active Display Mode On: This button is pressed.
When the option Displaying Unit Formula Together with Procedure is not checked;
Active Display Mode Off: This button is not pressed.
SEE ALSO
For more information about displaying unit formula together with procedure, see the following in the
previous paragraph:
Displaying Unit Formula Together with Procedure
SFC Action Item
SFC action item displays as follows according to the SFC status.
Before execution
The initial step of step1 displays and flashes in white.
During execution
The running steps are displayed in cyan.
Execution complete
The display of the completed steps and the checked transitions change to green.
Not Executed
The display of the steps not executed and the transitions not checked are in white.
IM 33S01B30-01E
Formula Dialog Box
The formula (common block data) may be displayed and defined in this dialog box. The
data are displayed according to the common block names. The operation and monitoring
authority to the data items defined on the Common Block Builder will be checked according
to the security level. When the common block data have high and low range limits that have
been defined in the Common Block Builder, that data are subject to range check when
entered. The figure below shows an example of the formula dialog box:
G070226E.EPS
01-0009 SYSRCM SYSTEM COMMON
RECIPEGR GROUP : 1
RECIPE RECIPE : RECIPE01
BATCHID BATCH ID : 01-0009
STATUS STATUS = RESERVED
MAXPART No. OF PART : 1
RSVTIME RESERVED TIME : 24/07/98 11:31 AM
TRAIN TRAIN :
PATH PATH :
PLANT PLANT :
LOADMODE LOAD MODE : MAN
STARTMODE START MODE : MAN
USER1 USER CODE1 = LOT. 301
USER2 USER CODE2 =
USER3 USER CODE3 =
SYSTEM COMMON
#01 UNIT RECIPE
SCALE
REACT1
REACR2
STOCK
DUMMY
Figure Formula Dialog Box
Display Items
The data items defined on the Common Block Builder may be displayed in the common
block dialog box. The following display items are displayed in the common block dialog
box.
Common block name
Common block comment
Data item name
Data item comment
Data value
Engineering unit symbol
IM 33S01B30-01E
Array Data Display
A dialog box for displaying details of arrayed data can be extended from the array data in
the formula dialog box. The details of the arrayed data are display in the dialog box as
follows.
[X] X elements (one-dimensional array)
[X,Y] X and Y elements (two-dimensional array)
The details of the arrayed data displayed in the dialog box extended from formula dialog
box are as follows.
20.0
30.0
40.0
45.0
40.0
G070246E.EPS
comment [ 5, 7] unit
1 2 3 4 5
1
2
3
4
5
6
7
8
9
10
Figure Array Data Dialog Box (One-Dimensional Array)
G070227E.EPS
comment [ 5, 7] unit
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0
[1, *] [2, *] [3, *] [4, *] [5, *]
[*, 1]
[*, 2]
[*, 3]
[*, 4]
[*, 5]
[*, 6]
[*, 7]
Figure Array Data Dialog Box (Two-Dimensional Array)
IM 33S01B30-01E
Unit Formula Dialog Box
Unit formula dialog box is used for setting and displaying the formulae of a designated unit.
A Unit Formula Dialog Box is shown as follows.
G070244E.EPS
Unit Common Block1
Unit Common Block2
Unit Common Block3
Unit Common Block4
PICSV Pressure [ 1] = 120.0
TICSV Temperature [ 1] = 150.0
01-0001 COMB01 Unit Common Block1
Figure Unit Formula Dialog Box
Operation Formula Dialog Box
Operation formula dialog box is used for setting and displaying the formula of a designated
operation. An Operation Formula Dialog Box is shown as follows.
G070245E.EPS
Operation Common Block1
SETV1 Setting Value [ 1, 1] = 45.0
ACTV1 Result [ 1, 1] = 0.0
01-0001 COMB11 Operation Common Block
Figure Operation Formula Dialog Box
IM 33S01B30-01E
Unit-SFC Window
The SFC in a unit instrument is displayed in Unit-SFC window. Clicking the Unit-SFC tool
button on recipe procedure window after selecting a recipe procedure SFC step, the details
of the selected step can be displayed in the Unit-SFC window.
G070249E.EPS
RA001 SFC A1 Polymer tank A1
Ready
RA001 A1 Polymer tank A1
MODE=AUT ALRM:NR BSTS=RUN
DIALOGUE:
Prepare reaction 2
Dischaege 3
#1 Raw material charge 4
Mix addition B 9 Mix addition C 10
Heating 5
Agitation 1 6
Cooling 7
Mix addition A 8
Agitation 2 12
Figure Unit-SFC Window
IM 33S01B30-01E
Operation-SFC Window
The SFC in an operation is displayed in Operation-SFC window. Clicking the Unit-SFC tool
button on recipe procedure window after selecting a recipe procedure SFC step, the details
of the selected step operation can be displayed. Clicking a step of the displayed operation,
a SEBOL window for the details of the selected step displays.
OP0104 SFC #1 Raw material charge
Ready
OP0104 #1 Raw material charge 2
DIALOGUE: PHASE:#1 Raw material charge
2
Changing additive 3
#1 Raw material charge
4
Heating 5
Agitation 1
6
Cooling 7
Agitation 2
G070250E.EPS
OP0104 SFC #1 Raw material charge
OP0104 #1 Raw material charge 2
DIALOGUE: PHASE:#1 Raw material charge
27 * Message from Instruments
28 *-----------------------------------------------------------------------------------------------------------*
29 if (%.PGSTEP 20) then
30
31 wait until (%SW0413.PV==1) !change end FL
32 %SW0413.PV=0
33
34 %.PGSTEP=20
35
36 end if
37
38
39 *-----------------------------------------------------------------------------------------------------------*
40 * Write data to Instruments
41 *-----------------------------------------------------------------------------------------------------------*
More (41/46)
Ready
SEBOL Window
Operation-SFC WINDOW
Figure Operation-SFC Window
IM 33S01B30-01E
Equipment Requirements Dialog Box
The equipment requirements dialog box displays the unit name and the unit recipe status
assigned to a control recipe. An example of equipment requirements dialog box display is
shown as follows.
G070228E.EPS
1 UT0101 ASSIGNED
No. UNITNAME STATUS START TIME END TIME
Figure Equipment Requirements Dialog Box
IM 33S01B30-01E
Toolbar
Operating the buttons on the toolbar of the equipment requirements dialog box, the opera-
tions such as dynamic unit assignment, unit recipe download and start may be performed.
G070229E.EPS
Figure Toolbar Displayed on Equipment Requirements Dialog Box
The buttons on the toolbar on equipment requirements dialog box have the following
functions.
G070230E.EPS
Assigning the selected unit recipe with a unit by dynamic assignment.
G070231E.EPS
Downloading the selected unit recipe to FCS.
G070232E.EPS
Starting the selected unit recipe.
G070233E.EPS
Printout the actual results of the selected unit recipe if the batch report function is defined.
G070234E.EPS
Displaying the procedure window of the selected unit recipe.
Display Items
The following items on the equipment requirements dialog box are displayed as default.
Unit recipe name
Unit recipe status
Unit recipe start time
Unit recipe end time
Color Corresponds to Unit Recipe Status
The color of unit recipe status characters varies with recipe status changes. The colors are
shown as follows.
NOASSIGN: White
RESERVED: White
READY: White
ACTIVE: Cyan
LOG : Cyan
COMPLETE: Green
ABORTED: Magenta
IM 33S01B30-01E
Operator Memorandum Dialog Box
The operator may put memorandum for a running batch and the memorandum may be put
in the operator memorandum dialog box. Up to 128 alphanumeric characters or 64 double-
byte characters are allowed for the operator memorandum. The input memorandum text
will be displayed in the historical message report window as the batch journals. An example
of operator memorandum dialog box display is shown as follows.
G070235E.EPS
Clear OK
Recipe setup completed successfully
Figure Operator Memorandum Dialog Box
IM 33S01B30-01E
Recipe List Dialog Box
The master recipe may be selected on this dialog box for recipe setup. This dialog box may
be displayed from the product overview window by clicking the recipe list button.
The master recipes created on Recipe View are listed on the recipe list dialog box. Select
one of the master recipes for recipe setup, then the recipe setup dialog box will be dis-
played.
An example of recipe list dialog box display is shown as follows.
G070236E.EPS
1 RECIPE01 Recipe for producing 20t of product-ABC
2 RECIPE02 Recipe for producing 5t of product-EFG
3
4
5
6
7
8
9
10
11
12
13
14
15
16
No. Recipe name
Recipe Group 1
Figure Recipe List Dialog Box
IM 33S01B30-01E
Recipe Setup Dialog Box
A batch ID can be set for a recipe in the recipe setup dialog box as follows.
Selecting a master recipe in the recipe list dialog box will display the recipe setup dialog
box. Set a batch ID for a recipe in the recipe setup dialog box. With a batch ID set to be
added automatically, a batch ID displayed in the recipe setup dialog box when the dialog
box is displayed becomes valid. A batch ID can be set to be added automatically in the
Process Management Configuration Builder for each recipe group.
When Train-Path is specified for Equipment Requirements in Recipe Builder, the train and
the path can be designated in this dialog box.
Reset
Equipment...
Formula...
Reserve
G070237E.EPS
BATCH ID 01-0020
Train
Path
Figure Recipe Setup Dialog Box
Changing Formula
When changing the currently used formula, clicking the [Formula...] button may pop up the
formula dialog box. The values of the formula may be changed on the formula dialog box.
G070238E.EPS
CHARGE SC1SV = 100.0
CHARGE SC101SV = 50.0
CHARGE SCMANIN1 = 10
CHARGE SCMANIN2 = 12
REACT1 R11SV = 100.0
REACT1 R1201SV = 20.0
REACT2 R21SV = 30.0
REACT2 R22SV = 20.0
REACT2 R2ALSV = 30.0
REACT2 R2PHSV = 50.0
STOCK STRCV STRCV Level = 50.0
DUMMY DATA1 = 100.0
DUMMY ARRAY ARRAY DATA [001, 001] : 20.0
SYSRCM USER1 USER CODE1 = LOT. 1001
Figure Formula Dialog Box
TIP
The recipe formula selected on the recipe list dialog box will be displayed on the recipe setup dialog box
called up from the formula dialog box.
IM 33S01B30-01E
Specifying Unit Name
When setting a unit recipe to a unit, clicking the [Equipment...] button may pop up the
equipment requirements dialog box. In this dialog box, the unit recipe number can be
selected. After selecting the unit recipe number, a dialog box for unit selection appears. The
name of the unit to apply the selected unit recipe may be specified in the unit selection
dialog box.
When defining multiple equipment requirements on the Recipe Builder, the name list of the
units defined in unit selection dialog box is displayed. The names of the units can be se-
lected from the list for applying the selected recipe.
However, with only one unit set for equipment requirements on the Recipe Builder specify-
ing names of units in the recipe setup dialog box is not required. The following figures show
the equipment requirements dialog box and unit selection dialog box.
G070239E.EPS
1 UT0101
2 -
3
TRAIN
PATH
Figure Equipment Requirements Dialog Box
G070240E.EPS
SYSPCM01. UNITNAME
UT0101
UT0102
Cancel OK
Figure Unit Selection Dialog Box
IM 33S01B30-01E
This dialog box contains the settings for copying control recipe. In this dialog box, the Batch
ID of the copied recipe can be changed and the option of copying the result data from the
master recipe can be set.
G070256E.EPS
Reset
ORIGIN BATCH ID 01-0009
01-0012
RECIPE01
BATCH ID
RECIPE
Copy Result Data
Copy
Figure Control Recipe Copy Dialog Box
This dialog box contains the settings for exporting formula. In this dialog box, the exported
file type and the option of exporting the result data can be set.
G070257E.EPS
BATCH ID 01-0009 Master Server HIS0124
\\BATCH1\CTMRECP\Formula
01-0009.CSV
Save in
File name
Export Result Data
Export File Type
For General Purpose For Recipe Builder
Reset
Export
Figure Formula Export Dialog Box
Trend Window Selection Dialog Box
This dialog box contains the settings for displaying the batch related trend window. In this
dialog box, the trend displayed in the window can be selected.
G070258E.EPS
Relation Unit
UT1001
Unit Recipe No.
Unit Name
No. Trend Window Comment
1 TG0101 Block:01 Group:01
2
3
4
Figure Trend Window Selection Dialog Box
IM 33S01B30-01E
Train Selection Dialog Box
The train selection dialog box is used for selecting a train in a recipe group. The control
recipe of the selected train may be displayed on Product Overview window.
When choosing [NO TRAIN], all control recipes in the group will be displayed on the Prod-
uct Overview window.
G070241E.EPS
SYSRCM.TRAIN
Train1
Train2
( NO TRAIN )
Cancel OK
Figure Train Selection Dialog Box
IM 33S01B30-01E
Server Switching Dialog Box
On the server switch dialog box, the status of severs corresponds to each recipe group is
displayed, and master server switching may be performed on this dialog box. The server
switching window may be called up from the Product Overview window by clicking the
server switching button. An example of server switching dialog box display is shown as
follows.
G070242E.EPS
Number Server 1 Server 2 Recipe group comment
1 HIS0124 HIS0123 Recipe Group 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
HIS01024
Figure Server Switching Dialog Box
Display Items
The following items are displayed on the server switching dialog box.
Recipe group number
Server 1 status
Server 1 station name
Server 2 status
Server 2 station name
Server Status Indicator
Server status indicators color varies according to the server status.
: Master server
: Backup server
No display: Not working as server
Restrictions on Recipe Setup
Right after server switch is performed, the display of the server status starts to flash. At this
moment, the master server is gathering the list of control recipes. Thus, the recipe setup
can not be performed while the server status display is flashing.
<G7.3 Product Control Window> G7-35
IM 33S01B30-01E
G7.3 Product Control Window
The status of control recipes may be displayed in the Product Control window.
What is Product Control Window
Product control window may display the batch ID of a specified recipe header, as well as
the formula, procedure and equipment requirements. An example of Product Control
window display is shown as follows.
G070301E.EPS
.RM 1.01-0013 Product Control
Recipe Group 1
This is a recipe for Product -A.
Recipe : RECIPE01 TRAIN :
Batch ID : 01-0013 STATUS : RESERVED
START TIME : START PLAN :
END TIME : END PLAN :
PATH : User Code 1 = LOT. 1001
User Code 2 =
User Code 3 =
User Code 4 =
ALARM JOURNAL
OVERVIEW
OPEGUIDE
Ready
Test Recipe
01-0013
No. Unit Name Status
1 UT0101 ASSIGNED
2 UT0201 ASSIGNED
Figure Product Control Window Display
G7-36 <G7.3 Product Control Window>
IM 33S01B30-01E
Calling up Product Control Windows
A product control window may be called up by following methods.
Calling up from Name Input Dialog Box
The product control window may be called up from the name input dialog box by entering
the following script.
.RMRecipeGroupNumber.BatchID {.Train} {Display Size} {=Display Position}
{ }: Omissible
: Space
SEE ALSO
For details on display size and display position, see the following:
Calling up Windows by Entering Names in E2.5.1, Directly Calling up Operation and Monitoring
Windows
Calling up from Other Windows
The Product Control window can be called up from the Product Overview window and the
Graphic window.
IM 33S01B30-01E
G7.3.1 Elements of Product Control Window
A Product Control window consists of toolbar and items.
Toolbar of Product Control Window
From the toolbar on the Product Control window, the operations such as displaying the may
be performed.
G070302E.EPS
Figure An Example of Product Overview Window Toolbar Display
Buttons on the product control window toolbar have the following functions.
G070303E.EPS
Outputting the window image of the currently displayed Product Control window.
G070304E.EPS
Displaying the recipe header dialog box.
G070305E.EPS
Displaying the recipe procedure window.
G070306E.EPS
Displaying the formula dialog box.
G070307E.EPS
Displaying the equipment requirements dialog box.
G070308E.EPS
Displaying the operator memorandum dialog box.
G7-38 <G7.3 Product Control Window>
IM 33S01B30-01E
G070309E.EPS
Performing the dynamic unit assignment.
G070310E.EPS
Downloading the unit recipe to FCS.
G070311E.EPS
Starting the unit recipe.
G070312E.EPS
Printout the actual results if the batch report function is defined.
Display Items on Product Control Window
Recipe Group Comment, Description, Recipe Comment, Equipment Requirement
The elements to be displayed in Product Control window may be specified on the Product
Control Builder for each recipe group.
The same graphical object used for the Graphic windows may be used for Product Control
window generation.
The objects that may be created only on the product control window are shown as follows.
A recipe comment defined in the Process Management Configuration Builder is
displayed.
Recipe comment
A recipe comment defined in a recipe header for the Recipe Builder is displayed.
Recipe description
A recipe description defined in a recipe header for the Recipe Builder is displayed.
Equipment requirement
Assigned unit name and unit recipe status are displayed.
Color Corresponds to Unit Recipe Status
The color of unit recipe status characters varies with unit recipe status changes. The colors
are shown as follows.
RESERVED: White
READY: White
ACTIVE: Cyan
LOG : Cyan
COMPLETE: Green
ABORTED: Magenta
IM 33S01B30-01E
Dialog Boxes Extended from Product Control Window
The dialog boxes may be extended from product control window are shown as follows.
Recipe header dialog box
Recipe unit procedure window
Formula dialog box
Equipment requirements dialog box
Operator memorandum dialog box
SEE ALSO
For more information on the dialog boxes may be extended from the product control window, see the
following:
G7.2.2, Dialog Boxes Extended from Product Overview Window
Blank Page
<G8. Engineering when Connecting Multiple Projects> G8-1
IM 33S01B30-01E
G8. Engineering when Connecting Multiple
Projects
It is possible to connect different multiple projects by designating the upper-level
project as the CS 3000 and the lower-level project as the CS 1000, CS 3000 or
CENTUM CS (hereinafter called CS). If Batch Management is present in each of the
connected projects, the recipe from the upper-level project to the lower-level project
can be monitored.
The following explains the batch management operation and the batch engineering
in each project when multiple projects are connected.
Forms of Project Connection
There are two connecting forms for multiple projects: unilateral connection and bilateral.
Unilateral connection is a method that can monitor the operation of the lower-level project
from the upper-level project. However, it cannot monitor the operation of the upper level
from the lower level. In the unilateral connection the CS 3000 will be the upper-level
project, and CS 1000, CS 3000 and CS will be the lower-level projects. The bilateral con-
nection is a method that can monitor the operation mutually between the connected
projects. The bilateral connection is only allowed between the upper-level project CS 3000
and lower-level project CS 3000.
SEE ALSO
For details on project connection, see the following:
M9, Multiple Project Connection
Recipe Group in Unilateral Connection
When multiple projects are connected in unilateral mode, the recipe group can stride over
both the upper- and lower-level projects. It is possible to specify the stations of both levels
as a server/client of each recipe group to be defined by the Process Management Configu-
ration Builder. However, the station of the upper-level project cannot be assigned as a
recipe server of Lower project. If the upper-level projects station is added as a client to a
recipe group in which the server/client of the lower-level project side has been defined, the
recipe group of the lower-level project can be monitored from the upper-level projects
station.
G080001E.EPS
HIS of upper-
level project
HIS of lower-
level project
Can be defined only as a recipe client
Can be defined as a recipe server/client
Recipe group
Figure Recipe Group Operation in Unilateral Connection
G8-2 <G8. Engineering when Connecting Multiple Projects>
IM 33S01B30-01E
Functions that can be Performed from the Upper-Level Project
There is no functional difference between the client function of the lower-level project and
the client function of the upper-level project. Any operation that can be performed by the
client function in a system with a single-project structure can also be performed by the
client function of the upper-level project.
Recipe Group in Bilateral Connection
The bilateral connection is a method that can monitor the operation mutually between
connected projects. Logically, then, there is no concept of upper-level project and lower-
level project. However, as in the case of the recipe group structure in unilateral connection,
a recipe server consists of only a station of the lower-level project. Therefore, the bilateral
connection, when viewed from Batch Management, is performed for each recipe group.
The projects connected in lateral mode are divided into two recipe groups: a recipe group in
which self projects are positioned as upper-level projects, and a recipe group in which self
projects are positioned as lower-level projects, for each recipe group. There will never be
bilateral connection within the same recipe group (i.e., stations of both the upper- and
lower-level projects becoming recipe servers).
G080002E.EPS
Can be defined only as a recipe client of recipe group 1
Can be defined as a recipe server/client of recipe group 2
Can be defined as a recipe server/client of recipe group 1
Can be defined only as a recipe client of recipe group 2
Recipe group 2 Recipe group 1
Upper
level
Upper
level
Lower
level
Lower
level
HIS
HIS
Figure Recipe Group Operation in Bilateral Connection
Functions that can be Performed from the Upper-Level Project
The bilateral connection viewed from Batch Management can be considered a collection of
unilateral connections in recipe group units. It can be treated in a manner similar to the
unilateral connection in each recipe-group unit. It can monitor the operations of lower-level
projects in the same manner as for the unilateral connection, from the client station of an
upper-level project viewed from a certain recipe group.
Definition of Process Management Configuration
The contents defined by the Process Management Configuration Builder cannot be down-
loaded to another project. The upper-level project and lower-level project individually define
the process management configuration. When connecting multiple projects, the recipe
group strides over both the upper- and lower-level projects. Therefore, define the same
process management configuration for the same recipe group number of both the upper-
and lower-level projects.
IM 33S01B30-01E
Definition of Master Recipe
A master recipe when multiple projects are connected is created by the Recipe Builder of
the lower-level project. It will not be created by the upper-level project. The master recipe
can be created only by the project of the side to which the recipe server of each recipe
group belongs. The master recipe file that is newly created will be downloaded to the recipe
server station and recipe backup station.
G080003E.EPS
Recipe builder of upper-level project
HIS
Recipe client
Upper-level project
Recipe Builder of lower-level project
HIS
or
ICS
Recipe client
Lower-level project
Recipe group 1
The master recipe of this recipe group
(recipe group 1 in this example) is not created
by the Recipe Builder of the upper-level project.
Leave recipe group 1 blank.
The master recipe is created by the Recipe
Builder of the lower-level project (project of
the side to which the recipe server belongs).
Figure Definition of Master Recipe
Download Destination of Recipe-Related Definition Files
The download destinations of the recipe-related definition files that are defined by the
Builder are as follows:
Files to be Downloaded to the Server Station
The following files are downloaded to the server station:
Process management configuration definition file
Train definition file
Product control definition file
Common block definition file
Master recipe definition file
Files to be Downloaded to the Client Station
The following files are downloaded to the client station:
Process management configuration definition file
Product control definition file
G8-4 <G8. Engineering when Connecting Multiple Projects>
IM 33S01B30-01E
Definition of Units (Equipment Requirements)
The units that can be used by a recipe group when multiple projects are connected can
only be units that are defined in the FCS of the project to which the recipe server station
belongs. Namely, they are the units defined in the FCS of the lower-level project.
G080004E.EPS
FCS of upper-level project
Irrelevant to this recipe group
(recipe group 1 in this example)
HIS Recipe client
Upper-level project
FCS of lower-level project
A unit defined in this FCS is used.
A download of the recipe is also performed
for this FCS.
Lower-level project
Recipe group 1
FCS
HIS
or
ICS
Recipe server
FCS
Figure Relationship between Recipe Group and Unit
IM 33S01B30-01E
Monitoring Batch Operation in Multiple Project Connection
The recipes of the upper- and lower-level projects are distinguished by recipe group num-
bers. Product-related windows are distinguished between the upper-level project and
lower-level project, depending on which side the server station corresponding to the recipe
group number is located. CS Batch and CS Batch 1000/CS Batch 3000 have different
displays and operations of the product-related windows.
Specifying the Equipment Requirements
When setting up a recipe and specifying a unit name from the product control window,
specify the unit name without adding the project ID specified by the Multiple Project
Connection Builder.
Historical Messages
All recipe group messages are stored in the client station of the upper-level project. The
recipe group number and batch ID are added before the messages are stored. When
retrieving messages, the recipes of the upper-level project and lower-level project can be
distinguished by specifying the batch ID.
Batch Report
Batch Report is started from the server station that manages control recipes. Therefore, it is
not necessary to define batch reports in the client station.
G8-6 <G8.1 Connecting CS 3000 and CS 1000>
IM 33S01B30-01E
G8.1 Connecting CS 3000 and CS 1000
When a CS 3000 and CS 1000 are connected, the upper-level project will be the CS
3000 and the lower-level project will be the CS 1000.
Overview of Connection between CS 3000 Project and CS 1000 Project
The recipes of the lower-level project can be operated by the upper-level project by con-
necting the projects. However, the recipes of the upper-level project cannot be operated by
the lower-level project.
To operate and monitor the recipe of the lower-level project from the upper-level project,
specify the HIS of the upper-level project as the client station of the lower-level project. The
HIS thus specified as the client station will operate and monitor recipes using the recipe
group number of the lower-level project.
Recipes can be downloaded from the server station in the lower-level project. Therefore,
only the station in the lower-level project can be specified as the server station. The follow-
ing figure shows an example of the project connection configuration.
Ethernet
HIS
FCS
G080101E.EPS
Client
station
V net
HIS
Ethernet
HIS
FCS
Server
station
Server
station
VL net
HIS
Client
station
BCV
Recipe group 2
(extending over projects)
Recipe group 1
Recipe group 1
Recipe group of
upper-level project
Recipe group of
lower-level project
CS 3000
CS 1000
Figure Example of Project Connection Configuration
TIP
Only the station in the self project can be specified as both the server station and client station.
<G8.1 Connecting CS 3000 and CS 1000> G8-7
IM 33S01B30-01E
G8.1.1 Engineering of the Upper-Level Project (CS 3000)
This section describes the engineering of the upper-level project (CS 3000) when a
CS 3000 and CS 1000 are connected.
G080102E.EPS
Start engineering of
the upper-level project (CS 3000).
For items enclosed by dashed lines, see M9,
Multiple Project Connection.
Items explained in this document
Confirm that the IP addresses and HIS
computer names are not duplicated in
any station in the projects to be connected.
Define the project to be monitored by each HIS.
Define the following items using the Multiple
Project Connection Builder.
Specify whether or not duplicate tag names
exist.
Define the list and details of projects to be
connected (to a maximum of 16 projects).
Resolve project-name duplication as necessary.
Define other project stations as necessary.
Define recipe groups using the Process
End engineering of
Download the projects common part for all
stations in the upper-level project.
Restart all stations in the upper-level project.
Specify the tag-list reference destination station.
Define other items.
Define product control windows.
Define common blocks.
Define trains.
Define master recipes.
Figure Engineering Procedure for Upper-Level Project (CS 3000)
IM 33S01B30-01E
Using the Process Management Configuration Builder on the upper-level project side,
define the recipe group used for connecting projects. Specify the same recipe group
number, which is used to connect projects, for the upper- and lower-level projects. The
following shows the contents of definition on the upper-level project side. The definitions of
other recipe groups and process management configuration follow the process manage-
ment configuration definition on the lower-level project side. The definition on the upper-
level project side will be ignored.
Recipe comment
Maximum number of master recipes
Maximum number of control recipes
Server station
Client station
Product-overview display data
G080103E.EPS
Ready
Recipe comment Recipe Group 1
Maximum number of master recipes 10
Maximum number of control recipes 10
Maximum number of COMPLETE recipes 2
COMPLETE recipe attribute COMPLETE recipe only
Batch ID %2G-%4N
Message
Process Management Configuration Builder - [Pjt:MYPJT File:BatchCnf.edf]
Recipe Group 1 Recipe Group 2 Recipe Group 3 Recipe Group 4 Process Management Definition
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
This definition
is ignored.
Figure Example of Definition Using the Process Management Configuration Builder
Recipe Comment
Any recipe group comment can be created on the upper-level project side.
Define the same value as the maximum number of master recipes on the lower-level
project side.
Define the same value as the maximum number of control recipes on the lower-level
project side.
IM 33S01B30-01E
Definition of Server Station
Define the server station according to the following:
Define the HIS station name of the lower-level project that will be assigned as a recipe
server. The HIS station name of the lower-level project is not displayed in the drop-
down menu. So, enter the HIS station name from the keyboard.
Make the recipe server configuration the same as the one defined by the process
management configuration of the lower-level project.
If a station alias is being used on the lower-level project side, enter the station alias as
the server name.
If other project station has been defined on the upper-level project side and a station
alias is being used, enter the station alias as the server name.
Server station
1 HIS0324
2 HIS0323
Process management configuration
of upper-level project
G080104E.EPS
Server station
1 HIS0324
2 HIS0323
of lower-level project
HIS0263 HIS0264
Client Client
HIS0321 HIS0322 HIS0323 HIS0324 STN0263 STN0264
UHMIS UHMIS Client Client Server #1 Server #2
BCV-A
FCS FCS FCS
FCS FCS FCS
Upper-level project (CS 3000)
Lower-level project (CS 1000)
V net
VL net
Figure Example of Definition when a Station Alias is not Used
IM 33S01B30-01E
Server station
1 BCH324
2 BCH323
G080105E.EPS
Server station
1 BCH324
2 BCH323
Define station aliases
HIS0263 HIS0264
Client Client
HIS0321 HIS0322
BCH323
(HIS0323)
BCH324
(HIS0324)
STN0263 STN0264
BCV-A
FCS FCS FCS
FCS FCS FCS
V net
VL net
Figure Example 1 of Definition when Station Aliases are Used
Server station
1 BCH324
2 BCH323
G080106E.EPS
Server station
1 HIS0324
2 HIS0323
HIS0263 HIS0264
Client Client
BCH323
(STN0323)
BCH324
(STN0324)
Other project stations
BCV-A
FCS FCS FCS
FCS FCS FCS
V net
VL net
Define other project stations,
then define station aliases for
these stations.
IM 33S01B30-01E
Definition of Client Station
Define the client station as follows:
Define the HIS station name of the lower-level project that will become a recipe client.
The HIS station name of the lower-level project is not displayed in the drop-down
menu, so enter the HIS station name using the keyboard.
If a station alias is being used on the lower-level project side, enter the station alias.
alias is being used, enter the station alias as the client name.
Define the HIS station name of the upper-level project that will become a recipe client.
The HIS station name can be selected from the drop-down menu. If a station alias is
being used, the station alias can be selected from the menu.
Make the recipe-client configuration the same as the one defined by the process
management configuration of the lower-level project. However, the station name to be
defined may be different.
G080107E.EPS
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
6
Client station
1 HIS0322
2 HIS0321
3 STN0264
4 STN0263
5
6
HIS0263 HIS0264
Client Client
BCV-A
FCS FCS FCS
FCS FCS FCS
V net
VL net
IM 33S01B30-01E
G080108E.EPS
Client station
1 BCH322
2 BCH321
3 BCH264
4 BCH263
5
6
Client station
1 BCH322
2 BCH321
3 STN0264
4 STN0263
5
6
BCH263
(HIS0263)
BCH264
(HIS0264)
Client Client
BCH321
(HIS0321)
BCH322
(HIS0322)
HIS0323 HIS0324 STN0263 STN0264
BCV-A
FCS FCS FCS
FCS FCS FCS
V net
VL net
G080109E.EPS
Client station
1 BCH322
2 BCH321
3 HIS0264
4 HIS0263
5
6
Client station
1 HIS0322
2 HIS0321
3 STN0264
4 STN0263
5
6
FCS FCS FCS
HIS0263 HIS0264
Client Client
BCH321
(STN0321)
BCH322
(STN0322)
BCV-A
FCS FCS FCS
V net
VL net
these stations.
Product Overview Display Data
Any display data can be created on the upper-level project side.
IM 33S01B30-01E
Other Definitions
The following explains the definitions established by the upper-level project, in addition to
the process management configuration definition.
Definition of Product Control Windows
The contents defined in product control windows are downloaded to the server station and
client station as specified by the Process Management Configuration Builder for each
recipe group. The definition contents of other project cannot be downloaded to exceed the
domain.
Define the product control windows using each of the Product Control Builders of the
upper- and lower-level projects for each recipe group. The newly created product control
windows will become valid only if operation and monitoring are performed from the upper-
level HIS. The product control window to be used on the lower-level project side must be
created by the lower-level project. The content defined in the lower-level project can be
reflected in the Product Control Builder of the upper-level project via import operation.
Definition of Common Blocks
Common blocks are created on the lower-level project side, so they are not defined on the
upper-level project side.
Definition of Trains
Trains are created on the lower-level project side, so they are not defined on the upper-
level project side.
Definition of Master Recipes
Master recipes are created on the lower-level project side, so they are not defined on the
IM 33S01B30-01E
G8.1.2 Engineering of the Lower-Level Project (CS 1000)
This section describes the engineering of the lower-level project (CS 1000) when a
CS 3000 and CS 1000 are connected.
G080110E.EPS
the lower-level project (CS 1000).
End engineering of
Define the operation monitoring station on the
upper-level project side that gives notifications
of equalization as an UHMIS (unified operation/
monitoring station).
Define other items.
Define trains.
Download the tag list to new UHMIS
(unified operation/monitoring station).
Restart all stations in the lower-level project.
Connect Ethernet to CS 1000.
For items enclosed by dashed lines,
see M9, Multiple Project Connection.
Figure Engineering Procedure for Lower-Level Project (CS 1000)
IM 33S01B30-01E
Definition of Upper-Level Projects Operation/Monitoring Station
It is necessary to download the tag list of the lower-level project to the HIS of the upper-
level project that is to be specified as a client station. If a tag list is not downloaded, equip-
ment requirements cannot be specified during recipe setup.
Define the HIS of the upper-level project as a UHMIS (unified operation/monitoring station)
on the lower-level project side. The UHMIS thus defined can be specified as the client
station of the lower-level project.
For the station address, specify the station address that is being used by the HIS of the
upper-level project. If a station alias is set in the HIS of the upper-level project, specify the
station alias.
For the Control Bus TCP/IP Settings and Ethernet TCP/IP Settings on the network tab
sheet, set the same values as for the HIS of the upper-level project.
Note that there is no definition relating to station configuration for the upper-level project.
IM 33S01B30-01E
Define the recipe groups that connect projects using the Process Management Configura-
tion Builder on the lower-level project side. It is necessary to set the same number in the
upper- and lower-level projects for the recipe group number used to connect projects.
When connecting the projects, the client station item must be carefully defined. Other
recipe group definitions, as well as the contents of the process management configuration
definition, are the same as the definitions for a single project configuration. The following
explains the client-station definition method.
Define the client station according to the following:
Define the HIS station name of the lower-level project that is to become a recipe client.
The HIS station name of the lower-level project can be selected from the drop-down
menu. If a station alias is being used, the station alias can be selected from the menu.
Define the station name of the UHMIS (unified operation/monitoring station) of the
upper-level project that will become a recipe client, which is newly created in System
View of the lower-level project. The UHMIS station name can be selected from the
drop-down menu. If a station alias is being used, the station alias can be selected from
the menu.
G080111E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
Figure Example of Client-Station Definition
IM 33S01B30-01E
Other Definition
The following explains the definitions that are made by the lower-level project, in addition to
the upper-level projects operation/monitoring station definition and the process manage-
ment configuration definition.
domain.
upper- and lower-level projects for each recipe group. The product control windows that are
newly created will become valid only if operation and monitoring are performed from the
lower-level HIS. Create the product control window to be used on the upper-level project
side on the upper-level project side. The contents defined in the upper-level project can be
reflected in the Product Control Builder of the lower-level project via import operation.
The contents of the common block definition made by the Common Block Builder are
downloaded only to the server station defined by the Process Management Configuration
Builder. If a different server station has been specified for each recipe group, the contents
of the common block definition will be downloaded to all the stations specified as server
stations. No information will be downloaded to the client station.
The definition of common blocks is required only in the lower-level project.
TIP
The contents of the common block definition will be downloaded to the server station, but they will not be
downloaded to exceed the domain. When the server station of the lower-level project is specified in the
upper-level project, the contents relating to the common blocks of the upper-level project will not be
downloaded to the server station of the lower-level project.
The contents of the train definition made by the Train Builder are downloaded only to the
server station in recipe group units. No information will be downloaded to the client station.
The definition of trains is only required for the lower-level project.
Furthermore, define the unit name to be specified for the path of the Train Builder without
adding the Project ID specified by the Multiple Project Connection Builder.
TIP
If a recipe group of the lower-level project is created by the upper-level project, the train of the lower-level
project can be defined. However, it is not necessary to define the train in the upper-level project.
IM 33S01B30-01E
The master recipes defined by the Recipe Builder, and the recipe procedures and unit-
recipe procedures defined by the Recipe Procedure Builder are downloaded only to the
server station. No information will be downloaded to the client station.
The definitions of the master recipes, recipe procedures and unit-recipe procedures are
required only for the lower-level project. Moreover, if the unit name is specified in the
equipment requirements, define it without adding the Project ID specified by the Multiple
Project Connection Builder. Also, do not add the Project ID when defining the operation
name to be specified via the Unit Recipe Procedure.
<G8.2 Unilateral Connection between CS 3000s> G8-19
IM 33S01B30-01E
G8.2 Unilateral Connection between CS 3000s
Either the unilateral connection or bilateral connection can be used to connect CS
3000s. This section describes the unilateral connection of CS 3000s.
Overview of Unilateral Connection between CS 3000 Projects
Unilateral connection allows only the operation and monitoring of the lower-level project
from the upper-level project.
To operate and monitor a recipe of the lower-level project from the upper-level project,
HIS that is specified as the client station will perform operation and monitoring using the
recipe group number of the lower-level project.
ing shows an example of project connection configuration.
Ethernet
HIS
FCS
G080201E.EPS
Client
station
V net
HIS
Server
station
Ethernet
HIS
FCS
Server
station
V net
HIS
Client
station
BCV
Recipe group 2
Recipe group 1
Recipe group 1
Recipe group of
upper-level project
Recipe group of
lower-level project
CS 3000
CS 3000
TIP
G8-20 <G8.2 Unilateral Connection between CS 3000s>
IM 33S01B30-01E
This section describes the engineering of the upper-level project (CS 3000) when
two CS 3000s are connected via the unilateral mode.
G080202E.EPS
Start engineering
of the upper-level project (CS 3000).
exist.
End engineering of
Define other items.
Define trains.
IM 33S01B30-01E
Recipe comment
Server station
Client station
G080203E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
This definition
is ignored.
Recipe Comment
project side.
project side.
IM 33S01B30-01E
server.
menu. So, enter the HIS station name from the keyboard.
the server name.
Server station
1 HIS0464
2 HIS0463
G080204E.EPS
Server station
1 HIS0464
2 HIS0463
HIS0263 HIS0264
Client Client
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
IM 33S01B30-01E
Server station
1 BCH464
2 BCH463
G080205E.EPS
Server station
1 BCH464
2 BCH463
HIS0263 HIS0264
Client Client
HIS0461 HIS0462
BCH463
(HIS0463)
BCH464
(HIS0464)
STN0263 STN0264
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
Server station
1 BCH464
2 BCH463
G080206E.EPS
Server station
1 HIS0464
2 HIS0463
HIS0263 HIS0264
Client Client
BCH463
(STN0463)
BCH464
(STN0464)
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
these stations.
IM 33S01B30-01E
G080207E.EPS
Client station
1 HIS0462
2 HIS0461
3 HIS0264
4 HIS0263
5
6
Client station
1 HIS0462
2 HIS0461
3 STN0264
4 STN0263
5
6
HIS0263 HIS0264
Client Client
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
IM 33S01B30-01E
G080208E.EPS
Client station
1 BCH462
2 BCH461
3 BCH264
4 BCH263
5
6
Client station
1 BCH462
2 BCH461
3 STN0264
4 STN0263
5
6
BCH263
(HIS0263)
BCH264
(HIS0264)
Client Client
BCH461
(HIS0461)
BCH462
(HIS0462)
HIS0463 HIS0464 STN0263 STN0264
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
G080209E.EPS
Client station
1 BCH462
2 BCH461
3 HIS0264
4 HIS0263
5
6
Client station
1 HIS0462
2 HIS0461
3 STN0264
4 STN0263
5
6
FCS FCS FCS
HIS0263 HIS0264
Client Client
BCH461
(STN0461)
BCH462
(STN0462)
BCV-V
FCS FCS FCS
V net
V net
these stations.
IM 33S01B30-01E
Other Definitions
domain.
level project side.
IM 33S01B30-01E
G8.2.2 Engineering of the Lower-Level Project (CS 3000)
This section describes the engineering of the lower-level project (CS 3000) when two
CS 3000s are connected via the unilateral mode.
G080210E.EPS
Start engineering
of the lower-level project (CS 3000).
computer names are not duplicated in any
station in the projects to be connected.
End engineering of
Define other items.
Define trains.
Figure Engineering Procedure for Lower-Level Project (CS 3000)
IM 33S01B30-01E
Definition of Upper-Level Projects Operation/Monitoring Station
It is necessary to download the tag list of the lower-level project to the HIS of the upper-
level project that is to be specified as a client station. If a tag list is not downloaded, equip-
ment requirements cannot be specified during recipe setup.
Define the HIS of the upper-level project as a UHMIS (unified operation/monitoring station)
on the lower-level project side. The UHMIS thus defined can be specified as the client
station of the lower-level project.
For the station address, specify the station address that is being used by the HIS of the
upper-level project. If a station alias is set in the HIS of the upper-level project, specify the
station alias.
For the Control Bus TCP/IP Settings and Ethernet TCP/IP Settings on the network tab
sheet, set the same values as for the HIS of the upper-level project.
Note that there is no definition relating to station configuration for the upper-level project.
IM 33S01B30-01E
upper- and lower-level projects for the recipe group number used to connect projects.
When connecting the projects, the client station item must be carefully defined. Other
recipe group definitions, as well as the contents of the process management configuration
definition, are the same as the definitions for a single project configuration. The following
explains the client-station definition method.
Define the HIS station name of the lower-level project that is to become a recipe client.
The HIS station name of the lower-level project can be selected from the drop-down
menu. If a station alias is being used, the station alias can be selected from the menu.
Define the station name of the UHMIS (unified operation/monitoring station) of the
upper-level project that will become a recipe client, which is newly created in System
View of the lower-level project. The UHMIS station name can be selected from the
drop-down menu. If a station alias is being used, the station alias can be selected from
the menu.
G080211E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
IM 33S01B30-01E
Other Definition
domain.
TIP
TIP
IM 33S01B30-01E
G8-32 <G8.3 Bilateral Connection between CS 3000s>
IM 33S01B30-01E
G8.3 Bilateral Connection between CS 3000s
Either the unilateral connection or bilateral connection can be used to connect
between CS 3000s. This section describes the bilateral connection of CS 3000s.
Overview of Bilateral Connection between CS 3000 Projects
Bilateral connection allows the operation and monitoring of the lower-level project from the
upper-level project, and the upper-level project from the lower-level project.
To operate and monitor a recipe of the lower-level project from the upper-level project,
HIS that is specified as the client station will perform operation and monitoring using the
recipe group number of the lower-level project.
Vice versa, to operate and monitor the recipes of upper-level project from the lower-level
project, the HIS of the lower-level project should be configured to the upper level project as
a client station. Thus, from this HIS, the recipes of the upper-level project can be operated
and monitored using the upper-level project recipe group numbers.
Recipes can be downloaded from the server station in the self project. Therefore, only the
station in the self project can be specified as the server station.
<G8.3 Bilateral Connection between CS 3000s> G8-33
IM 33S01B30-01E
The following shows an example of project connection configuration.
Ethernet
HIS
FCS
G080301E.EPS
HIS
Ethernet
HIS HIS
BCV
CS 3000
CS 3000
Recipe group of
lower-level project
Recipe group 1
Client
station
Server
station
V net
Recipe group 2
Recipe group 3
Recipe group of
upper-level project
V net
Recipe group 1
Client
station
Server
station
FCS
TIP
IM 33S01B30-01E
Engineering Procedure for Bilateral Connection between CS 3000s
The following shows the engineering procedure for bilateral connection:
G080302E.EPS
Start engineering of both
the upper- and lower-level projects.
Perform engineering of the common part to be
used by both projects.
Perform the engineering of the recipe group in
which each of the self projects in both projects
becomes an upper-level project.
Perform the engineering of the recipe group in
which each of the self projects in both projects
becomes a lower-level project.
Download the projects common part to all
stations in both projects that will perform bilateral
connection.
Restart all stations in both projects.
End engineering of both
the upper and lower-level projects.
Figure Engineering Procedure for Bilateral Connection
IM 33S01B30-01E
G8.3.1 Common Engineering
This section describes the common engineering to be performed in both projects
when CS 3000 projects are connected in bilateral mode.
Procedure for Common Engineering to be Performed in Both Projects
The following shows the common engineering procedure that is performed in both projects.
Perform the engineering shown below in both projects.
G080303E.EPS
Start engineering of the common
part of both projects.
Confirm that the IP addresses and HIS computer
names are not duplicated in any station in the
projects to be connected.
exist.
Define the operation/monitoring station that gives
notifications of equalization.
Download the projects common part to all
stations.
End engineering of the common
part to be used in both projects.
Figure Common Engineering Procedure to be Performed
IM 33S01B30-01E
Definition of Multiple Project Connection Builder
Define the Multiple Project Connection Builder in both projects that are to be connected via
the bilateral mode.
Definition of Operation/Monitoring Station Notifying Equalization
Define the UHMIS (unified operation/monitoring station) that gives notification of equaliza-
tion via System Views of both projects to be connected bilaterally.
IM 33S01B30-01E
G8.3.2 Engineering of Recipe Group in which the Self Project
Becomes the Upper-Level Project
This section describes the engineering of the recipe group in which the self project
becomes the upper-level project when CS 3000s are connected in bilateral mode.
The recipe group in which the self project becomes the upper-level project signifies
the case when the HIS of the opposite project becomes a recipe server in bilateral
connection. In relation to this recipe group, the self project and opposite project
become upper- and lower level projects, respectively.
G080304E.EPS
End engineering of the upper-level
project recipe group.
Start engineering of the upper-level
Define other items.
Define trains.
Figure Procedure for Engineering of a Recipe Group that Becomes the Upper-Level Project
IM 33S01B30-01E
Using the Process Management Configuration Builder of the self project, define the recipe
group in which the self project becomes the upper-level project. Specify the same recipe
group number, which is used to connect projects, for the upper- and lower-level projects.
The following shows the contents of definition on the upper-level project side. The defini-
tions of other recipe groups and the process management configuration follow the process
management configuration definition on the lower-level project side. The definition on the
upper-level project side will be ignored.
Recipe comment
Server station
Client station
G080305E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
This definition
is ignored.
Recipe Comment
project side.
project side.
IM 33S01B30-01E
server.
menu. So, enter the HIS station name from the keyboard.
Do not select UHMIS (unified operation/monitoring station) from the drop-down
menu.
the server name.
G080306E.EPS
Server station
1 HIS0464
2 HIS0463
HIS0263 HIS0264
UHMIS UHMIS
BCV-V
FCS FCS FCS
FCS FCS FCS
Client Client
V net
Client Client Server #2 Server #1
V net
Server station
1 HIS0464
2 HIS0463
Server station
1 BCH464
2 BCH463
G080307E.EPS
Server station
1 BCH464
2 BCH463
HIS0263 HIS0264
HIS0461 HIS0462
BCH463
(HIS0463)
BCH464
(HIS0464)
STN0263 STN0264
UHMIS UHMIS
BCV-V
FCS FCS FCS
FCS FCS FCS
Client Client
Client Client
V net
V net
Server #2 Server #1
Figure Example of Definition when Station Aliases are Used
IM 33S01B30-01E
menu.
G080308E.EPS
Client station
1 HIS0462
2 HIS0461
3 HIS0264
4 HIS0263
5
6
Client station
1 HIS0462
2 HIS0461
3 HIS0264
4 HIS0263
5
6
HIS0263 HIS0264
UHMIS UHMIS
BCV-V
FCS FCS FCS
FCS FCS FCS
Client
V net
Server #2 Server #1
Client
Client Client
V net
IM 33S01B30-01E
G080309E.EPS
Client station
1 BCH462
2 BCH461
3 BCH264
4 BCH263
5
6
Client station
1 BCH462
2 BCH461
3 BCH264
4 BCH263
5
6
BCH263
(HIS0263)
BCH264
(HIS0264)
BCH461
(HIS0461)
BCH462
(HIS0462)
HIS0463 HIS0464 STN0263 STN0264
UHMIS UHMIS
BCV-V
FCS FCS FCS
FCS FCS FCS
Client Client
Client Client
V net
V net
Server #2 Server #1
Figure Example of Definition when Station Aliases are Used
IM 33S01B30-01E
Other Definitions
domain.
level project side.
IM 33S01B30-01E
G8.3.3 Engineering of Recipe Group in which the Self Project
Becomes the Lower-Level Project
This section describes the engineering of the recipe group in which the self project
becomes the lower-level project when CS 3000s are connected in bilateral mode.
The recipe group in which the self project becomes the lower-level project signifies
the case when the HIS of the opposite project becomes a recipe server in bilateral
connection. In relation to this recipe group, the self project and opposite project
become lower- and upper level projects, respectively.
G080310E.EPS
End engineering of the lower-level
Start engineering of the lower-level
Define other items.
Define trains.
Figure Procedure for Engineering of a Recipe Group that Becomes the Lower-Level Project
Define the recipe groups in which the self project becomes the lower-level project using the
Process Management Configuration Builder of the self project. It is necessary to set the
same number in the upper- and lower-level projects for the recipe group number used for
connecting projects.
The client station item must be carefully defined when performing bilateral connection.
Other recipe group definitions, as well as the contents of the process management configu-
ration definition, are the same as the definitions for a single project configuration. The
following explains the client-station definition method.
IM 33S01B30-01E
Define the client stations according to the following items.
Define the HIS station name of the self project that will become a recipe client.
The HIS station name of the upper-level project is not displayed on the drop-down
menu.
If a station alias is being used on the upper-level project side, enter the station alias.
IMPORTANT
Define the station name of a UHMIS (unified operation/monitoring station) as an upper
client for unilateral connection between CS 3000s. However, for bilateral connection, define
the HIS station name of the opposite project as an upper client.
G080311E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
IM 33S01B30-01E
Other Definition
domain.
TIP
IM 33S01B30-01E
TIP
<G8.4 Connecting CS 3000 and CS> G8-47
IM 33S01B30-01E
G8.4 Connecting CS 3000 and CS
When a CS 3000 and CS are connected, the upper-level project will be the CS 3000
and lower-level project will be the CS. If a plant name is being used in the CS, Batch
Management cannot be used.
Overview of Connection between CS 3000 Project and CS Project
The recipes of the lower-level project can be operated via the upper-level project by con-
necting the projects. However, the recipes of the upper-level project cannot be operated by
the lower-level project.
To operate and monitor the recipe of the lower-level project from the upper-level project,
HIS thus specified as the client station will operate and monitor recipes using the recipe
group number of the lower-level project.
ing figure shows an example of the project connection configuration.
Ethernet
HIS
FCS
G080401E.EPS
Client
station
V net
HIS
Server
station
Ethernet
FCS
Server
station
V net
Client
station
Recipe group 2
Recipe group 1
Recipe group 1
E net
BCV
CGW
EWS
ICS
ICS
Recipe group of
upper-level project
Recipe group of
lower-level project
CS 3000
CS
TIP
G8-48 <G8.4 Connecting CS 3000 and CS>
IM 33S01B30-01E
This section describes the engineering of the upper-level project (CS 3000) when a
CS 3000 and CS are connected.
G080402E.EPS
For items enclosed by dashed lines, see M9,
Multiple Project Connection.
exist.
End engineering of
Define other items.
Define trains.
Confirm that station names are not duplicated
in any station of the projects to be connected.
Confirm that the host names of ICS and host
names of EWS are not duplicated in any station
of the projects to be connected.
IM 33S01B30-01E
Recipe comment
Server station
Client station
G080403E.EPS
Ready
Batch ID %2G-%4N
Message
Server station
1 HIS0324
2 HIS0323
Client station
1 HIS0322
2 HIS0321
3 HIS0264
4 HIS0263
5
This definition
is ignored.
Recipe Comment
project side.
project side.
IM 33S01B30-01E
Define the ICS station name of the lower-level project that will be assigned as a recipe
server.
The ICS station name of the lower-level project is not displayed in the drop-down
menu. So, enter the ICS station name from the keyboard.
the server name.
Server station
1 ICS0164
2 ICS0163
G080404E.EPS
Server station
1 ICS0164
2 ICS0163
HIS0263 HIS0264
Client Client
ICS0161 ICS0162 ICS0163 ICS0164 STN0263 STN0264
BCV-V
FCS FCS FCS
FCS FCS FCS
Lower-level project (CS)
V net
V net
IM 33S01B30-01E
Server station
1 BCH164
2 BCH163
G080405E.EPS
Server station
1 ICS0164
2 ICS0163
HIS0263 HIS0264
Client Client
ICS0161 ICS0162
BCH163
(ICS0163)
BCH164
(ICS0164)
STN0263 STN0264
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
Server station
1 BCH164
2 BCH163
G080406E.EPS
Server station
1 ICS0164
2 ICS0163
HIS0263 HIS0264
Client Client
BCH163
(STN0163)
BCH164
(STN0164)
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
these stations.
IM 33S01B30-01E
A connection with a CS can employ a maximum of eight recipe clients.
G080407E.EPS
Client station
1 ICS0162
2 ICS0161
3 HIS0264
4 HIS0263
5
6
Client station
1 ICS0162
2 ICS0161
3 STN0264
4 STN0263
5
6
HIS0263 HIS0264
Client Client
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
IM 33S01B30-01E
G080408E.EPS
Client station
1 BCH162
2 BCH161
3 BCH264
4 BCH263
5
6
Client station
1 ICS0162
2 ICS0161
3 STN0264
4 STN0263
5
6
BCH263
(HIS0263)
BCH264
(HIS0264)
Client Client
BCH161
(ICS0161)
BCH162
(ICS0162)
ICS0163 ICS0164 STN0263 STN0264
BCV-V
FCS FCS FCS
FCS FCS FCS
V net
V net
G080409E.EPS
Client station
1 BCH162
2 BCH161
3 HIS0264
4 HIS0263
5
6
Client station
1 ICS0162
2 ICS0161
3 STN0264
4 STN0263
5
6
FCS FCS FCS
HIS0263 HIS0264
Client Client
BCH161
(STN0161)
BCH162
(STN0162)
BCV-V
FCS FCS FCS
V net
V net
then define station aliases
for these stations.
IM 33S01B30-01E
Other Definitions
domain.
level HIS.
level project side.
IM 33S01B30-01E
G8.4.2 Engineering of the Lower-Level Project (CS)
This section describes the engineering of the lower-level project (CS) when a CS
3000 and CS are connected.
G080410E.EPS
Start engineering
of the lower-level project (CS).
End engineering
of the lower-level project (CS).
Define other items.
Define trains.
Perform a ICS selection master load for all
stations in lower-level project.
Confirm that station names are not duplicated
in any station of the projects to be connected.
Confirm that the host names of ICS and host
names of EWS are not duplicated in any station
of the projects to be connected.
Figure Engineering Procedure for Lower-Level Project (CS)
IM 33S01B30-01E
upper- and lower-level projects for the recipe group number used for connecting projects.
The client station must be carefully defined when connecting projects. Other recipe group
definitions, as well as the contents of the process management configuration definition, are
the same as the definitions for a single project configuration. The following explains the
client-station definition method.
Define the ICS station name of the lower-level project that will become a recipe client.
Define the station name of the unified operation/monitoring station (UHMIS) of the
upper-level project that will become a recipe client, which has been defined by the
System Configuration Definition Builder of the lower-level project. Although any station
name stipulated for CS stations can be defined on the System Configuration Definition
Builder of the lower-level project, use the same name employed in the Process Man-
agement Configuration Builder.
G080411E.EPS
Type Name Address Comment Plant name
AIH21C ICS0164 01.64 BatchServerICS
AIH21C ICS0163 01.63 BatchServerICS
AIH21C ICS0162 01.62 BatchClientICS
AIH21C ICS0161 01.61 BatchClientICS
UHMIS STN0264 02.64 BatchClientHIS
UHMIS STN0263 02.63 BatchClientHIS
Client station
1 ICS0162
2 ICS0161
3 ICS0160
4 STN0264
5 STN0263
6
7
8
Lower-level project Process management configuration definition
Lower-level project System-configuration definition
Define the same station names.
Batch Management
cannot use plant names.
Figure Example of Client Station Definition
IM 33S01B30-01E
Other Definition
CS Batch does not have a builder with which to define product control windows. The
product control windows are fixed by the system.
downloaded only to the server station defined for each recipe group. If a different server
station has been specified for each recipe group, the contents of the common block defini-
tion will be downloaded to all the stations specified as server stations. No information will
be downloaded to the client station.
TIP
TIP
Master recipes, recipe procedures and unit-recipe procedures are downloaded only to the
server station.
No information will be downloaded to the client station. The definitions of the master reci-
pes, recipe procedures and unit-recipe procedures are required only for the lower-level
project.
Moreover, if the unit name is specified in the equipment requirements, define it without
adding the Project ID specified by the Multiple Project Connection Builder. Also, do not
add the Project ID when defining the operation name to be specified via the Unit Recipe
Procedure.
Blank Page

Ref Batch Management

Uploaded by

Document Information

Original Description:

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

Ref Batch Management

Uploaded by

Copyright:

Available Formats

Toc G-1

Form when the status of the

From when the status of the

You might also like