Method, device management apparatus, program

Abstract

The model data points on the user interface side and the device data points on the device machine side are automatically matched. The present invention is a method in which a device management apparatus that manages a device machine matches model data points that hold data used in an application program that monitors and controls the device machine with device data points that hold data input or output to or from the device machine provided in a building, and a control section matches the model data points and the device data points based on identification information assigned to the model data points and the device data points.

Description

Technical Field

[0001] This invention relates to methods, equipment management devices, and procedures. Background Technology

[0002] In buildings and other structures, electrical equipment such as air conditioners and lighting systems, as well as disaster prevention equipment, are introduced. Equipment management devices are known to manage such equipment in a unified manner. Using these devices, users can operate any equipment, regardless of manufacturer or model, through a common user interface. The equipment management device stores control data related to the equipment, such as temperature and humidity, as equipment data points, and the same data is stored as model data points on the user interface side. Multiple equipment data points exist on a single equipment, each corresponding to a different model data point in the user interface. Previously, the connection between the equipment data points and the model data points was performed by the importing operator.

[0003] Techniques for connecting modules within software using tags are known (see, for example, Patent Document 1). Patent Document 1 discloses a technique that corresponds to the following two: an I / O tag T2 used in the controller and an I / O tag T1 set on the I / O port P of the I / O module.

[0004] [Existing Technical Documents]

[0005] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Application Publication No. 2016-081415 Summary of the Invention

[0007] [The problem the invention aims to solve]

[0008] However, in existing technologies, the model data points on the user interface side and the device data points on the machine side cannot be automatically mapped, thus requiring operators to perform cumbersome tasks. To automatically map model data points to device data points, it is necessary to identify the information of each data point. However, due to the large number of data points, the assignment of identification information itself has not yet been carried out, and therefore, automatic mapping of data points with consistent identification information has not been implemented.

[0009] In view of the above-mentioned problems, the present invention provides a technology that automatically maps model data points on the user interface side to device data points on the device machine side.

[0010] [Methods for solving the problem]

[0011] The first aspect of the present invention is a method, wherein,

[0012] The equipment management device for managing equipment and machinery will,

[0013] The model data points that store the data used in the application that monitors and controls the machine are stored.

[0014] Corresponding to the device data points that are stored on the equipment machines installed in the building and input or output data.

[0015] The control unit maps the model data points to the device data points based on the identification information assigned to the model data points and the device data points.

[0016] According to the first aspect of the present invention, the workload of the equipment management device implementation operation can be reduced.

[0017] The second aspect of the present invention is based on the method described in the first aspect.

[0018] Based on the model template prepared for each type of device, the model data points are generated.

[0019] The model template defines model data points for monitoring and controlling the equipment, and defines identification information for each model data point.

[0020] The third aspect of the present invention is the method described according to the first or second aspect.

[0021] The device management device stores the linking rules for determining the identification information, and the identification information is assigned to the corresponding model data points and device data points.

[0022] Based on the linking rules, the control unit determines the corresponding model data points and device data points and performs the corresponding matching.

[0023] The fourth aspect of the present invention is the method described according to the first to third aspects.

[0024] Based on the device template prepared for each device model, the device data points are generated.

[0025] The device template defines all the device data points stored in the device machine and defines identification information for each device data point.

[0026] The fifth aspect of the present invention is the method described according to aspects 1 to 4.

[0027] The control unit,

[0028] When the data stored in the device data point changes, the data stored in the model data point also changes.

[0029] When the data stored in the model data points changes, the data stored in the device data points is changed, and the device outputs a data change request.

[0030] The sixth aspect of the present invention is the method described according to the first aspect.

[0031] Based on the model template prepared for each type of device, the model data points are generated.

[0032] The model template defines model data points for monitoring and controlling the equipment, and assigns identification information to each model data point.

[0033] Based on the device template prepared for each device model, the device data points are generated.

[0034] The device template defines all the device data points stored by the device machine, and assigns identification information to each device data point.

[0035] The control unit maps the model data points of the model template to the device data points of the device template based on the identification information assigned to the model data points and the device data points.

[0036] The seventh aspect of the present invention is based on the method described in aspects 1 to 6, wherein the data conversion template includes conversion data points.

[0037] The data conversion template converts the data format of the device data points to the data format of the model data points, and vice versa. The converted data points relay data from the device data points to the model data points, or vice versa.

[0038] The control unit maps the conversion data points to the device data points based on the identification information assigned to them.

[0039] Based on the identification information assigned to the transformation data points and the model data points, the transformation data points and the model data points are mapped together.

[0040] The eighth aspect of the present invention is the method described according to the seventh aspect.

[0041] The data conversion template converts the data format of the device data point corresponding to the conversion data point into the first data format and the second data format corresponding to the model data point corresponding to the conversion data point, or...

[0042] The first and second data formats corresponding to the model data points corresponding to the conversion data points are converted into the data format of the device data points that are input to the conversion data points.

[0043] The ninth aspect of the present invention is the method described according to the seventh aspect.

[0044] The data conversion template converts the data format with multiple key-value pairs output by the device data point corresponding to the conversion data point into a binary data format and a data format with multiple key-value pairs corresponding to the model data point corresponding to the conversion data point, or...

[0045] The binary data format corresponding to the model data point corresponding to the conversion data point and the data format with multiple sets of keys and values ​​are converted into the data format with multiple sets of keys and values ​​that are input to the device data point corresponding to the conversion data point.

[0046] The tenth aspect of the present invention is the method according to the seventh aspect.

[0047] The data conversion template converts the data format of the numerical values ​​output by the device data points corresponding to the conversion data points into a binary data format and a data format with multiple sets of keys and values ​​corresponding to the model data points corresponding to the conversion data points, or...

[0048] The binary data format corresponding to the model data point corresponding to the conversion data point and the data format with multiple sets of keys and values ​​are converted into the data format of the numerical value of the device data point corresponding to the conversion data point.

[0049] The eleventh aspect of the present invention is an equipment management device for managing equipment and machinery, which includes a control unit based on...

[0050] The identification information is assigned to the model data points and the device data points.

[0051] The model data points will be stored in the application that monitors and controls the machine containing the device.

[0052] Corresponding to the device data points that are stored on the equipment machines installed in the building and input or output data.

[0053] According to the eleventh aspect of the present invention, the workload of the equipment management device implementation operation can be reduced.

[0054] The 12th aspect of the present invention is a procedure.

[0055] The equipment management device is used to enable the management of equipment and machinery to function as a control unit.

[0056] The control unit

[0057] Based on the identification information assigned to the model data points and the device data points

[0058] The model data points will be stored in the application that monitors and controls the machine containing the device.

[0059] Corresponding to the device data points that are stored on the equipment machines installed in the building and input or output data.

[0060] According to the 12th aspect of the present invention, the workload of the equipment management device implementation operation can be reduced.

[0061] [The effects of the invention]

[0062] This invention provides a technique to reduce the workload of implementing equipment management devices. Attached Figure Description

[0063] 【 Figure 1 This is an example of a system architecture diagram for an equipment management system that uses a network to control various devices and machines.

[0064] 【 Figure 2 [A diagram illustrating the structure of the software in the control equipment management system.]

[0065] 【 Figure 3 This diagram illustrates how operators connect equipment data points and model data points in software tools.

[0066] 【 Figure 4 A diagram is created to represent the corresponding information and the software and equipment running in the device.

[0067] 【 Figure 5 [A diagram illustrating the structure of the software tools running in the corresponding information generation device.]

[0068] 【 Figure 6 [A diagram illustrating the connection example between device data points and model data points.]

[0069] 【 Figure 7 [A hardware structure diagram of an example of a device for generating corresponding information.]

[0070] 【 Figure 8 A functional block diagram of an example of a device for generating information corresponding to the automatic linking module.

