Editing Enterprise application integration (section)

=== Implementation pitfalls ===
In 2003 it was reported that 70% of all EAI projects fail. Most of these failures are not due to the software itself or technical difficulties, but due to management issues. Integration Consortium European Chairman Steve Craggs has outlined the seven main pitfalls undertaken by companies using EAI systems and explains solutions to these problems.<ref>{{cite web|title=Dancing Around EAI 'Bear Traps'|date=2003-12-15|first=Gian|last=Trotta|url=http://www.ebizq.net/topics/int_sbp/features/3463.html|access-date=2006-06-27}}</ref>

#Constant change: The very nature of EAI is dynamic and requires dynamic project managers to manage their implementation.
#Shortage of [[middleware analyst|EAI expert]]s: EAI requires knowledge of many issues and technical aspects.
#Competing standards: Within the EAI field, the paradox is that EAI standards themselves are not universal.
#EAI is a tool paradigm: EAI is not a tool, but rather a system and should be implemented as such.
#Building interfaces is an art: Engineering the solution is not sufficient. Solutions need to be negotiated with user departments to reach a common consensus on the final outcome. A lack of consensus on interface designs leads to excessive effort to map between various systems' data requirements.
#Loss of detail: Information that seemed unimportant at an earlier stage may become crucial later.
#Accountability: Since so many departments have many conflicting requirements, there should be clear accountability for the system's final structure.

Other potential problems may arise in these areas:{{citation needed|date=February 2020}}
*Lack of centralized co-ordination of EAI work.<ref>{{cite web|title=Avoiding Pitfalls of Integration Competency Centers|date=2013-10-25|first=Antti|last=Toivanen|url=http://integrationwarstories.com/2013/10/25/avoiding-pitfalls-of-integration-competency-centers/|access-date=2013-10-26|archive-url=https://web.archive.org/web/20170730052826/https://integrationwarstories.com/2013/10/25/avoiding-pitfalls-of-integration-competency-centers/|archive-date=2017-07-30|url-status=dead}}</ref>
*Emerging Requirements: EAI implementations should be extensible and modular to allow for future changes.
*Protectionism: The applications whose data is being integrated often belong to different departments that have technical, cultural, and political reasons for not wanting to share their data with other departments