From empty land to an operating logistics center

How to plan, contract, build, test and hand over a large-scale automated distribution center. Written for the engineer who answers for schedule, cost, quality and commissioning.

Reference project (assumed)

Site
12 ha, industrial use
Building
60,000 m² + 18,000 m² mezzanine
Capacity
250,000 shipments/day at peak
Dock doors
48 inbound · 64 outbound
Automation
7 km of conveyors, 2 sorters, 85,000 pallet positions
Duration
24 months to start of operations
Investment
USD 145 M (reference)

1. Scope, assumptions and project structure

Before scheduling anything, the engineer needs to know what is being built, what is being purchased, who delivers it and what “finished” means. This guide starts from a generic, fully automated distribution center; the figures are reference values and must be recalculated for your project.

60,000 m²floor area of the main building
480,000 m³estimated earthmoving
7,500 tstructural steel and roofing
~13,500 m³slab-on-grade concrete (e = 20 cm + fibers)

What makes this type of project different

The floor is part of the equipment

Narrow-aisle trucks, shuttles and conveyors demand floor flatness and levelness (FF/FL) that an ordinary slab does not meet. A 3 mm error here becomes a piece of equipment that does not run.

Two industries, one calendar

Civil works are driven by cubic meters, tons and curing. Automation is driven by manufacturing lead times, software and integration. They meet on the same floor, and that boundary concentrates most of the delays.

Success is measured in operation

“Finishing the construction” is not enough. The contract closes when the system reaches the committed capacity, accuracy and availability during a reliability test.

Work breakdown structure (WBS)

The WBS is the backbone: the schedule, budget, contracts, reports and documents all hang from it. If a package has no owner in the WBS, nobody controls it.

Logistics center (0) 1 Management and contracts 2 Civil works 3 MEP services 4 Equipment, automation 5 IT and software 6 Testing, start-up 1.1 Permits and design1.2 Tendering1.3 Contracts and changes1.4 Insurance, guarantees1.5 Project controls1.6 HSE and community 2.1 Site setup, earthworks2.2 Ground improvement2.3 Foundations2.4 Industrial slab2.5 Steel structure2.6 Roof and cladding2.7 Docks and paving2.8 External works 3.1 Substation and MV3.2 Low voltage3.3 Lighting3.4 Fire protection3.5 HVAC3.6 Water and plumbing3.7 Backup and UPS 4.1 Racking and mezzanine4.2 Conveyors4.3 Sorters4.4 Dim./weight/scanner4.5 Robots and shuttles4.6 Dock equipment4.7 Workstations 5.1 Network and Wi-Fi5.2 WMS / WES5.3 WCS and PLC5.4 SCADA5.5 ERP integration5.6 Cybersecurity5.7 CCTV and access 6.1 FAT6.2 Pre-comm.6.3 SAT6.4 Integrated test6.5 Pilot and ramp-up6.6 Closeout, handover
Level-2 WBS. Each box breaks down to levels 3–4 with a unique code: that code travels to the budget, schedule, contract, drawing and test protocol.
Assumptions of this guide

Owner-developer with its own engineering team; a civil general contractor; an automation integrator with equipment suppliers; owner's inspection (ITO, independent technical oversight). Chilean regulations are used as the reference (OGUC, the General Urban Planning and Construction Ordinance; NCh 2369, seismic design of industrial structures; SEC, the electrical and fuels regulator; DOM, the municipal building authority). Adapt names and requirements to the regulations of your country.

2. Contracting strategy and packages

The contract is the most powerful control tool you have. Whatever was not written down (scope, interfaces, acceptance criteria, penalties) becomes a claim.

Delivery models

ModelHow it worksAdvantageMain riskWhen it fits
Separate packages (multi-contract)The owner contracts civil, MEP, racking, conveyors and IT separatelyBetter price per specialty; full controlInterfaces stay with the owner; cross-claimsOwner with a strong technical team
EPC / turnkeyA single contractor designs, procures and builds for a lump-sum priceOne responsible party; fixed price and scheduleLess transparency; changes are very expensiveOwner with little in-house capacity
EPCM / construction managementA construction manager coordinates contracts signed by the ownerFlexibility and coordination expertiseThe owner carries the cost riskComplex project with evolving design
Automation integrator + separate civilCivil and structure with a general contractor; the entire automated system with a single integratorOne performance guarantee for the complete systemCivil–integrator interface: floors, mezzanine structure, powerThe most common model for automated centers

Recommended contract packages

PackageContract type% of investmentTypical award windowPayment milestonesGuarantees
C-01 Earthworks and ground improvementUnit prices with re-measurable quantities7%M2 – M4Monthly progress by measured m³Performance bond 5–10%; retention 5%
C-02 Foundations, slab and structureLump sum with unit prices for changes24%M3 – M5Physical milestones: foundations, slab by strip, erection by grid linePerformance bond, advance payment bond, 24-month workmanship warranty
C-03 Roof, cladding and docksLump sum9%M5 – M7Per enclosed bay; certified watertightness10-year watertightness
C-04 Paving and external worksUnit prices4%M8 – M10Progress measured by m² and layersPerformance bond
C-05 MV/LV electrical and backup powerLump sum7%M3 – M6Substation energized, switchboards delivered, testsEquipment warranty; SEC certification
C-06 Fire protection and HVACLump sum5%M6 – M8Networks installed, hydrostatic tests, approvalFire department / insurer approval
C-07 Racking and mezzanineSupply + installation, lump sum11%M3 – M5 (manufacturing 9–11 months)10% advance · 30% manufacturing · 30% delivery · 20% installation · 10% SATAdvance payment bond; certified seismic calculation
C-08 Automation integrator (conveyors, sorters, controls)Lump sum with performance guarantee and penalties22%M3 – M7 (manufacturing 10–14 months)Engineering · FAT · site delivery · installation · SAT · final acceptancePerformance bond 10%; 10% retention until acceptance; 24-month warranty
C-09 IT: WMS/WES, network and cybersecurityLicenses + services by milestones6%M3 – M6Design · development · testing · go-liveSupport with SLA; source code escrow
C-10 Handling equipment (forklifts, AMRs, dock equipment)Purchase order5%M8 – M12Delivery and commissioningManufacturer warranty 12–24 months

