WO2013046750A1 - Maintenance support system - Google Patents

Maintenance support system Download PDF

Info

Publication number
WO2013046750A1
WO2013046750A1 PCT/JP2012/055936 JP2012055936W WO2013046750A1 WO 2013046750 A1 WO2013046750 A1 WO 2013046750A1 JP 2012055936 W JP2012055936 W JP 2012055936W WO 2013046750 A1 WO2013046750 A1 WO 2013046750A1
Authority
WO
WIPO (PCT)
Prior art keywords
maintenance
information
condition
customer
candidate
Prior art date
Application number
PCT/JP2012/055936
Other languages
French (fr)
Japanese (ja)
Inventor
峰幸 田村
Original Assignee
株式会社日立システムズ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立システムズ filed Critical 株式会社日立システムズ
Publication of WO2013046750A1 publication Critical patent/WO2013046750A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311Scheduling, planning or task assignment for a person or group
    • G06Q10/063114Status monitoring or status determination for a person or group

Definitions

  • the present invention relates to maintenance support for customer computer systems (computer equipment such as servers) and information processing systems (maintenance support systems) related to operations and services such as help desks (customer support).
  • the present invention relates to information processing for determining maintenance personnel or the like (persons in charge).
  • Patent Document 1 (“Maintenance Management System” and the like) describes, as a problem, efficient maintenance by appropriately utilizing maintenance personnel. Solutions include remote monitoring and control systems that monitor and notify device failures, systems that maintain maintenance personnel's location information, systems that maintain maintenance capability information of maintenance personnel, A system that holds information to be provided to maintenance personnel with maintenance capabilities and a wireless terminal carried by the maintenance personnel. When a failure is notified, maintenance close to the location of the failure is based on the location information of the maintenance personnel.
  • an operator is selected (listing), the maintenance capability information of the selected maintenance worker is extracted, and the corresponding maintenance manual information is transmitted to the corresponding wireless terminal based on the extracted maintenance capability information of the maintenance worker. It is described that when a failure is notified, candidates are narrowed down according to the maintenance ability from maintenance personnel near the failure occurrence location, and corresponding maintenance / maintenance manual information is sent to the candidate. In addition, it is described that information is first extracted from maintenance personnel information having high maintenance capability information. In addition, it is described that information is transmitted to the next candidate maintenance staff when a response cannot be obtained from the destination wireless terminal.
  • the above-mentioned conventional maintenance support system has the following problems.
  • a person in charge such as a maintenance staff is assigned to the site (the device Visit to the place where is installed and conduct maintenance.
  • the maintenance staff is dispatched from the nearest base (maintenance base) to the site.
  • the base is a place / facility or the like in which a maintenance staff is normally on standby for maintenance work.
  • the maintenance staff receives the instruction, the maintenance staff carries the maintenance parts necessary for the maintenance work from the nearest base, moves to the site, and performs the maintenance work.
  • Patent Document 1 in determining the maintenance personnel who perform maintenance of equipment, the position and maintenance ability (skill level) of the maintenance personnel are considered as factors. As a result, the speed of maintenance response and the selection (in charge) of maintenance personnel appropriate in terms of capability are realized. However, considering these factors alone, the efficiency of work (maintenance correspondence) between a plurality of maintenance personnel and a plurality of bases, load distribution, and the like are insufficient.
  • the main objectives of the present invention are the appropriateness and speed of maintenance response (work), and the overall efficiency and load distribution of maintenance response (work) among multiple bases and multiple maintenance personnel. It is to provide technology that can be realized.
  • a representative form of the present invention is information processing related to operations and services such as maintenance support and help desk (customer support) for a customer computer system (computer equipment such as a server).
  • a system maintenance-compatible system, etc., having the following configuration.
  • This system has an information processing device having a function of determining a person in charge of maintenance of customer equipment from a plurality of maintenance personnel at a plurality of bases.
  • the information processing apparatus includes a diagnosis unit and a DB that stores management information, and inputs maintenance request information from the outside, for example. Based on the management information or input information, the diagnosis unit diagnoses or confirms the state of the target customer's device, the contents and conditions of necessary maintenance, and the management information or input information.
  • a plurality of A third process is performed for determining a matching of a person in charge or a candidate for a maintenance base from among a plurality of maintenance staff at the base.
  • the first condition as a necessary maintenance response condition, a maintenance person having necessary skills according to the state of the target customer's device is selected as the first candidate, and as the second condition, From one candidate, a maintenance worker at a location that is as close as possible to the target customer's equipment is selected as a second candidate, and as a third condition, maintenance work at a plurality of locations or a plurality of maintenance personnel is selected from the second candidate.
  • the maintenance staff at the site with the smallest possible load is selected as the third candidate.
  • the appropriateness and speed of maintenance response (work), and the overall efficiency and load distribution of maintenance response (work) among a plurality of bases and maintenance personnel are realizable.
  • FIG. 1 is a diagram showing an overall configuration of a system (maintenance support system) according to an embodiment of the present invention. It is a figure which shows the structural example of management information (DB) in the system of this Embodiment. It is a figure which shows the processing flow of a server (control part) in the system of this Embodiment. It is a figure which shows the processing flow of a diagnostic part in the system of this Embodiment. It is a figure which shows an example (image) of the relationship between a customer / equipment and a plurality of bases / maintenance personnel. (A), (b) is a figure which shows an example (image) of matching determination.
  • DB management information
  • the system of this embodiment has an efficient matching function including dynamic load distribution related to maintenance support (work).
  • the maintenance personnel / bases in charge of maintenance of customer computer equipment are considered in consideration of factors such as maintenance staff skills and language, distance (position) to customer equipment, and overall load status. Match and decide. In particular, the determination is automatically made so that the work load is distributed among a plurality of maintenance personnel at a plurality of bases.
  • the target customer computer device is a fixed server, and an example of performing maintenance corresponding to a failure / error will be described.
  • FIG. 1 shows the overall configuration of the system according to the present embodiment.
  • the entire system includes a center system 1, a customer system 2, a base (maintenance support base) 3, and a help desk system 4, which are networks 5, 6 such as the Internet, a wireless network, or a dedicated line. It is connected.
  • networks 5, 6 such as the Internet, a wireless network, or a dedicated line. It is connected.
  • the center system 1 is a main control system part, and has a server 10 and management information (DB) 50.
  • the server 10 includes a monitoring unit 11, a diagnosis unit 12, and an instruction unit 13 as processing units, and manages and reads / writes management information (DB) 50.
  • the diagnosis unit 12 includes a customer device diagnosis unit 12A, a base maintenance personnel diagnosis unit 12B, and a matching unit 12C.
  • the management information (DB) 50 includes customer information 51, device information 52, base information 53, maintenance staff information 54, and maintenance correspondence information 55 in detail.
  • a subsystem for managing each information (51 to 55) of the DB 50 may be provided (an existing subsystem may be used).
  • the monitoring unit 11 performs monitoring processing of the monitoring target device 21 in cooperation with the agent 22 of the monitoring target device 21 on the customer system 2 side.
  • the monitoring unit 11 receives and records the monitoring information (a1) from the agent 22, and determines / detects a failure / error state or a load state of the device 21 from the contents of the monitoring information (a1).
  • the diagnosis unit 12 performs this characteristic diagnosis process (described later) based on the processing result of the monitoring unit 11 and the DB 50, and is in charge of maintenance for the target customer (U) / device 21 (C). Decide the base (K) and maintenance staff (H).
  • the control content (such as an algorithm for matching determination) in the diagnosis unit 12 can be changed by setting (a4).
  • setting (a4) for example, the setting person of the center system 1 selects an algorithm (determination method) on the setting Web page, and gives priority to parameter values (for example, distance (time), load distribution, etc., and a threshold for determination Etc.) is changed (described later).
  • the instructing unit 13 Based on the processing result of the diagnosis unit 12 (which maintenance staff at which base is the person in charge of maintenance), the instructing unit 13 sends the instruction (a2) related to maintenance to the target base 3 (31, 32). ) And a process of acquiring information such as the status of the base and the maintenance staff from the maintenance support facility (31) and the portable terminal 32 of the maintenance staff.
  • the customer system 2 is an information processing system used by a customer (U), for example, a business system built in a customer company, and has at least a customer computer device 21 (abbreviated as “device”). .
  • the device 21 is a server or the like to be monitored and maintained by the center system 1, and is fixedly installed in the customer system 2.
  • the customer system 2 (device 21) is not limited to the above-mentioned customer company system, and may use a data center or the like. In this case, the equipment in the data center is subject to monitoring and maintenance.
  • the agent 21 is realized by software program processing, for example.
  • the agent 22 monitors the operation / state of the device 21 in cooperation with the monitoring unit 11.
  • the agent 22 issues monitoring information (a1) indicating the operation / state of the device 21 based on the setting information, and transmits it to the server 10 (monitoring unit 11) via the network 5.
  • the agent 22 may be realized by a device different from the device 21 or a program process thereof.
  • the monitoring information a1 includes, for example, information such as the ID, state, and position of the device 21. The transmission of the position information of the device 21 is not necessary when the position information is registered and managed in advance on the center system 1 side.
  • Each of the plurality of bases 3 (K) is a geographical base where the maintenance staff (H) is on standby for maintenance work, and includes a maintenance equipment 31 and maintenance parts 33 (stock).
  • Each maintenance staff (H) possesses the portable terminal 32 for business for maintenance.
  • the maintenance support facility 31 receives the instruction (a2) from the center system 1 (instruction unit 13), and sends maintenance support instruction information corresponding to the instruction (a2) to the maintenance staff (H) in the base 3. On the other hand, it outputs (list display, notification, information transmission to the portable terminal 32 of the maintenance staff, etc.).
  • the maintenance staff (H) at the base 3 receives an instruction for maintenance
  • the maintenance staff (H) goes to the equipment 21 of the customer system 2 of the target customer (U) while holding the portable terminal 32 and the necessary maintenance parts 33 and handles maintenance. (A3).
  • the portable terminal 32 includes a maintenance-compatible business application, and a maintenance-response instruction (for example, designation of date and time, customer (U), device 21 (C), etc.) or specific work for maintenance is displayed on the screen. Information of contents and the like (for example, error locations, recovery procedures, detailed information, etc.) is displayed.
  • the maintenance staff (H) can input the status of maintenance support (for example, incomplete / completed) on the screen of the mobile terminal 32 and can communicate the status to the base 3 (31), the center system 1, and the like. As a result, the center system 1 and the like can grasp the status such as incomplete / completed of the work in response to the maintenance work instruction.
  • the instruction (a 2) may be transmitted directly from the center system 1 to the mobile terminal 32.
  • the help desk system 4 is a well-known system, connected to each element (1, 2, 3), and responds to inquiries from customers (U) via telephone or the Web, etc. Provide customer support related to maintenance while cooperating with the center system 1 and the base 3. Note that this system may have a form in which the help desk system 4 is eliminated, or a form in which the help desk system 4 and the center system 1 are integrated.
  • the customer device diagnosis unit 12A performs necessary maintenance corresponding to the state of the customer (U) / device 21 side based on information such as an error state detected by the monitoring unit 11. Diagnose or check the contents (such as recovery work). Note that 12A is not necessary if the monitoring unit 11 has already diagnosed.
  • the site maintenance worker diagnosis unit 12B is in a current (real-time) state (for example, whether or not the site is in the site). Diagnose or confirm whether maintenance support is acceptable.
  • the confirmation may be performed at any time.
  • the matching unit 12C Based on the processing results of 12A and 12B (confirmation of basic preconditions for matching), the matching unit 12C sets this characteristic maintenance correspondence matching determination process (described later) with a predetermined algorithm (a4) Possible). As a result, in order to support maintenance of the device 21 (C) of the customer (U), it is matched (decided) which maintenance staff at which of the plurality of bases (K) and maintenance staff (H) is in charge. ) As a result, a suitable person in charge including the overall work load distribution is determined.
  • FIG. 2 shows a configuration example of the management information (DB) 50 (51 to 55). The management of the following information elements may be integrated and separated as appropriate.
  • FIG. 5 shows a specific example of the value of each ID (U, C, K, H, etc.).
  • the customer information 51 includes information on (a) customer ID, (b) area / region ID, (c) language, and (d) state.
  • Customer ID is information for identifying the customer (U) or the customer system 2. For example, it is indicated by Ux.
  • Area / region ID is information for identifying an area / region where the customer system 2 (device 21) exists. For example, it is indicated by Rx.
  • the language is information for identifying a language (Japanese, English, etc.) used by the customer (U) or the customer system 2. For example, it is indicated by Wx.
  • the status indicates, for example, the presence or absence of a request for maintenance as the status of the customer (U).
  • the device information 52 includes (a) device ID, (b) position, (c) configuration information / attribute information, (d) state, and information.
  • the device ID is identification information of the device 21.
  • Cx is indicated by Cx.
  • the position is position information of the device 21 (for example, by GPS).
  • Lx position information of the device 21
  • the 51 b area (R) information and the 52 b position (L) information correspond to each other and may be replaced, or only one of them may be managed.
  • the position information of b may be set in advance, or may be acquired as needed by the monitoring information (a1).
  • Configuration information / attribute information is information indicating the configuration and attributes of the device 21 and includes, for example, information indicating that the type is a server, component component identification information, and the like.
  • the status includes a code indicating the normal state, failure / error, etc. of the device 21, information indicating the load status, information indicating whether maintenance support is necessary, and the like.
  • the base information 53 includes information on (a) base ID, (b) area / region, (c) position, (d) maintenance personnel ID, and (e) status.
  • the base ID is information for identifying the base 3. For example, it is indicated by K1.
  • Area / region ID is identification information of an area / region where the base 3 exists. Indicated by R1 and the like.
  • the position is position information (by GPS or the like) of the position where the base 3 exists. As described above, only one of R and L may be managed.
  • Maintenance personnel ID is identification information of the maintenance personnel (H) related to the base 3 (K). For example, it is indicated by H1-1, H1-2, etc.
  • (d) maintenance personnel ID indicates a plurality of maintenance personnel (H) belonging to the base 3 (basically waiting).
  • the status includes information such as the ID list of maintenance personnel (H) who are currently waiting at the base 3 and the number of people (m) waiting as the status of the base 3.
  • the maintenance staff information 54 includes information on (a) maintenance staff ID, (b) skill, (c) language, (d) status, (e) charge, and (f) load.
  • the position information (L) is included in the case where the position of the maintenance staff (mobile terminal 32) is managed by GPS or the like.
  • the maintenance worker ID is identification information of the maintenance worker (H). For example, it is indicated by H1-1.
  • Skill is information indicating a skill set (ability) related to the maintenance response of the maintenance staff. For example, it is indicated by Sa. For example, the type of the equipment 21 that can be maintained, the knowledge of the equipment 21 and the skills related to the recovery work are shown.
  • the language indicates the language (Japanese, English, etc.) used by the maintenance staff. For example, it is indicated by Wa.
  • the status is the latest status of the maintenance staff, whether the maintenance staff is waiting in the base (K) to which the maintenance staff belongs or is out of the base (K) (is at the nearest base or not) It is the information which shows the states. Alternatively, it is information indicating a state such as whether the maintenance staff currently has time for maintenance support (whether a new job can be accepted), whether the job is absent, or the like.
  • the relationship between the maintenance staff (H) and the base (K) basically belongs to a specific base, but a certain maintenance staff can stop (wait) at a plurality of bases. In that case, the information may be managed including which base (K) is waiting.
  • the person in charge is information regarding the maintenance work (the unit managed in 55) that the maintenance staff is currently in charge of, and is indicated by a maintenance correspondence ID (P1 etc.).
  • the load is a kind of state, but is information indicating the magnitude of the work load of the maintenance staff.
  • the load information may be managed by a level value such as large / medium / small, the number and amount of maintenance work (units managed by 55) handled by the maintenance staff, You may express by the number of times you are in charge.
  • each base (K) and the overall situation including a plurality of bases (K) can be understood by referring to the base information 53 and maintenance staff information 54.
  • the maintenance support information 55 is information for managing individual maintenance support work, (a) maintenance support ID, (b) customer ID, (c) device ID, (d) status code, (e) Each item includes information on work contents, (f) necessary conditions, (g) charge, and (h) state. In addition, time information such as work due dates may be managed.
  • the maintenance correspondence ID is information for identifying the maintenance correspondence job. For example, it is indicated by P1.
  • the customer ID is identification information indicating the customer (U) who is the target of the maintenance correspondence (P).
  • the device ID is identification information of the device 21 (C) that is a work target of the maintenance correspondence (P).
  • the status code is a code indicating a status such as a failure / error of the device 21 (C), and corresponds to the status d of 52.
  • the work content is information indicating the work content of the maintenance correspondence (P), for example, information indicating a work procedure such as recovery according to the status code of d. The information is provided to the portable terminal 32 of the maintenance staff (H) and used as guide information.
  • Necessary conditions indicate necessary conditions related to the maintenance correspondence (P), and include, for example, necessary maintenance parts (such as b1), necessary skills (such as Sa), and necessary languages (such as Wa). .
  • the necessary maintenance parts (b1 and the like) are replacement parts necessary for the maintenance correspondence (P), and the maintenance parts 33 provided in the base 3 are used.
  • the necessary skill (Sa or the like) indicates the skill of the maintenance staff (H) required for the maintenance response (P).
  • the necessary language (Wa or the like) indicates a language required for communication with the customer (U) or operation of the device 21 in the maintenance correspondence (P). Note that the language (W) may be a recommended condition instead of a necessary condition.
  • the language (W) may be managed by being included in the concept of the skill (S).
  • the person in charge is the identification information (K1, H1-1, etc.) of the base (K) and the maintenance person (H) who is in charge of the maintenance response (P).
  • the status includes incomplete / completed as the status of the maintenance response (P).
  • FIG. 5 shows an example of the relationship between a customer (U) / device (C) and a plurality of bases (K) / maintenance personnel (H).
  • the customer system 2 / device 21 (Cx) of the target customer Ux In the area Rx (position Lx), there is the customer system 2 / device 21 (Cx) of the target customer Ux.
  • the necessary part For the maintenance response (P1) related to the error state (001) of the device Cx, the necessary part is b1, the necessary skill is Sa, and the usage language (necessary language) of the customer Ux is Wa.
  • each base 3 for example, there are K1, K2, and K3, and areas R (positions L) are R1 (L1), R2 (L2), and R3 (L3), respectively.
  • the distances (referred to as E) to the area Rx (Lx) on the customer Ux / device Cx side are defined as E1, E2, and E3.
  • the base K1 has H1-1, H1-2, etc. as the maintenance personnel to which it belongs.
  • the H1-1 is on standby, the H1-2 is out, and the standby number (m) in K1 is 1. is there.
  • the base K2 has H2-1, H2-2, etc. as maintenance personnel to which it belongs, for example, all are on standby, and the number of standby persons (m) in K2 is 2.
  • the base K3 has H3-1, H3-2, H3-3, etc. as maintenance personnel to which it belongs, for example, all of them are on standby, and the number of people waiting in K3 (m) is 3.
  • FIG. 3 shows a processing example of the server (control unit) 10 in this system (s1 and the like indicate processing steps).
  • the monitoring unit 11 determines and detects the state of failure / error of the target customer (U) side device 21 (C) from the monitoring information a1, The information is reflected in the customer information 51 and the device information 52 of the DB 50. Alternatively, a maintenance request is received from the help desk system 4 as another trigger.
  • the customer device diagnosis unit 12A uses the information from the monitoring unit 11 of s0 (eg, customer ID, device ID, error status code, etc.) and DB50 (51, 52) as the target customer ( U)-Diagnose or confirm the state of the device (C), the required maintenance (P) work contents and necessary conditions (required maintenance parts, required skills, required language, etc.) according to the state, and check the DB50 ( The maintenance information 55 etc. is reflected. For example, 55 values a to f are stored.
  • the site maintenance staff diagnosis unit 12B based on the information from the monitoring unit 11 of s0 and the DB 50 (53, 54), each of the target (candidate) sites (K) and maintenance personnel (H) The current (latest) state (whether waiting in the base 3 or whether maintenance support can be accepted, etc.) is diagnosed or confirmed, and processing to reflect in the DB 50 (53, 54) is performed.
  • the matching unit 12C Based on the result information (DB50) of s1 and s2, the matching unit 12C performs maintenance on the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side (P ) Matching determination process (FIG. 4).
  • the diagnosis unit 12 selects and determines a predetermined number (for example, one person) of bases (K) and maintenance staff (H) who actually take charge of the maintenance response (P) from the candidate results of s3, Processing to reflect in DB50 (55 etc.) is performed. For example, 55 g values are stored.
  • a predetermined number of people in s4 an appropriate method such as random or round robin can be used. Note that if the result of s3 has already been narrowed down to one candidate, s4 may be unnecessary. It should be noted that the number of persons in charge can be set to a plurality of persons instead of one according to the target job (P).
  • the instruction unit 13 includes the work contents of maintenance correspondence (P) to the corresponding base (K) / maintenance staff (H) (corresponding equipment 31 and portable terminal 32) according to the result of s4 (DB50). Processing to transmit the instruction (a2) is performed. Thereby, maintenance correspondence (a3) is implemented by the person in charge according to the instruction (a2).
  • FIG. 4 shows a processing example of the matching unit 12C (s3 in FIG. 3) of the diagnosis unit 12.
  • the matching unit 12C Based on the processing result information (DB50) of 12A and 12B in FIG. 3, the matching unit 12C performs maintenance support on the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side.
  • Matching determination processing is performed by a predetermined algorithm (based on setting a4). This determination is roughly divided into a first condition determination (s3-1), a second condition determination (s3-2), and a third condition determination (s3-3).
  • (S3-1) First condition determination: First, as a basic condition (necessary condition), the maintenance-ready work is currently in a state where it can be accepted, and a skill that can deal with an error or the like of the target device (C) ( S), and the first candidate is extracted from the viewpoint of using the same language (W) as the target customer (U).
  • the matching unit 12C has the necessary skill (S) and the necessary language (W) for the target maintenance work (P) as the first condition, and has a base (K) instead of a holiday. From the DB 50, the maintenance personnel (H) and the corresponding bases (K) satisfying the first condition, which are in a waiting state, etc., are in a state where there is a time vacancy for the job (P) at that time and can be accepted from the DB 50. This is extracted by searching, and this is set as the first candidate.
  • the distance E between the areas R of the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side is determined.
  • the distance E is determined by a range F divided by a predetermined length (for example, every 5 km).
  • the base (K) with the closest distance E (range F) and the corresponding maintenance staff (H) are extracted (selected) and set as the second candidate.
  • the load distribution of the maintenance work at the second candidate site (K) / maintenance staff (H) (a state where the number of waiting persons is sufficiently secured and the load is not too high) is determined. For example, a base (K) / maintenance worker (H) having the smallest load is selected from a plurality of candidates, and this is set as the third candidate. Since the person in charge is finally determined in s4, a plurality of candidates may be selected.
  • the maintenance personnel H having the smallest load is selected.
  • the above-described matching determination algorithm is a case in which the charge (candidate) is determined in consideration of the distance (second condition) first and then the load distribution (third condition). is there. Not limited to this, it is also possible to reverse the priority order and determine the charge (candidate) in consideration of the load distribution (third condition) first and then the distance (second condition). is there. Furthermore, whether to assign priority (candidate) with priority given to distance (time) or load distribution viewpoints (conditions and effects) can be variably controlled by setting (a4), instruction input, state detection, or the like. Good. For example, when it is detected that the state of the target device 21 is serious, or when the customer (U) requests immediate help from the help desk (4), the distance is determined first. If this is not the case, it may be decided to prioritize load balancing.
  • FIG. 6 shows an example of matching determination by the diagnosis unit 12.
  • the ID value in FIG. 6 corresponds to the example in FIG. FIG. 6A shows a first example, and FIG. 6B shows a second example.
  • An asterisk indicates a candidate selected in the matching determination.
  • Each base K1, K2, K3 is a case where it becomes far from the area Rx (Lx) of the customer Ux (Cx) in the order of the above-mentioned distances E1, E2, E3.
  • a method for determining the distance E between the customer U side and the base K side a method for determining the distance between the areas R is used, but a method for determining the distance between the positions L may be used.
  • a determination method of the distance E a method of calculating the distance E in detail may be used.
  • the distance E is divided into a predetermined range (F), and the distance division range F is a unit.
  • a method for determining as follows is used.
  • the bases K1 (E1) and K2 (E2) are included in the range F1
  • the base K3 (E3) is included in the range F2
  • F1 (K1, K2) is closer than F2 (K3).
  • maintenance personnel H H1-1 to H3-3) are present in each base K.
  • all of these maintenance personnel have a skill Sa and a language Wa for maintenance correspondence (P1) of the device Cx.
  • H1-1 in K1, H2-2 in K2, and H3-3 in K3 are heavy, and H2-1 in K2, H3-1 in K3 , H3-2 is assumed to have a small load.
  • the first candidates are the six persons (H1-1 to H3-3) shown in the figure who have the necessary skills Sa and the like.
  • the second candidates are three persons (H1-1, H2-1, H2-2) corresponding to F1 having a short distance E (range F).
  • the third candidate is H2-1 (one person) corresponding to the condition with the smallest load state in F1.
  • H1-1 in K1 is applicable, but if H1-1 is in charge, Since the number of waiting in K1 is 0, it is determined as NG (exclusion). Therefore, H2-1 in K2 is OK (third candidate) because the load is small.
  • the state is almost the same as that in FIG. 6A, but both the loads H2-1 and H2-2 in K2 are in a large load state.
  • the first candidates are six persons (H1-1 to H3-3) shown in the figure.
  • the second candidates are initially three persons (H1-1, H2-1, H2-2) corresponding to F1 having a short distance E (range F).
  • range F range F
  • the second candidate is determined again as NG, and three persons (H3-1 to H3-3) corresponding to the next closest range F2 are obtained.
  • the third candidates are H3-1 and H3-2 (two people) that meet the condition with the smallest load in the range F2.
  • H2-1 in K2 is close, but the load is large, so it is NG, and even if it is a little far away, H3-1 etc. with a small load is OK (third candidate).
  • an algorithm that prioritizes load distribution over distance is used.
  • the distance is determined as the second condition and the load distribution is determined as the third condition.
  • the first condition and the second condition are used.
  • the candidate / charge may be determined, or the candidate / charge may be determined only by the first condition and the third condition.
  • the previous (past) May be determined to be the same person in charge.
  • the load on the maintenance staff who becomes the person in charge may increase, but for example, by distributing the load so that other maintenance staff is in charge of the subsequent work, the load on the maintenance staff is suppressed.
  • the past processing information is stored as a history in the center system 1 (DB 50), and the above processing is realized by referring to the history information at the time of matching.
  • the language (W) or the like may be determined as a recommended condition instead of being determined as an essential condition.
  • the candidate is determined with the skill S or the like as an indispensable condition or priority condition and the language W as a recommended condition (considering as much as possible the same as the language W of the customer U). If the candidate maintenance staff H is not the same as the language W of the customer U, for example, a plurality of persons in charge are determined so that another person who is the same as the language W of the customer U is accompanied.
  • setting (a4) not only distance priority and load distribution priority but also skill priority and language priority can be set similarly.
  • the distance information and the time information may be related to each other and managed in the DB 50.
  • the determination of the distance under the second condition is a time determination directly.
  • the shortest travel time from the base K / maintenance staff H side to the customer U / equipment C side is the candidate.
  • the present invention can be used for a help desk system, an integrated monitoring system, and the like.

