Gas Compressor Package (Chloromethane & Mixed Gas) | EPC Guide

PART 0 — HOW TO USE THIS GUIDE (READER MAP + “CHOOSE YOUR PATH”)

This long-form guide is built for EPC teams who need schedule certainty and scope clarity when buying a gas compressor package—especially for chloromethane and mixed-gas services where composition and dew point can move the goalposts.

The core principle is simple: most compressor delays are not “compressor problems.” They are interface problems—ownership gaps between EPC, vendor, and site teams (controls, utilities, battery limits, testing, documentation closure).

0.1 Choose your reading path (fast navigation)

If you are EPC Procurement (Buyer / SCM):

• Read: Part 1 → Part 3 → Part 17–20 (later)
• Your mission: lock scope boundaries, compare bids fairly, prevent “TBD creep.”

If you are EPC Process / Rotating Engineer:

• Read: Part 2 → Part 6 (later) → Part 11–12 (later)
• Your mission: define the duty envelope, avoid condensation carryover, make control ownership explicit.

If you are EPC Project / Construction / Commissioning:

• Read: Part 3 → Part 18–22 (later)
• Your mission: convert “vendor promises” into evidence (ITP, FAT, MDR/VDB, readiness gates).

0.2 The “Scope-First” method (how this guide is organized)

1. Define the service (composition envelope + contamination + suction conditions).
2. Freeze battery limits (what EPC owns vs what vendor owns).
3. Select compressor type (based on envelope and operability, not brand).
4. Define controls ownership (anti-surge/recycle, trips, SIS/ESD boundaries).
5. Lock test & documentation (FAT protocol + ITP hold points + VDB structure).

This ordering mirrors how successful EPC projects avoid redesign loops.

0.3 One-page “Reader Map” diagram

---

PART 1 — EXECUTIVE OVERVIEW: WHAT A COMPRESSOR PACKAGE REALLY IS (AND WHY PROJECTS SLIP)

A gas compressor package is not a single machine. It is a system of systems: compression element, driver, lube/seal systems, scrubbers/filters, coolers, control panel/PLC, instruments, piping, valves, foundation/baseplate, and the full documentation/evidence set.

When EPC teams buy “compressor only,” the project later pays for what was missing: unclear battery limits, incomplete duty envelope, and late control ownership decisions.

1.1 The three hidden schedule killers (seen repeatedly in EPC)

1. Datasheet TBDs that matter (composition range, suction temperature min/max, dew point margin, turndown).
2. Battery-limit ambiguity (who supplies recycle valve? who owns ESD logic? who supplies nitrogen/seal gas?).
3. Evidence closure lag (FAT done, but MDR/VDB still missing—site cannot commission cleanly).

These are management problems disguised as engineering.

1.2 The “EPC-ready” compressor package expectation

A serious packager should be able to deliver:

• A bid that is comparable (clear inclusions/exclusions, utilities list, performance assumptions)
• A design that maps to recognized industry standards for compressor scope (e.g., API/ISO for compressor categories) (apiwebstore.org)
• A hazardous-area compliance path (IECEx/Ex standards alignment where relevant) (IECEx)
• A test plan (FAT protocol + acceptance criteria)
• A Vendor Data Book (VDB/MDR) structure that closes before shipment

1.3 Quick scope snapshot table (what buyers should explicitly ask for)

Subsystem / Deliverable	EPC must define early	Vendor must provide clearly	Typical dispute if unclear
Duty envelope (min/normal/max)	✅	✅ (validate)	Re-rate / redesign late
Gas composition & dew point margin	✅	✅	Liquid carryover, seal failures
Battery limits (tie-ins, utilities)	✅	✅	“Not in scope” change orders
Controls ownership (DCS/PLC/SIS)	✅	✅	Trip logic fights at site
FAT protocol + acceptance criteria	✅	✅	FAT passes but site fails
VDB/MDR index & document closure	✅	✅	Commissioning blocked

---

PART 2 — APPLICATION LANDSCAPE: CHLOROMETHANE, MIXED GAS, AND OTHER INDUSTRIAL SERVICES

Chloromethane and mixed-gas services are not “exotic,” but they are unforgiving: small composition swings can move density, molecular weight, compressibility, and dew point enough to push the compressor outside its stable map or cause condensation in the wrong place.

For EPC, the practical question is: Where can liquids appear, and how do we guarantee they do not reach the compression element or seals?

2.1 Chloromethane services: typical compression “pain points”

Common EPC realities (project-dependent, but recurring):

• Trace contaminants and moisture control: small amounts can change corrosion risk and condensation behavior.
• Temperature swings: suction temperature changes can move the dew point margin dramatically.
• Material compatibility: elastomers and sealing materials are often overlooked until late.

Your RFQ must treat chloromethane service as a system (scrubbing + filtration + temperature control + shutdown philosophy), not only a compressor.

2.2 Mixed gas services: the “envelope problem”

Mixed gas is an EPC trap because many specifications still provide only a single composition point. Vendors then optimize to that point, and the project discovers at start-up that:

• actual composition is wider than expected,
• dew point crosses into operating range,
• recycle/turndown behavior is unstable.

The correct approach is specifying a composition envelope (min/normal/max) and requiring vendor confirmation of stable operation across it.

2.3 Application-to-risk table (use in kickoff & bid leveling)

Application	Primary technical risk	EPC “freeze-first” focus
Chloromethane compression	condensation + materials compatibility	dew point margin + materials + separator design
Mixed gas boosting	composition uncertainty + map stability	envelope definition + turndown + recycle philosophy
Flare/Vapor recovery	contaminants + variable flow	filtration + separation + controls ownership
Recycle gas / process loop	surge/instability	anti-surge/recycle sizing + response time
Brownfield tie-in	power quality + interface	VSD harmonics + tie-in scope + shutdown logic

---

PART 3 — THE EPC RFQ FRAMEWORK: DEFINE DUTY, THEN FREEZE INTERFACES (SCOPE-FIRST METHOD)

If you want high-quality RFQs, your RFQ must make it easy for vendors to give comparable bids and hard for them to hide behind assumptions.

This section gives you a step-by-step RFQ structure designed to prevent redesign loops and late scope disputes.

3.1 Step-by-step RFQ structure (what to write, in what order)

Step A — Service & duty envelope (non-negotiable)

• Gas composition (min/normal/max), impurities, moisture
• Suction pressure/temperature (min/normal/max)
• Required discharge pressure
• Flow range, turndown requirement, transient cases

Step B — Battery limits (make ownership explicit)

• Mechanical tie-ins (suction/discharge flange standards)
• Utilities (power, cooling medium, nitrogen, instrument air)
• Vent/drain, flare connection philosophy
• Foundation/baseplate scope boundaries

Step C — Controls & safety ownership

• Package PLC vs DCS vs SIS/ESD responsibility
• Trip logic boundaries
• Required interfaces (signals list, protocols, hardwired vs comms)

Step D — QA evidence and acceptance

• ITP hold points (witness points that matter)
• FAT procedure + acceptance criteria
• Vendor Data Book structure and closure timing

3.2 “Freeze-first” checklist table (RFQ-critical)

Category	Freeze early	Why it prevents delay
Composition envelope	✅	avoids re-rate and map instability
Dew point margin / liquid handling philosophy	✅	prevents carryover and seal damage
Turndown and control mode	✅	prevents unstable recycle behavior
Cooling medium availability & design points	✅	avoids cooler redesign and power changes
Hazardous area classification	✅	drives Ex selection and lead time (IECEx)
Controls ownership (DCS/PLC/SIS)	✅	avoids commissioning disputes
Documentation closure date (pre-shipment)	✅	prevents site blocking

3.3 Bid leveling: force apples-to-apples comparisons

Require bidders to provide, in a single table:

• All design assumptions (composition point chosen, ambient, cooling medium)
• Included subsystems (scrubber, coalescer, aftercooler, control panel)
• Utilities consumption summary
• List of deviations

This is how you convert “lowest price” into “lowest risk.”

---

PART 4 — PROCESS FUNDAMENTALS (PLAIN-ENGLISH): WHAT NON-PROCESS BUYERS MUST UNDERSTAND

Compression is simple in principle: pressure up → temperature up. But the reason compressors fail is also simple: liquid shows up where the machine expects dry gas, or the machine is forced into unstable operation by unclear turndown and recycle control.

If you remember only one idea: gas properties are not stable in chloromethane/mixed-gas services—so your spec must describe the operating envelope, not a single point.

4.1 The practical meaning of “turndown” and “recycle”

• Turndown = how low you can run while staying stable and safe.
• Recycle = a controlled loop that keeps the compressor away from surge/instability and maintains minimum flow.

If EPC does not specify control intent early, vendors will select different philosophies—and you cannot compare bids meaningfully.

4.2 Why dew point is the hidden boss

