JP7230404B2 - Servers, systems, cost management methods - Google Patents

Description

The present invention relates to a server , system , and cost management method.

In a system that manages the usage status of equipment including image forming devices such as MFPs (Multifunction Peripherals) and the usage capacity that is the upper limit of usage, the usage capacity is allocated to a group to which multiple users belong, and the balance is calculated for each group. Techniques are already known that allow the management of

Further, a technique is disclosed in which, when a user belongs to a plurality of groups, the amount of usage of the MFP (for example, the number of prints made by a specific user) is assigned as the number of prints made by the group to which the user belongs (see, for example, Patent Document 1).

According to the conventional technology, even if a job (print processing, image data output processing, etc.) performed by a user is not related to the group to which the user belongs, the group to which the user belongs is not related to the job. The problem arises that it will be consumed from the balance of

If it is determined that the executed job is clearly related to the group to which the user belongs, the above problem does not occur. However, existing settings (rules) may not be able to properly determine related groups. In that case, it is up to the administrator to determine from which group the usable amount of the job is to be allocated. However, it is not easy for the administrator to decide which group's balance is to be consumed.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a technique that allows the balance to be consumed from the appropriate group when the device is used.

In order to solve the above problems, one aspect of the present invention is a server connected to an image forming apparatus and a terminal device via a network, wherein the cost generated by executing a job in the image forming apparatus is in a server that manages each group to which a user belongs, in creating a rule for distributing the cost, a first item for receiving input of the target user who is the target of the rule, and a destination for distributing the cost and a distribution condition for distributing the costs to the distribution destination group, the distribution condition including a set value set for the job as a condition. and a first setting screen displaying items 3 and 3 to the terminal device, and the information input to each of the second item and the third item is input to the first item. a registration unit that registers rule information of the target user; a reception unit that receives, via the network, job setting values and identification information that identifies a user from the image forming apparatus; and the received job. and a setting value included in the distribution condition included in the rule information of the user identified by the received identification information identifying the user, and and a cost management unit that specifies based on the received set value of the job, and the cost management unit distributes the calculated cost to the specified allocation destination group. and

According to the present invention, it is possible to provide a technology that allows the balance to be consumed from the appropriate group when the device is used.

1 is a diagram showing an example of the overall configuration of a usable amount management system according to a first embodiment; FIG. 2 is a diagram illustrating an example hardware configuration of the MFP of the first embodiment; FIG. It is a figure which shows the hardware structural example of the available-capacity management server of 1st Embodiment. 1 is a block diagram showing a configuration example of a usable amount management system according to a first embodiment; FIG. It is a figure which shows the data structural example which the usable amount management system of 1st Embodiment uses. It is a figure which shows an example of the setting screen produced by the available-capacity management server of 1st Embodiment. 7 is a diagram showing an example of rule information input via the setting screen of FIG. 6; FIG. 4 is a sequence diagram showing an operation example of the usable amount management system of the first embodiment; FIG. It is a figure which shows an example of the use cost for every group of 1st Embodiment, and a cost balance. FIG. 5 is a diagram illustrating an example of job history according to the first embodiment; FIG. It is a figure which shows an example of the setting screen of 2nd Embodiment. It is a figure which shows an example of the rule information of 2nd Embodiment. FIG. 11 is a sequence diagram showing an operation example of the usable amount management system of the second embodiment; It is a figure which shows an example of the setting screen of 3rd Embodiment. It is a figure which shows an example of the setting screen of 3rd Embodiment. FIG. 12 is a sequence diagram showing an operation example of the usable amount management system of the third embodiment; It is a block diagram which shows the structural example at the time of functionally dividing the cost management part of 3rd Embodiment further.

A usable amount management server, a usable amount managing system, and a usable amount managing method according to embodiments will be described below with reference to the drawings.

In the first embodiment, when a user uses an MFP (Multifunction Peripheral), a detailed rule is provided in advance as to which group the cost (usage amount) generated by the job should be allocated to. In the first embodiment, a mode of automatically distributing costs according to this rule when a job is executed will be described. In the second embodiment, a mode will be described in which a distribution ratio is set in advance for each group and the cost is apportioned according to this ratio.

In the first and second embodiments described above, even when a user executes a job that is not related to the group to which he belongs, it is assigned to the group to which he belongs. In order to solve this problem, in the third embodiment, a mode in which the administrator allocates groups after the fact will be described.

(First embodiment)
FIG. 1 is a diagram showing an example of the overall configuration of a usable amount management system according to the first embodiment. The usable amount management system 1 has an MFP (Multifunction Peripheral) 100 used by a user 10 , a usable amount management server 200 (hereinafter referred to as server 200 ), and a terminal device 300 used by an administrator 20 . A network is constructed so that server 200 can exchange data with MFP 100 and with terminal device 300 .

The MFP 100 is an image forming apparatus having functions such as copying, printing, scanning, and facsimile. The server 200 is a computer that manages the usage status of the MFP 100 for each user and each group to which the user belongs, and manages the upper limit of usage (usable amount). Terminal device 300 is a computer for operating server 200 remotely.

