Industrial Refrigeration Unit for EPC | Skid-Mounted Packages

Industrial Refrigeration Units Are Rarely “Just Utilities”

Industrial refrigeration units are rarely “just utilities” in EPC projects. They become schedule-critical packages because they touch many interfaces at once: process duty, power, cooling medium, hazardous area, controls, FAT, preservation, and document closure.

If you want qualified RFQs (not price-shopping emails), your procurement process must do two jobs at the same time: teach EPC teams how to specify correctly and make it easy to submit a complete duty sheet.

Part 0 — Executive Overview & RFQ Shortcut

0.1 What an “Industrial Refrigeration Unit” Means in EPC Language

In EPC procurement, an industrial refrigeration unit (IRU) typically means a packaged refrigeration system that delivers a defined cooling duty (kW/TR) at specified temperature levels, with stable operation across expected load ranges.

In engineering terms, it is not one machine—it’s a system: compressor(s) + oil management + condenser/heat rejection + evaporator/secondary loop + receiver + controls/safeties + electrical + instrumentation + documentation pack.

Battery limits (what EPC should clarify early)

0.2 EPC “3-Minute Decision Map”

Most RFQ delays happen because EPC teams ask vendors to quote while the core decisions are still TBD. You can avoid 80% of redesign loops by freezing three items early: (1) refrigerant strategy, (2) cycle architecture, (3) delivery model (packaged skid vs stick-built).

Step-by-step: the EPC decision sequence

1. Confirm duty + temperature levels (normal / peak / minimum)
2. Confirm site constraints (ambient, cooling medium, utilities, hazardous area)
3. Select refrigerant family (safety + compliance + service availability)
4. Select cycle (single-stage / economized / two-stage / cascade / CO₂ transcritical)
5. Confirm packaging strategy (single skid, split modules, or site assembly)
6. Lock interface matrix (piping, electrical, controls, ESD/SIS, documents)

0.3 Refrigerant Strategy

For EPC decision-makers, refrigerant selection is not a “preference debate.” It is a risk and compliance decision that affects layout, detection/ventilation, relief philosophy, and operator training. Terminology is commonly aligned with ASHRAE Standard 15 (refrigeration safety) and ASHRAE Standard 34 (refrigerant designation & safety classification) for international projects.

0.4 The RFQ Shortcut — Minimum Viable Inputs

Below is a minimum viable RFQ table you can paste into an email or web form to get a serious quotation, not a “budget number.”

0.5 Release-to-Ship Gate

EPC teams get burned when the unit is “mechanically complete” but can’t ship because documents, punch items, or preservation are not closed. The clean solution is to contractually define a Release-to-Ship Gate. This gate ties FAT closure + databook completeness + packing/preservation to shipment approval.

• FAT completed + punch list closed (or agreed Category A/B/C rules)
• Pressure test / leak test records complete
• Instrument calibration certificates compiled
• Electrical test records (IR, continuity, functional checks) compiled
• Preservation applied (desiccant, nitrogen purge if required, rust prevention)
• Packing list + lifting plan + shipping splits confirmed
• Final databook index issued (as-built docs, drawings, QA records)

Part 1 — Industrial Refrigeration Unit 101

1.1 Where IRUs Are Used in EPC Projects

In chemical, oil & gas, LNG/LPG, marine, and energy projects, refrigeration is frequently tied to yield, safety margins, and uptime—not just comfort cooling. A refrigeration trip can stop a downstream process, trigger flaring, or delay cargo operations.

That’s why EPC buyers evaluate IRUs like a process-critical package: interface discipline, controls stability, and evidence-based QA/QC often matter more than a small CAPEX difference.

1.2 What an IRU System Contains

An EPC-friendly way to explain an IRU is to break it into five functional blocks. This block view also makes bid leveling cleaner, because you can compare vendors subsystem-by-subsystem:

1. Compression Block — compressor + motor/VFD + oil system
2. Condensing / Heat Rejection — air or water cooled
3. Expansion & Control — valves + capacity control
4. Evaporation / Chilling — evaporator or secondary loop
5. Safety + Controls — PLC, trips, relief, detection

Part 2 — How EPC Should Specify an Industrial Refrigeration Unit

EPC teams don’t “lose time” because refrigeration is complex. They lose time because the inputs are incomplete, and the vendor is forced to guess. The guess turns into a “budget quote,” then a redesign, then a change order.

2.1 The #1 Root Cause of IRU Schedule Delay: “TBD Inputs”

In refrigeration packages, a small “TBD” is rarely small. If evaporating temperature is unclear by 2–3°C, it can change compressor size, motor power, oil cooling, condenser selection, piping sizes, and even electrical classification.

