Industrial AI
Production Pattern

Xenith Twin

Multi-plant cell twins operators can act on, fed by live OPC-UA and MQTT.

Xenith Twin is an Asset Administration Shell desk for discrete manufacturing: factory → line → cell with live protocol feeds, historian, alarms, and signed operator writes. Identity-stable assets, OPC-UA/MQTT ingestion, and auditable action loops. Demo plants ship simulated; production hardening swaps connectors without changing asset IDs.

PoC slice in weeks
PoC → pilot → plant rollout

Deployed as a scoped engagement for your stack - not a self-serve trial or live sandbox.

Xenith Twin: Multi-plant cell twins operators can act on, fed by live OPC-UA and MQTT.

Why teams look for this

Problems this pattern addresses

CAD sold as a twin

Operators ignore photoreal models that do not carry live state, alarms, or auditable actions.

Siloed HMIs per cell

Plant IT cannot compare OEE or protocol lag across lines with identity-stable asset IDs.

Open write loops

Unsigned setpoints and informal radio acks fail compliance review when AI enters the desk.

Where it sits in your stack

CNC / robot / MQTT
Historian / MES
Xenith Twin desk
Signed operator writes

How it works

Campus catalog

Factory → line → cell with BaSyx-style AAS shells.

Live protocols

OPC-UA and MQTT ingestion with twin-health lag metrics.

Action desk

Alarm ack and work orders with JWT on writes.

Connector swap

Keep asset IDs when moving from simulated cells to real PLCs.

Governed AI

Safety, audit, and rollout rules

Read the Governed AI doctrine for how Xenqube separates model output from money and safety actions.

Signed writes only

Operator actions are authenticated. Closed-loop PLC write-back is an explicit Assist-phase decision, not a PoC default.

What is not day one

IEC 62443 hardening, HA, and photoreal plant CAD are roadmap items, not claimed as shipped.

Proof and measurement

Workshop and shadow-trial metrics are labeled when synthetic. Live SLAs require a named pilot agreement.

MetricTarget / demoNotes
Simulated cells on one desk2+PoC campus pattern
Asset ID stabilityPreservedSwap connectors without renaming shells
Closed-loop PLC writeOut of PoCRoadmap after Assist design

Who this is for

OT / MES engineers
Cell leads
Plant IT
Continuous improvement

Use cases

Automotive tier-1 cells needing one desk across CNC and robot lines
Packaging lines where OT/MES data never matched operator reality
Plant IT evaluating multi-cell twins before PLC write-back
Programs migrating from CAD-only “twins” to live state

Rollout

Phased trust model

1. Simulate

Ship desk UX on synthetic cells with stable AAS IDs.

2. Connect

Swap OPC-UA/MQTT connectors to real equipment read paths.

3. Assist

Enable signed writes for approved action classes only.

4. Harden

IdP, HA, and security controls for multi-plant rollout.

What's included

Typical engagement deliverables

Scoped to your stack and compliance needs. We deploy the working system into your environment and hand over runbooks - not a sandbox login.

1

Two simulated manufacturing cells on shared campus pattern

2

Twin API and operator desk UI

3

Signed write path on approved actions only

4

Connector swap plan for your real PLCs

Questions buyers ask

Frequently asked questions

Is this a 3D digital twin?
No. It is an identity-stable AAS desk with live state. Pretty CAD without protocols is not the product.
Will it write to our PLCs in the PoC?
PoCs default to simulated or read-path. Signed writes are gated; closed-loop control is designed deliberately.

Want Xenith Twin in your environment?

Book a 30-minute call. We'll map your use case, confirm fit, and outline a deployment timeline - no self-serve trial, no pitch deck.

PoC slice in weeks from kickoff.