Maintenance readiness status management system, maintenance readiness status management program, and maintenance readiness status management method

Abstract

A maintenance preparation status management system, a maintenance preparation status management program, and a maintenance preparation status management method are provided to effectively support the provision of information regarding maintenance services. [Solution] In a maintenance preparation status management device, a registration unit registers contract information regarding maintenance services in a database, linking it to users of the maintenance service and target products that are the subject of the maintenance service, and registers preparation information in the database indicating the preparation status of configurations used in maintaining the products. An identification unit identifies target products for maintenance services contracted by the users based on the contract information in response to inquiry requests that specify a user, identifies configurations included in the products that correspond to the target products by referencing configuration information registered for each product, and identifies the preparation status corresponding to each identified configuration based on the preparation information. A display unit displays the results of identification by the identification unit, and displays a preparation status screen that lists the preparation status for each configuration for the target products corresponding to the users.

Description

[Technical Field]

[0001] The present invention relates to a maintenance preparation status management system, a maintenance preparation status management program, and a maintenance preparation status management method. [Background technology]

[0002] Generally, product manufacturers provide repair and other maintenance services to purchasers of new products for a certain period of time. However, once the period has expired, the manufacturer's maintenance service ends and users are no longer able to receive support. There are also products, such as second-hand products, that are not covered by manufacturer's maintenance services.

[0003] Therefore, a service called third-party maintenance is offered for maintenance work. Third-party maintenance refers to maintenance provided by a third party other than the manufacturer. In third-party maintenance, it is necessary to identify and prepare the parts and materials required for maintenance.

[0004] Patent Document 1 describes a technique for checking the inventory of broken maintenance parts in relation to maintenance after the production of a device has been discontinued.

[0005] Furthermore, Patent Document 2 describes a technology for identifying components that make up a device based on a device code and searching for inventory of the components. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-107934 [Patent Document 2] Japanese Patent Application Laid-Open No. 2002-288370 Summary of the Invention [Problem to be solved by the invention]

[0007] However, with the technology described in Patent Document 1, it is necessary to specifically identify the part before searching, and if the required part itself is unknown, it is not possible to check the stock.

[0008] Furthermore, with the technology described in Patent Document 2, it was not possible to search for parts inventory unless a device code was specified.

[0009] In view of the above circumstances, an object of the present invention is to provide a novel technique for effectively supporting the provision of information related to maintenance services. [Means for solving the problem]

[0010] [1] A maintenance preparation status management system comprising a registration unit, an identification unit, and a display unit, wherein the registration unit registers contract information regarding maintenance services in a database, linking it to a user of the maintenance service and a target product that is the subject of the maintenance service used by the user, and registers preparation information in the database indicating the preparation status of a configuration used in maintaining the product; the identification unit, in response to an inquiry request specifying the user, identifies the target product of the maintenance service contracted by the user based on the contract information, identifies a configuration corresponding to the target product by referring to configuration information registered for each product of the configurations included in the product, and identifies the preparation status corresponding to each identified configuration based on the preparation information; the display unit displays the identification results by the identification unit, and displays a preparation status screen that lists the preparation status for each configuration of the target product corresponding to the user.

[0011] This configuration allows the system to identify and display a list of the preparation status of the configurations used for the maintenance of the target product according to the user's contract. This allows the user to see at a glance the products covered by the contract, the configurations required for their maintenance, and their preparation status. This allows the user to check the individual preparation status of the target product even if they do not know the configuration of the product.

[0012] [2] The maintenance preparation status management system described in [1], wherein the configuration information is information indicating the components that make up the product, the preparation information includes a preparation number indicating the number of each component prepared for maintenance, and the identification unit identifies the preparation status for each configuration based on the preparation number.

[0013] With this configuration, it is possible to present a more specific preparation status according to the number of components that are actually prepared.

[0014] [3] The maintenance preparation status management system described in [2], wherein the preparation status screen displays the prepared quantity of the component for each configuration for the target product corresponding to the user.

[0015] [4] The preparation status screen displays, for the target product corresponding to the user, a standard number indicating the number of parts that should be prepared in advance for each configuration, in association with the prepared number of the parts. [3] The maintenance preparation status management system described in [3].