Abstract

Provided is a technique with which it is possible to achieve suitable and prompt maintenance support, as well as overall efficiency and load distribution of the maintenance support among a plurality of locations and a plurality of maintenance workers. A diagnostic unit in a server of the present system performs, on the basis of management information (DB) or the like, a process for the matching determination of a person in charge or a candidate maintenance worker at a location, from a plurality of maintenance workers at a plurality of locations, in order to provide maintenance support for a device of a customer to be supported. In this process: as a first condition (s3-1), maintenance workers having necessary skills appropriate for the state of the device of the customer to be supported are selected as first candidates; as a second condition (s3-2), maintenance workers at locations closest in distance to the device of the customer to be supported are selected from the first candidates as second candidates; and as a third condition (s3-3), a maintenance worker at a location with the smallest load is selected from the second candidates as a third candidate, such that the load of maintenance support tasks is distributed among the plurality of locations or the plurality of maintenance workers.

Description

保守対応システムMaintenance support system
 本発明は、顧客のコンピュータシステム(サーバ等のコンピュータ機器)を対象とした保守対応やヘルプデスク(顧客サポート)等の業務・サービスに係わる情報処理システム(保守対応システム)等に関し、特に、保守対応を行う保守員等(担当者)を決定する情報処理に関する。 The present invention relates to maintenance support for customer computer systems (computer equipment such as servers) and information processing systems (maintenance support systems) related to operations and services such as help desks (customer support). The present invention relates to information processing for determining maintenance personnel or the like (persons in charge).
 従来、顧客のコンピュータシステムの保守対応やヘルプデスク等の業務・サービスに係わる保守対応システムの代表的な構成例として、対象の機器の状態を監視して、障害・エラー等の状態を検知した時、必要な復旧作業等の保守対応内容を判定し、保守対応を行う保守員を決定し、当該保守員へ保守対応の指示情報を通知する、といったシステムが挙げられる。 Conventionally, as a typical configuration example of maintenance support systems related to customer computer system maintenance and operations and services such as help desks, when the status of the target device is monitored and a failure or error is detected A system in which the contents of maintenance such as necessary recovery work are determined, a maintenance person who performs maintenance is determined, and the maintenance support instruction information is notified to the maintenance staff.
 先行技術例として、特開2002-203064号公報(特許文献1)などがある。特許文献1(「保守管理システム」等)では、課題として、保守員を適切に有効活用して効率的な保守を行うことが記載されている。解決手段として、機器の障害を監視し通知する遠隔監視制御システムと、保守員の位置情報を保持するシステムと、保守員の保守能力情報を保持するシステムと、機器の障害内容に対応して各保守能力の保守員へ提供すべき情報を保持するシステムと、保守員が携帯する無線端末とを有し、障害発生が通知されると、保守員の位置情報に基づき、障害発生位置に近い保守員を選び(リスティング)、選んだ保守員の保守能力情報を取り出し、取り出された保守員の保守能力情報に基づき、対応保守マニュアル情報を該当の無線端末へ送信することが記載されている。障害が通知された際に、障害発生場所に近い保守員から保守能力に応じて候補が絞られ、候補に対し対応する保守保全マニュアル情報が送られることが記載されている。また、保守能力情報の高い保守員の情報から先に取り出すことが記載されている。また、送信先の無線端末から応答が得られない場合に、次候補の保守員へ情報を送信することが記載されている。 As a prior art example, there is JP-A-2002-203064 (Patent Document 1). Patent Document 1 (“Maintenance Management System” and the like) describes, as a problem, efficient maintenance by appropriately utilizing maintenance personnel. Solutions include remote monitoring and control systems that monitor and notify device failures, systems that maintain maintenance personnel's location information, systems that maintain maintenance capability information of maintenance personnel, A system that holds information to be provided to maintenance personnel with maintenance capabilities and a wireless terminal carried by the maintenance personnel. When a failure is notified, maintenance close to the location of the failure is based on the location information of the maintenance personnel. It is described that an operator is selected (listing), the maintenance capability information of the selected maintenance worker is extracted, and the corresponding maintenance manual information is transmitted to the corresponding wireless terminal based on the extracted maintenance capability information of the maintenance worker. It is described that when a failure is notified, candidates are narrowed down according to the maintenance ability from maintenance personnel near the failure occurrence location, and corresponding maintenance / maintenance manual information is sent to the candidate. In addition, it is described that information is first extracted from maintenance personnel information having high maintenance capability information. In addition, it is described that information is transmitted to the next candidate maintenance staff when a response cannot be obtained from the destination wireless terminal.
