JP6948997B2 - Control logic diagram analysis device and control logic diagram analysis method - Google Patents

Description

The present application relates to a control logic diagram analysis device for analyzing a control logic diagram and a control logic diagram analysis method.

In the development of plants for water and sewage, control logic diagrams that describe operation plans that define the operation specifications of equipment with flowcharts and logical operations are often used. However, depending on the scale of the plant to be developed, several hundred control logic diagrams may be required, and it is required to efficiently create control logic diagrams.
Product line development that creates a control logic diagram by combining common processing and variable processing by identifying the processing that is common to multiple plants and the processing that changes (variable processing) as one of the methods for improving the efficiency of creating control logic diagrams. There is. By converting common processing into parts and combining these parts with variable processing to create a control logic diagram, it is possible to efficiently carry out derivative development of the plant.

In the technique described in Patent Document 1, another control logic is used for the logic described in a certain control logic drawing by using the logical connection information or the position information of the signal or the arithmetic element in the control logic diagram. You can search for similar logic contained in the figure.
As a result, it is possible to acquire highly reusable control logic components by converting the frequently described logic into components.

Japanese Patent No. 5538301 (Page 6, Fig. 1) Japanese Patent No. 6297235 (pages 8 to 10, FIG. 2)

In the technique shown in Patent Document 1, since the searchable similar logic matches the reference logic, a logic that is partially different from the reference logic is searched for. There was a problem that it could not be done.
Therefore, the common processing common to a plurality of plants can be made into parts, but the variable processing different for each plant cannot be appropriately extracted.

Patent Document 2 describes a method of searching a control logic diagram for a similar control logic component suitable for reuse by using an analysis rule for analyzing the contents of the control logic component from the control logic diagram.
In Patent Document 2, although it is possible to search for a control logic that is partially different from the reference control logic, there is a problem that only similar ones can be searched.
There is also the problem that it is necessary to create analysis rules.

The present application discloses a technique for solving the above-mentioned problems, and provides a control logic diagram analysis device and a control logic diagram analysis method capable of extracting common processing in a plurality of plants and variable processing for each plant. The purpose is to do.

The control logic diagram analysis device disclosed in the present application is a control logic diagram database that stores a control logic diagram for controlling a plant, and a control for creating a control logic diagram for common processing commonly used in a plurality of plants. A common processing search unit that searches for common processing by searching the parts used in the control logic diagram of the control logic diagram database for the control logic component database stored as logic components and the control logic components of this control logic component database. , Based on the search result by this common processing search unit, the variable processing search unit that searches the variable processing that changes for each plant from the control logic diagram, the common processing searched by the common processing search unit, and the variable processing search unit It is provided with a feature model generation unit that generates a feature model that defines the relationship between these processes based on the variable processing performed.

According to the control logic diagram analysis apparatus disclosed in the present application, it is possible to extract common processing in a plurality of plants and variable processing for each plant.

FIG. 6 is a block diagram showing a schematic configuration of a control logic diagram analysis device according to the first embodiment. The control logic diagram according to the first embodiment is a block diagram showing a hardware configuration for realizing the analysis device. The control logic diagram according to the first embodiment is a diagram showing an example of a control logic diagram stored in the control logic diagram DB of the analysis device. FIG. 5 is a diagram showing an example of a feature model input from the feature model generation unit of the control logic diagram analysis device according to the first embodiment. Diagram of Control Logic According to Embodiment 1. FIG. 5 is a diagram showing an example of component specifications set by the control logic component specification setting unit of the analysis device. The control logic diagram according to the first embodiment is a flowchart showing the operation of the control logic component specification setting unit of the analysis device. FIG. 5 is a flowchart showing the operation of the common processing search unit of the control logic diagram analysis device according to the first embodiment. The control logic diagram according to the first embodiment is a diagram showing an example of a method of storing a place where a control logic component appears in the operation of the common processing search unit of the analysis device. FIG. 5 is a flowchart showing the operation of the variable processing search unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a flowchart showing the operation of the feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a flowchart showing details of inter-component setting processing of the feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a diagram showing a specific example of a method of setting a parent-child relationship between features from an arrangement of parts in a feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a flowchart showing details of non-functional requirement setting processing of the feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a diagram showing an example of generating features of non-functional requirements of the feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 5 is a flowchart showing details of inter-component connection processing of the feature model generation unit of the control logic diagram analysis device according to the first embodiment. FIG. 6 is a block diagram showing a schematic configuration of a control logic diagram analysis device according to the second embodiment. FIG. 5 is a flowchart showing the operation of the layered control logic diagram analysis rule generation unit of the control logic diagram analysis device according to the second embodiment. The control logic diagram according to the second embodiment is a diagram showing an example of the layered control logic diagram analysis rule generated by the layered control logic diagram analysis rule generation unit of the analysis device.

