pros
Cons
Suited for
Single ERR Single
Instance
• Best to standardize
business processes
• Better management control
of IT t»dgets. infrastructure
aru licenses
• Difficult to accommrxiate
mandatory localization
requirements across a large
ot countries and
business units as
customizalions cannot
prowl'/ managed
• Medium-sized enterprises
managed/ governed centrally
Medium-sized enterprises
managed/ gm'erned centrally
Single ERR Multiple
Instances
• Reasonable way manage
scale and System performatxe
• Some requirements can
be met through
customizations of local
Instances
• Each instance
implementation sub track
works separatelv, thereby'
making standardization a
challenge across "HJltiple
instances of the ERP
• Sub-optimal model for
licenses nd infrastructure
• Large-sized enterprises
already heavily imested in a
particular ERP stack in HO with
few cfvisions or operations in
disparate hxations
Multiple ERPs. Multiple
Instances
• Optimal method to manage
scale and System performance
• Specific ERP packages can be
selected based on budget
infrastructure constraints to
meet local requirements
• Proper evaluation Of the ERP
package is needed to
mitigate the risk of
sewral packages across
locations or lines ot
Ensiress. which increases
the complexity Of the IT
landscape
Large-sized entermises alreaO
invested in a Ie.acy ERP in their
HO Ic&ing to grovide flexYitv
to their
(fistributed subsidiaries while
cmtroUing costs
industryweek.com