1 Data and Information Architecture: Not Just for Enterprise Architects! Gartner Enterprise Architecture Conference June 2007, Nashville, TN Gaylord Opryland Resort & Convention Center Brand L. Niemann, Senior Enterprise Architect, U.S. EPA, and Co-Chair, CIO Council's Semantic Interoperability Community of Practice (SICoP) and SOA CoP June 14, 2007

2 1. Introduction In my 25+ year government career I have been asked by senior government leadership to: –(1) Chair the CIO Council’s Web Services Working Group. –(2) Served on the Solution Architects Working Group and the Data Reference Model (DRM) 1.0 Team. –(3) Co-Chair the CIO Council’s Semantic Interoperability Community of Practice (SICoP). –(4) Lead the DRM 2.0 Implementation Through Testing and Iteration Team. –(5) Co-Chair the SOA CoP. –(6) Serve as the Secretariat of the CIO Council’s Best Practices Committee.

3 2. The Evolution of EA in the Federal Government SOA Service Systems Web Services Shared Services The “Medici Effect” Stakeholders Input and Outreach Communities of Practice Management of Change (1): see slide 2 (2) (3-5)(6)

4 Getting The “Medici Effect” “The Medicis were a banking family in Florence who funded creators from a wide range of disciplines. Thanks to this family and a few others like it, sculptors, scientists, poets, philosophers, financiers, painters, and architects converged on the city of Florence. There they found each other, learned from one another, and broke down barriers and cultures. Together they forged a new world based on new ideas – what became known as the Renaissance.” –Frans Johansson, The Medici Effect, Harvard Business School Press, 2006, pages 2-3.

5 Getting The “Medici Effect” The Medici Effect: –“When you step into an intersection of fields, disciplines, or cultures, you can combine existing concepts into a large number of extraordinary ideas.” –“We have met teams and individuals who have searched for, and found, intersections between disciplines, cultures, concepts, and domains. Once there, they have the opportunity to innovate as never before, creating the Medici Effect.” Frans Johansson, The Medici Effect, Harvard Business School Press, 2006, page 186.

6 3. Defining EA in the Federal Government Source: FEA Practice Guidance, “Value to the Mission”, December 2006, Federal Enterprise Architecture Program, Management Office, OMB, 45 pp.

7 3. Defining EA in the Federal Government Make the relationships between: –1. Enterprise Architecture A management practice for transitioning from the current state to the desired future state. –2. Segment Architecture, and Detailed results-oriented architecture (baseline and target) and transition strategy for common, shared, or enterprise services. –3. Solution Architecture An architecture for an individual IT system that is part of a segment. real using SOA in white papers, workshops/conferences, and pilots: –See Collaborative Expedition Workshop #57, Tuesday, January 23, 2007 at NSF, Opening Up Networked Improvement Activities Around Service Oriented Architecture in –3 rd SOA for E-Government Conference, May 1-2, –Note: I ended up back where I began with Solution Architecture!

8 4. Six Critical Areas (1) Enterprise Architecture (previous) (2) Semantic Interoperability (3) Service-Oriented Architecture (4) Data and Information Architecture (5) Service Systems, and an (6) Information Sharing Environment See for complete slides.

9 (2) Semantic Interoperability Semantics = Meaning = Relationships –Humans (and therefore our machines) only ever understand anything in so far as it is related to other things ID

10 (2) Semantic Interoperability Semantics = Meaning = Relationships –Humans (and therefore our machines) only ever understand anything in so far as it is related to other things ID VA NY MD

11 (2) Semantic Interoperability Semantics = Meaning = Relationships –Humans (and therefore our machines) only ever understand anything in so far as it is related to other things ID SUPEREGO EGO ANALYSIS

12 (2) Semantic Interoperability Semantics = Meaning = Relationships –Humans (and therefore our machines) only ever understand anything in so far as it is related to other things ID LICENSE CARD BADGE

13 (3) Service-Oriented Architecture PeopleBusiness Information Technology Information SOA Architecture & Infrastructure SOA CoP Knowledgebase SOA CoP Demo Phases 1-4SOA Tutorials Goal 1* Goal 2 Goal 3 Goal 4 The “Medici Effect” Stakeholders Input and Outreach * See next slide for details. SOA CoP

14 Federal Chief Information Officer Council Strategic Plan (FY ) Goals Goal 1. A cadre of highly capable IT professionals with the mission critical competencies needed to meet agency goals. Goal 2. Information securely, rapidly, and reliably delivered to our stakeholders. Goal 3. Interoperable IT solutions, identified and used efficiently and effectively across the Federal Government. Goal 4. An integrated, accessible Federal infrastructure enabling interoperability across Federal, state, tribal, and local governments, as well as partners in the commercial and academic sectors.

