**Concept of Operations**

**and**

**Operational Requirements**

# Public Observation Program

**OSIP Number 08-011**

August 25, 2008

**Table of Contents**

**Page**

[**Revision History** 3](#__RefHeading___Toc191892729)

[**Reference Documents** 3](#__RefHeading___Toc191892730)

[**Acronyms and Abbreviations Used in This Document**
3](#__RefHeading___Toc191892731)

[**1.0** **INTRODUCTION** 4](#__RefHeading___Toc191892732)

[**2.0** **CURRENT STATE OF OPERATIONS**
4](#__RefHeading___Toc191892733)

[**3.0** **PROPOSED CONCEPT OF OPERATIONS**
5](#__RefHeading___Toc191892734)

[**4.0** **OPERATIONAL SCENARIOS** 6](#__RefHeading___Toc191892735)

[**5.0** **SUMMARY OF IMPACTS** 6](#__RefHeading___Toc191892736)

[**6.0** **ANALYSIS** 7](#__RefHeading___Toc191892737)

[**7.0** **REQUIREMENTS DEVELOPMENT** 8](#__RefHeading___Toc191892738)

[**8.0** **OPERATIONAL REQUIREMENTS** 8](#__RefHeading___Toc191892739)

**Revision History**[]{#__RefHeading___Toc191892729 .anchor}**:**

  --------------------------------------------------------------------------
  Date      Version   Description                        Name
  --------- --------- ---------------------------------- -------------------
                                                         

                                                         

                                                         

                                                         

                                                         
  --------------------------------------------------------------------------

**Reference Documents**[]{#__RefHeading___Toc191892730 .anchor}**:**

  -----------------------------------------------------------------------
  Document Title                       Date or    Author
                                       Version    
  ------------------------------------ ---------- -----------------------
                                                  

                                                  

                                                  

                                                  

                                                  
  -----------------------------------------------------------------------

**Acronyms and Abbreviations Used in This
Document**[]{#__RefHeading___Toc191892731 .anchor}**:**

  ----------------- -----------------------------------------------------
  Acronym           Description

                    

                    

                    

                    

                    
  ----------------- -----------------------------------------------------

**1.0 INTRODUCTION**[]{#__RefHeading___Toc191892732 .anchor}

Considerable resources are dedicated in each WFO to search for reports
of hazardous weather during and after events to validate the watch,
warning and advisory process. The goal in every WFO is to get as many
reports during severe weather to come in unsolicited so WFO resources
can be focused on the warning and processes. Only a limited segment of
the population has been engaged by the NWS in the reporting of severe
weather: Emergency manager, spotters and those called by the WFO. As
hazardous weather often occurs over small, or in sparsely populated
areas, the quick flow of information can be greatly impeded as this
limited segment of the population has to have experienced it or become
aware of it. If any citizen could call in immediately, the awareness of
severe weather experienced can be dramatically increased. For example,
truckers and marine users are often in these types of locations and this
would facilitate the ability of them to provide feedback without having
to know which WFO they are in and how to get in contact with that WFO.

If these reports of hazardous weather could be increased without using
resources that could otherwise be used in the warning process, more
efficient and effective operations could be run during hazardous weather
events. Being able to engage every citizen, rather then just spotter and
emergency manager resources, for preliminary reports would result in an
increase in information to the warning decision makers.

The Public Observations Program (POP) is already meeting this need in a
large section the NWS ER. The POP consists of an automated phone system,
an 800 #, for the general public to report hazardous weather using their
zip code (for user simplicity) or the latitude and longitude of the
observed event. The caller is stepped through questions and the caller
can also leave a voice message to provide supplemental information.

> Not sure if moredetail is needed in this section such as a brief
> discussion of:
>
> \~Severe reports alerted and plotted on map (i.e. CWA, regional)
>
> \~LSR generated and displayed for QC, editing if necessary, and
> transmission
>
> \~Upon receipt, calls immediately sent to appropriate users (i.e. WFO,
> Regional Office)
>
> \~NWR specific LSR created for each transmitter

**2.0 CURRENT STATE OF OPERATIONS**[]{#__RefHeading___Toc191892733
.anchor}

\[Describe the system or situation as it currently exists. [Provide a
simple and clear description of the existing system]{.underline} in user
terminology, including: operational environment; major components;
interfaces; capabilities, functions and features; inputs, outputs and
data flows from a users perspective; cost of operations; operational
risk factors; performance characteristics such as speed, throughput,
volume and frequency, quality attributes; safety, security, privacy, and
continuity of operations in emergencies; modes of operation; user
classes and involved personnel; support environment. Include a
description of operational policies and constraints that apply to the
current situation or system. If there is no current system, describe the
situation that motivates development of the proposed system.

[Describe the reasons for the desired changes and improvements,
including a description of the problem and existing system
shortcomings]{.underline} to enable the reader to understand the reasons
for the changes and improvements. Discuss the desired changes and any
assumptions and constraints.\]

**DEBBIE, I'M THINKING FIRST WE COULD PROVIDE A HIGH-LEVEL (BIG PICTURE)
DESCRIPTION OF THE NUMBER OF COMPUTERS, WRITTEN IN MICROSOFT VISUAL
BASIC, AND CURRENT COVERAGE AREA OF POP. THEN, WE COULD EXPLAIN HOW THE
USER CALLS INTO THIS AUTOMATED SYSTEM AND WHAT HAPPENS TO THE REPORT
(E.G., FORWARDED TO APPROPRIATE OFFICE IN THE FORM OF EITHER AN AWIPS
TEXT PRODUCT AND/OR DISPLAYED USING A WINDOWS PC SOFTWARE PACKAGE). ONE
OR TWO OF THE SLIDES COULD BE INCLUDED SINCE THEY ARE VERY
INFORMATIVE.**

ER funds 8 phone lines and 2 computers are used. This provides coverage
to a large part of the NWS Eastern Region (ER). POP doesn't provide
coverage to highly populated areas, such as the New York City
Metropolitan area (WFO OKX). One computer is hosted at WFO Charleston,
West Virginia (RLX) while the other is hosted at WFO Portland-Gray,
Maine (GYX).

The general public call reports of weather hazards into a national 800
number. A log of the call is created on one of the two computers. The
report is forwarded from one of the two computers to the WFO within
whose area of responsibilty the phenomenon occurred. The report is
received at the WFO in the form of an AWIPS text product and/or
displayed using a Windows PC software package (POP). Forecasters can
quality control the reports before they are sent directly to AWIPS.
Multiple reports can be combined into a single Local Storm Report
(LSR)/Public Information Statement (PNS). NOAA Weather Radio (NWR)
transmitter-specific radio text can be created and sent to the Console
Replacement System (CRS).

ER will not fund this project anymore. POP is only available in parts of
ER but all regions are very interested in implementing this phone
system.

**3.0 PROPOSED CONCEPT OF OPERATIONS**[]{#__RefHeading___Toc191892734
.anchor}

**\[**Describe the proposed system that results from the desired changes
specified in Section 2.0. [Provide a simple and clear description of the
proposed system]{.underline} in user terminology, including: operational
environment; major components; interfaces; capabilities, functions and
features; inputs, outputs, and data flows from a users perspective; cost
of operations, operational risk factors; performance characteristics
such as speed, throughput, volume and frequency; quality attributes;
safety, security, privacy, and continuity of operations in emergencies;
modes of operation; user classes; involved personnel; support
environment.

The level of detail should be sufficient to fully explain how the
proposed system is envisioned to operate in fulfilling user's needs
without including design specifications. Include a description of
operational policies that apply to the proposed system and identified
assumptions and constraints.

[Describe the benefits and advantages of the proposed]{.underline}
concept to enable the reader to understand the reasons for the changes
and improvements. Describe changes that were considered but not
included. If change to an aspect of the current system is not necessary
or desired, state that no change is required.\]

Expand to all parts of ER and to all of the other five regions. Increase
to 3 computers and 12 phone lines. Assumption is there will rarely be
more than one extreme weather event occurring in the nation so one
additional computer, which will provide 4 extra phone lines, will
suffice. Also, if one computer is inoperable for maintenance or due to
unexpected failure, the remaining two computers will suffice for the
time being. The maintenance and repair of the computers and related
software will be performed by?

**4.0 OPERATIONAL SCENARIOS**[]{#__RefHeading___Toc191892735 .anchor}

\[Develop a step by step description of how the proposed system should
operate and interact with its users and its external interfaces under a
given set of circumstances. Scenarios allow readers to gain an
understanding of how all the various parts of the proposed system
function and interact to provide operational capabilities. Scenarios can
be presented in several ways: a) Specify scenarios for each major
processing function, b) Specify thread-based scenarios where one
transaction type is followed from beginning to end, and c) Follow the
information flow through the system for each capability. Describe
operational scenarios for all modes and user classes identified for the
proposed system. Note that technical descriptions of how the system will
work are included in future design documents, not in this document.\]

Truck driver drives through thunderstorm containing very heavy rain,
hail, and strong winds. Truck driver call the 800# and reports, to an
automated system, the wx conditions and observed destruction. The POP
provides the public/caller the steps to follow when entering a report
through an automated touch tone menu. A request is made for the caller
to leave a phone number for a possible call back. The caller may also
leave a voice mail with addition details.

The report is automatically uploaded into a database and also
automatically formatted and read over the CRS.

**5.0 SUMMARY OF IMPACTS**[]{#__RefHeading___Toc191892736 .anchor}

\[Describe the anticipated operational and organizational impacts of the
proposed system

on the users, system developers, and the support and maintenance
organizations. Also

describe the temporary impacts during the period of time when the new
system is being

developed, installed, or training is being provided. This information
will allow all

affected organizations to prepare for the changes that will be brought
about by the new

system and to plan for the impacts during development and transition to
the new system. Examples of impacts to consider include: changes in
procedures, use of new data sources, changes in the quantity, type and
timing of data to be input into the system, training or retraining of
users, user involvement in reviews and testing, or parallel operation of
the new and existing systems.\]

(Examples:

Cost

Hardware Needed

Storage Needed

Maintenance

Training

Operational Impacts - WFOs will automatically access the modified model
data within AWIPS rather than using the EMC website or transferring the
data using LDAD.

Technical Impacts --

1 - The models containing the modifications will need to be stored. A
fixed size (no larger than the operational version of the numerical
model shall be allocated on AWIPS for the experimental model data). No
more than three experimental model suite (NAM, GFS, RUC, SREF, WWW3,
GEFS, etc.) will be avialble through the client-server at any one time.
This extra storage space will only be utilized when NCEP releases
updates to fields of its models.

2 -- Additional AWIPS bandwidth will be used to distribute the updated
model data to the WFOs. The exact form of the AWIPS 2.0 client --server
network configuration will be determined as part of the AWIPS2.0
enhancement process. An AWIPS RC will be submitted to perform an
analysis of the amount of additional WAN/SBN volume this proposed
project will use. --Will both SBN and WAN be affected?

Organizational Impacts -- None

Transitional Impacts -- The modified model fields will be analyzed and
manipulated like other NCEP model data available in AWIPS. Training will
not be required by NSTEP. NCEP may chose to provide some limited
training or familiarization of the new fields to help facilitate the
evaluation)

**6.0 ANALYSIS**[]{#__RefHeading___Toc191892737 .anchor}

\[Provide a qualitative (and to the extent possible, quantitative)
analysis of the benefits, advantages, limitations, and disadvantages of
the proposed concept. Benefits and advantages include new capabilities,
enhanced capabilities, deleted capabilities, and improved performance as
they relate to the deficiencies of the current system. Limitations and
disadvantages include features desired by users but not included,
degradation of existing capabilities to gain new capabilities, the need
to retrain personnel, a change to a new style interface, etc. Also
describe major alternatives considered, the trade-offs among them, and
the rationale for the decisions reached. Alternatives are operational
alternatives, not design alternatives.\]

**7.0 REQUIREMENTS DEVELOPMENT**[]{#__RefHeading___Toc191892738 .anchor}

The IWT Leader and OSIP analyst brainstormed to develop the operational
requirements. The requirements were reviewed and commented on by the IWT
members.

**8.0 OPERATIONAL REQUIREMENTS**[]{#__RefHeading___Toc191892739 .anchor}

\[Document the operating capabilities (fundamental requirements of the
system which represent the features or functions of the system needed by
the user), conditions (further qualify the capability and provide
attributes that allow a requirement to be validated and verified), and
constraints (requirements imposed on the solution by circumstance) of
the proposed system from the user's perspective in Table 1, Operational
Requirements.

Note that every category listed in the table may not apply. The goal is
to document all operational requirements, ensure that each requirement
is stated once, and ensure none are missed. [Write each requirement as a
concise, verifiable, stand-alone statement]{.underline} and assign a
unique identification number to each requirement.

Document the requirement owner, priority, and verification method. The
owner is the stakeholder office, user class/group or service area
stating the need for the requirement. The owner understands the
operational concept that drove the requirement and has the domain
knowledge to consider the impact of changes to the requirement. An
approach and definitions for priority level and verification method
assignments is provided in the keys on Table 1, Operational
Requirements.\]

**Table 1. OPERATIONAL REQUIREMENTS**

+------+----------------------------------+-----+------+-----+-------+
| **   | **Statement of Requirement**     | **  | *    | **P | **Ve  |
| ID** |                                  | Ver | *Own | rio | rific |
|      |                                  | sio | er** | rit | ation |
| **   |                                  | n** |      | y** | Met   |
| Numb |                                  |     |      |     | hod** |
| er** |                                  |     |      | **L |       |
|      |                                  |     |      | eve |       |
|      |                                  |     |      | l** |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **Operational**                  |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The POP** **system shall**     |     | NWS  | H   | Test  |
| .1** | **enable** **reporting** **of    |     | Reg  | igh |       |
|      | hazardous weather using one toll |     | ions |     |       |
|      | free number for nationwide       |     |      |     |       |
|      | access (i.e., 1-877-633-6772).   |     |      |     |       |
|      | [Alan, ]{.underline}** **[AR,    |     |      |     |       |
|      | PR,]{.underline}** **[Puerto     |     |      |     |       |
|      | Rico and GUAM                    |     |      |     |       |
|      | ALSO?]{.underline}**             |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **The POP system shall           |     |      |     |       |
|      | accommodate at least 12          |     |      |     |       |
|      | simultaneous phone calls.**      |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale:**                   |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The POP system shall have      |     | NWS  | H   | Test  |
| .2** | redundant** **"Hosts" located in |     | Reg  | igh |       |
|      | different parts of the           |     | ions |     |       |
|      | country.**                       |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: In order to ensure  |     |      |     |       |
|      | continuity of operations in the  |     |      |     |       |
|      | event of equipment or**          |     |      |     |       |
|      | **communications                 |     |      |     |       |
|      | infrastructure** **failure, and  |     |      |     |       |
|      | to distribute the volume of      |     |      |     |       |
|      | calls.**                         |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **Each of the** **host systems   |     | NWS  | H   | Test  |
| *1.2 | shall contain** **re-direct      |     | Reg  | igh |       |
| .1** | calls to one of the other        |     | ions |     |       |
|      | systems when the maximum number  |     |      |     |       |
|      | of calls for the system is       |     |      |     |       |
|      | reached.**                       |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **If any "host" system fails,    |     | NWS  | H   | Test  |
| *1.2 | the other** **systems shall      |     | Reg  | igh |       |
| .2** | remain operational.**            |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall automatically |     | NWS  | H   | Test  |
| .3** | prompt the user for information  |     | Reg  | igh |       |
|      | concerning the hazardous         |     | ions |     |       |
|      | weather.**                       |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The POP system shall play an   |     |      |     |       |
| *1.3 | automated message upon answering |     |      |     |       |
| .1** | a call.**                        |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: callers will have   |     |      |     |       |
|      | assurance that they have reached |     |      |     |       |
|      | the correct number, a message    |     |      |     |       |
|      | such as "This is the National    |     |      |     |       |
|      | Weather Service Public           |     |      |     |       |
|      | Observation Program for          |     |      |     |       |
|      | reporting of hazardous           |     |      |     |       |
|      | weather...."**                   |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The POP system shall prompt    |     |      |     |       |
| *1.3 | the caller for options for       |     |      |     |       |
| .2** | identification of their          |     |      |     |       |
|      | location**                       |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: Depending of the    |     |      |     |       |
|      | caller, they may have**          |     |      |     |       |
|      | **limited** **information on     |     |      |     |       |
|      | their location. Prompt shall     |     |      |     |       |
|      | include identification of        |     |      |     |       |
|      | location by; Zip code,**         |     |      |     |       |
|      | **latitude and** **longitude,    |     |      |     |       |
|      | or** **voice message of**        |     |      |     |       |
|      | **major** **roads or nearby      |     |      |     |       |
|      | intersection.**                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall prompt the    |     | NWS  | H   | Test  |
| .3.2 | user for** **the zip code of the |     | Reg  | igh |       |
| .3** | location where the hazard was    |     | ions |     |       |
|      | observed.**                      |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user for the latitude and        |     | Reg  | igh |       |
| .2** | longitude of the location where  |     | ions |     |       |
|      | the hazard was observed.**       |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall use caller ID |     | NWS  | H   | Test  |
| *1.3 | technology to identify the user, |     | Reg  | igh |       |
| .3** | in the event that the number is  |     | ions |     |       |
|      | not available, the system        |     |      |     |       |
|      | shall** **prompt the user to     |     |      |     |       |
|      | enter a phone number.**          |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: Forecasters may     |     |      |     |       |
|      | decide to telephone the          |     |      |     |       |
|      | user/caller in order to obtain   |     |      |     |       |
|      | additional information about a   |     |      |     |       |
|      | reported event.**                |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **The POP system shall provide   |     |      |     |       |
|      | prompts to select the type of    |     |      |     |       |
|      | hazardous weather event being    |     |      |     |       |
|      | reported.**                      |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user to** **report**             |     | Reg  | igh |       |
| .4** | **tornadoes.**                   |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user to report wind damage.**    |     | Reg  | igh |       |
| .5** |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user** **to** **report hail.**   |     | Reg  | igh |       |
| .6** |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user to** **report flooding.**   |     | Reg  | igh |       |
| .7** |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user to** **report snow.**       |     | Reg  | igh |       |
| .8** |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall prompt the    |     | NWS  | H   | Test  |
| *1.3 | user** **to** **report sleet.**  |     | Reg  | igh |       |
| .9** |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **   | **The system shall prompt the    |     | NWS  | H   | Test  |
| 1.3. | user** **to report** **freezing  |     | Reg  | igh |       |
| 10** | rain.**                          |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **[ALAN, ARE THERE ANY OTHER     |     |      |     |       |
|      | HAZARDS THAT NEED TO BE ADDED TO |     |      |     |       |
|      | THIS GROUP?]{.underline}**       |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **   | **The system shall prompt**      |     | NWS  | H   | Test  |
| 1.3. | **the user to leave a voice      |     | Reg  | igh |       |
| 11** | message.**                       |     | ions |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: This will provide   |     |      |     |       |
|      | an opportunity to gather         |     |      |     |       |
|      | additional detail and            |     |      |     |       |
|      | information on the nature of the |     |      |     |       |
|      | report**                         |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **The POP system shall limit**   |     |      |     |       |
|      | **each** **voice recorded        |     |      |     |       |
|      | messages to two minutes.**       |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: This is**           |     |      |     |       |
|      | **expected** **to be sufficient  |     |      |     |       |
|      | time for an explanation and yet  |     |      |     |       |
|      | not take up too much 'storage'   |     |      |     |       |
|      | space.**                         |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall obtain the    |     | NWS  | H   | Test  |
| .4** | users' responses** **via         |     | Reg  | igh |       |
|      | telephone touch tone**           |     | ions |     |       |
|      | **signals.**                     |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Assumption: The prototype      |     |      |     |       |
|      | system will be used, which       |     |      |     |       |
|      | accepts touch tone input, other  |     |      |     |       |
|      | options, such as voice are       |     |      |     |       |
|      | acceptable if available.**       |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The** **POP system shall       |     | NWS  | H   | Test  |
| .5** | accept all the necessary input   |     | Reg  | igh |       |
|      | within a** **maximum length**    |     | ions |     |       |
|      | **of three minutes.**            |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **Rationale: If the system takes |     |      |     |       |
|      | too long to prompt and record    |     |      |     |       |
|      | the results, the caller may give |     |      |     |       |
|      | up,** **and** **the chance of    |     |      |     |       |
|      | the call being dropped is        |     |      |     |       |
|      | higher** **if longer times are   |     |      |     |       |
|      | required.**                      |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **The** **POP** **system shall** |     |      |     |       |
|      | **provide reports to the WFO     |     |      |     |       |
|      | whose area of responsibility is  |     |      |     |       |
|      | in the location identified**     |     |      |     |       |
|      | **by the caller in requirement   |     |      |     |       |
|      | 1.3.2.**                         |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **Upon receipt of the hazardous  |     | NWS  | H   | Test  |
| .6** | weather report, the system shall |     | Reg  | igh |       |
|      | send the report to the WFO       |     | ions |     |       |
|      | within whose area of             |     |      |     |       |
|      | responsibility the hazardous     |     |      |     |       |
|      | weather occurred.**              |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The** **hazardous weather      |     | NWS  | H   | Test  |
| *1.6 | report shall be sent** **as an   |     | Reg  | igh |       |
| .1** | AWIPS text product.**            |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **Upon receipt of the hazardous  |     | NWS  | H   | Test  |
| .7** | weather report, the system shall |     | Reg  | igh |       |
|      | send the report to the NWS       |     | ions |     |       |
|      | regional headquarter within      |     |      |     |       |
|      | whose jusisdiction the hazardous |     |      |     |       |
|      | weather occurred.**              |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The hazardous weather report   |     | NWS  | H   | Test  |
| *1.7 | shall be sent as an AWIPS text   |     | Reg  | igh |       |
| .1** | product.**                       |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | **The hazardous weather          |     | NWS  | H   | Test  |
|      | reportshall begin** **with these |     | Reg  | igh |       |
|      | sentences:**                     |     | ions |     |       |
|      |                                  |     |      |     |       |
|      | **"\*\*\*WARNING\*\*\*THIS       |     |      |     |       |
|      | REPORT HAS NOT BEEN QUALITY      |     |      |     |       |
|      | CONTROLLED\*\*\***               |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **\<The site of the server that  |     |      |     |       |
|      | received the hazardous weather   |     |      |     |       |
|      | report (e.g., CHARLESTON, WV)\>  |     |      |     |       |
|      | JUST RECEIVED THIS STORM REPORT  |     |      |     |       |
|      | FROM THE GENERAL PUBLIC ON OUR   |     |      |     |       |
|      | AUTOMATED** **REPORTING**        |     |      |     |       |
|      | **SYSTEM** **(POP). THIS REPORT  |     |      |     |       |
|      | HAS NOT BEEN CHECKED FOR         |     |      |     |       |
|      | ACCURACY...BUT HAS BEEN          |     |      |     |       |
|      | AUTOMATICALLY FORMATTED TO       |     |      |     |       |
|      | YOU.**                           |     |      |     |       |
|      |                                  |     |      |     |       |
|      | **THIS REPORT IS ALREADY IN THE  |     |      |     |       |
|      | LSR FORMAT."**                   |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **A preliminary Local Storm      |     | NWS  | H   | Test  |
| *1.7 | Report shall follow for the WFO  |     | Reg  | igh |       |
| .2** | within whose area of             |     | ions |     |       |
|      | responsibility the hazardous     |     |      |     |       |
|      | weather occurred. An example of  |     |      |     |       |
|      | a hazardous weather report is    |     |      |     |       |
|      | provided in Attachment 1         |     |      |     |       |
|      | below.**                         |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall provide an    |     | NWS  | H   | Test  |
| .8** | alert sound (or is it "provide   |     | Reg  | igh |       |
|      | an alert message?") upon receipt |     | ions |     |       |
|      | of the hazardous weather report  |     |      |     |       |
|      | at the NWS regional              |     |      |     |       |
|      | headquarter's pc.**              |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall provide an    |     | NWS  | H   | Test  |
| *1.8 | alert sound (or is it "provide   |     | Reg  | igh |       |
| .1** | an alert message?") upon receipt |     | ions |     |       |
|      | of the hazardous weather report  |     |      |     |       |
|      | at the** **WFO.**                |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall plot the      |     | NWS  | H   | Test  |
| .9** | hazardous weather report upon    |     | Reg  | igh |       |
|      | receipt of the hazardous weather |     | ions |     |       |
|      | report at the WFO.**             |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The plotted hazardous weather  |     | NWS  | H   | Test  |
| *1.9 | report shall be displayable on   |     | Reg  | igh |       |
| .1** | the WFO's PC.**                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall plot the      |     | NWS  | H   | Test  |
| *1.9 | hazardous weather report upon    |     | Reg  | igh |       |
| .2** | receipt of the hazardous weather |     | ions |     |       |
|      | report at the NWS regional       |     |      |     |       |
|      | headquarter.**                   |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The plotted hazardous weather  |     | NWS  | H   | Test  |
| .9.2 | report shall be displayable on   |     | Reg  | igh |       |
| .1** | the NWS regional headquarter's   |     | ions |     |       |
|      | PC.**                            |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| *    | **The system shall provide the   |     | NWS  | H   | Test  |
| *1.9 | forecaster the** **option to     |     | Reg  | igh |       |
| .3** | delete the** **plotted hazardous |     | ions |     |       |
|      | weather report.**                |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall automatically |     |      |     |       |
| .9.3 | create a draft** **single,**     |     |      |     |       |
| .1** | **Local Storm Report containing  |     |      |     |       |
|      | only the current hazardous       |     |      |     |       |
|      | weather report.**                |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall provide the   |     | NWS  | H   | Test  |
| .9.3 | forecaster the option to send    |     | Reg  | igh |       |
| .2** | the hazardous weather report**   |     | ions |     |       |
|      | **as a single Local Storm        |     |      |     |       |
|      | Report.**                        |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall provide the   |     | NWS  | H   | Test  |
| .9.3 | forecaster the option to**       |     | Reg  | igh |       |
| .3** | **change the Local Storm Report  |     | ions |     |       |
|      | already containing** **the       |     |      |     |       |
|      | hazardous weather report.**      |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1  | **The system shall provide the   |     | NWS  | H   | Test  |
| .9.3 | forecaster the option to change  |     | Reg  | igh |       |
| .4** | the NOAA Radio status for the    |     | ions |     |       |
|      | single Local Storm** **Report.** |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **1. | **A log of the telephone calls   |     | NWS  | H   | Test  |
| 10** | shall be created**               |     | Reg  | igh |       |
|      |                                  |     | ions |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **2  | **Data**                         |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **3  | **System Level Interfaces**      |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **4  | **Operational Maintenance**      |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      | The POP system shall operate 24  |     |      |     |       |
|      | hours per day, 365 days a year.  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **5  | **Logistics**                    |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **6  | **Security and Privacy**         |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **7  | **Training**                     |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **8  | **Documentation**                |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **9  | **Constraints**                  |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
| **10 | **Other**                        |     |      |     |       |
| .0** |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+
|      |                                  |     |      |     |       |
+------+----------------------------------+-----+------+-----+-------+

+-----------------------------+------------+---------------------------+
| [**Priority Level**         |            | **[Verification Method    |
| **Key**:]{.underline}       |            | Key:]{.underline}**       |
+-----------------------------+------------+---------------------------+
| **High**: The requirement   |            | **Test**: The requirement |
| has the highest priority    |            | will be verified with     |
| classification in the       |            | testing.                  |
| proposed systems. It is     |            |                           |
| essential and must be met.  |            | **Demo**: The requirement |
|                             |            | will be verified by       |
| **Medium**: The requirement |            | demonstration.            |
| is important. Not meeting   |            |                           |
| this requirement would      |            | **Inspect**: The          |
| result in a [significantly  |            | requirement will be       |
| degraded]{.underline} (but  |            | verified by inspection.   |
| still useable) capability.  |            |                           |
|                             |            | **None**: None required.  |
| **Low**: If this            |            |                           |
| requirement is not met,     |            |                           |
| some capability or ease of  |            |                           |
| use would be degraded or    |            |                           |
| slightly degraded           |            |                           |
+-----------------------------+------------+---------------------------+

Attachment 1: Sample Reports

ZCZC CRWADARLX SEW

TTAA00 KCRW DDHHMM

\*\*\* **WARNING\*\*\* THIS REPORT HAS NOT BEEN QUALITY CONTROLLED
\*\*\***

**CHARLESTON, WV JUST RECEIVED THIS STORM REPORT FROM THE GENERAL PUBLIC
ON OUR AUTOMATED REPORTING SYSTEM (POP). THIS REPORT HAS NOT BEEN
CHECKED FOR ACCURACY...BUT HAS BEEN AUTOMATICALLY FORMATTED TO YOU.**

**THIS REPORT IS ALREADY IN THE LSR FORMAT FOR YOUR CONVENIENCE.**

**PRELIMINARY LOCAL STORM REPORT**

**NATIONAL WEATHER SERVICE SEATTLE WA**

**126 PM EDT TUE APR 22 2008**

**..TIME... \...EVENT... ...CITY LOCATION... ...LAT .LON...**

**. DATE... ...MAG... .. COUNTY LOCATION...ST.. ...SOURCE....**

**..REMARKS..**

**0123 PM POSSIBLE TORNADO EVERETT 47.90N122.26W**

**04/22/2008 SNOHOMISH WA PUBLIC**

**EVENT OCCURRED BETWEEN**

**108 PM 04/22/2008 AND 123 PM 04/22/2008**

**&&**

**\$\$**

**NNNN**

Fig 1. Hazardous weather report in the form of an AWIPS text product