1 / 22

HazCollect Project AWIPS Critical Design Review

Outline. System Design OverviewAWIPS System InterfacesAWIPS Software DesignSoftware Development StatusTesting. 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 header

zivanka
Télécharger la présentation

HazCollect Project AWIPS Critical Design Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    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

    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.

    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?

    13. Warning Products: From SBN to Text DB

    14. Automated Dissemination of Hazard Products

    15. Hazard Warning Dissemination: Current / Backup Design

    16. Automated and Backup Modes

    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

    19. Issues / Notes

    20. Issues / Notes

    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 FSLs 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.

More Related