JP2004062740A - Schedule management method and system - Google Patents

Abstract

By linking a project management system and a schedule management system, the trouble of a user who has to access each of the two can be reduced.
A project management system sets a meeting ID in association with work schedule data and registers both in a work schedule database. Also, the conference information is transmitted to the schedule management system 106 to start the conference reservation processing. The schedule management system 106 reserves conference facilities and participating members, and registers reservation data relating to the conference in the schedule database 111. Further, it receives advance materials or minutes, registers them in the document management system 107, and registers advance material IDs and minutes IDs in the schedule database 111 in association with reservation data.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a schedule management technique, and more particularly to a schedule management technique that cooperates with a project management technique.
[0002]
[Prior art]
As a schedule management technique, for example, as described in Japanese Patent Application Laid-Open No. 2000-315228, a project member's schedule is registered and managed, and a schedule ID assigned to schedule data and a document related to the schedule data are stored. There is a schedule management system provided with a data processing unit that manages them in association with each other.
[0003]
[Problems to be solved by the invention]
Conventionally, a schedule management system and a project management system are constructed as separate systems. For this reason, after setting a meeting necessary for proceeding with the work process in the project management system, it is necessary to make a reservation for a meeting room and a participating member for holding the meeting in the schedule management system. Also, it is not easy to derive information about related work processes based on the names of conferences and conference participants. In addition, meeting materials for distribution in advance and minutes of the meeting after the meeting are created, but this meeting material and minutes must be separately registered or referenced via a document management system. was there. Furthermore, no consideration was given to encouraging participating members to prepare pre-meeting materials and minutes in time for the meeting.
[0004]
An object of the present invention is to solve the above problem by linking project management and schedule management.
[0005]
[Means for Solving the Problems]
The present invention sets an identifier of a conference to be held in connection with the work in association with the work schedule data of the work constituting the project in the storage means, and sets the meeting including the meeting identifier, the date, the time, and the participating members of the meeting. The information is transmitted to the schedule management means to start the conference reservation process, and the schedule management means reserves the conference facility based on the date, time, and participating members in the conference information, and the conference identifier, the date, and the reserved time. A schedule management technique for creating schedule data including bands, participating members and reserved conference facilities, registering the schedule data in storage means, and setting identifiers of advance materials and identifiers of conference minutes in association with the schedule data. .
[0006]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0007]
FIG. 1 is a system configuration diagram showing an embodiment of the present invention. Reference numeral 101 denotes a project manager (U004) that performs project management, and a client computer corresponds to the device. Reference numeral 102 denotes a worker (U001) of the project members, which corresponds to a client computer as an apparatus. Reference numerals 103 and 104 denote project members (U002 and U003), each of which corresponds to a client computer. 105 is a project management system, 106 is a schedule management system, 107 is a document management system, and is deployed on one or a plurality of server computers. A work schedule database 108 is provided in the project management system 105 and stores work schedule data 113 transmitted by the project manager 101. A conference information database 109 stores conference schedule data 114 and conference member data 115 transmitted by the project manager 101. Reference numeral 110 denotes a user / facility management database that manages information on users and facilities registered in the system. Reference numeral 111 denotes a schedule database that stores schedule data relating to a conference. Reference numeral 112 denotes a document database for registering advance materials created by the worker 102 at the time of holding the meeting and minutes of the meeting after the meeting. The above databases are all stored on a storage device.
[0008]
The work schedule management unit 120 of the project management system 105 receives the work schedule data 113, the meeting reservation data 114, and the meeting member data 115, registers the work schedule data in the work schedule database 108, and stores the meeting schedule data in the meeting information database. Register to 109. Further, the work schedule management unit 120 responds to a search request for the work schedule database 108 and the conference information database 109. The project information management unit 119 accesses the user / facility information management database 110 of the schedule management system 106 via the schedule management cooperation unit 118. The schedule management cooperation unit 118 has a function of communicating with the schedule management system 106.
[0009]
The user / facility management unit 121 of the schedule management system 106 responds to data registration, update, and reference requests to the user / facility information management database 110. The reservation execution / management unit 122 creates reservation data relating to the holding of the conference and registers it in the schedule database 111. Further, the reservation execution / management unit 122 requests the worker in charge 102 to transmit advance materials of the meeting, and accesses the document management system 107 to register the received advance materials in the document database 112. Further, the reservation execution / management unit 122 accesses the document management system 107 to obtain a template for creating the minutes after the meeting, requests the worker 102 to transmit the minutes, and receives the received minutes. To the document management system 107 in order to register the Further, in response to a request from the client, the reservation execution / management unit 122 searches the schedule database 111 and transmits the requested schedule data to the client. Further, the reservation execution / management unit 122 accesses the project management system 105 or the document management system 107 in response to a request for document data or work schedule data, and mediates acquisition of these data. The schedule adjustment unit 123 accesses the user / facility information management database 110 and searches for facilities to be used for the conference and free time for the conference participants. The project management cooperation unit 124 has a function of communicating with the project management system 105. The document management cooperation unit 125 has a function of communicating with the document management system 107.
[0010]
The document management unit 127 of the document management system 107 responds to a request for registering, updating, and referencing document data in the document database 112. The template creating unit 128 creates a template of the minutes from the given meeting information. The schedule management cooperation unit 126 has a function of communicating with the schedule management system 106.
[0011]
FIG. 2 is a diagram illustrating an example of a data configuration of user information managed by the user / facility information database 110. Each user information data in the user / facility information database includes a worker name 201, an ID 202, a personal schedule of the user, and the like. When creating the work schedule data, the user ID for the registered project member's name is referred to. When creating the minutes of a meeting, the name corresponding to the user ID is referred to.
[0012]
FIG. 3 is a diagram illustrating an example of a data configuration of facility information managed by the user / facility information database 110. Each facility information in the user / facility information database 110 is composed of a facility name 301, an ID 302, a use status of the facility (use date, time zone), and the like. Since the present invention deals with facilities for meetings, the facilities are typically conference rooms. When creating the meeting minutes, the facility name corresponding to the facility ID is referred to.
[0013]
FIG. 4 is a diagram illustrating an example of a data configuration of the work schedule database 108. Each work schedule data includes a work ID 401, a work name 402, a start date 403, the number of work days 404, a worker 405, a meeting ID 406, a status 407, and the like. The work ID 401 and the conference ID 406 are added by the work schedule management unit 108. In the case of work that does not require a conference, “−” is registered in the conference ID 406. “Not yet” is registered in the status 407 at first, but when the work is completed, it becomes “completed”. The work schedule data is created based on the work schedule data 113.
[0014]
FIG. 5 is a diagram illustrating an example of a data configuration of the conference information database 109. Each meeting schedule data in the meeting information database 109 includes a meeting ID 501, a meeting name 502, a date 503, a holding time 504, a worker 505, a participating member 506, a status 507, and the like. "Not yet" is initially registered in the status 507, but when the conference ends, the status is "completed". The meeting schedule data is created based on the meeting schedule data 114 and the meeting member data 115.
[0015]
FIG. 6 is a diagram illustrating an example of a data configuration of the schedule database 111. Each schedule data is composed of a meeting name 601, a meeting ID 602, a date 603, a holding time 604, a reservation person 605, a reservation member 606, a facility 607, a prior material ID 608, a minutes ID 609, and the like. The holding time 604 of the reservation data matches the reservation person, the reservation member, and the vacant time zone of the facility. The worker 505 is set as the reservation person 605. The reservation member 606 is set from the participating member 506. Of the schedule data, the conference name 601 to the facility 607 are reservation data, and the preliminary material ID 608 and the minutes ID 609 are set when the preliminary materials and minutes are registered, respectively.
[0016]
FIG. 7 is a diagram illustrating an example of a data configuration of the document database 112. Each document management data includes a document ID 701, a registrant 702, a registration date 703, a document name 704, and the like. The prior material ID 608 or the minutes ID 609 is set in the document ID 701. The registrant 702 is set to the reservation person 605, and the document name 704 is set to the file name of the document data.
[0017]
FIG. 8 is a diagram illustrating an example of a minutes template. Heading information separated by [] is fixed information. The variable information from "planning meeting" to "Yamada" is automatically generated from the meeting name 601, the date of the meeting 603, the holding time 604, the facility 607, the reservation member 606, and the reservation person 605, respectively.
The contents of [Purpose] [Details] and [Future schedule] are to be prepared by the minutes creator.
[0018]
Next, a processing procedure of a program in which the project management system 105 receives data such as the work schedule data 113 from the project manager 101 and creates the work schedule database 108 and the conference information database 109 will be described with reference to the flowchart of FIG. First, the project manager 101 sends the work schedule data 113, the meeting schedule data 114, and the meeting member data 115 to the work schedule management unit 120 of the project management system 105. The work schedule management unit 120 sequentially receives the work schedule data 113, the meeting schedule data 114, and the meeting member data 115 (Steps 901, 902, and 903). Next, a work ID is obtained for the work schedule data (step 904), and a meeting ID is further obtained for the meeting schedule data (step 905). The project information management unit 119 acquires the user ID for the name of the worker in charge and the name of the meeting participant from the user / facility management database 110 of the schedule management system 106 via the schedule management linkage unit 118 (step 906). Are registered in the work schedule database 108 and the conference information database 109, respectively (step 907).
[0019]
Here, assuming that the schedule data is data of the work ID S001 in FIG. 4, the work name is work 1, the work start date is 2002/3/8, the number of work days is 4, and the worker is Yamada, ie, the user of the schedule management system 106. The user ID is set to U001 from the facility information database 110. A conference required for the work is registered as a conference IDK001. The status is initially set to "not yet". The meeting schedule data is registered as the data of the meeting ID K001 in FIG. 5 with respect to the meeting ID previously obtained. That is, the conference name is "Planning Conference", the date is March 11, 2002, the holding time is one hour, the worker is U001 (Yamada), and the participating members are Sato, Tanaka, and Suzuki, ie, users of the schedule management system 106. -Each user ID is set as U002, U003, and U004 from the facility information database 110. In addition, the status is initially set to “not yet”.
[0020]
Next, a processing procedure of a program in which the reservation execution / management unit 122 of the schedule management system 106 creates reservation data from information registered in the conference information database 109 of the project management system 105 will be described with reference to the flowchart of FIG. As an example of data registered in the conference information database 109, data of the conference ID K001 in FIG. 5 is used. First, the work schedule management unit 120 of the project management system 105 determines whether or not meeting schedule data is stored in the meeting information database 109 (step 1001). If there is no meeting schedule data, the process ends.
[0021]
If the meeting schedule data exists, for example, assuming that the data of the meeting IDK001 in FIG. 5 is the meeting IDK001, the meeting name “planning meeting”, the date of the meeting 2002/3/11, the holding time of 1 hour, the worker U001 and the participating members U002, U003, and U004 are acquired and sent to the schedule management system 106 through the schedule management cooperation unit 118 (step 1002). The schedule adjusting unit 123 of the schedule management system 106 determines whether the worker in charge U001 is a reservation person and the participating members U002, U003, and U004 are reservationees, and whether there is a one-hour schedule available on March 3, 2002. The user / facility management database 110 is searched for user information and facility information (step 1003). A search is made for a vacant time zone of a facility that can be used for a conference based on the vacant time zone that matches the reservation person and the participating member. In this example, it is found that the facility with the facility ID S001 is available from 10:00 to 11:00 at the holding time. Here, as a means for searching for the free time of the reservation person, the participating member and the facility, a multi-stage free time search system disclosed in JP-A-10-91685 can be used. Next, the reservation execution / management unit 122 creates reservation data including information such as the previously acquired conference name “planning conference” and the holding time 10:00 to 11:00 acquired as a result of the search, including the facility ID S001 ( Step 1004). In this example, the data from the conference name 601 to the facility 607 in FIG. 6 is the reservation data. Next, the reservation execution / management unit 122 registers the created reservation data in the schedule database 111, and notifies the reservation data to the reservation person and the participating members (step 1005).
[0022]
Next, the reservation execution / management unit 122 of the schedule management system 106 requests the worker 102 to register advance materials, and the document management system 107 registers the prior materials in the document database 112. It will be described using FIG. First, the reservation execution / management unit 122 of the schedule management system 106 searches the schedule database 111 to determine whether there is data set after the reservation date of the reservation data is within 7 days (step 1101). Here, it is assumed that the conference ID K001 in FIG. Next, the corresponding reservation data is sent to U001 of the person in charge of the reservation data, that is, the worker in charge 102, and a request for prior material registration is made (step 1102). Upon receiving the request, the worker in charge (U001) transmits the preliminary data together with the reservation data (step 1103). The reservation execution / management unit 122 accesses the document management system 107 via the document management cooperation unit 125, acquires the document ID of the advance material through the document management unit 127 (step 1104), and acquires the corresponding schedule data in the schedule database 111. The document ID, that is, B001, is registered in (step 1105). The received reservation data may be re-registered. Next, the acquired document IDB001, the worker in charge, ie, the reservation person U001, and the preliminary material (file name “planning material”) are sent to the document management unit 127 via the schedule management cooperation unit 126 of the document management system 107, and the document management unit 127 Creates document data and registers it in the document database 112 (steps 1106 and 1107). The registered data is the data of the document IDB001 in FIG. Further, the schedule management system 106 notifies the conference participants, that is, U002, U003, and U004, of the completion of the advance material registration (step 1108). Meeting participants can access the document database 112 of the document management system 107 and refer to the registered prior materials.
[0023]
Next, the reservation execution / management unit 122 of the schedule management system 106 requests the worker 102 to register the minutes, and the document management system 107 registers the minutes in the document database 112. It will be described using FIG. First, the reservation execution / management unit 122 of the schedule management system 106 refers to the schedule data and determines whether there is data for which the processing day is set to the meeting date (step 1201). Here, it is assumed that the conference ID K001 in FIG. Next, the name “Yamada” is obtained from the user / facility management database 110 via the user / facility management unit 121 from the user ID U001 of the person who made the reservation data, ie, the worker in charge. Also, the names of Sato, Tanaka, and Suzuki are similarly acquired for the reservation members, that is, the meeting participation members U002, U003, and U004. Further, for the facility ID S001, the facility name “facility A” is similarly acquired and transmitted to the template creation unit 128 via the schedule management cooperation unit 126 of the document management system 107. The received template creation unit 128 creates a template of the minutes from the data (step 1202). FIG. 8 shows an example.
[0024]
Next, the reservation data and the minutes template are sent to the reservation person of the reservation data, that is, U001 of the worker 102, to request the minutes registration (step 1203). The worker in charge (U001) receives the request, creates the minutes, and transmits the minutes together with the reservation data (step 1204). The reservation execution / management unit 122 acquires the document ID of the received minutes via the document management system 107 (step 1205), and registers the document ID, ie, B006, in the corresponding schedule data of the schedule database 111 (step 1206). . The received reservation data may be re-registered. Next, the acquired document IDB 006, the worker in charge, ie, the reservation person U001, and the minutes (file name “Planning Meeting Minutes”) are sent to the document management unit 127 via the schedule management linkage unit 126 of the document management system 107, and the document management is performed. The unit 127 creates document data and registers it in the document database 112 (steps 1207 and 1208). The registered data becomes the data of the document IDB006 in FIG. Further, the schedule management system 106 notifies the meeting participants, that is, U002, U003, and U004, that registration of the minutes has been completed (step 1209). The conference participant can access the document database 112 of the document management system 107 and refer to the registered minutes of the conference.
[0025]
Next, the work schedule management unit 120 of the project management system 105 searches the meeting information database 109 based on the meeting ID K001, and sets the status 507 of the corresponding meeting schedule data to “completed” (step 1210). When the work is completed, the work schedule management unit 120 searches the work schedule database 108 according to an instruction from the worker 102 and sets “completed” in the status 407 of the corresponding work. That is, the data of the work ID S001 in FIG. 4 is updated.
[0026]
Next, the processing procedure of a program for searching for registered work schedules and documents will be described with reference to the flowchart in FIG. First, the reservation execution / management unit 122 of the schedule management system 106 receives search conditions such as a meeting name, a work name, a document name, a worker (meeting participant name), and a date from the client (step 1301). The schedule database 111 is searched under the conditions (step 1302), and the search result is transmitted to the client (step 1303). If there is a request for reference to a registered document from the client (step 1304yes), the document database 112 of the document management system 107 is searched from the document ID of the schedule data to acquire a document (step 1305). Further, if there is a request for reference to the work schedule data from the client (step 1306yes), the work schedule database 108 of the project management system 106 is searched from the meeting ID of the schedule data, and the work ID is obtained (step 1307). Is obtained (step 1308). For example, if the retrieval condition from the client is the conference name “planning conference”, the retrieved schedule data is the data of the conference ID K001 in FIG. Further, the acquired document is “planning material” of the document IDB001 of FIG. 7 and “minutes of the planning meeting” of the document IDB006, and the acquired work schedule data is data having the work ID S001 of FIG.
[0027]
【The invention's effect】
As described above, according to the present invention, by linking project management and schedule management, a conference is set up by the project management system and then the conference facilities and participating members required for the conference are automatically reserved. Also, the user enters the schedule management system, and can access work schedule data managed by the project system, advance materials and meeting minutes managed by the document management system, using the conference name and the participating members as keys. Further, it is possible to urge the worker to prepare advance materials and minutes of the meeting at a timing depending on the date of the meeting.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration of a system according to an embodiment.
FIG. 2 is a diagram illustrating a data configuration example of user information in a user / facility management database.
FIG. 3 is a diagram showing a data configuration example of facility information in a user / facility management database.
FIG. 4 is a diagram showing a data configuration example of a work schedule database.
FIG. 5 is a diagram illustrating a data configuration example of a conference information database.
FIG. 6 is a diagram illustrating a data configuration example of a schedule database.
FIG. 7 is a diagram illustrating a data configuration example of a document database.
FIG. 8 is a diagram showing an example of a minutes template.
FIG. 9 is a diagram showing a processing procedure for creating a work schedule database and a meeting information database.
FIG. 10 is a diagram showing a processing procedure for reserving a schedule from conference information.
FIG. 11 is a diagram showing a processing procedure for registering advance materials in a document management system.
FIG. 12 is a diagram showing a processing procedure for registering minutes in a document management system.
FIG. 13 is a diagram showing a processing procedure for searching for a work schedule and a document.
[Explanation of symbols]
105: Project management system, 106: Schedule management system, 107: Document management system, 108: Work schedule database, 109: Meeting information database, 110: User / facility management database, 111: Schedule database, 112: Document database, 120: Work schedule management unit, 122: reservation execution / management unit, 123: schedule adjustment unit.

