HOOSAI ✕ BNSF RAILWAY — THE BUILD SLATE · JULY 2026

We built the demos.

Not a deck. Not a roadmap. Six working consoles built around how a 32,500-mile railroad actually runs — a meet/pass planner for the dispatcher, a load-plan engine for the ramp, a predictive-maintenance desk for mechanical, a shipment copilot for customer service, a compliance-aware callboard for the crew office, and a safety desk for FRA reporting. Every one is live. Click into all of them.

06working demos
100%clickable — nothing staged off-screen
00slides in this pitch
01team that builds it with you

BNSF already proved the instinct works — wayside detectors reading wheels and brakes in motion by the tens of millions every day, an AI load planner sequencing outbound trains in seconds instead of hours. These six consoles are what that same instinct looks like at the desks around it: the dispatcher holding the board, the ramp planner building the train, the mechanical desk chasing a defect before it fails, the customer service rep fielding "where's my shipment," the crew clerk protecting a rest law, the safety officer drafting a report against the clock. Try them the way each of those people would. If they resonate, we scope the real builds together.

THE SLATE

Six builds. All live.

Working titles throughout — every name below is a placeholder BNSF can rename. Every demo runs on seeded, fictional data.

01
FOR THE DISPATCHER · WORKING TITLE

Meet Point — network meet/pass planner

Open the demo ↗

A dispatcher holds a subdivision the way an air-traffic controller holds a sector — juggling meets, sidings, and priority calls on instinct built over years. Meet Point puts the same math the best dispatchers already carry in their heads onto the board: which meet costs the least network time, which siding is too short, which delay is about to cascade three trains down the line.

Screenshot of the Meet Point dispatcher console
  • Live subdivision board — every train, siding, and signal block in one line-of-road view
  • AI-ranked meet/pass recommendations with total network delay shown for each option
  • Cascade warning flags a downstream conflict before the current meet is even resolved
  • Siding-capacity check stops a meet plan that a train physically won't fit
  • One-click "hold" vs "run" decision log, timestamped for the trick sheet

bnsf-meet-point.netlify.app

02
FOR THE RAMP · WORKING TITLE

Ramp Sequence — intermodal load-plan & switch list

Open the demo ↗

Building an outbound train by hand means balancing weight distribution, destination blocks, and a production track that only has so many pockets. Ramp Sequence takes today's inbound containers and trailers and returns a full load plan and switch list in seconds — not a shift.

Screenshot of the Ramp Sequence load-plan console
  • AI-generated load plan across production tracks, weight-balanced end to end
  • Auto-built switch list a hostler crew can run straight off the screen
  • Live pocket map shows track fill in real time as units get placed
  • Re-plan button reflows the whole train in seconds when a late unit shows up
  • Flags an over-length or over-weight block before it reaches the departure yard

bnsf-ramp-sequence.netlify.app

03
FOR THE MECHANICAL DESK · WORKING TITLE

Wayside — predictive maintenance from detector data

Open the demo ↗

Wayside detectors already watch every wheel and brake that rolls past — the hard part is turning tens of millions of daily readings into three cars the mechanical desk should actually pull tonight. Wayside scores every flagged axle by failure risk, not just threshold breach, and drafts the bad-order and shop routing before a human opens the report.

Screenshot of the Wayside predictive maintenance console
  • Fleet-wide risk board pulling wheel-impact, hot-bearing, and brake-thermal detector reads
  • Risk score trends a reading over its last 10 passes, not just today's snapshot
  • AI-drafted bad-order and shop-routing recommendation, one click to issue
  • Detector health map flags a wayside site drifting out of calibration
  • Car history trace shows every prior flag for the axle in question

bnsf-wayside.netlify.app

04
FOR CUSTOMER SERVICE · WORKING TITLE

Waybill Copilot — shipment visibility & predictive ETA

Open the demo ↗

"Where's my shipment" is the single most common call a customer service desk fields, and the honest answer usually takes digging across three systems. Waybill Copilot answers in a sentence — current location, predicted arrival with a confidence band, and the exception that's actually causing the delay — and drafts the customer-facing update itself.

