1. AWIPS II Migration Issues Jon Roe OHD/HL/HSEB Semi-Annual RFC HIC Meeting 31 July 2008

2. AWIPS II Migration Issues2 Topics AWIPS II schedule Task Order 10 Local application migration RFC activities now AWIPS Technology Infusion, AWIPS II Extended & beyond

3. 31 July 2008AWIPS II Migration Issues3 AWIPS II Schedule From AWIPS Technology Infusion web site, http://www.nws.noaa.gov/ost/SEC/AE/ http://www.nws.noaa.gov/ost/SEC/AE/ Task Order 10 (“Hydro”) due 2/5/09 Task Order 11 due 7/31/09 OT&E from November 2009 to May 2010 General deployment start NET Sep. 2010 General deployment done NET Feb. 2011

4. 31 July 2008AWIPS II Migration Issues4 Task Order 10: TIM #1 Task Order 10 (“Hydro”) Developer Technical Interchange Meeting (TIM) #1 held at NWRFC 29-30 April 2008 Goals: –Obtain operational view of the NWRFC –Provide AWIPS II information to the RFC and provide for a Q&A for the RFC and other attendees –Achieve understanding of work scope prior to T.O. 10 proposal

5. 31 July 2008AWIPS II Migration Issues5 Task Order 10: TIM # 1 Results Re-engineer “OHD Common” components into CAVE and edex for WFOs and RFCs Proposed CAVE hydrology perspective(s): –HydroView, RiverPro, TimeSeries, RiverMonitor, MPE, & SSHP NWSRFS untouched and to operate exactly as currently Other “RFC-Only” components to be ported or untouched

6. 31 July 2008AWIPS II Migration Issues6 Task Order 10: TIM # 1 Results OHD Common Components –Data ingest & storage covered METAR-to-SHEF Translator was to be eliminated but now being re-considered due to dependencies –IHFS Database structure unchanged Hibernate access layer added for new code Existing psql-based access still supported although introduces risks for DB writes –HydroBase to be re-engineered

7. 31 July 2008AWIPS II Migration Issues7 Task Order 10: TIM # 1 Results OHD Common Components (cont’d) –Scheduled for T.O. 11, not T.O. 10 DamCrest application and database WAN comms (e.g., for RiverPro, SSHP) High-resolution Precipitation Estimator (HPE) High-resolution Precipitation Nowcaster (HPN) Bias transfer application VAR updates to SSHP

8. 31 July 2008AWIPS II Migration Issues8 Task Order 10: TIM # 1 Results RFC-Only Components –NWSRFS core untouched (ofs, ifp, ffg, icp, most of calb, most of ens, & RFS utilities) –espadp untouched –ofsde and fs5files database untouched –Logistical Measures/Forecast Services to be embedded into HydroView CAVE perspective and re- engineered HydroBase –XDAT capabilities included in CAVE –XNAV GUI and interactive capabilities included in CAVE (no access to fs5files) –XSETS untouched but outbound comms provided

9. 31 July 2008AWIPS II Migration Issues9 Task Order 10: TIM # 1 Results RFC-Only Components (cont’d) –Scheduled for T.O. 11, not T.O. 10 Historical Data Browser (HDB), its database, and IDMA to be ported (DB structure unchanged) ens_pre to be ported away from using CPC gridded outlook netCDF input files (to HDF5) Send_RFC outbound data comms RAX data ingest & database (DB structure unchanged, Hibernate & psql access) RAX data access applications (untouched) Verification applications (untouched)

