Data management systems, management methods, management programs

Abstract

To support routine work related to the operation of a building to be performed by a manager of the building after completion of the building.SOLUTION: A management system (1) comprises: a completion database (3) storing a member ID, member coordinates, and a member attribute with respect to a completion member of a building; an environment database (4) storing an environment acquisition result ID, environment acquisition coordinates, work time, and an environment attribute with respect to environment conditions of the building; a rule database (5) including a rule table (51) storing, with respect to an operation rule of the building, a rule ID of the operation rule, rule attributes of the operation rule, and a rule element of the operation rule, and an object table (52) storing the rule ID and related member attributes of a related member related to the rule ID; an operation database (6) including an operation rule table storing the rule ID, a member list of the related member, and an operation rule element based on the rule element; and an operation rule creating section (7) that creates the operation rule table.SELECTED DRAWING: Figure 1

Description

Technical Field

[0004] , , , ,

[0001] The present invention relates to a system, a method, and a program for maintaining and managing a completed building.

Background Art

[0002] In recent years, in the field of architecture, the use of 3D models called BIM (Building Information Modeling) has been progressing. BIM is a 3D model of a building reproduced on a computer, and it is possible to create 3D models of individual members. Although BIM is being widely used in the building design site (planning, design, equipment design, design analysis, detailed design, construction plan, and component manufacturing), it is said that its use in the building construction site has been delayed. In contrast, the applicant has proposed a technique for using BIM in the construction site as follows. According to Patent Documents 1 to 4, it is possible to create a 3D model (hereinafter referred to as a "construction model") in which information on the construction process is reflected in the design BIM.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the adoption of BIM appears to be lagging behind, not only during the construction phase of a building but also after its completion. After completion, it is necessary to maintain and manage the building and periodically inspect whether it is being operated properly. However, plans for such inspections are sometimes created using the drawings and data from when the building was completed, and problems often arise where the current environmental conditions of the building do not match the completed drawings, making it difficult to create plans or leading to incorrect plans.

[0005] This invention was made in view of these problems, and aims to provide data management to support the routine operations related to the management of a building that are carried out by the building manager after the building is completed. [Means for solving the problem]

[0006] To solve the above problems, a management system in one aspect of the present invention is characterized by comprising: a completion database that stores at least member IDs, member coordinates, and member attributes with respect to completed building components of a building to be managed; an environment database that stores at least environment acquisition result IDs, environment acquisition coordinates, work time, and environment attributes with respect to the environmental conditions of the building, including the completed building components or objects related to the completed building components after completion; a rule database that stores at least the rule IDs, rule attributes, and rule elements of the operation rules of the building; an object table that stores at least the rule IDs and related member attributes of related components related to the rule IDs in order to associate the completed building components, environmental conditions, and operation rules; an operation database that stores the rule IDs, member lists of related components, and operation rule elements based on the rule elements; and an operation rule creation unit that associates the data of the completion database, the environment database, and the rule database to create the operation rule table.

[0007] In the above embodiment, it is also preferable to further include an operation plan creation unit for creating an operation plan using a selection of operation rules, wherein the operation plan creation unit uses the operation rule creation unit to create an operation rule table for each of the selected operation rules' rule IDs, and creates an operation plan table in the operation database that stores the plan ID of the operation plan, the rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rule relating to the rule ID has been carried out or not, and a confirmation date and time that manages the date and time when the inspection has been confirmed.

[0008] In the above embodiment, it is also preferable that the completion database stores the characteristics of the completed components, the environment database stores the characteristics of the environmental conditions, the rule database stores the characteristics of the related components, and the operation rule creation unit creates the component list for the operation rule table from the component characteristics.

[0009] To solve the above problems, a management system in another aspect of the present invention is characterized by comprising: a completion database that stores at least member IDs, member coordinates, and member attributes with respect to completed building components of a building to be managed; an environment database that stores at least environment acquisition result IDs, environment acquisition coordinates, work time, and environment attributes with respect to the environmental conditions of the building, including the completed building components or objects related to the completed building components after completion; a rule database that stores at least the rule IDs, rule attributes, and rule elements of the operation rules of the building; an object table that stores at least the rule IDs and relationship attributes of related components related to the rule IDs in order to associate the completed building components, the environmental conditions, and the operation rules; an operation database that stores the rule IDs, a member list of the related components, and operation rule elements based on the rule elements; and an operation rule operation unit that checks the operation rules using the completion database, the environment database, and the operation rule table.

[0010] In the above embodiment, it is also preferable to further provide an operation plan table and an operation plan operation unit for checking an operation plan that includes a plurality of operation rules, wherein the operation plan table stores the plan ID of the operation plan, the rule ID of the operation rules selected for the operation plan, a plan attribute that manages whether the check of the operation rules of the rule ID has been performed or not, and a confirmation date and time that manages the date and time when the performance of the check has been confirmed, and stores these in the operation database, and the operation plan operation unit lists records that have become inspection days from the environment database based on the inspection frequency information stored in the rule database, and uses the operation rule operation unit to check the operation rules of the records that have become inspection days, and updates the plan attribute of the operation plan table to performed and stores the confirmation date and time for records that do not detect any violations.

[0011] In the above embodiment, it is also preferable to further include a notification management database that stores the rule ID, the notifier's notifier ID, and the notifier's contact information, and when a violation of the operational rule is detected in the inspection, an alert is sent to the notifier based on the rule ID, by referring to the notification management database.

[0012] In the above embodiment, it is also preferable that records whose work time has elapsed for a certain period of time are transferred to a storage device separate from the storage device of the environmental database.

[0013] In the above embodiment, it is also preferable that the data in the environment database is divided into a first table having the environment acquisition result ID, coordinate point ID, and environment acquisition coordinates, and a second table having the environment acquisition result ID, the work time, the environment attributes, and the reference destination, and that the first table is transferred to a storage device other than the storage device of the environment database, the information of the other storage device is registered in the reference destination of the second table, and the data is read from the reference destination as needed.

[0014] In the above embodiment, it is also preferable that the operational rules creation unit outputs a report of the records created in the operational rules table in response to a request from the administrator.

[0015] In the above embodiment, it is also preferable that the operational rules operation unit outputs a report of records of violations checked based on the operational rules table, in response to a request from the administrator.

[0016] In the above embodiment, it is also preferable that the operation plan creation unit outputs a report of the records created in the operation plan table in response to a request from the administrator.

[0017] In the above embodiment, it is also preferable that the operational planning unit outputs a report of records in which violations have been checked based on the operational planning table, in response to a request from the administrator.

[0018] To solve the above problems, a management method in one aspect of the present invention includes a rule database that stores at least the member ID, member coordinates, and member attributes with respect to completed building components of a building to be managed; an environment database that stores at least the environment acquisition result ID, environment acquisition coordinates, work time, and environment attributes with respect to the environmental conditions of the building, including the completed building components or objects related to the completed building components after completion; a rule table that stores at least the rule ID, rule attributes, and rule elements of the operation rules of the building; and an object table that stores at least the rule ID and relationship attributes of related components related to the rule ID in order to associate the completed building components, the environmental conditions, and the operation rules, and transmits and receives information between the rule database and the rule database, and (A1): select one record from the rule ID in the rule database. The method is characterized by having the following steps: (B1): referencing the related member having the rule ID of step (A1) from the object table, and listing the completed member and / or the environmental condition corresponding to the related member attribute of the related member from the completed database and / or the environmental database as a member list of the related member; (C1): repeating step (B1) to list all the corresponding completed member and / or the environmental condition; and (D1): creating an operation rule table by making each member list of the related member listed in steps (B1) and (C1) into a record, along with the rule ID of step (A1) and the operation rule element based on the rule element of the rule ID of step (A1), and storing it in the operation database.

