Construction planning device, construction planning method, and construction planning program

Abstract

A construction plan planning device (100) for drafting a construction plan for a plurality of facilities comprises a facility group generation unit (120) and an execution pattern generation unit (130). The facility group generation unit (120) generates each facility group comprising a series of facilities that can each be reached by tracing an adjacency relationship indicated by influence range data indicating the adjacency relationship between the two facilities among the plurality of facilities. The execution pattern generation unit (130) generates execution pattern data (131) indicating one or more execution patterns each of which comprehensively indicates each construction corresponding to each facility included in a target facility group on the basis of influence range data (53), construction data (51) indicating each work corresponding to each construction corresponding to each facility included in the target facility group, and common work data (52) indicating each work that can be shared among the plurality of works, where the target facility group is assumed to be each facility group of the generated one or more facility groups.

Description

Construction planning device, construction planning method, and construction planning program

[0001] The present disclosure relates to a construction planning device, a construction planning method, and a construction planning program.

[0002] When planning construction work for social infrastructure facilities, construction work is assigned to workers taking into consideration various factors such as the priority of the work and the skills possessed by the workers, and a plan is drawn up to minimize the time and number of workers required for the work (hereafter referred to as cost). In this case, costs associated with multiple construction works can be reduced by carrying out multiple construction works at the same time. As a specific example, on highways, by carrying out adjacent construction works simultaneously, costs can be reduced by sharing the work related to multiple facilities (construction applications, traffic maintenance, etc.).

[0003] Japanese Patent Application Laid-Open No. 2015-215759

[0004] The technology disclosed in Patent Document 1 can take into consideration the reduction of opportunity losses such as road closures caused by the simultaneous execution of multiple construction projects. However, since this technology does not use information indicating work that can be shared among multiple construction projects, it is not possible to take into consideration the reduction of work such as traffic improvement and construction application that can be shared among multiple construction projects.

[0005] The purpose of the present disclosure is to enable consideration of which tasks can be shared when multiple construction projects are carried out simultaneously by utilizing information (common task data) indicating tasks that can be shared among multiple construction projects.

[0006] The construction planning device according to the present disclosure is a construction planning device for planning construction plans for a plurality of facilities, and includes: an equipment group generation unit that generates one or more equipment groups by generating equipment groups consisting of each series of facilities that can be reached by tracing the adjacency relationships indicated by impact range data indicating the adjacency relationships between two facilities among the plurality of facilities; and an execution pattern generation unit that, when each of the one or more generated equipment groups is set as a target equipment group, generates execution pattern data that indicates one or more execution patterns that each comprehensively indicates each construction work corresponding to each facility included in the target equipment group based on the impact range data, construction data that indicates each task corresponding to each construction work corresponding to each facility included in the target equipment group, and common task data that indicates each task that can be common among a plurality of construction works.

[0007] According to the present disclosure, the execution pattern generation unit generates execution pattern data that comprehensively indicates each construction project based on the common task data. Therefore, according to the present disclosure, by using information (common task data) that indicates tasks that can be shared among multiple construction projects, it is possible to consider which tasks can be shared when multiple construction projects are performed simultaneously.

[0008] FIG. 1 is a diagram showing an example of the configuration of a construction planning system 90 according to the first embodiment. FIG. 2 is a diagram showing a specific example of construction data 51 according to the first embodiment. FIG. 3 is a diagram showing a specific example of common task data 52 according to the first embodiment. FIG. 4 is a diagram explaining impact range data 53 according to the first embodiment, where (a) is a schematic diagram of each facility and its adjacent relationships, and (b) is a table showing the impact range data 53. FIG. 5 is a diagram showing a specific example of group data 121 according to the first embodiment. FIG. 6 is a diagram explaining the processing of an execution pattern generation unit 130 according to the first embodiment. FIG. 7 is a flowchart showing the operation of a construction planning device 100 according to the first embodiment. FIG. 8 is a flowchart showing the operation of a facility group generation unit 120 according to the first embodiment. FIG. 9 is a flowchart showing the operation of an execution pattern generation unit 130 according to the first embodiment. FIG. 10 is a diagram showing an example of the hardware configuration of a construction planning device 100 according to a modification of the first embodiment. FIG. 11 is a diagram showing an example of the configuration of a construction planning system 90 according to the second embodiment. FIG. 11 is a diagram explaining a specific example of construction candidate data 211 according to the second embodiment. 10A to 10C are diagrams for explaining the processing of the construction candidate generation unit 210 according to the second embodiment, where (a) is a diagram for explaining "parallel," (b) is a diagram for explaining "series," and (c) is a diagram for explaining "single." FIG. 10B is a flowchart showing the operation of the construction candidate generation unit 210 according to the second embodiment. FIG. 10C is a flowchart showing the operation of the construction candidate generation unit 210 according to the second embodiment. FIG. 10D is a diagram showing an example of the configuration of the construction planning system 90 according to the third embodiment. FIG. 10E is a diagram showing a specific example of worker data 54 according to the third embodiment. FIG. 10F is a flowchart showing the operation of the construction planning device 100 according to the third embodiment. FIG. 10F is a flowchart showing the operation of the construction plan generation unit 310 according to the third embodiment. FIG. 10F is a diagram showing an example of the configuration of the construction planning system 90 according to the fourth embodiment. FIG. 10F is a diagram showing a specific example of construction-related data 56 according to the fourth embodiment. FIG. 10F is a flowchart showing the operation of the construction candidate generation unit 210 according to the fourth embodiment. FIG. 10F is a diagram showing an example of the configuration of the construction planning system 90 according to the fifth embodiment. FIG. 10F is a diagram showing the processing of the priority generation unit 510 according to the fifth embodiment. FIG. 10F is a flowchart showing the operation of the construction planning device 100 according to the fifth embodiment. Fig. 10 is a flowchart showing the operation of a priority generation unit 510 according to embodiment 5. Fig. 11 is a diagram showing an example of the configuration of a construction planning system 90 according to embodiment 6. Fig. 12 is a diagram showing a specific example of inspection data 57 according to embodiment 6.13 is a flowchart showing the operation of a priority generation unit 510 according to the sixth embodiment.