It should be noted that the MFP 100 may be composed of one unit or a plurality of units. Further, the server 200 may have a redundant configuration with a plurality of units, and the terminal device 300 may also have a configuration with one or a plurality of units.

FIG. 2 is a diagram showing an example of the internal configuration of the MFP 100. As shown in FIG. The MFP 100 has a main control unit 201 , a display operation unit 202 , an image processing ASIC (Application Specific Integrated Circuit) 203 , an image forming unit 204 , and a network I/F 205 (I/F: Interface). connected through

The main control unit 201 has a CPU (Central Processing Unit) 211, a RAM (Random Access Memory) 212, a ROM (Read Only Memory) 213, and a HDD (Hard Disk Drive) 214, and controls the internal hardware of the MFP 100. Control. CPU 211 is an arithmetic processing unit and controls the overall operation of MFP 100 . The RAM 212 is a volatile storage medium from which data can be read and written at high speed, and is used as a working area when the CPU 211 processes information. The ROM 213 is a read-only non-volatile storage medium and stores programs such as firmware. The HDD 214 is a non-volatile storage medium from which data can be read and written. The HDD 214 stores an OS (Operating System), various control programs that provide functions such as copying, scanning, printing, and FAX transmission/reception, and application programs such as a browser program.

The image processing ASIC 203 performs image processing on print data and image data before forming an image on a sheet. Note that the main control unit 101 may execute part or all of the processing executed by the image processing ASIC 203 .

A display operation unit 202 is a user interface that accepts input of parameters such as the number of copies and density values from the user, and displays the operating state and processing results. The display operation unit 202 includes an LCD (Liquid Crystal Display) 221 and an operation section 222 . LCD 221 is a display device for the user to check the state of MFP 100 . Operation unit 222 is an input device, such as physical keys and a touch panel, for inputting information to MFP 100 . Via the display/operation unit 202, the user can perform login authentication and make detailed job settings.

An image forming unit 204 forms print data transmitted from a terminal used by a user or an image read by a scanner on a sheet. The network I/F 205 controls communication with external devices, and includes an interface board for transmitting and receiving data to and from external devices such as the server 200 .

Further, MFP 100 may be provided with a card reader for reading an IC card held by a user. An IC card held by a user records identification information that uniquely identifies the user (hereinafter, "identification information" is referred to as an ID) and the like. When the user brings the IC card close to the card reader, the card reader reads information recorded on the card, and authentication processing is performed based on the information.

FIG. 3 is a diagram showing an internal configuration example of the server 200. As shown in FIG. The main control unit 301 has a CPU 311 , a RAM 312 , a ROM 313 and an HDD 314 . The display operation unit 302 is composed of a monitor 321 and input devices 322 such as a keyboard and a mouse. Network I/F 305 includes a network interface card and the like for communicating with the outside. These are connected by a bus 307 . Each of these units is also functionally identical to that of existing computers. The HDD 314 is preloaded with prescribed programs, a web server program, and the like, and the CPU 311 develops these programs in the RAM 312 and performs calculations to provide the functions described below.

It is assumed that the terminal device 300 has the same configuration as the internal configuration example of the server 200 .

FIG. 4 is a block diagram showing a configuration example of the usable amount management system 1 of the first embodiment, and mainly shows the configurations of the MFP 100 and the server 200. As shown in FIG.

The MFP 100 has an input unit 401 , a processing control unit 402 , a communication unit 403 , an authentication unit 411 and an image formation processing unit 412 . An input unit 401 is a functional unit including the display operation unit 202 and the network I/F 205, and receives job parameters and execution instructions, and receives authentication data. In the case of copy processing and scanner processing, the input unit 401 accepts parameters via the display operation unit 202 according to the operation of the user 10, but in the case of FAX reception processing and print processing, the parameters are set to default values or print data. The included value.

The communication unit 403 is a functional unit including the network I/F 205 in its configuration, and is responsible for data communication with the server 200 . A processing control unit 402 controls the operation of each functional unit in the MFP 100 and relays data transfer between the functional units. The processing control unit 402 is implemented by the main control unit 201 cooperating with software.

Authentication unit 411 transmits authentication data such as a user ID acquired from user 10 to server 200 via communication unit 403 , and determines whether use of MFP 100 is permitted according to the authentication result returned from server 200 . judge. The authentication unit 411 is implemented by the main control unit 201 cooperating with software.

The image forming processing unit 412 is a functional unit including the image forming unit 204 and the image processing ASIC 203 in its configuration. An image formation processing unit 412 provides the main functions of the MFP, such as forming an image of print data on a sheet.

The server 200 has a UI section 451 (UI: user interface), a processing control section 452 , a communication section 453 , an authentication processing section 461 , a registration section 462 , a cost management section 463 and a storage section 470 . The storage unit 470 also stores group information 471 , user information 472 , location information 473 , rate information 474 , rule information 475 , job history 476 and cost information 477 .

