Montgomery Supply Control Tower
Diageo
AWS

Montgomery Supply Control Tower

MG3 · Montgomery, AL · Warehouse Automation & Optimization concept
Live simulation 08:30

Scanning and Exception Management

Every pallet is checked at five scan points from the gate to the line. Problems are caught where they happen, routed to an owner and fixed before they reach SAP or Line 3.

Feeds Yard · Inventory · Line-Side

Scan journey · gate to line Red pallets drop into the exception lane

Handheld view RF scanner

MG3 RF-07Wi-Fi · 86%
ReadyOperator 14
LPN —

    Simulation triggers Click to run a scenario through the handheld

    Exceptions by type This shift

    Exception queue

    Where exceptions were stopped Earlier is cheaper

    How they were resolved Outcome mix

    Every resolution posts to SAP from the handheld: no paper, no re-keying at the desk.

    Material Inventory Control

    Every pallet scanned from dock to line, so SAP matches the floor and Line 3 is never starved or fed the wrong component.

    Team B · 11 votes · Priority 1

    Dock-to-line flow Click a pallet to trace its LPN

    Scanned LPN No label at dock Replenishment (kanban) QA hold

    LPN trace

    Select a pallet on the map to see its SKU, batch, location history and SAP postings.

    Event feed SAP / scanner

    SAP vs floor reconciliation Variances found by scan

    SKUSAPFloorCause

    Line 3 component cover Hours of supply · white tick = kanban min

    Yard and Trailer Storage

    Know what is in every trailer, SKU and quantity, on demand. Empties are flagged to carriers the moment they clear, cutting dwell and demurrage.

    Team A · 7 votes · Priority 2

    Live yard map Click a trailer for contents

    Loaded Partly consumed Empty · carrier notified Past free time At dock door Held by gate scan

    Trailer contents

    Select a trailer to see SKU, quantity, dwell and demurrage clock.

    Event feed LEAP / carrier

    Demurrage this month Simulated · manual notice vs auto notice

    Carrier turnaround Empty → pickup

    CarrierIn yardEmptiesAvg pickupStatus

    Line-Side Supply and Waste

    Stage ahead of every run, catch bad packaging before it reaches the line, and post waste to SAP as it happens.

    Team C · 4 votes · Priority 3

    Line 3 · Crown Royal 750 ml Click a machine for status

    Running Starved / waiting material Down Tugger cart

    Machine

    Select a machine to see state, cause and the component it consumes.

    Event feed Ignition / SAP

    Line-side exception triage Recommended action first · posts straight to SAP

    0open
    —avg time to triage
    0SAP postings from line
    0desk re-keys

    SAP postings from the line Material docs, QM and PM notifications

    TimeDocTxnMaterialQtyReason

    Next-run staging Run 3-118 · CR 750 ml

    CV incoming inspection Dock 4 camera

    scanning…
    LotItemResult

    Waste streams Auto write-off to SAP

    DocStreamQtyValue

    Consumption Funnel and Incident Control

    Follow every pallet from inbound to consumed on Line 3. Defects are pulled out at each stage, replenishment lands before a component runs out, and every task and event is kept for review.

    Line 3 · Crown Royal 750 ml

    Consumption funnel · this shift Pallet equivalents · red drops are defects removed

    Starvation radar Next 8 hours

    Cover Kanban trigger Replenishment en route

    Pre-emptive actions Acted before run-out

    Shift timeline Last 4 hours · click a marker

    Event Exception caught Pre-emptive replenishment Line stop (duration)
    Select a marker to see what happened, who owned it and how long it took.

    Task and event history

    Concept mockup for the Diageo × AWS discovery workshop, 17–18 Nov 2026. All figures are simulated and illustrative; nothing here is connected to SAP, LEAP or Ignition. Use case owners: Team B · Team A · Team C