Information processing method, information processing device, and program

Abstract

To provide an information processing method, an information processing device, and a program capable of supporting creation of data related to an apparatus.SOLUTION: An information processing method according to the embodiment includes creating, on the basis of a meta model located in a first layer where containment relationship and reference relationship between a plurality of types of information models located in a second layer are defined, a guide tree that represents the relationship between the information models. The information model defines data items related to an apparatus. The guide tree indicates that a higher-level first information model, whose relationship is expressed in the guide tree, can use a data item defined in a lower-level second information model.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Embodiments of the present invention relate to an information processing method, an information processing apparatus, and a program.

Background Art

[0002] In recent years, for example, in order to realize a digital twin of a device utilizing IoT (Internet of Things), it has been considered to use an Asset Administration Shell proposed in Industry 4.0. Here, an asset refers to, for example, a device (physical device) existing in the real world, and data related to the device is managed in the Asset Administration Shell.

[0003] The data related to the above-described device can be created using the AASX Package Explorer provided as open source software (OSS), but it is not easy to create such data.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem to be solved by the present invention is to provide an information processing method, an information processing apparatus, and a program capable of creating a useful guide tree for creating data related to a device.

Means for Solving the Problems

[0006] The information processing method according to the embodiment is a metamodel located in the first layer, in which inclusion relationships and reference relationships between a plurality of types of information models located in the second layer are defined. The information processing device, which has a database that stores the information, executes the information processing method, which includes obtaining the metamodel from the database and the obtained metamodel Based on this, the system includes creating a guide tree that represents the relationships between the information models. Creating the guide tree includes extracting first and second information models in which an inclusion relationship is defined in the metamodel; if the first information model inclusively includes the second information model, placing the first information model as the higher-level model and the second information model as the lower-level model in the guide tree; extracting third and fourth information models in which a reference relationship is defined in the metamodel; and if the third information model references the fourth information model, placing the third information model as the source and the fourth information model as the destination in the guide tree. The information models define data items related to the equipment. The guide tree is, The aforementioned The first information model The aforementioned This indicates that the data items defined in the second information model are available. [Brief explanation of the drawing]

[0007] [Figure 1] A block diagram showing an example of the functional configuration of the information processing device according to the embodiment. [Figure 2] A diagram showing an example of the hardware configuration of an information processing device. [Figure 3] A flowchart illustrating an example of the processing procedure for an information processing device. [Figure 4] A diagram showing an example of a guide tree. [Figure 5] A diagram showing an example of an AAS definition table. [Figure 6] A diagram showing an example of a submodel definition table. [Figure 7] This diagram shows an example of a state where data has been set in the AAS definition table. [Figure 8] This diagram shows an example of a state where data has been set in the Submodel definition table. [Figure 9] A diagram showing an example of a submodel graph. [Figure 10] A diagram showing an example of a model tree. [Figure 11] A diagram showing an example of an instance data definition table. [Figure 12] A diagram showing an example of an instance data tree. [Figure 13] A diagram showing an example of the output settings screen. [Modes for carrying out the invention]

[0008] The embodiments will be described below with reference to the drawings. The information processing device according to this embodiment is an electronic device used, for example, to utilize the asset management shell proposed in Industry 4.0. The asset management shell corresponds to a mechanism for creating and storing (managing) data (data related to the equipment) to realize a digital twin of the equipment. In this embodiment, the assets are assumed to be equipment (physical equipment) that exists in the real world, but such assets may also include facilities, people, and systems.

[0009] Here, if we define the data handled in the asset management shell as AAS data, then this AAS data includes the AAS metamodel located in the M2 layer, the AAS model located in the M1 layer, and the AAS instance data located in the M0 layer. In this embodiment, the AAS metamodel is fixed data defined by international standards, and the AAS model and AAS instance data correspond to the data related to the equipment described above.

[0010] The AAS metamodel corresponds to data that defines how to describe data related to equipment (data structure, relationships, format, and style, etc.). Specifically, the AAS metamodel defines the inclusion and reference relationships between multiple types of AAS models.

[0011] The AAS model corresponds to data such as data items of data related to devices and correlations with other AAS models. When the device is, for example, a storage battery managed in a HEMS (Home Energy Management System), the AAS model defines data items such as catalog information (model number, manufacturer, device number, etc.), operating status, measured current (A), and CO2 emissions of the storage battery.

[0012] AAS instance data corresponds to the data of the data items defined in the AAS model. When the data item of the catalog information of the storage battery is defined in the above AAS model, the data of the data item of the catalog information of the storage battery is the catalog value of the storage battery. Also, when the data items of operating status, measured current, and CO2 emissions are defined in the above AAS model, the data of the data items of operating status, measured current, and CO2 emissions are, for example, "ON", "5A", and "50tCO2 / GJ", etc.

[0013] The information processing apparatus according to the present embodiment has a function of assisting in creating, for example, an AAS model corresponding to the data related to the above devices.

[0014] FIG. 1 is a block diagram showing an example of the functional configuration of the information processing apparatus according to the present embodiment. As shown in FIG. 1, the information processing apparatus 10 includes a database (DB) 11, a tree creation unit 12, a definition table creation unit 13, an input / output unit 14, a graph creation unit 15, and a recommendation processing unit 16.

[0015] The database 11 stores AAS data and the like handled in the above asset management shell. The AAS metamodel, which is fixed data, is assumed to be stored in the database 11 in advance.

[0016] The tree creation unit 12 creates a guide tree representing the relationship (correlation) between the AAS models based on the inclusion relationship and reference relationship between multiple types of AAS models defined in the AAS metamodel stored in the database 11.