The UI unit 451 includes the network I/F 305 in its configuration, and is implemented by the main control unit 301 executing the web server program. The UI unit 451 provides the administrator 20 with a setting screen and the like, which will be described later, according to a request from the terminal device 300 .

Communication unit 453 is a functional unit including network I/F 305 in its configuration, and is responsible for data communication with MFP 100 . The processing control unit 452 relays operation control of each function unit in the server 200 and data transfer between each function unit. The processing control unit 452 is implemented by the main control unit 301 cooperating with software.

Authentication processing unit 461 acquires authentication data transmitted from MFP 100 via communication unit 453, and based on this authentication data and data registered in user information 472, the user uses MFP 100. A determination (authentication process) is performed as to whether the user is authorized or not. Authentication processing portion 461 transmits the authentication result to MFP 100 via communication portion 453 .

The registration unit 462 acquires data input by the administrator 20 to a setting screen (described later) via the UI unit 451 and registers it in the rule information 475 .

The cost management unit 463 is a functional unit that determines to which group the costs generated by job execution are to be allocated, and calculates the cost balance, which is the usable amount of each group.

FIG. 5 is a diagram showing a data configuration example used by the usable amount management system 1 of the first embodiment, showing group information 471, user information 472, location information 473, and rate information 474 here. Each of these pieces of information is master data registered in advance by the administrator 20, and management such as registration, update, search, and deletion of records is performed by the administrator 20 as necessary.

Group information 471 shown in FIG. 5A is data relating to each department (group) of an organization (such as a company) in which MFP 100 is installed. One record of the group information 471 is a data structure in which a group ID, which is identification information of the group, the name of the group, and the upper limit of the cost that can be used by the group ("upper limit of cost balance" in the figure) are associated. It has become.

The user information 472 shown in FIG. 5B is data relating to employees (users) of the organization. One record of the group information 471 has a data structure in which a user ID, which is user identification information, the name of the user, and identification information (group ID) of the group to which the user belongs are associated. In the example of FIG. 5B, for example, a user with UserA's ID belongs only to the administration department (Group01), but a user with UserC's ID belongs to the planning department (Group03) and the product development department (Group04). ) belongs to two groups.

Location information 473 shown in FIG. 5C is data relating to the location and department name of MFP 100 (hereinafter referred to as location as necessary). One record of the location information 473 has a data structure in which a location ID, which is identification information of a location, and the name of the location are associated. Location information 473 is utilized when MFPs 100 are installed at different locations. If multiple MFPs are installed in the same area, such as multiple MFPs installed in the 3rd floor of the head office, these MFPs are distinguished from each other and assigned different location IDs. Also, identification information or an IP address assigned to MFP 100 itself may be provided in location information 473 in place of the location ID or together with the location ID. Thus, the location information also functions as information for uniquely identifying the MFP.

Rate information 474 shown in FIG. 5D is data representing how much cost is incurred per sheet according to the job type and parameters. One record of the rate information 474 includes rate ID which is identification information for uniquely identifying the record, job type (copy, print, scan, FAX, etc.), paper size (A4, A3, etc.), color mode (gray scale, full-color, two-color printing, etc.), double-sided/single-sided distinction, and rate are associated with each other.

For example, a record with a rate ID of "Rate001" indicates a copy or print job that forms an image with A4 size, grayscale, and single-sided settings. It also shows that a cost of "0.04" per sheet is incurred when a job with such parameter settings is executed. Therefore, when printing 5 sheets with this parameter setting, a cost of 0.2 (=0.04×5) is incurred. Incidentally, when the cost is 0.2 in this way, it is multiplied by 100 to obtain 20 yen, and the cost is finally input into a predetermined conversion formula and converted into a monetary amount.

Next, we will explain to which group the incurred costs are allocated. For example, in the case of a user whose ID is "UserA", as shown in FIG. 5B, the only group to which the user belongs is the administration department (Group01). In this case, the cost of using the MFP 100 by the user may be directly calculated as the cost of the generalization department. On the other hand, a user with an ID of "UserC" (in the following description, this user will be referred to as User C) is divided into two groups, the planning department (Group03) and the product development department (Group04), as shown in FIG. 5B. belong to a group. When this user C uses the MFP 100, it becomes necessary to determine to which group the cost should be added. In this embodiment, the administrator 20 establishes sorting rules and registers them in the rule information 475 . Then, when each user executes a job, the server 200 allocates costs to groups according to the registered rules.

FIG. 6 is a diagram showing an example of a setting screen for registering rules according to this embodiment, and FIG. 7 is a diagram showing an example of rule information 475 set on the setting screen of FIG. The administrator 20 activates the web browser of the terminal device 300, accesses the server 200, and displays the setting screen of FIG. 6 according to a predetermined procedure. FIG. 6A shows the initial state immediately after the setting screen is displayed, and FIG. 6B shows the state after the administrator 20 inputs data to each setting item.

