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

The client portal now looks like a product, not a backend test page.

P26 finalises the client-facing portal layer for approval conversations. It shows what a client sees after GCCAP validates hardware and approves evidence: cart status, alerts, reports, evidence packs, device health, and action lanes.

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
BuildP26
FocusClient portal
ModeStatic preview + live login
NextP27 command centre

Decision clarity

What changed in P26

P26 upgrades the client portal from a restricted access page into a buyer-readable product layer.

Portal previewClient dashboard, cart list, selected cart evidence, alerts, reports, device health and action lane
Claim controlStatic preview is labelled as simulated until hardware validation and approved reports exist
Tenant boundaryClient sees own carts, approved reports and client-visible alerts only
Backend continuityExisting portal login/API flow remains available for local/private Node testing

Data path

Portal evidence path

Sensor event -> gateway receipt -> normalised telemetry -> journey stage -> rules/incident -> approved report -> client portal evidence pack.

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

Next build

P27 should finalise the internal GCCAP command centre so the client portal and internal command layer are clearly separated and commercially believable.

Request a controlled pilot