Manufacturing operations context for Tier-1 Supplier: Multi-Plant AAS Cell Twin PoC

Manufacturing · Digital Twin

Tier-1 Supplier: Multi-Plant AAS Cell Twin PoC

Simulated powertrain and packaging cells on one campus desk, swap connectors to real OPC-UA without changing asset IDs.

Plants on one desk
Siloed HMIs
2 simulated lines
Write path
Open loops
Signed operator actions only
Asset identity
CAD-only
Stable AAS IDs for swap

The Problem

Plant leadership invested in 3D visuals that operators ignored. They needed identity-stable assets, live protocol feeds, and signed writes, not another CAD spin.

The Solution

Xenith Twin shipped a Helios-style campus: catalog, two simulated cells, Twin API, JWT on writes, AAS inspector, and schematic process view. No closed-loop PLC write in PoC.

Twin vs 3D model

Operators needed live state and auditable writes, not photoreal CAD. See the blog on why identity-stable AAS beats decorative models.

What we would do differently

Model one cell end to end before touching the second plant. Templating across plants too early baked in one site's naming and cost a rework pass.

Business Impact

OT engineers validated desk UX before connector spend. Distinct from line-side QC vision case study, this is campus twin patterning.

Xenith Twin product

Tech Stack

Next.jsBaSyx-style AASKeycloak JWTMQTT/OPC-UA simTimescale history

Want a system like this?

Tell us the workflow. We reply with a short architecture brief: stack, gates, and timeline.