Association method, facility management device, and program

Abstract

The present invention automatically associates data points with each other. The present disclosure relates to an association method performed by an information processing device that processes data relating to facility equipment, wherein a control unit performs: a step for, on the basis of identification information of a first data storage location of a first template and a second data storage location of a second template with said templates having data storage locations into which data points where the data is inputted or outputted are classified and stored, associating the first data storage location and the second data storage location with each other; and a step for, on the basis of identification information of a first data point that is stored in the first data storage location and a second data point that is stored in the second data storage location associated with the first data storage location, associating the first data point and the second data point.

Description

Association method, facility management device, program

[0001] The present invention relates to an association method, a facility management device, and a program.

[0002] When introducing software into a facility management system such as a BMS (Building Management System), an operation of registering facility equipment in the software occurs. A plurality of templates for the operation are prepared in the software, and furthermore, data points can be arranged in the templates. A data point is a node for inputting or outputting data related to facility equipment.

[0003] Patent Document 1 discloses a technique for automatically generating and updating document files such as operation manuals, control logic definition documents, and specifications of industrial plants, and applications based on unified management design data in order to reduce the man-hours required for BMS construction.

[0004] U.S. Patent No. 10,108,183

[0005] However, in the conventional technology, it was necessary to manually perform an operation of associating data points arranged in templates between templates. The operation of the installer manually associating data points one by one requires a lot of man-hours. When introducing a plurality of devices, the number of data points also increases by the number of devices, so the number of data points becomes enormous, requiring even more man-hours and sometimes causing mistakes.

[0006] The present disclosure provides a technique for automatically associating data points.

[0007] A first aspect of the present disclosure is an association method performed by an information processing device that processes data relating to equipment, wherein a control unit performs the following steps: a step of associating a first data storage location in a first template and a second data storage location in a second template, based on identification information of the first and second data storage locations, in a template having data storage locations for classifying and storing data points that the data is input or output from.

[0008] According to a first aspect of this disclosure, associations between data points can be performed automatically.

[0009] A second aspect of the present disclosure is the association method described in the first aspect, wherein the template comprises a device template for data points that input or output data to or from the equipment, an application template for data points that input or output data to or from control logic, and a model template for data points that input or output data between the device template and the application template, and the control unit associates the device data storage location of the device template with the application data storage location of the application template, the model data storage location of the model template with the device data storage location, or the model data storage location with the application data storage location, based on relation information defining the data storage locations to be associated.

[0010] A third aspect of this disclosure is the association method described in the second aspect, wherein, as a result of the control unit associating the data points of the application data storage location with the data points of the model data storage location, if there are data points in the application data storage location that are not associated with the data points of the model data storage location, the control unit associates the data points of the application data storage location that were not associated with the data points of the model data storage location with the data points of the device data storage location based on the identification information of the data points of the application data storage location and the data points of the device data storage location.

[0011] A fourth aspect of this disclosure is the association method described in the second aspect, wherein the relation information is defined in the model template and the device template, the control unit associates the device data storage location with the application data storage location based on the relation information defined in the device template, associates the model data storage location with the device data storage location based on the relation information in the model template, and associates the model data storage location with the application data storage location based on the relation information in the model template.

[0012] A fifth aspect of this disclosure is the association method described in the second aspect, wherein the control unit first expands the application data storage locations located in the application template into memory based on the application template, then expands the device data storage locations located in the device template into memory based on the device template, then expands the model data storage locations located in the model template into memory based on the model template, and after associating the device data storage locations with the application data storage locations, it performs the association between the application data storage locations and the model data storage locations, or the association between the device data storage locations and the model data storage locations, in no particular order.

[0013] A sixth aspect of this disclosure is the association method described in the second aspect, wherein the control unit first expands the application data storage locations located in the application template into memory based on the application template, then expands the model data storage locations located in the model template into memory based on the model template, then expands the device data storage locations located in the device template into memory based on the device template, then associates the model data storage locations with the application data storage locations, and then associates the application data storage locations with the device data storage locations, or associates the device data storage locations with the model data storage locations, in no particular order.

[0014] A seventh aspect of this disclosure is the association method described in the second aspect, wherein the template is further a data conversion template for converting the format of the data, and the control unit associates the conversion data storage location and the device data storage location, and the conversion data storage location and the model data storage location, based on the relationship information, based on the identification information of the conversion data storage location, the device data storage location and the model data storage location, associates the data points of the conversion data storage location with the data points of the model data storage location, and associates the data points of the conversion data storage location and the data points of the device data storage location, based on the identification information of the data points of the conversion data storage location, the device data storage location and the model data storage location.

[0015] An eighth aspect of the present disclosure is an equipment management device for processing data relating to equipment, wherein a control unit has a template in which data storage locations are arranged for classifying and storing data points that the data is input or output from, and associates a first data storage location in a first template with a second data storage location in a second template based on identification information of the first data storage location and the second data storage location, and associates a first data point stored in the first data storage location with a second data point stored in the second data storage location associated with the first data storage location based on identification information of the first data point and the second data point.

[0016] According to the eighth aspect of this disclosure, associations between data points can be performed automatically.

[0017] A ninth aspect of the present disclosure is a program to be executed by an information processing device that processes data relating to equipment, wherein the control unit of the information processing device is configured to perform the following steps: a step of associating a first data storage location in a first template with a second data storage location in a second template based on identification information of the first data storage location and the second data storage location; and a step of associating a first data point stored in the first data storage location with a second data point stored in the second data storage location associated with the first data storage location based on identification information of the first data point and the second data point.

[0018] According to the ninth aspect of this disclosure, associations between data points can be performed automatically.

[0019] This is an example of a system configuration diagram for an equipment management system in which an equipment management device controls various equipment via a network. This diagram explains data points and their connections. This diagram shows an example of data point connections for each template in the tool software. This is a hardware configuration diagram of an example of an equipment management device and a corresponding information creation device. This is a functional block diagram of an example of a corresponding information creation device on which the tool software operates. This diagram schematically shows folder information for folders deployed in an application template. This diagram schematically shows folder information for folders deployed in a device template. This diagram schematically shows folder information for folders deployed in a model template. This diagram explains the tabs of a spreadsheet file. This diagram shows an example of application template information stored in the application template information storage unit. This diagram shows an example of device template information stored in the device template information storage unit. This diagram shows an example of model template information stored in the model template information storage unit. This diagram shows an example of data point information for a folder in a D template. This diagram shows an example of data point information for a folder in an M template. This diagram shows an example of link rule information associated with an M template. This diagram shows an example of data point information for a folder in an APP template. This diagram shows an example of link rule information associated with an APP template. This diagram shows an example of data point information for a folder in a data conversion template. This is a diagram showing an example of link rule information associated with a data conversion template. This is a diagram showing an example of a link rule. This is a diagram showing an example of a relationship set between folders and a link set between data points. This is a flowchart diagram showing an example of the work that an installation worker performs on the corresponding information creation device on which the tool software operates. This is a flowchart diagram showing an example of the process by which the tool software connects data points in the APP template, M template, and D template. This is a diagram explaining the data format called Boolean. This is a diagram explaining the data format called Numeric. This is a diagram explaining the data format called Multi.This figure shows an example of data conversion, specifically converting a Multi to a Boolean and then to another Multi. It also shows an example of setting up relationships and links when an M template is not available.

