Information processing apparatus with report creation on usage state of printing devices, control method of information processing apparatus, and non-transitory computer-readable storage medium

A device management application acquires device information at a predetermined frequency from a printing device on a network and generates a device list by adding a newly detected printing device. In the device list, for a printing device on which device information is acquired, the device information is accumulated in association with the acquisition date and time, and for a printing device on which device information is not acquired, information indicating no connection is accumulated as device usage information in association with the acquisition date and time. A report is created based on the information accumulated for printing devices included in the device list.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to an information processing apparatus, a control method of the information processing apparatus, and a non-transitory computer-readable storage medium for executing software that acquires and manages device information from a printing device.

Description of the Related Art

In recent years, as a usage form of a printing device such as a printer or a multi-function peripheral (MFP) (hereinafter, referred to as a “device”), subscription contracts have increased under which a user pays a flat rate charge determined in advance and is allowed to use the device for a predetermined period. In general, a subscription contract is made for each device, and the device can be used at a flat rate as long as the upper limit on the number of printed sheets is not exceeded within the period determined under the contract. For example, in a case of a monthly contract, the device can be used at a flat rate as long as the upper limit on the number of printed sheets is not exceeded in a month. The user has to pay an excess charge only when the upper limit on the number of printed sheets is exceeded, and consumable supplies such as a toner are automatically delivered free of charge when the remaining amount becomes small.

Note that, when a device fails and repairment thereof is difficult, the device is replaced with an alternative device, and thereby the service is continued.

Further, to enable the user to select the number or models of installed devices in accordance with a usage state of devices, an application to create a report related to the usage state of the devices is used.

Conventionally, a method of creating a report that takes alternative use of another device in place of a failed device into consideration in a case of a device failure has been proposed.

In Japanese Patent Application Laid-Open No. 2016-66237, in response to detection of a failure, a device whose usage state has negative correlation with the usage state of the failed device is identified and grouped with the failed device as a device used in place of the failed device. Accordingly, a report that enables the user to suitably understand the usage state is created.

When the device was replaced due to a failure or the like, the user' interest is directed not only to the usage state of a device in connection at the time of report output but also to the usage state of a device that was replaced and is not in connection at the time of report output. However, it is not possible to acquire information related to the usage state from the device that was replaced and is no longer connected, and it is not possible to include such information in the report. Thus, it is not possible for the user to understand the usage state of the device that was replaced and is no longer connected at the time of report output.

The present invention has been made to solve the above problem. An object of the present invention is to provide a mechanism that can create a report including not only the usage state of a printing device in connection at the time of report output but also the usage state of a printing device that was replaced and is no longer connected even when the printing device is replaced under a subscription contract or the like.

SUMMARY OF THE INVENTION

The present invention is an information processing apparatus that executes software configured to acquire and manage device information including at least any one of usage information and operation information on a printing device, and the information processing apparatus includes: an acquisition unit that performs an acquisition process to acquire the device information at a predetermined frequency from a printing device connected to a network; a generation unit that generates a list by adding a newly detected printing device in the acquisition process; an accumulation unit that, for a printing device on which the device information is acquired out of printing devices included in the list, accumulates the device information in association with an execution date and time of the acquisition process and, for a printing device on which the device information is not acquired, accumulates information indicating that the printing device on which the device information is not acquired is not in connection in association with the execution date and time of the acquisition process; and a creation unit that creates a report based on the accumulated information for the printing devices included in the list.

According to the present invention, it is possible to create a report including not only the usage state of a printing device in connection at the time of report output but also the usage state of a printing device that was replaced and is no longer connected even when the printing device is replaced under a subscription contract or the like. Accordingly, the user may understand the usage state including the usage state of the printing device that was connected in the past and was replaced and is no longer connected at the time of report output. Further features of the present invention will become apparent from the following description of exemplary embodiments with reference to the attached drawings.

DESCRIPTION OF THE EMBODIMENTS

First Embodiment

System Configuration

FIG.1is a diagram illustrating an overall configuration of a system in one embodiment of the present invention.

The system of the present embodiment includes a personal computer (PC)100, a device101, and a local area network (LAN)102, and the PC100and the device101are connected so as to be able to communicate with each other via the LAN102. The LAN102may be wired or wireless.

