CMS 01_0171_igs- 1 Moving SECOORA Forward Conceptual Design of an Enterprise Architectural Framework Fact and Speculation 13 September 2006 Carroll A.

Slides:



Advertisements
Similar presentations
© GEO Secretariat Agenda Item 3. GEO UPDATE. © GEO Secretariat Membership 67 members and 43 Participating Organisations – New Members:Latvia, Moldova,
Advertisements

Building an Operational Enterprise Architecture and Service Oriented Architecture Best Practices Presented by: Ajay Budhraja Copyright 2006 Ajay Budhraja,
ITIL: Service Transition
e-Framework Components and Responsibilities.
Enterprise Architecture. 2 Agenda What is Enterprise Architecture (EA)? Roles in EA? Why is EA Important? Tangible Benefits from EA? What Do We Need to.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
Open Library Environment Designing technology for the way libraries really work November 19, 2008 ~ ASERL, Atlanta Lynne O’Brien Director, Academic Technology.
All Rights Reserved: JusticeExperts.com Enterprise? What Enterprise? Enterprise Development.
Thee-Framework for Education & Research The e-Framework for Education & Research an Overview TEN Competence, Jan 2007 Bill Olivier,
Interoperability. Martin Sykes Information architecture programs suffer from EA's worst problem: They have a strategic and enterprisewide focus that.
Lecture Nine Database Planning, Design, and Administration
Considering an Enterprise Architecture for the NSDI
The Planning Perspective Presented by Joel Eisenfeld – KFH Group.
Software Architecture April-10Confidential Proprietary Master Data Management mainly inspired from Enterprise Master Data Management – An SOA approach.
Enterprise Architecture
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Don Von Dollen Senior Program Manager, Data Integration & Communications Grid Interop December 4, 2012 A Utility Standards and Technology Adoption Framework.
DATA FOUNDATION TERMINOLOGY WG 4 th Plenary Update THE PLUM GOALS This model together with the derived terminology can be used Across communities and stakeholders.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
EGI-Engage EGI-Engage Engaging the EGI Community towards an Open Science Commons Project Overview 9/14/2015 EGI-Engage: a project.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Working Group: Practical Policy Rainer Stotzka, Reagan Moore.
The importance of a collective approach in delivering a thriving visitor economy Jason Freezer, Destinations Manager.
SOCIAL DEVELOPMENT CANADA 1 The Government of Canada and the Non-Profit and Voluntary Sector: Moving Forward Together Presentation to Civil Society Excellence:
Mid Wales LTP Stakeholder Workshop 3 rd October Presentation by Ann Elias and Janice Hughes.
Geospatial Enterprise Architecture Community of Practice Working Group Geospatial Community of Practice: Development of an FEA Geospatial Profile Briefing.
7 th GEO Capacity Building Committee Meeting Tashkent, Uzbekistan 3-4 June 2008 CB-07-01a Task report Marta ANGOLOTI AEMET Spain.
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All SMART GRID ICT: SECURITY, INTEROPERABILITY & NEXT STEPS John O’Neill, Senior Project Manager CSA.
Data Warehouse Development Methodology
JOINING UP GOVERNMENTS EUROPEAN COMMISSION Establishing a European Union Location Framework.
CLARIN work packages. Conference Place yyyy-mm-dd
Zdenka Willis Briefing to GCOOS March 4, 2010 US IOOS Update.
GBIF Mid Term Meetings 2011 Biodiversity Data Portals for GBIF Participants: The NPT Global Biodiversity Information Facility (GBIF) 3 rd May 2011.
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
Draft Modernization Roadmap for the Geospatial Platform Karen Siderelis NGAC Meeting March 25,2010.
1 Chapter 1 Introduction to Databases Transparencies.
EGovOS Panel Discussion CIO Council Architecture & Infrastructure Committee Subcommittee Co-Chairs March 15, 2004.
Promoting excellence in social security Building on sector wide commonalities to enhance the benefits of Information.
Geospatial LoB: Lifecycle WG Update November 3, 2009.
The Integrated Coastal and Oceans Observation System Act of 2009: Implementation 2009 IOOS Regional Coordination Workshop Thursday, August 27.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
The SouthEast Coastal Ocean Observing SECOORA Meeting Regional Association (SECOORA) June 11-12, 2007 Business Plan Overview.
Seeking SC Feedback on Draft Technology Strategy and Roadmap for EarthCube Draft of 3 November 2015 The Technology and Architecture Committee (TAC) Chairs:
1 VGIN’s GIS Strategic Plan Dan Widner VGIN Advisory Board Meeting January 6,
Technical Support to SOA Governance E-Government Conference May 1-2, 2008 John Salasin, Ph.D. DARPA
Hydro DWG at the RDA Plenary BoF - Improve sharing of water resource data globally 24 September BREAKOUT :30-15:00.
May 2007 Registration Status Small Group Meeting 1: August 24, 2009.
Report of the Architecture and Data Committee (ADC) R.Shibasaki (ADC, Japan)
25 April Unified Cryptologic Architecture: A Framework for a Service Based Architecture Unified Cryptologic Architecture: A Framework for a Service.
ARCH-04 Before You Begin Your Transformation Project… Phillip Magnay Architect – Applied Technology.
State of Georgia Release Management Training
National Geospatial Enterprise Architecture N S D I National Spatial Data Infrastructure An Architectural Process Overview Presented by Eliot Christian.
The FEA Data Reference Model V1.5 Michael C. Daconta, DRM Working Group Lead Susan Turnbull, AIC Representative Mary McCaffery, FEA PMO Representative.
1 SAIC XMSF Update XMSF Workshop & MOVES Open House 4-5 August 2003 Katherine L. Morse, Ph.D., David L. Drake, Ryan.
ISWG / SIF / GEOSS OOSSIW - November, 2008 GEOSS “Interoperability” Steven F. Browdy (ISWG, SIF, SCC)
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Data Management and Communications Current State Transition Actions Desired Future State (1 yr) Transition Actions Desired Future State (3-5 yrs) Operations.
ESS Enterprise Architecture Reference Framework Jean-Marc Museux, Eurostat 2016 UNECE CSPA Workshop on CSPA Geneva
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Data Management and Communications
ITIL: Service Transition
2009 IOOS Regional Coordination Workshop Thursday, August 27
Paul Eglitis [IEEE] and Siri Jodha S. Khalsa [IEEE]
WMO Integrated Global Observing System (WIGOS) 16-RA VI Side Event Helsinki, Finland, 11 September 2013 Dr Miroslav Ondráš, Dr Wenjian Zhang (WMO) Dr.
Metadata The metadata contains
Enterprise Architecture at Penn State
Introduction to SOA Part II: SOA in the enterprise
Presentation transcript:

