WorkflowShutdown, Turnaround & Outage

Engineering Document Review

Engineering document review that puts each flagged turnaround record beside its source page, lets an engineer keep, retire or send it back, and finds the documents the same ruling covers.

See the demo Book a demo

Follow one cyclone job pack from flag to family ↓

The problem

Engineering document review, one old PDF at a time

A flag says a record might be out of date. It does not say whether it is. Some old job packs are still the best method the plant has; others describe a cyclone set or a valve that was replaced years ago, and only an engineer who knows the unit can tell which.

So engineers open the scan in one window, the change log in another and the drawing register in a third, between planning meetings. Their reasons rarely get written down. And a clean, unflagged record about changed equipment never reaches an engineer at all, so it would move into the new system untouched.

Built forTurnaround engineersLead engineersRecords leadsDocument control supervisorsAuditors

The Problem Today

A flag is only a question, and engineers answer it one PDF at a time, in several windows, with little record of why.

2,954: engineer hours to judge the flagged documents by hand our estimate

Opened by hand for each document

Scanned PDF
Change log
Drawings
Work orders

Old is not obsoleteSome packs from past turnarounds are still the best method
Clear documents slip byNobody reads a clear record about changed equipment

The Solution

Source beside each fieldFields drawn on the page; a faded tag is marked for a person to settle
A correction, a new answerFix the tag and the agents search again, then cite what changed
Siblings lined up with rulesThe same reason across flagged and clear documents; history left out
A second engineer signsThe lead opens the doubtful ones and a sample, and signs rules for the rest

Built-in controls

Agents propose, engineers rule
Maker and checker are two different people
Retired is archived; deletion needs a person

What You Get

The new turnaround system starts from history an engineer has ruled on, with the reason behind each record.

788: engineer hours for the whole review on the bench our estimate

A reason on each rulingIn the engineer’s own words, with both names beside it
Rulings that disagree surfaceTwo answers on one unit go to a lead to settle
Evidence for an auditorWho ruled, why, and from which page

One engineer, one morning

An engineering document review process for one regenerator job pack

A refinery is ruling on 35,447 flagged turnaround documents before they move into a new turnaround system. This morning a static equipment engineer opens an old regenerator cyclone repair pack.

demoThe plant, its people and the document counts are sample data.

01Morning
A faded cyclone tag the agent will not guess, read at 71%
Turnaround engineer
The pack opens with its cover page on the left and every field drawn on it, each with a confidence. A register note says the cyclones were replaced under a plant change, so the pack was flagged. The cyclone tag reads CY-1307, the last digit faded, and no change record names it. The agent asks the engineer to settle the tag first.
02Morning
35,447 documents need an engineer, in seven waves
Turnaround records lead
The queue holds every flagged document by unit and reason: potentially obsolete, incomplete or low confidence. Waves go out to 22 engineers, each giving it 10 hours a week. The queue router has spotted that this packet is past its wave clock because a plant change was traced, and that one family accounts for 132 of the 412 left.
03Morning
The drawing on page 4 says CY-1301
Turnaround engineer
The engineer opens the general arrangement drawing cited on page 4. Its title block names the cyclones on the regenerator and the arrangement of eight two-stage sets. The faded digit on the cover is a 1, so the low-confidence 7 had sent the change-record search to the wrong equipment. The engineer uses the drawing’s value.
04Morning
With the tag fixed, the agents find the change record
Turnaround engineer
The correction is saved with page 4 as its source, and the agents read again. Now the change record turns up: the cyclone set was replaced after 20 years in service, with a new head and 10 sets. This pack repairs sets 1 to 8 through a door sheet, on hardware that is gone. The agent proposes retire, at 94%.
05Morning
A door sheet rigging method, written for hardware that is gone
Turnaround engineer
Page 7 holds the rigging method the agent flagged: cut the door sheet, rig new diplegs and hangers for sets 1 to 8, one set per shift. A handwritten note adds two rigging shifts on site. The method no longer fits the new head. The completed records and the overrun note are history worth keeping.
0610:43
Retire the method, keep the history, and wait for a second name
Turnaround engineer
The engineer takes the proposal and signs its reason: the cyclones were replaced, this pack repairs the old sets, the method no longer fits; as-found notes and hours stay as history. Nothing moves yet. The ruling waits for a lead engineer, and the bench already counts 212 other documents that may share it, 81 of them clear.
0710:45
212 siblings: 131 flagged, 81 clear, 9 the agent is unsure of
Turnaround engineer
The sibling finder lines up drawings, job packs, take-offs, blank hold-point plans and schedule files written for the old set. Inspection findings and completed test records are left out of a method ruling. Four written rules say what applies to whom, and the screen says which documents a lead must open: the unsure ones, plus a random sample.
0811:20
21 must be opened one by one before the lead can sign
Lead turnaround engineer
The lead engineer works from a strip of the family. Each must-open document appears with its page and why it is in the sample, and she agrees or takes it out. Two are open so far. For the rest she will sign the written rules, each with its count, and none of it counts until she does.
09Noon
Where 466,654 documents end, and 788 hours instead of 2,954
Turnaround records lead
The outcome screen follows the whole estate: what migrates today, what is retired to the archive, and what is still undecided. Clear documents retired with a family are counted on their own line. Our estimate for the whole review is 788 engineer hours on the bench, against 2,954 by hand, and the final list is released only when nothing is undecided.

Which ruling a record gets, and why

Three documents on the same screens, three different answers.