[0020] The following describes an example of how to implement this disclosure, specifically the method of linking equipment management systems.

[0021] <About Facility Management Systems> Facility management systems are installed in many properties such as office buildings, commercial facilities, schools, and hospitals. Facility management systems are called BAS (Building Automation System), BEMS (Building Energy Management System), BMS (Building Management System), BACS (Building Automation and Control System), etc. There are no strict definitions for these, but we will briefly explain each of them.

[0022] BAS is a system that automatically controls the equipment in a property. It allows for the centralized control and monitoring of all equipment, such as air conditioning, lighting, security systems, and electricity meters, which were previously managed manually by the administrator, via a network.

[0023] BEMS is a system for managing the energy consumption of a property. While BAS can also manage energy, BEMS is a system that focuses more on "visualizing energy consumption." Visualizing energy consumption with BEMS not only shows current energy consumption in real time, but also displays it in comparison with data from the previous day, month, and year, making it easy to determine whether the current energy consumption is appropriate.

[0024] A Building Management System (BMS) is a system that monitors and controls various equipment in a property, such as power, air conditioning, lighting, fire prevention, and security. In properties such as office buildings, these various pieces of equipment are in operation. To maintain them in a safe state and ensure they function as intended, it is necessary to monitor their status and immediately detect any abnormalities. Furthermore, if administrators can operate the equipment remotely and change settings without directly operating it, the workload can be reduced.

[0025] BACS, while not strictly defined, refers to a system that combines BAS, BMS, and BEMS, and is registered under ISO 16484-5.

[0026] In the following, BAS, BEMS, BMS, BACS, or similar systems for equipment and properties will be described as equipment management systems without any particular distinction.

[0027] <About the terminology> A data point is a software node that holds data that is input to or output by equipment. Data points connect to other data points to supply data to functions that require it.

[0028] A data storage location is a function that stores one or more data points together. In the case of a device template, one or more data points are grouped by equipment model number. In the case of a model template, one or more data points are grouped by equipment type. In the case of an application template, one or more data points are grouped by equipment model number. In this disclosure, the term "folder" is used to describe a data storage location.

[0029] A template is a pre-built system with basic settings and data processing pre-configured, depending on its intended use. Templates allow installers to place appropriate data points (data storage locations) for equipment and other devices. Templates include device templates, model templates, application templates, and data conversion templates. Device templates provide data input or output functions for equipment, model templates provide user interface functions such as data display, and application templates provide functions such as data processing logic.

[0030] <System Configuration Example> Figure 1 is an example of a system configuration diagram of an equipment management system 100 in which an equipment management device 10 controls various equipment 20 via a network. As shown in Figure 1, the equipment management device 10 and the various equipment 20 are connected to communicate via a network N1. This network N1 is assumed to be, for example, BACnet. BACnet is a network in which the equipment management system 100 communicates with the various equipment 20 using the BACnet protocol. Network N1 may use a dedicated cable, or it may use an Ethernet cable (registered trademark) as with a normal LAN. The equipment management system 100 is not required to use the BACnet protocol for network communication; the BACnet protocol is just one example. For example, the communication protocol may be Modbus, etc.

[0031] Examples of equipment 20 include air conditioners, lighting fixtures, security devices, disaster prevention devices, power supply devices, and elevators, but these are just examples. Furthermore, multiple units of the same device, such as an air conditioner, may be connected. A gateway device called a BACnet gateway may be placed between the equipment 20 and BACnet. The BACnet gateway converts communication data compatible with the BACnet protocol into communication data for the communication protocol supported by each piece of equipment 20, and then converts the communication data for the communication protocol supported by each piece of equipment 20 back into communication data compatible with the BACnet protocol. The communication protocol supported by each piece of equipment 20 is a proprietary communication protocol defined by the company that manufactured the equipment 20. Therefore, the equipment 20 may be manufactured by different companies or brands.

[0032] The equipment management device 10 has the functionality of a web server and creates a screen for managing the equipment 20 using HTML or the like, and sends it to the terminal device 50 via the network N2. The network N2 is, for example, the internet. Users can monitor the equipment 20 by connecting the terminal device 50 to the equipment management device 10 from any location. Even without a terminal device 50, users can monitor the equipment 20 by directly operating the console (display and keyboard) of the equipment management device 10.

[0033] Furthermore, the corresponding information creation device 60 is connected to network N2 in a communicative manner. The corresponding information creation device 60 only needs to be able to communicate with the equipment management device 10 via network N2, and does not need to be constantly connected to network N2. When connecting the device data points (hereinafter referred to as D data points), model data points (hereinafter referred to as M data points), and application data points (hereinafter referred to as APP data points) as described in this disclosure, the corresponding information creation device 60 can process the information independently. In this embodiment, the connection between data points may be performed by either the equipment management device 10 or the corresponding information creation device 60.

[0034] The equipment management device 10 or the corresponding information creation device 60 may be any information processing device with an OS such as Windows® installed. The equipment management device 10 or the corresponding information creation device 60 has the tool software described later installed and performs the process of connecting (or associating) APP data points, M data points, and D data points (details of which will be described later). Hereafter, the term "connect" will be used in this disclosure. The corresponding information creation device 60 may be a PC (Personal Computer), tablet terminal, smartphone, etc., as long as the tool software can run on it.

[0035] In BACnet, the functions of equipment 20 are treated as objects. An object is a representation of various pieces of information grouped together, and the information associated with an object is called a property in BACnet. For example, if an air conditioner is an object, the control options available to the air conditioner (temperature, airflow, etc.) correspond to properties. In BACnet, reading or writing objects or associated properties is called a service. For the sake of clarity, in the following description of this disclosure, objects and properties are not distinguished and are simply referred to as "data points."

[0036] <Software Structure within the Information Processing System> Figure 2 is a diagram illustrating data points and their connections. Tool software 8 operates in the equipment management device 10. First, tool software 8 has a station template 9, an application template (hereinafter sometimes referred to as APP template 11), a device template 19 (hereinafter sometimes referred to as D template 19), a model template 14 (hereinafter sometimes referred to as M template 14), and a data conversion template 31. Tool software 8 is an introductory tool for connecting data points using these templates. Once the data points are connected, an application for the equipment management system 100 that controls the equipment 20 becomes executable. Station template 9 is an abstraction of the equipment management system 100 represented in software.

