Transportation Demand and Freight Unit Building

Key takeaway

📌 KEY POINTS ✅ TM plans Freight Units, not raw source documents — FUBRs decide how demand is split or combined. ⚠️ One tiny FU per line item overloads the optimizer; over-aggregating breaks delivery-date and equipment-constraint accuracy. 💡 Always trace an FU back to its original order/delivery during support — that's the real audit trail. ━━━━━━━━━━━━━━━━━━━━ ▶ 1.

Explanation

📌 KEY POINTS
✅ TM plans Freight Units, not raw source documents — FUBRs decide how demand is split or combined.
⚠️ One tiny FU per line item overloads the optimizer; over-aggregating breaks delivery-date and equipment-constraint accuracy.
💡 Always trace an FU back to its original order/delivery during support — that's the real audit trail.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHERE DEMAND COMES FROM

Sales orders, purchase orders, stock transport orders, deliveries → transportation requirements → Freight Units (the planning-relevant object)

━━━━━━━━━━━━━━━━━━━━
▶ 2. FREIGHT UNIT BUILDING RULES (FUBR)

Split or combine by location, date, quantity, product property, or other supported attributes
The resulting FU carries origin, destination, quantity, dates, planning info

━━━━━━━━━━━━━━━━━━━━
⚠️ 3. THE GRANULARITY TRADE-OFF

Too many tiny FUs → optimizer/planner overload
Over-aggregated → can't represent delivery dates or equipment constraints correctly

━━━━━━━━━━━━━━━━━━━━
▶ 4. LATE CHANGES

Source changes can update demand until execution status/process rules limit it
Planners must know when a late change needs a rebuild vs. a replan

✅ CHECKPOINT: explain the granularity trade-off in FU building, in one sentence.

Real project scenario

A distributor created one freight unit per order item, producing tens of thousands of planning objects. A revised FUBR consolidated compatible items by location and date, simplifying planning without losing business constraints.

Common mistakes

Treating freight unit as the source delivery itself.
Over-splitting demand.
Aggregating incompatible dates or locations.
Ignoring source changes.
Troubleshooting FU without original document reference.

Best practices

Design FUBR with real shipment patterns.
Preserve source references.
Measure FU granularity.
Test late source changes.
Keep business constraints visible.

Interview angle

Explain transportation requirement, Freight Unit Building Rule and freight unit in sequence.

Practice this lesson

Quick check

1. In the lesson "Transportation Demand and Freight Unit Building", consider this project situation: A distributor created one freight unit per order item, producing tens of thousands of planning objects. Which statement is correct?

2. For Transportation Demand, Freight Units and Planning, consider this mapped project scenario from Freight Units: Building Transportation Demand from Orders and Deliveries: A company generated one freight unit per sales-order item, creating tens of thousands of tiny planning objects. Which response best addresses the underlying risk?

3. While applying Freight Units: Building Transportation Demand from Orders and Deliveries to Transportation Demand, Freight Units and Planning, a team follows this risky pattern: "Applying one tendering strategy uniformly across all lanes regardless of contractual relationships". Which correction is most appropriate?

Interview questions

1. A project team is working on Transportation Demand, Freight Units and Planning. Using the Transportation Demand and Freight Unit Building scenario, how would you approach the requirement from design through validation?

Answer it in your own words first, then compare.

2. What design decisions and trade-offs matter most when implementing Transportation Demand, Freight Units and Planning, particularly for Transportation Demand and Freight Unit Building?