[0017] The definition table creation unit 13 creates a definition table for setting, for example, the attributes of the AAS model and the data items defined in the AAS model, based on the guide tree created by the AAS metamodel and the tree creation unit 12.

[0018] The input / output unit 14 outputs the guide tree created by the tree creation unit 12 and the definition table created by the definition table creation unit 13. Furthermore, the input / output unit 14 inputs the data set for the definition table. The data input by the input / output unit 14 (hereinafter referred to as input data) is stored in the database 11.

[0019] Here, the AAS model described above includes multiple submodels in the asset management shell. In this case, the definition table described above is set with data items defined for each of the multiple submodels. In other words, the input data stored in database 11 includes data items defined for each of the multiple submodels.

[0020] The graph creation unit 15 retrieves data items defined for each of the above-mentioned submodels from the database 11 (input data stored therein), and creates a Submodel graph that includes nodes representing each of the above-mentioned submodels and links representing the relationships between the submodels.

[0021] The recommendation processing unit 16 uses the above-mentioned input data and the Submodel graph created by the graph creation unit 15 to perform a process of recommending data (or candidates for data) that should be set in the definition table created by the definition table creation unit 13.

[0022] Figure 2 shows an example of the hardware configuration of the information processing device 10. As shown in Figure 2, the information processing device 10 includes a CPU 101, non-volatile memory 102, main memory 103, and communication device 104, etc.

[0023] The CPU 101 is a hardware processor that controls the operation of each component within the information processing device 10. The CPU 101 executes various programs that are loaded from the non-volatile memory 102, which is a storage device, into the main memory 103. The programs executed by the CPU 101 include the operating system (OS) and programs that assist in creating data related to the above-mentioned devices (hereinafter referred to as information processing programs).

[0024] The communication device 104 is a device configured to perform communication with an external device, for example, by wire or wireless connection.

[0025] Although only the non-volatile memory 102 and main memory 103 are shown in Figure 2, the information processing device 10 may further include other storage devices such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive). The information processing device 10 may also further include input devices such as a mouse and a keyboard, and a display device such as a display.

[0026] In this embodiment, the database 11 shown in Figure 1 is implemented by the non-volatile memory 102 or other storage device shown in Figure 2.

[0027] Furthermore, in this embodiment, some or all of the tree creation unit 12, definition table creation unit 13, input / output unit 14, graph creation unit 15, and recommendation processing unit 16 shown in Figure 1 are implemented by having the CPU 101 shown in Figure 2 execute an information processing program, that is, by software. Some or all of these units 12-16 may be implemented by hardware such as an IC (Integrated Circuit), or by a combination of software and hardware.

[0028] The following describes an example of the processing procedure of the information processing device 10, referring to the flowchart in Figure 3.

[0029] The process shown in Figure 3 can be executed at a time specified by, for example, the user of the information processing device 10 (the creator of the data related to the device), but it may also be executed at other times.

[0030] Furthermore, the information processing device 10 according to this embodiment may be implemented as, for example, a user terminal used by a user, or as a server device that is communicatively connected to the user terminal.

[0031] First, the tree creation unit 12 retrieves the AAS metamodel stored in the database 11 (step S1).

[0032] Next, the tree creation unit 12 uses the inclusion relationships (has-a relationships) and reference relationships between multiple types of AAS models defined in the AAS metamodel obtained in step S1 to create a guide tree representing the relationships between AAS models (information models of the M1 layer) (step S2).

[0033] Here, Figure 4 shows an example of a guide tree created in step S2. Here, the AAS metamodel can include multiple types of AAS models (i.e., AAS models located in the M1 layer) with defined inclusion and reference relationships, such as the AAS, Asset, Submodel, ConceptDescription, and SubmodelElement in the asset management shell.

[0034] Mark 201 in the guide tree 200 shown in Figure 4 indicates the inclusion relationships between AAS models. Specifically, the guide tree 200 shown in Figure 4 indicates that AAS is an inclusion of Asset, Submodel, and ConceptDescription, and that Submodel is an inclusion of SubmodelElement. In this case, AAS is a higher-level model of Asset, Submodel, and ConceptDescription, and Submodel is a higher-level model of SubmodelElement. In other words, Asset, Submodel, and ConceptDescription are lower-level models of AAS, and SubmodelElement is a lower-level model of Submodel.

[0035] Furthermore, the guide tree 200 also represents the relationship in which a higher-level model (higher-level information model) whose inclusion relationship is shown in the guide tree 200 can utilize data items defined in a lower-level model (lower-level information model).

[0036] The arrow 202 in the guide tree 200 shown in Figure 4 indicates the reference relationship between AAS models. According to the guide tree 200 shown in Figure 4, it is shown that the Submodel references the Asset.

[0037] In Figure 4, as described above, it is assumed that the multiple types of AAS models located in the M1 layer are AAS, Asset, Submodel, ConceptDescription, and SubmodelElement. However, the AAS model may also include other models such as Property.

[0038] Returning to Figure 3, the definition table creation unit 13 creates a definition table for each of the multiple types of AAS models located in the M1 layer, based on the AAS metamodel acquired in step S1 and the guide tree created in step S2 (step S3).

[0039] Now, with reference to Figures 5 and 6, we will explain the definition table created in step S3.

[0040] Figure 5 shows an example of a definition table (hereinafter referred to as the AAS definition table) created for one of several types of AAS models.

