JP6763271B2 - Scheduling program, scheduling device, and scheduling method - Google Patents

Description

The present invention relates to a scheduling program, a scheduling device, and a scheduling method.

Conventionally, the scheduled dates for executing multiple events that are performed in sequence may be adjusted. As related prior art, for example, one or more test configuration proposals are drafted using the delivery, inventory status, and alternative relationship data of each component, and the effectiveness of component switching is evaluated from the selection result of the received test configuration. There is one that drafts one or more scheduled member switching dates. In addition, there is a technique of accepting conditions specified by the reservation person and creating a plurality of candidate schedules in which time zones and venues that are candidates for the schedule are set based on the conditions. In addition, by accessing the designated homepage by entering the ID, the customer is automatically presented with the visitable date of the sales office in charge of the customer, and the customer selects and inputs the desired date from among them. is there.

Japanese Unexamined Patent Publication No. 2005-922382 Japanese Unexamined Patent Publication No. 2011-53923 JP-A-2002-288395

However, according to the prior art, if there is a discrepancy between the scheduled period for executing an event among a plurality of events that are performed in sequence and the actual period for which the event is actually performed, the event after the event Determining the scheduled period can be time-consuming. For example, if the person who executes an event is a customer and the person who executes a later event is a person who provides services to the customer, does the customer alone maintain the scheduled period of the later event? Moreover, it is not possible to determine whether or not to shift. Therefore, it takes time and effort because the customer and the person who provides the service discuss the scheduled period of the later event.

In one aspect, the present invention is a scheduling program, scheduling that can easily determine the scheduled period of an event after an event in which a difference between the scheduled period and the actual period occurs among a plurality of events performed in sequence. It is an object of the present invention to provide an apparatus and a scheduling method.

According to one aspect of the present invention, an actual period in which one of a plurality of events to be performed in sequence is executed is accepted, a scheduled period in which each event of the plurality of events is scheduled to be executed, and a period before each event. After the execution of each event, the period to be secured before each event is executed is executed after the actual period and after the scheduled period of any event by referring to the storage unit that stores the period associated with each event. Determines if the time associated with the other event that is scheduled has elapsed is later than the scheduled period of the other event, and determines that the elapsed time is later than the scheduled period of the other event. When it is determined, the scheduled period of another event stored in the storage unit is changed to the period after the elapsed time, and when the elapsed time is before the scheduled period of the other event, the above-mentioned stored in the storage unit. Scheduling programs, scheduling devices, and scheduling methods that maintain the scheduled duration of other events are proposed.

According to one aspect of the present invention, there is an effect that the scheduled period of the event after the event in which the scheduled period and the actual period are different from each other among the plurality of events performed in order can be easily determined. ..

FIG. 1 is an explanatory diagram showing an operation example of the scheduling device 101 according to the present embodiment. FIG. 2 is an explanatory diagram showing a configuration example of the scheduling system 200. FIG. 3 is an explanatory diagram showing a hardware configuration example of the customer-specific calendar DB server 201. FIG. 4 is an explanatory diagram showing a hardware configuration example of the customer PC 203. FIG. 5 is an explanatory diagram showing an example of a functional configuration of the scheduling system 200. FIG. 6 is an explanatory diagram (No. 1) showing a screen example of creating an action plan. FIG. 7 is an explanatory diagram (No. 2) showing an example of a screen for creating an action plan. FIG. 8 is an explanatory diagram showing a screen example of reschedule due to customer convenience. FIG. 9 is a flowchart showing an example of the action plan creation processing procedure. FIG. 10 is a flowchart showing an example of a procedure for calculating and displaying candidate dates for the next event. FIG. 11 is a flowchart showing an example of the reschedule processing procedure due to customer convenience.

Hereinafter, embodiments of the disclosed scheduling program, scheduling apparatus, and scheduling method will be described in detail with reference to the drawings.

FIG. 1 is an explanatory diagram showing an operation example of the scheduling device 101 according to the present embodiment. The scheduling device 101 is a computer that schedules a scheduled period for executing a plurality of events that are sequentially performed. The scheduling device 101 is, for example, a PC (Personal Computer). The unit time of the scheduled period may be any length, for example, 1 hour unit, half day unit, 1 day unit, 1 week unit, or the like. In the following description, the unit of the scheduled period is assumed to be one day, and the scheduled period is referred to as "scheduled date".

Here, the plurality of events described above have the characteristic that after a certain event is executed, another event is executed based on the execution result of the certain event. For example, a plurality of events that occur between a support person who supports a certain service as a person who provides a certain service and a customer of a certain service as a person who receives a certain service are described.

When a customer makes an inquiry or a failure response request to a support staff member, the first event occurs in which the support staff member requests the customer for investigation materials. Next, as the second event following the first event, an event occurs in which the customer provides survey materials to the support staff. Next, as the third event following the second event, an event occurs in which the support staff gives a primary response to the customer. Finally, as the fourth event following the third event, an event occurs in which the support staff gives the final response to the customer. Here, the support person notifies the customer of the scheduled dates of the plurality of events from the first event to the fourth event, that is, the schedules of the plurality of events to be performed in order, and acknowledges the customer. get. Hereinafter, the schedule of a plurality of events performed in order is referred to as an "action plan".

Here, after notifying the customer of the action plan, the scheduled date of an event in the action plan may differ from the actual period during which the event is actually executed. Here, the unit of the actual period may be any unit time as well as the unit time of the scheduled period. In the following description, it is assumed that the unit time is one day as well as the unit time of the scheduled time, and the actual period is referred to as "actual date".

Then, if there is a discrepancy between the scheduled date for executing an event among multiple events that are performed in sequence and the actual date for which a certain event is actually performed, the scheduled date for the event after the certain event is determined. It may take time and effort. For example, if the person who executes an event is a customer and the person who executes a later event is a support person, the customer alone determines whether to keep the scheduled date of the later event as it is or to shift it. It is not possible. More specifically, incident response in support derives the number of days for a later event based on the content of the incident and the rules of thumb, but these cannot be determined by the customer. Therefore, it is troublesome because the customer and the support person cannot decide the scheduled date of the later event only by the proposal on the customer side, and the customer and the support person discuss the scheduled date of the later event.

Therefore, in the present embodiment, the scheduled date of the event after a certain event, whose actual date is deviated from the schedule, is the date after the period for securing the event after the actual date of the certain event has elapsed. Explain that the event should be staggered after the scheduled date and maintained before the scheduled date.

