There needs to be a step by step guide on how to create a product from start to finish in the PLM 360 system using all the various workspace components. This will enable companies that do not have a PLM or have never seen one easily adopt and setup their PLM 360 environment without the need to hire a PLM specialist to configure the environment for the product.
As mentioned earlier during a telephone survey I would to see/get help configuring a basic employee management workspace for the sole reason: to be able to use the TCO for an employee to calculate TCO's for (E)CO's and more accurate project cost estimations up front.
This workspace can be:
- basic, because most smaller companies already have a program running to manage employees. So you would need a script accessing/reading a datafile from that specific program's db
- extended, if you would want to create a workspace that makes 3rd party programs managing employees obsolete. A small nudge to move more & more company assets into the cloud/PLM.
Furthermore (maybe for a later date) I believe there was an intention to create a share/marketplace for AutodeskPLM360 scripts/workflows/workspaces to share or buy best practice addons to your existing PLM config.
I would like to know how that is coming along; wouldn't want to struggle on a script when an expert in that field has already created something similar.
It would be geatly benefitial if there was a way to pass a parameter automatically to a form when creating a new item via the URL? For example the following URL is currently used to go directly to the form to create a new item;
The following is a usage case for this functionality;
I'm creating a workspace to allow sales managers to submit RFCQs (Request For Customisation Quotation) to the engineering department. When the sales manager goes to create an RFCQ he does so by clicking on a shortcut that brings him directly to the form for a new RFCQ in PLM;
The sales managers are required to fill in fields on the form such as 'Customer', 'Sales Region', 'Industry Type' etc. However some of these fields (like 'Sales Region' will always be the same for each sales manager. So I want to give them a shortcut that links them a new RFCQ where the 'Sales Region' field is already filled in to match their personal requirement. Some other fields like 'Customer' should default to the largest customer for that region.
The functionality allows us to embed 'smart' hyperlinks from within other enterprise systems that open up new forms in PLM that are pre-populated with the correct information. We already use this to great effect with SAP and some other web-based applications we use.
The API is not useful in this case as we don't necessarily want to create an item - we just want to open the web form to create a new item with pre-filled information.
The 'default values' cannot be used as they will differ depending on user
The create behaviour script cannot be used as it will not pre-populate the form and will be a difficult script to maintain
We are deriving information from a workspace.Sometimes the derived information needs to be edited. We don't want to edit the workspace it is deriving from.
For example: I have a worksapce with a list of approved builders and I have another workspace with a filtered picklist that references that list of builders and imports fields as derived. However, sometimes a builder that we want to use is not in our list and we want to add it as a temporary only and not add it to our list of approved builders.
In the approved builders list if there was an option for "other" that would trigger the fields that are derived to be editable.
Inventor Fusion mutates to Fusion360, a cloud based application, as it looks like. I've started using the beta of Fusion360. Descriptions of models created in Fusion360 appear in PLM360 - great. I'm on OSX wherever possible and do highly welcome the availability of Fusion360 for Mac.
I'd expect that PLM360 starts Fusion360 (if it's a Fusion file) when I click a link at the info of a part in the BOM of PLM360. I'm sure that there will be more cloud based apps and it should be standard, that a model or a design for which there is an entry in PLM360 can be opened directly from the PLM360 UI.
Privilege levels should be granted to memebers of the team - not everybody should be authorized to change.