特開2002-203064号公報JP 2002-203064 A
 前述の従来の保守対応システムでは、以下のような課題がある。 The above-mentioned conventional maintenance support system has the following problems.
 従来のシステムにおいて、例えば顧客のサーバ等のコンピュータ機器の障害状態を監視で検知した場合などに、例えば当該機器の復旧作業等の保守対応のために、保守員等の担当者が現地(当該機器が設置されている場所)へ訪問し、保守対応を実施する。その際、当該保守員は、最寄りの拠点(保守対応拠点)から現地へ派遣される。拠点は、保守員が保守対応の業務のために通常待機(スタンバイ)している場所・施設等である。保守員は、指示を受けると、最寄りの拠点から、保守作業に必要な保守部品などを携えて、現地へ移動し、保守作業等を実施する。 In a conventional system, for example, when a failure state of a computer device such as a customer's server is detected by monitoring, a person in charge such as a maintenance staff is assigned to the site (the device Visit to the place where is installed and conduct maintenance. At that time, the maintenance staff is dispatched from the nearest base (maintenance base) to the site. The base is a place / facility or the like in which a maintenance staff is normally on standby for maintenance work. When the maintenance staff receives the instruction, the maintenance staff carries the maintenance parts necessary for the maintenance work from the nearest base, moves to the site, and performs the maintenance work.
 しかし、上記拠点で待機する保守員(要求されている保守対応のための適切なスキル等を持つ保守員)が不足する場合、要求されている保守対応を迅速に実現できない場合がある。例えば、複数の拠点のうち一部の拠点で待機している保守員が不足したり、拠点内の複数の保守員のうち一部の保守員に担当が集中したり、といったように、仕事の負荷が偏る場合がある。従来のシステムは、複数の保守員・複数の拠点間における仕事(保守対応)の効率性や負荷分散などについては不十分である。 However, if there is a shortage of maintenance personnel (maintenance personnel with appropriate skills for the required maintenance response) waiting at the above-mentioned bases, the required maintenance response may not be realized quickly. For example, there is a shortage of maintenance personnel waiting at some of the multiple locations, or the work is concentrated on some of the multiple maintenance personnel within the location. The load may be uneven. Conventional systems are insufficient in terms of work efficiency (maintenance support) and load distribution among a plurality of maintenance personnel and a plurality of bases.
 また、顧客の機器の適切な保守対応のために、適切なスキルや言語を持つ保守員を担当させることが好ましいが、拠点に適切なスキルや言語を持つ保守員が待機しているとは限らず、適切な保守対応、迅速な保守対応を実現できない場合がある。スキルについては、対象の機器(サーバ等)の復旧作業等のための知識などが要求される。言語については、顧客とのコミュニケーション(会話などを含む)で顧客の使用する言語(例えば地域などによって異なる)によってはうまくコミュニケーションできず時間を要してしまう場合がある。 In addition, it is preferable to have maintenance personnel with appropriate skills and languages in charge of appropriate maintenance of customer equipment. However, maintenance personnel with appropriate skills and languages are not always at the site. Therefore, there are cases where appropriate maintenance response and quick maintenance response cannot be realized. As for the skill, knowledge for recovery work of the target device (server, etc.) is required. As for language, communication (including conversation) with a customer may not be able to communicate well depending on the language (for example, different depending on the region) used by the customer.
 また例えば特許文献1では、機器の保守対応を行う保守員を決めるにあたり、要因として、保守員の位置と保守能力(スキルレベル)を考慮している。これにより、保守対応の迅速性や、能力的に適切な保守員の選択(担当)を実現している。しかしながら、これら要因の考慮だけでは、複数の保守員・複数の拠点間における仕事(保守対応)の効率性や負荷分散などについては不十分である。 Also, for example, in Patent Document 1, in determining the maintenance personnel who perform maintenance of equipment, the position and maintenance ability (skill level) of the maintenance personnel are considered as factors. As a result, the speed of maintenance response and the selection (in charge) of maintenance personnel appropriate in terms of capability are realized. However, considering these factors alone, the efficiency of work (maintenance correspondence) between a plurality of maintenance personnel and a plurality of bases, load distribution, and the like are insufficient.
 以上を鑑み、本発明の主な目的は、保守対応(仕事)の適切性、迅速性、及び複数の拠点・複数の保守員間における保守対応(仕事)の全体的な効率性・負荷分散を実現できる技術を提供することである。 In view of the above, the main objectives of the present invention are the appropriateness and speed of maintenance response (work), and the overall efficiency and load distribution of maintenance response (work) among multiple bases and multiple maintenance personnel. It is to provide technology that can be realized.
 上記目的を達成するため、本発明のうち代表的な形態は、顧客のコンピュータシステム(サーバ等のコンピュータ機器)を対象とした保守対応やヘルプデスク(顧客サポート)等の業務・サービスに係わる情報処理システム(保守対応システム)、等であって、以下に示す構成を有することを特徴とする。 In order to achieve the above object, a representative form of the present invention is information processing related to operations and services such as maintenance support and help desk (customer support) for a customer computer system (computer equipment such as a server). A system (maintenance-compatible system), etc., having the following configuration.
 本システムは、複数の拠点の複数の保守員の中から顧客の機器の保守対応を行う担当者を決定する機能を持つ情報処理装置を有する。情報処理装置は、診断部と、管理情報を格納するDBとを有し、例えば外部から保守対応の要求の情報を入力する。診断部は、管理情報または入力情報をもとに、対象の顧客の機器の状態、必要な保守対応の内容及び条件を診断または確認する第1の処理と、管理情報または入力情報をもとに、複数の拠点と複数の保守員の最新の状態を診断または確認する第2の処理と、第1、第2の処理をもとに、対象の顧客の機器の保守対応のために、複数の拠点の複数の保守員の中から、担当者またはその候補となる拠点の保守員をマッチング判定する第3の処理とを行う。第3の処理において、第1条件として、必要な保守対応の条件として、対象の顧客の機器の状態に応じた必要なスキルを持つ保守員を第1候補として選択し、第2条件として、第1候補から、対象の顧客の機器との距離がなるべく近い拠点の保守員を第2候補として選択し、第3条件として、第2候補から、複数の拠点または複数の保守員における保守対応の仕事の負荷分散が実現されるように、負荷がなるべく小さい拠点の保守員を第3候補として選択する。 This system has an information processing device having a function of determining a person in charge of maintenance of customer equipment from a plurality of maintenance personnel at a plurality of bases. The information processing apparatus includes a diagnosis unit and a DB that stores management information, and inputs maintenance request information from the outside, for example. Based on the management information or input information, the diagnosis unit diagnoses or confirms the state of the target customer's device, the contents and conditions of necessary maintenance, and the management information or input information. Based on the second process for diagnosing or confirming the latest status of a plurality of bases and a plurality of maintenance personnel, and the first and second processes, a plurality of A third process is performed for determining a matching of a person in charge or a candidate for a maintenance base from among a plurality of maintenance staff at the base. In the third process, as the first condition, as a necessary maintenance response condition, a maintenance person having necessary skills according to the state of the target customer's device is selected as the first candidate, and as the second condition, From one candidate, a maintenance worker at a location that is as close as possible to the target customer's equipment is selected as a second candidate, and as a third condition, maintenance work at a plurality of locations or a plurality of maintenance personnel is selected from the second candidate. In order to realize the load distribution, the maintenance staff at the site with the smallest possible load is selected as the third candidate.
 本発明のうち代表的な形態によれば、保守対応(仕事)の適切性、迅速性、及び複数の拠点・複数の保守員間における保守対応(仕事)の全体的な効率性・負荷分散を実現できる。 According to a typical embodiment of the present invention, the appropriateness and speed of maintenance response (work), and the overall efficiency and load distribution of maintenance response (work) among a plurality of bases and maintenance personnel. realizable.
本発明の一実施の形態のシステム(保守対応システム)の全体の構成を示す図である。1 is a diagram showing an overall configuration of a system (maintenance support system) according to an embodiment of the present invention. 本実施の形態のシステムにおける、管理情報(DB)の構成例を示す図である。It is a figure which shows the structural example of management information (DB) in the system of this Embodiment. 本実施の形態のシステムにおける、サーバ(制御部)の処理フローを示す図である。It is a figure which shows the processing flow of a server (control part) in the system of this Embodiment. 本実施の形態のシステムにおける、診断部の処理フローを示す図である。It is a figure which shows the processing flow of a diagnostic part in the system of this Embodiment. 顧客・機器と複数の拠点・保守員との関係の一例(イメージ)を示す図である。It is a figure which shows an example (image) of the relationship between a customer / equipment and a plurality of bases / maintenance personnel. (a),(b)は、マッチング判定の一例(イメージ)を示す図である。(A), (b) is a figure which shows an example (image) of matching determination.
 以下、本発明の実施の形態を図面に基づいて詳細に説明する。なお、実施の形態を説明するための全図において、同一部には原則として同一符号を付し、その繰り返しの説明は省略する。なお説明上、適宜、U:顧客、C:機器、K:拠点、H:保守員、といった記号を使用する。 Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted. For the sake of explanation, symbols such as U: customer, C: equipment, K: base, H: maintenance personnel are used as appropriate.
 <概要等>
 本実施の形態のシステム(図1等)は、保守対応(仕事)に関する動的負荷分散を含む効率的なマッチング機能を持つ。この機能では、顧客コンピュータ機器の保守対応のために担当させる保守員・拠点を、保守員のスキルや言語、顧客機器との距離(位置)、及び全体的な負荷状態などの要因を考慮してマッチングし決定する。特に、複数の拠点の複数の保守員の間における仕事の負荷分散の状態になるように自動的に判断される。