The PC100is an example of an information processing apparatus and has predetermined operating system (OS) (not illustrated) installed therein. Further, a device management application300described later is installed in the PC100. The device management application300acquires status information on the device101connected to the PC100from the device101and displays the information on a graphical user interface (GUI) described later of the device management application300. Note that the status information on the device101refers to information such as apparatus status that indicates availability of printing, an occurrence state of warnings and errors, or the like, a remaining amount of each color toner loaded in the device101, and the number of printed sheets that indicates the cumulative total number of printed sheets that have been printed by the device101.

The device101is an example of an image forming device (printing device) such as a printer or an MFP and may have not only a printing function but also a FAX function, a copying function, a scanner function, or a function such as file transmission. The device101performs an output process such as printing in accordance with an instruction from the PC100. Note that a plurality of devices101are connected to the LAN102and may be configured to be able to communicate with the PC100, respectively.

Hardware Configuration of Information Processing Apparatus

FIG.2is a diagram illustrating an example of a hardware configuration of the PC100.

As illustrated inFIG.2, the PC100has an input device205that receives user operation input, such as a keyboard or a pointing device, and a display unit202that provides visual output information feedback to the user.

Further, the PC100is provided with storage devices, namely, a RAM203that stores various programs or execution information in the present embodiment, an external memory206such as a hard disk drive (HDD) or a flexible disk drive (FDD), and a ROM204.

Furthermore, the PC100has an interface device I/O207that communicates with an external apparatus and a CPU201that executes a program. Note that a form of connection to a peripheral apparatus may be wired or wireless. The PC100is connected to the device101via the I/O207.

Software Configuration

FIG.3is a diagram illustrating an example of a software configuration of a device management application300executed in the PC100. Various units illustrated inFIG.3are implemented when the CPU201loads a program of the device management application300stored in the ROM204or the external memory206into the RAM203and executes the program.

The device management application300has a device management unit301, a report output unit302, a device information acquisition unit303, an input unit304, and a window display unit305as the software configuration.

The device management unit301manages device information on the device101that is a management target of the device management application300. Herein, the device101that is a management target represents a device that is a display target on the device management application300and refers to a device in a device list. The device information refers to the device list storing information used for identifying the device and device usage information storing information such as the number of printed sheets and the number of times for use of each function and is stored and managed in the external memory206by the device management unit301.

The report output unit302is responsible for a device usage report function in the device management application300and creates a device usage report from the device information stored in the external memory206. The device usage report refers to a report related to the usage state of a device, such as the number of printed sheets of the device in an aggregation period designated by the user. Note that the device usage report is created targeting the device101that is a management target of the device management application300.

The device information acquisition unit303detects the device101connected on the network and acquires device information. The acquisition of the device information is processed in the following flow, for example.

First, the device information acquisition unit303transmits a broadcast packet of simple network management protocol (SNMP) version1 (SNMPv1). The device101responds to an SNMPv1 request from the device information acquisition unit303. The device information acquisition unit303additionally acquires device information used in the device management application300for the device101from which the response has been returned. Further, for the device101managed in the device list by the device management unit301, the device information acquisition unit303regularly acquires device information including the number of printed sheets of the device machine and stores the device information via the device management unit301. Note that the acquisition of the device information may be configured to be performed by using any other schemes than the above. For example, the device information acquisition unit303may be notified of device information from the device side. Alternatively, another server (not illustrated) that manages the device may collect the device information, and the device information acquisition unit303may acquire the device information via the server.

The input unit304detects a user operation performed on the input device205via a GUI of the device management application300displayed by the window display unit305and acquires user operation information.

The window display unit305performs window display control such as displaying a GUI of the device management application300or accepting the user operation performed on a GUI.

GUI of Device Management Application

FIG.4AtoFIG.4Care diagrams each illustrating an example of a GUI400of the device management application300of the first embodiment.

The GUI400is displayed on the display unit202by the window display unit305.

Once the input unit304detects a user operation performed on the input device205, the input unit304passes the user operation information to the window display unit305, and the window display unit305displays, on the display unit202, the GUI400in accordance with the user operation information.