Document	What the engineer found	Ruling
Regenerator cyclone repair pack	The cyclone set was replaced; the method fits hardware that is gone	Retire the method, keep the history
Reactor effluent exchanger pack	Same equipment, same pack number, a later turnaround	Keep, as the equipment’s history
Scan with a water-damaged page	A second scan failed, and the page cannot be read	Sent back, with a decision for the engineer

demoSample data, from the working solution.

Around the bench

Sent back, overnight preparation, workload and every ruling with its reason

Six more screens the records lead, the leads and auditors work from.

Documents sent back from engineering document review: pages missing, signature missing, scan unreadable, each with a person and a clock — **Sent back**Each document an engineer could not rule on yet, with a named person, a clock and where it stands.

Overnight preparation of the next documents for each engineer, with the plan, last night’s counts and what each agent may never do — **Ready by morning**Overnight the agents read the next documents in each queue, so each bench opens on a reason and a proposal.

Human in the loop document review workload by team: first rulings waiting, rulings made, hours, minutes a ruling and changes by a checker — **Workload and quality**Rulings by team, minutes a ruling and how often a checker changed one, with the router’s proposed moves.

Reassigning turnaround documents by discipline, such as instrument loop sheets moved to instruments, each move approved by the records lead — **Reassign by discipline**Documents in the wrong discipline’s queue, why the router thinks so, and the records lead’s approval to move them.

Engineering judgments list: keep and retire rulings with reasons and checkers, and a consistency check that found two rulings that disagree — **Engineering judgments**Each ruling in the engineer’s own words, who checked it, and two rulings that disagree, flagged for a lead who signed neither.

Turnaround document control audit trail: a field corrected, a ruling made, siblings proposed and sent to countersign, each line named — **Audit trail**Corrections, rulings, countersignatures and agent steps, newest first, each line naming who acted.

demoSample data, from the working solution.

Obsolete is an engineer’s word, and agents never say it

The agents read, match and line up documents. Engineers and leads make these calls.

No agent rules a documentThe flag explainer proposes keep, retire or send back with its sources. An engineer decides.

A faded value is not guessedBelow the confidence line, the field waits for a person, and no proposal is made on an unsettled field.

No record found is not nothing changedWhen the change-record matcher finds nothing, it says so, and the engineer weighs it.

History stays out of method rulingsInspection findings, completed test records, cost records and lessons learned are never swept into a family.

Retired is archivedA retired document goes to the archive with its reason. Deleting anything needs a person.

The agents

Seven agents match, explain and route, and none rules on a document

Each hands to a named person when its part is done.

Field reader

Reads fields and draws them on the page with a confidence.

Never guesses a faded value

Flag explainer

Writes a plain reason and a proposal, with sources.

Never rules
No proposal on an unsettled field

Change-record matcher

Checks the equipment against change records, maintenance history and the drawing register.

Never treats no record found as nothing changed

Sibling finder

Finds documents the same reason applies to, flagged or clear.

Never applies a ruling
Never puts findings or test records in a method ruling

Queue router

Assigns by discipline, watches clocks and proposes moves.

Never sends a ruling to its own maker

Consistency checker

Runs blind re-checks and finds rulings that disagree.

Never overrides a signed ruling
Never used to score people

Evidence packager

Builds the audit export.

Never changes a record

What turnaround engineers ask about engineering document review

What is engineering document review in a turnaround records migration?

Engineering document review is where an engineer decides whether a flagged turnaround record is still true before it moves into a new system. Here each document opens beside its source page with its fields drawn on it, the agent’s reason and proposal sit beside it, and the engineer keeps it, retires it or sends it back. A lead engineer countersigns.

How is an obsolete document review different from deleting duplicates?

A duplicate is a copy. An obsolete document is one whose content no longer fits the plant, such as a repair method for equipment that was replaced. Only an engineer can rule on that, and a retired document is archived with its reason, never deleted by an agent.

What happens to clear documents about changed equipment?

When an engineer retires a document because the equipment changed, the sibling finder lines up the other documents the same reason applies to, including clear ones nobody flagged. The lead engineer opens the unsure ones and a random sample, and signs written rules for the rest.

Does an engineer still check every document?

Every flagged document gets an engineer’s ruling, alone or as part of a family. In a family, the lead opens what is unsure and a sample, and the rest go under written rules that state their counts. The estimate of hours assumes exactly that.

How does this fit our turnaround document control?

Documents come from the records classification step before it and go on to data migration after it. The records lead runs the queue, moves work between disciplines and releases the final list only when nothing is undecided.

Who can see what an engineer decided, and why?

Anyone with access, including an internal auditor with a read-only role. Each ruling carries the engineer’s reason in their own words, both names, the pages they opened and the documents it covers, and two rulings that disagree go to a lead who signed neither.

Shutdown, Turnaround & Outage

Bring one packet
of flagged job packs.

We’ll put each beside its source page and show you the family a single ruling would settle.

Book a demo Browse solutions

Engineering Document Review

Engineering document review, one old PDF at a time

The Problem Today

The Solution

What You Get

An engineering document review process for one regenerator job pack

A faded cyclone tag the agent will not guess, read at 71%

35,447 documents need an engineer, in seven waves

The drawing on page 4 says CY-1301

With the tag fixed, the agents find the change record

A door sheet rigging method, written for hardware that is gone

Retire the method, keep the history, and wait for a second name

212 siblings: 131 flagged, 81 clear, 9 the agent is unsure of

21 must be opened one by one before the lead can sign

Where 466,654 documents end, and 788 hours instead of 2,954