A rail operator had data. Plenty of it. The real problem was how long it took that data to reach the moment of decision.
In a large-scale rail operation handling roughly 3 million trips a day, trip data, field inspections, performance indicators and operational records were all kept in different systems.
Enterprise applications, databases, analytics platforms, reporting tools and mobile apps in the field were each doing their job. But the answers to the questions that mattered most to operations were not in one place:
The data was there. But pulling it together from different systems and making sense of it took time. So the challenge was not to create a new data source. It was to make existing data ready for decisions.
A shared data layer, without replacing any systems
The solution was not to rip out existing systems and rebuild. Enterprise applications, the SAP landscape with its dozens of modules, various databases, reporting tools and field apps all kept running.
Butterfly sat on top of these systems and brought data from different sources into a shared structure. Data spread across different systems came together in a single decision layer.
The idea behind this approach was simple: instead of replacing existing technology investments, connect the value those systems already create. As a result, the organization could access data from different systems through a single operational view.
The 27-page report is now ready every morning
For operations teams, the daily report is more than a document. It is the core source of information that shapes how the day begins. In this project, the 27-page daily operations report started being generated automatically every night.
Instead of spending the morning collecting data from different systems, merging files and preparing the report, the team can focus directly on the results. The process went from:
From 30 minutes to 3 seconds
Bringing data into a single structure changed more than reporting. It changed query speed too. Queries that used to take about 30 minutes now return results in about 3 seconds.
This difference goes beyond a technical performance metric. If getting an answer takes half an hour, the question often gets pushed aside in the flow of operations. If it can be answered in seconds, the same question becomes a natural part of daily decision-making. The shorter the time to data, the shorter the path to a decision.
100,000 rows of field data become performance indicators the same day
Rail operations generate field data nonstop. Station inspections alone add about 100,000 rows of data to the system every day. But simply recording raw data is not enough. The real value comes when that data turns into indicators that mean something for operations.
Field data can now be reflected in these indicators on the same day:
This shortens the time between something happening in the field and the result showing up on the management screen. The field → data → analysis → decision chain moves faster.
6,000 records synced in 5 seconds
One of the biggest obstacles to different systems working together is syncing data at the right time and in the right format. In this setup, 6,000 records can be synced in about 5 seconds. That keeps information from different sources up to date in the shared view operations rely on.
Instead of waiting on IT for reports, users build their own dashboards
Reporting is another area where access to data has been democratized. Operations teams can build the dashboards they need without writing code. They can also ask questions of the data in plain language to get the information they need.
That means no new report request or waiting on the technical team for every new question. IT’s role shifts from producing reports to providing the infrastructure that helps the organization use data more effectively. Operations teams, in turn, can put the information they need to work directly.
The real transformation is in decision speed, not data volume
Processing data from millions of trips certainly matters in this case. But the real issue is not the size of the data. Because in large organizations, the data is already there:
If an operations report is ready in the morning, the team can start the day making decisions instead of collecting data. If a 30-minute query returns in 3 seconds, questions that were put off can be asked again. If 100,000 rows of field data become performance indicators the same day, the gap between operations and management can shrink. And if different systems can talk to each other, a new decision layer can be built while protecting the technology investments the organization has made over the years.
Because digital transformation doesn’t always mean replacing systems. Sometimes the real transformation is making the data your existing systems already produce faster, more accessible and more meaningful.
Conclusion
In an operation handling 3 million trips a day, data is always flowing. What creates value is not the flow of data, but turning it into the right decision at the right time.
Butterfly brings different data sources together in a shared structure without replacing existing enterprise systems, helping organizations get results from operational data faster.
