The Asset Passport
One physical asset, as EOS holds it: every record that describes it, where those records disagree, what each costs, the evidence behind each statement, and the one next step, all under one persistent identity. Portunus is the capture, the code on the part. The Passport is the object that code points to.
The asset below is a brake caliper from the synthetic tenant, the same asset the Portunus demonstration scans. Every figure on this page is DEMO sample data from the tenant file, not a customer's record. The page draws itself from one JSON object you can read.
- Identity
- Source records
- Lifecycle
- Documents
- Maintenance
- Financial exposure
- Risk
- QR
- Evidence
- History
- Current status
- Recommendations
- Proof
The sample could not be read, so nothing is drawn. The page shows no figure it cannot read from the JSON.
Identity
One persistent identity; every other record attaches to it.
Source records
Five systems state where this part is and under what warranty. EOS reads each and keeps every statement beside the others; none is overwritten.
Lifecycle
Dashed stages are projected, not recorded.
Documents
The documents the statements above rest on, and the system that holds each one.
Maintenance
Service events with their work order; the wear trend is derived from them.
Financial exposure
Lifecycle value and the exposure the open disagreements put at risk.
Risk
Each open disagreement names the authority that can settle it.
QR
The code carries a pointer to the identity, not the asset's data. It is drawn in this page, on this device; nothing is sent anywhere.
Evidence
Every statement above names the record behind it and says how it is known.
History
Dated events, oldest first. EOS adds none of its own: it holds no write credential to these systems.
Current status
Where the asset stands now, and what is still open.
Recommendations
Each recommendation gives the conclusion, why, the systems it rests on, the action, an expected impact as a modeled range, and the assumptions. None is executed; each waits for a named approval.
Proof
One figure on this page, the lifecycle value, carries its own derivation. Open it, recompute it here, or download it.
Next: the discrepancy session opens one disagreement between two systems end to end; the verification ledger explains how a proof object is published and checked. Request an assessment to see your own assets here.
Read-only toward your systems of record. Every figure on this page is sample data from a synthetic tenant, labeled DEMO.