Guide 01

Which protocol does my plant use?

Select your PLC brand to identify your protocol and MOFF support status.

Siemens PLCs

S7-1200 and S7-1500 support native OPC-UA, fully supported by MOFF today. Older S7-300/400 is read directly over S7comm, supported today. PROFINET-only setups: bridge via OPC-UA.

OPC-UA: NOWS7comm: NOW

Allen-Bradley / Rockwell

ControlLogix and CompactLogix are read directly over EtherNet/IP (CIP), supported today. No gateway needed.

EtherNet/IP: NOW

Schneider Electric

Modicon M340/M580 supports both Modbus TCP and OPC-UA natively. Both fully supported by MOFF today.

OPC-UA: NOWModbus TCP: NOW

Beckhoff

TwinCAT 3 has excellent native OPC-UA support, fully supported today.

OPC-UA: NOW

Omron

NX/NJ series supports OPC-UA natively. FINS over Ethernet is on the roadmap.

OPC-UA: NOWFINS: Roadmap

ABB

AC500 PLC supports both Modbus TCP and OPC-UA. Both fully supported today.

OPC-UA: NOWModbus TCP: NOW

Danfoss / Festo

Older Danfoss drives use Modbus RTU or PROFIBUS. Modbus RTU/TCP is fully supported.

Modbus RTU/TCP: NOWPROFIBUS: Roadmap

Power / Grid / Substation

SCADA-RTU telemetry over IEC 60870-5-104 is supported today. IEC 61850 and DNP3 are on the roadmap; bridge those via OPC-UA gateway for now.

IEC 60870-5-104: NOWIEC 61850 / DNP3: Roadmap

Building Automation / HVAC

Building systems are read directly over BACnet/IP, supported today.

BACnet/IP: NOW

Unknown / Mixed

Most controllers built after 2015 support OPC-UA or Modbus TCP. Both fully supported today. Book a demo and we identify your stack together.

OPC-UA + Modbus TCP: NOW
Guide 02

NIS2 for OT in 5 minutes

NIS2 entered force in Denmark October 2024. Here is what it means for your plant.

1
Does NIS2 apply to you?
Energy, water, food, transport, and health entities with 50+ employees or €10M+ turnover. Most Danish water utilities are in scope.
2
What NIS2 requires from OT
Article 21: incident reporting within 24/72 hours and audit logging. You must prove who accessed control systems, what was changed, and when.
3
The forensics requirement
When the regulator investigates, you must answer: who changed setpoint X on PLC Y at time Z? The answer must be cryptographically verifiable. A mutable log file is not accepted.
4
24-hour warning, 72-hour full report
Without structured OT audit data, assembling a NIS2 incident report manually takes days, well beyond the deadline. MOFF assembles the signed evidence in seconds.
5
Penalties
Essential entities: up to €10M or 2% of global turnover. Management liability is personal. Directors can be held individually responsible.
YOUR PLCs → MOFF → YOUR IT SYSTEMS

The proof of what happened on the plant floor. Signed at the source.

Every reading is signed and chained before it leaves the floor. One layer. One contract. Same proof, all the way out.

PLC SOURCES DESTINATIONS MOFF sign · chain

Read-only. Never writes to your OT network. If a destination goes down, MOFF buffers locally and delivers automatically when it reconnects. ZERO LOSS.

The Problem

Sound familiar?

“Your operator still exports CSV manually every morning.”
Twelve PLCs, one USB stick, and an Excel sheet as your historian.
“Who changed that setpoint at 03:17?”
The SCADA log says nothing useful, and the authorities want an answer.
“4 vendors. 4 contracts. None of them talk to each other.”
An aggregator, a historian and an integration project. No shared audit trail.
MOFF solves all three. One layer. One contract.
Installed in hours, not quarters. No rip-and-replace, no PLC changes, no production risk to sign off.
What it changes

The case you take to your management.

The technical argument is the easy half. These are the four lines that decide whether a plant manager, a CFO or a compliance owner signs.

Audit prep stops being a project
Evidence for an inspection is assembled by hand today, by the people who can least afford the week. A signed chain turns that into one export.
Four supplier relationships become one
Aggregator, historian, integration project and the licences that follow. One layer, one contract, one renewal date to manage.
Nothing stops on the floor
Read-only, outside the control path, no PLC changes. There is no production risk to weigh against the business case.
Answers in minutes, not days
When management, an auditor or an authority asks what happened at 03:17, the record already exists and can be verified without you.
The full business case →
How It Works

Six steps.

01
Discover
Auto-detect PLCs and sensors. Config validated before the pipeline starts.
▶
02
Poll
Async parallel read of all tags. One device offline never blocks the rest.
▶
03
Process
Type-validate and normalize. Bad data blocked before it enters the chain.
▶
04
Validate
Every value checked against your alarm limits. Rules update without stopping the pipeline.
▶
05
Sign
Sealed the moment it is read, so any later change shows. Built on ECDSA-signed SHA-256 blocks.
▶
06
Deliver
Forward to all configured destinations simultaneously. Buffered locally, retried automatically on reconnect.
Platform

One layer. Everything it does.

Six protocols read live today. Every value signed at capture and chained. Four delivery paths out, trend history inside, and a one-click evidence bundle your auditor can verify without us.

See the platform →
NIS2

Built for NIS2 from the ground up.

NIS2 asks operators of essential services to prove what happened on their systems, and to report incidents on a deadline. Here is what MOFF gives you for that.

✓
Tamper-evident audit trail on every process value, signed and chained.
✓
Read-only connection to OT. MOFF never writes to your plant network.
✓
No cloud required. All data stays on your machine, on your network.
✓
One-click evidence export for the reporting deadlines: chain, config, CSV, verifier.
✓
Full chain of custody from PLC to IT system, verifiable independently.
✓
Runs alongside your existing SCADA. No rip-and-replace to become compliant.
Deployment

From install to audit-ready.

DAY0
Install
One Windows machine in your DMZ or server room. Read-only network access to your PLCs: no agents on controllers, no firmware changes, no SCADA downtime. Production never notices.
→
DAY1
Data flows, signed
The setup wizard discovers your PLCs and maps your tags. From the first poll, every value is ECDSA-signed into the audit chain and lands in your historian and IT systems. 10-second cycles.
→
DAY2
Everything flows
PLC to historian to IT: every value moving automatically, signed, around the clock. No operator touches a USB stick again. And when the auditor asks: one click exports the signed proof. MOFF runs silently in the background.
Deployed by your own team, by us, or by your integration partner. Days, not quarters. No rip-and-replace. No six-month integration project.

See it running on real data.

30 minutes on your protocols. Collected, signed, verified while you watch. No slides, no sales theatre.

We will be in touch within 24 hours.

Or answer six questions first and see the fit yourself: Plant Fit →

Not ready for a call? Download the 1-page overview (PDF) →