[0016] With this configuration, the user can see at a glance whether a sufficient number of each component is available, and can receive maintenance services with greater peace of mind.

[0017] [5] A maintenance preparation status management system described in any of [2] to [4], wherein the identification unit compares a standard number indicating the number of the components that should be prepared in advance with the prepared number to identify the preparation status.

[0018] This configuration makes it possible to present the preparation status more clearly and accurately.

[0019] [6] A maintenance readiness status management system according to [4] or [5], wherein the contract information includes a contract period, and the standard quantity is determined based on the remaining period determined from the contract period.

[0020] This configuration allows for more appropriate information to be provided that reflects the contract period. Specifically, for example, it is possible to reflect the number of items expected to be consumed in the remaining period, and it is possible to prevent the presentation of an amount that is actually larger than necessary.

[0021] [7] The maintenance readiness status management system described in [6], wherein the standard number is determined based on the remaining life as well as the failure rate of each component.

[0022] By adopting such a configuration, it becomes possible to provide more appropriate information for each component.

[0023] [8] A maintenance preparation status management program that causes a computer to function as a registration unit, an identification unit, and a display unit, wherein the registration unit registers contract information regarding maintenance services in a database, linking it to a user of the maintenance service and a target product that is the subject of the maintenance service used by the user, and registers preparation information in the database indicating the preparation status of the configuration used in maintaining the product; the identification unit, in response to an inquiry request specifying the user, identifies the target product of the maintenance service contracted by the user based on the contract information, identifies the configuration corresponding to the target product by referring to configuration information registered for each product of the configuration included in the product, and identifies the preparation status corresponding to each identified configuration based on the preparation information; the display unit displays the identification results by the identification unit, and displays a preparation status screen that lists the preparation status for each configuration of the target product corresponding to the user.

[0024] [9] A maintenance preparation status management method, in which a computer registers contract information regarding a maintenance service in a database, linking it to a user of the maintenance service and a target product that is the subject of the maintenance service used by the user, registers preparation information in the database indicating the preparation status of a configuration used in maintaining the product, identifies the target product of the maintenance service contracted by the user based on the contract information in response to an inquiry request specifying the user, identifies a configuration corresponding to the target product by referring to configuration information in which the configurations included in the product are registered for each product, identifies the preparation status corresponding to each identified configuration based on the preparation information, displays the identification results, and displays a preparation status screen that lists the preparation status for each configuration for the target product corresponding to the user. [Effects of the Invention]

[0025] According to the present invention, it is possible to provide a novel technique for effectively supporting the provision of information relating to maintenance services. [Brief explanation of the drawings]

[0026] [Figure 1] FIG. 1 is a diagram illustrating a configuration of an embodiment of the present invention. [Figure 2] Hardware configuration diagram. [Figure 3] FIG. 4 is a diagram showing an example of registration data according to the embodiment. [Figure 4] 10 is a flowchart showing a procedure for displaying a preparation status screen in the present embodiment. [Figure 5] 10 shows an example of a screen display in this embodiment. [Figure 6] 10 shows an example of a screen display in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0027] <1. Overview> The present invention relates to a technology for displaying the readiness status of a configuration used for maintenance. Hereinafter, the term "maintenance" refers to support for the continued use of a product, including responses to defects and breakdowns.

[0028] In particular, in this embodiment, the following description is given assuming a technology used in providing third-party maintenance services. In this embodiment, an example is given of a system that displays the preparation status for maintenance work on a target product (in particular, the preparation status of configurations required for repair or replacement) to a user who uses a third-party maintenance service.

[0029] The present invention will now be described in more detail with reference to the accompanying drawings, in which preferred embodiments are shown, but which may be embodied in many different forms and are not limited to the embodiments set forth herein.

[0030] For example, in this embodiment, the configuration, operation, etc. of the maintenance preparation status management system will be described, but similar effects can be achieved by a device having similar functions, a method executed by the device, a computer program that causes a computer device to execute the method, etc. The program may be provided as a non-transitory computer-readable recording medium, or may be provided so as to be downloadable from an external server.

