1. 1 Issues in the Architecture: SOA and Semantic Web Brand Niemann Data Architect, U.S. EPA Co-Chair, Federal Service Oriented Architecture (SOA) Community of Practice and the Federal Semantic Interoperability Community of Practice November 16, 2006 (See Proposal Added to Slide 23 After Seminar)

2. 2 Introduction Leading-Edge Government, IT Management – Server Consolidation, Virtualization and Other Best Practices. Some Questions Considered: –What are the major issues being discussed in the blogs? –What are some alternative architectures and chip sets that you should understand as you migrate or consolidate Unix-based applications? –What steps can be taken to realize efficiencies in performance, security and cost to accommodate increasing server consolidation?

3. 3 Introduction This timely seminar looks at new best practices that government and commercial organizations are adopting to streamline IT using server consolidation, virtualization, and open source methods. Performance and the Role of Architecture in Server Consolidation, Carl Drisko, Data Center Best Practices Leader, Novell Consulting: –Novell and Microsoft sign agreement that “bridges the divide between open source and proprietary software” (Steve Ballmer, Microsoft CEO). Advanced Virtualization Support Using Quad Core, Margaret Lewis, Commercial Solutions Director, AMD: –A glimpse into the future of the Quad Core Processor Road Map.

4. 4 Overview Best Practices: –Secretariat, Federal CIO Council’s Best Practices Committee: Documentation of Successful Implementations Based on Standards. “Champion Collaboration to Facilitate Electronic Data Exchange” (Power Player 2006, FCW, October 30, 2006) Streamline IT: –Co-Chair of the Federal SOA CoP: Bringing SOA with Governance to the Federal Enterprise Architecture. Open Source Methods: –Co-Chair of the Federal Semantic Interoperability CoP (SICoP): Logical Inference Over Distributed Knowledge Bases.

5. 5 Overview ComputersFunctionExample ServersContent Management & Data Architecture Many (documents and databases) ServicesWeb-ServicesAmazon.Com (transactions) KnowledgeSemantic WebGoPubMed (ontology organization)

6. 6 Overview Rather Than Talk Abstractly: –Use an Example of a Major Federal Government Program for Information Sharing That is Going Through this Evolution (File- Sharing and Data Architecture to Web Services in a SOA to Knowledge Computing) and How IT Management – Server Consolidation, Virtualization and Other Best Practices Come Into Play.

7. 7 Example National Information Exchange Model (NIEM): –A partnership of the U.S. Department of Justice and the Department of Homeland Security. It is designed to develop, disseminate and support enterprise-wide information exchange standards and processes that can enable jurisdictions to effectively share critical information in emergency situations, as well as support the day-to-day operations of agencies throughout the nation. –NIEM will standardize content (actual data exchange standards), provide tools, and managed processes. –NIEM builds on the demonstrated success of the Global Justice XML Data Model. See http://www.niem.gov/

8. 8 Suggested NIEM Roadmap From ZIP Files: –Information Exchange Package Documentation (e.g. Amber Alert, a bulletin or message sent by law enforcement agencies to announce the suspected abduction of a child.) (a Zip file) –Download Current Release and Documentation (niem-1.0-with-docs- 110106.Zip) (see next slide)

9. 9 Suggested NIEM Roadmap One ZIP File (3.5 MB): –Eight PDF Files (2 MB) –One Excel File (56 KB) –One ZIP File (XML Files) (1.7 MB) About 30 Web pages Note: My EPA Spam Filter automatically deletes ZIP files so this is not the way to share information.

10. 10 Suggested NIEM Roadmap And Limited Data Architecture: –NIEM only addresses part of the Federal Enterprise Architecture’s Data Reference Model 2.0 (see next slide) –So lets repurpose the NIEM ZIP files to make them a DRM 2.0-compliant Data Architecture that functions like Web Services in a SOA (nodes communicate with each other with SOAP-like messages) and the virtualization makes it look and function as though it is on one server and includes the DRM 2.0 Implementation Metamodel (see slide 13) on the way to Knowledge Computing (see slide 14).

11. 11 Suggested NIEM Roadmap And Limited Data Architecture (continued): –Source of Slides 13 and 14: Data Reference Model Implementation Through Iteration and Testing Version 1.0, October 17, 2005 (Updated November 21st for Section 508 Compliance of the Graphics). http://web- services.gov/DRMITIT10172005.doc. –This is a functioning pilot of the NIEM Roadmap!

12. 12 The FEA Data Reference Model 2.0 Source: Expanding E-Government, Improved Service Delivery for the American People Using Information Technology, December 2005, pages 2-3. http://www.whitehouse.gov/omb/budintegration/expanding_egov_2005.pdf NIEM 1.0 NIEM Roadmap Pilot

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

