Evidence-Based Delivery for Skid Integration

Overview: Why Integration Projects Demand a Different Approach

EPC teams do not need hype. You need repeatable gates and traceable evidence — especially when the main equipment is customer-supplied and the integration scope sits between multiple vendors. Skid integration projects carry a distinct risk profile: the integrator must accept customer-supplied equipment (CSE), align it to a skid that was designed around interface data that may still be provisional, and produce a shipment that a remote EPC document control team can actually close.

This page explains how Lmart builds trust on skid integration projects: clear responsibility boundaries, controlled documentation, and shipment readiness that is audit-friendly. The six mechanisms below are not aspirational — they are the structure used on every integration project we take on.

Six Delivery Mechanisms That Protect EPC Schedule

These mechanisms are applied systematically because they address the categories of failure that recur on integration projects, not the ones that only happen once.

• Battery limits: We baseline a responsibility matrix at kickoff. Tie-in locations and ratings, E&I boundaries (terminal schedule / I/O ownership), drains and vent routing, packing and preservation scope — all defined before fabrication starts.
• Controlled documentation: One document register baseline (MDR/VDRL mapping). Revision rules agreed upfront — what triggers re-approval. “Report issued” is treated as a milestone, not just “test performed.”
• CSE receiving gate: Customer-supplied equipment is inspected on arrival with a formal checklist and photo record. EPC gets a clear three-way decision: proceed / proceed with conditions / hold for resolution. No verbal “looks fine.”
• ITP hold points: Witness windows planned around irreversible steps: CSE fit-up acceptance, baseframe completion, pressure and leak checks (if in scope), functional checks / FAT, and packing evidence before ship release.
• FAT / functional checks: For integration projects, FAT proves assembly correctness and interface alignment, E&I checks within agreed boundary, alarm and interlock steps for what the vendor controls, and punch categorization with closure rules.
• Shipping readiness: Packing and preservation are part of the ship-release evidence pack: sealing and protection records, COG and lifting markings, bracing and shock indicators (when specified), and a photo set tied to the packing record.

EPC teams do not need hype. You need repeatable gates and traceable evidence — especially when the main equipment is customer-supplied and the integration scope sits between multiple vendors.

Scope Boundary Table (Battery Limits)

Use this in your RFQ and kickoff minutes. Freeze vendor vs EPC/site responsibilities before fabrication begins. Any item left as “TBD” in this table is a future change order or a future rework event.

Scope Item	Vendor (Skid)	EPC / Site	Notes — Lock at Kickoff
Skid base frame + structural steel			COG, lifting points, transport restraints
Customer-supplied equipment (CSE) mounting			CSE interface dimensions, hold-down pattern
On-skid piping to tie-in flanges			Tie-in coordinates, flange ratings, orientation
Instruments and tags (on-skid)			Ranges, calibration evidence
Control panel / junction box (if in scope)	/ Opt	/ Opt	I/O ownership, protocol, ESD interface
E&I boundary (terminal schedule)			Termination points, cable responsibility
Vent / drain routing off-skid			Vendor provides loads; EPC routes
Electrical feeder to skid			Voltage, frequency, starter/MCC boundary
Foundations / civil			Vendor provides loads / COG / lifting plan
Packing / preservation			Storage duration, shipment mode constraints
Site receiving inspection			Vendor provides ship-release evidence pack

ITP Hold Points — Protecting Schedule at Each Gate

Witness windows are planned around irreversible steps at kickoff — not booked last-minute. An inspection that slips by one week cascades into multi-week delays when it sits on the critical path.

#	Hold / Witness Point	What Is Verified	Why Irreversible
H1	CSE receiving gate	Checklist + photo record; proceed / conditions / hold decision issued	Retrofitting missing accessories mid-assembly doubles labour
H2	CSE fit-up acceptance	Interface dimensions, hold-down pattern, nozzle / flange alignment	Structural rework after welding is costly and time-consuming
H3	Baseframe completion + markings	COG mark, lifting lug ratings, transport restraint points	Later changes require re-analysis and re-stamping
H4	Pressure / leak checks (if in scope)	Test procedure + calibrated gauges + signed report	Remediation after insulation / fireproofing applied is expensive
H5	Functional checks / FAT	Assembly correctness, E&I within boundary, alarms / interlocks	Site commissioning delays are the most expensive correction
H6	Packing + preservation + ship release	Photo set, COG/lifting marks, desiccant / VCI / restraints, release note	Transit damage without evidence pack has no insurance path

FAT Evidence — Interface Proof, Not a Factory Tour

For integration projects, FAT is about proving the integration scope is correct and closable before the package leaves the shop floor. The following four areas are covered in sequence, with evidence referenced throughout.