[0041] As shown in Figure 5, the AAS definition table is configured to allow setting of id, idShort, AAS / Asset, Submodel, and data items (ConceptDescription / SubmodelElement).

[0042] `id` is an identifier used to identify an AAS. `idShort` corresponds to the name of the AAS identified by `id`. `AAS / Asset` is an AAS or Asset that is a subordinate model of the AAS identified by `id`. `Submodel` is a Submodel that is a subordinate model of the AAS identified by `id`. `DataItem` is a data item defined in the AAS (or its subordinate model, ConceptDescription / SubmodelElement) identified by `id` (a data item used in that AAS).

[0043] The AAS definition table shown in Figure 5 is used to create an AAS. In other words, an AAS is created based on the data set in the AAS definition table (the settings in the AAS definition table).

[0044] In the AAS definition table shown in Figure 5, id and idShort correspond to AAS attributes and are defined in the AAS metamodel. Furthermore, the AAS / Asset, Submodel, and data items (ConceptDescription / SubmodelElement) in the AAS definition table shown in Figure 5 are identified based on the inclusion relationships shown in the guide tree. In other words, the AAS definition table can be said to be a table containing two types of columns based on the AAS metamodel and the guide tree. The definition table shown in Figure 5 is an example, and the columns of the definition table consist of the two types of data (AAS model and guide tree) described above, depending on the embodiment.

[0045] Figure 6 shows an example of a definition table (hereinafter referred to as the Submodel definition table) created for a Submodel among several types of AAS models.

[0046] As shown in Figure 6, the Submodel definition table is configured to allow setting of id, idShort, and data items (SubmodelElement).

[0047] The ID is an identifier used to identify a Submodel. `idShort` corresponds to the name of the Submodel identified by the ID. Data items are data items defined in the Submodel (or its submodel element) identified by the ID (data items used in that Submodel).

[0048] The Submodel definition table shown in Figure 6 is used to create Submodels. In other words, Submodels are created based on the data set in the Submodel definition table (the settings in the Submodel definition table).

[0049] In the Submodel definition table shown in Figure 6, `id` and `idShort` correspond to attributes of the Submodel and are defined in the AAS metamodel. Furthermore, the data items (SubmodelElement) in the Submodel definition table shown in Figure 6 are identified based on the inclusion relationships shown in the guide tree. In other words, the Submodel definition table, like the AAS definition table described above, is a table that contains two types of columns based on the AAS metamodel and the guide tree.

[0050] Here, we have explained the AAS definition table and the Submodel definition table, but in step S3, as described above, definition tables for each of the multiple types of AAS models are created.

[0051] Returning to Figure 3, the input / output unit 14 outputs the guide tree created in step S2 and the definition tables (AAS definition table and Submodel definition table, etc.) created in step S3 (step S4). The guide tree and definition tables output in step S4 are displayed, for example, on a display.

[0052] In this case, the user can set various data for the definition table while checking the relationships (inclusion and reference relationships) between multiple types of AAS models located in the M1 layer of the asset management shell by referring to the guide tree.

[0053] Figure 7 shows an example of the state in which data has been set (input) into the AAS definition table shown in Figure 5 above. Figure 8 shows an example of the state in which data has been set (input) into the Submodel definition table shown in Figure 6 above.

[0054] Note that the data items defined in AAS include the data items defined in the Submodel, which is a lower-level model of the AAS. Therefore, the data items set in the AAS definition table (i.e., the data items defined in AAS) may be automatically set using the data items set in the definition table of the Submodel, which is a lower-level model of the AAS (i.e., the data items defined in the Submodel).

[0055] As described above, the data set in the definition table is input by the input / output unit 14 (step S5). The data entered in step S5 (input data) is stored in the database 11. The input data includes, for example, the data set in the AAS definition table and the data set in the Submodel definition table.

[0056] Next, the graph creation unit 15 creates a submodel graph based on the input data stored in the database 11 (step S6).

[0057] The following describes the process of step S6 in detail. First, the graph creation unit 15 adds nodes representing each of the multiple submodels to the submodel graph (format) based on the data set in the Submodel (column) of the AAS definition table described above.

[0058] Next, the graph creation unit 15 determines, based on the data set in the data items (columns) of the Submodel definition table described above (i.e., the data items defined in the Submodel), whether a common data item is defined for each combination of two nodes included in the Submodel graph that represents the two Submodels represented by those two nodes. The graph creation unit 15 adds a link (edge) to the Submodel graph that connects the two nodes representing the two Submodels that have been determined to have a common data item defined.

[0059] Furthermore, the graph creation unit 15 may create graphs using dependencies between data items (for example, measured values ​​and temperature at the time of measurement) rather than common data items.

[0060] As a result, the graph creation unit 15 can create a submodel graph that includes nodes representing each of the multiple submodels and links representing the relationships between the submodels.

[0061] Here, Figure 9 shows an example of a Submodel graph created in step S6.

[0062] In the Submodel graph 300 shown in Figure 9, nodes 301-304 representing Submodels "SM_1", "SM_3", "SM_4", and "SM_5" have been added. Submodel "SM_1" is a Submodel with the id "SM001" and idShort "SM_1". A detailed explanation is omitted, but the same applies to the other Submodels "SM_3", "SM_4", and "SM_5".

[0063] Furthermore, in the Submodel graph 300, nodes 301 and 303 are connected by link 305. This indicates that data items common to Submodels "SM_1" and "SM_4" are defined. In addition, {data items 1, 2} are attached near link 305. This indicates that data item 1 and data item 2 are common data items for Submodels "SM_1" and "SM_4".