[0019] In the above embodiment, it is also preferable to further include the steps of: (A3): selecting one record from the rule IDs in the rule database in order to create an operation plan using a selection of the aforementioned operation rules; (B3): performing steps (A1) to (D1) with respect to the rule ID selected in step (A3) to create an operation rule table for the rule ID; (C3): repeating steps (A3) to (B3) to create a set of operation rules using the rule IDs necessary for the operation plan; and (D3): with respect to step (C3), creating an operation plan table by making the plan ID of the operation plan, the rule ID, a plan attribute that manages whether the inspection of the operation rule for the rule ID has been performed or not, and a confirmation date and time that manages the date and time when the inspection has been confirmed, one record each, and storing it in the operation database.

[0020] To solve the above problems, a management method in another aspect of the present invention includes a completion database that stores at least member IDs, member coordinates, and member attributes with respect to completed building components of a building to be managed; an environment database that stores at least an environment acquisition result ID, environment acquisition coordinates, work time, and environment attributes with respect to the environmental conditions of the building, including the completed building components or objects related to the completed building components after completion; a rule database that stores at least a rule ID of the operation rules, rule attributes of the operation rules, and rule elements of the operation rules with respect to the building's operation rules; an object table that stores at least a rule ID and relational attributes of the relevant components which are the environmental conditions related to the operation rules in order to associate the environmental conditions with the operation rules; and an operation database that stores a rule ID, a member list of the relevant components, and operation rule elements based on the rule elements, and transmits and receives information between the operation database and the operation database, and (A2): a step of listing specific records from the environment database, and (B2): a step of extracting from the operation rule table the records listed in step (A2) (C2): A step of extracting records that have the relational member relating to the environmental attribute of the extracted records; (D2): A step of further extracting records from the records extracted in step (B2) that have the relational member that is paired with the member list; (E2): A step of repeating the extraction in step (C2) for the number of records extracted in step (B2); (F2): A step of listing records from the environment database that have a work time ±N seconds after the work time in step (A2); (G2): A step of extracting records from the selected records that have the same environmental attributes as in step S(B2); (G2): A step of calculating the distance between the environmental acquisition coordinates in step (A2) and step (F2); (H2): A step of calculating the movement speed from the difference in work time between step (A2) and step (E2) and the distance in step (G2); (I2): A step of detecting whether the movement speed violates the conditions described in the operation rule elements of the operation rule table; (J2): For the records extracted in step (D2),The present invention is characterized by having a step of repeating the above steps (E2) to (I2) and performing an inspection.

[0021] In the above embodiment, it is also preferable to further include an operation database that stores an operation plan table which stores an operation plan table that stores an operation plan ID of the operation plan, a rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rule of the rule ID has been performed or not, and a confirmation date and time that manages the date and time when the performance of the inspection was confirmed, in order to inspect an operation plan which includes a plurality of operation rules, and an operation database which stores an operation plan table which stores an operation plan ID of the operation plan, a rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rule of the rule ID has been performed or not, and a confirmation date and time that manages the date and time when the performance of the inspection in step (B4) was confirmed, and to send and receive information, and (A4): a step of listing records from the environment database in which the work time has become an inspection date by comparing it with the inspection frequency stored in the rule database, (B4): a step of performing steps (A2) to (I2) with respect to the records listed in step (A4) to detect a violation, and (C4): a step of setting the plan attribute of the operation plan table to "performed" for records in which no violation was detected in step (B4), and storing the date and time when the inspection in step (B4) was performed as the confirmation date and time.

[0022] In order to solve the above problems, another aspect of the management method of the present invention relates to the completed members of a building to be managed, and at least includes a completed database that stores at least member ID, member coordinates, and member attributes, and the completed members after completion or objects related to the completed members. Regarding the environmental situation of the building, at least an environmental database that stores environmental acquisition result ID, environmental acquisition coordinates, working time, and environmental attributes, and regarding the operation rules of the building, at least a rule table that stores the rule ID of the operation rules, the rule attributes of the operation rules, and the rule elements of the operation rules, and in order to associate the completed members, the environmental situation, and the operation rules, at least an object table that stores the rule ID and the relationship attributes of the related members related to the rule ID, a rule database comprising the same, an operation database comprising an operation rule table that stores the rule ID, the member list of the related members, and the operation rule elements based on the rule elements, and information is transmitted and received to perform (A2´) a step of listing up specific records from the environmental database, (B2´) a step of extracting, from the operation rule table, records having the related members regarding the environmental attributes of the records listed up in the step (A2´), (C2´) if there is a record among the records listed up in the step (A2´) whose environmental acquisition coordinates do not satisfy the conditions described in the operation rule elements of the operation rule table in the step (B2´), a step of extracting the corresponding code, (D2´) a step of repeating and inspecting the steps (B2´) to (C) for the records listed up in the step (A2´), and (E2´) a step of detecting the corresponding records detected in the steps (C2´) to (D2´) as violations, and is characterized by having the same.

[0023] In the above aspect, further, in order to check an operation plan including a plurality of the above operation rules, a plan ID of the operation plan, the rule ID selected in the operation plan, a plan attribute for managing whether the check of the operation rule of the rule ID has been performed or not, and a confirmation date and time for managing the date and time when the check has been confirmed are stored, and an operation database that stores an operation plan table, transmits and receives information, and (A4´): from the environment database, list up records in which the working time is a check date as compared with the check frequency stored in the rule database; (B4´): for the records listed up in the step (A4´), perform the steps (A2´) to (E2´) to detect a violation; (C4´): for records in which no violation is detected in the step (B4´), set the plan attribute in the operation plan table to "completed" and store the date and time when the check in the step (B4´) was performed as the confirmation date and time. It is also preferable to have these steps.

[0024] In the above aspect, further, a notification management database that stores the rule ID, a notifier ID of a notifier, and a contact address of the notifier, transmits and receives information, and after the step of detecting the violation, for the operation rule in which the violation has been detected, based on the rule ID, refer to the notification management database and transmit an alert to the notifier. It is also preferable to have this step.

[0025] It is also preferable to have a management program characterized in that the management method described in the above aspect is described in a computer program and made executable.

Effect of the Invention

[0026] According to the data management system, management method, and management program of the present invention, after the completion of a building, data management for supporting routine operations related to the operation of the building performed by the building administrator can be performed.

Brief Description of the Drawings

