JP2001297045A - Equipment management system, management client, management server, and method and program for use state management - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an equipment management system which can adequately manage OA equipment. SOLUTION: A processing control unit of a hybrid machine managing device sends an obtained company employee's number to a management server to request it to authenticate the user (step S12). The management server having received the employee's number performs retrieval from a user management DB (step S21) and sends information showing an authentication OK back to the hybrid machine managing device (step S24) when obtaining user information. The processing control unit once obtaining the information showing the authentication OK allows a hybrid machine to perform user's copying operation (step S14). After the user's copying operation, the processing control unit obtains information showing a copy quantity (step S16) and generates and sends equipment use information to the management server (step S17). The management server stores the obtained equipment use information in an equipment use quantity management DB (step S25).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a device management system, a management client, a management server, a usage management method, and a program capable of appropriately managing various devices such as a copying machine and a printer.

[0002]

2. Description of the Related Art Office automation equipment such as copiers and printers has been introduced in workplaces to improve efficiency of office work. Copiers are arranged, for example, for each department in a workplace, and are used for copying documents required by users (such as staff). Further, the printers are arranged, for example, in units of work groups in a department, and print documents output by a user from a work terminal (such as a personal computer).

In recent years, an OA device called a “multifunction machine” that has not only the function of a copying machine but also a scanner function and a printer function has been known. This multifunction peripheral can print a predetermined document or the like as a printer as well as copy a document, and can read a document as a scanner and take in image data. Recently, these various OA devices have been connected to each other by a LAN (Local Area Network) or the like, so that each OA device can be operated from a user's work terminal or the like.

[0004] Even if the OA device connected via a LAN or the like can be operated from a work terminal or the like, the user goes to the installation location of the target OA device and performs some operation. For example, when a user prints a predetermined document from a work terminal, the user needs to go to a printer or the like, and when copying a document, it is necessary to go to a copying machine or the like to perform an operation. Therefore, OA placed in the workplace
Whether or not the arrangement location and the number of devices are appropriate determines whether the work efficiency is good or bad. That is, if the arrangement of the OA equipment is not appropriate, the work efficiency is reduced and the operation management cost of the system is increased.

[0005] In order to determine whether or not the arrangement of the OA devices is appropriate, it is necessary to manage the use status of each OA device. Conventionally, the usage status of each OA device is roughly managed based on a counter value provided in the OA device such as a copying machine, the consumption of paper used in a printer or the like. For example, the administrator manages the usage status of the OA equipment for each department by counting the counter values of the copiers arranged for each department.

However, in this case, since the case where the user of another department uses the OA equipment is not considered, the counter value may not be the usage status of the department as it is. That is, conventionally, the use status of the OA equipment has not been properly managed. Therefore, it is not possible to determine whether or not the arrangement and the number of OA devices are not appropriate, and there is a problem that it is not possible to improve work efficiency and reduce system operation management costs.

[0007] In addition, due to demands for appropriate management of consumables used in each OA device and promotion of paperless workplaces due to environmental measures, appropriate management of the use status of OA devices is required. Had been. Further, in order to use an OA device such as a printer connected to a LAN or the like, it is necessary to install necessary driver software on a work terminal. This installation work is required even when another OA device is newly used, and labor saving of the installation work and appropriate management of the driver software have been required.

[0008]

SUMMARY OF THE INVENTION The present invention has been made in view of the above situation, and has an apparatus management system, a management client, a management server, and a management system capable of appropriately managing various devices such as a copying machine and a printer. It is intended to provide a usage management method and a program.

[0009]

To achieve the above object, a device management system according to a first aspect of the present invention is a device management system for managing devices to be managed connected to a network, An authentication unit that authenticates a user who operates the device; a usage information obtaining unit that obtains device usage information including a usage amount of the device by an operation of the user authenticated by the authentication unit; and an obtaining unit that obtains the usage information. Use information storage means for storing the obtained device use information.

According to the invention, the authentication means includes, for example,
The user operating the device is authenticated according to the acquired employee number and the like. The usage information acquisition unit acquires device usage information including the usage amount (for example, the number of used devices) of the device by the operation of the user authenticated by the authentication unit. The use information storage unit sequentially stores the device use information acquired by the use information acquisition unit. As described above, the usage information storage unit stores the usage information of the device. Then, from the stored usage information, the usage amount of the device for each user or for each department can be summed up as needed. As a result, it is possible to appropriately manage the usage status of the device.

The authentication means includes, for example, user information storage means for storing in advance user information for specifying a user who is permitted to operate the device, and identification information for identifying a user who operates the device. Identification information input means for inputting, and means for authenticating a user who operates the device in accordance with the identification information input by the identification information input means and the user information stored in the user information storage means. The use information acquisition unit is, for example, a count unit that counts the amount of use of the device by the operation of the user authenticated by the authentication unit, the usage amount counted by the count unit, and the authentication unit that has been authenticated. Usage information generating means for generating device usage information including information for identifying a user.

[0012] The device management system includes a usage amount obtaining unit that obtains a past usage amount of the device from the device usage information stored in the usage information storage unit, a usage amount obtained by the usage amount obtaining unit, Comparison means for comparing a predetermined reference value, according to the comparison result by the comparison means,
Output means for outputting a predetermined message to a user of the device and / or a manager of the device. By adopting such a configuration, for example, the usage amount of each device in the past month or one year and the reference value are compared with each other, and the devices that have been used or hardly used more than the extent determined by the specification of the device are used. The device can be determined.

[0013] The device management system includes: a usage amount obtaining unit that obtains a past usage amount of an arbitrary device by an arbitrary user from the device usage information stored in the usage information storage unit; The apparatus may further include a comparing unit that compares the obtained usage amount with a predetermined reference value, and an output unit that outputs a predetermined message to the user according to a comparison result by the comparing unit. By adopting such a configuration, for example, it is possible to call attention to a person who makes a large number of copies or prints a large amount.

[0014] The device management system includes a usage amount obtaining unit for obtaining a past usage amount of a device for each department to which a user belongs from the device usage information stored in the usage information storage unit; Comparing means for comparing the used amount obtained with the predetermined reference value, and output means for outputting a predetermined message to a user and / or a device administrator according to a comparison result by the comparing means; May be further provided. With such a configuration, for example, it is possible to call attention to a department that copies a large amount or prints a large amount.

[0015] The device management system includes: usage amount obtaining means for obtaining, from the device usage information stored in the usage information storage device, the usage amount of the device after the consumables of the device have been exchanged; Comparing means for comparing the usage amount obtained by the obtaining means with a predetermined reference value; and a predetermined message directed to a user operating the device and / or a manager of the device according to a comparison result by the comparing means. And an output unit that outputs the data. With such a configuration, for example, it is possible to output a message and prompt the user to prepare for the replacement of consumables (for example, toner, ink, and photoconductor) before the replacement is necessary.

To achieve the above object, a device management system according to a second aspect of the present invention is a device management system that manages software of a terminal device that controls a control target device connected on a network, Driver software storage means for storing in advance the driver software of the terminal equipment required for controlling the control target equipment, and correspondence information defining the correspondence between the driver software and the control target equipment stored in the driver software storage means Corresponding information storage means for storing, a selecting means for selecting a control target device to be controlled from a terminal device, and a driver for the control target device selected by the selecting means according to the correspondence information stored in the corresponding information storing means A specifying means for specifying the software, and a driver software specified by the specifying means connected to a network with the terminal device. And by supplying, and a installation means for installing the terminal equipment. With such a configuration, the user can easily install the driver software required by the user in the terminal device, and can easily use any device.

The device management system includes means for inputting information of a person who has installed the driver software on the terminal device, an installer storage means for storing information for identifying an installer based on the input information, Output means for, when the driver software stored in the software storage means is updated, discriminating the installer of the driver software from the contents stored in the installer storage means and outputting a predetermined message to the discriminated user; And may be further provided. With such a configuration, for example, the user can update the driver software by judging from the message that the driver software has been updated.

The installer storage means stores information indicating whether or not a notification is desired, for example, in association with the user who has installed the driver software, and the output means is stored in the driver software storage means. When the driver software is updated, a predetermined message is output to an installer of the driver software who wants to be notified. With this configuration, when the driver software is updated, a message is output only to the person who installed the driver software, and the driver software can be reinstalled.

To achieve the above object, a device management system according to a third aspect of the present invention comprises a device to be managed mutually connected via a network and a management device for managing the device to be managed. Wherein the management device stores in advance user information for identifying a user who is permitted to operate the device, and each device stores identification information for identifying the user of the device. Transmitting to the management device, the management device receives the transmitted identification information, according to the received identification information and the stored user information, authenticates the user, notifies the authentication result to the device, The device allows the operation of the user authenticated by the management device, obtains the usage amount of the user, notifies the management device, and the management device uses the notified usage amount and the user. Record by associating with equipment To, characterized in that.

The management device outputs a predetermined message to a user and / or a manager of each device, for example, based on the stored usage information.

