These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Product Lifecycle Mgmt (PLM)
- Data model and import order
The tables behind Product Lifecycle Mgmt (PLM)
Product Lifecycle Mgmt (PLM) ships with 17 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 17
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Design documents
Design documents refers to Items through Product and People through approved by. Revision, document type and File carry the submitted design identity.
Engineering changes
Engineering changes refers to Items through Product and retains from revision, to revision, effective date and Status. Use the product identity when reviewing the related design and operating context.
Production planning
Work orders refers to Items, Resources and Orders. Orders connects Parties through Customer; order lines connects Order and Item.
Materials and purchasing
Inventory balances and material issues identify Item and lot number, with work order on the issue. Purchase orders refers to Parties through Supplier; purchase lines connects purchase order and Item. Exchange rates stores read-only effective rate data.
Production execution
Production logs refers to work orders and People through Operator. People.User resolves the authenticated user. Users.User is itself a reference and needs the platform's identity resolution.
Batch acceptance
Batches refers to work orders and retains lot number, produced at, expiry date and Disposition. Inventory balances holds the finished-goods projection after accepted release.
Every table, by feature
- Design documents4
- Engineering changes4
- Production planning6
- Materials and purchasing8
- Production execution7
- Batch acceptance6
- Design documents
Controlled design documents and approvals.
Linked to Items, People - Items
Materials, components and finished goods.
- People
People records for Product Lifecycle Mgmt (PLM).
Linked to Users - Users
Users
Linked to Users
- Engineering changes
Engineering change requests and lifecycle.
Linked to Items - Design documents
Controlled design documents and approvals.
Linked to Items, People - Items
Materials, components and finished goods.
- Work orders
Production work orders.
Linked to Items, Resources, Orders
- Work orders
Production work orders.
Linked to Items, Resources, Orders - Orders
Customer orders.
Linked to Parties - Order lines
Order line items.
Linked to Items, Orders - Resources
Production resources and capacity.
- Items
Materials, components and finished goods.
- Parties
Customers and suppliers.
- Inventory balances
Item inventory balances by location and lot.
Linked to Items - Material issues
Material issue postings.
Linked to Items, Work orders - Purchase orders
Supplier purchase orders.
Linked to Parties - Purchase lines
Purchase order lines.
Linked to Items, Purchase orders - Items
Materials, components and finished goods.
- Parties
Customers and suppliers.
- Work orders
Production work orders.
Linked to Items, Resources, Orders - Exchange rates
Read-only effective exchange rates for this app.
- Production logs
Production interval logs.
Linked to People, Work orders - People
People records for Product Lifecycle Mgmt (PLM).
Linked to Users - Users
Users
Linked to Users - Work orders
Production work orders.
Linked to Items, Resources, Orders - Batches
Produced batches and disposition.
Linked to Work orders - Items
Materials, components and finished goods.
- Resources
Production resources and capacity.
- Batches
Produced batches and disposition.
Linked to Work orders - Work orders
Production work orders.
Linked to Items, Resources, Orders - Production logs
Production interval logs.
Linked to People, Work orders - Inventory balances
Item inventory balances by location and lot.
Linked to Items - Items
Materials, components and finished goods.
- Design documents
Controlled design documents and approvals.
Linked to Items, People
Keys and references
The model connects 17 tables through 20 declared relationships. Preserve source record identities and resolve references by those identities. Similar display names, item code or lot number labels must not silently identify a different record. Exchange rates uses ID; most operational tables use Id. Resolve Users through the platform account identity.
Design documents duplicate scope is Product + Revision + document type, enforced by the capture workflow. Retain the reviewed design basis and accepted-quantity evidence when explaining engineering and inventory handoffs. Item units and date handling require agreed import conventions.
Migration order
- Establish Users identities and resolve Users.User with the platform; then load People with valid User references. Use a validated second pass for references that cannot be resolved during initial identity creation.
- Load Items, Parties and Resources. Read exchange rates through its supported read-only source rather than treating it as an operational write target.
- Load design documents and engineering changes with source attribution and revision context. Historical review or implementation needs its original evidence; imports must not fabricate decisions.
- Load Orders and order lines, then purchase orders and purchase lines. Load work orders only after Product, Resource and Order references resolve.
- Reconcile inventory balances by Item, Location and lot number. Import material issues, production logs and Batches with their linked work orders and original evidence. Agree replay handling before importing posted effects so historical material and finished-goods movements are not applied again.
- Compare opening on-hand and reserved balances, operating state and batch disposition with the source. Configure access and views, then rehearse refused and repeated actions before cutover.
Set up Product Lifecycle Mgmt (PLM) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.