EAI Service Components in Relation to XML Registry Services, eGov, LOBs & FEA/TRM

1. EAI Service Components in Relation to XML Registry Services, eGov, LOBs & FEA/TRM

2. Agenda • What is Integration Consortium • Integration Definitions • IC’s Global Integration Framework • Components of Integration • Applying this to eGov initiatives • FEA TRM • OMB LOBs • Use of Registry • Questions?

3. TheIntegration Challenge A CEO once aptly described the current state of most corporate IT structures as modern cities connected by dirt roads.

4. Organizational Overview Founded July 2001 http://www.integrationconsortium.org

5. Mission & Purpose • The Integration Consortium is a non-profit, leading industry body responsible for influencing the direction of the integration industry. Its members champion Integration Acumen by establishing standards, guidelines, best practices, research and the articulation of strategic and measurable business benefits. • The mission of the Consortium is to: • (1) support the acceptance and implementation of Enterprise Application Integration and other integration technologies, applications and services, based on international standards, • (2) support the interoperability, advancement and convergence of technologies that enhance enterprise integration markets.

6. Integration Consortium • Launched in 2001 as the EAI Industry Consortium • Incorporated as a non-profit organization under the Alberta Societies Act on February 25, 2002 • Changed name to Integration Consortium on May 24, 2004 to reflect broader mandate • Membership categories: • Executive • Associate • Educational/Non-Profit • End-User • Professional Services • Individual • Student • Partnership • Notes: • Full voting rights • Non voting member

7. Committees • Adaptor Technology • Enterprise Information Integration • Business Process Integration • SOA • Web Services • Wireless Technology • Emerging Technologies • Methodology • Best Practices • More

8. Definitions • Enterprise Application Integration • Definition: The process of integrating multiple applications that were independently developed, may use incompatible technology, and remain independently managed. • By this definition, EAI would include: • Business Process Integration • Enterprise Information Integration

9. Guiding Principles for Enterprise Integration • Clear IT Strategy mapped to Business Strategy • Mapping of corporate process and data models • Plan ahead for EI - investment vs. cost justification • Formulate an EI architecture based on integration characteristics • Establish clear lines of ownership and accountability • Evaluate vendors on commercials, stability, references, strategy • Evaluate technologies - scalability, flexibility, customization, standards • Invest in the right skills - Solution & Integration Architects • Pilot the desired solution, but in a real environment • Ensure tools and processes in place for end-to-end service mgmt

10. Enterprise Integration Taxonomy

11. Common Layers of EAI Solutions Business Intelligence Provides real-time and historical data on performance of processes and assists in making decisions. Business Process Management Manages and tracks business transactions that might span multiple systems and last minutes to days. Messaging Ensures the reliability of data delivery across the Enterprise or between systems. Adapters Provides “open” connectivity into data sources while allowing filtering and transformations of data.

12. IC Integration Methodology

13. Global Integration Framework (GIF) • a universal lexicon of integration terminology • a vendor-neutral reference architecture • an integration methodology including prescriptive templates and standards • a central registry of GIF-compliant interfaces • a software framework (possibly open source) of integration services • an integration data model and associated tools • an education program • a certification process to validate the skills and knowledge of individuals, the conformance of products, and the maturity of organizations

14. Global Integration Framework (GIF) The Global Integration Framework brings together industry standards, integration best practices, formal modeling techniques, and other initiatives to create a prescriptive approach to systems integration. GIF is similar to • W3C’s Semantic Web Vision • Model Driven Architecture from OMG • Boundaryless Information Flow from The Open Group

15. Global Integration Framework (GIF) • Defines: • Business Architecture • Data Architecture • Application Architecture • Technology Architecture • Based on The Open Group Architecture Framework (TOGAF) • This is similar to FEA Reference Models

