Engineering plan making device, engineering plan making method, and engineering plan making program

Abstract

An engineering plan formulation device (100) for formulating an engineering plan for a plurality of devices includes a device group generation section (120) and an execution pattern generation section (130). The device group generation section (120) generates each device group formed of a series of devices among the plurality of devices that are able to reach each other by following an adjacency relationship indicated by influence range data indicating an adjacency relationship between two devices. The execution pattern generation section (130) generates execution pattern data (131) indicating one or more execution patterns that comprehensively indicate each engineering corresponding to each device included in a target device group, based on the influence range data (53), engineering data (51) indicating each work corresponding to each engineering, and common work data (52) indicating each work that can be common among a plurality of engineering, when each device group of one or more generated device groups is set as the target device group.

Description

Technical Field

[0001] This disclosure relates to an engineering planning apparatus, an engineering planning method, and an engineering planning procedure. Background Technology

[0002] In developing engineering plans for social infrastructure projects, various factors such as project priority and the skills of the personnel are considered when allocating projects to personnel, and a plan is developed that minimizes the time and number of personnel required for each project (hereinafter referred to as cost). In this case, by concentrating the execution of multiple projects, the costs associated with those projects can sometimes be reduced.

[0003] As a specific example, in highways and similar projects, costs can be reduced by simultaneously carrying out adjacent projects and collaborating on operations related to multiple facilities (such as project applications and traffic preparations).

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: Japanese Patent Application Publication No. 2015-215759 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In the technology disclosed in Patent Document 1, it is possible to consider reducing the opportunity loss such as traffic closures by simultaneously constructing multiple projects. However, in this technology, since information indicating that operations can be shared among multiple projects is not utilized, it is impossible to consider reducing operations such as traffic preparation and project application that can be shared among multiple projects.

[0009] The purpose of this disclosure is to enable the consideration of which task can be common when multiple tasks are executed simultaneously by utilizing information representing tasks that can be common across multiple projects (common task data).

[0010] Methods for solving problems

[0011] The engineering planning apparatus disclosed herein is used to formulate engineering plans for multiple devices. The engineering planning apparatus includes: an equipment group generation unit, which generates one or more equipment groups by generating equipment groups composed of a series of devices that can be reached by following the adjacency relationship indicated by the influence range data representing the adjacency relationship between two devices; and an execution mode generation unit, which, when setting each equipment group of the generated one or more equipment groups as an object equipment group, generates execution mode data representing one or more execution modes based on the influence range data, engineering data representing each operation corresponding to each project, and common operation data representing each operation that can be common to multiple projects. The project corresponds to each device included in the object equipment group, and the one or more execution modes comprehensively cover each project corresponding to each device included in the object equipment group.

[0012] Invention Effects

[0013] According to this disclosure, the execution mode generation unit generates execution mode data that comprehensively represents each project based on collaborative work data.

[0014] Therefore, according to this disclosure, by utilizing information representing operations that can be shared among multiple projects (shared operation data), it is possible to consider which operation can be shared when multiple projects are executed simultaneously. Attached Figure Description

[0015] Figure 1 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 1.

[0016] Figure 2 This is a diagram showing a specific example of engineering data 51 in implementation method 1.

[0017] Figure 3 This is a diagram illustrating a specific example of the common operation data 52 in Implementation Method 1.

[0018] Figure 4 The diagram illustrates the influence range data 53 of Implementation Method 1. (a) is a schematic diagram of each device and its adjacency relationship, and (b) is a table showing the influence range data 53.

[0019] Figure 5 This is a diagram illustrating a specific example of group data 121 in Implementation Method 1.

[0020] Figure 6 This diagram illustrates the processing of the execution mode generation unit 130 in Embodiment 1.

[0021] Figure 7 This is a flowchart illustrating the operation of the engineering planning device 100 in Implementation Method 1.

[0022] Figure 8 This is a flowchart illustrating the operation of the device assembly generation unit 120 in Embodiment 1.

[0023] Figure 9 This is a flowchart illustrating the operation of the execution mode generation unit 130 in Embodiment 1.

[0024] Figure 10 This is a diagram illustrating a hardware structure example of an engineering planning device 100, which is a variation of implementation 1.

[0025] Figure 11 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 2.

[0026] Figure 12 This is a diagram illustrating a specific example of the engineering candidate data 211 in Implementation Method 2.

[0027] Figure 13 These are diagrams illustrating the processing of the engineering candidate generation unit 210 in Embodiment 2. (a) is a diagram illustrating "parallel connection", (b) is a diagram illustrating "series connection", and (c) is a diagram illustrating "individual connection".

[0028] Figure 14 This is a flowchart illustrating the operation of the engineering planning device 100 in Embodiment 2.

[0029] Figure 15 This is a flowchart illustrating the operation of the engineering candidate generation unit 210 in Embodiment 2.

[0030] Figure 16 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 3.

[0031] Figure 17 This is a diagram illustrating a specific example of the operator data 54 in Implementation Method 3.

[0032] Figure 18 This is a flowchart illustrating the operation of the engineering planning device 100 in Implementation Method 3.

[0033] Figure 19 This is a flowchart illustrating the operation of the engineering plan generation unit 310 in embodiment 3.

[0034] Figure 20 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 4.

[0035] Figure 21 This is a diagram illustrating a specific example of the engineering-related data 56 in implementation method 4.

[0036] Figure 22This diagram illustrates the processing of the engineering candidate generation unit 210 in Embodiment 4.

[0037] Figure 23 This is a flowchart illustrating the operation of the engineering candidate generation unit 210 in embodiment 4.

[0038] Figure 24 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 5.

[0039] Figure 25 This diagram illustrates the processing of the priority generation unit 510 in Embodiment 5.

[0040] Figure 26 This is a flowchart illustrating the operation of the engineering planning device 100 in embodiment 5.

[0041] Figure 27 This is a flowchart illustrating the operation of the priority generation unit 510 in embodiment 5.

[0042] Figure 28 This is a diagram illustrating a structural example of the engineering planning system 90 in implementation method 6.

[0043] Figure 29 This is a diagram illustrating a specific example of the inspection data 57 in Implementation Method 6.

[0044] Figure 30 This is a flowchart illustrating the operation of the priority generation unit 510 in embodiment 6. Detailed Implementation

