PLM Capability Map
Status: Foundation draft · Owner: Unassigned · Last reviewed: Not yet reviewed
This map separates capabilities by the decisions and records they own. It is a research model: confirm ownership against current workflows before treating it as a product requirement.
Capability groups
| Group | Core capabilities | Primary records |
|---|---|---|
| Product definition | Collection, style, variants, specifications | Style, colorway, size, SKU, tech pack |
| Materials | Component catalog, supplier options, approvals | Fabric, trim, label, packaging |
| BOM and cost | Variant-aware BOM, quantity, revision, costing | BOM, cost sheet, price basis |
| Development | Samples, fit, comments, tasks, gates | Sample request, measurement, approval |
| Collaboration | Supplier exchange, feedback, notifications | Shared package, comment, task |
| Governance | Roles, audit, lifecycle, release | Permission, audit event, release baseline |
| Insights | Progress, exception, cost, and data quality views | Metrics and reports |
Boundary hypothesis
PLM owns the definition and approval of product intent. ERP often owns purchase orders, inventory, and financial execution; CAD owns patterns and markers; PIM owns channel-facing product content; MES or factory systems own execution. These are starting hypotheses, not universal rules. Confirm the owner of each field and event in the integration map.
Questions to resolve
- Which capability is essential for the first release?
- Which data is authored in PLM, imported, or merely referenced?
- What must be frozen at production release?
- How are external suppliers allowed to contribute without changing approved product intent?
Expected outputs
- A prioritized capability matrix with evidence and acceptance scenarios.
- A system-of-record table for shared entities.
- A clear first-release boundary and later expansion path.