Managing Automation - November 2007 - (Page 34)

[NOVEMBER 2007] Transformation TechWatch Integration [INTEGRATION] dreaming of ONE ERP No longer just wishing and hoping, many customers are now consolidating their ERP systems down to one instance and one database running in one place. Here’s why. B Y L AU R E N G I B B O N S PAU L alk about unintended consequences. Just as a ploy by mainframe programmers to save space ended up causing the infamous Y2K bug, so too did globalization spawn the problem of multiple instances of ERP. Offshore outsourcing, mergers and acquisitions, and far-flung operations have resulted in many different versions of ERP applications running in different locations or, worse, applications from different vendors. ERP installations seem to grow like kudzu, increasing in complexity ever y day, as users clamor to keep using the local ERP instance. The problem is, multiple-instance ERP is difficult to manage and hampers enterprise visibility. Worse, it is a huge waste of money. Why maintain many different servers for different geographies when you no longer have to? Top executives at manufacturers all over the globe are asking themselves that very question. Rationalizing their ERP systems down to one version of a single vendor’s application and database running in one location appears to be the holy grail for larger companies, which often find themselves running a tangled mix of systems. Enterprise software vendors are only too happy to help with consolidation, which involves porting legacy applications to the new platform, training users on the new system, and helping with change management issues, which can be immense. “Multiple databases, multiple vendors, multiple instances — it happens all the time,” says Sharad Vajpayee, vice president at 3i InfoTech, an enterprise software vendor. Vajpayee notes this is a pressing matter for large companies, though mid-size manufacturers are interested in it, too. Commonsense guideline: The more instances, locations, and versions you’re running, the harder it will be consolidate into one instance. Single-instance ERP was nothing more than a dream until recently when international telecommunications costs dropped exponentially. Now that geographically dispersed users can access an application across continents thanks to a highspeed, cost-effective Internet connection, running a single instance becomes a much more plausible goal. “Cheaper, easier, more reliable communications — that got executives thinking about whether they needed to have a separate instance,” Vajpayee says. Then, given the brutal margin squeeze — another consequence of globalization — manufacturers quickly wised up to the potentially great cost savings of consolidating ERP. ERP provider Oracle Corp., for example, itself Industries ma November 34 2007 Photo: Justin Horrocks

Table of Contents Feed for the Digital Edition of Managing Automation - November 2007

Managing Automation - November 2007 Contents Take 1 Mailbox SAP's Business ByDesign to Validate On-Demand Model for Enterprise SW Portfolio Management Specialist Losing Ground to Rivals At Incor, It's Time for Some Deep Breathing Can HART, ISA Get Together on a Wireless Spec? Mesa Tries to Help Improve Plant Metrics Notes Cover Story: The Digital Factory Special Report: Breaking Down Walls Integration: Dreaming of One ERP Industries: Locking onto Cyber-Security Transformation: Not Your Father's Time & Attendance Program Product Scan Advertiser Index Next

Managing Automation - November 2007

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.