A request must link room and asset while allowing a location issue when the equipment has not yet been identified.
Index
Naming only the building leaves technicians searching for the exact point; naming only equipment can lose room context.
The rule that changes the scope
A request must link room and asset while allowing a location issue when the equipment has not yet been identified.
Service software handles queues; a custom application adds location hierarchy and identification performed during the visit.
Hierarchical identification can start with the building and end at a room, but naming must reflect actual use. Local nicknames may aid search without replacing asset identity. Include equipment removed or moved to another room in the pilot: earlier requests remain available in their old context. Current location informs the next visit; it must not retrospectively rewrite where previous interventions actually took place or where the original issue was reported.
Specify operational deliverables
- Record building, room and affected point before requiring an asset code.
- Let the technician associate located equipment without erasing the original report.
- Keep location changes and earlier requests associated with the same asset.
Test the exception before acceptance
In a hypothetical scenario, a requester names the wrong room; correction must keep the original attempt and redirect service to the confirmed point.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a hard-to-locate request and the naming structure used for rooms and equipment.