JP5209014B2 - Construction plan management apparatus and method - Google Patents

Description

  The present invention relates to a construction plan management apparatus and method.

  Conventionally, various construction plans have been managed using a computer for planning, plan changes, construction progress, and the like. If there is no error in the input to the computer, the management of the construction plan by the computer promotes labor saving for frequent changes and recalculations accompanying the changes, and prevents calculation errors.

  For example, Patent Document 1 that discloses a budget document creation system for preventing calculation errors, transcription errors, subject instruction errors, and the like when creating a budget document for a plan is known. The budget document creation system disclosed in Patent Document 1 registers a subject code and name on a file, and registers an estimate content on the file while referring to this. Next, the budget document creation system checks the calculation error, the transcription error, and the subject instruction error by summing up the registered estimate contents, and if there is no error, outputs the budget document.

JP-A-6-35921

  However, the budget document creation system of Patent Document 1 cannot perform comparative analysis because past aggregated data cannot be reused. In addition, the construction plan is changed every time the budget is adjusted, but if there is no function to hold the contents and details of the change, human work increases. For example, when there are a large number of construction plans (about 1700), a lot of human work is required for rearranging and classifying the construction plan subject for creation and modification of the construction plan, which takes a lot of time. In addition, when the construction plan is frequently changed, it may be unclear which construction plan is the latest and why the construction plan has been changed.

  Therefore, there is a need for a device that can reuse and compare construction plan data and indicate changes and details of construction plans.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a construction plan management apparatus and method capable of reusing and comparing construction plan data and easily showing changes and history of construction plans.

  The present invention provides the following solutions.

  (1) A construction plan management device for managing a construction plan, a construction plan storage means for storing an aggregate construction plan in which a construction plan associated with construction identification information for identifying the construction is provided for a plurality of constructions; Version storage control means for storing a version in the version storage means in association with a copy at an arbitrary point in time of the aggregate construction plan stored in the construction plan storage means; and the aggregate construction plan stored in the construction plan storage means A construction plan extracting means for extracting an arbitrary construction plan from a plurality of construction plans included in the above as a comparison target construction plan, and an aggregated work associated with an arbitrary version among the aggregated construction plans stored in the version storage means Version extracting means for extracting a plan, the construction plan for comparison extracted by the construction plan extracting means, and the version Work plan management device and a construction plan comparing means for comparing a work plan associated with the comparison work plan and the same of the work identification information of the extracted by detecting means the aggregate construction plan.

According to the configuration of (1), the construction plan management apparatus according to the present invention associates a plurality of construction plans with construction identification information and aggregates them and stores them as an aggregate construction plan. Version storage means for storing a version in association with a copy at an arbitrary point of time in the aggregated construction plan stored in Then, the construction plan management device can compare an arbitrary construction plan (comparison target construction plan) stored in the construction plan storage means and an aggregate construction plan associated with any version stored in the version storage means. The construction plan associated with the construction identification information identical to the construction plan is compared.
Thus, by managing and reusing the data of the construction plan, even if the construction plan is changed several times by budget adjustment or the like, the change contents can be easily managed. In addition, since the construction identification information is attached to each construction plan, it is possible to easily compare with a past construction plan even if a large number of constructions exist.

  (2) When a change instruction for the work plan stored in the work plan storage means is received, the work plan change means further stores the changed work plan in the work plan storage means and receives the reason for the change. The construction plan management apparatus according to (1).

  According to the configuration of (2), when an instruction to change the construction plan is received, the construction plan after the change is stored in the construction plan storage unit, and the reason for the change is received. Thereby, in the construction plan management apparatus which concerns on this invention, the reason for change can be shown easily about the changed construction plan.

  (3) When the version storage control unit receives a copy instruction for copying the consolidated construction plan stored in the construction plan storage unit to the version storage unit, the version storage control unit stores the aggregation stored in the construction plan storage unit The construction plan management apparatus according to (1) or (2), wherein a new version is associated with the construction plan and stored in the version storage unit.

  According to the configuration of (3), since it is possible to generate a copy of the aggregated construction plan based on an instruction from the administrator, the construction plan can be reused and compared by version, making it easier to change the construction plan and history Can be shown.

  (4) Upon receiving an instruction to change the construction plan stored in the construction plan storage unit, the version storage control unit associates a new version with the integrated construction plan including the construction plan before the change, and the version The construction plan management apparatus according to any one of (1) to (3), which is stored in a storage unit.

  According to the configuration of (4), since the construction plan before the change is automatically duplicated and stored in association with the version, it can be reused and compared according to the version to easily show the change and the history of the construction plan. it can.

  (5) A construction plan management device for managing a construction plan, comprising construction plan storage means for storing an aggregate construction plan in which a construction plan associated with construction identification information for identifying a construction is provided for a plurality of constructions, is executed. A version storage control step of storing a version in a version storage unit in association with a version at a point in time of the aggregated construction plan stored in the construction plan storage unit, and a method stored in the construction plan storage unit A construction plan extracting step for extracting an arbitrary construction plan as a comparison target construction plan from a plurality of construction plans included in the aggregate construction plan, and corresponding to an arbitrary version of the aggregate construction plans stored in the version storage means A version extracting step for extracting the attached integrated construction plan, and a version extracted by the construction plan extracting step. A construction plan comparison step for comparing a construction plan to be compared with a construction plan associated with the construction identification information identical to the construction plan to be compared among the aggregate construction plans extracted by the version extraction step; A method comprising:

  According to the configuration of (5), as in (1), the latest construction plan can be easily extracted, the construction plan copied and stored is compared by the construction identification information, History can be shown easily.

  According to the present invention, the present invention can facilitate comparison of budget tabulation between the current time and the past by adding a function that can retain and reuse past consolidated data for a construction plan. Further, according to the present invention, change management can be easily performed by adding a function that holds and confirms the reason for changing the construction plan (change contents, history, etc.). Therefore, the present invention can speed up and save labor for the construction work totalization work and change management.

