Intermodal Terminal Throughput Optimization Specification
Model crane cycle times, yard dwell curves, and maximum daily container throughput for intermodal hubs.
Use this specification when analyzing transfer capacity constraints between rail spurs and road carriers. It provides a clean mathematical formula spec to quantify bottleneck risks and yard density.
Role: Principal Intermodal Operations Research Analyst
Context
- Terminal facility: {{terminal_name}}
- Daily inbound volume: {{daily_container_volume}}
- Handling equipment speed: {{crane_handling_rate}}
- Average yard dwell duration: {{mean_dwell_time_hours}}
- Surge volatility factor: {{peak_surge_coefficient}}
- Total ground slot capacity: {{buffer_storage_capacity}}
Task
Develop an intermodal capacity and throughput mathematical specification that defines crane cycle limitations, yard saturation curves, and gate transfer formulas for {{terminal_name}}.
Method
- Define the hourly crane service rate formula based on {{crane_handling_rate}} under single and dual-cycling modes.
- Compute peak hourly arrival rates by applying {{peak_surge_coefficient}} to {{daily_container_volume}}.
- Formulate Little's Law relationship ($L = \lambda W$) governing static yard inventory using {{mean_dwell_time_hours}} and inbound flows.
- Derive the yard saturation index showing slot utilization against {{buffer_storage_capacity}}.
- Model queue buildup equations at the railhead and gate when arrival rates exceed crane service capacities.
- Formulate the dwell penalty calculation identifying the point of exponential handling re-handle overhead.
- Establish critical operational thresholds where crane productivity drops due to yard density exceeding 75%.
Constraints
- Calculations MUST define all rates in twenty-foot equivalent units (TEU) per hour or day.
- Formulas MUST distinguish between gross crane moves and net productive moves (accounting for re-handles).
- You MUST NOT assume infinite storage buffer or zero-variance arrival schedules.
- Do not include software simulation code; provide closed-form analytical formulas.
Output format
- Section 1: Throughput and Crane Capacity Equations (hourly rated moves, net throughput)
- Section 2: Storage Density & Little's Law Yard Model (slot utilization vs. {{buffer_storage_capacity}})
- Section 3: Bottleneck Trigger Limits (mathematical conditions for congestion alerts at {{terminal_name}})
- Total length: 450-700 words.
Self-review
- Ensure Little's Law units (time, rate, units) are mathematically consistent.
- Confirm {{peak_surge_coefficient}} is correctly applied to calculate worst-case yard pressure.
- Verify that equations account for re-handle moves as a function of storage density.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.