In order to achieve the above object, a management client according to a fourth aspect of the present invention provides a management server for performing communication via a network to a management server that manages devices to be managed connected to the network. A client, an information input unit for inputting identification information for identifying a user who operates the device, and transmitting the identification information input by the information input unit to a management server; Authentication means for authenticating a user who operates the device, counting means for counting the usage of office equipment by the user authenticated by the authentication means, and management of equipment usage information including the usage amount counted by the counting means. And use information transmitting means for transmitting the information to the server.

To achieve the above object, a management server according to a fifth aspect of the present invention is a management server that manages devices to be managed connected on a network via a management client, A storage device for storing in advance user information for identifying a user permitted to operate the device,
Identification information acquisition means for acquiring identification information for identifying a user who operates a device from a management client via a network, identification information acquired by the identification information acquisition means, and stored in the user information storage means Authentication means for authenticating a user who operates the device, and device usage information including the usage amount of the device by the operation of the user who has been authenticated by the authentication means, from the management client via the network. It is characterized by comprising a use information acquisition unit for acquiring, and a use information storage unit for sequentially storing the device use information acquired by the use information acquisition unit.

To achieve the above object, a usage management method according to a sixth aspect of the present invention is a usage management method for managing the usage of a device to be managed connected to a network. Authenticate the user to be used, obtain the usage of the device by the operation of the authenticated user, obtain the device usage information including the obtained usage, and store the obtained device usage information in a predetermined database. It is characterized by the following. The device usage information stored in the database may be processed, and a predetermined message may be transmitted to a user and / or a manager of the device.

To achieve the above object, a method for managing software of a terminal device according to a seventh aspect of the present invention is a method for managing software of a terminal device for controlling a device to be controlled connected to a network. The driver software of the terminal device required to control the control target device and the correspondence information that defines the correspondence between the driver software and the control target device are stored in the storage device in advance, and the control device is controlled from the terminal device. Select the target device, specify the driver software of the selected control target device according to the correspondence information stored in the storage device, supply the specified driver software to the terminal device via a network, and Installation.

The information of the user who has installed the driver software is stored in a storage device, and when the driver software stored in the storage device is updated, the installer of the driver software is notified of the storage contents of the storage device. And a predetermined message may be notified to the determined user.

Further, a program according to an eighth aspect of the present invention is a program for causing a computer to execute a usage status management method for managing the usage status of a device to be managed connected on a network, An authentication step of authenticating a user who operates the device, a counting step of counting the usage of the device by the operation of the user authenticated in the authentication step, and a usage amount counted in the counting step. A computer is caused to execute a usage management method having a usage information obtaining step of obtaining device usage information and a storing step of sequentially storing the device usage information obtained in the usage information obtaining step in a predetermined database.

A program according to a ninth aspect of the present invention is a program for causing a computer to execute management of software of a terminal device that controls a device to be controlled connected to a network, and is stored in advance. Based on the correspondence information that defines the correspondence between the driver software and the control target device, information that specifies the control target device to be controlled is received from the terminal device, and the terminal necessary for operating the specified control target device is received. The device driver software and the determined driver software are provided to the terminal device and can be installed.

[0028]

DESCRIPTION OF THE PREFERRED EMBODIMENTS OA according to an embodiment of the present invention
(Office Automation) A device management system for managing devices will be described below with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a device management system applied to an embodiment of the present invention. As shown in FIG. 1, the device management system 1
MFP management device 12, scanner 13, scanner management device 14, database 15, management server 16
Business card print management device 17, business card print printer 18
, A FAX server 19, a facsimile machine 20, a printer 21, and a general-purpose terminal 22.

Multifunction machine management device 12, scanner management device 1
4. The management server 16, the business card print management device 17, the FAX server 19, the printer 21, and the general-purpose terminal 22 are connected via a network 2 including, for example, a LAN (Local Area Network). Note that the MFP 1
1, the scanner 13, the business card printing printer 18, the facsimile 20, and the printer 21 are OA devices for which usage status is managed.

Each of the multifunction peripherals 11 is a device having functions such as a copier, a scanner, and a printer. The multifunction peripheral 11 performs copying of a document by an operation of a user, scanning (reading) of the document, printing of a document output from the general-purpose terminal 22, and the like. Note that the multifunction peripheral 11
For example, each is set for each department in the workplace.

The multifunction device management apparatus 12 is a client device for the management server 16, requests the management server 16 to authenticate a user who uses the multifunction device 11, and uses the amount of use of the multifunction device 11 by the authenticated user. For example, the number of copies, the number of prints, the number of scans, etc.) are counted.
Then, device usage information including the counted usage amount is generated and supplied to the management server 16 via the network 2.

More specifically, each multifunction device management device 1
2 is a processing control unit 31 as shown in FIG.
, A touch panel 32, a CD-R drive 33, and a business card scanner 34.

The processing control unit 31 controls the entire multifunction device management device 12. That is, the processing control unit 31
Authenticates the user using identification information (for example, employee number) input from the touch panel 32. And
The processing control unit 31 is provided for the MFP 11 used by the user.
(For example, the number of copies, the number of prints, the number of scans, etc.), generates device use information including the counted amount of use and information for specifying the user, and sends the device use information to the management server 16 via the network 2. Supply.

Further, the processing control unit 31
When the scanner 1 scans a document using the scanner function, the scan data (image data) sent from the multifunction peripheral 11 is acquired, and the acquired image data is recorded on a disk medium by the CD-R drive 33.

When the processing control unit 31 acquires the image data of the business card read by the business card scanner 34,
By comparing the character data included in the image data with reference character data stored in advance, the character printed on the business card is recognized and converted to corresponding character data.

The touch panel 32 includes, for example, input / output devices in which a plurality of touch sensors are arranged on a liquid crystal display unit. The touch panel 32 acquires instruction information and the like input by the user according to the information displayed on the liquid crystal display unit, and supplies the acquired instruction information and the like to the processing control unit 31.

A CD-R (Compact Disc Recordable) drive 33 stores a disk medium (CD-R) coated with an organic dye or the like on a data recording surface, and irradiates the disk medium with a laser beam or the like to store data. Record
For example, the CD-R drive 33 records, on a disk medium, image data of a document read by the multifunction peripheral 11 by a scanner function.

The business card scanner 34 is a scanner dedicated to business cards, scans and reads a set business card with a light receiving element or the like, and supplies the read image data to the processing control unit 31.

Returning to FIG. 1, the scanner 13 is, for example,
It includes a semiconductor photoelectric conversion element such as a CCD (Charge Coupled Device), scans a document placed on a document table, and inputs the image data. The scanner 13 supplies the input image data to the scanner management device 14. The scanners 13 are installed, for example, for each department in the workplace.

The scanner management device 14 includes a management server 16
, And manages the scanner 13. The scanner management device 14 includes a touch panel 32 and a CD-R drive 33, as shown in FIG.
And a processing control unit 35.

The processing control unit 35 controls the entire scanner management device 14. That is, the processing control unit 3
Reference numeral 5 authenticates the user based on the employee number or the like input from the touch panel 32 and counts the amount of use of the scanner 13 (for example, the number of scans) used by the authenticated user. The processing control unit 35 generates device usage information including the counted usage amount and the like, and transmits the generated device usage information to the management server 16 via the network 2. The touch panel 32 and the CD-R drive 33 shown in FIG. 2B have the same configuration as the touch panel 32 and the CD-R drive 33 shown in FIG.

Returning to FIG. 1, the database 15 stores various data for managing OA equipment such as the multifunction peripheral 11 to be managed. More specifically, as shown in FIG. 3, the database 15 stores the user management DB 41
, A device management DB 42, a driver management DB 43, a device usage management DB 44, and a customer destination management DB 45.

The user management DB 41 stores the O
This is a database that stores information used when authenticating a user who uses the device A. For example, user management D
B41 stores user information including an employee number, a name, a department code, a department name, a telephone number, a FAX number, and the like as shown in FIG. 4A. The user management DB 41
The information and array stored in are arbitrary, for example,
CSV (Comma Separated Valu) from existing database
Information about the user may be acquired in the e format) format to generate the user information described above.

The device management DB 42 stores the OA of the multifunction peripheral 11 or the like.
This is a database that stores information for managing devices. For example, the device management DB 42 stores device information including a device number, a model name, a device classification, a network address, an installation location, and the like as shown in FIG.

The driver management DB 43 is a database that stores information for managing driver software such as the printer 21 that can be installed in the general-purpose terminal 22.
For example, the driver management DB 43 stores driver information including a model name, a version, a storage folder for driver software, and the like as shown in FIG.

The device usage management DB 44 is a database that stores information indicating the usage of OA devices by users. For example, the device usage management DB 44 stores the information shown in FIG.
And the device usage information including the number of double-sided copies or the number of sheets used in units of paper size, and the like, and the employee number specifying the user who uses the OA device as shown in FIG. The device usage management DB 44 also stores date and time information (date and time, etc.) such as the usage start time. The device usage information DB 44 stores such device usage information as O.
Stored for each A device.

