JP2021103423A - Notification system, browser device, and notification program - Google Patents

Abstract

To make notifications displayed by a browser device more user-friendly.SOLUTION: A server device receives status of an image forming device from the image forming device via a first communication interface, stores it in a first storage device, determines notifications to be sent to a browser device based on the status of the image forming device, and sends notification history data for display including a device ID that identifies the image forming device and the type of notification to the browser device via the first communication interface, the browser device receives the notification history data for display from the server device via a second communication interface, stores it in the second storage device, and based on the notification history data for display, generates a first two-dimensional table that is a two-dimensional table in which a number of notifications of the image formation device identified by the device ID is displayed in a cell at an intersection of the device ID and a type of notification by using a first axis as the device ID and a second axis as the type notification to display the table in a display.SELECTED DRAWING: Figure 5

Description

The present disclosure relates to a notification system including a server device that receives the status of the image forming apparatus and transmits a notification about the image forming apparatus to the browser apparatus, and the browser apparatus. The present disclosure further relates to the browser device. The present disclosure further relates to a notification program executed by the browser device.

A notification system including a server device that receives the status of a plurality of image forming devices and transmits a notification regarding the plurality of image forming devices to the browser device, and the browser device is known. The browser device presents to the user (typically an employee of a sales company or dealer who manages the plurality of image forming devices) by displaying a notification regarding the plurality of image forming devices.

Japanese Unexamined Patent Publication No. 2010-134645 Japanese Unexamined Patent Publication No. 2003-323380 Japanese Unexamined Patent Publication No. 2014-106775 International Publication No. 2008/120338 JP-A-2009-217520

As the number of image forming devices managed by the user increases, the number of notifications displayed by the browser device also increases, which may be complicated for the user. For this reason, the notifications displayed by the browser device should be more user-friendly.

The notification system according to one form of the present disclosure is
A server device that is communicatively connected to the image forming device,
It is equipped with a browser device that is communicatively connected to the server device.
The server device
The first communication interface and
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted to the browser apparatus is determined, and the notification is determined.
It has a device ID for identifying the image forming device and a first control circuit for transmitting display notification history data including the type of notification to the browser device via the first communication interface.
The browser device
The second communication interface and
The second storage device and
Display device and
Operating device and
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell, which is the intersection of the device ID and the notification type, is identified by the device ID. It has a second control circuit that generates a first two-dimensional table, which is a two-dimensional table displaying the number of notifications of the image forming apparatus, and displays the notifications on the display device.

(1) According to the present embodiment, one row is registered for one device ID in the first two-dimensional table. This makes the table less complicated and easier to understand.

The display notification history data further includes a report date.
The second control circuit of the browser device is
Based on the display notification history data, the first axis is the notification type, the second axis is the report date, and the cell at the intersection of the notification type and the report date is in the cell of the report date. A second two-dimensional table, which is a two-dimensional table displaying the number of notifications, is generated and displayed on the display device.

(2) According to the present embodiment, one row is registered for one notification type in the second two-dimensional table. This makes the table less complicated and easier to understand.

The second control circuit of the browser device is
The first two-dimensional table including the first check box for designating the device ID included in the first two-dimensional table is displayed on the display device.
The operation on the first check box of the first two-dimensional table input via the operating device is detected.
A second two-dimensional table for the notification of the image forming apparatus identified by the apparatus ID specified by the manipulated first check box is generated and displayed on the display device.

(3) According to the present embodiment, when there are a large number of notifications for one image forming apparatus, the number of notifications is displayed in a second two-dimensional table having the notification type as the first axis. As a result, the user can perform operations such as deleting and forwarding after grasping the whole picture without checking each notification, so that the notification organizing work is assisted.

The second control circuit of the browser device is
When the type of notification included in the second two-dimensional table for the notification of the image forming apparatus can be displayed in the form of a graph, a graph button is displayed in association with the type of notification.
When the operation for the graph button input via the operating device is detected,
A graph of the type of notification associated with the graph button of the image forming apparatus is displayed on the display device.

(4) According to the present embodiment, the user can grasp the whole picture without checking each notification, display a desired graph, and can grasp the whole picture more efficiently by the graph.

The second control circuit of the browser device is
The display device displays the second two-dimensional table including a second check box for specifying the type of notification included in the second two-dimensional table, and a non-latest delete button. ,
When the operation for the second check box and the non-latest delete button input via the operating device is detected,
The second two-dimensional table is updated and displayed on the display device by deleting the notification history data for display other than the latest predetermined period of the notification type specified by the second check box. ..

(5) According to the present embodiment, the user can flexibly select and collectively operate (collectively delete) a large number of notifications, and it is easy to leave only the latest notification and delete the others.

The second control circuit of the browser device is
The cell with the maximum number of cases in the first two-dimensional table or the second two-dimensional table is highlighted.

(6) According to the present embodiment, the notification contents are classified and the number of notifications is displayed in two dimensions, so that the user can confirm the overall distribution of the notification types and the number of notifications is the maximum value. By highlighting the cells that are, it is easy to pinpoint the distribution of notification types.

The browser device according to one form of the present disclosure is
The first communication interface, which is communicably connected to the image forming apparatus,
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted is determined.
It is possible to communicate with a server device having a first control circuit that transmits display notification history data including a device ID that identifies the image forming device and the notification type via the first communication interface. Connected,
The second communication interface and
The second storage device and
Display device and
Operating device and
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell, which is the intersection of the device ID and the notification type, is identified by the device ID. The image forming apparatus includes a second control circuit that generates a first two-dimensional table, which is a two-dimensional table displaying the number of notifications of the image forming apparatus, and displays the notifications on the display apparatus.

The notification program according to one form of the present disclosure is
The first communication interface, which is communicably connected to the image forming apparatus,
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted is determined.
It is possible to communicate with a server device having a first control circuit that transmits display notification history data including a device ID that identifies the image forming device and the notification type via the first communication interface. Connected,
The second communication interface and
The second storage device and
Display device and
Operating device and
The second control circuit of the browser device having the second control circuit,
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell, which is the intersection of the device ID and the notification type, is identified by the device ID. A first two-dimensional table, which is a two-dimensional table displaying the number of notifications of the image forming apparatus, is generated and operated so as to be displayed on the display apparatus.

According to the present disclosure, in a notification system having a server device that receives the status of a plurality of image forming devices and transmits a notification regarding the plurality of image forming devices to the browser device, and the browser device, the notification displayed by the browser device. Can be made more user-friendly.

The effects described here are not necessarily limited, and may be any of the effects described in the present disclosure.

