I think that's a bit too broad a topic to cover. There is way, way too many areas that can be customized that one document can handle, and lots of subtle little details.
How about this: Go from the fundamental logical core of what you want to do, regardless of the software itself. Virtually every process, object and team can be significantly customized in nearly every aspect. So what do you want?
-Which process steps do you want a particular object to follow?
-What data fields do you want to show up when?
-Which user roles do you want to have handle the work?
And one key question, how familiar are you with Windchill's fundamental data creation framework, i.e. the relationships between the Object Initialization Rules, Lifecycle Templates, Type and Attribute Manager object layouts and the process Workflows?
And how familiar are you with the overlapping access control systems:
-Policy Administrator
-User Account Profiles
-Configure Actions for Roles within the contexts
-Ad-Hoc rules within the lifecycle templates (honestly don't use these, you can't see or edit them en masse and the Policy Administrator can do all of it anyways)
-Server side controls
Maybe pop out a few ideas as to what you want to have happen and we can give some pointers on where to start. Oh, and which version of Windchill are you the administrator of?
Daryl