[0071] 【 Figure 9 The image shows an example of device template information stored in the device template information storage unit.

[0072] 【 Figure 10A The image shows an example of model template information stored in the model template information storage unit.

[0073] 【 Figure 10B The diagram shows an example of link rule information corresponding to model template 14.

[0074] 【 Figure 11A The image shows an example of data conversion template information stored in the data conversion template information storage unit.

[0075] 【 Figure 11B The image above represents an example of link rule information corresponding to the data transformation template.

[0076] 【 Figure 12 The diagram above represents an example of a linking rule.

[0077] 【 Figure 13 The flowchart shows an example of an operation performed by an importer on a device that generates corresponding information.

[0078] 【 Figure 14 This is an example of a flowchart illustrating the process by which the automatic linking module connects the model data points of the model template with the device data points of the device template.

[0079] 【 Figure 15 [A diagram illustrating the corresponding information generated by the automatic linking module.]

[0080] 【 Figure 16A [A diagram illustrating the data format.]

[0081] 【 Figure 16B [A diagram illustrating the data format.]

[0082] 【 Figure 16C [A diagram illustrating the data format.]

[0083] 【 Figure 17 The figure represents an example of data transformation, showing the conversion of a composite type to a Boolean type and other composite types.

[0084] 【 Figure 18 The diagram illustrates examples of data format conversion in the following situations. Figure 17 Starting with the model template, the same data format does not exist in the device template.

[0085] 【 Figure 19 The figure represents an example of data transformation, showing the conversion of numeric types to Boolean and composite types.

[0086] 【 Figure 20 The diagram illustrates examples of data format conversion in the following situations. Figure 19 Starting with the model template, we can see that the fan rotation count and ON / OFF command methods differ between the model template and the device template. Detailed Implementation

[0087] The following describes an equipment management system and a corresponding method performed by the equipment management system as an example of how the present invention is implemented.

[0088] <About Equipment Management System>

[0089] Many buildings, including office buildings, commercial facilities, schools, and hospitals, are equipped with equipment management systems. These systems are also known as BAS (Building Automation System), BEMS (Building Energy Management System), BMS (Building Management System), and BACS (Building Automation and Control System), among others. While there are no strict definitions for each, a brief explanation is provided below.

[0090] BAS is a system that automatically controls equipment located in a building. It can centrally control and monitor all equipment and machines, such as air conditioning, lighting, crime prevention and security systems, and electricity meters, which are manually managed by administrators, through a network.

[0091] BEMS is a system for managing a building's energy. While BAS can also manage energy, BEMS focuses on "visualizing energy consumption." BEMS-based energy consumption visualization not only provides real-time data on current energy consumption but also allows for comparison with data from the previous day, month, and year, making it easy to determine whether current energy consumption is appropriate.

[0092] A Building Management System (BMS) is a system that monitors and controls various equipment and machines in a building, including those for power supply, air conditioning, lighting, disaster prevention, and crime prevention. In buildings, especially office buildings, these various equipment and machines operate. To maintain them in a safe state and ensure they function properly, their status needs to be monitored, and any anomalies should be detected immediately. Furthermore, when managers can remotely operate the equipment and machines without directly manipulating them, and can also change settings, the workload can be reduced.

[0093] Although not strictly speaking, BACS refers to a system that integrates BAS, BMS, and BEMS, and is registered in ISO:16484-5.

[0094] The following description does not specifically distinguish between BAS, BEMS, BMS, BACS, or similar equipment or building systems, but refers to them as equipment management systems.

[0095] <System Structure Example>

[0096] Figure 1This is an example of a system architecture diagram of an equipment management system 100 in which the equipment management device 10 controls various equipment and machines 20 via a network. For example... Figure 1 As shown, the device management unit 10 and various devices 20 are communicatively connected via a network N1. This network N1 is assumed to be, for example, BACnet. BACnet is a network that uses the BACnet protocol for communication between the device management system 100 and the various devices 20. Network N1 can use dedicated cables or, like a typical LAN, Ethernet cables (registered trademark). The device management system 100 is not required to use the BACnet protocol for network communication; BACnet is just one example. For example, the communication protocol could be Modbus, etc.

[0097] Examples of devices 20 shown include air conditioners, lighting fixtures, crime prevention devices, disaster prevention devices, electrical installations, and elevators; however, these are just examples. Furthermore, a gateway device called a BACnet gateway is sometimes provided between the devices 20 and the BACnet. The BACnet gateway converts communication data corresponding to the BACnet protocol into communication data corresponding to the communication protocol of each device 20, and vice versa. The communication protocol corresponding to each device 20 refers to a unique communication protocol determined by the company that manufactures the device 20. Therefore, the manufacturers and brands of the devices 20 can be different.

[0098] The device management device 10 functions as a web server, generating images of the managed device 20 using HTML or similar methods and sending them to the terminal device 50 via network N2. Network N2 is, for example, the Internet. Users can monitor the device 20 by connecting the terminal device 50 to the device management device 10 from any location. When the terminal device 50 is unavailable, users can monitor the device 20 by directly operating the control panel (display screen, keyboard) of the device management device 10.

[0099] Furthermore, network N2 can be communicatively connected to the corresponding information generation device 60. The corresponding information generation device 60 can communicate with the device management device 10 via network N2, and does not necessarily need to be always connected to network N2. When connecting the device data point 16 and model data point 15 described in this invention, the device management device 10 can be a standalone device.

[0100] The corresponding information generation apparatus 60 can be any information processing device that runs an OS such as Windows (registered trademark). The corresponding information generation apparatus 60 is equipped with software tools (described later) to perform the process of connecting (or mapping) model data points and device data points (details of which will be described later). In this invention, the term "connection" is used. Furthermore, the corresponding information generation apparatus 60 can run software tools, such as a PC (personal computer), tablet computer, or smartphone.

[0101] In BACnet, the functions of device machine 20 are handled using the concept of objects. An object is the product of grouping and representing various types of information; the information associated with an object is called an attribute in BACnet. For example, when an air conditioner is an object, the possible control contents (temperature, airflow, etc.) within the air conditioner are equivalent to attributes. Furthermore, in BACnet, reading and writing objects or associated attributes is called a service. In the following description of this invention, for ease of explanation, objects and attributes are not distinguished, and are simply referred to as "device data points."

[0102] Software Structure within Information Processing Systems

[0103] Figure 2 This diagram illustrates the structure of the software 201 of the control equipment management system 100. The software 201 runs in the equipment management device 10. As described above, the equipment management device 10 is communicatively connected to the actual existing equipment machines 20. The software 201 is an application program for controlling and monitoring these equipment machines 20. The software 201 operates the equipment machines 20 on the equipment management device 10 and therefore has device data points 16 as interfaces with the equipment machines 20. The device data points 16 store data input to or output to the equipment machines 20. The device data points 16 are prepared according to the type and format of the data input and output to the equipment machines 20, such as analog signals and digital signals, and vary depending on the equipment machine 20. Users can operate the device data points 16 of the equipment machines 20 on the equipment management device 10.

[0104] In addition, Software 201 features a user interface and system control logic created by engineers. Figure 2 In the diagram, as the user interface, a graphical representation 21 of air conditioners 1 and 2 is provided. Furthermore, as the system control logic, demand control 22 and lighting plan control 23 are provided. Demand control 22 controls the equipment 20 to any set value. Lighting plan control 23 arranges the lighting's illumination and brightness control.

[0105] To enable users to easily operate different devices 20, a common user interface and system control logic are provided for each device 20. Here, the user interface and system control logic can exist on each device 20.

[0106] In order for users to operate the equipment machine 20 from the user interface via the device data point 16, before the equipment management system 100 is put into operation, the operator is required to perform the following operations: connect the model data points 15 of the user interface, system control logic, etc., to the device data points 16. The model data points 15 store the data used in the application program (software 201 mentioned above) that monitors and controls the equipment machine 20.