A notification system according to an embodiment of the present disclosure is shown. The hardware configuration of the image forming apparatus is shown. The hardware configuration of the server device is shown. The hardware configuration of the browser device is shown. Shows the functional configuration of the notification system. An example of notification history is shown. The first operation flow of the server apparatus is shown. An example of display notification history data is shown. The operation flow of the browser device is shown. An example of a one-dimensional screen is shown. The processing flow for generating the first temporary data for display is shown. The processing for generating the first temporary data for display is shown in order. An example of the first two-dimensional screen is shown. The processing flow for generating the second temporary data for display is shown. The processing for generating the second temporary data for display is shown in order. An example of the second two-dimensional screen is shown. The processing flow for additionally displaying the graph button is shown. The graph display table is shown. An example of a second two-dimensional screen including a graph button is shown. An example of the graph is shown. The second operation flow of the server apparatus is shown.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

1. 1. Notification system

FIG. 1 shows a notification system according to an embodiment of the present disclosure.

The notification system 1 is, for example, a web system such as KYOCERA Fleet Services. The notification system 1 has a server device 20 and a browser device 30. The server device 20 and the browser device 30 function as a web server and a web browser. The server device 20 and the browser device 30 are communicably connected via a network N such as the Internet. The server device 20 is communicably connected to the plurality of image forming devices 10 via the network N.

When it is not necessary to distinguish between a plurality of image forming devices 10, a single image forming device 10 will be described and illustrated. The image forming apparatus 10 is typically an MFP (Multifunction Peripheral). The image forming apparatus 10 transmits the status information 130 (FIG. 5) to the server apparatus 20 when an event occurs periodically or suddenly. The status information 130 includes operation information (toner level, page count, etc.) and sudden event information (system error, paper jam, etc.).

The server device 20 receives and stores the status information 130 from the plurality of image forming devices 10. The server device 20 transmits a notification to the browser device 30 by e-mail or the like based on the status information 130 of the plurality of image forming devices 10. When the server device 20 receives a request from the browser device 30 (request for the history of notifications transmitted in the past), the server device 20 uses the display notification history data 120 (FIG. 5) to display the notification history on the browser device 30. ) Is transmitted to the browser device 30. Typically, the server device 20 is a plurality of images associated with a user who logs in to the notification system 1 (typically, an employee of a sales company or a dealer who manages the plurality of image forming devices 10; the same applies hereinafter). The display notification history data 120 relating to the forming device 10 is transmitted to the browser device 30.

The browser device 30 sends a request to the server device 20, and receives the display notification history data 120 from the server device 20. The browser device 30 generates and displays display data based on the display notification history data 120.

2. Hardware configuration of image forming device

FIG. 2 shows the hardware configuration of the image forming apparatus.

The hardware configuration of the image forming apparatus 10 will be described. The image forming apparatus 10 includes a control circuit 100. The control circuit 100 is composed of a CPU 11a (Central Processing Unit) which is a processor, a RAM 11b (Random Access Memory), a ROM 11c (Read Only Memory) which is a memory, a dedicated hardware circuit, and the like, and is an overall image forming apparatus 10. Controls motion control. The CPU 11a loads the information processing program stored in the ROM 11c into the RAM 11b and executes it. The ROM 11c fixedly stores programs, data, and the like executed by the CPU 11a. ROM 11c is an example of a non-transient computer-readable recording medium.

The control circuit 100 includes an image reading unit 12 (image scanner), an image processing unit 14 (including a GPU (Graphics Processing Unit)), an image memory 15, an image forming unit 16 (printer), and an operation unit 17 (including a display unit 17a). It is connected to a large-capacity non-volatile storage device 18 such as a touch panel), an HDD (Hard Disk Drive) or an SSD (Solid State Drive), a facsimile communication unit 19, a network communication interface 13, and the like. The control circuit 100 controls the operation of each of the connected parts and transmits / receives a signal or data to / from each part. The operation unit 17 (touch panel) is a form of an input device, and a voice input device including a microphone may be provided as the input device.

3. 3. Hardware configuration of server device

FIG. 3 shows the hardware configuration of the server device.

The server device 20 includes a CPU 21, a ROM 22, a RAM 23, a storage device 24, a network communication interface 25, an operating device 26, a display device 27, and a bus 28 that connects them to each other.

The CPU 21, ROM 22, and RAM 23 constitute the control circuit 200. The CPU 21 loads the information processing program stored in the ROM 22 into the RAM 23 and executes it. The ROM 22 fixedly stores programs, data, and the like executed by the CPU 21. The ROM 22 is an example of a non-transient computer-readable recording medium.

4. Browser device hardware configuration

FIG. 4 shows the hardware configuration of the browser device.

The browser device 30 includes a CPU 31, a ROM 32, a RAM 33, a storage device 34, a network communication interface 35, an operation device 36, a display device 37, and a bus 38 that connects them to each other.

The CPU 31, ROM 32, and RAM 33 constitute the control circuit 300. The CPU 31 loads the information processing program stored in the ROM 32 into the RAM 33 and executes it. The ROM 32 fixedly stores programs, data, and the like executed by the CPU 31. The ROM 32 is an example of a non-transient computer-readable recording medium.

5. Functional configuration of notification system

FIG. 5 shows the functional configuration of the notification system.

In the control circuit 200 of the server device 20, the CPU 21 loads the information processing program stored in the ROM 22 into the RAM 23 and executes it to execute the notification determination unit 201, the notification data creation transmission unit 204, and the display notification history data creation unit 202. And, it operates as a display notification history data transmission unit 203.

The storage device 24 of the server device 20 has a status information 130, a notification history 110, a criterion 211, a template 212, and a first layout associated with a user who logs in to the notification system 1 using the browser device 30. 213, the second layout 214 and the third layout 215 are stored (all described later).

In the control circuit 300 of the browser device 30, the CPU 31 loads the information processing program stored in the ROM 32 into the RAM 33 and executes it to execute the display notification history data receiving unit 301, the one-dimensional screen display unit 302, and the first display. It operates as a temporary data creation unit 303, a first two-dimensional screen display unit 304, a second temporary data creation unit 305 for display, a second two-dimensional screen display unit 306, and a graph button display unit 307. The storage device 34 of the browser device 30 stores the graph display table 350.

FIG. 6 shows an example of the notification history.

The notification history 110 is a list of notifications sent to the browser device 30 by e-mail or the like based on the status information 130 related to the plurality of image forming devices 10 associated with the user who logs in to the notification system 1. The notification history 110 includes a notification history ID 111, a report date and time 112, a device ID 113, a notification type 114, a notification type (subclassification) 115, a subject 116, and a text 117.

