Building equipment control system and building equipment control method

Abstract

To provide a building facility control system that can easily collectively set the control of a plurality of apparatuses installed in a building.SOLUTION: A building facility control system comprises: a storage unit that stores a building facility ID specifying a building facility installed in a building and the attribute of the building or building facility, and stores the building facility ID and the attribute in association with each other; an input receiving unit that receives input of the same building facility ID as the building facility ID stored in the storage unit; and a control instruction unit that outputs a control command to the building facility received by the input receiving unit. The building facility control system further comprises: a building facility extraction unit that extracts a building facility ID specifying another building facility including information on the same attribute as that of the building facility specified by the building facility ID received by the input receiving unit; and an output unit that outputs the building facility ID extracted by the building facility extraction unit.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present invention relates to a building equipment control system for collectively setting the control of a plurality of devices separately installed in a plurality of buildings, and a building equipment control method.

Background Art

[0002] As a conventional system for collectively setting the control of a plurality of devices separately installed in a plurality of buildings, the wide area management system of Patent Document 1 is known. For example, in the abstract of the same document, it is described as a problem that "a wide area management system and its program that are highly convenient, highly efficient, low cost, and not restricted to an operation base are provided." As a solution, it is described that "the wide area management system of the present invention includes storage means 111, 112, 113, 114 that store a plurality of input / output points commonly set among a plurality of monitoring / control target devices 105, and a control device 101 that monitors or controls the monitoring / control target devices 105 via a device control device 104. When the control device 101 selects an arbitrary input / output point from the input / output points stored in the storage means 111, 112, 113, 114, a plurality of monitoring / control target devices 105 having the selected input / output point are collectively monitored or controlled via the device control device 104 using the selected input / output point." Also, FIG. 7 of the same document discloses various devices separately installed in Buildings A to D. Thus, Patent Document 1 discloses a wide area management system capable of collectively setting the control of various devices separately installed in a plurality of buildings.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In Patent Document 1, paragraph 0025 of the same document explains that "the door information DB 111 shown in Figure 2 has the following data fields: ..., batch setting enabled / disabled 111b, which indicates whether batch setting by the user using the man-machine device 102 is enabled (flag "1") or disabled (flag "0")..." A flag indicating whether batch setting is enabled or disabled is pre-set for each door to be monitored and controlled. This is also true for the terminal, contact, and machine security information DBs illustrated in Figures 3 to 5 of the same document.

[0005] Furthermore, paragraph 0040 of the same document states that "On the connected device batch setting control selection screen G1, data with the batch setting enabled flag "1" is acquired from the data of door information DB111 (see Figure 2), terminal information DB112 (see Figure 3), contact information DB113 (see Figure 4), and mechanical security information DB114 (see Figure 5). As a result, data of the building name 210 (not shown), equipment type 220, and equipment name 230 (not shown) managed by the access control system S are displayed, and checkboxes 200 are displayed to select one or any number of data for each of these items (equipment shown in one row of the table on screen G1 in Figure 7)." As explained in paragraph 0042, "On the connected device batch setting control selection screen G1, the user checks the Select All Devices checkbox 201 with the mouse if they want to select all the displayed devices, or checks the Select Desired Device Individually checkbox 202 with the mouse if they want to select a specific device from the displayed devices, selects one or more monitoring and control target devices 105 (see Figure 1) that they want to set up and control in batches, and presses the batch setting button 203." Thus, in the system of Patent Document 1, a list of monitoring and control target devices that can be set up in batches is presented to the user, and then batch settings are performed only for any device selected by the user.

[0006] However, since some devices installed in a building may or may not be capable of batch configuration depending on the situation, it was not possible to use the system described in Patent Document 1, which requires setting a flag indicating whether batch configuration is enabled or disabled for each device in advance when controlling this type of device.

[0007] Therefore, the present invention aims to provide a building equipment control system and a building equipment control method that can set the control of equipment installed in a building, taking into consideration various conditions such as the location and use of each building and the type of disaster that has been forecasted or reported. [Means for solving the problem]

