Usage satisfaction degree diagnosis system, usage satisfaction degree diagnosis method, and computer program

Abstract

To provide a usage satisfaction degree diagnosis system capable of awaking a user to a consumer behavior for using a product for a long term while suppressing failures and deterioration.SOLUTION: A usage satisfaction degree diagnosis system includes a device information acquisition unit that acquires information about at least one of an operation on a device, setting of the device, and the arrangement environment of the device, a usage satisfaction degree diagnosis unit that diagnoses a usage satisfaction degree concerning at least one of a user's usage condition of the device and the installation environment of the device on the basis of the information acquired by the device information acquisition unit, and a diagnosis result output unit that outputs a diagnosis result obtained by the usage satisfaction degree diagnosis unit.SELECTED DRAWING: Figure 24

Description

[Technical field]

[0001] The present invention relates to a utilization goodness diagnostic system, a utilization goodness diagnostic method, and a computer program. [Background technology]

[0002] In recent years, efforts to achieve the Sustainable Development Goals (SDGs) have expanded and are attracting more attention. Among the 17 goals and 169 targets set out in the SDGs is "Goal 12: Responsible Consumption and Production" and the target to achieve it is "12.5: By 2030, substantially reduce waste generation through prevention, reduction, recycling and reuse."

[0003] As one of the efforts to target this target, consumer behavior such as "using the product for a long time" is encouraged for product users. In addition, there is a support technology that enables driving support such as diagnosing the driving characteristics of the driver from driving data and providing the diagnosis results and advice with the aim of improving the driving operation technique of the driver (user of the product) in driving an automobile (Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-37002 A Summary of the Invention [Problem to be solved by the invention]

[0005] Consumer behavior such as "using products in bad environments" and "rough handling of products" leads to "breakdown" and "accelerated deterioration" of products and their component parts, and increases the frequency of waste generation. In order to improve this "consumer behavior that increases the frequency of waste disposal," it is necessary to support product users in understanding and improving their own consumer behavior.

[0006] In addition, while support for driving techniques and driving awareness for the purposes of "improving driving operation techniques" and "reducing fuel consumption and CO2 emissions to prevent global warming" as in Patent Document 1 is being implemented for automobile driving, no support is being provided for the purpose of reducing waste.

[0007] Therefore, one of the objects of the present invention is to provide a utilization efficiency diagnostic system that can make users aware of consumption behavior that reduces product failures and deterioration and enables products to be used for a long period of time. [Means for solving the problem]

[0008] A utilization efficiency diagnostic system according to one aspect of the present invention comprises: a device information acquisition unit that acquires information regarding at least one of a device operation, a device setting, and a device placement environment; a utilization efficiency diagnosis unit that diagnoses a utilization efficiency of at least one of a device utilization status by a user and a device installation environment based on the information acquired by the device information acquisition unit; a diagnostic result output unit that outputs a diagnostic result by the utilization degree diagnostic unit; The present invention is characterized by comprising: Effect of the Invention

[0009] According to the present invention, it is possible to realize a utilization efficiency diagnostic system that can make users aware of consumption behaviors that will reduce product failures and deterioration and allow the products to be used for a long period of time. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of a utilization goodness diagnostic system according to a first embodiment. [Diagram 2] 1A and 1B are diagrams illustrating an example of the hardware configuration of a utilization goodness diagnostic system 121 and client terminals 131 to 133 in the first embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of a functional block of the utilization improvement diagnostic system according to the first embodiment. [Figure 4] 11 is a diagram showing an example of a main menu screen displayed when a user logs in on the UI operation panel of the client terminal (multifunction peripheral) according to the first embodiment. FIG. [Diagram 5] 11 is a diagram showing an example of a display of a usability rating (overall evaluation) on a UI operation panel of the client terminal (multifunction peripheral) according to the first embodiment. FIG. [Figure 6] This is a diagram showing a display example in which overall evaluation 501 is selected in FIG. 5, and furthermore, "individual" is selected in target user pull-down menu 505 and "monthly" is selected in aggregation period unit pull-down menu 506. [Figure 7] This is a diagram showing a display example in which overall evaluation 501 is selected in FIG. 5, and furthermore, "department" is selected in target user pull-down menu 505 and "yearly" is selected in aggregation period unit pull-down menu 506. [Figure 8] FIG. 13 is a diagram showing an example of a display screen relating to a hardware utilization advantage degree when Utilization (Hardware) 502 is selected on the UI operation panel of the client terminal (multifunction peripheral) according to the first embodiment. [Figure 9] FIG. 13 is a diagram showing an example of a display screen relating to a software utilization advantage level when Utilization (Software) 503 is selected on the UI operation panel of the client terminal (multifunction peripheral) according to the first embodiment. [Figure 10] FIG. 13 is a diagram showing an example of a utilization favorability screen when an environment 504 is selected on the UI operation panel of the client terminal (multifunction peripheral) according to the first embodiment. [Figure 11] FIG. 11 is a diagram showing a display example of a screen for selecting a counting method of a utilization goodness level on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 12] FIG. 12 is a diagram showing a display example when an item is selected in FIG. [Figure 13] FIG. 11 is a diagram illustrating an example of a display of a utilization favorability level (overall evaluation) on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 14] 14 is a diagram showing examples of pull-down items of the pull-down 811 in FIG. 13. [Figure 15] FIG. 11 is a diagram showing an example of display of a utilization favorability level (utilization (hardware)) on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 16] FIG. 13 is a diagram showing a display example of an area 903 for a utilization degree (utilization (hardware)) on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 17] FIG. 17 is a diagram showing an example of a display when the main body door open / close icon 904 in FIG. 16 is pressed. [Figure 18] FIG. 11 is a diagram showing an example of display of a utilization favorability level (utilization (software)) on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 19] FIG. 10 is a diagram showing a display example of an area 1002 of a utilization favorability level (utilization (software)) on a Web portal screen of a client terminal (information terminal) according to the first embodiment. [Figure 20] FIG. 20 is a diagram showing an example of a display when a power OFF icon 1003 in FIG. 19 is pressed during job execution. [Figure 21] FIG. 11 is a diagram illustrating an example of a display of a utilization favorability degree (environment) on a Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 22] FIG. 22 is a diagram showing a display example of the utilization efficiency (environment) area 1102 on the Web portal screen of the client terminal (information terminal) according to the first embodiment. [Figure 23] FIG. 13 is a diagram showing another example of display of the utilization advantage degree (environment) on the Web portal screen of the client terminal (information terminal) in the first embodiment. [Figure 24] 1 is a process flowchart for making a "diagnosis request" and "acquisition of diagnosis results" from a client terminal (multifunction device / information terminal) to the utilization performance diagnosis system in the first embodiment. [Diagram 25] 25 is a flowchart showing an example of processing of the utilization goodness diagnostic system 121 according to FIG. 24. [Figure 26] 25 is a flowchart showing an example of processing performed by the client terminal (information terminal) 133 according to FIG. 24. [Figure 27] FIG. 11 is a diagram showing a display example of a utilization favorability level (utilization (software)) on a UI operation panel of a client terminal (multifunction machine) according to the second embodiment. [Figure 28] FIG. 27 is a diagram showing an example of a pop-up screen 1302 that appears when the improvement recommendation button 1301 in FIG. 27 is pressed. [Figure 29] FIG. 11 is a diagram showing an example of display of a utilization favorability level (utilization (software)) on a Web portal screen of a client terminal (information terminal) according to the second embodiment. [Diagram 30] FIG. 14 is a diagram showing an example of a pop-up screen 1402 that appears when an improvement recommendation button 1401 is pressed on a Web portal screen of a client terminal (information terminal) according to the second embodiment. [Diagram 31] FIG. 30 shows examples of pull-down items when pull-down 1404 and pull-down 1405 are opened. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiment of the present invention will be described with reference to the drawings. However, the present invention is not limited to the following embodiment. In each drawing, the same members or elements are given the same reference numerals, and duplicated descriptions are omitted or simplified. EXAMPLES

[0012] 1 is a diagram showing an example of the overall configuration of a utilization goodness diagnostic system in the first embodiment of the present invention. In FIG. 1, a utilization goodness diagnostic system 121 and client terminals 131 to 133 are connected via a network 101.

[0013] The network 101 is, for example, a communication network such as the Internet or other LAN, a WAN, a telephone line, a dedicated digital line, ATM (Asynchronous Transfer Mode), etc. The communication network may also be a frame relay line, a cable television line, a wireless line for data broadcasting, etc.

[0014] It is sufficient for the network 101 to be capable of transmitting and receiving data. In this embodiment, the network 101 may be the Internet, a general home or office network, or a wireless LAN set up in a city.

[0015] The client terminals 131 and 132 in this embodiment are, for example, multifunction machines (image forming devices) that realize a plurality of types of functions such as copying, scanning, faxing, etc. When there is a change in sensing information acquired by each sensor provided in the client terminals 131 and 132, the client terminals 131 and 132 request a diagnosis of the utilization degree to the utilization degree diagnosis system 121 via the network 101.

[0016] When the utilization efficiency diagnostic system 121 receives a diagnostic request, it calculates the utilization efficiency of the usage environment and user usage status of the client terminals 131 and 132 based on the “sensing information included in the diagnostic request” and the “past history of sensing information”, and registers the diagnostic results.

[0017] Furthermore, the client terminals 131 and 132 request the utilization goodness diagnostic system 121 to obtain a diagnostic result via the network 101. Upon receiving the request to obtain a diagnostic result, the utilization goodness diagnostic system 121 responds to the client terminals 131 and 132 with the diagnosed diagnostic result.

