Patent Description:
As disclosed in PTL <NUM> (<CIT>), there is a technique in which a management apparatus collects operation data from facility equipment to manage the facility equipment.

<CIT> discloses a data-collecting apparatus for collecting, from at least one piece of facility equipment, operation data of the facility equipment, the data-collecting apparatus comprising: a communication unit for being connected to a network that connects a management apparatus that manages the facility equipment, and the facility equipment; and a data-collecting unit configured to collect, with the communication unit, the operation data from the facility equipment on a basis of a second collection condition, which is different from a first collection condition at a time when the management apparatus collects the operation data from the facility equipment.

Since in the PTL <NUM>, the management apparatus mainly collects data necessary for managing the facility equipment, the operation data collected by the management apparatus is part of the operation data of the facility equipment. Therefore, there is a problem that the useful operation data except the operation data collected by the management apparatus is not collected.

The scope of the invention is defined by the independent claim <NUM>. Embodiments which do not fall within the scope of the set of claims are to be interpreted as background information, useful only for understanding the invention.

An air-conditioning system <NUM> conditions air of a target space RM in a building. <FIG> is an overall configuration diagram of the air-conditioning system <NUM> according to the present embodiment. As shown in <FIG>, the air-conditioning system <NUM> mainly includes a data-collecting apparatus <NUM>, a management apparatus <NUM>, and facility equipment <NUM>.

The facility equipment <NUM> is an air conditioner, such as an air conditioner or heat source equipment. The air-conditioning system <NUM> includes one piece of facility equipment <NUM> or a plurality of pieces of facility equipment <NUM> of a plurality of types. In the present embodiment, the facility equipment <NUM> is three chiller units 30a to 30c. The management apparatus <NUM> is an apparatus that manages the facility equipment <NUM>. The air-conditioning system <NUM> includes one management apparatus <NUM> or a plurality of management apparatuses <NUM> of a plurality of types. In the present embodiment, the management apparatus <NUM> is an apparatus that manages the chiller units 30a to 30c. The data-collecting apparatus <NUM> is installed to relay communication between the management apparatus <NUM> and the facility equipment <NUM>, and is an apparatus that mainly collects surplus data <NUM>, which will be described later, from the facility equipment <NUM>. In the present embodiment, the data-collecting apparatus <NUM> is installed to relay communication between the management apparatus <NUM> and the chiller units 30a to 30c, and collects surplus data <NUM> from the chiller units 30a to 30c.

<FIG> is a diagram showing a communication network around the data-collecting apparatus <NUM> according to the present embodiment. As shown in <FIG>, the data-collecting apparatus <NUM>, the management apparatus <NUM>, and the chiller units 30a to 30c are communicably connected to each other through a network NW2b. Further, the management apparatus <NUM> is communicably connected to a data-utilizing apparatus <NUM> via a gateway GW through networks NW1 and NW2a. The network NW1 is, for example, the Internet. The networks NW2a and NW2b are, for example, Modbus, BACnet, Ethernet, and the like. The data-collecting apparatus <NUM> is communicably connected to the data-utilizing apparatus <NUM> by a communication line X and a communication line Y to be described later.

As shown in <FIG>, the air-conditioning system <NUM> also includes air-conditioning units <NUM>. <FIG> shows one of the plurality of air-conditioning units <NUM> as a representative. In the present embodiment, the air-conditioning unit <NUM> is assumed to be an air-handling unit. However, the air-conditioning unit <NUM> is not limited to an air-handling unit, and may be, for example, another air conditioner, such as a fan coil unit.

<FIG> is a diagram showing refrigerant circuits of the chiller units 30a to 30c according to the present embodiment. As shown in <FIG> and <FIG>, the chiller units 30a to 30c mainly include compressors 32a to 32c, radiators 34a to 34c, expansion valves 36a to 36c, evaporators 38a to 38c, primary pumps 41a to 41c, and control units 39a to 39c. The compressors 32a to 32c, the radiators 34a to 34c, the expansion valves 36a to 36c, and the evaporators 38a to 38c are connected to each other by first refrigerant circuits 31a to 31c. The first refrigerant circuits 31a to 31c are filled with a refrigerant, such as R32. The primary pumps 41a to 41c are installed in heat-source-side flow channels 40a to 40c. Water as a heat carrier flows through the heat-source-side circuits 48a to 48c.

The compressors 32a to 32c suck in low-pressure refrigerant, compress the refrigerant with a compression mechanism (not shown), and discharge the compressed refrigerant. The compressors 32a to 32c are, for example, rotary-type or scroll-type positive displacement compressors. The compression mechanisms of the compressors 32a to 32c are driven by compressor motors (not shown). The compressor motor is a motor whose number of revolutions can be controlled by an inverter. The numbers of revolutions of the compressor motors are controlled to control the capacities of the compressors 32a to 32c.

The radiators 34a to 34c include first heat transfer tubes connected to the first refrigerant circuits 31a to 31c, and second heat transfer tubes connected to water circuits 60a to 60c. The radiators 34a to 34c perform heat exchange between the refrigerant flowing through the first heat transfer tubes on the first-refrigerant-circuits-31a-to-31c side, and water flowing through the second heat transfer tubes on the water-circuits-60a-to-60c side. The radiators 34a to 34c are, for example, a fin-and-tube-type heat exchanger including the plurality of heat transfer tubes and fins.

The expansion valves 36a to 36c are mechanisms for adjusting pressures and flow rates of the refrigerant flowing through the first refrigerant circuits 31a to 31c. In the present embodiment, the expansion valves 36a to 36c are electronic expansion valves.

The evaporators 38a to 38c include first heat transfer tubes connected to the first refrigerant circuits 31a to 31c, and second heat transfer tubes connected to the heat-source-side flow channels 40a to 40c. The evaporators 38a to 38c perform heat exchange between the refrigerant flowing through the first heat transfer tubes on the first-refrigerant-circuits-31a-to-31c side, and the heat carrier flowing through the second heat transfer tubes on the heat-source-side-flow-channels-40a-to-40c side, respectively. The evaporators 38a to 38c are, for example, a fin-and-tube-type heat exchanger including the plurality of heat transfer tubes and fins.

The primary pumps 41a to 41c feed out the water of the heat-source-side flow channels 40a to 40c from the upstream side to the downstream side. Since the primary pumps 41a to 41c are inverter-driven pumps, the capacities can be regulated, and the leaving-water pressures (or discharge flow rates) can be adjusted.

The control units 39a to 39c receive control signals from the management apparatus <NUM>, and control the operations of the chiller units 30a to 30c. The control units 39a to 39c include a control arithmetic device and a storage device. As the control arithmetic device, a processor, such as a central processing unit (CPU) or a graphics processing unit (GPU), can be used. The control arithmetic device reads programs stored in the storage device, and performs predetermined arithmetic processing according to the programs. In addition, according to the programs, the control arithmetic device can write an arithmetic result into the storage device, and can read information stored in the storage device. The control units 39a to 39c also include timers.

The control units 39a to 39c are electrically connected to each equipment in the chiller units 30a to 30c, such as the compressors 32a to 32c, and are electrically connected to each sensor (not shown), such as a temperature sensor, to exchange control signals and information. The control units 39a to 39c store, in the storage devices for a certain period, various kinds of data acquired from each equipment in the chiller units 30a to 30c and each sensor. In the present embodiment, the various kinds of data will be referred to as operation data <NUM>.

As shown in <FIG>, the control units 39a to 39c are communicably connected to the management apparatus <NUM> via the data-collecting apparatus <NUM> through the network NW2b. The control units 39a to 39c receive control signals from the management apparatus <NUM> through the network NW2b. The control units 39a to 39c also transmit, to the management apparatus <NUM>, part of the operation data <NUM> necessary for the control of the chiller units 30a to 30c by the management apparatus <NUM>. In the present embodiment, the part of the operation data <NUM> is referred to as control data <NUM>. Further, in the present embodiment, the operation data <NUM> except the control data <NUM> is referred to as surplus data <NUM>. In other words, the operation data <NUM> includes the control data <NUM> and the surplus data <NUM>.

