JP6395910B1 - Device management system, data exchange system, data exchange method, and device management program - Google Patents

Abstract

To recognize a classification of a device even if information necessary for recognizing the classification of the device is not explicitly provided from the device. In a device management system, a device recognition unit acquires, from a recording medium, characteristic data that defines in advance a phenomenon that occurs when each device is activated for each category of the device. The device recognizing unit 130 collates the observation result of the phenomenon that occurs when the new device, which is the device 500 to be newly managed, is started up with the characteristic data 166. The device recognition unit 130 recognizes the classification of the new device from the collation result, and if the recognized classification matches the classification indicated in the classification information 162 registered by the device registration unit 110, the device recognition unit 130 selects the new device. Enable. [Selection] Figure 1

Description

  The present invention relates to a device management system, a data exchange system, a data exchange method, and a device management program.

  In a large-scale building such as a condominium, a building, or a factory, many measuring devices, control devices, electronic devices, and the like are installed. These devices are connected to a network and managed from various viewpoints such as energy saving, disaster prevention, and environment. Each device has a different encoding method such as analog or digital, a communication protocol such as TCP and HTTP, or a communication data format such as text, binary, or XML. Therefore, it is necessary to individually create software for accessing the device. “TCP” is an abbreviation for Transmission Control Protocol. “HTTP” is an abbreviation for Hypertext Transfer Protocol. “XML” is an abbreviation for Extensible Markup Language.

  Patent Document 1 describes a technique for constructing a network between a device installed in a building and a home server, and displaying the corresponding device and the cause of failure when the device fails to connect to the network. ing. In this technique, when a device can be connected, the operation confirmation status of the device and the installation location in the building are displayed.

  Patent Document 2 describes a technology for automatically recognizing a device such as a home appliance connected to a network, collecting necessary information from the recognized device, and setting the device based on the collected information. .

International Publication No. 2014/049849 JP 2000-269998 A

  In the technique described in Patent Document 1, it is necessary to input the installation location of the device in the system in advance. As the number of devices increases, it takes time to input. In addition, if the purpose of energy saving, monitoring control, or system control changes, the items to be handled and the evaluation method change, so the database may be recreated. In some cases, a device has a management method that differs depending on the purpose, and may be managed not only by a simple installation location such as the technique described in Patent Document 1, but also by a manufacturer, a price, a supplier, an installer, or the like. For example, regarding the temperature sensor, if the purpose is to evaluate the temperature distribution, the location of the temperature sensor need only be managed in the database, and the supplier of the temperature sensor need not be managed. However, when the purpose is changed to the evaluation of the supplier, it is necessary to recreate the database so that the supplier of the temperature sensor can be managed. In addition, devices may be managed according to a hierarchical structure. For example, if an air conditioner manufactured by B company is installed on the 7th floor of A building of XYZ apartment, management in the form of XYZ apartment-> A building-> 7F-> B company-> air conditioner can be considered. In such cases, if the target or management purpose changes, the database must be recreated. When the database is recreated, the device ID also changes. “ID” is an abbreviation for Identifier.

  In the technology described in Patent Document 2, the device to be recognized holds information necessary for device setting such as device type and device name in advance, or is required for device setting such as a file address or catalog number. It is necessary to store in advance information for acquiring external information. In addition, the device to be recognized needs to have a function of transmitting information. Therefore, a device that does not have such information and function is not recognized.

  An object of the present invention is to make it possible to recognize a classification of a device even if information necessary for recognizing the classification of the device is not explicitly provided from the device.

An apparatus management system according to an aspect of the present invention includes:
For each device classification, the characteristic data that predefines the phenomenon that occurs when each device is activated is acquired from the recording medium, and the observation result of the phenomenon that occurs when the new device that is the new management target device is activated is the characteristic data. And a device recognition unit that recognizes the classification of the new device from the comparison result.

  In the present invention, the classification of the device is recognized from the characteristics at the time of activation of the device. Therefore, even if information necessary for recognizing the classification of the device is not explicitly provided from the device, the classification of the device can be recognized.

1 is a block diagram showing a configuration of a data exchange system according to a first embodiment. 3 is a flowchart showing the operation of the data exchange system according to the first embodiment. FIG. 3 shows an input screen of the data exchange system according to the first embodiment. The figure which shows the completion screen of the data exchange system which concerns on Embodiment 1. FIG. 3 is a flowchart showing the operation of the data exchange system according to the first embodiment. 3 is a flowchart showing the operation of the data exchange system according to the first embodiment. 3 is a flowchart showing the operation of the data exchange system according to the first embodiment. 3 is a flowchart showing the operation of the data exchange system according to the first embodiment. FIG. 3 shows a selection screen of the data exchange system according to the first embodiment. FIG. 3 shows a selection screen of the data exchange system according to the first embodiment. The figure which shows the search screen of the data exchange system which concerns on Embodiment 1. FIG. The figure which shows the search screen of the data exchange system which concerns on Embodiment 1. FIG. 9 is a flowchart showing the operation of the data exchange system according to the second embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals. In the description of the embodiments, the description of the same or corresponding parts will be omitted or simplified as appropriate. The present invention is not limited to the embodiments described below, and various modifications can be made as necessary. For example, two or more embodiments among the embodiments described below may be combined and executed. Alternatively, among the embodiments described below, one embodiment or a combination of two or more embodiments may be partially implemented.

Embodiment 1 FIG.
This embodiment will be described with reference to FIGS.

