The Platform

Three products. One machine model.

PulseMQ runs from the edge device to the enterprise dashboard as one connected system. A single core that speaks to every controller, every business system, and every screen on the floor — the same equipment model, proved once at the Edge, shared by all three layers.

Book a Pilot Get the Sales Guide
Architecture

From the edge to the enterprise.

Data flows up the stack and understanding flows back down — every layer adding meaning while sharing the same live model of the machine.

Industrial Equipment
PLCs & Controllers
Layer 01 · Edge

PulseMQ-Edge™

Securely acquire & normalize industrial data.

EtherNet/IP OPC UA Modbus MQTT / Sparkplug B
Layer 02 · The Engineering Layer

AlarmIQ™

Understand & explain the machine.

AlarmIQ™ Machine Intelligence™ Replay™
Layer 03 · Manufacturing

PulseMQ Manufacturing™

Optimize production — OEE, MES, materials, maintenance.

OEE MES ISA-88 Traceability Scheduling
Dashboards Mobile · Reports · APIs

One equipment model runs through all three layers. Adding a machine at the Edge automatically flows up through AlarmIQ and Manufacturing — no re-integration between the layers.

Layer 01 · Edge

PulseMQ-Edge™

Standards-based control, on the box. Read-only by default. No new controllers, no cloud dependency for machine-level operation.

01

Counts the wear.

One appliance beside your line. Every controller feeds it read-only.

PulseMQ-Edge connects directly to your PLCs over open industrial protocols and runs full ISA-88 batch and ISA-106 continuous-process control right on the device — with live equipment state machines, interlocks and permissives, recipe dispatch, and audit logging built in.

Protocols: EtherNet/IP · OPC UA · Modbus · MQTT / Sparkplug B
Counts: Cycles, runtime, starts — per mechanism, on the box
ISA-88 batch: Live equipment state machine driven straight from PLC state
ISA-106 continuous: Startup, shutdown, grade-change with live interlocks

How connectivity works →

Read-only by default

Controllers feed the Edge read-only. Writes are the exception, gated per-role, per-tag, and logged.

One hub, every screen

Normalizes what it polls and publishes one clean stream to the broker, the apps, and the enterprise.

No new hardware

Runs on standard industrial PCs. Fits into your existing OT DMZ. No PLC changes required.

Layer 02 · The Engineering Layer

AlarmIQ™

Ask the machine. In plain English. Operators, maintenance, and engineers get straight, evidence-based answers grounded in live PLC state — not documents.

02

Understands your machine.

The layer that reads live PLC logic and turns it into plain-language answers.

AlarmIQ turns troubleshooting into an engineering conversation. Ask “Why won't Line 5 start?” and get an answer drawn from live logic, machine state, and alarm history — with the evidence chain attached to every claim.

Engineering Conversation™ plain-English chat grounded in live PLC state
Machine Intelligence™ learns normal cycle behavior, flags drift
Replay™ the seconds before every fault, evidence attached
Live viewers ladder logic, SFC, sequence diagrams, PID

See AlarmIQ →  ·  Read the Evidence Contract →

Evidence-first

Every value traces to a live PLC read. If a tag wasn't polled, PulseMQ won't invent one.

Anyone can ask

Plain-English questions. No tag names, no ladder logic knowledge, no training required.

It can act

Sixty-four registered tools, gated by role and domain, every session logged. Inside your permissions, not around them.

Layer 03 · Manufacturing

PulseMQ Manufacturing™

Live OEE, the moment it happens. Availability, performance, and quality derived continuously from live signals — not hand-keyed at the end of a shift.

03

Turns machine understanding into production performance.

Six areas of the operation, running on the same equipment model the Edge already proved.

Every KPI on this layer is derived from the same live signals that feed AlarmIQ. Downtime is ranked by cause. Work orders arrive as jobs the controller can see. Recipes become plans the equipment can run. Material lots stay attached to the runs that consumed them.

Production live OEE, counts, downtime ranked by cause
Maintenance counter-based queue with parts staged
Batches & recipes ISA-88 phases, versioning, control recipes
Materials lot traceability from raw material to shipment
Alarms impact-ranked, replayable, tied to root cause
Enterprise ERP sync, multi-plant rollup, ISA-95 models

Explore all modules →

Nothing re-keyed

OEE derives from live signals. Counts come from cycle events. Nobody types shift numbers at the end of the day.

Nothing re-integrated

The same equipment model that AlarmIQ reads is the one the Manufacturing layer runs on. One integration, three layers of value.

Six roles, one platform

Operators, maintenance, engineering, supervisors, plant managers, leadership — each sees the slice they act on.

One Machine Model

Proved once at the Edge. Shared by all three.

Most manufacturing stacks fail at the seams. You buy an OEE tool from vendor A, an alarm tool from vendor B, an MES from vendor C — and every one of them has to be integrated against your equipment separately. When you add a machine, you integrate it three times.

PulseMQ collapses that. Every controller you add at the Edge automatically appears in AlarmIQ (with its interlocks and permissives ready to trace) and in the Manufacturing layer (with its cycle counts and OEE inputs live).

Add once, appears everywhere

Configure a machine in the Edge. Its OEE inputs, alarm sources, and equipment model flow up automatically.

Update once, applies everywhere

Change a poll rate, a permissive definition, or a mechanism name — every layer sees the update in seconds.

No re-integration ever

No point-tool seam maintenance. No mapping spreadsheets. No “why is OEE off by 3% from the alarm tool?”

Open by Design

Built to fit your plant.

PulseMQ complements the automation you already run. Deploy on a single machine or a whole site, connect mixed-vendor equipment over open standards, and integrate with the systems of record you depend on — without ripping anything out.

Open standards

EtherNet/IP, OPC UA, Modbus, MQTT / Sparkplug B. Connect any modern controller.

Enterprise integration

Bi-directional ERP sync for SAP, Oracle, Epicor, NetSuite. ISA-88 and ISA-106 models supported natively.

Your deployment topology

Air-gapped, on-prem, hybrid, or cloud. Your network decides — not our architecture.

See the platform on a controller you already know.

Give us a program export from one of your lines. We'll come back with your machine answering questions about itself — and every layer of the platform working against your real data.

Book a Pilot Get the Sales Guide