An operation example of the scheduling device 101 will be described with reference to FIG. Here, the scheduling device 101 is a computer operated by the customer. Then, the scheduling device 101 shown in FIG. 1 executes reschedule when the scheduled date and the actual date are different from the plurality of events e1 to e4 that are sequentially performed. Further, the scheduled dates of the events e1 to e4 are set before the state shown in FIG. An example of setting the scheduled date for the events e1 to e4 will be described with reference to FIGS. 6 and 7. Further, in the events e1 to e4, a period to be secured until each event is executed after the execution of the event before each event is set. The period to be secured may be, for example, a minimum period guided by a support person, or a period obtained by adding a predetermined number of days to the minimum period. Further, in the events e1 to e4, a minimum period to be secured and a maximum period to be secured are set as a period to be secured before each event is executed after the execution of the event before each event. May be good. In the following description, the minimum period to be secured is referred to as "minimum period", and the maximum period to be secured is referred to as "maximum period". The unit time of the minimum period and the maximum period may be any length as well as the unit time of the scheduled period. In the following description, the unit of the minimum period and the maximum period is assumed to be one day.

Here, the minimum period and the maximum period are specified in advance based on the experience of the support staff. The scheduled dates, minimum periods, etc. of the events e1 to e4 are stored in the storage unit 110 accessible to the scheduling device 101 in association with each event.

Specifically, the event name of the event e1 is "request for collecting survey data", and it corresponds to the first event described above, and the scheduled date of the event e1 is July 2. Here, since the event e1 is the first event among the plurality of events performed in order, the minimum period is not set. In addition, the event name of the event e2 is "Providing survey materials", which corresponds to the second event described above. The scheduled date of the event e2 is July 8, and the minimum period of the event e2 is 6. It's a day. In addition, the event name of the event e3 is "primary report", which corresponds to the third event described above, the scheduled date of the event e3 is July 14, and the minimum period of the event e3 is 6 days. Is. In addition, the event name of the event e4 is "final report", which corresponds to the fourth event described above, the scheduled date of the event e4 is July 23, and the minimum period of the event e4 is 7 days. Is.

The scheduling device 101 shown in FIG. 1 displays the scheduled dates of the events e1 to e4 on the screen 111 of the scheduling device 101. More specifically, the scheduling device 101 displays a calendar on the screen 111, and displays the events e1 to e4 on the dates corresponding to the scheduled dates of the events e1 to e4 in the calendar.

Here, as shown in FIG. 1 (1), the scheduling device 101 accepts the actual date of the event e2 as one of a plurality of events that are sequentially performed by the customer's operation. In the example of FIG. 1, the scheduling device 101 accepts July 10 as the actual date of the event e2.

Next, the scheduling device 101 determines whether or not to shift the scheduled date of the event e3 as another event scheduled to be executed after the scheduled date of the event e2. Specifically, as shown in FIG. 1 (2), the scheduling device 101 refers to the storage unit 110, and the time when the minimum period of the event e3 elapses after the actual date of the event e2 is the schedule of the event e3. Determine if it is later than the day. In the example of FIG. 1, the day when the minimum period of the event e3 elapses from the actual date of the event e2 is July 15th, which is 5 days after July 10th. In FIG. 1, a thick arrow indicates July 15th, which is five days after July 10th.

Then, when it is determined that the above-mentioned elapsed time is later than the scheduled date of the event e3, the scheduling device 101 schedules the event e3 stored in the storage unit 110 as shown in FIG. 1 (3). Change the date to a date after the above-mentioned elapsed time. Here, the date to be changed may be any day after the elapsed time, but it is preferable for the customer to change the date to be the elapsed time. In the example of FIG. 1, the scheduling device 101 changes the scheduled date of the event e3 stored in the storage unit 110 from July 14th to July 15th. Further, the scheduling device 101 displays the event e3 on the screen 111 as the event e3'.

Further, although different from the example shown in FIG. 1, when the elapsed time is before the scheduled date of the event e3, the scheduling device 101 maintains the scheduled date of the event e3 stored in the storage unit 110. Here, as a method of maintaining, the scheduling device 101 may not update the scheduled date of the event e3 stored in the storage unit 110, or may update it on the same date.

Further, the scheduling device 101 determines whether or not to shift the scheduled date of the event e4 for the event e4 after the event e3. Whether or not to shift the scheduled date of the event e4 will be described with reference to FIGS. 6 and 7.

In this way, the scheduling device 101 sets the scheduled date of the event after a certain event, whose actual date is deviated from the scheduled date, at the time when the minimum period for securing the event after the actual date of the certain event has elapsed. , Stagger after the scheduled date of a later event, or keep it. Here, since the minimum period of the later event secures the period that the support person should reserve to complete the work, the scheduling device 101 can easily set the scheduled date of the later event according to the actual date. Can be decided.

Further, in the example of FIG. 1, when the minimum period of the event e3 is obtained from the actual date of the event e2, the scheduling device 101 includes holidays such as Saturdays and Sundays and holidays, but includes holidays and holidays. It doesn't have to be. Conversely, the scheduling device 101 may include holidays and holidays when 24-hour support is required. In the following example, for the sake of simplification of the explanation, holidays and holidays are included when calculating the number of days elapsed from the actual date.

Next, an example in which the scheduling device 101 is applied to the scheduling system 200 will be described with reference to FIG.

FIG. 2 is an explanatory diagram showing a configuration example of the scheduling system 200. The scheduling system 200 includes a customer-specific calendar DB (DataBase) server 201, a support staff PC 202, and customer PCs 203A to 203C. The customer-specific calendar DB server 201, the support staff PC202, and the customer PC203A to 203C are connected by the network 210. Here, the customer PCs 203A to 203C correspond to the scheduling device 101 shown in FIG. The customer PCs 203A to 203C are computers operated by the customer clia to clicC, respectively. Further, the support person PC 202 is a computer operated by the support person sr.

The scheduling system 200 is a system that provides an action plan to customers clia to clicC. As a method of providing the action plan to the customer, for example, conventionally, it is conceivable to notify via the Web, or to notify by e-mail, telephone, or the like. However, with these methods, even if the customer obtains an action plan from the support department, it is difficult to manage it unless the obtained action plan is incorporated into his / her schedule table. In addition, in the notification by e-mail, it may be difficult for the customer to reconfirm the content of the notification because the e-mail containing the action plan is deleted or mixed with other e-mails. Also, with telephone notifications, no action plan remains unless you take notes while you are on the phone. In addition, the method via the Web or email is a one-sided notification from the support department, and feedback from the customer such as consent, change, refusal, etc. must be received by another method such as telephone or email, so no feedback is given. Or, the information may be confused.

Therefore, the scheduling system 200 provides a service that provides an action plan. The customer-specific calendar DB server 201 provides a dedicated calendar for each incident of customers clia to clicC. The support staff PC 202 registers the action plans related to the customers clia to clic in the dedicated calendar for each customer incident by the operation of the support staff sr. This dedicated calendar is displayed on the Web so that only the customer PC 203 operated by the corresponding customer can refer to it via the network 210.

The customer PC 203 registers the scheduled date of each event in the action plan within the range preset by the support person sr. Then, among the events in the action plan, the range that can be registered as the scheduled date of each event changes depending on the scheduled date of the previous event for the event whose interval from the previous event is fixed. An example of this variation will be described with reference to FIGS. 6 and 7.