The value displayed in the column of record ID is obtained by automatically assigning an empty ID by searching the rule information 475 by the registration unit 462 of the server 200 . Here, it is assumed that the ID "0005" is available. The target user column is a display column for the administrator 20 to select a target user for which a rule is to be set from a pull-down menu.

In the distribution destination group column, the group to which the user belongs selected by the administrator 20 is displayed in a selectable format. The registration unit 462 of the server 200 acquires the selected user ID, searches the user information 472 with the user ID, acquires the belonging group, and presents it to the administrator 20 via the terminal device 300 . In this example, IDs are displayed in the target user column and the allocation destination group column, but they may be converted to user names or group names and displayed.

In the column of rules, a line is added each time the "+" button is pressed. Also, when the "-" mark button is pressed, the corresponding line is deleted. The administrator 20 determines rules by manually inputting items, condition columns, and value columns or making selections from pull-down menus. Application name, PDL format, number of sheets, job type, paper size, double-sided/single-sided distinction, color mode, location information, etc. can be selected in the item column. In addition, the date, day of the week, time zone and time, data size, destination e-mail address, source FAX number, etc. can be selected. In the condition column, conditions such as inclusion, equivalence, magnitude relation, etc. can be selected. In the value column, manual input by the administrator 20 or values prepared in advance in conjunction with the display contents of the item column are displayed in a selectable manner.

A specific input example is shown in FIG. The example of FIG. 6 illustrates the following conditions.
- The job type is printing (print job), and the name of the application that issued the print job includes the character string "XXX".
- The PDL is in PostScript format.
・The number of sheets used is less than 39, including A4 size sheets.
・All prints are single-sided.
In the example of FIG. 6B, when user C executes a job with parameter settings that match the above conditions, the cost is allocated to Group03.

Data input by the administrator 20 via the setting screen in FIG. 6 is registered in the rule information 475 shown in FIG. The rule information 475 has a data structure in which values of record ID, user ID, condition, and group ID are associated with each other. A record ID is identification information of a record, and is displayed in the record ID column of FIG. The values entered in the user ID column and the group ID column in FIG. 6 are set for the user ID and group ID, respectively.

The values input in the rule column of FIG. 6 are registered in the condition column of FIG. As shown in FIG. 7, the registration unit 462 converts the acquired data into a prescribed format and registers it. A setting value of "DEFAULT" shown in the condition column means that no condition is specified. For example, the record ID "0001" means that when a user assigned the ID of UserA executes a job, the incurred cost is unconditionally assigned to Group01.

In this embodiment, the records are evaluated in ascending order of record ID numbers. When user C executes a job, the record ID "0003" is first evaluated, and if there is no match, the record ID "0004" is evaluated. When the parameters of user C's execution job do not match any of the conditions "0003" to "0009", the unspecified record "0010" is finally evaluated, and the cost is assigned to Group03.

Next, an operation example of the usable amount management system 1 of this embodiment will be described based on the sequence diagram of FIG. First, the above rule registration processing will be described, followed by the authentication processing and job execution. Note that the terminal device 300 is omitted in FIG. Also, here, it is assumed that the user 10 performs a copy job for copying a document sheet.

A rule registration process will be described. When the administrator 20 performs a predetermined operation on the terminal device 300, the registration unit 462 of the server 200 transmits the setting screen shown in FIG. 6 to the terminal device 300 via the UI unit 451 (S801). The administrator 20 performs necessary settings on the setting screen to create a rule, and when the "registration/update" button is pressed, the entered rule is transmitted to the server 200 (S802).

The registration unit 462 of the server 200 acquires the rule input by the administrator 20 via the UI unit 451 and registers it as one record in the rule information 475 (S803). A plurality of records are registered by the administrator 20 inputting rules each time as necessary.

Next, authentication processing when user 10 uses MFP 100 will be described. When the user 10 inputs authentication data such as a user ID through the input unit 401 of the MFP 100 (S811), the authentication unit 411 accepts this and transmits the authentication data to the server 200 through the communication unit 403 (S812). ). After acquiring the authentication data, the authentication processing unit 461 of the server 200 performs authentication processing by determining whether the user ID is registered in the user information 472 (S813). Authentication processing unit 461 returns to MFP 100 an authentication result indicating the propriety of authentication (S814).

Authentication unit 411 of MFP 100 notifies user 10 of the authentication result by, for example, displaying it on display operation unit 202 . If the authentication result indicates that the job is inappropriate, the process ends here, and if the authentication result indicates that the job is acceptable, the MFP 100 switches the mode so that the job can be accepted.

Next, job execution processing (copy processing) will be described. The user 10 inputs various parameters (the number of copies, sheet size, color mode, single-sided/double-sided, etc.) via the input unit 401 . Then, the user 10 places the document sheet on the glass surface for scanning or on the tray of the automatic document feeder, and presses the execution button (S822).