[0018] The client terminals 131 and 132 that receive the response reflect the state of the utilization degree in the LED lamps on their own UI operation panels, and display the diagnosis results on the screen of the UI operation panel based on the user's screen display instruction.

[0019] The client terminal 133 is a mobile terminal such as a PC or a smartphone that performs information processing. The client terminal 133 requests the utilization efficiency diagnostic system 121 via the network 101 to obtain a diagnostic result based on a user instruction on a web browser.

[0020] When the utilization efficiency diagnostic system 121 receives the request to obtain the diagnostic results, it responds to the client terminal 133 with the diagnostic results that have already been diagnosed for the client terminals 131 and 132. Upon receiving the response, the client terminal 133 displays the diagnostic results on the web browser.

[0021] The utilization goodness diagnostic system 121 not only diagnoses the utilization goodness and responds to requests to obtain the diagnosis results, but also manages users who use the client terminals 131 to 133. That is, the utilization goodness diagnostic system 121 receives login / logout requests from the client terminals 131 to 133 and performs login / logout processing.

[0022] The utilization goodness diagnostic system 121 can be constructed by adopting a server computer, cloud computing technology, etc. In this case, the server function may be realized by a single server or may be realized by multiple servers.

[0023] 2(A) and (B) are diagrams showing examples of the hardware configuration of utilization goodness diagnostic system 121 and client terminals 131 to 133 in Example 1. Fig. 2(A) is a diagram showing an example of the hardware configuration of client terminals (multifunction peripherals) 131 and 132, and Fig. 2(B) is a diagram showing an example of the hardware configuration of utilization goodness diagnostic system 121 and client terminal (information terminal) 133.

[0024] 2A, a CPU 201 functions as a computer that controls the client terminals (multifunction peripherals) 131 and 132, and a RAM 202 functions as a work area for the CPU 201. A HDD 203 stores various computer programs executed by the CPU 201 and various data used in the processes executed by the CPU 201. The HDD 203 also temporarily stores data and is used in place of the RAM 202.

[0025] A CPU 201 reads out a computer program stored in a HDD 203 into a RAM 202 and executes it to configure each of the functional blocks of client terminals (multifunction peripherals) 131 and 132 (to be described later) and to realize the processing of the flowcharts.

[0026] The operation unit 204 is a display, a liquid crystal display, a touch panel, or the like, which displays the status of the client terminals (multifunction peripherals) 131 and 132, error messages, and the like, and receives input regarding the designation of a desired print job, and the like.

[0027] Furthermore, the operation unit 204 can read a card held up by the user to perform login authentication (card authentication), and can also perform login authentication (keyboard authentication) from information entered via a keyboard or the like of the operation unit 204.

[0028] Furthermore, the operation unit 204 can indicate, by its own LED lamp, a state in which an error is occurring, a state in which a job is being executed, etc. A NIC (Network Interface Card) 205 is used by the client terminals (multifunction peripherals) 131 and 132 to exchange data with other network devices via the network 101.

[0029] A printer (printing device) 206 prints scanned image data, etc. onto paper. The printer 206 can identify the status of paper feed options (paper feed cassettes, etc.) and paper discharge options (finisher devices, etc.) related to printing processing.

[0030] A scanner (reading device) 207 reads a paper document placed on a platen and generates black and white binary or multi-value color image data (print data), etc. A printer 206 can print the image data read by the scanner 207.

[0031] The interface 208 indicates an external device I / F that transmits and receives data to and from peripheral devices (such as various external sensors). The operation unit 204, the printer 206, and the scanner 207 each include various sensors. For example, the operation unit 204 includes a human sensor that detects whether a human body is present around the client terminals (multifunction peripherals) 131 and 132.

[0032] For example, the printer 206 includes sensors that detect the opening and closing of the main body doors and paper cassettes of the client terminals (multifunction devices) 131 and 132, and sensors that detect the presence or absence of paper inside the main body (including paper jams during paper transport).The printer 206 also includes sensors that detect the placement environment information (temperature, humidity, vibration, etc.) of the client terminals (multifunction devices) 131 and 132, a sensor that detects the ON / OFF state of the power button, and the like.

[0033] The scanner 207 includes a sensor for detecting the presence or absence of paper in the scanner 207 (including paper jams when transporting a scanned document), a document reading sensor (which can also detect dirt on the document table glass), a sensor for detecting whether the document table is open or closed, etc. The above devices are connected to each other via a main bus 200.

[0034] As described above, Fig. 2(B) shows an example of the hardware configuration of utilization goodness diagnostic system 121 and client terminal (information terminal) 133. In Fig. 2(B), CPU 211 as a computer controls utilization goodness diagnostic system 121 and client terminal (information terminal) 133 as a whole. CPU 211 executes computer application programs, OS, etc. stored in HDD 213.

[0035] The CPU 211 then performs control to temporarily store information, files, etc. required for executing the program in the RAM 212. The RAM 212 is a temporary storage means, and functions as the main memory, work area, etc. of the CPU 211.

[0036] The HDD 103 is one of the external storage means, functions as a large-capacity memory, and stores application programs such as a web browser, programs for a group of service servers, an OS, related programs, and the like.

[0037] The operation unit 214 is a display means, and has a function of accepting operation instructions from a user (operation instructions via a touch panel, mouse, keyboard, etc.) and displaying the results of processing based on the operation instructions.

[0038] The NIC 215 is used by the utilization goodness diagnostic system 121 and the client terminal (information terminal) 133 to exchange data with other network devices via the network 101. The interface 216 is an external device I / F, and transmits and receives data to and from peripheral devices such as various external sensors. The above devices are connected to each other via the main bus 210.

[0039] FIG. 3 is a diagram showing an example of functional blocks of the utilization efficiency diagnostic system in the first embodiment, and illustrates an example of the functional block configuration in which functions related to this embodiment are extracted from the utilization efficiency diagnostic system 121, client terminals 131 to 133, etc. in this embodiment.

[0040] Some of the functional blocks shown in FIG. 3 are realized by causing a CPU serving as a computer included in the utilization degree diagnostic system 121 and the client terminals 131 to 133 to execute a computer program stored in a memory serving as a storage medium.

[0041] However, some or all of these may be realized by hardware. For the hardware, a dedicated circuit (ASIC) or a processor (reconfigurable processor, DSP) may be used. Furthermore, the functional blocks shown in Fig. 3 do not have to be built into the same housing, and may be configured by separate devices connected to each other via signal paths.

[0042] First, a description will be given of the functional blocks of the utilization goodness diagnostic system 121. The utilization goodness diagnostic system 121 includes a data communication unit 311, a user management unit 312, a login processing unit 313, and a device information management unit 314.

[0043] The data communication unit 311 is for the utilization goodness diagnostic system 121 to communicate with the client terminals 131-133 to transmit and receive data. The user management unit 312 manages user information of users who log in via the client terminals 131-133.

[0044] The login processing unit 313 receives login requests from the client terminals 131 to 133, collates the information with the information in the user management unit 312, and returns the login processing result to the client terminals 131 to 133. Table 1 is an example of a user information management table for users managed by the user management unit 312.

[0045] [Table 1]

[0046] The user ID column is an ID that uniquely identifies a user. The user name column is the user's name and can be freely set to any name such as a nickname. The department ID column is the ID of the department to which the user belongs. The password column is the basic authentication password used when logging in with the user ID.

[0047] The login processing unit 313 checks the combination of the user ID and password included in the login request from the client terminals 131 to 133 against Table 1, and if they match, returns the login result to each client terminal as successful.

[0048] The login status column indicates the login status of the user, with on indicating a logged-in state and off indicating a logged-out state. The login expiration date column indicates the expiration date of the authentication status of the logged-in user. The user management unit 312 also manages department information of the department to which the user belongs. Table 2 below shows an example of a department information management table managed by the user management unit 312.

[0049] [Table 2]

[0050] The department ID column is an ID that uniquely identifies a department. The department name column is the name of the department and can be named freely. The registration / update date and time column indicates the "date and time when a new department was registered" or the "date and time when the department name of an already registered department was changed." The device information management unit 314 manages model information and individual device information of the client terminals (multifunction peripherals) 131, 132 that are the targets of diagnosis by the utilization performance diagnosis system 121.

[0051] Table 3 below shows an example of a model table which is model information managed by the device information management unit 314. The model ID column is an ID that uniquely identifies the model of the client terminals (multifunction peripherals) 131 and 132. The model name column is the name of the model. [Table 3]

[0052] Next, Table 4 below shows an example of information on each device managed by the device information management unit 314. [Table 4]

[0053] The device ID column is an ID that uniquely identifies each device. The device name column is the name of the device and can be freely set. The model ID column indicates which model ID in Table 3 the device ID corresponds to. The registered user ID column indicates the user ID of the user who registered the device on the utilization efficiency diagnostic system 121 via the device information management unit 314.

[0054] The device information management unit 314 also has various sensor information of each model (Table 3) described above. Table 5 below shows an example of sensor information managed by the device information management unit 314. [Table 5]

[0055] The sensor ID column is an ID that uniquely identifies the sensor installed in each model. The sensor name column is the name of the sensor. The model ID indicates which model the sensor is installed in.

[0056] Furthermore, the device information management unit 314 manages the sensor value history (Table 6) of each sensor (Table 5) used for diagnosis by the utilization efficiency diagnosis system 121, each diagnostic item (Table 7), regular diagnostic results (Table 8), and immediate diagnostic results (Table 9).

[0057] Table 6 below shows an example of the history of sensor values ​​managed by the device information management unit 314. [Table 6]

[0058] The history ID column is an ID that uniquely identifies the history information from the sensor. The user ID column indicates which user used the history. Here, the user ID column contains the login user ID when the history is issued while the user is logged in to the client terminal (multifunction device) 131, 132.

