Skip to content
HeuriTel
Sign in
Partner and Delivery Operations

Field & Workforce Operations

Send the right technician, with the right part, to the job that matters most today.

Field jobs are prioritised by the customers and revenue behind them; technicians are scheduled and routed, parts demand is forecast, and tower and fibre maintenance is predicted before the fault, with each dispatch approved through the operator's change process.

For Field operations, network operations and contractor management teams.

The decision, annotated from the record

Sixty field jobs are open for twelve technicians, and the oldest job is a cabinet nobody depends on while a tower serving a district clinic waits.

The jobs worked today, by whom, in which order, and with which parts on the van.

  1. The jobs ranked by the customers and revenue behind each siteConsidered
  2. A remote fix, where the fault allows oneConsidered
  3. A rescheduled visit, where site access or the part is missingConsidered
  4. No dispatch, where the safety policy or a freeze forbids itConsidered

Before anything reaches the customer: Safety policy, site access, parts availability, maintenance freeze and change policy checks pass.

What would reach them: Dispatch through the work-order system on approval, and tell the customer waiting when the visit will come. On Field app, SMS.

Annotated, not computed. No engine runs on this page. Read the journey in full

No demonstration is configured for this journey yet.

Configured for

Bank or MFI

Change
The decision

The jobs worked today, by whom, in which order, and with which parts on the van.

Sixty field jobs are open for twelve technicians. The oldest job is a cabinet nobody depends on. A tower serving a district clinic has waited since the morning.

  • The jobs ranked by the customers and revenue behind each site
  • A remote fix, where the fault allows one
  • A rescheduled visit, where site access or the part is missing
  • No dispatch, where the safety policy or a freeze forbids it
What it does

Three things it helps you decide or do.

  • Prioritise the job by who it affects

    Field job prioritisation reads telemetry, topology and the customers behind each site, and tower and fibre maintenance prediction puts the failing asset on the list before it fails.

    • site_or_cell_id
    • timestamp
    • traffic
    • throughput
    • latency
    • loss
    • utilisation
    • alarms
    • coverage
    • affected_customers
    • revenue_aggregate
    • capex_or_opex
    • action_outcome
  • Schedule, route and equip the visit

    Technician scheduling and routing, parts demand forecasting and site access coordination decide who goes, when and with what; a safety policy, a maintenance freeze or missing site access holds the dispatch.

    • Observe
    • tune
    • dispatch
    • add capacity
    • rehome traffic
    • schedule change
    • communicate
    • reject investment
    • escalate
  • Judge the visit by first-time fix and work-order quality

    The change ticket, the controller's response and the KPI before and after are kept per job, so first-time fix, contractor performance and work-order quality are measured and the customer is told what happened.

    • Telemetry snapshot
    • topology/version
    • recommendation
    • approval/change ticket
    • controller response
    • before/after KPI
    • finance validation
The journey

Send the right technician, with the right part, to the job that matters most

No demonstration is configured for this product yet.

Field & Workforce Operations: the situation this product is about

Field operations, network operations and contractor management teams

StepWhat the customer experiencesWhat the operator does
The momentThe moment that started it.Sixty field jobs are open for twelve technicians, and the oldest job is a cabinet nobody depends on while a tower serving a district clinic waits.Reads the open jobs and the customers behind each site, technician skills, location and hours, parts availability and site access, safety policy, freezes and change approval.
The decisionThe decision to be made.Nothing reaches the customer yet.Ranks the jobs by the customers and revenue behind each site, and schedules and routes the technicians with the parts each job needs.
The safeguardsThe conditions that stop it.Still nothing. No action is sent until every check has passed.Safety policy, site access, parts availability, maintenance freeze and change policy checks pass.
The actionThe action that reaches the customer.Dispatch through the work-order system on approval, and tell the customer waiting when the visit will come. Reaches them on Field app, SMS, in English, Kiswahili.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.The tower is dispatched first and the technician arrives without the access permit, so the visit is wasted and the clinic waits another day.Site access coordination is a check before dispatch, the permit is requested with the job, and the work-order record shows the wait was the permit's, not the technician's.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.First-time fix and time to restore on the jobs that mattered most, against jobs re-visited.
The proofThe proof anyone can check.Can be answered for, later, from the record.Job list, customer impact, ranking reasons, schedule, route, parts, work order, controller response and first-time-fix record.

Hypothesis

A visit that fixes the job first time costs one trip; one that finds the part missing costs two and the customer's confidence.

Desired result: Improved service and reliability; lower cost/energy; better CAPEX prioritisation; reduced MTTR

Modelled not observed

No figure is modelled for this journey. The mechanism that could produce the result is stated instead.

Collect → validate topology → detect/forecast → quantify impact → recommend → human/controller approve → execute → verify service/economic result → learn

Observed

Nothing yet. Measurement begins in a pilot’s validate stage, on your systems, against a comparison agreed first.

Matched site/cell comparison, stepped-wedge rollout or before/after with seasonality controls; technical and economic acceptance criteria

Measured on: Service experience; utilisation; incidents; MTTR; repeat fault; avoided congestion; cost; energy; affected customers; incremental/retained value