Triggered by pressing of the execution button, the image forming processing unit 412 transmits parameters, the number of read original sheets, and the like to the server 200 via the communication unit 403 (S823).

The cost management unit 463 of the server 200 acquires the job parameters transmitted from the MFP 100, and specifies the group to which the costs are allocated based on the user ID and the job parameters acquired by the previous authentication process (S824). ). In step S<b>824 , the cost management unit 463 uses the acquired user ID and job parameters as search keys to identify records that match these from the rule information 475 . After specifying one record, the cost management unit 463 extracts the group ID in the record. Thereby, the cost management unit 463 can specify the group to which the cost of the current execution job is allocated.

The cost management unit 463 calculates the cost of the current execution job based on the acquired job parameters (S825). At this time, the cost management unit 463 refers to the rate information 474, acquires the value of the corresponding rate, adds the number of sheets used by the current job, and calculates the cost of the current job. do.

The cost management unit 463 determines whether or not the current job can be executed based on the cost incurred this time and the cost balance of the group to be distributed (S826).

FIG. 9 is a diagram exemplifying the cost information 477. As shown in FIG. The cost information 477 is a table for managing the amount of cost used during the target period (usage cost) and the remaining amount (cost balance) for each group. The cost management unit 463 determines whether or not the balance is insufficient by comparing the cost generated by the current execution job with the cost balance of the group to be distributed. If the cost incurred this time is greater than the balance, the cost management unit 463 returns a judgment result of impossibility of execution, and if the cost incurred this time is less than or equal to the balance, returns a judgment result of feasibility (S827).

The image formation processing unit 412 of the MFP 100 acquires the determination result, executes the job if the determination result indicates that the job is executable, and outputs a sheet after image formation as a product (S829). Then, the image forming processing unit 412 transmits job execution information including execution parameters and the like to the server 200 as a job execution result (S830).

The cost management unit 463 registers the received job execution information in the job history 476 (S831). FIG. 10 is a diagram exemplifying the data structure registered in the job history 476. As shown in FIG. Note that the date and time, user ID, execution parameters, and number of sheets shown in FIG. 10 are information included in the job execution information transmitted from MFP 100 . On the other hand, the job ID is an ID automatically numbered by the cost management unit 463 . Also, the distribution destination group and cost obtained in steps S824 and S825 are registered. By accumulating information about each job executed in this way, statistical data about the use of the MFP 100 can be obtained.

Finally, the cost management unit 463 updates the usage cost and cost balance of the cost information 477 using the cost generated by the execution job (S832). The cost management unit 463 extracts the usage cost and cost balance of the distribution destination group from the cost information 477, adds the currently incurred cost to the usage cost, and subtracts the currently incurred cost to the cost balance. The cost information 477 is updated.

(Second embodiment)
In the above-described first embodiment, the administrator 20 provides detailed rules for allocating costs to which group, and a mode in which costs are allocated according to the rules has been described. On the other hand, in the second embodiment, a mode of setting the allocation ratio for each group will be described. It should be noted that the configuration of the apparatus and the configuration of functional blocks will be described by using the configuration of the first embodiment as it is.

FIG. 11 is a diagram showing an example of a setting screen according to the second embodiment. FIG. 11A is an example of an initial setting screen displayed on the terminal device 300 immediately after the terminal device 300 transmits a request message via the web browser. FIG. 11B is a display example after the target user is specified, and is a diagram of a setting screen on which default values and existing ratios are displayed. FIG. 11(C) is an example of the setting screen after the administrator 20 has entered the distribution ratio for each group.

When the web browser of the terminal device 300 transmits a setting screen request message, the registration unit 462 of the second embodiment acquires this via the UI unit 451, creates the setting screen shown in FIG. This is returned to the terminal device 300 . The administrator 20 enters the ID of the target user in the target user column and presses the group display button. As a result, the web browser of the terminal device 300 transmits the input user ID to the server 200 .

The registration unit 462 of the server 200 acquires the transmitted user ID, searches the user information 472 using this user ID as a search key, and extracts the ID of the group to which the user belongs. Then, the registration unit 462 creates a setting screen including all the extracted group IDs and sends it back to the terminal device 300 via the UI unit 451 . As a result, the setting screen of FIG. 11B is displayed on the terminal device 300 . The registration unit 462 sets the ratio of groups with small IDs to 100 and the other groups to 0 as initial values to create a setting screen. The administrator 20 inputs a suitable ratio on this setting screen and presses the OK button. This state is shown in FIG.

By pressing the OK button, the registration unit 462 of the server 200 acquires data in which the group ID and the specified ratio are associated with each other, and registers the acquired data in the rule information 475 . FIG. 12 is a diagram illustrating rule information 475 of the second embodiment. In the rule information 475 of the second embodiment, record IDs, user IDs, ratios, and group IDs are associated and stored. Since the user assigned "UserA" belongs only to the generalization department (Group01), in the example of FIG. 12, the cost of executing the job is 100% borne by the group. On the other hand, the cost of the job executed by user C, who is given "UserC", is 60% for the planning department (Group03) and 40% for the product development department (Group04).

