Allocation and scheduling systems, and the data infrastructure underneath them.

The work

Routing a delivery fleet, assigning physicians across sites, distributing scarce slots fairly, classifying freight at scale — underneath, these are one problem. Finite resources, hard constraints, and a decision that has to be defensible to the people living with it.

I build the systems that make those decisions, and the data infrastructure that makes the results measurable afterwards. Then I keep them running.

Depth

Thirty years in transportation software, ending as VP of Engineering at Omnitracs — the company that builds Roadnet Anywhere. Since 2020, independent practice.

That includes designing and operating a Transportation Data Warehouse on Azure, populated from a customer's own routing data through the RNA web services, and the reporting layer that turns dispatch and execution data into something an operations team can actually run on.

Range

• Healthcare operations Physician scheduling across a multi-site radiology practice — assignment by time and distance, and fair allocation of contested time off.
• Fleet & distribution Routing analytics, geofencing, territory planning, and operational reporting for logistics and distribution operators.
• Freight standards Rules-driven freight classification and charge calculation at scale.
• Platform Azure SQL, Azure Functions, Automation Accounts, C# and .NET, ETL and systems integration.

How I work

One good test is worth a thousand expert opinions.

Estimates and opinions are cheap, including mine. Build the thing, measure it, and let the result decide.

I also operate what I build. Most of these systems have been in production for years, and I am still the person who answers when something needs attention — which tends to matter more than how the first version was written.