Data Architecture, Modeling, and Networks Brand L. Niemann January 5, 2007

Definitions Data Architecture: Describes how data is processed, stored, and utilized in a given system. It provides criteria for data processing operations that make it possible to design data flows and also control the flow of data in the system. A term commonly used in one of two senses: physical (e.g., servers) and logical or enterprise-wide (e.g. Zachman framework) Data Modeling: A model that describes in an abstract way how data are represented in a business organization, an information system, or a database management system. Note: An Ontology is a data model that represents a domain and is used to reason about the objects in that domain and the relations between them. Data Networks: Communication of data between computers. For example, a semantic service oriented architecture.

Examples of Definitions Data Architecture Data Modeling Data Network Definitions Schematic of Data Flows Relationships Data Services An Architect Sketches and Drawings Blueprints and Scale Models Building An Enterprise Architect Architect Invest Implement Content DRM 2.0 DRM 2.0 Metamodel WS Nodes in a SOA Concept Map Knowledge Representation Ontology Semantic SOA State of the Environment Digital Library Indicator Ontology Performance Semantic Wiki Wiki and WS Nodes in SOA Emergency Response Disaster Event Event Ontology

The FEA Data Reference Model 2.0 DRM 1.0 SICoP All Three DRM 3.0 unify 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

DRM 2.0 Implementation Metamodel Note: The Data Network makes these links visible and searchable! 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.

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

Concept Map of DRM 2.0 Is_a Recall Slide 4 and see next slide for explanation.

Concept Map of DRM 2.0 Essentially a Data Model of a Data Model! PDF Version for Use in a Document, SVG Version for Use on the Web, XML Version for Structure, OWL Version for Semantic Relationships, and Simple Text Version. Source: Brand Niemann, Jr., Informal Communication, October 28, 2006, as part of the October 11, 2006, Birds of a Feather Meeting on National Information Sharing Standards at the Fifth Semantic Interoperability for E-Government Conference, October 10-11, 2006. http://colab.cim3.net/file/work/SICoP/2006-10-10/NatilStandards_10_11_2006.doc See Concept Maps Home Page at http://cmap.ihmc.us/

Data Networks Contents: History Semantic Wiki Pilots Semantic Technologies & Interoperability Enterprise Architecture Data Architecture XML EPA EPA Region 4 Environmental Health Webmaster http://web-services.gov/

Data Networks Contents: Federal Environmental Statistics Biological Resources Sustainable Development Indicators and Industrial Ecology Digital Library (State of the Environment and Federal Statistics) Indicators Community Programs Semantic Interoperability CEQ Roundtables Webmaster http://www.sdi.gov

Some New Initiatives Federal Sitemaps: http://colab.cim3.net/cgi-bin/wiki.pl?FederalSitemaps John Shirey – January 29th Practical Guide to Federal Service Oriented Architecture (SOA) Implementation: http://colab.cim3.net/cgi-bin/wiki.pl?ExpeditionWorkshop/CollaborativeOrganizingWorkshopToPlanWorkshops_01_23_07 Integration of Environmental Information and Indicators: January 25-26, 2007, Sustainable Water Resources Roundtable and Sustainable Development Indicators Web Site Upgrade: http://www.sdi.gov

Some New Initiatives Ontologies for the Government Domain (a monthly series): The National Academies Transportation Research Board 86th Annual Meeting. Workshop 163, Sunday, January 21, 2007, 1:30 p.m.-5:00 p.m., Hilton Washington. Benchmarking for Data Stewardship in Asset Management: http://colab.cim3.net/file/work/SICoP/2007-01-21/SICoPTRB01212007.ppt Building DRM 3.0 and Web 3.0 for Managing Context Across Multiple Documents and Organizations: Special SICoP Conference, February 6, 2007: http://colab.cim3.net/cgi-bin/wiki.pl?SICoPSpecialConference_2007_02_06

