Best Practices and Guidelines - Windchill Change and Configuration Management

In the context of considering a very large Enterprise Change and Configuration Management process, we are currently looking at the best practices and guidelines associated to managing change and configurations within Windchill;

We would need to be able to clearly check all capabilities and features for envisioning what can be considered as part of the Windchill landscape, associated to several heterogenous systems which can be federated, aggregated and orchestrated using specific middleware layers based on ThingWorx

In case anyone has anything to share in this area - restricted to Windchill and/or extended to any interfaced system(s) - please provide your own field experience, expertise and associated communication materials; this will help our very large program as well as anyone involved into Windchill Change and Configuration Management Processes for considering several implementation layers most essentially using OOTB layers provided by PTC Windchill (and Thingworx)