The customer destination management DB 45 is a database for storing information on customers and the like who are business partners of users. For example, the customer destination management DB 45 stores a customer number, a name, a company code, a company name, a facsimile as shown in FIG.
Stores supplier information including a number and a mail address. The information stored in the customer destination management DB 45 and the arrangement thereof are arbitrary. For example, information on the business partner may be acquired from an existing database in a CSV format, and the above-described business partner information may be generated. . In addition, the processing control unit 31 recognizes characters of the image of the business card read by the business card scanner 34 (the multifunction peripheral management device 12),
The character data of the recognition result may be sequentially stored in the customer destination management DB 45.

Returning to FIG. 1, the management server 16 is a server device for managing the entire device management system 1, and is constituted by a predetermined computer system. Management server 16
Transmits and receives predetermined data to and from the MFP management device 12, the scanner management device 14, the business card print management device 17, and the like, authenticates a user who uses the OA device such as the MFP 11, and Acquire the usage amount of the OA device used by the authenticated user.

The management server 16 includes a mail receiving box (received mail storage area) and a mail transmission box (transmitted mail storage area) as shown in FIGS. 5 (c) and 5 (d). Function. That is, the management server 16 stores the e-mail received via the Internet or the like in a mail inbox,
The e-mail stored in the mail transmission box is transmitted to a destination via the Internet or the like.

The business card print management device 17 includes a management server 16
And manages the business card printing printer 18. The business card print management device 17 includes, for example,
The management server 16 acquires user information to be created as a business card stored in the user management DB 41 via the management server 16 and creates print information in a predetermined format. Then, the generated print information is supplied to the business card printing printer 18 to print the business card.

The business card printing printer 18 is a printer having a cutting mechanism for cutting printed paper into a predetermined business card size, and prints business card data on predetermined paper in accordance with print information supplied from the business card printing management device 17. Print.

When the FAX (facsimile) server 19 acquires the image data sent from the scanner management device 14 or the like by the scanning operation, it converts it into a data format for facsimile communication. Then, the converted data is transmitted to a predetermined destination via the facsimile 20. Further, the FAX server 19 converts facsimile data received via the facsimile 20 into image data of a predetermined format, and stores the converted image data in a reception data storage area (not shown) provided therein. At this time, a notification that the facsimile has been received may be transmitted to the target general-purpose terminal 22 via the management server 16.

The facsimile 20 is controlled by the facsimile server 19, is connected to a predetermined destination or a destination via a general telephone line, and transmits / receives data for facsimile communication.

The printers 21 are, for example, page printers and the like, and are installed for each work group in a department. Upon receiving the print data sent from the general-purpose terminal 22 or the like via the network 2, the printer 21
A document or the like is printed on a predetermined sheet according to the acquired print data.

The general-purpose terminals 22 are composed of, for example, personal computers and are arranged on the desks of users in the workplace. The general-purpose terminal 22 generates print data to be output to the printer 21 or the like, and transmits the generated print data to the printer 21 or the like via the network 2. Note that the general-purpose terminal 22 has a printer 21 before printing.
Is read out from the driver management DB 43 via the management server 16 and installed. After outputting the print data to the printer 21, the general-purpose terminal 22 generates print log (print record) information indicating the number of prints and the like, and transmits the generated print log information to the management server 16. Based on the print log information, the usage of the printer 21 is supplied to the management server 16.

Hereinafter, the management of the use status of the OA equipment performed by the equipment management system 1 according to the embodiment of the present invention will be specifically described with reference to the drawings.

First, the operation when the user operates the multifunction peripheral 11 to copy a predetermined document will be described with reference to FIGS.
This will be described with reference to FIG. FIG. 6A illustrates a copy number counting process performed by the multifunction peripheral management apparatus 12.
9 is a flowchart for explaining a device use information acquisition process performed by the management server 16. The copy number counting process shown in FIG. 6A is started when the user operates the touch panel 32 of the multifunction device management apparatus 12 and inputs a copy operation instruction. The device use information acquisition process shown in FIG. 6B is started in response to the execution of the copy number counting process.

First, the processing control unit 31 of the multifunction peripheral management apparatus 12 waits for processing until an employee number is input (step S11). That is, the processing control unit 3
1 waits for subsequent processing until an employee number is input from the touch panel 32 by a user operation.

When the employee number is input from the touch panel 32, the processing control unit 31 transmits the obtained employee number to the management server 16 and requests authentication of the user (step S12). That is, the processing control unit 31 transmits the input employee number to the management server 16 via the network 2 and requests authentication of the user who operates the multifunction peripheral 11.

The management server 16 includes a processing control unit 31
Upon receiving the employee number transmitted from, the user management DB 41 of the database 15 is searched using the received employee number as a key (step S21).

The management server 16 determines whether the user information has been obtained from the user management DB 41 (step S22). That is, the management server 16 determines whether or not the employee number acquired from the processing control unit 31 is registered in the user management DB 41.

If the management server 16 determines that the user information cannot be acquired, the user operating the multifunction device 11 cannot be authenticated, so information indicating authentication NG (failure) is returned to the multifunction device management device 12 (step S23), the process ends.

On the other hand, if it is determined that the user information has been acquired, the management server 16 returns information indicating that the authentication is OK (success) to the multifunction peripheral management apparatus 12 (step S24).
That is, since the management server 16 has been able to authenticate the user who operates the multifunction peripheral 11, the management server 16 returns information indicating that the authentication is OK to the processing control unit 31 via the network 2.

The processing control unit 31 controls the management server 16
When the information sent from is received, the acquired information is
It is determined whether the information indicates K (step S1).
3). That is, the processing control unit 31
It is determined whether the user who operates is authenticated by the management server 16.

If the processing control unit 31 determines that the authentication is not OK (it is authentication NG), the processing returns to step S11 and repeats the processing of steps S11 to S13. Note that the processing control unit 31 determines in step S1
After it is determined in step 3 that the authentication has failed, a message such as “Please enter the employee number again” may be displayed on the touch panel 32. On the other hand, in step S13,
If it is determined that the authentication is OK, the processing control unit 31
Permits the MFP 11 to perform the copy operation of the user (step S14). That is, the processing control unit 31 supplies a predetermined control signal to the multifunction peripheral 11 to make the multifunction peripheral 11 operable, and permits the user to perform a copy operation.

The processing control unit 31 waits for processing until the user's copy operation is completed (step S1).
5). In the meantime, the user operates the multifunction device 11 to copy a predetermined document as much as necessary.

When the user completes the copy operation, the processing control unit 31 acquires information indicating the number of used copies and the like from the multifunction peripheral 11 (step S16). That is, the processing control unit 31 acquires information indicating the number of sheets used and the number of copies used in the MFP 11 by a user operation.

The processing control unit 31 generates device use information and transmits it to the management server 16 (step S1).
7). That is, the processing control unit 31
Then, information such as an employee number is added to the information such as the number of copies acquired from the device, and device use information as shown in FIG. 7 is generated. Then, the generated device use information is transmitted to the management server 16 via the network 2.

Upon receiving the device usage information sent from the processing control unit 31, the management server 16 stores the obtained device usage information in the device usage management DB 44 (step S25). That is, the management server 16 stores the device usage information indicating the usage of the MFP 11 by the authenticated user in the device usage management DB 44.

As described above, the usage information of the OA equipment such as the multifunction peripheral 11 is sequentially stored in the equipment usage management DB 44 for each user. Then, from the stored usage information, the usage amount of the OA device for each user or each department can be totaled. In addition, calculation such as billing can be performed according to the total usage amount. As a result, the usage status of the OA device can be appropriately managed.

Next, an operation when a user reads a predetermined document with the scanner 13 and records the read image data on a disk medium will be described with reference to FIGS. 8 (a) and 8 (b). FIG. 8A illustrates an image reading process performed by the scanner management device 14, and FIG.
5 is a flowchart for describing device use information acquisition processing performed by the user. The image reading process in FIG. 8A is performed by the user using the touch panel 32 of the scanner management device 14.
Is operated when a scan operation start instruction is input, and the device use information acquisition process of FIG. 8B is started in response to the execution of the image reading process.

First, the processing control unit 35 of the scanner management device 14 waits for subsequent processing until an employee number is input from the touch panel 32 by a user operation (step S31). Then, when the employee number is input, the processing control unit 35 transmits the acquired employee number to the management server 16 and requests authentication of the user (step S32).

The management server 16 having received the employee number searches the user management DB 41 of the database 15 using the obtained employee number as a key (step S41), and determines whether the user information has been obtained (step S42). .

If the management server 16 determines that the user information cannot be obtained, it returns information indicating authentication NG to the scanner management device 14 (step S43), and ends the processing. On the other hand, if it is determined that the user information has been acquired, the management server 16 returns information indicating that the authentication is OK to the scanner management device 14 (step S44).

Upon receiving the information sent from the management server 16, the processing control unit 35 determines that the acquired information is
It is determined whether the information indicates K (step S3).
3). If the process control unit 35 determines that the authentication is not OK (it is authentication NG), the process returns to step S31, and repeats the processes of steps S31 to S33 described above. On the other hand, when it is determined that the authentication is OK, the processing control unit 35 permits the scanner 13 to perform the scanning operation by the user (step S34).