The percentages are an order of magnitude; the rest of the investment covers engineering, permits, project management, insurance, contingency and start-up costs.

Clauses you should require in every contract

Scope and schedule

  • Scope with explicit exclusions and an interface matrix (who delivers what to whom and when).
  • Contractual schedule with milestones, site access date and handover date to the next contractor.
  • Rules for requesting time extensions: maximum notice period, critical path impact calculation.
  • Engineering review calendar: how many days the owner has to approve drawings.

Money and changes

  • Payment tied to measurable milestones, not only to dates.
  • Retention and advance payment with a guarantee bond.
  • Change order procedure: nothing is executed without prior signature, except documented emergencies.
  • Delay penalties (for example 0.1–0.2% of the contract per day, capped at 10%) and early-completion bonuses.
  • Price adjustment with a defined index (steel, concrete, copper, dollar).

Quality and acceptance

  • Quality plan and ITP (inspection and test plan) approved before starting.
  • FAT and SAT protocols as contract annexes, with numerical acceptance criteria.
  • Performance guarantee: capacity (items/hour), availability (≥ 98%), sorting accuracy (≥ 99.9%).
  • Delivery of documentation as a condition of final payment (as-builts, manuals, certificates).

Risk and safety

  • Construction and erection all-risk insurance, third-party liability and transport cover.
  • Risk prevention requirements, audits and grounds for work stoppage.
  • Intellectual property and control software licenses; access to source code or escrow.
  • Assignment and subcontracting: list of approved subcontractors.
The engineer's golden rule

Whenever a verbal instruction changes scope, schedule or cost, it becomes a document the same day: a letter, a signed minute or a change order. The contractor will always keep count; you must keep count too.

Change management step by step

  1. Detect. Site, engineering or the client identify a difference from the contracted scope and record it in the site logbook or in an RFI.
  2. Assess. The contractor submits the impact on cost, schedule and quality within a maximum of 7 days, backed by quantities and a critical path analysis.
  3. Validate. Owner's engineering reviews, compares against contract prices and prepares an independent cost estimate.
  4. Approve. The change committee (project manager, finance, operations) approves within authority limits and draws on the approved contingency.
  5. Execute and close. The signed change order is issued, and the budget, schedule and baseline are updated; it is filed in the change register.

3. Organization and roles

A project of this size has 15 to 30 management staff on the owner's side and more than 900 workers at peak. Defining who decides what avoids the “I thought you were doing it”.

RoleAnswers forDelivers to the project
Project managerSchedule, budget, scope, relationship with the boardMonthly report, change decisions, contingency management
Engineer in charge / owner's site manager (you)That what is built is what was planned, contracted and testedProgress control, inspection, engineering review, FAT/SAT, contract closeout
Planner / project controlsSchedule, S-curve, earned value, forecastsBaselines, weekly lookahead, critical path analysis
Cost and contracts engineerBudget, payment certificates, changes and claimsChange register, cash flow, EAC
Automation / systems engineerFunctional design, PLC–WCS–WMS interfaces, testingFunctional specification, FAT/SAT protocols, test reports
Civil / structural engineer (ITO)Technical inspection of civil works and structureHold point approvals, test reports, nonconformities
Electrical / MEP engineerPower, fire, HVACTests, SEC and fire department certifications
Health, safety and environment (HSE)Safety, health and environmentAudits, accident statistics, work permits
Quality (QA/QC)Compliance with ITP, tests and documentationNCR register, quality dossier
Operations representativeThat the design is operable; training and acceptanceOperating procedures, staffing plan and operational tests
Document controlDrawings, RFIs, transmittals, revisionsSingle register with statuses and versions

Summary decision matrix

DecisionProposesApprovesMust be consulted
Scope change under USD 50 kContractorEngineer in chargeCost
Change between USD 50 k and 500 kEngineer in chargeProject managerFinance, operations
Change above USD 500 k or one that moves the handover dateProject managerSteering committeeExecutive management, insurer
FAT acceptanceAutomation engineerEngineer in chargeOperations, QA
SAT acceptance and final handoverEngineer in chargeProject managerOperations, HSE, QA
Stop work for safety reasonsAnyoneHSE or site manager, without prior consultation—

4. Civil works plan

Civil works take up the first 14–16 months and set the pace for everything else. The logical order is: understand the soil, prepare it, build the foundations, pour the floor, erect the structure, close the building, and only then install equipment.

Aerial view of a large logistics center with parking lots
General view. A large-footprint building, docks on two sides, and parking areas separated from truck circulation.
MAIN BUILDING 60,000 m² + mezzanine Inbound docks (48) Outbound docks (64) Truck maneuvering yard Truck yard — inbound Substation+ generator Fire watertank Pumproom Employeeparkinglot Access and control Schematic plan, not to scale
Typical site layout: inbound and outbound on opposite sides for a U-shaped or linear flow, separate yards, and utilities grouped away from truck traffic.

