GEOSSA Key to IEEE ComSoc

1
GEOSSA Key to IEEE ComSoc
Paul E. GartzPresident-elect, IEEE Systems
Council Past President, IEEE Aerospace and
Electronics Systems SocietyMark Hopkins Hotel,
San Francisco 2006-11-28 p.gartz_at_ieee.org
paul.e.gartz_at_boeing.com 1 206-954-9616
Seattle, USA
GP45126001.ppt
2
-
GEOSS Global Earth Observation SoS
Administered by GEO Group on Earth Observation,
Secretariat in Geneva
3
(No Transcript)
4
Weather and Climate Affect Everything!
5
(No Transcript)
6
GEOSS is Organized Moving Forward 10-year
Implementation Plan

• Plan Accepted by GEO Members
• 66 Nations 43 NGOs Feb 2005
• Phases 2, 6, 10 Years
• 9 Societal Benefit Areas
• Goal Comprehensive, coordinated, sustained
  Earth observation
• Architecture Data Comm Key
• IEEE Very Active NGO Member

7
Nine GEOSS Societal Benefit Areas
Water Resources
Natural Human Induced Disasters
Ecosystems
Energy Resources
Sustainable Agriculture Desertification
Human Health Well-Being
Oceans
Climate Variability Change
8
Defense, Commercial and Civil are
LinkedTelecommunications, Navigation,
Geospatial Info Used by All
9
Economic Exposure to Natural DisastersGEOSS Can
have a Huge Impact on Lives and Money and
EnvironmentGEOSS Global Earth Observation
System-of-Systems
Agriculture/Mining
Earth Observation Prediction
Construction
Transportation/Utilities
GEO/GEOSS
RetailTrade
Finances/Insurance
Services
. . .
Many More
Source Opportunities and Priorities in a New
Era for Weather and Climate Services Dutton
AMS 9/02
10
Status of GEOSS Architecture
11
Interoperability Objective
What few things must be the same so that
everything else can be different?
12
Common Glue is Needed for all SoSs
SoS Systems/Technologies Systems
Sensors
Computing, Software
Common- ication
Signal Processing
Networks
Navigation
Geo-Spatial Data
13
GEO/GEOSS is about Integration Paul E. Gartz,
Chairman TAB Earth Observation Committee to
Create IEEE Council
SoS Systems/Technologies
Networks
Vehicles
Sensors
Signal Processing
Comm
Computing Software
14
The IEEE and GEOSS

• The IEEE has a multi-society, multi-councilIEEE
  Committee on Earth Observation (ICEO) to provide
  leadership for our GEOSS contribution it is the
  formal interface with GEO
• The IEEE is actively leading or participating in
  Architecture, Standards, User Requirements/benefit
  s, technical training and education, and capacity
  building through
• GEOSS formulation
• workshops and conferences,
• Technical task teams
• Internet and public outreach

15
ICEO Structure
IEEE CEO J Pearlman
Executive Committee
User Interface
Science Technology
Outreach Capacity
Architecture Data
A Williams A Gasiewski
E LeDrew
W Ottichilo Lucia Kocar
R Garello
Wind Energy CP
Standards Interoperability
Renewable Energy CP
M Ahlstrom C Hasager Y Yuping
SJS Khalsa R Shibasaki
M Schroedter T Ranchin
16
IEEE Systems Council
17
Our Heritage and our Childrens Future

• What we do in
• the next ten years
• will determine
• what is possible
• in the next fifty

Courtesy of R. Anthes
18
GEOSS Needs IEEEAnd ICEO Needs ComSocs Deep
Participation Leadership
Questions?
19
Backups L1
AM2325.18
20
Paul E. GartzBio

• IEEEIn IEEE Paul has presidency positions in two
  IEEE business units called IEEE Operating
  Units. He is Past President of the Aerospace
  and Electronic Systems Society (AESS) and
  President-elect of the IEEE Systems Council. He
  re-organized AESS to expand globally and into
  systems-of-systems and created new officers for
  each major population and economic center in the
  world and began events of interest to Boeing in
  ATM, SoSs, Defense, UAVs, sensors, etc.