Assumptions, costs and the record’s five answers
  1. 01
    Desired result

    The result wanted.

    Improved service and reliability; lower cost/energy; better CAPEX prioritisation; reduced MTTR

  2. 02
    Mechanism

    The mechanism that could produce it.

    Collect → validate topology → detect/forecast → quantify impact → recommend → human/controller approve → execute → verify service/economic result → learn

  3. 03
    Evidence required

    The records kept to show it.

    Telemetry snapshot; topology/version; recommendation; approval/change ticket; controller response; before/after KPI; finance validation

  4. 04
    Costs and risks

    The cost, and the ways it can go wrong.

    Costs: Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline

    If it fails: Default to observe/recommend; never make unapproved network change; open incident; preserve last-known-good config and audit trail

  5. 05
    Measurement approach

    The measure that shows it helped.

    Matched site/cell comparison, stepped-wedge rollout or before/after with seasonality controls; technical and economic acceptance criteria

    Measured on: Service experience; utilisation; incidents; MTTR; repeat fault; avoided congestion; cost; energy; affected customers; incremental/retained value

Nothing has been observed for this product. Every line above is the record's own design intent; measurement begins in a pilot's validate stage, on your systems, with the comparison agreed first.

The business side

The change
First-time fix and time to restore on the jobs that mattered most, against jobs re-visited.
Running cost
Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
What evidence supports it
Job list, customer impact, ranking reasons, schedule, route, parts, work order, controller response and first-time-fix record.
Technical detail

Inputs, decision logic, systems touched, records kept.

Four questions an evaluation asks in a different order every time. Every field is the workbook’s own, unedited.

What would we need from your systems, and how much history?

Attributes required

  • site_or_cell_id
  • timestamp
  • traffic
  • throughput
  • latency
  • loss
  • utilisation
  • alarms
  • coverage
  • affected_customers
  • revenue_aggregate
  • capex_or_opex
  • action_outcome

Also useful, not required

  • Competitor/drive-test data
  • weather
  • events
  • crowds
  • complaints
  • device mix
  • spectrum
  • energy
  • partner demand

8-12 weeks telemetry and topology; stable site/cell mapping; incident/action history; cost/action catalogue; aggregated customer value where used

The 14 definitions underneath

14 in this product

  1. HeuriTel Field Workforce OptimisationDecision definitionHT-0493

    Identify eligible records for field workforce optimisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0493
  2. HeuriTel Technician SchedulingDecision definitionHT-0494

    Identify eligible records for technician scheduling, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0494
  3. HeuriTel Technician RoutingDecision definitionHT-0495

    Identify eligible records for technician routing, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0495
  4. HeuriTel First-Time FixDecision definitionHT-0496

    Identify eligible records for first-time fix, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0496
  5. HeuriTel Parts Demand ForecastingDecision definitionHT-0497

    Identify eligible records for parts demand forecasting, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0497
  6. HeuriTel Field Job PrioritisationDecision definitionHT-0498

    Identify eligible records for field job prioritisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0498
  7. HeuriTel Tower Maintenance PredictionDecision definitionHT-0499

    Identify eligible records for tower maintenance prediction, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0499
  8. HeuriTel Fibre Maintenance PredictionDecision definitionHT-0500

    Use network, customer and economic data to support fibre maintenance prediction, with operator-approved actions, change controls and post-action verification.

    /d/HT-0500
  9. HeuriTel Site Access CoordinationDecision definitionHT-0501

    Use network, customer and economic data to support site access coordination, with operator-approved actions, change controls and post-action verification.

    /d/HT-0501
  10. HeuriTel Field Safety MonitoringDecision definitionHT-0502

    Identify eligible records for field safety monitoring, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0502
  11. HeuriTel Contractor PerformanceDecision definitionHT-0503

    Identify eligible records for contractor performance, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0503
  12. HeuriTel Work Order QualityDecision definitionHT-0504

    Identify eligible records for work order quality, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0504
  13. HeuriTel Remote Technician AssistDecision definitionHT-0505

    Identify eligible records for remote technician assist, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0505
  14. HeuriTel Field Service Customer CommunicationDecision definitionHT-0506

    Identify eligible records for field service customer communication, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0506

Search definitions across every product

Implementing it

Four stages, and what has to be true before the next one starts.

12-16 weeks for decision support; closed-loop automation requires additional change, safety and vendor certification. A team of 8 roles, named in the record rather than promised.

  1. 01

    Scope

    One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.

    • Select scenario
    • define action authority
    • baseline
  2. 02

    Connect

    The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.

    • map topology/telemetry
    • integrate tickets
  3. 03

    Validate

    Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.

    • build detection/ranking
    • shadow
    • operator-approved pilot
  4. 04

    Operate

    The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.

    • Collect
    • validate topology
    • detect/forecast
    • quantify impact
    • recommend
    • human/controller approve
    • execute
    • verify service/economic result
    • learn

Who does it. 1 network solution lead · 1 network SME · 1 data engineer · 1 ML engineer · 1 OSS integration developer · 0.5 QA · 0.5 DevSecOps · 1 coordinator

Four states are tracked, and each is assessed against your systems.

Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.

Readiness

Needs client data and integration review

The client’s data and integration position.
Runtime / build state

Target product definition

What exists as running software.
Surface state

Not audited

Whether this product shows the entry anywhere.
Client status

Not assessed

Where a named client has reached.

Next steps from here.

14 definitions sit under Field & Workforce Operations. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.

See HeuriTel configured for your organisation

Verify your work email to open a demonstration configured for your organisation.