JP5420385B2 - Business support device - Google Patents

Description

  The present invention relates to a business support apparatus for supporting a service desk business.

  IT service management is becoming more important than ever as IT infrastructure is being used by a wide range of users. Along with this, there is a demand for more efficient business processes in executing IT service management. Regarding IT service management and operation rules, the Office of Government Commerce (OGC) has published a collection of best practices called Information Technology Infrastructure Library (ITIL) (registered trademark).

  Service support is one of the cores of ITIL. Service support is described for daily system operation and user support, and consists of one function and five processes. As functions, a service desk that serves as a contact point for inquiries from users, and incident management, problem management, change management, release management, and configuration management are defined as processes.

  In the service desk business, what kind of inquiries were received from users, how they were responded to, whether functional / hierarchical escalation was necessary, whether the inquiries were processed and closed Accumulate know-how by recording various things. In order to support such service desk operations, a system for accumulating inquiries from users as incident tickets has been put into practical use (see, for example, Patent Documents 1 and 2).

JP 2008-129973 A JP 2005-011140 A

  Many inquiries and service requests are sent to the service desk. The service desk also receives system failure detection from the operation management tool. It is necessary to respond as quickly as possible to a large number of inquiries, service requests, and system failures (hereinafter collectively referred to as incidents). Responding to these incidents as quickly as possible leads to improved customer satisfaction.

  Until now, due to carelessness and busyness of operators and maintenance managers (hereinafter collectively referred to as persons in charge) to whom incidents have been assigned, responses to incidents may not be completed by the set deadline. .

  This invention is made | formed in view of such a condition, The objective is to provide the technique which suppresses the response delay with respect to an incident.

  An operation support apparatus according to an aspect of the present invention is an operation support apparatus for supporting a system support operation, and includes an incident reception unit that receives an inquiry from a user, a service request, or failure detection by an operation management tool as an incident, A ticket holding unit that holds an electronic ticket issued for each incident, and a time limit management unit that manages a response time limit of the incident recorded in the ticket held in the ticket holding unit. The deadline management department is responsible for responding to incidents whose remaining time until the deadline for response falls below the grace period set for the incident, among the incidents recorded in the ticket held in the ticket holding section. An alert is notified to at least one of the terminal device of the person in charge and the terminal device of the supervisor in charge.

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

  According to the present invention, it is possible to suppress a response delay to an incident.

