National Weather Service AWIPS II Overview and Status

National Weather Service AWIPS II Overview and Status AMS IIPS January 14, 2008 Ronla Henry NWS/OST/PPD

Overview • Contract Overview • Infrastructure Review • Government Activities • Testing • Training • Site Migration • Governance • Getting Ready 2

Contract Overview

SOA Migration Task Orders Task Order Develop of AWIPS SW PIP (TO 1) Delivery Date June 2006 Conduct Initial System Analysis (TO 2) Develop ADE/SDK (TO 3 -6) October 2006 July 2007 Plan Baseline Application Migration (TO 7) October 2007 Migrate primarily D 2 D/Warngen capabilities migrate (TO 8) Migrate primarily GFE capabilities (TO 9) February 2008 Investigate technical issues/questions surrounding migration (TO-DTP) Migrate of primarily Hydrologic capabilities (TO 10) SOA Migration Complete (TO 11) Provide of technical materials supporting training preparation following TOs 8 -11 (TO-T 1) September 2008 February 2009 November 2009 3 weeks following TO delivery date 4

SOA Migration Roadmap 2006 ATI OSIP Gates MPLS OBx 2007 2008 2 7 3 4 8. 3 8 Deployment Analysis ADE Development Meshed Topology 9 ADE Training Development ADE Training PIP RTS IRAD 2010 2009 OB 9 Dev & Test SW CTR (AWIPS II) Migration Strategy 10 New Release Paradigm NWS New Capability Development in ADE O & M Transition Prep & Coordination O & M Transition Migration Planning Baseline Application Migration Note: Task bar colors are For speaker reference only = Calendar Year = Fiscal Year “User” Functional Tests ADE Local App Training Local App Migration Deployment Planning 07/15/08 AWIPS II 1. 0 OTE / Deployment Support C& A OTE Deployment Field Ops Training -- ITO, ESA 5

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. , OB 9) • 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 • ADE enables collaborative development • OS, Platform independence allows non-Linux based research to be easily integrated into AWIPS II 7

SOA Architecture – Logical Layered View Layers Separated By Simple APIs Client/Presentation Services JMX Ingest. Srv Notify. Srv Product. Srv Persist. Srv Auto. Bld. Srv Adapter. Srv Index. Srv Subscribe. Srv Utility. Srv Staging. Srv Purge. Srv Data Access Layer <<Java>> HDF 5 Data. Store <<Java>> Data. Layer HDF 5 API <<abstract>> Base. Dao Data Persistence Store External Programs Hydro Models LAPS FORTRAN/C/C++ Command Line Programs Hibernate Platform Layer HDF 5 Security Services /Demilitarized Zone (DMZ) Mbean Enterprise Service Bus - Communication Mission Services Layer CAVE Localization Store Spatial Index Postgre. SQL Metadata Index 8

Government Activities

SOA Migration Testing Approach • Purpose: • Provide feedback to Raytheon on TO software deliverables • Improve software quality in support of OT&E and Deployment • Layered Approach • IV&V (Independent Verification & Validation) – Testing Objective: Push the system; 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 TO 11 http: //www. nws. noaa. gov/ost/SEC/AE/Testing. htm 10

AWIPS II Testing Status • IV&V • Continue to evaluate TO deliveries • Focusing on operational performance metrics • UFE • Conducted Forecaster Initial Testing – Evaluated software along side AWIPS – Assisted in developing operational scenarios • Continue to evaluate TO deliveries • Working side-by-side plan for TO 11 testing • OT&E • Working OT&E plan – Signature Coordination, May 2009 • Expected to begin around November 30 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 Training Status • Operational Training • Requirements Identified • Mechanism – Training for Trainers via Technical Interchange Meetings • Initial focus on preparing OT&E sites • Development Training • Completed 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 http: //www. nws. noaa. gov/ost/SEC/AE/Site_Migration. htm 14

AWIPS-II Site Migration Status • Local Application • NCLADT – Analyzed capabilities supporting local application migration in TO 8 & TO 9 – Provided input to Raytheon on capabilities provide (and to be provided) – Provided test cases supporting future TO deliveries – Developing a plan supporting local application migration based on TO 10 capabilities • Site Migration • Identifying configuration/customization files within existing system • Identifying any changes resulting from SOA Migration activities • Investigating obtaining Raytheon assistance in this effort 15

AWIPS-II 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 16

AWIPS-II Governance Status • Governance Sub-Teams • Release team – Working to document release paradigm – Concept includes • Monthly DR release • Quarterly “major” release • Local Application team • Began by reviewing existing policy • Restart in February, 2009 – Identify changes to policy and AIFM 17

Getting Ready

What can you do? • Focus on SOA Migration • Be Prepared – TO 10 • Local application migration, including Smart. Tools – TO 11 “Slices” • User Functional Evaluation • Side-by-side Testing – OT&E • Stay Informed – Weekly Topic Reports – Website Updates • http: //www. nws. noaa. gov/ost/SEC/AE – Upcoming NWS Focus Articles 19