JP2017102694A - Gantt chart generation program, gantt chart generation apparatus and gantt charge generation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quickly perform reconsideration of an own project by using a Gantt chart when a project related to the own project is changed.SOLUTION: A Gantt chart generation apparatus 1 for generating a Gantt chart includes: a project generation section 11 for generating a plurality of projects so as to be displayed on multiple stages in a display device; an object generation section 13 for generating one or more objects in one project; and a shadow generation section 15 which when the project generation section 11 generates a first project and a second project different from the first project, the first project is managed by a first project manager and the second project is managed by a second project manager different from the first project manager, generates shadow to be a copy of an object in the first project, in the second project.SELECTED DRAWING: Figure 1

Description

  The present invention relates to Gantt chart technology.

  In Patent Document 1, “a production plan support system for supporting production planning, the system includes a plurality of terminals and a storage device, and the storage device includes data relating to a production plan, The data of the contact terminals of the parties related to the production plan are stored, and based on the contents of the new production plan input from the terminal, the system selects the parties to be contacted, and the new The terminal of the selected related party is notified of the contents of the production plan, and the terminal that has received the contents of the new production plan transmits a reply to the transmission destination by making an input related to the reception. "Production planning support system". That is, when there is a change in the production plan, the changer notifies the change content to the terminals of the parties involved in the change.

Japanese Patent No. 4116981 (Claim 1)

  However, according to Patent Document 1, in order for the parties concerned to know the change contents, it is necessary for the change person to be notified of the change contents. There was a problem that the judgment of the necessity of reviewing one's own plan was delayed.

  In view of such circumstances, an object of the present invention is to enable an early review of an own project with respect to a project change related to the own project using a Gantt chart.

In order to achieve the above object, the present invention provides:
A computer as a Gantt chart generation device for generating a Gantt chart,
Project generation means for generating a plurality of projects so that they can be displayed in multiple stages on a display device,
Object generation means for generating one or more objects in one project;
The project generation means generates a first project and a second project different from the first project, the first project manager manages the first project, and the second project is the first project. When a second project manager different from the one project manager manages
A shadow generating means for generating a shadow in the second project that is a copy of the object in the first project;
It is a Gantt chart generation program for functioning as
Other means will be described later.

  According to the present invention, it is possible to use a Gantt chart to review an own project at an early stage with respect to a project change related to the own project.

It is a block diagram of the Gantt chart production | generation apparatus of this embodiment. It is a data structure figure of a project table. It is a data structure figure of a member table. It is a data structure figure of a task table. It is a data structure figure of an activity table. It is a data structure figure of a milestone table. It is a data structure figure of a related line table. It is a data structure figure of a shadow table. It is a data structure figure of a track record table. It is a flowchart which shows the process regarding the multistage display of a Gantt chart. It is a screen display example of the Gantt chart displayed in multiple stages. It is a flowchart which shows the production | generation process of a shadow. It is an example of a screen display of a generated shadow and a related line that associates a shadow with an activity. It is a screen display example for demonstrating the reference of the document in a shadow. It is a flowchart which shows the edit process of a shadow when an original object changes. It is a screen display example for demonstrating the change of the shadow accompanying the change of an original object. It is a data structure figure of a document table.

  Next, modes for carrying out the present invention (hereinafter referred to as “embodiments”) will be described with reference to the drawings as appropriate.

≪Configuration≫
The Gantt chart generation device 1 (FIG. 1) of the present embodiment is a computer including hardware such as a control unit 10, a communication unit 20, and a storage unit 30, and specifically, is a server. The control unit 10 includes, for example, a CPU (Central Processing Unit) and a dedicated circuit. The communication unit 20 includes a communication interface that transmits and receives information via a communication line, and is connected to the processing unit via an internal bus or the like. The storage unit 30 includes, for example, a storage medium such as a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), and a flash (registered trademark) memory. When the control unit 10 includes a CPU, information processing by a computer including the control unit 10 is realized by a program execution process by the CPU. The storage unit 30 included in the computer stores a program (including a Gantt chart generation / management program) that is instructed by the CPU and implements the function of the computer. This realizes cooperation between software and hardware. The present embodiment can be realized by a program for executing the information processing, and the program can be provided by being stored in a computer-readable recording medium (eg, CD-ROM). The program can also be provided through a network such as the Internet.

