Say It the Same Way Twice: Why a Maintenance Database Needs a Shared Vocabulary

A computerized maintenance management system, or CMMS, is the software a hospital's biomedical engineering department uses to track its equipment and its work orders: every repair, every scheduled check, every part swapped, logged as a ticket. It's the backbone of how a department proves what it did and when. But a CMMS has a quiet dependency that "Say It the Same Way Twice" turns into two minutes of chaos and one clear chorus: the system is only as useful as the discipline behind what gets typed into it.

The problem behind the song

The song's spoken intro lays out the exact failure mode: "Fixed. Repaired. Corrected. Resolved. Four words for one job, and none of them match." That's not an exaggeration for effect. HTM leaders and analysts have reported real difficulty spotting trends and systemic issues across their equipment fleets because there's no shared standard for how a completed job gets described in free-text notes. Four technicians can close four tickets for the same underlying failure using four different words, and a search built to find that failure pattern later will only catch the ones that happen to match its exact phrasing.

That's a bigger problem than it sounds. A maintenance database exists partly so a department can look backward and ask questions: is this model of pump failing more than others, is this failure mode showing up across multiple units, is a particular part wearing out faster than expected. None of those questions can be answered reliably if the underlying records don't use consistent language to describe the same kind of event.

Chaos in the verses, one rule in the chorus

The song's structure makes the argument almost literally: the verses are shrieked and disorienting, mirroring a database full of inconsistent free text that resists being searched. The chorus switches to one clear, sung voice -- the relief of a shared standard cutting through the noise.

Say it the same way twiceSo the system hears us rightSay it the same way twiceSo the pattern comes to light

The bridge makes clear who the standard is actually for. It isn't framed as a rule imposed to satisfy an auditor or pass a review. It's framed as a favor to the next person who has to read the record.

"We're not chasing perfect, just chasing clear," the bridge argues, before naming the audience directly: not for the auditor, not for the fear, but for the tech who reads this next year. That reframes data standardization from a compliance chore into something closer to leaving clean notes for a colleague -- who, in a maintenance database, is often a future version of the same department trying to understand its own equipment's history.