On the GUI400, information on the device list managed by the device management application300, an entry window used for designating the target and outputting the device usage report, an entry window used for changing the setting of the device management application300, or the like are displayed.

As illustrated inFIG.4A, in response to selection of a device tab410, the window display unit305displays information on the device list managed by the device management unit301of the device management application300on a device list display part411of the GUI400. Details of the device list will be described later.

In the device list display part411, the device connection state, a device name, a serial number, a model name, a last acquisition date and time, an IP address, and the total number of printed sheets are displayed for each device managed by the device management unit301.

In response to selection of a report tab420, the window display unit305displays a report output window as withFIG.4Bon the GUI400. In the report output window, designation of a report aggregation period is accepted in an aggregation period designation part421. Further, selection of a device targeted for report output is accepted in a target device selection part422. In the target device selection part422, all the devices in the device list including a device that is not in connection at the time of selection are displayed as options, and a device that is not in connection at the time of selection can also be selected as an output target of the report. In response to a click on the report output button423, the report output unit302outputs the report of the device designated in the target device selection part422.

In response to selection of a setting button430, the window display unit305displays an entry window as withFIG.4Cused for changing the setting of the device management application300on the GUI400. Further, in this entry window, in response to selection of a device information acquisition/storage setting part431, the window display unit305displays an entry window used for changing the setting of the device information acquisition/storage. After the user inputs the acquisition frequency of the device information in a device information acquisition frequency setting part432and inputs a storage period of the device information in a device information storage period setting part433, the device management unit301reads the input setting in response to a click on a setting apply button434. The device management unit301stores the read setting in the external memory206as a device information acquisition/storage setting file.

The device information acquisition/storage setting file is read by the device management unit301at the time of start of the device management application300. The device management unit301performs acquisition/storage of the device information at an acquisition frequency of the device information read from the device information acquisition/storage setting file. Further, the device management unit301references the storage period of the device information read from the device information acquisition/storage setting file to perform deletion of the device usage information for which the storage period has elapsed.

Table 1 illustrates an example of the data structure of the device list managed by the device management application300.

In the device list, each record represents a single device and includes information on a device ID, a device name, a model name, a serial number, a last connection date and time, an IP address, or the like.

The device ID is an ID allocated to a pair of the model name and the serial number, and an individual device can be identified by the value of the ID. The device name is any name that can be set by the user for each device. The device name can be changed via the GUI of the device management application or the GUI of the device. The model name indicates a model name of the device and uniquely indicates the type of the device. The serial number is a number allocated to an individual device and is not duplicated with a serial number allocated to another device having the same model name. The last connection date and time indicates the last date and time when the device information acquisition unit confirmed that the device was in connection and acquired the device information. The IP address is an IP address allocated to the device and indicates an IP address of the device in the last acquisition of device information.

The device list is stored in a comma-separated values (CSV) format in the external memory206of the PC100. In addition, the device list may be stored as a JavaScript object notation (JSON)-format file or an extensible markup language (XML)-format file or may be stored in an external database (not illustrated). The storage method and the storage format of the device list are not particularly limited.

Date Structure (Device Usage Information)

Table 2 illustrates an example of the data structure of device usage information managed by the device management application300.

The device usage information includes a device ID, a connection state, an IP address, the total number of printed sheets, or the like and is additionally stored every time the device information collection is performed.

The device ID corresponds to the device ID in the device list illustrated in Table 1 and uniquely identifies a device. The connection state indicates whether or not the device was in connection to the network at the time of device information collection. The acquisition date and time indicates a date and time when a device information acquisition process was performed. The IP address indicates an IP address of the device if the device is in connection to the network at the time of device information collection. If the device is not in connection to the network at the time of device information collection, the field of a value of the IP address is blank. The total number of printed sheets indicates the total number of printed sheets of the device included in the device information if the device is in connection to the network at the time of device information collection. If the device is not in connection to the network at the time of device information collection, the field of a value of the total number of printed sheets is blank.

The device usage information is stored in the CSV format in the external memory206of the PC100. In addition, the device usage information may be stored as a JSON-format file or an XML-format file. Further, the device usage information may be stored in an external database (not illustrated). The storage method and the storage format of the device usage information are not particularly limited.

Device Usage Report

Table 3 illustrates an example of the device usage report output by the report output unit302.