The processing control unit 35 supplies the read image data to the CD-R drive 33 and records it on a disk medium (step S35). That is, the processing control unit 35 converts image data read from a document by a user's scanning operation into, for example, a TIFF format, and records the converted image data on a disk medium stored in the CD-R drive 33.

The processing control unit 35 determines whether or not the scanning operation has been completed (step S36), and stores the read image data in the CD-R until the scanning operation is completed.
The data is sequentially recorded on the disk medium stored in the drive 33. When the scanning operation is completed, the processing control unit 35
Acquires from the scanner 13 information indicating the number of scans used by the user who has operated the scanner 13 (step S37).

The processing control unit 35 generates device use information by adding information such as the employee number to the information on the number of scans acquired from the scanner 13, and sends the generated device use information to the management server 16 via the network 2. It transmits (step S38).

Upon receiving the device usage information sent from the processing control unit 35, the management server 16 stores the obtained device usage information in the device usage management DB 44 (step S45). That is, the management server 16 stores the device usage information indicating the usage of the scanner 13 by the authenticated user in the device usage management DB 44.

As described above, the usage information of the OA equipment such as the scanner 13 is sequentially stored in the equipment usage management DB 44 for each user. Then, from the stored usage information, the usage amount of the OA device for each user or each department can be totaled. In addition, calculation such as billing can be performed according to the total usage amount. As a result, the usage status of the OA device can be appropriately managed.

In step S37, the number of scans is acquired as the amount of use of the scanner 13, but instead of the number of scans, the image capacity (size) recorded on the disk medium by the CD-R drive 33 is used. May be obtained.

Next, the operation when the image data read by the scanner 13 is sent to the customer's customer by e-mail will be described with reference to FIGS. 9 (a) and 9 (b).
FIG. 9A is a flowchart for explaining the scan number counting process performed by the scanner management device 14, and 9B is a flowchart for explaining the device usage information acquisition process performed by the management server 16. Note that the scan number counting process in FIG.
The process is started when the user operates the touch panel 32 to input a mail transmission instruction for image data.
Is started in response to the execution of the scan number counting process.

First, the processing control unit 35 waits for subsequent processing until an employee number is input from the touch panel 32 by a user's operation (step S51). Management server 16
To request user authentication (step S5).
2).

The management server 16 having received the employee number searches the user management DB 41 using the obtained employee number as a key (step S61), and determines whether or not the user information has been obtained (step S62).

If the management server 16 determines that the user information cannot be obtained, it returns information indicating authentication NG to the scanner management device 14 (step S63), and ends the processing. On the other hand, when determining that the user information has been acquired, the management server 16 returns information indicating that the authentication is OK to the scanner management device 14 (step S64).

The processing control unit 35 includes the management server 16
When the information sent from is received, the acquired information is
It is determined whether the information indicates K (step S5).
3). If the processing control unit 35 determines that the authentication is not OK (it is authentication NG), the processing returns to step S51, and repeats the processing of steps S51 to S53 described above. On the other hand, if it is determined that the authentication is OK, the processing control unit 35 requests the management server 16 to transmit the mail address of the customer (step S54).

The management server 16 that has received the mail address transmission request obtains the mail address information from the customer destination management DB 45, and returns the obtained mail address information to the scanner management device 14 (step S65). That is, the management server 16 collectively reads out information including information such as the customer's name and mail address from the customer destination management DB 45 and generates mail address information as shown in FIG. Then, the generated mail address information is returned to the processing control unit 35 via the network 2.

Upon receiving the mail address information sent from the management server 16, the processing control unit 35 displays a list of the obtained mail address information on the touch panel 32 (step S55). The user selects a desired destination from the list displayed on the touch panel 32. In this case, a plurality of transmission destinations may be selectable. When an arbitrary transmission destination is selected by the user, the processing control unit 35 specifies the mail address as the transmission destination, and permits the scanning operation of the user to the scanner 13 (step S56). Then, the user operates the scanner 13 to read an image of a predetermined document.

The processing control unit 35 generates an e-mail attached with the image data read by the user's operation of the scanner and transmits it to the management server 16 (step S5).
7). That is, the processing control unit 35 sets the mail address selected by the user as the destination in the header information, generates an e-mail with the read image data attached, and supplies the generated e-mail to the management server 16 I do.

When the e-mail supplied from the processing control unit 35 is obtained, the management server 16 stores the obtained e-mail in a predetermined mail transmission box (step S66). The management server 16 transmits the electronic mail stored in the mail transmission box to the destination via the Internet or the like at a predetermined timing.

After supplying the electronic mail to the management server 16, the processing control unit 35 obtains information indicating the number of scans from the scanner 13 (step S58). The processing control unit 35 generates device usage information by adding information such as the employee number to the information such as the number of scans acquired from the scanner 13 and transmits the generated device usage information to the management server 16 via the network 2. (Step S5
9).

Upon receiving the device usage information sent from the processing control unit 35, the management server 16 stores the obtained device usage information in the device usage management DB 44 (step S67). That is, the management server 16 stores the device usage information indicating the usage of the scanner 13 by the authenticated user in the device usage management DB 44.

As described above, the usage information of the OA equipment such as the scanner 13 is sequentially stored in the equipment usage management DB 44 for each user. Then, from the stored usage information, the usage amount of the OA device for each user or each department can be totaled. In addition, calculation such as billing can be performed according to the total usage amount. As a result, the usage status of the OA device can be appropriately managed.

In the above processing, the image data read by the scanner 13 is transmitted to the customer as an e-mail, but the read image data may be transmitted to its own mailbox.

Next, the user connects the printer 2 to the general-purpose terminal 22.
The operation when installing the driver software such as No. 1 will be described with reference to FIGS. 11 (a) and 11 (b). FIG.
FIG. 1A shows an installation process performed by the general-purpose terminal 22, FIG.
FIG. 1B is a flowchart illustrating a driver software supply process performed by the management server 16. The installation process shown in FIG. 11A is started when the user operates the general-purpose terminal 22 and inputs a driver software installation start instruction. Further, the driver software supply processing of FIG. 11B is started in response to the execution of the installation processing.

First, the general-purpose terminal 22 requests the management server 16 to transmit the printer device arrangement information (step S7).
1). That is, the general-purpose terminal 22 is connected to the device management system 1.
It requests the management server 16 to transmit the printer device arrangement information including the model name and the location of each printer 21 in the printer.

When the management server 16 obtains the transmission request for the printer device arrangement information, it specifies the device whose device classification is a printer among the devices stored in the device management DB 42, and specifies the model name and the specified device. Information such as the installation location is read all together (step S81). Management server 16
Generates printer device layout information as shown in FIG. 12 from the information read from the device management DB 42, and returns the generated printer device layout information to the general-purpose terminal 22 (step S82).

When the general-purpose terminal 22 acquires the printer device layout information, the general-purpose terminal 22 displays the acquired printer device layout information in a list on a predetermined display unit (step S).
72). When the user selects an arbitrary printer device from the list, the general-purpose terminal 22 transmits the model name of the selected device to the management server 16 and requests transmission of the driver software (step S73).

When the management server 16 acquires the model name and the transmission request of the driver software, the management server 16 accesses the driver management DB 43 and specifies the folder for storing the driver software of the target device (step S83). The management server 16 reads the driver software from the specified storage folder and sends it to the general-purpose terminal 22 (Step S84).

Upon receiving the driver software sent from the management server 16, the general-purpose terminal 22 installs the acquired driver software (step S74).

In this case, even if it becomes necessary to use a different printer 21 (for example, a printer of another department) from the printer 21 normally used connected to the network 2, it is necessary to install the driver software properly. It can be carried out. As a result, the installation work of the printer driver software can be saved, and the latest driver software managed by the management server 16 can always be provided.

In the above embodiment, OA by the user
Device usage information including device usage information is stored in the device usage management DB
Although the storage is sequentially stored in the storage 44, the past usage by the user may be obtained from the device usage management DB 44, and a message corresponding to the obtained usage may be displayed on the touch panel 32 or the like. Hereinafter, a case where the user operates the multifunction peripheral 11 to copy a predetermined document will be described as an example.

First, as shown in step S12 in FIG. 6A, the processing control unit 31 transmits the employee number input by the user to the management server 16 and requests authentication. The management server 16 that has received the employee number, as shown in FIG.
User management DB as shown in steps S21 and S22 of
41 is searched to authenticate the user. At that time, the management server 16 searches the device usage management DB 44 to obtain the past usage of the user.

The management server 16 compares the acquired past usage with a predetermined reference value, and if the past usage exceeds the reference value, sends a predetermined warning message to the processing control unit 31 together with the authentication result. Send. Processing control unit 3
1 displays the acquired warning message on the touch panel 32 when the warning message is acquired.

As described above, by displaying the warning message, it is possible to inform the user on the spot that the usage amount of the user exceeds the reference value. As a result, the user's awareness of the usage amount is increased, and unnecessary copying and the like can be reduced.

(Second Embodiment) In the first embodiment, a system has been described in which the usage of each OA device is totaled. It is possible to give advice.