• TBD duty → vendor selects conservative equipment → process updates → duty changes → compressor/motor changes → base frame changes → layout changes → transport split changes → FAT scope expands → schedule slips

2.2 “Freeze-First” Inputs

2.2.1 Duty and Temperature Levels

You must clearly define one of these:

• Chilled fluid supply/return temperature (e.g., brine -10°C supply / -6°C return) or
• Evaporating temperature (refrigerant-side)

2.2.2 Load Profile

A refrigeration unit is not judged only at “peak duty.” It must operate stable at minimum load, during ramping, and across daily/seasonal swings. EPC should provide: Peak / Normal / Minimum load; Ramp rate; Operating hours (24/7 or batch); Start-up and upset cases.

2.2.3 Site Conditions

Refrigeration packages are sensitive to condensing conditions. EPC must give design points, not average weather. For air-cooled: summer dry bulb and winter minimum. For water-cooled: cooling water supply temperature range, water quality limits, max allowable approach and ΔP. For seawater/coastal: corrosion strategy becomes a major design driver.

2.2.4 Utilities and Electrical Constraints

EPC should specify: voltage/frequency tolerance; motor starting constraints (DOL allowed? soft start? VFD required?); power quality requirements (harmonics limits if VFD used); black-start / restart logic requirements.

2.2.5 Hazardous Area Classification

If hydrocarbons or flammable refrigerants are in scope, or if the installation area is classified, EPC must state: Zone/Division; Gas group; Temperature class; Boundary of classified area. This impacts motor/instrument selection, wiring method, ventilation/detection philosophy, enclosure ratings, cost and lead time.

2.3 Datasheet Discipline: A Clean IRU Datasheet Outline

2.3.1 IRU Datasheet Sections (Recommended)

1. Project & design basis
2. Operating cases (peak/normal/min/transient)
3. Cooling medium conditions (air/water/seawater)
4. Refrigerant strategy (preferred + acceptable alternatives)
5. Performance requirements
6. Mechanical requirements (materials, corrosion, insulation, noise)
7. Electrical requirements
8. Controls & interface requirements
9. Testing & documentation requirements (ITP/FAT/databook)

2.3.2 “Performance Requirements” You Should Always Include

2.4 Interface Matrix (Battery Limits): How EPC Prevents Scope Fights

2.5 Vendor Questions That Instantly Improve Bid Quality

2.5.1 Technical Clarity Questions

• Provide assumptions list (explicitly) and identify any missing RFQ inputs.
• Provide capacity control method and minimum stable load.
• Provide oil management philosophy and oil carryover expectations.
• Provide relief philosophy and relief destinations.
• Provide performance curves across operating range.

2.5.2 Execution and Schedule Questions

• Provide a document schedule aligned with engineering milestones.
• Provide ITP with hold points and required witness notices.
• Provide FAT plan and acceptance criteria.
• Provide packaging/preservation plan and shipment split list.
• Provide critical spares list and lead time.

2.6 The RFQ Pack Structure

2.7 Bid-Leveling Compliance Matrix

Part 3 — Technology Selection for Industrial Refrigeration Units

Technology selection becomes simple when you stop asking “Which refrigerant is best?” and start asking: “Which architecture has the lowest total project risk under our duty + site + compliance constraints?”

3.1 EPC Selection Framework

Before comparing cycles, EPC should freeze four decision anchors:

1. Temperature levels (single temp vs multiple temp consumers)
2. Load profile (steady vs highly variable; turndown requirement)
3. Site constraints (ambient, cooling medium, power limits, plot space, noise)
4. Compliance constraints (hazardous area, safety classification, regional regulations)

3.2 Cycle Architecture Options

3.2.1 The Common Architectures EPC Will See

A) Single-stage

• Best when: temperature lift is moderate; stable duty; schedule is tight.
• Why EPC likes it: fewer components, simpler controls, easier commissioning.
• Typical risk: limited efficiency when temperature lift grows; turndown may need careful control.

B) Economized / vapor-injection

• Best when: higher lift than single-stage; EPC wants better efficiency but manageable complexity.
• Why EPC likes it: often strong ROI with limited additional hardware.
• Typical risk: more sensitive to control tuning and operating envelope.

C) Two-stage compression

• Best when: suction temperatures are low or pressure ratios are high.
• Why EPC likes it: better thermodynamic fit; can reduce discharge temperatures and improve reliability.
• Typical risk: more equipment and controls; more commissioning steps.

D) Cascade systems