Dew point is where vapor becomes liquid at a given pressure. During compression, pressure rises and temperature rises, and then coolers drop temperature again. That is where liquids can appear unless:

• separators are sized correctly,
• instruments detect liquid risk,
• shutdown philosophy prevents carryover during trips.

4.3 A simple “keep liquids out” schematic

---

PART 5 — GAS PROPERTIES & COMPOSITION UNCERTAINTY (CHLOROMETHANE / MIXED GAS): HOW TO SPEC CORRECTLY

This is the chapter that separates “generic RFQs” from “EPC-grade RFQs.”

When composition changes, the compressor does not merely “work a little harder.” The machine can move into regions where:

• discharge temperature rises beyond limits,
• required power exceeds driver margin,
• surge margin shrinks (centrifugal),
• volumetric efficiency shifts (reciprocating),
• sealing and lubrication conditions degrade.

Standards and recognized frameworks exist to define minimum expectations for compressor categories and hazardous-area conformity; your RFQ should reference them in the right places (without turning the RFQ into a textbook). (ISO)

5.1 The “envelope” you should specify (minimum set)

Provide min/normal/max for each:

• Composition (key components + impurities)
• Suction pressure and temperature
• Flow rate (including start-up and upset cases if relevant)
• Discharge pressure target
• Ambient conditions (site design points)
• Cooling medium availability and temperature range

Then add the one line most RFQs miss:

“Vendor shall demonstrate stable, non-condensing operation across the specified envelope and identify any limiting cases.”

5.2 Condensation & carryover: where it shows up in real projects

Common carryover paths:

• Suction side: upstream KO drum undersized, poor mist extraction, upset liquid slug
• Aftercooler outlet: temperature drops below dew point, separator not designed for the real droplet spectrum
• Trip events: transient flow reversal or sudden cooling creates unexpected condensation

Your mitigation levers are specification items:

• separator type and performance basis,
• DP constraints and alarm philosophy,
• drains/vents routing,
• trip and restart procedures.

5.3 A practical data table you can paste into RFQs

Item	EPC to provide	Example format
Composition	Min/Normal/Max	mol% table (3 columns)
Suction P/T	Min/Normal/Max	barg, °C
Flow	Min/Normal/Max	kg/h or Nm³/h (state basis)
Discharge pressure	Target + allowable range	barg
Dew point requirement	margin statement	“No condensation at X–Y”
Contaminants	list + limits	ppmw / mg/Nm³
Turndown requirement	numeric + mode	“Stable to 60% with recycle”

5.4 Standards note (keep it clean and defensible)

When your project requires “recognized minimum requirements,” the following references are commonly used for framing expectations (project-specific selection is required):

• API 617 (centrifugal / axial categories) (apiwebstore.org)
• API 618 (reciprocating categories) (apiwebstore.org)
• ISO 10439 (special purpose compressor family reference) (ISO)
• IECEx overview and IECEx standards alignment for Ex equipment philosophy (where applicable) (IECEx)

---

PART 6 — COMPRESSOR TYPE SELECTION (CENTRIFUGAL VS SCREW VS RECIPROCATING): EPC DECISION LOGIC

A compressor package selection should start with operating envelope (min/normal/max) and liquid-risk reality, not brand preference. For chloromethane and mixed gas, the two most common failure patterns are (1) condensation/carryover and (2) off-design instability because the project specified only one “normal” point.

Your selection target is not “the best compressor.” It is the compressor most tolerant of your uncertainty—composition swing, suction temperature swing, turndown, recycle philosophy, and site power quality.

6.1 Plain-English comparison: where each type wins

Centrifugal (API/ISO special purpose) Best when flow is high and continuous, and when you can keep gas clean and dry with reliable anti-surge control. It’s widely used across petroleum/chemical/gas services; API 617 sets minimum requirements for axial and process centrifugal compressors in these industries. (API)

Screw (oil-injected / oil-free depending on service) Best when you need robust turndown and can tolerate some variability. In many industrial services, screws are chosen because capacity control is straightforward (e.g., slide valve + VSD), and they can be forgiving—but your liquid-handling philosophy still matters.

Reciprocating (API 618 family) Best when compression ratio is high and flow is moderate/low, and when you need a wide envelope. API 618 is the commonly referenced baseline for reciprocating compressors in petroleum/chemical/gas services, and it places major emphasis on controlling pulsation and vibration because those issues can dominate package reliability and site rework. (Wood Vibration Analysis)

6.2 Decision matrix (EPC-ready, bid-leveling friendly)

Decision factor	Centrifugal	Screw	Reciprocating
Wide composition envelope (mixed gas)	Medium (needs map margin)	Medium–High	High
High compression ratio	Medium	Medium	High
High flow continuous	High	Medium	Low–Medium
Turndown requirement (deep)	Medium (recycle/ASD)	High	High (steps/unloaders)
Liquid carryover tolerance	Low	Medium (service-dependent)	Low–Medium (still sensitive)
Vibration/pulsation complexity	Low–Medium	Low	High (studies critical)
Controls complexity	High (anti-surge)	Medium	Medium
Typical EPC risk	Map mismatch + surge	Oil management + carryover assumptions	Pulsation/vibration + foundations

6.3 A practical selection flow (use in RFQ kickoff)

6.4 RFQ language that prevents “wrong type” disputes

Include these three sentences (adapt project details):

1. “Vendor shall confirm stable operation across the specified envelope and identify limiting cases.”
2. “Vendor shall declare required protection/control philosophy (anti-surge/recycle/unload) and scope ownership.”
3. “Vendor shall provide a clear list of assumptions; deviations must be itemized for bid leveling.”

---

PART 7 — DRIVERS & SPEED CONTROL (MOTOR / VSD / SOFT STARTER): WHAT EPC MUST FREEZE EARLY

For EPC projects, the driver decision is less about “efficiency marketing” and more about grid reality and interface ownership. A VSD-driven compressor can be excellent, but only if the project plans for: harmonics, cooling, EMC, cable strategy, and trip philosophy.

The most frequent late surprise is harmonic compliance: utilities and owners increasingly require alignment with IEEE 519 principles at the point of common coupling (PCC). Eaton’s overview highlights that the focus is voltage distortion at the PCC, and industrial vendors apply IEEE 519 concepts frequently for VFD-driven systems. (Eaton)

7.1 Driver options: what they change in your RFQ

A) Motor + Direct-On-Line / Soft Starter

• Simple, fewer components.
• Limited speed control (turndown handled by recycle/unload strategy).
• Can be schedule-friendly if grid constraints are tight.

B) Motor + VSD (most common for variable operation)

• Enables speed-based turndown and can reduce recycle losses.
• Introduces harmonic and EMC requirements, plus drive cooling and sometimes filter/transformer complexity.
• May require harmonic mitigation approaches (e.g., multi-pulse, filters). Rockwell and other industrial suppliers publish common mitigation architectures used to meet power-quality requirements. (Rockwell Automation)

C) Turbine driver (project-dependent)

• Adds fuel, emissions, and maintenance scope—rarely “simple.”
• Often justified only by site fuel availability, power limitations, or specific project economics.

7.2 “Freeze-first” VSD checklist (copy into RFQ)

Item to freeze	Why it matters	Typical late pain if missing
Utility / owner harmonic requirement basis	Drives filter/transformer sizing	Rework + cost + commissioning delay
Motor insulation + dv/dt limits	Protects motor over long cable runs	Motor overheating/failures
Drive cooling method	Skid HVAC/ventilation scope	Overtemperature trips
Minimum stable speed	Defines true turndown	Unstable operation at site
Control ownership (PLC/DCS)	Trip and speed reference boundaries	Interface disputes during SAT

7.3 Simple “harmonics scope” map for EPC

Practical note: Many projects interpret IEEE 519 via consulting engineers and utility requirements; applying it correctly is often the difference between a smooth energization and weeks of troubleshooting. (mirusinternational.com)

7.4 Torsional and mechanical interface reality (don’t skip)

If the train includes gearbox/coupling or operates across a wide speed range, torsional behavior becomes material. You do not need to drown the RFQ in calculations, but you should require:

• vendor confirmation of torsional suitability across operating range,
• declared assumptions on train inertia and coupling type,
• clear responsibility for analysis deliverable and acceptance criteria.

---

PART 8 — SEALS, SEAL GAS, AND LUBE OIL: THE REAL RELIABILITY CENTER

Most compressor “failures” are not compression physics—they are seal system, oil contamination, or liquid management failures. That is why EPC specifications must treat seals and oil as first-class scope items, not accessories.

For special-purpose compressor services in petroleum/chemical/gas, widely referenced frameworks (API/ISO families) expect disciplined attention to accessories, inspection/testing, and vendor data requirements. API 617 explicitly structures requirements around accessories, inspection/testing, and supplier data—exactly the areas that prevent late reliability surprises. (Intertek Inform)

