Patent Application
20100272450
Embodiments are generally related to devices such as rendering devices, finishing devices, feeding devices, and the like. Embodiments also relate in general to the field of computers and similar technologies and, in particular, to software utilized in this field. In addition, embodiments relate to HFSI (High Frequency Service Item) and CRU (Customer Replaceable Unit) components associated with complex systems.
Rendering devices such as printers, for example, often include components that wear with usage and eventually may require replacement. For example, laser printers typically include internal rollers for transporting print media, an electro-photographic drum for transferring toner to the print media, and a fuser for fusing toner to the print media. Such components wear with usage and may need to be replaced, sometimes more than once, during the life of the rendering device. An HFSI is an integral component that can be replaced at the end of life or at the time of premature failure of one or more components. HFSI components enable a variety of machine subsystems to be incorporated into a single unit while maximizing the useful life of each component.
A typical HFSI can be configured from multiple components, each component having an independent HFSI counter. A number of such counters may be each associated with a particular replaceable component so that the HFSI counters can be reset independently. Such counters can be utilized for scheduling replacement of the individual component when the counter associated with the component attains a predetermined threshold value, or when directed to in concert with service documentation. The HFSI needs to be replaced completely when any of the components of the HFSI reach a count indicating the need for replacement.
One of the problems associated with such prior art approaches is that a conservative estimate of life needs to be provided so that the component does not fail before the scheduled replacement date, which means that a certain measure of useful life is being wasted. Such an approach can lead to the failure of certain components being changed when the related components are changed, thereby resulting in extra service calls or poor performance. Additionally, customers and service personnel may find it necessary to scroll through a large component list in order to find related components.
Based on the foregoing, it is believed that a need exists for an improved method and system for managing service intervals for related components associated with a particular device such as, for example, a rendering device. A need also exists for defining a parent/child relationship between high frequency service items.
The following summary is provided to facilitate an understanding of some of the innovative features unique to the present invention and is not intended to be a full description. A full appreciation of the various aspects of the embodiments disclosed herein can be gained by taking the entire specification, claims, drawings, and abstract as a whole.
It is, therefore, one aspect of the present invention to provide for an improved rendering device such as a printer, and/or other related devices such as a finishing device or a feeding device.
It is another aspect of the present invention to provide for an improved method and system for managing service intervals for related components associated with a device to maximize utilization of components and reliability of the device.
It is a further aspect of the present invention to provide for an improved method for defining a parent/child relationship between high frequency service items.
The aforementioned aspects and other objectives and advantages can now be achieved as described herein. A method and system for managing one or more high frequency service items associated with a device (e.g., rendering device, finishing device, feeding device, etc) is disclosed herein. A parent/child relationship between the high frequency service items can be defined to track replacement of components based on a service action related to a child component. A taxonomy of related service items and servicing functions can be specified in an XML document associated with the rendering system. The relationship between the high frequency service items can be indicated utilizing a related component indicator and a HFSI counter. A parent component can be replaced by a maintenance operator and individual child components can be replaced or repaired by a service engineer in order to retain the component life of those children whose component life counters indicate that they are not yet ready to be replaced thereby reducing down time and service costs.
The high frequency service items are an integral component that requires the service action (e.g., cleaning, repairing, rebuilding, replacing, calibration, and so forth) to be performed at the end of life or at a time of premature failure of one or more components. The high frequency service items are highly related to other service items associated with the device. The service items can be replaced after a certain count of instances the HFSI counter associated with the child component is reset (each time the child component is serviced). The XML based file can be updated via a remote service provider in order to change a service relationship between the high frequency service items.
The parent component can be named initially. If the child component reaches a predetermined threshold, an indicator for replacing the parent component can be automatically displayed. The child component associated with the parent component can be rebuilt by the service engineer and a new name can be created to retain the life of the parent component. A service count associated with the child component can be configured to follow a count associated with the parent component on replacement of the parent component into the device.
The complex list of components can be displayed in a hierarchical structure utilizing the related component indicator and stored in a HFSI memory. The relationship between the parent component and the child component can be configured such that the entire child components need to be replaced at a service call. Such an approach provides a separation of replacing an aggregate component from rebuilding an aggregate component. The parent/child relationship can be utilized to coordinate part replacement between the components in order to maximize both the utilization of parts and the reliability of the device.
The accompanying figures, in which like reference numerals refer to identical or functionally-similar elements throughout the separate views and which are incorporated in and form a part of the specification, further illustrate the present invention and, together with the detailed description of the invention, serve to explain the principles of the present invention.
The particular values and configurations discussed in these non-limiting examples can be varied and are cited merely to illustrate at least one embodiment and are not intended to limit the scope of such embodiments.
As depicted in
The interface 153, which is preferably a graphical user interface (GUI), also serves to display results, whereupon the user may supply additional inputs or terminate a given session. In one possible embodiment, operating system 151 and interface 153 can be implemented in the context of a “Windows” system. It can be appreciated, of course, that other types of systems are possible. For example, rather than a traditional “Windows” system, other operation systems such as, for example, Linux may also be employed with respect to operating system 151 and interface 153. Application module 152, on the other hand, can include instructions such as the various operations described herein with respect to the various components and modules described herein such as, for example, the method 500 depicted in
In the depicted example, server 304 and server 306 connect to network 302 along with storage unit 308. In addition, clients 310, 312, and 314 connect to network 302. These clients 310, 312, and 314 may be, for example, personal computers or network computers. Data-processing apparatus 100 depicted in
In the depicted example, server 304 provides data such as boot files, operating system images, and applications to clients 310, 312, and 314. Clients 310, 312, and 314 are clients to server 304 in this example. Network data processing system 300 may include additional servers, clients, and other devices not shown. Specifically, clients may connect to any member of a network of servers which provide equivalent content.
In the depicted example, network data processing system 300 is the Internet with network 302 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, government, educational, and other computer systems that route data and messages. Of course, network data processing system 300 also may be implemented as a number of different types of networks such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).
The following description is presented with respect to embodiments of the present invention, which can be embodied in the context of a data-processing system such as data-processing apparatus 100 and computer software system 150 depicted respectively
In general, high frequency service items can be defined as an integral component to modern rendering devices such as rendering device 108 to help a service personnel know when to replace components associated with the rendering device 108. The more complex products can possess several hundred high frequency service items and the components are mechanically and electrically related to each other. The service items 410 associated with the rendering device 108 can be defined utilizing a parent/child relationship. The parent components 415 and 420 can be made up of multiple parts (the children), each part having a HFSI counter 430 and 435 respectively. The service items 410 include a number of such counters 430 and 435 each associated with a particular replaceable element so that they can be reset independently.
The service items 410 further include a memory device 440 and a HFSI monitor 420 integral therewith. The service items 410 may include multiple memories of different types such as, for example, ROM, RAM, EEPROM, magnetic, or optical. Data relating to the service items 410 may be stored in the memory device 440. For example, a preset number of total images for the service items 410, various threshold(s) values associated with the service items 410, and various predetermined information can be stored in the memory device 440. The high frequency service items 410 require a service action to be performed at the end of life or at the time of premature failure of one or more components. The service action includes operations such as, for example, cleaning, calibration, rebuilding, repairing and replacing. The HFSI are highly related to other service items associated with the rendering device 108.
The service items 410 may represent any component in the rendering device 108 that is subject to wear over the life of the rendering device 108. For example, the component rendering device 108 may comprise high frequency service items such as, for example, a photoreceptor cartridge, a developer cartridge, a toner cartridge, an ink cartridge, print head, and print cartridge each of which is generally designed to function for a preset number of images in the form of prints or copies. These components are described for purposes of clarity and specificity; however, they should not be interpreted in any limiting way.
The parent/child relationship between the service items 410 can be defined in order to provide the user with the ability to manage “partial-life” components. An XML based system 445 can be utilized to configure the parent/child relationship between the service items 410 associated with the rendering device 108. The XML based system 445 can be updated via a remote service provider 450 in order to change the service relationship between the service items 410, if needed. The parent components 415 and 420 can be marked for replacement when the child components associated with the parent components 415 and 420 reaches a due state. The relationship between the parent and the child components 415 and 420 can be configured such that the entire child components need to be replaced at the service call. The parent/child relationships can provide the user with the ability to track the replacement of components 415 and 420 based on the service actions of the child components. The service items 410 can be replaced after a certain count of instances the child component is reset (each time the child component is serviced). For example, in some situations the wire assembly can be replaced every third time the wires are cleaned. The counter associated with the wire assembly represents the number of times the child component is reset (each time the wire is cleaned). A service count associated with the child component can be configured to follow a count associated with the parent components 415 and 420 on replacement of the parent components 415 and 420 into the rendering device 108.
The rendering device 108 further includes a related component indicator 425 that provides the service items 410 to reflect a relationship with each other. The parent components 415 and 420 end of life threshold is a function of its related child component and the HFSI counter 430 and 435. For example, a wire assembly is determined to have passed the threshold when the related component associated with the wire assembly is reset three times. Customers that may forget to clean the wires can get a warning when the wire assembly has reached the end of life. The related component indicator 425 displays a complex list of components on a hierarchical structure, in the HFSI monitor 420. Note that the embodiments discussed herein generally relate to a rendering device. It can be appreciated, however, that such embodiments can be implemented in the context of other systems and devices and are not limited to the rendering device. The discussion of rendering devices, as utilized herein, is presented for general illustrative purposes only.
Programs defining functions on the present invention can be delivered to a data storage system or a computer system via a variety of signal-bearing media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., hard disk drive, read/write CD ROM, optical media), system memory such as, but not limited to, Random Access Memory (RAM), and communication media such as computer and telephone networks including Ethernet, the Internet, wireless networks, and like network systems. It should be understood, therefore, that such signal-bearing media when carrying or encoding computer readable instructions that direct method functions in the present invention, represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by a system having means in the form of hardware, software, or a combination of software and hardware as described herein or their equivalent. Thus, the method 500 described herein can be deployed as process software in the context of a computer system or data-processing system as that depicted in
The parent/child relationship between high frequency service items 410 associated with the rendering device 108 can be configured utilizing the XML enabled system 445, as depicted at block 510. For example, the parent/child relationship can be defined in terms of the HFSI Id (e.g. <HFSI id=“5” parent=“10” name=“Parent”/><HFSI id=“10” name=“Child”>). The XML enabled system 445 can be updated via remote service providers 450 in order to change the service relationship between the service items 410 if data from the field indicates for a more optimum replacement strategy. A name for the parent components 415 and 420 can be created, as shown at block 520. The end of life threshold for the parent components 415 and 420 can be set, as illustrated at block 530.
Thereafter, the status of the components (children) with respect to the threshold value can be monitored in the HFSI monitor 420, as shown at block 540. A determination can be made if the threshold has been reached, as depicted at block 550. If the threshold condition is reached, the parent component indicator 425 can be automatically displayed for replacement, as illustrated at block 560. Such an approach allows the parent components 415 and 420 to be marked for replacement if any of its children need replacing. The parent components 415 and 420 can be replaced by the customer maintenance operator, as shown at block 570. The child component associated with parent components 415 and 420 can be rebuilt by the customer service engineer (CSE), as illustrated at block 580.
A new name can be created for the parent components 415 and 420 when replaced in order to retain- the component life associated with the parent components 415 and 420, as depicted at block 590. The new name can be created, or selected from the set of previously known names, upon replacement of the parent components 415 and 420. Such an approach provides aggregate components that are “rebuilt” by the CSE to retain some component life when replaced. Note that the access to the children component can be restricted to the CSE, but aggregate components can be replaceable by the customer maintenance operators. Note that a parent component can be replaced by a maintenance operator and individual child components can be replaced or repaired by a service engineer in order to retain the component life of those children whose component life counters indicate that they are not yet ready to be replaced thereby reducing down time and service costs. This approach can provide a separation of the concept of replacing an aggregate component from rebuilding an aggregate component. The CSE can “reset” individual HFSI 410 of named aggregates that are not currently in the device 108 when the CSE is rebuilding an aggregate component that is outside the rendering device 108. The residual component life is accurate when the component is ultimately placed back in service.
For example, the fuser module (the parent) associated with the rendering device 108 includes sub parts (the children) such as, for example, stripper fingers, fuser roll, fuser thermistors, fuser drawer connector, and fuser heat lamp. The fuser assembly may be customer replaceable, but the individual components associated with the fuser assembly are not replaceable. The customer can replace the fuser assembly and put it on the “shelf” and the CSE can replace individual components as needed. The “rebuilt” fuser assembly can be put back in the system when the customer replaces the current one. The “rebuilt” fuser assembly can be named and can “inherit” the component life for any component not replaced.
Note that the service counts associated with the parent and each of the children are associated with a “name” for an assembly thereof. This assembly can be replaced with another assembly of a different name. The other assembly, when replaced, can have its service counts restored to what they were when they were removed from the machine. This can be achieved either through storing the service counts in a crum-like tag (RFID Tag) on the assembly, or by having the device remember the name and associated counts, and when the user selects the “replace” option, they can pick a previously existing name or create a new one. This allows the operator to have two assemblies at the customer sight. When the parent needs to be replaced, they can pull the whole assembly, pop in a new one, and get the customer back up. The assembly with the child HFSI that needs replacing can be repaired or replaced and then placed “in the cabinet” for use at a future time.
While the present invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Furthermore, as used in the specification and the appended claims, the term “computer” or “system” or “computer system” or “computing device” includes any data processing system including, but not limited to, personal computers, servers, workstations, network computers, main frame computers, routers, switches, Personal Digital Assistants (PDA's), telephones, and any other system capable of processing, transmitting, receiving, capturing and/or storing data.
It is believed that by utilizing the parent/child relationship described herein, part replacement between components can be coordinated in such a manner as to maximize both the utilization of parts and the reliability of the system. The aggregate part replacement can be treated different from the component part replacement in order to allow different users and service actions to be performed, thereby reducing down time and service costs.
It will be appreciated that variations of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also, that various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.
