Association method, facility management device, and program

Abstract

Automatically make associations between data points. [Solution] The present disclosure provides an association method performed by an information processing device that processes data related to equipment, in which a control unit performs the following steps: associating a first data storage location of a first template with a second data storage location of a second template based on identification information held by the first data storage location and the second data storage location; and associating a first data point stored in the first data storage location with a second data point stored in a second data storage location associated with the first data storage location based on identification information held by the first data point and the second data point.

Description

[Technical Field]

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

[0002] When introducing software into a facility management system such as a BMS (Building Management System), the process of registering facility equipment into the software is required. The software provides multiple templates for this process, and data points can be placed in the templates. Data points are nodes for inputting or outputting data related to facility equipment.

[0003] Patent Document 1 discloses a technology that automatically generates and updates document files and applications, such as instruction manuals for industrial plants and control logic definitions and specifications, based on centrally managed design data in order to reduce the amount of work required when building a BMS. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] U.S. Patent No. 100108183 Summary of the Invention [Problem to be solved by the invention]

[0005] However, with conventional technology, data points placed on templates had to be associated with each other manually. This required a lot of work for installation workers to manually associate data points one by one. When multiple devices are installed, the number of data points increases by the number of devices, resulting in a huge number of data points, requiring even more work and potentially leading to errors.

[0006] The present disclosure provides techniques for automatically making associations between data points. [Means for solving the problem]

[0007] A first aspect of the present disclosure is An association method performed by an information processing device that processes data related to facility equipment, The control unit A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; 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 data point and the second data point.

[0008] According to the first aspect of the present disclosure, association between data points can be performed automatically.

[0009] A second aspect of the present disclosure is the association method according to the first aspect, the templates are a device template for a data point that inputs or outputs data between the equipment, an application template for a data point that inputs or outputs data between the equipment and a control logic, and a model template for a data point that inputs or outputs data between the device template and the application template; The control unit, based on relation information that defines the data storage location to be associated, The device data storage location of the device template is associated with the application data storage location of the application template, the model data storage location of the model template is associated with the device data storage location, or the model data storage location is associated with the application data storage location.

[0010] A third aspect of the present disclosure is the association method according to the second aspect, 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 app data store that are not associated with data points in the model data store, The application data store data points that were not associated with the model data store data points are associated with the device data store data points based on identification information possessed by the application data store data points and the device data store data points.

[0011] A fourth aspect of the present disclosure is the association method according to the second aspect, the relationship 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 relationship information defined in the device template; Associating the model data storage location with the device data storage location based on the relation information included in the model template; The model data storage location and the application data storage location are associated with each other based on the relation information included in the model template.

[0012] A fifth aspect of the present disclosure is the association method according to the second aspect, The control unit expands, based on the application template, an application data storage location arranged in the application template into a memory, and then Based on the device template, the device data storage location arranged in the device template is expanded in a memory, and then Based on the model template, the model data storage location arranged in the model template is expanded in a memory; After associating the device data storage location with the application data storage location, The application data storage location and the model data storage location are associated with each other, or the device data storage location and the model data storage location are associated with each other, in any order.

[0013] A sixth aspect of the present disclosure is the association method according to the second aspect, The control unit expands, based on the application template, an application data storage location arranged in the application template into a memory, and then Based on the model template, the model data storage location arranged in the model template is expanded in a memory, and then Based on the device template, the device data storage location arranged in the device template is expanded in a memory; After associating the model data storage location with the application data storage location, The application data storage location and the device data storage location or the device data storage location and the model data storage location are associated with each other in any order.

[0014] A seventh aspect of the present disclosure is the association method according to the second aspect, the template is further a data conversion template that converts the format of the data; The control unit, based on the relation information, associates the conversion data storage location and the device data storage location, and the conversion data storage location and the model data storage location, which are included in the data conversion template, based on identification information included in the conversion data storage location, the device data storage location, and the model data storage location; The data points of the transformation data storage location are associated with the data points of the model data storage location, and the data points of the transformation data storage location are associated with the data points of the device data storage location based on identification information possessed by the data points of the transformation 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 that processes data related to equipment, The control unit A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, Associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; A first data point stored in the first data storage location is associated with a second data point stored in the second data storage location associated with the first data storage location based on identification information possessed by the first data point and the second data point.

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

[0017] A ninth aspect of the present disclosure is A program executed by an information processing device that processes data related to facility equipment, A control unit included in the information processing device, A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; and associating first data points stored in the first data storage location with second data points stored in the second data storage location associated with the first data storage location based on identification information of the first data points and the second data points.

