PLM system features introduced using the PLM system
| Name | Description | State of practice |
|---|---|---|
| Revision management | Managing files and objects stored in the PLM file database | Documents are stored in an MS file structure without support for revision management |
| User and access management | Enables different professions within the company to have different kinds of access to the data depending on their role | The receivers of specific data are not identified and different levels of access cannot be used |
| Part management | Allows for modeling and managing product parts and structures such as components and assemblies | Parts are only handled in the CAD software without an assembly structure. Parts are not file based in the company CAD system obstructing reuse between projects |
| Process management | Enables keeping track of approval status and process progression connected to the data | Some processes are formalized, but no ones are supported by IT tools |
| Attribute management | Allows for enriched descriptions and different views on objects and linked data | No attribute data exist on current documents except for the data encapsulated in the documents and the categorization according to the guild system. Suitable attributes can support both part structures and room descriptions |
| Link objects | Makes it possible to link related objects to each other and attach attributes to the link | Existing links are hidden in the documents and cannot be managed separately from document content making it hard to get an overview of how the engineering assets are related |
| Object orientation | Separation of different classes of engineering assets depending on content and designated use | Only MS office and CAD file formats are used which does not communicate content or use |
| Name | Description | State of practice |
|---|---|---|
| Revision management | Managing files and objects stored in the PLM file database | Documents are stored in an MS file structure without support for revision management |
| User and access management | Enables different professions within the company to have different kinds of access to the data depending on their role | The receivers of specific data are not identified and different levels of access cannot be used |
| Part management | Allows for modeling and managing product parts and structures such as components and assemblies | Parts are only handled in the CAD software without an assembly structure. Parts are not file based in the company CAD system obstructing reuse between projects |
| Process management | Enables keeping track of approval status and process progression connected to the data | Some processes are formalized, but no ones are supported by IT tools |
| Attribute management | Allows for enriched descriptions and different views on objects and linked data | No attribute data exist on current documents except for the data encapsulated in the documents and the categorization according to the guild system. Suitable attributes can support both part structures and room descriptions |
| Link objects | Makes it possible to link related objects to each other and attach attributes to the link | Existing links are hidden in the documents and cannot be managed separately from document content making it hard to get an overview of how the engineering assets are related |
| Object orientation | Separation of different classes of engineering assets depending on content and designated use | Only MS office and CAD file formats are used which does not communicate content or use |
Sharing content requires targeting cookies to be enabled. Please update your cookie preferences to use this feature.