By Lawrence McGovern, SCdNorthrop Grumman Electronic Systems& International Council of System Engineers (INCOSE)10/29/09

Global Earth Observation

System of Systems

Global Earth Observation System of Systems (GEOSS) Description

• Being built by Group on Earth Observations (GEO)

• 10 Year Implementation plan in execution (2005-2015)

• Connect producers of environmental data and decision support tools with end users of products

• Objective enhancing the relevance of Earth observations to global issues

• Be a global public infrastructure that generates comprehensive, near-real-time environmental data, information and analyses for a wide range of users.

2

GEOSS Implementation

• Consists of 70 Task Workplan

• Each task supports nine Societal Based or Transverse Areas done by interested members, & participating Organizations. (International Council of System Engineers/Northrop Grumman Electronic Systems doing RM-ODP Architecture)

• GEO is developing the GEOPortal as a single Internet gateway to the data produced by GEOSS.

• The purpose of GEOPortal is to make it easier to integrate diverse data sets, identify relevant data and portals of contributing systems, and access models and other decision-support tools.

• Developed for users without good access to high-speed internet,

3

GEOSS Implementation

• GEO has established GEONETCast, a system of four communications satellites that transmit data to low-cost receiving stations maintained by the users.

• The GEOSS Implementation Plan identifies nine distinct groups of users and uses, which it calls “Societal Benefit Areas”.

• The nine areas are disasters, health, energy, climate, water, weather, ecosystems, agriculture and biodiversity.

• Current and potential users include decision makers in the public and private sectors, resource managers, planners, emergency responders and scientists.

4

RM-ODP Description

• Reference Model of Open Distributed Processing (RM-ODP) – is a Reference Model in computer science,

which provides a coordinating framework for the standardization of open distributed processing (ODP).

– It supports distribution, internet working, platform and technology independence, and portability, together with an enterprise architecture framework for the specification of ODP systems.

5

RM-ODP Standards

• RM-ODP, also named ITU-T Rec. X.901-X.904 and ISO/IEC 10746, is a joint effort by the International Organization for Standardization (ISO), the International Electrotechnical Commission (IEC) and the Telecommunication Standardization Sector (ITU-T)

• RMP View Model Viewpoints addressed in Volume 3 of ISO/IEC

10746

6

7

The ODP system specification Viewpoints

- Object configuration- Interactions between objects at interfaces

Computational

Enterprise- business aspects- What for? Why? Who? When?

- information- changes to information- constraints

Information

- Hardware and software components implementing the system

Technology

Engineering

- Mechanisms and services for distribution trans- parencies and QoS constraints.

- and correspondences between specifications

Viewpoints and Modeling

• Enterprise Viewpoint - Focuses on the purpose, scope and policies of the system and describes business requirements and how they are met

• Information Viewpoint - focuses on the semantics of the information and the information processing performed. It describes the information managed by the system and the structure and content type of the supporting data

• Computational Viewpoint - enables distribution through functional decomposition on the system into objects which interact at interfaces. It describes the functionality provided by the system and its functional decomposition

• Engineering Viewpoint - which focuses on the mechanisms and functions required to support distributed interactions between objects in the system. It describes the distribution of processing performed by the system to manage the information and provide the functionality

• Technology Viewpoint - which focuses on the choice of technology of the system. It describes the technologies chosen to provide the processing, functionality and presentation of information.

8

RM_ODP and UML

• ISO/IEC and the ITU-T started a joint project in 2004: "ITU-T Rec. X.906|ISO/IEC 19793: Information technology - Open distributed processing - Use of UML for ODP system specifications". This document (usually referred to as UML4ODP) defines use of the Unified Modeling Language 2 (UML 2; ISO/IEC 19505), for expressing the specifications of open distributed systems in terms of the viewpoint specifications defined by the RM-ODP

9

RM-ODP and SysML

• The System Engineering Modeling Language (SysML) Is an extension of UML syntax

• SysML Diagram Types were used to build Activity Diagrams , Block Diagrams and Internal Block Diagrams instead of UML Activity Diagrams, and Class Diagrams as specified in the UML Standard with permission of GEOSS Plenary

10

ENTERPRISE VIEW

11

UML Specification of GEOSS Community

12

«EV_CommunityContract»Enterprise View::AQ::GEOSS_Air Quality

EnterpriseView::AQ:-:Roles

Policies

UML Specification of GEOSSEnterprise Community

«EV_Community»«block»GEOSS

«block»«EV_Objective»

GEOSSObjective

EnterpriseView::AQ:-:Roles

Policies

UML Specification of GEOSSEnterprise Community

«EV_Community»«block»GEOSS

«block»«EV_Objective»

GEOSSObjective

«block»«EV_CommunityObject»

GEOSSCommunityObject

«EV_ObjectiveOf»

«EV_RefinesAsCommunity»

Policies have not been

determined as yet

Transverse Use Cases

13

Steps in use cases are defined by the Transverse workgroups. The Use Cases below are instances specific to the AQ WG.

Register Resources (see also CCRM transverse UC1)  Deploy Component & Services (Access)  Metadata via Clearinghouse (CCRM)  Client Search of Metadata (Portal/Client)   Services and Alert Presentation (Portal/Client) Interact with Services (Access)  Data Visualization & Analysis (Portal/Client) Workflow (Workflow)  Services Testing (Testing)  Interoperability Arrangements (CCRM)  

Use Cases: Air Quality & Health Specialized Use Cases:

https://sites.google.com/site/geosspilot2/

Transverse Use cases

14

GEOSS (E Spec)

15

Enterprise View::AQ::GEOSS (E Spec)

Enterprise Objects (global)

«block»«EV_CommunityObject»

GEOSS Domain

«block»

«EV_ODPSystem»

GEOSSPortal

«EV_CommunityContract»GEOSS

«block»«EV_Community»

GEOSS

Enterprise Objects (global)

«block»«EV_CommunityObject»

GEOSS Domain

«block»

«EV_ODPSystem»

GEOSSPortal«block»

«EV_CommunityObject»GEOSS Domain

«block»

«EV_ODPSystem»

GEOSSPortal

«EV_CommunityContract»GEOSS

«block»«EV_Community»

GEOSS

«block»«EV_Community»

GEOSS

«EV_RefinesAsCommunity»

AQ Community Roles

16

Roles

ActivityDiagrams

«block»«CV_Role»

Modeler

«block»«CV_Role»Actuator

«block»«CV_Role»

AQ Manager Analyst

ActivityDiagrams

«block»«CV_Role»

Modeler

«block»«CV_Role»Actuator

«block»«CV_Role»

AQ Manager Analyst

«EV_Community»«block»GEOSS

«EV_CommunityofBehavior»

«EV_CommunityofBehavior»

«EV_CommunityofBehavior»

Actor Role Fullfillment and Assignment Roles

17

GEOSSUser

Air QualityAnalysts

AQManagerAnalyst

Modeler

Person

Enterprise View –AQ Use Case Diagram

Modeler

AQManagerAnalyst

AQManagerAnalyst

AQ1 Get FireOccurence, Smoke andParticulate Matter data

AQ2 InitializeSmoke Forecast

ModelsAQ3 Obtain Smoke

ObservationProducts

AQ5 Visualizedifferences and

similarities in the SmokeForecast products

AQ4 Obtain Multiplesmoke observation

products

AQ6 Assess smokeforecasts to assess theneed for public alerts

AQ7Issue sensor taskingrequests to satellite and UAV

based sensors to collectsmoke impacted areas

AQ 8 Use smokeforecasts to anticipate

"exceptional" event waiverrequests by States AQ8

AQ9 Use apatial temporalcomparison services

between the forecast andobservation data

AQ10 Determinewhether "exceptional

event" waiver requestsshould be approved

«include»

«include»

«include»

«include»

«include»

«include»

«include»

«include»

«include»

18

Actors in the system - Descriptions

19

Enterprise View – SysML Activity Diagram

20

AQ Forecast Smoke Process State Diagram

21

do : InitiateSmokeForecast

InitateSmokeForecast

do : SendFireOccurenceData

RetrieveFireOccurenceDatado :PrepareDataUnavailableMess-age

DataUnavailable

do :SendSmokeForecastModelResults

RunForecastModel

do : SendForecastModelReport

ProvideForecastreport

/F ire Notific at io by M odeler

/F ireOc urrenc eDataA vailable

/Forec as tm odelreportS ent

/F ireoc c urenc eDataUnavailable

AQ Forecast Smoke Sequence Diagram

22

:USFS SmartfireSoapService :AQCommunityCatalogModeler

RequestFireoccurrenceData requestFireOccurenceDataSendFireoccurencedata

sendFireOccurenceDataRequestSmokeForecast requestFireOccurenceDataSendSmokeForecast

sendForecastReportProvideForecastReport

provideforecastReport

GEOSS Information Specification

23

Enterprise View::AQ::GEOSS (I Spec)

Information ObjectsInformation Actions

Current System

Information ObjectsInformation Actions

Current System

All three internal

Packages summarized

by Entity Relationship

Diagram

Information View – Entity Relationship Diagram

User

Name : StringID : String

RequestStatus

RequestedAcceptedDenied

ItemStatus

ProvidedNotAvailableBeingPrepared

UserStatus

AppliedEligibleRefusedValidDeletedArchived

CommunityCatalog

IsAvailable : Boolean

Policy Values

TBD

Requestor

ID : IdentifierRequestedItems : intStatus : RequestorStatus

Item

Id : IdentifierDateProvided : dateProvider : StringStatus : ItemStatusTitle : String

Correlation

ID : StringStatus : Item Status

Map

ID : StringStatus : Item Status

Report

11

1 1

1..*

1

0..1

1

1..*0..1

0..1

0..1

24

Computational View

25

Computational View – High Level Architecture Object Template (SysML Internal Block Diagram

26

Computational View –Detailed Architecture (SysML Internal Block Diagram)

27

Computational View – Interaction Signatures (SysML Blocks)

28

Computational View – Data Types (SysML Data Types)

29

GEOSS Way Forward in AIP3

• Develop Policies for each Societal Based Area Use Cases

• Update Enterprise/Information and Computational Views as necessary

• Develop Engineering View Diagrams

• Develop Technical View Diagrams

30

BACKUP SLIDES

31

32

Engineering View – Basic Engineering Objects (BEOs)

33

Engineering view – Enterprise Server Internals – SysML Internal Block Diagram

34

Technology Viewpoint Deployment Diagram (SysML IBD)

35

Technology View – Node Structure –(SysML IBD)

36

37