15 (3) Service-Oriented Architecture Improve Data Quality with Semantic SOA: –Data Modeling and OWL: Two Ways to Structure Data, David Hay, Essential Strategies, Inc.: Objectives of a Data Model: –Capture the semantics of an organization. –Communicate these to the business without requiring technical skills. –Provide an architecture to use as the basis for database design and system design. »Now: Provides the basis for designing Service Oriented Architectures.

16 (3) Service-Oriented Architecture Improve Data Quality with Semantic SOA: –Data Modeling and OWL: Two Ways to Structure Data, David Hay, Essential Strategies, Inc. (continued): Synopsis: –Both data modeling and ontology languages represent the structure of business data (ontologies). –Data modeling represent data being collected, and filters according to the rules. –Ontology languages represent data being used, with ability to have computer make inferences. Comment from Lucian Russell (SICoP White Paper 3): –So ontology can improve data quality in legacy systems! David Hay agreed.

17 (4) Data and Information Architecture Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pp DRM 1.0 SICoP Ontologies All Three DRM 3.0 unify

18 (4) Data and Information Architecture Definitions: –Metamodel: Precise definitions of constructs and rules needed for abstraction, generalization, and semantic models. –Model: Relationships between the data and its metadata - W3C. –Metadata: Data about the data for: Discovery, Integration, and Execution. –Data: Structured e.g. Table, Semi-Structured e.g. , and Unstructured e.g. Paragraph. Source: Professor Andreas Tolk, 2005, and DRM 2.0 Implementation Through Iteration and Testing Report, October 15, DRM 2.0 Implementation Metamodel

19 (4) Data and Information Architecture ToolProgramPurpose Web SearchFederal Sitemaps Google: Federal Sitemaps Locate Most searches start with Google, Yahoo, and MSN WikisCOLAB Google: COLAB Wiki Collaborate Need to Share* Semantic WikisKnowledgebases Google: DRM 3.0 and Web 3.0 Integrate Responsibility to Provide* * Mike McConnell, Director of National Intelligence: Move the intelligence community beyond the "need to share" philosophy toward a "responsibility to provide" model (March 6, 2007).

20 (4) Data and Information Architecture SICoP and SOA CoP Special Recognitions: –Outstanding Contributions to the SICoP Special Conference 2, April 25 th (recall slide 12); and –Best Presentation at the 3rd SOA for E-Government Conference, May 1-2nd: “Semantic Technology is the first fundamental change in Information Management since the RDBMS was developed in the early 1980’s”: –Michael Lang, Revelytix, Co-Founder and Director, and Co- Chair, SICoP Vocabulary Management WG. Enterprise Data Modeling / SOA in a Semantic Wiki Knoodl.com. –Demonstration at the June 18-19, 2007, W3C Workshop on eGovernment and the Web, National Academy of Sciences.

21 The Challenge: Service Industry Growth PeopleBusinessProductsInformation enable develop enable transform design operate & maintain create utilize Industrial services Information services Business services Consumer services Non-market services Source: Dr. Spohrer, Towards a Science of Service Systems, CIOC Best Practices Committee, March 19, (5) Service Systems

22 The Challenge: CIO Council Silos PeopleBusiness Information Technology Information Architecture & Infrastructure Committee Best Practices Committee Executive Committee IT Workforce Committee Source: Pages 21-22, Federal Chief Information Officer Council Strategic Plan: FY , 28 pp. Goal 1 (recall slide 14) Goal 2 Goal 3 Goal 4 (5) Service Systems The “Medici Effect” Stakeholders Input and Outreach

23 Semantic Wikis: The Role of Techno-Social Collaboration in Building DRM 3.0 and Web 3.0 for Managing Context Across Multiple Documents and Organizations, SICOP Special Conference, February 6, 2007, Mills Davis, Project10X. (5) Service Systems

24 (6) Information Sharing Environment NameOrganizationRole Model-Driven Architecture Modeldriven.orgSOA CoP Demo Phase 2 and 3 Semantic WikiKnoodl.comVocabulary Harmonization & Data Modeling GigLiteDoDComponent Development & Testing Open Source SOA Infrastructure IONASOA CoP Demo 3 Open Community SOA CoP Infrastructure

25 (6) Information Sharing Environment Google: SOA CoP Demo 4 and Join Us!

26 5. Synopsis Enterprise Architecture now is really about getting to a common language (Semantic Interoperability) about SOA (Service-Oriented Architecture). SOA itself is evolving to deal with the semantics of Data and Information Architecture across the distributed enterprise. Service Systems are about people working with their information using information technology for a business purpose in an Information Sharing Environment. An Information Sharing Environment produces service innovation (the Medici Effect). –So this is not for just Enterprise Architects, but about involving everybody! Recall slides 3, 13, and 22.