Build a master equipment list.
From a vendor datasheet binder and the P&ID set to a project asset register
Building a master equipment list is the engineering process of reconciling a vendor datasheet binder against the P&ID equipment scope to produce a single project register of every tagged equipment item. The master equipment list carries one row per equipment tag with type (pump, vessel, exchanger, column, tank, blower, compressor), service, capacity, design pressure and temperature, materials of construction, vendor, model, weights, dimensions, and a reference to the per-equipment datasheet. The master equipment list is the document handed to procurement, commissioning, and the operations CMMS or EAM (Maximo, SAP PM, Infor EAM) at end of job.
Inputs.
- +Vendor datasheet binder (PDF, often 200+ pages)
- +P&ID set
- +Existing equipment list (optional, for reconciliation)
Outputs.
- →Master equipment list with one row per equipment tag
- →Per-row datasheet PDF link (binder doubles as a lookup)
- →Cross-reference report: tags on P&ID with no datasheet, datasheets with no P&ID parent
- →Per-vendor comparison workbook (when multiple vendors bid the same equipment)
- →Export targets: Excel, CSV, JSON, asset-register import shape for Maximo / SAP PM / Infor EAM
| Source | Owner | What it carries |
|---|---|---|
| P&ID set | Process + I&C engineers | Equipment tag, service, P&ID page |
| Vendor datasheet binder | Mechanical engineers | Vendor model, materials, weights, dimensions |
| Pump and exchanger datasheets | Rotating-equipment specialist | API 610, API 682, TEMA type, performance |
| Package skid vendor docs | Project engineer | Parent skid, sub-equipment hierarchy |
| Final reconciliation | Project engineer | Single source of truth for asset register |
Step by step.
- 01
Upload the datasheet binder
Drop a vendor datasheet binder PDF into a workspace. Vendor-specific datasheet forms (Flowserve, Sulzer, John Crane, Alfa Laval, Kelvion) read into the canonical equipment-list column schema.
- 02
Upload the P&ID set
The P&ID set extracts equipment scope tagged from the drawing. Combined with the binder, the reconciliation surfaces tag-by-tag agreement.
- 03
Surface the cross-reference
Tags on the P&ID with no datasheet and datasheets with no P&ID parent flag for review. The bid-stage equipment scope locks down before the commercial number.
- 04
Handle package skids
Vendor-supplied skid drawings (lube oil consoles, BAS sub-skids, package compressor packages) extract with parent-skid attribution. Sub-equipment inherits the skid in the asset hierarchy.
- 05
Export to procurement and CMMS
Excel export drops into Aconex, ProjectWise, or SmartPlant Construction unmodified. The asset-register import shape feeds Maximo, SAP PM, Infor EAM directly.
Common questions.
Does this handle 240-page vendor binders?
Yes. Binders process as a single workspace; per-equipment datasheets extract into individual rows. Vendor-specific notation is preserved in a source-form column alongside the canonical mapping.
What about disagreement between two vendors bidding the same equipment?
Run each vendor's binder as a separate workspace, then export a side-by-side comparison on duty, NPSH, materials, and weights. The comparison surfaces where vendors interpreted the duty spec differently - usually the part that matters in the engineering decision.
Can this feed Maximo or SAP PM directly?
Yes. The Excel export carries the canonical column shape these systems import. Tag, type, vendor, model, and per-equipment metadata land in the correct CMMS field on import; the parent-skid relationship preserves the asset-tree hierarchy.
Start a workspace.
Upload the source documents, run the workflow, ship the document in the column shape the next consumer expects.