← All examples

PLEXUS EXAMPLE · 08

Equipment list vs datasheets

Six equipment items cross-checked across the register, two datasheets and the BoD: materials, duties and design conditions aligned, conflicts flagged.

Input

EQUIPMENT REGISTERACD-REG-0001

Master Tag Registers, Equipment sheet

Revision
Rev 0
Items
6
Scope
ACD-300-001 area
BASIS OF DESIGNACD-BOD-0001

Basis of Design & Operation/Control Philosophy

Revision
Rev 0
Sections
2.3, 3.6, 3.7
Used for
Duties, margins, materials
ACD-DS-E302-001Effluent condenser E-302
ACD-DS-V301-001Cold separator V-301

The source documents are not shown: registers and datasheets stay inside your project. The cross-check below runs on a hypothetical plant (ACD), presented the way consistency results arrive.

What Plexus does

  1. 01Reads the equipment register, both datasheets and the BoD into one structure.
  2. 02Aligns each item across documents: allocation, materials, key data and design conditions.
  3. 03Marks each result pass, conflict or check.
  4. 04Flags the conflicts; the engineer confirms which document governs.

Output

0 / 24 checksrun first, then export

This animation illustrates the Plexus workflow on a hypothetical plant (ACD). In the product, cross-checks run server-side and every value keeps provenance to its source document; an engineer reviews and confirms.

Source documents: ACD-REG-0001 Equipment sheet, two datasheets and ACD-BOD-0001, hypothetical plant

Equipment itemP&ID allocationMaterialsKey data and dutyDesign conditions
E-301Feed/effluent exchanger
E-302Effluent condenser (CW)
E-303Effluent chiller (brine)
V-301Cold separator
T-301Off-gas scrubber
P-301A/BScrubber circulation pumps

Manual: 3-5 hours
With Plexus: 15-30 min review (estimate, six equipment items across register, datasheets and BoD)

Next exampleP&ID tag extraction