JP6097666B2 - Job management system - Google Patents

Description

  The present invention is a job management system composed of a server and a client, for identifying an affected business when an abnormality occurs in a specific business, and determining a priority for recovering the affected business. It is about the system.

  Generally, in a job management system, various business operations in a company are defined as jobs, a group of one or more jobs with specified execution order is defined as a job net, and jobs and job nets are automatically executed in a planned manner. By doing so, the goal is to realize stable business operations that are less prone to mistakes and fraud.

In particular, in a large-scale job management system, various operations are defined and automatically operated from a basic business of a company to a business for a specific department.
In a large-scale job management system, daily operations are performed by an operation administrator who defines and edits jobs and job nets, and understands the entire system, and a business person who executes and monitors jobs and job nets in their department. Operations are managed and operated, and the amount of operations increases as the scale increases.

  Therefore, if an abnormality occurs in a specific job, the person in charge of the job will manually determine the extent to which the abnormality affects other operations, calculate the time required to recover from the abnormality, and determine the priority of recovery for each job. However, it is necessary to finally recover the abnormality sequentially, and the work burden on the person in charge of operations to deal with these operations promptly becomes very high.

  To deal with this problem, when an error occurs in a specific job in the conventional job management system, the operation manager and the person in charge of the job are notified that the error has occurred and the job can be easily identified. Furthermore, a function is provided that can identify a job that is scheduled to be executed after a job in which an abnormality has occurred has been completed normally.

  For example, in Patent Document 1, a factor estimated to be an abnormal cause is detected by referring to use resource information in which a job is associated with information on a resource used by the job, and an affected job is detected. A system is disclosed.

JP 2009-181495 A

However, in the above prior art, when an abnormality occurs in a business, it is necessary to artificially consider to determine the priority order for recovering the abnormality for an affected business.
This artificial work requires many jobs to be reviewed in order to identify the subsequent relationship of the target job, and it is necessary for a person who is familiar with the contents of the work to judge the priority order. is there.
For this reason, when an abnormality occurs, it is necessary to take a quick action, but it takes time to specify the affected area and to determine the priority order for the recovery of the work, and it becomes difficult to quickly cooperate with the parties concerned.

  An object of the present invention is to facilitate recovery work after the occurrence of an abnormality by automating human work so that a person in charge of business can quickly respond when the abnormality occurs.

  In order to achieve the above object, a job management system of the present invention is a job management system in which a server and a client are communicably connected via a network, and the server is provided for each job net and job. A job net / job database that stores a subsequent element (subsequent job net and / or job), recovery priority level, end deadline time, and scheduled start time, and a job net or an error An expected recovery time database that stores the expected recovery time from the occurrence of an error until the normal operation of the subsequent element of the job, an error occurrence detection means for detecting that an error has occurred in the job net or job, Whether a recovery priority level is set for each subsequent element of the job net or job that has occurred If it is set and set, recovery priority level judgment means for comparing recovery priority levels between subsequent elements and whether an end deadline is set for each subsequent element of the job net or job where the error occurred If it is set, the end deadline time determining means for comparing the end deadline time between the subsequent elements, and the scheduled start time for each subsequent element of the job net or job in which an abnormality has occurred are determined. If it is set, for each subsequent element of the job net or job in which an abnormality has occurred, and a scheduled start time determination means for comparing the scheduled start time between the subsequent elements. It is determined whether or not the expected recovery time is stored. If it is stored, the expected recovery time determination means for comparing the expected recovery time between the subsequent elements, and each determination comparison result Based on, characterized in that it comprises a recovery order determining means for determining a recovery order of successors, and notification means for notifying the recovery ranking the determined user.

Preferably, the job management system of the present invention is a screen display unit that causes the notification unit to display information to be notified on a screen of a user terminal connected to be communicable with the job management system. In addition, the user terminal includes a recovery order, a recovery priority level, an end deadline time, a scheduled start time, an expected recovery time, and the number of jobs included in the job net if the subsequent element is a job net. It is displayed on the screen.

