JP6436644B2 - Analysis device and computer program - Google Patents

Description

  The present invention relates to a data processing technique, and more particularly to a technique for analyzing an operation status of an information system.

  Outsourcing operation management of information systems is widespread, and service level agreements (hereinafter referred to as “SLA”) may be defined between users and operators of information systems (for example, Patent Document 1). reference).

International Publication No. 2012/144204

  In recent years, there has been an increasing demand for compression on the operating cost of information systems, and there is also a need to improve the ability to explain operating costs. A main object of the present invention is to provide a technique for obtaining useful information that visualizes the operation results of an information system.

  In order to solve the above problem, an analyzer according to an aspect of the present invention is generated in a system, a first acquisition unit that acquires information about a system held in an operation monitoring apparatus that monitors an operation state of a predetermined system. The second acquisition unit that acquires information about the operator held in the service desk device that supports the operator who should respond to the error detected by the operation monitoring device, and the information acquired by the first acquisition unit And an evaluation unit that generates information indicating the operation efficiency of the system according to the operation scale of the system and the number of operators specified based on the information acquired by the second acquisition unit.

  It should be noted that any combination of the above-described components and the expression of the present invention converted between a method, a system, a program, a recording medium storing the program, etc. are also effective as an aspect of the present invention.

  ADVANTAGE OF THE INVENTION According to this invention, it can support obtaining the useful information which visualized the operation performance of the information system.

It is a figure which shows the apparatus group in connection with operation | use of an information system. It is a block diagram which shows the function structure of the analyzer of FIG. FIG. 3A is a diagram showing system definition information, and FIG. 3B is a diagram showing an error message log. FIG. 4A is a diagram showing basic operator information, FIG. 4B is a diagram showing work performance information, and FIG. 4C is a diagram showing definition application information. It is a figure which shows the structure of operational efficiency information. It is a figure which shows the structure of operator evaluation information. It is a figure which shows the structure of service level information. It is a figure which shows an operational efficiency information screen. It is a figure which shows an operator evaluation information screen. It is a figure which shows a service level information screen. FIG. 11A is a diagram showing information of each system used for the first regression analysis, and FIG. 11B is a diagram showing information of each system used for the second regression analysis. 12A shows the result of the first regression analysis, FIG. 12B shows the result of the second regression analysis, and FIG. 12C shows the result of the third regression analysis. It is a figure which shows the example of the input value in a prediction process, and a prediction result.

Before describing the configuration of the analyzer according to the embodiment, an outline will be described.
In recent years, there has been a demand for compression of operating costs of information systems, but the scale of systems to be operated is rather increasing, and it is not easy to reduce operating costs. Based on such a background, the present inventor recognizes that it is necessary to improve the explanation capability when explaining the operation cost to the customer, and (1) visualization of the operation results of the information system and (2) the operation cost. We thought it necessary to improve the accuracy of estimation.

(1) About visualization of information system operation results:
Until now, operation results have been aggregated manually by the person in charge of operations, and the workload of the administrator has been large. In addition, only a small amount of information related to operations could be aggregated, and the aggregated information was already outdated. In addition, the evaluation criteria for operation personnel (hereinafter also referred to as “operators”) are limited, and the evaluation is limited to, for example, the years of service.

  Therefore, the analysis apparatus according to the embodiment automatically collects the system definition and the system error log from the operation monitoring apparatus, and automatically collects the operation log of the operation from the operation service desk apparatus. The analysis device aggregates these data, shapes and links them to the operation scale and operation results, and provides a view of operation efficiency, service level, and operator evaluation. This makes it possible to visualize a wide range of information related to the operation of information systems, improve the freshness of information, and support the utilization of information in the operation department and the improvement of explanation capabilities to customers.