Further, the customer PC 203 has a calendar update agent software capable of updating a dedicated calendar. The customer PC 203 exchanges data with the customer-specific calendar DB server 201 by executing the calendar update agent software. The calendar update agent software will be described with reference to FIG. Next, a hardware configuration example of the customer-specific calendar DB server 201 is shown in FIG. 3, and a hardware configuration example of the customer PC 203 is shown in FIG.

FIG. 3 is an explanatory diagram showing a hardware configuration example of the customer-specific calendar DB server 201. In FIG. 3, the customer-specific calendar DB server 201 includes a CPU 301, a ROM (Read Only Memory) 302, and a RAM (Random Access Memory) 303. Further, the customer-specific calendar DB server 201 includes a disk drive 304 and a disk 305, and a communication interface 306. Further, the CPU 301 to the disk drive 304 and the communication interface 306 are connected by the bus 307, respectively.

The CPU 301 is an arithmetic processing device that controls the entire customer-specific calendar DB server 201. The ROM 302 is a non-volatile memory that stores a program such as a boot program. The RAM 303 is a volatile memory used as a work area of the CPU 301.

The disk drive 304 is a control device that controls reading and writing of data to the disk 305 according to the control of the CPU 301. For the disk drive 304, for example, a magnetic disk drive, an optical disk drive, a solid state drive, or the like can be adopted. The disk 305 is a non-volatile memory that stores data written under the control of the disk drive 304. For example, when the disk drive 304 is a magnetic disk drive, a magnetic disk can be adopted as the disk 305. When the disk drive 304 is an optical disk drive, an optical disk can be used for the disk 305. When the disk drive 304 is a solid state drive, a semiconductor memory formed by semiconductor elements, a so-called semiconductor disk, can be adopted as the disk 305.

The communication interface 306 is a control device that controls the input / output of data from another device via the network 210 or the support person's PC 202. Specifically, the communication interface 306 is connected to another device via the network 210 through a communication line. For the communication interface 306, for example, a modem, a LAN (Local Area Network) adapter, or the like can be adopted.

Further, when the support person sr, the administrator of the scheduling system 200, or the like directly operates the customer-specific calendar DB server 201, the customer-specific calendar DB server 201 may have hardware such as a display, a keyboard, and a mouse. ..

FIG. 4 is an explanatory diagram showing a hardware configuration example of the customer PC 203. Here, since the hardware configuration example of the support staff PC 202 is the same as the hardware configuration example of the customer PC 203, description and illustration will be omitted.

The customer PC 203 includes a CPU 401, a ROM 402, a RAM 403, a disk drive 404, a disk 405, and a communication interface 406. Further, the customer PC 203 includes a display 407, a keyboard 408, a mouse 409, and a device connection interface 410. Further, the CPU 401 to the disk drive 404 and the communication interface 406 to the device connection interface 410 are connected by the bus 411, respectively.

The CPU 401 is an arithmetic processing unit that controls the entire customer PC 203. The ROM 402 is a non-volatile memory that stores a program such as a boot program. The RAM 403 is a volatile memory used as a work area of the CPU 401.

The disk drive 404 is a control device that controls reading and writing of data to the disk 405 according to the control of the CPU 401. For the disk drive 404, for example, a magnetic disk drive, an optical disk drive, a solid state drive, or the like can be adopted. The disk 405 is a non-volatile memory that stores data written under the control of the disk drive 404. For example, when the disk drive 404 is a magnetic disk drive, a magnetic disk can be adopted as the disk 405. When the disk drive 404 is an optical disk drive, an optical disk can be used as the disk 405. Further, when the disk drive 404 is a solid state drive, a semiconductor disk can be adopted as the disk 405.

The communication interface 406 is a control device that controls the internal interface with the network 210 and controls the input / output of data from the external device. Specifically, the communication interface 406 is connected to another device via the network 210 through a communication line. For the communication interface 406, for example, a modem, a LAN adapter, or the like can be adopted.

The display 407 is a device that displays data such as a document, an image, and functional information, including a mouse cursor, an icon, or a toolbox. For the display 407, for example, a CRT (Cathode Ray Tube), a TFT (Thin Film Transistor) liquid crystal display, a plasma display, or the like can be adopted.

The keyboard 408 is a device that has keys for inputting characters, numbers, various instructions, and the like, and inputs data. Further, the keyboard 408 may be a touch panel type input pad, a numeric keypad, or the like. The mouse 409 is a device that moves the mouse cursor, selects a range, moves a window, changes the size, and the like. The mouse 409 may be a trackball, a joystick, or the like as long as it has the same function as a pointing device.

The device connection interface 410 is a control device that connects the customer PC 203 and the peripheral device and controls the connected peripheral device. For example, the device connection interface 410 can adopt USB (Universal Serial Bus) or the like. Then, for example, when the device connection interface 410 is USB, a USB flash drive 421 or a memory card reader / writer 422 can be connected to the device connection interface 410.

The USB flash drive 421 includes a flash memory, which is a non-volatile semiconductor memory capable of holding data without supplying power, and includes a drive device that controls the flash memory and communicates with the device connection interface 410. It is a device. The memory card reader / writer 422 is a control device that controls reading and writing of data to the memory card 423. The memory card 423 is a card-type recording medium. A flash memory is built in the memory card 423.

(Example of functional configuration of scheduling system 200)
FIG. 5 is an explanatory diagram showing an example of a functional configuration of the scheduling system 200. The customer PC 203A has a control unit 500A. The control unit 500A has the calendar update agent software 501. The calendar update agent software 501 has a reception unit 511, a display unit 512, a registration unit 513, a determination unit 514, and a change unit 515. The control unit 500A realizes the functions of each unit by executing the program stored in the storage device by the CPU 401. Specifically, the storage device is, for example, ROM 402, RAM 403, disk 405, etc. shown in FIG. Further, the processing results of each part are stored in the RAM 403, the register of the CPU 401, the cache memory of the CPU 401, and the like.

Further, the customer PC 203 can access the storage unit 520A. The storage unit 520A is stored in a storage device such as a RAM 403 or the like.

Further, the customer PC 203B has a control unit 500B and a storage unit 520B, and the customer PC 203C has a control unit 500C and a storage unit 520C. The control units 500B and 500C have the calendar update agent software 501. Although omitted in FIG. 5, the calendar update agent software 501 included in the control units 500B and 500C also has a reception unit 511 to a change unit 515. The storage units 520A to 520C correspond to the storage units 110 shown in FIG.

The customer-specific calendar DB server 201 has dedicated calendars calAX, calBY, and calCZ. The dedicated calendars calAX to calCZ are a calendar corresponding to the incident X related to the customer cliA, a calendar corresponding to the incident Y related to the customer cliB, and a calendar corresponding to the incident Z related to the customer cliC, respectively.