[0018] According to the ninth aspect of the present disclosure, association between data points can be performed automatically. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is an example of a system configuration diagram of a facility management system in which a facility management device controls various facility devices via a network. [Figure 2] FIG. 1 is a diagram illustrating data points and their connections. [Figure 3] FIG. 10 is a diagram showing an example of connections between data points in each template in the tool software. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of an equipment management device and a correspondence information creation device. [Figure 5] FIG. 2 is a functional block diagram of an example of a correspondence information creating device on which tool software runs. [Figure 6] 10A and 10B are diagrams illustrating folder information related to folders deployed in each template. [Figure 7] FIG. 1 is a diagram illustrating tabs for one spreadsheet file. [Figure 8] FIG. 10 illustrates an example of application template information stored in an application template information storage unit. [Figure 9]10 is a diagram illustrating an example of device template information stored in a device template information storage unit. FIG. [Figure 10] FIG. 4 is a diagram illustrating an example of model template information stored in a model template information storage unit. [Figure 11] FIG. 10 is a diagram illustrating an example of data point information of a folder of a D template. [Figure 12] 10A and 10B are diagrams showing an example of data point information of an M template folder and an example of link rule information associated with an M template. [Figure 13] 10A and 10B are diagrams showing an example of data point information of an APP template folder and an example of link rule information associated with the APP template. [Figure 14] 10A and 10B are diagrams illustrating an example of data point information of a folder of a data transformation template and an example of link rule information associated with the data transformation template. [Figure 15] FIG. 10 is a diagram illustrating an example of a link rule. [Figure 16] FIG. 10 is a diagram showing an example of relations set between folders and links set between data points. [Figure 17] FIG. 10 is a flowchart illustrating an example of operations that an installation operator performs on a correspondence information creation device on which tool software runs. [Figure 18] FIG. 10 is a flowchart illustrating an example of a process in which the tool software connects data points in the APP template, M template, and D template. [Figure 19] FIG. 2 is a diagram illustrating a data format. [Figure 20] FIG. 10 is a diagram showing an example of converting Multi to Boolean and Multi as an example of data conversion. [Figure 21] FIG. 10 is a diagram illustrating an example of setting relations and links when there is no M template. DETAILED DESCRIPTION OF THE INVENTION

[0020] Hereinafter, an equipment management system and an association method performed by the equipment management system will be described as an example of an embodiment of the present disclosure.

[0021] <About the facility management system> Facility management systems are installed in many properties, including 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 is no strict definition for these, but we will briefly explain each of them.

[0022] BAS is a system that automatically controls the facilities in a property. It can centrally control and monitor all the facilities and equipment, such as air conditioning, lighting, security systems, and power meters, that were previously managed manually by the property manager, via a network.

[0023] BEMS is a system for managing energy consumption in properties. 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 allows you to compare it with data from the previous day, month, and year, making it easier to determine whether current energy consumption is appropriate.

[0024] A BMS is a system that monitors and controls various equipment in a property, including power, air conditioning, lighting, disaster prevention, and crime prevention. A wide variety of these equipment units are in operation in properties such as office buildings. To maintain these units in a safe state and ensure they function as intended, it is necessary to monitor their status and immediately detect any abnormalities that may occur. Furthermore, if managers can operate equipment remotely and change settings remotely, without having to operate them directly, the workload can be reduced.

[0025] BACS is a system that combines BAS, BMS, and BEMS, although not strictly speaking, and is registered in ISO:16484-5.

[0026] In the following, we will not distinguish between BAS, BEMS, BMS, BACS, or similar equipment or property systems, and will refer to them as equipment management systems.

[0027] <Terminology> A data point is a software node that holds data input to or output from equipment. Data points are connected to other data points to supply data to functions that require it.

[0028] A data repository is a facility for storing one or more data points together. For a device template, the one or more data points are organized by equipment model number. For a model template, the one or more data points are organized by equipment type. For an application template, the one or more data points are organized by equipment model number. In this disclosure, data repository is described in terms of folders.

[0029] There are several types of templates depending on the purpose, and they are models that have basic settings and data processing pre-installed depending on the purpose. In templates, installation workers can place appropriate data points (data storage locations) for equipment and devices. Templates include device templates, model templates, application templates, and data conversion templates. Device templates provide functions for inputting or outputting data to or from equipment and devices, model templates provide user interface functions such as data display, and application templates provide functions such as data processing logic.

[0030] <System configuration example> FIG. 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 FIG. 1, the equipment management device 10 and various equipment 20 are communicatively connected via a network N1. This network N1 may be, for example, BACnet. BACnet is a network through which the equipment management system 100 communicates with the various equipment 20 using the BACnet protocol. The network N1 may use a dedicated cable, or an Ethernet cable (registered trademark) similar to a normal LAN. The equipment management system 100 does not need to use the BACnet protocol for network communication; the BACnet protocol is merely an example. For example, the communication protocol may be Modbus or the like.

[0031] The illustrated facility devices 20 include, for example, air conditioners, lighting devices, security devices, disaster prevention devices, power devices, and elevators, but these are merely examples. Also, multiple units of the same device, such as air conditioners, may be connected. A gateway device called a BACnet gateway may be placed between the facility devices 20 and BACnet. The BACnet gateway converts communication data compatible with the BACnet protocol into communication data compatible with the communication protocol supported by each facility device 20, and converts communication data compatible with the communication protocol supported by each facility device 20 into communication data compatible with the BACnet protocol. The communication protocol supported by each facility device 20 is a proprietary communication protocol established by the company that manufactured the facility device 20. Therefore, the facility devices 20 may be manufactured by different companies or brands.

[0032] The equipment management device 10 has web server functionality, and creates screens for managing the equipment 20 in HTML or the like, and transmits them to the terminal device 50 via the network N2. The network N2 is, for example, the Internet. A user can monitor the equipment 20 by connecting the terminal device 50 to the equipment management device 10 from any location. Even if the terminal device 50 is not available, the user can monitor the equipment 20 by directly operating the console (display and keyboard) of the equipment management device 10.

