Construction management device and construction management method

Abstract

This construction management device comprises: a storage unit that stores design library information for a facility, and facility information in which the facility and any equipment connected to a system provided to the facility are associated with each other; and an inspection library creation unit that identifies the equipment connected to the system on the basis of the facility information, extracts information related to the system and to the equipment from the design library information and then integrates the same, and creates an inspection library required for inspecting the system.

Description

Construction management device and construction management method

[0001] The present disclosure relates to a construction management device and a construction management method.

[0002] When installing instrumentation systems in large-scale plants, etc., an inspection (hereinafter referred to as "loop check") is conducted to check that devices (such as pressure gauges and flow meters) connected to the systems (loops) of the instrumentation system are wired correctly and that control signals and other signals are properly communicated between the devices. For example, in the instrumentation systems of large-scale plants, the number of systems requiring loop checks can exceed tens of thousands of loops. In such cases, creating the inspection documents required for loop checks requires a huge amount of work.

[0003] The system diagram checking device described in Patent Document 1 can create system diagrams in the form of electronic data. The system diagram checking device described in Patent Document 1 also acquires equipment information for each piece of equipment included in a tracing section specified by a user on the system diagram, and checks the system of the tracing section.

[0004] Japanese Patent Application Laid-Open No. 2019-174946

[0005] However, the conventional construction management device described in Patent Document 1 and the like does not have a function to support the creation of inspection documents required for loop checks on systems (loops) or a function to systematically manage loop checks, so users still need to spend a huge amount of time and effort creating inspection documents and managing loop checks.

[0006] The present disclosure has been made in consideration of the above circumstances, and aims to provide a construction management device and a construction management method that support work related to loop checks on systems (loops).

[0007] In order to solve the above problems, the present disclosure proposes the following means: A construction management device according to a first aspect of the present disclosure includes a storage unit that stores design document information for equipment and equipment information that associates the equipment with devices connected to a system equipped with the equipment, and an inspection document creation unit that identifies the equipment connected to the system based on the equipment information, extracts and integrates information related to the system and the devices from the design document information, and creates inspection documents necessary for inspecting the system.

[0008] A construction management method according to a second aspect of the present disclosure identifies the equipment connected to a system based on equipment information that associates the equipment with the equipment connected to the system equipped on the equipment, extracts and integrates information related to the system and the equipment from the design document information of the equipment, and creates inspection documents necessary for inspecting the system.

[0009] The construction management device and construction management method according to the present disclosure can assist in work related to loop checks on systems (loops).

[0010] FIG. 1 is a configuration diagram of a construction management system according to one embodiment; FIG. 2 is a functional block diagram of a construction management device of the construction management system; FIG. 3 is a diagram showing plant information; FIG. 4 is a diagram showing inspection document definition information; FIG. 5 is a diagram showing inspection dependency information; FIG. 6 is a functional block diagram of an inspection management unit of the construction management device; FIG. 7 is a diagram illustrating a method for generating an inspection document; FIG. 8 is a diagram illustrating a determination result of whether or not a loop check can be performed; FIG. 9 is a diagram illustrating a generated inspection format; and FIG. 10 is a diagram illustrating an application for inputting the results of a loop check.

[0011] An embodiment of the present disclosure will be described with reference to Fig. 1 to Fig. 11. Fig. 1 is a configuration diagram of a construction management system 1000 according to this embodiment.

[0012] [Construction Management System 1000] The construction management system 1000 is a system for managing the construction of a large-scale plant. The construction management system 1000 includes a construction management device 100, a design document management device 200, a terminal 300, a management terminal 400, and a site management device 500. The construction management device 100, the design document management device 200, the terminal 300, the management terminal 400, and the site management device 500 are connected via a network NW, and may be installed in different countries or different regions.

[0013] The network NW may be a wide area network (WAN) such as the Internet, a private network (LAN) within the building where the construction management system 1000 is installed, or a combination thereof. The network NW may be either wired or wireless. Communication between devices may involve other devices such as access points.

