JP2016038914A - Recipe setting system, recipe setting method and computer program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To set a recipe.SOLUTION: A recipe setting system comprises a recipe procedure tool which is configured to display plural operation stencils related to a level of a unit procedure for selection. The recipe procedure tool displays plural tags, selects one operation stencil, and positions the operation stencil as a unit procedure operation on a drawing area. One tag is selected and then transferred to the drawing area. A tag link module determines whether or not the selected tag is in a predetermined area of the unit procedure operation, classifies the selected tag and allocates at least one predetermined property of the selected tag. A common block link module determines whether or not, the positioned operation stencil has a new tag or different tag, and allocates a formula of a common block database to the positioned operation stencil.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a recipe management system, a recipe management method, and a computer program for executing the recipe management method used in an industrial plant.

  Recipe management has a function for generating and editing a master recipe. The function classifies recipes into a group for generating a master recipe, a group for editing, a group for saving, and a group for reading in relation to process management. The process management has a function for creating a control recipe based on a predetermined master recipe.

  Recipes define units, procedures, method groups to be used and parameter values to be set to produce a particular product. The International Society for Instrumentation and Control (ISA) has established S88 to provide a consistent set of standards and terminology for batch control. According to S88.01, recipe types are classified into four hierarchical levels, for example 1) general recipes, 2) site recipes, 3) master recipes, and 4) control recipes, which are the activities and needs to be performed each time Depends on resources. In the present invention, master recipe management is executed.

Recipe Each master recipe 1 includes the four parts described below and shown in FIG.
(1) Header: Contains basic information about recipe management such as recipe name, comment, version, and author.
(2) Procedure: Graphically defines the procedure for producing a product in the form of SFC (Sequential function chart).
(3) Formula: Parameter values such as control set values for producing products.
(4) Equipment requirements: Define the equipment requirements for producing products, such as hardware components to be used.

Each procedure in the procedure type recipe is an ordered set of unit procedures, and each unit procedure is an ordered set of operations or steps.
(a) The recipe procedure defines the execution order of unit procedures.
(b) A unit procedure defines a continuous procedure to be completed within a specific unit by specifying the execution order of sequences called operations or steps in the form of SFC. A particular unit is a hardware component such as a distillation column or reactor. A unit procedure has a set of functions for organizing process equipment modules and control modules for a particular unit.

Multiple formulas or multiple formula items are used to define common block procedures and unit procedures. In implementations that reuse formulas for other operations, the formulas are stored in the common block repository as common blocks and common block items.

  The common block builder is an editor used to set and edit common blocks and common block items in the common block repository. The common block includes data extracted from a plurality of data sources or systems that manage and control field devices for equipment units, ie, equipment units within an industrial plant.

  FIG. 2A shows an example of the common block builder 100. The common block builder 100 includes a detailed setting tab 110 for defining properties as common block items 112 for each common block 114. General operation tab 120 is an editor for defining common block 114 for general operation 122. The operations tab 130 is another editor for defining the common block 114 for operations 132 such as field devices shown as tag names 134. Unit tab 140 is yet another editor for defining common block 114 with respect to unit 142, such as a facility unit shown as tag name 144. The function block builder 150 is an editor for defining the general operation 122 for each field device 142.

  FIG. 2B shows an example of the formula editor 200 when common blocks and common block items are applied from the common block repository to the unit recipe 210. In the formula editor, property logic is applied, and the unit recipe 210 is set using the common block and the common block item of the common block repository.

  In the existing recipe management system of FIG. 2B, a recipe procedure builder tool and a recipe builder tool are included to set up procedures and unit procedures.

  The unit procedure is created by the recipe procedure builder tool using the workflow shown in FIG. First, in step S10, the user defines a new unit procedure by searching using a search key for a stencil suitable for unit procedure operation. The appropriate stencil is applied to the drawing canvas. The stencil is linked to the recipe database to retrieve a list of tag names for the operation or step. The tag name list is categorized according to source type, eg, Generic or Operation. In step S20, the user double-clicks the stencil to activate the classification list in drop-down format, select a classification, and then the tag name is listed for the selected classification source. In step S30, the user needs to identify the correct source type of the desired tag name before selecting a classification.

  In step S40, the user then uses the recipe builder tool formula editor to retrieve the common block and common block items for the unit procedure operation based on the selected tag name. In step S50, in the formula editor, the user activates a function, for example, a “get command block data” function, and retrieves a common block item. The retrieved common block item is stored in the recipe database before being mapped to a unit procedure operation.

  In step S60, the user returns to the recipe procedure builder tool and creates the next unit procedure operation when the function is complete. It is inefficient for the user to switch between two tools, Recipe Builder and Recipe Procedure Builder, to create each unit procedure. In step S505, the series of steps described above continues to create the next unit procedure.

  U.S. Pat. Nos. 7,369,913 and 6,834,370 do not explicitly disclose how to set formula data. In US Pat. Nos. 5,499,188 and 7065714, recipe formulas are tightly tied to products or operations and lack flexibility in plant factory settings.

  There is a need to provide improved systems and methods for setting unit procedures.

  A recipe setting system configured to communicate with the common block database includes, but is not limited to, a recipe procedure tool configured to display a plurality of operation stencils for selection of unit procedures for selection. The recipe procedure tool displays a plurality of tags, selects one operation stencil, and receives input to position the selected operation stencil as a unit procedure operation in the drawing area. The recipe procedure tool receives input to select one tag and move to the drawing area. The tag link module communicates with the recipe procedure tool to determine whether the selected tag is within a predetermined area of the unit procedure operation, and the selected tag is determined to be within the predetermined area of the unit procedure operation. And is configured to assign at least one predetermined property of the selected tag and a classification of the selected tag. The common block link module communicates with the recipe procedure tool to determine whether the positioned operations stencil has a new tag or a different tag, and is determined that the positioned operations stencil has a new tag or a different tag. Configured to assign a formula from the common block database to the positioned operation stencil.