[0027] [Figure 1]This is a block diagram of the configuration of the management system 1 according to the first embodiment of the present invention. [Figure 2] This figure shows an example of the completed building database 3 in the management system 1. [Figure 3] This figure shows an example of the environment database 4 in the management system 1. [Figure 4] This figure shows an example of the rule database 5 in the management system 1. [Figure 5] This figure shows an example of the operational database 6 in the management system 1. [Figure 6] This is a flowchart of the management method according to the first embodiment of the present invention. [Figure 7] This is a block diagram of the configuration of the management system 1' according to a second embodiment of the present invention. [Figure 8] This figure shows an example of the notification management database 9 in the management system 1'. [Figure 9] This is a flowchart of a management method according to a second embodiment of the present invention. [Figure 10] Figure 9 is a diagram illustrating the workflow for the management method. [Figure 11] This is another flowchart of the management method according to the second embodiment of the present invention. [Figure 12] Figure 11 is a diagram illustrating the workflow of the management method. [Figure 13] This is a block diagram of the configuration of the management system 10 according to the third embodiment of the present invention. [Figure 14] This is a flowchart of a management method according to a third embodiment of the present invention. [Figure 15] This is a block diagram of the configuration of the management system 10' according to the fourth embodiment of the present invention. [Figure 16] This is a flowchart of the management method according to the fourth embodiment of the present invention. [Figure 17] This is an illustrative diagram of a data compression process according to a modified embodiment of the present invention. [Modes for carrying out the invention]

[0028] Next, preferred embodiments of the present invention will be described with reference to the drawings. The same or equivalent components, members, and processes shown in each drawing will be denoted by the same reference numerals, and redundant descriptions will be omitted as appropriate.

[0029] <First Embodiment> Creation of Operating Rules (Management system configuration) Figure 1 is a block diagram of the configuration of a management system 1 according to the first embodiment of the present invention. The management system 1 is a system for creating "operational rules" (described later). The management system 1 comprises an input / output device 2, a completion database 3, an environment database 4, a rule database 5, an operation database 6, and an operation rule creation unit 7.

[0030] Input / output device 2 is a general-purpose personal computer or tablet terminal, etc., equipped with at least an arithmetic unit, a storage unit, a communication unit, a display unit, and an operation unit, and can be operated by an administrator.

[0031] The operational rules creation unit 7 (hereinafter also referred to as the functional unit) is composed of electronic circuits such as a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), and a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array). The functional unit may be configured either within the input / output device 2 or with other external hardware / software. In the latter case, the functional unit can send and receive information with the input / output device 2 via a communication network.

[0032] The completion database 3, the environment database 4, the rule database 5, and the operation database 6 are stored in the same or different storage devices (such as server computers) configured to communicate via a communication network. The storage devices are capable of communicating with the functional units and sending and receiving information with them.

[0033] (Completion Database) The Completion Database 3 stores data on the building components (hereinafter referred to as "Completion Components") of the buildings under management at the time of completion. As shown in Figure 2, the Completion Database 3 includes a Completion Components Table 31 that associates the following information with each Completion Components: identification information (Component ID), coordinates (Component Coordinates), information on the attributes of the Completion Components (walls, slabs, doors, fire extinguishers, etc.; hereinafter referred to as "Component Attributes"), and information on the characteristics of the Completion Components (non-combustible materials, combustible materials, hazardous materials, etc.; hereinafter referred to as "Component Characteristics"). The Component ID is uniquely set for, for example, the Completion Components that make up a room, such as Wall A, Wall B, Wall C, Wall D, Slab (Floor) A, Slab (Ceiling) B, Door A, Door B, etc. Component Attributes are mandatory items, while Component Characteristics are optional and desirable (if present, information can be extracted based on characteristics).

[0034] The completed component table 31 can be created with respect to component coordinates from the coordinates in the completed drawings or coordinate data measured by measuring instruments such as scanners. However, it is preferable that it be created from the "design modification database" disclosed in Patent Document 1, the "modified construction plan database" disclosed in Patent Document 2, or from the "construction model" created by the work management system disclosed in Japanese Patent Application Publication No. 2021-173727 (hereinafter referred to as the "tool work management system") and the construction model creation system disclosed in Japanese Patent Application Publication No. 2022-6508 (hereinafter referred to as the "tool construction model creation system") proposed by the applicant. When the completed component table 31 is created from these construction models, it can store information from the "completed model" (construction model at the time of completion; a 3D model of the building at the time of completion, reproduced on a computer, with data that allows each completed component to be created as a 3D model; the 3D model also includes the shapes of surfaces, lines, and points) that has been inherited from the 3D model of each component of the construction model, such as component shape, component coordinates, component attributes, component characteristics, manufacturer, and price.

[0035] (Environmental Database) Environmental Database 4 continuously stores data on the "environmental conditions" of the buildings under management after their completion. In this specification, the term "environmental conditions" refers collectively to the completed building components and objects related to those components (anything other than the completed components that has a coordinate relationship with the completed components). As shown in Figure 3, the environmental database 4 includes an environmental status table 41 that associates environmental status identification information (environmental acquisition result ID), environmental status coordinates (environmental acquisition coordinates), information about the measuring instrument used to acquire the environmental status (camera, scanner, total station, tool, etc.) (environmental acquisition processing), information about the time (year, month, day and hour, minute, second) when the environmental status was acquired (work time), information about the attributes of the environmental status (wall, slab, door, fire extinguisher, etc. If a component ID from the completed component table 31 is assigned to the environmental acquisition coordinates, the component ID is also included. Hereafter referred to as "environmental attributes." Environmental attributes include not only the attributes of completed components but also the attributes of objects related to completed components (obstacles / moving objects (people / cars, etc.))..) and information about the characteristics of the environmental status (non-combustible materials, combustible materials, hazardous materials, etc. Hereafter referred to as "environmental characteristics.") Environmental attributes are mandatory items, but environmental characteristics are optional items that are preferable if present (if present, information can be extracted based on the characteristics). The environmental acquisition process is also a desirable optional item (if present, it allows for information extraction by environmental acquisition equipment). Furthermore, if the same environmental attribute is assigned to environmental attributes of different environmental acquisition result IDs, the environmental status table 41 may store identification information (attribute ID) for relating them by environmental attribute.

[0036] The environmental conditions table 41 can be created from coordinate data obtained from measuring instruments such as cameras, scanners, and total stations for environmental coordinate acquisition, and from known image recognition means (such as machine learning classifiers) for environmental attributes and characteristics. Preferably, by using the technology disclosed in Patent Document 3 to determine whether the coordinates (target points) acquired by the measuring instruments are the coordinates of completed members or objects related to completed members (shape calculation members), and by using the aforementioned "tool work management system" and "tool construction model creation system," all items of environmental coordinate acquisition, environmental acquisition processing, work time, environmental attributes, and environmental characteristics can be automatically created.

[0037] (Rule Database) The rule database 5 stores data on laws and / or rules set by the building manager (hereinafter referred to as "operational rules") necessary for the operation of the building under management. The rule database 5 includes at least a rule table 51 that associates operational rule identification information (rule ID), operational rule attributes (rule attributes), and operational rule elements (rule elements), as shown in Figure 4. The rule ID is set in the inspection items of the operational rules, for example, "Do not run in the corridors" for school rules, or "Fire extinguishers must be within 20m of the building" and "Fire equipment must not be damaged" for fire safety regulations. The rule attribute is an attribute of the operational rule, for example, fire safety regulations, evacuation safety verification methods, disaster prevention management, school rules, etc. The rule element is a condition element within the inspection items of the operational rules, and is set as "4m / s or more" for the inspection item "Do not run in the corridors," or "within 20m" for the inspection item "Fire extinguishers must be within 20m of the building."

