Top Banner
Project “Steer Clear” 102 Total Interviews Challenge: How can we stop space collisions from making space unusable? Team Space Evaders Our plan: New method to evaluate debris creation. Sponsor: Amber Charlesworth, Office of Space and Advanced Technology
20

Space Evaders Lessons Learned H4Dip Stanford 2016

Jan 06, 2017

Download

Education

Steve Blank
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Space Evaders Lessons Learned H4Dip Stanford 2016

Project “Steer Clear”

102 Total Interviews

Challenge:

How can we stop space collisions from making space unusable?

Team Space Evaders

Our plan:

New method to evaluate debris creation.

Sponsor: Amber Charlesworth, Office of Space and Advanced Technology

Page 2: Space Evaders Lessons Learned H4Dip Stanford 2016

Kate BoudreauJunior, Biomedical

[email protected]

Background: Bioinformatic

research

Expertise: Biocomputation

Tyler DammannJunior, Computer

[email protected]

Background: Software, computer

science

Expertise: Technology, data

Dave GablerMasters, Business/

Public [email protected]

Background: Air Force, business

Expertise:Strategy, aerospace,

management

Matthew KasemanFreshman, Aerospace

[email protected]

Background: Army, gov’t contracting

Expertise: Engineering

implementation

Team Space Evaders

Page 3: Space Evaders Lessons Learned H4Dip Stanford 2016

Increasing # of satellites

Space debris threatens critical infrastructure (GPS, communications, etc)

The Challenge

Increasing collisions

More debris

Page 4: Space Evaders Lessons Learned H4Dip Stanford 2016

Interviewed over 100 stakeholders

Mapped the status quo

Built simple prototypes to test our ideas

Lean methodology

Page 5: Space Evaders Lessons Learned H4Dip Stanford 2016

First industry process map

Focused on data flow in the collision avoidance system

Page 6: Space Evaders Lessons Learned H4Dip Stanford 2016

The Path to CollisionsTracking Modeling Warnings Response

“This will be an eye-opener to many people!”

- Amber, State Department

Page 7: Space Evaders Lessons Learned H4Dip Stanford 2016

Original Hypotheses - Tracking1) Collision warnings based

on estimates only

GPS position

Observed position

We can improve avoidance capability through:- Communication - Data Sharing

2) Satellites know precisely where they are

Solution!

Page 8: Space Evaders Lessons Learned H4Dip Stanford 2016

We tested many ideas

Worldwide Operator phone book

GPS data-sharing

Define debris size/shape(helps prediction accuracy)

Small satelliteID hardware

Page 9: Space Evaders Lessons Learned H4Dip Stanford 2016

Answer #1:This is a small part of the problem

Page 10: Space Evaders Lessons Learned H4Dip Stanford 2016

Answer #2:Satellite operator decision matrix

Warning?

Maneuver?

< 1% chanceY

N

N Y

< .01% chance < .01% chance

< 1% chancebut now YOU

caused it

< 1% chance

“My chances are no better if I move, so why would I assume the responsibility?”

- Commercial Satellite operator

Page 11: Space Evaders Lessons Learned H4Dip Stanford 2016

Data sharing isn’t the problem - technical uncertainty makes the whole process unreliable

The underlying problem?

Collision warnings are only “in the ballpark”

Operators need MUCH more detail

Page 12: Space Evaders Lessons Learned H4Dip Stanford 2016

“This insight will frame our approach to this problem and has given us a new way forward

with the international community”

- Deputy Assistant Secretary

Page 13: Space Evaders Lessons Learned H4Dip Stanford 2016

The Path to CollisionsTracking Modeling Warnings Response

Mission Planning

Page 14: Space Evaders Lessons Learned H4Dip Stanford 2016

Too much decentralized, limited accountability decision-making

Space as a Tragedy of the Commons

Cost/schedule limitations can prevent debris mitigation efforts

Vague debris mitigation standards = significant design leeway

Page 15: Space Evaders Lessons Learned H4Dip Stanford 2016

Fix the Commons Problem

Make choices and consequences transparent and accountable

Debris Responsibility Score

Page 16: Space Evaders Lessons Learned H4Dip Stanford 2016

Final MVP: Debris Responsibility Score

Time in Space Size of Object Congestion of Orbit

Risk of On-Orbit BreakupPlanned Mission Debris

Page 17: Space Evaders Lessons Learned H4Dip Stanford 2016

“If you can show me it works, I would use it.”

-U.S. Government Regulator

“This needs to be presented at the next

satellite operators conference”

-International satellite operator

“I’ve wanted to do this myself for

years!”

-Leading industry expert/journalist

Page 18: Space Evaders Lessons Learned H4Dip Stanford 2016

Iteration/peer review

Best Practice

Community Standard

Deployment: Iteration & Acceptance

Page 19: Space Evaders Lessons Learned H4Dip Stanford 2016

Deployment: Expected Use Cases

NGO monitors tradable credits

international policy

Page 20: Space Evaders Lessons Learned H4Dip Stanford 2016

Summary

Instead of avoiding as many debris items asoperators choose to put in space...

...Our rating will work to prevent new debris fromgetting there at all