Embodiment 1.
FIG. 1 is a block diagram showing a schematic configuration of a control logic diagram analysis device according to the first embodiment.
In FIG. 1, the control logic diagram analysis device 10 includes a control logic component DB (database, database, hereinafter referred to as DB) 11, a control logic component specification input unit 12, a control logic component specification setting unit 13, and a control logic diagram. It has a DB 14, a common processing search unit 15, a variable processing search unit 16, a feature model generation unit 17, and a feature model display unit 18.

The control logic component DB 11 stores control logic component assets, which is a common process used in a plurality of plants. The control logic component specification input unit 12 inputs the specifications of the control logic component in the control logic component DB 11.
The control logic component specification setting unit 13 sets the control logic component in the control logic component DB 11 and the specifications of the control logic component input by the control logic component specification input unit 12.
The control logic diagram DB 14 stores existing control logic diagram assets that control the plant.

The common processing search unit 15 is commonly used in a plurality of plants by searching for a part where the control logic component acquired from the control logic component DB 11 is used in the control logic diagram in the control logic diagram DB 14. Search for common processing. Then, the parent-child relationship of the control logic component is extracted.
The variable processing search unit 16 searches for and extracts variable processing, which is a plant-specific processing, based on the parent-child relationship of the control logic components searched by the common processing search unit 15.
The feature model generation unit 17 generates a feature model by combining the common processing and the variable processing obtained by the common processing search unit 15 and the variable processing search unit 16 as a tree structure. The feature model display unit 18 displays the generation result of the feature model generation unit 17.
A feature model is a tree-structured representation of the relationships between features in a target product or plant and is used to create control logic diagrams to enable product line development.

FIG. 2 is a block diagram showing a hardware configuration for realizing the control logic diagram analysis device according to the first embodiment.
In FIG. 2, the PC (Personal Computer) 100 is hardware that realizes the control logic diagram analysis device 10.
The PC 100 includes a CPU (Central Processing Unit) 101 that performs calculations, a storage device 102 that can store information, an input device 103 that can input information such as a keyboard, a display, and the like. It has an output device 104 capable of outputting a signal. This configuration is the same in the second embodiment described later.

The control logic component specification setting unit 13, the common processing search unit 15, the variable processing search unit 16, and the feature model generation unit 17 shown in FIG. 1 are operated by the CPU 101 using a program which is an example of the information stored in the storage device 102. It will be realized.
Further, the control logic component DB 11 and the control logic diagram DB 14 are realized by the storage device 102.
Further, the input of the control logic component to the control logic component DB 11 and the input of the control logic diagram to the control logic diagram DB 14 are realized by the input device 103. The feature model display unit 18 is realized by the output device 104.
The hardware configuration for realizing the control logic diagram analysis device 10 is not limited to a PC, and may be, for example, a general computer.

FIG. 3 is a diagram showing an example of a control logic diagram stored in the control logic diagram DB of the control logic diagram analysis device according to the first embodiment.
In FIG. 3, logical operators are indicated by MIL logical symbols and the like. Equipment 50 such as control right switching device and remote control device, processing 51 such as interlock and minor failure, connection of input / output signal and output signal between them is indicated by connection line 52, and signal direction is indicated by arrow. Has been done. If the signal branches, it is indicated using a branch point 56.
The logical operators include, for example, a logical sum operator 53, a logical product operator 54, a negative operator 55, and the like, and an exclusive logical sum operator and the like.

The control logic diagram according to the first embodiment is not limited to the example of FIG. 3, and is for processing such as an FBD (Funkion Block Diagram) language or an SFC (Sequential Function Chart) language defined by IEC 61131-3. Anything shown in a notation that understands the relationship between input and output signals and logical operators may be used.