It is a functional block diagram which shows the function of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a figure which shows an example of the hardware constitutions of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a figure which shows the example of construction plan DB which concerns on one Embodiment of this invention. It is a figure which shows the example of version DB which concerns on one Embodiment of this invention. It is a flowchart which shows the processing content of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a flowchart which shows the content of the construction plan comparison process of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a flowchart which shows the content of the construction plan change process of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a flowchart which shows the content of the duplication process of the construction plan management apparatus which concerns on one Embodiment of this invention. It is a figure which shows the example of the menu screen which the construction plan management apparatus which concerns on one Embodiment of this invention displays. It is a figure which shows the example of the construction plan comparison screen which the construction plan management apparatus concerning one Embodiment of this invention displays. It is a figure which shows the example of the construction plan change screen which the construction plan management apparatus concerning one Embodiment of this invention displays. It is a figure which shows the example of the correction screen of the construction plan change screen which the construction plan management apparatus which concerns on one Embodiment of this invention displays. It is a figure which shows the example of the change reason input screen of the construction plan change screen which the construction plan management apparatus which concerns on one Embodiment of this invention displays. It is a figure which shows the example of the version management screen which the construction plan management apparatus which concerns on one Embodiment of this invention displays. It is a figure which shows the example of the confirmation screen of the version management screen which the construction plan management apparatus which concerns on one Embodiment of this invention displays. It is a figure which shows the example of construction plan DB which concerns on Embodiment 2 of this invention. It is a flowchart which shows the content of the construction plan change process of the construction plan management apparatus which concerns on Embodiment 2 of this invention.

[Embodiment 1]
Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a functional block diagram showing functions of a construction plan management apparatus 10 according to an embodiment of the present invention. The construction plan management apparatus 10 includes a construction plan DB 31 as a construction plan storage means, a version DB 32 as a version storage means, a version storage control means 11, a construction plan extraction means 12, a version extraction means 13, and a construction plan comparison. Means 14 and construction plan changing means 15 are included. Each means will be described below.

  The construction plan DB 31 stores an aggregate construction plan in which construction plans associated with construction identification information for identifying construction are provided for a plurality of constructions. That is, the construction plan DB 31 stores individual construction plans in association with construction IDs, collects the individual construction plans, and stores them as an aggregate construction plan. For example, the construction plan includes a construction name, a construction amount, a construction period, and the like (see FIG. 3 described later). Since the construction plan is stored in the construction plan DB 31 when the construction plan is changed, the construction plan extracted from the construction plan DB 31 is the latest construction plan.

  The version storage control unit 11 stores a version in the version DB 32 by associating a version with a copy at an arbitrary point in the aggregated construction plan stored in the construction plan DB 31. At an arbitrary time, there is a case of copying by receiving an instruction from an administrator, or a case of copying automatically when a construction plan is changed. Versions are provided for changes to construction plans, such as initial aggregation of the 2010 mid-term plan and change plans based on interviews with managers of the 2010 mid-term plan, with identification information (version ID) attached. Managed.

  The construction plan extraction means 12 extracts an arbitrary construction plan from the plurality of construction plans included in the aggregate construction plan stored in the construction plan DB 31 as a comparison target construction plan. For example, the construction plan extraction unit 12 accepts an arbitrary construction plan selected by the manager and extracts the accepted construction plan from the construction plan DB 31. The extraction is performed by a search using an edit distance (Levenstein distance) algorithm. Such a search also searches for similar construction names that have a high degree of relevance between character strings for the keyword and the construction name, even if the keyword entered when accepting the construction plan does not match the construction name. be able to.

  The version extraction unit 13 extracts an aggregate work plan associated with an arbitrary version from the aggregate work plans stored in the version DB 32. For example, the version extraction unit 13 receives an arbitrary version input by the administrator, and extracts from the version DB 32 an aggregated construction plan associated with the received version.