[0008] To solve the above problems, the present invention provides a building equipment control system comprising: a storage unit that stores a building equipment ID that identifies building equipment installed in a building, and attributes of the building or building equipment, and stores the building equipment ID and attributes in association; an input receiving unit that receives input of a building equipment ID identical to the building equipment ID stored in the storage unit; and a control command unit that outputs control commands to the building equipment received by the input receiving unit, wherein the system further comprises: a building equipment extraction unit that extracts a building equipment ID that identifies other building equipment having the same attribute information as the building equipment identified by the building equipment ID received by the input receiving unit; and an output unit that outputs the building equipment ID extracted by the previous building equipment extraction unit. [Effects of the Invention]

[0009] According to the building equipment control system and building equipment control method of the present invention, the control of equipment installed in a building can be set considering various conditions such as the location and use of each building, and the type of disaster that has been forecasted or reported. [Brief explanation of the drawing]

[0010] [Figure 1] Functional block diagram of the elevator control system of Example 1. [Figure 2] An example of a customer information database in Example 1. [Figure 3] An example of a login information database for Example 1. [Figure 4] An example of a control menu database from Example 1. [Figure 5A] An example of the attribute information database for Example 1. [Figure 5B] An example of the correspondence between attribute information in the attribute information database of Example 1 and control menu information. [Figure 6] An example of a control command database for Example 1. [Figure 7A] An example of the GUI displayed on customer terminal 3's screen. [Figure 7B] An example of the GUI displayed on customer terminal 3's screen. [Figure 7C] An example of the GUI displayed on customer terminal 3's screen. [Figure 7D] An example of the GUI displayed on customer terminal 3's screen. [Figure 7E] An example of the GUI displayed on customer terminal 3's screen. [Figure 8] Flowchart of elevator control in Example 1. [Modes for carrying out the invention]

[0011] The building equipment control system 1 of the present invention will be described below with reference to the drawings. [Examples]

[0012] First, using Figures 1 to 8, we will describe an example of elevator control system 1A, where the controlled object of building equipment control system 1 is an elevator.

[0013] Figure 1 is a functional block diagram of the elevator control system 1A of this embodiment. As shown here, the elevator control system 1A of this embodiment is communicably connected to an administrator terminal 2, a customer terminal 3, a building equipment control device 4 (elevator control device 4A), an information providing server 5, a building sensor 6 (weight sensor 6A), etc. via a communication network N. The communication network N is, for example, an Internet line, a telephone line, etc., and it doesn't matter whether it is wired or wireless. Hereinafter, after giving an overview of the administrator terminal 2, the customer terminal 3, the elevator control device 4A, the information providing server 5, and the building sensor 6 (weight sensor 6A), the details of the elevator control system 1A of this embodiment will be described.

[0014] <Administrator terminal 2> The administrator terminal 2 is a terminal used by an administrator such as a building equipment maintenance company that performs maintenance management of building equipment. Specifically, it is a personal computer, a smartphone, a tablet, etc. for managing the elevator control system 1A. This administrator terminal 2 is mainly used when newly creating various databases in the elevator control system 1A or editing the data in various databases.

[0015] <Customer terminal 3> The customer terminal 3 is a terminal used by a customer such as a building management company that manages a building. Specifically, it is a personal computer, a smartphone, a tablet, etc. for managing the elevator control device 4A. This customer terminal 3 is mainly used when selecting an elevator to be collectively controlled or causing the selected elevator to execute a predetermined control command. The customer terminal 3 may be given the function of editing various databases in the elevator control system 1A.

[0016] <了 <Elevator control device 4A> The elevator control device 4A is a computer that monitors for malfunctions in elevators installed in the building and controls the elevators in response to control commands from the elevator control system 1A. Although not shown in Figure 1, each elevator control device 4A is connected to the hoisting machine that raises and lowers the elevator car, as well as the elevator car door opening and closing device, etc.

[0017] <Information Provision Server 5> Information server 5 is a server that provides various types of information in response to requests from elevator control system 1A. For example, if information server 5 is the Japan Meteorological Agency's server, it will provide forecast and breaking news information such as weather and earthquakes corresponding to the address of the managed building. If information server 5 is the power company's server, it will provide information such as power outages corresponding to the address of the managed building. If information server 5 is the Ministry of Health, Labour and Welfare's server, it will provide information such as outbreaks of epidemics corresponding to the address of the managed building.

