JP2013182437A - Device monitoring method and system thereof, and management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem in which the replacement of a consumable part of a device is performed by a serviceman and not performed by a user and therefore, the device cannot be available when a consumable part reaches the end of the life and the user has to wait for the arrival of a serviceman.SOLUTION: A management server detects a part which reaches the end of the life, from part information of a device, and issues a part replacement request notification to a user. Consequently, the user can reduce a period when the device cannot be available.

Description

  The present invention relates to a device management method of a device management system using network communication, a system thereof, and a management apparatus. In particular, the present invention relates to a mechanism by which a user can actively perform a component replacement operation and an application program for realizing it in order to reduce the time during which a device cannot be used when a consumable component of the device reaches the end of its life.

  Conventionally, devices in the commercial printing field have a mechanism called operator maintenance (hereinafter referred to as operation). This is a mechanism in which a user having the role of an operator can exchange device parts. The idea relates to a mechanism (hereinafter referred to as user maintenance) that allows a user to replace parts in the field of office printing.

  By using the user maintenance, the user can replace the parts without waiting for the arrival of the service person, and can reduce the downtime of the device.

  Conventionally, as a method for prompting a user to replace consumables, there is a method of giving a service point in accordance with the replacement of consumables (for example, see Reference 1). Here, the user gives a service point to the user by exchanging the toner cartridge and the bottle, and uses this point for other services.

Patent No. 4111847

  However, in Patent Document 1, it is not possible to select replacement of parts in accordance with the user's device usage conditions. Since the roles of the service person and the user are determined, there is a problem that the burden on the user in exchanging parts is increased.

  The present invention provides a method and system for enabling selection of a part replacement type according to a user's device usage conditions, determining the roles of a user and a service person according to the conditions at that time, and allowing appropriate personnel to replace the parts. I will provide a.

In order to solve the above-described problems, the device management system of the present invention provides:
A device management system comprising a management server that manages a plurality of devices via a network, and a device that is connected to the network and used, and that requires replacement of a component at the end of its component life. A first transmission function (414) for transmitting device product information and device identification information to the management server, a second transmission function (414) for transmitting the device usage status to the management server, and parts for replacement parts Receiving function (414) for receiving replacement instructions, I / O function when receiving parts replacement instructions via I / O function (operation panel) (401) and receiving function for displaying and receiving information to the user A component replacement notification function (401) that prompts the user to replace the component via the management server, and the management server performs user replacement for component replacement from the device, device product information, and device identification. A first receiving function (601) for receiving different information, a second receiving function (601) for receiving the usage status of the device from the device, user information received by the first receiving function, device product information, Depending on the usage status of the device received by the maintenance information storage function (606/608) and the second reception function that stores device identification information in the storage area, the user should request replacement or replace it with a service person A judgment function (611) for judging whether or not to request a replacement, and a parts replacement instruction function (601) for issuing a part replacement instruction to the device when the judgment function determines that the user should request replacement. A device management system comprising:

  According to the present invention, it is possible to reduce the downtime of the device by enabling the user to perform the component replacement for the component for which the user himself / herself recognizes the necessity for the component replacement.

It is a figure which shows the network connection relationship with a device and a management server. It is a figure which shows the hardware structural example of a device. It is a figure which shows the structural example of the hardware control part of a device. It is a figure which shows the software function structural example of a device. It is a block diagram which shows the hardware structural example of a management server. It is a block diagram which shows the example of a software function structure of a management server. It is a figure showing the data structural example in the memory | storage device of a management server. It is a figure showing the sequence of communication at the time of installation of a device and a management server. FIG. 3 is a diagram illustrating a first example of device usage state. FIG. 10 is a diagram illustrating a second example of device usage state. FIG. 10 is a diagram illustrating a third example of device usage state. It is a flowchart showing the operation example of a management server. It is a flowchart showing the operation example of a device. It is a figure showing the example of operation UI of a device.

  The best mode for carrying out the present invention will be described below with reference to the drawings.

