JP3926496B2 - Project management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a project management method for managing the progress of a project from design to manufacturing / shipment, and particularly suitable for a case where a plurality of development designers and production managers collaborate to carry out operations. Regarding the method.
[0002]
[Prior art]
In a conventional project management system, an administrator first inputs data representing a hierarchical structure of the processes necessary to carry out a project, and sets a scheduled start date / scheduled date for each process. The project was scheduled, and the actual start date / actual end date was entered to manage the progress.
[0003]
Note that the hierarchical structure of processes is generally called “WBS (work breakdown structure)”, and in this specification, data expressed in WBS is called “WBS data”.
[0004]
Here, how to divide the hierarchy in the WBS depends on the contents of the project. For example, considering the case of WBS data for a factory construction project, the first hierarchy is “Management Building”, “Material Warehouse”, “Machining Factory”, “Assembly Factory”, “Paint Factory”, “Test Inspection” The building is divided into facilities such as “building” and “product warehouse”. The next level is “building construction of management building”, “electric equipment construction”, “air conditioning equipment construction”, “interior construction”, etc. Divide by type.
[0005]
There is basically one type of hierarchy in the WBS for each project, and basically only one WBS data is defined for each project. The WBS data is created in order to cover the processes indispensable for completing the project, and has a tree structure.
[0006]
Projects are generally refined from the upper level process to the lower level process. Therefore, in WBS data, the schedule of each layer (level) process (work item) is changed from the upper level to the lower level. These are often called “large schedules”, “medium schedules”, and “small schedules”. Since the WBS data has a tree structure, one small schedule work item belongs only to one middle schedule work item, and similarly, one middle schedule work item corresponds to one large schedule work item. It belongs to only the item.
[0007]
In the conventional project management system, each work item is displayed as a bar chart from the start point to the end point. At this time, the bar chart of each work item is arranged below the bar chart of the higher-level work item to which the work item belongs so that the tree structure of the WBS data can be understood.
[0008]
For details of the conventional project management method and project management system as described above, for example, “Basic knowledge system of project management (published by Engineering Promotion Association: 1997)” and “Era of project management (written by Masato Shiga: Industrial Published by Investigative Committee: 1993) and “Microsoft Project Official Courseware for Windows 95 (Catapult, Inc .: ASCII Publishing Bureau: 1996)”.
[0009]
By the way, the work items of the small schedule of the project are grouped by the WBS, but there are cases where it is desired to extract the work item group of the specific small schedule and display it by grouping from a different viewpoint.
[0010]
At this time, conventionally, as in the “integrated production project information management system” described in Japanese Patent Application Laid-Open No. 6-44255, attributes from a certain viewpoint are separately assigned to the work items of each small schedule. In addition, a method of extracting a work item group of a specific small schedule using the attribute is adopted. A general project management system has a similar function.
[0011]
[Problems to be solved by the invention]
In recent years, shortening the product development period has become one of the important competitiveness in the manufacturing industry. Accordingly, it is becoming indispensable to view one product development process as one project and manage it appropriately. At that time, persons in charge of a plurality of departments related to one product development process are treated as members of the project.
[0012]
When a person in charge of a plurality of departments, who are project members handled in this way, uses a project management system, there may be a demand for a view according to a different WBS depending on the department to which the person belongs.
[0013]
For example, the overall system design is used to determine the type and number of major parts that make up the product, and the detailed design of each major part is made and manufactured, then assembled, tested, and shipped. Suppose that there is a product development project.
[0014]
In this case, as a person in charge of design, I would like to see how the first level of WBS is “system design”, “basic design”, “detailed design”, “manufacturing”, and “test”. This is a method of division based on the design work flow. In fact, there is generally an examination called a design review between the system design and the basic design, or between the basic design and the detailed design, which plays a role as a milestone in the progress of the project. This kind of division is easy for designers to understand.
[0015]
However, on the other hand, the person in charge of production management wants to be able to individually check whether or not the main parts group can be manufactured properly. In other words, the first level of the WBS is a way of dividing so as to be a main component group (for example, “LSI”, “printed board (PCB)”, “casing (CAB)”) constituting the product. In this way, the bar chart displayed in the project management system is a group of work items related to the same part. It is possible to easily check whether or not the PCB is likely to occur or whether the PCB and the CAB can be synchronized with each other. This makes it possible to quickly take a countermeasure when there is a problem.
[0016]
In recent years, the need for multi-project management for managing a plurality of projects simultaneously has increased. Among these, it is required to associate different WBSs with one project.
[0017]
For example, when “PCB1” developed in a certain “project A” is also used in “project B” in progress, the project manager of “project B” selects a work item group of small schedules related to “PCB1”. I want to check the progress alongside other PCBs developed in my project. This is because if you manage only the work items of your project, you want to follow the WBS based on the design flow, but if you manage it together with work items that are progressing in other projects, I want to see according to the WBS based.
[0018]
However, the conventional project management system can have only one WBS. For such a need, the “integrated production project information management system” described in JP-A-6-44255. As described above, it is only necessary to extract and display a work item group of a specific small schedule, and cannot have different WBSs.
[0019]
That is, for example, after defining the WBS according to the needs of the designer, the attribute indicating which part is the work is assigned to the work item of each small schedule and specified. It was only possible to extract a work item of a small schedule having the part name attribute and selectively display only the bar chart relating to the part. Specifically, only the component “PCB1” can be cut out and displayed.
[0020]
Of course, by displaying such individual cutout results side by side, it is possible to construct a pseudo WBS at first glance. However, in the case of the prior art, the cut out chunks are simply arranged and cannot have a hierarchical structure. That is, it is difficult to define that “PCB” is in the upper layer of “PCB1” and “PCB2”. Therefore, in order to display the entire schedule according to the WBS based on the configuration of the product, it has been necessary to add manpower to the chunks cut out by the conventional technique and edit them. For this reason, once the WBS based on the design flow is defined, it becomes difficult to quickly check, for example, whether the entire PCB and whether the PCB and CAB are synchronized. On the other hand, there is a problem that effective actions are delayed and management of the entire project is not successful.
[0021]
The object of the present invention is to provide a solution to such a problem. That is, an object of the present invention is to make it possible to define and refer to a plurality of types of WBSs as seen from the standpoint of each department, for one project involving persons in charge of many departments.
[0022]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides:
For an arbitrary project, a plurality of types of WBS data, each representing a process of the project in WBS, each of which is expressed in different ways except for the lowest layer,
Manage multiple types of WBS data entered in association with the above project,
A project management method is provided that displays WBS data instructed to be selected from WBS data managed in association with the project.
[0023]
In the project management method provided by the present invention,
Manage progress data on the above project processes,
The managed progress data can be displayed in accordance with the WBS represented by the WBS data selected and instructed from the WBS data managed in association with the project.
[0024]
In the project management method provided by the present invention,
When entering multiple types of WBS data,
For the first WBS data, accept the input up to the process of the lowest layer,
For the second and subsequent WBS data,
Accept the input of the process excluding the process of the lowest layer,
For the process of the lowest layer, the process of the lowest layer in the WBS data already input and managed is diverted.
It is possible to accept the designation of the process of the upper layer to which the process of the lowest layer belongs.
[0025]
If you do this,
At the time of inputting the second and subsequent WBS data, when accepting the designation of the process of the next upper layer to which the process of the lowest layer belongs,
The first table describing the process of accepting input for the second and subsequent WBS data according to the WBS represented by the WBS data, and the WBS data selected and instructed from the WBS data already input and managed And a matrix table in which a second table describing symbols corresponding to the processes of the lowest layer is arranged as a vertical axis and a horizontal axis, in accordance with the WBS represented by the WBS data.
When the symbol is moved from the second table to the matrix table, a layer process corresponding to a layer above the lowest layer in the first table corresponding to the movement destination is performed. Therefore, it can be determined that the process of the lowest layer corresponding to the symbol is designated as the process of the next higher layer to which the process belongs.
[0026]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0027]
FIG. 1 is an overall configuration diagram of a project management system according to an embodiment of the present invention.
[0028]
In the figure, 101 is a WBS registration unit that inputs a plurality of types of WBS data for the same project, 102 is a WBS relationship definition unit that inputs relationships between work items in a plurality of types of WBS data, and 103 is a plurality of types. 104 is a project management function unit having functions equivalent to those of a conventional project management system, and 105 is a schedule information storage unit that stores progress data (schedule information) related to work items. It is.
[0029]
The project management system according to the present embodiment can be realized by a general-purpose information processing apparatus such as a personal computer. That is, the WBS registration unit 101, the WBS relation definition unit 102, the display switching unit 103, and the project management function unit 104 are all realized by a program executed by the CPU of the information processing apparatus, and the schedule information storage unit 105 is configured by the information processing apparatus. Corresponds to the database provided by.
[0030]
Now, as examples of projects, FIGS. 2 and 3 show different WBS data in the same project (“A product development”).
[0031]
In the following description, in the tree structure of FIG. 2 and FIG. 3, among the four levels, in order from the left column, the work item of the second level is “large work item” and the work of the third level. The item is referred to as “medium schedule work item”, and the fourth work item is referred to as “small schedule work item”.
[0032]
The purpose of WBS is to identify all the work items necessary to complete the project. Accordingly, even if different WBSs are provided, the work items identified at the lowest level will match. In the example of FIGS. 2 and 3, the small schedule work items have the same contents although the arrangement order is different.
[0033]
FIG. 2 shows WBS data based on the design process flow.
[0034]
In FIG. 2, the large-scale work item is composed of five work items of “system design”, “basic design”, “detailed design”, “manufacturing”, and “inspection”. Moreover, the medium schedule work item is composed of work items for each type of main part. For example, under “basic design”, there are three types: “LSI basic design”, “PCB basic design”, and “CAB basic design”. The same applies to “detailed design” and “manufacturing”. Since “system design” and “inspection” are before being divided into such parts, and after such parts are assembled, they are unique medium schedule work items.
[0035]
The type of main parts, that is, the small schedule work item under the medium schedule work item for each of “LSI”, “PCB (printed board)”, and “CAB (housing)” is “necessary for one part. Work items equal to "work item x number of parts actually required" are arranged.
[0036]
Since FIG. 2 is a simple example, the number of work items for one component is one, and the number of components is “LSI” and “PCB” are two each, and “CAB” is one. It has become.
[0037]
FIG. 3 shows WBS data based on the product configuration.
[0038]
In FIG. 3, the large-scale work item is composed of five work items “system design”, “LSI”, “PCB”, “CAB”, and “inspection”. Here, “system design” and “inspection” are the same as those in FIG. 2 because they are before being divided into such parts and after such parts are assembled. Other medium schedule work items consist of individual parts of each major part type. For example, below “PCB” are two, “PCB1” and “PCB2”. In the small schedule, work items necessary for designing and manufacturing each part are arranged.
[0039]
FIG. 4 is a process flowchart of the WBS registration unit 101.
[0040]
The WBS registration unit 101 performs the process shown in FIG. 4 in order to input a plurality of types of WBS data for the same project.
[0041]
That is, as shown in FIG. 4, the WBS registration unit 101 first receives an input of the name of the WBS data (step 401).
[0042]
Subsequently, if there is the first WBS data for the same project (step 402), the WBS registration unit 101 accepts input up to the work item at the lowest level (step 403).
[0043]
For example, if the WBS data shown in FIG. 2 is the WBS data input first, in this case, the input of a large schedule work item, a medium schedule work item, and a small schedule work item is accepted. This input order is not specified. For example, after entering all large schedule work items, enter the middle schedule work items belonging to each large schedule work item, and then enter the small schedule work items, or enter one large schedule work item. There is also an order in which all medium schedule work items and small schedule work items belonging thereto are input, and then the next large schedule work item is input. There is also an order in which all work items are input at random.
[0044]
For each work item, if the “work item ID”, the “hierarchy level” of the work item in the WBS, and the “higher level work item ID” to which the work item belongs are defined, the input order It can be defined regardless of
[0045]
This is held for work items other than the lowest level by filling items 1301 to 1306 in the data shown in FIG. The item 1304 stores the value (WBS data name) input in step 401 of FIG. Further, the work item at the lowest level is held by filling the items 1401 to 1406 in the data shown in FIG.
[0046]
Here, the data shown in FIG. 13 and the data shown in FIG. 14 are data existing in the schedule information storage unit 5 and are data corresponding to an aggregate of WBS data as well as progress data. That is, data items 1307 to 1310 in the data shown in FIG. 13 are progress data, and data items 1410 to 1413 in the data shown in FIG. 14 are progress data.
[0047]
Returning to FIG. 4, if it is the second and subsequent WBS data for the same project (step 402), the WBS registration unit 101 accepts input of work items excluding the work item at the lowest level (step 404).
[0048]
For example, assuming that the WBS data shown in FIG. 3 is the second input WBS data, in this case, input of a large schedule work item and a medium schedule work item is accepted. As described above, this input order is not particularly specified.
[0049]
As described above, this is held by filling items 1301 to 1306 in the data shown in FIG.
[0050]
After the above processing is performed for the desired number of types of WBS data (step 405), the processing is terminated.
[0051]
When the process of the WBS registration unit 101 shown in FIG. 4 is completed, a large schedule work item, a medium schedule work item, and a small schedule work item are input for the first WBS data (the WBS data shown in FIG. 2). With respect to the second and subsequent WBS data (the WBS data shown in FIG. 3), the large schedule work item and the medium schedule work item are input.
[0052]
As described above, work items (small schedule work items) that are identified at the lowest level should match even if they are WBS data of different divisions. Therefore, in this embodiment, the second and subsequent WBSs are used. As for the data, the small schedule work item is diverted from the already entered WBS data, and there is a risk that the small schedule work item will not match due to an input error. Can be avoided.
[0053]
However, at this time, it is necessary to perform processing for defining which medium schedule work item each diverted work item to be used belongs to, and the WBS relation definition unit 102 performs this processing.
[0054]
FIG. 5 is a processing flowchart of the WBS relation definition unit 102.
[0055]
As shown in FIG. 5, the WBS relationship definition unit 102 first accepts designation of WBS data in which up to the lowest level work items are defined (step 501). Hereinafter, this is referred to as “WBS data 1”.
[0056]
Subsequently, the WBS relationship definition unit 102 accepts designation of WBS data in which work items are defined only up to a level one level higher than the lowest level (step 502). Hereinafter, this will be temporarily referred to as “WBS data 2”.
[0057]
For example, it is assumed that the WBS data shown in FIG. 2 is the WBS data 1, and the WBS data corresponding to the large schedule work item and the medium schedule work item in the WBS data shown in FIG.
[0058]
FIG. 7 shows an example of the screen displayed at step 501 and step 502 at this time.
[0059]
In step 501, the user presses a pull-down button 703 in the area 702 for designating WBS data to be WBS data 1 on the screen shown in FIG. A list of the WBS data being displayed is displayed in a pull-down manner, and the name of the desired WBS data (“WBS-B”) 704 is selected from the list, thereby setting the selected “WBS-B” 704 in the area 702. be able to.
[0060]
Similarly, in step 502, the user presses a pull-down button 706 in the area 705 for designating WBS data to be WBS data 2 on the screen shown in FIG. A list of WBS data in which work items are defined only up to the level of is displayed in a pull-down manner, and the name of the desired WBS data (“WBS-F”) 707 is selected and instructed, thereby selecting “WBS- F ”707 can be set in the area 705.
[0061]
Returning to FIG. 5, the WBS relationship definition unit 102 accepts designation of a work item that is not positioned in the WBS represented by the WBS data 2 among the work items at the lowest level in the WBS data 1 (step 503). Here, “position in the WBS” means that when the work item at the lowest level in the WBS data 1 is diverted to the WBS data 2, the work at the level one level higher to which the work item at the lowest level belongs. This corresponds to the item being designated from among the work items in the WBS data 2.
[0062]
Subsequently, the WBS relationship definition unit 102 performs the above specification (specification of the work item in the WBS data 2) in order to position the work item at the lowest level received in step 503 in the WBS represented by the WBS data 2. Accept (step 504).
[0063]
Steps 503 and 504 are performed for all work items at the lowest level in the WBS data 1 (step 505).
[0064]
For example, if the WBS data shown in FIG. 2 is the WBS data 1, and the WBS data corresponding to the large schedule work item and the medium schedule work item in the WBS data shown in FIG. In this case, the designation of the medium schedule work item in the WBS data 2 is accepted for each small schedule work item in the WBS data 1.
[0065]
The above processing is performed for the number of types of WBS data in which work items are defined only up to the level one level higher than the lowest level (step 506), and then the process ends.
[0066]
By the processing of step 503 to step 506, items 1407 to 1409 in the data shown in FIG. 14 are filled.
[0067]
An example of the screen displayed in steps 503 to 506 is shown in FIG.
[0068]
In the screen shown in FIG. 8, work items of WBS data 1 are arranged in area 802, and work items of WBS data 2 excluding the lowest level are arranged in area 803. In the area 804, black bars are displayed in association with the work items at the lowest level in the WBS data 1.
[0069]
The area 802, the area 803, and the area 804 form a matrix table.
[0070]
The user can position the work item at the lowest level corresponding to the bar in the WBS represented by the WBS data 2 by dragging the black bar to the right and moving it to a desired position.
[0071]
For example, in FIG. 8, when the user moves the work item “PCB1 specification” in the WBS data 1 to the area 805, the work item “PCB1 specification” is “PCB1” in the WBS data 2. It will be positioned in the lower order. The operation of “sliding the bar” has been described, but an operation of simply “clicking” the area 805 is also possible.
[0072]
Another example of the screen displayed in steps 503 to 506 is shown in FIG.
[0073]
In the screen shown in FIG. 9, work items of WBS data 1 are arranged in area 902, and an area 903 is provided with a level column excluding the lowest level in the WBS represented by WBS data 2.
[0074]
For example, in the screen shown in FIG. 9, the user selects the pull-down button 905 in the column 904 corresponding to the work item “PCB1 specification” in the WBS data 1 in the large-scale work item column in the WBS data 2. By pressing, a list of large-scale work items is displayed in a pull-down manner, and a desired work item name (“PCB”) 906 is selected from the list, and the designated “PCB” 906 is set in the column 904. To do. Further, for example, in the screen shown in FIG. 9, the user can select a pull-down button in the column 907 corresponding to the work item “PCB1 specification” in the WBS1 data in the medium schedule work item column in the WBS1 data. By pressing 908, a list of medium schedule work items is displayed in a pull-down manner, and a desired work item name (“PCB 1”) 909 is selected from the list to display “PCB 1” 909 instructed in the column 907. Set.
[0075]
In this way, the user can easily position the work item at the lowest level in the WBS data 1 in the WBS represented by the WBS data 2.
[0076]
Note that the designation of the WBS data 1 is accepted in step 501 of FIG. 5, but in particular, even if the designation of the WBS data 1 is not accepted, the lowest level of any WBS data for the target project. By simply presenting a list of work items (small schedule work items) to the user, the user can position them in the WBS represented by the WBS data 2.
[0077]
In the example of the screen shown in FIG. 9, the user also designates a large schedule work item. However, if a medium schedule work item is determined, the large schedule work item is always set to one. It is possible to specify only the schedule work item.
[0078]
FIG. 6 is a processing flowchart of the display switching unit 103.
[0079]
As shown in FIG. 6, the display switching unit 103 first receives designation of WBS data to be displayed (step 601). This can be realized, for example, with a screen as shown in FIG.
[0080]
Subsequently, the display switching unit 103 rearranges the work items according to the WBS represented by the designated WBS data (step 602).
[0081]
In step 602, specifically, the display switching unit 103 extracts a work item corresponding to the name of the designated WBS data from the data shown in FIG. 13 and the data shown in FIG. 14, and the data shown in FIG. This can be realized by copying to a separate table having the same configuration as in FIG. This separate table is the same as the data holding method of the project management system having only one conventional WBS.
[0082]
Accordingly, various functions serviced by the conventional project management system can be used (step 603).
[0083]
Various functions provided by the conventional project management system are provided by the project management function unit 104 that manages progress data. The specific contents are, for example, “Microsoft Project Official Courseware for Windows 95 (Catapult, Inc.) Author: Ascii Press Publishing: 1996) ”is omitted here.
[0084]
When receiving designation of another WBS data (step 604), the process returns to step 601.
[0085]
Now, one of the functions provided by the project management function unit 104 is a “bar chart editing function”. When the WBS data shown in FIG. 2 is specified, an example of a screen displayed by this function is as follows: As shown in FIG.
[0086]
As shown in FIG. 11, from the viewpoint according to the WBS data shown in FIG. 2, it becomes easy to roughly grasp the design flow of the entire project.
[0087]
On the other hand, FIG. 12 shows an example of a screen displayed by the bar chart editing function when the WBS data shown in FIG. 3 is designated.
[0088]
As shown in FIG. 12, according to the view according to the WBS data shown in FIG. 3, what is the schedule of individual parts, for example, “PCB1”, and how is the synchronization between these individual parts, It becomes easy to grasp that.
[0089]
As described above, according to the present embodiment, it is possible to define and refer to a plurality of types of WBSs as seen from the standpoint of each department, for one project involving persons in charge of many departments. From the standpoint of each department, it is possible to easily grasp the problems of the project and take effective actions promptly. Therefore, the action of each department is promoted, and overall project management such as project schedule management, cost management, and quality management can be performed more effectively.
[0090]
In this embodiment, the processing of the WBS registration unit 101 shown in FIG. 4 and the processing of the WBS relation definition unit 102 shown in FIG. 5 are often performed continuously. There is no particularly strong context with the processing of the switching display unit 103 shown.
[0091]
For example, when only one WBS data is initially input as in the prior art, only one WBS data is input by the processing of the WBS registration unit 101 shown in FIG. 4, and no other WBS data can be specified. Therefore, the processing of the WBS relation definition unit 102 shown in FIG. 5 is not performed, and the processing of the switching display unit 103 shown in FIG. 6 only displays the existing WBS data. This is the same flow as a conventional project management system.
[0092]
Thereafter, when it is desired to input new WBS data, the processing of the WBS registration unit 101 shown in FIG. 4 and the processing of the WBS relation definition unit 102 shown in FIG. 5 are performed. When these processes are completed, in order to input another WBS data, these processes may be performed again or may be shifted to the process of the switching display unit 103 shown in FIG.
[0093]
Further, in the present embodiment, the processing of the WBS registration unit 101 shown in FIG. 4 and the processing of the WBS relation definition unit 102 shown in FIG. 5 are separate processings, but these processings are combined. You may do it.
[0094]
Hereinafter, an embodiment in this case will be briefly described with reference to FIGS.
[0095]
FIG. 15 is an overall configuration diagram of the project management system when the processing of the WBS registration unit 101 shown in FIG. 4 and the processing of the WBS relation definition unit 102 shown in FIG. 5 are merged.
[0096]
In the figure, reference numeral 1501 denotes a WBS registration / relationship definition unit, which is a combination of the WBS definition unit 101 and the WBS relationship definition unit 102 in FIG.
[0097]
Since other components are the same as those in FIG. 1, only the WBS registration / relationship definition unit 1501 will be described here.
[0098]
FIG. 16 is a process flowchart of the WBS registration / relationship definition unit 1501.
[0099]
As shown in FIG. 16, the WBS registration / relationship definition unit 1501 first receives an input of the name of the WBS data (step 1601). Hereinafter, this is referred to as “WBS data 1”.
[0100]
Subsequently, if the WBS data 1 is the first WBS data for the same project (step 1602), the WBS registration / relationship definition unit 1501 accepts input up to the lowest level work item (step 1603).
[0101]
In addition, if the WBS data 1 is the second and subsequent WBS data for the same project (step 1602), the WBS registration / relationship definition unit 1501 determines the WBS data up to the lowest level work item. The designation is accepted (step 1604). Hereinafter, this will be temporarily referred to as “WBS data 2”.
[0102]
Step 1604 can be realized, for example, by a screen including only the areas 702 to 704 in the screen shown in FIG.
[0103]
Subsequently, the WBS registration / relationship definition unit 1501 accepts input up to the work item at the lowest level for the WBS data 1 (step 1605).
[0104]
However, in step 1605, the user newly inputs all work items at levels other than the lowest level while defining the WBS, and the work item at the lowest level is the lowest level work item in the WBS data 2. Specify from the item.
[0105]
Step 1605 can be realized, for example, on a screen as shown in FIG.
[0106]
In the screen shown in FIG. 17, an area 1702 is an area for inputting work items at levels other than the lowest level of the WBS data 1. The user can simultaneously define WBS by inputting work items in area 1702. In the area 1703, a column for inputting a work item at the lowest level of the WBS data 1 is provided.
[0107]
For example, in the screen shown in FIG. 17, when the user wants to register a small-schedule work item following the middle-schedule work item “PCB1” in the WBS data 1, a column corresponding to “PCB1” provided in the area 1703 When a pull-down button 1705 is pressed in 1704, a list of large-scale work items in the WBS data 2 is displayed in a pull-down manner, and a desired work item name (“basic design”) 1706 is selected and instructed. The pull-down list of intermediate schedule work items at the lower level of the designated “basic design” 1706 is displayed, and the desired work item name (“PCB specification creation”) 1707 is selected and designated. Then, a list of small-scale work items at the lower level of the “PCB specification creation” 1707 that has been instructed to be selected is displayed in a pull-down list, and a desired work is selected from the list. Item name ( "PCB1 specification creation") 1708 the selection instruction to things, to set the selected instruction "PCB1 specification creation" 1708 in the column 1704.
[0108]
In this way, the user can easily locate the lowest level work item in the WBS data 2 in the WBS represented by the WBS data 1.
[0109]
【The invention's effect】
As described above, according to the present invention, it is possible to define and refer to a plurality of types of WBSs as seen from the standpoint of each department for one project involving persons in charge of many departments. From the standpoint of the department, it becomes possible to easily grasp the problems of the project and take effective actions promptly. Therefore, the action of each department is promoted, and overall project management such as project schedule management, cost management, and quality management can be performed more effectively.
[Brief description of the drawings]
FIG. 1 is an overall configuration diagram of a project management system according to an embodiment of the present invention.
FIG. 2 is an explanatory diagram showing an example of WBS data based on a design process flow;
FIG. 3 is an explanatory diagram showing an example of WBS data based on a product configuration.
FIG. 4 is a process flowchart of a WBS registration unit.
FIG. 5 is a process flowchart of a WBS relation definition unit.
FIG. 6 is a processing flowchart of a display switching unit.
FIG. 7 is an explanatory diagram showing an example of a screen for accepting designation of WBS data in the processing by the WBS relation definition unit.
FIG. 8 is an explanatory diagram showing an example of a screen for diverting the work item at the lowest level in the processing by the WBS relation definition unit.
FIG. 9 is an explanatory diagram showing another example of a screen for diverting the work item at the lowest level in the processing by the WBS relation definition unit.
FIG. 10 is an explanatory diagram showing an example of a screen for accepting designation of WBS data in the processing by the display switching unit.
FIG. 11 is an explanatory diagram showing an example of a screen displayed by a bar chart editing function provided by a project management function unit.
FIG. 12 is an explanatory diagram showing an example of a screen displayed by a bar chart editing function provided by a project management function unit.
FIG. 13 is an explanatory diagram showing an example of progress data regarding work items at levels other than the lowest level in WBS data.
FIG. 14 is an explanatory diagram showing an example of progress data relating to a work item at the lowest level in WBS data.
FIG. 15 is an overall configuration diagram of a project management system in which a WBS registration unit and a WBS relation definition unit are merged.
FIG. 16 is a processing flowchart of a WBS registration / WBS relationship definition unit.
FIG. 17 is an explanatory diagram showing an example of a screen for inputting a work item at a level excluding the lowest level and diverting the work item at the lowest level in the process by the WBS registration / relationship definition unit.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 101 ... WBS registration part, 102 ... WBS relation definition part, 103 ... Display switching part, 104 ... Project management function part, 105 ... Schedule information storage part, 1501 ... WBS registration / relationship definition part.

