Overview
ISO/TS 20077-3:2024 - Road vehicles - Extended vehicle (ExVe) methodology - Part 3: Upstream process to develop services - defines a standardized, vendor-neutral process to initiate and facilitate requests from service providers (SPs) to vehicle manufacturers (VMs) for access to vehicle data and functions via Extended Vehicle (ExVe) interfaces. The Technical Specification complements ISO 20077-1 and ISO 20077-2 and focuses on the upstream steps: identification, request submission, confidentiality, basic need expression, VM analysis, iterative co‑design, and decisions on service deployability. Commercial negotiation and internal VM/supplier R&D use cases are explicitly excluded.
Key topics and technical requirements
- Request initiation and identification form: SPs are expected to complete a minimum identification template (Annex A) on the VM’s web entry point to clarify the requester profile and use case intent.
- Findability and keywords: VMs should publish clear contact/process pages and use searchable keywords (Annex B) to improve discovery of ExVe access points.
- Confidentiality: Mutual confidentiality agreements (e.g., NDAs/MoUs) are recommended to protect intellectual property during exchanges.
- API catalogue and availability: VMs should supply an API catalogue for already available data/functions to expedite access without repeating the full request process.
- Basic need expression: Use the technical request template referenced in ISO 20077-2 to describe use cases, especially where safety and security are involved.
- Response timelines and communication: VMs shall acknowledge requests within 15 working days and provide timely updates and a conclusive answer within a reasonable timeframe.
- Co-design iterative process: SPs and VMs engage in iterative negotiation to determine feasibility, acceptable compromises, data/function limits, and implementation constraints.
- Service deployability decision: Parties jointly assess viability; if viable, they proceed toward technical implementation (and potentially contractual phases). If not, the VM must justify refusal.
- SLA guidance: Application of SLA principles per ISO/IEC 20000-1 is recommended for operational service delivery expectations.
Applications and who uses it
- Primary users: Service providers, vehicle manufacturers, offering parties (API/platform providers), and suppliers integrating with ExVe interfaces.
- Secondary stakeholders: telematics firms, fleet operators, mobility-as-a-service (MaaS) developers, regulators and integrators who need a repeatable upstream process to request vehicle data or functions.
- Practical benefits: faster onboarding of third‑party services, clearer legal/technical expectations, reduced time-to-market for telematics and mobility services, and a structured co‑design path to resolve technical, legal, or safety constraints.
Related standards
Keywords: ISO/TS 20077-3, Extended Vehicle, ExVe, vehicle data access, API catalogue, service provider onboarding, upstream process, co-design, SLA.