[0045] In the description and accompanying drawings of the embodiments, the same reference numerals are used to label the same elements and corresponding elements. The descriptions of elements labeled with the same reference numerals are appropriately omitted or simplified. The arrows in the figures mainly indicate data flow or processing flow. In addition, "part" may be appropriately replaced with "circuit", "process", "step", "processing" or "line".

[0046] Implementation method 1.

[0047] Hereinafter, this embodiment will be described in detail with reference to the accompanying drawings.

[0048] Structural description

[0049] Figure 1 This figure shows a structural example of the engineering planning system 90 according to this embodiment. As shown in this figure, the engineering planning system 90 includes an engineering planning device 100.

[0050] As functional structural elements, the engineering planning device 100 includes a data acquisition unit 110, an equipment group generation unit 120, an execution mode generation unit 130, and a result output unit 140. The engineering planning device 100 is an apparatus for formulating engineering plans for multiple pieces of equipment, each representing an engineering object.

[0051] The data acquisition department 110 acquires engineering data 51, joint operation data 52, and impact range data 53.

[0052] Project data 51 is data representing the content of each project. As a specific example, project data 51 consists of information representing the equipment as the project object, the content of the project, the construction time, the number of workers required for construction, etc., for each project.

[0053] Figure 2 A specific example of engineering data 51 is shown. Figure 2 In this system, each project is assigned a "Project ID" as an identifier. "Equipment Name" corresponds to the equipment that is the project object, "Project Category" corresponds to the project classification, "Required Time" corresponds to the construction time, and "Required Personnel" corresponds to the number of workers required during construction.

[0054] Collaborative work data 52 represents data on individual work processes that can be shared among multiple projects. As a specific example, collaborative work data 52 consists of information indicating that each work process can be shared among multiple projects and the projects in which each shared work process is implemented.

[0055] Figure 3 A specific example of collaborative work data 52 is shown. Figure 3 In the table, for each job that can be shared and implemented, the table displays "Job ID", "Job Category", "Corresponding Project Category", "Required Time", "Required Number of Personnel", and "Job Timing".

[0056] "Job ID" represents the identifier assigned to a collaborative job.

[0057] "Job Category" indicates the classification corresponding to a collaborative task.

[0058] "Corresponding Project Category" indicates the classification of the projects that perform joint operations.

[0059] "Required time" refers to the time required to execute the collaborative work.

[0060] "Number of personnel required" refers to the number of personnel needed to perform a collaborative operation.

[0061] "Operation timing" refers to the timing of a project corresponding to a joint operation, indicating the appropriate time to execute the joint operation. Additionally, sometimes "operation timing" also refers to the period after the corresponding project has been completed.

[0062] The impact range data 53 consists of information representing the adjacency relationship between two devices. Here, for a group of multiple devices, the adjacency relationship between devices is defined based on whether there is a shared task that can be executed. As a specific example, the adjacency relationship is defined based on the distance between the multiple devices or on the access methods of each of the multiple devices.

[0063] Figure 4 This is a graph illustrating the scope of influence of data 53. In Figure 4 In the middle, each piece of equipment is a tunnel.

[0064] Figure 4 (a) is a schematic diagram of the devices and their adjacency relationships. Figure 4 In (a), when two tunnels are adjacent to each other, they are connected by a line. As a specific example, tunnel A and tunnel B are adjacent to each other on a road. Furthermore, the road containing tunnel D is different from the road containing tunnels A, B, and C.

[0065] Figure 4 (b) shows the relationship with Figure 4 Specific examples of the impact range data 53 corresponding to (a). In Figure 4 In (b), for each group of devices, "1" is shown if the groups of devices are adjacent, and "0" is shown if the groups of devices are not adjacent. Here, a group of devices consists of 2 devices.

[0066] When a group of devices is adjacent, and projects associated with each device in that group are executed simultaneously, the common work corresponding to that group can be shared and executed.

[0067] Furthermore, regarding groups of two devices, when one device within each group is shared, and projects associated with each device within the two-device group are executed simultaneously, it is sometimes possible to share the execution of shared tasks related to all devices within the two-device group. As a specific example, in... Figure 4 In the case where a group of two devices includes a group of devices consisting of tunnel A and tunnel B, and a group of devices consisting of tunnel B and tunnel C, tunnel B is common to both groups of two devices.

[0068] Furthermore, regarding two devices located on a branch path, since there is no relationship between the devices, they are considered not to be able to share common operations. As a specific example, tunnel C and tunnel D are equivalent to two devices located on a branch path.

[0069] The device group generation unit 120 generates one or more device groups. Each device group consists of a series of devices that can be reached by following the adjacency relationship shown in the influence range data 53.

[0070] As a specific example, the equipment group generation unit 120 summarizes a series of equipment that can be reached based on the adjacency relationship shown in the influence range data 53 into an equipment group, and then extracts each project associated with each equipment contained in each equipment group, thereby generating group data 121.

[0071] Group data 121 indicates a group of devices that can share and perform common tasks.

[0072] Figure 5 Showing with Figures 2-4 A specific example corresponding to group data 121. In Figure 5 In the middle, each equipment group shows the corresponding equipment and each project.

[0073] "Group ID" represents the identifier assigned to a device group.

[0074] The "Device ID List" represents a list of identifiers for the devices that make up each device group. Here, tunnels A, B, and C correspond to a series of devices that can be reached based on the adjacency relationships shown in the influence range data 53. Therefore, tunnels A, B, and C are grouped into one device group. On the other hand, tunnel D cannot be reached from any of tunnels A, B, or C based on the adjacency relationships shown in the influence range data 53. Therefore, tunnel D is not included in group 1.

[0075] The “Project ID List” represents a list of identifiers for the projects corresponding to the equipment that make up each equipment group. Here, Project 1 is associated with Tunnel A, Project 2 with Tunnel B, and Project 3 with Tunnel C. Therefore, for Group 1, the “Project ID List” includes Project 1, Project 2, and Project 3.

[0076] When the execution mode generation unit 130 considers each of the generated equipment groups as the target equipment group, it generates execution mode data 131 based on the influence range data 53, engineering data 51, and joint operation data 52. The engineering data 51 represents each operation corresponding to each engineering process for each equipment included in the target equipment group.