Hereinafter, a second embodiment in which advice is provided based on the contents of totalization will be described. In the second embodiment, for each OA device, an upper limit value of the usage amount is set, and when the usage amount reaches the upper limit value, a notification can be given. In this case, the device management DB 42 , FIG.
As shown in 3 (a), [Equipment number], [Model name], [Equipment classification], [Network address], [Installation location], [Monthly recommended upper limit], [Yearly recommended upper limit], [Equipment durability] Upper limit] and “substitute machine” are stored.

Here, the "monthly recommended upper limit" is the upper limit (number of copies / month) of the monthly usage (the number of copies, the number of prints, etc.) determined by the specifications of the device. The “yearly recommended upper limit” is the upper limit (number of sheets / year) of the amount of use per year determined by the specifications of the device. The “device endurance upper limit” is the upper limit (number of sheets / life) of the usage amount determined by the specifications of the device. The “substitute machine” is a candidate for a machine that can be used instead when a certain device becomes unusable for some reason.

The device usage amount management DB 44 is stored in FIG.
As shown in (b), in addition to the usage amount for each user, an annual usage amount (number of sheets), a monthly usage amount (number of sheets), and the like are stored.

Next, the operation of this system will be described. First, the user makes a copy with the multifunction device 11 or
When an image is printed by the printer 1 or the printer 21, the management server 16 records the usage amount (number of sheets) of the user (step S25 in FIG. 6B, step S4 in FIG. 8B).
5, FIG. 10 (b), step S67). Further, the management server 16 executes the device usage management DB 4 in these steps.
4 (FIG. 13 (b)), the number of current use is added to the number of monthly use, the number of yearly use, and the total number of use.

The management server 16 resets the monthly usage number registered in the device usage management DB 44 to “0” each time one month passes, and registers the monthly usage number in the device usage management DB 44 each time one year passes. Resets the annual number of sheets used to “0”.

The management server 16, for example, at midnight,
The usage management process shown in FIG. 14 is executed.

First, the management server 16 initializes an OA device number i (step S101). Subsequently, for the OA device i, the device usage management DB 44 (FIG. 13)
From (b)), the number of monthly use, the number of yearly use, and the total number of use are read (step S102).

Next, it is determined whether or not the read “monthly use number” is equal to or more than the monthly recommended upper limit value of the device i registered in the device management DB 42 (FIG. 13A) (step S103). . For example, when i designates the multifunction device having the device number 1234, the monthly recommended upper limit value is 12000 according to FIG. Therefore, step S1
In 02, it is determined whether or not the number of sheets used in the month is 12000 or more.

If it is determined that the monthly usage is equal to or greater than the monthly recommended upper limit (step S103: Yes),
An e-mail as shown in FIGS. 15A and 15B is created and transmitted to the administrator and the user (Step S).
104).

The administrator receives the e-mail shown in FIG. 15A and takes measures such as turning off the power of the device to make it unusable. Further, the user uses the substitute machine notified by the mail shown in FIG. On the other hand, when it is determined that the monthly usage amount is not the monthly recommended upper limit value (step S103: No), step S104 is skipped.

Next, it is determined whether or not the read “annual usage” is equal to or more than the annual usage upper limit registered in the device management DB 42 (step S105).

If it is determined that the annual usage is equal to or more than the annual recommended upper limit (step S105; Yes),
15 (c) and 15 in FIG.
An e-mail illustrated in (d) is created and transmitted (step S106). The administrator receives the notification e-mail and takes measures such as turning off the main power of the apparatus to make it unusable. Further, the user makes a copy or prints on the notified alternative device.

Further, it is determined whether or not the read “total usage” is equal to or more than the durability upper limit value registered in the device management DB 42 for the device i (step S10).
5).

Next, it is determined whether or not the read “total usage” is equal to or greater than the device durability upper limit value registered in the device management DB 42 (step S107).

When it is determined that the total usage is equal to or larger than the device durability upper limit value (step S107; Yes), the administrator and the user are illustrated in FIGS. 15 (a) to 15 (d). An e-mail similar to the e-mail to be created is created and transmitted (step S108). The administrator receives the notification e-mail, and takes measures such as turning off the main power of the apparatus and making it unusable. In addition, the user makes a copy or prints using the notified alternative device.

Subsequently, it is determined whether or not the device number i has reached the final value, that is, whether or not the processing for all the devices has been completed (step S109). (Step S109); No), the device number i is updated, and the same processing as described above is repeated.

Finally, when it is determined that the device number i has reached the final value, that is, the process for all devices has been completed (step S109; Yes), the process ends.

With such a configuration, it is possible to prevent each device from being used far beyond its specifications.

(Third Embodiment) It is also possible to totalize the usage of each OA device and notify the user that it is time to replace the consumables. An embodiment of such a system will be described below. In the third embodiment, as shown in FIG. 16, in the device management DB 42, [device number], [model name], [device class], [network address], [installation location], [consumables] [1 replacement number], [consumable number 1], [consumable number 2], [consumable number 2], [consumable number 3], [consumable number 3],
“Alternative machine” is stored.

Here, the “consumables replacement number 1” is the total used amount (printed number) of the device when the first consumable (eg, toner) of the device was replaced last time.
“Consumables contact number 1” indicates whether the consumables have been replaced.
This is the number of sheets to be used to notify that replacement of the consumables should be performed, and is set to a number slightly smaller than the number of sheets that can be printed using one consumable.

[0128] The "consumables replacement number 2" is the total amount of use (number of prints) of the device at the time when the second consumables (for example, photoconductors (drums, belts)) of the device were replaced last time.
It is. The “consumables contact number 2” indicates the number of times the consumables have been replaced and used to notify the user that the consumables should be replaced. The number is set slightly smaller than the number that can be printed.

"Consumables replacement number 3" is the total used amount (printed number) of the device when the third consumable of the device was replaced last time. The “consumables contact number 3” is a number indicating how many times the consumables have been replaced and used to notify the user that the consumables should be replaced.

[0130] The "alternative machine" is a candidate for a machine that can be used instead when a certain device becomes unusable due to consumption of consumables.

[Consumable replacement quantity 2], [Consumable replacement quantity 2], [Consumable replacement quantity 3], [Consumable replacement quantity 3]
Set as needed.

For example, the management server 16
The consumable steel pipe notification processing of FIG. 17 is executed. First, the management server 16 initializes the OA device number i (step S121).

Subsequently, for the device i, the total number of used devices is counted from the contents of the device usage management DB 44 (step S122). The device usage management DB shown in FIG.
As in 44, the total number of sheets used may be obtained in advance.

Next, the read “total use amount” is equal to or greater than the sum of “consumables replacement number 1” and “consumables contact number 1” of device i registered in device management DB 42 (FIG. 16). It is determined whether or not there is (step S123). In other words, the amount of equipment used since the first consumable was replaced,
It is determined whether or not “consumables contact number 1” or more has been reached.

“Total usage” is “Number of consumables replaced 1”
If it is determined that the sum is equal to or more than the “consumables contact number 1” (step S123; Yes), an e-mail as shown in FIGS. 18 (a) and 18 (b) is sent to the administrator and the user. Create and transmit (step S124). These e-mails notify the administrator and the user that the consumables are about to be replaced soon, that printing may be defective due to the consumption of consumables, and that the substitute machine is notified. It is.

The administrator receives the mail shown in FIG. 18A and prepares for replacement of the consumables. Further, the user uses the substitute machine notified by the mail shown in FIG. 18B as necessary.

On the other hand, if it is determined that the total used amount is less than the sum of “consumables replacement number 1” and “consumables contact number 1” (step S123; No), step S123 is performed.
Skip 124.

Next, if necessary, the consumable 2 and the consumable 3
(S125 to S12)
8).

Subsequently, it is determined whether or not the device number i has reached the final value, that is, whether or not the processing for all the devices has been completed (step S129). (Step S129); No), the device number i is updated (Step S130), the process returns to Step S122, and the same processing as described above is repeated.

Finally, if it is determined that the device number i has reached the final value, that is, if it is determined that the processing for all devices has been completed (step S129; Yes),
The process ends.

By adopting such a configuration, it is possible to know in advance the replacement time of the consumables of each device and to prevent a printing error due to the consumption of the consumables.

(Fourth Embodiment) Hereinafter, O
A description will be given of an embodiment of a system that can set an upper limit of the usage amount of the device A and notify the administrator or the like when the usage amount reaches the upper limit value.

In this example, the user management database 4
19, [Employee Number], [Name], [Department Code], [Department Name], [Phone Number], [Fax Number], [E-mail Address], [Monthly Printed Number] as shown in FIG. , [Monthly print count upper limit], [Annual print count], [Annual print count upper limit], [Annual recommended upper limit] are stored.

Here, the “monthly number of prints” is the number of prints (number / month) of a certain month of the user. The “maximum number of printed pages per month” is the upper limit (number of printed pages / month) of the number of printed pages for a certain month of the user, and is set individually according to job or position. “Annual number of prints” is the number of prints (number / year) of the user in a certain year. `` Annual print limit ''
This is the upper limit (number of prints / year) of the number of prints for a certain year of the user, and is set individually according to job or position.