• BoeingIn Boeing Paul is a Systems-of-Systems
  Architect and member of the Boeing Technical
  Fellowship. He was Chief Architect for NOAA SoS
  and head airplane architect for a new Boeing
  wide-band SoS business called CbB. He led
  Boeings 1st commercial systems engineering
  groups and was part of the development teams for
  all modern Boeing commercial transports.

21
Saudi Logistics Land Bridge
Saudi Investment Announced as 1.1T over 10
Years
Saudi Arabia
Notional Possibilities Only
22
Apparent GEOSS Phasing
Create Bigger and Bigger Tents of Collaboration
Develop Joint 10-yearPlan
Focus Linking Existing Systems Reqmts
Science Inputs
Focus Politics Reqmts Govmt Inputs New
Orgs Relationships
23
GEO/GEOSS w/IEEE TimelinesPaul E. Gartz,
Chairman TAB Earth Observation Committee to
Create IEEE Council
24
Temperature Greenhouse Gas Histories Starting
at 400,000 yr BP
Is the present a normal oscillation or is it
Global Warming?
25
Times are changing?
??
Agriculture
Industry
26
IEEE Participation in GEO

• IEEE - A focal point for technical and
  engineering expertise
• Architecture
• Co-Chair of Architecture and Data Committee
• Formulation of Standards and Interoperability
  Forum
• System of Systems Engineering
• User Interface
• Wind Energy Community of Practice
• Renewable Energy CP
• Capacity Building
• Initial focus on developing countries

27
What is GEOSS?

• Address the need for timely, quality, long-term,
  global information as a basis for sound decision
  making.
• Improved coordination of strategies and systems
  for Earth observations to achieve 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, their
  effective utilization of observations 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 cost

28

• The international effort to develop an Earth
  observations system GEOSS will fundamentally
  change business operations, policy decisions, and
  resource management in real and substantial ways.
• Former US Secretary of Commerce Donald
  EvansAlliance for Earth Observations, September
  2004

29
Three perceptions of A System of Systems
A System for Integrating Observation, Modeling,
and Data Management Systems
Disaster
Health
Energy
Climate
A System for Coordinating the Nine Socio Benefit
Areas
Water
Weather
A System for Converging Observation Systems
Worldwide
Ecosystem
Agriculture
Biodiversity
30
GEOSS Challenges

• Interoperability what is it and how do we
  address it
• Integration of Human factors broader influence
  means more impacts
• Dynamic participation
• End to end integration what does it mean??
• Multiple ownership/prioritization
• SOSA understanding

31
GEOSS Architecture -Basic Standards and Services

• "The success of GEOSS will depend on data and
  information providers accepting and implementing
  a set of interoperability arrangements, including
  technical specifications for collecting,
  processing, storing, and disseminating shared
  data, metadata, and products."

from GEOSS Implementation Plan,
5.3 Architecture and Interoperability
32
Solutions to the Architecture Challenge

• A set of standard services, based upon customers
  currently accepted set of common tools with
  extensibility to embrace future common tools
• Standard messages based on common interactions
  between standard services
• A methodology for defining and managing the
  messages and contracts for the interaction
  between the standard services
• An integration framework built on a set of
  reusable components, including service bus,
  adapters, messages and message transports

33
The GEOSS Architecture
34
GEOSS Challenges

• Interoperability what is it and how do we
  address it
• Integration of Human factors broader influence
  means more impacts
• Dynamic participation
• End to end integration what does it mean??
• Multiple ownership/prioritization
• SOSA understanding

35
GEOSS Architecture -Basic Standards and Services

• "The success of GEOSS will depend on data and
  information providers accepting and implementing
  a set of interoperability arrangements, including
  technical specifications for collecting,
  processing, storing, and disseminating shared
  data, metadata, and products."

from GEOSS Implementation Plan,
5.3 Architecture and Interoperability
36
Facts for Implementation (1/4)