It is a figure which shows the structure of the business assistance system which concerns on embodiment of this invention. It is a figure which shows the format example of the ticket accumulate | stored in a ticket holding part (the 1). It is a figure which shows the format example of the ticket accumulate | stored in a ticket holding part (the 2). It is a figure which shows an example of a priority table. It is a figure which shows an example of a cause division difficulty level table. It is a flowchart which shows an example of a grace period setting process. It is a figure which shows an example of a person in charge skill table. It is a flowchart which shows another example of a grace period setting process.

  FIG. 1 is a diagram showing a configuration of a business support system 500 according to an embodiment of the present invention. The business support system 500 is installed at a service desk to support system support business. The business support system 500 includes a business support device 100 and a console terminal device 200. The business support apparatus 100 can be configured with at least one server. For example, it can be composed of a web server and a database server. The console terminal device 200 can be configured by a PC. A plurality of console terminal devices 200 can be installed. In FIG. 1, one business support apparatus 100 and a plurality of console terminal apparatuses 200A, B,... Are connected by an internal network such as an intranet to constitute a server / client system.

  The business support apparatus 100 includes a control unit 110, a ticket holding unit 120, a priority table 130, a cause category difficulty level table 140, a person-in-charge skill table 150, and a communication unit 160. The control unit 110 includes an incident reception unit 111, a time limit management unit 112, a response time limit setting unit 113, and a grace period setting unit 114. The console terminal device 200 includes a communication unit 210, a control unit 220, a display unit 230, and an operation unit 240.

  The respective configurations of the business support apparatus 100 and the console terminal apparatus 200 can be realized in hardware by a CPU, memory, or other LSI of an arbitrary computer, and are realized by software loaded in a memory. However, here, functional blocks that are realized by their cooperation are depicted. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof.

  The incident reception unit 111 receives an inquiry from a user, a service request, or failure detection by an operation management tool as an incident. The ticket holding unit 120 holds an electronic ticket issued for each incident.

  Inquiries and service requests from users are sent to the service desk via telephone, FAX, postcard, sealed letter, e-mail, input form in a website, and the like. The operator of the service desk inputs the inquiry content and the service request content received through them from the operation unit 240 of the console terminal device 200 and issues the ticket. A format example of the ticket will be described later.

  Also, when inquiry information, service request information is sent through the input form in the website, and when failure detection information is sent from the operation management tool, at least some of the items in the above format The content may be automatically entered.

  The time limit management unit 112 manages the response time limit of the incident recorded in the ticket held in the ticket holding unit 120. More specifically, the time limit management unit 112 is a grace period in which the remaining period until the response time limit is set for each incident among the incidents recorded in the incident recorded in the ticket held in the ticket holding unit 120. For an incident that has fallen below the period, an alert is notified to at least one of the console terminal device 200 of the person in charge who should respond to the incident and the console terminal device 200 of the supervisor of the person in charge. For example, the grace period until the response deadline may be notified to the console terminal device 200 of the person in charge and the console terminal device 200 of the supervisor of the person in charge by e-mail. Here, the grace period may be zero. In this case, an alert is notified when the response time limit has come. A method for setting the response deadline and the grace period will be described later.

  The response time limit setting unit 113 sets a response time limit according to the priority of the accepted incident. For example, the response deadline can be determined with reference to the priority table 130. The priority table 130 describes the correspondence between the priority and the period from the draft date to the closing date that should be the corresponding deadline. A specific example of the priority table 130 will be described later.

  The grace period setting unit 114 determines the grace period in consideration of at least one of the cause classification of the accepted incident, the degree of difficulty, and the skill level of the person in charge. For example, the grace period can be determined with reference to at least one of a cause category difficulty table 140 and a person-in-charge skill table 150 described later.

  The cause category difficulty level table 140 describes associations between combinations of cause categories and difficulty levels and grace periods. The person-in-charge skill table 150 describes the skill level of each of a plurality of person-in-charge candidates who should handle an incident. Specific examples of the cause classification difficulty level table 140 and the person-in-charge skill table 150, and details of the grace period setting process by the grace period setting unit 114 will be described later.

  The communication unit 160 transmits / receives information to / from the communication unit 210 of the console terminal device 200, a communication unit of a user terminal (not shown), or a communication unit of a management operation tool (not shown).

  The communication unit 210 of the console terminal device 200 transmits / receives information to / from the communication unit 160 of the business support device 100 or the communication unit 210 of another console terminal device 200. The control unit 220 controls the console terminal device 200 as a whole. The display unit 230 displays a screen. In the present embodiment, the ticket management screen is mainly displayed. The operation unit 240 receives an operation of an operator or a person in charge and transmits it to the control unit 220.

  FIG. 2 is a diagram illustrating a format example of a ticket stored in the ticket holding unit 120 (part 1). FIG. 3 is a diagram illustrating a format example of a ticket stored in the ticket holding unit 120 (part 2). A ticket 600 is issued for each incident. 2 and 3, the ticket 600 includes basic information 610, classification information 620, progress information 630, draft date 641, and closing date 642.

  The basic information 610 includes, as items, an ID 611, a status 612, a system name 613, a title 614, a report content 615, a corresponding deadline date 616a, a corresponding deadline time 616b, a generation environment 617, and a procedure manual number 618. A serial number may be assigned to ID 611 in the order of acceptance on a daily basis. In the status 612, “accepted” is input before the corresponding person is assigned, and “allocated” is input after the corresponding person is assigned.

  The classification information 620 includes, as items, a cause category 621, a difficulty level 622, an urgency level 623, a priority level 624, a system 625, an OS 626, an OS version 627, an application 628, and a keyword 629. In the cause category 621, the cause of the incident is input. For example, “defect”, “inquiry”, “work request”, and the like are input. The difficulty level 622 is input with the incident resolution difficulty level. In the urgency level 623, an urgency level determined based on an objective factor (for example, an impact level on a customer service) is input. As the priority 624, a priority determined by adding a business viewpoint (eg, maintenance contract level, customer rank) to objective factors is input. For example, “high”, “medium”, “low”, and the like are input to the difficulty level 622, the urgency level 623, and the priority level 624.

  The system 625, the OS 626, the OS version 627, and the application 628 are items for classifying incidents. Here, an example is shown in which incidents are classified in four layers, but they may be classified in less than three layers or in five or more layers. For example, application versions may be added and classified in five layers.

  The progress information 630 is generated every time an action such as a response to a customer, a recovery work, a meeting, or the like is performed on the issued incident. The progress information 630 includes, as items, a title 631, a corresponding date 632, a corresponding time 633, a corresponding person 634, a corresponding destination 635, a channel 636, contents 637, and an attached file 638. Channel 636 is input with the channel that caused one process to be formed. For example, telephone, FAX, mail, and conference are described. In the content 637, the content of the response to the customer, the content of the recovery work, the matters determined for the conference, and the like are input. If there are document files or drawing files related to these contents, they can be attached to the attached file 638.

  As the draft date 641, the date when the ticket was drafted is input. As the closing date 642, the date when the response to the incident managed by the ticket is completed is input.

  These items are basically manually input by an operator based on the contents of an inquiry from a user, an in-house manual, an instruction from a service desk manager, and the like. Note that some items may be designed to be automatically input systematically. For example, the date and time determined by the response time limit setting unit 113 is input as the response time limit 616a and the response time limit 616b.

  FIG. 4 is a diagram illustrating an example of the priority table 130. The priority table 130 includes a priority 131 and a corresponding time limit 132 as items. The response time limit setting unit 113 can convert the priority into a response time limit with reference to the priority table 130. In the priority table 130 shown in FIG. 4, for example, when the priority is “high”, the response time limit setting unit 113 sets the next day of the draft date as the response time limit. In the example shown in FIG. 4, the corresponding deadline 132 is described in date units, but may be described in time units.

  FIG. 5 is a diagram illustrating an example of the cause category difficulty level table 140. The cause category difficulty level table 140 includes a cause category 141 and a difficulty level 142 as items. In the example illustrated in FIG. 5, “failure (for example, bug)”, “inquiry”, and “work request” are defined as the cause category 141, and “low”, “medium”, and “high” are defined as the difficulty level 142. It is prescribed. Since each is classified into three, there are nine combinations of cause categories and difficulty levels.

  The grace period setting unit 114 selects, from among the tickets held in the ticket holding unit 120, a combination of a cause category and a difficulty level set for a received new incident, and a ticket in which the cause category and the difficulty level of the same combination are set. Identify and calculate the average period from the launching to closing of those tickets, and set the average period to the grace period.

  FIG. 6 is a flowchart illustrating an example of a grace period setting process. First, when the incident reception unit 111 receives an incident (Y in S700), a ticket for the incident is issued, and the grace period setting unit 114 extracts the cause category and the difficulty level of the new incident from the ticket ( S701).

  Next, the grace period setting unit 114 identifies past incidents having the same combination as the combination of the cause category and the difficulty level of the new incident (S702). When there is one identified past incident, the period from the initial date of the incident to the closing date is set as the grace period for the new incident.

  When there are a plurality of identified past incidents, the grace period setting unit 114 calculates an average period from the draft date to the closing date of the plurality of past incidents (S703). The grace period setting unit 114 sets the calculated average period during the grace period for the new incident (S704).

  FIG. 7 is a diagram illustrating an example of the person-in-charge skill table 150. The person-in-charge skill table 150 includes a person-in-charge skill 151 and a weighting coefficient 152 as items. In the example shown in FIG. 5, the person-in-charge skill 151 is classified into three ranks of “high”, “medium”, and “low”.

  The grace period setting unit 114 is a combination of a cause category and a difficulty level set for a received new incident among the tickets held in the ticket holding unit 120, and a past incident in which the cause category and the difficulty level of the same combination are set. For each of the above, after weighting the period from drafting to closing according to the skill level of the person in charge, the average period is calculated. Then, a period in which the average period is weighted according to the skill level of the person in charge to deal with the new incident is set as a grace period for the new incident.

  At that time, the grace period setting unit 114 refers to the person-in-charge skill table 150 and weights the period from the past incident draft to the closing. For example, when the person in charge skill level of the target past incident is “high”, the period is multiplied by 1.2. When a person with a normal skill level is in charge, there is a high possibility that it will take longer than the relevant period, so this weight is adjusted. The same applies to the weighting of new incidents.

  FIG. 8 is a flowchart illustrating another example of the grace period setting process. First, when the incident reception unit 111 receives an incident (Y in S800), a ticket for the incident is issued, and the grace period setting unit 114 extracts the cause category and the difficulty level of the new incident from the ticket ( S801).

  Next, the grace period setting unit 114 identifies past incidents having the same combination as the combination of the cause classification and the difficulty level of the new incident (S802). When there is one identified past incident, the period from the initial date of the incident to the closing date is set as the grace period for the new incident. At that time, the grace period is weighted according to the skill level of the person in charge of the new incident.

  When there are a plurality of identified past incidents, the grace period setting unit 114 calculates a period from the date of drafting the plurality of past incidents to the closing date, respectively (S803). The grace period setting unit 114 weights each period according to the person-in-charge skill level (S804). The grace period setting unit 114 calculates the average period from the weighted draft date to the closing date by adding up the weighted periods and dividing by the identified number of past incidents (S805). The grace period setting unit 114 sets a period in which the calculated average period is weighted according to the skill level of the person in charge of the new incident during the grace period of the new incident (S806).

  As described above, according to the present embodiment, a response delay to an incident can be suppressed by notifying an alert to at least one terminal of the person in charge and its boss before the response deadline. Further, the alert can be notified at a more appropriate timing by flexibly setting the alert notification timing according to the cause classification, the difficulty level, the person-in-charge skill level, and the like. That is, if the alert is too early, there is a high possibility that the person in charge will ignore it. If the alert is too late, there is a high possibility that it will not be in time for the deadline even if the response is started.

  The present invention has been described based on some embodiments. It is understood by those skilled in the art that these embodiments are exemplifications, and 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. By the way.

  For example, when the timing for notifying the alert arrives, the time limit management unit 112 refers to the degree of business congestion of the person in charge to be notified, and if it is less than the set value, notifies the alert only to the console terminal device 200 of the person in charge. If the value is equal to or greater than the set value, an alert is notified to the console terminal device 200 of both the person in charge and the supervisor. When the amount of work of the person in charge is not large, it is highly likely that the person in charge will complete the response to the incident by the deadline, and problems do not easily occur even if the supervisor is not involved. On the other hand, when the amount of work of the person in charge is large, there is a high risk that the correspondence will not be completed by the deadline, so it is highly necessary for the supervisor to know and take measures such as changing the person in charge.

  DESCRIPTION OF SYMBOLS 100 Work support apparatus, 110 Control part, 111 Incident reception part, 112 Time limit management part, 113 Response time limit setting part, 114 Grace period setting part, 120 Ticket holding part, 130 Priority table, 140 Cause classification difficulty table, 150 Person skill table, 160 communication unit, 200 console terminal device, 210 communication unit, 220 control unit, 230 display unit, 240 operation unit, 500 business support system.