The calendar update agent software 501 refers to each event of the action plan from the customer-specific calendar DB server 201, and temporarily stores each event in the storage unit 520. Then, the calendar update agent software 501 transmits the scheduled date registered for each event to the customer-specific calendar DB server 201. The function of registering the scheduled date for each event is a function of the reception unit 511 to the registration unit 513. In addition, due to the convenience of both the customer cli and the support staff sr, the scheduled date and the actual date of the event may deviate from each other. The opportunity for the scheduled date and the actual date of the event to deviate is, for example, a delay in providing the survey of the customer cli, an extension of the survey period of the support person sr, or the like. In such a case, the calendar update agent software 501 shifts the scheduled date of the subsequent event according to the actual date. The function of shifting the scheduled date of the subsequent event is a function of the reception unit 511, the determination unit 514, and the change unit 515. At this time, the calendar update agent software 501 may notify the customer of the reschedule by e-mail, alarm message, or the like, and prompt the customer's approval.

First, the function of registering the scheduled date for each event will be described. The storage unit 520 stores information for identifying that each event of a plurality of events to be performed in order is either the first type or the second type, and the minimum period and the maximum period of each event. Remember. Here, the first type of event is an event executed by the support person sr. The second type of event is an event executed by the customer cli. Then, the information that identifies that it is either the first type or the second type may be, for example, an identifier that identifies the first type or the second type, or an event name. For example, the events e1, e3, and e4 shown in FIG. 1 are the first type of events executed by the support person sr. Similarly, the event e2 shown in FIG. 1 is a second type of event executed by the customer cli.

The receiving unit 511 receives the scheduled date of the specified second event, which is the second type, before the first event specified as the first type. Using the events e1 to e4 shown in FIG. 1, the reception unit 511 schedules the event e2, which is the second type of event executed by the customer cli, before the event e3 which is the first event. Accept the day.

The display unit 512 extends the period from the period obtained by adding the minimum period of the first event to the scheduled date of the second event received to the period obtained by adding the maximum period of the first event on the scheduled date of the second event. , Displayed as a candidate period for the scheduled date of the first event. A specific display example is shown in FIG. Also, from the period when the minimum period of the first event is added to the scheduled date to the period when the maximum period of the first event is added to the scheduled date of the second event, holidays and holidays may be included. It may or may not be included. For example, the display unit 512 includes holidays and holidays when the contract with the customer cli is supported for 24 hours, and does not include holidays and holidays when the contract with the customer cli is not supported for 24 hours.

In addition, the display unit 512 displays the candidate period on the dedicated calendar in the display 407. Alternatively, if the customer PC 203 has a printer, the display unit 512 may output the candidate period on a dedicated calendar on paper.

The registration unit 513 registers the date received as the scheduled date of the first event in the candidate period of the scheduled date of the first event in the storage unit 520 as the scheduled date of the first event.

Here, the display unit 512 may divide the candidate period of the scheduled date of the first event into a plurality of candidate dates and display them. Then, the display unit 512 corresponds to each candidate date of the plurality of candidate dates, and from the period in which the minimum period of the third event following the first event is added to each candidate date, the third event is added to each period. The period up to the period including the maximum period of may be displayed as a candidate period for the scheduled date of the third event. Specifically, using the example of FIG. 1, the event e4 is the third event following the event e3, which is the first event. Then, the display unit 512 displays the period from the minimum period to the maximum period of the event e4 as the candidate period of the scheduled date of the event e4, based on each candidate date, corresponding to each candidate date.

Further, the display unit 512 may display each candidate date with a different pattern or / and color between the candidate dates. Then, the display unit 512 assigns the candidate period of the scheduled date of the third event to the same pattern as the pattern given to each candidate date and / or to each candidate date corresponding to each candidate date. The same color as the color is added and displayed.

Then, the customer PC 203 executes the process of the determination unit 514 when the reception unit 511 receives the actual period in which the second event is executed after the registration unit 513 ends.

Next, the function of shifting the scheduled date of the event will be described. As described above, the reception unit 511 receives the actual date when any one of the plurality of events performed in order is executed.

The determination unit 514 refers to the storage unit 520, and the day when the minimum period of the other event scheduled to be executed after the scheduled date of any event elapses from the actual date is later than the scheduled date of the other event. It is determined whether or not it is. Here, the storage unit 520 at this stage stores the scheduled date for executing each event of a plurality of events to be performed in sequence and the minimum period of each event after the event before each event is executed. You just have to.

When the change unit 515 determines that the above-mentioned elapsed date is later than the scheduled date of the other event, the change unit 515 changes the scheduled date of the other event stored in the storage unit 520 to a date after the elapsed date. .. On the other hand, when the elapsed date is before the scheduled date of another event, the changing unit 515 maintains the scheduled date of the other event stored in the storage unit 520.

Next, an example of creating an action plan will be described with reference to FIGS. 6 and 7. In FIGS. 6 and 7, as an action plan, it is assumed that there are a plurality of events e1 to e4 that are sequentially performed as shown below.

Event e1: Support staff sr requests customer cli to collect survey materials Event e2: Customer cli provides support staff sr with collected survey materials Event e3: Support staff sr provides primary response event to customer cli e4: Final answer from support staff sr to customer cli

For events after event e2, the candidate dates that can be selected as scheduled dates will change depending on the customer cli's selection. Further, the minimum period and the maximum period of a plurality of events e1 to e4 to be performed in order are specified at the time of action plan formulation based on the experience of the support person sr. In the examples described with reference to FIGS. 6 and 7, it is assumed that the minimum period and the maximum period are determined as follows.

Minimum period of event e2: 6 days, maximum period: 8 days Minimum period of event e3: 5 days, maximum period: 7 days Minimum period of event e4: 7 days, maximum period: 9 days

First, the support person sr requests the customer cli to collect data as the event e1. The support staff PC 202 sets the occurrence date of the event e1 to the date when the customer cli is requested to collect data by the operation of the support staff sr. Next, a screen example of creating an action plan after the event e2 will be described with reference to FIGS. 6 and 7.

FIG. 6 is an explanatory diagram (No. 1) showing a screen example of creating an action plan. Further, FIG. 7 is an explanatory diagram (No. 2) showing a screen example of creating an action plan. 6 (a), 6 (b), and 7 (c) show a dedicated calendar for the customer cli displayed by the customer PC 203.

The customer PC 203 notified from the support staff PC 202 selects the scheduled date for providing the collected survey material as the event e2 by the operation of the customer cli. On the screen 601 shown in FIG. 6A, the customer PC 203 calculates and displays the candidate date of the event e2. Here, in the examples of FIGS. 6 and 7, it is assumed that the scheduled date of the event e1 is determined on July 2, 2015.

Here, the customer PC 203 calculates the maximum period of the previous event-the minimum period of the previous event + 1 candidate date according to the following equation (1).

i-th candidate date = date of occurrence of previous event + minimum period of previous event + i ... (1)

