1 / 42

SPSRB Project Plan on Polar-Geo Blended Hydrometeorological Products

SPSRB Project Plan on Polar-Geo Blended Hydrometeorological Products. Presenter: Limin Zhao (OSPO) Project Lead: Limin Zhao (OSPO) Project Backup Lead: Ralph Ferraro (STAR) August 8-9, 2012. Outline. Integrated Product Team (IPT) Requirements Capabilities Assessment

allene
Download Presentation

SPSRB Project Plan on Polar-Geo Blended Hydrometeorological Products

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. SPSRB Project Plan on Polar-Geo Blended Hydrometeorological Products Presenter: Limin Zhao (OSPO) Project Lead: Limin Zhao (OSPO)Project Backup Lead: Ralph Ferraro (STAR) August 8-9, 2012 V14.1 Jun 2009

  2. Outline Integrated Product Team (IPT) Requirements Capabilities Assessment IT System Architecture Plan of Operations Project Milestones Funding Spending plan and tasks V14.1 Jun 2009

  3. Integrated Product Team (IPT) IPT Lead: Limin Zhao IPT Backup Lead: Ralph Ferraro (STAR) and Stan Kidder (CIRA) NESDIS team: STAR: John Forsythe (CIRA), Andrew Jones (CIRA) and Ingrid Guch OSPO: John Paquette, Sheldon Kusselson, Zhaohui Cheng, Joseph Mani, Carl Bauer OSD: Tom Schott Data Center/NCDC: Phil Jones Contractor Support: Jiang Zhao (SGT), Clay Davenport (SGT), Ed Ladd (SSAI) User team Lead: Kevin Schrab/James Heil (NWS), Andy Edman (NWS/WFO) Others: Sheldon Kusselson (NESDIS/SAB), NOAA/HMT program Oversight Panel (OP) lead: PREPOP V14.1 Jun 2009

  4. Requirement Requirements 1004-0007: M-T data for NESDIS operational applications, which requires the M-T TPW and RR be included in the blended products. 0708-0023, POES-GOES Blended hydrometeorological products, which requires the operational blended total precipitable water (TPW) and rain rate (RR) products from multi-satellites, including POES, Metop, DMSP, GOES and GPS. …, etc Others: (1) OSIP 06-084; (2) NWS AWIPS OB9; (3) user requests from various WFOs (see backup slides); (4) NOAA's Hydrometeorological Testbed (HMT); (5) NOAA's Scientific Data Stewardship (SDS) program; Continuity of Operation. User Community NWS WR, NWS SPC, NWS NHC, NWS HPC, NWS WFOs (AWIPS) NESDIS/SAB NOAA Mission Goals Supported Weather and Water Commerce and Transportation Goal Wide – Satellite Services; Polar satellites acquisitions Mission Priority: Mission Critical/High V14.1 Jun 2009

  5. Capabilities Assessment (before FY12) V14.1 Jun 2009

  6. Capabilities Assessment (FY12 beyond) V14.1 Jun 2009

  7. SHORTFALLS (1/2) Timeliness Using of individual TPW and RR products from various sensors would add more time to the analysis of heavy precipitation events Multiple TPW products from various sensors take a longer time to process and disseminate to users as separated products Accuracy of Product Products from different sensors carry different biases, which makes the products hard to use by forecasters Orbital gap prevents the continuity of the changing levels of moisture Large artifacts exist when simply overlay observations from different sensors with different time and simple sizes The difference of TPW and RR retrievals from different sensors sometimes exceeds the stated accuracy of the retrievals. Define how product development addresses shortfalls Unifies a range of TPW and RR products from different sensors into a common global product and enables the forecaster to use one improved product in lieu of many single sensor products derived from multiple platforms. Proposed blending method mitigates the individual biases of the sensors to produce a more accurate, all-inclusive product. The blended TPW product provides an innovative capability to track moisture plumes by combining TPW information from the multiple sensors, including GPS. Single blended products will also enhance the timeliness in processing and disseminating. V14.1 Jun 2009

  8. SHORTFALLS (2/2) Benefit: The blended TPW product enables the forecaster to use one improved product in lieu of many products derived from multiple platforms. The blended TPW product provides a more complete observation of the movement of moisture in the atmosphere, therefore, innovative capability to track moisture plumes . Blending mitigates the individual biases of the sensors to produce a more accurate, all-inclusive product, therefore, provide better anticipation and forecast of heavy rain and flooding events. The inclusion of land based TPW coverage will provide the forecaster continuity on the changing levels of moisture moving across water to land areas, and allow them to monitor surges of moisture from the ocean areas into the U.S. and help analysts pinpoint the location of heavy precipitation over the CONUS that can be effectively used for flood guidance and forecasting. The blended TPW product would add approved values to forecasters in tracking monsoon surges out of the Pacific Ocean during the summer and fall, return moisture surges from Gulf of Mexico after frontal passages, and moisture plumes out of the tropics during the winter. The TPW anomaly product would help quickly identify areas that are abnormally wet or dry. Impact if not funded: The NWS forecasters will have to continue using a variety of TPW and RR products and combine them in a non-efficient way, therefore, the time latency to issue warnings and advisories to the public will not be improved. The NWS forecasters will continue to use internet to acquire the untimely products from CIRA, and can not combine them with any other AWIPS data sets to enhance the forecasting capability and support real-time operations. NESDIS’ innovation in integration of data from various sensors to provide improved hydrometeorological products to support NOAA’s mission will be delayed. V14.1 Jun 2009

  9. Algorithm Status and Approach (1/2) Current status of algorithms being considered in your project A peer-reviewed paper has been published on the blending technology. Several conference papers were presented on the use of the blended TPW products and its important impacts on weather forecasting. Individual retrievals have been validated and peer-reviewed papers have been published (see references in backup slides) Individual observations are blended in a way to eliminate artifacts. Briefly describe the validation concept The individual retrievals have been validated against radiosondes (see backup slides for references). The blending process adjusts the TPW values so that they have the same frequency distribution as that retrieved from the reference satellite/sensor, currently Metop-A. Thus the blended TPW product has the same accuracy as that retrieved from this reference satellite/sensor, approximately ±3 mm. An independent validation against rawinsondes has not yet been done on the blended TPW products. The blended RR product is under development and evaluation. The blended TPW products are being used in assisting forecasters for heavy rainfall forecasting on a daily basis (Kusselson et al. 2007). Very positive feedback are being received from WFO forecasters on their approved value (see backup slides). V14.1 Jun 2009

  10. Algorithm Status and Approach (2/2) Overview of technical approach of the algorithm and its implementation The goal is to produce nearly global (excluding only the poles) no-gap analyses of total precipitable water (TPW) and rain rate (RR) that will be of use to forecasters. The TPW blending algorithm, which is detailed in Kidder and Jones (2007), adopts the histogram matching concept, and calibrates observations from various satellites/sensors to a reference satellite/sensor to avoid artifacts caused by differences between observing systems. The TPW percentage of normal product is generated by comparing the observations with a satellite-based climatology. The blended RR product is still under development, and the plan is to adopt the best practice from the current exist algorithms. The only ancillary data used is the NASA Water Vapor Project weekly normal provided by Randel et al. (1996). Concept of operations: Acquire data (hourly): AMSU TPW from MSPPS and MIRS SSMIS TPW and RR from FNMOC, SSMIS TPW from MIRS GPS TPW (from ftpgps.fsl.noaa.gov) GOES PW (from satepsanone.nesdis.noaa.gov) ATMS TPW from MIRS (NDE) Form histogram matching correction from last 5 days of AMSU and SSM/I data (Kidder & Jones 2007) Correct and map each orbit of AMSU and SSMIS data onto the 16-km resolution Mercator map grid (one orbit per map file) Composite the last 12 hours of mapped AMSU and SSM/I data onto a single output map. Map the GPS data onto a Mercator map using a Barnes analysis. (The GOES PW data are already mapped.) Fill the holes in the AMSU/SSM/IS composite over the CONUS, AK, HI and Puerto Rico using GPS data (first priority) or GOES PW data to form the final TPW product. Form Percent of Normal product by dividing TPW by the NVAP weekly normal TPW Write the final TPW product and the Percent of Normal product out in McIDAS format and make available on a McIDAS server Convert the McIDAS-formatted products to AWIPS format and deliver to NWS. V14.1 Jun 2009

  11. IT System Architecture Users ESPC DDS Blended TPW, TPW anomaly, RR ESPC Production (IBM AIX) GPS Operational Develop ADDE Test/Backup CLASS Blended TPW, TPW anomaly, RR CIRA Develop QC/VAL/MON GINI ANCF/SBN AWIPS Users SAB users PC GRID Clusters Input Data Includes: AMSU TPW from MSPPS, MHS RR from MSPPS, TPW from MIRS (AMSU, SSMIS and ATMS), SSMIS TPW and RR from FNMOC, GPS-MET TPW, GOES Sounder. V14.1 Jun 2009

  12. IT System Transition Plan for FY08 ADDE Data files served from CIRA SAB users T/O Data files served from the operational system ANCF/SBN GINI AWIPS Users T: Test data sets (static and stream) O: Operational capability V14.1 Jun 2009

  13. Research and Operational System Environments * ESPC target architecture platform is IBM P6 for science production systems ** ESPC target OS is AIX with Redhat Linux partition *** IDL and MATLAB are not supported in ESPC for science algorithm processing, only for post-processing tasks V15.0 November 2009 Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project

  14. Operational Agency System Requirements Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project V15.0 November 2009

  15. The Blended Hydrometeorological Products System Input Data Includes: AMSU/MHS TPW & RR from MSPPS, MIRS; SSMIS TPW & RR from FNMOC; GOES-W & E TPW; GPS TPW; ATMS TPW & RR from NDE; AMSR-2 TPW & RR from ESPC GCOM servers; M-T TPW and RR from ESPC M-T servers. V14.1 Jun 2009

  16. Plan of Operations (1/3) Archive Plan NWS takes responsibility to archive AWIPS products. NESDIS is developing the Data Submission Agreement (DSA) between NESDIS and NCDC to archive the global blended TPW and RR products – the new NCDC archive request has been filled and discussed with Phil Jones at NCDC and CLASS representatives. The request is still waiting for COPB’s final approval. Deliverables to archive The global blended TPW, TPW anomaly and RR products Data documentation and user manual Cost requirements No cost for AWIPS products at NCDC/CLASS Long term archive for global products at CLASS (TBD) Long Term Maintenance Plan STAR CIRA maintain the DPEAS on their PC cluster system, and implement enhancements when applicable. OSPO ESPC Contractor maintenance support for the blended TPW system is estimated to be 0.15 FTE after its fully operational, and is covered by OSPO base funds. Implementation of the updated/enhanced algorithms will need to be funded through future PSDI proposal. V14.1 Jun 2009

  17. Plan of Operations (2/3) Quality Monitoring Plan Quality Control (QC) tools to be developed/used Primarily web-based tool (http://cat.cira.colostate.edu/) Operational product quality monitoring (http://www.osdpd.noaa.gov/bTPW.html; http://www.osdpd.noaa.gov/bRR.html) OPUS GUI interface and AWIPS workstation and job logs Who will use the QC tools CIRA SAB precipitation team OSPO Precipitation PAL and support contractor How the QC tools will be used OSPO Monitoring the job flow and processing status through OPUS GUI interface 24/7 and automated anomaly email notification. Monitoring the products generation, timeliness and distribution status, and also inspecting imagery during normal business hours to detect anomalies and monitor long term stability/accuracy of products http://www.osdpd.noaa.gov/bTPW.html; http://www.osdpd.noaa.gov/bRR.html Monitoring GINI data/product transmission logs for quality data transmissions, and FTP logs for successful transfer of AWIPS products from the NESDIS GINI to the NWS NCF ESPC contractor, SAB precipitation team will monitor the displayed products on AWIPS workstation for quality assurance. When product transmissions are not successful or degraded, a coordination call will be immediately placed from the ESPC Help Desk to the NCF in Silver Spring for problem resolution CIRA Monitoring and validating the products quality http://cat.cira.colostate.edu/ V14.1 Jun 2009

  18. Plan of Operations (3/3) Documentation/Metadata Plan CIRA and OSPO will work together to provide Interface Control Document, Program Description Document and User Manual, include ATBD. OSPO will provide System Maintenance Manual and Operational Manual OSPO will prepare other docs per the NWS/NESDIS AWIPS Project Requirements Document User Involvement Plan NWS and SAB users have been using the blended products for years, and OSPO are keeping its outreach function to users for training and assessing any new requirements. Feedback are communicated back to CIRA. User leads are actively involved through IPT, and invited to participate design reviews, verify the user requirements and products validation results to ensure the products meet the specs. CIRA and OSPO will continue present the enhancements to user community and gather feedbacks for further improvement on the blended TPW and RR products. V14.1 Jun 2009

  19. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Blended TPW and TPW anomaly products from POES/Metop-A AMSU, DMSP SSM/I and GPS TPW products Mar 08 (Mar 08): Development Phase Begins Mar 08: IPT Branch Lead informed to begin product development Mar 08: Initial Archive Requirements identified Mar 08: Quality Monitoring Concept Defined Mar 08: Static test data file provided to NWS/AWIPS (OB9.x) May 08: Long-term Maintenance Concept Defined Aug 08 (Jun 08)*: Preliminary Design Review July 08 (Jun 08)*: Development processing system defined Nov 08 (Sep 08)*: Critical Design Review Nov 08 (Oct 08)*: Code is prepared for implementation & Software code review held Oct 08: Final Archive requirements identified Oct 08: Operational and backup processing defined Nov 08* (July 08): Pre-operational Phase Begins Nov 08* (Oct 08): Pre-operational product output evaluated & tested July 08: Final/Streaming product delivered to NWS/AWIPS Nov 08: Operational and backup processing capabilities in place Nov 08: Final IT Security Concept Defined Jan 09: Code transitions to operations; all documentation is complete Jan 09: Operational and backup capabilities reach ops status Jan 09: Brief SPSRB Oversight Panel(s) (PREPOP) on product status Jan 09: Brief SPSRB capability is ready to operational Feb 09 (Feb 09): Operational Phase Begins Feb 09: SPSRB declares product operational SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database All AWIPS sites receiving Blended TPW Product Completed Note: The tasks highlighted with red indicate that the deliverables will be provided from the PC-based system when waiting for the migration be completed on IBM Linux. * The schedule is slipped due to the delayed start of migration of DPEAS to IBM. V14.1 Jun 2009

  20. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Enhanced Blended TPW and TPW anomaly products from multi-Sensors (SSMIS, GOES Sounder and MIRS/C1DOE over ocean) * Mar 09 (Mar 09) (Mar 09) (Mar 09) (Oct 08): Development Phase Begins Mar 09: Development processing system defined Oct 09: Test case processed Nov 09 : Design Review Jan 11: Code is prepared for implementation & Software code review held Jan 11: Operational and backup processing defined Apr 11 (Apr 11) (Dec 09) (Dec 09) (Aug 09): Pre-operational Phase Begins Apr 11: Operational and backup processing capabilities in place Apr 11: Final IT Security Concept Defined Apr 11: Pre-operational product output evaluated & tested Apr 11: Code transitions to operations; all documentation is complete Apr 11: Operational and backup capabilities reach ops status Jun 11: Brief SPSRB Oversight Panel(s) (PREPOP) on product status Aug 11: Brief OSPO capability is ready to operational Aug 11 (July 11) (May 10) (Apr 10) (Dec 09): Operational Phase Begins Aug 11: SPSRB manager and secretaries notified update/upgrade went into operation SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database Completed * AMSR-E and TMI are removed to allow resource be put on the development of a better blended RR product. Due to the limited spatial coverage of TMI , and also the duplicated launch time between AMSR-E and N16, there are not much extra information/benefit provided to the current blended TPW products by including ASMR-E and TMI. V14.1 Jun 2009

  21. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Enhanced Blended TPW and TPW anomaly products from multi-Sensors (MIRS/C1DOE over land) Mar 10 (Mar 10) (Mar 10) (Mar 10): Development Phase Begins Mar 10: Development processing system defined Oct 10: Test case processed Dec 10: Code is prepared for implementation & Software code review held Dec 10: Operational and backup processing defined Apr 11 (Apr 11) (Jan 11) (Jan 11): Pre-operational Phase Begins Apr 11: Operational and backup processing capabilities in place Apr 11: Final IT Security Concept Defined May 11: Pre-operational product output evaluated & tested Jun 11: Code transitions to operations; all documentation is complete Jun 11: Operational and backup capabilities reach ops status Jun 11: Update SPSRB Oversight Panel(s) on product status Jul 11: Brief OSPO capability is ready to operational Aug 11 (Jul 11) (Apr 11) (Apr 11): Operational Phase Begins Aug 11: SPSRB manager and secretaries notified update/upgrade went into operation SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database Completed V14.1 Jun 2009 C1DOE: the retrieval system developed at CIRA

  22. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Blended Rain Rate Product from POES/Metop and DMSP Nov 08 (Nov 08) (Nov 08) (Nov 08) (Oct 08): Development Phase Begins Nov 08: Development processing system defined Jul 09: Test case processed July 11: Design Review (delta CDR for RR only) Aug 11: Code is prepared for implementation & Software code review held Aug 11: Final Archive requirements identified Aug 11 (Apr 11) (Jan 10) (Jan 10) (Aug 09): Pre-operational Phase Begins Aug 11: Operational and backup processing capabilities in place Aug 11: Final IT Security Concept Defined Aug 11: Pre-operational product output evaluated & tested Dec 11 (Sep 11): Code transitions to operations; all documentation is complete Dec 11 (Sep11): Operational and backup capabilities reach ops status May 12 (Feb 12) (Oct 11): Brief SPSRB Oversight Panel(s) (PREPOP) on product status Jun 12 (Mar 12) (Nov 11): Brief SPSRB capability is ready to operational Jul 12 (Mar 12) (Nov 11) (Sep 11) (May 10) (Apr 10) (Dec 09): Operational Phase Begins Jul 12: SPSRB declares product operational SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database Completed V14.1 Jun 2009

  23. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: High Resolution Blended TPW product over CONUS from multi-Sensors Nov 08 (Nov 08): Development Phase Begins Nov 08: Development processing system defined Jul 09: Test case processed July 11: Design Review (delta CDR) Aug 11: Code is prepared for implementation & Software code review held Aug 11: Final Archive requirements identified Aug 11 (Aug 11): Pre-operational Phase Begins Aug 11: Operational and backup processing capabilities in place Aug 11: Final IT Security Concept Defined Aug 11: Pre-operational product output evaluated & tested Sep 11: Code transitions to operations; all documentation is complete Dec 11: Operational and backup capabilities reach ops status Jan 13: Brief SPSRB Oversight Panel(s) (PREPOP) on product status Feb 13: Brief SPSRB capability is ready to operational Mar 13 (Nov 11): Operational Phase Begins Mar 13: SPSRB declares product operational SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database V14.1 Jun 2009

  24. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Blended Hydro Products with Metop-B Sep 12 (Apr 12): Development Phase Begins Sep 12: IPT Lead informed to begin product development Sep 12: Metop-B launch Sep 13: Development processing system defined Jan 13: Test case processed Jan 13: Code is prepared for implementation Jan 13: Software Code Review following SPSRB standards Jan 13: Operational and backup processing defined Jan 13 (Aug 12): Pre-operational Phase Begins Jan 13: Operational and backup processing capabilities in place Jan 13: Pre-operational product output evaluated & tested Feb 13: Code transitions to operations; all documentation is complete Feb 13: Operational and backup capabilities reach ops status Mar 13: MSPPS and MIRS Metop-B products operational available Mar 13*: Update SPSRB Oversight Panel(s) on product status Mar 13*: Brief OSPO capability is ready to operational Mar 13 (Oct 12): Operational Phase Begins * Mar 13: SPSRB manager and secretaries and OSD Satellite Product Manager notified update/upgrade went into operations. SPSRB Secretaries/manager update the SPSRB product metrics web pages Mar 13: OSD updates Satellite Products database *Note: The operational date of the blended hydro products relies on when MSPPS and MIRS Metop-B will be operational. V14.1 Jun 2009

  25. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Enhanced Blended TPW, TPW anomaly and Rain Rate products with NPP/ATMS Mar 11 (Mar 11) (Mar 11) (Mar 11): Development Phase Begins Mar 11: Development processing system defined Oct 11: Test case processed Oct 11: NPP launch Nov 11: Final archive requirements identified May 12: Code is prepared for implementation & Software code review held June 12: Operational and backup processing defined Jul 12 (July 12) (July 12) (Jan 12): Pre-operational Phase Begins Jul 12: Operational and backup processing capabilities in place Jul 12: Final IT Security Concept Defined Sep 12: Pre-operational product output evaluated & tested Sep 12: Code transitions to operations; all documentation is complete Sep 12: Operational and backup capabilities reach ops status Oct 12*: MIRS products declared operational Dec 12: Update SPSRB Oversight Panel(s) on product status Jan 13: Brief OSPO capability is ready to operational Feb 13 (Feb 13) (Dec 12) (May 12): Operational Phase Begins Feb 13: SPSRB manager and secretaries notified update/upgrade went into operation SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database *Note: the operational date depends on when the operational MIRS ATMS products will be available. V14.1 Jun 2009

  26. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Enhanced Blended TPW, TPW anomaly and Rain Rate products with GCOM-W1 AMSR-2 Mar 13: Development Phase Begins Mar 13: Development processing system defined Aug 13: Design Review (Algo Review) Oct 13: Test case processed Nov 13: Final archive requirements identified Jan 14: Code is prepared for implementation & Software code review held Jan 14: Operational and backup processing defined Jan 14: Pre-operational Phase Begins Jan 14: Operational and backup processing capabilities in place Jan 14: Final IT Security Concept Defined Feb 14: Pre-operational product output evaluated & tested Feb 14: Code transitions to operations; all documentation is complete Feb 14: Operational and backup capabilities reach ops status Mar 14: Update SPSRB Oversight Panel(s) on product status Apr 14: Brief OSPO capability is ready to operational Apr 14: Operational Phase Begins Apr 14: SPSRB manager and secretaries notified update/upgrade went into operation SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database V14.1 Jun 2009

  27. SPSRB Milestones and Key Tasks Product Delivery/Tracking Name: Enhanced Blended TPW, TPW anomaly and Rain Rate products with Megha-Tropiques Mar 14: Development Phase Begins Mar 14: Development processing system defined Aug 14: Design Review (Algo Review) Oct 14: Test case processed Nov 14: Final archive requirements identified Feb 15: Code is prepared for implementation & Software code review held Feb 15: Operational and backup processing defined Feb 15: Pre-operational Phase Begins Feb 15: Operational and backup processing capabilities in place Feb 15: Final IT Security Concept Defined Mar 15: Pre-operational product output evaluated & tested Mar 15: Code transitions to operations; all documentation is complete Mar 15: Operational and backup capabilities reach ops status Apr 15: Update SPSRB Oversight Panel(s) on product status May 15 Brief OSPO capability is ready to operational May 15: Operational Phase Begins May 15: SPSRB manager and secretaries notified update/upgrade went into operation SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database V14.1 Jun 2009

  28. FY09 Product Deliverable Details Completed N=New E=Enhanced R=Replacement T=Tailored O=Other V14.1 Jun 2009

  29. FY11 Product Deliverable Details Completed N=New E=Enhanced R=Replacement T=Tailored O=Other V14.1 Jun 2009

  30. Product Deliverable Details V14.1 Jun 2009 N=New E=Enhanced R=Replacement T=Tailored O=Other

  31. Product Deliverable Details N=New E=Enhanced R=Replacement T=Tailored O=Other V14.1 Jun 2009

  32. Product Deliverable Details N=New E=Enhanced R=Replacement T=Tailored O=Other V14.1 Jun 2009

  33. Product Deliverable Details N=New E=Enhanced R=Replacement T=Tailored O=Other V14.1 Jun 2009

  34. Polar-Geo Blended Hydrometeorological Products Funding (K) V14.1 Jun 2009

  35. Polar-Geo Blended Hydrometeorological Products Funding (K) V14.1 Jun 2009

  36. FY08 Purchases and Tasks (70K P-PSDI): STAR Grant for .5 FTE at CIRA from Mar 08 to Feb 09 Integrate GPS TPW over CONUS into the ESPC version of DPEAS AMSU/SSMI Blended TPW Update the blended TPW to replace N17 with Metop-A Team with OSPO to deliver PDR and CDR for the blended TPW Prepare the required operational documents (ATBD, SSD, ICD and UM) for DPEAS Provide training to OSPO maintenance contractors Work on blending GOES Sounder PW with above products Begin developing blended RR product (80K P-PSDI): OSPO Software Contractor for .75 FTE from Mar 08 to Feb 09 Update the ESPC version with the GPS and GOES TPW capability Provide needed validation to the blended TPW system migrated onto IBM Linux Team with CIRA to deliver PDR and CDR for the blended TPW Develop the implementation plan and follow the best practice at ESPC to transition the blended TPW (SSMI, AMSU, GPS and GOES) product into operations Update the McIDAS/AWIPS format converters to reflect the new changes Generate the blended TPW and TPW anomaly products for AWIPS to meet the OB9 timeline Static file delivery in March 2008 Final/Streaming product delivery in July 2008 Implementation of product into AWIPS in January 2009 (OB9) Develop the monitoring tool for product generation, dissemination and quality monitoring. Prepare the operational and maintenance manuals Update the ICD, SSD and UM delivered from STAR to reflect the changes in the operational version V14.1 Jun 2009

  37. FY09 Purchases and Tasks (180K G-PSDI): STAR Grant for 1 FTE at CIRA from Mar 09 to Feb 10 Work on blending GOES and SSMIS TPW with AMSU/SSMI data Work on the effects of topography Work on improving climatological TPW anomaly products Continue on developing blended RR product Team with OSPO to deliver Design Review for the enhanced blended TPW and RR products Deliver the enhanced TPW products for operational implementation Deliver the blended RR product for operational implementation Exploring the capability to include TPW over land from MIRS and C1DOE (Prior Year G-PSDI): OSPO Software Contractor for .65 FTE from Mar 09 to Feb 10 Update the ESPC version of DPEAS with the GOES and SSMIS TPW capability Team with CIRA to deliver Design Review for the enhanced blended TPW and RR products Transition of the enhanced blended TPW and TPW anomaly products into operations Transition the blended RR product into operations (25K OSPO Base): S/H O&M cost Shared cost for software licenses, disk storage and CPU load needed for the operational support to the application under the ESPC production environment, and also hardware maintenance and system administration needs. V14.1 Jun 2009

  38. FY10 Purchases and Tasks (135K G-PSDI): STAR Grant for 0.8 FTE at from Mar 10 to Feb 11 Work on adding TPW over land from MIRS Upgrade the blending algorithm to deal with the effects of topography Deliver the enhanced blended TPW for operational implementation Extend the operational blended TPW products (AMSU. SSMI, SSMIS, GPS-MET and GOES ) to global land with MIRS TPW products A higher resolution blended -TPW products over CONUS from GPS-MET and GOES for severe weather monitoring (1-hour update with 8km spatial resolution) Exploring the capability to add ATMS TPW and RR to the blended products (10K G-PSDI): OSPO Software Contractor for 0.1 FTE from Mar 10 to Feb 11 The project is hold due to OSPO IT freeze. FY10 funding only covers limited non-IT tasks, and the rest of funding and tasks are pushed to FY11 Team with CIRA to deliver Design Review for the enhanced blended TPW and RR products Perform code review Prepare Data Submission Agreement for the blended RR products Prepare Operation Procedures for the blended RR products (15K OSPO Base): S/H O&M cost Shared cost for software licenses, disk storage and CPU load needed for the operational support to the application under the ESPC production environment, and also hardware maintenance and system administration needs. V14.1 Jun 2009

  39. FY11 Purchases and Tasks (57K OSD Gnd Sys NPP Products): 0.3 FTE at CIRA from Mar 11 to Feb 12 Develop the ATMS capability using test data from MIRS (85K G-PSDI): OSPO Software Contractor for 0.65 FTE from Mar 11 to Feb 12 Transition of the enhanced blended TPW and TPW anomaly products into operations Transition of the blended RR product into operations Update the monitoring tools for product generation, dissemination and quality check to include the blended RR product. Transition of the enhanced blended TPW and TPW anomaly products with MIRS TPW over land into operations Transition of the higher resolution blended-TPW products from GPS-MET and GOES over CONUS to operation Update the McIDAS/AWIPS format converter to include the RR and high resolution CONUS TPW products Update the ICD, SSD and UM delivered from CIRA to reflect the changes in the operational version Update the operational OM and SMM to reflect changes V14.1 Jun 2009

  40. FY12 Purchases and Tasks (53K OSD Gnd Sys NPP Products; (10K) G-PSDI): 0.1 FTE at CIRA from Mar 12 to Feb 13 Test real-time ATMS/NPP in TPW and RR products when they become available from MIRS in October 2012. Deliver the updated products for operational implementation Develop a snow & ice mask to eliminate problems with retrievals over snow or ice-covered areas Metop-B readiness (35K OSD Gnd Sys NPP Products ; (15K) G-PSDI): OSPO Software Contractor for .5 FTE from Mar 12 to Feb 13 Transition of the enhanced blended TPW and TPW anomaly products into operations Update the set of operational documents to include the changes. Metop-B readiness (5K OSPO Base): S/H O&M cost Shared cost for software licenses, disk storage and CPU load needed for the operational support to the application under the ESPC production environment, and also hardware maintenance and system administration needs. V14.1 Jun 2009

  41. FY13 Purchases and Tasks (162K JPSS): 1.0 FTE at CIRA from Mar 13 to Feb 14 Develop the AMSR-2 ingest capability in DPEAS Update the histogram code to process AMSR-2 TPW and RR data, and adjust the histogram correction algorithm if necessary Perform real-time test when AMSR-2 TPW and RR become operational available in Sept 2013. Evaluate the AMSR retrieval quality, and add QC checks and adjust the blending algorithm when necessary to provide the best possible blended product Deliver the updated products for operational implementation Support all required reviews for AMSR-2 enhancements Update ATBD, and other documents to reflect the changes Assist in code implementation at OSPO Assistant in evaluation of products generation from the ESPC operation (35K JPSS): OSPO Software Contractor for .3 FTE from May 13 to Apr 14 Work out data access issues for AMSR-2 Prepare the capacity for process AMSR-2 data Transition of the enhanced blended TPW, TPW anomaly, and blended RR products into operations Product quality evaluation Update the set of operational documents to include the changes. Operational Readiness Review (10K G-PSDI; 10K JPSS): S/H O&M cost 5 TB disk storage for archive the blended RR products declared operation in FY12 5 TB for extra AMSR-2 data, and also archive the blended hydro products V14.1 Jun 2009

  42. FY14 Purchases and Tasks (162K P-PSDI): 1.0 FTE at CIRA from Mar 14 to Feb 15 Develop the M-T ingest capability in DPEAS Update the histogram correction algorithm to account for the tropical orbit of M-T Evaluate the impact of M-T sampling time precession (56 days) and MADRAS latitude limits (± 27° latitude) on the blended products Perform real-time test when the M-T TPW and RR become operational available in Mar 2014. Evaluate the M-T retrieval quality, and add QC checks and adjust the blending algorithm when necessary to provide the best possible blended product Deliver the updated products for operational implementation Support all required reviews for M-T enhancements Update ATBD, and other documents to reflect the changes Assist in code implementation at OSPO Assistant in evaluation of products generation from the ESPC operation (40K P-PSDI; 10K JPSS): OSPO Software Contractor for .45 FTE from May 14 to May 15 Wrap-up the document changes for AMSR-2 Update the monitoring tools for AMSR-2 Work out data access issues for M-T Prepare the capacity for process M-T data Transition of the enhanced blended TPW, TPW anomaly, and blended RR products into operations Product quality evaluation Update the set of operational documents to include the changes. Operational Readiness Review Update the monitoring tools for M-T (10K P-PSDI): S/H O&M cost 5 TB extra disk storage for M-T data, and also archive the blended hydro products V14.1 Jun 2009

More Related