CMS 01_0171_igs- 1 Moving SECOORA Forward Conceptual Design of an Enterprise Architectural Framework Fact and Speculation 13 September 2006 Carroll A. Hood GEOSS Chief Architect 13 September 2006 Carroll A. Hood GEOSS Chief Architect

CMS 01_0171_igs- 2 Fact

CMS 01_0171_igs- 3 GEOSS Framework IOOS Framework SECOORA Planning Framework Governance and Funding WG Product Development and Marketing WG Operational and Systems Performance WG Research and Development WG RA Goals and Objectives Governance Plan By-Laws, Articles of Incorporation Budget Requirements Outreach Plan Marketing Plan Regional Research Priorities Pilot Projects Workforce Sustainment.Training Plan Observations And Data Transmission SG Data Management and Communications SG Data Analysis and Data Products SG RCOOS Design Document Asset Inventory/Future needs System Performance Milestones/Metrics Ocean Data Partnership Standards/Protocols System Performance Milestones/Metrics Modeling/Forecasting Strategic Plan User Interfaces Private Section Coordination System Performance Milestones//Metrics IEOS or GOOS Framework

CMS 01_0171_igs- 4 Higher Level Frameworks n Designed to ensure that the GEOSS Value Proposition can be fulfilled – Individual assets can be easily discovered, accessed, and exploited by as wide range of potential users as possible; – Assets can readily be combined to support any number of value-enhancing end uses; and – The implementation strategy proactively strives to expand empowerment at all levels, promote equal opportunity access and reduce life cycle costs by facilitating sharing and reuse. n Designed NOT to – Dictate local priorities – Prescribe which assets can become part of the enterprise, – Dictate the business model that an asset or organization can employ, – Specify how assets operate internally n Designed to ensure that the GEOSS Value Proposition can be fulfilled – Individual assets can be easily discovered, accessed, and exploited by as wide range of potential users as possible; – Assets can readily be combined to support any number of value-enhancing end uses; and – The implementation strategy proactively strives to expand empowerment at all levels, promote equal opportunity access and reduce life cycle costs by facilitating sharing and reuse. n Designed NOT to – Dictate local priorities – Prescribe which assets can become part of the enterprise, – Dictate the business model that an asset or organization can employ, – Specify how assets operate internally

