National Weather Service
AWIPS Technology Infusion
Unidata Policy Committee Meeting
May 12, 2009
Jason Tuell
Chief – Science Plans Branch
NOAA/NWS/Office of Science and Technology
1
Agenda
• Office of Science and Technology Overview
• AWIPS Technology Infusion Program Overview
• Scope
• Roadmap
• Status
• AWIPS Research to Operations
• Objective
• Strategies
– Data Rights Status
5/12/09
2
Office of Science and Technology
Overview
• OST Mission - Drive Science and Technology Advances into NWS
Operations
• OST Major Activities
• Planning, management, development and execution of major NWS
program including AWIPS, ASOS, NextRad and NWR, MOS, NDFD and
future systems such as NextGen WIDB
• Lead the development of the NWS Science and Technology Roadmap
• Coordinate plans and supports the execution and implementation of
science activities needed to improve NWS products and services
• OST Organizations
• Programs and Plans Division - Manages execution of program
management and development programs. Access science and
technology options
• Systems Engineering Center - Leads systems engineering,
development, integration, and testing of observing, information
processing, display, and communications systems.
• Meteorological Development Laboratory - Develop and implement
scientific techniques into National Weather Service Operations.
5/12/09
3
AWIPS Technology Infusion Scope
• AWIPS Technology Infusion (FY2005 – FY2014)
• A long-term project which delivers a modern, robust software
infrastructure that provides the foundation for future system level
enhancements for the entire NWS enterprise
• Phase 1: (FY2007-FY2010)
• Migration of WFO/RFC AWIPS 1 to a modern Service Oriented Architecture
(SOA) infrastructure
• Phase II: (FY2009-FY2011) – AWIPS SOA Extension
• Creation of a seamless weather enterprise spanning NWS operations
–
–
–
–
Migration of NAWIPS into the AWIPS SOA
Delivery of thin client to support Incident Meteorologists, e.g., Fire Weather,
Integration of “orphan” systems (e.g., Weather Event Simulator to support training requirements)
Integration of Community Hydrologic Prediction System (CHPS ) into AWIPS SOA
• Phase III: (FY2009 – FY2014) – Enterprise Level Enhancements
–
–
–
–
5/12/09
Data delivery enhancements: “Smart push-smart pull” data access
Visual collaboration enhancements
Information generation enhancements
Visualization enhancements
4
AWIPS Technology Infusion Roadmap
2007
2008
2009
2010
2011
2012
2013
2014
Baseline (AWIPS I) Application Migration
Phase I
AWIPS 1 Migration
OTE / Deployment
NAWIPS Migration
Phase II
AWIPS SOA
Extension
Thin Client
WES Integration
CHPS
Phase III
Enterprise
Enhancements
Data Delivery- Smart Push/Pull
IOC
NWS Integrated Collaboration
FOC
Phase 2
Phase 3
= Calendar Year
= Fiscal Year
Streamlined Generation of Products IOC
Advanced Visualization
5/12/09
FOC
IOC
5
AWIPS Technology Infusion Status
• AWIPS I application migration underway
• Eight incremental deliveries of infrastructure and functionality
provided thus far for NWS testing and evaluation
• Final incremental delivery of functionality (TO11) targeted for Fall
2009
• OTE begins – Winter 2009
• Deployment - 2010
• AWIPS SOA Extension projects that will enhance NWS
operations are underway
• NAWIPS migration in progress
– First incremental delivery of functionality provided to users for
testing/evaluation, April, 2009
– Next incremental delivery targeted for Fall 2009
• Thin Client, Data Delivery, CHPS, WES integration and Collaboration
Projects
– Requirements definition, AWIPS SOA evaluation and prototyping - 2009 ->
2010
– IOC targeted for FY11
5/12/09
6
AWIPS Research to Operations
• Objective - Enable faster and more effective infusion of new science
from research to operations into AWIPS
• Strategies
• Make AWIPS freely available to collaborators including research and
academic communities
– Government officially informed Raytheon that Government owns AWIPS data rights, April
2009
– Raytheon copyright markings on source code have been removed on TO11, Slice 1, April
2009
– AWIPS distribution subject to open source licensing agreements
• Establish open-source-closed community partnership
– Build open source project governance structure
– Provide AWIPS (Including NAWIPS components as open source), sans comms. and
product issuance software
• Build partnership with Unidata and research community
• Leverage open source projects to provide robust development environment,
tools, and support functions
• Utilize AWIPS plug in architecture to facilitate introduction of new algorithms
and data types by collaborators
5/12/09
7