JP2001243341A - Function block model creation method and device - Google Patents

Abstract

(57) [Summary] [Problem] Work evaluated by IDEF in order to perform work evaluation and creation of function blocks at the previous stage when programming using function blocks so that they can be executed accurately without any trouble. A means for automatically converting a flow into a function block is provided. SOLUTION: A function block model creation device gives a work procedure by an activity and an ICOM parameter corresponding to the activity by a modeling method which grasps a work as a set of activities and grasps a flow related to the activity and a flow of information as an ICOM. Means for converting the parameter into a parameter of a module of a function block which has a one-to-one correspondence with a component of the device for realizing the work; and output means for outputting the conversion result as a model of the function block. Prepare. The parameters are the inputs that are used and converted for the activity, the output resulting from the conversion of the input, the controls that constrain the activity, and the mechanism that executes the activity.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a method and an apparatus for creating a function block model used for system design.

[0002]

2. Description of the Related Art In a system design using a computer, programming is performed using an object-oriented notation called "function block". For example, a function block in a distributed system of industrial process control is defined by a standard called “IEC61499”. In the system assumed here, as shown in FIG. 16, a plurality of "devices 1" to "devices 4" are connected to each other via a communication network 5, and the functions of the system ( Application) is realized. For example,
As shown in FIG. 17, each device is represented by blocks 1 to 4, and each block is connected by two types of lines, “event flow” and “data flow”. According to this notation method, the point that the progress of the event can be managed in a ladder manner is superior to the conventional notation using only a simple data flow.

