Change one bolt and ask a simple question: what else uses it? In most manufacturers the answer takes a meeting. Engineering runs a where-used report in PLM, purchasing checks open orders in ERP, the floor checks which work orders and kits are already staged in MES, and quality checks which inspection plans call it out. Four reports from four systems, stitched together by whoever owns the change.
That meeting is not diligence. It is the cost of systems that each hold their own copy of the part. A where-used report is only as good as the system it runs in, and each system only knows about the assemblies, orders and plans that were synced into it. The assembly that was released last week but has not reached ERP yet, the spare-parts kit someone built from an exported BOM, the inspection plan keyed to an old part number: those are exactly the places a change goes wrong, and they are exactly the places no single report can see.
N23D answers the question once. CAD, PLM, ERP, MES and QMS share one vault in one Rust binary, so the part has one identity and every assembly, purchase order, work order and inspection plan points at that same record. Open a change on the bolt and the impact list is already there: every released assembly, every open order, every staged kit, every characteristic that measures it. Approve the change and they all move to the new revision together.
One platform. Full digital thread. If your answer to “where is this part used?” depends on how many reports you remembered to run, your change process is a guess with a signature on it.
Featured photo: Screws, nuts and washers. Dietmar Rabich, CC BY-SA 4.0, via Wikimedia Commons.