(2) Improvement in accuracy of operation cost estimation:
Until now, the estimation of information system operating costs has relied heavily on the experience and intuition of operators, and the accuracy was not necessarily high. The present inventor has come up with the idea that there is a correlation between the operator's workload and operation capability in actual information system operation and the operator's operation performance during actual system operation.

  The analysis apparatus according to the embodiment generates a regression model indicating a regression relationship between an operator's workload and operation capability in an actual information system operation and the operator's operation results, and uses it to estimate the operation cost of a new system. Apply regression model. As a result, the actual system operation results are reflected in the operation cost estimate of the new system, and the accuracy of the estimate is improved.

  It should be noted that quantification of the operator's workload, which is a prerequisite for regression analysis, is based on the following inventor's idea. That is, the operator work is defined by a predetermined work flow, and has the characteristic that the same result is returned in the same way regardless of who is the operator. For example, in the case of a system person who will be described later instead of an operator, a different approach may be taken for each individual against a system failure. As a specific example, when working with a plurality of servers, some people log in one by one and others work with a remote shell. In this way, since the work methods of each system person in charge are different, it is meaningless to measure the time, and it is difficult to quantify the work amount on a common basis across a plurality of system persons. However, since the operator work has the feature that any operator can perform the same work, the work amount can be quantified on a common basis across a plurality of operators. Therefore, it is possible to perform regression analysis based on operation results of a plurality of information systems in which a plurality of operators are engaged in operation.

  FIG. 1 shows a group of devices related to the operation of the information system. Each of the monitoring target system 10a, the monitoring target system 10b, the monitoring target system 10c, the monitoring target system 10d, and the monitoring target system 10e collectively referred to as the monitoring target system 10 executes information processing that supports various business operations such as a company. It is a server group. For example, one monitoring target system 10 includes one realized by one server to one in which several hundred servers cooperate.

  The operation monitoring apparatus 12a and the operation monitoring apparatus 12b, which are collectively referred to as the operation monitoring apparatus 12, are information processing apparatuses in which known operation monitoring software is installed. The operation monitoring apparatus 12a executes an operation monitoring process for the monitoring target system 10a, the monitoring target system 10b, and the monitoring target system 10c, and the operation monitoring apparatus 12b executes an operation monitoring process for the monitoring target system 10d and the monitoring target system 10e. .

  The operation monitoring process executed by the operation monitoring device 12 includes monitoring the operation status of the monitored system 10, detecting an error that has occurred in the monitored system 10, and notifying the service desk device 14 of an error. Further, job setting for the monitoring target system 10, job execution control, and command transmission to the monitoring target system 10 are included. The error in the embodiment includes various faults, operation stop, operation abnormality, deviation from normal state, and the like. The operation monitoring apparatus 12 holds system definition information (FIG. 3A described later) and an error message log (FIG. 3B described later) regarding each of the plurality of monitoring target systems 10.

  The service desk device 14 is an information processing device in which known service desk software is installed. The service desk device 14 supports the work of the operator who should respond to the error detected by the operation monitoring device 12. The operator is, for example, a person in charge of an SIer operation department that provides an outsourcing service for system operation, and operates the operator terminal 16.

  Further, the service desk device 14 holds various information related to the operator. For example, operator basic information indicating basic attributes of the operator (FIG. 4A described later), work result information indicating the operation results by the operator (FIG. 4B described later), and the operation monitoring device 12 by the operator. Definition application information (FIG. 4 (c) described later) indicating various registration contents is held.

  When an error occurs in the monitoring target system 10, the monitoring target system 10 transmits an error message to the operation monitoring apparatus 12, or the operation monitoring apparatus 12 autonomously detects the occurrence of the error. The operation monitoring device 12 transmits an error message to the service desk device 14. The service desk device 14 notifies the error content to the operator terminal 16 and displays it according to a predetermined separation condition. At this time, as the navigation message, the operator terminal 16 is also notified of the work content to be performed by the operator according to the error content and the contact information of the person in charge of the system (developer who should analyze the error and correct the bug). .

  The operator identifies the affected range according to the error content displayed on the operator terminal 16, makes a call (telephone contact) to the person in charge of the system, and appropriately performs failure recovery work. The service desk device 14 sequentially records error messages. Further, the operator's work contents, the time required for error handling, the presence / absence of errors in handling errors, etc. are acquired from the operator terminal 16 and sequentially recorded.

  The administrator terminal 18 is an information terminal operated by an administrator of the operation department. A part of the operator evaluation described later is input by the administrator and registered in the analyzer 20 from the administrator terminal 18.

  The analysis device 20 is connected to the operation monitoring device 12, the service desk device 14, the operator terminal 16, and the administrator terminal 18 via a communication network including a LAN, a WAN, the Internet, and the like. Based on the data acquired from the operation monitoring device 12 and the service desk device 14, the analysis device 20 executes (1) an operation performance visualization process for the monitored system 10 and (2) an operation cost estimation support process.

  FIG. 2 is a block diagram showing a functional configuration of the analyzer 20 of FIG. The analysis device 20 includes a control unit 50 that executes various data processing, and a data holding unit 30 that is a storage area for data that is referred to or updated by the control unit 50. Although not shown in FIG. 2, the analysis device 20 detects a communication unit that communicates with an external device via a communication network 22 according to a predetermined communication protocol, and an operation input via an input device such as a keyboard or a mouse. An operation detection unit and a display control unit for controlling the display content of the display 26 are provided. Each function block in FIG. 2 transmits / receives data to / from an external device via a communication unit, receives input information from an operator via an operation detection unit, and displays an image on a display via a display control unit.

  Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU and a memory of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. , Depicts functional blocks realized by their cooperation. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.

  For example, an analysis application including a software module corresponding to each functional block of the control unit 50 may be installed in the storage of the analysis apparatus 20. The function of each functional block of the control unit 50 may be exhibited by the CPU of the analyzer 20 by reading each software module into the main memory and executing it. Each functional block of the data holding unit 30 may be realized by storing data in a storage device such as a storage or a memory.

  The data holding unit 30 includes an actual system information holding unit 32, an operation result holding unit 34, an operation efficiency information holding unit 36, an evaluation reference holding unit 38, an operator evaluation holding unit 40, an SLA information holding unit 41, a service level holding unit 42, A regression model holding unit 44, a new system information holding unit 46, and a prediction result holding unit 48 are included.

  The real system information holding unit 32 holds system definition information, which is attribute information about each system, for each of a plurality of monitoring target systems 10 (also referred to as “real systems”) currently in operation. In addition, an error message log, which is error message accumulation information indicating an error that has occurred in each system, is held. FIG. 3A shows system definition information, and FIG. 3B shows an error message log. The monitoring target server ID, server setting information, and monitoring content in FIG. 3A are set for each server in one monitoring target system 10.

  Returning to FIG. 2, the operation record holding unit 34 holds operator basic information, which is attribute information about each operator, for each of a plurality of operators currently engaged in operation practice. Also, work result information indicating the results of error handling work by each operator and definition application information indicating the results of definition application work by each operator are held. 4A shows the operator basic information, FIG. 4B shows the work performance information, and FIG. 4C shows the definition application information.

  4B may be the date and time when the monitoring target system 10 or the operation monitoring apparatus 12 detects an error that has occurred in the monitoring target system 10. The response time may be the date and time when the call from the operator to the system person in charge, for example, the notification of the failure occurrence using a predetermined communication means such as a telephone is completed. In addition, a call mistake in the correspondence record means that an appropriate call could not be made, and includes an error in contact information, an error in contact contents, a failure to contact within a predetermined time, and the like.

  “Definition” in the definition application information means one unit of information that is instructed to the monitoring target system 10 or the operation monitoring apparatus 12 in the operation of the monitoring target system 10. “Definition application” means that various information for operation of the monitoring target system 10 is registered in the monitoring target system 10 and the operation monitoring apparatus 12. For example, this includes newly registering or changing a job to be executed by the monitoring target system 10 in the operation monitoring apparatus 12. In addition, the monitoring item of the monitoring target system 10 is newly registered and changed. Moreover, the setting change of each server of the monitoring target system 10 is included. The operator accesses the monitoring target system 10 and the operation monitoring apparatus 12 from the operator terminal 16 and performs the definition application work.

  Returning to FIG. 2, the operation efficiency information holding unit 36 holds the operation efficiency information (FIG. 5) generated by the operation efficiency evaluation unit 62 described later. The evaluation criterion holding unit 38 holds data indicating a criterion for evaluating the operation performance of the operator. For example, the correspondence relationship between the value derived based on the work performance by the operator and the evaluation values in a plurality of stages is held. The operator evaluation holding unit 40 holds operator evaluation information (FIG. 6) generated by an operator evaluation unit 64 described later.

  The SLA information holding unit 41 holds SLA information determined in each of the plurality of monitoring target systems 10. For example, values indicating the target of the operation state such as the average call time and the upper limit of the number of call misses are held. The service level holding unit 42 holds service level evaluation information (FIG. 7) generated by a service level evaluation unit 66 described later.

  The regression model holding unit 44 holds a regression model generated by a regression analysis unit 74 described later, that is, data indicating a regression coefficient and a regression equation. The new system information holding unit 46 holds attribute information about the new system, which is basic information for estimating the operating cost of the new system. For example, the operation scale assumed for the new system and the operator's operation capacity (for example, the number of persons and skill level) defined temporarily are held. Also, SLA information (for example, average call time, call miss rate) scheduled for the new system is held. The prediction result holding unit 48 holds information indicating the prediction result / estimation result based on the regression model for the new system.

  The control unit 50 includes an actual system information acquisition unit 52, an operation result acquisition unit 54, a new system information acquisition unit 56, an operation status visualization unit 60, and a prediction unit 70. The actual system information acquisition unit 52 acquires system definition information and error message logs related to each of the plurality of monitoring target systems 10 from the operation monitoring device 12a and the operation monitoring device 12b, and stores them in the actual system information holding unit 32. The operation result acquisition unit 54 acquires the operator basic information, work result information, and definition application information regarding each of a plurality of operators from the service desk device 14 and stores them in the operation result holding unit 34.

  The new system information acquisition unit 56 acquires new system attribute information input from the input device 24, and is input by the operator or the operation department administrator and transmitted from the operator terminal 16 or the administrator terminal 18. Get attribute information of. The new system information acquisition unit 56 stores the new system attribute information in the new system information holding unit 46.

  The operation status visualization unit 60 executes an operation performance visualization process for the monitoring target system 10. The operation status visualization unit 60 includes an operation efficiency evaluation unit 62, an operator evaluation unit 64, a service level evaluation unit 66, and an analysis result display unit 68.

  The operation efficiency evaluation unit 62 refers to both the data stored in the actual system information holding unit 32 and the data stored in the operation result holding unit 34, and the operation efficiency for each of the plurality of monitoring target systems 10. Operational efficiency information indicating is generated. The operation efficiency information can be said to be information indicating an operation performance per unit amount of operation cost, and can also be said to be operation cost efficiency information. The operation efficiency evaluation unit 62 stores the generated operation efficiency information in the operation efficiency information holding unit 36.

  FIG. 5 shows the structure of operational efficiency information. The values in the information item column in FIG. 5 indicate items of operational efficiency information stored in the operational efficiency information holding unit 36. The value in the information source column in FIG. 5 indicates the original information that the operational efficiency evaluation unit 62 maps to each item, and indicates an algorithm for generating information on each item.

  The operational efficiency evaluation unit 62 identifies the monitoring target system ID of the system definition information stored in the actual system information holding unit 32 as the system ID of the operational efficiency information. Hereinafter, an ID assigned to one monitoring target system 10 is referred to as a specific system ID, and a method for setting operation efficiency information for one monitoring target system 10 will be described.

  The operational efficiency evaluation unit 62 counts the number of monitoring target server IDs associated with the specific system ID in the system definition information, and identifies the number as the number of target servers in the operational efficiency information. Further, the number of operator IDs associated with the specific system ID in the operator basic information stored in the operation record holding unit 34 is counted, and the number is identified as the number of operators in the operation efficiency information. Also, the result of dividing the number of target servers by the number of operators is identified as the number of servers per person in the operational efficiency information.

  In addition, the operation efficiency evaluation unit 62 counts the number of message IDs associated with the specific system ID in the error message log stored in the actual system information holding unit 32 (may be work result information stored in the operation result holding unit 34). Count. Then, the result of dividing the number by the number of operators is identified as the number of messages per person in the operational efficiency information. In addition, the number of application IDs associated with the specific system ID in the definition application information stored in the operation record holding unit 34 (however, the record corresponding to the corresponding status is “completed”) is counted. Then, the result of dividing the number by the number of operators is identified as the number of definition registrations per person in the operational efficiency information.

  Although not specifically mentioned below, in the processing of the operation status visualization unit 60 and the prediction unit 70, the error message log, work performance information, and definition application information records were recorded within a predetermined unit period (for example, one month). Records are subject to aggregation. Therefore, the average call time, the number of call misses, and the number of definition registration deadlines that will be described later are values for the most recent month.

  Here, as the number of servers and the total number of messages (also referred to as the number of errors) in the monitoring target system 10 increase, the amount of work required to operate the monitoring target system 10 increases. Therefore, it can be said that these values are index values indicating the amount of work required for operation of the monitoring target system 10, that is, the operation scale. The number of servers per person, the number of messages per person (that is, the number of error responses per person), and the number of registered definitions per person can be said to be the amount of operation work covered by the cost of one operator. It can be said that it is an index value indicating efficiency. It can also be said to be an index value indicating the amount of work for one operator, and an index value indicating the degree of busyness for one operator.

  Returning to FIG. 2, the operator evaluation unit 64 refers to the data stored in the operation record holding unit 34 and generates operator evaluation information regarding each of the plurality of operators. The operator evaluation information can be said to be information that visualizes the operational capability of each operator based on the operation results of each operator. The operator evaluation unit 64 stores the generated operator evaluation information in the operator evaluation holding unit 40.

  FIG. 6 shows the structure of operator evaluation information. The values in the information item column in FIG. 6 indicate the items of operator evaluation information stored in the operator evaluation holding unit 40. The value in the information source column in FIG. 6 indicates original information that the operator evaluation unit 64 maps to information on each item, and indicates an algorithm for generating information on each item.

  For example, the operator evaluation unit 64 identifies the operator ID of the operator basic information stored in the operation result holding unit 34 as the operator ID of the operator evaluation information. Hereinafter, an operator ID assigned to one operator will be referred to as a specific operator ID, and a method for setting operator evaluation information for one operator will be described.

  The operator evaluation unit 64 identifies a record (referred to as a “specific record”) associated with a specific operator ID among the records of work performance information stored in the operation performance holding unit 34. Then, the corresponding required time from the occurrence time recorded in each specific record to the corresponding time is summed, and the total time is divided by the number of specific records (which can be said to be the number of message IDs associated with the specific operator ID). The result is calculated as the average call time. Further, an evaluation value associated with the average call time is acquired from the evaluation reference holding unit 38.

  Further, the operator evaluation unit 64 identifies the number of specific records in which mistakes are recorded in the correspondence record, and identifies the number of records as the number of call mistakes in the operator evaluation information. Further, the result of dividing the number of calls with no mistakes (a value obtained by subtracting the number of call mistakes from the total number of specific records) by the total number of specific records is identified as an accurate call ratio of the operator evaluation information. Then, the evaluation value associated with the ratio is acquired from the evaluation reference holding unit 38.

  Further, the operator evaluation unit 64 identifies a record (referred to as “specific record”) associated with the specific operator ID among the records of the definition application information stored in the operation result holding unit 34. Then, the number of specific records is identified as the definition registration number of the operator evaluation information. In addition, the number of records in which the corresponding deadline is recorded among the specific records is identified as the number of deadlines in the operator evaluation information. In addition, the evaluation value associated with the number of definition registrations, the number of expired periods, or a combination thereof is acquired from the evaluation reference holding unit 38.

  In addition, the operator evaluation unit 64 acquires the evaluation value of the appropriate cooperation with the development department, the evaluation value of the business improvement ability, and the evaluator comment transmitted from the administrator terminal 18, and holds each of them as an operator evaluation. To the unit 40. Of course, these data may be input from the local input device 24.

  Also, the operator evaluation unit 64 calculates the total of the call promptness evaluation value, the call accuracy evaluation value, the definition registration number evaluation value, the evaluation value of the appropriate collaboration with the development department, and the evaluation value of the business improvement ability. Identify as a total score of information. When the evaluation value of each item is a perfect score, the total score is a perfect score of 25. The operator evaluation unit 64 identifies an average evaluation value that is a result of dividing the total score by the number of evaluation items (for example, 5) as the skill of the operator evaluation information.

  Moreover, the operator evaluation part 64 compares the total score of each of several operators, and identifies the ranking of each operator. Also, referring to the correspondence between the combination of the total score and ranking stored in a predetermined storage area and the fictitious title to be assigned to the operator, the title of each operator is determined according to the total score and ranking of each operator. Identify. The title is a name that indicates the relative level of operational practical ability. It may be a nickname indicating a status or class in a predetermined virtual world. For example, titles such as “egg”, “apprentice”, “craftsman”, “master”, “hero”, etc. may be determined from the lower rank.

  The operator evaluation holding unit 40 accumulates past evaluation information of each operator in association with the evaluation date. The operator evaluation unit 64 identifies a difference between the previous evaluation information and the current evaluation information, and records data indicating the difference in the operator evaluation information as a difference from the previous time. The difference in evaluation information may be the amount of change in work performance such as the average call time or the number of definition registrations, or the amount of change in evaluation value or ranking.

  Returning to FIG. 2, the service level evaluation unit 66 refers to the data of the actual system information holding unit 32, the operation result holding unit 34, the operator evaluation holding unit 40, and the SLA information holding unit 41, and each of the plurality of monitoring target systems 10. Generate service level information for. The service level information can be said to be information obtained by evaluating and visualizing the service level in units of systems based on the operation results for each monitored system 10. Basically, operator evaluation information is aggregated for each system and evaluated from the viewpoint of SLA. The service level evaluation unit 66 stores the generated service level information in the service level holding unit 42.

  FIG. 7 shows the structure of service level information. The values in the information item column in FIG. 7 indicate items of service level information stored in the service level holding unit 42. The value in the information source column of FIG. 7 indicates the original information that the service level evaluation unit 66 maps to each item, and indicates an algorithm for generating information of each item.

  The service level evaluation unit 66 identifies the monitoring target system ID of the system definition information stored in the actual system information holding unit 32 as the system ID of the service level information. Hereinafter, an ID assigned to one monitoring target system 10 will be referred to as a specific system ID, and a service level information setting method for one monitoring target system 10 will be described.

  The service level evaluation unit 66 refers to the operator basic information stored in the operation result holding unit 34 and identifies the operator ID (referred to as “specific operator ID”) associated with the specific system ID. When a plurality of operators are in charge of operation of one monitoring target system 10, a plurality of specific operator IDs are identified. The service level evaluation unit 66 identifies a plurality of operator evaluation information associated with the specific operator ID among the operator evaluation information stored in the operator evaluation holding unit 40, and determines the average value of the average call time of each operator as a call. Identifies as actual time. Moreover, the call performance time is compared with the call target time stored in the SLA information holding unit 41 to determine whether or not the target has been achieved.

  The service level evaluation unit 66 identifies the result of dividing the total number of call misses recorded in the plurality of operator evaluation information associated with the specific operator ID by the total number of calls as an operation error occurrence rate. The total number of calls may be the number of records associated with the specific system ID in the error message log stored in the actual system information holding unit 32, or in the work result information stored in the operation result holding unit 34. The number of records associated with the specific system ID may be counted. The service level evaluation unit 66 compares the operation error occurrence rate with the target value of the operation error occurrence rate stored in the SLA information holding unit 41, and determines whether or not the target has been achieved.

  The service level evaluation unit 66 identifies the total number of definition registrations recorded in the plurality of operator evaluation information associated with the specific operator ID as a definition registration record. Further, the definition registration record is compared with the definition registration target value stored in the SLA information holding unit 41 to determine whether or not the target has been achieved.

  Returning to FIG. 2, the analysis result display unit 68 generates an operation efficiency information screen in which the operation efficiency information stored in the operation efficiency information holding unit 36 is arranged. Further, an operator evaluation information screen in which operator evaluation information held in the operator evaluation holding unit 40 is arranged is generated, and a service level information screen in which service level information held in the service level holding unit 42 is arranged is generated. When the analysis result display unit 68 receives an analysis information provision request from the operator terminal 16 or the administrator terminal 18, the analysis result display unit 68 transmits the screen data designated by the operator or administrator to the operator terminal 16 or the administrator terminal 18 for display. . Further, each screen is displayed on the display 26 in response to a display request from the input device 24.

  The analysis result display unit 68 may function as a web server, and may transmit web pages of the operation efficiency information screen, the operator evaluation information screen, and the service level information screen to the operator terminal 16 and the administrator terminal 18, respectively.

  FIG. 8 shows an operational efficiency information screen 80. The operation scale in FIG. 8 indicates the number of operators in the operation efficiency information. Further, as shown in FIG. 8, the analysis result display unit 68 displays a graph showing the transition of the operation efficiency according to the operation efficiency information generated a plurality of times from the past to the present held in the operation efficiency information holding unit 36. Information screen 80 is set. In FIG. 8, a graph is set that shows changes in the operation scale (here, the number of servers), operation scale (here, the number of operators), and operation efficiency (here, the number of servers per person).

  As a modification, the number of messages and the number of definition registrations of the monitoring target system 10 may be set as the operation scale, and an index value specified by a combination of these and the number of servers may be set as the operation scale. Further, the labor scale of one or more operators in charge of the operation of the monitored system 10 may be set as the operation scale.

  FIG. 9 shows an operator evaluation information screen 82. The average operation level in FIG. 9 indicates the skill value recorded in the operator evaluation information. Further, as shown in FIG. 9, the analysis result display unit 68 sets a radar chart indicating evaluation values (here, a maximum of 5 points) of a plurality of items held in the operator evaluation holding unit 40 on the operator evaluation information screen 82.

  FIG. 10 shows a service level information screen 84. As shown in FIG. 10, the analysis result display unit 68 displays whether or not each of the plurality of goals has been achieved in the SLA compliance status area 86. In addition, in the SLA unachieved situation detail area 88, the target value and the actual value are displayed in association with each other for the item for which the target has not been achieved.

  Returning to FIG. 2, the prediction unit 70 executes operation cost estimation support processing by regression analysis. The prediction unit 70 includes a variable acquisition unit 72, a regression analysis unit 74, an estimation unit 76, and a prediction result display unit 78.

  The variable acquisition unit 72 acquires information indicating an operator's workload required for operating an actual system, information indicating an operator's operation capability, and information indicating an operation history of the operator with respect to the actual system. Specifically, as information indicating the workload of the operator, the number of monitoring target servers arranged in the monitoring target system 10 and the number of error messages related to the monitoring target system 10 (generated in the monitoring target system 10 and detected by the operation monitoring device 12) The number of definition registrations is acquired. In addition, the number of operators involved in the operation of the monitoring target system 10 and the skill value of the operator are acquired as information indicating the operation capability of the operator. In addition, average call time, number of call misses, and number of definition registration deadlines exceeded are acquired as information indicating the operation results by the operator.

  The regression analysis unit 74 identifies an explanatory variable based on information indicating an operator's workload and information indicating an operator's operational capability, and identifies an objective variable based on information indicating an operation result of the operator. Then, a regression coefficient between the explanatory variable and the objective variable is derived by a known regression analysis method. The regression analysis unit 74 stores data indicating the derived regression coefficient and regression equation in the regression model holding unit 44.

  In the following, three types of regression analysis are proposed, and each is referred to as a first regression analysis, a second regression analysis, and a third regression analysis. FIG. 11A shows information of each system used for the first regression analysis and the second regression analysis, and FIG. 11B shows information of each system used for the third regression analysis. 12A shows the result of the first regression analysis, FIG. 12B shows the result of the second regression analysis, and FIG. 12C shows the result of the third regression analysis.