[0077] As a specific example, the execution mode generation unit 130 calculates the execution mode for executing all the projects contained in each equipment group based on group data 121, influence range data 53, project data 51, and joint operation data 52. Then, the execution mode generation unit 130 generates execution mode data 131 representing the calculated execution mode. The execution mode is determined based on each combination of equipment reachable based on the adjacency relationships shown in the influence range data 53.

[0078] Execution mode data 131, for each device group, represents various execution modes for each project used to comprehensively cover all projects associated with the device. Execution mode data 131 represents one or more execution modes that comprehensively cover each project corresponding to each device included in the target device group. When each execution mode shown in execution mode data 131 is set as an object execution mode, the object execution mode represents the following data: this data represents one or more projects corresponding to one or more devices selected based on the adjacency relationship shown in the influence range data 53, within each project corresponding to each device included in the target device group. Furthermore, if the one or more projects shown by the object execution mode do not comprehensively cover each project corresponding to each device included in the target device group, the object execution mode represents one or more execution modes shown in execution mode data 131 that represent each project that should be executed to comprehensively cover each project corresponding to each device included in the target device group.

[0079] Figure 6 Is with Figures 2-5 The corresponding diagram illustrates the processing of the execution mode generation unit 130. Figure 6 In the execution mode data 131, "Device Group," "Project ID List," "Job ID List," and "Supplementary Mode List" are displayed for each execution mode. Furthermore, for group 1, multiple modes can be generated based on adjacency relationships. On the other hand, for group 2, there is only one corresponding device, therefore, there is only one execution mode.

[0080] "Mode ID" represents the identifier assigned to each execution mode.

[0081] "Device group" refers to the device group corresponding to each execution mode.

[0082] The "Project ID List" represents a list of identifiers for one or more projects selected within the reachable range based on adjacency relationships, corresponding to the devices constituting each device group. Here, tunnel A and tunnel B are adjacent. Therefore, tunnel A and tunnel B correspond to the device combination reachable based on the adjacency relationship shown in influence range data 53. Therefore, in pattern ID2, only projects 1 and 2, corresponding to tunnel A and tunnel B respectively, are shown in the "Project ID List." On the other hand, tunnel A and tunnel C are not adjacent. Therefore, tunnel A and tunnel C do not correspond to the device combination reachable based on the adjacency relationship shown in influence range data 53. Therefore, only projects 1 and 3, corresponding to tunnel A and tunnel C respectively, are not shown in the "Project ID List."

[0083] The “Job ID List” represents a list of identifiers for common jobs performed in the projects shown in the “Project ID List”.

[0084] The "Supplementary Mode List" represents a list of identifiers for execution modes, indicating the remaining projects that need to be executed to fully cover all projects corresponding to the device groups listed in the "Device Groups". In the "Supplementary Mode List" corresponding to the object execution modes, one or more execution modes from the execution mode data 131 are shown, representing projects that should be executed to fully cover all projects corresponding to each device in the object device group, when one or more projects shown by the object execution mode alone do not fully cover all projects corresponding to each device in the object device group. Furthermore, when multiple execution modes need to be executed, the "Supplementary Mode List" shows groups consisting of identifiers corresponding to each of the multiple execution modes. Additionally, the list of identifiers for the execution modes shown in the "Supplementary Mode List" is not limited to one type. For example, regarding mode ID4, projects 1 and 2 need to be executed as remaining projects related to group 1. Here, projects 1 and 2 are executed even if mode ID3 is executed, and projects 1 and 2 are executed even if modes ID5 and mode ID6 are executed. Therefore, as a “supplementary pattern list” corresponding to pattern ID4, [3] and [5, 6] are shown.

[0085] use Figure 1 An example of the hardware structure of the engineering planning device 100 will be described. The engineering planning device 100 is composed of a computer. The engineering planning device 100 may also be composed of multiple computers.

[0086] like Figure 1 As shown, the engineering planning device 100 is a computer equipped with 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 hardware components are appropriately connected via signal lines.

[0087] Processor 11 is an IC (Integrated Circuit) that performs computational processing and controls the hardware of the computer. As a specific example, processor 11 is a CPU (Central Processing Unit), DSP (Digital Signal Processor), or GPU (Graphics Processing Unit).

[0088] The engineering planning device 100 may also have multiple processors to replace the processor 11. The multiple processors share the functions of the processor 11.

[0089] Storage device 12 is typically a volatile storage device, specifically RAM (Random Access Memory). Storage device 12 is also referred to as main storage device or main memory. Data stored in storage device 12 is stored in auxiliary storage device 13 as needed.

[0090] The auxiliary storage device 13 is typically a non-volatile storage device, such as ROM (Read Only Memory), HDD (Hard Disk Drive), or flash memory. Data stored in the auxiliary storage device 13 is loaded into the storage device 12 as needed.

[0091] The storage device 12 and the auxiliary storage device 13 can also be configured as a single unit.

[0092] Input interface 14 is a port for connecting input and output devices. As a specific example, input interface 14 is a USB (Universal Serial Bus) terminal. As a specific example, the input device is a keyboard and mouse. As a specific example, the output device is a monitor.

[0093] Communication device 15 is a receiver and a transmitter. As a specific example, communication device 15 is a communication chip or NIC (Network Interface Card).

[0094] When communicating with other devices, the various parts of the engineering planning device 100 may also appropriately use the input interface 14 and the communication device 15.

[0095] Auxiliary storage device 13 stores an engineering planning program. This program enables the computer to perform the functions of each component of the engineering planning device 100. The engineering planning program is loaded into storage device 12 and executed by processor 11. The functions of each component of the engineering planning device 100 are implemented through software.

[0096] Data used during the execution of the engineering planning process and data obtained through the execution of the engineering planning process are appropriately stored in a storage device. Each part of the engineering planning device 100 appropriately utilizes a storage device. Specifically, the storage device comprises at least one of a storage device 12, an auxiliary storage device 13, a register within the processor 11, and a cache memory within the processor 11. Furthermore, the terms "data" and "information" are sometimes used interchangeably. The storage device may also be independent of the computer.

[0097] The functions of storage device 12 and auxiliary storage device 13 can also be implemented by other storage devices.

[0098] Engineering planning procedures can also be recorded on computer-readable, non-volatile recording media. Specific examples of non-volatile recording media include optical discs or flash memory. Engineering planning procedures can also be provided as a program product.

