A designer moves a hole two millimeters and releases Rev C. In most shops the CAM programmer finds out when the first part fails inspection. The toolpath, the setup sheet, the inspection plan, and the open work order all still point at Rev B, and each one lives in a different vendor’s database.
N23D keeps one part identity across the whole digital thread. When Rev C is released, N23D lists everything downstream that still references Rev B: CAM toolpaths, CAE runs, MES work orders, QMS inspection plans, and open TIX tickets. Each one is flagged stale until someone reworks it or signs it off.
That impact list is part of the CCB change itself, so approving a change means seeing what it touches before the spindle turns. It all runs in one native Rust binary, local-first, with Entra sign-in when you want it and a permanent license.
One platform. Full digital thread. If your machinist still learns about a new revision from a scrapped part, the thread is broken.