Claims (5)

The identifier of the conference to be held in association with the work is set in the storage means in association with the work schedule data of the work constituting the project, and the schedule management of the meeting information including the meeting identifier, the date of the meeting, the time, and the participating members is performed. Means to start the conference reservation process,
The schedule management means reserves a conference facility based on the date, the time and the participating members in the conference information, and the conference identifier, the date, the reserved time zone, the participating members and the reserved A schedule management method comprising: creating schedule data including a meeting facility; registering the schedule data in a storage unit; and setting an identifier of a preliminary material and an identifier of a meeting minutes in association with the schedule data. Receiving the designation of a participant name included in the participating member, acquiring the conference identifier of the corresponding schedule data from the schedule data, and acquiring the corresponding work schedule data via the conference identifier. The schedule management method according to claim 1. 2. The schedule management method according to claim 1, wherein a request is made to the client computer to create the advance materials and the minutes of the meeting at a timing depending on the date of the meeting. A system in which the project management means and the schedule management means cooperate,
The project management means includes means for setting an identifier of a meeting to be held in association with the work in the storage means in association with the work schedule data of the work constituting the project, a meeting identifier of the meeting, date, time, and participation. Means for transmitting conference information including members to the schedule management means to start a conference reservation process,
The schedule management means includes means for reserving a conference facility based on the date, the time, and the participating members in the conference information, and the conference identifier, the date, the reserved time zone, the participating members, and the reservation. A schedule for creating schedule data including the conference facility described above and registering the schedule data in a storage unit; and a unit for setting an identifier of a preliminary material and an identifier of a meeting minutes in association with the schedule data. Management system. The schedule management unit further receives a designation of a participant name included in the participant, acquires the conference identifier of the corresponding schedule data from the schedule data, and the corresponding work schedule via the conference identifier. 5. The schedule management system according to claim 4, further comprising means for acquiring data.

Images