Field engineer servicing GPS and fuel sensor hardware on a construction vehicle
Field-verified repair & AMC

Repair & Maintenance That Keeps Every Sensor Reporting

Aether's Annual Maintenance Contract keeps GPS trackers, fuel sensors, and energy meters accurate across their full lifecycle. The same field team that installed your hardware handles preventive checks, recalibration, and fault resolution — every visit closed out with photo and live portal evidence, not a verbal assurance.

13,000+ Field service tickets logged and resolved to date
25+ Fault categories tracked, from wire tampering to sensor faults
14 Defined repair actions — nothing closed out as guesswork
100% Repairs cross-checked on the live Aether portal before closure

Why it matters

A damaged or tampered sensor is a data blind spot

Wiring tampering, hardware damage, GSM dropouts, and sensor drift don't just break a device — they break the fleet, fuel, and safety data your team relies on to make decisions. Aether's Repair & Maintenance service treats every fault as a tracked ticket: classified, diagnosed on-site, repaired, and verified against the portal before it's marked closed.

6 groups
of faults tracked separately — tampering, connectivity, hardware, data quality, lifecycle changes, and deinstallation.
Warranty-aware
every ticket records whether the fault leaves hardware warranty intact or void.
Photo-verified
device, wiring, and configuration evidence captured on every field visit.
Portal cross-check
the live Aether dashboard is reviewed on-site before a ticket is marked resolved.

What we handle

Every fault is classified before it's fixed

Aether's field team tracks more than 25 distinct fault types across six groups, so nothing gets resolved as a vague "device issue" — and every repair is billed, warrantied, and reported against a specific, known cause.

Wiring & Tampering

Manual wire tampering, hardware damage, operational wiring faults, and meter/odometer tampering — the leading cause of lost reporting on live sites.

Connectivity & GSM

GSM dropouts, gateway/GSM modem faults, and server-side configuration issues that stop data from reaching the portal at all.

Device & Sensor Malfunction

Technical and operational hardware malfunctions and configuration faults on the GPS unit, fuel sensor, or energy meter itself.

Data Quality Flags

GPS, engine, and fuel data quality issues caught before they distort fleet, safety, or fuel reporting downstream.

Asset Lifecycle Changes

Assets dehired, replaced, idled, or moved without proper hardware removal — plus asset code updates and missing-device checks.

Deinstallation & Relocation

Clean removal of GPS units and fuel level sensors (LLS) when an asset is decommissioned, sold, or reassigned.

AMC coverage

What your Annual Maintenance Contract covers

Preventive care and rapid fault resolution, delivered by the same team that installed your hardware.

Hardware Inspection

Physical device check, wiring integrity, and mounting stability verified on every scheduled visit.

  • Full wiring and connector inspection
  • Mounting and enclosure stability check

Fuel Sensor Recalibration

LLS sensor re-profiled against current tank geometry to maintain reading accuracy over time.

  • Tank-geometry re-profiling
  • Blind-area and threshold re-verification

Connectivity & Portal Health

SIM status, data upload frequency, and portal event accuracy reviewed on every maintenance cycle.

  • SIM and network signal check
  • Upload frequency and portal event review

Priority Fault Resolution

AMC clients get priority scheduling for on-site fault resolution — minimising data loss windows.

  • Priority ticket scheduling
  • Same field team that handled installation

End-to-end process

How a repair ticket gets closed

From a flagged fault to a verified fix — six steps every field engineer follows on every visit.

Issue Detected & Logged

A fault is flagged — through a portal alert, a client report, or a routine health check — and logged as a ticket with a specific fault category, site, and asset code.

Ticket opened with site, asset code, and fault category
Classified into one of 25+ defined fault types before dispatch

Site Visit & Diagnosis

A field engineer inspects the hardware on-site — wiring, mounting, and connections — and runs device-level diagnostics through the manufacturer's configurator tool.

Physical inspection of wiring, mounting, and connectors
Device configurator readout: signal, battery, GSM, GNSS status

Evidence Capture

Before any repair, the engineer photographs the fault, captures the device configuration screen, and pulls the current portal graph to document the "before" state.

Photos of the fault, wiring, and affected hardware
"Before" portal graph and device configuration screenshot

Repair Action

One of 14 defined repair actions is carried out on-site — from a simple reconnection to a full hardware, sensor, cable, SIM, or firmware replacement.

Reconnection, reconfiguration, or firmware update
Hardware, LLS sensor, cable, or SIM replacement where needed

Verification & Warranty Review

The repaired asset is checked live on the Aether portal before the engineer leaves site. The ticket is tagged with the warranty impact — intact or void — depending on the root cause.

Live portal check confirms the asset is reporting correctly
Warranty status recorded: intact for defects, void for tampering/damage

Closure & Reporting

The ticket is closed with engineer remarks, "after" evidence, and a final status — resolved, to be reinstalled, or irrecoverable hardware damage — for full traceability.

How we verify a repair

No ticket closes on a verbal "it's fixed"

Every field visit produces a documented, auditable record — not just a status change.

Before & After Photo Evidence

Device photos, wiring close-ups, and annotated fault markers are captured before the repair and after — so there's a visual record of what was wrong and what was done.

Live Portal Cross-Check

The engineer confirms the asset is reporting correctly on the live Aether dashboard before leaving site — not just that the hardware looks fixed.

Warranty Status Determination

Every repair is logged as warranty intact or warranty void based on root cause — giving you a clear, defensible record for manufacturer or vendor disputes.

Challenges addressed

What happens without a structured repair process

These are the problems Aether's Repair & Maintenance process is built to prevent.

Undetected tampering

Wire tampering is the single largest fault category Aether's field team sees — left unchecked, it silently kills fuel and GPS reporting without anyone noticing.

Warranty disputes

Without a documented root cause, it's difficult to prove whether a fault was a manufacturing defect or physical damage — leading to disputes with hardware vendors.

Data blind spots

A malfunctioning sensor or dropped connection creates a gap in fleet, fuel, or safety data — often invisible until a report or audit surfaces missing readings.

Delayed fault response

Without a defined process and priority scheduling, faults can sit unresolved for weeks — extending the window of missing or unreliable data.

FAQ

Repair & Maintenance FAQs

What does the Annual Maintenance Contract (AMC) include?

Scheduled preventive visits, fuel sensor recalibration, connectivity and portal health checks, and priority on-site fault resolution — delivered by the same field team that installed your hardware.

How does a repair ticket get raised?

A fault can be flagged through a portal alert, reported by your team, or found during a routine health check. It's logged as a ticket with a site, asset code, and specific fault category before a field engineer is dispatched.

How do you determine if a repair is covered under warranty?

Every ticket records the root cause and its warranty impact. Faults traced to a manufacturing or technical defect are logged as warranty intact; faults caused by tampering, physical damage, or unauthorised handling are logged as warranty void.

How do you prove a repair actually fixed the problem?

The field engineer captures before-and-after photo evidence and cross-checks the asset on the live Aether portal before closing the ticket — so resolution is confirmed with data, not just a status change.

What happens if hardware can't be repaired on-site?

Tickets that can't be resolved on the spot are tagged accordingly — to be reinstalled, hardware lost, or irrecoverable hardware damage — and escalated for replacement, keeping the fault visible until it's fully closed.

Keep every sensor accurate, accountable, and covered.

Talk to Aether about an Annual Maintenance Contract for your GPS trackers, fuel sensors, and energy meters — or get a field engineer out to resolve an existing fault, verified with photo and portal evidence.