Connections

What MOFF reads from, and what reads from MOFF.

MOFF speaks the protocols your plant already runs, and delivers over open interfaces anything upstream can read. No vendor connector to wait for, and nothing to install on the controllers.

Sources MOFF reads from

PLCs and controllers

Siemens S7-1500Siemens S7-1200Siemens S7-300Siemens S7-400Rockwell ControlLogixRockwell CompactLogixRockwell Micro800Beckhoff TwinCATSchneider Modicon M580Schneider Modicon M340WAGOPhoenix Contact PLCnextB&ROmron

SCADA and HMI

Siemens WinCCIGSSGE/Emerson iFIXIgnitionCOPA-DATA zenonAVEVA System PlatformAVEVA InTouchACOWA

Building, HVAC and cleanroom

Siemens Desigo CCSchneider EcoStruxure BuildingJohnson Controls MetasysHoneywellTrend

Utilities, RTU and field devices

ABB RTU5xxSiemens SicamSchneider SaitelKamstrupGrundfosDanfoss VLTABB ACSMettler-ToledoVaisala viewLinc

Destinations MOFF delivers to

Once a value is signed, any system that speaks REST, MQTT or a supported database can consume it.

Production apps

Pulls signed data from MOFF over REST.

Tulip

Any MES or MOM platform that can call an HTTP endpoint reads the same signed data over the pull API. Tulip is named as the example because it is the one we are asked about most; we have not run a joint deployment with any of them yet.

IT, BI and data

Pulls signed data from MOFF over REST.

Microsoft Power BISAPMicrosoft ExcelMicrosoft FabricSnowflakeDatabricksNode-REDGrafana

IIoT and Unified Namespace

Receives MOFF’s signed data over MQTT / Sparkplug B.

Ignition (Sparkplug B)HighByteHiveMQEMQXMosquittoN3uronLitmus Edge

Historian and SOC

MOFF delivers directly.

InfluxDBGrafanaSplunkMicrosoft SentinelWazuh

All product names are trademarks of their respective owners. Listed for compatibility reference only: no affiliation, partnership or endorsement is implied.