JP7620955B1 - Building management facility construction support system - Google Patents

Abstract

A building management facility construction support system is provided that enables appropriate communication among a variety of stakeholders.
[Solution] The system includes a correspondence information creation unit 104 that can input equipment information related to micro edge devices, sensor devices, etc. to be installed, and output correspondence information that is pre-associated with the equipment information, where the equipment includes at least micro edge devices, etc., and sensor devices, etc. that can be connected to the micro edge devices, and the equipment information includes information related to the micro edge devices and information related to the sensor devices, and the correspondence information creation unit 104 can manually input primary equipment information and can input XYZ coordinates related to the placement of the micro edge devices, and outputs information related to the connection of the micro edge devices with the sensor devices, etc., as additional information to the correspondence information related to the micro edge devices.
[Selection] Figure 36

Description

The present invention relates to a building management facility construction support system that supports the construction of building management facilities, for example.

When constructing building management facilities, it is necessary to create many different types of drawings and tables. The drawings and tables that are created include, for example, (1) outline drawings, (2) equipment lists, (3) nameplate lists, (4) power supply circuit diagrams, (5) deployment connection diagrams, (6) terminal layout diagrams, (7) system configuration diagrams, (8) point lists, (9) system diagrams, and (10) system function diagrams. Prior patent documents relating to the construction of building management facilities include Patent Documents 1 to 3, which are listed below. These Patent Documents 1 to 3 disclose inventions that reduce the effort required to create various drawings and tables.

Patent No. 3021766 Patent No. 3209535 Patent No. 4431945

Nowadays, buildings (such as so-called intelligent buildings) are equipped with a wide variety of equipment. In addition, the construction and renovation of buildings involve a wide variety of stakeholders, such as the owner, general contractor, design company, construction company, building management company, tenants, etc., who consult with each other. However, these stakeholders include people who do not have detailed knowledge of the technical specifications of the equipment, and people who are only familiar with the equipment of a specific manufacturer. For this reason, in the past, it was often necessary to remake drawings and tables created based on the results of discussions. Furthermore, insufficient communication between stakeholders could hinder the construction of building management facilities and labor-saving and DX (digital transformation) in building construction.

The objective of the present invention is to provide a building management facility construction support system that enables appropriate communication among various stakeholders.

In order to achieve the above object, the building management facility construction support system according to the present invention comprises:
A building management facility construction support system for supporting the construction of a building management facility, comprising:
A correspondence information creation unit is provided that is capable of inputting facility equipment information related to the facility equipment to be installed and outputting correspondence information that is previously associated with the facility equipment information,
The facility equipment includes at least a primary facility equipment and a secondary facility equipment connectable to the primary facility equipment,
The facility equipment information includes at least first facility equipment information related to the first facility equipment,
The correspondence information creation unit
The first facility equipment information can be manually input,
It is possible to input coordinate information relating to the arrangement of the first equipment,
outputting information related to a connection of the first equipment device with the second equipment device as supplementary information of the correspondence information related to the first equipment device information;
An individual structured entity which is a database corresponding to each of a plurality of types of communication standards;
An integrated structuring body which is a database that consolidates information of the individual structuring bodies in a predetermined structure,
a building management facility construction support system, wherein the corresponding information creation unit creates the auxiliary information by using information of the integrated structure body,
The building management facility continues to use the integrated structure.

The above invention provides a building management facility construction support system that enables appropriate communication among various stakeholders.

1 is an explanatory diagram illustrating an example of a building management system that can be constructed by a building management facility construction support system according to an embodiment. FIG. 1 is a block diagram illustrating a schematic configuration of a wireless sensor device that can be used in a building management system. 1 is a flowchart illustrating an outline of a procedure for creating a database in a building management system. FIG. 2 is an explanatory diagram illustrating information in a database related to a building management system. 1 is a diagram showing an example of an SNVT correspondence table. FIG. 1A is an explanatory diagram showing a conventional technique related to mapping, and FIG. 1B is an explanatory diagram showing an example of mapping using a productivity tool according to an embodiment. 7A is an explanatory diagram showing a conventional technique related to mapping, similar to FIG. 6, and FIG. 7B is an explanatory diagram showing an example of mapping using the productivity tool of the embodiment, similar to FIG. 6. FIG. 1A is an explanatory diagram showing, by means of an image, an example of an initial screen displayed when using a productivity tool, and FIG. 1B is an explanatory diagram showing, by means of an image, an example of a template for a specified protocol. FIG. 13A is an explanatory diagram showing an example of a template for another specified protocol using an image, and FIG. 13B is an explanatory diagram showing an example of a template for a specified management system using an image. 1 is a block diagram illustrating a schematic configuration of a building management facility construction support system according to an embodiment. FIG. 1 is an explanatory diagram showing an example of a layout diagram used in discussions regarding the placement of facility equipment. FIG. 10 is an explanatory diagram showing an example of an operation screen in a CAD system; 1A is an explanatory diagram showing an example of a control panel automatic drawing menu bar, and FIG. 1B is a diagram showing the outline of the contents of each function selectable by the automatic drawing function button. FIG. 13 is an explanatory diagram showing a display example when the automatic drawing function button of "attribute information setting" is selected. FIG. 15 is an explanatory diagram showing a display example following FIG. 14 . FIG. 16 is an explanatory diagram showing a display example following FIG. 15 . FIG. 17 is an explanatory diagram showing a display example following FIG. 16 . FIG. 13 is an explanatory diagram showing a display example when the "equipment layout" automatic drawing function button is selected. FIG. 19 is an explanatory diagram showing a display example following FIG. 18 . FIG. 20 is an explanatory diagram showing a display example following FIG. 19 . FIG. 21 is an explanatory diagram showing a display example following FIG. 20 . FIG. 13 is an explanatory diagram showing a display example when the automatic drawing function button "Micro Edge Level Placement" is selected. FIG. 23 is an explanatory diagram showing a display example following FIG. 22. FIG. 24 is an explanatory diagram showing a display example following FIG. 23 . FIG. 25 is an explanatory diagram showing a display example following FIG. 24 . FIG. 26 is an explanatory diagram showing a display example following FIG. 25 . FIG. 27 is an explanatory diagram showing a display example following FIG. 26. FIG. 28 is an explanatory diagram showing a display example following FIG. 27. FIG. 29 is an explanatory diagram showing a display example following FIG. 28. FIG. 13 is an explanatory diagram showing a display example when the automatic drawing function button for "sensor/operation terminal layout" is selected. FIG. 31 is an explanatory diagram showing a display example following FIG. 30 . FIG. 32 is an explanatory diagram showing a display example following FIG. 31 . FIG. 33 is an explanatory diagram showing a display example following FIG. 32. 1A is an explanatory diagram showing an "equipment list", FIG. 1B is an explanatory diagram showing a "device type" diagram, FIG. 1C is an explanatory diagram showing a "signal type" diagram, FIG. 1D is an explanatory diagram showing a "power supply system diagram", FIG. 1E is an explanatory diagram showing an "outline drawing", and FIG. 1F is an explanatory diagram showing an "expanded connection diagram". 10 is a flowchart showing a process flow until correspondence information can be created. FIG. 2 is a block diagram showing an integrated structuring body. 1 is a diagram showing an example of devices constituting a building management system. FIG. 2 is an explanatory diagram showing an example of data handled in the building management facility construction support system. FIG. 11 is an explanatory diagram showing an example of zoning of data. FIG. 11 is an explanatory diagram showing an example of how to divide upper and lower hierarchical levels. FIG. 4 is an explanatory diagram showing an example of a type of profile. FIG. 13 is an explanatory diagram showing a menu bar related to the “Execution Schedule” screen; FIG. 13 is an explanatory diagram showing a list of screens relating to a scheduler function. FIG. 4A is an explanatory diagram showing an example of a screen display related to a scheduler, and FIG. 4B is an explanatory diagram showing an example of a screen display related to settings of the scheduler. 1A is an explanatory diagram showing an example of a demand menu bar, FIG. 1B is an explanatory diagram showing an example of a trend screen, and FIG. 1C is an explanatory diagram showing an example of a daily report. FIG. 2 is an explanatory diagram showing an example of a structure for executing a demand control function.

[Order of Description in the Embodiment]
A building management facility construction support system 100 (FIG. 10) according to an embodiment of the present invention will be described. However, in order to facilitate understanding of the technical features of the building management facility construction support system 100 (FIG. 10), an example of a building management system to be constructed (designed) will first be described.

The building management system to be constructed in this embodiment is, for example, a building management system disclosed in the applicant's Japanese Patent Publication No. 7249078 (and Japanese Patent Publication No. 7262035 and Japanese Patent Publication No. 7262036) and Japanese Patent Application No. 2023-040742 (specification and drawings). The embodiment of the building management system disclosed in the specification and drawings of the above-mentioned Japanese Patent Application No. 2023-040742 will be described below by transcribing the contents (the other two applications have similar contents). After that, the embodiment of the invention of the building management facility construction support system (building management facility construction support system 100) will be described.

[Examples of building management equipment and building management systems to be developed]
<Outline of the building management system according to the embodiment>
A building management system according to an embodiment of the present invention will now be described. The building management system according to the present embodiment enables centralized management or distributed control of various management items such as air conditioning, lighting, sanitation, warnings (security, alarms), energy, etc., both inside and outside the building and from remote locations.

The building management system of this embodiment includes various equipment within a building. The equipment includes various equipment such as air conditioners, lighting equipment, doors, etc. The equipment also includes sensors such as temperature sensors that detect the temperature within a room, humidity sensors that detect humidity, illuminance sensors that detect the illuminance of lighting equipment, and contact sensors that detect the opening and closing of doors.

Facility equipment also includes air conditioner control panels and remote controls (remote controllers), lighting control panels and remote controls, various switches installed on walls, etc. (switches). Furthermore, facility equipment can also include current transformers, power monitors, circuit protectors, power supply units, compact gateways, etc. (other electrical equipment) that are used to understand power usage.

These are examples of facility equipment, and other equipment typically used in building management can also be included in the facility equipment of this embodiment.

The building management system of this embodiment enables the building manager who monitors the building's equipment and general users of each equipment (such as employees of tenants who use a floor or section) to select equipment and enter instructions (commands) from their own mobile information terminals (such as smartphones or tablets) based on the information collected by each equipment.

Furthermore, in the building management system of this embodiment, the types of software (including application software) used for building management are kept to a minimum by integrating the system. In addition, the building management system of this embodiment comes standard with a monitoring system that enables overall monitoring.

This may seem obvious, but with conventional building management systems, it was difficult to collect information horizontally and provide integrated services to building managers and general users of facility equipment, regardless of differences in the specifications of various information (signal standards, communication standards, OS (operating systems), programming languages, etc.) between manufacturers and vendors. The building management system of this embodiment makes this possible.

More specifically, the building management system of this embodiment aims to "liberate from monitoring rooms in the building (central monitoring rooms)." This means that it is possible to do away with the central monitoring rooms that were previously installed in buildings, and to keep the number of personnel involved in central monitoring to a minimum, such as just one person.

In conventional building management systems, a central monitoring room was essential in the building. Moreover, various management items such as air conditioning, lighting, sanitation, alarms, energy, etc. were managed independently for each installed device. As mentioned above, for example, in the invention disclosed in the above-mentioned Patent Document 1 (note: JP-A-2003-134120), it is necessary to select facility control devices for each manufacturer (paragraph 0009). For this reason, even if the control of devices can be integrated vertically (vertically) in the system configuration, it cannot be integrated horizontally (horizontally) regardless of differences in the specifications of various information for each manufacturer or vendor, and is therefore divided.

Figure 1 shows a schematic diagram of the building management system 10 of this embodiment. The diagram shows an example of multiple systems (item systems) related to facility equipment. Shown in Figure 1 are an air conditioning-related system 12, a lighting and outlet system 14, a sanitary and plumbing system 16, a status and alarm system 18, and an energy system 20.

The air conditioning-related system 12 represents a system (group) of multiple equipment related to air conditioning, such as air conditioners (air conditioners, air conditioners), temperature sensors, humidity sensors, etc.

The lighting and outlet system 14 represents a system of equipment related to lighting devices, illuminance sensors, devices for connecting to commercial power sources, etc. The sanitary and water system 16 represents a system of multiple equipment related to sanitary and water-related needs, such as toilets, washrooms, and hot water supply.

The status/alarm system 18 represents a system of multiple equipment devices related to dealing with the opening and closing of doors, earthquakes, intrusion by unauthorized persons, etc. The energy system 20 represents a system of multiple equipment devices such as sensors and switches related to grasping the amount of power used (power consumption), the amount of solar power generated, the amount of fuel used, etc.

Here, the classification of item systems is not limited to the above examples. For example, multiple systems may be integrated, such as the "air conditioning, lighting, and outlet system." Also, each system may be separated, such as the "lighting system," the "outlet system," the "sanitary system," and the "bathroom system." Furthermore, they may be divided into "air conditioning 1," "air conditioning 2," "lighting 1," and "lighting 2."

In the various item systems described above (air conditioning-related system 12, lighting and outlet system 14, sanitation and plumbing system 16, status and alarm system 18, energy system 20, etc.), equipment from various manufacturers and vendors is generally used. For this reason, in the past, each manufacturer and vendor in each item system had to shoulder the burden of information and communications, and when renovating or building a building, it was necessary to order the work from a construction company designated by the manufacturer or vendor.

In addition, each manufacturer or vendor often uses common signal standards and communication standards. For this reason, it is possible to build a management system for each manufacturer or vendor using common signal standards, communication standards, OS, programming languages, etc. Furthermore, when using equipment that is predetermined to support multi-protocol communication standards, it is possible to handle only that equipment in an integrated manner. However, in these cases, it is necessary to install a server compatible with the manufacturer or vendor and build a management system.

For example, if equipment from multiple manufacturers or vendors is used in one item system (such as air conditioning-related system 12), it was necessary to install multiple servers for each item system and build multiple management systems.

In addition, for example, if the manufacturers and vendors were uniform for each item system (air conditioning-related system 12, lighting and outlet system 14, sanitation and plumbing system 16, status and alarm system 18, energy system 20, etc.), it was necessary to install a server for each item system and build a management system.

In this way, integration by manufacturer or vendor (vertical integration in system configuration) is relatively easy, but integration across each item system (air conditioning-related system 12, lighting and outlet system 14, sanitary and plumbing system 16, status and alarm system 18, energy system 20, etc.) (horizontal integration in system configuration) is not easy. Furthermore, in conventional building management systems, IT (information technology) and OT (operational technology) are separated.

The building management system 10 of this embodiment shown in FIG. 1 integrates the equipment items related to various management items and performs appropriate cloud computing, making it possible to eliminate the need for a central monitoring room. The building management system 10 of this embodiment allows various management items to be monitored remotely from the building manager's mobile information terminal 22, such as a smartphone or tablet, without the need to install a large number of application software. As a result, there is no longer a need to tie people down in the central monitoring room, making it possible to reduce the number of personnel and labor costs required for management.

The building management system 10 of this embodiment also allows general users, such as tenant employees, to remotely operate specific management items from a mobile information terminal 24, such as a smartphone or tablet, without having to install a large number of application software.

<Hierarchical structure>
As shown in FIG. 1, the building management system 10 according to this embodiment has a hierarchical structure broadly divided into five levels, from level 0 to level 4. Level 0 is the sensor hierarchy, and level 1 is the sensor controller (micro edge device) hierarchy. Level 2 is the application edge device hierarchy, and level 3 is the integrated controller (integrated edge device) hierarchy. Level 4 is the enterprise edge server hierarchy. Each hierarchy will be described below.

