JP7211026B2 - Job management system - Google Patents

Description

The present invention relates to a job management system capable of appropriately notifying a maintenance worker of the occurrence of a failure when a failure is detected in a job executed in a business system.

2. Description of the Related Art In an information system that performs various tasks, a job management system is used that operates a plurality of jobs while controlling them in order to systematically and automatically operate daily tasks. In such a job management system, registration of jobs and setting of execution conditions are usually performed manually based on operation design. Temporary deregistration and reregistration of jobs associated with system improvement and maintenance are also performed manually.

When a failure occurs in a specific job, the job management system notifies the operation manager and the person in charge of the operation of the failure, making it easier to identify the job. It is also necessary to manually determine the order of priority. However, in order to properly determine the priority of failure recovery, it takes time to review many jobs before and after, so it is difficult to quickly deal with it. had to rely.

Therefore, conventionally, there has been proposed a job management system that can specify the extent and degree of impact when a job failure occurs and automatically calculate the priority of recovery without human intervention (see Patent Document 1). ).
This identifies the extent and degree of impact based on information such as the user-specified priority, scheduled start time, end deadline time, parent job net, succeeding job net, etc. for job nets and jobs, and prioritizes recovery. It calculates the rank.

JP 2015-64723 A

However, in the above-described job management system, the user specifies the priority of job nets or jobs in advance, and determines the priority of recovery accordingly. , the order of priority is not determined according to this, but it is appropriate to determine whether it is a failure that requires immediate response, whether it is a failure that can be handled within business days, or whether it is a failure that does not require response. It is not possible to make a decision and respond. For this reason, there are concerns about inconveniences such as delays in responding to failures that require urgency, and time being wasted due to failures that do not require response.

SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and provides a job management system that can determine the urgency of a job based on the content of the failure and appropriately notify a maintenance worker of the occurrence of the failure. The main task is to provide

In order to achieve the above object, a job management system according to the present invention is a job management system that manages execution results of jobs executed in a business system by a maintenance management system,
The business system is
Comparing the execution registered file generated by extracting the executed jobs and the expected value file storing the job information scheduled to be executed, if there is a non-existent job in any of the files, or , a failure detection unit that determines that there is a failure when the job is not executed within the execution time range or the daily execution count defined in the expected value file ;
a failure information transmission unit that transmits failure information when the failure detection unit determines that there is a failure;
The maintenance management system is
Equipped with a response record database that accumulates response results for past failures,
a failure level determination unit that determines a failure level indicating the degree of urgency of the failure to the job based on the transmitted failure information and the response record of the response record database;
a communication unit that performs failure occurrence notification by a means corresponding to the failure level determined by the failure level determination unit;
It is characterized by having

Therefore, when a failure occurs in a job executed in a business system, the maintenance management system uses the failure information sent from the business system based on the past failure response results accumulated in the response history database. Analyze the job, determine the failure level that indicates the degree of urgency of the failure, and notify the failure occurrence by means according to the determined failure level. It is possible to adjust the response according to the degree of urgency of the failure.

Here, the failure level determined by the failure level determination unit is, for example, a high level that requires immediate response, a middle level that can be handled after the next business day, and a low level that does not require response. , If the failure level determination unit determines that the failure level is high, the maintenance worker is immediately notified of the occurrence of the failure by means of directly recognizing it, and if the failure level determination unit determines that the failure level is medium level, the maintenance worker directly recognizes it. If the failure level is determined to be low by the failure level determination unit, the failure occurrence notification may be performed by simply notifying the maintenance worker.

As a means to be directly recognized by the maintenance worker, automatic calling directly to the terminal carried by the maintenance worker can be considered. Further, as means for simply notifying the maintenance worker, automatic transmission of an e-mail to a terminal carried by the maintenance worker can be considered.

Furthermore, the maintenance management system may further include a response result registration unit that registers, in response to a request for registration, a failure response result of the maintenance worker responding to the failure occurrence notification from the communication unit in the response record database. With such a configuration, as the job management system is operated, it becomes possible to improve the accuracy of failure level determination and failure occurrence notification.

