Transcript AWIPS Tech Infusion Status

National Weather Service
AWIPS Tech Infusion
Overview and Status
May 11, 2009
Ronla Henry
NWS/OST/PPD
Overview
• AWIPS Technology Infusion Scope
• Infrastructure Review
• Government Activities
– Testing
– Training
– Site Migration
– Governance
• Getting Ready
2
AWIPS Technology
Infusion Scope
AWIPS Technology
Infusion Scope
•
AWIPS Technology Infusion (FY2005 – FY2014)
•
Phase 1: (FY2007-FY2010)
•
Phase II: (FY2009-FY2011) – AWIPS SOA Extension
•
– 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
– Migration of WFO/RFC AWIPS 1 to a modern Service Oriented Architecture
(SOA) infrastructure
– 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
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
FOC
IOC
5
Service Oriented Architecture
(SOA) Migration
Task Orders
Task Order (TO)
Migrate primarily GFE capabilities (TO9)
Delivery Date
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)
SOA Migration Complete (TO11)
Provide of technical materials supporting training
preparation following TOs 8-11 (TO-T1)
March 2009
November 2009
3 weeks following TO
delivery date
6
Infrastructure
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
8
SOA Architecture – Logical Layered View
Layers Separated By Simple App Programming
Interfaces (APIs)
Client/Presentation Services
JMX
Mbean
IngestSrv
NotifySrv
ProductSrv
PersistSrv
AutoBldSrv
AdapterSrv
IndexSrv
SubscribeSrv
UtilitySrv
StagingSrv
PurgeSrv
Data Access Layer
<<Java>>
HDF5DataStore
<<Java>>
DataLayer
HDF5 API
<<abstract>>
BaseDao
Data Persistence
Store
External Programs
Hydro Models
LAPS
FORTRAN/C/C++
Command Line
Programs
Hibernate
Platform Layer
HDF5
Security Services /Demilitarized Zone (DMZ)
Mission Services
Layer
Enterprise Service Bus - Communication
CAVE
Localization
Store
Spatial
Index
PostgreSQL
Metadata
Index
9
Government Activities
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
• 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.htm
11
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
http://www.nws.noaa.gov/ost/SEC/AE/Training.htm
12
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
http://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htm
13
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
http://www.nws.noaa.gov/ost/SEC/AE/Governance.htm
14
Summary
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
16