[0099] Description of the action

[0100] The operating steps of the engineering planning device 100 are equivalent to the engineering planning method. Furthermore, the procedure for implementing the operation of the engineering planning device 100 is equivalent to the engineering planning procedure.

[0101] Figure 7 This is a flowchart illustrating an example of the operation of the engineering planning device 100. (Using...) Figure 7 Explain the operation of the engineering planning device 100.

[0102] (Step S11)

[0103] The data acquisition department 110 acquires engineering data 51, joint operation data 52, and impact range data 53.

[0104] (Step S12)

[0105] The equipment group generation unit 120 generates group data 121 based on the engineering data 51 and the influence range data 53 obtained by the data acquisition unit 110.

[0106] (Step S13)

[0107] The execution mode generation unit 130 generates execution mode data 131 based on group data 121, engineering data 51, and influence range data 53.

[0108] (Step S14)

[0109] The result output unit 140 outputs the execution mode data 131 generated by the execution mode generation unit 130.

[0110] As a specific example, the result output unit 140 displays the combination of devices and engineering processes contained in the execution mode data 131 on a display screen (not shown).

[0111] Figure 8 This is a flowchart illustrating an example of the operation of the equipment group generation unit 120 related to step S12. (Using...) Figure 8 Explain the action.

[0112] (Step 12.1)

[0113] Based on the influence range data 53, the device group generation unit 120 extracts all devices that can be reached by following the adjacency relationship as one group.

[0114] The device group generation unit 120 extracts the groups until all devices shown in the influence range data 53 belong to any group.

[0115] (Step 12.2)

[0116] The equipment group generation unit 120 extracts all the engineering processes that need to be performed on the equipment belonging to each group, based on the engineering data 51.

[0117] The equipment group generation unit 120 generates group data 121 based on the extracted groups and projects.

[0118] Figure 9 This is a flowchart illustrating an example of the operation of the execution mode generation unit 130 related to step S13. Figure 9 Explain the action.

[0119] (Step 13.1)

[0120] The execution mode generation unit 130 takes each group shown in the group data 121 as an object group, and extracts each combination of the projects belonging to the object group as an execution mode based on the equipment and projects belonging to the object group and the influence range data 53.

[0121] Furthermore, the execution mode generation unit 130 does not extract execution modes for projects that would not be reached if the adjacency relationship shown in the influence range data 53 is not followed.

[0122] This step is equivalent to generating a "project ID list".

[0123] (Step 13.2)

[0124] The execution mode generation unit 130 extracts common operations associated with each project belonging to each extracted execution mode.

[0125] This step is equivalent to generating a "job ID list".

[0126] (Step 13.3)

[0127] For each extracted execution mode, the execution mode generation unit 130 determines other execution modes that are complementary to the projects belonging to the device group corresponding to the execution mode, so that all projects corresponding to the execution mode can be executed.

[0128] This step is equivalent to generating a "supplementary pattern list".

[0129] Explanation of the effects of Implementation Method 1

[0130] As described above, according to this embodiment, data representing the simultaneous execution mode of multiple projects that include tasks that can be shared is generated. Therefore, by effectively utilizing this embodiment, it is possible to formulate a project plan that takes into account the reduction of tasks that can be shared and includes all projects without omission.

[0131] Other structures

[0132] <Variation Example 1>

[0133] Figure 10 This example illustrates the hardware structure of the engineering planning device 100 in this modified example.

[0134] The engineering planning device 100 has a processing circuit 18 instead of a processor 11, a processor 11 and a storage device 12, a processor 11 and an auxiliary storage device 13, or a processor 11, a storage device 12 and an auxiliary storage device 13.

[0135] The processing circuit 18 is hardware that implements at least a portion of the components of the engineering planning device 100.

[0136] The processing circuit 18 can be dedicated hardware, or it can be a processor that executes the program stored in the storage device 12.

[0137] In the case where the processing circuit 18 is dedicated hardware, as a specific example, the processing circuit 18 is a single circuit, a composite circuit, a programmable processor, a parallel programmable processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

[0138] The engineering planning device 100 may also have multiple processing circuits that can replace the processing circuit 18. The multiple processing circuits share the functions of the processing circuit 18.

[0139] In the engineering planning device 100, some functions may be implemented by dedicated hardware, while the remaining functions may be implemented by software or firmware.

[0140] As a specific example, the processing circuit 18 is implemented by hardware, software, firmware, or a combination thereof.

[0141] The processor 11, storage device 12, auxiliary storage device 13, and processing circuit 18 are collectively referred to as the "processing circuit". That is, the functions of each functional structural element of the engineering planning device 100 are realized through the processing circuit.

[0142] The engineering planning device 100 in other embodiments may also have the same structure as this modified example.

[0143] Implementation method 2.

[0144] Hereinafter, the differences from the embodiments described above will be explained with reference to the accompanying drawings.

[0145] Structural description

[0146] Figure 11 An example of the structure of the engineering planning system 90 of this embodiment is shown.

[0147] As a functional structural element, the engineering planning device 100 of this embodiment also has an engineering candidate generation unit 210.

[0148] In this embodiment, the result output unit 140 outputs project candidate data 211 instead of execution mode data 131.

[0149] When setting each execution mode shown in the execution mode data 131 as an object execution mode, the project candidate generation unit 210 generates a project candidate corresponding to the object execution mode based on the object execution mode and according to each execution method of the project shown in the object execution mode.

[0150] As a specific example, the project candidate generation unit 210 generates project candidate data 211 based on project data 51, collaborative work data 52, and execution mode data 131. As a specific example, the project candidate generation unit 210 generates project candidate data 211 according to each combination of the "project ID list" and the "execution method" related to the "project ID list" shown in the execution mode data 131. The project candidate data 211 represents the information required for the project plan (required time and required number of personnel) and the combinations used to carry out the construction of the entire project (supplementary project candidate list), etc.

[0151] "Execution Method" refers to the execution method of one or more projects shown in the corresponding project ID list. As a specific example, "Execution Method" is information corresponding to the execution order, and can be any one of "Parallel (simultaneous)," "Series (continuous)," and "Individual (individual)."

[0152] "Parallel" means executing multiple projects simultaneously. Furthermore, when the "execution method" for multiple projects is "parallel," it's not always necessary to execute all of those projects simultaneously.