The present invention has the following effects.
(1) From the job net or job where an error has occurred, identify the affected job and the range of the job net, and notify the person in charge of the impact on the local department and the impact on other systems. Cooperation becomes quick.
(2) By automatically determining the priority of the recovery work, it is not necessary to make an artificial decision, and the burden on the person in charge of business in the event of an abnormality is reduced.
(3) By numerically displaying the influence range, the degree of influence due to the occurrence of an abnormality can be understood.
(4) By accumulating information recovered in the past when an abnormality occurred, the expected recovery time in the event of an abnormality can be determined.

FIG. 1 is a block diagram showing an example of the configuration of the embodiment of the present invention. FIG. 2 is a conceptual diagram showing an example of a business management form managed by the operation manager and business staff in the job management system. FIG. 3 shows an example of the data structure of the job net / job database in the present invention. FIG. 4 shows the relationship between job nets and jobs based on the information shown in FIG. FIG. 5 is an operation image diagram showing the work of the person in charge of business when an abnormality occurs in the job net or job. FIG. 6 is an example of an information screen notified to a person in charge of business according to the present invention when an abnormality occurs in a job net or job. FIG. 7 is a diagram showing an example of a flowchart for determining the job net and job recovery order of the information screen notified to the business person in FIG. FIG. 8 is a diagram showing an example of a flowchart for determining the job net and job recovery order of the information screen notified to the business person in FIG. FIG. 9 is a diagram showing an example of a flowchart for determining the job net and job recovery order of the information screen notified to the business person in FIG. FIG. 10 is a diagram showing an example of a flowchart for determining the job net and job recovery order of the information screen notified to the business person in FIG.

  Hereinafter, an example of an embodiment when the present invention is applied will be specifically described with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention, which is a job management system targeted by the present invention.
The job management system includes a server 101 that manages and monitors various settings such as an execution environment and the entire job, a client 106 that executes jobs, and a network 108.

  The server 101 includes a job net execution / monitoring instruction unit 105, a job execution management unit 102, a job net management unit 103, a screen display unit 104 as a notification unit, a job net / job database 106, and an expected recovery time database 107. , User confirmation information database 108, abnormality occurrence detection unit 109, recovery priority level determination unit 110, end deadline time determination unit 111, scheduled start time determination unit 112, expected recovery time determination unit 113, recovery order And a determination unit 114.

  The server 101 is a computer including a CPU (Central Processing Unit), a memory configured by a RAM (Random Access Memory), and a storage device configured by a hard disk. The storage device stores a job management program. Each function of the server 101 is realized by the CPU reading and executing the job management program from the storage device to the memory.

  The job net execution / monitoring instruction unit 105 instructs the job execution management unit 102 to manage job execution, and instructs the job net management unit 103 to manage job nets.

  The job execution management unit 102 receives requests from the job net execution / monitoring instruction unit 105 and manages the execution of various jobs.

  Upon receiving a request from the job net execution / monitoring instruction unit 105, the job net management unit 103 manages the job net that defines the execution order of each job.