[0009] In the description of the embodiments and the drawings, the same elements and corresponding elements are given the same reference numerals. The description of elements given the same reference numerals will be omitted or simplified as appropriate. Arrows in the drawings mainly indicate the flow of data or the flow of processing. Furthermore, "unit" may be read as "circuit," "step," "procedure," "process," or "circuitry" as appropriate.

[0010] First Embodiment Hereinafter, the present embodiment will be described in detail with reference to the drawings.

[0011] ***Description of Configuration*** Fig. 1 shows an example of the configuration of a construction planning system 90 according to this embodiment. As shown in the figure, the construction planning system 90 includes a construction planning device 100.

[0012] The construction planning device 100 includes, as functional components, a data acquisition unit 110, a facility group generation unit 120, an execution pattern generation unit 130, and a result output unit 140. The construction planning device 100 is a device for creating construction plans for a plurality of facilities, each of which is a construction target.

[0013] The data acquisition unit 110 acquires construction data 51 , common task data 52 , and impact range data 53 .

[0014] The construction data 51 is data indicating the details of each construction work. As a specific example, the construction data 51 is composed of information indicating, for each construction work, the equipment that is the target of the construction work, the details of the construction work, the construction time, the number of workers required for the construction work, etc. FIG. 2 shows a specific example of the construction data 51. In FIG. 2, a "construction ID" is assigned as an identifier to each construction work. The "equipment name" corresponds to the equipment that is the target of the construction work, the "construction type" corresponds to the classification of the construction work, the "required time" corresponds to the construction time, and the "required number of workers" corresponds to the number of workers required for the construction work.

[0015] The common task data 52 is data indicating each task that can be shared among multiple construction projects. The common task data 52, as a specific example, includes information indicating each task that can be shared and performed among multiple construction projects, and each construction project on which each task that can be shared and performed is performed. FIG. 3 shows a specific example of the common task data 52. In FIG. 3, for each task that can be shared and performed, a "task ID," a "task type," a "corresponding construction type," a "required time," a "required number of people," and a "task timing" are shown. The "task ID" indicates an identifier assigned to the common task. The "task type" indicates the classification corresponding to the common task. The "corresponding construction type" indicates the classification of each construction project on which the common task is performed. The "required time" indicates the time required to perform the common task. The "required number of people" indicates the number of workers required to perform the common task. The "task timing" is the timing for the construction project corresponding to the common task, and indicates the timing for performing the common task. Note that the "task timing" may occur after the corresponding construction project is completed.

[0016] The impact range data 53 includes information indicating the adjacency relationship between two pieces of equipment. Here, the adjacency relationship between pieces of equipment is defined based on whether or not there is a common task that can be shared and performed between a set of pieces of equipment. Specifically, the adjacency relationship is defined based on the distance between the pieces of equipment or the access method to each piece of equipment. FIG. 4 is a diagram illustrating the impact range data 53. In FIG. 4, each piece of equipment is a tunnel. (a) in FIG. 4 is a schematic diagram of each piece of equipment and its adjacency relationship. In FIG. 4(a), two tunnels are connected by a line when they have an adjacency relationship. As a specific example, tunnels A and B are adjacent to each other on a single road. Furthermore, the road on which tunnel D exists is different from the road on which tunnels A, B, and C exist. (b) in FIG. 4(a) shows a specific example of the impact range data 53 corresponding to (a) in FIG. 4(a). In (b) in FIG. 4(b), for each piece of equipment, a "1" is indicated if the pair of equipment has an adjacency relationship, and a "0" is indicated if the pair of equipment does not have an adjacency relationship. Here, a facility set consists of two facilities. If a facility set has an adjacent relationship, when construction work associated with each facility included in the facility set is carried out simultaneously, it is possible to share and execute common work corresponding to the facility set. Furthermore, when two facility sets share one facility included in each facility set, when construction work associated with each facility included in the two facility sets is carried out simultaneously, it may be possible to share and execute common work for all facilities included in the two facility sets. As a specific example, in FIG. 4, when two facility sets consist of a facility set consisting of tunnel A and tunnel B and a facility set consisting of tunnel B and tunnel C, tunnel B is common to the two facility sets. Note that two facilities on a branched route have no relationship between them, and therefore it is considered impossible to share common work. As a specific example, tunnels C and D are two facilities on a branched route.

[0017] The facility group generation unit 120 generates one or more facility groups. Each facility group is made up of a series of facilities that can be reached by tracing the adjacent relationships indicated by the impact range data 53. As a specific example, the facility group generation unit 120 organizes a series of facilities that can be reached based on the adjacent relationships indicated by the impact range data 53 into facility groups, and further generates group data 121 by extracting each construction project linked to each facility included in each facility group.

[0018] Group data 121 indicates a group of equipment that can share and execute a common task. FIG. 5 shows a specific example of group data 121 corresponding to FIGS. 2 to 4. In FIG. 5, each equipment group is shown corresponding to each corresponding piece of equipment and each construction project. "Group ID" indicates an identifier assigned to the equipment group. "Equipment ID List" indicates a list of identifiers for equipment that constitute each equipment group. Here, tunnels A, B, and C are a series of equipment that can be reached based on the adjacency relationships indicated by the impact range data 53. Therefore, tunnels A, B, and C are grouped together in one equipment group. On the other hand, tunnel D cannot be reached from any of tunnels A, B, and C based on the adjacency relationships indicated by the impact range data 53. Therefore, tunnel D is not included in group 1. "Construction ID List" indicates a list of construction project identifiers corresponding to each piece of equipment that constitutes each equipment group. Here, construction project 1 is linked to tunnel A, construction project 2 is linked to tunnel B, and construction project 3 is linked to tunnel C. Therefore, for group 1, the "construction ID list" includes construction 1, construction 2, and construction 3.

[0019] When each of the one or more generated equipment groups is designated as a target equipment group, the execution pattern generation unit 130 generates execution pattern data 131 based on the impact range data 53, construction data 51, and common task data 52. The construction data 51 indicates each task corresponding to each construction work corresponding to each piece of equipment included in the target equipment group. As a specific example, the execution pattern generation unit 130 calculates an execution pattern for executing all construction work included in each equipment group based on the group data 121, impact range data 53, construction data 51, and common task data 52. The execution pattern generation unit 130 then generates execution pattern data 131 indicating the calculated execution pattern. The execution pattern is determined according to each combination of reachable equipment based on the adjacency relationships indicated by the impact range data 53.

