Logistics and Supply Chain Project Management (TUT) Notes (MG? / PM / Supply Chain Project Modules)

Logistics and supply chain project management blends project management fundamentals with the practical realities of procurement, warehousing, transport, inventory, and service-level performance. In a TUT-style project-management context, you’re expected to plan and control projects that build or improve supply chain capabilities—such as new distribution centres, warehouse automation, multimodal routing strategies, or process redesign across suppliers, depots, and customers. These exam notes align with common South African university study patterns and terminology you’ll see in TUT project management modules and related supply chain/project courses.

Section 1: Foundations of Logistics, Supply Chain, and Project Management in the TUT Context

Why “logistics” and “supply chain” are not the same

Students often mix up logistics and supply chain management because both deal with moving and storing goods. The difference is mostly about scope:

• Logistics: the functional activities of planning, implementing, and controlling the flow and storage of goods, services, and related information within and across organizations. Typical logistics functions:
  • Transportation management (road, rail, air, sea; fleet and routing)
  • Warehousing and materials handling
  • Inventory control
  • Order fulfilment
  • Customer delivery coordination
• Supply chain management (SCM): a broader, end-to-end approach that coordinates all upstream and downstream activities involved in:
  • Sourcing (suppliers)
  • Production or transformation (manufacturing/assembly)
  • Logistics and distribution
  • Retail/wholesaling
  • Service and returns
  • Information sharing and relationship management

In project management terms, SCM improvements are usually multi-functional and cross-company, which increases complexity: more stakeholders, more dependencies, more risks.

Core logistics performance metrics you’ll see in project questions

Exam-style questions often ask you to interpret data or propose improvements. That requires knowing common logistics KPIs:

1. Fill rate / service level
   • Example definition: percentage of customer orders delivered complete and on time.
2. On-time in-full (OTIF)
   • Orders delivered on time and with correct quantity.
3. Order cycle time
   • Time from order placement to delivery.
4. Inventory turns
   • Cost of goods sold / average inventory.
5. Stockouts and backorders
6. Forecast accuracy
7. Transportation cost per unit / per ton-km
8. Warehouse productivity
   • Cases picked per hour; labour utilisation; space utilisation.
9. Damages/returns rate
10. Total supply chain cost
    • Not just transport: includes inventory carrying costs, handling, quality losses, and reverse logistics.

Quantitative link to project decisions

A project manager might change a distribution network and expect:

• Lower transport cost
• Higher service levels
• But possibly higher inventory or higher capital expenditure.

So you need to think in trade-offs and justify decisions with KPIs.

Project management fundamentals applied to logistics and supply chain

In a TUT project-management course context, you’re typically assessed on the ability to use structured project management techniques: initiation, planning, executing, monitoring & controlling, closing, and managing integration, scope, schedule, cost, quality, risk, and stakeholder expectations.

A useful approach is to treat logistics/SCM projects as operations + change management projects:

• Operations side: process design, systems, people training, capacity planning.
• Change side: stakeholder alignment, adoption, governance, communication.

The five process groups (common exam framing)

1. Initiating
   • Define the project purpose: why build/upgrade/change?
   • Identify stakeholders: suppliers, customers, internal operations, procurement, finance, IT, labour representatives.
2. Planning
   • Scope, schedule, budget, procurement plan, resource plan.
   • Define quality standards and performance measurement plan.
3. Executing
   • Implement process changes, build sites, install systems, train staff.
4. Monitoring & controlling
   • Track progress (earned value or simpler variance analysis), manage risks, control changes.
5. Closing
   • Hand-over, final acceptance, lessons learned, benefits realisation.

Logistics and supply chain project types (what exam questions often target)

A wide range of project types can appear:

• Distribution network design
  • Selecting facility locations and defining service territories.
• Warehouse projects
  • New warehouses, layout redesign, automated storage and retrieval systems (AS/RS), WMS deployment.