[0031] In the following embodiments, the term "unit" may include, for example, a combination of hardware resources implemented by a broadly defined circuit and software information processing that can be specifically realized by these hardware resources. In this embodiment, "information" is represented by, for example, the physical value of a signal value representing voltage or current, the high or low value of a signal value as a binary bit set consisting of 0 or 1, or quantum superposition (so-called quantum bits), and communication and calculation can be performed on a broadly defined circuit.

[0032] A circuit in the broad sense is a circuit realized by appropriately combining a circuit, a processor, a memory, etc. For example, it is a circuit including any of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc.

[0033] <2.Definition> First, definitions of key terms used in this embodiment will be explained. In the following description, the term "product" refers to any product that includes multiple components. In the present invention, a product is an object that is the subject of maintenance service. In this embodiment, the product is particularly an electrical product. For example, electrical products such as storage devices, server devices, and network devices are included in the products of this embodiment.

[0034] In this invention, a "configuration" refers to a unit of a set of things that make up a product to be maintained, and is used in maintenance services. For example, to configure the power supply of a product to be maintained, "two specific redundant power supply units" is an example of a "configuration" in this invention.

[0035] In this invention, a component is an item required for providing maintenance services for the above configuration. For example, for a configuration with "two specific redundant power supply units," the "specific redundant power supply units" correspond to the component of this invention. Also, a component may be used in common for multiple types of configurations.

[0036] In the present invention, the readiness status refers to the status of preparation for use in maintenance for each configuration. For example, the preparation status of the present invention includes the inventory status of components required for maintenance of each configuration and the status of preparation (inspection, cleaning, deployment, etc.) of each component for use in maintenance services. More specifically, for example, the number of each component in each state can be used as the preparation status.

[0037] <3. System Configuration> Next, the configuration of the maintenance preparation status management system in this embodiment will be described. Fig. 1 is a block diagram showing the configuration of the maintenance preparation status management system in this embodiment. As shown in Fig. 1, the maintenance preparation status management system includes a maintenance preparation status management device 1, an administrator terminal 2, and a user terminal 3. The maintenance preparation status management device 1, the administrator terminal 2, and the user terminal 3 are configured to be able to communicate via a network NW.

[0038] There may be multiple administrator terminals 2 and multiple user terminals 3. Maintenance service providers and users can log in to their own accounts using any terminal device, thereby identifying individual users and sending and receiving information to and from the maintenance preparation status management device 1. In this embodiment, the network NW is an IP (Internet Protocol) network, but there are no restrictions on the type of communication protocol, type of network, etc.

[0039] One or more information processing devices 10 (computer devices), such as a general-purpose server or a personal computer, can be used as the maintenance preparation status management device 1. Furthermore, terminal devices 9 (computer devices), such as a personal computer, smartphone, or tablet terminal, can be used as the administrator terminal 2 and the user terminal 3. In this embodiment, the maintenance preparation status management device 1 is an information processing device 10 in which a computer program (maintenance preparation status management program) that executes a maintenance preparation status management method is installed.

[0040] Fig. 2(a) is a hardware configuration diagram of the information processing device 10. As shown in Fig. 2, the information processing device 10 has a control unit 101, a storage unit 102, and a communication unit 103, which are used to perform the functions of each unit and each process.

[0041] The control unit 101 has a processor such as a CPU that can execute an instruction set, and executes an OS and programs. The storage unit 102 includes a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or SSD capable of recording an OS, a maintenance preparation status management program, a DBMS, and the like. The communication unit 103 has an interface for physically connecting to a network, and controls communication with the network NW to input and output information.

[0042] Fig. 2(b) is a hardware configuration diagram of the terminal device 9. As shown in Fig. 2, the terminal device 9 has a control unit 901, a storage unit 902, a communication unit 903, an input unit 904, and an output unit 905, which are used to perform the functions of each unit and each process.

[0043] The control unit 901 has a processor such as a CPU that can execute an instruction set, and executes an OS, application programs, and the like. The storage unit 902 includes a volatile memory such as a RAM capable of storing an instruction set, and a non-volatile recording medium such as an HDD or SSD capable of recording an OS, any application program, and the like. The communication unit 903 has an interface for physically connecting to a network, and controls communication with the network NW to input and output information. The input unit 904 includes an operation input device capable of input processing, such as a touch panel or keyboard, and an audio input device capable of audio input, such as a microphone. The output unit 905 includes a display device capable of display processing, such as a display, and an audio output device, such as a speaker.

