Introduction
In the R2024x FD04 release, ENOVIA introduced a new functionality that allows instances of Engineering Items to be grouped/organized within the Engineering Definition.
The grouping of instances offers several benefits:
- Various departments such as Engineering, Marketing, and Sales, as well as different disciplines (e.g., mechanical, electronics, analytics, cinematics), can review engineering data in a way that aligns with their specific needs and workflows.
- It facilitates the standardization of navigation across Engineering Definitions, ensuring consistency across product lines.
This enhancement provides "multi-purpose" views of the Engineering Definition, making it easier for different teams to interact with, and analyze the data.
While the list of Engineering Items in the Engineering definition remains unchanged, it can be organized from different and various perspectives.
What
To allow users to view and organize the Engineering Definition in groups relevant to their needs, the existing "Browsing Structure Definition" app (*) can be utilized to create and release Browsing structures. Once defined, users can leverage these structures to group the Engineering Item instances, and navigate them in a way that aligns with their specific requirements.
(*) the app is already available in the role “Classification Manager (CCM)
Terms:
Browsing structure:
A name that represents a specific target for organizing Engineering item instances, such as:
Car Systems
Processing Technologies
Node:
Is used to assign Engineering Item instance to it. The Node is created under a Browsing Structure, and can have a structure of other Nodes under beneath it.
Later, you can use the Node to view all the Engineering instances which are assigned to it, for example:
All the Engineering instances that are related to the Node “Zone - Right”
How
Pre-requisite:
Browsing Structure creation:
The "Classification Manager" (CCM) role is required to define Browsing Structures using the "Browsing Structure Definition" app. For these structures to be accessible and utilized by users, they must first be promoted to the "Released" maturity state.
It is important to note that users do not need the "Classification Manager" (CCM) role to utilize the Browsing Structures within the relevant app; they can associate the Instances to the relevant Node(s), navigate and group the Engineering Definition without this role.
The usage of Browsing Structures in ENOVIA apps:
Currently, the released Browsing structures are available to be used in the following apps for Engineering Item instances organization:
Native client app:
- Product Structure Design
Dashboard apps:
- Product Explore
- Engineering Release
- Product Structure Editor
Here is the process to assign to Nodes, group by Browsing Structure and navigate on Engineering item Instances:
- Assign the Engineering Item instance to a Node, using the command “Add to Browsing Node”
Nodes are then displayed in the Browsing Structures:
2. Once the above assignment is completed, you can now start grouping the Engineering Definition and navigate in the structure, using the “Group By Browsing Structure” command:
You can run this grouping from any Engineering Item that has a structure.
Note:
Users who utilize the Browsing Structures defined by the Classification Manager (CCM), can:
- assign multiple Engineering Items Instance to the same Node
- assign the same Engineering Item Instance to multiple Nodes (in an existing Browsing Structure)
Classification manager (CCM), responsible for the creation of the Browsing Structures, can create a structure of Nodes (with the condition that the structure is In Work maturity state)
Please review the following videos that illustrate this capabilities:
- CCM Browsing Structure Definition
- CSV Group by Browsing Structure