• Transport and routing initiatives
  • Fleet acquisition/outsourcing, new routing policies, carrier contract redesign.
• Inventory policy projects
  • Reorder points, safety stock policy changes, multi-echelon inventory strategies.
• Procurement and supplier development
  • Supplier qualification, contract frameworks, lead-time reduction programmes.
• IT and systems projects
  • ERP/WMS/TMS implementations, EDI integration, visibility platforms.
• Process improvement projects
  • Lean logistics, Six Sigma for returns/damage reduction.
• Reverse logistics and returns programmes
  • Customer returns handling, repair/refurbishment process design.

A good exam answer connects project objectives to logistics KPIs and identifies constraints (budget, lead times, regulatory requirements, transport capacity, power and utilities in warehouses, and labour availability).

Stakeholder and governance complexity in SCM projects

Supply chain projects commonly involve cross-company and cross-functional stakeholders. Typical stakeholder groups:

• Project sponsor (e.g., Operations Director)
• Project manager (TUT expects you can coordinate planning and control)
• Procurement (contracting and supplier management)
• Logistics operations (warehouse, transport, planning)
• IT/Systems (WMS/TMS integration)
• Finance (budget, capex approval, costing model)
• Quality and compliance (SOPs, food safety, dangerous goods rules)
• HR/Labour (training and workforce readiness)
• External stakeholders
  • Carriers, third-party logistics providers (3PLs)
  • Manufacturers and suppliers
  • Customers and retailers

Governance structures for such projects often include:

• Steering committee meetings
• Stage-gate approvals (especially for capital-intensive warehouse/distribution projects)
• Change control board for scope/schedule changes

Mini case study: A warehouse WMS implementation project (how to structure answers)

Scenario (exam-style): A retailer wants to implement a Warehouse Management System (WMS) to improve picking accuracy and reduce order cycle times. The warehouse currently relies on manual scanning and paper-based picking lists.

Typical project objective statement:

• Improve picking accuracy from a baseline (e.g., “current error rate”) to a target.
• Reduce average order cycle time.
• Provide real-time inventory visibility.

Stakeholders:

• Warehouse manager, WMS vendor, IT team, procurement, finance, customer service.

Key planning elements you should write:

1. Scope: system configuration, integrations (ERP), hardware (handheld scanners), training.
2. Schedule: pilot phase, warehouse-wide rollout, parallel run.
3. Cost: licensing, implementation consulting, hardware, training, change management.
4. Risks: data migration errors, downtime during go-live, user adoption.
5. Quality: test scripts, acceptance criteria, KPI verification plan.

Monitoring:

• Weekly progress report, defect tracking, acceptance sign-off checkpoints.
• KPI monitoring (accuracy, cycle time, inventory variance).

This kind of structured response is often what TUT exam questions look for: a blend of project management process thinking and logistics operational detail.

Section 2: Planning and Designing Logistics/Supply Chain Projects (Scope, Network, Cost, and Schedule)

Translating business needs into project scope (scope clarity)

Supply chain and logistics projects fail often because the scope is fuzzy: stakeholders expect results that aren’t in the deliverables. In logistics terms, scope should specify:

• What will change?
  • e.g., “design a new cross-dock process” or “implement a WMS in DC1 only”.
• Where will it happen?
  • a specific warehouse/depot or multiple regions.
• When will it go live?
  • go-live date and whether there is a parallel run.
• To what standard?
  • quality and service-level targets.
• What is excluded?
  • e.g., “does not include new fleet procurement”.

A scope example (how to answer in exams)

If the project is to reduce OTIF problems, scope might include:

• process redesign for receiving and dispatch
• training for picking/packing staff
• WMS configuration for batch and zone picking logic
• integration for order data feeds from ERP

But it might exclude:

• changing supplier lead times
• redesigning product packaging SKUs
• re-negotiating transport contracts

Logistics network design and project objectives

Distribution network design is one of the most exam-popular topics because it links strategy with quantitative thinking.

Common design decisions:

• number and location of warehouses/depots
• whether to use a central warehouse or multiple regional ones
• direct shipping vs. hub-and-spoke
• cross-docking vs. storing
• carrier strategy: internal fleet vs. outsourced carriers vs. 3PL

Hub-and-spoke vs. direct delivery (exam comparison)

• Hub-and-spoke
  • Pros: consolidates shipments; can reduce transport cost.
  • Cons: adds handling steps; may increase cycle time and complexity.
• Direct delivery
  • Pros: potentially faster; fewer handoffs; simpler tracking.
  • Cons: less consolidation; potentially higher transport cost per unit.

A project manager should not just state “one is better”. They should show:

• service-level requirements
• demand patterns
• cost drivers: transport cost, inventory carrying cost, facility capex/opex, handling cost

Capacity planning: warehousing, labour, transport, and “bottlenecks”

Capacity constraints drive scheduling and operational readiness. Exam questions often ask you to identify bottlenecks.

Key capacity elements:

• Receiving capacity (dock doors, unloading process, inbound truck scheduling)
• Storage capacity (rack space, safety stock levels)
• Picking capacity (picking lanes, labour allocation, zone strategy)
• Packing capacity (packing stations, packaging materials)
• Loading capacity
• IT system capacity (number of concurrent users, network reliability)
• Transportation capacity
  • available trucks/tonnage; carrier lead times; planned routes

Bottleneck example logic

If picking becomes the constraint:

• Even if storage and receiving are adequate, orders can’t leave on time.
• Project remedies include:
  • redesign picking strategy (zone picking, batch picking)
  • train or add labour temporarily
  • improve slotting and pick-path optimisation
  • upgrade system workflow (WMS tasking)

If transport becomes the constraint:

• Warehouse output could be high but trucks can’t depart in required windows.
• Remedies include:
  • carrier contract redesign with service-level clauses
  • better yard management and appointment scheduling
  • adjust release schedules

Cost structure in logistics projects (what “cost” really includes)

In project management, you calculate costs for budgets and cost control. Logistics projects have cost categories:

• Capital expenditure (Capex)
  • warehouse build, equipment installation, automation, systems hardware.
• Operating expenditure (Opex)
  • labour, maintenance, utilities, software subscriptions.
• Implementation cost
  • consultants, system integration, training, cutover support.
• Transaction and contracting costs
  • contract management, supplier switching costs, legal fees.
• Inventory-related costs
  • safety stock, holding costs, obsolescence, write-offs.
• Service-related costs
  • expedite shipping, penalties, loss of goodwill, customer credits.
• Risk and contingency
  • budget for uncertainties and changes.

Example: evaluating transport + inventory trade-offs

Suppose you shift from a central warehouse to regional warehouses:

• Transport cost per shipment might decrease due to shorter distances.
• But you may need higher total inventory due to safety stock in multiple locations unless you use better inventory pooling strategies.

An exam answer should show you understand this interplay:

• reduce transport cost vs. increase inventory carrying cost
• reduce stockouts vs. increase capex and operating cost

Scheduling logistics projects: from milestones to go-live

Schedule planning should reflect logistics realities: cutovers, downtime windows, supplier lead times, training timelines.

A typical schedule structure for a logistics systems project

1. Requirements and process mapping
2. Vendor selection/contracting (if applicable)
3. Data cleansing and master data setup
4. Configuration and integration testing
5. Hardware installation
6. User training (super users first, then general users)
7. Pilot in a smaller area/shift
8. Parallel run (if used)
9. Cutover and go-live
10. Stabilisation period and final acceptance

Scheduling techniques you may be expected to know

• Work Breakdown Structure (WBS) for logistics projects.
• Gantt charts for timeline visualization.
• Critical Path Method (CPM) to identify tasks that cannot slip without delaying the whole project.
• Resource loading for labour-heavy periods (training, pilot operations).

Exam tip: “critical path” in a logistics context

