1. CHPS-AWIPS II Integration Jon Roe, Chris Dietz, Joe Gofus OHD/HL/HSEB Semi-Annual RFC HIC Meeting 29 July 2008

2. CHPS-AWIPS II Integration2 Topics  Situation  Technical integration  Project integration  Schedule overlap  Local applications  CHPS support & maintenance

3. 29 July 2008CHPS-AWIPS II Integration3 Situation  CHPS design & development began in earnest in 2005 following earlier proofs-of-concept  AWIPS decided to exercise Continuous Technology Refresh (CTR) contract option in 2006 leading to AWIPS II Migration  Concern on both sides for colliding paths  Collaborative approach reached in meetings, Sep. 2006  CHPS Pilot created and proven during 2007  Details of CHPS-AWIPS II boundaries determined during fall 2007 Raytheon task and spring 2008 AWIPS Task Order 10 Technical Interchange Meeting

4. 29 July 2008CHPS-AWIPS II Integration4 Technical Integration  OHD enlisted Raytheon to study CHPS-AWIPS II integration possibilities, fall 2007  Raytheon consulted with Delft  Task report delivered to OHD November 2007  Outcome: No serious compatibility problems No serious compatibility problems Visualization roles divided between CAVE and CHPS Visualization roles divided between CAVE and CHPS Three phase path to integration proposed Three phase path to integration proposed  Must consider RFC Archive and RFC Service Back-up wrt CHPS realizing complications

5. Page 5 CHPS: AWIPS II FEWS Interface Study Study Findings / recommendations  Integration is relatively low risk and cost – Interface can use existing interface mechanisms built into the AWIPS II architecture and FEWS – Pilot work can be reused with AWIPS II  Phased approach will effectively support CHPS Roadmap  Common GUI in CAVE is not desirable – Nature and separation of work Interface Will Be Low Cost and Low Risk

6. Page 6 AWIPS II - FEWS Interface End State  Enterprise Service Bus with SOA services loosely couple the systems together  Data flow to FEWS will be automatic by subscription or ad hoc as needed  AWIPS II visualization will continue as ports of AWIPS I to view forecast results and IHFS+ data  FEWS visualizations will be used at the RFC during the forecast cycle  Forecast and state data from FEWS will be ingested and archived back into AWIPS II  Can allow NWSRFS and FEWS to be deployed in parallel

7. Page 7 AWIPS II FEWS Interface Concept Diagram Leverages the SOA Interface Patterns of AWIPS II AWIPS II - FEWS SOA Interface Concept FEWS CAVE Enterprise Service Bus (File, HTTP, JMS…) HDF5METAIHFS FEWS Forecast Database Forecast System XML Request For Data (subscription) XML AWIPS-II Response Doc AWIPS-II Data Files Forecast Output Files Forecast Output Files AWIPS II File Ingest End-point Hydro Plug In FEWS End-point AWIPS II AWIPS Plug In Archive FEWS Requests FEWS Visualization Subscription Widget XML Request For Data (subscription) Modified FEWS Adapter Option For Phase 3 interface Extensions for Phase 2 FEWS Interface FEWS Data Files

8. Page 8 Phase I requires no change  AWIPS II substitutes for AWIPS I  The FEWS adapter developed for AWIPS I will continue to run unchanged off a crontab – Extracts data out of the IHFS – Formats the data into FEWS interface compatible XML time series – Text file configuration – (Note from OHD: adapter replaced by modified ofsde)  FEWS will require no changes  Communication through shared file system

9. Page 9 AWIPS II FEWS Pilot Interface Diagram Phase I just replaces AWIPS I with AWIPS II AWIPS I - FEWS Pilot Interface can be reused FEWS IHFS FEWS Forecast Database Forecast System Data Files AWIPS-I Data Files FEWS End-point AWIPS II Archive FEWS Visualization FEWS Adapter Existing MPEfieldgen cron Shared File System Directory CAVE Data Files AWIPS-I Data Files

10. 29 July 2008CHPS-AWIPS II Integration10 Project Integration  By July 2007 HIC meeting AWIPS included CHPS as one of four major components of AWIPS II Extended  OHD working closely with Steve Schotz, AWIPS II Extended project manager  CHPS project documentation to fold into AWIPS II Extended OSIP umbrella

11. 29 July 2008CHPS-AWIPS II Integration11 Schedule Overlap  AWIPS II Migration and CHPS Development & Deployment schedules overlap 2008 to 2011  Recent AWIPS II Migration schedule changes have lessened overlap

12. 29 July 2008CHPS-AWIPS II Integration12 Local Applications  Refer to Thursday’s talk on AWIPS II Migration Issues for details  Short story is: AWIPS II arrival should require small effort for RFC local application migration AWIPS II arrival should require small effort for RFC local application migration OHD suggests RFCs verify continued operation of local applications under AWIPS II OHD suggests RFCs verify continued operation of local applications under AWIPS II CHPS migration is the best time to look at consolidation and re-use of local applications CHPS migration is the best time to look at consolidation and re-use of local applications

13. 29 July 2008CHPS-AWIPS II Integration13 CHPS Support & Maintenance  Deltares to deliver Support & Maintenance Plan as part of development contract tasks Three phases envisioned (next slide) Three phases envisioned (next slide) Patch/upgrade notification & distribution for phase 1 Patch/upgrade notification & distribution for phase 1 Patch/upgrade/release notification & distribution for FEWS during operations, phases 2 and 3 Patch/upgrade/release notification & distribution for FEWS during operations, phases 2 and 3 Bug reporting & tracking for FEWS during operations, phases 2 and 3 Bug reporting & tracking for FEWS during operations, phases 2 and 3  Requires considerable planning coordination among AWIPS NCF, HSD, OHD, & Deltares

14. 29 July 2008CHPS-AWIPS II Integration14 CHPS Support & Maintenance  CAT RFC Migration phase HSD/OHD & RFC staff perform primary installation/support tasks HSD/OHD & RFC staff perform primary installation/support tasks Deltares moves to secondary support Deltares moves to secondary support  CAT RFC Operations/Other RFC Migration phase Target support structure in place for CAT RFCs (AWIPS NCF primary, HSD/OHD secondary, Deltares back line) Target support structure in place for CAT RFCs (AWIPS NCF primary, HSD/OHD secondary, Deltares back line) OHD/HSD & RFC staff perform primary installation/support tasks for other 9 RFCs OHD/HSD & RFC staff perform primary installation/support tasks for other 9 RFCs  All RFCs Operations phase Target support structure in place for all RFCs (AWIPS NCF primary, HSD/OHD secondary, Deltares back line) Target support structure in place for all RFCs (AWIPS NCF primary, HSD/OHD secondary, Deltares back line)

15. 29 July 2008CHPS-AWIPS II Integration15 Discussion?