The construction plan comparison means 14 is associated with the same construction identification information as the comparison target construction plan among the comparison construction plans extracted by the construction plan extraction means 12 and the aggregate construction plans extracted by the version extraction means 13. Compare the construction plan.
The construction plan management apparatus 10 may display the comparison result by the construction plan comparison unit 14. In this case, it is preferable to clearly indicate a difference in construction amount, a difference in construction period, or the like by displaying different parts in color or displaying only different construction plans. Moreover, the color display of a different location is good also as highlighting with a different color according to a different location. For example, when the construction amount is different, it may be emphasized in blue, and when the construction period is different, it may be emphasized in green.

  When the version storage control unit 11 receives a copy instruction for copying the aggregated construction plan stored in the construction plan DB 31 to the version DB 32, the version storage control unit 11 associates a new version with the aggregated construction plan stored in the construction plan DB 31 and performs versioning. Store in DB32. For example, when the version storage control unit 11 accepts pressing of the copy button 503 (see FIG. 9 described later), the version storage control unit 11 associates a new version with the aggregated construction plan stored in the construction plan DB 31 and stores the new version in the version DB 32 (optional). Duplication).

  When the construction plan changing means 15 receives a change instruction for the construction plan stored in the construction plan DB 31, the construction plan changing means 15 stores the changed construction plan in the construction plan DB 31 and accepts the reason for the change. For example, when the construction plan changing unit 15 accepts pressing of the change button 502 (see FIG. 9 described later), the construction plan changing unit 15 accepts the change of the construction plan and stores the changed construction plan in the construction plan DB 31. Next, the construction plan changing unit 15 receives an input of the reason for the change, and stores the received reason for the change in the version DB 32 arbitrarily copied by the version storage control unit 11.

  FIG. 2 is a diagram illustrating an example of a hardware configuration of the construction plan management apparatus 10 according to an embodiment of the present invention. The construction plan management apparatus 10 includes a CPU (Central Processing Unit) 1000, a communication I / F 1040, a main memory 1050, a BIOS (Basic Input Output System) 1060, an I / O controller 1070, a hard disk 1074, a display device 1080, an input device 1100, and the like. An input / output I / F device 2000 is provided and connected by a bus line 1005.

  The CPU 1000 is a part that controls the construction plan management apparatus 10 in an integrated manner, and by reading and executing various programs stored in the hard disk 1074 as appropriate, the CPU 1000 cooperates with the above-described hardware and performs various functions according to the present invention. Is realized.

  The communication I / F 1040 is a network adapter that enables the construction plan management apparatus 10 to be connected to a user terminal or the like via a dedicated network or a public network.

  The main memory 1050 stores a program that is read and executed as appropriate, and stores various types of information created by the execution of the program. The BIOS 1060 stores a boot program executed by the CPU 1000 when the construction plan management apparatus 10 is started up, a program depending on the hardware of the construction plan management apparatus 10, and the like.

  Storage means such as a hard disk 1074 can be connected to the I / O controller 1070. The hard disk 1074 stores a program for the construction plan management apparatus 10 to execute the functions of the present invention.

  The program provided to the construction plan management apparatus 10 is provided by being stored in a recording medium such as a hard disk 1074 or a memory card. This program may be installed in the construction plan management apparatus 10 and executed by being read from a recording medium via the I / O controller 1070 or downloaded via the communication I / F 1040.

  The display device 1080 displays a screen of a calculation processing result by the construction plan management device 10, a screen for receiving an instruction from the administrator, and the like, and includes a display device such as a cathode ray tube display device or a liquid crystal display device. The input device 1100 is a device that performs input by an operator of the construction plan management device 10 and includes a keyboard and a mouse. The input / output I / F device 2000 connects the construction plan management device 10 to another device such as an auxiliary storage device.

  FIG. 3 is a diagram illustrating an example of the construction plan DB 31 according to an embodiment of the present invention. The construction plan DB 31 stores a construction plan in association with the construction ID. The construction plan is, for example, responsible (name of person in charge, department in charge, etc.), planning schedule, construction period (starting and completion), total construction amount (total budget amount for each fiscal year), construction for the current fiscal year as a breakdown of the total construction amount It consists of the amount (including details of the current year, for example, the amount of work for each quarter) and the amount of work for each year.

  FIG. 4 is a diagram showing an example of the version DB 32 according to an embodiment of the present invention. The version DB 32 stores a copy of the construction plan DB 31 and the reason for changing the construction plan in association with the version ID of the aggregate construction plan. The version ID is, for example, V10_1 (initial summation of the 2010 mid-term plan), V10_2 (change plan based on the hearing of the manager of the 2010 mid-term plan), or the like.

  FIG. 5 is a flowchart showing the processing contents of the construction plan management apparatus 10 according to one embodiment of the present invention.

  In step S101, the CPU 1000 determines whether or not the construction plans are compared. That is, the CPU 1000 determines whether or not a comparison button 501 (see FIG. 9 described later) has been pressed. If this determination is YES, the CPU 1000 moves the process to step S102, and if NO, the CPU 1000 moves the process to step S103.

  In step S102, the CPU 1000 performs a construction plan comparison process (see FIG. 6 described later). Thereafter, the CPU 1000 shifts the processing to step S103.

  In step S103, the CPU 1000 determines whether or not the construction plan is changed. That is, the CPU 1000 determines whether or not a change button 502 (see FIG. 9 described later) has been pressed. If this determination is YES, the CPU 1000 moves the process to step S104, and if NO, the CPU 1000 moves the process to step S105.

  In step S104, the CPU 1000 performs a construction plan change process (see FIG. 7 described later). Thereafter, the CPU 1000 shifts the processing to step S105.

  In step S105, the CPU 1000 determines whether or not the work plan is duplicated. That is, the CPU 1000 determines whether or not the copy button 503 (see FIG. 9 described later) has been pressed. If this determination is YES, the CPU 1000 moves the process to step S106, and if NO, the CPU 1000 moves the process to step S107.

  In step S106, the CPU 1000 performs a construction plan duplication process (see FIG. 8 described later). Thereafter, the CPU 1000 shifts the processing to step S107.

  In step S107, the CPU 1000 determines whether a construction plan is to be created. That is, the CPU 1000 determines whether a creation button 504 (see FIG. 9 described later) has been pressed. If this determination is YES, the CPU 1000 moves the process to step S108, and if NO, the CPU 1000 moves the process to step S109.

  In step S108, the CPU 1000 creates a construction plan. More specifically, the CPU 1000 accepts the contents of the construction plan for the construction plan to be created by using a screen similar to the modification screen (see FIG. 12 to be described later) among the construction plan change screens, and newly explains the reason for changing the construction plan. A construction ID is automatically generated (for example, K100001 in the first case in 2010), an input of a construction name is accepted, and stored in the construction plan DB 31 in association with the construction plan. After that, the CPU 1000 moves the process to step S109.

  In step S109, the CPU 1000 determines whether to perform version management. That is, the CPU 1000 determines whether or not a management button 505 (see FIG. 9 described later) has been pressed. If this determination is YES, the CPU 1000 moves the process to step S110, and if NO, the CPU 1000 moves the process to step S101.

  In step S110, the CPU 1000 performs version management. More specifically, the CPU 1000 displays a version management screen (see FIGS. 14 and 15 described later) on the display device 1080, searches for the received version, and corrects the reason for changing the construction plan in the searched version. Etc. Thereafter, the CPU 1000 shifts the processing to step S101.

  FIG. 6 is a flowchart showing the contents of the construction plan comparison process of the construction plan management apparatus 10 according to one embodiment of the present invention.

  In step S201, the CPU 1000 (construction plan extraction means 12) accepts a construction plan to be compared. More specifically, the CPU 1000 receives an input of a construction name of a construction plan to be compared (see FIG. 10 described later). Thereafter, the CPU 1000 shifts the processing to step S202.

  In step S202, the CPU 1000 (construction plan extraction means 12) extracts the accepted construction plan from the construction plan DB 31. More specifically, the CPU 1000 searches the construction plan DB 31 based on the construction name received in step S201, and extracts the searched construction plan. Thereafter, the CPU 1000 moves the process to step S203.

  In step S203, the CPU 1000 (version extraction unit 13) receives a version. More specifically, the CPU 1000 accepts input of the version name and version ID of the versions to be compared (see FIG. 10 described later). Thereafter, the CPU 1000 shifts the processing to step S204.

  In step S204, the CPU 1000 (version extraction unit 13) extracts the received version from the version DB 32. More specifically, the CPU 1000 searches the version DB 32 using the version ID received in step S203 and extracts the searched version (see FIG. 10 described later). Thereafter, the CPU 1000 shifts the processing to step S205.

  In step S205, the CPU 1000 (construction plan comparison means 14) compares construction plans having the same construction ID. More specifically, the CPU 1000 compares the comparison target construction plan extracted in step S202 with the construction plan associated with the same construction ID as the comparison target construction plan among the versions extracted in step S204. To do. Thereafter, the CPU 1000 shifts the processing to step S206.

  In step S206, the CPU 1000 displays the comparison result in color. More specifically, the CPU 1000 compares items included in the construction plan (in charge, planning schedule, construction period, total construction amount, breakdown of the total construction amount, etc.), and displays different items with color display (for example, construction period Green when there is a difference, blue when the construction amount is different, blue when newly created and red when there is no same construction plan) and display the difference on the display device 1080, or output a comparison table to the printer To do. Thereafter, the CPU 1000 ends the process, and returns the process to the next step after the step that moves to the present process.

  FIG. 7 is a flowchart showing the contents of the construction plan change process of the construction plan management apparatus 10 according to one embodiment of the present invention.

  In step S301, the CPU 1000 (construction plan changing means 15) accepts a construction plan to be changed, and extracts the accepted construction plan from the construction plan DB 31. More specifically, the CPU 1000 receives an input of a construction name of a construction plan to be changed (see FIG. 11 described later). Next, the CPU 1000 searches the construction plan DB 31 by the accepted construction name and displays the searched construction plan (see FIG. 11 described later). Next, the CPU 1000 displays a construction plan selected from the searched construction plans (see FIGS. 11 and 12 described later). After that, the CPU 1000 moves the process to step S302.

  In step S302, the CPU 1000 (construction plan changing means 15) changes the contents of the extracted construction plan according to the accepted contents. More specifically, the CPU 1000 displays the contents of items included in the construction plan (in charge, planning schedule, construction period, total construction amount, breakdown of the total construction amount, etc.) and accepts changes in the contents (FIG. 12 described later). reference). Thereafter, the CPU 1000 shifts the processing to step S303.

  In step S303, the CPU 1000 (construction plan changing unit 15) receives the reason for changing the construction plan, stores the changed construction plan in the construction plan DB 31, and stores the reason for the change in the version DB 32. More specifically, the CPU 1000 displays a reason input screen for the construction plan change screen and accepts input in order to input the reason for changing the construction plan (see FIG. 13 described later). And CPU1000 memorize | stores the construction plan changed by step S302 in construction plan DB31, and memorize | stores the reason for the inputted change in version DB32. Thereafter, the CPU 1000 ends the process, and returns the process to the next step after the step that moves to the present process.

  FIG. 8 is a flowchart showing the contents of the duplication process of the construction plan management apparatus 10 according to the embodiment of the present invention.

  In step S401, the CPU 1000 (version storage control unit 11) receives a version. More specifically, the CPU 1000 receives an input of the version name of the version for associating with the aggregated construction plan to be copied. After that, the CPU 1000 moves the process to step S402.

  In step S402, the CPU 1000 (version storage control means 11) copies the version to the version DB 32 by associating the version with the aggregated construction plan stored in the construction plan DB 31. More specifically, the CPU 1000 associates the version received in step S401 with the aggregated work plan stored in the work plan DB 31, and copies it to the version DB 32. Thereafter, the CPU 1000 ends the process, and returns the process to the next step after the step that moves to the present process.

  FIG. 9 is a diagram illustrating an example of a menu screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. In the menu screen shown in FIG. 9, a comparison button 501 for accepting selection of construction plan comparison processing, a change button 502 for accepting selection of construction plan change processing, and a duplicate button for accepting selection of construction plan duplication processing 503, a creation button 504 for accepting selection of construction plan creation processing, and a management button 505 for accepting selection of version management processing are displayed. The construction plan management apparatus 10 displays the construction plan comparison screen shown in FIG. 10 on the display device 1080 when the pressing of the comparison button 501 is accepted, and the construction plan change screen shown in FIGS. 11 to 13 when the pressing of the change button 502 is accepted. Is displayed on the display device 1080, and when the depression of the copy button 503 is accepted, the construction plan duplication process is performed. When the depression of the creation button 504 is accepted, the construction plan creation process is performed, and when the depression of the management button 505 is accepted, FIGS. Is displayed on the display device 1080.

