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

2. 2 6/3/2015 Overview Contract OverviewContract Overview Infrastructure ReviewInfrastructure Review Government ActivitiesGovernment Activities TestingTesting TrainingTraining Site MigrationSite Migration GovernanceGovernance Getting ReadyGetting Ready

3. 3 Contract Overview

4. 4 6/3/2015 SOA Migration Task Orders Task Order Delivery Date Develop of AWIPS SW PIP (TO1) June 2006 Conduct Initial System Analysis (TO2) October 2006 Develop ADE/SDK (TO3-6) July 2007 Plan Baseline Application Migration (TO7) October 2007 Migrate primarily D2D/Warngen capabilities migrate (TO8) February 2008 Migrate primarily GFE capabilities (TO9) September 2008 Investigate technical issues/questions surrounding migration (TO-DTP) February 2009 Migrate of primarily Hydrologic capabilities (TO10) February 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

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

6. 6 Infrastructure

7. 7 6/3/2015 SOA Migration Re-Architecture Approach Perform “black-box” conversionPerform “black-box” conversion Preserve existing functionality, look and feel on top of new infrastructurePreserve existing functionality, look and feel on top of new infrastructure No loss of functionalityNo loss of functionality Deployed system current with deployed AWIPS capability (i.e., OB9)Deployed system current with deployed AWIPS capability (i.e., OB9) Thorough field validation and acceptance before deploymentThorough field validation and acceptance before deployment Use open source projects - No proprietary codeUse open source projects - No proprietary code JAVA and open source projects enable AWIPS II to be platform and OS independentJAVA and open source projects enable AWIPS II to be platform and OS independent ADE enables collaborative developmentADE enables collaborative development OS, Platform independence allows non-Linux based research to be easily integrated into AWIPS IIOS, Platform independence allows non-Linux based research to be easily integrated into AWIPS II

8. 8 6/3/2015 SOA Architecture – Logical Layered View Layers Separated By Simple APIs Client/Presentation Services Platform Layer Mission Services Layer Data Access Layer Metadata Index Data Persistence Store Enterprise Service Bus - Communication Security Services /Demilitarized Zone (DMZ) Spatial Index Hydro Models LAPS FORTRAN/C/C++ Command Line Programs External Programs JMX > DataLayer PostgreSQL HDF5 > BaseDao Hibernate > HDF5DataStore HDF5 API IngestSrv PersistSrv IndexSrv ProductSrv AdapterSrv NotifySrv SubscribeSrv AutoBldSrv PurgeSrv Mbean CAVE StagingSrv UtilitySrv Localization Store

9. 9 Government Activities

10. 10 6/3/2015 SOA Migration Testing Approach Purpose:Purpose: Provide feedback to Raytheon on TO software deliverablesProvide feedback to Raytheon on TO software deliverables Improve software quality in support of OT&E and DeploymentImprove software quality in support of OT&E and Deployment Layered ApproachLayered Approach IV&V (Independent Verification & Validation)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)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)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. 11 6/3/2015 AWIPS II Testing Status IV&VIV&V Continue to evaluate TO deliveriesContinue to evaluate TO deliveries Focusing on operational performance metricsFocusing on operational performance metrics UFEUFE Conducted Forecaster Initial TestingConducted Forecaster Initial Testing –Evaluated software along side AWIPS –Assisted in developing operational scenarios Continue to evaluate TO deliveriesContinue to evaluate TO deliveries Working side-by-side plan for TO11 testingWorking side-by-side plan for TO11 testing OT&EOT&E Working OT&E planWorking OT&E plan –Signature Coordination, May 2009 Expected to begin around November 30Expected to begin around November 30

12. 12 6/3/2015 SOA Migration Training Approach Purpose:Purpose: Ensure that developers able to utilize migrated softwareEnsure that developers able to utilize migrated software Ensure that end-users able to configure, monitor, and administer systemEnsure that end-users able to configure, monitor, and administer system Approach:Approach: Development Organizations (GSD, MDL, OHD, SEC) planning and executing trainingDevelopment Organizations (GSD, MDL, OHD, SEC) planning and executing training NWSTD involved in planning and executing operational trainingNWSTD involved in planning and executing operational training –Focus Areas: Local Application DeveloperLocal Application Developer Application Focal PointApplication Focal Point System AdministrationSystem Administration http://www.nws.noaa.gov/ost/SEC/AE/Training.htm

13. 13 6/3/2015 SOA Migration Training Status Operational TrainingOperational Training Requirements IdentifiedRequirements Identified MechanismMechanism –Training for Trainers via Technical Interchange Meetings Initial focus on preparing OT&E sitesInitial focus on preparing OT&E sites Development TrainingDevelopment Training CompletedCompleted

14. 14 6/3/2015 SOA Migration Site Migration Approach Purpose:Purpose: Provide structured method to ensure local sites’ migrationProvide structured method to ensure local sites’ migration –Includes: Local Application MigrationLocal Application Migration Site MigrationSite Migration »Application Configuration »Product Format Template Configuration Approach:Approach: Team (regions, HQ) plan/coordinateTeam (regions, HQ) plan/coordinate Regions/Offices executeRegions/Offices execute http://www.nws.noaa.gov/ost/SEC/AE/Site_Migration.htm

15. 15 6/3/2015 AWIPS-II Site Migration Status Local ApplicationLocal Application NCLADTNCLADT –Analyzed capabilities supporting local application migration in TO8 & TO9 –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 TO10 capabilities Site MigrationSite Migration Identifying configuration/customization files within existing systemIdentifying configuration/customization files within existing system Identifying any changes resulting from SOA Migration activitiesIdentifying any changes resulting from SOA Migration activities Investigating obtaining Raytheon assistance in this effortInvestigating obtaining Raytheon assistance in this effort

16. 16 6/3/2015 AWIPS-II Governance Approach What is it?What is it? Governance model controls the development, test, integration, configuration management, deployment and support of the new system -- both hardware and softwareGovernance model controls the development, test, integration, configuration management, deployment and support of the new system -- both hardware and software Why?Why? SOA offers new levels of flexibility and extensibilitySOA offers new levels of flexibility and extensibility New rules needed to exploit system capabilities, define limitsNew rules needed to exploit system capabilities, define limits Tension between unlimited modifications and ability to support the baseline systemTension between unlimited modifications and ability to support the baseline system http://www.nws.noaa.gov/ost/SEC/AE/Governance.htm

17. 17 6/3/2015 AWIPS-II Governance Status Governance Sub-TeamsGovernance Sub-Teams Release teamRelease team –Working to document release paradigm –Concept includes Monthly DR releaseMonthly DR release Quarterly “major” releaseQuarterly “major” release Local Application teamLocal Application team Began by reviewing existing policyBegan by reviewing existing policy Restart in February, 2009Restart in February, 2009 –Identify changes to policy and AIFM

18. 18 Getting Ready

19. 19 6/3/2015 What can you do? Focus on SOA MigrationFocus on SOA Migration Be PreparedBe Prepared –TO10 Local application migration, including SmartToolsLocal application migration, including SmartTools –TO11 “Slices” User Functional EvaluationUser Functional Evaluation Side-by-side TestingSide-by-side Testing –OT&E Stay InformedStay Informed –Weekly Topic Reports –Website Updates http://www.nws.noaa.gov/ost/SEC/AEhttp://www.nws.noaa.gov/ost/SEC/AE –Upcoming NWS Focus Articles