JP5285654B2 - Schedule adjustment support apparatus, schedule reservation method, and schedule reservation program - Google Patents

Description

  The present invention relates to a schedule adjustment support apparatus, a schedule reservation method, and a schedule reservation program that adjust and reserve a schedule of a plurality of participants.

  Various techniques for adjusting a plurality of related schedules are disclosed. For example, in Patent Document 1, the same related schedule ID is attached to the related schedule, and when a specific schedule is changed, a schedule having the same related schedule ID as the changed schedule is searched, and these A technique for changing the schedule in conjunction with each other is disclosed.

  In Patent Document 2, when the related schedule is changed in conjunction, if there is an existing schedule at the date and time to be changed, or if it is a movement prohibition date that prohibits the change of the schedule, the date and time before and after those schedules are changed. A technique for moving a schedule is disclosed.

  In Patent Document 3, in order to create a series of routine schedules, the implementation contents, implementation order, and implementation time interval of a plurality of items to be implemented are recorded in advance as a template together with data used in the implementation. In addition, a technique is disclosed in which, when creating and registering a schedule as an actual schedule, only the date and time information of the template is adjusted, and all items to be scheduled are registered as a schedule in a lump.

Japanese Patent Application Laid-Open No. 08-22495 Japanese Patent Laid-Open No. 10-293783 Japanese Patent Laid-Open No. 11-296486

  The prior art is intended for adjustment with a related schedule when scheduling a conference, and a schedule between people participating in the conference is not disclosed. Typically, when setting up a conference, it can be very laborious to adjust the schedule of a large number of participants.

  For example, a schedule such as a meeting has a role in the schedule (for example, whether or not it is an organizer) for each schedule and for each participant of the schedule. There are also individual schedules according to their role in the schedule.

  Here, a schedule such as a meeting or a briefing session is called a main schedule, and a user who reserves the main schedule selects and registers a participant of the main schedule. Also, a schedule according to the role of the main schedule, or a schedule related to a customer briefing session such as a social gathering is called a secondary schedule, and a schedule for executing the secondary schedule is also a secondary schedule. Call it. In a conventional schedule adjustment support system, participants in the main schedule have to determine their roles from the contents of the main schedule, and each participant has to register a sub-schedule.

  In addition, in the conventional schedule adjustment support system, the system has no relation between the main schedule and the sub-schedule. For example, when the user changes the date and time of the main schedule, the system changes the sub-schedule in conjunction. I can't. Therefore, each participant had to modify the sub schedule.

  In the technique described in Patent Document 1, when a date and time change is made in the main schedule, the related schedules can be changed in conjunction with each other. However, it is necessary for the participant to individually register a plurality of related schedules, which is troublesome. Further, it is necessary to individually set the association between the main schedule and a plurality of schedules, which is a complicated operation.

  In the technique described in Patent Literature 2, when the related schedule is changed in conjunction with the change of the main schedule, the changed schedule can be adjusted so as not to overlap the movement prohibition date or the existing schedule. . However, in order to adjust the related schedule, it is necessary to have a free time frame in which the time required for all related schedules is added, so there is no free time before and after the date and time of the changed schedule. The schedule date and time may be delayed.

  In the technique described in Patent Document 3, a series of schedules can be registered, but since it is personal schedule management, the role of the user has not been considered.

  The present invention is an invention for solving the above-described problem, and is a schedule adjustment support apparatus, a schedule reservation method, and a schedule reservation method capable of adjusting and reserving schedules of a plurality of participants in consideration of user convenience The purpose is to provide a schedule reservation program.

  In order to achieve the above object, the schedule adjustment support apparatus (for example, the schedule management apparatus 100) of the present invention provides the main schedule for each type of main schedule (for example, the model condition ID or the model condition name) in which a plurality of participants participate. One or more sub-schedules necessary for executing the schedule, role sub-schedule management information (for example, template sub-schedule management table 110) for managing the role and condition information for executing the full schedule for each sub-schedule, and A storage device for storing schedule management information (for example, schedule management table 118) for managing the schedule reservation status of the participants, and an allowable date and time zone in which the main schedule can be implemented for the main schedule reservation, Time required for main schedule, type of main schedule, participants and A screen display processing unit that displays to input condition information including the role of the participant, and the template sub-schedule management information is identified from the input condition information. Based on the specified template sub-schedule management information, To execute the sub-schedule from the sub-schedule condition analysis processing unit that analyzes the association between the input participant and the sub-schedule, and the template sub-schedule management information and schedule management information using the role of the input participant as a key Analyzes the time required for the main schedule and the time required for the sub-schedule within the allowable time zone of the main schedule from the time calculation processing unit that calculates the time required for the sub-schedule and the schedule management information Based on the free time analyzed by the free time analysis processor and the free time analyzed by the free time analysis processor. And a schedule adjustment processing unit for adjusting the sub-schedules of a plurality of participants, and a schedule reservation processing unit for reserving and registering the main schedule and the sub-schedule adjusted by the schedule adjustment processing unit in the schedule management information And

  According to the present invention, it is possible to make a reservation by adjusting a schedule of a plurality of participants in consideration of user convenience.

It is a figure which shows the structure of the schedule management apparatus which concerns on embodiment of this invention. It is a figure which shows the relationship between each process part and each table, and the flow of control. It is a figure which shows the example of a model sub schedule management table. It is a figure which shows the example of a template condition information management table. It is a figure which shows the example of a model role information management table. It is a figure which shows the example of a main schedule management table. It is a figure which shows the example of a role information management table. It is a figure which shows the example of a user information management table. It is a figure which shows the example of a base information management table. It is a figure which shows the example of a sub schedule management table. It is a figure which shows the example of a schedule management table. It is a figure which shows the example which changed the order of the sub schedule management table. It is a figure which shows the example which changed the time of the main schedule of the schedule management table. It is a figure which shows the outline | summary of the process sequence which reserves a schedule. It is a figure which shows the process sequence which produces | generates the sub schedule object required from a reservation object. It is a figure which shows the process sequence which produces | generates a free time candidate object from a sub schedule object. It is a figure which shows the outline | summary of the process sequence which registers a schedule. It is a figure which shows the process sequence which determines the date and time of a sub schedule, and registers a sub schedule. It is a figure which shows the process sequence at the time of changing the time of a main schedule. It is a figure which shows the process sequence at the time of changing subschedule conditions. It is a figure which shows the example of the reservation object list which a schedule adjustment process part produces on a main memory. It is a figure which shows the example of the template condition information object which a schedule adjustment process part produces on a main memory. It is a figure which shows the example of the secondary schedule object list which a secondary schedule condition analysis process part produces on a main memory. It is a figure which shows the example of the free time candidate object which a free time analysis process part produces on a main memory. It is a figure which shows the example of the screen which designates the template conditions of a schedule. It is a figure which shows the example of the screen which reserves a schedule. It is a figure which shows the example of the screen which sets the sub schedule conditions of schedule "A product briefing session". It is a figure which shows the example of the screen which refers to the schedule registered into each participant. It is a figure which shows the example of the screen which changes the content of the schedule "A product briefing session". It is a figure which shows the example of the screen at the time of changing the sub schedule condition information "order" of schedule "A product briefing session". It is a figure which shows the example of the screen which refers to the schedule registered into each participant at the time of schedule "A product briefing session", and the sub schedule condition information "order" of "A product briefing session" being changed. It is a figure which shows the example of the main screen of a schedule reservation.

