Customers using baselines or part configurations to capture prototypes / validation configurations request to be able to link documents to the configuration object (as validation reports etc.).
@Pekholm I don't understand the link to documents for Baselines - a document can be part of a baseline today. Are you thinking about a different kind of link?
For Product Configurations there is no plans - they are a place holder to help build Product Instances and there are no plans to support beyond that. They should not be recommended for other purposes as they are not supported in most contexts.
The requirement is to be able to link documentation about a specific configuration as validation protocols or describing documents about the configuration. The documents are already stored in Windchill, but are not a part of the structure. Configurable links would be one solution, but they are not supporting Managed Baselines today (?)
Baseline and part configuration represent a static view of the data. I'm aware that you recommend baselines infront of product configurations for this use case, but a common requirement is that customers like to store a snapshot of the structure with a identity. Might be something coming?
@Pekholm a baseline is made for this purpose - it is not meant to only hold Parts for the BOM to identify the configuration. A baseline is meant to hold information for an important event in time - as such it can hold not only the Parts, but Documents, CAD, Changes, MPM information and more. It is commonly used for this purpose. You can have one to many baselines to describe different configurations that can contain a variety of information about this configuration.
Another way to solve this would be to use a Product Instance which does support Instance specific documentation.
Thanks for your comments. Please let me know how this is Current Functionality? Using a Product Instance is not a solution. The Product Instance represents a As Build product, which occurs after order. In this case, the customer need to document the As Designed Configuration.
For an As Designed a Managed Baseline would be the recommended practice and contain all of this information.
When you said specific configuration above I took it to mean a serialized configuration which is why I mentioned Product Instance. Sorry for the confusion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
