TimescaleDB readiness
Provider and extension readiness for PostgreSQL time-series workloads.
Internal GCCAP operating surface
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
P13 adds the time-series production control layer for TimescaleDB readiness, hypertable design, telemetry partitioning, compression, retention, rollups, high-volume query patterns, migration planning and load-test assumptions.
StatusInternal / restricted surface. Not part of the public client walkthrough.
Operational layer
These controls prepare GCCAP for high-volume cart, sensor and gateway readings without turning PostgreSQL into an unbounded telemetry table.
Provider and extension readiness for PostgreSQL time-series workloads.
Telemetry, gateway health, alerts and journey telemetry split into time-partitioned structures.
Rules for live, warm, archive and legally retained evidence data.
Minute, hour, day and journey-level rollups for dashboards, Watchdog and reports.
Operational layer
P13 does not claim live TimescaleDB cutover. It defines what must be true before production telemetry storage is approved.
Managed PostgreSQL/TimescaleDB host not connected.
High-volume reading assumptions must be tested with expected cart and site volume.
File-backed and PostgreSQL schema data needs cutover verification.
Evidence, privacy and commercial retention classes need approval.