Hereinafter, modes for carrying out the present invention (referred to as “embodiments”) will be described in detail.
FIG. 1 is a diagram showing a configuration of a schedule management apparatus 100 according to the embodiment of the present invention. Explaining the outline processing of the schedule management device 100 (schedule adjustment support device), it is used from one or more template sub-schedule management tables 110 (model sub-schedule management information) stored in the storage device 109 of the schedule management device 100. When the template to be selected is selected, the sub-schedule management information for the main schedule is registered in the sub-schedule management table 117. The schedule management apparatus 100 creates a secondary schedule from the secondary schedule management information set by the user and the primary schedule information, and registers the schedule in the primary schedule management table 116 and the schedule management table 118 (schedule management information). In this way, it is possible to save the user from associating and registering the main schedule and the sub-schedule. In addition, when changing the main schedule, the schedule management apparatus 100 refers to the sub-schedule management information in the sub-schedule management table 117 to effectively use the free time of each participant and readjust the sub-schedule. These processes will be described in detail with reference to the drawings as appropriate.

  The schedule management apparatus 100 includes a main storage device 101, a CPU 119, a storage device 109, and the like. The CPU 119 executes various programs stored in the main storage device 101. The storage device 109 stores various data for the schedule management device 100 to execute processing. The main storage device 101 holds various programs executed by the schedule management device 100 and temporary data. The schedule management apparatus 100 communicates with the client PC 121 via the network 120. There may be a plurality of client PCs 121. CPU is an abbreviation for Central Processing Unit, and PC is an abbreviation for Personal Computer.

  The main storage device 101 stores a screen display processing unit 102, a schedule adjustment processing unit 103, a schedule reservation processing unit 104, and an analysis unit 105. The analysis unit 105 includes a sub-schedule condition analysis processing unit 106, a required time calculation processing unit 107, and a free time analysis processing unit 108.

  The storage device 109 stores a template sub-schedule management table 110 (model sub-schedule management information) (see FIG. 3) having template sub-schedule condition information for each template condition (for each template condition ID), a template condition ID and a template condition name. Template condition information management table 111 to be associated (see FIG. 4), template condition ID, template role ID, and model role information management table 112 to associate template role names (see FIG. 5), role information management table having role information in the main schedule 113 (see FIG. 7), a user information management table 114 (see FIG. 8) for associating the work location for each user, a base information management table 115 (see FIG. 9) for associating the base ID and base name, and the main schedule input by the user Main schedule management table 116 (see FIG. 6) having the following information, main schedule Sub-schedule management table 117 (see FIGS. 10 and 12) having sub-schedule condition information of the schedule, and schedule management table 118 (see FIGS. 11 and 13) having schedule information reserved for the participants and reserved schedule information. ) Is stored.

  FIG. 2 is a diagram illustrating the relationship between each processing unit and each table and the flow of control. The operation processing relationship between each processing unit and each table will be described with reference to FIG. Reference is made to FIG. 1 as appropriate.

  Based on the role information management table 113, the sub-schedule management table 117, and the schedule management table 118, the schedule adjustment processing unit 103 performs role information in the main schedule, sub-schedule condition information in the main schedule, schedule information reserved for participants, Exchange data such as reserved schedule information and adjust the schedule.

  The screen display processing unit 102 includes a schedule adjustment processing unit 103, an analysis unit 105, a schedule reservation processing unit 104, main schedule information input by the user, sub-schedule condition information, schedule information to be reserved for participants, and reservation information. Data such as schedule information is exchanged and a screen is displayed on the client PC 121. Examples of screens to be displayed are shown in FIGS.

  FIG. 32 is a diagram showing an example of a main screen 3200 for schedule reservation. FIG. 32 shows a screen displayed on the display device of the client PC 121. The main screen 3200 includes a “schedule reservation” button 3201, a “schedule change” button 3202, and a member used to search for a member confirming the schedule. A “search member” button 3203, a schedule section 3204 for displaying the reservation status, and a “close” button 3205 for closing the main screen. Note that the schedule unit 3204 can be switched between a monthly unit, a week unit, and a day unit.

  Specifically, the case of the user 1 shown in FIG. 32 will be described. Reservations for the week from October 20 to October 26 are already registered in the schedule management table 118 (see FIG. 1). When making a new reservation for an individual schedule, it is easy to find a free time by looking at the schedule contents of the schedule unit 3204. However, conventionally, when user 1 is the organizer and wants to reserve a briefing session for A product, not only the person but also all participants can check the reservation status, check free time, check travel time, etc. Therefore, it is necessary to determine the schedule, and it takes a lot of time to confirm the reservation.

  In the case of this embodiment, when a schedule reservation user presses a “schedule reservation” button 3201, a schedule reservation screen 2600 (see FIG. 26) shown in FIG. If you select a time, place, template, and participant, you can adjust the schedule and schedule the participants as well as the organizer. Further, when the user presses the “schedule change” button 3202 for a schedule once reserved, the reservation can be changed from the schedule change screen 2900 (see FIG. 29). Details of other screens (FIGS. 25 to 30) will be described later.

  Returning to FIG. 2, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 includes a template sub-schedule management table 110, a template condition information management table 111, a template role information management table 112, and template sub-schedule condition information for each template condition. Exchange data and analyze the sub-schedule conditions.

  Based on the user information management table 114, the base information management table 115, and the schedule management table 118, the required time calculation processing unit 107 of the analysis unit 105 includes information on the user's working place, base information, and reserved schedule information data. The time required for schedule reservation is calculated.

  Based on the main schedule management table 116, the sub schedule management table 117, and the schedule management table 118, the free time analysis processing unit 108 of the analysis unit 105 is sub schedule condition information of the main schedule, schedule information to be reserved for the participants, reservation Data such as schedule information is exchanged, and analysis is performed as to whether there is free time in the schedule of the participant who reserves the schedule.

  The schedule reservation processing unit 104, based on the role information management table 113, the sub-schedule management table 117, and the schedule management table 118, the role information of the participant, the sub-schedule condition information of the main schedule, the schedule information and the reservation to be reserved for the participant Exchange schedule data and other data and make schedule reservations. Details of each processing unit and each table will be described later.

  FIG. 3 is a diagram illustrating an example of the template sub-schedule management table 110. Specific information managed by the template sub-schedule management table 110 will be described with reference to FIG. In the template sub-schedule management table 110, a schedule ID 301 that is an ID for uniquely identifying a sub-schedule, a schedule name 302 for displaying to a user, and an ID for uniquely identifying a template condition used in the sub-schedule. A certain template condition ID 303 (type of main schedule), a template role ID 304 that is an ID for identifying a role to be registered in the sub-schedule, an order of schedule reservation date and time are set, and the position of the main schedule is set to “0”. If it is earlier than the start date and time of the schedule, it is a negative number. If it is later than the end date and time of the main schedule, it indicates the order in which the positive value is held 305, and whether the sub schedule must be the same day as the main schedule. Same day 306, secondary schedule should be adjacent to main schedule Adjacent 307 indicating whether or not, the time interval required by the sub-schedule is held in minutes, or if the time required by the sub-schedule fluctuates, the required time 308 to hold the text “automatic”, and the sub-schedule is reserved Information on the sub-schedule serving as a template is managed, such as an allowable time 309 indicating a time zone in which the job can be performed and a type 310 indicating the type of the sub-schedule. In addition, although the example of the order 305 shown in FIG. 3 is 2, 1, 3, 4 from the top, -1, -2, 1, and 2 may be sufficient.

  FIG. 25 is a diagram showing an example of a screen 2500 for specifying a schedule template condition. A screen 2500 for specifying a schedule template condition is a user interface screen displayed on the display device of the client PC 121 by the screen display processing unit 102 in order for the user to set a template condition for a sub-schedule for the main schedule. The screen 2500 for specifying schedule template conditions is called when the condition setting button 2614 on the schedule reservation screen 2600 (see FIG. 26) is pressed.

  A screen 2500 for specifying schedule template conditions includes a template name field 2501 having a template pull-down menu 2502, a template item table 1515, a secondary schedule addition button 2511, a secondary schedule deletion button 2512, an OK button 2513, and a cancel button 2514.

  The template item table 2515 has a sub-schedule name column 2503, a role column 2504, and a condition column 2505. The secondary schedule name column 2503 has a secondary schedule selection check box 2508 for each secondary schedule. The role column 2504 includes a role addition button 2506, a role deletion button 2507, a role selection check box 2509, and a sub schedule assignment check box 2510 for each sub schedule.

  The template pull-down menu 2502 displays the value of the template condition name 402 in the template condition information management table 111. Specifically, template condition names such as “unused”, “for briefing session”, “for meeting” are displayed.

  The user sets the name of the schedule template condition to be registered in the template pull-down menu 2502 on the screen 2500 for specifying the template conditions of the schedule. When changing the template conditions of a schedule used by the user, the user selects a schedule template condition name from the template pull-down menu 2502, and a screen 2500 for specifying the template conditions of the schedule is displayed. Is displayed.

  The sub-schedule name column 2503 displays the value of the schedule name 302 of the sub-schedule that matches the template condition ID 401 of the template condition selected from the template pull-down menu 2502 and the template condition ID 303 of the template sub-schedule management table 110. Specifically, when the template condition is “for explanatory meeting”, sub schedules of “preparation”, “movement (row)”, “cleanup”, and “movement (return)” with the template condition ID “C002” are displayed. To do.

  When the user presses the sub schedule addition button 2511, the screen display processing unit 102 displays a screen on which the user can input the name of the sub schedule to be added, and the sub schedule input by the user is displayed in the sub schedule name field 2503. Add to When the user selects a sub-schedule in the sub-schedule selection check box 2508 in the sub-schedule name column 2503 and presses the sub-schedule delete button 2512, the screen display processing unit 102 checks the sub-schedule selection from the sub-schedule name column 2503. The secondary schedule selected in box 2508 is deleted.

  The role column 2504 displays the value of the template role name 503 of the role that matches the template condition ID 401 of the template condition selected from the template pull-down menu 2502 and the template condition ID 501 of the template role information management table 112. Specifically, when the template condition is “for explanatory meeting”, the roles of “organizer” and “participant” whose template condition ID is “C002” are displayed.

  When the user presses the add role button 2506, the screen display processing unit 102 displays the name of the role to be added and a screen that can be input by the user, and adds the role input by the user to the role column 2504. To do. When the user selects a role in the role selection check box 2509 in the role column 2504 and presses the delete role button 2507, the screen display processing unit 102 deletes the role selected in the role selection check box 2509 from the role column 2504. To do.

  The condition column 2505 includes an order specification column 2516 having an order text box 2521, a same day specification column 2517 having a same day specification check box 2522, an adjacent specification column 2518 having an adjacent specification check box 2523, and a required time specification text box 2524. A time specification column 2519, an allowable time specification column 2520 (allowable time zone) having an allowable time specification text box 2525, and a type specification column 2526 having a type specification text box 2528 are displayed.

  The user selects a role to execute the sub-schedule from the sub-schedule assignment check box 2510 in the role column 2504, and designates the order to execute the sub-schedule in the order text box 2521. At the first display, the value set in the order 305 of the template sub-schedule management table 110 is displayed. In this embodiment, the position of the main schedule is set to “0”, and a negative value is specified when it is before the start date and time of the main schedule, and a positive value is specified when it is after the end date and time of the main schedule.

  In addition, the user selects whether to set the secondary schedule to the same date as the main schedule by using the same day designation check box 2522. When the same day designation check box 2522 is selected, the sub-schedule needs to be executed on the same day as the main schedule, and the value of the attribute is “Y” (see the column of the same day 306 shown in FIG. 3). If the same day designation check box 2522 is not selected, the secondary schedule does not need to be executed on the same day as the main schedule, and the value of the attribute is “N” (see the column of the same day 306 shown in FIG. 3). At the time of initial display, the value set for the same day 306 in the template sub-schedule management table 110 is displayed.

  In addition, the user selects whether the main schedule and the sub-schedule are adjacent by using the adjacent designation check box 2523. When the adjacent designation check box 2523 is selected, the secondary schedule needs to be adjacent to the main schedule, and the value of the attribute is “Y” (see the column of the adjacent 307 shown in FIG. 3). When the adjacent designation check box 2523 is not selected, the secondary schedule does not have to be adjacent to the main schedule, and the attribute value is “N” (see the column of the adjacent 307 shown in FIG. 3).

  If the same day specification check box 2522 is not selected, the adjacent specification check box 2523 of the sub-schedule is inactive, and the user cannot select the adjacent specification check box 2523. At the first display, the value set in the adjacent 307 of the template sub-schedule management table 110 is displayed.

  In addition, the user designates the time required for executing the sub-schedule in the required time designation text box 2524 in minutes. At the time of initial display, the value set in the required time 308 of the template sub-schedule management table 110 is displayed.

  In addition, the user designates a time in which the secondary schedule can be reserved in the allowable time designation text box 2525. In the allowable time designation text box 2525, a plurality of reservable time zones can be designated in the format of “start time to end time”, separated by commas. At the time of initial display, the value set in the allowable time 309 of the template sub-schedule management table 110 is displayed.

  Further, the user designates the type of the sub schedule in the type designation text box 2528. At the first display, the value set in the type 310 of the template sub-schedule management table 110 is displayed.

  The OK button 2513 has a function of transmitting the input data to the schedule management apparatus 100. When the user presses the OK button 2513, the input data is confirmed. Thereafter, the schedule adjustment processing unit 103 registers the template condition setting contents in the template condition information management table 111. When the user presses the cancel button 2514, the value of the input item and the template condition setting content are canceled, and the screen display processing unit 102 closes the screen 2500 for specifying the schedule template conditions.

  FIG. 4 is a diagram illustrating an example of the template condition information management table 111. The template condition information management table 111 manages information that is a template of conditions such as a template condition ID 401 that is an ID for uniquely identifying a template condition and a template condition name 402 that is a name of a template condition displayed to the user.

  FIG. 5 is a diagram illustrating an example of the template role information management table 112. In the template role information management table 112, a template condition ID 501 that is an ID for uniquely identifying a template condition, a template role ID 502 that is an ID for uniquely identifying a role, and a template that is a name of a role to be displayed to the user. Role information used in the template condition information such as role name 503 is managed.

  FIG. 6 is a diagram illustrating an example of the main schedule management table 116. In the main schedule management table 116, a main schedule ID 601 that is an ID for uniquely identifying the main schedule, a participant ID 602 that holds a list of participants in the main schedule with a user ID, and a condition that is a template for the main schedule is unique. Main schedule information such as a template condition ID 603, which is an ID for identifying each, is managed.

  FIG. 7 is a diagram illustrating an example of the role information management table 113. In the role information management table 113, a main schedule ID 701 that is an ID for uniquely identifying the main schedule, a role ID 702 that is an ID for uniquely identifying a role required in the main schedule, and the role are displayed to the user. For example, role information such as a role name 703 that is a name for managing the role is managed.

  FIG. 8 is a diagram illustrating an example of the user information management table 114. In the user information management table 114, a user ID 801 that is an ID for uniquely identifying a participant, a user name 802 that is a name for displaying the participant to the user, and a user working location 803 that indicates the working location of the participant. Manage user information.

  FIG. 9 is a diagram illustrating an example of the base information management table 115. The base information management table 115 manages base information such as a base ID 901 that is an ID for uniquely identifying a base and a base name 902 that is a name for displaying the base to the user. Here, the base indicates a place where the user works or a place where the schedule is held, and the system manages the base information based on information registered by the user.

  FIG. 10 is a diagram illustrating an example of the secondary schedule management table 117. Specific information for the A product briefing session managed by the secondary schedule management table 117 will be described with reference to FIG. In the secondary schedule management table 117, condition information of the secondary schedule corresponding to the primary schedule is managed. A primary schedule ID 1001 that is an ID for uniquely identifying the primary schedule, a secondary schedule ID 1002 that is an ID for identifying the secondary schedule, a secondary schedule name 1003 that is a name for displaying the secondary schedule to the user, and a secondary schedule A role ID 1004 that is an ID for identifying a role to be reserved, an order 1005 that retains the context of the schedule reservation date, the same date 1006 indicating whether the sub-schedule needs to be the same day as the main schedule, sub-schedule Adjacent to the main schedule 1007, a required time 1008 indicating the time required for the secondary schedule, an allowable time 1009 indicating a time zone in which the secondary schedule can be reserved, a type 1010 indicating the type of the secondary schedule, etc. , Deputy schedule To manage the condition information of Le.

  The sub-schedule management table 117 for the A product briefing session shown in FIG. 10 includes sub-schedules registered by the user using the schedule reservation screen 2600 shown in FIG. 26 and the sub-schedule condition setting screen 2700 shown in FIG. Management information. When the user tries to reserve the main schedule of the A product briefing session, it is necessary to check the schedule of each participant and adjust the time. As the auxiliary schedule related to the A product briefing session, preparation, movement, tidying up, social gathering, etc. can be considered.

  FIG. 26 is a diagram showing an example of a screen 2600 for reserving a schedule. FIG. 27 is a diagram showing an example of a sub-schedule condition setting screen 2700 for the schedule “A product briefing session”.

  In the schedule reservation screen 2600, the schedule condition information set on the sub schedule condition setting screen 2700 displayed by pressing the condition setting button 2614 is registered in the sub schedule management table 117.

  Details of the schedule reservation screen 2600 will be described with reference to FIG. The schedule reservation screen 2600 is a user interface screen displayed on the display device of the client PC 121 by the screen display processing unit 102 in order for the user to reserve a schedule.

  The user sets the schedule item in the item text box 2607 of the item 2601, the start date of the date for which the schedule is reserved in the date text box 2608 of the date 2602, the end date of the date in the date text box 2609, and the time of time 2603. In the text box 2610, the required time in hours, in the minute text box 2611 in required minutes, and in the place pull-down menu 2612 of the place 2604, select a place to execute the schedule. The location pull-down menu 2612 displays the location name 902 of the location information management table 115.

  When the user selects a template condition (item of use template 2701) to be used on the sub schedule condition setting screen 2700, the screen display processing unit 102 selects the template condition name selected in the template condition text box 2613 of the template 2605. Set.

  In the area of the participant 2606, when the user presses the user addition button 2619, the screen display processing unit 102 displays a user designation screen (not shown) that can designate a participant who reserves the schedule, and the user selects it. A row is displayed in which the user name of the selected user is displayed in the user name area 2616 of the participant 2606.

  The role pull-down menu 2618 in the role area 2617 of the participant 2606 displays the role name displayed in the role column 2704 of the sub-schedule condition setting screen 2700 displayed by pressing the condition setting button 2614. The user designates a role to the participant added to the participant 2606 using the role pull-down menu 2618.

  In addition, the user can delete a participant from the participant 2606 by selecting a participant using the user selection check box 2615 in the area of the participant 2606 and pressing a user deletion button 2620.

  The OK button 2621 has a function of transmitting the input data to the schedule management apparatus 100. When the user presses the OK button 2621, the input data is confirmed. When the user presses a cancel button 2622, the data input so far is canceled, and the screen display processing unit 102 closes the schedule reservation screen 2600.

  Details of the sub-schedule condition setting screen 2700 will be described with reference to FIG. The sub-schedule condition setting screen 2700 is a user interface screen displayed on the display device of the client PC 121 by the screen display processing unit 102 in order for the user to set sub-schedule conditions for the main schedule.

  The secondary schedule condition setting screen 2700 includes a usage template 2701 having a usage template pull-down menu 2702, a secondary schedule item table 2715, a secondary schedule addition button 2711, a secondary schedule deletion button 2712, an OK button 2713, and a cancel button 2714. The secondary schedule item table 2715 has a secondary schedule name column 2703, a role column 2704, and a condition column 2705. The secondary schedule name field 2703 has a secondary schedule selection check box 2708 for each secondary schedule. The role column 2704 includes a role addition button 2706, a role deletion button 2707, a role selection check box 2709, and a sub schedule assignment check box 2710 for each sub schedule.

  The usage template pull-down menu 2702 displays the value of the template condition name 402 in the template condition information management table 111. Specifically, template condition names such as “unused”, “for explanatory meetings”, and “for meetings” are displayed. In the secondary schedule name column 2703, the value of the schedule name 302 of the template secondary schedule management table 110 is displayed. Specifically, when the template condition is “for explanatory meeting”, the sub-schedule names such as “preparation”, “move (row)”, “clean up”, “move (return)”, etc., with the template condition ID “C002” Is displayed.

  When the user presses the sub schedule addition button 2711, the screen display processing unit 102 displays a screen on which the user can input the name of the sub schedule to be added, and displays the sub schedule input by the user in the sub schedule name field 2703. Add to For example, a sub-schedule “Social gathering” that does not exist in the template sub-schedule management table 110 can be added. When the user selects a sub-schedule in the sub-schedule selection check box 2708 in the sub-schedule name column 2703 and presses the sub-schedule delete button 2712, the screen display processing unit 102 checks the sub-schedule selection from the sub-schedule name column 2703. The secondary schedule selected in box 2708 is deleted.

  In the role column 2704, a template condition ID 501 (see FIG. 5) that matches the key in the template role information management table 112 is used with the template condition ID 401 (see FIG. 4) of the template condition selected from the use template pull-down menu 2702 as a key. The extracted role template role name 503 value is displayed. Specifically, when the template condition is “for explanatory meeting”, the template condition ID is “C002”, and role names of “organizer” and “participant” are displayed.

  When the user presses the add role button 2706, the screen display processing unit 102 displays the name of the role to be added on the screen in a state that can be input by the user, and adds the role input by the user to the role column 2704. To do. For example, a role “observer” that does not exist in the template role information management table 112 can be added. When the user selects a role in the role selection check box 2709 in the role column 2704 and presses the delete role button 2707, the screen display processing unit 102 deletes the role selected in the role selection check box 2709 from the role column 2704. To do.

  The condition field 2705 includes an order designation field 2716 having an order text box 2721, a same day designation field 2717 having a same day designation check box 2722, an adjacent designation field 2718 having an adjacent designation check box 2723, and a requirement having a required time designation text box 2724. A time specification column 2719, an allowable time specification column 2720 (allowable time zone) having an allowable time specification text box 2725, and a type specification column 2726 having a type specification text box 2728 are displayed.

  The user selects a role in the secondary schedule using the secondary schedule assignment check box 2710 in the role column 2704 and designates the order in which the secondary schedule is to be executed in the order text box 2721. At the first display, the values set in the order 305 (see FIG. 3) of the template sub-schedule management table 110 are displayed. In the present embodiment, the position of the main schedule is set to “0”, and a negative value is specified when it is before the start date and time of the main schedule, and a positive value is specified when it is after the end date and time of the main schedule.

  In addition, the user selects whether to set the main schedule and the sub-schedule to the same date using the same day designation check box 2722. When the same day designation check box 2722 is selected, the secondary schedule needs to be executed on the same day as the main schedule, and the value of the attribute is “Y” (see the column of the same day 1006 shown in FIG. 10). If the same day designation check box 2722 is not selected, the secondary schedule does not need to be executed on the same day as the main schedule, and the value of the attribute is “N” (see the column of the same day 1006 shown in FIG. 10). At the first display, the value set on the same day 306 (see FIG. 3) of the template sub-schedule management table 110 is displayed.

  In addition, the user selects whether the secondary schedule is adjacent to the main schedule by the adjacent designation check box 2723. When the adjacent designation check box 2723 is selected, the secondary schedule needs to be adjacent to the main schedule, and the value of the attribute is “Y” (see the column of adjacent 1007 shown in FIG. 10). When the adjacent designation check box 2723 is not selected, the secondary schedule does not need to be adjacent to the main schedule, and the attribute value is “N” (see the column of adjacent 1007 shown in FIG. 10). If the same day specification check box 2722 is not selected, the adjacent specification check box 2723 of the secondary schedule is inactive, and the user cannot select the adjacent specification check box 2723. At the first display, the value set in the adjacent 307 (see FIG. 3) of the template sub-schedule management table 110 is displayed.

  In addition, the user designates the time required for the secondary schedule in the required time designation text box 2724 in minutes. At the first display, the value set in the required time 308 (see FIG. 3) in the template sub-schedule management table 110 is displayed.

  In addition, the user designates a time in which the secondary schedule can be reserved in the allowable time designation text box 2725. In the allowable time designation text box 2725, a reservable time zone can be designated in the form of “start time to end time”, and a plurality of time zones can be designated by separating them with commas. At the first display, the value set in the allowable time 309 (see FIG. 3) of the template sub-schedule management table 110 is displayed.

  Further, the user designates the type of the sub schedule in the type designation text box 2728. At the first display, the value set in the type 310 (see FIG. 3) of the template sub-schedule management table 110 is displayed.

  The OK button 2713 has a function of transmitting the input data to the schedule management apparatus 100. When the user presses the OK button 2713, the value of the input item is confirmed. Thereafter, the schedule adjustment processing unit 103 stores the sub schedule condition setting content in the main storage device 101. When the user presses a cancel button 2714, the value of the input item and the sub schedule condition setting content are canceled, and the screen display processing unit 102 closes the sub schedule condition setting screen 2700.

  FIG. 11 is a diagram illustrating an example of the schedule management table 118. The schedule management table 118 holds all reserved schedules. A user ID 1101 that is an ID for uniquely identifying a participant, a schedule ID 1102 that is an ID for uniquely identifying a schedule, and a related schedule ID 1103 that indicates a schedule ID of a main schedule when the schedule is a secondary schedule, Date 1104 indicating date and time, start time 1105, end time 1106, location 1107 indicating the location where the schedule is held and the destination ID of the travel schedule, schedule name 1108 for display to the user, role in the main schedule Information on reserved schedules such as a role ID 1109 to be shown and a main schedule ID 1110 which is an ID for uniquely identifying the accompanying main schedule is managed.

  The schedule management table 118 contains the schedules that are initially described as separate schedules. When the user makes a schedule reservation for “A product briefing session”, the schedule of the user 1 whose role is the organizer includes “preparation” (sub schedule), “A product briefing session” (main schedule), “cleanup” ( Sub-schedule) and “Social gathering” (sub-schedule) are reserved. Since the place where the main schedule is held is “Higashi Totsuka”, which is the place where the user 1 is working, no schedule for movement is reserved.

  On the other hand, the schedules of the user 2 and the user 3 who are participants include “movement (row)” (sub-schedule), “A product briefing session” (main schedule), “social gathering” (sub-schedule), (Return) ”(sub schedule) is reserved. However, since the user 2 and the user 3 are not organizers, the schedule for “preparation” before the A product briefing and “cleanup” after the A product briefing is not reserved. In addition, the “movement” schedule is the required time calculated from the location information of user 2 and user 3 and the location information of other schedules on the same day in the process of FIG.

  FIG. 28 is a diagram showing an example of a screen 2800 for referring to a schedule registered for each participant. The screen example shown in FIG. 28 is based on a schedule registered in the schedule management table 118. The schedule display screen 2800 is a user interface screen displayed on the display device of the client PC 121 by the screen display processing unit 102 so that the user can refer to the schedule.

  The schedule display screen 2800 includes, for example, a user name 2801, a time area 2802, a schedule display area 2803, a subject name 2804, and a close button 2805. In the user name 2801, the value of the user name 802 (see FIG. 8) of the user information management table 114 is displayed. Time is displayed in the time area 2802, and the user can grasp the start time and end time of the schedule at a glance. The business name 2804 displays a value acquired from the schedule name 1108 of the schedule management table 118 (see FIG. 11) for each schedule. When the user presses a close button 2805, the screen display processing unit 102 closes the schedule display screen 2800.

