The Gold Standard of Urban Systems | Separating Scheduled Service Frequency from Experienced Waiting Time Under Non-Random Arrivals

The short answer is that frequency is a schedule input and experienced wait is the elapsed time from a passenger’s usable arrival at the stop to boarding. Chapter 1 focuses on name the planned service and the passenger outcome. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. a route schedules six departures from 08:00 to 09:00, but a passenger arriving at 08:07 boards at 08:14 and experiences seven minutes rather than the five-minute half-headway shortcut. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for name the planned service and the passenger outcome is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. move the passenger arrival to 08:11 while preserving the vehicle record and recalculate only that passenger’s wait. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: one passenger cannot establish the route-wide distribution. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. retain passenger arrival, first boardable departure, boarding time and exclusion rules. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of name the planned service and the passenger outcome should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Next chapter

The short answer is that a regular scheduled headway is the reciprocal of frequency only inside the same stated window. Chapter 2 focuses on convert frequency to scheduled headway carefully. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. six evenly spaced departures per hour imply a ten-minute scheduled headway, whereas six departures clustered in the first forty minutes do not describe a ten-minute interval throughout the hour. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for convert frequency to scheduled headway carefully is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. shift two departures into the last twenty minutes and rebuild the sequence. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: an hourly average can hide a long gap at a window boundary. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. inspect every scheduled interval instead of dividing one headline count. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of convert frequency to scheduled headway carefully should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that mean waiting equals half a constant headway only when passenger arrivals are independent and effectively uniform within the interval and every arriving passenger can board. Chapter 3 focuses on state when half-headway reasoning applies. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. twenty passengers placed uniformly through a ten-minute repeating headway produce a teaching mean near five minutes. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for state when half-headway reasoning applies is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. make seventy per cent of passengers arrive two minutes before the scheduled departure and recompute the mean. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: exact schedule-following, crowding and real-time information break the uniform-arrival premise. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. write the passenger-arrival assumption beside the h/2 calculation. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of state when half-headway reasoning applies should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that random arrivals encounter long gaps more often because long gaps occupy more clock time. Chapter 4 focuses on weight irregular headways by the time they occupy. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. alternating actual headways of four and sixteen minutes have a time-weighted random-arrival mean of (4²+16²)/(2×(4+16)) = 6.8 minutes, not the five minutes implied by the ten-minute arithmetic mean. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for weight irregular headways by the time they occupy is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. replace the sequence with two ten-minute gaps and show why the mean returns to five. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: the formula still assumes random arrivals and boardable vehicles. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. preserve the actual headway sequence and the observation boundary. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of weight irregular headways by the time they occupy should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that when riders time their arrival to a schedule, the arrival distribution belongs in the calculation. Chapter 5 focuses on model non-random passenger arrivals directly. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. forty commuters arrive two minutes before each scheduled train and twenty arrive uniformly; the combined teaching mean is weighted from the two groups rather than inferred from frequency alone. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for model non-random passenger arrivals directly is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. give the schedule-following group a three-minute information delay and rebuild their waits. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: self-reported arrival habits can differ from observed timestamps. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. use observed or declared arrival groups and publish their weights. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of model non-random passenger arrivals directly should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that experienced waiting should be calculated from eligible passenger journeys rather than vehicle counts. Chapter 6 focuses on work an original stop-level cohort. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. twelve passenger records show waits of 2, 3, 3, 4, 4, 5, 6, 7, 8, 11, 15 and 18 minutes; the mean is 7.17 minutes and the median is 5.5 minutes despite a six-per-hour schedule. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for work an original stop-level cohort is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. remove the two longest waits only after documenting a disruption rule and compare the changed summary. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: a small fixture teaches the calculation but does not estimate a city network. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. keep the unsummarised wait records and state mean, median and upper-tail measures. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of work an original stop-level cohort should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that a vehicle leaving before its scheduled time can turn a short planned wait into nearly a full extra headway. Chapter 7 focuses on treat early departures and missed service as real events. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. a rider arrives at 08:09 for an 08:10 departure that left at 08:08 and boards the 08:20 vehicle, producing an eleven-minute experienced wait. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for treat early departures and missed service as real events is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. hold the actual departure until 08:10 and isolate the two-minute early-departure effect. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: a passenger may not know whether the vehicle left early or was cancelled. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. reconcile timetable, vehicle-location and passenger records before assigning cause. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of treat early departures and missed service as real events should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that the first arriving vehicle is not the end of the wait when a passenger cannot board. Chapter 8 focuses on include capacity and denied boarding. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. a train reaches the platform after four minutes but is full; boarding occurs on the next train nine minutes later, so the experienced wait is thirteen minutes. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for include capacity and denied boarding is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. add enough capacity to the first train and recompute without changing frequency. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: observed platform crowding does not identify each passenger’s boarding choice. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. record pass-ups, capacity evidence and voluntary versus involuntary non-boarding. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of include capacity and denied boarding should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that reliable countdown information can shift when passengers enter the waiting environment without changing scheduled frequency. Chapter 9 focuses on recognise that information changes arrival behaviour. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. a group that once arrived randomly begins arriving three minutes before predicted departures, lowering observed platform wait while door-to-door planning time may remain. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for recognise that information changes arrival behaviour is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. introduce prediction errors of plus or minus four minutes and examine the new tail. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: shorter measured platform wait does not by itself prove a shorter whole journey. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. state the start point of the clock and the information available to passengers. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of recognise that information changes arrival behaviour should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that a daily experienced-wait average should weight passenger journeys, not give a quiet and busy period equal influence. Chapter 10 focuses on compare periods with passenger weighting. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. the peak has 800 riders averaging seven minutes and the off-peak has 200 averaging four minutes, giving 6.4 minutes passenger-weighted rather than 5.5 minutes from an unweighted period mean. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for compare periods with passenger weighting is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. swap the passenger volumes while keeping period means fixed. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: aggregate figures can conceal stop, direction and accessibility differences. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. publish period counts and stratified results with the total. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of compare periods with passenger weighting should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that the distinction must survive a new passenger-arrival pattern and an irregular actual service pattern. Chapter 11 focuses on run a changed-context reliability check. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. the schedule remains six per hour, but actual headways become 6, 7, 9, 14 and 14 minutes while more riders use live predictions; the wait distribution is rebuilt from the joined records. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for run a changed-context reliability check is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. restore even actual headways while leaving passenger behaviour unchanged. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: a changed wait can reflect operations, behaviour or both. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. compare schedule, actual service and arrival-pattern changes in separate columns. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of run a changed-context reliability check should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Next chapter

