The latch was fixed four times. The pattern was never seen.
Machine 90 became a lesson in what happens when every team has the information—but no one has the whole operating picture.
Story figures reflect the original Machine 90 account.
Something was wrong with the door latch.
An employee noticed a safety issue on Machine 90. Maintenance logged the work order, fixed the latch, and closed the request. The process worked exactly as designed.
A few weeks later, someone reported the same latch. Maintenance fixed it again. Then it happened again: same component, same machine, another complete repair record.
“Reported. Repaired. Closed. Repeated.”
Each record looked complete. Together, they told a different story.
First report
A safety concern becomes a maintenance work order. The latch is repaired.
Closed locallySame failure
A new request enters as a new job. The prior repair is not part of the working view.
Closed locallyPattern grows
HR, Safety, and Maintenance continue to record their own parts of the event.
Still fragmentedConnection appears
Four latch repairs are finally seen inside 12 maintenance requests.
Pattern visibleNobody failed.
Nobody hid information.
Nobody ignored a work order.
Nobody was negligent.
HR had the incident report. Maintenance had the work orders. Safety had the near-miss log. Each team was doing its job.
What the organization lacked was a view wide enough to connect the recurring latch failure to a pattern of risk before the cost compounded.
The information existed in three different operating worlds.
Nothing was missing. The connection was missing.
The fourth repair finally made the pattern expensive enough to notice.
This was not a maintenance problem. It was a visibility problem.
The information existed.
Every relevant point was captured somewhere: incident, work order, near miss, repair, cost, and downtime.
The systems did not connect.
Each function had a complete local record and no shared view across departmental boundaries.
The pattern repeated.
The issue became visible only after recurrence, expense, and downtime accumulated.
Most organizations do not have an information problem. They have a visibility problem.
The Machine 90 pattern appears wherever complex work crosses teams: injuries, claims, leave, accommodations, employee concerns, investigations, safety, and return to work.
Each department has records. Each system holds a piece. InfraNet is designed to keep the employee event, related work, owners, timing, and follow-up connected—so authorized people can see recurrence and context earlier.
Can this help the right person see the pattern before the fourth repair?
How many Machine 90 problems are invisible inside your organization right now?
Bring us one recurring issue, handoff, or employee event. We’ll map where the information lives and where the connection disappears.