PDM and PLM concept
In short
A PLM concept is a written specification of how product data is managed: object types, relationships between items, documents and CAD models, release states, roles and rights, numbering and the change process. We draft it with your design, production and IT leads, before or alongside choosing SolidWorks PDM, Autodesk Vault or 3DEXPERIENCE.
Updated 27 Oct 2026
Many PDM problems trace back to an unclear data model: drawings without an item, part numbers assigned differently in each department, release states that nobody enforces. The concept settles these rules in writing before anyone configures a system.
- Start with
- Intro callfree, 45 minutes
- Billing
- Day rates€790 engineer day · €990 lead day
- Systems
- SolidWorks PDM, Autodesk Vault, 3DEXPERIENCE/ENOVIA
How it works
- 01
Record the current state
We talk to design, work preparation, purchasing and IT and review sample assemblies and drawings, for example from Solid Edge or SolidWorks, and the numbering schemes in use today.
- 02
Define the data model
We define object types, how items, documents and CAD models relate, which attributes are mandatory and how part numbers and revisions are assigned.
- 03
Lifecycle, roles and change
We define release states and their transitions, who may check out, release or revise in each state, and how an engineering change runs from request to released revision.
- 04
Roadmap and system choice
We order the steps into a roadmap and check how SolidWorks PDM, Autodesk Vault or 3DEXPERIENCE/ENOVIA can map the concept, including the edition each requirement needs. The decision stays with you.
What you get
Data model
Object types, relationships and mandatory attributes, documented with examples from your own assemblies.
Lifecycle and rights
Release states, transitions and a role matrix that states who may do what in each state.
Numbering and change process
Rules for part numbers and revisions, plus the change process as a flow from request to release.
Roadmap
Ordered steps with dependencies, including data migration and the hand-over of items and BOMs to ERP, and a comparison of candidate systems against your requirements.
Limits
The concept describes what the system must do. Configuration and rollout are separate steps. Rules only hold in daily work when design, production and IT agree on them, so the workshops need time from these departments. A system recommendation is a comparison against your requirements; the purchase decision and licence negotiation stay with you.
Systems
- SolidWorks PDM
- Autodesk Vault
- 3DEXPERIENCE
- ENOVIA
Frequently asked questions
What should a PLM concept for a mechanical engineering company contain?
A PLM concept contains the data model, the lifecycle and the change process. In detail, these are object types and how items, documents and CAD models relate, mandatory attributes and who owns them, part number and revision rules, release states and transitions, a role and rights matrix, the engineering change process and a roadmap. The migration of existing data and the hand-over to ERP usually appear in the roadmap as separate stages.
Should a PLM concept be written before choosing between SolidWorks PDM, Autodesk Vault and 3DEXPERIENCE?
Yes. The concept states requirements in system-neutral terms, so SolidWorks PDM, Vault and 3DEXPERIENCE can be compared against the same list in demos and test installations. It also shows which edition a requirement needs, for example several workflows or API access, which call for SolidWorks PDM Professional instead of PDM Standard. Without a concept, demos show features, and the default settings of the first system quietly become the data model. The concept stays valid if the system changes later.
Should part numbers in a PLM system be meaningful or sequential?
Sequential, non-meaningful part numbers are the usual recommendation for PLM. Meaning such as product group or material belongs in attributes and classification, where it can change without renumbering the part. Meaningful numbers stop fitting once a part is reused in another product group or its material changes. Existing meaningful numbers can be kept as a searchable attribute after the switch.
What drives the effort of a PLM concept in mechanical engineering?
The effort depends on the number of sites, CAD systems and product variants, the departments involved, and whether data migration and the hand-over to ERP are in scope. A single site with one CAD system needs far less than a group with several CAD systems and an existing ERP interface. Most of the time goes into agreeing rules between design, production and IT. Writing the document is the smaller part.
Talk to us about your task.
In the free 45-minute intro call we show a live demo on comparable geometry. Someone from our team replies personally within one working day.