Skip to content
PDMLYNXPRODUCT DATA REFERENCEMethodology
METHOD / 01

PDM Software Evaluation Criteria

How records, evidence states, and corrections are handled.

A quiet review desk holds source folders, a metal part, a ruler, and a pencil arranged in calm morning light.
A review desk holds source notes, product records, and a visible evidence ladder.

What a record means

Each capability record describes a product family or named edition at a stated review date. A field is displayed as documented only when a primary source supports that specific claim. Where an edition changes the claim, the record says so.

What the states do not mean

Not disclosed is not a negative verdict. It means the public sources reviewed do not answer the question. Needs verification is a visible research debt, not a guess. This prevents omission from becoming an unsupported comparison claim.

Source register

STD-003NIST, A Product Information Modeling Framework for PLM
STD-004OMG, Product Data Management Enablers
STD-006NASA, Product Data and Life-Cycle Management
VEN-001Autodesk Vault overview
VEN-002SOLIDWORKS PDM overview
VEN-004PTC Windchill overview
VEN-005PTC Windchill data management documentation
VEN-006Aras PLM overview
VEN-007Aras Innovator product summary
VEN-008OpenBOM overview
VEN-009OpenBOM data management library
VEN-010Odoo PLM documentation
VEN-011SAP Product Lifecycle Management
VEN-012Oracle Fusion Cloud PLM
VEN-013ENOVIA overview
VEN-014ENOVIA Product Data Management

Corrections and review

Product records are designed for review. Send official source material to [email protected]. A material change is logged at the record level on a later review rather than silently replacing the previous assessment.