[0059] On the other hand, if the history is issued when the user is not logged in, the user ID will be left blank. The device ID column indicates which device the sensor history is for. The sensor ID_1 column indicates which sensor the sensor history is for, and corresponds to the sensor ID in Table 5.

[0060] The sensor value_1 column indicates the value read by the sensor ID indicated in the sensor ID_1 column. The sensor ID_2 column and sensor value_2 column to the sensor ID_N column and sensor value_N column store the sensor IDs of the device model indicated in the device ID column and the read values ​​of each sensor in order.

[0061] The history records in Table 6 are registered each time sensor information (sensor readings) is transmitted from the client terminals (multifunction devices) 131 and 132. The reception date and time column indicates the reception date and time of the sensor information transmitted from the client terminals (multifunction devices) 131 and 132.

[0062] Here, the timing of transmission of sensor information from the client terminals (multifunction devices) 131 and 132 (timing of issuing history) may be immediately after one or more sensor values ​​are updated, or may be at regular time intervals.

[0063] Also, at regular intervals, it may be determined whether one or more sensor values ​​have been updated, and if there is an update, it may be transmitted. If a user is currently logged in, the above-mentioned immediate transmission or periodic transmission at short intervals (e.g., every few seconds) may be used, and if no user is currently logged in, periodic transmission at long intervals (e.g., every hour) may be used.

[0064] Table 7 below shows examples of diagnostic items managed by the device information management unit 314. [Table 7]

[0065] The item ID column is an ID that uniquely identifies a diagnostic item. The item name column indicates the name of the diagnostic item. For example, there is a diagnostic item name "BodyDoorOpen" based on the frequency of opening and closing the body doors of the client terminals (multifunction devices) 131 and 132, and a diagnostic item name "PanelHists" based on the number of consecutive taps when the user presses the display panel of the operation unit 204.

[0066] There is also a diagnostic item name "PowerOffInJobRunning" based on the frequency of power OFF during job execution on the client terminals (multifunction devices) 131 and 132, and a diagnostic item name "Clearing" based on the presence / absence and frequency of cleaning by system operation. There are also diagnostic item names such as "Temperature" and "Humidity" based on the temperature and humidity of the locations where the client terminals (multifunction devices) 131 and 132 are installed.

[0067] The diagnosis type column indicates the type of diagnosis content, and a diagnosis item for determining whether the user's hardware usage is good or bad is the diagnosis type "Hard". A diagnosis item for determining whether the user's software usage is good or bad is the diagnosis type "Soft". Furthermore, a diagnosis item for determining whether the setting environment of the client terminals (multifunction peripherals) 131 and 132 is good or bad is the diagnosis type "Env".

[0068] The model ID column indicates which model ID the diagnostic item ID is for. In this example, even if the item name is the same, if the model ID is different, the item ID will also be different. The diagnostic logic column indicates the file name that describes the calculation processing logic for diagnosing each diagnostic name.

[0069] The file describing this logic is managed by the device information management unit 314, and the file can be updated based on instructions from the system management user to the utilization efficiency diagnostic system 121.

[0070] For example, in a diagnostic logic file, one or more sensor IDs (Table 5) required for calculation are specified, and a history acquisition process is written to acquire history from the sensor information history table (Table 5). For example, an SQL statement is written to acquire history information for a specified sensor ID and period from the DB table in Table 5.

[0071] Furthermore, the diagnostic logic file also contains a formula for calculating diagnostic results from the acquired history information. This formula may be the average value of multiple sensor values ​​from the same sensor ID.

[0072] Also, when the value is "ON" or "OFF" as in the "Sensor Value_2" column in Table 6, the formula may be one that counts the number of times the sensor value transitions from "OFF" to "ON."

[0073] The following is an example of diagnostic processing for a device with device ID "Device001" (Table 4). Since device ID "Device001" has model ID "Model1", diagnosis of all diagnostic items associated with model ID "Model1" in Table 7 is executed.

[0074] For the sake of simplicity, only one of the diagnosis names, "BodyDoorOpen" (Table 7), will be described here. For the diagnosis name "BodyDoorOpen", the processing logic "dxLogic1" is applied.

[0075] The diagnostic logic "dxLogic1" contains an SQL statement that retrieves historical information from the sensor information history (Table 6) by specifying three conditions: user ID, device ID, sensor ID, and reception date and time.

[0076] In this case, the condition specification for the sensor ID is written in the diagnostic logic "dxLogic1" so that "sensor2" (Table 5) is the fixed condition specification. The remaining condition specifications are variable input values ​​depending on the user ID, device ID, and diagnosis execution date.

[0077] In this example, the conditions are specified as "userA" for the user ID, "Device001" for the device ID, and "2023 / 3 / 14" for the reception date and time. At this time, two records that match the conditions are retrieved from the sensor information history (Table 6).

[0078] If these two records are sorted in chronological order by the received date and time column, the values ​​in the sensor value_2 column will be "OFF" and "ON", respectively. In other words, it can be determined that the value of the sensor ID "sensor2" changed from "OFF" to "ON" once.

[0079] This determination process is also described in the diagnostic logic "dxLogic1." Furthermore, the diagnostic logic "dxLogic1" describes a calculation formula for calculating the diagnostic result based on the frequency of occurrence of the value of the sensor ID "sensor2" changing from "OFF" to "ON" in one day. For example, in this embodiment, the diagnostic result is calculated as a five-level numerical value of 0, 1, 2, 3, and 4.

[0080] The calculation formula for the diagnostic logic "dxLogic1" is written so that when the occurrence frequency is less than 5 times, 5 times or more, 10 times or more, 15 times or more, or 20 times or more, the diagnostic results will be 0, 1, 2, 3, or 4, respectively. Therefore, as described above, if it is determined that the number of times the value of the sensor ID "sensor2" changed from "OFF" to "ON" is 1, the diagnostic result will be 0.

[0081] Although one example of a calculation formula described in the diagnostic logic has been explained above, it is assumed that various variations of the calculation formula other than the above can be described in the diagnostic logic.

[0082] The registration / update date column in Table 7 indicates the date and time when a new diagnostic item is registered, the diagnosis name of a registered diagnostic item, the associated model ID, and the update date and time when the diagnostic logic is corrected or updated.

[0083] Table 8 below shows an example of the periodic diagnosis results managed by the device information management unit 314. [Table 8] TIFF2025012553000010.tif113160

[0084] The diagnosis result ID column is an ID that uniquely identifies the diagnosis result. The diagnosis target date column indicates the date to be diagnosed. Furthermore, the diagnosis execution date column indicates the date and time when the diagnosis was performed. In this embodiment, the periodic diagnosis result is determined by performing the diagnosis process for the previous day at 00:05 every day, for example.

[0085] If you want to obtain diagnostic results on a daily basis, you can use the record information for that day as the diagnostic result. If you want to obtain diagnostic results on a monthly basis, you can obtain the record information for that month and calculate the average value of the diagnostic results to obtain the diagnostic result value for that month.

[0086] In this example, the periodic diagnosis result is shown at one-day intervals, but the diagnosis interval for the periodic diagnosis result may be a specified time interval. The user ID column indicates which user the diagnosis result is for.

[0087] Here, in the case of a diagnosis result calculated based on history information (Table 5) issued in a state where no user is currently logged in to the client terminal (multifunction device) 131, 132, the user ID column will be left blank.

[0088] The Device ID column indicates which device the diagnosis result is for. The Item ID_1 column indicates which diagnosis item ID (Table 7) the diagnosis result is for, and the Result_1 column shows the diagnosis result.

[0089] Then, each diagnostic item ID (Table 7) and its diagnostic result are stored in order from "Item ID_2 column and Result_2 column" to "Item ID_N column and Result_N column". In this embodiment, the diagnostic result indicates the degree of goodness or badness of the diagnostic item with a five-level value of 0, 1, 2, 3, and 4.

[0090] In this embodiment, the quality is shown in a 5-level scale, but it may be shown in other levels, such as 3 levels or 8 levels. Also, the value of the diagnosis result does not have to be a numerical value as long as the information indicates the degree of quality.

[0091] Table 9 below shows an example of the immediate periodic diagnosis results managed by the device information management unit 314. [Table 9]

[0092] The columns for the diagnosis result ID column, diagnosis execution date and time column, user ID column, result_1 column, and "item ID_2 column and result_2 column" to "item ID_N column and result_N column" are the same as those in Table 8. The diagnosis interval column indicates the time interval that is the target of real-time diagnosis processing.

[0093] For example, in Table 9, if the diagnosis execution date and time is "2023 / 3 / 14, 15:03", the sensor information is obtained from the sensor information history (Table 6) for the date and time section up to 5 minutes before this diagnosis execution date and time.

[0094] Specifically, this date and time interval is "2023 / 3 / 14, 14:58" to "2023 / 3 / 14, 15:03". Then, a diagnosis is performed on the sensor information history (Table 6) for this date and time interval, and the result is stored in the real-time diagnosis result table (Table 8). This real-time diagnosis may be performed every time history information of the sensor information history (Table 6) is received from the client terminals (multifunction devices) 131 and 132.

[0095] Alternatively, a diagnosis request may be sent from the client terminals (multifunction peripherals) 131, 132 in response to a specific user instruction or operation on the client terminals (multifunction peripherals) 131, 132 or a change in the state of the client terminals (multifunction peripherals) 131, 132. Furthermore, the diagnosis logic used for calculating this immediate diagnosis result may be different from the diagnosis logic used for calculating the periodic diagnosis result, even if the diagnosis item name is the same.