FAT Area	What Is Verified	Evidence Required
Assembly correctness	Interface alignment between CSE and skid confirmed; nozzle orientations, pipe routing, and clearances match approved GA	Marked-up GA with sign-off
E&I within boundary	I/O mapping checked against terminal schedule; point-to-point verification within agreed vendor boundary; communications tests where applicable	Signed I/O loop records
Alarms and interlocks	Alarm and interlock steps verified for instruments and controls within vendor scope; setpoint schedule confirmed; out-of-scope items formally noted	Signed alarm/interlock test sheet
Punch categorization	Category A items (ship-stop) closed before release; Category B items documented with agreed closure plan	FAT report with all evidence referenced

Vendor Data Book (Turnover Package)

If EPC document control cannot close the register, the project schedule pays the price. Agree the index at kickoff and track it weekly. The format below is Lmart’s standard for skid integration projects.

Vol.	Contents
1	Final document register (status + revision history + transmittals)
2	Scope boundary + responsibility matrix + tie-in list (mechanical and E&I)
3	Approved battery limits + interface list
4	GA + COG / lifting plan + transport restraints + access clearances
5	P&ID / schematic + line list + valve list (as applicable to package)
6	CSE receiving record + photos + proceed / conditions / hold decision
7	Electrical: SLD / wiring / terminal schedule
8	Controls: I/O list, interlock list, alarm schedule, comms mapping
9	ITP + hold/witness records + NCR disposition
10	FAT procedure + FAT report + calibration records
11	Preservation / packing record + photo set + indicator records
12	As-built drawings + redline log + final tag verification
13	Change impact forms + re-approval evidence (if changes occurred)
14	O&M notes + spares list + special tools (if applicable)

Delivery Milestones Map (EPC View)

Gate-based delivery keeps ship release predictable and document control closeable.

Gate	Milestone	Output
M0	Kickoff	Battery limits + document register agreed. Revision rules and witness plan confirmed.
M1	IFA Issue	GA / schematic / I/O issued for EPC review. CSE interface data confirmed.
M2	AFC Release	Approved drawings released. CSE delivery aligned to fabrication start date.
M3	CSE Received + Gated	Receiving checklist complete. Proceed / proceed-with-conditions / hold decision issued.
M4	ITP Hold Points Complete	Fit-up, baseframe, pressure checks (if in scope) — all witness records issued.
M5	FAT Complete	FAT report issued with all evidence. Category A punch items closed.
M6	Ship Release	Preservation / packing evidence complete. Final register closed. Release-to-ship statement issued.

Change Control — Late Changes Without Late Delivery

Changes happen on every integration project. A simple change impact form keeps them from becoming uncontrolled rework events that consume schedule without a traceable decision trail.

• Interfaces affected: Which tie-ins, terminal points, or document references are touched by the change. Prevents partial updates that leave downstream documents inconsistent.
• Documents to revise: Which drawings, lists, and data sheets must be re-issued. Re-approval trigger assessed and documented before fabrication continues.
• Retest trigger: Whether the change requires repeat of any ITP hold point or FAT check. Determined before sign-off, not discovered at final inspection.
• Schedule impact: Expected number of days absorbed. Agreed between vendor and EPC before implementation. Keeps the critical path visible and surprises off the schedule.

For EU-Bound Skids: Machinery Regulation 2023/1230

A planning note if your integrated skid will be placed on the EU market.

Topic	What EPC Typically Needs From the Integrator
Regulation basis	EU Machinery Regulation (EU) 2023/1230 repeals and replaces Directive 2006/42/EC. Application date: 20 January 2027. Confirm which basis applies to your project schedule.
Technical documentation	Clarity on who provides which parts of the technical documentation — especially for integrated assemblies with customer-supplied main equipment.
Revision control	As-built documents must match the conformity evidence plan. Agree revision rules at kickoff so final as-builts are not a last-minute retrofit.
Data book index	A structured data book supports conformity closeout. If you share your MDR/VDRL and destination (EU / US / other), we map the evidence pack to your project basis.

Summary

Skid integration projects require a different risk management posture than static equipment fabrication. The integrator does not fully control the primary asset — the customer supplies it — which means the interface, the documentation, and the shipment evidence must be managed with unusual rigour. Freeze battery limits at kickoff. Treat CSE receiving as a formal gate. Plan ITP hold points around irreversible steps with witness windows agreed in advance. Issue the FAT procedure with evidence requirements, not just a test agenda. Ship only when the Vendor Data Book register is closed. That discipline is what lets EPC document control sign off cleanly and site commissioning start without surprises.