JP6039791B2 - Schedule determination apparatus and determination method - Google Patents

Description

  The present invention relates to a schedule determination apparatus and a determination method for determining an execution schedule of a manual operation performed by an operator or an operation performed by software for cloud service operation.

  In order to operate cloud services, it is essential to reduce operational management costs (OPEX), and the key is how efficiently operators can operate the services. In cloud service operation, an operator works according to some routine operation work flows (operation routine flow) of the infrastructure that constitutes the cloud service, in response to a request from a customer who receives the service. An administrator who supervises the operator assigns an operation work flow of the cloud service to the operator. The operator works according to the operation work flow assigned by the administrator. An operator may be assigned multiple operational workflows at the same time.

  Such an operation work flow is a series of processes composed of a plurality of operations (the operation may be further subdivided into a plurality of tasks), and the operator installs management software corresponding to each operation. In order to reduce IT operation management costs and operational errors, these operational workflows tend to be automatically executed as much as possible. A representative technology is Run Book Automation (RBA).

  Japanese Patent Application Laid-Open No. 2004-228561 discloses a content in which a business procedure is defined as a workflow in order to automate a business process, and each procedure constituting the workflow is sequentially executed by a workflow control device. The RBA technology listed above can be regarded as an application of the business process automatic execution technology disclosed in Patent Document 1 to operation management operations.

  Furthermore, Patent Document 2 discloses a technique for managing a schedule of a device and its worker. The schedule is adjusted so that there is no duplication of the device usage occupancy time by shifting the device usage occupancy time and the operator work time.

JP2009-80581A JP 2006-285784 A

  In the series of operations shown in the operation routine flow, there is always an approval task, a visual confirmation task, and a task that does not provide an API and only has to work through the GUI. Execution is difficult. When there is a task (manual task) that requires such human work (approval, visual confirmation, work via GUI), if the work is assigned sequentially, the operator (approver for the approval task) is assigned. Since it is restrained manually, the operator cannot perform other operations. Therefore, an operation execution schedule determination device and a determination method that shorten the time for restraining the operator are required.

  The schedule determination device to be disclosed is realized by a management server connected to a management terminal. The management server receives a scenario execution request from the management terminal, determines the scheduled start time and scheduled end time of the operations constituting the scenario, and secures the schedule of operators and equipment that execute operations that satisfy these times, When the scheduled end time of the operation according to the secured schedule satisfies the deadline time included in the execution request, the execution schedule management unit displays the secured schedule on the management terminal, and the management terminal displays the restraint time display request. The operator's schedule is acquired, and operations whose scheduled operation start time is within the specified time are grouped. From the grouped operations, the earliest scheduled start time of the operation is started. In addition, a schedule evaluation unit that obtains the time until the scheduled end time of the operation with a later scheduled end time as an operator's restraint time and displays it on the management terminal is provided. Operation, the operator's schedule is acquired, the operations whose scheduled operation start time of the acquired schedule is grouped within a predetermined time, and when there is an operation that can adjust the schedule among the grouped operations, the adjustable operation The time between the scheduled start time of the operation with the earliest scheduled start time and the scheduled end time of the operation with the latest scheduled end time of the group including the rescheduled operation Determined as the time, a new constraint time is shorter than the restraint time schedule evaluation unit is determined to display the operator's schedule including a schedule and a new duty time and reschedule the management terminal.

  According to the present invention, it is possible to determine an operation execution schedule that shortens the time for restraining the operator.

