First machine connected in under 2 hours

OPC-UA and MQTT native

The Edge Gateway subscribes to OPC-UA nodes and MQTT topics. Configuration is done through the admin UI — no code required. A profile rule maps raw topics to Qontiv's data model (equipment, tag, value) using a pattern-matching syntax that handles ISA-95 Unified Namespace topics automatically.

Native protocol and vendor support

• OPC-UA — the industry baseline. Subscribe to nodes, browse address spaces, configure via the admin UI.
• MQTT Sparkplug B — Qontiv consumes Sparkplug B, so any Sparkplug-publishing gateway or broker works, Ignition included. There is no Qontiv module to install on the SCADA side.
• Rockwell FactoryTalk — a purpose-built connector for FactoryTalk Optix: assets and alarm/recipe definitions sync over its REST API, and Qontiv exposes a signature-verified webhook endpoint for change notifications.
• Atlas Copco smart tools — torque and angle results read from Power Focus controllers over Open Protocol (MID 0061), either by a direct TCP connection from the gateway or through a middleware bridge. Each rundown is resolved against the work-instruction step it belongs to, so a NOK result lands on the operation that produced it.
• ISA-95 Unified Namespace — MQTT topics published in a UNS layout auto-discover your site and equipment hierarchy. Qontiv consumes UNS-layout topics; it does not broker or publish the namespace.

Runs anywhere on your factory network

The gateway is a containerized Linux service. Run it on a Raspberry Pi, an industrial PC, or a VM — whatever's already on your OT network. Minimum specs: 512 MB RAM, 2 GB storage.

Outbound-only connection

The gateway initiates the connection to the Qontiv cloud; nothing connects inbound to your factory network. This pattern supports most OT security and network segmentation requirements without firewall exceptions.

ISA-95 Unified Namespace support

Factories already publishing MQTT in an ISA-95 UNS layout connect without per-tag mapping. Auto-discovery is opt-in; when it is enabled, Qontiv reads the enterprise, site, area, line, and cell segments out of the topic name and creates the matching site and equipment records for you. Sparkplug B topic layouts are recognized the same way. Qontiv is a consumer of your namespace, not a broker for it.

Automated capture from measurement gauges

Separately from machine connectivity, Qontiv reads measurement devices directly so operators stop typing gauge readings into a form. Five transports ship: OPC UA, MQTT, RS-232/RS-485 serial, USB-HID (for receivers such as Mitutoyo U-WAVE), and a watched file drop. File-drop parsing covers ASME QIF 3.0, Zeiss Calypso CSV, and Mitutoyo MCOSMOS XML, plus generic CSV.

This is measurement ingest, not machine-protocol extensibility — the instrument drivers produce SPC measurement records, and machine state, tag telemetry, and OEE come through the OPC-UA, MQTT, and Sparkplug B paths above. Equipment that speaks none of those needs a gateway or broker on your side that does.