YARDMASTER: Midterm Master Architecture

Use this dashboard to walk the class through the exact financial and physical stakes of a "Plant Down" event during the live S7 Midterm Presentation.

The Event: The Cascading Plant Failure

A typical 10-yard pour is standard operations. But when a batch plant suffers a mechanical failure mid-schedule, the dispatcher is instantly hit with a mathematically impossible cognitive load. Here is how YARDMASTER resolves the chaos.

T-00:00 | 09:14 AM

Plant South: Aggregate Belt Snaps

Plant South goes offline instantly. 12 trucks are assigned to jobs sourced from this plant. 4 are loaded, 3 are under the silo, 5 are en route to reload.

The Physical Stake: The 90-minute concrete perishable window is ticking on loaded trucks. Any truck that cures in the drum is a $35,000+ total loss (drum replacement + DOT towing).
T+02:00 | 09:16 AM

YARDMASTER Ingestion & Anomaly Detection

Jonel API flags [PLANT_SOUTH_STATUS: OFFLINE]. YARDMASTER instantly queries the Knowledge Graph for all dependent entities.

Trucks Affected
12 Units
Active Jobs at Risk
Job Beta (Bridge Deck)
T+02:45 | 09:16:45 AM

The Triple-Gate Verification

YARDMASTER calculates rerouting the 5 empty trucks to Plant North. Before presenting to the dispatcher, the Generative Agent runs the mandatory Rigor check:

T+03:00 | 09:17 AM

Dispatcher Commitment (Human-in-the-Loop)

Instead of manually radioing 12 trucks, checking 2 computer monitors, and calling the plant manager, the Dispatcher clicks [COMMIT REROUTE] on the YARDMASTER dashboard.

The Outcome: 5 trucks successfully rerouted. $175,000 in potential catastrophic losses mitigated. Zero driver DOT violations. Plant manager isolated to fix the belt.