If “data migration” depends on “system configuration freeze”, and “user training” depends on “system readiness”, then configuration and data migration often become critical. Any delays affect go-live.

Risk planning: logistics-specific risk categories

Risk management should be explicit and logistics-oriented. Typical logistics project risks:

1. Supply risks
   • supplier lead time delays
   • single-source dependencies
2. Operational risks
   • labour shortages
   • equipment downtime (forklifts, conveyor systems, scanners)
3. IT/system risks
   • integration failures
   • data migration errors
   • network downtime
4. Quality risks
   • incorrect item master data leading to mispicks
   • compliance failures (e.g., temperature control for cold chain)
5. Demand/service risks
   • peak season demand causing capacity overload
6. Change adoption risks
   • staff resistance, training gaps
7. Contracting and governance risks
   • unclear SLAs with carriers or vendors
   • scope creep

A strong exam answer lists:

• risk event
• cause
• impact on schedule/cost/service
• probability (qualitative)
• mitigation and contingency actions

Procurement planning and vendor selection (logistics supply chain style)

In logistics projects, procurement often involves:

• selecting a WMS/TMS vendor or consultant partner
• contracting 3PL providers
• procuring automation equipment (conveyors, sorters)
• buying scanners/printers

Exam questions may ask you to describe procurement planning steps:

1. Define procurement needs and scope of vendor work.
2. Decide procurement strategy:
   • fixed-price vs. time-and-materials (T&M)
   • single-vendor vs. multi-vendor solutions
3. Create evaluation criteria:
   • experience, references, implementation timeline, cost, support model
4. Manage vendor performance and SLAs:
   • uptime
   • response time
   • delivery acceptance criteria
5. Contract management:
   • change order handling
   • penalties/bonuses tied to service levels

Example of SLAs for a 3PL transport contract

• OTIF minimum percentage per month
• maximum allowable late deliveries
• compensation for damages beyond threshold
• tracking/visibility requirements (GPS scan events, ETAs)

Mini case study: Distribution centre redesign project (network + schedule + cost)

Scenario: A beverage distributor faces frequent stockouts in two regions and long order cycle times. Management proposes:

• redesign distribution network using a central DC + two regional depots
• implement improved scheduling and dock appointment system
• train staff and update SOPs

Exam-grade structure:

• Scope: network change, depot setup processes, dock scheduling SOPs, training, performance KPIs.
• Schedule: phased rollout by region; depot readiness; transport contract transition.
• Cost: capex for depot improvements; increased labour during transition; expected reduction in stockout penalties and expedite shipping.
• Risks: supplier lead time issues for new depot inventory; transport transition disruption; WMS integration if systems are used.
• KPIs: OTIF, stockout rate, order cycle time, warehouse utilisation.

Section 3: Execution, Monitoring & Controlling Logistics Projects (Quality, Integration, KPIs, and Change)

Executing logistics projects without breaking operations

A key challenge is executing while maintaining continuity of service. Many logistics projects cannot fully stop operations.

Common execution strategies:

• Phased rollout
  • pilot in one warehouse or one product category, then scale.
• Parallel run
  • old and new systems/processes run simultaneously for a period.
• Big-bang go-live
  • switch at once (riskier, used when systems are mature and downtime is manageable).
• Cutover windows
  • perform transition during low-demand periods.

Example: WMS cutover planning

Execution steps typically include:

1. Freeze master data changes before migration window.
2. Create test scenarios for top SKUs and high-volume routes.
3. Train pickers using real warehouse zones and tasks.
4. Define escalation paths:
   • who approves emergency overrides
   • who resolves system faults
5. Establish “hypercare” period:
   • daily support meetings
   • rapid fix cycle for issues

Quality management in logistics and supply chain

Quality in logistics is not only about product quality. It includes process quality:

• correct picking and packing
• accurate inventory records
• safe material handling
• compliance with temperature, hygiene, hazardous goods standards
• documentation quality: bills of lading, manifests, proof of delivery