[0107] Figure 2 In the diagram, model data point 15 of graphic 21 for air conditioners 1 and 2 is connected to, for example, ON / OFF or operating mode as device data point 16. Model data point 15 of demand control 22 is connected to, for example, the setpoint of the air conditioner as device data point 16. Model data point 15 of lighting plan control 23 is connected to, for example, the ON / OFF or illuminance of the lighting controller as device data point 16. Conventionally, operators have connected the user interface, control model data point 15, and device data point 16 on the machine side in this way.

[0108] The types of equipment and machines 20 in the buildings at the delivery sites of each equipment management system 100 vary greatly, therefore the operators implementing the equipment management system 100 must build it from scratch. One method for building an equipment management system 100 is as follows: using a dedicated software tool, the operator manually connects the model data points 15 and the equipment data points 16.

[0109] Figure 2 In the diagram, several arrows schematically represent connections. A bidirectional arrow indicates that bidirectional data communication is possible between device data point 16 and model data point 15, while a unidirectional arrow indicates that only unidirectional data communication is possible between device data point 16 and model data point 15.

[0110] When a user inputs data to the user interface provided by the device management device 10, the device management device 10 outputs data to the device data point 16 connected to the model data point 15 of the user interface. The device data point 16 then sends the data to the device machine 20 via BACnet. In this way, the user can control the actual machine through the software 201. Conversely, data transmitted from the device machine 20 to the device data point 16 via BACnet will be transmitted to the model data point 15, allowing the user to check the status of the device machine 20.

[0111] <Comparative Example>

[0112] As a comparative example of the technology of the present invention, the following operation is described: The importer manually connects the equipment data point 16 and the model data point 15. A software tool for importing the operation exists, and the importer operates the corresponding information generation device 60 to perform the operation.

[0113] Figure 3 The diagram illustrates the following operation. The operator imports the diagram into the software tool and connects the equipment data point 16 and the model data point 15.

[0114] The importer will

[0115] A. Equipment Machine 20 and Equipment Data Point 16

[0116] B. Equipment data point 16 and model data point 15

[0117] The connection is performed manually. In this invention, the connection operation of B can be automated.

[0118] <Examples of software and software tool structures>

[0119] Figure 4 This is a schematic representation, showing the corresponding diagram of the software running in the information generation device 60 and the device machine 20. As described above, the device machine 20 and the device management device 10 are connected via network N1. Network N1 is also connected to the data collection and storage unit 39. The data collection and storage unit 39 stores various information acquired from the device machine 20.

[0120] Figure 4 In this configuration, one or more device machines 20 are connected to one controller 32. The controller 32 has the function of receiving operations from the device machines 20 (which are hardware) and sending control signals to the device machines 20. That is, one or more device machines 20 that use the controller 32 as a common node are connected to the controller 32.

[0121] Furthermore, there is no substantial difference between software and software tools, but for the sake of convenience, the software used up to the point of import is called a software tool, and the software used after import is called software.

[0122] This software tool includes site template 17, model template 14, and device template 19. Site template 17 is a template for site files. Site files are an abstraction of the device management system 100.

[0123] Model template 14 is the working area for configuring model data points 15. Model data points 15 are generated based on model templates prepared for each type of equipment machine 20. Model template 14 defines model data points 15 used for monitoring and controlling the equipment machine 20, and defines identification information (labels described later) for each model data point 15. Model template 14 is set as follows... Figure 2 The model data point 15 shown corresponds to the user interface and control.

[0124] Equipment template 19 is the working area for configuring equipment data points 16. Equipment data points 16 are generated based on equipment template 19 prepared for each equipment machine 20 model. Equipment template 19 defines all equipment data points 16 stored by the equipment machine 20 and defines identification information (labels described later) for each equipment data point 16. The equipment template 19 is configured as follows... Figure 2 The device data point 16 is shown.

[0125] Prepare a model template 14 for each type of equipment 20, and prepare an equipment template 19 for each model. The type represents the series name and brand name of the equipment 20. The model is equivalent to the model launched under the same series name and brand name of equipment 20. Figure 4 In the text, air conditioner A001, air conditioner A002, and air conditioner B001 are model numbers, while air conditioner A and air conditioner B are types.

[0126] The importer adds equipment template 19 and model template 14 to site template 17, creating the equipment management system 100. That is, site template 17 is the foundation of the equipment management system, summarizing equipment template 19 and model template 14.

[0127] Site template 17 has two layers (model layer 18b and driver layer 18a). Driver layer 18a is the layer on the device machine 20 side, and model layer 18b is the layer on the user interface side. On driver layer 18a on the device machine 20 side, a device template 19 is configured for each model of device machine 20. Device template 19 sets device data points 16 to store the input and output data on device machine 20. On model layer 18b on the user interface side, a model template 14 is configured for each type of device machine 20. Model template 14 sets model data points 15 to store data about device machine 20. The following relationship exists: number of models ≥ number of types. Therefore, the number of device data points 16 in device template 19 is greater than the number of model data points 15 in model template 14. By summarizing the model data points 15 in model template 14 according to the types divided as the same product, it is not necessary to create many model templates 14, thus reducing workload. Furthermore, the connection between model data point 15 and device data point 16 is based on the linking rules of model template 14, which reduces the number of connection processing steps.

[0128] Device data point 16 and model data point 15 each store their own data. The data stored in device data point 16 can be referenced by controller 32, and the data set on model data point 15 can be referenced by user interface. Model data point 15 receives data sent from device machine 20 to device data point 16 connected to it. This data is processed according to the needs of model data point 15, including display processing and logic processing. Device data point 16 receives data sent from model data point 15 connected to it and sends it to device machine 20. The corresponding information generation device 60 of the present invention automatically connects device data point 16 of device template 19 and model data point 15 of model template 14 in a manner that allows for referencing between model data point 15 and device data point 16 in device management device 10.

[0129] Next, refer to Figure 5 This illustrates the automatic connection between device data points 16 and model template 14 based on software tools. Figure 5 This is a diagram illustrating the structure of the software tools running in the corresponding information generation device 60. For example... Figure 5 As shown, in the software tool, site template 17 configures model template 14 and device template 19. These can be set by the import operator. In site template 17, the layer that configures model template 14 is called the aforementioned model layer 18b, and the layer that configures device template 19 and data conversion template 31 is called driver layer 18a.

[0130] In model template 14, multiple folders 33 have a hierarchical structure. Each folder 33 contains one or more model data points 15. Model data points 15 with similar functions are grouped together and stored in the same folder 33. The circles and squares below the folder 33 represent model data points 15. The reason why the importer stores model data points 15 in folders 33 in this way is that, due to their large number, they are easy to manage, and even if there are model data points 15 with the same identification information (labels described later) in the entire system, the model data points 15 of the connected objects will be restricted to folders 33, etc.

[0131] Device template 19 also has more than one folder 35. Figure 5In this configuration, device template 19 has one folder 35, but typically multiple folders 35 exist. Each folder 35 contains more than one device data point 16. Device data points 16 with similar functions are grouped together and stored in the same folder 35. The lower circle of folder 35 represents a device data point 16. The reason why importers store device data points 16 in folder 35 is that, due to their large number, they are easier to manage, and even if there are device data points 16 with the same identification information (labels described later) throughout the entire system, the device data points 16 of the connected processing objects are restricted to folder 35, etc.

[0132] In addition, data conversion template 31 is sometimes used to convert the data format of device data point 16 of device template 19 to fit the data format of model template 14 (or vice versa). Data conversion template 31 is a template for tools used to convert the data formats of device data point 16 and model data point 15 to each other.

[0133] Data conversion template 31 also has more than one folder 36. Figure 5 In the data conversion template 31, there is one folder 36, but this is only for the convenience of drawing; usually, there are multiple folders 36. Folder 36 contains more than one conversion data point 34. Data conversion template 31 has conversion data point 34a from the model template 14 side and conversion data point 34b from the device template 19 side.