The first regression analysis will be described with reference to FIG.
The variable acquisition unit 72 acquires the number of monitoring target servers and the number of messages (that is, the number of error occurrences) in each monitoring target system 10 from the system definition information and the error message log of the actual system information holding unit 32. Further, the number of operators involved in the operation of each monitored system 10 is acquired from the basic operator information of the operation result holding unit 34. Further, the skill value and average call time of each of a plurality of operators who are engaged in the operation of each monitored system 10 are acquired from the operator evaluation holding unit 40. Unless otherwise specified, the variable acquisition unit 72 may acquire necessary information from the data holding unit 30 in the same manner as the operation status visualization unit 60. In the following examples, the skill value of the operator is adjusted to 10 levels (10 points maximum).

  The regression analysis unit 74 identifies the result of integrating the number of monitoring target servers and the number of messages (that is, the number of error occurrences) as the operation scale (call). The number of monitoring target servers and the number of messages are positively correlated with the entire workload of a plurality of operators in the monitoring target system 10. Therefore, the operation scale (call) is also positively correlated with the entire work amount of a plurality of operators in the monitored system 10, and the operation scale (call) is an index value indicating the amount of work load. That is, the regression analysis unit 74 determines the operator's workload larger as the number of monitoring target servers in the monitoring target system 10 increases or as the number of errors generated in the monitoring target system 10 increases.

  The regression analysis unit 74 identifies the result of dividing the operation scale (call) by (number of operators × skill average value of a plurality of operators) as an explanatory variable (herein referred to as “operation capability basic value (call)”). To do. The operational capability basic value (call) is the amount of work per operator, and is an index value indicating the busyness of the work of each operator. The greater the number of monitored servers in the monitored system 10, the greater the number of errors that have occurred in the monitored system 10, the fewer the number of operators, and the lower the skill value of each operator, the greater the operational capability basic value (call). Calculated. Moreover, the regression analysis part 74 averages the average call time of several operators, and identifies the average value as an objective variable.

  As shown in FIG. 12A, the regression analysis unit 74 derives a regression coefficient between the operational capability basic numerical values (calls) identified for the plurality of monitoring target systems 10 and the average call time by regression analysis. FIG. 12A shows a regression equation derived by single regression analysis, and shows that a regression coefficient having a slope “0.7897” and an intercept “10.683” is derived.

  The second regression analysis will be described with reference to FIG. The second regression analysis is different from the first regression analysis only in the objective variable, and the description overlapping with the first regression analysis is omitted. The variable acquisition unit 72 acquires the number of call mistakes for each of a plurality of operators involved in the operation of each monitored system 10 from the work performance information of the operator evaluation holding unit 40. The regression analysis unit 74 averages the number of call misses of a plurality of operators, and identifies the average value as an objective variable.

  As shown in FIG. 12B, the regression analysis unit 74 derives a regression coefficient between the operational capability basic numerical values (calls) identified for the plurality of monitoring target systems 10 and the average number of call misses by regression analysis. FIG. 12B shows a regression equation derived by single regression analysis, and shows that a regression coefficient having a slope of “0.0367” and an intercept of “−3.278” is derived.

  The third regression analysis will be described with reference to FIG. In the third regression analysis, both the explanatory variable and the objective variable are different from the first regression analysis, and the description overlapping with the first regression analysis is omitted.

  The variable acquisition unit 72 acquires the number of definition registrations in each monitoring target system 10 from the definition application information of the operation result holding unit 34 and identifies it as the operation scale (definition registration). For example, the number of records in which the IDs of the respective monitoring target systems 10 are recorded among the records of the definition application information may be acquired as the definition registration number. The number of definition registrations is positively correlated with the entire workload of a plurality of operators in the monitoring target system 10. Therefore, the operation scale (definition registration) as well as the operation scale (call) is positively correlated with the entire work amount of a plurality of operators in the monitoring target system 10, and is an index value indicating the amount of the work amount.

  The variable acquisition unit 72 acquires from the operation result holding unit 34 the number of definition registration deadlines exceeded for each of the plurality of operators involved in the operation of each monitored system 10. For example, the number of records for which the corresponding deadline has been exceeded may be counted among the records of the definition application information. The regression analysis unit 74 calls the result of dividing the operation scale (definition registration) by (the number of operators × average value of skills of a plurality of operators) as an explanatory variable (here, “operation capability basic value (definition registration)”). ). Further, the regression analysis unit 74 identifies an average value of the definition registration deadline surpluses of a plurality of operators as an objective variable.

  As shown in FIG. 12C, the regression analysis unit 74 performs regression analysis on the regression coefficient between the operational capability basic numerical values (definition registration) identified for the plurality of monitoring target systems 10 and the average value of the definition registration deadline exceeded. Derived by FIG. 12C shows a regression equation derived by single regression analysis, and shows that a regression coefficient having a slope “0.1564” and an intercept “−0.993” is derived.

  Returning to FIG. 2, the estimation unit 76 uses the regression model generated by the regression analysis unit 74 to execute a prediction process related to the operation of the prediction target system. The estimation unit 76 stores data indicating the result of the prediction process in the prediction result holding unit 48. Hereinafter, the first prediction process and the second prediction process will be described. In the embodiment, the prediction target system is a new system for which operation is newly started, and processing for supporting estimation of the operation cost of the new system is executed.