<Level 0: Sensor>
The lowest level hierarchy of the building management system 10 is the sensor. Conventionally, in order to convert various analog information such as temperature, humidity, etc. into digital information, it was necessary to provide a sequencer and set thresholds for the various pieces of information for management.

The data sent from the sensor is formed into a single block by adding various elements such as thresholds, current values, range conversion, etc. In other words, the data is processed in the sequencer, thresholds are set by designers or workers, and only a portion of the output data is used for building management.

One characteristic of conventional building management systems is that they only physically connect devices together using a specific serial bus (RS485). Communications are carried out using the serial bus (RS485) interface, and signal processing is carried out using a communications chip that does not have a CPU. As a result, conventional building management systems only have limited functionality and lack intelligence.

In the building management system 10 according to this embodiment, a wireless intelligent sensor device (hereinafter referred to as a "wireless sensor device") 30 as shown in FIG. 2 is used as a level 0 sensor. The wireless sensor device 30 is capable of detecting multiple types of detection items (physical quantities) (e.g., five types: temperature, humidity, illuminance, acceleration, and contact).

The wireless sensor devices 30 are used in multiple systems (e.g., air conditioning-related system 12, lighting and outlet system 14, sanitation and plumbing system 16, status and alarm system 18, energy system 20, etc.). Furthermore, there are multiple models of wireless sensor devices 30, each of which performs wireless communication using its own communication standard. For this reason, the wireless sensor devices 30 include those that perform wireless communication using different communication standards. Furthermore, it does not matter whether the wireless sensor devices 30 are designed to be compatible with multiple protocols.

The wireless sensor devices 30 are installed, for example, on the walls, ceilings, and doors of a building, and wirelessly transmit the detected information to a level 1 sensor controller (described later). As the wireless sensor devices 30, it is possible to use a mixture of various types provided by multiple manufacturers and vendors.

As shown in FIG. 2, the wireless sensor device 30 includes a temperature sensor unit 32, a humidity sensor unit 34, an illuminance sensor unit 36, an acceleration sensor unit 38, and a contact sensor unit 40. The wireless sensor device 30 further includes a CPU 42, a memory unit 44, an information format conversion unit 46, an information input unit 48, a wireless communication unit 50, and a power generation unit 52.

The temperature sensor unit 32 is equipped with a temperature sensor and can detect, for example, the temperature of the air in a room. The humidity sensor unit 34 is equipped with a humidity sensor and can detect, for example, the humidity of the air in a room. The illuminance sensor unit 36 is equipped with an illuminance sensor and can detect, for example, the brightness of a room.

The acceleration sensor unit 38 is equipped with an acceleration sensor and can detect, for example, an impact transmitted to a wall. The contact sensor unit 40 is equipped with a contact sensor (magnetic contact sensor) and can detect, for example, the opening and closing of a door.

Various common sensors can be used as the temperature sensor, humidity sensor, illuminance sensor, acceleration sensor, and contact sensor provided in the wireless sensor device 30.

The wireless sensor device 30 uses a communications standard (EnOcean) that uses energy harvesting technology to generate power and transmit it wirelessly. In the wireless sensor device 30, the power required for the normal operation of the CPU 42 and the sensor units 32, 34, 36, 38, and 40 is supplied by the power generation unit 52 (here, photovoltaic power generation).

The wireless sensor device 30 can select which detection function to use for which detection item. The wireless sensor device 30 can also use all detection functions simultaneously.

The detection function to be used is set by storing information identifying the selected detection function (detection function identification information) in the storage unit 44. The detection function identification information can be stored using an external communication device capable of wireless communication.

The above-mentioned external communication device can be, for example, a mobile information terminal such as a smartphone or a tablet terminal (mobile information terminals 22, 24, etc.). In this case, it is possible to install a specific application software on the mobile information terminal and operate this application software. Examples of the specific application software include an administrator device management app used by the building administrator and a general user device management app.

In the wireless sensor device 30, the signals from the sensor units being used (at least some of the sensor units 32, 34, 36, 38, and 40) are converted into information in industrial units through information processing by the CPU 42, and digital data is generated. In the wireless sensor device 30, wireless packets are created using the generated digital data, and the wireless packets are sent to a level 1 sensor controller (micro edge device) described below.

For sensors that detect continuous quantities, such as the temperature sensor unit 32, humidity sensor unit 34, and illuminance sensor unit 36, information is transmitted at predetermined intervals (e.g., every few tens of seconds to three minutes). Information related to the signals of the acceleration sensor unit 38 and contact sensor unit 40 is transmitted when acceleration or contact (such as contact pressure) large enough to reach a predetermined threshold is detected.

The larger the information transmission interval for the temperature sensor unit 32, humidity sensor unit 34, illuminance sensor unit 36, etc., the more the amount of information transmitted can be reduced. Information relating to the temperature sensor unit 32, humidity sensor unit 34, and illuminance sensor unit 36 may be transmitted within the above-mentioned specified time, or information relating to the temperature sensor unit 32, humidity sensor unit 34, and illuminance sensor unit 36 may be transmitted in sequence at each of the above-mentioned specified times.

In conventional building management systems, wireless information communication has often been avoided due to problems such as the need for frequent battery replacement and the interruption of wireless signals. The building management system 10 of this embodiment solves the battery issues associated with wireless communication by using energy harvesting technology.

The power generation unit 52 used in the energy harvesting technology is not limited to photovoltaic power generation, but may be, for example, thermoelectric power generation, electromagnetic wave power generation, vibration power generation, etc.

In thermoelectric power generation, for example, a thermoelectric conversion element (an element that converts heat and electricity) that utilizes the Seebeck effect (the phenomenon in which a temperature difference is converted into a voltage) is used to convert the temperature difference of an object into a voltage. For example, heat generated by air conditioning equipment or pipes in a building is converted into electrical energy.

In electromagnetic wave power generation, for example, the energy of radio waves emitted by a wireless LAN in a building is converted into direct current by a rectifying antenna to generate electricity.

In vibration power generation, pressure generated by vibration is converted into electricity via piezoelectric elements or other devices. For example, pressure sensors are installed on the floors of a building, and the pressure generated when people walk along the corridor or pressure caused by vibration is converted into electrical energy.

In addition, in the building management system 10 of this embodiment, a wireless switch (not shown) is used as a switch for turning lights on and off. The wireless switch has a built-in switch mechanism and wireless communication unit, and uses energy harvesting technology to wirelessly transmit information indicating the state of the switch mechanism to the outside.

When an administrator or general user operates the wireless switch with their fingers, on/off information is transmitted wirelessly using induced electromotive force. The wireless switch can be installed on a wall by using screws or attaching a magnetic sheet.

By using wireless switches, it is possible to turn lights on and off without the need for wiring. Because no wiring is required, there are no restrictions on where switches can be placed, allowing for greater freedom in switch placement. In addition, no batteries are required, which also eliminates the need for the time-consuming task of changing batteries.

As described above, by using as many wireless sensor devices 30 and wireless switches as possible for the necessary sensors and switches, it is no longer necessary to run wires to connect the sensors and switches that make up the end of the system to the sequencer. This makes it easier to install the sensors and switches.

Many sensors and switches are included in the aforementioned items 12, 14, 16, 18, and 20. The number of sensors and switches used in a single building will vary depending on factors such as the number of rooms on each floor, but the more intelligent the building, the more likely they will be.

For this reason, when renovating or building a building with many rooms or a highly intelligent building, the amount of work required to wire sensors and switches (number of personnel x time) can be considerable. Therefore, by using the wireless sensor device 30 and wireless switches, much of the wiring work can be eliminated, making it possible to significantly reduce the amount of work required.

Traditionally, the work content and man-hours required for wiring work have tended to be left to the discretion of the work site, which has been a major factor in inaccurate estimates of construction time and labor costs. For example, the wiring between the sensor device and the sequencer, and the wiring between the sequencer and the above-mentioned equipment, was often decided at the discretion of the work site. Also, the number of sensor devices installed can reach hundreds to hundreds of thousands, depending on the type and size of the building. Furthermore, a large portion of the cost of renovating or building a new building is made up of labor costs. Therefore, reducing the man-hours required for wiring will greatly contribute to cost reduction.

In addition, in the building management system 10 according to this embodiment, not all sensors and switches are limited to being wireless, and some sensors and switches may be wired to send signals to a sequencer or the like. In addition, the other electrical devices mentioned above may include those that communicate wirelessly and those that communicate wired.

<Level 1: Sensor Controller (Micro Edge Device)>
The digital data transmitted from each wireless sensor device 30 is received by a sensor controller (micro edge device 60) at level 1. The sensor controller is constituted by the micro edge device 60.

In the building management system 10 of this embodiment, multiple micro edge devices 60 are used depending on conditions such as the size and number of buildings to be managed. Three micro edge devices 60 are shown in FIG. 1 as an example. For example, one micro edge device 60 can be associated with 100 or more (up to about 200) wireless sensor devices 30, and can also be associated with wired sensors and sequencers connected to switches (not shown). One micro edge device 60 can process data for about 100 to 200 monitoring points.

Conventionally, for example, when controlling blinds installed on windows in a building, a controller dedicated to blinds (dedicated controller) was used. The dedicated controller executed a blind control program and carried out processing related to controlling the blinds. In other words, control of the controlled object (here, the blinds) was completed in the control system consisting of the blinds and the dedicated controller.

Traditionally, building management systems have monitored and controlled many management items related to air conditioning, lighting, sanitation, security, energy, etc. In controlling these management items (monitoring and control), as mentioned above, it has been common to control using a variety of signal standards, communication standards, operating systems, programming languages, etc. depending on the equipment used, the equipment manufacturer, model, etc.

Furthermore, in the technical field of building management, there are various standards related to IT (information technology) and OT (operational technology), and because the content of these standards differs, it was not possible to communicatively connect multiple types of sensors, such as various existing sensors and sensors selected by the building construction company, to a single controller.

In contrast, in the building management system 10 of this embodiment, the analog data (data collected by the wireless sensor devices 30), which is the starting point of all information, is digitized by the level 0 wireless sensor devices 30 themselves. For one micro edge device 60, digital information from multiple wireless sensor devices 30 is aggregated in the micro edge device 60.

The wireless sensor devices 30 include those that communicate information using the same digital wireless communication standard and those that communicate information using different digital wireless communication standards. The micro edge device 60 is configured to be able to handle a large number of communication standards (communication protocols) (e.g., 150 or more).

The micro edge device 60 can handle information from multiple wireless sensor devices 30 by converting it into a common communication standard (here, IP (Internet Protocol)) for each communication standard adopted by the wireless sensor devices 30. In other words, the micro edge device 60 inputs signals of different communication standards and outputs a unified signal of the common standard. The micro edge device 60 assigns an IP address to the associated equipment and identifies it using the IP address.

Each micro edge device 60 functions as a gateway that aggregates signals of different communication standards and outputs a signal of common specifications. By providing a large number of micro edge devices 60 according to the size and number of buildings to be managed, it is possible to form a large-scale gateway group consisting of multiple gateways. Note that there may be other gateways (subdivided gateways) between each item system 12, 14, 16, 18, 20 and the micro edge device 60. The gateway group here also includes gateways that exist as equipment separate from the micro edge device 60. The relationship (position) between the micro edge device 60 and the gateways is that the micro edge device is superior and the gateway is subordinate.

In the micro edge device 60, information from the wireless sensor device 30 is collected, the necessary information is organized, and it is sent to the upper layer application edge device 62 (level 2). In the micro edge device 60 hierarchy (level 1), for example, a micro edge device group 60A is formed by a large number of micro edge devices 60. The micro edge device group 60A can be conceptually included in the gateway group mentioned above.

The micro edge device group 60A performs the function of a gateway to convert data and transmits information with standardized specifications (information in a patterned format) to the associated application edge device 62 at the upper layer.

In this way, the analog data digitized by the wireless sensor devices 30 and sequencers undergoes preliminary processing in the micro edge device 60, and is sent to a higher level as information with standardized specifications. In the micro edge device 60, the information digitized by the wireless sensor devices 30 at the terminal undergoes preliminary processing for database creation at level 2.

Although not shown in the figure, the micro edge device 60 may be, for example, a device equipped with a CPU, a memory unit, a wireless communication unit, etc., and capable of converting multi-protocol digital information into a common communication standard through processing such as time division or information conversion processing.

<Level 2: Application Edge Devices>
An application edge device 62 is located in the upper layer (level 2) of the micro edge device 60. The application edge device 62 plays a role in collecting data for each management item (application) such as the building's air conditioning, electricity, sanitation, central monitoring, etc.

As mentioned above, in the micro edge device 60 (level 1), data from the sensor (level 0) is aggregated, and the data digitized by the sensor (level 0) is sent from the micro edge device 60 (level 1) to the application edge device 62 (level 2).

Depending on the size of the building to be managed, for example, one application edge device 62 is installed for approximately 100 micro edge devices 60. At the level of a so-called small to medium-sized building, the entire building can be managed with one application edge device 62. In this case, levels 3 and 4 described below can be omitted.

The application edge device 62 is equipped with a central monitoring function. The central monitoring function performs processing for monitoring and controlling the energy management system (EMS) and enables the obtained information to be provided to external devices. The central monitoring function unit processes information such as the amount of power in real time based on the information collected by each wireless sensor device 30, statistically visualizes it, and outputs it as displayable information. In other words, the monitoring and control system for the energy management system (EMS) is built into the application edge device 62.

In the application edge device 62, as shown in FIG. 3, the information sent from the micro edge device 60 is read into the database creation software (S (step) 11), and the database is automatically created (S12). Furthermore, a productivity tool is used to set individual recognition data (parameter settings, etc.).

The productivity tool was developed as one of the application software used in the building management system 10 of this embodiment. The productivity tool will be described later. Various general software can be used for creating the database.

As shown in Figure 4, the created database records various attributes (including properties) of the collected data. The recorded attributes include information such as IP address, building name, floor, area, management item, information type, information acquisition date, and information acquisition time. In addition, in the case of information on sensors, information such as the detection values of each sensor (detection value information) and on/off information are also included.

Conventionally, setting data had to be manually entered one by one when registering it in an intelligent sensor or micro edge device 60. This type of work not only requires a lot of time and effort, but also requires an understanding of the characteristics and mechanisms of the data. With the building management system 10 of this embodiment, a database is automatically created, making it possible to register data without manual work or the need to understand the mechanisms.

Furthermore, the application edge device 62 can use the central monitoring function unit to output information for statistically visualizing and displaying information such as temperature, humidity, and power consumption collected from each piece of equipment in real time based on databased information. The output information is displayed on a display device or mobile information terminal connected to the building manager's PC (personal computer) via an Internet line (public wireless communication line and public wired communication line) 68. A connection is made to the central monitoring application software via a browser installed on the building manager's PC or mobile information terminal.

The aforementioned EMS (Energy Management System) makes information visible. In other words, the information collected from sensors and various devices such as lighting, air conditioning, sanitation, and energy does not create value if it simply exists. Value is created only when this data (information) is classified by type, only the necessary parts and times are collected, statistically processed, and then displayed on a screen.

The EMS in the building management system 10 of this embodiment is configured to allow the amount of electricity used to be viewed in various graphs. Of course, it is also possible to view the amount of electricity used for each of the various pieces of equipment being used.

Generally, 65% of the energy consumed in a building is for air conditioning and lighting. If air conditioning and lighting, which are usually left on, could be controlled based on the surrounding environment, such as the outside temperature and sunlight, and the presence or absence of people in the room, it would be possible to significantly reduce energy consumption.

