RICHEMONT RFP DEMO · MACHINE SOFTWARE GATEWAY

Industrial Connectivity & Unified Namespace

Multi-Maison gateway demo · 3 Maisons · 6 cells · 1 UNS

EMQX Platform 6.2 EMQX Neuron · 6 instances Edge → UNS → Maintenance
Open Grafana Maintenance Alert Console

About this demo

This demo materialises the architecture proposed for Richemont's Machine Software Gateway: a centrally-brokered Unified Namespace fed by per-cell EMQX Neuron instances at each Maison's site.

Three Maisons — Cartier, IWC Schaffhausen, and Vacheron Constantin — each operate two simulated cells (machining + assembly). Six OPC-UA generators expose flat machine-local tags. Six Neuron instances (one per cell, each pre-seeded with its own configuration) bridge those tags onto the UNS topic <maison>/<site>/<line>/<device>/data.

Threshold breaches publish to …/anomaly. The Maintenance Alert Console subscribes group-wide and routes acknowledgements to notifications/maintenance. All telemetry, anomalies, and acks land in TimescaleDB and surface in Grafana.

EMQX Platform 6.2 EMQX Neuron (6×) OPC-UA MQTT · UNS TimescaleDB Grafana

Architecture

CARTIER La Chaux-de-Fonds IWC Schaffhausen VACHERON CONSTANTIN Plan-les-Ouates cnc-001 OPC-UA asm-001 OPC-UA Neuron cartier-machining Neuron cartier-assembly cnc-007 OPC-UA asm-007 OPC-UA Neuron iwc-machining Neuron iwc-assembly cnc-101 OPC-UA asm-101 OPC-UA Neuron vacheron-machining Neuron vacheron-assembly EMQX Platform · UNS broker Rule engine · Timescale bridge · ACL per Maison cartier/…/data iwc/…/data vacheron-constantin/…/data TimescaleDB telemetry · anomalies · acks Grafana cross-Maison dashboards Alert Console anomalies · acknowledge → maintenance Maintenance system notifications/maintenance

UNS Topic Hierarchy

  • <maison>/<site>/<line>/<device>/data
  • <maison>/<site>/<line>/<device>/anomaly
  • Wildcards: cartier/#, +/+/+/+/data
  • ACLs scope per Maison/site

Why Multiple Neurons

  • One per cell (machining / assembly) per Maison site
  • Failure isolation between cells
  • Each cell can speak its native protocol
  • Centrally configurable, locally resilient

Demo Flow

  • 1. All cells publish nominal telemetry
  • 2. Operator injects anomaly on a device
  • 3. Anomaly published on UNS
  • 4. Alert Console picks it up with full UNS context
  • 5. Operator acknowledges → maintenance dispatched