[0033] In addition, a correspondence information creation device 60 is communicatively connected to the network N2. The correspondence information creation device 60 only needs to be able to communicate with the equipment management device 10 via the network N2, and does not need to be constantly connected to the network N2. When connecting 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) described in the present disclosure, the correspondence information creation device 60 can process the connections independently. In this embodiment, the connections between data points may be implemented by either the equipment management device 10 or the correspondence information creation device 60.

[0034] The equipment management device 10 or the correspondence information creation device 60 may be any information processing device with an OS such as Windows (registered trademark) installed. The equipment management device 10 or the correspondence information creation device 60 has tool software installed, which will be described later, and performs processing to connect (or associate) APP data points, M data points, and D data points (these will be described in detail later). Hereinafter, the term "connect" will be used in this disclosure. Note that the correspondence information creation device 60 may be a PC (Personal Computer), tablet terminal, smartphone, etc., as long as it is capable of running the tool software.

[0035] In BACnet, the functions of equipment 20 are handled under the concept of objects. An object is a representation of various pieces of information grouped together, and in BACnet, information related to an object is called a property. For example, if an air conditioner were an object, the control capabilities of the air conditioner (temperature, air volume, etc.) would correspond to the property. In BACnet, reading or writing an object or related properties is called a service. For the sake of convenience, in the following explanation of this disclosure, objects and properties are not distinguished from each other and are simply referred to as "data points."

[0036] <Software structure within information processing systems> FIG. 2 is a diagram explaining data points and their connections. Tool software 8 runs on equipment management device 10. First, tool software 8 has station template 9, application template (hereinafter sometimes referred to as APP template 11), device template 19 (hereinafter sometimes referred to as D template 19), model template 14 (hereinafter sometimes referred to as M template 14), and data conversion template 31. Tool software 8 is an implementation tool for connecting data points using these templates. Once data points are connected, applications for equipment management system 100 that control equipment 20 become executable. Station template 9 is an abstraction of 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 autolink module. The APP template 11 also has control logic 12A-12C. Any of the control logic 12A-12C is referred to as "control logic 12." Control logic refers to various calculations performed according to data. The APP template 11 is a template that packages the data points 17, a folder containing an autolink module 21, and multiple pieces of control logic 12A-12C. The autolink module 21 sets up links (between the app and model / app and device) for the APP template 11, as described below.

[0038] The D template 19 is a template that defines all D data points 16 that equipment holds for each equipment model number. The M template 14 is a template that defines standard M data points 15 for each category of building equipment. The D template 19 has D data points 16 that depend on the equipment model number, while the 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. The M template 14 has an autolink module 22, and the autolink module 22 sets up links (between models and devices) for the M template 14, as described below.

[0039] Previously, installation workers manually connected APP data points 17, D data points 16, and M data points 15. However, this was a cumbersome process, which increased the number of steps and made it prone to errors.

[0040] Therefore, in this embodiment, the developer assigns a tag to each data point. The tag is identification information for the data point, and in FIG. 2, it can be thought of as a circled number and a tag. The tool software 8 connects the data points in the APP template 11, D template 19, and M template 14 based on link rules (described below) that stipulate that data points with the same tag information should be connected. Note that the control logic 12 of the APP template 11 can be connected to data points in both the D template 19 and the M template 14.

[0041] <Examples of connecting data points and relationships> FIG. 3 is a diagram showing an example of connections between data points in each template in the tool software 8. FIG. 3 shows the elements of FIG. 2 arranged horizontally, with the same configuration. However, FIG. 3 explains the function of each template in more detail. FIG. 3 also includes specific examples of data points in each template. The installation technician deploys the APP template 11, D template 19, and M template 14 in the tool software 8 to create application functions for the equipment management system 100.