Screenshot of the Waybill Copilot shipment visibility console
  • Natural-language lookup by waybill, equipment ID, or PO — one box, one answer
  • Predictive ETA with a confidence band, recalculated as the shipment moves
  • Exception feed surfaces the actual delay cause — interchange hold, weather, mechanical
  • One-click AI-drafted customer update, tone-matched to the account
  • Network map view traces the full route from origin to destination

bnsf-waybill-copilot.netlify.app

05
FOR THE CREW DESK · WORKING TITLE

Callboard — crew calling & Hours of Service compliance

Open the demo ↗

Calling a crew means threading seniority, rest law, and an actual train that needs to move — usually against the clock. Callboard ranks who's legal and rested right now, flags the crew member closing in on a Hours of Service limit before they're called, and builds the call list a clerk can execute in one pass.

Screenshot of the Callboard crew calling console
  • Live crew board ranked by rest status, seniority, and terminal availability
  • Hours of Service countdown per crew member, red-flagged before a limit is at risk
  • AI-suggested call order for an open turn, seniority board respected automatically
  • Dead-head and final-terminal delay math built into every rest-law calculation
  • One-tap call log — who was called, when, and what they said

bnsf-callboard.netlify.app

06
FOR THE SAFETY DESK · WORKING TITLE

Redboard — incident intake & FRA reportability copilot

Open the demo ↗

An incident report comes in from the field. Redboard structures it against the location, equipment, and prior history, drafts the FRA reportability determination with the exact threshold cited, and surfaces a defect-trend cluster before it becomes a pattern someone has to notice by hand.

Screenshot of the Redboard safety and FRA compliance console
  • Structured incident intake — no report starts as a blank text box
  • AI-drafted FRA reportability determination with the threshold and form cited
  • Defect and near-miss trend view flags a cluster by subdivision or equipment class
  • Grade-crossing risk panel ranks crossings by incident and near-miss history
  • One click routes a confirmed finding to corrective action with the full record attached

bnsf-redboard.netlify.app

THE PROCESS

Demos first. Then we scope it together.

  1. 01

    Walk the demos

    Click through all six the way a dispatcher, a ramp planner, a mechanical desk, a customer service rep, a crew clerk, or a safety officer would. Break them. Note what's wrong, what's missing, what's close.

  2. 02

    Pick the slate

    Some of these matter more than others — you tell us which. We scope the real builds around BNSF's systems, data, and safety requirements, and put the terms in writing. No fine print.

  3. 03

    Build the real thing

    The demos become production software: your data, your dispatch and detector systems, validated against the regulations you run under — FRA, PTC, whatever governs the network.

  4. 04

    Run it with you

    Built for BNSF, run with BNSF — measured against the numbers that matter to you: on-time performance, dwell time, meet delay, mean distance between failures.

BEYOND THE SLATE

Where this goes after 06.

The demos are the front of the system. Behind them sits a longer slate we'd scope the same way — demo first, then build. Working titles, all of it.

  1. 07

    PTC & signal system integration

    Meet Point's recommendations checked live against Positive Train Control enforcement before a plan is ever issued.

  2. 08

    Locomotive fuel-optimization AI

    Throttle and braking guidance tuned to grade, tonnage, and train handling — cents per gallon add up over 32,500 miles.

  3. 09

    Grade-crossing risk intelligence

    Redboard's incident history turned predictive — ranking crossings by near-miss risk before an incident happens, not after.

  4. 10

    Interline & short-line coordination copilot

    Waybill Copilot's visibility extended across a handoff to a connecting carrier, not just BNSF's own rail.

  5. 11

    Autonomous track-inspection vision

    Computer vision on an inspection car catching a rail or tie defect before a wayside detector or a human ever would.

  6. 12

    Demand & capacity forecasting by commodity

    Grain, coal, and intermodal volume forecasts tied straight to car allocation and ramp capacity planning.

  7. 13

    Hands-free dispatcher voice interface

    Meet Point, voice-driven, for the moment a dispatcher can't take their eyes off the board to touch a screen.

Walk it with us.

Thirty minutes, screens shared, all six demos open. Bring the person who'd say no — that's the most useful voice in the room.