Every technician.
Every route. Every asset.

Field service management software is one system that runs the field part of a business: the work order, the engineer, the parts on the van, the time spent, the customer signature and the invoice. Because those things are recorded as they happen rather than reconstructed afterwards, you can see the true cost and margin of every job, tell a customer when an engineer will arrive, and bill on the spot.

Six integrated modules: Contract Management (contracts, revenue, profit, entitlement and SLA terms), Project Management (projects with WBS, estimated materials and resources, dependencies and duration), Customer Invoicing (milestone or on-completion invoices, cash and credit settlement), Field Service (work orders, materials, time, GPS, van inventory and tool control), Budgets and Costs (budget and cost tracking, cost per work order, margin by contract and customer) and Reports (configurable reporting on revenue, profit, SLA, cost and productivity).

It gives the engineer the day's route with navigation guidance, the job history for the asset, the parts list and the drawings; lets them book time and record materials by barcode; captures the signature; and lets them raise and settle the invoice from the same device. It works offline and syncs when coverage returns, which matters because routes routinely pass through dead zones.

The invoice can be raised at the point of service from the completed work order, settled as a cash sale or a credit payment, and printed as a receipt on a handheld device. Because the invoice is generated from source transactions, the matching accounting entries are created automatically rather than being keyed in later.

Every field work order carries a GPS track, and engineers are assigned against skills, location and current workload. The CRM creates and assigns service requests, and route planning takes into account travel time so the schedule reflects the journey and not just the job duration.

Yes. Reactive work is raised as a call-out; preventive work is generated automatically from usage data, fault history and manufacturer intervals, and it is planned against the same asset records. That matters because planned work that is never scheduled simply displaces emergency work rather than reducing it.

The van is a controlled stocking location in the same system as the depot. Availability against the scheduled job BOM is visible before the engineer leaves, tools are issued and returned against the work order, and calibration due dates are tracked, so a first-visit fix is planned rather than hoped for.

Field Service is one of six modules on a single data model, so a purchase order raised from a shortfall flows into purchasing and accounts payable, an approved call-out posts to the contract, and time booked reaches costing. There is no parallel reporting and no re-keying between the field, the depot and the finance department.

Athena deploys goal-driven agents running a continuous sense–reason–plan–act–learn loop over live field data. They sense changes in SLA status, van stock and usage; reason about which jobs will breach and which parts will be short; plan the cheapest correction; and act by reassigning engineers, raising transfers, building PM plans and pre-coding invoices. Every action is permissioned, logged and reversible, and you decide which actions run autonomously.

Engineering and facilities, automotive aftersales, oil and gas, aircraft MRO, healthcare and medical equipment, utilities and water, telecoms and manufacturing. The common requirement is installed equipment with a service obligation, where a customer expects an engineer to arrive and where the margin depends on controlling travel, parts and time.

Yes. Athena is architected as a sovereign platform and can be deployed on-premise, in a private cloud, or in a sovereign cloud region. That matters because contract values, engineer movements and customer site data are commercially sensitive, and the mobile applications and the agentic layer run inside the same deployment under your own permission model.