Analyzing electricity usage requires analysis of multiple factors such as the operating status of equipment, temperature, and outside air temperature. In the building management system 10 of this embodiment, trend data can be displayed for energy management. Trend data can collect a large amount of data in units of as little as one second, making it ideal for energy analysis.

Using such an EMS, it is possible to analyze the amount of energy used by energy type and energy over time. Furthermore, it is possible to select equipment and perform settings and display the status in real time.

The aforementioned productivity tool automatically collects information from sensors, switches, and other equipment installed on the same network and stores it in a database (Figure 4). Each piece of setting information can then be efficiently registered in the created database.

Previously, in order to collect information from each device and sensor in a building, such as lighting fixtures, air conditioning, and sanitary equipment, and to display and control current usage, it was necessary to configure each device and its functions one by one.

For example, not only in huge buildings with hundreds of thousands of contact points (monitoring points), but even for a few hundred points, the settings had to be done one by one by hand, which took a lot of time. Furthermore, status management to check the current status of the information also required a lot of effort.

In order to solve these problems, the building management system 10 of this embodiment uses the productivity tools described above. By using the productivity tools, work that previously took tens of days just to set up can now be completed in just a few minutes. Moreover, the data to be registered can be set by downloading it from a remote location. The productivity tools greatly simplify the construction work and also greatly reduce construction costs.

<Level 3: Integrated Controller (Integrated Edge Device)>
Many application-specific systems, such as air conditioning, electricity, sanitation, and central monitoring, are constructed within a building. The integrated controller (integrated edge device 64) in the building management system 10 of this embodiment integrates these application-specific systems and transmits the received information to higher-level systems in sequence via an Internet line (public wireless communication line and public wired communication line) 68. A LAN (local area network, in-house network) is also used as appropriate for transmitting information.

In the building management system 10 of this embodiment, the hardware and software of the integrated controller (integrated edge device 64) are constructed so that one unit has the processing power to manage a building with a floor area of 100,000 square meters. 100,000 square meters is 10 hectares, equivalent to a floor of 316 m x 316 m, or a 40-story building with each floor being 50 m x 50 m. In this way, a considerable scale of management is possible with one integrated controller (integrated edge device 64).

<Level 4: Enterprise Edge Server>
In the building management system 10 of this embodiment, a hierarchy of an enterprise edge server 66 (level 4) is constructed above a micro edge device 60 (level 1), an application edge device 62 (level 2), and an integrated edge device 64 (level 3). All of these devices and servers are configured using computer equipment, but the major difference between them is the performance (processing capacity, processing speed, etc.) as a computer equipment and the usage pattern of memory area.

Conventionally, there were significant restrictions on the number of monitoring points, but the enterprise edge server 66 in the building management system 10 of this embodiment can use unused slots and increase the number of CPUs to deal with insufficient performance due to an increase in the size or number of buildings to be managed. Performance can also be improved by replacing the board with one equipped with a CPU with higher processing power.

Furthermore, a computer device capable of configuring a VM (Virtual Machine) is used as the enterprise edge server 66. By configuring a VM, multiplexing (here, duplication) of the management system is possible.

VMs are isolated from the rest of the system and are built to coexist on the same hardware. VMs allow multiple different operating systems to run simultaneously on a single computing device.

For example, when upgrading a building management system, it may be necessary to continue using old operating systems (OSs) such as Windows NT (registered trademark) or XP, which are not newly introduced these days, even after the upgrade.

In conventional building management systems, the monitoring server is dependent on the OS, so when a higher-level device is changed, all lower-level devices must also be changed to match the higher-level device. For this reason, even if you try to update the system while maintaining at least some of the lower-level devices, you are dragged down by the previous system and need to keep the old OS.

In the building management system 10 of this embodiment, the enterprise edge server 66 can be configured as a virtual server. Therefore, when a new enterprise edge server 66 is introduced, it is possible to run a variety of operating systems in parallel on the enterprise edge server 66. For example, it is possible to run Linux (registered trademark) and Windows NT (registered trademark) in parallel.

Therefore, when upgrading a building management system, it is possible to leave the lower-layer equipment and replace only the upper-layer equipment with new equipment. Moreover, it is possible to build systems that relate to multiple OSs. This idea itself is different from the past and represents a new approach. And because the old OS can be left in the VM, replacing server equipment when upgrading the system becomes much easier than before.

The benefits of using the Enterprise Edge Server 66 are great. Not only does it reduce the size of the equipment that makes it possible to perform repairs at regular intervals (approximately every seven years), it also makes it easier.

Previously, when upgrading a large-scale system, it took a full day to back up, save, and reload the system. Furthermore, because the work had to be done for each server, the entire upgrade process took several days.

In the building management system 10 of this embodiment, such problems are solved by using an enterprise edge server 66, and equipment modifications (replacement, addition, etc.) can be made by hot swapping (with the power on) without stopping the system. In order to make equipment modifications by hot swapping possible, it is possible to make the enterprise edge server 66 redundant by configuring it in a duplicated manner. In this case, one enterprise edge server 66 is operated while the other enterprise edge server 66 is modified.

<Functions of edge devices>
<<Distributed System>>
One of the major features of the building management system 10 according to this embodiment is that it makes it easy to increase the number of monitoring points by appropriately combining wireless communication and Internet communication. Conventional building management systems have a limit on the number of monitoring points, ranging from several thousand to tens of thousands at most. When attempting to advance intelligent building management or multi-building management that manages multiple buildings, the management capacity easily reaches its limit. With conventional building management systems, when introducing a system that exceeds the limit on the number of management points, it was necessary to write a special program and bridge multiple servers.

In the building management system 10 of this embodiment, the enterprise edge server 66 constitutes a virtual server, so it is possible to easily increase processing power by increasing the number of CPUs. This makes it possible to build a huge building management system by utilizing the hard disk (storage means), which can be considered an infinite resource.

Another major feature of the building management system 10 is that it is a distributed system. For example, one server can be distributed to two. Although the server is divided, it is not necessary to collect all the data in one place; the data is distributed and can be retrieved as needed (collected on demand). In other words, there is no need to connect all the servers.

By performing the necessary operations when necessary, it is possible to collect the necessary data from multiple servers. In the building management system 10 of this embodiment, for example, when a command to the effect that "I only want data A, data B, and data C" is entered into a PC or mobile information terminal, the necessary data is output. The building management system 10 of this embodiment operates as if it were being processed by a single computer.

Most conventional building management systems are client-server type and cannot operate in this way. Conventional building management systems cannot be distributed and have had to become large systems. One of the features of the building management system 10 of this embodiment is that it has created a mechanism that overcomes this limitation.

<<Utilizing edge servers>>
Conventional building management systems aggregate data in one server and manage it centrally. This makes the system itself large. However, the building management system 10 of this embodiment decentralizes the system by using edge servers. Although the system is decentralized, it is possible to view the data on demand by entering a command such as "I want to view specific data from the micro edge device 60," for example.

<< Unified Data Format >>
Another feature of the building management system 10 of this embodiment is that all information management is performed in a unified format. As described above, by using the wireless sensor devices 30, data is automatically collected in a unified format. Moreover, the format is common to all of the four types of edge devices described above (the micro edge device 60, the application edge device 62, the integrated edge device 64, and the enterprise edge server 66).

The data format structure handled by the micro edge device 60 (level 1) is the same as that of the higher-level application edge device 62 (level 2), integrated edge device 64 (level 3), and enterprise edge server 66 (level 4). Therefore, the higher-level edge device can take over the data of the higher-level edge device.

In this way, data in a unified format is created, and the created data is utilized for a variety of management items (various applications such as air conditioning, electricity, sanitation, central monitoring, etc.). By utilizing data in a unified format, it becomes possible to build an entirely integrated building management system 10, just as if a desired structure were created by combining building block toys with a common connection structure.

<Utilizing the cloud>
<<Remote monitoring>>
The building management system 10 of this embodiment utilizes the cloud. This allows building supervisors and general users to receive building management services using a public communication network without having to have their own servers or storage devices. One of the reasons for using the cloud in this way is to enable remote monitoring.

However, if digitized data from multiple lower-level devices is sent directly to a higher-level device, the amount of communication traffic will increase on the higher-level device receiving the data, which could result in a slower data processing speed.

According to the inventors' knowledge, when using the cloud for building management, the data that should be uploaded to the cloud from the on-site data (end points of the building management system 10) collected by sensors and switches is, in fact, a few percent (e.g., about 3%) of the total collected data. This few percent is, for example, EMS (energy management system), energy data, and FMS (facility management system). It is possible to perform sufficient building management by simply collecting this data, for example, once every 30 minutes or once every hour.

The data required for building management is static data, rather than data that changes dynamically from moment to moment. For static data, simply collecting and accumulating it at regular intervals is sufficient for building management. For this reason, as described below, building management combines on-premise data collection with data collection from the cloud. Considering what should be uploaded to the cloud to maximize overall performance, a selection is made as to what data to upload to the cloud as static data and what to leave as dynamic data in the application, edge device, or other device.

<<On-premise/Cloud>>
Cloud services are currently the mainstream of information processing services. It is often thought that cloud services are a good way to collect large amounts of data and accumulate big data, but when applied to building management systems, it has been difficult to build an effective building management system even if a huge amount of data is actually collected.

One of the reasons why it was difficult to build an effective building management system was that it was hard to know how to handle the accumulated data, and in some cases, more than 90% of the data that was collected did not even need to be used.

Even if 100% of the data collected on-site (at the end of the building management system 10) is uploaded to the cloud, over 90% of that data will not be used unless some kind of trouble occurs.

Uploading data to the cloud incurs communication costs, CPU usage fees, and requires storage space (also called "usage space") to store the information to be uploaded to the cloud. If storage space large enough to store all generated data is secured, the size of the storage space will not be measured in gigabytes or terabytes, but is expected to reach petabytes or more. Furthermore, the storage capacity of the cloud is huge, and it is natural that maintaining and managing the cloud requires enormous costs.

The building management system 10 of this embodiment therefore makes it possible to build an effective building management system by utilizing edge devices (systems that perform pre-processing on-site) and appropriately using on-premise data processing and cloud services.

In the building management system 10 of this embodiment, not all data is uploaded to the cloud, but selected data is uploaded to the cloud. Under normal circumstances, only static data is selectively uploaded, and only when a certain condition is met (for example, when an alarm is issued), other data (for example, historical data) is used from the on-premise data.

In this way, for example, when an alarm is issued, it is possible to execute a processing program to investigate the cause by referencing on-premise data from the time period when the event that caused the alarm occurred. This also reduces communication volume and storage space, and improves communication speed and response speed.

<< Technology Integration >>
The building management system 10 of this embodiment is equipped with various devices and tools (application software) to utilize collected data in the cloud or on-premise. These devices and tools do not exist separately but work together. These devices and tools are essential for maximizing the performance of the system.

<Central monitoring function>
<<Realizing diverse visualization through the fusion of IT and OT>>
The main purpose of a building management system is to centrally monitor and control the status of the devices installed in a building. Conventionally, such overall management has been difficult. However, the building management system 10 of this embodiment combines various ideas to achieve overall management. For example, regarding the amount of power, the total overall amount for a specified period (designated period) and the total amount for each device are visualized. It is then possible to check matters such as when, where, which device is using how much power, and so on.

<<Visualization of lighting, temperature, humidity, etc.>>
In the building management system 10 of this embodiment, with regard to lighting, in addition to the lighting status, on/off, dimming control status, etc. can be displayed on the screen in a specific manner. Also, with regard to the indoor environment, the indoor CO2 concentration, temperature, humidity, etc. can be displayed on the screen in a specific manner (such as a heat map).

<<Visualization of the environment – trend graph>>
In the building management system 10 of this embodiment, the temperature, humidity, illuminance, etc. can also be displayed on the screen using trend graphs.

<<Usage status and linked applications>>
In the building management system 10 of this embodiment, it is possible to display schedules, operation history, forms, earthquake warning systems, cloud applications, and the like on the screen.

<Remote monitoring function>
<<Cloud monitoring system that enables multi-building management>>
In the building management system 10 of this embodiment, various devices related to air conditioning, lighting, sanitation, alarms, and energy in a building can be monitored and controlled via a mobile information terminal such as a smartphone or tablet. In addition, monitoring and control can be performed via a mobile information terminal from a remote location away from the building.

The mobile information terminal can connect to application software for building management via an installed browser and use the application software. An easy-to-operate, highly responsive management screen is provided via the mobile information terminal's browser.

As mentioned above, only static data is stored in the cloud, and infrequently used dynamic data is placed on edge devices. This means that the cloud uses a small amount of space, reducing costs and improving response. By reducing the amount of data processed, the time required for processing can be reduced. A storage format can be adopted that stores data in a form that is easy to aggregate (small amounts). These factors also improve response.

<<Realizing CBM>>
In multi-building management, where multiple buildings are managed, it is important to know in which building a fault (abnormality) has occurred. Conventionally, constant monitoring has been performed to constantly check for abnormalities. In contrast, the building management system 10 of this embodiment collects data periodically and takes action only when an abnormality occurs, in other words, "preventive maintenance" (CBM: preventive maintenance).
Condition Based Maintenance (BCBM) has been realized.

If an abnormality is discovered based on the data collected periodically, a warning (alarm) is sent to the mobile information terminal. Furthermore, by specifying the building where the alarm occurred and drilling down, it is possible to grasp the situation in more detail even from a remote location. When drilling down, data linked to the attributes of the building where the alarm occurred is selected and various predetermined analyses are carried out.

<Smart Palm (registered trademark) enables monitoring and control from the palm of your hand>
The building management system 10 of this embodiment utilizes the latest technology to realize an intelligent tool for controlling lighting and air conditioning that is suitable for the new era. Smart Palm (registered trademark), which is provided to building managers and general users via a browser, realizes remote control (remote operation) for both lighting and air conditioning on a mobile information terminal, making it possible to control and monitor lighting and air conditioning in an office. Smart Palm (registered trademark) is a tool that provides operability as if the palm of your hand were a switch.
<<Remote monitoring across networks possible>>
In the building management system 10 of this embodiment, by using a mobile information terminal such as a smartphone or a tablet, it is possible to control the building management system from anywhere, without being restricted by restrictions such as location and time.

<<Lighting and air conditioning control>>
In the building management system 10 of the present embodiment, air conditioning, lighting, etc. can be directly controlled using a mobile information terminal. This eliminates the need for personnel in the office to go to a wall switch to change the temperature of the office lighting or air conditioning (air conditioner), for example.

For example, when it comes to lighting, the system has been built so that all the lights on a floor can be turned on/off all at once or in groups. The system has also been built so that the brightness can be adjusted from the comfort of your own hand.

SmartPalm (registered trademark), which is provided via a browser, also has a function that displays electricity usage by floor, group, and lighting, for example. This allows users to check the amount of electricity usage in a given area via a mobile information terminal.

<<Settings and QR Code Generation>>
In the building management system 10 of this embodiment, the lighting and air conditioning (air conditioner) groups that have been set can be changed on a mobile information terminal. This eliminates the need to have an air conditioning contractor or a system contractor change the groups on a weekend when the tenants in the building are closed.

When performing such work, in order to control lighting and air conditioning (air conditioner), for example, a QR code (registered trademark) is distributed to a predetermined group manager in a group of general users for setting management. The QR code (registered trademark) is distributed from the group manager to other group members. The group is made up of a predetermined designated range of general users (which may include building managers and other managers) whose settings are permitted. The range of lighting whose settings are permitted is determined using a lighting design tool described below.