[0018] <Building Sensor 6 (Weight Sensor 6A)> The building sensor 6 is a sensor that provides various measurement information in response to requests from the elevator control system 1A. For example, if the building sensor 6 is a weight sensor 6A installed in an elevator car, it will provide information on the approximate number of passengers (occupancy level) in each elevator car. As is clear from Figure 1, multiple building sensors 6 can be connected to the elevator control system 1A.

[0019] <Elevator control system 1A> The elevator control system 1A is a server that generates control commands to be output to any elevator control device 4A in response to input from a customer terminal 3, etc. It comprises an information input unit 11, a storage unit 12, an information processing unit 13, a recommendation generation unit 14, and a control command unit 15. Specifically, this elevator control system 1A is a computer equipped with hardware such as a CPU or other arithmetic unit, a main memory device such as semiconductor memory, an auxiliary storage device such as a hard disk, and a communication device. The arithmetic unit executes a predetermined program while referring to a database to realize each of the above-mentioned functional units. In the following, the outline of each functional unit will be described while appropriately omitting such well-known technologies.

[0020] <<Information Input Section 11>> The information input unit 11 is a functional unit that registers various types of information input from the administrator terminal 2, information provision server 5, building sensors 6, etc., into an appropriate database in the storage unit 12.

[0021] <<Storage section 12>> The storage unit 12 is a functional unit that stores multiple databases created using the administrator terminal 2. The databases stored here are the customer information database 12a, the login information database 12b, the control menu database 12c, the attribute information database 12d, and the control command database 12e. Each database will be described in turn below.

[0022] The customer information database 12a is a table that manages information such as the address of the building under each customer's jurisdiction. As illustrated in Figure 2, it registers the customer's name, a unique customer ID assigned to each customer to identify them, a unique building ID assigned to each building to identify the building, and the address of each building.

[0023] The login information database 12b is a table that manages login information for connecting each customer's customer terminal 3 to the elevator control system 1A. As illustrated in Figure 3, it stores the customer ID and the password required to connect the customer terminal 3 to the elevator control system 1A. Therefore, the elevator control system 1A only allows communication with the customer terminal 3 when the correct combination of customer ID and password is entered.

[0024] The control menu database 12c is a table that manages the control menus that can be executed for each elevator. As illustrated in Figure 4, it registers the customer ID, building ID, a unique elevator ID assigned to each elevator to identify it, and the control menus that can be executed according to the specifications of each elevator. Among the control menus shown, flood avoidance is a control that stops the elevator car at the top floor or changes the reference floor to the top floor when flooding is expected due to heavy rain, etc. Operation suspension is a control that stops the elevator operation at night or on holidays to save power. Earthquake control is a control that stops the elevator car at the nearest floor when an earthquake early warning is received. Crowding avoidance is a control that warns people to maintain distance from each other using the in-car speaker or in-car display when many people are in the elevator car during an epidemic. Video display is a control that displays a desired video on the in-car display. The control menus managed in the control menu database may be managed in association with the attribute information managed in the attribute information database described later.

[0025] The attribute information database 12d is a table that manages the attributes of buildings and elevators. As illustrated in Figure 5A, it registers customer IDs, building IDs, elevator IDs, control menus, and attribute information. The attribute information includes, for example, the building's purpose, prefecture, municipality, currently declared disasters requiring attention, and the number of passengers, and is updated as needed. The disasters requiring attention are registered as data such as "typhoons / heavy rain," "river flooding," "widespread power outages," "earthquakes," and "epidemics," which are input from various information provision servers 5. In addition to what is shown in the figure, other attribute information such as elevator utilization rate, number of floors, elevator car congestion level, weather information, and event information inside or around the building may also be registered. Event information for office buildings and commercial facilities may include building closing days, and event information for condominiums may include garbage collection schedules and water outage information. Event information may be stored by day of the week, or by day or time. Furthermore, as illustrated in Figure 5B, attribute information items and control menu items may be stored in association. For example, the attribute information to be considered when setting up flood evacuation operation includes information on disasters requiring attention, prefectures, and municipalities, and the relevant attribute information is stored in association. Congestion avoidance operation may be associated with building use and congestion level.