A display device D shown in FIG. 1 is a computer used by a user who uses a Gantt chart, for example, a thin client. The display device D includes hardware such as an input unit, a display unit, a storage unit, and a control unit (not shown). The display device D includes a display control unit 40 that controls screen display of the Gantt chart.
The “user” in the present embodiment is a user who uses the Gantt chart as described above, and is synonymous with a member of a project handled in the Gantt chart. In addition, the user is a “project manager” who manages the project he / she is in charge of (eg, a boss, who mainly adjusts the schedule, and may actually perform work) and the project manager under the project manager. It can be classified as a “non-project manager” (eg, subordinate, who mainly performs actual work) who works on business.

  The control unit 10 of the Gantt chart generation device 1 includes a project generation unit 11, a task generation unit 12, an object generation unit 13, a relation line generation unit 14, a shadow generation unit 15, a document registration unit 16, and a document reference. Unit 17 and a result setting unit 18.

  The project generation unit 11 generates a Gantt chart project in response to a project generation request from the display device D. The project generation unit 11 generates a project so that a plurality of projects can be displayed in multiple stages on the screen of the display device D. The project generation request is executed by operating the input unit of the display device D. The display control unit 40 of the display device D has, for example, a mode in which a Gantt chart of a project of its own project manager and a Gantt chart of another project manager's project are on the same screen and a calendar (schedule) is shared. Can be displayed.

  The task generation unit 12 generates a Gantt chart task in response to a task generation request from the display device D. The task generation unit 12 generates a task subordinate to the project in the project designated by the display device D. The task generation request includes the ID (Identifier) of the project on which the task is subordinate, and is executed by operating the input unit of the display device D. The task generation unit 12 can convert (upgrade) a specified task into a project in response to a request from the display device D.

The object generation unit 13 generates a Gantt chart object in response to an object generation request from the display device D. In the present embodiment, the objects are classified into activities and milestones, but are not limited thereto. The object generation request includes the ID of the project including the object, and is executed by operating the input unit of the display device D. The object generation unit 13 generates an object subordinate to the project and the task in the project and task specified by the display device D. The object generation unit 13 can generate one or a plurality of objects in one project and one task.
Note that projects and tasks can be equated in that they can include one or more objects. Therefore, in this respect, the explanation about the project also applies to the task. Therefore, in the present embodiment, only the project will be described, and the description of the task may be omitted for convenience.

  The related line generation unit 14 generates a related line of the Gantt chart in response to a related line generation request from the display device D. The related line generation unit 14 generates a related line that is specified by the display device D and associates the two objects in the same project. The related line generation request includes the IDs of the two objects associated with the related line and the IDs of the projects to which these two objects belong, and is executed by operating the input unit of the display device D.

The shadow generation unit 15 generates a Gantt chart shadow in response to a shadow generation request from the display device D. A shadow is a project managed by another project manager (first project manager) that can be placed in a project (second project) managed by its own project manager (second project manager). It is a copy of the object of (first project). The shadow generation request includes an ID of an object to be a copy source (sometimes referred to as an original), and is executed by an operation of the input unit of the display device D.
Note that the related line generation unit 14 can generate a related line that associates a shadow with an object (or another shadow).

  In response to a document registration request from the display device D, the document registration unit 16 registers a document associated with the Gantt chart object. The document is, for example, a document file and is created by a known document creation application installed in the display device D. The document registration request includes an ID of an object to be associated with a document, and is executed by an operation of the input unit of the display device D.

  When the document registered by the document registration unit 16 is registered in the object in the project of another project manager, the document reference unit 17 creates a shadow (other project management) generated by the shadow generation unit 15. Can be referred to in the shadow of the object in the user's project.

The result setting unit 18 sets the result of the object generated by the object generation unit 13 in response to the result setting request from the display device D. The actual result of an object is a degree of achievement of a plan defined by the object, and can be represented by, for example, a work progress rate. The method of calculating the progress rate is well known and varies depending on the specific form of the object, and detailed description thereof is omitted. For example, when an object for producing 1000 articles in one week is generated, when 760 articles have been produced so far, the progress rate can be 76%. The result setting request includes the ID of the object for which the progress rate is to be set, and is executed by operating the input unit of the display device D.
When the record setting unit 18 has set a record for the original shadow generated by the shadow generation unit 15, the record setting unit 18 can set the same record for the shadow.

  The storage unit 30 of the Gantt chart generation device 1 includes a project table 31, a member table 32, a task table 33, an activity table 34, a milestone table 35, a related line table 36, a shadow table 37, and an actual result table. 38 and a document table 39.

(Project table 31)
The project table 31 stores and manages the project generated by the project generation unit 11. As shown in FIG. 2, the project table 31 has items such as “ID”, “name”, “project start date”, and “project end date”, and a record is created for each project.