Explanation of the first prediction process:
As the first prediction process, the estimation unit 76 performs an operation on the new system in accordance with the operator's workload assumed in the new system, the operator's operational capacity temporarily determined, and the regression coefficient stored in the regression model holding unit 44. Estimate the operational status of the operator. The operation state to be estimated indicates the service level of the system operation, and specifically is the call time and call miss frequency by the operator.

  FIG. 13 shows an example of input values and prediction results in the prediction process. In the figure, the value in the shaded area indicates the input value, and the underlined value indicates the prediction result.

  An example of the first prediction process will be described with reference to FIG. The estimation unit 76 is an index value indicating the workload of the operator assumed in the new system, which is stored in advance in the new system information holding unit 46. In this example, the operation scale is the product of the number of monitored servers and the number of messages. Get the expected value of (call). The new system information holding unit 46 may store the estimated values of the number of servers to be monitored and the number of messages, and the estimating unit 76 integrates these estimated values and identifies the result as the operation scale (call). May be. In addition, the estimation unit 76 acquires the planned number of operators and planned skills stored in advance in the new system information holding unit 46.

  These assumed values and scheduled values may be input from the operator terminal 16 or the administrator terminal 18 to the analyzer 20 via the communication network 22 or may be input from the input device 24 to the analyzer 20.

  The estimation unit 76 divides the estimated value of the operation scale (call) by the product of the planned number of operators and the planned skill to calculate an operation capability basic value (call). Then, by inputting the value to the regression model derived by the first regression analysis (for example, x in the regression equation in FIG. 12A), the call time (for example, y in the regression equation in FIG. 12A) is obtained. calculate. This call time is an estimate of the average call time required for the operator to complete a call to the system staff when an error message is output in the new system.

  Further, the estimation unit 76 inputs the operational capability basic value (call) to the regression model derived by the second regression analysis (for example, x in the regression equation of FIG. 12B), thereby making the number of call misses (for example, FIG. Calculate y) of the regression equation of b). The number of call misses is an estimated value of the number of times that one operator makes a call mistake when an error occurs in the new system in a predetermined unit period (for example, one month). The estimation unit 76 stores information including the input value of the prediction process and the prediction result (for example, information in FIG. 13A) in the prediction result holding unit 48.

  Next, an example of the first prediction process will be described with reference to FIG. The estimation unit 76 is an index value indicating the workload of the operator assumed in the new system, which is stored in advance in the new system information holding unit 46. In this example, the estimation unit 76 performs the operation during a predetermined operation period (for example, one month). Get the expected value of the operational scale (definition registration) indicating the number of definition registrations that should be performed. In addition, the planned number of operators and planned skills stored in advance in the new system information holding unit 46 are acquired.

  The estimation unit 76 divides the estimated value of the operational scale (definition registration) by the product of the planned number of operators and the planned skill to calculate an operational capability basic value (definition registration). Then, by inputting the value to the regression model derived by the third regression analysis (for example, x in the regression equation of FIG. 12C), the number of definition registration deadlines exceeded (for example, the regression equation of FIG. 12C). y) is calculated. The definition registration deadline excess number is an estimated value of the number of times one operator exceeds the definition registration work deadline in a predetermined unit period (for example, one month). The estimation unit 76 stores information including the input value of the prediction process and the prediction result (for example, information in FIG. 13B) in the prediction result holding unit 48.

