JP7574561B2 - Information processing device and information processing program - Google Patents

Description

The present invention relates to an information processing device and an information processing program.

Patent Document 1 discloses an information processing device that aims to support the improvement of business issues by utilizing information generated by devices used by users, and includes a collection means for collecting job logs and document image logs, a job classification means for classifying job logs by type, an image classification means for classifying image logs by type, and a compilation means for compiling usage records for combinations of job log types and image log types.

Patent Document 2 discloses a method for improving the accuracy of counter confirmation, which involves extracting devices for which the amount of consumables usage is to be confirmed based on a contract ID, obtaining a closing date for checking the amount of consumables usage that is specified for each extracted device, and then referencing a log that records the amount of consumables usage to check whether there is a confirmation date by the closing date on which the amount of usage was confirmed, and if there is no confirmation date in the log, changing the procedure for checking the amount of usage according to priority data defined by the contract ID.

Patent Document 3 discloses that the objective of an information management system is to process information obtained from each gaming device based on items specified by a terminal computer, and to compile and display information such as the total sales amount of multiple gaming devices installed in a certain area and information on each type of game that each gaming device has, and that the gaming device information stored on a server is processed based on instructions from the terminal computer regarding the desired compilation range, and the processed gaming device information is displayed using a spreadsheet program, allowing system users to easily extract only the desired information from the gaming device information stored on the server, compile the necessary information, and display it on the terminal.

JP 2019-091242 A JP 2008-250201 A JP 2000-176160 A

When tallying up billing data for a customer's use of a device, tallying is done for each customer on a predetermined closing date within the month. However, some customers may have multiple closing dates within the same month, and a configuration in which tallying up data on a predetermined closing date within the month results in double tallying. Therefore, the present invention aims to provide an information processing device and information processing program that can perform tallying up billing data for a customer's use of a device without double tallying, even if there are multiple closing dates within the same month.

The gist of the present invention to achieve the above object resides in the following inventions. Note that the "claims" below refer to the claims as originally filed.
The invention of claim 1 is an information processing device comprising a memory and one or more processors, the memory stores the date and time when the tally is performed for each device in correspondence with information indicating whether or not the data has been tallied, and when the date and time when the tally is performed occurs multiple times a month, and if the information indicates that the data has been tallied for the target device, the processor tallies the usage of the device since the date and time when the tally was performed.

The invention of claim 2 is the information processing device of claim 1, in which the memory further stores the device corresponding to the contract and the date and time when the tally is performed for the contract, and when the first date and time when the tally is performed for the target contract differs from the second date and time when the tally is performed for the device corresponding to the contract, the processor performs the tally using the date and time when the tally is performed for the device as the first date and time.

The invention of claim 3 is the information processing device of claim 2, in which the processor, when a first date and time for performing the tally for the target contract differs from a second date and time for performing the tally for the device corresponding to the contract, changes the date and time for performing the tally for the device in the memory to the first date and time, and controls the display device to display a notice of the change.

The invention of claim 4 is the information processing device of claim 1, in which, when a first date and time for performing the tally at the target business establishment is different from a second date and time for performing the tally for the equipment installed at the business establishment, the processor performs the tally using the date and time for performing the tally for the equipment as the first date and time.

The invention of claim 5 is the information processing device of claim 4, in which the processor, when a first date and time for performing the tally at the target business establishment is different from a second date and time for performing the tally for the device installed at the business establishment, changes the date and time for performing the tally for the device in the memory to the first date and time, and controls the display device to display a notice of the change.

The invention of claim 6 is the information processing device of claim 1, in which the processor controls to tally up the tabulated results for each device for each business establishment where the device is installed, tally up the tabulated results for each business establishment for each contract, and display on a display device one or more of the tabulated results for each device, the tabulated results for each business establishment, or the tabulated results for each contract.

The invention of claim 7 is the information processing device of claim 6, in which the processor controls the device to change the date and time for tallying the device to the first date and time when the first date and time for tallying the target contract is different from the second date and time for tallying the device corresponding to the contract, and to state that the change has been made in the tallying results for each contract.

The invention of claim 8 is the information processing device of claim 6, in which the processor controls the device to change the date and time for tallying the data on the device to the first date and time when the first date and time for tallying the data on the device at the business establishment in question differs from the second date and time for tallying the data on the device at the business establishment, and to state that the change has been made in the tallying results for each business establishment.

The invention of claim 9 is an information processing program for causing the processor to execute a process in which the memory of a computer having a memory and one or more processors stores the date and time when the tally is performed for each device in association with information indicating whether or not the tally has been performed, and if the date and time when the tally is performed occurs multiple times a month, and if the information indicates that the tally has been performed for the target device, the processor tallys up the usage of the device since the date and time when the tally was performed.

According to the information processing device of claim 1, when tallying up billing for a customer's use of a device, even if there are multiple closing dates in the same month, tallying up billing can be done without double tallying.

According to the information processing device of claim 2, when the first date and time for performing the tally for a contract is different from the second date and time for performing the tally for a device corresponding to the contract, the tally can be performed with the date and time for performing the tally for that device as the first date and time.

According to the information processing device of claim 3, when the first date and time for performing the tally for a contract differs from the second date and time for performing the tally for a device corresponding to the contract, the date and time for performing the tally for that device in the memory can be changed to the first date and time, and a display device can be controlled to display a notice of the change.

According to the information processing device of claim 4, when the first date and time for performing the tally at the business establishment is different from the second date and time for performing the tally for the device installed at the business establishment, the tally can be performed using the date and time for performing the tally for the device as the first date and time.

According to the information processing device of claim 5, when the first date and time when the tally is performed at the business establishment is different from the second date and time when the tally is performed on the device installed at the business establishment, the date and time when the tally is performed on the device in the memory is changed to the first date and time, and the change is displayed on the display device.

According to the information processing device of claim 6, it is possible to control the display device to display one or more of the tabulated results for each device, the tabulated results for each business location, or the tabulated results for each contract.

According to the information processing device of claim 7, if the first date and time for performing the tally for a contract is different from the second date and time for performing the tally for a device corresponding to that contract, the date and time for performing the tally for that device can be changed to the first date and time, and the change can be controlled so as to be indicated in the tally results for each contract.

According to the information processing device of claim 8, if the first date and time when the tally is performed at a business establishment is different from the second date and time when the tally is performed on a device installed at that business establishment, the date and time when the tally is performed on that device can be changed to the first date and time, and the change can be controlled so as to be indicated in the tally results for each business establishment.

According to the information processing program of claim 9, when tallying up billing data for a customer's use of a device, even if there are multiple closing dates in the same month, tallying up billing data can be performed without double tallying up billing data.