<Configuration example of device management system of this embodiment>
FIG. 1 is a diagram showing a connection relationship in a network between a copier according to an embodiment of the present invention and a management server.

  In FIG. 1, reference numeral 100 denotes an MFP (Multi Function Printer) or SFP (Single Function Printer) connected to the customer's in-house network. These devices having functions such as printing and copying are called devices here.

  Reference numeral 101 denotes a management server that manages a plurality of devices.

  Although a management server is placed on the Internet as a general form here, there is no particular limitation as long as it communicates with a device via a network.

  Reference numeral 102 denotes a customer's in-house LAN. In addition to devices, a PC (personal computer) and a server are connected to this network.

  103 represents the Internet. In the figure, the customer's internal LAN is drawn on the Internet, but in fact, an infinite number of internal LANs similar to 102 are connected to the Internet.

  Reference numeral 104 denotes a firewall which is a connection point between the corporate network and the Internet. The firewall 104 prevents unauthorized network access from the Internet to the corporate LAN 102.

  The device 100 can transmit device monitoring information such as device counter information and alarms to the management server 101. In order to validate this device monitoring function, the device 100 acquires monitoring setting information from the management server through initial communication with the management server. The monitoring setting information is, for example, transmission information of event information such as a counter transmission cycle and an error / alarm.

  Based on the monitoring setting information, the device 100 transmits various operation mode settings, operation information such as counter values and operation logs, and failure information such as hardware failures and frequent jams to the management server.

  The management server 101 manages device status by acquiring device monitoring information from the device 100. The management server provides services for device maintenance, such as report display of billing counters, failure event notifications such as errors and alarms, calculation of device component consumption, and management of the number of toner stocks.

<Example of device configuration of this embodiment>
FIG. 2 is a cross-sectional view showing the configuration of the device 100 according to the embodiment of the present invention.

  In the figure, reference numeral 202 denotes a scanner. The scanner 202 includes a document illumination lamp 203, scanning mirrors 204 to 206, and the like.

  The automatic document feeder 250 (DF) conveys documents one by one on the platen glass 201 sequentially from the last page, and discharges the documents after the document reading operation is completed. The document conveyed on the platen glass 201 is scanned back and forth by a scanner 202 driven by a motor (not shown), and the reflected light is transmitted through the lens 207 via the scanning mirrors 204 to 206, and is stored in the image sensor unit 208. The image is formed on the CCD sensor. Reference numeral 209 denotes an exposure control unit composed of a laser, a polygon scanner, etc., which converts the laser light 219, which is converted into an electric signal by the image sensor unit 208 and modulated based on an image signal subjected to predetermined image processing, to the photosensitive drum. Irradiate 211.

  Around the photosensitive drum 211, a primary charger 212, a developing device 213, a transfer charger 216, a pre-exposure lamp 214, and a cleaning device 215 are provided. In the image forming unit 210, the photosensitive drum 211 is rotated in the direction of the arrow by a motor (not shown), and after being charged to a desired potential by the primary charger 212, the laser beam 219 from the exposure control unit 209 is obtained. And an electrostatic latent image is formed thereon. The electrostatic latent image formed on the photosensitive drum 211 is developed by the developing unit 213 and visualized as a toner image.

  On the other hand, transfer sheets fed from cassette decks 221 to 222 and upper and lower cassettes 223 to 224 by pickup rollers 225 to 228 are fed to transfer belt 234 by sheet feed rollers 229 to 232 and registration rollers 233. The toner image visualized in the process is transferred onto the transfer paper by the transfer charger 216. A multi-manual feed 251 that can accommodate 100 sheets of transfer paper is also provided.

  After the toner image is transferred, the residual toner is cleaned by the cleaner 215 from the photosensitive drum 211, and the residual charge is erased by the pre-exposure lamp 214. The transferred transfer paper is separated from the photosensitive drum 211 by the separation charger 217 and conveyed to the fixing device 235 by the transfer belt 234. In the fixing device 235, the toner image is fixed by pressurization and heating, and is discharged out of the device 100 by the discharge roller 236.

  Reference numeral 237 denotes a paper discharge flapper that switches between the transport path 238 side and the discharge path 243 side. A lower conveyance path 240 guides the transfer paper fed from the paper discharge roller 236 upside down through the reverse path 239 and into the refeed path 241. Further, the transfer paper fed from the left cassette deck 222 by the paper feed roller 230 is also guided to the refeed path 241. Reference numeral 242 denotes a refeed roller that refeeds the transfer sheet to the image forming unit 210. A discharge roller 244 is disposed in the vicinity of the paper discharge flapper 237, and discharges the transfer paper switched to the discharge path 243 side by the paper discharge flapper 237.

  During double-sided recording (double-sided copying), the paper discharge flapper 237 is raised upward, and the copied transfer paper is guided to the paper re-feeding path 241 via the transport path 238, the reverse path 239, and the lower transport path 240. At this time, the transfer paper is completely pulled out of the conveyance path 238 by the reverse roller 245 at the rear end, and is drawn into the reverse path 239 to the position where the transfer paper is bitten by the reverse roller 245, and the reverse roller 245 is reversed. It is sent out to the conveyance path 240.

  When the transfer paper is reversed and discharged from the device 100, the paper discharge flapper 237 is lifted upward, and is drawn into the reverse path 239 by the reverse roller 245 until the rear end of the transfer paper remains in the transport path 238. Further, by rotating the reverse roller 245 in the reverse direction, the transfer paper is turned over and sent to the discharge roller 244 side.

  Reference numeral 260 denotes a paper discharge processing apparatus that aligns and closes the transfer paper discharged from the device 100. In this apparatus, transfer sheets discharged one by one are stacked on the processing tray 264 and aligned. When part of the image formation is completed, the transfer sheet bundle is stapled and discharged to the discharge tray 262 or 263.

  The vertical movement of the paper discharge tray 263 is controlled by a motor (not shown). The paper discharge tray 263 moves to the position of the processing tray 264 before the image forming operation starts, and the height of the paper surface increases as the transferred transfer paper is stacked. Move to the processing tray 264 position. Reference numeral 268 denotes a tray lower limit sensor that detects the lower limit of the paper discharge tray 263, and detects this when approximately 2000 transfer sheets are stacked on the paper discharge tray 263.

  Reference numeral 261 denotes a paper tray on which separator sheets to be inserted between the discharged transfer sheets are stacked, and reference numeral 265 denotes a Z-folding machine that Z-folds the discharged transfer sheets. Reference numeral 266 denotes a bookbinding machine that performs bookbinding by collectively folding a part of the discharged transfer paper and performing stapling, and the bound paper bundle is discharged to a discharge tray 267.

  Various sensors (not shown) are arranged in various places in the cross-sectional view, and are used for toner exhaustion, document jam, transfer paper remaining amount, transfer paper jam, development-related consumable member remaining amount, document illumination lamp failure, and various other types. Detect mechanical troubles. Further, when each part is used by copying or printing, it is detected whether or not various sensors have been used, and managed as a counter such as the usage status (number of sheets and number of times) of each part. The device 100 transmits the counter information as device monitoring information to the management server based on the monitoring program.

