As vehicles become software‑defined, OEMs might want to expose while at the the same time fully control reliable, consistent vehicle data to insurance partners, fleet operators, mobility services, ADAS analytics, anfd in‑car digital applications. Today, an OEM can offer either all vehicle data via OEM signature or close none at all. Today, every OEM solves this differently — resulting in fragmentation, high integration costs, and slow time‑to‑market. An OEM AOSP‑based VHAL offers a harmonized and scalable way to publish core vehicle data across models and regions using Android’s native Vehicle HAL framework. For OEMs, this creates tangible benefits: Lower engineering and integration cost through a unified data interface New revenue opportunities (insurance, UBI products, ADAS insights, fleet services) More competitive vehicles via lower TCO and better connected‑service offerings Faster ecosystem integration with insurers, fleets, mobility partners, and service providers Built‑in regulatory alignment through Android’s permission & transparency mechanisms In this workshop, we will walk through a hands‑on AOSP VHAL showcase using an emulator, demonstrate how standardized data flow and websockets enable partner integration, and collaboratively identify high‑value use cases. OEMs will shape which VHAL values should be prioritized to support real commercial opportunities and operational efficiencies.