[0038] Furthermore, the rule database 5 includes an object table 52 for extracting operational rules based on the relationship between completed building components and / or environmental conditions in a building. The object table 52 stores completed building components and / or environmental conditions related to a given operational rule (rule ID) in association with each other. (Hereafter, completed building components and / or environmental conditions stored in the object table 52 will be referred to as "related components." A related component may be a single related component 1, a pair of related components 1 and 2, or a set of three or more related components such as related component 1, related component 2, related component 3, etc.) As shown in Figure 4, the object table 52 stores the rule ID (linked to the rule table 51), the attributes of the related components (walls, slabs, doors, fire extinguishers, etc. Hereafter referred to as "related component attributes"), and the characteristics of the related components (non-combustible, combustible, handle with care, etc. Hereafter referred to as "related component characteristics") in association with each other. Note that related component attributes are mandatory items, while related component features are optional and desirable (if present, information can be extracted based on the features).

[0039] The rule database 5 is preferably created by the administrator or a rule database creation unit (functional unit) (not shown) that reads the name of the law, the name of the rule, the inspection items, the related components and their attributes / characteristics within the inspection items, and the condition elements from the management data containing the operational rules, or by scanning the management documents with an OCR (Optical Character Reader), and stores them in the corresponding locations in the rule table 51 and object table 52.

[0040] (Operational Database) In the operational database 6, data for creating operational rules, which links the completion database 3, the environment database 4, and the rules database 5 based on the operational rules, is recorded in the operational rules table 61 as it is needed.

[0041] As shown in Figure 5, the operational rules table 61 stores the rule ID (linked to rule database 5: rule table 51), the list of related components (described later), and the operational rules elements necessary for checking the operational rules (described later), in association with each other. The list of related components lists the related components linked in rule database 5: object table 52, with component IDs such as component 1 ID, component 2 ID, component 3 ID, component 4 ID, etc. The related components listed in the component list are the component ID, component attributes, and component characteristics from completion database 3: completion component table 31, or the environmental attributes and component characteristics from environment database 4: environment condition table 41. If the related component in object table 52 is blank, the component list is set to "not specified" (see Examples 1, 2, and 3 in Figure 5). The operational rules elements store the condition elements described in the rule elements of rule database 5: rule table 51 linked by the rule ID.

[0042] The operational rules creation unit 7 links the data from the completion database 3, the environment database 4, and the rules database 5 to create an operational rules table 61, and then creates "operational rules" based on the operational rules table 61. Details will be explained in the management method described below.

[0043] (Management method: Create operational rules) Figure 6 is a flowchart of a management method according to the first embodiment of the present invention. This management method is for creating operational rules. When the management process is started, in step S101, the operational rule creation unit 7 prompts the administrator to select one record from the rule IDs in the rule database 5: rule table 51. Next, in step S102, the operational rule creation unit 7 refers to the related member having the rule ID selected in step S101 from the rule database 5: object table 52, and lists the completed members and / or environmental conditions corresponding to the related member attributes of the said related member as a member list from the completed member table 31 and / or environmental conditions table 41. In step S103, the operational rule creation unit 7 repeats step S102 and lists all the corresponding completed members and / or environmental conditions. Next, in step S104, the operational rule creation unit 7 stores the list of related components listed in step S103, the rule ID selected in step S101, and the condition elements based on the rule elements of the rule ID as individual records in the operational rule table 61. In step S105, the operational rule creation unit 7 outputs a report containing the contents of the records in the operational rule table 61 stored in step S104 to the input / output device 2, in response to a request from the administrator. In step S102 or S103, the operational rule creation unit 7 may also list the completed components and / or environmental conditions in the related component characteristics of the related components.

[0044] (Example of a management method: Example of creating dynamic operating rules) Example 1: Example of creating operational rules based on school rules (no running in the hallways). Step S101: Rule ID "Do not run in the hallway" is selected from rule table 51. Step S102: Referencing object table 52, member 1 ID "Slab (Corridor) A" is listed from completed member table 31 for related member 1 attribute "Slab (Corridor)", and member 2 ID "Person" is listed from environmental condition table 41 for related member 2 attribute "Moving body (Person)". Step S104: A record is created in the operational rules table 61 with rule ID "Do not run in the corridor", component 1 ID "Slab (corridor) A", component 2 ID "Person", and "Operational rule element: No person is moving at a speed of 4m / s or more". Step S105: Operational rules are created with content such as "No one should be moving at a speed of 4m / s or more in the XX corridor (slab A)."

[0045] Example 2: Example of creating operational rules regarding working hour limits Step S101: From Rule Table 51, Rule ID “No one should be inside the building during times other than 7:00 to 22:00” is selected. Steps S102-S103: Referencing object table 52, for related member 1 attribute "entire building", member 1 ID "Slab A, Slab B, Slab C (floor of each room)" is listed from completed member table 31, and for related member 2 attribute "moving body (person)", member 2 ID "person" is listed from environment status table 41. Step S104: In the operational rules table 61, a record is created with the following entry: "Rule ID 'No one should be in the building outside of the hours between 7am and 10pm', Component 1 ID 'Slab A', Component 2 ID 'Person', 'Operational rule element: No one should be in Slab A outside of the hours between 7am and 10pm'", a record is created with the following entry: "Rule ID '7am to 10pm...not allowed', Component 1 ID 'Slab B', Component 2 ID 'Person', 'Operational rule element: 7am to 10pm...not allowed'", and a record is created with the following entry: "Rule ID '7am to 10pm...not allowed', Component 1 ID 'Slab C', Component 2 ID 'Person', 'Operational rule element: 7am to 10pm...not allowed'". Step S105: Operational rules are created with content such as "No one should be present in Room XX (Slab A), Room YY (Slab B), Room ZZ (Slab C), etc., during hours other than 7:00 to 22:00."

[0046] Example 3: Example of creating operational rules for evacuation drills Step S101: From rule table 51, rule ID “Evacuation must be completed within 20 minutes of the start of evacuation” is selected. Steps S102-S103: Referencing object table 52, member 1 ID "Slab A, Slab B, Slab C... (floors of each room, each corridor)" is listed for related member 1 attribute "Entire building", and member 2 ID "Person" is listed from environment status table 41 for related member 2 attribute "Moving body (person)". Step S104: A record is created with the following rules: Rule ID "Evacuation must be completed within 20 minutes of the start of evacuation", Component 1 ID "Slab A", Component 2 ID "Person", "Operational Rule Element: No person should be inside the building 20 minutes after the start of evacuation". A similar record is created for each of the following: Component 1 ID "Slab B", Component 1 ID "Slab C", etc. Step S105: Operational rules are created with content such as "20 minutes after the start of evacuation, there should be no people in Room XX (Slab A), Room YY (Slab B), Corridor ZZ (Slab C)...".

[0047] Example 4: Example of creating operational rules regarding restoration to original condition Step S101: From rule table 51, rule ID "The color change of the wallpaper upon return must be less than XX%" is selected. Steps S102-S103: Refer to object table 52, and for related member 1 attribute "Wall", "Wall A, Wall B, Wall C..." are listed from completed member table 31. Related member 2 attribute is "Blank". Step S104: A record is created in the operational rules table 61 with the following content: "Rule ID: 'The color change of the wallpaper upon return must be less than XX%', Component 1 ID: 'Wall A', 'Operational rule element: The color change of the wallpaper upon return must be less than XX%'". A similar record is created for each of Component 1 ID: 'Wall B', Component 1 ID: 'Wall C', etc. Step S105: Operational rules are created with content such as "The color change of the wallpaper on walls A, B, C, etc. upon return must be XX% or more."

