1 / 49

AWIPS Software Recommendation and Evaluation Committee (SREC) OB7 Development

AWIPS Software Recommendation and Evaluation Committee (SREC) OB7 Development. March 29, 2005 Systems Engineering Center. Agenda. SREC Introduction Charter, Responsibilities, Membership, Process Review of Past Releases OB5 and OB6 SREC Process

ziarre
Download Presentation

AWIPS Software Recommendation and Evaluation Committee (SREC) OB7 Development

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) OB7 Development March 29, 2005 Systems Engineering Center

  2. Agenda • SREC Introduction • Charter, Responsibilities, Membership, Process • Review of Past Releases • OB5 and OB6 • SREC Process • AWIPS Prioritization, Analysis, Release Plan • Presentation of OB7 Straw man • Remaining Activities • SREC review and approval and S&T approval • Process Improvement • Continue Process for Future Releases • Five Year Plan

  3. SREC Charter • Establishes SREC responsibilities • The priority order of presented software modifications based on validated requests, • Software build contents and schedules, and • A five year roadmap of build contents (OB7 – OB11) • Establishes SREC voting and non-voting membership • Establishes an SREC meeting schedule in synchronization with the AWIPS Software Build Cycle

  4. SREC Responsibilities • Evaluate and prioritize software content recommendations, based on mission priorities, for integration into the AWIPS baseline (SREC) • Analyze software content recommendations to determine impacts or level of effort of requests and resources available to fulfill need (SEC, Development Organizations), • Recommend the contents for AWIPS software builds to the S&T Committee (SREC) • Facilitate enhanced communication, cooperation, flexibility, and discipline among Regions, Centers, and Headquarters to concur on software build contents, 5 year roadmap, and overall vision of AWIPS (SREC)

  5. SREC Members • Chairperson (non-voting) • Charles Piercy (AWIPS Program Manager) • Vice Chairperson (non-voting) • Edward Mandel (AWIPS Development Manager) • The Executive Secretary (non-voting) • Suzanne Lenihan

  6. SREC Membership • Field members (voting) • Eastern – Neal Dipasquale • Central – Bill Gery • Southern – Eric Howieson • Western – Jeff Walker • Pacific – Bill Ward • Alaska – James Partain • NCEP – Steve Schotz • Integration Members (voting) • OCWWS – Leroy Spayd • OHD – Jon Roe • OST – TBD • OOS – Ashley Kells • Changes? • Email to SREC Secretary from S&T Committee member or Director of each FMC

  7. SREC Membership • Support Staff (non-voting) • SREC Planning team • Area Advocates • Radar, WWA, IFPS/GFE, New Products, Hydrology, Fire and Public, marine and Coastal, Aviation, Hydrology • Centers: AWC, TPC, SPC, HPC, CPC • NEXRAD ROC • Data Providers (NCEP, NESDIS, SEC Data Management) • Development Organizations (FSL, MDL, SEC, OHD) • Training Group (HQ and WDTB) • CIO

  8. OB5 Contents • Radar • TDWR Products • Mesocyclone Detection Algorithm • RPS List Expansion from 65 to 150 • Satellite • Add 3.9u HDW product • Upgrades to Satellite Decoder

  9. OB5 Contents • Data  • Decode and Display AVN, MRF, ETA MOS products • PR Lightning Decoder • HPC 5km 4-7 days (GRIB2 changes) • Decision Assistance • SCAN: Service Backup, Rapid Update New Alarm • FFMP: Service Backup, Point Data Control (PDC) Server and Display, Basin Layer Depictables • SAFESEAS: Station Obs Tables • LSR: Marine Events, Predefined Location Sets

  10. OB5 Contents • Hydrology • Site Specific Hydrologic Prediction Function • WHFS Observed Precipitation Processing Server • Enhance Dam Break Analysis to DAMCREST • RFC OH Enhancements • Fire Weather • Format and Display Fire Weather SPOT Forecast • LAPS • Routine Product Updates

  11. OB5 Contents • Security • Modify directory access • Infrastructure • AS Decommissioning • Enable stack tracing • Augment localization script with patch scripts • Complete Imp of Fire Weather zones map background • Fix compiler warning messages • Baseline RSA Software • Intelligent Purging Mechanism • Notification Server Enhancements • Record Climate not a persistent process

  12. OB6 Contents • Adaptive and Corrective maintenance • Radar • TDWR Products (mult. radars, WAN based RMR) • Snowfall Accumulation Products • MDA DMD Product Changes • Change to Clutter Filter Control Changes from ORDA • Report RPG and RDA build n NEXRAD Unit Display Status • WSR-88D Archive Level 3 Status Product • All 88D products from neighboring offices • Satellite • Polar Visible and IR imagery • Decision Assistance • SCAN Enhancements: VIL Density, Handel MDA Product, Time of Arrival • FFMP Enhancements: Basin Trace, Gage Removal, Multiple Monitor Times • SAFESEAS: Table sampling parameters, Processor Enhancements, Customizability changes • LSR Enhancements: Quick List • GFE • Provide capabilities for generation of Gridded Watches and Warnings in IFPS

  13. OB6 Contents • Adaptive and Corrective maintenance • Data • Gridded MOS (CONUS & OCONUS)-5km grid, issued 2x daily • MOS Guidance for Coop Sites • Enhancements to marine MOS • Ingest/Display Gridded MOS Data • Full GFS (180 hrs for 4 cycles at max resolution) • Ingest Gridded Probabilistic Winds from TPC • Ingest Global Model Visibility guidance • Ingest Global Model Ice Accretion guidance

  14. OB6 Contents • Strategic • Dissemination • All Hazards (5.1) • New Science • Data • Ingest/Display MAROB marine coop observations

  15. OB6 Contents • Infrastructure • Linux OS Upgrade to ER3.0 • Migrate to Postgres • Applications • Database • OH crons/apps • Additional Frame Capability • Replacement Trigger function • Display a subset of GFE parameters on D2D • Display RFC based QPE grids on D2D • Remove Verification form the Baseline • Remove ICAT from the Baseline • Test/ Practice Mode

  16. AWIPS Development AllocationsOB6 SREC (Planned vs Actual)

  17. Items Pushed from OB6 SRECReassigned to OB7

  18. Items Pushed from OB6 SRECNeed to be Reassigned

  19. SREC Process • AWIPS Requirements Prioritization • Analysis • Release Plan and Obtain Approval • Process Improvement • Continue Process for Future Releases • Five Year Plan

  20. AWIPS Requirements Prioritization • SREC members recommend candidates to Executive Secretary (September – November 2004) • Master list created (December 2004) • Requirements assigned either to: • Must Do, Major Return on Investment, or Strategic • Separate Tactical and Strategic items • Tactical: nearer term or more mature items, lower hanging fruit, continual unmet requirements (reviewed by SREC) • Strategic: longer term or less mature items requiring more planning, conops needs to be considered, investment in resources required, greater complexity (reviewed by STAT)

  21. AWIPS Requirements Prioritization • Evaluate and Prioritize (Dec 2004) • Two lists voted on by SREC voting members • Use Weighted approach for final ranking • Tactical • 71 Requirements 1st tier 2nd tier 3rd tier 22 21 28 • Strategic • 106 Requirements 1st tier 2nd tier 3rd tier 36 37 33 Note: Some duplication between lists

  22. AWIPS Requirements Prioritization • Candidates should ideally be following the Operations and Services Improvement Plan (OSIP) and completed Stage 1 and Stage 2 (February 2005) • Perform ROM System Impact Analysis • Look at impact on hardware, data, communications • Look at software development effort, cost and uncertainty • Requirements assessed as Medium/High Risk assigned to the OSI process • Area advocate will be primarily responsible for leading the OSIP • Executive Secretary will be the coordination focal point • Once the OSIP process is completed for Stage 1 and 2, the requirements can be prioritized by the SREC members

  23. Analysis • Further Definition by Development organizations SEC and Area Advocates (March 2005) • Perform Requirement Definition • Fully Define Functional Requirements • Fully Define Data Requirements • Prepare Work Breakdown structure • Review Dependencies • Data and Development Organization • Hardware, Communications, System Architecture/Configuration • COTS, Freeware, Operating System, System Services/Infrastructure • Prepare Level of Effort Estimate

  24. Define Release Plan • Strawman release plan prepared by SEC (March 2005) • Based on SREC weighting • AWIPS Budget • Development organization’s expertise • Development allocations • Release schedule

  25. Development Allocations • As a result of Corporate Board and S&T Committee actions, looking for a new focus • Focus near term strategic and infrastructure efforts on addressing critical AWIPS “warts” • Software quality • Length installs and recoveries • Long lead time for incorporating new functionality and data sets • Start laying foundation for re-architecture

  26. Development Allocations • New Development Allocations for OB7 SREC • Assignment of 10% towards improving software quality • Development Process • Standardize, improve and enforce development process and guidelines • In-house/alpha functional testing (with forecasters) prior to GFS handoff to minimize DRs during integration testing • Develop metrics to measure improvement • Testing • All types of weather, critical scenarios • Increase percentages of infrastructure (20-36%) and strategic (15-32%) tasking • Length installs and recoveries • Long lead time for incorporating new functionality and data sets • Decrease Adaptive & Corrective Maintenance (50-18%) and New Science (15- 4%)

  27. OB6/OB7 Development Allocations OB6 Proposed OB7

  28. AWIPS Release Schedule • Release OB 6.0 • Alpha - June/July • Beta – July, August • Deploys September 14, 2005 • Release OB 7.0 (Deploys 9/27/06) • Implement new Release paradigm for Post OB6 • Rapid Alpha Release (RAP) process will end with IFPS 17.Final and AVNFPS 3.0 • Replaced with Application Releases • Requirements will be assigned to a major release (OB7) • But could be delivered early via the application release process

  29. AWIPS Release ScheduleNew Paradigm for 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 (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)

  30. OB7 StrawmanTactical • Software maintenance • DRs from previous releases • FSL (40), MDL (40), SEC (80), OHD (30) • Radar • Super‑resolution 88D base products • Model data • GFS BUFR Sounding Data (OB6 SREC) • GFS Ensemble data (192 hrs/12 members) • All 12 km Eta products CONUS & AK upgraded to 10 km from North American Mesoscale WRF • Full suite of SREF products for CONUS and Alaska • ECMWF model (prep work) • All 20 km RUC products upgraded to 13 km.

  31. OB7 StrawmanTactical • Hydrology • WHFS site specific model • Integrate HL-RMS into NWSRFS operations • Decision Assistance • Auto-nowcaster short-term convective forecast application • GFE • Develop and incorporation of a new Universal Formatter (UFOR) for CRS • Grid Initialization • Add the capability to use NCDC climatological data in GFE for display, smart tools, and formatters • NDFD • NDFD grid sub sectors for RFCs via AWIPS

  32. OB7 StrawmanStrategic • Radar • Add products to TDWR SPG • candidates are: composite reflectivity (CZ and/or ULR), VAD wind profile (VWP), Vertically Integrated Liquid (VIL). • Satellite • GOES 0 products (launch between Jul 05 & Apr 07) • Decision Assistance • FFMP Enhancements • Guardian • SAFESEAS Enhancements • SNOW • Hydrology • Integration of RFC QPE tools into a common National System NDFD • NDFD • Extend geographic domain of NDFD products to cover Offshore and High Seas domain

  33. OB7 StrawmanStrategic • Infrastructure • Improve installation times • Analyze where time is spent during installations over last four OB releases • Target biggest opportunities for improvement • Objective reduction • 25% reduction in installation times • Threshold reduction • 15% reduction in installation times • Develop prototype data distribution method • Objective: Have prototype installed in at least one WFO and RFC. • Threshold: Have fully working prototype in lab

  34. OB7 StrawmanInfrastructure Tasks • COTS Upgrades (e.g., gcc compiler, Postgres) • Technology Transfer (e.g., GFE Support, Communications, Graphic Workstation, WarnGen) • Decommission DS • Dail-out Radar replacement • LDAD Server replacement (HP with LX) • GFE/GHG Infrastructure • GRIB2 Decoder (MDL to NCEP) • Removing local data access on NAS • Modify architecture to allow more frequent release • Modify architecture to support testing of different weather scenarios

  35. Release Plan Approval • Obtain SREC Approval (April 13) • Allow trading between regions • Obtain S&T Approval (April 20) • Publish Release Plan (April 27) • Establish Development Organization tasking • Establish/maintain an SREC Website • Provide to OCWWS training group

  36. Process for Future Releases • Prepare five year plan (May/June 2005) • Identify tasks for OB8 (9/07) – OB11(9/10) • Use process similar to OB7 • Include process improvements

  37. Process Improvement • Submission of candidate requirements • More descriptive requirements • Use checklists • Update and quality control listings • Group similar requirements • Numerous duplicate entries • Separate infrastructure list • Include OCWWS Directive Changes

  38. Directive Changes • Proposal for handling Directive changes • Allocate 2% of Infrastructure tasking towards Directive changes • Prepare and implement a method to handle Directive changes • Prepare Draft Directive Change (OCWWS) • Submit to regions, applicable offices and OST for review (OCWWS) • Submit to SREC for analysis and assignment to a release (OCWWS) • Include priority ranking • Approval of Directive changes (SREC) • 2nd draft of Directive Change prepared with effective dates based on release assignment (OCWWS) • Submit to regions, applicable offices and OST for review and obtain final approval (OCWWS) • Submit AWIPS RC, DRG Request and begin Public Notification (OCWWS) • Begin development • Implement for next SREC

  39. SREC Schedule Highlights March 8 , 2005 Provide OB7 straw man to SREC team March 29, 2005 Opening SREC Session to discuss OB7 straw man list April 6, 2005 Regions to provide the final proposed OB7 contents (includes internal negotiations between regions), April 13, 2005 Second SREC session to get consensus on proposed OB7 contents April 20, 2005 Present to S&T Committee for approval or revision April 27, 2005 Final SREC Session to review S&T Committee revisions and planning of future release contents May/June 2005 Future release planning September 2005 SREC Meeting to Review OB6 Content and OB7 Progress and New Candidates for OB8 March 2006 OB8 SREC

  40. OB7 Straw man Tactical -1st Tier

  41. OB7 Strawman Tactical -2nd Tier

  42. AWIPS Requirement PrioritizationTactical – 3rd Tier

  43. AWIPS Requirement PrioritizationTactical – 3rd Tier

  44. OB7 StrawmanStrategic -1st Tier

  45. OB7 StrawmanStrategic -1st Tier

  46. OB7 StrawmanStrategic -2nd Tier

  47. OB7 StrawmanStrategic -2nd Tier

  48. OB7 StrawmanStrategic – 3rd Tier

  49. OB7 StrawmanStrategic – 3rd Tier

More Related