Field Engineer App — Every job, route and test — in one field-hardened app.
The Field Engineer App is the phone-side of NOS. Assigned work orders appear the moment dispatch schedules them, GPS routing takes the technician to the door, on-site link testing writes results straight back to the subscriber NOS record, and photo evidence pins to the same graph everyone else on the operator team sees. It is offline-first, so it keeps working in the rural drop where the technician has no signal — jobs, forms and photos queue on the device and sync the moment the signal returns. Stock reconciles automatically to Netxol ERP as parts are fitted. The result: fewer wasted truck rolls, shorter time from install to first paid invoice, and a field team whose data does not evaporate at the end of the day.
- iOS
- Android
The field, without the paperwork.
Every truck roll becomes a data point. Every install becomes a customer record. Every part fitted reconciles to ERP.
Work orders and jobs
A live work-order board sorted by priority, SLA and route — no more paper stubs, no more WhatsApp job assignments, no more scribbled notes on the way to the next appointment. Dispatch schedules the job in Netxol; it appears on the technician device the moment it is assigned; and every subsequent event on that job (arrival, on-site tests, photos, sign-off) writes back to the same shared graph that CRM and Billing see. Care agents answering a subscriber call know exactly which technician is en route and when they will arrive, because the ticket, the job and the subscriber all live on the same record.
GIS-aware routing
Turn-by-turn GIS-aware navigation that already knows the operator poles, cabinets, splice points and drops — not just the street network from a public map. When a technician heads to a service call, the map shows the closest access chamber, the fibre route from the OLT to the customer premises, and any known plant issues (splice loss above threshold, degrading optical power on the adjacent drop) that might be relevant on arrival. Routing is aware of technician traffic so two vans do not end up on the same stretch of road when the dispatcher had one job for each.
On-site signal tests
On-site link tests — optical Tx/Rx power, RSSI, throughput against your own edge, TR-143 speed test via the CPE — captured and filed straight back into the subscriber NOS record. The technician never has to write results down and rekey them later. Baseline capture on install starts a per-subscriber optical history that becomes the leading indicator of splice degradation weeks or months later; see the study on optical power monitoring as a leading indicator at /blog/optical-power-leading-indicator.
Work orders and jobs
A live work-order board sorted by priority, SLA and route — no more paper stubs, no more WhatsApp job assignments, no more scribbled notes on the way to the next appointment. Dispatch schedules the job in Netxol; it appears on the technician device the moment it is assigned; and every subsequent event on that job (arrival, on-site tests, photos, sign-off) writes back to the same shared graph that CRM and Billing see. Care agents answering a subscriber call know exactly which technician is en route and when they will arrive, because the ticket, the job and the subscriber all live on the same record.
- Live job board sorted by priority and SLA
- Auto-attached to the subscriber NOS record
- GPS ETA visible to care agents
- Escalation on missed SLA
GIS-aware routing
Turn-by-turn GIS-aware navigation that already knows the operator poles, cabinets, splice points and drops — not just the street network from a public map. When a technician heads to a service call, the map shows the closest access chamber, the fibre route from the OLT to the customer premises, and any known plant issues (splice loss above threshold, degrading optical power on the adjacent drop) that might be relevant on arrival. Routing is aware of technician traffic so two vans do not end up on the same stretch of road when the dispatcher had one job for each.
- Poles, splices and drops on the map
- Route awareness across the whole field team
- Nearest access chamber highlighted
- Related plant issues surfaced on approach
On-site signal tests
On-site link tests — optical Tx/Rx power, RSSI, throughput against your own edge, TR-143 speed test via the CPE — captured and filed straight back into the subscriber NOS record. The technician never has to write results down and rekey them later. Baseline capture on install starts a per-subscriber optical history that becomes the leading indicator of splice degradation weeks or months later; see the study on optical power monitoring as a leading indicator at /blog/optical-power-leading-indicator.
- Optical Tx/Rx dBm captured to subscriber record
- Throughput test against operator edge
- TR-143 speed test via the CPE
- Baseline recorded for future drift detection
Everything the Field Engineer App carries.
A short reference of what a Standard-edition Core ships with. Advanced adds MDM-managed white-label bundles.
Photo evidence & sign-off
Photo evidence of the install (rack, splice tray, drop cable, ONT position) plus the customer signature captured at the doorstep — all pinned to the subscriber record before the technician drives away. This is the single most important operational discipline for reducing installation disputes: when a subscriber later claims their install was botched, the operator has photos with GPS coordinates and a signed acceptance from the day of installation. It also cuts field re-visits materially: technicians know their work is on the record, so quality on first visit improves.
Stock and reconciliation
Each technician van carries a live inventory that reconciles to Netxol ERP the moment a part is fitted at a customer site. No more month-end write-off scrambles because the paper stock sheet drifted from reality. No more mystery losses of ONTs that were signed out but not accounted for. Barcode/QR scan on install writes the specific ONT serial to the subscriber record, so the same unit reclaimed on churn goes back to the correct van inventory instead of vanishing.
Works offline
Offline-first is not optional for a Pakistani or MEA field team — rural drops, indoor blackspots, poor signal at basement service panels. The Field Engineer App is architected assuming no network. Jobs, forms and photos queue on the device and sync the moment signal returns. Conflicting edits are handled with a well-defined precedence (technician wins on job status; server wins on subscriber master), so the app never surprises the operator with lost work or overwritten records.
Where this app takes you.
Questions we get on the first call.
How do we distribute the Field Engineer App?
Signed APK for Android and IPA for iOS, distributed via your enterprise MDM (Intune, Workspace ONE, Jamf or Google Endpoint Management). We publish signed builds on every stable NOS release.
What happens if a technician loses signal mid-job?
The app is offline-first — jobs, forms and photos queue on the device and sync automatically the moment signal returns. Technicians never lose work.
Can technicians close jobs from the field?
Yes. Signal readings, install photos, customer signatures and stock consumption all land in the subscriber record before the tech drives away.
Does the app track the technician?
Only during active work hours and only with the technician's consent. Location scope, retention and visibility to managers are all configurable.
Put every technician on the same page.
Both apps ship with every Core. Download the installers today, or configure a Core with the white-label service included.