Field Ops
Track field technicians and vehicles live, approve fuel with fraud flagging, schedule maintenance and tie every truck roll back to the subscriber ticket that caused it.
Field teams — live
liveWhat Field Ops gives your ISP.
Most ISPs dispatch technicians by phone call and chat group. Field Ops puts the team, the vehicle and the subscriber ticket on one screen.
Live technician and vehicle map
Every technician and vehicle plotted live, with speed, heading and stop duration. Dispatch sees who is nearest to a fault, not who answered the phone.
Tickets tied to truck rolls
Each visit links to the subscriber ticket that caused it, so a repeat visit to the same address is visible and the cost of a fault is traceable.
Trips reconstructed automatically
Journeys, stops, idling and out-of-hours movement are built from the raw track, so a question about where a technician was takes seconds to answer.
Fuel approval with fraud flagging
Fuel claims are checked against tank capacity, distance travelled and the vehicle's own consumption history. Anything that cannot physically be true is flagged before it is paid.
Maintenance schedule
Service intervals by distance or date, defect reports from technicians, and workshop jobs tracked to completion, so vehicles are serviced before they fail.
Fleet costs
Fuel, parts, labour and downtime accumulate per vehicle, so the running cost of each van or motorbike is a figure you can defend.
Dispatch sees the field team, not a report about it.
The map is the working surface. Click a technician for the current ticket, the vehicle, the last fuel event and the next service. What dispatch needs to answer a subscriber is one click from the dot.
- Live positions, speed and heading for technicians and vehicles
- Geofences for depots, POPs and restricted areas
- Trip replay for any vehicle over any date range
Technician — TECH-A
liveThe fraud that hides in plain sight.
Most fuel loss is not dramatic. It is a claim larger than the tank, repeated quietly for a year. Field Ops checks every claim against physics and history before it reaches the approver.
- Tank capacity check — a claim larger than the tank cannot be right
- Consumption check — litres against distance actually travelled
- Pattern check — repeat anomalies grouped by vehicle, technician and site
Fuel approvals
What each vehicle costs, and when it needs the workshop.
Every fuel approval, workshop job and part is booked against the vehicle that consumed it. Run it per vehicle, per technician team or per depot, and the expensive ones stop hiding inside the average.
- Running cost calculated from real, approved spend
- Downtime tracked alongside direct cost
- Costs flow to the Back Office module when both run together
Maintenance schedule
Field teams on the map, on the same subscriber record.
The hardware conversation happens first, because that is what determines the timeline.
Survey
We confirm what is already fitted or carried. Existing trackers and technician phones are often usable, which removes cost and delay.
Connect
Devices are repointed to your instance, and each vehicle is matched to its record, technician and depot.
Configure
Geofences, service intervals, fuel tolerances and alert rules are set to your operation rather than to defaults.
Run
Dispatch, the workshop and the support desk are trained on their own views, then the first month runs with us watching alongside.
The details engineers ask about.
No asterisks. If something depends on your hardware, it says so.
- Live tracking
- Live positions on the map for technicians and vehicles, with speed, heading and stop duration.
- Telematics inputs
- GPS position and, where the hardware supports it, CAN bus data for odometer, fuel level and engine hours.
- Hardware
- Vendor-neutral. Existing tracker fleets can usually be repointed rather than replaced, confirmed during the survey.
- Ticket linkage
- Each truck roll links to the Support Desk subscriber ticket that caused it.
- Trips & history
- Automatic trip reconstruction with replay over any date range; retention period set by you.
- Fuel control
- Claims validated against tank capacity, odometer movement and per-vehicle consumption history, with approval workflow.
- Maintenance
- Service schedules by distance or date, technician defect reports, workshop job tracking and parts consumption.
- Alerts
- Speeding, geofence entry/exit, extended idling and out-of-hours movement, configurable per team and per vehicle class.
- Deployment
- Self-hosted or cloud. Runs on the SentraNet subscriber record, with REST API access.
Run your ISP on one platform.
We will walk SentraNet through your own network — your plans, your NAS estate, your OLT vendors — so you can judge it on the operation you actually run.