The PLM 360 user interface is great. Its very clean and consistent between workspaces. However, some of our users complain that its not always easy to tell one workspace from another.
I think it would be a great idea to be able to add a soft colour theme to individual workspaces. Nothing too complicated. Light almost white shades would be enough. Perhaps one workspace could have a light blue interface coulour while another could be a light green. Perhaps all email notifications from individual workspaces could have the same colour shading?
Our request is for the dashboard charts to be able to be set to be visible by default at log on. In our company it is crucial for users to be able to see their current KPIs, metrics etc easily. Having them visible at logon (and any time they revist their homepage), means that they see them dailywithout having to remember to look for them. We believe this will help to improve the company productivity, accuracy and timeliness in hitting weekly targets - all very important for us!
In truth, I rather assumed that having charts that were specific to the user login and being able to set them as always visible came by deault so it 's a bit disappointing to discover that functionality is not there yet! However, I'm sure Autodesk will be able to being this about in a future release!
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.
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.
If you could add the tabs to the workspace the same way you add a field, you would gain a ton of functionality. Even if you were still restricted to the same types of tabs currently available (grid, BOM, etc.), being able to add multiples of a tab and to add them only when necessary would be a great boost.
A function where a "desktop folder" can be added inorder to add/view documents from the desktop/finder directly into PLM360. The folder to be added should be connected to a certain workspace, where the user can chose which workspaces should be able to "share" information.
The folder should be a direct connection through the username and password from the user, where permissions should be added depending on what role the user has.
Similar to dropbox, but with the added finess of PLM360.
Is there a chance that the same ability to move multiple dates out at the same time that is found in the milestones tab, can be replicated in the Project Management tab? With the complex way we are using PLM360 to support project management we cannot utilize the milestones tab.
That said we really like the ability to move multiple task dates out without having to change them one by one.
I have beening setting up views in a workspace. Some of the views are similar and would require a lot of the same field columns and filters. Can you please introduce a clone feature for views so taht these views could be set up quicker