P&ID vs PFD.
A process flow diagram, PFD sketches process intent. Major equipment, principal streams, mass and energy balance. A piping and instrumentation diagram, P&ID is the working document. Every instrument, every pipe spec break, every relief device, every interlock. PFDs are read. P&IDs are operated against.
What P&ID vs PFD means.
Both documents describe the same physical plant, but at different levels of resolution and for different audiences. The PFD is a communication tool. It shows what the process does and why. It carries stream flow rates, temperatures, pressures, and compositions, often in tabular form on the same sheet. Equipment is shown schematically without physical detail. Instruments appear only as generic blocks representing major control schemes. The P&ID is a specification tool. It commits to every tag number, every pipe specification, every relief valve, every block valve and bypass, every instrument air supply, and every interlock signal path. The audience is the team that will build, commission, and maintain the plant. Errors in the PFD indicate process design problems. Errors in the P&ID cause physical construction mistakes, incorrect PLC configurations, and failed FATs.
Where each lives in the engineering lifecycle
PFDs appear during conceptual design and FEED. They survive into operations as a high-level reference for tours, troubleshooting briefings, and incident reviews. P&IDs appear during detailed engineering, get marked up during construction and commissioning, and become the controlled document under MOC for the life of the plant. A revision of the PFD is a process intent change. A revision of the P&ID can be a single instrument tag change. On most projects the PFD is frozen after FEED while P&IDs continue to accrue revisions through startup and into ongoing operations.
What each document shows
PFD contents. Major equipment items with reference numbers, primary process streams with flow direction, heat and material balance data, often as a table on the drawing, major control loops represented as a single block, utility connections shown at a summary level. P&ID contents. Every piping run with line number and pipe specification, every instrument with ISA 5.1, or project-standard tag, all manual valves and blinds, equipment nozzle designations, instrument air and electrical supply connections, interlock logic references, relief valve and safety device settings, off-page connectors for multi-page sets.
How line specifications work on each document
PFDs carry stream numbers and design conditions, temperature, pressure, phase. They do not encode corrosion allowances, insulation class, or pipe schedule. P&IDs carry the full line designation. Nominal bore, fluid service code, material class, insulation type, and heat trace flag, all encoded in the line number or in a piping class note attached to the line. A commissioning engineer can read a pipe class directly off a P&ID. The PFD tells them nothing about what grade of stainless was used.
Common confusions
Some companies issue simplified P&IDs for operator training that look closer to a PFD. Others draw mechanical flow diagrams that sit between the two. The terminology is not perfectly consistent across operating companies. The functional distinction holds. If a document carries every tag, it is a P&ID. If it omits instrument tags in favor of process clarity, it is a PFD or a derivative. ATEX and SIS reviews are scoped off P&IDs, not PFDs, because the PFD lacks the instrument and interlock detail those reviews require.
Downstream documents that trace back to each drawing
PFD downstream. Process design basis, equipment data sheets, HAZOP node list. P&ID downstream. Instrument index, I/O list, cable schedule, marshalling schedule, commissioning loop sheets, SIS cause-and-effect matrix, MOC records. The P&ID is the root of most controls-engineering documents. Any error in the P&ID propagates through all of them.
Common questions
Can you build an I/O list from a PFD.
Should the PFD and the P&ID match.
At what phase of a project does a P&ID supersede the PFD as the working document.
Which document is used as the basis for a HAZOP.
Do both documents require revision control.
Run it on your drawings.
Upload a drawing set, get every document populated and classified, export to the format your team uses.