[0026] The control command database 12e is a table that manages control commands entered by customers. As illustrated in Figure 6, it registers the customer ID, building ID, elevator ID, control menu, control command date and time, and the execution result of the control command. The example in Figure 6 shows that when control commands for flood evacuation were issued simultaneously to elevator 001 in building A and elevator 0004 in building C, both located in aa ward, Tokyo, the elevator cars of both elevators moved to the top floor.

[0027] <<Information Processing Unit 13>> The information processing unit 13 includes a screen generation unit 13a that generates a GUI (Graphical User Interface) to be displayed on the customer terminal 3 based on each database in the storage unit 12, an input reception unit 13b that receives input from the customer terminal 3 and activates the building equipment extraction unit 14 according to the command, an output unit 13c that outputs the screen generated by the screen generation unit to the customer terminal 3, and a control command database editing unit 13d that edits the control command database 12e. Details of this information processing unit 13 will be described later.

[0028] <<Recommendation Generation Unit 14>> The recommendation generation unit 14 is a functional unit that, when a customer designates a particular elevator as the destination for a control command, includes an attribute extraction unit 14b that extracts the attributes of that elevator, and a building equipment extraction unit that extracts elevators having the same attributes as those extracted by the attribute extraction unit 14b, and recommends other elevators as candidates for the same control command destination. Details of this recommendation generation unit 14 will be described later.

[0029] <<Control Command Unit 15>> The control command unit 15 is a functional unit that transmits control commands to the elevator control device 4A based on data registered in the control command database 12e, and also acquires the control results from the elevator control device 4A and registers them in the control command database 12e. Details of this control command unit 15 will be described later.

[0030] <GUI transitions during collaboration between elevator control system 1A and customer terminal 3> Next, using Figures 7A to 7E, we will explain the transition of the screen display on the customer terminal 3 when the elevator control system 1A and the customer terminal 3 are working together. In the following explanation, it will be assumed that the data exemplified in Figures 2 to 5A is registered in the various databases.

[0031] Figure 7A shows an example of the GUI 30 displayed on the customer terminal 3's screen after logging into the elevator control system 1A. This GUI 30 lists control menus obtained from the control menu column of the control menu database 12c in the form of buttons. In this example, buttons such as the flood prevention button 31, the operation pause button 32, the earthquake control button 33, the crowd avoidance button 34, and the video display button 35 are displayed. When the customer presses the desired button, the GUI transitions to the next GUI where the target elevator for flood prevention is selected. The following example describes the case where the flood prevention button 31 is pressed and the GUI transitions to the selection GUI for the target elevator for flood prevention.

[0032] Figure 7B shows an example of the GUI 310 displayed when the flood avoidance button 31 is pressed in Figure 7A. This GUI 310 notifies the customer of elevators capable of performing flood avoidance control and allows the customer to select at least one elevator to be controlled. As shown in the figure, the customer name field 311 of the GUI 310 displays the logged-in customer name "xx Management Company", the control menu field 312 displays the control menu "Flood Avoidance" selected by the customer, and the elevator list 313 displays the elevator IDs of elevators equipped with the "Flood Avoidance" function along with the building IDs. The elevator list 313 is provided with checkboxes for selecting elevators to perform "Flood Avoidance" control, and in this example, elevator 001 is selected. The recommendation button 314 is pressed when the customer wishes to receive recommendations from the recommendation generation unit 14, and the execute button 315 is pressed to send a control command to the elevator control device 4A of the selected elevator. Then, when the customer presses the desired button, the system transitions to the next GUI.