[0037] The APP template 11 has one or more folders for storing APP data points 17, and each folder contains the APP data points 17 and an auto-link module. The APP template 11 also has control logic 12A to 12C. Any of the control logic 12A to 12C is referred to as "control logic 12". Control logic refers to various calculations based on data. The APP template 11 is a template that packages the data points 17, the folder containing the auto-link module 21, and the multiple control logics 12A to 12C. The auto-link module 21 performs the link settings (between the app and the model / app and the device) related to the APP template 11, which will be described later.

[0038] D template 19 is a template that defines all D data points 16 held by equipment for each equipment model number. M template 14 is a template that defines standard M data points 15 for each category of building equipment. D template 19 has D data points 16 that depend on the equipment model number, and M template 14 has M data points 15 that are common to all types of building equipment, even if the model numbers are different. Therefore, the number of D data points 16 is generally greater than the number of M data points 15. M template 14 has an auto-link module 22, and the auto-link module 22 performs the link settings (between model and device) for M template 14, which will be described later.

[0039] Previously, installation personnel manually connected APP data point 17, D data point 16, and M data point 15. However, this process was cumbersome, increasing man-hours and making errors more likely.

[0040] Therefore, in this embodiment, the developer sets a tag for each data point. The tag is identification information for the data point, and in Figure 2, it can be thought of as a circled number and a tag. The tool software 8 connects the data points of APP template 11, D template 19, and M template 14 based on link rules (described later) that define the connection of data points having the same tag information. The control logic 12 of APP template 11 can be connected to data points of either D template 19 or M template 14.

[0041] <Examples of Data Point Connections and Relationships> Figure 3 shows examples of data point connections for each template in the tool software 8. Figure 3 is the same configuration as Figure 2, with the elements arranged horizontally. However, Figure 3 explains the function of each template in more detail. Figure 3 includes specific examples of data points for each template. The installer deploys the APP template 11, D template 19, and M template 14 into the tool software 8 to create the application functions for the equipment management system 100.

[0042] D data points 16 are placed in the D template 19. D data points 16 are generated for each model number of the equipment 20. The D template 19 defines D data points 16 for all the data that the equipment 20 inputs or outputs. A tag (identification information that identifies, for example, "room temperature") is also defined for each D data point 16. One or more D data points 16 are stored in a single folder 35a, 36b. Folders 35a, 35b are generated for each model number of the equipment 20. Therefore, D data points 16 of the same model number are grouped in the same folder. By classifying the D data points 16 in folders, the equipment management device 10 can place different D data points 16 with the same tag in a single D template 19.

[0043] The M template 14 has M data points 15 arranged therein. The M template 14 has M data points 15 common to the types of facility equipment 20 defined therein. Also, a tag is defined for each M data point 15. Also, one or more M data points 15 are stored in folders 33a and 33b. The folders 33a and 33b are generated for each type of facility equipment 20. Thus, the folders 33a and 33b of the M template 14 cover data common among the types of facility equipment. The facility management device 10 can generate different M data points 15 having the same tag in one M template 14 by classifying the M data points 15 by folder.

[0044] The APP template 11 has a plurality of control logics 12A to 12C arranged therein. For example, the control logic 12A processes the indoor temperature, the control logic 12B processes the fan on / off, and the control logic 12C processes the outlet temperature. In addition, the control logic can incorporate various functions such as energy-saving operation control spanning multiple air conditioners, operation control based on a schedule, and abnormality management (alarm).

[0045] In order for the control logics 12A to 12C to input or output data such as the indoor temperature, fan on / off, and outlet temperature, the APP template 11 has APP data points 17 for inputting or outputting the data used by the control logic 12 arranged therein. The APP data points 17 generally correspond to the D data points 16. A tag is defined for each APP data point 17. Also, one or more APP data points 17 are stored in folders 37a and 37b. The folders 37a and 37b of the APP template 11 are generated for each model number of the facility equipment 20. The facility management device 10 can generate different APP data points 17 having the same tag in one APP template 11 by classifying the APP data points 17.

[0046] Since there is a relationship where the number of data points for each model > the number of data points common to all models, the number of D data points 16 in the D template 19 is greater than or equal to the number of M data points 15 in the M template 14.

[0047] In FIG. 3, the folder 35a of the D template 19 has three D data points 16. The folder 33a of the M template 14 has three M data points 15. The folder 37a of the APP template 11 has three APP data points 17. The three D data points 16 are automatically connected to the three M data points 15 based on tags. Also, the D data point 16 may be directly connected to the APP data point 17. The three M data points 15 in the folder 33a are automatically connected to the three APP data points 17 in the folder 37a based on tags. The folders 35b, 33b, and 37b are connected in the same way.

[0048] Also, for the transfer of data between the D template 19 and the M template 14, a data conversion template 31 is arranged as needed. The data conversion template 31 is a template for converting the data format. The folder 39a of the data conversion template 31 has conversion data points 34a, 34b, and the folder 39b has conversion data points 34c, 34d. The conversion data points 34a, 34c are connected to the D data points 16 of the D template 19 based on tags, and the conversion data points 34b, 34d are connected to the M data points 15 of the M template 14 based on tags.

[0049] Thus, the tool software 8 only needs to connect data points on one template to data points on another template. However, a single template may contain multiple data points with the same tag. For example, if room temperature, fan on / off status, and outlet temperature are tags, then each tag may exist multiple times in a single template. When the tool software 8 makes an automatic connection, it cannot determine whether to connect, for example, the room temperature in folder 35a to the room temperature in folder 33a, or to the room temperature in folder 33b.

[0050] Therefore, in this embodiment, the relationship setting unit 62 establishes relationships between folders. For this purpose, the developer sets tags (tags different from data points) for the folders as well. Folder 35a has tag 41a, folder 35b has tag 41b, folder 33a has tag 42a, folder 33b has tag 42b, folder 37a has tag 43a, and folder 37b has tag 43b.

[0051] The tool software 8 searches for folder tags using the "relationship information" described later and establishes relationships between folders in different templates. The relationship information has a search key for searching for tags set in folders. As a result, relationship 27a is established between folder 37a in APP template 11 and folder 33a in M ​​template 14. Relationship 25a is established between folder 37a in APP template 11 and folder 35a in D template 19. Relationship 26a is established between folder 33a in M ​​template 14 and folder 35a in D template 19. Connections between data points are made within these relationships. Relationships are omitted for folders 37b, 33b, and 35b, but relationships are established similarly.

[0052] APP data point 17, D data point 16, and M data point 15 each hold data. The data held by D data point 16 can be accessed by the equipment 20, and the data set in M ​​data point 15 can be displayed on the user interface. The data set in APP data point 17 can be accessed by the control logic 12. Various types of data are handled in the equipment management system, so room temperature, fan on / off status, or outlet temperature are just examples.

