Rail-Freight Data Reliability Director — Intermodal Network

The mandate

Shipment visibility is assembled from locomotive feeds, terminal scans, partner messages and manual operating updates, but late and contradictory events routinely produce plausible yet wrong arrival forecasts. Planners know which corridors require interpretation; customers do not. The company wants a bounded reliability system that reveals confidence and operational consequence instead of another central cleansing project across every partner feed.

The deliverable is a Rail-Freight Data Reliability Playbook applied to three international corridors. It must include event identity, sequencing, source precedence, lateness, correction, shipment-state reconciliation, confidence, service objectives and partner accountability. A live evidence view and intervention backlog will connect defects to train planning, terminal handling, customs readiness and customer promises rather than treating message conformance as success.

Milestone one in week three supplies journey traces, defect economics and partner-source profiles. Week seven concludes milestone two with reliability contracts and reconciliation design. At week twelve, milestone three delivers corridor pilots and disruption tests. The accepted playbook, partner scorecards, operating ownership and investment case reach the executive sponsors in week seventeen as milestone four.

Acceptance requires planners to reconstruct twenty unseen shipment states from retained events, customer teams to explain confidence for every tested milestone, and data owners to resolve injected late, duplicate and contradictory updates within target. Two partner railways must accept their source obligations. The COO signs only after a disruption exercise changes decisions correctly without hiding uncertainty behind a refreshed forecast.

The client will provide train plans, wagon and shipment references, terminal histories, partner messages, customer milestones, exception logs, forecasts and interface terms. Corridor controllers and customer teams will join observation; partner managers will secure external participation. Client engineers implement production changes, and the COO will resolve disputed source precedence or operating ownership within three business days.

Why this is external work

Corridor controllers compensate for weak data through experience, while digital teams see syntactically successful partner messages and customer teams see missed promises. No single function owns the full operational truth or can challenge external railways neutrally. External work provides cross-corridor evidence and a practical contract without assuming that central replacement of partner systems is possible.

What you will own

• Trace wagon, train, shipment, terminal and customs events through source creation, partner exchange, reconciliation, forecast and customer communication.
• Define identity, ordering, precedence, lateness, correction and confidence rules for conflicting operational updates across corridor participants.
• Link reliability objectives to planning, terminal, customs and customer decisions with explicit consequence when a threshold is breached.
• Design reconciled shipment states that preserve disputed evidence and operator judgement rather than overwriting inconvenient source differences.
• Run corridor disruptions covering reroute, missed scan, wagon split, delayed border message, terminal congestion and partner-system outage.
• Build partner scorecards around decision impact, correction behaviour and recurring root cause, not message volume or interface uptime alone.
• Transfer daily control, partner escalation, contract change and quarterly corridor review to named operations and data owners.

Candidate qualifications

• Led data reliability or control across rail, shipping, aviation, parcel or another multi-party physical logistics network.
• Reconciled late, duplicate and contradictory operational events while preserving the evidence needed for planners and customers.
• Designed data contracts with external operators whose source systems and priorities could not be controlled directly.
• Converted reliability failures into measured capacity, dwell, customs, service or customer effects rather than abstract quality scores.
• Facilitated cross-border operating exercises where physical disruption and information delay interacted differently by corridor.
• Delivered a durable operating playbook without requiring wholesale replacement of every partner interface or legacy terminal system.

Non-negotiables

• The named director must observe corridor control in Warsaw and Silesia and attend working sessions with participating foreign railways.
• No commercial or referral relationship may exist with rail visibility, integration or transport-management suppliers likely to be evaluated.
• Safety and train-control authority remain with licensed operators; data-reliability recommendations cannot direct railway movement.
• Customer confidence statements must expose unresolved operational uncertainty rather than presenting a precise but unsupported arrival time.

1. 49 words maximum. Describe contradictory logistics events you reconciled and the physical decision changed by your resulting state.
2. 49 words maximum. How would you score a partner feed whose interface is available but corrections routinely arrive after planning cut-off?
3. 49 words maximum. Which disruption test would reveal whether customer confidence survives a wagon split across two corridors?