The water circuits 60a to 60c are filled with water as a heat carrier. As shown in <FIG>, the water circuits 60a to 60c are connected to the radiators 34a to 34c, water pumps 62a to 62c, and cooling towers CTa to CTc. The water pumps 62a to 62c can adjust discharge flow rates, and circulate the water of the water circuits 60a to 60c. The cooling towers CTa to CTc cool the water circulating through the water circuits 60a to 60c. In <FIG>, the arrows attached to the water pumps 62a to 62c indicate the direction in which the water flows.

Water as a heat carrier flows through the heat-source-side circuits 48a to 48c. As shown in <FIG>, the heat-source-side circuits 48a to 48c include the heat-source-side flow channels 40a to 40c, the primary pumps 41a to 41c provided in the middle of the heat-source-side flow channels 40a to 40c, and heat-transfer-tube portions of the evaporators 38a to 38c connected to the heat-source-side flow channels 40a to 40c. The evaporators 38a to 38c cool the water as a heat carrier circulating through the heat-source-side flow channels 40a to 40c. In <FIG>, the arrows attached to the primary pumps 41a to 41c indicate the direction in which the water flows.

As shown in <FIG>, water that has passed through a usage-side circuit <NUM> described below is fed to the heat-source-side circuits 48a to 48c via a return header portion <NUM>. The upstream sides of the heat-source-side circuits 48a to 48c are connected to the downstream side of the return header portion <NUM>. The downstream side of a usage-downstream-side merging-tube <NUM>, which will be described later, is connected to the upstream side of the return header portion <NUM>.

The return header portion <NUM> is provided with a flow rate sensor (not shown) for measuring the flow rate of water passing therethrough.

As shown in <FIG>, the water that has passed through the heat-source-side circuits 48a to 48c is fed to the usage-side circuit <NUM> via a leaving-header portion <NUM>. The downstream sides of the heat-source-side circuits 48a to 48c are connected to the upstream side of the leaving-header portion <NUM>. The upstream side of a usage-upstream-side merging-tube <NUM>, which will be described later, is connected to the downstream side of the leaving-header portion <NUM>.

The leaving-header portion <NUM> is provided with a secondary pump (not shown), and can feed water from the heat-source-side circuits 48a to 48c toward the usage-side circuit <NUM>. The secondary pump is an inverter-driven pump, and the capacity can be regulated to adjust the discharge flow rate.

As shown in <FIG>, a bypass circuit <NUM> extends from the leaving-header portion <NUM> to the return header portion <NUM>, and does not merge with the heat-source-side circuits 48a to 48c and the usage-side circuit <NUM>.

The bypass circuit <NUM> is provided to return water excessively fed to the leaving-header portion <NUM>, to the return header portion <NUM>.

As shown in <FIG>, the usage-upstream-side merging-tube <NUM> extending from the leaving-header portion <NUM> toward the downstream side branches, at a branching point P1, into the usage-side circuit <NUM> and a tube connected to another usage-side circuit (not shown). Further, the usage-side circuit <NUM> and the tube connected to another usage-side circuit (not shown) merge at a merging point P2. The usage-downstream-side merging-tube <NUM> extends from the merging point P2, and a downstream-side end portion of the usage-downstream-side merging-tube <NUM> is connected to the return header portion <NUM>.

Water as a heat carrier flows through the usage-side circuit <NUM>. The usage-side circuit <NUM> includes a usage-side flow channel <NUM>, a flow-rate-adjusting valve <NUM> provided in the middle of the usage-side flow channel <NUM>, and an air-cooling heat exchanger <NUM> connected to the usage-side flow channel <NUM>. The flow-rate-adjusting valve <NUM> controls the valve opening degree to adjust the flow rate of the water flowing through the usage-side flow channel <NUM>.

As shown in <FIG>, the air-conditioning unit <NUM> includes a casing <NUM> having a substantially rectangular-parallelepiped shape. An air passage through which air circulates is formed inside the casing <NUM>. One end of a ventilation duct RA is connected to an inflow end of the air passage of the casing <NUM>. The other end of the ventilation duct RA is connected to the target space RM. One end of an outdoor-air duct OA is also connected to the inflow end of the air passage. The other end of the outdoor-air duct OA is connected to the outdoor. One end of an air supply duct SA is connected to an outflow end of the air passage. The other end of the air supply duct SA is connected to the target space RM. Air in the target space RM and outdoor air are taken into the casing <NUM> through the ventilation duct RA and the outdoor-air duct OA, respectively. The temperature and humidity of the taken-into air are regulated in the casing <NUM>. The air whose temperature and humidity have been regulated is fed to the target space RM through the air supply duct SA. In this way, the air in the target space RM is conditioned.

In the air passage in the casing <NUM>, the air-cooling heat exchanger <NUM>, an electric heater <NUM>, a water spray humidifier <NUM>, and a fan <NUM> are installed in this order from the upstream side to the downstream side. The air-cooling heat exchanger <NUM> is equipment that cools air to lower the temperature of the air, or dehumidifies air to lower the humidity. The air-cooling heat exchanger <NUM> is a fin-and-tube-type heat exchanger including a plurality of heat transfer fins, and a heat transfer tube penetrating the heat transfer fins. The electric heater <NUM> heats the air that has passed through the air-cooling heat exchanger <NUM>. The electric heater <NUM> can adjust the heating amount of the air. The water spray humidifier <NUM> humidifies air flowing in the casing <NUM> by spraying, into the air from a nozzle, water in a tank (not shown) installed outside the casing <NUM>. The water spray humidifier <NUM> can adjust the humidification amount of the air. The fan <NUM> generates a flow of the air to be blown into the target space RM through the air-cooling heat exchanger <NUM>, the electric heater <NUM>, and the water spray humidifier <NUM>. The fan <NUM> can change the number of revolutions in a stepwise manner by inverter control to adjust the blowing amount.

The management apparatus <NUM> manages the chiller units 30a to 30c (facility equipment <NUM>). The management referred to here includes control. The management apparatus <NUM> includes a control arithmetic device and a storage device. As the control arithmetic device, a processor, such as a CPU or a GPU, can be used. The control arithmetic device reads programs stored in the storage device, and performs predetermined arithmetic processing according to the programs. In addition, according to the programs, the control arithmetic device can write an arithmetic result into the storage device, and can read information stored in the storage device. The management apparatus <NUM> also includes a timer.

The management apparatus <NUM> is configured to be capable of receiving various signals transmitted from a remote controller (not shown) for operating the chiller units 30a to 30c. The various signals transmitted from the remote controller include signals instructing operation and stop of the chiller units 30a to 30c, and signals related to various settings. The signals related to various settings include, for example, a switching signal of the operation mode, and a signal related to a set temperature and set humidity.

As shown in <FIG>, the management apparatus <NUM> is communicably connected to the chiller units 30a to 30c via the data-collecting apparatus <NUM> through the network NW2b. The management apparatus <NUM> receives control data <NUM> from the control units 39a to 39c of the chiller units 30a to 30c. On the basis of the control data <NUM> received from the chiller units 30a to 30c, or various signals transmitted from the remote controller, the management apparatus <NUM> transmits control signals to the chiller units 30a to 30c.

Further, the management apparatus <NUM> is communicably connected to the data-utilizing apparatus <NUM> via the gateway GW through the networks NW1 and NW2a. The management apparatus <NUM> transmits, to the data-utilizing apparatus <NUM>, the control data <NUM> received from the chiller units 30a to 30c.