FIG. 13 is a sequence diagram showing an operation example of the usable amount management system 1 of the second embodiment. Here, rule registration processing (S801 to S803), authentication processing (S811 to S815), and preceding processing (S821 to S823) in job execution are the same as in the first embodiment. Note that the rule registration process is performed using the setting screen shown in FIG.

After obtaining the job parameters in step S823 (S823), the cost management unit 463 of the server 200 calculates the cost of the current job based on the job parameters (S825), as in the first embodiment. Then, according to the rule information 475 shown in FIG. 12, the cost management unit 463 proportionally distributes the calculated cost to each group to which the user belongs (S1301). For example, if the ID of the user who gave the job execution instruction is UserC, the cost management unit 463 identifies a record whose ID is UserC from the rule information 475 (see FIG. 12), and Get all sets of ratios and group IDs. For example, if the cost of the current job is 50, the cost management unit 463 allocates a cost of 30 (=50×0.6) to the group having the ID of Group03, and 20 (=50×0.6) to the group having the ID of Group04. = 50 x 0.4).

The cost management unit 463 extracts the cost balance of the group to be allocated from the cost information 477 and compares it with the proportionally distributed cost, thereby determining whether the job can be executed (S1302). If there is at least one group whose cost exceeds the balance (that is, the group whose balance is insufficient), the cost management unit 463 determines that execution is impossible. Judged as acceptable.

Subsequent steps S827 to S832 are the same as in the first embodiment.

In the first embodiment, by providing detailed rules, fine cost allocation can be performed, but it takes time and effort to create the rules and to input them. In the second embodiment, detailed cost allocation cannot be performed, but the labor for rule creation and input is alleviated.

(Third embodiment)
In the first and second embodiments, rules are registered in advance, and according to the rules, generated costs are allocated to groups each time a job is executed. When the user decides the rule and allocates the cost in this way, it functions properly when the user performs a job related to the group to which the user belongs. However, if the user does a job that is not related to the group to which he belongs, the administrator 20 needs to make adjustments.

In the third embodiment, a mode will be described in which the costs of jobs that have occurred so far are allocated to a regular group related to the job after the fact or upon receiving a request from the user, and totaled. It should be noted that the configuration of the apparatus and the configuration of functional blocks will be described by using the configuration of the first embodiment as it is.

FIG. 14 is a diagram showing an example of a setting screen according to the third embodiment. The cost management unit 463 of the third embodiment provides the administrator 20 with the screen shown in FIG. 14A via the UI unit 451 in order to distribute the costs. The administrator 20 inputs search conditions on this screen. The administrator 20 inputs the user ID of the target user as a search condition, specifies the execution date and time of the job, inputs information on where the job was performed, or inputs a combination of these, and presses the job acquisition button. Press. When the "other conditions" button is pressed, other information included in the job history, such as the color mode and the number of sheets, can also be added to the conditions.

When the job acquisition button is pressed, the cost management unit 463 acquires the corresponding execution job from the job history 476 (see FIG. 10) and creates the setting screen shown in FIG. 14B. When creating the setting screen of FIG. 14B, the cost management unit 463 creates the setting screen so that all groups registered in the group information 471 are displayed in a selectable format. In the example of FIG. 14B, group names are displayed as a pull-down menu.

In the example of FIG. 14B, the job ID, date and time of execution, number of sheets, location information, cost, and current assignment group in the job history are displayed. items (color mode, single-sided/double-sided, etc.) are also displayed.

The administrator 20 selects a group to which costs are to be allocated for the job from a list of pull-down menus. The state after this selection is shown in FIG. On the setting screen, as shown in FIG. 14C, the current cost balance (usage amount balance) of the selected destination group is also displayed. When the balance becomes insufficient, the cost balance may be displayed in a conspicuous manner, such as by displaying it in red. The determination of insufficient balance may be made by the cost management unit 463 of the server 200 acquiring data from the terminal device 300 on a case-by-case basis. can be done by executing

When the manager 20 presses the confirm button, the allocation destination group for the costs incurred in the job is changed. That is, the cost management unit 463 acquires at least the ID of the group selected by the administrator 20, and acquires the corresponding record of the job history 476 (see FIG. 10). Then, the cost management unit 463 updates the job history 476 by changing the value of the allocation destination group to the group ID selected by the administrator 20 . The cost management unit 463 also updates the cost information 477 (see FIG. 9). Here, the groups to be updated are the group before change and the group after change, and the cost management unit 463 reaggregates and updates the usage cost and cost balance of each group.

When changing the allocation destination group for other jobs as well, the administrator 20 presses the "next job" button or the "previous job" button. As a result, the setting screen switches to display the next job (or the previous job) that matches the conditions specified in FIG. 14A.