[0044] <4. Functional configuration> 1, the maintenance preparation status management device 1 includes a registration unit 11, an identification unit 12, a display unit 13, and a database DB. This is a specific implementation of software-based information processing using hardware. Note that these components do not need to be implemented by a single computer, and may be implemented by multiple computers working together. For example, the database DB may be provided on an external server.

[0045] The registration unit 11 registers contract information regarding maintenance services in the database DB, linking the contract information with the user of the maintenance service and the target product that is the subject of the maintenance service. In this embodiment, the contract contents are determined between the maintenance service provider and the user, and the user on the provider side inputs the contract information according to the contents via the administrator terminal 2. The registration unit 11 registers the contract information in the database DB based on the information received from the administrator terminal 2.

[0046] The registration unit 11 also registers preparation information indicating the preparation status of a configuration used in product maintenance in the database DB. In this embodiment, a maintenance service provider inputs information related to the preparation status via the administrator terminal 2. The registration unit 11 registers the preparation information in the database DB based on the information received from the administrator terminal 2. The registered information in the database DB will be described later.

[0047] In response to a query request specifying a user, the identification unit 12 refers to the database DB and identifies the target products for the maintenance service contracted by the user based on the contract information.The identification unit 12 then refers to the configuration information described below to identify the configurations corresponding to the identified target products and the preparation status corresponding to each configuration.The query request may be sent from the user terminal 3 or from the administrator terminal 2.

[0048] Here, "preparation status" broadly refers to the status of preparation for maintenance using each configuration. For example, the preparation status includes the inventory status of parts corresponding to each configuration and the status of preparation for providing those parts to target users. More specifically, examples of preparation status include the number of parts prepared for maintenance, the standard number indicating the number of parts that should be prepared for maintenance, and the comparison results between them.

[0049] The number of preparations can be, for example, simply the number of parts reserved for the user, the number of reserved parts that have been prepared for inspection, cleaning, etc., or the number of parts stored at the location nearest to the user. The standard number may be arbitrarily determined for each component and registered in advance in the database DB, or may be calculated for each contract based on the contract information. In this embodiment, the standard number is calculated individually, and the calculation method will be described later.

[0050] The display unit 13 displays the identification result by the identification unit 12 and displays a preparation status screen. Specifically, the display processing results are sent to the terminal that sent the inquiry request (the administrator terminal 2 or the user terminal 3), and are displayed on the display device of the terminal that received them to the operator of the terminal that sent the inquiry request (the person in charge on the service provider side or the user). The preparation status screen is a screen that displays a list of the preparation status for each configuration of the target product in the contract information linked to the user specified in the inquiry request. A specific example will be given later.

[0051] <5. Registration Information> 3 is a diagram showing an example of various information stored in the database DB of this embodiment. The database DB of this embodiment stores contract information related to maintenance services, product master, component master, configuration information, and component individual information. An example of this embodiment will be specifically described below.

[0052] The contract information includes information indicating the content of the maintenance service, the user, and the product. Specifically, the contract information includes the contract number, the user ID, the product ID, the contract period, the type, and the location. The contract information is associated with the user of the maintenance service and the target product by the user ID and the product ID. Here, the target product is an individual product that is the target of maintenance. The product ID identifies the product information, and the product information is linked to the product master.

[0053] The contract number may be a unique value for each contract information, or in the case where similar contracts are made collectively for a plurality of products, the same contract number may be assigned to those contracts.

[0054] The contract period is the period during which the maintenance service is provided as specified in the contract. The type indicates the type of the maintenance service provided. For example, if a maintenance service provider prepares a specific plan for each service content, the type is information that identifies the plan. The location is the location where the maintenance service is provided, for example, the location where the target product is used.

[0055] The product master shows information for each type of product that may be subject to maintenance. The product master includes the product ID, product name, and product model number. In addition, product information for each individual product is linked to the product master and registered separately.

[0056] The configuration information is information that indicates the configuration included in each product, linked to the individual product. The configuration information includes the configuration name, the individual product ID (information that uniquely identifies the individual product information), the component ID, and the number of components (the number of components). In other words, the configuration information indicates the correspondence between the individual product, the configuration, and the components and their numbers required for that configuration.