FIG. 4 is a diagram showing an example of a feature model input from the feature model generation unit of the control logic diagram analysis device according to the first embodiment.
In FIG. 4, the feature 61 is a feature such as a function and a performance provided by the target product or the target plant. A feature model is a tree-structured representation of the relationships between features in a target product or plant.
In the parent-child relationship of features, when a black circle 62 is attached to the child feature side, it indicates that the child feature is indispensable for the parent feature. Similarly, when a white circle 63 is attached to the child feature side, it indicates that the child feature is an option for the parent feature.
Also, if there is a curve 64 between one parent and two child features, it indicates that the child features are substitutable for the parent features.

In FIG. 4, the sewage treatment system includes "pump control" and "valve control" as functions, and "pump control" is specifically an essential function "pump ON / OFF control" and an optional function. It shows that it consists of an "interlock" function and a "remote monitoring" function.
Further, it is defined that the "alarm requirement" of "pump control" is indispensable, and this "alarm requirement" is a non-functional requirement described later in FIG. In FIG. 4, the “alarm requirement” indicates that either “alarm generation when a failure occurs” or “no alarm generation” is indispensable.

FIG. 5 is a diagram showing an example of component specifications set by the control logic component specification setting unit of the control logic diagram analysis device according to the first embodiment.
In FIG. 5, the control logic component is provided with a control logic component ID that uniquely identifies the control logic component, a control logic component name, a functional requirement indicating the function of the component, and a non-functional requirement indicating the performance or security of the component. Correspond.
This makes it possible to grasp the functional requirements and non-functional requirements of each control logic component.
The control logic component specifications are not limited to the example shown in FIG. 5, and for example, non-functional requirements may be described by mathematical formulas or logical formulas. Further, the non-functional requirements set for each component are not limited to one, and a plurality of non-functional requirements may be set.

FIG. 8 is a diagram showing an example of a method of storing a portion where a control logic component appears in the operation of the common processing search unit of the control logic diagram analysis device according to the first embodiment.
FIG. 8 shows an example of a method of storing a portion where a control logic component appears in step ST601 in the flowchart of FIG. 7 showing the operation of the common processing search unit 15 described later. In this process, how a plurality of control logic components are related is stored.

FIG. 8A shows “Pattern 1: Series”, indicating that the output of component 1 is the input of component 2.
FIG. 8B shows “Pattern 2: Series (indirect)”, in which the output of the component 1 is the input of the component 2, but the non-component portion that is not the control logic component is processed during that time. Is shown.
FIG. 8C shows “Pattern 3: Parallel”, indicating that the output of component 1 and component 2 is the input of component 3.
FIG. 8D shows "Pattern 4: Parallel (indirect) A", and the outputs of the parts 1 and 2 are the inputs of the parts 3, but there is a non-part part between the parts 1 and 3. Indicates that processing is to be performed.
FIG. 8 (e) shows "Pattern 5: Parallel (indirect) B", and the outputs of the parts 1 and 2 are the inputs of the parts 3, but there is a non-part part between the parts 2 and 3. Indicates that processing is to be performed.
FIG. 8 (f) shows "Pattern 6: Parallel (indirect) C", and the outputs of the parts 1 and 2 are the inputs of the parts 3, but between the parts 1 and 3 and between the parts 2 and the parts 3. Indicates that the processing of non-part parts is performed.

FIG. 12 is a diagram showing a specific example of a method of setting a parent-child relationship between features from the arrangement of parts of the feature model generation unit of the control logic diagram analysis device according to the first embodiment.
FIG. 12 shows a specific example of a method of setting a parent-child relationship between features from the arrangement of parts performed in step ST821 of FIG. 11, which will be described later, and shows patterns 1, pattern 2, and pattern 3 of the arrangement between parts of FIG. Describes the details of.
12 (a) shows the case of "pattern 1: series", FIG. 12 (b) shows the case of "pattern 2: series (indirect)", and FIG. 12 (c) shows the case of "pattern 3: parallel". The parent-child relationship between features is shown on the right side of the figure.