[0053] The M data point 15 receives data transmitted from the equipment 20 to the D data point 16 connected to the M data point 15. This data is processed according to the M data point 15, such as display processing. The D data point 16 receives data transmitted from the M data point 15 connected to the D data point 16 and transmits it to the equipment 20. The APP data point 17 receives data transmitted from the M data point 15 or D data point 16 connected to the APP data point 17. This data is processed according to the APP data point 17, such as control logic 12. The M data point 15 receives data transmitted from the APP data point 17 connected to the M data point 15 and either displays it or transmits it to the D data point 16.

[0054] <Hardware Configuration Example> Figure 4 is a hardware configuration diagram of the equipment management device 10 and the corresponding information creation device 60. As shown in Figure 4, the equipment management device 10 and the corresponding information creation device 60 are built on a computer 500 and include a CPU 501, ROM 502, RAM 503, HD 504, HDD (Hard Disk Drive) controller 505, display 506, external device connection I / F (Interface) 508, network I / F 509, bus line 510, keyboard 511, pointing device 512, optical drive 514, and media I / F 516.

[0055] Of these, the CPU 501 controls the operation of the entire computer 500. The CPU 501 corresponds to the control unit 200 that controls the entire computer 500.

[0056] ROM 502 stores programs used to drive the CPU 501, such as IPL. RAM 503 is used as the work area for the CPU 501. HD 504 stores various data such as programs. HDD controller 505 controls the reading or writing of various data to HD 504 according to the control of the CPU 501. Display 506 displays various information such as cursors, menus, windows, characters, or images. External device connection I / F 508 is an interface for connecting various external devices. External devices in this case include, for example, USB (Universal Serial Bus) memory and printers. Network I / F 509 is an interface for data communication using networks N1 and N2. Bus line 510 is an address bus, data bus, etc., for electrically connecting each component such as the CPU 501 shown in Figure 4.

[0057] The keyboard 511 is a type of input means equipped with multiple keys for inputting characters, numbers, and various instructions. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting processing targets, and moving the cursor. The optical drive 514 controls the reading or writing of various data to the optical storage medium 513, which is an example of a removable recording medium. The optical storage medium may be a CD, DVD, Blu-ray (registered trademark), etc. The media interface 516 controls the reading or writing (storage) of data to the recording medium 515, such as flash memory.

[0058] <About the Functions> Figure 5 is a functional block diagram of the equipment management device 10 on which the tool software 8 operates. The equipment management device 10 has a display control unit 61, a relationship setting unit 62, a link creation unit 63, and an operation reception unit 64. Each of these functional units of the equipment management device 10 is a function of the control unit 200. Each functional unit is a function or means realized by the CPU 501 shown in Figure 5 executing instructions contained in one or more programs installed in the equipment management device 10. This program may be, for example, the tool software 8.

[0059] Furthermore, the equipment management device 10 includes an application template information storage unit 65, a device template information storage unit 66, a model template information storage unit 67, and a data conversion template information storage unit 68. Each of these storage units is built into the HD 504 and RAM 503 shown in Figure 4.

[0060] The display control unit 61 displays various screens for the operator to use to operate the tool software 8 (APP template 11, M template 14, D template 19, data conversion template 31, etc.).

[0061] The relationship setting unit 62 sets relationships between folders. Setting a relationship is sometimes referred to as "establishing a relationship." The relationship setting unit 62 searches for folder tags in different templates using the search key set in the relationship information described later. The relationship setting unit 62 establishes a relationship with the folders that match the search. The relationship restricts the range of data points that are searched. The order in which the relationship setting unit 62 establishes relationships between template folders is predetermined. As will be described in detail later, the order in which each template is loaded into memory is also predetermined so that relationships can be established in this order.

[0062] The link creation unit 63 creates a link between the data points of one folder and the other folder with which a relationship has been established. This link corresponds to the connection (association) between data points in this disclosure. The link creation unit 63 searches for tags possessed by the data points within the relationship using the search key set in the link rule described later. This identifies two data points from different templates.

[0063] The operation reception unit 64 receives various operations from the installation operator for the tool software 8 that operates on the corresponding information creation device 60.

[0064] <Folder Information> Figures 6A to 6C schematically show the folder information for the folders deployed in each template. Figure 6A shows the folder information for APP template 11, Figure 6B shows the folder information for D template 19, and Figure 6C shows the folder information for M template 14.

[0065] Each template's folder information has tags. The tags in Figures 6A to 6C are folder identification information. These tags are searched to establish relationships between folders. In Figures 6A to 6C, different folders within the template have the same tags, but this does not cause any problems because relationships are established between folders with the same number at the end of the folder name (e.g., "1" for folder 1). Alternatively, if the number at the end of the folder name is not used for relationship settings, the developer can set different tags for each folder.

[0066] <Template Information> Refer to Figure 7 and other documents to explain template information. First, Figure 7 shows the tabs of a single spreadsheet file. Each tab contains application template information, device template information, and model template information. Thus, template information is contained in a single spreadsheet file, but application template information, device template information, and model template information may be stored in separate files.

[0067] The application template information defines an APP template 11 that includes a folder, the device template information defines a D template 19 that includes a folder, and the model template information defines an M template 14 that includes a folder. When this spreadsheet file (D template 19, M template 14, APP template 11) is loaded into memory, the order of loading is important. In order to establish a relationship, the folder to which the relationship is to be established must already exist in memory. Therefore, in this embodiment, the tool software 8 loads the templates into memory in the order of APP template 11 > D template 19 > M template 14.

[0068] Figure 8 shows an example of application template information stored in the application template information storage unit 65. Although not explicitly stated in Figure 8, the application template information defines the folders and data points included in the APP template 11.

[0069] Figure 9 shows an example of device template information stored in the device template information storage unit 66. The device template information defines the folders and data points included in the D template 19. Rows 7 to 16 of the device template information contain information for each folder. Of these, column 301 contains bibliographic information about the equipment. Column 302 contains relation information 303 and the folder name 304. The Relation Id on the third row of relation information 303 is identification information that identifies the relationship between the configured folders. When a relationship is established, this Relation Id is set in the link rule described later. The Relation Hints on the fourth row of relation information 303 are search keys for searching the tags attached to the folders. "h4:indoor and dk:app" indicates that "h4:indoor" and "dk:app" are AND conditions. In other words, AND is a logical operator. Logical operators such as OR, NOT, and XOR can also be used. Note that the relationship settings starting from template D 19 only apply to template APP 11, so there is only one Relation Hint. Since relation information 303 is linked to a folder, the source folder is fixed and there is no need to search the tags of the source folder. However, there is no problem in searching the source folder. The Direction on the 5th line of relation information 303 indicates the direction in which data flows between data points.

[0070] For example, let's explain the relationship established with the VRV_2 folder defined on line 8. The relationship setting unit 62 searches for tags attached to folders in the APP template 11 using "h4:indoor and dk:app" as the search key. If a match is found, the relationship setting unit 62 establishes a relationship called h4:deviceRef between the VRV_2 folder and the folder in the APP template 11. If there are multiple folders in the APP template 11 that match the search, the relationship is established between folders with the same number at the end of their name (2 in the case of VRV_2). Therefore, the folder name may sometimes become part of the tag.

