If your enterprise has customized your mission-critical ERP systems over the years, your future upgrades will likely be more troublesome and terrifying because the changes can conflict with the patches. On the other hand, if you are running out-of-the-box ERP with little customization, maybe you're not getting all the important features your business needs.
So what's a CIO to do? And how do you figure out what to do next if upgrades or replacement are looming in your future?
These are the kinds of important decisions faced regularly by enterprises of all sizes as they carefully examine the future of ERP implementations inside their businesses, says Rebecca Wettemann, an ERP analyst with Nucleus Research Inc.
"We do see more and more CIOs going the 'less customization' route" nowadays, she says. "In the last round of ERP deployments that people did, maybe 10 years ago, they did a lot of customizations. But I would say that the majority today are going 90 percent out of the box -- with very vanilla installations. It gives you a more predictable and cheaper deployment and then obviously, it makes upgrades less disruptive and less costly."
Part of the reason for this recent trend is that ERP vendors are now recognizing that if they build applications that include verticalization, they will be easier for more companies to adopt with fewer problems and far less customization, she says.
"Verticalized applications" are built with specific vertical industries in mind, so they are essentially designed to fit different kinds of businesses out of the box. To help the applications better conform to your specific company, they include role-based views and components that users can configure with check boxes and other methods so that they more closely suit your business and process needs, without requiring code writing and deep code customization. That means that verticalized applications can later be upgraded more easily minus the associated problems and sometimes major complications that come with trying to upgrade customized code.
One vendor that does this well is NetSuite, a cloud ERP company that allows lots of configurability, she says.
Even some of the big players in the ERP marketplace tend to discourage the full customization route today.
"If you talk to Oracle, they will tell you don't customize," Wettemann says. "They'll tell you to use a verticalized application and limit yourself to configuring as opposed to customizing code."
It's becoming a more common mantra in the ERP industry, according to Wettemann.
"What we're seeing more and more are companies that are saying let's go vanilla now because they can always adjust or change things later," she says. "The idea that ERP is a big bandage and that nothing can ever change after you deploy it is going away."
And in practice, this "install vanilla" approach is a good one for many clients, she says. "I think it depends to a certain extent on the application that is chosen. If the application has vertical functionality with role-based sourcing and other possible configuring, then, yes, you're better off going vanilla."
"Clients see this as a less risky move, a more predictable way to deploy ERP and a way that is more likely to minimize disruptions and costs over time, which is even more important."