[0033] Figure 7C is an example of a GUI 314a for notifying the attribute information used for the recommendation, which is displayed after pressing the recommendation button 314 in Figure 7B. In Figure 7B, the customer selected to take evacuation to the flooded elevator 001, so the recommendation generation unit 14 extracts and notifies the attribute information of elevator 001 from the attribute information database 12d as the attribute information used for the recommendation. For example, the corresponding attribute "flood evacuation" is extracted from the attribute information database 12d in Figure 5B. Next, in the attribute information database 12d in Figure 5A, the building use of building A where elevator 001 is installed is "office building," the location of building A is "Tokyo" and "aa ward," and the disaster of concern corresponding to the control menu "flood evacuation" is "typhoon / heavy rain" or "river flooding." Therefore, the recommendation generation unit 14 extracts these as attribute information to be used for recommendations and displays a GUI 314a as shown in Figure 7C on the display of the customer terminal 3. Then, when the customer presses the confirmation button 314b, the GUI transitions to the next GUI. By using only attribute information associated with control menus, it becomes possible to recommend control menu settings only for the necessary building equipment.

[0034] Figure 7D is another example of the GUI 314a that is displayed after pressing the recommendation button 314 in Figure 7B, for informing the user of the attribute information used for the recommendation. In the example in Figure 7C, all of the attribute information extracted by the recommendation generation unit 14 was used to generate the recommendation, but there may be cases where the customer does not wish to use some of the attribute information. Therefore, in Figure 7D, a checkbox is provided for each attribute information extracted by the recommendation generation unit 14 to allow the customer to select whether or not to use it when generating the recommendation, so that the customer can arbitrarily set which attribute information to use. Accordingly, if the confirmation button 314b is pressed with any of the checkboxes unchecked, the recommendation will be regenerated using only the checked attribute information, and then the GUI will transition to the next GUI. For the items that were unchecked here, the information that associates the control menu information and attribute information as exemplified in Figure 5B may be updated. For example, if the building's use is deemed unnecessary for determining whether to perform flood evacuation operation, and the user unchecks this option, the building's use may be configured so that it is not considered when setting up flood evacuation operation in the future. This configuration allows for updating of attribute information necessary for executing control menus, enabling more accurate recommendations for control menus.

[0035] Figure 7E is an example of the GUI 310 that appears after pressing the confirmation button in Figure 7C or Figure 7D. This GUI 310 is the screen after the recommendation generation unit 14 has added elevator 004 of building C to the list, so the message field 316 displays a message such as "Building selection added by recommendation," indicating that an elevator other than the one selected by the customer has been added.

[0036] If the execution button 315 is pressed directly at the point shown in Figure 7B, the recommendation generation unit 14 will not perform the recommendation. In this case, instead of the GUI 310 shown in Figure 7E, a GUI will be displayed that includes only the elevator 001 selected by the customer in the elevator list 313.

[0037] <Flowchart for elevator control> Next, the details of the elevator control in this embodiment will be explained using the flowchart in Figure 8. Prior to the start of this flowchart, it is assumed that appropriate data entered from the administrator terminal 2, information provision server 5, etc., as illustrated in Figures 2 to 5A, is registered in each database within the storage unit 12 of the elevator control system 1A.

[0038] In step S1, the information processing unit 13 compares the customer ID and password entered from the customer terminal 3 with the login information database 12b. If the combination of customer ID and password is correct, it allows login to the customer terminal 3. Then, the information processing unit 13 generates a GUI for the elevator control menu based on the control menu database 12c and displays it on the display of the customer terminal 3 (see Figure 7A). After that, when the customer terminal 3 inputs the control menu to be executed, the process proceeds to step S2.

[0039] In step S2, the information processing unit 13 extracts elevators that can execute the control menu selected in step S1 based on the control menu database 12c, then generates a GUI for the elevator list 313 and displays it on the customer terminal 3's display (see Figure 7B). In addition to the elevator list 313, the customer terminal 3's display also shows a recommendation button 314 and an execution button 315 (see Figure 7B).

[0040] In step S3, the information processing unit 13 determines whether the recommendation button 314 or the execute button 315 was pressed after at least one elevator ID has been selected from the elevator list 313. If the recommendation button 314 was pressed, the process proceeds to step S4; if the execute button 315 was pressed, the process proceeds to step S11.

[0041] In step S4, the information processing unit 13 activates the recommendation generation unit 14.