*** Explanation of configuration ***
With reference to FIG. 1, the structure of the data exchange system 600 which concerns on this Embodiment is demonstrated.

  The data exchange system 600 includes a device management system 100, a manufacturer device 200, a developer device 300, a manager device 400, and a plurality of devices 500.

  The device management system 100 is a computer. The device management system 100 is a server such as a cloud system, for example.

  The manufacturer device 200 is a computer. The manufacturer device 200 is, for example, a PC. “PC” is an abbreviation for Personal Computer. The manufacturer apparatus 200 is connected to the device management system 100 via a network such as the Internet (not shown). The manufacturer device 200 is used for accessing the device management system 100 by a person in charge of a device manufacturer who is a manufacturer that manufactures the device 500.

  Developer device 300 is a computer. Developer device 300 is, for example, a PC. The developer device 300 is connected to the device management system 100 via a network such as the Internet (not shown). The developer device 300 is used by an application developer to access the device management system 100.

  The management company apparatus 400 is a computer. The management company device 400 is, for example, a PC. The management company apparatus 400 is connected to the device management system 100 via a network such as the Internet (not shown). The management company apparatus 400 is used for access to the equipment management system 100 by a person in charge of a system maker who is at least one of a developer of the equipment management system 100 and a management company.

  The device 500 is, for example, a measuring device such as a temperature sensor, a control device, an electronic device, a refrigeration device such as an air conditioner, or a lighting device. The device 500 is installed in a condominium room in this embodiment, but may be installed in a common part of the apartment, or may be installed in another place such as a building or a factory. The device 500 is connected to the device management system 100 via a network such as the Internet (not shown).

  The device management system 100 includes a processor 101 and other hardware such as a memory 102, an auxiliary storage device 103, an input device 104, a display 105, and a communication device 106. The processor 101 is connected to other hardware via a signal line, and controls these other hardware.

  The device management system 100 includes a device registration unit 110, a device configuration definition unit 120, a device recognition unit 130, an operation result collection unit 140, a similar device search unit 150, and a database 160. The functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are realized by software. The database 160 is constructed in the auxiliary storage device 103 in the present embodiment, but may be constructed in the memory 102.

  The database 160 is a graph database in the present embodiment, but may be another type of database such as a relational database.

  In the database 160, information about the device 500 is registered for each device 500 together with a device ID 161 that is an identifier for individually identifying the device 500. Information relating to the device 500 includes classification information 162 indicating the classification of the device 500, device configuration information 163 indicating the location where the device 500 is installed, attribute information 164 indicating the attributes of the device 500, and the frequency of failure of the device 500. Failure information 165 indicating the above. In the present embodiment, the classification information 162 is information indicating the model of the device 500, the device manufacturer that manufactured the device 500, and the model number of the device 500. The classification information 162 may include information indicating the name of the device 500 as information indicating the classification of the device 500, instead of the model of the device 500 or together with the model of the device 500. The classification information 162 may include information indicating the model name of the device 500 instead of the model number of the device 500 or together with the model number of the device 500 as information indicating the classification of the device 500. In the present embodiment, the device configuration information 163 is information indicating the apartment room in which the device 500 is installed. In the present embodiment, the attribute information 164 is information indicating the delivery date of the device 500, the price of the device 500, the contractor who installed the device 500, and the like. The failure information 165 may be information indicating the frequency of failure of the device 500 such as the number of failures of the device 500, but in the present embodiment, is information indicating the failure date of the device 500.

  The characteristic data 166 is also registered in the database 160. The characteristic data 166 is data in which a phenomenon that occurs when each device 500 is activated for each category of the device 500 is defined in advance. Specifically, the characteristic data 166 is data indicating a variation characteristic of at least one of the voltage and current output from each device 500 when the power to each device 500 is turned on for each classification of the device 500. Alternatively, the characteristic data 166 is data indicating a variation characteristic of at least one of sound and vibration generated from each device 500 when each device 500 is activated for each classification of the device 500. Alternatively, the characteristic data 166 is data indicating the timing at which two or more components included in each device 500 are activated when each device 500 is activated for each category of the device 500 with respect to the device 500 including two or more components. . Alternatively, the characteristic data 166 is data indicating the temperature fluctuation characteristics adjusted by each refrigeration device at the start of operation of each refrigeration device for each refrigeration device class, with respect to the device 500 roughly classified into refrigeration devices such as air conditioners. . Alternatively, the characteristic data 166 is data indicating the fluctuation characteristics of the light output from each lighting device at the start of lighting of each lighting device for each lighting device class, with respect to the device 500 roughly classified into lighting devices.

  In the present embodiment, the characteristic data 166 is provided from the equipment manufacturer in exchange for providing the operation data 167.

  The operation data 167 is data indicating the operation results of the device 500 to be managed for the device management system 100, that is, the device 500 whose information is registered in the database 160 and has already been validated. “Validation” refers to starting actual operation of the device 500. For example, if an initialization process necessary for actual operation is performed in a certain device 500, the device 500 is validated. The operation data 167 is specifically operation data, alarm data, and operation data.

  The operation data 167 may be registered in the database 160 or may be stored in the memory 102 or the auxiliary storage device 103 separately from the database 160. In any case, it is desirable that the operation data 167 is stored after being subjected to processing such as compression processing and statistical processing. This is because the storage capacity can be reduced as compared with the case where data collected from the device 500 is stored as it is. The operation data 167 is desirably data that has been subjected to processing such as compression processing and statistical processing even when provided to the device manufacturer.

  Information regarding the device ID 161 and the device 500 registered in the database 160 can be used as the search condition 168. The search result 169 can be obtained from the database 160 by providing the search condition 168 to the database 160.

  In this embodiment, the search condition 168 is specified by the system manufacturer. The search result 169 is returned to the system manufacturer.

  The processor 101 is a device that executes a device management program. The device management program is a program that realizes the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150. The processor 101 is a CPU, for example. “CPU” is an abbreviation for Central Processing Unit.

  The memory 102 and the auxiliary storage device 103 are examples of recording media. The memory 102 is, for example, a flash memory or a RAM. “RAM” is an abbreviation for Random Access Memory. The auxiliary storage device 103 is, for example, a flash memory or an HDD. “HDD” is an abbreviation for Hard Disk Drive.

  The input device 104 is a device operated by a user for inputting data to the device management program. The input device 104 is, for example, a mouse, a keyboard, or a touch panel.

