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

Operate GCCAP without hand-editing the evidence system.

Internal system phase creates the private back-office layer needed to onboard clients, facilities, carts, FMC150 gateways, EYE EN12830 sensors, rules, users, support items and commercial status in a controlled, auditable way.

Return to public platform Open portal access

StatusInternal / restricted surface. Not part of the public client walkthrough.

GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Admin scopeClients + facilities + devices
GovernanceAudit logs + corrections
CommercialBilling status + notes

Operational layer

What Build 12 controls

GCCAP now has an internal setup and operations layer so future pilots do not require developers to edit raw files or manually wire clients to devices.

Client creation

Create and maintain airline, caterer, airport and pilot-client records.

Facility setup

Register airports, kitchens, loading bays, truck zones and operational areas for later geofence and journey logic.

Device assignment

Link FMC150 gateways, EYE EN12830 sensors and carts to the correct client, facility and operational lane.

Commercial status

Track pilot candidate, paid pilot, contract, expansion and suspended status without exposing this to clients.

Decision clarity

Back-office objects

Build 12 creates the operating records needed before GCCAP can onboard new clients repeatedly.

ClientsCommercial, operational and data status for each customer.
FacilitiesAirports, catering facilities, loading bays and truck zones.
RegistriesGateways, sensors, carts and assignments.
Rule configsClient threshold and soak assumptions for the rules engine.
UsersPortal user records and same-client access controls.
SupportTickets, corrections, notes, access logs and audit records.

Governance

What stays controlled

This build does not remove the need for production security or formal governance.

  1. No direct public access to back-office data.
  2. Manual corrections create requests and audit trails; source evidence is not silently overwritten.
  3. Rule changes are recorded and remain internal until approved.
  4. Billing status is internal only.
  5. Production onboarding still requires managed database, MFA, backups, monitoring and legal/commercial templates.