Christopher Azar-Brandes
Software for the jobs that go sideways.
Industrial operations · Procurement and logistics · Decision-support software
More than three years in industrial parts, purchasing and supplier coordination for field service, and five working tools built from that work: dispatch, purchasing, freight, production scheduling and bids. Close a road on that map and FreightFlow's real router, running in this tab, finds another way and prices the detour.
- 5
- tools you can actually use here, not screenshots of them
- 455
- unit tests passing in the five original projects, re-run from fresh clones on 1 Nov 2026 (commits listed under Engineering)
- 0
- real customers. Every company, part and load in here is made up
- Distance
- 581 mi
- Drive time
- 10.4 h
- Lane cost
- $1,459
The five tools
One hard operational problem each, worked all the way through.
Each started as a full app with its own test suite. Pick one: you get the problem it solves, a number its own engine calculated, and the working version, running in your browser on made-up data. Break something; Reset puts it back.
Turn urgent service demand into an accountable plan for people, parts, and time.
Constraint-aware technician assignment that names exactly why a candidate is disqualified.
recommendTechnicians()- 66ptsT-104 ranks first for WO-10483; 4 of 6 technicians blocked with a stated reason Calculated when this page was built
Inside: Command center · Work orders · Dispatch · Parts · SLA & exceptions · Scenario Lab
36 unit tests passed in the original project
Full ServiceOPS app: deployed privately; public release pending
Make sourcing decisions with the cost, timing, risk, and approval path visible.
Shortage maths (safety stock, reorder point, EOQ) plus a seeded Monte Carlo stockout model that ranks sourcing options.
reorderMetrics()- 118.4unitsReorder point for MOT-4408 at 98% service, 42-day lead time Calculated when this page was built
Inside: Command Center · Decision Workbench · Inventory · Suppliers · RFQs & Quotes · Purchase Orders · Approvals · Audit Trail
85 unit tests passed in the original project
Full ProcureOS app: deployed privately; public release pending
Keep freight moving when routes, equipment, timing, and margin pull in different directions.
Operation Iron Relay: a breakdown-to-recovery exercise using feasibility-gated carrier scoring and Dijkstra routing.
calculateRoute() · Dijkstra- 581miDetroit → Nashville, 10.4 h modeled across 2 corridors Calculated when this page was built
Inside: Command Center · Shipments · Dispatch Board · Carriers · Route Intelligence · Exceptions · Freight Costs · Recovery Simulator
14 unit tests passed in the original project
Full FreightFlow app: deployed privately; public release pending
Recover a production plan when machine capacity and delivery promises collide.
Deterministic scheduling engine with invariant auditing and a ranked factory-recovery comparison after a CNC outage.
finite-capacity replan- 11orders delayedby an 8-hour CNC-02 outage after a plain re-plan; 24 orders were already late. Recorded from the full app Recorded run
Inside: Command center · Production orders · Routings · Work centers · Schedule · Disruption & recovery
280 unit tests passed in the original project
Full ForgePlan app: deployed privately; public release pending
Build a defensible price from quantities, costs, risk, and commercial rules.
A pricing chain (direct, indirect, contingency, tax, fee) that reproduces to the cent, with frozen revisions and bid leveling.
calcEstimate()- $1,223,520sell10.0% markup = 9.1% gross margin. Not the same number Calculated when this page was built
Inside: Projects & estimates · Estimate editor · Bid leveling · Pricing summary · Revisions
40 unit tests passed in the original project
Full EstimateOS app: not deployed yet; public release pending
06 · Pantry Pal: household inventory and use-it-first cooking. In development; its demo is unmerged, so it is described, not demonstrated. Status
Short on time?
Ten minutes is enough.
Make a bad call
Pick a job or a load, try something the rules don't allow, and read the reason you get back.
Look under the hood
The case studies walk through the rules and the math, and point to the files they came from.
Check the receipts
Every test count says how it was produced. What isn't finished is listed next to the work.
Who built this
Christopher Azar-Brandes
Procurement · Industrial Operations · Operations Systems
I'm an industrial operations professional who also builds software. I've handled parts and service requests end to end, from identifying the component on a drawing or schematic to the supplier quote, the purchase, the shipment and the warranty claim. I've seen what happens when a part the system says is coming isn't, when two jobs need the same crew, or when nobody can say why a decision was made. The five tools on this site are my answers to those problems.
- Veldarium Technology Systems LLCFounder, Industrial Software Development
- WhiskerMatchFounder, Software Product Development
- MoveJunkProject Manager, Business Consultant
Purchasing · Supplier coordination · Global Shop ERP · Salesforce · Excel · SQL/PostgreSQL · Python · TypeScript · React / Next.js