<Summary>
The system of this embodiment (FIG. 1 and the like) has an efficient matching function including dynamic load distribution related to maintenance support (work). In this function, the maintenance personnel / bases in charge of maintenance of customer computer equipment are considered in consideration of factors such as maintenance staff skills and language, distance (position) to customer equipment, and overall load status. Match and decide. In particular, the determination is automatically made so that the work load is distributed among a plurality of maintenance personnel at a plurality of bases.
 本例では特に、対象の顧客コンピュータ機器が固定的なサーバでありその障害・エラー等の場合の保守対応を実施する例を用いて説明する。 In this example, the target customer computer device is a fixed server, and an example of performing maintenance corresponding to a failure / error will be described.
 [システム]
 図1において、本実施の形態のシステムの全体の構成を示している。本システム全体は、センターシステム1と、顧客システム2と、拠点(保守対応拠点)3と、ヘルプデスクシステム4とを有し、これらがインターネット、無線網、あるいは専用線などのネットワーク5,6で接続されている。
[system]
FIG. 1 shows the overall configuration of the system according to the present embodiment. The entire system includes a center system 1, a customer system 2, a base (maintenance support base) 3, and a help desk system 4, which are networks 5, 6 such as the Internet, a wireless network, or a dedicated line. It is connected.
 (1) センターシステム1は、主制御システム部分であり、サーバ10及び管理情報(DB)50を有する。サーバ10は、処理部として、監視部11、診断部12、指示部13を有し、管理情報(DB)50を管理・読み書きして処理を行う。診断部12は、詳しくは、顧客機器診断部12A、拠点保守員診断部12B、マッチング部12Cを有する。管理情報(DB)50は、詳しくは、顧客情報51、機器情報52、拠点情報53、保守員情報54、保守対応情報55を含む。なおDB50の各情報(51~55)を管理するためのサブシステムを設けてもよい(既存のサブシステムを利用してもよい)。 (1) The center system 1 is a main control system part, and has a server 10 and management information (DB) 50. The server 10 includes a monitoring unit 11, a diagnosis unit 12, and an instruction unit 13 as processing units, and manages and reads / writes management information (DB) 50. Specifically, the diagnosis unit 12 includes a customer device diagnosis unit 12A, a base maintenance personnel diagnosis unit 12B, and a matching unit 12C. The management information (DB) 50 includes customer information 51, device information 52, base information 53, maintenance staff information 54, and maintenance correspondence information 55 in detail. A subsystem for managing each information (51 to 55) of the DB 50 may be provided (an existing subsystem may be used).
 監視部11は、顧客システム2側の監視対象の機器21のエージェント22と連携して、監視対象の機器21の監視処理を行う。監視部11は、エージェント22から監視情報(a1)を受信して記録すると共に、監視情報(a1)の内容から機器21の障害・エラー等の状態や負荷状態などを判断・検知する。 The monitoring unit 11 performs monitoring processing of the monitoring target device 21 in cooperation with the agent 22 of the monitoring target device 21 on the customer system 2 side. The monitoring unit 11 receives and records the monitoring information (a1) from the agent 22, and determines / detects a failure / error state or a load state of the device 21 from the contents of the monitoring information (a1).
 診断部12は、監視部11の処理結果及びDB50をもとに、本特徴的な診断処理(後述)を行い、対象の顧客(U)・機器21(C)の保守対応のために担当させる拠点(K)・保守員(H)を決定する。診断部12での制御内容(マッチング判定の際のアルゴリズム等)は、設定(a4)により変更可能となっている。設定(a4)は例えばセンターシステム1の設定者により設定用Webページでアルゴリズム(判定方式)を選択したりそのパラメータ値(例えば距離(時間)や負荷分散などの優先する観点や、判定用の閾値など)を変更する形などである(後述)。 The diagnosis unit 12 performs this characteristic diagnosis process (described later) based on the processing result of the monitoring unit 11 and the DB 50, and is in charge of maintenance for the target customer (U) / device 21 (C). Decide the base (K) and maintenance staff (H). The control content (such as an algorithm for matching determination) in the diagnosis unit 12 can be changed by setting (a4). For the setting (a4), for example, the setting person of the center system 1 selects an algorithm (determination method) on the setting Web page, and gives priority to parameter values (for example, distance (time), load distribution, etc., and a threshold for determination Etc.) is changed (described later).
 指示部13は、診断部12の処理結果(どの拠点のどの保守員を保守対応の担当者とするか)をもとに、保守対応に係わる指示(a2)を対象の拠点3(31,32)へ送信する処理や、保守対応用設備(31)や保守員の携帯端末32から当該拠点や保守員の状態などの情報を取得する処理を行う。 Based on the processing result of the diagnosis unit 12 (which maintenance staff at which base is the person in charge of maintenance), the instructing unit 13 sends the instruction (a2) related to maintenance to the target base 3 (31, 32). ) And a process of acquiring information such as the status of the base and the maintenance staff from the maintenance support facility (31) and the portable terminal 32 of the maintenance staff.
 (2) 顧客システム2は、顧客(U)が利用する情報処理システムであり、例えば顧客企業内に構築された業務用システム等であり、少なくとも顧客コンピュータ機器21(「機器」と略す)を有する。機器21は、センターシステム1により監視・保守の対象となる、例えばサーバ等であり、顧客システム2内に固定的に設置されている。なお、顧客システム2(機器21)は、上記顧客企業内システムに限らず、データセンタ等を利用する形でもよい。この場合はデータセンタ内の機器が監視・保守の対象となる。 (2) The customer system 2 is an information processing system used by a customer (U), for example, a business system built in a customer company, and has at least a customer computer device 21 (abbreviated as “device”). . The device 21 is a server or the like to be monitored and maintained by the center system 1, and is fixedly installed in the customer system 2. Note that the customer system 2 (device 21) is not limited to the above-mentioned customer company system, and may use a data center or the like. In this case, the equipment in the data center is subject to monitoring and maintenance.
 機器21では、業務処理などが行われると共に、エージェント21が稼働する。エージェント22は、例えばソフトウェアプログラム処理で実現される。エージェント22は、監視部11と連携し、機器21の動作・状態を監視する。例えば、エージェント22は、設定情報に基づき、機器21の動作・状態を表す監視情報(a1)を発行してネットワーク5を介してサーバ10(監視部11)へ送信する。なお、エージェント22は、機器21とは別の装置やそのプログラム処理などで実現されてもよい。監視情報a1は、例えば、機器21のID,状態、位置などの情報を含む。なお機器21の位置情報の送信は、予めセンターシステム1側で当該位置情報が登録・管理されている場合は必要無い。 In the device 21, business processing and the like are performed, and the agent 21 is activated. The agent 22 is realized by software program processing, for example. The agent 22 monitors the operation / state of the device 21 in cooperation with the monitoring unit 11. For example, the agent 22 issues monitoring information (a1) indicating the operation / state of the device 21 based on the setting information, and transmits it to the server 10 (monitoring unit 11) via the network 5. The agent 22 may be realized by a device different from the device 21 or a program process thereof. The monitoring information a1 includes, for example, information such as the ID, state, and position of the device 21. The transmission of the position information of the device 21 is not necessary when the position information is registered and managed in advance on the center system 1 side.
 (3) 複数の各拠点3(K)は、保守員(H)が保守対応の業務のために待機する地理的な拠点であり、保守対応用設備31や保守部品33(ストック)を備える。各保守員(H)は、保守対応の業務用に、携帯端末32を所持する。保守対応用設備31は、センターシステム1(指示部13)からの指示(a2)を受信し、当該指示(a2)に対応する保守対応指示情報を、当該拠点3内の保守員(H)に対して出力(一覧表示、報知、あるいは保守員の携帯端末32への情報送信等)する。拠点3の保守員(H)は、保守対応の指示を受けた場合、携帯端末32及び必要な保守部品33を持ちつつ、対象の顧客(U)の顧客システム2の機器21へ出向き、保守対応のコミュニケーションや作業などを実施する(a3)。 (3) Each of the plurality of bases 3 (K) is a geographical base where the maintenance staff (H) is on standby for maintenance work, and includes a maintenance equipment 31 and maintenance parts 33 (stock). Each maintenance staff (H) possesses the portable terminal 32 for business for maintenance. The maintenance support facility 31 receives the instruction (a2) from the center system 1 (instruction unit 13), and sends maintenance support instruction information corresponding to the instruction (a2) to the maintenance staff (H) in the base 3. On the other hand, it outputs (list display, notification, information transmission to the portable terminal 32 of the maintenance staff, etc.). When the maintenance staff (H) at the base 3 receives an instruction for maintenance, the maintenance staff (H) goes to the equipment 21 of the customer system 2 of the target customer (U) while holding the portable terminal 32 and the necessary maintenance parts 33 and handles maintenance. (A3).
 携帯端末32は、保守対応の業務用のアプリケーションを備えており、画面に、保守対応指示(例えば日時、顧客(U)、機器21(C)などの指定)や、保守対応の具体的な作業内容等の指示(例えばエラー等の箇所、復旧手順、詳細情報など)の情報を表示する。また保守員(H)は、携帯端末32の画面に保守対応の状況(例えば未完了/済みなど)を入力し、拠点3(31)や、センターシステム1等へ状況を伝えることができる。これにより、センターシステム1等は、保守対応の仕事の指示に対しての当該仕事の未完了/済みなどの状態を把握できる。 The portable terminal 32 includes a maintenance-compatible business application, and a maintenance-response instruction (for example, designation of date and time, customer (U), device 21 (C), etc.) or specific work for maintenance is displayed on the screen. Information of contents and the like (for example, error locations, recovery procedures, detailed information, etc.) is displayed. In addition, the maintenance staff (H) can input the status of maintenance support (for example, incomplete / completed) on the screen of the mobile terminal 32 and can communicate the status to the base 3 (31), the center system 1, and the like. As a result, the center system 1 and the like can grasp the status such as incomplete / completed of the work in response to the maintenance work instruction.
 なお保守対応用設備31を省略する形態や、携帯端末32を省略する形態とすることができる。保守対応用設備31を省略する形態の場合は、センターシステム1から携帯端末32へ直接的に指示(a2)を送信してもよい。 In addition, it can be set as the form which abbreviate | omits the equipment 31 for a maintenance, and the portable terminal 32. In the case of omitting the maintenance support facility 31, the instruction (a 2) may be transmitted directly from the center system 1 to the mobile terminal 32.
 (4) ヘルプデスクシステム4は、公知のシステムであり、各要素(1,2,3)と接続され、顧客(U)からの電話やWeb等での問い合わせに対して応対者により応対し、センターシステム1や拠点3と連携しながら、保守対応に係わる顧客サポートを行う。なお本システムは、ヘルプデスクシステム4を無くした形態、ヘルプデスクシステム4とセンターシステム1を統合した形態も可能である。 (4) The help desk system 4 is a well-known system, connected to each element (1, 2, 3), and responds to inquiries from customers (U) via telephone or the Web, etc. Provide customer support related to maintenance while cooperating with the center system 1 and the base 3. Note that this system may have a form in which the help desk system 4 is eliminated, or a form in which the help desk system 4 and the center system 1 are integrated.
 (12) 診断部12において、顧客機器診断部12Aは、監視部11で検知したエラー状態などの情報をもとに、当該顧客(U)・機器21側の状態に応じた、必要な保守対応の内容(復旧作業など)を診断または確認する。なお監視部11で診断済みの場合は12Aは不要である。 (12) In the diagnosis unit 12, the customer device diagnosis unit 12A performs necessary maintenance corresponding to the state of the customer (U) / device 21 side based on information such as an error state detected by the monitoring unit 11. Diagnose or check the contents (such as recovery work). Note that 12A is not necessary if the monitoring unit 11 has already diagnosed.
 拠点保守員診断部12Bは、監視部11によるエラー状態などの検知時に、複数の各拠点3(K)・保守員(H)側の現在(リアルタイム)の状態(例えば拠点内に待機中か否か、保守対応を受け付け可能か否か等)を診断または確認する。当該確認は、随時実行しておくこととしてもよい。特に保守対応の迅速化の観点から、予め各拠点3等から情報を取得して最新の状況を確認し必要な情報を保持しておくとよい。 When the monitoring unit 11 detects an error state or the like, the site maintenance worker diagnosis unit 12B is in a current (real-time) state (for example, whether or not the site is in the site). Diagnose or confirm whether maintenance support is acceptable. The confirmation may be performed at any time. In particular, from the viewpoint of speeding up the maintenance response, it is preferable to acquire information from each base 3 in advance, check the latest situation, and hold necessary information.
 マッチング部12Cは、12Aと12Bの処理結果(マッチングのための基本的な前提条件の確認)をもとに、本特徴的な保守対応のマッチング判定処理(後述)を所定のアルゴリズム(a4で設定可能)により行う。これにより、当該顧客(U)の機器21(C)の保守対応のために、複数の拠点(K)・保守員(H)のうちのどの拠点のどの保守員を担当させるかをマッチング(決定)する。これにより、全体的な仕事の負荷分散を含めて考慮した好適な担当者が決定される。 Based on the processing results of 12A and 12B (confirmation of basic preconditions for matching), the matching unit 12C sets this characteristic maintenance correspondence matching determination process (described later) with a predetermined algorithm (a4) Possible). As a result, in order to support maintenance of the device 21 (C) of the customer (U), it is matched (decided) which maintenance staff at which of the plurality of bases (K) and maintenance staff (H) is in charge. ) As a result, a suitable person in charge including the overall work load distribution is determined.
 [管理情報]
 図2は、管理情報(DB)50(51~55)の構成例を示す。なお下記の各情報要素の管理は適宜統合・分離してもよい。なお図5には各ID(U,C,K,H等)の値の具体例を示している。
