A fault report saying "the air quality is poor in our meeting room" contains almost no useful information for the person who has to act on it. Which room? Which building? Which ventilation system? Is this a recurring problem? Who is responsible?

That is not the fault of the person reporting. It is the fault of the system.

Property management is fundamentally location-based. Faults occur in a specific building, on a specific floor, in a specific room, at a specific installation. Yet most work orders are still handled as free text, and it is the receiver who has to manually interpret where, what and who.

Location data changes that. When a work order is linked to an exact location from the start, the receiver can more quickly see which room and floor it concerns, which ventilation system serves that space, whether it is the third fault report from the same room in the past month, and who is responsible according to the boundary schedule.

The work order moves from being a description of a problem to being a basis for a decision.

It does not have to be complicated for the person reporting. Alecta Fastigheter, working with Vyer, has built a flow at Nacka Strand where tenants can submit a fault report via QR code or web page, select the floor and mark the exact location on the floor plan. The work order then goes directly to operations staff with the location already linked. The person reporting does not need to understand the building's technical structure, but the receiver gets a completely different starting point.

Location is the foundational structure. But knowing where is not enough. The work order also needs to be linked to what the fault concerns, the installation, component or system, and what is already known from before. It is when location, asset and history are connected that a work order becomes actionable.

That combination is also what enables learning. Every closed work order linked to the right location and the right component enriches the history. Patterns become visible. Recurring faults are identified. The organisation stops starting from scratch every time the same unit fails.

The principle is simple: value before data volume, process before model. Start with the location link that actually affects a decision. Build from there.

Vyer has, together with Vasakronan, Jernhusen, Algorithma, Solrun and Epicenter, contributed to a report published by REDI on visual fault management and AI. Read the full report at redi.city/rapporter/visuell-felhantering-och-ai.

Nils Berglund, CEO at Vyer

Nils Berglund

CEO