Site Structure

Site Structure

Site Structure is how you logically group Assets into Sites. A Site need not be strictly geographical, but it should be rigid — Sites are meant to organize assets the way you organize them in the real world, and they often follow budgetary lines.

A Recommended Pattern

Build a top-level “Sites” folder containing your real locations, plus two helper folders:

• A Test folder for trying Blueprints and Modifiers before rolling them out org-wide.
• An Unknown Location folder to isolate assets you can’t place yet.

Example: A School District

• Pleasantville Public Schools
  • Sites
    • Pleasantville High School District → PHS
    • Pleasantville Elementary School District
      • Middle Schools → East Middle School, West Middle School
      • Elementary Schools → Elmwood, Lincoln, Meadowlark, Roosevelt
  • Test
  • Unknown Location

Example: A Nonprofit

• Good Neighbor Deeds
  • Sites
    • Pleasantville → Main Campus (Admin Building, Youth Outreach Building), Distribution Center
    • Honeydew Branch Office
  • Test
  • Unknown Location

Common Questions

Should Sites be geographical?
Usually, but not strictly. The key is that they’re rigid and reflect how you organize assets in the real world.

Why add a Test site?
To trial Blueprints and Modifiers safely before rolling out to the whole organization.

What’s the Unknown Location site for?
To isolate assets you can’t yet place, so missing items are easy to spot.

Do Sites relate to budgeting?
Often yes — Sites are frequently drawn along budgetary lines and feed Budget Scenarios.