hopit hopit

Use Case

Machine Monitoring

OPC UA, Modbus, Siemens S7, TwinCAT and more — forwarded to a local Grafana dashboard, a time series database, or a cloud platform. hopit Edge connects to machines through their native interface, with no PLC changes and no six-month IT project.

Machine Monitoring

CNC-7 · live process data

Live

Spindle speed

3,000 RPM

847

Parts today

4.2 s

Cycle time

Running

Status

Status timeline · last 8h

Running Stopped Maintenance

The problem

Why machine data stays locked inside the machine

Most manufacturers know what data their machines could provide. The problem is getting to it without making connectivity a project in its own right.

01

Every machine speaks a different protocol

A 2012 Siemens CNC uses S7. The conveyor runs Modbus. The newer machining centre has OPC UA. Four machines, four protocols, four separate integration efforts. Most projects never start because the connection phase alone gets scoped as months of work.

02

Connectivity becomes a €100k IT project

The integrator quote arrives: €80k, five months, custom middleware for each machine. The budget doesn't get approved. The machines stay unmonitored. The digitization project sits on a slide deck for another year.

03

Your oldest machines stay invisible

Every digitization project covers the newest machines first. The 15-year-old lathe that runs 40% of your volume gets left out because nobody knows how to bridge a relay output to a modern data platform. Your most-used asset is your least-visible one.

How it works

hopit Edge reads your machines — and sends the data where you need it

hopit Edge connects to machines through their native protocol, reads process data in real time, and forwards it to your chosen destination — a local time series database, a Grafana dashboard, or a cloud platform. The connection work is the same regardless of destination.

Live process data from connected machines

Process variables, part counts, machine states — each machine reporting through its own protocol, all collected in one place.

Live process data

Live
Machine Protocol Variable Value Status
CNC-7 OPC UA Spindle RPM 3,012 ● Running
Press-3 Modbus Pressure 182 bar ● Running
Welder-1 S7 Temperature 847 °C ● Running
Conveyor-2 Digital I/O Running signal ● Stopped

Multiple protocols, simultaneously

One agent. All supported drivers running at the same time.

OPC UA Modbus TCP/RTU Siemens S7 Sinumerik TwinCAT ADS MQTT Digital I/O

Local monitoring with Grafana

Write to a local time series database on-premises. Visualize process data and machine timelines in Grafana — full control, no cloud dependency.

Furnace-1 · Temperature

847 °C

hopit Edge Time Series DB Grafana

Cloud forwarding on your terms

Configure which data goes where — hopit Manufacturing, Azure IoT Hub, or an MQTT broker. Nothing leaves the plant without explicit configuration.

See what machine data looks like once it's connected

Try the live demo — or download hopit Edge free and connect your first machine.

TRY OUR FREE DEMO Download hopit Edge

Features and what they change

Each capability removes a specific blocker

Zero protocol lock-in — OPC UA, Modbus TCP/RTU, Siemens S7, TwinCAT ADS, Sinumerik, MQTT and digital I/O relay outputs. hopit Edge runs all drivers simultaneously. Mixed machine parks connect through a single instance.

Zero PLC changes — hopit Edge reads passively through standard industrial protocols. No modifications to machine programs or configuration required. Your OT team stays in control of the machine layer.

Local monitoring with Grafana — data written to a local time series database and visualized in Grafana. Full data control, no internet dependency, no cloud cost. The setup that works in air-gapped environments.

Cloud forwarding on your terms — route machine data to hopit Manufacturing, Azure IoT Hub, or any MQTT broker. You configure what goes where — nothing leaves the plant without explicit setup.

Edge preprocessing — filter, aggregate and tag data before forwarding. Reduce bandwidth to the cloud target and keep raw high-frequency data local where it belongs.

Offline buffering — if the internet connection drops, hopit Edge continues collecting locally and forwards the buffered data once connectivity is restored. No data loss during outages.

Who it's for

Roles and industries

Roles

Plant Managers & Operations Directors — need machine data but can't wait for a six-month IT project to deliver it. hopit Edge is a connection, not a project.

OT/IT Integrators & Automation Engineers — need a gateway that handles mixed protocols without custom middleware for each machine. One agent, every driver.

Maintenance Engineers — need live process data — temperature, spindle load, vibration — to detect abnormal conditions before they cause unplanned stops.

Continuous Improvement & Lean Leads — need raw machine data as the foundation for OEE tracking and structured downtime analysis.

Industries

hopit Edge is used across a wide range of manufacturing sectors. Common industries:

Metalworking and precision machining
Plastics and injection moulding
Electronics and PCB assembly
Food and beverage processing
Packaging and converting
Automotive components and subassembly
Medical device manufacturing

Frequently Asked Questions

Yes — that's the scenario hopit Edge is designed for. One Edge instance runs multiple protocol drivers simultaneously: OPC UA for your new CNC, Modbus for the older sensor rail, S7 for the Siemens PLC. Each machine connects through its native interface.
No. hopit Edge reads machine data passively through standard industrial protocols. PLC programs stay untouched and no modifications to machine configuration are required.
Yes. hopit Edge can write directly to a local time series database. From there you can visualize in Grafana or any other tool. No internet connection is required for this setup.
hopit Edge supports MQTT forwarding, Azure IoT Hub, and direct connection to hopit Manufacturing. You configure which data goes where — nothing leaves the plant without explicit configuration.
Most first machines are connected within hours. hopit Edge has a configuration interface — not a development project. Once the driver is configured, data starts flowing immediately.
hopit Edge continues collecting and buffering data locally. Once connectivity is restored, it forwards the buffered data to the configured cloud target. No data is lost during outages.

Connect your first machine today.

hopit Edge is free to download and runs on your hardware. Or talk to us if you want help with the first connection.

Related use cases