Here, i is an integer from 0 to (maximum period of the previous event-minimum period of the previous event). For example, for event e2, since the minimum period of event e2 is 6 days and the maximum period is 8 days, the customer PC 203 calculates three candidate dates from 0 to 8-6 = 2. Then, the customer PC 203 calculates the first candidate date as July 2 + 6 days = July 8 and the second candidate date as July 2 + 6 days + 1 day = July 9. Calculate and calculate the third candidate date as July 2 + 6 days + 2 days = July 10.

In FIG. 6A, the customer PC 203 displays the first candidate date as the event candidate e2c_1, the second candidate date as the event candidate e2c_1, and the third candidate date as the event candidate. Displayed as e2c_3. Further, the customer PC 203 displays selection buttons e2c_1btn to e2c_3btn for selecting each candidate inside each of the event candidates e2c_1 to e2c_3. The customer cli can select the scheduled date of the event e2 by selecting the selection buttons e2c_1btn to e2c_3btn with the mouse 409 or the like.

Further, the customer PC 203 may impart different patterns and / and colors to the event candidates e2c_1 to e2c_3. For example, in FIG. 6A, in the customer PC 203, the event candidate e2c_1 is given white as a color, the event candidate e2c_2 is given a light shade as a pattern, and the event candidate e2c_3 is given a dark shade as a pattern. Give a hook. Further, as another example, in the customer PC 203, the event candidate e2c_1 may be given an orange color, the event candidate e2c_2 may be given a yellow color, and the event candidate e2c_3 may be given a green color. Good.

Further, the customer PC 203 calculates the candidate date of the next event e3 according to the equation (1) corresponding to each of the event candidates e2c_1 to e2c_3. Specifically, the customer PC 203 displays the candidate date of the event e3 corresponding to the event candidate e2c_1 as the event candidate e2c_1_e3. Similarly, the customer PC 203 displays the candidate date of the event e3 corresponding to the event candidate e2c_2 as the event candidate e2c_2_e3, and displays the candidate date of the event e3 corresponding to the event candidate e2c_3 as the event candidate e2c_3_e3. Then, the customer PC 203 may display the event candidates e2c_1_e3 to e2c_3_e3 with the same pattern and / or the same color as the pattern given to the corresponding event candidates e2c_1 to e2c_3.

Specifically, in the example of FIG. 6A, the customer PC 203 displays the event candidate e2c_1_e3 with the white color given to the corresponding event candidate e2c_1. Similarly, the customer PC 203 displays the event candidate e2c_2_e3 with the light shading given to the corresponding event candidate e2c_2, and displays the event candidate e2c_3_e3 with the dark shading given to the corresponding event candidate e2c_3. Give and display.

Next, as shown in the screen 602 shown in FIG. 6B, it is assumed that the customer PC 203 accepts the press of the selection button e2c_1btn by the operation of the customer cli. As a result, the scheduled date of the event e2 is fixed, so that the customer PC 203 displays a candidate for the scheduled date of the event e3 in the same manner as the method described with FIG. 6A. Here, the candidates for the event e3 have already been calculated at the time of FIG. 6A.

In FIG. 6B, the customer PC 203 displays the event candidate e3c_1 as the first candidate for the scheduled date of the event e3. Similarly, the customer PC 203 displays the event candidate e3c_2 as the second candidate for the scheduled date of the event e3, and displays the event candidate e3c_3 as the third candidate for the scheduled date of the event e3.

Further, the customer PC 203 displays selection buttons e3c_1btn to e3c_3btn for selecting each candidate inside the event candidates e3c_1 to e3c_3, as in the method described in FIG. 6A. Further, the customer PC 203 imparts different patterns or / and colors to the event candidates e3c_1 to e3c_3 in the same manner as in the method described in FIG. 6A. Further, the customer PC 203 calculates the candidate date of the next event e4 corresponding to each of the event candidates e3c_1 to e3c_3 in the same manner as the method described in FIG. 6A, and sets them as event candidates e3c_1_e4 to e3c_3_e4. indicate.

Further, the customer PC 203 displays the "back to the previous" button back_btn on the screen 602. The customer PC 203, which has received that the "back to previous" button back_btn has been pressed, cancels the scheduled date of the confirmed event e2 and returns to the state of the screen 601.

Then, on the screen 701 shown in FIG. 7 (c), it is assumed that the customer PC 203 accepts the pressing of the selection button e3c_2btn by the operation of the customer cli. As a result, the scheduled date of the event e3 is fixed, so that the customer PC 203 displays a candidate for the scheduled date of the event e4 in the same manner as the method described with FIG. 6A. Specifically, in FIG. 7C, the customer PC 203 displays the event candidate e4c_1 as the first candidate for the scheduled date of the event e4. Similarly, the customer PC 203 displays the event candidate e4c_2 as the second candidate for the scheduled date of the event e4, and displays the event candidate e4c_3 as the third candidate for the scheduled date of the event e4.

Further, the customer PC 203 displays selection buttons e4c_1btn to e4c_3btn for selecting each candidate inside the event candidates e4c_1 to e4c_3, as in the method described in FIG. 6A. Further, the customer PC 203 imparts different patterns or / and colors to the event candidates e4c_1 to e4c_3 in the same manner as in the method described in FIG. 6A. Further, similarly to (b) of FIG. 6, the customer PC 203 displays the "back to previous" button back_btn in the screen 701. The customer PC 203, which has received that the "back to previous" button back_btn has been pressed, cancels the scheduled date of the confirmed event e3 and returns to the state of the screen 602.

Next, using the events e1 to e4 shown in FIGS. 6 and 7, a screen example when a reschedule occurs due to customer convenience will be described with reference to FIG.

FIG. 8 is an explanatory diagram showing a screen example of reschedule due to customer convenience. In FIG. 8, when the actual event occurrence date deviates from the initial schedule of the event due to the customer cli's convenience, the customer PC 203 automatically sets the scheduled date of the event after the deviated event according to the event occurrence record. I will explain how to change it and reflect it in the dedicated calendar.

In the example of FIG. 8, among the events e1 to e4 shown in FIGS. 6 and 7, the scheduled date of the event e2 was July 8, 2015, but the actual date was July 10, which was delayed by two days. Suppose that As shown on the screen 801 shown in FIG. 8, the event reflecting the actual date of the event e2 is shown as the event e2'.

The customer PC 203 determines whether or not to shift the event e3 after the event e2 to the rear. The customer PC 203 determines that if there is an event whose actual date is shifted m days later than the scheduled date, and the following equation (2) is satisfied, the next event of the shifted event is shifted later.

Interval from the actual date of the event whose actual date is shifted by m days to the scheduled date of the next event L <Minimum period of the next event x ... (2)