Construction sequence and dependencies

Soilstudies Earthworks Groundimprovement Foundationsand pedestals Steelstructure Roof andenclosure Final slab+ joints Equipmentinstallation Weathertight (dry-in) building: key milestone Floor ready for handover Major risk: soil bearing capacity and settlement Option to save time: pour the slab in strips after closing each zone, with equipment entering by sector. On sites with a high water table or soft soils, ground improvement (gravel columns or preloading) can add 2–4 months.
General sequence. The slab is usually poured after the roof of each zone is closed, to control moisture, curing, and temperature.

Detail by stage: what to plan, what to control

4.1Studies, surveying, and preliminary permitsM1 – M5

What is done

  • Topographic survey and bathymetry of nearby watercourses or canals.
  • Geotechnical study: boreholes every 40–50 m (at least 1 per 2,500 m²), SPT, CPT, laboratory tests, groundwater level.
  • Traffic impact and stormwater runoff study; environmental assessment as applicable.
  • Building permit, preliminary design review with the municipal building authority (DOM in Chile), water and power availability.

What you control

  • Signed geotechnical report: bearing capacity, subgrade reaction modulus k, expected settlement.
  • Fixed and protected survey coordinates and benchmarks (BM).
  • Permit calendar with an owner and a deadline for each; every overdue permit appears in the weekly report.

Risk: designing from an insufficient study. An extra borehole costs thousands; reinforcing foundations costs hundreds of thousands.

4.2Site setup and earthworksM4 – M7 · ~480,000 m³

What is done

  • Perimeter fencing, access roads, offices, storage areas, wastewater treatment plants, dust control.
  • Clearing and topsoil stripping, cut and fill to design grade.
  • Structural fill in compacted lifts of 25–30 cm.
  • Temporary drainage and a stormwater management plan.

Typical equipment: 6–8 motor graders and bulldozers, 20 dump trucks, 4 vibratory rollers, 5 excavators, water trucks.

What you control

  • Compaction ≥ 95% of modified Proctor (nuclear density gauge every 500 m² per lift).
  • Elevations and slopes checked by daily surveying; tolerance ±2 cm on subgrade elevation.
  • Earthworks balance: measured volume vs. budgeted volume, every week.
  • Certificate of surplus material disposal.

Risk: rain. Prepare a plan B (sump pumps, a calendar with weather allowances) and identify the historical non-working days.

4.3Ground improvement and foundationsM6 – M9

What is done

  • Improvement: gravel columns, dynamic compaction, or preloading, depending on the soil study.
  • Excavation for isolated footings under columns and for grade beams at the docks.
  • Blinding concrete, rebar placement, formwork, concrete pouring (typically H30), anchor bolts set with templates.
  • Retaining walls for the docks and dock leveler pits.

What you control

  • Load tests on gravel columns (at least 1% of the units) and settlement measurements.
  • Anchor bolts: ±3 mm in plan, ±5 mm in elevation. This is the most expensive error to fix once the structure arrives.
  • Concrete: slump, temperature, cylinders at 7 and 28 days (one set per 50 m³ or per critical truck).
  • Reinforcing steel: heat certificates and tensile tests per lot.
4.4Industrial slab on grade (floor)M9 – M13 · ~13,500 m³
Concrete slab with fibers or mesh — t = 20 cm · FF ≥ 50 / FL ≥ 35 (narrow-aisle zones) PE sheet 0.2 mm · slip layer Stabilized granular base — t = 30 cm · CBR ≥ 80% Compacted subbase ≥ 95% M.P. — t = 30–40 cm Improved subgrade · modulus k ≥ 60 MPa/m contraction jointconstruction joint with dowels
Schematic section. Thicknesses and strengths depend on the design calculation (rack loads of 4–6 t per upright and heavy equipment).

What is done

  • Strips 6–8 m wide and 40–60 m long placed with a laser screed or vibratory screeds.
  • Curing with compounds or sheeting for at least 7 days; surface hardener.
  • Saw-cut joints within 6–18 h to prevent shrinkage cracking.
  • Marking of gridlines and layout of racks and conveyors on the finished floor.

What you control

  • Flatness and levelness: FF/FL per ASTM E1155, or 3 m straightedge readings per DIN 15185 in aisles for wire-guided trucks.
  • Strength: cylinders at 7/28 days; cores if in doubt. Flexural strength when fibers are used.
  • Flatness measured at 24–72 h, before full shrinkage; defects are corrected by grinding or surface rectification.
  • Record for each strip: date, weather, start time, quantity, trucks, tests, responsible person.
Point of maximum care

An out-of-tolerance slab forces you to regrind 60,000 m² with machinery or to recalibrate the entire racking and conveyor structure. Define formal hold points: nobody pours a strip without approval of the formwork, laser leveling, and the joint plan.

4.5Steel structureM8 – M13 · ~7,500 t

What is done

  • Shop fabrication (frames, beams, purlins, bracing) with material traceability.
  • Painting or galvanizing; transport in special convoys.
  • Erection with 100–400 t cranes, by gridline and by sector, with temporary bracing.
  • Independent mezzanine structure, designed for the actual weights of equipment and people.

What you control

  • Steel certificates (A36 / A572 or equivalent), shop inspection, and dimensional control.
  • Welds: 100% visual inspection, ultrasonic or magnetic particle testing according to the plan's percentage.
  • High-strength bolts with calibrated torque and a record for each connection.
  • Plumb and alignment: L/500 tolerance on columns; layout verification with a total station when closing each gridline.