The notification history ID 111 is a serial number that identifies one notification (notification sent to the browser device 30 by e-mail or the like). The report date and time 112 is the date and time when the notification was sent by e-mail or the like. The device ID 113 identifies the image forming device 10 in which the status has occurred. Notification types 114 include events, page counts, toner level alerts, and the like. The notification type (subclassification) 115 is a subdivided type of the notification type 114. Specifically, there are "paper jam" and "system error" as the notification type (subclassification) 115 for the notification type 114 "event". As the notification type (subclassification) 115 for the notification type 114 "page count", there is "copy total over 3000". Notification type 114 As the notification type (subclassification) 115 for "toner level alert", there is "cyan ≤ 5%". Subject 116 is the subject of the message included in the notification. The text 117 is the text of the message included in the notification.

6. Notification system operation flow

FIG. 7 shows the first operation flow of the server device.

The notification determination unit 201 of the server device 20 determines whether or not the notification should be sent to the browser device 30 by e-mail or the like based on whether the status information 130 satisfies the condition defined in the criteria 211 (step S201). ).

The server device 20 stores one criterion 211 for each user who logs in to the notification system 1. Criteria 211 includes a template 212 (template in the title and body of the e-mail) used when sending a notification to the browser device 30 by e-mail or the like, a condition for transmitting the notification, and a destination (e-mail) for transmitting the notification. Address, browser, etc.) are defined. The "condition for transmitting a notification" is, for example, a condition such that the toner level is equal to or less than a specific value (5% or the like).

If the status information 130 satisfies the condition defined in the criteria 211, the notification determination unit 201 of the server device 20 determines that the notification should be sent to the browser device 30 by e-mail or the like (steps S202, YES). Then, the notification data creation / transmission unit 204 of the server device 20 creates notification data by arranging the status information 130 in the template 212, and transmits the notification data by e-mail or the like (step S203). The notification data creation transmission unit 204 adds the transmitted notification data to the notification history 110 (step S204).

FIG. 21 shows a second operation flow of the server device.

The display notification history data creation unit 202 of the server device 20 receives a request for displaying the notification history screen from the browser device 30 (step S701, YES). Then, the display notification history data creation unit 202 creates the display notification history data 120 by extracting necessary data from the notification history 110. The display notification history data creation unit 202 stores the created display notification history data 120 in the storage device 24 (step S702).

The display notification history data transmission unit 203 of the server device 20 reads the display notification history data 120 from the storage device 24 and transmits the display notification history data 120 to the browser device 30 via the network N. The display notification history data transmission unit 203 further transmits the first layout 213, the second layout 214, and the third layout 215 stored in the storage device 24 to the browser device 30 via the network N ( Step S703).

The first layout 213, the second layout 214, and the third layout 215 are HTML data used by the browser device 30 to create screen data for displaying the display notification history data 120, respectively.

FIG. 8 shows an example of display notification history data.

The display notification history data 120 includes, for example, a notification history ID 111, a report date / time 112, a device ID 113, a notification type 114, a notification type (subclassification) 115, and a subject 116. The notification history ID 111, the report date and time 112, the device ID 113, the notification type 114, the notification type (subclassification) 115, and the subject 116 are extracted from the notification history 110.

FIG. 9 shows the operation flow of the browser device.

The display notification history data receiving unit 301 of the browser device 30 transmits the display notification history data 120 and the first layout 213, the second layout 214, and the third layout 215 from the server device 20 via the network N. To receive. The display notification history data receiving unit 301 stores the received display notification history data 120 and the first layout 213, the second layout 214, and the third layout 215. For example, the display notification history data receiving unit 301 stores the display notification history data 120 in the storage device 34, and stores the first layout 213, the second layout 214, and the third layout 215 in the RAM 33 (step). S301).

The one-dimensional screen display unit 302 of the browser device 30 generates a one-dimensional screen 320 based on the display notification history data 120 and the first layout 213, and displays the one-dimensional screen 320 on the display device 37 (step S302). .. Specifically, the one-dimensional screen display unit 302 generates the one-dimensional screen 320 by arranging the display notification history data 120 in the first layout 213. The first layout 213 is a layout for displaying the data of at least a part of the items included in the display notification history data 120 in one dimension.

FIG. 10 shows an example of a one-dimensional screen.

The one-dimensional screen 320 includes a one-dimensional table 321 and various buttons including a display switching button 322 and a delete button 323.

The one-dimensional table 321 shows data of some items (subject 116, notification type 114, notification type (subclassification) 115, device ID 113, and report date / time 112) included in the display notification history data 120. Is displayed in one dimension. One row 324 of the one-dimensional table 321 corresponds to one notification history ID 111 (FIG. 6). In other words, the one-dimensional table 321 includes rows 324 as many as the number of notification history IDs 111 (FIG. 6) included in the display notification history data 120.

The one-dimensional table 321 further includes a check box 325. One check box 325 is provided for each line 324 corresponding to one notification history ID 111 (FIG. 6).

The display switching button 322 is a button for instructing the display notification history data 120 to be displayed in a layout different from that of the one-dimensional table 321 (first two-dimensional table 331).

The first display temporary data creation unit 303 of the browser device 30 is an operation input via the operation device 36 for the display switching button 322 included in the one-dimensional screen 320 (for example, a mouse click or a touch panel touch). Is detected (step S303, YES). Then, the first display temporary data creation unit 303 generates the first display temporary data 410 based on the display notification history data 120 stored in the storage device 34 (step S304).

FIG. 11 shows a processing flow for generating the first temporary display data. FIG. 12 shows in order the processing for generating the first temporary data for display.

The first display temporary data creation unit 303 of the browser device 30 includes the device ID 113, the notification type 114, the notification history ID 111, and the number of cases 118, which are items included in the display notification history data 120, as the heading 411. An empty (blank) first display temporary data 410 is created (step S401, A in FIG. 12).

The first display temporary data creation unit 303 reads the device ID 113, the notification type 114, and the notification history ID 111 of the first line 121 from the display notification history data 120 (FIG. 8) (step S402).

In the first display temporary data creation unit 303, the device ID 113 “Device_10000” of the first line 121 read from the display notification history data 120 (FIG. 8) is changed to the device ID 113 of the first display temporary data 410. It is determined whether or not it is registered (step S403).

Since the first temporary display data 410 only includes the heading 411 (A in FIG. 12), it does not include the device ID 113 “Device_10000” (steps S404, NO).

In this case, the first display temporary data creation unit 303 reads each value (device ID 113,) of the first line 121 read from the display notification history data 120 (FIG. 8) into the first display temporary data 410. The first line 412 in which the notification type 114 and the notification history ID 111) are registered is added to the first temporary display data 410. The first display temporary data creation unit 303 registers "1" in the number 118 of the first line 412 (step S405, B in FIG. 12). After that, the first display temporary data creation unit 303 repeats the same processing for the second line 122 and subsequent lines of the display notification history data 120 (FIG. 8).

