The COVESA CV BoF group has been having various initial alignment calls with various similar efforts, more in heavy duty truck space than light vehicle (passenger car, delivery van). Those efforts are seeking specific signals and fidelity of them to be available consistently on OBDII or alternate in-vehicle interface. CV BoF is focusing more on signals to be collected by OEM and exposed to third party providers for fleet operations.
CV BoF signals ask is more modest in its data ask of OEM Cloud Offering than the other efforts for the In-Vehicle Data Port (OBDII, RP1226). COVESA and AutoSAR are advancing VISS for the In-Vehicle API interface where vetted third parties will be allowed to run logic. We expect the initial ask for signals to be made available for fleet operations on an In-Vehicle API to be essentially the same as what is being defined for the in-vehicle data ports.
Efforts to seek alignment, coordination are:
RP1226 - US/NA, HD trucks and currently working towards complying with the data requirements from the California Air Resource Board (CARB) Inspection and Maintenance
VDV - German public sector (eg transportation - buses) requirements for vehicle acquisition
FMS - EU in-vehicle data port access, defined by HD OEM. rFMS is for cloud based offering by OEM
With the exception of VDV, the rest are recommendations and unfortunately not all OEM, even when they have agreed on the signals lists, are providing them. Alignment between these efforts will make it easier for OEM to adopt, encourage consistency, support future standardized in-vehicle API and fleets to know which vehicle information platforms can meet which of their needs.
The COVESA CV BoF group has been having various initial alignment calls with various similar efforts, more in heavy duty truck space than light vehicle (passenger car, delivery van). Those efforts are seeking specific signals and fidelity of them to be available consistently on OBDII or alternate in-vehicle interface. CV BoF is focusing more on signals to be collected by OEM and exposed to third party providers for fleet operations.
CV BoF signals ask is more modest in its data ask of OEM Cloud Offering than the other efforts for the In-Vehicle Data Port (OBDII, RP1226). COVESA and AutoSAR are advancing VISS for the In-Vehicle API interface where vetted third parties will be allowed to run logic. We expect the initial ask for signals to be made available for fleet operations on an In-Vehicle API to be essentially the same as what is being defined for the in-vehicle data ports.
Efforts to seek alignment, coordination are: RP1226 - US/NA, HD trucks and currently working towards complying with the data requirements from the California Air Resource Board (CARB) Inspection and Maintenance
VDV - German public sector (eg transportation - buses) requirements for vehicle acquisition FMS - EU in-vehicle data port access, defined by HD OEM. rFMS is for cloud based offering by OEM
With the exception of VDV, the rest are recommendations and unfortunately not all OEM, even when they have agreed on the signals lists, are providing them. Alignment between these efforts will make it easier for OEM to adopt, encourage consistency, support future standardized in-vehicle API and fleets to know which vehicle information platforms can meet which of their needs.