[0020] The execution pattern data 131 indicates each execution pattern of construction work for comprehensively executing all construction work associated with the equipment for each equipment group. The execution pattern data 131 indicates one or more execution patterns, each of which comprehensively indicates each construction work corresponding to each equipment included in the target equipment group. When each execution pattern indicated by the execution pattern data 131 is defined as a target execution pattern, the target execution pattern indicates data indicating one or more construction work corresponding to one or more equipment selected based on the adjacent relationship indicated by the impact range data 53 from among the construction work corresponding to each equipment included in the target equipment group. Furthermore, when the one or more construction work indicated by the target execution pattern alone does not cover all the construction work corresponding to each equipment included in the target equipment group, the target execution pattern indicates one or more execution patterns from among the execution patterns indicated by the execution pattern data 131, indicating each construction work that should be performed to cover all the construction work corresponding to each equipment included in the target equipment group. Figure 6 is a diagram corresponding to Figures 2 to 5 and explains the processing of the execution pattern generation unit 130. In FIG. 6 , the execution pattern data 131 indicates a "facility group," a "construction ID list," a "task ID list," and a "complementary pattern list" for each execution pattern. Note that for group 1, multiple patterns can be generated based on the adjacency relationship. On the other hand, for group 2, there is only one corresponding facility, so there is only one execution pattern. The "pattern ID" indicates the identifier assigned to each execution pattern. The "facility group" indicates the facility group corresponding to each execution pattern. The "construction ID list" indicates a list of identifiers for one or more construction projects corresponding to each facility that constitutes each facility group, selected within a reachable range based on the adjacency relationship. Here, tunnels A and B have an adjacency relationship. Therefore, tunnels A and B are a combination of facilities that are reachable based on the adjacency relationship indicated by the impact range data 53. Therefore, for pattern ID 2, only construction projects 1 and 2 corresponding to tunnels A and B, respectively, are shown in the "construction ID list." On the other hand, tunnels A and C do not have an adjacency relationship.Therefore, tunnels A and C are not a combination of facilities that can be reached based on the adjacency relationship indicated by the impact range data 53. Therefore, only works 1 and 3 corresponding to tunnels A and C, respectively, are not shown in the "Work ID List." The "Work ID List" shows a list of identifiers for common tasks performed in each work indicated by the "Work ID List." The "Supplementary Pattern List" shows a list of identifiers for execution patterns indicating the remaining works that need to be performed to cover all works corresponding to the equipment groups listed in the "Equipment Group." In the "Supplementary Pattern List" corresponding to the target execution pattern, if one or more works indicated by the target execution pattern alone do not cover each work corresponding to each piece of equipment included in the target equipment group, one or more execution patterns indicated by the execution pattern data 131 are shown, indicating each work that needs to be performed to cover each piece of equipment included in the target equipment group. Note that if multiple execution patterns need to be executed, a group consisting of identifiers corresponding to each execution pattern of the multiple execution patterns is shown in the "Supplementary Pattern List." Furthermore, for each execution pattern, the list of execution pattern identifiers shown in the "Supplementary Pattern List" is not necessarily unique. As a specific example, for pattern ID 4, work 1 and work 2 must be carried out as the remaining work for group 1. Here, work 1 and work 2 will be carried out even if pattern ID 3 is executed, and work 1 and work 2 will also be carried out even if pattern ID 5 and pattern ID 6 are executed. Therefore, [3] and [5, 6] are shown as the "complementary pattern list" corresponding to pattern ID 4.

[0021] An example of the hardware configuration of the construction planning device 100 will be described with reference to Fig. 1. The construction planning device 100 is composed of a computer. The construction planning device 100 may be composed of multiple computers.

[0022] 1, the construction planning device 100 is a computer including hardware such as a processor 11, a storage device 12, an auxiliary storage device 13, an input interface 14, and a communication device 15. These pieces of hardware are connected to each other via signal lines.

[0023] The processor 11 is an integrated circuit (IC) that performs arithmetic processing and controls the hardware of the computer. Specific examples of the processor 11 include a central processing unit (CPU), a digital signal processor (DSP), or a graphics processing unit (GPU). The construction plan planning device 100 may include multiple processors that replace the processor 11. The multiple processors share the role of the processor 11.

[0024] The storage device 12 is typically a volatile storage device, and a specific example is RAM (Random Access Memory). The storage device 12 is also called a primary storage device or a main memory. Data stored in the storage device 12 is saved in the auxiliary storage device 13 as needed.

[0025] The auxiliary storage device 13 is typically a non-volatile storage device, and specific examples thereof include a ROM (Read Only Memory), an HDD (Hard Disk Drive), or a flash memory. Data stored in the auxiliary storage device 13 is loaded into the storage device 12 as needed. The storage device 12 and the auxiliary storage device 13 may be configured integrally.

[0026] The input interface 14 is a port to which an input device and an output device are connected. A specific example of the input interface 14 is a USB (Universal Serial Bus) terminal. Specific examples of the input device are a keyboard and a mouse. A specific example of the output device is a display.

[0027] The communication device 15 is a receiver and a transmitter, and is specifically a communication chip or a NIC (Network Interface Card).

[0028] Each part of the construction planning device 100 may use the input interface 14 and the communication device 15 as appropriate when communicating with other devices.

[0029] The auxiliary storage device 13 stores a construction planning program. The construction planning program is a program that causes a computer to realize the functions of each unit included in the construction planning device 100. The construction planning program is loaded into the storage device 12 and executed by the processor 11. The functions of each unit included in the construction planning device 100 are realized by software.

[0030] Data used when executing the construction planning program and data obtained by executing the construction planning program are stored in a storage device as appropriate. Each part of the construction planning device 100 uses a storage device as appropriate. As a specific example, the storage device comprises at least one of the storage device 12, the auxiliary storage device 13, a register in the processor 11, and a cache memory in the processor 11. Note that the terms "data" and "information" may have the same meaning. The storage device may be independent of the computer. The functions of the storage device 12 and the auxiliary storage device 13 may be realized by other storage devices.