Next, a process for reserving a schedule will be described.
FIG. 14 is a diagram showing an outline of a processing procedure for reserving a schedule. The schedule reservation process S1400 is a process for registering the main schedule and the sub-schedule in the schedule management table 118 (see FIG. 11). It consists of “Process B” for performing the free time search process S1600 and “Process C” for performing the schedule registration process S1700.

  When the user inputs schedule information via the schedule reservation screen 2600 displayed by the screen display processing unit 102, the schedule adjustment processing unit 103 accepts the schedule reservation based on the input schedule information (step S1401).

  Next, based on the reservation object 2101 of the reservation object list 2100 (see FIG. 21) that is the schedule reservation received in step S1401, the analysis unit 105 analyzes the reservation status, and the schedule reservation processing unit 104 displays the sub-schedule management table. The secondary schedule is registered in 117 (step S1402). In step S1402, the participant ID is added to the main schedule management table 116, and the role ID and role name are added to the role information management table 113 as roles. Process A in step S1500 in which step S1401 and step S1402 are combined will be described later with reference to FIG.

  Next, the analysis unit 105 searches for a vacant time necessary for the schedule reservation received in step S1401, and adds a vacant time candidate to the vacant time candidate object 2400 (see FIG. 24) (step S1600). The process B in step S1600 will be described later with reference to FIG.

  Next, the schedule reservation processing unit 104 receives the processing results of the schedule adjustment processing unit 103 and the analysis unit 105, and registers the main schedule and the sub schedule in the schedule management table 118 (step S1700). The process of registering the main schedule and the sub schedule in the schedule management table 118 in the process C of step S1700 will be described later with reference to FIGS.

  FIG. 15 is a diagram illustrating a processing procedure for generating a necessary sub-schedule object from a reservation object. With reference to FIG. 15, the processing procedure of processing S1500 from schedule reservation reception to sub-schedule registration according to processing A will be described in detail. Process A is a process of registering a sub-schedule in the sub-schedule management table 117, adding a participant ID to the main schedule management table 116, and adding a role to the role information management table 113.

  When the user inputs a condition via the schedule reservation screen 2600 (see FIG. 26) displayed by the screen display processing unit 102, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 displays the reservation object list 2100 (FIG. 21) is received (step S1501).

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 acquires the template condition ID 2106 from the reservation object 2101 of the reservation object list 2100 (step S1502). Specifically, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 acquires “C002” as the template condition ID 2106 from the reservation object 2101 of the reservation object list 2100.

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 creates a secondary schedule object list 2300 and a participant ID list (step S1503). Note that the participant ID list includes only character string information such as “U001”, “U002”, and “U003”.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires one element of the reservation object from the reservation object list 2100 received in step S1501 (step S1504). Specifically, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires the participant object 2103 with the object ID “0001” as the reservation object from the reservation object list 2100 received in step S1501.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires a model role ID and a participant ID from the element of the reservation object acquired in step S1504 (step S1505). Specifically, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires the model role ID 2112 “DROL1” and the participant ID 2109 “U001” from the participant object 2103 of the reservation object acquired in step S1504.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 adds the participant ID acquired in step S1505 to the participant ID list created in advance in step S1503 (step S1506). Specifically, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 adds “U001” as the participant ID acquired in step S1505 to the participant ID list created in step S1503.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 uses the condition information input in advance by the user via the sub-schedule condition setting screen 2700 (see FIG. 27) of the A product briefing session when the main schedule is reserved. The template condition information object 2200 (see FIG. 22) which is the set sub schedule is acquired (step S1507).

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires a list of template role IDs 2203 from the template condition information object 2200 acquired in step S1507 (step S1508).

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 adds the template role ID acquired in step S1505 included in the reserved object element to the list of template role IDs 2203 of the template condition information object 2200 acquired in step S1508. Whether it is included is determined by comparing the template role ID (step S1509).

  Specifically, the template role ID included in each reservation object in which the values of the participant IDs acquired in step S1505 included in the element of the reservation object are “U001”, “U002”, and “U003”, and the step The schedule name of the template condition information object 2200 acquired in S1508 is included in each sub-schedule object of “preparation”, “movement (line)”, “cleaning up”, “movement (returning)”, and “social gathering”. Compare the contents of the template role ID.

  In step S1509, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the template role ID acquired in step S1505 is included in the list of template role IDs acquired in step S1508. The process proceeds to step S1510. On the other hand, if the template role ID acquired in step S1505 is not included in the list of template role IDs acquired in step S1508, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines “No”, and step S1511. Proceed to the process.

  In step S1510, the sub-schedule corresponding to the template role ID and the participant ID acquired in step S1505 is added to the sub-schedule object list 2300 (see FIG. 23) created in advance in step S1503, and the process proceeds to step S1511. This is because the sub-schedule is registered in the schedule of the participant having the template role ID.

  In step S <b> 1511, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether there is an unprocessed next sub-schedule based on the number of remaining sub-schedules. If there is one or more remaining sub-schedules in step S1511, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is a next unprocessed sub-schedule and returns to the process of step S1507. . On the other hand, if the number of remaining sub-schedules is less than one in step S1511, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” because there is no unprocessed sub-schedule, and proceeds to the process of step S1512. .

  In step S1512, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether there is a next reservation object that has not been processed, based on the number of remaining reservation objects. If the number of remaining reservation objects is one or more in step S1512, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is a next unprocessed reservation object and determines “Yes”, and the process of step S1504 Return to.

  On the other hand, if the number of remaining reservation objects is less than 1 in step S1512, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” because there is no unprocessed reservation object, and schedule reservation processing unit In step 104, the process proceeds to step S1513.

  In step S1513, the schedule reservation processing unit 104 adds the participant ID list created in step S1503 and added with the participant ID in step S1506 to the main schedule management table 116. Further, the schedule reservation processing unit 104 also registers the template condition ID 2106 acquired from the reservation object in the reservation object list 2100 in step S1502 in the main schedule management table 116.

  Next, the schedule reservation processing unit 104 additionally registers a secondary schedule in the secondary schedule management table 117 (step S1514). Next, the schedule reservation processing unit 104 performs role information management based on the template condition ID 2202 of the template condition information object 2200, the template role ID 2203, the template condition ID 501, the template role ID 502, and the template role name 503 of the template role information management table 112. The main schedule ID 701, role ID 702, and role name 703, which are role information, are additionally registered in the table 113 (step S1515), and the process A ends.

  FIG. 16 is a diagram illustrating a processing procedure for generating a free time candidate object from the secondary schedule object. The schedule free time search process S1600 of process B will be described in detail with reference to FIG. The process B is a process in which the analysis unit 105 searches for a schedule free time for a required time and adds a free time candidate to the free time candidate object 2400. Specifically, the required time calculation processing unit 107 of the analysis unit 105 calculates the total required time, and the free time analysis processing unit 108 of the analysis unit 105 searches for the schedule free time for the total required time. Also, a free time candidate is added to the free time candidate object 2400 (see FIG. 24).

  Here, the total required time means a time obtained by adding the time of the sub-schedule determined from the attribute value to the required time of the main schedule. For example, when an adjacent attribute is designated in the “preparation” of the sub-schedule of “A product briefing session” on the sub-schedule condition setting screen 2700 shown in FIG. 27, the time required for “preparation” and “A product description” The total time required is the sum of the time required for the “meeting”.

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 sets the total required time as the required time for the main schedule (step S1601). Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 receives the sub-schedule object list 2300 (see FIG. 23) created in the process A (step S1602), and extracts the elements of the sub-schedule object from the sub-schedule object list 2300. One is acquired (step S1603).

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 acquires condition information from the secondary schedule object (step S1604). Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the required time 2310 is “automatic” based on the value of the required time (step S1605).

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the required time value is “automatic” in step S1605, and the required time calculation processing unit 107 of the analysis unit 105 performs the process of step S1606. move on. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the required time value is “30 minutes” or “120 minutes” other than “automatic” in step S1605, and step S1610. Proceed to the process.

  In step S1606, when the required time calculation processing unit 107 of the analysis unit 105 has a value of “automatic”, the base information management table 115 that is the user working place 803 of the user information management table 114 (see FIG. 8). The base name corresponding to the base ID 901 of the base information management table 115 is acquired based on the base ID 901 of the base information management table 115 (see FIG. 9) and the base ID 901 of the base information management table 115 which is the location 1107 of the schedule management table 118 (see FIG. 11). Based on the two base names, the required time is calculated in cooperation with an existing train time search system.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the required time is longer than “0 minutes” based on the value of the required time calculated in step S1606 (step S1607). The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the required time exceeds “0 minutes” in step S1607, such as “30 minutes” or “120 minutes”, and performs the processing of step S1608. move on. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the required time is “0 minutes” or less in step S1607, and proceeds to the process of step S1609.

  In step S1608, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 stores the required time exceeding “0 minutes” calculated in step S1606 in the sub-schedule calculation time of the sub-schedule object list 2300, and the process proceeds to step S1610. move on. Specifically, the value is stored in the calculation time of the element 2305 whose object ID is “0002”.

  In step S1609, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 deletes from the sub-schedule object list 2300 the elements of the sub-schedule object having the required time equal to or less than “0 minutes” calculated in step S1606. This is because the time required for the secondary schedule is “0 minutes” or less, and the secondary schedule need not be executed.

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the same day attribute is “Y” based on the value of the same day 2308 of the secondary schedule object 2301 (step S1610).

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the value of the same day attribute is “Y” in step S1610, and proceeds to the process of step S1611. On the other hand, if the same day attribute value is not “Y” in step S1610, the sub schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” and proceeds to the process of step S1613.

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the adjacent attribute is “Y” based on the value of the adjacent 2309 of the secondary schedule object 2301 (step S1611).

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the value of the adjacent attribute is “Y” in step S <b> 1611, and proceeds to the process of step S <b> 1612. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the value of the adjacent attribute is not “Y” in step S1611, and proceeds to the process of step S1613.

  In step S1612, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 adds the required time of the sub-schedule to the total required time. If the calculation time has already been stored in the secondary schedule object 2301 in step S1608, the calculation time is added to the total required time. Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether there is an unprocessed next sub-schedule based on the number of remaining sub-schedules (step S1613).

  If the number of remaining sub-schedules is one or more in step S1613, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is a next unprocessed sub-schedule and determines “Yes”, and the process of step S1604 Return to. On the other hand, if the number of remaining sub-schedules is less than 1 in step S1613, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is no unprocessed sub-schedule and determines “No”. The time analysis processing unit 108 proceeds to the process of step S1614.

  In step S1614, the free time analysis processing unit 108 of the analysis unit 105 searches for free time for the entire required time. The free time analysis processing unit 108 includes a schedule in which the user ID 1101 of the schedule management table 118 is included in the participant ID list created in process A, and the date 1104 of the schedule management table 118 is in the range of the specified date 2104 of the reserved object list 2100. To get. Then, the time obtained by removing the end time 1106 from the start time 1105 of the acquired schedule is set as a free time. However, the free time is searched so that the time frame for the sub-schedule of the total required time is within the allowable time of the sub-schedule object list 2300.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 adds the free time (free time 1, free time 2, etc.) searched in step S1614 to the free time candidate object 2400 (see FIG. 24) (step S1615). ), The process B ends.

  FIG. 17 is a diagram showing an outline of a processing procedure for registering a schedule. Referring to FIG. 17, for process C, the schedule adjustment processing unit 103 adjusts the main schedule and the sub-schedule based on the available time candidates obtained by the analysis unit 105, and the schedule reservation processing unit 104 uses the schedule management table. A process of registering in 118 (see FIG. 11) will be described.

  The free time analysis processing unit 108 of the analysis unit 105 acquires free time for main schedule reservation common to all participants from the free time candidate object 2400 (step S1701).

  Next, the schedule adjustment processing unit 103 determines the date, start time, and end time for reserving the main schedule from the common free time for main schedule reservation common to all the participants acquired in step S1701 (step S1702). .

  Next, the schedule reservation processing unit 104 registers the main schedule in the schedule management table 118 for all participants from the date, start time, and end time for reserving the main schedule determined in step S1702 (step S1703). .

  Next, the schedule reservation processing unit 104 executes a sub-schedule registration process (step S1704) and ends the process C schedule registration. The sub-schedule registration process of process C will be described with reference to FIG.

  FIG. 18 is a diagram illustrating a processing procedure for determining the date and time of the secondary schedule and registering the secondary schedule. FIG. 18 is a detailed processing procedure of the sub-schedule registration processing S1704. The schedule adjustment processing unit 103 adjusts the sub-schedule based on the available time candidates obtained by the analysis unit 105, and the schedule reservation processing unit 104 A process of registering in the schedule management table 118 (see FIG. 11) will be described.

  The secondary schedule condition analysis processing unit 106 of the analysis unit 105 acquires one element of the secondary schedule object from the secondary schedule object list 2300 (see FIG. 23) (step S1801).

  Next, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 acquires condition information from the elements of the secondary schedule object 2301 acquired in step S1801 (step S1802). Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the value of the required time is “automatic” based on the condition information acquired in step S1802 (step S1803).

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when the value of the required time is “automatic” in step S1803, and proceeds to the process of step S1804. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the required time value is “30 minutes” or “120 minutes” other than “automatic” in step S1803. Proceed to processing.

  In step S1804, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether it is a movement schedule from the condition information acquired in step S1802. Specifically, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether it is a movement schedule from the type 2312 of the sub-schedule element object 2304 acquired in step S1802.

  If the type is “move” in step S1804, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes”, and the process proceeds to step S1805. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the type is “preparation” or “cleanup” other than “move” in step S1804, and the process proceeds to step S1814.

  In step S1805, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 acquires the other schedule of the same day from the schedule management table 118, and determines the other schedule of the same day. The details of the other schedule determination process for the same day are as follows.

  If the order 2307 of the sub-schedule element object 2304, which is the condition information acquired in step S1802, is a value smaller than “0”, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 registers the main schedule for process C. Other schedules on the same day that are closest to the start time of the main schedule determined in step S1702 are acquired. When the order 2307 of the sub-schedule element object 2304, which is the condition information acquired in step S1802, is a value greater than “0”, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 registers the main schedule for process C. The other schedule of the same day closest after the end time of the main schedule determined in step S1702 is acquired. Then, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether there is another schedule on the same day.

  In step S1805, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when there is another schedule on the same day, and the process proceeds to step S1806. If there is no other schedule on the same day, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” and proceeds to the process of step S1814.

  In step S1806, the required time calculation processing unit 107 of the analysis unit 105 calculates the required time from other schedule locations on the same day. Details of the process for calculating the required time from other schedule locations on the same day are as follows.

  The base information management table based on the contents of the base ID 901 of the base information management table 115 that is the other schedule location on the same day and the contents of the base ID 901 of the base information management table 115 that is the main schedule location 1107 of the schedule management table 118 The base name corresponding to 115 base ID 901 is acquired, the required time is calculated in cooperation with an existing train time search system based on the two base names, and the calculated time is stored in the memory.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the required time is longer than “0 minutes” based on the value of the required time calculated in step S1806 (step S1814). The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” if the required time exceeds “0 minutes” in step S1814, such as “30 minutes” or “120 minutes”, and performs the processing in step S1807. move on. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when the required time is “0 minutes” or less in step S1814, and proceeds to the process of step S1813. If the place 1107 in the schedule management table 118 is the same as the place 2105 in the reserved object list 2100 where the main schedule is held, the time calculated in step S1806 is “0 minutes” or less, and the sub-schedule This is because there is no need to execute.

  In step S1807, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 stores the time calculated in step S1806 in the required time. Also, it is determined as “No” in step S1804, and when the required time is “automatic” but not the movement schedule, it is determined as “No” in step S1805 and the required time is “automatic”. If there is no schedule, the calculated time stored in advance in the secondary schedule object 2301 is set as the required time.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the sub-schedule is before or after the main schedule from the order value of the condition information acquired in step S1802 (step S1808). ).

  The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” in the case where the order is a value larger than “0” in step S1808, specifically, “movement (return)” of “3” or the like. The free time analysis processing unit 108 of the analysis unit 105 proceeds to the process of step S1810. On the other hand, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” in the case where the order attribute is a value of “0” or less in step S1808, specifically, “move (row)” of “−2”. ”And the process proceeds to step S1809.

  In step S1809, the free time analysis processing unit 108 of the analysis unit 105 searches for a free time within the allowable time zone before the main schedule from the time required for the sub-schedule, and proceeds to step S1811.

  In step S1810, the free time analysis processing unit 108 of the analysis unit 105 searches for free time within the allowable time zone after the main schedule from the time required for the sub-schedule, and proceeds to step S1811.

  In step S1811, the schedule adjustment processing unit 103 determines the sub-schedule from the free time in the allowable time zone before the main schedule searched in step S1809 or the free time in the allowable time zone after the main schedule searched in step S1810. Determine the date, start time, and end time.

  Next, the schedule reservation processing unit 104 registers the sub-schedule in the schedule management table 118 from the sub-schedule date, start time, and end time determined in step S1811 (step S1812).

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether there is an unprocessed next sub-schedule based on the number of remaining sub-schedules (step S1813). If the number of remaining sub-schedules is one or more in step S1813, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is a next unprocessed sub-schedule and determines “Yes”, and the process of step S1801 Return to. On the other hand, if the number of remaining sub-schedules is less than one in step S1813, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that there is no unprocessed sub-schedule and determines “No”. End schedule registration.

