Connect CMMS and EAM Data to FactVerse
Use this guide when a customer needs FactVerse to read, normalize, and govern work-order data from one or more CMMS or EAM providers. The goal is a reliable operations dataset that can support CMMS Operations, Facility Operations, Predictive Maintenance, ECM evidence, dashboards, and AI Agent workflows.
For a multi-provider architecture, read Multi-CMMS Consolidation first.
Integration Flow
Two Data Paths
CMMS data enters FactVerse through two different patterns:
| Path | Use it for | Notes |
|---|---|---|
| Master data loading | Equipment, spare parts, inventory references, preventive-maintenance templates, schedules, and demo data | Uses the existing domain create/import flows and the shared equipment registry. |
| External CMMS integration | Commercial CMMS or EAM systems that remain the customer system of record | Uses a connector or adapter pattern, with explicit asset mapping and synchronization rules. |
Treat these as separate implementation decisions. Loading equipment and preventive-maintenance master data prepares the FactVerse operating model. Connecting Maximo, Honeywell Forge, SAP PM, or another CMMS defines how source records and write-back should be synchronized.
Prerequisites
| Requirement | Why it matters |
|---|---|
| Source owner | A customer owner must approve source access, field meaning, synchronization cadence, and exception handling |
| Integration method | REST, JDBC, CSV, SFTP, Fabric, middleware, or manual upload must be selected for each provider |
| Service identity | A scoped account or credential is required for scheduled imports and controlled write-back |
| Work-order model | Required fields, status values, priority values, SLA rules, assignment fields, and closeout codes must be understood |
| Asset identity | Work orders need a stable asset, equipment, location, or system reference before operational use |
| Data freshness target | The team must decide whether the workflow needs near-real-time, hourly, daily, or manual refresh |
| Review owner | Someone must review rejected rows, mapping exceptions, duplicates, and stale data |
Source Data Inputs
| Input | Required fields |
|---|---|
| Work-order header | Work-order ID, provider ID, source status, priority, type, title, description, requester, owner, assignee |
| Lifecycle timestamps | Created, approved, assigned, started, completed, closed, canceled, reopened, last updated |
| Asset reference | Source asset ID, equipment ID, building, floor, room, system, line, or functional location |
| SLA and priority | Priority, severity, due date, response target, completion target, breach indicator |
| Execution details | Work type, service category, fault code, action taken, root cause, resolution note |
| Attachments | File ID, file name, URL or source path, document type, upload time, access policy |
| Synchronization metadata | Import time, source revision, sync state, retry count, error reason |
Choose the Connector Pattern
| Pattern | Use when | Review points |
|---|---|---|
| REST API | The provider exposes work-order, asset, attachment, and status endpoints | Pagination, rate limits, deleted records, retries, and field-level permission |
| JDBC or database view | The customer exposes curated views for reporting or integration | Read isolation, query window, timezone handling, and source-owner approval |
| CSV or scheduled file | The source can export reliable files on a schedule | File naming, schema drift, duplicate rows, failed deliveries, and late files |
| SFTP or managed file drop | The customer uses controlled file exchange | Credential rotation, folder cleanup, transfer logs, and partial-file handling |
| Fabric or data lake | CMMS records are already staged in a governed data platform | Dataset owner, refresh schedule, lineage, and field definitions |
| Manual upload | Pilot, one-time import, or offline site setup | Reviewer signoff, versioning, and replacement rules |
Configure DFS Lite
- Open DFS Lite > Connectors.
- Create or select the connector for the CMMS, EAM, file source, or middleware.
- Configure authentication, endpoint, folder, database view, or dataset reference.
- Run a small sample import.
- Open preview and confirm row count, required fields, and timestamp parsing.
- Save the connector and record the refresh cadence.
Use a narrow sample first. A pilot import should include open, completed, closed, blocked, canceled, and reopened work orders so mapping issues appear early.
Load CMMS Master Data
CMMS reads the shared equipment registry, preventive-maintenance, spare-parts, and inventory records. Operators can start from the standard domain create/import flows, then add provider synchronization where the deployment needs it.
| Domain | Loading approach |
|---|---|
| Equipment | Onboard equipment through the shared equipment registry used by Facility Operations, Predictive Maintenance, and other modules |
| Spare parts | Create and maintain part catalog records, low-stock rules, and equipment associations where the spare-parts workflow is enabled |
| Inventory | Use issue, receive, transaction, and valuation flows when warehouse or spare-parts stock movement needs to be visible |
| Preventive maintenance | Create preventive-maintenance templates and schedules so due schedules can appear on the calendar and generate work orders when enabled |
| Work requests | Capture demand through field worker, portal, natural-language, alert, email, or supervisor entry paths |
For pilots and demos, seed a tenant with clearly marked evaluation data: equipment, mixed-status work orders, preventive-maintenance schedules, spare parts, technicians, crews, and work requests. Keep evaluation records distinguishable from customer operational records and production evidence.
Map Fields
Create a mapping from source fields to the normalized work-order model:
| Target field | Mapping notes |
|---|---|
provider_id | Stable provider key such as maximo-sg-campus or sap-pm-plant-a |
source_work_order_id | Native provider work-order identifier |
common_status | Mapped lifecycle state used by FactVerse operators |
source_status | Original provider status retained for audit and provider communication |
asset_ref | MDM-aligned asset, equipment, location, or system reference |
priority | Normalized priority with source priority retained |
sla_due_at | Due time or response target after timezone normalization |
closeout_summary | Customer-readable completion, root-cause, or remediation note |
sync_state | Imported, pending review, rejected, stale, retrying, or synchronized |
For lifecycle mapping details, see Work-Order Lifecycle and Status Mapping.
External CMMS Adapter Pattern
When a commercial CMMS remains the system of record, FactVerse connects through a governed work-order adapter pattern. The adapter profile depends on the downstream system: webhook, Generic REST, IBM Maximo, SAP Plant Maintenance, or a customer-approved overlay such as Honeywell Forge.
The pattern typically includes:
- pushing reviewed work orders or handoff records to the provider;
- pulling status updates back into the unified work-order view;
- maintaining a provider-specific asset mapping between FactVerse equipment and the external asset ID;
- recording synchronization logs, retries, and provider responses;
- separating read-only imports, draft handoff, status sync, and write-back permissions.
Use CMMS Work-Order Adapters, the provider-specific adapter documentation, and the customer-approved integration mode as the final contract. Field protocol adapters such as BACnet, Modbus, and SNMP provide equipment context; they do not replace a downstream CMMS work-order adapter.
Validate Data Quality
Before exposing the dataset to operators, check:
- required fields are present for open and closed work orders;
- timestamps parse correctly and use the expected timezone;
- source statuses map to a common lifecycle state;
- asset references can be matched through MDM;
- duplicate source records are detected;
- canceled and reopened work orders retain the original source reason;
- attachments have reachable paths and approved access policy;
- sync errors are visible to the review owner.
Expected Output
At the end of integration setup, the customer should have:
- an approved connector or import path;
- a normalized work-order dataset;
- field mapping and status mapping records;
- asset identity match results;
- rejected-row and exception review process;
- sync history for imports, retries, and failures;
- a handoff decision for read-only aggregation, controlled handoff, or write-back.
Troubleshooting
| Symptom | Check |
|---|---|
| Work orders import but do not appear in CMMS Operations | Provider ID, tenant scope, source status mapping, and dataset publication state |
| Many records are rejected | Required fields, timestamp format, field type, enum mapping, and source schema drift |
| Asset links are missing | Source asset ID, alias table, MDM match confidence, retired assets, and location hierarchy |
| Status looks wrong | Provider status taxonomy, canceled/reopened mapping, and source status overrides |
| Duplicates appear | Import window, source revision, provider ID, source work-order ID, and retry behavior |
| Attachments are missing | File access, attachment metadata, ECM import rule, file size, and retention policy |
| Data is stale | Connector schedule, last successful sync, rate limit, failed job, and source export time |