[0014] The construction management device 100 is a management device that includes one or more servers and manages the construction of a large-scale plant. The server is a computer that includes a processor such as a CPU, memory, recording media such as a hard disk or flash memory, and a communication device. When the construction management device 100 is configured with multiple servers, the multiple servers may have different types of operating systems and software. The multiple servers may also be operated by different operating entities. The multiple servers may be installed in different countries or regions. The multiple servers may also be a system that combines an on-site server and a cloud server that provides IaaS (Infrastructure as a Service), PaaS (Platform as a Service), or SaaS (Software as a Service). In the following description, "server" includes any of the above servers.

[0015] The design document management device 200 is a server that manages design documents related to the design and inspection of equipment modules of a large-scale plant. The design document management device 200 is a server to which, for example, design documents related to the design and inspection created by a designer DE of a large-scale plant are uploaded. Note that the construction management device 100 may have at least some of the functions of the design document management device 200.

[0016] Terminal 300 is a terminal such as a smartphone, tablet terminal, or personal computer owned by a project manager PA involved in the construction of a large-scale plant. The project manager PA manages projects relating to the construction of a large-scale plant via terminal 300. Note that the project manager PA may also operate construction management device 100 directly without using terminal 300.

[0017] The management terminal 400 is a terminal owned by a system administrator SA of the construction management device 100. The system administrator SA manages the construction management device 100 via the management terminal 400. The system administrator SA may also operate the construction management device 100 directly without going through the management terminal 400.

[0018] The site management device 500 is a server installed at a site where a large-scale plant is constructed, and manages the process of plant construction (including related work). The site management device 500 is operated by a site inspector SI. Note that the construction management device 100 may have at least some of the functions of the site management device 500.

[0019] 2 is a functional block diagram of the construction management device 100. The construction management device 100 comprises a memory unit 1, a design document acquisition unit 2, a management interface 3, a site information acquisition unit 4, and an inspection management unit 5.

[0020] The functions of the functional blocks of the construction management device 100 (memory unit 1, design document acquisition unit 2, management interface 3, site information acquisition unit 4, and inspection management unit 5) are realized by a processor executing a construction management program provided to the construction management device 100. The construction management device 100 may have a logic circuit that executes at least some of the calculations, etc. of the construction management device 100.

[0021] [Memory Unit 1] The memory unit 1 is a non-volatile recording medium that stores a construction management program that operates the construction management device 100 and data necessary for construction management, and is a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The memory unit 1 stores plant information 11, design document information 12, inspection document definition information 13, inspection document information 14, inspection dependency information 15, inspection format information 16, process information 17, and inspection result information 18.

[0022] FIG. 3 is a diagram showing plant information 11. Plant information (equipment information) 11 is information related to a plant. As shown in FIG. 3, the plant information 11 is information that associates a plant (equipment), a system (hereinafter also referred to as a "loop") provided in the plant's instrumentation system, and equipment (such as gauges and valves) connected to the system. The plant type, system type, and equipment type are represented by "tags" consisting of alphanumeric symbols. Tags are unique in the construction management system 1000 and do not overlap.

[0023] The design document information 12 is information related to the design documents of the plant. The design document information 12 includes design drawings of the plant, system drawings (documents) of the plant's instrumentation system, and specifications (documents) of the equipment connected to the system (loop). The design document information 12 is stored in association with tags.

[0024] 4 is a diagram showing the inspection document definition information 13. The inspection document definition information 13 is information that defines the inspection documents (hereinafter also referred to as "loop packages") required for an inspection (hereinafter also referred to as "loop check") to confirm that devices connected to a system (loop) in the plant's instrumentation system are correctly wired and that signals such as control signals are correctly communicated between the devices. As shown in FIG. 4, the inspection document definition information 13 is information that defines, for each system, the types of design documents included in the inspection documents required for the loop check.

[0025] The inspection document information 14 is information related to documents required for the loop check. The inspection document information 14 includes inspection documents (loop packages) created by extracting them from the design document information 12 based on the inspection document definition information 13. The inspection document information 14 is stored in association with tags.

