Coordinating engineers across sites when the CAFM tool goes quiet

The work order sits in the CAFM system with a status, a priority, and an engineer's name against it. What it does not show is whether that engineer is actually in the building, which plant room they are standing in, or whether they have already fixed something similar two floors down twenty minutes ago. The helpdesk knows the job exists. Finding the person who can actually deal with it right now is a separate problem, usually solved by phoning around.

RevoNet does not replace your CAFM tool, and it is not trying to. Work orders, asset history, and SLA tracking stay exactly where they are. What changes is everything around the job: whether you know where your engineers are, whether you can reach them without a phone call, and whether reassigning a job takes a radio call or a tap on a map.

What a CAFM system does not tell you

Most CAFM platforms are built around the work order lifecycle, not live coordination. They are good at telling you what needs doing and when it was last done. They are not built to answer "who is closest right now" or "is anyone actually near plant room 3B this afternoon." That gap gets filled by phone calls, radio, or a WhatsApp group, none of which leave a record anyone can search later.

Engineers moving between plant rooms, roof spaces, and basement risers also fall out of normal mobile coverage more often than office-based staff. A missed call from the helpdesk becomes a missed job, and nobody finds out until someone chases it an hour later.

Voice and a map, running alongside your CAFM tool

RevoNet gives your team a talkgroup per site or contract, so engineers hear only what is relevant to the building they are in. A live map shows who is online and roughly where they were last seen, so a duty manager glancing at the dashboard before assigning a job has a genuine answer to "who is closest" rather than a guess based on who usually covers that floor.

None of this needs an integration with your existing CAFM system. The work order stays there. The coordination layer, voice, presence, and a lightweight incident record, sits next to it rather than trying to replace years of asset and SLA data with something new.

Creating an incident without duplicating the work order

When something needs a fast response, faults, call-outs, anything that cannot wait for the next CAFM sync, create an incident in RevoNet, assign it to whoever is actually nearest on the map, and let the talkgroup carry the voice detail that would otherwise be typed into a chat. Close it with a note once it is done. That record exists separately from your CAFM ticket, and the two are not meant to merge automatically. Think of the incident as the fast, informal layer for coordination in the moment, and the CAFM ticket as the formal record that survives it.

For contracts where a client wants evidence of response times, the incident timeline (creation, assignment, closure) gives you something concrete to point to without waiting on a full CAFM report to be pulled.

Setting it up per site or contract

Facilities teams tend to start with one site or one contract, not the whole portfolio. Set up a talkgroup for that site's engineers, run incidents alongside the CAFM tool for a few weeks, and see whether the duty manager actually reaches for the map before assigning a job. If it holds up, add the next site's talkgroup separately, so one building's chatter never bleeds into another's.

Multiple contracts under one management company can run as separate talkgroups within the same tenant, or as fully separate tenants where a client's own procurement requires it. Neither choice needs deciding on day one.

Common questions

Does RevoNet integrate with our CAFM system? No, and it is not designed to. Work orders and asset data stay in your CAFM tool. RevoNet adds voice, live position, and a lightweight incident record alongside it, not an API connection between the two.

Do we need a talkgroup per building or per contract? Whichever matches how your team actually splits up. A single-site contract usually needs one group. A multi-site contract often benefits from one talkgroup per site, so engineers only hear traffic relevant to where they are working.

Can a duty manager reassign a job from a tablet? Yes. The dashboard runs on desktop, laptop, or tablet, so a duty manager on a walk round can reassign a job without heading back to an office screen.

Is this only useful for large facilities teams? No. A two-person pilot, one supervisor and one engineer, on the free tier is enough to see whether voice and the map change how jobs actually get assigned, before you commit a wider contract to it.

Start with the free tier on one site, and read the device pairing guide if you are rolling out beyond phones your engineers already carry.