[0042] D data points 16 are placed in the D template 19. The D data points 16 are generated for each model number of the equipment 20. The D template 19 defines the D data points 16 of all data input or output by the equipment 20. A tag (identification information specifying, 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. The folders 35a, 35b are generated for each model number of the equipment 20. Therefore, D data points 16 with the same model number are grouped together 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 that have the same tag in a single D template 19.

[0043] M data points 15 are placed in the M template 14. M data points 15 that are common to all types of equipment 20 are defined in the M template 14. A tag is also defined for each M data point 15. One or more M data points 15 are stored in folders 33a and 33b. Folders 33a and 33b are generated for each type of equipment 20. Thus, the folders 33a and 33b of the M template 14 cover data that is common to all types of equipment. By classifying the M data points 15 in folders, the equipment management device 10 can generate different M data points 15 that have the same tag in a single M template 14.

[0044] A plurality of control logics 12A to 12C are arranged in the APP template 11. For example, the control logic 12A processes the room temperature, the control logic 12B processes the fan on / off, and the control logic 12C processes the air outlet temperature. In addition, the control logic can be equipped with various functions such as energy-saving operation control across multiple air conditioners, operation control according to a schedule, and abnormality management (alarms).

[0045] Because the control logic 12A to 12C input or output data such as room temperature, fan on / off, and air outlet temperature, the APP template 11 is provided with APP data points 17 for inputting or outputting data used by the control logic 12. The APP data points 17 generally correspond to the D data points 16. A tag is defined for each APP data point 17. One or more APP data points 17 are stored in folders 37a and 37b. The folders 37a and 37b in the APP template 11 are created for each model number of the equipment 20. The equipment management device 10 classifies the APP data points 17, allowing different APP data points 17 with the same tag to be created in a single APP template 11.

[0046] Since the number of data points for each model is greater than 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, folder 35a of D template 19 has three D data points 16. Folder 33a of M template 14 has three M data points 15. Folder 37a of 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. In some cases, the D data points 16 are directly connected to the APP data points 17. The three M data points 15 in folder 33a are automatically connected to the three APP data points 17 in folder 37a based on tags. The same connection is made for folders 35b, 33b, and 37b.

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

[0049] In this way, the tool software 8 simply connects data points on one template with data points on another template. However, one template may contain multiple data points with the same tag. For example, if the room temperature, fan on / off, and air outlet temperature are tags, each tag may exist multiple times in one template. When the tool software 8 automatically connects data, it cannot determine whether to connect the room temperature in folder 35a to the room temperature in folder 33a or the room temperature in folder 33b.

[0050] Therefore, in this embodiment, the relation setting unit 62 sets relations between folders. For this purpose, the developer also sets tags (tags separate from data points) to folders. 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 below, 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, a relationship 27a is established between folder 37a of APP template 11 and folder 33a of M template 14. A relationship 25a is established between folder 37a of APP template 11 and folder 35a of D template 19. A relationship 26a is established between folder 33a of M template 14 and folder 35a of D template 19. Connections between data points are made within these relationships. Although relationships are omitted for folders 37b, 33b, and 35b, relationships are established similarly.

[0052] The APP data points 17, D data points 16, and M data points 15 each hold data. The data held by the D data points 16 can be referenced by the equipment 20, and the data set in the M data points 15 can be displayed on the user interface. The data set in the APP data points 17 can be referenced by the control logic 12. The equipment management system handles a variety of data, and the room temperature, fan on / off, and air outlet temperature are merely examples.

[0053] The M data point 15 receives data sent 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 for display. The D data point 16 receives data sent from the M data point 15 connected to the D data point 16 and sends it to the equipment 20. The APP data point 17 receives data sent 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 by the control logic 12. The M data point 15 receives data sent from the APP data point 17 connected to the M data point 15 and displays it or sends it to the D data point 16.

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

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

[0056] The ROM 502 stores programs such as IPL used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information such as a cursor, menu, window, text, or image. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external devices are, for example, USB (Universal Serial Bus) memories, printers, etc. The network I / F 509 is an interface for data communication using the networks N1 and N2. The bus line 510 is an address bus, data bus, etc. for electrically connecting the components such as the CPU 501 shown in FIG. 4.

[0057] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The optical drive 514 controls reading and writing of various data from an optical storage medium 513, which is an example of a removable storage medium. The optical storage medium may be a CD, DVD, Blu-Ray (registered trademark), etc. The media I / F 516 controls reading and writing (storing) of data from a storage medium 515, such as a flash memory.

[0058] <About the function> 5 is a functional block diagram of an equipment management device 10 on which tool software 8 runs. The equipment management device 10 has a display control unit 61, a relation setting unit 62, a link creation unit 63, and an operation reception unit 64. Each of these functional units in 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 FIG. 5 executing instructions contained in one or more programs installed in the equipment management device 10. This program may be, for example, tool software 8.

[0059] The equipment management device 10 also has 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 constructed in the HD 504, RAM 503, etc. shown in FIG.

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

[0061] The relation setting unit 62 sets relations between folders. Setting relations is sometimes referred to as "establishing a relation." The relation setting unit 62 searches for tags of folders in different templates using a search key set in the relation information described below. The relation setting unit 62 establishes a relation between folders that match the search. The relation limits the range of data points to be searched. The order in which the relation setting unit 62 establishes relations between template folders is predetermined. Details will be described later, but the order in which each template is expanded into memory is also determined so that relations can be established in this order.

[0062] The link creation unit 63 creates a link between one folder in which a relation is established and a data point in the other folder. This link corresponds to the connection (association) between data points in this disclosure. The link creation unit 63 searches for tags held by data points in the relation using a search key set in a link rule, which will be described later. This identifies two data points from different templates.

[0063] The operation receiving unit 64 receives various operations performed by the installation worker on the tool software 8 running on the correspondence information creating device 60 .

[0064] <Folder information> Figure 6 shows a schematic diagram of folder information related to folders deployed in each template. Figure 6(a) shows folder information for the APP template 11, Figure 6(b) shows folder information for the D template 19, and Figure 6(c) shows folder information for the M template 14.

[0065] The folder information for each template has a tag. The tag in Figure 6 is the identification information for the folder. This tag is searched to establish relationships between folders. In Figure 6, different folders within the template have the same tag, but this does not cause any problems because relationships are established between folders with the same number at the end of the folder name ("1" for folder 1). Also, if the number at the end of the folder name is not used to set relationships, the developer can simply set a different tag for each folder.

[0066] <Template information> Template information will be described with reference to FIG. 7 and other figures. First, FIG. 7 shows the tabs of one spreadsheet file. Each tab lists application template information, device template information, and model template information. In this way, the template information is included in one spreadsheet file, but the application template information, device template information, and model template information may also be stored in separate files.

[0067] The application template information defines the APP template 11 that includes a folder, the device template information defines the D template 19 that includes a folder, and the model template information defines the M template 14 that includes a folder. When these spreadsheet files (D template 19, M template 14, APP template 11) are expanded into memory, the order of expansion is important. In order to establish a relationship, the folder to which the relationship is to be established must already exist in memory. For this reason, in this embodiment, APP Template 11 > D Template 19 > M Template 14 The tool software 8 expands the template in the memory in the above order.

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

[0069] 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 about each folder. Of these, column 301 contains bibliographic information about the equipment. Column 302 contains relation information 303 and folder names 304. The Relation Id on the third line of the relation information 303 is identification information that identifies the relation between the set folders. When a relation is established, this Relation Id is set in the link rule, which will be described later. The Relation Hints on the fourth line of the relation information 303 is a search key for searching for tags attached to a folder. "h4:indoor and dk:app" indicates that "h4:indoor" and "dk:app" are an AND condition. In other words, "and" is a logical operator. Logical operators such as "or," "not," and "xor" can also be used. Note that the relationship setting starting from the D template 19 targets only the APP template 11, so there is only one Relation Hint. Because the relation information 303 is linked to a folder, the source folder is already determined and there is no need to search for the tags of the source folder. However, there is no problem if the source folder is searched. The Direction on the fifth line of the relation information 303 indicates the direction in which data flows between data points.

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

[0071] A relation is not related to the transfer of data, but rather indicates a place to create a link. A good example of a relation is a relationship between folders in different templates.

[0072] 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 similar to the structure of the device template information, so only the differences will be explained.

[0073] The Relation Hints on the fourth line are search keys for searching for tags attached to folders. Two search keys are set in the model template information. Specifically, the search keys are "h4:indoor and dk:device" and "h4:indoor and dk:app." The search key on the left is for searching for tags in the folder of D template 19, and the search key on the right is for searching for tags in the folder of APP template 11. The left and right search keys also define the order in which relations are established; in relation settings starting from M template 14, a relation is established first for the folder of D template 19, and then for the folder of APP template 11.

[0074] <<Data point information in the folder generated for each template>> Next, the information held by data points in folders created in each template will be described with reference to Fig. 11 etc. Fig. 11 is an example of data point information for folders in D template 19. The data point information has items such as model number ID, tag, device data point ID, and belonging folder. The model number ID field stores identification information of the model number of the facility device 20. The tag field stores the name used by the installation worker to identify the D data point 16. The tag field stores the tag to be searched. The tag of the D data point 16 is searched when setting up a link. The device data point ID stores the identification information of the D data point 16 included in the folder. · Belonging Folder is the folder to which the D Data Point 16 belongs and is known in the D Template 19.

[0075] 12A is an example of data point information of a folder in the M template 14. The data point information has the following items: type ID, tag, model data point ID, and belonging folder. The type ID field stores identification information for the type of facility device 20. The tag item stores the name by which the installation worker identifies the M data point 15. The tag field stores the tag to be searched. The tag of M data point 15 is searched when setting a link. · Model Data Point ID stores the identification information of the M Data Point 15 set in the software. · Belonging Folder is the folder to which the M data point 15 belongs, and is known in the M template 14.

[0076] 12(b) shows link rule information associated with the M template 14. The link rule ID field stores identification information for 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] 13A is an example of data point information for a folder in the APP template 11. The data point information includes items such as a type ID, a tag, an application data point ID, and a folder to which the folder belongs. The type ID field stores identification information for the model number of the equipment 20. The tag field stores the name by which the installer identifies the APP data point 17. The tag field stores the tag to be searched. The tag of the APP data point 17 is searched when setting a link. The application data point ID stores the identification information of the APP data point 17 set in the software. · Belonging Folder is the folder to which the APP data point 17 belongs and is known in the APP template 11.