The screen display unit 104 is a preferred example of a notification unit. When an abnormality occurs in a job net or job, the screen display unit 104 indicates that an abnormality has occurred and the subsequent elements that are affected by the occurrence of the abnormality (in the present invention, the job net And / or a job may be referred to as an element.) Is displayed on the screen of the user terminal of a business person in charge connected to the job management system of the present invention. Specifically, the job manager is notified of the succeeding job net / job name and the recovery order determined by the recovery order determination unit 114. More preferably, the screen display unit 104 includes, for each subsequent element, a subsequent job net / job name, a recovery order, a recovery priority level, an end deadline time, a scheduled start time, an expected recovery time, and a subsequent element. If it is a job net, the number of jobs included in the job net is displayed on the screen of the user terminal of the person in charge of business.
Note that the notification means is not limited to displaying the information on the screen of the user terminal of the person in charge of the operation by the screen display unit 104, but other methods, for example, outputting to a paper medium for the person in charge of the operation Information can be notified to the person.

  The job net / job database 106 stores information on job nets and jobs as shown in FIG. Specifically, the subsequent elements, the recovery priority level, the end deadline time, the scheduled start time, and the like that are arbitrarily set for each job net and job are stored.

  The expected recovery time database 107 stores the expected recovery time from the occurrence of an abnormality of the subsequent element after the occurrence of the abnormality until the normal operation is started. Specifically, the expected recovery time is the time taken from the time when an abnormality occurred in a job net or job that occurred in the past to the time when each subsequent element started operating normally (time required for recovery) Is the average value of the time required for recovery for each subsequent element of the job net or job.

  The user confirmation information database 108 stores information regarding subsequent elements to be notified to the person in charge of the job when an abnormality occurs in the job net or job, specifically, information shown on the user confirmation screen 606.

  The abnormality detection unit 109 detects that an abnormality has occurred in the job net or job.

  The recovery priority level determination unit 110 determines a recovery priority level that is a reference value for determining the recovery order. Specifically, referring to the information in the job net / job database 106, it is determined whether or not the recovery priority level is set for each subsequent element of the job net or job in which an abnormality has occurred. In this case, the recovery priority level is compared between subsequent elements.

  The end time limit determination unit 111 determines an end time limit that is a reference value for determining the recovery order. Specifically, preferably, among the subsequent elements of a job net or job in which an abnormality has occurred, the job net / job database is set for each subsequent element whose recovery priority level is the same or for which no recovery priority level is set. 106, it is determined whether or not the end deadline time has been set. If it has been set, the recovery priority level is the same level or a subsequent element in which the recovery priority level is not set Comparing end deadlines between the two.

  The scheduled start time determination unit 112 determines a scheduled start time that is a reference value for determining the recovery order. Specifically, it is preferable that the recovery priority level is the same level or the recovery priority level is not set among the subsequent elements of the job net or job in which an abnormality has occurred, and the end time limit is the same time. For each subsequent element for which there is no end deadline time, it is determined whether or not the scheduled start time is set by referring to the information in the job net / job database 106. , Compare the scheduled start time between subsequent elements that have the same recovery priority level or no recovery priority level and the same end time or end time is not set Do.

  The expected recovery time determination unit 113 determines the expected recovery time that is the determination reference value for the recovery order. Specifically, it is preferable that the recovery priority level is the same level or the recovery priority level is not set among the subsequent elements of the job net or job in which an abnormality has occurred, and the end time limit is the same time. Recovery is performed by referring to the information in the estimated recovery time database 107 for each subsequent element that has the end deadline time set and the scheduled start time is the same time or the scheduled start time is not set. It is determined whether or not the expected time is stored, and if stored, the recovery priority level is the same level or the recovery priority level is not set, and the end time limit is the same time Recovery time is expected between subsequent elements for which the end deadline time is not set and the scheduled start time is the same time or the scheduled start time is not set Performing a comparison of the time.

  The recovery order determination unit 114 determines the recovery order of subsequent elements based on the determination comparison result by the recovery priority level determination unit 110, the end deadline time determination unit 111, the scheduled start time determination unit 112, and / or the expected recovery time determination unit 113. Are registered in the user confirmation information database 108.

  A job net that includes itself under a job and / or job net is called a parent job net. For example, for the job: A31 (407) in FIG. 4, the parent job nets are job net: A3 (406), job net: A2 (404), job net: A1 (402), and job net: Route (401).

  In addition, among the parent job nets that include themselves under the job and / or job net, the parent job net closest to the self is referred to as the nearest parent job net. For example, the immediate parent job net of job: A31 (407) in FIG. 4 is job net: A3 (406). In the present invention, the term “most recent parent job net” as well as the simple “parent job net” may mean the latest parent job net.

  The client 115 includes a job execution processing unit 116 that executes a job net or job defined as each business, and there may be a plurality of clients 115 in the job management system. The client 115 is communicably connected to the server 101 via the network 117.

  The client 115 is a computer including a CPU, a memory configured by a RAM, a storage device configured by a hard disk, an input device configured by a keyboard and a touch panel, and an output device configured by a display. It is.

  FIG. 2 is a conceptual diagram showing a management system of job nets and jobs managed by an operation manager and a business person in the job management system configured based on the above contents.

  The operation manager 201 has the authority to manage the entire job management system, and is the highest-level administrator who can refer to, edit, and execute job nets and jobs managed by each business person in charge. .

  As a general rule, the business person 202 can refer only to the job nets and jobs of his / her department that he is in charge of, and the job nets and jobs of other systems that the business person 203 and the business person 204 are in charge of. Cannot be referenced.

