120 likes | 222 Views
Office of Hydrologic Development R2O Perspective. Geoff Bonnin Chief, Hydrologic Science & Modeling Branch Office of Hydrologic Development NOAA National Weather Service.
E N D
Office of Hydrologic DevelopmentR2O Perspective Geoff Bonnin Chief, Hydrologic Science & Modeling Branch Office of Hydrologic Development NOAA National Weather Service
Weather Forecast Offices (WFOs) prepare and deliver information and services to the public with the help of the media and private weather industry WFOs (124) The Public
NWS Headqua r te r s R e gional Headqua r te r s (6) NCEP Center (9) Ri v er F o r ecast Center (13) W e a ther F o r ecast O f fice (122) T sunami W a r ning Cente r s (2) Center W e a ther Se r vice Unit (21) “First echelon offices” (River Forecast Centers (RFCs) and the National Centers for Environmental Prediction (NCEP) prepare “guidance” used by WFOs to serve the public. RFCs (13) NCEP WFOs (124) The Public
Each of these “field” or “operational” offices uses software and systems to perform their jobs. RFCs (13) NCEP WFOs (124) The Public
Dept of Commerce NOAA NWS OHD OCWWS OS&T OOS Field Structure RFCs (13) NCEP HSMB HSEB HSD The Office of Hydrologic Development (OHD) is a line Office Within the National Weather Service The Hydrologic Science & Modeling Branch (HSMB) & the Hydrologic Software Engineering Branch (HSEB) make up OHD’s Hydrology Laboratory WFOs (124) The Public
RFCs (13) NCEP WFOs (124) The Public HSMB, HSEB and the Hydrologic Services Division (HSD) work together to support hydrologic science and techniques implemented as operational software at field offices OHD HSD User Support HSMB HSEB Operational Quality Hydrologic Software Science & Techniques Feedback & Requirements
RFCs (13) NCEP WFOs (124) The Public There is no reason for HSMB, HSEB and HSD to exist except to help the field offices do a better job! OHD HSD User Support HSMB HSEB Operational Quality Hydrologic Software Science & Techniques Feedback & Requirements
We must ensure these "great ideas" are implementable - Gary Carter For HMT to succeed we must improve the ability of the forecasters to make forecasts
Data Flow Diagram Process Input Output
Business Process Modeling Policy Process Input Output Infrastructure
Nationally supported software and systems exist in the context of: - policy - systems infrastructure capacity, reliability, availability - forecaster capacity & workflow - competing funding priorities - etc Policy Process Input Output Infrastructure
WFO Raleigh Collaborative Research5 Step Collaborative Process • Step1 – Discover and Share (only the beginning) • Relative to the needs of NWS operations, a paper is not the end product; rather it is only the beginning. • Step2 – Demonstrate Added Value (so what? show me) • Forecasters will not use a discovery until its added value, above and beyond current forecast practices, has been demonstrated. • Step3 – Operational Implementation (practical?) • User friendly, reliable, and efficient accessibility is a must. • Step4 – Mastery (by all, not a few) • Training and quality control ensuring the effective utilization of the discovery by the entire forecast staff is required. • Step5 – Periodic Review (a necessity) • Periodical review for the staff is at least a seasonal necessity, while there is always a need for additional refinements.