FIG. 3 is a system configuration diagram showing a management server that determines an operation execution schedule and its management target. It is a figure which shows an example of a scenario definition table. It is a figure which shows an example of a scenario instance table. It is a figure which shows an example of an operator schedule management table. It is a figure which shows an example of an apparatus schedule management table. It is a flowchart which shows the process by the execution schedule management part when a scenario execution request is received. It is a figure which shows the process in which an execution schedule evaluation part calculates an operator's restraint time. It is a figure which shows the process rescheduled by the execution schedule management part so that the operator's restraint time may be shortened. It is a flowchart which shows the request destination of operation by the execution schedule management part, and the process which temporarily secures the schedule. It is a processing flowchart of the 1st processing example which specifies the operator who satisfy | fills a request destination condition. It is a processing flowchart of the 2nd processing example which specifies the operator who satisfy | fills a request destination condition. It is a processing flow figure of the 3rd processing example which specifies an operator who satisfies a demand destination condition. It is a processing flow figure of the 4th example of processing which specifies an operator who fulfills a demand destination.

  Hereinafter, modes for carrying out the invention will be described. In this embodiment, in response to an operation scenario execution request including a plurality of operations including an operator's manual task, the execution order and execution timing of the operation including the manual operation are adjusted to adjust the execution order and execution of the operation. Determine timing. In this decision, operations including manual tasks with similar execution start times are grouped, and the time from the earliest start time to the latest end time of operations within each group is defined as the operator's constraint time, and this constraint time is short. The execution timing and execution order are determined as follows.

  FIG. 1 is a system configuration diagram showing a management server that determines an operation execution schedule and its management target. The management server functions as a schedule determination device. In this system, a management server 101 and a management terminal 102 are connected via a management IP network 107. The management server 101 is connected to a device for providing a cloud service, such as a management target server or storage device, via the management IP network 107, but is not shown.

  The management server 101 performs scheduling to determine the execution order and execution timing of operations. The management server 101 can be composed of a general computer and includes a central processing unit 111, a main storage device 112, and an external storage device 113.

  The main storage device 112 stores an execution schedule evaluation unit 130, an execution schedule management unit 131, an operator schedule management unit 132, an equipment schedule management unit 133, and a scenario execution unit 134, and is read into the central processing unit 111. As a result, the function of each processing unit is executed.

  The execution schedule evaluation unit 130 evaluates the operation schedule. Specifically, based on the schedule of operations including the current manual task, the operator's restraint time is calculated and the current schedule is evaluated.

  The execution schedule management unit 131 manages a schedule of an operator (referred to collectively as an operator although referred to as an operator, an approver, an administrator, etc. depending on the role) and a device schedule. The execution schedule management unit 131 accepts an execution request for an operation scenario (hereinafter referred to as a scenario) from the management terminal 102 or an operation reschedule request from the management terminal 102, so that the operator's restraint time is shortened. Schedule. The execution schedule evaluation unit 130 calculates the constraint time. Specific processing steps will be described later.

  The operator schedule management unit 132 manages the operator's schedule. The operator schedule includes an operation schedule including an operator's manual task related to the scenario, and a meeting schedule not related to the scenario. The operator schedule management unit 132 manages the operator's schedule, displays the operator's schedule information, and accepts the operator's schedule change request.

  The device schedule management unit 133 manages a device usage schedule. The device usage schedule includes a task schedule registered in the device management software.

  The scenario execution unit 134 sequentially executes scenarios requested to be executed from the management terminal 102. The scenario execution unit 134 sequentially executes each operation constituting the scenario. If the operation is an automatic execution task for a device, a task execution request is issued to the device. If the operation is a manual task, a notification indicating an execution request is sent to the corresponding operator.

  The external storage device 113 includes a scenario definition table 200, a scenario instance table 300, an operator schedule management table 400, and a device schedule management table 500.

  The scenario definition table 200 is a table that defines the contents of a scenario. A scenario is a predefined sequence of operations. A scenario includes at least one operation.

  FIG. 2 is a diagram illustrating an example of the scenario definition table 200. Each record of the scenario definition table 200 indicates scenario definition information. When there are a plurality of operations constituting a scenario, records are registered in the order in which the operations are executed. “#” In each figure indicates an identifier. The scenario definition table 200 includes a scenario template identifier 201, a scenario content 202, an operation identifier 203, a request destination condition 204, and a requested operation content 205.

  The scenario template identifier 201 is a scenario identifier. The scenario content 202 is the content of the scenario. The operation identifier 203 is an identifier of each operation constituting the scenario. The request destination condition 204 is condition information of an operation request destination. If the operation requires execution of management software, this information is information for specifying the management software. In the case of a manual operation, this is information for specifying an operator to be executed. The requested operation content 205 is the content of the operation.

  The scenario instance table 300 is a table that stores the execution state and execution schedule of a scenario in response to a scenario execution request from the management terminal 102. The scenario requested to be executed from the management terminal 102 is registered in the scenario instance table 300 with reference to the scenario definition table 200.

  FIG. 3 is a diagram illustrating an example of the scenario instance table 300. The scenario instance table 300 includes a scenario 301, an operation identifier 305, a request destination 306, an execution state 307, and a time 308. The scenario 301 includes a scenario instance identifier 302, a scenario template identifier 303, and scenario contents 304. The time 308 includes the scheduled start time 309, the scheduled end time 310, the actual start time 311, the actual end time 312, and the scenario deadline time 313 of the operation 305 to be executed.

  The scenario 301 is content representing a scenario. The scenario instance identifier 302 is an identifier for identifying a scenario instance. The scenario template identifier 303 is an identifier for identifying the original scenario definition of the scenario instance. The scenario content 304 is the content of a scenario executed with a scenario instance. The operation identifier 305 is an identifier for identifying operations constituting the scenario instance.

  For example, if the content of the scenario requested to be executed from the management terminal 102 is “virtual server deployment”, “SI1” is attached as the scenario instance identifier 302 to the scenario requested to execute, and the scenario definition table 200 is referred to. , Scenario template identifier 201 “ST1” corresponding to “virtual server deployment”, scenario content 202 “virtual server deployment”, and operation identifier 203 “OP1, OP2,. A template identifier 303, scenario contents 304, and an operation identifier 305 are used.

  The request destination 306 is a request destination that requests execution of the operation specified by the operation identifier 305. The request destination for requesting the execution of the operation is information for specifying specific management software or information for specifying an operator who performs a manual operation.

  The execution state 307 is an execution state of the operation specified by the operation identifier 305. The execution state of the operation includes execution states such as reception complete, schedule adjustment, temporary provisional reservation, full schedule reservation, execution in progress, execution completion.

  The reception completion state indicates a state in which the management server 101 receives a scenario execution request from the management terminal 102, and the request destination 306, the scheduled start time 309, and the scheduled end time 310 for requesting the execution of each operation of the scenario are undetermined. The schedule adjustment in progress state indicates a state in which processing for determining a request destination 306 for requesting execution of each operation of the scenario, a scheduled start time 309, and a scheduled end time 310 is being executed.

  The temporary schedule secured state is a state in which a consistent schedule for each operation of the scenario is being secured, and the schedule of the operator who executes each operation and the equipment required for the execution of the operation (the target device of the operation) is temporarily held. . For example, the request destination 306, scheduled start time 309, and scheduled end time 310 are determined for an operation 305 having a scenario 301, but the request destination 306, scheduled start time 309, and scheduled end time are determined for other operations 305 that constitute the scenario 301. 310 indicates an undetermined state. The operator indicating the request destination 306 and the target device of the operation also have a schedule for executing the operation from the scheduled start time 309 to the scheduled end time 310.

  The secured schedule state indicates a state where the scenario schedule has been secured. For each operation constituting the scenario, the request destination 306, the scheduled start time 309, and the scheduled end time 310 are determined. An operator indicating the request destination and a target device of the operation also have a schedule for executing the operation from the scheduled start time 309 to the scheduled end time 310. Execution of the scenario operation is not started in the secured schedule state.

  The in-execution state indicates that the operation according to Nario has been started and is being executed. The execution completion state indicates a state in which execution of each operation of the scenario is finished.

  Time 308 is an operation execution schedule schedule and execution result schedule information. The scheduled start time 309 is a scheduled time for starting execution of the operation. The scheduled end time 310 is a scheduled time when the execution of the operation is ended. The actual start time 311 is the time when the execution of the operation is started. The end record time 312 is the time when the execution of the operation is ended. The scenario deadline time 313 is time limit information designated when a time limit is set at the end time in accordance with a scenario execution request from the management terminal 102.

  The processing of the scenario execution unit 134 using the scenario instance table 300 and the scenario definition table 200 will be briefly described. The scenario execution unit 134 sequentially executes the operations identified by the template identifier 303 and the operation identifier 305 for each instance of the scenario instance table 300. It controls the execution of the operations and tasks defined by the requested operation content 205 indicated by the scenario template identifier 201 and the operation identifier 203 of the scenario definition table 200 corresponding to the template identifier 303 and the operation identifier 305. The scenario execution unit 134 issues an operation execution request to the request destination 306 of the scenario instance table 300. If the operation is an operation to management software or a device, an operation execution request is issued to the management software or device. On the other hand, when the operation is a manual operation, the operation of the operation is requested by transmitting an email requesting the operation to the operator of the request destination 306 or by transmitting a message or event information requesting the operation. . . When the operation is started, the time when the operation is started is stored as the actual start time 311. When it is detected that the operation is finished, the time when the operation is finished is stored as the end result time 312. Then, the execution state 307 is changed to the execution completion state, and the operation following the operation is started. In this way, when execution of all the series of operations belonging to the scenario instance is completed, execution of the scenario instance is completed.

  The operator schedule management table 400 is a table that stores an operator's work schedule.

  FIG. 4 is a diagram illustrating an example of the operator schedule management table 400. The operator schedule management table 400 includes an administrator identifier 401, an operator name 402, a team 403, a role 404, an authority 405, a start time 406, an end time 407, a scheduled content 408, a related operation 409, a secured state 410, and an adjustment availability 411. Contains.

