Sensor identity and cart mapping
Every device must map to the correct cart, client, site and journey.
Technical integration pathway
Hardware validation first. Live data second. Production scale only after proof.
GCCAP is prepared around a sensor-to-gateway-to-platform architecture for airline catering cart monitoring. The live pilot pathway validates sensor placement, gateway capture, timestamp integrity, stored-record recovery, duplicate handling and data quality before wider deployment.
StatusRepresentative demo available now. Live pilot reporting activates after hardware validation, site approval, first payload proof and agreed data governance controls. Stage 1 avoids washer exposure until permanent mounting is validated.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
InputSensor/gateway
NormaliseEvent schema
SeparateTenant data
OutputDashboards + reports
Operational layer
What must be proven before live pilot activation.
The integration pathway is deliberately strict because evidence quality depends on original data integrity.
Gateway capture
Facility/truck gateways must capture readings reliably enough for the pilot purpose.
Payload format
GCCAP must understand temperature, timestamp, device ID and gateway source fields.
Raw data preservation
Raw payloads are stored before normalised events are created.
Duplicate and backfill handling
Live and recovered records must be reconciled without inflating events.
Evidence report generation
The platform must convert validated trial data into a controlled client report.