Further, when the ratio distribution button is pressed, the web browser of the terminal device 300 switches the display to the screen shown in FIG. 15 . With the setting screen shown in FIG. 15, the administrator 20 can set the allocation rate for the costs incurred in the job. It should be noted that when the "+" mark button is pressed, a row is added and can be sorted into three or more groups. When the "-" mark button is pressed, the line is deleted.

In the example of FIG. 15, the setting is such that the cost is allocated at a ratio of 60 to the generalization department (Group01) and 40 to the planning department (Group03). Further, as shown in FIG. 15, the current cost balance of each group is also displayed, but the predicted value after change may be displayed. This calculation of the predicted value may be performed by the cost management unit 463 of the server 200 each time, or may be performed by the web browser of the terminal device 300 executing a script incorporated in the page.

In this embodiment, it is possible to select not only the group to which the target user belongs, but also the group to which the target user does not belong, as shown in FIGS. For example, in FIG. 14C, the generalization department (Group01) to which User C does not belong is selected as the allocation destination. By doing so, it is possible to allocate costs even to unrelated groups.

FIG. 16 is a flow chart showing an operation example in the third embodiment. Note that the rule registration process, the authentication process, and the job execution process are the same as those in the flowchart of FIG. 8, so they are simplified.

When the manager 20 accesses the server 200 by operating the terminal device 300 when adjustment of distribution is required, the cost management unit 463 of the server 200 displays the screen shown in FIG. 14A. (S1601). Then, when search conditions such as a user ID are set by the administrator 20 (S1602), the cost management unit 463 searches the job history 476 under the selected conditions (S1610), and displays the setting screen shown in FIG. 14B. (S1611), and transmitted so that it can be displayed on the terminal device 300 (S1612).

When the administrator 20 inputs the group ID or the ratio of the distribution destination (S1613), the cost management unit 463 updates the job history 476, and calculates the usage cost and cost of the group registered in the cost information 477. The balance is updated (S1614). Specifically, the writing process is performed by pressing the confirmation button as described above.

As described above, when the "next job" button or the "previous job" button is pressed, steps S1610 to S1614 are repeatedly executed. Also, when another condition is input (S1602), steps S1610 to S1614 are performed for that condition.

By applying the aspect of the third embodiment, instead of allocating costs to groups based on rules set in advance each time a job is executed, jobs executed during a specified period such as weekly or monthly It may be implemented to allocate the cost to the group ex post facto for all. In this case, either the costs are allocated to the groups ex post facto using the setting screens shown in FIGS. 14 and 15, or the proportions for each group are determined ex post facto using the setting screens shown in FIG. 11 to adjust the burden costs. may

In the third embodiment, the cost management unit 463 may be functionally divided into a calculation unit 1701, a creation unit 1702, and a usage amount management unit 1703, as shown in FIG. 17, for example. In the example of FIG. 17, the communication unit 453 (receiving unit) receives from the image forming apparatus a job including at least information about the user and setting values (job parameters) of the job executed by the user to the image forming apparatus. information (see S812, S823, and S830 in FIG. 8). A job setting value (job parameter) is a setting value specified by a user when using an image forming apparatus. ), color mode (gray scale, full color, 2-color printing, etc.), double-sided/single-sided distinction, etc., which are shown as an example in the rate information 474 of FIG. 5(D). The communication unit 453 (receiving unit) receives job information including these various types of information. Also, the job information may include location information indicating the location of the image forming apparatus. The calculation unit 1701 calculates the usage amount generated by the job based on the setting values included in the job information (see S825 in FIG. 8). The creation unit 1702 creates a setting screen that includes information about the user and job information, and that includes information for individually specifying each group in a selectable format (FIGS. 14 and 17). 15, see S1610 to S1612 in FIG. 16). Then, the usage amount management unit 1703 allocates the usage amount calculated by the calculation unit 1701 to the group selected via the setting screen (see S1613 and S1614 in FIG. 16).

Each functional unit shown in FIG. 4, FIG. 17, etc. is merely an example, and the name of each functional unit and the function provided by each functional unit are not limited to these. Any one function unit shown in FIGS. 4 and 17 may be functionally divided into a plurality of function units, or a plurality of function units may be integrated into one function unit.

As described above, according to the embodiment, it is possible to present the administrator with a setting screen containing information about the user and job execution information, and based on this information, the administrator can reallocate costs to suitable groups. Therefore, it is possible to provide a technology that allows the balance to be consumed from the appropriate group when the device is used.

1: Usable amount management system 10: User 20: Administrator 100: MFP
200: Server (Available amount management server)
401: Input unit 402: Processing control unit 403: Communication unit 411: Authentication unit 412: Image formation processing unit 451: UI unit 452: Processing control unit 453: Communication unit 461: Authentication processing unit 462: Registration unit 463: Cost management unit 470: Storage unit 471: Group information 472: User information 473: Location information 474: Rate information 475: Rule information 476: Job history 477: Cost information 1701: Calculation unit 1702: Creation unit 1703: Usage management unit

JP 2012-131125 A

