SystemEngineering Data, Tags & Documents

As-Built Reconciliation

As-built reconciliation that names each disagreement between five records, plans the shortest field walk to settle the ones that matter next, and leaves each ruling to an engineer.

See the demo Book a demo

From the map to a registered change, in one walk ↓

The problem

As-built documentation that each looks fine alone

Shutdowns change a plant faster than its records follow. A valve is swapped like for like, a transmitter gets a new range, a line is rerouted, and the redline goes into a site binder. Years later the drawing, the line list, the datasheet, the certificate and the work orders each look fine and still disagree.

Nobody can tell from a desk which one is right. The usual answer is a spreadsheet of mismatches walked in tag order, and people find the gap when they write a permit or plan an isolation, which is the worst time to find it.

Built forAs-built engineersDiscipline leadsWalkdown techniciansChange coordinatorsOperations superintendents

The Problem Today

Drawings, registers, datasheets, certificates and field records drift apart, and each looks fine alone.

Among the five sources

Drawings
Registers
Datasheets
Field work

Spelling buries substanceOne item spelled two ways hides the real conflicts
Truth in old bindersHand markups that never reached the drawing

The Solution

Five sources comparedEach tag read each night, with spelling split from real conflicts
One walk, many conflictsGrouped by where a person stands, ranked by what is used next
Photos come back as proofAgents match each photo and ask about anything no record carries
An engineer settles each oneA second person checks safety items, and the fix goes to change control

Built-in controls

Agents never rule or change a record
The person who settles never countersigns
Each drawing fix goes through change control

What You Get

Engineering teams settle what is used next first, with the evidence from one walk and a change for each fix.

280: hours of walking for the sample terminal's field conflicts our estimate

One walk, a cluster settledStops grouped by where a person can stand
Binder markups foundHandwriting read and shown to a person
Fixes that reach the drawingEach ruling becomes a change, tracked to issue

One walk at Manifold 4

As-built reconciliation on Route 47, the walk that found a 41st conflict

A marine terminal with five record sets that disagree 11,940 times. One manifold matters most this week, because a tanker loads at the jetty it feeds.

demoEverything on these screens is sample data: terminal, tags, binders and people. The photos are drawn for this walk.

01Morning
11,940 conflicts on a plot plan, and Route 47 goes first
As-built engineer
The terminal is drawn as its plot plan, each area shaded by how often its five sources disagree. Manifold 4 is darkest, and the walk planner ranks Route 47 first: one walk answers 40 conflicts, three of them safety items, on equipment that feeds a tanker loading this week, with a permit open today.
02Morning
Three stops, 40 conflicts, about 2.6 hours, inside one permit
As-built engineer
The route page draws the stops on the manifold's lines and lists what each one should answer: a shutdown valve's fail position, a relief valve's set pressure, a blind's position. It names what to bring, an intrinsically safe tablet, and the rule for the walk: stay on walkways, nothing opened or touched.
03On the walk
Stop 1: what to look for, on the tablet she carries
Walkdown technician
The technician sees the stop, the items to photograph and a prompt to point at each tag. The walk runs inside the permit window shown at the top. She photographs what is in view and does not open or touch anything. Each photo goes back to the desk with the stop and the time it was taken.
04On the walk
The photo shows tubing to the relief valve pilot that no record carries
Walkdown technician
As her photos come back, the photo reader matches each item to its conflict, reads the plates it can see clearly, and asks one thing more: something runs to the relief valve's pilot that none of the records list. Can she follow it and photograph both ends? She can also answer that it is not safe to reach, and it stays open as a safety finding.
05At the desk
Five records agree with each other, and the field says otherwise
As-built engineer
The new conflict sets the five sources side by side: the drawing, the register, the datasheet, the certificate and the maintenance tasks all have the pilot sensing at the valve's own inlet. The photo shows about 38 ft of tubing from the header upstream of the shutdown valve, with a needle valve open and no lock or seal.
06At the desk
A hand markup in Binder 27 says the sensing was moved, never drawn
As-built engineer
The binder reader searched the site binders and found a hand markup on an old print: pilot sense moved to a header tap to cure chatter, tube with needle valve, and nothing on CAD yet. It reads the handwriting at 68% and asks the engineer to read it herself. A markup counts as evidence; on its own it does not become an approved record.
07At the desk
She rules field shows the current state: field change never recorded
As-built engineer
The ruling means the records must follow the plant. It does not mean the plant is acceptable as it stands. What the agent cannot say is said on screen: whether that needle valve should be open or locked, and whether the relief still protects the header. Those go to an engineer and the change review.
08Same day
The tanker decision is operations', and the screen proposes none
Operations superintendent
Because the line feeds a relief valve protecting the loading header, a dated decision goes to the terminal operations superintendent: load as planned, load with conditions, or hold the loading, under her own procedures. The product shows the evidence and stops there.
09Same day
The lead opens the photo and the binder page before he countersigns
Discipline lead
The second person sees the ruling, the five records and the evidence, and opens both the photo and the binder page. Safety items are checked one at a time. Only then does he countersign, and the change drafter writes a change from the signed ruling for the coordinator to register.