16. Integration Today BFDI E-Commerce 15 SAP 14 17 DRP 2 16 3 11 9 Customer Call Email CBCF BW Financials 12 Computer Telephony 6 Customer Call COPS 1 JDA 7 BW Tax System Computer Telephony 6 COPS 1 JDA 7 1 ? 13 10 4 5 8 BFDI 14 E-Commerce 1 13 10 15 SAP 4 5 8 14 BFDI 14 E-Commerce 17 DRP 15 SAP 2 14 16 3 11 17 9 DRP 2 Email 16 CBCF Financials 3 11 12 9 Email CBCF Financials Tax System 12 Tax System Customer Call BW Computer Telephony 6 COPS 1 Customer Call JDA 7 BW Computer Telephony 6 COPS 1 1 13 10 JDA 4 7 5 8 BFDI 14 E-Commerce 15 SAP 1 13 10 4 14 5 8 BFDI 17 14 DRP E-Commerce 2 15 SAP 16 14 3 11 Customer Call 9 BW 17 DRP Computer Telephony 2 Email 6 CBCF Financials 16 COPS 1 12 3 11 JDA 7 9 Email Tax System CBCF Financials 12 1 13 10 4 5 8 BFDI 14 Tax System E-Commerce 15 SAP 14

17. Integration Requirements As boundaries in organizations are demolished and stovepipes eliminated, the challenge of managing and accessing information becomes critical to organization success • Data / information available • Access mechanisms • Security • Relationships of data across disparate sources • Rules for sharing relevant information • Proof • Lineage • Verification

18. documents N-Tier Architecture Presentation Tier Presentation Logic Tiers Business Logic Tiers Data Access Logic Tiers Data Tier Adapters Templates Related Information Aggregation Web Services Transformation Message Middleware Rules Portal Interface Constraints Filters Terminology Resolution Terminology Resolution Data Tier Security Integration Forms Operational Security Formatting Objects RPC Interface Object Model Workflow Adapters

19. Integration Approach Benefits • Reuse of integration objects • Modeling business information corresponds directly to business model • End-user / SME driven changes • Multiple presentations for single piece of information • Lower cost of integration • Initial • Maintenance

20. What’s Driving Change in Federal Government? • Agency business rationalization • Citizen-centric services • ROI & ROA • Need for real-time & integrated data • Consolidation within and across agencies • Legacy system limitations • Shorter development lifecycles / reduced development costs

21. Federal Enterprise Architecture FEA reference models create a comprehensive government-wide framework to guide agency IT investment activities; and identify opportunities to collaborate on and consolidate initiatives, and integrate government activities.

22. E-Gov Initiatives • Government should be • citizen-centered • results-oriented • market-based “Effective implementation of E-Government is important in making Government more responsive and cost-effective.”

23. OMB LOB’s The five Lines of Business and their agency team leads are: • Financial Management (FM) • Department of Energy • Department of Labor • Human Resources Management (HR) • Office of Personnel Management • Grants Management (GM) • Department of Education • National Science Foundation • Federal Health Architecture (FHA) • Health and Human Services • Case Management (CM) • Department of Justice

24. IC and e-Gov Initiatives • Stove-piped, agency-centric  open, citizen-centric • Replacement too expensive • Different “duplicate” data across agencies; data access and business logic tiers resolve this • Need to model business information to produce citizen-centric services • Separate presentation reuse business logic / function

25. XML Registry Uses • Data Access Logic Tier utilizes adapters and services that will be defined as XML and should be sharable across agencies • Business Logic Tier could use XML-based information models, like RDF< OWL or XTM, and rules, like SWRL or RuleML. Reuse is imperative. • Presentation Logic Tier will utilize XSL, XForms, and other XML markups.

26. documents The Final Architecture Presentation Tier Presentation Logic Tiers Business Logic Tiers Data Access Logic Tiers Data Tier Adapters Templates Related Information Aggregation Web Services Transformation Message Middleware Rules Portal Interface Constraints Filters Terminology Resolution Terminology Resolution Data Tier Security Integration Forms Operational Security Formatting Objects RPC Interface Object Model Workflow Adapters Security Model, Encryption, Signature…Proof Registry

27. Agenda • What is Integration Consortium • Integration Definitions • IC’s Global Integration Framework • Components of Integration • Applying this to eGov initiatives • FEA TRM • OMB LOBs • Use of Registry • Questions?