Explanation of the second prediction process:
As the second prediction process, the estimation unit 76 performs a new operation according to the operator's workload assumed in the new system, the operation state by the operator required for the new system, and the regression coefficient stored in the regression model holding unit 44. Estimate the operator's operational capacity required for the system. The operation status of the operator required for the new system may be the service level required for the new system, and may be information defined by the SLA. Specifically, the average call time and the number of call misses by the operator are allowable values. Further, the operational ability of the operator to be estimated is specifically the number of operators and / or operator skills.

  An example of the second prediction process will be described with reference to FIG. Here, an example is shown in which the regression model derived by the first regression analysis (specifically, the regression equation of FIG. 12A) is used, but the regression model derived by the second regression analysis or the third regression analysis is used. Of course, the second prediction process may be executed using the second prediction process.

  The estimation unit 76 acquires an assumed value of the operation scale (call) stored in advance in the new system information holding unit 46. In this example, it is assumed that the operator's necessary skill (planned skill) is also stored, and the estimation unit 76 also acquires the operator's necessary skill. Further, the estimation unit 76 acquires a service level required for a new system stored in advance in the new system information holding unit 46, in this case, a request value for average call time.

  The estimation unit 76 inputs the required value of the average call time to the regression model derived by the first regression analysis (for example, y in the regression equation of FIG. 12A), thereby requiring the operational capability basic value (call). A value (for example, x in the regression equation of FIG. 12A) is calculated. Since the operational capacity basic value (call) is obtained by dividing the operational scale (call) by the product of the required number of operators and the required skills, the estimation unit 76 calculates the calculated operational capacity basic value (call) and the place. Calculate the required number of operators based on the required skills.

  The estimation unit 76 is a skill unit price stored in a predetermined storage area, and according to information that defines the labor cost of the operator for each skill in a predetermined unit period (for example, one month), Calculate labor costs. In the example of FIG. 13C, since the operator of skill 5 is 7.5 (may be 8), the labor cost of the operator is calculated as 750. The labor cost of this operator can be said to be an estimated value of the operating cost of the new system in a predetermined unit period. The estimation unit 76 stores information including the input value of the prediction process and the prediction result (for example, information in FIG. 13C) in the prediction result holding unit 48.

  Returning to FIG. 2, the prediction result display unit 78 provides the result of the prediction process by the estimation unit 76 to an operation manager, an operator, and an external device. Specifically, the prediction result display unit 78 generates a prediction result screen in which the prediction result information regarding the operation of the new system stored in the prediction result holding unit 48 is arranged, and this screen data is used as the operator terminal 16 and the administrator terminal. 18 and displayed on the display 26.

  The prediction result display unit 78 is information including both an assumed value (scheduled value) and a prediction result related to the operation of the new system. For example, a prediction result screen showing information on each of FIGS. It may be generated. The prediction result display unit 78 may function as a web server, and may transmit a web page indicating the prediction result screen to the operator terminal 16 and the administrator terminal 18 and display the web page on the display 26.

  In the above example, the required skill of the operator is determined in advance, but instead, the required number of operators (scheduled number) may be determined in advance. In this case, the estimation unit 76 may estimate an operator's required skill, that is, an average value of skills of a plurality of operators. In addition, the estimation unit 76 may record an operational capability basic value (call) as an estimation result when the required number of operators and the required skills are indefinite. By presenting the estimated value of the basic operation capability value to the person in charge of the operation department as the required operation capability of the operator, the person in charge may consider the number of operators and skills that satisfy the basic operation value.

