# Inbound Consist Triage

*/Opportunities/Inbound_Consist_Triage*

## Opportunity Overview

**Wedge**: The beachhead focuses on independent intermodal facilities handling mixed-freight trains, where consist variability causes the highest manual labor load. The initial product strictly automates the ingestion of emailed PDF manifests and converts them into standardized payloads for the Terminal Operating System. Once this ingestion layer is trusted, the product expands into automated yard spotting, actively assigning incoming railcars to specific tracks based on dwell times and outbound schedules.
**Timing**: Multimodal vision models now reliably parse highly unstructured, low-resolution manifest scans and unstandardized emails that break traditional OCR templates. Concurrently, chronic yard congestion and clerk shortages force operators to automate inbound processing to avoid demurrage penalties.
**Why This I C P**: Independent intermodal terminal operators face acute, immediate congestion penalties if trains sit idle awaiting clearance, creating high urgency. Unlike Class I railroads that mandate massive, slow-moving enterprise deployments, independent yards quickly adopt point solutions that clear specific operational bottlenecks.
**Size Of Prize**: Approximately 1,500 major rail yards and intermodal terminals in North America spend roughly $80,000 annually on dedicated clerical labor for consist triage. This creates a directly addressable labor replacement market of $120M per year.
**Gap Narrative**: Intermodal terminals and rail yards receive inbound consists across fragmented formats, including broken EDIs, scanned PDFs, and unstructured emails. Terminal clerks manually parse these documents to verify car sequencing, hazardous material constraints, and destination routing before a train arrives. No current system automatically extracts and reconciles this messy inbound data directly into terminal operating software without manual data entry.
**Defensibility**: The core defensibility stems from workflow lock-in via deep integration with legacy Terminal Operating Systems and localized yard safety rules. While the initial document extraction capability is fundamentally a commodity, the system builds a proprietary map of yard-specific routing habits and constraint handling over time. Ripping out the system requires an operator to manually rebuild years of localized routing logic and re-expose themselves to immediate yard congestion.
**Why This Thesis**: A Service-as-Software approach directly substitutes the clerk's specific output of reading an email and populating the Terminal Operating System. Buyers pay per processed consist rather than per software seat, directly tying the expense to the volume of cleared freight.

## Opportunity Linked Thesis

**Thesis**: [Service-as-Software](/Theses/Service-as-Software)

## Opportunity Linked I C P

**Icp**: [Freight Terminal Operator](/CompanyTypes/Freight_Terminal_Operator)

## Opportunity Market Sizing

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**S A M**: ~$200M-350M North American and European Tier 1 and Tier 2 freight terminals
**S O M**: ~$15M-30M
**T A M**: ~12,000 global rail and intermodal freight terminals × ~$60k/yr average triage software and labor allocation ≈ ~$720M
**Growth Rate**: ~8-12%/yr, driven by precision scheduled railroading (PSR) efficiency mandates and the need to reduce yard dwell times
**Paid Comparable Spend**: ~$80k-120k/yr per terminal spent on manual yard clerk labor to cross-reference EDI 418 consist messages, legacy terminal operating system (TOS) modules, and custom spreadsheet maintenance

## Opportunity Incumbents

- [Wabtec ExpressYard](/Products/Wabtec_ExpressYard) — Tool
- [SAP Yard Logistics](/Products/SAP_Yard_Logistics) — Tool
- [Microsoft Excel](/Products/Microsoft_Excel) — Spreadsheet
- [Bourque Yardmaster](/Products/Bourque_Yardmaster) — Tool
- [Custom Legacy Databases](/Products/Custom_Legacy_Databases) — DIY
- [Railinc EDI Services](/Products/Railinc_EDI_Services) — Service

## Opportunity Win Conditions

**Kill Thresholds**:
- EDI 418 auto-match rate < 85% after 30 days of deployment
- Human-in-loop escalation rate > 20% on week four
- Sales cycle > 120 days for Tier 2 terminals
- Pilot-to-paid conversion < 40% at the 90-day mark
**Leading Metrics**:
- EDI 418 message auto-match rate %
- Time spent per inbound consist triage in minutes
- Human-in-loop escalation % for mismatched railcars
- Daily active yard clerks per deployed terminal
- Legacy TOS API error rate %
**What Proves Right**: Terminal yard clerks route daily EDI 418 messages through the system and process yard inventory matches without opening Microsoft Excel. Terminals convert from 30-day pilots to $50k annual contracts at a 60% rate. The system processes inbound consists 40% faster than manual clerk verification against legacy terminal operating systems.
**What Proves Wrong**: Yard clerks revert to manual spreadsheets to verify consist discrepancies because they do not trust the automated parsing logic. Terminals refuse to transition to paid contracts due to excessive integration failures with incumbent systems like Wabtec ExpressYard or SAP Yard Logistics. The sales cycle stretches beyond six months as Tier 1 and Tier 2 IT departments block access to legacy databases.

## Opportunity Build Profile