In the example of FIG. 8, since the actual date of the event e2 is July 10 and the scheduled date of the event e3 is July 14, L = 4. Further, as described with reference to FIGS. 6 and 7, x = 5 and the equation (2) is satisfied. Therefore, the customer PC 203 determines that the event e3 is shifted backward. Here, when the equation (2) is satisfied, it means that the time required for the support person sr to work is insufficient as a result of the actual date being shifted to the back by m days.

Then, the customer PC 203 sets the scheduled date of the event e3 to the day x days after the actual date of the event e2. Therefore, in the example of FIG. 8, the customer PC 203 is set on July 15, which is five days after July 10, which is the actual date of the event e2. Further, the customer PC 203 may set the scheduled date of the event e3 m + x days after the scheduled date of the event e2.

Subsequently, the customer PC 203 determines whether or not to shift the event e4 after the event e3 to the rear. The customer PC 203 shifts the next event of the shifted event later when there is an event whose scheduled date is shifted m days later and the following formula (2)'is satisfied. Judge.

Interval from the changed scheduled date of the event whose scheduled date is shifted by m days to the scheduled date of the next event L <Minimum period of the next event x ... (2)'

In the example of FIG. 8, since the scheduled date after the change of the event e3 is July 15 and the scheduled date of the event e4 is July 23, L = 8. Further, as described with reference to FIGS. 6 and 7, x = 7 and the equation (2)'is not satisfied. Therefore, the customer PC 203 determines that the event e4 is not shifted backward. Here, when the equation (2)'is not satisfied, it means that the time required for the work by the support person sr is secured even if the scheduled date shifts to the back m days.

As described above, in FIG. 8, it was explained that the actual date shifts behind the scheduled date, but as a result of the customer cli working earlier than the scheduled date, the actual date may be earlier than the scheduled date, so-called ahead of schedule. Can occur. In this case, the customer PC 203 advances all the events after the event that has been advanced. Alternatively, the customer PC 203 displays an event reset button or the like on the screen of the customer PC 203, and when the reset button is pressed, the scheduled date after the event that has been advanced is reset. You may make settings.

Further, in FIG. 8, although the reschedule due to the customer's convenience has been described, the reschedule may occur due to the convenience of the support staff sr, such as the response of the support staff sr not being in time. In this case, the support staff PC 202 resets the schedule of the event whose actual date changes by the operation of the support staff sr. Then, the customer PC 203 displays the schedule of the reset event. In this way, the support person sr asks the customer cli to confirm the schedule of the reset event and obtains approval.

Next, the processing executed by the scheduling system 200 will be described with reference to FIGS. 9 to 11.

FIG. 9 is a flowchart showing an example of the action plan creation processing procedure. The action plan creation process is a process of creating an action plan on the customer PC 203. Further, the action plan creation process shown in FIG. 9 shall create an action plan formed from the four events shown in FIGS. 5 and 6.

The support staff PC 202 sets the event e1 "data collection request" by the operation of the support staff sr (step S901). After the setting, the support staff PC 202 notifies the customer PC 203 that the scheduled date after the event e2 is selected.

Upon receiving the notification, the customer PC 203 executes the calculation / display process of the candidate date of the next event for the event e2 “Provision of survey material” (step S902). The calculation / display process of the candidate date for the next event will be described with reference to FIG. By the process of step S902, the customer PC 203 displays the event candidates e2c_1 to e2c_3 shown in FIG. 6 and the selection buttons e2c_1btn to e2c_3btn. Here, the customer PC 203 can display the event candidates e2c_1_e3 to e2c_3_e3 by performing the calculation and display processing of the candidate date of the next event for each of the event candidates e2c_1 to e2c_3.

Then, the customer PC 203 determines whether or not the selection buttons e2c_1btn to e2c_3btn of any of the candidate dates are pressed from the candidate dates of the event e2 "Provision of survey material" (step S903). If neither of the candidate date selection buttons e2c_1btn to e2c_3btn is pressed (step S903: No), the customer PC 203 executes the process of step S903 again.

On the other hand, when any of the candidate date selection buttons e2c_1btn to e2c_3btn is pressed (step S903: Yes), the customer PC 203 stores the candidate date corresponding to the pressed selection button as the scheduled date of the event e2. Register with 520 (step S904). Next, the customer PC 203 executes the calculation / display process of the candidate date of the next event for the event e3 “primary response” (step S905). Then, the customer PC 203 determines whether or not the "back to previous" button back_btn has been pressed (step S906). When the "back to previous" button back_btn is pressed (step S906: Yes), the customer PC 203 shifts to the process of step S903.

On the other hand, when the "back to previous" button back_btn is not pressed (step S906: No), the customer PC 203 is a button for selecting any candidate date from the candidate dates of the event e3 "primary answer". It is determined whether or not e3c_1btn to e3c_3btn are pressed (step S907). When none of the candidate date selection buttons e3c_1btn to e3c_3btn is pressed (step S907: No), the customer PC 203 proceeds to the process of step S906.

On the other hand, when any of the candidate date selection buttons e3c_1btn to e3c_3btn is pressed (step S907: Yes), the customer PC 203 registers the candidate date corresponding to the pressed selection button as the scheduled date of the event e3. (Step S908). Next, the customer PC 203 executes the calculation / display process of the candidate date of the next event for the event e4 “final answer” (step S909). Then, the customer PC 203 determines whether or not the "back to previous" button back_btn has been pressed (step S910). When the "back to previous" button back_btn is pressed (step S910: Yes), the customer PC 203 shifts to the process of step S907.

On the other hand, when the "back to previous" button back_btn is not pressed (step S910: No), the customer PC 203 is a button for selecting any candidate date from the candidate dates of the event e4 "final answer". It is determined whether or not e4c_1btn to e4c_3btn are pressed (step S911). When none of the candidate date selection buttons e4c_1btn to e4c_3btn is pressed (step S9111: No), the customer PC 203 proceeds to the process of step S910.

On the other hand, when any of the candidate date selection buttons is pressed (step S911: Yes), the customer PC 203 registers the candidate date corresponding to the pressed selection button in the storage unit 520 as the scheduled date of the event e4. (Step S912). Next, the customer PC 203 determines whether or not the "back to previous" button back_btn has been pressed (step S913). When the "back to previous" button back_btn is pressed (step S913: Yes), the customer PC 203 shifts to the process of step S911. On the other hand, when the "back to previous" button back_btn is not pressed (step S913: No), the customer PC 203 ends the action plan creation process.

When the action plan creation process is completed, the customer PC 203 transmits the set scheduled dates of the events e2 to e4 to the customer-specific calendar DB server 201.

FIG. 10 is a flowchart showing an example of a procedure for calculating and displaying candidate dates for the next event. The candidate date calculation / display process for the next event is a process for calculating the candidate date for the next event to be the target and displaying it on the screen of the customer PC 203.

