Automotive Knowledge Model (AKM) for Automobiles

Automotive Knowledge Model (AKM) is an expressive and extensible vocabulary and data model that provides semantics and standards-based signals, metrics, DIDs, and DTCs for automobiles. This model includes sample signals like HVAC station temperature settings and features a comprehensive data structure for automotive information management.

• Automotive Knowledge Model
• AKM
• Automobiles
• Signals
• Data Model

araminta Follow

Uploaded on Jul 05, 2024 | 2 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. Automotive Knowledge Model (AKM)

2. Alan Freedman Principal Data Architect Ford Motor Company afreedm2@ford.com

3. Mohit Yadav Software Engineer Ford Motor Company myadav5@ford.com

4. An expressive and extensible An expressive and extensible An expressive and extensible An expressive and extensible AKM semantics and standards-based semantics and standards-based semantics and standards-based semantics and standards-based vocabulary and data model vocabulary and data model vocabulary and data model vocabulary and data model for automobiles for automobiles for automobiles for automobiles

5. AKM Version 1.0 Signals - Metrics Version 2.0 Signals - DIDs Version 3.0 Signals - DTCs Version 4.0 ?

6. { Sample Signal "id": "HVACStation.Row1.Driver.AmbientAirTemperature", "name": "HVAC Station Row1 Driver Air Temperature", "definition": The air temperature setting serving row 1 driver side", "entityTypeID": "Metric", "property": { referentEntityTypeID": "Property", "referentID": "AmbientAirTemperature" }, "featureOfInterest": { " referentEntityTypeID": "FeatureOfInterest", "referentID": "HVACStation.Row1.Driver" }, "representations": [ { "entityTypeID": "Representation", "schema": "VehicleSignalSpecification", "id": "Vehicle.Cabin.HVAC.Station.Row1.Driver.Temperature", "xsdDataType": "float", "unit": "degree_celsius" }, { "entityTypeID": "Representation", "schema": "CANBus", "id": "DrvrVntTmp", "xsdDataType": "short", "unit": "degree_celsius" } ] }

7. { "Metric": { "$id": "akm.Metric", "description": "A particular property of a particular feature of interest", "type": "object", "allOf": [ { "$ref": "akm.Entity" }, { "$ref": "akm.extension.Metric" } ], "properties": { "entityTypeID": { "type": "string", "description": "A classfication of objects that share semantics, structure, and often behavior", "const": "Metric" }, "property": { "type": "object", "$ref": "akm.Reference", "description": "A reference to the quality or quantity that describes a feature of interest. Set entityTypeID to Property" }, "featureOfInterest": { "type": "object", "$ref": "akm.Reference", "description": "A reference to the thing whose property is being observed or manipulated. Set entityTypeID to FeatureOfInterest" } } } } Sample Spec

8. Expressive and Extensible AKM Data Model

9. Requirements - Expressive An expressive and extensible semantics and standards-based vocabulary and data model for automobiles An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Signal Schema Feature of Interest Property Metric part of is a Unit Data Property Object Property Value Data Type

10. Requirements - Expressive An expressive and extensible semantics and standards-based vocabulary and data model for automobiles An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Vehicle Cabin Chassis Feature of Interest HVAC Seats Metric Seat.Row1.Driver part of is a Seatbelt.Row1.Driver SideAirbag.Row1.Driver SideAirbag.Row1.Driver.IsDeployed SideAirbag.Row1.Driver.IsEnabled

11. Requirements - Expressive An expressive and extensible semantics and standards-based vocabulary and data model for automobiles An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Feature of Interest Vehicle Component Vehicle Process Comfort Component Feature of Interest Safety Component Metric Airbag Seatbelt part of is a CurtainAirbag SideAirbag SideAirbag.Row1.Driver.IsDeployed SideAirbag.Row1.Driver.IsEnabled

12. Requirements - Expressive An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Data Type boolean Property IsEnabled IsDeployed Feature of Interest SideAirbag.Row1.Driver.IsEnabled LaneDepartureDetection.IsEnabled Metric part of is a

13. Requirements - Expressive An expressive and extensible semantics and standards-based vocabulary and data model for automobiles schema data data data feature_of_interest_classes vehicle master_data features_of_interest cabin features_of_interest metrics powertrain properties properties chassis static_properties data_types dynamic_properties reference data_types units reference_data units

14. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Model is declared using JSON Schema (https://json-schema.org/) Well-known schema language Very expressive Abundant tooling (editors, validators, converters, documentation generators ) Well-documented Many implementations and examples Standardized data types and formats The AKM becomes self-documenting

15. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Defining an entity type Inheritance "Metric": { "$id":"akm.Metric", "description": "A signal that describes a particular property of a particular feature of interest", "type": "object" "allOf": [ { "$ref": "akm.Entity" }, "entityTypeID": "Metric", "definition": "Indicates whether the Airbag at Row 1 Driver Side has been deployed ", "internalID": 60240 "iotProcedureType": "Observation" id * name * definition * entityTypeID * comment deprecation "id": "Airbag.Row1.DriverSide.IsDeployed", "name": "Row 1 Driver Side Airbag is Deployed", { internalID * emissionRate iotProcedureType "$ref": "akm.extension.Metric" } ],

16. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Defining an entity type Linking "Metric": { "featureOfInterestID": { "type": "object", "description": "The identifier of the thing whose property is being observed or manipulated", "properties": { "entityTypeID": { "type": "string", "const": "FeatureOfInterest" }, "id": { "type": "string" } } } } "id": "Airbag.Row1.DriverSide.IsDeployed", "featureOfInterestID": { "entityTypeID": "FeatureOfInterest", "id": "Airbag.Row1.DriverSide" },

17. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Defining an entity type Embedding "Entity": { "deprecation": { "type": "object", "$ref": "akm.Deprecation" } } "id": "Vehicle.Speed" , "deprecation": { "release": "2.1.2", "deprecationDate": "2024-03-01", "sunsetDate": null, "replacedBy": "VehicleTravel.Speed", "comment": "Distinguish Processes" } } "Deprecation": { "$id":"akm.Deprecation", "type": "object", "description": "An indication that the object is obsolete and best avoided", "properties": { "release": ..., "deprecationDate": ..., "sunsetDate": ..., "replacedBy": ..., "comment": ..., "required": [ "release" ] }

18. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Defining an entity type Constraints "required": [ "entityTypeID", "propertyID", "featureOfInterestID" ] "unevaluatedProperties": false },

19. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Self-documenting "DataProperty": { "$id":"akm.DataProperty", "type": "object", "description": "A property whose value is a literal", "allOf": [ { "$ref": "akm.Entity" }, { "$ref": "akm.extension.DataProperty" } ], "properties": { "entityTypeID": { "type": "string", "description": "A classfication of objects that share semantics, structure, and often behavior", "const": "DataProperty" }, "dataType": { "type": "string", "description": "The identifier of the data type that specifies what values and operations are available for the property" } # Automotive Knowledge Model An expressive and extensible semantics and standards-based vocabulary and data model for automobiles. Required properties are in ***bold italics***. version: 1.1 ## DataProperty A property whose value is a literal * ***id***: A data element that uniquely locates or identifies an individual thing * ***name***: A term that provides enough context for a human to identify the subject * ***definition***: A statement or formal explanation of the meaning of a concept * ***entityTypeID***: A classification of objects that share semantics, structure, and often behavior * ***dataTypeID***: The identifier of the data type that specifies what values and operations are available for the property * *format*: A mask, value constraint, or formatting hint for string values * *unitID*: The identifier of the unit of measure for values of this property * *min*: The minimum possible value available or permitted for the property * *max*: The maximum possible value available or permitted for the property

20. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Self-documenting

21. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Why JSON and not YAML? - id: Vehicle.Cabin.Seat.Airbag.Row1.Middle name: Airbag at Row 1 Middle entityTypeID: FeatureOfInterest definition: Airbag at Row 1 Middle isA: referentEntityID: FeatureOfInterest referentID: Vehicle.Cabin.Seat.Airbag partOf: referentEntityID: FeatureOfInterest referentID: Vehicle.Cabin.Seat.Row1.Middle { "id": "Vehicle.Cabin.Seat.Airbag.Row1.Middle", "name": "Airbag at Row 1 Middle", "entityTypeID": "FeatureOfInterest", "definition": "Airbag at Row 1 Middle", "isA": { "referentEntityID": "FeatureOfInterest", referentID": "Vehicle.Cabin.Seat.Airbag" }, "partOf": { "referentEntityID": "FeatureOfInterest", "referentID": "Vehicle.Cabin.Seat.Row1.Middle" } } versus https://aws.amazon.com/compare/the-difference-between-yaml-and-json/

22. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Data Types are from Standards Data Properties are constrained by a standard data type Data Types can express their own semantics A Metric can override the default Data Type { { "id": "Length", "name": "Length", "definition": "The linear extent or measurement of something from end to end, usually being the longest dimension or, for something fixed, the longest horizontal dimension", "dataType": { "referentEntityTypeID": "DataType", "referentID": "uint16" } "id": "uint16", "name": "uint16", "definition": "16-bit unsigned integer for range 0 to 65535", "entityTypeID": "DataType", "jsonDataType": "integer", "xsdDataType": "xsd:unsignedLong", "min": 0, "max": 65535 } "id": SeatCushion.Row1.Driver.Length ", "name": The seat cushion for the seat at row 1 driver", "definition": "The part of a seat that supports the buttocks and thighs of the occupant at row 1 driver", "entityTypeID": "Metric", unit": { "referentEntityTypeID": Unit", "referentID": "inch" }

23. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Units are from Standard Systems of Measurements Data Properties can have a default Unit The unit can be overridden for any metric { "id": "AmbientAirTemperature", "name": "Ambient Air Temperature", "definition": "The temperature of the air in a site or spatial region", "entityTypeID": "DataProperty", "dataType": { "referentEntityTypeID": "DataType", "referentID": "float" }, "defaultUnit": { "referentEntityTypeID": "Unit", "referentID": "degree_celsius" } } { "id": "degree_celsius", "name": "degree Celsius", "systemOfUnits": "International System of Units", "symbol": " C", "definition": "The unit of temperature on the Celsius scale", "quantityKind": "K" }

24. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Identifiers No Magic Numbers Vehicle.Cabin.Door.Row1.DriverSide.IsOpen.Boolean.Every10ms Vehicle.Cabin.Door.Row1.DriverSide.IsOpen c4870126-5d78-4084-a8cc-23da2b3d119c AKM00003501

25. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Identifiers Human Readable SELECT DISTINCT ?subject WHERE { ?subject rdf:type akm:07920a42-0d16 . ?subject akm:9d4623a3-2419 akm:59eaa048-0c36 . } c4870126-5d78-4084-a8cc-23da2b3d119c AKM00003501 FeatureOfInterest SELECT DISTINCT ?subject WHERE { ?subject rdf:type akm:FeatureOfInterest . ?subject akm:partOf akm:Cabin . } Cabin isAbout partOf

26. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Identifiers Consistent Format Vehicle.Cabin.HVAC.Station.Row1.Driver.Temperature Vehicle.Cabin.HVAC.IsFrontDefrosterActive USD US Dollar CAD - Canadian Dollar DJF - Djibouti Franc RWF Rawandan Franc IQD Iraqi Dinar Vehicle.Cabin.Infotainment.Media.Played.Source HVACStation.Row1.Driver.AmbientAirTemperature Defroster.Front.IsActive Infotainment.MediaSource

27. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Bidirectional Generation of Ontology { "id": "AirRecirculation", "name": "Air Recirculation", "definition": "A vehicle part that controls the system for recycling cabin air", "entityTypeID": "FeatureOfInterest", "partOf": { referentEntityTypeID": "FeatureOfInterest", "referentID": "HVAC" }, "isA": { "referentEntityTypeID": "FeatureOfInterestClass", "referentID": "ComfortComponent" } }

28. Requirements Standards-Based An expressive and extensible semantics and standards-based vocabulary and data model for automobiles Bidirectional Generation of Ontology { "id": "AirRecirculation", "name": "Air Recirculation", "definition": "A vehicle part that controls the system for recycling cabin air", "entityTypeID": "FeatureOfInterest", "partOf": { referentEntityTypeID": "FeatureOfInterest", "referentID": "HVAC" }, "isA": { "referentEntityTypeID": "FeatureOfInterestClass", referentID": "ComfortComponent" } } rdfs:label "Air Recirculation" skos:definition "A vehicle part that controls the system for recycling cabin air" akm:partOf akm:HVAC rdf:type akm:ComfortComponent

29. Questions Questions