[Management Information]
FIG. 2 shows a configuration example of the management information (DB) 50 (51 to 55). The management of the following information elements may be integrated and separated as appropriate. FIG. 5 shows a specific example of the value of each ID (U, C, K, H, etc.).
 (51) 顧客情報51は、(a)顧客ID、(b)エリア/地域ID、(c)言語、(d)状態、の各情報を含む。 (51) The customer information 51 includes information on (a) customer ID, (b) area / region ID, (c) language, and (d) state.
 (a)顧客IDは、顧客(U)ないし顧客システム2を識別する情報である。例えばUx等で示す。(b)エリア/地域IDは、顧客システム2(機器21)の存在するエリア/地域を識別する情報である。例えばRx等で示す。(c)言語は、顧客(U)ないし顧客システム2の使用する言語(日本語、英語など)を識別する情報である。例えばWx等で示す。(d)状態は、顧客(U)の状態として、例えば保守対応の要求の有無などを示す。 (A) Customer ID is information for identifying the customer (U) or the customer system 2. For example, it is indicated by Ux. (B) Area / region ID is information for identifying an area / region where the customer system 2 (device 21) exists. For example, it is indicated by Rx. (C) The language is information for identifying a language (Japanese, English, etc.) used by the customer (U) or the customer system 2. For example, it is indicated by Wx. (D) The status indicates, for example, the presence or absence of a request for maintenance as the status of the customer (U).
 (52) 機器情報52は、(a)機器ID、(b)位置、(c)構成情報/属性情報、(d)状態、各情報を含む。 (52) The device information 52 includes (a) device ID, (b) position, (c) configuration information / attribute information, (d) state, and information.
 (a)機器IDは、機器21の識別情報である。例えばCx等で示す。(b)位置は、当該機器21の位置情報(例えばGPSによる)である。例えばLx等で示す。なお51のbのエリア(R)の情報と52のbの位置(L)の情報は対応しており、置き換えてもよいし、一方のみの管理としてもよい。bの位置情報は、予め設定してもよいし、監視情報(a1)により随時取得してもよい。 (A) The device ID is identification information of the device 21. For example, it is indicated by Cx. (B) The position is position information of the device 21 (for example, by GPS). For example, it is indicated by Lx. Note that the 51 b area (R) information and the 52 b position (L) information correspond to each other and may be replaced, or only one of them may be managed. The position information of b may be set in advance, or may be acquired as needed by the monitoring information (a1).
 (c)構成情報/属性情報は、機器21の構成や属性を示す情報であり、例えば種別がサーバであることを示す情報や、構成要素の部品の識別情報などを有する。(d)状態は、機器21の正常や障害・エラー等の状態を表すコードや、負荷状態を示す情報や、保守対応必要有無を示す情報などがある。 (C) Configuration information / attribute information is information indicating the configuration and attributes of the device 21 and includes, for example, information indicating that the type is a server, component component identification information, and the like. (D) The status includes a code indicating the normal state, failure / error, etc. of the device 21, information indicating the load status, information indicating whether maintenance support is necessary, and the like.
 (53) 拠点情報53は、(a)拠点ID、(b)エリア/地域、(c)位置、(d)保守員ID、(e)状態、の各情報を含む。 (53) The base information 53 includes information on (a) base ID, (b) area / region, (c) position, (d) maintenance personnel ID, and (e) status.
 (a)拠点IDは、拠点3を識別する情報である。例えばK1等で示す。(b)エリア/地域IDは、当該拠点3が存在するエリア/地域の識別情報である。R1等で示す。(c)位置は、当該拠点3が存在する位置の位置情報(GPS等による)である。前述同様にRとLは一方のみの管理でもよい。 (A) The base ID is information for identifying the base 3. For example, it is indicated by K1. (B) Area / region ID is identification information of an area / region where the base 3 exists. Indicated by R1 and the like. (C) The position is position information (by GPS or the like) of the position where the base 3 exists. As described above, only one of R and L may be managed.
 (d)保守員IDは、当該拠点3(K)に関係付けられる保守員(H)の識別情報である。例えばH1-1,H1-2等で示す。本実施の形態では、(d)保守員IDは、当該拠点3に所属(基本的に待機)する複数の保守員(H)を示す。(e)状態は、当該拠点3の状態として、当該拠点3に現在待機中の状態の保守員(H)のIDリストや、待機中の人数(m)などの情報がある。 (D) Maintenance personnel ID is identification information of the maintenance personnel (H) related to the base 3 (K). For example, it is indicated by H1-1, H1-2, etc. In the present embodiment, (d) maintenance personnel ID indicates a plurality of maintenance personnel (H) belonging to the base 3 (basically waiting). (E) The status includes information such as the ID list of maintenance personnel (H) who are currently waiting at the base 3 and the number of people (m) waiting as the status of the base 3.
 (54) 保守員情報54は、(a)保守員ID、(b)スキル、(c)言語、(d)状態、(e)担当、(f)負荷、の各情報を含む。その他、保守員(携帯端末32)の位置をGPS等で管理する形態の場合はその位置情報(L)を含む。 (54) The maintenance staff information 54 includes information on (a) maintenance staff ID, (b) skill, (c) language, (d) status, (e) charge, and (f) load. In addition, the position information (L) is included in the case where the position of the maintenance staff (mobile terminal 32) is managed by GPS or the like.
 (a)保守員IDは、保守員(H)の識別情報である。例えばH1-1等で示す。(b)スキルは、当該保守員の保守対応に係わるスキルセット(能力)を示す情報である。例えばSa等で示す。例えば保守対応可能な機器21の種別や、機器21の知識や復旧作業に関するスキルを示す。(c)言語は、当該保守員の使用する言語(日本語、英語等)を示す。例えばWa等で示す。 (A) The maintenance worker ID is identification information of the maintenance worker (H). For example, it is indicated by H1-1. (B) Skill is information indicating a skill set (ability) related to the maintenance response of the maintenance staff. For example, it is indicated by Sa. For example, the type of the equipment 21 that can be maintained, the knowledge of the equipment 21 and the skills related to the recovery work are shown. (C) The language indicates the language (Japanese, English, etc.) used by the maintenance staff. For example, it is indicated by Wa.
 (d)状態は、当該保守員の最新の状態として、当該保守員が所属する拠点(K)内に待機中か当該拠点(K)外に外出中か(最寄り拠点に居る/居ない)、等の状態を示す情報である。あるいは、当該保守員が、現在、保守対応用の時間が空いているか否か(新たな仕事を受け付け可能か否か)、仕事が休みかどうか、等の状態を示す情報である。 (D) The status is the latest status of the maintenance staff, whether the maintenance staff is waiting in the base (K) to which the maintenance staff belongs or is out of the base (K) (is at the nearest base or not) It is the information which shows the states. Alternatively, it is information indicating a state such as whether the maintenance staff currently has time for maintenance support (whether a new job can be accepted), whether the job is absent, or the like.
 なお保守員(H)と拠点(K)との関係は、基本的には特定の拠点に所属する形とするが、ある保守員は複数の拠点に寄る(待機する)こともできる。その場合、どの拠点(K)に待機しているかを含めて情報を管理すればよい。 It should be noted that the relationship between the maintenance staff (H) and the base (K) basically belongs to a specific base, but a certain maintenance staff can stop (wait) at a plurality of bases. In that case, the information may be managed including which base (K) is waiting.
 (e)担当は、当該保守員が現在担当している保守対応の仕事(55で管理される単位)に関する情報であり、保守対応ID(P1等)等で示される。 (E) The person in charge is information regarding the maintenance work (the unit managed in 55) that the maintenance staff is currently in charge of, and is indicated by a maintenance correspondence ID (P1 etc.).
 (f)負荷は、状態の一種であるが、当該保守員の保守対応の仕事の負荷の大きさを示す情報である。負荷の情報は、例えば、大/中/小といったレベル値で管理してもよいし、当該保守員が担当している保守対応の仕事(55で管理される単位)の数や量や、連続で担当している回数などで表してもよい。 (F) The load is a kind of state, but is information indicating the magnitude of the work load of the maintenance staff. For example, the load information may be managed by a level value such as large / medium / small, the number and amount of maintenance work (units managed by 55) handled by the maintenance staff, You may express by the number of times you are in charge.
 なお拠点(K)ごとの状況、及び複数の拠点(K)を含む全体的な状況は、拠点情報53、保守員情報54を参照することでわかる。 The situation for each base (K) and the overall situation including a plurality of bases (K) can be understood by referring to the base information 53 and maintenance staff information 54.
 (55) 保守対応情報55は、個々の保守対応の仕事を管理する情報であり、(a)保守対応ID、(b)顧客ID、(c)機器ID、(d)状態コード、(e)作業内容、(f)必要条件、(g)担当、(h)状態、の各情報を含む。その他、仕事の期日などの時間情報を管理してもよい。 (55) The maintenance support information 55 is information for managing individual maintenance support work, (a) maintenance support ID, (b) customer ID, (c) device ID, (d) status code, (e) Each item includes information on work contents, (f) necessary conditions, (g) charge, and (h) state. In addition, time information such as work due dates may be managed.
 (a)保守対応IDは、当該保守対応の仕事を識別する情報である。例えばP1等で示す。(b)顧客IDは、当該保守対応(P)の仕事の対象となる顧客(U)を示す識別情報である。(c)機器IDは、当該保守対応(P)の仕事の対象となる機器21(C)の識別情報である。(d)状態コードは、当該機器21(C)の障害・エラー等の状態を示すコードであり、52のdの状態と対応する。(e)作業内容は、当該保守対応(P)の作業内容を示す情報であり、例えば、dの状態コードに応じた復旧等の作業手順を示す情報であり、必須ではないが、例えば担当の保守員(H)の携帯端末32へ提供してガイド情報として用いる。 (A) The maintenance correspondence ID is information for identifying the maintenance correspondence job. For example, it is indicated by P1. (B) The customer ID is identification information indicating the customer (U) who is the target of the maintenance correspondence (P). (C) The device ID is identification information of the device 21 (C) that is a work target of the maintenance correspondence (P). (D) The status code is a code indicating a status such as a failure / error of the device 21 (C), and corresponds to the status d of 52. (E) The work content is information indicating the work content of the maintenance correspondence (P), for example, information indicating a work procedure such as recovery according to the status code of d. The information is provided to the portable terminal 32 of the maintenance staff (H) and used as guide information.
 (f)必要条件は、当該保守対応(P)に係わる必要な条件を示し、例えば、必要保守部品(b1等)、必要スキル(Sa等)、必要言語(Wa等)、等の情報がある。必要保守部品(b1等)は、当該保守対応(P)で必要な交換部品などであり、拠点3に備える保守部品33を用いる。必要スキル(Sa等)は、当該保守対応(P)で必要な保守員(H)のスキルを示す。必要言語(Wa等)は、当該保守対応(P)で当該顧客(U)とのコミュニケーションや当該機器21の操作のために必要とされる言語を示す。なお、言語(W)については、必要条件とせずに推奨条件としてもよい。また言語(W)をスキル(S)の概念の中に含めて管理してもよい。 (F) Necessary conditions indicate necessary conditions related to the maintenance correspondence (P), and include, for example, necessary maintenance parts (such as b1), necessary skills (such as Sa), and necessary languages (such as Wa). . The necessary maintenance parts (b1 and the like) are replacement parts necessary for the maintenance correspondence (P), and the maintenance parts 33 provided in the base 3 are used. The necessary skill (Sa or the like) indicates the skill of the maintenance staff (H) required for the maintenance response (P). The necessary language (Wa or the like) indicates a language required for communication with the customer (U) or operation of the device 21 in the maintenance correspondence (P). Note that the language (W) may be a recommended condition instead of a necessary condition. The language (W) may be managed by being included in the concept of the skill (S).
 (g)担当は、当該保守対応(P)の仕事を担当する拠点(K)・保守員(H)の識別情報(K1,H1-1等)などである。(h)状態は、当該保守対応(P)の仕事の状態として、未完/済み等がある。 (G) The person in charge is the identification information (K1, H1-1, etc.) of the base (K) and the maintenance person (H) who is in charge of the maintenance response (P). (H) The status includes incomplete / completed as the status of the maintenance response (P).
 [具体例]
 図5は、顧客(U)・機器(C)と複数の拠点(K)・保守員(H)との関係の一例を示す。エリアRx(位置Lx)に、対象の顧客Uxの顧客システム2・機器21(Cx)がある。機器Cxのエラー状態(001)に関する保守対応(P1)のために、必要部品がb1、必要スキルがSaであり、顧客Uxの使用言語(必要言語)がWaである。
[Concrete example]
FIG. 5 shows an example of the relationship between a customer (U) / device (C) and a plurality of bases (K) / maintenance personnel (H). In the area Rx (position Lx), there is the customer system 2 / device 21 (Cx) of the target customer Ux. For the maintenance response (P1) related to the error state (001) of the device Cx, the necessary part is b1, the necessary skill is Sa, and the usage language (necessary language) of the customer Ux is Wa.
 複数の各拠点3(K)として、例えばK1,K2,K3を有し、それぞれエリアR(位置L)がR1(L1),R2(L2),R3(L3)である。これらそれぞれの、顧客Ux・機器Cx側のエリアRx(Lx)との距離(Eとする)をE1,E2,E3とする。 As a plurality of bases 3 (K), for example, there are K1, K2, and K3, and areas R (positions L) are R1 (L1), R2 (L2), and R3 (L3), respectively. The distances (referred to as E) to the area Rx (Lx) on the customer Ux / device Cx side are defined as E1, E2, and E3.
 拠点K1は、所属する保守員として、H1-1,H1-2等を有し、例えばH1-1は待機中、H1-2は外出中であり、K1内の待機人数(m)が1である。拠点K2は、所属する保守員として、H2-1,H2-2等を有し、例えばいずれも待機中であり、K2内の待機人数(m)が2である。拠点K3は、所属する保守員として、H3-1,H3-2,H3-3等を有し、例えばいずれも待機中であり、K3内の待機人数(m)が3である。 The base K1 has H1-1, H1-2, etc. as the maintenance personnel to which it belongs. For example, the H1-1 is on standby, the H1-2 is out, and the standby number (m) in K1 is 1. is there. The base K2 has H2-1, H2-2, etc. as maintenance personnel to which it belongs, for example, all are on standby, and the number of standby persons (m) in K2 is 2. The base K3 has H3-1, H3-2, H3-3, etc. as maintenance personnel to which it belongs, for example, all of them are on standby, and the number of people waiting in K3 (m) is 3.
 [処理(1)]
 図3は、本システムにおけるサーバ(制御部)10の処理例を示す(s1等は処理ステップを示す)。