My EPA History 1980s: Data Modeling – Acid Rain Problem Lotus Most Innovative Application, Agency Most Innovative Application, and Computerworld Smithsonian Finalist (two years) 1990s: Data Networks – Environmental Statistics, Federal Statistics, and State of the Environment EPA Bronze Medal (first Data Network!) and Department of Interior and USGS Recognitions (on three year detail) 2000s: Data Architecture – LandView, Semantic Interoperability, Region 4, Data Reference Model 2.0, and Semantic Dataspace (distributed authoring of Data Networks!) OMB Quad Council Special Award for Innovation and Many Recognitions.

Current Activities Enterprise Architecture Team: Data Architecture: Leads the architecting of environmental and health information needed to truly understand the state of the environment, measure environmental performance gains, and enable EPA be able to be respond to emergencies. Collaborative Wiki Pages: http://colab.cim3.net/cgi-bin/wiki.pl?BrandNiemann CIO Council Activities: Architecture & Infrastructure Committee, Emerging Technology Subcommittee, and Best Practices Committee, Secretariat, and SICoP Co-chair and SOA CoP Co-chair. Federal Computer Week, Brand Niemann champions collaboration: EPA’s data architect does the groundwork to facilitate electronic data exchanges, October 20, 2006: http://www.fcw.com/article96594-10-30-06-Print

Metadata/Semantic Interoperability Paper for the CIO’s Office November 29, 2006, EPA/OTOP Business Intelligence and Analytics (BIA) User Group (UG) Meeting: BIA UG, Business Objects, and Informatica. Greatly assisted in this interactive session by Phil Magrogan (LMCO), who along with Steve Hufford, received the Special Recognition for Best Breakout Session Presentation at our recent 2nd SOA for E-Government Conference as judged by the IAC SOA Committee.

Metadata/Semantic Interoperability Paper for the CIO’s Office 1. Educate and empower the three user groups using common tools (BIA, SAS, and Statistics) to produce and register their applications as standard web services, otherwise they are not really useable/reusable in an agency SOA. We can and will pilot this to provide examples. 2. Maintain competition among the tools vendors to support open standards for metadata so the tools produce interoperable metadata, not proprietary metadata (e.g. Business Objects demonstrated their new product LiveOffice that takes Microsoft Office proprietary formats and puts them into another proprietary format!) I have already spoken with senior management at Business Objects about this because they want to participate in one of our SICoP pilots on semantic interoperability of person data and we told them what they need to do to be interoperable with the other vendors in the pilot. 3. Add semantic interoperability to what Informatica does for us. SICoP already has several pilots that demonstrate this.

EPA Segment Architecture EPA Segments: Services to Citizens (only 4 of 11 listed here): Air Quality Management Water Quality Management (I have the external-to-agency part of this) Toxic Substances Management Clean-up and Restoration Support Delivery of Services: Research & Science Geospatial Services (see new Spatial Ontology Community of Practice) Regulatory Development Management of Government Resources: IT Management Records Management Official Agency priority as reported to OMB –Serves as Test Case for Segment Architecture* Administrative Services * I suggest using the Wiki and Semantic Wiki Infrastructure!

EPA Segment Architecture Federal Enterprise Architecture Program Management Office (FEA-PMO) Update* – Dick Burk, Chief Architect, Office of Management and Budget (OMB): New guidance regarding segment architectures: The beginning of the fiscal year kicks off the six month period when agency architects should be working with program managers to design segment architectures for lines of business. Agencies can take the opportunity over the next several months to develop Line of Business (LoB) architectures that meet business needs while aligning to their agency enterprise architecture. A key to success is building a level of trust and cooperation between the architects and program officials. This partnership requires time listening to business leaders, and replacing architect-speak with business-speak. ‘Get out of your offices and stop drawing Visio diagrams and start helping the your business people and areas’ * The Federal Architect, December 2005, Volume 1, Issue 2, and the September 21st Architecture and Infrastructure Committee Meeting.