1. NWS Partners Meeting Presented by: Ronla Henry NWS – Office of Science and Technology AWIPS SBN / NOAAPort Data Flow Interruptions National Weather Service

2. AWIPS SBN / NOAAPort Data Flow Interruptions Summary Event #1 (Range Feb, 2012 – May, 2013) –Problem: Duplicate/Missing ETNs/0000 in header –Root Cause: Combination software discrepancies and/or human error –Resolution: Software discrepancies corrected in over the past year Event #2 (May 21, 2013) –Problem: Failure of communication between WFO and NCF –Root Cause: Interruption within OPSnet/Verizon core network. –Resolution: Outage is attributed to a Natural Disaster

3. AWIPS SBN / NOAAPort Data Flow Interruptions Summary Event #3 (July 9-10, 2013) –Problem: Data flow interruption took place while trouble shooting extensive latency problem on the SBN/NOAAPORT NMC Channel –Root Cause: Product queues to small to handle products receipt. –Resolution: Outbound communications data flow configuration moved from 50 pps (products per second) out to 200 pps

4. AWIPS SBN / NOAAPort Data Flow Interruptions Summary Event #4 (July 23-25, 2013) –Problem: Data flow interruption took place while transitioning the AWIPS/NCF from primary facility to backup facility –Root Cause: Procedural and/or software issues within NCF –Resolution: Raytheon Standard Operating Procedures will be modified to mitigate the threat of queues filling up resulting in the loss of data.

5. AWIPS SBN / NOAAPort Summary Root Causes/Resolutions: –Human Error –Software Discrepancies –Procedures/policies –Configuration adjustments Short-term –Continue to analyze, review, and revise procedures, policies, and configuration settings Long-term –Investigate the implementation of an audit trail(s) for all Warnings sent by WFO’s