8.1 Seal choices (plain-English, EPC-focused)

Dry gas seals (common on centrifugal special-purpose)

• Excellent when seal gas is clean, dry, and stable.
• Vulnerable when seal gas supply is contaminated or when condensation occurs during transients.

Mechanical seals / packing (service-dependent)

• Can be robust but highly dependent on flush plan and cleanliness.
• Sensitive to installation quality and upset conditions.

Key EPC message: whatever the seal type, the package must define where seal gas comes from, how it is filtered/dried, and how it behaves during shutdown/trip.

8.2 Seal gas system: what to specify (minimum set)

Seal gas element	EPC must clarify	Vendor must provide
Source	N₂ / process gas / instrument gas	Supply/conditioning skid
Filtration	target micron level + DP alarm	filters + DP transmitters
Dew point margin	“no condensation across envelope”	confirmation + limiting cases
Isolation during trip	valve logic + fail positions	cause & effect + testing

8.3 Lube oil system: the non-negotiables

In real projects, oil issues show up as:

• bearing temperature rise,
• filter DP alarms,
• varnish/contamination problems,
• unstable control due to sensor fouling.

So your RFQ should require:

• oil cleanliness targets and filtration strategy,
• oil cooler approach (water/air) and fouling factor assumptions,
• instrumentation list and alarm set philosophy,
• commissioning oil flush and evidence requirements.

8.4 RFQ “Reliability Clause” (useful and short)

Vendor shall define seal and lube oil system design basis, including source/quality requirements, filtration and monitoring, trip behavior, and commissioning procedures. Vendor shall provide a single-page “Reliability Design Basis” summary for bid leveling and handover.

---

PART 9 — PACKAGE MODULES (SCRUBBER, COALESCER, AFTERCOOLER): LIQUID MANAGEMENT DONE RIGHT

For chloromethane and mixed gas, your most valuable mechanical equipment may be the simplest: the suction scrubber, coalescer, and aftercooler separator. If these are wrong, the compressor becomes the victim, not the cause.

This is also where EPCs win by specifying performance intent rather than guessing internals: you define the envelope, the allowable pressure drop, the detection philosophy, and the drainage routing; the vendor designs the internals accordingly.

9.1 Suction scrubber / KO drum: what EPC should actually control

Freeze these items early:

• Allowable pressure drop (DP) across scrubber
• Liquid handling philosophy (normal drain vs upset slug)
• Level instrumentation and trip logic ownership
• Drain routing (closed drain vs oily water vs flare knock-out)

Add one practical requirement:

“Scrubber design shall prevent liquid carryover to compressor under normal operation and define response under upset.”

9.2 Coalescers and filters: where misunderstandings hide

A coalescer is often selected by marketing terms (“high efficiency”), but EPC needs to specify:

• expected aerosol/contaminant scenario (as best available),
• DP limits and alarm philosophy,
• element change-out access and maintenance space,
• spare elements strategy (commissioning + 2-year operation).

9.3 Aftercooler + downstream separator: why dew point returns here

Compression heats the gas, then cooling drops it—this is where condensation appears if dew point margin is insufficient. The correct EPC posture is:

• specify cooler outlet temperature targets across seasons,
• require vendor to check condensation risk across envelope,
• ensure downstream separation and drains are not “optional.”

9.4 A simple “liquid protection” cause-and-effect sketch

Syntax error in textmermaid version 11.9.0ERROR: [Mermaid] Parse error on line 3: ...rip / Close Suction (project philosophy) -----------------------^ Expecting 'SQE', 'DOUBLECIRCLEEND', 'PE', '-)', 'STADIUMEND', 'SUBROUTINEEND', 'PIPE', 'CYLINDEREND', 'DIAMOND_STOP', 'TAGEND', 'TRAPEND', 'INVTRAPEND', 'UNICODE_TEXT', 'TEXT', 'TAGSTART', got 'PS'

---

PART 10 — HEAT EXCHANGERS & COOLING: AIR VS WATER VS CLOSED-LOOP GLYCOL (WHY COOLERS CAUSE TRIPS)

In compressor packages, coolers and separators look “secondary,” but they often decide whether start-up is smooth or painful. The pattern is consistent: temperature control drifts, dew point margin collapses, liquids appear, and then the compressor trips—so everyone blames the compressor.

Your EPC objective is to define cooling intent early: what outlet temperature you need, across which seasons, with what utilities, and what happens during transient conditions (start-up, trip, recycle changes). When you do that, vendors can design a stable package instead of guessing.

10.1 Cooling options (what changes in scope, cost, and risk)

Option A — Air cooler (fin-fan)

• Strong when water is limited or water quality is poor.
• Risk points: hot summer ambient reduces capacity; noise footprint; larger plot space.

Option B — Cooling water (open or plant CW)

• Strong when CW is stable and available with known design temperatures.
• Risk points: fouling, corrosion, seasonal variation, water-side DP constraints.

Option C — Closed-loop glycol / brine

• Strong when freezing protection or stable temperature control is required.
• Risk points: higher pump power, extra skid interfaces, glycol concentration management.

10.2 What EPC must “freeze first” for coolers (copy into RFQ)

Item to freeze	Why it matters	What happens if you don’t
Cooling medium type (air / water / glycol)	Drives equipment selection + layout	Vendor bids become non-comparable
Design points (summer/winter)	Prevents undersized or overbuilt coolers	Rework and late changes
Target outlet temperature range	Defines dew point margin strategy	Condensation risk surprises
Allowable pressure drop (process + utility side)	Ensures compressor sees correct suction/discharge conditions	Instability, power increase
Fouling factor / water quality assumption	Drives thermal sizing and metallurgy	Underperformance after commissioning

10.3 API 660 context (when shell-and-tube is used)

Many EPC projects specify shell-and-tube aftercoolers or oil coolers under recognized frameworks. API 660 describes requirements and recommendations for mechanical design, materials, fabrication, inspection, testing, and shipment preparation for shell-and-tube exchangers used in petroleum, petrochemical, and natural gas industries. (API)

You do not need to overwhelm the RFQ with standard text—but referencing the correct standard scope helps align expectations and reduces clarification cycles.

10.4 A practical “cooling-to-trip” cause chain (use in design review)

---

PART 11 — CONTROLS & PROTECTION: ANTI-SURGE, RECYCLE, CAPACITY CONTROL, AND ESD OWNERSHIP

Controls are where EPC packages succeed or fail—because controls define who is responsible when the unit trips at site. The quickest way to create conflict is to leave the ownership unclear: “DCS will handle it” or “vendor PLC will handle it” without defining signals, permissives, cause & effect, and testing.

Your EPC goal is to make controls auditable: every trip and interlock should trace to a cause, an action, and a test method—before shipment.

11.1 Three control philosophies EPC must define early

1. Capacity control (how the unit follows demand)

• VSD speed control, slide valve, unloaders, recycle, or combinations.

2. Protection control (how the unit protects itself)

• High discharge temperature, vibration, seal/oil alarms, separator level trips.

3. Process safety / ESD boundary (how the plant shuts down safely)

• What belongs to package PLC vs DCS vs SIS/ESD.

11.2 Anti-surge and recycle ownership (the EPC-safe approach)

For centrifugal packages, anti-surge is not optional: the question is where it lives and how it’s proven.

EPC-safe rule of thumb

• Vendor provides anti-surge algorithm and recycle valve sizing basis.
• EPC defines DCS/ESD interfaces, permissives, and site shutdown philosophy.
• FAT verifies: signal simulation, valve stroke time, trip behavior, permissive logic.

11.3 “Control ownership map” (include in RFQ and kickoff)

11.4 Cause & Effect table starter (site-proof template)

Initiator	Action	Owner	Test method (FAT/SAT)
Vibration HH	Trip compressor	Package PLC + SIS boundary	Simulate input + verify trip
Discharge temp HH	Trip / reduce load (project-specific)	Package PLC	Simulation + alarm checks
Scrubber level HH	Alarm → then Trip (if specified)	EPC defines philosophy	Level simulation
ESD signal from plant	Controlled shutdown	SIS/DCS	Hardwired loop test

---

PART 12 — ELECTRICAL & INSTRUMENTATION SCOPE: HAZARDOUS AREA, SIGNALS, TIE-INS, AND “FREEZE-FIRST” CHECKLIST

EPC packages often stall late because E&I scope was treated as “later.” In reality, E&I choices drive lead time (Ex equipment), interface engineering (signals/protocols), and commissioning readiness (loop checks and cause & effect closure).

If your project is in a potentially explosive atmosphere, you must align early on the compliance route. IECEx is an IEC system for certification to standards relating to equipment for use in explosive atmospheres, used globally as a conformity assessment tool. (IECEx)

12.1 Hazardous area compliance (IECEx / ATEX) — what to decide early

