Information Interoperability Challenges:  Strategic Approach and Federated Data Management John Dodd - CSC Bruce Peat - eP...
Information Quality Enterprise Information Management FEAPMO DRM Congressional Impact on G2B Technology Enablers Public Tr...
Objective <ul><li>Breaking the Functional Stovepipes </li></ul><ul><li>Interoperability Strategy </li></ul><ul><li>Data Ma...
Interoperability Strategy <ul><li>Architecture    Implementation </li></ul><ul><ul><li>Concepts </li></ul></ul><ul><ul><l...
Architecture    Implementation Business Lines Transformation Federal Enterprise Architecture DoD Architecture Framework N...
Concepts Interoperability Strategy <ul><li>Agreements are Key for Interoperability </li></ul><ul><ul><li>Agree on ways to ...
Interoperability Challenges <ul><li>Organizational </li></ul><ul><ul><li>Perceived loss of control </li></ul></ul><ul><ul>...
Think Differently - Conventional Physical Data Link Network  Transport Session Presentation Application Open Systems Inter...
Think Differently – Paradigm Shift Physical Data Link Network  Transport Session Presentation Application Interconnection ...
Information Architecture for Interoperability Information Architecture Navigation Products / Services Enabling Technologie...
Strategic Methodology Information Architecture Source: BusinessCentricMethodology.com Methodology Strategic Tactical
Templates – Best Practices Business Drivers: Model / Process / Constraints Contract –  Collaboration Partner Specific Cons...
Providing Precise Communications Templates  Implementation
Use Case :  Architecture Driving Transformation
“ No Regret” Recommendations <ul><li>Business-Centric Methodology </li></ul><ul><ul><li>Provide semantic and pragmatic int...
Reference   Model <ul><li>Data and Information Reference Model (DRM)  – Will be an aggregated description of the data and ...
Federal Enterprise Architecture – A New Business Driven Data Model <ul><ul><ul><ul><ul><li>To facilitate efforts to transf...
Data Management Challenges <ul><li>Enterprise Data Management is a step child of the Enterprise Architecture </li></ul><ul...
The Key Principles <ul><li>Data is an enterprise asset </li></ul><ul><li>Data is more valuable when standardized, managed,...
Federated Data Management <ul><li>Must be a standards-based approach </li></ul><ul><li>A Web services approach is the best...
The Result: Inter-Agency Information Federation Virtual Views Physical Sources This approach is equally valid for  intra-a...
Federated Data Management - Metadata <ul><li>Federated Data Management  is an enormous challenge. </li></ul><ul><li>Unders...
What Every CIO Needs to Know About Metadata <ul><li>Quotes from a CIO recommendation paper written by the federal governme...
Federal Enterprise Architecture  (FEA) Reference Models Business Reference Model (BRM) <ul><li>Lines of Business </li></ul...
How Model Driven Integration Works
The FEA & Federated Data Management Approach
The FEA & Federated Data Management Approach
 
Design-Time Integration of Data Via Web Services Architecture
“ Rap Sheet” Use Case:  Using MOF models and XML based Web Services <ul><li>Law enforcement agencies need access to rap sh...
Single Agency Run-time Integration Via Web Service Architecture
Beyond Technology <ul><li>Policies are needed </li></ul><ul><li>Solution Frameworks- Proof of concepts </li></ul><ul><li>G...
Contact Information <ul><li>For more information about IAC, go to </li></ul><ul><li>www.iaconline.org </li></ul><ul><li>Fo...
Upcoming SlideShare
Loading in …5
×

IAC Secure eBiz Inf..

