 Copyright 2001 Perot Systems Europe. All rights reserved Systems Integration and EAI

 Copyright 2001 Perot Systems Europe. All rights reserved 2 Point-To-Point Databases Packaged Apps Custom Apps Mainframe Apps Web Apps Messaging Apps Systems Integration and EAI EAI Flexible and scalable architecture Cross-application process control Easier & cheaper to maintain “Spaghetti” Rigid & static Poor scalability Costly, particularly to change No Integration Databases Packaged Apps Custom Apps Mainframe Apps Web Apps Islands of technology “Integration” by paper, fax, etc No process control Messaging Apps

 Copyright 2001 Perot Systems Europe. All rights reserved 3 EAI - Potential Benefits  E-Business – provides a standard integration infrastructure - easier for ESP’s to be integrated – open new channels to the marketplace via B2B integration platform – superior alternative to Electronic Data Interchange (EDI), permitting managed, real-time inter- enterprise system integration instead of simple batch system interfaces  Process Redesign – facilitates creation of cross-functional workflows, interacting with multiple systems  Mergers & Acquisitions – permits business-level integration without immediate conversions Source: Gartner Group Average % realised savings of EAI EAI??

 Copyright 2001 Perot Systems Europe. All rights reserved 4 EAI Approaches – “thick” or “thin” App1App2App3App4 App6 App8 App7App5 App1App2App3App4 App6 App8 App7App5  Integration layer handles the business rules – data manipulation – access to applications  Applications only need to be visible  Can develop new applications  Applications do the bulk of the work – formatting/manipulating data – presentation to integration layer  Integration layer manages flow of data – messaging – eg: file transfer

 Copyright 2001 Perot Systems Europe. All rights reserved 5 Business Environment Issues Unclear business models Processes not adopted Services and service levels not clearly defined Rate of change Unpredictable future  Greater use of 3 rd party Services – more flexibility in use of ESP’s – E-commerce  Legal / Regulatory – performance measures – reporting – operating licences  Organisational changes – mergers/acquisitions – internal business flexibility  Process Driven – across organisational boundaries – “decoupled” approach – requires service definition  Increase revenues – new channels – improved customer service (CRM) – time to market ESP External Service Provider External Service Provider Your business ESP Customer Legal / Regulatory Legal / Regulatory Supplier  Reduce costs – improved asset management – supply chain integration

 Copyright 2001 Perot Systems Europe. All rights reserved 6 Technical Architecture Issues Issues The real picture is never this simple! Lack of overall architecture Unresolved issues, eg: duplicate functionality duplicate data Business ownership unclear  Integration by a variety of methods – “thick” and “thin” – messaging – API – ORB’s – TPM – at the Powerpoint level, & beyond…..  Future systems architecture – buy not build and packages – large integrated applications – legacy migration – address Total Cost of Ownership (TCO) App7App9App8 App5 Integrated App App6App1App2App3App4 Legal / Regulatory Other Industry ESP Customer  Includes 3 rd party systems – “e-business” – other industry bodies  Integration for a variety of requirements – data migration – data integrity – process flow (particularly ESP’s)

 Copyright 2001 Perot Systems Europe. All rights reserved 7 Other considerations  Industry Standards – EDI – PKI  Related “integration” work in progress – process modelling – technical architecture  Other integration work – project specific, eg: point to point interfaces – hidden, eg: regulatory reporting  Business Case – start small, but not to constrain future strategy  Ownership App7App9App8 App5 Integrated App App6 App1App2App3App4 Legal / Regulatory Other Industry ESP Customer

 Copyright 2001 Perot Systems Europe. All rights reserved 8 “Ten Ways to Sabotage Your Application Integration Effort” 1. Focus on integrating applications, not your business 2. Hard-wire your solution to inhibit future business changes 3. Go shopping for an out-of-the-box solution 4. Fail to exploit the flexibility of a process engine 5. Connect your applications at the lowest level possible 6. Don't bother with standards 7. Ignore market developments in your industry 8. Fail to deliver immediate business benefits 9. Keep the "suits" out of the process 10. Whatever you do, don't rock the business Source: EAI Journal /Sun Microsystems

 Copyright 2001 Perot Systems Europe. All rights reserved 9 PS Approach  Architecture driven – provides the strategic direction to help avoid tactical mistakes – sell benefits of architecture to the business – reduce TOTAL cost of ownership  Take a “slice” of architecture and develop, eg: – Cost of ownership – Process – Business change – Interface / Integration  Start small, then evolve – prove the technical architecture – prove the EAI tool(s) – reduce risk – while still delivering benefit