Requires Membership to View
To gain access to this and all member only content, please provide the following information:
By submitting your registration information to SearchManufacturingERP.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here
- Your use of SearchManufacturingERP.com is governed by our Terms of Use
- We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
- If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.
The key is to make sure you create business flows around an object like an order. Then take that order and walk it through the process across all the functional fiefdoms and all the roles that touch that order. Once you do that, you can determine who should be included in the ERP upgrade team.
You will quickly find that there are more people needed than expected. However, with a process map, people in every role understand the upstream and downstream implications.
This was first published in December 2008