The “ID” item stores a project identifier. In FIG. 2, an underline applied to an item indicates that the item is a primary key. The same applies to the other drawings.
The name of the project (for example, input designation from the input unit of the display device D) is registered in the “name” item.
The item “project start date” stores the project start date, that is, the date on which the left end of the project depicted in the Gantt chart is located.
The item “project end date” stores the project end date, that is, the date on which the right end portion of the project depicted in the Gantt chart is located.

(Member table 32)
The member table 32 stores and manages users (members) who use the Gantt chart generated by the Gantt chart generating apparatus 1. As shown in FIG. 3, the member table 32 has items such as “user name”, “project ID”, and “role”, and a record is created for each user.

In the “user name” item, the name of the user who uses the Gantt chart is stored.
In the “project ID” item, an identifier of a project handled by the target user is stored, and corresponds to “ID” of the project table 31. Note that the user associated with the project ID is a member in charge of the project identified by the project ID.
The “role” item stores a value indicating the authority of the target user for the corresponding project. For example, “project manager” stored in the “role” item means that the target user can create, edit, and refer to the corresponding project. In addition, “reference” stored in the “role” item means that the target user can refer to the corresponding project, but cannot create or edit (ie, corresponds to a non-project administrator). .

(Task table 33)
The task table 33 stores and manages tasks generated by the task generation unit 12. As shown in FIG. 4, the task table 33 has items such as “ID”, “name”, “task start date”, “task end date”, and “subordinate task ID”, and a record is created for each task. Is done.

In the item “ID”, an identifier of a task is stored.
The name of the task (for example, input designation from the input unit of the display device D) is registered in the “name” item.
The item “task start date” stores the start date of the task, that is, the date on which the left end portion of the task depicted in the Gantt chart is located.
The “task end date” item stores the task end date, that is, the date on which the right end portion of the task depicted in the Gantt chart is located.
The item of “subordinate source task ID” stores the identifier of the task or project to which the target task belongs directly. The projects and tasks generated in the Gantt chart have a tree structure with the project as the root.

(Activity table 34)
The activity table 34 stores and manages activities generated by the object generation unit 13. As shown in FIG. 5, the activity table 34 has items such as “ID”, “project ID”, “name”, “start date”, “end date”, and “document”, and a record is created for each activity. Is done.

In the item “ID”, an identifier of an activity is stored.
The item “project ID” stores the identifier of the project to which the target activity belongs, and corresponds to “ID” in the project table 31.
In the “name” item, the name of the activity (for example, input designation from the input unit of the display device D) is registered.
The item “start date” stores the start date of the activity, that is, the date on which the left end of the activity depicted in the Gantt chart is located.
The “end date” item stores the end date of the activity, that is, the date on which the right end portion of the activity depicted in the Gantt chart is located.
The “document” item stores the file name of the document registered by the document registration unit 16 for the target activity.
The activity table 34 may include an item including an ID of a task to which the target activity belongs.

(Milestone table 35)
The milestone table 35 stores and manages milestones generated by the object generator 13. As shown in FIG. 6, the milestone table 35 has items such as “ID”, “project ID”, “name”, “planned date”, and “document”, and a record is created for each milestone.

In the item “ID”, an identifier of a milestone is stored.
In the “project ID” item, an identifier of a project to which the target milestone belongs is stored, and corresponds to “ID” of the project table 31.
In the “name” item, a milestone name (for example, input designation from the input unit of the display device D) is registered.
The “scheduled date” item stores a scheduled date of the milestone, that is, a date on which the milestone depicted in the Gantt chart is located.
In the “document” item, the file name of the document registered by the document registration unit 16 for the target milestone is stored.
The milestone table 35 may include an item including an ID of a task to which the target milestone belongs.

(Related line table 36)
The related line table 36 stores and manages the related lines generated by the related line generation unit 14. As shown in FIG. 7, the related line table 36 has items such as “ID”, “project ID”, “preceding object ID”, and “subsequent object ID”, and a record is created for each related line.

In the item “ID”, an identifier of a related line is stored.
The item “project ID” stores the identifier of the project in which the target related line is arranged, and corresponds to “ID” in the project table 31. The related line table 36 does not have to include the item “project ID”.
The item “preceding object ID” is an identifier of one of the two objects associated with the target relation line. At this time, if the object is an activity, the related line is related to the right end (end date) of this activity, and if the object is a milestone, the related line is connected to the milestone itself (planned date). Associated.
The item “subsequent object ID” is an identifier of one of the two objects associated with the target relation line. At this time, if the object is an activity, the relation line is associated with the left end (start date) of this activity, and if the object is a milestone, the relation line is the milestone itself (planned date). Associated.

