# Presentation: 228279

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

**August 30, 2005**
**Systems Engineering Center**

## Agenda

**Outstanding Model Data Issues**
***GFS40, Gridded MOS, NOGAP, FNMOC, ECWMF***
**CCB Request for OB7**
**Post OB6 Schedules**
***Operation Builds, Infrastructure Updates, Application Releases***
**Incorporating Software Development Process Improvement**
**Remaining OB7 SREC activities**
**Next Meeting Agenda**

## Outstanding Model Data Issues

**GFS 40**
**Gridded MOS (CONUS & OCONUS)  **
***Proposed changes to Agreement***
*Provide Gridded MOS in Application Release 6.2 (May 2006)*
**Max/Min Temp, Temp, Dew Point, Wind Speed and Direction, Thunderstorms 6 and 12 hr, snowfall, POP 6 and 12 hr and Relative Humidity**
**Initially populate grid with Western third of the country**
**Populate rest of CONUS as data becomes available**
*Provide Gridded MOS in OB7*
**Add clouds, precipitation type, QPF, wind gusts**
*OB8/9*
**OCONUS**

## Outstanding Model Data Issues

**NOGAPS**
***Initial Stated requirement ***
*Needed for routine support to operational forecasters at WFO's with marine forecast responsibilities.  Requested by SR, WR and PR.** *
***Currently***
*Currently received at TOC for backup purposes.  NCEP uses GFS headers in that case. *
***Issues***
*Data doesn’t have WMO headers for AWIPS.*
*Data interruptions can occur, not controlled by NCEP, Military needs take priority.*
*FNMOC going from data push to data pull. *
*No resources available to develop routine capability at NCEP or TOC.*
***What’s next?***
*SREC will revalidate the requirement*
*If still valid, TOC or NCEP resources will be necessary to develop this capability*

## Outstanding Model Data Issues

**FNMOC WW3**
***Initial Stated requirement***
*Needed for routine support to operational forecasters at WFO's with marine forecast responsibilities. This output includes spectral output in a spatial grid form, and swell height and direction which have been an outstanding marine request. *
*provides sites with marine responsibilities with another model look.*
***Currently***
*FNMOC Wave Watch serves as backup for NWS. *
***Issues ***
*NCEP modelers believe the FNMOC output is not useful because it is the average of many swell fields and not physically meaningful .  NCEP believes the information is in the wave field separation at points, and would like to expand this approach to the entire grid.  *
*The Navy version is initialized w/Navy model and not GFS.  *
***What’s Next? ***
*OCWWS has indicated that this is still valid *
**provides sites with marine responsibilities with another model look**
*An OSIP IWT on Wave Modeling is addressing a variety of requirements which would include local solutions and funding for a WWIII improvement.  This team should address NCEPs concerns and consider NCEPS solution.*
*OCWWS Division Chief will send a memorandum to CIO with requirement to add generic header(s) so AWIPS can recognize and process the data. *
*TOC or NCEP resources will be necessary to develop this capability*

## Outstanding Model Data Issues 

**ECMWF**
***Initial Stated requirement***
*The National Oceanic and Atmospheric Administration (NOAA) Office of Climate, Weather, and Water Services (OCWWS) conducted a field review in 2002-03 through regional focal points and technical representatives, developing requirements for an expanded product list.*
*Requested an increase in ECMWF products to four run times (0Z, 6Z, 12Z, and 18Z), an increase in vertical resolution to 15 levels for four of the atmospheric profile parameters (10 levels for RH), as well as an additional eleven parameters (all single-level except Vertical Velocity at 7 levels). *
***Current Status ***
*ECMWF products are available within AWIPS via the GTS. *
*These products are available at two run times (0Z and 12Z) and at 24 hour forecast intervals from 0 to 168 hours, for five atmospheric profile parameters at a very limited number of levels, as well as for PMSL.  *
*SEC sent expanded requirements for WFOs/AWIPS to NWS/CIO/Data Management Group who assist in international data issues.  However, little/no progress thus far.*

## Outstanding Model Data Issues

