DataLink digital-twin data layer (preview)

Dawn Engine DataLink is a planned first-class orchestration Gem family (first-release entry Gems/DataLink, with planned VideoFusion and DataViz tracks). It binds MQTT / OPC UA / Kafka / WebSocket telemetry and surveillance video into one query-and-binding model over 3D scene entities, and exposes heatmaps, flow fields, geofences, and POI labels as visualization outputs.

Maturity: planned / product preview. This page describes target capabilities and rollout stages—not available product APIs. Enabling any future Registry gate must leave existing World Streaming, Cesium, Dawn Stream, and Script Canvas paths unchanged when DataLink is off.

It does not replace a business middleware or SCADA stack: DataLink consumes normalized telemetry and video streams; device-protocol adapters, auth gateways, and historians stay at the project or external-service layer.

What problem it solves

Digital-twin projects often split “ingest → bind entities → visualize → demo” across fragile glue code, stretching PoC timelines. DataLink is intended to provide:

  • A unified real-time data bus and property binding (entity / component fields / material parameters / Script Canvas variables);
  • Protocol adapters (MQTT, OPC UA, Kafka, WebSocket) enabled on demand via Registry;
  • Surveillance video (RTSP / GB28181) projected onto 3D surfaces, with camera calibration and multi-stream management;
  • 3D visualization primitives: heatmaps, flow arrows, geofences, POI labels, and lightweight chart panels;
  • Coordination with double-precision large worlds, Cesium, and Dawn Stream—so bound scenes can also be viewed in the browser.

Planned capabilities

Ingest and binding (DL0–DL4)

MilestoneFocus
DL0Gem scaffold, Registry opt-in (default off), binding model, headless unit tests
DL1MQTT / WebSocket adapters, property binding, Script Canvas / Lua query nodes
DL2OPC UA / Kafka adapters, reconnect / back-pressure policy, sample Prefabs
DL3Spatial-index binding with World Streaming cells / Cesium Globe Anchors
DL4Server-authoritative relay mode, quality tiers, performance gates, shipping docs

Video fusion track (VF1–VF3)

Depends on the ingest bus’s entity and calibration pipeline; does not replace it:

TrackFocus
VF1RTSP pull, decode, planar / curved projection, single-stream calibration editor
VF2GB28181 integration, multi-stream management, occlusion and LOD policy
VF3Remote viewing path with Dawn Stream; multi-channel projection on cluster displays

Visualization track (DV1–DV3)

TrackFocus
DV1POI labels, geofences, basic numeric panels
DV2Heatmaps / flow arrows with binding-driven color maps
DV3Timeline playback hooks; optional bridge to a record/replay system

Point clouds (LAS / LAZ / E57) and BIM / CAD (IFC and similar) import are later candidate tracks, outside DataLink’s first-release scope. The design reserves the same spatial index and double-precision query interfaces.

How it will work

MQTT / OPC UA / Kafka / WebSocket / RTSP
DataLink Core (normalized telemetry + binding graph)
 ├─ BindingBus ──► entity properties / materials / Script Canvas
 ├─ VideoFusion ──► decode → projection mesh / Overlay
 ├─ DataViz ──► heatmaps / fences / POI / panels
 └─ StreamBridge (optional) ──► Dawn Stream browser sessions

Design rules in the specs:

  1. Orchestrate, do not reinvent: no second renderer; visualization uses existing Atom / LyShine / Overlay paths.
  2. Double-precision spatial queries: bindings and fences use AZ::Vector3d / AabbD; GPU quantities stay render-origin-relative.
  3. Default off: projects that never enable DataLink pay zero runtime cost (Registry / subsystem gating).
  4. Projects own protocol truth: the engine ships adapter contracts and samples—not a bundled vendor cloud.

Explicitly out of scope for v1

Not in v1Notes
Full SCADA / MES replacementReal-time binding and visualization orchestration only
Historical time-series databaseHooks only; storage is project-layer
Lossless import of arbitrary CAD formatsBIM / CAD is a later candidate
Full productization of massive point cloudsPoint cloud is a later candidate track
Out-of-the-box on-device AI recognitionVideo may feed external inference; no built-in model training
TopicRelationship
Double-precision renderingLarge-world precision for fences, POI, and projection anchors
World StreamingBound objects load/unload with cells
Cesium 3D TilesGeospatial anchors and global basemap context
Dawn StreamBrowser viewing of bound twin scenes
ClusterDisplayVenue / CAVE multi-channel presentation
SensorSim (planned)Simulated telemetry can write into the same binding model

Status and next steps

This chapter is a product preview. When DataLink ships, the guide will grow Quick start, Registry keys, protocol adapter samples, and Script Canvas node notes—consistent with chapters such as PolyTerrain and Dawn Stream.


Copyright © 2026 DawnEngine. All rights reserved.

DawnEngine is a commercial 3D engine distributed under the DawnEngine end-user license agreement. Engine binaries and source are proprietary and are not covered by the licenses below.

Documentation only: the prose and templates on this site are a derivative work of Open 3D Engine (O3DE) documentation by the O3DE Contributors, used under CC BY 4.0 (documentation content), Apache 2.0 (site code), and the MIT license (inline code samples).

The open-source 3D engine that DawnEngine is built on top of is Open 3D Engine . DawnEngine is not affiliated with, endorsed by, or sponsored by The Linux Foundation or the O3DE project. “O3DE” and “Open 3D Engine” are trademarks of The Linux Foundation.