Underground Mine Rail Traffic Management: A Block, Authority and Communication Plan

Where does the traffic-management boundary begin and end?

Define the controlled railway before choosing signals or software. Include main lines, sidings, loops, loading and discharge stations, workshops, charging or trolley-power areas, crossings, doors, shafts, refuge points, pedestrian access and every interface where another vehicle can enter. Give each route element a stable identifier that is used on drawings, signs, displays, permits, radio calls and event records. A system cannot protect an unnamed turnout or a temporary connection that is absent from its map.

List every movement class: loaded and empty production trains, personnel trains, supply cars, maintenance vehicles, shunting, rescue equipment and people working on or near the track. Record maximum authorized consist and direction by route only after separate traction and braking approval. The traffic plan controls compatible occupancy; it does not calculate whether the train can start, fit, stop or hold on the route.

How should blocks and movement authority work?

A block is useful only when its boundaries can be recognized underground and its occupancy can be determined to the confidence required by the operating rule. Fixed blocks may follow signals, switches, stations and single-track constraints. Smaller blocks can improve flow but increase detection, communications, logic and maintenance demands. The longest train, stopping case and overlap assumptions must be considered by competent designers; do not copy a block length from another mine.

Define the complete authority lifecycle: request, route check, switch proof, conflicting-authority exclusion, issue, operator acknowledgement, entry, occupancy monitoring, exit confirmation, release and cancellation. State whether authority is verbal, written, signalled or enforced by control logic. A green indication should never be interpreted without its documented meaning and failure behavior. MSHA's underground powered-haulage material identifies dispatchers and block-light systems as traffic-regulation methods in its US context, while leaving the mine responsible for a workable policy.

1. Identify every route conflict and define a visible block boundary.
2. Assign one accountable authority source for each operating mode.
3. Prove route availability, train clearance and switch position before issue.
4. Require a standardized acknowledgement before the train enters.
5. Release the route only from positive evidence, not elapsed time alone.
6. Record overrides, cancellations and uncertain states for review.

What location and train-integrity information is required?

Specify information from the decisions it supports. The dispatcher may need train identity, direction, block occupancy, last confirmed point, consist class and communication health. An automated interlock may also require switch detection, route locking and a quality or confidence state. Do not publish a universal positioning accuracy: the necessary performance depends on block boundaries, vehicle dimensions, route geometry, operating speed and the approved protection concept.

Location of the lead locomotive is not automatically proof that the complete train has cleared a conflict. Define how the last vehicle, split consist, detached car or failed tag is handled. Reconcile electronic status with operating reports and provide a method to establish a known position after maintenance, power loss or database restart. The South African rail-bound equipment guideline treats locomotive, rolling stock and the complete coupled train as related system entities; its jurisdictional scope must remain explicit.

How should traffic communications be designed?

Create a message dictionary before selecting the bearer. Define call signs, route and block names, standard request and repeat-back wording, emergency priority, lost-message handling and the record that proves authority. Separate safety-critical movement messages from production coordination, video and maintenance traffic. Train operators, dispatchers, loading crews and track workers should use the same controlled vocabulary so that a successful radio connection does not still produce an ambiguous instruction.

Survey coverage under representative mine conditions and identify interference, shadow areas, power dependencies and equipment damage scenarios. NIOSH material explains that underground communication performance depends on mine geometry and infrastructure and that hardwired and wireless systems have different failure modes. Provide an independent or suitably separated fallback where the risk assessment requires it. If both channels share the same power supply, cable route or control server, they may not be credible redundancy.

Engineering note: Scope boundary: communication technology supports authority; it does not create authority by itself. The mine's approved rules determine who may move, stop, isolate and restore the railway.

How are pedestrians, work parties and temporary changes protected?

Map normal pedestrian crossings, boarding points, workshops and places where people must approach cars, switches or trolley infrastructure. Define physical segregation, warning, access permission and a protected work-block process. A person working inside a route needs a positive protection that cannot be removed by an ordinary production instruction. Include contractors and infrequent tasks; unfamiliar personnel are especially vulnerable to local signal conventions.

Temporary track, blocked routes, construction interfaces and changed traffic direction require a controlled map and rule update before use. Specify who installs and verifies temporary signs, stops, switch locks and communication equipment, how the dispatcher display is changed, and how all affected operators are briefed. NIOSH identifies confined spaces and proximity to moving machinery as important powered-haulage concerns, but the exact controls and access distances remain project-specific.

Which degraded modes must be written and tested?

Create a response for lost communications, uncertain train location, unproved switch, failed signal, unavailable dispatcher, power interruption, obstructed route, split train, stalled consist, emergency access and conflicting database state. For each event state detection, immediate stop or permitted movement, protection applied, communication path, responsible authority, recovery evidence and conditions for returning to normal. A generic instruction to proceed cautiously is not a complete degraded mode.

Keep capacity pressure out of the safety decision. A fallback may reduce the network to one train, one block or escorted movements, and the capacity model should represent that reduction rather than encourage an informal workaround. Test degraded procedures during commissioning and drills using a controlled scenario. Capture alarms, voice or message records, switch and occupancy states, operator decisions and recovery time so the plan can be improved without relying on memory.

What should commissioning and acceptance demonstrate?

Trace each rule and interface to a test. Begin with static checks of map identifiers, signs, switch indications, signals, permissions and communication paths. Then run controlled normal movements, opposing requests, following trains, shunting and work-block scenarios. Inject credible failures without exposing people to uncontrolled movement. Confirm that conflicting authority is prevented, alarms are understandable and restoration requires the expected evidence.

Acceptance records should identify software and map version, vehicle and consist, route, test personnel, instruments where used, initial conditions, expected result, observed event sequence, deviations and approval. The Western Australian historical regulation is a useful example of requiring a mine rail-haulage plan containing layout, operating, maintenance and safety information; it is not a universal legal template. Use the project's current jurisdiction and mine rules.

What should a traffic-management RFQ contain?

Give suppliers the surveyed route and interfaces, movement classes, train formations, operating concept, existing signals and communications, mine network constraints, applicable rules, availability target and required degraded modes. Ask for a requirements-to-function matrix, architecture, coverage method, block and switch logic, cybersecurity and remote-access boundary, event data, maintenance tools, training and staged acceptance plan. Require exclusions and dependencies to be visible.

Compare proposals on controlled outcomes, not the number of dashboard features. Confirm ownership of route data, configurations, event history, backups and diagnostic access. State who maintains field devices and who is authorized to change map or logic. ShaoLi's underground control-system pages can support an initial configuration discussion; final traffic rules, risk decisions and authorization remain with the mine and competent project parties.

• Controlled route, asset and conflict-zone map.
• Movement classes, authority roles and message dictionary.
• Detection, switch, signal and communication requirements.
• Normal, worksite, degraded and emergency scenarios.
• FAT, site integration, acceptance and lifecycle evidence plan.