Asset management system for network-based and non-network-based assets and information

• US 20030093521A1
• Filed: 11/04/2002
• Published: 05/15/2003
• Est. Priority Date: 11/09/2001
• Status: Active Grant

• Current Assignee: Paradise IP LLC (IP Edge LLC)
• Original Assignee: Xerox Corporation (Xerox Holdings Corp.)
• Inventors: Scrafford, Matthew, Schlonski, Steven T., Mallery, Craig H., Silver, Thomas A., Pothos, Kirk V., Hawes, M. Kerrigan
• Granted Patent: US 7,200,613 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A server on a network controls a database which functions as an “asset manager” for a large population of items or assets. For “network” assets which are capable of electronically communicating data about themselves, such as computers and digital printers, relevant data is gathered over the network and entered into the database. For “non-network” assets which are not capable of electronic communication, such as typewriters and furniture, information is gathered into the database by other means. Within the database, the distinction between network and non-network assets is largely hidden.

Claims

1. A method of retaining data about a plurality of assets, the assets including network assets and non-network assets, the data including network data and non-network data, the network data being obtainable over a network, comprising:

for each asset, associating a file with the asset, the file including spaces for holding data, each space being associated with a type of data;

for a network asset, populating a space associated with a first type of data in the associated file with the network data;

for a non-network asset, populating the space associated with the first type of data in the associated file with non-network data.

2. The method of claim 1, wherein the network asset has a network address associated therewith.

3. The method of claim 1, wherein at least one network asset is at least one of a group comprising a digital printer, copier, and facsimile machine.

4. The method of claim 1, wherein at least one type of network data relates to a count of prints output from the asset.

5. The method of claim 1, wherein at least one asset outputs prints and does not have a network address associated therewith;

and

wherein the first type of data relates to a count of prints output from the asset.

6. The method of claim 1, further comprising

for at least one type of data retained in a file, retaining a history of values of the data in the file.

7. The method of claim 1, wherein a type of data relates to a physical location of the asset.

8. The method of claim 1, wherein a type of data relates to a history of physical locations of the asset.

9. The method of claim 1, wherein a type of data relates to an identity of a vendor of the asset.

10. The method of claim 1, wherein a type of data relates to a warranty associated with the asset.

11. The method of claim 1, wherein a type of data relates to an identity of a manager of the asset.

12. The method of claim 1, wherein a type of data relates to a fault experienced by the asset.

13. The method of claim 1, wherein a type of data relates to a history of faults experienced by the asset.

14. The method of claim 1, further comprising translating a fault code generated by a network asset.

15. The method of claim 1, further comprising

discovering a network asset;

as a result of discovering the asset, creating a file and populating at least one space in the file with network data relating to the asset.

16. The method of claim 1, further comprising

for each file associated with a subset of assets including at least one network asset and at least one non-network asset, updating data in one predetermined space for each file.

17. The method of claim 1, further comprising

displaying a template whereby the data for the predetermined space in each file is updated in substantially one operation.

18. A method of managing a set of assets interconnected over a network, comprising:

for a first subset of assets, polling each asset for a first type of data at a first predetermined frequency; and

for a second subset of assets, polling each asset for the first type of data at a second predetermined frequency.

19. The method of claim 18, wherein the first type of data relates to a possible malfunction of the asset.

20. The method of claim 18, wherein the first type of data relates to the asset being out of a material required for outputting prints.

21. The method of claim 18, the assets including network assets and non-network assets, the data including network data and non-network data, the network data being obtainable over a network.

22. A method of managing a plurality of assets, each asset being associated with a file, each file including a plurality of spaces for retaining data of predetermined types, a first type of data being an identifier of the asset, comprising:

for a first subset of the plurality of assets, assigning a first appendage to each identifier;

whereby an identifier for an asset in the first subset can be identical to an identifier for an asset not in the first subset, except for the appendage.

23. The method of claim 22, further comprising

for a user accessing data relating to the first subset of the plurality of assets, causing the first appendage to be substantially unapparent.

24. The method of claim 22, further comprising

for a second subset of the plurality of assets, assigning a second appendage to each identifier.