[0026] FIG. 5 is a diagram showing the inspection dependency information 15. The inspection dependency information 15 defines, for each piece of equipment, tasks (such as construction, inspection, and on-site delivery) that have dependencies on loop checks. For example, as shown in FIG. 5, the equipment "J12-Z-30006BA" is classified as the "Hardwired" functional class. In order to inspect the equipment "J12-Z-30006BA," the dependent tasks WA and WB must be completed. Furthermore, the equipment "J12-Z-30006BO" is classified as the "DPXC" functional class. In order to inspect the equipment "J12-Z-30006BO," the dependent tasks WX, WY, and WZ must be completed. Dependent tasks are defined for each equipment functional class.

[0027] FIG. 6 is a diagram showing test format information 16. The test format information 16 is information that defines, for each device, the test format (such as test items and test records) (also referred to as "ITR") used when performing a loop check. For example, as shown in FIG. 6, device "J12-Z-30006BA" is classified as a "Hardwired" functional class and must be loop checked based on test format FA. Device "J12-Z-30006BO" is classified as a "DPXC" functional class and must be loop checked based on test format FB. Test formats are defined for each device's functional class. The test format includes, for example, test items and test pass criteria for each test item.

[0028] The process information 17 is information relating to the process of construction of the plant. The process information 17 includes the process of construction of the plant (including related work). The process information 17 is stored in association with a tag.

[0029] The inspection result information 18 is information about the results of the plant inspection. The inspection result information 18 includes the results of the loop check. The inspection result information 18 is stored in association with a tag.

[0030] [Design document acquisition unit 2] The design document acquisition unit 2 is connected to the design document management device 200 via an interface including an API (Application Programming Interface), and acquires design documents created by the designer DE from the design document management device 200 (design document acquisition step). The design document acquisition unit 2 records the acquired design documents in the storage unit 1 as inspection document information 14.

[0031] For example, the design document acquisition unit 2 may periodically acquire design documents collectively from the design document management device 200 and update the inspection document information 14 recorded in the storage unit 1. In addition, the design document acquisition unit 2 may individually acquire design documents from the design document management device 200 as needed.

[0032] The designer DE may directly upload the created design documents to the design document acquisition unit 2 of the construction management device 100. In this case, the design document acquisition unit 2 records the received design documents in the storage unit 1 as inspection document information 14.

[0033] [Management Interface 3] The management interface 3 is an interface connected to the terminal 300 and the management terminal 400. Specifically, the management interface 3 includes an API that connects the terminal 300, the management terminal 400, and the test management unit 5.

[0034] The project manager PA can access the inspection management unit 5 via the management interface 3 using an application running on the terminal 300. The project manager PA accesses the inspection management unit 5 to create inspection documents (loop packages), etc.

[0035] The system administrator SA can access the inspection management unit 5 via the management interface 3 using an application running on the management terminal 400. The system administrator SA accesses the inspection management unit 5 and performs connection settings between the construction management device 100, the design document management device 200, and the site management device 500, etc.

[0036] The applications that run on the terminal 300 and the management terminal 400 may be web applications or native applications.

[0037] [Site Information Acquisition Unit 4] The site information acquisition unit 4 is connected to the site management device 500 via an interface including an API, acquires site-related information from the site management device 500, and records the information in the storage unit 1. Specifically, the site information acquisition unit 4 acquires the plant construction process (including related work) from the site management device 500 and records the process information 17 in the storage unit 1 (construction process acquisition step). The site information acquisition unit 4 also acquires the results of the loop check from the site management device 500 and records the results in the storage unit 1 as inspection result information 18 (inspection result acquisition step).

[0038] For example, the site information acquisition unit 4 may periodically acquire information related to a site collectively from the site management device 500 and update the process information 17 and the inspection result information 18 recorded in the storage unit 1. Furthermore, the site information acquisition unit 4 may also acquire information related to a site individually from the site management device 500 as needed.

[0039] The site inspector SI may directly upload information related to the site (the plant construction process and loop check results) to the site information acquisition unit 4 of the construction management device 100. In this case, the site information acquisition unit 4 records the received site-related information in the memory unit 1 as process information 17 and inspection result information 18.

[0040] 7 is a functional block diagram of the inspection management unit 5. The inspection management unit 5 manages inspections during the construction of large-scale plants. The inspection management unit 5 has an inspection document creation unit 51, an inspection process management unit 52, an inspection format creation unit 53, and an inspection result collection unit 54.