FIG. 10 is a diagram illustrating an example of a construction plan comparison screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. On the construction plan comparison screen shown in FIG. 10, the construction plan stored in the construction plan DB 31 is compared with the construction plan stored in the version DB 32 and having the same construction ID, and displayed on the display device 1080.
On the construction plan comparison screen, the construction plan management apparatus 10 receives an input of a construction name from the input field 611. The construction plan management apparatus 10 extracts a construction plan (comparison target construction plan) from the construction plan DB 31 based on the accepted construction name. If no construction name is input, the construction plan management apparatus 10 targets all construction plans.
In the construction plan comparison screen, the construction plan management apparatus 10 accepts version input from the input field 612 and extracts an aggregate construction plan associated with the accepted version from the version DB 32.
Then, the construction plan management apparatus 10 compares the comparison target construction plan extracted from the construction plan DB 31 with the construction plan having the same construction ID as the comparison target construction plan among the aggregated construction plans extracted from the version DB 32. The result is displayed in the display field 613 of the display device 1080. For example, in FIG. 10, the display method of different portions is changed (displays the difference by color). Note that the manager may be able to appropriately select items to be compared, for example, charge, planning schedule, construction period, total construction amount, breakdown of the total construction amount, and the like. When the pressing of the comparison table button 512 is accepted, the comparison result is printed on the printer as a comparison table. In the comparison table, for example, the content of the construction plan extracted from the construction plan DB 31 is printed on the left half of the sheet, the construction ID is the same, and the content of the construction plan extracted from the version DB 32 is printed on the right half of the same line. Then, different portions are printed so as to be displayed in color.

