I am sure you had to
keep inventory lists, even when you didn't realize it! I have on many occasions
and that is why this application exists today.
But did you ever stop to think that there always seems to be a relationship
or hierarchy for almost any type of inventory. And to even stretch the idea a
little further, did you ever think of people as being inventory items?
Once you start thinking of inventory having "ownership" everything seems to
fit into a neat list format. Even people.
For example, it can be said that a company "owns" a building. Multiple
floors, offices, storage areas etc. By the same token, you could also say an
employee "owns" their work area. Their cubicle or office, their desk, phone,
data & voice jacks, etc. In reality, it is most likely the bank that really
"owns" the building and the employee work areas. But, the company and the
employee have "owner" responsibilities.
Having said all that, maybe you can think of some lists you made up not
realizing it really had an ownership flavor. For instances, did you ever make an
inventory of your house contents for insurance purposes? You automatically start
thinking about each room separately, kitchen, living room, etc., even though
your list may not end up the way you think, but why not? Wouldn't be nice if
inventory lists could be simple and reflect they way you "think" about things?
THIS is a "Totally Heuristic Inventory System" that lists things in the way
you might think about them, showing ownership relationships in a simple format.
For a house, you have a
kitchen and in the kitchen there is a refrigerator, stove etc. You may already
have this information tucked away in a box somewhere. Now go to THIS and open up
the HOMESAMPLE.THIS file to see an example of how THIS would list the inventory
found in a typical house. Note that makes, models and serial numbers can easily
be added to each item listed.
For a company, there are managers and then managers and then managers.
Eventually you get down to worker bees. But no matter what level you are in an
organization, you usually end up with a working area and "stuff" that you use.
(as in "own", so to speak) So Henry, a programmer, has a cubicle with a
workstation and phone. Now don't forget the model of the workstation, type of
phone, for example speaker phone, cubicle location and number and most important
seems to be the data and phone jack numbers associated with that work area. How
many lists do you have trying to show this information? Now go to THIS and open
up the WORKSAMPLE.THIS file to see an example of how THIS would list these
things you have to deal with in a typical business setting. Note that makes,
models and again, note how workstation models and serial numbers can easily be
added to each item listed as well as location and wall jack(s) information.
By now you must be asking yourself, why not just use a word processor or
spreadsheet to list these items? Go for it! I'm still looking for my list of
important items that I put into a test file a few years ago. I also had several
spreadsheets and word processing documents with various names and all over the
place. THIS just provided me with a "standard" way of representi