[0096] The periodic diagnosis result (Table 8) is used to display the diagnosis result summary for a period that is repeated periodically, such as daily or monthly. The immediate diagnosis result (Table 4) is mainly used to feed back the diagnosis result to the client terminals (multifunction devices) 131 and 132 that are in operation at time intervals close to real time.

[0097] The client terminals (multifunction devices) 131, 132 that have received the immediate diagnostic results (Table 4) can inform the user by turning on or off an LED lamp if the diagnostic results become worse than the default.

[0098] Next, a description will be given of the functional blocks of the client terminals (multifunction peripherals) 131 and 132. The client terminals (multifunction peripherals) 131 and 132 each include a data communication unit 321, a display unit 322, a login unit 323, a job control unit 324, a sensor management unit 325, and a local device information management unit 326.

[0099] The display unit 322 displays a screen for the user to give instructions to the client terminals (multifunction peripherals) 131, 132 via the operation unit 204, a screen for displaying information (Tables 1 to 9) obtained from the utilization efficiency diagnostic system 121, and the like.

[0100] The display unit 322 also lights or blinks an LED lamp as feedback of the diagnosis result at time intervals close to real time based on the diagnosis result (Table 9) included in the device information. The login unit 323 transmits the user name and password entered by an input device connected to the interface 208 to the login processing unit 313 for authentication.

[0101] The authentication may be performed by facial recognition using a face image captured by a camera using an input device, or by iris recognition using an iris.Fingerprint authentication may also be performed by using a fingerprint sensor using an input device.The local device information management unit 326 stores and manages the device information (Tables 3 to 9) acquired from the utilization efficiency diagnostic system 121 via the data communication unit 321 on the client terminals (multifunction devices) 131 and 132.

[0102] In addition, when there is a change in the user operation or environmental information of the client terminals (multifunction peripherals) 131 and 132, the local device information management unit 326 immediately or periodically transmits updated device information to the device information management unit 314 via the data communication unit 321.

[0103] A login unit 323 transmits a user name and a password inputted by an input device connected to the operation unit 204 or the interface 208 to a login processing unit 313. A job control unit 324 controls jobs that execute various functions such as a copy function, a scan function, a print function, and a FAX function that the client terminals (multifunction devices) 131 and 132 have.

[0104] For example, when the display unit 322 receives an instruction to execute a copy function by inputting from a touch panel (operation unit 204) or the like, the instruction is transmitted to the job control unit 324, which controls the start, stop, and end of a copy execution job. Also, when an instruction to execute a print function is received from a client terminal (information terminal) 133 or the like via the data communication unit 321, the job control unit 324 temporarily stores print data and controls print execution.

[0105] The sensor management unit 325 can acquire sensor information of peripheral devices (not shown) (such as a finisher, a cassette deck, and a USB memory) connected to the client terminals (multifunction peripherals) 131 and 132 via the interface 208, and attachment / detachment information of these peripheral devices.

[0106] The sensor information of the peripheral devices is, for example, information on the opening and closing of a finisher or a cassette deck, the presence or absence of paper (including paper jams during paper transport), the ON / OFF state of a power button, etc. The sensor management unit 325 can also acquire various types of sensor information provided inside the operation unit 204, the printer 206, and the scanner 207.

[0107] The above-mentioned various sensor information including peripheral device information acquired by the sensor management unit 325 is called sensing information. Furthermore, the sensor management unit 325 can acquire logs related to specific user operations, such as a log of a user pressing a button on the display panel of the operation unit 204, from the operation unit 204, the printer 206, the scanner 207, and the interface 208.

[0108] These acquired logs can then be analyzed, converted into sensing information, and saved. For example, based on a log of a user pressing down on the display panel of the operation unit 204, it can be determined that the user is repeatedly tapping the display panel, and this can be converted into sensing information of the detection of repeated taps and saved.

[0109] Next, a description will be given of the software configuration of the client terminal (information terminal) 133. The client terminal (information terminal) 133 includes a data communication unit 331, a display unit 332, a login unit 333, and a device information management unit 334.

[0110] The display unit 332 displays a screen for the user to give instructions to the client terminal (information terminal) 133 via the operation unit 214, a screen for displaying information (Tables 1 to 9) obtained from the utilization performance diagnostic system 121, and the like.

[0111] The login unit 333 transmits the user name and password inputted by an input device connected to the interface 216 to the login processing unit 313 for authentication. Note that the authentication may be performed by using a camera as the input device and performing face authentication based on a face image captured by the camera, or iris authentication based on the iris.

[0112] Moreover, the input device may be a fingerprint sensor for fingerprint authentication. The device information management unit 334 stores and manages the device information (Tables 3 to 9) and the like acquired from the utilization performance diagnostic system 121 via the data communication unit 331 on the client terminal (information terminal) 133. The login unit 333 transmits the user name and password entered by the input device connected to the operation unit 214 or the interface 216 to the login processing unit 313.

[0113] 4 is a diagram showing an example of a main menu screen displayed when a user logs in on the UI operation panel of the client terminal (multifunction device) according to the first embodiment, and is an image of the operation unit 204 of the client terminals (multifunction devices) 131 and 132. On the operation unit 204, a touch panel display screen 401 and LED lamps (411 to 414) are provided.

[0114] A main menu screen is displayed on the display screen 401 immediately after the user logs in to the client terminal (multifunction device) 131, 132, and includes function icons for executing various functions such as copying and faxing. Furthermore, on the left side of the main menu screen, there is a display area for submenus.

[0115] This submenu includes items for displaying a login user information screen, a main menu screen, a custom menu screen that displays function icons (not shown) that the user has set for each function (e.g., double-sided reading setting for the copy function), etc. Furthermore, this submenu also includes a utilization degree item (402) for displaying a utilization degree screen that displays the utilization degree of the device itself (client terminals (multifunction devices) 131, 132).

[0116] The main power lamp 411 lights up when the power of the client terminals (multifunction devices) 131, 132 is on. The error lamp 412 lights up or blinks when an error such as a paper jam occurs. The execution memory lamp 413 blinks while the client terminals (multifunction devices) 131, 132 are in operation such as communicating or printing, and lights up when there is data waiting to be processed.

[0117] The availability lamp 414 as a real-time display unit lights up or blinks when the availability diagnostic result for the client terminals (multifunction peripherals) 131 and 132 is displayed, or when a user operation or an environmental change that may worsen the diagnostic result is detected.

[0118] For example, if the periodic diagnosis result (Table 8) of the logged-in user is poor (eg, the average value of the diagnosis results for each diagnosis result item is less than a predetermined value), the utilization favorability lamp 414 is lit in red while the user is logged in.

[0119] On the other hand, if the result is good, the utilization goodness lamp 405 may be lit green. Furthermore, if a user operation or an environmental change that may worsen the diagnosis result is detected, the utilization goodness lamp 414 is made to flash red.

[0120] For example, user operations that deteriorate the diagnosis result include actions such as repeatedly tapping the display screen 401, opening the door several times within one minute, etc. Furthermore, environmental changes that deteriorate the diagnosis result include, for example, shaking during operation of the client terminals (multifunction peripherals) 131, 132 (earthquakes or moving while operating), and temperature differences between the inside and outside of the client terminals (multifunction peripherals) 131, 132 that cause condensation, etc.

[0121] In this embodiment, the detection of user operations or environmental changes that may worsen the diagnostic results is performed by defining diagnostic logic corresponding to the diagnostic items (Table 9) and detecting them as immediate diagnostic results (Table 9), but other means may also be used.

[0122] Fig. 5 is a diagram showing an example of a display of a utilization degree (overall evaluation) on a UI operation panel of a client terminal (multifunction device) according to Example 1. Fig. 5 shows an example of a utilization degree screen transitioned to by pressing a utilization degree item 402 on a submenu on a display screen 401 in Fig. 4. Fig. 5 explains an operation for narrowing down display conditions on the utilization degree screen.

[0123] The utilization favorability screen shown in Fig. 5 has buttons for displaying the diagnostic results of Overall Evaluation 501, Utilization (Hardware) 502, Utilization (Software) 503, and Environment 504. Fig. 5 shows the button state in which Overall Evaluation 501 has been pressed and is enabled for display.

[0124] The overall evaluation 501 displays the overall result of the diagnostic results (Tables 8 and 9) of all diagnostic items (Table 7) of the own device (client terminal (multifunction device) 131, 132) for the own device. For example, it may be the average value of the diagnostic results of all diagnostic items, or a single diagnostic result value may be calculated by adding a predetermined weight to the values ​​of the diagnostic results of all diagnostic items.

[0125] In addition, in this embodiment, the process for calculating the diagnostic result of this overall evaluation 501 is incorporated into the processing program of the device information management unit 314 of the utilization performance diagnostic system 121, but other means may be used.

[0126] For example, a method may be used in which a "diagnosis item for calculating the overall evaluation" is defined separately as one item among all the diagnosis items (Table 7), and a file describing the calculation formula, such as the aforementioned average calculation or weighted addition, is linked to the diagnosis logic column.

[0127] Similarly, the calculation of the diagnostic results for Usage (Hardware) 502, Usage (Software) 503, and Environment 504, which will be described later, may be incorporated into the processing program of the device information management unit 314, or a means for separately defining it as one item of all diagnostic items (Table 7) may be used.

[0128] Usage (hardware) 502 displays each diagnostic result (Table 8, Table 9) of diagnostic items with a diagnostic type of "Hard" out of all diagnostic items (Table 7) described above, and their overall results. Usage (software) 503 displays each diagnostic result (Table 8, Table 9) of diagnostic items with a diagnostic type of "Soft" out of all diagnostic items (Table 7) described above, and their overall results.

