Understand Undercarriage Parts Lead Time Before Ordering

A quotation says “30 days,” but that number does not yet tell a maintenance planner when usable undercarriage parts will reach the repair site. The buyer may count from the purchase-order date to arrival. The supplier may count from cleared payment and drawing approval to cargo-ready status. Both parties can repeat the same number while planning different intervals.

An undercarriage parts delivery lead time becomes usable only when it has a defined start event, a defined finish event, a time basis and a chain of dependencies. Record quotation, approval, material, production, any outside process, inspection, documentation, packing, carrier handover, delivery and receiving release as separate milestones. Then a late approval or incomplete document has a visible effect instead of disappearing inside a percentage-complete update.

This method does not predict a standard KTSU lead time or a live transport schedule. It turns one order’s promise into questions that a buyer and supplier can answer with order-specific evidence.

Ask which event starts the clock

Do not enter “30 days” in a repair plan until the quotation or order acknowledgement identifies the event that starts those days. Also record whether the count uses working days or calendar days, which holidays or shutdowns are excluded, and what the stated finish means. “Complete,” “ready,” “shipped” and “delivered” are not interchangeable finish events.

A published order lifecycle from Indu Thermoformers, for example, puts first-article approval before production and treats packing and dispatch as later stages. That is evidence of one supplier’s staged workflow, not a timing promise for an undercarriage order. Its useful planning lesson is that a duration belongs between named events.

Purchase order, payment or approval

A supplier may require more than one condition before releasing production. Possible conditions include acceptance of the purchase order, receipt of a deposit, confirmation of the drawing revision, resolution of a technical question or approval of a first article. RapidMfgPro’s CNC-order guide similarly lists purchase-order acceptance, deposit receipt and several approval events as possible clock starts. The applicable event still comes from the actual quotation and agreement.

If several conditions must all be satisfied, write the start as an “and” statement: “PO accepted + deposit received + revision B approved.” Keep the date of each condition. The latest required condition becomes the observed release date; the earliest one does not start the clock by itself.

Ask the supplier to confirm these four fields in one reply:

• Start event: the exact record that releases the quoted lead time.
• Time basis: working or calendar days and any excluded shutdowns.
• Finish event: production complete, cargo ready, carrier handover, arrival at a named point or another defined event.
• Buyer-response allowance: whether approval time is inside the quoted duration and when a delayed response causes a reforecast.

This turns an order date into a testable starting condition. If any required input is missing, the schedule is not released; its status is open.

Separate production from ready-to-ship status

Production completion answers a manufacturing question: has the agreed production route been completed for the identified quantity? Cargo-ready status answers a wider release question: are the agreed inspection records, documents, identification, packaging and handover information also complete? Shipment then records carrier possession or departure under the order’s transport arrangement. Arrival and receiving acceptance occur later.

RapidMfgPro explicitly distinguishes production completion, ready-to-ship, shipment, estimated arrival, delivery and acceptance dates. Use those distinctions as planning labels, while letting the actual sales and transport terms define what each label means for your order.

Outside processing

An undercarriage component route may include an operation performed away from the main production step. If the quoted route includes heat treatment, coating, grinding, marking or another sub-tier process, give that operation its own row. Record the quantity sent, the quantity returned, the planned and current dates, the sub-tier evidence required and whether the parts need reinspection after return.

“Machining complete” would be misleading if the agreed route still has an unconfirmed sub-tier slot. Ask whether the outside-process capacity was confirmed when the quotation was issued or remains an assumption. Also ask which earlier tasks can continue without that slot. Packaging design or draft paperwork might move in parallel, but final cargo release can remain blocked by the unfinished operation.

Do not convert an unconfirmed outside-process date into zero days. Keep it as an open dependency and request a dated update from the party that controls it.

Inspection and documentation

Inspection activity is not automatically complete because the parts exist. Define the evidence required by this order: for example, an identified final inspection report, an applicable material or process certificate, a quantity record, part and package identification, and any agreed first-article approval. The list should come from the purchase order and approved quality requirements rather than a generic checklist.

Documentation can partly overlap production. A supplier may prepare templates or assemble existing material records while the batch runs. Final values and release signatures, however, depend on the finished and inspected parts. Treat a draft as a draft. Cargo becomes ready only when the order’s agreed release conditions and final packing inputs are complete.

A cargo-ready notice should identify the order, line items, released quantity, package count, gross weight and dimensions, release date, evidence index and pickup location. Without those fields, a forwarder may be unable to turn a production-complete message into an actionable handover.

Map the dependencies that control the need date

A useful schedule is a dependency map rather than a list of durations to add. For each task, record what must finish before it can start. Then work backward from the real need event: not merely arrival at a port or warehouse, but the point at which the identified parts have reached the named location and passed the receiving checks required for the repair.

The controlling path is the linked sequence whose movement changes that need event. A short delayed approval can control the date when production waits for it. A longer freight-planning task may not control the date if it finishes in parallel before cargo is ready.

Parallel work

Parallel tasks share elapsed time. They should appear on separate rows with overlapping dates, not be added as though they ran one after another. Suppose material reservation takes Days 1–4 and drawing approval runs from Day 0 to Day 5. If production requires both, it can begin after Day 5 in this illustration. The combined prerequisite interval is not nine days.