The display 105 is a device that displays data output from the device management program on a screen. The display 105 is, for example, an LCD. "LCD" is Liquid
Abbreviation for Crystal Display.

  The communication device 106 includes a receiver that receives data input to the device management program and a transmitter that transmits data output from the device management program. The communication device 106 is, for example, a communication chip or a NIC. “NIC” is an abbreviation for Network Interface Card.

  The device management program is stored in advance in the auxiliary storage device 103, loaded into the memory 102, and executed by the processor 101. The auxiliary storage device 103 stores not only the device management program but also the OS. “OS” is an abbreviation for Operating System. The processor 101 executes a device management program while executing the OS.

  Part or all of the device management program may be incorporated in the OS.

  The device management system 100 may include a plurality of processors that replace the processor 101. The plurality of processors share the execution of the device management program. Each processor is, for example, a CPU.

  Data, information, signal values, and variable values used, processed, or output by the device management program are stored in the memory 102, the auxiliary storage device 103, or a register or cache memory in the processor 101.

  The device management program causes the computer to execute each process in which “part” in the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 is replaced with “processing”. It is a program. Alternatively, the device management program stores each procedure obtained by replacing “unit” in the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 with “procedure”. It is a program to be executed. The device management program may be provided by being recorded on a computer-readable medium, or may be provided as a program product.

  The device management system 100 may be configured by a single computer or may be configured by a plurality of computers. When the device management system 100 is composed of a plurality of computers, the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are included in each computer. It may be realized by being distributed. The database 160 may be constructed on any one computer, or may be constructed distributed over two or more computers.