The operation of the analyzer 20 having the above configuration will be described below.
When it is detected that a predetermined period (for example, one month) has passed since the previous analysis process, the actual system information acquisition unit 52 changes the operation monitoring apparatus 12 from the operation monitoring apparatus 12 that is executing the operation monitoring process to the monitored system 10. Acquire system definition information and error message log managed by. The operation result acquisition unit 54 acquires operator basic information, work result information, and definition application information managed by the service desk device 14 from the service desk device 14 that is executing the operator support processing in cooperation with the operation monitoring device 12. The operation efficiency evaluation unit 62, the operator evaluation unit 64, and the service level evaluation unit 66 are based on the information managed by the operation monitoring device 12 and the information managed by the service desk device 14, and the operation efficiency information, operator evaluation information, Generate service level information.

  When the analysis result display unit 68 receives an operation efficiency information screen provision request specifying a specific system ID from an external device such as the administrator terminal 18, the analysis result display unit 68 transmits the operation efficiency information screen illustrated in FIG. 8 to the external device. Display on an external device. When the analysis result display unit 68 accepts a request for providing operator evaluation information specifying a specific operator ID from an external device such as the operator terminal 16 or the administrator terminal 18, the operator evaluation information screen shown in FIG. To be displayed on the external device. When the analysis result display unit 68 receives a service level information screen provision request designating a specific system ID from an external device such as the administrator terminal 18, the service level information screen shown in FIG. 10 is transmitted to the external device. Display on an external device.

  As described above, according to the analysis device 20 of the embodiment, the management data by the operation monitoring device 12 and the management data by the service desk device 14 are associated with each other so that the operation efficiency, the service level, and the operator evaluation based on the latest operation status are performed. A view can be provided. This makes it possible to visualize a wide range of information related to the operation of the information system and improve the information freshness. In addition, objective operator evaluation results based on operational results can be provided, and maintenance of the operator's motivation for operational tasks can be supported by introducing gamification of giving titles.

  When a predetermined analysis instruction is input from the administrator terminal 18 or the input device 24, or periodically, the variable acquisition unit 72 performs the operations of the operator in the actual system operation based on the information managed by the operation monitoring device 12. Get information that shows quantity. In addition, information indicating an operator's operation capability based on information managed by the service desk device 14 is acquired, and information indicating an operator's operation performance based on information managed by the service desk device 14 is acquired. The regression analysis unit 74 performs a regression analysis using the operator's workload and operational capability as explanatory variables and the operator's operational performance as an objective variable, and derives a regression equation indicating the regression relationship between the two.

  The person in charge (for example, the developer of the new system or the administrator of the operation department) who should estimate the operation cost of the new system sends the prerequisites (for example, the number of servers to be monitored and SLA information) to the analyzer 20 regarding the operation of the new system. input. As a precondition for the operation of the new system, when an estimated value of the operator's workload and a planned value of the operator's operational capacity are designated and an instruction to start the prediction process is input, the estimation unit 76 performs the precondition and regression analysis. According to the regression equation derived by the unit 74, the operating state of the operator in the new system is estimated. The prediction result display unit 78 transmits information (for example, FIGS. 13A and 13B) indicating the prediction result of the operation state of the operator in the new system to the terminal of the person in charge for display.

  Also, as a precondition for the operation of the new system, when the assumed value of the operator's workload and the service level required by the new system are specified and an instruction to start the prediction process is input, the estimation unit 76 According to the regression equation derived by the regression analysis unit 74, the operator's operational capability required for the new system, such as the number and skills of operators, and labor costs are estimated. The prediction result display unit 78 transmits information (for example, FIG. 13 (c)) indicating the prediction result of the operator's operational ability required for the new system to the terminal of the person in charge for display.

  As described above, according to the analysis apparatus 20 of the embodiment, the operation of the operator in the new system that reflects the regression relationship that exists between the operator's workload and operation capacity and the operator's operation results in the actual system operation. Estimate the state. The person in charge examines whether the estimated operational status of the operator (for example, average call time, number of call misses, etc.) is within an acceptable range, so that the expected value of the operator's operational capability as a prerequisite for the new system is appropriate. Can be determined.

  Further, according to the analysis apparatus 20, a necessary operator's operation capability is estimated by reflecting a regression relationship existing between the operator's workload and operation capability and the operator's operation results in actual system operation. As a result, the operator's operational ability required for satisfying the service level required for the operation of the new system, such as the number of operators, skills, and labor costs, can be presented to the person in charge, and the estimation of reasonable operational costs can be supported.

  Further, a regression equation is obtained based on information managed by the operation monitoring apparatus 12 that is executing the operation monitoring process for the monitored system 10 and the service desk apparatus 14 that is executing the operator support process in cooperation with the operation monitoring apparatus 12. By deriving, a regression equation reflecting the actual operation state and the latest operation state is derived. In addition, the index value indicating the operator's workload is increased as the number of monitored servers in the monitored system 10 is increased, and the index value indicating the operator's workload is increased as the number of errors in the monitored system 10 is increased. In this way, a regression equation that matches the actual system operation is derived.

  The present invention has been described based on the embodiments. This embodiment is an exemplification, and it will be understood by those skilled in the art that various modifications can be made to combinations of the respective constituent elements and processing processes, and such modifications are also within the scope of the present invention. is there. A modification is shown below.