The distributed QR code (registered trademark) is displayed on a display device or mobile information terminal connected to the group member's PC. The QR code (registered trademark) is read by the camera of another group member's mobile information terminal, and the URL, etc. is displayed. The URL, etc. is linked to a setting change site related to the corresponding application edge device 62.

When a group member selects a URL or the like, a settings change site for the corresponding application edge device 62 is displayed on the group member's mobile information terminal. On the settings change site, the group member operates the settings of the facility device for which he or she wishes to change the settings.

In this way, general users can change the groups of lights and air conditioners via a browser without having to install application software for changing the settings.

<<Multiple projects can be set up>>
The settings made via the mobile information terminal can be saved as a project. Multiple projects can be saved. This makes it possible, for example, to change settings for different time periods, or to change lighting or air conditioning groups between weekdays and weekends. In this way, there is no need to install new switches or control panels on the wall to change groups. There is also no need to connect wiring to the switches or control panels and run it inside the walls or under the floor. Furthermore, users can change settings in-house without having to ask a contractor to do the work.

<<Lighting design tool>>
When installing lighting fixtures, important points to consider are how many devices should be installed on a floor and how to group the installed lights with the switches that turn the power on and off. If the design is too detailed, the control will become complicated and many control devices will be required. On the other hand, if the design is too rough, waste will occur, for example, lights will be turned on in places where no one is present.

For this reason, a lighting design tool has been developed as one of the application software in the building management system 10 of this embodiment. For example, the building supervisor connects to the application edge device 62 (level 2) with the lighting design tool and performs design operations within the displayed lighting design tool site.

<Productivity Tools Details>
So far, we have explained the overall picture of the building management system 10 according to this embodiment. In the following, we will focus on the above-mentioned productivity tools and explain the background that led to the development of the productivity tools and the details of the productivity tools.

<<History of Building Management Systems>>
The history of building management systems is surprisingly long, with the concept having been around since the 1950s. Computer-controlled systems have been constructed as intelligent buildings since the mid-1980s.
Because it is an industry with such a long history, the procedures for establishing building management systems have traditionally been rational.
The scope of a building management system includes lighting, air conditioning, sanitation, energy, facility management, etc. These are planned from the design stage of the building, including where they will be placed, what information they will collect, and how they will function.
For example, if it is temperature, the minimum and maximum temperatures to be set are defined, as well as the intervals at which notifications are to be sent.
These detailed regulations are set for each type of device.

<Existence of design documents>
The equipment used in a building is described in detail in the design documents, including what it is, which floor it is located on, where it is installed, and how it is configured. Each piece of equipment is configured based on the design documents, and is also registered in the building management system.
Obviously, the larger the building, the more equipment is installed and the more items need to be configured. Naturally, this configuration work had to be done manually one by one, which was extremely time-consuming.
It's this hassle that productivity tools are designed to solve.

<Differences in protocols>
Building management systems have another challenge: the interconnection of devices.
There are various devices used for building management, but when connecting the devices, there are agreements in place for them to communicate with each other.
Traditionally, each device manufacturer used its own protocols to connect to its own network, but these were not made public, meaning that devices from different manufacturers could not connect to each other.
As a solution to this problem, in the name of openness, several protocols have been established for the purpose of connecting devices made by different manufacturers with each other. Representative ones are Modbus (product name), LonWorks (product name), and BACnet (product name).
LonWorks is a network technology aimed at openness and provided by the American company ECHELON.
BACnet is registered as an international standard based on standards established by ASHRAE (American Heating, Refrigeration and Air Conditioning Industry Association).

<Impact of different protocols>
The aim of this openness initiative was to promote interconnectivity, but one issue that remained afterwards was that even though it was openness, it was only open within the limited scope of each country's own area.
In other words, devices that use the LonWorks or BACnet protocol could be managed by a BACnet-compatible or LonWorks-compatible building management system, but it was difficult to use them in a building management system that simultaneously used both LonWorks and BACnet. The difficulty was that the attributes were different for each protocol, so common data had to be configured, which was a lot of work.
For example, when LonWorks and BACnet protocols were mixed, data conversion and handling between the two was difficult, resulting in a series of problems. Furthermore, it was necessary to process data in an integrated manner, including sequencers and Modbus.
The mixture of these elements posed a challenge for the building management system.

<< Difficulty of setting up >>
<<<<Difficulties in creating a building management system>>>
A building management system is a system that obtains information from various sensors, such as those for lighting, air conditioning, and energy, and displays and controls the status and past trends on a monitoring system.
The analog information coming from the sensor is digitized by the sensor itself, which is equipped with a sequencer or analog/digital conversion function, and sent to the host system. When the host system receives the information from a single sensor, it is necessary to give a unique name to each piece of information that the sensor has and to distinguish them. This is where the need to register various settings arises.

<<<<Understanding the protocol itself>>>
Previously, there were the following issues with setting up the sensors and higher-level devices used:
(a) Data must be structured per protocol.
(b) It was necessary to understand the characteristics of the equipment and the protocols.
(c) Moreover, it was extremely complex and difficult to handle and understand.
(d) If you use it without understanding it or if you follow the rules incorrectly, it will be restricted to not working.
(e) As a result, there were many mistakes due to lack of understanding.

<<<<Existence of dedicated tools>>>>
For each protocol there is a dedicated tool to configure it, or there are multiple dedicated tools, and sometimes there are plugins.
For example, LonWorks has a tool called LonMaker, but LonMaker can only configure LonWorks.
This is a big learning curve, and you have to switch between each protocol one by one.

<<<<Large amount of settings>>>
Each protocol has many settings, and I had to enter settings for them.
The LonWorks SNVT (Standard Network Variable Type) configuration has 219 setting items.
The settings were done manually, and registering them took a lot of time. BACnet also has a large number of settings.
FIG. 5 shows an example of the SNVT correspondence table.

<<Structured body as a solution>>
<<<<Means to achieve this>>>
In order to solve these issues and problems, we have prepared a structured body as a function to convert the data to be handled. This is a function that has not been available in the past.
A "structured entity" in this context refers to data (information) that is predefined and formatted into a certain prescribed structure before being placed in data storage.
In essence, a database is constructed based on the data handled within the building management system, allowing it to be used in an integrated manner within the building management system.

<<<<A system for accepting a variety of data>>>
Specifically, the system determines where data should be stored for each type of device used in the building, such as lighting, sensors, gateways, and controllers, making it easier to set up the devices and also easier to handle the collected data.
In order to be able to handle various types of data other than protocols such as LonWorks and BACnet, 150 protocols are also available.
In this way, we were able to handle a variety of information in a centralized manner.

<<<<Productivity tools for registering data>>>
In addition, as mentioned above, we have prepared a productivity tool that supports various protocols and allows you to enter various settings.
Productivity tools are tools that make configuration easier.
<<<<Productivity Tool Features>>>>
Productivity tools have the following features:
(a) Both LonWorks and BACnet can be registered with one tool.
(b) There is no need to use a gateway to perform external conversion.
(c) The time required to register the setting data is short.
(d) Similar data can be registered by copying the data.

<<<<Configuration diagram example>>>
Here, a relationship diagram (FIG. 7(b)) of the devices, protocols, and productivity tools used in a building management system (for example, the building management system 10) is shown.
The application edge device 62 is connected to gateways, sequencers, and sensors that use various protocols such as LonWorks and BACnet.
The application edge device 62 has a mechanism for displaying the monitoring system.

<<<<Database Improvements>>>
To solve the above problem, we first devised a way to hold the database. Specifically, we solved the difference in protocols by using structures. We then built a database to store data according to those structures.
The database is consolidated into six types: analog input and output, digital input and output, and power integrator and counter. Within this, there is a large database with about 200 items, including upper and lower limits.

<<<<Linking Registers>>>
The productivity tools automate tasks that previously had to be configured manually, such as binding controller registers to application edge devices 62.
Various information is registered in the objects used in the LonWorks protocol. For example, the rules are strictly defined, such as what is sent every second, every number of seconds, or every number of minutes. This information is read and the data is registered in the specified location.

<<<<Data Mapping>>>
The controller has a register that specifies which object number is used in the code. This mapping is the most important thing.
When I need a particular piece of data, I read the register, which is then automatically mapped to my database using web access.
The productivity tools allow you to map LonWorks or BACnet data to web access without having to understand the addresses.

<<<< Extensibility >>>
For new building management devices, we will use Representational State Transfer (REST) and REST APIs to enable data entry in productivity tools.
A function is added so that commands can be sent by command operations of the REST Application Programming Interface (for example, command input operations performed in advance by the building manager using the mobile information terminal 22). This makes it easier to set up new products.
The important thing is to make it possible to exchange data with devices by command. There are five main protocols that can exchange data: Modbus, LonWorks, BACnet, and others.

6(a), 6(b) and 7(a), 7(b) show data mapping in the building management system 10 of the present embodiment so as to be compared with the conventional example.
For example, as shown in Figure 6(a), in the past, information from each sensor was stored in a SCADA (Supervisory Control And Data Acquisition) register, and addresses were manually assigned one by one via a protocol, and the data was mapped to web access.
In contrast, in the mapping according to this embodiment, as shown in Fig. 6(b), the productivity tool converts data of structures for various protocols (here, Modbus structure, LonWorks structure, BACnet structure, etc.) and creates an integrated structure (here, NWC structure, database). The integrated structure is then formatted so that it can be passed to SCADA. Here, "NWC" refers to the applicant of the present invention.

In a conventional building management system, for example, as shown in FIG. 7(a), information from various sensors and the like is collected in a SCADA via various protocols and displayed on a screen.
This meant that information sent via each protocol had to be addressed and mapped directly to SCADA items manually.
In particular, it was necessary to register information for each connected device, and the amount of manual registration work was enormous. Here, "HMI" in Fig. 7(a) is an abbreviation for Human Machine Interface.
In contrast, in the mapping according to the present embodiment, as shown in Fig. 7(b), the productivity tool creates an integrated structure (here, an NWC structure) using structured bodies for various protocols (here, a Modbus structured body, a LonWorks structured body, a BACnet structured body, etc.), and makes it possible to pass the integrated structured body to a higher-level system (here, SCADA). In other words, data is registered in the structured body for each protocol, and then aggregated in the NMC structured body, which is then passed to SCADA, eliminating the need to understand addresses.
Therefore, it is possible to significantly reduce the labor required for data registration. The database can be created not only in the application edge device 62 but also in the integration edge device 64 or enterprise edge server 66.

<< Effects of productivity tools (visual effects) >>
What would happen if there were no productivity tools? First, the setup process would take a lot of time. Second, it would be easier to make mistakes in the setup, which would increase the chances of errors.
One of the features of the Productivity Tool is that you can map without understanding various structures. Until now, when mapping, people had to make decisions. For example, when you said "space temp" (room temperature), you had to remember what it stood for. The Productivity Tool solved this problem. And by making the settings into patterns, you can set them without having to deeply understand the protocol. It has become possible to free people from the difficulty of setting things up.
Furthermore, the settings were made into templates so that it was not necessary to input them one by one manually. Data that had been set once could be used without rewriting or adding anything, such as copying data for each floor. This also freed us from the need to set a large number of settings.
In addition, by preparing as many as 150 different protocols, such as Modbus, LonWorks, and BACnet, and constructing the setting data as a structured body and absorbing the differences between the protocols, it has become possible to interconnect different protocols (absorbing the differences in protocols via a structured body).
In addition, items that previously had to be set manually can now be automatically linked to the controller (register linking), such as how to set the timing of processing and where data is registered.
In addition, when reading data, it is now possible to read data from BACnet, LonWorks, etc., by accessing the web and mapping the data, without having to understand the addresses. As a result, all data settings, which previously had to be made through analog work, can now be processed through digital work.
To summarize these points, the following can be said about the building management system 10 of this embodiment.
(a) We established a centralized management system under multiple vendors.
(b) Both BACnet and LonWorks can be configured using the same tool.
(c) Configuration can be performed without detailed knowledge of the protocol.
(d) Supports over 150 protocols.
(e) Various settings can be used as templates.
(f) By copying and using the settings you have already made, you do not have to set things up from scratch.
(g) By assigning attributes, a screen can be created, and dashboards can also be created one-to-one.
(h) Setup is easy.
(i) The number of cases where the system did not function due to configuration errors has decreased dramatically.
(j) The time required for setup, which previously took days, can now be reduced to just a few hours.

<<Other Effects>>
The productivity tools have some visible benefits, as mentioned above, but their biggest benefit is that they free us from the need to understand multiple protocols.
In the past, it took a considerable amount of time to understand the LonWorks protocol, and people often hesitated to understand BACnet and other protocols.
This invention has also solved this problem.

<<<<Improvement of engineering work>>>
Traditionally, when trying to build a building management system, intermediate tasks such as required specifications, design, equipment selection, ladder creation, operation confirmation, and delivery/construction work (processes) were required.
On the other hand, by using the productivity tools, intermediate steps such as creating ladders are no longer necessary.

<<Examples>>
In one building project, 84 packaged air conditioners are used. Each packaged air conditioner has 16 monitoring points. This means that a total of 16 points x 84 units = 1,344 points must be registered. Previously, these 1,344 points were registered manually, and it took days to set them up. However, by using a productivity tool, the settings can be completed in just 5 to 10 minutes. Moreover, the task of setting up one item and then creating multiple items can be done very quickly.

If you are okay with using the names that the productivity tool automatically assigns to the monitored points, you can finish the setup in no time. In reality, this part takes a little time, since people often give their own names in Japanese to make them easier to understand. Even so, this part is only ancillary to the information setup.
The important thing is to configure the information that defines the sensors attached to the device itself. Productivity tools make this task easy.

<<Digitalization of analog work>>
As described above, productivity tools have digitized work that was previously done in an analog manner, and this is a major advantage of using productivity tools.

Figures 8 and 9 show examples of screens that are displayed when using the productivity tool. These screens can be displayed on a display device connected to the building manager's PC, a mobile information terminal, etc.

Figure 8 (a) shows an example of the initial screen. When you launch the productivity tool, the initial screen shown in Figure 8 (a) is displayed.

Figures 8(b), 9(a) and (b) show example screens when creating a template. Productivity tools have parameters that need to be set as templates, and templates can be called up and registered as needed. In addition, a template that has already been set can be used to set similar parameters.

Figures 8(b), 9(a), and (b) show examples of templates corresponding to various protocols and management systems. Figure 8(b) shows an example of a template for LonWorks (product name), and Figure 9(a) shows an example of a template for BACnet (product name). Figure 9(b) shows an example of a template for SCADA.

Productivity tools have parameters that need to be set as templates, so you can simply call up and register the template as needed (to set it). Also, once a template has been set, it can be used to set similar parameters.

The building management method performed by the building management system 10 according to this embodiment can be considered as a building management method. Also, the computer program executed by the building management system 10 can be considered as a building management program. Furthermore, the building management system 10 can be considered as a building management device.

