There are four types of MOBI Working Group Standards:
0001 – Business White Papers (WP)
MOBI Business White Papers are high-level business reviews that discuss issues and propose solutions to the world’s most pressing transportation challenges with consideration to ecosystem stakeholders, new strategies, emerging technologies, and global policies.
0002 – Use Cases and Business Requirements (UC)
MOBI Use Cases and Business Requirements documents describe pain points, stakeholder responsibilities, and high-level business requirements potential solutions must meet in order to resolve stakeholder needs. UCs also detail workflows for particular applications and are technology-agnostic.
0003 – Technical Specifications (TS)
MOBI Technical Specifications define recommended minimum interfaces between systems/modules and data specification exchanged in the process leading up to a reference implementation. This process allows independently developed systems to be interoperable.
0004 – Reference Implementation Architectures (RI)
MOBI Reference Implementation Architectures prescribe and recommend a solution architecture stakeholders can refer to when they deploy solutions, ensuring that stakeholder requirements described in TS and UC are met in the process. RIs are vendor-agnostic.
Full access to White Papers and Use Cases and partial access to Technical Specifications and Reference Implementation Architectures is available below. Full access to Technical Specifications and Reference Implementation Architecture documents is reserved for MOBI members. If you are interested in becoming a member, please contact Matt Shi at email@example.com or fill out our Membership Inquiry Form.
Before reading MOBI Standards, you might find it helpful to view the MOBI Glossary of Terms. The Glossary of Terms is a compilation of terms commonly found in MOBI Standards and their definitions.
The VID working group aims to define a digital document that is a verifiable link to a specific vehicle, a minimum representation of that vehicle’s digital twin. VID can be used to establish existence, manage access control, confirm ownership history, and contain key events in the life of a vehicle.
1.VID Business White Paper
The VID White Paper introduces a business review for the MOBI Vehicle Identity (VID) to accompany the standards created by the Vehicle Identity working group.
2.VID I Technical Specifications
The VID I Technical Specification document specifies the first standard for Vehicle Identity (VID), which represents the principal digital foundation of future mobility.
3. VID II Use Cases and Business Requirements
The VID II UC extends VID I to data related to lifetime events and transfer of ownership, exploring two main use cases: vehicle registration and maintenance traceability.
4. VID II Reference Implementation Architecture
The VID II Reference Implementation Architecture introduces a technical standard for selected VID-based use cases, describing repeated information flows that serve as building blocks for more complicated use cases.
The EVGI working group aims to aid the increasing adoption of electric vehicles by creating interoperable systems for governments, utilities, and the mobility industry alike. These systems will enable a better way to manage the grid load, calculate carbon offsets, and generate carbon credits, facilitating the implementation of peer-to-peer services. The first standard defines the system and data requirements for three core use case areas: Vehicle to Grid (V2G), Peer to Peer (P2P), and Tokenized Carbon Credits (TCC).
1. EVGI Business White Paper
The EVGI White Paper covers the current state of affairs with regard to powering electric vehicles, the growth of decentralized renewable energy production, and carbon credit generation/trading. The WP explores key use cases in interoperable system applications and explains the role of the standard in aiding this development.
2. EVGI Technical Specifications
The EVGI Technical Specifications specifies the high-level system design, reference architecture, multi-party processes, and EVGI-specific data structures that are utilized throughout the ecosystem. The TS provides guidance toward the implementation of EVGI Standards, covering three primary use cases and their process flows.
The CMDM working group aims to enable a DLT-based data marketplace for all stakeholders of the mobility ecosystem — including OEMs, insurance providers, infrastructure operators, and others — to effectively share data with their business partners while complying with emerging regulatory and industry best practices for preserving data privacy and property rights.
The CMDM Standards provide a foundation for a multitude of applications, including but not limited to V2X data exchange, connected vehicle commerce, and sharing/monetizing AV driving data for better driving algorithms through machine learning.
1. CMDM Business White Paper
The CMDM White Paper covers the current state of affairs with regard to mobility ecosystems and data exchange within the automotive industry. The WP explores key use cases in short, medium, and long-term time horizons, and explains the role of the standard to aid this development.
2. CMDM Technical Specifications
The CMDM Technical Specifications specifies the high-level system design, reference architecture, multi-party processes, and specific data structures that are utilized throughout the ecosystem. The TS provides guidance to implementation for the CMDM standard, covering three primary use cases and their process flows: Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2X), and Infrastructure-to-Infrastructure (X2X).
The FSSC working group strives to improve accuracy and transparency, create operational efficiencies, minimize fraud risks, and save on costs and time in the execution of financings, including securitizations, for all entities in the financing lifecycle. The FSSC Standards leverage distributed ledger technologies to create a trust layer for transactions and data exchange within a shared digital ecosystem.
1. FSSC Business White Paper
The FSSC White Paper provides an overview of a variety of use cases that were considered by the FSSC WG, including Dealer Floorplan Financing and Fractional Ownership of Mobility Assets. The Working Group considered both B2B (business-to-business) and B2C (business-to-consumer) use cases, and each section of this paper focuses on B2B and B2C use cases separately.
2. FSSC Technical Specifications
The FSSC Technical Specifications specifies high-level system design, reference architecture, multi-party processes, and FSSC-specific data that is used throughout the ecosystem. The TS prescribes a digital ecosystem where entities are able to securely authenticate each others’ identities, share data, and record transactions.
The SC working group assesses the value proposition of blockchain in mobility supply chain management for stakeholders of the procurement, logistics, and finance or accounting divisions, including Original Equipment Manufacturers, N-tier suppliers, and further business partners. The group aims to create interoperability standards to bring operational efficiencies and increased visibility through the N-tiers; enable provenance, tracking, and authenticity of parts and vehicles; and improve conflict resolution and settlement with distributed ledger technology (DLT).
1. SC Use Cases and Business Requirements
The SC UC describes the parts traceability problem by breaking down the current workflow into nuanced steps, specific steps in the workflow that can be enhanced/modified DLT/blockchain, and high-level business requirements to build an enhanced parts traceability solution.
2. SC Reference Implementation Architecture
The SC RI focuses on standardized bilateral communication using extensive API calls, decentralized identity with blockchain/DLT as a trust anchor. The RI discusses the benefits and potential interplay of different blockchain setups, embedded into a system that provides a basic communication layer, and the role of privacy-enhancing technologies.