The data-collecting apparatus <NUM> collects, from the at least one chiller units 30a to 30c (facility equipment <NUM>), surplus data <NUM> (operation data <NUM>) of the chiller units 30a to 30c (facility equipment <NUM>). <FIG> are functional block diagrams of the data-collecting apparatus <NUM> according to the present embodiment. <FIG> are connected by circled numbers. In <FIG>, the three chiller units 30a to 30c are collectively shown. As shown in <FIG>, the data-collecting apparatus <NUM> mainly includes a communication unit <NUM> and a data-collecting unit <NUM>.

The data-collecting apparatus <NUM> includes a control arithmetic device and a storage device. As the control arithmetic device, a processor, such as a CPU or a GPU, can be used. The control arithmetic device reads programs stored in the storage device, and performs predetermined image processing and arithmetic processing according to the programs. In addition, according to the programs, the control arithmetic device can write an arithmetic result into the storage device, and can read information stored in the storage device. The data-collecting apparatus <NUM> also includes a timer. The communication unit <NUM>, the data-collecting unit <NUM>, an input unit <NUM> to be described later, an analyzing unit <NUM> to be described later, and a transmission-schedule-determining unit <NUM> to be described later are various functional blocks implemented by the control arithmetic device and the storage device.

The communication unit <NUM> connects the data-collecting apparatus <NUM> to the network NW2b that connects the management apparatus <NUM> and the chiller units 30a to 30c (facility equipment <NUM>). As shown in <FIG>, the communication unit <NUM> includes a first communication unit 11a that communicates with the management apparatus <NUM>, and a second communication unit 11b that communicates with the chiller units 30a to 30c (facility equipment <NUM>). The first communication unit 11a and the second communication unit 11b cooperate with each other to relay communication between the management apparatus <NUM> and the chiller units 30a to 30c (facility equipment <NUM>).

Hereinafter, the relay processing will be specifically described. As indicated by dashed-dotted-line arrows in <FIG>, when the first communication unit 11a receives a first request packet D1 from the management apparatus <NUM>, the first communication unit 11a passes the first request packet D1 to the second communication unit 11b. The first request packet D1 is a packet with which the management apparatus <NUM> requests control data <NUM> from the chiller units 30a to 30c. The details will be described later. Here, it is assumed that the transmission destination of the first request packet D1 is the chiller unit 30a. When the second communication unit 11b receives the first request packet D1 from the first communication unit 11a, the second communication unit 11b transmits the first request packet D1 to the chiller unit 30a.

When the second communication unit 11b receives, from the chiller unit 30a, control data <NUM> requested with the first request packet D1, the second communication unit 11b passes the control data <NUM> to the first communication unit 11a. When the first communication unit 11a receives the control data <NUM> from the second communication unit 11b, the first communication unit 11a transmits the control data <NUM> to the management apparatus <NUM>.

In this way, the first communication unit 11a and the second communication unit 11b cooperate with each other to relay communication between the management apparatus <NUM> and the chiller units 30a to 30c.

As shown in <FIG>, the data-collecting unit <NUM> collects, with the second communication unit 11b (communication unit <NUM>), surplus data <NUM> (operation data <NUM>) from the chiller units 30a to 30c (facility equipment <NUM>) on the basis of a second collection condition C2, which is different from a first collection condition at a time when the management apparatus <NUM> collects control data <NUM> (operation data <NUM>) from the chiller units 30a to 30c (facility equipment <NUM>). In the present embodiment, the first collection condition is a condition under which the management apparatus <NUM> collects part or all of control data <NUM> from the chiller units 30a to 30c. In other words, the first collection condition is a condition under which part or all of control data <NUM> is extracted. Further, the second collection condition C2 is a condition under which the data-collecting unit <NUM> collects part or all of surplus data <NUM> from the chiller units 30a to 30c. In other words, the second collection condition C2 is a condition under which part or all of surplus data <NUM> is extracted.

The data-collecting unit <NUM> transmits second request packets D2, which will be described later, to the chiller units 30a to 30c to collect surplus data <NUM> that satisfies the second collection condition C2. As shown in <FIG>, the data-collecting unit <NUM> transmits the second request packets D2 according to a transmission schedule SS to be described later. Further, the data-collecting unit <NUM> acquires the second collection condition C2 from the input unit <NUM>.

As shown in <FIG>, the data-collecting unit <NUM> transmits the surplus data <NUM> (operation data <NUM>) collected on the basis of the second collection condition C2, to the data-utilizing apparatus <NUM>, which is an apparatus that is different from the management apparatus <NUM> and utilizes operation data <NUM>. The data-collecting unit <NUM> sequentially or periodically transmits surplus data <NUM> that satisfies the second collection condition C2, to the data-utilizing apparatus <NUM>. For example, as shown in <FIG>, the data-collecting unit <NUM> transmits surplus data <NUM> to the data-utilizing apparatus <NUM> through the communication line X and the network NW1. The communication line X is a communication line for connecting the data-collecting apparatus <NUM> to the network NW1. Alternatively, for example, as shown in <FIG>, the data-collecting unit <NUM> transmits surplus data <NUM> to the data-utilizing apparatus <NUM> through the communication line Y and the networks NW1 and NW2a. The communication line Y is a communication line for connecting the data-collecting apparatus <NUM> to the network NW2a.

The input unit <NUM> inputs the second collection condition C2. As shown in <FIG>, the input unit <NUM> receives at least input from the data-utilizing apparatus <NUM>. For example, the input unit <NUM> may directly receive input from the user.

As shown in <FIG>, the analyzing unit <NUM> analyzes the regularity of first request packets D1. The first request packet D1 is a communication packet that is for requesting control data <NUM> (operation data <NUM>) and is transmitted to the chiller units 30a to 30c (facility equipment <NUM>) when the management apparatus <NUM> collects the control data <NUM> (operation data <NUM>) on the basis of the first collection condition.

On the basis of the first request packet information included in first request packets D1, the analyzing unit <NUM> determines, from the first request packets D1, a periodically-transmitted packet PP. The first request packet information includes information on the chiller units 30a to 30c (facility equipment <NUM>), which are the transmission destinations of the first request packet D1, and the request content of the first request packet D1. The periodically-transmitted packet PP is a first request packet D1 periodically transmitted.

Hereinafter, a method for determining, from first request packets D1, a periodically-transmitted packet PP will be described.

As shown in <FIG>, the analyzing unit <NUM> creates a first table TBL1 in which first request packet information, and the receipt times of the first request packets D1 are accumulated. Every time the first communication unit 11a receives a first request packet D1, the analyzing unit <NUM> acquires, from the first communication unit 11a, the first request packet information and receipt time of the first request packet D1, and updates the first table TBL1.

The analyzing unit <NUM> periodically scans the first table TBL1 (hereinafter, the scanning may be referred to as the periodic scanning) to check the state of the first table TBL1. In the present embodiment, the periodic scanning is performed once per minute. The timing of the periodic scanning can be appropriately changed, and may be, for example, once every <NUM> seconds. Further, the analyzing unit <NUM> periodically deletes all records of the first table TBL1 to reset the first table TBL1 (hereinafter, the reset may be referred to as the periodic reset). In the present embodiment, the periodic reset is performed once per hour. The timing of the periodic reset can be appropriately changed, and may be, for example, once every <NUM> minutes.

Further, the analyzing unit <NUM> starts to determine a periodically-transmitted packet PP at a predetermined timing. In the present embodiment, after a periodic reset is performed, at the timing of third periodic scanning, the analyzing unit <NUM> starts to determine a periodically-transmitted packet PP. In other words, the analyzing unit <NUM> redetermines a periodically-transmitted packet PP every time a periodic reset is performed. The purpose is for dealing with a change in the regularity of periodically-transmitted packets PP in the middle. Here, the predetermined timing at which a periodically-transmitted packet PP is determined can be appropriately changed.

Table <NUM> below is an example of the first table TBL1 at a time when first periodic scanning has been performed after a periodic reset is performed.