Job nets and jobs can be defined (included) under each job net, and the person in charge of the job manages and edits the job nets and jobs of his / her department with management authority.
For job nets and jobs other than their own departments, browsing, management, editing, and operations cannot be performed if they do not have authority, and the scope of work for each person in charge is clearly defined by authority. It has become.

  The job nets and jobs defined under the job net 205 have dependency relationships with each other, and when a specific job net or job ends normally, the specific job net or job is executed. Control is possible.

Dependencies can be specified arbitrarily by the person in charge of the job according to the job. In addition to the dependency between job nets and jobs placed in the same department job net, the dependency relation with job nets in different departments Therefore, it is possible to perform control such that the job net 206 is executed after the job net 205 is normally completed.
In addition, when having a dependency relationship with a job net or job of another department in this way, it is permitted to refer to the job net or job of the other department.

  FIG. 3 is a diagram showing a data structure of the job net / job database 106, which is information held when a business person in charge defines a job net or a job. Details are described below.

  The job content is composed of a job net having elements in the lower level and a job defining the job itself. Each job net / job name 301, type 302, parent job net 303, status 304, subsequent element 305, scheduled start time 306, It consists of an end deadline time 307, an abnormality recovery priority level 308, and other attribute information 309.

  The job net / job name 301 specifies the name of the job net or job that constitutes the job, and is an indispensable item that can be set by the person in charge of the job. There must be no element with the same name in the same job net. It must be unique.

  The type 302 holds the type information of the elements constituting the business, and it is defined whether the defined data is job net data or job data. When creating an element, information is automatically stored by selecting a job net or job.

  The parent job net 303 holds information on the most recent parent job net on which each element is arranged, and is automatically stored as information when a business person in charge defines a job net or job.

  The status 304 represents the current status of the job net and the job, and the status is roughly classified into whether it is waiting for execution, is in execution, has already ended, or an abnormality has occurred. The four states are held, and the detailed information is held in the other attribute information 309.

Subsequent element 305 is a job net or job that needs to be executed after each job and job net has been successfully executed. If there is this, it holds that information and the person in charge of the job Alternatively, when defining a job net, information is held as a succeeding element of the preceding element by defining the preceding element.
In addition, the person in charge of business may define the dependency relationship between each element by visual function, or may explicitly define the job net or job name. Retained.

  The scheduled start time 306 can be arbitrarily specified by the person in charge of the job when there is a scheduled time for starting the job net or job, and information is stored when it is specified. The scheduled start time is the specified value when the person in charge of the job specifies the start time of the job net or job and automatically executes the job periodically. The scheduled start time is the value when an error occurs in the job. This is the reference value for determining the priority of recovery.

  The end deadline time 307 can be arbitrarily specified by the person in charge of the job when there is a time at which the job net or job must be ended, and when it is specified, information is stored and stored. The time is a standard for notifying an alert to the person in charge of business, and is a reference value for determining the priority of recovery when an abnormality occurs in the business.