FIG. 2 is a conceptual module configuration diagram of a configuration example of the present embodiment. FIG. 1 is an explanatory diagram showing an example of a system configuration using the present embodiment. FIG. 2 is a module configuration diagram showing a specific configuration example of the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. 4 is a flowchart showing an example of processing according to the present embodiment. FIG. 2 is an explanatory diagram showing a display example according to the present embodiment. FIG. 4 is an explanatory diagram illustrating an example of the data structure of a contract information table. FIG. 2 is an explanatory diagram illustrating an example of a data structure of a business establishment information table; 11 is an explanatory diagram illustrating an example of the data structure of a device information table; FIG. 4 is an explanatory diagram illustrating an example of the data structure of a job information table. 13 is an explanatory diagram illustrating an example of the data structure of a model-specific tally result table; FIG. FIG. 13 is an explanatory diagram illustrating an example of the data structure of a business-specific tally result table. FIG. 13 is an explanatory diagram illustrating an example of the data structure of a contract-based tally result table. FIG. 11 is an explanatory diagram illustrating an example of the data structure of a compilation history table;

Hereinafter, a preferred embodiment of the present invention will be described with reference to the drawings.
FIG. 1 shows a conceptual module configuration diagram of an example of the configuration of this embodiment.
In addition, a module generally refers to a logically separable piece of software (including a computer program as an interpretation of "software"), hardware, or the like. Therefore, in this embodiment, a module refers not only to a module in a computer program, but also to a module in a hardware configuration. Therefore, this embodiment also describes a computer program for functioning as those modules (for example, a program for causing a computer to execute each procedure, a program for causing a computer to function as each means, a program for causing a computer to realize each function), a system, and a method. However, for convenience of explanation, words such as "store" and "store" are used, but these words mean that, when the embodiment is a computer program, the storage device stores the information, or the storage device stores the information. In addition, a module may correspond one-to-one to a function, but in implementation, one module may be configured with one program, multiple modules may be configured with one program, or conversely, one module may be configured with multiple programs. In addition, multiple modules may be executed by one computer, or one module may be executed by multiple computers by computers in a distributed or parallel environment. In addition, one module may include other modules. In addition, hereinafter, the term "connection" is used not only for physical connection but also for logical connection (e.g., data transfer, instruction, reference relationship between data, login, etc.). "Predetermined" means that it is determined before the target processing, and is used to include the meaning of being determined according to the situation/state at that time or according to the situation/state up to that point, not only before the processing according to this embodiment begins, but also after the processing according to this embodiment begins, as long as it is before the target processing. When there are multiple "predetermined values", each may be a different value, or two or more values ("two or more values" includes all values, of course) may be the same. In addition, the description "if A, do B" is used to mean "determine whether A is the case, and if it is determined that A is the case, do B". However, this does not include cases where it is not necessary to determine whether A is the case. In addition, when things are listed, such as "A, B, C", etc., it is an example list unless otherwise specified, and includes the case where only one of them is selected (for example, only A).
Furthermore, a system or device may be configured by connecting multiple computers, hardware, devices, etc. via a communication means such as a network ("network" includes one-to-one communication connections), or may be realized by a single computer, hardware, device, etc. "Device" and "system" are used as synonyms. Of course, a "system" does not include anything that is merely a social "mechanism" (i.e., a social system) that is an artificial arrangement.
Furthermore, for each process by each module, or for each process when multiple processes are performed within a module, the target information is read from the storage device, and after the process is performed, the processing results are written to the storage device. Therefore, the description of reading from the storage device before processing and writing to the storage device after processing may be omitted.

The information processing device 100 according to this embodiment has a function of performing tallying processing of devices being used. As shown in the example of FIG. 1, the information processing device 100 has at least a processor 105 and a memory 110, and is configured with a bus 198 for connecting them to exchange data. In addition, the information processing device 100 may have an output device 185, a reception device 190, and a communication device 195. Data is exchanged between the processor 105, memory 110, output device 185, reception device 190, and communication device 195 via the bus 198.

The block diagram shown in the example of FIG. 1 also shows an example of the hardware configuration of a computer that realizes this embodiment. The hardware configuration of the computer on which the program of this embodiment is executed is a computer as shown in FIG. 1, specifically a personal computer, a computer that can be a server, etc. As a specific example, a processor 105 is used as the processing unit, and a memory 110 is used as the storage device.

There may be one processor 105 or multiple processors. Examples of processors 105 include a CPU (abbreviation for Central Processing Unit), a microprocessor, etc. When multiple processors 105 are used, the system may be either a tightly coupled multiprocessor or a loosely coupled multiprocessor. For example, multiple processor cores may be mounted in one processor 105. Furthermore, a system may be configured in which multiple computers are connected by a communication path to virtually behave as if they were a single computer. As a specific example, a loosely coupled multiprocessor may be configured as a cluster system or a computer cluster. The processor 105 executes the program in the program memory 140.

The memory 110 may include, for example, semiconductor memory inside the processor 105, such as a register or cache memory, a main memory that is a primary storage device configured by RAM (abbreviation of Random Access Memory) or ROM (abbreviation of Read Only Memory), or an internal storage device such as an HDD (abbreviation of Hard Disk Drive) or SSD (abbreviation of Solid State Drive) that has a function as a persistent storage device, an external storage device or auxiliary storage device such as a CD, DVD, Blu-ray (registered trademark) Disc, USB memory, or memory card, or may also include a storage device such as a server connected via a communication line.
The memory 110 has a data memory 120 that mainly stores data, and a program memory 140 that mainly stores programs. Note that the data memory 120 and the program memory 140 may store, in addition to the illustrated information and module programs, programs such as an OS for starting up the computer, and data such as parameters that change as appropriate during execution of the modules.

The output device 185 includes, for example, a display device 187, a printing device 189, etc. The display device 187, such as a liquid crystal display, an organic EL display, a three-dimensional display, a projector, etc., displays the processing results by the processor 105, the data in the data memory 120, etc. as text, image information, etc. The printing device 189, such as a printer, a multifunction device, etc., prints the processing results by the processor 105, the data in the data memory 120, etc. The output device 185 may also include a speaker, an actuator that vibrates a device, etc.
The reception device 190 includes, for example, an instruction reception device 192 and a document reading device 194. The instruction reception device 192, which includes a keyboard, a mouse, a microphone, a camera (including a gaze detection camera, etc.), receives data based on user operations (including movements, voice, gaze, etc.) on these devices.
Also, there may be a device, such as a touch screen, that has the functions of both the display device 187 and the instruction receiving device 192. In that case, even if there are no physical keys, the keyboard function may be realized by drawing a keyboard (also called a software keyboard or a screen keyboard) on the touch screen by software.
As the user interface, mainly the display device 187 and the instruction receiving device 192 are used.
A document reading device 194 such as a scanner or camera reads or photographs a document and accepts the resulting image data.
The communication device 195 is a communication line interface such as a network card for connecting to other devices via a communication line.