The first table TBL1 in which the "facility equipment" and the "request content" are primary keys is created. Here, the "facility equipment" is information for identifying the chiller units 30a to 30c, which are the transmission destinations of the first request packet D1. In Table <NUM>, "30a" indicates the chiller unit 30a, and "30b" indicates the chiller unit 30b. The "request content" is information indicating the request content of the first request packet D1. Shown in Table <NUM> are the request contents encoded with hexadecimal numbers, such as "0x01". The "receipt time" is a time at which the first communication unit 11a receives the first request packet D1. In a case where first request packets D1 whose "facility equipment" and "request content" are the same have been received, the analyzing unit <NUM> updates the "receipt time" of the corresponding record to the most recent time. Every time the "receipt time" is updated, the "receipt time" before the update is stored in the "receipt time (before update)". Since in Table <NUM>, first request packets D1 whose "facility equipment" and "request content" are the same have not yet been received, "-" is stored in the "receipt time (before update)". The "counter" is the number of times of receipt of first request packets D1 whose "facility equipment" and "request content" are the same. In other words, among first request packets D1 transmitted within a predetermined period, the analyzing unit <NUM> totals the number of the first request packets D1 whose "facility equipment" and "request content" (part of the first request packet information) are the same. The "record ID" is an identification number assigned to each record in which the "facility equipment" and the "request content" are the same. The "record ID" is provided to facilitate the following description.

Table <NUM> below is an example of the first table TBL1 at a time when second periodic scanning has been performed.

In Table <NUM>, as compared with Table <NUM>, the "receipt time" and the "counter" of the records of the "record ID" = <NUM>, <NUM>, <NUM>, and <NUM> are updated. The reason is that after the state of Table <NUM>, first request packets D1 corresponding to the "record ID" = <NUM>, <NUM>, <NUM>, and <NUM> (first request packets D1 whose "facility equipment" and "request content" are the same) have been received. A record whose "record ID" = <NUM> is a record newly added to the first table TBL1. It is seen that the first request packet D1 corresponding to the "record ID" = <NUM> has been received after the first request packet D1 corresponding to the "record ID" = <NUM> has been received and before the first request packet D1 corresponding to the "record ID" = <NUM> has been received.

Table <NUM> below is an example of the first table TBL1 at a time when third periodic scanning has been performed. In the present embodiment, at this timing, the determination of a periodically-transmitted packet PP is started.

In Table <NUM>, as compared with Table <NUM>, the records of the "record ID" = <NUM>, <NUM>, and <NUM> are updated. Further, a record of the "record ID" = <NUM> is newly added.

The analyzing unit <NUM> determines that a first request packet D1 having at least the largest value of the "counter" (totaled value) is a periodically-transmitted packet PP. Therefore, the analyzing unit <NUM> determines that the records of the "record ID" = <NUM>, <NUM>, and <NUM> having the largest value of the "counter" are periodically-transmitted packets PP. Further, the analyzing unit <NUM> stores the largest value of the "counter", and stores records that have not been determined as the periodically-transmitted packets PP (that hereinafter may be referred to as pending records). In this case, the largest value to be stored is three. Further, the pending records to be stored are records whose "record ID" = <NUM>, <NUM>, and <NUM>.

Table <NUM> below is an example of the first table TBL1 at a time when fourth periodic scanning has been performed.

In Table <NUM>, as compared with Table <NUM>, the record of the "record ID" = <NUM> is updated.

The analyzing unit <NUM> subtracts the most recent values of the "counter" of the stored pending records (not in Table <NUM> but in Table <NUM>), from the largest value that has been also stored. The analyzing unit <NUM> further determines that the pending record whose subtraction result is smaller than a predetermined value is a periodically-transmitted packet PP. In the present embodiment, the predetermined value is two. The predetermined value can be appropriately changed.

In Table <NUM>, the record whose "record ID" = <NUM> has the subtraction result of <NUM> (= <NUM> - <NUM>), which is smaller than the predetermined value (= <NUM>). Therefore, the analyzing unit <NUM> further determines that the record whose "record ID" = <NUM> is a periodically-transmitted packet PP. The records whose "record ID" = <NUM> and <NUM> have the subtraction result of <NUM> (= <NUM> - <NUM>), which is not smaller than the predetermined value (= <NUM>). Therefore, the analyzing unit <NUM> does not determine that the records whose "record ID" = <NUM> and <NUM> are periodically-transmitted packets PP.

As described above, the analyzing unit <NUM> determines that the records whose "record ID" = <NUM>, <NUM>, <NUM>, and <NUM> are periodically-transmitted packets PP.

Note that the analyzing unit <NUM> may not use the predetermined value, and may determine that a stored pending record whose most recent value of the "counter" (not in Table <NUM> but in Table <NUM>) becomes equal to or larger than the largest value that has been also stored is a periodically-transmitted packet PP.

The transmission-schedule-determining unit <NUM> determines a transmission schedule SS of second request packets D2. The second request packets D2 are communication packets that are for requesting surplus data <NUM> (operation data <NUM>) and are transmitted to the chiller units 30a to 30c (facility equipment <NUM>) when the data-collecting unit <NUM> collects the surplus data <NUM> (operation data <NUM>) on the basis of the second collection condition C2. The second request packets D2 exist for the chiller units 30a to 30c, respectively.

The transmission-schedule-determining unit <NUM> determines a transmission schedule SS to transmit second request packets D2 in such a manner that the timings at which first request packets D1 are transmitted are avoided. In the present embodiment, as shown in <FIG>, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS to transmit second request packets D2 in such a manner that the timings at which periodically-transmitted packets PP are transmitted are avoided.

In the present embodiment, the transmission-schedule-determining unit <NUM> shares, with the analyzing unit <NUM>, the results of the periodic scanning. When the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of the periodically-transmitted packets PP received by the first communication unit 11a (communication unit <NUM>), a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2. Specifically, when the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> monitors a timing at which the records of the periodically-transmitted packets PP are further updated from the state of the first table TBL1 of Table <NUM>. Here, it is assumed that the records of the periodically-transmitted packets PP are updated in fifth periodic scanning. Table <NUM> below is an example of the first table TBL1 at a time when the fifth periodic scanning has been performed.

In Table <NUM>, as compared with Table <NUM>, the record of the "record ID" = <NUM> is updated. It is seen from Table <NUM> that an interval time period during which the periodically-transmitted packets PP are not transmitted (time period from the "receipt time" of the record whose "record ID" = <NUM> to the "receipt time" of the record whose "record ID" = <NUM>) is one minute. Further, it is seen from Table <NUM> that a receipt time period of consecutive ones of the periodically-transmitted packets PP (time period from the "receipt time (before update)" of the record whose "record ID" = <NUM> to the "receipt time" of the record whose "record ID" = <NUM>) is one minute and five seconds.

A time period during which second request packets D2 are going to be transmitted is set to, for example, one minute from the receipt of the first request packet D1 whose "record ID" = <NUM> (interval time period). For example, it is assumed that <NUM> seconds (= one minute and five seconds (receipt time period)/four packets (the number of periodically-transmitted packets PP)) are necessary for each second request packet D2. Therefore, the number of the second request packets D2 to be transmitted is set to three (= an integer part obtained by dividing one minute (interval time period) by <NUM> seconds (time period necessary for one of the second request packets D2)). Since in the present embodiment, there are the three chiller units 30a to 30c, for example, one second request packet D2 is transmitted to each chiller unit during the interval time period.

As described above, the transmission-schedule-determining unit <NUM> determines the transmission schedule SS such that a total of the three second request packets D2 are going to be transmitted to the chiller units 30a to 30c within one minute of the receipt of the first request packet D1 corresponding to the "record ID" = <NUM>.

As shown in <FIG>, according to the transmission schedule SS, the data-collecting unit <NUM> transmits second request packets D2 to the chiller units 30a to 30c. The data-collecting unit <NUM> acquires, from the first communication unit 11a or the analyzing unit <NUM>, the timing of the receipt of the first request packet D1 corresponding to the "record ID" = <NUM>.