Other planning tasks may overlap as well:

• Provisional freight planning can begin with estimated package data, then be refreshed after final packing.
• Packaging planning can begin from the approved part scope while production is running.
• Draft document preparation can run before final inspection, while the final release still waits for actual inspection results.

Record the assumption that allows each task to start early. If final package dimensions differ from the estimate, the freight plan needs a revision; early work does not guarantee that its first output remains valid.

Blocked approvals

An approval is a schedule task with an owner, requested date, response deadline and release evidence. Mark it approval hold when the responsible person has not supplied the required decision. Do not show the dependent production task as in progress simply because its planned start date has passed.

When an approval arrives late, first move the tasks that depend on it. Then ask the supplier to confirm whether capacity, material or sub-tier reservations still hold. A late customer answer does not prove that every later task moves by the same number of days, but the old finish date also should not remain untouched without a supported recovery plan.

If the supplier proceeds at risk before approval, record that choice separately. It does not transform the missing buyer decision into an approval, and it may create completed or committed work that needs its own disposition if the requirement changes.

Compare a repeat order with a changed order

A repeat part number does not by itself prove a repeat schedule. The applicable revision, quantity, material, process route, inspection package, packaging, destination and release terms may have changed. Compare those fields before applying an earlier order’s parts production lead time.

Approved baseline

For a true repeat, identify the earlier approved baseline and the evidence that remains valid. At minimum, bind the new order to the correct part and revision, quantity range, approved manufacturing and inspection route, required documents, packaging configuration and delivery point. Then ask the supplier which reservations or retained resources still support the new release.

The following milestone timeline is a hypothetical worked example. It uses elapsed-day markers so the overlap is visible; it is not a KTSU test record, quotation or carrier forecast. The customer approval was planned for Day 2 and completed on Day 5. Material reservation and freight planning continued in parallel, while production waited until both material and approval prerequisites were satisfied.

The example reaches cargo-ready status on Day 20, carrier handover on Day 21, arrival on Day 28 and usable-parts release on Day 29. Those dates come from the hypothetical rows. They do not result from adding every row duration, because several tasks overlap.

Requalification triggers

Compare the new order against the approved baseline before calling it a repeat. A drawing revision, material specification, quantity range, manufacturing route, outside processor, inspection requirement, package design, destination or requested need date may require new review. A long interval since the previous order can also make capacity or material assumptions stale even when the part definition is unchanged.

RapidMfgPro notes that a buyer-requested change after material or tooling commitment can affect completed work, fixtures, schedule and inspection, and that the original delivery commitment should not be reused automatically after a material design change. Apply that observation narrowly: identify the changed field, ask which milestones it invalidates, and obtain a revised order-specific acknowledgement. It does not establish a universal requalification rule.

When the same part number masks a changed revision or delivery point, preserve both facts. Do not overwrite the earlier baseline to make the new schedule look like a clean repeat.

Keep updates tied to observable milestones

“Eighty percent complete” is difficult to audit and may hide the only task that controls the need date. Ask for the latest completed event, its evidence, the next dependency and the effect on cargo ready, handover, arrival and usable-parts dates. A milestone should remain forecast until its defined evidence exists.

Evidence of completion

Evidence depends on the event. An accepted PO and approved drawing may support order release. A linked completion notice may support production completion. An identified inspection report and document index may support quality release. Final package data and a cargo-ready notice may support pickup planning. A carrier reference supports handover, while a signed receiving record supports arrival at the named point.

RapidMfgPro provides examples of documents that can support payment, approval, inspection, shipment and delivery milestones. Select only the records required by your order. A photograph can supplement an identified completion record but should not be treated as proof of dimensions, material or hidden condition.

Procut-CNC’s lead-time guide flags schedules that omit material or outside-process availability, customer approval, documentation or final inspection. It also asks buyers to provide the required date, usable partial quantity, finishing, inspection package and approval path. That published CNC guidance supports the dependency method; it does not verify an undercarriage supplier’s current capacity or date.

Revised dates and assumptions

A useful update carries its own comparison point. Record the update date and time zone, the last completed milestone, the open dependency, who owns the next action, the prior date, the current date and the assumption behind the change. Keep an estimated arrival labelled as an estimate, and identify the delivery point it refers to.

If a dependency remains unknown, do not fill the gap with the old date. State which downstream milestones cannot yet be forecast. If a recovery action is proposed, show what changes—such as a confirmed earlier sub-tier slot or an approved partial quantity—and which later dates were recalculated. Do not turn a request for faster service into a confirmed plan until the responsible parties acknowledge it.

Use the same record for good news. If packaging planning and documentation preparation finish in parallel, close those rows with evidence while leaving outside processing open. The timeline then shows progress without implying that the order is ready to ship.

For broader discussion of supply-network location and downtime, see KTSU’s article on nearshore supply chains and undercarriage-parts availability. For a specific enquiry, send the part number, revision, quantity, required location and milestone questions to KTSU. Keep any unconfirmed start event, approval, outside-process slot, cargo-ready date or arrival estimate visibly open until the relevant order record supports it.