Automatic Baseline Creation for Windchill Part Structures on Release:
Best Practice when using Windchill Parts is to Create a Baseline on Release of a Product Structure; This is a manual step.
Baseline of Released Structure captures how the BOM Structure looked at Release.
This is a Best Practice since Windchill Parts do not have an :AsStored similar to EPMDocuments.
The reason is to Capture what a BOM Structure (Ex 8,000 Componennt Assembly) appears when Released at Rev A (say in 2012); This is Useful in 2014 when for Form/Fit/Function Exceptions where 100's of COmponents could be at higher Revisions. Used by Engineering/Technical Support/etc... to note differences from Initial Approved Released and Current Configuration of a BOM Structure, via Compare Report Functionality.
Also used by Companies that Create Unique BOMs for Customers such as simulators.. Where they can use baseline to manage the "As Maintained" Configuration of a Customer's BOM.
As this step is Manual, it can be built into Workflow Instructions or Activities..
Workflow in Windchill that will Automatic Build a Baseline using Default Collection when a Part/Part Type reaches a certain State.
(Similar to ERP Connector KickOff OR can be built into the OOTB Change Notice Process as a Condition Java Expression) [A preference determines if it is used of not]
This will be useful to new customers who do not realize they need Baselines until 2 years of using Windchill; Or customers who do not have resources to teach/check users to create Baselines. Covers the Gap of not having an equavalent AsStored Baseline and not wanting the Overhead of having a Baseline getting created everytime a Part was Checked In.