Brownfield data migration from legacy P&IDs.

For engineering firms and EPC contractors delivering brownfield work, this decoding phase is the unbillable overhead that precedes every billable hour — and the quality of the decoding directly determines the quality of every downstream deliverable.

Today's brownfield migration workflow

The typical brownfield project kicks off with a drawing package from the owner. A representative package might include:

• Original FEED P&IDs from the 1990s, as TIFF or PDF scans of printed originals.
• Detailed engineering P&IDs from the early 2000s in native CAD export formats from a now-deprecated tool.
• Post-revamp drawings from multiple later projects, each from a different contractor with a different symbol library.
• As-built drawings of varying quality, some with field redlines never formally incorporated.
• A partial MOC log that may or may not reconcile to the drawing archive.

The engineering team's first task is to determine what they actually have:

• Which drawings are current? Which are superseded?
• Which drawings use which symbol conventions? Which tags follow which conventions?
• Where are the gaps — drawings that exist in the index but not in the archive, drawings that exist in the archive but not in the index?
• Which field modifications have been documented? Which haven't?

This work typically consumes the first one to three months of the engagement before any design work can begin. It is the silent tax on every brownfield revamp.

How Armeta transforms brownfield data migration

Armeta's extraction engine reads any PDF P&ID — regardless of source, age, or format — and produces structured engineering data. For brownfield data migration, the typical engagement:

1. 01Archive ingest — the full drawing package from the owner is ingested, including scanned originals, native CAD exports, and as-builts.
2. 02Per-drawing extraction — each drawing is processed to produce structured equipment, line, instrument, and connectivity data.
3. 03Cross-drawing connectivity — off-page connectors are reconciled across the archive, producing a facility-level engineering graph.
4. 04Revision reconciliation — where multiple revisions of the same drawing exist, Armeta's compare stage identifies the deltas and produces a unified current-revision graph.
5. 05Gap identification — drawings referenced by off-page connectors that don't exist in the archive are flagged for owner inquiry.
6. 06Deliverable — a structured engineering graph of the entire inherited archive, delivered as API, JSON, or structured Excel.

The engineering outcome

For a typical mid-size brownfield revamp with 800 P&IDs in the inherited archive:

• Manual archive decoding: 2–4 months of engineering work before design begins.
• Armeta-supported archive decoding: 4–6 weeks, with structured output feeding directly into detail engineering.
• Engineering hours reclaimed: thousands per project.
• Revamp scope lock-in: earlier, with fewer surprises later in execution.
• Change order defense: improved, because the baseline engineering graph is structured and defensible.

The strategic importance for EPC contractors

On lump-sum EPC contracts, brownfield engagements carry disproportionate execution risk. The baseline inherited drawings define what the contractor assumed; deviations from that baseline become change orders or absorbed cost. A structured, defensible baseline — produced at the start of the engagement rather than reconstructed during disputes — materially shifts the risk profile.