[0042] In step S5, the recommendation generation unit 14 refers to the attribute information database 12d and determines whether there is an elevator that has the same attribute information as the elevator selected by the customer in step S3 and belongs to the same customer. If the requirements are met, the unit proceeds to step S6; otherwise, it proceeds to step S7. Note that the attribute information evaluated in this step is limited to that which affects the execution of the control menu selected in step S1, using the information that associates attribute information items with control menu items (Figure 5B), and attribute information that does not affect the execution of the control menu may not be considered.

[0043] In step S6, the recommendation generation unit 14 extracts elevators that meet the requirements of step S5 and notifies the information processing unit 13.

[0044] On the other hand, in step S7, the recommendation generation unit 14 notifies the information processing unit 13 of an error indicating that there are no elevators that meet the requirements of step S5.

[0045] In step S8, the information processing unit 13 updates the elevator list 313 based on the notification in step S6 or step S7. Specifically, if there is an elevator that satisfies the requirements of step S5, the elevator list 313 is updated to consist of the elevator selected by the customer in step S3 and elevators that satisfy the requirements of step S5 (see Figure 7E). On the other hand, if there is no elevator that satisfies the requirements of step S5, the elevator list 313 is updated to consist only of the elevator selected by the customer in step S3.

[0046] In step S9, the information processing unit 13 generates a GUI that presents the attribute information used to update the elevator list in step S8 to the customer, and displays it on the customer terminal 3's display (see Figures 7C and 7D). When the customer determines whether the displayed attribute information is appropriate and presses the confirmation button 314b, the process proceeds to step S10.

[0047] In step S10, the information processing unit 13 displays the elevator list 313 updated in step S8 on the customer terminal 3's display and waits for the customer, after reviewing the updated elevator list 313, to press the execute button 315 (see Figure 7E). Once the execute button 315 is pressed on the customer terminal 3, the process proceeds to step S11. Note that the elevators added in step S8 may include some that the customer wishes to exclude from the control menu selected in step S2. In such cases, the customer can simply uncheck the appropriate checkbox in the elevator list 313 before pressing the execute button 315.

[0048] In step S11, the information processing unit 13 registers the control command information necessary to execute the control menu selected in step S1 on the elevator selected in step S10 into the control command database 12e. The control command information registered in the control command database 12e in this step includes the customer ID, building ID, elevator ID, control menu, and control command date and time, as illustrated in Figure 6.

[0049] In step S12, the control command unit 15 periodically monitors the control command database 12e and detects any newly registered control command information.

[0050] In step S13, the control command unit 15 generates a control command based on the control command information detected in step S12, and transmits the generated control command to the elevator control device 4A corresponding to the elevator ID specified in the control command information.

[0051] In step S14, the elevator control device 4A, having received a control command from the control command unit 15, executes control corresponding to the control menu specified in the control command. If the control is successful, the elevator control device 4A notifies the control command unit 15 of the success as a control result. On the other hand, if the control fails, the elevator control device 4A notifies the control command unit 15 of the failure as a control result.

[0052] In step S15, the control command unit 15 registers the control result received from the elevator control device 4A in step S14 into the control command database 12e (see Figure 6).

[0053] In step S16, the information processing unit 13 periodically monitors the control command database 12e and, if any newly registered control results are found, displays those results on the customer terminal 3's display. This allows the customer to understand the control results for each elevator selected in step S10.

[0054] <Effects of this embodiment> As explained above, the elevator control system 1A of this embodiment automatically extracts other elevators that have the same attribute information as the one elevator designated by the customer for control, taking into account various conditions such as the location and use of each building and the type of disaster that has been forecasted or reported. This makes it possible to easily set up the control of multiple elevators that are distributed across multiple buildings. [Examples]

[0055] Next, as Embodiment 2 of the present invention, an escalator control system 1B in which the controlled building equipment is an escalator will be described. Note that the following description will omit redundant explanations of common points with Embodiment 1, but in order to understand this embodiment, you can refer to Embodiment 1 while substituting the elevator control device in Embodiment 1 with the escalator control device, the elevator ID with the escalator ID, and the elevator control menu with the escalator control menu.