[0048] (Example of management method: Example of creating static operating rules) Example 5: Example of creating operational rules based on the Fire Service Act (fire extinguishers must be within 20m of the building subject to fire protection regulations) Step S101: From rule table 51, rule ID "Fire extinguishers must be within 20m of the fire-protected building" is selected. Steps S102-S103: Refer to object table 52. For related component 1 attribute "fire extinguisher", component 1 ID "fire extinguisher A" is listed from completed component table 31. For related component 2 feature "combustible material", component 2 ID "wall A, wall B" is listed from completed component table 31. Step S104: In the operational rules table 61, a rule ID "Fire extinguishers must be within 20m of the fire-protected object", component 1 ID "Fire extinguisher A", component 2 ID "Wall A", and "Operational rule element: Fire extinguisher A is located within 20m of the fire-protected object (Wall A)" are created. A similar record is also created for component 2 ID "Wall B". Step S105: Operational rules are created, including provisions such as "Fire extinguisher A must not be more than 20 meters from the fire-protected building (wall A) or the fire-protected building (wall B)."

[0049] Example 6: Example of creating operational rules based on train track inspection rules (no obstacles on the rails). Step S101: Rule ID “No objects may be placed on the rails” is selected from rule table 51. Step S102: Refer to the object table 52. For the related member 1 attribute "rail", member 1 IDs "rail A, rail B, rail C..." are listed from the completed member table 31. For the related member 2 attribute "all things", member 2 IDs "obstacle, moving object (person), moving object (vehicle)..." are listed from the environment condition table 41. Step S104: A record is created in the operational rules table 61 with the following conditions: "Rule ID 'No objects may be placed on the rails', Component 1 ID 'Rail A', Component 2 ID 'Obstacle, Moving object (person), Moving object (car)...'", and similarly, one record is created for each of Component 1 ID 'Rail B', Component 1 ID 'Rail C', etc. Step S105: Operational rules are created with content such as "There must be no obstacles, moving objects (people), moving objects (vehicles), etc. on rails A, B, C, etc."

[0050] Example 7: Example of creating operational rules based on company regulations (conference rooms must have speakers). Step S101: Rule ID “There must be a speaker in the conference room” is selected from rule table 51. Step S102: Referencing object table 52, component 1 ID "Slab B" is listed from completed component table 31 for related component 1 attribute "Conference Room", and component 2 ID "Speaker" is listed from environmental conditions table 41 for related component 2 attribute "Speaker". Step S104: The following rule is created in the operational rules table 61: Rule ID "There must be a speaker in the conference room", Component 1 ID "Slab B", Component 2 ID "Speaker", and "Operational rule element: A speaker exists in Slab B". Step S105: Operating rules are created, including details such as "There must be a speaker in the conference room (slab B)."

[0051] As described above, according to the management system 1 and management method of the first embodiment, a completion database 3 that grasps the state of the building at the time of completion, an environmental database 4 that grasps the current environmental conditions of the building, and a rules database 5 that grasps the building's operating rules are related to create an operation database 6 (operating rules table 61). Therefore, based on the operation database 6 (operating rules table 61), operating rules for the proper operation of the building can be automatically created, reflecting the building's current environmental conditions.

[0052] <Second Embodiment> Operational Rules Implementation (Inspection) (Management system configuration) Figure 7 is a block diagram of the configuration of management system 1' according to a second embodiment of the present invention. Management system 1' is a system for implementing operational rules. Management system 1' comprises an input / output device 2, a completion database 3, an environment database 4, an operation database 6 (operational rules table 61), an operation rules operation unit 7', and a notification management database 9.

[0053] The notification management database 9 stores data on the means of notifying administrators when a violation of the operational rules is detected. As shown in Figure 8, the notification management database 9 includes a notification management table 91 in which the rule ID (linked to the rule ID in the operational database 6: operational rules table 61), the notifier's identification information (notifier ID), and the notifier's contact information are stored in association.

[0054] The Operation Rules Department 7' is a functional department that uses the Completion Database 3, the Environment Database 4, and the Operation Database 6 (Operation Rules Table 61) to implement (check) the operation rules. Details will be explained in the management method described below.

[0055] (Management method: Dynamic operation rules) Figure 9 is a flowchart of a management method according to the second embodiment of the present invention. This management method is a management method that operates (checks) "dynamic" operational rules. Figure 10 is a diagram illustrating the operation of this management method.

[0056] When the management process begins, in step S201, the Operation Rules Operation Unit 7' lists specific records from the Environment Database 4. Specific records are listed using the work time, environment attributes, or attribute ID if applicable. Next, in step S202, the Operation Rules Operation Unit 7' extracts records from the Operation Database 6: Operation Rules Table 61 that have related components for the environment attributes of the records listed in step S201. Next, in step S203, the Operation Rules Operation Unit 7' further extracts records from the records extracted in step S202 that have corresponding related components in the component list. In step S204, the Operation Rules Operation Unit 7' repeats the extraction in step S203 for the number of records extracted in step S202, extracting one or more records. Next, in step S205, the Operation Rules Operation Unit 7' refers to the Environment Status Table 41 and lists records with work times ±N seconds after step S201. Next, in step S206, the operation rule operation unit 7' extracts records with the same environmental attributes as in step S202 from the records listed in step S205. Next, in step S207, the operation rule operation unit 7' calculates the distance between the environmental acquisition coordinates of the record in step S201 and the record in step S206. Next, in step S208, the operation rule operation unit 7' calculates the movement speed from the difference in work times between step S201 and step S205 and the distance in step S207. Next, in step S209, the operation rule operation unit 7' refers to the operation rule elements of the operation rule table 61 and detects (checks) whether the movement speed in step S208 violates the condition elements. Next, in step S210, the operation rule operation unit 7' repeats steps S205 to S209 for the number of records extracted in step S204. Next, in step S211, the operational rules operation unit 7' either notifies the administrator of an alert or outputs a report containing the contents of the records checked in steps S209 to S210 to the input / output device 2. Regarding alerts to the administrator, the operational rules operation unit 7' refers to the notification management database 9 and sends, for example, an alert message to the notifier contact identified by the rule ID of the operational rule in which a violation was detected in step S209.In addition, in step S202 or S206, the operational rules unit 7' may list records based on the environmental characteristics of the environmental conditions. In step S211, it is also preferable for the operational rules unit 7' to output a checklist-style report of records in which violations were detected and records in which no violations were detected.

[0057] (Example of management method: Example of dynamic operational rules) Example 8: Example of checking the operational rules for "No running in the hallway" Step S201: From the environment status table 41, records with a specific work time (January 1, 2022, 00:00:00) are listed. Step S202: From the operational rules table 61, records are extracted that have related components (a mobile object (person) in component 1 ID or component 2 ID) related to the environmental attributes (mobile object, person A) of S201. Step S203: Extract the corresponding related member (Member 1 ID: Slab A) from the member list using the records extracted in Step S202. Step S205: From the environmental status table 41, list the records with an operation time of ±1 second later (January 1, 2022, 00:00:01). Step S206: From the records listed in Step S205, extract the records that have the same “moving object, person A” as in Step S202. Step S207: Calculate the movement distance of person A from the environment coordinates obtained from the records of Step S201 and Step S206. Step S208: Calculate the travel speed from the difference in work time between Step S201 and Step S205 and the travel distance in Step S207. Step S209: Detect the violation. Step S210: Send an alert.