[0064] Furthermore, in the Submodel graph 300, nodes 303 and 304 are connected by link 306. This indicates that data items common to Submodels "SM_4" and "SM_5" are defined. In addition, {data items 3, 4, 5, 6} are attached near link 306. This indicates that the data items common to Submodels "SM_4" and "SM_5" are data items 3, 4, 5, and 6.

[0065] Furthermore, in the Submodel graph 300, nodes 302 and 304 are connected by link 307. This indicates that a common data item is defined for Submodels "SM_3" and "SM_5". Note that {data item 6} is attached near link 307. This indicates that data item 6 is the common data item for Submodels "SM_3" and "SM_5".

[0066] Furthermore, in the Submodel graph 300, nodes 302 and 303 are connected by link 308. This indicates that a common data item is defined for Submodels "SM_3" and "SM_4". Additionally, {data item 6} is attached near link 308. This indicates that data item 6 is the common data item for Submodels "SM_3" and "SM_4".

[0067] In the example shown in Figure 9, a common data item is added to the vicinity of each link, representing the two submodels represented by the two nodes connected by that link. However, the number of such common data items may also be added to the vicinity of the link. The number of such common data items can be used, for example, as a weight for the relationship between the two submodels.

[0068] In Figure 9, a portion of the Submodel graph created based on the data set in the AAS definition table shown in Figure 7 and the data set in the Submodel definition table shown in Figure 8 is shown, while the Submodels "SM_2" and "SM_6" shown in Figures 7 and 8 are omitted.

[0069] Returning to Figure 3, the recommendation processing unit 16 identifies candidate data (hereinafter referred to as "candidate data") to be set in the definition table described above (for example, the AAS definition table) (step S7).

[0070] The following describes the process of step S7 in detail. In the AAS definition table output in step S4 described above, the user needs to set the id, idShort, AAS / Asset, Submodel, and data items (ConceptDescription / SubmodelElement).

[0071] Here, for example, if the settings for the Submodel definition table have been made by another user (i.e., reusing an already configured Submodel definition table), the user making the settings for the AAS definition table may be able to set the data items, for example, but may not have a full understanding of the settings for the Submodel definition table, making it difficult to set the Submodel in the AAS definition table according to those settings.

[0072] Therefore, in step S7, based on the data items set in the AAS definition table, a Submodel to be set in the AAS definition table is identified as a setting candidate (hereinafter referred to as the first setting candidate).

[0073] To explain in detail using Figure 8, for example, if data item 1 is set in a data item (column) of the AAS definition table, the recommendation processing unit 16 identifies the Submodels "SM_1" and "SM_4", etc., in which data item 1 is defined, as first setting candidates based on the data set in the Submodel definition table.

[0074] On the other hand, if, for example, data item 6 is set in a data item (column) of the AAS definition table, the recommendation processing unit 16 identifies the Submodels "SM_3", "SM_4", and "SM_5", etc., in which data item 6 is defined, as first setting candidates based on the data set in the Submodel definition table.

[0075] Note that the AAS definition table may contain one or more data items (i.e., data items used to identify candidate settings).

[0076] Here, we have described identifying potential settings based on the data items set in the AAS definition table, but these potential settings may also be identified based on the Submodel graph.

[0077] In this case, the recommendation processing unit 16 can identify, for example, the Submodel identified as the first setting candidate and the Submodel whose relationship is shown in the Submodel graph (related submodel) as setting candidates (hereinafter referred to as the second setting candidate).

[0078] To explain this in more detail using Figure 9, for example, if Submodel "SM_1" is identified as the first configuration candidate, then Submodel "SM_4" (represented by node 303), which is connected to Submodel "SM_1" (represented by node 301) by link 305, is identified as the second configuration candidate.

[0079] Furthermore, if, for example, Submodel "SM_4" is identified as the first configuration candidate, then Submodel "SM_1" (represented by node 301), which is connected to Submodel "SM_4" (represented by node 303) by link 305, Submodel "SM_3" (represented by node 302), which is connected to Submodel "SM_4" by link 308, and Submodel "SM_5" (represented by node 304), which is connected to Submodel "SM_4" by link 306, are identified as second configuration candidates.

[0080] In this explanation, we have described identifying a Submodel that is related to the Submodel graph identified as the first candidate for setting as the second candidate for setting. However, for example, you could also identify a Submodel that is related to the Submodel graph set in the AAS definition table as a candidate for setting.

[0081] The configuration candidates identified in step S7 (a list including the Submodels identified as the first and second configuration candidates) are output by the input / output unit 14 (step S8). These output configuration candidates are then recommended to the user as Submodels (or candidates for Submodels) to be set in the AAS definition table, for example, by being displayed on a screen.

[0082] If the user instructs that the configuration candidates output in step S8 be set (reflected) in the AAS definition table, the configuration candidates (Submodels selected by the user) are set in the AAS definition table and input by the input / output unit 14. Here, it has been explained that the configuration candidates are set in the AAS definition table in response to user instructions, but the configuration candidates may also be set in the AAS definition table automatically.

[0083] Furthermore, to assist users in determining (selecting) the configuration candidates to be set in the AAS definition table, each of these configuration candidates (Submodels) may be assigned a priority (recommendation ranking). This priority is determined based on the number of common data items attached to the links in the Submodel graph described above (the weight of the relationship between the two Submodels). Specifically, for example, if Submodel "SM_4" is identified as the first recommended candidate, Submodels "SM_1", "SM_3", and "SM_5" will be identified as second recommended candidates. In this case, Submodel "SM_4" will be assigned the highest priority (hereinafter referred to as the first priority), Submodel "SM_5", which is connected via link 306 with 4 common data items, will be assigned a lower priority than the first priority (hereinafter referred to as the second priority), Submodel "SM_1", which is connected via link 305 with 2 common data items, will be assigned a lower priority than the second priority (hereinafter referred to as the third priority), and Submodel "SM_3", which is connected via link 308 with 1 common data item, will be assigned a lower priority than the third priority. Note that the priority order described here is just one example, and prioritization may be performed using other methods.

