How often can we send a bus?
A bus must drive to SIC, unload, return and load again before repeating the trip. More buses can overlap those trips, but each bus still needs time to complete its cycle.
| Starting point | Distance (km) to SIC / back | One bus: full cycle | One departure about every | People moved per hour* | Buses needed for 1-min departures |
|---|
*Steady-state planning rate, using occupancy and shared SIC loading-bay limits. Not a daily ticket cap. Rest, time-varying queues and final cutoff are tested in the simulation.
What is included, assumed and missing
Dedicated service baseline only. Mixed-origin pickup/drop-off is not credited with extra capacity. Return paths for T1/LTCP use the supplied road via Mitsui; shorter direct return geometry is missing. The supplied T1 walking sketch is excluded. Small gaps at hub entrances are not treated as surveyed bay circulation.
SIC queue controls are conceptual. Holding-space dimensions, safe crowd limits, checkpoint positions, T1 double-decker clearance, actual driver roster, confirmed bus staging and internal-shuttle supply still need site confirmation. No cost, ticket revenue, GPS or booking integration is included.
Hourly movement & end-of-day result
| Hour | Our hub departures passengers | Rapid hub passengers | SIC departures all passengers |
|---|
| End result | Our services | Rapid* |
|---|
Time · location · waiting people · oldest wait · buses ready · last departure / onboard count · journey minutes · incident.
Queue numbers here are model estimates. These reports should replace assumptions during operations; they are not connected automatically.
*Rapid return timing is provisional. Departures count passenger legs, not unique return-pass buyers. The last SIC departure is a cutoff; passengers can arrive at their hub later.