[0058] (Management method: Application of static operating rules) Figure 11 is a flowchart of a management method according to the second embodiment of the present invention. This management method is a management method that operates using "static" operational rules. Figure 12 is a diagram illustrating the operation of this management method.

[0059] When the management process begins, in step S201', the Operation Rules Operation Unit 7' lists specific records from the environment database 4. Specific records are listed using the work time, environment attribute, or attribute ID. Next, in step S202', the Operation Rules Operation Unit 7' extracts records from the operation database 6 that have related components concerning the environment attribute of the record selected in step S201'. Next, in step S203', the Operation Rules Operation Unit 7' extracts any records from the environment status table 41 listed in step S201' where the environment acquisition coordinates do not meet the conditions described in the operation rule element of the operation rule table 61 in step S202'. In step S204', the Operation Rules Operation Unit 7' repeats the extraction in steps S202' to S203' for the number of records listed in step S201', extracting (one or more) relevant records. Next, in step S205', the operational rules unit 7' detects a violation if there is at least one relevant record. Then, in step S206', the operational rules unit 7' either notifies the administrator of an alert or outputs a report containing the contents of the records detected in step S205' to the input / output device 2. Alternatively, in step S202', the operational rules unit 7' may list the records based on the environmental characteristics of the environmental status. In step S206', it is also preferable for the operational rules unit 7' to output a checklist-style report containing the records for which violations were detected and the records for which violations were not detected.

[0060] (Example of management method: Example of static operational rules) Example 9: Inspection example of the operational rules of the Fire Service Act (fire extinguishers must be within 20m of the building subject to fire protection regulations) Step S201': From the environment status table 41, records with a specific work time (January 1, 2022) are listed. Step S202': From the operational rules table 61, records are extracted that have a related component (component 1 ID or component 2 ID, which is a wall) related to the environmental attribute (wall) of step S201'. Step S203': If any of the records listed in Step S201' do not meet the distance conditions described in the operational rule element (within 20m) of Step S202', they are extracted as such records. Step S205': Detects a violation. Step S206': Send an alert.

[0061] As described above, according to the management system 1' and management method of the second embodiment, the operation rules can be automatically checked while reflecting the current environmental conditions of the building by utilizing the completion database 3, the environmental database 4, and the operation database 6 (operation rule table 61).

[0062] <Third Embodiment> Operational Plan Creation (Management system configuration) Figure 13 is a block diagram of the management system 10 according to a third embodiment of the present invention. The management system 10 is a system for creating a new plan (hereinafter referred to as "operation plan") necessary for the operation of a building using the set of operation rules described above. The management system 10 comprises an input / output device 2, a completion database 3, an environment database 4, a rule database 5, an operation database 6, an operation rule creation unit 7, and an operation plan creation unit 8.

[0063] As shown in Figure 13, the rule database 5: rule table 51 in this configuration also stores information on the inspection frequency for each record. In addition, the operation database 6 in this configuration stores an operation rules table 61 and an operation plan table 62. The operation plan table 62 manages data by linking multiple operation rules as a single operation plan linked by a single plan ID. The operation plan table 62 is assigned a plan ID (Fire Service Act, Evacuation Safety Verification Method, Disaster Prevention Management, School Rules, etc., based on the rule attributes of the rule database 5: rule table 51), and stores the rule ID of the operation rule selected for the operation plan (linked to the rule ID of the operation rules table 61), the plan attribute that manages whether the inspection of the operation rule selected for the operation plan has been carried out or not, and the date and time (confirmation date and time) on which the inspection of the operation rule selected for the operation plan was confirmed.

[0064] The Operation Plan Creation Unit 8 is a functional unit that uses the Operation Rule Creation Unit 7 to create a new operation plan from a set of operation rules. Further details will be explained in the management method described below.

[0065] (Management method: Operation plan creation) Figure 14 is a flowchart of a management method according to a third embodiment of the present invention. This management method is for creating an operation plan. When the management process is started, in step S301, the operation plan creation unit 8 asks the administrator to select one rule ID from the rule IDs in the rule database 5: rule table 51 that they want to include in the operation plan. Next, in step S302, the operation plan creation unit 8 asks the operation rule creation unit 7 to create an operation rule table 61 relating to the rule ID from step S301 (see the first embodiment). In step S303, the operation plan creation unit 8 repeats steps S301 and S302 to create a set of operation rules with the rule IDs necessary for the operation plan. Next, in step S304, the operation plan creation unit 8 assigns common identification information (plan ID) to the set of operation rules from step S303 and stores the rule ID, plan attribute, and confirmation date and time as separate records in the operation plan table 62. In step S305, the operation plan creation unit 8, in response to a request from the administrator, outputs a report containing the contents of the records in the operation plan table 62 stored in step S304 to the input / output device 2.

[0066] As described above, according to the management system 10 and management method of the third embodiment, a new operational plan for the proper operation of a building can be easily created by arbitrarily assembling the operational rules that the administrator wishes to adopt.

[0067] <Fourth Embodiment> Operation Plan Operation (Inspection) (Management system configuration) Figure 15 is a block diagram of the configuration of the management system 10' according to the fourth embodiment of the present invention. The management system 10' is a system for operating an operation plan. The management system 10' comprises an input / output device 2, a completion database 3, an environment database 4, an operation database 6 (operation rule table 61, operation plan table 62), an operation rule operation unit 7', an operation plan operation unit 8', and a notification management database 9.

[0068] The Operations Planning Department 8' is a functional department that manages the operations plan (checks the operations rules) using the Completion Database 3, the Environment Database 4, and the Operations Database 6. Further details will be explained in the management methods described below.

[0069] (Management method: Operation of the operational plan) Figure 16 is a flowchart of a management method according to a fourth embodiment of the present invention. This management method is a management method for operating an operation plan. When the management process is started, in step S401, the operation plan operation unit 8' lists records from the environment database 4: environment status table 41 whose work time matches the inspection date by comparing it with the inspection frequency in the rule database 5: rule table 51. Next, in step S402, the operation plan operation unit 8' has the operation rule operation unit 7' check the operation rules related to the records in step S401 (see the second embodiment) and detect violations. Next, in step S403, for records in the operation rule table 61 for which no violations were detected in step S402, the operation plan operation unit 8' updates the plan attribute in the operation plan table 62 linked by the rule ID to "Completed", and also stores the date and time the processing in step S402 was performed as the "Confirmation Date and Time". Next, in step S404, the Operation Planning and Operation Unit 8' either refers to the Notification Management Database 9 to notify the administrator of an alert regarding the records in the Operation Rules Table 61 for which a violation was detected in step S402, or outputs a report containing the contents of the records checked for violations in step S403 to the Input / Output Device 2. It is also preferable that in step S404, the Operation Planning and Operation Unit 8' outputs a checklist-style report based on the plan attribute "Completed" or "Not Completed" in the Operation Plan Table 62. Furthermore, it is also preferable that the Operation Planning and Operation Unit 8' sends an alert or outputs a report for records whose inspection date has passed while the plan attribute remains "Not Completed," based on the inspection frequency in the Rule Table 51.

