Control Drawing Revisions Before Ordering Undercarriage Parts
A supplier can have your newest drawing while part of your order is still being made to an earlier revision. The missing information is often the change boundary: which purchase-order lines, quantities and production lots should use the new release?
Drawing revision control gives each group of parts an identifiable requirement and a recorded release decision. For a repeat order of roller cores, sprocket components or other drawing-controlled parts, that means linking the approved document package to the order, obtaining a specific supplier acknowledgement, and deciding separately what happens to work already started.
Find the released drawing package
Start with the record that authorizes use of the drawing. Look for the document number, revision, release status, approval reference and any stated effective date or order boundary. A recent modification date only tells you when a file changed. Autodesk’s explanation of versions and controlled revisions distinguishes development history from the information released for downstream use.
Collect the documents needed for this order into an indexed package. A component drawing might be revision C while the assembly drawing remains revision A and the packaging instruction remains revision 2. The index should identify those exact documents. Giving the package its own release ID does not require renaming every included document to the same revision.
If a model and drawing disagree, identify the conflict and obtain an authorized answer before releasing affected work. Procurement should not choose a dimension simply because it appears in the newer file. The engineering reasons for controlling individual features are covered separately in precision CNC machining tolerances for track rollers.
Bind each PO line to its approved revision
Use a release register whose rows represent a PO line and its applicable production group. A single row for the entire supplier becomes inadequate when the supplier has several orders, or when one order straddles a change.
The register below defines the information to retain. Link it to the actual files and approval records so that another buyer or inspector can recover the evidence without searching through an email conversation.
| Record | What to enter | What it resolves |
|---|---|---|
| Order identity | Supplier, PO number, line, part number and ordered quantity | Which commercial requirement is being controlled |
| Document package | Package ID and an index of drawing, model, specification and instruction revisions | Exactly which files belong together |
| Approval | Release authority, approval reference and release date | Who authorized the requirement |
| Effective scope | Applicable lot, quantity or other agreed boundary | Which physical parts the release covers |
| Supplier reply | Package and revision confirmed, respondent, date and affected work status | Whether the supplier’s understanding matches the release |
| Earlier work | Actual revision, quantity, location and disposition reference | What remains outside the new release |
| File identity | Controlled file location or export ID; a checksum where used | Which saved file was issued and acknowledged |
A checksum can help detect whether two copies contain the same bytes. It does not establish that the design was approved, that the drawing is technically correct, or that the supplier used it in production. Keep file identity and release authority as separate fields.
Ask the supplier to acknowledge the package by ID and revision, rather than replying only “received.” The response should identify whether the affected quantity is unstarted, in progress or complete. Where the change reaches manufacturing or inspection instructions, request confirmation that those instructions have been updated for the relevant work.
Lifecycle controls can support this separation. Autodesk describes review and release states in an engineering data system. The practical requirement for the buyer is a visible, authorized release state; a software check-in or an email delivery receipt alone does not supply it.
Set the effective boundary for a later revision
Consider a hypothetical order, PO EX-040, for 40 roller cores to drawing EX-RC-17 revision B. Engineering releases revision C under change record EC-EX-02. The supplier reports 12 cores complete, eight in progress and 20 not started. Those quantities account for the order, but they require different decisions.
For the 20 unstarted cores, the release record can identify revision C as the applicable requirement. Before that group proceeds, the supplier’s acknowledgement must match both the package and the quantity boundary. A reply that confirms “C for the order” leaves the other 20 cores unexplained.
Work already in progress
For the eight in-progress cores, ask which affected operations have been completed. Engineering needs that information to decide whether the work can continue, needs an approved modification, or should remain held while another disposition is developed. Do not prescribe rework from the revision letter alone.
Keep the affected work identifiable while the decision is open. If the supplier says four of the eight have passed the changed operation and four have not, split the record again. The finer grouping is useful because it changes the decision, not because every manufacturing step needs another spreadsheet row.
Stock made to the earlier revision
The 12 completed cores remain revision B parts. A buyer may need engineering to assess whether they can be accepted under a defined concession, modified under an approved route, or rejected. Preserve the actual revision and the disposition reference whichever route is chosen.
Do not change the labels or inspection-report revision to C merely to match the updated PO. That would erase the distinction the register is meant to preserve. A repeat-production sourcing guide also identifies earlier stock and work in progress as items requiring a separate decision. The particular acceptance authority and conditions must come from your own order and quality arrangements.
Close the supplier acknowledgement loop
Use three distinct outcomes when reviewing the reply:
- No specific acknowledgement: the supplier has not identified the released package and affected work. Keep the release decision open and request those details.
- A conflicting acknowledgement: the supplier cites an earlier revision, a different package or a different quantity boundary. Reconcile the difference before the affected work proceeds.
- A matching acknowledgement: the package, revision and effective scope agree. Record the reply and confirm that any earlier work still has its own disposition record.
In the example, a matching reply for the 20 unstarted cores closes that group’s document-release question. It does not close the eight in-progress or 12 completed cores, and it does not constitute acceptance of the finished parts.
At shipment, check that the lot identities and inspection records still point to the applicable requirement. At the next repeat order, make a new release check instead of assuming the last acknowledgement applies indefinitely. The completed record should let a colleague answer three questions directly: which revision applied, to which parts, and on whose authority?