1.8 Supplier commit control & expediting
A Purchase Order outlines your requested demand; the Supplier Acknowledgement (ACK) confirms the actual commitment. The difference between the “Requested Date” and the “Committed Date” is a critical point in supply chain management. For a “Clear-to-Build” (CTB) signal to be accurate, the ERP system must reflect the vendor’s actual physical promise, rather than the initial operational request.
Commit date management rules
Section titled “Commit date management rules”The “Current Promise Date” field within the ERP drives the accuracy of the master manufacturing schedule, dictating whether production lines will have the necessary materials to run.
Rule 1: the ACK confirmation
Section titled “Rule 1: the ACK confirmation”- The Protocol: Upon receipt of the formal Supplier ACK (expected within a short window, e.g. 48 hours of PO issuance), the ERP “Promise Date” must be updated to match the vendor’s confirmed date.
- The Check: If the Vendor Commit Date is significantly past your required Need Date, the system should flag this as a potential shortage to the Planning team.
Rule 2: delivery verification protocol
Section titled “Rule 2: delivery verification protocol”- The Concept: A delivery promise made weeks in advance may shift. Proactive verification helps catch slips before they impact production.
- The Practice:
- Weeks Prior: An automated re-confirmation request should be sent to the vendor (“Is this still on schedule?”).
- Days Prior: Tracking information or Proof of Shipment (e.g. AWB Tracking number) must be requested.
Rule 3: managing date changes
Section titled “Rule 3: managing date changes”- The Expectation: Vendors should notify Procurement before updating delivery dates or shipping late. Unilateral date changes on B2B portals without communication disrupt planning.
- The Metric: These uncommunicated changes must be tracked as part of the Quarterly On-Time Delivery (OTD) scoring process to encourage better supplier communication.
Operational impact: CTB & ATP
Section titled “Operational impact: CTB & ATP”Procurement data feeds directly into overall business planning. Accuracy is essential for smooth operations.
- CTB (Clear-to-Build): If an ERP Commit Date slips past the Production Start Date, the Work Order becomes blocked, and kits cannot be pulled from the warehouse until the material arrives.
- ATP (Available-to-Promise): The Sales team relies on material arrival dates to promise finished goods to customers. If PO Commit Dates are missing or inaccurate, the factory cannot provide reliable completion dates.
Managing partial shipments
Section titled “Managing partial shipments”Suppliers may offer partial shipments to mitigate delays. Deciding to accept them involves balancing setup costs against stockout risks.
When the Partial Qty is equal to or greater than a Full Production Run (e.g. sufficient for a complete batch):
- It is often beneficial to accept the partial shipment. This allows the SMT line to run efficiently without requiring mid-run machine changeovers.
When the Partial Qty is less than a Minimum Run Size:
- Rejecting the partial should be considered unless a line-down situation is imminent. Loading a small partial reel to build only a few boards can be inefficient regarding machine setup time and receiving overhead.
Substitution approval workflow
Section titled “Substitution approval workflow”When a vendor cannot meet a delivery date, they may suggest a “functional equivalent.” Proper evaluation of these suggestions is crucial for product quality.
The Protocol:
- The Request: The Procurement team receives the substitution offer.
- The Verification: The physical package and pinout must be ensured to be identical to the original requirement.
- The Engineering Review: Design Engineering must validate the electrical parameters (Voltage, Tolerance, Temp Range) to ensure functional parity.
- The Action:
- If Engineering approves the substitution, the PO must be revised explicitly to the new MPN.
- It is important that Receiving QA inspects parts against a PO that matches the actual MPN received to maintain accurate inventory traceability.
Expediting decisions
Section titled “Expediting decisions”When critical parts are delayed, a structured approach must be used to determine the appropriate response and escalation level.
| The Scenario | The Business Impact | The Action | Typical Escalation Level |
|---|---|---|---|
| Minor Slip | Minimal | The ERP Commit Date must be updated and the shipment monitored closely. | Buyer |
| Moderate Slip | Risk to Safety Stock | Expediting (e.g. Air Freight) must be requested from the supplier. | Sr. Buyer |
| Line Stop (Soft) | Reschedule Required | The cost of premium freight must be evaluated against the financial impact of the delay. | Commodity Manager |
| Line Stop (Hard) | Risk to Customer Delivery | This must be escalated to leadership; authorized spot market buys should be considered if essential. | Supply Chain Leadership |
Clear communication
Section titled “Clear communication”When expediting, the operational requirements must be stated clearly and professionally.
Example Request:
“The current commit date of [Date] presents a challenge for our production schedule for [Project/Customer]. We are facing down-time if the material is delayed.
Could you please address the following:
- Provide the current production status of these parts.
- Please advise on the cost and feasibility of expediting this shipment via Premium Air Freight.
- If this date cannot be improved, please let us know if authorized stock is available at your other locations.”
Shortage tracking
Section titled “Shortage tracking”A focused “Shortage List” must be maintained for high-priority tracking, separate from standard backlog reports.
| Criticality | PO # | Exact MPN | Need Date | Commit Date | Current Status | Owner |
|---|---|---|---|---|---|---|
| Line Down | 45001 | STM32… | 10/24 | 11/02 | Escalated to Supplier Management | J. Doe |
| At Risk | 45009 | R-10k-0402 | 10/25 | 10/26 | Air Waybill (AWB) Tracking Pending | S. Smith |
| Buffer Low | 45112 | Conn-04 | 10/30 | Pending | Following up on Acknowledgment | J. Doe |
Recap: Supplier Commit Control & Expediting
Section titled “Recap: Supplier Commit Control & Expediting”| Parameter | Requirement | Action / Criterion | Escalation Level |
|---|---|---|---|
| ACK Confirmation | ERP Promise Date must match Supplier ACK. | Update ERP within 48 hours of ACK receipt. Flag if Commit Date > Need Date. | N/A |
| Delivery Verification | Proactively confirm shipment status. | Weeks prior: request schedule confirmation. Days prior: request Proof of Shipment (AWB). | N/A |
| Partial Shipment | Optimize production efficiency. | Accept if quantity ≥ Full Production Run. Reject if quantity < Minimum Run Size (unless line-down). | Commodity Manager |
| Component Substitution | Ensure functional and physical equivalence. | Engineering must validate package, pinout, and electrical parameters (Voltage, Tolerance, Temp Range). Revise PO to new MPN. | N/A |
| Expediting Decision | Match response to business impact. | Minor Slip: Monitor. Moderate Slip: Request Air Freight. Line Stop (Soft): Evaluate cost vs. delay. Line Stop (Hard): Escalate; consider spot market buy. | Buyer to Supply Chain Leadership |