THE PLATFORM DIRECTION

One plant record.
Every stage of the work.

INSP Works is being developed to connect field capture, inspection, asset context and reporting. Explore the intended capabilities and the working public concept.

01 / CAPTURE & DRAWINGS

Make the plant
easier to understand.

Photos, walk-through video, drone imagery, scans and existing drawings can each contribute different evidence. The goal is a useful drawing with a traceable basis.

In research and local prototyping

Explore capture to drawing

Preserve the captureKeep original files, time references and capture conditions. Distinguish requested frames from the images actually recorded.
Locate the subjectOutline visible components and propose asset associations. Retain uncertainty when the plant tag or correspondence is unresolved.
Build the drawingMove from geometry proposals toward editable drawings. Retain original evidence, missing regions and revision history.
Check the dimensionsUse appropriate calibration, independent controls and an agreed acceptance method before relying on dimensions.

A convincing rendering does not establish measurement accuracy. The first field pilot must test the complete capture-to-drawing result.

02 / ASSET CONTEXT

Keep the history
with the asset.

A document name, plant tag, installed component and inspection location describe different things. The record needs to preserve those relationships over time.

Identity and revision mechanics prototyped locally

Source-linked identityRecord where an asset association came from. Keep proposed, disputed and reviewed relationships distinct.
Change over timeSeparate replacement equipment from a changed tag or drawing. Preserve the basis for previous observations.
Existing systemsBegin with read-only imports and a defined mapping. Validate a limited handoff before replacing any client system.

03 / FIELD INSPECTION

Give each program
the workflow it needs.

A turnaround, a recurring corrosion survey and an equipment inspection should share reliable records without being forced into the same checklist.

Business workflows to be defined with inspection leads

Scope and locationsKeep required items visible, including work that has not been observed or completed. Record the source of a location.
Evidence at the point of workAssociate observations, readings, notes and attachments with the correct asset and event.
Handoffs and correctionsCarry outstanding work across shifts and preserve who changed what. A correction should not erase the earlier record.
Field connectivityOffline capture, synchronization and conflict recovery are design requirements for the field product. This public demonstration is not an offline field application.

04 / REPORTING

Less rebuilding.
More reviewing.

Use the recorded evidence to assemble a draft, with clear links back to the source and explicit gaps for the reviewer.

Try the report example

Traceable draftsCarry asset context, observations and source references into the report. Keep entered narrative distinct from original records.
Revision-aware reviewA changed source or drawing may invalidate an earlier review. Preserve the history and identify what needs another check.
Client deliverablesDefine the required template, drawing format and recipient acceptance criteria with each program. Export fidelity and presentation both matter.
Professional decisionsKeep engineering assessment, inspection acceptance and signatures with the appropriately authorized people.

05 / AI ASSISTANCE

Useful assistance.
Visible evidence.

The intended assistant helps find records, compare revisions and prepare drafts. It should show the basis for a suggestion and say when the supplied evidence is insufficient.

Live AI integration planned; public example is scripted

Explore the assistance example

Find the relevant sourceSearch approved records in context, with references to the specific evidence used.
Spot inconsistenciesPropose checks for conflicting tags, missing items and changed reports. A suggestion should remain reviewable.
Draft with restraintSupport narrative preparation without inventing readings, findings, signatures or evidence of completed work.
Keep authority explicitLimit access by the user's scope and keep consequential actions behind the appropriate review.

A PRACTICAL START

Prove the useful part first.

Plan a bounded pilot

The long-term direction is broad. The first commercial proof should be specific: a defined area, agreed drawings and reports, independent quality checks and a complete comparison of delivery effort.

DIFFERENT PROGRAMS, SHARED RECORDS

The workflow follows
the inspection program.

These are proposed operating patterns for the inspection lead to define with the client. One turnaround example does not define the whole product.

Corrosion surveys

Bring together circuits, inspection locations, drawing revisions and recorded measurements. Keep the location identity, method and measurement history available for the qualified assessment.

First proof: less drawing and reconciliation effort for the same accepted survey scope.

Turnarounds

Carry the work pack, inspected items, incomplete work and review across shifts. Keep repair decisions and release authority connected to the specific work performed.

First proof: fewer handoff gaps and less report rebuilding at closeout.

Recurring equipment inspection

Connect the equipment record, previous findings, current scope and follow-up work. Separate a replaced component from a changed tag or a newer drawing.

First proof: faster retrieval and an accurate, usable history.

Plant documentation

Use capture to improve plant context and proposed drawings. Keep visible geometry, asset identity, process connectivity and engineering acceptance as separate questions.

First proof: a recipient can locate the required subject and verify the drawing’s basis.

Inspection scope and acceptance remain program-specific. API’s description of API 570 illustrates the breadth of in-service piping work; this site does not implement or certify compliance with that code.

A PATH TO BECOMING THE WORKING SYSTEM

Earn the transition.
Keep the history.

Replacing a client’s system is a data, workflow and operating change. The proposed sequence makes each step reviewable.

Map the records
Identify systems, exports, asset identifiers, drawings, measurement units, owners and historical revisions. Record missing or disputed relationships.
Prove the import
Start read-only. Reconcile counts, exact files and important relationships. Review exceptions with the owner instead of silently merging them.
Run in parallel
Deliver one agreed scope through both processes. Compare outputs, corrections, review effort and the complete cost of accepted work.
Agree the cutover
Validate permissions, historical access, exports, recovery and support. Name the system of record and test the return path before expanding.

CAPABILITY STATUS

See what you can use
and what comes next.

Area	Available to explore	Required before operational use
Capture & drawings	Fictional capture walkthrough and downloadable pilot plan.	Real media processing, field controls, editable output and agreed accuracy.
Reporting	Editable fictional drafts, revisions, source comparison and downloads.	Client templates, live evidence, authorized review and release.
Field inspection	Example asset and evidence navigation.	Program workflows, device/offline qualification and measured field usability.
AI assistance	Scripted source-linked questions and responses.	Live models evaluated on relevant records, permissions and failure cases.
System transition	A proposed import, parallel-run and cutover approach.	Chosen source system, reconciled data, operational support and tested recovery.
Business value	Complete-cost worksheet and correction sensitivity.	Comparable accepted field results and recorded delivery costs.

Define the first proof Read the research behind the direction

One plant record.Every stage of the work.

Make the planteasier to understand.

Keep the historywith the asset.

Give each programthe workflow it needs.

Less rebuilding.More reviewing.

Useful assistance.Visible evidence.

Prove the useful part first.

The workflow followsthe inspection program.

Corrosion surveys

Turnarounds

Recurring equipment inspection

Plant documentation

Earn the transition.Keep the history.

Map the records

Prove the import

Run in parallel

Agree the cutover

See what you can useand what comes next.