If you ask experienced piping engineers which document review task they dread most, line list reconciliation against the P&IDs comes up with remarkable consistency. Not because it requires sophisticated judgment, but precisely because it does not. It is a methodical, time-consuming comparison of values that should match but often do not, for reasons that are rarely surprising and almost never easily fixed in a single pass.
Understanding why this task is reliably painful, and what can be done to reduce its cycle time, starts with understanding the structural relationship between a line list and a P&ID.
The Line List as a Derivative Document
The line list is not an originating document. It does not define operating conditions, pipe sizes, or fluid services. It records them, aggregated from P&IDs and process data sheets, organized by line number. For each pipeline in the plant, the line list captures: the line number (size, material code, service code, sequence), fluid service, design and operating pressure and temperature, insulation specification, line class, the P&ID drawing reference, and sometimes pipe support requirements.
The P&ID is the originating source for the line attributes. When the P&ID says a 6-inch line carries a certain fluid at a certain pressure and temperature, the line list entry for that line should reflect exactly those values.
The problem is that the line list is created and maintained by the piping discipline, while the P&IDs are maintained by process and instrument engineers. A P&ID revision that changes an operating condition on a line does not automatically update the line list. The piping engineer maintaining the line list needs to be notified of the change, or needs to perform a periodic check against the current P&ID revision, to keep the two in sync.
The Five Most Common Discrepancies
In working with engineering teams on this problem, the same categories of discrepancy appear repeatedly:
Operating temperature mismatch. The P&ID was revised to update an operating temperature after a heat and mass balance refinement, but the line list was not updated. This is the most common category. The line list may still reflect the previous HMB revision's value, and depending on how many HMB revisions have occurred, the gap can be significant enough to affect the pipe stress or insulation specification.
Design pressure discrepancy. Less common than temperature mismatches but higher consequence. A P&ID revision that changes the rated design pressure of a section of piping needs to flow through to the line list, which determines the pipe class (and therefore wall thickness, flange rating, and valve specification). A missed design pressure change can result in under-rated piping or over-specified fittings, neither of which is discovered cheaply.
Line size inconsistency. P&ID revisions sometimes rescale a line based on updated hydraulic calculations. If the line number convention includes the nominal bore (as many do, e.g., 4"-P-3014 for a 4-inch process line), a line size change requires both a line list update and a line number change on every document that references that line. This is a cross-document cascade that is structurally similar to a tag number change.
New lines without line list entries. During detailed design, P&IDs are sometimes revised to add new auxiliary lines (drain connections, vent lines, instrument connections) that were not in the FEED P&ID and were not therefore captured in the original line list population. The piping discipline may not receive explicit notification that these lines were added, and the line list can end up incomplete relative to the current P&ID revision.
Fluid service description divergence. Fluid service codes and descriptions are defined in the project piping specification or material selection diagram. If the process team updates the fluid service classification for a stream (for example, reclassifying a utility steam line from medium-pressure steam to high-pressure steam based on revised steam balance data), the line list entry needs to be updated along with the pipe class specification. This type of change is often flagged in the process data sheet revision but not always explicitly communicated to the piping line list.
Why Manual Reconciliation Takes as Long as It Does
A typical line list for a mid-scale gas processing or petrochemical facility will contain between 300 and 1,200 line entries. A reconciliation against the current P&ID set involves checking each line entry against the corresponding P&ID drawing and confirming that the recorded attributes match. The P&ID for a complex section of plant may contain 50 to 80 line numbers on a single sheet. At that density, confirming a single attribute value for a single line requires finding the line on the drawing (which may require zooming into the PDF several times), locating the process conditions notation, and comparing it to the line list cell value.
An experienced piping engineer doing this carefully takes approximately 15 to 25 seconds per line per attribute. For a 600-line list checking three key attributes (temperature, pressure, line class), the raw comparison work is 7 to 12 hours. Add navigation time between documents, time to resolve ambiguous notations on the P&ID, and time to flag and document discrepancies for follow-up, and the realistic duration for a careful reconciliation pass is two full working days.
That two-day estimate assumes the P&ID PDFs are well-organized, the line numbers are clearly legible, and the engineer doing the work is familiar with the project's notation conventions. On projects where the P&ID set runs to 100 or more sheets and has been through multiple revision cycles, the time scales proportionally.
The Timing Problem: Reconciliation Is Done Too Late
In most project schedules, a formal line list reconciliation against the current P&ID is performed at discrete milestones: before IFD (Issued for Design), before IFC, and before handover. Between milestones, the line list and P&IDs may drift apart as each is independently revised.
The issue is that decisions made using the line list between formal reconciliation points can be based on data that has already been superseded. A piping stress engineer performing a stress analysis uses the operating temperature and design pressure from the line list. If those values are outdated by one P&ID revision, the stress analysis is performed on the wrong basis. The error may be small enough to be within safety margins, or it may require rework after the next reconciliation catches it. Either way, the decision to use unreconciled line list data is invisible at the time it is made.
What a Continuous Cross-Reference Would Change
The structural solution to the line list reconciliation problem is not a better reconciliation process at milestone points. It is a system that tracks the state of each line attribute in the line list relative to the current P&ID revision continuously, flagging discrepancies as they are introduced rather than accumulating them between formal checks.
This requires two capabilities that are not straightforward to implement: reading attribute values from P&ID PDFs (which are graphical documents, not structured data), and maintaining a mapping between line numbers in the line list and their graphical representation on P&ID drawings. The first capability requires document parsing with engineering-domain understanding of P&ID notation conventions. The second requires building and maintaining a cross-reference that links line entries to their source drawings and sections.
These are the technical challenges that the SnapScale extraction layer addresses directly. When a P&ID is revised and uploaded, the system re-reads the affected sections and updates the cross-reference for every line that appears on those sheets. The line list entries for those lines are then flagged for review if the extracted P&ID attribute differs from the current line list value. The reconciliation becomes an ongoing check rather than a periodic event, which means that discrepancies are surfaced before they affect downstream work rather than after.