[0078] 13(b) shows link rule information associated with an APP template 11. The link rule ID field stores identification information for the link rule. A link rule is prepared for each APP data point 17. An APP data point 17 is connected to either a D data point 16 or an M data point 15, but since there is only one APP data point 17 that serves as the connection source, only one link rule is required for each APP data point 17. The link rule information is stored in the auto link module 21 of the APP template 11.

[0079] 14(a) is an example of data point information of a folder of the data conversion template 31. The data point information has the following items: type ID, tag, conversion data point ID, and belonging folder. The type ID field stores identification information for the type of facility device 20. The tag field stores names that are used by the installation worker to identify the data points in the data conversion template 31. There are tags for D data points 16 and M data points 15. These may be the same. Tags are searched for when setting up a link. The conversion data point ID stores the identification information of the conversion data point set in the software. Different IDs may be assigned to the D data point 16 and the M data point 15. The belonging folder is the folder to which the transformed data point 34 belongs, and is known in the data transformation template 31.

[0080] 14(b) shows link rule information associated with the data conversion template 31. A link rule is prepared for each conversion data point. In addition, link rules are prepared for both the D data point 16 side and the M data point 15 side. The link rule ID (for device data point) field stores identification information of the link rule for connecting the D data point 16 of the D template 19 with the conversion data point 34 of the data conversion template 31. The link rule ID (for model data point) field stores identification information of the link rule for connecting the data point of the M template 14 with the conversion data point 34 of the data conversion template 31.

[0081] <Link rule> FIG. 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 points 17, M data points 15, and converted data points 34. In other words, no link rule exists for D data points 16. This is because the connection between data points is mutual, so it is sufficient if one of the data points (the data point that is the starting point for the connection process) has a link rule. A link rule has the following items:

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

