Calculating Discharge/Loading Rate (TPH) in Shore Crane Operations — Formulas, Assumptions, and Worked Examples
In cargo handling, few numbers are quoted as frequently—or misunderstood as easily—as TPH (tons per hour). In shore crane operations, TPH is often used to benchmark performance, estimate berth time, negotiate contracts, and forecast exposure to demurrage/despatch. Yet two stakeholders can report different TPH for the same vessel call and both can be “right,” simply because they are measuring different time bases, using different weight assumptions, or including/excluding stoppages differently.
This article provides a formal, business-ready methodology for calculating discharge/loading rate (TPH) in shore crane operations, including the core formulas, practical definitions (gross vs net), and two worked examples. It is written for port and terminal management, stevedores, ship agents, chartering teams, and logistics/procurement functions that need a defensible, auditable approach.
What “TPH” Means in Shore Crane Operations (And Why Definitions Matter)
At its simplest, TPH is:
TPH = Tons handled / Hours
The complication is that neither “tons” nor “hours” are as straightforward as they appear.
On the tons side, you may be using draft survey (bulk), weighbridge tickets (truck flows), belt scale totals (conveyor systems), tally-based estimates (breakbulk), or container weights (VGM/manifest). Each method has uncertainty and timing differences.
On the hours side, you must choose a time base. The most common practical definitions are:
- Gross TPH (GTPH): uses total elapsed time across a defined operational window, typically including most stoppages.
- Net TPH (NTPH): uses only “productive time” (hook-on to hook-off cycles), excluding delays not attributable to the crane cycle.
- Crane-hour TPH vs gang-hour TPH: depends on whether you normalize by crane operating hours or by the stevedoring gang’s paid/allocated hours.
If you do not define the time base explicitly, TPH becomes a discussion about semantics rather than performance.
Why TPH Is Commercially and Operationally Critical
TPH is not just a KPI; it is a lever that affects cost and schedule. In most calls, the operational consequences of a misestimated TPH are predictable:
- Underestimating TPH may lead to over-allocating berth time and equipment, reducing berth utilization and terminal throughput.
- Overestimating TPH can create berth conflicts, missed sailing windows, crew overtime, congestion, and inflated demurrage risk.
From a contract perspective, TPH is often embedded in service-level expectations, bonus/penalty mechanisms, and performance claims. From an operational perspective, TPH is shaped by factors that are only partly under the crane operator’s control: cargo properties, truck/conveyor capacity, hatch layout, vessel trim requirements, wind limits for grabs, lighting constraints, and interface discipline (signalman, tally, traffic control).
The best practice is to calculate TPH in a way that is transparent, repeatable, and aligned with the decision you are making (planning, benchmarking, invoicing, or dispute resolution).
The Building Blocks: Key Variables and Time Bases
To calculate TPH cleanly, define the following variables up front.
Tonnage Variables
Let:
- W = total weight handled (tons) within the window
- Wi = weight for parcel/hold i
- wcycle = average payload per crane cycle (tons per grab / tons per lift)
For bulk grabs, wcycle is rarely equal to the nominal grab capacity because fill factor depends on cargo density, moisture, trimming, and operator technique.
Time Variables
Let:
- Telapsed = total elapsed time in the window (hours)
- Tproductive = productive handling time (hours)
- Tdelay = delays/stoppages (hours)
Such that:
Telapsed = Tproductive + Tdelay
You must define what counts as “productive.” A workable, auditable approach is to define productive time as the period when the crane is actively executing the handling cycle for that cargo stream (not merely “running” or “available”).
Cycle Variables (for a cycle-based estimate)
Let:
- tcycle = average cycle time (minutes/cycle)
- N = number of cycles completed
- A = availability factor (0–1), if you incorporate expected downtime
- eta = efficiency factor (0–1), capturing micro-stoppages, trimming, and non-ideal conditions
Cycle-based calculations are useful in planning or early-stage estimating. For final reporting, weight-based actuals are usually preferable.
Core Formulas for TPH in Shore Crane Operations
Gross TPH (GTPH)
GTPH = W / Telapsed
Use GTPH when you want a “real world” rate that reflects stoppages, weather, congestion, shift changes, and interface delays. It is often the best measure for berth occupancy planning.
Net TPH (NTPH)
NTPH = W / Tproductive
Use NTPH when you want to isolate handling productivity during active work. It is useful for comparing crane performance across calls, provided “productive time” is measured consistently.
Crane-Based Planning TPH (Cycle Method)
If you estimate output from cycle time and payload:
TPHcycle = (wcycle x 60) / tcycle
If you incorporate efficiency:
TPHadj = ((wcycle x 60) / tcycle) x eta
If you plan over a shift with availability:
Wshift = TPHadj x Hshift x A
This method is only as good as your assumptions for wcycle, tcycle, eta, and A. It is powerful for planning, but it should not replace actual measurement when settling performance claims.
Choosing the Right “Hours”: Common Time Windows (And Their Implications)
In port operations, “hours” can be defined in multiple legitimate ways. The key is to select the one that matches your business question and state it explicitly.
Typical time windows used in reporting
- From first lift to last lift (FLLL): excludes pre-start preparations and post-completion activities.
- From gang on to gang off: includes briefings, set-up, and waiting under instruction.
- From all fast to all gone: aligns with berth occupancy, but includes non-cargo ship operations (paperwork, pilotage waits) that may not reflect cargo handling.
There is no universally “correct” window. There is only a window that is appropriate for the decision and consistently applied.
What Determines TPH in Shore Crane Bulk/General Cargo Handling
TPH is constrained by the slowest element in the cargo flow. In many operations, the crane is not the bottleneck; the receiving chain is. Understanding this helps you diagnose performance without blaming the wrong party.
The key drivers include crane cycle time, grab fill factor, hatch geometry, re-positioning frequency, truck turn time, hopper capacity, conveyor belt rate, stockpile management, dust suppression stops, and the incidence of trimming and clean-up near the end of each hold.
A practical way to think about it is: your effective TPH is the cycle-based theoretical rate, reduced by efficiency losses and constrained by downstream capacity.
A Minimal Checklist of Assumptions to Document (Use It Every Time)
To keep reporting defensible, document these items in every TPH report:
- The tonnage source (draft survey, weighbridge, belt scale, tally) and the time stamp boundaries of that tonnage.
- The time window definition and whether it is local time, ship time, or terminal system time.
- The delay classification logic (weather, breakdown, waiting trucks, hatch change, shift change, safety stop).
- The number of cranes/gangs and whether TPH is per crane, per berth, or aggregate.
This is deliberately short: it prevents most disputes before they start.
Worked Example 1: Actual TPH from Weights and Time (Gross vs Net)
Scenario: A shore crane discharges bulk cargo into hoppers feeding trucks. Total measured tonnage for the call segment is W = 12,000 tons. The operational window is from first lift to last lift.
- Total elapsed time: Telapsed = 18.0 hours
- Weather stop: 1.5 hours
- Hopper blockage / clean-out: 0.5 hours
- Waiting trucks (receiving chain constraint): 1.0 hour
- Shift change and toolbox talk: 0.5 hours
Total delays = 3.5 hours
Tproductive = 18.0 – 3.5 = 14.5 hours
Gross TPH:
GTPH = 12,000 / 18.0 = 666.7 TPH
Net TPH:
NTPH = 12,000 / 14.5 = 827.6 TPH
Interpretation: Both numbers are meaningful. GTPH reflects the berth-facing reality (including delays). NTPH reflects the productivity when the system was actively working. If the commercial discussion is about berth occupancy, GTPH is more relevant. If the technical discussion is about the crane’s productive capability, NTPH is more relevant—provided delay allocation is agreed.
Worked Example 2: Planning TPH from Cycle Time and Grab Payload
Scenario: You must estimate whether one shore crane can meet a discharge target. You plan to use a grab with an average effective payload of wcycle = 12 tons per cycle. The expected average cycle time is tcycle = 2.2 minutes per cycle. Due to trimming, hatch moves, and micro-stoppages, you apply an efficiency factor eta = 0.78.
Theoretical cycle TPH:
TPHcycle = (12 x 60) / 2.2 = 327.3 TPH
Adjusted planning TPH:
TPHadj = 327.3 x 0.78 = 255.3 TPH
If you plan an 11-hour effective shift with availability A = 0.92:
Wshift = 255.3 x 11 x 0.92 = 2,584 tons/shift (approx.)
Interpretation: This estimate is helpful for planning equipment and berth time. However, it is highly sensitive to your assumptions on cycle time and payload. When operations start, replace planning assumptions with actual measured weights and times to avoid disputes.
Table: Practical TPH Definitions You Can Standardize in Reports
| Metric | Formula | Time Base | Best Used For | Key Risk if Misused |
|---|---|---|---|---|
| Gross TPH (GTPH) | W / Telapsed | First lift to last lift (or defined window) | Berth planning, overall performance | Penalizes parties for non-crane constraints unless delays are attributed |
| Net TPH (NTPH) | W / Tproductive | Productive handling time only | Comparing handling productivity | Inflated if “productive time” is defined too narrowly |
| Cycle TPH | (wcycle x 60) / tcycle | Cycle-level | Early planning, feasibility | Can be unrealistic if fill factor and micro-stops are ignored |
| Adjusted Cycle TPH | Cycle TPH x eta | Cycle-level with efficiency | More realistic planning | Still assumption-driven; requires calibration |
This standardization improves consistency across calls and reduces the “TPH debate” that often happens after the fact.
How to Treat Delays: A Formal, Practical Approach
Delay treatment is where most reporting disagreements originate. The solution is not to eliminate discretion entirely; it is to define categories and apply them consistently.
A sensible approach is to classify delays into: weather/environment, equipment, ship, terminal/receiving chain, and operational management (shift change, briefing, permit controls). The precise taxonomy should match your contract language and terminal practice.
Use delay categories to support two parallel narratives: the berth-level narrative (GTPH) and the productivity narrative (NTPH). When you do this, your report remains truthful and useful to multiple stakeholders without forcing a single number to carry every meaning.
Practical Guidance: Improving TPH Without Compromising HSE
Improving TPH is not synonymous with “working faster.” In mature operations, TPH improvements come from reducing friction: smoother truck dispatch, better hopper feeding discipline, predictable shift handovers, proactive maintenance, and better trimming strategy to avoid end-of-hold slowdowns.
In shore crane operations, a recurring pattern is that the last 10–15% of a hold takes disproportionately longer due to clean-up, reach constraints, and reduced grab fill factor. Planning for this “tail effect” leads to more accurate berth time estimates and more credible performance targets. Operationally, it also encourages the right conversations early: whether additional mobile plant support is required, whether hold cleaning scope is clarified, and whether cargo receiver capacity is stable.
Conclusion: A TPH Number Is Only as Strong as Its Definition
In shore crane operations, TPH is a powerful metric precisely because it is simple in form and broad in impact. That simplicity can also make it vulnerable: different teams measure different time windows, use different tonnage sources, and then argue over a single number as if it were absolute truth. The operationally mature approach is to treat TPH as a defined metric family—gross, net, and cycle-based—each serving a distinct purpose.
If you standardize your time base, document tonnage sources, classify delays consistently, and present both gross and net rates transparently, your TPH reporting becomes more than a KPI. It becomes a reliable planning tool, a fair benchmarking method, and a defensible commercial reference point. And in a business where hours at berth translate quickly into material cost, that kind of clarity is not cosmetic—it is competitive.
The inherent complexities of TPH reporting—specifically the friction between operational reality and commercial contracts—often demand more than just manual reconciliation. Robust terminal management requires a standardized, digital framework that bridges the divide between raw operational data and auditable performance metrics. This is where advanced analytical ecosystems like Baareman Solutions become essential; by automating the integration of crane cycle telemetry with precise tonnage inputs, such systems effectively eliminate the subjectivity that so often fuels demurrage disputes, ultimately transforming disparate data points into a single, defensible source of truth for all stakeholders.