• Best when: very low temperatures or when safety/regulatory strategy pushes a split approach (e.g., CO₂ in the low-temp side).
• Why EPC likes it: can match extreme temperature requirements while managing risks and efficiencies.
• Typical risk: more interfaces, more trip modes, more FAT complexity.

E) CO₂ transcritical systems

• Best when: specific low-temperature needs, footprint sensitivity, or where project strategy prefers CO₂.
• Why EPC likes it: compactness and the long-term “natural refrigerant” direction.
• Typical risk: pressure-driven design and relief strategy are central; engineering discipline must be high.

3.3 Direct Expansion (DX) vs Secondary Loop (Brine/Glycol)

3.3.1 DX (refrigerant goes to the evaporator/consumer)

• Pros: fewer heat transfer steps; potentially higher efficiency.
• Cons: refrigerant distribution becomes a larger safety and leak-management topic; more field piping complexity.

3.3.2 Secondary loop (refrigeration unit chills brine/glycol; fluid goes to consumers)

• Pros: isolates refrigerant to the skid area; simplifies consumer-side distribution; often easier for multi-consumer plants.
• Cons: extra heat transfer step; pump power; requires careful freeze protection and fluid management.

EPC rule of thumb: If you have many consumers and long distribution piping, secondary loop often reduces execution risk. If you have one major consumer and tight approach requirements, DX can be competitive—if safety and installation discipline are strong.

3.4 Heat Rejection Selection

3.4.1 Air-cooled

• Best when: water is limited; simple utilities preferred; remote sites.
• Risks: performance sensitivity in hot climates; fan noise; footprint.

3.4.2 Water-cooled

• Best when: reliable cooling water is available; EPC wants stable operation across seasons.
• Risks: water treatment/quality, fouling, maintenance, cooling tower integration.

3.4.3 Seawater/coastal

• Best when: seawater is the only viable medium; offshore/coastal facilities.
• Risks: corrosion, biofouling, filtration, material selection and lifecycle maintenance planning.

3.5 Regulatory Reality Check

If your EPC projects serve Europe or European OEM/end-users, refrigerant choices can be affected by the EU F-gas Regulation (EU) 2024/573, which applies from 11 March 2024. This means refrigerant selection isn’t only technical—it can impact availability, lead time, and lifecycle servicing. Your RFQ should request acceptable refrigerant alternatives and require the vendor to state assumptions and compliance basis clearly.

3.6 EPC Decision Matrix

3.7 Packaging Patterns

A) Single integrated skid

• One base frame, pre-wired, pre-piped
• Best when transport limits allow

B) Split modules

• Compression skid + condenser module + pump/utility module
• Clear interfaces are mandatory (piping tie-ins, signal ownership)

C) Hybrid (factory packaged core + site-installed heat rejection)

• Common when cooling towers or seawater systems are EPC-owned

Part 4 — Compressor Packages & Rotating Equipment

In most EPC industrial refrigeration projects, the compressor package is where performance, reliability, and schedule risk converge. The compressor itself is rarely the single point of failure—oil management, liquid handling, capacity control, and interface discipline are the usual root causes of trips and redesign.

4.1 What EPC Must Decide Before Vendors Start Guessing

1. Compressor type (screw / reciprocating / centrifugal)
2. Capacity control philosophy (slide valve / VFD / parallel compressors / hot-gas bypass)
3. Oil management concept (separation, cooling, return strategy, monitoring)
4. Protection & automation scope (local PLC logic, permissives, trip causes, DCS interface)

4.2 Compressor Type Selection

4.3 Screw Compressors

Screw compressors are popular in industrial refrigeration because they package well on skids, are tolerant to practical plant conditions, and offer multiple capacity control options. EPC should treat the screw compressor package as a system module, not a single machine, and specify the oil system and protection logic explicitly.

4.3.1 Capacity Control Options

• Slide valve unloading — widely used; efficiency can drop at low loads
• VFD speed control — better part-load efficiency; harmonics/motor selection considerations
• Parallel compressors — high turndown with stable control; higher CAPEX
• Hot gas bypass — stability tool, but can waste energy; use intentionally

4.4 Reciprocating Compressors

Reciprocating compressors remain competitive where the project values intermittent operation or smaller duty packages. The EPC caution is that reciprocating machines introduce more pulsation/vibration management work, and long-term performance depends heavily on maintenance discipline.

4.5 Centrifugal Compressors

Centrifugal compressors are typically selected for large capacity, where stable duty and high efficiency matter. In major hydrocarbon and process services, centrifugal compressor packages are frequently specified against API 617. For industrial refrigeration, the key EPC risk is surge margin management across all operating cases defined in the RFQ.