As shown in FIG. 7, the relation line identified by “Relation Line 002” is the original activity identified by “Activity 002”, the shadow of the activity identified by “Shadow 001” (see FIG. 8), and Can be associated. That is, the relation line can associate the original and the shadow.
The relation line identified by “Relation Line 003” is the shadow of the activity identified by “Shadow 001” (see FIG. 8) and the shadow of the milestone identified by “Shadow 002” (see FIG. 8). Can be associated with each other. That is, the relation line can associate shadows with each other.

(Shadow table 37)
The shadow table 37 stores and manages the shadow generated by the shadow generation unit 15. As shown in FIG. 8, the shadow table 37 has items such as “ID”, “project ID”, “original object ID”, and “original ID”, and a record is created for each shadow.

The “ID” item stores a shadow identifier.
The “project ID” item stores the identifier of the project to which the target shadow belongs, and corresponds to “ID” in the project table 31.
The item “original object ID” stores the identifier of the project to which the object that is the copy source of the target shadow belongs.
In the “original ID” item, an identifier of an object that is a copy source of the target shadow is stored.

(Result table 38)
The result table 38 stores and manages the results set by the result setting unit 18. As shown in FIG. 9, the performance table 38 has items such as “object ID”, “project ID”, and “progress rate”, and a record is created for each object.

In the item “object ID”, an identifier of an object in which a progress rate as a result is set is stored.
In the item “project ID”, an identifier of a project to which an object for which a progress rate as a result is set belongs is stored. Note that the result table 38 may not have this “project ID” item.
In the item “progress rate”, the value of the progress rate set for the target object is stored. When the object is a milestone, the progress rate takes only two values of 0 (not achieved) or 100 (achieved).

(Document table 39)
The document table 39 stores and manages documents registered by the document registration unit 16. As shown in FIG. 17, the document table 39 has items such as “ID”, “file name”, “project ID”, and “object ID”, and a record is created for each document.

In the item “ID”, an identifier of a document is stored.
In the “file name” item, the file name of the document registered by the document registration unit 16 is stored.
In the “project ID” item, an identifier of a project associated with the target document is stored, and corresponds to “ID” in the project table 31.
The item “object ID” stores an identifier of an object to which the target document is linked.

<< Process >>
With reference to FIG. 10, the process regarding the multistage display of the Gantt chart by the control part 10 of the Gantt chart production | generation apparatus 1 of this embodiment is demonstrated. The process of FIG. 10 is started when an operation for displaying a Gantt chart is performed on the display device D, and the process proceeds to step S1.

  In step S <b> 1, the control unit 10 receives a Gantt chart display request from the display device D. The Gantt chart display request includes project IDs of a plurality of projects that are targets of multistage display. After step S1, the process proceeds to step S2.

In step S2, the control unit 10 acquires the task, activity, milestone, relation line, progress rate, and shadow of the target project identified by the project ID included in the Gantt chart display request. Specifically, the control unit 10 extracts a record of the target project from the project table 31. Further, records of all tasks included in the target project are extracted from the task table 33. Further, records of all activities included in the target project (and tasks included in the project) are extracted from the activity table 34. Further, records of all milestones included in the target project (and tasks included in the project) are extracted from the milestone table 35. Also, records of all related lines included in (belonging to) the target project are extracted from the related line table 36. Further, records of all the achievements (progress rates) set for the objects included in the target project are extracted from the achievement table 38. Further, all shadow records included in the target project are extracted from the shadow table 37.
Note that the shadow acquired by the control unit 10 in step S2 is a shadow generated by the shadow generation process (step S14) in FIG.
After step S2, the process proceeds to step S3.

In step S3, the control unit 10 generates a Gantt chart for the project specified by the Gantt chart display request. Specifically, the control part 10 produces | generates the image information of a Gantt chart using the various records extracted at step S2. When there are a plurality of projects specified in the Gantt chart display request, the control unit 10 generates a Gantt chart for each target project as image information in a multistage display mode with a common calendar.
After step S3, the process proceeds to step S4.

In step S <b> 4, the control unit 10 transmits the generated Gantt chart (plurality) of multistage display mode image information to the display device D via the communication unit 20. The display control unit 40 of the display device D displays the Gantt chart on the screen using the image information received from the control unit 10 of the Gantt chart generation device 1.
After step S4, the process of FIG.

  FIG. 11 shows a screen display example of a Gantt chart displayed in multiple stages on the display device D. In this screen display example, the Gantt chart of the project that the project manager is in charge of (new communication management system development) is displayed in the lower row, and related to the project that the project manager is in charge of (belonging to other departments) Projects that other project managers are responsible for (new communication management system surveys. For example, projects created by other project managers for displaying Gantt charts, and their own project managers are also members of this project. .) Gantt chart is displayed at the top.

