Study NRS material by tracing each scenario through the train control chain: signal or cab display, interlocking, train detection, and timetable constraints. Identify which constraint binds the situation, compare the named technologies by their headway logic, and practice degraded-mode reasoning and documentation on paper before attempting mixed case questions.
Trace the train control chain before answering any movement question
Every movement scenario rests on a chain: the signal or cab display, the interlocking that locks the route, and the train detection that proves a section is clear. Name each link before reasoning.
Learn these terms as links, not as a vocabulary list. A signal aspect tells a driver what may be done. A route is the locked path between two points, set and held by an interlocking that prevents conflicting routes from being established at the same time. Train detection, typically a track circuit or an axle counter, reports whether a section is occupied or clear. Occupancy is the state on which a movement scenario can turn.
Apply the chain as a tracing habit. When a prompt says a signal is at danger or a section is occupied, ask two questions: which link produced this information, and what can that link actually prove? A signal shows what the interlocking has permitted, not what is physically on the track; detection proves presence or, within its design limits, absence of axles. An answer that quotes the right term but skips this tracing step can end up assigning properties to the wrong link.
- Signal aspect: what the driver is authorized to do.
- Interlocking: enforces that conflicting routes cannot be set simultaneously.
- Train detection: reports occupancy; it does not authorize anything.
- Tracing question: which link generated this fact, and what does it prove?
Fixed block versus moving block: identify the headway logic a scenario assumes
A capacity or headway scenario can hinge on which block logic it assumes. Fixed block spaces trains by physical sections; moving block spaces them by a computed braking envelope. Identify it explicitly in your answer.
In fixed block operation, the line is divided into sections, and a following train must keep a full clear section plus margins between it and the train ahead. Headway therefore depends on section length, line speed, and train length. In moving block concepts, spacing is computed continuously from reported position and braking characteristics, so the section structure stops being the limiting factor and safe braking distance plus margin becomes the driver of separation.
The comparison matters for application, not just recall. If a scenario describes upgrading a busy line and quotes new section lengths, it is inviting a fixed-block headway calculation. If it describes continuous position reporting and removes wayside signals, it is inviting a braking-envelope argument. Stating the assumed logic in one sentence, then calculating under it, is what turns a descriptive answer into a decision answer.
| Feature | Fixed block | Moving block |
|---|---|---|
| Division of the line | Physical sections with boundaries | No fixed section boundaries; virtual spacing |
| Train detection role | Proves each section occupied or clear | Reports train position to the control system |
| What sets minimum headway | Section length, line speed, train length | Safe braking distance plus margin, plus reporting accuracy |
| Main capacity lever | Shorter sections or higher speeds | More accurate position and braking data |
| Degraded consideration | Failed detection treated conservatively per section | Loss of position reporting or communication forces fallback |
Worked scenario: the capacity trap when consolidating freight trains
A freight operator proposes replacing several shorter trains with fewer, longer ones to free paths. The tempting answer is that fewer trains always means more capacity. The correct move is to find the binding constraint first.
Simplified teaching example, with invented round numbers: on a fixed-block line, minimum headway distance is roughly the block section plus train length plus a fixed margin of 300 m, taken at 25 m/s. With a 1500 m section, a 300 m freight consumes 2100 m, about 84 seconds of headway; a 900 m freight consumes 2700 m, about 108 seconds. Two long freights cost about 216 seconds; three short ones cost about 252 seconds. Consolidation helps, saving about 36 seconds of headway, but far less than the count of trains suggests.
The mistake a plausible answer would make is stopping there. Suppose the same line carries a frequent passenger service whose own headway, set by its braking distance and length, is 120 seconds. That passenger headway is the binding constraint: it caps how many paths of any length exist. The 36-second freight saving is only 36/120, about three-tenths of one passenger path, and less than a full path in any case. A plan built on the freight arithmetic alone will overpromise. The better decision is to state both computations, name the passenger headway as binding, and quantify the freight saving honestly.
Why it matters: capacity reasoning in this subject is fundamentally about which limit binds first. A decision that optimizes a non-binding quantity reads as confident and is wrong. Turn this into a habit: after any capacity calculation, write one sentence naming the binding constraint and one sentence testing whether your proposed change affects it.
Gradient, adhesion, and braking distance: convert geometry into timing
Geometry facts in a scenario are inputs, not decoration. A ruling gradient changes adhesion, braking, and running time. Practice converting each geometric detail into a timing or braking consequence before you answer.
Fix the named concepts and how they differ. Ruling gradient is the steepest sustained gradient on a route, and it sets what a locomotive can haul at line speed. Adhesion is the friction available between wheel and rail; it falls on wet or contaminated rail, which lengthens stopping distance. Braking distance is the distance needed to stop from a given speed under service braking, and it grows with the square of speed in simplified models. These are three distinct effects that often appear together.
Application looks like this: if a scenario places a descending gradient before a station with a speed restriction, work the chain downward, speed into the restriction, braking distance at that speed, adhesion adjustment for stated conditions, and the additional running time. Then ask what decision the scenario wants: an operating speed, a needed margin, or a feasible stopping point. Each demands the same conversion but a different conclusion.
- Ruling gradient: limits what can be hauled at line speed.
- Adhesion: falls on wet or contaminated rail, lengthening stopping distance.
- Braking distance: grows with the square of speed in simplified models.
- Exercise: compute stopping distance at three speeds under a stated simplified braking rule, repeat with a stated adhesion reduction, and note which concept the change is attributed to.
Worked scenario: degraded working when train detection fails
A track circuit section reads occupied with no train in it. The plausible error is to plan around the fault casually. The sound decision is to treat it as loss of train detection and apply formal degraded procedure on paper.
Paper scenario: a dispatcher's panel shows a section occupied, the signaller confirms no train was scheduled there, and maintenance suspects a failed track circuit. The tempting answer is to confirm by phone that the section looks clear and let trains proceed, since the panel is presumably wrong. That answer assigns a capability the system no longer has: with detection failed, the system cannot prove vacancy, so the conservative convention used in this exercise is to treat the failed section as occupied until it is proven clear by an agreed inspection process.
The better decision works in three labeled steps. First, classify: this is loss of train detection, not merely a display fault, so the whole section's status is unproven. Second, restrict: under the documented degraded procedure for the network in the scenario, movements are governed by a written authority, following trains are not allowed into the affected section, and the block is worked manually until vacancy is established. Third, document: record the time, the affected section, the procedure invoked, and the authorities issued. A complete paper answer names all three steps; a weak one names only the fault.
Why it matters: degraded-mode questions test whether you understand what each system link normally guarantees, because only then can you say what is lost when it fails. Keep such exercises strictly on paper; the learning objective is the classification-and-restriction reasoning, not any real-world operating instruction, which always belongs to the network's own rulebook.
Build a timetable graph for a single-track line: exercise and rubric
Single-track working forces every conflict to be resolved at a crossing loop, which makes it the cleanest practice ground for capacity reasoning. Draw a time-distance graph, then audit it against the rubric below.
Suggested exercise with invented numbers: take a line A to C with a crossing loop at M, the midpoint. Two trains, one up and one down, each take 30 minutes end to end. Schedule them 20 minutes apart in opposite directions, so the down train departs 20 minutes after the up train. Plot both on a time-distance graph, mark where their lines would cross if both ran unimpeded, and then resolve the conflict at the loop M. Add a third train departing A 10 minutes behind the first up train and find where the new conflict appears.
Expected observations: with a 20-minute offset and 30-minute end-to-end runs, the unimpeded lines cross at 25 minutes after the first departure, about five-sixths of the way along from A, well past the midpoint loop at M. The graph therefore resolves the conflict by holding the up train at M: it arrives there 15 minutes after departure and must wait until the down train passes M at 35 minutes, drawn as a horizontal segment of 20 minutes. The third train, departing 10 minutes behind, reaches the M area just as the first up train leaves; whether it fits behind depends on the headway you accept in the section beyond M. If the gap is too tight, the graph shows it waiting at M, which extends loop occupancy. Read the exact waiting times from your plot rather than assuming them.
- Plot time on the horizontal axis, distance on the vertical.
- A train waiting at a loop appears as a horizontal line segment.
- Every mid-section crossing on your graph is an unresolved conflict.
- End by naming the binding constraint in one written sentence.
Documentation habits and an adaptable six-step preparation sequence
Case answers earn their weight through documentation: what was observed, what was classified, what restriction applied, and what was recorded. Build a writing template, then follow a sequence that layers concepts before mixed scenarios.
Draft a four-field note template and use it in every scenario from now on: observed facts, classification, restriction or decision, and record made. Applying it to the two worked scenarios above, the degraded-mode case fills all four fields naturally, while the capacity case fills them with the binding-constraint statement and the quantified proposal. Practicing with a fixed structure makes gaps obvious: a scenario where you cannot fill the classification field means the underlying concept needs another pass.
An adaptable preparation sequence, adjustable to the time you have: first, build a glossary of the named system links and technologies from this guide and mark how each differs from its neighbor. Second, practice tracing movements on diagrams until the chain is automatic. Third, work small headway and braking calculations with clearly labeled simplified numbers. Fourth, drill degraded-mode classification on paper. Fifth, build the timetable graph exercise and score it against the rubric. Sixth, mix everything in case-style scenarios and write the four-field note each time. Score the graph rubric from 0 to 2 per item; 8 or more suggests readiness to move on, below that rework the plotting. Treat these as learning milestones for your own review, not as predictions of any result.
- Template fields: observed facts, classification, restriction or decision, record made.
- Sequence order: glossary, tracing, calculations, degraded drills, graph building, mixed cases.
- A gap in the classification field points to the exact concept to reread.
- Note: administrative details such as format and registration belong to the issuing organization's official pages, not to this guide.