Quality planning components

• Quality plan with standards and acceptance criteria
• Inspection and testing:
  • test inventory transactions and pick/pack confirmations
  • load testing for system performance
• Process control:
  • SOPs, checklists, and error-proofing
• Root-cause analysis for failures:
  • use 5 Whys or fishbone diagrams
• Continuous improvement:
  • feedback loops from customers and warehouse operators

Integrated change control: scope creep and operational realities

SCM projects face constant change:

• new regulatory requirements
• supplier changes
• customer order profile changes
• technology upgrades mid-project

Integrated change control is essential:

1. Identify change requests
2. Evaluate impact on:
   • scope, schedule, cost, quality, risk
3. Approve/reject changes through change control board (CCB)
4. Update baselines and communicate decisions

Operational example of change impact

If “additional warehouse zones” are added to WMS scope late:

• it increases configuration effort
• increases testing cycles
• increases training time
• may shift go-live date, especially if the critical path includes data migration

An exam answer should mention:

• baseline management (original plan vs. updated plan)
• documentation: change logs, version control

Monitoring and controlling: KPIs, schedule, and cost variances

Monitoring schedule performance

Common metrics:

• Planned Value (PV)
• Earned Value (EV)
• Actual Cost (AC)
• Schedule Variance (SV = EV − PV)
• Cost Variance (CV = EV − AC)

While many TUT exam questions may not require earned value calculations numerically, you should know how monitoring works conceptually.

Logistics KPI monitoring examples

• If OTIF declines:
  • examine transport delays (carrier performance)
  • check warehouse picking accuracy
  • review order release timing
• If inventory accuracy declines:
  • investigate receiving scan discipline
  • verify cycle count process
  • check WMS transaction processing logic

Benefits realisation: proving the project worked

A project is not “done” when deliverables are installed; it’s done when benefits are achieved.

Benefits realisation planning can be structured as:

• Identify benefit and KPI baseline
• Define target improvement
• Set measurement period (post go-live weeks/months)
• Assign responsibility (operations vs. project team)

Benefits in logistics often include:

• reduced stockouts
• improved OTIF
• reduced damages and returns
• reduced cycle time
• reduced cost per order or cost per shipment

Example: benefits plan for a distribution improvement project

• Baseline OTIF: measured for one or two months before change.
• Target: increase OTIF in the rollout regions.
• Measurement:
  • compare post-rollout months to baseline.
• Ownership:
  • operations owns KPI; project team supports initial measurement.

Conflict and stakeholder management during execution

Execution introduces friction:

• warehouse staff may resist new scanning routines
• IT may experience performance problems during peak loads
• procurement may dispute vendor responsibilities

Exam-ready stakeholder practices:

• Communication plan:
  • daily stand-ups for cutover teams
  • weekly steering committee reports
  • immediate incident communication during hypercare
• Issue logs and escalation:
  • how issues are triaged
  • who resolves them
• Negotiation and alignment:
  • define service-level expectations in contract and in operational SOPs

Mini case study: Reducing order cycle time through process redesign

Scenario: A retailer finds that order cycle time is long due to:

• delayed receiving approvals
• inefficient picking paths
• late dispatch release

Project execution approach:

1. Process mapping identifies “waiting time” between steps.
2. Implement receiving appointment scheduling and quality clearance workflow.
3. Introduce zone picking and batch picking rules.
4. Set dispatch release cutoffs tied to carrier departure schedules.
5. Train staff and update SOPs.

Monitoring approach:

• measure cycle time by order stage (receipt-to-putaway, pick-to-pack, pack-to-dispatch)
• track defects (wrong picks) and rework volumes
• adjust resource allocations during peak days

This case demonstrates that in logistics project management, the deliverable might be “process capability improvement”, not just a system upgrade.

Section 4: Supply Chain Project Finance, Contracting, Procurement Strategy, and Sustainability (Risk, Contracts, and Trade-offs)

Project financing basics for logistics initiatives

While many project management modules focus on general budgeting, logistics projects have a specific financing reality:

• capex is often large (warehouses, automation, material handling equipment)
• benefits may be realized over time (service improvements, cost savings)
• demand uncertainty may make payback periods risky

Key financial planning concepts:

• Budgeting across capex and opex
• Cashflow planning: timing matters because capex payments occur before benefits fully materialize.
• Contingency reserves for schedule and scope uncertainties.
• Cost-benefit analysis and business case alignment.

Example of cost-benefit logic

• Capex: warehouse automation equipment
• Opex change: reduced labour per picked unit; higher maintenance cost
• Benefit: reduced picking errors and faster fulfilment
• Additional benefit: reduced lost sales due to improved service level

Even when exam questions don’t ask for exact NPV/IRR, they may ask for reasoning: “how do you justify this expenditure?”

Contracting and procurement strategy: choosing the right commercial model

Logistics projects may use:

• Fixed-price contracts for scope-stable deliverables
• Time-and-materials (T&M) for uncertain scope (e.g., complex system integration where requirements evolve)
• Unit-price contracts (common in construction and sometimes logistics services measured per unit)
• Performance-based contracts
  • penalties/bonuses tied to KPIs like OTIF, damages, or uptime

Example: carrier contract with performance incentives

A contract might specify:

• base rate per shipment
• bonus for OTIF above a threshold
• penalty for late deliveries or damages above a threshold

This links commercial incentives to operational KPIs, improving accountability.

Procurement lifecycle and supplier management

Effective procurement in logistics projects includes:

1. Needs assessment and make/buy decisions
2. Supplier identification and market research
3. RFP/RFQ development
4. Evaluation and selection
5. Contract negotiation
6. Supplier onboarding
7. Ongoing supplier performance management

Supplier performance management can include:

• delivery lead time adherence
• quality failure rate
• documentation compliance
• responsiveness and corrective action time

Corrective action processes (exam-grade content)

When supplier issues occur:

• root cause analysis
• containment actions
• corrective and preventive actions (CAPA)
• verification and closure criteria

Risk allocation in contracts (how to handle uncertainty)

A powerful exam answer mentions that contracts manage risk allocation:

• Who bears the risk of delays: vendor or contractor?
• Who pays for change requests outside baseline scope?
• What happens if system integration fails due to unclear requirements?
• Are there penalties for missed milestones?

Risk mitigation also happens through:

• staged payments based on milestones
• acceptance tests
• clearly defined deliverables
• documentation requirements
• service level agreements

Sustainability and compliance in logistics project management

South African logistics projects increasingly face pressure related to:

• environmental compliance
• energy efficiency and emissions considerations
• labour and safety regulations
• product traceability and regulated supply chains (food, pharmaceuticals)

Sustainability considerations can be integrated into project design:

• reduce unnecessary transport through better route planning and load consolidation
• optimise warehousing energy usage (lighting, HVAC where applicable)
• adopt greener packaging practices
• improve load factors and reduce empty kilometres

Exam application: “green logistics” as a project objective

If sustainability is an objective, KPIs might include:

• reductions in fuel consumption
• improved utilisation of vehicle capacity
• reduced waste from packaging and damage
• improved recycling rates in returns processing

But an exam answer should avoid vague claims: connect sustainability to measurable operations and project deliverables.

Reverse logistics projects: returns, repairs, and closed-loop improvement

Reverse logistics often becomes a major cost driver. Projects may focus on:

• returns inspection centres
• refurbishment workflows
• spare parts logistics
• disposition policies: return to stock vs. refurbish vs. scrap

Key project design elements:

• define return categories and decision criteria
• design inventory and system treatment for returns
• set SLAs for inspection and disposition
• ensure traceability and quality controls

Example: reducing returns processing time

If returns processing is slow:

• customer refunds are delayed
• inventory is “stuck” in returns
• resale or refurb refurbishment opportunities are reduced

A project can redesign:

• receiving and inspection workflow
• appointment scheduling for returned items
• WMS configuration for reverse inventory states

Counter-argument discussion: why “outsourcing everything” may be risky

A common exam question is to discuss whether to use 3PLs.

Potential benefits of outsourcing:

• access to logistics expertise
• scalability during peak season
• potentially lower unit costs

But risks include:

• reduced control over service quality
• confidentiality and data integration problems (ERP/WMS)
• dependency on external carriers
• contract disputes when KPIs are unclear

A good answer balances:

• internal capability vs. external maturity
• contract quality and SLA enforceability
• transition plan and governance

Section 5: Integrated Logistics/Supply Chain Project Lifecycle, Tools, and Exam-Ready Problem Solving

Building an exam-ready project plan structure (what markers expect)

When you’re given a scenario in an exam, your best responses typically have these elements:

1. Project objective
   • A clear statement linked to logistics KPIs.
2. Scope definition
   • in-scope and out-of-scope.
3. Work breakdown structure (WBS) outline
   • major deliverables and sub-deliverables.
4. Schedule logic
   • milestones, critical dependencies, and rollout approach.
5. Resource plan
   • key roles: logistics lead, procurement, IT, training coordinator.
6. Cost/budget narrative
   • capex/opex, implementation cost categories.
7. Risk register outline
   • at least 5 risks with mitigations.
8. Quality management
   • acceptance tests, SOP updates, KPI measurement.
9. Stakeholder engagement plan
   • communication channels and decision points.
10. Monitoring and control

• KPIs + schedule and cost tracking.

11. Closure and handover

• training complete, acceptance sign-off, lessons learned.

Tools you should be able to apply quickly

1) WBS (Work Breakdown Structure)

A WBS for a logistics project can be structured by deliverables, for example:

• system configuration
• data migration
• hardware installation
• training
• pilot and go-live support
• SOP development

2) Gantt chart logic (without drawing)

In exams, you may not need to draw a chart, but you should describe:

• tasks and their order
• estimated durations
• milestone dates
• dependencies

3) Risk register template (exam-friendly)

A risk register typically includes:

• Risk ID
• Description
• Probability (Low/Med/High)
• Impact (Low/Med/High)
• Owner
• Mitigation
• Contingency

4) KPI dashboard reasoning

Explain what you would monitor:

• OTIF, fill rate, cycle time, inventory accuracy, damages
• and how you would react to trends.

Worked exam-style example: planning a multimodal transport optimisation project

Scenario: A logistics company wants to reduce delivery times and transport costs for a set of routes by introducing a multimodal plan (e.g., road for pickup and rail for trunk line, or road + intermodal where appropriate). The project includes:

• carrier contracting adjustments
• new routing policy
• dispatch planning changes
• tracking improvements

1) Objective

• Improve OTIF and reduce average delivery cycle time.

2) Scope

• Route selection and routing policy design
• Carrier contract modifications and onboarding
• Dispatch planning SOP changes
• Tracking integration for visibility (e.g., scan events for handoffs)
• Training dispatch teams

3) Out of scope

• Changing product packaging
• Changing supplier lead times

4) Schedule approach

• Phase 1: route analysis and pilot on 1–2 routes
• Phase 2: scale routing policy to full network
• Hypercare during peak period

5) Cost categories

• contract changes (commercial cost)
• system/tracking upgrades (if required)
• training and implementation costs
• contingency for disruptions (damages, rerouting)

6) Risk examples

• rail schedule variability causing missed handoffs
• carrier performance mismatch
• tracking gaps during handoff transitions
• dispatch team adoption problems

7) Monitoring

• OTIF by route and week
• cycle time distribution
• incident count and root cause categories
• cost per shipment and cost per ton-km (conceptually)

This example demonstrates integrated planning: project management structure + logistics operational detail.

Worked exam-style example: warehouse layout redesign project