Next, the operation of this system will be described. First, when a user makes a copy with the multifunction peripheral 11 or prints an image with the printer 21, the management server 16
Manages the usage amount (number of sheets) for each user by the device usage management D
Recorded in B44 (FIG. 6B step S25, FIG. 8B step S45, FIG. 10B step S67). Further, the management server 16 executes the user management DB 4 in these steps.
The number used this time is added to the number of months used and the number of years used registered in 1 (FIG. 19).

The management server 16 resets the monthly usage number registered in the device usage DB 44 to “0” each time one month elapses, and resets the device usage D every one year.
The annual number of sheets registered in B44 is reset to “0”.

For example, the management server 16
The processing of FIG. 20 is performed. First, the user number i is initialized (step S141).

Subsequently, for the user i, the user management D
From B41 (FIG. 19), the number of months used, the upper limit of the number of printed pages per month, the number of used pages per year, and the upper limit of the number of printed pages per year are read (step S142).

Next, it is determined whether or not the read “monthly usage amount” is equal to or more than the upper limit of the number of monthly printed sheets (step S143).

If it is determined that the monthly usage is equal to or greater than the upper limit of the number of printed pages per month (step S143: Yes), the administrator and the user are notified to FIG. 21 (a) and FIG.
An e-mail as shown in (b) is created and transmitted (step S144). These e-mails have contents for notifying the administrator and the user that the print amount of the user has exceeded the upper limit.

On the other hand, when it is determined that the monthly usage amount is not the upper limit of the monthly print number (step S143: N).
In step o), step S144 is skipped.

Next, it is determined whether or not the read “annual number of prints” is equal to or larger than the annual print number upper limit (step S145).

When it is determined that the annual print number is equal to or more than the annual print number upper limit value (step S145; Yes)
In FIG. 21 (a) and FIG.
An e-mail similar to the e-mail illustrated in FIG. 1 (b) is created and transmitted (step S146).

Subsequently, it is determined whether or not the user number i has reached the final value, that is, whether or not the processing has been completed for all users (step S147), and it is determined that the processing has not been completed. If (Step S147); No, the user number i is updated, the process returns to Step S142, and the same processing as described above is repeated.

Finally, when the user number i has reached the final value,
That is, when it is determined that the processing has been completed for all users (step S147; Yes), the processing is terminated. With such a configuration, it is possible to prevent a situation where each user performs an abnormally large amount of printing.

(Fifth Embodiment) In the fourth embodiment, the upper limit of the amount of OA equipment used is set for each user. For example, the upper limit can be set for each department (section) of a company. It may be.

In this example, the user management DB 41 stores
It includes a department management DB 48 as shown in FIG. This department management DB includes items such as [department code], [department name],
[Constitution Employee Number], [Constitution Employee Name], [Monthly Prints],
It has [Maximum number of prints per month], [Annual number of prints], and [Upper limit of number of annual prints].

Here, “department code” and “department name” are
The code and name of the department. "Constituent employee number"
The employee number of the employee belonging to the department is shown, and the “constituent employee name” is the name of the employee belonging to the department. The number of printed sheets per month is the number of printed sheets (number of sheets / month) in a certain month for employees belonging to each department. "Maximum number of prints per month" is the upper limit of the number of prints for each month assigned to the department (number of copies / month)
, And are set individually according to the content and the number of duties of the department. “Annual number of prints” is the number of prints (number / year) of the department in a certain year. `` Annual print quantity upper limit ''
Is the upper limit of the number of printed sheets (number of sheets / year) of the department.

Next, the operation of this system will be described with reference to the flowchart of FIG. First, when a certain user makes a copy using the multifunction peripheral 11 or prints an image using the printer 21, the management server 16 records the usage amount (number of copies) for each user in the device usage management DB 44 ( FIG. 6 (b) Step S25, FIG. 8 (b) Step S4
5, FIG. 10 (b), step S67). Further, in these steps, the management server 16 determines the department to which the user belongs, and adds the current usage number to the monthly usage number and the annual usage number registered in the department management DB 48 (FIG. 22).

The management server 16 sets the monthly use number registered in the department management DB 48 to “0” every one month.
And the annual number of sheets registered in the department management DB 48 is reset to “0” every year.

For example, the management server 16
The department-specific usage management process shown in FIG. 23 is executed. First,
The department number i is initialized (step S151).

Subsequently, for the department i, the department management DB 4
From FIG. 8 (FIG. 22), the monthly use number, the monthly print number upper limit value, the annual use number, and the annual print number upper limit value are read (step S152).

Next, it is determined whether or not the read “monthly print number” is equal to or more than the monthly print number upper limit value (step S153).

When it is determined that the number of monthly prints is equal to or greater than the upper limit of the number of monthly prints (step S153: Yes).
Figure 2 shows the administrator and the users belonging to the department.
An electronic mail as shown in FIG. 4A and FIG. 24B is created and transmitted (step S154). These e-mails are contents that notify the administrator and the user that the number of prints of the department exceeds the upper limit.

On the other hand, if it is determined that the number of monthly prints is not complete (step S153: N)
In step o), step S154 is skipped.

Next, it is determined whether or not the read “annual number of prints” is equal to or more than the upper limit of the number of annual prints (step S155).

When it is determined that the annual print number is equal to or more than the annual print number upper limit value (step S155; Yes).
In FIG. 24A and FIG.
An e-mail similar to the e-mail illustrated in FIG. 4 (b) is created and transmitted (step S156).

Subsequently, it is determined whether or not the department number i has reached the final value, that is, whether or not the processing has been completed for all the departments (step S157). (Step S157); No), the department number i is updated, the process returns to Step S152, and the same processing as described above is repeated.

Finally, when it is determined that the department number i has reached the final value, that is, the processing for all the departments has been completed (step S157; Yes), the processing is terminated.

By adopting such a configuration, it is possible to prevent each department from performing a large amount of printing.

(Sixth Embodiment) According to the above embodiments, collected information can be analyzed and used for efficient use of each device. The following describes such an embodiment.

In this example, as shown in FIG. 13A, the device management DB 42 stores [device number], [model name], [device type], [network address], [installation location], [.・
-], [Monthly recommended upper limit], [Yearly recommended upper limit], [Monthly recommended lower limit], and "Monthly recommended upper limit" are stored.

Here, the “monthly recommended upper limit value” is the upper limit value of the monthly usage amount (number of sheets / month) determined by the specifications of the device.
It is. The “yearly recommended upper limit” is the upper limit (number of sheets / year) of the amount of use per year determined by the specifications of the device. Here, the “monthly recommended lower limit value” is a lower limit value (number of sheets / month) of monthly usage determined by the specifications of the device. The “yearly recommended lower limit” is the lower limit (number of sheets / year) of the amount of use per year determined by the specifications of the device.

Further, the device usage DB 44 is stored in FIG.
As shown in (b), in addition to the usage amount for each user, an annual usage amount (number of sheets), a monthly usage amount (number of sheets), and the like of each device are stored.

Next, the operation of this system will be described with reference to the flowchart of FIG. First, when a user makes a copy or prints an image with a printer using the multifunction peripheral 11, the management server 16 records the usage amount (number of sheets) for each user (FIG. 6B, step S25). , FIG.
(B) Step S45, FIG. 10 (b) Step S6
7). Further, in these steps, the management server 16 adds the current number of used sheets to the monthly used number, the annual used number, and the total used number registered in the device usage amount management DB 44 (FIG. 13B).

The management server 16 resets the monthly usage number registered in the device usage DB 44 to “0” each time one month passes, and resets the device usage D every time one year passes.
The annual number of sheets registered in B44 is reset to “0”.

[0177] Further, the administrator can extract either a device whose usage is higher than the monthly or annual recommended upper limit, or a device whose usage is lower than the monthly or annual recommended lower limit, or extract both. Is set in advance.

The management server 16 executes the use status management process shown in FIG. 26, for example, every one month.

First, it is determined whether extraction of both the equipment whose usage amount is equal to or more than the upper limit value and the equipment whose usage amount is equal to or less than the lower limit value is selected, or extraction of only the equipment whose usage amount is equal to or more than the upper limit value or less than the lower limit value is selected. Is determined (step S161).
When it is determined that the extraction of both the device whose usage amount is equal to or more than the upper limit value and the device whose usage amount is equal to or less than the lower limit value is selected (Step S
161; No), first, the device number i is initialized (step S162).

Subsequently, for the device i, the device usage DB
44 (FIG. 13 (b)), and reads the monthly and annual recommended upper limit values and the monthly and annual recommended lower limit values from the device management DB 42 (FIG. 25) (step S163).

Next, it is determined whether or not the read “monthly usage amount” is equal to or more than the monthly recommended upper limit value of the device i or equal to or less than the monthly recommended lower limit value (step S164).

If the monthly usage is determined to be equal to or greater than the monthly recommended upper limit or equal to or less than the monthly recommended lower limit (step S164: Yes), FIG.
Device i is added to one of the lists shown in (a) and (c). That is, when it is determined that the monthly usage is equal to or more than the monthly recommended upper limit, the device i is added to the list illustrated in FIG. On the other hand, if it is determined that the monthly usage is equal to or less than the monthly recommended lower limit, the device i is added to the list shown in FIG.

