5 Pitfalls for Enterprise-Wide System Integrations (& How to Avoid Them!)

At the Enterprise Application Integration Industry Consortium, EAIIC European Chairman Steve Craggs said that enterprise application integrations fail approximately 70% of the time, but not for the reasons you might assume. “None of them are really technical,” Craggs said, “Almost all are management issues.”

When beginning the integration process, keep these common pitfalls in mind:

#1. Constant Change

No matter how long you plan for your enterprise system integration, there’s no way you can be prepared for everything. The only constant in these integrations is change. While constructing a game plan for your business is important, it’s just as important to save room for changes along the way. Traditional life-cycle models are changing as a result of technologies that support integrations with other systems.

#2. Where are the experts?

Integrating your enterprise systems won’t be easy. Chances are, you’ll have many questions along the way, but who will you ask? There may not be a member of your staff boasting experience with
enterprise system integrations. with enterprise system integrations. This is why finding a skilled vendor is vital to the integration process.

#3. Territorial staff

While sharing data across enterprise systems will greatly improve your business processes, you might see staff members or entire departments unwilling to share their data with others. Make sure to fully explain both the short- and long-term benefits of integration to your staff so they don’t feel forced or blindsided. Making the entire organization a part of the solution helps to bring them together and start to act and work as a common unit.

#4. Accountability

Since each department has unique and conflicting requirements, there should be clear accountability for the system’s final structure. Moving away from disparate systems operating in parallel towards a more common shared architecture really is a team effort.

#5. Missing information/data

Even if certain data seems unimportant at the beginning of the implementation process, it might be crucial at a later date. Make sure to save all information in case it’s needed later in the process.

To read more about enterprise-wide system integrations, view the complete white paper here.

AssetWorks Enterprise Asset Management (EAM) system integrates seamlessly with AssetWorks comprehensive fleet management, fuel management and GPS systems to provide organizations with an end-to-end solution. To learn more about EAM, click here. 


Share This Story, Choose Your Platform!