<Inventions that can be extracted from the embodiments of building management systems>
From the embodiments described above, the following inventions can be extracted.
(1) Multiple types of facility equipment (air conditioners, lighting equipment, doors, sensors such as wireless sensor devices 30, switches, other electrical equipment, etc.) classified into multiple management items (air conditioning, lighting, sanitation, alarms, energy, etc.),
A sensor device (such as a wireless sensor device 30) capable of detecting a plurality of types of detection items (such as temperature, humidity, illuminance, acceleration, and contact),
The system includes at least a first tier device (such as a micro edge device 60), a second tier device (such as an application edge device 62), a third tier device (such as an integrated edge device 64), and a fourth tier device (such as an enterprise edge server 66), which are in ascending order of upper tiers, and a first tier device and a second tier device,
At least one of the management items may be defined as one item system, and multiple item systems (such as an air conditioning-related system 12, a lighting and outlet system 14, a sanitation and water-related system 16, a status and alarm system 18, and an energy system 20) may be defined.
A building management system, wherein the plurality of item systems include at least an air conditioning system, a lighting system, an alarm system, and an energy system,
A plurality of the sensor devices are provided,
A plurality of the sensor devices
A digital information can be output to the first layer device according to at least one wireless communication standard;
A sensor device group is configured across a plurality of the item systems,
The first layer device transmits unified information based on a common communication standard to the second layer device,
The second tier device,
A building management system capable of organizing the information from the first level device into a database as a predetermined structured entity using a productivity tool, which is a specified application software.
(2) When the second hierarchical device is not provided with the third hierarchical device,
When a request for a specific management item (such as air conditioning) is received from a user's terminal device (such as the mobile information terminal 22 or 24) via at least a public wireless communication line (such as the Internet line 68), the system selects pre-processing information (such as the air conditioning temperature and room humidity information) necessary for responding to the user from the information stored in the database,
The building management system described in (1) above provides provided information (such as an air conditioning temperature setting screen that allows the air conditioning temperature to be set by operating a mobile information terminal 22, 24) which is information about the specific management item based on the pre-processing information to the user's terminal device via the public wireless communication line using the common communication standard.
(3) In a case where a plurality of the second hierarchical devices are provided, one third hierarchical device is provided for the plurality of the second hierarchical devices,
When the fourth hierarchical device is not provided, the third hierarchical device
When a request is made from a user's terminal device (mobile information terminal 22, 24, etc.) via at least a public wireless communication line (Internet line 68, etc.) regarding a specific management item (air conditioning, etc.), a request is made to the second layer device to select and send pre-processing information (air conditioning temperature, room humidity information, etc.) necessary for responding to the user from the information stored in the database,
The building management system described in (1) above, in which, based on the pre-processing information sent from the second hierarchical device via the public wireless communication line using the common communication standard, provided information (such as an air conditioning temperature setting screen that allows the air conditioning temperature to be set by operating a mobile information terminal 22, 24), which is information about the specific management item, is provided to the user's terminal device via the public wireless communication line using the common communication standard.
(4) In a case where a plurality of the second hierarchical devices are provided, one third hierarchical device is provided for the plurality of the second hierarchical devices,
When a plurality of the third hierarchical devices are provided, the fourth hierarchical device is provided,
The fourth layer device is
When a request for a specific management item (such as air conditioning) is received from a user's terminal device (such as the mobile information terminals 22 and 24) via at least a public wireless communication line (such as the Internet line 68), a request is made to the second hierarchical device via the third hierarchical device to select and transmit pre-processing information (such as the air conditioning temperature and room humidity information) necessary for responding to the user from the information stored in the database;
The third hierarchical device is
relaying the pre-processing information transmitted from the second layer device via at least the public wireless communication line according to the common communication standard to the fourth layer device;
The fourth layer device is
A building management system as described in (1) above, in which provided information (such as an air conditioning temperature setting screen that allows the air conditioning temperature to be set by operating a mobile information terminal 22, 24), which is information about the specific management item based on the pre-processing information relayed by the third hierarchical device, is provided to the user's terminal device at least via the public wireless communication line using the common communication standard.
(5) A building management method carried out by the building management system described above in (1) to (5).
(6) An invention in which the "building management system" in the above (1) to (5) is replaced with a "building management device."

[Building management facility construction support system 100 according to the embodiment]
<Outline of the building management facility construction support system 100>
The above describes the building management system 10 to be constructed. In the following, a building management facility construction support system 100 suitable for designing a combination of various equipment (building management facility construction) for the above-mentioned building management system 10 will be described.

First of all, the renovation or construction of a building involves a variety of stakeholders, such as the owner, general contractor, design firm, construction company, building management company, etc. Furthermore, as mentioned above, these stakeholders hold discussions (meetings, meetings, consultations, etc.) regarding the selection of various equipment and the installation work related to the various equipment, and building management facilities are constructed. Then, matters such as the type and number of equipment and construction plans are decided, and the purchasing, transportation, storage, and installation work of the equipment are carried out in sequence.

During the process of constructing building management facilities, various documents are created and referred to. The documents that are created or referred to include diagrams and tables such as (1) outline drawings, (2) equipment list, (3) nameplate list, (4) power supply circuit diagram, (5) expansion and connection diagram, (6) terminal arrangement diagram, (7) system configuration diagram, (8) point list, (9) system system diagram, and (10) system function diagram. These diagrams and tables are created as needed at each stage of discussion and construction.

The people involved in the design of building management facilities include, for example, sales staff, development engineers, design engineers, purchasing staff, and construction staff. These staff members usually have varying degrees of knowledge about the technical specifications of the facilities and equipment. Furthermore, these staff members may be knowledgeable about the facilities and equipment of a particular manufacturer, but may not have detailed knowledge about the same type of facilities and equipment of other manufacturers.

In constructing building management facilities, the actual situation is that these personnel hold discussions in stages to select the equipment and decide on its placement. There may also be cases where the equipment to be connected to the selected equipment is selected and its placement is decided. The connections of equipment include mechanical connections, electrical connections, and communication connections (wireless or wired communication connections), etc.

In discussions regarding equipment, the people involved are not always those with detailed knowledge of the technical information (hereafter referred to as "technical specifications") of the equipment being discussed. For this reason, unexpected revisions and redoing of work occurs when constructing building management facilities. For example, when an estimated cost amount agreed upon by people without detailed knowledge of the equipment's technical specifications is later checked by a person with detailed knowledge, it is found to be too low compared to the actual amount required, and the estimate work must be redone. This often happens.

Such situations that require review of the contents of consultations and redoing work have been factors that hinder labor-saving and DX (digital transformation) in the construction of building management facilities. According to the knowledge of the inventors, about 80% of the labor involved in the design and construction of building management facilities is spent on work that hinders labor-saving and DX, as described above. Under these circumstances, the inventors have come to the conclusion that in order to advance labor-saving and DX, it is essential to be able to improve the quality of technical communication among various stakeholders.

The building management facility construction support system 100 according to this embodiment enables the improvement of the quality of technical communication between various parties. As shown in FIG. 10, the building management facility construction support system 100 according to this embodiment includes an equipment information input unit 102, a corresponding information creation unit 104, and a corresponding information output unit 106. Of these, various types of computer equipment can be used as the corresponding information creation unit 104, and details of the corresponding information creation unit 104 will be described later.

As the equipment information input unit 102, for example, an operation input means such as a keyboard, a mouse, or a touch panel can be used. The equipment information input unit 102 may be provided integrally with the correspondence information creation unit 104. The equipment information input unit 102 may include multiple input devices such as a keyboard, a mouse, and a touch panel. Furthermore, the equipment information input unit 102 may be connected to the correspondence information creation unit 104 by wire or wirelessly.

The facility equipment information input unit 102 may be connected to the correspondence information creation unit 104 via a communication network. Examples of communication networks include the Internet, LANs, WANs, public telephone lines, base stations, mobile communication networks, and networks interconnected via gateways, etc. (including so-called clouds).

Various display devices (display devices) can be used as the correspondence information output unit 106. The correspondence information output unit 106 may be provided integrally with the correspondence information creation unit 104. The correspondence information output unit 106 may also be integrated with the facility equipment information input unit 102. Examples of the correspondence information output unit 106 and the facility equipment information input unit 102 integrated together include a device that is equipped with a touch panel and a display, and a device that is capable of switching between a touch panel function and a display function.

The correspondence information creation unit 104 may be a general personal computer (hereinafter referred to as "PC") device, a notebook PC, a smartphone, a tablet terminal, or the like. The correspondence information creation unit 104 includes a control unit 107, a storage unit 108, a communication unit 109, and the like. The storage unit 108 and the communication unit 109 may be external.

Although not shown, the control unit 107 is composed of a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), etc. The CPU of the control unit 107 deploys various computer programs stored in the ROM and the storage unit 108 onto the RAM and executes them. The control unit 107 may be any processing circuit or arithmetic circuit equipped with multiple CPUs, a multi-core CPU, a GPU (Graphics Processing Unit), a microcomputer, volatile or non-volatile memory, etc.

The storage unit 108 is a non-volatile storage unit including semiconductor memory such as ROM or RAM that stores various information, a hard disk drive (HDD), or a solid state drive (SSD). The storage unit 108 stores an operating system program, driver programs, application programs, data, etc., used for processing in the processor (here, the control unit 107).

The program stored in the storage unit 108 may be provided by a non-transitory recording medium (not shown) on which the program is readably recorded. Examples of the recording medium include a portable memory such as a CD-ROM, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a micro SD card, and a Compact Flash (registered trademark). In this case, the control unit 107 reads the program from the recording medium using a reading device (not shown) and installs the read program in the storage unit 108.

The program stored in the memory unit 108 may be provided by communication via the communication unit 109. In this case, the control unit 107 acquires the program through the communication unit 109 and installs the acquired program in the memory unit 108.

The communication unit 109 has an interface circuit capable of communicating with the equipment information input unit 102 and the corresponding information output unit 106. It may be connected to the equipment information input unit 102 and the corresponding information output unit 106 via a communication network such as the Internet.

A CAD (Computer Aided Design) application program is stored in the storage unit 108 of the correspondence information creation unit 104. Various general CAD programs can be used, but in this embodiment, an application program for the "control panel automatic drawing" function described below is added (added in) to the CAD.

Here, the correspondence information creation unit 104 may be configured by a combination of multiple computer devices.

<Arrangement of equipment on layout drawing>
The building management facility construction assistance system 100 according to this embodiment can be used, for example, as follows. For example, assume that a number of parties are discussing the construction of a building management facility. The parties operate the facility equipment information input unit 102, and hypothetically input the types of facility equipment included in the building management facility and the locations of the facility equipment to the correspondence information creation unit 104.

Specifically, for example, information on a layout drawing 110 (layout drawing information) as shown in FIG. 11 is input to the corresponding information creation unit 104 and displayed on the corresponding information output unit 106 (not shown). The layout drawing 110 is created in advance at the design stage of the building. The layout drawing information (layout drawing information) is information (CAD data information) that can be obtained at the same time as the layout drawing 110 is created using CAD.

The layout drawing information includes three-dimensional (XYZ three-axis directions) information relating to the actual dimensions of each part of the room in the building. Note that the layout drawing information may be created using another CAD or another computer device and read into the correspondence information creation unit 104.

Next, the relevant parties place the equipment to be discussed on the layout diagram 110 on the screen (define the location). The example in Figure 11 shows the relevant parties using the layout diagram 110 on CAD to discuss the placement of a multi-sensor (shown as a black block), a gateway (shown as a shaded block), and a CO2 sensor (shown as a white block). Here, the "multi-sensor" corresponds to the wireless sensor device 30 in the building management system 10 (Figures 1 to 9) described above. The "gateway" includes the micro edge device 60 in the building management system 10 (Figures 1 to 9) described above.

The three dashed-dotted circles 111A to 111C shown in FIG. 11 indicate the areas where wireless communication is possible for each gateway (wireless communication possible areas). In CAD, the coordinate values on the XY coordinate system related to the layout diagram 110 are determined by placing the shapes (or symbols) of the multi-sensor and the CO2 sensor on the layout diagram 110.

The coordinate values within any of the circles 111A to 111C are known in advance on the CAD system. Therefore, the gateway to which the multi-sensor or CO2 sensor is connected is automatically determined depending on which of the circles 111A to 111C the multi-sensor or CO2 sensor is placed.

The parties involved will decide on the placement of the gateway, multi-sensors, and CO2 sensors so that each piece of equipment can be used effectively. It is also possible to decide on the placement of the gateway in advance, and then decide on the placement of the multi-sensors and CO2 sensors.

Information on the position of the equipment (here, the gateway, multi-sensor, and CO2 sensor) is stored as three-dimensional information in accordance with its placement on the CAD operation screen. In this case, not only coordinate information (XY coordinates) within the layout diagram 110, but also Z coordinate information can be obtained from information on the number of floors in the building. It is also possible to input not only coordinate information within a plane (X coordinate information and Y axis coordinate information), but also information on the height direction within the building (Z coordinate information). The reference position for the Z coordinate information (position where Z = 0) can be, for example, the floor surface of the relevant floor, a specified position under the floor, or the ground surface.

When the layout of the equipment is finalized on the CAD, information on the equipment to be installed is saved, and information on the equipment to be connected (such as the type of equipment, technical specifications, and number of units) is linked. The linked information is stored in a structuring body (integrated structuring body 206, FIG. 36) to be described later. The structuring body in the building management facility construction support system 100 will be described later.

<Outline of primary equipment information and secondary equipment information>
As described later, the CAD of the correspondence information creation unit 104 can use a function of "automatic control panel drawing." When "automatic control panel drawing" is performed, equipment (hereinafter referred to as "primary equipment") is selected and arranged in the CAD, and technical specification information (a type of primary equipment information) related to the primary equipment and information (secondary equipment information) related to equipment (secondary equipment) that can be connected to the primary equipment are automatically called up.

The technical specifications for the primary equipment (a type of primary equipment information) include information such as dimensional information for each part of the primary equipment, communication standards, etc. For example, if the primary equipment is a gateway (micro edge device 60), the secondary equipment information includes information such as the name, manufacturer name, model number, technical specifications, etc. for each wirelessly connected sensor (such as sensor device 30).

Note that multiple second equipment devices may be connected to one first equipment device. Also, subsequent equipment devices (tertiary equipment devices, quaternary equipment devices, ..., nth-order equipment devices (n is a natural number)) may be connected to a second equipment device.

The primary equipment information and the second equipment information are used in various situations. Details will be described later, but in this embodiment, for example, the primary equipment information and the second equipment information may be called up automatically during the execution of automatic control panel drawing, as shown in Figures 14 to 33 described later.

The primary equipment information and the second equipment information may be automatically called up and used as needed, for example, when creating diagrams or tables such as those shown in Figures 34(a) to (f).

Here, Figures 34(a) to (f) show examples of the "equipment list," the "device type" diagram, the "signal type" diagram, the "power supply system diagram," the "outline drawing," and the "developed connection diagram." Of these, the "equipment list" in Figure 34(a) shows a list of facility equipment used in the building management system 10. If the CAD has a data link function, the "equipment list" can be drawn using the existing functions of the CAD.

The "Device Type" diagram in Figure 34(b) shows the appearance and dimensions of the equipment used in the building management system 10. The "Signal Type" diagram in Figure 34(c) shows the IN/OUT signals of IO (input/output) devices. The "Power System Diagram" in Figure 34(d) shows the layout of the electrical equipment system. The "Outline Drawing" in Figure 34(e) shows the appearance and dimensions of the equipment, and the positional relationship between the device main body (equipment main body) and the operation panel. The "Expanded Connection Diagram" in Figure 34(f) shows the connection status between the equipment.

<Outline of automatic control panel operation diagram>
The automatic control panel drawing, an example of which is shown in Fig. 14 to Fig. 33, is performed by selecting the "automatic control panel drawing" function on the CAD. Fig. 12 shows an example of an operation screen 112 on the CAD. A basic operation menu bar 114 is displayed on the operation screen 112, and the basic operation menu bar 114 displays various buttons such as "home", "insert", "annotation", ..., and "notable application", as well as a "automatic control panel drawing" button.

