Appendix A — Master Data Dependencies¶
Reference Document | Audience: Admin, Owner
Overview¶
This appendix shows how master data entities depend on each other. Set up entities from top to bottom — an entity cannot be created until its dependencies exist.
Dependency Tree¶
Countries ← standalone; create first
└── States ← depends on Country
└── Sites ← depends on Country; optionally State
└── Locations ← depends on Site; parent Location
(hierarchical: Building → Block → Floor → Zone → Room → Sub Location)
Departments ← standalone
Asset Categories ← standalone; self-referencing hierarchy (parent category)
Asset Statuses ← standalone
Asset Conditions ← standalone
Manufacturers ← standalone
└── Models ← depends on Manufacturer
Suppliers ← standalone
(optionally linked to: Asset Categories, Locations, Transaction Types)
Activity Types ← standalone
User Groups ← depends on Users (for members)
Checklist Templates ← standalone
Cost Templates ← standalone
Roles ← standalone
└── Permissions ← system-defined; assigned to Roles
Users ← depends on: Departments, Locations, Roles, Users (Reporting Manager)
─────────────────────────────────────────────────────────────
OPERATIONAL ENTITIES (depend on master data above)
─────────────────────────────────────────────────────────────
Assets ← depends on: Categories, Statuses, Conditions,
Locations, Departments, Manufacturers, Models,
Suppliers, Users
Floor Plans ← depends on: Locations
RFID Readers ← depends on: Locations, Reader Types, Floor Plans
Reader Types ← standalone
Vehicles ← depends on: Manufacturers, Models
Workflow Templates ← depends on: Roles, Users (for approval levels)
Schedules ← depends on: Activity Types, Assets, Locations,
User Groups, Cost Templates, Checklist Templates
Audit Requests ← depends on: Categories, Statuses, Conditions,
Locations, Departments, Users
Transfer Requests ← depends on: Assets, Locations, Departments, Users, Vehicles
Disposal Requests ← depends on: Assets
Recommended Setup Sequence¶
| Order | Entity | Prerequisites |
|---|---|---|
| 1 | Countries | (none) |
| 2 | States | Countries |
| 3 | Sites | Countries, States |
| 4 | Locations | Sites |
| 5 | Departments | (none) |
| 6 | Asset Categories | (none — self-referencing) |
| 7 | Asset Statuses | (none) |
| 8 | Asset Conditions | (none) |
| 9 | Manufacturers | (none) |
| 10 | Models | Manufacturers |
| 11 | Suppliers | (none — optional links to Categories, Locations) |
| 12 | Activity Types | (none) |
| 13 | Checklist Templates | (none) |
| 14 | Cost Templates | (none) |
| 15 | Roles | (none) |
| 16 | Users | Departments, Locations, Roles |
| 17 | User Groups | Users |
| 18 | Assets | Steps 4–11, 16 |
| 19 | Workflow Templates | Roles, Users |
| 20 | Everything else | As needed |
Key Dependency Rules¶
| Rule | Detail |
|---|---|
| State → Country | A State must belong to a Country |
| Site → Country | A Site must have a Country; if a State is selected, it must belong to the same Country |
| Location → Site | A Location can optionally belong to a Site |
| Location → Parent | A Location's parent must be the immediate parent type (e.g., Floor's parent must be a Block) |
| Model → Manufacturer | A Model must belong to a Manufacturer |
| Asset → Category | Every asset must have a Category |
| Asset → Status | Every asset must have a Status |
| Asset → Location | Every asset must have a Location |
| User → Department | Every user must be assigned a Department |
| User → Location | Every user must be assigned at least one Location |
| User → Role | Every user must have a Role |
| User → Reporting Manager | Every user must have a Reporting Manager (another User) |
Back to: Index · Master Data Configuration