[0084] When the process in step S8 is executed, an AAS model is created based on the data (input data) set in the definition table (step S9). In this case, for example, an AAS is created based on the data set in the AAS definition table (settings for the AAS definition table), and a Submodel is created based on the data set in the Submodel definition table (settings for the Submodel definition table). Although AAS and Submodel have been explained here, the same applies to other AAS models.

[0085] Although the process in step S9 described above is assumed to be performed in the information processing device 10, the information processing device 10 only needs to be configured to support the creation of the AAS model, and the process in step S9 may be performed outside of the information processing device 10.

[0086] As described above, in this embodiment, a guide tree representing the relationships between AAS models (information models) is created based on the AAS metamodel located in the M2 layer (first layer), and a definition table is created to set the attributes of the AAS models (e.g., AAS and Submodel) and the data items defined in the AAS models based on the metamodel and guide tree. Furthermore, in this embodiment, the AAS models are automatically created based on the data set in the definition table created in this way (the settings for the definition table).

[0087] In this embodiment, the above-described configuration can support the creation of an AAS model (i.e., data related to the equipment).

[0088] In this embodiment, the definition table includes, for example, an AAS definition table (first definition table) and a Submodel definition table (second definition table).

[0089] In this case, a Submodel that defines the data items set in the AAS definition table can be recommended as the Submodel to be set in the AAS definition table.

[0090] In this embodiment, with this configuration, even if, for example, the user is unaware of which Submodel should be set in the AAS definition table, it is possible to support the creation of an AAS model (AAS) by reusing a Submodel in which data items have already been defined. In other words, in this embodiment, even users with little background knowledge of the asset management shell can easily create data related to equipment.

[0091] Furthermore, in this embodiment, a Submodel graph is created that includes nodes representing each of the multiple Submodels and links representing the relationships between the Submodels, based on the data items defined for each Submodel set in the Submodel definition table described above. In this embodiment, the Submodel graph may be configured to further recommend Submodels whose relationships with the recommended Submodels are represented by the links included in the created Submodel graph (related Submodels of the recommended Submodels). Alternatively, a related Submodel (second submodel) of a Submodel (first submodel) set in the AAS definition table may be recommended as a Submodel to be further set in the AAS definition table. In other words, this embodiment may be configured to further recommend Submodels to be set in the AAS definition table using a Submodel graph (commonality and dependencies of data items used by Submodels).

[0092] In this embodiment, the process shown in Figure 3 has been described as being performed, but some of the processes shown in Figure 3 may be omitted.

[0093] Specifically, the information processing device 10 according to this embodiment may operate, for example, simply to create and output (present to the user) a guide tree. The M1 layer is provided with various types of AAS models (AAS, Asset, Submodel, ConceptDescription, etc.), and there are mutual reference and inclusion relationships. Even if the configuration simply outputs a guide tree as described above, the user can understand the relationships between AAS models by referring to the guide tree and create the AAS model, thus supporting the creation of data (AAS model) related to the device. In other words, in this embodiment, processing other than the creation and output of the guide tree may be omitted.

[0094] Furthermore, the information processing device 10 according to this embodiment may also operate to create and output, for example, a guide tree and a definition table. With such a configuration, the user can easily create an AAS model simply by setting data in a flat format in the definition table while referring to the guide tree, thus supporting the creation of data related to the equipment. In other words, although this embodiment was described as recommending a Submodel to be set in the AAS definition table as a candidate, if the user can set all the data in the definition table (AAS definition table), the process related to such recommendation may be omitted.

[0095] Furthermore, although this embodiment describes the use of a Submodel graph to recommend Submodels to be set in the AAS definition table, the configuration may also be configured to output (present to the user) the Submodel graph. Generally, it is not possible to define relationships between Submodels when using the asset management shell, but as described above, with the configuration that outputs the Submodel graph, the user can easily understand the relationships between multiple Submodels by referring to the Submodel graph.

[0096] Furthermore, although this embodiment has been described as creating a guide tree based on an AAS metamodel, the tree creation unit 12 may be configured to create a model tree based on data set in the AAS definition table (such as the attributes of each AAS and the Submodel which is a subordinate model of each AAS).

