Integration

Works with your existing CMMS

Already use Fiix, UpKeep, SAP PM, or Maximo? UMP syncs bidirectionally with your system. Work orders flow in, signed credentials flow out. No double data entry.

[01] COMPATIBILITYSUPPORTED SYSTEMS

Native adapters and generic REST support.

Fiix

Native adapter

UpKeep

Native adapter

eMaint

Native adapter

SAP PM

API integration

IBM Maximo

API integration

Infor EAM

API integration

Custom REST

Generic adapter

Don't see your CMMS? The generic REST adapter connects to any system with an API. Contact us to discuss your specific system.

[02] CAPABILITIESWHAT YOU GET

Bidirectional sync

Work orders flow from your CMMS to UMP. Verification status writes back to your system.

Automatic asset matching

Serial number matching with fuzzy fallback. Learn once, match forever.

Configurable field mapping

Map your CMMS fields to UMP event fields using JSONPath expressions or simple rules.

Auto-issue on close

When work orders close in your CMMS, credentials are issued automatically.

[03] SYNC OPTIONSREAL-TIME OR SCHEDULED

Choose your sync mode.

Webhook (Real-time)

Your CMMS pushes events to UMP instantly when work orders change status.

Best for: Systems with webhook support

Polling (Scheduled)

UMP polls your CMMS at configurable intervals (hourly, daily, etc.).

Best for: Systems without webhook support

Both modes can be used together. Webhooks for immediate sync, polling as a backup to catch any missed events.

[04] DATA FLOWHOW IT WORKS

From work order to signed credential.

Your CMMS

FiixUpKeepSAP PMMaximo

Webhook / Polling

UMP Processing

Automated credential issuance

Asset Match

Field Map

Sign VC

Anchor

Write-back

Credential URL in your CMMS

Work order linked to verifiable proof

[05] PROCESSSTEP BY STEP

The sync process in detail.

1

Work order closes in CMMS

Technician completes work in your existing system — no workflow change.

2

UMP receives notification

Via webhook push or scheduled polling, the work order arrives in UMP.

3

Asset matching

UMP matches the CMMS asset to a UMP asset by serial number or learned mapping.

4

Field mapping

Configurable rules transform CMMS fields into UMP event format.

5

Credential issuance

If auto-issue is enabled, a signed credential is created and anchored.

6

Write-back (optional)

UMP writes the credential URL and verification status back to your CMMS.

[06] SMART MATCHINGASSET RESOLUTION

Automatic asset matching that learns.

Exact serial number match

If the CMMS asset has a serial number that matches a UMP asset exactly, it's linked automatically.

Fuzzy matching

When exact match fails, UMP suggests matches based on make, model, and other attributes with confidence scores.

Learned mappings

Manually resolve a match once, and UMP remembers it for all future work orders from that CMMS asset.

Pending matches queue

When a work order arrives for an unmatched asset, it goes into a pending queue for manual resolution. No data is lost — just waiting for your decision.

[07] SECURITYENTERPRISE READY

Enterprise-grade security.

Encrypted credentials

CMMS API keys and OAuth tokens stored in AWS Secrets Manager, encrypted at rest.

Webhook signature validation

Incoming webhooks are validated using HMAC signatures when supported.

Audit logging

Every sync operation is logged with timestamps, record counts, and error details.

Ready to connect your CMMS?

Let's discuss your specific CMMS and integration requirements.