CHPS Status and Plans Jon Roe, Chris Dietz, Joe Gofus OHD/HL/HSEB Semi-Annual RFC HIC Meeting 29 July 2008

CHPS Status and Plans2 Topics  Terminology  Approach & strategy  Status/Recent activities  Schedule  Hardware  Useful resources  HIC to do list

29 July Terminology FEWS FEWS features have potential application to the entire FEWS user community (generic time- series storage, displays, workflows, etc.) Preferred Usage “FEWS for CHPS” “CHPS and FEWS” “CHPS or FEWS” Avoid Ambiguous Usage “CHPS/FEWS” “CHPS-FEWS” FEWS is a suite of configurable modules which can store, manipulate, and display time series data using your own and community applications. CHPS is a uniquely configured realization of FEWS, using RFC-specific data and applications. Other FEWS-based systems (e.g., NFFS) are different realizations of FEWS. Community applications shared with other FEWS users Applications, configurations, data, unique to CHPS

29 July 2008CHPS Status and Plans4 General Approach  CAT RFCs bear brunt of the pain for all! CAT RFCs go through migration one year ahead of other RFCs to work out wrinkles CAT RFCs go through migration one year ahead of other RFCs to work out wrinkles CAT RFCs act as mentors for other RFCs during the main CHPS migration CAT RFCs act as mentors for other RFCs during the main CHPS migration

29 July 2008CHPS Status and Plans5 Implementation Strategy  Clear planning and execution Gap analysis for essential operations Gap analysis for essential operations Use of existing calibrated parameter sets is essentialUse of existing calibrated parameter sets is essential Pre-processing and post-processing utilities Pre-processing and post-processing utilities AWIPS II integration AWIPS II integration Staff training Staff training Technical support Technical support Many others… Many others… 5

29 July 2008CHPS Status and Plans6 Implementation Strategy  Port models that require calibration e.g., LAG/K, RES-J, SNOW-17, SSARRESV, UNIT-HG, RES-SNGL, SAC-SMA e.g., LAG/K, RES-J, SNOW-17, SSARRESV, UNIT-HG, RES-SNGL, SAC-SMA  Create adapters for several new models e.g., HEC-RAS, HEC-ResSim e.g., HEC-RAS, HEC-ResSim  Rely on existing FEWS data and display utilities with identified enhancements e.g., CHANGE-T, SET-TS, MERG-TS, LOOKUP3, ADJUST-Q, PLOT-TS e.g., CHANGE-T, SET-TS, MERG-TS, LOOKUP3, ADJUST-Q, PLOT-TS  Provide for forecaster run-time modifications  Provide for existing level of ensemble operations, products, and services Port ESP, ESPADP, ENS_PRE, ENS_POST, to use FEWS capabilities Port ESP, ESPADP, ENS_PRE, ENS_POST, to use FEWS capabilities Leverage FEWS existing ensemble capabilities Leverage FEWS existing ensemble capabilities Future: XEFS Future: XEFS 6

29 July 2008CHPS Status and Plans7 Status/Recent Activities  Decision to implement CHPS using FEWS made Jan. 17  Instituted Thursday CAT calls on Feb. 7  First implementation planning sessions with Deltares on Feb. 21 & week of Apr. 14 in Silver Spring  Clarified CHPS-AWIPS II boundaries at AWIPS Task Order #10 Technical Interchange Meeting Apr. 29 – 30 at NWRFC

29 July 2008CHPS Status and Plans8 Status/Recent Activities  CAT strategy session May 1 – 2 at NWRFC  NERFC replaced NCRFC in front runner RFCs following John Halquist move in June; Rob Shedd added to CAT  CHPS Implementation Workshop #01 held in Silver Spring week of June 16  Latest status briefed to DOHs along with detailed demo on Jul. 15  Latest status briefed to HICs today

29 July 2008CHPS Status and Plans9 Implementation Phasing  Two tiers of deployment CAT RFCs (AB, CN, NE, NW) CAT RFCs (AB, CN, NE, NW) Initial hardware delivery in October 2008Initial hardware delivery in October 2008 Initial migration software and training in January 2009Initial migration software and training in January 2009 Operational hardware delivery summer 2009Operational hardware delivery summer 2009 Parallel operations by October 2009Parallel operations by October 2009 Remaining 9 RFCs Remaining 9 RFCs Initial hardware delivery in October 2009Initial hardware delivery in October 2009 Migration/Systems training fall 2009Migration/Systems training fall 2009 Migration begins January 2010Migration begins January 2010 Parallel operations by October 2010Parallel operations by October 2010  RFCs not required to drop NWSRFS until “fully ready” 9

29 July 2008CHPS Status and Plans10 Project Timeline

29 July 2008CHPS Status and Plans11 Key Milestone Types  Preparation and progress workshops ~ 3 per year starting June 2008 for CAT RFCs ~ 3 per year starting June 2008 for CAT RFCs ~ 3 per year starting December 2009 for 9 other RFCs ~ 3 per year starting December 2009 for 9 other RFCs Spring 2009, 2010, 2011 for all RFCs Spring 2009, 2010, 2011 for all RFCs  Software releases ~ every 3 months during migration ~ every 3 months during migration  Acceptance testing Software: following major software deliveries Software: following major software deliveries System: following the two major migrations System: following the two major migrations  Configuration training Just prior to the two migration periods Just prior to the two migration periods  System management training During & toward end of the two migration periods During & toward end of the two migration periods  User training End of each migration period End of each migration period  Details being finalized for publication

29 July 2008CHPS Status and Plans12 FEWS Hardware Infrastructure Duty SystemStandby System

29 July 2008CHPS Status and Plans13 Useful Resources  Deltares wiki page for NWS FEWS users: %2Fdisplay%2FFEWSUSA %2Fdisplay%2FFEWSUSA %2Fdisplay%2FFEWSUSA %2Fdisplay%2FFEWSUSA Userid nws; Password nws123 Userid nws; Password nws123 (Or go to click on “Log In”, enter userid and password, then select DELFT-FEWS USA. This also takes you to the CHPS area.) (Or go to click on “Log In”, enter userid and password, then select DELFT-FEWS USA. This also takes you to the CHPS area.) (For wiki help, visit (For wiki help, visit  Harold and Chris will answer your questions Harold and Chris will answer your questions

29 July 2008CHPS Status and Plans14 HIC To Do List  Start thinking about upcoming milestones out to 2011  CHPS Action Item No : “Need HIC management commitment to plan leave around upcoming CHPS technical workshops and training sessions” “Need HIC management commitment to plan leave around upcoming CHPS technical workshops and training sessions” “Think of office position succession as the CHPS project evolves from now to 2011” “Think of office position succession as the CHPS project evolves from now to 2011”  Start thinking about how to consolidate and re-use local applications in the CHPS era  Ask questions about CHPS or FEWS -  Go to wiki page (slide 12) and learn

29 July 2008CHPS Status and Plans15 Discussion?