FIG. 11 is a diagram illustrating an example of a construction plan change screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. The construction plan change screen shown in FIG. 11 accepts an input of a construction plan whose contents are to be changed.
On the construction plan change screen, the construction plan management apparatus 10 accepts an input of a construction name that is a keyword for searching from the input field 621. When the construction plan management apparatus 10 accepts an input to the input field 621 and detects that the search button 521 is pressed, the construction plan management apparatus 10 searches the construction plan DB 31 by the accepted construction name, and displays a list of retrieved candidates. The content displayed in the display field 622 includes, for example, a construction name and a construction ID.
From the searched construction plans, a construction plan to be corrected is selected (broken line 629), and when the pressing of the correction button 522 is detected, the construction plan management apparatus 10 receives a modification screen for accepting a change in the construction plan (FIG. 12). ).

FIG. 12 is a diagram illustrating an example of a modification screen of the construction plan change screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. In the modification screen of the construction plan change screen shown in FIG. 12, items constituting the construction plan are displayed, and input of change contents of each item is accepted.
When the pressing of the update button 523 is detected after the change content is input in the input field 623 on the correction screen of the work plan change screen, the work plan management apparatus 10 transitions to a change reason input screen (FIG. 13). Also, when the pressing of the delete button 524 is detected, the screen changes to the change reason input screen (FIG. 13).

