We started using Packages in the past few months - very simple to start. Have created just over 400 so far. Using for sort of a non-standard need - to manage the data going to a vendor and other preparation the first time any component is purchased.
[cid:image002.png@01CF8C93.25F973E0]
A few lessons learned:
- Still don't quite understand the difference between these two OTB types. For now we made the 2nd one not substantiable.
[cid:image003.png@01CF8C93.25F973E0]
[cid:image004.png@01CF8C93.25F973E0]
- These types are listed like this in Policy Admin (confusing)
[cid:image001.png@01CF8C94.41DDB110]
- Package Routing works just like ProjectLink Document Routing. Need a lifecycle that is assigned on creation of a Package and likely a different one (or more than one) for Routing. The OTB Lifecycle for Package (like most Windchill objects) is the "Basic" Lifecycle. The states are: In Work, Released, Canceled. These don't seem like states that make sense for Packages; likely want to change. But - Realize that if you route the Package, then the states of the Lifecycle used to Route are put in their place, so it doesn't matter much. If you accomplish Package state changes only via routing, then the Lifecycle assigned on creation can have a single state; we did this.
- You can configure saved searched for this type; very handy. Query Builder Reports also.
[cid:image006.png@01CF8C94.87FEB9A0] [cid:image007.png@01CF8C94.87FEB9A0]
