1. HazCollect Project AWIPS Critical Design Review MarySue Schultz CIRA/FSL December 8, 2004

2. Outline System Design Overview AWIPS System Interfaces AWIPS Software Design Software Development Status Testing

3. System Design Overview

4. AWIPS Requirements Store hazard products received from the SBN and WAN in the Text Database (filter out duplicates). Send hazard products with local WMO headers to the primary and backup NWWS uplink sites. Transfer products in voice-ready format to the CRS. Notify WFO staff prior to warning dissemination (audible and visible alarm). Perform all of the above within 30 seconds.

5. AWIPS Requirements Software must perform during failover. Software must perform during site backup

6. Assumptions Hazard products transmitted on the SBN / WAN will have the same format as current weather warning products: –A valid WMO header –Full county codes Software for formatting and transmitting products to the CRS will be provided to FSL.

7. HazCollect System Design EMsDMIS NWS Gateway HazCollect Servers NCF CAP format Converts to AWIPS WMO format SBN WAN NWWS (primary) NWS WFOs CRS transmitters NOAA weather radios (primary/ backup) NWWS DMIS: Disaster Management Interoperability Services CAP: Common Alert Protocol CRS: Console Replacement System NWSTG

8. OB6 Hardware Configuration NAS CP DX1DX2PX1 PV LX FDDI DS1DS2 DX1: TextDB read/write WarnDB Decoder SMTP MTA/MHS HazCollect Processes Text Notification [Text Database] [Data Storage]

9. AWIPS System Interfaces

10. AWIPS Interfaces HazCollect Servers - Warning products delivered over SBN and WAN CRS - CEM Formatter NWWS - WAN interface package (NGIT)

11. Interface Issues / Notes Products delivered over the SBN have CCB headers; products delivered over the WAN do not. CEM formatter does not return status values. Check CEM formatter into OB6?

12. AWIPS Software Design

13. Warning Products: From SBN to Text DB CP Acq Server Comms Router Data Controller Warn DB Decoder Text DB Writer Data Server (DX1) FSL SEC Text DB NGIT SBN

14. Automated Dissemination of Hazard Products CP SBN Acquisition And Processing Text DB NWWS CRS DX1 New Code Product Notification Text WS To NWWS And CRS WAN D-2D Archive

15. Hazard Warning Dissemination: Current / Backup Design Forecaster Input Text Workstation WAN Data Server Text Window WAN Interface Text DB Writer Text DB NWWS NCF NWR Hazard Product [Archive] (Primary and Backup) CRS

16. Automated and Backup Modes NCF SBN WAN NWWS SBN Ingest WAN Ingest Text DB CRSNWR NWWSNCF Text DB Text WS CRS NWR WFO NWWS Automated Backup NWWS

17. Design Changes Sites required to use CEM formatter for hazard products; locally developed formatters can be used for weather products. D2D notifications: - Red banner box used for arrival of priority 1 and 2 products; - Red banner box used for error notification; - Blinking status box used for arrival of priority 3 products; - Three attempts to send products will be made before error notifications sent to D2D. Check contents of CEM formatter output files to determine the success or failure of the formatter. Activate alarm/alert on the Text Workstation.

18. Issues / Notes Development / testing of CRS code: - Formatters: CEM formatter has been modified to handle new event codes. - Testing of CRS transmission code: CRS and NWR transmission code has been installed in a previous build. - CRS dictionary

19. Issues / Notes Error handling: - Notify D2D of any processing errors - Attempt to send products three times - Red banner box + audible alarm - CEM formatter errors

20. Issues / Notes Site backup: - No access to neighboring sites’ NWR transmitters - NCF will transmit to NWWS Text DB performance No VTEC numbers: - Hazard warnings are not VTEC products No acknowledgement from AWIPS to EMs: - Error notification is possible

21. Software Development Status

22. Phase I Development Requirement: develop and test software that processes one event code. Status: - Development has been completed. - Testing at FSL and NGIT has been completed. - Software has been checked into FSL’s OB6 CMS. - Phase I test plan has been started; due early Jan.

23. Phase II Development Requirement: develop and test software that processes all event codes. Status: - Software development and testing has started. - Software will be checked into OB6 CMS early Jan.