In both Gantt charts, the root project and the tasks subordinate to the project are arranged on the vertical axis so that the hierarchical structure is clearly shown. A calendar common to both Gantt charts is arranged on the horizontal axis. The images of activities, milestones, documents, and related lines are as shown in FIG. For activities and milestones, progress is indicated by a shaded dot display. When the progress rate has changed, the latest state of the progress rate can be displayed by operating a reload button (not shown) on the screen.
In addition, although the shadow of the object of another project manager is not generated in the Gantt chart of the own project in FIG. 11, if the shadow is already generated, the corresponding shadow is displayed in the own project. .

  As shown in FIG. 11, by displaying the Gantt chart of its own project manager and the Gantt chart of other project managers in multiple stages, the objects of the own project manager and the objects of other project managers are displayed. The temporal context can be clarified.

  Next, a shadow generation process performed by the control unit 10 of the Gantt chart generation device 1 according to the present embodiment will be described with reference to FIG. The process of FIG. 11 starts when the object in the project of another project manager is copied on the display device D, and proceeds to step S11.

  In step S11, the control unit 10 receives from the display device D a shadow generation request indicating that an object in another project manager's project is to be generated by copying. The shadow generation request includes the ID (user name) of the project manager of the display device D that is the transmission source, the ID of the copy source object, and the ID of the project that includes the copy source object. After step S11, the process proceeds to step S12.

In step S12, the control unit 10 analyzes the shadow generation request and confirms the authority of shadow generation for the project manager who has transmitted the shadow generation request. Specifically, the control unit 10 refers to the member table 32 (FIG. 3) and determines the “role” value of the project manager who has transmitted the shadow generation request. If the value of “role” is “project administrator”, the user has the authority to generate a shadow and accepts a shadow generation operation. On the other hand, if the value of “role” is other than “project manager”, for example, “reference”, the project manager does not have the authority to generate a shadow. The administrator notifies that a shadow cannot be generated and ends this processing.
The control unit 10 refers to the member table 32 (FIG. 3), and the project manager who transmitted the shadow generation request is a member of the project of another project manager displayed on the display device D. Also check whether it exists. Basically, a project displayed in a multistage Gantt chart display on the display device D can be a project in which its own project manager is a member.
After step S12, the process proceeds to step S13.

  In step S <b> 13, the control unit 10 confirms the presence of the object that is the original of the shadow to be generated. Specifically, the control unit 10 refers to the activity table 34 and the milestone table 35 and acquires a record having the ID of the copy source object included in the shadow generation request. If the record cannot be acquired (for example, because it has already been deleted), the control unit 10 notifies the display device D that a shadow cannot be generated, and ends this processing. After step S13, the process proceeds to step S14.

  In step S <b> 14, the control unit 10 generates a shadow that is a target of a shadow generation request, and additionally registers a corresponding record in the shadow table 37. After step S14, the process proceeds to step S15.

  In step S <b> 15, the control unit 10 determines whether there is a request for generating a related line associated with the generated shadow. Specifically, a related line generation request is generated by performing a related line generation operation for associating the shadow with the object designated by the project manager on the display device D on which the shadow generation operation has been performed. Has occurred, and the control unit 10 determines whether or not it has been received from the display device D. If there is a related line generation request (Yes in step S15), the process proceeds to step S16. If there is no related line generation request (No in step S15), the process proceeds to step S17.

  In step S <b> 16, the control unit 10 generates a related line for which a generation request has been made, and additionally registers a corresponding record in the related line table 36. Thereby, by associating the shadow displayed on the display device D with the object specified by the project manager, the object handled by the project manager and the object handled by the other project manager Can be associated within a project manager's project. After step S16, the process proceeds to step S17.

  In step S <b> 17, the control unit 10 determines whether there is a progress rate set for the object that is the original of the generated shadow. Specifically, the control unit 10 refers to the result table 38 and determines whether or not the progress rate value is stored in the record of the original object. When the progress rate exists (Yes in step S17), the process proceeds to step S18, and when the progress rate does not exist (No in step S17), the process proceeds to step S19.

  In step S <b> 18, the control unit 10 transmits the progress rate image information stored in the original object record to the display device D for the generated shadow. Thereby, the same progress rate as the progress rate currently displayed with the original object can be displayed on the shadow which the display apparatus D displays. After step S18, the process proceeds to step S19.

  In step S19, the control unit 10 determines whether there is a document registered in the object that is the original of the generated shadow. Specifically, the control unit 10 refers to the activity table 34 or the milestone table 35 to determine whether there is a document registered in the record of the original object. If the document exists (Yes in step S19), the process proceeds to step S20. If the document does not exist (No in step S19), the process in FIG. 12 ends.

