Technical Information

TI 33M05L10-40E

VP Batch Batch Management Package

Yokogawa Electric Corporation 2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan Tel.: 81-422-52-5634 Fax.: 81-422-52-9802

TI 33M05L10-40E ©Copyright Oct. 2010 (YK) 1st Edition Oct. 2010 (YK)

Blank Page

i

Introduction
The VP Batch is the CENTUM VP Batch Management Package. VP Batch is designed for the management of batch operations with the CENTUM VP Integrated Production Control System. It has been derived from Yokogawa’s extensive experience with distributed control systems (DCSs) and wide-ranging batch applications, and complies with international standards of batch processes.

Documentation Configuration
This manual is composed of the following chapters: Chapter 1 introduces the concepts of batch processes. Chapter 2 covers ISA-88 compliance of the VP Batch software. Chapter 3 summarizes the VP Batch software. Chapter s 4, 5 and 6 describe its recipe management function, process management function, and unit supervision function. Chapter 7 describes the VP Batch Operation and Monitoring Windows. Chapter 8 introduces the Access Administrator function (FDA : 21 CFR Part 11) Chapter 9 is a glossary of terms.

Applicable Readers
This manual is intended for instrumentation/electrical engineers with basic knowledge about DCSs, who want to know the outline of VP Batch or are considering their application.

All Rights Reserved Copyright © 2010, Yokogawa Electric Corporation

TI 33M05L10-40E

Oct. 29, 2010-00

Blank Page .

.......................................................................... 6-4 6.............. 6-2 Unit Data..........1 6.......Toc-1 VP Batch Batch Management Package TI 33M05L10-40E 1st Edition CONTENTS 1........................................................ 1-1 1.........................6 Control Recipe Setup .................. 3-2 Recipe Structure ..........1 3...... 4-8 Overview ....... 5-3 Reuse of Control Recipe ..................................... 4-7 Access Control Function ...................................................................................1 4.............. 3-6 Unit Supervision ............................. 3-1 3..............................2 6... 4-1 4............................................................................1 Requirements for DCS Manufacturers ............3 5............................................................ Unit Supervision Function ..................................................................................................................... Process Management Function....................................................3 4.........2... 5-2 Control Recipe Setup ...4 4...................... 29........ 5-5 4.5 4...................................................................2 Batch Control .................................................................... 3-3 Recipe Setup and Downloading ............... 4-5 Formula ......................... 3.......... 6-9 Unit Mode and Status ............. 3-5 Batch-Operation Monitoring ................. Batch Processes ........................................................................ 6-3 Unit Procedure ....................................................................................................................................................................1 5.....................5 Recipes .........2 5......................................................................................................... 6-1 6....................................5 5....................... 2............................... 5-1 5.................................. 5-16 Production Planning and Scheduling Interface ..................4 6............................................................................................3 6........................................................2 4............................2 3......1 5.......................................... Recipe Management Function ......................1 SFC Language . 6-11 TI 33M05L10-40E Oct................................... 4-2 Header .....................................6 5.................................... 2-1 Overview of VP Batch Software ............................................. 4-7 Equipment Requirements .....................4 3.........................................................2..................................... 3-7 Overview of Recipe Management ........... 5-7 Batch Results ......................... 6-5 Operation ............................................................................................ 5-3 5............................................................................................................................................. 4-4 Procedure ..................... 2010-00 6.........................3..................................................................................................................................................................................................................................................................4 5....................3 3............... 1-3 ISA-88 compliant VP Batch ............................................ 5-18 Unit ........................................... 5-13 Server/Client Function Redundancy ..5 ............................

........ 6-13 Using Generic Name and Sharing Resources ............................................................... 8..................... 9-1 TI 33M05L10-40E Oct................................................ VP Batch Operation and Monitoring Windows ........ 8-1 Glossary ...........................8 6...................................... 2010-00 ........Toc-2 6...................................... 7-1 FDA : 21 CFR Part 11 Compliant ......7 6..................................6 6............... 6-16 7... 6-15 The definition of link between Common Block & Operation ........ 9.................................6-14 Status Transition Matrix ...............................9 Initialization and Monitoring Operation .................... 29.....

Single-Product Process TI 33M05L10-40E Oct. single-product process (see below) • Multi-path.” The continuous-process operation is performed continuously without any shutdown. multi-product process • Variable-path process (see next page) F010101. heating. multi-path. 2010-00 . 29. for example. A recipe is used for process actions of charging. In a continuous process.ai Figure Single-Path. and so forth.” Batch Process The term “batch process” is commonly used in contrast with “continuous process. A batch process applicable to only one product is called a “single product” process and one applicable to a number of products a “multi-product” process. Batch Processes This chapter defines the word “batch processes. for example. in every operation cycle. in a predetermined period of time. cooling. The operation of reactors is a representative example. single-product process (see next page) • Single-path. The batch-process operation is performed repeatedly in a cycle of a few hours or days. The operation of distillation columns is a typical example. reaction. at oil refineries and power plants. Thus there are the following types of batch processes: • Single-path. pressures. and discharging. often extending for a year or longer. to output a predetermined quantity of product. and variable path structures according to how the processes are incorporated in a plant.1. A batch process features an increase in operation frequency to increase production quantity and process’s applicability to production of other products. which are further classified into single-path. or a batch. raw materials are input and products are output at the same time while maintaining steady states of temperatures. Batch Processes 1-1 1. multi-product process (see next page) • Multi-path.

1. 2010-00 . Single-Product Process F010103.ai Figure Variable-path Process TI 33M05L10-40E Oct. 29.ai Figure Single-Path. Multi-Product Process F010104. Batch Processes 1-2 F010102.ai Figure Multi-Path.