4.6 Capacity Control Strategy

A refrigeration system that meets peak duty but hunts at part load is a plant reliability problem. EPC should require vendors to state minimum stable capacity and how it is achieved.

4.7 Oil Management

In EPC execution, oil management is often the most under-specified area—until commissioning. EPC should require the vendor to submit an oil management narrative covering: separation, cooling, return, monitoring, and failure modes.

4.8 Liquid Handling and Protection

Liquid slugging is one of the fastest routes to compressor damage. EPC should ensure the package includes clear measures to avoid liquid carryover under all expected cases: start-up, shutdown, upset, and defrost.

• Suction accumulator / knock-out protection (as applicable)
• High-high liquid level trips (where relevant)
• Suction superheat or temperature stability monitoring
• Discharge temperature protection
• Oil pressure differential protection
• Vibration monitoring (critical packages)
• Permissives that prevent restart into unsafe states

4.9 Vibration, Piping Loads, and Skid Engineering

Many field failures are not “compressor design issues.” They are installation-induced: piping loads, misalignment, resonance, or insufficient supports. EPC should require the vendor to state allowable nozzle loads, skid stiffness philosophy, and transport/lifting design assumptions. If the unit is modular or split, EPC must require the vendor to define field tie-in tolerances and re-alignment requirements.

4.10 EPC RFQ Checklist (Compressor Package)

4.11 FAT Witness Points

Part 5 — Refrigerants + Safety/Compliance Landscape

Refrigerant selection is not a “thermodynamics preference.” In EPC projects, it is a compliance-and-operability decision that determines: equipment location, ventilation and detection, relief philosophy, hazardous-area implications, operator training, long-term servicing, and refrigerant availability.

5.1 EPC Reality: Refrigerant Choice Changes Scope, Layout, and Documentation

In real procurement, the refrigerant decision often shifts the battery limits. One refrigerant may push the design toward a machinery room concept with ventilation and detection requirements, while another enables more outdoor packaging—changing civil works, E&I scope, and schedule risk.

5.2 Key Standards EPC Teams Reference

ASHRAE Standard 15 is a widely used safety standard specifying safe design, construction, installation, and operation of refrigeration systems. ASHRAE Standard 34 provides refrigerant designation and safety classification (toxicity/flammability classes). ISO 5149 (multi-part) provides safety and environmental requirements for refrigerating systems. In Europe, EN 378 is commonly referenced for safety and environmental requirements across design, installation, and operation/maintenance contexts.

5.3 Refrigerant Families: What EPC Buyers Must Evaluate

5.4 Region and Policy Impact: Plan for Lifecycle Availability

If your end user or market is Europe, refrigerant strategy is increasingly influenced by regulation. The EU F-gas Regulation (EU) 2024/573 started to apply on 11 March 2024 and applies to fluorinated greenhouse gases. For EPC procurement, treat some refrigerants as a lifecycle procurement item: ask vendors to quote the preferred refrigerant plus one acceptable alternative, and to state compliance basis and assumptions clearly.

5.5 Ammonia (NH₃) Projects: What EPC Must Address Upfront

Ammonia refrigeration is widely used industrially, but it demands disciplined safety management. Industry practice often references IIAR standards for ammonia system design.

• Define equipment location strategy (machinery room vs outdoor, and any site constraints).
• Require a detection + ventilation philosophy and tie it to alarms/interlocks.
• Require a relief philosophy (what protects what, where relief discharges, and how it is made safe).
• Require O&M and training deliverables as part of the package scope.

5.6 EPC Refrigerant Selection Scorecard

5.7 RFQ Clause Set: “Compliance Basis”

Insert into RFQ (vendor to respond):

1. State refrigerant(s) proposed and the safety classification basis.
2. State system safety compliance basis and how it impacts location, ventilation, detection, and relief philosophy.
3. Provide an assumptions list (explicitly) and list any RFQ inputs required to remove assumptions.
4. Provide an alternative refrigerant option and identify scope/performance changes.
5. Provide O&M deliverables that match the chosen compliance basis (procedures, training scope, spare parts philosophy).

Part 6 — Packaged Skid vs Stick-Built: EPC Execution Model

For EPC projects, the “best refrigeration technology” can still fail commercially if the delivery model is wrong. The execution choice determines how many interfaces you must manage, how much risk you carry on-site, and whether commissioning starts with a stable baseline or a long punch-list fight.

6.1 Definitions EPC Teams Should Align On

