Client intake
Captures sponsor, owner, site, cart volume, data terms and success outcome.
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 accessInternal GCCAP surface
Turn pilots into repeatable client deployments.
GCCAP now has an onboarding factory that connects client intake, site/facility setup, hardware assignment, portal users, pilot acceptance, training, go-live and expansion review. This is the layer that turns the technical platform into a repeatable implementation machine.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Build22
Focusclient onboarding
Outcomerepeatable pilots
Boundarynot production go-live yet
Operational layer
What Build 22 controls
The onboarding factory makes client setup repeatable instead of improvised.
Site setup
Maps facility zones, airport context, gateway placement and geofence assumptions.
Device assignment
Connects client, site, cart, sensor, gateway and installation evidence.
Go-live control
Blocks rollout until acceptance, training, portal, alerts, reports and support are ready.
Decision clarity
Onboarding sequence
The sequence turns a serious website enquiry into a controlled evidence pilot.
1Commercial and technical client intake
2Site/facility mapping and operational lane definition
3Device/sensor/cart assignment and installation evidence
4Portal users, training and support handover
5Pilot acceptance, go-live approval and expansion review