BOM, drawing and CAD revision alignment checklist
A focused review method for finding identity and revision conflicts before manufacturing files reach a supplier.
Why apparently matching packages still fail
Revision conflicts are rarely limited to an obviously old file. They appear when the BOM, drawing register, CAD vault and exported filenames express configuration differently.
A filename can look current while its title block is obsolete. A CAD model can be geometrically current while its metadata carries an earlier revision. Alignment therefore has to compare both identity and release state.
Map each manufactured item to its files
Create a relationship between every supplied BOM item and its drawing or model. Include drawing-only, model-only and reference items so absence is intentional rather than accidental.
Where drawing number and part number differ, record the relationship. Do not rely on filename similarity.
- BOM item number and part number
- Drawing number and sheet count
- Native CAD document and model configuration
- Neutral CAD export when required
- Current revision or version for each source
Compare content, not only filenames
Inspect title blocks, file metadata and BOM revision fields. Normalize casing, separators and known system-specific suffixes, but do not normalize away meaningful configuration markers.
Classify each difference as a naming variation, confirmed mismatch, missing value or unsupported mapping. This keeps the review evidence useful.
- Part identity matches the intended BOM row.
- Drawing revision matches the authoritative release.
- CAD version maps to the same approved change.
- Neutral exports were generated from the approved native model.
- Sheet counts and referenced drawings are complete.
Resolve exceptions before approval
A mismatch must lead to a correction or a documented acceptance. Accepted differences need an owner, reason and scope so the next reviewer does not repeat the same investigation.
Do not approve a package simply because every warning was viewed. Approval means the complete release is suitable for the stated supplier handoff.
Freeze the aligned set
Once aligned, bind the manifest, files and decisions into one approved release. Record a content hash or stable package identifier when the delivery system supports it.
Any subsequent file replacement should invalidate the earlier approval and restart the relevant checks.
Repeat the check after every engineering change
Revision alignment is not a one-time cleanup. Repeat it whenever an ECO changes a supplied part, drawing, CAD model or referenced specification.
Use the previous approved package as a comparison point. A focused delta review is faster and more reliable than reconstructing history from shared folders.