<Configuration Example of Device Control Unit of this Embodiment>
FIG. 3 is a block diagram showing a configuration of a hardware control unit of the device in FIG.

  The control unit of the device 100 mainly performs program control processing such as printing and scanning. In addition, each application such as a device monitoring program is controlled. When transmitting the monitoring information to the management server 101, the device 100 performs processing such as generating the monitoring information of the device 100 in a predetermined communication format in the control unit.

  The control unit includes a part that performs system management and a part that performs image processing management. Each component that performs system management includes an operation unit 301, a network I / F unit 302, a line I / F unit 303, a ROM 304, a RAM 305, a storage device 306, and a CPU 307. Each component that performs image processing management includes an IO control unit 308, an image processing unit 309, an image rotation unit 310, a digital I / F unit 311, a compression / decompression unit 312, and a pixel density conversion unit 313. These components are connected to a system bus 316 and an image bus 317.

  The ROM 304 stores a device control program and a device monitoring program and is executed by the CPU 307. The RAM 305 is a work memory area for executing a program, and is also an image memory for temporarily storing device status information and image data necessary for monitoring by the device monitoring program.

  Reference numeral 306 denotes a non-volatile storage device, and various operation mode settings that need to be retained after the device 100 is restarted, counter values (such as the number of printed sheets for each size and the number of times of document reading), and status information ( Status flag and the like are stored.

  A network I / F 302 is an interface unit for connecting to a LAN, and communicates with the management server 101 via the LAN. Line I / F unit 303 is connected to an ISDN or public telephone network, controlled by a communication control program in ROM 304, and transmits / receives data to / from a remote terminal via ISDN I / F, modem, and NCU (Network Control Unit) I do. The line I / F unit 303 is also used for facsimile transmission / reception. The operation unit 301 includes display means and key input means, which are controlled by the CPU 307. The operator gives various setting instructions and operation / stop instructions regarding scanner reading and print output through the key input means.

  The above devices are arranged on the system bus 316. The IO control unit 308 is a bus bridge for connecting the system bus 316 and an image bus 317 that transfers image data at high speed. The image bus 317 is configured by a PCI bus or IEEE1394. The following devices are arranged on the image bus 317. The digital I / F unit 311 connects the reader unit 315 or the printer unit 314 of the device and the control unit, and performs synchronous / asynchronous conversion of image data. In addition, information detected by the above-described various sensors arranged at various locations in the reader unit 315 and the printer unit 314 flows to the system bus 316 via the digital I / F unit 311 and the IO control unit 308. An image processing unit 309 performs correction / processing / editing on input and output image data. The image rotation unit 310 rotates image data. The image compression / decompression unit 312 performs compression / decompression processing of JPEG for multi-valued image data and JBIG / MMR / MR / MH for binary image data. The image density conversion unit 313 performs resolution conversion and the like on the output image data.

  By the control program executed by the CPU 307, the CPU 307 reads the operation information and failure information such as the counter value and operation log in the storage device 306, and transmits them as status information of the device 100 to the management server 101 via the Network I / F 302. To do.

<Software module configuration of printing device apparatus>
FIG. 4 is a diagram illustrating the configuration of device monitoring and device UI software modules in the device 100 of FIG. Mainly, a function related to transmission of a device UI and component usage status related to this patent will be described.

  401 to 405 and 407 to 414 in the figure correspond to software modules of the device 100. Reference numeral 405 denotes an operation UI software module, and reference numeral 413 denotes a status monitoring manager software module of the device 100.

  Reference numeral 401 denotes the operation unit 301 in FIG. The user can control the device via the operation unit UI. In addition, the device status and settings can be confirmed.

  Reference numeral 405 denotes operation UI software, which inputs and outputs setting information and device status with the user via the UI. 405 is divided into modules such as an input management manager 402, a maintenance program 403, and an authentication 404. When a device setting or information acquisition request is received from the user by the input management manager, it is determined whether or not the user has an appropriate authority to access the information. The authentication 404 is a program for confirming the authority of the user. When authentication information is received from the input management manager, an authentication result is returned. For example, a user who can replace a component needs to have access authority to the user maintenance screen. The user receives password authentication when switching from the normal user mode to the user maintenance mode. The user can access information in the user maintenance mode through this authentication.

  Reference numeral 406 denotes a nonvolatile storage device such as an HDD or an SRAM. Here, device monitoring information is stored, and the wear level of consumable parts such as feeders, rollers, and drums described in FIG. 2 is stored as a part counter. Also, authentication information required when entering the privileged mode from the operation unit UI is stored. This indicates which user can access which mode.

  Reference numeral 407 denotes a device interface. This is the IO control unit 308 in FIG.

  Reference numeral 413 denotes a state monitoring manager, which is a device state monitoring program. The state monitoring manager 413 includes a timer 408, a manager 409, a logic 410, a monitoring information control 411, and a SOAP function 412.

  The state monitoring manager 413 acquires the device state at a specified time, and transmits the device monitoring information to the management server at the specified time. This specified time is managed by a timer 408, and the manager 409 is notified when the specified time comes. The manager that is notified that the specified time is reached determines whether to acquire the device status or to transmit the device monitoring information to the management server through the logic 410. When the status is acquired from the device, the acquisition time and the device status information at that time are stored in the nonvolatile storage device 406.

  When device monitoring information is transmitted to the management server, device monitoring information is acquired from the non-volatile area 406, and the device status including the component usage status detected by the printer unit 314 in FIG. Is provided to the state monitoring manager 409. The state monitoring manager 409 that has received the device status information passes the device monitoring information to the monitoring information control 411. Upon receiving the device monitoring information for transmission, the monitoring information control 411 passes the monitoring information to the SOAP function 412. The SOAP function 412 converts to a data format for transmission and issues a data transmission request to the HTTP / SOAP client 414. The HTTP / SOAP client 414 transmits device monitoring information to the management server. Although the device receives an instruction as a response from the management server, the device receives the data with the HTTP / SOAP client 414, decomposes the data with the SOAP function 412, and analyzes the instruction information with the monitoring information control 411.

<Configuration example of control unit of management server 101 of this embodiment>
FIG. 5 is a block diagram showing a hardware configuration of the management server 101 in FIG.

  The management server 101 executes an application for receiving device monitoring information transmitted from the device 100 using HTTP (S). The management apparatus 101 has a general information processing apparatus configuration. That is, in addition to the bus 401, the CPU 402, the ROM 403, and the RAM 404, a network I / F 405, a display control unit 406, a display device 409, an input control unit 407, input devices 410 and 411, and a storage device 408 are provided.

  The bus 401 is a common signal path for transferring data between components constituting the management apparatus 101 in FIG. The RAM 404 is a rewritable storage means and serves as a work memory area for executing device management software. The device management software includes a program for acquiring management data from the device 100 using SNMP. Also, the management data acquired from the device 100 is expanded here and converted into a predetermined form. The storage device 408 is a nonvolatile storage device. Here, an OS for controlling hardware is stored. In addition to this, a list of devices 100 to be managed and programs constituting management software and plug-in software are stored. In addition to this program, setting information for processing the program, for example, authentication information for issuing an SNMP request, is also stored in this nonvolatile storage device.

  A network I / F 405 is an interface for connecting to a LAN, and communicates with the device 100 via the LAN.

  The CPU 402 controls each of the component parts 403 to 411 individually or in an integrated manner, and collects management information of the device 100 via the network I / F 405 based on the program and schedule stored in the storage device 408. .

<Example of Software Configuration of Management Server 101 of this Embodiment>
FIG. 6 is a block diagram showing functions of management software installed in the management server 101. As shown in FIG. Here, a description will be given of a program process for the management software to acquire device component information, determine whether or not the component is a user replacement component, and instruct the device.

  Reference numeral 601 denotes a SOAP Web Service interface, which receives device monitoring information transmitted by the device and returns an appropriate response to the device.

  Reference numeral 602 denotes a SOAP data reception information interpretation unit. Here, the device monitoring information transmitted by the device is interpreted and the data is passed to an appropriate program. The device monitoring information includes device model information and device identification information transmitted by the device when the device is installed. In addition, when normal monitoring is started, device counter information, firmware, and other device log information are received at a specified frequency. The counter information includes a billing counter used as billing for the user, a component counter indicating the wear level of a consumable component, and the like.

  Reference numeral 603 denotes a SOAP data response information creation unit. For the device monitoring information received from the device, response information is created and passed to SOAP Web Service 601.

  Reference numeral 604 denotes a device product master information storage unit. This is a part of the storage device 508 in FIG. Stores product information for devices managed by the management server.

  Reference numeral 605 denotes a device component master information storage unit. This is a part of the storage device 508 in FIG. Stored in the device product master information storage unit 604 is consumable part information of the product. Here, information on parts that can be replaced only by service personnel, information on parts that can be replaced by users, and the like are recorded.

  Reference numeral 606 denotes a device information input / output unit. When the component information is required by the management software, appropriate device component information is acquired from the device master information storage unit 604 and the device product master information storage unit 605 based on the device product information.

  Reference numeral 607 denotes a user management information storage unit. In some customers, a single user manages multiple devices. Here, the relationship between the user and the device is held, and information for managing the user such as which part the user can replace and what kind of part has been replaced so far is recorded.

  Reference numeral 608 denotes a user information input / output unit. When a user needs to replace a new part or replace a part, information needs to be registered in the user management information storage unit 607 or read out. The user information input / output unit 608 performs this processing.

  Reference numeral 609 denotes a user type determination unit. A plurality of types of user maintenance are prepared, and the number of parts that can be replaced is defined so as to change depending on the type. The user can easily determine how much parts replacement is desired by selecting a favorite type. This type information is attribute information of the user, and it can be determined according to the type whether the service person should replace the component when the component reaches the end of its life or whether the user can request component replacement.

  Reference numeral 610 denotes a point determination unit. When a user replaces a part, points indicating user maintenance experience are given. The point is determined for each part according to the frequency and difficulty of parts replacement. Also, the criteria for application and exclusion of user maintenance target parts are used according to points.

  Reference numeral 611 denotes a user maintenance part information determination unit. Here, when device installation information is received, it is confirmed whether or not user maintenance is to be performed. If it is determined that user maintenance is to be performed, the user maintenance target component of the device is determined as response communication of the device installation information. Send to device. In addition, when the SOAP data reception information interpretation unit receives the component information from the device, it checks whether the component is consumed and decides whether to request the user to replace the component, or to request the service technician to replace the component. . If it is determined that the user should request parts replacement, a parts replacement request by user maintenance is issued in response to the parts counter reception communication.

<Example of parts master information of the management server 101 of this embodiment>
FIG. 7A is a table showing an example of device component master information stored in the management server 101. FIG. Here, a consumable parts list for each product is registered, and the lifespan and replacement frequency of consumable parts, the difficulty level for replacement, and the like are recorded in categories. Also, there are descriptions such as parts that can be replaced by user maintenance and parts that can be replaced only by service personnel. The point information is a point assigned to the user when the user exchanges it by user maintenance, and this point can be used for incentives such as price adjustment such as a maintenance fee. Parts that can only be replaced by service personnel, such as replacing parts where high voltage is generated, are recorded as N / A in the point column and are not subject to user maintenance. In addition, the definition of whether or not to be replaced is recorded for each type of user maintenance.

  FIG. 7B is a table showing a part of the user management information stored in the management server 101. Here, the definition of the user type in the user maintenance is described. For example, for users who are planning to perform user maintenance for the first time, the type “Type A” is defined for only parts that can be easily replaced, so that parts can be replaced without scrutinizing each part. However, it is possible to implement simply by selecting the type of parts replacement with simple parts.

  FIG. 7C is a table showing a part of the user management information stored in the management server 101. Here, user authentication information, information on parts replacement performed so far, point information accumulated thereby, and which type the user belongs to are registered.

<Initial communication example between the device 100 and the management server 101 of this embodiment>
FIG. 8 is a communication sequence diagram when communication with the management server is performed for the first time when the device 100 is installed in the in-house LAN of the customer. By this initial communication, initial setting of user maintenance is performed.

  Reference numeral 801 denotes initial communication from the device 100 to the management server 101, and includes product information, identification information, and user registration information when performing user maintenance.

  802 is response information from the management server 101 to the device 100. Here, the confirmation result of the product information received by the management server in the initial communication is returned. Further, when the user information received by the management server as a user performing user maintenance is a user who is not registered in the management server, confirmation of type information required for starting user maintenance is requested.

  If the user information has already been registered in the management server, the initial communication sequence is completed here.

  However, this initial communication sequence only describes the user maintenance, but other communication such as the counter communication frequency and the request for event information is performed for the initial communication when the device is installed.

  803 is a communication of a type registration request from the device 100 to the management server 101. The device 100 that has received the user maintenance type information inquiry through the communication 802 confirms the type information to the user through the operation UI (operation panel). When the user determines user maintenance type information through the operation UI, the determination information is transmitted to the management server 101.

  Reference numeral 804 denotes a type registration completion communication from the management server 101 to the device 100. When the user maintenance type registration is completed without any problem through the communication 803, a response 804 indicating the completion of registration is transmitted from the management server 101 to the device 100.

<Example 1 in the device component state of this embodiment>
Based on the above configuration, an operation example of the management software when a certain component usage state of the device in this embodiment is reached will be described.

  FIG. 9 (a) shows a part usage situation of a device that has started operation. The device transmits various counters to the management server based on the counter transmission schedule.

  When receiving the component counter shown in FIG. 9A, the management server detects that component B has already reached the end of its life.

  When the management server detects a component that has reached the end of its life, it prepares to issue a component replacement request. First, it is confirmed that the device is a user maintenance target device from the device component master information in FIG. 7A, and further, the user who manages the device is specified from the device identification information.

  FIG. 9B shows user maintenance attribute information of a user who manages the device. From here, the management server confirms that the user type is “type A” from the user attribute information.

  When the management server confirms that component B is replaceable by the user, the management server notifies the response information of the component counter that the time for replacement of component B has come.

<Example 2 in the device component state of this embodiment>
An operation example of the management software when a certain component usage state of the device in this embodiment is reached will be described. However, here, a description will be given of a mechanism for notifying a part to be replaced by a service person as a part subject to user maintenance depending on conditions at that time.

  FIG. 10 (a) shows a part usage situation of a device that has started operation. The device transmits various counters to the management server based on the counter transmission schedule.

  When receiving the component counter shown in FIG. 10 (a), the management server detects that component A has already reached the end of its life.

  When the management server detects a component that has reached the end of its life, it prepares to issue a component replacement request. First, it is confirmed that the device is a user maintenance target device from the device component master information in FIG. 7A, and further, the user who manages the device is specified from the device identification information.

  FIG. 10B shows user maintenance attribute information of a user who manages the device. From here, the management server confirms from the user attribute information that the user type is “type A” and that the point has reached 3000 points.

  The management server can confirm that the part A is not a replacement target part for the user of type A, but the user's points have been accumulated and have reached the specified point (10 times) or more that is assigned when the part A is replaced. It is confirmed at the same time.

  Then, the management server determines that the component A can be replaced by the user, and notifies the response information of the component counter that the replacement time for the component A has come.

<Example 3 in the device component state of this embodiment>
An operation example of the management software when a certain component usage state of the device in this embodiment is reached will be described. However, here, a description will be given of a mechanism in which a serviceman replaces a part even if it is a part subject to user maintenance when the part to be replaced by the serviceman and the part to be replaced by the user are approaching the end of their lives at the same time.

  FIG. 11 (a) shows a component usage situation of a device that has started operation. The device transmits various counters to the management server based on the counter transmission schedule.

  When the management server receives the component counter shown in FIG. 11 (a), it detects that component B has already reached the end of life, and that component E will soon reach the end of its life.

  When the management server detects a component that has reached the end of its life, it prepares to issue a component replacement request. First, it is confirmed from the device part master information of FIG. 7 (a) that the part A is a user maintenance target device and that the part E is a replacement target part of a service person.

  Then, the management server knows that the service person always goes to the part replacement for the part replacement. Therefore, instead of requesting the user to replace the part, the management server requests the service person to replace the part.

<Operation example of management software of this embodiment>
Based on the above configuration, an example of the operation of the management software of this embodiment will be described.

  FIG. 12 is a flowchart showing processing when the management software of the management server receives component counter information from the device. The processing of this flowchart is stored in either the storage unit of the ROM 503 or the storage device 508 shown in FIG. 5, expanded in the RAM 504 as necessary, and executed by the CPU 502. The processing of the flowchart shown here shows the processing of the management software shown in FIG.

  In FIG. 12, when the SOAP Web Service 601 of the management server receives the component information, the processing shown in the flowchart is started.

  In step S1201, the SOAP data reception information interpretation unit 602 of the management software confirms whether component information has been received. If the component information has not been received, the process returns to step S1201 and starts by checking whether the component information has been received. If the component information has been acquired, the process proceeds to step S1202.

  In step S1202, the user maintenance part information determination unit 611 confirms whether there is a part whose wear level of the part to be replaced is 90% or more. If there is no component with a consumption level of 90% or more in the received component information, the process returns to step S1201 and starts by checking whether or not a device registration request has been received for the component information. If the received component information includes a component with a wear level of 90% or more, the process proceeds to step S1203.

  In step S1203, the user maintenance part information determination unit 611 confirms whether there is a replacement part dedicated to the service person among the parts having a wear level of 90% or more. If there is no replacement part dedicated to the service person among the parts having a wear level of 90% or more, the process proceeds to step S1207. If there is a replacement part dedicated to the service person among the parts having a wear level of 90% or more, the process proceeds to step S1204.

  In step S1204, the user maintenance part information determination unit 611 confirms whether there is a part to be replaced by the user among the parts having a wear level of 90% or more. If there is a part to be replaced by the user among the parts having a wear level of 90% or more, the process proceeds to step S1206. If there is no user-replaceable part among the parts having a wear level of 90% or more, the process proceeds to step S1205.

  In step S1205, the user maintenance part information determination unit 611 issues a part replacement request to the service person based on the part information whose degree of wear has reached 90% or more. Then, as a response to the received component information, only the fact that the component information has been normally received is responded to the device, and the process ends.

  In step S1206, the user maintenance part information determination unit 611 issues a part replacement request to the service person for all parts information whose wear level has reached 90% or more. At this time, as a response to the received component information, only the fact that the component information has been normally received is responded to the device, and the process is terminated.

  The processing in step S1206 is the processing flow of the third embodiment in the device component state.

  In step S1207, the user maintenance part information determination unit 611 determines whether or not a part whose wear level has reached 90% or more is a part to be replaced in the user who manages the device. If the component whose wear level has reached 90% or more is a replacement target component for the user who manages the device, the process proceeds to step S1208. If the part whose wear level has reached 90% or more is not the part to be replaced by the user who manages the device, the process proceeds to step S1211.

  In step S1208, user maintenance part information determination unit 611 checks whether or not the degree of wear of the replacement target part has reached 100% or more. If the wear level of the replacement target part has reached 100% or more, the process proceeds to step S1209. If the wear level has not reached 100%, the process proceeds to step S1210.

  In step S1209, since the user replacement conditions are satisfied, the user maintenance part information determination unit 611 transmits a part replacement request by user maintenance to the response of the part information notification and ends the process.

  The processing in step S1209 is the processing flow of the first embodiment in the device component state.

  In step S1210, as a response to the received component information notification, user maintenance component information determination unit 611 responds to the device only that component information has been normally received by the device, and ends the process.

  In step S1211, the user maintenance part information determination unit 611 confirms whether or not the point of the replacement target part is smaller than the prescribed value (10%) of the accumulated points of the user. If the point of the replacement target part is smaller than the specified value (10%) of the accumulated point of the user, the process proceeds to step S1212. If the point of the replacement target part is larger than the specified value (10%) of the accumulated points of the user, the process proceeds to step S1215.

  In step S1212, the user maintenance part information determination unit 611 issues an inquiry as a response to the reception of part information to inquire whether or not to replace parts exceeding the range determined by the type set by the user, and the process proceeds to step S1213. Proceed.

  In step S1213, the user maintenance part information determination unit 611 confirms whether a notification that the type change has been accepted has been received from the user or a rejection notification (part replacement request) has been received. If a notification that the type change has been accepted is received from the user, the process proceeds to step S1214. If a rejection notification is received from the user, the process proceeds to step S1215.

  In step S1214, user type determination unit 609 changes the user type, notifies the user of the replacement part shipment, and ends the process.

  The processing in step S1214 is a processing flow of the second embodiment in the device component state.

  In step S1215, the user maintenance parts information determination unit 611 issues a parts replacement request to the service person, and responds to the user only that the information has been normally received, and ends the process.

<Operation example of device of this embodiment>
Based on the above configuration, an operation example of the device of the present embodiment will be described.

  FIG. 13 is a flowchart showing processing when the device transmits component counter information to the management server. The processing of this flowchart is stored in either the storage means of the ROM 303 or the storage device 506 shown in FIG. The processing of the flowchart shown here shows the processing of the functional block diagram shown in FIG.

  In FIG. 13, when the device transmits component information to the management server, the processing shown in the flowchart is started.

  When the SOAP function 412 of the device transmits the component information in step S1301, the process proceeds to step S1302.

  In step S1302, the SOAP function 412 receives a response to the component information transmission. In the response information, it is confirmed whether or not there is a parts replacement instruction by user maintenance. If there is a part replacement instruction, the manager 409 records the part replacement instruction in the HDD / SRAM device part information 406 and advances the process to step S1303. If there is no part replacement instruction, the process returns to step S1301.

  In step S1303, when the maintenance program 403 detects that a component replacement instruction is described in the HDD / SRAM device component information 406, the maintenance program 403 notifies the operation UI (operation panel) that there is a component that needs replacement. The process proceeds to step S1304.

  In step S1304, the input management manager 402 confirms whether the user has been notified and logged into the user maintenance mode. If logged in, the process advances to step S1305. If the login cannot be confirmed, it is confirmed again in step S1304 whether or not the user has logged in to the user maintenance mode.

  In step S1305, the input management manager 402 represents a part that needs to be replaced on the user maintenance mode screen on the operation UI (operation panel), and proceeds to step S1306.

  In step S1306, the input management manager 402 confirms whether or not the user has selected a replacement part from the operation UI and started part replacement. When component replacement is started, the process proceeds to step S1307. If the user refuses to replace the part, the process proceeds to step S1311.

  In step S1307, the input management manager 402 confirms whether or not the user selects a replacement part from the operation UI and completes the part replacement. When the parts replacement is completed, the process proceeds to step S1308. If the user cannot complete the part replacement, the process proceeds to step S1311.

  In step S1308, the input management manager 402 confirms whether or not the part has been normally replaced when a condition such as a print process using the replacement part is satisfied after the constant part replacement condition. Run. After this confirmation process, the process proceeds to step S1309.

  In step S1309, the result of the device normality confirmation process is confirmed. If it is determined that the device is normal, the process ends here. If any abnormality is detected in the device, the process proceeds to step S1310.

  In step S1310, the device issues a service call error, requests a service man, and ends the process.

  In step S1311, the input management manager 402 confirms whether or not the user has pressed the “part replacement request” button from the operation UI to request a service person for part replacement. If a parts replacement request has been made to the service person, the process proceeds to step S1312. If no parts replacement request is made, a parts list is displayed in step S1306.

  In step S1312, the SOAP function 412 issues a parts replacement request and ends the process.

<Example of device operation UI of this embodiment>
FIG. 14 (a) is an example of an operation UI for notifying the user that there is a replacement part using the device operation UI. Here, a part for displaying the device status information is provided at the bottom of the screen, and when the necessity of parts replacement occurs, the user is notified from the status information field that the parts need to be replaced. When the user confirms the status display, the screen transitions to the user maintenance screen, and the parts that need to be replaced can be confirmed.

  FIG. 14 (b) is an example of an operation UI that allows the user to confirm whether or not to perform component replacement on the device operation UI. When the user logs in to the user maintenance mode, a list of replacement target parts is displayed. When one part is selected from the list, it is possible to select whether to start part replacement or to request a service person together with the detailed information of the part. When the user replaces a part by user maintenance, the user presses a “replacement” button and declares that the part is to be replaced. Further, when requesting replacement of parts from the service person, the user can request replacement of parts by encouraging the “Replacement Request” button.

  In addition, even if the user cannot replace the parts after starting the parts replacement by the user maintenance, the “Replacement request” button can be pressed at any time in order to allow the service person to request the parts replacement. Display as follows.

100 devices
101 Management server
102 Internal LAN
103 Internet
413 Status monitoring manager

Claims (6)

It is a device management system that consists of a management server that manages multiple devices via a network, and a device that is connected to the network and used, and that requires replacement of parts as the parts reach the end of their service life.
The device
User information for parts replacement, device product information, and a first transmission function (414) for transmitting device identification information to the management server,
A second transmission function (414) for transmitting the usage status of the device to the management server;
A reception function (414) for receiving a replacement instruction for replacement parts;
Input / output function (operation panel) (401) for displaying information to the user and receiving input,
A component replacement notification function (401) that prompts the user to replace a component via the input / output function when a component replacement instruction is received via the reception function;
The management server comprises
User information for exchanging parts from the device, device product information, a first receiving function (601) for receiving device identification information,
A second receiving function (601) for receiving the usage status of the device from the device;
Maintenance information storage function (606/608) that stores user information received by the first reception function, device product information, and device identification information in a storage area;
A determination function (611) for determining whether to request replacement by a user or a replacement by a service person according to the usage status of the device received by the second reception function;
A component replacement instruction function (601) that issues a component replacement instruction to the device when it is determined by the determination function that the user should request replacement, and
A device management system comprising: 2. The device management system according to claim 1, wherein the user information for performing component replacement is information representing user identification information and a type of replacement component. The part replacement instruction function of the management server is based on the part replacement instruction from the management server, and detects the user's part replacement. 2. The device management system according to claim 1, further comprising a point function for attaching point information to be added. The point function of the management server increases the point information of the user who determines the type of replacement part, and has a part replacement type health function that prompts the user to change the type of replacement part when it reaches a specified value or more. The device management system according to claim 1 or 2. 2. The device management system according to claim 1, wherein the usage state of the device is a degree of wear of replacement parts. The user has a parts replacement request function for requesting parts replacement to the service person via the input / output function when the parts start replacement by the parts replacement instruction from the management server but the parts replacement cannot be completed. 2. The device management system according to claim 1, wherein