140 likes | 154 Views
VTEC Status & Plan for Action. National Partners Workshop June 24, 2004 Jason Tuell Office of Science and Technology. Overview. Objective Current status Actions since the September Partner’s conference Proposed schedule Issues Interaction with partners Summary. Current status.
E N D
VTECStatus & Plan for Action National Partners Workshop June 24, 2004 Jason Tuell Office of Science and Technology
Overview • Objective • Current status • Actions since the September Partner’s conference • Proposed schedule • Issues • Interaction with partners • Summary
Current status • Software • Original VTEC implemented in AWIPS OB2 software • Revised VTEC updated in OB3.1 • Deficiencies corrected in OB3.3 • NWSI 10-1703 • Updated with new specification and clarifications • Signed 28 May 2004 • IOT&E complete
Changes since January O4 • Delay implementation of VTEC in Marine Forecasts and Warnings • Offshore waters forecast (OFF), Coastal waters forecast (CWF), Near shore waters forecast (NSH), Open Lakes Forecast (GLF) • VTEC still to be implemented in Special Marine Warning (SMW), Marine Weather Statements (MWS), Coastal Flood Watch, Warnings, and Statements (CFW), Lakeshore Flood Warnings and Statements (CFW) • Change in schedule
IOT&E • IOT&E conducted between 20 Apr through 14 May • Testers included service area leads, field forecasters and one Partner (Marvin Mcinnis) • 74 TTRs • 31 Critical • 20 Major (Urgent) • 5 Minor (Routine) • 18 Watch items, potential enhancements, withdrawn or other • 2 CONOPS issues • 2 New Requirements • Segmentation of follow up statements • Head line time rounding requirements • 19 Headline errors and standardization • ALL reproducible TTRs, headline errors and standardization will be corrected by 28 June • Segmented follow up statements for short fuse warnings will be allowed in OB3.3
Schedule Changes • Revised schedule (presented January 2004) • OT&E 5 July – 30 August • Turn key on 1 Dec 2004 • Driving force behind schedule changes • Performance problems in OB3 delayed development and testing • Errors discovered during IOT&E • Service back up and unique OCONUS requirements • Schedule change will allow • Correction of IOT&E deficiencies • Implementation of unique OCONUS requirements • Implementation of robust service back up capability • More coordination between the NWS and partners
ScheduleIssues – OT&E • Watch-by-County, VTEC OT&E run concurrently • ~20 VTEC sites • ~20 WBC sites • Evaluation criteria defined in OT&E plan • Use of scripted scenarios for out-of-season products • Majority of long fuse products (winter weather, non-precipitation) to be tested using scripted scenarios
Partner-NWS Interaction Robert McLeod Chief, Awareness Branch Office of Climate, Water, and Weather Services
Partner Interaction • Must ensure adequate feedback on VTEC and other issues • Participation in OT&E is critical as learned in WBC • Planning and execution • Draft OT&E plan out for review VTEC listserve/remailer to disseminate and share VTEC related information Send comments to NWS.VTEC@noaa.gov
Summary • VTEC turn key 8 Feb 2005 • OT&E late summer early fall • Conduct joint OT&E to determine whether we are jointly ready for VTEC February 2005 Work together to make VTEC a success!