On the other hand, the first display temporary data creation unit 303 states that the device ID 113 of the line read from the display notification history data 120 (FIG. 8) is registered in the device ID 113 of the first display temporary data 410. Judgment (step S404, YES).

In the case of this example (B in FIG. 12), in the first display temporary data creation unit 303, the device ID 113 “Device_10000” in the fourth line 124 read from the display notification history data 120 (FIG. 8) is the first. It is determined that the temporary data for display of 1 is registered in the device ID 113 of the first line 412 of the temporary data 410 (step S404, YES).

In this case, the first display temporary data creation unit 303 has the same notification type 114 of the fourth line 124 read from the display notification history data 120 (FIG. 8) as the first display temporary data 410. It is determined whether or not the line (first line 412) of the device ID 113 “Device_10000” is registered (step S406).

In the case of this example (B in FIG. 12), the notification type 114 of the line (first line 412) of the device ID 113 “Device_10000” of the first temporary data 410 for display is “event”. Therefore, the notification type 114 “toner level alert” of the fourth line 124 read from the display notification history data 120 (FIG. 8) is the line of the same device ID 113 “Device_10000” of the first temporary data 410 (FIG. 8). It is not registered for the first line 412) (step S407, NO).

In this case, the first display temporary data creation unit 303 reads each value (device ID 113,) of the fourth line 124 read from the display notification history data 120 (FIG. 8) into the first display temporary data 410. The second line 413 in which the notification type 114 and the notification history ID 111) are registered is added immediately below the first line 412, which is the line of the same device ID 113 “Device_10000” in the temporary display data 410. The first display temporary data creation unit 303 registers "1" in the number 118 of the second line 413 (step S408, C in FIG. 12). After that, the first display temporary data creation unit 303 repeats the same processing for the fifth line 125 and subsequent lines of the display notification history data 120 (FIG. 8).

On the other hand, in the first display temporary data creation unit 303, the notification type 114 of the line read from the display notification history data 120 (FIG. 8) is set to the same device ID 113 line of the first display temporary data 410. It is determined that the data is registered (step S407, YES).

In the case of this example (C in FIG. 12), the notification type 114 of the line (first line 412) of the device ID 113 “Device_10000” of the first temporary data 410 for display is “event”. Therefore, the notification type 114 “event” of the fifth line 125 read from the display notification history data 120 (FIG. 8) is the line (first) of the same device ID 113 “Device_10000” of the first temporary display data 410. It is registered for the line 412) of (step S407, YES).

In this case, the first display temporary data creation unit 303 is the first line in which the same device ID 113 “Device_10000” and the same notification type 114 “event” are registered in the first display temporary data 410. The number 118 "1" in line 412 is counted up (incremented) and overwritten with "2". Further, the first display temporary data creation unit 303 finally reads the notification history ID 111 of the fifth line 125 read from the display notification history data 120 (FIG. 8) at the end of the notification history ID 111 of the first line 412. Add "N-00005" separated by commas (step S409, D in FIG. 12).

The first display temporary data creation unit 303 repeats the processes of steps S401 to S409 for all the lines 121 and below included in the display notification history data 120 (steps S410, NO). As a result, the first display temporary data creation unit 303 registers all the rows 121 and below included in the display notification history data 120 in the first display temporary data 410 (step S410, YES).

By the way, in this example, the first display temporary data creation unit 303 reads each value of the first line 121 read from the display notification history data 120 (FIG. 8) into the first display temporary data 410 (FIG. 8). The second line 413 in which the device ID 113, the notification type 114, and the notification history ID 111) are registered is added directly under the first line 412, which is the line of the same device ID 113, in the temporary display data 410 (1). Step S408, C in FIG. 12). In short, the first display temporary data 410 includes a plurality of rows (first row 412 and second row 413) in which the same device ID 113 “Device_10000” is registered (C in FIG. 12).

Instead of this, the first temporary display data creation unit 303 may create the first temporary display data 410 having a different structure. For example, the first display temporary data 410 includes only one line (first line 412) for one device ID 113 “Device_10000”. For example, for one device ID 113, the notification type 114, the number of cases 118, and the notification history ID 111 may be enclosed in parentheses and separated by commas (E in FIG. 12).

See FIG. The first two-dimensional screen display unit 304 of the browser device 30 generates the first two-dimensional screen 330 based on the created temporary data 410 for display and the second layout 214, and the first two. The dimension screen 330 is displayed on the display device 37 (step S305). Specifically, the first two-dimensional screen display unit 304 generates the first two-dimensional screen 330 by arranging the first display temporary data 410 in the second layout 214. The second layout 214 is a layout for displaying the data of at least a part of the items included in the display notification history data 120 in two dimensions.

The first two-dimensional screen 330 includes a first two-dimensional table 331 and various buttons including a display switching button 322, a delete button 323, and a priority display button 327. In the first two-dimensional table 331, the first axis is the device ID 113, the second axis is the notification type 114, and the cell at the intersection of the device ID 113 and the notification type 114 is identified by the device ID 113. It is a two-dimensional table displaying the number of notifications of the image forming apparatus 10.

FIG. 13 shows an example of the first two-dimensional screen.