[0057] The component master is information about the components that make up a product. The component master includes the component ID, component name, and component model number.

[0058] Component individual information is information that indicates information about individual components managed by the maintenance service provider. Component individual information includes a component individual ID, a component ID, a product ID, a status, and a location. Component individual information is linked to the component master by the component ID, and is also linked to the product master by the product ID.

[0059] Here, even for products of the same model, different product IDs may be issued and multiple product masters may be registered. Then, by linking and registering product individual information to these product masters, these product individual groups can be distinguished. Similarly, multiple component masters may be issued with different component IDs for the same component, and configuration information may be registered for each combination of these. This allows products (or product groups) of the same model to be distinguished and the corresponding parts to be managed, making it possible to comply with contracts such as preparing exclusive parts for specific customers.

[0060] Condition is information that indicates the condition of a part. Particularly in third-party maintenance, there are often cases where the product manufacturer has stopped providing the part and it is difficult to obtain the part. In such cases, the parts that can be obtained are not necessarily new, and they may be obtained from discarded products. Therefore, situations can arise where the condition of each part varies. Possible conditions include, for example, "before inspection," "inspected and repaired," etc.

[0061] The location refers to the place where the parts are stored. When the scale of maintenance service provision is large, there may be multiple warehouses for storing parts and maintenance service bases. In this case, in order to provide maintenance services to users, the necessary parts must be available at the responsible base. Therefore, in this embodiment, the location of the parts is stored as part of the part individual information in order to check whether the parts are stored at the nearest (responsible) location as a preparation status.

[0062] Furthermore, although not shown, the component individual information may be configured to include a contract ID so that individual components can be allocated to each user. When a specific contract ID is registered, it indicates that the component indicated by the component individual information is allocated for maintenance under the applicable contract.

[0063] These configurations are merely examples, and can be changed as desired, such as adding or deleting registered items in the various information. For example, the configuration information may be included in the product master. Also, for example, in this embodiment, the preparation information is obtained by aggregating the component individual information, but the preparation information may be stored separately from the component individual information.

[0064] <6. Calculation of standard number> In this embodiment, when determining the readiness status, a "standard number" is used to indicate the number of components that should be prepared for maintenance. The standard number may be determined arbitrarily, and for example, a specific standard number may be set for each configuration. As an example, this embodiment will explain an example in which the standard number is calculated for each contract (for each combination of user and target product) taking into account contract information.

[0065] In this embodiment, the standard quantity is calculated based on the failure rate of each component and the contract period included in the contract information. More specifically, the number of components to be consumed during the remaining period specified by the contract period, i.e., the period from the present time to the end of the contract period, is calculated taking into account the failure rate, and the standard quantity is determined based on the result.

[0066] The standard number determined in this manner can be used as the "readiness status" of the present invention. For example, a combination of the standard number and the prepared number, or a comparison result between the standard number and the prepared number, can be used as the preparation status. When the comparison result is used as the preparation status, the difference between the prepared number and the standard number (prepared number - standard number), a multi-level evaluation depending on the magnitude of the difference, or the like may be displayed for each configuration on the preparation status screen.

[0067] In this embodiment, the readiness status of a component is determined based on the individual information of the same (or compatible) component. More specifically, the number of components is tallied according to their status (readiness status) and deployment status, and the readiness status is determined based on the results. For example, the total number of parts in stock, the number in stock for each state, the number stored at the location nearest to the user's address (place where the target product is used) (number already deployed), etc. may be used as the preparation status.

[0068] <7. Preparation status display procedure> Next, the procedure for identifying the target preparation status and displaying the preparation status screen will be described. Fig. 4 is a flowchart showing the procedure for displaying the preparation status screen in this embodiment. Here, the description will be made assuming that a user of a maintenance service checks whether sufficient preparations for maintenance (particularly preparation of parts) have been made for the service they use.

[0069] In step S1, first, the user terminal 3 transmits a request to query the preparation status to the maintenance preparation status management device 1 in response to an input from the user. Specifically, for example, the user accesses a maintenance service site using a browser application and logs in. This identifies the user. Then, by inputting a request to display the preparation status from My Page or the like, the user terminal 3 transmits an inquiry request including the user ID to the maintenance preparation status management device 1. In the maintenance preparation status management device 1, the identification unit 12 identifies the user by the user ID.

