Cutover checklist
Scope, supplier, hardware and portal launch gates.
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
Control supplier feed acceptance, launch gates, signoffs and live pilot go/no-go evidence.
The lab is the internal operating surface for P15. It keeps the controlled live pilot cutover blocked until supplier feed, payload, tenant, monitoring, notification, hardware and client approval gates are complete.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
APIs/api/live-pilot/*
PurposeLive pilot go/no-go
StatusBlocked until approved
Revenue pathControlled paid pilot
Operational layer
Lab controls
Use these APIs to maintain the pilot launch acceptance evidence.
Supplier data contract
Connection, data use and service-level acceptance.
Evidence gates
Tenant isolation, monitoring, backup and notification proof.
Final approvals
Commercial, technical, governance, operations and final launch approvals.
Governance
Launch rule
No real paid/live pilot cutover until readiness is green.
- Real sample payload and field dictionary must be accepted.
- Tenant isolation evidence must be retained.
- Monitoring, backups and notification delivery must be tested.
- Hardware/site deployment and client signoff must be captured.