[0071] A relationship indicates a location for creating a link, regardless of whether data is being transferred. A good example of a relationship is the relationship between folders in different templates.

[0072] Figure 10 shows an example of model template information stored in the model template information storage unit 67. The model template information defines the folders and data points included in the M template 14. The structure of the model template information is the same as that of the device template information, so the differences will be explained.

[0073] The fourth line, Relation Hints, is a search key for searching for tags attached to folders. The model template information has two search keys set: "h4:indoor and dk:device" and "h4:indoor and dk:app". The search key on the left is for searching for folder tags in D template 19, and the search key on the right is for searching for folder tags in APP template 11. The left and right search keys also define the order in which relationships are established. In a relationship setting starting from M template 14, a relationship is established first with the folders in D template 19, and then with the folders in APP template 11.

[0074] <<Data Point Information in Folders Generated in Each Template>> Next, referring to Figure 11, etc., the information contained in the data points in folders generated in each template will be explained. Figure 11 is an example of data point information for a folder in template D 19. The data point information has the following items: model number ID, tag, device data point ID, and belonging folder. ・The model number ID item stores identification information of the model number of the equipment 20. ・The tag item stores the name used by the installation worker to identify the D data point 16. The tag item stores the tags that will be searched. The tags of D data point 16 will be searched when setting up links. ・The device data point ID stores identification information of the D data point 16 contained in the folder. ・The belonging folder is the folder to which the D data point 16 belongs, and is known in template D 19.

[0075] Figure 12A shows an example of data point information for a folder in M ​​template 14. The data point information has the following items: type ID, tag, model data point ID, and belonging folder. • The type ID item stores identification information for the type of equipment 20. • The tag item stores a name used by the installation worker to identify the M data point 15. The tag item stores the tags that will be searched. The tags of M data point 15 are searchable when setting up links. • The model data point ID stores identification information for M data point 15 set in the software. • The belonging folder is the folder to which M data point 15 belongs, and is known in M ​​template 14.

[0076] Figure 12B shows the link rule information associated with the M template 14. The Link Rule ID field stores the identification information of the link rule. A link rule is prepared for each M data point 15. The link rule information is held by the auto-link module 22 of the M template 14.

[0077] Figure 13A shows an example of data point information for a folder in APP template 11. The data point information includes the following items: type ID, tag, application data point ID, and belonging folder. • The type ID item stores identification information for the equipment 20 model number. • The tag item stores a name used by the installer to identify the APP data point 17. The tag item also stores the tags to be searched. The tags of APP data point 17 are searchable when setting up links. • The application data point ID stores identification information for the APP data point 17 set in the software. • The belonging folder is the folder to which the APP data point 17 belongs, and is known in APP template 11.

[0078] Figure 13B shows the link rule information associated with the APP template 11. The Link Rule ID field stores the identification information of the link rule. A link rule is prepared for each APP data point 17. Although each APP data point 17 is connected to either a D data point 16 or an M data point 15, there is only one APP data point 17 that is the source of the connection, so only one link rule is needed for each APP data point 17. The link rule information is held by the auto-link module 21 of the APP template 11.

[0079] Figure 14A shows an example of data point information for a folder in the data conversion template 31. The data point information includes the following items: type ID, tag, conversion data point ID, and belonging folder. • The type ID item stores identification information for the type of equipment 20. • The tag item stores a name used by the operator to identify the data point in the data conversion template 31. There are tags for D data point 16 and M data point 15. These may be the same. Tags are searchable when setting links. • The conversion data point ID stores identification information for the conversion data point set in the software. Different IDs may be assigned for D data point 16 and M data point 15. • The belonging folder is the folder to which the conversion data point 34 belongs, and is known in the data conversion template 31.

[0080] Figure 14B shows the link rule information associated with the data conversion template 31. A link rule is provided for each conversion data point. Link rules are also provided on both the D data point 16 side and the M data point 15 side. The Link Rule ID (for Device Data Point) field stores the identification information of the link rule for connecting the D data point 16 of the D template 19 and the conversion data point 34 of the data conversion template 31. The Link Rule ID (for Model Data Point) field stores the identification information of the link rule for connecting the data point of the M template 14 and the conversion data point 34 of the data conversion template 31.

[0081] <Link Rules> Figure 15 shows an example of a link rule. A link rule is a rule (regulation) for connecting data points. As described above, link rules are provided for APP data point 17, M data point 15, and conversion data point 34. In other words, there are no link rules for D data point 16. This is because the connection of data points is reciprocal, so it is sufficient for one data point (the data point that is the starting point of the connection process) to have a link rule. A link rule has the following items.

[0082] Rule Name 201 is the name of the link rule and is arbitrarily set by the developer.

[0083] Device Relationship 202 is a relationship set by the relationship setting unit 62. That is, Device Relationship 202 is the Relation ID in column 302 of Figure 9. Device Relationship 202 identifies two folders in different templates.

[0084] Point Query 203 is a query (search key) for searching for tags attached to data points. In Figure 15, Point Query 203 is listed as "hs:alarm and hs:sensor". This means that using "hs:alarm and hs:sensor" as the key, it searches for tags associated with data points within two related folders. "and" is a logical operator. Logical operators such as "or", "not", and "xor" can also be used. Developers can specify the data point to connect to in the query.

[0085] Link Direction 204 is the direction of the link as viewed from the APP template 11, M template 14, or data conversion template 31. In means that data is input to the data point where the link rule is set. Out means that data is output from the data point where the link rule is set.

[0086] "From Slot Name 205" is the name of the starting point.

[0087] "To Slot Name 206" is the name of the final destination.

[0088] <Examples of Relationship and Link Settings> Figure 16 shows an example of a relationship set between folders and a link set between data points. Note that Figure 16 illustrates the case where the data conversion template 31 does not exist. Thus, the data conversion template 31 is not necessary.

[0089] A. Based on the relationship information defined in template D 19, relationship 25a is established between folders 35a and 37a. Based on the relationship information defined in template D 19, relationship 25b is established between folders 35b and 37b. Note that any of relations 25a and 25b is referred to as relationship 25.

[0090] B. Based on the relationship information defined in M ​​template 14, relationship 26a is established between folders 33a and 35a. Based on the relationship information defined in M ​​template 14, relationship 26b is established between folders 33b and 35b. Note that any of relations 26a and 26b is referred to as relationship 26.

[0091] C. Based on the relationship information defined in M ​​template 14, relationship 27a is established between folders 33a and 37a. Based on the relationship information defined in M ​​template 14, relationship 27b is established between folders 33b and 37b. Note that any of relations 27a and 27b is referred to as relationship 27.

[0092] Relationships 25-27 establish links to the data points as follows:

[0093] D data point 16a and M data point 15a, D data point 16b and M data point 15b, M data point 15a and APP data point 17a, M data point 15b and APP data point 17b, D data point 16d and M data point 15d, D data point 16e and M data point 15e, M data point 15d and APP data point 17d, M data point 15e and APP data point 17e.

[0094] Furthermore, a relationship 25 is established between the D template 19 and the APP template 11 because the number of data points in the D template 19 is greater than the number of data points in the M template 14, resulting in some D data points 16 not being connected to the M data points 15. However, if the M template 14 contains M data points 15, it is preferable that the data points of the D template 19 and the APP template 11 be connected via the M template 14. This is because it enables data display on the user interface, etc. For this reason, the connection between the APP data point 17 of the APP template 11 and the D data point 16 of the D template 19 is performed last. In other words, if, as a result of connecting the D data point 16 and the M data point 15, there are D data points 16 that are not connected to the M data point 15, then the D data point 16 and the APP data point 17 are connected.

[0095] This establishes links between the data points as follows: D data point 16c and APP data point 17c, and D data point 16f and APP data point 17f.

[0096] <Operation or Processing> Referring to Figure 17, the tasks performed by the installation operator on the tool software 8 will be explained. These tasks are preparatory steps for the tool software 8 to create links between data points. Figure 17 is a flowchart showing the tasks performed by the installation operator on the equipment management device 10 on which the tool software 8 operates.

[0097] The installation worker operates the equipment management device 10 to add the station template 9 (S1). Specifically, the installation worker adds the station template 9 (an abstract representation of the equipment management system in software) for adding the APP template 11, the D template 19, and the M template 14 to the tool software 8.

[0098] Then, the installation worker adds APP template 11 to station template 9 (S2). The installation worker adds D template 19 to station template 9 (S3). The installation worker adds M template 14 to station template 9 (S4).

[0099] Furthermore, if the installer needs to convert the data format of the D data point 16 of the D template 19 to match the M template 14 (Yes in S5), they add the data conversion template 31 to the station template 9 (S6).

[0100] Next, with reference to Figure 18, the process of setting up links between data points will be explained. Figure 18 is a flowchart illustrating the process by which the tool software 8 connects the data points in APP template 11, M template 14, and D template 19. The same procedure can be used when connecting the data points in data conversion template 31.

[0101] First, the installer exports the template information to a spreadsheet file (S11). The information that forms the basis of each template is information about equipment and data, and is created separately. Exporting to a spreadsheet file is done because tool software 8 supports it, and is not necessarily required.

[0102] Next, the operator enters template information, including relationship information as explained in Figures 7 to 10, into a spreadsheet file (S12).

[0103] Once the template information is complete in the spreadsheet file, the installer loads the spreadsheet file into memory (S13). The tool software 8 loads the spreadsheet file into memory, which allows each template to be loaded into memory. As described above, the template loading is performed in the order of APP template 11 > D template 19 > M template 14. This allows relationships to be established in the following order. Note that 2 and 3 can be in any order. 1. Relationship from D template 19 to APP template 11 2. Relationship from M template 14 to D template 19 3. Relationship from M template 14 to APP template 11 Also, if the template loading is in the following order, the order in which relationships are established will also be different. APP template 11 > M template 14 > D template 19 In this case, relationships can be established in the following order. 1. Relationship from M template 14 to APP template 11 2. Relationship from D template 19 to APP template 11 3. The relationship setting unit 62 establishes a relationship between the template folders through an operation performed by the operator introducing the relationship from M template 14 to D template 19 (S14). Specifically, the relationship setting unit 62 selects one folder from the folders set in D template 19 as the target. The relationship setting unit 62 searches for the folder tags of APP template 11 using relationship information (Relation Hints). The relationship setting unit 62 establishes a relationship between the APP template 11 folder that matches the search and the currently selected target folder in D template 19. At this time, the relationship setting unit 62 identifies the link rules of each data point in the related folder of APP template 11 and sets the Relation Id in Device Relationship. The relationship setting unit 62 performs the same process between M template 14 and D template 19, and between M template 14 and APP template 11.

[0104] If relation information is not defined in template D 19 (i.e., the source folder cannot be identified), the relation setting unit 62 can search for both the folder tags in template APP 11 and the folder tags in template D 19 using relation hints.

[0105] Next, the link creation unit 63 searches for the tags of data points in the related folders using the link rules in order to create a link (S15). For example, the link creation unit 63 sets the links in the following order: 1. From M template 14 to D template 19 2. From APP template 11 to M template 14 3. From APP template 11 to D template 19 However, 1 and 2 can be done in any order. Since the link between APP template 11 and D template 19 is preferably done only if there are no data points in M ​​template 14, 3 should be done last.

[0106] First, the link creation unit 63 selects any data point in any folder of the M template 14 as its target. The link creation unit 63 obtains the link rule associated with the selected data point (see Figure 15). The link creation unit 63 identifies the folder in the D template 19 based on the relationship identified by the Relation Id of the link rule. The link creation unit 63 searches for the tags of the data points contained in this folder using the Point Query of the link rule.

[0107] The link creation unit 63 determines whether there were any data points that matched the search performed by Point Query (S16).

[0108] If the link creation unit 63 finds a data point that matches the Point Query in step S16 (Yes in S16), it creates a link between the data point in the folder of the M template 14 selected as the target and the data point in the folder of the D template 19 that matches the search (S17).

[0109] If no data points matching the search are found in step S16 (No. in S16), the link creation unit 63 determines whether there is a link rule associated with the next data point in any folder of the M template 14 (S18).

[0110] Once the search for all data points in all folders of M template 14 is complete, the link creation unit 63 creates links to the data points in the folders of M template 14 based on the link rules associated with the data points in the folders of APP template 11. As a result of setting the links between the folders of M template 14 and the folders of APP template 11, the link creation unit 63 creates links to the data points in the folders of D template 19 based on the link rules for the data points in the folders of APP template 11 that are not associated with M data points 15 (the remaining data points).

[0111] If the following link rule exists, the process returns to step S15 (S19); otherwise, the process in Figure 18 ends.

[0112] As a result of the above process, relationships are established between folders, as shown in Figure 16, and links are set between data points within the related folders. This reduces the effort required for the implementation worker to connect data points and also reduces errors.

[0113] <Data Format Conversion> Next, referring to Figure 19, etc., the relaying of data and conversion of data format by the data conversion template 31 will be explained. The data conversion template 31 has a conversion data point 34 set up, and the conversion data point 34 converts the data format and relays the data from the D data point 16 to the M data point 15, or relays the data from the M data point 15 to the D data point 16.

[0114] Figures 19A to 19C illustrate the data formats. As shown in Figures 19A to 19C, there are, for example, three data formats: (i) Boolean (ii) Numeric (iii) Multi. Boolean is a data format that takes two values: True or False. For example, the Boolean value taken by the M data point 15 that controls the ON and OFF states of the air conditioner can be True (representing ON) or False (representing OFF).