[0031] The construction planning program may be recorded on a computer-readable non-volatile recording medium. Specific examples of the non-volatile recording medium include an optical disk and a flash memory. The construction planning program may be provided as a program product.

[0032] ***Description of Operation*** The operation procedure of the construction planning device 100 corresponds to a construction planning method. Also, the program that realizes the operation of the construction planning device 100 corresponds to a construction planning program.

[0033] 7 is a flowchart showing an example of the operation of the construction planning device 100. The operation of the construction planning device 100 will be described with reference to FIG.

[0034] (Step S11 ) The data acquisition unit 110 acquires the construction data 51 , the common task data 52 , and the affected area data 53 .

[0035] (Step S12 ) The facility group generation unit 120 generates group data 121 based on the construction data 51 and the affected area data 53 acquired by the data acquisition unit 110 .

[0036] (Step S13 ) The execution pattern generation unit 130 generates execution pattern data 131 based on the group data 121 , the construction data 51 , and the affected area data 53 .

[0037] (Step S14) The result output unit 140 outputs the execution pattern data 131 generated by the execution pattern generation unit 130. As a specific example, the result output unit 140 displays the combinations of facilities and construction works included in the execution pattern data 131 on a display (not shown).

[0038] 8 is a flowchart showing an example of the operation of the facility group generation unit 120 in step S12. This operation will be described with reference to FIG.

[0039] (Step S12.1) The facility group generation unit 120 extracts, as one group, all facilities that can be reached by tracing the adjacency relationships based on the influence range data 53. The facility group generation unit 120 continues extracting groups until all facilities indicated by the influence range data 53 belong to one of the groups.

[0040] (Step S12.2) For each extracted group, the facility group generation unit 120 extracts all the construction work that needs to be performed on the facilities belonging to the group based on the construction work data 51. The facility group generation unit 120 generates group data 121 based on the extracted groups and construction work.

[0041] 9 is a flowchart showing an example of the operation of the execution pattern generating unit 130 in step S13. This operation will be described with reference to FIG.

[0042] (Step S13.1) The execution pattern generation unit 130 treats each group indicated by the group data 121 as a target group, and extracts each combination of construction works belonging to the target group as an execution pattern based on the equipment and construction works belonging to the target group and the impact range data 53. Note that the execution pattern generation unit 130 does not extract, as an execution pattern, construction works corresponding to equipment that cannot be reached without tracing the adjacent relationships indicated by the impact range data 53, i.e., equipment that does not have a direct adjacent relationship. This step corresponds to the process of generating a "construction ID list."

[0043] (Step S13.2) For each extracted execution pattern, the execution pattern generation unit 130 extracts common tasks associated with each construction project belonging to the execution pattern. This step corresponds to the process of generating a "task ID list."

[0044] (Step S13.3) For each extracted execution pattern, the execution pattern generation unit 130 identifies other execution patterns that are complementary to each other so that all construction works corresponding to the execution pattern can be executed based on the construction works belonging to the facility group corresponding to the execution pattern. This step corresponds to the process of generating a "complementary pattern list."

[0045] ***Explanation of Effects of First Embodiment*** As described above, according to this embodiment, data is generated that indicates an execution pattern that takes into account the simultaneous execution of multiple construction projects, including tasks that can be shared. Therefore, by utilizing this embodiment, it is possible to create a construction plan that takes into account the reduction of tasks that can be shared and that includes all construction projects without omission.

[0046] ***Other Configurations*** <Modification 1> Fig. 10 shows an example of the hardware configuration of the construction planning device 100 according to this modification. The construction planning device 100 includes a processing circuit 18 instead of the processor 11, the processor 11 and the storage device 12, the processor 11 and the auxiliary storage device 13, or the processor 11, the storage device 12, and the auxiliary storage device 13. The processing circuit 18 is hardware that realizes at least a part of the components included in the construction planning device 100. The processing circuit 18 may be dedicated hardware, or may be a processor that executes a program stored in the storage device 12.

[0047] When the processing circuitry 18 is dedicated hardware, the processing circuitry 18 is, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof. The construction plan planning device 100 may be provided with multiple processing circuits that replace the processing circuitry 18. The multiple processing circuits share the role of the processing circuitry 18.

[0048] In the construction planning device 100, some functions may be realized by dedicated hardware, and the remaining functions may be realized by software or firmware.

[0049] The processing circuitry 18 is realized by, for example, hardware, software, firmware, or a combination of these. The processor 11, the storage device 12, the auxiliary storage device 13, and the processing circuitry 18 are collectively referred to as the "processing circuitry." In other words, the functions of the functional components of the construction plan planning device 100 are realized by the processing circuitry. Construction plan planning devices 100 according to other embodiments may also have the same configuration as this modification.

[0050] Second Embodiment The following mainly describes the differences from the above-described embodiment with reference to the drawings.

[0051] ***Description of Configuration*** Fig. 11 shows an example of the configuration of a construction plan planning system 90 according to this embodiment. The construction plan planning device 100 according to this embodiment further includes a construction candidate generation unit 210 as a functional component. The result output unit 140 according to this embodiment outputs construction candidate data 211 instead of the execution pattern data 131.

[0052] When each execution pattern indicated by the execution pattern data 131 is set as a target execution pattern, the work candidate generation unit 210 generates work candidates corresponding to the target execution pattern for each execution method of the work indicated by the target execution pattern based on the target execution pattern. As a specific example, the work candidate generation unit 210 generates work candidate data 211 based on the work data 51, the common task data 52, and the execution pattern data 131. As a specific example, for each combination of a "work ID list" indicated by the execution pattern data 131 and an "execution method" related to the "work ID list," the work candidate generation unit 210 generates work candidate data 211 indicating information necessary for the work plan (required time and required number of personnel) and combinations for performing all the work (complementary work candidate list). The "execution method" indicates the execution method of one or more work indicated by the corresponding work ID list. As a specific example, the "execution method" is information corresponding to the execution order, and is one of "parallel (simultaneous)," "serial (continuous)," and "single (individual)." "Parallel" means that multiple work projects are performed simultaneously. In addition, when the "Execution Method" for multiple construction works is "Parallel," it is not necessary for all of the multiple construction works to always be executed simultaneously. "Serial" means that multiple construction works are not executed simultaneously, but are executed consecutively. "Single" means that one construction work is executed.

