Digital Thread

Digital Thread. The digital thread is not a diagram. It is the fact that CAD, CAM, CAE, MAT, PLM, ERP, MES, QMS, PMO, CRM, TIX, CCB, and BUS share identity. The body, the process, the sim, the material, the books, the floor, the assets, the change spine, and the business can name the same thing. That is the product.

You asked for one enterprise application that replaces the rest. This page is that sentence without the poetry. Not a CAD seat with thirteen integrations. one native Rust binary — N23D. 100% Rust we write. Design, make, operate, and run the company on the same record.

Scan-to-BIM mechanical room — as-built linked to design identity

Item, VariantId, Person, and AssetId are global. Invoice, work order, inventory, quote, pay result, and NCR are per LegalEntityId. Materials live in MAT; CAD selects. ERP is one company’s books. BUS consolidates and does not file 1120. Cross-entity stock is an intercompany sale. TIX holds operational life of assets; ERP holds the financial view. CCB is the full-spectrum change record — not a second vault.

Who owns what

  • BUS owns Person, org, the legal-entity graph, intercompany pairs, and group close. Every posting that needs an employer or books owner carries LegalEntityId.
  • PLM owns the item, engineering BOM, CAD vault, configuration, and product effectivity. Item number is group-global and does not fork per subsidiary.
  • ERP owns one operational ledger per entity and the commercial view of the item. Quantity lives here. ERP does not consolidate the group.
  • MES executes the work order and records genealogy inside one entity. ERP releases; MES runs.
  • QMS owns CAPA, NCR, and signed quality records on the owning entity.
  • TIX owns AssetId operational life: IT, OT (including softPLC/SCADA), networking, and maintenance. ERP has nothing at scan rate.
  • CCB owns the cross-domain change decision and audit. It does not copy product or asset masters.
  • CRM owns the customer and the quote as the selling entity. A won quote writes an ERP sales order.
  • PMO owns the project and WBS. Charge code is an entity.
  • CAD, CAM, CAE, MAT masters are global. Lots and machines belong to an entity; machines are also AssetIds in TIX. CAD selects VariantId. Missing density means mass unknown.
  • Manufacturing BOM and routing: PLM authors, ERP plans, MES executes. Same id, plus entity.
  • Intercompany document pair is BUS, with elimination keys. Same-entity warehouse move is a transfer. Cross-entity move is an intercompany sale or explicit consignment. No third kind.
CAD model above CNC part — design-to-part on one thread

How the chain actually runs

Lead to cash, design to as-built, hire to badge, ticket to asset, change to effectivity — none of it is an integration project. It is typed identity on one thread.

  • A quote in CRM configures released PLM options, prices from the selling entity’s list, and margin from ERP cost. Accept writes one sales order.
  • An engineering change authorized through CCB carries PLM effectivity. ERP and MES consume that object. Old work orders stay on the old revision until effectivity says otherwise.
  • A work order released by ERP runs in MES against a frozen process-plan snapshot and a verified CAM packet on a TIX AssetId cell. Out of spec holds the unit and opens a QMS NCR. ERP cannot ship that lot.
  • A badge at the cell resolves through BUS to a Person employed by that entity. Time hits that entity’s books.
  • An IT or facility change goes through CCB, updates TIX AssetId state, and posts cost to ERP when money moves — without a second truth in email.
  • Stock from Nevada to Germany is an intercompany sale. Group close in BUS eliminates the pair.
  • Simulation evaluates a pinned MAT snapshot. A passed study is evidence, not a release. Release stays a PLM state.
Terrestrial laser scan of a bridge — scan-to-model unique to the thread

How N23D puts this in one place

Most stacks fail the day after save, when the model, the ticket, or the invoice becomes someone else’s import. N23D removes that day. This module reads the same record as the others.

  • one native Rust binary: N23D. 100% Rust we write. No vendor kernel, ledger, PLC runtime, HRIS, or ITSM as the source of truth. File readers and protocol bridges are interchange.
  • One identity plane: Item, VariantId, Person, and AssetId are global. Invoice, work order, inventory, quote, pay result, and NCR sit on a LegalEntityId.
  • One digital thread: modules read the same record. There is no daily STEP shuffle as the workflow. Check-in is PLM save. CAM does not fork the body.
  • Command::Core is the identity and policy plane. CCB is the full-spectrum change spine (not a second vault). TIX holds operational life of assets; ERP sees only the financial view.
  • Materials only from MAT. CAD selects VariantId. Missing density means mass is unknown — we do not invent a number so a BOM or plot closes.
  • ERP is one company’s books. BUS holds HR, org, legal entities, and group consolidation. HoldCo is not a plant. No fake Form 1120. No fake Lohnsteuer.
  • Check-in is PLM. CAM does not fork the body. No daily STEP shuffle.
  • No SIL claim in v1. No fake Lohnsteuer. No vendor as runtime source.

What we will not fake

This is the product promise, not a claim that every solver and every pack already ships in the binary today. Industry-class names below are capability equals. They are not products we ship.

  • Peers do not share a mega-database. They share identity.
  • HoldCo is not a plant code and not a corporate site that owns all inventory.
  • Part numbers do not fork per subsidiary. AssetId does not fork per ticket tool.
  • There is no silent third kind of stock movement besides transfer and intercompany sale or consignment.
  • We do not present a vendor kernel, vendor PLM, vendor ERP, vendor ITSM, or vendor PLC runtime as the source of truth.
  • This is the product promise, pre-sale — not a claim that every solver is already in the binary today.

If you still have thirteen vendors after you buy this, we failed. One binary. One auditable thread.

Natively connected, not glued together

N23D runs one data model across design, make, operate, and the business. Nothing is exported as the daily path. Nothing is re-keyed. Nothing is lost in translation between vendors.

  • One data model. A part, an order, a nonconformance, a ticket, and a change point at the same objects. No mapping tables, no nightly sync, no drift.
  • No export/import loss. Geometry, tolerances, revisions, asset state, and history stay intact because they never leave the system as the daily path.
  • Auditability by default. Every change is versioned and attributable, so traceability is a query, not a project.
  • Speed. 100% Rust: native performance, small footprint, no runtime surprises.
  • Sovereignty. Your data, your infrastructure, your rules. No lock-in.