national aeronautics and space administration 1 technology infusion working group karen moe,...

1

NATIONAL AERONAUTICSAND SPACE ADMINISTRATION

Technology Infusion Working Group

Karen Moe, NASA/ESTORob Raskin, NASA/JPL

2nd Earth Science Data Systems Working GroupJoint Working Group Meeting

Greenbelt, MD October 18 – 19, 2004


Agenda

• Mission & Scope• Activities & Accomplishments• Draft Capability Vision Storyboard• Breakout Session Agenda


Tech Infusion Working Group

• Mission– Enable NASA’s Earth Science Enterprise to reach its research,

application, and education goals more quickly and cost effectively through widespread adoption of key emerging information technologies

• Scope– Information technologies that...

• Provide capabilities critical to the ESE mission & vision

• Have been substantially developed (TRL6-9) but have not been widely deployed

• Cannot be obtained simply through reuse of mature subsystems or software

• May be slow to be adopted because of the unique characteristics of Earth science (e.g., high data volumes)


Working Group Members

NAME AFFILIATION

Don Atwood Alaska Satellite Facility

Karl Benedict Earth Data Analysis Center

Yuechen Chi George Mason University

Jim Closs NASA/GSFC-SSAI

David Cordner NASA/LaRC

Peter Cornillon University of Rhode Island

Liping Di George Mason University

Elaine Dobinson JPL

Stefan Falke Washington U. in St. Louis

James Frew University of California

Kerry Handron Carnegie Museums

Michael Hodgson U. of South Carolina

NAME AFFILIATION

Rudolf Husar Washington U. in St. Louis

David Isaac Business Performance Sys.

Thomas Kalvelage LP DAAC / USGS

Erick Malaret Applied Coherent Tech.

Karen Moe NASA/ESTO

Neal Most Intelview

Rob Raskin JPL

Vince Troisi NSIDC

Fred Watson Cal State U. Monterey Bay

Brian Wilson JPL

Wenli Yang George Mason University

Tom Yunck JPL


FY04 Activities

• Elected Co-Chair (Rob Raskin)• Created working group charter and rules of operation• Established infrastructure for telecons and Web

collaboration• Conducted 31 telecons and two face-to-face meetings

including workshop at August ESIP Federation meeting• Developed visionary use cases• Developed vision “snippets” to capture key capabilities• Integrated vision snippets into a common scenario• Explored infusion barriers and strategies


FY04 Accomplishments

• Capability Vision– Defined in detail ten capabilities comprising an Earth science

information system capability vision– Achieved a shared understanding of the capability vision within

the working group– Created a draft “storyboard” for a vision presentation– Identified technologies critical to achieving the vision

• Infusion Processes– Identified barriers to infusing critical technologies– Identified project and enterprise-level infusion strategies

Note: capability vision is intended to help focus technology infusion, reuse, and standards efforts.


Capability Vision Focus

Interactive Algorithm

Construction

Interoperable Information

Services

Seamless Data Access

Assisted Information Selection

Assisted Knowledge

Building

Community Modeling

Frameworks

Responsive Information

Logistics

Verifiable Information

Quality

Evolvable Technical Infrastructure

Scalable Collaborative

Analysis


Infusion Process Focus

Barrier Infusion Strategies

Lack of critical mass • Encourage merging of similar/complimentary technologies

Interoperability problems • Promote open standards• Specify interoperability requirements in solicitations

New technologies not operationally robust

• Fund technology maturation & deployment

Lack of awareness • Foster communication & education • Technical workshops, “opportunity fairs”, community bulletin board, Earth Science Informatics conference, etc.

Unique Earth science requirements

• Provide technology configuration & deployment guide tailored for Earth science applications


Draft Capability Vision Storyboard

(10 min presentation)


TIWG Breakout Session Agenda

• Monday 2:30 – 3:15– Capability vision presentation (with detail)

• Monday 3:30 – 5:00– Joint Reuse WG recommendation discussion

• Tuesday 10:30 – 12:00– Capability vision discussion

• Consolidating capability themes• Prioritizing key technologies

