JP5766013B2 - Progress management device, progress management system, progress management method, and progress management program - Google Patents

Description

  The present invention relates to a progress management device, a progress management system, a progress management method, and a progress management program.

  In the work of formulating a development schedule in product development or the like and grasping the progress of the product development, the required information differs depending on the job title related to the product development. For example, a practitioner (designer or the like) needs to manage the progress of all tasks that he is in charge of. Managers (design managers, etc.) need to confirm the schedule and performance of development hold points (drawing review / drawing meetings, etc.) at the level of development management regulations and the status of creation of design deliverables. Managers (factory managers, manufacturing managers, etc.) need to check the progress of multiple developed products throughout the factory.

  In this way, since the time unit of the required information becomes larger as the senior position becomes higher, it is necessary to reflect the lower level progress information to the upper level, but there are problems such as manual transcription mistakes and lack of immediacy. It was. A system that links schedule information (planned schedules / actual schedules, etc. for each task) between large schedules (monthly), medium schedules (weekly), and small schedules (daily) for such problems is as follows. It is disclosed in Patent Document 1.

JP 2006-072413 A

  However, according to the technique described in Patent Document 1, schedule information with different time units is linked, but only by linkage of schedules, the practitioner can make a self-judgment with the preceding development hold points incomplete. It is not possible to determine whether there is a “skip” that completes the next and subsequent development hold points, or an “overtaking” that precedes the next development hold point when the previous development hold point is incomplete. . For this reason, the progress management method of Patent Document 1 has a problem that the manager layer and the manager layer may not be able to recognize “skip” or “pass”.

  The present invention has been made in view of the above, and avoids manual transcription mistakes and immediacy, reflects lower-level progress information to the upper level, and performs product development in the original order in units of development hold points. It is an object of the present invention to obtain a progress management device, a progress management system, a progress management method, and a progress management program that can easily determine whether or not the program is being handled.

  In order to solve the above-described problems and achieve the object, the present invention performs progress management using upper schedule management information that is schedule management information of an upper hierarchy and lower schedule management information that is schedule management information of a lower hierarchy. A progress management device for performing schedule management information for each development hold point generated based on the upper schedule management information and the lower schedule management information as schedule management registration information, and a development hold For each point, the planned schedule reflection processing unit for updating the planned schedule in the lower schedule management information and the planned schedule in the schedule management registration information based on the planned schedule included in the higher schedule management information, and each development hold point In addition, the actual schedule in the upper schedule management information and the actual schedule in the schedule management registration information are updated based on the actual schedule included in the lower schedule management information. An actual schedule reflection processing unit, and the actual schedule reflection processing unit performs a process for determining whether or not product development is performed in an original order in units of development hold points based on the schedule management registration information. The determination result by the determination process is added to the upper schedule management information.

  According to the present invention, it is possible to easily determine whether or not product development is performed in the original order in units of development hold points by preventing manual transcription mistakes and immediacy and reflecting low-order progress information to the high-order. There is an effect that can be done.

