InboundIQ — Intelligent Dock Allocation Engine

Reduced truck TAT from 6.7 → 2.2 hours across Amazon FCs
Python
ReactJS
AWS Lambda
MySQL RDS
API Gateway
CloudWatch
Midway Auth

Problem Statement

Fulfillment Center dock doors are among the scarcest resources in Amazon's inbound logistics network — each site operates with just 10 to 15 doors. Without a systematic prioritization engine, operations associates relied on manual judgment to decide which truck in the yard should be sent to the next available door. This approach introduced inconsistency, bias toward familiar carriers, and frequent misallocation that left high-priority cargo waiting while less urgent loads occupied doors.

Heimdall (InboundIQ) replaced all manual decision-making with a data-driven priority model. The system continuously evaluates every truck in the yard across five weighted dimensions — shelf criticality, appointment urgency, dwell time, stow window pressure, and arrival timing — to produce a real-time ranked queue. When a door becomes available, the highest-priority truck is automatically surfaced to the operator, eliminating guesswork and ensuring that the most business-critical cargo always moves first.

System Architecture

Serverless, event-driven architecture on AWS. The system ingests real-time appointment, shipment, and yard events through the Infinity Pipeline (SNS), processes them via Lambda, persists state in MySQL RDS (Multi-AZ), and serves a React dashboard through API Gateway. Drag to explore, scroll to zoom.

Animated edges show the primary request path. Dashed edges show async/secondary flows.

Database Schema

Appointments
ColumnTypeNotes
appointmentIdVARCHARPK
warehouseIdVARCHARFK → FC
appointmentStatusENUMOPEN, CHECKED_IN, CLOSED
carrierNameVARCHARSCAC carrier
appointmentStartDateDATETIME
appointmentEndDateDATETIME
vridVARCHARVehicle Registration ID
unitCountINT
cartonCountINT
apptTypeENUMCARP, AMZL, SPD, HOT
lowInstockPctDECIMAL0-80, shelf criticality
scacVARCHARCarrier code
doorNumberINTAssigned dock door
lastUpdatedTimeDATETIME
recordVersionINTOptimistic locking
YardEvents
ColumnTypeNotes
nodeIdVARCHARPK
buildingCodeVARCHARFC identifier
equipmentNumberVARCHAR
registrationIdVARCHAR
shipperAccountVARCHAR
vridVARCHAR
ISAVARCHARISA identifier
userIdVARCHAROperator
timeStampDATETIME
notesTEXT
Shipments
ColumnTypeNotes
appointmentIdVARCHARPK (composite)
shipmentIdVARCHARPK (composite)
warehouseIdVARCHAR
eventTypeENUM
cartonCountINT
unitCountINT
shipmentStatusENUM
recordVersionINT

Priority Scoring Model

Priority Score = (lowInstockPct × 0.35) + (apptTypeScore × 0.25) + (dwellHoursScore × 0.20) + (stowUrgencyScore × 0.12) + (arrivalScore × 0.08)

Low In-Stock %
35%
How critically the FC shelves need this cargo
Appointment Type
25%
HOT = 100, SPD = 75, CARP = 50, AMZL = 40
Dwell Hours
20%
Time waiting in yard, normalized
Stow Urgency
12%
Stow window pressure
Arrival Status
8%
Timing vs scheduled appointment

LLM Enhancements

Explain Rank

Per-truck AI explanation of why it is ranked at its current position, referencing actual model weights — lowInstockPct, apptType, dwellHours, stowUrgency, and arrivalStatus — with a plain-English narrative for operations associates.

Represents how I would build this system today with LLM capabilities
Natural Language Filter

Plain English queries like "show HOT trucks with high instock need" or "dwell over 12 hours at SEA1" that the LLM translates into structured filters applied to the yard queue table in real time.

Represents how I would build this system today with LLM capabilities
Dock Intelligence

AI-powered recommendations for dock allocation that analyze the current yard queue, dock occupancy, unloading ETAs, and truck priority scores to suggest which truck should be assigned to the next available door.

Represents how I would build this system today with LLM capabilities
Ask the Yard

Conversational chat interface with full yard context — docked trucks, waiting trucks, door status, and FC metrics — enabling operations leads to ask ad-hoc questions without building queries.

Represents how I would build this system today with LLM capabilities

Key Metrics

6.7 → 2.2 hrs

Truck TAT P95

100%

Decision Automation

5 FCs

Deployment Scope

<2 min

Ranking Refresh Rate

View System Design on GitHub