• Tuesday 1:30 – 3:00– Infusion process discussion

• Potential TIWG, ESDS, and NASA activities• Infusing key technologies• Geospatial Web services roadmap

– Planning• FY05 working group activities• Meeting format and frequency


More Information

• Working group home page– http://lennier.gsfc.nasa.gov/seeds/WG/TI

• Working group collaboration site– http://www.sciencedatasystems.org/seeds/wg/infusion/

• Working group telecons– Thursday 4:00 EST– Dial in: 888-677-7890 Passcode: 82333

• Working group co-chairs– Karen Moe: [email protected]– Rob Raskin: [email protected]


Background


What is Technology Infusion?

• Technology Infusion– The gradual process of

identifying, understanding, adapting, and incorporating new but fully developed technologies into a set of systems

• Capability Vision– A high-level, user-oriented

description of the key future capabilities of ESE data systems

– Used to guide technology infusion efforts

New Technologies

Community Data Systems


• One of four groups established by the REASoN CAN– Standards & Interfaces

– Metrics Planning & Reporting

– Reuse Frameworks

– Technology Infusion

• Outgrowth of SEEDS– Strategic Evolution of ESE

Data Systems

– Explored ways to support ESE strategy

• More PI production processing

• Measurement-oriented systems

REASoN = Research, Applications, and Education Solutions NetworkCAN = Cooperative Agreement NoticeESDSWG = Earth Science Data System Working Groups

What is the Technology Infusion Working Group?

SEEDS

REASoN CAN

ESE Strategic

Plan

ProjectsProjects

Projects

• • • Data Life Cycle

ESDSWG• Standards• Metrics• Reuse• Infusion

New in 2005


Summary of SEEDS Study Recommendations

• Improve technology infusion– Deliver needed

capabilities– Prevent orphaned

technologies

• Define a capability vision– Focus technology

infusion efforts

• Extend strategic technology planning processes– Incorporate systems

vision into the process– Fund technology

infusion projects

INFUSIONPilots

IncentivesOutreach

Enablement

INFUSIONPilots

IncentivesOutreach

Enablement

CapabilityNeeds Identification

•ESE Visions, Roadmaps•ESTO Workshops

•SEEDS Workshops•ESIP Workshops

•REASoN Workshops?•Etc.

TechnologyProjection

* ESTO Workshops

TechnologyRoadmaps

Gap Analysis•ESTO Support

•New Mission Formulation•SEEDS PMO & Support?

Priority Weighting

Matrix

ESE Research Funding Process

•NASA HQ analysis•ESIS recommendations

Technology Infusion

•REASoN CAN•SEEDS Initiatives

Technology Development•REASoN CAN

•ESTO/CT Project•AIST NRA Topic 4

•CICT/IS NRA•Many Others

Needs/ Investment

Matrix

SEEDS Capability

Vision

ESTO Capability

Needs Database

ESTO Capability

Needs Database

New

New


Effective Technology

Infusion

Enterprise Context• Constrained budgets• Broad data service provider community

Pragmatic Infusion Approaches

• Information sharing• Demonstration testbeds

Emerging Technologies

• Tech program results• Web and grid computing

• Linux clusters

Organizational Goals• Increased community

participation• Lower system costs

• Increased flexibility & responsiveness

Internal

Opportunities

Drivers

External

Why is Technology Infusion Important?Drivers and Opportunities

• Need to meet organizational goals in the context of constrained budgets

• Opportunity to increase benefit from existing technology programs using pragmatic infusion approaches


Why is Technology Infusion Important?Meeting ESE Goals Requires Tech Infusion

• Science and application needs– Faster & better models– Near-real-time data – Easier data fusion

• Science community needs– Open distributed architecture

for PI processing• Current systems are lacking

needed capabilities

New Research

New Applications

New System Capabilities

System Capability

Vision

Technology Infusion

Technology Identificatio

n / Developmen

t

Science & App Needs


Capability Needs

Technology

Projections

Technology Roadmaps

Technology DevelopmentTechnology

Infusion

