Appendix: Full Engineering Architecture Expanded
- Physical World and Data Sources
The twin mirrors reality. Data flows from OT systems (PLCs, SCADA/DCS, sensors, substations, robotics), IT systems (ERP, identity, SIEM, workflows), people and processes (roles, policies, controls), edge devices (drones, gateways, vehicles), and external signals (weather, markets, threat intel, regulations). We twin assets, systems, workflows, and the governing logic that binds them.
- Ingestion and Data Engineering
AI assists; humans define “good enough.” We ingest streaming and batch data safely.
Core functions:
- Schema normalization
- Quality and drift detection
- Time alignment of multi-rate streams
- Data minimization
Only data required for modeling, compliance, and decisions enters the twin.
- Storage and Database Layer
Specialized stores perform distinct roles, coordinated by the knowledge graph:
- Graph Database: relationships and dependencies
- Relational: configuration and transactions
- Time-series: telemetry
- Object/document: policies and designs
- Vector: semantic search
- Model/agent registries
The graph unifies them into a coherent system.
- Meta Grid Layer
Governance of meaning and metadata (semantic oversight, metadata oversight, and policy control): The Meta Grid governs metadata, policy, and lifecycle across the twin. It defines schemas, regulatory mappings (CMMC, NIST, IEC, HIPAA), sensitivity tiers, lineage, tag governance, versioning, and lifecycle rules. It is the compliance and semantic control ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access