XBE

We Put Dispatch On Trial

And It Was Convicted.

At XBE, we recently ran an internal ritual we call “putting something on trial.”

No slides. No roadmap talk. No defending the status quo.

Just one question, argued honestly from every angle:

Is the way dispatch is done today actually good enough?

Not “is it familiar.”
Not “does it technically work.”
But: If we were designing dispatch from scratch today, knowing what modern operations actually demand, would we build this?

The verdict was unanimous.

Dispatch, as it exists today, is guilty—not because people are bad at it, but because the tools are fundamentally misaligned with the job.

And yes, that includes our own.

Exhibit A: What’s Dumb About Dispatch Today

Let’s be specific.

Modern dispatch asks people to run one of the most complex, time-sensitive operations in industrial logistics. Concrete producers are balancing:

Orders with hard delivery windows
Plants with physical constraints
Drivers with hours, skills, and fatigue
Trucks that never break down on schedule
Margin, service, and customer promises—all at once

And then we hand dispatchers tools that show:

Trucks on one screen
Orders on another
Demand charts somewhere else
Driver hours tracked manually—or not at all
Sticky notes, spreadsheets, and tribal knowledge filling the gaps

The “system” doesn’t actually model the operation. It shows fragments and asks humans to mentally stitch them together—while taking calls, handling surprises, and absorbing blame when the day goes sideways.

So what happens?

Firefighting becomes the default
The loudest problem gets solved, not the most important one
Tradeoffs stay implicit until it’s too late
The entire day hinges on whether the first round went perfectly

This approach only works when the day is stable. And concrete operations are almost never stable.

Exhibit B: Cloud Didn’t Fix This

As an industry (us included!), we spent years modernizing infrastructure and told ourselves we were modernizing dispatch.

We moved systems to the cloud. We made data more accessible. We talked about openness and integrations.

That work mattered. But quietly, it became the ceiling instead of the foundation.

Dispatch itself stayed the same:

Orders still scheduled one by one
Decisions still made in isolation
Ripple effects still discovered after they cascaded

What’s most absurd? In 2026 we are still seeing exports into excel, sticky notes aghast & critical decisions on whiteboards lost into oblivion.

Our own system is guilty. Until operations got more complex, expectations increased, and “working” stopped being good enough.

By today’s standards, running dispatch without the ability to simulate outcomes, understand system-wide impact, and act from a unified model isn’t just limiting, it’s irresponsible.

That realization is what led to All-22.

The Core Insight: You Don’t Get Late Late. You Get Late Early.

Most operational failures are visible before they happen.

The problem isn’t that dispatchers make bad decisions. It’s that they’re forced to make decisions without seeing the system clearly enough.

Traditional dispatch shows activity. All-22 was built to show interaction.

Where risk is accumulating
Which loads matter most to the rest of the day
How uncertainty propagates across plants, trucks, and schedules

Once you can see the full operation as a system, reacting after problems cascade stops making sense.

Introducing All-22

All-22 is not a dispatch screen. It’s not an optimizer bolted on. It’s not a dashboard.

All-22 is the sole view within XBE that ready-mix producers need to run their day.

It models the entire operation, from order intake to final truck return - in one living frame. An fundamentally different way of working is unlocked

1. Simulation Before Commitment

Dispatch teams can simulate the day before locking it in. They can test scenarios, adjust priorities, identify fragile plans, and see whether the day can actually work—without learning the hard way.

2. Optimization on Your Terms

All-22 optimizes based on how you want to operate.

Prioritize service
Protect margin
Smooth plant rhythm
Adjust risk tolerance

The system adapts to the operator—not the other way around.

3. Execution With Context

The same model used to plan the day is used to run it. As reality drifts, that drift becomes visible early. Adjustments happen with full context—not panic.

Insight and execution stay connected.

Why This Is a Line in the Sand

All-22 isn’t an incremental upgrade. It’s a rejection of the old mental model.

Once you can:

See the full field in one frame
Make tradeoffs explicit before committing
Understand why something will break—not just that it did

Running dispatch any other way stops making sense.

This is dispatch evolving from activity management to operational control.

The Real Outcome: Confidence

Without All-22:

Dispatch relies on experience and gut feel
First round is planned—everything else is chaos
Stress scales faster than performance

With All-22:

The entire system is intelligible
Risk is visible early
Decisions are explainable and shared
Performance compounds instead of breaking

The day stops running you. You run the day.

Final Thought

Putting dispatch on trial wasn’t about blaming the past.

It was about admitting that the industry, and our own product, outgrew an old way of thinking.

All-22 is our answer to that moment.

Not a better screen. A better standard.

And once you see the entire operation from this angle, there’s no going back.