CCS Proof-Of-Concept - Work Breakdown Structure

• Implementation of SOME/IP client
• Either locally cached during uptime of system or
• Stored and indexed in a database to allow access to historical data
  • Selection of database
  • Implementation of database schema

In-vehicle

Data server

• Data server implementation for W3C Gen2
  • Reference implementation exists in GitHub https://github.com/MEAE-GOT/W3C_VehicleSignalInterfaceImpl/tree/master/server

OEM Cloud

Vehicle client

• Implementation of the client to the vehicle server
  • Reference implementation exists in GitHub https://github.com/MEAE-GOT/W3C_VehicleSignalInterfaceImpl/tree/master/client

OEM Cloud

VSS2 data lake

• Selection of libraries and database to handle data lake

OEM Cloud

Identity management

• Implementation of end-user login and authentication using OpenID

OEM Cloud

Access management

• Implementation of authorization between end-user and 3rd party application or Neutral Server using OAuth2

OEM Cloud

Resource management

• Implementation of basic API management
• Implementation of a GraphQL API using the VSS2 schema

Neutral Server

Data Marketplace

• Separate instance that consumes the OEM Cloud OAuth2 and GraphQL APIs

• Separate instance that consumes the OEM Cloud OAuth2 and GraphQL APIs
• Separate instance that consumes the Neutral Server/Data Marketplace APIs