Page History

Overview

Today OEMs implement common vehicle capabilities, such as seat and HVAC differently on a variety of electronic architectures with different interfaces often tied to the chosen architecture.  The result is unnecessary complexity and inefficiency in integration and long term support.   

Shared capability definitions, abstracting and encapsulating vehicle capabilities from specific technical implementations and hardware can reduce the complexity of integration, ease long term support, and promote re-use.

The goal of the Capabilities Project Charter

Meeting Notes

20241025

is for participating OEMS to identify and describe vehicle capabilities in a technology neutral manner/format abstracted from underlying hardware.

Project Charter

The Project Charter can be found here

Current Work

• Seating Capabilities

Previous Work - for reference

Meeting Notes

20241025

Agenda

• Walk through the project Seating Capabilities 
• Discussion points:
  
  • Commercial vehicle seat "resources" might be different
  • Discussed Information Type definitions
    • They are critical to understanding Capabilities.  This is the information that is required for the capability.
    • Agreeing on Definitions is critical
• Action Item:  Diagrams to help with definitions Halim Ragab 
• Action Item:  Provide updated version of uServices Halim Ragab 
• Action Item:  Complete Seating Capabilities Paul Boyes and Halim Ragab 
• Action Item:  Provide more definition to Information Types
• Action Item:  Recruit other OEMs
• Agreed to schedule Friday meetings through November

20241018

Agenda

• Walk through the project Charter
• Discussion points:
  
  • Why create and implement another entertainment api?
  • Regulation 
  • Test suite
  • Make internal integration easier
  • Just because capabilities are defined does not mean they are implemented and available
  • Should we do diagnostic/non-functional capabilities as well?
• Action Item:  Start with translating Seat Capabilities from uServices 

...