[0053] FIG. 12 shows a specific example of the construction candidate data 211. When the "construction ID list" indicated by the execution pattern data 131 contains multiple construction IDs, the corresponding "execution method" can be parallel or serial. On the other hand, when the "construction ID list" contains only one construction ID, there is no room for devising an execution method, so a construction candidate is generated with the "execution method" field left blank. This blank field indicates "single." The "required time" and "required number of people" are values ​​calculated based on the "execution method," the "construction ID list," and the "task ID list." The values ​​of the "complementary construction candidate list" are calculated by converting each pattern ID indicated by the "complementary pattern list" indicated by the execution pattern data 131 into the construction candidate ID corresponding to each pattern ID. Each element indicated by the "complementary construction candidate list" corresponds to a construction candidate group. In other words, [6] and [8, 9] each correspond to a construction candidate group. A construction candidate group indicates one or more construction candidates.

[0054] FIG. 13 shows a specific example of a method for calculating the "required time" and "required number of workers" for each execution method. For each construction project and each task, the timing of the execution of the process, the duration of the process, and the number of workers required for the process are shown. Even if the "construction ID list" and "task ID list" are the same for each construction project candidate, the "required time" and "required number of workers" may differ depending on the "execution method." In this example, the "required number of workers" is calculated as the maximum total number of workers required for each construction project and task during a period in which multiple processes are executed in parallel. (a) of FIG. 13 shows a specific example when the "execution method" for construction projects 1 and 2 is parallel. In this example, the "required time" is 6 hours and the "required number of workers" is 10. (b) of FIG. 13 shows a specific example when the "execution method" for construction projects 1 and 2 is serial. In this example, the "required time" is 10 hours and the "required number of workers" is 6. 13(c) shows a specific example in which construction 1 is carried out by a single person. In this example, the "required time" is 5 hours and the "required number of people" is 6 people.

[0055] ***Explanation of Operation*** Fig. 14 is a flowchart showing an example of the operation of the construction planning device 100. The operation of the construction planning device 100 will be described with reference to Fig. 14 .

[0056] (Step S24) Based on the construction data 51, the common work data 52, and the execution pattern data 131, the construction candidate generation unit 210 determines, for each execution pattern, the "execution method" of each construction work associated with the execution pattern, and generates construction candidate data 211 that shows information regarding the construction of all construction works corresponding to the execution pattern.

[0057] (Step S25) The result output unit 140 outputs the construction candidate data 211 generated by the construction candidate generation unit 210. The output method is the same as in step S14.

[0058] 15 is a flowchart showing an example of the operation of the construction candidate generator 210 in step S24. This operation will be described with reference to FIG.

[0059] (Step S24.1) The construction candidate generator 210 generates construction candidate plans for each execution method based on the execution pattern data 131. Here, when one execution pattern includes two or more construction projects, the "execution method" can be either parallel or serial. When one execution pattern includes one construction project, the "execution method" can be either single or serial.

[0060] (Step S24.2) For each construction candidate, the construction candidate generation unit 210 calculates the work time and number of workers required to carry out the construction candidate based on the construction and common work corresponding to the construction candidate, taking into account the execution method.

[0061] (Step S24.3) Based on the construction candidates and the execution pattern, the construction candidate generator 210 extracts complementary relationships between the construction candidates for executing all of the construction works linked to the execution pattern.

[0062] ***Explanation of the Effects of Embodiment 2*** As described above, according to this embodiment, by setting an execution method for each execution pattern, it is possible to generate construction candidate works for a variety of execution patterns, and it is also possible to clarify the required time and number of people for each construction candidate work. Therefore, by utilizing this embodiment, it is possible to create construction plans that require relatively little time and number of people.

[0063] Third Embodiment Hereinafter, differences from the above-described embodiments will be mainly described with reference to the drawings.

[0064] *** Description of Configuration *** Fig. 16 shows an example of the configuration of a construction planning system 90 according to this embodiment. The construction planning device 100 according to this embodiment further includes a construction plan generation unit 310 as a functional component. The data acquisition unit 110 according to this embodiment further acquires worker data 54 and objective function data 55. The result output unit 140 outputs construction plan data 311 instead of the construction candidate data 211.

[0065] The worker data 54 is information indicating candidate workers to be assigned to each construction project, and is made up of information corresponding to workers who can be assigned to each construction project. Specific examples of the information corresponding to workers include information indicating the start time, end time, and qualifications of each worker. FIG. 17 shows a specific example of the worker data 54.

[0066] The objective function data 55 is made up of information for determining whether the construction plan is good or bad. As a specific example, the objective function data 55 indicates an objective function, where the number of workers assigned to the construction plan is N, and the working time of worker n is T ｎ In this case, the objective function is expressed as follows:

[0067]

[0068] The construction plan generation unit 310 generates construction plans corresponding to multiple facilities based on each construction candidate generated by the construction candidate generation unit 210, the worker data 54, and an objective function for evaluating the construction plans. For each target facility group, the construction plan generated by the construction plan generation unit 310 indicates each construction project corresponding to each facility included in the target facility group. As a specific example, the construction plan generation unit 310 generates combinations of construction candidates based on the construction candidate data 211 so that all construction projects corresponding to the facility group are carried out once, and formulates construction plans based on each generated combination. In this case, when a combination of each construction candidate is treated as a target combination, the construction plan generation unit 310 generates target combinations based on the construction candidate data 211 so that the target combination satisfies the following three conditions: For the construction candidate data 211 shown in Figure 12, when the construction plan generation unit 310 generates combinations of construction candidates so as to satisfy the following three conditions, the combinations of construction candidates generated are [1, 10], [2, 10], [3, 9, 10], [4, 9, 10], [5, 7, 10], [6, 7, 10], and [7, 8, 9, 10].