For EU-related projects, ATEX Directive 2014/34/EU addresses equipment and protective systems intended for use in potentially explosive atmospheres and defines responsibilities for manufacturers, importers, and distributors. (EUR-Lex)

EPC practical takeaway: decide early:

• area classification (Zone/Division) and equipment marking expectations,
• whether IECEx certificates are acceptable in the project compliance strategy,
• documentation requirements for Ex equipment in the Vendor Data Book.

12.2 Signals & integration: avoid “protocol surprises”

Define, at RFQ stage:

• I/O list ownership (who supplies which instruments and where they terminate)
• Communication protocol (hardwired vs Modbus/Profinet/etc.)
• Time sync and event log expectations
• Alarm/trip handshake logic between package PLC and DCS/SIS

12.3 VSD and power quality: where commissioning often slows

If the compressor uses a VSD, many owners and utilities apply harmonic control requirements at the point of common coupling (PCC). IEEE 519 describes the PCC concept and establishes waveform distortion goals for designers to reduce interference between electrical equipment. (IEEE Standards Association)

EPC-safe approach: require the bidder to state:

• assumed PCC location,
• harmonic mitigation approach (if needed),
• what evidence will be provided (study summary + commissioning checks).

12.4 Freeze-first E&I checklist (copy into RFQ)

E&I item	Freeze early	Why it prevents late delay
Hazardous area classification + Ex strategy	✅	Drives equipment selection and lead time (EUR-Lex)
Power supply conditions + start method (VSD/soft starter)	✅	Prevents redesign of motor/drive
PCC/harmonic requirement basis	✅	Avoids last-minute filter/transformer changes (IEEE Standards Association)
Signal list + protocol + termination scope	✅	Avoids interface disputes at SAT
Instrument ranges + alarm philosophy	✅	Prevents control tuning chaos
Earthing/bonding and cable routing assumptions	✅	Avoids rework in installation

---

PART 13 — MECHANICAL PACKAGING: SKID, BASEPLATE, ALIGNMENT, LIFTING, AND MAINTAINABILITY (EPC “INSTALLABILITY” RULES)

A compressor package can be perfectly designed on paper and still become a site problem if the mechanical packagingignores reality: transport limits, lifting, access for maintenance, alignment retention, and piping load paths.

For EPC, the goal is not “a nice-looking skid.” The goal is repeatable installability: the package should land on foundations, connect to tie-ins, pass alignment checks, and remain stable after thermal growth and piping loads—without weeks of rework.

13.1 Skid scope: what to freeze at RFQ (so bids stay comparable)

Freeze these items early, because they drive steel, layout, and cost:

• Module split strategy (single skid vs split modules for transport/weight limits)
• Lifting requirements (top lift, side lift, spreader beam assumptions, lifting lugs certification)
• Footprint + interface orientation (suction/discharge direction, cable entry, operator access side)
• Foundation concept (grouted vs non-grouted, anchor bolt layout responsibility)

13.2 Baseplate stiffness and alignment retention (plain-English)

Alignment is not a “one-time event.” On site, alignment changes due to:

• piping loads pulling nozzles,
• thermal growth during operation,
• baseplate flexibility and support points.

So your RFQ should require alignment philosophy and evidence:

• cold alignment procedure + tolerances,
• hot alignment considerations (if applicable),
• defined jacking/shimming points,
• “after shipment” and “after installation” check requirements.

13.3 Maintainability: the EPC checklist that prevents future shutdown pain

If owners cannot service filters, coalescers, valves, and instruments safely, the package becomes a liability. Require a maintenance access drawing that shows:

• element removal space (filters/coalescers),
• cooler bundle access (if shell-and-tube),
• valve reach and isolation capability,
• drain and vent access (safe routing and tagging).

13.4 Mechanical packaging deliverables (what “EPC-ready” looks like)

Deliverable	Why EPC needs it	When needed
GA drawing + interface list	Tie-ins and layout freeze	Bid + kickoff
Lifting plan + lift points	Site rigging readiness	Pre-shipment
Foundation loads + COG	Civil design and anchors	IFC
Alignment procedure	Commissioning readiness	FAT/SAT
Preservation & shipping restraints	Prevent transport damage	Pre-shipment

---

PART 14 — PULSATION, VIBRATION, AND NOISE: WHAT BITES LATE (ESPECIALLY FOR RECIPROCATING)

When reciprocating compressors are involved, pulsation and vibration are not “extra engineering.” They are often the difference between a package that starts reliably and one that cracks supports, loosens instruments, or fails piping at site.

API 618 is commonly used as a baseline for reciprocating compressors in petroleum/chemical/gas services, and it is frequently referenced in the industry specifically because pulsation/vibration problems can cause fatigue and structural damage if not addressed properly. (Apiwebstore)

14.1 The EPC mistake: treating pulsation study as “later”

If you wait until fabrication is finished, fixes become expensive:

• bottle sizing changes,
• piping reroutes,
• additional supports and clamps,
• instrument line failures.

Instead, require at RFQ/kickoff:

• pulsation analysis scope and deliverable timing,
• vibration acceptance criteria and measurement method,
• foundation assumptions and structural interface responsibilities.

14.2 What to require (minimum practical set)

Requirement	Applies mostly to	Why it matters
Pulsation study + bottle sizing basis	Reciprocating	Prevents fatigue and resonance (Southwest Research Institute)
Mechanical response / support review	Reciprocating	Avoids pipe and skid failures
Vibration monitoring points defined	All (esp. critical service)	Enables acceptance and long-term reliability
Noise target and mitigation plan	All	Avoids rework (barriers, silencers)

14.3 A simple “late vibration failure chain” (use in risk reviews)

14.4 Noise: specify it like an EPC professional

Noise is often ignored until HAZOP or commissioning. Specify:

• boundary condition for noise measurement (distance, operating mode),
• whether silencers are included in vendor scope,
• whether acoustic insulation is required and who supplies it.

---

PART 15 — MATERIALS & CORROSION: CHLOROMETHANE AND MIXED-GAS UNCERTAINTY (HOW TO STAY SAFE WITHOUT OVER-SPECIFYING)

Materials selection is where projects either (a) protect reliability with disciplined assumptions or (b) burn money with fear-driven over-specification. The correct approach is data-driven: composition envelope, contaminants, moisture, temperature range, and cleaning strategy.

For EPC, the most overlooked failures are not in the casing—they’re in elastomers, seal materials, instrument impulse lines, and small-bore connections.

15.1 “What actually drives metallurgy” (simple drivers list)

1. Moisture presence + temperature cycling (condensation is corrosive reality)
2. Trace contaminants (chlorides, acids, sulfur species—project dependent)
3. Cleaning method (solvents, steam-out, chemical cleaning)
4. Erosion/particles (filter strategy and DP monitoring)

If you cannot quantify a contaminant, do not guess an alloy blindly—write a risk-based clause requiring vendor confirmation and a mitigation plan (filtration, dew point control, coatings, inspection access).

15.2 Elastomers and non-metallics (the silent failure mode)

In compressor packages, non-metallic compatibility matters in:

• O-rings and gaskets,
• seal secondary components,
• hose assemblies,
• instrument seals.

Require a materials compatibility list as a vendor deliverable: “all non-metallics by location and media exposure.”

15.3 A practical materials decision table (EPC-friendly)

Component	Typical risk in uncertain gas service	EPC specification strategy
Wetted piping & vessels	corrosion/condensation	define moisture + dew point margin + inspection evidence
Seals & seal gas system	contamination sensitivity	specify filtration + dew point + trip behavior
Coolers (gas + oil)	fouling + corrosion	freeze cooling medium assumptions and fouling factor
Small bore & instruments	vibration + corrosion	require proper support + metallurgy + impulse line routing

15.4 Keep it auditable: what evidence to request

Ask for:

• material certificates (MTC/MTR) and traceability plan,
• welding procedures and NDT summary,
• coating/painting spec for environment,
• “as-built” materials list in Vendor Data Book.

---

PART 16 — CODES, STANDARDS, AND COMPLIANCE MAP: GLOBAL EPC-READY EVIDENCE (WHAT TO REFERENCE, WHAT TO DELIVER)

This part is about one thing: auditability. EPC buyers do not want “we comply.” They want a clean mapping from standard → requirement → test → document evidence.

Below is a practical compliance map that is widely recognized in petroleum/chemical/gas projects and global trade, with sources you can cite in your website “Resources” section.

16.1 Compressor standards (typical references)

• API 617: minimum requirements for axial and process centrifugal compressors used in petroleum, chemical, and gas industries. (API)
• API 618: minimum requirements for reciprocating compressors and drivers for petroleum/chemical/gas services (commonly purchased through API webstore). (Apiwebstore)
• ISO 10439: minimum requirements and recommendations for axial and centrifugal compressors for special purpose applications in petroleum/petrochemical/natural gas. (ISO)

