How to Structure Sites, Categories, Locations, and Departments

How to structure sites, categories, locations, and departments

Four structures, four questions. Keeping them separate is the single most valuable structural decision you will make.

An asset is filed under a Category, Location (which belongs to a Site), and Department independently. Site comes from the Location — it is not a separate field on the asset.

Categories carry the money

This is the part people miss. A category carries depreciation configuration — method, useful life, rate, residual value percentage, and MACRS property class.

Financial treatment is declared once per class of asset rather than per asset. An asset with no category has no depreciation configuration and therefore no net book value.

So the right question when designing categories is: do these things share a financial treatment?

Categories can also carry preventive maintenance rules that apply to every asset in them, including assets added later. One rule on "Fire Extinguishers" covers every extinguisher you will ever add. This is the highest-leverage thing categories do.

Filtering includes descendants

Filtering on a category returns everything beneath it — filtering "IT Equipment" returns the laptops under "IT Equipment → Portable → Laptops".

The same applies to locations. You never have to select every child.

Keep them apart

The failure mode is encoding one structure inside another.

Every time you combine two dimensions into one, you lose the ability to ask about either independently.

Depth

Two to four levels covers most organizations for categories and for locations within a Site.

The test: if nobody will ever filter at a level, that level does not need to exist.

Depth you do not need costs you on every asset form, because someone has to pick the right leaf.

For multiple operational places (two plants, two campuses), create separate Sites, each with its own location tree — do not encode the site name into every location. See How to build a location hierarchy.

Start small

You do not need the finished structure before you add assets. Time to first asset matters more than a perfect taxonomy, and both hierarchies are easy to extend.

Every organization starts with a Main Office Site. On Nova that is your one Site; on Orbit and above, add Sites for additional facilities first, then build locations under each. See Main Office — the default Site.

Start with the classes and places you actually have. Add depth when a filter you want to run is not possible.

Nothing is deleted

Categories and departments archive rather than delete, so restructuring is reversible and history stays attributable. Locations can be archived or, when empty, deleted. Sites are archived, not deleted.

Move the assets before archiving the structure they sit in.

Where custom fields fit

(Orbit and above)

When you need a dimension none of these provide — a cost centre code, a compliance grade, a contract reference — use a custom field. They are filterable and are included in exports.

Do not build a custom field that duplicates your category tree.

A worked example

A facilities team across two Sites:

Sites                     Categories              Locations (per Site)     Departments
Manchester                HVAC                    Building A               Facilities
Leeds                      |-- Rooftop units       |-- Floor 1             Operations
                           +-- Air handling        +-- Floor 2             Finance
                          Electrical              Building B               IT
                           |-- Distribution        +-- Workshop
                           +-- Lighting
                          IT Equipment
                           +-- Portable

A rooftop unit is: category "Rooftop units", Site "Manchester" (via location), location "Building A → Floor 1", department "Facilities". Each answers its own question, and none repeats another.

Related articles

• Categories, sites, locations and departments explained
• What are Sites?
• Managing categories
• How to build a location hierarchy
• Managing departments
• Asset naming conventions
• Custom fields