[0083] The Device Relationship 202 is a relationship set by the relationship setting unit 62. That is, the Device Relationship 202 is the Relation Id in the column 302 in Fig. 9. The 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, "hs:alarm and hs:sensor" is entered in Point Query 203. This means that tags associated with data points are searched for in two related folders using "hs:alarm and hs:sensor" as the key. "and" is a logical operator. Logical operators such as "or," "not," and "xor" can also be used. Developers can specify the data points to be connected to in the query.

[0085] Link Direction 204 is the direction of the link as seen from the APP template 11, M template 14, or data conversion template 31. In indicates that data is input to the data point for which the link rule is set. Out indicates that data is output from the data point for which 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 destination.

[0088] <Examples of relationship and link settings> Figure 16 shows an example of relations set between folders and links set between data points. Note that Figure 16 illustrates a case where there is no data conversion template 31. In this way, the data conversion template 31 may not be necessary.

[0089] A relation 25a is set between folders 35a and 37a according to the relation information defined in the AD template 19. A relation 25b is set between folders 35b and 37b according to the relation information defined in the D template 19. Any of the relations 25a and 25b will be referred to as a relation 25.

[0090] A relation 26a is set between folders 33a and 35a according to the relation information defined in the BM template 14. A relation 26b is set between folders 33b and 35b according to the relation information defined in the M template 14. Any of the relations 26a and 26b will be referred to as a relation 26.

[0091] A relationship 27a is set between folders 33a and 37a according to the relationship information defined in the CM template 14. A relationship 27b is set between folders 33b and 37b according to the relationship information defined in the M template 14. Any of the relationships 27a and 27b will be referred to as a relationship 27.

[0092] These relations 25 to 27 set 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, the reason why a relationship 25 is established between the D template 19 and the APP template 11 is that 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 has M data points 15, it is preferable to connect the data points in the D template 19 and the APP template 11 via the M template 14. This allows for data display in the user interface, etc. For this reason, the connection between the APP data points 17 in the APP template 11 and the D data points 16 in the D template 19 is performed last. In other words, if connecting the D data points 16 and the M data points 15 results in some D data points 16 not being connected to the M data points 15, the D data points 16 and the APP data points 17 are connected.

[0095] This sets up a link to the data point as follows: D data point 16c and APP data point 17c, D data point 16f and APP data point 17f.

[0096] <Action or Processing> The work performed by the installation worker on the tool software 8 will be described with reference to Fig. 17. This work is a preparation for the tool software 8 to create links between data points. Fig. 17 is a flowchart showing the work performed by the installation worker on the equipment management device 10 on which the tool software 8 runs.

