Jaguar Land Rover · Cloud platform & connected vehicles
Enable data in both directions. Build once for the platform.
Owning cloud-side bidirectional large-file transfer across HD Maps, scenario recording and vehicle logging.
Downloads: HD Maps & scenario recording · Uploads: recording & logging
Four vehicle-data use cases. Uploads and downloads through one platform.
01 / problem
The problem to solve
Connected vehicles both consume large datasets and generate data that must reach cloud services. HD Maps, Special Scenario Recording, Secure Logging and Central Logging had different transfer needs, integration dependencies and delivery priorities. Building separate solutions for each consumer would fragment capability and increase operational complexity and cost.
02 / decision
The decision
I prioritised a reusable, bidirectional cloud-side File Transfer Agent (FTA) rather than a series of product-specific integrations. The platform needed to support cloud-to-vehicle downloads as well as vehicle-to-cloud uploads, while balancing immediate partner commitments, reliability, architecture and long-term operating costs.
03 / approach
How I approached it
As Senior Product Owner, I owned and prioritised the FTA Cloud backlog and coordinated delivery across cloud engineering, onboard teams, architecture and consuming product owners. HD Maps required cloud-to-vehicle distribution; Special Scenario Recording required both download and upload flows; Secure Logging used uploads; and Central Logging combined completed upload work with further download and configuration integration. I managed requirements around transfer resilience, file metadata, content distribution and integration readiness, and worked with external partners including NVIDIA on architectural and cost trade-offs.
04 / outcome
What changed
The shared FTA Cloud capability supported delivery and integration across four connected-vehicle use cases at different stages of maturity. Secure Logging upload was completed; Central Logging upload was completed with download/configuration work continuing; HD Maps and Special Scenario Recording integration remained in progress. The product direction preserved reusable upload and download infrastructure instead of tying the platform to a single use case. These are delivery states, not a claim of fleet-wide deployment or measured performance improvement.
05 / What I take forward
What I take forward
A platform succeeds when different products can reuse it reliably in both directions. Product decisions must account for vehicle connectivity, interruption recovery, metadata contracts, cloud distribution and ingestion costs, as well as the competing milestones of the teams consuming the capability.
The question I ask:
Does this decision make the shared platform more useful to the next consuming product?