1 / 45

Enabling innovation through open standards in the transportation domain

Explore the impact of open standards and data-centric approach in the transportation sector, focusing on connected vehicles and smart cities. Learn about the importance of standardized data architecture and taxonomy. Source: BMW Group Research 2019.

provencher
Download Presentation

Enabling innovation through open standards in the transportation domain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enablinginnovationthrough open standards in thetransportationdomain BMW Group | Research | 2019 Adnan Bekan

  2. Data-centric approach are designed with data sharing in mind. The Data is permanent and enduring, and applications can come and go. 1SOURCE: The Data-Centric Revolution, Dave McComb

  3. NUMBER OF CONNECTED VEHICLES INCREASING The global connected cars market is expected to grow 270% by 2022. In Europe areexpectedtotouchnearly 100% connectedcarpenetrationby 2020, withearlyadoption kick-in due toeCallmandate SOURCE: Counterpoint Research ‘Global Connected Car Tracker 2018’

  4. Connected? What does it mean?

  5. Smart Ciity … Web of Services

  6. Smart Ciity … Web of Systems

  7. context matters.

  8. Context is created through a common understanding of DATA.

  9. BUT, where to start if your data is: • unstructured • lagging description • version dependent • application centric?

  10. Follow your intuition? Common data architecture paradigm Source: https://www.instagram.com/p/BxXl7wLAX_P

  11. Follow your intuition? Common data architecture paradigm • Doesn’t scale • Hard to maintain Source: https://www.instagram.com/p/BxXl7wLAX_P

  12. ACT Or start with a common goal! ANALYSE CREATE AGGREGATE COMMUNICATE

  13. But how to achieve that?

  14. Divide the problem!

  15. Raw values

  16. Correct & relevant

  17. Connect other sources

  18. ACT!

  19. Now a common rule set.

  20. DATA CENTRIC APPROACH 1 Data is a keyassetof an organization. 1SOURCE: The Data CentricManifesto

  21. DATA CENTRIC APPROACH Data isself-describinganddoes not rely on an applicationforinterpretationandmeaning. 2 1SOURCE: The Data CentricManifesto

  22. DATA CENTRIC APPROACH Access toandsecurityofthedatais a responsibilityofthedatalayer, and not managedbyapplications. 3 1SOURCE: The Data CentricManifesto

  23. DATA CENTRIC APPROACH Applicationsareallowedtovisitthedata, performtheirmagicand express theresultsoftheirprocess back intothedatalayerfor all toshare. 4 1SOURCE: The Data CentricManifesto

  24. DATA CENTRIC APPROACH 5 Data isexpressed in open, non-proprietaryformats. 1SOURCE: The Data CentricManifesto

  25. What to standardize?Choose your core competence!

  26. Standardization # IoT devices # Connected vehicles 5 Data isexpressed in open, non-proprietaryformats. 1SOURCE: The Data CentricManifesto

  27. VEHICLE SIGNAL SPECIFICATION. Defines a taxonomyforattributes, sensorsandactuatorsofvehicles.

  28. TAXONOMY. „…isthescienceofclassificationaccordingto a pre-determinedsystemwiththeresultingcatalogusedtoprovide a conceptualframeworkfordiscussion, analysis, orinformationretrieval. In practice, a goodtaxonomyshouldbe simple, easy torememberand easy touse.“ Origin: "taxis" = arrangementordivision "nomos" = law Source: https://searchcontentmanagement.techtarget.com/definition/taxonomy

  29. VEHICLE SIGNAL SPECIFICATION. VEHICLE Everythingstartswith fromthevehicle…

  30. VEHICLE SIGNAL SPECIFICATION. VEHICLE CHASSIS Everythingstartswith fromthevehicleandfollowsthephysicalstructure. … CABIN DRIVETRAIN

  31. VEHICLE SIGNAL SPECIFICATION. VEHICLE CHASSIS Everythingstartswith fromthevehicleandfollowsthephysicalstructure. … CABIN DRIVETRAIN AXLE DOOR SEAT

  32. VEHICLE SIGNAL SPECIFICATION. VEHICLE CHASSIS Everythingstartswith fromthevehicleandfollowsthephysicalstructure. … CABIN DRIVETRAIN AXLE DOOR SEAT ISOPEN ISLOCKED ISBELTED HASPASSENGER

  33. VEHICLE SIGNAL SPECIFICATION. VEHICLE CHASSIS Everythingstartswith fromthevehicleandfollowsthephysicalstructure. … CABIN DRIVETRAIN AXLE DOOR SEAT WHEEL ISOPEN ISLOCKED ISBELTED HASPASSENGER TIRE PRESSURE

  34. VEHICLE SIGNAL SPECIFICATION. VEHICLE BRANCHES actaslogicalcategoriesandprovidethestructureofthetree. CHASSIS … CABIN DRIVETRAIN AXLE DOOR SEAT WHEEL ISOPEN ISLOCKED ISBELTED HASPASSENGER TIRE PRESSURE

  35. VEHICLE SIGNAL SPECIFICATION. VEHICLE BRANCHES actaslogicalcategoriesandprovidethestructureofthetree. Theycanhaveinstanceattributestodeterminehowoftentheyoccur. CHASSIS … CABIN DRIVETRAIN Row [1,2] Position [1,3] AXLE DOOR SEAT WHEEL ISOPEN ISLOCKED ISBELTED HASPASSENGER TIRE PRESSURE

  36. VEHICLE SIGNAL SPECIFICATION. VEHICLE BRANCHES actaslogicalcategoriesandprovidethestructureofthetree. Theycanhaveinstanceattributestodeterminehowoftentheyoccur. CHASSIS … CABIN DRIVETRAIN LEAFS actasdatacontainers. Determiningdatatype, description, type (attribute, sensor, actuator, etc.). Theyareaddressed in dotnotationofthepaththreoughthetree. AXLE DOOR SEAT WHEEL ISOPEN ISLOCKED ISBELTED HASPASSENGER TIRE PRESSURE

  37. Vehicle taxonomy offers information, which is necessary to understand the context and derive knowledge. Smart Ciity …

  38. How VSS is used?

  39. VSS @World W3C Automotive WG: VSS asthecoredomainmodelforvehiclesignals. VSS Ontology: Derive an ontologyfrom VSS andpreparethestepfrominformationtowardsknowledge. W3C Web of Things: Usedefinedstandardwithautomotiverequirementsand VSS ontology. W3C Transportation Workshop: Connect transportationdomainwithVSSoas THE vehiclesensorontology.

  40. Vehicle Shadow - VSS @BMW

  41. Vehicle Shadow - VSS @BMW • ServedatawithGraphQL • Schema generatedfrom VSS Transformation ofdatatowardsinformation realized in backend. The closeritmovestothesensor, theeasier tomaintaintheentiredatachain.

  42. Two open questions: Howto find an alignment on a vehicletaxonomyforexistingstandardsandconnectittootherdomains? 1 2 Howtoavoidthe n+1 issuefornewstandards?

  43. One possible answer: • Successful definition of the transportation domain. • Defining cross domain use cases. • Identifying solutions for cross domain user identification and privacy. • Defining rules, guidelines and tools for creating a driving context.

  44. Questions?

More Related