botminds.aiRequest a demo
SystemEngineering Data, Tags & Documents

EDMS Migration

EDMS migration for decades of engineering records: each wave rehearsed on copies, stale links answered before cutover, and a ledger that accounts for every record.

See the demoBook a demo
Follow one wave from its rehearsal to its close ↓
The problem

Go-live is when a planner finds the drawing link that opens nothing

Replacing an engineering document management system means moving decades of drawings, data sheets, inspection records and procedures out of old vaults, network shares and boxes of paper. A consultant exports lists into spreadsheets, a trial load or two runs, and the count is checked at the end.

A file the export skipped because its path was too long shows up months later, or never. Work orders and equipment records still point at old numbers, and nobody finds out until a planner clicks one before dawn. Because nobody can prove nothing was lost, the old system keeps running for years.

Built forMigration leadsDocument control managersInformation ownersMaintenance systems liaisonsRecords auditors

The Problem Today

Moves to a new engineering document management system lose track of records and leave links stale.

612 hrs
to walk one wave's 18,362 links by hand, at 2 minutes each our estimate
Each
test or inspection of process equipment must be on record published

Tracked by hand today

  • Drawings
  • Data sheets
  • Inspections
  • Paper boxes
  • Silent skipsAn export drops files and the final count hides it
  • The old system keeps runningNobody can prove it is safe to switch off

The Solution

  1. Waves on a calendarEach block of records is rehearsed before its freeze window opens
  2. Dress rehearsal on copiesAgents count, copy and fingerprint records before anything moves
  3. Links answered before cutoverA forwarding table gives each old number an answer
  4. A ledger that closesLeft equals arrived, held and retired, or the wave cannot be signed

Built-in controls

  • The owner opens each sampled record before signing
  • Agents never delete; retired means archived
  • Live links change only with liaison approval

What You Get

Teams switch off old systems with proof, and planners open the right drawing from the first morning.

  • Metadata fixed on the wayRevisions, units and tags corrected by approved rules
  • Held records stay visibleEach shows why it stays, whose it is and when it is due
  • Old numbers keep answeringMoved, held and retired records each give a link somewhere to land
One wave, rehearsal to close

EDMS migration of one refinery wave: 214,906 records out of the drawing vault

Wave 9 carries the hydroprocessing units' records out of the drawing vault. The freeze runs from Friday 6:00 PM to Monday 6:00 AM, and the rehearsal starts ten days before it, while there is still time to fix what it finds.

