Most plants have data sitting inside machines, PLCs, sensors, and monitoring devices. The hard part is turning the data into something people can actually use - fast enough to prevent downtime, improve quality, and hit production goals. That’s the idea behind OMRON’s DX100 Data Flow Edge Device: a simple way to collect and visualize production-floor data, so teams can make decisions with confidence instead of guesses.
The Problem It Solves | Introducing OMRON's DX100 | Pre-Built Packages for Quick Start | DX100 Product Details | A Simple Way to Get Started | More Information About Omron's DX100
If you’ve ever dealt with unplanned downtime, you know the pattern:
Production sites often run into three big roadblocks when trying to use data:
Meanwhile, leadership still asks for improvements in OEE, quality, and energy/GHG performance—and they want progress now.
This works for a while. But it’s slow, it’s hard to keep consistent, and it usually can’t explain what happened right before the problem.
These can deliver results, but they often take time, planning, and budget. Many plants want a faster path to value—especially for a single line, a single machine, or a single problem.
Custom work can be powerful. But it can also turn into “only one person knows how it works,” which makes long-term support tough.
This is the biggest hammer—and not always needed. Many plants want to improve data use without changing devices or control programs just to get started.
The Omron DX100 is built to sit between your equipment and your decision-making tools. Think of it as a data hub that collects, organizes, and visualizes information from machines, sensors, and controllers in one place. Instead of building everything from scratch, users start with pre-built monitoring packages designed for real manufacturing problems.
This is where DX100 stands out. Instead of asking you to redesign your systems or start a long IT project, it focuses on practical ways to get value from the equipment you already have. These design choices are meant to lower the barrier to entry and help teams move from idea to insight faster.
1. Start with a simple retrofit approach
DX100 is designed to connect to existing equipment through Ethernet cables, without rewiring your machines. It also has two Ethernet ports—one commonly used for data collection and one commonly used for connecting a PC to view/configure through the web interface.
Key tools are browser-based, so you can view and configure without loading special software on a PC.
DX100 includes a flow editor where you create data processes by connecting building blocks—an approach that’s more approachable than starting from scratch in code.
And when you do need advanced work, it supports deeper customization (including options like Python and C) for special protocols or complex calculations.
DX100 can collect data from different devices in time-series format and view it alongside related video. That’s a big help when you’re trying to answer, “What changed right before the fault?”
It’s also built to work with a wide range of devices, including IP cameras, IO-Link devices, condition monitoring devices, and PLCs (including non‑OMRON PLCs—model support should be confirmed).
The DX100 includes ready-to-use software packages, which are pre-built templates designed around common manufacturing problems. Instead of starting from zero with unformatted data and an empty dashboard, these packages give you a practical starting point. Each package focuses on a specific operational goal, such as classifying downtime, trending throughput, and performing root cause analysis.
This package is designed to calculate and visualize 14 common factory KPIs for a piece of equipment.
The dashboard helps you track OEE, downtime, cycle time, production counts, and throughput so you can see where time is being lost and where to focus your time.
🌎Real-world use:
Your packaging machine “feels slower” this week. Instead of guessing, you can see whether the issue is more stops, longer cycles, fewer good parts, or a mix.
This package collects KPIs from multiple controllers and aggregates and visualizes them by factory, line, and process.
🌎Real-world use:
A supervisor wants to know which line is falling behind today—without walking the whole building. This gives a faster way to spot which area needs help.
Condition monitoring packages are built to collect and visualize data from monitoring devices, support threshold calculation, and enable alerts—so you can spot trends and act before a failure becomes downtime.
There are multiple condition monitoring options, including support for:
• Variable Speed motors
• Induction motors (current-based or vibration-based)
• Temperature inside control panel
🌎Real-world use:
A motor “sounds fine”… until it doesn’t. This helps maintenance teams move from calendar-based checks to condition-based timing, with trend data they can show and explain.
This package records and stores video from before and after an abnormal status signal is detected, so teams can review what happened without being physically at the machine right away.
It’s designed to speed up root-cause work and reduce recovery time—especially when issues are intermittent and hard to catch live.
🌎Real-world use:
A jam during changeover sporadically happens at 2 AM, and witnesses aren’t around. Now you can review the exact time window around the event and match it with signals from the PLC.
If you want a low-risk first step, there’s also a trial version option that helps teams try the approach before purchasing hardware (and reuse the flows later).
Stop Guessing & Start Making Decisions with the DX100
If you’re ready to stop guessing and start making decisions with real machine data, the DX100 is a practical place to begin. Start with one machine, prove the value, and scale to more lines when you’re ready.
Want help scoping a first use case? Our team can help you confirm connectivity, choose the right package, and plan a rollout that doesn't disrupt production.