1 / 23

AWIPS Software Recommendation and Evaluation Committee (SREC) Monthly Status Meeting

AWIPS Software Recommendation and Evaluation Committee (SREC) Monthly Status Meeting. July 31, 2006 Systems Engineering Center. Agenda. OB7.2 Status OB8 Planning OB8 Contents, Schedule, Remaining SREC Activities Documentation Needed Process for SREC Updates to OB8

cooper
Download Presentation

AWIPS Software Recommendation and Evaluation Committee (SREC) Monthly Status Meeting

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. AWIPS Software Recommendation and Evaluation Committee (SREC) Monthly Status Meeting July 31, 2006 Systems Engineering Center

  2. Agenda • OB7.2 Status • OB8 Planning • OB8 Contents, Schedule, Remaining SREC Activities • Documentation Needed • Process for SREC Updates to OB8 • New Items to Consider for OB8 • DR Team • Purpose, Logistics, Members • Process and Responsibilities • DR Classification • DR Backlog • Next Meeting • Action Item Review

  3. Release 7.2 • Development Status • Pre-Integration Testing (PIT) completed in June 2006 • Participants - ER, SR, WR, CR, Training (2), OCWWS, SST • Found 90+ Drs • Pre-SwIT started on July 24

  4. OB8 Contents • Development Allocations • Planned: • Infrastructure – 45%, Strategic – 43%, A&C – 12% • Actual so far: • Infrastructure – 14%, Strategic – 60%, A&C – 26% • OB8 Contents • OB8 Release Plan (Attachment 1 – Sorted by Category and Release) • Meets all of the Regional top 5 and most of the top 20 for each category • Transition of GSD and OHD O&M to Raytheon will impact the OB8 deliveries. Significant impact between July 2006 – January 2007. (e.g., GFE items) • Follows OSIP priorities • Assigned some items to OB9. These items (e.g., AWIPS Software Training Capability) will be developed within part of the OB8 timeframe (last quarter FY2006 and FY2007) • NWS Concept of Operations not included • Needs to be added now that funding will be available • NOGAPS – Remove from OB8. OSIP task looked at 4 alternatives and selected a partial ECMWF

  5. OB8 Schedule5/30/06

  6. Remaining OB8 SREC Activates • Step 10: Validate/Approve Release Content (August) • S&T Committee • Step 11: Prepared Change Requests for AWIPS CCB approval (August) • Software Release and Data Items (e.g., RUC) • Responsibility: SREC Vice Chair • Step 12: Provide the OCWWS Training Division with approved software build contents for inclusion to the NSTEP process (August) • Responsibility: Executive Secretary • Step 13: Identify SREC Focal Points for each OB8 development item (August) • Responsibility: SREC Vice Chair

  7. Documentation Needed for OB8 • Need OSIP Documentation for: • Hardware upgrades (Raytheon) • Port to NCEP GRIB2 Decoder (SEC- Gockel) • Ensembles (OST -Sreela Nandi) • NWS AWIPS Software Training Capability (Training - Magsig) • Centrally Produced 5km derived grids of sensible weather elements (ER- Waldstreicher) • FNMOC Wave Watch Model Guidance (OST – McAloon) • 4D Weather Information (Johnston, Graf) • Aviation Forecast Preparation System (Graf) • Next Generation Warning Tool (Ferree)

  8. Process for SREC Updates • Planned SREC Update dates for new requirements • OB8.1 – September 1, 2006 • OB8.2 – March 1, 2007 • OB8.3 – August 1, 2007 • Planned Date for DRs • OB8.1 – September 26, 2006 • OB8.2 – March 16, 2007 • OB8.3 – August 10, 2007

  9. Process for SREC Updates • Request official nominations and gather documentation • Prioritize • Option 1: Weigh new items and see where they fall according to prioritization • Option 2: Voting members recommend items for a OB release, group votes on new addition and what to remove (if necessary). • Note: Any new addition will usually require taking something of the list

  10. New Items to Consider for OB8 • Strategic • New CONOPS • Autonowcaster (OSIP 06-010) • Infrastructure • Security patches as needed • Ensure AWIPS baseline applications can be executed by users who run Korn Shell • NAM Consolidation • Add a GD Perl module • Implement GIS for NWS (OSIP 06-003) • Removing Redundant files from Shapefiles • A&C • Data • Excellent New Precipitable Water Web Page • RUC13 Product Changes (add terrain height, CAPE and CIN) • Gridded Icing/Turb/CB products for World Area Forecasts (OSIP 05-082) • Higher Resolution QuikSCAT • GMSRA product

  11. New Items to Consider for OB8 • A&C • Data (continued) • NCEP • Marine • North Pacific Hurricane wave model during hurricane season out to 126-h at 6-h intervals • Wave Steepness for all models to be implemented this month. • RTG_SST_HR analysis done daily need to determine how to break into usable pieces for coastal and Great Lakes WFOs. • Models or enhancements on the way and to be considered: • Great Lakes WW3. Products should be available  4th quarter of 2006 • Real-Time Ocean Forecasting System (Atlantic): Surface heights and surface currents hourly; north wall of Gulf Stream; temperature, salinity, and  and currents  at selected levels. All products out to 120-h at 24-h intervals, updated daily FY. Products already in production • Real-Time Ocean Forecasting System (West Coast, Hawaii, and Alaska) ) Surface heights and surface currents hourly;  temperature, salinity, and  and currents  at selected levels. All products out to 120-h at 24-h intervals, updated daily. Products expected to  be available FY 2008-2009 time frame.

  12. New Items to Consider for OB8 • A&C • Data (continued) • NCEP (continued) • In FY2007 to early FY2008 timeframe, EMC's Mesoscale Modeling Branch will perform upgrades to: • NAM & DGEX • horizontal resolution increase to ~8 km.  However, if central downscaling efforts mature fast enough, there may be LESS need to upgrade the current full complement of 12 km NAM output to 8 km.  Forecasters may still need some 3D fields on the full 8 km grid while the sensible weather elements would be provided via central downscaling at the 5 km NDFD resolution.  If central downscaling works, then there will be less need for DGEX which would normally be upgraded simultaneously with the NAM • SREF • horizontal resolution increases to have all members run at horizontal resolution closer to 32 km resolution. This would allow use of output grid #221 (32 km) rather than #212(40 km) and #216(45km) and use of WRF modeling system for all members.  This latter point does not effect output except in naming conventions of individual members which aren't going to AWIPS anyway.

  13. New Items to Consider for OB8 • A&C • Data (continued) • NCEP (continued) • Reinstatement of Fire Weather / IMET Support runs.  • These will definitely be at sufficient resolution to run with explicit convection (~4 km or better).  Upgrade the output grids being used by the regions to feed FX-Net from the current 8 km HiResWindow grids.  Currently, these are not being sent over SBN to AWIPS but IMETs report it is difficult to use NCEP's special FWIS runs when they only ever see them when they are in the field where pressures & stress make it difficult to use an "unfamiliar" model.  This will be alleviated somewhat by WRF-NMM going into the NAM because then FWIS will be just a higher resolution version of the model running in the NAM. Still, there has been discussion of having these runs distributed via AWIPS. • HiResWindow • horizontal resolution increase to ~4 km and synchronization with latest version of WRF being used in NAM and SREF and FWIS.  Output grids are currently 8 km, new output grids for the 6 domains (4 large: eastern CONUS, central CONUS, western CONUS and Alaska and 2 small: Hawaii and Puerto Rico) will be defined at the new higher resolution.

  14. DR Team • The DR team was established to: • Support the SREC in the preparation of AWIPS release content • Classify the Deficiency Reports (DRs) in terms of mission priority, severity and urgency, • Recommend an AWIPS Release • The DR team charter will establish: • Establishes voting and non-voting membership • Establishes an meeting schedule • DR Process and Responsibilities

  15. DR Team • Logistics • DR Team meets every Tuesday at 2:00pm Eastern time • Conference Call Number • 1-877-784-1165 Passcode: 649604 • SSMC2, Room 8246

  16. DR Team • Members • Chairperson • Susan Reiley (OS12 – Requirements and Change Management) • Vice Chairperson • Edward Mandel (SREC/SEC) • Voting Members • Regions (1 vote for each Region) • Joe Palko (ER) • Bill Gery (CR) • Eric Howieson (SR) • Sean Wink (WR) • Duane Carpenter (AR) • Bill Ward (PR) • OCWWS (1 vote from either) • Wayne Weeks (OS21 - Marine) • Art Thomas (OS22 – Met Services) • Mike Graf (OS23 - Aviation) • Jeff Zimmerman (OS3- Hydrologic) • Myron Berger (OS4 - Climate) • Mike Szkil (OS6 - Training) • Jim Heil (OS7 – Observation Systems) • OPS (1 vote from either) • Jamie Vavra (OPS21) • Tim Crum (OPS4)

  17. DR Team • Support Staff • Data • Brent Gordon (NCEP) • John Paquette (NESDIS) • Mike Istok (Radar) • Development Organizations • Mohsen Ghandi (ASM) • Jim Fluke (GSD) • Iris Boon (MDL) • Steve Schotz (NCEP) • Mark Glaudemans (OHD) • Kevin Johnson (NCF) • Release Managers • Thuy Tran (Release 7.1) • Edward Mandel (Release 7.2, OB8, Post OB8) • DR Originators

  18. DR TeamProcess and Responsibilities • Step 1: Prepare List of New DRs Since Last Meeting and Distribute to the DR Team • Responsibility: Chairperson • When: COB every Tuesday • Step 2: DR Team Provides Comments • Responsibility: DR Team and Development Organizations • Request action (Cancel, Retest and Close) or Classification (Impact, Severity and Urgency) and information to support that assignment (Justification) • When: COB every Thursday • Critical DRs – 2 day response, Major and Minor DRs – 9 day response • Step 3: Consolidate Comments and Distribute to DR Team • Responsibility: Chairperson • When: COB every Monday

  19. DR TeamProcess and Responsibilities • Step 4: Review at the DR Team Meeting • Review DR Classifications, obtain DR Originator and Development Organization input and recommend a OB release • Responsibility: DR Team • When: 2:00pm every Tuesday • Step 5: Prepare Release Adjustment • Prepares Release Adjustment (RA) to modify the requirements baseline and to make the necessary changes in PVCS (Cancel, Retest, Close or assignment to a OB release and a Development Organization Assignment • Responsibility: Release Managers • When: Every Wednesday • Step 6: Approve Release Adjustment • Responsibility: Raytheon, SEC, and OPS • When: Every Monday

  20. DR Team - DR Classification • Mission Priority • How important is the functionality, data or capabilities? • Is it required for environmental monitoring, assessment, warning or forecast product generation or dissemination? • Crucial, Major, Minor • Severity • How much is the current capability limited by the problem? • Critical, Serious Moderate, Minimal • Urgency • Based on Priority and Severity of the problem • Resolve Immediately, Give High Attention, Normal, Low and Defer

  21. DR team - Review of DR Backlog • Objective • Prioritize Unassigned DRs and Assign to a release • Result • Correct 210 Major DRs and 75 Minor DRs during OB8 • Unassigned DRs • Review OB6-P HELD DRs Major (3) • Review OB7 DRs Majors (9), Minors (5) • Review OBX DRs – Majors (106), Minors (250) • Review DRs with no Target Release - Majors (104), Minors (70) • DR Team will validate and assign to a release • Looking to complete these items by September 26, 2006

  22. Next Meeting • Regular meeting on August 28 at 2:00pm EDT • Discuss any changes to OB8.1

  23. Actions • Old Action Items • Review of Charter – Address the DR process. (Completed) • Draft included in today’s meeting • Determine how to handle new requirements received after March 27, 2006. (Draft proposal at the July 31, SREC meeting) • Determine and publish cutoff dates for new requirements and DRs. (Part of this briefing) • Address limited access to SREC website and AWIPS One-Stop Shop. SREC suggests implementing a password policy (Chambers). • Submit change request to provide TPC probabilistic wind speed forecasts in 6 hour vs 12 hr intervals. The 12 hour intervals have been tested during the 2005 hurricane season and OB6. SREC agreed to review the change and provide options (OB7.1, OB7.2 or prioritize for OB8), to the SREC members. (Completed) • Insure that NWS CONOPS is provided the necessary resources to meet the objectives of the group (Completed)

More Related