Next, a process for changing a schedule reservation will be described.
When the user needs to change the schedule reservation on the main screen 3200 for schedule reservation shown in FIG. 32, when the “change schedule” button 3202 is pressed, the schedule change screen 2900 is displayed on the client PC 121. Displayed on the device.

  FIG. 29 is a diagram showing an example of a screen for changing the content of the schedule “A product briefing session”. A method of changing the preconditions of the registered main schedule and the sub-schedule conditions of the main schedule will be described with reference to FIG.

  A schedule change screen 2900 is a user interface screen displayed on the display device of the client PC 121 by the screen display processing unit 102 in order for the user to change the schedule. The user inputs a schedule item in the item text box 2907 of the item 2901, a date to reserve the schedule in the date text box 2908 of the date 2902, a start time and an end time text of the schedule in the start time text box 2909 of the time 2903 In the box 2910, the schedule end time is specified, and the location where the schedule is to be executed is specified by the location pull-down menu 2911 of the location 2904, and the information of the registered schedule is changed. The location pull-down menu 2911 displays the location name 902 of the location information management table 115. For a schedule that has already been registered, when the schedule adjustment processing unit 103 receives, for example, “A product briefing session”, the registered information can be displayed using the schedule management table 118.

  When the user selects a template to be used on the sub schedule condition setting screen 2700A (see FIG. 30) displayed by pressing the condition setting button 2913, the screen display processing unit 102 displays the template condition text box of the template 2905. In 2912, the name of the selected template condition is set.

  When the user presses the add user button 2918, the screen display processing unit 102 displays a user designation screen that can designate a participant who reserves the schedule, and the user name of the participant selected by the user is the user of the participant 2906. The line displayed in the name area 2915 is added.

  The role pull-down menu 2917 of the role area 2916 of the participant 2906 area is displayed in the role column 2704 of the sub-schedule condition setting screen 2700A (see FIG. 30) displayed by pressing the condition setting button 2913. Display the name. The user designates a role to the participant added to the area of the participant 2906 using the role pull-down menu 2917.

  In addition, the user can delete a participant from the area of the participant 2906 by selecting the participant with the user selection check box 2914 in the area of the participant 2906 and pressing a user deletion button 2919. The change button 2920 has a function of transmitting the input data to the schedule management apparatus 100. When the user presses the change button 2920, the input data is determined, and the main schedule management table 116 and the schedule management table are confirmed. The schedule information registered in 118 is changed. When the user presses a cancel button 2921, the data input so far is canceled, and the screen display processing unit 102 closes the schedule change screen 2900.

  FIG. 19 is a diagram illustrating a processing procedure when the time of the main schedule is changed. The process in which the schedule adjustment process part 103 changes the time of the main schedule of the schedule management table 118 is demonstrated using FIG. Reference is made to FIG. 29 as appropriate. In this process, only the time of the main schedule is changed.

  When the user inputs information different from existing information in the start time text box 2909 and end time text box 2910 of time 2903 via the schedule change screen 2900 and presses the change button 2920, the schedule adjustment processing unit 103 The main schedule time change request is accepted (step S1901).

  Specifically, the user changes from “16:00” to “10:00” in the start time text box 2909 at time 2903 of the schedule change screen 2900, and “18:00” to “12” in the end time text box 2910. : 0 ". When the user presses the change button 2920, the schedule adjustment processing unit 103 receives a change request for changing the start time of the main schedule ID “MS001” to “10:00” and the end time to “12:00”.

  On the schedule change screen 2900, not only the time 2903 but also the user changes the schedule name of the main schedule in the business text box 2907, changes the main schedule date in the date text box 2908, the start time text box 2909 and In the end time text box 2910, change the main schedule holding time, change the place where the main schedule is held in the place pull-down menu 2911, press the condition setting button 2913, change the sub-schedule condition setting, press the user addition button 2918 Add main schedule participant, select user selection check box 2914, press user delete button 2919 to delete main schedule participant, change role of participant selected in role pull-down menu 2917 Ukoto is also possible. When the user changes an item to be changed and the change button 2920 is pressed, the schedule adjustment processing unit 103 can similarly accept a schedule change request.

  Next, the schedule adjustment processing unit 103 acquires the main schedule ID of the schedule to be changed (step S1902). Specifically, the schedule adjustment processing unit 103 acquires “MS001” that is the main schedule ID held in the memory when the screen display processing unit 102 displays the schedule change screen 2900.

  Next, the schedule adjustment processing unit 103 selects the secondary schedule corresponding to the primary schedule ID from the secondary schedule management table 117, and the user ID and role ID specified by the participant 2906 of the schedule change screen 2900 from the screen display processing unit 102. And the secondary schedule object list 2300 is created (step S1903). Specifically, the schedule adjustment processing unit 103 refers to the main schedule ID 1001 of the sub-schedule management table 117, extracts the sub-schedule corresponding to the main schedule ID acquired in step S1902, and performs step S1503 of the schedule registration process. Similarly, for each user ID designated as the participant 2906 on the schedule change screen 2900, a sub-schedule object list 2300 is created based on the role ID and sub-schedule assigned to the user ID.

  This time, it is assumed that the user has not pressed the condition setting button 2913, and information is acquired from the sub-schedule management table 117. However, the user presses the condition setting button 2913 to display the sub-schedule condition setting screen 2700. Is displayed, the schedule adjustment processing unit 103 extracts the secondary schedule object list 2300 from the secondary schedule condition setting screen 2700 and creates it.

  Next, the schedule adjustment processing unit 103 acquires a participant ID list designated by the participant 2906 on the schedule change screen 2900 (step S1904). Note that the participant ID list includes only character string information such as “U001”, “U002”, and “U003”.

  Next, the schedule adjustment processing unit 103 acquires one element (for example, “U001”) of the participant ID list acquired in step S1904 (step S1905), and the participation acquired in step S1905 from the schedule change screen 2900. A role ID corresponding to the person ID is acquired (step S1906). Specifically, the role corresponding to the participant ID of “U001” is “sponsor”, and the role ID is “ROL1”.

  Next, the schedule reservation processing unit 104 matches the value of the main schedule ID 1110 in the schedule management table 118 and the main schedule ID acquired in step S1902, and the value of the user ID 1101 in the schedule management table 118 acquired in step S1905. The value of the schedule ID 1102 of the schedule management table 118 of the line that matches the ID is acquired, and the line that matches the value of the related schedule ID 1103 of the schedule management table 118 is deleted from the schedule management table 118 (step S1907). Specifically, the value of the main schedule ID 1110 is “MS001”, and the schedule ID of the row where the value of the user ID 1101 matches “U001” is “S001”. Then, the schedule reservation processing unit 104 deletes the row (schedule ID 1102 is “S002”, “S003”, “S004”) in which the value of the related schedule ID 1103 matches “S001” from the schedule management table 118.

  Next, the schedule reservation processing unit 104 performs sub-schedule registration processing (step S1704). Specifically, the secondary schedule object 2301 is analyzed from the secondary schedule object list 2300 created in step S1904, the participant ID acquired in step S1905, and the role ID acquired in step S1906, and the corresponding participant is analyzed. Re-register the secondary schedule. The sub-schedule registration process is the same as the flowchart 1704 shown in the sub-schedule registration of the process C, and details are as described above.

  Next, the schedule reservation processing unit 104 sets the row in which the value of the main schedule ID 1110 in the schedule management table 118 matches the main schedule ID acquired in step S1902 and the value of the user ID 1101 matches the participant ID acquired in step S1905. The values of the start time 1105 and the end time 1106 are changed to the values of the start time and end time received in step S1901 (step S1908). Specifically, the row with the main schedule ID 1110 value “MS001” and the user ID 1101 value “U001” is the row with the schedule ID 1102 “S001”, and the start time 1105 is “16:00”. The end time 1106 is changed from “18:00” to “12:00” from “10:00” to “10:00”.

  Next, the schedule adjustment processing unit 103 determines whether there is an unprocessed participant ID in the participant ID list acquired in the unprocessed step S1904 based on the number of remaining participant IDs (step S1909).

  If the number of remaining participant IDs is 1 or more in step S1909, the schedule adjustment processing unit 103 determines that there is an unprocessed next participant ID, and returns to step S1905. On the other hand, if the number of remaining participant IDs is less than 1 in step S1909, the schedule adjustment processing unit 103 determines that there is no unprocessed participant ID and determines “No”, and ends the time change processing of the main schedule. . The schedule management table 118 in FIG. 13 shows the result of executing the above main schedule time change processing.

  FIG. 20 is a diagram illustrating a processing procedure when the sub-schedule condition is changed. The sub-schedule condition changing process for changing the sub-schedule condition of a certain main schedule will be described with reference to FIG. When the user presses the condition setting button 2913 on the schedule change screen 2900 (see FIG. 29) to change the conditions on the sub-schedule condition setting screen 2700 and then presses the change button 2920, the schedule adjustment processing unit 103 receives a request for changing the condition information from the input condition (step S2001).

  Next, the schedule adjustment processing unit 103 acquires the main schedule ID from the schedule change screen 2900 (step S2002). Specifically, the schedule adjustment processing unit 103 acquires “MS001” that is the main schedule ID held in the memory when the screen display processing unit 102 displays the schedule change screen 2900.

  Next, the schedule adjustment processing unit 103 acquires the condition information that the screen display processing unit 102 holds on the memory. Then, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the role information of the condition information has been added or deleted (step S2003). If the role information has been changed (added or deleted), the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” and proceeds to the process of step S2004. If there is no change in the role information, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines “No”, and proceeds to the process of step S2008.

  In step S2004, when the role information is deleted in the change of the role information in step S2003, the schedule adjustment processing unit 103 displays the deleted role ID held in the memory by the screen display processing unit 102. Acquired and deletes the row in which the role ID 702 matches the corresponding role ID and the main schedule ID 701 matches the main schedule ID acquired in step S2002 from the role information management table 113 (see FIG. 7). Similarly, the schedule adjustment processing unit 103 adds new role information to the role information management table 113 when role information is added in the change of role information in step S2003.

  Next, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether role information has been added (step S2005). If the role information has been added, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” and proceeds to the process of step S2006. If the role has not been added, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” and proceeds to the process of step S2008.

  In step S2006, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the sub-schedule is assigned to the added role information, and the condition information that the screen display processing unit 102 holds in the memory. Judgment from. Whether or not a sub-schedule is assigned to the added role information is determined based on whether or not the sub-schedule assignment check box 2710 for a new role added to the role column 2704 of the sub-schedule condition setting screen 2700 is selected. To do.

  If the sub-schedule assignment check box 2710 is selected, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” by assigning a role in the sub-schedule, and the schedule adjustment processing unit 103 performs step. The process proceeds to S2007. If the sub-schedule assignment check box 2710 is not selected, it is determined that the role in the sub-schedule is not assigned, and “No” is determined, and the process proceeds to step S2008.

  In step S2007, the schedule adjustment processing unit 103 adds the newly added role information to the secondary schedule management table 117, and updates the secondary schedule management table 117. Specifically, the schedule ID of the secondary schedule in which the new role is assigned to the secondary schedule is acquired from the condition information held in the memory by the screen display processing unit 102, and the secondary schedule ID 1002 of the secondary schedule management table 117 is acquired. And the value of the role ID 702 added to the role information management table 113 in step S2004 is added to the role ID 1004 in the row where the value of the main schedule ID 1001 matches the main schedule ID acquired in step S2002. The management table 117 is updated.

  In step S2008, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether a sub-schedule has been added or deleted. The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “Yes” when a new sub-schedule is added or an existing sub-schedule is deleted, and the schedule adjustment processing unit 103 performs the process of step S2009. Proceed to The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” when a new sub-schedule has been added or an existing sub-schedule has not been deleted, and the process proceeds to step S2010.

  In step S2009, the schedule adjustment processing unit 103 updates (adds or deletes) the sub-schedule information in the sub-schedule management table 117, and proceeds to step S2010. Specifically, when there is an added sub-schedule that the screen display processing unit 102 holds in the memory, the schedule adjustment processing unit 103 stores the value of the main schedule ID acquired in step S2002 and the memory. A row is added to the secondary schedule management table 117 from the held condition information. If there is deleted schedule information held in the memory by the screen display processing unit 102, the schedule adjustment processing unit 103 uses the main schedule ID 1001 of the secondary schedule management table 117 acquired in step S2002. The row that matches the ID value and the sub-schedule ID 1002 of the sub-schedule management table 117 matches the ID of the deleted sub-schedule held in the memory is deleted from the sub-schedule management table 117.

  In step S2010, the sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines whether the condition information has been changed. The sub-schedule condition analysis processing unit 106 of the analysis unit 105 determines that “order”, “same day”, “adjacent”, etc., which are the condition information stored in the memory by the screen display processing unit 102, are changed to “ The schedule adjustment processing unit 103 proceeds to the process of step S2011. If there is no change in the condition information, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 determines “No” and ends the secondary schedule condition change process.

  In step S <b> 2011, the schedule adjustment processing unit 103 determines the order 1005 of the secondary schedule management table 117, the same day 1006, the adjacent 1007, the required time 1008, and the allowable time 1009 from the condition information held in the memory by the screen display processing unit 102. Then, the value of the type 1010 is changed, and the series of processes is terminated.