[0097] Figure 10 shows an example of a model tree created based on data set in the AAS definition table shown in Figure 7. Mark 401 in the model tree 400 shown in Figure 10 indicates the inclusion relationship between AAS models. When such a model tree 400 is output (presented to the user), the user can confirm the relationships between AAS models based on the data set in the AAS definition table (i.e., the user's settings for the AAS definition table). The model tree is assumed to conform to the constraints of the relationships between AAS models represented by the guide tree described above.

[0098] Furthermore, although this embodiment has been mainly described as creating, for example, an AAS definition table and a Submodel definition table, and automatically creating an AAS and a Submodel based on the data set in the AAS definition table and Submodel definition table (i.e., supporting the creation of an AAS model as data related to the device), this embodiment may also be configured to support the creation of AAS instance data as data related to the device. In this case, the definition table creation unit 13 further creates a definition table (third definition table) on which data for data items defined in the AAS model can be set, for example, as shown in Figure 11. Figure 11 shows an example of a definition table (hereinafter referred to as the instance data definition table) for setting the data for each data item defined in the Submodel "SM_1". When such an instance data definition table is output and data is set in the instance data definition table by the user, the information processing device 10 can input the data and automatically create AAS instance data based on the data.

[0099] Alternatively, the tree creation unit 12 may create the instance data tree shown in Figure 12 by adding the data set in the instance data definition table described above (data for each data item) to the model tree shown in Figure 10. With such an instance data tree, the user can check the user's settings for the instance data definition table.

[0100] Although an instance data definition table is created for each AAS model, if the same data item is set (defined) in common across multiple AAS models, the data for that data item (AAS instance data) will also be common. For this reason, for example, data set in one instance data definition table among the multiple instance data definition tables created for each AAS model may be automatically set (i.e., reused) in the other instance data definition tables.

[0101] Specifically, as shown in Figure 8, for example, data item 1 and data item 2 defined in Submodel "SM_1" and Submodel "SM_4" are common to both. In this case, for example, when the data for data item 1 and data item 2 defined in Submodel "SM_1" is set in the instance data definition table, that data is automatically set in the instance data definition table as the data for data item 1 and data item 2 defined in Submodel "SM_4". By reusing the data for data item 1 and data item 2 defined in Submodel "SM_1" as the data for data item 1 and data item 2 defined in Submodel "SM_4", it becomes possible to reduce the effort required of users, such as setting data individually for each Submodel.

[0102] In other words, while AASSX Package Explorer generally requires creating AAS instance data item by item by tracing the structure of the AAS model, the instance data definition table described above makes it possible to simultaneously set (create) data for data items (AAS instance data) that are commonly defined across multiple AAS models, thereby improving the ease of creating such AAS instance data.

[0103] Incidentally, in this embodiment, for example, it is possible to automatically create an AAS based on the data set in the AAS definition table (the settings for the AAS definition table) and to automatically create a Submodel based on the data set in the Submodel definition table (the settings for the Submodel definition table). The AAS and Submodel created in this way (i.e., the AAS model) can be output for, for example, user verification. Here, we have described the AAS model, but the same applies to the automatically created AAS instance data.

[0104] In this case, the user can configure the output settings for the AAS model and AAS instance data described above via an output settings screen, for example, as shown in Figure 13. The output settings screen 500 shown in Figure 13 is provided with first to third areas 501 to 503.

[0105] Area 1, 501, is the area for selecting (specifying) the output format of AAS model and AAS instance data. In Area 1, 501, one of the following can be selected as the output format for AAS model and AAS instance data: "AAS JSON", "WBCSD PACT", and "IEC CDD". AAS JSON is an example of a data format compliant with the AAS metamodel. If "AAS JSON" is selected in Area 1, 501, the AAS model and AAS instance data will be output in AAS JSON format. If "WBCSD PACT" is selected in Area 1, 501, the AAS model and AAS instance data will be output in WBCSD PACT format. If "IEC CDD" is selected in Area 1, 501, the AAS model and AAS instance data will be output in IEC CDD format.

[0106] The second area 502 is an area for selecting (specifying) the output range for AAS models and AAS instance data. In the second area 502, one of the following can be selected: "M1 layer (first output range)" and "M1M0 layer (second output range)". If "M1 layer" is selected in the second area 502, the AAS models located in the M1 layer will be output. If "M1M0 layer" is selected in the second area 502, the AAS models located in the M1 layer and the AAS instance data located in the M0 layer will be output. Although not shown in Figure 13, there may be an additional "M0 layer" which outputs only AAS instance data.

[0107] Area 3, 503, is for selecting (specifying) whether or not to split the file when outputting the AAS model and AAS instance data to a file (i.e., whether or not to split the file). In Area 3, 503, you can select either "none" or "yes". If "none" is selected in Area 3, 503, the AAS model and AAS instance data will be output in a single file. If "yes" is selected in Area 3, 503, the AAS model and AAS instance data will be output in multiple files. Note that if the AAS model and AAS instance data are output in multiple files, for example, the AAS and Submodel may be output in different files.

[0108] With a configuration that allows users to specify (select) the output format, output range, and whether or not to split files for AAS model and AAS instance data via an output settings screen 500 as shown in Figure 13, users can improve the efficiency of verifying the automatically created AAS model and AAS instance data.

[0109] In this embodiment, a Submodel graph representing the relationships between Submodels has been described as being created. However, it is also possible to create an AAS graph that includes nodes representing AASs set in the AAS definition table and links representing the relationships between those AASs. Similarly, it is possible to create an Asset graph that includes nodes representing Assets set in the AAS definition table and links representing the relationships between those Assets. Since the AAS graph and Asset graph are similar to the Submodel graph except that the Submodels are AASs and Assets, a detailed explanation of the AAS graph and Asset graph will be omitted. Users can easily understand the relationships between multiple AASs and multiple Assets by referring to such AAS graphs and Asset graphs.

[0110] According to this embodiment as described above, users can simultaneously create multiple AAS models and AAS instance data (data related to devices) without considering the correlation between data, thereby improving the efficiency and ease of creating data related to such devices. Furthermore, the Submodel graphs and the like created in this embodiment can be shared as know-how in the asset management shell and used to improve data reusability.

[0111] Furthermore, since the information processing device 10 according to this embodiment can be used, for example, as part of a general-purpose mechanism for addressing the carbon footprint of equipment (products), it can promote the use of asset management shells for addressing such carbon footprints.

[0112] Although this embodiment has been described as utilizing an asset management shell, the information processing device 10 according to this embodiment only needs to operate to support the creation of data models and instance data (data related to devices) that use a multi-layered structure such as a metamodel, and is not necessarily limited to a configuration that utilizes an asset management shell.

[0113] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0114] With regard to the embodiments described above, the following additional information is disclosed. [1] The system comprises a metamodel located in the first layer, which defines inclusion and reference relationships between multiple types of information models located in the second layer, and a guide tree representing the relationships between the information models based on this metamodel, The aforementioned information model defines data items related to the equipment, The aforementioned guide tree indicates that the higher-level first information model, whose relationships are represented in the guide tree, can utilize the data items defined in the lower-level second information model. Information processing methods. [2] The information processing method according to [1] further comprises creating a definition table for setting the attributes of the information model and the data items defined in the information model based on the metamodel and the guide tree. [3] The information processing method described in [2] includes a first definition table for setting the attributes of the first information model, the second information model, and the data items defined in the first information model, and a second definition table for setting the attributes of the second information model and the data items defined in the second information model. [4] The aforementioned first information model includes AAS in the asset management shell, The aforementioned second information model includes submodels in the asset management shell, The invention further comprises creating a submodel graph that includes nodes representing each of the submodels and links representing the relationships between the submodels, based on the data items defined for each of the submodels set in the second definition table, The submodel graph includes data items common to the two submodels whose relationship is represented by the link, or the number of such data items. [3] The information processing method described in [3]. [5] The information processing method according to [4] further comprises recommending a submodel in which a data item is defined as a submodel to be set in the first definition table, based on the data items set in the first definition table. [6] The information processing method described in [5], which includes recommending further submodels whose relationship to the recommended submodels is represented by links included in the submodel graph. [7] The information processing method according to any one of the items [4] to [6], further comprising recommending a second submodel, whose relationship to a first submodel set in the first definition table is represented by a link included in the submodel graph, as a submodel to be further set in the first definition table. [8] The recommended submodels are assigned a priority order determined based on the submodel graph, according to the information processing method described in any one of the [5] to [7] paragraphs. [9] The recommended submodel is an information processing method described in any one of the items [5] to [8] set in the first definition table.