The error recovery priority level 308 is used to recover the error of the affected job net or job when another job net or job is affected when an error occurs in a specific job net or job. If there is a priority for handling, it is set by the person in charge of the job, and this is stored as information, which becomes a reference value for determining the priority of recovery when an abnormality occurs in the job.
The abnormality recovery priority level 308 can be determined by, for example, the number of subordinate jobs included in the subsequent job net affected by the occurrence of an abnormality.

  The other attribute information 309 holds information on job nets or jobs other than those described above, and holds information such as job net and job IDs and execution file names of jobs to be executed.

  FIG. 4 schematically shows the relationship between job nets and jobs based on the information described in the parent job net 303 and the succeeding element 305 in FIG.

  The job net: route 401 is the highest-level job net corresponding to the route described in the job net / job name 301 in FIG. 3, and has job net: A1 (402) and job net: B410 as elements. When the execution of job net: A1 (402) ends normally, the job net: B410 is defined to be executed.

  Job net: A1 (402) has job: A11 (403) and job net: A2 (404) as subordinate elements, and when job: A11 (403) ends normally, job net: A2 (404) is executed. It is defined to be.

  Job net: A2 (404) has job: A21 (405) and job net: A3 (406) as subordinate elements, and job net: A2 (404) is executed at the same time as job: A21 (405) and job. Net: A3 (406) is defined to be executed.

  In the job net A3 (406), a job: A31 (407), a job: A32 (408), and a job: A33 (409) are defined under the job net A3 (406). When the job: A31 (407) ends normally, the job: A32 (408) ) And job: A33 (409) are defined to be executed.

  The job net: B410 is defined such that the job: B1 (411) and the job: B2 (412) are defined under the job net, and the job: B2 (412) is executed when the job: B1 (411) ends normally. Has been.

  The relationship diagrammatically shown in FIG. 4 becomes the dependency relationship of each job net and job, and when an abnormality occurs in a specific job net or job, it is determined how much the dependency affects the business. Can do.

  FIG. 5 is an operation image diagram showing the work of the person in charge of business when an abnormality occurs in the job net or job.

  When an abnormality occurs, the business person in charge 501 of the business in which the abnormality has occurred identifies the job net or job in which the abnormality has occurred, and from the information displayed on the user confirmation screen 606 notified from the server 101, Check the scope of impact on your department and the scope of impact on other departments' systems, and check the expected recovery time.

  After identifying the affected area and confirming the expected recovery time, notify the person in charge 502 of the other system about the occurrence of an abnormality, notify the presence or absence of the effect and the expected recovery time, and operate in the same way as the notification to the person in charge of the operation. The administrator 503 is also notified of the occurrence of an abnormality.

  After that, regarding the influential elements identified from the job net or job in which an abnormality has occurred, the priority of recovery of each element is examined based on the information displayed on the user confirmation screen 606, and an abnormality is detected from the job with the highest priority. Implement recovery work.

  When determining the priority of recovery, it is specified based on the information displayed on the user confirmation screen 606 notified from the server 101, the magnitude of the influence on other elements, the scheduled start time or the end deadline time of the elements. The elements that have a large effect on other systems or that have exceeded the specified time are restored preferentially.

  After all the recovery work is completed, the business person in charge 502 is notified of the completion of recovery, and a report on the status of occurrence of abnormality is sent to the operation manager 503 who is the system administrator.

  Of the series of operations described above, when the business staff 501 contacts the business staff 502 and the operations manager 503, the business staff 501 must perform the investigation of the influence range and the determination of the recovery order. According to the present invention, even if the person in charge of business 501 does not perform it artificially, these are automatically executed by the server 101.

  FIG. 6 is an example of an information screen that is notified to the person in charge of business when an abnormality occurs in the job net A 601. Preferably, the same information as the user confirmation screen 606 is stored in the user confirmation information database.

  When the job net A 601 is abnormally terminated, the business person in charge is notified from the screen display unit 104 that the abnormality has occurred, for example, by displaying on the user terminal of the business person in charge, and the business person in charge generates an abnormality. 6 to confirm the information displayed on the user confirmation screen shown in FIG. 6, that is, the list of elements that are affected by the occurrence of an abnormality and the information such as the recovery order thereof. Can do.

  If the job net A 601 ends abnormally at 8:30, the recovery order determination unit 114 sets the recovery order 607 to the scheduled start time 610, the end deadline time 611, and the recovery priority for the subsequent job net of the job net A 601 in which the abnormality has occurred. The recovery order is determined from the information held in each item of the level 612 and the expected recovery time 613, and the screen display unit 104 outputs a list of influential elements shown in the user confirmation screen 606 to the user terminal. Display from the highest priority of recovery.

  In the succeeding job net / job name 608, the name of the job net and job defined as the succeeding job net A601 is displayed, and the affected job net and job can be identified.

  The number of jobs under job net 609 displays the number of jobs defined under the job net displayed in the succeeding job net / job name 608, and the number of jobs affected by abnormal termination of the job net or job. Can be specified.

  In the scheduled start time 610, information on the scheduled start time of the subsequent job net or job is displayed, and the time when the abnormality occurred in the job net or job is later than the scheduled start time of the job or until the scheduled start time. It can be determined that the shorter the time, the higher the priority for recovery.

  The end deadline time 611 displays information about the end deadline time of the succeeding job net or job, and the time when the abnormality occurred in the job net or job is later than the end deadline time or the time until the end deadline time. It can be determined that the shorter the time, the higher the priority for recovery.

  The estimated recovery time 613 displays a time obtained by adding an estimated recovery time for each subsequent element of the job net or job to the time when the abnormality occurred in the job net or job, and confirms the expected recovery time of each element. The expected recovery time when an error occurs in the job net or job for the first time is not displayed.

  By presenting the above information to the person in charge of the job when an abnormality occurs in the job net or job, it becomes possible to easily determine the influence range, the expected recovery time, and the priority of element recovery.

  If the job net A 601 is abnormally terminated, the subsequent job net B 602 is designated as 100 in the recovery priority level 612 specified by the person in charge of the job. Is done.

  The subsequent job net C 603 and the subsequent job net D 604 are set to 30 in the recovery priority level 612 specified by the person in charge of the job, and are the same level, but the scheduled start time is defined in the job net C 603. The priority becomes higher, and the job net C603 is designated second and then the job net D604 is designated third.

  The succeeding job net E605 does not have the recovery priority level specified by the person in charge of the job, but the end time limit is specified, and the estimated recovery time exceeds the end time limit, so the priority is higher than other job nets. It becomes higher and is designated fourth.

  FIG. 7 is a diagram showing an example of a flowchart for determining the job net and job recovery order.

  When the abnormality occurrence detection unit 109 detects an abnormality in the job net or job, the server 101 determines all subsequent elements in order to determine the recovery order 607 of each subsequent element for all the subsequent elements of the element that ended abnormally. Is analyzed (701), and the rank of subsequent elements to be output to the recovery rank 607 is determined.

  The recovery order determination unit 114 extracts one subsequent element of the element that has ended abnormally (702) (hereinafter, the extracted subsequent element is referred to as an unregistered subsequent element), and has already been output as another element to be output to the recovery order 607. It is determined whether the subsequent element is registered in the user confirmation information database 108 (703).

  When another subsequent element is not registered in the user confirmation information database 108 as an element to be output to the recovery rank 607, the recovery rank determination unit 114 sets the unregistered subsequent element to the recovery rank 607 with the highest recovery rank. It registers (704) in the user confirmation information database 108 as an element to be output.

  When another subsequent element is already registered in the user confirmation information database 108 as an element to be output to the recovery order 607, in order to register unregistered subsequent elements for all registered subsequent elements, Analyze (705) the appropriate registration location of the unregistered subsequent element.

  The recovery priority level determination unit 110 extracts one element from the subsequent elements registered in the user confirmation information database 108 as an element to be output to the recovery order 607 (706) (hereinafter, the extracted subsequent elements are Refers to the job net / job database 106 to determine whether or not the recovery priority level is set for the unregistered subsequent element and the registered subsequent element. In this case, it is determined whether the recovery priority level of the unregistered subsequent element is higher than the recovery priority level of the registered subsequent element (707).

  When the recovery priority level of the unregistered subsequent element is higher than the registered subsequent element, the recovery order determination unit 114 outputs the user confirmation information database as an element to be output to the recovery order 607 in which the unregistered subsequent element is higher than the registered subsequent element. Registered in 108 (708).

  If the recovery priority level of the unregistered subsequent element is not higher, the recovery priority level determination unit 110 determines whether the recovery priority level of the unregistered subsequent element is the same as the recovery priority level of the registered subsequent element (709). If they are the same, the end time limit determining unit 111 refers to the job net / job database 106 to determine whether end time limits are set for the unregistered subsequent element and the registered subsequent element. If it is also set, it is determined whether the end deadline time of the unregistered subsequent element is earlier than the end deadline time of the registered subsequent element (710).

  In addition, the recovery priority determination unit 114 sets the unregistered subsequent element more than the registered subsequent element when the recovery priority level is set for the unregistered subsequent element and the recovery priority level is not set for the registered subsequent element. The high recovery rank is registered in the user confirmation information database 108 as an element to be output to the recovery rank 607. If the recovery priority level is not set for both the unregistered subsequent element and the registered subsequent element, the recovery priority level is the same as when both recovery priority levels are the same. Determine the rank of the ranking.

  When the end deadline time of the unregistered subsequent element is earlier, the recovery order determining unit 114 confirms the user as an element to be output to the recovery order 607 in which the unregistered subsequent element is higher than the registered subsequent element. Register (711) in the information database 108.

  If the end deadline time of the unregistered subsequent element is not earlier, the end deadline time determination unit 111 determines whether the end deadline time of the unregistered subsequent element is the same as the end deadline time of the registered subsequent element (712) To do.

  If the end time limit of the unregistered subsequent element is not the same as the end time limit of the unregistered subsequent element, the recovery order determining unit 114 outputs the user confirmation information database 108 as an element to be output to the recovery order 607 in which the unregistered subsequent element is lower than the registered subsequent element. (713).

  When the end deadline times of the unregistered subsequent element and the registered subsequent element are the same, the scheduled start time determination unit 111 refers to the job net / job database 106 and starts the scheduled start time for the unregistered subsequent element and the registered subsequent element. Is set, and if both are set, it is determined whether the scheduled start time of the unregistered subsequent element is earlier than the scheduled start time of the registered subsequent element (714). .

  The recovery order determination unit 114 sets the unregistered subsequent element more than the registered subsequent element when the end deadline time is set for the unregistered subsequent element and the end deadline time is not set for the registered subsequent element. The high recovery rank is registered in the user confirmation information database as an element to be output to the recovery rank 607. On the other hand, if the end deadline time is not set for the unregistered subsequent element and the end deadline time is set for the registered subsequent element, the recovery order determination unit 114 determines that the unregistered succeeding element is higher than the registered subsequent element. It is registered in the user confirmation information database as an element to be output to the recovery rank 607 with the low recovery rank. In addition, if the end deadline time is not set for both the unregistered subsequent element and the registered subsequent element, the same as when both end deadline times are the same time, that is, depending on the items after the scheduled start time, Determine the recovery rank.

  If the scheduled start time of the unregistered subsequent element is earlier than the registered subsequent element, the recovery order determining unit 114 confirms the user as an element to be output to the recovery order 607 in which the unregistered subsequent element is higher than the registered subsequent element. Register (715) in the information database 108.

  When the scheduled start time of the unregistered subsequent element is not earlier, the scheduled start time determination unit 112 determines whether the scheduled start time of the unregistered subsequent element is the same as the scheduled start time of the registered subsequent element ( 716), and if they are not the same, the recovery order determination unit 114 registers in the user confirmation information database 108 as an element to be output to the recovery order 607 in which the unregistered subsequent element is lower than the registered subsequent element (717). To do.

  When the scheduled start time of the unregistered subsequent element and the scheduled start time of the registered subsequent element are the same, the expected recovery time determination unit 113 determines the expected recovery time of the unregistered subsequent element and the registered subsequent element as the expected recovery time database 107. In the case where both are stored, the recovery order determination unit 114 requires that the element stored in the expected recovery time has a long time to recover and is prioritized. Is registered in the user confirmation information database 108 as an element to be output to the recovery order 607 with a high recovery order (718). In addition, when the expected recovery time is not stored in either the unregistered subsequent element or the registered subsequent element, and when the expected recovery time is stored only in either the unregistered subsequent element or the registered subsequent element The recovery order of both is the same.

  The recovery order determination unit 114 sets the unregistered subsequent element more than the registered subsequent element when the scheduled start time is set for the unregistered subsequent element and the scheduled start time is not set for the registered subsequent element. The high recovery rank is registered in the user confirmation information database 108 as an element to be output to the recovery rank 607. On the other hand, the recovery order determination unit 114 determines that the unregistered succeeding element is set more than the registered succeeding element when the scheduled start time is not set for the unregistered succeeding element and the scheduled start time is set for the registered succeeding element. It is registered in the user confirmation information database 108 as an element to be output to the recovery order 607 of the recovery order having a low element. In addition, when the scheduled start time is not set for both the unregistered subsequent element and the registered subsequent element, the same as the case where both scheduled start times are the same time, that is, the recovery order of both is determined by the estimated recovery time. Determine high and low.

  After the analysis (705) of unregistered subsequent elements is completed for all elements registered in the user confirmation information database 108 as elements to be output to the recovery order 607, the recovery order determining unit 114 performs the unregistered subsequent elements. Is registered in the user confirmation information database 108 as an element to be output to the recovery order 607 (719).

  When an unregistered subsequent element is not registered as an element to be output to the recovery order 607, the recovery order determining unit 114 stores the unregistered subsequent element in the user confirmation information database 108 as an element of the recovery order 607 having the lowest recovery order. Register (720).

  In accordance with the above analysis of unregistered subsequent elements, all unregistered subsequent elements are analyzed.

  After all the analysis (701) is completed, the screen display unit 104 displays the information shown in the user confirmation screen 606 on the user terminal based on the information registered in the user confirmation information database 108 as an element to be output to the recovery order 607. Notification (721) is made.

101 Server 102 Job execution management unit 103 Job net management unit 104 Screen display unit (notification unit)
105 Jobnet execution / monitoring instruction unit 106 Jobnet / job database 107 Expected recovery time database 108 User confirmation information database 109 Abnormality detection unit 110 Recovery priority level determination unit 111 End deadline time determination unit 112 Scheduled start time determination unit 113 Expected recovery Time determination unit 114 Recovery order determination unit 115 Client 116 Job execution processing unit 117 Network

Claims (2)

A job management system in which a server and a client are communicably connected via a network,
The server is
A job net / job database that stores a subsequent element (subsequent job net and / or job), recovery priority level, end deadline time, and scheduled start time arbitrarily set for each job net and job;
An estimated recovery time database that stores an estimated recovery time from the occurrence of an abnormality to the job net or the subsequent element of the job in which an error has occurred until normal operation starts;
An abnormality occurrence detection means for detecting that an abnormality has occurred in the job net or job,
Determine whether recovery priority level is set for each subsequent element of a job net or job where an error has occurred, and if so, recovery priority level comparison that compares the recovery priority level between subsequent elements Means,
It is determined whether or not the end deadline time is set for each subsequent element of the job net or job where the error occurred. If so, the end deadline time for comparing the end deadline time between the subsequent elements A determination means;
Judges whether the scheduled start time is set for each subsequent element of the job net or job where an error has occurred, and if it is set, compares the scheduled start time between the subsequent elements A determination means;
It is determined whether or not the expected recovery time is stored for each subsequent element of the job net or job in which an error has occurred, and if it is stored, the expected recovery time for comparing the expected recovery time between the subsequent elements A determination means;
A recovery order determination means for determining a recovery order of subsequent elements based on the results of each determination and comparison;
A job management system comprising: notification means for notifying the user of the determined recovery order. The notification means is a screen display means for displaying information to be notified on a screen of a user terminal connected to be communicable with the job management system ;
For each subsequent element, the recovery order, the recovery priority level, the end deadline time, the scheduled start time, the expected recovery time, and the number of jobs included in the job net if the subsequent element is a job net, The job management system according to claim 1, wherein: is displayed on a screen of the user terminal.