More specifically, the first two-dimensional screen display unit 304 is the data registered in the column of the notification type 114 of the first temporary data 410 for display (E in FIG. 12) (in this example, " Load all "Events", "Toner Level Alerts" and "Page Counts"). The first two-dimensional screen display unit 304 displays all the read notification types 114 (that is, event 114A, toner level alert 114B, and page count 114C) on the title line 332 of the second layout 214. The first two-dimensional screen display unit 304 displays various buttons including a display switching button 322, a delete button 323, and a priority display button 327.

The first two-dimensional screen display unit 304 reads the first display temporary data 410 (E in FIG. 12) in order from the first line 412, and with respect to all the lines (first line 412 and below), the device ID 113. And the number 118 are displayed in the first two-dimensional table 331.

As a specific example, the first line 412 of the first temporary data for display 410 (E in FIG. 12) will be described. The first two-dimensional screen display unit 304 displays the device ID 113 “Device_10000” included in the first row 412 in the first two-dimensional table 331. The first two-dimensional screen display unit 304 is the device ID 113 “Device_10000” included in the first row 412 and the notification type 114 included in the first row 412 in the first two-dimensional table 331. In cell 333, which is the intersection with "event" 114A, the number of notifications 118 "2" included in the first row 412 is displayed. The first two-dimensional screen display unit 304 may highlight (for example, change the background color) the cell 333 in which the number of cases 118 is the maximum value (2 cases).

The first two-dimensional table 331 further includes a check box 335 (first check box). One check box 335 is provided for each row 334 corresponding to one device ID 113. The check box 335 is a button for designating the device ID 113.

The priority display button 327 displays the display notification history data 120 related to the device ID 113 specified by the check box 335 in a two-dimensional table (second two-dimensional table 341) different from the first two-dimensional table 331. It is a button for instructing to display.

The display switching button 322 is a button for instructing the display notification history data 120 to be displayed in a layout (one-dimensional table 321) different from that of the first two-dimensional table 331.

By the way, the one-dimensional table 321 (FIG. 10) includes rows 324 as many as the number of notification history IDs 111 (FIG. 6) included in the display notification history data 120. In contrast, the first two-dimensional table 331 (FIG. 13) includes as many rows 334 as the number of device IDs 113 (FIG. 12). In other words, the one-dimensional table 321 (FIG. 10) displays a plurality of rows 324 for the same device ID 113. On the other hand, in the first two-dimensional table 331 (FIG. 13), one row 334 is registered for one device ID 113. This makes the table less complicated and easier to understand.

See FIG. The second display temporary data creation unit 305 of the browser device 30 detects an operation on one check box 335 and the priority display button 327 included in the first two-dimensional table 331 (steps S306, YES). In this example, the check box 335A for designating the device ID 113 "Device_10000" is operated.

Then, the second temporary display data creation unit 305 generates the second temporary display data 510 based on the display notification history data 120 stored in the storage device 34 (step S307).

FIG. 14 shows a processing flow for generating the second temporary data for display. FIG. 15 shows in order the processing for generating the second temporary data for display.

The second temporary data creation unit 305 for display of the browser device 30 finds the notification type 114, the notification type (subclassification) 115, the report date 112A (not the report date and time 112), the number of cases 118, and the notification history ID 111. A blank second temporary data 510 for display is created (step S501, A in FIG. 15).

From the display notification history data 120 (FIG. 8), the second display temporary data creation unit 305 includes the notification history ID 111, the report date and time 112, the device ID 113, and the notification type 114 in the first line 121. , Notification type (subclassification) 115 and is read (step S502).

In the second display temporary data creation unit 305, the device ID 113 “Device_10000” of the first line 121 read from the display notification history data 120 (FIG. 8) is checked in the check box 335 (step S306, YES). It is determined whether or not the device ID 113 has been used (step S503).

The second display temporary data creation unit 305 determines that the device ID 113 in the first row 121 is not the device ID 113 checked in the check box 335 (step S306, YES) (step S504, NO). In this case, the second display temporary data creation unit 305 reads each data in the second line 122 from the display notification history data 120 (FIG. 8) (step S502), and repeats the process.

On the other hand, the second display temporary data creation unit 305 determines that the device ID 113 in the first row 121 is the device ID 113 checked in the check box 335 (step S306, YES) (step S504, YES). ). In this case, in the second display temporary data creation unit 305, the notification type 114 “event” of the first line 121 read from the display notification history data 120 (FIG. 8) is the second display temporary data 510. It is determined whether or not the notification type 114 is registered (step S505).

Since the second display temporary data 510 only includes the heading 511 (A in FIG. 15), it does not include the notification type 114 “event” (step S506, NO).

In this case, the second display temporary data creation unit 305 reads each value (notification type) of the first line 121 read from the display notification history data 120 (FIG. 8) into the second display temporary data 510. The first line 512 in which 114, the type of notification (subclassification) 115, the report date 112A (created based on the report date and time 112), and the notification history ID 111) is registered is added to the second temporary data 510 for display. The second temporary data creation unit 305 for display registers "1" in the number 118 of the first line 512 (step S507, B in FIG. 15). After that, the second display temporary data creation unit 305 repeats the same processing for the second line 122 and subsequent lines of the display notification history data 120 (FIG. 8).

On the other hand, in the second temporary display data creation unit 305, the notification type 114 of the line read from the display notification history data 120 (FIG. 8) is registered in the notification type 114 of the second temporary display data 510. It is determined that this has been done (step S506, YES).

In the case of this example (B in FIG. 15), the second display temporary data creation unit 305 has the notification type 114 “event” of the 51st line 127 read from the display notification history data 120 (FIG. 8). , It is determined that the data is registered in the notification type 114 of the first line 512 of the second temporary data 510 for display (step S506, YES).

In this case, in the second display temporary data creation unit 305, the notification type (subclassification) 115 of the 51st line 127 read from the display notification history data 120 (FIG. 8) is the second display temporary data. It is determined whether or not the data 510 is registered for the same notification type 114 “event” line (first line 512) (step S508).

In the case of this example (B in FIG. 15), the notification type (subclassification) 115 of the notification type 114 “event” line (first line 512) of the second temporary data 510 for display is “paper jam”. ". Therefore, the notification type (subclassification) 115 “other errors” of the 51st line 127 read from the display notification history data 120 (FIG. 8) is the same notification type 114 of the second temporary display data 510. It is not registered for the "event" line (first line 512) (step S509, NO).

In this case, the second display temporary data creation unit 305 reads each value (notification type) of the 51st line 127 read from the display notification history data 120 (FIG. 8) into the second display temporary data 510. The second line 513 in which 114, the type of notification (subclassification) 115, the report date 112A (created based on the report date and time 112), and the notification history ID 111) is registered in the notification of the second temporary data 510 for display. Add just below the first line 512, which is the line of type 114 "event". The second temporary data creation unit 305 for display registers "1" in the number 118 of the second line 513 (step S510, C in FIG. 15). After that, the second display temporary data creation unit 305 repeats the same processing for the next and subsequent lines of the display notification history data 120 (FIG. 8).

On the other hand, in the second display temporary data creation unit 305, the notification type (subclassification) 115 of the line read from the display notification history data 120 (FIG. 8) is the same notification of the second display temporary data 510. It is determined that the line of type 114 is registered (step S509, YES).

In the case of this example (B in FIG. 15), the notification type (subclassification) 115 of the notification type 114 “event” line (first line 512) of the second temporary data 510 for display is “paper jam”. ". Therefore, the notification type (subclassification) 115 “paper jam” of the 52nd line 128 read from the display notification history data 120 (FIG. 8) is the same notification type 114 “paper jam” of the second temporary display data 510. It is registered for the "event" line (first line 512) (step S509, YES).