[0153] "Serial execution" means that multiple projects are executed sequentially, not simultaneously.

[0154] "Single" means to execute one project.

[0155] Figure 12 A specific example of project candidate data 211 is shown. When the "Project ID List" shown in execution mode data 131 contains multiple project IDs, the corresponding "Execution Methods" can be parallel or serial. On the other hand, when the "Project ID List" contains only one project ID, there is no room to consider execution methods; therefore, a project candidate with an empty "Execution Method" field is generated. This empty field signifies "alone".

[0156] The "Time Required" and "Number of Personnel Required" are values ​​calculated based on the "Execution Method", "Project ID List", and "Job ID List".

[0157] The value of the “Supplementary Project Candidate List” is calculated by converting each mode ID shown in the “Supplementary Mode List” of execution mode data 131 into a project candidate ID corresponding to each mode ID. Each element shown in the “Supplementary Project Candidate List” is equivalent to a project candidate group. That is, [6] and [8, 9] are equivalent to project candidate groups respectively. A project candidate group represents more than one project candidate.

[0158] Figure 13 This shows a specific example of how to calculate the "time required" and "number of people required" according to the execution method. Figure 13The document shows the timing of each process and the duration of each process, as well as the number of personnel required for that process, for each project and task. Here, for each project candidate, even if the "Project ID List" and "Task ID List" are the same, the "Required Time" and "Required Personnel" may differ depending on the "Execution Method." Furthermore, in this example, the "Required Personnel" is the maximum total number of personnel required for each project and task during the repeated execution of multiple processes.

[0159] Figure 13 (a) shows a specific example where the “execution method” for Project 1 and Project 2 is in parallel. In this example, the “required time” is 6 hours and the “required number of people” is 10.

[0160] Figure 13 (b) shows a specific example where the “execution method” for Project 1 and Project 2 is in series. In this example, the “time required” is 10 hours and the “number of people required” is 6.

[0161] Figure 13 (c) shows a specific example of performing Project 1 alone. In this example, the "time required" is 5 hours and the "number of people required" is 6.

[0162] Description of the action

[0163] Figure 14 This is a flowchart illustrating an example of the operation of the engineering planning device 100. (Using...) Figure 14 Explain the operation of the engineering planning device 100.

[0164] (Step S24)

[0165] Based on the project data 51, the joint operation data 52, and the execution mode data 131, the project candidate generation unit 210 determines the "execution method" of each project associated with the execution mode according to each execution mode, and generates project candidate data 211 that represents information related to the construction of all projects corresponding to the execution mode.

[0166] (Step S25)

[0167] The result output unit 140 outputs the engineering candidate data 211 generated by the engineering candidate generation unit 210. The output method is the same as step S14.

[0168] Figure 15 This is a flowchart illustrating an example of the operation of the project candidate generation unit 210 related to step S24. Figure 15 Explain the action.

[0169] (Step 24.1)

[0170] The project candidate generation unit 210 generates project candidates for each execution method based on the execution mode data 131. Here, when one execution mode contains two or more projects, the "execution method" is either a parallel or serial option. Alternatively, when one execution mode contains one project, the "execution method" is a single option.

[0171] (Step 24.2)

[0172] The project candidate generation unit 210 calculates the work time and number of workers required to carry out construction on each project candidate based on the project and common operations corresponding to the project candidate and considering the execution method.

[0173] (Step 24.3)

[0174] The project candidate generation unit 210 extracts supplementary relationships for project candidates to execute all projects associated with the execution mode, based on project candidates and execution modes.

[0175] Explanation of the effects of Implementation Method 2

[0176] As described above, according to this embodiment, by setting the execution method for each execution mode, multiple project candidates for different execution modes can be generated. Furthermore, the required time and number of personnel can be clearly defined for each project candidate. Therefore, by effectively utilizing this embodiment, project plans requiring less time and fewer personnel can be developed.

[0177] Implementation method 3.

[0178] Hereinafter, the differences from the embodiments described above will be explained with reference to the accompanying drawings.

[0179] Structural description

[0180] Figure 16 An example of the structure of the engineering planning system 90 of this embodiment is shown.

[0181] As a functional structural element, the engineering planning device 100 of this embodiment also includes an engineering planning generation unit 310.

[0182] In this embodiment, the data acquisition unit 110 also acquires operator data 54 and objective function data 55.

[0183] The output unit 140 outputs project plan data 311 to replace project candidate data 211.

[0184] Worker data 54 represents candidate workers to be assigned to each project, consisting of information corresponding to the workers that can be assigned to each project. Specifically, the information corresponding to each worker includes their start and end times, qualifications, etc.

[0185] Figure 17 This shows a specific example of worker data 54.

[0186] The objective function data 55 consists of information used to determine whether the project plan is good. As a specific example, objective function data 55 represents the objective function, where the number of workers assigned to the project plan is N, and the working time of each worker is T. n In this case, the objective function is shown in [Mathematical Formula 1].

[0187] [Mathematical Expression 1]

[0188] Objective function =

[0189] The project plan generation unit 310 generates project plans corresponding to multiple devices based on the project candidate data 54 generated by the project candidate generation unit 210, the operator data 54, and the objective function used to evaluate the project plans. The project plans generated by the project plan generation unit 310 represent each project corresponding to each device in any group of target devices.

[0190] As a specific example, the project planning generation unit 310 generates combinations of project candidates based on the project candidate data 211, in a manner that each project corresponding to the equipment group is constructed once, and formulates a project plan based on each generated combination. At this time, when the project planning generation unit 310 sets each combination of project candidates as an object combination, it generates the object combination based on the project candidate data 211 in a manner that the object combination satisfies the following three conditions.

[0191] about Figure 12 The project candidate data 211 shown, when the project planning generation unit 310 generates a combination of project candidates in such a way that the following three conditions are met, generates [1, 10], [2, 10], [3, 9, 10], [4, 9, 10], [5, 7, 10], [6, 7, 10] and [7, 8, 9, 10] as each combination of project candidates.

[0192] Condition 1: When setting various classes of "equipment group" as object group types, for any object group type, there must be at least one project candidate corresponding to the object group type in the object group.