On the other hand, an industrial production process control system (Industrial P
(Rocess Manufacturing Control System) has become huge in recent years, and design is performed for each module. The use of the "function block" is very effective in designing a mechanism or mechanism for controlling those modules, but in order to design while viewing the whole, very high skills are required for the designer. Has been requested.

[0004] Specifically, when a system is designed by the above-described event-driven function block (IEC61499), it is necessary to perform a basic design of the system as preprocessing. Therefore, a method of developing from the human interface portion is used. This is based on the definition of what to do internally when a switch on the operation panel of the control system is pressed, and it is performed for all switches and the whole is configured by combining them It is. However, this method is performed manually, and the flow of each component is easy to understand. However, it may be very difficult to understand as a whole.

[0005] When programming an operation using an application using a function block, conventionally, it has been usual to use an application tool itself and perform programming in a graphic processing manner on a screen. However, when trying to determine the flow while evaluating the work, it was hard to say that the mark using this function block was easy to use.

On the other hand, in terms of evaluation, IDEF (In
Integration Definition Language) is known. This is a general term for a modeling method based on a transition diagram (diagram) expression, and is used to evaluate waste of work, inconsistency in flow, and the like. Therefore, when constructing a system as described above, it is conceivable to perform work evaluation using this method at a stage prior to programming using function blocks.

[0007]

However, when work evaluation is performed before the system design,
Creating a model using IDEF, and then creating a function block, is a time-consuming task. For this reason, there is a case where programming in the function block is performed without performing sufficient evaluation, and as a result, there is a problem that maintenance takes time or does not work well.

According to the present invention, since the work evaluation and the creation of the function block at the previous stage when programming using the function block as described above can be executed accurately without any trouble, the evaluation by the IDEF is performed. It is an object of the present invention to provide a technique for automatically converting a work flow into a function block.

[0009]

According to the present invention, a preprocessing for creating a function block, which has been performed by a combination of individual components, is executed by a method of evaluating the entire work from analysis, and the result of the analysis and evaluation by the method is used as a function. The basic idea is to automatically convert to blocks.

In the present invention, one of the IDEF techniques, "IDEF
Evaluate work using “0.” “IDEF0” regards work or work as a set of “activity” and “ICOM” describes the flow of “things” and “information” involved in the activity.
This is a modeling method (Function Modeling) that is explicitly grasped as (Icom).

Therefore, according to the present invention, a work procedure is given by an activity and an Icom parameter corresponding to the activity by a modeling method in which the work is regarded as a set of activities and those involved in the activity and the flow of information are grasped as an ICOM. A method and apparatus for creating a function block model, wherein the parameters are converted into the parameters of a function block module corresponding to the components of the apparatus for realizing the work, and the conversion result is output as a function block model. Is provided.

Further, there is provided a recording medium on which a computer program for executing the method of creating a function block model according to the present invention is recorded.

As shown in FIG. 1A, for one activity, ICOM is as follows.

Input (input): what is used and converted for the activity Control (constraint): what restricts the activity Output (output): what is obtained as a result of converting the input Mechanism: what executes the activity (People, objects, machines, etc.).

The following rules are used to convert the model parameters (input, output, control, mechanism) according to the above "IDEF0" into the parameters of the function block module. That is, as shown in FIG. 1B, the activity (AC) of “IDEF0” is located at the upper part of the function block 1 (event input / output unit).
a, input (I) is the upper part 1a of the function block 1
Input (event flow), mechanism (M) is at the bottom of the function block 1 (data input / output unit) 1
b, control (C) is input (data flow) to the lower part 1b of the function block 1; output (0) is output (event flow) (0) -1 from the upper part 1a of the function block 1;
b to output (data flow) (0) -2.

The function block 1 in the preceding stage
(0) -1 and data (0)-output from
2 is an input to the upper part 2a and the lower part 2b of the function block 2 at the next stage, respectively. The input (data corresponding to the control) to the lower part of the function block corresponding to the mechanism (M) is not limited to the output from the preceding function block, but may be the output from another function block.

[0017]

According to the present invention, ICOM (Input, Control, Output, Mechanism) for activity
Is automatically converted into a function block in accordance with the rules as described above.

Thus, evaluation and programming are appropriately performed, the quality of the completed program is improved, and at the time of maintenance, re-analysis of work is easy, and as a result, efficiency can be improved. Further, since the function blocks correspond to the hardware, the cooperation between the hardware can be easily understood.

Since the entire work is modeled, the entire flow is not mistaken. In addition, since the function block is automatically converted into a function block, a function block diagram having no contradiction can be created without error such as omission.

Since work analysis is performed by a method such as IDEF, inconsistencies at the time of design in the system are removed in advance, so that the system can be optimized.

Before the conversion into the function blocks, the system can be evaluated by applying the work analysis to the simulation tool.

[0022] Therefore, improvement of total development efficiency,
The development period can be shortened.

Since the flows evaluated systematically by the IDEF are collectively converted into function blocks, the degree of perfection is high and maintenance is easy, so that the time can be reduced as a result.

[0024]

DESCRIPTION OF THE PREFERRED EMBODIMENTS As described above, when a "function block", which is a notation used in system design, is used, it is necessary to perform a basic design of the system as a preceding step. When performing the basic design, the work performed by the system is decomposed into detailed element work that is a unit using the work analysis tool of “IDEF0”. Through the analysis at IDEF0, activities that represent the contents of elementary work, mechanisms that perform each elementary work (Mechanism), inputs that are the target of elementary work (Input), outputs that result from elementary work (Output), and elementary work The controls (Control) required to perform the operation become clear (Fig. 1).

On the other hand, the function block is a block that executes a function when an “event flow” is input. The whole system is configured by combining these blocks.

As shown in FIG. 2, the function block defined by the IEC61499 is an event input / output unit ("Insta
1a and data input / output unit ("Type name")
1b).

The event input / output unit 1a has its input unit (Ev
ent inputs) to receive events from the event flow. Thereby, one or more algorithms are executed. The event input / output unit 1a sends an event from an output unit (Event outputs) to an event flow due to execution of an algorithm or some function in a resource.

The data input / output unit 1b includes a data input unit (Data inputs) representing a variable and a data output unit (Data output).
s). Internal data representing internal variables (Interna
l data) cannot be accessed from the outside by the data flow, and can be used only by the execution control function (Execution Control) in the event input / output unit 1a and the algorithm in the data input / output unit 1b.