[0070] The same process may be performed by the administrator terminal 2 instead of the user terminal 3. In this case, instead of the user logging in, the user who uses the administrator terminal 2 designates the user.

[0071] Next, in step S2, the identification unit 12 refers to the contract information linked to the user identified in step S1, and further identifies the target product linked to that contract information. Then, the information on the identified target product is passed to the display unit 13, which processes it for display and transmits the processing result to the user terminal 3. A list screen of the target products is displayed on the user terminal.

[0072] The user terminal 3 accepts the selection of a target product from the user on the displayed target product list screen. Note that step S3 is not essential, and the processes from step S4 onward may be executed for all target products related to the user's contract information.

[0073] In step S4, the identification unit 12 identifies the configuration of the selected target product by referring to the configuration information in the database DB. Specifically, a product master is identified from the product ID in the product individual information of the target product, and the identification unit 12 refers to multiple pieces of configuration information linked to the product master. In this embodiment, the configuration name, components, and the number of components (number of components) are identified for each of the multiple components included in the target product.

[0074] Furthermore, in step S5, the identification unit 12 identifies the prepared quantity by referring to the component individual information. In this embodiment, the following four types of information are identified as examples of the prepared quantity: the total inventory quantity, the number of components out of the total inventory that are ready for deployment (inspection, etc., completed) (hereinafter referred to as the secured quantity), the number of components that have been deployed to the deployment destination according to the location in the contract information (hereinafter referred to as the deployed quantity), and the sum of the secured quantity and the deployed quantity.

[0075] Then, in step S6, the display unit 13 displays the preparation status based on the preparation number specified in step S5 and the standard number, and transmits the processing result to the user terminal 3. Then, the user terminal 3 displays a preparation status screen on the display device based on the received processing result.

[0076] <8. Display example> An example of a screen display in this embodiment will be described below. 5 is an example of the target product list screen displayed in step S2 above. Hereinafter, this will be referred to as the product list screen W1. The product list screen W1 comprises a search section W11 and a list display section W12. In the search section W11, search criteria for the target product can be entered, and when the "Search" button is selected, a list of target products that match the entered search criteria is displayed in the list display section W12.

[0077] The list display unit W12 displays, for each target product, a list of the product ID ("Device ID" in FIG. 5), manufacturer, product name, serial number, maintenance start date, maintenance end date, system name, and whether or not configuration information is available. The product ID is an ID unique to this system, and the serial number is a code assigned to the product by the manufacturer or the like. Only one of these may be displayed. The manufacturer and product name are identified by the product master linked to the individual product information, and the maintenance start date and maintenance end date are the start and end dates of the contract period in the contract information.

[0078] When a target product is selected from the list displayed in this way, a preparation status disclosure screen for the selected product is displayed. Fig. 6 shows an example of the display of the preparation status disclosure screen in this embodiment.

[0079] The preparation status disclosure screen W2 includes a contract information display section W21, a product information individual display section W22, and a preparation status display section W23. The preparation status display section W23 displays a list of product configurations, and displays the configuration name, the number of components corresponding to the configuration (number of components), the component name, and the preparation status for each configuration.

[0080] In this embodiment, the preparation status displayed for each configuration includes the standard number, the secured number, the deployed number, the total number of secured numbers and deployed numbers, and the total inventory number. The total inventory number indicates the total inventory held by the maintenance service provider, regardless of whether it has been secured for the user. In addition to these, this embodiment also displays a "status" that indicates the preparation status in multiple levels, such as O, X, and △. The "status" is determined based on the difference or ratio between the secured number, deployed number, or their total number and the standard number. Note that it is also possible to display only the "status" without displaying specific numerical values.

[0081] The number of parts that the maintenance service provider has procured for maintenance, more specifically, the number of parts that are in preparation, including parts that have not yet been obtained from stock but will be procured in the future, may also be displayed.

[0082] In addition to these, the predicted number of failures for each configuration may also be displayed. The predicted number of failures is the predicted number of failures during the remaining period, determined from the failure rate linked to the component master and registered in advance, and the remaining period of the contract. This allows the user to get a more specific idea of ​​the number of components required.

