The Hidden Cost of Disconnected Information
A regular scenario that I encounter: A question is asked about an asset, a customer, a site or an incident.
It sounds straightforward. But answering can require checking several systems, opening a collection of documents, searching through email/teams/slack and finding someone who understands how everything fits together.
Eventually, the answer may be found, but how much time did it take? How many people were involved? How confident are they that they found everything relevant?
How often is the process doomed to be repeated!? Every month or week?
Disconnected information rarely presents itself as one obvious problem. Instead, it appears as hundreds of small delays, repeated questions, duplicated effort and decisions made without the complete picture.
Over time, those small inefficiencies become a significant operational cost.
The information usually already exists
In many organisations, the problem is not a lack of information.
The information may already be stored in an asset management system, a spreadsheet, a PDF report, a maintenance record, a sensor platform, an email conversation or a project folder. Some of it may exist only in the memory of an experienced employee.
Each source may be useful and accurate on its own. The difficulty comes when someone needs to understand how those separate pieces of information relate to a real operational situation.
Consider a piece of equipment at an operational site.
Understanding its current condition might require access to:
its maintenance history;
recent sensor readings;
the latest inspection report;
manufacturer documentation;
previous incidents;
its physical location;
the team responsible for it;
and its next planned service date.
All of that information may exist, but not necessarily in one place or connected in a way that makes it easy to understand.
The information is technically available, yet operationally difficult to use.
The cost of searching and reconstructing context
When information is fragmented, people spend a surprising amount of time searching for it.
Finding the individual records is often only the first step. Someone must then reconstruct the context around them, asking questions such as:
Is this the correct asset?
Is this the latest version of the document?
Does this incident relate to the same equipment?
Has the issue already been resolved?
Who is responsible for the next action?
This reconstruction often depends on experience and local knowledge. A person who has worked in the organisation for years may know which system to check, which document can be trusted and who to contact for clarification. The problem is that this understanding is rarely captured.
The next person who asks the same question may have to repeat the entire process - in the worst case repeating work another person has already done to find the same answer.
Workarounds become part of the operation
When formal systems do not provide a complete view, teams naturally create their own ways of filling the gaps.
They build spreadsheets, maintain personal notes, create shared folders or keep informal lists of actions and responsibilities.
These workarounds are often practical and necessary. They help people get work done despite the limitations of the systems around them.
However, over time, they can also create another layer of fragmentation.
Different teams may maintain different versions of the same information. Important decisions may depend on a spreadsheet that only one person fully understands. Data may need to be copied manually between systems, introducing delay and the possibility of error.
What begins as a temporary solution can quietly become a critical part of the operation.
Decisions become slower or less informed
Disconnected information affects decision-making in two ways.
The first is delay.
Before making a decision, people may need to gather information from several sources, reconcile inconsistencies and wait for responses from colleagues. A question that should take minutes can take hours or days.
The second is incomplete understanding.
Under pressure, people often make decisions using the information that is easiest to access rather than the information that is most relevant. This does not mean they are careless. It means the cost of finding the complete picture is too high at the moment the decision needs to be made.
The result may be a delayed repair, an unnecessary site visit, a duplicated inspection or a missed opportunity to intervene before a problem becomes more serious.
The organisation becomes dependent on individuals
In many businesses, experienced employees act as the connection between disconnected systems.
They understand the history of a customer, the structure of a site, the quirks of a particular asset and the meaning behind incomplete records.
That knowledge is extremely valuable and is also a source of organisational risk.
When those individuals are unavailable, change roles or leave the organisation, the connections they carried with them may disappear. Documentation can record facts, but it does not always preserve the relationships between those facts. Knowing that an inspection happened is useful. Understanding which asset it concerned, what earlier issue triggered it, which document contains the findings and who is responsible for the follow-up is far more valuable.
Important signals can be missed
Operational issues rarely exist in complete isolation.
A maintenance problem may become significant because it is connected to repeated alarms, recent environmental conditions, a history of similar failures or an overdue inspection.
A compliance risk may only become visible when information from several departments is considered together.
A customer issue may involve service records, correspondence, equipment performance and previous commitments.
When information remains separated, these patterns are harder to recognise; Each individual system may show part of the situation without revealing the wider significance.
The risk is not simply that information cannot be found. It is that the organisation cannot easily see what the information means when considered as a whole.
Integration does not automatically create understanding
The usual response to fragmented information is to integrate systems or move data into a central repository. This can be valuable as it makes information easier to access and reduces some duplication.
Putting data into the same technical environment does not automatically connect it in a meaningful way.
The organisation still needs to understand:
what each record represents;
which asset, person, location or event it concerns;
how those things are related;
what has changed;
why the change matters;
and what action may be required.
A data warehouse may bring information together physically while leaving the user to reconstruct the operational context.
A dashboard may present several charts while still failing to explain how the underlying information relates to the real world.
The real objective is not simply to centralise information. It is to connect information around the people, assets, locations, events and processes that make up the operation.
What connected information looks like
When information is connected around real operational entities, people can investigate a situation more naturally.
They can begin with a site, an asset, a customer or an event and move through the information related to it.
They can see its relationships, history, documents, data, current status and responsible people without repeatedly searching across disconnected systems.
This does not necessarily mean replacing every existing application.
Specialist systems will always continue to perform important roles. Sensor platforms, document repositories, maintenance systems and business applications are designed to solve specific problems well.
The opportunity is to connect the information they hold so that the wider operational picture becomes easier to understand.
This was one of the ideas behind my creation of Ontaura: creating a connected operational context around real-world entities, while allowing information to remain in the systems best suited to manage it.
The value comes not only from having access to more data, but from understanding how that data relates.
The cumulative cost
The cost of disconnected information is rarely one dramatic failure.
It is the accumulation of small delays, duplicated work, repeated searches, incomplete decisions and missed connections across the organisation.
Because these costs are distributed across teams and everyday activities, they are difficult to measure. They often become accepted as a normal part of working.
So what solution do I suggest when asked about this? A useful starting point is to look at the questions people ask repeatedly.
Where do they go to find the answers?
How many systems must they check?
How much of the answer depends on one person’s knowledge?
How often does someone have to reconstruct context that the organisation has already encountered before?
These questions reveal where disconnected information is creating operational friction and where knowledge can be captured into a system.
Before investing in another dashboard, another reporting layer or another isolated application, organisations can first ask whether their information is connected well enough to answer the operational questions that matter.
