Data onboarding
Static data is data known at the creation time of a battery that does not change across its lifecycle.
Onboarding of this static data is performed by providing JSON files for the Aspects in the Semantic Data Lakehouse of Bosch Semantic Stack. Data pipelines will then transfer this data and automatically register a digital twin (Asset Administration Shell) for a new battery.
Data ingestion approach
The static data to be ingested into the Battery Passport application is expected in multiple JSON files, separated for each Aspect Model.
Each customer needs to provide a folder for each battery identifier. The folder holds a simple list of the Aspect data as a JSON file.
Example structure for future data ingestion
Landing zone static data/
├─ Tenant one (= customer A)/
├─ Tenant two (= customer B)/
│ ├─ Battery identifier one/
│ │ ├─ BatteryInformation.json
│ │ ├─ BatteryInformationPublic.json
│ │ ├─ CarbonFootprintsPublic.json
│ │ ├─ CircularityAndResourceEfficiency.json
│ │ ├─ CircularityAndResourceEfficiencyPublic.json
│ │ ├─ ComplianceLabelsAndCertifications.json
│ │ ├─ ComplianceLabelsAndCertificationsPublic.json
│ │ ├─ MaterialsComposition.json
│ │ ├─ MaterialsCompositionPublic.json
│ │ ├─ PerformanceAndDurabilityEV.json
│ │ ├─ PerformanceAndDurabilityPublicEV.json
│ │ ├─ SupplyChainDueDiligencePublic.json
│ ├─ Battery identifier two/
│ │ ├─ the exactly same files as listed above are expected for each battery,
│ │ ├─ but for of Performance and Durability - ONE of the variants:
│ │ ├─ Performance and Durability EV Aspect
│ │ ├─ Performance and Durability LMT Aspect
│ │ ├─ Performance and Durability Stationary Aspect
│ │ ├─ Performance and Durability Industrial Aspect
├─ Tenant n (= customer X)/
Aspect Model API documentation
Refer to the predefined structure and data types outlined in the Aspect Model documentation to ensure all data is supplied in the exact specified format.
Consulting
For any questions regarding data onboarding for your tenant, please contact our consulting team.