improving operational space responsiveness

Improving Operational Space Responsiveness

Pat G. Cappelaere (pat@vightel.com)D. MandlL. DerezinskiS. Frye

EO-1

1

Responsive Space

A Better Question To Ask:

Has Rapid Space Deployment Generated A Better Operational Response From A User’s Perspective

2

Magritte

“This model designs military capabilities directly for the operational commander. The key attribute of the Operationally Responsive Space business model is that the field commanders drive the demand…”

Adm A. K. Cebrowski, OFT Director, 25 Mar, 2004

Operationally Responsive Space

A New Business Model

3

TACSATs

TACSAT-1

TACSAT-2

TACSAT-3

4

YASP (Yet Another Stove Pipe)

USCG D7 Matagorda, 110’

But: Where is the Don Matilde?

TACSAT-1

Tacsat-1 CopperfieldTacsat-2 TIE

5

NASA

SOPHISTICATED PAYLOADS...

SO WE ARE GETTING DATA...

EO-1 Terra

Aqua

Aura

IceSatCALIPSOALTAIR

6

Reality

Sept 11

Hurricane Katrina

Shortly after…

... about 2 weeks

7

Know your Customer

8

Problem Statement

• Restricted Data Access

• Science Data Rights

• We want to charge you (USGS)

• They Won’t Let You Have Access to It

• You Don’t Know Where the Data Is

• You Know Where it is But Don’t Know How to Get It

• Or You Can’t Have Access to It

• You Got It but Data Is Not in Right Format

• And It is Too Complicated to Process It Right

• Do Not Have a Scientist in the Trunk

• You Have Access to Satellite but It is Too Complicated to Task From the Field

• Data/User Mismatch

9

What Happened?

• Broader Audience

• Not just the engineers/scientists

• Many New Organizations Involved

• Broader Needs For Humanitarian Assistance/Emergency Response

• Plume, Contaminants, Oil Spills, Water..

• Those Users are Focused on Specific Products & Realtime Delivery

10

They Do Not Care About Infrastructure Or Plumbing

11

SensorWeb Enablement Concept

• Many SWE Data Nodes

• One or more Decision Support System

• Standard OGC Interfaces

Data Center

SD

SD

SD

Node

SD SD

SD

Node

SD

SD

SD

Node

PublicUser

Decision Support System

12

SensorWeb Enablement

• Users are shielded from Implementation Specifics

• Assets are Discoverable Using Catalog Services

SWE SWE SWE

User

CatalogService DSS

General Atomics Altair UASEO-1

Transparent User Access To Assets

13

Stilleto

SWE Data Node OGC Components

• Sensor Planning Service (SPS)

• Sensor Observation Service (SOS)

• Web Feature Service (WFS)

• Sensor Alert Service (SAS)

• Auxiliary Services

• Web Mapping Service (WMS)

• Web Coverage Service (WCS)

• Web Coordinate Transformation Service (WCTS)

• Catalog Service (CS-W)

14

DSS Easy Data Aggregation

• WFS-Basic / OpenSearch

• www.opengeospatial.org

• www.opensearch.org (Amazon)

• http://a9.com/

• GeoRSS Data Publishing & Mashup

• www.georss.org

15

SensorWeb Today

• Many Specifications... Still Evolving... OGC OWS-5: Next Iteration

• Good News:

• Open Source Reference Implementation: Ruby on Rails, GeoBliki

• We Are Producing Data

• We Are Delivering Data Products to Our Customers Based on Subscriptions (Pubsub)

16

OWS-4

17

OWS-4 EO Demo Participants

UAH VAST

GMU

Demis

Vightel Corporation

Innovative Solutions

GeoBliki

18

[Geo-Data] Mass Production

This is What We Achieved...19

But What Do We Really Need?

20

A Perfect Fit!

Custom Tailored Data Products For Customer Size=1

How Can We Get There?

• Automated Workflows

• Service-chains

• Bad News:

• BPEL, BPEL4WS, BPEL2.0…

• SOAP, WS-*

21What Did We Do For OWS-4?

GeoBrain

Still A Good Option

22

A New and Lighter Alternative Using Standards

<process-definition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.openwfe.org/flowdef.xsd" name="EO1 Tasking Workflow" revision="0.1" theme="n/a" security="restricted" > <sequence> <participant ref='XForms' task='RequestTasking’ comments='Enter EO-1 Tasking Parameters' /> <participant ref="SPS" task='GetFeasibilities’ comments='Check EO-1 Tasking Feasibilities'/> <participant ref='XForms' task='SelectFeasibility' comments='Select Desired Feasibility' /> <cancel-process if="${f:status} == 'cancelled'" /> <participant ref="SPS" task='Submit' comments='Submit Task to JPL'/> <cancel-process if="${f:status} == 'cancelled'" /> <participant ref="SOS" task='Publish' comments="SOS will make raw data available"/> <set field="msg" value="You've got data" /> <participant ref="WNS” task='Email' /> </sequence></process-definition>

BPMN

To XML via XPDL 2.0 23

With Other Open Tools

• OpenWFEru

• Process Engine

• Ruby Rools

• Inference Engine

• XForms

• User Interface

Ruby Rools

And a RESTFul Approach…24

Last Problem But Not The Least

• Identity 2.0

• Decentralized User Authentication

• Easy and Cheap to Implement

• User Centric/Open Source

• Relies on Trust among Cooperating Organizations/Entities

And You Want Me to Let People I Do Not Know Task My Satellite?

25

/ PKI Approach

DSS

IdP SWE

Identity Propagation

https

Email Organization Access Rights

26

Our Next Target: This Summer

For a More Operationally Responsive Space 27

Thank You!

• Pat Cappelaere, Vightel Corporation, MD

• pat@cappelaere.com

• Dan Mandl, NASA GSFC, MD

• dan.mandl@gsfc.nasa.gov

• Linda Derezinski, Innovative Solution, MD

• linda@i-sol.biz

• Stu Frye, Noblis, VA

• sfrye@noblis.org

28