One field operation. Every site. Anywhere.

Five controlled stages, each with an owner, a timestamp and an exit condition. Intake and remote triage an engineer attempts remote resolution and confirms the fault, part and skill, so a truck rolls only when a visit is genuinely the answer. Dispatch and parts match the nearest qualified engineer is assigned against the site’s response tier and the spare released from a forward stocking location, consignment stock or regional hub, engineer and part planned as one movement. Onsite execution — access, security and site rules cleared in advance, a documented checklist per asset class, and live escalation to a senior specialist rather than a second visit. Evidence and closure — photos, serials, checklist results and sign-off attached before the ticket can close. Review and reduction monthly reporting on SLA, first-time fix, repeat-visit causes and cost per ticket, with a standing agenda item on which recurring faults should be engineered out rather than serviced forever.

Response tiers are set per site rather than per contract 4-hour critical, same-business-day, next-business-day and planned and priced against the criticality of that location. Metro and critical sites are covered by resident or retained engineers. For long-tail locations we operate a vetted partner and contractor network under the same onboarding, background-check and quality standards, managed through one dispatch desk so you are never chasing a subcontractor. Any genuine coverage gap is declared in the site matrix during the coverage review not discovered during an incident.

We work inside it by default. Our dispatch desk integrates with ServiceNow, Jira Service Management, Freshservice, Ivanti and similar platforms so tickets, status updates, attachments and closure evidence flow into your system of record — no parallel portal for your team to check and no manual re-keying at month end. Where a client has no field workflow of their own, we provide ours, configured to your escalation matrix and reporting formats.

Spares strategy is designed alongside the SLA, not bolted on afterwards. Depending on criticality we use forward stocking locations near the site, consignment stock held and managed by us, or just-in-time courier from a regional hub — with importer-of-record, customs documentation and duty handling managed by our procurement arm. Behind it sits a 45-warehouse network handling 48,000+ item movements a year. At the other end of the lifecycle, returns, RMA management, secure data wipe and certified disposal close the loop, with chain-of-custody evidence attached to the ticket.

All three, and most estates end up mixing them. Pay-per-incident suits low-volume and long-tail sites. Per-site retained coverage suits locations with predictable volume or strict response tiers. Full-time embedded engineers suit hub sites, campuses and data centres we run onsite teams from 14 to 480 engineers on that model. Most clients begin with a coverage review that maps every site to the cheapest model that still meets its SLA, which is usually where the first round of savings comes from, before any service improvement.