In this case, the second display temporary data creation unit 305 sets the report date 112A (not the report date and time 112) of the 52nd line 128 read from the display notification history data 120 (FIG. 8) to the second display. It is determined whether or not the temporary data 510 is registered for the same notification type (subclassification) 115 “paper jam” line (first line 512) (step S511).

In the case of this example (B in FIG. 15), the report date 112A of the notification type (subclassification) 115 “paper jam” line (first line 512) of the second temporary data 510 for display is “2019 / 09/27 ". Therefore, the report date 112A (not the report date and time 112) "2019/09/30" of the 52nd line 128 read from the display notification history data 120 (FIG. 8) is the same as the second temporary display data 510. Notification type (subclassification) 115 Not registered for the "paper jam" line (first line 512) (step S512, NO).

In this case, the second display temporary data creation unit 305 reads each value (notification type) of the 52nd line 128 read from the display notification history data 120 (FIG. 8) into the second display temporary data 510. The second line 514 in which 114, the type of notification (subclassification) 115, the report date 112A (created based on the report date and time 112), and the notification history ID 111) are registered in the notification of the second temporary data 510 for display. Type (subcategory) 115 Add just below the first line 512, which is the "paper jam" line. The second temporary data creation unit 305 for display registers "1" in the number 118 of the second line 514 (step S513, D in FIG. 15). After that, the second display temporary data creation unit 305 repeats the same processing for the next and subsequent lines of the display notification history data 120 (FIG. 8).

On the other hand, the second display temporary data creation unit 305 changes the report date 112A of the line read from the display notification history data 120 (FIG. 8) to the same report date 112A of the second display temporary data 510. It is determined that the data is registered (step S512, YES).

In the case of this example (B in FIG. 15), the report date 112A of the notification type (subclassification) 115 “paper jam” line (first line 512) of the second temporary data 510 for display is “2019 / 09/27 ". Therefore, the report date 112A "2019/09/27" of the 53rd line 129 read from the display notification history data 120 (FIG. 8) is the same notification type (subclassification) of the second display temporary data 510. It is registered for the 115 "paper jam" line (first line 512) (step S512, YES).

In this case, the second display temporary data creation unit 305 has the same notification type (subclassification) 115 “paper jam” and the same report date 112A “2019/09/27” in the second display temporary data 510. Counts up (increments) the number 118 "1" of the first line 512, which is the line in which is registered, and overwrites "2". Further, the second display temporary data creation unit 305 adds the notification history ID 111 of the 53rd line 129 read from the display notification history data 120 (FIG. 8) to the end of the notification history ID 111 of the first line 512. Add "N-00053" separated by commas (step S514, E in FIG. 15).

The second display temporary data creation unit 305 repeats the processes of steps S501 to S514 for all the lines 121 and below included in the display notification history data 120 (steps S515, NO). As a result, the second display temporary data creation unit 305 registers all the rows 121 and below included in the display notification history data 120 in the second display temporary data 510 (step S515, YES).

By the way, in this example, the second display temporary data creation unit 305 reads each value of the first line 121 read from the display notification history data 120 (FIG. 8) into the second display temporary data 510 (FIG. 8). The second line 514 in which the notification type 114, the notification type (subclassification) 115, the report date 112A, and the notification history ID 111) are registered, is the same notification type 114 “event” of the second temporary data 510 for display. And the type of notification (subclassification) 115, which is the line of "paper jam", is added immediately below the first line 512 (step S513, D in FIG. 15). In short, the second display temporary data 510 includes a plurality of lines (first line 512 and second line 514) in which the same notification type 114 "event" is registered (D in FIG. 15).

Instead of this, the second temporary display data creation unit 305 may create the second temporary data 510 for display having a different structure. For example, the second display temporary data 510 includes only one line (first line 512) for one notification type 114 “event”. For example, for one notification type 114 "event", the notification type (subclassification) 115, the report date 112A, the number of cases 118, and the notification history ID 111 may be enclosed in parentheses and separated by commas (Fig.). 15 E).

See FIG. The second two-dimensional screen display unit 306 of the browser device 30 generates a second two-dimensional screen 340 based on the created temporary data 510 for display and the third layout 215, and the second 2 The dimensional screen 340 is displayed on the display device 37 (step S308). Specifically, the second two-dimensional screen display unit 306 generates the second two-dimensional screen 340 by arranging the second display temporary data 510 in the third layout 215. The third layout 215 is a layout for displaying the data of at least a part of the items included in the display notification history data 120 in two dimensions.

The second two-dimensional screen 340 includes a second two-dimensional table 341 and various buttons including a delete button 323, a priority display release button 325, and a non-latest delete button 326. In the second two-dimensional table 341, regarding the notification of one image forming apparatus 10 identified by one apparatus ID 113, the first axis is the notification type 114 and the second axis is the reporting date 112A. It is a two-dimensional table in which the number of notifications of the report date 112A is displayed in the cell which is the intersection of the notification type 114 and the report date 112A.

FIG. 16 shows an example of a second two-dimensional screen.

More specifically, the second two-dimensional screen display unit 306 is the data registered in the column of the report date 112A of the second temporary data 510 for display (F in FIG. 15) (in this example, "2019". / 09/27 ”,“ 2019/09/29 ”and“ 2019/09/30 ”) are all read. The second two-dimensional screen display unit 306 displays all the read report dates 112A (that is, "2019/09/27" 112B, "2019/09/29" 112C and "2019/09/30" 112D). It is displayed in the title line 342 of the third layout 215. The second two-dimensional screen display unit 306 displays various buttons including a delete button 323, a priority display release button 325, and a non-latest delete button 326.

The second two-dimensional screen display unit 306 reads the second display temporary data 510 (F in FIG. 15) in order from the first line 512, and notifies all the lines (first line 512 and below). The type 114, the type of notification (subclassification) 115, and the reporting date 112A are displayed in the second two-dimensional table 341.

As a specific example, the first line 512 of the second temporary data 510 for display (F in FIG. 15) will be described. In the second two-dimensional table 341, the second two-dimensional screen display unit 306 includes a notification type 114 “event” and a notification type (subclassification) 115 “paper jam” included in the first row 512. , "Other errors" and "System errors" are displayed. The second two-dimensional screen display unit 306 includes the notification type (subclassification) 115 “paper jam” included in the first row 512 and the first row 512 in the second two-dimensional table 341. In cell 343, which is the intersection with "2019/09/27" 112B, which is the report date 112A, the number of notifications 118 "2" included in the first row 512 is displayed. The second two-dimensional screen display unit 306 may highlight (for example, change the background color) the cell 343 in which the number 118 is the maximum value (2 cases).

The second two-dimensional table 341 further includes a check box 345 (a second check box). One check box 345 is provided for each line 344 corresponding to the notification type 114 and one notification type (subclassification) 115. The check box 345 is a button for designating the notification type (subclassification) 115.