Operational Systems Identified

Gaps

Solicitation Formulation

Peer Review & Competitive Selection

Capability Vision

Technology Infusion is Part of a Larger System Evolution Process

• Think globally, act locally– How can we improve technology infusion across the community?

– How can you successfully infuse technology in your own projects?


How Can You Help & Benefit?

• Technology infusion process– Suggest changes to NASA and ESIP Federation processes that

would enable you to deploy key technologies more broadly– Share strategies that can help you and others successfully

deploy new technologies

• Capability vision– Ensure the capability vision reflects your priorities– Focus on key capabilities that help meet ESE goals– Share & adopt technologies that provide key capabilities


What Capabilities are Needed?

Capability BenefitAssisted information discovery Identify needed data quickly and easily

Seamless data access Enable access to any data from anywhere

Assisted knowledge building Provide research and operations assistance

Interactive algorithm construction Reduce research algorithm implementation from months to hours

Scalable collaborative analysis Provide computing power and data storage on demand

Interoperable information services Increase synergy within the ESE community through service chaining

Community modeling frameworks Enable linked and ensemble models for improved predictive capability

Responsive information logistics Ensure research priorities are met and enable new uses of ESE data

Verifiable information quality Provide confidence in products and enable community data providers

Evolvable technical infrastructure Exploit emerging technologies quickly


What are Common Barriers to Technology Infusion?

• Technical– Technologies are too complicated to deploy– Too many system interdependencies & incompatibilities

• Informational & Sociological– Insufficient awareness of key emerging technologies– Unclear cost/benefit ratio– Risk of problems and unexpected costs– Scientists don’t understand a technology’s potential– Technologists don’t understand science needs– IT support group lacks the time or commitment– General resistance to change

• Financial & Policy– Lack of funding for technology deployment & support– Risk of licensing fees being imposed after adoption– Difficulty obtaining approval for software distribution


• Technical– Harden prototypes through testbeds

• Participate in a relevant testbed to demonstrate operational readiness

• Current/past examples include OGC Web Services 2 testbed, NOAA/Navy/NASA Joint Hurricane Testbed, Proposed OGC Earth Science-Driven Testbed, NSF Middleware Initiative Testbed

• Others focused on Earth science needed– Facilitate experimentation through Web-accessible services

• Provide your technology as a Web-accessible service to let others experiment easily with your technology

• Removes the startup barrier, and helps potential users understand the capabilities & value offered

• Can be provided on an experimental or permanent basis– Promote open standards, open APIs, and open source solutions

• Viable standards can accelerate adoption of components/products that implement them

• Open source and open APIs allows a broad community to adopt and adapt software-based technologies for their specific needs

What are Some Strategies for Successful Technology Infusion?



• Informational & Sociological– Focus on key emerging technologies

• You can accomplish more if you don’t dilute your efforts

• Start with science/application goals, identify needed capabilities, and focus on technologies that provide those capabilities

– Clarify return on investment for key technologies• Users will adopt a technology if the value proposition is clear

• Needs to be more than hand waving

– Participate in early deployments• Hands-on experience is often the most convincing

– Promote partnering between scientists and technologists• Include partnering as an explicit evaluation criterion in solicitations

• Provide forums that make interaction possible (e.g., yesterday’s opportunity fair)



• Financial & Policy– Fund initial deployments and user support

• Technology development funds often do not cover these activities, which are critical to infusion

• Infusion will be slower if the first users bear all risks and costs• Possible role for your organization, ESIP Federation, and NASA

– Develop ROI and funding models for new technology deployments

• Technology deployment can be self-funding in some cases• Note: share-in-savings contracts are gaining ground as a way to get

over the hurdle of initial cost of changing to a new technology

– Promote appropriate data rights policies• Commercial acquisition of university-held licenses has made some

users unwilling to adopt certain technologies• Potential role for ESIP Federation to develop a position on data

rights language in solicitations• Technology developers should examine their own licenses in light of

the potential impact to adoption and infusion

national aeronautics and space administration 1 technology infusion working group karen moe,...

Documents