1. The Architecture of GEOSS Dr
The Architecture of GEOSS Dr. Jay Pearlman The IEEE Committee on Earth Observation September 21, 2007

2. The Information System (SoS) of GEOSS Dr
The Information System (SoS) of GEOSS Dr. Jay Pearlman The IEEE Committee on Earth Observation September 21, 2007

3. What is GEOSS?
Affirm the need for timely, quality, long-term, global information as a basis for sound decision making, leading to societal benefits globally
Improved coordination of strategies and systems for observations of the Earth with a view to moving toward a comprehensive, coordinated, and sustained Earth observation system or systems;
A coordinated effort to involve and assist developing countries in improving and sustaining their contributions to observing systems, as well as their access to and effective utilization of observations, data and products, and the related technologies;
The exchange of observations recorded from in situ, aircraft, and satellite networks, in a full and open manner with minimum time delay and minimum cost

4. The Earth is a complex system of systems
The Earth is a complex system of systems, and to understand it, data is required from multiple observation networks and systems. A Global Earth Observation System of Systems is required to meet the challenge
Data are required from multiple observation networks and systems

5. GEOSS – real world issues

6. Not just a large, complex system Dynamic, open environment
What is a “System of Systems?”
Definition:
A System-of-Systems (SoS) is a “super-system” comprised of elements that are themselves complex, independent systems which interact to achieve a common goal.
Common Characteristics:
Not just a large, complex system
The components systems are managed and have objectives in large part for their own purposes
It exhibits emergent behavior, not achievable by the component systems acting independently
Value of the synergy
Component systems, functions, and behaviors may be added or removed during its use
Dynamic, open environment

7. Interoperability Objective
What few things must be the same so that everything else can be different?
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different".

8. Architecture and Interoperability Approach
Build a flexible architecture and Integration framework on a set of reusable components
Leverage existing external and internal standards, architectures, and models
Capture future capabilities through open architecture
Support wide range of processes and environments
Integrate development through a service oriented architecture (SOA)

9. Core Architecture Users Components Registry Standards Registry
Candidate GEOSS Component
SBA Activity
GEOSS Base Standards
Request for help with interoperability
Component offered
Initial content
Experts, SDOs,
Interoperability capabilities of contributed systems
Contributed Systems Facilitator
Standards and Interoperability Forum
Consults
References standards
populates
populates
Components Registry
Services Registry
Special Arrangements Registry
Standards Registry
Service Component
Registry
Public Interface
accesses
GEOSS Clearinghouse
Points to
Portal to all EO data
Users

10. Architecture Implementation Objectives - 2006-7
Create an interoperability structure
Implement Registries for Components, Standards
Establish a web portal
Develop a clearinghouse for data and information
Provide for prototype operations
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different".

11. “Interoperability Arrangements”
When two GEOSS components conform to the same data description and transport standards, and are well-defined within the GEOSS registries, interoperability should be achievable with minimal effort
Where two GEOSS components do not share common standards, or where the service definitions are not adequate, interoperability “Special Arrangements” will need to be made.
This will be managed by the GEO “Standards and Interoperability Forum.”

12. The Standards and Interoperability Forum
Provides advice, expertise and impartial guidance on issues relating to standards and interoperability” for GEOSS.
Its objectives include:
help in the identification and adoption of standards required to achieve GEOSS interoperability objectives
facilitate cooperation among the many organizations, and national agencies of member countries, in selecting, developing and using standards applicable to GEOSS
support education and outreach for international participants and help increase technical and public awareness
Pretty tall order

13. Interoperability

14. IP3 Scenarios and Data Flows
NSIDC
Glacier change
Flood Risk Scenario
GBIF
Seismic Events from Glacier/Ice Sheet Disintegration Scenario
Soil moisture, stream gage, etc.
CEOP
Precip, soil moisture (TIGGE)
Species data
Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS)
Climate data (NCAR)
WIS
Fault Lubrication Scenario
Species Response to Climate Change Scenario
Precip, soil moisture (TIGGE)
Exotic event catalog
Event catalog
FDSN
Landslide Risk Scenario GA
Seismic Trigger

15.  Architecture Implementation Objectives - 2006-7
Create an interoperability structure
Implement Registries for Components, Standards
Establish a web portal
Develop a clearinghouse for data and information
Provide for prototype operations
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different".

16. Registries Context Community Web Portal Resources User GEOSS GEOSS
accesses
Community
Resources
Web Portal
accesses
searches
User
searches
get list of
catalogue
services
GEOSS
Clearinghouse
invokes
GEOSS
Component,
Service registry
references
accesses
This explains the relationship of registries and Clearinghouse. Numbers imply an order to the interactions.
Catalogues
Standards,
Special
Arrangements
Registries
contribute
register
Offerors
reference
Services

17. Register Information
on Services (1/2)

18.   Architecture Implementation Objectives - 2006-7
Create an interoperability structure
Implement Registries for Components, Standards
Establish a web portal
Develop a clearinghouse for data and information
Provide for prototype operations 
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different".

20.   Architecture Implementation Objectives - 2006-7 
Create an interoperability structure
Implement Registries for Components, Standards
Establish a web portal
Develop a clearinghouse for data and information
Provide for prototype operations 
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different". 

21. GEOSS Architecture GEOSS Clearinghouse GEOSS Catalog 3 GEOSS Service
GEOSS Portal
Web Browser
Search Service
Component Register
Reply
Query
Reply
Query
Reply
Query
GEOSS Catalog 3
GEOSS
Clearinghouse
Service Register
Harvest in advance
GEOSS Service
Protocol A
Protocol B
I thought George’s diagram from the Clearinghouse RFI could be enhanced to show more possible interactions, processes and registers, but didn’t get farther than this.
Register
Services
Query/Reply
Query/Reply
Query/Reply
Non-GEOSS Service
GEOSS Catalog 1
Non-GEOSS Catalog 2

22.   Architecture Implementation Objectives - 2006-7  
Create an interoperability structure
Implement Registries for Components, Standards
Establish a web portal
Develop a clearinghouse for data and information
Provide for prototype operations 
As a "System of Systems", the success of GEOSS depends on how well the contributed systems achieve "Interoperability".
Here, interoperability is that condition wherein differences among systems are not a barrier to a task that spans those systems. The focus is on how systems work together. GEOSS itself does not delve into how the contributed systems operate within themselves.
The GEOSS Implementation Plan Reference Document makes this statement:
"GEOSS does not mean an attempt to incorporate all Earth observing systems into a single, monolithic, centrally controlled system.
It is intended to improve the data supply to users and not as a justification for annexing existing observation and data distribution systems into a new international organization."
Put another way, the GEOSS architecture will specify just those "few things that must be the same so that everything else can be different".  

23. Documentation for contributors

24. Potential Plans 2008-9 more details (1)
Operations
Institute Operational Capability – Phases 1,2
Portal, Clearinghouse, SIF, Registries
Maintain Reference Cases – IP3, …
Interoperability
Metadata, data harmonization
Quality Assurance approach and processes
Data Sharing Principles

25. Initial Operational Capability by Nov. 2007
Societal Benefits

26. What we do in this generation will determine the destiny of our children’s children
Courtesy of Rick Anthes