On the other hand, if it is determined that the monthly usage amount is not completed and the monthly recommended upper limit value is not completed and is larger than the monthly recommended lower limit value (step S164: No), step S165 is skipped.

Next, it is determined whether or not the read “annual usage” is equal to or more than the annual recommended upper limit value or equal to or less than the annual recommended lower limit value for the device i (step S166).

If it is determined that the annual usage is equal to or more than the annual recommended upper limit or equal to or less than the annual recommended lower limit (step S166: Yes), the process shown in FIG.
Device i is added to one of the lists shown in (b) and (d). That is, when it is determined that the annual usage is equal to or more than the annual recommended upper limit, the device i is added to the list shown in FIG. On the other hand, when it is determined that the annual usage is equal to or less than the annual recommended lower limit, the device i is added to the list shown in FIG.

On the other hand, if it is determined that the annual usage amount is not completed and the annual recommended upper limit is not completed and is larger than the annual recommended lower limit (step S166: No), step S167 is skipped.

Subsequently, it is determined whether or not the device number i has reached the final value, that is, whether or not the processing for all the devices has been completed (step S168). (Step S168); No), Step S1
At 69, the device number i is updated, and the process returns to step S163 to repeat the same processing as described above.

Finally, when it is determined that the device number i has reached the final value, that is, the process for all the devices has been completed (step S168; Yes), the process ends.

By adopting such a configuration, it is possible to determine a device that is used excessively or a device that is not used often, and to change the installation location of the device, etc., and to use it as a material for efficiently using the device. Can be.

In the above description, the usage of the device is compared with the recommended upper limit and the recommended lower limit. However, only the usage of the device and the recommended upper limit are compared, and only the overused device is extracted and listed. Alternatively, a list may be created by comparing only the usage amount of the device and the recommended lower limit value, and extracting only the device that is hardly used. If such a setting has been made, “YES” is determined in the step S161, and only the process related to the upper limit or the lower limit is executed in the step S170.

Further, the past usage of each device is accumulated in units of months and years, and an arbitrary month or year is designated so that the usage of the month or year can be compared with the recommended value. You may.

The lists shown in FIGS. 27 (a) to 27 (d) are merely examples. For example, the list includes the usage amounts of all devices and the upper and lower limits, and the usage amounts indicate the upper limit values. Those exceeding or lower than the lower limit may be displayed and printed in a form that allows identification (for example, color-coding).

Further, the process relating to the monthly recommended value (steps S164 and S165) is executed every month (each time the usage amount for January is obtained), and the process relating to the annual recommended value (steps S166 and S167) is performed. It may be executed every one year (every one year of usage is calculated).

(Seventh Embodiment) When the printer driver software is upgraded, the user may be notified of the fact.

In this example, the [driver name], [version], [storage folder], and [downloader list] are stored in the driver management DB 43 as shown in FIG.

In the “downloader list”, the employee number of the person who downloaded the driver software is registered. Each employee number is set with a flag (Y: N) indicating whether a notification is desired when the driver is updated. The flag Y is a flag indicating that notification is desired, and the flag N is a flag indicating that notification is not desired.

Next, a usage status management process executed by the management server 16 will be described. First, when the user installs the driver software on the general-purpose terminal 22, the user:
In step S73, when the driver is updated, it is specified whether or not a notification of the update is desired. Management server 16
Registers the employee number of the downloader in the driver management DB 43 shown in FIG. Also, a flag “Y” or “N” indicating the designated desire is set.

The management server 16 has a driver management DB 43
When the version information is updated, a driver update notification process shown in FIG. 29 is executed.

First, the number i of the downloader is initialized (step S181). Subsequently, information on the i-th downloader in the downloader list on the driver management DB 43 shown in FIG. 28 is obtained (step S182).
Next, it is determined whether the flag in the acquired downloader information is “Y” or “N” (step S183). If the flag is Y, that is, if the downloader wants to be notified when the driver is updated, the e-mail address is acquired from the employee number with reference to the user management DB 41 and recorded (step S184). .

Subsequently, it is determined whether or not the downloader number i has reached the final value, that is, whether or not the processing has been completed for all downloaders (step S185).
If it is determined that the processing has not been completed (step S185);
No), the downloader number i is updated in step S186, the process returns to step S182, and the same processing as described above is repeated.

Finally, when it is determined that the downloader number i has reached the final value, that is, that the processing for all the downloaders has been completed (step S187; Ye)
s) An e-mail as shown in FIG. 30 is created and transmitted to the e-mail address stored in step S184.

For example, assume that the driver software of the printer BCD-2345 has been upgraded to version 2.03 as registered in the driver management DB 43 of FIG. Then, the management server 16 reads “N: 1234567” from the downloader list as the information of the first downloader. In this case, since the flag N is set, the employee number 1234567 is set.
Do not send email to Subsequently, “Y: 2348788” is read as the information of the second downloader. In this case, since the flag Y is set, a mail as shown in FIG. 30 is transmitted to the user of the employee number 2348878.

With this configuration, the user can easily know that the driver has been upgraded. Then, the driver can be installed as needed.

As described above, in the second to sixth embodiments, the example of the method of managing the OA device using the information collected by the management server 16 has been described. However, these management methods are merely examples, and the present invention is not limited to these.

In the above embodiment, the user is authenticated by the input employee number when authenticating the user. However, the identification information for identifying the user is not limited to the employee number and the like, but is arbitrary. The input method of the identification information is the touch panel 3
It is not limited to 2 and the like, and is arbitrary. For example, identification information may be input by reading a magnetic card or an IC card on which an employee number or the like is recorded with a predetermined card reader.

The device management system according to the embodiment of the present invention can be realized by using a general computer system without using a dedicated system. For example, a medium (floppy (registered trademark) disk, CD-RO) storing a program for executing any of the above-described processes in a computer operating under the control of a network OS
M), the device management system that executes the above-described processing can be configured.

The method for supplying the program to the computer is arbitrary. For example, the information may be supplied via a communication line, a communication network, a communication system, or the like. As an example, a bulletin board (BB) of a communication network
The program is posted on S), transmitted by being superimposed on a carrier wave, and distributed via a network. And
By starting this program and executing it in the same manner as other application programs under the control of the OS, the above-described processing can be executed.

[0208]

As described above, according to the present invention,
Equipment can be managed properly.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating an example of a configuration of a device management system according to an embodiment of the present invention.

FIG. 2A is a block diagram illustrating a detailed configuration of a multifunction peripheral management device, and FIG. 2B is a block diagram illustrating a detailed configuration of a scanner management device.

FIG. 3 is a block diagram showing a detailed configuration of a database.

4A is a schematic diagram illustrating an example of information stored in a user management DB, FIG. 4B is a schematic diagram illustrating an example of information stored in a device management DB, and FIG. FIG. 4 is a schematic diagram illustrating an example of information stored in a driver management DB.

FIG. 5A is a schematic diagram illustrating an example of information stored in a device usage management DB, and FIG. 5B is a customer destination management DB;
FIG. 3 is a schematic diagram illustrating an example of information stored in a storage device.

FIG. 6 is a flowchart illustrating a copy sheet count process and a device use information acquisition process according to the embodiment of the present invention.

FIG. 7 is a schematic diagram illustrating an example of device usage information generated by a processing control unit.

FIG. 8 is a flowchart illustrating an image reading process and a device use information obtaining process according to the embodiment of the present invention.

FIG. 9 is a flowchart illustrating a scan sheet count process and a device use information acquisition process according to the embodiment of the present invention.

FIG. 10 is a schematic diagram illustrating an example of mail address information sent from a management server.

FIG. 11 is a flowchart illustrating an installation process and a driver software supply process according to the embodiment of the present invention.

FIG. 12 is a schematic diagram illustrating an example of printer device arrangement information sent from the management server.

FIG. 13A shows a configuration example of a device management DB according to a second embodiment of the present invention, and FIG. 13B shows a configuration of the device usage management DB according to the second embodiment of the present invention; FIG. 3 is a diagram illustrating a configuration.

FIG. 14 is a flowchart illustrating a usage management process executed by a management server according to the second embodiment of this invention.

FIGS. 15A and 15B are examples of e-mails transmitted to an administrator and a user, respectively, when the monthly usage amount of a device exceeds a recommended monthly upper limit. ) And (d)
Is an example of an e-mail sent to the administrator and the user when the annual usage of the device exceeds the annual recommended upper limit.

FIG. 16 is a diagram illustrating a configuration example of a device management DB according to a third embodiment of the present invention.

FIG. 17 is a flowchart illustrating a consumables replacement notification process executed by the management server according to the third embodiment of this invention.

FIGS. 18A and 18B are examples of e-mails transmitted to an administrator and a user when replacement of consumables of a device is approaching, respectively.

FIG. 19 is a diagram illustrating a configuration example of a user management DB according to a fourth embodiment of the present invention.