[0129] Environment 504 displays each diagnosis result (Table 8, Table 9) of the diagnosis item whose diagnosis type is "Env" among all the above-mentioned diagnosis items (Table 7) and their overall result. The target user pull-down 505 is used to select whether to display the utilization degree of only the logged-in user, the department to which the logged-in user belongs, or the whole (all users) when displaying the utilization degree (the overall evaluation result in FIG. 5).

[0130] In the example of the target user pull-down 505, the pull-down items of individual, department, and whole are displayed. The aggregation period unit pull-down 506 is used to conditionally select the unit of the aggregation period of the diagnosis results. In the example of the aggregation period unit pull-down 506, the pull-down items of daily, weekly, monthly, annual, and entire period are displayed.

[0131] For example, as shown in Table 8, when the diagnostic results are output for a one-day period, the results can be output as is for days. In addition, for weekly or monthly periods, the average value of the diagnostic results for seven days can be used as the weekly diagnostic result, and the average value of the diagnostic results for one month can be used as the monthly diagnostic result.

[0132] Alternatively, diagnostic items for calculating weekly and monthly diagnostic results may be provided in the diagnostic items (Table 7), and these may be output daily in the periodic diagnostic results (Table 8). In this case, the start date and end date of the one-week or one-month period to be compiled are entered in the diagnostic target date column in Table 8.

[0133] In addition, when the pull-down menu 506 for the aggregation period unit is selected, the device (131, 132) may request the utilization goodness diagnostic system 121 to output the diagnostic result for the selected period unit, and output it to the immediate diagnostic result (Table 9). In this case, the diagnostic interval in Table 9 may be a period such as one week or one month.

[0134] In this manner, when the target user pull-down 505 and the aggregation period unit pull-down 506 are selected with the overall rating 501 selected, the result of the utilization goodness is displayed as shown in Fig. 6. Fig. 6 is a diagram showing a display example when the overall rating 501 is selected in Fig. 5, and further, "individual" is selected in the target user pull-down 505 and "monthly" is selected in the aggregation period unit pull-down 506.

[0135] In Fig. 6, for example, the current month's tally results (511) and previous month's tally results (514) are displayed and compared. At this time, for this month's data, the history (Table 6) is added daily, so each time the utilization rate is displayed, the average value of this month's diagnostic results is calculated from the diagnostic results (Tables 8 and 9) based on the current month's history (Table 6). Then, the calculated diagnostic results (511, 514) for this month and previous month are displayed in graphs (512, 515).

[0136] In graphs 512 and 513, the shorter the bar in the graph, the worse the utilization degree, and the longer the bar, the better the utilization degree. Also, as mentioned above, when the diagnosis result is shown on a five-level scale (0 to 4), the length of the bar is displayed according to the numerical value. In FIG. 6, the bar in graph 512 for this month is longer than the center, indicating that the utilization degree is relatively good.

[0137] Also, the bar 515 for the previous month is long enough to reach the middle, indicating that the usage level is neither good nor bad and is normal. Furthermore, the usage level screen ranks the usage levels of users of the device (131, 132) and indicates the ranking (diagnosis result) of the logged-in user among all users.

[0138] In Figure 6, it is shown that out of 30 users, this month's usage rating is 5th (513), and last month's usage rating was 15th (516). In addition, the usage rating screen can also show how much the usage rating and ranking have improved (Up), worsened (Down), or remained the same (Keep). In Figure 6, it shows that the usage rating has increased by 25% (517), and the ranking has increased by 10 places (518).

[0139] FIG. 7 is a diagram showing a display example when the overall evaluation 501 is selected in FIG. 5, and further, "department" is selected in the target user pull-down menu 505 and "yearly" is selected in the aggregation period unit pull-down menu 506.

[0140] In this case, for example, the results of the current year (521) and the results of the previous year (524) are displayed for comparison. At this time, since the history (Table 6) for this year is added daily, the average value of the diagnosis results for this year is calculated from the diagnosis results (Tables 8 and 9) every time the utilization degree is displayed based on the current history (Table 6) for this year.

[0141] The calculated diagnostic results (521, 524) for this year and last year are then displayed in graphs (522, 525) in the same manner as in Fig. 6. In Fig. 7, the bars 522 and 525 reach the middle in both cases, indicating that the degree of utilization is neither good nor bad, and is normal.

[0142] Furthermore, the ranking display of the usage goodness of the usage department of this device (131, 132) shows the ranking (diagnosis result) of the usage goodness (diagnosis result) of the logged-in user's department among all departments. In FIG. 7, it shows that out of five usage departments, the usage goodness is fifth this year (523), and third last year (526).

[0143] Furthermore, it shows that the utilization rate has not changed (527) and the ranking has dropped by two places (528). In Fig. 6 and Fig. 7, the case where "individual" or "department" is selected in the target user pull-down 505 has been explained, but when "all" is selected, there is no comparison with other users or other departments, so in this case, the ranking is not displayed.

[0144] Also, when "all period" is selected in the pull-down menu 506 for the aggregation period unit, since there is no comparison such as last month vs. this month or last year vs. this year, only a bar graph showing the diagnosis results for the entire period is displayed.

[0145] Fig. 8 is a diagram showing an example of a display screen relating to the hardware utilization advantage degree when Usage (Hardware) 502 is selected on the UI operation panel of the client terminal (multifunction machine) according to Example 1. In Fig. 8, it is assumed that "Individual" is selected in the target user pull-down 505 and "Monthly" is selected in the aggregation period unit pull-down 506.

[0146] An overall result 601 regarding the degree of goodness of hardware utilization is displayed at the top of the screen, with a bar 602 showing the diagnosis result for this month displayed above the horizontal line of the graph, and a bar 603 showing the diagnosis result for the previous month displayed below the graph.

[0147] The ranking order for the previous month and this month is displayed as shown in 604, and the degree to which the degree of quality and ranking have increased or decreased (or remained the same) is also displayed in 605 and 606. Furthermore, the diagnostic results for each diagnostic item (items with the diagnostic type "Hard" in Table 7) used to calculate the overall result 601 of utilization (hard) are also displayed in the same manner using a graph in 607 at the bottom of the screen.

[0148] 9 is a diagram showing an example of a display screen relating to the software utilization advantage when USE (software) 503 is selected on the UI operation panel of the client terminal (multifunction device) according to Example 1. An overall result 611 relating to the software utilization advantage is displayed at the top of the screen, and a bar 612 of the diagnosis result for this month is displayed above the horizontal line of the graph, and a bar 613 of the diagnosis result for the previous month is displayed below the graph.

[0149] In addition, the ranking position for the previous month and this month is displayed as 614, and the degree to which the goodness and ranking have improved or fallen (or remained the same) is also displayed as 615 and 616, respectively.

[0150] Furthermore, the diagnostic results of each diagnostic item (items with a diagnostic type of "Soft" in Table 7) used to calculate the overall usage (software) result 611 are also displayed in the form of a graph at the bottom of the screen 617. In this manner, in this embodiment, when diagnosing the device usage by the user, at least one of the hardware utilization degree related to the physical handling of the device and the software utilization degree related to the handling related to the software operation of the device is output (displayed).

[0151] 10 is a diagram showing an example of a utilization favorability screen when environment 504 is selected on the UI operation panel of the client terminal (multifunction device) according to Example 1. An overall result 621 of the environment is displayed at the top of the screen, and a bar 622 of the diagnosis result for the current month is displayed above the horizontal line of the graph, and a bar 623 of the diagnosis result for the previous month is displayed below the graph.

[0152] Also, the extent to which the degree of goodness has increased or decreased (or remained unchanged) is displayed in 624. Furthermore, in the lower part of the screen 625, the diagnostic results of each item (items with the diagnostic type "Env" in Table 7) used in calculating the overall result 621 of the environment are also displayed in the same manner using a graph.

[0153] However, since the environment 504 does not affect the user's own operations, it is assumed in this embodiment that diagnosis and display of diagnosis results will not be limited to the logged-in user or the department to which the user belongs. Therefore, in Fig. 10 which is an explanatory diagram of the screen when the environment 504 is selected, the target user pull-down menu 505 is not displayed.

[0154] 10, the diagnostic results are displayed under the same conditions as when "All" is selected in the target user pull-down menu 505. Also, since there is no comparison with other users or other departments, rankings are not displayed in FIG.

[0155] Fig. 11 is a diagram showing a display example of a screen for selecting a method for counting utilization goodness on a Web portal screen of a client terminal (information terminal) according to Example 1. Fig. 12 is a diagram showing another display example of a screen for selecting a method for counting utilization goodness on a Web portal screen of a client terminal (information terminal) according to Example 1.

[0156] The utilization degree screen on the client terminal (information terminal) 133 displays utilization degrees for multiple devices (same model or all devices) in addition to the utilization degree for one device as shown in FIGS. 8 to 10.

[0157] FIG. 11 shows an example of the top screen of the utilization rate screen. The left side of the screen is a sub-menu, which displays menu items related to device information 701 and logged-in user information 702.

[0158] The device information 701 includes a utilization degree item 703, and pressing the utilization degree item 703 transitions to a utilization degree screen. The top screen of the utilization degree screen displays a screen for specifying a counting method for tallying and displaying utilization degrees (diagnosis results of utilization degrees) of multiple users or multiple devices. In Fig. 11, two counting methods, tallying method 1 and tallying method 2, are specified.

[0159] First, in tabulation method 1, either "per selection" 704 or "average selection" 705 is selected by radio button. When "per selection" 704 is selected, it is possible to display the utilization goodness for each user and each department. On the other hand, when "average selection" 705 is selected, the average utilization goodness for multiple users or multiple departments is displayed.

