Journey report
One cart journey from soak to aircraft handover with stage reconstruction, temperature summary, incidents, confidence, and source references.
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 telemetry into reports a client can actually use.
Internal system phase converts reconstructed cart journeys and cold-chain rule decisions into journey reports, breach reports, daily client summaries, executive pilot packs, and machine-readable evidence bundles. It is the commercial bridge between data collection and paid pilot proof.
StatusInternal / restricted surface. Not part of the public client walkthrough.
GCCAP
Sensor
Gateway
Evidence
Watchdog
Journey intelligenceRepresentative demo
Report typesJourney / breach / daily / executive / evidence
ExportsJSON / HTML / CSV / PDF
GovernanceDraft -> approved -> issued
Operational layer
What Build 6 delivers
This build creates the first evidence output layer. It does not just show dashboards; it creates controlled documents and evidence packs that can become client deliverables after review.
Breach report
One incident-focused report with severity, rule trace, recommendation, journey context, and evidence limitations.
Daily client report
Daily operational summary across journeys, evaluations, incident counts, confidence, and action queues.
Executive pilot report
Commercially useful management pack showing pilot value, major findings, evidence quality, and expansion logic.
Decision clarity
Report governance
Build 6 keeps high-risk outputs controlled until GCCAP is ready to release them.
Default stateDraft internal review. Nothing is automatically client-facing or public.
Approval stateReports can be approved or issued by an admin action for controlled pilot use.
Evidence packMachine-readable bundle containing journey, replay timeline, rule evaluation, incidents, source hashes, and limitations.
Public WatchdogStill blocked. Public scoring requires later aggregation, anonymisation, confidence thresholds, dispute process, and publication approval.
Production boundaryCurrent Build 6 reporting is file-backed and pilot-grade; production needs durable object storage and tenant security.
Data path
Where reports fit in the GCCAP evidence chain
Reports are generated only after the intake, telemetry, journey, and rules layers have created a defensible evidence base.
01Sensor captures cart temperature behaviour
02Gateway collects sensor records
03Raw payload is received and preserved
04Payload is mapped to sensor, cart, gateway, site and client
05Temperature event is normalised into the GCCAP event model
06Event is assigned to the correct cart journey stage
07Rules engine flags warning or review conditions
08Recovery and duration are calculated
09Data completeness and hardware health are assessed
10Evidence report is prepared for private client review
11Approved outputs can support client action and future benchmark methodology
Strongest next move
The commercial move
Use Build 6 to produce a controlled pilot evidence pack: one lane, selected carts, daily report, incident report, and executive findings. This is what converts technical testing into money.
Request a controlled pilot