[0134] In this invention, the corresponding information generation device 60 automatically performs the connection described above (B). The function in the automatic connection software tool is referred to as the automatic linking module 30. The automatic linking module 30 operates through the driver layer 18a, but can also operate through the model layer 18b, or both the driver layer 18a and the model layer 18b. The automatic linking module 30 connects the device data point 16 and the model data point 15 based on linking rules. Details regarding the linking rules are provided in [link to related documentation]. Figure 12 illustrate.

[0135] <Example of connecting device data points and model data points>

[0136] Based on the above structure, the outline of the automatic connection of the present invention will be explained. First, the importer assigns tags (identification information) to the equipment data point 16 and the model data point 15 respectively. Based on the tags, the corresponding information generation device 60 determines the equipment data point 16 of the equipment template 19 that should be connected to the model data point 15 of the model template 14, and automatically performs the connection. In addition, when the data formats in the model template 14 and the equipment template 19 are different, the corresponding information generation device 60 connects the equipment data point 16 of the equipment template 19 with the conversion data point 34b of the data conversion template 31, and automatically connects the conversion data point 34a with the model data point 15 of the model template 14.

[0137] Figure 6 This diagram illustrates an example of the connection between device data point 16 and model data point 15. (See diagram below.) Figure 6 As shown, there are multiple device data points 16 in device template 19 and multiple model data points 15 in model template 14. Each device data point 16 and model data point 15 corresponds to one data point. The device management system processes various data, such as indoor temperature, fan on / off status, or outlet temperature.

[0138] The importer assigns labels representing characteristics to the equipment data points 16 and each model data point 15. These labels serve as identification information for the equipment data points 16 and model data points 15, and can be easily identified by the importer. During automatic connection, the corresponding information generation device 60 locates the labels of the model data points 15 located in the model template 14 and the equipment data points 16 in the equipment template 19 with the same labels, and connects them.

[0139] Figure 6 In this process, a data conversion template 31 is configured for a portion of the model data points 15. The importing operator is aware of the data formats of the equipment data points 16 in equipment template 19 and the model data points 15 in model template 14. Therefore, when the data formats differ, a data conversion template 31 is prepared between equipment template 19 and model template 14. During automatic connection implementation, the importing operator, for example, selects the required equipment template 19 and model template 14 using a software tool and then performs the connection process.

[0140] <Hardware Structure Example>

[0141] Figure 7 A hardware structure diagram of the device management device 10 and the corresponding information fabrication device 60 is provided. (See diagram for example.) Figure 7 As shown, the device management device 10 and the corresponding information generation device 60 are constructed by a computer 500, which includes a CPU 501, ROM 502, RAM 503, HD 504, HDD (mechanical hard disk) controller 505, display screen 506, external machine connection I / F (interface) 508, network I / F 509, bus 510, keyboard 511, fixed-point device 512, DVD-RW (rewritable digital multifunction optical disc) drive 514, and media I / F 516.

[0142] The CPU 501 controls the overall operation of the computer 500. The ROM 502 stores the programs used by the CPU 501 driver, such as IPL. The RAM 503 serves as the working area for the CPU 501. The HDD 504 stores various data, including programs. The HDD controller 505, under the control of the CPU 501, controls the reading and writing of various data to the HDD 504. The display screen 506 displays various information such as cursor, menus, windows, text, or images. The external machine connection I / F 508 is an interface for connecting various external machines, such as USB (Universal Serial Bus) memory devices and printers. The network I / F 509 is an interface for data communication using networks N1 and N2. The bus 510 is used for connecting devices such as… Figure 7 The CPU501 and other structural elements shown are electrically connected, including the address bus and data bus.

[0143] Furthermore, the keyboard 511 is an input method with multiple keys for inputting text, numbers, various instructions, etc. The pointing device 512 is an input method for selecting and executing various instructions, selecting processing objects, moving the cursor, etc. The DVD-RW drive 514 controls the reading or writing of various data to a DVD-RW 513, which is an example of a removable recording medium. Furthermore, the DVD-RW can be a DVD-R, etc. The media I / F 516 controls the reading or writing (storage) of data to a recording medium 515 such as flash memory.

[0144] <About Features>

[0145] Figure 8 This is a functional block diagram of the corresponding information generation device 60 for running the automatic linking module 30. The corresponding information generation device 60 can be any computer such as a PC. The corresponding information generation device 60 includes a retrieval unit 61, a display control unit 62, a relationship setting unit 63, a link generation unit 64, and an operation receiving unit 65. These functional units of the corresponding information generation device 60 are implemented through the following methods or means: Figure 5 The CPU 501 shown executes commands contained in one or more programs installed in the corresponding information generation device 60. This program may be a software tool.

[0146] Furthermore, the corresponding information generation apparatus 60 includes a device template information storage unit 66, a model template information storage unit 67, a data conversion template information storage unit 68, and a linking rule storage unit 69. These storage units are composed of… Figure 5 It is constructed using HD504, RAM503, etc. as shown.

[0147] The retrieval unit 61 performs two searches. First, it retrieves the specified tag names from the folder of the device template 19 within the folder of the device template 14. A relationship is established between the folders of the model template 14 and the device template 19. Second, within the established relationship, the retrieval unit 61 retrieves device data points 16 that satisfy the linking rules determined by the model data points 15.

[0148] The display control unit 62 displays various images for importing into the operator's software tools (site template 17, model template 14, equipment template 19, data conversion template 31, etc.).

[0149] The relationship setting unit 63 sets a relationship between the folder 33 of model template 14 and the folder 35 of device template 19, which are determined by the retrieval unit 61 to be compatible with the search. The relationship restricts the range of device data points 16 being retrieved. In addition, the relationship setting unit 63 also sets relationships between the folder 33 of model template 14 and the folder 36 of data conversion template 31, and between the folder 36 of data conversion template 31 and the folder 35 of device template 19.

[0150] The linking unit 64 links the model data point 15 of the model template 14 and the device data point 16 of the device template 19, which are determined by the retrieval unit 61 to be compatible with the retrieval. This link corresponds to the connection (correspondence) between the device data point 16 and the model data point 15 in this invention. Furthermore, the linking unit 64 links the conversion data point 34 of the data conversion template 31 and the device data point 16 of the device template 19, which are determined by the retrieval unit 61 to be compatible with the retrieval, and also links the conversion data point 34 of the data conversion template 31 and the model data point 15 of the model template 14.

[0151] The operation receiving unit 65 receives various operations from the importing operator for the software tools running in the corresponding information making device 60.

[0152] Figure 9 This is an example of device template information stored in the device template information storage unit 66. Figure 9 The device template information represents the device data point 16 possessed by device template 19. The device template information includes items such as model ID, label, and device data point ID.

[0153] • The Model ID project stores the identification information of the model of the device machine 20 corresponding to the device template 19.

[0154] The tag project stores the names, etc., used by the operator to identify equipment data point 16. The tag project stores the tags used as the retrieval objects. When connected to model data point 15 or transformation data point 34, the tags of equipment data point 16 are the retrieval objects.

[0155] • The identification information of device data point 16 set by the software is stored in the device data point ID.

[0156] Figure 10A This is an example of model template information stored in the model template information storage unit 67. Figure 10A The model template information represents the model data points 15 possessed by model template 14. The model template information includes items such as category ID, label, and model data point ID.

[0157] • The category ID is stored in the project, which contains the identification information of the category of the device machine 20 corresponding to the model template 14.

[0158] • The project saves the tags and imports the names, etc., used by the operator to identify model data point 15. When connected to device data point 16 or conversion data point 34, the tags of model data point 15 are the retrieval objects.