[0069] Condition 1: When each type of "equipment group" is set as the target group type, for each target group type, at least one construction candidate corresponding to the target group type must be included in the target combination. Condition 2: When a construction candidate that does not have a value in the corresponding "supplementary construction candidate list" is set as the target construction candidate, if the target construction candidate is to be included in the target combination, construction candidates that correspond to the same "equipment group" as the "equipment group" that corresponds to the target construction candidate must not be included in the target combination. Condition 3: When a construction candidate that has a value in the corresponding "supplementary construction candidate list" is set as the target construction candidate, if the target construction candidate is to be included in the target combination, all construction candidates indicated by any one of the construction candidate groups included in the "supplementary construction candidate list" that corresponds to the target construction candidate must be included in the target combination.

[0070] The construction plan generator 310 assigns workers to each combination of construction candidates so as not to exceed the number of workers available for each time period, based on the worker data 54 and the objective function data 55. The construction plan generator 310 then adopts the construction plan corresponding to the combination of construction candidates with the best objective function value.

[0071] ***Explanation of Operation*** Fig. 18 is a flowchart showing an example of the operation of the construction planning device 100. The operation of the construction planning device 100 will be described with reference to Fig. 18 .

[0072] (Step S31) The data acquisition unit 110 acquires worker data 54 and objective function data 55 in addition to the data acquired in step S11.

[0073] (Step S35) Based on the construction candidate data 211, the worker data 54, and the objective function data 55, the construction plan generation unit 310 creates construction plan data 311 in which the worker assignment and patrol order, etc. are set so that the objective function indicated by the objective function data 55 is minimized or maximized.

[0074] (Step S36) The result output unit 140 outputs the construction plan data 311 generated by the construction plan generation unit 310. The output method is the same as in step S14.

[0075] 19 is a flowchart showing an example of the operation of the construction plan generating unit 310 in step S35. This operation will be described with reference to FIG.

[0076] (Step S35.1) The construction work plan generating unit 310 generates a combination of construction work candidates so as to execute all construction work corresponding to each facility group.

[0077] (Step S35.2) Based on the generated combinations of construction candidates, the worker data 54, and the objective function data 55, the construction plan generation unit 310 formulates a construction plan for each combination of construction candidates so that the corresponding objective function value is maximized (or minimized).

[0078] (Step S35.3) The construction plan generation unit 310 compares the objective function values ​​corresponding to each construction plan created from the combination of each construction candidate, selects the construction plan with the maximum (or minimum) objective function value, and sets the selected construction plan as the final construction plan.

[0079] ***Explanation of Effects of Embodiment 3*** As described above, according to this embodiment, construction plans corresponding to various execution patterns are created taking into account the corresponding objective function values. Therefore, according to this embodiment, construction plans corresponding to small (or large) objective function values ​​can be created.

[0080] Fourth Embodiment Hereinafter, differences from the above-described embodiments will be mainly described with reference to the drawings.

[0081] 20 shows an example of the configuration of a construction planning system 90 according to this embodiment. The data acquisition unit 110 according to this embodiment further acquires construction-related data 56.

[0082] The construction-related data 56 is data indicating constraints on the construction data 51 and the common work data 52. The construction-related data 56 indicates constraints that must be met when carrying out each construction work corresponding to each piece of equipment included in the target equipment group. Specific examples of constraints include required qualifications (qualifications that must be held by the workers who carry out the construction work), delivery dates (dates and times when the construction work must be completed), and construction permission periods (periods during which the construction work can be carried out). Figure 21 shows a specific example of the construction-related data 56. In Figure 21, constraints are shown for each construction work and task.

[0083] The construction candidate generation unit 210 according to this embodiment adds information indicated by the construction-related data 56 to the construction candidate data 211. Furthermore, the construction candidate generation unit 210 excludes, from among the generated construction candidates, construction candidates that do not satisfy the constraints corresponding to each construction corresponding to each facility included in the target facility group. As a specific example, if construction-related data 56 indicating conflicting constraints is added to a construction candidate for which multiple corresponding construction projects exist, the construction candidate generation unit 210 deletes the construction candidate. FIG. 22 shows a specific example of construction candidate data 211 to which construction-related data 56 has been added. For a certain construction candidate, as shown in FIG. 22 , if there is no overlapping period between the two specified construction permission periods, or if there is an overlapping period but the construction will not be completed by the specified deadline, construction of the certain construction candidate is impossible. Therefore, the construction candidate generation unit 210 deletes the certain construction candidate from the construction candidate data 211.

[0084] In addition to the above-mentioned functions, the construction plan generating unit 310 according to this embodiment has a function of formulating construction plan data 311 so as to satisfy the constraints indicated by the construction-related data 56 .

[0085] ***Description of Operation*** The flowchart showing the operation of the construction planning device 100 according to the present embodiment is similar to the flowchart showing the operation of the construction planning device 100 according to embodiment 3. The differences between the operation of the construction planning device 100 according to the present embodiment and embodiment 3 will be described.

[0086] (Step S31) The data acquisition unit 110 acquires construction-related data 56 in addition to the data acquired in step S31 according to the third embodiment.

[0087] (Step S24) This step is the same as step S24 according to the third embodiment, except that the construction candidate generator 210 uses the construction-related data 56 when generating the construction candidate data 211.

[0088] (Step S35) This step is the same as step S35 according to the third embodiment, except that the construction plan generating unit 310 uses the construction-related data 56 when formulating the construction plan data 311.

[0089] 23 is a flowchart showing an example of the operation of the construction candidate generator 210 in step S24. This operation will be described with reference to FIG.

[0090] (Step S44.3) The construction candidate generator 210 assigns constraints to each construction candidate based on the construction candidate and the construction-related data 56, the constraints being imposed on the construction of each construction candidate.

[0091] ***Explanation of Effects of the Fourth Embodiment*** As described above, according to this embodiment, construction candidates that do not need to be considered when creating a construction plan are eliminated based on constraints. Furthermore, according to this embodiment, since constraints on construction can be added, more complex construction plans can be created.

[0092] Fifth Embodiment Hereinafter, differences from the above-described embodiments will be mainly described with reference to the drawings.

[0093] 24 shows an example of the configuration of an construction planning system 90 according to this embodiment. The construction planning device 100 according to this embodiment further includes a priority generation unit 510 as a functional component.