The device usage report includes information such as a device ID, a device name, a model name, a serial number, a start date and time of an aggregation period, an end date and time of the aggregation period, an increment of the total number of printed sheets, or the like.

The device ID, the device name, the model name, and the serial number are acquired from the device list illustrated in Table 1 in accordance with selection in the target device selection part422. The first acquisition date and time in an aggregation period and the last acquisition date and time in the aggregation period indicate the first acquisition date and time of device usage information and the last acquisition date and time of device usage information on a device in a connected state in the aggregation period designated on a GUI421of the device management application300. The increment of the total number of printed sheets indicates a difference between the first acquired total number of printed sheets and the last acquired total number of printed sheets in an aggregation period designated on the GUI421of the device management application300.

The device usage report is stored in the CSV format in the external memory206of the PC100. The storage method and the storage format of the device usage report are not particularly limited.

Execution Process of Device Information Collection

FIG.5is a flowchart illustrating an example of an execution process procedure of device information collection performed by the device management application300. This example illustrates a process to perform device information collection for all the devices in the device list illustrated in Table 1 in accordance with a frequency of information collection set by the user on a GUI432of the device management application300illustrated inFIG.4C.

Note that the processes of the flowcharts illustrated inFIG.5andFIG.6described later are implemented when the CPU201loads a program of the device management application300stored in the ROM204or the external memory206into the RAM203and executes the program.

In S501, the device management unit301of the device management application300reads a device list stored in the external memory206.

Next, in S502, the device management unit301instructs the device information acquisition unit303to acquire device information. The instructed device information acquisition unit303acquires information such as a device name, a model name, a serial number, an IP address, the total number of printed sheets, or the like from all the devices on the network (device information acquisition process).

Next, in S503, the device management unit301receives the device information acquired by the device information acquisition unit303and compares the acquired device information with the device list acquired in S501described above. Then, if the device information includes information on a device not present in the device list, the information on the device is added to the device list.

Next, in S504, the device management unit301selects one device which has not performed the process of S504to S508as a target device out of the device list.

Next, in S505, the device management unit301adds a row of the target device to the device usage information and stores the acquisition date and time of the information (execution date and time of the device information acquisition process (S502)).

Next, in S506, the device management unit301determines whether or not the target device is connected to the network. This determination is to check whether or not information on the target device is included in the device information received in S503described above and determine that the target device is in connection if the information thereon is included or determine that the target device is not in connection if the information thereon is not included.

If the target device is in connection to the network (S506, Yes), the device management unit301proceeds with the process to S507.

In S507, the device management unit301additionally stores information indicating that the target device is in a “connected state” and the device information on the target device in the device usage information and proceeds with the process to S509.

In contrast, if the target device is not in connection to the network (S506, No), the device management unit301proceeds with the process to S508.

In S508, the device management unit301additionally stores information indicating that the target device is an “unconnected state” in the device usage information and proceeds with the process to S509.

In S509, the device management unit301checks whether or not the process of S504to S508has been performed on all the devices in the device list. If there is an unprocessed device (S509, No), the device management unit301returns the process to S504and performs the process of S504and the subsequent steps.

In contrast, if the process of S504to S508has been performed on all the devices (S509, Yes), the device management unit301ends the process of this flowchart.

With the above process, after a device newly connected to the network is added to a device list, device information on all the devices in the device list can be acquired. At this time, for a device on which the device information has been acquired, information indicating that the device is in a “connected” state and the acquired device information are added to the device usage information. On the other hand, for a device on which the device information has not been acquired, information indicating that the device is in an “unconnected” state is added to the device usage information. This makes it possible to generate a device list and device usage information on a device that has been connected at least once in the past.

Execution Process of Device Usage Report Output

FIG.6is a flowchart illustrating an example of an execution process procedure of device usage report output performed by the device management application300of the first embodiment. This example illustrates a process to output a device usage report illustrated in Table 3 from the device usage information illustrated in Table 2 in the aggregation period for a device designated by the user on the GUI400of the device management application300as withFIG.4B. After a target of a report is designated in the aggregation period designation part421and the target device selection part422, in response to accepting a user operation on the report output button423, the input unit304notifies the device management unit301that the user operation has been accepted. In response to this notification, the device management unit301starts the device usage report output process inFIG.6.