First modification:
Although not mentioned in the above-described embodiment, the analysis apparatus 20 of the present modification provides attribute information regarding each error for each type of error that can occur in each of the plurality of monitoring target systems 10. An error attribute holding unit that holds the information in association with the ID is further provided. Hereinafter, the specific monitoring target system 10 will be described. The error attribute information includes identification information of each of a plurality of types of errors that can occur in a specific monitoring target system 10, and a weight value corresponding to the severity of each error. Specifically, the greater the error-induced result, the greater the error influence range, the greater the cost of error resolution, and the longer the time to error resolution, the larger the weight value is set. . For example, (1) Java exception: weight 1, (2) timeout error: weight 2, (3) server A stop error: weight 3, may be predetermined ("Java" is a registered trademark).

  The operation efficiency evaluation unit 62 acquires the error weight value indicated by each message from the error attribute holding unit when calculating the number of messages per person in the generation of operation efficiency information related to one monitoring target system 10. Then, the total number of messages (that is, the total number of errors) that is the number to be divided is adjusted according to the error weight value indicated by each message. Specifically, the larger the error weight value indicated by the message, the greater the number of messages. For example, if there are 5 messages indicating Java exceptions, 2 messages indicating a timeout error, and 1 message indicating a server A stop error, the total number of messages is not simply 8 (= 5 + 2 + 1). The total number is determined to be 12 (= 5 × 1 + 2 × 2 + 1 × 3). As a result, the greater the error indicated by each message, the greater the value of the number of messages per person, that is, the higher the operational efficiency. In this way, the fact corresponding to a serious error is reflected in the operational efficiency information.

  Further, the operator evaluation unit 64 acquires the error weight value indicated by each message from the error attribute holding unit when calculating the average call time (call promptness) in the generation of operator evaluation information related to one operator. Then, the total number of messages (that is, the total number of errors), which is the number that divides the total required time, is adjusted according to the error weight value indicated by each message. Specifically, as described above, the larger the error weight value indicated by the message, the greater the number of messages. As a result, the more serious the error indicated by each message, the smaller the average call time value, and the higher the operator's operational capability. In addition, the call performance time of the service level information that aggregates the average call time of each operator is reduced, and the service level is also evaluated higher. Thus, the fact corresponding to the serious error is reflected in the operator evaluation information and the service level information.

  Even if the number of errors is the same, there is a reality that the difficulty and complexity of the operator work differ if the severity of the error is different. According to the first modified example, it is possible to evaluate the operation results more realistically.

Second modification:
In the first modification, a method for reflecting the severity of error in the operation performance evaluation is proposed. In the second modification, a method for reflecting the severity of error in the operation cost estimation support process is proposed. The analysis device 20 of the second modification also includes an error attribute holding unit similar to that of the first modification.

  The regression analysis unit 74 (which may be the variable acquisition unit 72) acquires the error weight value indicated by each message from the error attribute holding unit when calculating the actual value of the operation scale (call) indicating the work amount of the operator. . Then, the total number of messages is adjusted according to the error weight value indicated by each message. Specifically, as in the first modified example, the larger the error weight value indicated by the message, the larger the number of messages. As a result, the greater the error indicated by each message, the larger the total number of messages and the larger the operation scale (call) value. As described above, even if the number of errors is the same as one, there is a reality that the difficulty and complexity of the operator work differ if the severity of the error is different. It is possible to generate a regression model suitable for

  Note that, in the second modification, an assumed value of the operation scale (call) of the new system may be set in consideration of the occurrence ratio of a plurality of types of errors assumed in the new system. The estimation unit 76 may execute the first prediction process and the second prediction process using an assumed value of the operation scale (call) set in consideration of the severity of the error. It is possible to derive a more accurate prediction result that is more realistic.

