Fable
The clock tower that rings only once at night
The machine house in Salt Bay City had many bells. When the water pump slowed, one bell rang; when the furnace temperature rose, two bells rang; when the accounts system jammed, two and a half bells rang. In the early years there were few machines, and the night watchman would take his lantern and head over as soon as he heard the bells, usually arriving in time.
Later the city connected more pumps, ledgers, warehouses and automated delivery carts. The bell went from a reminder to a downpour, waking everyone in the middle of the night, yet no one knew which ring would truly bring the whole city to a halt.
The supervisor's first fix was to make the bell louder. Another person proposed different colored lights based on machine importance. Short term, the night watchmen did become more alert, but once exhausted, they began treating most bell rings as background noise.
On the worst night, the warehouse access control, order queue, and settlement system raised alarms one after another. Everyone split up to check their own machines, and no one realized all three anomalies came from the same network link jitter. By the time the root cause was found, customers had already received duplicate charge notices.
An old repairman did not wind the clock again. He laid out the past three months of bell strikes, machine metrics, maintenance records, shift changes and incident reviews on the table and reconnected them along a timeline. Many alarms that looked terrifying on their own were really just shadows of the same problem.
They added a night-watch book that could learn to the bell tower. It merged alarms from adjacent times, similar topologies, and shared impact surfaces, flagged anomalous patterns, and ranked the most likely sources first.
The new system did not make every decision for people. It simply suppressed the noise first, gathered relevant clues, and brought out the handling paths of similar past incidents, so the night watch could focus their energy on judgment and recovery.
A few weeks later, the total number of alarms in the city had not dropped much, but there were fewer bells that truly interrupted sleep. More importantly, incident meetings no longer began with 'who failed to see it,' but with 'what did the system see, and why did it judge wrong?' The supervisor finally admitted that operations was not about watching every machine more tightly, but about turning messy signals into an actionable chain of events. Later, when a new night watchman came on duty, the supervisor did not make him memorize all the bells. He first had the newcomer look at three old incidents: one was a false furnace-temperature alarm, one was a real water pump failure, and one was three warehouses slowing down at the same time. The newcomer gradually learned that a single bell only meant something somewhere was ringing, and that several bells connected by time and location might point to the real root cause. The value of the night watch log also showed itself along this thread.