[0041] The inspection document creation unit 51 creates an inspection document (loop package) based on the plant information 11, the design document information 12, and the inspection document definition information 13. The inspection document creation unit 51 creates an inspection document for the corresponding system based on the tag of the plant system specified by the project manager PA.

[0042] FIG. 8 illustrates an example of an inspection document generation method. The following describes a method in which the inspection document creation unit 51 creates an inspection document for the system "J12-F-500V" of the plant "A110-SH" shown in FIG. 3 . Using an application running on the terminal 300, the project manager PA inputs an instruction to the inspection document creation unit 51 to create an inspection document for the system "J12-F-500V." The inspection document creation unit 51 identifies the equipment connected to the system "J12-F-500V" from the plant information 11 shown in FIG. 3 and obtains the equipment tags (J12-F-500VB, J12-F-500VC, J12-F-500VY). Next, the inspection document creation unit 51 obtains the design document type (system drawing, equipment specification) included in the inspection document required for the loop check of the system "J12-F-500V" from the inspection document definition information 13 shown in FIG. 4 . Next, as shown in Figure 8, the inspection document creation unit 51 generates an inspection document by extracting and integrating all of the design documents tagged with equipment from the design documents included in the inspection documents required for the loop check, or some of the pages of the design documents that are distinguished by equipment tags.

[0043] The inspection document creation unit 51 regenerates the inspection document using the latest design document when the design document recorded as design document information 12 in the memory unit 1 and included in the inspection document required for loop checking is updated.

[0044] By simply specifying the tag of a system, the project manager PA can automatically generate the inspection documents required for the loop check of the corresponding system. In addition, when the design documents that make up the inspection documents are updated, the project manager PA can easily regenerate the inspection documents.

[0045] In the example of generating an inspection document shown in FIG. 8, there are few devices connected to the system, and only a few types of design documents are required for loop checks. However, in actual generation of inspection documents, there are many devices connected to the system, and many types of design documents are required for loop checks. Therefore, the generation and regeneration of inspection documents by the inspection document creation unit 51 is more efficient than manual creation of inspection documents by a user. Furthermore, the generation and regeneration of inspection documents by the inspection document creation unit 51 is accurate and error-free.

[0046] The inspection process management unit 52 makes a preliminary determination as to whether or not a loop check can be performed on the relevant system (loop) based on the plant information 11, the inspection dependency relationship information 15, and the process information 17. Here, the preliminary determination is information that the inspection process management unit 52 provides to the project manager PA, and is used by the project manager PA to determine whether or not a loop check can be performed.

[0047] FIG. 9 is a diagram illustrating the results of a preliminary determination of whether or not a loop check can be performed. Hereinafter, a method for the inspection process management unit 52 to make a preliminary determination of whether or not a loop check can be performed for the system "J12-Z-30006B" of the plant "A110-SH" shown in FIG. 3 will be described. Using an application running on the terminal 300, the project manager PA inputs an instruction to the inspection process management unit 52 to make a preliminary determination of whether or not a loop check can be performed for the system "J12-Z-30006B." The inspection process management unit 52 identifies the equipment connected to the system "J12-Z-30006B" from the plant information 11 shown in FIG. 3 and obtains the equipment tags (J12-Z-30006BA, J12-Z-30006BO, J12-Z-30006BZ). Next, the inspection process management unit 52 identifies the tasks (task WA, task WB, task WX, task WY, task WZ, and task WO) that have dependencies on the inspection of the connected equipment from the inspection dependency relationship information 15 shown in FIG. 5 . Next, the inspection process management unit 52 checks the status of the dependent tasks from the process information 17. When the status of all dependent tasks is "completed," the inspection process management unit 52 makes a preliminary determination that the loop check for the system "J12-Z-30006B" is "executable." When the status of at least one dependent task is "incomplete," the inspection process management unit 52 makes a preliminary determination that the loop check for the system "J12-Z-30006B" is "not executable." The inspection process management unit 52 transmits the preliminary determination result to the terminal 300. The terminal 300 displays the preliminary determination result, as shown in FIG. 9 , on the display screen of the terminal 300, indicating whether or not the loop check can be performed.