[Process (1)]
FIG. 3 shows a processing example of the server (control unit) 10 in this system (s1 and the like indicate processing steps).
 (s0) まず前提(トリガ)として、前述のように、監視部11が、監視情報a1から対象の顧客(U)側の機器21(C)の障害・エラー等の状態を判断・検知し、DB50の顧客情報51や機器情報52に当該情報を反映する。あるいは別のトリガとして、ヘルプデスクシステム4から保守対応の依頼が入る。 (S0) First, as a premise (trigger), as described above, the monitoring unit 11 determines and detects the state of failure / error of the target customer (U) side device 21 (C) from the monitoring information a1, The information is reflected in the customer information 51 and the device information 52 of the DB 50. Alternatively, a maintenance request is received from the help desk system 4 as another trigger.
 (s1) 顧客機器診断部12Aは、s0の監視部11からの情報(例:顧客ID、機器ID、エラー状態を示すコードなど)、DB50(51,52)をもとに、対象の顧客(U)・機器(C)側の状態と、当該状態に応じた必要な保守対応(P)の作業内容、必要条件(必要保守部品、必要スキル、必要言語など)を診断または確認し、DB50(保守対応情報55等)に反映する処理を行う。例えば55のa~fの値を格納する。 (S1) The customer device diagnosis unit 12A uses the information from the monitoring unit 11 of s0 (eg, customer ID, device ID, error status code, etc.) and DB50 (51, 52) as the target customer ( U)-Diagnose or confirm the state of the device (C), the required maintenance (P) work contents and necessary conditions (required maintenance parts, required skills, required language, etc.) according to the state, and check the DB50 ( The maintenance information 55 etc. is reflected. For example, 55 values a to f are stored.
 (s2) 拠点保守員診断部12Bは、s0の監視部11からの情報、DB50(53,54)をもとに、対象(候補)となる複数の各拠点(K)・保守員(H)側の現在(最新)の状態(拠点3内に待機中か否か、保守対応を受け付け可能か否か等)を診断または確認し、DB50(53,54)に反映する処理を行う。 (S2) The site maintenance staff diagnosis unit 12B, based on the information from the monitoring unit 11 of s0 and the DB 50 (53, 54), each of the target (candidate) sites (K) and maintenance personnel (H) The current (latest) state (whether waiting in the base 3 or whether maintenance support can be accepted, etc.) is diagnosed or confirmed, and processing to reflect in the DB 50 (53, 54) is performed.
 (s3) マッチング部12Cは、s1,s2の結果情報(DB50)をもとに、顧客(U)・機器(C)側と拠点(K)・保守員(H)側とにおける保守対応(P)のマッチング判定処理(図4)を行う。 (S3) Based on the result information (DB50) of s1 and s2, the matching unit 12C performs maintenance on the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side (P ) Matching determination process (FIG. 4).
 (s4) 診断部12は、s3の結果の候補から、当該保守対応(P)を実際に担当させる拠点(K)・保守員(H)を所定人数(例えば1人)選択して決定し、DB50(55等)に反映する処理を行う。例えば55のgの値を格納する。s4で所定人数を選択する際には、例えばランダム、ラウンドロビン等、適当な手法を用いることができる。なおs3の結果で既に候補が1人などに絞られている場合はs4は不要とできる。なお対象の仕事(P)に応じて担当者を1人ではなく複数人にすることもできる。 (S4) The diagnosis unit 12 selects and determines a predetermined number (for example, one person) of bases (K) and maintenance staff (H) who actually take charge of the maintenance response (P) from the candidate results of s3, Processing to reflect in DB50 (55 etc.) is performed. For example, 55 g values are stored. When selecting a predetermined number of people in s4, an appropriate method such as random or round robin can be used. Note that if the result of s3 has already been narrowed down to one candidate, s4 may be unnecessary. It should be noted that the number of persons in charge can be set to a plurality of persons instead of one according to the target job (P).
 (s5) 指示部13は、s4の結果(DB50)に従い、該当の拠点(K)・保守員(H)(対応する設備31や携帯端末32)へ保守対応(P)の作業内容等を含む指示(a2)を送信する処理を行う。これにより、その後、当該指示(a2)に従って担当者により保守対応(a3)が実施される。 (S5) The instruction unit 13 includes the work contents of maintenance correspondence (P) to the corresponding base (K) / maintenance staff (H) (corresponding equipment 31 and portable terminal 32) according to the result of s4 (DB50). Processing to transmit the instruction (a2) is performed. Thereby, maintenance correspondence (a3) is implemented by the person in charge according to the instruction (a2).
 [処理(2)]
 図4は、診断部12のマッチング部12C(図3のs3)の処理例を示す。マッチング部12Cは、図3の12A,12Bの処理結果情報(DB50)をもとに、顧客(U)・機器(C)側と拠点(K)・保守員(H)側とにおける保守対応のマッチング判定処理を所定のアルゴリズム(設定a4に基づく)により行う。この判定は、大別して第1の条件判定(s3-1)、第2の条件判定(s3-2)、第3の条件判定(s3-3)がある。これにより、対象の顧客(U)の機器21(C)の保守対応(P)のために、複数の拠点(K)・保守員(H)のうちのどの拠点(K)のどの保守員(H)を担当させるか(候補)を決定し、ここで決定した担当の情報をDB50(54のe、55のg等)に反映する。
[Process (2)]
FIG. 4 shows a processing example of the matching unit 12C (s3 in FIG. 3) of the diagnosis unit 12. Based on the processing result information (DB50) of 12A and 12B in FIG. 3, the matching unit 12C performs maintenance support on the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side. Matching determination processing is performed by a predetermined algorithm (based on setting a4). This determination is roughly divided into a first condition determination (s3-1), a second condition determination (s3-2), and a third condition determination (s3-3). Thereby, for maintenance support (P) of the device 21 (C) of the target customer (U), which maintenance staff (K) of which base (K) among the plurality of bases (K) and maintenance staff (H) ( H) is determined whether or not to be in charge (candidate), and the determined information is reflected in the DB 50 (e in 54, g in 55, etc.).
 (s3-1) 第1条件判定: まず基本条件(必要条件)として、当該保守対応の仕事が現在受付可能な状態であり、対象の機器(C)のエラー等の状態に対処可能なスキル(S)を持ち、対象の顧客(U)と同じ言語(W)を使用する、等の観点から第1候補を抽出する。 (S3-1) First condition determination: First, as a basic condition (necessary condition), the maintenance-ready work is currently in a state where it can be accepted, and a skill that can deal with an error or the like of the target device (C) ( S), and the first candidate is extracted from the viewpoint of using the same language (W) as the target customer (U).
 (s401) s401では、マッチング部12Cは、第1条件として、対象の保守対応の仕事(P)にあたって、必要なスキル(S)、必要な言語(W)を持ち、休みではなく拠点(K)に待機中などの状態であり、当該時点で当該仕事(P)用の時間的な空きがあり受付可能な状態である第1条件を満たす保守員(H)及び対応拠点(K)をDB50から検索により抽出し、これを第1候補とする。 (S401) In s401, the matching unit 12C has the necessary skill (S) and the necessary language (W) for the target maintenance work (P) as the first condition, and has a base (K) instead of a holiday. From the DB 50, the maintenance personnel (H) and the corresponding bases (K) satisfying the first condition, which are in a waiting state, etc., are in a state where there is a time vacancy for the job (P) at that time and can be accepted from the DB 50. This is extracted by searching, and this is set as the first candidate.
 (s3-2) 第2条件判定: 次にs3-2では、距離(言い換えると時間)の観点から判定し、第1候補から絞り込み、第2候補とする。対象の顧客(U)の機器(C)と、保守員(H)の拠点(K)との距離(E)がなるべく近いという第2条件を満たすものを第2候補とする。即ち、保守員(H)が現場へ移動する際の時間が短くなるように選択する。 (S3-2) Second condition determination: Next, in s3-2, determination is made from the viewpoint of distance (in other words, time), and the second candidate is narrowed down from the first candidate. Those satisfying the second condition that the distance (E) between the device (C) of the target customer (U) and the base (K) of the maintenance staff (H) are as close as possible are set as second candidates. That is, the time required for the maintenance person (H) to move to the site is selected to be short.
 (s402) s402では、s401の結果の第1候補の保守員(H)が、同一の拠点(K)に関係付けられる保守員であるかどうかを判断する。同一拠点である場合(s402-Y)、s403の判定は不要であるため、当該保守員を第2候補として、s3-3へ遷移する。 (S402) In s402, it is determined whether the first candidate maintenance staff (H) as a result of s401 is a maintenance staff related to the same base (K). If it is the same site (s402-Y), the determination of s403 is unnecessary, so that the maintenance staff is set as the second candidate and the process proceeds to s3-3.
 (s403) s403では、第1候補の複数の保守員(H)に関係付けられる複数の拠点(K)のエリアR(または位置L)、及び、対象の顧客(U)の機器21(C)のエリアR(または位置L)を確認する(DB50内の51~54のエリアRまたは位置Lの情報を参照すればよい)。ここではエリアRで判定する方式とする。 (S403) In s403, the area R (or position L) of the plurality of bases (K) related to the plurality of maintenance personnel (H) of the first candidate, and the device 21 (C) of the target customer (U) Area R (or position L) is confirmed (information on area R or position L of 51 to 54 in DB 50 may be referred to). Here, the determination is made in area R.
 そして、それぞれの候補について、顧客(U)・機器(C)側と拠点(K)・保守員(H)側の両者のエリアR間の距離Eを判定する。ここでは距離Eを所定長(例えば5km毎)で区分した範囲Fで判定する方式とする。そして、当該距離E(範囲F)が一番近い拠点(K)及び対応する保守員(H)を抽出(選択)し、これを第2候補とする。 Then, for each candidate, the distance E between the areas R of the customer (U) / equipment (C) side and the base (K) / maintenance staff (H) side is determined. Here, the distance E is determined by a range F divided by a predetermined length (for example, every 5 km). Then, the base (K) with the closest distance E (range F) and the corresponding maintenance staff (H) are extracted (selected) and set as the second candidate.
 (s3-3) 第3条件判定: 次にs3-3では、センターシステム1で管理している複数の拠点(K)・複数の保守員(H)を含む全体の範囲で、保守対応の仕事に関する効率性・負荷分散の観点から判定し、第2候補から絞り込み、第3候補とする。各拠点(K)内に待機人数を確保するとともに、特定の保守員(H)に仕事が集中しないようにする。 (S3-3) Third Condition Judgment: Next, in s3-3, work for maintenance in the whole range including multiple bases (K) and multiple maintenance personnel (H) managed by the center system 1 From the viewpoint of efficiency and load distribution, the second candidate is narrowed down to be the third candidate. The number of waiting persons is secured in each base (K) and work is not concentrated on specific maintenance personnel (H).
 (s404) s404では、上記s3-2の結果の第2候補の拠点(K)・保守員(H)における仕事(P)の負荷状態が概略同様であるかどうかを判断する。概略同様の負荷状態である場合(s404-Y)、s405以降の判定は不要であるため、当該保守員を第3候補として、s3-3の終わりへ遷移する。 (S404) In s404, it is determined whether the work (P) load state at the second candidate site (K) / maintenance staff (H) as a result of s3-2 is substantially the same. When the load state is substantially the same (s404-Y), the determination after s405 is unnecessary, and the maintenance personnel is set as the third candidate, and the process proceeds to the end of s3-3.
 (s405) s405では、上記第2候補の保守員(H)における1人(任意選択)の保守員(Hiとする)ごとに、当該保守員Hiの対応拠点(Kiとする)の待機人数(m)を確認する。即ち当該保守員Hiを保守対応(P)に担当させると仮定したとき、当該拠点Kiの現在の待機人数(m)から当該保守員Hi分を除いた人数(m-1)をみる。この仮定の待機人数が、所定人数(例えば1)以上確保されるかどうかを判断する。これは、効率性・負荷分散の観点から、当該拠点Kiで保守対応の仕事を受けるために所定人数以上の待機人数を確保しておくことが望ましいからである。上記確保できない場合(s405-N)、s406で当該保守員Hiを候補から除外する。 (S405) In s405, for each one (optional) maintenance staff (referred to as Hi) in the second candidate maintenance staff (H), the number of standby persons (referred to as Ki) corresponding to the maintenance staff Hi (referred to as Ki) Check m). That is, assuming that the maintenance staff Hi is in charge of maintenance support (P), the number of persons (m−1) obtained by subtracting the maintenance staff Hi from the current waiting number (m) of the base Ki is seen. It is determined whether or not the assumed number of standby persons is secured by a predetermined number (for example, 1) or more. This is because, from the viewpoint of efficiency and load distribution, it is desirable to secure a standby number of persons equal to or greater than a predetermined number in order to receive maintenance work at the base Ki. If the above cannot be secured (s405-N), the maintenance staff Hi is excluded from candidates in s406.
 (s407) s407では、上記第2候補の保守員(Hi)ごとに、保守対応の仕事の負荷が大きすぎないかどうかを確認する。即ち、当該保守員Hiが今回の保守対応の仕事(P)を担当すると仮定したとき、当該保守員Hiに仕事が集中しすぎていたり、当該保守員Hiが何回も連続して仕事を受けていたりといったように、負荷が大きい状態を望ましくない状態として判定する。例えばDB50内の保守員の負荷の情報(54のf)を参照し、当該負荷のレベル等を閾値と比較して判定する。上記負荷が高い場合(s407-Y)、s408で当該保守員Hiを候補から除外する。上記のように一部の保守員の負荷が大きい状態は、全体的な効率性・負荷分散の観点から望ましくないため、ここで除外される。 (S407) In s407, it is confirmed for each maintenance candidate (Hi) of the second candidate whether the work load for maintenance is too large. That is, when it is assumed that the maintenance worker Hi is in charge of this maintenance work (P), the maintenance worker Hi is too concentrated, or the maintenance worker Hi receives the work continuously several times. For example, a state where the load is large is determined as an undesirable state. For example, referring to the load information (54 f) of the maintenance staff in the DB 50, the load level and the like are compared with a threshold value for determination. When the load is high (s407-Y), the maintenance staff Hi is excluded from candidates in s408. A state in which the load of some maintenance personnel is large as described above is not desirable from the viewpoint of overall efficiency and load distribution, and is excluded here.
 (s409) s409では、上記第2候補の拠点(K)・保守員(H)(待機人数が十分確保され負荷も高すぎない状態)における保守対応の仕事の負荷分散を判定する。例えば、複数の中から負荷が一番小さい拠点(K)・保守員(H)を選択し、これを第3候補とする。なお担当者はs4で最終的に決定するため、候補は複数人が選択されてもよい。 (S409) In s409, the load distribution of the maintenance work at the second candidate site (K) / maintenance staff (H) (a state where the number of waiting persons is sufficiently secured and the load is not too high) is determined. For example, a base (K) / maintenance worker (H) having the smallest load is selected from a plurality of candidates, and this is set as the third candidate. Since the person in charge is finally determined in s4, a plurality of candidates may be selected.
 例えば、拠点K単位の負荷分散の判定として、同じ範囲F(同程度の距離E)に含まれる複数の拠点Kがある場合、それらのうち一番負荷が小さい拠点K(対応する保守員H)を選択する。 For example, when there is a plurality of bases K included in the same range F (same distance E) as the determination of load distribution in units of bases K, the base K with the smallest load (corresponding maintenance staff H) among them. Select.
 例えば、保守員H単位の負荷分散の判定として、同じ範囲Fや拠点Kの中の複数の保守員Hがいる場合、それらのうち一番負荷が小さい保守員Hを選択する。 For example, when there are a plurality of maintenance personnel H in the same range F or base K as a determination of load distribution in units of maintenance personnel H, the maintenance personnel H having the smallest load is selected.
 なお第3判定(s3-3)で、該当の候補が無くなる場合(s410-Y)は、例えば第2判定(s3-2)に戻り、距離の観点で次の候補(次に距離が近いもの)を選択してやりなおす(同様の処理の繰り返し)。 If there is no corresponding candidate in the third determination (s3-3) (s410-Y), for example, the process returns to the second determination (s3-2), and the next candidate (those with the next closest distance) is considered in terms of distance. ) And start over (repeat the same process).
 上述したマッチング判定のアルゴリズム(図4)は、先に距離(第2条件)を優先して考慮し次に負荷分散(第3条件)を考慮して担当(候補)を判定する形態の場合である。これに限らず、優先の順序を逆にし、先に負荷分散(第3条件)を優先して考慮し次に距離(第2条件)を考慮して担当(候補)を判定する形態も可能である。更に、距離(時間)や負荷分散の観点(条件、効果)のいずれを優先して担当(候補)を決定するかを、設定(a4)や指示入力や状態検知などによって可変に制御してもよい。例えば対象の機器21の状態が深刻であることを検知した場合や、顧客(U)がヘルプデスク(4)に対して即時対応を要求している場合などには、距離優先で決定し、そうではない場合は負荷分散優先で決定する、等が挙げられる。 The above-described matching determination algorithm (FIG. 4) is a case in which the charge (candidate) is determined in consideration of the distance (second condition) first and then the load distribution (third condition). is there. Not limited to this, it is also possible to reverse the priority order and determine the charge (candidate) in consideration of the load distribution (third condition) first and then the distance (second condition). is there. Furthermore, whether to assign priority (candidate) with priority given to distance (time) or load distribution viewpoints (conditions and effects) can be variably controlled by setting (a4), instruction input, state detection, or the like. Good. For example, when it is detected that the state of the target device 21 is serious, or when the customer (U) requests immediate help from the help desk (4), the distance is determined first. If this is not the case, it may be decided to prioritize load balancing.
 [判定例]
 図6は、診断部12によるマッチング判定例を示す。図6のID値は図5の例と対応している。図6(a)は第1の例、図6(b)は第2の例を示す。星印はマッチング判定で選択される候補を示す。