Claims (3)

A business support device for supporting system support business,
An incident reception unit that receives an inquiry from a user, a service request, or failure detection by an operation management tool as an incident;
A ticket holding unit that holds an electronic ticket issued for each incident;
A time limit management unit that manages the time limit for handling incidents recorded in the ticket held in the ticket holding unit;
A grace period setting unit that determines a grace period to be set for an incident in consideration of at least one of the cause category, difficulty level, and skill level of the person in charge,
With
The term management unit, of the incidents recorded in the ticket held by the ticket holder, the remaining period until the corresponding deadline, the incidents that below the grace period, the person in charge should correspond to the incident terminal Alert the device and / or its supervisor's terminal device to an alert,
The grace period setting unit identifies a combination of a cause category and a difficulty level set for the received incident, and a ticket having the same combination of the cause category and the difficulty level, among the tickets held in the ticket holding unit. And calculating the average period from drafting to closing of those tickets, and setting the average period to the grace period,
A business support device characterized by that.   The business support apparatus according to claim 1, further comprising a response time limit setting unit that sets the response time limit according to the priority of the accepted incident. It further includes a table that describes the skill level of each of a plurality of candidate candidates who should handle the incident,
The grace period setting unit weights the period from the draft to the close according to the skill level of the person in charge for each of the incidents for which the cause category and the difficulty level of the same combination are set, and then calculates the average period thereof. calculated, the average period, the period weighted in accordance with the skill level of the person to be corresponding to the received incident, business support system according to claim 1, characterized in that to set the grace period.

Images