Information providing system and information providing method
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- CANON KK
- Filing Date
- 2023-06-29
- Publication Date
- 2026-06-26
AI Technical Summary
Existing device management systems require more efficient responses when multiple devices need treatment to improve business efficiency.
An information providing system with search and display means to identify devices requiring treatment and their related devices, displaying urgency information based on analysis of device data.
Improves business efficiency by enabling efficient dispatch of engineers to treat multiple devices and their related devices based on urgency.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a technology for providing information in device management. Regarding. [Background technology]
[0002] Conventionally, systems have been constructed that collect information from image forming devices such as printers (hereinafter referred to as devices) and manage the status of the devices. In such systems, a management server receives device information and is able to manage the occurrence of errors in the device, the degree of wear of parts, or signs of part failure. Based on this management information, the system provides the administrator with information necessary for dealing with errors, such as part replacement or cleaning information required to deal with device errors, information on parts that are nearing the end of their life, or information on parts that are likely to cause failures. This allows the administrator's engineers to efficiently take appropriate measures for the devices.
[0003] For example, Patent Document 1 discloses a technology that performs an analysis process to determine whether or not repairs or other measures are necessary not only for the device for which a user has made a repair request, but also for devices that belong to the same group. This technology makes it possible to collectively take measures for multiple devices that belong to the same group, allowing engineers to be dispatched for repairs efficiently. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2009-206788 A Summary of the Invention [Problem to be solved by the invention]
[0005] In the management system described above, when a process needs to be performed on a plurality of devices, a more efficient response is required, and there is room for improvement of the system in order to increase business efficiency.
[0006] The present disclosure provides an information processing technique that can improve business efficiency. [Means for solving the problem]
[0007] An information providing system according to one embodiment of the present disclosure is characterized by having a first search means for searching for devices, a first display means for displaying information of the searched devices, a second search means for searching for at least devices that are related to the searched device and require treatment as associated devices based on the information of the searched devices, and a second display means for displaying information indicating an order of urgency of the searched associated devices that require treatment. Effect of the Invention
[0008] According to the present disclosure, business efficiency can be improved. [Brief description of the drawings]
[0009] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a system including a device management system according to a first embodiment. [Diagram 2] 2 is a block diagram showing an example of a hardware configuration of an information processing device constituting the management system; [Diagram 3] FIG. 2 is a block diagram showing an example of a functional configuration of a management system and a device. [Figure 4] 11 is a flowchart showing a process of the device management system. [Diagram 5] FIG. 13 illustrates an example of a device search screen. [Figure 6] FIG. 13 illustrates an example of a device alert list screen. [Figure 7] FIG. 5 is a diagram showing an example of a related device display screen 511. [Figure 8]FIG. 11 is a diagram showing an example of an associated device display screen according to the second embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a group list screen that displays all groups to which one device belongs. [Figure 10] FIG. 13 is a diagram showing an example of a related device display screen for all groups. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In the drawings, elements having the same configuration or function are given the same reference numerals, and repeated description thereof will be omitted. The configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the configurations shown in the drawings.
[0011] [First embodiment] <System configuration> 1 is a diagram showing an example of the overall configuration of a system. This system includes a device management system (hereinafter referred to as a management system) 101 according to an embodiment, and a plurality of devices 102 that can be connected to this management system 101 via a network 104. The management system 101 is an example of an information providing system that provides various types of information required by an administrator who manages the devices 102 and a customer 103 who uses the devices 102.
[0012] The management system 101 may be built on cloud computing technology. The management system 101 centrally manages a plurality of devices 102. Specifically, the management system 101 manages various settings and operating statuses of each device 102 by collecting information (described later) about the device 102 that each device 102 has. The management system 101 is configured, for example, by multiple servers on a cloud, but may be realized by a single server. Alternatively, the management system 101 may be configured by a server instead of a cloud.
[0013] The device 102 is an image forming apparatus such as a printer, a scanner, or an MFP (Multi-Function Peripheral), and has functions such as printing, scanning, faxing, and copying. The device 102 also has a function of communicating with the management system 101 via the network 104, and collects various types of data based on a data collection request received from the management system 101, and transmits the collected data to the management system 101. The various types of data are the device-related information described above.
[0014] The information about the device includes device information and device data. The device information includes information unique to each device (such as a device ID, which will be described later) and various setting information set in the device 102. The device data includes usage record information (such as counter and log information), status information, error information, sensor data, and the like, and is data necessary to realize each service (described later) that constitutes the management system 101.
[0015] The management system 101 uses the above device data to manage the occurrence of errors and failures, the wear level of consumable parts, and the status of signs of failure of parts based on sensor data, and provides these to the administrator.
[0016] A customer 103 is a user who uses multiple devices 102. In the example shown in FIG. 1, there are multiple customers 103. In most cases, multiple devices 102 may be used for each customer 103. There are no restrictions on the configuration or number of devices for each customer 103, or the number of customers 103.
[0017] The network 104 is a communication network that may be realized by, for example, a LAN, a WAN, a telephone line, or a dedicated digital line, or by a combination of at least two of these. The Internet is typically used as a WAN. An intranet is typically used as a LAN.
[0018] <Management system hardware configuration> FIG. 2 is a block diagram showing an example of a hardware configuration of an information processing device that constitutes the management system 101 in the first embodiment.
[0019] The management system 101 may be realized by an information processing device provided as a cloud computing service. Examples of cloud computing include serverless computing and virtual machines. In cloud computing, each hardware resource shown in FIG. 2 is used in multiple instances. Note that the management system 101 may be realized by one physical machine, or may be realized by multiple physical machines connected via a network or physical lines. In the example shown in FIG. 2, the management system 101 is configured as one physical machine.
[0020] The information processing device constituting the management system 101 includes a CPU 201 , a memory 202 , a HDD (hard disk drive) 203 , an input control unit 205 , a display control unit 207 , a network control unit 209 , an input device 206 , and a display device 208 .
[0021] The CPU 201 comprehensively controls each hardware element connected to a system bus 204 . The memory 202 is a main memory for the CPU 201 and functions as a work area, etc. The memory 202 may also store programs executed by the CPU 201. The HDD 203 is a large-capacity storage device that stores the programs executed by the CPU 201 and also stores various other data.
[0022] The input control unit 205 controls input from an input device 206 such as a mouse or a keyboard. Depending on the role of the information processing device, the input control unit 205 and the input device 206 may not be required.
[0023] The display control unit 207 controls the display on a display device 208 such as a liquid crystal display. Depending on the role of the information processing device, the display control unit 207 and the display device 208 may be omitted.
[0024] A network control unit 209 transmits and receives data bidirectionally to and from other nodes via the network 104 .
[0025] 2, instead of the CPU 201, a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array) may be used. Alternatively, an ASIC (Application Specific Integrated Circuit) may be used. Also, instead of the HDD 203, other storage devices such as a flash memory, an optical recording device, or a magneto-optical recording device may be used.
[0026] <Functional configuration> FIG. 3 is a block diagram showing an example of the functional configuration of the management system 101 and the device 102. As shown in FIG. The management system 101 includes a device data receiving unit 303 , a device management service 321 , a repair location notification service 322 , a consumable part life prediction service 323 , a failure sign service 324 , and a device search service 325 .
[0027] There are no limitations on the configuration of each service in the management system 101. For example, the management system 101 may have only one of the repair location notification service 322, the consumable part life prediction service 323, and the failure sign service 324.
[0028] The device 102 includes a device data collection unit 301 and a device data notification unit 302 . The device data collection unit 301 collects various data (mainly device data here) within the device 102 , and passes it to the device data notification unit 302 .
[0029] The device data notification unit 302 transmits the device data collected by the device data collection unit 301 to the management system 101. Note that a management server for collecting data may mediate the collection of device data from the device 102. In this case, the management server can extract data required by the management system 101 from the data sent from the device 102, and transmit the extracted data to the device data receiving unit 303.
[0030] In the example shown in FIG. 3, only one device 102 is shown, but one or more other devices 102 having a similar functional configuration may be connected to the management system 101.
[0031] In the management system 101, a device data receiving unit 303 receives device data transmitted from a device data notifying unit 302 of the device 102 and notifies each service. In this embodiment, the device data is sent to an error determining unit 305, a consumable part life predicting unit 307, and a failure predicting unit 309 depending on the type of the data.
[0032] The device management service 321 is a service for managing devices that are targets of the management system 101, and includes a device management unit 304. The device management unit 304 manages device information, including information on the customer 103 to which the device 102 belongs, for the device 102 that is to be managed by this system. For example, when the device 102 is connected to the management system 101 for the first time and a registration process for the management system 101 is performed, the management system 101 receives the device information. The device management service 321 is an example of a management unit that manages device information set for each device, mainly in cooperation with the CPU 201 .
[0033] The device information includes, for example, customer information to which the device 102 belongs, a device ID (device serial number), a model name, etc. The device information may also include, as setting information, the installation location of the device 102. The information on the installation location is set for each intranet, for example.
[0034] The repair location notification service 322 is a service that receives and analyzes information about an error that has occurred in the device 102, and presents information about the location where the error should be repaired. The repair location notification service 322 includes an error determination unit 305 and an estimation result management unit 306.
[0035] When the error determination unit 305 receives error information from the device data receiving unit 303, it analyzes the error information and estimates the treatment information (replacement of parts, cleaning, adjustment, etc.) required to eliminate the error. Then, the error determination unit 305 notifies the estimated treatment information together with the error information to the estimation result management unit 306. Note that the error information is mainly information on the part or function where the actual failure has occurred. The error information also includes, for example, jam information. The treatment information is an example of information on the estimation result of the failure. The estimation result management unit 306 manages information about errors that have occurred in the device 102 and information about estimated actions to be taken, and provides the information to a device search service 325 .
[0036] The consumable part life prediction service 323 is a service that receives and analyzes the degree of wear (wear rate) of a consumable part included in the device 102, and presents the number of days remaining until the end of the life period of the consumable part. Hereinafter, the number of days remaining until the end of the life period of a consumable part is referred to as the remaining life days. Information on the remaining life days is an example of information on the consumable part life period. The consumable part life prediction service 323 includes a consumable part life prediction unit 307 and a life prediction result management unit 308.
[0037] The consumable part life prediction unit 307 receives the wear level of the consumable part from the device data receiving unit 303, calculates the remaining life days, and notifies the calculated remaining days to the life prediction result management unit 308. One method of analyzing the consumable part life prediction is, for example, to calculate the amount of change in wear rate and calculate the number of days until the wear rate of the consumable part exceeds a threshold value to calculate the remaining life days. Note that there is no restriction on the method of calculating the remaining life days, and multiple device data other than the amount of change in wear rate may be handled for the calculation. The life prediction result management unit 308 manages the information on the remaining life days notified from the consumable part life prediction unit 307 and provides it to a device search service 325 .
[0038] The failure sign service 324 is a service that detects abnormal values and seeks failure signs of components by analyzing sensor data that is detection data of a sensor included in the device 102. The failure sign service 324 includes a failure sign unit 309 and a failure sign result management unit 310.
[0039] The failure prediction unit 309 detects abnormal values by receiving and analyzing sensor data from the device data receiving unit 303, and notifies the detected failure prediction result of the component to the failure prediction result management unit 310. In this embodiment, the failure prediction unit 309 detects abnormal values and determines a failure prediction, but the determination may be made by machine learning, and there are no limitations on the data used or the detection method. The failure sign result management unit 310 manages the failure sign results of the components and provides them to the device search service 325 .
[0040] At least one of the repair location notification service 322, the consumable parts life prediction service 323, and the failure sign service 324 is an example of an analysis means that analyzes the state of a device based on device data acquired from the device, mainly in cooperation with the CPU 201.
[0041] The device search service 325 is a service that searches for devices 102 that are targets of management of the management system 101, and provides information held by each service regarding the searched device 102. The information held by each service is information managed by the estimation result management unit 306, the lifespan prediction result management unit 308, and the failure sign result management unit 310, respectively. The device search service includes a device search section 311 , a device display section 312 , an associated device search section 313 , and an associated device display section 314 .
[0042] The device search unit 311 searches for the devices 102 managed by the device management unit 304 in accordance with a request (input instruction) from a user (here, a user on the administrator side; the same applies below).
[0043] The device display unit 312 displays information about devices searched for (found by search) by the device search unit 311 in response to a request from a user. Here, the device display unit 312 displays at least the device information as information about the device 102. Typically, the device display unit 312 displays information indicating the status of the device 102 together with the device information.
[0044] The information indicating the state of the device 102 is information managed by the estimation result management unit 306, the life prediction result management unit 308, and the failure sign result management unit 310. In other words, the information indicating the state of the device 102 includes, from among the device data, error information, information on parts with signs of failure, information on the remaining days of life, and the like.
[0045] The device display unit 312 may display other information, such as counter information and firmware information of the device 102, in addition to the device information and the information indicating the state of the device 102 obtained as a result of the analysis.
[0046] The associated device search unit 313 searches for other devices 102 that belong to the same group as the group to which the device 102 searched for by the device search unit 311 belongs. Hereinafter, devices 102 other than the searched device 102 that belong to the same group as the group to which the searched device 102 belongs are referred to as associated devices.
[0047] For example, the associated device search unit 313 searches for associated devices based on device information of the searched device 102 managed by the device management unit 304. Typically, the associated device search unit 313 searches for associated devices belonging to the same customer 103 based on customer information (such as a customer name or a customer ID) of the customer 103 among the device information.
[0048] However, related devices are not limited to devices 102 linked to the same customer 103. An administrator user (or engineer) can freely set the scope of a group (group definition). For example, a group may be a collection of devices that have location information of the same range, such as the same building or address. Alternatively, a group may be a collection of devices set in any unit managed by an engineer, such as a category unit determined by the engineer.
[0049] The associated device display unit 314 displays the associated devices searched for (found by search) by the associated device search unit 313. Specifically, the associated device display unit 314 displays information on the searched associated devices, that is, device information on those devices. The associated device display unit 314 displays information on devices requiring treatment based on information (results of analysis) managed by the estimation result management unit 306, the life prediction result management unit 308, and the failure sign result management unit 310, and also displays information indicating the order of urgency of the treatment. Specifically, the associated device display unit 314 displays information on associated devices in order of urgency. In addition to the information on associated devices, the associated device display unit 314 can also display information indicating the status of the associated devices obtained as a result of analysis. The flow for determining the urgency of treatment is shown in the flowchart of FIG. 4.
[0050] <Device search and display process> 4 is a flowchart showing a process in which the device search unit 311 searches for devices managed by the device management unit 304, the associated device search unit 313 searches for devices associated with the searched devices, and the associated device display unit 314 displays them. This process is realized by the CPU 201 executing a program stored in the HDD 203 or the like. User Interface (UI) data generated in this process is displayed on the display device 208 via the display control unit 207.
[0051] In this embodiment, the UI is displayed via the display device 208 of the device management system 101, but the UI may be displayed via a separate browser, and the display method is not limited.
[0052] In S401, in response to a user request, the device search unit 311 searches for devices 102 managed by the device management unit 304. The devices 102 to be searched for are, for example, devices notified by the customer that may require some kind of action, but are not limited to such cases. If the device search does not find the corresponding device 102, the process ends.
[0053] In this embodiment, the device search unit 311 performs a device search using a device ID, and displays the devices 102 that match the condition of "prefix match" as the search result. Note that the device search unit 311 may perform a device search using the condition of "exact match" using a device ID, or may perform a search using information other than the device ID, and the method of searching for the devices 102 is not limited.
[0054] In S402, in accordance with the device search results in S401, the device display unit 312 displays device information managed by the device management unit 304. The device display unit 312 also displays information indicating the device status managed by the estimation result management unit 306, the lifespan prediction result management unit 308, and the failure sign result management unit 310. The device search unit 311 is an example of a first search means that searches for the device 102 mainly in cooperation with the CPU 201. The device display unit 312 is an example of a first display means that displays information about the searched device mainly in cooperation with the CPU 201.
[0055] In S403, in response to a user request, the associated device search unit 313 searches for associated devices that belong to the same group based on the device information displayed in S402. In this embodiment, the associated device search unit 313 searches for other devices 102 included in the customer 103 to which the device 102 belongs, as associated devices. The associated device search unit 313 is an example of a second search means that, mainly in cooperation with the CPU 201, searches for at least devices that are related to the searched device and require action as associated devices based on information about the searched device.
[0056] In S404 to S409, the associated device display unit 314 determines the priority of the associated devices to be displayed, and sorts and displays the associated devices according to the priority. Note that, instead of the associated device display unit 314 determining the priority of the associated devices, an analysis function (analysis means) may determine it.
[0057] In S404, the associated device display unit 314 judges whether the searched associated device is a faulty device in which an error has occurred (a device having a faulty part or function). For example, the device 102 that is the source of error information and that requires treatment corresponding to the treatment information estimated by the estimation result management unit 306 is judged to be a faulty device. In this way, if it is judged that a faulty device exists, the process transitions to S405, and if it is judged that a faulty device does not exist, the process transitions to S406.
[0058] In S405, the associated device display unit 314 regards the device 102 determined to be out of order as a device that requires treatment with the highest priority. In S410, the associated device display unit 314 displays the associated devices in order of urgency according to the priority set here.
[0059] In S406, the associated device display unit 314 determines whether the searched associated device is a device with a failure sign. For example, the device 102 having part information in which a failure sign has been detected and managed by the failure sign result management unit 310 is determined to be a device with a failure sign. If it is determined that the device 102 has a failure sign, the process proceeds to S407, and if it is determined that the device 102 does not have a failure sign, the process proceeds to S408.
[0060] In S407, the associated device display unit 314 regards the device 102 determined to have a malfunction symptom as a second priority device. In S410, the associated device display unit 314 displays the associated devices in order of urgency according to the set priority.
[0061] In S408, the associated device display unit 314 determines whether the parts of the searched associated devices are nearing the end of their life spans. For example, a device 102 managed by the life span prediction result management unit 308 that has a part whose remaining life span is within a threshold value is regarded as a device that has a part nearing the end of its life span. Hereinafter, a device that has a part nearing the end of its life span may also be referred to as a near-life part device. The threshold value of the remaining life days may be set for each device 102 or may be a fixed value, and there is no limitation on the method of setting the threshold value. If the associated device is determined to be a near-life part device, the process proceeds to S409, and if the associated device is determined to not be a near-life part device, the process proceeds to S410.
[0062] In S409, the associated device display unit 314 regards the near-life part device as a third-priority device. In S410, the associated device display unit 314 displays the associated devices in order of urgency according to the set priority.
[0063] In S410, the associated device display unit 314 sorts and displays the associated devices in order of urgency according to the first, second, and third priorities set in S405, S407, and S409, respectively. In this embodiment, the associated device display unit 314 sorts and displays the associated devices in the order of first priority, second priority, and third priority, assuming that the urgency is greatest in that order. The associated device display unit 314 does not display devices for which no priority has been set as associated devices. However, devices for which no priority has been set may be displayed as devices with low urgency, and the display order of the devices with low urgency is not limited.
[0064] The related device display unit 314 is an example of second display means that mainly displays, in cooperation with the CPU 201, information indicating the order of urgency of the searched related devices that require treatment.
[0065] <Example of GUI> Next, with reference to FIGS. 5 to 7, an example of a GUI (Graphical User Interface) until the management system 101 sorts and displays related devices according to the flow of FIG. 4 will be described. FIG. 5 is a diagram showing an example of a device search screen.
[0066] The device search screen 501 is a screen on which the device search unit 311 searches for the devices 102 managed by the device management unit 304. The device search screen 501 includes a device search box 502, a device search button 503, and a device search result list 504.
[0067] The device search box 502 is an input field for specifying the device ID of the device 102 that the user wants to search for. The example shown in FIG. 5 is configured to search for the device 102 by specifying the device ID, but any information that can be used to search for the device 102, such as the friendly name of the device 102, may be specified.
[0068] The device search button 503 is a button for executing a search for the device 102 according to the device ID input in the device search box 502. When the device search button 503 is pressed, the search result is displayed in the device search result list 504.
[0069] The device search result list 504 displays devices 102 that meet the search criteria in the device search, together with information about the devices managed by the device management unit 304. Hereinafter, the device 102 searched for (found by search) by the device search unit 311 will be referred to as device 102A. In this embodiment, devices (two devices, DEV11111 and DEV11112) having device IDs that prefix-match the device ID (DEV1111) specified in the device search box 502 are displayed as search results.
[0070] In the example shown in FIG. 5, device information (device ID, model name, customer name) is displayed as information about device 102A, but device data may also be displayed, and the information that is displayed is not limited.
[0071] When the user selects one device 102A from the one or more devices 102A displayed in the device search result list 504, the screen transitions to a device alert list screen 505. Hereinafter, the one device selected by the user from the one or more searched devices 102A will be referred to as device 102AS.
[0072] 6 is a diagram showing an example of a device alert list screen 505. The device alert list screen 505 displays a list of alerts as information indicating the state of one device 102AS selected in the device search result list 504. The device alert list screen 505 includes selected device information 506, an error information list 507, a list of faulty parts (parts showing signs of failure) 508, and a list of parts due for replacement soon 509. The error information list 507 also includes jam information.
[0073] The selected device information 506 shows the device information of the device 102AS. In the example shown in the figure, the device ID (DEV11111), the customer name (XX Corporation), and the installation location (YY building / ZZ floor) are displayed. However, other information such as the model name may be displayed.
[0074] The error information list 507 displays a list of error information that has occurred in the device 102AS, based on the error information and action information managed by the estimation result management unit 306. In the example shown in the figure, one item of error information 507a and one item of jam information 507b are displayed. For the error information 507a, an icon 515 and other information 518 are displayed. The other information is, for example, an error code, an error name, the date and time of the error occurrence, and the accuracy of the treatment information (accuracy of the estimated information). The accuracy of the treatment information indicates the accuracy of the estimation result by the estimation result management unit 306, that is, the accuracy of the estimated treatment information. Similarly, an icon 515 is displayed for jam information 507b, and the jam error code and the date and time when the jam occurred are displayed as other information 518.
[0075] The faulty parts list 508 displays a list of parts that are deemed to have a fault sign in the device 102AS based on the fault sign results managed by the fault sign result management unit 310. In the example shown in the figure, one item is displayed. As faulty part information, an icon 516, part name, and the deadline until a fault is predicted based on the fault sign information are displayed. Note that other part information such as part number may also be displayed as the faulty part information.
[0076] The list of parts due for replacement soon 509 displays a list of parts (parts owned by the device 102AS) that are close to the end of their life spans managed based on the remaining number of days in life by the life prediction result management unit 308. In the example shown in the figure, two items are displayed. In the example shown in the figure, an icon 517 indicating that the part is nearing the end of its life span, the part name, and the estimated replacement date (or remaining number of days of life) are shown as part information about parts that are nearing the end of their life span. For example, two or three types of icons may be set for each level of urgency based on a first threshold value of the estimated date for a part that needs to be replaced immediately and a second threshold value of the estimated date for a part that can be assumed to be replaced at the same time. In the example shown in the figure, icons of different colors may be set for each level of urgency. Not limited to color, shapes and / or patterns may also be set for each level of urgency.
[0077] The associated device menu 510 is a menu for transitioning to an associated device display screen 511 that displays the devices 102 associated with the device 102AS.
[0078] 7 is a diagram showing an example of an associated device display screen 511. The associated device display screen 511 is a screen that displays information on one or more associated devices 102 searched for by the associated device search unit 313 based on information on the device 102AS. Hereinafter, the device 102 searched for by the associated device search unit 313 will be referred to as an associated device 102B. The devices 102 found by the associated device search unit 313 based on the customer information to which the device 102AS belongs and which belong to the same customer 103 are displayed as associated devices 102B. The associated device display screen 511 then displays the device information as information on the associated devices 102B.
[0079] The associated device display screen 511 displays information about the associated devices 102B in order of the urgency of the treatment according to the flow of Fig. 4 (associated device list 512). Here, information about devices for which no priority has been set (no treatment is required) is not displayed. However, devices for which no priority has been set may also be displayed, for example, in a separate column.
[0080] The associated device list 512 displays the associated devices 102B in order of urgency of treatment, for example, from the top, based on the priority determined in accordance with S404 to S409 shown in Fig. 4. The selected device display field 513 displays information about the device 102AS searched and selected on the device search screen 501 (the device that was the search source when the associated device display screen 511 was opened). In the example shown in the figure, this device 102AS is displayed at the top of the associated device list 512. It should be noted that the associated device list 512 does not have to include the device display column 513. In other words, the associated device list 512 does not have to display the device 102AS that is the source of the search.
[0081] The associated device display field 514 displays one or more associated devices 102B searched for by the associated device search unit 313. When the user selects one associated device 102B from the associated device display field 514, the device search service 325 switches the search source device 102AS and displays the device alert list screen 505 (FIG. 6). For example, when DEV22222 is selected in the associated device display field 514 (when switch button 519 is pressed), the device alert list screen 505 is displayed and information about DEV22222 is displayed in selected device information 506.
[0082] In the related device list 512, in addition to the device ID, customer name, and installation location, an icon 515 indicating that a failure such as an error / jam has occurred and an icon 516 indicating that there are signs of failure are displayed for each device. Also, for each of the devices DV33333 and DV44444, an icon 517 indicating that there is a part near the end of its life span is displayed. Furthermore, the update date and time when device data was received and the device status was updated is displayed.
[0083] The associated device list 512 displays the associated devices 102B in descending order of the urgency of the treatment as described above, based on the priority determined in accordance with S404 to S409 shown in Fig. 4. The associated device list 512 may be displayed in a visually easy-to-understand manner, such as by color-coding the devices according to the urgency.
[0084] Conventionally, an engineer on the administrator side of the management system 101, for example, would respond to a call for service to deal with a single device by confirming the work required to repair that device and then dispatching the device. Here, the information the engineer received in the call request was the serial number of the requested device, and when responding to the call request, the engineer was unable to check other devices that required repair or part replacement at the site.
[0085] In response to this, the management system 101 according to the present embodiment provides information on the associated device 102B that is related to the searched device 102A and requires treatment. That is, the engineer can obtain not only information on the searched device 102A but also information on the associated device 102B that is related to the device 102A and requires treatment. For example, if the associated device 102B is a device of the same customer as the customer who uses the device 102A, the engineer can also deal with the associated device 102B on-site while dealing with the searched device 102A, such as dealing with the treatment. This allows efficient dispatch of engineers, and improves the work efficiency of the administrator, including the engineer.
[0086] Moreover, in this embodiment, when there are multiple associated devices 102B that require treatment, the order of urgency is displayed. This allows an engineer to quickly and easily recognize the urgency, i.e., the priority of treatment, simply by looking at the display screen (associated device display screen 511 shown in FIG. 7). In other words, in this embodiment, engineers can more efficiently handle devices that require treatment, and the work efficiency of managers, including engineers, can be further improved.
[0087] [Second embodiment] Next, an example of a GUI in the second embodiment will be described. Fig. 8 is a diagram showing an example of a related device display screen as the GUI. Hereinafter, the description of the same parts as the configuration, functions, and processes in the first embodiment will be omitted or simplified.
[0088] As described above, this associated device display screen 601 displays information about associated devices 102B based on information about devices 102AS searched and selected on the device search screen 501. This embodiment differs from the first embodiment in that the associated device list 602 includes a group selection button 603. In this embodiment, since one device may belong to multiple groups, a group can be selected by using the group selection button 603. Note that although the group selection button 603 allows selection in a pull-down format, the selection format is not limited to this method.
[0089] The associated device list 602 displays information about associated devices 102B that belong to a group ("Group A" in the figure) selected by the user via a group selection button 603. By switching groups with the group selection button 603, the associated device list 602 can display a list of associated devices 102B that belong to a different group. As in the first embodiment, the associated device list 602 does not have to include the device display field 513.
[0090] In this embodiment, by switching the group selection button 603, the associated device list 602 displays associated devices 102B that belong to the group to which the device 102AS belongs and that belong to the switched-to different group. However, the associated device list 602 may display devices of all groups to which the selected device 102AS belongs as a list of associated devices 102B, and display each group as a display item. An example in which multiple groups to which one device (selected device 102AS) belongs are collectively displayed will be described below.
[0091] 9 is a diagram showing an example of a group list screen that displays all groups to which one device 102AS belongs. The group list screen 901 includes a group display field 902 that displays information about the group to which the device 102AS belongs. The information about the device 102AS is displayed as selected device information 506.
[0092] In the illustrated example, the group display field 902 displays three groups with the group names "AAA", "BBB", and "CCC", and also displays the number of associated devices 102B that require treatment for each group. Other detailed information may also be displayed. The group list screen 901 displays information indicating the urgency order of the groups according to the total number of these vehicles, and here displays the groups in order of urgency. The greater the total number of vehicles, the higher the urgency, and the higher the number of vehicles, for example, the higher the number of vehicles, and the higher the urgency, and the higher the number of vehicles, ...
[0093] The device search service 325 etc. is an example of a third display means that cooperates with the CPU 201 to display information indicating the urgency order of a group based on information about related devices that require treatment.
[0094] In FIG. 9, for example, in group AAA, one related device is experiencing a failure such as an error, one related device is considered to have a failure symptom, and two devices are near-life part devices, for a total of four devices. The urgency may be determined not by the total number of all the items, but by the number of items with the highest urgency (for example, occurrence of a failure such as an error). The configuration may be such that the total number of all the items and the number of items with the highest urgency can be sorted by input instructions from the user. The group display column 902 may be displayed in a visually easy-to-understand manner, such as by color coding according to the level of urgency.
[0095] In the present embodiment, it is preferable that the number of devices displayed in the group display field 902 includes the device 102AS that is the search source, but this is not necessarily required.
[0096] When the user presses the select button 9021 in the group display field 902, the associated device display unit 314 displays a display screen of information on associated devices of all groups related to the device 102AS. Fig. 10 is a diagram showing an example of the associated device display screen of all groups.
[0097] The associated device display screen 1001, with the urgency order of the groups displayed, displays the associated devices 102B belonging to the groups in order of urgency from the top for each group. That is, within one group, one or more associated devices 102B are displayed in order of urgency from the top. Here, the devices 102AS, which are the search source, are also displayed in order of urgency, but this is not necessarily the case. As information on the associated devices 102B, information such as device ID, customer name, status (failure and signs of failure), consumable parts (parts nearing the end of their life span), and update date and time may be displayed in each column. On the associated device display screen 1001, urgency may be displayed in a visually easy-to-understand manner, such as color coding, etc.
[0098] As described above, in this embodiment, when the selected device 102AS belongs to multiple groups, the groups are displayed in order of urgency, so that the engineer can easily understand the urgency of each group. This improves the work efficiency of the administrator. In addition, the engineer can understand the information of the related device 102B in the group that requires treatment in order of urgency simply by pressing the selection button 9021 corresponding to the group.
[0099] [Other embodiments] In each of the above embodiments, the associated device display screens 511 and 601 display at least the associated devices 102B that require treatment in order of urgency from the top. However, the display does not necessarily have to be in order of urgency, and the associated device display screens 511 and 601 only need to display information indicating the order of urgency. The display information in order of urgency for the associated devices 102B arranged from the top is an example of "information indicating the order of urgency". The information indicating the order of urgency may be, for example, a character string and / or an image indicating the order. The order of urgency may also be expressed by the size or severity of an image showing the information of the related device 102B. Similarly, in the group list screen 901 shown in FIG. 9, the groups are not limited to being displayed in order of urgency, and information indicating the order of urgency of the groups may be displayed.
[0100] In each of the above embodiments, the urgency levels are set according to three device states: occurrence of an error (failure), a sign of failure, and consumable parts. However, the related device search unit 313 and the related device display unit 314 may search for related devices and display them in order of urgency based on at least one of these three. For example, in the list 509 of parts due for replacement in Fig. 6, two or more stages of urgency (first threshold, second threshold) are set for the estimated date for part replacement. That is, in this case, the associated device search unit 313 and the associated device display unit 314 can display the associated devices 102B in order of urgency according to the state of the consumable parts. Additionally, the related device search unit 313 and the related device display unit 314 can search and display based on the number of parts (error (failure) parts, failure-premonitory parts, or consumable parts). The more error-premonitory parts, failure-premonitory parts, or consumable parts a related device has, the higher its urgency (priority). Alternatively, the number of parts is not limited, and a case may be assumed in which a priority is previously determined for each type of part for multiple types of parts. If the parts are faulty parts, parts that indicate a possible failure, or consumable parts, devices having those parts may be displayed in order of urgency according to their priority.
[0101] 4, the priority order is determined such that the second priority is given to devices with signs of failure, and the third priority is given to devices with parts with short life spans. However, the priority order may be determined conversely such that the second priority is given to devices with parts with short life spans, and the third priority is given to devices with signs of failure.
[0102] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) a first searching means for searching for a device; a first display means for displaying information of the searched device; A second search means for searching, based on information of the searched device, at least a device related to the searched device and requiring a treatment as an associated device; and a second display means for displaying information indicating the urgency order of the searched related devices requiring treatment. An information providing system comprising: (Configuration 2) The device further includes an analysis means for analyzing a state of the device based on device data acquired from the device. 2. The information providing system according to configuration 1. (Configuration 3) The first display means further displays information indicating a state of the device based on a result of the analysis. 3. The information providing system according to configuration 2. (Configuration 4) The second display means displays information indicating the status of the related device and information indicating the order of urgency based on a result of the analysis. 4. The information providing system according to configuration 3. (Configuration 5) the analysis means generates, through the analysis, at least one of information indicating the state of the device, including information on a failure estimation result, information on a failure sign result, and information on a life span of a consumable part; The second display means displays information indicating an urgency order of the related devices based on the at least one piece of information. 5. The information providing system according to any one of configurations 2 to 4. (Configuration 6) The device further includes a management unit for managing information of the device. The second search means searches for devices that belong to the same group as the group to which the device searched for by the first search means belongs, as the associated devices, based on the information on the device. 6. The information providing system according to configuration 5. (Configuration 7) The device further includes a third display means for displaying information indicating the urgency order of the groups based on information on the related devices that require treatment when the devices searched for by the first search means belong to multiple groups. 7. The information providing system according to configuration 6. (Configuration 8) The second display means displays information indicating an urgency order of the related devices requiring treatment for each group in a state in which the information indicating the urgency order of the groups is displayed by the third display means. 8. The information providing system according to configuration 7. (Configuration 9) The second display means displays the searched related devices in order of urgency of treatment required. 9. The information providing system according to any one of configurations 1 to 8. (method) searching for a device; displaying information of the searched devices; A step of searching for at least a device that is related to the searched device and requires a treatment as an associated device using information of the searched device; and displaying information indicating an urgency order of the searched related devices requiring treatment. 13. An information providing method comprising:
[0103] The present disclosure has been described above in detail based on preferred embodiments thereof, but the present disclosure is not limited to the above embodiments, and various modifications are possible based on the gist of the present disclosure, and these modifications are not excluded from the scope of the present disclosure.
Claims
1. A first search means for searching for a device; a first display means for displaying information of the searched device; A second search means for searching, based on information of the searched device, at least a device related to the searched device and requiring a treatment as an associated device; and a second display means for displaying information indicating the urgency order of the searched related devices requiring treatment. An information providing system comprising:
2. The device further includes an analysis means for analyzing a state of the device based on device data acquired from the device.
2. The information providing system according to claim 1 .
3. The first display means further displays information indicating a state of the device based on a result of the analysis.
3. The information providing system according to claim 2.
4. The second display means displays information indicating the status of the related device and information indicating the order of urgency based on a result of the analysis.
4. The information providing system according to claim 3.
5. the analysis means generates, through the analysis, at least one of information indicating the state of the device, including information on a failure estimation result, information on a failure sign result, and information on a life span of a consumable part; The second display means displays information indicating an urgency order of the related devices based on the at least one piece of information.
3. The information providing system according to claim 2.
6. The device further includes a management unit for managing information of the device. The second search means searches for devices that belong to the same group as the group to which the device searched for by the first search means belongs, as the associated devices, based on the information on the device.
6. The information providing system according to claim 5.
7. The device further comprises a third display means for displaying information indicating an order of urgency of the groups based on information of the related devices requiring treatment when the devices searched for by the first search means belong to a plurality of groups.
7. The information providing system according to claim 6.
8. The second display means displays information indicating an urgency order of the related devices requiring treatment for each group in a state in which the information indicating the urgency order of the groups is displayed by the third display means.
8. The information providing system according to claim 7,
9. The second display means displays the searched related devices in order of urgency of treatment required.
2. The information providing system according to claim 1 .
10. searching for a device; displaying information of the searched devices; A step of searching for at least a device that is related to the searched device and requires a treatment as an associated device using information of the searched device; and displaying information indicating an urgency order of the searched related devices requiring treatment.
13. An information providing method comprising: