Value Stream Mapping at Ports and Container Terminals: Unclogging the Gate-to-Berth Bottleneck

In the realm of container logistics, speed is only one part of performance. A terminal can operate powerful ship-to-shore cranes and still lose capacity through truck queues, delayed approvals, poorly sequenced yard moves, customs holds, and incomplete information.

Value Stream Mapping (VSM) makes these delays visible. It shows how containers, people, equipment, data and decisions move from one end of the terminal to the other. More importantly, it separates value-adding handling from the waiting and rework that extend vessel turnaround, truck turnaround and container dwell time.

For ports, the objective is not to make every activity faster in isolation. It is to improve the entire flow from gate to berth: and from berth back to gate.

The port infrastructure and process relationships described in this maritime port procedures mapping guide provide useful context for identifying the physical and information flows that a VSM should capture.

Select the Right Port Value Stream Before Mapping

A container terminal contains several overlapping value streams:

• Vessel arrival, berthing, discharge and departure
• Import container discharge to truck gate-out
• Export container gate-in to vessel loading
• Empty-container collection and return
• Customs, inspection and scanning
• Rail or inland barge transfer
• Reefer monitoring and specialised cargo handling

Do not attempt to map the entire port in one workshop. Begin with a defined product family, customer requirement and operating window.

A practical scope statement might be:

Map standard import containers from vessel arrival at Berth 3 through discharge, yard storage, release and truck gate-out, including the information flow required to authorise each movement.

The scope should identify:

1. Start point: vessel arrival or truck gate-in
2. End point: vessel departure or truck gate-out
3. Container family: standard dry import containers, for example
4. Customer: consignee, shipping line, trucking company or terminal operator
5. Critical-to-quality measures: dwell time, reliability, truck waiting time and cargo availability

This approach aligns with the Measure Phase principles in the Lean Six Sigma Practitioner’s Guide: define operational measures before collecting data.

Build the Current-State Map at the Gemba

A credible port VSM cannot be created solely from a terminal operating system report. Walk the process. Observe the gate, yard, control tower, inspection area and berth. Record what actually happens, including workarounds that may not appear in system data.

Capture both material flow and information flow.

Material flow

• Truck arrival and gate-in
• Security, document and equipment checks
• Weighing or scanning
• Yard dispatch
• Internal transport
• Container stacking and retrieval
• Inspection or customs transfer
• Quay-side positioning
• Ship-to-shore crane handling
• Truck gate-out or vessel departure

Information flow

• Booking and pre-arrival notices
• Manifest and bay plan
• Customs release
• Inspection instructions
• Truck appointments
• Yard location assignments
• Crane dispatch instructions
• Approvals and exception messages

For each step, record:

• Processing time
• Waiting time
• Queue size
• Number of handoffs
• Rework or repeat transactions
• Equipment and labour involved
• First-pass yield
• Constraint or failure condition

A Time Observation Sheet is particularly useful for separating actual handling time from waiting. For example, a truck may spend only 18 minutes receiving a container while remaining inside the terminal for 74 minutes.

Worked Example: An Import Flow at a Container Terminal

Consider an illustrative terminal handling 4,800 import containers per week. The project team maps one representative flow during a four-week baseline period.

The current-state map reveals the following sequence:

1. Vessel arrives and waits for berth allocation.
2. The ship is berthed and discharge begins.
3. Containers are transferred to the yard.
4. Containers wait for customs or inspection release.
5. Yard equipment retrieves the container.
6. A truck enters through the gate and waits for dispatch.
7. The container is loaded.
8. The truck completes exit processing.

The baseline data shows:

• Vessel turnaround: 36 hours
• Ship-to-shore crane productivity: 24 moves per hour
• Truck turnaround: 74 minutes
• Average truck waiting time: 31 minutes
• Container dwell time: 4.8 days
• Berth utilisation: 68%
• Total lead time from vessel arrival to truck gate-out: 149 hours

The terminal’s average is useful, but it does not tell the whole story. A box plot of truck turnaround data shows a median of 61 minutes, with the upper quartile at 86 minutes and several observations above 140 minutes. This variation indicates that the average is being influenced by exceptional delays.

The team also classifies gate outcomes using attribute data:

• Pass on first attempt
• Documentation exception
• Customs hold
• Equipment mismatch
• Yard location unavailable

Only 91.5% of transactions pass first time. The remaining 8.5% generate additional information exchanges, approval requests or truck repositioning.

In the Analyse Phase, the team uses Pareto analysis, process observation and a cause-and-effect diagram. Where data supports it, ANOVA compares average truck waiting time across shifts, while Bartlett’s Test checks whether group variances are sufficiently similar before interpreting the ANOVA result. This prevents the team from confusing a shift effect with inconsistent variation.

