NOAX/Executive Brief
May 2026 · OSP Operations Review · Executive

0
Trucks Rolled.

Yet only a fraction actually fixed the network.

OSP Dispatches
0
NOC Tickets
0
Unique Nodes
0
Tickets Escalated
0%

As the month unfolded, one question emerged —

Were we fixing problems, or simply chasing them?

§ 02Where did the trucks go?

25,104 dispatches.
Eight outcomes.

Tap any outcome to see what the technician actually encountered on site.

Outcome composition · May 2026
Tap any outcome to expand
Conclusion
57%of completed dispatches produced no actionable field work.
Power outage · cleared before arrival · duplicate parent · no trouble found · auto kickback · maintenance.
§ 03So how many trucks actually mattered?
Only
0%
actually repaired the network.
Effectiveness ratio
84% · no fix
16%

Most trucks were sent to situations where the technician could not change the outcome.

§ 04Were these new problems, or the same problems again?

The real cost wasn't one dispatch.
It was the second.

15,406 unique nodes generated tickets in May. One third generated them again. And again.

One-and-done
Repeat node
Unique nodes
15,406
Repeat
5,089
% Repeat
33%
Repeat nodes
0
of 15,406 unique
Dispatches from repeats
0
58% of all activity
Excess truck rolls
0
redundant repeat visits

One-third of the network generated nearly 60% of all dispatch activity.

§ 05Why do the same nodes keep generating trucks?

Repeat nodes don't look broken differently —
they look ambiguous more often.

Outcome
Single
Repeat
Cleared Before Arrival

The fault disappears before the truck arrives. Days later it returns. The system dispatches again. The cycle repeats.

↻Truck dispatched
↻Issue disappears
↻Truck returns
↻Issue reappears
Tap a row to inspect
§ 06What is actually happening on the ground?

The
intermittent
loop.

An alarm fires. A truck rolls. The condition clears in transit. The technician finds nothing. Days later, the same node fires again. The system, having no memory, dispatches again.

Dispatch is not a tool for solving this. It is the loop's accelerant.

Issue AppearsAlarm FiresTruck DispatchedCondition ClearsTech ArrivesNothing FoundIssue ReturnsAlarm Fires Again
The core failure
Dispatch cannot break
intermittent faults
§ 07What does this cost the business?
Dispatches initiated
0
Were repeat truck rolls
0
Produced no actionable work
0%
Downstream
Thousands of engineering hours,
consumed by symptoms.
Dispatch volume · running
0 excess
§ 08What changes if dispatch has memory?

Two operating models.
One decision gap.

Current Model
Reflex
SIGNAL → ACTION
  1. 01Alarm↓
  2. 02Dispatch↓
  3. 03Repeat↓
  4. 04Dispatch↓
  5. 05Repeat↓
  6. 06Dispatch↓
  7. 07Repeat
NOAX
Reasoned
SIGNAL → DECISION
  1. 01
    Alarm
    Signal received.
    ↓
  2. 02
    Operational Memory
    What happened here before?
    ↓
  3. 03
    Historical Evidence
    Last 90 days of outcomes for this node.
    ↓
  4. 04
    Engineering Pattern Detection
    Is this intermittent? Power-side? Seasonal?
    ↓
  5. 05
    Probability of Success
    Will another truck actually help?
    ↓
  6. 06
    Best Next Action
    Dispatch, monitor, investigate, escalate, or suppress.
Dispatch only if justified.
Tap a step to expand
§ 09So what is the real opportunity?

The opportunity is not reducing dispatch.
The opportunity is preventing the wrong dispatch.

Today
Every alarm becomes
a truck.
NOAX
Every alarm becomes
a decision.

The Network Doesn't
Need More Trucks.

It Needs Better Memory.

One-third of nodes created nearly sixty percent of dispatch activity.

Those nodes don't need another technician.

They need intelligence.

NOAX
Network Operational Awareness · 2026