• Variety of users governments, private sector,
  academic, science, Users requirements and
  expectations vary a lot.
• Users to be closely associated to any design and
  implementation process
• Various communities with their own cultures data
  information providers / users with specific
  system interfaces data formats, own ways of
  processing information, ..
• No revolution imposed on work habits

37
Facts for Implementation (2/4)

• Distributed System Heterogeneous sets of
  world-wide distributed systems. Different
  technologies based on multitude of standards,
  proprietary solutions,
• No new single architecture imposed to everyone. ,
• Preserve the existing infrastructures as much as
  possible,
• Simple and robust interfaces and formats (based
  on common, open, and widely used standards).
• Progressive integration of thematic systems
• Fusion of sources Increasing user request for
  combined use of space and non-space data e.g.
  multi satellite missions with in-situ observation
  data

38
Facts for Implementation (3/4)

• Dynamic, Open system the SoS should be able to
  grow attract third-party data service
  providers and accept intermittent participation
  with disconnected/connected modes without
  disruption .
• Comprehensive information flow
• end to end - product order, planning,
  acquisition, processing, archiving and
  distribution for data and information

39
Facts for Implementation (4/4)

• User Interface Increase demand from users for
  enhanced quality of geo-spatial data, information
  and services with more user-friendly, faster,
  easier and transparent access
• Dependency between GEO tasks risks that optimum
  solutions (technical, programmatic, data policy,
  ..) for a given task are sometimes incompatible
  across-tasks

40
Solutions to the Architecture Challenge

• A set of standard services, based upon customers
  currently accepted set of common tools with
  extensibility to embrace future common tools
• Standard messages based on common interactions
  between standard services
• A methodology for defining and managing the
  messages and contracts for the interaction
  between the standard services
• An integration framework built on a set of
  reusable components, including service bus,
  adapters, messages and message transports

41
Status of GEOSS Architecture
42
Sample GEOSS Architecture Tasks
43
The IEEE Committee on Earth ObservationICEO
44
IEEE Participation in GEO

• IEEE - A focal point for technical and
  engineering expertise
• Architecture
• Co-Chair of Architecture and Data Committee
• Formulation of Standards and Interoperability
  Forum
• System of Systems Engineering
• User Interface
• Wind Energy Community of Practice
• Renewable Energy CP
• Capacity Building
• Initial focus on developing countries

45
ICEO Structure
IEEE CEO J Pearlman
Executive Committee
User Interface
Science Technology
Outreach Capacity
Architecture Data
A Williams A Gasiewski
E LeDrew
W Ottichilo Lucia Kocar
R Garello
Wind Energy CP
Standards Interoperability
Renewable Energy CP
M Ahlstrom C Hasager Y Yuping
SJS Khalsa R Shibasaki
M Schroedter T Ranchin
46
Summary

• SoSE A process for identifying SoS
  capabilities allocating such capabilities to a
  set of loosely coupled independent systems and
  coordinating development, production,
  sustainment, and other activities throughout the
  life cycle of a SoS
• The GEOSS SoSE Architecture Development Process
  is a common process at a global level -
  applicable to DoD, commercial and other customers
  - translated into the terminology and patterns of
  each customer

GEOSS is challenging and an excellent validation
of the SoS concepts and processes
47
What we do in this generation will determine the
destiny of our childrens children
Courtesy of Rick Anthes
48
Acknowledgements

• Eliot Christian
• Chris Stoughton
• Dennis Schwarz
• The ADC Co-Chairs

49
GEO Creation February 2005

• Earth Observation Summit III, Brussels, Belgium
• Established GEO
• 10 Year Implementation Plan
• Resolution Endorsing Plan
• Continued growth
• 2006 Tasks Implemented

50
Challenges

• GEOSS
• Disparate motivations
• Competing agendas
• Diverse backgrounds
• Varying technology levels
• Multiple views of data standards and quality

• US DoD SoS
• Uniformity of objectives
• Single corporate direction
• Cultural uniformity
• Common Technology
• Data standards and quality established
• Process for encouraging or enforcing
  participation