[0056] In the control menu database 12c of Example 1, control menus for elevators included flood evacuation, operation stop, earthquake control, crowd avoidance, and video display (see Figure 4). In contrast, in this embodiment, control menus that can also be implemented for escalators include operation stop and earthquake control.

[0057] This escalator control system 1B also takes into account various conditions such as the location and use of each building, and the type of disaster that has been forecasted or reported, and automatically extracts other escalators that have the same attribute information as the escalator designated by the customer as the target of control. This makes it easy to set up the control of multiple escalators that are distributed across multiple buildings. [Examples]

[0058] Next, as Embodiment 3 of the present invention, an air conditioning control system 1C in which the controlled building equipment is an air conditioner will be described. Note that the following description will omit redundant explanations of common points with Embodiment 1, but in order to understand this embodiment, you can refer to Embodiment 1 while substituting the elevator control device in Embodiment 1 with the air conditioning control device, the elevator ID with the air conditioner ID, and the elevator control menu with the air conditioner control menu.

[0059] In the control menu database 12c of Example 1, control menus for elevators included flood evacuation, operation stop, earthquake control, crowd avoidance, and video display (see Figure 4). In contrast, this embodiment provides operation stop as a control menu that can also be implemented for air conditioners.

[0060] Furthermore, while a weight sensor 6A was used as the building sensor 6 in Example 1, a light sensor 6C that detects the on / off status of the lights near each air conditioner is used in this embodiment. Therefore, instead of the passenger count information registered in the attribute information 12d of Example 1, the on / off status information of the lights detected by the light sensor 6C near each air conditioner is registered in the attribute information 12d of this embodiment.

[0061] This air conditioning control system 1C also takes into account various conditions such as the location and use of each building and lighting on / off information, and automatically extracts other air conditioners that have the same attribute information as the one air conditioner designated by the customer as the control target, making it easy to set up the control of multiple air conditioners distributed across multiple buildings all at once. [Examples]

[0062] Next, as Embodiment 4 of the present invention, a signage control system 1D in which the controlled building equipment is signage will be described. Note that the following description will omit redundant explanations of common points with Embodiment 1, but in order to understand this embodiment, you can refer to Embodiment 1 while substituting the elevator control device in Embodiment 1 with the signage control device, the elevator ID with the signage ID, and the signage control menu with the signage control menu.

[0063] In the control menu database 12c of Example 1, control menus for elevators included flood evacuation, operation stop, earthquake control, congestion avoidance, and video display (see Figure 4). In contrast, this embodiment provides display stop and video display as control menus that can also be implemented with signage.

[0064] Furthermore, while a weight sensor 6A was used as the building sensor 6 in Example 1, a human presence sensor 6D is used in this embodiment to detect the presence or absence of people near each signage. Therefore, instead of the passenger count information registered in the attribute information 12d of Example 1, the attribute information 12d of this embodiment is registered with information on the presence or absence of people detected by the human presence sensor 6D near each signage.

[0065] The signage in this embodiment is a display whose main content is determined according to the building's purpose. For example, if the building is an office building, it may display the names of the companies on each floor or news. If the building is a train station, it may display directions to the platforms for each line or timetables. If the building is a commercial facility, it may display sales information or closing days. If the building is an apartment building, it may display garbage collection days or regular cleaning days. If the building is a hospital, it may display disease prevention measures or closing days.

[0066] This signage control system 1D also takes into account various conditions such as the location and purpose of each building and the detection information from motion sensors, and automatically extracts other signage that have the same attribute information as the one signage that the customer has designated as the control target, making it easy to set up the control of multiple signage installed in multiple buildings all at once.

[0067] It should be noted that the above-described embodiment is merely an example, and is not limited to the above-described equipment when controlling equipment installed in multiple locations collectively. Depending on the equipment to be controlled, attribute information not described in the embodiment may be used to identify the equipment to be controlled collectively. Furthermore, the functional block configurations in the embodiments and modifications described above are merely examples. Several functional configurations shown as separate functional blocks may be integrated, or a configuration represented in one functional block diagram may be divided into two or more functions. Additionally, some of the functions of one functional block may be provided by other functional blocks.

[0068] The embodiments and modifications described above may be combined in any way. Although various embodiments and modifications have been described above, the present invention is not limited to these. Other embodiments that can be conceivable within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention. [Explanation of Symbols]