The administrator identifier 401 is an identifier that identifies an operator or the like. The operator name 402 is name information of the operator, and the team 403 is affiliation information such as a team or a group to which the operator belongs. The role 404 is the role information of the operator, the authority 405 is the authority information held by the operator, the start time 406 is the scheduled start time of the operator's schedule, and the end time 407 is the scheduled end time of the operator's schedule. The schedule content 408 is information on the schedule of the operator. The related operation 409 is identifier information of the operation when the schedule of the operator is registered by the operation scheduling requested by the first management server 101.

  The secured state 410 is a state secured so that the operator's schedule is being adjusted or no other schedule is entered, and is temporarily secured during the scenario schedule adjustment, or the scenario schedule adjustment is completed. Status information indicating that the reservation (start time 406, end time 407, scheduled content 408, and related operation 409) is secured. When the schedule is being adjusted or not in the secured state, the secured state 410 is null (empty). When the state is temporarily secured during schedule adjustment, the state information indicates a provisional secured state. In addition, when the schedule adjustment is completed and the reservation is secured, the status information indicates the secured status.

  The adjustment availability 411 indicates whether or not the execution time (start time 406 and / or end time 407) of the operator can be changed. True indicates adjustable, False indicates non-adjustable. A reservation that has already been executed becomes False because it cannot be adjusted.

  The device schedule management table 500 is a table for storing schedule information of operations requested to be executed by the management software for managing devices and devices.

  FIG. 5 is a diagram illustrating an example of the device schedule management table 500. The device schedule management table 500 includes an operation request destination identifier 501, a device identifier 502, a task identifier 503, task contents 504, an execution state 505, a start time 506, an end time 507, a related operation 508, a reservation state 509, and adjustment availability 510. Contains.

  The operation request destination identifier 501 is an identifier for identifying a device or management software determined by the execution schedule management unit 131 or the device schedule management unit 133 of the management server 101 as an operation request destination (request destination 306 of the scenario instance table 300). .

  The device identifier 502 is an identifier of a device that executes a task that constitutes an operation. When the management software or device identified by the operation request destination identifier 501 is a device or the like that is the actual execution destination of the task, it is the identifier of the device. The operation requested by the operation request destination identifier 501 is composed of at least one task, and the identifier of the device that executes the task is the device identifier 502.

  The task identifier 503 is an identifier of a task that constitutes an operation. The task content 504 is the content of a task that constitutes an operation. The execution state 505 is an execution state of tasks constituting the operation. The execution state of the task includes states such as unexecuted, executing, and execution completed.

  The start time 506 is the execution start time of the task that constitutes the operation. The end time 507 is the execution end time of the task constituting the operation.

  The related operation 508 is the operation identifier 305 of the scenario instance table 300 that identifies the operation if the task is a task constituting the operation requested to be executed from the scenario execution unit 134.

  The secured state 509 is a state secured so that the device schedule is being adjusted or other schedules are not entered, and is temporarily secured during the scenario schedule adjustment, or the scenario schedule adjustment has been completed. Status information indicating that reservations (start time 506, end time 507, and related operation 508) are secured. When the schedule is being adjusted or is not in the secured state, the secured state 509 is null (empty). When the state is temporarily secured during schedule adjustment, the state information indicates a provisional secured state. In addition, when the schedule adjustment is completed and the reservation is secured, the status information indicates the secured status.

  The adjustment availability 510 indicates whether or not the execution time (start time 506 and / or end time 507) of the schedule of the device can be changed. True indicates adjustable, False indicates non-adjustable. A task that has already been executed becomes False because it cannot be adjusted.

  FIG. 6 is a flowchart showing processing of the execution schedule management unit 131 when an operation scenario execution request (hereinafter, scenario execution request) is received from the management terminal 102.

(1) A scenario execution request is accepted (step 601).
The scenario execution request includes a scenario template identifier for specifying the content of the scenario to be executed, and deadline information specifying a time at which the scenario execution must be completed.

(2) The scenario information is acquired from the scenario execution request (step 602).
A scenario template identifier is acquired from the scenario execution request received in step 601. Based on this scenario template identifier, the scenario template identifier 201 in the scenario definition table 200 is searched to identify a record with a matching scenario template identifier. In this specified record, the definition contents of the scenario requested to execute the scenario are stored. From this scenario definition, the operation (operation identifier 203 and requested operation content 205) constituting the scenario and the condition information (request destination condition 204) of the request destination of the operation are acquired.

(3) A scenario instance is generated and registered (step 603).
A new scenario 301 record corresponding to the scenario execution request is generated in the scenario instance table 300. In the scenario instance identifier 302, a unique identifier for identifying a record is set. Information on the record of the scenario definition table 200 identified in step 602 is set in the record. As the template identifier 303, the scenario template identifier 201 of the record specified in step 602 is set. In the scenario content 304, the scenario content 202 identified in step 602 is set. In the operation number 305, the operation identifier 203 of the record specified in step 602 is set.

  In the execution state 307, a reception completion state is set. Nothing is set in the request destination 306, the scheduled start time 309, the scheduled end time 310, the actual start time 311, and the actual end time 312. In the deadline time 313, a time as deadline information included in the scenario execution request received in step 601 is set.

  (4) Steps 605 and 606 are executed for the operation 305 constituting the set scenario 301 (step 604). If there are multiple operations 305, they are executed for each of them.

(5) The scheduled start time 309 and scheduled end time 310 of each operation are calculated (step 605).
A record representing the operation identified by the operation identifier 305 constituting the new scenario 301 in the scenario instance table 300 generated in step 603 is specified, and the scheduled start time 309 and scheduled end time 310 of the operation of the record are set.

  If the operation start scheduled time 309 is the first operation of the scenario 301, the current time is set. In the case of the second and subsequent operations of the scenario 301, the time after the scheduled end time of the immediately preceding operation is set as the scheduled start time 309 of the operation. If the operation schedule provisional reservation fails in step 606, which will be described later, and step 605 is executed again, a time different from the scheduled start time and end time of the operation for which provisional reservation has failed fails. Scheduled time. The operation end scheduled time 310 is calculated by adding the operation execution time to the operation start scheduled time 309.

  The execution time used for calculating the scheduled operation end time 310 is estimated from the execution history of the same or similar operations executed in the past. The process estimated from the execution history of the same operation is shown. In step 604, a record corresponding to the operation to be processed is specified from the scenario instance table 300, and its operation identifier 305 is specified. Each operation identifier 305 in the scenario instance table 300 is the same as the identified operation identifier, and a record in which the execution state 307 is completed is searched. The execution time of the same operation executed in the past is calculated from the difference between the end record time 312 and the start record time 311 of the record hit by the search. When there are a plurality of the same operations executed in the past, a statistical value such as an average value or a maximum value of the calculated execution times may be calculated as the operation execution time.

(6) The request destination 306 of the operation constituting the scenario 301 is specified, and the schedule of the specified request destination 306 is provisionally secured (step 606). Details of this step will be described later with reference to FIG.
The operator or device that executes the operation of the scenario 301 is determined, and the schedule of the determined operator or device is secured by using the operation start time 309 to the end time 310 as the time for executing the operation. If a schedule of operations constituting the scenario 301 (actually, a schedule of an operator or a device that executes the operation) can be secured, the schedule is secured in the form of provisional reservation in the sense that the schedule is unconfirmed. If the schedule of all the operations constituting the scenario 301 can be provisionally secured, the schedule of each operation constituting the scenario 301 is changed to the actual reservation, assuming that the schedule of the scenario 301 can be secured.