[0159] • The link rule ID is stored in the project, which contains the identification information of the link rule set in model data point 15. Prepare link rules for each model template 14.

[0160] • The identification information of model data point 15 set by the software is saved in the model data point ID.

[0161] Figure 10B This represents the linking rule information corresponding to a specific model template 14. Prepare at least one linking rule for each model template 14.

[0162] Figure 11A This is an example of data conversion template information stored in the data conversion template information storage unit 68. Figure 11A The data transformation template information represents the transformation data points 34 contained in the data transformation template 31. The data transformation template information includes items such as category ID, label, and transformation data point ID. The category ID can be the same as the model template information.

[0163] • The project saves the tags and imports the names, etc., used by the operator to identify the conversion data point 34. There are tags for equipment data points and tags for model data points. They can be the same. When connected to equipment data point 16 or model data point 15, the tags of the conversion data point 34 are the retrieval objects.

[0164] The conversion data point ID stores the identification information of the conversion data points as set by the software. Different IDs can be assigned when using equipment data points and model data points.

[0165] Figure 11B This indicates the linking rule information corresponding to a specific data transformation template 31. Prepare at least one linking rule for each data transformation template 31.

[0166] • The Link Rule ID (for device data points) is stored in the project, which is used to identify the link rule for connecting device data point 16 of device template 19 and conversion data point 34 of data conversion template 31.

[0167] • The link rule ID (used for model data points) is stored in the project and is the identification information of the link rule used to connect model data point 15 of model template 14 and transformation data point 34 of data transformation template 31.

[0168] Furthermore, the linking rules can be the same on the device data point 16 side and the model data point 15 side.

[0169] Figure 12 This represents an example of a linking rule. A linking rule is a rule used to connect model data point 15 and device data point 16. Additionally, a linking rule is a rule used to connect transformation data point 34 and device data point 16, and a linking rule is a rule used to connect transformation data point 34 and model data point 15.

[0170] Link rules are set only on model template 14 and data conversion template 31 (not on device data point 16). When the importer adds model template 14 and data conversion template 31 to site template 17, link rules are also set.

[0171] The linking rules have the following items.

[0172] • Rule name 201 is the name of the link rule, which can be set arbitrarily by the importer.

[0173] Device relationship 202 represents a relationship used to create a link. This relationship is unrelated to data transfer; it indicates the location used to create the link. A suitable example of a relationship is the relationship between folders.

[0174] • Point Query 203 represents a query (search criteria) used to retrieve the labels of device template 19. Figure 12 In query 203, the query specifies "hs:alarm and hs:sensor". This means connecting device data points 16 with names (labels) like "hs:alarm" and "hs:sensor" that match device template 19 to model data points 15 of the model template 14 of interest. "and" is a logical operator. Logical operators such as "or", "not", and "xor" can also be used. Users can specify the device data point 16 to be connected through a query.

[0175] Under the linking rules of data conversion template 31, the point query 203 can be configured to retrieve the tags of device data point 16 and model template 14.

[0176] • Link direction 204 is the direction of the link observed from model template 14 or data conversion template 31. Incoming (In) is data input from device template 19 to model template 14. Incoming (In) is data input from device template 19 to data conversion template 31. Incoming (In) is data input from data conversion template 31 to model template 14. Outgoing (Out) is the opposite.

[0177] • The starting slot name (205) is the name of the starting point.

[0178] • The destination slot name (To Slot Name) 206 is the name of the destination.

[0179] <Run or process>

[0180] Reference Figure 13 This describes the work performed by the importer for the automatic linking module 30. This work is a preliminary preparation for the automatic linking module 30 to create links. Figure 13 This is a flowchart illustrating the operation performed by the operator on the corresponding information generation device 60 of the automatic linking module 30.

[0181] The operator operation information is imported into the device 60, and the site template 17 is added (S1). That is, the site template 17, which the operator prepares for adding the equipment template 19 and the model template 14, is imported (the equipment management system is abstracted and represented by software).

[0182] Then, the importer adds equipment template 19 to site template 17 (S2). The importer adds model template 14 to site template 17 (S3).

[0183] In addition, when the importer needs to convert the data format of the equipment data point 16 of the equipment template 19 to fit the model template 14 (S4), the data conversion template 31 is added to the site template 17 (S5).

[0184] Next, refer to Figure 14 This explains the processing of connection device data point 16 and model data point 15. Figure 14 The flowchart illustrates the following process: The automatic linking module 30 connects the model data point 15 of the model template 14 with the device data point 16 of the device template 19. Figure 14 The document describes the case where model data point 15 of model template 14 is connected to device data point 16 of device template 19. However, the same applies to connecting conversion data point 34 of data conversion template 31 to device data point 16 of device template 19, as well as connecting conversion data point 34 to model data point 15.

[0185] First, the importer adds the template of the built-in automatic linking module 30 to the site template 17 (S11). The automatic linking module 30 refers to each linking rule set in the model template 14 or the data conversion template 31. Furthermore, the importer can specify the type of equipment 20 (i.e., model template 14), allowing the automatic linking module 30 to process only that type. Alternatively, the automatic linking module 30 can process different types of equipment 20 sequentially.

[0186] The retrieval unit 61 of the automatic linking module 30 retrieves folders 33 and 35 from the equipment template 19, which are set to the machine categories specified by the import operator (S12). The machine category refers to the category of equipment machines 20, such as air conditioners and lighting units. That is, connection processing is performed for each individual equipment machine 20. Folders 33 and 35 are created for each equipment machine 20. Under each of these folders, data points 16 and model data points 15 are categorized according to function and nature. For example, the subfolders 33 and 35 could be folders representing temperature, humidity, etc.

[0187] When folders 33 and 35 with the machine category of step S12 exist in model template 14 and device template 19 (S13), the display control unit 62 displays a list of folders 33 and 35 with the machine category of step S12 (S14).

[0188] Import the specified data into folder 33 on the model template 14 side and folder 35 on the device template 19 side (S15). The operation receiving unit 65 receives the specified data.

[0189] The relationship setting unit 63 of the automatic linking module 30 sets the relationship between folder 33 and folder 35 specified by the importer (S16). The relationship refers to the location where a link is created even though no data is transferred.

[0190] Next, the retrieval unit 61 retrieves the model template 14 that has an established relationship with the folder 33 and sets the corresponding linking rules (see...). Figure 10A , Figure 10B Within the relationships set in step S16 (folder 35 of device template 19 and folder 33 of model template 14), the retrieval unit 61 retrieves device data points 16 and model data points 15 that satisfy the linking rules (S17). That is, the retrieval unit 61 retrieves device data points 16 and model data points 15 that have the query tags set in the point query that conform to the linking rules.

[0191] When the retrieved device data point 16 and model data point 15 exist in step S17 (yes in S18), the linking unit 64 creates a link between the model data point 15 of the model template 14 and the device data point 16 of the device template 19 (S19).

[0192] If the device data point 16 or model data point 15 that matches the search criteria does not exist in step S18 (No in S18), the retrieval unit 61 determines whether it exists and performs the corresponding next link rule with the model template 14 of the folder 33 with which it has established a relationship (S20).

[0193] If the next linking rule exists, the process returns to step S17 (S21); if the next linking rule does not exist, Figure 14 The processing is now complete.

[0194] Supplementary explanation of data conversion template 31. The automatic linking module 30, for data conversion template 31, will... Figure 14 The same processing is performed twice on both the device template 19 and model template 14 sides. The retrieval unit 61 retrieves the tags for the device data points of the converted data point 34 and the tags for the device data point 16 using the point query of the link rules (for device data points) in the data conversion template 31. The retrieval unit 61 also retrieves the tags for the model data points of the converted data point 34 and the tags for the model data point 15 using the point query of the link rules (for model data points) in the data conversion template 31.

