Ronla HenryNWS/OST/PPD

AWIPS Tech Infusion Overview and Status

May 11, 2009

National Weather ServiceNational Weather Service

2

Overview

• AWIPS Technology Infusion Scope

• Infrastructure Review

• Government Activities– Testing– Training– Site Migration– Governance

• Getting Ready

AWIPS TechnologyInfusion Scope

4

AWIPS TechnologyInfusion 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

• Data delivery enhancements: “Smart push-smart pull” data access• Visual collaboration enhancements • Information generation enhancements • Visualization enhancements

5

2007 2008 2009 2010 2011 2012 2013 2014

Phase IIAWIPS SOA Extension

= Fiscal Year

= Calendar Year

OTE / Deployment

Phase IAWIPS 1

Migration

Baseline (AWIPS I) Application Migration

NAWIPS Migration

Thin Client

WES Integration

Phase III Enterprise

Enhancements

Data Delivery- Smart Push/Pull

CHPS

IOC FOC

NWS Integrated Collaboration Phase 2 Phase 3

Streamlined Generation of Products IOC FOC

Advanced Visualization IOC

AWIPS TechnologyInfusion Roadmap

6

Service Oriented Architecture (SOA) Migration

Task Orders

Task Order (TO) Delivery DateMigrate primarily GFE capabilities (TO9) September 2008

Investigate technical issues/questions surrounding migration (TO-DTP)

February 2009

Migrate of primarily Hydrologic capabilities (TO10) February 2009

Task Order Development and Transition Planning (DTP) March 2009

SOA Migration Complete (TO11) November 2009

Provide of technical materials supporting training preparation following TOs 8-11 (TO-T1)

3 weeks following TO delivery date

Infrastructure

8

SOA MigrationRe-Architecture Approach

• Perform “black-box” conversion– Preserve existing functionality, look and feel on top of new

infrastructure

• No loss of functionality– Deployed system current with deployed AWIPS capability (i.e.,

Operational Build 9 (OB9))

• Thorough field validation and acceptance before deployment• Use open source projects - No proprietary code

– JAVA and open source projects enable AWIPS II to be platform and OS independent

• AWIPS Development Environment (ADE) enables collaborative development– Operating System (OS), Platform independence allows non-Linux

based research to be easily integrated into AWIPS II

9

SOA Architecture – Logical Layered ViewLayers Separated By Simple App Programming

Interfaces (APIs)Client/Presentation Services

Platform Layer

Mission Services Layer

Data Access Layer

Metadata Index

Data PersistenceStore

En

terp

ris

e S

erv

ice

Bu

s -

Co

mm

un

ica

tio

n

Se

cu

rity

Se

rvic

es

/D

em

ilit

ari

zed

Zo

ne

(D

MZ

)

SpatialIndex

Hydro Models

LAPS

FORTRAN/C/C++Command Line

Programs

External Programs

JMX

<<Java>>

DataLayer

PostgreSQLHDF5

<<abstract>>

BaseDao

Hibernate

<<Java>>

HDF5DataStore

HDF5 API

IngestSrv

PersistSrv

IndexSrv

ProductSrv

AdapterSrv

NotifySrv

SubscribeSrv

AutoBldSrv

PurgeSrv

Mbean

CAVE

StagingSrv

UtilitySrv

LocalizationStore

Government Activities

11

SOA MigrationTesting Approach

• Purpose:– Provide feedback to Raytheon on Task Order (TO) software

deliverables– Improve software quality in support of Operational Testing &

Evaluation (OT&E) and Deployment

• Layered Approach– IV&V (Independent Verification & Validation)

• Testing Objective: Push the system (Stress testing); Test to break• Testing based on TO contents• Includes “menu mapping” exercise

– UFE (User Functional Evaluation)• Testing Objective: Provide operational look at TO deliverables• Testing based on TO contents• Heavily focused on implementation variances of end-user functionality

– OT&E (Operational Testing & Evaluation)• Testing Objective: Verify AWIPS-II operationally ready for deployment• Controlled testing environment at operational sites• Follows evaluation of TO11

http://www.nws.noaa.gov/ost/SEC/AE/Testing.htmhttp://www.nws.noaa.gov/ost/SEC/AE/Testing.htm

12

SOA MigrationTraining Approach

• Purpose:– Ensure that developers able to utilize migrated software– Ensure that end-users able to configure, monitor, and

administer system

• Approach:– Development Organizations (GSD, MDL, OHD, SEC)

planning and executing training– NWSTD involved in planning and executing operational

training• Focus Areas:

– Local Application Developer– Application Focal Point– System Administration

http://www.nws.noaa.gov/ost/SEC/AE/Training.htmhttp://www.nws.noaa.gov/ost/SEC/AE/Training.htm

13

SOA MigrationSite Migration Approach

• Purpose:– Provide structured method to ensure local sites’

migration• Includes:

– Local Application Migration– Site Migration

» Application Configuration» Product Format Template Configuration

• Approach:– Team (regions, HQ) plan/coordinate– Regions/Offices execute

http://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htmhttp://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htm

14

AWIPS Technology Infusion Governance Approach

• What is it?– Governance model controls the development, test,

integration, configuration management, deployment and support of the new system -- both hardware and software

• Why?– SOA offers new levels of flexibility and extensibility– New rules needed to exploit system capabilities,

define limits– Tension between unlimited modifications and ability to

support the baseline systemhttp://www.nws.noaa.gov/ost/SEC/AE/Governance.htmhttp://www.nws.noaa.gov/ost/SEC/AE/Governance.htm

Summary

16

Summary

• 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