(7) It is determined whether the request destination 306 for executing each operation constituting the scenario 301 has been determined by the processing from step 604 to step 606 (step 607).
As a result of the determination, if the request destination 306 for executing each operation can be determined, the process proceeds to step 608. If there is an operation for which even one request destination 306 could not be determined, the process proceeds to step 618.

  Whether or not the request destination 306 for executing each operation of this step has been determined is determined by determining that the execution state 307 has been temporarily reserved for all the operations stored in the scenario instance record generated in step 603 in the scenario instance table 300. Judgment is made.

(8) It is determined whether the scheduled end time 310 of the scenario 301 satisfies the deadline 313 requested by the scenario 301 (step 608).
All the operations stored in the scenario instance record generated in step 603 are referred to the scheduled end time 310 and compared with the time of the deadline 313. As a result of the comparison, if the latest time of the scheduled end time 310 is earlier than the time of the deadline 313, it is determined that the deadline is satisfied. If the latest time of the scheduled end time 310 is later than the time of the deadline 313, it is determined that the deadline is not satisfied.

  (9) If the determination result of step 608 is YES (deadline is satisfied), the process proceeds to step 611. If the determination result is NO (does not satisfy the deadline), the process proceeds to step 618 (step 609).

(10) A message to the effect that the scenario execution request has been accepted is displayed on the management terminal 102 and the process ends (step 611).
For all the operations stored in the scenario instance record generated in step 603, the execution state 307 is changed to the scheduled book secured state. After changing to the secured state, a message to the effect that the scenario execution request has been accepted is displayed to the management terminal 102 that is the request source in step 601.

(11) If the result of determination in step 607 or step 609 is NO, it is determined whether all candidates (A) and (B) described later have been determined (step 618).
For all operations described in the scenario instance record generated in step 603, the execution state 307 is changed to a schedule adjustment state. Further, the request destination 306, the scheduled start time 309 and the scheduled end time 310 of the operation are initialized and returned to the blank.

  (12) If the result of the determination at step 618 is YES, the process proceeds to step 620. In this case, it is indicated that even if there is no request destination 306 of the operation 305 constituting the scenario 301, the schedule of the request destination 306 cannot be secured even if there is, and the execution request for the scenario 301 cannot be accepted.

  If the result of determination in step 618 is NO, the process proceeds to step 612 (step 619). In this case, there is a possibility that the operation 305 can be executed if there is another request destination 306 of the operation 305 that constitutes the scenario 301 or if the schedule of a candidate device or operator that executes the operation 305 is adjusted.

  (13) An error message indicating that the scenario execution request cannot be accepted is displayed on the management terminal 102, and the process ends (step 620).

(14) If the result of determination in step 619 is NO, it is determined whether there is another request destination candidate (A) that can execute operation 305 (step 612).
Based on the condition information of the request destination of operation 305 acquired in step 602, operation 305 determines whether to request the operator to execute or to request the device to execute.

  If the operation 305 is a request to the operator, the operator schedule management table 400 is searched for the operator name 402 of the team 403, the role 404, and the authority 405 that satisfies the request destination condition acquired in step 602. It is determined whether there is another request destination candidate (A) that can be executed by determining whether there is a record for which the processing from step 604 to step 606 has not been executed.

  If the operation 305 is an execution request to the device, the operation request destination identifier 501 that satisfies the request destination condition acquired in step 602 is specified by searching the device schedule management table.

  (15) If the result of the determination at step 612 is YES, the process proceeds to step 614. If NO, the process proceeds to step 615 (step 613).

(16) Specify another request destination of the operation, and proceed to Step 605 (Step 614).
One of the request destination candidates specified in step 612 is selected, and the flow advances to step 604 to determine a request destination candidate specified in the subsequent processing.

(17) If the result of determination in step 613 is NO, it is determined whether there is a schedule adjustment candidate (B) for the device or operator (step 615).
Whether or not the schedule of the device can be adjusted is determined based on whether or not the adjustment availability 510 of the device schedule management table 500 is true if the schedule to be adjusted is a device schedule. If the adjustment availability 510 is True, the schedule can be adjusted.
If the schedule to be adjusted is an operator's schedule, the determination is made based on whether the adjustment availability 411 of the operator schedule management table 400 is true. If the adjustment availability 411 is True, the operation can be adjusted for the schedule.

  (18) If the result of determination in step 615 is YES, the process proceeds to step 617, and if NO, the process proceeds to step 618 (step 616).

(19) Adjust other schedules of the device and operator and proceed to Step 604 (Step 617).
In the readjustment of the schedule in step 617, the scenario 301 to which the operation to be readjusted determined to be adjustable in step 615 belongs is specified from the scenario instance table 300, and the schedule of all the operations constituting the scenario 301 is readjusted. For the operation to be readjusted, the same processing as in steps 604 to 606 is executed, and the time zone schedule excluding the time zone from the scheduled start time 309 before readjustment to the scheduled end time 310 before readjustment. Try to secure.
If the schedule cannot be readjusted in step 617, all request destinations cannot be determined in step 607 after step 606, and the scenario execution request cannot be accepted as a determination result in step 619.

  FIG. 7 is a flowchart showing a process in which the execution schedule evaluation unit 130 calculates and displays the operator's constraint time in response to the operator's constraint time display request. The execution schedule evaluation unit 130 calculates the operator's constraint time based on the schedule at the time when the constraint time display request is received.

(1) An operator's request for displaying the restraint time is received from the management terminal 102 (step 701).
The display request includes operator identification information for specifying an operator to display the restraint time.

(2) The schedule information of the display request target operator is acquired (step 702).
The administrator identifier 401 in the operator schedule management table 400 is searched, and schedule information (start time 406, end time 407, schedule content 408) of the record with the administrator identifier 401 that matches the operator identification information included in the display request is acquired. . When there are a plurality of administrator identifiers 401 that match the operator identification information, schedule information is acquired for each record corresponding to each. Each record corresponds to an operation.

(3) The scheduled operations are grouped (step 703).
Operations that are close in time are grouped, and a constraint time is calculated for the grouped operations. For example, when the execution schedule evaluation unit 130 has a time threshold and the start time 406 is within the threshold time from the current time, the operation is grouped as one group. And
Another grouping method may be as follows. If the time from the end time 407 of a certain operation to the start time 406 of another adjacent operation is less than or equal to the threshold time, a certain operation and another operation are made the same group, and if the time is longer than the threshold time, a different group To do.