The priority display release button 325 is a button for instructing that the display notification history data 120 is displayed in a two-dimensional table (first two-dimensional table 331) different from the second two-dimensional table 341. Is.

The delete button 326 other than the latest deletes the notification history data 120 for display other than the report date 112A (for example, "2019/09/27" 112B) other than the report date 112A of the latest predetermined period, and reports the latest predetermined period. It is a button for instructing to display only the display notification history data 120 of the day 112A (for example, “2019/09/27” 112B) in the second two-dimensional table 341.

More specifically, the browser device 30 has a check box 345 for designating a notification type 114 (may be a notification type (subclassification) 115) included in the second two-dimensional table 341, and a check box 345 other than the latest. The operation input to the delete button 326 via the operation device 36 is detected. Then, the browser device 30 is the latest one associated with the notification type 114 or the notification type (subclassification) 115 specified by the check box 345 from the second display temporary data 510 (F in FIG. 15). Read the notification history ID 111 other than the predetermined period. The browser device 30 transmits the read notification history ID 111 to the server device 20. The server device 20 updates the display notification history data 120 by deleting the received notification history ID 111 from the display notification history data 120. The server device 20 transmits the updated display notification history data 120 to the browser device 30. The browser device 30 executes the processes of step S301 and subsequent steps based on the updated display notification history data 120. As a result, the browser device 30 deletes the notification history data for display other than the latest predetermined period of the notification type 114 or the notification type (subclassification) 115 specified by the check box 345, so that the second 2 The dimension table 341 is updated and displayed on the display device 37.

By the way, the one-dimensional table 321 (FIG. 10) includes rows 324 as many as the number of notification history IDs 111 (FIG. 6) included in the display notification history data 120. In contrast, the second two-dimensional table 341 (FIG. 16) includes as many rows 344 as there are notification types (subclassifications) 115 (FIG. 15). In other words, the one-dimensional table 321 (FIG. 10) displays a plurality of rows 324 for the same notification type (subclassification) 115. On the other hand, in the second two-dimensional table 341 (FIG. 16), one row 344 is registered for one notification type (subclassification) 115. This makes the table less complicated and easier to understand.

See FIG. The graph button display unit 307 of the browser device 30 additionally displays the graph button 346 on the second two-dimensional table 341 (step S309).

The graph button 346 is a button for supporting the display of a graph relating to a particular notification type 114 of a particular image forming apparatus 10.

FIG. 17 shows a processing flow for additionally displaying a graph button.

The graph button display unit 307 of the browser device 30 reads the first line 512 of the second temporary data 510 for display (F in FIG. 15) (step S601). The graph button display unit 307 of the browser device 30 reads the graph display table 350 from the storage device 34.

FIG. 18 shows a graph display table.

The graph display table 350 defines "TRUE" 351 indicating that it can be displayed in the form of a graph or "FALSE" 352 indicating that it cannot be displayed in the form of a graph for the type 114 of the notification. Specifically, "TRUE" 351 is defined for the notification types "toner level alert" 114B and "page count" 114C. This means that the toner level and page count can be displayed in the form of a graph. On the other hand, "FALSE" 352 is defined for the notification type "event" 114A. This means that the event cannot be displayed in the form of a graph.

The graph button display unit 307 of the browser device 30 refers to the graph display table 350, and refers to the notification type 114 included in the first row 512 read from the second temporary data 510 for display (F in FIG. 15). Then, it is determined whether "TRUE" 351 or "FALSE" 352 is defined (step S602).

In the case of this example, the graph button display unit 307 of the browser device 30 has "event" 114A for the notification type "event" 114A included in the first line 512 of the second temporary data 510 for display (F in FIG. 15). It is determined that "FALSE" 352 is defined (step S603, NO). Then, the graph button display unit 307 reads the second line 513 from the second temporary data 510 for display (F in FIG. 15) (step S601), and repeats the process.

On the other hand, in the graph button display unit 307, "TRUE" 351 is defined for the notification type "toner level alert" 114B included in the second line 515 of the second temporary data 510 (F in FIG. 15). It is determined that this has been done (step S603, YES).

Then, the graph button display unit 307 includes the second two-dimensional table 341A by arranging the graph button 346 in association with the notification type "toner level alert" 114B of the second two-dimensional table 341. The two-dimensional screen 340A of 2 is updated (redisplayed) (step S604).

FIG. 19 shows an example of a second two-dimensional screen including a graph button.

The second two-dimensional table 341A includes a graph button 346 in association with the notification type "toner level alert" 114B (in the same column). On the other hand, the second two-dimensional table 341A does not include a graph button in the column of the notification type "event" 114A.

The graph button display unit 307 repeats the processes of steps S601 to S604 for all rows 512 and below included in the second temporary display data 510 (F in FIG. 15) (steps S605, NO). As a result, the graph button display unit 307 displays the graph button 346 for the notification type 114 that can be displayed in all graph formats (step S605, YES).

FIG. 20 shows an example of a graph.

The browser device 30 detects an operation on the graph button 346 input via the operation device 36. Then, the browser device 30 transmits the device ID 113 of the image forming device 10 shown in the second two-dimensional table 341A being displayed and the notification type 114 associated with the graph button 346 to the server device 20. The browser device 30 receives detailed historical data regarding the device ID 113 and the notification type 114 from the server device 20. The browser device 30 draws a graph 360 based on the received history data and displays it in a separate window.

7. Conclusion

A web system (for example, Kyocera Fleet Services) in which a browser device acquires information on an image forming device from a server device via a network and remotely maintains the image forming device is known. Typically, the browser device receives display notification history data from the server device when the image forming device meets the criteria (conditions for transmitting the notification). The browser device displays the received display notification history data as a history list screen. For example, on the history list screen, one history is displayed per line like a mailer. However, with this display method, when a large number of notification histories exist, there is a risk that it is difficult for the user to understand at first glance, and it is difficult to determine whether to delete or save for organizing.

(1) On the other hand, according to the present embodiment, the browser device 30 has the first axis as the device ID and the second axis as the notification type 114, and at the intersection of the device ID and the notification type 114. A first two-dimensional table 331, which is a two-dimensional table displaying the number of notifications of the image forming apparatus identified by the device ID, is generated in a certain cell and displayed on the display device. According to this embodiment, the first two-dimensional table 331 (FIG. 13) includes as many rows 334 as the number of device IDs 113 (FIG. 12). In other words, the one-dimensional table 321 (FIG. 10) displays a plurality of rows 324 for the same device ID 113. On the other hand, in the first two-dimensional table 331 (FIG. 13), one row 334 is registered for one device ID 113. This makes the table less complicated and easier to understand.

