YMS: Container Interchange
Manage the "drop loaded / pick up empty" container workflow, the most common intermodal yard operation.
Capability
How it works
- 1 Container Check-In: ISO 6346 container number validation (owner+serial+check digit), container size (20ft/40ft/40HC/45ft), container type (dry/reefer/open top/flat...
- 2 Interchange Types: Drop Loaded, Drop Empty, Pick Loaded, Pick Empty, Drop-and-Pick (combined), Live Load, Live Unload
- 3 Equipment Interchange Receipt (EIR): Legal custody transfer document with UIIA-aligned damage inspection codes.
- 4 Chassis Pairing: Track which container is mounted on which chassis.
Operational outcomes
- Container Check-In: ISO 6346 container number validation (owner+serial+check digit), container size (20ft/40ft/40HC/45ft), container type (dry/reefer/open top/flat...
- Interchange Types: Drop Loaded, Drop Empty, Pick Loaded, Pick Empty, Drop-and-Pick (combined), Live Load, Live Unload
- Equipment Interchange Receipt (EIR): Legal custody transfer document with UIIA-aligned damage inspection codes.
Integration boundaries
- Ownership Realignment Program (Crew + CMMS)
- Crew Integration Summary (Mirrored)
- Sites & Zones
Proof model
Feature-level proof
Container Interchange scope is defined in product module catalog.
verified
docs/products/yms/product.md · Module Catalog > Container Interchange
YMS gate operation execution is implemented with dedicated gate rule modules and geofence-ready integrations.
verified
docs/products/yms/product.md · Module Catalog > Gate Operations
Code: backend/services/yms/internal/modules/gates
Contract: proto/yms/gates/v1
YMS gate execution is implemented in dedicated gate modules.
verified
docs/products/yms/product.md · Module Catalog > Gate Operations
Code: backend/services/yms/internal/modules/gates
Contract: proto/yms/gates/v1
Solution routes that reuse this feature
Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).
Yard throughput
Outcome: Site execution is coordinated through shared gate, dock, and appointment workflows.
Gate, dock, and appointment behavior stays coordinated when yard workflows are linked to dispatch context.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
Detention Detection
Formula: YMS -> TMS
Open continuity routeDock-to-Load Sync
Formula: TMS <-> YMS
Open continuity routeHealthy Yards
Formula: CMMS + YMS
Open continuity routeOperational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.