[0160] In 706 to 708, the user or department to be used for display or average calculation in each selection 704 or selection average 705 is searched for and displayed in a list in 709. In the pull-down 706, the user selects whether to search by user ID, department ID, or entirety, as shown in Fig. 12. Fig. 12 is a diagram showing an example of the display when selecting an item in Fig. 11.

[0161] When a character string is input in 707 and a search button 708 is pressed, a partial match search is performed for the item selected in 706 with the character string input in 707, and the results are displayed in a list in 709. If no input is made in 707 and the search button 708 is pressed, all selected items in the pull-down menu 706 are displayed in a list in 709.

[0162] In addition, by turning on / off check boxes provided in the search result list 709, it is possible to further limit and select the user IDs and departments for which the utilization degree is to be displayed.

[0163] Next, in the aggregation method 2, either "per selection" 710 or "average selection" 711 is selected by using a radio button. When "per selection" 710 is selected, it is possible to display the degree of utilization for each device and model.

[0164] On the other hand, when the selection average 711 is selected, the average utilization degree of a plurality of devices or a plurality of models is displayed. In 712 to 714, the devices or models used for display or average calculation in each selection 710 or selection average 711 are searched for and displayed in a list in 715.

[0165] In the pull-down menu 712, the user can select whether to search by device ID, model, or all devices, as shown in Fig. 12. Then, when the user enters a character string in 713 and presses a search button 714, the results are displayed in a list in 715.

[0166] If the user presses the search button 714 without inputting anything in 713, all the selection items in the pull-down menu 712 are displayed in a list in 715. Also, by turning on / off the check boxes in the search result list 715, the user can further select a part of the device IDs and models of the utilization goodness that the user wishes to display.

[0167] By specifying tallying methods 1 and 2 as described above and pressing the report output button 716, it is possible to output a report (file output) of information on the utilization goodness using the specified tallying method. In addition, by pressing the display button 717, the screen transitions to Fig. 13 or Fig. 14, where the utilization goodness is displayed using the specified tallying method.

[0168] Fig. 13 is a diagram showing an example of display of the degree of favorable use (overall evaluation) on the Web portal screen of the client terminal (information terminal) according to the embodiment 1. Fig. 14 is a diagram showing an example of pull-down items of the pull-down 811 in Fig. 13. In Fig. 13, selection buttons for displaying each diagnosis result of overall evaluation 801, use (hardware) 802, use (software) 803, and environment 804 are provided at the top of the screen.

[0169] 13, the unit of the aggregation period to be displayed in the graph can be specified using a pull-down menu 811, and the aggregation period can be specified using a specified period 812. In this embodiment, for simplicity, the unit of the aggregation period is specified as "months", and the aggregation period is specified as from "2023 / 1" to "2023 / 12".

[0170] In Fig. 13, overall evaluation 801 is selected, and the overall evaluation of the degree of utilization is displayed in a graph in area 813 on the screen. In this graph example, the horizontal axis represents each month, and the vertical axis represents the degree of utilization, and the degree of utilization for each month is expressed in a line graph, and each line graph corresponds to the user ID selected in counting method 1 in Figs. 11 and 12.

[0171] Fig. 13 shows an example in which three user IDs, UserA, UserB, and UserC, are selected by counting method 1 in Figs. 11 and 12. The line graph of utilization degree indicates the average utilization degree of multiple devices (e.g. DeviceA, DeviceB) selected by the corresponding user ID by counting method 2. The pull-down items of the pull-down 811 can be selected from daily, weekly, monthly, yearly, and all-period items, as shown in Fig. 14.

[0172] Fig. 15 is a diagram showing an example of display of the utilization efficiency (utilization (hardware)) on the Web portal screen of the client terminal (information terminal) according to the first embodiment. In Fig. 15, utilization (hardware) 802 is selected, and the utilization efficiency of utilization (hardware) is displayed. In Fig. 15, the overall result of the utilization efficiency of utilization (hardware) is displayed in a graph in area 901 on the screen in the same display method as area 813 in Fig. 13.

[0173] Moreover, when the scroll bar 902 is scrolled downward, an area 903 in Fig. 16 is displayed. Fig. 16 is a diagram showing an example of the display of the area 903 of the utilization advantage level (utilization (hard)) on the Web portal screen of the client terminal (information terminal) according to the embodiment 1. In this area 903, icons corresponding to each diagnostic item (item of the diagnostic type "Hard" in Table 7) used for calculating the overall result of the utilization advantage level of the utilization (hard) are displayed side by side.

[0174] For example, when the body door open / close icon 904 is pressed, a pop-up screen 910 is displayed as shown in Fig. 17. Fig. 17 is a diagram showing an example of the display when the body door open / close icon 904 in Fig. 16 is pressed, and displays a graph of the utilization degree (diagnosis result) corresponding to the item name "BodyDoorOpen" in Table 7.

[0175] The pop-up screen 910 displays a pull-down menu 911 and a specified period 912, which are equivalent to the pull-down menu 811 and the specified period 812, and allows the user to specify the unit of the aggregation period to be displayed in the graph and the period to be aggregated. In addition, an area 913 displays the utilization degree corresponding to the above-mentioned item name "BodyDoorOpen" in a graph in the same manner as the area 813 in FIG. 13.

[0176] Fig. 18 is a diagram showing an example of display of the utilization advantage (utilization (software)) on the Web portal screen of the client terminal (information terminal) according to the embodiment 1. In Fig. 18, utilization (software) 803 is selected, and the overall utilization advantage result of utilization (software) is displayed in a graph in an area 1001 on the screen in the same manner as in area 813 in Fig. 13.

[0177] Moreover, when the scroll bar 902 is scrolled downward, an area 1002 in Fig. 19 is displayed. Fig. 19 is a diagram showing an example of the display of the area 1002 of the utilization goodness level (utilization (software)) on the Web portal screen of the client terminal (information terminal) according to the embodiment 1. In this area 1002, icons corresponding to each diagnostic item (item of diagnostic type "Soft" in Table 7) used for calculating the overall result of the utilization goodness level of utilization (software) are displayed side by side.

[0178] For example, when the power OFF icon 1003 during job execution is pressed, a pop-up screen 1010 is displayed as shown in Fig. 20. Fig. 20 is a diagram showing an example of the display when the power OFF icon 1003 during job execution in Fig. 19 is pressed, and displays a graph of the utilization favorability (diagnosis result) corresponding to the item name "PowerOffInJobRunning" in Table 7.

[0179] A pop-up screen 1010 displays a pull-down menu 1011 and a specified period 1012, which are equivalent to the pull-down menu 811 and the specified period 812, and allows the user to specify the unit of the aggregation period to be displayed in the graph and the period to be aggregated. Also, an area 1013 displays the utilization degree corresponding to the above-mentioned item name "PowerOffInJobRunning" in a graph in the same manner as the area 813 in FIG.

[0180] Fig. 21 is a diagram showing an example of display of the utilization degree (environment) on the Web portal screen of the client terminal (information terminal) according to Example 1. In Fig. 21, environment 804 is selected, and the overall result of the utilization degree of the environment is displayed in a graph in an area 1101 on the screen in the same manner as in area 813 in Fig. 13.

[0181] Moreover, when the scroll bar 902 is scrolled downward, an area 1102 in Fig. 22 is displayed. Fig. 22 is a diagram showing an example of the display of the area 1102 of the utilization degree (environment) on the Web portal screen of the client terminal (information terminal) according to the embodiment 1. In this area 1102, icons corresponding to each diagnostic item (item of the diagnostic type "Env" in Table 7) used for calculating the overall result of the utilization degree of the environment are displayed side by side.

[0182] For example, when the temperature icon 1103 is pressed, a pop-up screen 1110 is displayed as shown in Fig. 23. Fig. 23 is a diagram showing an example of the display when the temperature icon 1103 in Fig. 22 is pressed, and displays a graph of the utilization favorability (diagnosis result) corresponding to the item name "BodyDoorOpen" in Table 7.

[0183] A pop-up screen 1110 displays a pull-down menu 1111 and a specified period 1112 equivalent to the pull-down menu 811 and the specified period 812, and allows the user to specify the unit of the aggregation period to be displayed in the graph and the period to be aggregated. Also, an area 1113 displays the utilization degree corresponding to the above-mentioned item name "Temperature" in a graph in the same manner as the area 813 in FIG. 13.

[0184] FIG. 24 is a process flowchart for making a “diagnosis request” and a “diagnosis result acquisition” from the client terminals (multifunction devices / information terminals) to the utilization diagnostic system in the first embodiment, and is the process of the client terminals (multifunction devices) 131 and 132.

[0185] The operations of the steps in the flowchart of FIG. 24 are performed in sequence by a CPU or the like serving as a computer in the client terminals 131 and 132 executing a computer program stored in a memory.

[0186] In step S1201, the CPU of the client terminal (multifunction device) acquires sensing information of the device via the sensor management unit 325. At this time, step S1201 functions as a device information acquisition step (device information acquisition unit) that acquires information regarding at least one of the device operation, device settings, and device placement environment.

[0187] Then, in step S1202, it is determined whether there is a change in the sensing information. If the answer is Yes in step S1201, the process proceeds to step S1203, where the CPU of the client terminal (multifunction device) transmits a request for diagnosis of the utilization degree to the utilization degree diagnosis system 121 via the data communication unit 321.

[0188] At this time, the device sensing information acquired in step S1201 is included in the request information at the time of the diagnosis request as sensor information (information equivalent to one record in Table 6). On the other hand, if there is no change in the sensing information in step S1202 (No), the process proceeds to step S1207.

[0189] After transmitting the diagnosis request in step S1203, the CPU of the client terminal (multifunction device) transmits a request to obtain the diagnosis result of the utilization degree to the utilization degree diagnosis system 121 via the data communication unit 321 in step S1204.

