Product Lifecycle Management (PLM)

Product Lifecycle Management (PLM). PLM is the product record: item identity, vaulted design, configurations, engineering BOM, manufacturing BOM/routing authorship, revision, lifecycle state, and product effectivity. Check-in is save — not copy to a folder.

In industry this is Windchill / Teamcenter / 3DEXPERIENCE-class PLM capability. In N23D it is not a seat next to someone else’s stack. It is a peer module on one native Rust binary — N23D — 100% Rust we write.

Logistics center racks — configuration-controlled assemblies and parts

Same product. PLM is the thread of the product, not a vault sitting next to CAD. Where-used is a query. An ECO is a change object. CCB is the full-spectrum decision spine that can authorize that ECO alongside IT and facility change — PLM still holds product effectivity; CCB is not a second vault.

What PLM actually does

  • Item and part master: numbering schemes, types, lifecycle map, classification tree, where-used, parametric and text search. Types include part, assembly, document, software, process, tool, and raw.
  • Release and effectivity may be scoped to entities: released to make in the Nevada LLC, not yet sellable by the GmbH. The item id does not fork.
  • Multi-view BOM. Engineering BOM and service BOM live here. Manufacturing BOM is authored here, planned in ERP, executed in MES. Engineering BOM is derived from CAD structure and may be edited under change control. Manufacturing BOM is a transformed view with reconciliation indicators, not a fork. No product stores a second BOM. Effectivity is a first-class object on the thread, not a comment.
  • CAD and document vault: check-in, working copy, derived STEP/PDF/thumbnail, visualization from our tessellation. CAD files are vaulted objects with a parent Item and Revision. Save-to-PLM is check-in, not copy to a folder. Delete of a released file is refused. Native CAD is N23D CAD. Multi-CAD later as ingest of others’ files.
  • Configuration, options, variants, effectivity. Option family with include, exclude, and require. A 150% BOM resolves to a valid 100% for a sales config or a unit.
  • Change that is CMII-capable. An engineering change request states the problem and the impact: where-used, open work orders, open purchase orders, open nonconformances. An engineering change order implements revisions and effectivity. Deviation and waiver are time-boxed. Use-as-is on a released product is a deviation PLM must see. Closed loop: MES and ERP confirm that effectivity was consumed.
  • Classification and parts reuse. Requirements trace to projects, quality, and CAD PMI: hardware shall-statements plus verification links to simulation reports and quality tests. Not a full software ALM. Software CI lives elsewhere.
  • Approved manufacturer and vendor lists as first-class objects: manufacturer, MPN, status from Materials, quality, and ERP. Not a second lifecycle. Ties to the ERP vendor id and the quality supplier score. PLM does not issue purchase orders.
  • Manufacturing process plan as engineering intent: routing steps, work instructions, standard times, machine family from CAM. ERP uses it for costing and MRP. MES uses it as the executable plan template.
  • Technical publications and service BOM. Material on the item is a VariantId from Materials, an assignment, not a card. Mass roll-up via Materials evaluation.
  • Workflow is data plus Rust handlers, not a vendor BPMN product. 100% Rust we write. No Aras, Teamcenter, or Windchill process in-process.
Modern warehouse aisle — product record storage at industrial scale

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.
  • Item and VariantId are global. Release may be scoped per LegalEntityId. Invoice/WO/NCR stay per entity in ERP/QMS.
  • CAD vault under Item/Revision. CAM plans and CAE results check in on that identity.
  • CCB binds cross-domain authority; PLM does not become ServiceNow and does not become TIX.
Storehouse bays — vault vibe for revisions and effectivity

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.

  • We do not ship Windchill or Teamcenter as the runtime. File readers are interchange.
  • PLM is not a connector farm. If PLM is only integration, you still have thirteen vendors.
  • Save-to-folder is not check-in. Shadow PDM is failure.

If you still export to ERP after you buy this, or treat PLM as a connector, we failed. The thread is that nobody has to export.

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.