demoThis wave, its people and its record counts are sample data.

  1. 01Ten days out

    Eight waves closed with 0 missing, and Wave 9 is next on the calendar

    Migration lead

    The first screen is the whole program: 14 waves on a year calendar, each a block of records leaving a share, a vault or a box room, with a no-move band around the turnaround. Beside it runs the custody ledger: left, arrived, held, retired, missing. The last column has to read 0 before a wave can be signed, and Wave 10 already shows a date clash.

  2. 02Rehearsal 1

    Rehearsal on copies: 35 files missing and 26,871 links that would go stale

    Agents, for the migration lead

    The run copies every record and its revisions into a rehearsal copy of the new system. 204,083 arrive and match their fingerprints, 1,842 are held and 8,946 retired, so 35 are missing and the ledger refuses to close. The link walk finds 18,362 maintenance links, 6,092 drawing cross-references and 2,417 procedure links that point at the old vault.

  3. 03Before the freeze

    Three old numbers have two answers, and he settles each one himself

    Maintenance systems liaison

    The forwarding table holds one line for each old number, so a link nobody found still lands. 26,114 links land on a moved record, 612 on a held record and 145 on a retired one. One isometric became two sheets, one seal plan covered two pumps, one number held a vendor original and a plant copy. He settles those, opens three spot rows, then approves his 18,362 maintenance lines.

  4. 04Rehearsal 2

    The 35 arrive on a short path, and the ledger closes at 214,906

    Migration lead

    The rerun reads the skipped files on a short path, keeping each original name, and applies the approved table to the rehearsal copy. 204,118 arrived, 1,842 held, 8,946 retired, 0 missing. Every link lands in the rehearsal copy, and the screen says plainly that the live maintenance system has not been touched yet.

  5. 05Ledger check

    He opens one held record per reason before he countersigns

    Document control manager

    Held is fine; unknown is not. The wave page breaks the 1,842 held records into open changes, legal holds, unreadable files and records with no owner, and the 8,946 retired into past retention and exact copies. He opens a record from each group, sees why it stays or goes, and countersigns. The migration lead made the ledger, so she cannot check it.

  6. 06Owner sample

    Third of 40: the plant copy, Rev 2, sits where the vendor's Rev 5 belongs

    Information owner

    The sample of 40 takes every record changed by a rule or a person, then a spread by type. She opens them one at a time, old vault beside new system. On VD-2401-L the fingerprint does not match the vault file and the revision reads 5 against 2, with no rule to explain it. Pass stays grey: a record cannot pass with an unexplained difference.

  7. 07Owner sample

    One failed record reopens the whole wave's ledger, with its name on it

    Information owner, then the migration lead

    She fails it as a wrong revision. The ledger drops back to 1 missing and names VD-2401-L, and the plan marks Wave 9 reopened. The migration lead reloads it from the right file, which re-checks every record changed by a person or a rule and corrects 14 more. Then a rerun, a fresh ledger check and a new draw with a new seed.

  8. 08Freeze weekend

    212 records fail to load on a locked index, with the freeze clock running

    Migration lead

    With the go signed on a clean draw, the freeze opens and the load begins. The new system times out on a locked index and 212 records do not load. The plan shows Wave 9 with 212 failed and 212 missing in the ledger, and says the freeze ends Monday at 6:00 AM. She retries the 212 before anyone calls the load done.

  9. 09Last hours of the freeze

    Three live links opened by hand, then a close with four signatures on it

    Document control manager, then the information owner

    After the retry, the link walk on the live systems reports 204,118 arrived and 26,871 links answered. He opens three live links himself, a work order, an equipment record and a maintenance plan, and passes the check. She closes the wave. The record carries the ledger check, the go after opening 40 of 40, the live check and the close.

Wave 9 by the time it closes: 214,906 left and each one accounted for

The custody ledger for the hydroprocessing wave after the live check.

Arrived in the new system204,118
Held at source, each with a reason and an owner1,842
Retired to the read-only archive8,946
Missing0
Records that left the drawing vault214,906

demoSample data, from the working solution.

Around the wave

Long paths, old links, paper boxes and the vault's switch-off

Six more places the migration team and document control look while a wave moves.

The skipped filesEach file the export skipped, with its full path and length against the 260 characters the export can read, and a CSV of all 35.
Try an old linkVT-0048213 lands on TH-24-DWG-0417, the E-2417A bundle general arrangement. The vault copy shows a Moved banner and gets no new revisions.
One record's custodyCounted at source with its fingerprint, copied to rehearsal, cut over and arrived, with old number, new number and the work order linking to it.
Box rooms6,180 paper boxes at three sites. Two are not where the register says and one label does not match its pages; each stays on the ledger.
Metadata fixed on the wayRules for revisions, units, old tags and status, each approved after its examples were opened. 5,233 records filed as Miscellaneous still wait.
Switching off old systemsThe largest decision. One file store has its evidence, a clock and three people in turn; the vault switches off once, after the last wave.

demoSample data, from the working solution.

Three wrong records in the Wave 9 load that only the owner's sample shows

Each one passes the count. Each shows only when old and new are opened side by side, and none can pass while its difference has no rule behind it.

The plant copy for the vendor original

VD-2401-L loaded as Rev 2, the plant copy, where the vendor's Rev 5 belongs.

Sheet 2 under sheet 1's number

One isometric split into two sheets, and the second loaded under the first one's number.

A status that changed meaning

A drawing landing as Issued for use where its fix rule says In review.