First, in S601, the device management unit301acquires a list of devices selected in the target device selection part422and instructs the report output unit302to output a device usage report for an aggregation period designated in the aggregation period designation part421.

In S602, the report output unit302selects one device which has not performed the process of S602to S604as a target device out of the list of devices targeted for report output and adds a row of the target device to the device usage report.

In S603, the report output unit302checks device usage information in the aggregation period for the target device. If there is device usage information on a device in a connected state in the aggregation period for the target device (S603, Yes), the report output unit302proceeds with the process to S604.

In S604, the report output unit302acquires the first acquisition date and time and the last acquisition date and time in the aggregation period from the device usage information in the aggregation period for the target device and outputs the acquired date and time to the row of the target device of the report. Further, the report output unit302outputs a difference between the first acquired total number of printed sheets and the last acquired total number of printed sheets in the aggregation period to the row of the target device of the report as the increment of the total number of printed sheets and proceeds with the process to S605.

In contrast, if there is no device usage information on a device in a connected state in the aggregation period for the target device (S603, No), the report output unit302proceeds with the process to S605.

In S605, the report output unit302checks whether or not the process of S602to S604has been performed on all the devices in the list of devices targeted for report output. If there is an unprocessed device (S605, No), the report output unit302returns the process to S602and performs the process of S602and the subsequent steps.

In contrast, if the process of S602to S604has been performed on all the devices in the list of devices targeted for report output (S605, Yes), the report output unit302ends the process of this flowchart.

With the above process, for a device designated by the user, a device usage report in an aggregation period can be output regardless of the connection state of the device at the time of report output. That is, it is possible to create a report including not only the usage state of a device in connection at the time of report output but also the usage state of a device that was replaced and is no longer connected. This enables the user to understand the usage state of devices including the usage state of a device that was connected in the past but was replaced and is no longer connected at the time of report output.

Second Embodiment

In the first embodiment, the configuration in which a report about information on a counter or the like is output as a history also for an unconnected device has been described. Note that, if which device the unconnected device was replaced with can be understood from report output, this can further improve usability. Thus, in the second embodiment, a configuration in which a device replaced from and a device replaced with are grouped as devices of the same group and a report is output collectively for devices of the same group will be described.

GUI of Device Management Application

FIG.7AandFIG.7Bare diagrams each illustrating an example of the GUI400of the device management application300of the second embodiment.

On the GUI400, information on a device list or a group managed by the device management application300, an entry window used for designating a target and outputting a device usage report, an entry window used for changing the setting of the device management application300, and the like are displayed. Differences from the first embodiment will be described below, and description for the same configuration will be omitted.

In response to selection of the device tab410, the window display unit305displays an all-device display button711, a group list712, and a group creation button714on the GUI400as illustrated inFIG.7A. When the all-device display button711is selected, device information on all the devices in the device list is displayed in the device list display part411in the same manner asFIG.4A.

In response to selection of a group713from the group list712, the window display unit305displays device information on devices included in the group713in the device list display part411.

Further, selection of the group creation button714enables creation of a new group composed of devices in the device list. Herein, since a device not in connection at the time of group creation is also included in the device list, a group composed of devices before and after replacement can be created. The creation of a group is performed by the device management unit301, for example.

In response to selection of the report tab420, the window display unit305displays a report output window as withFIG.7Bon the GUI400. In the report output window, designation of a report aggregation period is accepted in the aggregation period designation part421. Further, selection of a device targeted for report output is accepted in the target device selection part422, and selection of a group targeted for report output is accepted in a target group selection part721. In response to a click on the report output button423, the report output unit302outputs a report on the device designated in the target device selection part422and a group designated in the target group selection part721.

Table 4 illustrates an example of the data structure of group information managed by the device management application300.

The group information has a group ID, a group name, and a device ID.

The group ID is an ID allocated to each group at the time of group creation, and a group can be identified by the value of the ID. The group name is a name that can be set by the user for each group. The group name can be changed via the GUI400of the device management application. The device ID is a device ID of a device included in a group and corresponds to the device ID in the device list illustrated in Table 1.