(4) The operator restraint time is calculated from the difference between the predicted start time of the operation with the earliest start time in the group and the predicted end time of the operation with the latest end time (step 704).
All the records of the operator schedule management table 400 corresponding to the grouped operations are searched, and the time from the earliest start time 406 to the latest end time 407 of the operations in the group is set as the operator binding time.
In this way, operations close to the target operator are grouped, and the time from the earliest start time 406 to the latest end time 407 of the operations in the group is set as the constraint time. By doing so, it is possible to prevent the time between operations that are not close to each other (exceeding the threshold time), that is, the free time of the operator from being added as the constraint time for the operation execution.

  It is assumed that these constraint times calculated for each group correspond to the operator's constraint time display request. Further, the maximum value, the average value, the minimum value, or the evaluation value (for example, five-step evaluation) calculated according to a predetermined evaluation formula may be calculated as the constraint time index. The selection of these indices may be based on the way (parameters, etc.) of the operator's request to display the restraint time.

  (5) The operator's binding time is output to the management terminal 102 (step 705).

  FIG. 8 is a flowchart illustrating processing in which the execution schedule management unit 131 reschedules (schedules changes) an operator's operation in order to shorten the operator's binding time.

(1) A schedule change request for requesting shortening of the operator's restraint time is received from the management terminal 102 (step 801).
The schedule change request message includes operator identification information that is identification information for specifying an operator to be restrained for shortening.

(2) Obtain schedule information (step 802).
The administrator identifier 401 in the operator schedule management table 400 is searched, and the schedule information (start time 406, end time 407, schedule content 408) of the record with the administrator identifier 401 that matches the operator identifier information included in the schedule change request is acquired. To do. When there are a plurality of administrator identifiers 401 that match the operator identification information, schedule information is acquired for each record corresponding to each.

(3) Group multiple scheduled operations (step 803).
Similar to step 703, the operations are grouped.

  Subsequently, in steps 804 to 808, the shortest constraint time of the operator designated in the schedule change request is calculated. The operator's constraint time is calculated for each adjustable schedule candidate, and if the calculated constraint time is shorter than the previously calculated constraint time, the newly calculated constraint time is temporarily stored internally, so that the shortest constraint Calculate time.

(4) The operator restraint time (A) is calculated from the difference between the predicted start time of the operation with the earliest start time in the group and the predicted end time of the operation with the latest end time (step 804).
The restraint time is calculated as in step 704. Specifically, the difference between the earliest start time 406 and latest end time 407 of the operations in the group is defined as the operator restraint time (A).

(5) It is determined whether the calculated operator restraint time (A) is shorter than the stored operator restraint time (B) (step 805).
In step 805, it is determined whether the newly calculated operator constraint time (A) is shorter than the operator constraint time (B) temporarily stored in the execution schedule management unit 131 in step 807 described later. When step 805 is executed for the first time, the operator restraint time (B) is not stored, so the determination here is YES.

(6) If YES in step 805, the process proceeds to step 807. If NO, the process proceeds to step 808 (step 806).
If the determination in step 805 is YES, this indicates that there is a schedule candidate with a shorter constraint time (a newly calculated operator constraint time (A). If NO, the operator constraint time temporarily stored is stored. (B) has shown that it is shorter than the newly calculated operator restraint time (A).

(7) The scheduling information (C) and the operator restraint time (A) calculated at that time are stored (step 807).
Since the newly calculated operator restraint time (A) is a shorter restraint time, the newly calculated operator restraint time (A) is used as the operator restraint time (B), and the schedule adjustment candidates (start time 406, end time 407). The execution schedule management unit 131 temporarily stores the scheduled contents 408) as scheduling information (C).

(8) It is determined whether there is another schedule adjustment candidate capable of adjusting the operator's schedule in the group (step 808).
Referring to operator schedule management table 400, it is determined whether there is a schedule adjustment candidate.

(9) If YES in step 808, the process proceeds to step 811. If NO, the process proceeds to step 810 (step 810).
In the case of YES, the process proceeds to step 811 in order to evaluate the constraint time of other schedule adjustment candidates determined in step 808. In the case of NO, it is determined that the constraint time of all schedule adjustment candidates has been evaluated, and the process proceeds to Step 810.

(10) Reschedule the operator's schedule within the group and proceed to step 804 (step 811).
In step 811, a change schedule candidate obtained by changing the schedule of the adjustable schedule belonging to the group in the group is obtained, and the steps after step 804 subsequent to the change schedule candidate are executed.

  (11) If NO in step 809, the stored restraint time (B) and schedule information (C) at that time are output (step 810).

  The execution schedule management unit 131 outputs the constraint time (B) and scheduling information (C) stored therein to the management terminal 102 and waits for a schedule change confirmation request from the management terminal 102.

  (12) It is determined whether a confirmation request for schedule change has been received (step 812).

(13) If YES in step 812, the process proceeds to step 814. If NO, the process proceeds to step 815 (step 813).
In the process of waiting for the schedule confirmation request in step 812, if a schedule confirmation request is received, the process proceeds to step 814. If a message for canceling the schedule change is received, the process proceeds to step 813. If there is no message, wait for a confirmation request message.

(14) The operator's schedule is changed based on the schedule information (C) (step 814).
The execution schedule management unit 131 updates the contents of the changed operator schedule management table 400 with the scheduling information (C) stored therein.

(15) A message indicating that the operator's schedule has been changed is output to the management terminal 102 (step 815).
FIG. 9 is a flowchart showing a process of determining a request destination (operator or device) for executing an operation by the execution schedule management unit 131 and temporarily securing a schedule of the request destination (operator or device). A case where step 606 of FIG. 6 is processed as a subroutine will be described as an example.

(1) An operation request destination determination request is accepted (step 901).
In the operation request destination determination request, operation identification information 305 for identifying an operation for which the request destination 306 is determined, condition information (request destination condition 204) for specifying the request destination for securing the schedule 306, and the operation destination information 305 are to be secured. The scheduled start time 309 of the schedule and the scheduled end time 310 of the schedule to be secured are included.

The request destination condition 204 includes request destination type information indicating whether the operation is to be executed by the operator to be determined as the request destination or the operation is automatically executed by the device.
Further, in the case of an operation executed by the operator, the request destination condition 204 includes condition information for specifying the team to which the operator belongs, condition information for specifying the role or authority of the operator, and the like. When the operation is executed by a plurality of operators, it includes condition information for specifying a team required for the operator for each operator, condition information for specifying a role, and authority. Hereinafter, such condition information for each operator is referred to as a member condition. The request destination condition is composed of one or more member conditions.
When the request target is a device, it includes condition information for specifying an operation request destination that is a request destination of a task for operating the device.

(2) The operation identifier, request destination condition, scheduled start time, and scheduled end time are specified (step 902).
The operation identifier 305, the request destination condition 204, the scheduled start time 309, and the scheduled end time 310 included in the operation request destination determination request are acquired.

(3) The type of operation request destination is determined (step 903).
If the request destination 306 of the operation that satisfies the request destination condition 204 is a device, the process proceeds to step 915. If the request destination 306 is an operator, the process proceeds to step 904.

  (4) If there are a plurality of operators designated as the operation request destinations 306, the process proceeds to step 905. If the designated operator is one person, the process proceeds to step 917. (Step 904).

  (5) Steps 906 to 909 are executed for each operator constituting the operator set designated as the operation request destination 306 (step 905).

  The operator member conditions included in the request destination condition 204 acquired in step 902 are acquired one by one, and the steps from step 906 to step 909 are executed.

  (6) An operator that satisfies the request destination condition 204 is specified (step 906). Details of the processing in this step will be described later with reference to FIGS. 10, 11, 12, and 13.

  Based on the specified member condition, an operator satisfying the request destination condition 204 is specified.

