JP2004355417A - Project information management device and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a project information management device capable of managing all information about a project, and if there are all operations for changing the information managed, creating a report format indicating the changes in the information caused by the operations, specifying members related to the information changed, and notifying the members of the report format. <P>SOLUTION: When a project state notification process part 220 is notified of a command from a document information processing part 204, a schedule information processing part 209, a project information processing part 213 or a user information processing part 217, it creates an appropriate document matching the command and determines whether the document is distributed to members of the project about the command or to all the users registered. It then creates a list of addresses to which the document should be distributed, and distributes the document to the addresses on the list. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
[Industrial applications]
The present invention relates to a project information management apparatus, and in particular, when a change occurs in information managed by the project information management apparatus, automatically changes details of the information to a user or a project involved in the project. The present invention relates to a project information management device for notifying a user who does not have any information.
[0002]
[Prior art]
Information sharing among members is extremely important for the smooth execution of project work. Conventional project information management devices use file sharing and e-mail on computer networks as a means for information sharing among members. Was used.
[0003]
However, in a project in which the shared information is frequently updated, a notification to that effect may be required when the shared information is updated. In such a case, the above-described file sharing and e-mail alone are not sufficient, and for example, the following problems have occurred.
[0004]
(1) When an information update notification is issued, e-mail or the like can be used. However, as the number of project members increases, it takes time and effort to select a user to be notified. To make matters worse, an appropriate user is not notified in a timely manner unless a distribution list is updated strictly according to a member change.
[0005]
(2) The text for notifying the information update must be prepared by the member who has changed the information, but if the text format is not strictly standardized, the level of the notification content varies depending on the user, There is a difference in the level at which changes are recognized.
[0006]
{Circle around (3)} If a project is not strictly enforced as to which update notification is issued to which information, there is a possibility that omission of communication will occur.
[0007]
In order to solve the above problems, there has been a demand for a mechanism for updating shared information of a project at an appropriate timing to an appropriate member with appropriate contents.
[0008]
Incidentally, in addition to the above, a technology relating to the project information management device is disclosed in Patent Document 1 below.
[0009]
[Patent Document 1] Japanese Patent No. 2956667
[0010]
[Problems to be solved by the invention]
Therefore, in view of the above problems, a main object of the present invention is to manage all information related to a project, and when there is any operation to change the managed information, a fixed form indicating the change of information by the operation. An object of the present invention is to provide a project information management device that creates a document, specifies a member related to changed information, and notifies the member of the fixed document.
[0011]
[Means for Solving the Problems]
The project information management device according to the first aspect of the present invention is a project information management device that manages information relating to one or more projects, a change screen providing unit that provides a screen for changing the information, A user information storage unit for storing a user to be configured and a delivery destination address of the user in association with each other and updating the storage content in response to a user change being input from the change screen; A fixed form document storing means for storing the fixed form document, and when a change of information relating to a predetermined project is input from the change screen, a delivery document corresponding to the change is based on the fixed form document stored in the fixed form document storing means. A delivery document creation unit to be created, and a change in information on a predetermined project is input from the change screen. A document distribution unit that determines a delivery destination address of a user related to the project based on the storage information of the user information storage unit, and distributes a delivery document created by the delivery document creation unit to the delivery destination address. It is characterized by the following.
[0012]
The project information management device according to the invention of claim 2 is characterized in that the change screen providing means provides a change screen according to the type of information to be changed.
[0013]
The project information management device according to a third aspect of the present invention is characterized in that the change screen providing means provides a screen for inputting a change in document information on the project.
[0014]
A project information management apparatus according to a fourth aspect of the invention is characterized in that the change screen providing means provides a screen for inputting a change in schedule information on the project.
[0015]
The project information management device according to the invention of claim 5 of the present application is characterized in that the change screen providing means provides a screen for inputting a change of current status information on the project.
[0016]
The project information management device according to the invention of claim 6 of the present application is characterized in that the change screen providing means provides a screen for inputting a change of user information on the project.
[0017]
In the project information management device according to the invention of claim 7, the document distribution unit includes a distribution document storage unit that stores the distribution document created by the distribution document creation unit, and completion of the change is input from the change screen. Until this is done, the distribution document created so far with respect to the information is stored in the distribution document storage unit, and stored in the distribution document storage unit in response to the completion of the change being input from the change screen. And delivering the document.
[0018]
The project information management device according to the invention of claim 8 is characterized in that the document distribution unit determines whether only a user who configures a project is a distribution destination or a distribution destination including users who do not configure a project. The storage device further includes a division storage unit that stores the information in association with the contents of the change, and when a change of the information is input, a distribution destination user is determined based on the storage contents of the division storage unit.
[0019]
A ninth aspect of the present invention is a program for causing a computer to function as the project information management device according to any one of the first to eighth aspects.
[0020]
The changes described in claims 1 to 8 of the present application broadly include not only the meaning of the original change but also the meaning of deletion and addition.
[0021]
The features of the present invention will become more apparent from the following description of embodiments.
[0022]
However, the embodiment described below is merely one embodiment of the present invention, and the meaning of the terms of the respective constituent elements according to the present invention is not limited to those described in the following embodiment. Absent.
[0023]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 is a configuration diagram of a project management server system using a project management server according to an embodiment of the present invention.
In the project management server 100, a project management program described later is executed to manage a plurality of pieces of project information.
[0024]
A user accessing the project management server 100 accesses the project management server 100 from the user terminal 300 via a network, thereby displaying information on a desired project on the user terminal 300 or from the user terminal 300 regarding the project. Edit information.
[0025]
FIG. 2 is a configuration diagram of the project management server 100 according to one embodiment of the present invention.
[0026]
Referring to FIG. 2, project management server 100 includes storage device 101, CPU 102, input device 103, and display device 104.
[0027]
The storage device 101 stores a project management program for executing a function described later, and also stores various tables and the like that are referred to when executing this function. The CPU 102 executes processing according to the project management program stored in the storage device 101. The input device 103 is used when the user inputs information necessary for executing the project management program. The display device 104 displays the execution result of the project management program by the CPU 102.
[0028]
FIG. 3 is a configuration diagram of each function of the project management server.
[0029]
The project management server 100 includes a my portal screen processing unit 201, a project portal screen processing unit 202, a document information operation screen processing unit 203, a document information processing unit 204, a document information management unit 205, a document management information table 206, and a document information table 207. Schedule information operation screen processing unit 208, schedule information processing unit 209, schedule information management unit 210, schedule management information table 211, project information operation screen processing unit 212, project information processing unit 213, project information management unit 214, project management information It includes a table 215, a user information operation screen processing unit 216, a user information processing unit 217, a user information management unit 218, a user management information table 219, a project status notification processing unit 220, a command management information table 221, and a document storage unit 222.
[0030]
The my portal screen processing unit 201 is a user interface screen for using the project management server 100 when a user logs in to the project management server 100 from the user terminal 300 via a network (hereinafter, referred to as a my portal screen). Is displayed on the user terminal 300.
[0031]
Referring to FIG. 4, on the My Portal screen, all the projects in which the login user is in charge and information on the projects are displayed (see the list of projects in charge in FIG. 4). The logged-in user selects a project portal icon, a project management icon, or a user management icon on the My Portal screen, and thereby a project portal screen processing unit 202, a project information operation screen processing unit 212, or a user information screen processing, which will be described later, respectively. The screen can be shifted to a screen displayed by the unit 216.
[0032]
In addition, a status change notification distributed to the login user from the project status notification processing unit 220 described later is also displayed on the My Portal screen (see the update notification list in FIG. 4).
[0033]
Here, the status change notification is described below when document information, schedule information, project information, and user information managed by the project management program 200 are changed, added, or deleted by another user or the user. The notification related to the change, addition, or deletion delivered from the project status notification processing unit 220.
[0034]
In the update notification list on the My Portal screen, the status change when there is a project change, addition, or deletion in the project information, or when the user changes, addition, or deletion in the user information A notification is displayed.
[0035]
The login user can recognize the change, addition, or deletion of the project information and the user information from the notification.
[0036]
The project portal screen processing unit 202 is a user interface for shifting to a screen displayed by a document information operation screen processing unit 203 and a schedule information operation screen processing unit 208 corresponding to a project selected by the login user for the login user. Display the screen (hereinafter referred to as the project portal screen).
[0037]
That is, when, for example, the project “1UR ** 1” is selected from the project in charge on the My Portal screen of FIG. 4, the project portal screen processing unit 202 selects the project “1UR ** 1” as shown in FIG. Display the project portal screen about.
[0038]
Referring to FIG. 5, on the project portal screen for project "1UR *** 1", a list of groups consisting of a plurality of members in charge of project "1UR *** 1" (member list in FIG. 5 is displayed). Reference) is displayed.
[0039]
Also, the login user can shift to the screen displayed by the document information operation screen processing unit 203 by selecting the document management icon on the project portal screen of FIG. 5, and can select the schedule information operation screen by selecting the schedule management icon. The screen can be shifted to a screen displayed by the processing unit 209.
[0040]
Also, on the project portal screen, among the status change notifications distributed from the project status notification processing unit 220 described later, there was a change, addition, or deletion of document information and schedule information on the project for which the login user is in charge. The status change notification in the case is displayed (see the update notification list in FIG. 5).
[0041]
The log-in user can recognize from the notification that the document information and the schedule information have been changed, added, or deleted for the project in charge of the user.
[0042]
The document information operation screen processing unit 203 displays a screen (hereinafter, referred to as a document information screen) showing a list of documents created for the project to the login user.
[0043]
Referring to FIG. 6, the login user can input document information such as deletion, change, copy, move, or creation of a new document from the document information screen.
[0044]
That is, the login user selects one document from the document tree of FIG. 6, and then selects a file delete icon, a file change icon, a file copy icon, or a file move icon to delete, change, or delete the document. You can copy or move. By selecting the file registration icon, a new document can be created. When the file change icon or the file registration icon is selected, the screen shifts to a document change or new document creation screen (not shown). After the login user changes a document and creates a new document on each screen, the user selects a completion icon (not shown) on each screen to complete each process and return to the document information. Return to the screen.
[0045]
When receiving document information from the document information screen, the document information operation screen processing unit 203 outputs the document information to the document information processing unit 204.
[0046]
When document information is input from the document information operation screen processing unit 203, the document information processing unit 204 acquires a document corresponding to the document information from a document information management unit 205 described later, and sends the document to the document information operation screen processing unit 203. hand over. The document information operation screen processing unit 203 displays the edit screen for the login user. If the document information is newly created, a new document edit screen is displayed.
[0047]
Further, when there is an input of document information from the log-in user, the document information processing unit 204 inputs the document information together with the title of the deleted, changed, copied, moved, or newly created document and the name of the project to which the document is related. A command indicating the presence is notified to a project information notification processing unit 220 described later.
[0048]
The document information management unit 205 extracts text document management information corresponding to the document information from the document information processing unit 204 from a document management information table 206 described later, and extracts a document corresponding to the document management information from a document information table described later. Extracted from 207 and passed to document information processing section 205.
[0049]
The document management information table 206 stores document management information for document management, and the document information table 207 stores documents corresponding to the document management information.
[0050]
The schedule information operation screen processing unit 208 displays a schedule screen (hereinafter, referred to as a schedule screen) of events constituting a schedule of a project to be assigned to the login user. Here, the project schedule includes a plurality of different tasks, and an event refers to a task that constitutes the project.
[0051]
Referring to FIG. 7, the log-in user can input event information such as deletion and change of an event, editing of a scheduled date of an event in charge, or addition of an event from the schedule screen.
[0052]
That is, the login user selects one event from the schedule screen, and then selects the event deletion icon, the event change icon, or the scheduled date edit icon to delete, change, or schedule the event. Can edit. When the event addition icon is selected, an event can be added. When the event change icon, the event addition icon, or the scheduled date editing icon is selected, the screen shifts to a screen (not shown) for changing the event, adding an event, or editing the scheduled date of the event. After the login user changes the event, adds the event, or edits the scheduled date of the event on each screen, the user selects the completion icon (not shown) on each screen to perform each processing. Is completed, and the screen returns to the schedule screen again. Finally, by selecting the event editing end icon on the schedule screen, the input of the event information ends.
[0053]
When schedule information is input from the login user on the schedule screen, the schedule information processing unit 209 outputs the input schedule information to the schedule information management unit 209 described below, and outputs the schedule information to the project state notification processing unit 220 described below. , A command indicating that the schedule information has been input, and the event name thereof. When the scheduled date of the event is changed, not the schedule after the change but the schedule before the change that has been recognized by each member is notified to draw the attention of each member.
[0054]
The schedule information management unit 210 updates the schedule management information stored in the schedule management information table 211 described below based on the input schedule information.
[0055]
The project information operation screen processing unit 212 displays a user interface screen (hereinafter, referred to as a project information screen) for creating a new project, deleting or changing an existing project for a login user.
[0056]
Referring to FIG. 8, the login user can input project information such as deleting, changing, or registering a project from the project information screen.
[0057]
That is, the login user can delete or change the project by selecting one project from the project information screen and then selecting the project deletion icon and the project change icon. When the project registration icon is selected, a project can be registered. When the project change icon or the project registration icon is selected, the screen shifts to a project change or project registration screen (not shown). After the login user changes a project or registers a project on each screen, the user selects a completion icon (not shown) on each screen to complete each process and return to the project information again. Return to the screen.
[0058]
When the project information is input from the project information operation screen processing unit 212, the project information processing unit 213 outputs the project information to the project information management unit 214, which will be described later, and sends the project information to the project status notification processing unit 220, which will be described later. Notifies the name of the project that has been changed, added, or deleted, with a command indicating that the information has been entered.
[0059]
The project information management unit 214 accesses a project management information table 215 described later, and updates the project management information based on the input project information.
[0060]
Further, when a member is added to the project, the project information management unit 214 assigns an account to the project portal screen processing unit 202 for the project to the member. For example, when the member A is added to the project “1UR *** 1”, the member A receives “Member A @ 1UR **” as an account to the project screen processing unit 202 for the project “1UR *** 1”. * 1.COM ”is assigned.
[0061]
As shown in FIG. 10, the project management information table 215 includes all projects managed on the project management program, members in charge of each project, and projects in charge of each member of the project portal screen processing unit 202 of each member. The account to which is stored.
[0062]
The user information operation screen processing unit 216 displays a user interface screen (hereinafter, referred to as a user information screen) for updating the user information for the login user. Referring to FIG. 9, the login user can input user information such as deletion, change, or registration of the user from the user information screen.
[0063]
That is, the login user can delete or change the user by selecting one user from the user information screen and then selecting the user deletion icon and the user change icon. When the user registration icon is selected, user registration becomes possible.
[0064]
When the user change icon or the user registration icon is selected, the screen shifts to a user change or user registration screen (not shown). After the login user changes the user or registers the user on each screen, the user selects the completion icon (not shown) on each screen, thereby completing the respective processing and returning to the user information. Return to the screen.
[0065]
When the user information is input from the user information operation screen processing unit 216, the user information processing unit 217 outputs the user information to the user information processing unit 217 described later, and sends the user information to the project status notification processing unit 220 described later. Notify the user name that has been changed, deleted, or registered along with a command indicating that the information has been input.
[0066]
The user information management unit 218 accesses a user management information table 219 described later and updates the user management information based on the input information.
[0067]
When the user is registered, the user information management unit 218 assigns an account to the my portal screen processing unit 201 to each user.
[0068]
As shown in FIG. 11, the user management information table 219 stores accounts of all users registered in the project management program to the my portal screen processing unit 201.
[0069]
The project status notification processing unit 220 includes commands notified from the document information processing unit 204, the schedule information processing unit 209, the project information processing unit 213, and the user information processing unit 217, and information notified along with each command. Based on the command management information table 221, an appropriate document is created, the project management information table 215 and the user management information table 219 are used to determine a user to be delivered, and a project portal screen of the user to be delivered Or deliver the created document to the My Portal screen.
[0070]
The document storage unit 222 is a storage unit that stores a distribution document created by the project status notification processing unit 220.
[0071]
The command management information table 221 is configured as shown in FIG. Referring to FIG. 12, the command name column includes commands notified from document information processing unit 204, schedule information processing unit 209, project information processing unit 213, or user information processing unit 217 to project status notification processing unit 220. Is described.
[0072]
"Single" or "accumulation" is described in the notification type column, and "F" or "T" is described in the completion command column.
[0073]
The notification type “single shot” indicates that document distribution is performed each time the command is notified. On the other hand, when the notification type is “accumulate”, even if the command is notified a plurality of times, if the completion command of the command is “F”, document distribution is not performed, and the notification type is “accumulate” and the When a command whose command is “T” is notified, a document is created together with a document that has not been distributed and has been accumulated, and is distributed.
[0074]
The column of the distribution screen describes “My Portal Screen” or “Project Portal Screen”, and indicates whether to distribute to the My Portal Screen or the Project Portal Screen.
[0075]
In the text field, a template of an appropriate document corresponding to the command is described. The project status notification processing unit 220 incorporates the file name, scheduled date, event name, project name, etc. notified together with the command into a document. Complete and deliver.
[0076]
For example, when the administrator of the project management server performs a user registration process for “member Z” from the user information screen (see FIG. 9), the user information processing unit 217 issues a “user addition” command and a user name “member Z ″ is notified to the project status notification processing unit 220.
[0077]
When receiving the “user addition”, the project status notification processing unit 220 searches the command management table 221. Referring to the command management table 221 in FIG. 12, the project status notification processing unit 220 detects the “add user” command, creates “add user member Z” from the text thereof, and temporarily stores it in the document storage unit 222. Store. Since the distribution type is “single shot”, the “add user” command distributes the text stored in the document storage unit 222 and then deletes the text from the document storage unit 222. Further, since the distribution screen is “My Portal”, the accounts of all users registered in the user management information table 219 to the My Portal screen processing unit 201 are detected, and the text “Add User Member Z” is added to this account. To deliver.
[0078]
As a result, "add user" member Z "" is notified to the update notification list (see FIG. 4) on the My Portal screen of all users registered in the project management server 100.
[0079]
Also, for example, when the member A who is the login user selects the event “design” of the project “1UR *** 1” in charge from the schedule screen shown in FIG. 7 and selects the event change icon, the event change screen ( (Not shown). When the member A changes the event on the event change screen and completes the change of the event by selecting the completion icon (not shown), the schedule information processing unit 209 executes the “event change” command and the project name “ 1UR ** 1 "and the event name" design "are notified to the project status notification processing unit 220.
[0080]
When receiving the “event change”, the project status notification processing unit 220 searches the command management table 221. With reference to the command management table 221 in FIG. 12, the project status notification processing unit 220 detects “event change”, creates “change event design” from the text, and temporarily stores it in the document storage unit 222. . Since the “event change” command has the distribution type “accumulate” and the completion command “F”, the text stored in the document storage unit 222 is accumulated without being distributed. Subsequently, when the member A further changes the event “manufacturing” from the schedule screen of FIG. 7, similarly, “change event manufacturing” is created, and the distribution type is “accumulate” and the process is completed. Since the command is “F”, the command is not distributed and is stored in the document storage unit 222.
[0081]
Finally, when the member A finishes changing the series of events by selecting the event editing end icon from the schedule screen of FIG. 7, the schedule information processing unit 209 issues a “schedule editing end” command and a project name “1UR”. *** 1 "to the project status notification processing unit 220.
[0082]
When receiving the “schedule edit end”, the project status notification processing unit 220 performs the same operation, creates the text “event changed” with reference to the command management table 221 shown in FIG. The document is stored in the document storage unit 222. Further, since the distribution type is “accumulate” and the completion command is “T”, the “schedule edit end” command includes the texts stored in the document storage unit 222, “change event design”, and “event change”. “The manufacturing has been changed” and “the event has been changed” are distributed as one text, and these texts are deleted from the document storage unit 222.
[0083]
Here, since these command distribution screens are “project portal”, the project status notification processing unit 220 determines from the project management information table 215 the project “1UR ** 1” of the member in charge of the project “1UR ** 1”. An account for “* 1” to the project portal screen processing unit 202 is detected, and the created text is delivered to this account.
[0084]
As a result, a list of update notifications on the project portal screen for the project "1UR **** 1" of all members in charge of the project "1UR *** 1" managed by the project management server 100 (see FIG. 5). Will be notified that the event has been changed. All members in charge of "1UR ** 1" can refer to the text by selecting the title "Event has been changed" in the update notification list (see FIG. 5) on the project portal screen.
[0085]
Next, a document distribution flow by the project status notification processing unit 220 will be described with reference to FIG.
[0086]
Referring to FIG. 13, in step S100, the contents of document storage unit 222 are reset, and the process proceeds to step S101.
[0087]
In step S101, it is determined whether there is a command notification from the document information processing unit 204, the schedule information processing unit 209, the project information processing unit 213, or the user information processing unit 217. If there is a command notification, the process proceeds to step S102. .
[0088]
In step S102, the project status notification processing unit 220 refers to the command management information table 221 to determine whether the delivery type of the notified command is “single shot”, and if it is “single shot”, the process proceeds to step S107. Otherwise, the process proceeds to step S103.
[0089]
In step S103, it is determined whether the accumulation flag is ON. The accumulation flag is a flag indicating whether to distribute the document corresponding to the notified command or to accumulate without distributing the document. If the accumulation flag is ON, the process proceeds to step S105; otherwise, the process proceeds to S104.
[0090]
In step S104, the accumulation flag is turned on, and the process proceeds to step S107.
[0091]
In step S105, it is determined with reference to the command management information table 221 whether the completion command of the notified command is “T” or “F”. If the completion command is "T", the process proceeds to step S106, the accumulation flag is turned off, and the process proceeds to step S108. If the completion command is “F”, the process proceeds to step S107.
[0092]
In step S107, the project name, the file name of the document, the event name, the user name, or the scheduled date of the event before the change is performed in the text template of the text field of the notified command in the text template. By incorporating it, the text is completed and stored in the document storage means 222, and the process proceeds to step S108.
[0093]
In step S108, it is determined whether or not the accumulation flag is ON. If the accumulation flag is ON, the process returns to step S101 without distributing the document. If it is OFF, the process proceeds to step S109.
[0094]
In step S109, it is determined whether the document delivery destination is the My Portal screen. If the destination is the My Portal screen, the process proceeds to step S111; otherwise, the process proceeds to step S110. The determination of the distribution destination refers to the command management information table 221, and if "My Portal" is described in the distribution screen column corresponding to the notified command, the distribution destination is the My Portal screen of all users. If "project portal" is described, it is determined that the screen is a project portal screen for the project of all members in charge of the project of the project name notified together with the command.
[0095]
In step S110, referring to the project management information table 215, all the members in charge of the project detect accounts of the project portal for the project, create a distribution address list, and proceed to step S112.
[0096]
In step S111, the user management information table 219 is referred to, the accounts of my portal of all the registered users are detected, a distribution address list is created, and the process proceeds to step S112.
[0097]
In step S112, the document stored in the document storage unit 222 is distributed to the address of the created address list, and the process returns to step S100.
[0098]
As can be understood from the above description, when the project status notification processing unit 220 receives a command notification from the document information processing unit 204, the schedule information processing unit 209, the project information processing unit 213 or the user information processing unit 217, the command management information table With reference to H.221, an appropriate document is created according to the command. Further, the project status notification processing unit 220 determines from the notified command whether to deliver the document to the members of the project relating to the command or to all registered users, and With reference to the management information table 219, an address list to be delivered is created, and the created document is delivered to the addresses in the address list.
[0099]
With this configuration, the logged-in user can change, add, or delete document information or schedule information on the project for which the user is responsible, or change, add, or delete the project or registered user. If there is, you can know the change of the information only by logging in to the project management program.
[0100]
On the other hand, a logged-in user who has changed, deleted, or added information on a project as described above must create a distribution document and distribute it from a vast number of registered users after changing the information. This eliminates the troublesome task of identifying the user and distributing the document.
[0101]
The embodiments of the present invention can be variously modified as appropriate within the scope of the technical idea of the present invention.
[0102]
【The invention's effect】
According to the present invention, all information related to a project is managed, and when there is any operation that changes the managed information, a fixed document indicating the change of information by the operation is created, and the changed information is created. Can be provided, and a project information management apparatus capable of notifying the user of the fixed document by specifying the user related to the project information can be provided.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a project management system according to an embodiment.
FIG. 2 is a diagram showing a configuration of a project management server according to the embodiment.
FIG. 3 is a diagram showing a configuration of each function of a project management server according to the embodiment.
FIG. 4 is a display example of a my portal screen displayed by a display device 104 to a login user.
FIG. 5 is a display example of a project portal screen displayed by the display device 104 to a login user.
FIG. 6 is a display example of a document information screen displayed by the display device 104 to a login user.
FIG. 7 is a display example of a schedule setting screen displayed by the display device 104 to a login user.
FIG. 8 is a display example of a project setting screen displayed by the display device 104 to a login user.
FIG. 9 is a display example of a user setting screen displayed by the display device 104 to a login user.
FIG. 10 is a data structure of a project management information table 215.
FIG. 11 is a data structure of a user management information table 219;
FIG. 12 is a data structure of a command management table 221.
FIG. 13 is a diagram showing a flowchart according to the embodiment.
[Explanation of symbols]
200 Project management program
201 ・ ・ ・ My portal screen processing unit
202 ・ ・ ・ Project portal screen processing unit
203: Document information operation screen processing unit
204: Document information processing unit
208: schedule information operation screen processing unit
209 ・ ・ ・ Schedule information processing unit
212 Project information operation screen processing unit
213 ... Project Information Processing Department
216 ... user information operation screen processing unit
217 ... user information processing unit
220 ・ ・ ・ Project status notification processing unit
221... Command management information table

Claims (9)

In a project information management device that manages information on one or more projects,
Change screen providing means for providing a screen for changing the information,
User information storage means for storing a user constituting a project in association with a delivery destination address of the user and updating the stored content in response to a user change being input from the change screen;
A standard document storage unit for storing a standard document according to the type of change of the information,
When a change of information on a predetermined project is input from the change screen, a delivery document creating unit that creates a delivery document corresponding to the change based on the standard document stored in the standard document storage unit,
When a change of information on a predetermined project is input from the change screen, a delivery destination address of a user related to the project is determined based on information stored in the user information storage unit, and the delivery document creation is performed on the delivery destination address. Document delivery means for delivering a delivery document created by the means;
A project information management device comprising: 2. The project information management device according to claim 1, wherein the change screen providing unit provides a change screen according to a type of information to be changed. 3. The project information management device according to claim 2, wherein the change screen providing unit provides a screen for inputting a change in document information on the project. The project information management device according to claim 2, wherein the change screen providing unit provides a screen for inputting a change in schedule information regarding the project. The project information management device according to claim 2, wherein the change screen providing unit provides a screen for inputting a change in current status information regarding the project. The project information management device according to claim 2, wherein the change screen providing unit provides a screen for inputting a change of user information regarding the project. The document distribution unit includes a distribution document storage unit that stores the distribution document created by the distribution document creation unit. Until the completion of the change is input from the change screen, the document has been created with respect to the information. 3. A delivery document is stored in said delivery document storage means, and the document stored in said delivery document storage means is delivered in response to completion of change being input from said change screen. 6. The project information management device according to any one of 6. The document distribution means further includes a division storage means for storing, in association with the contents of change of the information, whether only the users constituting the project are to be the distribution destinations or the distribution destinations including the users who do not constitute the project. 8. The project information management apparatus according to claim 1, wherein when a change of the information is input, a distribution destination user is determined based on the storage content of the classification storage unit. A program for causing a computer to function as the project information management device according to claim 1.

Images