As described above, according to the present invention, for a job failure that occurred in a business system, a failure level indicating the degree of urgency of the failure is determined by referring to a response record database that stores results of handling past failures, and Since the failure occurrence notification is performed by means corresponding to the determined failure level, it is possible to take appropriate measures according to the urgency of the failure based on the past response record.
Therefore, it is possible to avoid inconveniences such as delays in response to urgent failures and wasted time due to failures that do not require response.

FIG. 1 is a diagram showing the overall configuration of a job management system according to the present invention. FIG. 2 is a flow chart showing the processing performed by the business system. FIG. 3(a) is a flow chart showing the processing performed in the maintenance management system, and FIG. 3(b) is a table showing an example of failure level and corresponding failure occurrence notification.

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 shows the overall configuration of a job management system according to the present invention. This job management system connects a business system 1 provided in a business execution facility or the like, a maintenance management system 2 that performs maintenance and management of the business system 1, and the business system 1 and the maintenance management system 2 so as to be able to communicate with each other. network 3;

A business system 1 includes a business terminal 11 that can be operated by a person in charge of business, a business server 12 that executes a group of jobs registered via the business terminal, and these business terminals 11 and business server 12 that are mutually communicatively connected. and a LAN 13 that

The business server 12 confirms the result of the executed job and notifies the failure information when a failure occurs. and a failure information transmission unit 15 .

Various methods are conceivable for detecting a failure by the failure detection unit 14. For example, an executed job is extracted, an execution registered file 16 is generated, and this execution registered file 16 and job information scheduled to be executed are extracted. are compared with the expected value file 17 that stores the failure, and the job log file 18 is monitored to detect an abnormal log.

Specifically, as shown in FIG. 2, the business server 12 extracts the executed jobs and generates the execution registered file 16 (step 52), and the execution registered file 16 and the expected value file 17 are compared with each other, and a fault notification is issued in the following cases, for example (step 54).
- If there is a job that exists in the expected value file but does not exist in the execution registration file, a failure notification will be made assuming that the job has not been registered.
- If there is a job that exists in the execution registration file but does not exist in the expected value file, a failure notification is issued as an unnecessary job registration.
- Define an execution time range in the expected value file, and issue a failure notification if the job is not executed within that range. If the execution time is shorter than the execution time range, for example, it is assumed that the process that should be executed is processed with 0 cases, and if the execution time is longer than the execution time range, for example, a timeout Since it is assumed that the subsequent process is stopped due to
- Define the number of daily executions in the expected value file, and issue a failure notification if the job is not executed within that range.
Further, when the job log file 18 is monitored and an abnormal log is detected, a fault notification is issued (step 56).

The maintenance management system 2 includes a maintenance management terminal 21 that can be operated by a maintenance manager, a maintenance management server 22 that analyzes failure information transmitted from the business system 1 and issues an alert, and a LAN 23 that connects the management terminals 21 so as to be able to communicate with each other.

The maintenance management server 22 is provided with a response record database 24 that accumulates the results of handling past failures. It has a failure level determination unit 25 that determines a failure level indicating a degree of failure, and a failure occurrence communication unit 26 that performs failure occurrence notification by means corresponding to the failure level determined by the failure level determination unit 25 .

That is, as shown in FIG. 3A, when the maintenance management server 22 receives fault information from the business system 1 (business server 12) (step 62), it accumulates the content of the fault information in the response record database 24. Analysis is performed on the basis of the response results for past failures (step 64), and a failure level indicating the degree of urgency of the failure is determined (step 66).

For example, as shown in FIG. 3(b), the failure level is a high level with high urgency that requires immediate response, a medium level with low urgency that can be handled on the next business day, and an emergency level that does not require response. Divide into low-level and no sex.

Here, referring to the response record database 24 as a criterion for determining the failure level as a high level,
(1) Failures that have occurred in the past and require immediate response,
(2) new obstacles that have not occurred in the past;
(3) A failure that has been occurring for more than one year since the last occurrence (if more than one year has passed, the content of the business using the business system 1 has also changed (the service level has changed) Considering possible points),
It may be determined whether or not.