[10] The information processing method according to any one of the [3] to [9] paragraphs, further comprising creating a third definition table for setting data for data items defined in the information model set in the definition table.

[11] The aforementioned third definition table is created for each information model, The data set in one of the third definition tables created for each information model is reused in the other third definition tables.

[10] The information processing method described in

[10] .

[12] The system further comprises creating a model tree representing the relationship between the first and second information models based on the attributes of the first information model and the second information model set in the first definition table, The aforementioned model tree conforms to the constraints of the relationships represented by the aforementioned guide tree. The information processing method described in any one of the items [3] to

[11] .

[13] The system further comprises creating an instance data tree representing the relationship between the first and second information models and the data, based on the attributes of the first information model and the second information model set in the first definition table and the data set in the third definition table. The instance data tree conforms to the constraints of the relationships represented by the guide tree. The information processing method described in

[10] or

[11] .

[14] Creating the first information model according to the settings for the first definition table, To create the second information model according to the settings for the second definition table. An information processing method described in any one of the items [3] to

[13] further comprising:

[15] The information processing method according to

[14] further comprises outputting the first and second information models created in a specified format.

[16] The information processing method described above, which includes outputting further data of data items defined in the first and second information models created

[15] .

[17] The information processing method described in

[16] , wherein the user specifies one of a first output range that indicates outputting the first and second information models, and a second output range that outputs the first and second information models and the data of the data items defined in the first and second information models.

[18] The information processing method described in any one of the

[15] to

[17] paragraphs, wherein outputting includes outputting the first and second information models in different files.

[19] The information processing method according to any one of the items in [4] to

[18] , which further includes creating an AAS graph that includes nodes representing each of the AASs and links representing the relationships between the AASs.

[20] The aforementioned second information model includes Asset in the asset management shell, Creating the aforementioned includes further creating an Asset graph which includes nodes representing each of the Assets and links representing the relationships between those Assets. The information processing method described in any one of the items [4] to

[18] . [twenty one] The system comprises a metamodel located in the first layer, which defines inclusion and reference relationships between multiple types of information models located in the second layer, and a means for creating a guide tree that represents the relationships between the information models, The aforementioned information model defines data items related to the equipment, The aforementioned guide tree indicates that the higher-level first information model, whose relationships are represented in the guide tree, can utilize the data items defined in the lower-level second information model. Information processing device. [twenty two] The computer is instructed to perform the step of creating a guide tree representing the relationships between information models, based on a metamodel located in the first layer, which defines the inclusion and reference relationships between multiple types of information models located in the second layer. The aforementioned information model defines data items related to the equipment, The aforementioned guide tree indicates that the higher-level first information model, whose relationships are represented in the guide tree, can utilize the data items defined in the lower-level second information model. program. [Explanation of symbols]

[0115] 10... Information processing unit, 11... Database, 12... Tree creation unit, 13... Definition table creation unit, 14... Input / output unit, 15... Graph creation unit, 16... Recommendation processing unit, 101... CPU, 102... Non-volatile memory, 103... Main memory, 104... Communication device.

Claims