(7) The specified person's schedule is temporarily secured from the scheduled start time to the scheduled end time of the operation (step 907).
The operator schedule management table 400 is searched based on the operator name 402 specified in step 906, and a new record with the reservation state 410 set to “provisional reservation state” is added. The start time 406 of the newly added record is set as the scheduled start time 309 acquired in step 902, and the end time 407 is set as the scheduled end time 310 acquired in step 902.

(8) If the processing from step 906 to step 908 has been executed for the member condition, the process proceeds to step 910. If not executed, the process proceeds to step 909 (step 908).
When the processing from step 906 to step 909 for specifying the operator is executed for all the member conditions acquired in step 905, the process proceeds to step 910. Otherwise, go to step 909.

(9) The next member condition is specified, and the processing after step 906 is executed (step 909).
The member condition that has not been executed in steps 906 to 909 is identified based on the member condition acquired in step 905.

(10) It is determined whether the schedules of all members (operators) designated in the operation request destination condition 204 have been provisionally reserved. If there is a member (operator) that cannot be temporarily reserved, the process proceeds to step 911 (step 910).
If the processing of step 906 and step 907 is executed for all the member conditions and the record of the temporarily secured state is successfully added, the process proceeds to step 912. Otherwise, go to step 911.

(11) If there is a member (operator) who could not be secured, the temporarily secured schedule is released, assuming that the securing has failed, and the process proceeds to step 922 (step 911).
By deleting the record added in step 907 from the operator schedule management table 400, the temporarily secured schedule is released.

(12) If the schedule of all members can be secured temporarily, it is determined that a plurality of operators such as teams and groups can execute the operation at the same time. (Step 912), the temporarily secured schedule is treated as secured (Step 913).
Based on the operation identifier 305 acquired in step 902, a record corresponding to the operation stored in the scenario instance table 300 is specified. The identification information of the operator temporarily reserved is stored in the request destination 306 of the record. Further, the scheduled start time acquired in step 902 is stored as the scheduled start time 309 of the record, and the scheduled end time acquired in step 902 is stored as the scheduled end time 310 of the record.

  (13) In response to the caller of this subroutine, the last determined operator, the secured schedule, and the secured success are terminated (step 914).

(14) If it is determined in step 903 that the operation request destination is a device, a device that satisfies the request destination condition 204 is specified (step 915).
The device schedule management table 500 is searched to identify a device that matches the request destination condition 204 acquired in step 902.

(15) From the scheduled start time to the scheduled end time of the operation, the specified device schedule is provisionally reserved, and the process proceeds to step 913 (step 916).
A new record is added to the device schedule management table 500 for the device identified in step 915, and the start time 506 and the end time 507 are set as the scheduled start time 309 and the scheduled end time 310 acquired in step 902, respectively. Further, the secured state 509 is assumed to be a provisional secured state.

  (16) If it is determined in step 904 that there is only one operator, an operator that satisfies the request destination condition 204 is specified (step 917). Details of the processing in this step will be described later using FIG. 10, FIG. 11, FIG. 12, and FIG.

(17) The specified person's schedule is temporarily secured from the scheduled start time to the scheduled end time of the operation (step 918).
The operator schedule management table 400 is searched based on the operator name 402 specified in step 917, and a new record with the reservation state 410 set to “provisional reservation state” is added. The start time 406 of the newly added record is set as the scheduled start time acquired in step 902, and the end time 407 is set as the scheduled end time acquired in step 902.

(18) It is determined whether or not the schedule has been provisionally secured in step 918 (step 919). If it can be secured, the process proceeds to step 920, and if it cannot be secured, the process proceeds to step 922.
If the processing from step 917 to step 918 for specifying the operator is executed for the request destination condition 204 acquired in step 902, the process proceeds to step 920. Otherwise, go to step 922.

(19) If it is determined in step 919 that the operator has been secured, the secured operator is determined as the operation request destination (step 920).
Based on the operation identifier 305 acquired in step 902, the record of the scenario instance table 300 is specified. The operator who temporarily secures the request destination 306 of the record is used as identification information. Further, the scheduled start time 309 acquired in step 902 at the scheduled start time 309 of the record is set, and the scheduled end time 310 of the record is set as the scheduled end time 310 acquired in step 902.

  (20) The operator determined in step 920, the reserved schedule, and the fact that the reservation was successful are responded to the caller of this subroutine processing flow, and the process ends (step 921).

  (21) If it is determined in step 911 and step 919 that the schedule could not be secured, the process is terminated in response to the subroutine caller that the schedule securing of the operation has failed (step 922).

  (22) After processing step 916, it is determined whether a schedule has been temporarily secured (step 923). If it is determined that it has been secured, the process proceeds to step 924. If it is determined that it could not be secured, the process proceeds to step 926 (step 923).

(23) If it is determined in step 923 that the device has been secured, the secured device is determined as the operation request destination (step 924).
The device schedule management table 500 is searched based on the device specified in step 915, and a new record with the secured state 509 as “provisional secured state” is added. The start time 506 of the newly added record is set as the scheduled start time 309 acquired in step 902, and the end time 507 is set as the scheduled end time acquired in step 902.

  (24) In response to the caller of this subroutine, the process ends (step 925).

  25) If it is determined in step 923 that the allocation has not been ensured, the process is terminated in response to the subroutine caller that the allocation has failed (step 926).

  FIG. 10 is a process flow diagram of a first process example for identifying an operator that satisfies the request destination condition in step 906. By this processing, it is possible to assign work to the same operator for operations with high similarity between operations based on an index of operation characteristics designated in advance. Thereby, since the operator can perform the same operation continuously, the burden on the operator can be reduced.

(1) The feature of the requested operation is extracted (step 1001).
The feature of the operation is extracted based on the requested operation content 205 defined in the scenario definition table 200 and the skill and proficiency required for the operation. Although not shown in the figure, the operation contents, the category of the operation, the skill required for the operation, the proficiency level, and the correspondence table of the software (or Web site to be used) stored in advance in the external storage device 113 (operation characteristic table) ) To obtain operation characteristic information such as category information, skill information, proficiency level information, and software used (or web site).

