GCCAPCold chain. Clear evidence. Confidence.

Internal GCCAP operating surface

This page is retained behind the public client website.

GCCAP does not delete operating records, trial packs, hardware activation surfaces or evidence automation layers. They are preserved for authorised client portal, command-centre and internal operating use while the public website stays clean for airline first impressions.

Open portal access

Internal GCCAP surface

Turn website interest into a controlled trial without risking hardware capital too early.

Build 67 locks the business sequence: Netlify first, client interest second, pilot scope third, hardware purchase trigger fourth, then VPS/MQTT runtime and first real evidence report.

Return to public website Review pilot page

StatusInternal / restricted operating pack. Public clients should see the website and pilot walkthrough, not this internal execution control layer.

GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Website layerNetlify
Runtime layerVPS/backend
Hardware spendAfter trial interest
Main blockersClient + hardware

Decision clarity

Deployment layers

GCCAP must be understood as three coordinated layers, not one static website upload.

Layer 1 - Netlify public websiteMarketing and trust layer. Shows GCCAP, captures walkthroughs and explains the pilot path. This is the build that should go public first.
Layer 2 - Pilot runtimeVPS/backend layer with MQTT broker, Teltonika parser, raw payload storage, normalised events, device registers and first evidence report workflow.
Layer 3 - Production platformHardened multi-client platform with auth, tenant isolation, database, backups, monitoring, client portal, internal command centre and governed Watchdog gates.

Decision clarity

Hardware purchase strategy

The capital-safe model is to avoid ordering the full kit before client interest is proven. A client-approved pilot should trigger purchase or reimbursement.

Do not over-spend before demandThe public site can go live and generate trial interest without hardware being purchased first.
Preferred triggerPurchase hardware after client walkthrough and pilot approval, deposit, purchase order, reimbursement agreement or written client commitment.
Minimum kitStart with the smallest practical kit needed to prove EYE sensor -> FMC150 -> GCCAP -> evidence report.
Client expectationA pilot proposal should clearly state whether hardware is client-paid, reimbursed, loaned, or included in a paid pilot fee.
Risk protectionAvoid promising permanent deployment until the washer/mounting strategy is proven.

Decision clarity

Stage gates from website to live client

This is the clean forward path from Build 67 onward.

Gate 1 - Netlify launchUpload public website after final local review. Objective: interest, credibility and walkthrough requests.
Gate 2 - Client walkthroughUse website plus pilot explanation to secure a defined trial discussion.
Gate 3 - Pilot proposalSend costed scope document: client roles, hardware purchase trigger, timeline, privacy and outputs.
Gate 4 - Hardware orderOrder sensors/gateways after commercial confidence is created.
Gate 5 - Runtime setupProvision VPS, Mosquitto, backend receiver, parser, registers and first-payload test harness.
Gate 6 - First real readingReceive FMC150 Codec 8 payload and confirm sensor/gateway mappings.
Gate 7 - First evidence reportGenerate private report from real trial data.
Gate 8 - Scale decisionDecide whether to expand, refine hardware/mounting, or stop.

Governance

What clients should understand about cost

The website should create interest, not publish a rigid price list. Costing belongs in a separate pilot proposal or scope document after a walkthrough.

  1. Client may pay or reimburse pilot hardware once the trial is approved.
  2. Client may pay a fixed pilot fee covering setup, configuration, support and first evidence report.
  3. Client provides site access and operational cooperation at no charge unless otherwise negotiated.
  4. GCCAP should not absorb large hardware costs until client demand or funding exists.
  5. A later subscription can cover monitoring, reporting, portal access, trend packs and support.