[0097] The installation worker operates the equipment management device 10 to add a station template 9 (S1). That is, the installation worker adds the station template 9 (an abstraction of the equipment management system expressed 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 the APP template 11 to the station template 9 (S2). The installation worker adds the D template 19 to the station template 9 (S3). The installation worker adds the M template 14 to the station template 9 (S4).

[0099] Furthermore, if the installation worker needs to convert the data format of the D data points 16 in the D template 19 to conform to the M template 14 (Yes in S5), he or she adds the data conversion template 31 to the station template 9 (S6).

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

[0101] First, the installation worker 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 only necessary because the tool software 8 supports it, but it is not necessarily required.

[0102] Next, the installation worker inputs the template information including the relation information explained with reference to FIGS. 7 to 10 into the spreadsheet file (S12).

[0103] When the template information is completed in the spreadsheet file, the installation worker loads the spreadsheet file into memory (S13). The tool software 8 loads the spreadsheet file into memory, thereby loading each template into memory. As described above, the loading of a template is performed as follows: APP Template 11 > D Template 19 > M Template 14 This allows you to create relationships in the following order. Note that steps 2 and 3 can be done in any order. 1. Relationship from D Template 19 to APP Template 11 2.Relation from M template 14 to D template 19 3. Relationship from M Template 14 to APP Template 11 Also, if the template is expanded in the following order, the order in which relationships are created will also be different. APP Template 11 > M Template 14 > D Template 19 In this case, the 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.Relationship from M template 14 to D template 19 In response to an operation by the installation operator, the relation setting unit 62 establishes a relation between the template folders (S14). That is, the relation setting unit 62 selects one folder from the folders set in the D template 19 as the target. The relation setting unit 62 searches for the tag of the folder of the APP template 11 using relation information (Relation Hints). The relation setting unit 62 establishes a relation between the folder of the APP template 11 that matches the search and the folder of the D template 19 that is currently selected as the target. At this time, the relation setting unit 62 identifies the link rule of each data point of the folder to which the relation of the APP template 11 is established, and sets the Relation Id in the Device Relationship. The relation setting unit 62 performs similar processing between the M template 14 and the D template 19 and between the M template 14 and the APP template 11.

[0104] In addition, if the relationship information is not defined in the D template 19 (if the source folder is not identified), the relationship setting unit 62 simply searches for both the folder tag of the APP template 11 and the folder tag of the D template 19 using the relationship information (Relation Hints).

[0105] Next, the link creating unit 63 searches for the tag of the data point of the folder to which the relation is set using the link rule in order to set the link (S15). For example, the link creating unit 63 sets the link in the following order: 1. From M template 14 to D template 19 2. APP Template 11 to M Template 14 3. From APP template 11 to D template 19 However, either 1 or 2 can be performed first. Since it is preferable to link the APP template 11 and the D template 19 when there are no data points in the M template 14, it is better to perform 3 last.

[0106] First, the link creation unit 63 selects an arbitrary data point in an arbitrary folder in the M template 14. The link creation unit 63 acquires a link rule associated with the selected data point (see FIG. 15). The link creation unit 63 identifies a folder in the D template 19 based on the relation identified by the Relation Id in the link rule. The link creation unit 63 searches for the tags of the data points contained in this folder using the Point Query in the link rule.

[0107] The link creating unit 63 determines whether or not there is a data point that matches the search using the Point Query (S16).

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

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

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

[0111] If there is a next link rule, the process returns to step S15 (S19), and if there is no next link rule, the process of FIG. 18 ends.

[0112] Through the above process, relationships are established between folders, and links are set between data points within the related folders, as shown in Figure 16. This reduces the amount of work required by installation workers to connect data points, and also reduces errors.

[0113] <Data format conversion> 19 etc., we will explain data relay and data format conversion by the data conversion template 31. Conversion data points 34 are set in the data conversion template 31, and the conversion data points 34 convert the data format and relay data of D data points 16 to M data points 15, or relay data of M data points 15 to D data points 16.

[0114] Fig. 19 is a diagram for explaining data formats. As shown in Fig. 19(a) to (c), there are, for example, the following 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 values ​​taken by M data point 15, which controls the ON / OFF of an air conditioner, are True (representing ON) and False (representing OFF).

[0115] Numeric is a data format that takes a single numeric value. The value can be either an integer or a decimal. For example, an M data point 15 that displays the room temperature could have a numeric value such as 24.6°C, and an M data point 15 that displays the room humidity could have a numeric value such as 62%.

[0116] Multi is a data format with a "key: value" value. The key can be an integer, and the value can be true / false, a number, or a string. For example, the values ​​of the Multi format taken by the M data point 15 that controls the operation mode of an air conditioner include "1: automatic," "2: cooling," "3: heating," "4: fan," and "5: off."

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

[0118] Fig. 20 shows an example of data conversion in which Multi is converted to Boolean and Multi. The conversion example in Fig. 20 is a conversion example in which there is no D data point 16 in the D template 19 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 Fig. 20 is a data conversion in which Multi format data held by the D data point 16 is converted into Boolean format 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 operation 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 also has a Multi-type data format, but the "key: value" is different from the "key: value" of D template 19.

[0121] For this reason, 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" into 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 D template 19, which is a Multi format, and the keys of the M template 14, which is also a Multi format. In other words, 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] By this conversion, the M template 14 can display ON or OFF even if the D data point 16 is not in Boolean data format. Also, the M template 14 can display the operation mode in Multi format even if the key correspondence between 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 conversion data point 34c for Boolean->Multi conversion of the data conversion template 31. The data conversion template 31 converts to True or False according to key=1 to 4 or key=5.

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

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

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

[0127] <Relationship between Data Transformation Template and D Template / M Template> Referring to FIG. 3, the relations and links of the data conversion template will be described. As shown in FIG. 3, since the data conversion template 31 is installed between the D template 19 and the M template 14, a relation is established between these folders. In FIG. 3, a relation 28a is set between folders 35a and 39a, and a relation 29a is set between folders 33a and 39a. A relation 28b is set between folders 35b and 39b, and a relation 29b is set between folders 33b and 39b.

[0128] When setting the link, the link rules associated with the conversion data points 34a to 34d of the data conversion template 31 are used with higher priority than the link rules on the M template 14 side. This can prevent the data points of the folder of the M template 14 and the D template 19 from being connected by a link despite the presence of the data conversion template 31.

[0129] Therefore, the link creation unit 63 creates links 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 point) 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 point) that the data conversion template 31 has.

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

[0131] <Connection in the case where there is no M template> Figure 21 shows an example of setting relations and links when there is no M template 14. The processing flow when setting links can be the same as that shown in Figure 18. Because there is no M template 14, the process of establishing a relation with the folder of the M template 14 is skipped. Similarly, the process of establishing a link with the M data point 15 of the M template 14 is skipped.

[0132] That is, since there is no M template 14, a relationship 25a is established between the folder 37a of the APP template 11 and the folder 35a of the D template 19. A relationship 25b is established between the folder 37b of the APP template 11 and the folder 35b of the D template 19.

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

[0134] <Major Effects> The information processing method disclosed herein reduces errors made by installation workers compared to manually connecting data points, and reduces the amount of work required for on-site connection tests, etc. Reducing the amount of work required to build the facility management system 100 also reduces the necessary expenses.

[0135] <Other application examples> The best mode for carrying out the present disclosure has been described above using examples, but the present disclosure is not limited to these examples, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present disclosure.

[0136] For example, although the present disclosure has described the facility management system 100, it can be suitably applied to cases where one data point is connected to another data point within software.

[0137] Furthermore, the process of automatically associating data points with each other 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 the like are divided according to main functions to make it easier to understand the processing by the equipment management device 10. The present disclosure is not limited by the way in which the processing units are divided or the names of the processing units. The processing by the equipment management device 10 can also be divided into more processing units depending on the processing content. Furthermore, it can also be divided so that one processing unit includes even more processes.

[0139] Furthermore, the devices described in the examples are merely one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, correspondence information creation device 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, shared memory, etc., and perform the processes disclosed herein.