FIG. 1 is a diagram illustrating a functional configuration example of the progress management device. FIG. 2 is a diagram illustrating a configuration example of a computer or the like used as a progress management device. FIG. 3 is a diagram showing an outline of the overall operation of the embodiment. FIG. 4 is a flowchart illustrating an example of the operation of the planned schedule reflection processing unit. FIG. 5 is a diagram illustrating a configuration example of the process management table. FIG. 6 is a diagram illustrating a configuration example of the small schedule management table. FIG. 7 is a diagram illustrating a configuration example of a schedule management database. FIG. 8 is a flowchart showing an example of the operation of the design product monitoring processing unit. FIG. 9 is a diagram illustrating an example of a file in the completed design product storage folder. FIG. 10 is a flowchart illustrating an example of the operation of the actual schedule reflection processing unit. FIG. 11 is a diagram illustrating a configuration example of the progress management table.

  Embodiments of a progress management device, a progress management system, a progress management method, and a progress management program according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram illustrating a functional configuration example of a progress management apparatus according to the present invention. As shown in FIG. 1, the progress management device 1 according to the present embodiment includes a planned schedule reflection processing unit 11, an actual schedule reflection processing unit 12, and a design product monitoring processing unit 13, and a schedule management database ( (Schedule management registration information) 14 is stored. The progress management device 1 is connected to a management table holding device 2 and a design product management device 3 through a network or the like.

  The progress management device 1 is, for example, a general computer. FIG. 2 is a diagram illustrating a configuration example of a computer or the like used as the progress management device 1. As shown in FIG. 2, the computer includes a control unit 41 that is a calculation means such as a CPU, an input unit 42 that is a keyboard or a mouse, and various memories such as a RAM (Random Access Memory) and a ROM (Read Only Memory). And a storage unit 43 that is a storage device such as a hard disk, a display unit 44 that is a monitor, and a communication unit 45 that is connected to a network or the like and communicates with other devices. They are connected by a bus 46. Note that the configuration of FIG. 2 is an example, and the configuration of a computer or the like used as the progress management device 1 is not limited to FIG.

  The control unit 41 executes various programs including a progress management program according to the present invention. The input unit 42 is used by the user to input various information as necessary. The storage unit 43 stores programs to be executed by the control unit 41, necessary data obtained in the course of processing, and the like. The storage unit 43 is also used as a temporary storage area for programs. The display unit 4 displays information to be displayed to the user.

  Here, an operation example until the progress management program becomes executable will be described. In the computer having the above-described configuration, for example, a progress management program is installed in the storage unit 43 from a recording medium set in a CD / DVD drive (not shown). When the progress management program is executed, the progress management program read from the storage unit 43 is stored in a predetermined location in the storage unit 43. In this state, the control unit 41 executes the progress management process according to the program stored in the storage unit 43.

  In the present embodiment, a program describing the progress management process is provided by a recording medium. However, the present invention is not limited to this, and a program provided by a transmission medium such as e-mail or the Internet is used. Also good.

  The functional configuration example of FIG. 1 shows a configuration example when the progress management program is ready to be executed. The planned schedule reflection processing unit 11, the actual schedule reflection processing unit 12, and the design product monitoring processing unit 13 are It exists on the control unit 41 and operates using the storage unit 43 as a temporary storage unit as necessary. The schedule management database 14 is stored in the storage unit 43.

  The management table holding device 2 and the design product management device 3 shown in FIG. 1 are also, for example, the computer having the configuration example shown in FIG. 2, and the management table holding device 2 stores the progress management table (maximum) in the storage unit 43. The upper schedule management information) 21, the process management table (upper schedule management information) 22, and the small schedule table (lower schedule management information) 23 are held, and the design artifact management apparatus 3 stores the completed design artifact storage folder in the storage unit 43. The design product 32 stored in 31 is held.

  1, the management table holding device 2 holds the progress management table 21, the process management table 22, and the small schedule table 23, and the design product management device 3 holds the design product 32. Not limited to this, the progress management device 1 may hold the progress management table 21, the process management table 22, the small schedule table 23, and the design deliverable 32. Further, the progress management device 1 holds a progress management table 21, a process management table 22, and a small schedule table 23, and the design product management device 3 holds a design product 32, or the progress management device 1 designs. The deliverable 32 may be held, and the management table holding device 2 may hold the progress management table 21, the process management table 22, and the small schedule table 23.