[0190] In step S1204, for example, a request is made to acquire only the diagnostic result items of the utilization degree to be displayed on the real-time display unit (utilization degree lamp 414, etc.), and the request includes information on the relevant items.

[0191] Then, in step S1205, the CPU of the client terminal (multifunction device) determines whether or not a response has been received from the utilization degree diagnosis system 121, and if a response has not been received (if No), the process returns to step S1205. If a response has been received (if Yes), in step S1206, the real-time display unit (utilization degree lamp 414, etc.) is caused to reflect (display) the diagnosis result.

[0192] Next, the CPU of the client terminal (multifunction device) determines in step S1207 whether or not a user has instructed to display a utilization degree screen (diagnosis result screen). This display instruction is executed when the user presses the utilization degree item 402 in Fig. 4 to Fig. 10, or when the pull-down menu 505 or the pull-down menu 506 is changed in Fig. 5 to Fig. 10.

[0193] If it is determined in step S1207 that a display instruction has been issued, the CPU of the client terminal (multifunction device) in step S1208 transmits a request to acquire the utilization efficiency diagnostic results to the utilization efficiency diagnostic system 121 via the data communication unit 321. Here, in step S1208, a request is made to acquire only the utilization efficiency diagnostic result items displayed on the display screens of Figures 5 to 10, and information on the relevant items is included in the request for acquisition.

[0194] Then, in step S1209, the CPU of the client terminal (multifunction device) determines whether or not a response has been received in the utilization degree diagnostic system 121. If no response has been received in step S1209 (No), the process returns to step S1209.

[0195] On the other hand, if a response has been received (Yes), in step S1210, the CPU of the client terminal (multifunction device) reflects the diagnosis result on the utilization degree screen (FIGS. 5 to 10), and ends the flow of FIG.

[0196] Here, step S1206 and step S1210 function as a diagnostic result output step (diagnosis result output unit) that outputs the diagnosis result by the utilization degree diagnosis step (utilization degree diagnosis unit). Also, the diagnostic result output step (diagnosis result output unit) displays the utilization degree lamp 414 or at least one of the utilization degree screens such as a UI panel.

[0197] If there is no display instruction in step S1207 (No), the CPU of the client terminal (multifunction device) ends the flow of Fig. 24. The process flow of Fig. 24 may be executed periodically or at the user login timing.

[0198] For example, when there is no logged-in user, it may be executed periodically at intervals of one hour to one day, and when any user is logged in, it may be executed periodically at one-minute intervals at login, logout, and while logged in.

[0199] Fig. 25 is a flowchart showing an example of processing of the utilization goodness diagnostic system 121 according to Fig. 24. Note that the operation of each step of the flowchart in Fig. 25 is performed sequentially by a CPU or the like as a computer in the utilization goodness diagnostic system 121 executing a computer program stored in a memory.

[0200] The CPU of the utilization efficiency diagnostic system 121 checks in step S1211 whether a utilization efficiency diagnostic request has been received from the client terminals (multifunction devices) 131, 132, and if a diagnostic request has been received (Yes), it diagnoses the utilization efficiency in step S1212.

[0201] In step S1212, the CPU of the utilization efficiency diagnostic system 121 receives and acquires the sensor information transmitted in step S1203, and stores the sensor information in the sensor information history (Table 6) via the device information management unit 314.

[0202] Furthermore, in step S1212, the CPU of the utilization efficiency diagnostic system 121 identifies the models of the client terminals (multifunction peripherals) 131 and 132 from Table 4, then diagnoses the utilization efficiency using the sensor information history (Table 6) and calculates the diagnostic results (Tables 8 and 9).

[0203] At this time, step S1212 functions as a utilization efficiency diagnosis step (utilization efficiency diagnosis unit) that diagnoses the utilization efficiency of at least one of the device utilization status by the user and the device installation environment based on the information acquired by the device information acquisition unit.

[0204] Then, in step S1213, the CPU of utilization efficiency diagnostic system 121 stores the calculated diagnostic results (Tables 8 and 9) via device information management unit 314. Then, in step S1214, the CPU of utilization efficiency diagnostic system 121 responds to the client terminal (multifunction device) that sent the diagnostic request to notify it of completion of receipt of the diagnostic request, and ends the process.

[0205] If the diagnosis request has not been received in step S1211 (if No), the process proceeds to step S1215, where the CPU of utilization efficiency diagnostic system 121 determines whether or not a request to obtain a diagnosis result has been received. If the request to obtain a diagnosis result has been received (if Yes), the result is obtained from the diagnosis result (Tables 8 and 9) via device information management unit 314 in step S1216.

[0206] Then, in step S1217, the CPU of the utilization efficiency diagnostic system 121 responds with the acquired diagnostic result to the client terminal (multifunction device) that sent the request to acquire the diagnostic result, and ends the flow of Fig. 25. If the request to acquire the diagnostic result has not been received in step S1215 (No), the flow of Fig. 25 ends. The flow of Fig. 25 is executed periodically, for example.

[0207] Fig. 26 is a flowchart showing an example of processing of the client terminal (information terminal) 133 according to Fig. 24. Note that the operation of each step of the flowchart in Fig. 24 is performed sequentially by a CPU or the like as a computer in the client terminal 133 executing a computer program stored in a memory.

[0208] In step S1221, the CPU of the client terminal (information terminal) 133 determines whether or not a user has instructed to display a utilization favorability screen (diagnosis result screen). This display instruction is executed when the user presses the display button 717 in Fig. 11 and Fig. 12, or when the selection items of the pull-down menus 811, 911, 1011, and 1111 or the designated periods 812, 912, 1012, and 1112 are changed in Fig. 13 to Fig. 23.

[0209] Also, if a display instruction has been given in step S1221 (Yes), in step S1222 the CPU of client terminal (information terminal) 133 transmits a request to acquire the diagnosis results of the utilization degree to utilization goodness diagnostic system 121 via data communication unit 331. Here, in step S1222, a request is made to acquire only the diagnosis result items of the utilization degree displayed on the display screens of Figures 13 to 23, and information on the relevant items is included in the request for acquisition.

[0210] Then, in step S1223, the CPU of client terminal (information terminal) 133 determines whether or not a response (diagnosis result) has been received from utilization degree diagnosis system 121, and if no response has been received (No), returns to step S1223.

[0211] If a response has been received (Yes), in step S1224, the CPU of the client terminal (information terminal) 133 displays the received diagnosis result on the utilization degree screen (FIGS. 13 to 23), and ends the flow of FIG.

[0212] Here, step S1224 also functions as a diagnostic result output step (diagnosis result output unit) that outputs the diagnosis result by the utilization goodness diagnosis step (utilization goodness diagnosis unit). Also, the diagnostic result output step (diagnosis result output unit) displays the result on the display of an information terminal different from the device (client terminals 131 and 132).

[0213] If there is no instruction to display the utilization rate screen in step S1221 (No), the flow in Fig. 26 ends. The flow in Fig. 26 is executed periodically, for example.

[0214] As described above, in the first embodiment, a method for diagnosing the user's usage status of a device (multifunction peripheral, image processing device) and the degree of suitability of the device's placement environment and presenting the diagnosis result to the user has been described. This enables the user of the device to perform operations while being aware of user behavior that accelerates the breakdown and deterioration of the device and its components and of improvements to the placement environment. EXAMPLES

[0215] In the first embodiment, if the diagnosis result of the utilization goodness level presented to the user is provided with a solution to improve the utilization goodness level, the user can take specific action to improve the utilization goodness level. Therefore, in the second embodiment, settings and advice for improving the utilization goodness level are recommended and displayed.

[0216] Fig. 27 is a diagram showing an example of display of the utilization favorability (utilization (software)) on the UI operation panel of the client terminal (multifunction device) according to the embodiment 2. Fig. 27 is a screen equivalent to Fig. 9, and is different from Fig. 9 in that an improvement recommendation button 1301 is provided.

[0217] By pressing this improvement recommendation button 1301, a pop-up screen 1302 is displayed as shown in Fig. 28. Fig. 28 is a diagram showing an example of the pop-up screen 1302 when the improvement recommendation button 1301 in Fig. 27 is pressed.

[0218] Since the use (software) 503 is selected in FIG. 27, the pop-up screen 1302 displays settings and advice for improving the utilization efficiency level for each diagnostic item for the utilization (software) of the utilization efficiency level.

[0219] Here, the pop-up screen 1302 functions as an improvement recommendation display section that displays an improvement method for the diagnosis result by the utilization goodness diagnosis section. Also, as shown in Fig. 28, the improvement recommendation display section displays a message encouraging a predetermined device setting or a message encouraging a predetermined user action.

[0220] When the improvement recommendation button 1301 is pressed, the diagnostic items for which recommendations are displayed include settings and advice for improving the degree of utilization according to the selection of overall evaluation 501, utilization (hardware) 502, utilization (software) 503, and environment 504.

[0221] When Overall Evaluation 501 is selected, improvement recommendations are displayed for all diagnostic items displayed in Use (Hardware) 502, Use (Software) 503, and Environment 504. If the display contents do not fit in the pop-up screen 1302, a scroll bar (not shown) is displayed on the pop-up screen 1302.

[0222] Note that the recommended improvement contents displayed on the pop-up screen 1302 in Fig. 28 are just an example and are not limited to this. For example, an improvement to the diagnostic item of the utilization degree for "power off while a job is being executed" advises to refrain from turning off the power switch or unplugging the power cable while the "execution / memory lamp" that lights up while a job is being executed is on.

[0223] In addition, in an improvement to the diagnostic item "sleep ⇔ sleep return transition," for example, it is assumed that user usage patterns are analyzed and that "the automatic sleep time is set to a short time, such as 5 minutes, and the frequency of sleep return is high."