The data-utilizing apparatus <NUM> is an apparatus that utilizes operation data <NUM>. As shown in <FIG>, the data-utilizing apparatus <NUM> is communicably connected to the data-collecting apparatus <NUM> and the management apparatus <NUM> through the networks NW1 and NW2a. As shown in <FIG>, the data-utilizing apparatus <NUM> mainly includes a collection-condition-setting unit <NUM> and an analyzing unit <NUM>.

The data-utilizing apparatus <NUM> includes a control arithmetic device and a storage device. As the control arithmetic device, a processor, such as a CPU or a GPU, can be used. The control arithmetic device reads programs stored in the storage device, and performs predetermined image processing and arithmetic processing according to the programs. In addition, according to the programs, the control arithmetic device can write an arithmetic result into the storage device, and can read information stored in the storage device. The data-utilizing apparatus <NUM> also includes a timer. The collection-condition-setting unit <NUM> and the analyzing unit <NUM> are various functional blocks implemented by the control arithmetic device and the storage device.

As shown in <FIG>, the collection-condition-setting unit <NUM> receives the setting of the second collection condition C2, and transmits the set second collection condition C2 to the input unit <NUM>. The second collection condition C2 is set by, for example, input by the user or reading of a file.

As shown in <FIG>, the analyzing unit <NUM> receives control data <NUM> from the management apparatus <NUM>. The analyzing unit <NUM> also receives surplus data <NUM> from the data-collecting unit <NUM>.

The analyzing unit <NUM> analyzes the received control data <NUM> and surplus data <NUM>, and utilizes the received control data <NUM> and surplus data <NUM> for remote monitoring, failure diagnosis, and the like of the chiller units 30a to 30c. For the analysis, for example, a statistical technique, machine learning, or the like are used.

An example of data collection processing performed by the data-collecting apparatus <NUM> will be described with reference to the flowchart of <FIG>. Note that in <FIG>, the data collection processing is indicated by solid-line arrows.

As shown in step S1, the data-collecting apparatus <NUM> performs a periodic reset of the first table TBL1.

After step S1 is ended, as shown in step S2, every time the data-collecting apparatus <NUM> receives a first request packet D1 from the management apparatus <NUM>, the data-collecting apparatus <NUM> acquires the first request packet information of the first request packet D1 and updates the first table TBL1.

After step S2 is ended, as shown in step S3, the data-collecting apparatus <NUM> ascertains whether or not a timing for determining periodically-transmitted packets PP has come. In a case where a timing for determining periodically-transmitted packets PP has come, the data-collecting apparatus <NUM> proceeds to step S4. In a case where a timing for determining periodically-transmitted packets PP has not come, the data-collecting apparatus <NUM> returns to step S2 to continue to update the first table TBL1.

When the data-collecting apparatus <NUM> proceeds from step S3 to step S4, as shown in step S4, the data-collecting apparatus <NUM> determines, from first request packets D1 of the first table TBL1, periodically-transmitted packets PP.

When step S4 is ended, as shown in step S5, the data-collecting apparatus <NUM> determines a transmission schedule SS of second request packets D2 on the basis of the receipt times of the periodically-transmitted packets PP.

After step S5 is ended, as shown in step S6, the data-collecting apparatus <NUM> acquires a second collection condition C2 set by the data-utilizing apparatus <NUM>.

When step S6 is ended, as shown in step S7, according to the transmission schedule SS, the data-collecting apparatus <NUM> transmits, to the chiller units 30a to 30c, second request packets D2 for requesting surplus data <NUM> that satisfies the second collection condition C2.

After step S7 is ended, as shown in step S8, the data-collecting apparatus <NUM> receives, from the chiller units 30a to 30c, surplus data <NUM> that has been requested with the second request packets D2 and satisfies the second collection condition C2.

After step S8 is ended, as shown in step S9, the data-collecting apparatus <NUM> transmits, to the data-utilizing apparatus <NUM>, the surplus data <NUM> received from the chiller units 30a to 30c.

When step S9 is ended, as shown in step S10, the data-collecting apparatus <NUM> ascertains whether or not a timing for performing a periodic reset of the first table TBL1 has come. In a case where a timing for performing a periodic reset of the first table TBL1 has come, the data-collecting apparatus <NUM> returns to step S1 to perform the periodic reset of the first table TBL1. In a case where a timing for performing a periodic reset of the first table TBL1 has not come, the data-collecting apparatus <NUM> proceeds to step S11.

When the data-collecting apparatus <NUM> proceeds from step S10 to step S11, as shown in step S11, the data-collecting apparatus <NUM> ascertains whether or not the second collection condition C2 has been changed. In a case where the second collection condition C2 has been changed, the data-collecting apparatus <NUM> proceeds to step S11 to acquire the changed second collection condition C2. In a case where the second collection condition C2 has not been changed, the data-collecting apparatus <NUM> proceeds to step S7 to continue to transmit second request packets D2.

The data collection processing is executed until all the chiller units 30a to 30c are stopped.

(<NUM>-<NUM>) There has been a technique in which a management apparatus collects operation data from facility equipment to manage the facility equipment. However, since the management apparatus mainly collects data necessary for managing the facility equipment, the operation data collected by the management apparatus is part of the operation data of the facility equipment. Therefore, there is a problem that the useful operation data except the operation data collected by the management apparatus is not collected.

In the data-collecting apparatus <NUM> of the present embodiment, the communication unit <NUM> connects the data-collecting apparatus <NUM> to the network NW2b that connects the management apparatus <NUM> that manages the chiller units 30a to 30c, and the chiller units 30a to 30c. The data-collecting unit <NUM> collects, with the second communication unit 11b, surplus data <NUM> from the chiller units 30a to 30c on the basis of the second collection condition C2, which is different from the first collection condition at a time when the management apparatus <NUM> collects control data <NUM> from the chiller units 30a to 30c.

As a result, the data-collecting apparatus <NUM> can collect, from the chiller units 30a to 30c, the useful surplus data <NUM> except the control data <NUM> collected by the management apparatus <NUM> from the chiller units 30a to 30c.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, the communication unit <NUM> includes the first communication unit 11a that communicates with the management apparatus <NUM>, and the second communication unit 11b that communicates with the chiller units 30a to 30c. The first communication unit 11a and the second communication unit 11b cooperate with each other to relay the communication between the management apparatus <NUM> and the chiller units 30a to 30c.

As a result, the data-collecting apparatus <NUM> is installed to relay the communication between the management apparatus <NUM> and the chiller units 30a to 30c, and thus can collect operation data <NUM> on the basis of the second collection condition C2 without a change to an existing system.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, the data-collecting unit <NUM> transmits surplus data <NUM> collected on the basis of the second collection condition C2, to the data-utilizing apparatus <NUM>, which is an apparatus that is different from the management apparatus <NUM> and utilizes operation data <NUM>.

As a result, the data-collecting apparatus <NUM> can utilize, for remote monitoring, failure diagnosis, and the like, the surplus data <NUM> collected on the basis of the second collection condition C2.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, the input unit <NUM> inputs the second collection condition C2. The input unit <NUM> receives at least input from the data-utilizing apparatus <NUM>.

As a result, the data-collecting apparatus <NUM> can input the second collection condition C2 corresponding to a purpose of utilization of surplus data <NUM>.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, the analyzing unit <NUM> analyzes the regularity of first request packets D1. The first request packet D1 is a communication packet that is for requesting control data <NUM> and is transmitted to the chiller units 30a to 30c when the management apparatus <NUM> collects the control data <NUM> on the basis of the first collection condition.