One 2.6-hour walk brings back evidence for 41 conflicts

The 40 the route was planned for, plus the one found by walking.

Found by walking, not by comparing	1
Safety items, each to settle and check on its own	3
Field changes that skipped change control	7
Rows in 4 piles, checked on a sample	30
Conflicts answered by Route 47	41

demoSample data, from the working solution. Each safety item gets its own change; the field changes share one, and the record corrections another.

Around the walk

Changes, walks and binders behind as-built drawing verification

What the change coordinator, the planner and the auditor open after a route comes back.

Management of change for an unrecorded sensing line: drafted from the signed ruling, registered, with the reviews it needs — **Changes**The signed ruling becomes MoC-2026-0612: redline the drawing, add the line, update the datasheet and maintenance tasks. It needs two reviews and proposes no design answer.

P&ID walkdown routes ranked by next use, with conflicts, safety items, stops, hours and permit state for each — **Walks ranked**86 walks cover 5,160 field conflicts, about 280 hours. Walks that can start first lead: a permit today, then the next vessel use, then safety items.

Pattern sign-off for spelling conflicts: patterns such as a missing hyphen, each with sampled rows to check — **Pattern sign-off**4,140 conflicts that are one item spelled two ways, grouped into patterns. Each is signed on its own sample, with its bound stated.

Site binder pages searched for a tag, with handwritten markups marked and a page picked to read — **Site binders**412 binders of scanned pages, outside all five sources. Pages with handwriting are marked, and markups stay evidence rather than approved records.

The five record sources compared each night, with what each holds, when it was last read and its odd-one-out count — **The five sources**Drawings, registers, datasheets, certificates and field records, read only, each with what it holds, when it was last read and files held back.

Audit trail of one field walk from photos to ruling, countersignature and the registered change — **Audit trail**Every action in order, by a person or an agent: photos taken, the binder found, the ruling, the opened evidence, the countersignature and the change.

demoSample data, from the working solution.

Who reads the records

Six agents compare records and photos, and none of them rules

Their findings land with the as-built engineer, who decides.

Source reader

Reads the five sources into one view per tag, with page and line.

Read only
Never fills a gap by guessing

Conflict finder

Compares each tag, names each disagreement and separates spelling from substance.

Never says which source is right

Walk planner

Groups conflicts by where a person stands and draws the shortest walk for what matters most.

Never sends a walk
Never plans one without a permit window

Photo reader

Reads photos, matches them to conflicts and flags what no record carries.

Never says whether something is safe

Binder reader

Searches scanned binders and reads handwriting.

A markup is evidence, never an approved record

Change drafter

Drafts a change from signed rulings.

Never registers a change or issues a drawing

Five record sets, each read only, each a different system

A photo and a binder page sit beside them as evidence, and neither counts as a sixth source.

DrawingsPiping and instrument diagrams and isometrics, in the document system

RegistersThe tag register and the line list

DatasheetsEquipment and instrument datasheets

CertificatesCalibration, set-pressure and test certificates

Field recordsWork orders and inspection rounds in the maintenance system

What engineering teams ask about as-built reconciliation

What is as-built reconciliation?

As-built reconciliation brings a plant's records back in line with what is built. This as-built reconciliation compares drawings, registers, datasheets, certificates and field records each night, names each disagreement, and plans field walks so an engineer can settle them with evidence.

Do we still need a P&ID walkdown in tag order?

No. Conflicts are grouped by where a person would stand and ranked by what is used next, so one walk settles a cluster, and nobody walks the same manifold twice for neighbouring tags. The walk also catches what no record carries, as on the relief valve's sensing line.

Does it change the drawings?

No. The engineer rules, a second person checks safety items and field changes, and each fix goes through management of change before a drawing is issued.

What about the thousands of spelling differences?

They are grouped into patterns, such as a missing hyphen, and each pattern is signed on its own sample with its bound stated, so they do not bury the conflicts that matter.

Can it read old site binders and hand markups?

Yes. It searches scanned binders, reads handwriting with a stated confidence, and asks a person to read the page before relying on it.

What happens if a finding affects operations?

A dated decision goes to operations, with the evidence. The product proposes no answer; operations decides under its own procedures.

Engineering Data, Tags & Documents

Pick one area of your plant
and its five record sets.

We will show where they disagree, and the walk that would settle the ones you need next.

Book a demo Browse solutions

As-Built Reconciliation

As-built documentation that each looks fine alone

The Problem Today

The Solution

What You Get

As-built reconciliation on Route 47, the walk that found a 41st conflict

11,940 conflicts on a plot plan, and Route 47 goes first

Three stops, 40 conflicts, about 2.6 hours, inside one permit

Stop 1: what to look for, on the tablet she carries

The photo shows tubing to the relief valve pilot that no record carries

Five records agree with each other, and the field says otherwise

A hand markup in Binder 27 says the sensing was moved, never drawn

She rules field shows the current state: field change never recorded

The tanker decision is operations', and the screen proposes none

The lead opens the photo and the binder page before he countersigns