In step S20, the control unit 10 transmits the image information of the document registered in the original object record to the display device D in a state where the content of the document can be referred to for the generated shadow. Thereby, the same document as the document registered as the original object can be displayed in the shadow displayed by the display device D. The own project manager can confirm the details of the document by clicking the image of the document displayed in the shadow.
After step S20, the process of FIG.

  FIG. 13 shows a screen display example of the generated shadow and a related line that associates the shadow with the activity. Your project manager in charge of the project in the lower Gantt chart, see the upper Gantt chart for other project managers' projects and view activities (or milestones) that may be related to their tasks It designates from the input part of the apparatus D. When the display device D of its own project manager sends a shadow generation request to the Gantt chart generation device 1 for the specified activity, the shadow generation unit 15 of the Gantt chart generation device 1 copies the specified activity, The shadow S having the same shape can be displayed on the lower Gantt chart.

  His project manager can place the shadow S in a desired task area of his Gantt chart. The display control unit 40 of the display device D can display in a manner that clearly indicates that it is a shadow. For example, the shadow color can be made the same as the original color, and a predetermined transparency can be set to display the shadow transparently (for convenience of illustration, the shadow S can be used as an alternative to the transparent display). Show.)

  Conventionally, in order to refer to projects of other project managers in other departments, it is necessary for the own project manager to refer to the projects of other project managers. Also, after referring to other project managers' projects, it takes time to identify the objects related to the objects for which the project manager is responsible from the many objects in the projects of other project managers. I needed it.

According to the present embodiment, by generating a shadow of an object of another project manager's project once in the project manager's project, the other project manager's related project manager's shadow is generated. You can monitor the object. Thus, even if another project manager's object has changed (for example, even if the other project manager's activity end date has been lowered), refer to the project of another project manager. Without the need for separate notifications of changes from other project managers, the contents of the changes can be immediately known from the shadow.
As a result, using the Gantt chart, it is possible to review the own project at an early stage with respect to the project change related to the own project.
In general, according to the present embodiment, a plurality of projects displayed in multiple stages of Gantt charts are projects having different data management sources, data management locations (for example, locations of project managers), and the like. The Gantt chart generation apparatus 1 according to the present embodiment uses the function of displaying a plurality of projects having different characteristics on one screen, so that each project manager can cross over the management departments of each project in a timely manner. Information can be shared.

  Further, when the relation line associated with the shadow generated in the own project is registered in the relation line table 36 (step S16), the object handled by the own project manager and the object handled by the other project manager Can be associated within the project of their project manager (without crossing projects). In FIG. 13, a relation line L for associating a shadow with an object (activity in FIG. 13) is displayed. Even if the object of another project manager is changed by the association by the relation line L, the project of the other project manager is not referred to, and the change notification is sent from the other project manager. You can quickly review your project manager's objects that are likely to be affected by the change without having to ask for them separately.

  Further, when the progress rate is set for the activity that is the original of the shadow S, the result setting unit 18 can set the same progress rate for the shadow S. As a result, the display control unit 40 of the display device D can highlight the progress rate of the original activity in the shadow S (in FIG. 13, the same highlighting as the original progress rate is highlighted). However, in accordance with the shadow transparent display, the shadow progress rate highlighting display may be transparent. Therefore, the own project manager obtains the progress rate of other related project manager's objects in his / her project, and uses the obtained progress rate as a judgment material. Review can be done early.

  FIG. 14 shows a screen display example for explaining the reference of a document with a shadow. As shown in FIG. 14, when the document d1 is registered in the original object of another project manager, the document d2 having the same substance as the document d1 is displayed in the shadow of its own project. When the own project manager clicks the document d2, the display device D can display the attached file dialog F on the screen. Further, when the own project manager clicks the file (with hyperlink setting) in the attached file dialog F, the display device D can display the contents (not shown) of the file.

  In this way, their own project managers can use shadows to ensure that the documents that are expected to be related to their project managers from among the many documents registered in the objects of other project managers. Can be accessed (referenced). That is, it is possible to accurately find a document (input) to be used for work performed by the own project manager. For example, your project manager, who is responsible for manufacturing car parts, finds as input a car part design document that was created by another project manager who is responsible for car part design. You can start manufacturing a new document or create a new document for your project (such as a document that describes your manufacturing performance). Note that the Gantt chart generation device 1 allows the non-project manager of his / her project to update the results and register a new document as a work result of work such as manufacture of car parts. The chart display may be controlled.

  Next, with reference to FIG. 15, a shadow editing process when the original object is changed by the control unit 10 of the Gantt chart generation device 1 of the present embodiment will be described. The process of FIG. 15 is performed when an original object of another project manager is changed (for example, the end date of the activity is deferred) and a Gantt chart display request is received from the display device D of the own project manager. Start and go to step S21.

  In step S21, the control unit 10 analyzes the received Gantt chart display request and determines whether or not the project that is the target of the Gantt chart display request includes a shadow. Specifically, the control unit 10 refers to the shadow table 37 and determines whether there is a record having a project ID included in the Gantt chart display request. If the project that is the target of the Gantt chart display request includes a shadow (Yes in step S21), the process proceeds to step S22. If not included (No in step S21), the process of FIG.

