After having become more familar with PLM it appears to me that the BOM handling across workspaces are lacking.
I like the idea of having multiple workspaces because it allows me to collect different information for different types of items.
But I have come to the conclusion that this is simply not viable at this point, because:
1) PLM does not support BOM import when it references items in other workspaces. (It is possible manually)
2) Even if I did add them all manually, I cannot create a BOM view that includes my custom fields from other workspaces because the BOM view can only see the Descriptor field from other workspaces.
The result of this is that I have to put everything in a common workspace have have to clutter up the item details with a lot of fields that does not apply.
Proposed improvement
1) Include cross-workspace BOM import
2) More configurale BOM view, where I can specify the FIELDNAME (could be free text) for each column. If the FIELDNAME does not exist for a specific item/WS on the BOM, just leave it blank. For example: If I am referencing 3 different workspaces in a BOM and 2 of them has a field called PART_NUMBER, I would expect the value to be inserted if available, otherwise left blank/null.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.