FIG. 1 shows the four parts of the recipe. FIG. 2A shows a common block application. FIG. 2B shows a related art recipe management system. FIG. 3 is a related art workflow. FIG. 4 illustrates a recipe management system according to some embodiments of the present invention. FIG. 5 illustrates an example of a level window according to some embodiments of the present invention. FIG. 6 illustrates an example of a stencil window and drawing area according to some embodiments of the present invention. FIG. 7 illustrates an example of a tag window and drawing area according to some embodiments of the present invention. FIG. 8 illustrates an exemplary display on a user interface according to some embodiments of the present invention. FIG. 9 is a workflow according to some embodiments of the invention.

  Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. While certain aspects of the invention will be described in connection with the preferred embodiments, it will be understood that they are not intended to limit the invention to these embodiments. Rather, the invention extends to alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Also, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and features have not been described in detail so as not to unnecessarily obscure aspects of the present invention.

  In some embodiments of the present invention shown in FIG. 4, the recipe setting system 400 can be implemented with a computer system and configured to communicate with the repository 300. The repository 300 includes, but is not limited to, a recipe database 310, a common block database 320, and a factory database 330. Recipe setting system 400 includes, but is not limited to, recipe procedure tool 410.

  The recipe procedure tool 410 can set and edit different levels. In the preferred embodiment, the recipe procedure tool 410 includes a level selection option 420. Preferably, the level selection option 420 is provided in the level window 422 shown in FIG. In level window 422, available levels 424 such as recipes, procedures, and unit procedures are listed in hierarchical order or hierarchical tree format for ease of browsing and selection. Such a display is intuitive for an inexperienced user to select a desired setting level. Embodiments of the present invention relate to setting and editing a unit procedure level that is also a unit procedure related to a recipe procedure, and more particularly to setting and editing a unit procedure operation.

  The recipe procedure tool 410 includes a stencil option 430 in the stencil window 432 shown in FIG. 6 and provides an operation stencil 434 for setting and editing a recipe procedure. In some embodiments, each operation stencil 434 has properties and defines the level (s) with which the stencil is associated. The stencil option 430 is linked to the level selection option 420. In some embodiments, when a unit procedure level is selected, the recipe procedure tool 410 is configured to display an operation stencil 434 associated with the selected level. In another embodiment, all operation stencils 434 are displayed, allowing only the stencil associated with the selected level to be selected by the user. This minimizes the error of incorrectly selecting a stencil during setup.

  Different stencils are used to indicate various functionalities. Thus, different stencils are configured to have various properties required to perform the function. The operation stencil selected for the unit procedure operation has at least three properties: operation name, operation identifier, and operation type.

  The recipe procedure tool 410 provides a tag list 440 of tags 442. The tag 442 is a field device identifier related to a usable field device installed in the industrial plant and a facility identifier related to a usable facility installed in the industrial plant. The recipe procedure tool 410 identifies and retrieves usable field devices and equipment installed in the industrial plant from the factory database 330. In the factory database 330, each tag 442 has a hierarchy property 444 (not shown) that defines the tag 442 at the industrial plant hierarchy. In the preferred embodiment, the recipe procedure tool 410 retrieves the hierarchical properties 444 of the tag 442 and displays the tags 442 in a hierarchical tree in the tag window 446.

  In some embodiments, the hierarchical properties 444 of several tags 442 are stored in the recipe database 330, for example at the procedure level or recipe level. In these embodiments, the recipe procedure tool 410 retrieves the hierarchical properties 444 of the tags 442 from both the recipe database 310 and the factory database 330 and displays the tags 442 in a hierarchical tree in the tag window 446.

  Advantageously, since all tags can be displayed and selected in the tag window 446, the user operates the tag window 446 to find the desired tag and the user can select the source type of the tag 442, eg, general (Generic) or no need to know the operation. Regardless of the user's knowledge of the desired tag hierarchy, the user can search for the desired tag by manipulating the tag window 446.

  Preferably, the recipe procedure tool 410 displays the properties of the selected tag 442 in the tag property area 448. Tag property area 448 is located in a separate window from tag list 440 for ease of viewing. The user can review the properties in the tag property area 448 to determine if the selected tag 442 is the desired tag. This makes it easier to identify the desired tag.

  Recipe setting system 400 is configured to communicate with an input device to receive user input. Examples of input devices include a mouse, keyboard, or touch pad. Based on user input, the recipe procedure tool 410 sets or edits a recipe on a drawing area such as a drawing canvas.

  The input received by the recipe procedure tool 410 selects the level 424 with the level selection option 420, selects the operation stencil 434 with the stencil option 430, and drags the selected operation stencil 434 to the desired location in the drawing area 450. And selecting the desired tag 442 in the tag list 440 and dragging the selected tag 442 to the desired stencil on the drawing area 450.

  When the selected operation stencil 434 is positioned in the drawing area 450, it is a unit procedure operation 436. The recipe procedure tool 410 assigns predetermined properties to the unit procedure operation 436. The predetermined property is an identifier such as an operation identifier.

  The tag link module 460 is provided to the recipe setting system. In a preferred embodiment, tag link module 460 is configured to detect that a desired tag 442 in tag list 440 has been selected. When the selected tag 442 moves on the drawing area 450 by input, the tag link module 460 is configured to detect a unit procedure operation 436 located in the drawing area 450. In some embodiments, the tag link module 460 determines whether the selected tag 442 is within a predetermined area of the unit procedure operation 436. The display size of the unit procedure operation 426 on the drawing area constitutes a predetermined area of the unit procedure operation 426. The selected tag 442 is assigned to the detected unit procedure operation 436 located in the drawing area 450. Preferably, at least one preferred property of the selected tag 442 assigned to the unit procedure operation 436 is the operation name, and the classification assigned to the unit procedure operation from the selected tag 442 is the operation type. These are some examples of properties required to establish a formula for unit procedure operation 436.

  In some preferred embodiments, tag link module 460 includes a distance property that defines a minimum or maximum distance for detecting unit procedure operations 436 located in drawing area 450. Preferably, the tag link module 460 detects that the selected tag 442 is above the unit procedure operation 436. The tag link module 460 includes a confirmation function 462 (not shown) to determine whether the unit procedure operation 436 located in the drawing area 450 is set to register the tag 442.

  Optionally, the tag link module 460 includes an assignment option 464 (not shown). The assignment option 464 allows the user to select whether to assign a tag 442 to the unit procedure operation 436. In an embodiment when there are multiple unit procedure operations 436 in the drawing area 450, this option further allows the user to determine whether to assign a tag 442 to the first detected unit procedure operation 436. Make assignments easier.

  The common block link module 470 is provided to the recipe setting system. In the preferred embodiment, the common block link module 470 is configured to detect a unit procedure operation 436 located in the drawing area 450 that is configured to register the desired tag 442. The common block link module 470 determines whether the unit procedure operation 436 has an undefined property, for example, a new tag or a different tag 442 assigned from the operation name or classification property of the unit procedure operation 436. When the common block link module 470 identifies common blocks and common block items from the recipe database and detects that a new tag or a different tag 442 has been assigned, the common block link module 470 has identified the common block database to the unit procedure operation 436. Assign common blocks and identified common block entries.

  In some embodiments, the recipe procedure tool 410 includes other recipe related editors, such as a recipe header editor, equipment requirement editor, and unit recipe attribute editor. Thereby, the user can further automatically perform recipe setting for other levels.

  In an exemplary implementation, recipe procedure tool 410 includes an equipment requirement editor 480 for updating equipment and field devices installed in an industrial plant by setting and editing. In this embodiment, the updated equipment and field devices are stored in the recipe database 310.

  In another exemplary implementation, the recipe procedure tool 410 includes a formula editor 490 for updating recipe formulas. The formula editor is used to set and edit common blocks and common block items from the common block database for the formula. In this embodiment, the formula is stored in the recipe database 310.

  Another embodiment of the present invention is a workflow related to recipe setting shown in FIG. The workflow 500 is executed by the recipe setting system 400 described above.

  In optional step S501, the recipe procedure tool 410 receives input from the input device and selects the level 424 from the level selection option 420. Recipe procedure tool 410 displays an optional stencil 434 associated with the selected level 434 in stencil window 432.

  In step S502, an input is received from the input device, the operation stencil 434 is selected, and the selected operation stencil 434 is moved and placed at a desired position in the drawing area 450 as shown in FIG. 6A. In the present invention, operation stencil 434 relates to unit procedure operation. Properties are assigned to the unit procedure operation 436 located in the drawing area 450, and at least an operation name, an operation identifier, and an operation type are assigned. Optionally, other properties are included that make it possible to automate the assignment of other functions, for example formulas.

  When the selected operation stencil 434 is located in the drawing area 450, it is a unit procedure operation 436. The recipe procedure tool 410 assigns predetermined properties to the unit procedure operation 436. The predetermined property is an identifier such as an operation identifier.

  In step S503, an input from the input device is received and a tag 442 is selected from the tag list 440. In some embodiments, the properties of the selected tag 442 are displayed in the tag properties area 448 for use in reviewing and determining whether the selected tag 442 is the desired tag. In addition, the input is received, and the selected tag 442 is moved to the drawing area 450.

  The tag link module 460 is configured to detect that the unit procedure operation 436 is on the drawing area 450. The tag link module 460 assigns the properties of the selected tag 442 to the detected unit procedure operation 436 when the detected unit procedure operation 436 is within a predetermined distance from the tag link module 460. In some embodiments, when there are multiple unit procedure operations 436 on the drawing area 450, a query window is displayed to the user to determine whether to assign the selected tag 442 to the detected unit procedure operation 436. Indicated.

  In step S504, the common block link module 470 determines whether a new tag or a different tag 442 is assigned to the unit procedure operation 436 based on the property assigned to the unit procedure operation 436. Detect for each procedure operation. The common block link module 470 identifies common blocks and common block items from the recipe database for the unit procedure operation 436, and when it is detected that a new tag or a different tag 442 has been assigned, the unit procedure from the common block database. Operation 436 is assigned the identified common block and the identified common block item. In step S505, the series of steps described above continues to create the next unit procedure.

  In an alternative embodiment, the common block link module 470 identifies formulas from the recipe database based on the properties of the operation stencil, ie, operation name, operation identifier, and operation type. The common block link module 470 uses the identified formula to retrieve common blocks and common block items from the common block database 320 and assign them to the unit procedure operation 436 on the drawing area 450. If the unit procedure operation 436 has a formula, the common block and common block items are assigned to the unit procedure operation 436.