*** Explanation of operation ***
The operation of the data exchange system 600 according to the present embodiment will be described with reference to FIGS. 2 to 12 in addition to FIG. The operation of the data exchange system 600 corresponds to the data exchange method according to the present embodiment.

  The operation of the data exchange system 600 when the device manufacturer registers the device 500 in the device management system 100 will be described with reference to FIG.

  Here, a flow for registering the device 500 newly installed in the apartment in the device management system 100 according to the information input on the input screen 171 as shown in FIG. 3 will be described. The input screen 171 is displayed on the display of the manufacturer apparatus 200 by an application such as a web browser operating on the manufacturer apparatus 200 based on data such as an HTTP message transmitted from the device management system 100.

  In step S <b> 11, the device registration unit 110 of the device management system 100 accepts input of information on the input screen 171 by the person in charge of the device manufacturer who has accessed the device management system 100 from the manufacturer apparatus 200. Based on the input information, the device registration unit 110 checks the database 160 to determine whether there is a component that is a basic model of the newly installed device 500. In the present embodiment, since the database 160 is a graph database, the node of the directed graph corresponds to “component”. Here, it is assumed that the air conditioner is registered. The device registration unit 110 confirms whether or not basic parts of the same type from the same manufacturer as the air conditioner are registered. Air conditioners of the same type from the same manufacturer have the same basic parts as the mold even if the serial numbers are different.

  If there is a basic part, in step S12, the device registration unit 110 newly generates a device object using the component. If there is no basic part, in step S13, the device registration unit 110 creates a new basic part and registers it in the database 160. For example, if a B-type air conditioner manufactured by A company is added, the device registration unit 110 newly creates a basic component common to the B-type air conditioner manufactured by A company. Then, the device registration unit 110 newly generates a device object using the created part.

  In step S <b> 14, the device registration unit 110 uses an algorithm that can identify the device 500 from a signal output from the device 500 when the device 500 is connected, and observes the above-described characteristics data 166 and the phenomenon that occurs when the device 500 is activated. The result is registered in the database 160 as a mechanism for collating the result. For example, if the B-type air conditioner manufactured by Company A has a characteristic that the output fluctuates for 100 ms in the range of −0.1 V to 4 V when the power is turned on, the device registration unit 110 determines the characteristic. Register the automatic recognition algorithm in an executable form such as a script. That is, the device registration unit 110 registers an algorithm that can check whether the device 500 has entered just by starting a script. In the present embodiment, such a script is registered in the database 160 together with information about the device 500.

  In step S <b> 15, the device registration unit 110 registers KPI, which is an index for evaluating the operation of the device 500. “KPI” is an abbreviation for Key Performance Indicator. KPIs are later used for analysis. For example, if KPI is Max (A), it indicates the maximum amount of current consumed by the device 500, and if Σ (P), it indicates the amount of power consumed by the device 500 so far. It is represented by Although not shown, the KPI may also be specified on the input screen 171.

  In step S <b> 16, the device registration unit 110 registers information such as the model, manufacturer, model number, delivery date, and price of the device 500 in the database 160. The model, manufacturer, and model number are registered in the database 160 as the classification information 162 described above. The delivery date and price are registered in the database 160 as part of the attribute information 164 described above. At this time, the device registration unit 110 can also register a command for operating the device 500. Information and commands to be registered are acquired from the input screen 171.

  In step S <b> 17, the device registration unit 110 issues the device ID 161 described above as an ID for uniquely identifying the device 500 in the entire database 160 and registers the device ID 161 in the database 160. The device ID 161 is a unique ID in the device management system 100. Therefore, the device 500 can be uniquely identified even if the arrangement of the device 500 is changed. The device registration unit 110 displays the issued device ID 161 on a completion screen 172 as shown in FIG. Similar to the input screen 171, the completion screen 172 is displayed on the display of the manufacturer apparatus 200 by an application such as a web browser operating on the manufacturer apparatus 200 based on data such as an HTTP message transmitted from the device management system 100. The

  At this time, the device 500 is only registered in the database 160 and is not connected to any room of the apartment. That is, only a new device object is added to the database 160, and the device object is not connected to the room object.

  The operation of the data exchange system 600 when the application developer registers the device configuration in the device management system 100 will be described with reference to FIG.

  Here, a flow for registering in the device management system 100 what kind of configuration the device 500 has will be described.

  In step S <b> 21, the device configuration definition unit 120 of the device management system 100 receives selection of a device object by an application developer who has accessed the device management system 100 from the developer device 300. Here, it is assumed that an air conditioner is selected.

  In step S <b> 22, the device configuration definition unit 120 accepts an operation for setting attributes of entities such as names and parameters in the device object. Such attributes include non-common values such as serial numbers and purchase amounts.

  In step S <b> 23, the device configuration definition unit 120 accepts an operation for confirming in the database 160 whether there is an already registered device configuration pattern, i.e., a template, before registering the device configuration. For example, in the case of “one residence of an apartment of A Type”, a device configuration template having a floor at the upper level and a Japanese-style room, a Western-style room, a bath, a toilet, and the like at the lower level can be considered.

  If there is a template, in step S24, the device configuration defining unit 120 automatically assigns the device 500 according to the template. In the previous example, an air conditioner is assigned to the Western-style room. If there is no template, in step S25, the device configuration definition unit 120 accepts an operation for inputting the device configuration one by one. In either case, the device object newly added to the database 160 is connected to the room object. That is, information indicating the apartment room in which the device 500 is installed is registered in the database 160 as the device configuration information 163 described above.

  In step S <b> 26, the device configuration definition unit 120 accepts an operation for registering a similar device configuration as a template while performing such input.

  With reference to FIG. 6, an operation in which the device management system 100 automatically recognizes the device 500 will be described.

  Here, a flow for recognizing what the device 500 is when the device 500 is installed will be described.

  In step S31, the device recognition unit 130 of the device management system 100 is an application developer who has accessed the device management system 100 from the developer device 300, or a person in charge of a system manufacturer who has accessed the device management system 100 from the manager device 400. The selection of the device 500 registered in the database 160 is accepted. And the apparatus recognition part 130 receives operation which produces the construction data which shows which apparatus 500 is installed where. The construction data includes a device ID 161 of a new device Xn, which is a newly installed device 500, and a device ID 161 of a control device Xc such as a router to which the new device Xn is connected. Although not shown in FIG. 1, the construction data is stored in the memory 102. At this time, the remaining attribute information 164 is registered in the database 160.

  In step S <b> 32, the device recognition unit 130 acquires construction data from the memory 102. The device recognition unit 130 uses the device ID 161 of the new device Xn included in the construction data to acquire an automatic recognition algorithm for the new device Xn provided by the device manufacturer and registered in the database 160. The device recognition unit 130 identifies the control device Xc using the device ID 161 of the control device Xc included in the construction data. The device recognition unit 130 transmits the acquired algorithm to the identified control device Xc. For example, if a certain air conditioner is installed in room 702, the device recognition unit 130 downloads an automatic recognition algorithm to a network device such as a router in room 702.

  After the new device Xn is installed, in step S33, the control device Xc executes the downloaded automatic recognition algorithm while monitoring the signal of the new device Xn.

  In step S34, if the characteristic of the new device Xn can be detected by an algorithm, the control device Xc notifies the device recognition unit 130 that the new device Xn has been detected. Accordingly, the device recognition unit 130 recognizes the classification of the new device Xn, and the recognized classification matches the classification indicated in the classification information 162 registered by the device registration unit 110 for the new device Xn. It can be judged.

  When two or more types of algorithms are downloaded to the control device Xc, the control device Xc notifies the device recognition unit 130 of which algorithm the characteristic corresponding to has been detected. As a result, the device recognition unit 130 can recognize the classification of the new device Xn. The device recognition unit 130 compares the recognized classification with the classification indicated in the classification information 162 registered by the device registration unit 110 for the new device Xn, thereby determining whether or not they match. Can do.

  The device recognition unit 130 may directly execute an automatic recognition algorithm instead of the control device Xc.

  As described above, in the present embodiment, the device recognition unit 130 obtains an observation result of a phenomenon that occurs when the new device Xn, which is a new device 500 to be managed, is started up directly or using the control device Xc. . Specifically, the device recognition unit 130 generates time series data of at least one of voltage and current output from the new device Xn when the power to the new device Xn is turned on as an observation result. Or the apparatus recognition part 130 produces | generates the time series data of at least any one of the sound and vibration which were generated from the new apparatus Xn at the time of starting of the new apparatus Xn as an observation result. Alternatively, the device recognition unit 130 records the time at which two or more parts included in the new device Xn are operated when the new device Xn is activated as an observation result. Alternatively, if the new device Xn is a refrigeration device, the device recognition unit 130 generates time-series data of temperatures adjusted by the new device Xn at the start of operation of the new device Xn as an observation result. Alternatively, if the new device Xn is a lighting device, the device recognition unit 130 generates time-series data of light output from the new device Xn at the start of lighting of the new device Xn as an observation result.

  Any method can be used as a method for generating time-series data. When generating time-series data of voltage and current, the voltage and current of the power line to which the new device Xn is electrically connected are respectively set to a voltage sensor and a current sensor for a certain period of time from when the new device Xn is turned on. Observe by When generating time-series data of sound and vibration, the sound and vibration around the new device Xn or the new device Xn may be observed by the sound sensor and the vibration sensor for a certain period of time from the start-up of the new device Xn, respectively. . When generating time-series data of temperature, the temperature of the new device Xn or the temperature around the new device Xn may be observed by a temperature sensor for a certain time from the start of operation of the new device Xn. When generating time-series data of light, light around the new device Xn may be observed by a photosensor for a certain time from the start of lighting of the new device Xn.

  Any method can be used as the time recording method. For example, if the new device Xn is a drainage system including a valve and a pump as parts, the time when the valve is opened and the time when the output of the pump downstream of the valve reaches the threshold after the operation of the new device Xn is started. Each may be observed by an open / close sensor and a pressure sensor or a flow sensor. Alternatively, if the new device Xn is an illumination system including a plurality of lighting devices as components, the time when each lighting device is turned on after the switch of the new device Xn is turned on may be observed by an optical sensor or the like. .

  The device recognition unit 130 obtains the characteristic data 166 from the recording medium, and collates the observation result obtained as described above with the characteristic data 166. Thereby, the device recognition unit 130 confirms whether or not the phenomenon defined by the characteristic data 166 has actually occurred. Specifically, the device recognizing unit 130 checks whether or not the variation characteristic indicated in the characteristic data 166 actually appears by comparing the generated time series data with the characteristic data 166. Alternatively, the device recognition unit 130 checks whether or not each component actually operates at the timing indicated by the characteristic data 166 by comparing the recorded time with the characteristic data 166.

  The device recognition unit 130 recognizes the classification of the new device Xn from the collation result. Then, the device recognition unit 130 determines whether the recognized classification matches the classification indicated in the classification information 162 registered by the device registration unit 110.

  As described above, in this embodiment, the bag as a product of the device 500 that is known to be installed by construction is registered in advance. “癖” is common among devices 500 having the same classification such as model, manufacturer, and type. Therefore, the device recognition unit 130 can recognize the classification of the device 500 by observing the eyelids of the newly installed device 500. Therefore, information necessary for recognizing the classification of the device 500 does not need to be explicitly provided from the device 500.

  The activation of the device 500 may be performed on site by a contractor or the like who installed the device 500, but may be performed by remote operation using a registered command. When the device 500 is activated by remote operation, a plurality of devices 500 can be activated at a time, and automatic recognition processing of the device 500 can be efficiently executed.

  If the classification recognized by the device recognition unit 130 matches the classification indicated in the classification information 162 registered by the device registration unit 110, the device recognition unit 130 displays the status of the construction data in step S35. As the connection is completed, the new device Xn is validated. For example, the device recognition unit 130 activates an initialization process registered with a command.

  The device recognition unit 130 determines that the recognized classification matches the classification indicated by the classification information 162 registered by the device registration unit 110 and the location where the observation result is obtained and the device configuration definition unit 120. The new device Xn may be validated only when the location indicated in the registered device configuration information 163 matches. The place where the observation result is obtained can be specified from the device configuration information 163 registered in the database 160 for the control device Xc.

  According to the present embodiment, construction data can be registered in advance, and it can be automatically confirmed whether or not the device 500 according to the construction data has been installed.

  With reference to FIG. 7, an operation in which the device management system 100 collects data related to the operation state of the device 500 will be described.

  Here, a flow in which the device management system 100 extracts the state of the activated device 500 will be described.

  In step S <b> 41, the operation result collection unit 140 of the device management system 100 collects operation data 167. Specifically, the operation result collection unit 140 collects operation data, alarm data, and operation data from the connected device 500 constantly or periodically. The collected data may be different for each device 500. As an example of the operation data 167, when the device 500 is an air conditioner, operation data indicating when the power is turned on or off, alarm data indicating whether an error has occurred, operation modes such as cooling, heating, and dehumidification The change, set temperature, and operation data indicating the operation date and time are recorded.

  In step S <b> 42, the operation result collection unit 140 processes the operation data 167. Specifically, the operation result collection unit 140 analyzes the operation data 167 or evaluates the operation data 167, and accumulates the analysis result and the evaluation result in the recording medium as the operation data 167 after processing. As a specific example, the operation result collection unit 140 aggregates operation data every day, takes an average on a monthly basis, calculates a KPI, and evaluates an operation state. The operation data 167 is stored in a format that can be searched by the device ID 161.

  In step S <b> 43, the operation result collection unit 140 transmits the operation data 167 to the outside in order to provide it to the device manufacturer that is the manufacturer that manufactured the corresponding device 500. Specifically, the operation result collection unit 140 transmits the operation data 167 via a network such as the Internet. The manufacturer apparatus 200 receives the operation data 167 from the operation result collection unit 140 via the network. As a specific example, the operation result collection unit 140 receives access from the manufacturer device 200 to the operation data 167 stored in a format that can be searched by the device ID 161 by the person in charge of the device manufacturer.

  After step S43, in step S14 described above, manufacturer apparatus 200 transmits characteristic data 166 to device management system 100 as data to be provided in exchange for providing operation data 167 via the network. The device management system 100 receives the characteristic data 166 from the manufacturer device 200 via the network. Specifically, the device management system 100 receives a script from the manufacturer device 200 that is created by a device manufacturer and in which an algorithm for the device recognition unit 130 to collate the observation result with the characteristic data 166 is received from the manufacturer device 200. To store. The device recognition unit 130 can recognize the classification of the new device Xn by executing a script stored in the database 160. The device management system 100 may receive a program in a format other than a script from the manufacturer apparatus 200 and store it in the database 160 as long as it is a program in which the same algorithm is implemented.

  As described above, in the present embodiment, the entity that operates and manages the device 500 provides the operation data 167 of the device 500 to the manufacturer that manufactured the device 500, so that the manufacturer manufactured the device 500. It is possible to have the device management system 100 register the property data 166 of the new device 500 as a reward. In addition, the entity operating and managing the device 500 may provide the manufacturer 500 who has registered the characteristic data 166 of the device 500 in the device management system 100 in return for the operation data 167 of the device 500. it can. With such a mechanism, it is possible to increase the motivation of providing information to each other in both the entity that operates and manages the device 500 and the manufacturer of the device 500.

  As a specific example, the above-mentioned algorithm created by the device manufacturer in exchange for ensuring that the entity that operates and manages the device 500 regularly provides operation data of the device 500 to the device manufacturer at the time of operation. You can receive a program that implements. The device management system 100 registers the provided program in the database 160 together with the classification of the device 500. The device recognition unit 130 can recognize the classification of the new device Xn by executing the registered program. According to the present embodiment, the classification of the device 500 can be recognized without creating an algorithm for classifying the device 500 for each device 500.

  With reference to FIG. 8, the operation of the data exchange system 600 when the system manufacturer searches for similar devices will be described.

  Here, a flow in which the device management system 100 searches for a device 500 similar to the device 500 selected on the selection screen 173 as shown in FIG. 9 will be described. For example, if a failed device 500 is selected, it is possible to know a device 500 that may fail in the same manner. The selection screen 173 is displayed on the display of the manager apparatus 400 by an application such as a web browser operating on the manager apparatus 400 based on data such as an HTTP message transmitted from the device management system 100.

  In step S <b> 51, the similar device search unit 150 of the device management system 100 accepts input of information on the selection screen 173 by the person in charge of the system manufacturer who has accessed the device management system 100 from the management company device 400. Specifically, the similar device search unit 150 receives an operation for designating the model of the device 500 and the type of ranking. The similar device search unit 150 searches the database 160 according to the specified content, and displays a device list 174 as shown in FIG. 10 on the selection screen 173. Then, the similar device search unit 150 receives an operation of selecting the device 500 that is a reference for the search from the device list 174.

  In step S52, the similar device search unit 150 receives input of the search condition 168 on the search screen 175 as shown in FIG. Specifically, the similar device search unit 150 receives an operation for specifying a search condition 168 regarding the manufacturer, model number, delivery date, and price of the device 500. The similar device search unit 150 satisfies the search condition 168 among the connected devices 500, and the evaluation count is calculated for the device 500 in which the attribute list and the attribute value are the same as the selected device 500. Increment. For example, when the delivery date of the selected device 500 is March 16, 2017, as shown in FIG. 10, among the other connected devices 500, the device whose delivery date is March 16, 2017. An evaluation count of 500 is incremented. Similar to the selection screen 173, the search screen 175 is displayed on the display of the management company apparatus 400 by an application such as a web browser operating on the management company apparatus 400 based on data such as an HTTP message transmitted from the device management system 100. The

  In step S <b> 53, the similar device search unit 150 satisfies the search condition 168 among the connected devices 500 and has an evaluation count for the device 500 whose basic type is the same as the selected device 500. Increment. For example, when the selected device 500 is an air conditioner, the manufacturer is A company, and the type is B type as shown in FIG. 10, among other connected devices 500, the manufacturer is A company and the type is B type. An air conditioner's evaluation count is incremented.

  In step S <b> 54, the similar device search unit 150 rearranges in order from the device 500 with the largest evaluation count value, and displays a list of similar devices on the search screen 175 as the search result 169.

  With such a mechanism, a list of devices 500 similar to the selected device 500 can be displayed. Note that the selection screen 173 and the search screen 175 may display information indicating the location where each device 500 is installed, such as an apartment name, a building number, and a room number. On the search screen 175, when any device 500 is selected from the search results 169, detailed information on the device 500 and registered commands may be displayed. In the search screen 175, when a range of a building is specified, the search result 169 may be updated according to the range. In this way, by providing an additional narrowing function, it is possible to efficiently search for the device 500 from a large number of similar devices 500.

  As described above, in the present embodiment, the similar device search unit 150 searches the database 160 when one of the devices 500 registered in the database 160 fails, A device 500 having a common attribute is extracted as a similar device. The similar device search unit 150 displays a list of similar devices.

  According to the present embodiment, when a failure occurs in a certain device 500, the device 500 having the same device configuration and attributes as the device 500 is extracted, and the extracted device 500 has a similar failure such as inspection. Measures that do not occur can be taken in advance.