Seismic design: verify compliance with NCh 2369 (the Chilean seismic design standard for industrial structures and facilities) and compatibility with racks and mezzanine.

4.6Roof, enclosure, and docksM11 – M16

What is done

  • Insulated sandwich-panel or metal roofing; translucent panels for daylighting savings.
  • Perimeter walls (precast concrete panel or metal panel) and dock doors.
  • Hydraulic dock levelers, dock seals, bumpers, guides, dock traffic lights.
  • Ventilation, smoke evacuation, and pedestrian entrances.

What you control

  • Watertightness test (hose or spray test) on 100% of critical joints.
  • Dock alignment and floor height of 1.2–1.3 m above the yard, with ±5 mm tolerance.
  • Inspection of seals and airtightness: air leaks and infiltration are a source of operational claims.
  • Fire-resistance certificate for dividing walls.
4.7Exterior paving and road worksM12 – M18

What is done

  • Maneuvering yard with rigid pavement (22–26 cm concrete) in braking and turning areas.
  • Flexible pavement roadways, parking, access roads, signage.
  • Stormwater system: collectors, grit chambers, grease separators, retention ponds.

What you control

  • Thicknesses by cores, base compaction, and drainage slopes (min. 1–2%).
  • Turning radii checked with a truck template (tractor + semitrailer).
  • Drainage performance test with simulated rain before acceptance.
4.8Finishes, offices, technical rooms, and staff facilitiesM14 – M20
  • Offices, dining hall, locker rooms, training rooms, control room (CCR), server room, and battery rooms.
  • Noise control, ergonomics, and universal accessibility.
  • Control room with a view of the operation and environmental conditions suited to screens, racks, and operators.

Control: switchboard thermography, lighting measurements (lux at workstation), noise (dB), ventilation (air changes per hour), and photographic evidence for each room before handover to operations.

Critical materials: lead times and control

Material / itemTypical lead timeApprox. quantityWhat is required on receipt
Structural steel (sections and plates)16 – 24 weeks7,500 tHeat certificate, dimensional inspection
Ready-mix concreteFramework supply contract~25,000 m³ totalDelivery ticket per truck, departure time, tests
A630-420H reinforcing steel6 – 10 weeks~1,800 tCertificate per lot, tensile test
Roof and wall panels14 – 20 weeks65,000 m²Fire and insulation certificates; protection in transit
Dock levelers and dock doors20 – 28 weeks112 unitsDrawings, factory FAT, load capacity
MV/LV transformers40 – 60 weeks4 – 6 unitsFactory test protocol
Distribution boards and MCCs26 – 40 weeks60 – 90 unitsFAT, internal arc certification
Fire pumps, piping, and sprinklers16 – 28 weeks1 systemLaboratory certification, pump curves
Buy early

Transformers, switchboards, and automation equipment have the longest lead times. If you buy after the structure is finished, you have already lost the project: they must be ordered in the first 5–7 months.

5. Electrical, fire protection, and HVAC systems

An automated center draws between 8 and 15 MVA of installed capacity and cannot tolerate outages: power is part of the system.