[0070] As described above, according to the management system 1' and management method of the fourth embodiment, the operation plan arbitrarily created by the administrator can be automatically checked using the completion database 3, the environment database 4, and the operation database 6 (operation plan table 62).

[0071] As described above, according to the embodiments of the present invention, the creation of operational rules, the implementation (inspection) of operational rules, the creation of operational plans, and the implementation (inspection) of operational plans are automated. The creation of rules or plans and the inspection of rules or plans to ensure that a building is being operated properly were often managed manually by the building owner, but as described above, since these processes are automated, it becomes possible to significantly shorten the routine tasks related to the operation of the building.

[0072] <Variation> Next, we will describe suitable modifications that can be applied to the above embodiments. In the environmental database 4: environmental status table 41, depending on the operating rules, such as in Example 8, it is necessary to store information on a second-by-second basis, and data compression processing is required.

[0073] (1) Data compression process (Part 1) The Operations Rules Department 7' or the Operations Planning Department 8' extracts records from the Environmental Status Table 41 whose work time has elapsed for a certain period of time (e.g., 7 days) and transfers them to a storage device (such as a large-capacity storage server) separate from the server computer that stores the Environmental Database 4.

[0074] (2) Data compression process (Part 2) The environmental status table 41 is normalized. Figure 17 is an image diagram of the data compression process. The environmental status table 41 is divided into a first table 411 containing the environmental acquisition result ID, coordinate point ID, and environmental acquisition coordinates, and a second table 412 containing the environmental acquisition result ID, environmental acquisition process, work time, environmental attributes, and reference destination. The first table 411 is compressed into a file and transferred to a storage device SS (such as a large-capacity storage server) separate from the storage device that stores the environmental database 4. The second table 412 registers information about the reference destination (storage location) of the compressed file of the first table 411, so that it can be read from the reference destination and used as needed.

[0075] By constructing the environmental database 4 using the above modifications, the operation of the above embodiments will become smoother.

[0076] Although preferred embodiments and variations of the present invention have been described above, each form and each variation can be combined based on the knowledge of those skilled in the art, and such forms are also included within the scope of the present invention. [Explanation of symbols]

[0077] 1,1',10,10' Management System 2 Input / Output Devices 3. Completion Database 31 Completed Materials Table 4. Environmental Database 41 Environmental Conditions Table 5. Rule Database 51 Rule Table 52 Object Tables 6. Operational Database 61 Operating Rules Table 62 Operational Plan Table 7. Department for Creating Operational Rules 7´ Operational Regulations Operation Department 8. Operations Planning Department 8' Operations Planning Department 9. Notification Management Database 91 Notification Management Table

Claims

1. Regarding the completed building components of the buildings under management, a completion database is used that stores at least the component ID, component coordinates, and component attributes. Regarding the environmental conditions of the building after completion, including the completed components or objects related to the completed components, an environmental database storing at least the environmental acquisition result ID, environmental acquisition coordinates, work time, and environmental attributes, Regarding the operating rules of the aforementioned building, a rule database comprising at least a rule table storing the rule ID, rule attributes, and rule elements of the operating rules, and an object table storing at least the rule ID and related member attributes of related members related to the rule ID, in order to associate the completed building materials, environmental conditions, and the operating rules, An operation database comprising an operation rule table storing the rule ID, the list of related components, and the operation rule elements based on the rule elements, An operation rule creation unit creates the operation rule table by associating the data of the completion database, the environment database, and the rule database, A management system characterized by having the following features.

2. A method for causing a management system to perform the following steps, comprising an electronic circuit configured to perform each of the following steps: Regarding completed building components of a building to be managed, the system transmits and receives information from a system comprising: a completed building database storing at least component IDs, component coordinates, and component attributes; an environmental database storing at least environmental acquisition result IDs, environmental acquisition coordinates, work time, and environmental attributes regarding the environmental conditions of the building, including the completed building components or objects related to the completed building components after completion; a rule table storing at least the rule IDs, rule attributes, and rule elements of the operational rules of the building; and an object table storing at least the rule IDs and relational attributes of related components related to the rule IDs, in order to associate the completed building components, the environmental conditions, and the operational rules. (A1): A step of selecting one record from the rule ID in the rule database, (B1): A step of referring to the related member having the rule ID of step (A1) from the object table, and listing the completed member and / or the environmental status corresponding to the related member attribute of the related member from the completed database and / or the environmental database as a member list of the related member, (C1): The step of repeating step (B1) and listing all the relevant completed components and / or environmental conditions, (D1): A step of creating an operation rule table and storing it in the operation database, by taking the list of related members listed in steps (B1) and (C1), together with the rule ID from step (A1), the operation rule element based on the rule ID from step (A1), and so on, as individual records. A management method characterized by having the following.

3. Regarding the completed building components of the buildings under management, a completion database is used that stores at least the component ID, component coordinates, and component attributes. Regarding the environmental conditions of the building after completion, including the completed components or objects related to the completed components, an environmental database storing at least the environmental acquisition result ID, environmental acquisition coordinates, work time, and environmental attributes, Regarding the operating rules of the said building, a rule database comprising at least a rule table storing the rule ID, rule attributes, and rule elements of the said operating rules, and an object table storing at least the rule ID and the relational attributes of related members related to the rule ID, in order to associate the completed building components, the environmental conditions, and the said operating rules, An operation database comprising an operation rule table storing the rule ID, the list of related components, and the operation rule elements based on the rule elements, An operational rules management unit that checks the operational rules using the aforementioned completion database, the aforementioned environment database, and the aforementioned operational rules table, A management system characterized by having the following features.

4. A method for causing a management system to perform the following steps, comprising an electronic circuit configured to perform each of the following steps: Regarding completed building components of a building to be managed, the system includes: a completed building database that stores at least component IDs, component coordinates, and component attributes; an environmental database that stores at least environmental acquisition result IDs, environmental acquisition coordinates, work time, and environmental attributes regarding the building's environmental conditions, including the completed building components or objects related to the completed building components after completion; a rule database that stores at least the rule IDs, rule attributes, and rule elements of the operational rules of the building; an object table that stores at least the rule IDs and relational attributes of the relevant components, which are the environmental conditions related to the operational rules, in order to associate the environmental conditions with the operational rules; and an operational database that stores the rule IDs, a component list of the relevant components, and operational rule elements based on the rule elements. (A2): The step of listing specific records from the environmental database, (B2): A step of extracting from the operational rules table the records that have the relevant members relating to the environmental attributes of the records listed in step (A2), (C2): A step of further extracting records from the records extracted in step (B2) that have a corresponding related member in the member list, (D2): A step in which the extraction in step (C2) is repeated for the number of records extracted in step (B2), (E2): A step of listing records from the environment database that have a work time ± N seconds after the work time of step (A2), (F2): A step of extracting records from the records listed in step (E2) that have the same environmental attributes as in step S (B2), (G2): A step of calculating the distance between step (A2) and the environment acquisition coordinates of step (F2), (H2): A step of calculating the travel speed from the difference in working time between step (A2) and step (E2) and the distance in step (G2), (I2): A step of detecting whether the movement speed violates the conditions described in the operational rule elements of the operational rule table, (J2): A step in which steps (E2) to (I2) are repeated and checked for the records extracted in step (D2), A management method characterized by having the following.