Third modification:
In the above embodiment, the regression analysis unit 74 performs the single regression analysis using the operational capability basic numerical value as an explanatory variable. However, multiple regression analysis using a plurality of explanatory variables may be performed. For example, for each of a plurality of monitoring target systems 10, a plurality of items such as the number of monitoring target servers, the number of messages (number of error occurrences), the number of teams in charge of the system, the number of operators, the operator skill, etc. are used as explanatory variables, and service level results ( Multiple regression analysis may be performed using the average call time and the like as objective variables.

Fourth modification:
In the above embodiment, a new system that has not yet started operation is the operation cost prediction target system. However, as a modification, an existing system that has already started operation may be the prediction target system. In this case, the operation scale (call), the operation scale (definition registration), the number of operators, and the actual value of the operator skill may be input as preconditions for the prediction target system. The service level comparison unit (not shown) compares the predicted service level output in the first prediction process with the actual service level output from the service level evaluation unit 66, and displays the comparison result indicating the difference as the data holding unit 30. May be stored. If the actual service level is worse than the predicted service level, for example, if the call time is long, the number of call misses is large, or the number of definition registration deadlines is excessive, there is a problem in the operation of the existing system to be predicted compared to other existing systems. I understand that there is.

  Further, the operation capability comparison unit (not shown) compares the operator's operation capability output in the second prediction process with the average number of operators and operator skills output from the operation efficiency evaluation unit 62, and the actual operator's operation capability When the number of operators is excessive, for example, when the number of operators is large, it is understood that the operation efficiency of the existing system to be predicted is lower than that of other existing systems. In this way, useful information can be acquired even when an existing system that has already started operation is used as a prediction target system.

Fifth modification:
When one operator is engaged in the operation of a plurality of systems, the number of operators serving as a calculation criterion for operation efficiency may be adjusted according to the operation results of the operators. When the operational efficiency evaluation unit 62 of this modification generates operational efficiency information of one monitoring target system 10 (referred to as a specific system), each operator associated with the ID of the specific system actually The number of operators may be calculated according to the amount of operation engaged in operation, in other words, the proportion of the total operation amount of each operator engaged in the operation of the specific system.

  For example, the ratio of the number of records associated with both the ID of the specific system and the ID of the specific operator in the number of records of work performance information associated with the ID of one operator (referred to as a specific operator) is calculated. May be. If the ratio is 0.4, 0.4 may be added to the number of operators as a specific operator. Instead of the work performance information, the ratio in the definition application information record may be calculated, or an average value of the ratios in both the work performance information and the definition application information may be calculated. When information indicating how much a specific operator has been engaged in the operation work of each of a plurality of systems can be acquired from a predetermined work management device, the number of operators may be calculated using that information. According to the fifth modification, operational efficiency information that is more realistic can be generated.

Sixth modification:
Similar to the fifth modification, when one operator is engaged in the operation of a plurality of systems, the number of operators as an explanatory variable for regression analysis for operation cost prediction may be adjusted according to the operation performance of the operator. . Specifically, similarly to the operational efficiency evaluation unit 62 of the fifth modification, the variable acquisition unit 72 is an operation amount that each operator associated with the ID of the specific system actually engaged in the operation of the specific system, in other words, For example, the number of operators may be calculated according to the proportion of the total operation amount of each operator who is engaged in the operation of the specific system. According to the sixth modified example, it is possible to generate a regression model that is more realistic and to derive a more accurate prediction result that is more realistic.

  Any combination of the above-described embodiments and modifications is also useful as an embodiment of the present invention. The new embodiment generated by the combination has the effects of the combined embodiment and the modified examples. In addition, it should be understood by those skilled in the art that the functions to be fulfilled by the constituent elements described in the claims are realized by the individual constituent elements shown in the embodiments and the modified examples or by their cooperation. .

  10 monitoring target system, 12 operation monitoring device, 14 service desk device, 20 analysis device, 52 actual system information acquisition unit, 54 operation result acquisition unit, 62 operation efficiency evaluation unit, 64 operator evaluation unit, 66 service level evaluation unit, 72 Variable acquisition unit, 74 regression analysis unit, 76 estimation unit.

Claims (5)

A first acquisition unit that acquires information about the system held in an operation monitoring apparatus that monitors an operation state of a predetermined system;
A second acquisition unit that acquires information about an operator that is held in a service desk device that supports an operator that occurs in the system and that should respond to an error detected by the operation monitoring device;
The operation efficiency of the system according to the operation scale of the system specified based on the information acquired by the first acquisition unit and the number of operators specified based on the information acquired by the second acquisition unit An evaluation unit that generates information indicating
Equipped with a,
At least one of the plurality of operators is engaged in the operation of the plurality of systems,
The information acquired by the second acquisition unit includes information indicating results of engaging in operation of one or more systems for each of the plurality of operators,
The evaluation unit calculates, for each of the plurality of operators, a ratio of being engaged in the operation of the target system for calculating the operation efficiency in the total operation amount of each operator according to the information acquired by the second acquisition unit. and, said ratio of each operator, depending on the operating scale of the target system, the analyzer characterized that you generate information indicating the operational efficiency of the target system. A first acquisition unit that acquires information about the system held in an operation monitoring apparatus that monitors an operation state of a predetermined system;
A second acquisition unit that acquires information about an operator that is held in a service desk device that supports an operator that occurs in the system and that should respond to an error detected by the operation monitoring device;
The operation efficiency of the system according to the operation scale of the system specified based on the information acquired by the first acquisition unit and the number of operators specified based on the information acquired by the second acquisition unit An evaluation unit that generates information indicating
Equipped with a,
The evaluation unit calculates the skill value of each of a plurality of operators according to the information acquired by the second acquisition unit, and engages in the operation scale of the target system for determining operation efficiency and the operation of the target system. and the number of operators was, depending on the skill value of the operator engaged in the operation of the target system, the analyzer characterized that you generate information indicating the operational efficiency of the target system. An error attribute holding unit that holds information indicating the severity of each of a plurality of types of errors that may occur in the system;
The first acquisition unit acquires information indicating an error that has occurred in the system held in the operation monitoring device,
The evaluation unit generates information indicating the operational efficiency of the system reflecting the severity of the error generated in the system according to the error generated in the system and its severity and the number of operators. The analyzer according to claim 1 or 2 . A first acquisition function for acquiring information related to the system held in an operation monitoring apparatus that monitors an operation state of a predetermined system;
A second acquisition function for acquiring information about an operator held in a service desk device that supports an operator that occurs in the system and that should respond to an error detected by the operation monitoring device;
The operation efficiency of the system according to the operation scale of the system specified based on the information acquired by the first acquisition function and the number of operators specified based on the information acquired by the second acquisition function A function for generating information indicating
Is realized on a computer ,
At least one of the plurality of operators is engaged in the operation of the plurality of systems,
The information acquired by the second acquisition function includes information indicating results of engaging in operation of one or more systems for each of the plurality of operators,
According to the information acquired by the second acquisition function, the function to generate, for each of the plurality of operators, the percentage engaged in the operation of the target system for the operation efficiency occupying the total operation amount of each operator A computer program for calculating and generating information indicating operational efficiency of the target system according to the ratio of each operator . A first acquisition function for acquiring information related to the system held in an operation monitoring apparatus that monitors an operation state of a predetermined system;
A second acquisition function for acquiring information about an operator held in a service desk device that supports an operator that occurs in the system and that should respond to an error detected by the operation monitoring device;
The operation efficiency of the system according to the operation scale of the system specified based on the information acquired by the first acquisition function and the number of operators specified based on the information acquired by the second acquisition function A function for generating information indicating
Is realized on a computer ,
The function to be generated is based on the information acquired by the second acquisition function, calculates the skill value of each of a plurality of operators, and determines the operation scale of the target system for which operation efficiency is obtained, and the operation of the target system. A computer program that generates information indicating the operation efficiency of the target system according to the number of engaged operators and the skill value of the operator engaged in the operation of the target system .

Images