Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

YMS: Appointments

Appointment Types: Inbound (receive), Outbound (ship), Live Load, Drop & Hook TMS Integration: Link appointments to TMS load IDs for end-to-end visibility Carrier Communication:...

Problem

Appointment Types: Inbound (receive), Outbound (ship), Live Load, Drop & Hook TMS Integration: Link appointments to TMS load IDs for end-to-end visibility Carrier Communication:...

Capability

Link TMS loads to dock scheduling.

How it works

  1. 1 Appointment Types: Inbound (receive), Outbound (ship), Live Load, Drop & Hook
  2. 2 TMS Integration: Link appointments to TMS load IDs for end-to-end visibility
  3. 3 Carrier Communication: SCAC code, trailer number, driver name, ETA tracking
  4. 4 Status Lifecycle: SCHEDULED -> CHECKED_IN -> AT_DOCK -> LOADING/UNLOADING -> COMPLETED

Operational outcomes

  • Appointment Types: Inbound (receive), Outbound (ship), Live Load, Drop & Hook
  • TMS Integration: Link appointments to TMS load IDs for end-to-end visibility
  • Carrier Communication: SCAC code, trailer number, driver name, ETA tracking

Integration boundaries

  • Ownership Realignment Program (Crew + CMMS)
  • Crew Integration Summary (Mirrored)
  • Sites & Zones

Proof model

Feature-level proof

  • Appointments scope is defined in product module catalog.

    verified

    docs/products/yms/product.md · Module Catalog > Appointments

  • 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).