demoSample data, from the working solution.

Four people stand between a wave and its close, and none checks their own work

The migration lead makes; three others check, approve and sign.

Migration lead
Sees
The plan, the rehearsal and what came back
Signs
Runs waves and cutovers, and corrects what the sample or ledger sends back
Maintenance systems liaison
Sees
The forwarding table and its two-answer groups
Signs
Approves the maintenance lines before any live link changes
Document control manager
Sees
Held and retired records, one per reason
Signs
Countersigns the ledger and runs the live check after the load
Information owner
Sees
Her sample, old and new side by side
Signs
Signs the go only after opening each record, and closes the wave
Records auditor
Sees
Every ledger, sample and decision on the trail
Signs
No signature: repeats a sample from its seed and exports evidence
The agents

Eight agents count, copy and walk links, and none can sign a wave

They do the counting, copying, reading and link walking. People approve, check, open and sign.

Wave planner

Drafts waves and freeze windows, and checks them for clashes.

  • Never sets or moves a date on its own
Source counter

Counts and fingerprints records at the source.

  • Read only; never writes to a source
Record mover

Copies records with their revisions to the rehearsal copy, then at cutover to the new system.

  • Never deletes
  • Never cuts over without a signed go
Metadata fixer

Reads title blocks and proposes fix rules with examples.

  • Never changes a revision it cannot read
  • Never marks a record as-built
Link finder

Walks links and drafts the forwarding table.

  • Never writes to the live maintenance system without the liaison's approval
Ledger keeper

Keeps left, arrived, held, retired and missing for each wave.

  • Never closes with a gap
  • Never retires a record on its own
Sample picker

Draws the owner's sample with a saved seed.

  • Never lets the maker pick
Box reader

Matches the box register, barcodes and title blocks.

  • Never declares a box lost

What document control managers ask before an EDMS migration

What is an EDMS migration?

An EDMS migration moves engineering records from old document systems, shares and paper into a new engineering document management system. Here it runs in rehearsed waves: each wave is copied first into a rehearsal copy, its links are walked, and a custody ledger shows every record as arrived, held or retired before anyone signs.

How do you prove nothing was lost in an engineering document migration?

Each wave has a ledger: left must equal arrived plus held plus retired, and a wave with any record missing cannot be signed. A skipped file is named with its reason, and the owner opens a sample of records side by side, old and new, before the go.

What happens to work order links that point at old document numbers?

The link finder walks the maintenance system, drawing cross-references and procedures before cutover and drafts a forwarding table with one line per old number. The maintenance liaison settles any number with two answers and approves his lines before a live link changes.

What about records that cannot move yet?

They are held, and each held record names its reason, its owner and its due date: an open change, a legal hold, an unreadable file or no owner. A held record stays in the old system with a banner, and an old link to it lands there.

Do you move paper boxes too?

Yes. Boxes are pulled in their own waves. The box reader matches the register, barcodes and title blocks, and a box that is not on the shelf stays on the ledger until it is found or a person accepts its loss.

Is metadata mapping part of the move?

Fix rules travel with the records: revisions written several ways, missing units, old equipment tags and statuses that mean something else now. Document control opens the examples behind each rule before approving it, and a record the agent cannot read keeps its old value.

When is it safe to switch off the old system?

When every wave that drew on it is closed and no record in it is still held. The switch-off has an owner, a clock, a sample opened by document control and a final signature, and the vault switches off once, after its last wave.

Engineering Data, Tags & Documents

More for engineering data, tags and records

All 11 solutions →
Asset Tag Management

One checked record per plant tag, with every value tied to its source.

1-min demoOil and Gas Document Extraction

One clean table from messy pages, with every cell tied to its place.

1-min demoEngineering Tag Data Extraction

Every value read, cited and tested against the others, before it loads.

1-min demo

Rehearse one wave
on a copy of your own vault.

Bring one unit’s records, and we’ll show its ledger, the links that would go stale and the owner’s sample.

Book a demoBrowse solutions