**ECMWF (Cont.)**
***Issues ***
*ECMWF tightly controls and limits their model output to the international community. *
*NCEP has no ability to lobby for more data.  NOAA/NWS International Affairs would need to be involved. *
*Given international nature and ECMWF tight controls, doubtful this requirement could be met even in OB7 timeframe.*
***What’s Next?***
*SREC (WFOs/Regions) should revalidate that the return justify the effort?*
*If still valid, OCWWS should pursue with IA*
*Possibly an OSIP SON should be prepared*
*Remove from OB7 SREC List*

## CCB Request for OB7

**Lost OB1 Requirement**
***Add an option in the D2D display that will allow the isopeth interval to be set so that they will not be changed when zooming in or out***
***When setting up scripts to display forecast models on the D2D workstation with either the volume browser or just calling up a particular model, the spacing is assigned based on the magnification or zoom setting of the background. ***
***While there is a setting for density, which will change the isopeth spacing for the current zoom setting (background magnification), this spacing changes when the zoom setting is changed***
***LOE - 6 months and we are not sure there is enough time to develop this capability***

## Application Releases

**New Paradigm for Post OB6 **
***Infrastructure releases (Once a year, with 2 maintenance updates/year)***
*OS and COTS Upgrades, Compiler , Hardware, Communications, System configuration*
*Integration of existing applications*
*Functionality tied closely to the infrastructure *
**WarnGen, D2D, SCAN**
*Requires extensive integration testing*
***Application Releases (2 or 3/year)***
*Strict definition of an “Application”*
**Self contained, limited integration points **
**Functionality like AVNFPS, GFE**
**Requires significant less integration and regression testing**
*Easier to install (e.g., no service backup) and deploy*
***Emergency Releases***
**Just emergency fixes (security, critical operational impact, performance**

## OB and Application Release DRAFT Schedule

**Note:  Could be affected by Prime Contractor Transition**
***OB6 Maintenance Release 1***
*GFE Handoff – October 2005*
*Deployment Begins – November 2005*
***Application Release 1***
*GFS Handoff – October  2005*
*Deployment Begins - December 2005*
***OB6 Maintenance Release 2***
*GFE Handoff – February 2006*
*Deployment Begins – March 2005*
***Application Release 2***
*GFS Handoff – February 2006*
*Deployment Begins - May 2006*
***Emergency releases***
*As necessary*
***OB7***
*GFE Handoff – February 2006*
*Deployment Begins – October 2006*

## Software Development ProcessImprovements

**SEC and development organizations have agreed on some improvements to the AWIPS development process**
***Improve planning of architecture, COTS changes, security changes, and releases***
***Improve planning of development resources***
***Use reviews to identify requirements, design, coding, and testing defects during development ***
***Use field personnel to find DRs earlier in the development process***

## Software Development ProcessImprovements

**Need help form OCWWS, Regions and field personnel in two areas**
***Actively participate in mandatory reviews for requirements, design, user interface, test plan and procedures, GFS handoff***
*Reviews will be schedule by Sept 30  (part of our improved planning)*
***Act as an approval authority and insure that the review meets the exit criteria before moving on to the next step***
*Assign a person to each review (Requirements, User Interface Test Plan and Procedures*
*Use SREC Points of Contact as a starting point*
*Approval provided to AWIPS Development Manager*

## Software Development ProcessImprovements

**Demonstrate functionality to users prior to integration**
***Either bring field representatives to development organization site or ATAN software to regional or WFOs***
***Demonstrate the functionality to field representatives on a development platform***
***Field representatives will validate testing using the test plan and procedures***
***Allow field users to perform adhoc testing***
***Capture adhoc testing and update test plan and procedures***
***Field representative approves software***
*Approval provided to AWIPS Development Manager*

## Remaining OB7 SREC Activities

**Publish Release Plan (Sept 15)**
***SEC working on SREC Website with OB7 Contents listing***
**Define application release contents**
**Identify  status of AWIPS Masterlist conversion and OSIP tasks **
**Address process for small maintenance items**
**Support for process improvement**
***Identify approval authority for each development task and review (Requirements, User Interface, Test Plan and Procedures)***
***Identify field representatives for development testing ***

## Next Meeting Agenda

**Meeting to be held on September 27 at 2:30pm EDT**
***SREC Website***
***OB7 Status***
***Application release contents - draft***
***Address process for small maintenance items ***
***Review status of AWIPS Masterlist conversion and OSIP tasks***
***Support for process improvements***
*Approval authorities and field testers*