← All examples

PLEXUS EXAMPLE · 05

Pump RFQ generation

From datasheet to inquiry: a 40-line RFQ draft with every line traced to the datasheet or the BoD and open points flagged before issue.

Input

PUMP DATASHEETACD-DS-P101-001

IPA Feed Pumps P-101A/B

Revision
Rev 0
Service
IPA feed to reaction section
Duty
5.0 m3/h @ 105 m
BASIS OF DESIGNACD-BOD-0001

Basis of Design & Operation/Control Philosophy

Revision
Rev 0
Used for
Service, site and utility data
Sections
2, 3.4

The source documents are not shown: datasheets and design bases stay inside your project. The draft below comes from a hypothetical plant (ACD), presented the way a generated document arrives for review.

What Plexus does

  1. 01Reads the pump datasheet and the BoD into one requirement set.
  2. 02Drafts the RFQ sections and fills each line from its source.
  3. 03Marks lines without a document source as proposed template defaults.
  4. 04Flags open points; the engineer completes and issues the RFQ.

Output

0 / 40 lines draftedrun first, then export

This animation illustrates the Plexus workflow on a hypothetical plant (ACD). In the product, document drafting runs server-side and every line keeps provenance to its source; an engineer completes and issues the RFQ.

Source documents: ACD-DS-P101-001 Rev 0 and ACD-BOD-0001 Rev 0, hypothetical plant

Request for Quotation: IPA Feed Pumps P-101A/B

RFQ number
ACD-RFQ-P101-001

Status
Draft for engineer review

References
ACD-DS-P101-001 Rev 0 · ACD-BOD-0001 Rev 0

Due date
Set at issue

ItemRequirementSource

Manual: 3-6 hours
With Plexus: 20-40 min review (estimate, single-pump inquiry package)

Next exampleSIF register vs Basis of Design