14. 14 SICoP Knowledge Reference Model The point of this graph is that Increasing Metadata (from glossaries to ontologies) is highly correlated with Increasing Search Capability (from discovery to reasoning).

15. 15 NIEM Roadmap Pilot

16. 16 NIEM Roadmap Pilot Imagine that the Nodes, Subnodes, etc. could be for organization, Threat Category, Persons of Interest, Intelligence Analysis, etc.

17. 17 NIEM Roadmap Pilot Department of Justice: –Bureau A Person of Interest X –Threat Analysis 1 –Etc. Department of Homeland Security –Bureau B Person of Interest Y –Incident Report 2 –Bureau C Person of Interest Z –Interview Report 3 –Etc. Content Management Services Knowledge Moreover, the level of integration that is possible today is evident in an ever-expanding array of online services in commercial endeavors and consumer products (e.g., eBay and Amazon.com). Surely, first responders should be able to share information and effectively communicate in emergency situations, when seconds count and lives are at stake. NIEM CONOPS, Page 6)

18. 18 Suggested NIEM Roadmap To Service Oriented Architecture and Knowledge Computing: –NIEM at the 2 nd SOA for E-Government Conference, October 30- 31st: Chris Travers, Office of Justice Programs, U.S. DOJ: –Justice Reference Architecture: Service-Orientation for the State and Local Justice Community Tom Clarke, National Center for State Courts, Chair, Global Infrastructure/Standards Working Group, and Co-chair, NIEM Technical Architecture Committee: –Achieving Justice Information Interoperability –Very Relevant Presentations: Kapow Technologies, SOA Solutions: The Future of Information Sharing is Now (Live data from multiple heterogeneous data sources) Arun Majumdar (Cutter Consortium/VivioMind Intelligence), Operationalizing SOA - Lessons Learned (SSOA Metamodel) SOA for Information Sharing, Track 2, Organized by Greg Lomow, Bearing Point, and SOA Co-Chair (Information Bus - see slide 20)

19. 19 Suggested NIEM Roadmap To Service Oriented Architecture and Knowledge Computing: –NIEM at the 5 th Semantic Interoperability for E- Government Conference, October 10-11 th : Richard MacKnight, System Planning Corporation, NIJ/USDOJ, NIEM: –Panelist for The Role of DRM 2.0 “Context” in the Development of National Standards for Information Sharing. –NIEM Followup After the Conference: Review of NIEM Ontology (Adam Pease for DHS). Invitation to Co-Chair the Vocabularly Management WG with Michael Lang, Revelytix, Using the Knoodl Semantic Wiki.

20. 20 FinMgmt Services Border Surveillance Grants Services HR Services Asset Mgmt Services Tax Fraud Detection Information Bus PublishSubscribe & Notify PublishSubscribe & Notify Metadata Repository Information Broker Semantic Integration Subscription Mgmt Content Delivery & Caching Data Fusion Situational Awareness Search / Retrieval Collaboration Information Dissemination BI & Analytics Business Reporting Geospatial Services Content/ Doc Mgmt Shared Data Spaces Data Exchange Services Federal Agencies State & Local Gov’t Citizens Foreign Governments Commercial Organizations International Organizations Homeland Security National Defense Law Enforcement Counter Terrorism Public Health Public Safety Emergency Response

21. 21 Summary How this example shows how the Federal Government will need IT Management – Server Consolidation, Virtualization and Other Best Practices. SICoP Co-Chair, Mills Davis: Semantic Web Driver for Advanced Processors –Graphics (e.g. GIS, Semantic Web Display, etc. will take even more processor power) Contact Information: –Brand Niemann: niemann.brand@epa.gov, 202-564- 9491.

22. 22 Summary Some URLs: –http://colab.cim3.net/cgi-bin/wiki.pl?SICoP –http://colab.cim3.net/cgi- bin/wiki.pl?FifthSemanticInteroperabilityforEGovernm entConference_2006_10_1011 –http://colab.cim3.net/cgi- bin/wiki.pl?SOAforEGovernment_2006_10_3031 –http://vkwiki.visualknowledge.com/wiki/sensors –http://knoodl.com (active soon)

23. 23 Proposal Bring this to the Federal CIO Council/OMB under their new Infrastructure Optimization Line of Business as a White Paper, even Pilots, and Seminar or Conference over the next 3-6 months using virtual conference calls, etc. The 5 steps we follow are: –1. Draft a Mission Statement –2. Draft a Membership List and Select a Government and Non- Government Co-Chairs –3. Draft a Strategy (e.g. White Paper, Pilots, and Seminar/Conference) –4. Hold An Open Conference Call Using a Public Wiki to Publish Items 1-3 for All to See –5. Get Agreement to Work Together to Build a Knowledge Base to Support the Strategy.