[0083] As described above, the maintenance preparation status management system of this embodiment can specifically present the maintenance preparation status according to the status of the parts to be used for maintenance. This makes it possible to provide information that provides reassurance to users about whether they will be able to receive sufficient maintenance service in the event of a breakdown, which was previously unclear to users. [Explanation of symbols]

[0084] 1: Maintenance preparation status management device 11: Registration section 12: Specific part 13: Display section 2: Administrator terminal 3: User terminal 9: Terminal device 10: Information processing device 101: Control unit 102: Storage section 103: Communications Department 901: Control unit 902: Storage section 903: Communications Department 904: Input section 905: Output section NW: Network W1: Product list screen W11: Search section W12: List display section W2: Preparation status disclosure screen W21: Contract information display section W22: Product information display section W23: Preparation status display section

Claims

1. A maintenance preparation status management system including a registration unit, an identification unit, and a display unit, The registration unit The contract information regarding the maintenance service is registered in a database in association with the user of the maintenance service and the target product that is the target of the maintenance service used by the user; Registering preparation information including a preparation number indicating the number of each component prepared for product maintenance in a database; The member constitutes the product, The identification unit Accepting a user's designation and an input of an inquiry request from a user, and identifying the target product for the maintenance service contracted by the user based on the contract information linked to the user; Identifying a configuration corresponding to the target product by referring to configuration information in which information indicating the components constituting the product is registered for each product; Identifying a readiness status corresponding to each identified configuration by tallying the number of readiness; The display unit processes and displays the results of the identification by the identification unit, and displays a preparation status screen that lists the preparation status for each configuration of the target product corresponding to the user.

2. The maintenance preparation status management system according to claim 1 , wherein the preparation status screen displays the prepared quantity of the component for each configuration of the target product corresponding to the user.

3. 3. The maintenance preparation status management system according to claim 2, wherein the preparation status screen displays a standard number indicating the number of components that should be prepared in advance for each configuration of the target product corresponding to the user, in association with the prepared number of the components.

4. The maintenance preparation status management system according to claim 1 , wherein the specifying unit specifies the preparation status by comparing a standard number indicating the number of the components that should be prepared in advance with the prepared number.

5. The contract information includes a contract period, The maintenance readiness management system according to claim 3 or 4, wherein the standard number is determined based on a remaining period specified from the contract period.

6. The maintenance readiness management system according to claim 5 , wherein the standard number is determined based on a failure rate of each of the components in addition to the remaining period.

7. A maintenance preparation status management program that causes a computer to function as a registration unit, an identification unit, and a display unit, The registration unit The contract information regarding the maintenance service is registered in a database in association with the user of the maintenance service and the target product that is the target of the maintenance service used by the user; Registering preparation information including a preparation number indicating the number of each component prepared for product maintenance in a database; The member constitutes the product, The identification unit Accepting a user's designation and an input of an inquiry request from a user, and identifying the target product for the maintenance service contracted by the user based on the contract information linked to the user; Identifying a configuration corresponding to the target product by referring to configuration information in which information indicating the components constituting the product is registered for each product; Identifying a readiness status corresponding to each identified configuration by tallying the number of readiness; A maintenance preparation status management program in which the display unit processes and displays the results of the identification by the identification unit, and displays a preparation status screen that lists the preparation status for each configuration of the target product corresponding to the user.

8. A maintenance readiness management method, comprising: The contract information regarding the maintenance service is registered in a database in association with the user of the maintenance service and the target product that is the target of the maintenance service used by the user; Registering preparation information including a preparation number indicating the number of each component prepared for product maintenance in a database; The member constitutes the product, Accepting a user's designation and an input of an inquiry request from a user, and identifying the target product for the maintenance service contracted by the user based on the contract information linked to the user; Identifying a configuration corresponding to the target product by referring to configuration information in which information indicating the components constituting the product is registered for each product; Identifying a readiness status corresponding to each identified configuration by tallying the number of readiness; A maintenance preparation status management method that displays the identification results and displays a preparation status screen that displays a list of the preparation status for each configuration of the target product corresponding to the user.

Images