The customer PC 203 acquires the preset minimum period and maximum period of the previous event from the target next event name (step S1001). Next, the customer PC 203 substitutes 0 for the variable i (step S1002). Then, the customer PC 203 determines whether or not i is smaller than the maximum period of the previous event − the minimum period of the previous event (step S1003). If i is less than the maximum period of the previous event-the minimum period of the previous event (step S1003: Yes), the customer PC 203 has the occurrence date of the previous event + the previous event on the i-th candidate date of the next event. The minimum period + i of is set (step S1004). Then, the customer PC 203 increments i (step S1005) and shifts to the process of step S1003.

On the other hand, when i is equal to or greater than the maximum period of the previous event − the minimum period of the previous event (step S1003: No), the customer PC 203 displays all candidate dates of the next event on the screen of the customer PC 203. Display (step S1006). Next, the customer PC 203 displays a selection button within all candidate days of the next event (step S1007). After the end of step S1007, the customer PC 203 ends the candidate date calculation / display process for the next event.

FIG. 11 is a flowchart showing an example of the reschedule processing procedure due to customer convenience. The reschedule process due to customer convenience is a process for changing the scheduled date of an event after an event in which a difference between the actual date and the scheduled date occurs due to customer convenience. In the process shown in FIG. 11, it is assumed that the actual date of the nth event among the plurality of events included in the action plan is set.

The customer PC 203 determines whether or not the actual date of the received nth event is different from the scheduled date (step S1101). When the actual date of the nth event is the same as the scheduled date (step S1101: No), the reschedule does not occur, so that the customer PC 203 ends the reschedule process due to the customer's convenience.

On the other hand, when the actual date of the nth event is different from the scheduled date (step S1101: Yes), the customer PC 203 sets the actual date of the nth event to a date m days after the scheduled date (step S1102). ). Next, the customer PC 203 confirms the direction of movement (step S1103).

When the direction of movement is forward, that is, when m is less than 0 (step S1103: m <0 (move forward)), the customer PC 203 sets all scheduled dates of the events after the nth event to m days. Set the day ahead of schedule (step S1104). Then, the customer PC 203 ends the reschedule process due to the customer's convenience.

When the direction of movement is backward, that is, m is greater than 0 (step S1103: m> 0 (move backward)), the customer PC 203 is set in the variable L by the actual date of the nth event or after the movement. Substitute the interval between the scheduled date and the scheduled date of the n + 1th event (step S1105). Next, the customer PC 203 compares the “minimum period (x) of the previous event” set in the n + 1th event with L (step S1106).

As a result of the comparison, the customer PC 203 determines whether or not L is smaller than x (step S1107). When L is smaller than x (step S1107: Yes), the customer PC 203 sets the scheduled date of the n + 1th event before the change to m + x days after the scheduled date before the change of the nth event, and the customer PC 203. Is displayed on the screen of (step S1108). Then, the customer PC 203 increments n (step S1109) and shifts to the process of step S1105. In this way, the customer PC 203 repeats the same process for the next event as long as L is smaller than x.

On the other hand, when L is x or more (step S1107: No), the customer PC 203 ends the reschedule process due to the customer's convenience. As described above, when L is larger than x, the customer PC 203 does not change the scheduled date of the subsequent event.

As described above, in the customer PC 203, the scheduled date of the event after a certain event is set to the date after the minimum period for securing the event after the actual date of the certain event has elapsed, which is after the scheduled date of the later event. Stagger and maintain before the scheduled date. Here, since it is guaranteed that the minimum period of the later event secures the period that the support staff should secure in order to complete the work, the customer PC 203 is set according to the actual date of the later event. The scheduled date can be easily determined.

Further, it is assumed that the customer PC 203 accepts the scheduled date of the second event executed by the customer cli. Then, it is assumed that there is a first event executed by the support person sr after the second event. In this case, the customer PC 203 displays the candidate period of the scheduled date of the first event as the minimum period to the maximum period of the first event based on the scheduled reception date, and the received date is the first event. It may be registered as the scheduled date of. As a result, in the customer PC 203, in the presence of the customer cli and the support staff sr having different interests, the support staff sr is the first while setting the scheduled date of the first event as desired by the customer cli. It is possible to secure the minimum period for executing the event.

Further, the customer PC 203 may display the candidate period of the scheduled date of the first event by dividing it into a plurality of candidate days. Then, it is assumed that there is a third event after the first event. In this case, the customer PC 203 corresponds to each candidate date from the period in which the minimum period of the third event is added to each candidate date to the period in which the maximum period of the third event is added to each period. , May be displayed as a candidate period for the scheduled date of the third event. As a result, the customer cli confirms what kind of period the candidate period for the third event following the first event will be, even if one of the candidate dates is not selected as the scheduled date for the first event. can do.

Further, the customer PC 203 may display the candidate period of the scheduled date of the first event by giving a plurality of candidate dates with different patterns and / and colors among the candidate dates. Then, in the customer PC 203, the candidate period of the scheduled date of the third event is assigned to the same pattern as the pattern assigned to each candidate date and / or to each candidate date corresponding to each candidate date. The same color as the color may be added and displayed. As a result, the customer cli can intuitively grasp the correspondence relationship between the candidate date of the scheduled date of the first event and the candidate period of the scheduled date of the third event by the pattern or color.

In addition, the scheduling system 200 can agree on an action plan with the customer cli with one proposal. Further, the scheduling system 200 can agree with the customer cli on the subsequent schedule with one proposal even if there is a change after the action plan is agreed. In addition, the customer cli can know the situation in a timely manner. Further, unlike the method of notifying the action plan by e-mail, the scheduling system 200 does not send or lose the schedule.

Further, depending on the calendar update agent software 501, an alarm notification can be issued. Further, the calendar update agent software 501 can link the calendar with the schedule management software of a plurality of devices including a smartphone or the like by importing the distributed calendar. Further, since the scheduling system 200 goes through the network 210, the action plan can be notified to the overseas customer cli without considering the time difference and the language barrier. In addition, the scheduling system 200 can measure the quality of service from the execution history of the action plan. For example, the scheduling system 200 can calculate the quality of service based on the amount of deviation between the actual date of the event executed by the support staff and the scheduled date registered by the customer cli.

The scheduling method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. This scheduling program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM (Compact Disc-Read Only Memory), or a DVD (Digital Versaille Disk), and is read from the recording medium by the computer. Will be executed. Further, this scheduling program may be distributed via a network such as the Internet.

The following additional notes are further disclosed with respect to the above-described embodiment.

(Appendix 1) To the computer
Accepts the actual period during which any of the multiple events that occur in sequence is executed,
The scheduled period for executing each event of the plurality of events and the period to be secured before executing each event after the execution of the event before each event are stored in association with each event. The scheduled period of the other event is the time when the period associated with the other event scheduled to be executed after the scheduled period of any of the events elapses after the actual period with reference to the storage unit. Determine if it is later,
When it is determined that the elapsed time point is later than the scheduled period of the other event, the scheduled period of the other event stored in the storage unit is changed to a period after the elapsed time point, and the elapsed time is described. If the time point is before the scheduled period of the other event, the scheduled period of the other event stored in the storage unit is maintained.
A scheduling program characterized by executing processing.