[0193] Condition 2: When setting a project candidate that does not have a value in the corresponding "supplementary project candidate list" as an object project candidate, if the object combination contains an object project candidate, the object combination cannot contain a project candidate corresponding to the following "equipment group", which is the same as the "equipment group" corresponding to the object project candidate.

[0194] Condition 3: When setting a project candidate with a value in the corresponding "supplementary project candidate list" as an object project candidate, if the object combination contains an object project candidate, the object combination must contain all project candidates shown in any one of the project candidate groups contained in the "supplementary project candidate list" corresponding to the object project candidate.

[0195] The project planning unit 310, based on worker data 54 and objective function data 55, allocates workers for each combination of project candidates in a manner that does not exceed the number of workers available to work in each time period, and calculates the objective function value corresponding to the project candidate. Then, the project planning unit 310 adopts the project plan corresponding to the combination of project candidates with the best objective function value.

[0196] Description of the action

[0197] Figure 18 This is a flowchart illustrating an example of the operation of the engineering planning device 100. (Using...) Figure 18 Explain the operation of the engineering planning device 100.

[0198] (Step S31)

[0199] In addition to the data acquired in step S11, the data acquisition unit 110 also acquires operator data 54 and objective function data 55.

[0200] (Step S35)

[0201] The engineering planning generation unit 310, based on the engineering candidate data 211, the operator data 54, and the objective function data 55, formulates engineering plan data 311 that sets the allocation of operators and the order of inspections in a manner that minimizes or maximizes the objective function shown in the objective function data 55.

[0202] (Step S36)

[0203] The output unit 140 outputs the engineering plan data 311 generated by the engineering plan generation unit 310. The output method is the same as step S14.

[0204] Figure 19 This is a flowchart illustrating an example of the operation of the engineering plan generation unit 310 related to step S35. (Using...) Figure 19 Explain the action.

[0205] (Step 35.1)

[0206] The engineering planning generation unit 310 generates a combination of engineering candidates by executing all engineering projects corresponding to each equipment group.

[0207] (Step 35.2)

[0208] The engineering plan generation unit 310, based on the generated combinations of engineering candidates, operator data 54, and objective function data 55, formulates an engineering plan for each combination of engineering candidates in a manner that maximizes (or minimizes) the corresponding objective function value.

[0209] (Step 35.3)

[0210] The engineering plan generation unit 310 compares the objective function values ​​corresponding to each engineering plan with the engineering plan formulated based on the combination of each engineering candidate, selects the engineering plan with the largest (or smallest) objective function value, and uses the selected engineering plan as the final engineering plan.

[0211] Explanation of the effects of implementation method 3

[0212] As described above, according to this embodiment, considering the corresponding objective function value, an engineering plan corresponding to various execution modes is formulated. Therefore, according to this embodiment, an engineering plan with a corresponding objective function value that is small (or large) can be formulated.

[0213] Implementation method 4.

[0214] Hereinafter, the differences from the embodiments described above will be explained with reference to the accompanying drawings.

[0215] Structural description

[0216] Figure 20 An example of the structure of the engineering planning system 90 of this embodiment is shown.

[0217] In this embodiment, the data acquisition unit 110 also acquires engineering-related data 56.

[0218] Project-related data 56 represents the constraints imposed on project data 51 and collaborative work data 52. Project-related data 56 represents the constraints that must be met when executing each project corresponding to each piece of equipment included in the object equipment group.

[0219] Among the constraints, specific examples include required qualifications (the qualifications that workers must possess to carry out the construction work), delivery date (the date and time by which the work must be completed), and construction permit period (the period during which the work can be carried out).

[0220] Figure 21 This shows a specific example of project-related data 56. Figure 21 The constraints are shown for each project and each operation.

[0221] In this embodiment, the project candidate generation unit 210 adds the information shown in the project-related data 56 to the project candidate data 211.

[0222] Furthermore, the project candidate generation unit 210 excludes project candidates that do not meet the constraints corresponding to each project, and assigns each project to each piece of equipment included in the target equipment group. As a specific example, if project association data 56 representing opposite constraints is added to a project candidate for which there are multiple corresponding projects, the project candidate generation unit 210 deletes that project candidate.

[0223] Figure 22 This shows a specific example of project candidate data 211 with the addition of project-related data 56. For a given project candidate, such as... Figure 22 As shown, construction of a particular project candidate cannot proceed if there is no overlapping period between the two specified construction permit periods, or if the project is not completed before the specified delivery date even though there is an overlapping period. Therefore, the project candidate generation unit 210 deletes the project candidate from the project candidate data 211.

[0224] In addition to the functions described above, the engineering plan generation unit 310 of this embodiment also has the function of generating engineering plan data 311 in a manner that satisfies the constraints shown in the engineering-related data 56.

[0225] Description of the action

[0226] The flowchart illustrating the operation of the engineering planning device 100 in this embodiment is the same as the flowchart illustrating the operation of the engineering planning device 100 in Embodiment 3. The differences between this embodiment and Embodiment 3 will be explained regarding the operation of the engineering planning device 100.

[0227] (Step S31)

[0228] In addition to the data obtained in step S31 of embodiment 3, the data acquisition unit 110 also acquires engineering-related data 56.

[0229] (Step S24)

[0230] This step is the same as step S24 in Embodiment 3. However, the engineering candidate generation unit 210 uses engineering-related data 56 when generating engineering candidate data 211.

[0231] (Step S35)

[0232] This step is the same as step S35 in Embodiment 3. However, the engineering plan generation unit 310 uses engineering-related data 56 when generating engineering plan data 311.

[0233] Figure 23 This is a flowchart illustrating an example of the operation of the project candidate generation unit 210 related to step S24. Figure 23 Explain the action.

[0234] (Step 44.3)

[0235] The project candidate generation unit 210 assigns constraints to each project candidate for construction based on each project candidate and project-related data 56.

[0236] Explanation of the effects of implementation method 4

[0237] As described above, according to this embodiment, project candidates that do not need to be considered when formulating a project plan are deleted based on constraints.

[0238] Furthermore, according to this embodiment, constraints related to construction can be imposed, thus enabling the development of more complex engineering plans.

[0239] Implementation method 5.

[0240] Hereinafter, the differences from the embodiments described above will be explained with reference to the accompanying drawings.

[0241] Structural description

[0242] Figure 24 An example of the structure of the engineering planning system 90 of this embodiment is shown.

