When to Consider a Single-Instance Erp Strategy
Research
Publication Date: 28 September 2005 ID Number: G00130366
When to Consider a Single-Instance ERP Strategy
Nigel Rayner, Erik Dorr
Many consider deploying a single instance of an enterprise resource planning application to save on operational costs, reduce IT complexity and align their application strategy with the business strategy. Undertake such a project only if it matches most of Gartner's single-instance success factors.
© 2005 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.
WHAT YOU NEED TO KNOW
Adopting a single-instance, single-vendor enterprise resource planning strategy can deliver benefits, but it does not make sense for every organization. It should only be undertaken if you have a good business case for the project and it matches most or all of Gartner's single-instance success factors. If the challenges balance or outweigh the success factors, then you should address organizational issues before proceeding. If this is not feasible, then consider limitedinstance consolidation or a tiered business application strategy.
ANALYSIS
Most large multinational organizations have a heterogeneous application portfolio that has built up over time. The portfolio often is made more complex by tactical purchasing and merger and acquisition
Publication Date: 28 September 2005 ID Number: G00130366
When to Consider a Single-Instance ERP Strategy
Nigel Rayner, Erik Dorr
Many consider deploying a single instance of an enterprise resource planning application to save on operational costs, reduce IT complexity and align their application strategy with the business strategy. Undertake such a project only if it matches most of Gartner's single-instance success factors.
© 2005 Gartner, Inc. and/or its Affiliates. All Rights Reserved. Reproduction of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.
WHAT YOU NEED TO KNOW
Adopting a single-instance, single-vendor enterprise resource planning strategy can deliver benefits, but it does not make sense for every organization. It should only be undertaken if you have a good business case for the project and it matches most or all of Gartner's single-instance success factors. If the challenges balance or outweigh the success factors, then you should address organizational issues before proceeding. If this is not feasible, then consider limitedinstance consolidation or a tiered business application strategy.
ANALYSIS
Most large multinational organizations have a heterogeneous application portfolio that has built up over time. The portfolio often is made more complex by tactical purchasing and merger and acquisition