and to upload batch production data to the computer. Batch Processes 1-3 1.S. Now users demand the following DCS for batch processes: Requirements for DCS Manufacturers Adaptability A DCS has a number of recipes in order to use the same group of equipment for production of different products. The DCS must flexibly perform operation even if recipes and procedures vary. selecting the standardcompliant packages for batch process control is vital for enterprises. 2010-00 .1 The control of a batch process is dependent on the close alliance of continuous control and sequence control as in the control of a reactor. In batch processes.S. the regulation of electronic records and electronic signatures established by FDA (Food and Drug Administration) of U. The DCS must also support all types of batch processes from a single-path. Compliance with International Standard (ISA-88.. the standard windows should be used for uniformity in operation and monitoring and easy operation.1. new recipes must be added without affecting processes. Also. etc. is a recent key issue of the pharmaceutical companies.01 and 21 CFR Part 11) ISA-88 of U. new recipes are often added. temperature setting. single-product process to a variable process. complying with 21 CFR Part 11. and NAMUR of Europe are working on standardization of batch process. Easy Operation Although DCS windows may be modified if batch-process recipes or procedures are varied. TI 33M05L10-40E Oct.) and process-phase control procedure. In this case. Each recipe contains data (charging volume. In batch processes. Open Environment It must be easy to download recipes and schedules from a supervisory computer. 29. The new recipes may be different from the old ones in data and procedural combination only. an operation monitoring window is also required for every control unit because a batch process is often separate from each other. To increase internationalization of production.

than sharing and reusing them. 2010-00 . and the programming of a batch process takes more time than that of a continuous process. 29. Batch Processes 1-4 Higher Engineering Efficiency It is said that every batch control varies and is not uniform. The VP Batch is designed to automate and systemize batch processes to fulfill these demands. TI 33M05L10-40E Oct. By dividing programs in to layers. efficiency in the programming and maintenance can be improved.1.

ISA-88 compliant VP Batch This chapter covers ISA-88 compliance of VP Batch software. models and functions does: • Promotes optimum plant design and operation. 29. 2010-00 .01 presents a number of batch-process models including Physical Model. ISA-88 The Instrument Society of America (ISA) -88 Batch Control Standards Committee has been organized to provide batch control standards. The Batch Control Part 1: Models and Terminology was released as ISA-88. • Increases applicability.01 Physical Model & VP Batch TI 33M05L10-40E Oct. ISA-88. see Chapter 3.01 in 1995.01 Physical Model The ISA-88. For VP Batch software. ISA-88 compliant VP Batch 2-1 2. models and functions for batch manufacturing plants and batch control system. The standardization of terminology. The following figure shows the relationship between Physical Model and VP Batch software.ai Figure ISA-88.2. Purpose To define terminology. Enterprise Site (factory) Area (plant) Process cell Unit Equipment module Control module Production management Recipe group/Train Unit (instrument) Operation Function block SEBOL block Sequence table block Logic chart block <VP Batch> F020201. • Improves batch control.

A unit executes a procedure such as reaction.ai Figure ISA-88. control module) are provided by grouping devices or equipment through batch engineering. The model illustrates the total image of batch control and inter-functional relationships — various functions are required to perform batch-process operation. site. and control recipes. Recipe management (*1) Production planing and scheduling Production information management Process management Unit supervision (*2) *1: : Covered by the VP Batch software Process control (function block) *2: The ISA-88. without VP Batch Recipe Management and Process Managenent packages. The lower four levels (process cell. site. 29. F020202.01 Control Activity Model and VP Batch software. but the VP Batch software supports master and control recipes.01 Control Activity Model & VP Batch TI 33M05L10-40E Oct. recovery and drying. 2010-00 . ISA-88 compliant VP Batch 2-2 The Physical Model divides physical resources of an enterprise into seven hierarchical levels — the upper three levels (enterprise. which are described in Chapters 4-6. master.2. equipment module. area) have not been discussed in detail in ISA-88. An equipment module executes an operation such as charging and measuring. It runs by itself. A process cell is composed of more than one train. A train is a group of units required to perform each batch operation. The following figure shows the relationship between ISA-88.01 Recipe Management covers general. unit. The Unit Supervision has standard FCS functions.01 because of their business-oriented nature.

Unit 2. etc. The VP Batch software show sequential function charts (SFC) as operation windows regardless of recipes with different procedures — it is not easy to provide such flexibility with graphically created windows. 1. Monitoring batch-process operation.3. HIS mgt. F030001. General Purpose PC Recipe Creates a product recipe containing data and procedures. 2010-00 . by downloading a recipe. data. 2. 5. • They comply with ISA-88. 3. Receiving batch ID. the VP Batch software control the entire function of batch-process operation. Downloading a recipe to FCS and giving start Process command. Notifying processmanagement of operationcompletion. • They have unified windows for batch-process operation. Deleting a recipe. 6. Overview of VP Batch Software The VP Batch is designed to simplify installation of a batch program on the CENTUM VP system and implement full capabilities. • They have their own control data and algorithms..ai Figure Flow of Batch-Process Operation Some conventional batch packages permit programming variable data in recipes and downloading the data to the controller when the operator commands it. The flow of a batch-process operation is divided into four sections to cover VP Batch: • Recipe structure • Recipe setup and downloading • Batch-operation monitoring • Unit supervision TI 33M05L10-40E Oct. 4. as shown in Chapter 2. Starting specified unit upon FCS supervision receiving start command. The following shows the flow of a typical batch operation and the relationship among the three parts. Overview of VP Batch Software 3-1 3. procedure. mgt. The VP Batch is comprised of recipe management.01. 3. Unlike these packages. process management. The software have the following features: • They can modify procedures as well as formula. or HIS 1. They are designed in modules and hierarchy. Receiving operationcompletion notification and collecting operation data. Assigning unit and batch ID (setup). 29. and unit supervision. Selecting a recipe for product.

according to the required actions. resources. It may have been modified to account for actual raw material qualities and actual equipment to be utilized. the amounts of raw materials are specified as relative values rather than absolute values. batch size. 29. Control Recipe A control recipe contains information necessary to manufacture a particular batch of product. is the recipe level that is targeted to a specific process cell or a set of that process cell’s equipment. the VP Batch handles master recipes and control recipes.ai Figure Recipe Types Master Recipe The master recipe.1 A recipe is an entity that contains the minimum set of information that uniquely defines the manufacturing requirements for a specific product. General Recipe Product-specific processing information Recipes Site Recipe Site-specific information Master Recipe Process cell-specific information Control Recipe Batch ID.01 standard defines four types of recipes as shown below. Of these four. Generally. The Process Management Package mainly handles control recipes. in-process. which is derived from a general recipe or a site recipe.3. execution parameters must be specified according to the set of process cell equipment for batch processes and the size of the batch being processed in that process cell. Overview of VP Batch Software 3-2 3. To derive a control recipe from a master recipe. TI 33M05L10-40E Oct. operator-and/or system-generated information F030101. 2010-00 . and so on. It has detailed information for plant operation. while the Recipe Management Package primarily deals with master recipes. The ISA-88.

2010-00 . For example. Overview of VP Batch Software 3-3 3. it defines how to use a mixing unit. Recipe Recipe Structure Header Procedure Formula (recipe data) Equipment requirements F030201. A unit recipe procedure defines how processes are executed in each step described in a recipe procedure.ai Figure Recipe Procedure and Unit Recipe Procedure TI 33M05L10-40E Oct. the create date. 1 1 2 3 Mixing Unit 1 Reactor 1 Crystallization 1 2 3 5 6 7 <Recipe Procedure> Initialize Charge Heat Reaction Cool Discharge 4 Mix <Unit Recipe Procedure> F030202. a reactor. the issue date and other administrative information Procedure: Contains a procedure to make a product. Equipment Requirements: Contains requirements of equipment required to make a product.ai Figure Recipe Structure Header Contains the recipe name. the version and other administrative information. Procedure Contains two procedures to make a product: recipe procedure and unit recipe procedure. Formula: Contains parameters and recipe data to make a product. A recipe procedure describes the order of used units. and a crystallization unit. 29.2 The recipe generated by VP Batch Recipe Management has the following four items: Header: Contains the recipe version. The following figure shows the relationship between recipe procedure and unit recipe procedure.3.

29. Equipment requirements Equipment requirements constrain the choice of the equipment that will be used to manufacture a product. TI 33M05L10-40E Oct. It is stored in system-specific common block and user-definable common block. they may be expressed in a manner that specifies allowable equipment in each step of a recipe procedure. because they are downloaded to the FCS. temperature set points. batch ID. An execution program resides in the FCS. and data required for the batch process in the manufacture of a product. while the user-definable common block contains the amount of raw materials. 2010-00 . Procedures and formulas are the most important information among the four types. For example. A recipe does not include an execution program to turn on/off a valve. The unit recipe procedure defines the strategy of carrying out the execution program. status and other data.3. Overview of VP Batch Software 3-4 Formula The formula (recipe data) is a category of information that includes process parameters to manufacture a product. The system-specific common block contains the recipe name.

Control Recipe Unit Recipe 1 1a 1b 1c Recipe Setup and Downloading Unit Recipe 2 2a 2b 2c Unit Recipe 3 3a 3b 3c <VP Batch> <Processes> F030301. 2010-00 .” To set up a recipe. as shown below.3 A master recipe is a group of information. multi-product process and a variablepath process. one has to define the equipment of the FCS that will be used for the recipe at the initiation of the batch. Overview of VP Batch Software 3-5 3.3. Now recipe setup is complete. It must be changed to a control recipe and sent to the FCS to use in the FCS-resided execution program. 29.” “2b. The VP Batch is a batch package for a multi-path. The name is called “batch ID. It allows recipe downloading for any combination of equipment as long as process requirements are met.” and “3a.” Next. when multiple equipment are required to manufacture a product. A control recipe is divided into more than one unit recipe according to the number of equipment to be utilized. a master recipe is changed to a control recipe.” The following figure shows that a recipe is assigned to the equipment “1a. and downloaded to the FCSs. Changing a master recipe to a control recipe is called “setup.ai Figure Downloading a Recipe TI 33M05L10-40E Oct.” and sending it to the FCS is called “recipe downloading. one has to give a name to the product manufactured using the recipe in order to distinguish them from products which have been created at different time or by different equipment.” After unit assignment and addition of batch ID. which is called a “unit assignment.

One is product-basis monitoring to monitor the progress of the entire operation. and how batch operation and each unit recipe are being operated. 2010-00 . Overview of VP Batch Software 3-6 3. etc. There are two approaches to monitor the operation. This window shows by which unit a product is made.3. Batch-Operation Monitoring TI 33M05L10-40E Oct. The HIS is used as a human interface to monitor the operation. Creating a graphic view to understand the status of a unit (device) that is executing the unit recipe enables the operation and monitoring of the device. For monitoring the entire batch processes. and the other is unit-basis monitoring to monitor the state of the currently-operated unit. actual batch operation starts in the FCS. The window displays the following items: • Recipe group name/train name/path name • Recipe name/comment • Equipment requirements • Recipe status • Recipe description • Production start and end times • Planned production start and end times • Batch ID • Lot number and user codes • Unit recipe status • Unit names • User-defined common block data. The Product Control View may be customized by graphics builder. the Product Control View is used.4 After a control recipe is downloaded to the FCS. 29.

it is downloaded from a control recipe. There are two types of units: a unit with or without a procedure. or logic chart block. UNIT Unit procedure *1 Charge Heat React Discharge Unit data Mode Status Operation start time Batch ID User-defined data Others Step Operation “Charge” ~ FIC100. Overview of VP Batch Software 3-7 3. operation. For example. and described using the SEBOL. The operation. sequence table. for example.LS=“AUT” drive[Valve_1=on] end ~ Initialize program FeedA Phase Operation procedure Charge start Charge end *1: When a procedure does not reside in a unit. The unit data indicate the condition of the equipment under the unit supervision function and divided into unit-specific and user-defined data. TI 33M05L10-40E Oct.” “heat. it can be downloaded from a control recipe/process management. Unit Supervision Unit Structure Units can reside independently in the FCS without being related to the control recipe. the execution order of “charge. 29. The structure of a unit and the downloading of a recipe are explained in this section. F030401. and unit data. is realized using the SFC block and includes the operation procedure and phases.5 The unit supervision function controls the batch process according to the downloaded recipe. to turn valves on and off or change regulator settings.ai Figure Unit Structure (Unit with a Procedure) As shown above. 2010-00 . The phases are used in actual operation. which is the sequence of each step started by the unit procedure.” and “discharge” as one step is described.3. If a procedure does not reside in a unit. The unit procedure describes the execution order of phases in the unit using the SFC block. the unit contains the unit procedure.” “react.

2010-00 . Control Recipe Recipe procedure Unit recipe procedure Unit recipe procedure Unit recipe procedure Header Equipment requirements Formula Temperature Charging volume Download Download Unit Unit recipe procedure Charge Heat Reaction Discharge Step Unit data Mode Status Execution time Batch ID User-defined data Common block Data Access from Phases F030402.3.ai Figure Unit Structure (Unit without a Procedure) TI 33M05L10-40E Oct. Overview of VP Batch Software 3-8 Downloading a Recipe Data and procedures are downloaded from the control recipe. The unit recipe procedure in a recipe is downloaded to the unit procedure. properly assigning operations to the units according to the steps used in the procedure. which can be accessed from the phase. The formula (recipe data) is not downloaded to the data area of the unit and remains outside of the unit as common block data. 29.

2010-00 . TI 33M05L10-40E Oct.4. Recipe Management Function This chapter describes the recipe management function of the VP Batch software. 29. Recipe Management Function 4-1 4.

29. ISA-88.02 Structure Overview of Recipe Management Recipe management Production planning and scheduling Production information management Production planning and scheduling interface OPC interface Process management Unit supervision F040101.ai Figure Positioning of Recipe Management Features Recipe Management does: • Managing master recipes • Editing recipes • Equalizing recipes • Security Management function TI 33M05L10-40E Oct. Recipe Management Function 4-2 4. 2010-00 .1 The Recipe Management is positioned at the same level as production planning and scheduling. Recipes are classified into groups.4. This function independent from the builder can be used as separate application. production information management. It primarily serves as an interface for process management. which generate and save master recipes.

Master recipes and control recipes are managed by a recipe group. or by product.000 recipes/recipe group Max.ai Figure Recipe Configuration TI 33M05L10-40E Oct.ai Figure Configuration of Recipe Groups One recipe managed by the Recipe Management consists of the following elements: Header: Contains the recipe version. 32 recipes/master recipe Max. Recipe Management Function 4-3 VP Batch recipes are managed by a recipe group. 1. 64 path menus/master recipe Project Recipe group 1 Recipe group 2 Recipe group 16 Master recipe Control recipe Master recipe Control recipe F040102. Any recipe is not managed by a few recipe groups. Number of recipe groups: Recipe to be managed: Number of master recipes: Number of unit recipes: Number of path menus: Max. 29. 16 groups/project Master recipe Max. 2010-00 . Recipes may be grouped by a physical layer such as area or production cell.4. the create date and other administrative information Procedure: Contains a procedure to make a product Formula: Contains parameters (recipe data) to make a product Equipment Requirements: Contains equipment requirements necessary to make a product Recipe Header Procedure Formula Equipment requirements F040103.

version and issue date.2 A header contains administrative information. download mode and start mode cannot be displayed on the Operation and Monitoring Window. A header’s elements are included in a control recipe. but elements excluding a recipe name. 2010-00 . Recipe Management Function 4-4 4. Header TI 33M05L10-40E Oct. These data are used for Recipe Management and Production Information Management. such as recipe name. description. Neither can these elements be downloaded to the FCS.4. 29.

Master recipe Recipe procedure Procedure Unit recipe procedure Unit recipe procedure Unit recipe procedure Operation Operation Unit supervision Phase Phase Phase Phase F040301.4. A recipe procedure shows the order of more than one unit procedure used in a recipe. 2010-00 .ai Figure Configuration of Procedure Unit recipe #1 1A 1B Recipe procedure 1A #2 2A 2B 2B #3 3A 3B 3A F040302.3 A procedure is a series of steps which stipulate the order of actions for a batch process.ai Figure Example of Recipe Procedure TI 33M05L10-40E Oct. 29. The Recipe Management defines recipe procedure and unit recipe procedure. Recipe Management Function 4-5 4.

2010-00 . which is described using the SFC (Sequencial Function Chart). 1 2 3 6 7 8 9 Initialize Charge Heat Branch Discharge Wash End F040303.ai 4 Add 5 Agitate Figure Example of Unit Recipe Procedure TI 33M05L10-40E Oct. defines the execution order of the operations defined in the unit recipe. 29. Recipe Management Function 4-6 The unit recipe procedure.4.

16 “-” (dynamic unit assignment) applicable Equipment Requirements Requirements Train-path specification (*1) Unit menu specification Used as defined information for process control *1: Trains: Paths: Max 16/recipe group Max. 2010-00 .4 A formula (recipe data) is a set of parameters used to produce a product.ai Figure Formula (Recipe Data) Structure 4. Train 1-Path 1 Train 2-Path 3 Name of the units used for each unit recipe Remarks “*” (wild card) applicable Max.. such as charging volumes.g. Master recipe Formula (recipe data) Formula Common block name Common block name Common block name Data item name Data item name Data value Data value Data attribute Definition using common block Data attribute F040401. temperature settings. 29. and result data. A master recipe has data values only. Table Configuration of Equipment Requirements Description 64 at maximum of a combination of train-path E. so use a common block for defining formula data attributes.4. It is divided into data values and attributes (data type.5 Equipment requirements show the conditions required to make a product. item comments). 64/train TI 33M05L10-40E Oct. Recipe Management Function 4-7 4. display format.

delete. Access Control Function Recipe Engineer Authentication and Authority Check This verifies identity and if the recipe engineer has the authority to perform the job. Cannot create. download a recipe. a system engineer. Can download recipes from Recipe View/Builder. Write. delete. Cannot create. Cannot create.6 Access Control Function of CENTUM VP is to protect systems and data from any breakins and to control individual operations by authenticating an operator. delete. delete. the management of a system engineer (System View/Builder) and a recipe engineer (Recipe Management Function) are ensured besides the conventional management for operators by User Name and Password enabled only in HIS Operation and Monitoring Function. delete. Download. The Authority Types Read (*1) Write Delete Download Approve (future function) Engineering (*2) *1: *2: All recipe engineers are automatically entitled Read authority and cannot set the authority scope. edit a project and a recipe group. TI 33M05L10-40E Oct. edit. Can delete a recipe. 2010-00 . edit a project and a recipe group. Can write in the recipe-approval person field. 29. This section covers the recipe engineer management (Recipe Management Function). Can create. Cannot create. Table The Authority Types Description Can start Recipe Builder/Procedure Builder and view recipes. edit a project and a recipe group. Delete. Cannot delete and download a recipe. delete. Recipe View and Builder are Read Only. and Approve (future function)). Cannot download a recipe. and a recipe engineer. By using this function. Cannot create. Can create and edit a recipe. Engineering authority plus Download authority for one recipe engineer. Can start Recipe Builder/Procedure Builder and view recipes. edit a project and a recipe group.4. For instance. Recipe Management Function 4-8 4. edit a project and a recipe group. Engineering authority can be used with Recipe-related authority (Read.

TI 33M05L10-40E Oct. 2010-00 . Process Management Function This chapter describes the process management function of the VP Batch software. 29. Process Management Function 5-1 5.5.

from the creation of control recipes to their completion. Master recipe Recipe setup HIS Control recipe (RESERVED) Control recipe (LOG) Completion of execution Control recipe (COMPLETE) Downloading Start of Control recipe execution Control recipe (READY) (ACTIVE) FCS Uploading Completion Control recipe of execution (LOG) Delation Control recipe (COMPLETE) F050101. 2010-00 . The figure below shows the flow of a batch. 29. Execution data acquisition The data resulted during batch execution are collected by a batch basis. Message generation Messages are generated to notify the start and end of batch execution and status changes.ai Figure Flow of Batch TI 33M05L10-40E Oct. Batch execution control A batch operation is controlled according to the transition of recipe statuses.5. Process Management Function 5-2 5.1 The process management function controls the execution of batch operation. It implements: Overview Control recipe create A control recipe can be created by copying a master recipe or a control recipe that has once been tuned.

which have achieved good production results. 2010-00 . Unit assignment Assign the unit or units to be executed for the selected master recipe.” At control recipe setup for a batch.2. Master recipe selection Select the master recipe to be used on the Product Overview. Control Recipe Setup 5. TI 33M05L10-40E Oct. This execution is called “Control recipe setup. Setup Procedure Follow the procedure below for the setup of a control recipe on the Product Overview. Reference trend display is a function to display the trend of a completed batch for which a reference batch ID is specified on top of the real time trend of a batch being executed. Process Management Function 5-3 5.5. Setting of Reference Batch ID Specify a batch ID of a completed control recipe as a reference destination of reference trend display. Formula (recipe data) modification Modify formula (recipe data) of the master recipe if any formulas need be adjusted to execute the batch. 29.2 In the process management. the control recipes for actual production are created from the master recipe generated using the recipe management function.1 Control Recipe Setup A control recipe can be set up either by manual operations via the Product Overview or by a command in a program. Batch ID specification Give a name to the batch to be executed for its identification. Control recipe setup Execute instructions to set up the control recipe. “Control Recipe Copy” function enables to reuse the batch formula data in another batch.

“Train-Path designation” and “Direct designation. A batch ID must be unique and composed of up to 16 alphanumeric characters including hyphens. no zero-suppression) %nY: Reserved date: YYMMDD (n = 1 to 6 digits) %nM: Reserved date: MMDD (n = 1 to 4 digits) %nD: Reserved date: DD (n = 1 to 2 digits) %nT: Reserved time (n = 1 to 4 digits) %nN[t]: Numeric value increment [reset time: 00 thru 23] (n = no.” TI 33M05L10-40E Oct. of entered bytes) Characters: Fixed uppercase-character string (alphanumeric characters and hyphens only) • Examples of user-specified batch-ID format: BA-%4N → BA-0001 thru BA-9999 %6Y%2N → 93103101 thru 93103199 %2G-%4N → 01-0001 thru 01-9999 %2N-%4S → 01-**** thru 99-**** Unit Assignment Assigning a unit name to a unit recipe is called “unit assignment. of digits. • System-defined batch-ID descriptors: %nG: Reserved recipe group number (n = 1 to 2 digits. 2010-00 . Batch ID Descriptors Batch IDs.5.” There are two ways to assign a unit to a unit recipe. A user-specified ID format may be used for each recipe group. The batch ID can be entered in either one of the following manners: Manual Entry Batch IDs can be entered manually using the recipe setup window. Process Management Function 5-4 Batch ID Every batch must be named for its identification. which are unique in a group of recipes. 29. no zero suppression) Reset value: 1 %nS: Entered uppercase characters (n = no. are automatically attached using the systemdefined descriptors shown below.

2. some of formula data. Master Recipe Recipe Setup Original Recipe (Copied Recipe) Downloading Control Recipe Start Execution Control Recipe End Execution Control Recipe (RESERVED) (ACTIVE) (COMPLETE) Copy the initial parameters from master reicpe to control recipe Control Recipe copying function Copied Recipe Recipe Setup Control Recipe (RESERVED) Duplicating Downloading Start Execution Control Recipe End Execution Control Recipe (ACTIVE) (COMPLETE) F050202. 29. or export the modified formula data and feed it back to the original master recipe. such as “Batch ID” and “Reserved date and time”. While the most of formula data in the original recipe are copied to the copied recipe. Process Management Function 5-5 5. The source of copied recipe is called “Original Recipe”. the operator can make a copy of that control recipe containing the modified formula data (control recipe copying function) to set it up for the next batch. given the status “RESERVED” at first. For formula data “Origin Batch ID” of the copied recipe. the batch ID of the original control recipe is set up. but are set newly.2 Reuse of Control Recipe The operator can modify the formula data of a control recipe set up based on a master recipe. This control recipe set up is called “Copied recipe”. are not copied.ai Figure Flow of Control Recipe Copying Function TI 33M05L10-40E Oct. After this. Flow of Control Recipe Copying Function This function copies one of control recipes as another new control recipe and sets it up.5. 2010-00 .

Master Recipe Recipe Setup Control Recipe (RESERVED) HIS Downloading Start of Control Recipe execution Control Recipe (READY) (ACTIVE) FCS Uploading Control Recipe (LOG) Completion of execution Delation Control Recipe (COMPLETE) Control Recipe (LOG) Completion of execution Control Recipe (COMPLETE) Run export (Exported manually) Exported automatically Exporting Formula Exporting Formula CSV Format File For general-purpose CSV Format File For Recipe Builder CSV Format File For general-purpose F050201. It is possible to export the formula of the control recipe selected by the user as a CSV format file. 2010-00 . 29. Process Management Function 5-6 Exporting Formulas User can choose a formula and export the formula into a CSV format file.ai Figure Exporting Formula TI 33M05L10-40E Oct.5. Formulas can be exported in two ways. or they can be exported automatically when a batch is completed or the command to gather result data (GATHER) is issued. The formulas can either be exported manually from the Product Overview.

Being executed. Table Recipe Statuses Symbol RESERVED ASSIGNED NOASSIGN READY ACTIVE LOG COMPLETE ABORTED Description Reserved for execution. 2010-00 . x x x x x Control Recipe Status x x x x x x x x Unit Recipe Status Unit status: ACTIVE Unit recipe status 1: COMPLETE Unit recipe status 2: ACTIVE Unit recipe status 3: READY F050301. Downloaded and standing by. Batch Control Recipe Statuses The control recipe has Control Recipe Status indicating the state of the entire recipe and Unit Recipe Status showing the state of the unit recipe. Units not assigned.5.3 This section describes the execution and synchronization control of units used for a control recipe. 29. Data being acquired. Execution aborted. Process Management Function 5-7 5. Execution completed. The control recipe status changes in accordance with the status of the unit recipe contained in the control recipe.ai Figure Unit Status and Unit Recipe Statuses TI 33M05L10-40E Oct. Units assigned.

the status becomes NO ASSIGN if units have not yet been assigned. Indicates that the recipe has been aborted. 29.ai Figure Transition Between Recipe Statuses Table Control Recipe Statuses Description Indicates that recipe setup ended successfully and the required recipe has been reserved. This status can take place only when the recipe status is either RESERVED. A recipe is in the ACTIVE state when it is started. Upon reservation completion. A recipe is in this state if every unit recipe status is either ABORTED or COMPLETE and at least one unit recipe status becomes ABORTED.5. Indicates that the recipe is running. ABORTED or COMPLETE. the recipe is in the RESERVED state. 2010-00 . Process Management Function 5-8 Control Recipe Status Master Recipe Control Recipe Reserve END RESERVED LOAD READY START ACTIVE UP_LOAD LOG COMPLETE ABORT ABORT ABORT DELETE ABORTED DELETE DELETE DELETED F050302. Indicates that result data are being uploaded (logged). A recipe is in this state if all of the unit recipe statuses become COMPLETE. A recipe is in this state if every unit recipe status is either LOG or COMPLETE and at least one unit recipe status becomes LOG. Indicates that a control recipe has been deleted. the recipe status does not exist. Indicates that downloading has been completed and the downloaded recipe is waiting for execution (start). Notation RESERVED READY ACTIVE LOG COMPLETE ABORTED (DELETED) TI 33M05L10-40E Oct. The unit recipe status becomes ASSIGNED if units have already been assigned. The recipe is in the READY state when the shared section of the recipe is downloaded successfully. Since the control recipe disappears. Indicates that all of the recipes have been executed successfully.

Indicates that the result data are being uploaded (logged). 2010-00 . Indicates that units have been assigned to a unit recipe. This status takes place when uploading is completed or a unit recipe ends successfully. Indicates that all of the unit recipes have been executed successfully. This status takes place when the execution of a unit recipe has been completed. This status takes place when a unit recipe is started. This status takes place when the downloading of unit recipes ends successfully. 29. This status takes place if a unit recipe is aborted. Indicates that a unit recipe has been aborted. This status occurs when the assignment of units ends successfully. units are under dynamic (unit) assignment. or any of the assigned units are canceled. This status takes place if units have not yet been assigned.ASSIGN ASSIGNED ASSIGN READY START ACTIVE UP_LOAD LOG COMPLETE CANCEL ABORT ABORT ABORT ABORTED F050303. Since no data is available for uploading at the LOG status of a unit recipe. Indicates that unit recipes have been downloaded and are waiting for execution (start). this status takes place soon. Indicates that a unit recipe is running. Process Management Function 5-9 Unit Recipe Status Control Recipe END UNIT LOAD NO. Notation NO ASSIGN ASSIGNED READY ACTIVE LOG COMPLETE ABORTED TI 33M05L10-40E Oct.ai Figure Transition Between Unit Recipe Statuses Table Unit Recipe Statuses Description Indicates that units have not yet been assigned to a unit recipe. the dynamic assignment abnormally ends.5.

TIME: Automatically starts at the specified time. • Unit Recipe Downloading Mode AUT (default): Automatically downloaded as soon as the common part of the control recipe has been downloaded. the START directive will result in an error. Starting Modes • Recipe (Common Part) Starting Mode AUT (default): Automatically starts as soon as a control recipe has been downloaded. MAN: Manually starts. IMPORTANT • Change a batch mode during the recipe setup. is in use by another batch process when the start mode of that unit recipe is either AUT or TIME. You cannot change it after the recipe setup. MAN: Manually starts. Downloading Modes • Recipe (Common Part) Downloading Mode AUT (default): Automatically downloaded when the recipe has been reserved. In this case. • Downloading Modes: Receives a download command for a control recipe. the user must issue the START directive on the Operation and Monitoring Window. • Unit Recipe Starting Mode AUT (default): Automatically starts as soon as a unit recipe has been downloaded. • Starting Modes: Receives a start command for a recipe or a unit recipe. 2010-00 . TI 33M05L10-40E Oct. Process Management Function 5-10 Batch Modes A control recipe has batch modes to show whether the DownLoading Modes and Starting Modes are carried out automatically or manually. TIME: Automatically downloaded at the specified time. TIME: Automatically starts at the specified time. MAN: Manually downloaded. MAN: Manually downloaded.5. 29. which has been assigned to a unit recipe. TIME: Automatically downloaded at the specified time. • If a unit.

The dynamic assignment of units is useful when determining which unit to use for recipe #4. • 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. Unit recipe #1 UNIT A1 #2 UNIT A2 #3 UNIT A3 #4 UNIT A4 UNIT B4 F050304. Process Management Function 5-11 Dynamic Unit Assignment The dynamic assignment of units means to assign units to be run before a given unit recipe starts running. the UNIT A1 to UNIT A3 have already been assigned to unit recipes #1 to #3 at the time a given recipe is started. Using the Dynamic Unit Assignment to change the name of a unit already assigned. 2010-00 . UNIT A4 or UNIT B4 during the running of UNIT A3. the information on the original unit name will be lost. TI 33M05L10-40E Oct.ai Figure Example of Dynamic Assignment of Units As seen in the above example.5. The directive must be used for a unit recipe that is not yet started when: • units to be assigned are not assigned (NOASSIGN). 29.

type a unit name for separate specification of the unit name. the existing units are cancelled by the system so that the directive can take effect. • If the ASSIGN directive is issued on the Operation and Monitoring Window (or Product Control View) after downloading a unit recipe. If the directive is issued through the Operation and Monitoring Window after downloading a unit recipe.5. • If an error occurs when the ASSIGN directive is issued after downloading a recipe. carries out dynamic assignment of units. • No dynamic assignment of units is allowed for the starting unit recipe (unit recipe #1).” TI 33M05L10-40E Oct. resulting in the cancellation of downloaded unit recipes. The ASSIGN directive can be used to assign unit recipes within the same batch by SEBOL (urassign) as well as the Operation and Monitoring Window. To implement the dynamic assignment of units through the Operation and Monitoring Window (or Product Control View). 2010-00 . 29. there are some restrictions. A unit name can be designated using: • Direct specification • Selection from unit menu • Selection from a list of usable unit names Select a method as specified in the Master Recipe Builder. a unit will be cancelled. and downloads the new units when the downloading modes of a recipe and a unit recipe are “AUT. the system cancels original units. However. Process Management Function 5-12 The ASSIGN directive is valid only for unit recipes before starting.

The user copies process data to the common block data area of the FCS arbitrarily using the SEBOL block or other blocks. Table Data Collection Timing When GATHER is specified on the Product Control View When the unit or control recipe has been Uploaded Data Common block data Common block data Collection Arbitrarily Automatically Control start and end time The control start time (STRTIME) and control end time (ENDTIME) which have been defined for system-specific common block recipes and unit recipes are automatically defined for batch execution. TI 33M05L10-40E Oct. setpoints. Batch Results Data Collection The data recorded during batch execution is collected on a batch basis. Process Management Function 5-13 5. Processes. such as the HIS. When data has been collected arbitrarily a number of times. quality. Manner of data collection Data is collected at a time after recipe execution has been completed. calculation.5. manual input. The copied data is to be collected on a batch (control recipe) basis. and other data recorded during batch execution are collected and saved in the common block data area.4 This section covers how the data recorded during batch execution are collected and saved. Collected data “Collecting” means the FCS-resided common block data is collected at a station that manages processes. 2010-00 . or when data has been uploaded after it was collected arbitrarily. the data will be renewed by the latest data. 29. Timing of data collection Data is collected automatically (at the time of uploading) or arbitrarily.

0 Upper 100.3 42.7 14.8 25. PV FIC002.3 82.0 100. Process Management Function 5-14 Batch Related Trend Data Filing By linking the process management of the batch management package and the trend recording functions of the HIS. and whether to create one. 2010-00 . PV TIC200. process management selectively extracts data related to the batch ID of a given batch for the time period corresponding to the execution time (runtime) of that batch.0 100. Two kinds of files can be created. 29.PV 62.3 FIC001. and saves it to CSV files.0 0. These output files are referred to as batch-related trend files.ai TI 33M05L10-40E Oct.0 0. the other or both of them can be specified using the corresponding Builder depending on the purpose. trend data related to each batch and acquired by the HIS can be output to files upon the end of the batch or upon invocation of the batch result gathering (GATHER) command.0 Trend Data Acquisition Trend View F050401.1 53.1 Unit M3/h M3/h M DEGC DEGC Lower 0.3 Trend Data File Gathering 13:34 05/10/2010 00:12:00 13:36 100% 13:38 13:40 05/10/2010 13:42 13:44 22.0 100.3 Tag Name □ □ □ □ □ □ □ □ ● ● ● ● ● ● ● ● 1 2 3 4 5 6 7 8 FIC001.3 2.3 3.0 0. CSV format files Batch-related trend files in CSV format are useful for application to other systems. Process Management Function Batch Related Trend Data Filing (CSV file) Batch Related Trend Data Filing (Binary file) Data Filing Standard Operation and Monitoring Function TG1001 Block:10 Group:01 1 2 102. PV Tag Comment Inlet flow Outlet flow Level Temp A Temp B Value 72.0 100. Binary format files Batch-related trend files in binary format are used to display the trend graphs of batch-related data using a trend window after the execution of each batch.0 0. PV TIC100. From the binary trend data that the trend recording functions of the HIS operation and monitoring functions store in trend data files. PV LIC100.5.

Reference from Application Programs With application programs. 2010-00 . tag attributes. The following data is recorded during batch execution: • Historical messages • Common block data • Historical trend data These data may be printed as batch reports by arbitrary formats at the time of batch process end. The VP Batch allows the user to specify a batch ID as the search conditions. To use this function. For data reference on the Report Package. To print them as batch reports. Process Report The Process Report Function collects data regarding the state of system operation. print it as a report and use it on application programs. the Process Management must have been installed. closing data as well as the above data are collected and detailed batch reports are printed. use the Report Package. Process Management Function 5-15 Message Gathering The VP Batch gathers messages generated during batch execution as part of batch result data. Batch Journal The VP Batch allows the user to access recorded data according to a batch ID. Previous batch journal includes the function. current tag data. the user can access recorded data using a batch ID through OPC communications. 29. the Open Data Interface Package (Exaopc) for OPC must be installed. The gathered messages can be retrieved with a batch ID from a historical message report.5. TI 33M05L10-40E Oct. With the Report Package. Messages are stored in a historical file of the HIS upon receipt of the messages by Message Management Function.

5 This section describes the use of a number of HISs for operation and monitoring applying the process management function.5. 29. To define server and client station names for each recipe group. • Server station: • Client station: Ethernet A station that processes requests of the client station Up to 2 server stations/recipe group A station that uses information of the server station Up to 14 client stations/recipe group HIS 1 Server #1 Control bus FCS HIS 2 Client HIS 3 Server #2 General purpose PC Recipe management (When the Server #1 is a master. These HISs serve as server/client stations.ai Figure Station Configuration TI 33M05L10-40E Oct. 2010-00 .) F050501. Process Management Function 5-16 5. suitable for mission-critical application. the Server #2 serves as a backup and client server. The server station can also be made redundant (master/ backup). Server/Client Function Redundancy Specifying Server and Client Stations The Process Management Function can be used and monitored from a number of HISs. so the user can operate and monitor the Process Management Function from any HIS. use the Process Management Configuration Builder.

• Control recipe copy is performed automatically upon completion of recipe setup and completion of execution. If the formula is modified between recipe setup completion and recipe downloading. When 2 candidate servers are specified. • Control recipe is equalized for each recipe group.ai Figure Control Recipe Transition TI 33M05L10-40E Oct. one station becomes the master server and the other the backup server. • Switching between the master server and backup server is performed manually for each recipe group. the following control recipe copy is performed between server stations. 2010-00 . However.5. HIS Backup Server Control Recipe (RESERVED) HIS Master Server Equalize Control Recipe (LOG) Equalize End Control Recipe (COMPLETE) Master Recipe Recipe Setup Control Recipe (RESERVED) Control Recipe (LOG) End Control Recipe (COMPLETE) FCS Download Control Recipe (READY) Start Control Recipe (ACTIVE) Upload Delete Control Recipe (LOG) End Control Recipe (COMPLETE) F050502E. With a recipe status between READY and LOG (or between recipe downloading and recipe uploading upon completion of execution). 29. during execution of the process management function. Process Management Function 5-17 Control Recipe Copy between Servers Up to 2 HIS that can offer the server function can be specified for each recipe group. the control recipe exists in the FCS and therefore its equalization is not necessary. control recipe is equalized at the timing at which each individual data was written.

recipes are executed according to the schedule information file(*1) through the production planning and scheduling interface. formulas. 29.6 Production Planning and Scheduling Interface The schedule management function is used to plan the schedule of the process management function. The production planning and scheduling interface is used to exchange information between the schedule management function and the process management function. On the process management side. Process Management Function 5-18 5. and equipment requirements. *1: Including the respective batch IDs.ai Figure Positioning of Production Planning and Scheduling Interface TI 33M05L10-40E Oct. but excluding the headers. recipe names. Production Planning and Scheduling Interface Recipe management Schedule management Production information management Production planning and scheduling interface Process management Unit supervision Function block Function described in this chapter F050601E. 2010-00 .5. The production planning and scheduling interface is included in the package of the process management function.

The schedule management function can communicate with either the server station or client station. Schedule Expansion The schedule expansion function makes it possible to expand the established schedule created by schedule management to the process management function.ai Figure System Configuration Including Schedule Management Function TI 33M05L10-40E Oct. production planning and scheduling interface. Process Management Function 5-19 Overview of Production Planning and Scheduling Interface Function The following describes the overview of the production planning and scheduling interface function. System Configuration Including Schedule Management Function The following shows the system configuration based on the combination of the schedule management function. Batch Progress Information The batch journal showing the batch progress information can be collected through the OPC interface. and scheduled execution start time within the established schedule file and then executes the recipe. and process management function. Host computer Schedule management Ethernet HIS Production planning and scheduling interface Process management HIS Production planning and scheduling interface Process management HIS Production planning and scheduling interface Process management Server #1 Server #2 Client Control bus FCS F050602E.5. batch ID. 2010-00 . The process management function performs recipe setup automatically according to the recipe name. specify all the target HIS on the schedule management function side. 29. The process management function registers the server station and client station for each recipe group. To communication with multiple server stations and client stations. The schedule management function also allows scheduling which reflects messages collected from the batch journal.

6. Unit Supervision Function This chapter describes the Unit Supervision Function of the VP Batch software. TI 33M05L10-40E Oct. Unit Supervision Function 6-1 6. 29. 2010-00 .

The unit data saves the tuning data for the entire equipment. There are two types of units: one where procedures reside and the other where they must be downloaded from control recipes.6. and operator guide messages and alarms on the blocks can also be grouped as a unit.1 A number of equipment used to control continuous or batch processes can be controlled as a unit. A unit has control algorithm and unit data to control equipment. The control algorithm is composed of unit procedures (SFC) showing the order of processes. 2010-00 . Function blocks can be placed under a unit.ai Figure Configuration of Unit with Procedures TI 33M05L10-40E Oct. 29. operations (SFC and SEBOL) controlling respective action of each equipment. simplifying operation. Giving a command to a unit activates a group of equipment. sequence table logic. A unit represents a group of equipment. and logic charts. a group of reactors in batch processes can be controlled as a unit. For example. Unit data SET_DATA=10 kg Unit Unit Procedure 1 Operation (SFC block) Phase SEBOL Sequence table Logic chart F060101. Unit Supervision Function 6-2 6. The user does not need to use individual tag names.

Unit Supervision Function 6-3 6. Up to 16 bytes display label can be attached to each user-defined unit data item and displayed on the Operation and Monitoring Window. Data items are either unit-specific or user-defined. data names and data types. 29. 2010-00 .2 Unit data is a group of data indicating the condition of the unit-controlled equipment.6. Unit Data Unit-Specific Data Items There are unit-specific data item names. User-Defined Data Items Up to 256 data items can be user-defined. A default storage named BIDQUEUE[ ] is reserved in the user-defined data area to save the Process Management Function-defined batch ID to start recipes. TI 33M05L10-40E Oct.

a generic operation name or operation tag name is described in the action box of each step (In the following figure. To control the order of carrying out operations. 2010-00 . It is described in SFC.” and others).ai Unit Procedure 4 Add 5 Agitate 8 Discharge 2 Figure Example of Unit Procedure TI 33M05L10-40E Oct. Unit Supervision Function 6-4 6.3 The unit procedure executes unit processes (procedures). 29. 1 2 3 6 7 9 10 Initialize Charge Heat Analyze Discharge Wash End F060301.6.” “heat. “charge.

10 F060302. 2010-00 . Satisfying a transition condition moves to next step. Linking steps and transitions. which is called the initial step. 5 6 7 F060303. and in the inactive state the step either has been executed or has not yet been executed.ai Links Links between steps. 3 4 5 <Regular linking> 5 6 7 <Looped linking> 10 11 12 <Selected linking> F060304. between steps and transition are expressed using horizontal and vertical lines. Unit Supervision Function 6-5 6. A display label.ai 13 TI 33M05L10-40E Oct. moving to the next step. Basic Elements Steps Steps are expressed by putting numbers (step numbers) in squares. A logical expression called “transition condition” can be described for transition. and is examined upon completion of the operation in the action box. The initial step is expressed differently.6.1 SFC Language The SFC language has the following three basic elements: • Steps: • Links: Description of actions. They show the order (path) of carrying out steps. if it is defined. • Transition: Description of transition conditions. is shown in double squares. In the action box. is shown in the box using the SFC function display. 29. Upon completion of the operation. When a step is active. the user defines an action in rectangles.3. The transition condition becomes active at previous step. but the action of the initial step is the same as those of successive steps. A step has active and inactive states. a generic operation name or operation tag name is entered. the operation described in the rectangular action box starts. Transition Transition from one step to another is indicated using lines. In the active state the step is being executed.ai For each step. the step is inactive. The first step.

The activated step executes the operation described in the action box. Selective Sequence The selective sequence is used when different step must be executed according to transition conditions. three transition conditions connected to the step are examined from the left. 2010-00 . Up to eight selective sequences can be described.ai 7 8 In the example shown above. 5. Complex Sequences There are two types of complex sequences — selective and parallel sequences. When the unit procedure starts. If more than one transition condition have been proved true. the initial step is activated for execution. The step is inactivated when the operation is completed.6. The step of which the condition has been proved true will be activated. The next step linked to the current step is activated. a transition condition will be examined. If there is a transition. as Step 5 becomes inactive. TI 33M05L10-40E Oct. When the transition condition is proved true. the step following the transition will be activated for execution. 4. 5 6 9 10 <Example of Selective Sequence> F060305. 2. If none of transition conditions is proved true. Unit Supervision Function 6-6 SFC Execution The unit procedure is executed as follows: 1. their conditions will be examined repeatedly until one is proved true. priority is given to the step on the left. 3. 29.

Table SFC Elements Name Initial step Steps Step Wait step Transition Transition Branch Join Parallel branch Parallel join Loop out Links Loop in Jump up Jump down Jump in Link T060301. Unit Supervision Function 6-7 Parallel Sequence The parallel sequence is used when a number of sequences must be executed at the same time. Drawing double horizontal lines at the end of parallel sequences returns to its original path.ai Class Symbol Jnn Jnn Jnn TI 33M05L10-40E Oct. Steps connected to the line become active and executed at the same time. Up to 32 steps can be executed at the same time if parallel sequences are included within parallel sequences (they can be nested up to three levels in one sequence). 2010-00 . A parallel sequence is indicated using double horizontal lines.6.ai Up to eight steps can be executed at the same time in a parallel sequence. 29. 5 6 9 10 7 8 <Example of Parallel Sequence> F060306.

Unit Supervision Function 6-8 Transition Condition As a transition condition. either one of =.6. the common block data of the recipe being executed on relevant unit can be described as the left operand. or >= can be entered. one item can be described. TI 33M05L10-40E Oct. <=. or a constant. such as unit data or function block data of the present station. such as unit data. 2010-00 . 29. function block data of the present station. For the operator. <. >. one line can be described using a simple logical expression in the following format: “Left operand” “Operator” “Right operand” One item can be described as the left operand. For the right operand. With the Process Management Function. <>.

When the user tries to execute a unit procedure by a unit. the common block data of the recipe can be accessed from the operation. You may think that we call the unit-started SFC block an operation. but not from the SFC block. When the user tries to execute multiple steps at the same time in the unit procedure. • With the Process Management Function. while it can be accessed by data item format “unit name. Operation (OPSFC) Unit Unit procedure (SFC) Initialize Charge Initial step Charge 1 Agitation Charge 2 Heat Operation (OPSBL) SEBOL or Logic chart Terminate or Sequence table Y N SEBOL Operation F060401. The user cannot start the operation by themselves. • The operation can request the downloading of the unit procedure for another unit in the same recipe. TI 33M05L10-40E Oct. Unit Supervision Function 6-9 6.ai Figure Positioning of Operation The operation has functions that are equivalent to those of the SFC block. It is an independent process in a series of production processes assigned to the device. Other differences are described below: • Present unit data can be accessed by data item “%%. The major difference between them is that the operation can use additional functions such as access to activated units and formulas (recipe data). • The operation can control the start and termination of the unit procedure for another unit in the same recipe. operations are executed according to the progress of the unit procedure processing. 2010-00 .6. • The operation can be started by a unit only. Each operation corresponds to one step of a unit procedure.4 An operation is a series of control steps executed in the unit-controlled device. 29. multiple operations are executed at appropriate timing. • The operation can reserve (or dynamically assign) the unit to be executed by the unit procedure for another unit in the same recipe.” from the operation.” from the SFC block.

Table Operation SFC vs. Operation Mode and Status The operation is a function block with a tag name. The operation is normally executed under the control of a unit. The user cannot specify userspecific data items. Operation SFC The differences between operation SFC and unit procedure SFC are shown below. and has its block mode and block status like other function blocks. 29. Description using SEBOL. SEBOL expression. Description of name of operation to be started. Unit Procedure SFC Parallel sequence Not available. TI 33M05L10-40E Oct. 2010-00 . which cannot be started by operators.6. etc. Unit Procedure SFC Item Transition condition Action Operation SFC Available. Unit Supervision Function 6-10 Operation Data Items Only system-specific data items are available for operations. Unit-specific logical expression. The block mode indicates the state of operation control and the block status indicates the state of operation.

All unit functions are automatically controlled. Unit Mode and Status Unit Modes Like function blocks. The unit can be manually operated. Symbol TI 33M05L10-40E Oct. There are operation statuses indicating the state of operation and internal statuses indicating internal detailed condition. 2010-00 . The unit procedure is being executed. or emergency stop due to failure. The unit procedure has been abnormally aborted. The combination of statuses and modes expresses the overall operation condition of a unit. 29. Inter-step transition can be manually operated but the step itself is automatically controlled. The unit procedure is being suspended at the start of a step. The modes can be changed by a mode change directive from the Operation and Monitoring Function. Table O/S MAN SEMI AUT Unit Modes Name Out-of-service mode Manual mode Semi-automatic mode Automatic mode Description All unit functions are stopped. however. Operation Statuses The operation statuses of the unit are described below. Symbol Unit Statuses The unit status indicates the operation condition of a unit (a unit procedure). Table END ABORTED RUNNING SUSPEND PAUSED Operation Statuses Name Completion Abnormal termination Execution Procedure suspension Sequence suspension Description The unit procedure has been executed. The mode change directive can also be sent from the Operation and Monitoring Function.5 The user can send a status change directive to a unit.6. The operation sequence is being suspended at the start of a phase. such as operation from the Operation and Monitoring Function. The unit also has modes to order the actions of unit procedures and operations. Unit Supervision Function 6-11 6. The unit procedure cannot be activated. units have modes indicating the control state of a unit.

The unit procedure has been aborted due to a system-detected error. An interruption process is being executed. The transition condition is being examined. Unit Supervision Function 6-12 Internal Statuses The internal statuses show detailed internal conditions of operation statuses. Table Internal Statuses Status Code CNCT NOCNCT INIT INTR USER SYSTEM INTR INTRCKTR INTR Description The unit procedure is standing by for execution. An interruption process is being executed. The unit procedure has been aborted by the user. There is not unit procedure to execute.6. Symbol END ABORTED RUNNING SUSPEND PAUSED TI 33M05L10-40E Oct. An interruption process is being executed. 29. An interruption process is being executed. The initialization operation sequence is being eecuted. 2010-00 .

TI 33M05L10-40E Oct.6. though unit procedures do not run. It runs regardless of the unit status. It initializes processes. Unit Supervision Function 6-13 6. Monitoring Operation The monitoring operation is used for monitoring a unit.6 The unit executes initialization and monitoring operations in addition to unit procedures and operations. 2010-00 . It is used when equipment must be monitored all the time. Initialization and Monitoring Operation Initialization Operation The initialization operation starts one time at system startup before a unit starts. 29.

and units. unit procedures and operations which have the same function can be shared. a generic name can be used. tag name and unit name can be registered in the unit. Entering a generic name of operation in the SFC action box and starting as unit SFC starts corresponding operation. TI 33M05L10-40E Oct. can be shared among units. instead of a tag name. Unit Supervision Function 6-14 6. Sharing Unit Procedure The same unit procedure (SFC) can be shared among multiple units. the function blocks and units accessed in a program can be described by their generic names. Sharing Unit Definition Unit definitions.7 To use FCS memory effectively and improve engineering productivity. The relationship among generic name. the relationship between a generic name and a tag name can be defined. a program can be described without a tag name. such as unit data definitions. Using Generic Name and Sharing Resources Using Generic Name for Units A generic name is a variable name used in a program within operation.6. 2010-00 . Sharing Operation To share the same operation. 29. For units. With a generic name.

2010-00 . it shifts to a new unit mode and unit status according to the state transition matrix and. A unit changes unit mode/status according to the status transition matrix. transmits operation commands to control the control status and operation status of the unit instrument and operation. It is executed by unit mode/status change command. Status Transition Matrix Status Transition A unit mode shows the control status of a unit and a unit status shows its operation status. When the unit instrument receives the change command. (*1) *1: Planned to be customized in future. Status Transition at the AUT Mode END RUNNING PSTART ABORT PAUSE SUSPEND RESTART RESTART END END PAUSED SUSPEND SUSPEND ABORT ABORT RESET ABORTED F060801. “Status transition” means the change of the unit mode and unit status.8 The status transition matrix determines actions for unit mode/status change commands. The state transition matrix can be customized by the user. Unit Supervision Function 6-15 6.ai Figure Status Transition at the AUT Mode TI 33M05L10-40E Oct. 29. at the same time.6.

Unit Supervision Function 6-16 Status Transition at the SEMI Mode END RUNNING PSTART ABORT PAUSE END At start of step execution or SUSPEND RESTART END RESTART PAUSED SUSPEND SUSPEND ABORT ABORT RESET ABORTED F060802. The definition of link between Common Block & Operation TI 33M05L10-40E Oct. 2010-00 . it is also possible to use some common blocks only for some units or some operations.9 While the common blocks are usually used commonly among all recipes.6. 29. by closely link between each unit/phase and formula data contributes to much more efficient configuration and to improvement plant operation and monitoring. as users like. This link between common blocks and units/operation is configured.ai Figure Status Transition at the SEMI Mode 6. Thus.

The operation and monitoring windows are supplied as the human-machine interface of VP Batch. Figure Windows Opened from the Product Overview (Windows for Information Display) TI 33M05L10-40E Oct. Product Overview Recipe List Operator Guide View (*1) Historical Message Report Window (*2) Recipe Procedure View Formula Dialog Box Trend Selection Dialog Box Trend View Unit Recipe List Operator Guide View (*1) Historical Message Report Window (*2) Unit Recipe Procedure View (or Unit-SFC View) Unit Formula Dialog Box Trend Selection Dialog Box Trend View Operation List Operator Guide View (*1) Historical Message Report Window (*2) Operation-SFC View Operation Formula Dialog Box Faceplate Phase List Operator Guide View (*1) Historical Message Report Window (*2) Phase-SFC View (or SEBOL/Logic Chart/Sequence Table View) Recipe Header Dialog Box Faceplate Operator Memo Dialog Box Product Control View F070001. VP Batch Operation and Monitoring Windows 7-1 7.7. VP Batch Operation and Monitoring Windows This chapter describes operation and monitoring windows of the VP Batch software. The VP Batch has various standard windows. 2010-00 . The CAMS for HIS Historical Viewer is displayed if Consolidated Alarm Management Software (CAMS for HIS) is enabled. The user does not need to create graphic windows for batch control.ai *1: *2: The CAMS for HIS Message Monitor is displayed if Consolidated Alarm Management Software (CAMS for HIS) is enabled and operator guide messages are integrated. They are classified into a window switching from Product overview and a window switching from Product Control view. 29. permitting consistent operation and reducing engineering steps. Windows that can be opened from the Product Overview are shown below.

Figure Windows Opened from the Product Control View TI 33M05L10-40E Oct. 2010-00 . The CAMS for HIS Message Monitor is displayed if Consolidated Alarm Management Software (CAMS for HIS) is enabled.7. The CAMS for HIS Historical Viewer is displayed if Consolidated Alarm Management Software (CAMS for HIS) is enabled. VP Batch Operation and Monitoring Windows 7-2 Product Overview Recipe List Recipe List Dialog Box Control Recipe Copy Dialog Box Server Switch Dialog Box Formula Export Dialog Box Train Selection Dialog Box F070002.ai Unit Recipe List Recipe Setup Dialog Box Dynamic Unit Assign Dialog Box Figure Windows Opened from the Product Overview (Windows for Operations) Windows that can be opened from the Product Control View are shown below. 29. Product Control View Operator Guide View (*1) Process Alarm View (*2) Historical Message Report Window (*3) Unit Recipe Procedure View Unit Formula Dialog Box Recipe Header Dialog Box Operator Memo Dialog Box Equipment Requirement Dialog Box Product Overview F070003.ai Operation-SFC View Operation Formula Dialog Box Phase-SFC View (or SEBOL/Logic Chart/Sequence Table View) Dynamic Unit Assign Dialog Box *1: *2: *3: The CAMS for HIS Message Monitor is displayed if Consolidated Alarm Management Software (CAMS for HIS) is enabled and operator guide messages are integrated.

The window is customized by the graphic builder. • Operator Memo dialog box Enters memo of the specified control recipe for operators. • Operation Formula dialog box Displays and allows the user to change the formula applied to a selected operation. • Formula Export dialog box Used to export formula data for a selected control recipe to a comma-separated value (CSV) text file. 2010-00 . • Train Selection dialog box Used to change the trains within the recipe group. TI 33M05L10-40E Oct. • Recipe Procedure View Displays the recipe procedure (SFC) and unit recipe procedure (SFC) of the specified control recipe. • Control Recipe Copy dialog box Used to make a copy of a selected control recipe to create a new control recipe. • Recipe Setup dialog box The master recipe selected from the Recipe Overview Dialogue is converted into a control recipe by adding a batch ID.7. • Formula dialog box Defines and displays the formula of the specified control recipe. • Recipe List dialog box Displays a list of master recipes for each recipe group/train. • Product Control View Displays the status of each batch. VP Batch Operation and Monitoring Windows 7-3 Recipe-related Views and Dialog Boxes • Product Overview Displays batch status for each recipe group/train. • Server Switch dialog box Sends a command to switch server stations according to recipe group. assigning a unit and setting actual volumes. • Equipment Requirement dialog box Defines and displays the equipment requirement of the specified control recipe. • Unit Formula dialog box Displays and allows the user to change the formula commonly applied to a selected unit. • Unit Recipe Procedure View Displays the unit recipe procedures of a selected control recipe. 29. • Recipe Header dialog box Displays the recipe header of the specified control recipe. The operation of all batches or individual unit recipes can be carried out.

Set up a recipe (convert from a master recipe to a control recipe) on the Recipe Setup dialog box. • Specify a batch ID. 4. 2. 29. TI 33M05L10-40E Oct. • the batch operation is monitored on the Product Overview or Product Control View and • the unit operation is monitored on the Graphic View. Send the Load and Start commands to the FCS to download and start the recipe on the same window (When the automatic starting mode is specified.7. Select a recipe to be formulated on the Recipe Overview. 2010-00 . 3. • Assign a unit to be utilized. the system automatically executes the downloading and starting of the recipe upon completion of the recipe setup.) After the operation has started. VP Batch Operation and Monitoring Windows 7-4 Follow the procedure below to use the operation and monitoring windows: 1.

The management of recipe engineer (Recipe Management Function) includes “Access Control Function” and “Audit Trail Management Function” that meet the regulations in FDA : 21 CFR Part 11. 2010-00 . see following TI: Achieving 21 CFR Part 11 Compliance Using CENTUM VP Authored by Stelex (TI 33M01A62-40E) TI 33M05L10-40E Oct. FDA : 21 CFR Part 11 Compliant Supporting FDA : 21 CFR Part 11 compliant functions. 29. FDA : 21 CFR Part 11 Compliant 8-1 8. CENTUM VP achieves comprehensive FDA : 21 CFR Part 11 compliant by supporting the management of an operator (Operation and Monitoring Function) and a system engineer (System View/Builder) besides a recipe engineer (Recipe Management Function). SEE ALSO For details of FDA : 21 CFR Part 11.8.

status change notification and operator guide messages. An example is process equipment such as tanks and heaters. It includes messages from currently operating units and function blocks under the control of units. data entry.) batch journal Batch data recorded during batch operation. An area is a component of hierarchical plant information and contains process cells. process units. The information defines all the details required for the production. and control modules. geographically. (See recipe. mode change.9. equipment modules.) equipment module A unit of functions to control specific and limited minor process activities. control module A unit that combines a regulating device and a state-transition control device for a combined operation. Glossary 9-1 9. 29.) common block data Data that can be shared among unit recipes. control recipe A recipe that contains information for manufacturing one specific batch of a product. An element in a batch process plant physically. The term. equipment module. 2010-00 . The term is used to identify resources and recipes used in processing each kind of products. (See batch. TI 33M05L10-40E Oct. More than one unit recipes comprise one control recipe. It includes operator input. “Area” in this sense is different from that used in “controlled area. unit. or logically divided.) batch A unit of finished or half-finished products of the same kind that is processed using more than one manufacturing unit. is used as a means of implementing recipe data.” (See control module. batch message Batch process messages from the FCS and batch history messages from the Operation and Monitoring Function during batch operation. batch process A process of manufacturing a limited quantity of products by using more than one manufacturing unit in order of the defined procedure. process cell. (See batch. area Glossary This chapter gives definitions of terms used in this manual. such as measuring and material additions. unit recipe. operation command. common block. An example is a single-loop controller.

9. A formula include the product grade. The term is also applied to the order of executing a unit recipe. 29. transportation. (See batch. master recipe A recipe that is prepared in accordance with specific manufacturing equipment. unit.) TI 33M05L10-40E Oct. process.) path A group of process units that are configured in series or parallel and used. controls. batch. (See unit recipe. (See operation. formula A set of recipe data that separates procedure-defined products from other products. (See procedure. recipe. A master recipe contains the information for manufacturing a batch of a product. process variables.) process A series of chemical.01 Instrument Society of America (ISA)’s SP (Standards&Practices)88 Committee has been working on batch process standardization and modelling. It released Batch Control Part 1: models and terminology as ISA-88. A cell is a component of hierarchical plant information and logically controls an entire set of process equipment in an area. physical. (See procedure. (See area.) phase Processing or action that is related to the process in an operation sequence. in a batch production operation. or planned to be used. unit. An example is the distillation process of a refinery.) ISA-88. and monitors.) procedure A series of actions taken to accomplish a specified purpose or that defines the order manufacturing steps and the control method for a batch production operation.) operation (sequence) A sequence of steps in operation of a process unit or a sequence of phases in an independent major process contained in the procedure. process cell A concentrated group of equipment involved in the production of batches. quality specification. (See batch. Glossary 9-2 equipment requirement A requirement for the unit or equipment used in manufacturing products. or biological activities for the conversion. 2010-00 . or storage of material or energy — excluding computers.01 in 1995. material type and quantity.

equipment module. control recipe. general recipe.) SFC (sequential function chart) A graphical language used to describe the sequential control function. and originator and originated data. unit procedure. and so on. sequence tables and logic charts. and parameters. (See SFC. dissolution.) SEBOL (Sequence and Batch Oriented Language) A text language used to describe sequential control and batch control. procedure. 2010-00 . process units. unit. including recipe and product identifications. equipment modules.) train A group of process units that are planned to be used in manufacturing a batch of products finished or half-finished. methods. master recipe. Each recipe is composed of a recipe header. equipment requirements. unit. Recipes are created in four levels.) SFC block A function block that executes the SFC-described control function. recipe header. and a procedure. (See SEBOL. unit. geographically. or logically divided. crystallization. It is also a group of control modules or equipment modules. and so on and assigning process units that are to be executed by the recipe. site recipe. (See SFC. control modules. version of the recipe. A site is a component of hierarchical plant information and contains areas. master recipe. and control recipe. (See recipe.) TI 33M05L10-40E Oct. control recipe. master recipe. process cells. (See batch. process cell. control module. namely. (See area.) recipe header A set of information given to each recipe. batch identification. (See batch. a formula. equipment module. 29.9.) recipe setup The procedure for generating a control recipe from a master recipe by setting parameters. (See master recipe. (See batch.) recipe group A group of master recipes classified by plant and product line. Glossary 9-3 recipe A recipe is a set of information that defines control requirements for the production of a batch specifying steps. which controls SEBOL.) site An element in a batch production enterprise physically. It actually executes a unit procedure that describes the order of manufacturing steps and the control method for reaction. control module. (See batch. equipment requirement. formula. unit recipe.) unit (unit instrument) An instrument having a function to execute part of a specific batch and manage the data and procedure for the purpose.

2010-00 . (See unit. phase. (See operation. 29. recipe. Glossary 9-4 unit procedure A sequence of operation steps or phases completed within one unit.) TI 33M05L10-40E Oct.9. A procedure in a unit recipe is called unit recipe procedure.) unit recipe A recipe that defines a unit for operation. procedure.

Ind-1

VP Batch Batch Management Package
TI 33M05L10-40E 1st Edition

INDEX
A
Access Control Function ....................................... 4-8 Adaptability............................................................ 1-3 area ...................................................................... 9-1

D
Data Collection ....................................................5-13 Downloading a Recipe .......................................... 3-8 Downloading Modes ...........................................5-10 Dynamic Unit Assignment ................................... 5-11

B
Basic Elements ..................................................... 6-5 batch ..................................................................... 9-1 Batch-Operation Monitoring.................................. 3-6 Batch Control ........................................................ 5-7 Batch execution control......................................... 5-2 Batch ID ................................................................ 5-4 Batch ID Descriptors ............................................. 5-4 Batch ID specification ........................................... 5-3 Batch Journal ...............................................5-15, 9-1 batch message...................................................... 9-1 Batch Modes .......................................................5-10 Batch Process ....................................................... 1-1 Batch Processes ............................................1-1, 9-1 Batch Progress Information ................................5-19 Batch Related Trend Data Filing .........................5-14 Batch Results ......................................................5-13 Binary format files ...............................................5-14

E
Easy Operation ..................................................... 1-3 equipment module ................................................ 9-1 Equipment Requirements .......................3-4, 4-7, 9-2 Execution data acquisition .................................... 5-2 Exporting Formulas ............................................... 5-6

F
FDA : 21 CFR Part 11 Compliant .......................... 8-1 Flow of Control Recipe Copying Function ............ 5-5 Formula ...................................................3-4, 4-7, 9-2 Formula (recipe data) modification ....................... 5-3

G
Glossary ................................................................ 9-1

H
Header ...........................................................3-3, 4-4 Higher Engineering Efficiency .............................. 1-4

C
Collected data .....................................................5-13 common block data ............................................... 9-1 Complex Sequences............................................. 6-6 Compliance with International Standard (ISA-88.01 and 21 CFR Part 11) .................. 1-3 control module ...................................................... 9-1 Control Recipe ...............................................3-2, 9-1 Control Recipe Copy between Servers ..............5-17 Control recipe create............................................. 5-2 Control Recipe Setup ............................................ 5-3 Control Recipe Status ........................................... 5-8 Control start and end time ...................................5-13 CSV format files ..................................................5-14

I
Initialization and Monitoring Operation ...............6-13 Initialization Operation ........................................6-13 Internal Statuses .................................................6-12 ISA-88 ................................................................... 2-1 ISA-88.01 .............................................................. 9-2 ISA-88.01 Physical Model..................................... 2-1 ISA-88 compliant VP Batch................................... 2-1

L
Links ...................................................................... 6-5

TI 33M05L10-40E

Oct. 29, 2010-00

Ind-2
M
Manner of data collection ....................................5-13 Manual Entry ......................................................... 5-4 Master Recipe ................................................3-2, 9-2 Master recipe selection ......................................... 5-3 Message Gathering ............................................5-15 Message generation ............................................. 5-2 Monitoring Operation ..........................................6-13

S
Schedule Expansion ...........................................5-19 SEBOL .................................................................. 9-3 Selective Sequence .............................................. 6-6 Server/Client Function Redundancy...................5-16 Setting of Reference Batch ID .............................. 5-3 Setup Procedure ................................................... 5-3 SFC ...................................................................... 9-3 SFC block.............................................................. 9-3 SFC Execution ...................................................... 6-6 SFC Language ...................................................... 6-5 Sharing Operation ...............................................6-14 Sharing Unit Definition ........................................6-14 Sharing Unit Procedure ......................................6-14 site ...................................................................... 9-3 Specifying Server and Client Stations ................5-16 Starting Modes ....................................................5-10 Status Transition .................................................6-15 Status Transition at the AUT Mode .....................6-15 Status Transition at the SEMI Mode ...................6-16 Status Transition Matrix ......................................6-15 Steps ..................................................................... 6-5 System Configuration Including Schedule Management Function ................................5-19

O
Open Environment ................................................ 1-3 Operation .......................................................6-9, 9-2 Operation Data Items ..........................................6-10 Operation Mode and Status ................................6-10 Operation SFC ....................................................6-10 Operation Statuses ............................................. 6-11 Overview ............................................................... 5-2 Overview of Production Planning and Scheduling Interface Function ........................................5-19 Overview of Recipe Management ........................ 4-2 Overview of VP Batch Software ............................ 3-1

P
Parallel Sequence ................................................. 6-7 path ...................................................................... 9-2 phase .................................................................... 9-2 Procedure ...............................................3-3, 4-5, 9-2 process.................................................................. 9-2 process cell ........................................................... 9-2 Process Management Function ............................ 5-1 Process Report ...................................................5-15 Production Planning and Scheduling Interface .......................................................5-18

T
The definition of link between Common Block & Operation .....................................................6-16 Timing of data collection .....................................5-13 train ...................................................................... 9-3 Transition............................................................... 6-5 Transition Condition .............................................. 6-8

U
unit ...............................................................6-2, 9-3 Unit-Specific Data Items ....................................... 6-3 Unit Assignment .............................................5-3, 5-4 Unit Data ............................................................... 6-3 Unit Modes .......................................................... 6-11 Unit Mode and Status ......................................... 6-11 Unit Procedure ...............................................6-4, 9-4 unit recipe .............................................................. 9-4 Unit Recipe Status ................................................ 5-9 Unit Statuses ....................................................... 6-11 Unit Structure ........................................................ 3-7 Unit Supervision .................................................... 3-7 Unit Supervision Function ..................................... 6-1 User-Defined Data Items ...................................... 6-3

R
Recipe ................................................................... 3-2 recipe .................................................................... 9-3 Recipe Engineer Authentication and Authority Check ............................................. 4-8 recipe group .......................................................... 9-3 recipe header ........................................................ 9-3 Recipe Management Function.............................. 4-1 recipe setup........................................................... 9-3 Recipe Setup and Downloading ........................... 3-5 Recipe Statuses .................................................... 5-7 Recipe Structure ................................................... 3-3 Reference from Application Programs ................5-15 Requirements for DCS Manufacturers ................. 1-3 Reuse of Control Recipe ....................................... 5-5

TI 33M05L10-40E

Oct. 29, 2010-00

Ind-3
Using Generic Name and Sharing Resources ...6-14 Using Generic Name for Units ............................6-14

V
VP Batch Operation and Monitoring Windows ..... 7-1

TI 33M05L10-40E

Oct. 29, 2010-00

Blank Page .

i Revision Information  Title  Manual No. 2010-00 . 29. 2010/1st Edition Newly published TI 33M05L10-40E Oct. : VP Batch Batch Management Package : TI 33M05L10-40E Oct.

Musashino-shi.Written by Published by Product Marketing Dept. . Tokyo 180-8750. JAPAN Subject to change without notice. Industrial Automation Systems Business Division Yokogawa Electric Corporation Yokogawa Electric Corporation 2-9-32 Nakacho.

Sign up to vote on this title
UsefulNot useful