As a result, the data-collecting apparatus <NUM> analyzes the regularity of first request packets D1, so that the data-collecting apparatus <NUM> can collect surplus data <NUM> on the basis of the second collection condition C2 in such a manner that delays in responses to the first request packets D1 do not occur.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, on the basis of the first request packet information included in first request packets D1, the analyzing unit <NUM> determines, from the first request packets D1, a periodically-transmitted packet PP. The first request packet information includes information on the chiller units 30a to 30c, which are the transmission destinations of the first request packet D1, and the request content of the first request packet D1. The periodically-transmitted packet PP is a first request packet D1 periodically transmitted.

As a result, the data-collecting apparatus <NUM> determines, from first request packets D1, a periodically-transmitted packet PP, so that the data-collecting apparatus <NUM> can collect surplus data <NUM> on the basis of the second collection condition C2 in such a manner that a delay in a response to the periodically-transmitted packet PP does not occur.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, among first request packets D1 transmitted within a predetermined period, the analyzing unit <NUM> totals the number of the first request packets D1 whose part of the first request packet information is the same. The analyzing unit <NUM> determines that a first request packet D1 having at least the largest totaled value is a periodically-transmitted packet PP.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM> of the present embodiment, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS of second request packets D2. The second request packets D2 are communication packets that are for requesting surplus data <NUM> and are transmitted to the chiller units 30a to 30c when the data-collecting unit <NUM> collects the surplus data <NUM> on the basis of the second collection condition C2. The transmission-schedule-determining unit <NUM> determines a transmission schedule SS to transmit second request packets D2 in such a manner that the timings at which first request packets D1 are transmitted are avoided.

Specifically, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of periodically-transmitted packets PP received by the first communication unit 11a, a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

As a result, according to the transmission schedule SS, the data-collecting apparatus <NUM> transmits the second request packets D2, so that delays in responses to periodically-transmitted packets PP can be prevented.

In the present embodiment, first request packet information includes information on the chiller units 30a to 30c, which are the transmission destinations of the first request packet D1, and the request content of the first request packet D1.

However, first request packet information may further include "IP address", "memory address", "number of registers", and the like of the chiller units 30a to <NUM>. In this case, a first table TBL1 is created with "facility equipment", "request content", "IP address", "memory address", "number of registers", and the like as primary keys. In other words, the analyzing unit <NUM> ascertains first request packets D1 that have the same "facility equipment", "request content", "IP address", "memory address", "number of registers", and the like as the same first request packets D1.

As a result, the data-collecting apparatus <NUM> can determine, with the analyzing unit <NUM>, periodically-transmitted packets PP in more detail. Further, the data-collecting apparatus <NUM> can determine, with the transmission-schedule-determining unit <NUM>, a transmission schedule SS in more detail.

In the present embodiment, control data <NUM> that satisfies the first collection condition is transmitted from the management apparatus <NUM> to the data-utilizing apparatus <NUM>.

However, control data <NUM> that satisfies the first collection condition may be transmitted from the data-collecting apparatus <NUM> to the data-utilizing apparatus <NUM>.

In other words, on the basis of the first collection condition, the data-collecting unit <NUM> further collects, with the communication unit <NUM>, control data <NUM> (operation data <NUM>) from the chiller units 30a to 30c (facility equipment <NUM>). The data-collecting unit <NUM> further transmits, to the data-utilizing apparatus <NUM>, the control data <NUM> (operation data <NUM>) collected on the basis of the first collection condition.

For example, the data-collecting unit <NUM> collects, from the first communication unit 11a or the second communication unit 11b, control data <NUM> that satisfies the first collection condition and has been received from the chiller units 30a to 30c by the first communication unit 11a or the second communication unit 11b, and transmits the control data <NUM> to the data-utilizing apparatus <NUM>. The data-collecting unit <NUM> sequentially or periodically collects control data <NUM> that satisfies the first collection condition, and transmits the control data <NUM> to the data-utilizing apparatus <NUM>.

As a result, the data-collecting apparatus <NUM> can utilize, for remote monitoring, failure diagnosis, and the like, control data <NUM> collected on the basis of the first collection condition. Further, the data-collecting apparatus <NUM> can remove a load of the management apparatus <NUM> transmitting control data <NUM> to the data-utilizing apparatus <NUM>.

In the present embodiment, when the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of the periodically-transmitted packets PP received by the first communication unit 11a, a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

However, when the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> calculates, on the basis of the transmission times of the periodically-transmitted packets PP transmitted by the second communication unit 11b and the receipt times of control data <NUM> (operation data <NUM>) received by the second communication unit 11b (communication unit <NUM>) and transmitted from the chiller units 30a to 30c (facility equipment <NUM>) in response to the periodically-transmitted packets PP, response time periods of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

In this case, after a periodically-transmitted packet PP is received from the management apparatus <NUM>, the analyzing unit <NUM> acquires, from the second communication unit 11b, a transmission time at which the periodically-transmitted packet PP is transmitted to the chiller units 30a to 30c and receipt times at which pieces of control data <NUM> corresponding to the periodically-transmitted packet PP are received (hereinafter, the receipt times may be referred to as the response times), and stores the transmission times and the receipt times in the first table TBL1.

Table <NUM> below is an example showing the above-described transmission time and response times with respect to four periodically-transmitted packets PP. In Table <NUM>, as in Table <NUM> and the like, transmission times and response times before update are stored.

It is seen from Table <NUM> that the response time periods of the periodically-transmitted packets PP (time periods from the transmission times to the response times of the same records) are one minute for the record whose "record ID" = <NUM>, two minutes for the record whose "record ID" = <NUM>, one minute for the record whose "record ID" = <NUM>, and two minutes for the record whose "record ID" = <NUM>. In other words, it is seen that the response time period of the chiller unit 30a is one minute, and the response time period of the chiller unit 30b is two minutes. Further, it is seen that the interval time periods during which the periodically-transmitted packets PP are not transmitted (time periods from the response times of certain records to the transmission times of the next transmitted records) are three minutes and two seconds between the "record IDs" = <NUM> and <NUM>, three minutes and one second between the "record IDs" = <NUM> and <NUM>, four minutes and two seconds between the "record IDs" = <NUM> and <NUM>, and ten minutes between the "record IDs" = <NUM> and <NUM>.

A time period during which second request packets D2 are transmitted is, for example, an interval time period during which the periodically-transmitted packets PP are not transmitted. The transmission destinations of second request packets D2 may be determined such that corresponding interval time periods are filled with the response time period of each of the chiller units 30a to 30c. For example, since the interval time period between the "record IDs" = <NUM> and <NUM> is three minutes and two seconds, during the interval time period, one second request packet D2 is transmitted to each of the chiller unit 30a (the response time period is one minute) and the chiller unit 30b (the response time period is two minutes).

As described above, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS such that second request packets D2 are transmitted to the appropriate chiller units 30a to 30c during an interval time period from a response time at which each control data <NUM> corresponding to a periodically-transmitted packet PP is received. Note that when the data-collecting unit <NUM> transmits second request packets D2 according to a transmission schedule SS, the data-collecting unit <NUM> acquires, from the second communication unit 11b or the analyzing unit <NUM>, a response time at which each control data <NUM> corresponding to a periodically-transmitted packet PP is received.

The transmission-schedule-determining unit <NUM> may determine, on the basis of the priorities of second request packets D2, a transmission schedule SS of the second request packets D2. For example, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS in such a manner that a second request packet D2 for requesting surplus data <NUM> related to a malfunction and having a high priority is preferentially transmitted.

As a result, the data-collecting apparatus <NUM> can preferentially collect surplus data <NUM> related to a malfunction or the like and having a high priority.

For example, the transmission-schedule-determining unit <NUM> may determine a transmission schedule SS on the basis of the bandwidth occupancy rate of the network NW2b that connects the management apparatus <NUM> and the chiller units 30a to 30c (facility equipment <NUM>). For example, in a case where the bandwidth occupancy rate of the network NW2b exceeds a predetermined value, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS in such a manner that transmission of second request packets D2 is stopped. Here, the bandwidth occupancy rate of the network NW2b is analyzed by the analyzing unit <NUM>. The analysis of the bandwidth occupancy rate is performed by using, for example, existing network diagnosis software or the like.