*** Explanation of the effect of the embodiment ***
In the present embodiment, the classification of the device 500 is recognized from the characteristics when the device 500 is activated. Therefore, even if information necessary for recognizing the classification of the device 500 is not explicitly provided from the device 500, the classification of the device 500 can be recognized.

  In the present embodiment, operation data 167 indicating the operation results of the device 500 is provided from the device management system 100 to the manufacturer device 200, and in exchange, the device data is sent from the manufacturer device 200 to the device management system 100. Characteristic data 166 that can be used for automatic recognition of 500 is provided. Therefore, the motivation that each user of the device management system 100 and the manufacturer apparatus 200 provides information to each other can be enhanced.

  According to the present embodiment, an ID unique to the device 500 can be issued. Using this ID, the device 500 can be registered together with the device configuration such as equipment, facility, and department. Information on the device configuration can be stored in the database 160 as a directed graph according to the purpose of analysis. The device 500 can be searched by designating the shape of a part of a common graph regardless of the field. The output signal characteristics of the device 500 are stored, the value of the connection terminal of the device 500 is monitored, the connected device 500 is automatically recognized when a signal matching the stored signal characteristics is detected, and the device configuration is determined from the ID. And the fact that the device 500 is connected can be recorded.

  In the present embodiment, the device configuration can be managed separately from the device information by a graph database having a flexible structure. Therefore, the configuration information of the device 500 can be shared even if management purposes such as energy saving, exhaust gas, or organization are different. It is possible to centrally manage the devices 500 having various attributes or the devices 500 having various configurations. Further, the signal characteristics of the device 500 can be stored as device information, and the device 500 can be specified without using a special communication procedure or protocol. Furthermore, operation data of the device 500 can be collected, aggregated and analyzed according to the device configuration, and stored as operation data 167. By providing the operation data 167 to the device manufacturer that registered the device 500, it becomes easier to register the device information.