[Judgment example]
FIG. 6 shows an example of matching determination by the diagnosis unit 12. The ID value in FIG. 6 corresponds to the example in FIG. FIG. 6A shows a first example, and FIG. 6B shows a second example. An asterisk indicates a candidate selected in the matching determination.
 各拠点K1,K2,K3は、前述の距離E1,E2,E3の順に顧客Ux(Cx)のエリアRx(Lx)から遠くなる場合である。顧客U側と拠点K側との距離Eの判定方式として、エリアR間の距離を判定する方式とするが、位置L間の距離を判定する方式としてもよい。また更に、距離Eの判定方式として、距離Eを細かく算出する方式としてもよいが、本実施の形態では、距離Eを所定の範囲(Fとする)に区分し、この距離区分範囲Fを単位として判定する方式を用いる。 Each base K1, K2, K3 is a case where it becomes far from the area Rx (Lx) of the customer Ux (Cx) in the order of the above-mentioned distances E1, E2, E3. As a method for determining the distance E between the customer U side and the base K side, a method for determining the distance between the areas R is used, but a method for determining the distance between the positions L may be used. Furthermore, as a determination method of the distance E, a method of calculating the distance E in detail may be used. In the present embodiment, the distance E is divided into a predetermined range (F), and the distance division range F is a unit. A method for determining as follows is used.
 図6(a)で、距離Eの判定に関し、拠点K1(E1),K2(E2)は範囲F1に含まれ、拠点K3(E3)は範囲F2に含まれ、Cxに対してF1(K1,K2)の方がF2(K3)よりも近い。図5と同様に各拠点K内に保守員H(H1-1~H3-3)がいる状態とする。また、これらの保守員は、いずれも、機器Cxの保守対応(P1)のためのスキルSa及び言語Waを持つとする。また、各保守員Hの負荷状態として、K1内のH1-1、K2内のH2-2、K3内のH3-3は負荷大であり、K2内のH2-1、K3内のH3-1,H3-2は負荷小であるとする。 In FIG. 6A, regarding the determination of the distance E, the bases K1 (E1) and K2 (E2) are included in the range F1, the base K3 (E3) is included in the range F2, and F1 (K1, K2) is closer than F2 (K3). As in FIG. 5, it is assumed that maintenance personnel H (H1-1 to H3-3) are present in each base K. Further, it is assumed that all of these maintenance personnel have a skill Sa and a language Wa for maintenance correspondence (P1) of the device Cx. Also, as the load state of each maintenance person H, H1-1 in K1, H2-2 in K2, and H3-3 in K3 are heavy, and H2-1 in K2, H3-1 in K3 , H3-2 is assumed to have a small load.
 前述(図4)の制御処理により、図6(a)の第1の例では、第1候補は、必要スキルSa等持つ、図示する6人(H1-1~H3-3)となる。第2候補は、距離E(範囲F)が近いF1に該当する3人(H1-1,H2-1,H2-2)となる。そして、第3候補は、F1の中で負荷状態が一番小さい条件に該当するH2-1(1人)となる。 According to the control process described above (FIG. 4), in the first example of FIG. 6A, the first candidates are the six persons (H1-1 to H3-3) shown in the figure who have the necessary skills Sa and the like. The second candidates are three persons (H1-1, H2-1, H2-2) corresponding to F1 having a short distance E (range F). The third candidate is H2-1 (one person) corresponding to the condition with the smallest load state in F1.
 なお、範囲F1の中で、負荷ではなく距離Eが近い方を優先する場合(第2判定までの場合)、K1内のH1-1が該当するが、H1-1を担当者としてしまうと、K1内の待機人数が0人になってしまうため、NG(除外)とする。そこで、K2内のH2-1は負荷が小さいため、OK(第3候補)となる。 If priority is given to the distance E rather than the load in the range F1 (up to the second determination), H1-1 in K1 is applicable, but if H1-1 is in charge, Since the number of waiting in K1 is 0, it is determined as NG (exclusion). Therefore, H2-1 in K2 is OK (third candidate) because the load is small.
 図6(b)では、図6(a)と概略同様の状態であるが、K2内のH2-1,H2-2ともに負荷が大きい状態とする。前述(図4)の制御処理により、同様に、第1候補は図示する6人(H1-1~H3-3)となる。第2候補は、最初、距離E(範囲F)が近いF1に該当する3人(H1-1,H2-1,H2-2)となる。しかし、これらの負荷状態はいずれも大きいため、NGとして、第2候補を決めなおし、次に近い範囲F2に該当する3人(H3-1~H3-3)となる。そして、第3候補は、範囲F2の中で負荷が一番小さい条件に該当するH3-1,H3-2(2人)となる。例えばK2内のH2-1は近いが負荷が大きいためNGとなり、少し遠くても負荷が小さいH3-1等がOK(第3候補)となる。このように第2の例では、距離よりも負荷分散を優先するアルゴリズムとした場合である。 In FIG. 6B, the state is almost the same as that in FIG. 6A, but both the loads H2-1 and H2-2 in K2 are in a large load state. Similarly, by the control process described above (FIG. 4), the first candidates are six persons (H1-1 to H3-3) shown in the figure. The second candidates are initially three persons (H1-1, H2-1, H2-2) corresponding to F1 having a short distance E (range F). However, since both of these load states are large, the second candidate is determined again as NG, and three persons (H3-1 to H3-3) corresponding to the next closest range F2 are obtained. The third candidates are H3-1 and H3-2 (two people) that meet the condition with the smallest load in the range F2. For example, H2-1 in K2 is close, but the load is large, so it is NG, and even if it is a little far away, H3-1 etc. with a small load is OK (third candidate). As described above, in the second example, an algorithm that prioritizes load distribution over distance is used.
 [効果等]
 以上説明したように、本実施の形態のシステムによれば、複数の各拠点(K)・保守員(H)におけるスキル(S)・言語(W)、顧客(U)・機器(C)との距離(E)、及び動的な負荷分散などを考慮して保守対応の仕事(P)のマッチング判定を行う機能により、保守対応の仕事の適切性、迅速性、及び複数の拠点(K)・複数の保守員(H)間における全体的な効率性・負荷分散を実現できる。
[Effects]
As described above, according to the system of the present embodiment, skills (S) / languages (W), customers (U) / equipment (C) in a plurality of bases (K) / maintenance personnel (H) The ability to determine the matching of maintenance work (P) taking into account the distance (E) and dynamic load distribution, etc., the appropriateness and speed of maintenance work, and multiple locations (K) -Overall efficiency and load distribution among multiple maintenance personnel (H) can be realized.
 以上、本発明者によってなされた発明を実施の形態に基づき具体的に説明したが、本発明は前記実施の形態に限定されるものではなく、その要旨を逸脱しない範囲で種々変更可能であることは言うまでもない。実施の形態の変形例として以下が挙げられる。 As mentioned above, the invention made by the present inventor has been specifically described based on the embodiment. However, the present invention is not limited to the embodiment, and various modifications can be made without departing from the scope of the invention. Needless to say. The following is given as a modification of the embodiment.
 (1) 前述の処理例(図4)では、第2条件として距離を判定し、第3条件として負荷分散を判定したが、設定(a4)等に基づき、第1条件と第2条件のみで候補/担当を決定する形としてもよいし、第1条件と第3条件のみで候補/担当を決定する形としてもよい。 (1) In the above processing example (FIG. 4), the distance is determined as the second condition and the load distribution is determined as the third condition. However, based on the setting (a4) and the like, only the first condition and the second condition are used. The candidate / charge may be determined, or the candidate / charge may be determined only by the first condition and the third condition.
 (2) 保守対応(P)の仕事の対象の顧客(U)・機器(C)が前(過去)と同じである場合に、当該仕事の適切性・効率性を考慮して、前(過去)と同じ担当者となるように決定してもよい。この場合、担当者となる保守員の負荷が大きくなる可能性があるが、例えば以降の他の仕事を他の保守員に担当させるように負荷分散することにより、当該保守員の負荷を抑制させる。例えばセンターシステム1内(DB50)に過去の担当の情報を履歴として保持しておき、マッチングの際に当該履歴情報を参照して判定することにより、上記のような処理を実現する。 (2) If the customer (U) / equipment (C) that is the subject of the maintenance correspondence (P) job is the same as the previous (past), the previous (past) ) May be determined to be the same person in charge. In this case, there is a possibility that the load on the maintenance staff who becomes the person in charge may increase, but for example, by distributing the load so that other maintenance staff is in charge of the subsequent work, the load on the maintenance staff is suppressed. . For example, the past processing information is stored as a history in the center system 1 (DB 50), and the above processing is realized by referring to the history information at the time of matching.
 (3) マッチング判定で一旦担当者(保守員H、拠点K)を決定した後、当該担当者の都合が悪くなり当該保守対応が実施できない場合などには、当該保守員等を除いて再度のマッチング判定を行ったり、あるいは順序付きで保持しておいた別の候補から選択して決定してもよい。 (3) Once the person in charge (maintenance personnel H, base K) is determined in the matching judgment, if the person in charge becomes inconvenient and the maintenance response cannot be implemented, repeat the procedure except for the maintenance personnel. It may be determined by performing a matching determination or selecting from other candidates held in order.
 (4) 言語(W)等に関して、必須条件として判定するのではなく、例えば推奨条件として判定してもよい。例えば、スキルS等を必須条件や優先条件とし、言語Wを推奨条件(なるべく顧客Uの言語Wと同じになるように考慮する)として候補を決定する。候補の保守員Hが顧客Uの言語Wと同じにならない場合は、例えば顧客Uの言語Wと同じである別の者を同行させるように複数人の担当者を決定する。設定(a4)により、距離優先や負荷分散優先だけでなく、スキル優先や言語優先などを同様に設定可能とする。 (4) The language (W) or the like may be determined as a recommended condition instead of being determined as an essential condition. For example, the candidate is determined with the skill S or the like as an indispensable condition or priority condition and the language W as a recommended condition (considering as much as possible the same as the language W of the customer U). If the candidate maintenance staff H is not the same as the language W of the customer U, for example, a plurality of persons in charge are determined so that another person who is the same as the language W of the customer U is accompanied. By setting (a4), not only distance priority and load distribution priority but also skill priority and language priority can be set similarly.
 (5) 制御的にはより単純化した形態であるが、個別の担当者となる保守員Hを決定するのではなく、より大まかな単位として、担当させる1つの拠点Kを決定する形態も可能である。担当拠点Kの決定後は、その担当拠点K(複数の保守員H)の中で任意に対応させる。 (5) Although it is a simplified form in terms of control, it is possible to decide a single base K to be assigned as a rough unit, rather than determining the maintenance person H who will be the individual person in charge. It is. After the assigned base K is determined, it is arbitrarily handled in the assigned base K (a plurality of maintenance personnel H).
 (6) 前記第2条件の距離の判定に関して、距離情報と時間情報とを関係付けてDB50に管理してもよい。この場合、前記第2条件の距離の判定は、直接的に時間判定になる。即ち、拠点K・保守員H側から顧客U・機器C側への移動時間が一番短いものを候補とするような形となる。 (6) Regarding the determination of the distance of the second condition, the distance information and the time information may be related to each other and managed in the DB 50. In this case, the determination of the distance under the second condition is a time determination directly. In other words, the shortest travel time from the base K / maintenance staff H side to the customer U / equipment C side is the candidate.
 本発明は、ヘルプデスクシステム、統合監視システム、等に利用可能である。 The present invention can be used for a help desk system, an integrated monitoring system, and the like.