Here, a three-level schedule management table used in the present embodiment is defined as follows.
(1) Progress Management Table (Large Schedule) 21: The top level hierarchy / development hold point is a table / development hold point “skip” that shows the minimum plan necessary for business management and the end schedule of results. ”,“ Overtaking ”alert display (2) Process management table (medium schedule) 22: WBS (Work Breakdown Structure) number and plan schedule (plan start date / plan end date) for each upper layer / development hold point are entered Specification of design deliverables that need to be created in the table / development hold points / designation of the development hold points to be displayed in the progress management table / development hold points results schedule (actual start date / Results end date) Display / development hold point “Blow”, “Overtaking” alert display • Design deliverable registration (3) Small schedule management table (Small schedule) 2 : The table at the lower levels and performance schedule is input

  In the process management table 22, the schedule and design deliverables are input by the manager. At this time, the administrator may input by operating the management table holding device 2, but the process management table 22 by operating another device (such as a personal computer) connected to the management table holding device 2. Input may be made. In the small schedule management table 23, the contents of the process management table 22 are reflected for the planned schedule and the design deliverables, and the actual schedule is input by the practitioner. At this time, the practitioner may input by operating the management table holding device 2, but by operating another device (such as a personal computer) connected to the management table holding device 2. 23 may be input.

  In the small schedule management table 23, each item is described in units of tasks obtained by further breaking down the WBS number unit managed by the process management table 22. It is assumed that the number (or name) of the broken down task is described in advance in the small schedule management table 23 by an administrator or a practitioner.

  The development hold point indicates a drawing examination / drawing meeting and the like, and is a timing for evaluating development performed in stages. After all necessary evaluations and operations are performed at a certain development hold point (hereinafter, the development hold point is completed), the next development hold point is performed.

  Here, the WBS number is used to identify the work, but it is only necessary to be able to identify each work, and the work name or the like is not limited to the WBS number.

  FIG. 3 is a diagram showing an outline of the overall operation of the present embodiment. The plan schedule reflection processing unit 11 reads the process management table 22, registers the plan schedule and design deliverables in the process management table 22 in the schedule management database 14, and reflects the plan schedule in the small schedule management line 23.

  The actual schedule reflection processing unit 12 reads the small schedule management line 23, registers the actual schedule in the small schedule management line 23 in the schedule management database 14, and reflects the actual schedule in the process management table 22. The design product monitoring processing unit 13 searches the completed design product storage folder 31 to monitor whether or not the design product 32 is newly registered. When the design product 32 is newly registered, The completion of the generation of the design deliverable 3 is registered in the schedule management database 14.

  In addition, the actual schedule reflection processing unit 12 performs “jumping” in which the practitioner completes the next and subsequent development hold points by the self-judgment in a state where the preceding development hold points are not completed based on the schedule management database 14. It is determined whether or not “overtaking” for starting the next development hold point in the state where the development hold point is incomplete has occurred, and the determination result is registered in the schedule management database 14. Then, the actual schedule reflection processing unit 12 describes in the progress management table 21 the minimum necessary plan, the actual end schedule, and the presence / absence of “skip” or “overtaking” based on the schedule management database 14. In addition, the performance schedule reflection processing unit 12 reflects the presence / absence of “skip” or “pass” in the process management table 22.

  Hereinafter, each operation | movement of the plan schedule reflection process part 11, the performance schedule reflection process part 12, and the design product monitoring process part 13 is demonstrated using figures.

  FIG. 4 is a flowchart illustrating an example of the operation of the planned schedule reflection processing unit 11. The plan schedule reflection processing unit 11 reads the process management table 22 and registers the WBS number, the plan schedule, and the design product in the process management table 22 in the schedule management database 14 (step S11). At this point, it is assumed that the WBS number, the schedule, and the design deliverable in the process management table 22 have already been input.

  FIG. 5 is a diagram illustrating a configuration example of the process management table 22 according to the present embodiment. As shown in FIG. 5, the process management table 22 includes a WBS number, task name, “skip / overtake”, progress management table linkage, plan schedule (abbreviated as plan in FIG. 5), actual schedule (abbreviated as actual in FIG. 5). ), Each of the items of design deliverables (abbreviated as deliverables in FIG. 5). The order of the items is not limited to the example of FIG. 5 and may include items other than those shown in FIG.

  Of the items illustrated in FIG. 5, the WBS number, task name, planned schedule, and deliverables have been input by the administrator at the start of step S11 or have been described in advance by another operator or the like. . Note that the progress management linkage in FIG. 5 is an item provided for identifying each hold point with a symbol (such as ○, □) in the progress management table 21, and the hold point is displayed with a symbol in the progress management table 21. If not, this item is not necessary. The “skip / overtake” and the actual schedule will be described in the operation of the actual schedule reflection processing unit 12 described later.

  Next, the plan schedule reflection processing unit 11 reads the small schedule management table 23 (step S12) and determines whether there is a task that matches the WBS number in the process management table 22 among the tasks in the small schedule management table 23. Is checked (step S13). As a result of the check, if it is determined that there is a task that matches the WBS number in the process management table 22 among the tasks in the small schedule management table 23 (Yes in step S14), the process management table for the task that matches the WBS number. The 22 schedules are reflected in the small schedule management table 23 (step S15), and the process is terminated. If there is no task that matches the WBS number in the process management table 22 among the tasks in the small schedule management table 23 (No in step S14), the process ends.

  FIG. 6 is a diagram illustrating a configuration example of the small schedule management table 23 according to the present embodiment. As shown in FIG. 6, the small schedule management table 23 is composed of items of WBS number, task name, hierarchy, planned schedule (abbreviated as plan in FIG. 6), and actual schedule (abbreviated as actual in FIG. 6). . Note that the order of the items is not limited to the example of FIG. 6, and may include items other than those shown in FIG. For example, a design product item may be further included, and the contents of the design product in the process management table 22 may be reflected in the small schedule management table 23.

  As described above, in the small schedule management table 23, a task obtained by further breaking down the task in units of WBS numbers managed by the process management table 22 is also registered. The hierarchy of FIG. 6 shows the hierarchy of the work that has been broken down. Here, the task corresponding to the WBS number is one hierarchy, the hierarchy that is broken down from the first hierarchy is two, and so on. In this example, the small schedule management table 23 describes an example in which a task that is further broken down by a task in units of WBS numbers is registered, but the breakdown may not be performed.

  The planned schedule reflection processing unit 11 performs the above-described operation when the planned schedule is first input to the process management table 22, and thereafter performs the above-described operation when, for example, the process management table 22 is updated. To do. Regardless of the update of the process management table 22, for example, the above-described operation may be performed periodically, or when the progress management table 21 is to be updated, the above-described operation may be performed.

  FIG. 7 is a diagram illustrating a configuration example of the schedule management database 14 according to the present embodiment. The schedule management database 14 includes items such as a WBS number, a task name, a planned schedule, an actual schedule, a deliverable, a completion flag, and a “skip / overtake” item. As described above, the WBS number, task name, plan schedule, and design deliverable (abbreviated as deliverable in FIG. 7) are transferred from the process management table 22. The completion flag is information indicating whether or not all the deliverables for each WBS number have been created, and stores a value indicating incomplete in the initial state (here, “0” as an example). The completion flag is updated by the operation of the design product monitoring processing unit 13.

  FIG. 8 is a flowchart illustrating an example of the operation of the design product monitoring processing unit 13. As illustrated in FIG. 8, the design product monitoring processing unit 13 checks the completed design product storage folder 31 and determines whether there is a file whose name matches the design product registered in the schedule management database 14. (Step S21).

  When there is a file whose name matches the design deliverable registered in the schedule management database 14 (Yes in step S22), a completion flag corresponding to the design deliverable in the schedule management database 14 is set to a value (here). Then, it is updated to “1” as an example (step S23), and the process is terminated. If there is no file whose name matches the design deliverable registered in the schedule management database 14 (No in step S22), the process is terminated.

  The design deliverable monitoring processing unit 13 performs the above operation, for example, periodically. For example, the above operation can be performed by batch processing. In the present embodiment, the design product monitoring processing unit 13 of the progress management device 1 performs the above-described processing. However, the design product management device 3 performs the above steps S21 and S22, and schedule management. When there is a file whose name matches the design product registered in the database 14, the design product monitoring processing unit 13 of the progress management apparatus 1 is notified, and the design product monitoring processing unit 13 performs the above based on the notification. You may make it implement step S23 of.

  FIG. 9 is a diagram illustrating an example of a file in the completed design product storage folder 31. As shown in FIG. 9, the document AAA. xls and the like are stored.

  FIG. 10 is a flowchart illustrating an example of the operation of the actual schedule reflection processing unit 12. As shown in FIG. 10, the actual schedule reflection processing unit 12 reads the small schedule management table 23 (step S31), and among the tasks of the small schedule management table 23, the WBS number of the process management table 22 (that is, in the schedule management database). It is checked whether there is a match with the registered WBS number (step S32).