(Appendix 2) The storage unit is
Each event of a plurality of events performed in sequence is either a first type of event executed by a person who provides a service or a second type of event executed by a person who receives the service. It remembers the information that identifies it and the minimum and maximum time that should be secured before each event is executed.
On the computer
Accepting the scheduled period of the second event identified as the second type before the first event identified as the first type,
From the period obtained by adding the minimum period of the first event to the scheduled period of the second event received to the period of adding the maximum period of the first event to the scheduled period of the second event. Is displayed as a candidate period for the scheduled period of the first event.
The period accepted as the scheduled period of the first event among the candidate periods is registered in the storage unit as the scheduled period of the first event.
When the actual period in which the second event is executed is received, the determination process is executed.
The scheduling program according to Appendix 1, characterized by the above.

(Appendix 3) The process to be displayed is
The candidate period is divided into a plurality of periods and displayed.
On the computer
The maximum period of the third event is added to each period from the period obtained by adding the minimum period of the third event following the first event to each period corresponding to each period of the plurality of periods. Is displayed as a candidate period for the scheduled period of the third event until the period in which is added.
The scheduling program according to Appendix 2, wherein the process is executed.

(Appendix 4) The processing to be displayed is
Each of the periods is displayed with different patterns and / and colors between the periods.
On the computer
Corresponding to each of the above periods, from the period in which the minimum period of the third event is added to each of the periods to the period in which the maximum period of the third event is added to each of the above periods, each of the above. The same pattern as the pattern given to the period and / and the same color as the color given to each period are given and displayed.
The scheduling program according to Appendix 3, wherein the process is executed.

(Appendix 5) The process to be displayed is
The candidate period is displayed on the calendar in the screen of the computer.
The scheduling program according to any one of Supplementary note 2 to 4, wherein the processing is executed.

(Appendix 6) The scheduled period for executing each event of a plurality of events to be performed in order and the period to be secured before executing each event after the execution of the event before each event are set for each of the above. A storage unit that stores events in association with them,
The other event that is scheduled to be executed after the actual period and after the scheduled period of any of the events, with reference to the storage unit, accepting the actual period in which any of the plurality of events is executed. It was determined whether or not the time point associated with the event had elapsed was later than the scheduled period of the other event, and it was determined that the elapsed time point was later than the scheduled period of the other event. In this case, the scheduled period of the other event stored in the storage unit is changed to a period after the elapsed time, and when the elapsed time is before the scheduled period of the other event, the storage unit stores the scheduled period. A control unit that maintains the stored scheduled period of the other event,
A scheduling device characterized by having.

(Appendix 7) The computer
Accepts the actual period during which any of the multiple events that occur in sequence is executed,
The scheduled period for executing each event of the plurality of events and the period to be secured until each event is executed after the execution of the event before each event is stored in association with each event. The scheduled period of the other event is the time when the period associated with the other event scheduled to be executed after the scheduled period of any of the events elapses after the actual period with reference to the storage unit. Determine if it is later,
When it is determined that the elapsed time point is later than the scheduled period of the other event, the scheduled period of the other event stored in the storage unit is changed to a period after the elapsed time point, and the elapsed time is described. If the time point is before the scheduled period of the other event, the scheduled period of the other event stored in the storage unit is maintained.
A scheduling method characterized by performing processing.

clia to clic Customer e1 to e4 Event sr Support staff 101 Scheduling device 110, 520 Storage unit 511 Reception unit 512 Display unit 513 Registration unit 514 Judgment unit 515 Change unit

Claims (6)

On the computer
The scheduled period for executing each event of a plurality of events to be performed in sequence, and the minimum and maximum period to be secured before executing each event after executing the event before each event. With reference to the storage unit that stores in association with each event ,
The maximum period associated with the second event is added from the period obtained by adding the minimum period associated with the second event following the first event to the scheduled period of the first event. The period up to the above period is divided into a plurality of periods and displayed as candidate periods for the scheduled period of the second event.
Corresponding to the third event from the period obtained by adding the minimum period associated with the third event following the second event to each period corresponding to each of the plurality of periods. The period up to the period including the maximum period attached is displayed as a candidate period for the scheduled period of the third event.
A scheduling program characterized by executing processing. The process of displaying the candidate period of the scheduled period of the second event is
Each of the periods is displayed with different patterns and / and colors between the periods.
The process of displaying the candidate period of the scheduled period of the third event is
Corresponding to each of the above periods, from the period obtained by adding the minimum period associated with the third event to each of the above periods to the period obtained by adding the maximum period associated with the third event. The space is displayed with the same pattern as the pattern given in each period, and / and the same color as the color given in each period.
The scheduling program according to claim 1. When the actual period in which the first event is executed is accepted, the computer is notified.
After the actual period, it is determined whether or not the time point at which the minimum period associated with the second event elapses is later than the scheduled period of the second event.
When it is determined that the elapsed time point is later than the scheduled period of the second event, the scheduled period of the second event stored in the storage unit is changed to a period after the elapsed time point. When the elapsed time is before the scheduled period of the second event, the scheduled period of the second event stored in the storage unit is maintained.
The scheduling program according to claim 1 or 2, wherein the processing is executed. The storage unit
Each event of the plurality of events is either one of the first type of the event executed by the person who provides the service or the second type of the event executed by the person who receives the service. Memorize the information that identifies
The first event and the third event are events of the second type, and the second event is an event of the first type.
The scheduling program according to any one of claims 1 to 3. The scheduled period for executing each event of a plurality of events to be performed in sequence, and the minimum and maximum period to be secured before executing each event after executing the event before each event. a storage unit that stores in association said each event,
Corresponding to the second event from the period obtained by adding the minimum period associated with the second event following the first event to the scheduled period of the first event with reference to the storage unit. The period up to the period including the maximum period attached is displayed as a candidate period for the scheduled period of the second event by dividing it into a plurality of periods, and corresponding to each period of the plurality of periods. From the period obtained by adding the minimum period associated with the third event following the second event to the period obtained by adding the maximum period associated with the third event. A control unit that displays the interval as a candidate period for the scheduled period of the third event, and
A scheduling device characterized by having. The computer
The scheduled period for executing each event of a plurality of events to be performed in sequence, and the minimum and maximum period to be secured before executing each event after executing the event before each event. With reference to the storage unit that stores in association with each event ,
The maximum period associated with the second event is added from the period obtained by adding the minimum period associated with the second event following the first event to the scheduled period of the first event. The period up to the above period is divided into a plurality of periods and displayed as candidate periods for the scheduled period of the second event.
Corresponding to the third event from the period obtained by adding the minimum period associated with the third event following the second event to each period corresponding to each of the plurality of periods. The period up to the period including the maximum period attached is displayed as a candidate period for the scheduled period of the third event.
A scheduling method characterized by performing processing.

Images