One of the critical sets of decisions that needs to be made in any ERP concerns the choice of common standard MAPs – that is, models (e.g., organization models), artifacts (e.g., vendor numbering schemes and lists), and processes (e.g., order management). Two expressions, “common … and global” and “input by many,” have received attention as guidelines to help implement those common MAPs in some companies (see CIO 1996). Rather than following the historical process of each business unit choosing its own MAPs, as is often done in legacy systems, an ERP-structured company will use the same MAPs for each business unit. However, the choice, implementation, and use of common MAPs is not easy. Within a given firm there are likely to be conflicts over those MAPs. As a result, this chapter addresses the following questions.

• Why are MAPs important?

• Where do common MAPs come from?

• Why do firms need common MAPs for ERP systems?

• Why didn't firms have common MAPs prior to ERP systems?

• Why is it difficult to choose common standards?

• What are some choice motivations?

• In order to develop “common … and global” processes, what methods have been used to choose common ERP models, artifacts, and processes so that there is “input by many”?

Why Are MAPs Important?

The quality of the MAPs will have a huge impact on the overall success of the ERP implementation.