WFO Advanced Build 4.1 Requirements
Set of requirements for FSL's portion of AWIPS Build 4.1
9 Jan 98 (revised 12 Feb)
Synopsis
The NWS plans to start removing existing systems such as AFOS, SWIS (satellite
display), and WSR-88D PUP during the AWIPS Build 4 time frame. In order
to accomplish this, AWIPS Build 4.1 must have the critical capabilities
of these systems or their functional equivalents. AWIPS Build 4.1 is a
joint development effort, with FSL, Office of Hydrology, Techniques Development
Laboratory, and PRC all contributing software; only FSL requirements are
addressed in this document. Highlights of this build are:
-
develop essential communications capabilities
-
develop additional radar processing capabilities
-
develop additional LDAD capability
Objective
Provide NWS with a reliable, highly functional system, which can be used
by forecasters and hydromet technicians to perform their duties and allow
NWS to begin removing existing systems.
Replace AFOS Comms
Message Handling System
FSL4.1-8
-
B-3: The site can acquire data that is available to it through external
interfaces with other existing systems and other AWIPS segments.
-
When the site sends a high priority product to another AWIPS site (and
the other site receives the product), the site gets an acknowledgment from
AWIPS that the product was received.
Functional Specification
AWIPS Message Handling System (X.400)
-
3.1.1 install
-
add UI
-
specify destination (distribution)
-
specify priority
-
encode/decode messages for the PRC API
-
interface to gateway message handling
-
specify destination, ID of data to send out
LDAD
FSL4.1-5
-
B-1: The site can acquire data automatically when permitted by the observation
systems
Many systems will automatically send information to designated files
on the LDAD system where they will be retrieved and processed. Examples
include microART, ALERT, ASOS, and local mesonets such as Colorado DoT.
-
B-12: The site AWIPS can automatically disseminate data to external users.
For build 4 (or 4.1) there may be an automated fax capability.
-
B-13: The site can disseminate data to external users upon their request.
A menu driven bulletin board system will be provided by which external
users may request designated products.
-
B-14: The site can specify dissemination control parameters
-
B-2: The site can request data from observation systems that accept requests
and can receive data sent in response to these requests. (LARC)
-
B-3: The site can acquire all data that is available to it through external
interfaces with other existing systems and other AWIPS segments.
The following systems will have interfaces implemented for Build 4.1:
Designated emergency management systems (UDFCD, CDoT)
Mesonet (CDoT)
ALERT
IFLOWS
LARC
Menu Users
-
E-51: The site can perform quality control checks on data acquired at the
site via LDAD interfaces listed above
Localization
FSL4.1-6
-
E-32: The site can define communication interface characteristics. (LDAD
localization)
The localization techniques should allow the selection of primary radar
site, products to acquire (e.g. western or eastern satellite sector), and
location of regional and local scales. It must also provide an override
for the default parameters generated by localization such as AFOS node.
Radar Processing
FSL4.0-9
-
C-33a: The site can create a Local Area mosaic of 4 km data from multiple
WSR-88D systems, using the following mosaic algorithms: Maximum value method.
Done
-
C-58b: The site can produce cross-section (space-height) plots of hydrometeorological
data based on site specified locations and time. (PUP xsections)
-
The appropriate information is sent to the RPG and the RPG returns a displayable
product. The module that generates the request to the RPG must ensure that
the points are within 124 nm of the radar location.
-
E-55: The site can emulate the Principal User Processor function command
and control capabilities for the NEXRAD Radar Products Generator function
as described in Reference Document 21.
Functional Specification
Display digital hybrid scan graphic
VAD
Attributes table multiload?
Remove layer composite turbulence
Modify lines to 14.4 kbps from 9.6
Change km to nmi
Add audible alarm for arrival of specified radar products
Correct display of 8 level products
Make WSR-88D precip data available to OH
Digital Precip Array on NEXRAD
AAR (automatic alert request) retransmission
Archive
FSL 4.1-1
-
D-17: The site AWIPS can automatically archive all Official User Products,
as listed in Appendix F, issued by the site and retain each product for
the most recent 31 days.
Functional Specification
Archive official user products issued by the local office. For
purposes of
this requirement, all products generated on AWIPS and disseminated
either via
the AFOS link or via the MHS shall be archived for 31 days. The
contents
should be write protected to prevent deletion or modification.
The contents
must be able to be viewed and printed at the local site.
System Enhancements
FSL4.1-12 Site Status
-
Keep site status messages for 10 days (e-1.12)
Miscellaneous
Analysis/design to integrate WHFS. A necessary first step here is
to assist
OH to implement a mechanism
which uses SBN data rather than depending
on AFOS for the data feed.
Link ProductMaker items into procedures?
Generic zones formatter
Generic TAF formatter
Manual option to decode raob and store in plotfile
Incorporate OSO tables into text processing
Revised foundation classes
W/W/A integration (TDL lead, Jim I forwarded a couple of emails to
you with
field comments on this)
ICWF support
Redbook purger rewrite
Linear least-squares algorithm for storm extrapolation in warngen
Fix specified bugs (agreed upon DR list)
-
Revise purging capability -- particularly for redbook graphics
Graphics Workstation
Schedule