Pilot scope
Defines paid pilot boundaries and deliverables
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
Package GCCAP into a paid pilot that can be sold, deployed, monitored, reported and reviewed without claiming full global production too early.
P9 converts the release-candidate and productionisation controls into a practical controlled paid pilot package: scope, client/site readiness, hardware deployment, supplier feed acceptance, portal access, reports, alerts, training, support, success criteria and executive pack.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Pilot laneOne client, one site, selected carts
DeliverablesPortal, alerts, reports, executive pack
StatusBlocked until go/no-go gates pass
Operational layer
P9 launch controls
This layer is designed to get GCCAP to revenue without overclaiming global production readiness.
Client/site readiness
Maps facility, process, approvals and owners
Hardware deployment
Controls gateways, sensors, SIMs, labels and certificates
Feed acceptance
Blocks launch until CtrlOps/Teltonika data is verified
Report delivery
Defines daily, breach and executive report outputs
Go/no-go gate
Prevents premature pilot launch
Decision clarity
Launch blockers
These items must pass before a client paid pilot starts.
Supplier feedSample payload and field dictionary pending
HardwareReal device inventory and installation plan pending
MonitoringAlert route/provider or manual fallback required
ReportsClient-facing approval workflow required
SecurityTenant/access checks required