FIG. 14 is a diagram showing an example of generating features of non-functional requirements of the feature model generation unit of the control logic diagram analysis device according to the first embodiment.
FIG. 14 shows an example of generating features of non-functional requirements according to step ST801 of FIG. 10 described later.
In FIG. 14, the non-functional requirement N is acquired from the non-functional requirement 1 of the component 2, and is set as a child feature (required) of the feature “function of component 2”.

Next, the operation will be described.
First, the operation of the control logic component specification setting unit 13 will be described with reference to FIG.
In step ST500, the control logic component specification setting unit 13 acquires a component for which component specifications are not set from the control logic component DB 11 and moves to step ST501.

In step ST501, the component ID and name of the control logic component are associated with the functional requirements and non-functional requirements input by the control logic component specification input unit 12, stored in the control logic component DB 11, and moved to step ST502. ..

In step ST502, it is determined whether or not the component specifications are set for all the control logic components in the control logic component DB 11. If it is set, the process ends, and if it is not set, the process proceeds to step ST500.

Next, the operation (first step) of the common processing search unit 15 will be described with reference to FIG. 7.
In step ST600, the common processing search unit 15 acquires one control logic component from the control logic component DB 11 and moves to step ST601.
In step ST601, the control logic component acquired in step ST600 searches for and stores the location where the component appears in the control logic diagram in the control logic diagram DB 14, and moves to step ST602.

In step ST602, it is determined whether or not the processing of step ST601 has been completed for all the control logic components. That is, the corresponding control logic diagram component is searched for all the control logic components, and it is determined whether or not the corresponding control logic diagram component is stored.
For all control logic components, if it is finished, it ends, and if it is not finished, it moves to step ST600.

FIG. 8 shows an example of a method of storing the location where the control logic component appears in the operation of the common processing search unit 15. In any of the patterns of FIGS. 8 (a) to 8 (f), how the plurality of parts are related is stored by this processing.
Here, the control logic component becomes a common process.

Next, the operation (second step) of the variable processing search unit 16 will be described with reference to FIG.
In step ST700, the variable processing search unit 16 acquires one non-part part at the appearance location of the control logic component stored in step ST601 by the common processing search unit 15 and moves to step ST701.
In step ST701, a part similar to the non-part part acquired in step ST700 is searched from the control logic diagram in the control logic diagram DB14, and the process proceeds to step ST703.

In step ST703, when a part similar to a non-part part appears more than a certain amount, a new control logic part is used, and the part specification input by the control logic part specification input unit 12 is passed to the control logic part specification setting unit 13, and step ST704 Move to. The control logic component specification setting unit 13 stores the control logic component in the control logic component DB 11 as a control logic component.
Here, non-part parts where the number of similar parts is less than a certain number are subjected to variable processing.
In step ST704, it is determined whether or not all the non-part parts have been acquired. If it has been acquired, it ends, and if it has not been acquired, the process proceeds to step ST700.

Next, the operation (third step) of the feature model generation unit 17 will be described with reference to FIG.
The feature model generation unit 17 performs inter-component setting processing in step ST800 and moves to step ST801.
In step ST801, the non-functional requirement setting process is performed, and the process proceeds to step ST802.
In step ST802, the inter-parts connection process is performed and the process ends.
Details of each process will be described later.

Next, the details of the inter-parts setting process in step ST800 of FIG. 10 will be described with reference to FIG.
In step ST820, the sequence between the parts stored in step ST601 is acquired, and the process proceeds to step ST821.
In step ST821, the parent-child relationship between the features is set from the arrangement of parts, and the process proceeds to step ST822.
In step ST822, it is determined whether or not the arrangement of all the parts has been acquired. If it is acquired, it will end. If it has not been acquired, the process proceeds to step ST820.

A specific example of a method of setting a parent-child relationship between features from the arrangement of parts performed in step ST821 is as shown in FIG.
That is, FIG. 12A shows the case of "Pattern 1: Series", and since the output of the component 1 is the input of the component 2, the feature "function of the component 1" is the feature "function of the component 2". It is considered essential for. Therefore, the relationship between the features as shown on the right in FIG. 12A is derived.