When the "Control Panel Automatic Drawing" button is selected, the control panel automatic drawing menu bar 116 is expanded and displayed as shown in an enlarged view in FIG. 13(a), and the control panel automatic drawing function (control panel automatic drawing function) is enabled. The control panel automatic drawing menu bar 116 displays multiple (11 in this embodiment) automatic drawing function buttons 118-128. The multiple automatic drawing function buttons 118-128 include the following buttons: "Attribute information setting," "Equipment layout," "Signal type layout," "Unit connection layout," "Power supply system diagram layout," "Expanded connection diagram layout," "ENT edge server/monitoring terminal layout," "Integrated edge level layout," "App edge level layout," "Micro edge level layout," and "Sensor/operation terminal layout."

These automatic drawing function buttons 118-128 are operated to select a function with a displayed name (function name). The functions selectable by the automatic drawing function buttons 118-128 are divided into two groups: the panel drawing group and the system configuration drawing group. The panel drawing group includes six types of functions selectable by the automatic drawing function buttons 118-123: "Attribute information setting," "Equipment layout," "Signal type layout," "Unit connection layout," "Power supply system diagram layout," and "Expanded connection diagram layout."

The system configuration diagram group includes five types of functions that can be selected using the automatic diagram function buttons 124 to 128: "ENT edge server/monitoring terminal placement," "integrated edge level placement," "App edge level placement," "Micro edge level placement," and "sensor/operation terminal placement."

Figure 13(b) shows an overview of the contents of each function selectable by the automatic drawing function buttons 118 to 128. When the "attribute information setting" automatic drawing function button 118 is selected, a function for setting attribute information of placed block figures is enabled. When the "equipment placement" automatic drawing function button 119 is selected, a function for placing block figures for which names need to be set is enabled. When the "signal type placement" automatic drawing function button 120 is selected, a function for placing block figures of signal types that include IO (input/output) patterns is enabled.