The group information is stored in the CSV format in the external memory206of the PC100. In addition, the group information may be stored as a JSON-format file or an XML-format file or may be stored in an external database (not illustrated). The storage method and the storage format of the group information are not particularly limited.

Device Usage Report

Table 5 illustrates an example of the device usage report output by the report output unit302. Differences from the first embodiment will be described below.

The device usage report includes information on a group/device ID, a group/device name, a model name, a serial number, a start date and time of an aggregation period, an end date and time of an aggregation period, an increment of the total number of printed sheets, or the like. Each record represents any of a group selected in the target group selection part721, a device included in a group selected in the target group selection part721, and a device selected in the target device selection part422.

The group/device ID indicates a group ID, a device ID, or a value combining a group ID and a device ID. For a group selected in the target group selection part721, a group ID is output (“Grp00001” in the example of Table 5). For a device selected in the target device selection part422, a device ID is output (“Dev00001” in the example of Table 5).

For a device included in a group selected in the target group selection part721, a value combining a group ID and a device ID is output (“Grp00001|Dev00002” or “Grp00001|Dev00003” in the example of Table 5).

The group/device name indicates a group name or a device name. For a group selected in the target group selection part721, a group name is output (“XX branch, 2F” in the example of Table 5). For a device selected in the target device selection part422, a device name is output (“XX branch, 1F” in the example of Table 5). For a device included in a group selected in the target group selection part721, a device name is output (“XX branch, 2F (old)” or “XX branch, 2F (new)” in the example of Table 5).

For a group selected in the target group selection part721, the fields of a model name and a serial number are blank. As the first acquisition date and time in an aggregation period and the last acquisition date and time in an aggregation period, the first date and time and the last date and time are output from the first acquisition date and time in an aggregation period and the last acquisition date and time in the aggregation period for a device included in a group, respectively. As the increment of the total number of printed sheets, a sum of increments of the total number of printed sheets for a device included in a group is output. In the example of Table 5, a sum “450” of an increment “240” of the total number of printed sheets for “Dev00002” and an increment “210” of the total number of printed sheets for “Dev00003” is output as the increment of the total number of printed sheets for “Grp00001”.

Execution Process of Device Usage Report Output

FIG.8is a flowchart illustrating an example of an execution process procedure of device usage report output performed by the device management application300of the second embodiment. This example illustrates a process to output a device usage report illustrated in Table 5 from the device usage information illustrated in Table 2 in an aggregation period for a device/group designated by the user on the GUI400of the device management application300as withFIG.7B. After a target for a report is designated in the aggregation period designation part421, the target device selection part422, and the target group selection part721, in response to accepting a user operation via the report output button423, the input unit304notifies the device management unit301that the user operation has been accepted. In response to this notification, the device management unit301starts a device usage report output process ofFIG.8. Note that the process of the flowchart illustrated inFIG.8is implemented when the CPU201loads a program of the device management application300stored in the ROM204or the external memory206into the RAM203and executes the program.

First, in S801, the device management unit301acquires a list of devices/groups selected in the target device selection part422and the target group selection part721. Furthermore, the device management unit301passes the acquired list to the report output unit302and instructs the report output unit302to output a device usage report for an aggregation period designated in the aggregation period designation part421.

Next, in S802, the report output unit302checks whether or not a device is included in the received list of devices/groups. If no device is included (S802, No), the report output unit302proceeds with the process to S807.

In contrast, if a device is included in the received list of devices/groups (S802, Yes), the report output unit302proceeds with the process to S803. Note that, since the process of S803to S806is the same as the process of S602to S605ofFIG.6, the description thereof will be omitted.

In S807, the report output unit302checks whether or not a group is included in the received list of devices/groups. If no group is included (S807, No), the report output unit302ends the process of this flowchart.

In contrast, if a group is included in the received list of devices/groups (S807, Yes), the report output unit302proceeds with the process to S808.

In S808, the report output unit302selects one group which has not performed the process of S808to S813as a target group from the list of groups targeted for report output and acquires the device list of the target group.

Next, in S809, the report output unit302selects an unprocessed device as a target from a device list of the target group and adds a row of the target device of the target group to the device usage report.

Next, in S810, the report output unit302checks whether or not there is device usage information on a device in a connected state in the aggregation period for the target device. Then, if there is device usage information on a device in a connected state in the aggregation period (S810, Yes), the report output unit302proceeds with the process to S811.