[0195] When a search is performed, the linking unit 64 connects the device data point 16 of the device template 19, which holds tags for point queries that conform to the linking rules (for device data points), and the conversion data point 34 of the data conversion template 31. The linking unit 64 also connects the model data point 15 of the model template 14, which holds tags for point queries that conform to the linking rules (for model data points), and the conversion data point 34 of the data conversion template 31.

[0196] <Corresponding information generated by the automatic linking module>

[0197] Figure 15 This diagram illustrates the corresponding information generated by the automatic linking module 30. Figure 15 In the diagram, layers from left to right represent those closer to the user. Device template 19 contains numbers 1 to 6 (device data point 16), and model template 14 contains numbers 1 to 6 (model data point 15).

[0198] The automatic linking module 30 connects model data points 15 and device data points 16 with the same number (representing a label) based on linking rules. Furthermore, regarding device data points 16 and model data points 15 that require data conversion, the data conversion template 31 connects model data points 15 and device data points 16. Dashed lines connecting numbers indicate links created by the linking unit 64. One or more links correspond to information 40.

[0199] Through this connection, when the data stored in the device data point 16 changes, the device management system 100 changes the data stored in the model data point 15; when the data stored in the model data point 15 changes, the data stored in the device data point 16 changes; and at the same time, it outputs data change requests to the device machine 20.

[0200] The program module 41 is a software group that provides the functions of the equipment management system 100. The program module 41 performs functions such as image generation, alarm signaling, chart generation, schedule management, and tag information management.

[0201] The function of the user interface unit 42 is to construct the images displayed on the screen. The user interface unit 42 displays images such as calendars, user management, display boards (displaying various charts, tables, and other data), alarm management, etc.

[0202] <Data Format Conversion>

[0203] Refer to Figure 16~ Figure 20 This describes the relaying and data format conversion of data based on data conversion template 31. Data conversion template 31 sets conversion data point 34, which converts the data format and relays data from device data point 16 to model data point 15, or data from model data point 15 to device data point 16.

[0204] Figures 16A-16C It's a diagram illustrating the data format. For example... Figures 16A-16C As shown, the data format includes, for example, the following three.

[0205] (i) Boolean

[0206] (ii) Numeric

[0207] (iii) Multi-type

[0208] Boolean data is a binary data format that takes either a true or a false value. For example, the Boolean value of model data point 15, which controls the ON and OFF states of an air conditioner, can be either true (representing ON) or false (representing OFF).

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

[0210] A composite data type is a data format with a "key:value" pair. The key can be an integer, and the value can be true / false, a number, or a string. For example, the composite data point 15 in the model controlling the air conditioner's operating mode could take values ​​such as "1: Auto", "2: Cooling", "3: Heating", "4: Fan", and "5: OFF".

[0211] Data conversion template 31 can convert Boolean, numeric, and composite data formats from one to another, or vice versa.

[0212] Figure 17 This indicates, as an example of data transformation, the conversion of a composite type to a Boolean type and examples of composite types. Figure 17 In the example of the conversion, there is no device data point 16 in device template 19 that displays the ON or OFF of the air conditioner, but when the model template 14 is a specification for displaying the ON or OFF of the air conditioner, the data conversion is to convert the composite format data of device data point 16 into the Boolean format and composite format data of model data point 15.

[0213] Equipment data point 16 in equipment template 19 is the equipment data point 16 that displays the operating mode. The data format is composite, and equipment data point 16 has values ​​of "1: Automatic", "2: Cooling", "3: Heating", "4: Air supply", and "5: OFF".

[0214] On the other hand, in model template 14, the operator wants to display whether the air conditioner is ON or OFF. In addition, although model template 14 also has a composite data format, the "key:value" is different from the "key:value" of device template 19.

[0215] Therefore, data conversion template 31 performs the following conversions. First, data conversion template 31 converts the composite format values ​​shown by device data point 16, namely "1: Auto", "2: Cooling", "3: Heating", and "4: Fan", into the Boolean format (an example of the first data format) ON. Similarly, it converts "5: OFF" into OFF. In model template 14, ON corresponds to true and OFF corresponds to false. Furthermore, data conversion template 31 converts the correspondence between the keys of device template 19 (as a composite format) and the keys of model template 14 (as a composite format (an example of the second data format)). That is, data conversion template 31 does not change key = 1 to 4, but converts key = 5 into key = 0. In model template 14, 1 corresponds to Auto, 2 to Cooling, 3 to Heating, 4 to Fan, and 0 to OFF.

[0216] Through this conversion, even if device data point 16 is not in Boolean data format, model template 14 can still display ON or OFF. Furthermore, even if the keys of device template 19 and model template 14 correspond differently, model template 14 can still display the operating mode in a composite format.

[0217] At this time, the linking unit 64 connects the composite format device data point 16 of the device template 19 with the Boolean to composite conversion data point 34c of the data conversion template 31. The data conversion template 31 converts the data to true or false based on key = 1 to 4 or key = 5.

[0218] Furthermore, the linking unit 64 connects the composite format device data point 16 of the device template 19 to the composite-to-composite conversion data point 34d of the data conversion template 31. The data conversion template 31 does not convert key=1 to 4, but converts key=5 to key=0.

[0219] Furthermore, the linking unit 64 connects the Boolean-to-composite conversion data point 34c of the data conversion template 31 to the Boolean-format model data point 15c of the model template 14, and connects the composite-to-composite conversion data point 34d of the data conversion template 31 to the composite-format model data point 15d of the model template 14.

[0220] Therefore, the composite format data stored in the device data point 16 of the device template 19 is converted into Boolean format data and composite format data through the data conversion template 31, and sent to the Boolean format and composite format model data point 15 of the model template 14.

[0221] Figure 18 It means that, in Figure 17Starting with model template 14, this section shows an example of data format conversion when the same data format does not exist in device template 19. Figure 18 In the middle, the flow of data is observed starting from model template 14. Figure 18 In the device template 19, the device data point 16 for instructing the air conditioner to ON or OFF, which is present in the model template 14, is absent. Therefore, a data conversion template 31 for instructing the air conditioner to ON or OFF is required. Similarly, the key-value correspondence of the composite format in the model template 14 is different from that in the device template 19. Therefore, a data conversion template 31 is needed to convert the operating mode of the model template 14 to the operating mode of the device template 19.

[0222] therefore, Figure 18 In this process, data conversion template 31 converts the true values ​​of model template 14 to key=1 in a composite format, and converts the false values ​​of model template 14 to key=5 in a composite format. Furthermore, data conversion template 31 converts the correspondence between the keys of model template 14 (in composite format) and the keys of device template 19 (in composite format). That is, data conversion template 31 does not change keys 1 to 4, but converts key=0 to key=5.

[0223] Through this conversion, even if device data point 16 is not in Boolean data format, model template 14 can still indicate ON or OFF to device template 19. Furthermore, even if the key correspondences between device template 19 and model template 14 are different, model template 14 can still indicate the operating mode to device template 19 in a composite format.

[0224] The linking unit 64 connects the Boolean format model data point 15c of the model template 14 to the Boolean to composite format conversion data point 34c of the data conversion template 31, and connects the composite format model data point 15d of the model template 14 to the composite format conversion data point 34d of the data conversion template 31.

[0225] Furthermore, the linking unit 64 connects the conversion data point 34c of the Boolean-to-composite format conversion of the data conversion template 31 to the composite format device data point 16 of the device data point 16. The linking unit 64 also connects the conversion data point 34d of the composite-to-composite format conversion of the data conversion template 31 to the composite format device data point 16 of the device template 19.

[0226] according to Figure 18The Boolean format data stored in model data point 15 of model template 14 is converted into a composite format key (true is 1, false is 5) through data conversion template 31 and sent to device data point 16 of device template 19. The composite format data stored in model data point 15 of model template 14 is converted (0 is converted to 5) through data conversion template 31 and sent to device data point 16 of device template 19.