557 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
557
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IAC Secure eBiz Inf..

  1. 1. Information Interoperability Challenges: Strategic Approach and Federated Data Management John Dodd - CSC Bruce Peat - eProcess Solutions Michael Lang - Metamatrix
  2. 2. Information Quality Enterprise Information Management FEAPMO DRM Congressional Impact on G2B Technology Enablers Public Trust GAO Lessons Learned Reports Enterprise Information Management
  3. 3. Objective <ul><li>Breaking the Functional Stovepipes </li></ul><ul><li>Interoperability Strategy </li></ul><ul><li>Data Management </li></ul>
  4. 4. Interoperability Strategy <ul><li>Architecture  Implementation </li></ul><ul><ul><li>Concepts </li></ul></ul><ul><ul><li>Challenges; Think Differently </li></ul></ul><ul><ul><li>Recommendations </li></ul></ul>
  5. 5. Architecture  Implementation Business Lines Transformation Federal Enterprise Architecture DoD Architecture Framework NASCIO Adaptive Enterprise Architecture Agile Enterprise Implementation Netcentricity Architecture Interoperability Strategy Roadmap for going forward and provide traceability from vision to implementation
  6. 6. Concepts Interoperability Strategy <ul><li>Agreements are Key for Interoperability </li></ul><ul><ul><li>Agree on ways to accommodate system-to-system differences </li></ul></ul><ul><ul><li>Declarative methods for pragmatic interoperability </li></ul></ul><ul><li>Business First </li></ul><ul><ul><li>Shifting power to the users; customer and business experts </li></ul></ul><ul><ul><li>Moving the semantics from applications to the infrastructure layer </li></ul></ul><ul><li>Multi-Faceted Architecture </li></ul><ul><ul><li>Function-centric; not system or entity </li></ul></ul><ul><ul><li>Choice: Web (human), data, process, or services </li></ul></ul><ul><li>Successful Communication Relies on Three Principles: </li></ul><ul><ul><li>Common Semantics (the “meaning” of something) </li></ul></ul><ul><ul><li>Common Syntax (the structure of the message) </li></ul></ul><ul><ul><li>Common mechanism. </li></ul></ul>
  7. 7. Interoperability Challenges <ul><li>Organizational </li></ul><ul><ul><li>Perceived loss of control </li></ul></ul><ul><ul><li>Lack of incentives to cooperate – What is in it for me? </li></ul></ul><ul><ul><li>Lack of funds for cross-organization activities </li></ul></ul><ul><li>Architectural </li></ul><ul><ul><li>‘ Super Enterprise Architecture’ doesn’t lead to interoperability </li></ul></ul><ul><ul><li>Lack of a forum and governance for developing consensus </li></ul></ul><ul><ul><li>Data models don’t replace the need information architecture </li></ul></ul><ul><li>Technical </li></ul><ul><ul><li>Lack of infrastructure to support interoperability & reconciliation </li></ul></ul><ul><ul><li>Legacy systems in place with disparate definitions </li></ul></ul><ul><ul><li>Shackled: Stovepipe systems and elusive data </li></ul></ul>
  8. 8. Think Differently - Conventional Physical Data Link Network Transport Session Presentation Application Open Systems Interconnection - OSI Model Provides different services to the applications Converts the information Handles problems which are not communication issues Provides end to end communication control Routes the information in the network Provides error control between adjacent nodes Connects the entity to the transmission media Interconnection Proved to work well with understanding and mitigating differences with the information pipe
  9. 9. Think Differently – Paradigm Shift Physical Data Link Network Transport Session Presentation Application Interconnection Information Architecture Navigation Products / Services Enabling Technologies Interfaces Vocabularies Content High Low Stability Agility Model <ul><ul><li>Objective: insulate business from the high rate of change </li></ul></ul>
  10. 10. Information Architecture for Interoperability Information Architecture Navigation Products / Services Enabling Technologies Interfaces Vocabularies Content High Low Stability Agility Model Information Architecture Enables the management of critical Enterprise information artifacts Source: Lubash Pyramid
  11. 11. Strategic Methodology Information Architecture Source: BusinessCentricMethodology.com Methodology Strategic Tactical
  12. 12. Templates – Best Practices Business Drivers: Model / Process / Constraints Contract – Collaboration Partner Specific Constraints <ul><li>Business Goals </li></ul><ul><li>Frameworks & Standards </li></ul><ul><li>Legacy </li></ul><ul><li>Authoritative Sources </li></ul>Templates Methodology <ul><ul><li>Templates provide context for declaration of constraints and choices </li></ul></ul>
  13. 13. Providing Precise Communications Templates Implementation
  14. 14. Use Case : Architecture Driving Transformation
  15. 15. “ No Regret” Recommendations <ul><li>Business-Centric Methodology </li></ul><ul><ul><li>Provide semantic and pragmatic interoperability </li></ul></ul><ul><ul><li>Declarative mechanisms allow for mass customization </li></ul></ul><ul><ul><li>Provide infrastructure for visibility and discovery </li></ul></ul><ul><ul><li>Guidance centered around Communities of Interest </li></ul></ul><ul><li>Develop “Centers of Excellence” </li></ul><ul><li>Develop and Scope FirstGov </li></ul><ul><li>Identify Incentives for Collaboration </li></ul><ul><li>Fund Enterprise Interoperability Initiatives </li></ul><ul><li>Procurement must Dictate Interoperability </li></ul>
  16. 16. Reference Model <ul><li>Data and Information Reference Model (DRM) – Will be an aggregated description of the data and information that support program and business line operations, describing types of interactions and information exchanges. </li></ul>Information and Data Reference Model (DRM): Standards Based Architecture to Support Federated Data Management This paper is based on an approach and a Federated Information Model that can be populated along government Business Lines and be used across Federal, State, Local and International e-government initiatives. The approach is based on both sound information and data base theory, a serious need, and an approach that correlates with standards organizations to create an open and extendable family of information models. These models can be one element of each organization's push for information integration and increased consistency, commonality, and visibility.
  17. 17. Federal Enterprise Architecture – A New Business Driven Data Model <ul><ul><ul><ul><ul><li>To facilitate efforts to transform the Federal Government to one that is citizen-centered, results-oriented, and market-based. </li></ul></ul></ul></ul></ul>“ A collection of interrelated &quot;reference models&quot; designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps, and opportunities for collaboration within and across Federal Agencies .” Connect Information and Data Reference Model to BRM: Service Oriented Access
  18. 18. Data Management Challenges <ul><li>Enterprise Data Management is a step child of the Enterprise Architecture </li></ul><ul><ul><li>Dirty-Nasty-Complex </li></ul></ul><ul><ul><li>Many-many formats Exist </li></ul></ul><ul><ul><li>Each is “owned” by and protected from a “territorial” reason </li></ul></ul><ul><ul><li>Connected to system not to Process, Organization, Location- Context </li></ul></ul><ul><ul><li>Context-Content- Connection- Access Rights are not addressed fully in any standards </li></ul></ul><ul><ul><li>Often Data Analysis of Current “As-is” is done in a manual way- which is impossible with large organization changes </li></ul></ul><ul><ul><li>Metadata and Modeling are not understood and value is difficult to define </li></ul></ul><ul><ul><li>Emerging technology for information integration has many proprietary approaches </li></ul></ul><ul><ul><li>Crossing agency boundaries and business line architecture introduce new data management issues </li></ul></ul><ul><li>(Gather some challenges from the early DISA, EPA, Justice activities….) </li></ul><ul><li>Federated Data Management address some of the challenges- not all more complete Enterprise Data Management approach is needed. </li></ul>
  19. 19. The Key Principles <ul><li>Data is an enterprise asset </li></ul><ul><li>Data is more valuable when standardized, managed, and protected </li></ul><ul><li>Enterprise data security allows appropriate access to different user communities </li></ul><ul><li>Performance, integrity, and manageability are optimized by an enterprise organization of information </li></ul><ul><li>Achieving Enterprise Data Management is an evolutionary process </li></ul><ul><li>Enterprise Data Management must be part of the large enterprise architecture </li></ul>
  20. 20. Federated Data Management <ul><li>Must be a standards-based approach </li></ul><ul><li>A Web services approach is the best candidate for data interchange </li></ul><ul><ul><li>Steps : </li></ul></ul><ul><ul><ul><li>Define XML Schema </li></ul></ul></ul><ul><ul><ul><li>Map Schema to physical data stores </li></ul></ul></ul><ul><ul><ul><li>Define WSDL </li></ul></ul></ul><ul><ul><ul><li>Get XML document </li></ul></ul></ul><ul><li>Seems simple, straightforward </li></ul><ul><li>However, the mapping of XML schemas to disparate physical data stores can be a black hole </li></ul>
  21. 21. The Result: Inter-Agency Information Federation Virtual Views Physical Sources This approach is equally valid for intra-agency data integration
  22. 22. Federated Data Management - Metadata <ul><li>Federated Data Management is an enormous challenge. </li></ul><ul><li>Understanding the underlying metadata must take place before any integration efforts begin. </li></ul><ul><ul><li>Post-it notes </li></ul></ul><ul><ul><li>Spreadsheets </li></ul></ul><ul><ul><li>Registries – ISO 11179, UDDI, ebXML </li></ul></ul><ul><ul><li>Datatypes </li></ul></ul><ul><ul><li>Attributes </li></ul></ul><ul><ul><li>Structure </li></ul></ul><ul><ul><li>Relationships </li></ul></ul><ul><ul><li>Models </li></ul></ul>
  23. 23. What Every CIO Needs to Know About Metadata <ul><li>Quotes from a CIO recommendation paper written by the federal government CIO council's interoperability committee: </li></ul><ul><li>“ Metadata is one of the biggest critical success factors to sharing information …and storing information cost-effectively. Metadata can make your information sharing and storage efforts great successes, or great failures.” </li></ul><ul><li>“ Simply put, metadata management is making metadata do more things for more people in more ways, more economically.” </li></ul><ul><li>“ The alternative to metadata management is information chaos.” </li></ul><ul><li>http://www.cio.Gov/documents/metadata_cio_knowledge_feb_1999.html </li></ul>
  24. 24. Federal Enterprise Architecture (FEA) Reference Models Business Reference Model (BRM) <ul><li>Lines of Business </li></ul><ul><li>Agencies, Customers, Partners </li></ul>Service Component Reference Model (SRM) Technical Reference Model (TRM) Data Reference Model (DRM) Business-Driven Approach Performance Reference Model (PRM) <ul><li>Government-wide Performance Measures & Outcomes </li></ul><ul><li>Line of Business-Specific Performance Measures & Outcomes </li></ul><ul><li>Service Layers, Service Types </li></ul><ul><li>Components, Access and Delivery Channels </li></ul><ul><li>Service Component Interfaces, Interoperability </li></ul><ul><li>Technologies, Recommendations </li></ul><ul><li>Business-focused data standardization </li></ul><ul><li>Cross-Agency Information exchanges </li></ul><ul><li>&quot;The Business Reference Model is a function-driven framework </li></ul><ul><li>for describing the business operations of the Federal Government </li></ul><ul><li>independent of the agencies that perform them. </li></ul><ul><ul><li>The Data and Information Reference Model (DRM) will describe … the data and information that support program and business line operations. “ </li></ul></ul><ul><li>http://www.feapmo.gov/fea.htm </li></ul>
  25. 25. How Model Driven Integration Works
  26. 26. The FEA & Federated Data Management Approach
  27. 27. The FEA & Federated Data Management Approach
  28. 29. Design-Time Integration of Data Via Web Services Architecture
  29. 30. “ Rap Sheet” Use Case: Using MOF models and XML based Web Services <ul><li>Law enforcement agencies need access to rap sheets for suspects. </li></ul><ul><li>Federal law enforcement agencies, state police departments, and county police departments store arrest record information in disparate sources. </li></ul><ul><li>XML schema the is best candidate for a useful “exchange” format. </li></ul><ul><li>How do these agencies map the XML schema (rap sheet) to physical data sources? </li></ul><ul><li>How does the FBI access schema-compliant XML documents? </li></ul><ul><li>The document is reported as a Web Service (component) and can be retrieved by any properly authorized entity. </li></ul>
  30. 31. Single Agency Run-time Integration Via Web Service Architecture
  31. 32. Beyond Technology <ul><li>Policies are needed </li></ul><ul><li>Solution Frameworks- Proof of concepts </li></ul><ul><li>Government involvement in Standards Organizations with Government Contractor Support </li></ul><ul><li>Defining Competency Centers with government and contractor personnel that can share the knowledge and support Cross-Agency and Cross-government projects </li></ul>
  32. 33. Contact Information <ul><li>For more information about IAC, go to </li></ul><ul><li>www.iaconline.org </li></ul><ul><li>For more information about the IAC EA SIG, please </li></ul><ul><li>contact Kay Cederoth at: </li></ul><ul><li>[email_address] </li></ul><ul><li>For more information on each of the IAC EA SIG </li></ul><ul><li>White Papers, go to: </li></ul><ul><li>http://www.ichnet.org/IAC_EA.htm </li></ul>

×