Digital twin · asset foundation
For the engineers who own the asset register and the twin. Capture the plant once, govern the hierarchy from enterprise to component, and every module reads the same asset truth.
Built in, not bolted on
Enterprise to system to component to CML, one governed spine every module reads its asset from.
The whole estate
Its systems
Every component, addressable
Capabilities
03 layers · scroll to stack
One governed hierarchy, so every module and your CMMS read the same equipment, not six versions.
Click the steel in 3D and see every record ever logged on it, in place.
The scan you already paid for becomes the living interface to the asset, not a dead file.
Duplicate codes are flagged before they save, so the same pump stops appearing seven times.
Assisted extraction reads P&IDs into structured tags, turning months of mapping into weeks of review.
Contractor data is validated at the door, so the as-built register is born clean and matches the plant.
Every asset and relationship reads and writes through one API, the shared spine across the systems you run.
Effective-dated relationships record when an asset moved, so the register keeps its past without clouding the present.
For the asset register owner
Real screens from the platform, not mockups
Grounded by design
Proof
Standards referenced
Explore
03 related modules
Evaluation path
Answers
No. intelliVISION is the asset register and digital twin every intelliSPEC module resolves to, sitting alongside your CMMS or EAM. Your current system of record stays in place; intelliVISION keeps every discipline reading the same asset.
3D models, photogrammetry, and LiDAR or 360 reality capture. The scan becomes a navigable model where you click an asset and see every record logged on it, in place.
Yes. It is included with every intelliSPEC subscription, because cross-module asset truth only works when every module reads from the same register.
Yes. Import any entity type from Excel with column mapping, validation, and a preview before anything commits, and export a structured workbook with deduplication keys per entity type.
Through one open API. The same asset that appears in an inspection package also appears in an integrity circuit, a turnaround scope, a coating spec, and a fireproofing zone, by the same identity.
ISO 55001 and ISO 14224 for asset and reliability data, CFIHOS and ISO 15926 for handover and interoperability, DEXPI for P&ID exchange, and ISA-95 and IEC 81346 for hierarchy and tagging.
Each asset carries a unique code in its scope, enforced before it saves, and Spectra surfaces naming inconsistencies and hierarchy gaps continuously, so the register stays clean as it grows.
See one asset workflow, from field record to audit evidence.
