Architecture
Six layers, one loop
Perceive the ore, pulp, froth and concentrate, plan the grind, float, separate and dewater, act inside limits, sense and predict grade and recovery continuously, optimise the whole plant, log everything, retrain. The layers below are the design, not a description of a shipped system.
Layer 01 · Connectors
Mill, flotation, analyzer, dewatering, robot and MES connectors
Mill control and APC, flotation APC and expert systems, froth cameras, online XRF and particle-size analyzers, reagent dosing, cyclones, thickeners and filters, DCS tags and historians, LIMS assays, sampling robots and the concentrator MES. Signals are normalised into one time-aligned circuit and lot record.
millapcxrfmes
Layer 02 · Plant-edge runtime
Perception and bounded control at the circuit
DeepStream and Holoscan process froth video, analyzer and sensor streams on Jetson Orin. TensorRT-optimised models read froth condition, grade and P80 and flag collapse, upsets and mineralogy shifts; time-series models predict recovery, grind response and equipment drift. Triton serves them with canary rollout by circuit, and the edge runs fail-safe through a network outage.
Jetson OrinHoloscanTensorRTTriton
Layer 03 · Orchestrator and agents
Plan, arbitrate, approve, act
The concentrator orchestrator assigns work to specialist agents. Agents retrieve reagent schemes, flowsheets and standards through permission-aware retrieval, evaluate action envelopes, ask for approval when required, and write through OT connectors only when interlocks, water and tailings constraints and the envelope allow.
plan.composepolicy.evaluateapproval.request
Layer 04 · Concentrator twin
Simulate before the shift
The Omniverse twin receives as-run telemetry, compares it with as-designed intent, and tests candidate grind, reagent and air schemes before the shift. GPU comminution and DEM, flotation and geometallurgy simulation; synthetic rare upsets from Cosmos and Replicator.
OmniversecuOptModulus (planned)
Layer 05 · Cloud training loop
Models, registry, reporting
Training on DGX or HGX, fleet model registry, versioning and enterprise reporting. Federated, IP-isolated aggregation across sites is planned and waits on customer data-rights agreements. Per-tenant isolation throughout.
NeMoDGX or HGX (planned)registry
Layer 06 · Review console and audit
Humans in the loop, by design
A review console for metallurgists to approve, correct and give feedback. Corrections train the models. An append-only, assurance-grade recovery and environmental audit log records every agent action from day one.
consoleaudit.writegenealogy