10. 31 July 2008AWIPS II Migration Issues10 Task Order 10: Proposal Proposal received end of May OHD & HSD comments provided June 13 Comments response received July 9 –No difficult issues in response Authorization to proceed given by Government on July 14 with work actually started about July 7 Developer TIM (#2) at OHD, Sep 10 Remote customer TIM (#3), Oct 29 Face-to-face customer TIM (#4), Dec 3 Completion out brief, Feb 5, 2009

11. 31 July 2008AWIPS II Migration Issues11 Local Application Migration: Roles & Responsibilities SEC  AWIPS II Project Responsibility Regions/NCEP Director  Local Application Migration Responsibility National Core Local Application Development Team (NCLADT) –Writing, testing, and maintaining local application infrastructure code with goal of reducing programming errors and code duplication –Who are NCLADT? See http://www.nws.noaa.gov/ost/SEC/AE/Weekly_Topics/06-06-08.pdfhttp://www.nws.noaa.gov/ost/SEC/AE/Weekly_Topics/06-06-08.pdf MICs/HICs and National Centers’ Directors –Ensure NCLADT members have time –Work with Regional Focal Points to pair a programmer w/ application –Ensure programmers have time –Certify critical local apps migrated prior to AWIPS II site installation Regional Focal Points –Develop detailed local application migration plan –Provide monthly status report

12. 31 July 2008AWIPS II Migration Issues12 Local Application Migration: NCLADT Activities Installed T.O. 8 software Setup build environment –Compiled edex –Explored edex architecture –Took a tour of the ingest components StagingSrv, IngestSrv, IndexSrv but concentrated on ProductSrv Practiced writing uEngine scripts –Experimented with the different ScriptTasks –Experimented with the javascript uEngine libraries provided by Raytheon –Became familiar with jibx's role and xml in message passing Supported Technical Interchange Meeting –Identified ~25 common functionalities

13. 31 July 2008AWIPS II Migration Issues13 Local Application Migration: Expected T.O. Technical Support T.O. 9 –Python interpreter (jep) added to uEngine –Javascript interpreter (rhino) will remain in the uEngine –Scripts sent to edex can be written in either javascript or python T.O. 10 –No structural change to the IHFS Database psql-based local apps will work as before –Textdb clone utility –SubscriptionManager implemented Triggers, crons for obtaining data T.O. 11 –handleOUP utility –No structural changes to RAX or Historical DBs psql-based local apps will work as before

14. 31 July 2008AWIPS II Migration Issues14 RFC Activities Now Focus on AWIPS II –Download and install T.O. 8 software Contact Regional Representative –Start training – don’t wait until T.O. 10 –Download and install T.O. 9 software when available Local application migration –Start training and learning the new environment –OHD suggests you perform minimal LA migrations now for AWIPS II and concentrate on LA consolidation and reuse as part of CHPS Testing –Support side-by-side and evaluation testing of AWIPS II, particularly for T.O. 10 next winter

15. AWIPS Technology Infusion Scope AWIPS Technology Infusion (FY05 – FY14) –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: AWIPS II – Migration of WFO/RFC AWIPS (FY07-FY09) –Implements a modern Services Oriented Architecture (SOA) infrastructure –First output of AWIPS Technology Infusion and provides the foundation for all subsequent improvements Phase II: AWIPS II Extended - Creation of a seamless weather enterprise spanning NWS operations (FY09-FY10) –Migration of N-AWIPS into the AWIPS II SOA –Delivery of thin client Support for the Weather Service Offices, Center Weather Support Units, Incident Meteorologists, e.g., Fire Weather –Integration of “orphan” systems (e.g., Weather Event Simulator) –CHPS Integration into AWIPS II SOA Phase III: AWIPS II Extended Enterprise Enhancements (FY09 – FY14) –Data delivery enhancements “Smart push-smart pull” data access –Integrated visual collaboration –Information generation enhancements –Visualization enhancements

16. 16 AWIPS II Extended Project Descriptions ProjectDescriptionKey BenefitsStake Holders N-AWIPS Migration Migrate N-AWIPS capabilities to AWIPS II architecture Enable more effective collaboration and seamless products between NCs and other NWS operational units Enable sharing of common capabilities, e.g., meteorological calculations toolkits NCEP Centers, RFCs, PR, AR, Unidata Thin ClientDevelop enterprise solution for remote access to AWIPS II capabilities Common solution to support Incident Meteorologist, CWSUs, WSOs, etc. AWIPS II remote access requirements Allow remote users access to latest AWIPS II capabilities NWS enterprise, Trusted partners WES Integration Develop enterprise solution to address AWIPS II training requirements Baseline solution to support NWS training requirements Allow training users access to latest AWIPS II capabilities NWS enterprise CHPS Integration Integrate CHPS into AWIPS II architecture CHPS integration will significantly reduce the time to transition new innovative analyses and forecast techniques (e.g., water quality models) from the drawing board to operational deployment. RFCs, Trusted partners

17. 17 AWIPS II Extended Project Descriptions - Continued ProjectDescriptionKey BenefitsStake Holders Data Delivery Develop operationally robust infrastructure to support “intelligent” remote access to datasets “Intelligent” includes data discovery and capabilities to sub-set the database by parameter, space, time, ensemble member, etc. Address significant growth in data volumes from higher resolution models and ensembles and from new data sources such as NPOESS and GOES-R Mitigate impacts of large datasets on SBN NWS enterprise, Trusted external data providers CollaborationDevelop infrastructure to support real-time collaboration, including graphical and chat and other technologies among NWS operational units and trusted partners Enable more effective collaboration among NWS operational units promoting a more coordinated and seamless set of NWS products Enable more effective communication and coordination between NWS and trusted partners, e.g., Emergency Managers NWS enterprise, Trusted partners and customers Information Generation Develop infrastructure to support a common set of information generation services and tools Streamline generation of products to support emerging industry standard formats, e.g., CAP, GIS, etc. Reduce development and maintenance costs associated with product generation, standardize templates for all NWS text products NWS enterprise, trusted partners and customers VisualizationBuild a common AWIPS visualization environment that will be used by all applications Enable more effective incorporation of advanced visualization techniques, e.g., 3-D visualization NWS enterprise

18. 31 July 2008AWIPS II Migration Issues18 Discussion?