Most suppliers still get their drawings the same way: a PDF attached to an email, maybe a STEP file, sometimes a zip from a portal link that expires in a week. The moment it leaves, it is a copy. When engineering releases revision C on Tuesday, the shop that got revision B on Friday keeps cutting B, and nobody finds out until incoming inspection rejects the lot, or worse, passes it.
This is the vendor tax in its plainest form. The model lives in CAD, the release in PLM, the purchase order in ERP and the inspection plan in QMS, each from a different vendor and each “integrated.” The part still travels by attachment, and the only link between the revision you released and the revision you paid for is somebody’s memory.
In N23D, the purchase order points at the released revision itself, not a file someone exported from it. The drawing in CAD, the release in PLM, the PO in ERP and the inspection plan in QMS sit on one vault in one Rust binary. When a change is approved, every open PO on the old revision is flagged before the next part is cut, and incoming inspection checks against the revision the PO actually named.
One platform. Full digital thread. If your supplier has to call you to learn which revision is current, you don’t have a thread. You have a mailing list.
Featured photo: an inspector at a New England razor plant checks completed V-blocks against the blueprint, 1942. Howard R. Hollem, U.S. Office of War Information, via Wikimedia Commons (public domain).



