Universal Maintenance Passport: a platform for creating, managing, and verifying tamper-evident maintenance records using W3C Verifiable Credentials. UMP is the system of proof that complements your existing CMMS or maintenance management system.
Key Takeaways
- 1UMP uses W3C Verifiable Credentials 2.0 — a web standard for tamper-evident claims
- 2Records are signed by issuers and can be verified by anyone without 'phoning home'
- 3Offline-first architecture means maintenance can be recorded even without connectivity
- 4UMP complements existing CMMS/EAM systems rather than replacing them
The UMP philosophy
UMP is built on a simple insight: the system of work and the system of proof should be separate. Your CMMS is where work gets planned and tracked. UMP is where that work becomes a verifiable credential that travels with the asset.
| Aspect | CMMS/EAM | UMP |
|---|---|---|
| Primary purpose | Manage work | Prove work happened |
| Audience | Internal teams | External counterparties |
| Trust model | Access controls | Cryptographic signatures |
| Data portability | PDF exports | Verifiable credentials |
| Verification | Call to confirm | Verify instantly |
Not another CMMS
UMP doesn't replace your existing maintenance management system. You keep using whatever tools your teams are comfortable with. UMP adds a layer of verifiable proof on top — like a notary for your maintenance records.
How UMP works
UMP transforms maintenance events into verifiable credentials through a straightforward process:
Capture
Maintenance events are recorded — either directly in UMP's offline-capable app, imported from your CMMS, or ingested from telematics systems.
Sign
Each event is cryptographically signed by the service provider using their verified identity. This signature is mathematically tied to both the issuer and the content.
Anchor
A hash of each credential is recorded in an append-only ledger, creating an immutable timestamp that proves when the record was created.
Share
Asset owners generate passport packs — bundles of credentials with selective disclosure — to share with buyers, lenders, or inspectors.
Verify
Anyone with a passport link can verify the signatures, check the ledger anchors, and confirm the records are authentic — without creating an account.
The standards behind UMP
UMP is built on open standards, not proprietary formats. This ensures interoperability and prevents vendor lock-in:
W3C Verifiable Credentials 2.0
The web standard for tamper-evident credentials. Used for everything from academic certificates to government IDs. UMP maintenance records are VCs that any compliant verifier can check.
JSON Web Signatures (JWS)
The cryptographic signature format that makes credentials tamper-evident. Industry-standard, widely supported, battle-tested.
did:web for issuer identity
Decentralized identifiers that tie signatures to verifiable organizations. Service providers prove their identity without a central authority.
GS1 GIAI for asset identity
Global individual asset identifiers that work across industries. Map your existing serial numbers to globally unique IDs.
Future-proof by design
These standards are also used for EU Digital Product Passports and Battery Passports. Building on them now means your maintenance records will integrate seamlessly as those regulations roll out.
Offline-first architecture
Maintenance happens where connectivity is unreliable — job sites, remote locations, inside metal buildings. UMP is designed for this reality:
Work offline
Capture maintenance events, photos, and signatures without an internet connection.
Sync when connected
Changes merge automatically when connectivity returns using conflict-free data types.
No lost data
Background synchronization with automatic retry ensures your drafts are preserved and synced when connectivity returns.
Queue for signing
Credentials are issued and anchored when back online, with full audit trail.
This isn't "offline mode as a fallback" — it's how UMP is designed to work. The app assumes connectivity is intermittent and handles it gracefully.
Integration, not replacement
UMP connects to your existing systems rather than asking you to abandon them:
CMMS export
Import work orders from systems like Maximo, SAP PM, UpKeep, or Fiix.
Telematics ingest
Pull meter readings from AEMP 2.0 feeds, OPC UA, or NMEA 2000.
Direct capture
Use UMP's mobile app for standalone credential issuance.
Integration timeline
Verify-only integration takes hours — just check credentials against the API. Export-on-close integration takes days.Full offline capture takes weeks but provides the richest experience.
The three layers of UMP
UMP is composed of three main components, each serving a different role in the ecosystem:
Issuer app
Mobile and desktop applications for service providers to capture maintenance events, attach evidence, and issue signed credentials. Works offline with automatic background sync.
Owner portal
Web application where asset owners manage their passports, generate sharing links, and control what information is disclosed to which parties.
Verifier portal
Public verification interface where anyone can paste a passport link and verify signatures, check ledger anchors, and view permitted evidence — without logging in.
What makes UMP different
Several features distinguish UMP from document management systems or basic digital record-keeping:
Tamper-evident by math
Signatures use the same cryptography as banking and government systems. Changes are detectable.
Selective disclosure
Share only what's needed. Show safety-critical maintenance to inspectors, full history to buyers.
No phone home
Verification doesn't require logging into your systems or calling your service providers.
Append-only ledger
Records can't be backdated or deleted. The ledger proves when each credential was created.
Standards-based
Built on W3C VCs, JWS, DIDs — not proprietary formats that lock you in.
Asset-centric
The passport belongs to the asset and transfers with it, not locked in a service provider's system.
Who uses UMP
UMP serves three main roles in the maintenance credential ecosystem:
Issuers (service providers)
MROs, dealerships, independent shops, and OEMs who perform maintenance and want to provide verifiable proof of their work. Issuing credentials builds reputation.
Owners (asset holders)
Fleet operators, equipment owners, and asset managers who want to prove their maintenance investment and get better transaction outcomes.
Verifiers (counterparties)
Buyers, lenders, insurers, inspectors, and auditors who need to confirm maintenance history without relying on trust.
The network effect
Value increases as more parties participate. More issuers means more assets have complete records. More verifiers demanding credentials creates incentive for owners to collect them. The flywheel spins faster over time.
Getting started with UMP
Ready to explore how UMP fits your organization? Here are the paths forward:
For service providers
Start issuing signed credentials for your maintenance work. Differentiate your services with verifiable records.
For asset owners
Begin collecting signed credentials for your fleet. Use them to accelerate sales and improve financing terms.
For platforms
Integrate verification into your marketplace, lending, or insurance workflows. Require credentials as a listing standard.
Learn about the MXM Mark
The certification badge for assets with verified maintenance records.
Read article