What is required for the "function block" is an event input, an event output, an algorithm (function), and a data flow (if necessary). FIG.
As shown in (1), the input, output, mechanism, and control of the work analysis result by IDEF0 are associated with the function blocks according to the rules described above (FIG. 1) (details will be described later). That is, activity → algorithm, flow of analysis result → event input and event output,
After conversion from control to data flow, the function block is completed by grouping by mechanism.

Hereinafter, a specific description will be given.

Conventionally, many production facilities have a PLC (Programma
ble Logic Controller) is used. The ladder language is used for programming of the PLC, but in the ladder language, due to the processing system, there are parts where modularization and layering are difficult to express, so logical modules are actually decided by the programmer himself. It is programmed by division and layering. This makes it difficult for others to understand, and repeated additions and deletions can obscure the programmer's own arrangements and cause bugs.

When designing a production system by programming using the aforementioned “function block”,
The structure of the program is closely linked to the mechanical system to be controlled, and a ladder in the PLC is clearly divided for each mechanical module. By doing so, both the operation and the program configuration can be made independent in units of single function modules, and a system is constructed by combining these modules.

However, the function cannot be exhibited only by stacking the modules. As a mechanism to connect them, MOFOS (Module Fo
rmation System). In FIG. 4, the manager receives an instruction based on a work description created by a user, and writes the instruction on a whiteboard serving as an interactive communication area with each module. Each module has a work order in advance, and when the work order on the whiteboard matches the work order held,
Perform work according to the work instructions. Then, tell the manager that you are working via the whiteboard. The manager monitors the behavior display and confirms that all modules are on standby, and then issues the next work instruction. By repeating this, a series of operations are performed. That is, this system is a distributed system in which each module operates autonomously in response to a work instruction.

To construct such an autonomous decentralized system,
The following two approaches are used.

System analysis (systematization and evaluation of functions) using "IDEF0" The procedure of system design (coordination design between modules) using "function blocks" is as follows.

As shown in FIG. 5, first, as step 1, system analysis is performed using IDEF0. How the initial input to the system is processed in the system until the goal is achieved (in this case, the processing is not limited to mechanical processing), what is required for the processing, etc. To clarify. Then, the evaluation of whether or not it is appropriate is repeated, and finally, the module configuration of the system is determined.

In the next step 2, mechanism design and system design are performed. Based on the output of step 1, the mechanism is designed based on the mechanism in IDEF0. Also, based on the activity and the ICOM connected to it, the system is designed using function blocks. Icom represents input and output for activities in IDEF0 as described above. Here, it is necessary to clarify at what timing each module performs processing and how each module has a relationship from the viewpoint of the module. Thereby, autonomy and cooperation between modules are determined for each module.

In the next step 3, hardware design and software design of the control system are performed. As the specifications of the control equipment become clear as a result of the mechanism design, the control system hardware is designed based on this. In addition, software design is performed from the algorithm, event flow, and data flow in the function block based on the output in system design.

Finally, as step 4, software is installed based on the input / output specifications from the control system hardware design and the module communication specifications from the software design.

The details will be described below. (1) System analysis using “IDEF0” As described above, one of the features of IDEF0 (Function Modeling)
One is the four arrows called ICOM, which are "information" and "things" in a business process that is a set of activities.
Is to distinguish them. That is, in addition to specifying inputs and outputs relating to activities, constraints and resources for performing the activities can be specified.

IDEF0 has one subject, purpose, and viewpoint. The theme defines the boundary area of the model, the "criterion for selecting the knowledge necessary for the model", the purpose is "a group of questions answered by building the model", and the viewpoint is "the purpose of the model". A person, object, or machine that can answer (2) System design by “function block” By introducing a software module that has a one-to-one correspondence with a hardware module, software design is performed as a combination of modules. "IEC 61499" is used for notation of modules and applications.

The system constructed by IEC61499 is described as a system model, a device model, a resource model, and an application model. First, build the application model. After that, a device model and a system model are constructed in consideration of decentralization and execution devices.