CMS 01_0171_igs- 5 Proposed SECOORA Enterprise Architecture Framework n Purpose – Provide guidance to the Working Groups and Subgroups to ensure that SECORRA development activities consider the context of IOOS, IEOS, GOOS, and GEOSS architectural frameworks Use what we need If we decide to go in a different direction, we do so with full understanding of the cost, the benefits and the implications n Activities – Develop an EA Framework for SECOORA – Vet framework through Working Groups – Publish/maintain SECOORA EA Framework Document n Constraints – Top-down guidance incomplete and not single source NOAA is currently normalizing the results from two IOOS Conceptual Design Studies GEOSS Secretariat is currently investigating options for developing Reference Architectures for GEOSS – Bottom-up driver required consensus across stakeholders We’re not there yet n Purpose – Provide guidance to the Working Groups and Subgroups to ensure that SECORRA development activities consider the context of IOOS, IEOS, GOOS, and GEOSS architectural frameworks Use what we need If we decide to go in a different direction, we do so with full understanding of the cost, the benefits and the implications n Activities – Develop an EA Framework for SECOORA – Vet framework through Working Groups – Publish/maintain SECOORA EA Framework Document n Constraints – Top-down guidance incomplete and not single source NOAA is currently normalizing the results from two IOOS Conceptual Design Studies GEOSS Secretariat is currently investigating options for developing Reference Architectures for GEOSS – Bottom-up driver required consensus across stakeholders We’re not there yet

CMS 01_0171_igs- 6 Speculation What Does it Mean to be GEOSS Compliant? Based On Raytheon's Proposed IOOS Conceptual Design

CMS 01_0171_igs- 7 GEOSS Architecture Framework n Assets. A GEOSS asset is any data stream, system, application, product or service that has utility or value to any potential GEOSS user. This definition is extremely broad and expansive – by design. We do not wish to constrain creativity or innovation in the ways in which GEOSS can create value to society. n Adapters. Adapters are the software that integrate assets into the GEOSS Enterprise. Adapters expose products or services to the Enterprise without impacting the systems or applications that they connect. Adapters are also used to connect users into the Enterprise. n Services Infrastructure. A GEOSS Services Infrastructure provides the “Backplane” or place where adapters physically integrate assets into the enterprise. A Service Infrastructure provides a common Asset Registry as well as the underlying communication, security and workflow services for the Enterprise. Replication of these services at multiple sites provides Enterprise-wide interoperability. n Assets. A GEOSS asset is any data stream, system, application, product or service that has utility or value to any potential GEOSS user. This definition is extremely broad and expansive – by design. We do not wish to constrain creativity or innovation in the ways in which GEOSS can create value to society. n Adapters. Adapters are the software that integrate assets into the GEOSS Enterprise. Adapters expose products or services to the Enterprise without impacting the systems or applications that they connect. Adapters are also used to connect users into the Enterprise. n Services Infrastructure. A GEOSS Services Infrastructure provides the “Backplane” or place where adapters physically integrate assets into the enterprise. A Service Infrastructure provides a common Asset Registry as well as the underlying communication, security and workflow services for the Enterprise. Replication of these services at multiple sites provides Enterprise-wide interoperability.

CMS 01_0171_igs- 8 GEOSS Architecture Framework (Logical View) Service Infrastructure GEOSS Enterprise SecurityWorkflow Communication Other Services Security Common Services User Asset Adapter (Data/Application Access) Adapter (Portlet) Workflo w Communications Registry

CMS 01_0171_igs- 9 GEOSS Architectural Framework (Physical View) GEOSS Node (geopolitical, thematic) Common Services Common Services Common Services Common Services Asset SECOORA

