Capacity claims need an operating basis

A statement of annual capacity conceals a calendar, a cargo specification and an operating method. The capacity of a loader may originate as a rate under a defined material condition while a railway capacity may originate as a timetable with particular train lengths and turnaround assumptions. A stockyard figure may describe storage rather than annual flow. These quantities cannot enter the same minimum calculation until the analyst establishes compatible units and operating bases. An impressive nominal number is not enough to make a stage comparable with its neighbours.

The first task is to distinguish a rate from a stock. A rate describes movement per unit of time. A stock describes material held at an instant. Stockyard area or usable storage can influence continuity and batch formation, but neither directly gives an annual throughput without a residence-time and handling basis. Similarly, the number of wagons is a fleet stock, while delivered cargo depends on payload, cycles and availability. Converting one into the other requires assumptions about operation, not a change of unit label.

Nominal capacity should identify the conditions under which it is attainable. These may include the handling configuration, allowable material characteristics, loading sequence, personnel, supply readiness and scheduled hours. A nominal annual quantity that already includes downtime should not be multiplied by an availability factor that removes the same downtime again. The analyst should ask whether the supplier's figure is instantaneous, shift-based or annualised, and whether it assumes uninterrupted feed. That question often matters more than another decimal place in the final throughput result.

The operating calendar should be shared only where it is genuinely common. A railway can be closed for planned maintenance while a port remains open; a vessel-loading operation may depend on tide or weather windows that do not constrain inland movement at the same time. Expressing each stage as an annual rate is a useful simplification, but it does not prove that those opportunities line up. The annual model assumes enough coordination and buffering to make the declared effective capacities mutually usable. Later chapters test the implications of that assumption.

Availability can refer to mechanical readiness, scheduled operating readiness or demonstrated service capability. An asset may be mechanically ready while its crew, fuel, path or cargo is unavailable. A report that counts that period as available can be correct for maintenance management and misleading for delivered service. Before using availability in a model, the team should define the denominator, state exclusions and distinguish the reason an apparently ready asset did not perform. An availability percentage without that dictionary is an argument waiting to happen.

The Corridor lab applies each user-supplied availability to nominal annual capacity. This is an explicit effective-capacity convention, not a reliability model. The resulting figure should be read as an annual usable capacity assumption for the stated stage. It does not assign random failure probabilities or simulate when unavailable periods occur. Two stages can have the same annual availability yet produce very different corridor service if their interruptions are coordinated, alternating or concentrated within the same critical season. The calculation deliberately leaves that chronology unresolved.

An analyst should maintain a downtime reconciliation. Planned maintenance, unplanned repair, missing crew, denied access, cargo starvation and downstream blocking are different mechanisms. Combining them into a single capacity multiplier may be adequate for a screening study, provided the team states what is inside it. It becomes dangerous when an intervention targets only one mechanism but the model assumes it improves the entire multiplier. A mechanical upgrade cannot automatically create a train path or release a consignment held for documentation.

The distinction also prevents circular measurement. If availability is inferred from realised throughput divided by nominal capacity, and realised throughput was limited by demand, the factor measures use rather than capability. Multiplying nominal capacity by that inferred factor simply reproduces historical flow. It cannot tell the committee what the stage could deliver under additional demand. A defensible operating basis separates intrinsic readiness from the system's choice or inability to utilise the stage, then states which concept the effective-capacity input represents.

The unit-cost calculation is equally sensitive to basis. Variable cost per tonne should describe the marginal operating cost attached to cargo moving through the stated stage. Annual fixed cost should describe the obligations that remain under the assumed operating regime. Their sum across stages is allocated to the common delivered throughput in the canonical model. This convention makes the denominator effect visible: a chain that delivers less cargo spreads the same assumed fixed obligations over less useful output.

That common-flow convention assumes no material loss, no rework loop and no difference between stage quantity and accepted destination quantity. If a material is dried, blended, rejected or recirculated, local tonnes and delivered tonnes differ. Then stage cost needs a conversion basis before it can be added consistently. Moisture also makes an apparently simple tonne ambiguous. The team should specify whether a physical measurement is wet, dry or defined by another acceptance convention, and should avoid treating a conversion factor as universally known.

The frozen intervention cases intentionally hold operating costs constant. This isolates what the annual serial model says about capacity and fixed-cost dilution. It does not imply that an expanded railway or loader can be acquired without capital expenditure, incremental maintenance or additional labour. Reading the lower illustrative unit cost as an investment return would skip the economic question. A proper appraisal would require incremental cost, timing, financing and the value of additional accepted service, all of which lie beyond the current app's method.

Currency and price basis need the same discipline. A real estimate should state whether costs use a constant or changing price basis, which currency applies and whether taxes, financing, insurance and replacement obligations enter the calculation. The fictional model's currency labels simply keep the calculation dimensionally coherent. They do not establish tariffs, exchange rates, market costs or contract entitlements. The absence of project-specific commercial information is deliberate, and the conclusions should remain physical screening conclusions rather than disguised transaction advice.

The basis sheet should permit a second operator to reconstruct each input without guessing how the first analyst interpreted a label. For every stage it should record the physical boundary, cargo basis, nominal-capacity source, calendar, availability definition and cost coverage. It should identify unresolved assumptions by name. An empty source cell must remain empty or be marked unknown; it should not be replaced with an authoritative-looking estimate solely to keep a model running. A screening estimate can be useful if its assumption status and challenge route are explicit.

The sheet should separate measured, stipulated and illustrative values. A measured input needs a defined observation universe and event dictionary. A stipulated input may reflect a design requirement or operating agreement that has not yet been demonstrated. An illustrative input is chosen to test reasoning and represents no actual operation. These statuses should survive export, review and later reuse. A copied spreadsheet or scenario file can otherwise lose its fictional context and become an apparently factual baseline in a subsequent committee paper.

Changes to the operating basis should trigger a new comparison rather than a silent edit. If an annual capacity is revised because the operating calendar changed, the team should explain which periods became usable and how the adjacent stages respond. If the change represents a corrected unit error, the earlier conclusion should be withdrawn or superseded visibly. Version control is valuable because it preserves the causal explanation of a result, not because a longer change log creates an appearance of diligence.

The resulting decision is to admit only inputs that are sufficiently defined for the current purpose. A rough estimate can pass a concept-screening gate and fail a procurement or service-acceptance gate. The team should name that difference instead of forcing every stage into a universal certainty standard. What cannot be accepted at any stage is a rate with an unknown denominator or a cost with an unknown quantity basis. Those defects prevent the calculation from answering even the simplest corridor question reliably.