Skip to content
Most industrial systems today claim they are “real-time” (that would be “near real-time” for the purists). Data updates instantly. Dashboards refresh continuously. On paper, everything is fast. So why does it still feel slow?
This isn’t about data availability. In most cases, the data is already there. The issue is everything that happens before that data becomes usable. The time it takes to prepare, align, and trust it is what creates the delay.
And that gap is what this article is about.
The Work Before the Work
Modern analytics tools are often judged by what they can do once the data is ready. Visualisation, calculations, dashboards, these are the visible parts.
But in practice, much of the effort sits just before that point. Industrial data is rarely clean or consistent. It comes from different systems, built at different times, with different assumptions. Signals don’t always line up. Data can arrive late or be corrected after the fact. Even something as simple as comparing two assets can require careful alignment.
None of this is unusual. It’s simply how these environments operate.
The question is how much of that complexity should be handled by the system, and how much is left to the user.
In one example we’ve seen, a sensor was reporting data in one time zone, but the team needed to analyse it in another. The data itself wasn’t wrong, but it wasn’t in the right context to be useful.
Before any analysis could happen, it had to be adjusted to match how the team actually worked. In this case, they were able to apply that shift directly within Ingenuity, aligning the data in real time without needing to export or rework it elsewhere.
When Preparation Becomes the Bottleneck
Over time, data preparation becomes a quiet constraint. Not because it is especially difficult, but because it is repeated. Each new question often requires the same groundwork. Connecting to sources, shaping the data, handling edge cases, making sure everything is usable.
As systems grow and more data becomes available, this effort tends to increase rather than decrease. Analysis still happens, but it takes longer to get there. Some questions are deprioritised because preparation work is put in the “too hard” pile. Others are simplified to fit within what is readily available.
In another very common case, a team was working with production data, oil rates, gas rates and other key metrics coming from an upstream system. On the surface, everything looked fine. But they regularly saw days where the values were clearly wrong, which threw off calculations like production efficiency and made the outputs hard to trust.
Their reference point became a sheet in Excel, where they had their own version of the “correct” data. But this didn’t match the source system, and in some cases older values would even override newer data.
Over time, they built logic into Excel to compensate, using well test data and formulas to override values rather than relying on the upstream system. What started as a workaround became the process: A convoluted process.
This kind of workaround is more common than most managers expect, and it highlights where time is really lost, not in analysis, but in getting data into a usable state.
The Gap Between Data and Decision
Many systems today are described as real-time, and technically, that is often true. Data is updated quickly, sometimes continuously.
But if that data still needs to be prepared before it can be used, then there is a wide gap between data availability and insights.
In day-to-day operations, that gap matters.
It affects how quickly teams can investigate issues, how confidently they can act, and how often they are willing to explore something new. Over time, it shapes behaviour. People adapt to the system, implement work arounds, rather than expecting the system to adapt to them.
A Subtle Shift in Expectations
What’s changing now is not the availability of data, but the expectation around how quickly it should become useful. There is less tolerance for delays between question and answer. Less appetite for workflows that depend on specialist knowledge or repeated setup.
There is a growing expectation that teams should be able to work with data as it is, not after it has been prepared.
This doesn’t remove the complexity of industrial data. But it does change where that complexity is handled.
From Preparation to Flow
The most effective environments treat data preparation as part of a continuous process rather than a separate step.
Data is integrated, shaped, and made usable as it arrives. Not perfectly, but consistently. Enough that engineers can start from a position of understanding, rather than setup. When that happens, something shifts. Analysis becomes more immediate. Questions can be explored in the moment. And “real-time” starts to reflect how people actually work, not just how quickly data updates.
This is where we see the difference most clearly in practice. The same issues still exist, late data, mismatches, and gaps but instead of forcing teams into workarounds, they can be handled directly within the workflow.
Situations like this are what led us to develop and expand the Data Editor within Ingenuity. Instead of pushing teams back into spreadsheets, it allows them to apply that same kind of operational logic, corrections, overrides, alignment to well tests directly to time-series data within the platform.
The difference is that it happens in place, with full traceability, and is immediately reflected across dashboards, analysis, and reporting.
The goal isn’t to remove complexity. It’s to stop that complexity from forcing teams out of the workflow every time something doesn’t quite line up.
From Preparation to Flow
Real-time data is no longer the challenge. Most systems already deliver it.
What still slows things down is the gap between data arriving and data being usable.
Closing that gap is where the real value sits, turning fast data into decisions that can keep pace with operations. Platforms like Ingenuity are evolving around this idea, bringing data integration, preparation, and real-time analytics together so that insight is available when it’s needed, not after the fact.
