CMMS Operator Workflow
This guide describes the operator workflow for FactVerse CMMS Operations. It is written for facility managers, maintenance supervisors, service coordinators, and field leads who need a common workspace for work-order review and execution.
Workflow Overview
Prerequisites
| Requirement | Why it matters |
|---|---|
| User permissions | Operators need work-order, asset, attachment, and field-execution permissions |
| Asset identity | Work orders must resolve to the intended asset or location |
| Status mapping | Provider statuses must map to the common lifecycle |
| Assignment rules | Teams need clear ownership for triage, dispatch, execution, and closeout |
| Evidence policy | Photos, reports, checklists, and closeout files need agreed handling |
| Integration mode | Operators should know whether the source is native FactVerse, read-only provider import, handoff, or write-back |
Source Data Inputs
| Input | Use |
|---|---|
| Work-order backlog | Main list of requests, assigned work, blocked work, and closeout candidates |
| Asset context | Equipment, location, history, inspections, alerts, and related documents |
| Provider status | Source-system state used for provider communication |
| Common status | FactVerse lifecycle state used for cross-provider operations |
| Assignment data | Owner, assignee, crew, provider, planned window, and escalation owner |
| Evidence files | Photos, service reports, checklists, permits, and closeout packages |
| Feedback fields | Root cause, action taken, replaced part, outcome, and follow-up recommendation |
Step 1: Review Backlog
Open CMMS Operations or Work Orders and filter by:
- site, building, or area;
- provider or source system;
- common status;
- priority and SLA;
- assigned owner or service provider;
- asset type or system;
- blocked or overdue state.
Start each shift by reviewing critical, high-priority, overdue, blocked, and newly created work.
Step 2: Triage Requests
For each request:
- Confirm the source and provider status.
- Check whether a duplicate work order already exists.
- Confirm the asset, location, and system.
- Review recent alerts, inspections, sensor signals, and related work orders.
- Set or confirm priority and SLA.
- Add triage notes and required evidence.
Step 3: Assign Work
Assign work according to the operating model:
| Assignment type | Use |
|---|---|
| Internal technician | Site team owns execution |
| Contractor | External provider owns field execution |
| Downstream CMMS provider | Native provider workflow owns dispatch |
| Supervisor review | Work needs approval before dispatch |
| Data-quality owner | The record needs mapping or source correction before action |
Record planned maintenance window, access constraints, safety requirements, and required attachments before execution.
Step 4: Execute Field Work
Field users can review assigned work, update progress, capture photos or voice notes, scan QR codes, and report new issues when the workflow is enabled.
Execution updates should preserve:
- start time and completion time;
- field notes;
- photos or files;
- issue count or finding category;
- parts or inventory references when available;
- blocker reason when work cannot proceed.
Step 5: Review Closeout
Before closing:
- Confirm field execution is complete.
- Review source status and common status.
- Check required evidence and service reports.
- Confirm root cause and action taken.
- Record follow-up recommendations.
- Synchronize closeout or feedback according to the integration mode.
Expected Output
At the end of the workflow, the work order should have:
- confirmed asset and location;
- assigned owner and execution record;
- updated lifecycle status;
- evidence files and closeout notes;
- feedback fields for maintenance analytics;
- sync state for connected CMMS or EAM providers.
Validation Checklist
- Operators can find open, assigned, blocked, completed, and closed work.
- Provider status and common status are both visible.
- Asset links open the intended equipment or location.
- Field users can upload evidence under the correct work order.
- Closed work orders preserve root cause, action, outcome, and feedback.
- Sync errors are visible to the owner.
Troubleshooting
| Symptom | Check |
|---|---|
| Operator cannot see assigned work | Role, tenant, site scope, provider filter, and status filter |
| Asset context is missing | MDM publication, alias mapping, retired asset handling, and model binding |
| Work cannot be assigned | Owner field, provider ownership rule, workflow status, and permission |
| Evidence upload fails | File size, file type, folder permission, ECM policy, and network state |
| Closeout cannot synchronize | Provider permission, field mapping, status transition rule, and sync log |