Based on the analysis performed by IDEF0 as described above, the application is described in the function block.

The “mechanism” of IDEF0 is replaced by a function block, the “activity” is replaced by a function of a function block, and the “arrow” representing data transfer is replaced by a data flow. Create a function block diagram from Arrows representing the flow of objects among the inputs / outputs in the IDEF0 notation do not appear on the function block diagram. Further, since information indicating the operation order is not included in IDEF0, the diagram is completed while supplementing this as an “event flow”. From the completed diagram, "event flow" and "data flow" become clear.

In many systems, long sequences need to be executed, and describing this as a single function block application is problematic in terms of readability and maintainability. Therefore, a method is adopted in which the sequence is divided into appropriate sizes, and an event for starting the sequence is generated from an external application.

The external application is responsible for monitoring the start and end of the function block application, and sends an execution command to the function block application so that the system appropriately executes a long sequence. Services to external applications are:
Converted (mapped) to service interface function block. The function block application performs a predetermined operation according to a command called from an external application.

In the example shown in FIG. 3, the external application sends a command to the system according to the execution order of the function block application described as the user program.

With the above operations, the system is represented as a plurality of application models. Since the function block appears in a plurality of application models, the specification of the function block is not clear as it is. Therefore, function blocks representing the same software module are collected from all application models, and the event input, event output, data input, data output, and functions (algorithms) executed when the event is activated are collected.
As a result, the specifications of each software module become clear.

Next, a specific embodiment will be described.

First, an apparatus is constituted by a combination of basic modules divided for each function. These modules are not merely divided mechanically, but are modules that operate autonomously.

An anodic bonding device for a pressure sensor will be described as an example of a device constituted by an autonomous module. This is an apparatus for joining a pressure sensor chip to a glass pedestal, and its schematic configuration is shown in FIG.

This device includes a component supply module, a position correction module, an assembly module, a pick and place
Modules 1 and 2, a Y-axis module and other modules (for example, an image module, an electrostatic removal module, a heating voltage application module, etc.). The outline of each module is as follows. (1) Component supply module Each component is supplied in each tray from the previous process. The positioning of the tray and the presence / absence detection are performed. After the joining, the work is projected. (2) Position correction module The position of the chip component is corrected. The alignment on the plane is performed mechanically, but the rotation direction is corrected based on the image captured from the camera. (3) Image module Recognizes the rotation direction of the chip component. This is because the chip components need not always be aligned with the supply tray. As a means for this image processing, a positioning image sensor is used. (4) Static electricity removal module By removing clean air by ionizing clean air and spraying it on each component. (5) Heating voltage application module Heat and voltage necessary for joining are applied to the work. An air heater is used as an aid to uniformly apply heat. A flow meter (mass flow meter) is used for detecting the flow rate of air. (6) Pick and place module 1 A mechanism for holding a glass part and a mechanism for moving up and down. (7) Pick & place module 2 A mechanism for picking up chip components and a mechanism for moving up and down. (8) Y-axis module The Y-axis indicates the depth direction of the device. The Y-axis module
The pick and place modules 1 and 2 are moved in the Y-axis direction. In this direction, the modules for supplying the component, correcting the position, removing static electricity, and applying a heating voltage are arranged.

As a controller, a personal computer (PC) and a PLC are used as shown in FIG. Rather than preparing control hardware for each mechanical module, the ladder in the PLC is clearly divided and distributed in software to realize the MOFOS described above.

A liquid crystal touch monitor is connected to the PC as a display. The role of the PC corresponds to the “manager” of the MOFOS, interpreting the operation program and giving work instructions. In addition, the PC is used as an HMI (Human Machine Interface) to input various operations by the operator,
It displays the status of the system and provides other information to the workers. In other words, the role of the personal computer is completely limited to the user interface, and all peripheral devices such as valves and motors are controlled by the PLC. By completely sharing the roles, input and output to and from peripheral devices can be exclusively handled, so that distributed modules in the PLC can be easily formed.