[0048] By simply specifying the tag of a system, the project manager PA can make a preliminary judgment as to whether or not a loop check can be performed on the system. If the preliminary judgment result is "unable to perform," the project manager PA can identify the unfinished work that is preventing the loop check from being performed.

[0049] The test format creation unit 53 generates a test format F (test items, test records, etc.) to be used when performing a loop check on the corresponding system (loop) based on the plant information 11 and the test format information 16 .

[0050] FIG. 10 is a diagram illustrating a generated test format F. Hereinafter, a method for generating the test format F for the system "J12-Z-30006B" of the plant "A110-SH" shown in FIG. 3 by the test format creation unit 53 will be described. Using an application running on the terminal 300, the project manager PA inputs an instruction to the test format creation unit 53 to generate the test format F for the system "J12-Z-30006B." The test format creation unit 53 identifies the equipment connected to the system "J12-Z-30006B" from the plant information 11 shown in FIG. 3 and obtains the equipment tags (J12-Z-30006BA, J12-Z-30006BO, J12-Z-30006BZ). Next, the test format creation unit 53 obtains the equipment test formats (equipment test format FA, equipment test format FB, equipment test format FC) for each connected equipment from the test format information 16 shown in FIG. 6. The test format creation unit 53 integrates the device test formats for each device to generate test format F for the system "J12-F-500V" as shown in FIG.

[0051] The project manager PA can generate an inspection format F (inspection items, test records, etc.) to be used when performing a loop check on the corresponding system (loop) simply by specifying the tag of the system.

[0052] The inspection result collection unit 54 receives the results of the loop check from the site management device 500 based on the inspection format F created by the inspection format creation unit 53, and tally up the results of the loop check.

[0053] FIG. 11 illustrates an application AP for inputting loop check results. Hereinafter, a method for the inspection result collection unit 54 to collect loop check results for the system "J12-Z-30006B" of the plant "A110-SH" shown in FIG. 3 will be described. The inspection result collection unit 54 is connected to the site management device 500 via the site information acquisition unit 4 and transmits an inspection format F for the system "J12-F-500V" to the site management device 500. The application AP running on the site management device 500 generates an "inspection result input region 510" for the loop check for the system "J12-F-500V" based on the received inspection format F and presents it to the site inspector SI. The application AP may be a web application or a native application.

[0054] The inspection result input region 510 includes, for example, the inspection items and inspection pass criteria included in the inspection format F, and an inspection result input form 511 for the inspection items. The site inspector SI can input the inspection results for the inspection items into the inspection result input form 511.

[0055] 11, the application AP may have an "approval input region 520." The approval input region 520 includes, for example, an approver and an approval input form 521. Multiple approvers included in the site inspector SI can input their approvals for the inspection results in the approval input form 521.

[0056] After the site inspector SI inputs the inspection results (and approval) in the application AP, he / she saves the input data by operating the save button 530. The inspection result collection unit 54 acquires the input data from the application AP. The inspection result collection unit 54 stores the acquired input data in the memory unit 1 as inspection result information 18.

[0057] The project manager PA can electronically and centrally manage the inspection format F used for loop checks on the system (loop) and the results of inspections based on the inspection format F.

[0058] The construction management device 100 according to this embodiment allows the project manager PA to centrally manage work related to loop checks on systems (loops) and supports the project manager PA in his or her work related to loop checks. Specifically, the project manager PA can automatically generate and regenerate inspection documents (loop packages) required for loop checks on the system by simply specifying a system tag. The project manager PA can determine whether or not to perform a loop check on the system by simply specifying a system tag. The project manager PA can generate an inspection format F to be used when performing a loop check on the system by simply specifying a system tag. The project manager PA can electronically centrally manage the inspection format F used for loop checks on the system and the results of inspections based on the inspection format F.

[0059] The programs in each embodiment may be recorded on a computer-readable recording medium, and then read and executed by a computer system. The term "computer system" includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. The term "computer-readable recording medium" may also include media that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or media that store programs for a fixed period of time, such as volatile memory within a computer system serving as a server or client. The program may also be designed to implement some of the functions described above, or may be capable of implementing the functions described above in combination with a program already stored in the computer system.