If there is a task that matches the WBS number in the process management table 22 among the tasks in the small schedule management table 23 (Yes in step S33), the actual schedule in the small schedule management table 23 for the task that matches the WBS number (Step S34). Then, the performance schedule reflection processing unit 12 checks whether or not the development hold point “skip” exists (step S35). Specifically, for example, if any of the following applies, it is determined to be “skip”.
In the actual schedule reflected in the schedule management database 14 from the small schedule management table 23, the actual completion date of the development hold point corresponding to a certain WBS number is not entered, and the WBS number is larger than this WBS number (= time The actual completion date of the development hold point (located later) is input. In the schedule management database 14, the actual completion date of the development hold point corresponding to a certain WBS number is input. When all the corresponding design deliverables have not been created (all have not been completed), and the actual completion date of the development hold point whose WBS number is greater than this WBS number has been entered

  Here, it is assumed that the WBS number is assigned a smaller (smaller) number for the preceding task. If the WBS number is not assigned a smaller (smaller) number than the preceding task, for example, a table in which the WBA numbers are listed in the preceding order is retained, and “skip” is similarly performed based on the table. What is necessary is just to judge whether it exists.

  As a result of the check in step S35, if “skip” exists (step S36 Yes), it is confirmed that the “skip / overtake” flag corresponding to the skipped development hold point in the schedule management database 14 is “skip”. The value is updated (in this example, “1” as an example) (step S37).

Next, the performance schedule reflection processing unit 12 checks whether or not “overtaking” exists (step S38). Specifically, for example, if any of the following applies, it is determined that the vehicle is “overtaking”.
In the actual schedule reflected in the schedule management database 14 from the small schedule management table 23, the actual completion date of the development hold point corresponding to a certain WBS number is not entered, and the WBS number is larger than this WBS number (= time In the case where the actual start date of the development hold point (which is located later) is input. In the schedule management database 14, the actual completion date of the development hold point corresponding to a certain WBS number is input. When all the corresponding design deliverables have not been created (all have not been completed) and the actual start date of the development hold point with a WBS number greater than this WBS number has been entered

  As a result of the check in step S38, if “overtaking” exists (step S39 Yes), it is confirmed that the “skip / overtake” flag corresponding to the development hold point being overtaken in the schedule management database 14 is “skip”. It is checked whether the value is “1” (here, “1” as an example) (step S40). As a result of the check, if the flag corresponding to the development hold point (the hold point being overtaken) is not a value indicating that there is a “skip” (Yes in step S41), the hold that has been overtaken in the schedule management database 14 The “skipping / overtaking” flag corresponding to the point is updated to a value indicating “overtaking” (here, “2” as an example) (step S42).

  Next, the actual schedule reflection processing unit 12 updates the “skip / overtake” item of the corresponding WBS number in the process management table 22 based on the “skip / overtake” flag in the schedule management database 14 (step S43). . For example, for the WBS number (corresponding to the hold point) in which the “jump / overtake” flag in the schedule management database 14 has a value “jump”, “jump / overtake” in the process management table 22 shown in FIG. In the column of, a symbol indicating that “skip” exists is plotted. Similarly for “overtaking”, a symbol indicating that “overtaking” exists is plotted in the “skipping / overtaking” column of the WBS number where “overtaking” exists based on the schedule management database 14.

  Further, the actual schedule reflection processing unit 12 corresponds to the symbol in the column of the progress management table in the process management table 22 for each hold point on the basis of the schedule management database 14 and the plan and actual end date of the progress management table 21. And the presence / absence of “skip / overtake” are plotted (step S44), and the process ends.

  FIG. 11 is a diagram illustrating a configuration example of the progress management table 21. In step S44, the information in the schedule management database 14 is reflected in the progress management table 21 in the format shown in FIG. 11, for example. Here, only one symbol is shown in the “skip / overtake” column of the progress management table 21. This is because the progress management table 21 is generally used by management to roughly grasp the progress status of multiple products (identified by development management number), so there is “jumping” or “overtaking” for each product. This is to make it possible to grasp whether or not to do. In addition, since “skip” is more problematic than “pass” (higher priority), if both “pass” and “skip” are present, a symbol indicating that “skip” is present is plotted. .

  Returning to the description of FIG. 10, if there is no task in the small schedule management table 23 that matches the WBS number in the process management table 22 (No in step S33), the process proceeds to step S35. When there is no development skip point “skip” (No in step S36), the process proceeds to step S38, and when there is no development hold point “pass” (step S39, No), the process proceeds to step S44. On the other hand, if the flag corresponding to the hold point being overtaken is a value indicating that “skip” is present (No in step S41), the process proceeds to step S43.

  The above operation of the actual schedule reflection processing unit 12 may be performed periodically, for example, or may be performed when the schedule management database 14 is updated. Moreover, you may implement when progress management table 21 needs to be produced | generated.

  Next, a determination example of “skip” and “pass” will be described with reference to FIGS. 5, 6, 9, and 11. As shown in FIG. 5, for the hold point B, the end date of the record is entered in the small schedule management table 23. Therefore, the hold point B, which is the development hold point, appears to be completed only in the small schedule management table 23, but if the completed design product folder 31 is in the state shown in FIG. Document B. xls does not exist. Accordingly, the actual schedule reflection processing unit 12 determines that the hold point B has not been completed, and the end point of the actual result is input to the hold point C, which is the next development hold point, and is stored in the completed design product folder 31. Document C. Since xls exists, it can be determined that a “skip” has occurred in which the preceding hold point B is not completed and the next hold point C is completed.

  For hold point D, which is the development hold point, the end date of the record is not entered in the small schedule management table 23 and is not completed, but the start date of the record is entered at hold point E, which is the next development hold point. Therefore, it can be determined that “overtaking” has occurred. Here, in order to explain the phenomenon that has occurred, the example of determination of “skip” and “overtake” has been described using the storage status in the small schedule management table 23 and the completed design product folder 31. As described above, the actual schedule reflection processing unit 12 makes the above determination based on the schedule management database 14 in which these contents are reflected.

  In the above example, it is determined that “overtake” exists for the hold point D and “skip” exists for the hold point B. In this case, the progress management table 21 displays a symbol indicating that “skip” exists, as shown in FIG.

  In this embodiment, the example in which the WBS number corresponds to the development hold point on a one-to-one basis has been described. However, when the WBS number does not correspond to the development hold point on a one-to-one basis (two developments per one WBS number). When there is a hold point or when two WBS numbers correspond to one development hold point), the process for each WBS number may be replaced with the process for each development hold point.

  In the present embodiment, the case where the schedule management table has three layers has been described. However, the schedule management table also includes only two layers of the upper layer (process management table) and the lower layer (small schedule management table 23). The above-described operations can be applied (except for the reflection operation to the progress management table 21). In addition, even when the upper and lower layers are further divided into a plurality of layers, the plan schedule is reflected in order from the upper layer to the lower layer in the upper layer, and from the lower layer in the lower layer. The actual schedule is reflected in order on the upper hierarchy, and the schedule management table of the lowest hierarchy in the upper hierarchy and the schedule management table of the highest hierarchy in the lower hierarchy are respectively stored in the process management table 22 described above. If treated as the small schedule management table 23, the above-described operation can be applied. In this case, the determination results of “skip” and “overtake” may be reflected in the schedule management table of all layers in the upper layer.

  As described above, in the present embodiment, for the schedule, the schedule schedule reflection processing unit 11 reflects the schedule from the schedule management table in the higher hierarchy to the schedule management table in the lower hierarchy and plans for each development hold point. The schedule is registered in the schedule management database 14, and the actual schedule reflection processing unit 12 reflects the schedule from the lower hierarchy schedule management table to the upper hierarchy schedule management table, and the actual schedule for each development hold point. Is registered in the schedule management database 14. Further, the design product monitoring processing unit 13 determines whether or not the generation of the product defined for each development hold point has been completed, registers the determination result in the schedule management database 14, and the actual schedule reflection processing unit 12 determines based on the schedule management database 14 whether or not “skip” and “overtake” exist and reflect the determination result in the schedule management table.

  For this reason, it is possible to prevent manual posting mistakes and immediacy and reflect the lower level progress information to the upper level, and whether or not the product development is performed in the original order in units of development hold points ("flip" of hold points) And “overtaking” or not) can be accurately determined. In addition, by immediately reflecting this determination result in the schedule management table of the upper hierarchy (including the upper hierarchy again), it is possible to take an early measure.