[0227] Figure 19 This indicates, as an example of data conversion, an example of converting numeric types to Boolean and composite types. Figure 19 The conversion example is the data conversion in the following case: the device data point 16 of device template 19 displays the fan rotation number, but the model template 14 displays the fan ON / OFF and operating mode.

[0228] Device data point 16 in device template 19 is a device data point 16 that displays the fan rotation count. The data format is numerical. On the other hand, model template 14 is a specification for displaying the fan's ON or OFF state. In addition, model template 14 is a specification for displaying the operating mode ("1: OFF", "2: Low", "3: Medium", "4: High").

[0229] Therefore, data conversion template 31 performs the following conversions. First, when the value (numerical type) shown by device data point 16 is 0, data conversion template 31 converts it to false; when it is greater than 0, it converts it to true. In model template 14, ON corresponds to true, and OFF corresponds to false. Furthermore, data conversion template 31 converts the value (numerical type) shown by device data point 16 into a key (1-4) of a composite format. That is, when the fan rotation count is 0, data conversion template 31 converts it to key=1; when the fan rotation count is 1-100, it converts it to key=2; when the fan rotation count is 101-500, it converts it to key=3; and when the fan rotation count exceeds 500, it converts it to key=4. In model template 14, 1 corresponds to OFF, 2 to weak, 3 to medium, and 4 to strong. These values ​​are just one example.

[0230] Through this conversion, even if device data point 16 is not in Boolean data format, model template 14 can still display ON or OFF based on the fan rotation number. Furthermore, even if device template 19 is not in a composite format, model template 14 can still display the operating mode in a composite format.

[0231] The linking unit 64 connects the numerical data point 16 of the device template 19 to the conversion data point 34e of the data conversion template 31 for numerical-to-Boolean conversion, and connects the numerical data point 16 to the conversion data point 34f of the data conversion template 31 for numerical-to-composite conversion. Furthermore, the linking unit 64 connects the conversion data point 34e of the data conversion template 31 for numerical-to-Boolean conversion to the model data point 15e of the model template 14 for Boolean conversion, and connects the conversion data point 34f of the data conversion template 31 for numerical-to-composite conversion to the model data point 15f of the model template 14 for composite conversion.

[0232] Therefore, the numerical data stored in the device data point 16 of the device template 19 is converted into Boolean data and composite data through the data conversion template 31 and sent to the Boolean and composite model data point 15 of the model template 14.

[0233] Figure 20 It means that, in Figure 19 The example below demonstrates data format conversion when the data formats for fan rotation count and operating mode differ, using model template 14 and device template 19. Figure 20 In the middle, the flow of data is observed starting from model template 14. Figure 20 In the device template 19, the device data point 16 for instructing the fan to ON or OFF, which is present in the model template 14, is not present. Therefore, a data conversion template 31 for instructing the fan to ON or OFF is required. Similarly, the device data point 16 for displaying the operating mode, which is present in the model template 14, is not present in the device template 19. Therefore, a data conversion template 31 for displaying the operating mode is required.

[0234] therefore, Figure 20 In the process, data conversion template 31 converts the true values ​​of model template 14 to 100 rpm in numeric format and converts the false values ​​of model template 14 to 0 rpm in numeric format. Furthermore, data conversion template 31 converts the "1" in the composite format of model template 14's "1: OFF" to 0 in numeric format, the "2" in the composite format of model template 14's "2: Weak" to 100 in numeric format, the "3" in the composite format of model template 14's "3: Medium" to 300 in numeric format, and the "4" in the composite format of model template 14's "4: Strong" to 500 in numeric format.

[0235] Through this conversion, even if device data point 16 is not in Boolean data format, model template 14 can still indicate the ON or OFF of the fan to device template 19. Furthermore, even if device template 19 is not in composite format, model template 14 can still indicate the operating mode to device template 19 in composite format.

[0236] The linking unit 64 connects the Boolean-format model data point 15e of the model template 14 to the Boolean-to-numerical conversion data point 34e of the data conversion template 31, and connects the composite-format model data point 15f of the model template 14 to the composite-to-numerical conversion data point 34f of the data conversion template 31. Furthermore, the linking unit 64 connects the Boolean-to-numerical conversion data point 34e of the data conversion template 31 to the numerical-format device data point 16 of the device template 19, and connects the composite-to-numerical conversion data point 34f of the data conversion template 31 to the numerical-format device data point 16 of the device template 19.

[0237] according to Figure 20 The Boolean-format data stored at model data point 15e of model template 14 is converted into a numerical fan rotation number via data conversion template 31 and sent to device data point 16 of device template 19. The composite-format data stored at model data point 15f of model template 14 is converted into a fan rotation number via data conversion template 31 and sent to device data point 16 of device template 19. Therefore, even if device data point 16 for instructing the fan to ON or OFF, as in model template 14, is not present in device template 19, the user can still instruct the fan to ON or OFF. Similarly, even if device data point 16 for processing operating modes, as in model template 14, is not present in device template 19, the user can still instruct the operating mode.

[0238] Figures 17-20 In this process, data conversion template 31 can convert one data format into two data formats, but it can also convert one data format into three or more data formats. In addition, data conversion template 31 can convert one data format of model template 14 into two or more data formats of device template 19.

[0239] <Main Effects>

[0240] The information processing method of the present invention, compared with the manual connection of equipment data points 16 and model data points 15, can reduce operator errors and the workload of on-site connection testing. The workload reduction achieved through the equipment management system 100 also reduces necessary expenses.

[0241] <Other applicable examples>

[0242] The above description of the best mode for carrying out the present invention has been illustrated by examples. The present invention is not limited to these examples, and various modifications and substitutions may be made without departing from the spirit of the invention.

[0243] For example, this invention describes a device management system 100, but it is also well applicable to situations where one data point is connected to another data point within software.

[0244] Furthermore, the automatic corresponding processing of equipment data points 16 and model data points 15 can be performed by the equipment management device 10, rather than by the corresponding information generation device 60.

[0245] Furthermore, in this invention, it is explained that the model template 14 or the data conversion template 31 has linking rules, but it is also possible that the model data point 15 or the conversion data point 34 corresponds to the linking rules.

[0246] also, Figure 8 The structural example is divided according to main functions to facilitate understanding of the processing of the corresponding information generation device 60. The invention is not limited to the method of dividing processing units or their names. The processing of the corresponding information generation device 60 can also be divided into more processing units depending on the processing content. Furthermore, it can also be divided in a way that one processing unit contains more processing.

[0247] Furthermore, the apparatus group described in the embodiments represents only one of multiple computing environments used to implement the embodiments disclosed in this specification. In one embodiment, the corresponding information generation apparatus 60 includes multiple computing devices referred to as a server cluster. The multiple computing devices are configured to communicate with each other through any type of communication link, including networks, shared memory, etc., to implement the processing disclosed in this specification.

[0248] The functions of the present invention described above can be implemented not only through software processing based on program execution, but also through one or more processing circuits. Here, "processing circuit" in this specification includes devices such as processors deployed by circuitry, processors programmed to perform functions by software, ASICs (Application Integrated Circuits), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and conventional circuit modules designed to perform the functions described above.

[0249] <Reasons for the effect>

[0250] The first aspect of the present invention involves mapping "model data points that store data used in the application of the monitoring and control equipment machine, and device data points that store data input or output on the equipment machine installed in the building" to "the control unit mapping the model data points and the device data points based on the identification information assigned to the model data points and the device data points." Therefore, the mapping operation performed manually can be automated, reducing the workload of the mapping process. The identification information in the first aspect refers to letters, numbers, symbols, alphabets, or combinations thereof used to uniquely identify or determine the model data point 15 or the device data point 16. In this embodiment, the term "label" is used.