(2) Using the extracted feature of the operation as an index, the degree of similarity between the requested operation and each operation having an execution history within a predetermined time (predetermined time to present) is calculated (step 1002).
The related operation 409 of the record in which the past time within the predetermined time is stored in the end time 407 of the operator schedule management table 400 is referred to, and the definition contents of the corresponding operation are stored in the scenario template identifier 201 and the operation identifier 203 of the scenario definition table 200. And identify from. The operation contents such as category information, skill information, and proficiency information to which the operation belongs by referring to the operation characteristic table described in step 1001 using the value of the requested operation content 205 of the scenario definition table 200 as a key. Get the feature information. The similarity between the acquired past feature information and the feature information acquired in step 1001 is calculated. The similarity is calculated by, for example, calculating a score indicating the distance between categories stored in advance in the external storage device 113, and calculating the similarity as the distance is different. For skill information, a score is calculated from the presence or absence of a skill, and the closer the score is, the higher the similarity is calculated. As for the proficiency level, the closer the index indicating the proficiency level is, the higher the similarity is calculated. In addition, the score is calculated based on the determination as to whether the used software (used Web site) is the same, or whether the used function, the used site, and the used page are the same, and the similarity is comprehensively calculated. The overall similarity is calculated from the category similarity, the skill similarity, the proficiency level, and the usage software (or usage site) similarity calculated in this way using a predetermined calculation formula.

(3) The operator of each operation is referred to and the similarity is totaled for each operator (step 1003).
For each operation in which the administrator identifier column 401 of the operator schedule management table 400 matches, the similarities calculated in step 1002 are totaled by grouping and summing.

  (4) The operator having the largest total similarity value is determined as the operation request destination (step 1004).

  Next, a second processing example for identifying an operator that satisfies the request destination condition will be described. In the second processing example, when an operation execution request composed of a plurality of tasks including an operator's manual task is input, the execution order and execution timing of all the tasks including each manual task are adjusted, and the manual operation task is executed. The assignment of operators who perform work tasks, the execution order and execution timing of each task are determined. In this decision, the operator who performs the manual task is determined in consideration of the work continuity and the work content, and the manual task with the execution start time close to that is grouped, and the task with the earliest start time in each group is executed. An example of processing in which the operator's restraint time is calculated from the time difference between the start time and the task end time of the latest execution end time, and the execution timing and execution order are determined so as to shorten this restraint time. Here, considering the continuity of work and the work content, when the execution operator of a certain operation is determined from among the (operable) operators, the same operator as other operations belonging to the same scenario instance is actively This means that the continuity in the scenario instance is satisfied by deciding to assign the target.

  FIG. 11 is a process flow diagram of a second process example for specifying an operator who satisfies the request destination condition in step 906. By this processing, operations defined in the same scenario instance can be positively assigned to the same operator.

  (1) The scenario instance to which the requested operation belongs is specified (step 1101).

  The extraction of the feature of the operation is the same as step 1001 in FIG.

(2) For other operations constituting the scenario instance, if operators to be executed are determined, the operators are totaled and specified as an operator set (step 1102).
The scenario instance identifier 302 in the scenario instance table 300 is searched, a set of records that match the scenario instance identifier acquired in step 1101 is specified, and the operator of the request destination 306 of those records is specified as an operator set.
(3) Of the operator set, the largest operator (the operator that appears most frequently as the operator of the request destination 306) is determined as the request destination of the requested operation, and the processing of this subroutine is terminated (step 1103).
The number of operations is totaled for each operator belonging to the operator set acquired in step 1102. The operator with the largest number of operations is determined as the operation request destination. At this time, referring to the team 403, role 404, and authority 405 in the operator schedule management table 400, the number of operations is the largest after narrowing down to operators (manager identifier 401) that match the request destination condition 204. An operator may be determined as an operation request destination.

  Next, a third processing example for specifying an operator that satisfies the request destination condition will be described. In the third processing example, when an execution request for an operation composed of a plurality of tasks including an operator's manual task is input, the execution order and execution timing of all the tasks including each manual task are adjusted and The assignment of operators who perform work tasks, the execution order and execution timing of each task are determined. In this determination, the operator who performs the manual task is determined in consideration of the skill required for performing the manual task and the skill of the operator who performs the task, and the manual tasks that are close to the execution start time are grouped. The constraint time of the operator is calculated from the time difference between the execution start time of the task with the earliest start time and the execution end time of the task with the latest execution end time, and the execution timing and execution order are set so as to shorten this constraint time. An example of processing to be determined will be shown.

  FIG. 12 is a process flow diagram of a third process example for identifying an operator that satisfies the request destination condition in step 906. By this process, the operation can be assigned to the operator in consideration of the skill of the operator working on the operation. Thus, work can be assigned to the operator based on the operator's operation proficiency and the operation processing speed.

(1) The feature of the requested operation is extracted (step 1201).
The extraction of the feature of the operation is the same as step 1001 in FIG.

(2) Based on the extracted operation characteristics, an operation set having similar characteristics in the operation execution history is acquired (step 1202).
The related operation 409 of the record in which the past time within a certain time set in the end time column 407 of the operator schedule management table 400 is stored is referred to, and the definition contents of the corresponding operation are stored in the scenario definition table 200. It is specified from the scenario template identifier field 201 and the operation identifier field 203. Using the value of the requested operation content field 205 of the scenario definition table 200 as a key for the definition content of the corresponding operation, the operation characteristic table described in step 1001 is referred to, and the category to which the operation belongs and the usage software (or usage site) belong. get. The similarity between the acquired past feature information and the feature information acquired in step 1001 is calculated. The similarity is calculated by, for example, calculating a score indicating the distance between categories stored in advance in the external storage device 113, and calculating the similarity as the distance is different. The overall similarity is calculated from the calculated skill similarity and proficiency similarity using a predetermined calculation formula. Then, an operation having a similarity that exceeds a similarity threshold stored in advance in the external storage device 113 is specified, and an operation set is acquired.

(3) The time of each operation belonging to the acquired similar operation set is acquired, and the average execution time is totaled for each operator (step 1203).
The time from the start record time 311 to the end record time 31 in the scenario instance table 300 is defined as the operation execution time.

  (4) The operator with the shortest average execution time is determined as the operation request destination (step 1204).

  Of the results of the operation execution time, an operator with a shorter average execution time is determined as a request destination, assuming that the operator with a shorter average execution time is an experienced operator.

  FIG. 13 is a process flow diagram of a fourth process example for identifying an operator that satisfies the request destination condition in step 906. This process makes it possible to assign the same operation as the operation executed recently by the operator. As a result, the operator can continuously perform similar work, and as a result, the simple work is repeated, so that the work time can be shortened and the work switching burden can be reduced. In addition, for example, by determining the similarity based on the characteristics of the same management software or tasks of the same management software, the operator can concentrate on the same management software. You will be able to make use of past know-how and experience without having to look up manuals and documents.

(1) The feature of the requested operation is specified (step 1301).
The extraction of the feature of the operation is the same as step 1001 in FIG.
(2) The schedule of each operator is acquired, and a predetermined number of operation sets to be executed most recently are identified for each operator, going back from the scheduled start time of the requested operation (step 1302).
The scheduled start time 309 of the operation requested in step 1301 is acquired.
The start time 406 of the operator schedule management table 400 is searched, and the operation identifier of the related operation 409 of the record at a time before a predetermined time before the scheduled start time 309 of the operation requested in step 1301 is obtained as an administrator identifier 401 ( Aggregate by operator).

