Since 2022FD02, we have the capability to overload the operation type with an implement link role.
Introduction
By default, assigning a part to a Loading or General Operation is considered as an ADD operation, meaning having the build-up showing it as mounted and triggering the supply in MES.
The role on Implement Link will allow us to add an additional semantic information in order to cover more scenarios.
It will NOT replace the operation types like Loading Operation or Unloading Operation. It is just an overload of information on top of it so we can cover more complex scenarios.
Example use cases
Here are non-exhaustive examples to understand the concept:
- I clean the part (Handle) without adding it in the assembly yet
- I take the part from the storage (Checkout) without adding it in the assembly yet
- I remove a part (Remove), clean it (Handle) and then add it again (Add).
Here is a concrete example from a customer:
First workplan to add the parts to the assembly, last workplan (in case of Manufacturing Installation), manipulate the same parts to plug them without triggering the supply
Data model used for this example:
Role Summary:
OOTB Roles | What | Default Types | Build Up behavior (current operation) | Build Up behavior (next operation) |
Add | Mount the part in the assembly | Mfg Assembly Provided Transform Fasten Manuf. Material Manuf. Part Manuf. Kit Continuous Items | CURRENT
| PREVIOUS
|
Remove | Remove the part from the assembly | Mfg Assembly Provided Transform Fasten Manuf. Material Manuf. Part Manuf. Kit Continuous Items | REMOVED | NOT VISIBLE |
Handle | Manipulate the part (either before it is added, or after) | Mfg Assembly Provided Transform Fasten Manuf. Material Manuf. Part Manuf. Kit Continuous Items Remove Material | Case BEFORE Add: CURRENT
| Case BEFORE Add: NOT VISIBLE
|
Case AFTER Add: CURRENT
| Case AFTER Add: PREVIOUS
| |||
Produce | The part is produced (Fabrication use case or last step which implement the scoped item to the workplan) | Transform Fasten Remove Material | Here: scoped assembly assigned. CURRENT | Here: scoped assembly assigned. PREVIOUS |
Checkout | The part is deducted from the inventory | Mfg Assembly Provided Fasten Manuf. Material Manuf. Part Manuf. Kit Continuous Items | CURRENT | NOT VISIBLE |
Checkin | The part is stored in the inventory | Mfg Assembly Provided Fasten Manuf. Material Manuf. Part Continuous Items | CURRENT
| NOT VISIBLE
|
Pin | I place pins on the assembly | Fasten Remove Material | CURRENT | PREVIOUS |
Unpin | I remove pins from the assembly | Fasten Remove Material | REMOVED | NOT VISIBLE |
When we see a <*> after the role (i.e.: Add*), it means it is the role by default for the assigned item type to the operation type.
How to edit the Role
On PPL
Assignment Manager
Dedicated column with a dropdown list. It includes the custom roles too.
System Assignment Assistant
Dedicated column with a contextual menu. It includes the custom roles too.
On MGA/RME
With the function "Relations" and its contextual menu.
Customization
Sub-Role creation
Depending on the customer needr, it is possible to create a sub-role of the OOTB ones (available on Cloud from 23xFD01, applicable on MGA from 23xFD03), which will inherit the semantic and behavior from the OOTB Role.
Prerequisites: VPLMAdmin role
Action possible:
- Create new role (as sub-role of OOTB role)
- Update Role (Name and parent OOTB Role)
- Delete Role
Widget:
Screen:
Open Operation Engineering menu > Authoring rules - Items & process
Click on + to create new role
The created role will be added in the list:
EKL
Function to get the role:
Function to set the role:
https://help.3ds.com/2023x/english/DSDoc/MsdUserMap/eklMSD-r-PLMProductionSystemAdvTypePackageMethods.htm?contextscope=cloud#r-SetRole
