J12.4 What Does It Take to Transition Six Forecasting Systems into Operations in Ten Years? — Lessons Learned, Myths and Facts

Wednesday, 25 January 2017: 11:15 AM
608 (Washington State Convention Center )
Philip Y. Chu, GLERL, Ann Arbor, MI; and E. J. Anderson, G. Lang, J. G. W. Kelley, E. Myers, A. Zhang, J. Xu, and Y. Chen

NOAA Great Lakes Operational Forecasting System (GLOFS), developed by the Great Lakes Environmental Research Laboratory and National Ocean Service, has been operational since 2005.  A project to upgrade GLOFS, using FVCOM as the core 3-D oceanographic forecast model, has been conducted during the past 3 years involving GLERL, NOS/CSDL and CO-OPS and NCEP Central Operations. The 1st phase of this project has been completed with the operational implementation of a new GLOFS version for Lake Erie on NOAA's Weather and Climate Operational Supercomputer System in May 2016.

Many lessons were learned from transitioning six forecasting systems to operations in 10 years.  On the technical aspects which include hardware, software, systems -- we found that keys to successful transition are on 1) methods to harden the software infrastructure to make a robust, automated system; 2) backup and alternative procedures for handling missing or corrupted input data; 3) standardized validation and skill assessment metrics; 4) preparation of complete documentation including validation test reports, standard operating procedures (SOP), and software user guides; 5) adequate near-real-time observations of discharge, and water levels to provide LBCs  for the system and 6) field projects in the Great Lakes (i.e. IFYGL) to provide surface and subsurface data for the evaluation of the forecast models during  development and testing. In particular, program source codes need to be frozen during the testing, validation and the transition period with proper version control.

In addition to the technical aspects, a successful system transition from the research/development stage into operations also involves non-technical aspects, such as commitment from senior leadership, frequent communications among all involved parties on progress and milestones, training sessions for the system operators and user engagement workshops for the end users.

- Indicates paper has been withdrawn from meeting
- Indicates an Award Winner