Claims (8)

  1.  顧客の機器を対象とした保守対応の業務に係わる情報処理を行う保守対応システムであって、
     複数の拠点の複数の保守員の中から前記顧客の機器の保守対応を行う担当者を決定する機能を持つ情報処理装置を有し、
     前記情報処理装置は、診断部と、管理情報を格納するDBとを有し、
     前記情報処理装置は、外部から前記保守対応の要求の情報を入力し、
     前記診断部は、
     前記管理情報または入力情報をもとに、対象の顧客の機器の状態、必要な保守対応の内容及び条件を診断または確認する第1の処理と、
     前記管理情報または入力情報をもとに、複数の拠点と複数の保守員の最新の状態を診断または確認する第2の処理と、
     前記第1、第2の処理をもとに、対象の顧客の機器の保守対応のために、前記複数の拠点の複数の保守員の中から、担当者またはその候補となる拠点の保守員をマッチング判定する第3の処理と、を行い、
     前記第3の処理において、
     第1条件として、前記必要な保守対応の条件として、前記対象の顧客の機器の状態に応じた必要なスキルを持つ保守員を第1候補として選択し、
     第2条件として、前記第1候補から、対象の顧客の機器との距離がなるべく近い拠点の保守員を第2候補として選択し、
     第3条件として、前記第2候補から、複数の拠点または複数の保守員における保守対応の仕事の負荷分散が実現されるように、負荷がなるべく小さい拠点の保守員を第3候補として選択すること、を特徴とする保守対応システム。
    A maintenance system that performs information processing related to maintenance work for customer equipment,
    An information processing apparatus having a function of determining a person in charge of maintenance of the customer's equipment from a plurality of maintenance staff at a plurality of bases;
    The information processing apparatus includes a diagnosis unit and a DB that stores management information.
    The information processing apparatus inputs the maintenance request information from the outside,
    The diagnostic unit
    A first process for diagnosing or confirming the state of the target customer's device, the contents and conditions of necessary maintenance, based on the management information or input information;
    A second process for diagnosing or confirming the latest state of a plurality of bases and a plurality of maintenance personnel based on the management information or the input information;
    Based on the first and second processes, in order to support maintenance of the target customer's equipment, a person in charge or a maintenance staff at a candidate site is selected from among a plurality of maintenance staff at the plurality of bases. And a third process for determining matching,
    In the third process,
    As a first condition, as a condition for the necessary maintenance, a maintenance person having a necessary skill according to the state of the target customer's equipment is selected as a first candidate,
    As a second condition, from the first candidate, a maintenance staff at a base as close as possible to the target customer's device is selected as a second candidate,
    As a third condition, from among the second candidates, a maintenance staff at a base with as little load as possible is selected as a third candidate so that the load distribution of maintenance work at a plurality of bases or a plurality of maintenance staff is realized. A maintenance support system characterized by
  2.  請求項1記載の保守対応システムにおいて、
     前記診断部の第3の処理において、前記第1条件として、前記必要な保守対応の条件として、前記顧客の言語に応じた必要な言語を持つ保守員を第1候補として選択すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    In the third process of the diagnosis unit, as the first condition, a maintenance person having a necessary language corresponding to the language of the customer is selected as a first candidate as the necessary maintenance response condition. Maintenance compatible system.
  3.  請求項1記載の保守対応システムにおいて、
     前記診断部の第3の処理において、前記第2条件の判定の際には、前記対象の顧客の機器が存在するエリアまたは位置の情報と、前記保守員の拠点が存在するエリアまたは位置の情報とを確認し、両者間の距離またはその距離区分範囲を判定すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    In the third process of the diagnostic unit, when determining the second condition, information on the area or position where the target customer's device exists and information on the area or position where the maintenance staff base exists And determining the distance between the two or the distance classification range.
  4.  請求項1記載の保守対応システムにおいて、
     前記診断部の第3の処理において、前記第3条件の判定の際には、拠点の待機人数が所定人数以上確保されないものを候補から除外すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    In the third process of the diagnosis unit, a maintenance support system is characterized in that, when the third condition is determined, a candidate whose number of standby persons at a base is not ensured more than a predetermined number is excluded from candidates.
  5.  請求項1記載の保守対応システムにおいて、
     前記診断部の第3の処理において、前記第3条件の判定の際には、前記保守員の負荷状態を判定し、負荷が大きすぎるものを候補から除外すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    In the third process of the diagnosis unit, when determining the third condition, the maintenance support system is configured to determine a load state of the maintenance staff and to exclude a too heavy load from candidates. .
  6.  請求項1記載の保守対応システムにおいて、
     設定または入力に基づいて、前記診断部の第3の処理において、前記第2条件の距離と、前記第3条件の負荷分散とで、前記第2条件の距離を優先して前記担当者またはその候補を決定すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    Based on the setting or input, in the third process of the diagnosis unit, the person in charge or the person in charge of the second condition is prioritized by the distance of the second condition and the load distribution of the third condition. A maintenance support system characterized by determining candidates.
  7.  請求項1記載の保守対応システムにおいて、
     設定または入力に基づいて、前記診断部の第3の処理において、前記第2条件の距離と、前記第3条件の負荷分散とで、前記第3条件の負荷分散を優先して前記担当者またはその候補を決定すること、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    Based on the setting or input, in the third process of the diagnostic unit, the person in charge or the person in charge of the load distribution of the third condition is prioritized by the distance of the second condition and the load distribution of the third condition. A maintenance support system characterized by determining the candidate.
  8.  請求項1記載の保守対応システムにおいて、
     前記情報処理装置は、監視部と、指示部とを有し、
     前記監視部は、前記顧客の機器の状態及び位置を監視し、保守対応が必要な状態を検知する処理を行い、
     前記指示部は、前記診断部の処理結果をもとに、前記担当者となる保守員の拠点の設備または当該保守員の携帯端末へ保守対応の指示情報を送信する処理、及び当該設備または携帯端末から当該拠点の保守員の状態を取得する処理を行うこと、を特徴とする保守対応システム。
    The maintenance support system according to claim 1,
    The information processing apparatus includes a monitoring unit and an instruction unit.
    The monitoring unit monitors the state and position of the customer's equipment and performs a process of detecting a state requiring maintenance,
    The instruction unit, based on the processing result of the diagnostic unit, a process of transmitting instruction information for maintenance to a facility of a maintenance staff base serving as the person in charge or a portable terminal of the maintenance staff, and the facility or mobile A maintenance-compatible system, characterized in that processing for acquiring the status of maintenance personnel at the base from a terminal is performed.
PCT/JP2012/055936 2011-09-26 2012-03-08 Maintenance support system WO2013046750A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011-209132 2011-09-26
JP2011209132A JP5917062B2 (en) 2011-09-26 2011-09-26 Maintenance support system

Publications (1)

Publication Number Publication Date
WO2013046750A1 true WO2013046750A1 (en) 2013-04-04

Family

ID=47994820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/055936 WO2013046750A1 (en) 2011-09-26 2012-03-08 Maintenance support system

Country Status (2)

Country Link
JP (1) JP5917062B2 (en)
WO (1) WO2013046750A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018088599A (en) * 2016-11-28 2018-06-07 富士通株式会社 Contact party output system, contact party output method and contact party output program
CN112055069A (en) * 2020-08-31 2020-12-08 深圳供电局有限公司 Electric power automation equipment testing method and system

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015031997A (en) * 2013-07-31 2015-02-16 株式会社日立システムズ Maintenance personnel assignment system
JP5932871B2 (en) * 2014-03-28 2016-06-08 株式会社富士通エフサス Management system and management method
JP6421600B2 (en) * 2015-01-05 2018-11-14 富士通株式会社 Fault monitoring device, fault monitoring program, fault monitoring method
JP6893726B2 (en) * 2017-01-13 2021-06-23 悠記 青木 Global maintenance service support system
JP6708348B2 (en) * 2017-11-02 2020-06-10 Necフィールディング株式会社 Management device, management system, management method, and program
EP3726440A4 (en) * 2017-12-15 2021-05-19 SEI Optifrontier Co., Ltd. Fusion splicing apparatus management system and fusion splicing apparatus management method
JP6590023B1 (en) * 2018-04-26 2019-10-16 日本電気株式会社 Information processing system, information processing method, and program
JP6787619B1 (en) * 2018-12-27 2020-11-18 株式会社ノグチHd Information processing device
CN110223411B (en) * 2019-05-29 2021-09-24 中国人民武装警察部队警官学院 Inspection system and method for public water dispenser
JP2022032175A (en) * 2020-08-11 2022-02-25 Necフィールディング株式会社 Construction engineer management device, construction engineer management method, and construction engineer management program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004192153A (en) * 2002-12-09 2004-07-08 Toshiba Corp Maintenance introduction method, system and program
JP2008009496A (en) * 2006-06-27 2008-01-17 Hitachi Ltd Maintenance service operation system and maintenance service operation method
JP2008257433A (en) * 2007-04-04 2008-10-23 Matsushita Electric Ind Co Ltd Reception/transmission device, mobile terminal, program and recording medium
JP2009099135A (en) * 2007-09-28 2009-05-07 Fujitsu Ltd Support management method, support management system and information processing device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5137166B2 (en) * 2004-01-19 2013-02-06 アリックス株式会社 Human resource / practical development method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004192153A (en) * 2002-12-09 2004-07-08 Toshiba Corp Maintenance introduction method, system and program
JP2008009496A (en) * 2006-06-27 2008-01-17 Hitachi Ltd Maintenance service operation system and maintenance service operation method
JP2008257433A (en) * 2007-04-04 2008-10-23 Matsushita Electric Ind Co Ltd Reception/transmission device, mobile terminal, program and recording medium
JP2009099135A (en) * 2007-09-28 2009-05-07 Fujitsu Ltd Support management method, support management system and information processing device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2018088599A (en) * 2016-11-28 2018-06-07 富士通株式会社 Contact party output system, contact party output method and contact party output program
CN112055069A (en) * 2020-08-31 2020-12-08 深圳供电局有限公司 Electric power automation equipment testing method and system
CN112055069B (en) * 2020-08-31 2023-12-05 深圳供电局有限公司 Electric power automation equipment testing method and system

Also Published As

Publication number Publication date
JP2013069239A (en) 2013-04-18
JP5917062B2 (en) 2016-05-11

Similar Documents

Publication Publication Date Title
JP5917062B2 (en) Maintenance support system
JP4819837B2 (en) Improved method and system for prioritized network printer inspection or maintenance
US20150120388A1 (en) Work and quality management system, device and method
US20070185754A1 (en) Task responsibility system
JP6095140B2 (en) Remote monitoring system, remote monitoring method, and program
CN102202085A (en) Method and device for processing operation/maintenance work orders based on mobile terminal
JP4539973B2 (en) Maintenance management method and maintenance management program
KR101620605B1 (en) Apparatus and method for safety diagnosis report
JP2003067877A (en) System, method and program for maintenance and monitoring
JP2008027022A (en) Fault data collection system
JP5229696B2 (en) Information processing system, information processing apparatus, control method thereof, control program thereof, and communication environment monitoring and recovery method
JP2005272067A (en) Maintenance track record managing device of elevator
WO2016199251A1 (en) Equipment maintenance/management system, equipment maintenance device, and program
KR101179359B1 (en) Work system and Method for managing mobile communication system
JP2007080010A (en) On-site communication/support system
JPH11259339A (en) Computer fault maintenance system and fault dealing computer
KR20170006552A (en) System for managing integrated failure and method thereof
JP2010218324A (en) Task allocation device, task allocation method and task allocation program
JP2003256027A (en) Field apparatus maintenance system
WO2017163757A1 (en) Information processing device and information processing method
KR102533361B1 (en) A method of operating messenger linked to HR information
JP2019004350A (en) Alarm notification system and alarm notification method
JP6562144B1 (en) Schedule management system, schedule management server, and schedule management method
JP2003216757A (en) Maintenance support system
JP2024016687A (en) Device management system and device management method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12835392

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12835392

Country of ref document: EP

Kind code of ref document: A1