1. Ronla Henry NWS/OST/PPD
National Weather Service
AWIPS Tech Infusion Overview and Status May 11, 2009
Ronla Henry
NWS/OST/PPD

2. Overview AWIPS Technology Infusion Scope Infrastructure Review
Government Activities
Testing
Training
Site Migration
Governance
Getting Ready

3. AWIPS Technology Infusion Scope

4. 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
Data delivery enhancements: “Smart push-smart pull” data access
Visual collaboration enhancements
Information generation enhancements
Visualization enhancements

5. 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
IOC
FOC
Data Delivery- Smart Push/Pull
NWS Integrated Collaboration
Phase 2
Phase 3
= Calendar Year
= Fiscal Year
IOC
FOC
Streamlined Generation of Products
Advanced Visualization
IOC

6. Service Oriented Architecture (SOA) Migration Task Orders
Task Order (TO)
Delivery Date
Migrate primarily GFE capabilities (TO9)
September 2008
Investigate technical issues/questions surrounding migration (TO-DTP)
February 2009
Migrate of primarily Hydrologic capabilities (TO10)
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

7. Infrastructure

8. SOA Migration Re-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. <<Java>> <<Java>> <<abstract>>
SOA Architecture – Logical Layered View Layers Separated By Simple App Programming Interfaces (APIs)
Client/Presentation Services
JMX
CAVE
External Programs
Mission Services Layer
Mbean
ProductSrv
IngestSrv
NotifySrv
Hydro Models
PersistSrv
AutoBldSrv
AdapterSrv
IndexSrv
SubscribeSrv
UtilitySrv
LAPS
Security Services /Demilitarized Zone (DMZ)
Enterprise Service Bus - Communication
StagingSrv
PurgeSrv
FORTRAN/C/C++
Command Line
Programs
Data Access Layer
The rendering shown here does not provide insight in how this state will be realized or cite its advantages.
It is similar to an architectural rendering of a building. To get a true picture of how the house will be built, we need the blueprints for construction.
User functions generally access from the top down.
The hardware is at the lowest layer, then basic services, then mission services, then user interface
Note that the term “services” is used for three of the layers.
The next few slides discuss SOA basics.
<<Java>>
HDF5DataStore
<<Java>>
DataLayer
<<abstract>>
BaseDao
HDF5 API
Hibernate
Platform Layer
Localization
Store
HDF5
PostgreSQL
Data Persistence
Store
Metadata
Index
Spatial
Index

10. Government Activities

11. SOA Migration Testing 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
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

12. SOA Migration Training 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

13. SOA Migration Site 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

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 system

15. 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
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 > 2010
IOC targeted for FY11