In addition, as a criterion for determining the failure level as a medium level, refer to the response record database 24,
・Similar failures have occurred in the past, and failures that require response on the next business day,
- A failure that has been occurring for more than half a year and less than a year since the last occurrence (taking into consideration the possibility that the business content using the business system has changed somewhat),
It may be determined whether or not.

Furthermore, as a criterion for determining the failure level as a low level, refer to the response record database 24,
・Similar failures have occurred in the past, and failures that are considered “unnecessary to respond”,
It may be determined whether or not.

Then, after the failure level is determined in step 66, the maintenance operator is notified of the occurrence of failure by means corresponding to the failure level (step 68).
For example, when the failure level is high, a means for directly recognizing the maintenance worker, for example, calling the mobile terminal 4 owned by the maintenance worker immediately after the failure occurs (this telephone contact is A pre-registered telephone number of the maintenance worker may be automatically called and automatic voice notification may be given).

In addition, when the failure level is medium level, means for directly recognizing the maintenance worker, for example, calling the portable terminal 4 owned by the maintenance worker after the next business day (this telephone contact is also It may also be possible to automatically call the maintenance worker's telephone number registered in advance and perform automatic voice notification.)

If the failure level is low, the maintenance worker is simply notified by means such as e-mail (this e-mail notification is automatically sent to the pre-registered e-mail address of the maintenance worker). should do).

Then, when the maintenance worker is contacted, as shown in FIG. When it is completed, it requests the maintenance management system 2 (maintenance management server 22 ) to register the response result via its own terminal (for example, mobile terminal 4 ) or maintenance management terminal 21 . The maintenance management system 2 (maintenance management server 22) has a response result registration unit 27 that receives this registration request and registers the response result in the response record database 24. The response result registration unit 27 receives the registration request. The result of the response to the failure is registered in the response history database 24, and used for determination of failure level when a failure occurs in the future.

Therefore, according to this job management system, the failure level (degree of urgency of the failure) is determined based on the past failure response results according to the content of the failure, and the failure occurs to the maintenance worker by means according to the failure level. Since the contact is made, instead of treating all failures uniformly, it is possible to give priority to handling the failures with urgency judged based on past response results.
In the above example, the case where the failure level is divided into three stages has been described, but the failure level may be divided more finely and handled.

1 business system 2 maintenance management system 4 mobile terminal 14 failure detection unit 15 failure information transmission unit 16 execution registered file 17 expected value file 18 job log file 24 response record database 25 failure level determination unit 26 failure occurrence communication unit 27 response result registration Department

Claims (3)

A job management system in which a maintenance management system manages execution results of jobs executed in a business system,
The business system is
Comparing the execution registered file generated by extracting the executed jobs and the expected value file storing the job information scheduled to be executed, if there is a non-existent job in any of the files, or , a failure detection unit that determines that there is a failure when the job is not executed within the execution time range or the daily execution count defined in the expected value file ;
a failure information transmission unit that transmits failure information when the failure detection unit determines that there is a failure;
The maintenance management system is
Equipped with a response record database that accumulates response results for past failures,
a failure level determination unit that determines a failure level indicating the degree of urgency of the failure to the job based on the transmitted failure information and the response record of the response record database;
a communication unit that performs failure occurrence notification by a means corresponding to the failure level determined by the failure level determination unit;
A job management system comprising: The failure level determined by the failure level determination unit is determined as a high level that requires immediate response, a middle level that can be handled after the next business day, and a low level that does not require response,
When the fault occurrence notification by the communication unit is determined to be the high level by the fault level determination unit, the failure occurrence communication is immediately performed by a means for directly recognizing the failure occurrence by the maintenance worker. means for directly recognizing by the maintenance worker when it is determined that the failure occurrence is notified after the next business day, and when the failure level determination section determines that the failure level is low, the maintenance worker is simply notified. 2. The job management system according to claim 1, wherein the job management system performs failure occurrence notification. The maintenance management system further comprises a response result registration unit for registering, in response to a registration request , a failure response result handled by the maintenance worker based on the failure occurrence notification from the communication unit in the response result database. 3. A job management system according to item 1 or 2 .

Images