In step S22, the control unit 10 changes the image information of the shadow. Specifically, the control unit 10 changes the shadow information confirmed in step S21 to the same image information as the image information when another project manager's original changed object is displayed on the Gantt chart. To the display device D. As a result, the project manager of his / her own can immediately know the latest state of the original object of the other project manager through the shadow.
If the change of the original object is a change of the contents of the document linked to the object, the contents of the document referred to via the shadow are also changed in the same manner, and the attached file dialog F The display content of (FIG. 14) is also updated to the content after the change. At this time, the shape, pattern, color, etc. of the document d1 in the original object and the document d2 (FIG. 14) in the shadow S may be changed. This makes it possible to immediately recognize changes in the input of their project manager.
Further, when the change of the original object is a change of the progress rate of the object, the display of the progress rate of the shadow can be made the same display as the progress rate after the change of the original object.
After step S22, the process proceeds to step S23.

  In step S23, the control unit 10 determines whether there is a related line associated with the changed shadow. Specifically, the control unit 10 refers to the related line table 36 and determines whether or not there is a record of the related line associated with the shadow confirmed to exist in step S21. If the related line exists (Yes in step S23), the process proceeds to step S24. If the related line does not exist (No in step S23), the process in FIG. 15 ends.

  In step S <b> 24, the control unit 10 determines whether or not the work schedule has been reversed for the related line associated with the changed shadow. Specifically, the control unit 10 determines whether or not the relationship between the shadow date and the object date, which are associated with the relation line, has been changed by changing the shadow original object. When the work schedule is reversed (Yes in step S24), the process proceeds to step S25. In this case, it means that it is assumed that it is impossible to start work that can be started by completing first. On the other hand, when the work schedule is not reversed (No in step S24), the process of FIG. 15 is terminated.

In step S25, the control unit 10 changes the image information of the related line in which the work schedule is reversed. Specifically, the control unit 10 transmits, to the display device D, image information that highlights a related line that associates a shadow and an object whose date order has been changed due to a change in shadow. As a result, the project manager who created the shadow can immediately know the inconvenience associated with the change of the object of another project manager.
After step S25, the process of FIG.

  FIG. 16 shows a screen display example for explaining the change of the shadow accompanying the change of the original object. As shown in FIG. 16, when the end date of the original activity A1 of another project manager is lowered, the end date of the shadow S is similarly lowered. As a result, when the end date of the shadow S is later than the start date of the activity A2 of the own project manager, the relation line L that associates the shadow S with the activity A2 is highlighted with a bold line or the like.

  Therefore, their own project managers can immediately know the reversal of work schedules due to changes in other project managers' objects by highlighting related lines, so that their own The object in charge can be reviewed at an early stage.

≪Others≫
When multiple departments collaborate and work in parallel, each department may share a milestone that should be protected, such as summarizing individual results by a predetermined date and completing intermediates. . At this time, conventionally, it has been extremely difficult for each department to grasp which object in each department is related to the node. According to the present embodiment, the knot can be set as a shadow, and a related line that associates a specific object of each department with the knot shadow can be generated. As a result, each department can immediately grasp which objects in other departments are related to the milestones. Therefore, when there is a change in the schedule of an object, each department discusses adjustments according to the schedule change. It is possible to easily identify what to do.

  Further, in the present embodiment, it has been described that the own project manager displays the shadow generated in the project of the own project manager. However, the Gantt chart generation device 1 controls to display the shadow generated in the project of another project manager that can be referred to by the project manager on the display device D of the project manager. You can also.

  Further, in this embodiment, even if the Gantt chart of the project of another project manager is not displayed, it is a shadow that has already been generated in the project of the own project manager, and the object of the other project manager The shadow that becomes a copy of can be displayed. If another project manager's object has been changed, the corresponding shadow can also be displayed in a modified manner.

  In the present embodiment, when a shadow is already generated in the project manager's project, the Gantt chart of another project manager's project including the shadow original is also displayed, and the original is selected. Described the creation of target shadows. However, it is also possible to introduce a Web API (Application Programming Interface) that defines a procedure for generating a target shadow without displaying the Gantt chart of the project of another project manager including the shadow original. As a result, even if the own project manager generates a shadow, the Gantt chart of the own project including the shadow can be displayed on the screen in an easy-to-read manner.

  Further, the shadow generation unit 15 of the Gantt chart generation device 1 according to the present embodiment can generate a secondary shadow obtained by copying a shadow generated by copying an original object as an original.