On the other hand, the module configuration of the PLC itself comprises four types: a digital input module (DI), a digital output module (DO), an analog input module (AI), and a positioning module (PPM). The role of the PLC is to handle the whiteboard and the members' workbooks, and to control the mechanical modules. Data transmission and reception between the manager and the whiteboard is performed by serial communication, and electrical connection with the mechanical system module is performed by an input / output table in the PLC.

The work is analyzed by IDEF0, and necessary mechanisms (modules) are clarified. Therefore, the above-mentioned modules correspond one-to-one with the machine modules constituting the actual apparatus.

The target step is an anodic bonding step of bonding the pressure sensor chip to the glass pedestal at a high temperature and a high voltage. In order to analyze this process in IDEF0, the purpose and viewpoint of the model by IDEF0 are determined as follows.

Purpose: "thing" in the joining / assembly process
And the flow of information.

Viewpoint: Designer of bonding / assembly equipment This anodic bonding process is analyzed by IDEF0. For example, as for the operation of “statically removing the pedestal on the tray” in this step, as shown in FIG.
For A0, input is I1 "pedestal tray", control is C1
`` Location (position) information of pedestal tray '', C2 `` Location (position) information of static removal module '', C3 `` Location (position) information of heating voltage application module '' and C4 `` Device characteristics of static removal module '', The mechanism is M1 "Parts supply module", M2 "Pick and place module"
(Hereinafter referred to as "PPM") 1 ", M3" Y-axis module "and M4" Electrostatic removal module ", outputs O1" pedestal placed in U-shape on heating module "and O2" U-shaped place ( Move) end information. ""U-shapedplace"
This means moving an object such as a pedestal in a U-shaped trajectory.

The result of analyzing this in a detailed work unit is as follows:
As shown in FIG. That is, for activity A1 of the work unit "positioning the pedestal tray" first, input is I1 "pedestal tray", control is C1 "location (position) information of pedestal tray", and mechanism is M1 "component supply module" And M3 “Y-axis module”, the output is “positioned pedestal tray” and “pedestal positioning end information”, which is the next “pick pedestal from pedestal tray”
The input is the activity A2 of the work unit.

For the next activity A2, the input is “positioned base tray” and “base positioning end information”, and the control is C1 “base tray location”.
(Position) information ", the mechanism is M2" PPM1 ", and the output is" Picked pedestal "and" Pedestal pick end information ", which is the next" Positioning the pedestal to the static removal module ".
The activity A3 of the work unit is input.

For the next activity A3, the input is “Picked pedestal” and “Pedestrian pick end information”, the control is C2 “Location (position) information of static elimination module”, the mechanism is M2 “PPM1” and The output of M3 “Y-axis module” is “the pedestal positioned on the static elimination module” and “positioning end information”, which are the inputs of the activity “A4” of the next “unit for static elimination” work unit.

For the next activity A4, the input is “pedestal positioned on the static elimination module” and “positioning end information”, the control is C4 “static elimination module device characteristics”, and the mechanism is M4 “static elimination module”. Module), the outputs are "statically removed pedestal" and "static removal end information", which are the activity "A5" of the next "place the statically removed pedestal on the heating module in a U-shape".
Input.

For the next activity A5, the input is “pedestal from which static electricity has been removed” and “information on the end of static electricity removal”, and the control is C3, “location of heating voltage application module”.
(Position) information ”, the mechanism is M3“ Y axis module ”and
M2 “PPM1”, output is O1 “pedestal placed in U-shape on heating module” and O2 “end information in U-shaped place”
Which is the output of the entire model (FIG. 8).

In other words, FIG. 9 shows an example of a task (work) modeled by IDEF0, and FIG. 8 shows the model of FIG.
These are collectively represented (called context diagrams).

In the analysis of FIG. 9, the four types of ICOMs for the activity are not one. This means that modeling is intermediate, and each activity can be analyzed into more detailed units of work. The result of further analysis is as shown in FIG.

