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

Inspect the telemetry pipeline before building cart journey intelligence.

Pipeline Lab shows whether mappable intake events are being queued, deduplicated, processed, stored as time-series points, and prepared for replay. It is an internal diagnostic surface, not a client portal.

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
PurposePipeline inspection
AccessAdmin-gated APIs
BoundaryNot a client portal

Build 3 operational tool

Telemetry pipeline control room

Inspect the durable queue, processed telemetry stream, time-series points, dedupe status, late/offline indicators, and replay controls before client portal or journey-engine builds consume the data.

Admin access

Use the same GCCAP_ADMIN_TOKEN configured for Build 2 intake APIs.

Waiting for server response.

Pipeline controls

Run processing manually, or replay all Build 2 normalised events after mappings are improved.


    

    

      
Pipeline status

      

        Stats load after token is saved.
      

    

    

      
Recent processed events

      

    

    

      
Recent time-series points

      

    

  






  

    
Governance

    
Pipeline lab operating rules

    
Use the lab to prove data movement before building conclusions or client-facing reports.

  

  
    
    
  1. Never expose Pipeline Lab publicly without authentication and network controls.
  2. Use Intake Lab to send sample payloads, then Pipeline Lab to inspect downstream processing.
  3. Replay normalised events after field mappings are updated from the real Teltonika/CtrlOps sample extract.
  4. Treat Build 3 storage as pilot/development storage; Build 7/20 must migrate this into production-grade database, queue, and monitoring infrastructure.
    5.