[0224] In addition, it is also assumed that the analysis shows that once a user uses the client terminal (multifunction device) 131, 132, the user continues to use the device for 50 minutes or less, and that the user rarely continues to use the device for more than 50 minutes. In this case, the improvement plan recommended is to "set the automatic sleep time to 50 minutes."

[0225] For the diagnosis item "Repeated power OFF ⇔ power ON", the analysis results show that the frequency of turning the power switch OFF ⇔ ON is high. For example, if there is a correlation between this and a hard disk failure or a failure of the power switch itself based on past records of failure replacement, a frequency that does not induce failure (e.g., 5 times or less per day) is recommended.

[0226] The "Cleaning Execution" diagnostic item detects the frequency and degree of dirt on parts that are targets for automatic cleaning, for example. If the frequency of cleaning is low, an appropriate frequency for automatic cleaning is recommended based on the above detection information.

[0227] The frequency with which this dirt occurs and the severity of the dirt are expected to vary depending on, for example, how frequently the user uses the printing-related components and document reading components when executing the copy, print, and scan functions.

[0228] Here, we have shown an example of the contents of improvement recommendations for usage (software), but as an example of improvement recommendations for usage (hardware), if there is a correlation between the frequency of opening and closing the main door and door failures based on past records of replacement due to failures, a frequency that does not induce failures will be recommended. Similarly, it is possible to recommend an appropriate range of frequency for repeatedly pressing the UI panel or plugging and unplugging the LAN, based on the correlation between the frequency and past records of replacement due to failures.

[0229] As another example of an improvement recommendation for the environment, if an analysis shows that the temperature is low and condensation is expected, it is possible to recommend turning on the warm-up operation setting of the client terminals (multifunction devices) 131 and 132. Furthermore, if an analysis shows that there is a large amount of dust, it is also possible to recommend moving the client terminals (multifunction devices) 131 and 132 to a clean room.

[0230] Fig. 29 is a diagram showing an example of displaying the utilization favorability (utilization (software)) on the Web portal screen of the client terminal (information terminal) according to the embodiment 2. Fig. 29 is a screen equivalent to Fig. 15, and differs from Fig. 15 in that an improvement recommendation button 1401 is provided.

[0231] By pressing this improvement recommendation button 1401, a pop-up screen 1402 is displayed as shown in Fig. 30. Fig. 30 is a diagram showing an example of the pop-up screen 1402 when the improvement recommendation button 1401 is pressed on the Web portal screen of the client terminal (information terminal) according to the second embodiment.

[0232] Since the use (software) 803 is selected in FIG. 27, the pop-up screen 1402 displays settings and advice for improving the utilization efficiency level for each diagnostic item for the utilization (software) of the utilization efficiency level.

[0233] The diagnostic items for which recommendations are to be displayed when the improvement recommendation button 1401 is pressed are displayed according to the selection of overall evaluation 801, usage (hardware) 802, usage (software) 803, and environment 804. When overall evaluation 801 is selected, improvement recommendations for all diagnostic items displayed in usage (hardware) 802, usage (software) 803, and environment 804 are displayed.

[0234] As shown in FIG. 30, in the improvement recommendation displayed on the pop-up screen 1402, one user is selected from the multiple users displayed in the graph in the area 1001 in FIG. 29 using a pull-down menu 1403, and recommendations for that user are displayed.

[0235] Also, a pull-down menu 1404 is used to select one device from among the multiple devices used in the graph display in area 1001 of Fig. 29, and recommendations for that device are displayed. Fig. 31 is a diagram showing examples of pull-down items when pull-down menus 1404 and 1405 are opened in Fig. 30.

[0236] The pull-down items in Fig. 31 display the multiple users and multiple devices used for the graph display in area 1001 in Fig. 29. Also, the display contents of the improvement recommendations on pop-up screen 1402 in Fig. 30 are the same as those on pop-up screen 1302 in Fig. 28, so a description thereof will be omitted.

[0237] As described above, in the second embodiment, improvement recommendations are presented, and the analysis process for the improvement recommendations is performed by the device information management unit 314. In addition, the analysis logic and the recommendation display content according to the analysis results are included in the diagnosis logic in Table 7.

[0238] In the second embodiment, the process flow when the client terminals (multifunction devices) 131, 132 and the client terminal (information terminal) 133 make a "diagnosis request" and "acquire a diagnosis result" for the utilization degree to the utilization degree diagnosis system 121 is the same as that shown in Fig. 24 to Fig. 26. The difference from the first embodiment is that the information responded in steps S1209, S1214, and S1223 in Fig. 24 to Fig. 26 includes information on improvement recommendations.

[0239] As described above, according to the second embodiment, it is possible to show the user the necessary measures to improve the utilization efficiency level in response to the diagnosis result of the utilization efficiency level presented to the user, and to encourage the user to take concrete improvement actions.

[0240] Although the present invention has been described in detail based on the preferred embodiments, the present invention is not limited to these specific embodiments, and various forms within the scope of the gist of the present invention are also included in the present invention. Parts of the above-mentioned embodiments may be appropriately combined. The present invention also includes the following combinations.

[0241] (Configuration 1) A utilization efficiency diagnostic system comprising: a device information acquisition unit that acquires information regarding at least one of a device operation, a setting of the device, and a placement environment of the device; a utilization efficiency diagnosis unit that diagnoses a utilization efficiency regarding at least one of a user's device usage status and a device installation environment based on the information acquired by the device information acquisition unit; and a diagnosis result output unit that outputs a diagnosis result by the utilization efficiency diagnosis unit.

[0242] (Configuration 2) The utilization efficiency diagnostic system described in Configuration 1, characterized in that when the utilization efficiency diagnostic unit diagnoses the device utilization status by the user, it outputs at least one of a hardware utilization efficiency relating to the physical handling of the device and a software utilization efficiency relating to the handling related to the software operation of the device.

[0243] (Configuration 3) The utilization efficiency diagnostic system according to configuration 1 or 2, characterized in that the diagnostic result output unit displays the result on at least one of a UI panel or a lamp of the device.

[0244] (Configuration 4) The utilization goodness diagnostic system according to any one of configurations 1 to 3, characterized in that the diagnostic result output unit displays the result on a display of an information terminal different from the device.

[0245] (Configuration 5) The utilization goodness diagnostic system according to any one of configurations 1 to 4, further comprising an improvement recommendation display unit that displays an improvement method for the diagnosis result by the utilization goodness diagnostic unit.

[0246] (Configuration 6) The utilization efficiency diagnostic system according to configuration 5, characterized in that the improvement recommendation display unit displays a message encouraging a specified device setting or a message encouraging a specified user action.

[0247] (Method) A utilization efficiency diagnosis method comprising: a device information acquisition step for acquiring information regarding at least one of a device operation, the settings of the device, and the device placement environment; a utilization efficiency diagnosis step for diagnosing utilization efficiency regarding at least one of a user's device usage status and the device installation environment based on the information acquired by the device information acquisition unit; and a diagnosis result output step for outputting the diagnosis result by the utilization efficiency diagnosis unit.

[0248] (Program) A computer program for controlling each part of the utilization efficiency diagnostic system according to any one of configurations 1 to 6 by a computer.

[0249] In order to realize a part or all of the control in the above embodiment, a computer program that realizes the functions of the above embodiment may be supplied to the utilization diagnostic system or the like via a network or various storage media. Then, a computer (or a CPU, MPU, or the like) in the utilization diagnostic system or the like may read and execute the program. In this case, the program and the storage medium storing the program constitute the present invention. [Explanation of symbols]

[0250] 121: Utilization diagnostic system 101: Network 131, 132: Client terminal (multifunction device) 133: Client terminal (information terminal)

Claims

1. a device information acquisition unit that acquires information regarding at least one of an operation of a device, a setting of the device, and an arrangement environment of the device; a utilization efficiency diagnosis unit that diagnoses a utilization efficiency of at least one of a device utilization status by a user and a device installation environment based on the information acquired by the device information acquisition unit; a diagnostic result output unit that outputs a diagnostic result by the utilization degree diagnostic unit; A utilization efficiency diagnostic system comprising:

2. The utilization efficiency diagnostic system described in claim 1, characterized in that when the utilization efficiency diagnostic unit diagnoses the device utilization status by the user, it outputs at least one of a hardware utilization efficiency related to the physical handling of the device and a software utilization efficiency related to the handling related to the software operation of the device.

3. 2. The utilization goodness diagnostic system according to claim 1, wherein the diagnostic result output unit displays the result on at least one of a UI panel or a lamp of the device.

4. 2. The utilization goodness diagnostic system according to claim 1, wherein the diagnostic result output unit displays the result on a display of an information terminal different from the device.

5. 2. The utilization goodness diagnostic system according to claim 1, further comprising an improvement recommendation display unit that displays an improvement method for the diagnosis result by said utilization goodness diagnostic unit.

6. 6. The utilization goodness diagnostic system according to claim 5, wherein the improvement recommendation display unit displays a message encouraging a user to make a predetermined device setting or a message encouraging a user to take a predetermined user action.

7. A device information acquisition step of acquiring information regarding at least one of an operation of a device, a setting of the device, and an environment in which the device is placed; a utilization efficiency diagnosis step of diagnosing a utilization efficiency of at least one of a device utilization status by a user and a device installation environment based on the information acquired by the device information acquisition unit; a diagnostic result output step of outputting a diagnostic result by the utilization degree diagnostic unit; A utilization goodness diagnostic method comprising:

8. A computer program for controlling each part of the utilization goodness diagnostic system according to any one of claims 1 to 6 by a computer.

Images