FIG. 13 is a diagram illustrating an example of a change reason input screen of a work plan change screen displayed by the work plan management apparatus 10 according to an embodiment of the present invention. In the change reason input screen of the construction plan change screen shown in FIG. 13, the input of the reason for changing the construction plan is accepted. Before the construction plan is changed, the consolidated construction plan in the construction plan DB 31 is copied to the version DB 32 in association with the version by pressing the copy button 503 in FIG.
On the change reason input screen of the work plan change screen, the work plan management apparatus 10 receives an input of the reason for change from the input field 624. Next, when detecting that the registration button 525 is pressed, the construction plan management apparatus 10 changes or deletes the construction plan to be changed and stores it in the construction plan DB 31. At this time, the reason for change input in the input field 624 is also stored in the version DB 32.
When the construction plan management apparatus 10 detects that the cancel button 526 has been pressed, the construction plan management apparatus 10 stops changing the construction plan.

FIG. 14 is a diagram illustrating an example of a version management screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. In the version management screen shown in FIG. 14, the input of the version ID is accepted and the selection of the version is accepted.
On the version management screen, the construction plan management apparatus 10 accepts a version ID, which is a keyword for searching for a version, from the input field 651, and when detecting that the search button 551 is pressed, searches the version DB 32 using the received version ID, The retrieved version is displayed in the display field 652. The contents displayed in the display field 652 are, for example, a version ID, a creation date, and a version name. When a version is selected from the displayed versions (broken frame 659) and the pressing of the confirmation button 552 is detected, the construction plan management apparatus 10 transitions to a correction screen (FIG. 15).

FIG. 15 is a diagram illustrating an example of a version management screen confirmation screen displayed by the construction plan management apparatus 10 according to an embodiment of the present invention. In the confirmation screen of the version management screen shown in FIG. 15, a list of reasons for changing the construction plan included in the version selected in FIG. 14 is displayed.
On the confirmation screen of the version management screen, not only a list of reasons for changing the construction plan included in the version but also the correction of the reason for change may be possible. Specifically, in FIG. 15, when the pressing of the correction button 553 is detected, the construction plan management apparatus 10 accepts the modification of the reason for changing the construction plan, and the contents newly input in the display field 653 and the modification are corrected. The contents are stored in the version DB 32 in association with the construction plan.

  According to the first embodiment, the construction plan management apparatus 10 includes a construction plan DB 31 for storing an aggregate construction plan in which a construction plan associated with construction identification information for identifying a construction is provided for a plurality of constructions. A version is associated with a copy at an arbitrary point of the stored aggregate construction plan and stored in the version storage means. Then, the construction plan management apparatus 10 extracts an arbitrary construction plan from the plurality of construction plans included in the aggregate construction plan stored in the construction plan DB 31 as a comparison target construction plan, and stores the aggregate construction plan stored in the version DB 32. An aggregated construction plan associated with an arbitrary version is extracted, and the extracted comparison target construction plan, and a construction plan associated with the same construction ID as the comparison target construction plan among the extracted aggregated construction plans, Compare. Furthermore, the construction plan management apparatus 10 performs duplication from the construction plan DB 31 to the version DB 32 by receiving a duplication instruction. When the construction plan management apparatus 10 receives a change instruction for the construction plan stored in the construction plan DB 31, the construction plan management apparatus 10 stores the changed construction plan in the construction plan DB 31, and the reason for the change received together with the change in the version DB 32. Remember. Therefore, the construction plan management apparatus 10 can easily extract the latest construction plan from the construction plan DB 31, compare the construction plan stored in the version DB 32 with the construction ID, and easily change or modify the construction plan. Can show.

[Embodiment 2]
In the second embodiment, the construction plan management apparatus 10 stores the reason for change in the construction plan DB 31 in addition to the first embodiment, and performs automatic duplication along with the change of the construction plan.

  When the construction plan changing means 15 receives the instruction to change the construction plan stored in the construction plan DB 31, the construction plan changing means 15 stores the changed construction plan in the construction plan DB 31 and accepts the reason for the change. The construction plan DB 31 is stored together with the reason for the accepted change. For example, when the construction plan changing means 15 accepts the pressing of the change button 502 (see FIG. 9), the construction plan changing means 15 accepts the input of the reason for the change after accepting the change of the construction plan, and the changed construction together with the reason for the accepted change. The plan is stored in the construction plan DB 31. Furthermore, when the construction plan is changed, the construction plan changing unit 15 may relate the changed construction plan and the construction plan copied to the version DB 32 (for example, link them with a pointer). The construction plan management apparatus 10 can easily refer to the construction plan before the change about the changed construction plan, and can easily show the history of the change.

  Further, when the version storage control unit 11 receives an instruction to change the construction plan stored in the construction plan DB 31, the version storage control unit 11 stores the new version in the version DB 32 in association with the aggregated construction plan including the construction plan before the change. For example, when the pressing of the change button 502 (see FIG. 9) is accepted and the construction plan is changed by the construction plan changing unit 15, the version storage control unit 11 includes an integrated construction plan including the construction plan before being changed. The new version is associated with and stored in the version DB 32 (automatic replication).

  FIG. 16 is a diagram illustrating an example of the construction plan DB 31 according to the second embodiment of the present invention. The construction plan DB 31 stores a construction plan and a reason for change in association with the construction ID. The construction plan is the same as in the first embodiment. The reason for the change is accepted and stored when the construction plan is changed.

  FIG. 17 is a flowchart showing the contents of the construction plan change process of the construction plan management apparatus 10 according to the second embodiment of the present invention. Steps S601 and S602 are the same as steps S301 and S302 of the first embodiment.

  In step S603, the CPU 1000 (construction plan changing unit 15) receives the reason for changing the construction plan, as in the first embodiment. Then, the CPU 1000 stores the changed construction plan in the construction plan DB 31 together with the reason for the change. After that, the CPU 1000 moves the process to step S604.

  In step S604, the CPU 1000 (construction plan changing unit 15) associates the version with the aggregated construction plan before the change and copies it to the version DB 32. For the version, for example, the CPU 1000 automatically generates a version ID consisting of a year (V10_1 is the first time in 2010), and receives the input of the version name to create a version. Thereafter, the CPU 1000 ends the process, and returns the process to the next step after the step that moves to the present process.

  According to the second embodiment, when the construction plan management apparatus 10 receives an instruction to change the construction plan stored in the construction plan DB 31, the construction plan management apparatus 10 stores the modified construction plan in the construction plan DB 31 together with the reason for the change. Further, the construction plan management apparatus 10 automatically duplicates the construction plan DB 31 to the version DB 32. Therefore, the construction plan management device 10 can easily extract the latest construction plan from the construction plan DB 31 together with the reason for the change, compare the construction plan stored in the version DB 32 by the construction ID, and change the construction plan. History can be shown easily.

  In the present embodiment, the construction plan DB 31 and the version DB 32 are provided in the construction plan management apparatus 10, but the version DB 32 may be a version management apparatus different from the construction plan management apparatus 10 and connected via a dedicated line. Good. The processing burden on the construction plan management apparatus 10 can be reduced.

  As mentioned above, although embodiment of this invention was described, this invention is not restricted to embodiment mentioned above. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments of the present invention. is not.