[0115] Numeric is a data format that takes the form of a single numerical value. The value can be either an integer or a decimal. For example, the Numeric value taken by M data point 15, which displays the indoor temperature of a room, could be 24.6°C, and the Numeric value taken by M data point 15, which displays the humidity of a room, could be 62%.

[0116] Multi is a data format that has values ​​in the format "key: value". The key can be an integer, and the value can be true / false, a number, or a string. For example, the Multi format value taken by the M data point 15 that controls the operating mode of the air conditioner may be "1: Automatic", "2: Cooling", "3: Heating", "4: Fan", or "5: OFF".

[0117] The data conversion template 31 can convert Boolean, Numeric, and Multi data formats from one to the other, and vice versa.

[0118] Figure 20 shows an example of data conversion, specifically the conversion of Multi to Boolean and Multi. The conversion example in Figure 20 is for a case where the D template 19 does not have a D data point 16 that displays whether the air conditioner is ON or OFF, but the M template 14 is specified to display whether the air conditioner is ON or OFF. The conversion example in Figure 20 is a data conversion that converts the Multi format data held by the D data point 16 to Boolean and Multi format data held by the M data point 15.

[0119] The D data point 16 of the D template 19 is a D data point 16 that displays the operating mode. The data format is Multi, and the D data point 16 has the values ​​"1: Automatic", "2: Cooling", "3: Heating", "4: Fan", and "5: OFF".

[0120] On the other hand, in M ​​template 14, the installer wants to display whether the air conditioner is ON or OFF. Also, M template 14 has a Multi-type data format, but the "key: value" is different from the "key: value" of D template 19.

[0121] Therefore, the data conversion template 31 performs the following conversions. First, the data conversion template 31 converts the Multi-format values ​​indicated by the D data point 16, "1: Automatic," "2: Cooling," "3: Heating," and "4: Fan," into Boolean format ON, and similarly converts "5: OFF" to OFF. In the M template 14, ON corresponds to True and OFF corresponds to False. The data conversion template 31 also converts the correspondence between the keys of the Multi-format D template 19 and the Multi-format M template 14. That is, the data conversion template 31 does not change keys 1 to 4, but converts key 5 to key 0. In the M template 14, 1 corresponds to Automatic, 2 to Cooling, 3 to Heating, 4 to Fan, and 0 to OFF.

[0122] Through this conversion, the M template 14 can display ON or OFF even if the D data point 16 is not in Boolean data format. Furthermore, the M template 14 can display the operating mode in Multi format even if the correspondence between the keys of the D template 19 and the M template 14 is different.

[0123] In this case, the link creation unit 63 connects the Multi-format D data point 16 of the D template 19 to the Boolean→Multi conversion data point 34c of the data conversion template 31. The data conversion template 31 converts to True or False depending on key=1 to 4, or key=5.

[0124] Furthermore, the link creation unit 63 connects the Multi-format D data point 16 of the D template 19 to the conversion data point 34d for Multi-to-Multi conversion of the data conversion template 31. The data conversion template 31 does not convert keys 1 to 4, but converts key 5 to key 0.

[0125] Furthermore, the link creation unit 63 connects the conversion data point 34c for Boolean→Multi conversion of the data conversion template 31 to the Boolean format M data point 15c of the M template 14. The link creation unit 63 also connects the conversion data point 34d for Multi→Multi conversion of the data conversion template 31 to the Multi format M data point 15d of the M template 14.

[0126] As a result, the Multi-format data held by the D data point 16 of the D template 19 is converted into Boolean format data and Multi-format data by the data conversion template 31 and sent to the Boolean format and Multi-format M data point 15 of the M template 14.

[0127] <Relationship between Data Conversion Template and D Template and M Template> Refer to Figure 3 to explain the relationships and links of the data conversion template. As shown in Figure 3, the data conversion template 31 is placed between the D template 19 and the M template 14, so relationships are established between these folders. In Figure 3, relationship 28a is set between folders 35a and 39a, and relationship 29a is set between folders 33a and 39a. Relationship 28b is set between folders 35b and 39b, and relationship 29b is set between folders 33b and 39b.

[0128] When setting up links, the link rules associated with the conversion data points 34a to 34d of the data conversion template 31 are used in priority over the link rules on the M template 14 side. This prevents the folders of the M template 14 and the data points of the D template 19 from being linked together even though the data conversion template 31 exists.

[0129] Therefore, the link creation unit 63 creates a link starting from the data conversion template 31 a total of two times, once on the D template 19 side and once on the M template 14 side. The link creation unit 63 searches for the tag of the D data point 16 using the Point Query of the link rule (for device data points) that the data conversion template 31 has. The link creation unit 63 searches for the tag of the M data point 15 using the Point Query of the link rule (for model data points) that the data conversion template 31 has.

[0130] If a match is found in the search, the link creation unit 63 connects the D data point 16 of the D template 19 (fan on / off in Figure 3) to the conversion data points 34a and 34c of the data conversion template 31. The link creation unit 63 also connects the M data point 15 of the M template 14 (fan on / off in Figure 3) to the conversion data points 34b and 34d of the data conversion template 31.

[0131] <Connection when M template is not available> Figure 21 shows an example of setting up relationships and links when M template 14 is not available. The processing flow when setting up links is the same as in Figure 18. Since M template 14 is not available, the process of establishing a relationship with the folder of M template 14 is skipped. Similarly, the process of establishing a link with the M data point 15 of M template 14 is skipped.

[0132] In other words, because there is no M template 14, a relationship 25a is established between folder 37a of APP template 11 and folder 35a of D template 19. A relationship 25b is established between folder 37b of APP template 11 and folder 35b of D template 19.

[0133] Furthermore, since there is no M template 14, the link creation unit 63 creates links between the APP data points 17a-17c and 17d-17f in folder 37a of the APP template 11 and the respective D data points 16a-16c and 16d-16f of the D template 19. Therefore, links are set to the data points as follows: D data point 16a to APP data point 17a, D data point 16b to APP data point 17b, D data point 16c to APP data point 17c, D data point 16d to APP data point 17d, D data point 16e to APP data point 17e, and D data point 16f to APP data point 17f.

[0134] <Main Effects> Compared to manually connecting data points, the information processing method disclosed here reduces errors by the implementation worker and decreases the man-hours required for on-site connection testing. By reducing the man-hours required to build the equipment management system 100, it is possible to lower necessary expenses.

[0135] <Other Application Examples> While the best mode for implementing this disclosure has been described above using examples, this disclosure is not limited to these examples, and various modifications and substitutions can be made without departing from the gist of this disclosure.

[0136] For example, although this disclosure describes an equipment management system 100, it can be suitably applied when connecting one data point and another data point within the software.

[0137] Furthermore, the process of automatically associating data points may be performed by the correspondence information creation device 60 instead of the equipment management device 10.