Packaged skid-mounted IRU typically means: steel base frame(s) with pre-installed compressors, vessels, piping, valves; pre-wired E&I, local control panel; factory FAT with defined acceptance evidence; transport-ready preservation and packing plan.

Stick-built / site-built IRU typically means: major components shipped loose; field piping fabrication and E&I installation executed on site; more site commissioning dependency and greater interface uncertainty.

6.2 When Packaged Skid Wins

Packaged skid execution is usually the best choice when: the refrigeration unit is package-critical (ties to major process start-up); the site has limited skilled labor or short shutdown windows; quality evidence and documentation closure must be auditable; project risk is high for interface integration.

• Reduced site uncertainty: fewer field welds, fewer late instrumentation surprises
• Earlier issue resolution: problems discovered in factory are cheaper to fix
• Evidence-based handover: databook completeness improves acceptance and warranty clarity
• Safer commissioning: interlocks and permissives can be proven before energization on site

6.3 When Stick-Built Is Unavoidable

Stick-built/site assembly becomes more realistic when: the system is too large for transport splits without major re-engineering; site heat rejection is fully integrated with cooling towers/seawater systems owned by EPC; local code or site restrictions require field assembly; plot plan access or lifting constraints prevent large modules.

When you must go stick-built, the most important control is to modularize anyway: define pre-tested “factory-built cores” (compression skid, oil skid, control panel) and limit field assembly to tie-ins.

6.4 The “Modular Split” Playbook

A common, EPC-friendly split for large IRUs:

• Module A — Compression & Oil skid
• Module B — Condensing / heat rejection module
• Module C — Pump/secondary loop module (if brine/glycol)
• Module D — Electrical / controls room (if required by classification)

EPC must define (or vendors will define it for you): transport envelope (max length/width/height, max module weight); lifting method and crane limits; tie-in locations and tolerances; which loop checks happen in factory vs site; cable routing philosophy between modules.

6.5 Release-to-Ship Gate: The Contractual Control

The RTS Gate is a procurement mechanism that turns shipment readiness into a measurable handover checkpoint.

6.6 ITP & FAT Hold-Point Map

6.7 Packaging, Preservation, and Marine Transport Discipline

If you target marine/offshore or long ocean shipments, preservation is a reliability requirement: corrosion, moisture ingress, and vibration damage can convert a successful FAT into a failed commissioning. EPC should demand preservation class, corrosion protection method, shock/vibration considerations, and clear storage/handling instructions.

Part 7 — Mechanical Design Essentials

In EPC refrigeration projects, mechanical design is where “a good cycle” becomes either a stable utility or a trip generator. The biggest failures come from repeatable issues: liquid carryover, unstable oil return, poor piping supports, corrosion under insulation, and mismatched relief/receiver philosophy.

7.1 Piping Design That Prevents Trips

Most nuisance trips originate from suction-side instability: liquid migration, inadequate superheat control, oil return collapse at low load, or piping that behaves differently than the vendor modeled. EPC should specify operating envelope, turndown, transients, and layout constraints.

7.2 Receivers, Separators, and Vessels

EPC often underestimates how many vessels exist inside a packaged refrigeration unit: receivers, separators, accumulators, oil pots, and sometimes economizers/flash tanks. These vessels define hold-up volume, control stability, and safety relief philosophy.

7.3 Relief Philosophy and Safe Discharge

Relief devices drive layout (discharge routing), safety interfaces, and sometimes civil requirements. If EPC does not require the vendor to state a relief philosophy at RFQ stage, you risk late changes to skid arrangement or added scope such as vent stacks and detection.

1. Provide a relief philosophy summary (what protects what, and why).
2. Identify relief discharge destinations (to atmosphere, safe location, recovery, etc.).
3. State assumptions for blocked-in cases, fire case if applicable, and ambient extremes.
4. Provide a list of relief devices with set pressures and the design basis.

7.4 Materials & Corrosion Strategy

Industrial refrigeration skids frequently operate in harsh environments: coastal plants, LNG terminals, chemical parks, offshore modules. EPC should request a clear corrosion design basis and connect it to: material selection, coating system, insulation system and sealing, drainability and water traps, preservation for shipment/storage.

7.5 Heat Exchangers Inside IRUs

EPC must force comparability by requiring vendors to state: thermal design basis (approach, pinch, fouling allowance), pressure drop limits, materials and corrosion basis, test/inspection method and acceptance criteria.

7.6 Mechanical RFQ Checklist

Part 8 — Electrical, Automation, Interlocks, and SIS/ESD Interfaces