In the present embodiment, the computer program is implemented by loading a computer program, which is software, into the program memory 140 of the present hardware configuration, and the software and hardware resources work together to realize the present embodiment. In other words, the present embodiment is specifically realized by software-based information processing using hardware resources (including at least the processor 105, memory 110, and possibly the output device 185, the receiving device 190, and the communication device 195), and utilizes the laws of nature as a whole.
1 is one example of the hardware configuration, and the present embodiment is not limited to the configuration shown in FIG. 1, and may be configured in any manner that can execute the modules described in the present embodiment. For example, a GPU (abbreviation of Graphics Processing Unit, including GPGPU (abbreviation of General-Purpose computing on Graphics Processing Units)) may be used as the processor 105, or some of the modules may be executed by dedicated hardware (for example, an application specific integrated circuit (a specific example is ASIC (abbreviation of Application Specific Integrated Circuit)) or a reconfigurable integrated circuit (a specific example is FPGA (Field-Programmable Gate Array)). 1 may be connected to each other via communication lines, and may operate in cooperation with each other. In particular, the system may be incorporated in a personal computer, a portable information and communication device (including a mobile phone, a smartphone, a mobile device, a wearable computer, etc.), an information appliance, a robot, a copier, a fax, a scanner, a printer, a multifunction device (an image processing device having two or more functions of a scanner, a printer, a copier, a fax, etc.), etc.

The processor 105 is connected to the memory 110, the output device 185, the reception device 190, and the communication device 195 via the bus 198. The processor 105 executes processing according to a computer program that describes the execution sequence of each module, which is a program in the program memory 140. For example, when a user operation is received by the instruction reception device 192, the processor 105 executes processing by a module in the program memory 140 that corresponds to that operation, and stores the processing results in the data memory 120, outputs them to the display device 187, or controls the communication device 195 to transmit them to another device.

The memory 110 has a data memory 120 and a program memory 140, and is connected to the processor 105, the output device 185, the reception device 190, and the communication device 195 via a bus 198.

The data memory 120 includes a device usage status storage module 122 and a device tally storage module 124 .
The device usage status storage module 122 stores the usage status of each device. The device usage status storage module 122 stores the date and time when the tally is performed for each device and information indicating whether or not the tally has been performed, in association with each other.
Here, the "date and time of tallying" is, for example, also called the closing date, and is determined by the contract with the customer, and is a predetermined date and time within the month. In other words, the "date and time of tallying" for the equipment installed under the contract will be the same. However, this may be changed at the request of the customer, etc., and the date and time of tallying may be multiple times a month.
The "date and time when the tally is performed" may be determined for each business establishment. In this case, the "date and time when the tally is performed" of the devices installed in the business establishment will be the same.
Furthermore, the "date and time for tallying" may be determined for each device. In this case, however, if the "date and time for tallying" determined by the contract differs from the "date and time for tallying" of the device, the "date and time for tallying" determined by the contract shall be followed. This is because there is a high possibility that the "date and time for tallying" of the device is incorrectly set. Furthermore, if the "date and time for tallying" determined for each business location differs from the "date and time for tallying" of the device, the "date and time for tallying" determined for that business location shall be followed. This is because there is a high possibility that the "date and time for tallying" of the device is incorrectly set.
The device usage status storage module 122 may further store the device corresponding to the contract and the date and time when the tally is performed for that contract.

The equipment tally storage module 124 stores the tally results generated by the tally module 142. Examples of tally results include tally results by equipment, by business establishment, or by contract.

The program memory 140 stores a counting module 142 and a display control module 144 .
The counting module 142 counts the usage of the target device.
Then, in the case where the tallying occurs multiple times a month, if the information in the device usage status storage module 122 for the target device indicates that tallying has already been performed, the tallying module 142 tallyes up the usage of the device from the date and time when the tallying was performed.
In addition, when the first date and time for performing the tally for the target contract is different from the second date and time for performing the tally for the equipment corresponding to that contract, the tally module 142 may perform the tally using the date and time for performing the tally for that equipment as the first date and time.

In addition, when the first date and time for performing the tally at the target business establishment is different from the second date and time for performing the tally for the equipment installed at that business establishment, the tally module 142 may perform the tally using the date and time for performing the tally for the equipment as the first date and time.
Furthermore, the tallying module 142 may tally up the tallying results for each device for each business establishment in which the device is installed, and tally up the tallying results for each business establishment for each contract.

If the first date and time for tallying for the target contract differs from the second date and time for tallying for the device corresponding to the contract, the display control module 144 changes the date and time for tallying for that device in the device usage status memory module 122 to the first date and time, and controls the display device 187 to display a notice of the change.
In addition, when a first date and time for tallying at the target business establishment is different from a second date and time for tallying for an equipment installed at that business establishment, the display control module 144 may be configured to change the date and time for tallying for that equipment in the equipment usage status memory module 122 to the first date and time, and to display on the display device a notice of the change.

Furthermore, the display control module 144 may perform control so that one or more of the tally results for each device, the tally results for each business establishment, or the tally results for each contract are displayed on the display device 187 .
In this case, if the first date and time for which the tally is performed for the target contract is different from the second date and time for which the tally is performed for the equipment corresponding to that contract, the tally module 142 may be configured to change the date and time for which the tally is performed for that equipment to the first date and time, and to indicate that this has been changed in the tally results for each contract.
In this case, if the first date and time at which the tally is performed at the target business establishment is different from the second date and time at which the tally is performed for the equipment installed at that business establishment, the tally module 142 may be configured to change the date and time at which the tally is performed for that equipment to the first date and time, and to control the tally module 142 so that the change is indicated in the tally results for each business establishment.

Fig. 2 is an explanatory diagram showing an example of a system configuration using this embodiment. Fig. 2 shows an image processing device 210, a mobile terminal 220, and a wearable device 230 as examples of devices to be managed. The image processing device 210 includes, for example, a copier, a fax machine, a scanner, a printer, a multifunction machine, etc. The mobile terminal 220 includes, for example, a mobile phone, a smartphone, etc. The wearable device 230 includes, for example, a smart watch that can measure the number of steps, heart rate, amount of exercise, calories burned, blood pressure, sleep state, etc.
At business establishment X, image processing device 210A, image processing device 210B, mobile terminal 220A, wearable device 230A, and administrator terminal 250A are each connected via an internal company communication line 280A, and are also connected to information processing device 100 via internal company communication line 280A and communication line 290.
At business establishment Y, image processing device 210C, image processing device 210D, mobile terminal 220B, mobile terminal 220C, wearable device 230B, wearable device 230C, and administrator terminal 250B are each connected via in-house communication line 280B. Also, they are connected to information processing device 100 via in-house communication line 280B and communication line 290.
The communication line 290 and the in-house communication line 280 may be wireless, wired, or a combination of these, and may be, for example, the Internet, an intranet, etc. as a communication infrastructure. Furthermore, the functions of the information processing device 100 may be realized as a cloud service.
The information processing device 100 tally up the usage of the image processing device 210, the mobile terminal 220, and the wearable device 230. For the image processing device 210, the number of copies, the number of prints, the number of scans, the number of faxes sent, etc. are the objects of tally up. For the mobile terminal 220, the number of times and the amount of use of an application installed in the mobile terminal 220 are the objects of tally up. For the wearable device 230, the number of times the wearable device 230 measures biological information such as blood pressure, etc. are the objects of tally up. For the wearable device 230, the biological information itself may be the object of tally up. For example, the average value of blood pressure, etc. may be calculated.
Then, the administrator of each business location uses the administrator terminal 250 to access the information processing device 100 and display the aggregated results of the usage, etc. of the equipment (image processing device 210, mobile terminal 220, wearable device 230) within each business location.

Conventionally, the tallying process is performed for all users at the end of the month. Therefore, it is not possible to handle cases where the closing date differs for each customer. In particular, in businesses related to multifunction printers, etc., differences in closing dates are allowed for each customer, so it is necessary to handle the following complexities: (1) There are devices with different closing dates even within the same contract or the same business. For example, when a new device is installed, even if the closing date of the device is standardized for the contract or business, the closing date may be different due to a mistake in the settings made by the person in charge. (2) There are cases where the closing date occurs more than once within the same month. For example, at the end of the year, the closing date may be the 1st and the 31st, etc. The information processing device 100, which is the present embodiment, is designed to perform tallying process that also handles these cases.

3 is a module configuration diagram showing a specific configuration example of the present embodiment. An information processing device 300 shows a specific configuration example of the information processing device 100. An IoT device 384 corresponds to the image processing device 210, the mobile terminal 220, and the wearable device 230 shown in the example of FIG. 2, and an administrator terminal 390 corresponds to the administrator terminal 250 shown in the example of FIG. 2.
In an office environment 392 corresponding to the business establishment shown in the example of FIG. 2, an IoT device 384 and an administrator terminal 390 are installed.
The IoT device 384 has an IoT data transmission module 382. The IoT data transmission module 382 is communicably connected to the IoT data receiving module 302 of the information processing device 300. The IoT data transmission module 382 transmits device information related to the office environment 392 (information such as a history of using the office environment 392, hereinafter also referred to as IoT data) to the information processing device 300.
The administrator terminal 390 is used by the administrator, and includes a display module 386 and a display request transmission module 388 .
The display module 386 is communicably connected to the display content forming module 352 of the information processing device 300. The display module 386 displays images, graphs, and the like formed by the information processing device 300. Examples of the display module 386 include a PC monitor, a browser, and a smartphone screen.
The display request transmission module 388 is communicably connected to the display request receiving module 340 of the information processing device 300. The display request transmission module 388 transmits a request to change the display content to the information processing device 300. Examples of the display request transmission module 388 include a browser, an HTML button or drop-down list, and an application button.

The information processing device 300 includes a data pre-processing module 330 , a visualization module 360 , a post-aggregation data storage module 362 , a data acquisition module 364 , and a rendering engine module 380 .
The data pre-processing module 330 includes an IoT data receiving module 302, a raw data storage module 304, a current day contract acquisition module 306, a target equipment acquisition module 308, an aggregation processing module 310, a contract information storage module 312, a business establishment information storage module 314, an equipment information storage module 316, a job information storage module 318, an aggregation processing history storage module 320, an aggregation processing logic storage module 322, and an aggregation processing logic setting module 324.
The IoT data receiving module 302 is connected to the raw data storage module 304 and the IoT data transmitting module 382. The IoT data receiving module 302 receives device information of the client-side IoT device 384. The IoT data receiving module 302 is constructed using, for example, a REST API, an API Gateway, or the like.
The raw data storage module 304 is connected to the IoT data receiving module 302. The raw data storage module 304 stores the device information received by the IoT data receiving module 302 without processing it. The raw data storage module 304 is constructed using, for example, an RDBMS or the like.

The tallying process logic setting module 324 is connected to the tallying process logic storage module 322. The tallying process logic setting module 324 sets a method for tallying device information for each purpose. The tallying process logic setting module 324 is constructed using, for example, Glue, which can be embedded with Python code.
The tallying process logic storage module 322 is connected to the tallying process module 310 and the tallying process logic setting module 324. The tallying process logic storage module 322 stores tallying process instruction information (a program indicating the procedure of the tallying process) set by the tallying process logic setting module 324.

The current day tally target contract acquisition module 306 is connected to the tally target device acquisition module 308 and the contract information storage module 312. The current day tally target contract acquisition module 306 acquires contract information from the contract information storage module 312. Only contract information with a tally target for the current day is extracted from the contract information storage module 312. The trigger for the execution timing is determined by schedule settings, etc. For example, the execution timing may be set to 12:00 pm every day, and contracts with a closing date on that day may be extracted.
The tally target equipment acquisition module 308 is connected to the current day tally target contract acquisition module 306, the tally processing module 310, and the equipment information storage module 316. The tally target equipment acquisition module 308 passes the current day tally target contract-specific equipment list 326 to the tally processing module 310. The tally target equipment acquisition module 308 acquires equipment information corresponding to (linked to) the contract extracted by the current day tally target contract acquisition module 306 from the equipment information storage module 316. In other words, it acquires a list of IoT equipment 384 installed under the target contract.
The tallying processing module 310 is connected to the tallying target equipment acquisition module 308, the job information storage module 318, the tallying processing history storage module 320, the tallying processing logic storage module 322, and the post-tallying data storage module 362. The tallying processing module 310 executes calculations such as addition and model evaluation on the contract information and equipment information extracted by the current day tallying target contract acquisition module 306 or the tallying target equipment acquisition module 308 based on the tallying processing instruction information in the tallying processing logic storage module 322.

The contract information storage module 312 is connected to the current day tally target contract acquisition module 306. The contract information storage module 312 stores contract information of the IoT device 384. If necessary, the contract information is extracted in response to a request from the current day tally target contract acquisition module 306. In addition to the contract information, the contract information storage module 312 may also store the history of the contract information (past contract information). For example, the contract information corresponds to information that associates the identification information of the contract with the contract contents including the closing date, etc. The contract information storage module 312 is constructed, for example, using an RDBMS or the like.
The business establishment information storage module 314 stores information about business establishments. For example, the information about business establishments includes information that associates business establishment identification information with contract identification information and the closing date at the business establishment. The business establishment information storage module 314 is constructed using, for example, an RDBMS.
The device information storage module 316 is connected to the tally target device acquisition module 308. The device information storage module 316 stores information about the IoT device 384, etc. If necessary, the device information storage module 316 extracts information about the IoT device 384, etc. in response to a request from the tally target device acquisition module 308. The device information storage module 316 is constructed using, for example, an RDBMS or the like.
The job information storage module 318 is connected to the tallying processing module 310. The job information storage module 318 stores the usage history and the like of the IoT device 384. If necessary, the usage history and the like are extracted from the IoT device 384 in response to a request from the tallying processing module 310. The job information storage module 318 is constructed using, for example, an RDBMS or the like.
The tallying process history storage module 320 is connected to the tallying process module 310. The tallying process history storage module 320 stores the results of tallying process by the tallying process module 310. The tallying process history storage module 320 is constructed using, for example, an RDBMS or the like.

The visualization module 360 includes a display request receiving module 340 , a request source determination module 342 , a rendering instruction sending module 344 , a screen design setting module 346 , a design instruction information storage module 348 , a rendering result receiving module 350 , and a display content forming module 352 .
The display request receiving module 340 is connected to a request source determining module 342 and a display request transmitting module 388. The display request receiving module 340 receives a display request from an administrator terminal 390, which is a client.
The request source determination module 342 is connected to the display request receiving module 340 and the rendering instruction transmitting module 344. The request source determination module 342 determines the request source and performs processes such as authentication and authorization.
The rendering instruction sending module 344 is connected to the request source determination module 342 and the rendering instruction receiving module 366. The rendering instruction sending module 344 sends a graph or image formation request to the rendering engine module 380 regarding a designation of a pie chart, a bar graph, etc. in accordance with the display request.
The screen design setting module 346 is connected to a design instruction information storage module 348. The screen design setting module 346 sets design instruction information that defines a content layout method such as a layout design. The design instruction information can change the screen layout for each device, for example. The design instruction information is constructed using, for example, an HTML template or the like.
The design instruction information storage module 348 is connected to the screen design setting module 346 and the display content formation module 352. The design instruction information storage module 348 stores the design instruction information set by the screen design setting module 346. The design instruction information storage module 348 is constructed using, for example, an RDBMS or the like.
The rendering result receiving module 350 is connected to the display content forming module 352 and the rendering result sending module 372. The rendering result receiving module 350 receives graphs and images formed by the rendering engine module 380. Information on the received graphs and images is constructed using, for example, HTML, PNG, or the like.
The display content forming module 352 is connected to the design instruction information storage module 348, the rendering result receiving module 350, and the display module 386. The display content forming module 352 forms the display content of graphs and images based on the design instruction information and the like in the design instruction information storage module 348. The formed information is transmitted to the administrator terminal 390. The formed content includes, for example, a view of a Web application that forms HTML.

The post-aggregation data storage module 362 is connected to the data acquisition module 364 and the aggregation processing module 310. The post-aggregation data storage module 362 stores the results of the aggregation processing performed by the data pre-processing module 330. The post-aggregation data storage module 362 is constructed using, for example, an RDBMS or the like.
The data acquisition module 364 is connected to the post-tallying data storage module 362 and the rendering execution module 370. The data acquisition module 364 acquires data to be rendered from the rendering execution module 370 of the rendering engine module 380. The acquired information includes, for example, a JDBC driver and SQL.

The rendering engine module 380 includes a rendering instruction receiving module 366 , a rendering execution module 370 , a rendering result sending module 372 , a rendering setting registration module 374 , and a rendering instruction information storage module 376 .
The rendering instruction receiving module 366 is connected to the rendering execution module 370 and the rendering instruction sending module 344. The rendering instruction receiving module 366 passes request information request source information 368 to the rendering execution module 370. The rendering instruction receiving module 366 receives a graph or image formation request from the visualization module 360.
The rendering execution module 370 is connected to the data acquisition module 364, the rendering instruction receiving module 366, the rendering result transmission module 372, and the rendering instruction information storage module 376. The rendering execution module 370 receives a rendering instruction (request information request source information 368) for a graph or image formation request, acquires necessary data from the data acquisition module 364, and forms an image based on the rendering instruction. It is also possible to change the graph type to a pie chart, a bar graph, or the like.
The rendering result transmission module 372 is connected to the rendering execution module 370 and the rendering result reception module 350. The rendering result transmission module 372 transmits the image formation result by the rendering execution module 370 to the visualization module 360.
The rendering setting registration module 374 is connected to the rendering instruction information storage module 376. The rendering setting registration module 374 sets rendering instruction information and stores it in the rendering instruction information storage module 376.
The rendering instruction information storage module 376 is connected to the rendering execution module 370 and the rendering setting registration module 374. The rendering instruction information storage module 376 stores the rendering instruction information set by the rendering setting registration module 374. The rendering instruction information storage module 376 is constructed using, for example, an RDBMS or the like.

4 is a flowchart showing an example of processing according to the present embodiment. This shows an example of processing in which the IoT device 384 transmits IoT data to the information processing device 300. This shows an example of processing in which IoT data is transmitted every time it is generated.
In step S400, use of the IoT device 384 occurs.
In step S402, device information and usage method (IoT data) are transmitted. For example, information to be transmitted as IoT data includes data such as a model code field 1502, a machine number field 1504, a number of divided processing sheets field 1506, a resolution field 1508, and a processing date and time field 1510 in a job information table 1500 described later in the example of FIG.
The processes in steps S400 and S402 are performed by the office environment 392 on the client side.

In step S404, IoT data is received.
In step S406, the IoT data is saved (permanently stored). Specifically, the IoT data is stored in a non-volatile storage device such as a hard disk.
The processes in steps S404 and S406 are performed by the data pre-processing module 330 of the information processing device 300 on the server side.

Fig. 5 is a flowchart showing a processing example according to the present embodiment. As with the flowchart shown in the example of Fig. 4, this shows a processing example in which the IoT device 384 transmits IoT data to the information processing device 300. However, unlike the flowchart shown in the example of Fig. 4, this shows a processing example in which IoT data is transmitted collectively. In this example, an example of transmission once a day is shown, but transmission may be performed multiple times a day, once every multiple days, etc.
In step S500, the schedule execution time arrives.
In step S502, the latest device information and daily usage method (IoT data) are transmitted. For example, information to be transmitted as IoT data includes data in a machine type code field 1502, a machine number field 1504, a number of divided processing sheets field 1506, a resolution field 1508, a processing date and time field 1510, and the like in a job information table 1500 described later in the example of FIG.
The processes in steps S500 and S502 are performed by the office environment 392 on the client side.

In step S504, IoT data is received.
In step S506, the IoT data is saved (permanently stored). Specifically, the IoT data is stored in a non-volatile storage device such as a hard disk.
The processes in steps S504 and S506 are performed by the data pre-processing module 330 of the information processing device 300 on the server side.

6 is a flow chart showing an example of processing according to this embodiment, which shows an example of calculation processing of the counting result, and corresponds to pre-processing of the display processing of the counting result.
In step S600, the schedule execution time occurs, which is the trigger for carrying out the process of this flowchart.
In step S602, a list of contracts 662 whose execution date matches the closing date is obtained from the contract information storage module 312. In other words, contracts whose closing date is today may be extracted. For example, the contract information table 1200 may be used. FIG. 12 is an explanatory diagram showing an example of the data structure of the contract information table 1200. The contract information table 1200 is stored in the contract information storage module 312.
The contract information table 1200 has a contract ID column 1202 and a company name column 1204. In this embodiment, the contract ID column 1202 stores information for uniquely identifying a contract (specifically, a contract ID (short for IDentification)). The company name column 1204 stores the company name.
For example, the first row of the contract information table 1200 indicates that the company name of the contract ID "AABBCC0001" is "Company A."
Furthermore, the closing date may be stored in the contract information table 1200. In other words, the contract and the closing date may be stored in correspondence with each other. In the example of step S602, a contract whose closing date matches the execution date may be extracted.

In step S604, the IoT device information 666 to be counted is obtained from the device information storage module 316.
In step S606, the device information is tallied. Details of the process in step S606 will be described later with reference to the flowcharts shown in the examples of FIGS.
In step S608, the counting result is stored in the post-counting data storage module 362.

Fig. 7 is a flowchart showing a processing example according to this embodiment. It is a specific example of the processing of step S606 in the flowchart shown in the example of Fig. 6. It is a flowchart of a processing example that can be used when there are devices (IoT devices 384) with different closing dates in the same business establishment.
In step S700, the schedule execution time arrives.
In step S702, the establishment list 762 to be counted for the current day is obtained from the establishment information storage module 314. For example, the establishment information table 1300 may be used. FIG. 13 is an explanatory diagram showing an example of the data structure of the establishment information table 1300. The establishment information table 1300 is stored in the establishment information storage module 314.
The business establishment information table 1300 has a contract ID column 1302, a business establishment code column 1304, a closing date column 1306, a destination column 1308, a sales company column 1310, and a maintenance contractor column 1312. The contract ID column 1302 stores a contract ID. The business establishment code column 1304 stores a business establishment code. The closing date column 1306 stores a closing date. The destination column 1308 stores a destination. The sales company column 1310 stores a sales company. The maintenance contractor column 1312 stores a maintenance contractor.
For example, the first row of the business establishment information table 1300 indicates that the business establishment code for the contract ID "AABBCC0001" is "DDEEFF0001", the closing date is "-1", the destination is "X", the sales company is "X Hokkaido", and the maintenance contractor is "X Hokkaido". Here, the closing date of "-1" indicates that it is the "end of the month".

In step S704, the device list 764 of each business location is obtained from the device information storage module 316. For example, the device information table 1400 may be used. FIG. 14 is an explanatory diagram showing an example of the data structure of the device information table 1400. The device information table 1400 is stored in the device information storage module 316.
The device information table 1400 has an establishment code column 1402, a model code column 1404, a machine number column 1406, a model name column 1408, a BW counter column 1410, and a CL counter column 1412. The establishment code column 1402 stores an establishment code. The model code column 1404 stores a model code. The machine number column 1406 stores a machine number. The model name column 1408 stores a model name. The BW counter column 1410 stores a black and white counter number indicating the number of pages printed in black and white. The CL counter column 1412 stores a color counter number indicating the number of pages printed in color.
For example, the first row of device information table 1400 indicates that the business establishment code "DDEEFF0001" has a model code of "NC100535," a machine number of "111111," a model name of "AP7771," a black and white counter count of "300," and a color counter count of "400."
Furthermore, the closing date may be stored in the device information table 1400. In other words, the device and the closing date may be stored in association with each other.
In step S706, it is confirmed that the closing date for all devices matches the closing date for the business location. The process in step S706 can be performed using the device information table 1400, which also stores the closing date.

In step S708, it is determined whether the closing dates for all devices and the business establishment match, and if a mismatch is found, the process proceeds to step S710, and if all match, the process proceeds to step S712.
In step S710, the closing date of the device is corrected to the business closing date. The closing date of the device is corrected, assuming that the device is misconfigured.

In step S712, the job list 766 of each device is obtained from the job information storage module 318. For example, the job information table 1500 may be used. FIG. 15 is an explanatory diagram showing an example of the data structure of the job information table 1500. The job information table 1500 is stored in the job information storage module 318.
The job information table 1500 has a model code column 1502, a machine number column 1504, a divided processing number column 1506, a resolution column 1508, a processing date and time column 1510, a counting completion flag column 1512, and a data creation date and time column 1514. The model code column 1502 stores the model code. The machine number column 1504 stores the machine number. The divided processing number column 1506 stores the divided processing number. The resolution column 1508 stores the resolution. The processing date and time column 1510 stores the processing date and time. The counting completion flag column 1512 stores a flag indicating whether or not counting has been completed. The data creation date and time column 1514 stores the data creation date and time.
For example, the first row of job information table 1500 indicates that the machine number of the model code "NC100535" is "111111", the number of divided processing sheets is "12", the resolution is "600", the processing date and time is "20200301T145959Z", the counted flag is "TRUE", and the data creation date and time is "20200302T151010Z".

In step S714, jobs are tallied for each device and stored in the device-specific tally result storage module 362A. For example, the jobs may be stored in the format of a model-specific tally result table 1600. FIG. 16 is an explanatory diagram showing an example of the data structure of the model-specific tally result table 1600. The model-specific tally result table 1600 is stored in the post-tally data storage module 362.
The model-specific tally result table 1600 has a model code column 1602, a machine number column 1604, tally year/month column 1606, a total number of processes column 1608, a list of devices to be tallyed column 1610, and a data creation date/time column 1612. The model code column 1602 stores the model code. The machine number column 1604 stores the machine number. The tally year/month column 1606 stores the tally year/month. The total number of processes column 1608 stores the total number of processes. The list of devices to be tallyed column 1610 stores a list of devices to be tallyed. The data creation date/time column 1612 stores the data creation date/time.
For example, the first row of the model-specific tally result table 1600 indicates that the machine number of the model code “NC100535” is “111111,” the tally month is “202002,” the total number of processes is “100,” the list of devices to be tallyed is “{NC100535, 111111},” and the data creation date and time is “20200302T151010Z.”

In step S716, the results of the device-specific tally are merged with the results of the business establishment-specific tally, and are stored in the business establishment-specific tally storage module 362B. The fact that a correction has been made may be recorded in order to display a disclaimer. For example, the results may be stored in the form of a business-specific tally result table 1700. FIG. 17 is an explanatory diagram showing an example of the data structure of the business-specific tally result table 1700. The business-specific tally result table 1700 is stored in the post-tally data storage module 362.
The business-specific tally result table 1700 has an establishment code column 1702, tally year and month column 1704, total number processed column 1706, free input field column 1708, and data creation date and time column 1710. The establishment code column 1702 stores the establishment code. The tally year and month column 1704 stores the tally year and month. The total number processed column 1706 stores the total number processed. The free input field column 1708 is a column where any input can be made. The data creation date and time column 1710 stores the data creation date and time.
For example, the second row of table 1700 of the summary results by business shows that the summary year and month for the business establishment code "DDEEFF0002" is "202003," the total number of transactions is "11,000," the free input field 1708 states "A correction has been made to the closing date for equipment A," and the data creation date and time is "20200302T151010Z."

In step S718, the establishment-specific tally results are merged with the contract-specific tally results and stored in the contract-specific tally results storage module 362C. For example, the tally results may be stored in the form of a contract-specific tally results table 1800. FIG. 18 is an explanatory diagram showing an example of the data structure of the contract-specific tally results table 1800. The contract-specific tally results table 1800 is stored in the post-tally data storage module 362.
The contract-specific tally result table 1800 has a contract ID column 1802, a tally date column 1804, a total number of transactions column 1806, and a data creation date and time column 1808. The contract ID column 1802 stores the contract ID. The tally date column 1804 stores the tally date and time. The total number of transactions column 1806 stores the total number of transactions. The data creation date and time column 1808 stores the data creation date and time.
For example, the first row of the contract-specific tally result table 1800 indicates that the tallying date for the contract ID "AABBCC0001" is "202002", the total number of processes is "100000", and the data creation date and time is "20200302T151010Z".

In the flowchart shown in the example of FIG. 7, step S706 "verifies that the closing dates of all devices and the business location match", but the contract closing date and the device closing date may be compared. In other words, step S706 may be "verifies that the closing dates of all devices and the contract closing date match". In that case, step S702 is changed to "obtain a list of contracts to be tallied for the current day from the contract information storage module 312" and step S704 is changed to "obtain a list of devices for each contract from the device information storage module 316".

Figure 8 is a flowchart showing an example of processing according to this embodiment. It is a specific example of the processing of step S606 in the flowchart shown in the example of Figure 6. The processing from step S800 to step S804 corresponds to the processing from step S700 to step S704 in the flowchart shown in the example of Figure 7. The processing of step S806 corresponds to the processing of step S712 in the flowchart shown in the example of Figure 7. And the processing from step S810 to step S814 corresponds to the processing from step S714 to step S718 in the flowchart shown in the example of Figure 7.

In step S800, the schedule execution time arrives.
In step S802, the list of establishments to be counted for the current day 762 is obtained from the establishment information storage module 314.

In step S804, the device list 764 of each business establishment is obtained from the device information storage module 316.
In step S806, the job list 766 of each device is obtained from the job information storage module 318.

In step S808, only job information 868 from the last tallying date and time onwards is extracted from the job information storage module 318. The tallying process history is compared with the job's processed flag, and only unprocessed jobs are extracted. For example, the tallying flag column 1512 of the job information table 1500 may be used. In the example of FIG. 15, rows in which the tallying flag column 1512 is set to "FALSE" are extracted as unprocessed jobs. Rows in which the tallying flag column 1512 is set to "TRUE" are not extracted as targets for tallying, as they are jobs that have already been tallying processed.

Then, in step S808, the extraction result is stored in the tallying process history storage module 320. For example, it may be stored in the format of a tallying history table 1900. Fig. 19 is an explanatory diagram showing an example of the data structure of the tallying history table 1900. The tallying history table 1900 is stored in the post-tallying data storage module 362.
The tally history table 1900 has a contract ID column 1902, a business establishment code column 1904, a list of tally target devices column 1906, and a final tally implementation date and time column 1908. The contract ID column 1902 stores a contract ID. The business establishment code column 1904 stores a business establishment code. The tally target device list column 1906 stores a list of tally target devices. The final tally implementation date and time column 1908 stores the date and time of the final tally implementation.
For example, the first row of the tally history table 1900 indicates that the business code for the contract ID "AABBCC0001" is "DDEEFF0001," the list of devices to be tallied is "{NC100535,111111}," and the date and time of the last tally was "20200302T151010Z."

In step S810, the job count for each device is performed and stored in the device count result storage module 362A.
In step S812, the device-specific tally results are merged with the establishment-specific tally results and stored in the establishment-specific tally results storage module 362B.
In step S814, the establishment-specific tally results are merged with the contract-specific tally results and stored in the contract-specific tally results storage module 362C.

In the flowchart shown in the example of FIG. 8, the devices in the business are counted, but the devices corresponding to the contracts may be counted. In that case, step S802 is changed to "obtain a list of contracts to be counted for the current day from the contract information storage module 312" and step S804 is changed to "obtain a list of devices for each contract from the device information storage module 316."

9 is a flowchart showing an example of processing according to this embodiment, which is a specific example of the processing in step S606 in the flowchart shown in the example of FIG.
The flowchart shown in the example of Fig. 9 is a combination of the flowcharts shown in the examples of Fig. 7 and Fig. 8. That is, the processes from step S900 to step S912 are equivalent to the processes from step S700 to step S712 in the flowchart shown in the example of Fig. 7, the process of step S914 is equivalent to the process of step S808 in the flowchart shown in the example of Fig. 8, and the processes from step S916 to step S920 are equivalent to the processes from step S714 to step S718 in the flowchart shown in the example of Fig. 7.

In step S900, the schedule execution time arrives.
In step S902, the list of establishments to be counted for the current day 762 is obtained from the establishment information storage module 314.

In step S 904 , the device list 764 of each business establishment is obtained from the device information storage module 316 .
In step S906, it is confirmed that the closing date for all devices matches the closing date for the business location.

In step S908, it is determined whether the closing dates for all devices and the business establishment match, and if a mismatch is found, the process proceeds to step S910, and if all match, the process proceeds to step S912.
In step S910, the closing date of the device is corrected to the business closing date.

In step S 912 , the job list 766 of each device is obtained from the job information storage module 318 .
In step S 914 , only the job information 868 after the last tallying date and time is extracted from the tallying process history storage module 320 .

In step S916, the job count for each device is performed and stored in the device count result storage module 362A.
In step S918, the results of the device-specific tabulation are merged with the results of the business establishment-specific tabulation, and are stored in the business establishment-specific tabulation result storage module 362B. For the purpose of displaying a disclaimer, it may be recorded that correction has been made.
In step S920, the establishment-specific tally results are merged with the contract-specific tally results and stored in the contract-specific tally results storage module 362C.

In the flowchart shown in the example of FIG. 9, step S906 "verifies that the closing dates of all devices and the business location match", but the contract closing date and the device closing date may be compared. In other words, step S906 may be "verifies that the closing dates of all devices and the contract closing date match". In that case, step S902 is changed to "obtain a list of contracts to be tallied for the current day from the contract information storage module 312", and step S904 is changed to "obtain a list of devices for each contract from the device information storage module 316".

10 is a flow chart showing an example of processing according to this embodiment, which shows an example of processing for displaying the counting results after the counting processing is completed.
In step S1000, a browser is started in accordance with a user's operation.
In step S1002, the display content is selected.

In step S1004, the display content is determined. If it is a user list display, the process proceeds to step S1006. If it is a device-by-device usage comparison display, the process proceeds to step S1010. If it is a usage ratio display, the process proceeds to step S1014.
In step S1006, a request to display a user list is transmitted.

In step S1008, a user list display rendering instruction setting file is obtained.
In step S1010, a request for comparing and displaying the amounts of usage by device is transmitted.

In step S1012, a device-specific usage amount comparison display rendering instruction setting file is acquired.
In step S1014, a request to display the utilization ratio is transmitted.

In step S1016, a utilization ratio display rendering instruction setting file is acquired.
In step S1018, rendering is performed based on the rendering settings. In step S1018, when a user list display rendering setting 1062 is received, a user list regarding the usage status is generated as shown in the example of Fig. 11(a), when a device-specific usage amount comparison display rendering setting 1064 is received, a graph regarding the device usage status is generated as shown in the example of Fig. 11(b), and when a usage ratio display rendering setting 1066 is received, a graph regarding the processing contents performed by the device is generated as shown in the example of Fig. 11(c).

In step S1020, design instruction information is obtained.
In step S1022, the image is embedded in the design to form a screen.

The program described above may be provided by storing it in a recording medium, or the program may be provided via a communication means. In that case, for example, the program described above may be regarded as an invention of "a computer-readable recording medium on which a program is recorded."
"Computer-readable recording medium on which a program is recorded" refers to a computer-readable recording medium on which a program is recorded, which is used for installing, executing, distributing, etc. a program.
Examples of recording media include digital versatile discs (DVDs) such as "DVD-R, DVD-RW, DVD-RAM, etc.", which are standards established by the DVD Forum, and "DVD+R, DVD+RW, etc.", which are standards established for DVD+RW; compact discs (CDs) such as read-only memories (CD-ROMs), CD recordables (CD-Rs), CD rewritables (CD-RWs), Blu-ray (registered trademark) Discs, magneto-optical discs (MOs), flexible discs (FDs), magnetic tapes, hard disks, read-only memories (ROMs), electrically erasable and rewritable read-only memories (EEPROMs), flash memories, random access memories (RAMs), and SD (short for Secure Digital) memory cards.
The whole or a part of the program may be recorded on the recording medium and stored or distributed, etc. Also, the program may be transmitted by communication using a transmission medium such as a wired network used in a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet, an intranet, an extranet, etc., a wireless communication network, or a combination of these, or may be transmitted on a carrier wave.
Furthermore, the program may be a part or the whole of another program, or may be recorded on a recording medium together with a separate program, or may be divided and recorded on a plurality of recording media, or may be recorded in any manner that allows restoration, such as compression or encryption.

100... Information processing device 105... Processor 110... Memory 120... Data memory 122... Equipment usage status storage module 124... Equipment tally storage module 140... Program memory 142... tally module 144... Display control module 185... Output device 187... Display device 189... Printing device 190... Reception device 192... Instruction reception device 194... Document reading device 195... Communication device 198... Bus 210... Image processing device 220... Mobile terminal 230... Wearable device 250... Administrator terminal 280... In-house communication line 290... Communication line 300... Information processing device 302... IoT data receiving module 304... Raw data storage module 306... Today's tally target contract acquisition module 308... Tally target equipment acquisition module 310... Tally processing module 312... Contract information storage module 314... Business establishment information storage module 316...Device information storage module 318...Job information storage module 320...Counting process history storage module 322...Counting process logic storage module 324...Counting process logic setting module 326...List of devices by contract to be counted on the current day 330...Data pre-processing module 340...Display request receiving module 342...Request source determination module 344...Rendering instruction sending module 346...Screen design setting module 348...Design instruction information storage module 350...Rendering result receiving module 352...Display content formation module 360...Visualization module 362...Post-counting data storage module 362A...Counting result storage module by device 362B...Counting result storage module by business establishment 362C...Counting result storage module by contract 364...Data acquisition module 366...Rendering instruction receiving module 368...Request information request source information 370...Rendering execution module 372...Rendering result sending module 374...Rendering setting registration module 376: Rendering instruction information storage module 380: Rendering engine module 382: IoT data transmission module 384: IoT device 386: Display module 388: Display request transmission module 390: Administrator terminal 392: Office environment

Claims (8)

A memory and one or more processors,
The memory stores, for each device, a date and time for performing calculation of the usage amount obtained from the device, and information indicating whether or not the calculation has been completed, in association with each other, and further stores tallying process instruction information which is a program indicating a procedure for the tallying process;
The processor,
If the above calculation is performed multiple times a month,
If the information indicates that the target device has already been counted, the usage amount of the device since the date and time when the counting was performed is counted according to the counting process instruction information ;
The memory further stores a device corresponding to a contract and a date and time for performing the tally under the contract,
The processor,
When a first date and time for performing the tally in the target contract is different from a second date and time for performing the tally of the device corresponding to the contract, the tally is performed by treating the date and time for performing the tally of the device as the first date and time.
Information processing device. The processor,
If a first date and time for performing the tally in the target contract is different from a second date and time for performing the tally in the device corresponding to the contract, the date and time for performing the tally in the device in the memory is changed to the first date and time;
Controlling the display device to display the change;
The information processing device according to claim 1 . The processor,
When a first date and time for performing tabulation at the target business establishment is different from a second date and time for performing tabulation of the device installed at the business establishment, the date and time for performing tabulation of the device is set as the first date and time for performing tabulation.
The information processing device according to claim 1 . The processor,
When a first date and time for performing tabulation at the business establishment to be targeted is different from a second date and time for performing tabulation of the device installed at the business establishment, the date and time for performing tabulation of the device in the memory is changed to the first date and time;
Controlling the display device to display the change;
The information processing device according to claim 3 . The processor,
The results of the survey for each device are collected for each business establishment in which the device is installed;
The results of the survey for each business establishment are tabulated for each contract.
and controlling the display device to display one or more of the tabulated results for each device, the tabulated results for each establishment, or the tabulated results for each contract.
The information processing device according to claim 1 . The processor,
If a first date and time for performing the tally in the target contract is different from a second date and time for performing the tally in the device corresponding to the contract, the date and time for performing the tally in the device is changed to the first date and time;
Controlling so that the fact that the change has been made is stated in the tabulation results for each contract;
The information processing device according to claim 5 . The processor,
If a first date and time for performing tabulation at the business establishment to be targeted is different from a second date and time for performing tabulation on a device installed at the business establishment, the date and time for performing tabulation on the device is changed to the first date and time;
Controlling the system so that the fact that the change has been made is recorded in the tabulation results for each business establishment,
The information processing device according to claim 5 . A computer having a memory and one or more processors, the memory comprising:
The date and time for calculating the usage amount of each device is stored in association with information indicating whether or not the calculation has been completed, and further, tally processing instruction information, which is a program indicating the procedure for the tally processing, is stored;
The processor,
If the above calculation is performed multiple times a month,
If the information indicates that the target device has already been counted, the usage amount of the device since the date and time when the counting was performed is counted according to the counting process instruction information ;
The memory further stores a device corresponding to a contract and a date and time for performing the tally under the contract,
The processor,
When a first date and time for performing the tally in the target contract is different from a second date and time for performing the tally of the device corresponding to the contract, the tally is performed by treating the date and time for performing the tally of the device as the first date and time.
An information processing program for executing processing.

Images