◆ The plan that gets staffed before the shift, not hoped through it
Savannah is short for the 06:00 inbound, and the current plan would not catch it.
A heavier-than-usual rail inbound lands at 06:00 tomorrow, and the standing crew plan is built for an average morning. The forecast reads the inbound volume and flags the gap the night before, so the early shift is sized for the real wave instead of scrambling for overtime once the boxes are already on the ground.
Recommended: add 4 to the 06:00 lift-and-yard crew and pull the start time 30 minutes earlier; the afternoon can run lighter to balance the day.
SAVANNAH · INBOUND VOLUME vs. PLANNED CREWBY HOUR
06:00 wave outruns the standing plan
◆ Tomorrow's plan · Savannah ramp
| Function | Forecast driver | Units / head | Rec. | Sched. | Gap | Status |
|---|
↳ Click any function for the hour-by-hour curve behind the recommendation.
Overtime trend
Savannah OT · last 6 weeks
Two weeks ago540 hrs
Last week420 hrs
This week (proj.)330 hrs
Most overtime traced back to morning surges the standing plan could not see coming.
Understaffing incidents
Shifts that ran short · last 30 days
Before the planner18
With the planner11
Reduction~40%
Fewer short shifts means fewer late inbounds and fewer detention exposures down the line.
Plugs into the stack USMMG already runs
read-only · works with your throughput & time-clock data · ~4–6 week build
Throughput / volume
TMramp/yard systemTime & attendance
TCtime-clockRail / inbound feed
RLrail EDILabor scheduling
SCscheduler→ Tell us your exact systems and we map the connectors to them. It reads the inbound forecast and your crew availability, and hands back a per-shift plan. Nothing migrates.
Cuts overtime around 25% and understaffing incidents around 40%.
Mockup by Instive AI for U.S. Multimodal Group · sample data
◆ Inbound volume drives the crew plan
Next 7 days · inbound by facility
The signal the staffing plan reads from
Savannah rampheavy Sat AM
Atlanta yardsteady
Charleston ramplight midweek
→ Saturday's Savannah morning is the week's sharpest peak; the crew plan is already sized for it.
Why volume + labor pair
One signal, the shift plan
The inbound forecast is the input; the staffing recommendation is the output. When a rail wave is coming, the crew is sized for it the night before instead of after the boxes hit the ground.
Savannah 06:00 · forecast+16%
Crew sized for ityes
Accuracy by facility
Forecast vs. actual
Savannah94%
Atlanta93%
Charleston91%
A staffing recommendation before every shift, sized to the inbound forecast.
Forecast view · Instive AI for USMMG · sample data
◆ Ramps & yards across the network
Savannah ramp
rail-served · high volume
Tomorrow06:00 surge
OT trenddown
Forecast accuracy94%
Atlanta yard
steady throughput
Tomorrowon plan
OT trendflat
Forecast accuracy93%
Charleston ramp
port-adjacent
Tomorrowlight
OT trenddown
Forecast accuracy91%
One planner, every facility
volume + labor from the same feeds
Every ramp and yard reads from the same inbound forecast and time-clock feeds. A 06:00 surge at Savannah and a steady day at Atlanta both turn into a crew plan the night before, so labor stops being the thing that gets hoped through the shift.
One AI layer · labor planning across ramps and yards.
Mockup by Instive AI for U.S. Multimodal Group · sample data