Nearest is not the same as allowed.
Routing finds the closest available technician. It cannot tell you whether that person may open the panel.
Proximity solves the easy half of the problem.
Any competent dispatch platform can find who is nearest and free. That part of field service is finished, and it was never where critical work went wrong.
What routing assumes away is everything that decides whether the visit is legal, safe and useful: whether this person is certified on this equipment, whether their site clearance is current, whether the manufacturer's warranty permits them to open the unit at all, and whether the approved procedure exists for the intervention they are being sent to perform.
Six constraints decide who can actually take the job.
Each of those lives in a different place today — a certification spreadsheet, an OEM portal, a badging system, an on-call roster, a procedure library. Nobody evaluates them together while the clock is running.
- Equipment expertise
- Certified on this class of plant — chiller, CDU, CRAH, controls — not on cooling in general.
- OEM authorisation
- Permitted by the manufacturer to open this unit without voiding the warranty.
- Site clearance
- Current badge, escort requirement and any two-person rule for the space.
- Shift and on-call
- Actually on rotation now, and not already committed to a higher-severity incident.
- Procedure
- The approved MOP, SOP or EOP for this intervention exists and the change window is open.
- Escalation path
- Who is named to approve, and who is called when the first responder cannot resolve it.
Three kinds of responder, and they do not share a system.
A critical cooling incident routinely involves two of these and sometimes all three. Pretending they can be managed inside one tenant is the assumption that makes generic platforms fail here — the coordination problem is between organisations, not inside one.
- In-house engineers
- On your systems, on your badge list, on your rota.
- OEM service
- On the manufacturer's dispatch, with entitlement rules you do not control.
- Mechanical contractors
- On their own field service platform, with their own certifications and their own queue.
The handoff carries the incident, not just the address.
Whoever goes should arrive knowing what was observed, what it was inferred to mean, what sits downstream, the asset's failure history, the approved procedure for this exact unit, and the parts most likely required — before leaving the van.
The reason is not convenience. A responder who does not know what the system already concluded cannot disagree with it, and disagreement from the person touching the equipment is the most valuable signal in the loop.
Execution and safety-critical approval stay with people.
The system proposes who is qualified and why, and records who it excluded and why. A human dispatches. A human performs the work. A named human signs for anything safety-critical, and that record is part of the incident.
How is this different from skills-based dispatch?
Skills-based dispatch matches a job type to a skill tag on a technician record, inside one organisation's platform. This evaluates live authorisation — current OEM entitlement, current site clearance, an open change window, an approved procedure for this specific unit — and it does so across in-house staff, OEM service and outside contractors who are not in the same system.
What if the qualified person is not the nearest?
Then the qualified person is the answer, and the drive time is a cost you were always going to pay. Sending someone who cannot legally open the equipment does not save time; it spends the response window and ends in a second dispatch.
Do you replace our field service platform?
No. The plant systems — BMS, BAS, DCIM, controls — stay exactly where they are and are only read. Where work execution already runs on a platform your team or your contractor uses, this coordinates against it rather than asking anyone to abandon it.