First, for the activity A1 of the work unit “position the glass pedestal tray”, the input is I1
`` Pedestal tray '', control is C1 `` pedestal tray location (position) information '', mechanism is M1 `` component supply module '', output is `` glass pedestal positioning completion information '',
This is the next “Positioning PPM1 on glass pedestal”
The input is the activity A2 of the work unit.

For the next activity A2, the input is “glass pedestal positioning completion information”, the control is C3 “the location (position) information of the glass pedestal”, and the mechanism is M3.
The “Y-axis module” output is “PPM1 positioning completion information”, which is the input of activity A3 of the next “pick glass pedestal” work unit.

For the next activity A3, the input is “PPM1 positioning completion information”, the control is C3 “glass pedestal location (position) information”, and the mechanism is M2.
“PPM1”, the output is “Pick Complete Information”, which is the next “Position PPM1 to Static Elimination Module”
The input is the activity A4 of the work unit.

For the next activity A4, the input is “pick completion information”, the control is C2 “location (position) information of the static removal module”, and the mechanism is M3 “Y”.
Axis module ", the output is" PPM1 module positioning complete ", which is the input for activity A5 of the next" set glass pedestal in static elimination module "work unit.

For the next activity A5, the input is “PPM1 module positioning completed” and the control is C2.
"Location (position) information of static elimination module", mechanism is M2 "PPM1", output is "glass pedestal set completion information", and this is the activity "A6" Input.

For the next activity A6, the input is “glass pedestal set completion information”, the mechanism is M4 “static elimination module”, and the output is “static elimination end information”.

From such a model, it is possible to extract a work item and a necessary function for each module, with the mechanism as one module.

Next, conversion into a function block
Perform (mapping).

For example, when the mechanisms, inputs, outputs, and controls relating to the activities of the intermediate analysis results as shown in FIG. 9 are mapped (converted) in accordance with the rules shown in FIG. 1, the function blocks as shown in FIG. (Part). This is IDEF0
Activity "Pick a glass pedestal" extracted in
Is described in a function block diagram.

Similarly, if the mechanism, input, output, and control relating to the activity of the analysis result in FIG. 10 are mapped (converted) according to the above-described rules, the function block (part) as shown in FIG. 12 is obtained.

FIG. 13 shows an example in which data input / data output / event input / event output related to the pick and place module are summarized from all the function block diagrams created in the same manner.

Further, considering the implementation of the PLC, the labels of data input / data output / event input / event output are replaced with addresses. FIG. 14 shows an example of “pick and place module 1” described by an address.

Although the appearance of the function block has been clarified, it is necessary to match the states of the software module and the hardware module to make them into parts, and to perform appropriate operations even in a situation where a plurality of events occur randomly. Need to be designed to do In IEC61499, the function for this is called “Execution Control” (execution control) and is described in “Execution Control Chart (ECC)” (execution control transition diagram). Here, “Execution Control” is described in a state chart in terms of readability. FIG. 15 shows an example of “pick and place module 1”.

With the above operation, the specifications of the function blocks and the data flows and event flows between the function blocks become clear.

As described above, the following advantages can be obtained by applying the autonomous decentralized system to the production facility using IDEF0 and the function block.

By applying IDEF0 and the function block, systematic and systematic module programming can be performed on a ladder which is a PLC programming language.

Since the ladder program of each block is independent by being designed by the function block, it is possible to develop the module unit.
Therefore, the time required for designing the system is reduced due to the efficiency of programming and debugging work by a plurality of developers.

In the debugging of the ladder sequence program of the PLC, one correction often affects the entire sequence.
Modification is easy because it only needs to be done within the block.

Each module is compatible with the IDEF0 mechanism in both hardware and software. In addition, since each module has a high degree of independence by a function block, if a similar mechanism is extracted by another device, Reusable.

