Appendix: measurement and intervention records

Adapt these completed fictional qualitative records by carrying each named object, actor, decision and missing evidence into a sourced entry for the actual corridor. The examples contain no observed timestamp, incident frequency or empirical operating quantity. Keep unknown values open and preserve the source and status of every replacement. A completed form can still support a conditional decision: it should show which confirmation is missing, who can provide it and what action waits for it. Completion of the form does not mean that the unknown has been measured.

The record should begin with the service edition and the decision it supports. A dispatch record answers whether an eligible object may move into a particular handoff. A measurement record answers how an event will be collected and interpreted. An incident record answers which restrictions and responses apply. A commissioning record answers which requirement has been demonstrated. Keeping these purposes separate prevents a form created for local administration from being reused as evidence of a broader service result.

Each record should distinguish an unresolved property from a failed property and a completed transition. In the fictional dispatch example, missing receipt confirmation leaves destination readiness unknown; it does not establish refusal and does not permit an assumed immediate completion. A confirmed incompatibility is a different disposition and can require a revised formation or destination plan. A confirmed receipt closes that handoff while leaving later vessel acceptance open. Preserving these states prevents an unanswered message from becoming a fabricated operating result. The next action follows the actual state: obtain the confirmation, resolve the incompatibility or advance the cargo trace to its next acceptance event.

The records also retain a challenge. A dispatch approval can be contradicted by missing downstream readiness. A measured interval can be invalidated by incompatible clocks. A claimed buffer can be unavailable because the cargo is unreleased. A commissioning test can fail to represent normal resources. The challenge field is not ceremonial. It directs the review toward the condition most likely to reverse the current interpretation and preserves the reason an earlier decision was qualified.

For the fictional eligible rail formation bound for the port yard and later vessel loading, assign each required confirmation to its originator. The producer supplies cargo identity and release; the rail operator supplies formation readiness and movement conditions; the receiving yard supplies space and acceptance eligibility. The coordinator aligns those confirmations within its agreed authority. Until an actual formation, path and cargo quantity are evidenced, the entry defines a real dispatch's evidence requirement rather than records a movement. Keep each absent confirmation with its owner before deciding whether dispatch can advance.

The record separates planned destination from confirmed receipt. A forecast yard slot can support planning, but the irreversible movement may require an actual confirmation under the relevant operating arrangement. The form should state which confirmation is necessary at the dispatch point and which conditions may remain provisional. If the yard cannot confirm readiness, the response should identify the permitted hold location and affected commitments rather than send the formation into an unmanaged queue.

The cargo record should map the commercial parcel to the physical formation and yard receipt object. A split or combined parcel needs a traceable relationship so that quantity and eligibility can be reconciled. If the mapping is absent, the dispatch may still be physically possible but the end-to-end evidence remains incomplete. The form should not treat a vehicle identifier as sufficient proof that the intended cargo has reached its acceptance boundary.

An exception should record authority, reason and consequence. Dispatch under a temporary recovery priority can be feasible while delaying another user. The record should state who approved the exception and when it expires. A recurring exception should trigger service-basis review. This prevents the corridor from relying indefinitely on informal interventions that are neither represented in the capacity input nor agreed as part of normal service.

The measurement example concerns the interval between eligible arrival at the yard and accepted receipt. Its start excludes cargo not yet eligible for the intended service, while a companion record preserves that ineligible waiting. Its end follows acceptance rather than merely the end of physical unloading. This pairing permits both a service-duration measure and a diagnosis of preparation delay. The observation basis should state those distinctions before data are extracted.

The form identifies event time, creation time and transmission time separately. A manually entered event may be accurate in content but late in reporting. A device record may be timely but use an incompatible clock. The collection plan should preserve original values and any correction rule. If a clock discrepancy cannot be resolved, the duration remains unavailable or bounded under a declared method. The example leaves all times unknown because it represents no actual movement.

The observation universe includes eligible arrivals and retains unfinished cases at cutoff. It also records the outside queue and excluded cargo class where relevant to the broader service. This prevents a clean completed-only extract from producing an apparently improved average while backlog remains. The analyst should document the relationship between the local observation and the end-to-end service population, not merely describe the number of available rows.

The cause record distinguishes immediate stop state from attribution. A full receipt area can be observed, while the reason it is full may be uncertain. The collector should retain that difference and seek release, reservation and downstream records before assigning blame. The resulting evidence can support a focused trial or operating change without making an unsupported claim about an actor's motive or contractual performance.

The fictional incident concerns loss of inland replenishment while a vessel-loading commitment remains active. The record first checks whether eligible reserve stock can protect that commitment. It identifies the relevant stop authority, stock eligibility, reclaim readiness and marine permission. If those conditions are unconfirmed, the reserve remains conditional. The form does not assign an interruption duration or claim that the protected service can continue for a quantified period.

The response should specify upstream and downstream actions together. The producer may need to restrain release; the railway may need to protect resources and revise paths; the yard may need to preserve space and eligible stock; the loading actor may need to revise the vessel plan. These actions depend on their respective authority and evidence. The coordinator's role is to align feasible responses and make user impacts visible, not to substitute a system objective for a technical or public stop condition.

The restoration section distinguishes repaired capability, operational readiness, resumed movement and stable service. It also asks whether reserves have been rebuilt. The incident should not close merely because the first train moves or the loader restarts. If temporary priorities and restrictions remain, the service state should retain them. The record should identify the condition and actor that permit return to the normal operating basis.

A corrective action should address the mechanism supported by evidence. If replenishment failed because of a path restriction, a loader-rate improvement is not a relevant closure action. If the yard's reserve was physically present but ineligible, a stock-volume increase may not solve the duty. The incident record should preserve the causal hypothesis, competing explanation and next test. This links operational learning to the intervention sequence rather than treating incidents as isolated stories.

The handover example concerns a proposed intervention after a local component test. The test may establish a defined equipment capability while the recurring corridor service remains unproven. The record should identify the accepted requirement, test conditions, temporary support and residual defects. It should then state the service state that may legitimately begin. This prevents a supplier milestone from being silently promoted into full corridor acceptance.

Update the model basis only as far as the commissioning evidence supports. For an effective annual capacity, retain the observation basis and reproduce the revised fixture through the canonical engine. Where annualisation is unsupported, leave the input provisional and name the evidence still needed. A required annual cell in a production table supplies no reason to invent capability. The handover should carry that unknown into its claim and next test, keeping the demonstrated local property separate from the annual service result.

An intervention evaluation record should compare the intended mechanism with the observed response under a defined basis. It should record concurrent changes in demand, cargo mix and operating envelope. A shorter local wait may be useful even when attribution is uncertain, but the report should not declare a causal effect without an adequate design. The evaluation should identify the next observation or trial needed to distinguish competing explanations.

Follow the fictional exception from dispatch to handover. Without compatible yard readiness confirmation, the formation stays at the last permissible hold point. The measurement record carries the missing event as unresolved rather than assigns an interval of zero duration. If that hold threatens loading duty, the incident record identifies eligible reserve and its closing condition. A later local equipment test closes its technical defect while destination acceptance remains open at handover. Each form therefore has a distinct job, and the unresolved handoff retains its consequence through the chain. This is the proposed record logic; no movement or test is asserted to have occurred.