DESCRIPTION OF SYMBOLS 10 Construction plan management apparatus 11 Version storage control means 12 Construction plan extraction means 13 Version extraction means 14 Construction plan comparison means 15 Construction plan change means 31 Construction plan DB
32 Version DB
1080 Display device

Claims (5)

A construction plan management device for managing construction plans,
Construction plan storage means for storing an aggregate construction plan in which a construction plan associated with construction identification information for identifying the construction is provided for a plurality of constructions;
Version storage control means for associating a version with a copy at an arbitrary point in time of the aggregate construction plan stored in the construction plan storage means and storing the version in the version storage means;
Construction plan accepting means for accepting input of the construction identification information;
The extracted work plan identified by the work identification information accepted by the construction plan reception unit, a plurality of construction plan or al comparisons target work plan contained in said stored aggregated work plan in the construction plan storage means Construction plan extraction means to perform,
An aggregate work selection means for accepting input of the version to select an aggregate work plan;
And version extracting means for extracting the aggregate work plan associated with the version received by the aggregate construction selection means, from said stored aggregated work plan in the version storage unit,
The items included in the comparison target construction plan extracted by the construction plan extraction unit are associated with the same construction identification information as the comparison target construction plan among the aggregated construction plans extracted by the version extraction unit. A construction plan comparison means for comparing items included in the construction plan and displaying a comparison result ;
Construction plan management device with   The construction plan changing means further comprising: a construction plan changing means for storing the construction plan after the change in the construction plan storage means and receiving the reason for the change when the construction plan change instruction stored in the construction plan storage means is received. The construction plan management device described in 1.   When the version storage control unit receives a copy instruction for copying the consolidated construction plan stored in the construction plan storage unit to the version storage unit, the version storage control unit stores the integrated construction plan in the construction plan storage unit. The construction plan management apparatus according to claim 1, wherein a new version is associated and stored in the version storage unit.   When the version storage control unit receives the instruction to change the construction plan stored in the construction plan storage unit, the version storage control unit associates a new version with the aggregated construction plan including the construction plan before the change in the version storage unit. The construction plan management apparatus according to claim 1, wherein the construction plan management apparatus is stored. This is a method executed by a construction plan management device for managing a construction plan, comprising construction plan storage means for storing an aggregate construction plan in which a construction plan associated with construction identification information for identifying a construction is provided for a plurality of constructions. And
A version storage control step of associating a version with a copy at an arbitrary time of the aggregated construction plan stored in the construction plan storage means and storing the version in the version storage means;
A construction plan reception step for receiving the construction identification information;
The extracted work plan identified by the work identification information accepted by the construction plan accepting step, a plurality of construction plan or al comparisons target work plan contained in said stored aggregated work plan in the construction plan storage means A construction plan extraction step to perform,
An aggregate work selection step for accepting input of the version to select an aggregate work plan;
And version extracting said aggregate construction selected aggregation work plan associated with the version received by step, from said stored aggregated work plan in the version storage unit,
The items included in the comparison target construction plan extracted in the construction plan extraction step are associated with the same construction identification information as the comparison target construction plan among the aggregated construction plans extracted in the version extraction step. A construction plan comparison step for comparing the items included in the construction plan and displaying the comparison result ;
A method comprising:

Images