Page History

Context: As an Idea from COVESA marketing team weekly meeting in-regards to the topic of increasing OEM participation in projects we discussed using EV-charging BoF as a topic area for creating use-cases and value propositoins that could be used to eventually create strong and engaging storyline content that helps inspire and onboard OEMs in the future.

Already things that pop to mind are

• VSS spec for charging & battery related signals & data > I started to categorize what could become branches of a charging .vspec or even potentially multiple .vspec's

> vehicle info - trip data, make & model, battery data > health, time to 80% SoC, charge curve etc

> charge site info - environmental data from vehicle sensor (VSSo?) + user feedback +energy providers info

> charge point info – exact location of charger per vehicle (GPS/dead reckoning), occupancy, health, total charges, number kWh, avg charge duration, max power

• VSC spec for standardizing EV charging functionality such as: Lock/unlock charge port (this has been a personal pain on multiple occasion for myself), perhaps a charge event type service could be standardized + others

...

• digital twin
• SdV service implementation (V-app) that aggregates and and reports all data/functionality relating to a specific charging use-case (template charging V-app could be created with say Eclipse Velocitas & deployed to hardware with Leda)

ISO15118 > charging std needs to be considered for technical content also

We need to create a Business Value proposition for EV charging use-cases! "Techie 2 Becky" user experience can be mapped pretty well already as Ford presentation already details various pain points & myself and other EV drivers can flood this with numerous other issues I'm sure!

Context: As an Idea from COVESA marketing team weekly meeting in-regards to the topic of increasing OEM participation in projects we discussed using EV-charging BoF as a topic area for creating use-cases and value propositoins that could be used to eventually create strong and engaging storyline content that helps inspire and onboard OEMs in the future.

Already things that pop to mind are

• VSS spec for charging & battery related signals & data > I started to categorize what could become branches of a charging .vspec or even potentially multiple .vspec's

> vehicle info - trip data, make & model, battery data > health, time to 80% SoC, charge curve etc

> charge site info - environmental data from vehicle sensor (VSSo?) + user feedback +energy providers info

> charge point info – exact location of charger per vehicle (GPS/dead reckoning), occupancy, health, total charges, number kWh, avg charge duration, max power

• VSC spec for standardizing EV charging functionality such as: Lock/unlock charge port (this has been a personal pain on multiple occasion for myself), perhaps a charge event type service could be standardized + others

...

• digital twin
• SdV service implementation (V-app) that aggregates and and reports all data/functionality relating to a specific charging use-case (template charging V-app could be created with say Eclipse Velocitas & deployed to hardware with Leda)

ISO15118 > charging std needs to be considered for technical content also

We need to create a Business Value proposition for EV charging use-cases! "Techie 2 Becky" user experience can be mapped pretty well already as Ford presentation already details various pain points & myself and other EV drivers can flood this with numerous other issues I'm sure!