[0069] 1. Building equipment control system 1A Elevator Control System 11. Information Input Section 12 Storage section 12a Customer Information Database 12b Login Information Database 12c Control Menu Database 12d Attribute Information Database 12e Control Command Database 13 Information Processing Department 13a Screen generator 13b Input reception section 13c output section 13d Database Editorial Department 14 Recommendation Generation Unit 14a Building Equipment Extraction Section 14b Attribute extraction part 15 Control Command Unit 1B Escalator control system 1C Air Conditioning Control System 1D Signage Control System 2 Administrator terminal 3 Customer terminal 4. Building equipment control system 4A Elevator control unit 4B Escalator control device 4C Air Conditioning Control Unit 4D Signage Control System 5. Information provision server 6. Building Sensors 6A Weight Sensor 6C Light Sensor 6D Human Motion Sensor

Claims

1. A storage unit that stores a building equipment ID that identifies building equipment installed in a building, and attributes of the building or the building equipment, and stores the building equipment ID and the attributes in association with each other. An input receiving unit that receives input of a building equipment ID that is the same as any of the building equipment IDs stored in the storage unit, A control command unit that outputs control commands to the building equipment received by the input receiving unit, A facility control system equipped with, A building equipment extraction unit extracts building equipment IDs that identify other building equipment having the same attribute information as the building equipment identified by the building equipment ID received by the input reception unit, An output unit that outputs the building equipment ID extracted by the building equipment extraction unit, In a building equipment control system equipped with, The memory unit stores control menus that are executable controls for the building equipment. The attributes stored in the storage unit have attributes of multiple items, and the control menu stored in the storage unit is stored in association with one or more specific attribute information. The input receiving unit receives a control menu stored in the storage unit, The building equipment extraction unit is characterized by extracting a building equipment ID that identifies other building equipment that has the same attribute as the control menu input in the input reception unit.

2. In the building equipment control system according to claim 1, The aforementioned input receiving unit receives input from the customer's terminal used by the customer. The building equipment control system is characterized in that the output unit displays attribute information used to extract the other building equipment on a customer terminal.

3. In the building equipment control system according to claim 2, It has an output screen generation unit that generates a screen to be output on the customer terminal, The output screen generation unit generates a screen in which the attributes used for extracting building equipment in the building equipment extraction unit can be selected. If some of the attributes displayed on the customer terminal are deselected, the building equipment extraction unit will re-extract the other building equipment using only the attributes that were not deselected. The building equipment control system is characterized in that the storage unit decouples the attribute information from the control menu for the attribute information whose selection has been deselected.

4. In the building equipment control system according to claim 2, The aforementioned storage unit stores a customer ID that identifies the customer, A building equipment control system that extracts building equipment that has the same customer ID as the building equipment entered from the customer terminal.

5. In the building equipment control system according to claim 2, The building equipment is equipped with a control command unit that generates control commands to be transmitted to the building equipment, A building equipment control system characterized in that, when a building equipment output to the customer terminal is selected as the target of centralized control, the control command unit transmits the control command to one building equipment and the other building equipment in a single operation.

6. In a building equipment control system according to any one of claims 1 to 4, A building equipment control system characterized in that the attribute is one of the following: the building's purpose, the building's location, weather information at the location, disaster information at the location, event information within the building, or detection information from sensors installed in the building.

7. In the building equipment control system according to any one of claims 2 to 4, A building equipment control system characterized in that the aforementioned attributes can be edited from an administrator terminal used by an administrator who maintains and manages the building equipment, or from a customer terminal.

8. A building equipment control method for controlling building equipment installed in a building, A first input step involves storing a building equipment ID that identifies building equipment installed in a building, attributes consisting of multiple items relating to the building or the building equipment, and a control menu that is an executable control for the building equipment, and inputting the control menu in association with one or more specific attribute pieces of information. A second input step in which the control menu entered in the first input step is entered, A recommendation generation step extracts the building equipment ID of other building equipment that has the same attribute as the control menu entered in the second input step, A building equipment control method characterized by comprising the following:

Images