As a result, the data-collecting apparatus <NUM> can prevent congestion of the network NW2b.

The data-collecting apparatus <NUM> may further include an acquisition unit <NUM>, a learning unit <NUM>, and a response unit <NUM>. <FIG> is a functional block diagram of the data-collecting apparatus <NUM> according to the present modification. In <FIG>, portions except portions related to the present modification are omitted. Further, <FIG> and <FIG> are connected by circled numbers. The acquisition unit <NUM>, the learning unit <NUM>, and the response unit <NUM> are various functional blocks implemented by the control arithmetic device and the storage device.

The acquisition unit <NUM> acquires the receipt time at which a first request packet D1 is received by the first communication unit 11a (communication unit <NUM>), and the first request packet information of the first request packet D1. Specifically, as indicated by solid-line arrows in <FIG>, the acquisition unit <NUM> creates a second table TBL2 in which the receipt times of first request packets D1, and the first request packet information of the first request packets D1 are accumulated. Every time the first communication unit 11a receives a first request packet D1, the acquisition unit <NUM> acquires, from the first communication unit 11a, the receipt time and first request packet information of the first request packet D1, and updates the second table TBL2.

Table <NUM> below is an example of the second table TBL2.

As shown in Table <NUM>, the difference between the second table TBL2 and the first table TBL1 is that when first request packets D1 whose "facility equipment" and "request content" are the same are received, the "receipt time" is not updated to the most recent time, but the first request packets D1 are simply accumulated.

As indicated by the solid-line arrows in <FIG>, the learning unit <NUM> generates a learned model LM that learns by association the receipt times of first request packets D1 and the first request packet information of the first request packets D1 that have been acquired by the acquisition unit <NUM>. The learning unit <NUM> uses the records accumulated in the second table TBL2 to generate the learned model LM. The learning unit <NUM> may update the learned model LM each time some records have been accumulated in the second table TBL2. Alternatively, the learning unit <NUM> may sequentially update the learned model LM each time one record is added to the second table TBL2. As the learned model LM, for example, a recurrent neural network, a state space model, or the like is used.

As a result, the data-collecting apparatus <NUM> can learn the relationships between the receipt times of the first request packets D1, and the transmission destinations, request contents, and the like of the first request packets D1 included in the first request packet information.

The response unit <NUM> responds to the first request packets D1. As indicated by the solid-line arrows in <FIG>, before a predetermined time, the response unit <NUM> uses the learned model LM to predict the first request packet information of a first request packet D1 to be received at the predetermined time. On the basis of a first request packet D1 including the predicted first request packet information, the response unit <NUM> acquires, with the second communication unit 11b, control data <NUM> (operation data <NUM>) from the chiller units 30a to 30c (facility equipment <NUM>). The response unit <NUM> caches the control data <NUM>. In a case where after the predetermined time, the first communication unit 11a receives a first request packet D1 including the predicted first request packet information, the response unit <NUM> does not relay the first request packet D1 to the chiller units 30a to 30c (facility equipment <NUM>), but the response unit <NUM>, instead of the chiller units 30a to 30c (facility equipment <NUM>), transmits the cached control data <NUM> (operation data <NUM>) to the management apparatus <NUM>.

As a result, the data-collecting apparatus <NUM> can respond to the management apparatus <NUM> on behalf of the chiller units 30a to 30c, and thus a time period of the response to the management apparatus <NUM> can be shortened.

Note that in a case where when a first request packet D1 is received from the management apparatus <NUM>, control data <NUM> requested by the first request packet D1 has not been cached, the data-collecting apparatus <NUM> performs relay processing similar to the relay processing of the present embodiment, as indicated by dashed-double-dotted-line arrows in <FIG>.

<FIG> is a diagram showing a communication network around data-collecting apparatuses 10a to 10c according to the present modification. In the present embodiment, as shown in <FIG>, the one data-collecting apparatus <NUM> is installed for the three chiller units 30a to 30c. However, as shown in <FIG>, the data-collecting apparatuses 10a to 10c may be installed for the chiller units 30a to 30c, respectively.

In this case, for example, the data-collecting apparatus 10a relays only first request packets D1 to the chiller unit 30a from the management apparatus <NUM>. Further, the data-collecting apparatus 10a transmits second request packets D2 only to the chiller unit 30a. As a result, the processing loads of the data-collecting apparatuses 10a to 10c can be reduced. Further, the data-collecting apparatuses 10a to 10c can increase the number of pieces of surplus data <NUM> to be collected.

(<NUM>-<NUM>) Although the embodiments of the present disclosure have been described above, it will be understood that various changes in the forms and details can be made without departing from the scope of the appended claims.

<FIG> is an overall configuration diagram of an air-conditioning system <NUM>' according to the present embodiment. <FIG> is a diagram showing a communication network around a data-collecting apparatus <NUM>' according to the present embodiment. <FIG> is a functional block diagram of the data-collecting apparatus <NUM>' according to the present embodiment. <FIG> and <FIG> are connected by circled numbers.

As shown in <FIG> and <FIG>, the data-collecting apparatus <NUM> of the first embodiment is installed to relay the communication between the management apparatus <NUM> and the chiller units 30a to 30c. Therefore, as shown in <FIG>, the communication unit <NUM> of the data-collecting apparatus <NUM> includes the first communication unit 11a that communicates with the management apparatus <NUM>, and the second communication unit 11b that communicates with the chiller units 30a to 30c.

For the data-collecting apparatus <NUM>' of the present embodiment, as shown in <FIG> and <FIG>, a network NW2b' connecting a management apparatus <NUM> and chiller units 30a to 30c (facility equipment <NUM>) is a bus-type network. The data-collecting apparatus <NUM>' is installed in such a manner that the data-collecting apparatus <NUM>' is connected to the network NW2b'. Therefore, as shown in <FIG>, the data-collecting apparatus <NUM>' includes one communication unit <NUM>' connected to the network NW2b'. The communication unit <NUM>' receives first request packets D1 from the management apparatus <NUM>, but, unlike the second communication unit 11b, does not transmit the first request packets D1 to the chiller units 30a to 30c. Further, the communication unit <NUM>' receives control data <NUM> from the chiller units 30a to 30c, but, unlike the first communication unit 11a, does not transmit the control data <NUM> to the management apparatus <NUM>.

Further, since the data-collecting apparatus <NUM>' does not relay the communication between the management apparatus <NUM> and the chiller units 30a to 30c, the data-collecting apparatus <NUM>' does not have, unlike the data-collecting apparatus <NUM>, a function for responding to the management apparatus <NUM> on behalf of the chiller units 30a to 30c (function of the modification 1F of the first embodiment).

Hereinafter, points different from the first embodiment will be mainly described. Except for the described points, the second embodiment is similar to the first embodiment unless otherwise described.

As shown in <FIG> and <FIG>, the data-collecting apparatus <NUM>', the management apparatus <NUM>, and the chiller units 30a to 30c are communicably connected to each other through the network NW2b'. The network NW2b' is a bus-type network. The network NW2b' is, for example, Modbus, BACnet, Ethernet, and the like. Data is transmitted and received between the data-collecting apparatus <NUM>', the management apparatus <NUM>, and the chiller units 30a to 30c through the network NW2b'.

As shown in <FIG>, the data-collecting apparatus <NUM>' mainly includes the communication unit <NUM>' and a data-collecting unit <NUM>.

