1 / 52

Data and Information Architecture: Not Just for Enterprise Architects!

Data and Information Architecture: Not Just for Enterprise Architects!. Gartner Enterprise Architecture Conference 13-15 June 2007, Nashville, TN Gaylord Opryland Resort & Convention Center Brand L. Niemann, Senior Enterprise Architect, U.S. EPA,

maudra
Télécharger la présentation

Data and Information Architecture: Not Just for Enterprise Architects!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data and Information Architecture: Not Just for Enterprise Architects! Gartner Enterprise Architecture Conference 13-15 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. Abstract • Enterprise architecture in the Federal Government is evolving from compliance-driven to value-driven with SOA leading the way. SOA itself is evolving to deal with the semantics of data and information across the distributed enterprise. Service systems (networking communities of practice) are also in play to integrate people, business, information, and information technology in an information sharing environment. • This keynote addresses what these all have in common and explains the evolution of the Federal Enterprise Architecture's Data Reference Model and the Internet itself from (1) the Web, (2) the Social Web, (3) the Semantic Web, and (4) the Ubiquitous Web. A specific example of architecting and implementing an information sharing environment is provided and demonstrated.

  3. Overview • What do: • 1. Enterprise Architecture • 2. Semantic Interoperability • 3. Service-Oriented Architecture • 4. Data and Information Architecture • 5. Service Systems, and an • 6. Information Sharing Environment • Have in Common? • The answer later.

  4. 1. Enterprise Architecture • Parsing the words like we are known for doing in the Nation’s Capital (): • Enterprise Architecture • Enterprise: A Star Trek Spaceship • Architecture: Blueprints • So, Blueprints of the Spaceship Enterprise! • Google WordNet Princeton: • Enterprise: 3 • Architecture: 4 • Combinations: 12 (we will come back to this later in the answer!) Hint: Imagine the words represented different disciplines, cultures, concepts, and domains.

  5. 1. Enterprise Architecture:Definitions • WordNet Princeton - Enterprise: • S: (n) enterprise, endeavor, endeavour (a purposeful or industrious undertaking (especially one that requires effort or boldness)) "he had doubts about the whole enterprise" • S: (n) enterprise (an organization created for business ventures) "a growing enterprise must have a bold leader" • S: (n) enterprise, enterprisingness, initiative, go-ahead (readiness to embark on bold new ventures)

  6. 1. Enterprise Architecture:Definitions • WordNet Princeton - Architecture: • S: (n) architecture (an architectural product or work) • S: (n) architecture (the discipline dealing with the principles of design and construction and ornamentation of fine buildings) "architecture and eloquence are mixed arts whose end is sometimes beauty and sometimes use" • S: (n) architecture (the profession of designing buildings and environments with consideration for their esthetic effect) • S: (n) computer architecture, architecture ((computer science) the structure and organization of a computer's hardware or system software) "the architecture of a computer's system software"

  7. 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

  8. 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 VA NY ID MD

  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 SUPEREGO EGO ID ANALYSIS

  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 LICENSE CARD ID BADGE

  11. 2. Semantic Interoperability:Community of Practice • Origin: Requested by CIOC’s Best Practices Committee as a solution to doing public-private partnerships without violating FACA. • Charter: Accepted • See http://colab.cim3.net/cgi-bin/wiki.pl?SICoP • CIOC Strategic Plan: Participated in and activities mapped to it (especially Goal 2). • See two most recent conference at http://colab.cim3.net/cgi-bin/wiki.pl?SICoPSpecialConference2_2007_04_25 • Themes: Building DRM 3.0 and Web 3.0 for Managing Context Across Multiple Documents and Organizations and Building Knowledgebases for Cross-Domain Semantic Interoperability • Best Practices Committee's “best practices“ process followed: • See same as above for CIOC Strategic Plan. • Collaborations: NCOIC, DERI, W3C, IAC Emerging Technology Committee, CIOC Architecture & Infrastructure Committee, Semantic Technology Community, etc.

  12. 2. Semantic Interoperability:Community of Practice • Special Recognitions at the SICoP Special Conference 2, April 25, 2007: • Michael Lang, Revelytix: • Enterprise Data Modeling / SOA in a Semantic Wiki Knoodl.com. See slide 23. • Marguerite Ardito, Information Exchange, and Kevin Lynch, CIA: • Semantic Technologies and Vocabulary Management in the Context of An Overall Enterprise Data Architecture. • Parsa Mirhaji, MD: • Texas Health Center Taps Semantic Web http://colab.cim3.net/cgi-bin/wiki.pl?SICoPSpecialConference2_2007_04_25

  13. 2. Semantic Interoperability:Community of Practice • What's the purpose? • To develop members' capabilities; to build and exchange knowledge. • Who belongs? • Members who select themselves. • What holds it together? • Passion, commitment, and identification with the group's expertise. • How long does it last? • As long as there is an interest in maintaining the group. William Snyder, Building Communities of Practice. Excerpted from the article "Communities of Practice: The Organizational Frontier" in the Harvard Business Review, January-February 2000. http://hbswk.hbs.edu/archive/1317.html

  14. 2. Semantic Interoperability: Community of Practice • SICoP is chartered to do: • White Papers (3): • Introducing Semantic Technologies and the Vision of the Semantic Web (2005). • Semantic Wave 2006 - Executive Guide to the Business Value of Semantic Technologies. Update in 2007. • Operationalizing the Semantic Web/Semantic Technologies: • A roadmap for agencies on how they can take advantage of semantic technologies and begin to develop Semantic Web implementations (recently released for public review). • Conferences (10): 35 Special Recognitions (see next slide). • Pilots: More than 50 (see Wiki pages).

  15. Arun Majumdar (Cutter Consortium/VivoMind Intelligence) By SOA CoP Co-Chairs, Greg Lomow, Bearing Point & Brand Niemann, US EPA Best Practices and Architecture & Infrastructure Committees of the Federal Chief Information Officers Council SOA CoP Produced in Collaboration With Special Recognition For Outstanding Contributions to the SICoP and SOA CoP at the 2nd SOA for E-Government Conference, October 30-31, 2006, at The MITRE Corporation, McLean, VA. Federal CIO Council’s Service-Oriented Architectures Community of Practice (SOA CoP) and Semantic Interoperability Community of Practice (SICoP)

  16. 3. Service-Oriented Architecture: SOA Community of Practice • Origin: Requested by the CIOC’s Architecture & Infrastructure Committee • Charter: Announcements at the Chief Architects Forum and Industry Advisory Committee SOA Committee • See http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP • CIOC Strategic Plan: Participated in and activities mapped to it (Goals 1 – 4: See next two slides). • See most recent conference at http://colab.cim3.net/cgi-bin/wiki.pl?SOAforEGovernment_2007_05_0102 • Theme: Responsibility to Provide Best Practices for An Information Sharing Environment - Bringing Together the Global Information Grid, W3C, SOA Consortium, and Shared Services. • Best Practices Committee's “best practices“ process followed: • See same as above for CIOC Strategic Plan. • Collaborations: MITRE, IAC, SOA Consortium, W3C, KSG Shared Services, World-Wide Consortium for the Grid and GIGLite Community, etc.

  17. 3. Service-Oriented Architecture: SOA Community of Practice Stakeholders Input and Outreach People Business Goal 1* Goal 4 SOA Tutorials The “Medici Effect” SOA CoP Demo Phases 1-4 Information Technology Information Goal 3 Goal 2 SOA Architecture & Infrastructure SOA CoP Knowledgebase * See next slide for details.

  18. 3. Service-Oriented Architecture: SOA Community of Practice • Federal Chief Information Officer Council Strategic Plan (FY 2007-2009) 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.

  19. 3. Service-Oriented Architecture: SOA Community of Practice • Special Recognitions at the 3rd SOA for E-Government Conference, May 1-2, 2007: • Outstanding Contributions to the SOA CoP: • Chris Gunderson, World-Wide Consortium for the Grid (W2COG) and the GIGLite Community. Opening Keynote. • Outstanding Service to the SOA CoP: • Eric Newcomer, Robert Kilker, & Michelle Davis, IONA, Closing Keynote, SOA CoP Demo 3, and Tutorial. • Best Agency SOA Application: • Avi Bender and Tom Lucas, Internal Revenue Service. http://colab.cim3.net/cgi-bin/wiki.pl?SOAforEGovernment_2007_05_0102

  20. 3. Service-Oriented Architecture: SOA Community of Practice • Special Recognitions at the 3rd SOA for E-Government Conference, May 1-2, 2007 (continued): • Best Organization SOA Application: • Dr. Jon Siegel, OMG, Dr. Burc Oral, CellExchange, Inc., & Peter Bostrom, BEA Systems. SOA Consortium / SOA Practitioner’s Guide. • Best Exhibit: • Scott Campbell and Erik Peters, InterSystems. • Best Presentation: • Michael Lang, Revelytix. SOA in Semantic Wikis: A Story About Communication. See slides 12 and 23. • Best Breakout Session Presentation: • David Pawloski, SOA Software. Overcoming the SOA Network Security Fallacy. http://colab.cim3.net/cgi-bin/wiki.pl?SOAforEGovernment_2007_05_0102

  21. 3. Service-Oriented Architecture:Semantic SOA • SICoP: • Public Meeting (September 14, 2005): Semantic Interoperability Architecture Pilots, Rex Brooks and Team (Event Ontology) • 4th SIEGOV Conference (February 8-9, 2006): Best Co-Papers: Elisa Kendall, Sandpiper, Sam Chance, US Navy, and Michael Seebold, Concurrent Technologies Corporation: • Enables dynamic discovery of new services as they become available and provides resources for enabling semantic descriptions of those services. • 5th SIEGOV Conference (October 10-11, 2006): Arun Majumdar, Cutter Consortium, Operationalizing SOA: Lessons Learned (recall slide 15). • http://www.cutter.com/offers/SOAorSOS.html

  22. 3. Service-Oriented Architecture:Semantic SOA • SOA CoP: • 2nd Conference (October 30-31, 2006): Track 4: SOA and Metadata (Ontologies?) Organized by Chuck Mosher, MetaMatrix. • At the 4th SIEGOV Conference: Special Recognition for Best Semantic Harmonization Tool Application to Chuck Mosher, MetaMatrix (credit for Slides 7-10). • 3rd Conference (May 1-2, 2007): Best Presentation – see next slide. • 2007 Semantic Technology Conference, May 20-24, 2007: • Semantics and SOA (5): Semantic Arts, BEA Systems, Modus Operandi, Revelytix, SoftPro, and Intel. • Data Modeling (see slides 24-25).

  23. 3. Service-Oriented Architecture:Semantic SOA • SICoP and SOA CoP Special Recognitions: • Outstanding Contributions to the SICoP Special Conference 2, April 25th (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. • Demonstration at the June 18-19, 2007, W3C Workshop on eGovernment and the Web, National Academy of Sciences. http://colab.cim3.net/file/work/SOACoP/2007_05_0102/MLang05022007.ppt

  24. 3. Service-Oriented Architecture:Semantic SOA • Improve Data Quality: • 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. http://www.semantic-conference.com/2007/sessions/m5.html http://www.semantic-conference.com/2007/handouts/2-UpBW/Hay_David_2_2UpBW.pdf

  25. 3. Service-Oriented Architecture:Semantic SOA • Improve Data Quality: • 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.

  26. 4. Data and Information Architecture DRM 1.0 SICoP All Three unify DRM 3.0 Ontologies Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pp. 2-3. http://www.whitehouse.gov/omb/budintegration/expanding_egov_2005.pdf

  27. 4. Data and Information Architecture DRM 2.0 Implementation Metamodel • 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. Email, and Unstructured e.g. Paragraph. Source: Professor Andreas Tolk, 2005, and DRM 2.0 Implementation Through Iteration and Testing Report, October 15, 2005.

  28. 4. Data and Information Architecture * 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).

  29. 4. Data and Information Architecture • Three-tier Architecture for Goal 2: • Tier 1: Locate (E.g. Google) • Tier 2: Collaborate (Wiki Pages) • Tier 3: Integrate (Trusted Reference Knowledgebases - see next slide): • SOA Practitioner’s Guide (SOA Consortium) and Proceedings of Three SOA for E-Government Conferences! • The Federal Enterprise Architecture Data Reference Model 2.0 was written in the COLAB Wiki and is being implemented in Semantic Wikis!

  30. 4. Data and Information Architecture http://web-services.gov

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

  32. 5. Service Systems The Challenge: CIO Council Silos Stakeholders Input and Outreach People Business Goal 1 (recall slide 18) Goal 4 The “Medici Effect” IT Workforce Committee Executive Committee Information Technology Information Goal 3 Goal 2 Architecture & Infrastructure Committee Best Practices Committee Source: Pages 21-22, Federal Chief Information Officer Council Strategic Plan: FY 2007-2009, 28 pp. http://www.cio.gov/documents/CIOCouncilStrategicPlan2007-2009.pdf

  33. 5. Service Systems Example of a Service System Application and Interface Information People Information Technology Business http://campustechnology.com/articles/46250/

  34. 5. Service Systems Case Study for Service Research & Innovation Initiative (SRII) • Technology Services Research & Innovation Symposium, May 30th, Santa Clara Convention Center, California: • The Federal Chief Information Officer Council (the CIO Council) is used as a case study of the initial effect that the “Science of Service Systems” paradigm can have on enterprise process improvement for people working with information using information technology to accomplish a business purpose. This case study documents that we were actually moving towards it before we were formally introduced to it and have gotten some of the “Medici Effect” after consciously moving towards it. • http://www.thesrii.org • http://colab.cim3.net/file/work/BPC/2007-05-30/BNiemannSSRI05262007.doc • http://hbswk.hbs.edu/archive/4376.html

  35. 5. Service Systems • Wiki Knowledge Management: What Are We Thinking?: • Technology Can Enable Complex Adaptive Behavior in Human Knowledge Workers: • Together, Google and the Wikipedia manage more knowledge better and faster and cheaper than any other framework we have yet invented. • Source: Dr. Calvin Andrus, CIA. Closing Keynote, Knowledge Management 2007 Conference, April 3-5. • http://events.fcw.com/events/2007/KM/downloads/KM07_Keynote_Andrus_V1.pdf • SICoP is trying to enhance this with Trusted Reference Knowledge in Semantic Wikis.

  36. 5. Service Systems 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.

  37. 6. Information Sharing Environment Stakeholders Input and Outreach SOA Service Systems CoPs The “Medici Effect” Web Services Shared Services See next slide for details. Management of Change

  38. 6. Information Sharing Environment • Shared Services White Paper: Some Key Questions: • 1. What are Shared Services? • 2. Why are They Important to the U.S. Federal Government? • 3. What are Some Best Practice Examples of Shared Services? • 4. What are the Activities Related to Shared Services? • 5. What are Some Suggested Next Steps for Shared Services? http://colab.cim3.net/file/work/BPC/SOAJointTaskForce/BNiemann12082006.Doc

  39. 6. Information Sharing Environment • Shared Services White Paper: Some Key Questions: 1. What are Shared Services? • Shared services is an organizational form in which common functions across a number of departments/agencies are consolidated and undertaken by a specialized agency/service delivery center (1). • (1) EDS Government Journal volume one issue one, Government Transformation: Delivering public value, achieving policy objectives: How transformation can help governments meet the challenges ahead, Shared Services pages 17-24, by Suparno Banerjee, EDS Global Government http://www.eds.com/services/whitepapers/downloads/govt_journal_v1-1.pdf

  40. 6. Information Sharing Environment • Shared Services Community of Practice: A Persistent Learning Community of Senior Executive Practitioners, May 29-31, 2007: • Leadership for a Networked World Program: An Executive Education Program of the John F. Kennedy School of Government. Convening senior most shared services practitioners from the public and private sector to explore these matters. • Case Studies: • California E-Mail (Consolidation of over 200 systems). • Iowa’s Recovery Center (Dealing with diverse recovery standards). • Grant’s.Gov (One-stop to find and apply). • Cross-Boundary Governance Through Agreements and Standards: Assuring Compliance and Results, March 20-22, 2007, and Making Cross-Boundary Transformation Happen: The Role of Executive Sponsors, June 26-27, 2007. • Note: Followed different order than NASCIO (see next slide)! http://colab.cim3.net/file/work/SOACoP/2007_05_0102/ZTumin05022007.ppt http://www.lnwprogram.org/lnwprogram/workshop_shared_services

  41. 6. Information Sharing Environment • Getting Started in Cross-Boundary Collaboration: What State CIOs Need to Know, NASCIO’s Cross-Boundary Collaboration Committee (May 2007): • Executive buy-in and support. Elected officials need to be convinced of a collaboration’s potential for success. • Governance structure. A governance model that reflects that the leadership of the entities involved is crucial to collaboration. • Statutory limits. Some states may have privacy or security requirements regulating such activities as sharing sensitive data. • Fiscal responsibility. The collaborating parties need to determine which entity will take the fiscal lead or whether the project represents a shared investment. • Community of Practice. The report calls this approach a “natural way to begin the collaborative process.” http://www.nascio.org/publications/documents/NASCIO-CrossBoundaryCollaboration.pdf

  42. 6. Information Sharing Environment Google: Net-Ready Sensors

  43. 6. Information Sharing Environment Google: SOA CoP Demo 3

  44. 6. Information Sharing Environment Open Community SOA CoP Infrastructure

  45. 6. Information Sharing Environment • Tutorial 1 at the 3rd SOA for E-Government Conference, Wednesday, May 2nd, 8:30 AM - 12 NOON: • Title: Model-driven SOA (Architecture) • Presentor: Ed Seidewitz, Model Driven Solutions • Files: http://colab.cim3.net/file/work/SOACoP/2007_05_0102/Tutorial1/ • Audience: Enterprise Architects and Solution Architects • Outline: • Introduction • Business Architecture • Solution Architecture • Technical Architecture

  46. 6. Information Sharing Environment • Tutorial 2 at the 3rd SOA for E-Government Conference, Wednesday, May 2nd, 1 - 4:15 PM: • Title: Open Source SOA Bootcamp Using Celtix (Implementation) • Presentor: Michelle Davis, IONA • Files: http://colab.cim3.net/file/work/SOACoP/2007_05_0102/Tutorial2/ • Audience: Enterprise Architects, Solution Architects, and Software Developers • Outline: • Introduction to Web Services • Celtix Installation and Environment • Jumpstart Building Blocks

  47. 6. Information Sharing EnvironmentUS EPA Example Stakeholders Input and Outreach Strategic Plan & Performance & Accountability Report Innovation & Collaboration People Business The “Medici Effect” Office of the Chief Financial Officer Office of Human Resources Enterprise Architecture 2007 Report on the Environment Information Technology Information Office of the Chief Information Officer Office of Research & Development Capture the Semantics of the Organization and the Line of Sight.

  48. 6. Information Sharing EnvironmentUS EPA Example http://web-services.gov

  49. The Answer • “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.

  50. The Answer • 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.” (recall slide 4) • “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.

More Related