CMS 01_0171_igs- 10 GEOSS Asset Compliance n All GEOSS assets need to be registered with in a node of the GEOSS Asset Registry. n The required set of attributes for this registry have not yet been defined, but it will need to go beyond a typical Federal Geospatial Data Committee (FGDC) profile. – All data and information products will need to include Machine readable description of product format Semantic characterization (ontology) Full detailed history of relevant milestones with the complete product life cycle (full provenance) Characterization of quality – All applications and services will need to include: Full characterization of the service interface Full detailed history of relevant milestones with the complete application life cycle (full provenance) Characterization of its Service Level Agreement (SLA) – Availability – Business Rules or Constraints – Quality n All GEOSS assets need to be registered with in a node of the GEOSS Asset Registry. n The required set of attributes for this registry have not yet been defined, but it will need to go beyond a typical Federal Geospatial Data Committee (FGDC) profile. – All data and information products will need to include Machine readable description of product format Semantic characterization (ontology) Full detailed history of relevant milestones with the complete product life cycle (full provenance) Characterization of quality – All applications and services will need to include: Full characterization of the service interface Full detailed history of relevant milestones with the complete application life cycle (full provenance) Characterization of its Service Level Agreement (SLA) – Availability – Business Rules or Constraints – Quality

CMS 01_0171_igs- 11 GEOSS Adapter Compliance n All GEOSS Adapters should be registered in the GEOSS Asset Registry and placed into a software reuse library. n An item in the reuse library shall consist of – Documented source code – Full detailed history of relevant milestones with the complete adapter life cycle (full provenance) – Test procedures – Relevant Use Cases n All GEOSS Adapters should be registered in the GEOSS Asset Registry and placed into a software reuse library. n An item in the reuse library shall consist of – Documented source code – Full detailed history of relevant milestones with the complete adapter life cycle (full provenance) – Test procedures – Relevant Use Cases

CMS 01_0171_igs- 12 GEOSS Service Infrastructure Compliance n The evolution towards GEOSS will be facilitated by the development of a basic services infrastructure that can be replicated across the enterprise. n Replication provides a degree of local autonomy in terms of what assets need to be brought to bear for a particular national, regional or thematic community of interest; yet, because the service infrastructure is common, it promotes interoperability across the enterprise. n Replication provides a set of “common services” n Components of this basic service infrastructure include: – GEOSS Asset Registry (single system distributed across multiple sites) – Semantic Services (ability to create, update and map ontologies) – Discovery/Access Services (ability to plug in tailored portlets) – Security Services (ability to provide authentication, authorization) – Workflow Services (ability to chain together applications) – Development Services (support the development of adapters, portlets) n The evolution towards GEOSS will be facilitated by the development of a basic services infrastructure that can be replicated across the enterprise. n Replication provides a degree of local autonomy in terms of what assets need to be brought to bear for a particular national, regional or thematic community of interest; yet, because the service infrastructure is common, it promotes interoperability across the enterprise. n Replication provides a set of “common services” n Components of this basic service infrastructure include: – GEOSS Asset Registry (single system distributed across multiple sites) – Semantic Services (ability to create, update and map ontologies) – Discovery/Access Services (ability to plug in tailored portlets) – Security Services (ability to provide authentication, authorization) – Workflow Services (ability to chain together applications) – Development Services (support the development of adapters, portlets)

CMS 01_0171_igs- 13 SECOORA Testbed n Raytheon is working to develop a Demonstration of the proposed architecture that utilizes SECOORA assets n Use demo to establish support and develop business case for a SECOORA EA Testbed – Establish SECORRA Leadership in RA EA Development – Working Facility to test and improve interoperability – Springboard for R&D to extend the state-of-the-practice n Testbed would be a SECOORA asset, not a Raytheon asset n Raytheon is working to develop a Demonstration of the proposed architecture that utilizes SECOORA assets n Use demo to establish support and develop business case for a SECOORA EA Testbed – Establish SECORRA Leadership in RA EA Development – Working Facility to test and improve interoperability – Springboard for R&D to extend the state-of-the-practice n Testbed would be a SECOORA asset, not a Raytheon asset