Mining Locomotive Tractive Effort: Route Inputs for a Defensible Haulage Review

TL;DR: what decision does the route-input package support?

Use one version-controlled package to decide whether a supplier or project engineer has enough evidence to review a proposed locomotive and consist. The package should make the worst credible movement visible: direction of travel, train formation, payload state, route section, grade, curvature, track condition, operating restriction and braking basis. A general statement such as 'underground haulage' is not enough because the ruling section may govern the answer.

The output is a review boundary, not a promised capacity. A supplier may need more information about wheel arrangement, motor/control characteristics, power source, couplers, brake equipment, local rules and acceptance method. If a field is unknown, label it unknown and assign an owner. Filling an unknown with an optimistic estimate can make a proposal appear suitable when the project has not yet established the condition that matters.

Build a route register before asking for traction numbers

Divide the planned movement into identifiable route sections instead of relying on one mine-wide distance. For each section, preserve the alignment drawing or survey source, direction, elevation change, maximum local gradient, curve and turnout locations, rail section, gauge, clearances, drainage condition, crossings, loading and discharge interfaces, work zones and temporary restrictions. Capture the date and method behind every observation. A route can change after rehabilitation, development, water ingress or a new passing point; the register needs a change trigger.

Mark the ruling case explicitly. It may be a loaded ascent, a constrained curve, a turnout with a lower speed, a wet location or a recovery move rather than the longest section. HSE's underground locomotive-haulage guidance treats haulage as a system of route, rolling stock, operation and control rather than an isolated vehicle choice. That is why a route sheet must travel with the train and duty record into engineering review. It also lets procurement ask suppliers to state which assumptions their proposal uses.

Describe the train and duty in both directions

Record the locomotive configuration and the complete consist separately. The train record should identify each car type, tare mass, approved payload or passenger duty, expected gross mass, coupler arrangement, brake participation, wheel condition and any item that changes the formation. Do not merge a nominal car capacity into a total train mass without checking material density, loading method and actual distribution. A different payload or added service car can change the governing movement.

Then map a duty cycle: loading, acceleration, travel, waiting, discharge, empty return, charging or power transitions, maintenance and credible degraded modes. State how many movements are expected and whether the route, load or timetable changes by shift. This does not create a capacity model; it provides the operating context for a traction review. For a broader production bottleneck study, use the related rail-haulage capacity planning guide, which keeps cycle queues separate from the route resistance question addressed here.

• Identify the exact locomotive, power arrangement and fitted revisions proposed for review.
• List each vehicle in the proposed consist and distinguish tare, payload and gross mass.
• State loaded and empty directions, normal and exceptional formation, and any permitted recovery mode.
• Record operating speed restrictions, stopping points, crossings, turnout moves and worksite interfaces.
• Attach the source and date for every mass, route and duty assumption; flag unverified values.

Why traction, adhesion and resistance are not one catalogue field

A review normally distinguishes force available at the wheel, force that can be transmitted through the wheel–rail interface, and resistance imposed by the train and route. Grade, curves, rolling condition and acceleration demand affect the resistance side. Wheel loading, rail condition, contamination, moisture, sanding arrangements where approved and operating controls affect the adhesion side. Motor and control characteristics influence how force is delivered across speed. These relationships require the actual vehicle and route data; this article intentionally supplies no universal coefficient or tonnage figure.

Supplier data can still be useful when it is kept in scope. Schalke publishes configuration-specific mining-locomotive information, and Brookville presents different underground mining rail vehicle families; neither supplier's stated values can be transferred to a ShaoLi configuration or an unreviewed route. Ask every bidder to identify the exact model, configuration, test or calculation basis, ambient and route assumptions, exclusions and the meaning of any traction value. Similar dimensions or a shared power label do not make values interchangeable.

Keep braking and train control as independent release gates

A train that can start is not automatically a train that can be held, stopped or recovered. Braking review needs the approved consist, worst route direction, speed, brake distribution, brake condition, coupler forces, response behaviour, stopping or holding criterion, failure modes and the mine's authority to release the movement. It must use the same route and mass assumptions as the traction review. Do not backfill a missing brake case with a tractive-effort statement.

HSE's Mines06 guidance addresses rail track and associated underground mine equipment, including the need for suitable inspection and maintenance arrangements. It is a United Kingdom guidance source, not a substitute for the mine's jurisdiction, risk assessment or approved test method. Use the published brake-testing guide for the evidence layers that follow a configuration decision. Until the site identifies its acceptance authority and criteria, describe braking status as unresolved rather than approved.

Engineering note: Boundary: this is a data-preparation guide. Only the responsible project process can determine calculations, operating limits, brake tests and release authority.

A five-gate route-input workflow

This workflow is deliberately sequenced so a missing route fact is found before it becomes a supplier assumption. It is an original planning flow for the evidence package, not an operating procedure. Each gate should retain the input source, reviewer, date, open issues and the condition that triggers a refresh. Project drawings, local rules, risk controls and approved test procedures take precedence at every gate.

1. Freeze the requested movement: route direction, consist, payload state, duty and proposed locomotive configuration.
2. Survey and register route sections: grade, curves, turnouts, gauge, rail condition, clearance, drainage and restrictions.
3. Check wheel–rail and train interfaces: wheel loading, track condition, couplers, brakes and permitted operating controls.
4. Issue an assumption-controlled review package: sources, unknowns, calculation and test requests, jurisdiction and acceptance owner.
5. Close the loop with approved evidence: drawings, configuration, measured or witnessed tests, deviations and formal release.

What should a traction-review or RFQ package contain?

Send a route plan and longitudinal profile, gauge and rail details, minimum curve information, clearances, turnout layout, train formation, masses in each direction, operating cycle, power arrangement, environment, maintenance constraints and governing local requirements. Include photographs only as context; they do not replace measurements or controlled drawings. State whether the study is conceptual, procurement-stage or acceptance-stage so the supplier does not mistake a preliminary request for a completed design basis.

Ask the respondent to return an assumption register, the proposed configuration, the route sections examined, calculation and braking boundaries, data gaps, required drawings, testing or proving evidence, documentation and exclusions. A meaningful response makes uncertainty visible. ShaoLi's mining locomotive series is the relevant commercial starting point for a configuration conversation, while the site's credentials and published cases are company context rather than proof that a proposed route has been approved.

Refresh the review when the route or configuration changes

Treat route data as a configuration item. Trigger a review after changes to grade, curve, turnout, rail, wheel, locomotive, car, coupler, brake, payload, power system, work zone or operating rule. A new route section can invalidate a previously accepted assumption even if the locomotive has not changed. Keep the prior package so engineers can see what changed rather than rebuilding an undocumented calculation from memory.

The transport engineer owns the route and train assumptions, maintenance owns factual condition records, operations owns the duty and restrictions, procurement owns the supplier's written assumptions, and the mine's responsible authority owns approval. If those owners disagree, preserve the disagreement as an open issue. That discipline is more valuable to a buyer than a generic claim that a locomotive 'handles steep grades.'