As a Gantt chart display function, displayed activities and milestones can be changed from their respective shapes (or colors) to desired shapes (or colors). For example, the milestone can be not only a circle (see FIG. 11) but also a triangle or a star depending on the application. When the original shape is changed, the shadow generation unit 15 of this embodiment can generate image information so that the shape of the shadow is the same as the original shape. Some users create a Gantt chart by giving a specific meaning to the original shape and color, and it is possible to generate a shadow that meets such user needs.
For example, in the Gantt chart, the original process can be distinguished and displayed by color, and the process can also be displayed by distinguishing the color by shadow. When software development is adopted based on the waterfall model, processes can be classified into requirement definition, design, implementation, unit test, combination test, and comprehensive test. The requirement definition is displayed in red, for example, and other processes. Are often displayed in other colors. In this case, the requirement-defined shadow can be displayed in red, and the shadows in the other processes can be displayed in the colors of the original processes.

In the present embodiment, components realized by hardware can be realized by software, and components realized by software can be realized by hardware.
Moreover, a new technique can be realized by appropriately combining the technical matters described in the present embodiment.
Other specific configurations of hardware, software, database, and the like can be changed as appropriate without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 1 Gantt chart production | generation apparatus 10 Control part 20 Communication part 30 Memory | storage part 11 Project production | generation part (project production | generation means)
12 task generation unit 13 object generation unit (object generation means)
14 related line generation part (related line generation means)
15 Shadow generator (shadow generator)
16 Document registration section (document registration means)
17 Document reference part (document reference means)
18 Performance setting section (performance setting means)
31 Project table 32 Member table 33 Task table 34 Activity table 35 Milestone table 36 Related line table 37 Shadow table 38 Results table 39 Document table

Claims (6)

A computer as a Gantt chart generation device for generating a Gantt chart,
Project generation means for generating a plurality of projects so that they can be displayed in multiple stages on a display device,
Object generation means for generating one or more objects in one project;
The project generation means generates a first project and a second project different from the first project, the first project manager manages the first project, and the second project is the first project. When a second project manager different from the one project manager manages
A shadow generating means for generating a shadow in the second project that is a copy of the object in the first project;
Gantt chart generation program to function as Said computer further
Related line generating means for generating a related line for associating the shadow with the object in the second project;
The Gantt chart generation program according to claim 1 for functioning as: Said computer further
Document registration means for registering a predetermined document in the specified object;
Document reference means for allowing the document to be referred to by the shadow when the document is registered in the object in the first project,
A Gantt chart generation program according to claim 1 or 2 for functioning as a program. Said computer further
A record setting means for setting a record of the object that is the copy source of the shadow in the shadow,
The Gantt chart production | generation program of any one of Claim 1 to 3 for functioning as. A Gantt chart generating device for generating a Gantt chart,
A project generation unit that generates a plurality of projects so that the display device can display multiple stages; and
An object generation unit for generating one or more objects in one project;
The project generation unit generates a first project and a second project different from the first project, the first project manager manages the first project, and the second project is the first project. When a second project manager different from the one project manager manages
A shadow generation unit that generates a shadow that is a copy of the object in the first project in the second project;
A Gantt chart generation device characterized by the above. A Gantt chart generation method in a Gantt chart generation device for generating a Gantt chart,
The Gantt chart generating device is
A project generation step for generating a plurality of projects so that the display device can display multiple stages; and
An object generation step of generating one or a plurality of objects in one project;
In the project generation step, a first project and a second project different from the first project are generated, the first project is managed by a first project manager, and the second project is In the case where a second project manager different from the first project manager manages,
Performing a shadow generation step of generating in the second project a shadow that is a copy of the object in the first project;
A Gantt chart generation method characterized by the above.

Images