FIG. 20 is a flowchart for explaining individual usage management processing executed by the management server according to the fourth embodiment of the present invention.

FIGS. 21A and 21B are examples of e-mails transmitted to the administrator and the user when the print amount of the user exceeds the upper limit of the number of monthly prints, respectively.

FIG. 22 is a diagram illustrating a configuration example of a department management DB according to the fifth embodiment of the present invention.

FIG. 23 is a flowchart illustrating a department-specific usage management process performed by the management server according to the fifth embodiment of this invention.

FIGS. 24A and 24B are examples of electronic mail transmitted to an administrator and a user when the printing amount of a certain department exceeds the monthly usage upper limit value, respectively.

FIG. 25 is a diagram illustrating a configuration example of a device management DB according to a sixth embodiment of the present invention.

FIG. 26 is a flowchart illustrating a usage status management process performed by a management server according to a sixth embodiment of the present invention.

FIGS. 27A and 27B are diagrams showing examples of a list of devices used exceeding the monthly recommended upper limit and the annual recommended upper limit, respectively. FIGS. It is a figure which shows the example of the list of the apparatus used below the monthly recommended lower limit and the annual recommended lower limit, respectively.

FIG. 28 is a diagram illustrating a configuration example of a driver management DB according to a seventh embodiment of the present invention;

FIG. 29 is a flowchart illustrating a driver update notification process executed by the management server according to the seventh embodiment of this invention.

FIG. 30 is a diagram illustrating an example of an e-mail notifying a user who has downloaded a driver that the driver has been updated.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Device management system 11 Multifunction machine 12 Multifunction machine management device 13 Scanner 14 Scanner management device 15 Database 16 Management server 17 Business card print management device 18 Business card print printer 19 FAX server 20 Facsimile 21 Printer 22 General-purpose terminal 31, 35 Processing control unit 32 Touch panel 33 CD-R drive 34 Business card scanner 41 User management DB 42 Device management DB 43 Driver management DB 44 Device usage management DB 45 Customer destination management DB 48 Department management DB

Claims (19)

[Claims] 1. A device management system for managing a device to be managed connected to a network, comprising: an authentication unit for authenticating a user who operates the device; and an operation performed by the user authenticated by the authentication unit. A device management system comprising: a use information acquisition unit that acquires device use information including a use amount of a device; and a use information storage unit that stores the device use information acquired by the use information acquisition unit. 2. The apparatus according to claim 1, wherein the authentication unit stores user information for identifying a user who is permitted to operate the device in advance, and identification information for identifying a user who operates the device. Identification information input means for inputting, and means for authenticating a user who operates the device in accordance with the identification information input by the identification information input means and the user information stored in the user information storage means. The usage information acquisition unit includes: a counting unit that counts a usage amount of a device by a user operation authenticated by the authentication unit; a usage amount counted by the counting unit; and a user authenticated by the authentication unit. Usage information generating means for generating device usage information including information specifying the
The device management system according to claim 1, further comprising: 3. A usage amount acquisition unit for acquiring a past usage amount of the device from the device usage information stored in the usage information storage unit; and a usage amount acquired by the usage amount acquisition unit. Comparing means for comparing the reference value with the reference value, and output means for outputting a predetermined message to a user of the device and / or a manager of the device according to a result of the comparison by the comparing device. The device management system according to claim 1. 4. A use amount acquisition unit for acquiring a past use amount of an arbitrary device by an arbitrary user from device use information stored in the use information storage unit, and a use amount acquired by the use amount acquisition unit. 2. The apparatus according to claim 1, further comprising: comparing means for comparing the amount with a predetermined reference value; and outputting means for outputting a predetermined message to the user according to a result of the comparison by the comparing means. The device management system according to 1. 5. A usage amount obtaining means for obtaining a usage amount of a device after replacement of a consumable of the device from the device usage information stored in the usage information storage means; A comparing unit that compares the obtained usage amount with a predetermined reference value, and outputs a predetermined message to a user who operates the device and / or a manager of the device according to a comparison result by the comparing unit. The apparatus management system according to claim 1, further comprising: an output unit. 6. A usage amount obtaining unit for obtaining a past usage amount of a device for each department to which a user belongs from a device usage information stored in the usage information storage unit; A comparison unit that compares the usage amount with a predetermined reference value; and an output unit that outputs a predetermined message to a user and / or a device administrator according to a comparison result by the comparison unit. The device management system according to claim 1, wherein: 7. A device management system for managing software of a terminal device for controlling a device to be controlled connected to a network, wherein driver software of the terminal device necessary for controlling the device to be controlled is stored in advance. Driver software storage means, correspondence information storage means for storing correspondence information defining correspondence between the driver software stored in the driver software storage means and the control target device, and a control target device to be controlled from the terminal device. Selecting means for selecting, according to the correspondence information stored in the correspondence information storage means,
Specifying means for specifying the driver software of the control target device selected by the selecting means; and installing means for supplying the driver software specified by the specifying means to the terminal device via a network and installing the driver software on the terminal device. A device management system comprising: 8. A means for inputting information of a person who installed the driver software on a terminal device, an installer storage means for storing information for identifying an installer based on the input information, and the driver software storage means. Output means for determining, when the driver software stored in the driver software is updated, the installer of the driver software from the stored contents of the installer storage means, and outputting a predetermined message to the determined user. The method according to claim 7, further comprising:
The device management system according to 1. 9. An installer storage means stores information indicating whether a notification is desired in association with a user who has installed the driver software, and the output means is stored in the driver software storage means. When the driver software is updated, the installer of the driver software who wants to be notified is
The device management system according to claim 7, wherein a predetermined message is output. 10. A system comprising a device to be managed mutually connected via a network, and a management device for managing the device to be managed, wherein the management device uses the device which is permitted to operate the device. Each device transmits identification information for identifying a user of the device to the management device, and the management device receives the transmitted identification information. Then, according to the received identification information and the stored user information, authenticate the user, notify the authentication result to the device, the device allows the operation of the user authenticated by the management device, A device management system, wherein the management device obtains the usage amount of the user and notifies the management device, and the management device stores the notified usage amount and the user and the used device in association with each other. 11. The device according to claim 10, wherein the management device outputs a predetermined message to a user and / or a manager of each device based on the stored use information. Management system. 12. Identification information for identifying a user who operates a device and is a management client that communicates via a network with a management server that manages a device to be managed connected to the network. Information input means for inputting the identification information input by the information input means to the management server, and an authentication means for authenticating a user who operates the device in accordance with the response information; Counting means for counting the usage amount of office equipment by the user, and usage information transmitting means for transmitting device usage information including the usage amount counted by the counting means to the management server, characterized by comprising: Admin client to do. 13. A management server for managing a device to be managed connected to a network via a management client, wherein user information for specifying a user who is permitted to operate the device is stored in advance. A storage device to perform, identification information acquisition means for acquiring identification information for identifying a user operating a device from a management client via a network, identification information acquired by the identification information acquisition means,
According to the user information stored in the user information storage unit, an authentication unit that authenticates a user who operates the device, and device usage information including a usage amount of the device by the operation of the user authenticated by the authentication unit. A management server comprising: a use information acquisition unit that acquires from a management client via a network; and a use information storage unit that sequentially stores the device use information acquired by the use information acquisition unit. 14. A use status management method for managing the use status of a device to be managed connected to a network, comprising: authenticating a user who operates the device; and using the device by an operation of the authenticated user. And acquiring device usage information including the determined usage amount, and storing the acquired device usage information in a predetermined database. 15. The usage management method according to claim 14, wherein the device usage information stored in the database is processed, and a predetermined message is transmitted to a user and / or a manager of the device. . 16. A method for managing software of a terminal device for controlling a device to be controlled connected to a network, comprising: driver software for the terminal device required to control the device to be controlled; Correspondence information that defines correspondence with the device is stored in the storage device in advance, a control target device to be controlled is selected from the terminal device, and the selected control target device is A software management method comprising: specifying driver software; supplying the specified driver software to a terminal device via a network; and installing the driver software in the terminal device. 17. The information of a user who has installed the driver software is stored in a storage device, and when the driver software stored in the storage device is updated, an installer of the driver software is notified to the storage device. 17. The software management method according to claim 16, further comprising: discriminating from the stored contents, and notifying the discriminated user of a predetermined message. 18. A use status management method for managing the use status of a device to be managed connected on a network, comprising: an authentication step for authenticating a user who operates the device; and an authentication step for the authentication step. A counting step of counting the usage amount of the device by the user operation performed, a usage information obtaining step of obtaining device usage information including the usage amount counted in the counting step, and an obtaining step of obtaining the usage information. And a storage step of sequentially storing the obtained device usage information in a predetermined database. 19. A program for causing a computer to execute software management of a terminal device for controlling a device to be controlled connected to a network, wherein the program defines correspondence between driver software stored in advance and the device to be controlled. Based on the corresponding information obtained, the terminal device receives information specifying the control target device to be controlled from the terminal device, and converts the driver software of the terminal device necessary for operating the specified control target device and the determined driver software to the terminal device. A program that can be provided and installed on a computer.