Re:Code CAD – Use code to create CAD models
by branko_d on Tuesday October 19, 2021 @03:31AM
(#28915699)
> PLM managed through git
I'm sorry but this is probably not a good idea. A typical PDM/PLM implements many things that don't exist or are not in the spirit of git, including but not limited to:
- Per-object security, lifecycle-dependent security (e.g. an object that is Work in Progress may be editable, but it becomes read-only when Released), groups and roles (per-object groups), LDAP / Active Directory integration, ITAR compliance.
- Object lifecycle (Work in Progress / Released / Obsolete etc.), driven by workflow graph that can be adjusted for the specific customer. Ability for one or more engineers to vote to accept or reject a transition from one lifecycle state to another.
- Revisioning: automatic generation of initial revision in prescribed format, automatic increment which follows the lifecycle (e.g. when transitioning from Released back to Work in Progress).
- Part numbers: automatic generation in prescribed format, alternate part numbers (e.g. when a supplier uses a different number for the same part).
- BOMs, including support for family tables.
- Custom attributes, search, "copy structure", viewable (usually PDF) generation, integration/customization API and many many other "small" details...
I'm sorry but this is probably not a good idea. A typical PDM/PLM implements many things that don't exist or are not in the spirit of git, including but not limited to:
- Per-object security, lifecycle-dependent security (e.g. an object that is Work in Progress may be editable, but it becomes read-only when Released), groups and roles (per-object groups), LDAP / Active Directory integration, ITAR compliance.
- Object lifecycle (Work in Progress / Released / Obsolete etc.), driven by workflow graph that can be adjusted for the specific customer. Ability for one or more engineers to vote to accept or reject a transition from one lifecycle state to another.
- Revisioning: automatic generation of initial revision in prescribed format, automatic increment which follows the lifecycle (e.g. when transitioning from Released back to Work in Progress).
- Part numbers: automatic generation in prescribed format, alternate part numbers (e.g. when a supplier uses a different number for the same part).
- BOMs, including support for family tables.
- Custom attributes, search, "copy structure", viewable (usually PDF) generation, integration/customization API and many many other "small" details...