Industrial refrigeration units succeed or fail at start-up based on one question: who owns the logic. When the vendor PLC, EPC DCS, and the site ESD/SIS responsibilities are not defined early, the result is predictable—late changes, unclear permissives, “temporary bypass culture,” and nuisance trips that destroy confidence in the package.

8.1 Control Architecture Options

Model A — Vendor PLC is primary (package-controlled)
The refrigeration package runs itself; EPC DCS monitors and sends high-level commands (start/stop, setpoints, mode selection). This is typically fastest for packaged skid projects.

Model B — EPC DCS is primary (plant-controlled)
DCS runs the control loops and sequencing; the vendor provides instrumentation and “dumb” hardware protections. This can work but increases integration risk and commissioning duration.

Model C — Hybrid (most common on complex sites)
Vendor PLC handles local high-speed protections and sequencing; DCS manages operating modes, coordination with upstream/downstream units, and plant-wide permissives.

8.3 The “Permissive Stack”

A refrigeration unit should never start because an operator presses “Start.” It should start because all permissives are proven healthy and stable.

1. Utility readiness: power healthy, instrument air available, cooling medium ready
2. Mechanical readiness: lube/oil conditions stable, valve lineup correct
3. Process readiness: load acceptance path open, minimum flow/return conditions met
4. Safety readiness: gas detection status, ventilation status, ESD inputs healthy
5. Control readiness: sensor validation, setpoints loaded, interlocks enabled (no bypasses)

8.4 Interlocks vs Trips vs ESD: Write Definitions Into Your RFQ

8.5 Signal List Discipline: The IO List That Makes Bids Comparable

8.6 Communications: Keep It Boring and Proven

• If DCS integration is required: specify your standard (e.g., Modbus TCP, Profibus/Profinet, OPC UA, Ethernet/IP) and require a test plan.
• If the site is strict on safety: require safety-relevant signals to be hardwired unless the owner approves safety networking.

Key deliverable: a one-page Interface Control Document (ICD) that lists: protocol, addressing, tag naming rules; time sync requirements; network segmentation responsibilities; FAT simulation approach for DCS handshake.

8.7 VFDs, Harmonics, and Power Quality

Variable frequency drives often improve part-load efficiency and control stability—but they introduce electrical questions EPC must close early: who supplies the VFD; harmonic limits and mitigation (filters); motor insulation and cable length considerations; EMC and grounding requirements; starting philosophy and power dip constraints.

8.8 Hazardous Area Electrical

When the unit is installed in a classified area, electrical scope expands quickly: motors, instruments, junction boxes, cable glands, and panel purge/pressurization requirements may change.

• RFQ must include: Zone/Division, gas group, temperature class; boundary of classified area relative to skid; whether the vendor must provide Ex-rated instruments and wiring accessories; whether control panels are in safe area, purged, or Ex-certified.
• Bid-leveling tip: force vendors to list every Ex-rated item in a separate schedule so you can compare apples-to-apples.

8.9 FAT for Controls: Test What Matters

8.10 E&I RFQ Checklist

8.11 Bid-Leveling: Control Maturity Scorecard

Part 9 — QA/QC, ITP, FAT, Documentation, and Release-to-Ship Gate

Industrial refrigeration packages do not slip schedule because fabrication is slow. They slip because evidence closure is slow: hold points missed, FAT done without disciplined punch closure, and databooks issued “after shipment.” The best-performing EPC teams define three things at RFQ stage: (1) ITP hold points, (2) FAT acceptance evidence, and (3) a Release-to-Ship (RTS) Gate.

9.2 What EPC Should Buy: “Evidence-Based Deliverables,” Not Promises

A practical mindset is: if it cannot be audited, it cannot be accepted. That is why the RTS gate must reference evidence, not intent.

9.3 ITP: The Hold Points That Actually Prevent Schedule Disasters

Your ITP should focus on irreversible risks: pressure integrity, cleanliness/dryness, safety devices, control logic proof, and preservation/packing.

9.4 FAT: What to Test, What to Record, How to Close Punches

9.4.2 Punch List Rules

9.5 Documentation (MDR/VDR): The Databook Structure EPC Should Enforce

9.6 Release-to-Ship (RTS) Gate: The Commercial Control Point

9.7 Procurement Clauses That Make QA/QC Enforceable

1. Milestone-linked documents: “Key documents are due before fabrication/FAT/shipment gates.”
2. Witness notice requirement: “Vendor shall give X days notice for hold points.”
3. Punch categorization: “Category A must close before shipment.”
4. RTS Gate: “Shipment release only after RTS acceptance.”
5. Deviation control: “Any deviation requires written approval and updated MDR.”

