Docs menu
Configuring CMS Industrial for your organization.
What's live today for project setup, access control, and system monitoring — and what's still ahead on the admin roadmap.
Dashboards are gated by access rights.
Every screen is gated by access rights, so each role sees exactly the dashboards and actions it's authorized for. The admin console itself requires the config:admin right — everyone else is refused before the page ever renders.
Project configuration is set once and enforced automatically.
Every project is configured with the fields below before intake begins, so downstream workflows (commissioning gates, reconciliation, retention) run without manual re-checking.
Entry model
Design-first or manifest-first intake, set per project.
Governance tier
Owner, contractor, or OEM — sets the compliance posture.
Reconciliation model
Reconcile before or after intake, per your operational process.
Retention policy
Fast-retire or long-term-retain, driving decommissioning defaults.
Historian target & intake template
Where data lands downstream and how intake manifests are structured.
Site, manager & engineer assignment
Who's accountable for the project across sites and the asset hierarchy.
Configurable values, field by field.
The exact options behind each field above.
| Field | Options |
|---|---|
| Entry model | Design-first · Manifest-first |
| Governance tier | Owner · Contractor · OEM |
| Reconciliation model | After-intake (polling) · Pre-intake (blocking) |
| Retention policy | Fast-retire · Long-term-retain |
| Project status | Active · Closing · Closed |
A project moves through three states.
Status isn't a free-text field — it's a lifecycle, and moving from Closing to Closed is gated by the closure checklist below.
Active
Normal operation — intake, tracking, and reconciliation all run.
Closing
Closure has been initiated; the prerequisite checklist is being worked through.
Closed
All prerequisites passed and the project was finalized with a captured reason.
Closing a project requires a gated checklist.
Closing a project checks every prerequisite before it lets you finalize. Each prerequisite is Ready, Blocked, or Not yet implemented — you see exactly what's holding up closure, traced back to real operational data.
- Asset decommissioning progress — how many assets are decommissioned vs. remaining
- Open transfers — none left in flight
- Open work orders — none left in flight
- Open reconciliations — no unresolved discrepancies
- Assets currently in use — none checked out
- Reason-for-change required before finalizing
System health monitoring.
The admin console's system health panel shows live component status and any queued/backlogged records, so operational issues surface before they become compliance issues.
On the admin roadmap.
- Validation-rules consoleRoadmap
- Email/notification watcher configurationRoadmap
- Archive lock controlsRoadmap
- Team activity viewRoadmap
- Access review workflowRoadmap
- Energy / utility IoT monitoringRoadmap
- Connectors for existing SCADA, historian & OEM systemsRoadmap