(3) Using the identified feature as an index, the similarity between each operation of the identified operation set and the requested operation is aggregated and calculated for each operator (step 1303).
The definition content of the corresponding operation is specified from the scenario template identifier 201 and the operation identifier 203 of the scenario definition table 200. Using the value of the requested operation content 205 of the scenario definition table 200 as a key for the definition content of the corresponding operation, refer to the operation feature table to obtain operation feature information such as category information, skill information, and proficiency level information to which the operation belongs. To do. The similarity between the acquired past feature information and the feature information acquired in step 1001 is calculated. The similarity is calculated by, for example, calculating a score indicating the distance between categories stored in advance in the external storage device 113, and calculating the similarity as the distance is different. For skill information, a score is calculated from the presence or absence of a skill, and the closer the score is, the higher the similarity is calculated. As for the proficiency level, the closer the index indicating the proficiency level is, the higher the similarity is calculated. In addition, the score is calculated based on the determination as to whether the used software (used Web site) is the same, or whether the used function, the used site, and the used page are the same, and the similarity is comprehensively calculated. The overall similarity is calculated from the category similarity, the skill similarity, the proficiency level, and the usage software (or usage site) similarity calculated in this way using a predetermined calculation formula.

  (4) The operator having the highest degree of similarity is determined as the operation request destination (step 1304).

  According to this embodiment, it is possible to determine an operation execution schedule that shortens the time for restraining the operator.

  101: Management server, 102: Management terminal, 111: Central processing unit, 112: Main storage device, 113: External storage device, 130: Execution schedule evaluation unit, 131: Execution schedule management unit, 132: Operator schedule management unit, 133 : Device schedule management unit, 134: scenario execution unit, 200: scenario definition table, 300: scenario instance table, 400: operator schedule management table, 500: device schedule management table.

Claims (8)

A schedule determination device that connects to a management terminal and determines the schedule of an operator or device,
Each of a plurality of operations constituting the scenario corresponding to the execution request by receiving a scenario execution request from the management terminal and referring to a scenario definition table defining an operation scenario in response to the execution request reception The scheduled start time and the scheduled end time are determined, and regions for storing schedules of operators and devices that execute a plurality of the operations are provided in the operator schedule management table and the device schedule management table, respectively. A schedule of operators and devices that execute the plurality of operations that satisfy the scheduled end time is temporarily reserved, and the operator and device schedules that are temporarily reserved are respectively stored in the operator schedule management table and the device schedule management table. When the scheduled end time of the plurality of operations according to the schedule stored and provisionally satisfied satisfies a deadline time included in the execution request, the operator schedule management table and the equipment schedule management table temporarily reserved The schedule of the operator and the device is changed to the secured state, a message indicating that the execution request is accepted and the schedule changed to the secured state is displayed on the management terminal, and the management terminal from the management terminal In response to the display request of the operator's restraint time, in response to the reception of the display request, the operator's schedule including the schedule is acquired from the operator schedule management table, and the operation schedule of the acquired schedule is scheduled to start. The operations within a predetermined time are grouped, and among the grouped operations, the time from the scheduled start time of the operation with the earliest scheduled start time to the scheduled end time of the operation with the latest scheduled end time is determined by the operator. Obtained as the restraint time, and having a schedule evaluation unit for displaying the found restraint time on the management terminal,
The execution schedule management unit receives the operator schedule change request from the management terminal, acquires the operator schedule from the operator schedule management table in response to the change request reception, and operates the acquired schedule. When operations whose scheduled start time is within a predetermined time are grouped, and there is an operation whose schedule can be adjusted among the grouped operations, the schedule of the adjustable operation is rescheduled, and the rescheduled operation is The time from the scheduled start time of the operation with the earliest scheduled start time to the scheduled end time of the operation with the latest scheduled end time is determined as a new binding time for the operator, A schedule determination device for displaying, on the management terminal, the operator's schedule including the new constraint time and the rescheduled schedule when a new constraint time is shorter than the constraint time obtained by the schedule evaluation unit. . The execution schedule management unit performs grouping according to operations having high similarity between the operations of the operator schedules before the operation start schedule time of the acquired operator schedules is grouped by operations within a predetermined time. The schedule determination apparatus according to claim 1, wherein: The schedule determination apparatus according to claim 1, wherein the execution schedule management unit selects an operator who has a history of executing an operation similar to the operation as each operator that executes the plurality of operations. The said execution schedule management part selects the operator with the shortest average execution time of the said similar operation, when there are several operators with the log | history which performed the operation similar to the said operation. Schedule decision device. A schedule determination device connected to a management terminal is a method for determining a schedule of an operator or a device, and the schedule determination device includes:
Each of a plurality of operations constituting the scenario corresponding to the execution request by receiving a scenario execution request from the management terminal and referring to a scenario definition table defining an operation scenario in response to the execution request reception The scheduled start time and the scheduled end time are determined, and regions for storing schedules of operators and devices that execute a plurality of the operations are provided in the operator schedule management table and the device schedule management table, respectively. A schedule of operators and devices that execute the plurality of operations that satisfy the scheduled end time is temporarily reserved, and the operator and device schedules that are temporarily reserved are respectively stored in the operator schedule management table and the device schedule management table. When the scheduled end time of the plurality of operations according to the schedule stored and provisionally satisfied satisfies a deadline time included in the execution request, the operator schedule management table and the equipment schedule management table temporarily reserved Changing the schedule of the operator and the device to the secured state, displaying the message indicating that the execution request has been accepted and the schedule changed to the secured state on the management terminal,
In response to receiving the display request from the management terminal, the operator acquires a schedule including the schedule from the operator schedule management table in response to receiving the display request. The operations with the scheduled start time within a predetermined time are grouped, and among the grouped operations, the time from the scheduled start time of the operation with the earliest scheduled start time to the scheduled end time of the operation with the latest scheduled end time is Obtained as the restraint time of the operator, display the obtained restraint time on the management terminal,
The operator's schedule change request is received from the management terminal, the operator's schedule is acquired from the operator schedule management table in response to the change request reception, and the scheduled operation start time of the acquired schedule is a predetermined time. When there are operations within the grouped operations that can be adjusted in schedule, reschedule the adjustable operation schedule and start most of the group that includes the rescheduled operation The time from the scheduled start time of the operation with the earlier time to the scheduled end time of the operation with the latest scheduled end time is obtained as the new constraint time of the operator, and the new constraint time is determined by the schedule. When the evaluation unit is shorter than the restraining time obtained, schedule determination method characterized by displaying the operator schedule containing the new duty time and rescheduling schedule to the management terminal. The schedule determination device performs grouping according to operations with high similarity between the operations of the operator schedules before the operations start scheduled times of the acquired operator schedules within a predetermined time. The schedule determination method according to claim 5. The schedule determination method according to claim 5, wherein the schedule determination device selects an operator who has a history of executing an operation similar to the operation as each operator who executes a plurality of the operations. The said schedule determination apparatus selects the operator with the shortest average execution time of the said similar operation, when there are two or more operators with the log | history which performed the operation similar to the said operation. Schedule determination method.

Images