In S811, the report output unit302acquires the first acquisition date and time and the last acquisition date and time in the aggregation period from the device usage information in the aggregation period and outputs the acquired first acquisition date and time and the acquired last acquisition date and time to the row of the target device of the target group in the report. Further, the report output unit302outputs a difference between the first acquired total number of printed sheets and the last acquired total number of printed sheets in the aggregation period to the row of the target device of the target group in the report as an increment of the total number of printed sheets. After S811, the report output unit302proceeds with the process to S812.

In contrast, if there is no device usage information on a device in a connected state in the aggregation period (S810, No), the report output unit302proceeds with the process to S812.

In S812, the report output unit302checks whether or not the process of S809to S811has been performed on all the devices in the device list of the target group. If there is an unprocessed device (S812, No), the report output unit302returns the process to S809and performs the process of S809and the subsequent steps.

In contrast, if the process of S809to S811has been performed on all the devices in the device list of the target group (S812, Yes), the report output unit302proceeds with the process to S813.

In S813, the report output unit302finds the increment of the total number of printed sheets of the target group from the report output result for each device of the target group and outputs the found increment to the row of the target group in the report. That is, the value that is a sum of the increments of the total number of printed sheets for respective devices of the target group is output to the report as the increments of the total number of printed sheets of the group.

In S814, the report output unit302checks whether or not the process of S808to S813has been performed on all the groups in the list of groups targeted for report output. Then, if there is an unprocessed group (S814, No), the report output unit302returns the process to S808and performs the process of S808and the subsequent steps.

In contrast, if the process of S808to S813has been performed on all the groups in the list of groups targeted for report output (S814, Yes), the report output unit302ends the process of this flowchart.

With the above process, a device usage report in an aggregation period can be output for a device or a group designated by the user. For example, devices such as a device which was replaced and is no longer connected, a device which is currently in connection instead of the device replaced from, and the like that the user wishes to manage collectively are set into a group. This makes it possible to collectively manage the usage state of a device before replaced and a device after replaced as if these devices were a single device. As a result, the user is able to aggregate and collectively understand the usage state of the device before replaced and the device after replaced as if these devices were a single device.

Note that, in each of the embodiments described above, the configuration in which device information including the number of printed sheets from a device is acquired at a set frequency has been described. However, the device information acquired from a device described above may be configured to include operation information such as the number of printed sheets, usage information such as the number of times for use of each function, counter information on a supply part, error information, or the like. Further, pieces of such device information may be accumulated as a history, and a report may be created based on the accumulated information.

In each of the embodiments described above, device information is acquired at a set frequency from a device connected to a network, and in this operation, a device list is generated by adding a newly detected device. For a device on which the device information is acquired out of devices included in the device list, information indicating a “connected” state and the device information are accumulated as device usage information in association with the date and time of the acquisition process. In contrast, for a device on which the device information is not acquired, information indicating an “unconnected” state is accumulated as device usage information in association with the date and time of the acquisition process. Furthermore, for a device designated out of the device list, a report is created based on device usage information corresponding to a designated aggregation period. In accordance with such a configuration, a device usage report in the aggregation period can be output for a device (an image forming device, a printing device) or a group designated by the user regardless of the connection state of the device at the time of report output. That is, it is possible to create a report including not only the usage state of a device which is in connection at the time of the report output but also the usage state of a device which was replaced and is no longer connected. This enables the user to understand the usage state of a device including the usage state of a device which was connected in the past but was replaced and is no longer connected at the time of report output.

The structure and contents of the various data described above are not limited to the above descriptions, and the various data may have various structures and contents depending on the use and purpose.

Although some embodiments have been described above, the present invention may be implemented as, for example, a system, apparatus, method, program, storage medium, or the like. Specifically, the present invention may be applied to a system comprising multiple apparatuses, or may be applied to a device comprising a single apparatus.

In addition, all of the configurations formed by combining the above embodiments are also included in the scope of the present invention.

Other Embodiments

This application claims the benefit of Japanese Patent Application No. 2021-189303, filed on Nov. 22, 2021, which is hereby incorporated by reference herein in its entirety.