< Previous section  |  Table of Contents  |  Index  |  Next section >

The equipment and facilities you maintain are called units. Every unit has a location; in fact, units can be locations. For example, in a shopping mall, stores might be considered locations, but they might also be considered units, since they are facilities you maintain. Here are some examples of units:

Sub-Units: Units can contain other units. For example, if a shopping mall treats each store as a unit, then it might be useful to divide large stores into smaller sections (e.g. "Store X Northwest Section", "Store X Northeast Section", and so on.) As another example, consider a forklift truck. This is a single unit, but you might treat the engine and forklift mechanism as sub-units of the truck.

Because units are like locations, and because units can have sub-units (which can also have sub-units), MainBoss depicts units using a map similar to the structure used to depict folders, subfolders, and files in Windows Explorer. The map shows locations and the units they contain.

Organization is Important! Since locations and units are shown in map format, you can make your life easier by setting up your location and unit records in some well-organized manner. For example, suppose you're maintaining a large commercial building. It's a bad idea to set up your location records like this:


With one long list of rooms, it's harder to find the one you want (and you end up scrolling a lot back and forth through the list). Here's a better way to organize the same locations:


Organizing rooms by floor (or in some other sensible way) makes it easier to find the location you want, since you don't have to search through long lists. Organizing your locations also makes it easier to find units, since every unit is a location.

Coding Definitions: The following appear under Coding Definitions | Units to define codes used in unit records:

Before you start recording information about your units, you should think about which of the above codes you intend to use. You don't have to use all the possibilities immediately; for example, when you're just starting out you may decide to omit service contract information—you can always add it later on. However, the more information you record what you start out, the more useful MainBoss can be.

As an example, consider information about spare parts. It can be a lot of work recording which spare parts are used in which unit. Nevertheless, this information can save you a lot of wasted effort: when workers go out to a job, they can look up spare part requirements in advance and can head to the work site prepared. To take a simple example, suppose you record what type of light bulbs are used in every room in your company. (In this case, rooms are the units and the bulbs are spare parts.) When you get a call that a light has burned out, your workers can immediately find out what type of replacement bulb is needed; they never end up having to make two trips because they brought the wrong kind of bulb.

You get back what you put in. Even if you don't record all possible spare parts used by your units, recording some spare part information will save you some wasted effort. Recording more information gives you the potential for more savings. Gradually adding more information (or phasing in the use of different types of codes) will help you get the most from your software.

See Also:

< Previous section  |  Table of Contents  |  Index  |  Next section >