[0140] The functions of the present disclosure described above can be realized not only by software processing through the execution of a program, but also by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and a conventional circuit module designed to perform each of the functions described above.

[0141] <Reasons for the effect> The first aspect of the present disclosure performs "a process of associating a first data storage location of a first template with a second data storage location of a second template based on identification information possessed by the first data storage location and the second data storage location, and a process 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 possessed by the first data point and the second data point," thereby enabling automatic association of a first data point possessed by a first template with a second data point possessed by a second template.

[0142] The second aspect of the present disclosure associates "device data storage locations" and "application data storage locations" "based on relationship information," and associates "model data storage locations and the device data storage locations," or "the model data storage locations and the application data storage locations." Therefore, by creating relationship information, developers can automatically associate data storage locations.

[0143] The third aspect of the present disclosure provides a method for identifying a data point in an application data repository that is not associated with a data point in the model data repository. The data points of the application data storage location that have not been 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 of the data points of the application data storage location and the data points of the device data storage location." Therefore, the data points of the application data storage location and the model data storage location are associated with priority, and data points that have not been associated with the application data storage location can also be associated with data points of the device data storage location.

[0144] The fourth aspect of the present disclosure "associates the device data storage location with the application data storage location, associates the model data storage location with the device data storage location based on the relationship information held by the model template, and associates the model data storage location with the application data storage location based on the relationship information held by the model template," thereby making it possible to associate data storage locations between each template without any omissions.

[0145] The fifth aspect of the present disclosure determines the order in which data storage locations located in templates are expanded in 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 expanded in memory.

[0146] The sixth aspect of the present disclosure determines the order in which data storage locations placed in templates are expanded in 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 expanded in memory.

[0147] A seventh aspect of the present disclosure associates, for a data conversion template that converts the format of data, "the converted data storage location and the device data storage location, and the converted data storage location and the model data storage location, which the data conversion template has," based on the identification information of each storage location, and "the association of the data points of the converted data storage location and the data points of the model data storage location, and 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 each data point. Therefore, even if a data storage template exists, data points can be automatically associated using the same processing method. [Explanation of symbols]

[0148] 10 Equipment management device 14 Model Templates 15 data points 16 Device Data Points 17 Application Data Points 20 Equipment 60 Correspondence information creation device 100 Facility Management System

Claims

1. An association method performed by an information processing device that processes data related to facility equipment, The control unit A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, a step of associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; associating first data points stored in the first data repository with second data points stored in the second data repository associated with the first data repository based on identification information of the first and second data points; A method of association.

2. the templates are a device template for a data point that inputs or outputs data between the equipment, an application template for a data point that inputs or outputs data between the equipment and a control logic, and a model template for a data point that inputs or outputs data between the device template and the application template; The control unit, based on relation information that defines the data storage location to be associated, The associating method according to claim 1, wherein a device data storage location of the device template is associated with an application data storage location of the application template, a model data storage location of the model template is associated with the device data storage location, or the model data storage location is associated with the application data storage location.

3. 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 app data store that are not associated with data points in the model data store, associate the application data store data points that were not associated with the model data store data points with the device data store data points based on identification information of the application data store data points and the device data store data points; The method of claim 2 .

4. the relationship 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 relationship information defined in the device template; Associating the model data storage location with the device data storage location based on the relation information included in the model template; The associating method according to claim 2 , wherein the model data storage location and the application data storage location are associated with each other based on the relationship information included in the model template.

5. The control unit expands the application data storage location arranged in the application template into a memory, and then The device data storage location arranged in the device template is expanded into a memory, and then Expanding the model data storage location arranged in the model template into a memory; After associating the device data storage location with the application data storage location, Associating the application data storage location with the model data storage location or associating the device data storage location with the model data storage location in any order; The method of claim 2 .

6. The control unit expands the application data storage location arranged in the application template into a memory, and then The model data storage location arranged in the model template is expanded into a memory, and then Expanding the device data storage location arranged in the device template into a memory; Associating the model data storage location with the application data storage location; Associating the app data storage location with the device data storage location; Associating the device data repository with the model data repository; The method of claim 2 .

7. The template further includes a data conversion template for converting the format of the data, The control unit, based on the relation information, associates the conversion data storage location and the device data storage location, and the conversion data storage location and the model data storage location, which are included in the data conversion template, based on identification information included in the conversion data storage location, the device data storage location, and the model data storage location; The association method according to claim 2, wherein the data points of the conversion data storage location are associated with the data points of the model data storage location, and the data points of the conversion data storage location are associated with the data points of the device data storage location based on identification information possessed by the data points of the conversion data storage location, the device data storage location, and the model data storage location.

8. An equipment management device that processes data related to equipment, The control unit A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, Associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; Associating first data points stored in the first data repository with second data points stored in the second data repository associated with the first data repository based on identification information of the first data points and the second data points; Equipment management device.

9. A program executed by an information processing device that processes data related to facility equipment, A control unit included in the information processing device, A template in which data storage locations are arranged to classify and store data points for inputting or outputting the data, a step of associating a first data storage location included in a first template with a second data storage location included in a second template based on identification information included in the first data storage location and the second data storage location; associating first data points stored in the first data repository with second data points stored in the second data repository associated with the first data repository based on identification information of the first and second data points; A program that executes the following.

Images