(2) According to the present embodiment, the browser device 30 reports to the cell which is the intersection of the notification type 114 and the reporting date, with the first axis as the notification type 114 and the second axis as the reporting date. A second two-dimensional table 341, which is a two-dimensional table displaying the number of day notifications, is generated and displayed on the display device. According to this embodiment, the second two-dimensional table 341 (FIG. 16) includes as many rows 344 as the number of notification types (subclassifications) 115 (FIG. 15). In other words, the one-dimensional table 321 (FIG. 10) displays a plurality of rows 324 for the same notification type (subclassification) 115. On the other hand, in the second two-dimensional table 341 (FIG. 16), one row 344 is registered for one notification type (subclassification) 115. This makes the table less complicated and easier to understand.

(3) According to the present embodiment, the browser device 30 forms an image identified by the device ID specified by the first check box for designating the device ID included in the first two-dimensional table 331. A second two-dimensional table 341 for device notifications is generated and displayed on the display device. As a result, when there are a large number of notifications for one image forming apparatus 10, the second 2 has the classification attribute (notification type 114 and notification type (subclassification) 115) as the first axis. The number of cases is displayed in the dimension table 341. As a result, the user can perform operations such as deleting and forwarding after grasping the whole picture without checking each notification, so that the notification organizing work is assisted.

(4) According to the present embodiment, the browser device 30 sets the graph button to the notification type 114 when the notification type 114 included in the second two-dimensional table 341 can be displayed in the form of a graph. Display in association. As a result, the user can grasp the whole picture without checking each notification, display a desired graph, and can grasp the whole picture more efficiently by the graph.

(5) According to the present embodiment, the browser device 30 has a second two-dimensional table including a second check box for designating the notification type 114 included in the second two-dimensional table 341. , The delete button other than the latest is displayed on the display device. As a result, the user can flexibly select and collectively operate a large number of notifications (collectively delete), and it is easy to leave only the latest notification and delete the others.

(6) According to the present embodiment, the browser device 30 highlights the cell in the two-dimensional table having the maximum number of cases. By classifying the notification contents and displaying the number of notifications in two dimensions, the user can check the overall distribution of the notification types and highlight the cell with the maximum number of notifications. This makes it easy to pinpoint the distribution of notification types.

Although each embodiment and each modification of the present technology have been described above, the present technology is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the present technology. Of course.

Notification system 1
Image forming apparatus 10
Server device 20
Browser device 30
Notification judgment unit 201
Display notification history data creation unit 202
Display notification history data transmitter 203
Notification data creation transmitter 204
Display notification history data receiver 301
One-dimensional screen display unit 302
First display temporary data creation unit 303
First two-dimensional screen display unit 304
Second display temporary data creation unit 305
Second two-dimensional screen display unit 306
Graph button display unit 307

Claims (8)

A server device that is communicatively connected to the image forming device,
It is equipped with a browser device that is communicatively connected to the server device.
The server device
The first communication interface and
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted to the browser apparatus is determined, and the notification is determined.
It has a device ID for identifying the image forming device and a first control circuit for transmitting display notification history data including the type of notification to the browser device via the first communication interface.
The browser device
The second communication interface and
The second storage device and
Display device and
Operating device and
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell that is the intersection of the device ID and the notification type is identified by the device ID. A notification system including a second control circuit that generates a first two-dimensional table, which is a two-dimensional table displaying the number of notifications of the image forming apparatus, and displays the notifications on the display device. The notification system according to claim 1.
The display notification history data further includes a report date.
The second control circuit of the browser device is
Based on the display notification history data, the first axis is the notification type, the second axis is the reporting date, and the cell at the intersection of the notification type and the reporting date is in the cell of the reporting date. A notification system that generates a second two-dimensional table, which is a two-dimensional table that displays the number of notifications, and displays it on the display device. The notification system according to claim 2.
The second control circuit of the browser device is
The first two-dimensional table including the first check box for designating the device ID included in the first two-dimensional table is displayed on the display device.
The operation on the first check box of the first two-dimensional table input via the operating device is detected.
A notification system that generates a second two-dimensional table for the notification of the image forming apparatus identified by the device ID specified by the operated first check box and displays it on the display device. The notification system according to claim 2 or 3.
The second control circuit of the browser device is
When the type of notification included in the second two-dimensional table for the notification of the image forming apparatus can be displayed in the form of a graph, a graph button is displayed in association with the type of notification.
When the operation for the graph button input via the operating device is detected,
A notification system that displays a graph of the type of notification associated with the graph button of the image forming device on the display device. The notification system according to any one of claims 2 to 4.
The second control circuit of the browser device is
The display device displays the second two-dimensional table including a second check box for specifying the type of notification included in the second two-dimensional table, and a non-latest delete button. ,
When the operation for the second check box and the non-latest delete button input via the operating device is detected,
The second two-dimensional table is updated and displayed on the display device by deleting the notification history data for display other than the latest predetermined period of the notification type specified by the second check box. Notification system. The notification system according to any one of claims 2 to 5.
The second control circuit of the browser device is
A notification system that highlights the cell with the maximum number of cases in the first two-dimensional table or the second two-dimensional table. The first communication interface, which is communicably connected to the image forming apparatus,
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted is determined.
It is possible to communicate with a server device having a first control circuit that transmits display notification history data including a device ID that identifies the image forming device and the notification type via the first communication interface. Connected,
The second communication interface and
The second storage device and
Display device and
Operating device and
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell, which is the intersection of the device ID and the notification type, is identified by the device ID. A browser device including a second control circuit that generates a first two-dimensional table that is a two-dimensional table that displays the number of notifications of the image forming device and displays it on the display device. The first communication interface, which is communicably connected to the image forming apparatus,
The first storage device and
The status of the image forming apparatus is received from the image forming apparatus via the first communication interface and stored in the first storage device.
Based on the status of the image forming apparatus, the notification to be transmitted is determined.
It is possible to communicate with a server device having a first control circuit that transmits display notification history data including a device ID that identifies the image forming device and the notification type via the first communication interface. Connected,
The second communication interface and
The second storage device and
Display device and
Operating device and
The second control circuit of the browser device having the second control circuit,
The display notification history data is received from the server device via the second communication interface and stored in the second storage device.
Based on the display notification history data, the first axis is the device ID, the second axis is the notification type, and the cell, which is the intersection of the device ID and the notification type, is identified by the device ID. A notification program that generates a first two-dimensional table, which is a two-dimensional table displaying the number of notifications of the image forming apparatus, and operates the display device to display the first two-dimensional table.

Images