Part 10 — EPC Procurement Playbook

A refrigeration package is one of those EPC purchases where “cheap” can become expensive very fast. The winning procurement strategy is not simply negotiating price—it is locking scope, enforcing evidence gates, and making bids comparable.

10.1 RFQ Pack Structure

10.2 Vendor Shortlisting (Pre-Qualification)

Red Flags (Treat as “High-Risk Deviations”)

• Refuses to declare assumptions (“we will confirm later”)
• Cannot provide sample FAT evidence or databook index
• Quotes with broad exclusions (controls, ESD interface, preservation, documentation)
• No defined punch categorization rule (A/B/C)
• Lead time is “aggressive” but not supported by a manufacturing schedule

10.3 Bid Leveling

10.3.3 Total Cost of Ownership Quick Model

10.4 Deviation Control

10.5 PO/Contract Levers That Protect EPC Schedule

1. Milestone document issuance: P&ID/C&E/GA due before fabrication; FAT docs due before FAT; databook threshold at RTS.
2. ITP hold points + notice: vendor must notify EPC X days prior to hold points.
3. Punch categorization: Category A must close before shipment; B/C rules defined.
4. Release-to-Ship (RTS) Gate: shipment only after evidence acceptance.
5. Assumption governance: any assumption becomes a tracked open item with a closure date.
6. Performance acceptance: acceptance criteria tied to defined duty cases (not vendor “standard conditions”).

10.6 Award and Post-Award Kickoff

• Confirm battery limits and interface matrix
• Freeze duty cases and assumptions closure schedule
• Approve MDR dates and document flow
• Confirm ITP hold points and witness notice rules
• Confirm FAT plan, punch categorization, and evidence format
• Confirm shipping splits, preservation class, packing plan
• Confirm communication protocol and DCS/ESD responsibilities

Part 11 — Commissioning, Start-Up, and Performance Acceptance (SAT)

Commissioning is where an IRU transitions from “equipment delivered” to “plant-ready utility.” The biggest time losses come from interface ambiguity: who owns permissives, who closes punch items, what evidence is required for acceptance, and what “performance” means under real site conditions.

11.1 Commissioning Strategy: Treat SAT as “FAT Replay + Site Interface Proof”

The fastest EPC startups use a simple principle: do not invent new tests on site. Instead, replay FAT tests under site conditions, then add only the site-specific checks: utilities, tie-ins, and plant control/ESD interfaces.

11.2 Pre-Commissioning Checklist

11.2.1 Mechanical Completion (MC) — Minimum Readiness Items

11.2.2 Electrical & Instrumentation Readiness

11.3 Pre-Startup Safety Review (PSSR)

For industrial refrigeration, PSSR is the formal moment where EPC confirms: safety devices are installed and functional; relief/discharge routing is safe; detection/ventilation (if applicable) is active; operators have procedures and escalation rules.

11.4 Start-Up Sequence

1. Cold checks (no power / limited power) — final walkdowns, valve lineup confirmation, mechanical clearances
2. Electrical energization — control power on, verify HMI/PLC health, verify sensor readings are sane
3. Dry functional tests — permissives, trips, alarms, ESD input simulation (no rotating run yet)
4. Oil system proving — oil heaters (if used), oil DP stability, oil cooling readiness
5. Rotation check / bump test — confirm rotation direction and basic mechanical health
6. Initial run at minimum load — stabilize suction/discharge pressures, verify no hunting, trend recording
7. Load-in and envelope proving — ramp load by defined steps; verify control stability and alarm behavior
8. Steady-state stabilization — hold stable operation for defined period before performance acceptance

11.5 SAT Test Set

11.6 Performance Acceptance: Define Acceptance on Your Operating Cases

11.7 The “First 72 Hours” Stabilization Playbook

Further reading: ASHRAE commissioning resources (includes HVAC&R commissioning guidance such as Guideline 1.1); ANSI/IIAR 5 (start-up and commissioning for closed-circuit ammonia refrigeration systems); ISO 5149 (Parts 1 and 4 are directly relevant to handover and O&M expectations).

Part 12 — O&M, Spares, and Lifecycle Services

A refrigeration unit can pass FAT and still become a long-term headache if the owner cannot operate it predictably and maintain it economically. EPC decision-makers typically care about three lifecycle outcomes: (1) stable operation at real load ranges, (2) fast recovery from trips, and (3) spares/service that match the project’s uptime target.

12.1 O&M Deliverables: What Must Be Handed Over

12.2 Spares Philosophy: The 3-Tier Model

12.3 Maintenance Plan That Prevents “Mystery Trips”

