PLCs / RTUsSCADA / HMIIndustrial devices
OTDataMule L2
CollectBufferNormalizeForward
OTDataMule
Move industrial data across systems, protocols, and network levels.
OTDataMule is an industrial data movement and integration platform that collects, buffers, transforms, stores, and forwards production data. Deploy it at Level 2, Level 3, the DMZ, or IT to build controlled data pipelines without tightly coupling the systems on either side.
Protocol conversion
Store and forward
Multi-level pipelines
Historian and Portal
Level 2 source
OPC UA
Production tags and events
OTDataMule
CollectBufferTransformForward
Level 3 / IT
Deliver anywhere
DatabaseWeb APIMQTTHistorian
One pipeline across the industrial network.
Run an OTDataMule instance in each network zone that needs to collect, receive, process, or deliver data. Each stage has a clear responsibility, allowing the architecture to follow site segmentation and security policy.
OTDataMule L2
CollectBufferNormalizeForward
Controlled flow
OTDataMule L3
ReceiveValidateTransformRoute
Controlled flow
OTDataMule DMZ
ReceiveFilterBufferPublish
Approved delivery
DatabasesWeb APIsAnalytics / BICloud servicesPortal
OTDataMule supports controlled one-way or bidirectional data movement according to the deployment architecture. For hardware-enforced one-way transfer, it powers the Diodos industrial data diode.
From raw plant signals to usable operational information.
OTDataMule can be deployed as a focused protocol bridge or as a broader industrial data platform with persistent history and user-facing visualization.
01
Data Movement Engine
Connect to industrial and enterprise sources, organize independent data paths, buffer during destination interruptions, transform values and metadata, and forward each stream to one or many approved targets.
- Source and destination decoupling
- Protocol conversion and routing
- Reliable store-and-forward pipelines
- Per-path collection and delivery logic
02
Industrial Historian
Persist operational measurements in a time-series database designed for efficient history retrieval. Preserve the values needed for trends, investigations, performance analysis, exports, and long-term operational context.
- Time-series tag history
- Raw and aggregated intervals
- Fast trend queries
- History export for downstream analysis
03
Operations Portal
Turn stored data into accessible operational views. Build and share dashboards, browse tags through an asset hierarchy, compare trends, add annotations, and give authorized users a practical window into production information.
- Configurable dashboards
- Trend visualization and comparison
- Assets, tags, and annotations
- Role-based sharing and access
Monitor every stage of the data pipeline.
OTDataMule provides the operational signals needed to confirm that services are running, data is moving at the expected rate, and failures can be investigated before they become silent data gaps.
Pipeline monitoring
Live operational view
Keep detailed records of startup, connections, service changes, warnings, errors, retries, and delivery events so support teams can trace what happened and when.
Expose service and runtime metrics through the deployment’s observability configuration, including OpenTelemetry-compatible export where required.
Connect metrics and logs to the site’s monitoring stack so notifications can be generated for stopped services, lost connectivity, abnormal message rates, repeated errors, resource pressure, or other configured conditions.
Read here. Deliver there. Keep each system independent.
A data path defines where information comes from, what happens to it, and where it must go. Multiple paths can operate in parallel across a single OTDataMule deployment.
Collect and receive
Bring data into the pipeline from control systems, brokers, files, and databases.
Need a proprietary source? Project-specific collectors can be developed for vendor systems, specialist devices, custom APIs, file formats, or other approved interfaces.
OTDataMule
ValidateBufferTransformMapRoute
Store, publish, and deliver
Write data in the format and interface required by the receiving environment.
Need a specific output? Custom destinations can be implemented for internal applications, proprietary platforms, vendor endpoints, special payload schemas, or project-defined delivery workflows.
Start with one integration. Extend into a data backbone.
Use only the components required for the project today, then add network stages, destinations, history, and visualization as the operational need grows.
Protocol bridge
Read from OPC UA or another plant source and write to a database, MQTT broker, file, PI System, or Web API on the same or adjacent network level.
Multi-level pipeline
Place separate OTDataMule instances at Level 2, Level 3, and the DMZ so each zone receives and forwards only the flows assigned to it.
Historian and Portal
Store time-series measurements centrally, then give operations and engineering teams dashboards, trends, asset navigation, annotations, and exports.
Diodos data diode
Use OTDataMule on both sides of a Diodos appliance to collect and convert OT data across a hardware-enforced one-way optical boundary.
Hardware-enforced one-way deployment
Explore the Diodos data diode
OTDataMule powers Diodos.
Diodos combines two OTDataMule endpoints with a transmit-only optical connection. The software handles collection, conversion, buffering, and delivery; the hardware prevents a network return path into OT.
Built for real industrial data work.
OTDataMule focuses on the practical gap between connected devices and useful business information: moving the right data, in the right format, through the right network path.
Decouple OT and IT systems
Sources do not need to know how the final destination works, and destinations do not need direct access to the originating control system.
Protect continuity with buffering
Maintain a controlled handoff when downstream services are temporarily unavailable, then continue delivery when the destination returns.
Reuse data without duplicating integrations
Collect once and route the resulting stream to history, analytics, reporting, APIs, or additional systems according to the project design.
Operate with visible health
Use throughput metrics, service state, error counters, logs, and monitoring integrations to identify interruptions and investigate events across the pipeline.
Questions about OTDataMule.
Short answers for teams evaluating the platform as standalone middleware or as part of a segmented industrial architecture.
Can OTDataMule be purchased without Diodos?
Yes. OTDataMule is a standalone industrial data movement and integration platform. Diodos is one hardware-enforced deployment that uses OTDataMule on the OT and IT sides.
Can it run across several network levels?
Yes. Separate instances can be deployed at Level 2, Level 3, the industrial DMZ, or IT. Each instance can collect, receive, buffer, transform, and forward the data paths assigned to that network zone.
Does it include an industrial historian?
Yes. OTDataMule can store tag measurements in a time-series database and provide raw or aggregated history for trends, analysis, and export.
What does the Portal provide?
The Portal provides dashboards, trend visualization, asset and tag navigation, annotations, history exports, and controlled sharing for authorized users.
Is every deployment one-way?
No. OTDataMule can support controlled one-way or bidirectional flows according to the network design. When a physical one-way guarantee is required, OTDataMule is deployed with the Diodos data diode.
What monitoring and alerting information is available?
OTDataMule tracks service health, message throughput, processed and failed counts, data-path details, errors, host metrics, and logs. Metrics and logs can be exported to the observability and alerting tools selected for the site so teams can be notified about important operational events.
Can custom sources and destinations be added?
Yes. In addition to the available industrial, messaging, file, database, historian, and API connectors, project-specific source and destination modules can be developed for proprietary systems, vendor interfaces, custom formats, or specialized delivery requirements.
How should we evaluate it?
Start with a focused POC: identify one source, one or two destinations, the required tags and update rate, the network levels involved, and the business outcome the data must enable.
Plan an OTDataMule proof of concept.
Tell us where the data starts, where it must arrive, which network levels it must cross, and whether you need protocol conversion, buffering, history, dashboards, or a one-way Diodos architecture.
Email: info@diodos-tech.com
Company: DataDiode IKE, Athens, Greece