ETABLIX · INTEGRATED SITE SERVICES · PART OF GROUPE NSEYA

See the deliverable before you buy it.

The Site Systems Diagnostic is a fixed-fee engagement with a defined output: a written report your board can act on. Below is a redacted, illustrative extract of that report — the format, the depth and the kind of findings it contains. Nobody should buy a document sight-unseen; here is what yours will look like.

The extract below is illustrative. It reflects the structure and analytical depth of a real deliverable using a hypothetical project; client-identifying detail in delivered reports is confidential to the client. Your report is yours to keep, whatever you decide afterwards.

SITE SYSTEMS DIAGNOSTIC — EXECUTIVE SUMMARY
Project: ████████ 400kV Substation · Peak workforce ~300 · Programme 26 months
ETABLIX — Commercial in confidence
Ref: SSD-████ · Rev B
Issued: ██ ███ 20██

Findings in one paragraph

The site-services scope is currently structured as 18 packages across 14 suppliers, producing 41 supplier-to-supplier interfaces of which 9 are unowned — no contract allocates responsibility for the hand-off. Three of the nine sit on the mobilisation critical path. The temporary power strategy is sized from the construction load only; the welfare and accommodation load added later exceeds the planned generator capacity in winter operation. The village opening date trails first workforce arrival by 11 working days under the current supplier programmes. Left as structured, the project carries a material risk of late mobilisation and contested prelims escalation that no individual supplier can be held accountable for.

The five decisions this report puts in front of you

  • 1. Re-package the 18 scopes into 11, eliminating 6 of the 9 unowned interfaces by moving each hand-off inside a single contract.
  • 2. Re-size temporary power for the combined construction + welfare + village winter load before generator orders are placed.
  • 3. Re-sequence village mobilisation to close the 11-day gap: early utilities energisation and phased block handover.
  • 4. Appoint one integration owner — internally, or contracted — with authority over the interface register and mobilisation gates.
  • 5. Adopt readiness gates so occupation, catering and transport start on evidence, not on supplier assurances.
SECTION 4 — INTERFACE REGISTER (EXTRACT)
41 interfaces identified · 9 unowned · extract shows 5
RefInterfaceBetweenOwner todayExposure
IF-07Generator sizing vs. welfare & village electrical loadTemporary power ↔ modular supplierUnownedWinter overload; unplanned hire costs; village heating failure
IF-12Cabin bases & drainage falls vs. module tolerancesEnabling civils ↔ modular supplierUnownedRework at install; occupation delay
IF-19Access-control integration with client turnstilesSecurity ↔ client systemsSplitDay-one workforce queuing; induction bottleneck
IF-23Village opening vs. first workforce arrival dateModular ↔ catering ↔ transportUnowned11-day gap; hotel costs; productivity loss
IF-31Waste licensing across three producing suppliersWaste ↔ civils ↔ FMOwnedCompliant as structured; consolidation saving available

Each of the 41 interfaces carries the same fields in the full register, plus the recommended owner, the contract clause that should carry it, and the gate at which it must be evidenced.

SECTION 6 — MOBILISATION READINESS GATES (EXTRACT)
6 gates defined · extract shows 3
GateOpens when — evidence, not assuranceGuards against
G2 · Power-readyCombined load calculation signed; generators on site, commissioned and load-tested against the winter profileIF-07 — village without heat or light
G4 · Village-readyBlock handover certificates; fire systems commissioned; catering hygiene sign-off; transport routes provenIF-23 — workforce arriving before beds exist
G5 · OccupationAccess control live-tested at forecast peak arrival rate; welfare capacities verified against week-1 headcountIF-19 — day-one queuing and induction collapse

Delivered as a one-page gate plan your project director can put on the wall — with owners, dates and the evidence list per gate.

What the full report contains

Requirements & demand review · full package and interface map · commercial and delivery-risk register · procurement and mobilisation roadmap · delivery-model recommendation · executive action list. Typically 25–40 pages, issued within ten working days of site access and information handover, presented to your leadership in person or by call. Every report closes with a document reconciliation ledger: which of your own documents disagree with which, both sources named, line by line.

Fixed fee, defined deliverable, yours to keep. If we never speak again, you still own the clearest picture of your site's operating requirement you've ever had.