As described above, in the embodiment, the anodic bonding step
Modeling is performed using IDEF0, and the system is designed using function blocks based on the results. In other words, the anodic bonding work is performed by a module (Mechan
analysis from the perspective of ism) and break it down into meaningful work-level units. The work (activity) appearing here corresponds to the title of the work instruction in MOFOS. Further, by decomposing the diagram into the operation of each module, the specific operation of each module in the work instruction sheet becomes clear. As a result, all the work is arranged in the module as a work instruction, and a signal for performing the operation can be clarified from the Control.

The work disassembled by IDEF0 not only becomes the contents of the work instruction, but also allows the activity to correspond to the function block as it is.
In IDEF0, activities are connected by objects and information. However, the notation of function blocks allows each operation to have the meaning of an event-driven work procedure. Further, the operation in the function block can be converted to a PLC ladder and implemented.

According to such a procedure, the system design can be systematically performed from the production process to the mounting of the PLC on the ladder in consideration of the autonomous decentralization.

[Brief description of the drawings]

FIG. 1 is a diagram showing rules for converting an activity based on “IDEF0” and an ICOM into a function block.

FIG. 2 is a diagram showing a configuration of a function block.

FIG. 3 is a diagram showing conversion from an “IDEF0” model to a function block.

FIG. 4 is a view showing a method of configuring a system by connecting modules.

FIG. 5 is a diagram showing a procedure of system development.

FIG. 6 is a diagram showing a schematic configuration of an anodic bonding apparatus for a pressure sensor chip.

FIG. 7 is a diagram showing a configuration of a module and a controller of the anodic bonding apparatus.

FIG. 8 is a diagram showing an example in which the “IDEF0” model is combined into one activity and a plurality of ICOMs.

FIG. 9 is a view showing an analysis model of “IDEF0” corresponding to the model of FIG. 8;

FIG. 10 is a diagram showing an “IDEF0” model by an activity of a work unit and ICOM.

FIG. 11 is a diagram showing a function block converted from the model of FIG. 9;

FIG. 12 is a diagram showing a function block converted from the analysis result of FIG. 10;

FIG. 13 is a diagram showing an example in which data input / data output / event input / event output related to the pick & place module are summarized from the function block diagram.

FIG. 14 is a diagram showing an example of “pick and place module 1” described by an address.

FIG. 15 is a diagram showing an example of “Pick & Place Module 1” described in an “Execution Control” chart.

FIG. 16 is a diagram showing a system model using function blocks.

FIG. 17 is a diagram showing an application model using function blocks.

[Explanation of symbols]

 1, 2, 3 ... block, 5 ... communication network.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Yutaka Harada 2-12-19 Shibuya, Shibuya-ku, Tokyo Stock Company Takeuchi Shayama (72) Inventor Hiroshi Tsunematsu 2-12-19 Shibuya, Shibuya-ku, Tokyo Stock Company Takeuchi Shayama (72) Inventor Yoshitaka Tomita 2-12-19, Shibuya, Shibuya-ku, Tokyo F-term (reference) 5B049 BB07 CC21 CC32 EE01 GG04 GG07

Claims (4)

[Claims] Claims 1. A work is regarded as a set of activities.
A step of giving a work procedure as an activity and an ICOM parameter corresponding to the activity by using a modeling technique for grasping what is involved in the activity and the flow of information as an ICOM, and the parameter corresponding to the component of the device that intends to realize the work. A method of creating a function block model, comprising: converting a parameter of a function block module into parameters; and outputting a result of the conversion as a function block model. 2. The method according to claim 1, wherein the parameters of the ICOM are used for an activity, an input to be converted, an output obtained as a result of converting the input, a control for restricting the activity, and execution of the activity. A function block model creation method, characterized in that 3. A recording medium on which a computer program for executing the method according to claim 1 or 2 is recorded. 4. The work is regarded as a set of activities,
By means of a modeling method that grasps the activities involved and the flow of information as ICOMs, means for giving the work procedure as activities and ICOM parameters for the activities, and the parameters correspond to the components of the device that intends to realize the work. A function block model creating apparatus, comprising: means for converting a parameter of a function block module into parameters; and output means for outputting the conversion result as a function block model.