HazCollect Project AWIPS Critical Design Review

MarySue Schultz

CIRA/FSL

December 8, 2004

Outline

• System Design Overview• AWIPS System Interfaces• AWIPS Software Design• Software Development Status• Testing

System Design Overview

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.

AWIPS Requirements

• Software must perform during failover.

• Software must perform during site backup

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.

HazCollect System Design

EMs DMIS

NWS Gateway

HazCollectServers

NCF

CAPformat

Converts toAWIPS WMO

format

SBN

WAN

NWWS

(primary)

NWSWFOs

CRS

transmitters

NOAA weather radios

(primary/backup)

NWWS

DMIS: Disaster Management Interoperability ServicesCAP: Common Alert ProtocolCRS: Console Replacement System

NWSTG

OB6 Hardware Configuration

NAS CP

DX1 DX2 PX1

PV PV

LX

FDDI

DS1 DS2

DX1:TextDB read/writeWarnDB DecoderSMTP MTA/MHSHazCollect Processes

Text Notification

[Text Database]

[Data Storage]

AWIPS System Interfaces

AWIPS Interfaces

• HazCollect Servers

- Warning products delivered over SBN and WAN

• CRS

- CEM Formatter

• NWWS

- WAN interface package (NGIT)

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?

AWIPS Software Design

Warning Products: From SBN to Text DB

CPAcq

ServerCommsRouter

DataController

Warn DBDecoder

Text DBWriter

Data Server (DX1) FSLSEC

Text DB

NGIT

SBN

Automated Dissemination of Hazard Products

CPSBN AcquisitionAnd Processing

Text DB

NWWS

CRS

DX1

New Code

ProductNotificationText WS

To NWWSAnd CRSWAN

D-2D

Archive

Hazard Warning Dissemination: Current / Backup Design

ForecasterInput

Text Workstation

WAN

Data Server

TextWindow

WAN Interface

Text DBWriter

Text DB

NWWS

NCF

NWR

Hazard Product

[Archive]

(Primary andBackup)

CRS

Automated and Backup Modes

NCF

SBN

WAN

NWWS

SBNIngest

WANIngest

TextDB

CRS NWR

NWWSNCF

TextDB

TextWS CRS NWR

WFO

WFO

NWWS

Automated

Backup

NWWS

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.

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

Issues / Notes

• Error handling:

- Notify D2D of any processing errors

- Attempt to send products three times

- Red banner box + audible alarm

- CEM formatter errors

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

Software Development Status

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.

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.