*** Other configurations ***
As described above, in the present embodiment, the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are realized by software. As a modification, the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 may be realized by a combination of software and hardware. That is, some of the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are realized by dedicated hardware, and the rest are realized by software. Also good.

  The dedicated hardware is, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an FPGA, or an ASIC. “IC” is an abbreviation for Integrated Circuit. “GA” is an abbreviation for Gate Array. “FPGA” is an abbreviation for Field-Programmable Gate Array. “ASIC” is an abbreviation for Application Specific Integrated Circuit.

  The processor 101 and dedicated hardware are both processing circuits. That is, the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are realized by software or a combination of software and hardware. Regardless of this, the functions of the device registration unit 110, the device configuration definition unit 120, the device recognition unit 130, the operation result collection unit 140, and the similar device search unit 150 are realized by a processing circuit.

Embodiment 2. FIG.
The difference between the present embodiment and the first embodiment will be mainly described with reference to FIG.

*** Explanation of configuration ***
The configuration of data exchange system 600 according to the present embodiment is the same as that of the first embodiment shown in FIG.

*** Explanation of operation ***
The operation of the data exchange system 600 according to the present embodiment will be described with reference to FIG. 13 in addition to FIG. The operation of the data exchange system 600 corresponds to the data exchange method according to the present embodiment.

  In the present embodiment, the similar device search unit 150 of the device management system 100 searches the database 160, groups the devices 500 whose information is registered in the database 160 by attribute, and includes the devices 500 included in each group. Displays a list of groups sorted by frequency of failure. That is, in the present embodiment, the similar device search unit 150 automatically creates a list of groups of similar devices, and further sorts the list in the order in which malfunctions may occur. Therefore, even if the device 500 is not selected, it is possible to automatically extract the device 500 that is likely to be defective, and take measures such that the extracted device 500 is not inspected, such as inspection.

  The operation of the data exchange system 600 when the device management system 100 searches for similar devices will be described with reference to FIG.

  In step S <b> 61, the similar device search unit 150 of the device management system 100 accepts designation of the attribute type by the person in charge of the system manufacturer who has accessed the device management system 100 from the management company apparatus 400. Here, it is assumed that the contractor who installed the device 500 is designated as the attribute type.

  In step S62, the similar device search unit 150 searches the database 160 and classifies the devices 500 having the same specified type of attribute into the same group. At this time, a setting may be made so that the group is divided according to the delivery date of the device 500. Here, it is assumed that the device 500 is installed by a contractor on the delivery date.

  In step S63, the similar device search unit 150 counts the number of failures of the device 500 for each group to be classified. For example, there are two air conditioners belonging to a group by the same contractor, the failure date indicated in the failure information 165 of one air conditioner is May 10, 2017, and the failure indicated in the failure information 165 of the other air conditioner. Suppose the days are May 20, 2017 and June 10, 2017. In this case, the number of failures of the group is 3.

  In step S <b> 64, the similar device search unit 150 displays a list of groups as a search result 169 by rearranging in order from the group with the highest number of failures.