**Hardest Part**: Achieving near-perfect extraction accuracy on scanned, handwritten, or poorly formatted legacy PDFs containing critical hazmat codes and railcar sequences, where a single misread letter triggers compliance violations.
**Min Viable Scope**: Ingest emailed PDFs and flat files, extract the car sequence and cargo payload, and push a structured feed into one specific Terminal Operating System. Exclude native EDI protocol support, automated track assignment, and hazmat compliance generation.
**Cold Start Problem**: The system requires a corpus of fragmented, non-standard rail consists to tune the extraction engine. Bypass this by securing a single shortline or terminal design partner to ingest their historical inbox data for baseline tuning.
**Time To First Value**: 1-2 weeks of parser tuning and Terminal Operating System integration
**Data Moat Available**: true
**Technical Difficulty**: Moderate

## Neighborhood

### Where the gap lives

- [Belt Line Railroads](/CompanyTypes/Belt_Line_Railroads) — latent gap · CompanyTypes

### Applies thesis

- [Freight Terminal Operator](/CompanyTypes/Freight_Terminal_Operator) — applies thesis · CompanyTypes

### Incumbent in

- [Microsoft Excel](/Software/Microsoft_Excel) — incumbent in · Software
- [Custom Legacy Databases](/Products/Custom_Legacy_Databases) — incumbent in · Products
- [Railinc EDI Services](/Products/Railinc_EDI_Services) — incumbent in · Products
- [Wabtec ExpressYard](/Products/Wabtec_ExpressYard) — incumbent in · Products
- [SAP Yard Logistics](/Products/SAP_Yard_Logistics) — incumbent in · Products
- [Outsourced Data Entry](/Products/Outsourced_Data_Entry) — incumbent in · Products
- [Railinc EDI Routing](/Products/Railinc_EDI_Routing) — incumbent in · Products
- [Manual Email Triage](/Products/Manual_Email_Triage) — incumbent in · Products
- [Custom EDI Scripts](/Products/Custom_EDI_Scripts) — incumbent in · Products
- [Bourque YardMaster](/Products/Bourque_YardMaster) — incumbent in · Products
- [Wabtec RailConnect](/Products/Wabtec_RailConnect) — incumbent in · Products

### Embodies

- [Service-as-Software](/Theses/Service-as-Software) — embodies · Theses
- [Software](/Theses/Software) — embodies · Theses

### Similar Opportunities

- [Inbound Consist Triage](/CompanyTypes/Belt_Line_Railroads/Opportunities/Inbound_Consist_Triage) — similar · Opportunities
- [Dynamic Train Dispatching](/CompanyTypes/Belt_Line_Railroads/Opportunities/Dynamic_Train_Dispatching) — similar · Opportunities
- [AI Railcar Logistics for Grain Mills](/Opportunities/AI_Railcar_Logistics_for_Grain_Mills) — similar · Opportunities
- [FRA Compliance Automation](/Opportunities/FRA_Compliance_Automation) — similar · Opportunities
- [Inbound Material Triage](/Opportunities/Inbound_Material_Triage) — similar · Opportunities
- [FRA Compliance Processing](/Opportunities/FRA_Compliance_Processing) — similar · Opportunities
- [Track Defect Triage](/CompanyTypes/Belt_Line_Railroads/Opportunities/Track_Defect_Triage) — similar · Opportunities
- [AI Intermodal Dispatch for Freight Forwarders](/Opportunities/AI_Intermodal_Dispatch_for_Freight_Forwarders) — similar · Opportunities
- [Dynamic Train Dispatching](/Opportunities/Dynamic_Train_Dispatching) — similar · Opportunities
- [AI Freight Yard Dispatch](/Opportunities/AI_Freight_Yard_Dispatch) — similar · Opportunities
- [Rail Dispatch Agent](/Opportunities/Rail_Dispatch_Agent) — similar · Opportunities
- [Yard Dispatch Automation](/CompanyTypes/Trade_Show_&_Exhibit_Furnishings_Provider/Opportunities/Yard_Dispatch_Automation) — similar · Opportunities
- [Freight Exception Management](/Opportunities/Freight_Exception_Management) — similar · Opportunities
- [Shipyard Container Orchestration](/Opportunities/Shipyard_Container_Orchestration) — similar · Opportunities
- [AI Waybill Parsing](/Opportunities/AI_Waybill_Parsing) — similar · Opportunities
- [Maintenance Defect API](/CompanyTypes/Class_I_Freight_Railroad/Opportunities/Maintenance_Defect_API) — similar · Opportunities
- [Yard Dispatch Automation](/Opportunities/Yard_Dispatch_Automation) — similar · Opportunities
- [Autonomous Yard Shunting](/CompanyTypes/Belt_Line_Railroads/Opportunities/Autonomous_Yard_Shunting) — similar · Opportunities
- [Freight Liability Clearinghouse](/Opportunities/Freight_Liability_Clearinghouse) — similar · Opportunities
- [Document Routing Engine](/Opportunities/Document_Routing_Engine) — similar · Opportunities