[0060] The construction management device and construction management method according to the present disclosure can be used in devices and systems that manage the inspection of systems equipped with many devices.

[0061] 1000 Construction management system 100 Construction management device 1 Storage unit 11 Plant information (equipment information) 12 Design document information 13 Inspection document definition information 14 Inspection document information 15 Inspection dependency information 16 Inspection format information 17 Process information 18 Inspection result information 2 Design document acquisition unit 3 Management interface 4 Site information acquisition unit 5 Inspection management unit 51 Inspection document creation unit 52 Inspection process management unit 53 Inspection format creation unit 54 Inspection result collection unit

Claims

1. A storage unit that stores design document information of a facility and facility information that associates the facility with devices connected to a system provided in the facility; an inspection document creation unit that identifies the equipment connected to the system based on the facility information, extracts and integrates information related to the system and the equipment from the design document information, and creates inspection documents necessary for inspecting the system; Equipped with Construction management device.

2. The storage unit records inspection document definition information that defines a type of the design document information included in the inspection document for each system, The inspection document creation unit extracts information related to the system and the equipment from the design document information based on the inspection document definition information. The construction management device according to claim 1 .

3. The facility information identifies the system and the device with unique tags; The design document information and the inspection document definition information are stored in association with the tag, The inspection document creation unit identifies the equipment connected to the system based on the tag, and extracts information related to the system and the equipment based on the tag. The construction management device according to claim 2.

4. The storage unit stores process information related to a construction process of the facility, an inspection process management unit that provides information for determining whether or not an inspection can be performed on the system based on the equipment information and the process information; The construction management device according to any one of claims 1 to 3.

5. The storage unit records inspection dependency relationship information that defines, for each of the devices, an operation that has a dependency relationship with the inspection of the system; The inspection process management department Identifying the task having a dependency relationship with the test for which the execution possibility is to be determined based on the test dependency relationship information; providing information for checking the process related to the identified work from the process information and determining whether or not the work can be carried out; The construction management device according to claim 4.

6. The storage unit records inspection format information that defines, for each device, a device inspection format used when inspecting the device, and a test format creation unit that acquires the device test format of the device connected to the system from the test format information and creates a test format to be used when testing the system. The construction management device according to any one of claims 1 to 3.

7. a test result collection unit that collects test result inputs of the system input based on the test format and records the inputs in the storage unit, The construction management device according to claim 6.

8. The test result collection unit collects the result input of the system test together with the approval input of the approver, and records them in the storage unit. The construction management device according to claim 7.

9. Identifying the equipment connected to the system based on equipment information that associates the equipment with the equipment and the equipment connected to the system provided in the equipment; Extracting and integrating information related to the system and the equipment from the design document information of the facility, and creating inspection documents necessary for inspecting the system; Construction management method.

10. Based on inspection document definition information that defines the type of the design document information included in the inspection document for each system, information related to the system and the equipment is integrated to create the inspection document. The construction management method according to claim 9.

11. The facility information identifies the system and the device with unique tags; The design document information and the inspection document definition information are associated with the tag, The device connected to the grid is identified based on the tag; Information relating to the system and the equipment is extracted from the design document information based on the tags. The construction management method according to claim 10.

12. providing information for determining whether or not to carry out an inspection of the system based on process information relating to a construction process of the facility and the facility information; The construction management method according to any one of claims 9 to 11.

13. Identifying the work having a dependency relationship with the test for which the possibility of execution is to be determined based on test dependency relationship information that defines, for each device, the work having a dependency relationship with the test of the system; providing information for checking the process related to the identified work from the process information and determining whether or not the work can be carried out; The construction management method according to claim 12.

14. Acquire the equipment inspection format of the equipment connected to the system from inspection format information that defines an equipment inspection format used when inspecting the equipment for each of the equipment; Creating a test format to be used when testing the system; The construction management method according to any one of claims 9 to 11.

15. collecting input of results of the test of the system input based on the test format; The construction management method according to claim 14.

16. Collecting the approval input of an approver together with the result input of the system test; The construction management method according to claim 15.