*** Explanation of the effect of the embodiment ***
In the present embodiment, a separate relational database is not constructed for each type of device 500 such as an air conditioner and a lighting as in the past, but a graph database that can manage a wide variety of devices 500 with a unified device ID 161 is provided. Built. Therefore, for example, there are many problems with the air conditioner and lighting installed by one contractor, and the same type of air conditioner installed by another contractor and the same type of lighting have few problems. And it becomes possible to discover that it is not a defect as a lighting product, but a construction method by a contractor. Appropriate measures can then be taken.

  100 device management system, 101 processor, 102 memory, 103 auxiliary storage device, 104 input device, 105 display, 106 communication device, 110 device registration unit, 120 device configuration definition unit, 130 device recognition unit, 140 operation result collection unit, 150 Similar device search unit, 160 database, 161 device ID, 162 classification information, 163 device configuration information, 164 attribute information, 165 failure information, 166 characteristic data, 167 operation data, 168 search condition, 169 search result, 171 input screen, 172 Completion screen, 173 selection screen, 174 device list, 175 search screen, 200 manufacturer device, 300 developer device, 400 manager device, 500 device, 600 data exchange system.

Claims (18)

For each device classification, the characteristic data that predefines the phenomenon that occurs when each device is activated is acquired from the recording medium, and the observation result of the phenomenon that occurs when the new device that is the new management target device is activated is the characteristic data. And a device recognition unit that recognizes the classification of the new device from the verification result ,
An operation result collection unit that collects operation data indicating the operation result of the managed device and transmits the operation data to the manufacturer that manufactured the corresponding device is provided.
The device management system , wherein the characteristic data is data provided from the manufacturer in exchange for providing the operation data . For each device classification, the characteristic data that predefines the phenomenon that occurs when each device is activated is acquired from the recording medium, and the observation result of the phenomenon that occurs when the new device that is the new management target device is activated is the characteristic data. And a device recognition unit that recognizes the classification of the new device from the verification result ,
The characteristic data is stored in the recording medium as a program in which an algorithm for collating the observation result with the characteristic data is implemented,
The device recognition unit is a device management system that recognizes a classification of the new device by executing a program stored in the recording medium . A device registration unit for registering information indicating the classification of the new device in a database;
The device recognition unit, in the case where the classification is shown on the recognized classification and information registered by the device registration unit match, according to claim 1 or 2 to activate the new device equipment Management system. A device configuration defining unit that registers information indicating a location where the new device is installed in the database;
The device recognition unit is registered by the device configuration definition unit where the recognized classification matches the classification indicated in the information registered by the device registration unit, and the observation result is obtained. The device management system according to claim 3 , wherein the new device is validated when the location indicated in the information matches. In the database, for each device, information indicating the device attributes as well as the device classification is registered,
When any of the devices whose information is registered in the database fails, the database is searched, devices having the same attributes as the failed device are extracted as similar devices, and the list of similar devices is displayed. The device management system according to claim 3 , further comprising a similar device search unit. In the database, for each device, information indicating the device classification and the frequency of device failure and the frequency of device failure is registered,
A similar device search unit that searches the database, groups devices registered in the database according to attributes, and displays a list of groups sorted according to the frequency of failure of the devices included in each group The device management system according to claim 3 or 4 , further comprising: The device management system according to claim 5 or 6 , wherein information indicating a contractor who installed a device is registered in the database as a device attribute for each device. The device management system according to claim 3 , wherein the database is a graph database. The characteristic data is data indicating a fluctuation characteristic of at least one of a voltage and a current output from each device when the power to each device is turned on for each device classification,
The device recognition unit generates time series data of at least one of voltage and current output from the new device when the new device is powered on as the observation result, and the time series data is the characteristic data. device management system according to any one of claims 1 to 8 to match. The characteristic data is data indicating a variation characteristic of at least one of sound and vibration generated from each device when starting each device for each device classification,
The device recognition unit generates, as the observation result, time series data of at least one of sound and vibration generated from the new device when the new device is activated, and collates the time series data with the characteristic data. Item 9. The device management system according to any one of Items 1 to 8 . The characteristic data is data indicating the timing at which two or more parts included in each device operate when starting each device for each device classification,
The device recognition unit, as the observation result, claim 1, wherein the new device of the recorded two or more times with parts and operations involved in the new equipment at the time of startup, matching the time and the characteristic data 8 The device management system according to any one of the above. The characteristic data is data indicating temperature fluctuation characteristics adjusted by each refrigeration device at the start of operation of each refrigeration device for each refrigeration device classification,
If the new device is a refrigeration device, the device recognition unit generates time series data of the temperature adjusted by the new device at the start of operation of the new device as the observation result, and the time series data is The device management system according to any one of claims 1 to 8 , wherein the device management system collates with characteristic data. The characteristic data is data indicating fluctuation characteristics of light output from each lighting device at the start of lighting of each lighting device for each classification of the lighting device,
If the new device is a lighting device, the device recognition unit generates time series data of light output from the new device at the start of lighting of the new device as the observation result, and the time series data is The device management system according to any one of claims 1 to 8 , wherein the device management system collates with characteristic data. It further includes an operation result collection unit that collects operation data indicating an operation result of the managed device, and transmits the operation data to the outside in order to provide the operation data to the manufacturer that manufactured the corresponding device.
The device management system according to claim 2 , wherein the characteristic data is data provided from the manufacturer in exchange for providing the operation data. The characteristic data is stored in the recording medium as a program in which an algorithm for collating the observation result with the characteristic data is implemented,
The device management system according to claim 1 , wherein the device recognition unit recognizes a classification of the new device by executing a program stored in the recording medium. A manufacturer apparatus that receives the operation data from the device management system via a network and transmits the characteristic data to the device management system;
The data exchange system provided with the apparatus management system of Claim 14 or 15 which receives the said characteristic data from the said manufacturer apparatus via the said network. The device management system collects operation data indicating the operation results of the managed device, transmits the operation data via the network,
A manufacturer device receives the operation data from the device management system via the network,
As the data provided by the manufacturer device in exchange for the operation data being provided via the network, characteristic data defining a phenomenon that occurs at the start-up of each device for each device classification is the device management. Send to the system,
The device management system receives the characteristic data from the manufacturer device via the network,
A data exchange method in which the device management system collates an observation result of a phenomenon that occurs when a new device, which is a device to be newly managed, is activated with the characteristic data, and recognizes the classification of the new device from the collation result. On the computer,
For each device classification, the characteristic data that predefines the phenomenon that occurs when each device is activated is acquired from the recording medium, and the observation result of the phenomenon that occurs when the new device that is the new management target device is activated is the characteristic data. And a device management program that executes a process of recognizing the classification of the new device from the matching result ,
The characteristic data is stored in the recording medium as a program in which an algorithm for collating the observation result with the characteristic data is implemented,
A device management program for causing the computer to execute a process for recognizing the classification of the new device by causing the computer to execute a program stored in the recording medium.

Images