Admin Reference
Systems Route Reference
Understand the office-side system register and its relationship to sites, assets, and inspection planning.
Before you start
- You need the system layer above assets and below sites.
Expected outcome
You can manage systems cleanly enough for asset grouping, inspection binding, and scheduler context to stay consistent.
What this route is for
Systems owns the middle layer between sites and assets, keeping the site installation structure clean enough for inspections, exports, and asset grouping to work consistently.
Visibility and capability notes
| Item | Details |
|---|---|
| Route id | systems |
| Visibility | Customer-facing core route. |
| Capability notes | Import links depend on connected-system availability, but system maintenance itself is broadly available. |
| Direct inbound | Shell nav, inspection planning context, global search, activity links, and site-driven register review. |
Main regions, dialogs, and controls
| Surface | What it does |
|---|---|
| System list | Searchable, paginated register scoped by site when needed. |
| System dialog | Create or edit system details. |
| Asset drill-in | Opens the child asset slice for the selected system. |
| Import action | Launches staged register import. |
Key actions
- Create or edit a system.
- Filter systems by site and search.
- Open the child asset view for one system.
- Launch staged import for systems and assets.
Filters and URL state
| Param | What it controls |
|---|---|
page | Pagination |
q | Search |
siteId | Site scope |
systemId | Open detail context |
create | Opens create mode |
- Search is debounced and the register is paginated.
- The route is list-first and dialog-driven.
Outputs and side effects
- Creates or updates system records that sit above assets.
- Sends the user into the asset register with site and system scope preserved.
- Launches staged import for bulk changes.
Inbound links
- Shell
Systemsnavigation. - Inspection creation or review context.
- Activity Feed resource links.
Outbound links
#/assets?siteId=...&systemId=...#/connected-systems?section=imports&dataset=systems-assets
Indirect handoffs
- Clean system structure keeps asset grouping, inspection binding, and report language more stable.
- The system layer is where many teams prevent a site from becoming one flat, unmanageable equipment list.
Troubleshooting
| Symptom | What to check |
|---|---|
| The wrong assets open from a system row | Confirm the route preserved both siteId and systemId. |
| A system is missing from the list | Re-check current site scope and search state before treating it as deleted. |
| Imported structure does not match expectations | Review the staged import dataset and upstream source mapping in Connected Systems. |