DESCRIPTION OF SYMBOLS 1 Progress management apparatus 2 Management table holding apparatus 3 Design deliverable management apparatus 11 Plan schedule reflection processing part 12 Actual schedule reflection processing part 13 Design deliverable monitoring processing part 14 Schedule management database 21 Progress management table 22 Process management table 23 Small schedule management Table 31 Completed design product storage folder 32 Design product 41 Control unit 42 Input unit 43 Storage unit 44 Display unit 45 Communication unit 46 System bus

Claims (9)

A progress management device that performs progress management using upper schedule management information that is upper-layer schedule management information and lower schedule management information that is lower-layer schedule management information,
A storage unit for storing schedule management information for each development hold point generated based on the upper schedule management information and the lower schedule management information as schedule management registration information;
For each development hold point, a plan schedule reflection processing unit for updating the plan schedule in the lower schedule management information and the schedule schedule in the schedule management registration information based on the plan schedule included in the higher schedule management information;
For each development hold point, an actual schedule reflecting processor for updating the actual schedule in the upper schedule management information and the actual schedule in the schedule management registration information based on the actual schedule included in the lower schedule management information;
With
The actual schedule reflection processing unit performs a process of determining whether or not product development is performed in an original order in units of development hold points based on the schedule management registration information, and the determination result by the determination process is displayed as the higher order A progress management device characterized by adding to schedule management information.   The actual schedule reflection processing unit performs the determination process as “jumping” in which the next development hold point is completed in a state where the preceding development hold point is incomplete, and in the state where the preceding development hold point is incomplete. The progress management device according to claim 1, wherein it is determined whether or not “overtaking” for starting the development hold point of the first time has occurred.   The actual schedule reflection processing unit adds the end date and the actual date of the planned schedule for each development hold point based on the schedule management registration information to the highest-level schedule management information that is higher-level schedule management information than the higher-level schedule management information. The progress management apparatus according to claim 1, wherein an end date of the schedule and the determination result are stored.   The actual schedule reflection processing unit selects, as the determination result stored in the highest-level schedule management information, one determination result having a high priority among the determination results obtained by the determination process. The progress management device according to claim 3. It is monitored whether or not the design deliverable registered as the design deliverable specified in the schedule management registration information is generated, and all the specified design deliverables in the schedule management registration information are generated. A design product monitoring processing unit for storing information indicating completion of generation of a design product in the schedule management registration information for the development hold point;
Further comprising
The actual schedule reflection processing unit updates the specified design product in the schedule management registration information for each development hold point based on the specified design product included in the higher-level schedule management information, and in the determination process For development hold points where all of the specified design deliverables have not been generated based on the schedule management registration information, even if it is determined that the development hold point has ended based on the actual schedule of the schedule management registration information, The progress management apparatus according to claim 2, wherein the hold point is determined not to be completed. A progress management system that performs progress management using upper schedule management information that is schedule management information of an upper hierarchy and lower schedule management information that is schedule management information of a lower hierarchy,
The progress management device according to any one of claims 1 to 4,
And a management table holding device for holding the upper schedule management information and the low order schedule management information,
Tracking System The progress management device, which performs the upper schedule management information and the progress management by using the lower schedule management information the management table retaining unit retains, characterized in that. A progress management system that performs progress management using upper schedule management information that is schedule management information of an upper hierarchy and lower schedule management information that is schedule management information of a lower hierarchy,
A progress management device according to claim 5;
A management table holding device for holding the upper schedule management information and the low order schedule management information,
A design product management device for holding design products,
The progress management device performs the progress management by using said upper schedule management information and the backward schedule management information the management table storage device holds, and a design artifact the designed product management device holds , A progress management system characterized by that. A progress management method in a progress management device that performs progress management using upper schedule management information that is schedule management information of an upper hierarchy and lower schedule management information that is schedule management information of a lower hierarchy,
Storing the schedule management information for each development hold point generated based on the upper schedule management information and the lower schedule management information as schedule management registration information;
For each development hold point, a plan schedule reflection processing step of updating the plan schedule in the lower schedule management information and the schedule schedule in the schedule management registration information based on the plan schedule included in the higher schedule management information;
For each development hold point, an actual schedule reflecting process step for updating the actual schedule in the upper schedule management information and the actual schedule in the schedule management registration information based on the actual schedule included in the lower schedule management information;
A determination step of performing determination processing as to whether or not product development is performed in an original order in units of development hold points based on the schedule management registration information, and adding a determination result by the determination processing to the higher-level schedule management information When,
The progress management method characterized by including.   A progress management program for causing a computer to execute the progress management method according to claim 8.

Images