1 / 15

CHPS-AWIPS II Integration

CHPS-AWIPS II Integration. Jon Roe, Chris Dietz, Joe Gofus OHD/HL/HSEB Semi-Annual RFC HIC Meeting 29 July 2008. Topics. Situation Technical integration Project integration Schedule overlap Local applications CHPS support & maintenance. Situation.

ketan
Download Presentation

CHPS-AWIPS II Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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 CHPS-AWIPS II Integration

  4. 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 • Visualization roles divided between CAVE and CHPS • Three phase path to integration proposed • Must consider RFC Archive and RFC Service Back-up wrt CHPS realizing complications CHPS-AWIPS II Integration

  5. CHPS: AWIPS II FEWS Interface StudyStudy 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. 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. AWIPS II FEWS Interface Concept DiagramLeverages the SOA Interface Patterns of AWIPS II FEWS Modified FEWS Adapter AWIPS II FEWS Forecast Database IHFS META HDF5 Archive Hydro Plug In Subscription Widget FEWS Visualization XML Request For Data (subscription) Extensions for Phase 2 FEWS Interface AWIPS Plug In CAVE Forecast System Option For Phase 3 interface XML Request For Data (subscription) AWIPS-II Data Files FEWS Requests Forecast Output Files Forecast Output Files AWIPS II File Ingest End-point XML AWIPS-II Response Doc FEWS Data Files FEWS End-point Enterprise Service Bus (File, HTTP, JMS…) AWIPS II - FEWS SOA Interface Concept

  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. AWIPS II FEWS Pilot Interface DiagramPhase I just replaces AWIPS I with AWIPS II FEWS AWIPS II FEWS Forecast Database IHFS CAVE Archive Existing MPEfieldgen FEWS Visualization Forecast System FEWS Adapter cron Data Files FEWS End-point AWIPS-I Data Files Data Files AWIPS-I Data Files Shared File System Directory AWIPS I - FEWS Pilot Interface can be reused

  10. 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 CHPS-AWIPS II Integration

  11. Schedule Overlap • AWIPS II Migration and CHPS Development & Deployment schedules overlap 2008 to 2011 • Recent AWIPS II Migration schedule changes have lessened overlap CHPS-AWIPS II Integration

  12. 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 • 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-AWIPS II Integration

  13. CHPS Support & Maintenance • Deltares to deliver Support & Maintenance Plan as part of development contract tasks • Three phases envisioned (next slide) • Patch/upgrade notification & distribution for phase 1 • Patch/upgrade/release notification & distribution 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 CHPS-AWIPS II Integration

  14. CHPS Support & Maintenance • CAT RFC Migration phase • HSD/OHD & RFC staff perform primary installation/support tasks • 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) • 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) CHPS-AWIPS II Integration

  15. Discussion? CHPS-AWIPS II Integration

More Related