The Umbrex Travel, Transportation & Logistics Industry Practice has prepared this guide to terminology, acronyms, shorthand, and insider language to help a newcomer to the public transit & mobility agencies (bus and rail authorities) sector get up to speed rapidly.
Service Planning and Scheduling
Headway and frequency
Headway is the scheduled or observed time between consecutive vehicles on the same service, usually stated in minutes. Frequency expresses the same concept as vehicles per hour: frequency = 60 / headway. A 10-minute headway therefore means six vehicles per hour.
The distinction between scheduled and observed headway matters. A route can be scheduled every 10 minutes yet produce observed gaps of 3, 7, and 20 minutes because of bunching. On high-frequency services, operations teams often care more about even headways than exact timetable adherence.
Span of service
The span is the period from the first scheduled trip to the last scheduled trip, either systemwide or on a particular route and day type. It is commonly described as early morning, late evening, overnight, or 24-hour service.
Span is not the duration of an individual trip. Expanding span can require relatively few additional trips but still create difficult crew, garage, security, and connecting-service implications at the edges of the service day.
Timepoint
A timepoint is a designated location where a timetable specifies an arrival or departure time. Unlike an ordinary stop, it is used to measure schedule adherence and control early departures. Operators are typically prohibited from leaving a timepoint early, even if they may pass intermediate stops ahead of the estimated schedule.
When a planner says a route needs another timepoint, the concern is usually schedule control rather than passenger demand at that location. Too many timepoints can make a schedule rigid; too few can allow early running to compound across a route.
Running time, recovery time, and cycle time
Running time is the scheduled time needed to travel between specified points. Recovery time is terminal time intended to absorb variability and help the next trip depart on time. Layover is terminal time available to the vehicle or operator, although agencies differ on whether they use layover and recovery as synonyms.
Cycle time is the time required to complete the full repeating route pattern, including outbound and inbound running time plus terminal time. Cycle time directly determines how many vehicles are needed for a headway. Adding five minutes of recovery can improve reliability while also tipping the schedule into another peak vehicle.
Peak vehicle requirement (PVR)
Peak vehicle requirement is the maximum number of vehicles simultaneously needed to operate the scheduled service. Practitioners may also say peak pull-out or maximum service requirement.
PVR is not fleet size. The agency needs PVR plus spare vehicles, maintenance float, and sometimes contingency equipment. A proposed service increase that adds one peak block may therefore require more than one additional vehicle once spare-ratio and maintenance needs are considered.
Trunk-feeder network
A trunk-feeder design concentrates frequent, high-capacity service on major corridors and uses local routes to feed passengers into the trunk. The alternative is often a network of one-seat routes that independently travel from neighborhoods toward major destinations.
Trunk-feeder designs can improve frequency and resource efficiency, but they create transfers and make connection reliability more important. In planning discussions, “strengthening the trunk” usually implies concentrating service rather than simply adding trips everywhere.
Timed-transfer pulse
A pulse coordinates multiple routes to arrive at a transfer point within a defined window and depart shortly afterward. It is especially useful in lower-frequency networks, where missing a connection may mean waiting 30 or 60 minutes.
Pulse scheduling creates dependencies. One late route may be held to protect transfers, but holding too long can export delay across the network. The control policy therefore matters almost as much as the printed schedule.
Interlining
Interlining allows the same vehicle and often the same operator to continue from one route into another without returning to a garage or terminal. To passengers, the route number or destination may change while the vehicle remains in service.
It can reduce terminal time and deadhead, but it also couples route reliability. Delay on the first route becomes delay on the second. When practitioners suggest breaking an interline, they are often trying to stop one unreliable corridor from contaminating another.
Block and blocking
A block is the complete sequence of trips and non-revenue movements assigned to one vehicle during an operating day. Blocking is the process of assembling scheduled trips into those vehicle assignments.
A block may begin with pull-out from a garage, operate several routes through interlining, include deadhead movements, and finish with pull-in. Blocks describe vehicle work, not operator work. That distinction becomes important when the block runs for 18 hours but labor rules require several operators to cover it.
Deadhead
Deadhead is vehicle movement without carrying passengers, such as travel from a garage to the first trip, from one route to another, or back to the garage. It consumes labor, fuel or electricity, vehicle miles, and sometimes scarce roadway or track capacity, but it does not produce passenger service.
Newcomers often assume deadhead is waste that can simply be eliminated. Some can be reduced through better blocking or garage assignment, but a network cannot generally place every vehicle exactly where its first passenger trip begins.
Run cutting
Run cutting converts vehicle blocks into daily operator assignments while applying labor agreements, work rules, relief opportunities, report allowances, meal provisions, and maximum spread limits. The resulting operator assignments are called runs.
This is where a service plan encounters workforce reality. Two schedules with identical vehicle hours can have different labor costs because one produces clean runs and the other produces awkward fragments, overtime, or excessive split work.
Run, piece, split, and spread
A run is an operator’s scheduled work assignment. A piece is a continuous segment of platform work within that run. A split run contains two or more pieces separated by an unpaid or differently paid break, often to cover both commute peaks.
Spread is the elapsed time from the beginning of the first piece to the end of the last, not simply paid driving time. Labor agreements often limit spread or require a spread premium. A run that looks efficient in vehicle terms may be expensive or unattractive once spread rules are applied.
Relief point
A relief point is an approved location where one operator takes over a vehicle from another. It must be operationally practical and accessible to the relieving operator, often through a crew shuttle, transit connection, or nearby reporting location.
Poorly located relief points create paid travel time, missed reliefs, and service delay. When scheduling staff discuss relief-point feasibility, they are checking whether a mathematically valid run can actually be staffed on the street.
Pull-out and pull-in
Pull-out is a vehicle’s departure from the garage or yard to begin its assignment. Pull-in is its return after completing service. The terms can refer to the movement, the scheduled time, or the operational wave of vehicles entering and leaving a facility.
A missed pull-out usually means the first scheduled trip or an entire block is in jeopardy. Causes can include an unavailable operator, a failed vehicle, fueling or charging delay, or congestion within the facility itself.
Pick, signup, and paddle
A pick or signup is the periodic process through which operators select work assignments, days off, or reporting locations according to seniority and labor rules. Terminology varies by agency, and some organizations use signup for the entire schedule-change period and pick for the employee bidding event.
A paddle is the operator-facing work instruction showing trips, times, reliefs, deadhead, and other assignment details. If the public timetable and paddle disagree, operations will need to determine which artifact controls before the first bus leaves the garage.
Extraboard
The extraboard is a pool of operators assigned to cover absences, open runs, special work, and service disruptions rather than one regular run. Employees may report without knowing their final assignment until dispatch identifies the day’s vacancies.
An undersized extraboard leads to uncovered work and missed trips. An oversized one creates paid standby time. The required size is affected by absence rates, leave policies, training, vacancies, and how aggressively the agency schedules overtime.
Bus and BRT Operations
Bus rapid transit (BRT) and BRT creep
Bus rapid transit combines bus service with features intended to provide rail-like speed, capacity, reliability, and passenger experience. Typical elements include dedicated running ways, transit signal priority, substantial stations, level boarding, frequent service, and off-board fare collection.
BRT creep is practitioner shorthand for gradually removing those features during planning, design, or budget reduction until the project is essentially a conventional bus route with upgraded branding. The label is slightly impolite because it is often accurate.
Transit signal priority (TSP)
Transit signal priority modifies normal traffic-signal timing to benefit an approaching transit vehicle. Common treatments include extending a green phase, shortening a red phase, or inserting a special transit phase. Requests may be conditional on lateness, passenger load, route, or vehicle type.
TSP is not the same as emergency vehicle preemption. Priority works within defined signal constraints; preemption can interrupt the normal sequence. A corridor may have TSP equipment installed yet produce little benefit if requests are rarely granted or buses cannot reach the detection point.
Queue jump and BAT lane
A queue jump gives a bus a short dedicated lane and usually a special signal phase so it can move ahead of queued traffic at an intersection. A business access and transit lane, commonly called a BAT lane, is reserved for transit but permits vehicles to enter for turns or property access.
Both improve bus movement without creating a fully exclusive transitway. Their effectiveness depends heavily on enforcement, intersection design, and whether turning vehicles block the lane.
Center-running and curb-running
A center-running busway occupies the roadway median, while a curb-running lane places transit next to the sidewalk. Center-running designs generally avoid conflicts with parking, deliveries, and right turns, but require median stations and carefully designed pedestrian access.
Curb-running service provides simpler sidewalk access but is more exposed to loading activity and unauthorized vehicles. The running-way choice affects station design, vehicle door configuration, emergency access, and future convertibility, not just traffic performance.
Dwell time
Dwell time is the time a vehicle spends stopped for passengers to board and alight, including door operation and sometimes a small allowance for securing the vehicle. It is driven by passenger volume, fare-payment method, door availability, accessibility boardings, crowding, and platform design.
On a busy route, small dwell reductions compound across many stops. Level boarding, all-door boarding, and off-board fare collection are valuable because they attack dwell directly rather than merely increasing the vehicle’s top speed between stops.
Bunching
Bunching occurs when two or more buses that should be evenly spaced begin running close together. The leading bus encounters more passengers and longer dwell times, while the following bus encounters fewer passengers and catches up. The result is a self-reinforcing pattern.
Adding recovery time alone may not solve bunching on a high-frequency route. Active headway management, holding, stop-level interventions, and adequate running time are often required. Two buses arriving together are not “extra frequency” to the passenger who waited through the preceding gap.
Rail Systems and Operations
Consist and married pair
A consist is the set of rail vehicles coupled to form an operating train. A married pair consists of two cars designed to operate together because equipment or functions are distributed between them. Some fleets use larger semi-permanently coupled units.
A ten-car train does not necessarily provide ten independently interchangeable cars. Maintenance staff may have to remove an entire married pair or unit when one component fails, which changes how fleet availability should be interpreted.
Fixed-block, moving-block, and CBTC
Fixed-block signaling divides track into predetermined sections and controls train separation based on block occupancy. Moving-block systems calculate a continuously updated safe separation around each train rather than relying solely on fixed track sections.
Communications-based train control (CBTC) uses continuous or frequent data communication between trains and wayside systems to locate and control trains. CBTC often supports moving-block operation, but the terms are not perfect synonyms. Migration from legacy fixed-block signaling can create complex mixed-fleet and fallback operating conditions.
ATP, ATO, and ATS
Automatic train protection (ATP) enforces safe speeds, stopping limits, and movement authorities. Automatic train operation (ATO) controls functions such as acceleration, braking, and station stopping. Automatic train supervision (ATS) manages higher-level functions such as routing, dispatching, schedule regulation, and service recovery.
A line described as automated may still require an operator, and ATO does not replace ATP. Vendor terminology and grades of automation vary, so practitioners usually ask which functions are automated rather than accepting the label at face value.
Interlocking and route locking
An interlocking is a controlled arrangement of signals, switches, and related equipment that prevents conflicting train movements through junctions and crossovers. Route locking holds switches and signals in the required state after a route has been established.
An interlocking failure can reduce capacity far beyond the physical limits of the failed equipment because trains may need manual authorization, restricted speed, or alternate routing. “Trouble at the interlocking” is rarely a small sentence operationally.
Signal aspect, indication, and movement authority
A signal aspect is its displayed appearance, such as a color or light pattern. The indication is the operating instruction conveyed by that aspect. A movement authority is the permission and limit under which a train may proceed.
People sometimes use aspect and indication interchangeably, but technically the display and its meaning are different. In cab-signaled or CBTC territory, the movement authority may be presented primarily inside the cab rather than through a conventional wayside signal.
Traction power, OCS, and third rail
Traction power is the electrical supply used to propel trains. It may be delivered through an overhead contact system (OCS), including catenary or trolley wire, or through an electrified third rail. Traction power substations convert and distribute electricity along the line.
Loss of traction power may strand trains even when stations, communications, and some onboard systems still have power. Practitioners distinguish traction power from auxiliary or station power because the failure effects and restoration responsibilities differ.
Crossover, pocket track, and tail track
A crossover allows a train to move between parallel tracks. A pocket track is a short track, often between main tracks, used to store or turn trains without blocking through movements. A tail track extends beyond a terminal platform and can support reversing, storage, and safe stopping distance.
These features determine where trains can turn during normal service and disruptions. A map may show two tracks throughout a corridor, but sparse crossovers can make service recovery surprisingly inflexible.
Single tracking and slow orders
Single tracking routes trains in both directions over one track while the other track is unavailable for maintenance, construction, or an incident. It requires controlled windows or meets and usually reduces capacity.
A slow order is a temporary speed restriction imposed because of track condition, construction, weather, inspection findings, or another safety concern. Multiple small slow orders can materially increase running time and fleet requirements even when no segment is fully closed.
Service Control
Operations control center (OCC)
The operations control center is the central function that monitors service, communicates with operators, manages incidents, coordinates field resources, and authorizes service adjustments. Rail organizations may call it the rail control center, while bus agencies may use central dispatch or bus operations control.
The OCC does not merely observe the service. It may hold vehicles, short-turn trains, deploy gap vehicles, arrange bus bridges, manage traction-power isolation, and coordinate emergency response. Its authority boundaries are usually defined by operating rules.
CAD/AVL
Computer-aided dispatch and automatic vehicle location (CAD/AVL) combines vehicle location, schedule or headway status, communications, incident handling, and dispatch functions. AVL supplies the location data; CAD turns that information into an operational control environment.
Practitioners sometimes blame “AVL” for any discrepancy on the control screen, but the problem may lie in GPS, odometer logic, trip assignment, schedule data, communications, or the dispatch application. A dot on a map is the end of a long technical chain.
Schedule adherence and headway management
Schedule adherence compares actual operation with the published or internal timetable. Headway management focuses on maintaining even spacing between vehicles. The first is usually appropriate for lower-frequency service; the second often produces better passenger outcomes on frequent routes.
A controller may intentionally hold an on-time bus to correct an uneven headway. That makes the bus late by schedule-adherence standards while improving average waiting time. The two control objectives can therefore point in opposite directions.
Holding
Holding deliberately delays a vehicle at a terminal, timepoint, station, or stop to regulate spacing, protect a connection, or prevent an early departure. It may be directed by a controller or generated through automated decision support.
Holding is useful only when applied to the right vehicle for the right duration. Holding a heavily loaded leading bus while an empty follower sits behind it may satisfy an algorithm and irritate nearly everyone else.
Short turn
A short turn reverses a vehicle before its scheduled terminal so it can return toward the area of greater demand or restore service after a disruption. Rail short turns require suitable crossovers or turnback tracks; bus short turns require a feasible and safe loop or turnaround.
Short turning can close a gap quickly, but passengers traveling beyond the turn point must transfer or wait. Control centers therefore balance network recovery against the immediate passenger impact on the truncated trip.
Gap vehicle and run-as-directed
A gap vehicle is inserted into a large service gap to restore spacing. A run-as-directed (RAD) vehicle or operator is scheduled without a fixed public trip pattern and can be assigned where needed. Agencies use several local names for this flexible work.
RAD resources can cover crowding, delays, missed trips, or planned surges. Their value depends on where they are staged, how quickly they can enter service, and whether control staff have reliable information about the actual gap.
Bus bridge
A bus bridge is temporary bus service replacing an unavailable rail segment. It may connect adjacent stations, bypass a longer closure, or feed passengers to an alternate rail line. Agencies may also call it a shuttle bridge or rail-replacement service.
One train can carry several busloads, so replacement capacity is rarely one-for-one. The bridge also requires buses, operators, curb space, wayfinding, accessible boarding, and traffic control, usually on very short notice.
Fares and Revenue Collection
Fare media and fare product
Fare media is the credential or device used to demonstrate payment, such as a smartcard, mobile token, paper ticket, or contactless bank card. A fare product is the entitlement or rule attached to that medium, such as stored value, a day pass, a reduced fare, or a zone-based ticket.
The distinction matters in system design. The same card can hold several products, and the same product can be delivered through several media. Replacing the media does not automatically simplify the fare policy underneath it.
Account-based ticketing (ABT)
In account-based ticketing, the back office associates taps with an account and calculates the fare centrally. The card or token serves primarily as an identifier. In a card-based system, value and fare rights are stored or processed substantially on the card itself.
ABT supports fare capping, online account management, multiple linked credentials, and rule changes without rewriting every card. It also makes communications, transaction latency, identity management, and back-office availability more important.
Open-loop EMV
Open-loop payment allows passengers to use a general-purpose contactless payment credential, usually an EMV bank card or mobile wallet, directly at a transit validator or gate. Closed-loop systems require agency-issued media.
Accepting a bank-card tap is only the visible part. The system must handle tokenization, aggregation, denied lists, incomplete journeys, payment retries, inspection, concessions, and payment-card security. The validator may look simple because the complexity has moved elsewhere.
Fare capping
Fare capping limits what a passenger pays over a period. Once qualifying single fares reach the daily or monthly cap, additional covered travel is free or discounted. It provides pass-like economics without requiring the passenger to buy a pass in advance.
Caps depend on detailed rules covering transfers, modes, zones, reduced fares, and linked accounts. When practitioners ask whether trips “accumulate toward the cap,” they are testing fare-engine logic, not merely pricing.
Proof of payment (POP)
Proof of payment is a fare-control model in which passengers board without passing through a controlled gate and must present valid evidence of payment during inspection. It is common on light rail, streetcar, and some BRT services.
POP supports all-door boarding and lower station infrastructure, but it depends on inspection policy, validator placement, citation processes, and clear rules for mobile or contactless payments. A successful bank-card authorization after inspection is not necessarily proof that the passenger had paid before boarding.
Tap-on and tap-off
Tap-on records entry into the system; tap-off records exit. Systems with distance, zone, or operator-based fares often need both to calculate the final charge. Flat-fare systems may require only entry validation.
A missing tap-off may trigger a maximum fare or an incomplete-journey adjustment. Requiring exit taps improves fare precision but creates gate, accessibility, customer-service, and transaction-volume consequences.
Transfer window
A transfer window is the period during which a subsequent boarding receives a free or discounted transfer. Rules may depend on elapsed time, direction of travel, mode, agency, route, or whether the passenger returns to the same station.
Transfer policy influences network design because it determines the financial penalty for changing vehicles. In an account-based system, apparently simple language such as “free transfers for two hours” still needs precise treatment of when the clock starts and what counts as a valid transfer.
Clearing and revenue apportionment
Clearing reconciles fare transactions and financial obligations among participating agencies, payment processors, and mobility providers. Revenue apportionment determines how a shared fare is divided when a passenger uses multiple operators or services.
Regional integration can appear seamless to the passenger while creating complex settlement rules behind the scenes. Agencies care about journey attribution, transfer discounts, transaction fees, chargebacks, and whether the clearing formula reflects actual service provided.
Ridership and Service Metrics
Unlinked passenger trip (UPT) and linked trip
An unlinked passenger trip is one boarding of one transit vehicle. A passenger who transfers twice makes three UPTs. A linked trip represents the complete origin-to-destination journey regardless of transfers.
UPT is widely used in National Transit Database reporting and operational analysis because boardings are measurable. It can overstate customer journeys in a transfer-oriented network, so comparisons between network designs require care.
Vehicle revenue miles and vehicle revenue hours
Vehicle revenue miles (VRM) and vehicle revenue hours (VRH) measure vehicle operation while available for passenger service. Deadhead, training, maintenance testing, and other non-revenue movement are excluded under formal reporting definitions.
VRH is a common denominator for productivity and contracted-service pricing. Scheduled VRH, actual VRH, and reported VRH may differ because of missed trips, detours, special service, and reporting rules.
Passenger miles traveled (PMT)
Passenger miles traveled measures the aggregate distance traveled by passengers. Ten passengers each traveling five miles produce 50 passenger miles. Agencies often estimate PMT using surveys, automatic passenger counters, fare data, or statistical sampling.
PMT distinguishes a route carrying many short trips from one carrying fewer long trips. It is not interchangeable with boardings and is often less directly observed than UPT.
On-time performance (OTP)
On-time performance measures the share of trips or timepoint observations falling within an agency-defined window around the schedule. Bus windows frequently tolerate several minutes of lateness but little or no early departure. Rail definitions may focus on terminal arrival, departure, or completed trips.
OTP comparisons are unreliable unless the measurement point, window, weighting, and exclusions are known. A generous terminal-only definition and a strict all-timepoint definition can describe the same service very differently.
Excess wait time (EWT)
Excess wait time estimates how much longer passengers wait than they would under the scheduled or ideal service pattern. It is particularly useful for frequent service where passengers arrive without consulting a timetable.
EWT captures irregularity that average headway can conceal. A route averaging one bus every 10 minutes may still have poor EWT if buses repeatedly arrive in pairs followed by long gaps. Exact formulas vary, so the benchmark and passenger-arrival assumptions should always be checked.
Load factor and maximum load point
Load factor compares passengers onboard with a specified vehicle capacity. The denominator may be seated capacity, a planning capacity, or crush capacity, which produces very different interpretations.
The maximum load point is the location where passenger load is highest on a trip or route segment. Service planning generally focuses on that point rather than average load across the entire route, since empty outer segments can hide severe crowding in the core.
Boardings per revenue hour
This productivity measure divides passenger boardings by vehicle revenue hours. It is useful for comparing routes, periods, or service alternatives while accounting for the amount of service supplied.
High values can indicate strong utilization or serious crowding. Low values can indicate weak demand, but may also reflect a coverage obligation, low-density geography, late-night service, or an intentionally low-demand accessibility function. It is a diagnostic, not an automatic route-cancellation rule.
Missed trip and trip completion rate
A missed trip is a scheduled trip that does not operate according to the agency’s reporting criteria. The trip completion rate is the share of scheduled trips actually delivered. Definitions must address partial trips, very late departures, short turns, and substitutions.
A bus can appear in location data yet still count as a missed or partial trip if it enters service too late or skips a substantial segment. Contracted operators and agencies therefore negotiate classification rules carefully.
Farebox recovery ratio
The farebox recovery ratio compares passenger fare revenue with operating expense: passenger fare revenue / operating expense. It indicates how much of operating expense is covered directly by fares rather than taxes, grants, or other support.
Definitions vary concerning expenses, subsidies, special services, and accounting periods. A higher ratio does not necessarily mean a better service, especially where fare policy is designed around affordability or where public funding intentionally supports low-volume coverage.
Route miles, directional route miles, and track miles
Route mileage measures the extent of service alignment, but agencies may count unique alignment or mileage by direction. Directional route miles count each direction separately. Track miles count the physical tracks, so a two-track rail corridor has more track miles than route miles.
These measures answer different questions about network extent, service coverage, and infrastructure maintenance. Hearing “the system has 100 miles” should prompt the immediate question: 100 miles of what?
Fleet Maintenance and Transit Asset Management
Transit asset management (TAM) and state of good repair (SGR)
Transit asset management is the formal process for inventorying assets, assessing condition, managing lifecycle needs, and prioritizing investment. Under Federal Transit Administration requirements, covered agencies prepare TAM plans and report specified performance measures.
State of good repair means more than looking presentable. It concerns whether assets can safely and reliably perform their intended function and whether lifecycle investment needs are being addressed. An asset can operate today while still contributing to an SGR backlog.
Useful life benchmark (ULB)
A useful life benchmark is the expected age or usage at which an asset enters its replacement window for TAM performance measurement. Agencies may use default benchmarks or support their own based on operating environment, maintenance, and asset characteristics.
ULB is not an automatic retirement date. A vehicle beyond ULB may remain safe and serviceable, while a younger vehicle may require replacement because of condition, obsolescence, parts availability, or operating incompatibility.
TERM condition scale
The Transit Economic Requirements Model, or TERM, condition scale rates assets from 5, excellent, to 1, poor. The intermediate ratings are 4, good; 3, adequate; and 2, marginal.
The scale is used in condition assessment and federal asset-management reporting, particularly for facilities. A numerical condition score should not be confused with a detailed engineering inspection or a declaration that the asset is safe for continued operation.
Spare ratio
Spare ratio compares spare revenue vehicles with the number required for maximum service: spares / vehicles operated in maximum service. Spares cover preventive maintenance, failures, inspections, campaigns, and accident repair.
For larger federally supported bus fleets, FTA generally expects a spare ratio around 20 percent unless an exception is justified. Rail and specialized fleets may be treated differently. A low ratio can signal efficiency or fragility; the maintenance condition of the fleet decides which.
Mean distance between failures (MDBF)
Mean distance between failures divides fleet mileage by the number of qualifying failures over the period. Agencies may measure all failures, chargeable failures, service interruptions, or failures by subsystem.
MDBF is highly sensitive to classification rules. Excluding minor defects, passenger-caused incidents, or vendor-responsible failures can materially change the result. Comparisons are useful only when the failure definition and fleet mix are comparable.
Road call
A road call occurs when maintenance assistance is dispatched to a vehicle in service or when a defect causes service interruption, change-off, or removal. Agencies often classify calls as chargeable, non-chargeable, mechanical, operational, or no-defect-found.
A road call is not necessarily a catastrophic breakdown. A door fault, warning light, fare-equipment issue, wheelchair-ramp problem, or damaged mirror may be enough to remove a vehicle from service.
Preventive maintenance inspection and midlife overhaul
A preventive maintenance inspection (PMI) is scheduled maintenance performed at mileage, time, or operating-hour intervals. It includes inspection, servicing, adjustment, and replacement intended to prevent failures and maintain regulatory compliance.
A midlife overhaul is a larger planned intervention that renews selected systems partway through the vehicle’s expected life. It does not make the asset new or reset its chronological age, but it can restore reliability and defer replacement.
ZEB, BEB, and FCEB
A zero-emission bus (ZEB) produces no tailpipe emissions during operation. The principal categories are battery-electric buses (BEBs) and fuel-cell electric buses (FCEBs), usually using hydrogen.
ZEB conversion affects more than vehicle procurement. Agencies must reconsider block range, climate loads, fueling or charging infrastructure, facility power, technician skills, emergency procedures, utility coordination, and fleet spare requirements.
Depot charging and opportunity charging
Depot charging primarily charges battery buses at the garage, often overnight. Opportunity charging adds energy during service, commonly at terminals or selected layover points, using overhead conductive equipment or other high-power systems.
A block that fits within a diesel bus’s daily range may not be feasible for a BEB without charging or reassignment. Energy use depends on temperature, topography, passenger load, auxiliary systems, traffic, battery condition, and available recovery time.
Wheel truing, rail grinding, and the wheel-rail interface
Wheel truing machines a rail wheel back to the required profile and removes defects such as flats. Rail grinding restores rail profile, controls surface damage, and manages contact conditions. Together they address the wheel-rail interface, where vehicle and infrastructure performance meet.
Poor interface management can produce noise, vibration, accelerated wear, ride-quality problems, and safety concerns. Vehicle maintenance and track maintenance cannot treat the issue as belonging exclusively to the other department.
Capital Development
NEPA: CE, EA, and EIS
The National Environmental Policy Act process commonly uses three levels of review. A categorical exclusion (CE) applies where significant environmental effects are not expected. An environmental assessment (EA) determines whether significant impacts are likely and may conclude with a finding of no significant impact. An environmental impact statement (EIS) is the most extensive review and concludes with a record of decision.
These are not simply document sizes. The classification affects schedule, public engagement, technical analysis, alternatives development, and federal decision-making.
Capital Investment Grants: New Starts, Small Starts, and Core Capacity
The Federal Transit Administration’s Section 5309 Capital Investment Grants program funds qualifying major transit investments. New Starts generally covers larger fixed-guideway projects, Small Starts covers projects below specified cost and grant thresholds, and Core Capacity expands capacity on existing fixed-guideway corridors.
Projects move through defined development and rating processes. Entry into a program stage is not the same as receiving construction funding, a distinction that tends to become important immediately after a celebratory press release.
Project Development and Engineering
Project Development and Engineering are formal stages within parts of the Capital Investment Grants process. Project Development advances alternatives, environmental review, scope, cost, finance, and justification. Engineering develops the project to a level supporting dependable cost, schedule, risk, and implementation commitments.
The terms may sound like ordinary project phases, but within CIG they carry specific entry requirements, timelines, and federal decision points.
FFGA and SSGA
A Full Funding Grant Agreement (FFGA) is the federal funding commitment commonly used for qualifying New Starts and Core Capacity projects. A Small Starts Grant Agreement (SSGA) serves a similar role for Small Starts projects.
The agreement establishes the federal commitment, project scope, cost, schedule, and other conditions. The revenue service date and baseline cost in an agreement become particularly consequential when the project later seeks relief from schedule or budget pressure.
Project Management Oversight Contractor (PMOC)
A Project Management Oversight Contractor is an independent firm engaged by FTA to evaluate a major recipient’s project management, scope, cost, schedule, risk, technical capacity, and readiness. The PMOC reports to FTA rather than functioning as the agency’s project manager.
A PMOC concern may affect federal approvals, risk assumptions, contingency, or readiness to advance. “The PMOC has a question” often means the answer needs evidence, not another optimistic adjective.
Revenue service date and pre-revenue operations
The revenue service date (RSD) is the date passenger service is planned to begin. Before RSD, agencies conduct integrated testing, operator qualification, emergency exercises, schedule proving, simulated passenger operations, and other pre-revenue activities.
Substantial construction completion does not mean the system is ready for passengers. Software, procedures, training, spare parts, certificates, and operating discipline all have to work together before opening.
Safety and Security Certification Plan (SSCP)
An SSCP defines how a new or modified transit system will demonstrate that safety and security requirements have been satisfied before service begins. It identifies certifiable elements, verification activities, documentation, responsibilities, and open-item closure processes.
Certification is evidence-based and extends beyond inspecting the finished asset. Design reviews, test results, training records, procedures, hazard resolutions, and emergency coordination may all support the final certification.
Altoona bus testing
Buses purchased with qualifying federal assistance generally undergo testing at the federally designated Bus Research and Testing Center in Altoona, Pennsylvania. Testing addresses areas such as durability, reliability, maintainability, safety, structural integrity, noise, fuel economy, and emissions.
An Altoona report is not a substitute for agency acceptance testing or a guarantee of performance in local service. It is a standardized federal procurement requirement and an important source of technical evidence.
Buy America and pre-award or post-delivery audits
FTA Buy America requirements address domestic manufacturing, component content, and final assembly for federally funded procurements. Rolling-stock procurements also require pre-award and post-delivery reviews under separate certification and audit requirements.
The pre-award review tests whether the proposed procurement is compliant before contract award. The post-delivery review verifies the delivered vehicles and documentation. Practitioners distinguish FTA Buy America from other domestic-preference regimes because the governing rules and certifications are not interchangeable.
Safety and Regulatory Oversight
Public Transportation Agency Safety Plan (PTASP)
A Public Transportation Agency Safety Plan documents how a covered transit operator manages safety under FTA requirements. It includes safety objectives, responsibilities, performance targets, risk-management processes, assurance activities, and plan-review requirements.
The PTASP is not meant to sit apart from operations. It should connect executive accountability, hazard management, employee reporting, performance monitoring, and corrective action. If nobody outside the safety department recognizes it, the implementation probably has room to mature.
Safety Management System and Safety Risk Management
A Safety Management System (SMS) is the structured framework through which an agency manages safety. FTA’s model includes safety management policy, safety risk management, safety assurance, and safety promotion.
Safety Risk Management (SRM) is the component used to identify hazards, assess risk, and select mitigations. A risk matrix can support the process, but it does not replace engineering judgment, operational evidence, or accountable acceptance of residual risk.
State Safety Oversight Agency (SSOA)
An SSOA is the state-level body responsible for safety oversight of rail fixed-guideway public transportation systems not regulated by the Federal Railroad Administration. It reviews agency safety practices, conducts audits and investigations, and tracks corrective actions under federal requirements.
The transit agency operates the system; the SSOA independently oversees it. A finding from the SSOA is therefore not merely an internal recommendation and may require formal corrective-action tracking and closure evidence.
FTA jurisdiction and FRA jurisdiction
Most urban rail transit systems fall under FTA’s framework and state safety oversight. Commuter railroads and rail operations connected to the general railroad system commonly fall under Federal Railroad Administration rules. Some organizations operate services under both regimes.
The distinction affects operating rules, vehicle standards, employee qualifications, drug and alcohol requirements, accident reporting, positive train control, and oversight authority. “Rail” is not a sufficient regulatory classification.
Roadway Worker Protection (RWP)
Roadway Worker Protection comprises the rules, qualifications, communications, and physical protections used when employees or contractors work on or near active tracks. Protection methods can include exclusive track occupancy, watchpersons, flagging, foul-time procedures, and traction-power controls.
RWP terminology and authority vary between FTA-regulated transit rail and FRA-regulated railroads. Entering the right-of-way is not just a site-access issue; it is a controlled operating condition.
Hazard log
A hazard log is the controlled record of identified hazards, causes, consequences, risk assessments, mitigations, owners, verification evidence, and closure status. Capital projects and operating systems use it to maintain traceability throughout the lifecycle.
Closing a hazard does not mean proving that nothing bad can happen. It means the required mitigations have been implemented and verified, and any residual risk has been accepted at the appropriate level.
Reportable event
A reportable event is a safety occurrence that meets defined notification or reporting thresholds, such as a fatality, injury, collision, derailment, evacuation, or substantial property damage. FTA, FRA, the National Transit Database, the SSOA, and local authorities may apply different thresholds and timelines.
An event can be operationally serious without meeting a particular federal threshold, or reportable without being the most severe event the agency has experienced. The first question is therefore: reportable to whom, under which rule, and by what deadline?
49 CFR Part 655
Title 49 Code of Federal Regulations Part 655 establishes FTA drug and alcohol testing requirements for covered safety-sensitive transit employees. Testing categories include pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up testing.
Part 655 works alongside Department of Transportation procedures in Part 40. Whether an employee performs a safety-sensitive function matters more than whether the person’s job title sounds operational.
Security Sensitive Information (SSI)
Security Sensitive Information is protected transportation-security information governed by federal rules. It can include certain security plans, vulnerability assessments, system details, and threat information. SSI is not classified national-security information, but its distribution and handling are restricted.
Marking something SSI creates handling obligations; it is not a convenient label for any document the agency would prefer not to release. Procurement, records, technology, and security teams often need to coordinate its treatment.
Accessibility, Paratransit, and Service Equity
Complementary ADA paratransit and the three-quarter-mile corridor
Complementary paratransit is origin-to-destination service required for eligible individuals with disabilities who cannot use the fixed-route system under specified conditions. It complements eligible bus or rail service rather than functioning as a general-purpose demand-response program.
The basic service area generally extends three-quarters of a mile on either side of covered fixed routes, with associated treatment around route ends and core areas. Eligibility, service hours, and trip availability are tied to the corresponding fixed-route service.
Unconditional, conditional, and temporary eligibility
Unconditional eligibility applies when a person cannot use fixed-route service for covered trips generally. Conditional eligibility applies only under specified circumstances, such as inaccessible paths, certain weather conditions, or particular trip environments. Temporary eligibility applies for a limited period.
Eligibility is functional, not simply diagnosis-based. The question is what the applicant can do in the actual transit environment, not whether the applicant possesses a particular medical label.
Origin-to-destination service
ADA complementary paratransit must provide origin-to-destination service. An agency may use curb-to-curb service as its normal model, but it must provide additional assistance when needed for the passenger to complete the trip, unless doing so would fundamentally alter the service or create a direct threat.
Door-to-door assistance is therefore not necessarily a separate premium product. The required level of assistance depends on the passenger’s needs and the physical environment.
Next-day service and capacity constraints
Eligible paratransit trips must generally be reservable on a next-day basis during required booking hours. Agencies may negotiate pickup times within permitted limits, but they cannot require substantially earlier booking as a condition of service.
Prohibited capacity constraints include waiting lists, trip caps, and operational patterns such as substantial numbers of denials, very late trips, or excessively long rides. A reservations system that technically accepts requests can still violate the rule if service is routinely unavailable in practice.
Personal care attendant and companion
A personal care attendant (PCA) travels because the eligible passenger requires assistance. The PCA is not charged a fare. A companion accompanies the passenger socially and generally pays the same fare as the eligible rider.
At least one companion must be accommodated when properly reserved, while additional companions are carried if space is available. Correctly distinguishing PCA status from companion status affects capacity, fares, and booking.
Subscription service and no-show suspension
Subscription service provides recurring paratransit trips without requiring each trip to be booked separately. Federal rules limit how much capacity can be committed to subscriptions unless sufficient excess capacity remains for other riders.
A no-show suspension must address a pattern or practice of missed trips within the passenger’s control, not isolated events or agency-caused failures. Policies require notice and due process. The important phrase is “pattern or practice,” not “we counted three.”
Reasonable modification
A reasonable modification is a change to a transit policy, practice, or procedure needed to prevent discrimination based on disability. Examples may involve boarding locations, assistance, or treatment of mobility devices, depending on the circumstances.
An agency may deny a request if it would fundamentally alter the service, create a direct threat, be unnecessary for access, or impose an undue financial and administrative burden under the applicable standard. Denials require individualized analysis rather than a blanket policy shortcut.
Title VI service and fare equity analysis
Transit agencies receiving federal assistance establish policies defining major service changes and analyze qualifying service or fare changes under Title VI. The analysis examines effects on minority populations and, under agency policy, low-income populations before final action.
Agencies also adopt service standards and policies covering matters such as vehicle load, headway, on-time performance, service availability, vehicle assignment, and transit amenities. The purpose is to test how apparently neutral decisions affect protected communities.
Disparate impact and disproportionate burden
Disparate impact refers to adverse effects on minority populations that exceed the threshold in the agency’s Title VI policy. Disproportionate burden is the corresponding policy concept generally used for adverse effects on low-income populations.
The terms are related but not interchangeable, and the required justification frameworks differ. An analysis also needs a defensible baseline, affected population, impact measure, threshold, alternatives review, and mitigation discussion.
Transit Funding and Grant Administration
Sections 5307, 5310, 5311, 5337, and 5339
Transit professionals often refer to major federal formula programs only by section number. The numbers identify statutory funding programs, not accounting codes invented by the local finance department.
| Section | Common practitioner meaning |
|---|---|
5307 |
Urbanized Area Formula funding for eligible transit capital, planning, preventive maintenance, and certain operating purposes. |
5310 |
Enhanced Mobility of Seniors and Individuals with Disabilities funding. |
5311 |
Formula funding for rural public transportation. |
5337 |
State of Good Repair funding for qualifying high-intensity fixed-guideway and motorbus systems. |
5339 |
Bus and Bus Facilities funding, including formula and discretionary components. |
Eligibility, recipient status, matching share, and program conditions still need to be checked. Having money in a section does not mean every locally desirable expense fits that section.
Designated recipient, direct recipient, and subrecipient
A designated recipient is selected to receive and allocate certain federal transit funds in an urbanized area. A direct recipient receives assistance directly from FTA. A subrecipient receives federal assistance through another recipient.
The roles determine who applies, enters into federal agreements, conducts oversight, and bears responsibility for compliance. One agency can occupy different roles for different programs.
Apportionment, allocation, and obligation
An apportionment distributes formula funds according to statutory formulas. An allocation identifies funding for a recipient or project, often through a discretionary process. An obligation occurs when FTA formally commits funds through an approved grant.
Announcement is not obligation, and obligation is not expenditure. Agencies generally build and amend grants in the Transit Award Management System, commonly called TrAMS, before drawing eligible cash through federal payment systems.
Local match and transportation development credits
Most federal transit grants require a non-federal matching share, with the percentage depending on the program and activity. Transportation development credits (TDCs), historically called toll credits, can sometimes satisfy the matching-share requirement on paper.
TDCs are not cash. They can permit a project to use a higher effective federal share, but the recipient still needs enough actual funding to pay the total project cost.
Preventive maintenance as a capital expense
Federal transit rules allow eligible preventive maintenance to be treated as a capital expense for grant purposes even though it may resemble an operating expense in the agency’s financial statements. This can make formula funds available for recurring maintenance activities.
The treatment is funding-specific, not a declaration that every maintenance cost is capital under generally accepted accounting principles. Finance and grants staff may therefore classify the same expenditure differently for different reporting purposes.
National Transit Database (NTD)
The National Transit Database is the federal reporting system for transit financial, operating, asset, service, and safety information. Data from NTD supports oversight, public benchmarking, and the formulas used to apportion substantial federal funding.
NTD definitions control terms such as UPT, VRM, mode, directly operated service, and purchased transportation. Local dashboard definitions may be operationally useful but cannot simply replace the federal definitions in an NTD report.
Triennial Review
The Triennial Review is FTA’s periodic assessment of how an urbanized-area formula recipient complies with federal transit requirements. Review areas can include legal authority, financial management, procurement, maintenance, civil rights, drug and alcohol programs, and grant administration.
A finding requires corrective action and evidence of closure. Although the review occurs every three years, agencies generally manage readiness continuously because the underlying obligations apply throughout the grant lifecycle.
Contracted Transit Services
Directly operated and purchased transportation
Directly operated (DO) service is provided using personnel employed by the reporting transit agency. Purchased transportation (PT) is operated by a separate entity under a contractual arrangement. These are formal NTD service classifications.
Owning the vehicles does not necessarily make the service directly operated, and contracting only maintenance does not necessarily make it purchased transportation. The determining issue is who operates the service and employs the operating workforce under the reporting rules.
Gross-cost and net-cost contracts
Under a gross-cost contract, the authority generally retains fare revenue and pays the operator according to agreed service-production terms. Under a net-cost contract, the operator’s compensation incorporates fare revenue, transferring more demand or revenue risk to the operator.
Gross-cost structures are more common where the agency controls fares, schedules, and network policy. Net-cost structures can create ridership incentives, but only if the operator has meaningful control over the factors that produce ridership.
Revenue-hour pricing
Contracted bus and paratransit service is frequently priced per vehicle revenue hour, sometimes with separate rates for revenue miles, deadhead, peak vehicles, dispatch, facilities, fuel, or special vehicle classes. The definition of a billable hour is therefore commercially important.
A lower hourly rate does not automatically mean a lower total cost. Minimum-hour guarantees, deadhead treatment, overtime assumptions, fleet responsibilities, and service-change provisions can matter more than the headline rate.
Paratransit brokerage and dedicated versus non-dedicated service
A paratransit broker accepts trip requests, schedules or assigns trips, manages providers, and reconciles service and payment. Dedicated service uses vehicles and operators reserved for the program. Non-dedicated service purchases trips from taxis, transportation network companies, or other providers serving additional markets.
Non-dedicated capacity can lower unit cost and improve flexibility, but the agency still retains responsibility for ADA compliance, driver qualifications, vehicle suitability, data integrity, and customer outcomes.
Passenger Information and Mobility Integration
GTFS
The General Transit Feed Specification, or GTFS, is the widely used data format for publishing scheduled transit service. Core files describe stops, routes, trips, stop times, calendars, fares, and related relationships.
A feed can be technically valid yet still mislead passengers through incorrect stop locations, calendar exceptions, destination labels, or trip relationships. GTFS is a passenger-information product, not merely an export from the scheduling system.
GTFS Realtime
GTFS Realtime supplements the static schedule with three principal entity types: TripUpdates, VehiclePositions, and Alerts. These support predicted arrivals, vehicle tracking, cancellations, detours, and service messages.
Realtime quality depends on correct matching to static trips, current timestamps, sensible prediction logic, and disciplined incident entry. Stale realtime data can be worse than no realtime data because it looks authoritative.
Real-time passenger information (RTPI)
Real-time passenger information presents predicted arrivals, departures, disruptions, and vehicle locations through signs, apps, websites, announcements, and third-party platforms. Predictions may come from AVL data, schedules, dispatch actions, and historical running patterns.
“Real time” usually means frequently updated prediction, not perfect knowledge. During severe disruption, a precise-looking countdown may simply be a schedule wearing a digital costume.
Headsign and sign code
A headsign is the passenger-facing destination or service message displayed on a vehicle. A sign code is the internal code used by operators or onboard systems to select that display, often along with announcements and route configuration.
Headsigns should describe where the vehicle is going in terms passengers understand, which may differ from the internal route pattern or terminal name. Incorrect sign-code mapping can send a correctly operated trip out with the wrong public identity.
Automatic passenger counter (APC)
An automatic passenger counter records boardings and alightings, usually through door-mounted infrared, stereoscopic, or other sensors. When combined with stop and trip data, APC records support ridership, load, dwell, and service-planning analysis.
APC totals require validation for sensor error, door events, trip matching, and missing data. The resulting passenger load is calculated from accumulated boardings and alightings, so small counting errors can persist across several stops.
Microtransit
Microtransit is technology-enabled demand-responsive shared transportation, usually operating within a zone or between designated points. Passengers request trips dynamically, and routing software groups compatible journeys.
Agencies use it for low-density coverage, first-mile and last-mile access, late-night service, or replacement of weak fixed routes. Performance depends on service-area geometry, promised wait time, pooling efficiency, accessibility, and how many vehicles are available at once.
Mobility as a Service and first-mile or last-mile integration
Mobility as a Service (MaaS) integrates information, trip planning, booking, and sometimes payment across public transit and other modes. First-mile or last-mile programs connect passengers between transit and origins or destinations that are difficult to reach by fixed route.
Integration can involve bikeshare, scooters, microtransit, taxis, or transportation network companies. Agencies need to distinguish a trip-planning partnership from true fare, account, operations, and customer-support integration.
The Phrase Translator
“We can save the cycle with a short turn, but we’ll open a gap outbound.”
It may mean: Turning one vehicle early can restore service in one direction, but passengers beyond the turn point or traveling the other way will experience a larger interval. The proposed cure moves part of the problem rather than eliminating it.
“The route is scheduled at ten, but the observed headways are three and seventeen.”
It may mean: The published frequency is six buses per hour, but bunching is giving passengers alternating pairs and long gaps. Average service quantity is not the immediate problem; regularity is.
“That is an AVL OTP issue, not necessarily a running-time issue.”
It may mean: The route appears late in the dashboard, but the underlying cause may be bad trip matching, location data, or timepoint logic rather than an inadequate schedule. Check the measurement before adding minutes.
“The service change adds one peak block, so check the spare ratio.”
It may mean: The timetable needs another vehicle at the busiest moment, and the agency may not have enough fleet capacity to add it while preserving maintenance spares. One scheduled bus can become a multi-vehicle procurement question.
“That block works on diesel, but it does not pencil for a BEB in winter.”
It may mean: The block’s mileage, deadhead, heating load, terrain, or layover leaves insufficient battery range or charging opportunity under cold-weather assumptions. The schedule must change, the charging plan must change, or another vehicle must cover it.
“We’re under a slow order through the interlocking.”
It may mean: Trains must reduce speed through a strategically important track area, likely increasing running time and constraining throughput. Even a short restriction can create line-wide delay if trains cannot clear the junction quickly.
“We’ll single-track to the crossover and bus bridge the outer segment.”
It may mean: Rail service will continue at reduced capacity over part of the line, trains will reverse where track geometry permits, and buses will replace service beyond that point. Several operational plans now have to behave like one coherent plan.
“The validators support ABT, but they are not open-loop yet.”
It may mean: Fares are calculated in a central account-based back office, but passengers still need agency-issued credentials. Direct tapping with a bank card or mobile wallet has not been enabled or certified.
“Those are UPTs, not linked trips.”
It may mean: The number counts boardings, so transferring passengers appear more than once. Do not interpret it as the number of people or complete journeys without further analysis.
“Part 37 requires next-day service; the broker cannot solve this with a waitlist.”
It may mean: The paratransit provider is facing a capacity problem, but delaying reservations or placing eligible riders on a waiting list is not an acceptable compliance strategy.
“This crosses our major-service-change threshold, so Title VI has to run before board action.”
It may mean: The proposal is large enough under agency policy to require a formal service-equity analysis before final approval. Public outreach alone does not substitute for the analysis.
“The 5337 funds are apportioned, not obligated.”
It may mean: Formula funding is legally available to the area or recipient, but it has not yet been committed through an approved federal grant. It should not be treated as immediately drawable project cash.
“The GTFS feed validates, but the TripUpdates are stale.”
It may mean: The scheduled-service files pass structural checks, but the realtime predictions are old or no longer refreshing. Journey planners may therefore present formally valid and operationally useless information.
Net Net
Public transit language is difficult because a single service depends on network planning, vehicle and crew scheduling, regulated operations, safety engineering, civil-rights obligations, asset condition, federal grants, and passenger technology. The same word can also have one local meaning, one contractual meaning, and a different NTD definition.
When a term or conclusion is unclear, useful questions include:
- Are we discussing scheduled service, actual service delivered, or federally reported service?
- Is the unit a trip, boarding, linked journey, revenue hour, block, run, route mile, or track mile?
- Does this service operate to a timetable, or is it controlled primarily by headway?
- Is the constraint running time, recovery time, cycle time, operator work rules, fleet availability, or charging capacity?
- Which failure or missed-trip classification is being applied, and what events are excluded?
- Is this asset beyond its ULB, below a condition threshold, or actually unsafe or unavailable?
- Does FTA, FRA, the SSOA, the ADA, Title VI, or a local operating rule control the decision?
- Are the funds apportioned, allocated, obligated, or already eligible for drawdown?
- Is the service directly operated or purchased transportation, and who retains revenue and production risk?
- What evidence supports the conclusion: AVL, APC, fare transactions, inspection findings, test results, or operator reports?
- What operating authority must approve the next step, and what must be verified before normal service resumes?
- Which assumption, such as headway, load standard, battery range, eligibility condition, or opening date, would materially change the answer?
Real fluency does not come from memorizing every acronym. It comes from recognizing whether the conversation is about service, vehicles, people, infrastructure, regulation, or money, then asking the question that exposes the controlling definition.