[0094] The priority generation unit 510 generates a priority for each construction project corresponding to each facility included in the target facility group based on the construction-related data 56. The priority generation unit 510 determines a priority for each construction project indicated by the construction plan data 311. The priority generation unit 510 then determines the construction project to be completed for each period based on the determined priority and information indicating the upper limit of the number of construction projects that can be completed in each period. The construction project to be completed is the construction project to be executed. As a specific example, when the priority generation unit 510 uses the delivery date corresponding to each construction project as the priority corresponding to each construction project, it sorts each construction project indicated by the construction-related data 56 based on the value indicated in the "Delivery Date" column of the construction-related data 56. Furthermore, if an upper limit of the number of construction projects that can be completed per specific period is set, the priority generation unit 510 selects construction projects to be completed in descending order from the top of the sorted construction-related data 56, using the upper limit as the upper limit. FIG. 25 shows a specific example of construction-related data 56 sorted based on delivery date. In this example, the upper limit of the number of construction projects that can be completed per specific period is two. Therefore, the top two of the three construction projects, i.e., construction project 2 and construction project 3, are selected as the construction projects to be carried out.

[0095] ***Explanation of Operation*** Fig. 26 is a flowchart showing an example of the operation of the construction planning device 100. The operation of the construction planning device 100 will be described with reference to Fig. 26 .

[0096] (Step S51) This step is the same as step S31 according to the fourth embodiment.

[0097] (Step S52) The priority generation unit 510 calculates a priority corresponding to each construction work to be carried out based on the construction-related data 56.

[0098] 27 is a flowchart showing an example of the operation of the priority generation unit 510 in step S52. This operation will be described with reference to FIG.

[0099] (Step S52.1) The priority generation unit 510 determines a priority for each construction project to be carried out based on the construction-related data 56. As a specific example, if the priority generation unit 510 treats delivery dates as priorities, it sorts the construction-related data 56 in ascending order based on delivery dates. In this example, each construction project is sorted in order of priority.

[0100] (Step S52.2) The priority generation unit 510 determines construction works to be executed from the construction works indicated by the construction plan data 311 based on the priorities determined in step S52.1.

[0101] ***Explanation of Effect of Embodiment 5*** As described above, according to this embodiment, the construction work to be carried out in each period is determined based on the priority corresponding to each construction work. Therefore, by utilizing this embodiment, when there is a large number of construction works and an upper limit is set on the number of construction works that can be carried out in a specific period, it is possible to determine which construction work should be given priority.

[0102] Sixth Embodiment Hereinafter, differences from the above-described embodiments will be mainly described with reference to the drawings.

[0103] 28 shows an example of the configuration of a construction planning system 90 according to this embodiment. The data acquisition unit 110 according to this embodiment further acquires inspection data 57 and deterioration model data 58.

[0104] The inspection data 57 is data showing the inspection results of each piece of equipment, and is data showing the inspection results corresponding to each piece of equipment included in the target equipment group. As a specific example, the inspection data 57 is made up of information showing, for each piece of equipment, the location where the inspection was performed, the time when the inspection was performed, and the soundness of the equipment at the time of the inspection. Figure 29 shows a specific example of the inspection data 57.

[0105] The deterioration model data 58 is data indicating a model for estimating the health of equipment. The deterioration model data 58 may indicate a model obtained from physical theory, or may indicate a statistical model obtained from actual data. As a specific example, the deterioration model data 58 is composed of information for estimating the health of equipment for each piece of equipment according to the inspection location and the time elapsed since the inspection. The health is an integer value indicating the normality of the equipment, and gradually decreases with age. [Equation 2] and [Equation 3] are specific examples of the deterioration model data 58. In this example, the health is expressed in five levels from 1 to 5. Health level 5 corresponds to a relatively good state, and health level 1 corresponds to a relatively bad state. [Equation 2] indicates the transition probability matrix P of the health in the Markov deterioration model. [Equation 3] indicates the risk cost R according to the health. Here, P ｎ，ｍ indicates the probability that the health level will transition from n to m in one year, and R ｎ denotes the risk cost when the health level is n.

[0106]

[0107] The priority generation unit 510 according to this embodiment estimates the degree of deterioration of each piece of equipment based on the inspection data 57, and generates a priority for each construction project corresponding to each piece of equipment included in the target equipment group based on the estimated degree of deterioration of each piece of equipment. As a specific example, the priority generation unit 510 calculates a priority for each construction project based on the degree of deterioration of each piece of equipment. A specific example of the processing of the priority generation unit 510 will be described below. First, the priority generation unit 510 calculates an estimate of the health of the equipment for each piece of inspection data 57 according to the time elapsed since the inspection. When the construction implementation year is m (m≧n), the priority generation unit 510 calculates the health as shown in [Equation 4]. Here, the health vector H ｃ，ｎ is a health vector for inspection year n at inspection location c of a certain facility, and is a five-dimensional vector in which the health level in past inspections is set to 1 (possible probability is 100%) and the others are set to 0 (possible probability is 0%). ｃ，ｍis the estimated health vector. The health vector is a vector that indicates the probability that each value of the five levels of health can take. As a specific example, when the health of the inspection location c of a certain piece of equipment at the time of inspection carried out in inspection year n is 4, H ｃ，ｎ = [0, 1, 0, 0, 0].

[0108]

[0109] Next, when the risk cost is R, the priority generation unit 510 calculates the cost C as shown in [Equation 5].

[0110]

[0111] Next, the priority generation unit 510 regards the calculated risk cost as a priority and sorts each construction project based on the priority of each facility c corresponding to each construction project. Thereafter, as in the fifth embodiment, the priority generation unit 510 determines construction projects to be carried out based on the upper limit of the number of construction projects that can be carried out per specific period.

[0112] ***Explanation of Operation*** The flowchart showing the operation of the construction planning device 100 according to the present embodiment is the same as the flowchart showing the operation of the construction planning device 100 according to embodiment 5. The differences between the operation of the construction planning device 100 according to the present embodiment and embodiment 5 will be described.

[0113] (Step S51) The data acquiring unit 110 further acquires inspection data 57 and deterioration model data 58 in addition to the data acquired in step S51 according to the fifth embodiment.

[0114] (Step S52) The priority generation unit 510 generates a priority corresponding to each construction work to be carried out based on the inspection data 57 and the deterioration model data 58.