FIG. 12B shows the case of "Pattern 2: Series (indirect)", and when non-part parts appear between parts 1 and part 2 at a frequency of a certain level or less, the non-part parts are considered to be optional. As shown on the right side of FIG. 12B, the feature "function of component 1" is indispensable for the feature "function of component 2", and the feature "function of non-component part" is optional.
In addition, when non-part parts appear between part 1 and part 2 more frequently than a certain frequency, the feature "function of part 1" and the feature "function of non-part part" are used for the feature "function of part 2". Become mandatory.

FIG. 12 (c) shows the case of "pattern 3: parallel", and since the outputs of the component 1 and the component 2 are the inputs of the component 3, as shown on the right of FIG. 12 (c), the feature "function of the component 3" is shown. The feature "function of component 1" and the feature "function of component 2" are indispensable.

Next, the details of the non-functional requirement setting process in step ST801 in FIG. 10 showing the operation of the feature model generation unit 17 will be described with reference to FIG.
In step ST850, the non-functional requirements of the control logic component corresponding to the feature are acquired and the process proceeds to step ST851.
In step ST851, a feature for the non-functional requirement is generated, registered as a child (required) feature of the feature in step ST850, and moved to step ST852.
In step ST852, it is determined whether or not all the features have been acquired. If it has been acquired, it ends, and if it has not been acquired, it moves to step ST850.

FIG. 14 shows an example of generating features with non-functional requirements according to step ST801. The non-functional requirement N is acquired from the non-functional requirement 1 of the component 2, and is set as a child feature (required) of the feature "function of the component 2".

Next, the details of the inter-component connection processing in step ST802 in FIG. 10 showing the operation of the feature model generation unit 17 will be described with reference to FIG.
In step ST900, the relationship settings between the parts are recursively set, the entire feature model is generated, and the process ends.

According to the first embodiment, the common processing between a plurality of plants and the variable processing for each plant can be extracted as a feature model from the usage status of the control logic components in the existing control logic diagram asset. Product line development can be realized.
As a result, the control logic diagram can be appropriately derived and created, and the system construction cost of system development using the control logic diagram can be reduced.

Embodiment 2.
FIG. 16 is a block diagram showing a schematic configuration of the control logic diagram analysis device according to the second embodiment.
In FIG. 16, reference numerals 10 to 18 are the same as those in FIG. In FIG. 16, the control logic diagram analysis device 10 is provided with a layered control logic diagram analysis rule generation unit 31 that generates a layered control logic diagram analysis rule. The layered control logic diagram analysis rule is a rule for analyzing a control logic diagram and extracting control logic components suitable for use.

FIG. 18 is a diagram showing an example of a layered control logic diagram analysis rule generated by the layered control logic diagram analysis rule generation unit of the control logic diagram analysis device according to the second embodiment.
FIG. 18A shows the Basic processing rule No. It is a figure which shows 1.
FIG. 18B shows the precondition rule No. It is a figure which shows 1.
FIG. 18C shows the remote monitoring function rule No. It is a figure which shows 1.
In FIG. 18, three control logic diagram analysis rules of FIGS. 18A to 18C are shown. The control logic diagram analysis rule is composed of a process component 80 and a logic operator component. The logical operator component includes a logical AND operator component 81, a negative operator component 82, a logical sum operator component 83, and the like.
The control logic diagram analysis rule is a rule for analyzing the control logic diagram and extracting the control logic component, and each rule has a parent-child relationship and is layered.

Next, the operation will be described.
The layered control logic diagram analysis rule can extract similar control logic components with high reusability from the control logic diagram to be analyzed when creating the control logic diagram.
The user can use not only the highly reusable control logic components but also the plant-specific processing associated therewith, and can efficiently create the control logic diagram.
In the second embodiment, the layered control logic diagram analysis rule generation unit 31 is provided to efficiently create the layered control logic diagram analysis rule.

Next, the operation (fourth step) of the layered control logic diagram analysis rule generation unit 31 will be described with reference to FIG.
In step ST1000, the feature model generated by the feature model generation unit 17 is acquired and moved to step ST1001.
In step ST1001, the tree structure indicated by the feature model is traced from the leaves to the roots, the control logic components corresponding to each feature are combined, and the process proceeds to step ST1002.
In step ST1002, it is determined whether or not the feature acquired in step ST1001 is an optional feature, and if it is an option, it is determined that the control logic component corresponding to the feature is variable processing, and the process ends.
At this time, the combined control logic components become a layered control logic diagram analysis rule.