Power

  • MV substation with dual feed if possible.
  • Transformers, main switchboards, and motor control centers.
  • Backup generators for critical loads (IT, security, minimum sorter operation).
  • Online UPS for PLCs, network, and servers; battery bank for 15–30 min.
  • Tests: protections, grounding grid (< 5 Ω), thermography, SEC certification (Chile's electrical and fuels regulator).

Fire

  • ESFR sprinklers (early suppression, fast response) in the warehouse and high-piled racks.
  • Reserve tank and main, jockey, and diesel pumps.
  • Aspirating early detection in battery and IT rooms.
  • In-rack protection when the height requires it.
  • Approval by the insurer and the fire department; hydrostatic test at 1.5 times working pressure.

Climate and environment

  • Natural and forced ventilation in the warehouse; smoke extractors.
  • Air conditioning in offices, technical rooms, and staffed packing areas.
  • LED lighting with sensors, 200–300 lux at floor level (500 at workstations).
  • Wastewater and sanitary systems, potable water, treatment where applicable.
  • Rainwater harvesting and rooftop solar panels (optional).
Interaction with automation

Sorters and conveyors generate startup peaks and harmonic loads. Request a power quality study and coordinate protections before energizing. An oversight here causes cascading trips during the SAT.

6. Machinery, equipment, and automation

The system is designed working backward from the order: how many shipments per hour, what package size, what delivery time. From that come the capacities, quantities, and areas. These are the equipment families you need to know, with what to require in the FAT and SAT.

Control and software architecture

ERP / OMS · orders, accounting inventory, invoicing WMS · inventory by location, work waves, receiving, shipping WES / WCS · equipment orchestration, routing, load balancing PLCs and zone controllers · motor logic, sensors, safety Field · motors, photoeyes, scanners, scales, robots, pushbuttons BusinessLogisticsExecutionControlPhysical Hours–daysMinutesSecondsMillisecondsReal time SCADA and control dashboards monitor the entire stack; the industrial network and cybersecurity protect it.
Every arrow between layers is an interface. Each interface must have a document (ICD), a test in the FAT, and another in the SAT.
Electrical control panel with PLC and touchscreen
Control panel. PLCs, drives, and HMI: check them in the FAT against the bill of materials and electrical drawings.
Operator in a control room with multiple SCADA screens
Control room. Display of faults, jams, and flows. Define alarms and priority levels before commissioning.
Industrial gear motor on a conveyor
Gear motor. Maintenance and critical spare parts are defined during engineering, not after startup.

7. Interfaces between civil works, building systems, and equipment

Most delays are born at an interface with no owner. Make them explicit, with a date and a responsible party.

InterfaceDeliversReceivesHandover conditionTarget date
Anchor bolts and basesCivilStructure / rackingAs-built survey within toleranceM9
Slab by zoneCivilRacking, conveyorsFF/FL approved, curing complete, cleaned, gridlines markedM11 – M13
Weathertight buildingCivilElectronic equipmentNo leaks, humidity < 70%, temperature controlledM14
Permanent powerElectricalIntegratorSwitchboards energized, grounding measured, protection tests doneM15
Data network and Wi-FiITIntegrator, WMSConduits, fiber, certified coverageM15
Sprinklers above racksFire protectionRackingPiping coordinated with rack and mezzanine heightsM15 – M17
Structural mezzanineRackingConveyorsLoads approved, leveling, guardrails, certificationM16
Fire curtains at conveyor crossingsFire protectionIntegratorSignals to PLC testedM17
Zone ready for SATAllTestingNo pending work in the area, punch lists closedM19
Useful practice: 3D coordination

Require a federated BIM model with clash detection between structure, cable trays, sprinklers, ducts, and conveyors. One hour of 3D review saves weeks of rework during installation.

8. Scheduling: how the plan should be built

A useful schedule is not a drawing: it is a logic model that answers “what happens to the finish date if this slips.” It is built from the WBS, loaded with resources and updated every week.

Scheduling levels

LevelNameHorizonDetailUsed byUpdated
L1Milestones and master scheduleWhole project20–40 contractual milestonesBoard, financeMonthly
L2Control schedule (CPM)Whole project500–1,500 activities with logic, resources and costsProject manager, project controlsWeekly
L3Coordination schedule by contract3–6 months5–15 day activities with interfacesEngineer in charge, contractorsWeekly
L43-week lookahead3 rolling weeksTasks with crew, equipment, permits and materialsSite manager, foremenWeekly
L5Daily plan24–48 hoursWho, where, with what, what gets doneEveryone on siteDaily

Illustrative master schedule (24 months)

Simplified Gantt chart

Orange bars with thick outline = critical path. Hover over a bar for details. Vertical line = data date of the example (month 14).

Critical path and float

In this project, the typical critical path is: soil study → ground improvement → foundations → structure → roof (dry-in building) → final slab → equipment installation → FAT/SAT → integrated testing → commissioning. A second, near-critical path runs in parallel: automation equipment purchase → manufacturing → FAT → shipping. If either one slips, the other becomes critical.

What the schedule must have

  • Relationship logic (FS, SS with lags) without forced date constraints.
  • Calendars by contract (shifts, holidays, rain).
  • Resources: crews, cranes, key equipment.
  • Quantities and productivity rates that justify each duration.
  • Frozen baselines and comparable versions.

Schedule quality checks

  • Activities without a predecessor or successor: < 2%.
  • Negative float: investigate and correct immediately.
  • Durations longer than 44 working days: split them.
  • Hard constraints: justify each one.
  • Baseline Execution Index (BEI) ≥ 0.95.

How to recover time

  • Crash: more crews or shifts on the critical path; the contractor pays if it is their fault.
  • Fast-track: start the slab by zones, hand over sectors to the integrator.
  • Resequence: change the rack installation sequence to free up work fronts.
  • Cut scope: later automation phases.

Procurement schedule for critical equipment

EquipmentSpecification readyPurchase orderManufacturingFATArrival on siteInstallation
MV/LV transformersM3M5M6 – M11M11M12M12 – M13
Racking and mezzanineM3M5M6 – M12M12M13 – M16M14 – M18
Conveyors and sortersM4M7M8 – M15M14 – M16M15 – M19M15 – M20
Dimensioners, scales, scannersM5M8M9 – M14M14M16M17 – M19
Mobile robots (AMR) and shuttlesM6M9M10 – M16M16M18M18 – M20
WMS / WESM3M6Design M6 – M10, development M10 – M16Software FAT M17—Installation M18
Forklifts and handling equipmentM9M12M13 – M17Receiving inspectionM19—

Example dates; adjust them with the suppliers’ actual Gantt charts. Ask each supplier for an engineering, procurement and manufacturing schedule with verifiable milestones.

9. Schedule and cost control

Controlling means comparing what happened with what was planned, understanding why, and acting in time. For that, use earned value management, which combines physical progress and money in a single language.

Definitions

PV = planned value (what should have been done) EV = earned value (actual % progress × budget) AC = actual cost incurred SPI = EV / PV (< 1: behind schedule) CPI = EV / AC (< 1: over budget) EAC = BAC / CPI (forecast at completion) VAC = BAC − EAC (expected final variance) TCPI = (BAC − EV) / (BAC − AC)

BAC = total budget at completion. Measure progress with fixed rules by activity type: physical units (m³, t), weighted milestones (0–25–75–100%) or share of hours.

Management traffic lights

IndicatorGreenAmberRed
SPI / CPI≥ 0.970.90 – 0.96< 0.90
Critical path float≥ 0 days−1 to −14< −14
Approved changes / BAC< 3%3 – 6%> 6%
Contingency used vs. progress≤ progress+10 pts> +10 pts
On-time payments≥ 95%85–94%< 85%

S-curve: cumulative progress, planned, actual and forecast

Illustrative example with data date at month 14. Dotted line = forecast at current performance (SPI 0.93).

SPI and CPI trend

Reference line at 1.0. Below it = unfavorable.

Site manpower

Average workers per month and by work front.

Budget, committed and paid by package

In USD millions, data date month 14 (illustrative). A package with a lot committed and little paid indicates pending work; the opposite, advances without progress.

Cost control in practice

  1. Baseline budget and contingency. Define the BAC by WBS code; separate contingency (known risks) from management reserve (unknowns).
  2. Commitments. Record every contract and purchase order; cash flow is forecast from the payment milestone dates.
  3. Payment applications. Check quantities measured on site, not just what the contractor reports; verify retentions and deductions.
  4. Monthly forecast. Calculate the EAC from the remaining work, not just from historical CPI; include pending changes and claims.
  5. Review with finance. Reconcile budget, accounting and payments; close the month with a report of explained variances.

10. Daily work and weekly rhythm

The project is won or lost in the work of each day. Routine discipline is what lets you see problems before they become delays.

A typical day for the engineer in charge

06:30
Arrival. Review of weather, safety report, attendance and overnight news.
07:00
Safety talk and daily planning with foremen and subcontractors. Review of critical work permits (height, hot work, confined spaces, lifts).
08:00
Site walk: physical progress, safety, housekeeping, quality. Photographs with date and location.
10:00
Hold points of the day: formwork acceptance, tests, inspections, concrete pour approval.
12:00
Interface meeting with the integrator or the MEP contractor, as needed.
14:00
Office: RFIs, drawings, letters, change orders, payment applications, pending emails.
16:00
Close-out with the site manager: executed vs. planned, causes of variance, plan for tomorrow.
17:30
Daily report and update of the punch list. Leave only after checking the safety of the close-out.

Meeting rhythm

CadenceMeetingAttendeesOutput
Daily, 15 minCoordination meeting (stand-up)Foremen, HSE, engineerPlan for the day, constraints
WeeklyLookahead and progress by contractContractors, scheduler3-week plan, % compliance
WeeklySafety and qualityHSE, QA/QCFindings, NCRs, actions
WeeklyCivil–equipment interfacesIntegrator, civil, MEP, ITHandover dates, conflicts
BiweeklyChanges and claimsCost, managerApprovals, impact
MonthlyProject committeeManagement, finance, operationsMonthly report, decisions
MonthlyRisk reviewManagement teamUpdated register

Daily site report: minimum content

General data

  • Date, weather, productive hours.
  • Headcount by contractor and trade.
  • Equipment present and in use.
  • Visits and inspections.

Progress

  • Activities executed with quantities (m³, t, lm).
  • Work fronts opened and closed.
  • Comparison with the plan for the day.
  • Classified photographs.

Alerts

  • Incidents, near misses and unsafe conditions.
  • Tests carried out and results.
  • Constraints, delayed materials, instructions received.
  • Pending decisions and deadlines.

3-week plan (lookahead): rules

  • A task enters the plan only if its 6 conditions are cleared: design, materials, labor, equipment, permits and work front released.
  • Every Friday the Percent Plan Complete (PPC) is measured: tasks completed ÷ tasks committed. Target ≥ 80%.
  • Every missed task carries a standardized cause: design, material, weather, labor, equipment, interference, safety, client. Root-cause analysis guides the actions.

11. Quality and safety

Quality and safety are not an appendix: they are in the contract, in the schedule and in every hold point.

Quality management

  • Project quality plan and inspection and test plan (ITP) for each contract; define hold and witness points.
  • Approved procedures before starting: concrete pouring, welding, erection, hydrostatic tests, energization.
  • Acceptance protocols per element with signatures from the contractor, the technical inspector (ITO) and, where applicable, the owner.
  • Non-conformances (NCR): detect → document → root cause → corrective action → verification → closure. No open NCR when accepting a sector.
  • Independent laboratory for concrete, soils and welds.
  • Monthly quality audits of contractors with a checklist.

Safety management

  • Critical risks: work at height, crane lifts, excavations, electrical energy, vehicle traffic, confined spaces, hot work.
  • Work permits and lockout-tagout (LOTO) mandatory before working on equipment.
  • Mandatory induction, access control and competency records.
  • Daily inspections of lifting equipment, scaffolding and harnesses.
  • Emergency and evacuation plan and quarterly drills.
  • Indicators: lost-time injury frequency rate (LTIFR), total recordable injury frequency rate (TRIFR), days without accidents, near misses reported, on-time closure of actions.
  • Compliance with current local occupational health and safety regulations.
Project rule

Anyone can stop work for a serious risk, without reprisal. A one-day stoppage costs far less than a serious accident, which can also halt the site for weeks.

Key tests and tolerances

ElementTest or controlFrequencyCriterion
Compacted fillIn-place density (sand cone / nuclear)1 per 500 m² per layer≥ 95% modified Proctor
Fresh concreteSlump (Abrams cone), temperature, air contentEvery critical truck / 50 m³Per specification
Hardened concreteCylinders at 7 and 28 days1 set per 50 m³fc ≥ specified strength
Industrial floorFF/FL, flatness with 3 m straightedge100% of critical zonesFF ≥ 50 · FL ≥ 35 (example)
WeldsVisual + UT / PT / MT100% visual, 10–20% NDTAWS D1.1 code or equivalent
High-strength boltsTorque control10% of each connectionSpecified torque and nut rotation
SprinklersHydrostatic testEach network1.5 × working pressure for 2 h
CablingInsulation resistance, continuity100%Code / protocol values
Grounding gridResistance measurementBefore energizing≤ 5 Ω (example; per design)

12. FAT and SAT: acceptance testing

Tests are the proof that the contract was fulfilled. They are done in four steps: at the factory (FAT), on site without load (pre-commissioning and SAT), integrated with software (IST) and with real operation (pilot and reliability tests).

FATAt the supplier’s factory Pre-commissioningMechanical and electrical, no load SATOn site, with products Integrated ISTEquipment + WMS + ERP Pilot and reliabilityReal operation, 72 h – 14 days Each step has entry criteria (what must be met before starting) and exit criteria (what counts as approved).

FAT — Factory Acceptance Test

Carried out at the supplier’s factory, with the equipment assembled and energized, before shipping. It lets you fix problems where it is cheap.

What to verify

  • Dimensions, materials, paint, nameplates, labeling, weld and wiring quality against approved drawings.
  • Operation of motors, drives, sensors, protections and emergency stops.
  • PLC logic test with signal simulation; communication tests with the WCS.
  • Performance: speed, capacity (for example 12,000 items/h on a sorter), read accuracy, noise level.
  • Safety tests: light curtains, interlocks, stop redundancy.
  • Documentation: manuals, spare parts lists, material certificates.

How to organize it

  • Protocol approved 4 weeks beforehand; attendance by the owner’s engineer, operations and maintenance.
  • Numerical acceptance criteria; punch items classified A (blocks shipment), B (before SAT), C (minor).
  • Shipment authorized only with a signed report and a punch list with closure deadlines.

SAT — Site Acceptance Test

Carried out on site, with the equipment installed, permanent power, network, controls and real products.

What to verify

  • Mechanical completion: torques, alignment, lubrication, safety, cleanliness.
  • Electrical tests: insulation, grounding, direction of rotation, protections, trip times.
  • Functional tests by zone: start, stop, ramps, manual, automatic and emergency modes.
  • Load tests: boxes of minimum and maximum weights and sizes; bags, deformed boxes; parcels with labels of varying quality.
  • Performance tests: rated capacity sustained for 4 h, jam rate, barcode read rate ≥ 99.5%, sorting accuracy ≥ 99.9%.
  • Failure scenarios: power outage, network loss, reader failure, jam and restart.

Typical acceptance criteria

ParameterTarget
System availability (72 h – 14 days)≥ 98.0%
Design capacity sustained for 4 h≥ 100%
Sorting accuracy≥ 99.9%
Barcode read rate≥ 99.5%
Jams per 10,000 items≤ 3
Recovery time after an outage≤ 15 min

FAT and SAT progress by system (example)

Approved protocols vs. total

Each bar shows the % of protocols approved; the red flag marks open critical punch items (category A).

How a test is run, step by step

  1. Prepare. Approved protocol, entry criteria met, calibrated instruments, competent personnel, safe lockouts.
  2. Execute. Follow the script line by line. Record the actual result, not a generic “OK”; photograph screens and measurements.
  3. Log deviations. Each failure generates an item on the punch list with category A/B/C, owner and date.
  4. Correct and repeat. Retest only what was affected, plus a regression check of whatever might have changed.
  5. Sign the report. Contractor, ITO and the owner’s engineer; operations signs when it is a functional acceptance.
  6. Release. With the signed report, the milestone payment is released, the work moves to the next step and the dossier is updated.

SAT readiness checklist

Tick the items to see progress. It is saved in this browser.

0 of 0

    Punch list: categories and deadlines

    CategoryDefinitionExampleClosure deadline
    APrevents operation, is a safety risk or blocks the next milestoneEmergency stop failure on the sorterBefore continuing
    BAffects performance or quality but allows operation with a restrictionReader with 97% read rate instead of 99.5%Before final acceptance
    CCosmetic or minorScratched paint, missing labelWithin 30 days

    13. Commissioning and Operational Start-up

    Start-up turns a tested installation into a real operation. It is a change of ownership: from construction to operations. It needs its own plan, with clear criteria for saying “yes, we go live.”

    1. Preparation (M18 – M20). Staff hired, simulator training, procedures, master data loaded into the WMS (items, locations, dimensions).
    2. System tests (M19 – M21). Zone-by-zone SAT, interface tests and power-outage tests. Safety certified.
    3. Dry run (M21 – M22). Simulated orders with real inventory, staff working in shifts; performance is measured and flows are fine-tuned.
    4. Pilot with real customers (M22 – M23). 10–20% of volume, reduced shifts, integrator support team on site.
    5. Gradual start-up (ramp-up). Weekly increases in volume and shifts until design capacity is reached in 12–16 weeks.
    6. Enhanced support (hypercare). Integrator and project team working alongside operations for 8–12 weeks.
    7. Final acceptance and handover. Reliability test, punch list closure, delivery of documentation, release of retentions.
    Handheld terminal, scale and label printer on a workbench
    Workstation. Scale, printer and terminal are validated with real data before start-up.
    Operator preparing orders with a mobile terminal between shelves
    Operations. People are part of the system: without training, the best equipment performs at half its potential.

    Ramp-up curve: capacity achieved vs. target

    Percentage of design capacity reached per week after the start of operation (example).

    Criteria for the “go / no-go” decision

    AreaCriterionEvidence
    SafetyNo open category A punch items; safety training at 100%; evacuation drill completedHSE report, training records
    LegalFinal works acceptance, electrical and fire certifications, health authorizationsCertificates and resolutions
    TechnicalSAT approved, availability ≥ 98% in 72 h test, interfaces testedReports and test records
    OperationalStaff trained, procedures approved, master data loaded and validatedCompetency matrix, data quality report
    CommercialCustomers and carriers informed; manual contingency planTransition plan
    SupportMaintenance contract, critical spare parts, 24/7 integrator help desk during hypercareContracts and spare parts stock
    Plan B

    Have a manual procedure and a rollback criterion: when to divert the flow to a temporary operation if the system fails. This keeps a technical problem from turning into a customer crisis.

    14. Documentation to Produce

    Documentation is a deliverable. Without it there is no acceptance, insurance, warranty or workable operation. Define from the start the coding system, who issues, who reviews and what status each document is in.

    Suggested coding system

    PRJ-AREA-DISCIPLINE-TYPE-NNNN-REV · example: CDL-BLD-STR-DRW-0123-B (center, building, structure, drawing, number 123, revision B). Statuses: A = issued for comments, B = for construction, C = as-built.

    DocumentPhaseProduced byApproved byKey content

    Final handover dossier

    Technical

    • As-built drawings for all disciplines.
    • Final design calculations.
    • Operation and maintenance manuals.
    • Lists of critical spare parts and consumables.

    Quality and testing

    • Signed test protocols.
    • Material and equipment certificates.
    • FAT, SAT, IST and reliability reports.
    • Closure of NCRs and punch items.

    Legal and administrative

    • Final municipal acceptance and permits.
    • Electrical and fire certifications.
    • Warranties, policies, bonds, final settlements.
    • Software licenses and escrow.

    15. Reports

    A report does not exist to be filed away: it exists so someone can decide. Each report has a reader, a question and an action it must produce.

    ReportFrequencyReaderQuestion it answersContent
    Daily site logDailyEngineer in chargeWhat happened today?Headcount, progress, tests, incidents, constraints
    Weekly reportWeeklyProject managerDid we meet the week and what comes next?PPC, progress by contract, lookahead, safety, quality, constraints
    Monthly executive reportMonthlyBoard, financeWill we meet schedule and cost?Summary, S-curve, EV, EAC, milestones, risks, changes, cash, decisions requested
    Safety reportMonthlyManagement and HSEAre we working safely?LTIFR, TRIFR, near misses, inspections, actions
    Quality reportMonthlyEngineer in charge, QADoes what was built comply?NCRs, tests, audits, trends
    FAT/SAT test reportPer testEngineer, operationsDo we accept or not?Protocol, results, deviations, recommendation
    Changes and claims reportBiweeklyCost control, committeeWhat changed and how much does it cost?Approved and pending changes, impact
    Start-up reportDaily during ramp-upOperations, managementHow is the system performing?Volume, throughput, failures, availability, actions

    Structure of a monthly executive report

    1. One-page summary: overall status (green/amber/red), 3 achievements, 3 problems, 3 decisions required.
    2. Progress: S-curve, SPI, comparison with baseline, milestones for the next 60 days.
    3. Cost: budget, committed, paid, EAC, contingency, changes.
    4. Contracts and procurement: package status, critical deliveries, supplier risks.
    5. Quality, safety and environment: main indicators and findings.
    6. Testing and commissioning: FAT/SAT progress, punch items, operations readiness.
    7. Risks and opportunities: top 10 with probability, impact, owner and action.
    8. Appendices: photographs, updated schedule, change log, minutes.

    16. Key Performance Indicators (KPIs)

    Few indicators, well defined and measured the same way every time. Each KPI needs a formula, source, frequency, target and owner.

    KPIFormulaTargetFrequencyIf it goes wrong
    Protect data quality

    A KPI is only useful if everyone calculates it the same way. Define who measures it, from what source and who reviews it. If physical progress is reported by the same contractor who bills for it, you need independent validation.

    17. Risk Management

    A risk is something that has not happened yet. If it already happened, it is an issue. The risk register is reviewed every month and each major risk has an owner and a dated action.

    Risk matrix (probability × impact)

    Hover over a dot. The codes match the table.
    IDRiskMain mitigation

    Avoid

    Change the plan so the risk does not occur: improve the soil study, choose a proven supplier.

    Reduce and transfer

    Early testing, redundancy, insurance, penalties, performance bonds.

    Accept with reserve

    Allocate time and cost contingency, with defined triggers to activate it.

    18. Common Problems and How to Solve Them

    These problems appear in almost every project. Each one has an early warning sign: if you spot it, you gain weeks.

    19. Your First 90 Days as Engineer in Charge

    Whether you join a project already underway or start one from scratch, this is a reasonable order of work.

    Days 1–30 Understand

    • Read contracts, technical specifications, scope, drawings and the master schedule.
    • Walk the entire site with each contractor.
    • Build the interface matrix and the risk map.
    • Validate the schedule and budget baseline.
    • Define the meeting rhythm, report formats and document system.
    • Meet key suppliers and visit factories.

    Days 31–60 Control

    • Implement the weekly lookahead and PPC measurement.
    • Set up ITPs, hold points and the NCR log.
    • First monthly report with EV and forecast.
    • Review FAT/SAT protocols with operations and the supplier.
    • Close pending changes and set contingency.
    • Audit quality and safety of each contractor.

    Days 61–90 Anticipate

    • Recovery plan for delayed critical activities.
    • Testing, training and start-up plan with dates and owners.
    • Verify long-lead purchases and import logistics.
    • Simulate scenarios: a 4-week delay in the structure, supplier failure.
    • Present to the committee the risks and decisions needed for the next 6 months.

    Habits that set a good project engineer apart

    Walk the site.

    Problems show up in the field before they show up in a report.

    Document everything.

    If it is not in writing, it did not happen.

    Measure with data.

    Verified quantities, not optimistic estimates.

    Communicate early.

    Bad news ages worse than wine.

    20. Glossary