Scenario: A DC experiences congestion at picking and frequent misplaced stock. The solution is a layout redesign:

• new slotting strategy
• rearranged picking zones
• improved material handling path
• cycle counting frequency changes

Project objectives:

• reduce picking congestion
• improve inventory accuracy
• reduce order cycle time

Scope:

• redesign layout (physical changes)
• update SOPs for picking, putaway, and cycle counts
• training for staff
• adjust WMS configuration if used

Risks:

• safety incidents during construction changes
• temporary disruption to picking productivity
• inaccurate slotting causing mispicks
• inaccurate cycle count process transition

Quality acceptance:

• productivity measures (e.g., items picked per hour, orders completed per shift)
• inventory accuracy checks (variance measurement)
• sampling audits for picks and placements

Counter-argument and trade-off questions (how to score higher)

Many logistics project management questions ask “justify” or “discuss advantages and disadvantages.” To score higher:

• Present a balanced view with specific risks and mitigations.
• Use “therefore” reasoning: trade-off leads to a decision criterion.

Example: “Is automation always better?”

Pro-automation points:

• higher throughput and consistency
• reduces human error with scanning/automation controls
• improves traceability

Anti-automation points:

• high capex and long implementation lead times
• risk if processes are not standardized first
• training and change adoption challenges
• maintenance dependencies and downtime risk

Good conclusion:

• automation should follow process standardisation, not replace it blindly.
• use pilot studies and stage-gate approvals.

South African university study framing: aligning to common TUT project management expectations

TUT modules in Project Management typically emphasise:

• structured project lifecycle
• integration of planning, monitoring and control
• stakeholder management
• basic project finance and procurement planning concepts
• risk and quality thinking
• practical application to real-world scenarios

In logistics and supply chain projects, the “real-world scenarios” should reflect:

• multi-stakeholder environments
• operational constraints (capacity, lead times, service requirements)
• system integration and data accuracy
• measurable outcomes via KPIs

Even if a question is theoretical, your answers should connect back to operational logistics consequences: OTIF, cycle time, inventory accuracy, and total cost.

Exam strategy: how to answer typical question types

1) “Explain” questions

Use a clear structure:

• define concept
• provide logistics-specific examples
• link to project management practice (where it fits in lifecycle)

2) “Discuss” questions

Use balanced arguments:

• advantages
• disadvantages
• under what conditions one approach is preferred

3) “Recommend” questions

Include:

• your recommendation
• justification using KPIs and risks
• implementation approach and monitoring plan

4) “Scenario-based” questions

Use the project plan structure checklist:

• objective, scope, schedule, budget logic, risks, quality, stakeholder communication, KPIs

Consolidated glossary (high-frequency terms)

• OTIF: On-Time In-Full delivery performance metric.
• WMS: Warehouse Management System.
• TMS: Transportation Management System.
• 3PL: Third-Party Logistics provider.
• Capex: Capital expenditure.
• Opex: Operating expenditure.
• SLA: Service Level Agreement.
• Cycle counting: inventory checking process to maintain accuracy.
• Safety stock: inventory held to mitigate demand/lead-time variability.
• Cross-docking: handling goods directly from inbound to outbound with minimal storage time.
• Hypercare: intensive support period after go-live.

Final synthesis: how the pieces fit together

Logistics and supply chain project management is best understood as a cycle of alignment and control:

1. Strategic need → project objective expressed in logistics KPIs (OTIF, cycle time, inventory accuracy).
2. Scope and network/process design create operational deliverables.
3. Planning (schedule, cost, resources, procurement) accounts for logistics constraints like lead times and cutovers.
4. Execution uses phased rollout, training, and cutover governance to protect service continuity.
5. Monitoring and controlling focuses on KPI trends plus project variance management and risk updates.
6. Benefits realisation and closure ensures improvements last beyond installation.

This integrated approach is what exam questions test: not only definitions, but your ability to structure a credible plan, manage trade-offs, and justify decisions with logistics performance outcomes.