16.2 Hazardous area compliance (IECEx / ATEX / IEC 60079 family)

• IECEx: IEC system for certification to standards relating to equipment for use in explosive atmospheres; designed to facilitate international trade while maintaining safety. (IECEx)
• ATEX Directive 2014/34/EU: defines responsibilities for placing equipment and protective systems on the EU market for potentially explosive atmospheres. (EUR-Lex)
• IECEx publishes operated standards lists (including IEC 60079-related documents) as part of the Ex ecosystem. (IECEx)

16.3 Pressure equipment compliance (PED / ASME BPVC)

• PED 2014/68/EU: applies to design, manufacture, and conformity assessment of stationary pressure equipment above 0.5 bar; entered into force 20 July 2016. (Internal Market & SMEs)
• ASME BPVC: major technical resource used in manufacturing and operation of boilers and pressure vessels. (ASME)

16.4 Electrical power quality (when VSD is used)

IEEE 519 describes the point of common coupling (PCC) concept and sets waveform distortion goals for designers to reduce interference between equipment—frequently used as the reference basis when VSDs are applied. (IEEE Standards Association)

16.5 “Compliance-to-evidence” matrix (use in RFQ and bid leveling)

Compliance area	Typical reference	Evidence EPC should request	When to close
Centrifugal compressor	API 617 / ISO 10439	datasheets, test records, inspection reports, vendor data	FAT / pre-ship (API)
Reciprocating compressor	API 618	pulsation/vibration deliverables + acceptance records	before fabrication freeze (Apiwebstore)
Ex equipment	IECEx / ATEX	certificates, marking list, Ex dossier section in VDB	before shipment (IECEx)
Pressure vessels/accessories	PED / ASME BPVC	conformity assessment, MTR, NDT, pressure test records	pre-ship (Internal Market & SMEs)
VSD power quality	IEEE 519	harmonic basis statement + mitigation + commissioning checks	energization (IEEE Standards Association)

---

PART 17 — ITP + HOLD POINTS THAT ACTUALLY PREVENT REWORK (EPC-PROVEN, NOT PAPERWORK)

Most EPC teams already “have an ITP.” The real question is whether your ITP forces early evidence on the items that cause late redesign, site rework, and commissioning delays.

An effective ITP for a compressor package is scope-specific: it covers not only the compressor core, but also the pressure parts, piping, instruments, electrical panels, controls logic, and documentation closure—because those are where most failures hide.

17.1 The difference between “busy” hold points and “valuable” hold points

Busy hold points: generate signatures but do not prevent a future failure (e.g., generic “visual inspection” without acceptance criteria). Valuable hold points: verify a condition that, if missed, becomes expensive or unsafe to correct later (e.g., material traceability closed before welding, NDE coverage confirmed before painting, FAT logic proven before shipment release).

In practice, valuable hold points align with the way special-purpose compressor standards structure requirements around inspection/testing and supplier data (even if your project uses a tailored specification). (American Petroleum Institute)

17.2 The “Minimum Hold Points” set for compressor packages (copy/paste)

Below is a pragmatic baseline. Adjust by service criticality (chloromethane/mixed-gas typically warrants a stricter set due to dew point/liquid risk).

ITP Stage	Hold / Witness Point	Acceptance focus	EPC value
Kickoff	Battery limits + control ownership freeze	signed interface list	prevents scope fights
Incoming	Material identification + MTR traceability	heat numbers match BOM	prevents traceability gaps
Fabrication	WPS/PQR/WPQ ready + welding traceability	qualified procedures	prevents NCR cascade
NDE	RT/UT/MT/PT coverage confirmed	per spec, recorded	avoids hidden defects
Pressure test	Hydro/pneumatic + relief devices checks	recorded pressures, duration	prevents site test surprises
Assembly	Alignment plan + piping load control	tolerances documented	avoids vibration/alignment drift
Electrical	Panel FAT + loop simulation	I/O, alarms, permissives	reduces SAT time
Controls	Cause & Effect verification	trip logic + permissives	prevents “who owns trip” disputes
Final	Preservation + packing + MDR/VDB closure gate	index complete	avoids commissioning blockage

---

17.3 A simple ITP workflow that EPC can manage weekly

Your expediting rhythm should be evidence-first: if evidence is late, the project is late—regardless of how fast steel is being fabricated.

---

PART 18 — FAT, PERFORMANCE, FUNCTIONAL TESTING: WHAT TO PROVE IN SHOP VS WHAT TO PROVE ON SITE

A compressor package “FAT” fails EPC projects in two common ways:

1. FAT is treated as a factory tour rather than a test with acceptance criteria.
2. FAT proves the machine can run, but does not prove the system (controls, trips, interfaces, documentation).

The best EPC approach is to split testing into three layers: mechanical integrity, functional readiness, and interface verification—then assign each layer an auditable acceptance record.

18.1 FAT types and what each one actually proves

Test type	What it proves	What it does NOT prove	EPC action
Mechanical run test	basic mechanical integrity	full site operability	require run record + limits
Performance test (when applicable)	capacity/efficiency at defined point	envelope across all cases	define test point + corrections
Functional test	sequences, alarms, permissives	site wiring correctness	require simulation and logs
Loop simulation / I/O test	PLC logic + signals	physical loop wiring	use simulated I/O + checklists
Protection test	trip actions and reset behavior	site ESD integration	require cause & effect proof

For reciprocating systems, industry discussions repeatedly emphasize that pulsation/vibration control is not optional and must be addressed systematically—your testing and acceptance plan should not ignore that reality. (vdn.woodplc.com)

18.2 FAT acceptance language (EPC-ready clauses)

Use short clauses that force clarity:

• “FAT shall be executed against an approved procedure with measurable acceptance criteria.”
• “All trips and permissives shall be verified by simulation or controlled input test; results shall be recorded.”
• “No shipment release until FAT punch list is closed or formally accepted with approved concessions.”
• “FAT deliverables include: test records, calibration certificates list, ‘as-tested’ logic backup, and event logs.”

18.3 “FAT to SAT” bridge: keep commissioning fast

This approach reduces the most expensive commissioning failure mode: “Everything was fine in shop, but no one can prove it now.”

---

PART 19 — VENDOR DATA BOOK (MDR/VDB): STRUCTURE THAT CLOSES BEFORE SHIPMENT

EPC commissioning rarely fails because of missing steel. It fails because of missing evidence: incomplete certificates, unclear as-built drawings, missing calibration records, or a VDB that arrives weeks after the skid.

Your Vendor Data Book should be treated as a deliverable with a closure date, not a “final paperwork task.” Special-purpose compressor frameworks typically embed supplier data expectations as part of minimum requirements—your project spec should do the same in an EPC-friendly way. (American Petroleum Institute)

19.1 Recommended VDB index (compressor package)

Use this structure to keep it searchable and audit-ready:

Section	Contents (examples)	Why it matters
0 Admin	PO, deviation list, MDR index	audit trail
1 Datasheets	final datasheets + envelope	prevents re-rating disputes
2 Drawings	GA, P&ID, wiring, loop diagrams, termination	site installation
3 Calculations	sizing notes (as required), studies summary	defensibility
4 Materials	MTR/MTC, PMI records, traceability	compliance
5 Welding/NDE	WPS/PQR/WPQ, NDE reports, repair logs	integrity
6 Tests	pressure tests, FAT report, functional logs	acceptance
7 Instruments	calibration list, certs, ranges	loop check speed
8 Electrical/Ex	Ex certificates list + marking, panel tests	hazardous area readiness (iecex.com)
9 Manuals	O&M, spares, preservation	operations continuity

19.2 Document closure gate (non-negotiable if you want smooth start-up)

Define a formal gate:

• Gate name: “Shipment Release – Documentation Complete”
• Rule: shipment release requires MDR index at ≥ 95% complete, with an agreed exception list.
• Output: signed MDR index + digital folder link + naming convention.

---

PART 20 — PROJECT EXECUTION + EXPEDITING RHYTHM (MILESTONES, CRITICAL PARTS, EVIDENCE KPIS)

A compressor package schedule does not slip because “fabrication is hard.” It slips because interfaces and evidence are late—and then fabrication must pause or rework.

Your expediting plan should be designed like a weekly operating system: one page, repeatable, and measurable.

20.1 Milestone map (compressor package baseline)

Phase	Milestone	Output	EPC check
Award	Kickoff	scope split + interface list	signed battery limits
Engineering	GA / P&ID freeze	approved drawings	tie-in certainty
Procurement	Long-lead items released	PO evidence	critical path protected
Fabrication	Assembly start	ITP records	traceability closed
Testing	FAT complete	FAT report + C&E proof	readiness
Closure	MDR/VDB closure gate	index + files	commissioning support
Logistics	Shipment	packing/preservation	storage-ready
Site	SAT + start-up	loop checks + trip tests	first gas readiness