Claims (1)

A project management system for managing project processes,
Storage means for storing first process management data representing work items using a hierarchical structure, and at least one second process management data representing work items using a hierarchical structure;
First accepting means for accepting work items of all layers of the first process management data and storing the work items in the storage unit;
Second receiving means for receiving work items other than the lowest layer of the at least one second process management data, and storing the work items in the storage unit;
The first process management data and the at least one second process management data are read from the storage unit, the work item of the lowest layer of the first process management data, and the at least one second process management data An association means for associating a work item one level higher than each lowest layer;
Display means for receiving an instruction to select any one of the first process management data and the at least one second process management data, and displaying the instructed process management data;
Have
Each of the first process management data and the at least one second process management data includes progress data relating to the work item,
The display means receives an instruction to select one of the first process management data and the at least one second process management data, and displays the process management data including the instructed progress data. Display
The associating means includes one symbol from the lowest layer of the symbol associated with each work item of the lowest layer of the first process management data and any one of the second process management data selected. Displaying a matrix table with a work item in a higher hierarchy as a vertical axis or a horizontal axis, accepting the movement of each of the symbols, and based on the moved position of each of the symbols, the first process management data A project management system characterized by associating a work item in the lowest layer with a work item in a hierarchy one level higher than the lowest layer in the second process management data .

Images