[0251] The second aspect of the present invention is that "the model data points are generated based on a model template prepared for each type of the equipment," thus, by summarizing the model data points 15 within the model template 14 according to the types of the same product, it is not necessary to create a multi-mode model template 14, thereby reducing workload. Furthermore, "the model template defines model data points for monitoring and controlling the equipment, and defines identification information for each model data point," thus enabling monitoring and control of the equipment through the model data points.

[0252] The third aspect of the present invention is that "the device management device stores the linking rules for determining identification information, the identification information is assigned to the corresponding model data points and device data points, and the control unit determines the corresponding model data points and device data points based on the linking rules and performs the corresponding operation." Thus, the user can control the connection between model data points and device data points by appropriately setting the linking rules.

[0253] The fourth method of the present invention is that "the device data points are generated based on the device template prepared for the model of each device machine, the device template defines all the device data points stored by the device machine, and defines identification information for each device data point". Therefore, the connection between model data point 15 and device data point 16 is carried out starting from the linking rules of model template 14, thus reducing the number of connection processing steps.

[0254] The fifth technology of the present invention is that "when the data stored in the device data point is changed, the control unit changes the data stored in the model data point; when the data stored in the model data point is changed, the control unit changes the data stored in the device data point and outputs a data change request to the device machine." Therefore, the device management device 10 displays the data sent from the device data point 16, which the user can confirm. When the user changes the data, the user can send the data to the device machine 20.

[0255] The sixth aspect of the present invention is to generate model data points based on a model template prepared for each type of device 20, and to generate device data points 16 based on a device template prepared for each model of device 20. "The model data points of the model template and the device data points of the device template are matched based on the identification information assigned to the model data points and the device data points." Therefore, the data points of the type of device 20 and the matching model can be interconnected.

[0256] The seventh method of the present invention is as follows: "Based on the identification information assigned to the conversion data point and the device data point, the conversion data point and the device data point are mapped together; based on the identification information assigned to the conversion data point and the model data point, the conversion data point and the model data point are mapped together." Therefore, the data format of the device data point 16 can be converted into the data format of the model data point, and the data format of the model data point 15 can be converted into the data format of the device data point 16.

[0257] The eighth method of the present invention is to "convert the data format of the data output by the device data point into the first data format and the second data format corresponding to the model data point corresponding to the conversion data point" or "convert the first data format and the second data format corresponding to the model data point into the data format of the data input to the device data point corresponding to the conversion data point". Therefore, the model data point 15 can store data in two data formats, and one data format of the device data point 16 can also be converted into the data format of the model data point 15.

[0258] The ninth aspect of the present invention can convert the data format with multiple sets of keys and values ​​processed by device data point 16 into a binary data format and a data format with multiple sets of keys and values ​​processed by model data point 15, or...

[0259] The binary data format and the data format with multiple sets of keys and values ​​processed by model data point 15 can be converted into the data format with multiple sets of keys and values ​​processed by device data point 16.

[0260] The tenth aspect of the present invention is that the data format of the values ​​processed by the device data point 16 can be converted into the binary data format and the data format with multiple sets of keys and values ​​processed by the model data point 15, or...

[0261] The binary data format and the data format with multiple sets of keys and values ​​processed by model data point 15 can be converted into the numerical data format processed by device data point 16.

[0262] This application claims priority based on Japan Patent Application No. 2023-059591, filed on March 31, 2023, and incorporates the entire contents of Japan Patent Application No. 2023-059591 into this application.

[0263] [Attached image labels]

[0264] 14 Model Templates

[0265] 15 data points

[0266] 16 device data points

[0267] 19 Equipment Templates

[0268] 20 Equipment and Machinery

[0269] 60 Corresponding Information Generating Device

[0270] 100 Equipment Management System

Claims

1. A method for managing equipment, wherein, The equipment management device that manages the equipment maps model data points to equipment data points. The model data points store data used in the application that monitors and controls the device. The device data points are stored in the data input or output by the device machines installed in the building. The control unit stores the linking rules that determine the search conditions, and maps the model data points and device data points that have identification information that meets the search conditions to each other. The search conditions are the criteria for retrieving the identification information assigned to the model data points and device data points. Based on the model template prepared for each type of device, the model data points are generated. The model template defines model data points for monitoring and controlling the equipment, and assigns identification information to each model data point. Based on the device template prepared for each device model, the device data points are generated. The device template defines all the device data points stored by the device machine, and assigns identification information to each device data point. The connection between the model data points and the device data points is based on the linking rules of the model template.

2. The equipment management method according to claim 1, wherein the control unit: When the data stored in the device data point changes, the data stored in the model data point also changes. When the data stored in the model data points changes, the data stored in the device data points is changed, and the device outputs a data change request.

3. The equipment management method according to claim 1, wherein the data conversion template includes conversion data points. The data conversion template converts the data format of the device data points to the data format of the model data points, or converts the data format of the model data points to the data format of the device data points. The conversion data point relays data from the device data point to the model data point, or relays data from the model data point to the device data point. The control unit maps the conversion data points to the device data points based on the identification information assigned to them. Based on the identification information assigned to the transformation data points and the model data points, the transformation data points and the model data points are mapped together.

4. The equipment management method according to claim 3, wherein the data conversion template converts the data format of the data output by the equipment data point corresponding to the conversion data point into the first data format and the second data format corresponding to the model data point corresponding to the conversion data point, or, The first and second data formats corresponding to the model data points corresponding to the conversion data points are converted into the data format of the device data points that are input to the conversion data points.

5. The equipment management method according to claim 3, wherein the data conversion template converts the data format with multiple sets of keys and values ​​output by the equipment data point corresponding to the conversion data point into a binary data format and a data format with multiple sets of keys and values ​​corresponding to the model data point corresponding to the conversion data point, or, The binary data format corresponding to the model data point corresponding to the conversion data point and the data format with multiple sets of keys and values ​​are converted into the data format with multiple sets of keys and values ​​that are input to the device data point corresponding to the conversion data point.

6. The equipment management method according to claim 3, wherein the data conversion template converts the data format of the numerical value output by the equipment data point corresponding to the conversion data point into a binary data format and a data format with multiple sets of keys and values ​​corresponding to the model data point corresponding to the conversion data point, or, The binary data format corresponding to the model data point corresponding to the conversion data point and the data format with multiple sets of keys and values ​​are converted into the data format of the numerical value of the device data point corresponding to the conversion data point.

7. An equipment management device for managing equipment machinery, comprising a control unit, The control unit will store model data points that store data used in the application program that monitors and controls the equipment, and correspond these data points to device data points that store data input or output on the equipment installed in the building. The control unit stores the linking rules that determine the search conditions, and maps the model data points and device data points that have identification information that meets the search conditions to each other. The search conditions are the search criteria for retrieving the identification information assigned to the model data points and device data points. Based on the model template prepared for each type of device, the model data points are generated. The model template defines model data points for monitoring and controlling the equipment, and assigns identification information to each model data point. Based on the device template prepared for each device model, the device data points are generated. The device template defines all the device data points stored by the device machine, and assigns identification information to each device data point. The connection between the model data points and the device data points is based on the linking rules of the model template.

8. A computer program product for enabling a device management unit for managing equipment and machinery to function as a control unit. The control unit will store model data points that store data used in the application program that monitors and controls the equipment, and correspond these data points to device data points that store data input or output on the equipment installed in the building. The control unit stores the linking rules that determine the search conditions, and maps the model data points and device data points that have identification information that meets the search conditions to each other. The search conditions are the search criteria for retrieving the identification information assigned to the model data points and device data points. Based on the model template prepared for each type of device, the model data points are generated. The model template defines model data points for monitoring and controlling the equipment, and assigns identification information to each model data point. Based on the device template prepared for each device model, the device data points are generated. The device template defines all the device data points stored by the device machine, and assigns identification information to each device data point. The connection between the model data points and the device data points is based on the linking rules of the model template.

Images