20.2 Critical path parts list (what to track weekly)

Typical schedule drivers (project-dependent):

• compressor core machine availability
• motor/VSD and transformer lead time
• Ex instruments and specialized valves
• coolers and pressure vessels (scrubbers/separators)
• control panel and PLC hardware availability

Track these with a weekly evidence KPI—not vague statements.

20.3 Evidence KPIs (simple dashboard that works)

KPI	Target	Why it matters
Drawing approval cycle time	≤ 7–10 days	prevents fabrication waiting
ITP hold points completed on time	≥ 95%	prevents hidden defects
FAT punch list closure	100% or approved concessions	avoids SAT chaos
MDR/VDB completeness at ship	≥ 95%	avoids commissioning blockage
Deviation log open items	trending down weekly	prevents scope creep

20.4 Expediting cadence (repeatable weekly routine)

This cadence is especially important when you have VSD/harmonics or hazardous area compliance items, where third-party documents and certificates can become silent schedule killers. IEEE explicitly defines PCC and distortion limits in IEEE 519 editions, which is why many owners demand early alignment on the harmonic compliance basis when drives are used. (IEEE Standards Association)

---

Next

Reply “go on 21–23” and I will write:

• Part 21: Logistics & preservation (export packing, storage, readiness)
• Part 22: Commissioning & start-up (loop checks, trip tests, first gas)
• Part 23: Operations & maintenance (spares strategy, condition monitoring, training)

PART 21 — LOGISTICS & PRESERVATION: EXPORT PACKING, STORAGE, AND “ARRIVAL-READY” COMMISSIONING

A compressor package can pass FAT and still fail your schedule if it arrives with corrosion, contamination, moisture ingress, or shipping damage. EPC teams should treat preservation as a deliverable with acceptance criteria, not an afterthought.

The key is to define a preservation class (duration + environment + storage mode), then require evidence: packing photos, preservation checklists, and re-preservation instructions in the Vendor Data Book.

21.1 Preservation strategy (the 3 questions EPC must answer)

1. How long will the package be in transit + storage before start-up? (weeks/months)
2. Will it be stored indoors or outdoors, and in what climate (humidity/salt air)?
3. Will the package be periodically energized/rotated, or completely dormant?

Once those are answered, you can lock the preservation method: moisture barrier, desiccant or VCI, shrink wrap vs crate, and periodic inspection tasks.

21.2 Packaging methods and “do not mix” rules (practical)

Many industrial preservation specifications emphasize that desiccant and VCI products may not be used together in the same enclosed space, and that desiccants must be used correctly (sealed barrier, contact avoidance, dispersion). (GE Vernova)

EPC-friendly packaging table

Method	Best for	Key requirement	Common mistake
Crate + moisture barrier	long ocean shipment	sealed barrier + inspection port	“sealed” but not actually sealed
Shrink wrap (approved)	large skids / short storage	wrap integrity + UV considerations	wrap tears during handling
Desiccant (sealed)	humidity control	must be inside sealed barrier	used in leaky package (GE Vernova)
VCI approach	corrosion protection	correct enclosure conditions	mixed with desiccant (GE Vernova)

21.3 Preservation acceptance checklist (use as shipment release gate)

Item	Acceptance evidence	Owner
Preservation plan approved	signed document	EPC + Vendor
Moisture barrier integrity	photos + checklist	Vendor
Desiccant/VCI application	weight/quantity + placement notes	Vendor
Rust prevention / coated surfaces	photos	Vendor
Shipping restraints & lockouts	photos + tag list	Vendor
“Storage & re-preservation” instructions	VDB section	Vendor

21.4 Site arrival inspection (EPC quick routine)

• Verify shock indicators (if used), crate integrity, moisture indicator cards
• Check drains/vents are correctly sealed and tagged
• Confirm preservation tags match VDB instructions
• Log any damage immediately (claim timeline protection)

---

PART 22 — COMMISSIONING & START-UP: INTERFACE DISCIPLINE (LOOP CHECKS, TRIP TESTS, FIRST GAS)

Commissioning failure is rarely about missing horsepower. It is usually about interfaces not proven: signals reversed, permissives misunderstood, ESD boundary unclear, recycle valve not responding fast enough, or liquids appearing during transients.

Your EPC objective is to run commissioning as a sequence of readiness gates, with the same Cause & Effect matrix used at FAT—so SAT becomes confirmation, not discovery.

22.1 Start-up readiness gates (EPC sequence that avoids chaos)

Gate 1 — Mechanical completion

• Punch list closed, preservations removed per procedure, oil system clean
• Alignment verified per vendor procedure
• Piping supports complete; no “temporary” pipe rests

Gate 2 — Electrical energization

• Correct rotation checks, VSD commissioning checks (if applicable)
• Instrument calibration verified (loop packs)

Gate 3 — Controls & trip proof

• Simulated trips and permissives confirmed
• Recycle valve stroke time proven (if centrifugal/AS control)
• ESD handshake tested (hardwired and/or protocol)

Gate 4 — First gas

• Purge/inerting complete
• Liquid management systems proven: scrubbers drained, level logic verified
• Controlled load-up with clear operating limits

22.2 The SAT checklist that actually saves days

SAT topic	What to verify	Evidence
I/O mapping	every critical tag	signed loop pack
Trip actions	input → action → reset	C&E test record
Valve behavior	recycle/anti-surge response	stroke test log
Separator protections	HH level action	simulated input test
Alarm philosophy	alarms vs trips	alarm list + setpoints

22.3 One commissioning rule that prevents 80% of disputes

If it is a trip, it must have a test. No exceptions. If it cannot be tested, it is not defined well enough.

22.4 Installation and pre-commissioning discipline (industry practice)

In many petroleum/chemical/gas projects, machinery installation and pre-commissioning practices are formalized through widely used industry procedures and checklists (often referenced as API RP 686 / PIP REIE686 in project specifications). PIP explicitly notes its machinery installation and design requirements are used alongside PIP REIE686/API RP686 for installation and pre-commissioning. (PIP)

---

PART 23 — OPERATIONS & MAINTENANCE: SPARES STRATEGY, CONDITION MONITORING, AND TRAINING THAT REDUCES DOWNTIME

EPC may hand over the compressor package, but the owner’s success depends on two things:

1. Can the unit run stably across the real operating envelope?
2. Can the site team maintain it without waiting weeks for parts and support?

An EPC-ready package should include an O&M bundle that is service-realistic: spares matched to failure modes, monitoring matched to real risks (vibration, oil cleanliness, seal gas quality), and training focused on trips and recovery.

23.1 Spares: the “3-tier” model that procurement can buy confidently

Spares tier	Typical contents	Why it exists
Commissioning spares	filters, gaskets, key sensors	covers installation damage and early tuning
2-year operating spares	seal elements (as applicable), valves kits, instruments	prevents downtime waiting for import
Insurance / critical spares	long-lead proprietary items	protects production continuity

Best practice clause: vendor must state lead times for each recommended spare and identify any “single-source” items.

23.2 Condition monitoring: what matters in real plants

• Vibration trending (early detection of alignment/bearing issues)
• Oil analysis + filter DP monitoring (contamination and varnish risk)
• Seal gas quality monitoring (for dry gas seal services)
• Separator performance (DP + level behavior under transients)

Operator-friendly rule: trend a small number of indicators reliably, rather than collecting dozens of tags nobody reviews.

23.3 Training package outline (EPC-friendly and practical)

Module	Duration	Outcome
System overview + limits	1–2 hours	operators understand “safe map”
Start/stop and trips	2 hours	operators can recover safely
Liquid management	1 hour	prevents carryover failures
Routine maintenance	2 hours	correct filter/seal/oil routines
Alarm response drills	1 hour	faster stabilization and fewer shutdowns

---

PART 24 — TROUBLESHOOTING PLAYBOOK (SYMPTOM → LIKELY CAUSE → FAST CHECKS → CORRECTIVE ACTIONS)

In EPC reality, troubleshooting is rarely “find the broken part.” It is usually prove which subsystem is lying—process inputs, instruments, controls logic, utilities, or mechanical condition. The fastest teams use a repeatable triage routinethat protects safety, avoids guesswork, and generates evidence for vendor support.

This playbook is written for chloromethane / mixed-gas services where dew point, contamination, and envelope driftmake “normal assumptions” dangerous.

24.1 The first 15 minutes (EPC-safe triage routine)

Step 1 — Stabilize and protect equipment

• Confirm unit status (running / tripped / permissive held).
• Confirm isolation state and safe operating conditions per site procedures.

Step 2 — Read the story in the event log

• Pull: last trip cause, pre-trip alarms, key PV trends (suction P/T, discharge P/T, vibration, separator level, filter DP, recycle valve position).