5. A method for causing a management system to perform the following steps, comprising an electronic circuit configured to perform each of the following steps: Regarding completed building components of a building to be managed, the system transmits and receives information between a completion database that stores at least component IDs, component coordinates, and component attributes; an environment database that stores at least environment acquisition result IDs, environment acquisition coordinates, work time, and environment attributes regarding the building's environmental conditions, including the completed building components or objects related to the completed building components after completion; a rule database that stores at least the rule IDs, rule attributes, and rule elements of the operation rules of the building; an object table that stores at least the rule IDs and relationship attributes of related components related to the rule IDs in order to associate the completed building components, the environmental conditions, and the operation rules; and an operation database that stores the rule IDs, a component list of the related components, and operation rule elements based on the rule elements. (A2'): The step of listing specific records from the environmental database, (B2'): A step of extracting from the operational rules table records that have the relevant members relating to the environmental attributes of the records listed in step (A2'), (C2'): A step in which, if there is a record among the records listed in step (A2') in which the environment acquisition coordinates of the record do not satisfy the conditions described in the operation rule element of the operation rule table in step (B2'), the corresponding code is extracted. (D2'): A step in which steps (B2') to (C2') are repeated for each record listed in step (A2') and checked, (E2'): A step of detecting the record found in steps (C2') to (D2') as a violation, A management method characterized by having the following.

6. Furthermore, it includes an operation plan creation unit for creating a single operation plan using a selection of the aforementioned operation rules, The operation plan creation unit uses the operation rule creation unit to create the operation rule table with respect to the rule ID of each selected operation rule, Create an operation plan table in the operation database that stores the plan ID of the operation plan, the rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rules related to the rule ID has been carried out or not, and a confirmation date and time that manages the date and time when the inspection was confirmed to have been carried out. The management system according to feature 1.

7. Furthermore, in order to create a single operational plan using the selected operational rules, (A3): A step of selecting one record from the rule ID in the rule database, (B3): With respect to the rule ID selected in step (A3), the steps (A1) to (D1) are performed to create the operational rule table for the rule ID, (C3): A step of repeating the above steps (A3) to (B3) to create a set of operational rules using the rule IDs necessary for the operational plan, (D3): With respect to step (C3), the steps include creating an operation plan table and storing it in the operation database, with each record containing the plan ID of the operation plan, the rule ID, the plan attribute which manages whether the inspection of the operation rules of the rule ID has been performed or not, and the confirmation date and time which manages the date and time when the performance of the inspection was confirmed, The management method according to claim 2, characterized by having the following features.

8. Furthermore, it includes an operational plan table and an operational plan operation unit for reviewing operational plans that include multiple operational rules, The aforementioned operational plan table is: The operation database stores the following: the plan ID of the operation plan, the rule ID of the operation rule selected for the operation plan, the plan attribute which manages whether the inspection of the operation rule of the rule ID has been performed or not, and the confirmation date and time which manages the date and time when the performance of the inspection was confirmed. The aforementioned Operations Planning and Operations Department, From the aforementioned environmental database, based on the inspection frequency information stored in the aforementioned rule database, a list of records for inspection dates is generated. Using the aforementioned operational rules operation unit, the operational rules of the records on the inspection date are checked, and for records where no violations are detected, the plan attribute of the operational plan table is updated to completed, and the confirmation date and time are stored. The management system according to claim 3.

9. Furthermore, in order to review the operational plan which includes multiple operational rules, The operation database stores an operation plan table that stores the plan ID of the operation plan, the rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rules of the rule ID has been carried out or not, and a confirmation date and time that manages the date and time when the inspection has been confirmed to have been carried out, and transmits and receives information. (A4): A step of listing records from the environmental database in which the work time corresponds to an inspection day, compared with the inspection frequency stored in the rule database, (B4): A step to detect a violation by performing steps (A2) to (I2) with respect to the records listed in step (A4), (C4): For records in which no violation is detected in step (B4), the plan attribute in the operation plan table is set to completed, and the date and time the inspection in step (B4) was performed is stored as the confirmation date and time. The management method according to claim 4, characterized by having the following features.

10. Furthermore, in order to review the operational plan which includes multiple operational rules, The operation database stores an operation plan table that stores the plan ID of the operation plan, the rule ID selected for the operation plan, a plan attribute that manages whether the inspection of the operation rules of the rule ID has been carried out or not, and a confirmation date and time that manages the date and time when the inspection has been confirmed to have been carried out, and transmits and receives information. (A4'): A step of listing records from the environment database in which the work time corresponds to an inspection day, compared with the inspection frequency stored in the rule database, (B4'): A step to detect a violation by performing steps (A2') to (E2') with respect to the records listed in step (A4'), (C4'): For records in which no violation is detected in step (B4'), the plan attribute in the operation plan table is set to completed, and the date and time the inspection in step (B4') was performed is stored as the confirmation date and time. The management method according to claim 5, characterized by having the following features.

11. Furthermore, it includes a notification management database that stores the rule ID, the notifier's notifier ID, and the notifier's contact information. The operational rules in which a violation is detected during the inspection are characterized in that, based on the rule ID, an alert is sent to the notifier by referring to the notification management database. The management system according to claim 3 or claim 8.

12. Furthermore, a notification management database that stores the rule ID, the notifier's notifier ID, and the notifier's contact information is used to send and receive information. Following the step of detecting the violation, the operational rule in which the violation was detected includes the step of sending an alert to the notifier by referring to the notification management database based on the rule ID, The management method according to any one of 4, 5, 9, or 10, characterized by having the following:

13. In the aforementioned environmental database, records for which a certain period of time has elapsed are transferred to a storage device separate from the storage device of the environmental database. The management system according to any one of claims 1, 3, 6, or 8.

14. The data in the environment database is divided into a first table containing the environment acquisition result ID, coordinate point ID, and environment acquisition coordinates, and a second table containing the environment acquisition result ID, work time, environment attributes, and reference destination. The first table is transferred to a storage device separate from the environment database storage device, and the information of the other storage device is registered in the reference destination of the second table, and the data is read from the reference destination as needed. The management system according to any one of claims 1, 3, 6, or 8.

15. The management system according to claim 1, characterized in that the operational rules creation unit outputs a report of the records created in the operational rules table in response to a request from the administrator.

16. The management system according to claim 3, characterized in that the operational rules operation unit outputs a report of records of violations checked based on the operational rules table in response to a request from the administrator.

17. The management system according to claim 6, characterized in that the operation plan creation unit outputs a report of the records created in the operation plan table in response to a request from the administrator.

18. The management system according to claim 8, characterized in that the operational planning unit outputs a report of records in which violations have been checked based on the operational planning table, in response to a request from the administrator.

19. The aforementioned completion database stores the characteristics of the completed components, The aforementioned environmental database stores the environmental characteristics of the aforementioned environmental conditions. The rule database stores the characteristics of the related members, The management system according to claim 1, characterized in that the operational rule creation unit creates the member list for the operational rule table from the member characteristics.

20. A management program characterized by describing the management method described in any of claims 2, 4, 5, 7, 9, 10, or 12 in a computer program and making it executable.

Images