1. An information processing method executed by an information processing device that includes a database storing a metamodel located in the first layer, in which inclusion and reference relationships between multiple types of information models located in the second layer are defined, Obtaining the metamodel from the aforementioned database, Based on the acquired metamodel, a guide tree is created that represents the relationships between the information models. It is equipped with, Creating the aforementioned guide tree means Extracting the first and second information models in which inclusion relationships are defined in the aforementioned metamodel, If the first information model encompasses the second information model, the first information model is placed in the guide tree as a higher-level model and the second information model as a lower-level model. Extracting third and fourth information models in which reference relationships are defined in the aforementioned metamodel, When the third information model references the fourth information model, the third information model is placed in the guide tree as the source and the fourth information model as the destination. Includes, The aforementioned information model defines data items related to the equipment, The guide tree indicates that the first information model can utilize the data items defined in the second information model. Information processing methods.

2. The information processing method according to claim 1, further comprising creating a definition table for setting the attributes of the information model and the data items defined in the information model, based on the metamodel and the guide tree.

3. The information processing method according to claim 2, wherein the definition table includes a first definition table for setting the attributes of the first information model, the second information model, and the data items defined in the first information model, and a second definition table for setting the attributes of the second information model and the data items defined in the second information model.

4. The first information model includes an AAS in the asset management shell, The aforementioned second information model includes a submodel in the asset management shell, The invention further comprises creating a submodel graph that includes nodes representing each of the submodels and links representing the relationships between the submodels, based on the data items defined for each of the submodels set in the second definition table, The submodel graph includes data items common to the two submodels whose relationship is represented by the link, or the number of such data items. The information processing method according to claim 3.

5. The information processing method according to claim 4, further comprising recommending a submodel in which a data item is defined as a submodel to be set in the first definition table, based on the data item set in the first definition table.

6. The information processing method according to claim 5, wherein the recommendation further recommends a submodel whose relationship to the recommended submodel is represented by a link included in the submodel graph.

7. The information processing method according to claim 4, further comprising recommending a second submodel, whose relationship to a first submodel set in the first definition table is represented by a link included in the submodel graph, as a submodel to be further set in the first definition table.

8. The information processing method according to any one of claims 5 to 7, wherein the recommended submodels are assigned a priority order determined based on the submodel graph.

9. The information processing method according to claim 8, in which the recommended submodel is set in the first definition table.

10. The information processing method according to claim 3, further comprising creating a third definition table for setting data for data items defined in the information model set in the definition table.

11. The third definition table is created for each information model. The data set in one of the third definition tables created for each information model is reused in the other third definition tables. The information processing method according to claim 10.

12. The system further comprises creating a model tree representing the relationship between the first and second information models based on the attributes of the first information model and the second information model set in the first definition table, The aforementioned model tree conforms to the constraints of the relationships represented by the aforementioned guide tree. The information processing method according to claim 3.

13. The system further comprises creating an instance data tree representing the relationship between the first and second information models and the data, based on the attributes of the first information model and the second information model set in the first definition table and the data set in the third definition table. The instance data tree conforms to the constraints of the relationships represented by the guide tree. The information processing method according to claim 10.

14. Creating the first information model according to the settings for the first definition table, To create the second information model according to the settings for the second definition table. The information processing method according to claim 3, further comprising the above.

15. The information processing method according to claim 14, further comprising outputting the first and second information models created in a specified format.

16. The information processing method according to claim 15, wherein the output further includes outputting data of data items defined in the first and second information models created.

17. The information processing method according to claim 16, wherein one of a first output range indicating the output of the first and second information models, and a second output range indicating the output of the first and second information models and the data of the data items defined in the first and second information models, is specified by the user.

18. The information processing method according to claim 15, wherein the output includes outputting the first and second information models in different files.

19. The information processing method according to claim 4, further comprising creating an AAS graph which includes nodes representing each of the AAS and links representing the relationships between the AAS.

20. The second information model includes an Asset in the asset management shell, The aforementioned creation includes further creating an Asset graph which includes nodes representing each of the Assets and links representing the relationships between those Assets. The information processing method according to claim 4.

21. A database that stores a metamodel located in the first layer, in which the inclusion and reference relationships between multiple types of information models located in the second layer are defined. Acquisition means for acquiring the metamodel from the database, The system includes means for creating a guide tree that represents the relationships between the information models based on the acquired metamodel, The aforementioned creation means is Extract the first and second information models in which inclusion relationships are defined in the aforementioned metamodel, If the first information model includes the second information model, the first information model is placed in the guide tree as a higher-level model and the second information model as a lower-level model. The third and fourth information models, in which reference relationships are defined in the aforementioned metamodel, are extracted. When the third information model references the fourth information model, the third information model is placed in the guide tree as the source and the fourth information model as the destination. The aforementioned information model defines data items related to the equipment, The guide tree indicates that the first information model can utilize the data items defined in the second information model. Information processing device.

22. A program executed by a computer of an information processing device, which includes a database for storing metamodels located in a first layer, in which inclusion relationships and reference relationships between a plurality of types of information models located in a second layer are defined, To the aforementioned computer, The steps include obtaining the metamodel from the database, The steps include creating a guide tree that represents the relationships between the information models based on the acquired metamodel, and Make it run, The steps to be created are as follows: The steps include extracting first and second information models in which inclusion relationships are defined in the metamodel, If the first information model includes the second information model, the first information model is placed in the guide tree as a higher-level model and the second information model as a lower-level model; The steps include extracting third and fourth information models in which reference relationships are defined in the aforementioned metamodel, When the third information model references the fourth information model, the third information model is placed in the guide tree as the source and the fourth information model as the destination. Includes, The aforementioned information model defines data items related to the equipment, The guide tree indicates that the first information model can utilize the data items defined in the second information model. program.

Images