Step 3 — Separate “measurement problem” from “process problem”

• Cross-check instruments with redundancy where available.
• If a trend is physically impossible (e.g., suction temperature jumps instantly), treat it as instrumentation or scaling.

Step 4 — Confirm utilities are real

• Cooling medium temperature/flow, instrument air/nitrogen, electrical supply quality, VSD status.

---

24.2 Symptom-based troubleshooting table (site-proven format)

Symptom (what you see)	Most likely causes	Fast checks (minutes)	Corrective actions (principle)
High vibration	misalignment, soft foot, piping load, resonance, bearing issue	trend vs speed; check piping supports; check recent maintenance	re-align; correct supports; verify base stiffness
High discharge temperature	cooler underperforming, recycle wrong, high ratio beyond envelope	check cooler inlet/outlet temps; verify recycle position	restore cooling; confirm operating point; adjust control strategy
Frequent surge / instability(centrifugal)	anti-surge tuning, wrong flow measurement, recycle valve slow	check recycle stroke time; verify flow DP scaling	retune/validate; ensure recycle capacity & speed
Scrubber HH level trips	liquid carryover/upset, drain blocked, level instrument issue	verify drain routing; check level transmitter health	fix drainage; adjust trip philosophy if wrong; improve separation
Filter/Coalescer DP high	fouling/contamination, wrong element, liquid loading	check DP trend vs flow; inspect bypass status	change elements; confirm upstream separation; review contamination source
Seal alarm / seal gas issues	seal gas quality, dew point margin, contamination	check seal gas pressure/DP/filter DP; check dew point basis	restore seal gas quality; improve filtration/drying; review transients
Motor/VSD trips	overcurrent, harmonics, cooling, torque at low speed	check VSD alarms; confirm cooling; verify min speed	adjust operating envelope; improve power quality mitigation; revise control

24.3 “Liquids are the enemy” decision tree (for chloromethane/mixed gas)

24.4 What to capture for vendor escalation (makes support fast)

Provide a standardized “incident bundle”:

• 30–60 minutes of trends (key PVs)
• Event log export (trip cause + alarms)
• Photos: separator drains, filter DP gauges, valve position indicators
• Current operating point vs specified envelope

This turns troubleshooting from phone calls into actionable engineering.

---

PART 25 — COMMERCIAL FRAMEWORK: BID LEVELING, TCO, GUARANTEES, AND “NO SURPRISE” CONTRACTING

Procurement success for compressor packages is not about negotiating price alone. It is about negotiating risk ownership: interfaces, performance boundaries, documentation closure, and schedule gates. The best EPC contracts make “what good looks like” measurable—then tie payment and shipment release to evidence.

25.1 Bid leveling scorecard (simple, defensible)

Use a weighted scorecard so technical and execution risks are visible.

Category	Weight	What to score (examples)
Technical fit	25%	envelope coverage, turndown, liquid protection philosophy
Package scope completeness	20%	inclusions/exclusions clarity, battery limits maturity
Controls & testing	15%	FAT plan quality, cause & effect clarity, simulation capability
QA/QC evidence	15%	ITP strength, traceability, NDE/test readiness
Documentation closure	10%	VDB/MDR index maturity and closure gate agreement
Delivery & execution	15%	schedule realism, expediting rhythm, critical parts plan

25.2 TCO model (what owners really pay for)

A low-priced package can become expensive through:

• extended commissioning time
• forced shutdowns due to carryover or control instability
• high spares consumption and long lead times
• repeated vendor mobilization

Practical EPC approach: request a one-page TCO annex from bidders:

• estimated energy consumption at main operating points
• recommended spares tiering (commissioning / 2-year / insurance) with lead times
• predicted maintenance intervals
• availability assumptions and limiting conditions

25.3 Performance guarantees: write them so they can be verified

Avoid ambiguous language. Define:

• test point(s) and correction basis
• acceptance tolerances
• instrumentation accuracy assumptions
• what happens if site conditions differ from RFQ envelope

25.4 Warranty traps and how to neutralize them (EPC checklist)

Common trap	Why it hurts	Contract countermeasure
“Warranty void if not operated per manual”	manual is vague; disputes at failure time	define operating envelope and protection logic in PO
“Vendor not responsible for site utilities”	utility quality is often unclear	define utility limits and verification method
“Docs delivered after shipment”	commissioning delayed	add document closure gate before shipment
“Ex compliance unclear”	rework and certification delays	list certificate requirements in VDB index

25.5 Shipment release gating: link money to evidence

A practical, low-conflict structure:

• Milestone payment at approved GA/P&ID freeze
• Milestone payment after FAT completion + punch closure
• Shipment release only after preservation + packing + VDB index ≥ 95% complete
• Retention until SAT acceptance and critical documents delivered

This aligns commercial terms with EPC reality: evidence drives readiness.

---

PART 26 — CASE STUDIES (STORY-DRIVEN EPC REFERENCES YOU CAN COPY INTO RFQS)

Below are case patterns designed for publishing and conversion. They are intentionally written as templates so you can adapt them to your actual projects without risking over-claiming. Each pattern includes: the trap, the fix, and the “RFQ clause you can copy.”

26.1 Case Pattern A — Chloromethane service: “The invisible liquid” problem

Situation EPC specified a normal operating point but did not lock the seasonal cooling conditions and dew point margin statement.

Trap At start-up, cooler outlet temperature drifted lower than expected; condensation appeared downstream, leading to separator level instability and nuisance trips.

Fix (Scope-first)

• Added a dew point margin clause tied to operating envelope
• Required downstream separation performance intent
• Required FAT simulation of level alarms and trip behavior

Copy-paste RFQ clause

Vendor shall confirm no-condensation operation across specified envelope and define liquid management philosophy, including downstream separation and trip behavior during transients.

---

26.2 Case Pattern B — Mixed gas: “Envelope mismatch” and unstable turndown

Situation Gas composition varied more than early lab data suggested.

Trap Compressor and control settings optimized to a single point, causing unstable operation at low load and frequent recycle hunting.

Fix (Scope-first)

• Reframed the RFQ around min/normal/max envelope
• Required bidder to declare limiting cases and stable turndown method
• Locked ownership of capacity control and recycle tuning

Copy-paste RFQ clause

Vendor shall demonstrate stable operation and turndown across min/normal/max composition envelope and identify limiting cases with proposed control strategy.

---

26.3 Case Pattern C — VSD integration: “Power quality surprise” at energization

Situation VSD selected for turndown benefit, but harmonic compliance basis and PCC definition were not frozen early.

Trap Late requirement for harmonic mitigation caused redesign of transformer/filter scope and delayed energization.

Fix (Scope-first)

• Required bidder to state PCC assumption and mitigation approach
• Included a commissioning verification method for power quality acceptance
• Structured a clear interface map between vendor and EPC electrical scope

Copy-paste RFQ clause

Bidder shall state harmonic compliance basis at PCC, propose mitigation approach (if required), and provide commissioning verification steps and evidence deliverables. (IEEE 519 is commonly referenced for PCC-based distortion limits.) (IEEE Standards Association)

---

26.4 Case Pattern D — Reciprocating package: “Vibration rework” avoided by early study

Situation High compression ratio and variable load suggested a reciprocating solution.

Trap Without early pulsation/vibration deliverables, piping support and bottle sizing risks would have been discovered after fabrication.

Fix (Scope-first)

• Locked pulsation study timing before fabrication freeze
• Defined vibration acceptance evidence and support strategy
• Coordinated foundation/interface requirements using established installation practices (API RP 686 is widely used for machinery installation and precommissioning guidance) (static.namatek.com)

Copy-paste RFQ clause

For reciprocating services, vendor shall provide pulsation/vibration deliverables prior to fabrication freeze and define acceptance criteria and evidence records.

---

26.5 Case-study publishing format (jnlmart.net-ready)

Use a consistent structure so EPC readers can scan quickly:

Section	What to write	Conversion intent
Context	service + why compression needed	qualify the reader
The trap	what typically causes delay	credibility + urgency
The fix	scope-first steps	teach + trust
Evidence	FAT/ITP/VDB deliverables	show professionalism
What to copy	RFQ clauses + checklist	immediate value
CTA	request technical review	lead generation

---

PART 27 — RFQ TOOLKIT CHAPTER: TEMPLATES, CHECKLISTS, AND “DOWNLOAD PACK” STRUCTURE (BUILT FOR EPC USE)

A long guide is useful, but EPC teams move faster with copy-paste tools. This toolkit chapter turns the key concepts into RFQ-ready templates you can standardize across projects (chloromethane, mixed gas, and other process gas services).

The objective is simple: reduce ambiguity so vendors quote the same scope basis, and your project avoids redesign loops during IFA/IFC, FAT, and commissioning.