Next, a method for updating the secondary schedule management table will be described.
FIG. 30 is a diagram illustrating an example of a screen when the sub-schedule condition information “order” of the schedule “A product briefing session” is changed. The sub-schedule condition setting screen 2700A shown in FIG. 30 is different from the sub-schedule condition setting screen 2700 shown in FIG. Initially, the sub-schedule is registered in the order of movement (line), preparation, cleanup, social gathering, movement (return), but the user can move (line), preparation, social gathering, cleanup, movement ( (Return) in order. That is, the schedule is changed so that it is not cleaned immediately after the A product briefing session, but is cleaned after the social gathering.

  An example of changing the order attribute of “cleaning up” and “social gathering” will be described in detail. The schedule adjustment processing unit 103 acquires the schedule ID “DS003” corresponding to the sub-schedule “cleaning up” from the information stored in the memory by the screen display processing unit 102, and the value “ 2 ”is acquired. Then, the schedule adjustment processing unit 103 matches the main schedule ID “MS001” acquired in step S2002 in the secondary schedule management table 117 and the secondary schedule ID 1002 in the secondary schedule management table 117 matches “DS003”. The row order 1005 is changed from “1” to “2”.

  Also, the schedule adjustment processing unit 103 acquires the schedule ID “DS005” corresponding to the sub-schedule “Social gathering” from the information stored in the memory by the screen display processing unit 102, and the order text box that is the change point The value “1” is acquired. Then, the schedule adjustment processing unit 103 matches the main schedule ID “MS001” acquired in step S2002 in the sub-schedule management table 117 and the sub-schedule ID 1002 in the sub-schedule management table 117 matches “DS005”. The row order 1005 is changed from “2” to “1”. Thereafter, the secondary schedule condition analysis processing unit 106 of the analysis unit 105 ends the secondary schedule condition change processing. The result of executing the example of the secondary schedule condition changing process is shown in the secondary schedule management table 117 of FIG.

  In addition, after the user adds or deletes a role, adds or deletes a secondary schedule, assigns a secondary schedule for a new role, or changes condition information on the secondary schedule condition setting screen 2700A, the user presses an OK button 2713 to If the role is reset in the role area 2916 of the change screen 2900 and the change button 2920 is pressed, the sub-schedule of each participant needs to be readjusted in addition to the sub-schedule condition change processing shown in the flowchart of FIG. It becomes.

Next, the various objects described above will be described in detail.
FIG. 21 is a diagram showing an example of a reserved object list 2100 created on the main storage device 101 by the schedule adjustment processing unit 103. The reservation object list 2100 is a list of reservation objects 2101, and the reservation object 2101 includes a reservation object header 2102 and a participant object 2103. The reservation object header 2102 includes a designated date 2104 that is a reservation period, a place 2105 where a reservation object schedule is held, a template condition ID 2106 that is a condition template used when creating a reservation, and a time required for reservation. Time 2107 is set.

  The participant object 2103 includes an object ID 2108 that is an ID for uniquely identifying the participant object, a participant ID 2109 that is an ID for uniquely identifying the participant, a user name 2110 that is the name of the participant, A location ID 2111, which is an ID for uniquely identifying a person's working location, and a model role ID 2112, which is an ID for uniquely identifying the role of a participant in a reservation, are set.

  FIG. 22 is a diagram illustrating an example of a template condition information object 2200 created on the main storage device 101 by the schedule adjustment processing unit 103. The template condition information object 2200 is a list of template condition information 2201. The template condition information 2201 is a template condition ID 2202 that is an ID for uniquely identifying the template condition of the sub-schedule and the template role possessed by the template condition. Is composed of a template role ID 2203 which is an ID for uniquely identifying the sub schedule condition information object 2204.

  The sub-schedule condition information object 2204 includes an object ID 2205 that is an ID for uniquely identifying the sub-schedule condition information object 2204, a schedule name 2206 that is the name of the sub-schedule condition information object 2204, and a sub-schedule condition information object 2204. A model role ID 2207 indicating a role to be performed, an order 2208 in which the secondary schedule condition information object 2204 is arranged, the same date 2209 indicating whether the secondary schedule condition information object 2204 has the same date as the reservation object 2101, and a continuous time with the reservation object 2101 Adjacent 2210 indicating whether to make a reservation, required time 2211 which is the time required for the secondary schedule condition information object 2204, and the secondary schedule condition information object Permissible time 2212 is the time that can be reserved for the defect 2204, type 2213 indicating the type of sub-schedule condition information object 2204 is set.

  FIG. 23 is a diagram showing an example of the secondary schedule object list 2300 created on the main storage device 101 by the secondary schedule condition analysis processing unit 106. The sub-schedule object list 2300 is a list of sub-schedule objects 2301. The sub-schedule object 2301 is a user ID 2302 that is an ID for uniquely identifying a participant who is a target of the sub-schedule to be reserved and a sub-schedule element object. 2304.

  The sub-schedule element object 2304 includes an object ID 2305 that is an ID for uniquely identifying the sub-schedule element object, a schedule name 2306 that is the name of the sub-schedule element object 2304, and a sub-schedule element object 2304. A certain order 2307, the same date 2308 indicating whether the reservation object 2101 is the same date, an adjacent 2309 indicating whether the reservation object 2101 is reserved at a continuous time, a required time 2310 which is a time required for the element object 2304 of the secondary schedule, When the allowable time 2311 that is the time when the element object 2304 of the secondary schedule can be reserved, the type 2312 that indicates the type of the element object 2304 of the secondary schedule, and the required time 2310 are “automatic” , Calculated time 2313 is set.

  FIG. 24 is a diagram illustrating an example of a free time candidate object 2400 created on the main storage device 101 by the free time analysis processing unit 108. The available time candidate object 2400 is a list of available time candidate objects 2401, and the available time candidate object 2401 includes an available time candidate object header 2409 and an available time candidate element object 2405.

  The free time candidate object header 2409 is a time obtained by adding the time of the sub-schedule that is determined based on the attribute value to the time required for the designated date 2402 and the reservation object 2101 for searching for a free time candidate. A total required time 2403 and a required time 2404 that is a time required for the reservation object 2101 are set.

  The free time candidate element object 2405 includes an object ID 2406 that is an ID for uniquely identifying the free time candidate element object 2405, a user ID 2407 that is an ID for uniquely identifying a participant, and the free time of the participant. When the vacant time 2408 is set and there are a plurality of vacant times 2408 for the participant, the vacant time 1, the vacant time 2, and the vacant time 3 are set in a list.

  To summarize the present embodiment, the storage device 109 of the schedule management device 100 (schedule adjustment support device) executes the main schedule type (for example, template condition ID) in which a plurality of participants participate and the main schedule. One or more required sub-schedules and a template sub-schedule management table 110 for managing the role to be executed for each sub-schedule and condition information are stored. When the user inputs condition information including the desired date and time of the main schedule, the type of the main schedule, the participants and the roles of the participants, the schedule management apparatus 100 determines the template sub-schedule management table specified from the input condition information. Based on 110, the sub-schedule corresponding to the roles of a plurality of participants and the inputted main schedule can be reserved and registered by searching for free time in the schedule management table 118.

  The template sub-schedule management table 110 (model sub-schedule management information) is adjacent to the main schedule and the same day information (for example, the same day 306 in FIG. 3) indicating whether the sub schedule should be executed on the same day as the main schedule. Adjacent information (for example, adjacent 307 in FIG. 3) and allowable time zone information (for example, allowable time 309 in FIG. 3) that is a time zone in which the secondary schedule can be reserved. Therefore, the sub-schedule condition analysis processing unit 106 determines the time required for the main schedule and the main schedule when the same day is specified from the same-day information and the adjacent is specified from the adjacent information based on the template sub-schedule management information. The total required time is calculated by adding the required time of the sub-schedule in which the adjacency is specified to the schedule, and the free time analysis processing unit 108 calculates the free time of the calculated total required time on the same day as the main schedule. It can be extracted from management information.

  The schedule reservation screen displayed on the client PC 121 by the screen display processing unit 102 has a condition setting button for calling an edit screen for editing the definition contents of the template sub-schedule management information. Therefore, the user can edit the template sub schedule management information.

  When the screen display processing unit 102 accepts the change of the date and time of the main schedule, the free time analysis processing unit 108 determines the required time of the main schedule and the required time of the sub schedule from the schedule management information according to the changed date and time. It can be extracted again.

  When the sub-schedule is a movement schedule, the required time calculation processing unit 107 determines the time required for the sub-schedule in consideration of the enrollment location of the participant registered in the schedule management information and the holding place of the main schedule. Can be calculated.

This embodiment has the following features.
(1) The role of the participant including the organizer is set in the template sub-schedule management table 110. When the role of the participant is designated when the main schedule is reserved and registered, a plurality of participants are assigned. A sub-schedule can be reserved according to the role of the participant. That is, the template sub-schedule can be set for each role, and an appropriate sub-schedule can be registered for each role according to the role of the participant (participant) of the main schedule.
(2) By changing the roles of the attendees of the main schedule, it is possible to recreate and readjust the necessary sub-schedules for each participant. An increase in the template sub-schedule management table 110 that is a template condition pattern can also be suppressed.
(3) In the template sub-schedule management table 110, the attribute of the same day 306 (whether it should be the same day), the attribute of the adjacent 307 (whether it must be adjacent to the main schedule), the attribute of the allowable time 309 ( The schedule can be reserved), and it is possible to effectively use idle time instead of fixed time specification. For example, the sub-schedule can be changed within a range of conditions within the day or within the time period. Specifically, if the main schedule meeting is in the morning and a luncheon is scheduled after the meeting, if the meeting is scheduled for the evening, it may be reset as a dinner or social gathering after the meeting. it can.
(4) The schedule management apparatus 100 (schedule adjustment support apparatus) can also consider an existing schedule (other schedule) of a user who is a participant. For example, when reserving a travel schedule, the schedule is the same before and after the schedule. If there is a schedule to be held at the place, the travel schedule becomes unnecessary. In addition, the required time can be changed in consideration of the attendee's working place and holding place.

100 Schedule management device (schedule adjustment support device)
DESCRIPTION OF SYMBOLS 101 Main storage device 102 Screen display process part 103 Schedule adjustment process part 104 Schedule reservation process part 105 Analysis part 106 Sub schedule condition analysis process part 107 Required time calculation process part 108 Free time analysis process part 109 Storage apparatus 110 Model sub schedule management table (Template sub-schedule management information)
111 Template Condition Information Management Table 112 Template Role Information Management Table 113 Role Information Management Table 114 User Information Management Table 115 Site Information Management Table 116 Main Schedule Management Table 117 Sub Schedule Management Table 118 Schedule Management Table (Schedule Management Information)
119 CPU
120 Network 121 Client PC
303 Template condition ID (main schedule type)

Claims (13)

A schedule adjustment support device that adjusts and reserves schedules of a plurality of participants,
One or more sub-schedules necessary for executing the main schedule for each type of the main schedule in which the plurality of persons participate, a role to execute the sub-schedule for each sub-schedule, and a template sub for managing condition information A storage device for storing schedule management information and schedule management information for managing a reservation status of the participant's schedule;
In order to reserve the main schedule, to input condition information including an allowable date and time in which the main schedule can be executed, a time required for the main schedule, a type of the main schedule, and the roles of the participants and the participants A screen display processing unit for displaying
The template sub-schedule management information is identified from the input condition information, and based on the identified template sub-schedule management information, the input participant's role is used as a key A sub-schedule condition analysis processing unit for analyzing the association with the sub-schedule;
A required time calculation processing unit for calculating a required time of the sub-schedule necessary for executing the sub-schedule from the template sub-schedule management information and the schedule management information;
From the schedule management information, a free time analysis processing unit that analyzes a free time of a required time of the main schedule and a required time of the sub schedule within an allowable date and time zone of the main schedule,
A schedule adjustment processing unit for adjusting the main schedule and the sub-schedules of the plurality of participants based on the free time analyzed by the free time analysis processing unit;
A schedule adjustment support device, comprising: a schedule reservation processing unit that reserves and registers the main schedule and the sub-schedule adjusted by the schedule adjustment processing unit in the schedule management information. The template sub-schedule management information is for each sub-schedule,
Same-day information that should be implemented on the same day as the main schedule;
Neighbor information about what should be performed adjacent to the main schedule;
The schedule adjustment support apparatus according to claim 1, further comprising: allowable time zone information that is a time zone in which the sub-schedule can be reserved. The sub-schedule condition analysis processing unit, based on the template sub-schedule management information, when the same day is specified from the same-day information and the adjacent is specified from the adjacent information, Calculate the total required time by adding the required time of the secondary schedule that is adjacent to the main schedule,
3. The schedule adjustment support according to claim 2, wherein the free time analysis processing unit extracts free time of the calculated total required time from the schedule management information on the same day as the main schedule. apparatus. In the schedule reservation screen displayed on the client by the screen display processing unit,
The schedule adjustment support apparatus according to claim 1, further comprising: a condition setting button for calling an edit screen for editing the definition contents of the template sub-schedule management information. When the screen display processing unit accepts the change of the date and time of the main schedule,
The free time analysis processing unit re-extracts the time required for the main schedule and the time required for the sub-schedule from the schedule management information again according to the changed date and time. The schedule adjustment support apparatus described. The required time calculation processing unit, when the sub-schedule is a movement schedule,
2. The schedule according to claim 1, wherein the time required for the sub-schedule is calculated in consideration of the enrollment location of the participant registered in the schedule management information and the location where the main schedule is held. Adjustment support device. A schedule reservation method for reserving a schedule using a schedule management device for managing a schedule of a plurality of participants,
In the storage device, one or more sub-schedules necessary for executing the main schedule for each type of main schedule in which the plurality of names participate, and role and condition information for executing the sub-schedule for each sub-schedule Template sub-schedule management information for managing the schedule and schedule management information for managing the reservation status of the schedule of the participants,
The screen display processing unit includes an allowable date and time zone in which the main schedule can be implemented, a time required for the main schedule, a type of the main schedule, the participants, and the roles of the participants for the reservation of the main schedule Display the screen to input the condition information,
The sub-schedule condition analysis processing unit identifies the template sub-schedule management information from the input condition information, and based on the specified template sub-schedule management information, the role of the input participant as a key , Analyze the association between the entered participant and the secondary schedule,
The required time calculation processing unit calculates a required time of the sub-schedule necessary for executing the sub-schedule from the template sub-schedule management information and the schedule management information,
The free time analysis processing unit analyzes the free time of the required time of the main schedule and the required time of the sub schedule within the allowable date and time zone of the main schedule from the schedule management information,
The schedule adjustment processing unit adjusts the main schedule and the sub-schedules of the plurality of participants based on the free time analyzed in the free time analysis process,
The schedule reservation processing unit reserves and registers the main schedule and the sub-schedule adjusted by the schedule adjustment processing unit in the schedule management information. The template sub-schedule management information is for each sub-schedule,
Same-day information that should be implemented on the same day as the main schedule;
Neighbor information about what should be performed adjacent to the main schedule;
The schedule reservation method according to claim 7, further comprising allowable time zone information that is a time zone in which the sub-schedule can be reserved. The sub-schedule condition analysis processing unit, based on the template sub-schedule management information, when the same day is specified from the same-day information and the adjacent is specified from the adjacent information, Calculate the total required time by adding the required time of the secondary schedule that is adjacent to the main schedule,
9. The schedule reservation method according to claim 8, wherein the free time analysis processing unit extracts free time of the calculated total required time from the schedule management information on the same day as the main schedule. . In the schedule reservation screen displayed on the client by the screen display processing unit,
The schedule reservation method according to claim 7, further comprising a condition setting button for calling an edit screen for editing the definition contents of the template sub-schedule management information. When the screen display processing unit accepts the change of the date and time of the main schedule,
The free time analysis processing unit re-extracts the time required for the main schedule and the time required for the sub schedule from the schedule management information again according to the changed date and time. The schedule reservation method described. The required time calculation processing unit, when the sub-schedule is a movement schedule,
The schedule according to claim 7, wherein the time required for the sub-schedule is calculated in consideration of the enrollment location of the participant registered in the schedule management information and the location where the main schedule is held. Reservation method. A schedule reservation program that adjusts the schedule of multiple participants and reserves a schedule,
Computer storage devices include
One or more sub-schedules necessary for executing the main schedule for each type of the main schedule in which the plurality of persons participate, a role to execute the sub-schedule for each sub-schedule, and a template sub for managing condition information Schedule management information and schedule management information for managing the reservation status of the participant's schedule are stored,
In the computer,
In order to reserve the main schedule, to input condition information including an allowable date and time in which the main schedule can be executed, a time required for the main schedule, a type of the main schedule, and the roles of the participants and the participants Processing to display the screen of
The template sub-schedule management information is identified from the input condition information, and based on the identified template sub-schedule management information, the input participant's role is used as a key Analyzing the association with the secondary schedule;
Processing for calculating the time required for the sub-schedule necessary for executing the sub-schedule from the template sub-schedule management information and the schedule management information;
From the schedule management information, within the allowable date and time zone of the main schedule, processing to analyze the time required for the main schedule and the time required for the sub schedule,
A process of adjusting the main schedule and the sub-schedules of the plurality of participants based on the free time analyzed in the process of analyzing the free time;
The schedule reservation program for performing the process which carries out reservation registration of the said main schedule and the said subschedule adjusted by the said process to adjust to the said schedule management information.

Images