The short answer is that a useful report states scheduled frequency, actual headways, passenger-arrival basis, boarding constraints and the resulting wait distribution. Chapter 12 focuses on write a decision-ready service account. Begin with define the stop, direction, service window, scheduled departures, actual departures, passenger-arrival process and boarding rule before comparing frequency with waiting. Writing those facts first prevents a familiar label or final summary value from replacing the mechanism or measurement basis that actually decides the result.

Worked example. the final note reports six scheduled departures per hour, actual headways from six to fourteen minutes, a 6.4-minute passenger-weighted mean and an eleven-minute ninetieth percentile under the stated fixture. Treat every stated value as part of a controlled teaching fixture. Record the starting state before the operation, then record each conversion, selection, calculation, check or state transition in order. If a prerequisite fails, stop the trace there rather than inferring later effects from the usual path.

A useful first-principles question for write a decision-ready service account is: what must be defined before this comparison can be made? Separate the population or physical quantity, observation, transformation and conclusion. Two reports can show similar values while using different units, windows, targets or measurement rules.

Now change exactly one premise. replace the bus route with a low-frequency ferry where most users follow a timetable and revise the method. Recalculate from the changed fact rather than editing the old conclusion. Name the earliest quantity or classification that differs, carry that difference through the remaining steps, and state which observations stay comparable.

The main limit is this: the worked figures are teaching data rather than a service-performance claim. Keep the measured or reported quantity separate from the wider decision, cause or quality claim. A focused example can establish the stated relationship without pretending to settle every operational, clinical, regulatory or institutional question around it.

Practical evidence check. verify timestamps, time zones, stop direction, cancellations, pass-ups and passenger weights. Capture the reported values and exception conditions, and preserve the calculation or observation trail that produced them. A check of only the final label can pass even when an earlier selection, conversion, denominator, target or measurement basis was wrong.

A concise final explanation of write a decision-ready service account should state the starting data, governing rule, ordered result and one boundary. It should not depend on one display, one dashboard tile or an unstated assumption. That form is short enough for revision and precise enough for a reproducible evidence note.

Contents · Previous chapter · Return to the Urban Systems subject guide