[0243] As a functional structural element, the engineering planning device 100 of this embodiment also includes a priority generation unit 510.

[0244] The priority generation unit 510 generates priorities corresponding to each project for each device included in the object device group based on the project association data 56.

[0245] The priority generation unit 510 determines the priority corresponding to each project shown in the project plan data 311. Then, based on the determined priorities and information indicating the upper limit of the number of projects that can be constructed in each period, the priority generation unit 510 determines the construction target projects for each period. The construction target projects are those projects that become the objects of execution.

[0246] As a specific example, when the delivery date corresponding to each project is used as the priority corresponding to each project, the priority generation unit 510 sorts the projects shown in the project association data 56 based on the value shown in the "Delivery Date" column of the project association data 56. Furthermore, when the upper limit of the number of projects that can be constructed in each specific period is determined, the priority generation unit 510 uses this upper limit as the upper limit and sequentially selects projects as construction targets from the uppermost position of the sorted project association data 56.

[0247] Figure 25 This example illustrates project-related data 56 sorted by delivery date. In this example, the maximum number of projects that can be constructed in each specific period is 2. Therefore, the top two projects out of the three, namely Project 2 and Project 3, are selected as the projects to be constructed.

[0248] Description of the action

[0249] Figure 26 This is a flowchart illustrating an example of the operation of the engineering planning device 100. (Using...) Figure 26 Explain the operation of the engineering planning device 100.

[0250] (Step S51)

[0251] This step is the same as step S31 in embodiment 4.

[0252] (Step S52)

[0253] The priority generation unit 510 calculates the priority corresponding to each project to be implemented based on the project association data 56.

[0254] Figure 27 This is a flowchart illustrating an example of the operation of the priority generation unit 510 related to step S52. Figure 27 Explain the action.

[0255] (Step 52.1)

[0256] The priority generation unit 510 determines the priority corresponding to each project to be implemented based on the project association data 56.

[0257] As a specific example, when the delivery date is treated as a priority, the priority generation unit 510 rearranges the project-related data 56 in ascending order based on the delivery date. In this example, the projects are sorted according to their priority order.

[0258] (Step 52.2)

[0259] Based on the priority determined in step 52.1, the priority generation unit 510 determines the construction target project from the projects shown in the project plan data 311.

[0260] Explanation of the effects of implementation method 5

[0261] As described above, according to this embodiment, the construction targets for each period are determined based on the priority corresponding to each project. Therefore, by effectively utilizing this embodiment, it is possible to determine which project should be prioritized when there are a large number of projects and the upper limit of the number of projects that can be constructed in each specific period is already determined.

[0262] Implementation method 6.

[0263] Hereinafter, the differences from the embodiments described above will be explained with reference to the accompanying drawings.

[0264] Structural description

[0265] Figure 28 An example of the structure of the engineering planning system 90 of this embodiment is shown.

[0266] In this embodiment, the data acquisition unit 110 also acquires inspection data 57 and degradation model data 58.

[0267] Inspection data 57 represents the inspection results of each piece of equipment, specifically the inspection results corresponding to each piece of equipment within the target equipment group. For example, inspection data 57 consists of information for each piece of equipment indicating the location where the inspection was conducted, the period during which the inspection was conducted, and the equipment's health status at the time of the inspection. Figure 29 This shows a specific example of inspection data 57.

[0268] Deterioration model data 58 represents data from a model that estimates the health of equipment. Deterioration model data 58 can represent a model derived from physical theory or a statistical model derived from actual data. Specifically, deterioration model data 58 consists of information used to deduce the health of each piece of equipment based on the inspection location and the elapsed time since the inspection. Health is an integer value representing the degree of normality of the equipment, which gradually decreases over time.

[0269] [Mathematical Expression 2] and [Mathematical Expression 3] are specific examples of the degradation model data 58. In this example, health is represented by five stages from 1 to 5. Health level 5 corresponds to a relatively good state, and health level 1 corresponds to a relatively poor state. [Mathematical Expression 2] represents the migration probability matrix P of health in the Markov degradation model. [Mathematical Expression 3] represents the risk cost R corresponding to the health level. Here, P... n,m R represents the probability that health will migrate from n to m within one year. n This represents the risk cost when the health level is n.

[0270] [Mathematical Expression 2]

[0271] [Mathematical Expression 3]

[0272] In this embodiment, the priority generation unit 510 deduces the degree of deterioration of each device based on the inspection data 57, and generates a priority corresponding to each project based on the deduced degree of deterioration of each device. Each project corresponds to each device included in the target device group.

[0273] As a specific example, the priority generation unit 510 calculates the priority corresponding to each project based on the degree of degradation of each device. The following describes a specific example of the processing by the priority generation unit 510.

[0274] First, the priority generation unit 510 calculates an estimated health value of the equipment corresponding to the elapsed time since the inspection for each inspection data 57. When the project implementation year is set to m (m≥n), the priority generation unit 510 calculates the health value as shown in [Mathematical Formula 4]. Here, the health value vector H... c,n H is the health vector of a certain equipment at inspection location c, with an inspection year n. It is a five-dimensional vector that sets the health of past inspections to 1 (with a probability of 100%) and sets all others to 0 (with a probability of 0%). c,m This is the estimated health vector. The health vector represents the probability of each possible health value across five stages. As a specific example, if the health of a certain piece of equipment at inspection location c is 4 during an inspection conducted in inspection year n, then H... c,n =[0, 1, 0, 0, 0].

[0275] [Mathematical Expression 4]

[0276] Next, the priority generation unit 510 calculates the cost C as shown in [Mathematical Formula 5], with the risk cost set to R.

[0277] [Mathematical Expression 5]

[0278] Next, the priority generation unit 510 considers the calculated risk cost as a priority and sorts each project based on the priority corresponding to each piece of equipment c corresponding to each project. Then, similarly to Embodiment 5, the priority generation unit 510 determines the project to be constructed based on the upper limit of the number of projects that can be constructed in each specific period.

[0279] Description of the action

[0280] The flowchart illustrating the operation of the engineering planning device 100 in this embodiment is the same as the flowchart illustrating the operation of the engineering planning device 100 in Embodiment 5. The differences between this embodiment and Embodiment 5 will be explained regarding the operation of the engineering planning device 100.

[0281] (Step S51)