The main constraint is not crane speed alone. It is the interaction between yard availability, release information and truck dispatch. In Theory of Constraints terms, the effective constraint is the release-to-retrieval interface, which limits the flow reaching the gate.

The project’s cause-and-effect logic can be expressed as Y = f(x):

Truck turnaround and container dwell time are outcomes influenced by release timing, yard slotting, appointment discipline, dispatch accuracy and equipment availability.

Identify the Eight Wastes in Port Operations

A current-state VSM should explicitly mark the eight DOWNTIME wastes:

• Defects: incorrect container status, documentation errors or failed gate checks
• Overproduction: moving or staging containers before they are ready for the next customer step
• Waiting: trucks, containers, cranes, inspectors or information waiting for release
• Non-utilised talent: operators solving recurring issues without being involved in process redesign
• Transportation: unnecessary internal transfers or movement to distant inspection areas
• Inventory: excessive work in process, stacked containers and unclaimed units
• Motion: extra walking, driving, searching or equipment repositioning
• Extra-processing: duplicate data entry, repeated approvals and manual reconciliation

Work in process is especially important. A crowded yard may appear productive because it contains many containers, yet excessive WIP increases re-handling, retrieval time and storage pressure.

An Andon-style visual signal can alert the control tower when a container exceeds its planned release time or when a crane is waiting for a vehicle. In more advanced terminals, autonomation: or Jidoka: can combine system rules, sensors and exception alerts to stop or redirect a transaction before the issue propagates.

Design the Future-State Map

The future state should not be a wish list of technology projects. It should show a connected operating design with clear rules, ownership and measurable targets.

For the worked example, the team designs the following changes:

1. Level truck arrivals using appointment windows aligned with yard capacity.
2. Pre-clear documentation before vessel discharge is complete.
3. Reserve yard slots for released import containers.
4. Use pull-based dispatch so retrieval is triggered by confirmed truck readiness.
5. Reduce re-handling through improved stacking logic.
6. Create an exception lane for documentation and customs issues.
7. Use visual alerts when queue time exceeds the agreed threshold.
8. Review performance in short Agile improvement cycles, piloting one yard block before expanding the design.

The future state also balances the Voice of the Customer, the Voice of the Business and the Voice of the Process. The consignee wants predictable availability, the terminal wants higher throughput and asset utilisation, and the process data must confirm that the new design is stable.

Current versus future-state targets

These are illustrative project targets rather than universal port benchmarks. Each terminal should establish its own baseline, specification limits and operating conditions.

The team should also verify that the improvement is not creating a new bottleneck. Higher berth utilisation is valuable only if yard and gate capacity can support the additional flow. Similarly, reducing dwell time must not compromise safety, customs compliance or container integrity.

Sequence Kaizen Instead of Launching Everything at Once

A disciplined kaizen sequence protects operations while building momentum.

1. Stabilise the baseline

Confirm definitions for vessel turnaround, truck turnaround, dwell time and crane moves per hour. Check for measurement bias caused by inconsistent timestamps or missing transactions.

2. Remove visible information delays

Standardise pre-arrival data, approval rules and exception ownership. Formal approvals support governance, but unnecessary approval layers can become bottlenecks.

3. Pilot the gate-and-yard interface

Test appointment windows, pull dispatch and reserved slots in one operating zone. Compare average, variation, queue length and first-pass yield with the baseline.

4. Address the constraint

The Black Belt or project lead should focus improvement effort on the release-to-retrieval constraint rather than distributing resources evenly across every activity. A Yellow Belt can support observations, data collection and daily visual management.

5. Standardise and control

Create standard work, response rules and a dashboard for the critical metrics. An X-bar and R chart can monitor process averages and variation when the data structure is appropriate. For skewed waiting-time data, use distributions, percentiles and box plots rather than relying on the average alone.

Build the Capability to Improve the Whole Flow

Value Stream Mapping is most powerful when it becomes part of a broader DMAIC discipline. It connects customer requirements to operational facts, exposes waste without blaming individuals, and gives leaders a common language for prioritising improvement.

If you work in logistics, supply chain, operations, quality or terminal management, a structured Lean Six Sigma qualification can help you move from isolated fixes to measurable, end-to-end flow improvement.

Explore the Lean Six Sigma Yellow Belt certification to build practical improvement capability, or develop deeper project leadership skills through the Lean Six Sigma Green Belt course. Professionals leading complex, cross-functional transformations can also review the Black Belt programme.

Choose a Lean Six Sigma certification and learn to map, analyse and improve the flow that your customers depend on.

Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)