[0115] 30 is a flowchart showing an example of the operation of the priority generation unit 510 in step S52. This operation will be described with reference to FIG.

[0116] (Step S62.1) The priority generation unit 510 calculates the health degree corresponding to the inspection data 57 based on the inspection data 57 and the deterioration model data 58. The health degree corresponding to the inspection data 57 may be a predicted value of the health degree based on the inspection data 57.

[0117] (Step S62.2) The priority generation unit 510 determines a priority for each construction project according to the health level estimated in S62.1. If a risk cost is set for each health level of each facility, the priority generation unit 510 may determine a priority for each construction project based on a value obtained by multiplying the health level by the risk cost.

[0118] ***Explanation of Effects of Embodiment 6*** As described above, according to this embodiment, the priority for each construction project is determined based on the degree of deterioration of the facility. Therefore, by utilizing this embodiment, it is possible to determine which construction project should be carried out with priority when some construction projects cannot be carried out due to constraints when planning the construction project.

[0119] ***Other Embodiments*** The above-described embodiments can be freely combined, or any of the components of each embodiment can be modified, or any of the components can be omitted from each embodiment. Furthermore, the embodiments are not limited to those shown in embodiments 1 to 6, and various modifications are possible as needed. The procedures described using flowcharts, etc., can be modified as appropriate.

[0120] 11 Processor, 12 Storage device, 13 Auxiliary storage device, 14 Input interface, 15 Communication device, 18 Processing circuit, 51 Construction data, 52 Common work data, 53 Impact range data, 54 Worker data, 55 Objective function data, 56 Construction-related data, 57 Inspection data, 58 Deterioration model data, 90 Construction planning system, 100 Construction planning device, 110 Data acquisition unit, 120 Equipment group generation unit, 121 Group data, 130 Execution pattern generation unit, 131 Execution pattern data, 140 Result output unit, 210 Construction candidate generation unit, 211 Construction candidate data, 310 Construction plan generation unit, 311 Construction plan data, 510 Priority generation unit.

Claims

1. A construction planning device for creating construction plans for multiple facilities, comprising: an equipment group generation unit that generates one or more equipment groups by generating equipment groups consisting of each series of facilities that can be reached by tracing the adjacency relationships indicated by impact range data that indicates the adjacency relationships between two facilities among the multiple facilities; and an execution pattern generation unit that, when each of the one or more generated equipment groups is set as a target equipment group, generates execution pattern data that indicates one or more execution patterns that each comprehensively indicates each construction work corresponding to each facility included in the target equipment group based on the impact range data, construction data that indicates each task corresponding to each construction work corresponding to each facility included in the target equipment group, and common task data that indicates each task that can be common among multiple construction works.

2. When each execution pattern indicated by the execution pattern data is taken as a target execution pattern, the target execution pattern indicates data indicating one or more construction works corresponding to one or more pieces of equipment selected based on the adjacency relationship indicated by the impact range data from among the construction works corresponding to each piece of equipment included in the target equipment group, and when the one or more construction works indicated by the target execution pattern do not cover all the construction works corresponding to each piece of equipment included in the target equipment group, the target execution pattern indicates one or more execution patterns from among the execution patterns indicated by the execution pattern data that indicate all the construction works that should be carried out in order to cover all the construction works corresponding to each piece of equipment included in the target equipment group.

3. The construction planning device according to claim 1, further comprising a construction candidate generation unit that, when each execution pattern indicated by the execution pattern data is set as a target execution pattern, generates construction candidates corresponding to the target execution pattern for each construction execution method indicated by the target execution pattern based on the target execution pattern.

4. The construction planning device according to claim 3 further comprises a construction plan generation unit that generates construction plans corresponding to the plurality of facilities based on each of the generated construction candidate projects, worker data indicating candidate workers to be assigned to each construction project, and an objective function for evaluating the construction plan, and the generated construction plan indicates, for each of the target equipment groups, each of the construction projects corresponding to each of the facilities included in the target equipment group.

5. The construction planning device according to claim 4, wherein the construction candidate generation unit excludes, from among the generated construction candidates, construction candidates that do not satisfy the constraint conditions corresponding to each construction corresponding to each facility included in the target facility group.

6. The construction planning device according to any one of claims 1 to 5, further comprising: a priority generation unit that generates a priority for each construction work corresponding to each piece of equipment included in the target equipment group based on construction-related data indicating constraints that must be satisfied when carrying out each construction work corresponding to each piece of equipment included in the target equipment group.

7. The construction planning device according to any one of claims 1 to 5, further comprising a priority generation unit that estimates the degree of deterioration of each piece of equipment based on inspection data indicating the inspection results corresponding to each piece of equipment included in the target equipment group, and generates a priority for each piece of construction work corresponding to each piece of equipment included in the target equipment group based on the estimated degree of deterioration of each piece of equipment.

8. A construction planning method executed by a construction planning device, which is a computer for creating construction plans for multiple facilities, wherein the construction planning device generates one or more facility groups by generating facility groups consisting of each series of facilities that can be reached by tracing the adjacency relationships indicated by influence range data that indicates the adjacency relationships between two facilities among the multiple facilities, and when the construction planning device designates each of the one or more generated facility groups as a target facility group, generates execution pattern data that indicates one or more execution patterns that each comprehensively indicates each construction work corresponding to each facility included in the target equipment group based on the influence range data, construction data that indicates each task corresponding to each construction work corresponding to each facility included in the target equipment group, and common task data that indicates each task that can be common among multiple construction works.

9. A construction planning program executed by a construction planning device, which is a computer for drawing up construction plans for multiple facilities, which causes the construction planning device to execute the following steps: an equipment group generation process that generates one or more equipment groups by generating equipment groups consisting of each series of facilities that can be reached by tracing the adjacency relationships indicated by impact range data that indicates the adjacency relationships between two facilities among the multiple facilities; and an execution pattern generation process that generates execution pattern data that indicates one or more execution patterns that each comprehensively indicates each construction work corresponding to each facility included in the target equipment group, based on the impact range data, construction data that indicates each task corresponding to each construction work corresponding to each facility included in the target equipment group, and common task data that indicates each task that can be common among multiple construction works, when each of the one or more generated equipment groups is set as a target equipment group.

Images