Number range CHAPTER

**OPERATIONAL ACCEPTANCE**

**TEST REPORT**

for the

**Console Replacement System (CRS)**

**Build 10.0**

and

**Voice Improvement Processor (VIP)**

**Build 3.1**

**November 2004**

![](media/image5.wmf){width="1.5in" height="1.5in"}

**U.S. DEPARTMENT OF COMMERCE**

**National Oceanic and Atmospheric Administration**

**National Weather Service/Office of Operational Systems**

**Field Systems Operations Center/Test and Evaluation Branch**

**(This page is blank)**

**Executive Summary**[]{#__RefHeading___Toc86026805 .anchor}

This report explains the method by which the National Weather Service
(NWS) conducted the Operational Acceptance Test (OAT) of the Console
Replacement System (CRS) Build 10.0 and the Voice Improvement Processor
(VIP) Build 3.1. The report describes the test results, Test Trouble
Reports (TTRs), and evaluation results from which conclusions were drawn
and recommendations made. The report also contains the test background,
methodology, sites, and resources used.

NWS Headquarters (WSH) engineered the CRS Build 10.0 and VIP Build 3.1
software development, integration, and testing. The Office of Operation
Systems, Field Systems Operations Center, Software Branch (OPS23)
developed the CRS software development update for Build 10.0 and VIP
software development update for Build 3.1 containing 10 software
enhancements and 16 software fixes.

The major changes to the new build included the automatic CRS and VIP
user's password checking, secure file transfers from CRS to VIP using
the Secure File Transfer Protocol (sftp), the authenticated secure shell
(ssh) key installations, and the NOAA Weather Radio Specific Area
Message Encoder (NWRSAME) DMO test event code processing.

The selected OAT sites were Weather Forecast Offices (WFO)
Philadelphia/Mt. Holly (PHI), Austin/San Antonio, TX (EWX), Northern
Indiana, IN (IWX), and San Diego, CA (SGX). The OAT began on August 9,
2004 and ended September 17, 2004. Test Review Group (TRG) meetings were
convened weekly to discuss the status of the CRS and VIP systems.

The CRS Build 10.0/VIP Build 3.1 installations required an average of
about 4 ½ hours to complete with minor problems corrected during
installations. Overall, the CRS and VIP systems at all OAT sites
performed remarkably well with no operational problems. All systems are
operational with minimal to no incidence of previously reported VIP
message conversion retries.

The OAT officially ended on September 17, 2003. At the Final OAT TRG
conference meeting held on September 16, 2004, the OAT test results
indicated the CRS Build 10.0/VIP Build 3.1 systems are operationally
stable with no system degradation.

**The CRS Build 10.0/VIP Build 3.1 OAT TRG recommends deploying the CRS
Build 10.0/VIP Build 3.1 nationally.**

**(This page is blank)**

**Table of Contents**

[Page]{.underline}

[Executive Summary iii](#__RefHeading___Toc86026805)

[Acronyms vii](#__RefHeading___Toc86026806)

[Introduction 1](#__RefHeading___Toc86026807)

[PART I: CRS Build 10.0/VIP Build 3.1 OAT Test Results and
Recommendations 2](#__RefHeading___Toc86026808)

[1.0 Installation Evaluation Results 2](#__RefHeading___Toc86026809)

[1.1 CRS Build 10.0/VIP 3.1 Software Installation
2](#__RefHeading___Toc86026810)

[1.2 Installation Time 3](#__RefHeading___Toc86026811)

[2.0 OAT Testing 3](#__RefHeading___Toc86026812)

[2.1 OAT Testing - WFO PHI 3](#__RefHeading___Toc86026813)

[2.2 OAT Testing - WFO EWX 6](#__RefHeading___Toc86026814)

[2.3 OAT Testing - WFO IWX 8](#__RefHeading___Toc86026815)

[2.4 OAT Testing - WFO SGX 9](#__RefHeading___Toc86026816)

[3.0 Test Trouble Reports 11](#__RefHeading___Toc86026817)

[4.0 Conclusions 13](#__RefHeading___Toc86026818)

[5.0 Recommendations 15](#__RefHeading___Toc86026819)

[PART II: CRS Build 10.0/VIP Build 3.1 OAT Description
16](#__RefHeading___Toc86026820)

[1.0 Background 16](#__RefHeading___Toc86026821)

[1.1 Prior Testing 16](#__RefHeading___Toc86026822)

[1.2 Test Objectives and Criteria 16](#__RefHeading___Toc86026823)

[1.3 CRS Build 10.0/VIP Build 3.1 Enhancements and Modifications under
Test 17](#__RefHeading___Toc86026824)

[1.4 Test Sites and Configurations 18](#__RefHeading___Toc86026825)

[2.0 Test Conduct 18](#__RefHeading___Toc86026826)

[2.1 Problem Documentation and Classification
19](#__RefHeading___Toc86026827)

[2.2 Test Personnel 19](#__RefHeading___Toc86026828)

[2.3 Test Schedule 20](#__RefHeading___Toc86026829)

**Tables**

[Page]{.underline}

[Table 1 - Installation Information Summary
2](#__RefHeading___Toc82480368)

[Table 2 - TTRs from the CRS Build 10.0/VIP Build 3.1 OAT
12](#__RefHeading___Toc82480369)

[Table 3 - CRS Build 10.0/VIP Build 3.1 OAT Test Sites and
Configurations 18](#__RefHeading___Toc82480370)

[Table 4 - CRS Build 10.0/VIP Build 3.1 OAT Test Personnel
20](#__RefHeading___Toc82480371)

**Attachments**

[Page]{.underline}

[Attachment A - CRS Build 10.0/VIP Build 3.1 Test Review Group
A-1](#__RefHeading___Toc82480377)

[Attachment B - CRS Build 10.0/VIP 3.1 OAT Installation Test Site
Comments and Recommendations B-1](#__RefHeading___Toc82480378)

[Attachment C - CRS Build 10.0/VIP Build 3.1 OAT Test Trouble Reports
C-1](#__RefHeading___Toc82480379)

[Attachment D - CRS Build 10.0/VIP 3.1 OAT Questionnaires
D-1](#__RefHeading___Toc82480380)

[Attachment E - CRS Build 10.0/VIP 3.1 Release Notes
E-1](#__RefHeading___Toc82480381)

**Acronyms**[]{#__RefHeading___Toc86026806 .anchor}

  ------------ ----------------------------------------------------------
  ACP          Audio Control Panel

  ASCII        American Standard Code for Information Interchange

  AWIPS        Advanced Weather Interactive Processing System

  CCB          Change Control Board

  CP_VC        Communications Processing Voice Conversion

  CRS          Console Replacement System

  EAS          Emergency Alert System

  ECR          Engineering Change Request

  EO           Emergency Override

  FEP          Front End Processor

  FTP          File Transfer Protocol

  IVR          Interactive Voice Response

  MIC          Meteorologist In Charge

  MP           Main Processor

  MP3          MPEG-2 Layer 3

  MPEG         Moving Pictures Expert Group

  MU           Monitoring Unit

  NOAA         National Oceanic and Atmospheric Administration

  NWR          NOAA Weather Radio

  NWRSAME      NOAA Weather Radio Specific Area Message Encoder

  NWS          National Weather Service

  OAT          Operational Acceptance Test

  OPS23        Office of Operation Systems, Field Systems Operations
               Center, Software Branch

  OPS24        Office of Operational Systems, Field Systems Operations
               Center, Test and Evaluation Branch

  ROAMS        Remote Off-Air Monitoring System

  RWT          Routine Weekly Test

  SOM          System Operators Manual

  SFTP         Secure File Transfer Protocol

  ST           System Test

  SSH          Secure Shell

  SSHD         Secure Shell Daemon

  TRG          Test Review Group

  TTR          Test Trouble Report

  UGC          Universal Generic Code

  VIP          Voice Improvement Processor

  WAV          Waveform audio

  WFO          Weather Forecast Office

  WSH          Weather Service Headquarters
  ------------ ----------------------------------------------------------

**(This page is blank)**

**Introduction**[]{#__RefHeading___Toc86026807 .anchor}

This report explains the results of the National Weather Service (NWS)
Operational Acceptance Test (OAT) of the NOAA Weather Radio Console
Replacement System (CRS) Build 10.0/VIP Build 3.1 Voice Improvement
Processor (VIP) Build 3.1. This report is organized into two parts: the
OAT results and recommendations (Part I), and the background and
methodology details (Part II).

-   Part I presents the OAT results documented in the Test Trouble
    Reports (TTRs) and OAT evaluation forms completed by the OAT site
    personnel. The OAT Conclusions and Recommendations are also in Part
    I, in Sections 4 and 5 respectively.

-   Part II presents the test objectives, test conduct, evaluation
    criteria, test sites, personnel, resources, responsibilities, and
    test schedules for these field tests.

A total of four Weather Forecast Office (WFO) sites (see Table 3 for
sites and configurations) conducted the OAT. The WFO Philadelphia, PA
(PHI) installed the CRS Build 10.0/VIP Build 3.1 software on August 9,
2004 and the WFO San Antonio, TX (EWX) started their installation on
August 10, 2004. Both sites at WFO Northern Indiana (IWX) and WFO San
Diego, CA (SGX) started their installations on August 17, 2004. The OAT
concluded for all sites on September 17, 2004.

An OAT Test Review Group (TRG, see Attachment A) met during weekly
conference calls to coordinate issues, review activities, and classify
problems identified during the OAT. The TRG members also reviewed the
draft of this CRS Build 10.0/VIP Build 3.1 OAT Report. The report
contains the TRG's recommendation for national implementation of the CRS
Build 10.0/VIP Build 3.1.

The purpose of the OAT was to have National Weather Service (NWS) field
personnel evaluate CRS Build 10.0/VIP Build 3.1, including installation,
documentation, and system operation for at least a 30-day period. The
evaluation verified the CRS Build 10.0/VIP Build 3.1 software usability
and system stability during operational use in an NWS office. This
evaluation provides information for NWS management to use in making the
decision for national deployment of CRS Build 10.0/VIP Build 3.1.

**PART I: CRS Build 10.0/VIP Build 3.1 OAT Test Results and
Recommendations**[]{#__RefHeading___Toc86026808 .anchor}

Part I presents the OAT test results which the TRG will assess and
evaluate based on the data gathered during the OAT. Section 1 presents
the CRS Build 10.0/VIP Build 3.1 installation process and documentation
evaluation. Section 2 presents the OAT site test activities during the
OAT. Section 3 contains the summarized list of TTRs documenting any CRS
or VIP problems. Section 4 contains a verification of the original CRS
and VIP objectives that were included in the CRS Build 10.0/VIP Build
3.1 OAT Test Plan and whether these objectives have been met. In Section
5, conclusions are drawn from the presented data and a recommendation is
made based on those conclusions.

**1.0 Installation Evaluation Results**[]{#__RefHeading___Toc86026809
.anchor}

The OAT gathered information on two major installation activities: the
CRS Build 10.0 and the VIP Build 3.1 software installations. For the
four OAT sites, the delivered software was actually CRS Build 9.93/VIP
Build 3.0.6; the nationally deployed versions will be officially named
CRS Build 10.0/VIP Build 3.1. At all four OAT test sites (WFO PHI, WFO
EWX, WFO IWX, and WFO SGX), the site Electronic System's Analysts (ESA),
electronic technicians, and CRS focal points loaded the new CRS and VIP
software by following instructions in the EHB-7 Software Note 6
document. Table 1 summarizes the OAT site installation.

  ---------------------------------- --------- --------- --------- ---------
  []{#__RefHeading___Toc82480368                                   
  .anchor}Table 1 - Installation                                   
  Information Summary                                              

  **Questions**                      **PHI**   **EWX**   **IWX**   **SGX**

  Were the CRS Build 10.0 and VIP    Yes       Yes       Yes       Yes
  Build 3.1 software successfully                                  
  installed and configured?                                        

  Was assistance from outside the    No        No        No        No
  office required to complete the                                  
  CRS Build 10.0 and VIP 3.1                                       
  replacement?                                                     

  How long did the CRS Build 10.0    4 ½ hrs   5 hrs     3 ½ hrs   4 ½ hrs
  and VIP Build 3.1 installation                                   
  take?[^1]                                                        

  Was VIP remote sftp part of the    Yes       No        Yes       Yes
  installation?                                                    
  ---------------------------------- --------- --------- --------- ---------

**1.1 CRS Build 10.0/VIP Build 3.1 Software
Installation**[]{#__RefHeading___Toc86026810 .anchor}

The CRS Build 10.0/VIP Build 3.1 software installation at WFO PHI went
smoothly but the OAT test personnel (see Table 4) had to update some
procedures in the EHB-7 Software Note 6 document. These updates included
an additional reboot after setting up the system passwords and before
starting the authenticated ssh key installations. Other changes included
the more restrictive FEP password settings, the "su -- crs" hang up
workaround, and the floppy unmount workaround. These recommended updates
are noted in Attachment B.

The software installation at the WFO EWX was also successful. A bad VIP
Restore #6 CD was detected and a personal copy of the same restore CD
was used instead. The installation proceeded to finish without any
further problems.

For both WFO IWX and WFO SGX, the software installations were
successfully performed without any problems.

[Recommendation:]{.underline} Revise the EHB-7 Software Note 6
installation instructions to include the corrections and recommendations
contained in Attachment B.

**1.2 Installation Time**[]{#__RefHeading___Toc86026811 .anchor}

The software installation for all four OAT sites averaged around 4 ½
hours. Some of the installations took longer due to configurations that
involved more Front End Processors (FEPs). If a site has more than two
FEPs in its configuration, then there are extra steps and time to
perform password changing, and hence the longer installation time. For
example, the WFO IWX only has four transmitters; this meant only having
two processors to work with -- one for 1FEP processor and the other for
the 4BKUP processor. Subsequently, the WFO IWX installation time only
took 3 ½ hours (see Table 1). See Table 3 for the different OAT site
transmitter configurations.

The WFO EWX installation took around 5 hours, even without having to set
up the VIP remote sftp function, due to a bad VIP Restore CD #6. A
personal copy, from one of the test team members, of the same Restore CD
was used and the restore install steps were repeated without any further
problems.

[Recommendation:]{.underline} None. The EHB-7 Software Note 6
recommended six hours of installation. This estimate is a conservative
estimate and should allow for unexpected hang-ups and/or repetition of
installation due to bad installation CDs.

**2.0 OAT Testing**[]{#__RefHeading___Toc86026812 .anchor}

The OAT Testing started on August 9, 2004 for the WFO PHI, August 10^th^
for WFO EWX, and August 17^th^ for both WFO IWX and WFO SGX. During the
first week of OAT testing, WSH personnel (see Table 4) were on-site to
support the OAT site personnel during scheduled and routine weekly
tests. The OAT officially ended on September 17, 2004. **The individual
OAT site assessments and evaluations, including installation and system
performance, are documented in Attachment D**.

**2.1 OAT Testing - WFO PHI**[]{#__RefHeading___Toc86026813 .anchor}

On August 9, 2004, the WFO PHI started their installation of the CRS
Build 10.0/VIP Build 3.1 from 9:00 AM to 1:30 PM. The CRS and VIP
software installation went well, including the authenticated **ssh**
keys and the VIP remote sftp functionality for the OAT site Interactive
Voice Response (IVR) phone system. However, the OAT test team did
encounter a few problems during installation:

a.  An additional reboot was performed directly after the setting of
    system passwords and before the creation and installation of the
    authenticated ssh keys. This extra reboot was needed to correctly
    start the secure shell daemon (sshd) which is required for the ssh
    to function properly. This reboot has been recommended for addition
    as Section 8.4 to the EHB-7 Software Note 6 document (see Attachment
    B).

b.  The password checking for the CRS Front-End processors (FEP) was
    more restrictive. A number and two alpha characters must be included
    in the first eight characters of a given password. This information
    has been recommended for addition to the EHB-7 Software Note 6
    document (see Attachment B).

c.  During the setting of passwords in the VIP, a "su -- crs" command
    was performed in order to switch the current user to "crs". This
    command caused a hang-up of the Linux shell window. This problem was
    also verified during pre-OAT activities at the WSH test lab. A
    workaround, generated by OPS23, was to open another Linux shell
    window and to enter the command "killall stty --s 9; exit
    \<Return\>". This workaround was applied, and the previous shell
    hang-up was terminated. The shell prompt also properly returned with
    "crs" as the current user. This workaround has been recommended for
    addition to the EHB-7 Software Note 6 document (see Attachment B).

d.  During the storing of the VIP dictionaries to a floppy disk, an
    error message was displayed to the operator indicating an inability
    to mount the new floppy diskette. A Linux shell window was opened
    and the command "umount /mnt/floppy" was executed to manually
    unmount the floppy diskette. This caused the floppy diskette to
    properly unmount and the dictionary storing procedures were repeated
    without any problems. This workaround has been recommended for
    addition to the EHB-7 Software Note 6 document (see Attachment B).

The network was also checked for errors which might compromise the ssh
connectivity and/or cause VIP message conversion retries. The network
command, "netstat --I net0 --w 10" yielded few cumulative errors and no
dynamic errors. The network was deemed working normally and did not
impact the ssh connectivity or caused VIP message conversion retries.
The LAN server password setting was skipped due to a currently unknown
password.

The VIP remote sftp functionality was properly performed with a few
updates and/or additional steps:

a.  The SAMBA software package, which is available on the LDAD server
    (LS1), was setup on LS1 to map the LS1 incoming directory for the
    external IVR machine. The incoming WAV and/or MP3 files from the VIP
    were directly retrieved by the IVR system from the mapped LS1
    incoming directory.

b.  There was no floppy drive on the LS1 server so the **vip.pub** key
    file was copied to the LS1 /home/crs.ssh directory as
    **authorized_keys**, via another external machine that recognized
    the remote mapping of the LS1 incoming directory. This **vip.pub**
    public key file was created during the authenticated ssh
    installation.

On August 10^th^, the CRS and VIP systems were verified as stable and
operational. The scheduled NOAA Weather Radio Specific Area Message
Encoder (NWRSAME) DMO event code testing was not performed because the
OAT site did not have a NWRSAME decoder that can verify the DMO event
code and the "999000" Universal Generic Code (UGC) replacement. The WFO
PHI eventually acquired an NWRSAME receiver and the non-startup of the
receiver was verified during the NWRSAME DMO test. The "TEST" string was
also displayed on the receiver display console, indicating the test mode
transmission.

The OAT test team noticed that some VIP timeouts were occurring on the
VIP processor. The OAT test team initially recommended that the site
personnel resend the messages that timed out. An unfortunate consequence
of this was for those messages that were inadvertently not resent, the
IVR messages were not being refreshed or replaced for the site's phone
system. Further into the same week, the OAT site personnel reported that
the VIP timeouts were occurring during 4:00 PM EDT and 4:00 AM EDT.
These times coincided when CRS and VIP are generally busy. The OAT site
noticed a large number of incoming messages (around 30 messages), some
of which were relatively larger in byte sizes, were being sent to CRS. A
further recommendation from the OAT test team was to increase the
maximum VIP timeout value beyond the current 60 seconds within the CRS
**Site Configuration** window.

A new TTR (*TTR #891: Increase the VIP timeout value under Site
Configuration menu*) was written to document this problem. This TTR was
discussed during the OAT TRG conference call on August 12^th^. New
instructions were given by the OPS23 to WFO PHI for properly extending
the VIP timeout. The new instructions basically involve updating a CRS
resource file (CI_site.xdr) to allow for a larger maximum VIP timeout
value. When the resource file is updated, the **Site Configuration** VIP
timeout GUI control will allow a higher maximum value than the current
60 second maximum value.

The WFO PHI tested the updated instructions and extended the VIP timeout
to around 160 seconds. This adjustment is now currently allowing
incoming CRS messages to properly convert in VIP without any timeout.
The WFO PHI IVR system was also properly replacing its voice files due
to the operational VIP conversions.

During the OAT TRG conference call on August 12^th^, a recommendation
was made, by the Office of Operational Systems, Field Systems Operations
Center, Test and Evaluation Branch (OPS24), for OPS23 to generate this
VIP software timeout patch for all sites in case of VIP timeout
problems. OPS23 strongly advised against this recommendation because the
workaround will fail during a CRS database recompile. The updated
database ASCII file (generated via the gui2ascii CRS database ASCII file
generator) saves the now higher maximum value but a recompile (crs_site)
will still enforce it range limits for only up to 60 seconds, and this
will lead into a recompile failure. OPS23 wants to properly update the
source files and decided that this fix will be included in a future
build. OPS23 has agreed to post a warning on the CRS web site that will
describe possible VIP timeouts due to unusually large messages for VIP
conversions.

The WFO PHI were also able to successfully update a script (scour), on
the LDAD server, that will purge WAV and/or MP3 files transferred from
VIP via the remote sftp functionality. During the August 26^th^ OAT TRG
conference call, it was confirmed that this scour script has been
working successfully without any system degradation.

The WFO PHI was unable to attend the final OAT TRG meeting held on
September 16, 2004. OPS24 contacted WFO PHI afterwards, and the OAT site
reported no problems with either CRS or VIP systems. The VIP is
currently not experiencing any more VIP timeouts and the network is
stable and operational. **The WFO PHI recommended the national
deployment of the CRS Build 10.0/VIP Build 3.1**.

**2.2 OAT Testing - WFO EWX**[]{#__RefHeading___Toc86026814 .anchor}

On August 10, 2004, after a brief meeting with the OAT test team to
discuss test strategies and schedule, the WFO EWX started their
installation of the CRS Build 10.0/VIP Build 3.1 from 8:45 AM to 1:50
PM. The CRS and VIP software installation went well. During the
installation and upon inserting the VIP Restore CD #6 during the disk
image processing, several input/output errors were displayed on the VIP
monitor. The disk image copy installation was immediately aborted.

A personal copy of the same VIP Restore CD#6 from the OAT test team was
then used instead of the delivered CD, and the disk image copy and the
rest of the installation proceeded without problems. The "killall"
workaround (see Section 2.1 paragraph c) for the "su -- crs" Linux shell
hang-up was also performed. AWIPS messages were sent to CRS and were
subsequently converted by VIP and normally broadcasted.

On August 11^th^, per the CRS Build 10.0/VIP Build 3.1 OAT Test Plan
document (dated August 2004) test schedule, the NWRSAME DMO event code
testing was performed. This functionality was tested prior to the OAT
site routine weekly tests. The WFO EWX had a DCR-450 NWRSAME tone
decoder that was monitoring the San Antonio transmitter (SAT) which can
parse out the actual NWRSAME tone outputs. The OAT site personnel
created a **SATDMOSAT** message type that was designated as an emergency
override (EO) message type. This same message type was then used during
an EO session with NWRSAME tones. The DCR-450 did not transmit audible
alarms which is the proper behavior. To verify the test tone event, the
**Activity Logs** window was displayed from CRS and the transmission log
was queried via the **SATDMOSAT** message type. The log entry reported
the proper "**ZCZC-WXR-DMO-999000** **..."** data output.

The OAT site then performed their normal routine weekly tests which
involved sending actual NWRSAME tones to the SAT transmitter. The
DCR-450 performed its audible alarm and when the OAT site personnel
pressed the DCR-450 **READ** button, it correctly displayed the **RWT**
event code with the proper UGC county codes. The OAT site RWT
interruption message was properly scheduled and broadcasted.

For the rest of the day, further monitoring of the system yielded no
errors in the network including no instances of VIP retries in the
system logs. The OAT test team and the OAT site personnel both concluded
that the network and the CRS and VIP systems were performing remarkably
well without any system degradation.

On August 12^th^, the OAT test team and site personnel participated in
the OAT TRG conference call and reported their findings. During the
conference call, OPS23 reminded the OAT test teams that for the NWRSAME
DMO tone testing, the actual test tones will still be generated
including the actual test message contents. OPS23 also added that the
feature will not turn on receivers that were previously off and will
generate the **ZCZC-WXR-DMO-999000** entry in the **Activity Logs**
window. Additionally, the testing for the NWRSAME DMO will now use voice
recorded (with test contents) weather messages that use a newly-created
DMO message type instead of just performing an EO session of the same
DMO message type. This DMO testing was used because the ON-AIR LIVE
nature of EO transmissions might prove difficult for detecting receiver
ON and OFF behavior.

During the OAT, the WFO EWX proceeded to add a new transmitter to its
configuration. One of the related tasks was to redefine previously
created listening area codes with their corresponding transmitter maps.
On September 9^th^, the WFO EWX reported that during a reassignment of
transmitters for a specific listening area, the reassigned transmitter
scheduling was terminated. The OAT site personnel noticed that on the
CRS **Status** window, the transmitter icon of the reassigned
transmitter, displayed the "inoperable" state ("slash mark on
transmitter icon"). As a workaround, the OAT site personnel manually
updated their current CRS database ASCII file and removed the
transmitter mapping for the specified listening area. Upon recompile and
restart, the CRS resumed normal operations and subsequently broadcasted
messages without any problems. A new TTR (*TTR #900: Listening Area
reassignment caused scheduling to stop*) was written to document this
problem.

OPS23 proceeded to investigate TTR #900 but could not reproduce, at the
WSH test bed facility, the same erred conditions using a copy of the WFO
EWX database and a WSH test bed ASCII file. After further analysis,
OPS23 recommended that the status of the TTR be updated to a **Watch**
state.

At the Final OAT TRG conference call on September 16, 2004, the WFO EWX
reported no problems with either CRS or VIP systems. AWIPS messages,
sent to CRS, were properly converted and subsequently broadcasted. There
were no reported VIP message conversion retries and the network has been
performing normally. OPS23 added that TTR #900 will remain in "Watch"
status and they will work with WFO SGX to try and resolve the reported
anomaly. **The WFO EWX recommended the national deployment of the CRS
Build 10.0/VIP Build 3.1**.

**2.3 OAT Testing - WFO IWX**[]{#__RefHeading___Toc86026815 .anchor}

On August 17, 2004, after a brief meeting with the OAT test team to
discuss test strategies and schedule, the WFO IWX started their
installation of the CRS Build 10.0/VIP Build 3.1 from 8:30 AM to 12:00
PM. The CRS and VIP software installation was performed without any
problems.

During the installation, the "killall" workaround (see Section 2.1
paragraph c) was performed for the "su -- crs" hang-up while setting the
passwords on the VIP machine. The VIP remote sftp functionality was
properly setup and MP3 files were directed and subsequently transferred
to the LS1 server. In order for WFO IWX to send the same MP3 files over
to their web server, the WFO SGX OAT site were asked, by the TRG, to
share a send script that updates MP3 files on the WFO SGX web server.

After the installation and during the initial startup of the CRS system,
one of the three configured transmitters (South Bend) did not
automatically restart. Initial findings by the OAT site personnel
attributed the fault to transmitter hardware problems.

On August 18^th^, the South Bend transmitter was back in service and the
initial fault from the previous day was due to a tripped circuit
breaker. The CRS and VIP systems continued to work normally. The VIP was
successfully converting all input messages without any VIP message
conversion retries. A network check was performed, using the "netstat"
command, and yielded no errors and minimal data collisions.

The NWRSAME DMO event code test was then performed via the creation and
scheduling of the DMO message type, **INDDMOIWX**. This message type was
manually scheduled in one of their current broadcast suites.
Additionally, a test weather message was recorded using the
**INDDMOIWX** message type and NWRSAME tones enabled for the selected
transmitter.

Instead of the DCR-450 decoder, the OAT site used a weather radio
receiver that was capable of detecting NWRSAME tones. This receiver was
used for checking the ON and OFF state during the DMO message broadcast.
When the DMO message was finally broadcasted on the specified
transmitter, the receiver did NOT turn on. This expected behavior in
addition to the **Activity Logs** verification of the
**ZCZC-WXR-DMO-999000** query result correctly indicated a successful
DMO test.

The OAT site personnel proceeded to successfully perform their routine
weekly tests and this time, the NWRSAME tone was tracked on all three
transmitters. The OAT test team then noticed an error message that they
found on the VIP machine which was displayed before every message
conversion. The error message was:

"**TTS: Warning -- swittsSetParameter not successful**"

OPS23 responded that the error log entry has previously existed in the
VIP maintenance logs, even on previous VIP builds. OPS23 further added
that the error message was only a warning and will not cause system
shutdown or degradation to either CRS or VIP system in any way.

At the Final OAT TRG conference call on September 16, 2004, the WFO IWX
reported no problems with either CRS or VIP systems. The incoming AWIPS
messages, sent to CRS, were properly converted and subsequently
broadcasted. There were no reported VIP message conversion retries and
the CRS network has been performing normally. The WFO IWX IVR machine is
properly retrieving the VIP MP3 files from the LS1 server. **The WFO IWX
recommended the national deployment of the CRS Build 10.0/VIP Build
3.1**.

**2.4 OAT Testing - WFO SGX**[]{#__RefHeading___Toc86026816 .anchor}

On August 17, 2004, after a brief meeting with the OAT test team to
discuss test strategies and schedule, the WFO SGX started their
installation of the CRS Build 10.0/VIP Build 3.1 from 9:00 AM to 2:50
PM. The CRS and VIP software installation went well.

During the installation, the "killall" workaround (see Section 2.1
paragraph c) was also performed for the "su -- crs" hang-up while
setting the passwords on the VIP machine. The VIP remote sftp
functionality was also properly setup and the WAV and MP3 files were
transferred from VIP to the LS1 server. The WFO SGX OAT site used their
own send script that was able to send the WAV and MP3 files from the LS1
server to their IVR system and web server. This same script was
requested and distributed to the WFO IWX for their use.

During the transfer of the voice files from the LS1 to the IVR system,
an MP3 playback problem was initially detected with regards to the audio
quality. The audio playback was muffled and barely understandable. This
error condition was later verified as a problem with the mode of file
transfer used for transfer of MP3 files from the LS1 to the IVR system.
It was incorrectly set to ASCII instead of BINARY. Once this mode was
updated, further testing encountered no more playback errors on their
IVR system.

The CRS and VIP systems were restarted and worked normally without any
system degradation. Weather messages were input to the systems and these
messages were properly converted in VIP, and verified to be normally
broadcasted.

On August 18^th^, the CRS and VIP systems were verified as performing
normally without any errors. Per the CRS Build 10.0/VIP Build 3.1 OAT
Test Plan, the NWRSAME DMO event code test was performed. The
**LAXDMOSGX** message type was created and included in the general
category suite for Transmitter 1. A weather message was created with the
same type and the NWRSAME tone option was set. The test message content
was recorded and saved; the message was subsequently scheduled on the
Transmitter 1 schedule.

A DCR-450 NWRSAME decoder was used to monitor Transmitter 1; and a Radio
Shack weather radio, which was turned OFF, was set to monitor
Transmitter 1. Another radio weather receiver was continuously
monitoring Transmitter 1. Upon the initial transmission of
**LAXDMOSGX**, the following observations were noted:

a.  The DCR-450 did NOT produce any audio alarms and it properly
    contained (upon the **READ** command) the
    \"**ZCZC-WXR-DMO-999000**\...\" data output.

b.  The currently broadcasting receiver, that was ALWAYS ON, broadcasted
    both the SAME tones and the test message.

c.  The Radio Shack weather radio did NOT automatically turn on but
    instead displayed \"TEST\" on its display console.

d.  Upon inspection of the **Maintenance-\>Activity Logs** window, the
    \"**ZCZC-WXR-DMO-999000**\...\" data was properly queried.

The DMO test was repeated two more times with the same results. The DMO
capability was deemed working as designed and the CRS and VIP systems
remained stable and normal.

The routine weekly tests were successfully performed at around 10:00 AM.
The interrupt message RWT (with NWRSAME tones) properly turned on the
Radio Shack weather radio and this message was heard properly on both
receivers. The DCR-450 displayed the proper data buffer output (and was
even printed for verification).

The network was verified as normal and stable via the "netstat" command
(no errors and very minimal collisions), and there were no occurrences
of VIP message conversion retries.

The SGX Remote Off-Air Monitoring System (ROAMS) Monitoring Unit (MU)
called in after the RWT tests, and the OAT test team verified that some
of the ROAMS phone numbers were not operational. After verifying and
updating **Site Configuration** values, Transmitters 2, 4, and 6 are now
working. Transmitters 3 and 5 were not sending out ROAMS query requests
due to bad site numbers and/or incorrect phone numbers. Transmitter 1
was unable to query ROAMS data due to reset requirements on the
Transmitter 1 \"tellular phone system\".

Additionally, in response to the ROAMS MU error event that was displayed
on the Alert Monitor, the OAT test team started the **ROAMS
Query/Modify** window (via the **Transmitter-\>ROAMS-\>ROAMS
Query/Modify**). ROAMS query requests for Transmitter 1 and 4 failed to
return successfully, so the saved datasets were viewed instead. For
Transmitter 1, the machine password displayed in the "More" window was
\"NATHAN\^\^\^:\" where \^ equals space. For Transmitter 4, the machine
password displayed in the "More" window was \"NATHAN\^4B\". Further
verification in the **Site Configuration** window revealed that for both
transmitters, the passwords were \"NATHAN\". The **Site Configuration**
password field value only allows 8 characters; the "More" window values
for both transmitters were beyond the maximum eight-character limit. A
new TTR was written (*TTR #893: ROAMS More Window displays bad machine
password*) to document the ROAMS "More" display problem.

On August 28^th^, the WFO SGX requested an enhancement for the VIP to
include product filters that will allow sites to limit outgoing WAV
and/or MP3 files that are remotely transferred to the LS1 server. OPS24
created a TTR (*TTR #898 VIP filter for outgoing remote WAV and/or MP3
files*) that documented this VIP filter enhancement. However, OPS23
rescinded the TTR due to the absence of a "Request for Change" that will
allow the TTR to remain in the TestTrack database. This issue was
brought to the attention of the TRG during the TRG conference call on
September 9, 2004. The Western region Program Manager commented that he
will look into the matter and discuss the enhancement with the regional
sites.

On August 19^th^, an MP3 file truncation problem, heard on the IVR
system, was detected and reported to the WFO SGX. The truncation
resulted in the IVR message playback ending abruptly due to the
incorrect IVR MP3 file size and contents. A new TTR was written (*TTR
#894: MP3 truncation problem*) to document the problem. The problem was
initially set in the "Watch" status since it has not been reproduced or
repeated since the initial incident. The earlier prognosis could not
verify whether the truncation occurred during the file transfer from VIP
to LS1 or from the LS1 to the IVR system. OPS23 later commented that,
after their analysis, the problem is highly likely to be a transfer
problem from LS1 to the IVR.

At the Final OAT TRG conference call on September 16, 2004, the WFO SGX
reported no problems with either CRS or VIP systems. The incoming AWIPS
messages, sent to CRS, were properly converted and subsequently
broadcasted. There were no reported MP3 file truncations and VIP message
conversion retries. The WFO SGX CRS network has been performing
normally. Additionally, the TRG recommended that the status for TTR #894
be updated to "Closed" since the MP3 truncation problem has not been
repeated. **The WFO SGX recommended the national deployment of the CRS
Build 10.0/VIP Build 3.1**.

**3.0 Test Trouble Reports**[]{#__RefHeading___Toc86026817 .anchor}

This section describes the TTRs written during the OAT, including each
TTR's Impact, Priority, summary and status. The **Impact** field deals
with how each problem affects the overall broadcast mission. The problem
can be assigned (sorted in ascending severity):

Impact 1 - prevent message broadcast, no workaround

Impact 2 - prevent message broadcast, reasonable workaround

Impact 3 - degradation of broadcast

Impact 4 - less critical, loss of minimum capability

Impact 5 - minimum to no impact, nice to have.

The **Priority** field deals with how the problem is planned to be
resolved. The problem can be assigned (sorted in ascending severity):

Priority 1 - need immediate emergency fix

Priority 2 - include in the next build

Priority 3 - include in future build

Priority 4 - requires replacement system

Priority 5 - undetermined

All reported TTRs during the OAT were non-critical and will be
candidates for a fix in a future build. The TTRs written during the OAT
are summarized in Table 2. The detailed TTRs are included in Attachment
C.

+-----+--------------------------------+---+-------+-------+--------------+
| []{ |                                |   |       |       |              |
| #__ |                                |   |       |       |              |
| Ref |                                |   |       |       |              |
| Hea |                                |   |       |       |              |
| din |                                |   |       |       |              |
| g__ |                                |   |       |       |              |
| _To |                                |   |       |       |              |
| c82 |                                |   |       |       |              |
| 480 |                                |   |       |       |              |
| 369 |                                |   |       |       |              |
| .   |                                |   |       |       |              |
| anc |                                |   |       |       |              |
| hor |                                |   |       |       |              |
| }Ta |                                |   |       |       |              |
| ble |                                |   |       |       |              |
| 2 - |                                |   |       |       |              |
| T   |                                |   |       |       |              |
| TRs |                                |   |       |       |              |
| f   |                                |   |       |       |              |
| rom |                                |   |       |       |              |
| the |                                |   |       |       |              |
| CRS |                                |   |       |       |              |
| Bu  |                                |   |       |       |              |
| ild |                                |   |       |       |              |
| 10  |                                |   |       |       |              |
| .0/ |                                |   |       |       |              |
| VIP |                                |   |       |       |              |
| Bu  |                                |   |       |       |              |
| ild |                                |   |       |       |              |
| 3.1 |                                |   |       |       |              |
| OAT |                                |   |       |       |              |
+-----+--------------------------------+---+-------+-------+--------------+
| Imp |                                | P |       |       |              |
| act |                                | r |       |       |              |
| 1 = |                                | i |       |       |              |
| Pr  |                                | o |       |       |              |
| eve |                                | r |       |       |              |
| nts |                                | i |       |       |              |
| msg |                                | t |       |       |              |
| b   |                                | y |       |       |              |
| roa |                                | 1 |       |       |              |
| dca |                                | = |       |       |              |
| st, |                                | I |       |       |              |
| no  |                                | m |       |       |              |
| w   |                                | m |       |       |              |
| ork |                                | e |       |       |              |
| aro |                                | d |       |       |              |
| und |                                | i |       |       |              |
|     |                                | a |       |       |              |
| Imp |                                | t |       |       |              |
| act |                                | e |       |       |              |
| 2 = |                                | f |       |       |              |
| P   |                                | i |       |       |              |
| rev |                                | x |       |       |              |
| ent |                                |   |       |       |              |
| msg |                                | P |       |       |              |
| b   |                                | r |       |       |              |
| roa |                                | i |       |       |              |
| dca |                                | o |       |       |              |
| st, |                                | r |       |       |              |
| r   |                                | i |       |       |              |
| eas |                                | t |       |       |              |
| ona |                                | y |       |       |              |
| ble |                                | 2 |       |       |              |
| w   |                                | = |       |       |              |
| ork |                                | I |       |       |              |
| aro |                                | n |       |       |              |
| und |                                | c |       |       |              |
|     |                                | l |       |       |              |
| Imp |                                | u |       |       |              |
| act |                                | d |       |       |              |
| 3 = |                                | e |       |       |              |
| De  |                                | i |       |       |              |
| gra |                                | n |       |       |              |
| dat |                                | n |       |       |              |
| ion |                                | e |       |       |              |
| of  |                                | x |       |       |              |
| bro |                                | t |       |       |              |
| adc |                                | b |       |       |              |
| ast |                                | u |       |       |              |
|     |                                | i |       |       |              |
| Imp |                                | l |       |       |              |
| act |                                | d |       |       |              |
| 4 = |                                |   |       |       |              |
| L   |                                | P |       |       |              |
| ess |                                | r |       |       |              |
| cri |                                | i |       |       |              |
| tic |                                | o |       |       |              |
| al, |                                | r |       |       |              |
| l   |                                | i |       |       |              |
| oss |                                | t |       |       |              |
| of  |                                | y |       |       |              |
| m   |                                | 3 |       |       |              |
| ini |                                | = |       |       |              |
| mum |                                | I |       |       |              |
| c   |                                | n |       |       |              |
| apa |                                | c |       |       |              |
| bil |                                | l |       |       |              |
| ity |                                | u |       |       |              |
|     |                                | d |       |       |              |
| Imp |                                | e |       |       |              |
| act |                                | i |       |       |              |
| 5 = |                                | n |       |       |              |
| M   |                                | a |       |       |              |
| ini |                                | f |       |       |              |
| mal |                                | u |       |       |              |
| to  |                                | t |       |       |              |
| no  |                                | u |       |       |              |
| i   |                                | r |       |       |              |
| mpa |                                | e |       |       |              |
| ct, |                                | b |       |       |              |
| n   |                                | u |       |       |              |
| ice |                                | i |       |       |              |
| to  |                                | l |       |       |              |
| h   |                                | d |       |       |              |
| ave |                                |   |       |       |              |
|     |                                | P |       |       |              |
|     |                                | r |       |       |              |
|     |                                | i |       |       |              |
|     |                                | o |       |       |              |
|     |                                | r |       |       |              |
|     |                                | i |       |       |              |
|     |                                | t |       |       |              |
|     |                                | y |       |       |              |
|     |                                | 4 |       |       |              |
|     |                                | = |       |       |              |
|     |                                | R |       |       |              |
|     |                                | e |       |       |              |
|     |                                | q |       |       |              |
|     |                                | u |       |       |              |
|     |                                | i |       |       |              |
|     |                                | r |       |       |              |
|     |                                | e |       |       |              |
|     |                                | s |       |       |              |
|     |                                | a |       |       |              |
|     |                                | r |       |       |              |
|     |                                | e |       |       |              |
|     |                                | p |       |       |              |
|     |                                | l |       |       |              |
|     |                                | a |       |       |              |
|     |                                | c |       |       |              |
|     |                                | e |       |       |              |
|     |                                | m |       |       |              |
|     |                                | e |       |       |              |
|     |                                | n |       |       |              |
|     |                                | t |       |       |              |
|     |                                | s |       |       |              |
|     |                                | y |       |       |              |
|     |                                | s |       |       |              |
|     |                                | t |       |       |              |
|     |                                | e |       |       |              |
|     |                                | m |       |       |              |
|     |                                |   |       |       |              |
|     |                                | P |       |       |              |
|     |                                | r |       |       |              |
|     |                                | i |       |       |              |
|     |                                | o |       |       |              |
|     |                                | r |       |       |              |
|     |                                | i |       |       |              |
|     |                                | t |       |       |              |
|     |                                | y |       |       |              |
|     |                                | 5 |       |       |              |
|     |                                | = |       |       |              |
|     |                                | U |       |       |              |
|     |                                | n |       |       |              |
|     |                                | d |       |       |              |
|     |                                | e |       |       |              |
|     |                                | t |       |       |              |
|     |                                | e |       |       |              |
|     |                                | r |       |       |              |
|     |                                | m |       |       |              |
|     |                                | i |       |       |              |
|     |                                | n |       |       |              |
|     |                                | e |       |       |              |
|     |                                | d |       |       |              |
+-----+--------------------------------+---+-------+-------+--------------+
| *   | **Summary**                    |   | **Imp | **    | **Status**   |
| *No |                                |   | act** | Prior |              |
| .** |                                |   |       | ity** |              |
+-----+--------------------------------+---+-------+-------+--------------+
| 891 | Increase the VIP timeout value |   | 5     | 3     | CCB Review   |
|     | under Site Configuration menu. |   |       |       |              |
+-----+--------------------------------+---+-------+-------+--------------+
| 893 | ROAMS More Window displays bad |   | 5     | 5     | Analysis     |
|     | machine password.              |   |       |       |              |
+-----+--------------------------------+---+-------+-------+--------------+
| 894 | MP3 truncation problem         |   | 3     | 3     | Closed       |
+-----+--------------------------------+---+-------+-------+--------------+
| 900 | Listening Area reassignment    |   | 2     | 5     | Watch        |
|     | caused scheduling to stop      |   |       |       |              |
+-----+--------------------------------+---+-------+-------+--------------+

**TTR #891** was written in response to the VIP timeouts that was
occurring in WFO PHI during their busy 4:00 PM to 4:00 AM timeframe.
OPS23 has written instructions on how to extend the VIP timeout value
beyond the currently maximum value of 60 seconds. OPS23 will post a
warning, on the CRS web site, regarding VIP timeouts when unusually
large-sized weather messages are input to CRS for conversion by VIP. At
the final OAT TRG meeting held in September 16, 2004, the TRG agreed
that this TTR will be fixed in a future build.

**TTR #893** was added to document an incorrect machine password display
on the "More" window of the **ROAMS Query/Modify** screen. The machine
password field displayed extraneous characters that did not match the
configured value in the ROAMS data from the **Site Configuration**
window. At the final OAT TRG meeting, the TRG agreed that this TTR will
be fixed in a future build.

**TTR #894** was written per a reported instance of MP3 truncation
during IVR playback. The incident happened only once; initial analysis
could not determine whether the truncation occurred during the VIP to
LS1 or from the LS1 to IVR MP3 transfer. This TTR, which degrades
current broadcasting, was updated to have a "**Watch**" status. At the
final OAT TRG meeting, the TRG agreed that TTR #894 will be recommended
for closure (status of "Close") because the error condition has not been
repeated.

**TTR #900** was added to document a reported transmitter scheduling
termination when the transmitter mapping for a specific listening area
record has been updated. The updated transmitter that was removed from
the listening area mapping was directly affected and the **Status**
window displayed an "inoperable" status (slash mark on the transmitter
icon). The OAT site was able to provide a workaround by updating the
current CRS database ASCII file and manually removing the transmitter
mapping and subsequently recompiling the CRS database. After a
successful recompile and restart, the CRS and VIP systems performed
normally without any problems and system degradation. OPS23 proceeded to
investigate the anomaly and was not able to reproduce the same erred
conditions. The OAT TRG recommended that this TTR's status be changed to
a "**Watch**". The WFO EWX agreed that this problem did not pose as
significant system problem that will affect normal operations.

**4.0 Conclusions**[]{#__RefHeading___Toc86026818 .anchor}

Conclusions are based on the OAT information gathered from installation
and operational use of CRS Build 10.0/VIP Build 3.1 at the four OAT
sites. Overall, the OAT tests verified that the CRS Build 10.0/VIP Build
3.1 provided reliable and timely NWR transmission of products using
AWIPS in an operational environment. The general conclusion is supported
by the following examination of the original OAT test objectives:

> a\. [Verify the EHB-7 Software Note 6 document instructions for the
> installation of CRS Build 10.0 and the VIP Build 3.1 software are
> complete and accurate]{.underline}. -- **PASSED**.
>
> The software installation had minor problems that were documented and
> forwarded to OPS23. OAT installation comments were forwarded, from
> OPS24 to OPS23, via an email dated August 30, 2004. The EHB-7 Software
> Note 6 installation document has been updated per critically reported
> problems. For the most part, as evident in the responses from the OAT
> Questionnaire forms returned by the OAT sites, the CRS Build 10.0/VIP
> Build 3.1 software installation went smoothly (mostly rated as a
> "**1**" Excellent or "**2**" Good).
>
> The WFO IWX further added, in their CRS Questionnaire (see Attachment
> D) that "*...Overall, the new build went very smooth. The knowledge
> and expertise of the install team was evident from the beginning
> through to the end...*"
>
> b\. [Verify, in an operational environment, successful operation of
> the CRS Build 10.0 and the VIP Build 3.1 software without any system
> degradation]{.underline}. -- **PASSED**.
>
> The CRS Build 10.0/VIP Build 3.1 software was stable and operated
> satisfactorily during the OAT with no problems and/or system
> shutdowns. The product formatters also worked well with the new
> CRS/VIP system. The WFO EWX also added, from their CRS Questionnaire
> (see Attachment D), that they "*...have sent numerous warnings and
> watches and have no malfunctions*".
>
> c\. [Verify the required CRS Build 10.0/VIP Build 3.1 documents are
> adequate (e.g., Release Notes, etc)]{.underline}. - **PASSED**
>
> The documentation provided to the OAT sites was adequate and
> understandable. Minor corrections were made to the installation
> instructions to correctly proceed with the installation and/or
> configure required data.
>
> d\. [Verify the CRS and VIP automatic user's password handling is
> adequate and operational]{.underline}. - **PASSED**
>
> Based on the OAT Questionnaire responses (see Attachment D), the CRS
> Build 10.0/VIP Build 3.1 password handling is adequate and
> operational. A minor procedure update has been reported regarding the
> strict CRS Front End Processor (FEP) password checking and this
> information has been recommended for update on the EHB-7 Software Note
> 6 document.
>
> Based on the responses from the OAT Questionnaire forms returned by
> the OAT sites, the CRS Build 10.0/VIP Build 3.1 automatic user's
> password handling was either rated as a "**1**" (Excellent) or "**2**"
> (Good).
>
> e\. [Verify the ingest of input messages into CRS, conversion
> processing with the VIP, and subsequent broadcast are operational
> without any system degradation]{.underline}. - **PASSED**
>
> The CRS Build 10.0/VIP Build 3.1 software did not incur problems for
> CRS input messages, VIP conversion processing, and did not cause any
> system degradation on the subsequent message broadcast.
>
> Based on the responses from the OAT Questionnaire forms returned by
> the OAT sites, the CRS Build 10.0/VIP Build 3.1 ingest of input
> messages into CRS were either rated as a "**1**" (Excellent) or
> "**2**" (Good).

f\. [Verify any problems found during VIP remote site file transfers,
per specifically designated OAT sites performing such functionality, are
mitigated and/or supported for operational status without any system
degradation]{.underline}. - **PASSED**

> Additional steps were taken to mitigate the new VIP remote sftp file
> transfers for the different OAT sites. For the WFO PHI, the OAT test
> personnel had to setup the SAMBA software package on the LDAD server
> (LS1). This SAMBA package allowed directory mappings for the LS1
> incoming directory in order for the IVR machine to "see" the LS1
> incoming directory and automatically extract the VIP-transferred files
> on the LS1 server unto the IVR.
>
> The WFO SGX created and used a send script, on the LS1 server, which
> will automatically send the MP3 files from the LS1 to the IVR phone
> system and to their web server. Initially, there was a problem with
> the MP3 file transfers from the LS1 to the IVR; the MP3 files being
> broadcasted seemed corrupted. This corruption was later diagnosed as a
> problem with the file mode transfer set to ASCII instead of BINARY.
> Once this transfer mode was corrected, the IVR playback of the MP3
> files was stable and operational.
>
> The WFO EWX did not currently perform VIP remote site file transfers,
> and so this feature was never installed and/or setup. The WFO IWX was
> able to setup their IVR system successfully. Per the last OAT TRG
> meeting, the WFO IWX indicated that they have not worked with the send
> script that was sent to them by WFO SGX for their web server update.
>
> Based on the responses from the OAT Questionnaire forms returned by
> the OAT sites, the CRS Build 10.0/VIP Build 3.1 VIP remote sftp
> implementation were rated from a "**1**" (Excellent) to a "**3**"
> (Satisfactory).

g\. [Verify the NWRSAME test event (e.g., DMO) does not incur any
problems during test transmission.]{.underline} - **PASSED**

> All OAT sites were able to test the NWRSAME DMO test event code
> successfully. During the first week of OAT, the WFO PHI did not have a
> NWRSAME tone decoder and was not able to test the DMO feature.
> However, WFO PHI was able to procure a NWRSAME tone receiver which
> successfully tested the non-startup of the receiver during their DMO
> testing. Using the Activity Logs window, the WFO PHI verified the DMO
> test code and the "999000" data output per the transmission queries.
> The rest of the OAT sites used an in-house DCR-440 NWRSAME tone
> decoder to verify the DMO output, including subsequent inspection of
> the Activity Logs transmission queries.
>
> Based on the responses from the OAT Questionnaire forms returned by
> the OAT sites, the CRS Build 10.0/VIP Build 3.1 NWRSAME DMO testing
> were rated from a "**1**" (Excellent) to a "**2**" (Good).

**5.0 Recommendations**[]{#__RefHeading___Toc86026819 .anchor}

Based on the review of the OAT results in Sections 1.0 and 2.0, and the
conclusions from Section 4.0, **the CRS Build 10.0/VIP Build 3.1 OAT TRG
recommends the national deployment of CRS Build 10.0/VIP Build 3.1 with
the workarounds identified in the release notes, related documentation,
and CRS web site information**. The national deployment is currently
scheduled from September 20, 2004 to October 29, 2004.

**PART II: CRS Build 10.0/VIP Build 3.1 OAT
Description**[]{#__RefHeading___Toc86026820 .anchor}

**1.0 Background**[]{#__RefHeading___Toc86026821 .anchor}

This section contains background information about the CRS/VIP system
under test, the test objectives for the CRS Build 10.0/VIP Build 3.1,
and a description of the CRS/VIP systems evaluated. More detailed
information can be found the in the CRS System Administrator's Manual
and the CRS Site Operator's Manual.

**1.1 Prior Testing**[]{#__RefHeading___Toc86026822 .anchor}

The NWS conducted CRS and VIP systems integration testing at WSH from
May 17 to June 11, 2004. After a successful software integration effort
by OPS23, the systems were turned over to OPS24 for a System Test (ST).
OPS24 conducted the ST of CRS Build 10.0/VIP Build 3.1 at WSH from June
14 to August 6, 2004.

There were a total of 55 TTRs generated during the ST. Refer to the CRS
Build 10.0/VIP Build 3.1 System Test Report document, dated September
2004, for more information regarding the system activities and
ST-related TTRs and their corresponding status. On August 5, 2004, the
ST Wrap-Up/OAT Readiness Review meeting was held to discuss whether the
CRS Build 10.0/VIP Build 3.1 is ready for the OAT. There were no
reported TTRs with an **Impact** of **1** or **2**. Subsequently, the
TRG decided that the CRS and VIP systems were ready for the OAT which
began August 9, 2004.

**1.2 Test Objectives and Criteria**[]{#__RefHeading___Toc86026823
.anchor}

The overall objective of the OAT was to verify the CRS Build 10.0/VIP
Build 3.1 provided reliable, timely, and understandable NWR
transmissions of NWS products in an operational environment using AWIPS.
The test objectives, as outlined from the CRS Build 10.0/VIP Build 3.1
OAT Test Plan document, dated August 2004, are listed below with the
success criteria:

> a\. [Verify the EHB-7 Software Note 6 document instructions for the
> installation of CRS Build 10.0 and the VIP Build 3.1 software are
> complete and accurate]{.underline}.
>
> CRITERIA: The CRS Build 10.0/VIP Build 3.1 installation instructions
> were understandable and could be used by site personnel, independently
> of the test team members, or WSH support personnel, to install,
> configure, and operate CRS Build 10.0 and VIP Build 3.1.
>
> b\. [Verify, in an operational environment, successful operation of
> the CRS Build 10.0 and the VIP Build 3.1 software without any system
> degradation]{.underline}.
>
> CRITERIA: The CRS Build 10.0/VIP 3.1 was successfully operational and
> stable during broadcast of messages using the new and updated
> software.
>
> c\. [Verify the required CRS Build 10.0/VIP Build 3.1 documents are
> adequate (e.g., Release Notes, etc)]{.underline}.
>
> CRITERIA: The CRS Build 10.0/VIP Build 3.1 documents were correctly
> updated for the CRS Build 10.0/VIP Build 3.1 software.
>
> d\. [Verify the CRS and VIP automatic user's password handling is
> adequate and operational]{.underline}.
>
> CRITERIA: The CRS Build 10.0/VIP Build 3.1 automatic user's password
> handling was normally operating within the password guidelines of
> EHB-7 Software Note 6 password generation.
>
> e\. [Verify the ingest of input messages into CRS, conversion
> processing with the VIP, and subsequent broadcast are operational
> without any system degradation]{.underline}.
>
> CRITERIA: The CRS Build 10.0/VIP 3.1 was converting and broadcasting
> the CRS input messages without any system degradation.

f\. [Verify any problems found during VIP remote site file transfers,
per specifically designated OAT sites performing such functionality, are
mitigated and/or supported for operational status without any system
degradation]{.underline}.

> CRITERIA: The VIP Build 3.1 remote sftp function was properly setup
> with no system degradation.

g\. [Verify the NWRSAME test event (e.g., DMO) does not incur any
problems during test transmission]{.underline}.

> CRITERIA: The CRS Build 10.0/VIP Build 3.1 NWRSAME DMO functionality
> properly output the DMO and "999000" data without turning on NWRSAME
> decoders.

**1.3 CRS Build 10.0/VIP Build 3.1 Enhancements and Modifications under
Test**[]{#__RefHeading___Toc86026824 .anchor}

The new CRS Build 10.0/VIP Build 3.1 contained 10 software enhancements
and 16 software fixes. Major changes to the new build include the
automatic CRS and VIP user's password checking, the secure file
transfers from CRS to VIP, authenticated secure shell key file
installations, and the NWRSAME DMO test event code processing.

A non-activated feature in the new build is the capability for
externally generated voice files. This capability allows the input of
waveform audio (WAV) files with appended CRS header data. This function
would have allowed WAV files, generated outside of CRS with correct
header data, to be checked on input, saved in the CRS database, and
broadcasted normally.

However, during the System Test (ST), there were some problems found
with the externally generated voice processing. These problems were
attributed to:

a.  Design. The main parsing, input queue, and other related critical
    code routines were shared with the non-related VIP Communications
    Processing Voice Conversion (CP_VC) process. The ST TRG agreed that
    a stand-alone process dedicated to this function might serve as a
    better solution. OPS23 agreed to revisit the design for a future
    build.

b.  Performance. During the ST, several externally generated voice
    messages were tested (including some watches and warnings) which
    resulted to slower than usual playback, as verified by the Broadcast
    Cycle window scheduling. Some externally-generated message name
    anomalies and message interruption inconsistencies during normal and
    override conditions were also observed.

The ST TRG subsequently decided that the externally generated voice
processing feature be deactivated for the OAT and for the nationally
deployed CRS Build 10.0/VIP Build 3.1. OPS23 added that this
functionality could be available, in a future build, in support of the
all-hazards collection system.

For a detailed discussion of all enhancements and fixes, the CRS Build
10.0/VIP Build 3.1 Release Notes are found in Attachment E.

**1.4 Test Sites and Configurations**[]{#__RefHeading___Toc86026825
.anchor}

The four WFO offices selected by the NWS for the OAT are listed in Table
3 together with their corresponding descriptive data.

  -------------------------------- -------- ------------ ------------------ ---------------- -------------
  []{#__RefHeading___Toc82480370                                                             
  .anchor}Table 3 - CRS Build                                                                
  10.0/VIP Build 3.1 OAT Test                                                                
  Sites and Configurations                                                                   

  **Site**                         **ID**   **Config**   **Transmitters**   **VIP Remote     **Spanish**
                                                                            SFTP**           

  Philadelphia, PA                 PHI      Large        7                  Yes              No

  Austin/San Antonio, TX           EWX      Max          12                 No               No

  Northern Indiana, IN             IWX      Typical      4                  Yes              No

  San Diego, CA                    SGX      Large        6                  Yes              Yes
  -------------------------------- -------- ------------ ------------------ ---------------- -------------

**2.0 Test Conduct**[]{#__RefHeading___Toc86026826 .anchor}

The CRS Build 10.0/VIP Build 3.1 software was delivered to the OAT sites
as complete package including software and documentation. WSH test teams
(see Table 4) initially traveled to the WFO PHI on August 8, 2004 and
installed the software the next day, August 9^th^. Another test team
traveled to WFO EWX on August 9^th^ and installed the software the next
day, August 10^th^. A couple of test teams simultaneously traveled to
WFO IWX and WFO SGX on August 16^th^ and installed the software on each
site the next day, August 17, 2004. For all OAT sites, the WSH test team
witnessed the successful installation and provided technical assistance
when required.

At each OAT site, the CRS and VIP systems were used in normal operations
24 hours a day, 7 days a week. Most of the messages that were normally
broadcasted were converted messages from the VIP. For the OAT sites in
WFO PHI, WFO IWX, and WFO SGX, the remote sftp functionality testing was
successfully performed. These OAT sites either had their IVR systems up
and running with SAMBA (WFO PHI) or field-created scripts (WFO IWX and
WFO SGX) that send the WAV and/or MP3 files from the LS1 to an external
machine.

The OAT started with short meetings between WSH test teams and their
respective OAT site focal points regarding scheduled tests and
installation strategies. The OAT then proceeded with the verification of
the site's receipt and installation of the complete CRS Build 10.0/VIP
Build 3.1 software package. The WSH test team (see Table 4) assisted
their assigned sites for at least 2-3 days of initial operations. The
OAT sites performed their routine weekly and scheduled testing including
the NWRSAME DMO test event code testing. The WSH test team also
performed network verification for VIP message conversion retries.

The OAT test personnel reported some errors in the installation
procedures and minor software problems (see Table 2) and completed the
TTRs to document problems. OAT site personnel continued evaluating the
CRS and VIP systems during routine operations through September 17,
2004.

**2.1 Problem Documentation and
Classification**[]{#__RefHeading___Toc86026827 .anchor}

OAT site personnel documented all CRS/VIP problems by completing CRS
TTRs (see Attachment C). The TTRs were reviewed by the OAT TRG during
weekly conference calls. The Test Review Group classified the documented
CRS problems via the **Impact** and the **Priority** values (see Part I,
Section 3.0). The OAT testing would not have started if TTRs generated
during the CRS Build 10.0/VIP Build 3.1 ST, with an **Impact** of **1**
or **2,** exists in the TestTrack database. An **Impact** **1** would
have necessitated a temporary suspension until an immediate fix has been
created and retested.

**TTR #900,** which is currently designated with an **Impact** of **2**,
has not been reproduced by OPS23 during retesting at WSH. On retest,
attempts to reassign transmitters from existing listening areas did not
yield any errors. Subsequently, the OAT TRG recommended that the status
for TTR #900 be updated to a "**Watch**"**.** The status for **TTR
#894** has been updated to "**Closed**" because the MP3 truncation error
has not been repeated for further analysis. The other TTRs (**#891 and
#893**) have minimal to no Impact; these TTRs are candidates for a fix
in a future build.

**2.2 Test Personnel**[]{#__RefHeading___Toc86026828 .anchor}

Personnel from WSH and OAT sites conducted the OAT and were included in
the TRG that reviewed and classified the TTRs. OPS24 was responsible for
the management of the OAT. The WSH test team was composed of personnel
from OPS24 and OPS23 (see Table 4).

+----------------+------------------+----------------+----------------+
| []             |                  |                |                |
| {#__RefHeading |                  |                |                |
| ___Toc82480371 |                  |                |                |
| .anchor}Table  |                  |                |                |
| 4 - CRS Build  |                  |                |                |
| 10.0/VIP Build |                  |                |                |
| 3.1 OAT Test   |                  |                |                |
| Personnel      |                  |                |                |
+----------------+------------------+----------------+----------------+
| **PHI**        | **EWX**          | **IWX**        | **SGX**        |
+----------------+------------------+----------------+----------------+
| Joe Byerly     | Joseph Baskin    | Dereek Adams   | Mike           |
| (ESA)          | (CRS FP)         | (ITO)          | Lauderdale     |
|                |                  |                | (ESA)          |
|                | Dale Lininger    |                |                |
|                | (ET)             |                | Scott          |
|                |                  |                | Brookshaw (ET) |
+----------------+------------------+----------------+----------------+
| Jae Lee        | Bert Viloria     | Harry Tran     | Bert Viloria   |
| (OPS24)        | (OPS24)          | (OPS24)        | (OPS24)        |
|                |                  |                |                |
| Harry Tran     | Nancy Helderman  | Warrick Moran  | Sung Vo        |
| (OPS24)        | (OPS23)          | (OPS23)        | (OPS23)        |
|                |                  |                |                |
| Dave Glotfelty |                  |                |                |
| (OPS23)        |                  |                |                |
+----------------+------------------+----------------+----------------+

**2.3 Test Schedule**[]{#__RefHeading___Toc86026829 .anchor}

The OAT started on August 9, 2004 at WFO PHI, August 10^th^ at WFO EWX,
and August 17^th^ for WFO IWX and WFO SGX. Due to test personnel
scheduling and site availability, the OAT testing for both WFO IWX and
WFO SGX was delayed one week.

The schedule included:

a.  One day for initial on-site meeting and CRS Build 10.0/VIP Build 3.1
    installation including VIP remote **sftp** setup and **ssh** key
    installations.

b.  One day to perform the NWRSAME DMO tone test and routine weekly
    tests (RWT) to assess the stability of the installed software.

c.  One day to verify any other system resources (CRS network, VIP
    retries, etc) and/or remote sftp capabilities.

d.  Six (at WFO PHI and WFO EWX) to five (at WFO IWX and WFO SGX) weeks
    of operational evaluation.

The TRG conference calls were held weekly starting from the OAT
Readiness review on August 5, 2004. The conference call for September 2,
2004 was cancelled due to no reported problems with the CRS and VIP
systems. The OAT ended on September 17, 2004.

[]{#__RefHeading___Toc82480377 .anchor}**Attachment A - CRS Build
10.0/VIP Build 3.1 Test Review Group**

+-------------------+-----------------------------+-----------+--------+
| **Na              | **Function**                | **Phone** | **     |
| me/Organization** |                             |           | Voting |
|                   |                             |           | Me     |
|                   |                             |           | mber** |
+===================+=============================+===========+========+
| Jerald Dinges     | Test Review Group Chair     | 301       | Number |
| (OPS24)           |                             | -713-0326 | range  |
|                   |                             | x160      | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Bert Viloria      | OAT Test Director           | 301       |        |
| (OPS24)           |                             | -713-0326 |        |
|                   |                             | x131      |        |
|                   |                             |           |        |
|                   |                             | *FAX:*    |        |
|                   |                             | 301       |        |
|                   |                             | -713-0912 |        |
+-------------------+-----------------------------+-----------+--------+
| Harry Tran        | OAT Support                 | 301       |        |
| (OPS24)           |                             | -713-0326 |        |
|                   |                             | x105      |        |
+-------------------+-----------------------------+-----------+--------+
| Jae Lee (OPS24)   | OAT Support                 | 301       |        |
|                   |                             | -713-0326 |        |
|                   |                             | x158      |        |
+-------------------+-----------------------------+-----------+--------+
| Joel Nathan       | CRS/VIP Software Manager    | 301       | Number |
| (OPS23)           |                             | -713-0191 | range  |
|                   |                             | x119      | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Jeff Earl (OPS12) | Maintenance Assurance       | 301       |        |
|                   |                             | -713-1833 |        |
|                   |                             | x162      |        |
+-------------------+-----------------------------+-----------+--------+
| Harvey Thurm      | Eastern Region Program      | 631       | Number |
| (ER1)             | Manager                     | -244-0124 | range  |
|                   |                             |           | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Mike Mach (SR)    | Southern Region Program     | 817       | Number |
|                   | Manager                     | -978-1100 | range  |
|                   |                             | x108      | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Greg Noonan(CR4)  | Central Region Program      | 816       | Number |
|                   | Manager                     | -891-7734 | range  |
|                   |                             | x301      | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Craig Schmidt     | Western Region Program      | 801       | Number |
| (WR1)             | Manager                     | -524-4000 | range  |
|                   |                             | x266      | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Per Pedersen      | Alaska Region Program       | 907       | Number |
| (AR41)            | Manager                     | -271-3462 | range  |
|                   |                             |           | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| Jay DelCano       | Pacific Region Program      | 808       | Number |
| (PR11)            | Manager                     | -532-6427 | range  |
|                   |                             |           | CH     |
|                   |                             |           | APTER |
+-------------------+-----------------------------+-----------+--------+
| **Philadelphia PA | Focal Points \[Input To     | 609       |        |
| WFO (PHI)**       | Region Prog. Manager\]      | -261-6600 |        |
|                   |                             |           |        |
| Gary Szatkowski   | *MIC*                       |           |        |
|                   |                             |           |        |
| Joseph Byerly     | *ESA*                       |           |        |
|                   |                             |           |        |
| Roy Miller        | *DAPM*                      |           |        |
|                   |                             |           |        |
| Dan Hagarty       | *ITO*                       |           |        |
+-------------------+-----------------------------+-----------+--------+
| **Austin/San      | Focal Points \[Input To     | 830       |        |
| Antonio TX WFO    | Region Prog. Manager\]      | -606-3617 |        |
| (EWX)**           |                             |           |        |
|                   | *MIC*                       |           |        |
| Joe Arellano      |                             |           |        |
|                   | *ESA*                       |           |        |
| Brian Read        |                             |           |        |
|                   | *DAPM*                      |           |        |
| William Runyon    |                             |           |        |
|                   | *ITO*                       |           |        |
| Mark Oliver       |                             |           |        |
+-------------------+-----------------------------+-----------+--------+
| **Northern        | Focal Points \[Input To     | 574       |        |
| Indiana IN WFO    | Region Prog. Manager\]      | -834-1104 |        |
| (IWX)**           |                             |           |        |
|                   | *MIC*                       |           |        |
| Mike Sabones      |                             |           |        |
|                   | *ESA*                       |           |        |
| Peter Wallace     |                             |           |        |
|                   | *DAPM*                      |           |        |
| Terry Click       |                             |           |        |
|                   | *ITO*                       |           |        |
| Dereek Adams      |                             |           |        |
+-------------------+-----------------------------+-----------+--------+
| **San Diego CA    | Focal Points \[Input To     | 858       |        |
| WFO (SGX)**       | Region Prog. Manager\]      | -675-8700 |        |
|                   |                             |           |        |
| Jim Purpura       | *MIC*                       |           |        |
|                   |                             |           |        |
| Mike Lauderdale   | *ESA*                       |           |        |
|                   |                             |           |        |
| Michael Khuat     | *ITO*                       |           |        |
+-------------------+-----------------------------+-----------+--------+

[]{#__RefHeading___Toc82480378 .anchor}**Attachment B - CRS Build
10.0/VIP 3.1 OAT Installation Test Site Comments and Recommendations**

+--------+-------+----------+------+---------------------------------+
| **Docu | *     | **P      | **O  | **Comments**                    |
| ment** | *Page | aragraph | AT** |                                 |
|        | Num   | Number** |      |                                 |
|        | ber** |          | **Si |                                 |
|        |       |          | te** |                                 |
+========+=======+==========+======+=================================+
| EHB-7  | after | Section  | PHI  | Add a new section that will     |
| So     |       | 8.4      |      | reboot the CRS MPs after the    |
| ftware | A-35  |          |      | password setting and before the |
| Note 6 |       |          |      | ssh key installation steps.     |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-23  | Section  | PHI  | Add CRS FEP information         |
| So     |       | 8        |      | indicating the more restrictive |
| ftware |       |          |      | password checking. On the CRS   |
| Note 6 |       |          |      | FEPs, a number and two alpha    |
|        |       |          |      | characters must be included in  |
|        |       |          |      | the new password within the     |
|        |       |          |      | first **eight** characters.     |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-11  | Section  | PHI, | The "**killall sty --s 9; exit  |
| So     |       | 4.1 Step |      | \<Return\>**" workaround for    |
| ftware |       | 56a      | EWX, | the "su -- crs" hang-up should  |
| Note 6 |       |          |      | be added in the document.       |
|        |       |          | IWX, |                                 |
|        |       |          |      |                                 |
|        |       |          | SGX  |                                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-3   | Section  | PHI  | Add the "**umount               |
| So     |       | 2.1      |      | /mnt/floppy/**" information on  |
| ftware |       |          |      | how to manually unmount a       |
| Note 6 |       |          |      | floppy during VIP dictionary    |
|        |       |          |      | backup and/or restore.          |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-11  | Section  | IWX  | Use the word "**Logout**"       |
| So     |       | 4.1 Step |      | instead of "**Restart**".       |
| ftware |       | 58       |      |                                 |
| Note 6 |       |          |      |                                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-16  | Section  | IWX  | **Bold** the following phrases: |
| So     |       | 6.1      |      |                                 |
| ftware |       |          |      | Step 1: XCRS_SITE Utility       |
| Note 6 |       |          |      |                                 |
|        |       |          |      | Step 2: Stop CRS System         |
|        |       |          |      |                                 |
|        |       |          |      | Step 3: OK                      |
|        |       |          |      |                                 |
|        |       |          |      | Step 5: Exit                    |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-16  | Section  | IWX  | **Bold** the following phrases: |
| So     |       | 6.2      |      |                                 |
| ftware |       |          |      | Step 1: XCRS_SITE Utility       |
| Note 6 |       |          |      |                                 |
|        |       |          |      | Step 2: Stop CRS System         |
|        |       |          |      |                                 |
|        |       |          |      | Step 3: OK and Exit             |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-16, | Section  | IWX  | **Bold** the following phrases: |
| So     | A-17  | 7.1      |      |                                 |
| ftware |       |          |      | Step 1: System                  |
| Note 6 |       |          |      |                                 |
|        |       |          |      | Step 2: Exit to UNIX and OK     |
|        |       |          |      |                                 |
|        |       |          |      | Step 3: Acknowledge             |
|        |       |          |      |                                 |
|        |       |          |      | Step 4: KDE Desktop Application |
|        |       |          |      | Starter                         |
|        |       |          |      |                                 |
|        |       |          |      | Step 5: SCO Control Center      |
|        |       |          |      |                                 |
|        |       |          |      | Step 6: Software_Management     |
|        |       |          |      |                                 |
|        |       |          |      | Step 7: Applications Installer  |
|        |       |          |      |                                 |
|        |       |          |      | Step 8: CD-ROM_1 and Update     |
|        |       |          |      | View                            |
|        |       |          |      |                                 |
|        |       |          |      | Step 9: crsopsais               |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-22  | Section  | IWX  | **Bold** the following phrases: |
| So     |       | 7.5      |      |                                 |
| ftware |       |          |      | Step 6: *Host*                  |
| Note 6 |       |          |      |                                 |
|        |       |          |      | Step 7: *License*               |
|        |       |          |      |                                 |
|        |       |          |      | Step 11: *Host*                 |
|        |       |          |      |                                 |
|        |       |          |      | Step 12: *Exit*                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-6   | Section  | Gen  | Step 4: should have, **in       |
| So     |       | 4.1      | eral | bold**, a warning to users that |
| ftware |       |          |      | the **boot:** prompt will be    |
| Note 6 |       |          |      | displayed and that operator     |
|        |       |          |      | needs to type in the "nuke      |
|        |       |          |      | noresize" command before it     |
|        |       |          |      | timeouts.                       |
|        |       |          |      |                                 |
|        |       |          |      | Steps 10 and 11 should be       |
|        |       |          |      | combined to avoid timeouts.     |
|        |       |          |      |                                 |
|        |       |          |      | Step 17: Replace "step 9" with  |
|        |       |          |      | "previous step"                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-6   | Section  | SGX  | Steps 37: Can the default       |
| So     |       | 4.1      |      | Netmask value be set to         |
| ftware |       |          |      | 255.255.0.0? The current value  |
| Note 6 |       |          |      | of 225.225.0.0 is easy to be    |
|        |       |          |      | missed.                         |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-10  | Section  | SGX  | Step 54: Add "Ctrl-C" to get    |
| So     |       | 4.1      |      | out of the ping command.        |
| ftware |       |          |      |                                 |
| Note 6 |       |          |      |                                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-43  | Section  | Gen  | Step 3: Update "/home.crs/.ssh  |
| So     |       | 9        | eral | to "/home/crs/.ssh"             |
| ftware |       |          |      |                                 |
| Note 6 |       |          |      |                                 |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-44  | Section  | Gen  | Step 10: the question prompt    |
| So     |       | 9        | eral | should say:                     |
| ftware |       |          |      |                                 |
| Note 6 |       |          |      | "RSA key fingerprinting is      |
|        |       |          |      | xxxxxxx                         |
|        |       |          |      |                                 |
|        |       |          |      | Are you sure you want to        |
|        |       |          |      | continue connecting (yes/no)?"  |
+--------+-------+----------+------+---------------------------------+
| EHB-7  | A-44  | Section  | Gen  | Step 10: After the operator     |
| So     |       | 9        | eral | responds by a yes, and the      |
| ftware |       |          |      | **known_hosts** is updated, the |
| Note 6 |       |          |      | next step should be a           |
|        |       |          |      | "**quit**" before the **exit**  |
|        |       |          |      | to close the shell.             |
+--------+-------+----------+------+---------------------------------+

[]{#__RefHeading___Toc82480379 .anchor}**Attachment C - CRS Build
10.0/VIP Build 3.1 OAT Test Trouble Reports**

**NUMBER: 891**

Date Entered: 08/11/04

Operation Mode: Full Configuration

Entered by: Lee, Jae

Frequency: Sometimes

Status: CCB Review, assigned to Joel Nathan

Impact: 5 - Minimal to no impact; nice to have

Type of Usage: Operational

Acceptance Test (OAT)

Priority: 3 - Include in a future build

Type of Issue: Modification of existing function / design

Reference: OAT day 1 and day 2

Summary: **[Increase the VIP timeout value under Site Configuration
menu]{.underline}**

Has Workaround:

Subsystem: Voice Improvement Processor (VIP)

Subsys Components:

Software Estimate:

Target Release Build:

Target Release Date:

Development Build:

Operational Build:

Found by: Lee, Jae

Date Found: 08/11/04

Software Version: 10.0

Description:

Around 3 - 4:40pm on August 9, 2004, Mt Holly CRS was very busy with
many products coming in at the same time. HWR, SAF, OFF, CWF, ZFP and
other products were coming from PHI, OKX and WBC. During this time, some
of the products (HWR, SAF) timed out by the VIP. These products were
correctly converted by DECtalk and scheduled in the broadcast cycle.

It seems like the \"60 second\" timeout value is not sufficient for the
VIP to process all the products during this busy time. Therefore,
recommend increasing the timeout value.

NOTE: on August 10 morning, the same problem occurred. We resent
products in

DECtalk voice and these products were converted successfully by the VIP.
We were told 4pm and 4am are the busiest time for CRS.

The VIP log file from 8/9 is attached.

Capture File: None available

Capture Filename and

Date Sent:

Computer Config:

Location/Test Environment:

Attachments: NJ_VIP_Aug\_\_9.log

Assign To: Helderman, Nancy; Nathan, Joel

Assign By: System

Date: 08/11/04

Notes: This assignment was auto generated by TestTrack.

Assign To: Vo, Sung

Assign for analysis By: Nathan, Joel

Date: 08/11/04

Notes:

Comment By: Vo, Sung

Date: 08/12/04

Notes:

The VIP timeout value is controlled and set by the CRS application,
which is now between 10 and 60 seconds. The problem is that if you have
a VIP text message over 2800 bytes long it would take VIP more than 60
seconds to convert the message which the product has timed out after 60
seconds. This VIP timeout

maximum allowable value can be changed to 120 seconds from 60 seconds in
the X-Design resource file without compiling the source codes. However
when you run the Gui2Ascii this value will be saved in the ASCII
database file which is fine but the problem you later run into is when
you do a Site Configure using this ASCII database file. It will fail to
compile due to range check for this value that the current UTsite_cfg.c
only checks for valid value which is between 10 and 60. The error
message \"Voice Conversion Timer = 120 invalid. Valid values are 10-60
seconds\" will be displayed when UTsite_cfg.c fails to compile the ASCII
database file.

The fix for this will be included in the next CRSv11.0 build. There is a
workaround for the current CRSv10.0 but site operator needs to be
guided.

Assign To: Nathan, Joel

Send to CCB By: Vo, Sung

Date: 08/12/04

Notes:

I have completed the analysis for this problem. The fix will be included
in our next CRSv11.0 build.

Created By: Lee, Jae

Date Created: 08/11/04 11:07 AM

Creation Method: Add CRS TTR window

Modified By: Vo, Sung

Date Modified: 08/12/04 01:22 PM

**NUMBER: 893**

Date Entered: 08/18/04

Operation Mode: Full Configuration

Entered by: Viloria, Bert

Frequency: Unknown

Status: CCB Review, assigned to Joel Nathan

Impact: 5 - Minimal to no impact; nice to have

Type of Usage: Operational

Acceptance Test (OAT)

Priority: 5 - Undetermined

Type of Issue: System malfunction (not working as designed)

Reference:

Summary: **[ROAMS More Window displays bad machine
password]{.underline}**

Has Workaround:

Subsystem: Main Processor (MP)

Subsys Components:

Software Estimate:

Target Release Build:

Target Release Date:

Development Build:

Operational Build:

Found by: Viloria, Bert

Date Found: 08/18/04

Software Version: 9.93

Description:

After the successful SGX OAT site routine weekly tests were performed,
ROAMS performed an error dial-in that was displayed on the Alert
Monitor. The OAT site personnel told us that this was something that is
always been happening after RWT.

The ROAMS Query/Modify window was displayed. We were not able to
properly query the data, for either Transmitter, so we decided to view
any saved datasets for Transmitter 1 (SAN) and Transmitter 4 (STP). For
the SAN transmitter, the machine password displayed in the MORE window
was \"NATHAN\^\^\^:\" where \^ equals space.

For the STP transmitter, the machine password displayed in the MORE
window was

\"NATHAN\^4B\". Further verification in the Site Configuration window
revealed that for both transmitters, the passwords were \"NATHAN\".
Additionally, the Site Configuration password field value only allows 8
characters which is violated in the MORE window values for both
transmitters.

Capture File: None available

Capture Filename and

Date Sent:

Computer Config:

Location /

Test Environment:

Attachments:

Assign To: Helderman, Nancy; Nathan, Joel

Assign By: System

Date: 08/18/04

Notes:

This assignment was auto generated by TestTrack.

Assign To: Vo, Sung

Assign for analysis By: Nathan, Joel

Date: 08/18/04

Notes:

Created By: Viloria, Bert

Date Created: 08/18/04 02:11 PM

Creation Method: Add CRS TTR window

Modified By: Nathan, Joel

Date Modified: 08/18/04 02:36 PM

**NUMBER: 894**

Date Entered: 08/21/04

Operation Mode: Full Configuration

Entered by: Viloria, Bert

Frequency: Unknown

Status: Watch, not assigned

Impact: 3 - Degradation of broadcast

Type of Usage: Operational

Acceptance Test (OAT)

Priority: 3 - Include in a future build

Type of Issue: System malfunction (not working as designed)

Reference:

Summary: **[MP3 truncation problem]{.underline}**

Has Workaround:

Subsystem: Not sure or Indeterminate

Subsys

Components:

Software:

Estimate:

Target Release Build:

Target Release Date:

Development Build:

Operational Build:

Found by: Viloria, Bert

Date Found: 08/21/04

Software Version: 9.93

Description:

During the OAT testing at the SGX OAT site, a truncation of an IVR MP3
playback of the ZFPSGX was observed and was duly reported to the field
office. The CRS is properly broadcasting the same message. The OAT
support team and the site personnel are not sure if the truncation
occurred during the VIP remote transfer to the LS1 server or during the
MP3 file transfer from LS1 to the IVR machine. During the whole OAT test
week (Aug 17-19), other than the problem stated above, there were no
other incidence of MP3 file truncations.

Capture File: None available

Capture Filename and

Date Sent:

Computer Config:

Location/ Test Environment:

Attachments:

Assign To: Helderman, Nancy; Nathan, Joel

Assign By: System

Date: 08/21/04

Notes:

This assignment was auto generated by TestTrack.

Assign To: Vo, Sung

Assign for analysis By: Nathan, Joel

Date: 08/23/04

Notes:

Created By: Viloria, Bert

Date Created: 08/21/04 08:00 PM

Creation Method: Add CRS TTR window

Modified By: Nathan, Joel

Date Modified: 08/23/04 03:38 PM

**NUMBER: 900**

Date Entered: 09/10/04

Operation Mode: Full Configuration

Entered by: Viloria, Bert

Frequency: Unknown

Status: Watch, not assigned

Impact: 2 - Prevents message broadcast; reasonable workaround

Type of Usage: Operational Acceptance Test (OAT)

Priority: 5 - Undetermined

Type of Issue: System malfunction (not working as designed)

Reference: WFO EWX

Summary: **[Listening Area reassignment caused scheduling to
stop]{.underline}**

Has Workaround:

Subsystem: Main Processor (MP)

Subsys Components: Software

Estimate:

Target Release Build:

Target Release Date:

Development Build:

Operational Build:

Found by: Viloria, Bert

Date Found: 09/10/04

Software Version: 9.93

Description:

WFO EWX reported that when a listening area transmitter mapping, for a
specific listening area record, has been reassigned, the transmitter
that was removed from the mapping is directly affected. While performing
some listening area reassignments due to a new transmitter, the removed
transmitter mapping caused the \"removed\" transmitter to halt the
scheduling and the Status Window displayed the \"inoperable\" state
(slash across the transmitter icon). The WFO EWX tried to perform
program assignments, reset the MP, and FEPs, but to no avail. The OAT
site then proceeded to manually update their current database ASCII file
and manually remove the mapping. After a successful recompile, the
transmitter and the CRS system resumed normal operations.

Capture File: None available

Capture Filename and Date Sent:

Computer Config:

Location / Test Environment:

Attachments:

Assign To: Helderman, Nancy; Nathan, Joel Assign By: System Date:
09/10/04

Notes: This assignment was auto generated by TestTrack.

Assign To: Helderman, Nancy Assign for analysis By: Nathan, Joel Date:
09/10/04

Notes: Problem is not repeatable at NWSHQ. The following was tested:

1\. Alpha had message type ANCHWRDUT broadcasting on all 13 channels.

2\. From the Broadcast Cycle display, selected channel 13, then clicked

on ANCHWRDUT. Pressed INFO button and it showed that LAC = AKC013

only.

3\. Selected Transmitter and Listening Areas. Found Area Code =

AKC013 - it was assigned to all 13 transmitters. Edited the

transmitters by removing transmitter 13 (STNMR) and Saved.

4\. No problem following this action - the broadcast on all transmitters

continued as before.

Could you contact EWX to see if they can repeat the problem and/or

provide more details about their configuration that may have caused

this?

Created By: Viloria, Bert

Date Created: 09/10/04 11:00 AM

Creation Method: Add CRS TTR window

Modified By: Nathan, Joel

Date Modified: 09/10/04 11:25 AM

[]{#__RefHeading___Toc82480380 .anchor}**Attachment D - CRS Build
10.0/VIP 3.1 OAT Questionnaires**

  --------------------------------------------------------------------------------------------------------------------
  **WFO Philadelphia/Mt Holly OAT                                                                            
  Questionnaire**                                                                                            
  ---------------------------------------------- ---------------- ------- ------- ------------------ ------- ---------
  **Name & Title: Joseph Byerly ESA**            1-Excellent                      4-Deficient                

  **OAT Test Dates: August 9-September 17,       2-Good                           5-Unsatisfactory           
  2004**                                                                                                     

  **Formatters Used: CAFÉ**                      3-Satisfactory                                              

  **Statement**                                  **1**            **2**   **3**   **4**              **5**   **N/A**

  CRS ingest of AWIPS products using listed                                                                 
  formatter(s).                                                                                              

  Installation of CRS Build 10.0 software                                                                   
  (*including password setting and accuracy of                                                               
  installation notes*).                                                                                      

  Installation of VIP Build 3.1 software                                                                    
  (*including accuracy of installation notes*).                                                              

  Installation of CRS/VIP ssh keys (*including                                                              
  accuracy of installation notes*).                                                                          

  CRS ability to successfully send products to                                                              
  NWR transmitters.                                                                                          

  NWR transmitters successfully transmitted CRS                                                             
  products.                                                                                                  

  The quality of the CRS Build 10.0/VIP Build                                                               
  3.1 audio.                                                                                                 

  CRS Build 10.0 automatic password checking                                                                

  VIP Build 3.1 automatic password checking                                                                 

  VIP remote sftp implementation, including any                                                             
  additional support for functional continuity                                                               
  (*only for sites performing VIP remote file                                                                
  transfers*)                                                                                                

  CRS operations with NWRSAME tones, including                                                              
  DMO test event code.                                                                                       

  The CRS Build 10.0/VIP Build 3.1 operators or                                                             
  forecasters workload.                                                                                      

  The CRS Build 10.0/VIP Build 3.1 maintenance                                                              
  workload.                                                                                                  

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  non-severe weather conditions.                                                                             

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  severe weather conditions.                                                                                 

  Overall, CRS Build 10.0/VIP Build 3.1 is                                                                  
  suitable for general implementation.                                                                       
  --------------------------------------------------------------------------------------------------------------------

  --------------------------------------------------------------------------------------------------------------------
  **WFO Austin/San Antonio TX OAT                                                                            
  Questionnaire**                                                                                            
  ---------------------------------------------- ---------------- ------- ------- ------------------ ------- ---------
  **Name & Title: Joseph Baskin CRS FP**         1-Excellent                      4-Deficient                

  **OAT Test Dates: August 10-September 17,      2-Good                           5-Unsatisfactory           
  2004**                                                                                                     

  **Formatters Used: CAFÉ**                      3-Satisfactory                                              

  **Statement**                                  **1**            **2**   **3**   **4**              **5**   **N/A**

  CRS ingest of AWIPS products using listed                                                                 
  formatter(s).                                                                                              

  Installation of CRS Build 10.0 software                                                                   
  (*including password setting and accuracy of                                                               
  installation notes*).                                                                                      

  Installation of VIP Build 3.1 software                                                                    
  (*including accuracy of installation                                                                       
  notes*).[^2]                                                                                               

  Installation of CRS/VIP ssh keys (*including                                                              
  accuracy of installation notes*).                                                                          

  CRS ability to successfully send products to                                                              
  NWR transmitters.                                                                                          

  NWR transmitters successfully transmitted CRS                                                             
  products.                                                                                                  

  The quality of the CRS Build 10.0/VIP Build                                                               
  3.1 audio.                                                                                                 

  CRS Build 10.0 automatic password checking                                                                

  VIP Build 3.1 automatic password checking                                                                 

  VIP remote sftp implementation, including any                                                              
  additional support for functional continuity                                                               
  (*only for sites performing VIP remote file                                                                
  transfers*)                                                                                                

  CRS operations with NWRSAME tones, including                                                              
  DMO test event code.[^3]                                                                                   

  The CRS Build 10.0/VIP Build 3.1 operators or                                                              
  forecasters workload.                                                                                      

  The CRS Build 10.0/VIP Build 3.1 maintenance                                                              
  workload.                                                                                                  

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  non-severe weather conditions.                                                                             

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  severe weather conditions.[^4]                                                                             

  Overall, CRS Build 10.0/VIP Build 3.1 is                                                                  
  suitable for general implementation.                                                                       
  --------------------------------------------------------------------------------------------------------------------

  --------------------------------------------------------------------------------------------------------------------
  **WFO Northern Indiana IN OAT Questionnaire**                                                              
  ---------------------------------------------- ---------------- ------- ------- ------------------ ------- ---------
  **Name & Title: Dereek Adams ITO**             1-Excellent                      4-Deficient                

  **OAT Test Dates: August 17-September 17,      2-Good                           5-Unsatisfactory           
  2004**                                                                                                     

  **Formatters Used: CAFÉ**                      3-Satisfactory                                              

  **Statement**                                  **1**            **2**   **3**   **4**              **5**   **N/A**

  CRS ingest of AWIPS products using listed                                                                 
  formatter(s).                                                                                              

  Installation of CRS Build 10.0 software                                                                   
  (*including password setting and accuracy of                                                               
  installation notes*).                                                                                      

  Installation of VIP Build 3.1 software                                                                    
  (*including accuracy of installation notes*).                                                              

  Installation of CRS/VIP ssh keys (*including                                                              
  accuracy of installation notes*).                                                                          

  CRS ability to successfully send products to                                                              
  NWR transmitters.                                                                                          

  NWR transmitters successfully transmitted CRS                                                             
  products.                                                                                                  

  The quality of the CRS Build 10.0/VIP Build                                                               
  3.1 audio.                                                                                                 

  CRS Build 10.0 automatic password checking                                                                

  VIP Build 3.1 automatic password checking                                                                 

  VIP remote sftp implementation, including any                                                             
  additional support for functional continuity                                                               
  (*only for sites performing VIP remote file                                                                
  transfers*)                                                                                                

  CRS operations with NWRSAME tones, including                                                              
  DMO test event code.                                                                                       

  The CRS Build 10.0/VIP Build 3.1 operators or                                                             
  forecasters workload.                                                                                      

  The CRS Build 10.0/VIP Build 3.1 maintenance                                                              
  workload.                                                                                                  

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  non-severe weather conditions.                                                                             

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  severe weather conditions.                                                                                 

  Overall, CRS Build 10.0/VIP Build 3.1 is                                                                  
  suitable for general implementation.                                                                       
  --------------------------------------------------------------------------------------------------------------------

**[Comments:]{.underline}**

"...*Overall, the new build went very smooth. The knowledge and
expertise of the install team was evident from the beginning through to
the end*..."

  --------------------------------------------------------------------------------------------------------------------
  **WFO San Diego CA OAT Questionnaire**                                                                     
  ---------------------------------------------- ---------------- ------- ------- ------------------ ------- ---------
  **Name & Title: Scott Brookshaw ET**           1-Excellent                      4-Deficient                

  **OAT Test Dates: August 17-September 17,      2-Good                           5-Unsatisfactory           
  2004**                                                                                                     

  **Formatters Used: CAFÉ**                      3-Satisfactory                                              

  **Statement**                                  **1**            **2**   **3**   **4**              **5**   **N/A**

  CRS ingest of AWIPS products using listed                                                                 
  formatter(s).                                                                                              

  Installation of CRS Build 10.0 software                                                                   
  (*including password setting and accuracy of                                                               
  installation notes*).                                                                                      

  Installation of VIP Build 3.1 software                                                                    
  (*including accuracy of installation notes*).                                                              

  Installation of CRS/VIP ssh keys (*including                                                              
  accuracy of installation notes*).                                                                          

  CRS ability to successfully send products to                                                              
  NWR transmitters.                                                                                          

  NWR transmitters successfully transmitted CRS                                                             
  products.                                                                                                  

  The quality of the CRS Build 10.0/VIP Build                                                               
  3.1 audio.                                                                                                 

  CRS Build 10.0 automatic password checking                                                                

  VIP Build 3.1 automatic password checking                                                                 

  VIP remote sftp implementation, including any                                                             
  additional support for functional continuity                                                               
  (*only for sites performing VIP remote file                                                                
  transfers*)                                                                                                

  CRS operations with NWRSAME tones, including                                                              
  DMO test event code.                                                                                       

  The CRS Build 10.0/VIP Build 3.1 operators or                                                             
  forecasters workload.                                                                                      

  The CRS Build 10.0/VIP Build 3.1 maintenance                                                              
  workload.                                                                                                  

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  non-severe weather conditions.                                                                             

  CRS Build 10.0/VIP Build 3.1 operations under                                                             
  severe weather conditions.[^5]                                                                             

  Overall, CRS Build 10.0/VIP Build 3.1 is                                                                  
  suitable for general implementation.                                                                       
  --------------------------------------------------------------------------------------------------------------------

[]{#__RefHeading___Toc82480381 .anchor}**Attachment E - CRS Build
10.0/VIP 3.1 Release Notes**

These notes document the new features and bug fixes incorporated into
CRS Build 10.0 and VIP Build 3.1 Engineering Change Request (ECR)
numbers have been provided to reference a formally documented problem
which has been resolved by this build. Refer to the CRS web page for the
latest Release Notes.

Number range CHAPTER**SOFTWARE ENHANCEMENTS**

1.  **ECR 832: [Support For Externally Generated Voice
    Messages]{.underline}** - Number range CHAPTER**THIS FEATURE WILL
    NOT BE ACTIVATED IN BUILD 10.0. IF CRS BUILD 10.0 RECEIVES AN
    EXTERNALLY GENERATED VOICE MESSAGE, AN ALERT MONITOR ERROR MESSAGE
    WILL BE GENERATED AND THE MESSAGE WILL BE DELETED. IF THIS
    CAPABILITY IS NEEDED IN THE FUTURE TO SUPPORT THE ALL HAZARDS
    COLLECTION SYSTEM, IT WILL BE ACTIVATED AT THAT TIME.** Prior to
    Build 10.0, CRS software only received weather related messages in
    ASCII text format. It processes the messages based on Message
    Attributes stored in the weather message header and system data
    stored in various database tables. These text messages are converted
    from text to speech either using the DECtalk algorithm or using the
    VIP. Prior to Build 10.0, CRS did not provide the capability for
    processing externally generated voice messages.

    Build 10.0 provides the capability to process, schedule, and
    broadcast externally generated voice messages. The CRS weather
    message header Message Attributes include a 5-character Message
    Format code used to identify the format and language of the message.
    Previously, the only Message Formats that could be properly
    processed were "T_ENG" and "T_SPA" for English and Spanish text
    respectively. The Build 10.0 software will process "V_ENG" and
    "V_SPA" for English and Spanish voice. Since these voice files will
    be passed through the DECtalk for broadcast on the transmitter in
    the same manner as manually recorded voice files, either of the
    "voice" Message Formats may be used for both English and Spanish
    externally generated voice files. However, for consistency, we
    recommend the use of "V_ENG" only for all externally generated voice
    files.

> Number range CHAPTERThe following is the format of the message name
> for the externally generated voice messages:
>
> **EV ID \<msg typ ID\> \<msg ID\>**

where \<msg typ ID\> is the internally-assigned numeric Message Type
identifier and \<msg ID\> is the internally-assigned numeric message
identifier of the subject message.

Some restrictions are required for the proper handling of the externally
generated voice files. Because the weather message header must be
extracted in its entirety, the **CTRL-F** and **CTRL-B** sequences are
**not** permitted to be imbedded in the voice file. The new voice
processing software will pass through DECtalk formatted .wav files, i.e.
10K sample .wav files. The software will also recognize and convert
using the SOX utility the more standard 16K sample .wav files. All voice
files must be monaural.

2.  **ECR 831: [Add Special DMO Test NWRSAME Capability]{.underline}** -
    Prior to Build 10.0, CRS did not have the capability to perform the
    DMO Test NWRSAME. This special event code provides the NWS field
    offices a means of conducting exercises to practice issuing
    authentic warnings and other critical messages without disrupting
    the EAS network or turning on receiver codes used by industry and
    the general public. It may also be used as a maintenance aid to
    align and test the communications link.

    The CRS software has been modified to check for special Event Code
    "DMO". If found, CRS will ignore the normal NWRSAME generation of
    UGC codes based on the LACs in the message header. Instead, CRS will
    generate a single code of "999000\". The event code "DMO" should not
    normally be programmed into the receiver decoder, and the location
    code of "999000\" does not match any existing or future geographical
    area codes.

> **Important Note: Even though receiver codes in NWR receivers and EAS
> equipment are not turned on by the DMO Test Message, the complete
> message including the NWRSAME tone will be broadcast by the
> transmitter and received by radios that are already turned on for
> broadcast monitoring. Therefore, sites generating the DMO Test Message
> should not generate the 1050 Hz Alert tone and should include
> appropriate test language in the message.**

3.  **ECR 804: [Replacement Of FTP Transactions With
    SFTP]{.underline}** - The CRS consists of 2 MPs, 2 -4 FEPs, and a
    single VIP. CRS receives specially formatted text messages from
    AWIPS that are placed in a directory on the Master MP for
    processing. Text messages that are flagged to be transformed into
    the Speechify voices (Tom, Donna, and Javier) are sent to the VIP
    for processing. The VIP will convert the text messages to 16K sample
    .wav files. Optionally these .wav files may be directed through LDAD
    to external systems, such as Web Servers, the WR Interactive Voice
    Response (IVR) system, etc. This option also allows for the files to
    be converted via the SOX utility to mp3 files and transferred. After
    the files received from the Master MP are processed, the SOX utility
    is used to convert them 10K sample .wav files, which is the format
    required for DECtalk acceptance. The 10K sample .wav files are
    transferred back to the Master MP, where they are scheduled and
    copied to the shadow MP and FEPs for subsequent transmission.
    Control files are also passed back and forth between the Master MP
    and VIP that allow the transfer of timeout and status information.

    Prior to CRS Build 10.0/VIP 3.1, all the message transactions
    between AWIPS and Master MP, Master MP and VIP, and VIP and external
    systems were via file transfer protocol (ftp). These ftp
    transactions require the passing of the crs user password between
    systems and create security problems that are in violation of the
    DOC Computer Security Policy. Therefore, these transactions will be
    replaced with secure file transfer protocol (sftp). The sftp
    required the passing of authentication keys between the systems
    rather than a password. Because the transition from ftp to sftp in
    CRS Build 10.0 requires close coordination of this same change
    implemented in AWIPS OB4, ftp will remain as an option for
    transactions between AWIPS and the Master MP. This will allow sites
    to install either AWIPS OB4 or CRS Build 10.0 first. **LATEST AWIPS
    UPDATE: PLEASE NOTE THAT BECAUSE OF AWIPS LOADING PROBLEMS, AWIPS
    OB4 WILL NOT BE IMPLEMENTING SFTP. TRANSACTIONS FROM AWIPS TO CRS
    WILL CONTINUE TO USE FTP.** However transactions between Master MP
    and VIP and those between VIP and external systems will only be with
    sftp. For those functions, the ftp function will be removed in CRS
    Build 10.0/VIP Build 3.1.

    The MPs and VIP support openssh connections between themselves and
    AWIPS. This allows for the use of sftp, secure shell (ssh), and
    secure telnet. Authentication keys are needed to authorize these
    transfers or remote sessions. Public and private key files have been
    established on all these processors as part of the installation
    process. The VIP disk recovery procedure continues to be the
    utilization of CD imaging system to restore the disk. The recovery
    procedures will include new steps for the authorization keys.
    Generally, if the CRS application is re-installed, the authorization
    keys remain intact, and no steps to re-establish the keys are
    necessary. However, if the CRS application software is being
    re-installed as the result of an MP hard drive replacement, the keys
    will need to be re-established. Appendix C, CRS Build Installation
    Procedure, has been modified to reflect this fact.

    **Paths:** After the initial CRS Build 10.0 software is installed,
    six or seven connections are defined that support sftp transfers and
    ssh remote sessions. The six required paths are AWIPS to 0MP, AWIPS
    to 5MP, 0MP to VIP, 5MP to VIP, VIP to 0MP, and VIP to 5MP. The
    optional path is VIP to External System.

    **Key Configuration Files:** The sftp transfers and ssh sessions
    require that openssh has configuration data. Public key data must be
    in the files for all the authorized systems that will transfer data
    to the system under configuration. All the public key data used by
    the setup scripts will be in three types of files:

    1\. **Individual Public Data Key Files**: These are mathematical
    data and the public half of a pair of keys. Each key is associated
    with the private key at the originating end of the paths described
    above. These keys are in filenames with extensions of "pub".

    2\. **Authorized Key Files**: These are an aggregate of the public
    key data. These are the individual identity key pairs created for a
    unique user to identify without a password.

    3\. **Known Hosts Key Files:** These are an aggregate of the public
    key data. These are the keys used for computer to computer
    communication during the encryption process.

    A system wide file called **Known Hosts File** also exists as part
    of the system ssh configuration directory. These are the
    configuration files used directly by openssh and contain several
    keys.

    **Key Generation Scripts:** Key generation is done with the contents
    of the public and private mathematical keystring files for openssh
    encryption. The key generation for 0MP and 5MP is done when they are
    first rebooted immediately following the installation of Build 10.0.
    After its initial use, the key generation script is stored on the
    0MP in /etc/config/osdone/sshinstaller.sh. The VIP key generation is
    done in a similar manner. The scripts will not replace key files
    already generated, but will generate new and distinct files if a key
    file is absent. If new keys are generated, the key configuration
    script must be rerun on the MPs and VIP.

    **Key Configuration Script:** This is also called the fixkey script.
    This script will display a fingerprint of the public key files for
    verification and concatenate them together into their respective
    authorized key files. It will then prompt for known hosts
    fingerprints approval and add the approved host public key
    information into the known hosts key files.

    **Fingerprint:** This is a short string of hexadecimal digits in
    ASCII text string format. This check sum of a public key file that
    can confirm the correct key data is used comparing it to a stored,
    printed copy of the fingerprint sequence.

    4\. **ECR 805: [CRS And VIP Automatic Password
    Checking]{.underline}** - Prior to CRS Build 10/VIP Build 3.1, very
    little automatic password checking was performed.

> Number range CHAPTERThe following six rules for password checking have
> been added to the MP, FEP, and VIP systems for all users except root,
> switchmp, and sysadm:
>
> a\. Password must have at least 8 non-blank characters.
>
> b\. Password must contain at least two alphabetic characters.
>
> c\. Password must contain at least one number.
>
> d\. Password must have at least 3 different characters from the old
> password.
>
> e\. Password must differ from the user name, any circular shift of the
> user name, reverse order of the user name, or any reverse circular
> shift of the user name. (Please note that all CRS user accounts
> contain fewer than 8 characters. Therefore, having the user name as
> the password will fail on the restriction described above in (a.).

f\. Password must be changed at least every 90 days.

Additionally, the following four rules for password checking have been
added to the VIP system:

> Number range CHAPTERa. Password must contain at least one upper case
> alphabetic character.
>
> b\. Six of the characters may occur only once in the password.
>
> c\. In addition to the current password, the password cannot be
> changed to the 10 previous passwords. Therefore, the current password
> will not be able to be re-used for the next 11 password changes.
>
> d\. Password cannot contain vendor/manufacturer default passwords,
> words found in any dictionary (forward or backward), addresses,
> birthdays, or common character sequence.

**Additionally, the FEP requires the password contain the two alphabetic
characters**

**and one number within the first 8 characters.**

> Number range CHAPTERBecause of password aging, when the operator logs
> into the CRS GUI or the KDE desktop, a pop-up dialog will display in
> the upper left-hand corner of the display advising him in how many
> days the respective password will expire. The operator must click
> **okay** to continue the login.
>
> **IMPORTANT NOTE: PASSWORDS FOR ALL USERS SHOULD BE CHANGED AT THE
> SAME TIME. THE WARNING AND EXPIRATION MESSAGES WILL ONLY BE SEEN FOR
> THOSE USERS THAT YOU LOG INTO. FOR EXAMPLE, MOST SITES DO NOT LOG IN
> AS CRS USER. THEREFORE, IF THE CRS USER PASSWORD IS GETTING CLOSE TO
> EXPIRATION OR HAS IN FACT EXPIRED, THE OPERATOR MAY NOT SEE THE
> WARNING OR EXPIRATION MESSAGE. THEREFORE, SITES SHOULD MAKE SURE THAT
> WHEN THEY SEE THE PASSWORD WARNING OR EXPIRATION MESSAGE FOR ONE USER,
> THEY CHANGE PASSWORDS FOR ALL USERS FOLLOWING THE PROCEDURES IN
> APPENDIX A OF THE DRAFT SYSTEM ADMINISTRATION MANUAL.**

5\. **ECR 807: [VIP Disk Imaging System Changed To Mondo Image
System]{.underline}** - Prior to VIP Build 3.1, the VIP operating system
and application software distribution, backup, and recovery were
performed using a DOS based package called Drive Image from PowerQuest.
This disk imaging system was difficult to generate the disk image and
very time consuming because it did not directly support the Linux ext3
file systems.

The new Mondo Image System is an open source Linux based package that
has been used previously in other NWS supported Linux systems. It boots
to Linux off a CD (Drive Image required a bootable diskette, and was
itself run from diskette) and can completely restore the VIP operating
system and application to a hard drive. It is Linux based and can more
easily handle the ext3 file systems.

6\. **ECR 808: [CRS Application Changes In MPs To Accommodate SFTP
Transactions With VIP]{.underline}** - Prior to CRS Build 10.0, CRS used
the ftp.ksh script to use the clear text crs user password for ftp
transfer to and from VIP. It also used the chg_emb_pw.ksh script during
CRS application install and when passwords were changed to prompt the
user to enter the crs user password. The chg_emb_pw script placed this
password in the ftp.ksh script and distributed the updated ftp.ksh
script to the other processors.

All references to ftp are changed to sftp. Commands will be accessed
from a dynamically created text file using functionality built into the
sftp so that the previous ftp mechanism is retained. The clear text crs
user password has been removed from the ftp.ksh script. This change also
requires the removal of the chg_emb_pw.ksh script.

7\. **ECR 809: [SFTP Flag Installation On AWIPS]{.underline}** - Prior
to CRS Build 10.0, all the message transactions between AWIPS and the
Master MP were via ftp.

Because the transition from ftp to sftp in CRS Build 10.0 requires close
coordination of this same change implemented in AWIPS OB4, ftp will
remain as an option for transactions between AWIPS and the Master MP.
This will allow sites to install either AWIPS OB4 or CRS Build 10.0
first. When sites install CRS Build 10.0, the installation instructions
will direct the installer to place a marker file in a shared directory
in the AWIPS system. The AWIPS OB4 software will look for that file to
direct it to use sftp for file transfer to CRS. Otherwise, it will
continue to use ftp.

**LATEST AWIPS UPDATE: PLEASE NOTE THAT BECAUSE OF AWIPS LOADING
PROBLEMS, AWIPS OB4 WILL NOT BE IMPLEMENTING SFTP. TRANSACTIONS FROM
AWIPS TO CRS WILL CONTINUE TO USE FTP. THEREFORE, THE MARKER FILE WILL
NOT BE INSTALLED ON AWIPS.**

8\. **ECR 811: [VIP SFTP Changes]{.underline}** - Prior to VIP Build
3.1, VIP used ftp for all message transactions to and from the CRS
Master MP and to external systems (remote ftp).

Libraries have been added to VIP to support the sftp and ssh protocols.
All transactions to and from the CRS Master MP and to external systems
(remote ftp) will now use the sftp protocol. For Master MP/VIP
transactions this includes receipt of VIP text messages, transmittal of
wave files, and receipt/transmittal of status information.

9\. **ECR 813: [CRS SFTP Wrapper]{.underline}** - Prior to CRS Build
10.0, CRS used ftp for both sending/receiving files to/from other
systems. The ftp wrapper used within CRS contains logic that at the end
of the ftp session, signals the CP_AI_RCV binary to look in the
appropriate Master MP directory for a new raw text message.

A similar sftp wrapper has been written to check in the appropriate
directory at the end of the sftp session.

10\. **ECR 815: [Expansion Of Civilian Generated Event Codes
Table]{.underline}** - CRS Build 8.5 included the capability to generate
a SAME originator code for civilian (non-NWS) generated event codes. NWS
generated event codes have an originator code of WXR. The civilian
generated event codes have an originator code of CIV. Build 8.5 defined
a new file on the MPs: /crs/data/SS/SAME_event_codes.dat with the four
civilian generated event codes: CEM, EVI, ADR, and CAE.

The Build 9.0.1 patch distributed in January 2004, added the following
16 additional event codes to the event code table: AVA, AVW, CDW, EQW,
FRW, HMW, LEW, LAE, TOE, NUW, RHW, SPW, VOW, NIC, NPT, and NMN.

Since Build 9.0.1 was implemented as a patch, this write-up is being
included in the Build 10.0 Release Notes to ensure that the updated
/crs/data/SS/SAME_event_codes.dat file is being included in the
ClearCase software build procedure.

**BUG FIXES**

1.  **ECR 833: [Date Time/AWIPS Time Updates Stop/Start Message
    Processing Software]{.underline}** - Date/Time updates and AWIPS
    time request updates generated by the CRS operator from the CRS
    Maintenance menu will always stop the CP_VC process, which is
    responsible for all VIP message processing, which will cause the VIP
    icon in the status window to go down briefly. This is necessary
    since CRS system time updates will affect the processing of incoming
    message effective/expiration time processing. However, the automatic
    stopping and subsequent starting of the VIP message processing
    process may prove to be confusing to the operator.

    The Date/Time Update window has been modified to add the following
    Information Dialog when the operator initiates a time change
    request:

    **Update time will restart VIP interface stop/start cp_vc**

    The operator will be given the opportunity to continue with the
    command or cancel it.

2.  **ECR 834: [Multiple Future Effective Time Watch/Warning Interrupts
    Not Scheduled]{.underline}** - Prior to CRS Build 10.0, multiple
    watch/warning interrupts with effective times in the future were not
    scheduled. For example, suppose the current time was 2200 and a
    severe thunderstorm warning (WBCSVRWBC) was received with an
    effective time of 2210. Then another severe thunderstorm warning
    (WBCSVRWBC) was received before 2210 with an effective time of 2220.
    Normally, the second message should replace the first message.
    However, in this operationally esoteric case, neither the first nor
    second message would ever play.

    The CRS software has been modified to handle this operational
    situation in a more reasonable manner. In the example described
    above, the first message would not play when its effective time was
    reached. Instead, because its effective time was in the future when
    it was received, it will be permanently replaced by the second
    message, thereby ensuring that it will never play. The second
    message will play when its effective time is reached.

3.  **ECR 835: [MMI Display's Font Is Too Small]{.underline}** - Prior
    to CRS Build 10.0, the font used for the Message Monitor (MMI
    display) was Helvetica 7. Middle Aged eyes found this very difficult
    to read. The font has been changed to Helvetica 10.

4.  **ECR 836: [CRS/ROAMS Interface Software Does Not Recognize Local
    10-Digit Dialing Bit]{.underline}** - Prior to CRS Build 10.0, the
    CRS/ROAMS interface software in CRS did not recognize the bit used
    to define local 10-digit dialing. Therefore, the display resulting
    from a Query to a ROAMS set for 10-digit dialing would include a
    garbled area code in the telephone number. For example, a site using
    10-digit dialing with an area code of 785 would display an area code
    of 7185 after the Query.

    The CRS software has been modified to check if the area code is
    overflowed as a result of the 10-digit dialing. If it is overflowed,
    it will offset the area code to adjust the display properly.

5.  **ECR 786: [VIP Processing/Manual Recording
    Collision]{.underline}** - Prior to CRS Build 10.0, it was possible
    to encounter problems while simultaneously manually recording a
    Weather Message (either Weather Message record or Emergency
    Override) and processing a VIP message. This could result in the
    stopping/starting of CRS. If database problems existed, CRS may not
    start successfully, which would require operator intervention to
    clean up the database. As a result, we recommended that sites
    separate the manual record function from the VIP processing
    function, i.e. make sure that all manual recordings are made on ACP2
    (Shadow Console).

    To distribute both digitized voice (manual voice recordings) and VIP
    wave files in a manner that alleviates the collision problems, the
    stream copy client/server logic was rewritten to support two stream
    copy processes. One supports digitized voice messages, the other
    supports VIP wave files. The new logic facilitates the stopping of
    all processing of any VIP message that is being stream copied while
    a digitized voice message is being distributed.

6.  **ECR 806: [VIP OS Security Patches]{.underline}** - When the Harris
    Scan software was performed on the VIP Red Hat Linux Version 7.3, it
    detected four security deficiencies for which patches exist but had
    not been installed. These four security patches and all production
    patch packages available from Red Hat, Red Hat Legacy, and the NOAA
    NCIRT patch server through May 3, 2004 have been applied to VIP
    Build 3.1.

7.  **ECR 810: [Messages With Duplicate LACs Are Not
    Scheduled]{.underline}** - Prior to CRS Build 10.0, messages
    containing duplicate Listening Area Codes (LACs) in the Message
    Attribute Header would result in its failure to be scheduled.
    Additionally, it would result in the generation of a log entry from
    CP_VC concerning DB_MH notification failing, this error message did
    not go to the Alert Monitor. Therefore, the operator would be left
    with a situation where a message was not being scheduled, but no
    operator notification that would indicate what the problem might be.

    The CRS Build 10.0 software includes a new function that performs a
    duplicate check that is used within the LAC parser. This check will
    allow the parser to "skip over" duplicate LACs and process the
    message normally.

    In the course of testing this change, we discovered that the changed
    exacerbated an existing, but never before detected problem. If a
    message incorrectly separates multiple LACs, i.e. using a ","
    instead of "-", the new function will cause the software to enter
    into an infinite loop. This problem has been fixed so the software
    will properly detect the illegal delimiter.

8.  **ECR 812: [Remote FTP Script Changes]{.underline}** - Prior to VIP
    Build 3.1, sometimes the VIPserver would not finish the conversion
    before the ftp put function called in the remote ftp of MP3 files.
    Also, the pre-defined length of the remote ftp string (remote
    username:hostname:password) was not always long enough to support
    what had to be entered.

    The remote ftp script has been modified to insert a 10-second delay
    in the script for the remote ftp of MP3 files. The 23 character
    string limitation has been increased to 32.

9.  **ECR 816: [Remove Spurious Messages From The MMI]{.underline}** -
    Prior to CRS Build 10.0, a number of error messages routinely
    displayed in the MMI, which caused questions and confusion. These
    errors include the following:

    a\. **System not licensed or unregistered software.**

    b\. **Multi-line sendmail errors (unqualified hostname 0mp unknown)
    with retries.**

    CRS Build 10.0 removes both **a** and **b**.

10. **ECR 819: [Multiple Sets of VIPserver Processes May
    Run]{.underline}** - It is possible for the VIP GUI to stop running,
    even though the VIPserver processes continue to run. In this case,
    even though the operator cannot access the VIP control windows, the
    VIP icon in the CRS Status window is up and VIP messages continue to
    be processed. The problem is that the natural reaction to this
    situation is for the operator to restart the GUI. After the GUI is
    up and operating, the main GUI menu will indicate that VIP is down,
    **even though it is not.** Therefore, the natural reaction of the
    operator is to restart the VIP application.

> Now the VIP menu will indicate that VIP is up, and the operator will
> assume all is O.K. Prior to VIP 3.1, when the operator restarted the
> VIP application under these circumstances, he was actually starting a
> second set of VIPserver processes. **When more than one set of
> VIPserver processes are running, the results of the VIP conversion may
> be disastrous.** Both sets of VIPserver processes are processing the
> same message and the results are unpredictable. The converted wave
> file may have long gaps of silence or may play much too fast.

Modifications in VIP Build 3.1 have been made that kill all the old
VIPserver processes when the VIP application is restarted. This prevents
the multiple VIPserver scenario described above.

11. **ECR 821: [SOM Changes]{.underline}** - The Operational Build 9.0
    version of the CRS Site Operator's Manual (SOM) is missing the
    Create ASCII file button on all figures depicting the XCRS_Site
    Configuration Developer screen. Also, Section 3.6.2.5.13 of the SOM,
    Off-Line Tone Generator, does not have language specifically
    instructing the user to close the Transmitter Configure window
    following the disabling of the transmitter and prior to entering the
    Off-Line Tone Generator window.

    The Operational Build 10.0 version of the SOM has been changed to
    include modified Figures 141 - 144 to depict the additional button
    and the language to exit the Transmitter Configure window in the
    appropriate part of Section 3.6.2.5.13. These changes have also been
    included in the on-line Hyper Text Help pages.

12. **ECR 823: [Some Site Identifiers Are Incorrect in the
    VIP]{.underline}** - Prior to VIP Build 3.1, the VIP file
    WFOsites.env had several incorrect entries. This file contains the
    list of approved sites during delivery of new VIP software. Only
    site identifiers in this list may be entered during VIP software
    setup via the Setup Wizard. Once the site identifier is selected, it
    is written to the version file on the VIP. This file is used during
    the configuration of the remote ftp. Therefore, an incorrect sited
    identifier in the WFOsites.env file will contaminate the remote ftp
    configuration.

    The following lists each site, the old identifier, and the new
    identifier in VIP Build 3.1:

    *Site Old ID New ID*

    **Jacksonville, FL KJAN KJAX**

    **Key West, FL KEYN KEYW**

    **NMTW (Alpha) NMTW NMTW**

    **NWSHQ2 (Beta) NNHDA NHDA**

    Also, neither the CRS nor VIP Site Identifier file contained the
    identifiers for the 3 NRC systems. Therefore, CRS Build 10.0 and VIP
    Build 3.1 will modify the respective files to include the 3 NRC
    identifiers as follows:

    *Site Old ID New ID*

    **NRC System 1 NRC1**

    **NRC System 2 NRC2**

    **NRC System 3 NRC3**

Number range CHAPTER13. **TTR 803: [Off-Line Tone Generator Failure To
Write Configuration To Disk]{.underline}** - Prior to Build 10.0, the
CRS Off-Line Tone Generator software did not write changes to tone
amplitude to the transmitter configuration file stored on the MP hard
drive. The changes were correctly made in memory, resulting in the tones
being generated with newly modified amplitude. However, at some later
point in time when the CRS application was terminated and then
restarted, the tone amplitude written into memory from the configuration
file was the old values. Therefore, from that point on the tones would
be generated with the old and incorrect values. This required a work
around in the transmitter alignment procedures to have the user enter
the Transmitter Configure window to save the values (including the tone
amplitudes), since changes in this window were correctly written to the
transmitter configuration file.

> CRS Build 10.0 has been corrected to write the tone amplitude changes
> to the transmitter configuration file.

14\. Number range CHAPTER**TTR 852: [The Save As Function Does Not Work
For Listening Areas and Listening Zones]{.underline}** - The CRS GUI
includes a *File* menu that allows users to access 5 submenu options.
The *Save As* option allows the operator to save the current record
under a new name, thereby maintaining the integrity of the originally
retrieved record. This option may prove useful in creating new records.
For instance, this option could be used in the creation of multiple new
Message Types that are very similar. Once all the parameters for the
first Message Type are entered and saved, it can be used as a template
for the others with the *Save As* option. From most of the GUI windows,
the *Save As* option will cause a pop-up window to display with a prompt
for a new name that is of variable length. However, prior to Build 10.0,
for Listening Areas and Zones, the *Save As* option prompts for a name
that is erroneously restricted to 5 characters, rather than 6. This
erroneous restriction, therefore, makes it impossible to use the *Save
As* function for Listening Areas and Zones.

> The problem is corrected in Build 10.0 by eliminating an incorrect
> decrement of the maximum length field.

Number range CHAPTER

15\. **TTR 856: [Message Record/Playback Dialog Help
Problems]{.underline}** - Clicking on the Help button while in any CRS
window forces the Netscape Communicator to display the SOM documentation
for that window. Prior to Build 10.0, however, the display for the
Weather Message Record/Playback dialog window resulted in the display of
an error window which detailed a lock file error in Netscape. Moreover,
another Netscape was displayed that listed all the Help files. Upon
clicking on the error window OK button, the Record/Playback dialog help
window was displayed. Additionally, clicking on the Help button in the
Weather Message Text Message Playback dialog window resulted in the
display of the Weather Message Correction documentation.

> These problems have been fixed in Build 10.0 so the proper
> documentation is initially displayed.

16\. **TTR 854: [Print Jobs Cannot Be Removed From Print
Queue]{.underline}** - The CRS Print Monitor can be invoked from the CRS
Utilities menu. Upon doing so, the Print Monitor window will be
presented. The currently configured printer and status will be displayed
as part of the window title. From this window, the operator may access,
select, and submit a job to the printer. Several print management
functions also are available to the operator including the ability to
remove a job from the print queue via the Remove Job button. However,
prior to CRS Build 10.0, pressing this button did not properly remove
the print job from the queue. This problem has been fixed in Build 10.0
so print jobs can be removed from the queue.

[^1]: See Section 1.2 for time difference factors.

[^2]: Bad CD Restore #6 caused delay, had to restart the install.

[^3]: DMO may cause problems -- even though DMO doesn't activate the
    alarm, the broadcast is still made. This could lead to an
    embarrassing situation. Not sure if this is a viable situation for
    training.

[^4]: We have sent numerous warnings and watches and have no
    malfunctions.

[^5]: During warning product transmission, the ROAMS "red" alert
    frequently comes up. Not all the time but frequent enough to be
    checked out.