[0282] In addition to the data acquired in step S51 of embodiment 5, the data acquisition unit 110 also acquires inspection data 57 and degradation model data 58.

[0283] (Step S52)

[0284] The priority generation unit 510 generates priorities corresponding to each project to be implemented based on the inspection data 57 and the degradation model data 58.

[0285] Figure 30 This is a flowchart illustrating an example of the operation of the priority generation unit 510 related to step S52. Figure 30 Explain the action.

[0286] (Step 62.1)

[0287] The priority generation unit 510 calculates the health level corresponding to the inspection data 57 based on the inspection data 57 and the degradation model data 58. The health level corresponding to the inspection data 57 can also be a predicted value based on the health level of the inspection data 57.

[0288] (Step 62.2)

[0289] The priority generation unit 510 determines the priority corresponding to each project based on the health status derived in S62.1.

[0290] Furthermore, if the risk cost is determined based on the health status of each device, the priority generation unit 510 can also determine the priority corresponding to each project based on the value obtained by multiplying the health status and the risk cost.

[0291] Explanation of the effects of implementation method 6

[0292] As described above, according to this embodiment, the priority of each project is determined based on the degree of equipment degradation. Therefore, by effectively utilizing this embodiment, when constraints prevent the execution of some projects during project planning, it is possible to determine which project should be prioritized.

[0293] Other implementation methods

[0294] It is possible to freely combine the above-described embodiments, modify any structural elements of each embodiment, or omit any structural elements in each embodiment.

[0295] Furthermore, the implementation method is not limited to the methods shown in Implementation Methods 1 to 6, and various modifications can be made as needed. The steps described using flowcharts and other methods can also be appropriately modified.

[0296] Label Explanation

[0297] 11: Processor; 12: Storage device; 13: Auxiliary storage device; 14: Input interface; 15: Communication device; 18: Processing circuit; 51: Engineering data; 52: Collaborative operation data; 53: Impact range data; 54: Operator data; 55: Objective function data; 56: Engineering correlation data; 57: Inspection data; 58: Deterioration model data; 90: Engineering planning system; 100: Engineering planning device; 110: Data acquisition unit; 120: Equipment group generation unit; 121: Group data; 130: Execution mode generation unit; 131: Execution mode data; 140: Result output unit; 210: Engineering candidate generation unit; 211: Engineering candidate data; 310: Engineering plan generation unit; 311: Engineering plan data; 510: Priority generation unit.

Claims

1. An engineering planning device for developing engineering plans for multiple devices, the engineering planning device comprising: The device group generation unit generates one or more device groups by generating a series of devices that can be reached by following the adjacency relationship data representing the influence range of the adjacency relationship between two devices. The execution mode generation unit, when setting each of the generated one or more device groups as an object device group, generates execution mode data representing one or more execution modes based on the influence range data, project data representing each operation corresponding to each project, and common operation data representing each operation that can be common across multiple projects. Each project corresponds to each device in the object device group, and the one or more execution modes comprehensively represent each project corresponding to each device in the object device group.

2. The engineering planning device according to claim 1, wherein, When the execution modes shown in the execution mode data are set to object execution modes... The object execution mode is represented by the following data: This data represents one or more projects corresponding to one or more devices selected based on the adjacency relationship shown by the influence range data, within each project corresponding to each device in the object device group. In cases where one or more projects shown by the object execution mode do not fully cover all projects corresponding to each device included in the object device group, the object execution mode refers to one or more execution modes among the execution modes shown by the execution mode data, representing all projects that should be executed in order to fully cover all projects corresponding to each device included in the object device group.

3. The engineering planning device according to claim 1, wherein, The project planning device also includes a project candidate generation unit. When each execution mode shown in the execution mode data is set as an object execution mode, the project candidate generation unit generates a project candidate corresponding to the object execution mode based on the object execution mode and according to each execution method of the project shown in the object execution mode.

4. The engineering planning device according to claim 3, wherein, The engineering planning device further includes an engineering plan generation unit, which generates an engineering plan corresponding to the plurality of devices based on the generated candidate projects, candidate worker data representing the workers to be assigned to each project, and an objective function for evaluating the engineering plan. The generated project plan represents, for any of the object device groups, the projects corresponding to each device contained in the object device group.

5. The engineering planning device according to claim 4, wherein, The project candidate generation unit excludes project candidates that do not meet the constraints corresponding to each project, and each project corresponds to each device included in the object device group.

6. The engineering planning device according to any one of claims 1 to 5, wherein, The project planning device further includes a priority generation unit, which generates priorities for each project based on project association data representing the constraints that should be met when executing each project corresponding to each device in the object device group, wherein each project corresponds to each device in the object device group.

7. The engineering planning apparatus according to any one of claims 1 to 5, wherein, The project planning device also includes a priority generation unit, which derives the degree of deterioration of each device based on inspection data representing the inspection results corresponding to each device in the target equipment group, and generates a priority corresponding to each project based on the derived degree of deterioration of each device, wherein each project corresponds to each device in the target equipment group.

8. A method for developing an engineering plan, executed by an engineering plan development device, said engineering plan development device being a computer for developing engineering plans for multiple devices, wherein, The engineering planning device generates one or more device groups by generating a series of devices that can be reached by following the adjacency range data representing the adjacency relationship between two devices. When setting each of the generated one or more equipment groups as an object equipment group, the project planning device generates execution mode data representing one or more execution modes based on the influence range data, project data representing each operation corresponding to each project, and common operation data representing each operation that can be common across multiple projects. Each project corresponds to each equipment included in the object equipment group, and the one or more execution modes comprehensively represent each project corresponding to each equipment included in the object equipment group.

9. An engineering planning program, executed by an engineering planning device, said engineering planning device being a computer for developing engineering plans for multiple devices, the engineering planning program causing the engineering planning device to perform the following processes: The device group generation process generates one or more device groups by generating a series of devices that can be reached by following the adjacency relationship data representing the influence range of the adjacency relationship between two devices. The execution mode generation process, when setting each of the generated equipment groups (one or more) as an object equipment group, generates execution mode data representing one or more execution modes based on the influence range data, project data representing each operation corresponding to each project, and common operation data representing each operation that can be common across multiple projects. Each project corresponds to each device in the object device group, and the one or more execution modes comprehensively represent each project corresponding to each device in the object device group.

Images