Claims (10)

A server that is connected to an image forming apparatus and a terminal device via a network and that manages costs generated by executing a job in the image forming apparatus for each group to which a user belongs . in
When creating a rule for distributing the cost, a first item for receiving an input of a target user who is a target of the rule, a second item for receiving an input of a destination group as a destination for distributing the cost, and the distribution a first setting screen for displaying a distribution condition for distributing the cost to the destination group, the third item receiving an input of the distribution condition including a set value set for the job as a condition; and registering the information entered in each of the second item and the third item as rule information of the target user entered in the first item;
a receiving unit that receives job setting values and identification information for identifying a user from the image forming apparatus via the network;
An allocation destination group to which costs calculated based on the received set values of the job are to be allocated is included in the allocation condition included in the rule information of the user identified by the received identification information identifying the user. a cost management unit that specifies based on the set values received and the received set values of the job ;
has
the cost management unit distributes the calculated cost to the specified distribution destination group;
A server characterized by : The server according to claim 1,
When the cost management unit receives job execution information as an execution result of the job, which is transmitted from the image forming apparatus based on execution of the job by the image forming apparatus, the cost management unit displays the execution result of the job. Registering in Job History
A server characterized by: The server according to claim 2,
Upon receiving the job execution information, the cost management unit distributes the calculated cost to the specified distribution destination group.
A server characterized by: In the server according to claim 2 or 3 ,
The server transmits to the terminal device a second setting screen capable of accepting selection of a change destination group for changing a cost allocation destination group of the job related to the job execution information registered in the job history. death,
When the selection of the change destination group is received via the second setting screen, the cost management unit distributes the allocated costs to the selected change destination group.
A server characterized by: The server according to claim 4,
The server, wherein the second setting screen includes display of the cost balance of the destination group . In the server according to claim 4 or 5,
The second setting screen is capable of selecting a plurality of groups as the change destination group, and is capable of accepting input of a distribution ratio to each of the plurality of groups,
When the plurality of groups are selected as the change destination group via the second setting screen and the input of the distribution ratio is received, the cost management unit converts the allocated costs to the distribution ratio. Allocate to each of the plurality of groups based on the ratio
A server characterized by : The server according to claim 1,
Upon receiving job execution information as an execution result of the job transmitted from the image forming apparatus based on execution of the job by the image forming apparatus, the cost management unit calculates the calculated cost. , distribute to the specified distribution destination group
A server characterized by: In the server according to any one of claims 1 to 7,
The setting values set as the distribution destination conditions of the third item are the number of sheets, job type, paper size, distinction between double-sided and single-sided, color mode, date, day of the week, time zone, time, data size, and destination. including at least one of an e-mail address, a sender's FAX number, and location information indicating the location of the image forming apparatus;
A server characterized by: A system including a server connected to an image forming apparatus and a terminal device via a network, and the image forming apparatus, wherein a user belongs to the system and the cost generated by the job executed by the image forming apparatus is paid by the user. In a system managed by the server for each group,
The server is
When creating a rule for distributing the cost, a first item for receiving an input of a target user who is a target of the rule, a second item for receiving an input of a destination group as a destination for distributing the cost, and the distribution transmitting to the terminal device a setting screen displaying conditions for allocating the costs to the destination group, and a third item for accepting input of allocating conditions as conditions including setting values set for the job; a registration unit that registers the information entered in each of the second item and the third item as rule information of the target user entered in the first item;
a receiving unit configured to receive, from the image forming apparatus via the network, setting values for a job to be executed by the image forming apparatus and identification information for identifying a user ;
An allocation destination group to which costs calculated based on the received set values of the job are to be allocated is included in the allocation condition included in the rule information of the user identified by the received identification information identifying the user. a cost management unit that specifies based on the set values received and the received set values of the job;
has
The image forming apparatus is
a transmission unit configured to transmit the job setting values and identification information for identifying the user to the server via the network;
the cost management unit distributes the calculated cost to the specified distribution destination group;
A system characterized by: A cost management method for managing, in a server connected to an image forming apparatus and a terminal device via a network, a cost generated by executing a job in the image forming apparatus for each group to which a user belongs. ,
the server
When creating a rule for distributing the cost, a first item for receiving an input of a target user who is a target of the rule, a second item for receiving an input of a destination group as a destination for distributing the cost, and the distribution a first setting screen for displaying a distribution condition for distributing the cost to the destination group, the third item receiving an input of the distribution condition including a set value set for the job as a condition; and registering the information entered in each of the second item and the third item as the rule information of the target user entered in the first item,
receiving setting values for a job to be executed by the image forming apparatus and identification information for identifying a user from the image forming apparatus via the network;
An allocation destination group to which costs calculated based on the received set values of the job are to be allocated is included in the allocation condition included in the rule information of the user identified by the received identification information identifying the user. identifying based on the set values received and the received set values of the job;
Distributing the calculated cost to the identified distribution destination group;
The cost control method of performing the action.

Images