1. Next Generation Warning Tool (NGWT) Jason Tuell Systems Engineering Center Office of Science and Technology

2. Overview Background Near term solution Strategic solution Implementation considerations Summary

3. Background Need to create integrated warning tool –Responsive streamlined software system in sync with WFO forecast, watch/warning process –Minimize training, support resources Need to address significant shortcomings in WWA application Provide foundation for future requirements –Allow long fuse warnings to leverage the digital forecast process –Anticipate changes in formats and allow greater geographical specificity

4. Near term solution Minimize the pain – make current version of WWA tolerable – more responsive to operations –More than 50% of OB3, OB4 WWA development effort targeted at improving usability –Field engaged in “test driving” OB3, OB4 WWA OB3 test drive 4 November – OB3 WWA well received by regional representatives OB4 test drive 18-19 February - OB4 WWA identified as significant improvement Keep Watch-by-County and VTEC on track

5. Near term – the pain High level Build DeliverablesCategory OB2.2 Editable final transmit window Usability OB3.0 Duplicate NWR products VTEC problems found in DT&E testing Redefine Upgrade/Downgrade function WBC/WCN Site Backup Follow-up/clear transmission Spell Checker Usability VTEC WBC Usability OB3.1 Apply QC of editable transmit window New VTEC requirements (e.g. test and experimental product designations) OB3.2 Correction/Amendment functionality Usability VTEC Usability OB4.0 WBC/WCN Redesign Forecaster identification interface TPC/JTWC/CPHC headlines in IFPS WWA WSO Intersite coordination Regenerate NWR Messages Preview display function WBC Other Usability G G G G

6. Strategic solution Objective: Improve watch/warning tools –Optimize utility and flexibility for WFO operations –Keep what works well, re-design what doesn’t –Make software sync with the forecasting process –Anticipate future requirements and concepts of operation Strategy –Use disciplined software development approach which identifies user needs and design constraints early in the process –Create dedicated, cross functional team to define requirements through use cases Review governing policies in parallel –Spiral development – build some, test some, field some – used with great success in Rapid Prototype Project

7. Implementation considerations Separate meteorological from formatting tools –Meteorological tools will allow forecasters to focus on the what, where and when of warnings –Formatting tools will focus on how content is delivered to customers Dissemination methods and contents to be flexible to accommodate alternative technologies –XML, GIS, graphics?

8. Summary Next Generation Warning Tool commitment made to field to overcome shortcomings in current software Team approach critical to success of defining and developing tool –Need regional representatives to the requirements definition team Prototyping the best method to deliver capability that the field wants