Capabilities Project

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 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

• Seating Capabilities

• Capabilities Project - Seating Capabilities - Clean

Previous Work - for reference

Agenda:

• Review Seating

  • What is needed to get this to an initial version?

    • Complete Terminology/Information Alignment Tables

    • Align Capabilities ↔ VSS

• Next Steps

  • Open up and present to the greater community

    • Present as process for eliciting/modeling domain requirements?

  • Identify next domain(s)

Agenda:

• Action Item from last week. 

• Next level of detail

  • Detail out/cut information types as needed

  • Behavior

Agenda:

• Action Item from last week. 

• Next level of detail

  • Detail out/cut information types as needed

  • Behavior

Agenda:

• Action Item from last week.  Coloring the OEM columns

• Next level of detail

  • Detail out/cut information types as needed

  • Behavior

• Walk through the Seating Capabilities again with new colums

  • See Capabilities Project - Seating Capabilities#InformationTypes for comments additions and graphics

  • Should we compare to Android?

    • Yes, but ideally we would be providing them the capabilities not the other way around.

      • https://source.android.com/docs/automotive/vhal/seat-steering

    • Ultimately the result of this work could be teh northbound interface to Android and south of this work would be industry components

  • Ultimately we need to map this to VSS 

    • Currently in https://github.com/COVESA/vehicle_signal_specification/blob/master/spec/Cabin/Seat.vspec 

• Action Items

  • Continue Coloring the OEM columns @Magnus Feuer , @Melissa Morris , @Halim Ragab @graham.smethurst@bmw.de 

  • Make seat graphics editable - @graham.smethurst@bmw.de provide PPT

  • Get VSS engaged - @Paul Boyes to message VSS - https://github.com/COVESA/vehicle_signal_specification/blob/master/spec/Cabin/Seat.vspec

  • Reach out to CV oems @Xavier Vera can you participate?

  • Look at relationship to Android @group

Agenda:

• Address Previous Action Items

• Walk through the project Seating Capabilities 

  • Discussed the concept of core vs what the oems do today.  Ultimately there needs to be agreement on core or common capabilities vs oem specific

  •  There is a need for a capability discovery capability that lets you know what capabilites are available 

  • It was stated It is about an industry adopted standard for commodity funcionality

  • It could be blue skied too (ejector seat)

  • what does "position" mean to other OEMs

  • Child set idea suggested

• Next Steps

  • Start on next level of detail

  • Action Item:  Each OEM (@Magnus Feuer @Melissa Morris @Halim Ragab @graham.smethurst@bmw.de  to fill out the column with their company name on it.  Green for agree, yellow for maybe, and red for no.  All cells should have notes as appropriate and needed.   New rows my be added as necessary as well.

Agenda:

• Walk through the project Seating Capabilities 

• Discussion Points:

  • Haptics Control capability added 

  • The following Capabilities were suggested:

    • Get Supported Capabilities

      • List of available capabilities

      • Does capability exist?

    • Seat Configuration

      • What seats are available?

      • Are seats removable?

      • Is specific seat present or is it removed?

      • Cargo mode - flatten back/tilt to 180.

  • Control Seat Massage is likely considered competitive by OEMs and defined differently by each OEM.  That said it could be useful to have Massage Status or On/Off

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

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