Inventory management database

• US 20030023516A1
• Filed: 05/17/2001
• Published: 01/30/2003
• Est. Priority Date: 05/17/2001
• Status: Abandoned Application

• Current Assignee: the united states of america as represented by the secretary of the navy
• Original Assignee: the united states of america as represented by the secretary of the navy
• Inventors: Sharrow, Sherry L., Krainski, William J.
• Application Number:
  US09/860,115
• Publication Number:
  US 20030023516A1
• Time in Patent Office: Days
• US Class Current: 705/28
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

An inventory management database is disclosed. The database can include container objects, hardware component objects, and software component objects. Container objects correspond to equipment on which other equipment can be installed. Hardware component objects correspond to hardware components that are installable on the equipment to which the container objects correspond. When a hardware component is installed on the equipment to which a container object corresponds, the corresponding hardware component object is assigned to this container object. Software component objects correspond to software components that are also installable on the equipment to which the container objects correspond. When a software component is installed on the equipment to which a container object corresponds, the corresponding software component object is assigned to this container object.

Claims

1. A database for managing equipment comprising:

one or more container objects, each container object corresponding to an equipment on which other equipment can be installed;

one or more hardware component objects, each hardware component object corresponding to a hardware component that is installable on the equipment corresponding to a container object such that the hardware component object is assignable to the container object.

2. The database of claim 1, further comprising one or more software component objects, each software component object corresponding to a software component that is installable on the equipment corresponding to a container object such that the software component object is assignable to the container object.

3. The database of claim 2, wherein each software component object is assigned to a container object when the software component to which the software component object corresponds is installed on the equipment to which the container object corresponds.

4. The database of claim 2, wherein the software component to which each software component object corresponds is selected from the group of software components essentially consisting of software programs, hot fix update programs, and service pack update programs.

5. The database of claim 1, wherein the equipment to which each container object corresponds is selected from the group of equipment essentially consisting of a system, a mass storage device, a printer, and a print server.

6. The database of claim 1, wherein each hardware component object is assigned to a container object when the hardware component to which the hardware component object corresponds is installed on the equipment to which the container object corresponds.

7. The database of claim 1, wherein the hardware component to which each hardware component object corresponds is selected from the group of hardware components essentially consisting of displays, docking stations, general office equipment, imaging equipment, input devices, interface drives, logic analyzers, memory, modems, network devices, removable hard drive cases, scanners, storage devices, terminals, test tools, uninterruptible power supplies, workstations, and zip drives.

8. The database of claim 1, wherein the hardware component to which each hardware component object corresponds is selected from the group of hardware components essentially consisting of network cards, network hubs, network modules, network sub-modules, and network print servers.

9. The database of claim 1, wherein the hardware component to which each hardware component object corresponds is selected from the group of hardware components essentially consisting of mass storage devices, phones, printers, and print servers.

10. The database of claim 1, farther comprising one or more hybrid objects, each hybrid object corresponding to equipment that is both installable on other equipment and on which other equipment can be installed.

11. The database of claim 1, wherein the database is relational.

12. A method for managing equipment comprising:

instantiating one or more container objects from one or more different container object types, each container object corresponding to an equipment on which other equipment can be installed; and

,

instantiating one or more hardware component objects from one or more different hardware component object types, each hardware component object corresponding to a hardware component that is installable on the equipment corresponding to a container object such that the hardware component object is assignable to the container object.

13. The method of claim 12, further comprising instantiating one or more software component objects from one or more different software component object types, each software component object corresponding to a software component that is installable on the equipment corresponding to a container object such that the software component object is assignable to the container object.

14. The method of claim 13, further comprising creating, modifying, and deleting the one or more different software component object types.

15. The method of claim 13, further comprising assigning each software component to a container object when the software component to which the software component object corresponds is installed on the equipment to which the container object corresponds.

16. The method of claim 12, further comprising creating, modifying, and deleting the one or more different container object types.

17. The method of claim 12, further comprising creating, modifying, and deleting the one or more different hardware component object types.

18. The method of claim 12, further comprising assigning each hardware component object to a container object when the hardware component to which the hardware component object corresponds is installed on the equipment to which the container object corresponds.

19. A computer-readable medium having instructions stored thereon for execution by a processor to perform the method of claim 12.

20. A database for managing equipment comprising:

container object means for corresponding to an equipment on which other equipment can be installed;

hardware component object means for corresponding to a hardware component that is installable on the equipment corresponding to the container object means such that the hardware component object means is assignable to the container object means; and

,

software component object means for corresponding to a software component that is installable on the equipment corresponding to the container object such that the software component object means is assignable to the container object means.