When the automatic drawing function button 121 of "Unit connection layout" is selected, a function for arranging unit connections is enabled. When the automatic drawing function button 122 of "Power supply system diagram layout" is selected, a function for selecting, setting, and arranging power supply system devices (block figures) is enabled. When the automatic drawing function button 123 of "Expanded connection diagram layout" is selected, a function for selecting [HUB], [
The function to select, set and place from the [I/F-P] (block figure) is enabled.

When the "ENT/edge server/monitoring terminal placement" automatic drawing function button 124 is selected, the function for selecting and placing the ENT/edge server/monitoring terminal placement is enabled. When the "integrated edge level placement" automatic drawing function button 125 is selected, the function for selecting and placing integrated edge level equipment is enabled. When the "App edge level placement" automatic drawing function button 126 is selected, the function for selecting and placing App edge level equipment is enabled.

When the "Micro Edge Level Placement" automatic drawing function button 127 is selected, a function for selecting and placing Micro Edge Level devices is enabled. When the "Sensor/Operation Terminal Placement" automatic drawing function button 128 is selected, a function for selecting and placing sensor/operation terminal devices is enabled.

<If you select "Attribute information setting">
Among the automatic drawing function buttons 118 to 128 shown in Fig. 13(a), when the automatic drawing function button 118 for "attribute information setting" is selected, the equipment (block figure) for which attribute information is to be set is selected (not shown). By selecting the equipment, an image of the selected equipment is displayed (equipment image 130 is displayed) as shown in Fig. 14. The equipment in this case corresponds to the above-mentioned primary equipment. In Figs. 14 to 33, when a symbol is placed on the drawing screen shown with a black background, the area (rectangular area) around the symbol is displayed inverted white to prevent the symbol from becoming difficult to see.

Then, as shown in FIG. 15, an attribute information setting screen 132 pops up. In the example of FIG. 15, an IP address input field 134 and a description field 136 are displayed on the attribute information setting screen 132. An IP address and description are entered in the IP address input field 134 and the description field 136, as shown in FIG. 16.

In the example of FIG. 16, the value "190.0.2.100" (IP address value) is entered in the IP address input field 134, and the characters "16th floor conference room" are entered in the description field 136. Input to the IP address input field 134 and the description field 136 is performed manually by the relevant person via the facility equipment information input unit 102.

The information input via the equipment information input unit 102 is equipment information. The input of information such as the examples in Figures 14 to 16 is the input of equipment information related to primary equipment.

After inputting information into the IP address input field 134 and the description field 136, the attribute information is saved by selecting the "Save" button (save button 138) displayed on the attribute information setting screen 132. The attribute information here is the attribute information of the equipment (primary equipment) corresponding to the equipment image 130 shown in FIG. 14. The attribute information is information created in the correspondence information creation unit 104 in conjunction with the input of the equipment information described above.

The IP address entered in the IP address input field 134 identifies an individual piece of equipment, similar to the IP address assigned by the building management system 10 described above. Furthermore, in the example of FIG. 16, the content entered in the description field 136 is the name of the room in which the equipment having the IP address entered in the IP address input field 134 is installed.

When the attribute information is set and saved, the attribute information setting screen 132 shown in Fig. 16 is erased, and a screen displaying the facility equipment image 130 remains as shown in Fig. 17. The state in which the display in the example of Fig. 17 is performed appears similar to the state in which the display (Fig. 14) is performed before the attribute information is set, but differs in that the attribute information is saved inside the correspondence information creation unit 104.

<Distinguishing between various types of information>
The attribute information described above is information that can be used to create supplementary information (described later). In this embodiment, as described above, the attribute information is saved by inputting the facility equipment via the facility equipment information input unit 102 and performing a save operation.

Figure 35 shows an overview of the steps for creating and outputting main information. As shown in Figure 35, after equipment information is input via the equipment information input unit 102 (S21), attribute information is saved (S22). Then, corresponding information can be created based on the attribute information (S23).

Correspondence information is a variety of information that can be created based on the input facility equipment information, and is defined in a relatively broad sense. For example, facility equipment information displayed as in the example of FIG. 14, and text displayed in the IP address input field 134 and description field 136 in response to input as in the example of FIG. 15, are included in correspondence information. In addition, the "equipment list" to "expanded connection diagram" in the above-mentioned FIGS. 34(a) to (f) are also included in correspondence information.

Corresponding information also includes additional information. Additional information is information that is automatically created and output based on equipment information (and attribute information). Additional information may be automatically called up as secondary equipment information when primary equipment information is input.

In addition, if the primary equipment and secondary equipment are connected by wire, the additional information also includes information on the length of the connecting wiring. The length information of the wiring can be calculated three-dimensionally, including in the height direction (Z direction), using three-dimensional coordinates in CAD.

Note that the examples in Figures 14 to 17 do not go as far as displaying the additional information in this embodiment, so specific examples of additional information will be described later based on the various examples in Figures 18 to 23.

<If "Device Layout" is selected>
Next, when the automatic drawing function button 119 for "equipment layout" is selected among the automatic drawing function buttons 118 to 128 shown in Fig. 13(a), an equipment selection screen (equipment layout information input screen 142) is popped up as shown in Fig. 18. In the example of Fig. 18, the equipment layout information input screen 142 displays a name column 144, a manufacturer column 146, a model number column 148, and a selection menu column 150.

The name of the equipment to be deployed is entered in the name field 144. In the example of FIG. 19, the relevant person inputs the characters via the equipment information input unit 102, and the characters "ECY-1" are displayed in the name field 144.

The word "Distech" has been entered in the manufacturer column 146. A drop-down menu has been set in the manufacturer column 146. Although not shown in the figure, the name of the manufacturer (manufacturer name, distributor name, etc.) supplying the equipment with the name entered in the name column 144 (here, "ECY-1") is displayed in the drop-down menu.

If there are multiple manufacturers supplying a component device named "ECY-1", the relevant multiple manufacturer names are displayed in a drop-down menu. If there is only one manufacturer supplying a component device named "ECY-1", the relevant one manufacturer name is displayed in a drop-down menu. When the relevant person selects an appropriate manufacturer name from the displayed manufacturer names, the selected manufacturer name is displayed in manufacturer column 146.

When a related party selects a manufacturer name from the drop-down menu via the facility equipment information input unit 102, the manufacturer name is automatically entered into the manufacturer field 146.

In the example of FIG. 19, the model number "ECY-S1000" has been entered in the model number field 148. A drop-down menu is also set in the model number field 148. Although not shown in the figure, model numbers that meet both the name conditions entered in the name field 144 and the manufacturer name conditions displayed in the manufacturer field 146 are displayed in the drop-down menu.

When the relevant person selects a model number displayed in the model number column 148 via the equipment information input unit 102, the selected model number is displayed in the selection menu column 150 below. If there are multiple model numbers that satisfy the conditions in the name column 144 and manufacturer column 146, the multiple applicable model numbers are displayed in the selection menu column 150. If there is only one model number that satisfies the conditions in the name column 144 and manufacturer column 146, the multiple applicable model numbers are displayed in the selection menu column 150. In the example of FIG. 19, there is only one model number that satisfies both conditions.

The model number "ECY-S1000" indicates one of multiple pieces of equipment included in the "ECY-1" equipment. In this way, equipment that constitutes part of an equipment may be referred to as a "constituent device" below. In the example of Figures 18 and 19, the equipment with the model number "ECY-S1000" is a constituent device of the equipment named "ECY-1".

In this way, the component device (here, "ECY-S1000") is linked to the manufacturer's name and model number of that component device in a database that has been created in advance.

The equipment layout information input screen 142 is provided with a layout button 152. When the person concerned selects the model number displayed in the selection menu field 150 via the facility equipment information input unit 102 and selects the layout button 152 with the model number highlighted, the equipment layout information input screen 142 is cleared. Furthermore, a drawing screen such as that shown in FIG. 20 is displayed.

The drawing screen displays a block diagram 154 of the equipment entered in the example of Figure 19. The block diagram 154 reflects the actual dimensions (actual measurements), which are one of the technical specifications of the equipment, and the dimensional relationships of each part are drawn at the same scale. The relevant person drags the block diagram 154 via the equipment information input unit 102 and moves it to the appropriate position.

In the example of Figure 20, the equipment to be installed in "ECY-1" (here, the component equipment "ECY-S1000") is placed below block diagrams 156, 158 relating to the other two equipment devices (component equipment). While looking at the preview screen displaying the block diagrams 156, 158 relating to the other two equipment devices, the person involved inserts (places) it in the appropriate position and finalizes the position of the block diagram 154.

In the example of Figure 20, the insertion position of block diagram 154 relating to the equipment to be installed is displayed as X-axis and Y-axis coordinate values in insertion position display field 160. Furthermore, when previewing as in the example of Figure 20, attribute information of the equipment corresponding to each block diagram 154, 156, 158 is not displayed. Figure 21 shows the state in which the placement of "ECY-S1000" has been completed and "ECY-1" is displayed on the preview screen.

In the examples of Figures 18 to 21, the information (name, manufacturer, model number) entered at the stage of the example of Figure 19 is included in the equipment information. Block diagram 154 displayed at the stage of the examples of Figures 20 and 21 is a diagram reflecting actual size, and corresponds to additional information (a type of corresponding information). Furthermore, the diagram of the combined equipment displayed at the stage of the example of Figure 21 (a diagram of the equipment including block diagrams 154, 156, and 158) also reflects actual size, and corresponds to additional information (a type of corresponding information).

<Configuration for creating supplementary information>
1 to 9, a productivity tool that can eliminate a great deal of work is used. In the building management system 10 according to the present embodiment, the technology related to the productivity tool is applied to generate the supplementary information.

The productivity tools in the building management system 10 described with reference to Figures 1 to 9 automatically collect information on sensors, switches, and each piece of equipment installed on the same network, and store it in a database (Figure 4). Each piece of setting information can be efficiently registered in the created database.

In the building management facility construction support system 100 of this embodiment, a tool that performs the same function as the productivity tool described above can be employed. Specifically, the correspondence information creation unit 104 has the function of a productivity tool in the building management facility construction support system 100. In the correspondence information creation unit 104, information related to various types of communication protocols for opening (hereinafter referred to as "open communication protocols") is collected into a common structured entity (such as a database), and storage destinations and output destinations are assigned. A certain register that is predetermined for each type of information is assigned as the storage destination.

The various open communication protocols include, for example, Modbus (product name), LonWorks (product name), BACnet (product name), and other protocols, as shown in Figure 36. Each of these open communication protocols enables the interconnection of multiple pieces of equipment (gateways, sequencers, sensors, etc.) from different manufacturers.

In the correspondence information creation unit 104, the individual structured bodies (hereinafter referred to as "individual structured bodies") 202 to 205 handled in these open communication protocols are aggregated into a common structured body (integrated structured body) 206. Then, based on the information aggregated in the integrated structured body 206, the incidental information creation unit 105 shown in FIG. 36 extracts the necessary information and creates incidental information, and the created information is output to the correspondence information output unit 106.

The incidental information creation unit 105 is a functional component included in the correspondence information creation unit 104, and is configured by the hardware of the correspondence information creation unit 104 (the control unit 107, the memory unit 108, the CAD application program, etc.).

The correspondence information creation unit 104 performs data mapping in the integrated structure body 206, similar to the productivity tool (FIG. 7(b)) of the building management system 10 (FIGS. 1 to 9). In the example of FIG. 36, data conversion is performed on the structure bodies for each protocol (here, Modbus structure body 202, LonWorks structure body 203, BACnet structure body 204, other structure body 205, etc.) to create an integrated structure body (here, integrated structure body 206, a database). Then, in the integrated structure body 206, the data format is adjusted so that it can be passed to the auxiliary information creation unit 105.

The "structured entity" referred to here refers to data (information, information stored in a database) that is predefined and formatted to have a certain structure before being placed in data storage, both for the individual structured entities 202-205 and the integrated structured entity 206. Furthermore, the integrated structured entity 206 integrates the information compiled by the individual structured entities 202-205 for each protocol into a database so that it can be handled as more versatile information in the building management facility construction support system 100.

In providing the building management facility construction support system 100 with productivity tools in this way, specifically, the location in the structuring body where data is to be saved for each type of facility equipment (lighting, sensors, gateways, controllers, etc.) used in the building is determined, making it easier to set up the equipment. At the same time, it also makes it easier to handle the data that is to be collected.
In order to be able to handle various types of data other than protocols such as LonWorks and BACnet, 150 protocols are also available.
In this way, we were able to handle various types of information in a unified manner. We also resolved the differences in protocols by using a structured body (integrated structured body).
The correspondence information creation unit 104 is a tool for appropriately and easily combining equipment devices in constructing a building management facility.

<When "Signal type layout" to "App edge level layout" is selected>
Specific examples of the case where the automatic drawing function buttons 120 to 126 of "signal type layout" to "App edge level layout" are selected will be omitted.

<When "Micro Edge Level Placement" is selected>
When the automatic drawing function button 127 of "Micro Edge Level Placement" is selected, a device selection screen (system configuration diagram placement information input screen 162) is popped up as shown in Fig. 22. In the example of Fig. 22, a drop-down menu is set in the device column 164 of the system configuration diagram placement information input screen 162.

In the drop-down menu, the person concerned selects a piece of equipment (not shown) displayed in a drop-down menu via the equipment information input unit 102. The selected equipment is displayed in the equipment column 164, as shown in FIG. 23. In the example of FIG. 23, "enocean" is displayed in the equipment column 164.

Next, when the "Next" button (Next button 166) is selected, a device selection screen (gateway device selection screen 168) as shown in FIG. 24 is displayed as a pop-up. In the example of FIG. 24, a drop-down menu is set in the device column 170 of the gateway device selection screen 168, and the relevant person selects the equipment device (not shown) displayed in the drop-down menu via the equipment device information input unit 102, thereby selecting the equipment device. The equipment device selected here is a gateway (gateway device).

The gateway device selection screen 168 has a unit number input field 171. The number of gateway devices is input into the unit number input field 171 by the relevant party via the facility device information input unit 102. FIG. 24 shows a state in which the name of the gateway device has not been input and the number of devices is "0" (zero). FIG. 25 shows a state in which the name of the gateway device is "e-G/W" and the number of devices is "10".

As shown in Fig. 25, when a "Next" button (Next button 172) is selected after inputting the name and number of gateway devices, a device selection screen (sensor device selection screen 174) as shown in Fig. 26 is popped up. In the example of Fig. 26, a drop-down menu is set in the device column 176 of the sensor device selection screen 174, and the relevant person selects a facility device (not shown) displayed in the drop-down menu via the facility device information input unit 102 to select the facility device.

The facility equipment selected here is a sensor (sensor device). In the example of Figure 26, the following options for sensor equipment are displayed: "CO2 sensor," "switch-related," "multi-sensor," "relay circuit-related," "motion sensor," "occupancy sensor," and "illuminance sensor."

In the example of Figure 27, the relevant person has selected "CO2 sensor," "switch-related," "multi-sensor," "relay circuit-related," "human presence sensor," and "occupancy sensor," and the names of the selected equipment devices are highlighted. As shown in Figure 27, after inputting the sensor devices, the Place button 177 is selected and the sensor device selection screen 174 is cleared. Furthermore, a drawing screen such as that shown in Figure 28 is displayed.

The drawing screen displays a block diagram 178 of the gateway device "e-G/W" that was input in the example of FIG. 25. The letters "e-G/W" are displayed within the block in the block diagram 178. In addition, the block diagram 178 includes the letters "enocean" that were displayed in the device column 164 in the example of FIG. 23, and the display "×□□□_□" (displaying the number of units).

The person concerned drags the block diagram 178 via the facility/equipment information input unit 102, and places (inserts) it at an appropriate position and confirms it. In the example of FIG. 28, the insertion position of the block diagram 178 is displayed as coordinate values on the X and Y axes in the insertion position display field 180.

When the position of the block diagram 178 relating to the gateway device is determined, automatic placement of the Micro Edge Level is performed as shown in Fig. 29. In the example of Fig. 29, block diagrams 182 to 187 of the "CO2 sensor", "switch related", "multi-sensor", "relay circuit related", "human presence sensor", and "occupancy sensor" selected in the example of Fig. 27 are displayed.

These block diagrams 182 to 187 relating to the sensor devices are automatically displayed when the placement of the block diagram 178 relating to the gateway device is completed. In the example of FIG. 29, the block diagrams 182 to 187 relating to the sensor devices are displayed in the area adjacent to the block diagram 178 relating to the gateway device.

In the examples of Figures 22 to 29, the information input at the stage of the example of Figure 23 (the information of "enocean" in the equipment column 164) is the equipment equipment information input to the correspondence information creation unit 104. Included in. The information of the equipment for which options are displayed in response to the input in the equipment column 164 (such as the information of the gateway device that is an option) is one type of correspondence information.

Furthermore, the information selected from the options and input at the stage of the example in FIG. 25 (the "e-G/W" information and the "10" information) is included in the equipment information input to the correspondence information creation unit 104. Furthermore, the information on the names of the various sensor devices displayed in the example in FIG. 26 is correspondence information. Furthermore, the information on the names of the various sensor devices selected and placed in the example in FIG. 27 is equipment information.

The block diagram 178 in the example of Fig. 28 is correspondence information in which the information of the gateway device ("e-G/W") in the example of Fig. 25 is treated as facility equipment information. Furthermore, the block diagram 178 in the example of Fig. 28 is supplementary information in which the gateway device is treated as the primary facility equipment and display (the characters "enocean" and the radio wave symbol) according to the technical specification information of the primary facility equipment is added.

In the example of FIG. 29, other block diagrams 182 to 187 added to block diagram 178 are corresponding information in which the information of the gateway device ("e-G/W") in the example of FIG. 25 is used as equipment information. Furthermore, block diagrams 182 to 187 are supplementary information showing secondary equipment (n-th equipment where n=2) that is connected to primary equipment according to the technical specifications.

<If "Sensor/operation terminal placement" is selected>
When the automatic drawing function button 128 of "sensor/operation terminal layout" is selected, an equipment selection screen (system configuration diagram layout information input screen 192) is popped up as shown in Fig. 30. In the example of Fig. 30, a drop-down menu is set in the equipment column 193 of the system configuration diagram layout information input screen 192, and the person concerned selects equipment equipment (not shown) displayed in the drop-down menu via the equipment equipment information input unit 102, thereby selecting the equipment equipment. Then, when the "Next" button (next button 199) is selected, the selected equipment equipment is displayed as in the example of Fig. 31.

Figure 31 shows a state in which the interface device "PAC" has been selected as the selected equipment device. Although not shown in the figure, the selected equipment device is displayed in a display field for selected equipment devices (selected equipment device display field). The selected equipment device display field has a placement button. When the person concerned selects the placement button, the selected equipment device display field is cleared and a drawing screen like the example in Figure 32 is displayed.

A block diagram 194 of "PAC" is displayed on the drawing screen. In the example of FIG. 32, "PAC" is used as an interface for an air conditioner. The letters "PAC_I/F" are displayed within the block in block diagram 194.

Furthermore, other block diagrams 196-198 are connected directly or indirectly to block diagram 194. These block diagrams 196-198 are automatically displayed when block diagram 194 of "PAC" is displayed. Here, each block diagram 196-198 represents an "outdoor unit", an "indoor unit", and a "total heat exchanger", respectively, but at the stage of the example in FIG. 32, no specific letters are displayed, and instead of letters, symbols (here, square symbols) are shown.

While viewing a preview via the facility equipment information input unit 102, the relevant person drags the "PAC" block diagram 194 with the air conditioner block diagrams 196-198 attached, and places (inserts) it at the appropriate position and confirms it. In the example of Figure 32, the insertion position of the block diagram 194 is displayed as coordinate values on the X and Y axes in the insertion position display field 190. Figure 33 shows the state when the placement of the "PAC" has been completed. The words "outdoor unit", "indoor unit" and "total heat exchanger" are displayed inside each of the block diagrams 196-198, respectively.

In the examples of Figures 30 to 33, the information selected at the stage in the example of Figure 31 (the "PAC" information in the equipment column 195) is facility equipment information. In the example of Figure 32, block diagram 194 is corresponding information based on the facility equipment information. Block diagram 194 is also supplementary information to which block diagrams 196 to 198 of the indoor and outdoor units of the air conditioner that are connected according to the technical specifications have been added.

Furthermore, the indoor and outdoor air conditioner units represented by the attached block diagrams 196 to 198 are secondary equipment (n-th equipment, where n=2) with the equipment shown in the connection source block diagram 194 being the primary equipment. Also, block diagrams 196 to 198 relating to the secondary equipment are part of the supplementary information.

<Basic advantages of the building management facility construction support system 100>
According to the building management facility construction support system 100 as described above, information on secondary facility equipment that can be connected according to technical specifications (secondary facility equipment information) is automatically output as supplementary information based on the input of primary facility equipment information input to the correspondence information creation unit 104. Therefore, in discussions between parties who have differing levels of understanding of technical specifications, it is possible to accurately communicate about the connection of facility equipment. Furthermore, it is possible to improve the quality of technical communication between various parties. As a result, appropriate communication between various parties becomes possible.

In addition, according to the building management facility construction support system 100 of this embodiment, the work up to the creation of the board plan can be performed automatically via CAD, so the labor previously required for the creation of the board plan can be significantly reduced, making it possible to save labor. As a result, it is possible to promote DX in the construction of building management facilities.

In addition, information on the connected equipment (first to nth equipment information) is handled by the correspondence information creation unit 104. This eliminates the need for the relevant parties to input equipment information separately for each piece of equipment into each computer device when estimating or purchasing the equipment.

The building management facility construction support system 100 according to this embodiment can be said to promote digital transformation of building management facility construction by horizontally distributing facility equipment information (collecting cross-sectional information) through the integrated structuring body 206. It can also be said that the secondary facility equipment that can be connected to the primary facility equipment is logicized.

In addition, when wireless devices (such as wireless sensors) that are assigned IP addresses as individual identification information are used for the secondary equipment, the building management equipment construction support system 100 according to this embodiment can eliminate the need to design and install wiring, making the labor-saving effect even more pronounced.

<Additional Description of the Building Management Facility Construction Support System 100>
<<1 Additional explanation>>
<<<<1.1 Features of the technology>>>
In the above explanation of the building management facility construction support system 100, one form of CAD usage has been described. In this embodiment, the use of CAD is one means for improving the efficiency of work. In the building management facility construction support system 100, the database (master database, integrated structuring body 206) that adjusts the information of each device plays an even more important role. In this database, various information including zoning, control information, and counting information is stored.

Furthermore, IP addresses, productivity tools, and CAD play major roles in constructing a database. These roles can be summarized as follows, for example:
・The IP address clarifies the segment information (information for identification) of the device.
- Productivity tools are responsible for the unique configuration information for each device.
-CAD automatically passes setting information, which previously had to be set and registered manually, to productivity tools as digitized information when creating drawings.

<<<<1.2 Additional information>>>
The following additional explanation can be broadly divided into three parts.
(1) The first part is about improving the productivity of system design by incorporating design functions into CAD.
(2) The second part is about a structure that stores configuration information and collected data in a database.
(3) Finally, the third part is about productivity tools that make it easy to register configuration information.

An example of a building management system 10 that is supported by the building management facility construction support system 100 has been described with reference to Figures 1 to 9. The equipment configuration in such a building management system 10 can be organized, for example, as shown in the diagram in Figure 37. In the building management system 10 (and the building management facility construction support system 100), each piece of equipment forms a hierarchical structure.

The "equipment" shown in Figure 37 is the "cloud," "application edge device," "micro edge device," "sensor," and "object." Of these, the "cloud" corresponds to the aforementioned cloud that enables remote monitoring of management items.

An "application edge device" corresponds to the application edge device 62. A "micro edge device" corresponds to the micro edge device 60 and functions as a gateway. A "sensor" corresponds to level 0 sensors including the wireless sensor device 30. An "object" corresponds to a heat source or the like detected by a sensor.

<<2. Realization of linking design information (analog information) to setting information (digital information) through the use of CAD>>
The main point realized by using CAD in the building management facility construction support system 100 is that, whereas in the past, "design work" and "setting work" were separated, "doing design work" itself is made to coincide with "doing setting work". As a result, it is possible to improve productivity.

Specifically, the following points (1) to (5) can be said to be realized using CAD.
(1) By assigning IP addresses and pre-registering equipment linked to IP addresses,
(2) It is possible to verify whether the capacity limits and prescribed specifications are met,
(3) The design work allows the creation of cable wiring diagrams,
(4) The setting information essential for the next step, parameter generation, is created here.
(5) In other words, conventional analog information can be digitized.

<<3 Structured body>>
<<<<3.1 Issues that needed to be resolved>>>
In the building management facility construction support system 100 of this embodiment, what can be said throughout the work of design, estimation, configuration, installation, testing, and monitoring and control is that the system is composed of a structuring entity. The reason for constructing a structuring entity in this way is that conventional building management systems (before the provision of the building management system 10 (FIGS. 1 to 9)) had the following problems:
(1) There were many devices used, each with its own specification, and consolidating them required a considerable amount of manual work.
(2) Whenever there was a change in specifications, such as a change in equipment or version, the program had to be rewritten to accommodate the change.
(3) Not only was the number of target devices a problem, but if the network structure of the target was changed, the program had to be reprogrammed.
(4) These factors also meant that the program would need to be reprogrammed if there were changes to the floor or number of floors, etc.

<<<<3.2 Countermeasures>>>
In order to solve these problems, the building management system 10 (FIGS. 1 to 9) takes the following measures.
(1) Even if the type of equipment handled changes, the quantity changes, or the floor or zone changes, the format of the data handled remains the same, eliminating the need to reconstruct the program. Of course, since the structure changes depending on the type of equipment handled, such as lighting, air conditioning, sanitation, and energy, the structure was designed to be able to handle any type of information while taking these factors into consideration.
(2) The sensor section basically digitizes analog information, but the data received by the micro edge device is unified so that it becomes a structured entity as specified by the NWC.
(3) Once the data format has been unified in the NWC structuring body, it can be handled in the same unified format at higher levels (levels above micro edge devices). Moreover, even if the number of floors increases or the number and types of devices handled increase, the data format itself is unified, so it appears as if the amount of data has simply increased.
(4) This has a significant effect, as it no longer requires rewriting the program even if the number of floors, the number of devices, or the number of different types of devices increases.

The building management facility construction support system 100, which was developed to support the construction of such a building management system 10, has an application configured so that a structured body similar to that of the building management system 10 is constructed at the construction support stage. Furthermore, a structured body (such as the integrated structured body 206) created and used in the building management facility construction support system 100 can be inherited and used in the building management system 10. At least a portion of the structured body information linked to at least an IP address can be shared with the building management system 10 being constructed.

<<<<3.3 Database>>>
The data handled by the building management system 10 (FIGS. 1 to 9) and the building management facility construction support system 100 include temperature, air conditioning, lighting, alarms/status, energy, etc. In the building management system 10 (FIGS. 1 to 9) and the building management facility construction support system 100, a mechanism is configured in which these data are organized into a database for each area in a structurant and stored. The format of the data stored in the database is substantially the same regardless of differences in the manufacturer (manufacturer) or vendor (distributor) of the equipment, or the specifications of various information (signal standards, communication standards, OS (operating system), programming language, etc.). For this reason, it is predetermined which area of the database the information should be stored in, regardless of the type of equipment.

Figure 38 shows this diagrammatically. In the example of Figure 38, the corresponding information for "temperature" handled by "device" is stored, for example, in the "Header section", "Device type", "Control information", "Segment data section", "Data section", "Data section", and "False judgment" areas provided in the database. The IP address is stored in the "Device type" area. These areas differ from the example of the database shown in Figure 4, but may be the same as in the example of Figure 4. Also, the example of Figure 38 may be applied instead of the example of Figure 4.

<<<<3.4 How to hold data structure>>>
As a way of holding the data structure (aspects of data storage), for example, for different "device types," it is possible to use information (e.g., "control information") relating to one "device type" as information (e.g., "control information") relating to the other "device type." For example, air conditioning and lighting are different "model types," but common information (e.g., "control information") is set for both. More specifically, when there is no one in the office and the "control information" for the lighting is information (flag) indicating that it is off, that information can be used as the "control information" for the air conditioning, and the set temperature for the air conditioning during heating can be lowered (or raised during cooling).

<<<3.5 Segmentation>>>
Another feature of the building management system 10 (FIGS. 1 to 9) and the building management facility construction support system 100 is that data can be segmented. For example, data can be segmented so that it can be divided by floor or by area (zone) within a floor. In the example of FIG. 39, one floor is divided into six areas (zones A to F). This makes it possible to prevent extra (unnecessary) packets from being sent to unrelated areas (zones) (broadcast restriction).

<<<<3.6 Vertical and horizontal divisions>>>
Previously (before the provision of the Building Management System 10 (FIGS. 1 to 9)), in order to manage data on temperature, air conditioning, lighting, alarms/status, energy, etc., separate management systems were used for each area, and these were managed separately. This was a vertical (or horizontal) division.

In contrast, horizontal (or vertical) division separates the upper and lower hierarchies as shown in Figure 40. This concept is adopted in the building management system 10 (Figures 1 to 9) and the building management facility construction support system 100. Horizontal division corresponds to the hierarchical division of sensors, micro edge devices, application edge devices, and enterprise edge servers in the building management system 10 (Figures 1 to 9) and the building management facility construction support system 100.

Figure 40 corresponds to a diagram in which the "Level 0" hierarchy in Figure 1 is divided into two hierarchical levels: the "Micro Edge Level" and the "Sensor/Operation Terminal." Note that communication between each device may be wireless or wired, or may be selectable and/or compatible.

In addition, the local on-premise data holds over 90% of the total dynamic data, while the cloud holds a few percent of the total static data, which is also a horizontal division. This can be easily achieved in the building management system 10 (Figures 1 to 9) and the building management facility construction support system 100 because of the way the data is structured.

<<4 Productivity Tools>>
<<<<4.1 Issues that needed to be resolved>>>
Although the data format has been unified by constructing a structured body, it is still necessary to register setting data including IP addresses and the like in the devices.

Previously (before the building management system 10 (Figures 1 to 9) was provided), configuration work had to be done manually to match the different specifications of each device, and the more monitoring points there were, the more configuration information had to be created, and on top of that, manual registration had to be done for each device.

In the building management system 10 (Fig. 1 to Fig. 9) and the building management facility construction support system 100, the format of the data to be registered has been standardized by constructing a structured entity (database). Accordingly, a "productivity tool" was developed to simplify the registration process.

<<<<4.2 Creating templates for setting information>>>
Productivity tools make it easy to set the data to be registered for each device. This is achieved by creating a "template" for each device, registering standard setting data, and changing only the parts that need to be changed. This means that, for example, what previously required the registration of 20 settings for one device can now be done once.

Furthermore, previously, if there were, say, 20 settings for each device, then those 20 configuration tasks had to be repeated for each device. In contrast, with the Productivity Tools, standard settings for devices are prepared as templates, and as long as only device-specific configuration information (for example, a name that identifies the device) is initially set, all other information can be copied and used. As a result, the more devices used, the more significantly the time required for configuration work can be reduced.

Furthermore, if designing is done using the CAD of the newly developed building management equipment construction support system 100, configuration data is generated, and this generated configuration data can now be registered for equipment during the design stage.

<<<<4.3 Information to be registered>>>
This is a productivity tool that is provided as a tool for registering settings on devices, and it allows you to efficiently register settings on each device.

For example, for a given multi-sensor (corresponding to the wireless sensor device 30 in the building management system 10 (Figures 1 to 9) described above), in addition to temperature, humidity, illuminance, acceleration, and contact names, tag description, and tag prefix, a profile is selected. In the case of standard specifications, for example, the profile "D2-14-41" shown in the bottom row of Figure 41 is used. As shown in an example in Figure 41, the specifications are patterned to a certain extent, but some items still must be specified.

The information required to be set here is prepared based on the CAD data created in the building management facility construction support system 100 according to this embodiment. Then, by linking with productivity tools, the effort required for data registration can be reduced.

<<5 Function example – Time schedule function>>
<<<5.1 Function Overview>>>
Next, there will be described functions that can be added as standard or options to the building management facility construction support system 100. First, a time schedule function will be described.

For example, a function setting screen is provided in addition to the CAD operation screen. FIG. 42 shows an example of the function setting screen. To enable operations on the function setting screen, a login operation is performed on the login screen, as shown by the block at the top of FIG. 43. The login screen may be a pop-up screen.

Fig. 43 shows the configuration of the hierarchical screens. When the login operation is properly performed on the login screen at the top, the screen transitions to the menu screen. The menu screen is configured to allow the selection of screens such as "Execution schedule", "Group management", "Calendar", "Linked start/stop", "Point setting", "Operation history", "User management", and "Settings".

Of these, the "Execution Schedule" screen allows you to display and set the schedule that will actually be executed by day, as shown in Figure 43. The "Group Management" screen allows you to display and set schedules that will be used as templates for creating execution schedules. It is also possible to set up multiple attachments to be grouped together as a single device group.

On the "Calendar" screen, it is possible to display and set operation patterns, holidays, and seasonal change dates. On the "Linked Start/Stop" screen, it is possible to set start/stop depending on the status of specified equipment. On the "Point Settings" screen, it is possible to set tag information to be used in this system. On the "Operation History" screen, it is possible to display the operation history of this system. On the "User Management" screen, it is possible to add, change, and delete users who have access to this system. On the "Settings" screen, the settings screen for this system is displayed.

When the time schedule function is turned on in the "Group Management" screen described above, the time schedule function becomes available for use. Using the time schedule function, for example, a time schedule for controlling the on/off of air conditioning and lighting is determined.

Conventionally, when trying to implement a time schedule function, not only did one have to program each function individually, but the settings had to be built into the equipment. In contrast, with the building management facility construction support system 100 and the building management system 10 constructed using the building management facility construction support system 100, the data structure in the database allows a function to be operated simply by turning on the flag for the required function.

Figures 44(a) and (b) show display examples related to scheduler settings. In the example scheduler screen of Figure 44(a), a calendar is displayed. In the example scheduler settings of Figure 44(b), a time scheduler related to turning the air conditioning on and off is displayed. Specifically, in the example scheduler settings of Figure 44(b), it is possible to specify (set) the air conditioning to be turned on when a specified temperature is reached, or to be turned off when a specified temperature is reached.

<<<<5.2 Hanging tags>>>
In the building management system 10 designed using the building management facility construction support system 100, when performing maintenance or the like, it is possible to exclude a specific device group from the automatic operation of the schedule. This is expressed as a "tag hanging function" and is enabled by pressing the "enable tag hanging" button. This function is also turned on/off by turning a flag on/off.

<<6 Function example – Demand control function>>
<<<6.1 Function Overview>>>
Next, we will explain the demand control function. The basic charge for electricity used in factories and other places is usually determined by the average power consumption (demand value) over a 30-minute period, and once determined, it cannot be changed for one year. Therefore, in order to reduce electricity bills, the power supply can be automatically turned on and off based on a preset priority order.

This setting itself is performed using demand control software, but the function of issuing on/off instructions to the air conditioning equipment to be controlled can be incorporated as a flag in a specified area of the database (integrated structure 206, FIG. 36). In the building management system 10 designed using the building management facility construction support system 100, such demand control functions and products are provided in an integrated manner, including the micro edge device that performs control, the system that monitors the status, and the control system that operates the control.

Conventionally, these various devices (and software) were separated from each other, making it difficult to connect them together, limiting the scope of coverage, and requiring high implementation costs.

In contrast, the building management system 10 designed using the building management facility construction support system 100 provides a management system (application edge device), control equipment (micro edge device), and software (demand control function) in an integrated manner. In addition, it is possible to easily introduce demand control without special programming, without introducing additional control equipment, and without paying expensive costs.

These functions are achieved by having the following features:
(1) Equipment with a hierarchical structure of micro edge devices and application edge devices.
(2) A structured entity that specifies how a database is held.
(3) Productivity tools that make data setting easier.

<<6.2 Demand menu example>>
Fig. 45(a) shows an example of a demand menu bar displayed when using the demand control function. Fig. 45(b) shows an example of a trend screen, which displays (1) tab menu, (3) demand graph, and (4) daily report, as shown with titles in the figure. Here, in Fig. 45(b), the numbers (1), (3), and (4) in the title are displayed using circled numbers.

Figure 45(c) shows an example of a daily report, in which the (2) information panel is displayed. Here, in Figure 45(c), the number (2) in the title is displayed using a circled number.

<<<<6.3 Structure>>>
46 shows an example of a structure (configuration) for executing a demand control function. Software for demand control (demand control software) is installed in an application edge device 62. Then, demand control of each device (here, air conditioners 1 to n) is performed via the micro edge device 60. In this case, the micro edge device 60 functions as an air conditioning management device.

<Inventions that can be extracted from the embodiments of the building management facility construction support system>
From the embodiments described above, the following inventions can be extracted.
(1) A building management facility construction support system (such as the building management facility construction support system 100) that supports the construction of a building management facility,
A correspondence information creation unit (such as the correspondence information creation unit 104) is provided that is capable of inputting equipment information related to the equipment to be installed (such as the sensor device 30, the micro edge device 60, the IO interface, the indoor unit of an air conditioner, the outdoor unit of an air conditioner, etc.) and outputting correspondence information (such as general information output in response to the input of equipment information) that is previously associated with the equipment information,
The equipment includes at least a primary equipment device (such as a micro edge device 60) and a secondary equipment device (such as a sensor device 30) that can be connected (mechanically, electrically, or communicatively) to the primary equipment device,
The equipment information includes at least primary equipment information related to the primary equipment equipment and secondary equipment information related to the secondary equipment equipment,
The correspondence information creation unit
The first facility equipment information can be manually input (e.g., input via a keyboard or touch panel, etc.),
It is possible to input coordinate information (such as XYZ coordinates) relating to the placement of the first equipment,
outputting information related to the connection of the first facility device with the second facility device as supplementary information of the correspondence information related to the first facility device information (such as information indicating a sensor device connected to a selected gateway);
Individual structured entities (such as individual structured entities 202 to 205) are databases corresponding to a plurality of types of communication standards (such as Modbus (product name), LonWorks (product name), BACnet (product name), and other protocols);
An integrated structure body (such as the integrated structure body 206) which is a database that aggregates information of the individual structure bodies in a predetermined structure,
a building management facility construction support system, wherein the corresponding information creation unit creates the auxiliary information by using information of the integrated structure body,
The building management facility construction support system, in which the integrated structure is taken over and used in the building management facility.
(2) In the building management facility, specific information based on the information aggregated in the integrated structure is output to a public communication line, enabling remote monitoring of the management items from a mobile information terminal via a browser and the public communication line, in the building management facility construction support system described in (1) above.
(3) A building management facility construction support method for supporting the construction of a building management facility (e.g., a building management facility construction support method performed by a building management facility construction support system 100), comprising:
A correspondence information creation unit (such as the correspondence information creation unit 104) is used that can input equipment information related to the equipment to be installed (such as the sensor device 30, the micro edge device 60, the IO interface, the indoor unit of the air conditioner, the outdoor unit of the air conditioner, etc.) and output correspondence information (such as general information output in response to the input of equipment information) that is previously associated with the equipment information,
The equipment includes at least a primary equipment device (such as a micro edge device 60) and a secondary equipment device (such as a sensor device 30) that can be connected (mechanically, electrically, or communicatively) to the primary equipment device,
The equipment information includes at least primary equipment information related to the primary equipment equipment and secondary equipment information related to the secondary equipment equipment,
The correspondence information creation unit
The first facility equipment information can be manually input (e.g., input via a keyboard, touch panel, etc.),
Using a building management facility construction support system capable of inputting coordinate information (such as XYZ coordinates) relating to the arrangement of the primary facility equipment,
The correspondence information creation unit outputs information related to the connection of the first equipment device with the second equipment device as supplementary information of the correspondence information related to the first equipment device information (such as information indicating a sensor device connected to a selected gateway);
The building management facility construction support system comprises:
Individual structured entities (such as individual structured entities 202 to 205) are databases corresponding to a plurality of types of communication standards (such as Modbus (product name), LonWorks (product name), BACnet (product name), and other protocols);
An integrated structure body (such as the integrated structure body 206) which is a database that aggregates information of the individual structure bodies in a predetermined structure,
a corresponding information creation unit creating the auxiliary information by using information on the integrated structure body ,
The building management facility construction support method, in which the integrated structure body is taken over and used in the building management facility.
(4) The primary facility equipment is:
The facility includes a plurality of types of equipment classified into a plurality of management items (air conditioning, lighting, sanitation, alarm, energy, etc.),
The secondary facility device includes a sensor device (such as the sensor device 30) capable of detecting a plurality of detection items (such as temperature, humidity, illuminance, acceleration, and contact),
At least one of the management items may be defined as one item system (such as an air conditioning-related system 12, a lighting and outlet system 14, a sanitation and water-related system 16, a status and alarm system 18, and an energy system 20), and a plurality of the item systems may be defined.
The plurality of item systems include at least an air conditioning system, a lighting system, an alarm system, and an energy system;
A plurality of the sensor devices are provided,
A plurality of the sensor devices
Digital information can be output to the first equipment device according to at least one wireless communication standard;
A sensor device group is configured across a plurality of the item systems,
The building management facility construction support system according to (1) or (2) above, wherein the supplementary information includes information about the sensor device.
(5) The first equipment information and the second equipment information include an IP address that identifies the equipment,
The building management facility construction support system according to any one of (1), (2), or (4) above, wherein the information on the integrated structure body includes the IP address.
(6) A building management facility construction support system as described in (5) above, in which at least a portion of the information of the integrated structure body linked to at least the IP address is shared by the building management system (such as building management system 10) to be constructed.

＜Other＞
It should be understood that those skilled in the art can make various changes, substitutions, and alterations thereto without departing from the spirit and scope of the present invention.

10: Building management system 12: Air conditioning-related system 14: Outlet system 16: Plumbing system 18: Alarm system 20: Energy system 22, 24: Portable information terminal 30: Wireless sensor device 60: Micro edge device 60A: Device group 62: Application edge device 64: Integrated edge device 66: Enterprise edge server 100: Building management facility construction support system 102: Facility equipment information input section 104: Correspondence information creation section 105: Supplementary information creation section 106: Correspondence information output section 116: Control panel automatic drawing menu bar 118-128: Automatic drawing function buttons 202-205: Individual structuring body 206: Integrated structuring body

Claims (3)

A building management facility construction support system for supporting the construction of a building management facility, comprising:
A correspondence information creation unit is provided that is capable of inputting facility equipment information related to the facility equipment to be installed and outputting correspondence information that is previously associated with the facility equipment information,
The facility equipment includes at least a primary facility equipment and a secondary facility equipment connectable to the primary facility equipment,
The equipment information includes at least primary equipment information related to the primary equipment equipment and secondary equipment information related to the secondary equipment equipment,
The correspondence information creation unit
The first facility equipment information can be manually input,
It is possible to input coordinate information relating to the arrangement of the first equipment,
outputting information related to a connection of the first equipment device with the second equipment device as supplementary information of the correspondence information related to the first equipment device information;
An individual structured entity which is a database corresponding to each of a plurality of types of communication standards;
An integrated structuring body which is a database that consolidates information of the individual structuring bodies in a predetermined structure,
a building management facility construction support system, wherein the corresponding information creation unit creates the auxiliary information by using information of the integrated structure body,
The building management facility construction support system, in which the integrated structure is taken over and used in the building management facility. 2. The building management equipment construction support system of claim 1, wherein in the building management equipment, specific information based on the information aggregated in the integrated structure is output to a public communication line, enabling remote monitoring of specific management items from a mobile information terminal via a browser and the public communication line. A building management facility construction support method for supporting construction of a building management facility, comprising:
A correspondence information creation unit is used that can input equipment information related to the equipment to be installed and output correspondence information that is previously associated with the equipment information,
The facility equipment includes at least a primary facility equipment and a secondary facility equipment connectable to the primary facility equipment,
The equipment information includes at least primary equipment information related to the primary equipment equipment and secondary equipment information related to the secondary equipment equipment,
The correspondence information creation unit
The first facility equipment information can be manually input,
Using a building management facility construction support system capable of inputting coordinate information relating to the arrangement of the first facility equipment,
The correspondence information creation unit outputs information related to a connection of the first equipment device with the second equipment device as auxiliary information of the correspondence information related to the first equipment device information;
The building management facility construction support system comprises:
An individual structured entity which is a database corresponding to each of a plurality of types of communication standards;
An integrated structuring body which is a database that consolidates information of the individual structuring bodies in a predetermined structure,
a corresponding information creation unit creating the auxiliary information by using information on the integrated structure body,
The building management facility construction support method, in which the integrated structure body is taken over and used in the building management facility.