INDUSTRIAL ASSET LIFECYCLE DATA
Book a demo
Built by practitioners. Demoed on real open data — Equinor’s Huldra platform — plus a synthetic refinery dataset.
$15.8B
2002 US INTEROPERABILITY COST — NIST
3D view — Huldra platform, Equinor public open data
01 / THE PROBLEM
Today’s asset data stack is fragmented by design: reference data in one tool, tag registers in another, documents in a separate DMS, AWP somewhere else, and 3D review bolted on top. Every seam becomes a mapping project, and every export begins going stale. In a 599-person industry survey, construction professionals averaged 5.5 hours a week looking for project information; the same PlanGrid/FMI research attributed 48% of US rework to poor data and miscommunication. NIST estimated poor interoperability cost the US capital-facilities industry $15.8 billion in 2002, with two-thirds borne by owners and operators. Handover does not fix the architecture — it moves the fragmentation into operations.
The fragmented stack — every seam is a mapping project
02 / THE PLATFORM
One data environment, one asset record
Every module below reads and writes the same asset record. Not integrated tools - one platform, one record, no seams.
01 / DEFINE
Structure the record before execution.
Living RDL / class library
Validation, completeness scoring, CFIHOS-aligned.
Tag Master Register (TMR)
The register born in FEED, carried to operations.
Standards library
Engineering standards adopted per project and cited clause by clause.
Requirements & traceability
Live records and evidence matrix that flags gaps as they appear.
02 / EXECUTE
Build against the governed record.
Document Management (DMS)
Revisions, transmittals, registers.
AWP / construction
Work packaging, constraints, look-ahead planning, field execution, progress, and 4D schedule playback. CII cites up to 25% productivity improvement and up to 10% TIC savings in effective AWP.
Quality & inspection
Inspection plans and records, hold points, NCRs, sign-off queues — traced to the requirements they verify.
03 / PROVE
Freeze evidence at handover.
Stage gates & change management
MOC with impact scanning; stage-gate evidence frozen at sign-off.
Completions & commissioning
Systemization, checksheets, punch lists, certificates.
Turnover dossiers
Handover packages per system or unit, pinned to exact document revisions.
04 / OPERATE
Carry the record into operations.
Operations & maintenance
Asset cards carry maintenance and operations data; work requests raised from 3D or reports, routed through workflows.
Shared record services
3D
Models, laser scans, point clouds; optional, not a prerequisite.
Workflows
Configurable review and approval graphs.
Automation / ETL & API
Visual pipelines plus a read/write REST API.
Dashboards & visual reports
Coverage, quality, and 3D color reports.
Knowledge graph
Relationships across assets, documents, and requirements.
Map / GIS
Geographic asset and work views; live field tracking shown today as a simulation (proof of concept).
AI assistant
Agentic, works on the same record with gated write access.
Configurable modules & grids
Build views and modules from grids, dashboards, 3D scenes, and workflows.
Atlas ALP platform map — one record, every module
A / FOUNDATION
Living RDL
The class library isn’t a document sitting beside your data — it drives validation, completeness scoring, and compliance reporting in place, continuously. Change a class definition and every downstream check follows it, instead of drifting out of sync with the register it’s supposed to govern.
Living RDL class library and validation workspace in Atlas ALP.
One asset record — documents, cross-references, 3D tag
B / CONTINUITY
Digital thread by default
Documents, 3D models, and work packages attach to the same asset record instead of living in separate systems cross-referenced by hand. The tag register built in FEED is the same tag register that carries into execution and handover — one continuous history, not a reset at every phase boundary.
C / OPTIONAL LAYER
3D when you have it
Work packaging, scoping, and progress tracking all run in ordinary grids and trees — no 3D model required. When a solid model, laser scan, or bubbleview does exist, 3D layers on top: draw a box to scope a work package, or paint red/green progress straight onto the geometry.
Work-package scoping in 3D — Huldra
D / HANDOVER
Handover that proves itself
CFIHOS-aligned reference data plus live coverage dashboards mean handover readiness is measured continuously, not discovered in a scramble at the end. “Pumps without datasheets” is a live query against the class library, not a spreadsheet exercise run once before the client walks in.
CFIHOS coverage dashboard — Refinery Demo
05 / ROADMAP
Where it’s going
Everything above runs today. What’s next is labeled as such — here and everywhere we show the product.
Atlas ALP is not a CMMS — it works alongside yours; direct connections are on the roadmap.
CMMS connections (Maximo, SAP PM)
Historian connections (OSIsoft PI)
Webhooks / event subscriptions on the external API (the REST API itself already exists — only eventing is next)
Live P6 schedule sync (schedule file import exists today)
Resource & cost loading in work packages
Crew mobile app for the field
Write-time reference-data enforcement (today the platform flags violations continuously; hard rejection at write time is next)
03 / ABOUT
Atlas ALP is built by a practitioner who has run information-handover and data-quality work firsthand, not a product team working from secondhand requirements. It’s early-stage software: what’s shown here is real and working today, and roadmap features — including CMMS connections (Maximo, SAP PM) and historian connections (OSIsoft PI) — are labeled plainly rather than implied. Every screenshot and recording is a real product demo, run against either Equinor’s public Huldra engineering dataset or the synthetic Refinery Demo project.
Book a demo