27.1 What the Toolkit contains (recommended download bundle)

Toolkit item	File name suggestion	Best used by	Outcome
Duty Envelope Datasheet (min/normal/max)	RFQ_01_DutyEnvelope.xlsx	Process / Rotating	Comparable bids
Battery Limits + Scope Split	RFQ_02_BatteryLimits.pdf	EPC Project	Fewer “not in scope” claims
Bid Leveling Scorecard	RFQ_03_BidLeveling.xlsx	Procurement	Apples-to-apples selection
Controls Ownership Map + I/O List	RFQ_04_Controls_IO.xlsx	E&I / Automation	Fewer SAT disputes
ITP Hold Points Template	RFQ_05_ITP_HoldPoints.xlsx	QA/QC	Earlier evidence closure
FAT Protocol + Acceptance Criteria	RFQ_06_FAT_Protocol.docx	EPC + Vendor	FAT becomes proof, not tour
VDB/MDR Index Template	RFQ_07_VDB_Index.xlsx	Doc Control	“Docs before shipment” gate
Preservation & Packing Checklist	RFQ_08_Preservation_Packing.pdf	Logistics / Site	Arrival-ready equipment
Commissioning Readiness Gate Sheet	RFQ_09_Readiness_Gates.xlsx	Commissioning	Faster first-gas

27.2 How EPC should use the toolkit (fast workflow)

27.3 A practical “RFQ Deviation Format” clause (high impact)

All deviations shall be listed in a single deviation table, including (a) what requirement is affected, (b) vendor proposal, (c) impact on performance/schedule/cost, and (d) mitigation. Any “TBD” must be explicitly identified with closure date.

27.4 Suggested “Downloads” section layout for jnlmart.net

• Download 1: Compressor Package RFQ Toolkit (PDF + XLSX bundle)
• Download 2: FAT + Cause & Effect template (DOCX/XLSX)
• Download 3: VDB/MDR index and naming convention (XLSX + PDF guide)
• Download 4: Commissioning readiness gates (XLSX)

---

PART 28 — LMART CAPABILITY STATEMENT: EPC-READY PACKAGING, EVIDENCE DISCIPLINE, AND GLOBAL COMPLIANCE

EPC buyers want two things from a compressor package supplier:

1. Engineering clarity (scope, interfaces, compliance route)
2. Execution evidence (ITP, FAT, traceability, VDB closure)

This section is written as a capability framework you can publish on jnlmart.net. Where you have project-specific proof (photos, FAT clips, sample databooks), insert it directly to strengthen credibility.

28.1 What Lmart can deliver (positioning for EPC)

Skid-mounted system integration

• Compressor package integration (mechanical + piping + instruments + control panels as project scope dictates)
• Ancillary modules: suction scrubbers/KO drums, aftercoolers, coalescers, oil/seal systems, structural skids
• Layout engineered for maintainability and transport constraints

Compliance-ready pressure equipment and documentation

• Pressure equipment manufacturing aligned with widely used conformity routes (e.g., PED/CE for EU pressure equipment where applicable) (Internal Market & SMEs)
• ASME BPVC is a major code family used globally for design/fabrication/inspection/testing frameworks for pressure equipment (ASME)

28.2 Evidence package: what EPC receives (the “no-surprises” promise)

Evidence category	Typical contents	EPC benefit
Traceability	MTR/MTC, PMI records (if required), heat numbers	audit-ready compliance
Welding & NDE	WPS/PQR/WPQ, RT/UT/MT/PT reports, repair logs	fewer NCRs
Pressure tests	hydro/pneumatic records, relief device checks	safe commissioning
FAT records	procedures, logs, punch closure	reduced SAT time
E&I dossier	I/O list, calibration list, panel test records	smoother integration
VDB/MDR	index + searchable files	faster turnover

28.3 Hazardous area readiness (when your project requires Ex compliance)

If your compressor package is installed in potentially explosive atmospheres, many projects adopt IECEx/ATEX-aligned strategies. IECEx describes its objective as facilitating international trade in Ex equipment while maintaining safety. (IECEx) For EU market placement, the European Commission summarizes ATEX Directive 2014/34/EU scope and conformity expectations. (Internal Market & SMEs)

28.4 Installation readiness (reduce site rework)

For machinery installation and pre-commissioning, EPC specs often reference established guidance such as API RP 686 (machinery installation and installation design). (Namatek) Process Industry Practices (PIP) also positions REIE686A as an industry standard used alongside REIE686/API RP686. (PIP)

---

PART 29 — EPC FAQ (PROCUREMENT + ENGINEERING): CLEAR ANSWERS WITHOUT SALES NOISE

This FAQ is designed to convert readers into scope-ready RFQs. Keep answers direct, and link to the relevant chapters.

29.1 Procurement-focused FAQs

Q1: What is the #1 reason compressor packages get delayed? Unfrozen inputs and interfaces: composition envelope, battery limits, and control ownership.

Q2: How do we compare bids fairly? Force a deviation table + common datasheet envelope + scope split checklist (Part 3 + Part 27).

Q3: What should we tie milestone payments to? To evidence: GA/P&ID freeze, FAT completion with punch closure, and VDB closure gate before shipment.

Q4: What should be in scope “by default”? Suction scrubber/KO logic, aftercooler/separation logic, controls/ESD interfaces, and a defined FAT procedure—unless explicitly excluded.

Q5: How do we avoid “docs delivered after shipment”? Add a shipment release gate requiring VDB index ≥ 95% complete (Part 19 + Part 20).

29.2 Engineering-focused FAQs

Q6: For mixed gas, is a single composition point acceptable? No. Specify min/normal/max envelope and require the vendor to identify limiting cases (Part 5 + Part 6).

Q7: How do we prevent condensation/carryover? Define dew point margin intent, cooler outlet targets, separator logic, and trip behavior during transients.

Q8: Centrifugal vs reciprocating—what’s the simplest rule? High flow steady service leans centrifugal; high ratio and wide envelope leans reciprocating; variable load and robust turndown often leans screw—then validate against the real envelope (Part 6).

Q9: What must be proven at FAT? Trips/permissives and cause & effect behavior—by simulation and recorded acceptance logs (Part 18).

Q10: When VSD is used, what must EPC freeze early? PCC/harmonic compliance basis and mitigation approach. IEEE 519 describes PCC and establishes distortion limits at the user PCC. (IEEE Standards Association)

29.3 Compliance and documentation FAQs

Q11: Which standards are commonly referenced for compressors? API 617 covers minimum requirements for axial and process centrifugal compressors in petroleum/chemical/gas industries. (American Petroleum Institute) ISO 10439 specifies minimum requirements and recommendations for special-purpose axial/centrifugal compressors in petroleum/petrochemical/natural gas. (ISO)

Q12: What about pressure equipment for EU projects? The European Commission’s PED page summarizes scope above 0.5 bar and the conformity assessment expectation. (Internal Market & SMEs)

---

PART 30 — CONCLUSION + CTA: TURN THIS GUIDE INTO BETTER RFQS (AND MORE RELIABLE START-UPS)

If you take only one operational lesson from this guide, take this: Freeze the envelope and the interfaces early, and tie shipment to evidence. That alone eliminates most compressor package schedule slips.

The rest—compressor type selection, cooler choice, VSD decisions, Ex strategy—becomes manageable when the project is structured around clarity and proof rather than assumptions.

30.1 A “Scope-First” closeout diagram (what success looks like)

30.2 Recommended page layout for maximum conversion (jnlmart.net)

Above the fold

• One-line value proposition: “EPC-ready compressor packages with scope-first RFQ tools and evidence-driven delivery”
• CTA buttons: Request Proposal | Download RFQ Toolkit | Book Technical Review

Middle

• “How to specify” summary + decision tables (Parts 3, 6, 10–12)
• Proof blocks: sample VDB index screenshot, FAT checklist excerpt, packaging photos

Bottom

• FAQ (Part 29)
• Downloads section (Part 27)
• Contact form with required inputs

30.3 RFQ Intake Form: 10 fields that generate high-quality inquiries

Field	Why it matters
Gas composition (min/normal/max)	envelope stability
Suction pressure/temperature range	limiting cases
Flow range + turndown target	control and sizing
Discharge pressure target	ratio/power
Dew point / condensation requirement	liquid risk control
Cooling medium and seasonal points	cooler selection
Hazardous area classification	Ex route planning (Internal Market & SMEs)
Power supply + VSD preference	electrical scope
Plot space + lifting/transport limits	packaging design
Storage duration before start-up	preservation class

30.4 Final CTA (publish-ready copy)

Request a scope-first compressor package proposal Send the 10 RFQ inputs above and you will receive a response package including:

• inclusions/exclusions list and battery limits map
• recommended compressor type with envelope commentary
• FAT plan + ITP hold points
• VDB/MDR index outline and documentation closure gate

---