Method, facility management device, and program
The equipment management device automates the association of model and device data points using templates and link rules, addressing the manual complexity in conventional systems and reducing installation time and errors.
Patent Information
- Application Number
- JP2023059591
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-03-31
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2043-03-31
AI Technical Summary
Conventional equipment management systems require manual and complex work to associate model data points on the user interface side with device data points on the equipment side, as identification information has not been attached to the large number of data points, leading to a lack of automatic correspondence.
An equipment management device and method that automatically associates model data points with device data points using identification information, generated based on model and device templates, and employs a control unit to correlate these points based on predefined link rules and data conversion templates.
Reduces the number of man-hours required for installing and managing equipment management systems by automating the association process, minimizing operator errors and reducing installation time.
Smart Images

Figure 0007583308000001 
Figure 0007583308000002 
Figure 0007583308000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a method, a facility management device, and a program. [Background technology]
[0002] In buildings and other structures, equipment such as electrical equipment for air conditioning and lighting, and disaster prevention equipment are installed. Equipment management devices that manage such equipment in a centralized manner are known. By using the equipment management device, a user can operate any equipment from a common user interface, even for equipment from different manufacturers and models. The equipment management device holds data related to the control of the equipment, such as temperature and humidity, as device data points, and the user interface holds similar data as model data points. One equipment has multiple device data points, and each device data point corresponds to a different model data point in the user interface. Conventionally, installation workers have been tasked with connecting device data points and model data points.
[0003] There is known a technology for connecting modules in software using tags (see, for example, Patent Document 1). Patent Document 1 discloses a technology for associating an I / O tag T2 used in a controller with an I / O tag T1 set in each of the I / O ports P of an I / O module. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2016-081415 A Summary of the Invention [Problem to be solved by the invention]
[0005] However, in conventional technology, model data points on the user interface side and device data points on the equipment side could not be automatically associated, requiring cumbersome work by an operator. Automatic association of model data points and device data points requires information to identify each data point, but because there are a large number of data points, no identification information has been assigned to them so far, and therefore no data points with matching identification information have been automatically associated.
[0006] In view of the above-mentioned problems, the present disclosure provides a technology for automatically associating model data points on a user interface side with device data points on an equipment side. [Means for solving the problem]
[0007] The first aspect of the present disclosure is The facility management device that manages the facility equipment A model data point that holds data used in an application that monitors and controls the facility equipment; A method for associating a property with a device data point that holds data input or output from the facility equipment installed in the property, comprising: The control unit associates the model data points with the device data points based on identification information assigned to the model data points and the device data points.
[0008] According to the first aspect of the present disclosure, it is possible to reduce the number of steps required for installing an equipment management device.
[0009] A second aspect of the present disclosure is a method according to the first aspect, comprising: The model data points are generated based on a model template prepared for each type of the facility equipment, In the model template, the model data points used for monitoring and controlling the facility devices are defined, and identification information is defined for each of the model data points.
[0010] A third aspect of the present disclosure is a method according to the first or second aspect, comprising: The equipment management device holds a link rule that defines identification information assigned to the model data point and the device data point that are to be associated with each other, The control unit determines which model data points and which device data points are to be associated based on the link rule, and associates them.
[0011] A fourth aspect of the present disclosure is a method according to the first to third aspects, The device data points are generated based on a device template prepared for each model number of the equipment, In the device template, all of the device data points held by the equipment are defined, and identification information is defined for each of the device data points.
[0012] A fifth aspect of the present disclosure is a method according to any one of the first to fourth aspects, The control unit is modifying the data held in said model data points if the data held in said device data points is modified; When the data held in the model data point is changed, the data held in the device data point is changed and a data change request is output to the facility equipment.
[0013] A sixth aspect of the present disclosure is a method according to the first aspect, comprising: The model data points are generated based on a model template prepared for each type of the facility equipment, In the model template, the model data points used for monitoring and controlling the facility equipment are defined, and identification information is defined for each of the model data points. The device data points are generated based on a device template prepared for each model number of the equipment, In the device template, all of the device data points held by the equipment are defined, and identification information is defined for each of the device data points; The control unit associates the model data points of the model template with the device data points of the device template based on identification information assigned to the model data points and the device data points.
[0014] A seventh aspect of the present disclosure is a method according to any one of the first to sixth aspects, A data conversion template converts a data format of the device data point into a data format of the model data point, and converts the data format of the model data point into the data format of the device data point, and a conversion data point is set in the data conversion template for relaying data of the device data point to the model data point or relaying data of the model data point to the device data point; The control unit associates the conversion data point with the device data point based on identification information assigned to the conversion data point and the device data point, The transformed data points and the model data points are associated with each other based on identification information assigned to the transformed data points and the model data points.
[0015] An eighth aspect of the present disclosure is a method according to the seventh aspect, comprising: The data transformation template transforms a data format of data output by the device data point associated with the transformation data point into a first data format and a second data format corresponding to the model data point associated with the transformation data point, or The first data format and the second data format corresponding to the model data point associated with the conversion data point are converted into a data format of data input to the device data point associated with the conversion data point.
[0016] A ninth aspect of the present disclosure is a method according to the seventh aspect, comprising: The data transformation template transforms a data format having a plurality of pairs of key and value output by the device data point associated with the transformation data point into a binary data format and a data format having a plurality of pairs of key and value corresponding to the model data point associated with the transformation data point, or The binary data format and the data format having multiple pairs of key and value corresponding to the model data point associated with the transformation data point are converted into a data format having multiple pairs of key and value that are input to the device data point associated with the transformation data point.
[0017] A tenth aspect of the present disclosure is a method according to the seventh aspect, comprising: The data transformation template transforms a numerical data format output by the device data point associated with the transformation data point into a binary data format and a data format having multiple key-value pairs corresponding to the model data point associated with the transformation data point, or The binary data format and the data format having multiple pairs of key and value corresponding to the model data point associated with the conversion data point are converted into a numerical data format to be input to the device data point associated with the conversion data point.
[0018] An eleventh aspect of the present disclosure is a method for manufacturing a semiconductor device comprising: An equipment management device that manages equipment, A model data point that holds data used in an application that monitors and controls the facility equipment; A device data point that holds data input or output from the equipment installed in the property, The device data point and the model data point are associated with each other based on identification information assigned to the model data point and the device data point.
[0019] According to the eleventh aspect of the present disclosure, it is possible to reduce the man-hours required for installing an equipment management device.
[0020] A twelfth aspect of the present disclosure is a method for manufacturing a semiconductor device comprising: Equipment management devices that manage equipment, A model data point that holds data used in an application that monitors and controls the facility equipment; A device data point that holds data input or output from the equipment installed in the property, The program causes the program to function as a control unit that associates the model data points with the device data points based on identification information assigned to the model data points and the device data points.
[0021] According to the twelfth aspect of the present disclosure, it is possible to reduce the man-hours required for installing an equipment management device. Effect of the Invention
[0022] The present disclosure can provide a technique for reducing the amount of work required for installing an equipment management device. [Brief description of the drawings]
[0023] [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. [Diagram 2] FIG. 2 is a diagram illustrating a structure of software for controlling the equipment management system. [Diagram 3] FIG. 13 is a diagram for explaining a schematic diagram of an installation operator connecting device data points and model data points in a software tool. [Figure 4] 2 is a diagram illustrating a correspondence between software operating on the correspondence information creating device and facility devices; FIG. [Diagram 5]FIG. 2 is a diagram illustrating a configuration of a software tool that operates on the correspondence information creating device. [Figure 6] FIG. 13 is a diagram illustrating an example of a connection between device data points and model data points. [Figure 7] FIG. 2 is a hardware configuration diagram of an example of a correspondence information creating device. [Figure 8] 1 is a functional block diagram of an example of a correspondence information creation device in which an autolink module operates; [Figure 9] FIG. 2 is a diagram illustrating an example of device template information stored in a device template information storage unit. [Figure 10] FIG. 4 is a diagram illustrating an example of model template information stored in a model template information storage unit. [Figure 11] 11 is a diagram illustrating an example of data transformation template information stored in a data transformation template information storage unit. FIG. [Figure 12] FIG. 13 is a diagram illustrating an example of a link rule. [Figure 13] FIG. 11 is a flowchart illustrating an example of operations performed by an installation operator on the correspondence information creating device. [Figure 14] FIG. 13 is an example flowchart illustrating the process by which the autolink module connects model data points of a model template to device data points of a device template. [Figure 15] 10 is a diagram for explaining correspondence information created by an autolink module; FIG. [Figure 16] FIG. 2 is a diagram illustrating a data format. [Figure 17] FIG. 13 is a diagram showing an example of data conversion, in which Multi is converted into Boolean and Multi. [Figure 18] FIG. 17 is a diagram showing an example of data format conversion in a case where the same data format as that of the model template does not exist in the device template. [Figure 19] FIG. 13 is a diagram showing an example of data conversion from Numeric to Boolean and Multi. [Figure 20] FIG. 19 is a diagram showing an example of data format conversion when the fan rotation speed and ON / OFF command method are different between the model template and the device template, as viewed from the model template. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0024] 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.
[0025] <About the facility management system> Facility management systems are installed in many properties such as office buildings, commercial facilities, schools, hospitals, etc. Facility management systems are called BAS (Building Automation System), BEMS (Building Energy Management System), BMS (Bill Management System), BACS (Building Automation and Control System), etc. There is no strict definition for these, but we will briefly explain each of them.
[0026] 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 managers, via a network.
[0027] BEMS is a system for managing energy in properties. Although BAS can also manage energy, BEMS is a system that focuses 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 the current energy consumption is appropriate.
[0028] A BMS is a system that monitors and controls various equipment such as electricity, air conditioning, lighting, disaster prevention, and crime prevention equipment in a property. In properties such as office buildings, various types of equipment are in operation. To keep these in a safe state and perform their intended functions, it is necessary to monitor their status and immediately detect the nature of any abnormality that occurs. In addition, if managers can remotely operate equipment and change settings without having to operate them directly, the workload can be reduced.
[0029] Strictly speaking, BACS refers to a system that combines BAS, BMS, and BEMS, and is registered in ISO:16484-5.
[0030] In the following, we will not distinguish between BAS, BEMS, BMS, BACS, or similar equipment or property systems, and will explain them as equipment management systems.
[0031] <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 devices 20 via a network. As shown in FIG. 1, the equipment management device 10 and various equipment devices 20 are communicably connected via a network N1. This network N1 is assumed to be, for example, BACnet. BACnet is a network in which the equipment management system 100 communicates with the various equipment devices 20 using a BACnet protocol. A dedicated cable may be used for the network N1, or an Ethernet cable (registered trademark) may be used as in a normal LAN. The equipment management system 100 does not need to use the BACnet protocol for network communication, and the BACnet protocol is merely an example. For example, the communication protocol may be Modbus or the like.
[0032] As the facility devices 20, for example, air conditioners, lighting devices, security devices, disaster prevention devices, power devices, and elevators are illustrated, but these are only examples. Note that a gateway device called a BACnet gateway may be placed between the facility devices 20 and BACnet. The BACnet gateway converts communication data corresponding to the BACnet protocol into communication data of a communication protocol supported by each facility device 20, and converts communication data of the communication protocol supported by each facility device 20 into communication data corresponding to the BACnet protocol. The communication protocol supported by each facility device 20 is a unique communication protocol determined by the company that manufactured the facility device 20. Therefore, the facility devices 20 may be manufactured by different companies or brands.
[0033] The equipment management device 10 has a web server function, creates a screen for managing the equipment 20 in HTML or the like, and transmits it 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 present, the user can monitor the equipment 20 by directly operating the console (display and keyboard) of the equipment management device 10.
[0034] 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 connected to the network N2 at all times. When connecting the device data points 16 and model data points 15 described in the present disclosure, the equipment management device 10 can be a standalone device.
[0035] The correspondence information creating device 60 may be any information processing device with an OS such as Windows (registered trademark) installed. A software tool described later is installed in the correspondence information creating device 60, and the correspondence information creating device 60 performs a process of connecting (or associating) model data points and device data points (details of which will be described later). In this disclosure, the term "connect" is used. Note that the correspondence information creating device 60 may be a PC (Personal Computer), a tablet terminal, a smartphone, etc., as long as the software tool can be operated.
[0036] In BACnet, the functions of the equipment 20 are handled under the concept of objects. An object is a representation of a variety of information grouped together, and in BACnet, information related to an object is called a property. For example, if an air conditioner is an object, the control contents (temperature, air volume, etc.) that the air conditioner can perform correspond to the property. Also, in BACnet, reading or writing an object or related properties is called a service. In the following explanation of this disclosure, for convenience of explanation, objects and properties are not distinguished from each other and are simply referred to as "device data points."
[0037] <Software structure in information processing system> FIG. 2 is a diagram for explaining the structure of software 201 that controls the equipment management system 100. This software 201 runs on the equipment management device 10. As described above, the equipment devices 20 that actually exist are connected to the equipment management device 10 so as to be able to communicate with each other. The software 201 is an application that controls and monitors these equipment devices 20. Since the software 201 handles the equipment devices 20 on the equipment management device 10, it has device data points 16 that serve as an interface with the equipment devices 20. The device data points 16 hold data that is input to the equipment devices 20 or output by the equipment devices 20. The device data points 16 are prepared according to the type and format of data input / output to / from the equipment devices 20, such as analog signals and digital signals, and often differ depending on the equipment devices 20. A user can operate the device data points 16 of the equipment devices 20 on the equipment management device 10.
[0038] The software 201 also has a user interface and system control logic created by engineers. In Fig. 2, graphics 21 of air conditioners 1 and 2 are shown as the user interface. Demand control 22 and lighting schedule control 23 are shown as system control logic. Demand control 22 controls the facility equipment 20 to an arbitrary setting value. Lighting schedule control 23 schedules the lighting and brightness control of the lights.
[0039] In order to allow a user to easily operate different equipment devices 20, a common user interface and system control logic are provided to different equipment devices 20. However, the user interface and system control logic may exist for each equipment device 20.
[0040] Conventionally, before starting up the equipment management system 100, an installation worker connects each model data point 15, such as the user interface and system control logic, to the device data points 16 so that a user can operate the equipment 20 from the user interface via the device data points 16. The model data points 15 hold data used by an application (the above-mentioned software 201) that monitors and controls the equipment 20.
[0041] 2, model data points 15 relating to the graphics 21 of the air conditioners 1 and 2 are connected to device data points 16, such as ON / OFF or an operation mode. Model data points 15 relating to demand control 22 are connected to device data points 16, such as the setting value of an air conditioner. Model data points 15 relating to lighting schedule control 23 are connected to device data points 16, such as ON / OFF or illuminance of a lighting controller. Conventionally, an installation worker connects model data points 15 of a user interface or control with device data points 16 on the facility equipment side in this way.
[0042] Since the types of equipment 20 that are present in each property to which the equipment management system 100 is delivered vary, the installer of the equipment management system 100 builds the equipment management system 100 from scratch. One method of building the equipment management system 100 is for the installer to manually connect the model data points 15 and the device data points 16 on a dedicated software tool.
[0043] In Fig. 2, several arrows show connections diagrammatically: a bidirectional arrow means that data communication is possible in both directions between the device data point 16 and the model data point 15, and a unidirectional arrow means that data communication is possible only in one direction between the device data point 16 and the model data point 15.
[0044] When a user inputs data into a user interface provided by the equipment management device 10, the equipment management device 10 outputs the data to a device data point 16 connected to a model data point 15 of the user interface. The device data point 16 transmits the data to the equipment 20 via BACnet. In this way, the user can control the actual equipment from the software 201. Conversely, data that arrives at the device data point 16 from the equipment 20 via BACnet arrives at the model data point 15, allowing the user to check the status of the equipment 20.
[0045] <Comparative Example> As a comparative example with the technology of the present disclosure, a description will be given of the work in which an installation worker manually connects device data points 16 and model data points 15. A software tool for the installation work is available, and the installation worker operates a correspondence information creation device 60 to perform the work.
[0046] FIG. 3 is a diagram for explaining a schematic operation of an installation worker connecting device data points 16 and model data points 15 in a software tool.
[0047] The installation worker must: A. 20 Equipment and 16 Device Data Points B. Device data point 16 and model data point 15 In the present disclosure, the connection work of B can be automated.
[0048] <Examples of software and software tool configurations> 4 is a diagram showing a schematic diagram of the correspondence between the software operating in the correspondence information creation device 60 and the facility equipment 20. As described above, the facility equipment 20 and the equipment management device 10 are connected via the network N1. The network N1 is also connected to the collected data storage unit 39. The collected data storage unit 39 stores various information acquired from the facility equipment 20.
[0049] 4, one controller 32 is connected to one or more facility devices 20. The controller 32 has a function of accepting operations of the facility devices 20 as hardware and a function of transmitting control signals to the facility devices 20. In other words, the controller 32 is connected to one or more facility devices 20 that share the controller 32.
[0050] Although there is no substantial difference between software and software tools, for the sake of convenience, what is used up until installation is referred to as a software tool, and what is used after installation is referred to as software.
[0051] This software tool is provided with a station template 17, a model template 14, and a device template 19. The station template 17 is a template of a station file. The station file is an abstraction of the facility management system 100.
[0052] The model template 14 is a working area in which model data points 15 are placed. The model data points 15 are generated based on a model template prepared for each type of facility equipment 20, and in the model template 14, the model data points 15 used for monitoring and controlling the facility equipment 20 are defined, and identification information (tags, which will be described later) is defined for each model data point 15. In the model template 14, model data points 15 corresponding to the user interface and controls shown in FIG. 2 are set.
[0053] The device template 19 is a working area in which the device data points 16 are arranged. The device data points 16 are generated based on the device template 19 prepared for each model number of the equipment 20, and in the device template 19, all the device data points 16 held by the equipment 20 are defined, and identification information (tags, described later) is defined for each device data point 16. In the device template 19, the device data points 16 shown in FIG. 2 are set.
[0054] A model template 14 is prepared for each type of equipment 20, and a device template 19 is prepared for each model number. The type represents the series name or brand name of the equipment 20. The model number corresponds to the model of the equipment 20 developed under the same series name or brand name. In Fig. 4, air conditioner A001, air conditioner A002, and air conditioner B001 are model numbers, and air conditioner A and air conditioner B are types.
[0055] An installation worker adds device templates 19 and model templates 14 to the station template 17 to create the functions of the equipment management system 100. In other words, the station template 17 is the foundation of the equipment management system, and brings together the device templates 19 and model templates 14.
[0056] The station template 17 has two layers (a model layer 18b and a driver layer 18a). The driver layer 18a is a layer on the equipment 20 side, and the model layer 18b is a layer on the user interface side. In the driver layer 18a on the equipment 20 side, a device template 19 is arranged for each model number of the equipment 20. In the device template 19, device data points 16 that hold data input and output to the equipment 20 are set. In the model layer 18b on the user interface side, a model template 14 is arranged for each type of equipment 20. In the model template 14, model data points 15 that hold data related to the equipment 20 are set. Since there is a relationship that the number of model numbers is greater than or equal to the number of types, the number of device data points 16 that the device template 19 has is greater than or equal to the number of model data points 15 that the model template 14 has. By grouping the model data points 15 in the model template 14 into types that are in the same product category, it is not necessary to create many patterns of model templates 14, and the labor costs can be reduced. Furthermore, the model data points 15 and device data points 16 are connected based on the link rules of the model template 14, so that the number of connection processes can be reduced.
[0057] The device data point 16 and the model data point 15 each hold data. The data held by the device data point 16 can be referenced by the controller 32, and the data set in the model data point 15 can be referenced by the user interface. The model data point 15 receives data transmitted from the equipment 20 to the device data point 16 connected to the model data point 15. This data is processed according to the model data point 15, such as display processing and logic processing. The device data point 16 receives data transmitted from the model data point 15 connected to the device data point 16 and transmits it to the equipment 20. The correspondence information creation device 60 of the present disclosure automatically connects the device data point 16 of the device template 19 to the model data point 15 of the model template 14 in the equipment management device 10 so that the model data point 15 and the device data point 16 can be referenced.
[0058] Next, automatic connection between device data points 16 and model templates 14 by a software tool will be described with reference to Fig. 5. Fig. 5 is a diagram for explaining the configuration of a software tool that operates on a correspondence information creation device 60. As shown in Fig. 5, in the software tool, a model template 14 and a device template 19 are placed in a station template 17. These can be set by an installation worker. In the station template 17, the layer in which the model template 14 is placed is called the above-mentioned model layer 18b, and the layer in which the device template 19 and data conversion template 31 are placed is called the driver layer 18a.
[0059] In the model template 14, a plurality of 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 stored together in the same folder 33. Circles and squares under the folder 33 indicate model data points 15. The reason why the installation worker stores the model data points 15 in the folders 33 in this way is to make management easier since there are many of them, and to limit the model data points 15 that are the target of the connection process to those in the folder 33 even if model data points 15 with the same identification information (tags described later) exist in the entire system.
[0060] The device template 19 also has one or more folders 35. In FIG. 5, the device template 19 has one folder 35, but typically, multiple folders 35 exist. The folder 35 contains one or more device data points 16. Device data points 16 with similar functions are stored together in the same folder 35. Circles below the folder 35 indicate device data points 16. The installation worker stores the device data points 16 in the folder 35 in this way for two reasons: to make management easier since there are many of them, and to limit the device data points 16 that are the target of the connection process to those in the folder 35, even if device data points 16 with the same identification information (tags, described later) exist in all systems.
[0061] In addition, a data conversion template 31 may be used to convert the data format of the device data points 16 of the device template 19 to conform to the data format of the model template 14 (or vice versa). The data conversion template 31 is a model of a tool for converting between the data formats of the device data points 16 and the model data points 15.
[0062] The data conversion template 31 also has one or more folders 36. Although the data conversion template 31 has one folder 36 in Fig. 5, this is merely for convenience of drawing, and typically there are multiple folders 36. The folder 36 contains one or more conversion data points 34. The data conversion template 31 has a conversion data point 34a on the model template 14 side and a conversion data point 34b on the device template 19 side.
[0063] In the present disclosure, the correspondence information creating device 60 automatically performs the above-mentioned connection B. The function in the software tool that automatically performs the connection is called the autolink module 30. The autolink module 30 operates in the driver layer 18a, but may also operate in the model layer 18b or in both the driver layer 18a and the model layer 18b. The autolink module 30 connects the device data points 16 and the model data points 15 based on the link rules. The link rules will be described in detail with reference to FIG. 12.
[0064] <Example of connecting device data points and model data points> Based on the above configuration, an outline of the automatic connection of the present disclosure will be described. First, the introduction operator assigns tags (identification information) to each of the device data points 16 and the model data points 15. The correspondence information creation device 60 identifies the device data points 16 of the device template 19 to be connected to the model data points 15 of the model template 14 based on the tags, and automatically connects them. Furthermore, when the data formats of the model template 14 and the device template 19 are different, the correspondence information creation device 60 connects the device data points 16 of the device template 19 to the conversion data points 34b of the data conversion template 31, and automatically connects the conversion data points 34a to the model data points 15 of the model template 14.
[0065] Fig. 6 is a diagram for explaining an example of connections between device data points 16 and model data points 15. As shown in Fig. 6, a device template 19 has a plurality of device data points 16, and a model template 14 has a plurality of model data points 15. Each of the device data points 16 and the model data points 15 corresponds to one piece of data. The facility management system handles various types of data, such as room temperature, fan on / off, or air outlet temperature.
[0066] The installation worker sets tags indicating characteristics to the device data points 16 and each model data point 15. The tags serve as identification information for the device data points 16 and the model data points 15, and the installation worker may set tags that are easy to distinguish. When performing automatic connection, the correspondence information creation device 60 searches for the tag of the model data point 15 in the model template 14 and the device data point 16 in the device template 19 that has the same tag, and connects them.
[0067] 6, data conversion templates 31 are arranged for some of the model data points 15. Since the installation worker knows the data format of the device data points 16 in the device template 19 and the data format of the model data points 15 in the model template 14, if the data formats of the two are different, the installation worker prepares a data conversion template 31 to be set between the device template 19 and the model template 14. When performing an automatic connection, for example, the installation worker selects the device template 19 and the model template 14 that require the data conversion template 31 using a software tool, and then executes the connection process.
[0068] <Hardware configuration example> Fig. 7 is a hardware configuration diagram of the equipment management device 10 and the correspondence information creation device 60. As shown in Fig. 7, 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, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.
[0069] Among these, the CPU 501 controls the operation of the entire computer 500. 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 reading or writing of various data from the HD 504 under the control of the CPU 501. The display 506 displays various information such as a cursor, a menu, a window, a character, or an image. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. 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, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG. 7.
[0070] Moreover, the keyboard 511 is a type of input means having a plurality of 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 DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513 as an example of a removable recording medium. The DVD-RW may be a DVD-R or the like. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515 such as a flash memory.
[0071] <About the function> 8 is a functional block diagram of a correspondence information creating device 60 in which the autolink module 30 operates. This correspondence information creating device 60 may be any computer such as a PC. The correspondence information creating device 60 has a search unit 61, a display control unit 62, a relation setting unit 63, a link creating unit 64, and an operation receiving unit 65. Each of these functional units of the correspondence information creating device 60 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 correspondence information creating device 60. The programs may be software tools.
[0072] Furthermore, the correspondence information creating device 60 has a device template information storage unit 66, a model template information storage unit 67, a data conversion template information storage unit 68, and a link rule storage unit 69. Each of these storage units is constructed in the HD 504, the RAM 503, etc. shown in FIG.
[0073] The search unit 61 performs two searches. First, the search unit 61 searches the folder of the device template 19 for a tag name specified in the model template 14. A relationship is set between the folder of the model template 14 and the folder of the device template 19. Second, the search unit 61 searches for a device data point 16 that satisfies a link rule specified by the model data point 15 within the set relationship.
[0074] The display control unit 62 displays various screens for the installation operator to operate the software tools (the station template 17, the model template 14, the device template 19, the data conversion template 31, etc.).
[0075] The relation setting unit 63 sets a relation between the folder 33 of the model template 14 that the search unit 61 has determined to match the search and the folder 35 of the device template 19. The relation limits the range of device data points 16 to be searched. The relation setting unit 63 also sets a relation between the folder 33 of the model template 14 and the folder 36 of the data conversion template 31, and between the folder 36 of the data conversion template 31 and the folder 35 of the device template 19.
[0076] The link creation 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, which the search unit 61 has determined to match the search. This link corresponds to the connection (association) of the device data point 16 and the model data point 15 in this disclosure. In addition, the link creation unit 64 creates a link between the conversion data point 34 of the data conversion template 31 and the device data point 16 of the device template 19, which the search unit 61 has determined to match the search, and creates a link between the conversion data point 34 of the data conversion template 31 and the model data point 15 of the model template 14.
[0077] The operation receiving unit 65 receives various operations performed by an installation worker on the software tools running on the correspondence information creating device 60 .
[0078] Fig. 9 is an example of device template information stored in the device template information storage unit 66. The device template information in Fig. 9 shows device data points 16 that a device template 19 has. The device template information has the following items: model number ID, tag, and device data point ID. The model number ID field stores identification information of the model number of the equipment 20 that corresponds to the device template 19. The tag field stores a name by which the installation operator identifies the device data point 16. The tag field stores tags to be searched. The tags of device data points 16 are searched when they are connected to model data points 15 or conversion data points 34. The device data point ID stores the identification information of the device data point 16 set in the software.
[0079] Fig. 10(a) is an example of model template information stored in the model template information storage unit 67. The model template information in Fig. 10(a) indicates model data points 15 that a model template 14 has. The model template information has items of type ID, tag, and model data point ID. The type ID field stores identification information for the type of equipment 20 that corresponds to the model template 14. The tag item stores a name by which the installation operator identifies the model data point 15. The tag of the model data point 15 is searched for when it is connected to the device data point 16 or the conversion data point 34. The link rule ID item stores identification information of the link rule set in the model data point 15. A link rule is prepared for each model template 14. The model data point ID stores the identification information of the model data point 15 set in the software.
[0080] 10(b) shows link rule information associated with a certain model template 14. One or more link rules are prepared for each model template 14.
[0081] Fig. 11(a) is an example of data conversion template information stored in the data conversion template information storage unit 68. The data conversion template information in Fig. 11(a) shows the conversion data points 34 that the data conversion template 31 has. The data conversion template information has the following items: type ID, tag, and conversion data point ID. The type ID may be the same as that of the model template information. The tag field stores the name by which the installation operator identifies the conversion data point 34. There are tags for device data points and tags for model data points. These may be the same. The tag of the conversion data point 34 is searched for when it is connected to a device data point 16 or a model data point 15. · The conversion data point ID stores the identification information of the conversion data point set in the software. Separate IDs may be assigned for device data points and model data points.
[0082] 11(b) shows link rule information associated with a certain data conversion template 31. One or more link rules are prepared for each data conversion template 31. The link rule ID (for device data point) item stores identification information of a link rule for connecting the device data point 16 of the device template 19 and the transformation data point 34 of the data transformation template 31. The link rule ID (for model data point) item stores identification information of a link rule for connecting the model data point 15 of the model template 14 and the transformation data point 34 of the data transformation template 31.
[0083] The link rule may be the same on the device data point 16 side and the model data point 15 side.
[0084] 12 shows an example of a link rule. The link rule is a rule for connecting a model data point 15 and a device data point 16. The link rule is also a rule for connecting a transformation data point 34 and a device data point 16, and a rule for connecting a transformation data point 34 and a model data point 15.
[0085] Link rules are set only for the model template 14 and the data conversion template 31 (not for the device data points 16). When the installation technician adds the model template 14 and the data conversion template 31 to the station template 17, the installation technician also sets the link rules.
[0086] The link rule has the following items:
[0087] · Rule Name 201 is the name of the link rule, and is arbitrarily set by the installation operator.
[0088] The Device Relationship 202 indicates a relationship for creating a link. The relationship indicates a location for creating a link, regardless of data transfer. A suitable example of a relationship is a relationship between folders.
[0089] Point Query 203 indicates a query (search condition) for searching tags of device template 19. In FIG. 12, "hs:alarm and hs:sensor" is entered in Point Query 203. This means that device data points 16 that match the names (tags) of hs:alarm and hs:sensor in the device template 19 are to be connected to the model data point 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. The user can specify the device data points 16 to be connected in the query.
[0090] In the case of a link rule of the data conversion template 31, a query for searching the tags of the device data points 16 and the model template 14 may be set in the Point Query 203.
[0091] Link Direction 204 is the direction of the link as seen from the model template 14 or the data conversion template 31. In is data input from the device template 19 to the model template 14. In is data input from the device template 19 to the data conversion template 31. In is data input from the data conversion template 31 to the model template 14. Out is the opposite of these.
[0092] ·From Slot Name 205 is the name of the starting point.
[0093] ·To Slot Name 206 is the name of the destination.
[0094] <Action or Processing> With reference to Fig. 13, the work performed by the installation worker for the autolink module 30 will be described. This work is a preparation for the autolink module 30 to create a link. Fig. 13 is a flow chart showing the work performed by the installation worker for the correspondence information creation device 60 in which the autolink module 30 operates.
[0095] The installation worker operates the correspondence information creation device 60 to add a station template 17 (S1). That is, the installation worker prepares a station template 17 (an abstraction of the equipment management system represented in software) to which the device template 19 and the model template 14 are to be added.
[0096] Then, the installation worker adds the device template 19 to the station template 17 (S2). The installation worker adds the model template 14 to the station template 17 (S3).
[0097] Furthermore, if the installation worker needs to convert the data format of the device data points 16 in the device template 19 to make them compatible with the model template 14 (Yes in S4), he or she adds a data conversion template 31 to the station template 17 (S5).
[0098] Next, a process for connecting the device data point 16 and the model data point 15 will be described with reference to Fig. 14. Fig. 14 is a flow chart for explaining a process in which the auto link module 30 connects the model data point 15 of the model template 14 to the device data point 16 of the device template 19. Fig. 14 describes a case in which the model data point 15 of the model template 14 is connected to the device data point 16 of the device template 19, but the same can be applied to a case in which the conversion data point 34 of the data conversion template 31 is connected to the device data point 16 of the device template 19, and a case in which the conversion data point 34 is connected to the model data point 15.
[0099] First, the installation worker adds a template incorporating the autolink module 30 to the station template 17 (S11). The autolink module 30 refers to the link rules set in the model template 14 or the data conversion template 31 one by one. The installation worker may specify the type of equipment 20 (i.e., the model template 14) and have the autolink module 30 process only that type. Alternatively, the autolink module 30 may process different types of equipment 20 in sequence.
[0100] The search unit 61 of the autolink module 30 searches the device template 19 for folders 33, 35 in which the equipment type specified by the installation worker is set (S12). The equipment type refers to the type of facility equipment 20, such as air conditioner or lighting. In other words, the connection process is performed for each facility equipment 20. The folders 33, 35 are created for each facility equipment 20, and the device data points 16 and model data points 15 are classified according to their functions and properties under the folders 33, 35 for the facility equipment 20. The lower folders 33, 35 may be, for example, folders representing temperature, folders representing humidity, etc.
[0101] If folders 33, 35 having the device type in step S12 exist in the model template 14 and the device template 19 (Yes in S13), the display control unit 62 displays a list of folders 33, 35 having the device type in step S12 (S14).
[0102] The installation operator designates the folder 33 on the model template 14 side and the folder 35 on the device template 19 side to which a relationship is to be established (S15). The operation reception unit 65 receives the designation.
[0103] The relation setting unit 63 of the auto link module 30 sets a relation between the folder 33 and the folder 35 specified by the installation operator (S16). A relation is a place where a link is created, although data is not exchanged.
[0104] Next, the search unit 61 acquires a link rule associated with the model template 14 having the folder 33 to which the relation is established (see FIG. 10). The search unit 61 searches for device data points 16 and model data points 15 that satisfy the link rule within the relation set in step S16 (within the folder 35 of the device template 19 and the folder 33 in the model template 14) (S17). That is, the search unit 61 searches for device data points 16 and model data points 15 that have tags that match the query set in the Point Query of the link rule.
[0105] If there are device data points 16 and model data points 15 that match the search in step S17 (Yes in S18), the link creation unit 64 creates a link between the model data point 15 in the model template 14 and the device data point 16 in the device template 19 (S19).
[0106] If there are no device data points 16 or model data points 15 that match the search in step S18 (No in S18), the search unit 61 determines whether there is a next link rule associated with a model template 14 that has a folder 33 to which a relationship is established (S20).
[0107] If there is a next link rule, the process returns to step S17 (S21), and if there is no next link rule, the process of FIG. 14 ends.
[0108] 14 twice, once on the device template 19 side and once on the model template 14 side. The search unit 61 searches for a tag for the device data point of the conversion data point 34 in the Point Query of the link rule (for device data point) of the data conversion template 31, and searches for the tag of the device data point 16. The search unit 61 searches for a tag for the model data point of the conversion data point 34 in the Point Query of the link rule (for model data point) of the data conversion template 31, and searches for the tag of the model data point 15.
[0109] If the search matches, the link creation unit 64 connects the device data point 16 of the device template 19, which has a tag that matches the Point Query of the link rule (for device data point), to the conversion data point 34 of the data conversion template 31. The link creation unit 64 connects the model data point 15 of the model template 14, which has a tag that matches the Point Query of the link rule (for model data point), to the conversion data point 34 of the data conversion template 31.
[0110] <Matching information created by the autolink module> Fig. 15 is a diagram for explaining the correspondence information created by the autolink module 30. In Fig. 15, the layers closer to the user are shown from left to right. The device template 19 has numbers 1 to 6 (device data points 16), and the model template 14 has numbers 1 to 6 (model data points 15).
[0111] The auto link module 30 connects model data points 15 and device data points 16 with the same number (representing a tag) based on the link rule. Furthermore, for device data points 16 and model data points 15 that require data conversion, the model data points 15 and device data points 16 are connected via a data conversion template 31. The dotted lines connecting the numbers indicate links created by the link creation unit 64. One or more links are correspondence information 40.
[0112] By connecting in this manner, the equipment management system 100 changes the data held in the model data points 15 when the data held in the device data points 16 is changed, and changes the data held in the device data points 16 when the data held in the model data points 15 is changed, and outputs a data change request to the equipment 20.
[0113] The program module unit 41 is a group of software that provides the functions of the equipment management system 100. The program module unit 41 performs, for example, screen creation, alarm notification, graph creation, schedule management, and tag information management.
[0114] The user interface unit 42 is a function for constructing screens to be displayed on the display. The user interface unit 42 displays screens such as a calendar, user management, a dashboard (displaying various data such as multiple graphs and tables), and alarm management.
[0115] <Data format conversion> 16 to 20, a description will be given of data relay and data format conversion by the data conversion template 31. A conversion data point 34 is set in the data conversion template 31, and the conversion data point 34 converts the data format and relays data of the device data point 16 to the model data point 15, or relays data of the model data point 15 to the device data point 16.
[0116] 16A to 16C are diagrams for explaining data formats. As shown in (a) to (c) of FIG. 16, 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 model data point 15 that controls the ON / OFF of an air conditioner are True (representing ON) and False (representing OFF).
[0117] Numeric is a data format that takes a single numeric value. The value can be either an integer or a decimal. For example, a model data point 15 that displays the room temperature may have a numeric value of 24.6°C, and a model data point 15 that displays the room humidity may have a numeric value of 62%.
[0118] Multi is a data format that has a value of "key: value". The key can be an integer, and the value can be true / false, a number, or a character string. For example, the values of the Multi format taken by model data point 15 that controls the operation mode of an air conditioner include "1: automatic", "2: cooling", "3: heating", "4: fan", "5: OFF", etc.
[0119] The data conversion template 31 can convert the Boolean, Numeric, and Multi data formats from one to another and from one to the other.
[0120] Fig. 17 shows an example of data conversion in which Multi is converted to Boolean and Multi. The conversion example in Fig. 17 is a data conversion in which, when there is no device data point 16 indicating whether an air conditioner is ON or OFF in the device template 19, but the model template 14 is specified to indicate whether the air conditioner is ON or OFF, data in the Multi format held by the device data point 16 is converted to data in the Boolean and Multi formats held by the model data point 15.
[0121] The device data point 16 of the device template 19 is a device data point 16 that displays the operation mode. The data format is Multi, and the device data point 16 has the values "1: automatic", "2: cooling", "3: heating", "4: fan", and "5: OFF".
[0122] On the other hand, in model template 14, the installer wants to display whether the air conditioner is ON or OFF. Also, model template 14 also has a Multi type data format, but the "key: value" is different from the "key: value" of device template 19.
[0123] For this reason, the data conversion template 31 performs the following conversion. First, the data conversion template 31 converts the values of the Multi format indicated by the device data point 16, "1: automatic", "2: cooling", "3: heating", and "4: fan", to ON in the Boolean format (an example of a first data format), and similarly converts "5: OFF" to OFF. In the model template 14, ON corresponds to True, and OFF corresponds to False. Furthermore, the data conversion template 31 converts the correspondence between the keys of the device template 19, which is a Multi format, and the keys of the model template 14, which is a Multi format (an example of a second data format). That is, the data conversion template 31 does not change keys=1 to 4, but converts key=5 to key=0. In the model template 14, 1 corresponds to automatic, 2 to cooling, 3 to heating, 4 to fan, and 0 to OFF.
[0124] By such conversion, the model template 14 can display ON or OFF even if the device data point 16 is not in Boolean data format. Also, the model template 14 can display the operation mode in Multi format even if the key correspondence between the device template 19 and the model template 14 is different.
[0125] In this case, the link creation unit 64 connects the Multi-format device data point 16 of the device 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.
[0126] In addition, the link creation unit 64 connects the device data point 16 of the Multi format in the device 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.
[0127] In addition, the link creation unit 64 connects the conversion data point 34c for Boolean → Multi conversion of the data conversion template 31 to the model data point 15c of Boolean format of the model template 14, and connects the conversion data point 34d for Multi → Multi conversion of the data conversion template 31 to the model data point 15d of Multi format of the model template 14.
[0128] As a result, the Multi format data held by the device data points 16 of the device 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 model data points 15 of the model template 14.
[0129] FIG. 18 shows an example of data format conversion in FIG. 17 when the same data format as that seen from the model template 14 does not exist in the device template 19. FIG. 18 explains the data flow seen from the model template 14. In FIG. 18, the device template 19 does not have the device data point 16 that commands the air conditioner in the model template 14 to be turned on or off. Therefore, a data conversion template 31 that commands the air conditioner to be turned on or off is required. Similarly, the correspondence between the keys and values of the Multi format in the model template 14 differs from the correspondence between the keys and values in the device template 19. Therefore, a data conversion template 31 that converts the operation mode of the model template 14 into the operation mode of the device template 19 is required.
[0130] 18, the data conversion template 31 converts True in the model template 14 to key=1 in the Multi format, and converts False in the model template 14 to key=5 in the Multi format. The data conversion template 31 also converts the correspondence between the key in the model template 14, which is the Multi format, and the key in the device template 19, which is also the Multi format. That is, the data conversion template 31 does not change keys=1 to 4, but converts key=0 to key=5.
[0131] By such conversion, the model template 14 can instruct the device template 19 to be ON or OFF even if the device data point 16 is not in the Boolean data format. Also, the model template 14 can instruct the device template 19 to be an operation mode in the Multi format even if the key correspondence between the device template 19 and the model template 14 is different.
[0132] The link creation unit 64 connects the Boolean format model data point 15c of the model template 14 to the conversion data point 34c for Boolean → Multi conversion of the data conversion template 31, and connects the Multi format model data point 15d of the model template 14 to the conversion data point 34d for Multi → Multi format conversion of the data conversion template 31.
[0133] In addition, the link creation unit 64 connects the conversion data point 34c for Boolean → Multi format conversion of the data conversion template 31 to the device data point 16 of the Multi format of the device data point 16. The link creation unit 64 connects the conversion data point 34d for Multi → Multi format conversion of the data conversion template 31 to the device data point 16 of the Multi format of the device template 19.
[0134] 18, the Boolean format data held by the model data point 15 of the model template 14 is converted to a Multi format key (True is 1, False is 5) by the data conversion template 31 and sent to the device data point 16 of the device template 19. The Multi format data held by the model data point 15 of the model template 14 has the key correspondence converted by the data conversion template 31 (0 is converted to 5) and sent to the device data point 16 of the device template 19.
[0135] Fig. 19 shows an example of data conversion in which Numeric is converted to Boolean and Multi. The conversion example in Fig. 19 is a data conversion in which the device data point 16 in the device template 19 displays the fan rotation speed, but the model template 14 displays the fan ON / OFF and operation mode.
[0136] The device data point 16 of the device template 19 is a device data point 16 that displays the fan rotation speed. The data format is Numeric. On the other hand, the model template 14 is a specification that displays whether the fan is ON or OFF. The model template 14 is also a specification that displays the operation mode ("1: OFF", "2: Low", "3: Medium", "4: High").
[0137] For this reason, the data conversion template 31 performs the following conversion. First, if the value (Numeric) indicated by the device data point 16 is 0, the data conversion template 31 converts it to False, and if it is greater than 0, it converts it to True. In the model template 14, ON corresponds to True, and OFF corresponds to False. Furthermore, the data conversion template 31 converts this value to a Multi format key (1 to 4) according to the value (Numeric) indicated by the device data point 16. That is, the data conversion template 31 converts the fan rotation speed to key=1 when the fan rotation speed is 0, converts it to key=2 when the fan rotation speed is 1 to 100, converts it to key=3 when the fan rotation speed is 101 to 500, and converts it to key=4 when the fan rotation speed is over 500. In the model template 14, 1 corresponds to OFF, 2 corresponds to weak, 3 corresponds to medium, and 4 corresponds to strong. These numerical values are merely examples.
[0138] By such conversion, even if the device data points 16 are not in Boolean data format, the model template 14 can display ON or OFF converted from the fan rotation speed. Also, even if the device template 19 is not in Multi format, the model template 14 can display the operation mode in Multi format.
[0139] The link creation unit 64 connects the numeric format device data point 16 of the device template 19 to the conversion data point 34e for Numeric → Boolean conversion of the data conversion template 31, and connects the numeric format device data point 16 to the conversion data point 34f for Numeric → Multi conversion of the data conversion template 31. The link creation unit 64 also connects the conversion data point 34e for Numeric → Boolean conversion of the data conversion template 31 to the Boolean format model data point 15e of the model template 14, and connects the conversion data point 34f for Numeric → Multi conversion of the data conversion template 31 to the Multi format model data point 15f of the model template 14.
[0140] As a result, the Numeric format data held by the device data points 16 of the device template 19 is converted to Boolean format data and Multi format data by the data conversion template 31, and sent to the Boolean and Multi format model data points 15 of the model template 14.
[0141] FIG. 20 shows an example of data format conversion when the data formats of the fan rotation speed and operation mode are different between the model template 14 and the device template 19 in FIG. 19. FIG. 20 explains the data flow as seen from the model template 14. In FIG. 20, the device template 19 does not have the device data point 16 that commands ON or OFF of the fan that the model template 14 has. Therefore, a data conversion template 31 that commands ON or OFF of the fan is required. Similarly, the device template 19 does not have the device data point 16 that displays the operation mode that the model template 14 has. Therefore, a data conversion template 31 that displays the operation mode is required.
[0142] 20, the data conversion template 31 converts True in the model template 14 to 100 rpm in numeric format, and converts False in the model template 14 to 0 rpm in numeric format. The data conversion template 31 also converts the "1" in "1: OFF" in the Multi format of the model template 14 to 0 in numeric format, the "2" in "2: Weak" in the Multi format of the model template 14 to 100 in numeric format, the "3" in "3: Medium" in the Multi format of the model template 14 to 300 in numeric format, and the "4" in "4: Strong" in the Multi format of the model template 14 to 500 in numeric format.
[0143] By such conversion, the model template 14 can instruct the device template 19 to turn the fan ON or OFF even if the device data points 16 are not in Boolean data format. Also, even if the device template 19 is not in Multi format, the model template 14 can instruct the device template 19 of the operation mode in Multi format.
[0144] The link creation unit 64 connects the model data point 15e in the Boolean format of the model template 14 to the conversion data point 34e for Boolean → Numeric conversion of the data conversion template 31, and connects the model data point 15f in the Multi format of the model template 14 to the conversion data point 34f for Multi → Numeric conversion of the data conversion template 31. In addition, the link creation unit 64 connects the conversion data point 34e for Boolean → Numeric format conversion of the data conversion template 31 to the device data point 16 in the Numeric format of the device template 19, and connects the conversion data point 34f for Multi → Numeric conversion of the data conversion template 31 to the device data point 16 in the Numeric format of the device template 19.
[0145] 20, the Boolean format data held by the model data point 15e of the model template 14 is converted into a fan rotation speed in the Numeric format by the data conversion template 31 and sent to the device data point 16 of the device template 19. The Multi format data held by the model data point 15f of the model template 14 is converted into a fan rotation speed by the data conversion template 31 and sent to the device data point 16 of the device template 19. Therefore, even if the device template 19 does not have the device data point 16 that commands the fan to be turned ON or OFF, which the model template 14 has, the user can command the fan to be turned ON or OFF. Even if the device template 19 does not have the device data point 16 that handles the operation mode that the model template 14 has, the user can command the operation mode.
[0146] 17 to 20, data conversion template 31 converts one data format into two data formats, but one data format may be converted into three or more data formats. Data conversion template 31 may also convert one data format of model template 14 into two or more data formats of device template 19.
[0147] <Major Effects> The information processing method of the present disclosure reduces operator errors and reduces the number of steps required for on-site connection tests, etc., compared to manually connecting device data points 16 and model data points 15. Reducing the number of steps required to build the facility management system 100 makes it possible to reduce necessary expenses.
[0148] <Other application examples> The above describes the best mode for carrying out the present disclosure using examples, but the present disclosure is not limited to these examples in any way, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present disclosure.
[0149] For example, while the present disclosure has been described with respect to the facility management system 100, it is also suitable for use in connecting one data point to another data point within software.
[0150] Furthermore, the process of automatically associating the device data points 16 with the model data points 15 may be performed by the equipment management device 10 instead of the correspondence information creating device 60 .
[0151] Also, in the present disclosure, the model template 14 or the data transformation template 31 has been described as having a link rule, but the link rule may be associated with the model data points 15 or the transformed data points 34 .
[0152] Moreover, the configuration example in Fig. 8 and the like is divided according to main functions in order to facilitate understanding of the processing by the correspondence information creation device 60. The present disclosure is not limited by the manner in which the processing units are divided or the names thereof. The processing of the correspondence information creation device 60 can also be divided into more processing units according to the processing contents. Also, it can be divided so that one processing unit includes more processes.
[0153] Moreover, the devices described in the examples are merely one of a number of computing environments for implementing the embodiments disclosed herein. In one embodiment, the correspondence information creating device 60 includes a number of computing devices, such as a server cluster. The computing devices are configured to communicate with each other via any type of communication link, including a network, shared memory, and the like, and perform the processes disclosed herein.
[0154] Each function of the present disclosure described above can be realized not only by software processing by executing a program, but also by one or more processing circuits. Here, the "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and a device such as a conventional circuit module designed to execute each function described above.
[0155] <Reasons for the effect> In the first aspect of the present disclosure, "a control unit associates model data points, which hold data used in an application for monitoring and controlling facility equipment, with device data points, which hold data input or output from the facility equipment installed in a property, based on identification information assigned to the model data points and the device data points," so that the manual association work can be automated and the association work burden can be reduced. The identification information in the first aspect is a character, a number, a symbol, an alphabet, or a combination thereof for uniquely identifying or specifying the model data point 15 or the device data point 16. In this embodiment, it is described by the term tag.
[0156] In the second aspect of the present disclosure, "the model data points are generated based on a model template prepared for each type of facility equipment", so by grouping model data points 15 in a model template 14 into types in the same product category, it is not necessary to create many patterns of model templates 14, and labor costs can be reduced. Also, "the model template defines the model data points used for monitoring and controlling the facility equipment, and also defines identification information for each of the model data points", so that the facility equipment can be monitored and controlled by the model data points.
[0157] In a third aspect of the present disclosure, "the equipment management device holds link rules that define identification information assigned to the model data points and device data points to be matched, and the control unit determines and matches the model data points and device data points to be matched based on the link rules," so a user can control the connection between model data points and device data points by appropriately setting link rules.
[0158] In the fourth aspect of the present disclosure, "the device data points are generated based on a device template prepared for each model number of the equipment, and all of the device data points held by the equipment are defined in the device template, and identification information is defined for each of the device data points." Therefore, the connection between model data points 15 and device data points 16 is based on the link rule of model template 14, thereby reducing the number of connection processes.
[0159] The fifth technology of the present disclosure is such that "when the data held in the device data point is changed, the control unit changes the data held in the model data point, and when the data held in the model data point is changed, the control unit changes the data held in the device data point and outputs a data change request to the equipment", so that the equipment management device 10 displays the data transmitted from the device data point 16 so that the user can confirm it, and when the user changes the data, this data can be transmitted to the equipment 20.
[0160] In the sixth aspect of the present disclosure, model data points are generated based on a model template prepared for each type of equipment 20, and device data points 16 are generated based on a device template prepared for each model number of equipment 20, and "the model data points of the model template and the device data points of the device template are associated with each other based on identification information assigned to the model data points and the device data points", so that the type of equipment 20 and the data points of the model number that matches it can be connected.
[0161] The seventh aspect of the present disclosure "associates the transformed data point with the device data point based on identification information assigned to the transformed data point and the device data point, and associates the transformed data point with the model data point based on identification information assigned to the transformed data point and the model data point," thereby converting the data format of device data point 16 into the data format of model data point, and converting the data format of model data point 15 into the data format of device data point 16.
[0162] The eighth aspect of the present disclosure "converts the data format of data output by a device data point into a first data format and a second data format corresponding to the model data point associated with the conversion data point" and "converts the first data format and the second data format corresponding to the model data point into a data format of data input to the device data point associated with the conversion data point", so that even if model data point 15 holds data in two data formats, one data format of device data point 16 can be converted into the data format of model data point 15.
[0163] The ninth aspect of the present disclosure is capable of converting a data format having multiple pairs of keys and values handled by the device data point 16 into a binary data format and a data format having multiple pairs of keys and values handled by the model data point 15, or The binary data format and data format having multiple pairs of keys and values handled by the model data point 15 can be converted into a data format having multiple pairs of keys and values handled by the device data point 16.
[0164] The tenth aspect of the present disclosure is capable of converting a numerical data format handled by the device data point 16 into a binary data format handled by the model data point 15 and a data format having multiple pairs of keys and values, or The model data point 15 can convert binary data formats and data formats having multiple key-value pairs into the numeric data formats handled by the device data point 16 . [Explanation of symbols]
[0165] 14 Model Templates 15 data points 16 Device Data Points 19 Device Templates 20 Equipment 60 Response information creation measures 100 Facility Management System
Claims
1. The facility management device that manages the facility equipment A model data point that holds data used in an application that monitors and controls the facility equipment; A method for associating a property with a device data point that holds data input or output from the facility equipment installed in the property, comprising: The control unit holds a link rule that defines a search condition for searching for identification information assigned to the model data point and the device data point, A method for matching the model data points with the device data points having identification information that matches the search criteria.
2. The model data points are generated based on a model template prepared for each type of the facility equipment, The method according to claim 1 , wherein the model template defines the model data points used for monitoring and controlling the facility equipment, and defines identification information for each of the model data points.
3. A method according to claim 1 or 2, wherein the control unit determines which model data points and which device data points are to be associated based on the link rule, and associates the model data points and the device data points.
4. The device data points are generated based on a device template prepared for each model number of the equipment, The method according to claim 1 , wherein all of the device data points held by the equipment are defined in the device template, and identification information is defined for each of the device data points.
5. The control unit is modifying the data held in said model data points if the data held in said device data points is modified; The method according to claim 1 , further comprising the steps of: modifying data held in the device data points when the data held in the model data points is changed; and outputting a data change request to the facility equipment.
6. The model data points are generated based on a model template prepared for each type of the facility equipment, In the model template, the model data points used for monitoring and controlling the facility equipment are defined, and identification information is defined for each of the model data points. The device data points are generated based on a device template prepared for each model number of the equipment, In the device template, all of the device data points held by the equipment are defined, and identification information is defined for each of the device data points; The method according to claim 1 , wherein the control unit associates the model data points of the model template with the device data points of the device template based on identification information assigned to the model data points and the device data points.
7. a data conversion template for converting the data format of the device data points into the data format of the model data points, or converting the data format of the model data points into the data format of the device data points; A transformation data point is set to relay data of the device data point to the model data point or to relay data of the model data point to the device data point; The control unit associates the conversion data point with the device data point based on identification information assigned to the conversion data point and the device data point, The method according to claim 1 , wherein the transformed data points and the model data points are associated with each other based on identification information given to the transformed data points and the model data points.
8. The data conversion template converts a data format of data output by the device data point associated with the conversion data point into a first data format and a second data format corresponding to the model data point associated with the conversion data point, or 8. The method of claim 7, wherein the first and second data formats corresponding to the model data points associated with the transformation data points are converted into a data format of data input to the device data points associated with the transformation data points.
9. The data transformation template transforms a data format having a plurality of pairs of key and value output by the device data point associated with the transformation data point into a binary data format and a data format having a plurality of pairs of key and value corresponding to the model data point associated with the transformation data point, or 8. The method of claim 7, wherein the model data points associated with the transformation data points are converted from a binary data format and a data format having multiple key-value pairs to a data format having multiple key-value pairs that is input to the device data points associated with the transformation data points.
10. The data transformation template transforms a numerical data format output by the device data point associated with the transformation data point into a binary data format and a data format having multiple key-value pairs corresponding to the model data point associated with the transformation data point, or 8. The method of claim 7, wherein the model data point associated with the transformation data point converts a binary data format and a data format having multiple key-value pairs to a numeric data format input to the device data point associated with the transformation data point.
11. An equipment management device that manages equipment, A model data point that holds data used in an application that monitors and controls the facility equipment; A control unit that associates the data input or output from the equipment installed in the property with a device data point, A link rule is stored that defines a search condition for searching identification information assigned to the model data point and the device data point, a control unit for associating the model data points with the device data points, the model data points having identification information that matches the search criteria; A facility management device having the above configuration.
12. Equipment management devices that manage equipment, A model data point that holds data used in an application that monitors and controls the facility equipment; A control unit that associates the data input or output from the equipment installed in the property with a device data point, A link rule is stored that defines a search condition for searching identification information assigned to the model data point and the device data point, a control unit for associating the model data points with the device data points having identification information that matches the search criteria; A program to function as a
Citation Information
Patent Citations
Monitoring system and its data management method
JP2007199798A
Engineering device and control logic verification method
JP2015146117A
I / O module, setting device, and method for constructing process control system
JP2016081415A
Management device
JP2022078390A