[0138] Furthermore, the configuration examples in Figure 5 and other figures are divided according to their main functions to facilitate understanding of the processing performed by the equipment management device 10. This disclosure is not limited by the way the processing units are divided or their names. The processing of the equipment management device 10 can be further divided into many more processing units depending on the processing content. It can also be divided so that one processing unit includes even more processing.

[0139] Furthermore, the apparatus described in the examples represents only one of several computing environments for carrying out the embodiments disclosed herein. In one embodiment, the corresponding information creation apparatus 60 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a network or shared memory, and perform the processing disclosed herein.

[0140] Each of the functions of this disclosure described above can be implemented not only by software processing through program execution, but also by one or more processing circuits. Here, "processing circuit" as used herein includes processors programmed to execute each function by software, such as processors implemented by electronic circuits, as well as devices such as ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to execute each of the functions described above.

[0141] <Reasons for the effect> The first aspect of this disclosure performs the steps of "associating a first data storage location in a first template with a second data storage location in a second template based on identification information of the first and second data storage locations, and associating a first data point stored in the first data storage location with a second data point stored in the second data storage location associated with the first data storage location based on identification information of the first and second data points," so that the association between the first data point in the first template and the second data point in the second template can be performed automatically.

[0142] A second aspect of this disclosure associates a device data storage location with an application data storage location based on relation information, and associates a model data storage location with the device data storage location, or the model data storage location with the application data storage location. Therefore, developers can automatically associate data storage locations by creating relation information.

[0143] A third aspect of this disclosure states that, "if there are data points in the app data storage location that are not associated with the data points in the model data storage location, the data points in the app data storage location that were not associated with the data points in the model data storage location are associated with the data points in the device data storage location based on the identification information possessed by the data points in the app data storage location and the data points in the device data storage location." This allows for prioritization of associating data points in the app data storage location with data points in the model data storage location, and also allows associating data points in the app data storage location that are not associated with data points in the device data storage location.

[0144] A fourth aspect of this disclosure involves "associating the device data storage location with the application data storage location, associating the model data storage location with the device data storage location based on the relation information held by the model template, and associating the model data storage location with the application data storage location based on the relation information held by the model template," thereby ensuring that data storage locations are associated with each template without any omissions.

[0145] A fifth aspect of this disclosure determines the order in which data storage locations placed in a template are loaded into memory, and associates data storage locations between templates according to that order, so that the association of data storage locations can be performed after the data storage location to be associated has been loaded into memory.

[0146] A sixth aspect of this disclosure determines the order in which data storage locations placed in a template are loaded into memory, and associates data storage locations between templates according to that order, so that the association of data storage locations can be performed after the data storage location to be associated has been loaded into memory.

[0147] A seventh aspect of this disclosure relates a data conversion template for converting data formats to a data conversion template, which associates the conversion data storage location of the data conversion template with the device data storage location, and the conversion data storage location with the model data storage location, based on the identification information of each storage location, and associates the data points of the conversion data storage location with the data points of the model data storage location, and the data points of the conversion data storage location with the data points of the device data storage location, based on the identification information of each data point. Therefore, even if a data storage template exists, the data points can be automatically associated using the same processing method.

[0148] This application claims priority based on Japanese Patent Application No. 2024-166595, filed with the Japan Patent Office on September 25, 2024, and the entire contents of Japanese Patent Application No. 2024-166595 are incorporated herein by reference.

[0149] 10 Equipment management device 14 Model template 15 Data point 16 Device data point 17 Application data point 20 Equipment 60 Corresponding information creation device 100 Equipment management system

Claims

1. An association method performed by an information processing device that processes data relating to equipment, wherein the control unit performs the following steps: a step of associating a first data storage location in a first template and a second data storage location in a second template, based on identification information of the first data storage location and the second data storage location, in a template having data storage locations for classifying and storing data points that the data is input or output from.

2. The association method according to claim 1, wherein the template comprises a device template for data points that input or output data with the equipment, an application template for data points that input or output data with the control logic, and a model template for data points that input or output data between the device template and the application template, and the control unit associates the device data storage location of the device template with the application data storage location of the application template, the model data storage location of the model template with the device data storage location, or the model data storage location with the application data storage location, based on relation information defining the data storage locations to be associated.

3. If, as a result of the control unit associating the data points of the application data storage location with the data points of the model data storage location, there are data points in the application data storage location that are not associated with the data points of the model data storage location, the association method according to claim 2, wherein the data points of the application data storage location that were not associated with the data points of the model data storage location are associated with the data points of the device data storage location based on the identification information possessed by the data points of the application data storage location and the data points of the device data storage location.

4. The association method according to claim 2, wherein the relation information is defined in the model template and the device template, the control unit associates the device data storage location with the application data storage location based on the relation information defined in the device template, associates the model data storage location with the device data storage location based on the relation information in the model template, and associates the model data storage location with the application data storage location based on the relation information in the model template.

5. The association method according to claim 2, wherein the control unit expands the application data storage location located in the application template into memory, then expands the device data storage location located in the device template into memory, then expands the model data storage location located in the model template into memory, associates the device data storage location with the application data storage location, and then associates the application data storage location with the model data storage location, or associates the device data storage location with the model data storage location, in any order.

6. The association method according to claim 2, wherein the control unit expands the application data storage location located in the application template into memory, then expands the model data storage location located in the model template into memory, then expands the device data storage location located in the device template into memory, associates the model data storage location with the application data storage location, associates the application data storage location with the device data storage location, and associates the device data storage location with the model data storage location.

7. The association method according to claim 2, wherein the template further includes a data conversion template for converting the format of the data, and the control unit, based on the relation information, associates the converted data storage location and the device data storage location, and the converted data storage location and the model data storage location, based on the identification information of the converted data storage location, the device data storage location and the model data storage location, associates the data points of the converted data storage location and the data points of the model data storage location, and associates the data points of the converted data storage location and the data points of the device data storage location, based on the identification information of the data points of the converted data storage location, the device data storage location and the model data storage location.

8. Equipment management device for processing data relating to equipment, wherein the control unit has a template in which data storage locations are arranged for classifying and storing data points that the data is input or output from, and associates a first data storage location in a first template with a second data storage location in a second template based on identification information of the first data storage location and the second data storage location, and associates a first data point stored in the first data storage location with a second data point stored in the second data storage location associated with the first data storage location based on identification information of the first data point and the second data point.

9. A program to be executed by an information processing device that processes data relating to equipment, wherein the control unit of the information processing device has a template in which data storage locations for classifying and storing data points for which the data is input or output is arranged, the program to cause the control unit to execute: a step of associating a first data storage location in a first template with a second data storage location in a second template based on identification information of the first data storage location and the second data storage location; and a step of associating a first data point stored in the first data storage location with a second data point stored in the second data storage location associated with the first data storage location based on identification information of the first data point and the second data point.

Images