300 repositories
310 Recipe database
320 common block database
330 Factory Database

Claims (14)

A recipe configuration system configured to communicate with a recipe database:
Displaying a plurality of operation stencils for selection of unit procedure levels for selection;
Displaying multiple tags;
Selecting one of the plurality of operation stencils by input, and positioning one operation stencil selected from the plurality of operation stencils as a unit procedure operation in a drawing area;
Assigning predetermined properties to the unit procedure operation;
A recipe procedure tool configured to: select one tag from the plurality of tags by input and move to the drawing area;
Determining whether the selected tag is within a predetermined area of the unit procedure operation, and configured to communicate with the recipe procedure tool;
When it is determined that the selected tag is within the predetermined area of the unit procedure operation, at least one predetermined property of the selected tag and a classification of the selected tag are assigned to the unit procedure operation. A tag link module configured to perform and assign to a given property;
Is configured to communicate with the recipe procedure tool, further determines whether the unit procedure operation has an undefined property, and determines that the unit procedure operation has an undefined property; A common block link module configured to perform a step of assigning a formula to the unit procedure operation;
The recipe setting system characterized by including.   The recipe setting system according to claim 1, wherein the predetermined property assigned to the unit procedure operation from the selected tag includes an operation name and an operation type.   The recipe setting system of claim 1, wherein the common block link module is further configured to determine at predetermined intervals whether the unit procedure operation has an undefined property. The recipe setting system is further configured to communicate with a common block database, the common block database storing a common block for setting the formula and a common block item for setting the formula, and the common block database Block link module
Identifying at least one common block for the formula or a common block item for the formula from the common block database based on the predetermined property of the unit procedure operation;
Retrieving the identified at least one common block or the identified common block item from the common block database;
The method of claim 1, further comprising: assigning the retrieved at least one common block of the formula or the retrieved common block item of the formula to the unit procedure operation. Recipe setting system. The recipe setting system is further configured to communicate with a factory database, and the recipe procedure tool includes:
Identifying hierarchical properties for the plurality of tags from the recipe database and the factory database;
Retrieving the identified hierarchical properties for the plurality of tags from the recipe database and the factory database;
The recipe setting system according to claim 1, further comprising: displaying the plurality of tags in a hierarchical order based on the retrieved hierarchical properties. Recipe Builder tool
Updating the equipment and field devices;
The recipe setting system according to claim 1, further comprising a facility editor configured to: store the updated equipment and the updated field device in the recipe database. A recipe setting method performed in a recipe setting system configured to communicate with a recipe database, comprising:
Displaying a plurality of operation stencils for selection of unit procedure levels for selection;
Displaying multiple tags;
Selecting one of the plurality of operation stencils by input, and positioning one operation stencil selected from the plurality of operation stencils as a unit procedure operation in a drawing area;
Assigning predetermined properties to the unit procedure operation;
Selecting one tag from the plurality of tags by input and moving to the drawing area;
Determining whether the selected tag is within a predetermined area of the unit procedure operation;
When it is determined that the selected tag is within the predetermined area of the unit procedure operation, at least one predetermined property of the selected tag and a classification of the selected tag are assigned to the unit procedure operation. Assigning to a given property;
Determining whether the unit procedure operation has an undefined property;
Assigning a formula of the recipe database to the positioned operation stencil when it is determined that the unit procedure operation has an undefined property.   The recipe setting method according to claim 7, wherein the predetermined property assigned to the unit procedure operation from the selected tag includes an operation name and an operation type. The recipe setting system is further configured to communicate with a common block database, the common block database storing a common block for setting the formula and a common block item for setting the formula, and the recipe The setting method is
Identifying at least one common block for the formula or a common block item for the formula based on the predetermined property of the unit procedure operation;
Retrieving the identified at least one common block or the identified common block item from the common block database;
The recipe setting method according to claim 7, further comprising: assigning the retrieved at least one common block of the formula or the retrieved common block item of the formula to the unit procedure operation.   The recipe setting method according to claim 9, further comprising a step of storing the extracted at least one common block and the extracted common block item in the recipe database. The recipe setting system is further configured to communicate with a factory database, the method comprising:
Identifying hierarchical properties for the plurality of tags from the recipe database and the factory database;
Retrieving the identified hierarchical properties for the plurality of tags from the recipe database and the factory database;
The recipe setting method according to claim 7, further comprising: displaying the plurality of tags in a hierarchical order based on the extracted hierarchical property. A non-transitory computer readable medium storing a computer program to be executed by a recipe setting system to perform a recipe setting method, the recipe setting system including a recipe procedure tool, the recipe setting method comprising: ,
Displaying a plurality of operation stencils for selection of unit procedure levels for selection;
Displaying multiple tags;
Selecting one of the plurality of operation stencils by input, and positioning one operation stencil selected from the plurality of operation stencils as a unit procedure operation in a drawing area;
Assigning predetermined properties to the unit procedure operation;
Selecting one tag from the plurality of tags by input and moving to the drawing area;
Determining whether the selected tag is within a predetermined area of the unit procedure operation;
When it is determined that the selected tag is within the predetermined area of the unit procedure operation, at least one predetermined property of the selected tag and a classification of the selected tag are assigned to the unit procedure operation. Assigning to a given property;
Determining whether the unit procedure operation has an undefined property;
Assigning a formula of the recipe database to the positioned operation stencil when it is determined that the unit procedure operation has an undefined property. The recipe setting system is further configured to communicate with a common block database, the common block database storing a common block for setting the formula and a common block item for setting the formula, and the recipe The setting method is
Identifying at least one common block for the formula or a common block item for the formula based on the predetermined property of the tag;
Retrieving the identified at least one common block or the identified common block item from the common block database;
12. The recipe setting of claim 11, further comprising: assigning the retrieved at least one common block of the formula or the retrieved common block item of the formula to the positioned operations stencil. Method. The recipe setting system is further configured to communicate with a factory database, and the recipe setting method includes:
Identifying hierarchical properties for the plurality of tags from the recipe database and the factory database;
Retrieving the identified properties for the plurality of tags from the recipe database and the factory database;
The recipe setting method according to claim 11, further comprising: displaying the plurality of tags in a hierarchical order based on the extracted hierarchical properties.

Images