
Inspector
Capture defensible readings in the field, network or not, and close the inspection without a second pass.
Asset-aware wizards configure to the equipment in front of you, every NDE method recorded, signed before you change your PPE.
Solutions
Start from the job you own or the asset class you run. Either way you land on one record, every discipline reading from the same digital twin.
Find your fit
Twenty-three sectors, one platform. Name the job you own and the asset class you run, and land on the record configured for it.
Pick your asset class to open the thread that fits it.

Built in, not bolted on
One thread, role by role. Every discipline, one record.
Inspector, integrity engineer, turnaround director: each starts where they own the work and lands on one record.

By role
Six roles, six jobs-to-be-done. Each routes to the disciplines that close it on one record.

Capture defensible readings in the field, network or not, and close the inspection without a second pass.
Asset-aware wizards configure to the equipment in front of you, every NDE method recorded, signed before you change your PPE.

Turn condition into a risk verdict and a fitness-for-service call you can defend to API 579.
RBI, FFS, corrosion rates and remaining life recompute the moment the readings land, with the standard cited.

Keep scope, schedule and cost on one thread, from readiness through the close-out report.
Gate reviews, inspector readiness and serialized inventory on one record, so the event does not drift over budget.

Make every permit, JSA, LOTO and incident defensible by default, not assembled the week of the audit.
Safety and compliance records build themselves as the work happens, with inspector qualifications checked at assignment.

See the real condition of the asset base and where the next failure is most likely to land.
One digital twin reads from every discipline, so risk, readiness and the record live in one place, not six systems.

Stand up one system of record your team can configure, without a multi-quarter rollout or a custom build.
Metadata-driven configuration, offline-first architecture, and governance built in: 524-permission RBAC and an audit trail.
By industry
Twenty-three sectors, grouped by the assets they run. Each tile leads with the outcome and the code it answers to, then opens the thread configured for your plant.
Built with input from operators across these sectors. Run a different asset class? See yours configured live.
One thread
The inspector, the integrity engineer and the turnaround manager work the same record, in step every shift.
“The inspector, the integrity engineer and the turnaround manager read the same record. One digital twin, every discipline, no second system of truth.”
Answers
Either works, both land on the same place. Start by role when you own a specific job, like inspection, integrity or the turnaround. Start by industry when you want to see the thread that fits your asset class. Both routes deep-link into the same modules and the same record.
Not yet. Each role card states one job-to-be-done and routes to the modules that close it. Those module pages carry the full detail. Per-role landing pages land later, as the named references and outcomes firm up.
The site covers oil and gas, LNG and gas processing, pipelines and terminals, power, nuclear, renewables, chemical, mining, manufacturing, utilities, water and wastewater, data centers, semiconductor, aerospace, automotive, rail, maritime, pharma, food and beverage, pulp and paper, cement, defense, and paint and coatings. A different sector can still be mapped live from your asset class and workflow.
They do not bolt together, they read from one record. An inspection reading recomputes the risk verdict, the remaining life and the turnaround scope at once. You adopt the modules you need first, then add the rest without a migration.
Yes. Asset-aware wizards configure to the equipment in front of the inspector, and 524-permission RBAC maps to your org. Configuration is metadata, not custom code, so a new asset class or workflow goes live in days, not a multi-quarter build.

See the failure before it happens. Prove the work after it is done.