PS-COO-183 · r2
COORDINATION
OBSERVED
ENGAGED
LINK LOST TO GEOMETRY
The status says disconnected; what the operator needs to know is which obstruction.
01 DEFINITION
Condition in which a connection fails for a geometric reason and its remedy is also geometric, while the display reporting the failure reports state rather than cause, so the operator is told that something is unreachable and not what would make it reachable.
02 CONDITIONS
UNCERTAINTY
MISSING
The reason for the loss is present in the world and absent from the display.
TIME PRESSURE
SHORT
The remedy is a movement, and movements take the time the loss was already costing.
ERROR ASYMMETRY
ASYMMETRIC
Moving the wrong element and moving nothing carry different costs, and both are available.
OPERATOR STATE
SUPERVISORY
The operator directs elements rather than being one of them, and cannot see what they can see.
03 WHERE IT APPEARS
TELECOMA node drops because of what stands between it and the next one, and the alarm names the node rather than the obstruction.
ENERGYRemote sites go unreachable for reasons of terrain and weather, and the operating picture shows only that they are unreachable.
LOGISTICSCoverage gaps along a route are a property of the route, and the dispatch view reports the gap rather than the geometry that makes it.
PUBLIC SERVICEField teams lose their link where the ground puts something in the way, and restoring it means moving someone rather than fixing something.
CONSTRUCTIONEquipment on a large site drops out behind structures that were not there last week.
DEFENSEElements are unreachable because of where they and the ground are, and reaching them again is a question of position.
04 WHAT AEON WORKED THROUGH HERE
Losses were not faults; they were consequences of where things had been put. A status colour told the operator that a link was gone and nothing about what to move, and moving the wrong element spent the time in which the loss mattered. The work went into what the map has to carry about why, rather than into how quickly it reports that.
The question it keeps returning to is how much of the reason a status view should carry — a display that explains every loss becomes a model to be maintained and doubted, and one that explains none leaves the operator moving things at random.