The data-collecting apparatus <NUM>' includes a control arithmetic device and a storage device. As the control arithmetic device, a processor, such as a CPU or a GPU, can be used. The control arithmetic device reads programs stored in the storage device, and performs predetermined image processing and arithmetic processing according to the programs. In addition, according to the programs, the control arithmetic device can write an arithmetic result into the storage device, and can read information stored in the storage device. The data-collecting apparatus <NUM>' also includes a timer. The communication unit <NUM>', the data-collecting unit <NUM>, an input unit <NUM>, an analyzing unit <NUM>, and a transmission-schedule-determining unit <NUM> are various functional blocks implemented by the control arithmetic device and the storage device.

The communication unit <NUM>' connects the data-collecting apparatus <NUM>' to the network NW2b' that connects the management apparatus <NUM> and the chiller units 30a to 30c.

As shown in <FIG>, the data-collecting unit <NUM> collects, with the communication unit <NUM>', surplus data <NUM> from the chiller units 30a to 30c on the basis of a second collection condition C2, which is different from a first collection condition at a time when the management apparatus <NUM> collects control data <NUM> from the chiller units 30a to 30c.

As shown in <FIG>, the analyzing unit <NUM> creates a first table TBL1 in which first request packet information, and the receipt times of the first request packets D1 are accumulated. Every time the communication unit <NUM>' receives a first request packet D1, the analyzing unit <NUM> acquires, from the communication unit <NUM>', the first request packet information and receipt time of the first request packet D1, and updates the first table TBL1. The "receipt time" of the first table TBL1 is a time at which the communication unit <NUM>' receives the first request packet D1.

When the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of the periodically-transmitted packets PP received by the communication unit <NUM>', a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

Among the consecutive ones of the periodically-transmitted packets PP, the data-collecting unit <NUM> acquires, from the communication unit <NUM>' or the analyzing unit <NUM>, the timing at which the last periodically-transmitted packet PP is received.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM>' of the present embodiment, the communication unit <NUM>' connects the data-collecting apparatus <NUM>' to the network NW2b' that connects the management apparatus <NUM> that manages the chiller units 30a to 30c, and the chiller units 30a to 30c. The data-collecting unit <NUM> collects, with the communication unit <NUM>', surplus data <NUM> from the chiller units 30a to 30c on the basis of the second collection condition C2, which is different from the first collection condition at a time when the management apparatus <NUM> collects control data <NUM> from the chiller units 30a to 30c.

As a result, the data-collecting apparatus <NUM>' can collect, from the chiller units 30a to 30c, the useful surplus data <NUM> except the control data <NUM> collected by the management apparatus <NUM> from the chiller units 30a to 30c.

(<NUM>-<NUM>) For the data-collecting apparatus <NUM>' of the present embodiment, the network NW2b' connecting the management apparatus <NUM> and the chiller units 30a to 30c is a bus-type network.

As a result, the data-collecting apparatus <NUM>' is connected to the bus-type network, and thus can collect surplus data <NUM> on the basis of the second collection condition C2 without a change to an existing system.

(<NUM>-<NUM>) In the data-collecting apparatus <NUM>' of the present embodiment, the transmission-schedule-determining unit <NUM> determines a transmission schedule SS of second request packets D2. The second request packets D2 are communication packets that are for requesting surplus data <NUM> and are transmitted to the chiller units 30a to 30c when the data-collecting unit <NUM> collects the surplus data <NUM> on the basis of the second collection condition C2. The transmission-schedule-determining unit <NUM> determines a transmission schedule SS to transmit second request packets D2 in such a manner that the timings at which first request packets D1 are transmitted are avoided.

Specifically, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of periodically-transmitted packets PP received by the communication unit <NUM>', a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

As a result, according to the transmission schedule SS, the data-collecting apparatus <NUM>' transmits the second request packets D2, so that delays in responses to periodically-transmitted packets PP can be prevented.

In the present embodiment, control data <NUM> that satisfies the first collection condition is transmitted from the management apparatus <NUM> to a data-utilizing apparatus <NUM>.

In other words, on the basis of the first collection condition, the data-collecting unit <NUM> further collects, with the communication unit <NUM>', control data <NUM> from the chiller units 30a to 30c. The data-collecting unit <NUM> further transmits, to the data-utilizing apparatus <NUM>, the control data <NUM> collected on the basis of the first collection condition.

For example, the data-collecting unit <NUM> collects, from the communication unit <NUM>', control data <NUM> that satisfies the first collection condition and has been received from the chiller units 30a to 30c by the communication unit <NUM>', and transmits the control data <NUM> to the data-utilizing apparatus <NUM>. The data-collecting unit <NUM> sequentially or periodically collects control data <NUM> that satisfies the first collection condition, and transmits the control data <NUM> to the data-utilizing apparatus <NUM>.

As a result, the data-collecting apparatus <NUM>' can utilize, for remote monitoring, failure diagnosis, and the like, the control data <NUM> collected on the basis of the first collection condition. Further, the data-collecting apparatus <NUM>' can remove a load of the management apparatus <NUM> transmitting control data <NUM> to the data-utilizing apparatus <NUM>.

In the present embodiment, when the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> calculates, on the basis of the receipt times of the periodically-transmitted packets PP received by the communication unit <NUM>', a receipt time period of consecutive ones of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

However, when the analyzing unit <NUM> determines periodically-transmitted packets PP, the transmission-schedule-determining unit <NUM> may calculate, on the basis of the receipt times of the periodically-transmitted packets PP received by the communication unit <NUM>' and the receipt times of control data <NUM> also received by the communication unit <NUM>' and transmitted from the chiller units 30a to 30c in response to the periodically-transmitted packets PP, response time periods of the periodically-transmitted packets PP and an interval time period during which the periodically-transmitted packets PP are not transmitted, to determine a transmission schedule SS of second request packets D2.

The present modification is the modification example 1C of the first embodiment in which "the transmission times of the periodically-transmitted packets PP transmitted by the second communication unit 11b" is replaced with "the receipt times of the periodically-transmitted packets PP received by the communication unit <NUM>'", and "the receipt times of control data <NUM> received by the second communication unit 11b and transmitted from the chiller units 30a to 30c in response to the periodically-transmitted packets PP" is replaced with "the receipt times of control data <NUM> received by the communication unit <NUM>' and transmitted from the chiller units 30a to 30c in response to the periodically-transmitted packets PP". Note that when the data-collecting unit <NUM> transmits second request packets D2 according to a transmission schedule SS, the data-collecting unit <NUM> acquires, from the communication unit <NUM>' or the analyzing unit <NUM>, a response time at which each control data <NUM> corresponding to a periodically-transmitted packet PP is received.

Claim 1:
A data-collecting apparatus (<NUM>, 10a, 10b, 10c, <NUM>') for collecting, from at least one piece of facility equipment (<NUM>, 30a, 30b, 30c), operation data (<NUM>, <NUM>, <NUM>) of the facility equipment, the data-collecting apparatus (<NUM>, 10a, 10b, 10c, <NUM>') comprising:
a communication unit (<NUM>, 11a, 11b, <NUM>') connectable to a network (NW2b, NW2b') that connects a management apparatus (<NUM>) that manages the facility equipment, and the facility equipment; and
a data-collecting unit (<NUM>) configured to collect, with the communication unit, the operation data from the facility equipment on a basis of a second collection condition (C2), which is different from a first collection condition at a time when the management apparatus collects the operation data from the facility equipment,
characterized by:
an analyzing unit (<NUM>) configured to analyze regularity of first request packets (D1), which are communication packets that are for requesting the operation data and are transmitted to the facility equipment when the management apparatus collects the operation data on a basis of the first collection condition; and
a transmission-schedule-determining unit (<NUM>) configured to determine a transmission schedule (SS) of a second request packet (D2), which is a communication packet that is for requesting the operation data, and is transmitted to the facility equipment when the data-collecting unit collects the operation data on a basis of the second collection condition,
wherein
the transmission-schedule-determining unit is configured to determine the transmission schedule (SS) to transmit the second request packet in such a manner that timings at which the first request packets are transmitted are avoided.