12.4 Training: The Cheapest Uptime Insurance

A packaged IRU often fails in the first year because operators do not trust it—so they bypass logic, run in manual, or ignore early warnings. EPC should require training that includes: a start-up simulation (permissives and trip logic); “what to do when it trips” playbook; a sign-off record (who was trained, when, and on what).

12.5 Lifecycle Service Model

Part 13 — Case Studies and Common EPC Mistakes

Case 1 — Brine/Glycol Chiller Skid for a Chemical Plant

This scenario represents projects where the buyer’s pain is variable load stability and fast commissioning. Secondary loops (brine/glycol) are often chosen to reduce distributed refrigerant risk and simplify plant tie-ins.

Evidence-based execution: FAT trend logs at minimum load (proves no hunting); Cause & Effect simulation sign-off (proves permissives/trips); RTS gate with databook index threshold (prevents “docs after ship”).

Case 2 — Hydrocarbon Refrigeration Skid (Hazardous Area)

This scenario fits projects with flammable refrigerants or hydrocarbon service, where EPC’s biggest concern is hazardous area compliance and control discipline.

Case 3 — NH₃/CO₂ Cascade Rack (Low Temperature)

This scenario represents cold-chain or industrial low-temperature duties where cascade is chosen to match temperature levels while managing safety and system constraints. For ammonia systems, EPC stakeholders frequently expect commissioning aligned to ANSI/IIAR 5 practices.

Case 4 — Coastal/Seawater Cooling Execution

This scenario fits marine/coastal EPC projects where seawater integration makes corrosion strategy the primary long-term risk driver. The case emphasizes: materials selection basis, filtration/biofouling approach, preservation for ocean transport, and CUI prevention.

• Material list and corrosion design basis (including insulation sealing and drainability)
• Preservation class (months, storage assumptions, packing evidence photos)
• Site acceptance: seawater quality assumptions and acceptance envelope

Case 5 — Retrofit/Upgrade (Lifecycle Risk, Refrigerant Availability)

Retrofits often happen when the owner’s priorities shift: energy efficiency, reliability, or regulatory/lifecycle constraints.

13.6 The “Top 10” EPC Mistakes

Part 14 — Toolkit Appendices: Downloadable EPC Templates

14.1 How to Use This Toolkit

Step 1 — Pick your delivery model: packaged skid vs modular split vs site build.
Step 2 — Fill Template A (Duty + Site Conditions) and send it to vendors.
Step 3 — Require vendors to reply using Template B (Compliance + Deviations).
Step 4 — Level bids using Template C (Scorecard + TCO quick model).

14.2 Toolkit Index

14.3 Template A — IRU RFQ Datasheet (Multi-Case)

A1) Project & Design Basis

A2) Operating Cases (Required)

A3) Site Conditions + Utilities

14.4 Template B — Interface Matrix (Battery Limits)

14.5 Template C — Controls Package Sheet (IO + C&E Outline)

C1) Control Ownership Model

C2) Signal List Outline (Vendor Must Complete)

14.6 Template D — Bid Leveling Pack

D1) Compliance Matrix

D2) Deviation Log (Mandatory Attachment)

14.7 Template E — ITP + FAT Checklist

E1) ITP Hold Points

E2) FAT Acceptance Evidence (Minimum)

• Trend logs at min/normal load
• Proof of permissives/trips without bypass
• VFD/motor settings snapshot (if used)
• Calibration certificates for critical instruments
• Punch list categorized (A/B/C) with closure rules

14.8 Template F — Release-to-Ship Gate (RTS)

14.9 Template G — Databook / MDR Index

14.10 Template H — Spares Tier Sheet

14.11 Template I — O&M Maintenance Plan

14.12 Template J — EPC Glossary

• IRU (Industrial Refrigeration Unit): packaged system delivering defined cooling duty at defined temps.
• Turndown: minimum stable operating capacity without hunting/trips.
• C&E (Cause & Effect): mapping of inputs/events to actions (alarms, trips, ESD responses).
• ITP: inspection and test plan with hold/witness points.
• FAT/SAT: factory/site acceptance testing.
• RTS gate: shipment release only after evidence and punch closure.
• MDR: master document register controlling deliverables and revisions.
• Battery limits: contractual scope boundary (what is included vs excluded).
• Deviations: explicit differences between vendor offer and EPC requirements.

If your project is EU-facing, explicitly track refrigerant regulatory risk: the EU F-gas Regulation (EU) 2024/573 was adopted on 7 Feb 2024 and started applying on 11 Mar 2024. European Commission