A usable GRE piping system specification defines more than nominal diameter and pressure class. Before requesting quotations, you need a system-level design basis that connects the service, operating envelope, layout, loads, joints, qualification evidence, field work, and acceptance documents.
Start With a System Definition, Not a Pipe Class
GRE stands for glass-reinforced epoxy, but the material name does not define a complete piping system. The proposed system must still connect its resin matrix, construction, dimensions, fittings, joints, manufacturing route, installation procedures, and qualification evidence.
That distinction matters at the RFQ stage. If you request only a nominal diameter and pressure class, different bidders may make different assumptions about temperature, chemical exposure, transient pressure, vacuum, external loads, connections, or field responsibilities. Their prices may look comparable even when their technical scopes are not.
Define the system boundary first. State where the GRE scope begins and ends, which components are included, which interfaces connect to equipment or other materials, and who is responsible for engineering, fabrication, installation, inspection, testing, and final records. The objective is not to select a product from a short label. It is to create an RFQ that exposes assumptions before award.
A workable GRE pipe specification can use the following procurement checklist. It does not replace the applicable code, the complete project specification, the supplier's qualified procedures, or approval by the responsible project engineer.
The 12-Input GRE Pipe RFQ Checklist
| No. | RFQ input | What you should define | What the supplier should return |
|---|---|---|---|
| 1 | Service fluid and chemistry | Composition, concentration, phases, contaminants, cleaning fluids, abnormal exposure, and the external environment | Compatibility basis, assumptions, limits, and required confirmations for the proposed construction |
| 2 | Design and operating envelope | Normal, minimum, maximum, design, upset, transient, cyclic, vacuum, start-up, shutdown, and cleaning conditions | Declared operating envelope and a list of assumptions or exclusions |
| 3 | Sizes, routing, and hydraulic basis | Flow cases, line sizes, route, elevation changes, tie-ins, and the approved calculation basis | Hydraulic inputs, dimensional assumptions, and required interface data |
| 4 | Mechanical loads, supports, and restraints | Weight cases, thermal movement, surge, vibration, external loads, support philosophy, anchors, guides, and restraints | Structural-analysis inputs, load limits, and system-specific support requirements |
| 5 | Product family and component scope | Pipe, fittings, flanges, branches, spools, specials, gaskets, fasteners, and interfaces | Proposed qualified product family and a complete bill of scope |
| 6 | Joint and interface strategy | Joint type, field closures, equipment connections, transitions, installation environment, and responsibility | Proposed joint system, applicable procedures, tools, inspection method, and limitations |
| 7 | Standards and precedence | Standard number, edition, scope, project supplements, governing order, and approval process | Compliance and deviation matrix tied to the offered system |
| 8 | Qualification basis | Required performance categories, environment, product-family boundaries, tests, and change controls | Qualification summary and an applicability statement for the offered configuration |
| 9 | Manufacturing QA and traceability | Quality plan, inspection points, release points, identification, traceability, and record requirements | Inspection and test plan, manufacturing record index, and traceability method |
| 10 | Delivery, storage, and installation | Packing, transport, receipt inspection, storage, tools, site conditions, personnel, and field controls | Controlled procedures, resource needs, competency requirements, and hold points |
| 11 | Inspection, testing, and repair | Inspection scope, test boundary, safety controls, acceptance route, nonconformance, and repair governance | Project-specific inspection, test, and repair procedures plus required records |
| 12 | Documents, responsibilities, and acceptance | Document register, submission schedule, approval status, responsibility matrix, deviations, as-builts, and handover criteria | Complete bid return, document schedule, responsibility matrix, exclusions, and acceptance evidence |
Do not fill missing fields with generic values copied from a previous project or another product family. Pressure-test values, hold times, inspection percentages, support spacing, and chemical-compatibility limits must come from the applicable project requirements and the evidence for the proposed system.
Define the Service and the Full Operating Envelope
Record the fluid and every relevant exposure
Start with the process fluid, but do not stop at its common name. Record composition, concentration, phases, contaminants, solids, additives, and any credible variation over the operating cycle. Identify fluids used during cleaning, flushing, preservation, commissioning, or upset conditions. External exposure can also matter, so state the surrounding environment, temperature, weather, ultraviolet exposure, soil or water conditions, and foreseeable contact with spilled chemicals where relevant.
Ask the supplier to state the compatibility basis for the exact construction it proposes. The answer should identify the assumptions and limits that apply to that product family. A general compatibility statement is not enough when the real service changes with concentration, temperature, exposure duration, stress state, or a secondary chemical.
Separate normal, design, and temporary conditions
List normal operating pressure and temperature separately from design values. Then describe minimum conditions, start-up and shutdown, blocked-in cases, surge, pressure cycling, vacuum or drain-down, cleaning, and other temporary or abnormal states that the project requires the system to withstand.
This distinction prevents one steady operating point from being treated as the whole design envelope. It also gives the supplier a defined basis for confirming product-family applicability and identifying cases that need additional analysis.
Use an operating-case table in the RFQ. Give each case a name, fluid, pressure, temperature, duration or frequency where applicable, and its status as normal, design, transient, or temporary.
Connect GRE Piping System Design: Hydraulics, Layout, and Loads
Give hydraulic and routing inputs together
Hydraulic design cannot be separated from the proposed dimensions and route. Provide flow cases, line-size basis, route, elevation profile, equipment tie-ins, valve or restriction information, and transient scenarios. State who performs each calculation and which inputs the supplier must confirm.
Parameters such as internal diameter and roughness should be tied to the offered system and the approved calculation method. They should not be assumed from an unrelated data sheet. If the route is not final, identify the maturity of the layout and require the bidder to list the dimensions or changes that would affect its offer.
Define loads, supports, and restraints as system inputs
Internal pressure is only one design action. The project may also need to consider pipe and fluid weight, insulation or attachments, thermal movement, surge, vibration, equipment loads, maintenance loads, wind, burial conditions, settlement, or other external effects.
Provide the support philosophy as well as available support locations. Identify anchors, guides, line stops, concentrated loads, and sensitive equipment interfaces. If the supplier is expected to provide allowable loads, support requirements, or analysis inputs, make that deliverable explicit.
Do not place generic support-spacing numbers in the RFQ without a traceable basis. The required arrangement can depend on size, construction, span condition, temperature, fluid weight, fittings, concentrated loads, and the proposed product family. A system-level review connects the hydraulic cases, physical route, support configuration, and mechanical load cases before final approval.
Specify the Qualified Product Family and Joint Strategy
Make GRE pipe qualification traceable to the offered configuration
Qualification evidence should apply to the configuration being offered. Ask the supplier to identify the relevant resin matrix, reinforcement and wall construction, liner or barrier where applicable, dimensions, component types, manufacturing process, and joint system. The bid should explain how its evidence covers the proposed pipe, fittings, and operating envelope.
This is especially important when a supplier offers several constructions under the same broad material label. Long-term pressure data or qualification results for one material, construction, manufacturing process, or test environment should not be assumed to cover a different family without a documented basis. ASTM D2992, for example, addresses hydrostatic or pressure design-basis procedures for defined fiberglass products; it should not be treated as a complete system specification or as evidence transferable to any GRE construction.
Ask how material, design, supplier, or manufacturing changes are controlled. A useful qualification summary states what was tested, which product-family boundaries apply, what conditions were covered, and why the offered configuration falls within those boundaries.
Treat GRE pipe jointing and interfaces as part of the system
Select the joint strategy during specification, not after material delivery. Define the proposed joint category, field closures, prefabricated spools, branches, flanged connections, equipment interfaces, and transitions to other materials. State which party supplies every joint component, consumable, tool, procedure, and record.
The supplier should return the approved procedure for its proposed system and identify environmental restrictions, preparation requirements, personnel competencies, inspection steps, cure or assembly controls, and repair route where applicable. These details are product- and procedure-specific. A method taken from a different system should not be used as a generic substitute.
Give interfaces their own schedule. For each tie-in, record the component, material, rating and dimensional basis, loads, sealing and bolting responsibility, other project requirements, and final approver.
Select GRE Pipe Standards by Scope, Edition, and Contract
A standards list should do more than display familiar numbers. For every reference, state the edition, the scope in which it applies, project supplements, governing jurisdiction, precedence over other documents, and the route for resolving conflict or deviation.
The four published parts of ISO 14692 illustrate why scope matters:
- ISO 14692-1 addresses vocabulary, applications, pressure rating, product classification, and limitations within its defined scope.
- ISO 14692-2 addresses qualification and manufacture, including quality and documentation topics.
- ISO 14692-3 addresses system design topics such as layout, hydraulic design, structural design, and detailing.
- ISO 14692-4 addresses fabrication, installation, inspection, maintenance, delivery, handling, storage, pressure testing, and repair within its scope.
That four-part structure is useful for organizing questions, but it does not mean ISO 14692 is mandatory for every GRE project. Applicability depends on the service, industry, product, jurisdiction, owner requirements, and contract.
Other projects may reference API specifications for defined product categories or ASME NM.2 as a code route for glass-fiber-reinforced thermosetting-resin piping systems. These documents have different scopes. Do not combine ISO, API, ASME, and ASTM references into a universal checklist without an engineering and contractual reason.
Verify publication status and editions when the RFQ is issued. A draft or planned edition is not the same as a published contractual edition. If several documents apply, include a standards matrix with these fields:
| Field | RFQ requirement |
|---|---|
| Reference and edition | Exact document identifier and required edition |
| Applied scope | Components, activities, or design questions governed by the reference |
| Project supplement | Additional owner or project requirements |
| Precedence | Which document controls if requirements conflict |
| Bidder response | Comply, deviate, clarify, or exclude, with supporting detail |
The responsible project parties must make the final code and compliance decisions. The supplier's role is to show clearly how the offered system responds to those decisions.
Require Qualification, QA, and Vendor Documents With the Bid
Separate product evidence from company-level certificates
A management-system certificate and product qualification answer different questions. The first may describe an organizational quality system. It does not by itself prove that a particular GRE product family is qualified for the project's pressure, temperature, chemical, load, or joint conditions.
Ask for a product-family-specific qualification summary. It should identify the offered construction, referenced methods, relevant test conditions, covered boundaries, manufacturing consistency, and any exclusions. If a certificate is required, request the actual document and check the issuing body, holder, site, product scope, standard, edition, and validity. Do not rely only on a logo or a general statement in a brochure.
Manufacturing requirements should also define identification and traceability. State the required quality plan, inspection and test plan, review points, witness or hold points, nonconformance process, release documents, marking, material records, and manufacturing record dossier.
Build a supplier document register before award
List the documents that must accompany the technical bid, those due after award, those required before manufacturing or shipment, and those needed for final handover. A practical register may include:
- technical data sheets and a complete bill of scope;
- drawings, dimensions, interfaces, and allowable-load information;
- qualification summary and applicability statement;
- standards compliance and deviation matrix;
- quality plan, inspection and test plan, and traceability method;
- packing, handling, storage, joining, installation, inspection, testing, and repair procedures as applicable;
- document schedule, manufacturing records, test records, nonconformance closeout, as-built drawings, and final dossier index.
For each document, define the responsible party, submission date, review status, approval route, and whether work may proceed before approval. This allows you to identify missing evidence during technical evaluation rather than after the system reaches site.
Bring GRE Pipe Installation, Testing, and Repair Into the Scope
Control the work before joint assembly begins
Field quality starts with packing and delivery. Define protection during transport, receipt inspection, unloading, storage conditions, material identification, damage reporting, and segregation of nonconforming items. State who provides special tools and consumables and who verifies their condition before use.
Before installation, require an approved method, current drawings, suitable site conditions, qualified personnel where required, and an agreed inspection sequence. Hold points should be visible in the inspection and test plan. The project should also define how deviations are raised, reviewed, approved, and recorded.
Use a project- and system-specific test procedure
Do not insert a universal test-pressure multiplier or hold time into a generic article or RFQ. The correct test boundary, medium, pressure, duration, temperature controls, instrumentation, exclusion zones, safety measures, acceptance criteria, and record format depend on the applicable project rules and the proposed system.
Require the supplier and responsible project parties to identify these details in an approved procedure. The procedure should also address test preparation, vents and drains, temporary restraints, connected equipment, calibrated instruments, leak response, depressurization, disposal of the test medium, reinstatement, and final documentation where applicable.
Define repair authority and handover evidence
State who may propose and approve a repair, which documented method applies, how the repaired area is reinspected or retested, and how the result enters the final dossier. Unapproved field modification can break the traceability between the installed system and its qualified configuration.
Handover should close open items and provide the agreed as-built drawings, inspection records, test reports, nonconformance and repair records, material traceability, and document index. Completion is an evidence package, not only a mechanically complete line.
Use Bid Clarifications to Close Scope Gaps
Require every bidder to respond against the same technical structure. A compliance and deviation matrix is more useful than a general statement of compliance because it makes assumptions and exceptions visible.
Use four response categories consistently:
| Response | Meaning |
|---|---|
| Comply | The offered system meets the stated requirement, with referenced evidence |
| Deviate | The offer differs from the requirement; the difference and impact are stated |
| Clarify | Additional project information or a decision is required |
| Exclude | The item is outside the offered scope; the responsible party is identified |
Add an interface and responsibility matrix for design, data supply, component supply, fabrication, installation, inspection, testing, approval, and handover. If a task is shared, identify who leads, who supplies inputs, who reviews, and who retains the final record.
During technical evaluation, compare more than the words “included” or “compliant.” Check the underlying product family, assumptions, evidence, procedures, document dates, exclusions, and interfaces. Resolve material differences before commercial comparison and award. The result should be a defined technical scope that can move into detailed engineering without reopening basic questions.
Frequently Asked Questions
Is ISO 14692 required for every GRE piping project?
No. Its applicability depends on the service, system, industry, jurisdiction, owner requirements, and contract. Your project engineering team should confirm the governing documents and their editions before they are placed in the RFQ.
Is pressure class enough to select a GRE piping system?
No. You also need the fluid and external environment, temperature range, transients, vacuum cases, cycles, route, hydraulic conditions, external loads, supports, joints, interfaces, qualification basis, and field requirements.
How should chemical compatibility be confirmed?
Provide the full service composition and exposure conditions. Ask for evidence applicable to the proposed resin, construction, and product family. Record assumptions and limitations. Do not rely on a generic compatibility table without checking its product and condition boundaries.
What does “qualified product family” mean in an RFQ?
It means the offered pipe, fittings, joints, materials, construction, dimensions, and manufacturing process can be traced to an applicable qualification basis. The supplier should explain that relationship and identify boundaries or changes that need separate review.
What should a GRE supplier return with the technical bid?
The return should include the proposed scope, technical data, drawings, qualification summary, compliance and deviation matrix, QA and traceability plan, required procedures, document schedule, assumptions, exclusions, and responsibility boundaries.
Who should approve the installation and pressure-test procedure?
The contract responsibility matrix should identify the qualified approving party. The procedure must match the project requirements, applicable standards, site conditions, safety rules, and proposed system. Supplier submission does not remove the project's review and approval duties.
Conclusion
Build the RFQ around the complete service, system, evidence, and execution scope before comparing offers. To discuss a project, review the CNPS GRE pipes page and submit your service conditions, layout, joint, standard, inspection, and document requirements for scope confirmation.
Request a Project-Specific GRE Scope Review
Share the service conditions, layout, joint, standard, inspection, testing, and document requirements available for your project.