A layered control logic diagram An example of a layered control logic diagram analysis rule generated by the analysis rule generation unit 31 is shown in FIG.
The layered control logic diagram analysis rule is a rule for analyzing the control logic diagram and extracting the control logic component, and each control logic diagram analysis rule of FIGS. 18 (a) to 18 (c) has a parent-child relationship. have.
That is, the remote monitoring function rule No. 1 in FIG. 18 (c). The specific processing of No. 1 is described in the Basic processing rule No. 1 of FIG. 18A. It is defined in No. 1 and the Basic processing rule No. The precondition of 1 is the precondition rule No. 1 of FIG. 18 (b). It is defined in 1.
The relationship between such rules is expressed in a hierarchical structure. For example, the remote monitoring function rule No. 1 in FIG. 18 (c). The specific processing of 1 is referred to by another rule, for example, Basic processing rule No. By switching to 2, etc., the control logic diagram can be analyzed flexibly.

According to the second embodiment, with the above configuration, it is possible to generate a layered control logic diagram analysis rule necessary for extracting highly reusable control logic components from the control logic diagram, and control the control. The logic diagram creation cost can be reduced.

Although the present disclosure describes various exemplary embodiments and examples, the various features, embodiments, and functions described in one or more embodiments are those of a particular embodiment. It is not limited to application, but can be applied to embodiments alone or in various combinations.
Therefore, innumerable variations not illustrated are envisioned within the scope of the techniques disclosed herein. For example, it is assumed that at least one component is modified, added or omitted, and further, at least one component is extracted and combined with the components of other embodiments.

10 Control logic diagram analyzer, 11 Control logic component DB,
12 Control logic component specification input section, 13 Control logic component specification setting section,
14 Control logic diagram DB, 15 Common processing search unit, 16 Variable processing search unit,
17 feature model generator, 18 feature model display,
31 Hierarchical control logic diagram Analysis rule generator, 50 equipment, 51 processing,
52 connection line, 53 OR operator, 54 AND operator, 55 negation operator,
56 branch points, 61 features, 62 black circles, 63 white circles, 64 curves,
80 process parts, 81 AND operator parts, 82 negative operator parts,
83 OR operator component, 100 PC, 101 CPU, 102 storage device,
103 input device, 104 output device

Claims (5)

Control logic diagram database that stores control logic diagrams for controlling the plant,
A control logic component database that stores common processes commonly used by a plurality of plants as control logic components for creating the control logic diagram.
A common process search unit that searches for the parts used in the control logic diagram of the control logic diagram database for the control logic component of the control logic component database, and searches for the common process.
A variable processing search unit that searches the control logic diagram for variable processing that changes for each plant based on the search results of this common processing search unit.
It is provided with a feature model generation unit that generates a feature model that defines the relationship between these processes based on the common process searched by the common process search unit and the variable process searched by the variable process search unit. A featured control logic diagram analyzer. The control logic diagram analysis device according to claim 1, further comprising a feature model display unit that displays a feature model generated by the feature model generation unit. Layered control logic diagram analysis rule generation that generates a layered control logic diagram analysis rule for searching control logic components that can be used to create a new control logic diagram from the above control logic diagram database based on the above feature model. The control logic diagram analysis device according to claim 1 or 2, further comprising a unit. Regarding the control logic components used to create the control logic diagram for controlling the plant, the common processing search unit searches for the parts used in the control logic diagram of the control logic diagram database, and searches for the parts used in the control logic diagram of the control logic diagram database, and searches for the parts used in the control logic diagram, and a plurality of the above plants. The first step in searching for common processing that is commonly used in
The second step, in which the variable processing search unit searches the control logic diagram for variable processing that changes for each plant based on the search results obtained in the first step.
Based on the common process searched by the first step and the variable process searched by the second step, the feature model generator generates a third feature model that defines the relationship between these processes. A control logic diagram analysis method characterized by including steps. The layered control logic diagram analysis rule generation unit uses the layered control logic diagram analysis rule for searching the control logic components that can be used to create a new control logic diagram from the control logic diagram database in the above feature model. The control logic diagram analysis method according to claim 4, wherein a fourth step of generation is included.

Images