Edge collection and contextualization (Industrial Edge)
Industrial Edge runs on-prem devices close to the shop floor and connects to vendor-agnostic automation equipment via OT connectors (OPC UA, Modbus, EtherNet/IP, etc.). It acquires raw telemetry, alarms and events.
At the edge, data is pre-processed: filtering, compression, timestamp normalization, enrichment with asset metadata (asset hierarchies, work order / batch context), and local aggregation to reduce cloud bandwidth.
An internal databus (MQTT / Unified Namespace) or Industrial Information Hub propagates harmonized topic streams for downstream components and local consumers.
Protocol and format bridging
FFT DataBridge (Edge App) prepares and enriches data for streaming and near–real-time ingestion into Databricks. Its free companion app, FFT DataService, accesses contextualized data from Industrial Information Hub Essentials (Edge App) and makes it available to FFT DataBridge, which then publishes aligned, contextualized data streams via Zerobus, enabling continuous delivery directly into Unity Catalog–governed tables.
To ensure robustness, the solution uses in-memory buffering and local persistence to bridge connectivity interruptions and extended outages. On the Databricks side, data is ingested incrementally into Delta tables under Unity Catalog, enabling governed, low-latency access for downstream analytics and AI workloads. Secure connectivity is maintained through token-based or key-based authentication mechanisms.
Databricks data intelligence platform
Streaming ingestion via Zerobus continuously delivers data into Databricks, where incoming OT payloads are written into Bronze Delta tables governed by Unity Catalog, preserving raw structure and metadata for full traceability and auditability.
Transformation pipelines built with Lakeflow Declarative Pipelines, Databricks Workflows, and Apache Spark progressively refine the data into Silver (curated) and Gold (analytical) layers, supporting time alignment, contextual enrichment, and readiness for BI consumption as well as AI-driven use cases.
AI models are developed and trained centrally in Databricks using MLflow and Mosaic AI, and can then be deployed back to Siemens Industrial Edge for low-latency execution close to the shop floor—enabling closed-loop optimization and physical AI scenarios.
Unity Catalog enforces end-to-end governance, including fine-grained access control, data masking, and lineage tracking, while the Lakehouse Platform runs natively across AWS, Microsoft Azure, and Google Cloud Platform, supporting cross-cloud deployment and seamless data mobility.