> \- Draft December 15, 2006 --

**Section C - Statement of Work**

**Performance Work Statement**

**For**

**Operations, Maintenance and Technical Support**

**for the U.S. Mission Control Center,**

**Direct Readout, Argos and GOES Data Collection Systems**

Task No. \[TBD\]

**Table of Contents**

[1 Introduction 4](#introduction)

[1 Introduction 4](#__RefHeading___Toc152738957)

[1.1 SARSAT/USMCC 4](#sarsatusmcc)

[1.2 Direct Readout, Argos and GOES DCS
8](#direct-readout-argos-and-goes-dcs)

[2 Scope of Work 9](#scope-of-work)

[2.1 USMCC 9](#usmcc)

[2.2 Direct Readout, Argos and GOES DCS (Optional)
10](#direct-readout-argos-and-goes-dcs-optional)

[2.3 Applicable Documents 10](#applicable-documents)

[3 System Description 11](#system-description)

[3.1 USMCC 11](#usmcc-1)

[3.1.1 Alert Processing 14](#alert-processing)

[3.1.2 Communications Processing 15](#communications-processing)

[3.1.3 System Data Processing 18](#system-data-processing)

[3.1.4 Real-Time System Monitoring 19](#real-time-system-monitoring)

[3.1.5 Operator Interface 19](#operator-interface)

[3.1.6 Interference Monitoring 19](#interference-monitoring)

[3.1.7 Database Maintenance 19](#database-maintenance)

[3.1.8 Incident History Database 19](#incident-history-database)

[3.1.9 Registration Database 20](#registration-database)

[3.1.10 Self-test And Monitoring 20](#self-test-and-monitoring)

[3.1.11 LUT Monitoring Database 20](#lut-monitoring-database)

[3.1.12 SAR Mapping/GEOSORT 20](#sar-mappinggeosort)

[3.2 Direct Readout and Argos and GOES DCS
20](#direct-readout-and-argos-and-goes-dcs)

[3.2.1 Direct Readout 20](#direct-readout)

[3.2.2 Argos DCS System 21](#argos-dcs-system)

[3.2.3 GOES DCS System 21](#goes-dcs-system)

[4 Work Requirements 21](#work-requirements)

[4.1 Operations Support 22](#operations-support)

[4.2 Software Support 23](#software-support)

[4.2.1 USMCC 23](#usmcc-2)

[4.2.2 Direct Readout, Argos and GOES DCS
24](#direct-readout-argos-and-goes-dcs-1)

[4.3 Technical Support 24](#technical-support)

[4.3.1 SARSAT/USMCC 24](#sarsatusmcc-1)

[4.3.2 Direct Readout, Argos and GOES DCS
28](#direct-readout-argos-and-goes-dcs-2)

[5 Processing Environment 28](#processing-environment)

[6 Reporting 29](#reporting)

[7 Travel 30](#travel)

[8 Transition 30](#transition)

[9 Backup USMCC Operations and Maintenance
30](#backup-usmcc-operations-and-maintenance)

[Appendix A -- List of Acronyms 32](#appendix-a-list-of-acronyms)

[Appendix B -- USMCC Requirements Analysis
34](#appendix-b-usmcc-requirements-analysis)

[Appendix 3 -- Performance Requirements
49](#appendix-c-performance-requirements)

[Figure 1: Overview of Cospas-Sarsat System
5](#__RefHeading___Toc152395868)

[Figure 2: Operational Concept of U.S. SARSAT System
8](#__RefHeading___Toc152395869)

[Figure 3: USMCC Hardware 13](#__RefHeading___Toc152395870)

[Figure 6: LUT - USMCC Communication 18](#__RefHeading___Toc152395871)

[Figure 7: International Communication 19](#__RefHeading___Toc152395872)

#   {#section .unnumbered}

# 1 Introduction

This Statement of Work is applicable to the Search and Rescue
Satellite-Aided Tracking (SARSAT) United States Mission Control Center
**(**USMCC**),** satellite direct readout functions, Argos and
Geostationary Operational Environmental Satellite **(**GOES**)** Data
Collection Systems (DCS) which are managed by the National Oceanic and
Atmospheric Administration's (NOAA) National Environmental Satellite,
Data, and Information Service's (NESDIS) Office of Satellite Data
Processing and Distribution (OSDPD).

The SARSAT system relays distress signals from emergency beacons carried
by aviators, mariners and land-based users to search and rescue (SAR)
services. The mission of the interagency SARSAT program is to:

> *Number range CHAPTERProtect life and property by providing timely,
> accurate and reliable distress alerts to search and rescue services
> worldwide in an effective and efficient manner.*

The mission of the SARSAT program is fulfilled by:

-   collecting and distributing reliable and accurate distress alert
    data in a timely fashion using satellite receiving stations and a
    mission control center;

-   coordinating with national and international organizations on
    frequency management, satellite, emergency beacon and search and
    rescue issues;

-   maintaining a national register for 406 MHz emergency beacons; and

-   serving as the lead for SARSAT within the United States, and
    representing the United States in the international Cospas-Sarsat
    Program.

The desired outcome of the SARSAT program is to reduce human risk and
economic consequences as a result of natural or human-induced
emergencies. These activities align with NOAA's goal to support the
Nation's Commerce with Information for Safe, Efficient, and
Environmentally Sound Transportation.

## 1.1 SARSAT/USMCC

Number range CHAPTERThe SARSAT program is part of the international
Cospas-Sarsat System. Cospas is a Russian acronym that stands for
"Cosmicheskaya Systyema Poiska Aariynyich Sudov" which translates
loosely into "Space System for the Search of Vessels in Distress." The
basic concept of the system involves the use of emergency beacons,
satellites, and ground equipment to relay distress location and
identification information (referred to as distress alerts) to SAR
authorities. SAR instruments are flown on low-Earth polar orbiting (LEO)
and geostationary-orbiting (GEO) satellites provided by the United
States, Russia, India and the European Organization for the Exploitation
of Meteorological Satellites (EUMETSAT). Canada and France provide the
SAR instruments (the Search and Rescue Repeater and the Search and
Rescue Processor) for the U.S. LEO satellites. These instruments are
capable of detecting signals on the Earth's surface transmitted from
emergency beacons. Emergency beacons include Emergency Locator
Transmitters (ELTs), Emergency Position Indicating Radio Beacons
(EPIRBs), Personal Locator Beacons (PLBs), or Ship Security Alerting
System (SSAS) beacons. ELTs are primarily used by aircraft, EPIRBs by
maritime vessels, PLBs by individuals on land, and SSAS beacons are used
by ships to alert authorities of piracy/terrorism activity.

Emergency beacons may operate on the 121.5, 243 or 406 MHz frequencies.
121.5/243 MHz beacons transmit an analog signal that does not contain
any information about the beacon or user. Alternatively, the 406 MHz
beacons transmit a digital code that contains information about the type
of beacon and possibly the location of the beacon (derived from the
Global Positioning System, GPS, or other navigational system). Each 406
MHz beacon in the world has a unique identifier. The unique identifier
allows for additional information called registration data to be linked
to each beacon. After receipt of ELT, EPIRB or PLB signals by the
satellite, the satellite relays the signals to earth stations referred
to as Local User Terminals (LUTs).

The LUT, after computing the location of the emergency beacon using the
Doppler Effect, transmits an alert message to its respective Mission
Control Center (MCC) via a data communication network. The MCC performs
matching and merging of alert messages with other received messages,
geographically sorts the data, and transmits a distress message to an
appropriate search and rescue authority such as a national Rescue
Coordination Center (RCC) or a foreign SAR Point of Contact (SPOC). The
distress message may also be sent to another MCC. Figure 1 describes the
Cospas-Sarsat System.

![](media/image1.png){width="1.2708661417322835in"
height="0.4779527559055118in"}![](media/image2.png){width="0.9165354330708662in"
height="0.7374015748031496in"}![](media/image3.wmf){width="0.4145669291338583in"
height="0.49921259842519683in"}![](media/image4.png){width="1.1251968503937009in"
height="0.27913385826771653in"}

[]{#__RefHeading___Toc152395868 .anchor}Figure 1: Overview of
Cospas-Sarsat System

The United States operates two types of satellites and LUTs to relay
distress signals. SAR instruments are carried on board the NOAA Polar
Orbiting Environmental Satellite (POES) and GOES series of satellites.
The POES satellites orbit the Earth at an altitude of approximately 850
kilometers and orbit the Earth once every 102 minutes. The relative
motion between the POES or LEO satellites and a beacon on the surface of
the Earth allows ground processing to use the Doppler Effect to
determine the beacon's location. The GOES satellites orbit the Earth in
a geosynchronous orbit, which means they orbit the equatorial plane of
the Earth at a speed matching the Earth\'s rotation. This allows them to
"hover" continuously over one position on the surface. The
geosynchronous plane is about 36,000 kilometers above the Earth, high
enough to allow the satellites to view approximately 1/3 of the Earth.
Because the GOES or GEO satellites stay above a fixed spot on the
surface, they provide a constant vigil for emergency beacons activated
within their footprint.

NOAA manages and operates Low-Earth Orbiting Search and Rescue (LEOSAR)
system LUTs (LEOLUTs) to track, receive and process alerts from the
POES, European Meteorological Operational (METOP) satellites, and the
Russian Nadezhda satellites. Dual LEOLUTs are located at Andersen Air
Force Base (AFB) on Guam, at the U.S. Coast Guard (USCG) communication
station on Hawaii, at the NOAA Command and Data Acquisition station in
Alaska, Vandenberg AFB in California and the USCG communication station
in Florida. Dual LEOLUTs at each site allow NOAA to resolve satellite
tracking conflicts and provides redundancy in case of failure. NOAA also
manages and operates two Geostationary-Earth Orbiting Search and Rescue
(GEOSAR) LUTs (GEOLUTs) in Suitland, Maryland to track, receive and
process alerts through the GOES East and GOES West satellites. Both sets
of LUTs perform error detection and correction on 406 MHz beacon
messages and automatically generate alert messages to the USMCC.
Additionally, one LEOLUT and GEOLUT in Maryland serve as backup
equipment and test beds.

The USMCC receives alert data from national LUTs and foreign MCCs. It
matches beacon signals to identify those coming from the same source and
merges them to improve position accuracy. The USMCC appends registration
information to distress alerts for 406 MHz beacons registered in the
United States then geographically sorts data to determine the
appropriate recipient -- a national RCC (operated either by the U.S. Air
Force, USAF, or USCG), foreign SPOC or MCC. Based on special coding the
USMCC also transmits distress alerts to a number of special Government
and military users. The USMCC filters redundant data and performs system
support and monitoring functions. System support functions include
relaying SAR instrument telemetry from the Environmental Satellite
Processing Center (ESPC) to the Canadian MCC (CMCC) and the French MCC
(FMCC) and relaying SAR instrument commands from the CMCC and FMCC to
the Satellite Operations Control Center (SOCC). The U.S. LEOLUTs and the
USMCC have the capability to detect and locate interference in the 406
MHz band. This information is automatically forward to the Federal
Communications Commission (FCC) for further investigation. Also
supporting the operations of the LUTs is the receipt of timing
information from GPS satellites or from the National Institute of
Standards and Technology. Figure 2 provides an overview of the U.S.
SARSAT system.

![](media/image5.jpeg){width="0.6251968503937008in"
height="0.8429133858267717in"}![](media/image6.png){width="0.8326771653543307in"
height="0.3590551181102362in"}![](media/image7.png){width="0.6779527559055119in"
height="0.3480314960629921in"}![](media/image3.wmf){width="0.36023622047244097in"
height="0.4334645669291339in"}![](media/image3.wmf){width="0.36023622047244097in"
height="0.43543307086614175in"}

[]{#__RefHeading___Toc152395869 .anchor}Figure 2: Operational Concept of
U.S. SARSAT System

Cospas-Sarsat's ultimate mission is to assist in the saving of human
lives. More than 20,000 persons have been rescued due to the
Cospas-Sarsat Program since its inception in 1982. The current
Cospas-Sarsat Program was established by an inter-governmental agreement
signed in 1988 between the

Governments of Canada, the Republic of France, the former Soviet Union
(now replaced by the Russian Federation) and the United States. The
agreement created the Cospas-Sarsat Council, which is responsible for
overall management of the Program, and the Cospas-Sarsat Secretariat,
which serves as the permanent administrative organ of the Program.

The Joint Committee (JC), Operational Working Group (OWG), Technical
Working Group (TWG) and Task Groups, have been established to support
the Council. The JC, OWG, TWG, and Task Groups meet once a year to
address operational and technical issues and make recommendations to the
Council. To date, 37 nations, and two organizations are formally
associated with the Cospas-Sarsat Program.

The Cospas-Sarsat Program is guided by System documentation that
provides technical specifications for equipment, operational procedures
and program structure. The documentation is separated into six series:

-   The "P" series contains documents that pertain to the management and
    policy of the Cospas-Sarsat Program.

-   The "B" series contains general information documents such as
    information bulletins.

-   The "G" series contains general information.

-   The "T" series contains technical documentation and specifications.

-   The "A" series contains operational documentation and procedures.

-   The "R" series contains reports and system test plans.

The documentation listed above can be found at
[www.Cospas-Sarsat.org](http://WWW.Cospas-Sarsat.org/) under the
documentation link.

The USMCC functions in accordance with specifications and procedures
outlined in the above documents. In addition, the USMCC has to meet
unique national requirements to fulfill its mission. These requirements
are contained in documentation referenced in section 2.3.

## 1.2 Direct Readout, Argos and GOES DCS

NOAA has the lead responsibility for managing Federal space-based civil
operational Earth observing systems necessary to meet civil
requirements. OSDPD is the focal point in the U.S. Government for the
NOAA direct readout service. NOAA direct readout activity provides
coordination and support for satellite data access and assists in
planning and evaluating changes to the next generation of NOAA
satellites by identifying user requirements and providing
recommendations. Direct readout activity also serves as a NOAA liaison
keeping its satellite user community informed of operational changes and
providing information to the global meteorological community with the
intention of facilitating international coordination and cooperation.
The following website contains more information on NOAA' direct readout
activity:

<http://noaasis.noaa.gov/NOAASIS/> .

The Argos DCS Number range CHAPTERoperates on the POES constellation and
was established through a Memorandum of Understanding (MOU) with France
in 1974. NOAA for the U.S. and the Centre Nationale d\'Etudes Spatiales
(CNES) for France are the lead agencies for this international
cooperative agreement. CNES provides for the development and delivery of
the Argos DCS instrument. NOAA provides spacecraft integration/launch
services, downloads stored mission data via NOAA Command Data
Acquisition facilities and provides pre-processed data delivery. Data
post-processing and delivery to customers is the responsibility of CNES,
which through a subsidiary maintains distribution centers located in
Toulouse, France and Largo, Maryland. OSDPD represents NOAA as the U.S.
Co-chair and the U.S. Secretariat to the Operations Committee (OPSCOM).
In conjunction with the OPSCOM, OSDPD provides overall program
management such as system access review and approval of System Use
Agreements, policy development and implementation, and future satellite
planning to meet customer requirements. Access to the Argos DCS is
governed by U.S. regulations 15 CFR Part 911 "Polices and Procedures
Concerning Use of the NOAA Space-Based Data Collection Systems" and
managed with the Argos System Use Agreement Database System.

The GOES DCS is a data relay system that transmits surface based
observations through a satellite to achieve almost real time
observations. The DCS transmitters send their messages in an assigned
channel and time slot to the GOES satellite. The messages are then
down-linked to a ground receiving station, where the owner and other
users can pick them up within approximately 5 seconds of transmission.
The GOES DCS program management and customer service functions take
place in Suitland, Maryland. Data ingest and limited processing take
place in Wallops, Virginia. Both the Suitland and the Maryland sites
host computer systems that perform specific functions. The system that
currently runs at Wallops is a Data General system, vintage 1989, which
maintains information about each of the 25,000 platforms that operate on
the system, and the users who operate them; scheduling information;
platform performance statistics, and general health of the system
information. The Suitland systems are all desk top systems, and include
a vintage address generation system, a more modern address generation
system (still under development), a data base system to collect contact
information for users, and various spreadsheet tools used to more easily
query and/or manipulate the information contained in the primary
database. Additionally, plans are underway to host a backup distribution
site at a remote site. While this site will be operated by a user
agency, NOAA will have a supporting role. More information on the GOES
DCS system can be found at <http://noaasis.noaa.gov/DCS> and
[http://dcs.noaa.gov](http://dcs.noaa.gov/).

# 

# 2 Scope of Work

This Statement of Work defines the required support for computer
operations, software support, and technical support for the USMCC. It
also defines the required software maintenance and technical support for
the Direct Readout system, Argos and GOES DCS systems.

## 2.1 USMCC

The contractor shall provide computer operations of the USMCC system on
an around-the-clock basis, as well as data entry and database
administration functions. These functions shall be performed onsite at
the NOAA Satellite Operations Facility (NSOF) in Suitland, Maryland, or
at its backup facility at Wallops Island, VA. Software support shall
consist of corrective, adaptive and perfective maintenance to support
the USMCC mission. Technical support shall include maintaining IT
hardware and system software, supporting IT security activities,
performing analysis, and supporting national and international meetings.
All of these activities help sustain the USMCC mission. Software and
technical support activities shall be performed at either the NSOF or
the NOAA Science Center. The document "USMCC Requirements Analysis,"
provided at Appendix B, provides additional reference material to assist
the contractor in understanding the USMCC mission. It is provided for
reference only.

## 2.2 Direct Readout, Argos and GOES DCS (Optional)

The contractor shall provide software and technical support of the
Direct Readout, Argos and GOES DCS systems. The contractor shall
administer database maintenance functions for which OSDPD is currently
responsible. These functions shall be performed onsite at the NOAA
program office responsible for Direct Readout, Argos and GOES DCS in
Suitland, Maryland, or at a future backup facility. Software support
shall consist of corrective, adaptive and perfective maintenance to
support the Direct Readout, Argos and GOES DCS mission. Technical
support shall include maintaining IT hardware and system software.

## 2.3 Applicable Documents

The following documents define terms, requirements, guidelines,
specifications, procedures, data formats and content, and plans. Unless
otherwise specified, all USMCC relevant work shall be performed in
accordance with these documents. Succeeding revisions shall be
substituted or incorporated as appropriate. The Cospas-Sarsat documents
can be viewed under the documentation link of
<http://www.cospas-sarsat.org/>.

USMCC documents can be viewed at the System Documentation link of
<http://www.sarsat.noaa.gov/>.

-   C/S G.003, Introduction to the Cospas-Sarsat System

-   C/S G.004, Cospas-Sarsat Glossary

-   C/S G.005, Cospas-Sarsat Guidelines on 406 MHZ Beacon Coding,
    Registration, and Type Approval

-   C/S T.001, Specification for Cospas-Sarsat 406 MHZ Distress Beacons

-   C/S A.001, Cospas-Sarsat Data Distribution Plan

-   C/S A.002, Cospas-Sarsat Mission Control Centers Standard Interface
    Description

-   C/S A.003, Cospas-Sarsat System Monitoring and Reporting

-   C/S A.005, Cospas-Sarsat Mission Control Center Performance
    Specification and Design Guidelines

-   C/S A.006, Cospas-Sarsat Mission Control Centre Commissioning
    Standard

-   USMCC Functional Requirements Document

-   USMCC Data Structures Document

-   USMCC Functional Description Document

-   406 MHz Registration Data Base (RGDB) Functional Requirements
    Document

-   Incident History Data Base (IHDB) Functional Requirements Document

-   USMCC Standard Operating Procedures

-   USMCC National Rescue Coordination Center and Search and Rescue
    Point of Contact Alert and Support Messages

-   SARSAT Configuration Management Plan

Applicable documents for the GOES DCS system include:

-   Office of Federal Coordinator for Meteorological Services and
    Supporting Research - National Geostationary Operational
    Environmental Satellite (GOES) Data Collection System (DCS)
    Operations Plan, FCM-P28-1997

-   NOAA Technical Memorandum NESDIS 40, The Geostationary Operational
    Environmental Satellite Data Collection System

-   User Interface Description and HTML Prototype for Argos System Use
    Agreement Document

# 3 System Description

## 3.1 USMCC

The USMCC is a distributed system comprised of 11 PC-based software
sub-systems as depicted in Figure 2. The USMCC exchanges more than 5,500
data and alert messages a day and ingests beacon data from approximately
250 LEO satellite passes a day. Beacon data is received from the GEO on
a continuous basis. There are more than 20 Structured Query Language
(SQL) database transactions per second.

The USMCC operates under Windows 2000/2003 operating system
environments. Commercial off the Shelf (COTS) software such as MapInfo,
MS SQL, Visual Basic, C++, Visual C++, Java, Netscape Navigator, and
dBase are also an integral part of the software sub-systems. The
languages used in the USMCC system include Visual BASIC, SQL, MapInfo,
Visual C++, and JAVA. The USMCC operates on an around-the-clock basis as
part of the operational Cospas-Sarsat Program. Table 1, Figure 2, and
Figure 3 show the hardware elements of the USMCC.

Table 1: USMCC Hardware List

  -----------------------------------------------------------------------
  **Machine Name**                   **Hardware Type**
  ---------------------------------- ------------------------------------
  **MCC**                            

  MCCOPS1                            DELL PRECISION 340

  MCCOPS2                            DELL PRECISION 340

  MCC TIMESERVER                     SYMMETRICOM NTS-150

  MCCDISPLAY                         DELL POWEREDGE 2850

  MCCSEC                             DELL POWEREDGE 2850

  MCCPRIM                            DELL POWEREDGE 2850

  MCCFTP2                            DELL POWEREDGE 2850

  MCCFTP1                            DELL POWEREDGE 2850

  FTPIDS                             DELL POWEREDGE 2850

  FTPMONITOR                         DELL POWEREDGE 2850

  MCCDB2A                            DELL POWEREDGE 2850

  MCCDB2B                            DELL POWEREDGE 2850

  MCCPROC2                           DELL POWEREDGE 2850

  MCCPROC1                           DELL POWEREDGE 2850

  MCCCOM2                            DELL POWEREDGE 2850

  MCCCOM1                            DELL POWEREDGE 2850

  MCCDB1A                            DELL POWEREDGE 2850

  MCCDB1B                            DELL POWEREDGE 2850

  MCCDB2                             DELL POWERVALUT 220S

  MCCDB1                             DELL POWERVAULT 220S

  FAXBACKSERVER                      DELL POWEREDGE 2550

  MCCIDS                             DELL POWEREDGE 2850

  MCCMONITOR                         DELL POWEREDGE 2850

  MCCARCHIVEDB                       DELL POWEREDGE 2850

  MCC FIREWALL                       CISCO PIX 515

  MCC FAILOVER FIREWALL              CISCO PIX 515

  ROUTER USMCC-A                     CISCO 2621

  ROUTER USMCC-B                     CISCO 2621

  ROUTER FAX                         CISCO 2621

  ROUTER MAN                         CISCO 2851

  VPN CONCENTRATOR                   CISCO VPN 3020

  MCC SNAP DRIVE                     SNAP APPLIANCE SNAP SERVER 4500

  MCCDMZ SNAP DRIVE                  SNAP APPLIANCE SNAP SERVER 4500

  LUT SERVER TIMESERVER              SYMMETRICOM NTS-150

  LUT SERVER FIREWALL                CISCO PIX 525

  LUT SERVER FAILOVER FIREWALL       CISCO PIX 525

  ROUTER MANAGEMENT                  DELL POWEREDGE 2650

  LUT SERVER SNAP DRIVE              SNAP APPLIANCE SNAP SERVER 4500

  LUT SERVER IDS                     DELL POWEREDGE 2850

  LUT SERVER MONITOR                 DELL POWEREDGE 2850

  LUT SERVER FTP2                    DELL POWEREDGE 2850

  LUT SERVER FTP1                    DELL POWEREDGE 2850

  7 LAN SWITCHES                     HP PROCURVE2824

  3 HUBS                             2 HP PROCURVE/1 3COM

  KVM SWITCH                         AVOCENT

  2 KMM USER STATIONS                AVOCENT

  4 KMM                              AVOCENT

  WEB                                

  RGDB FTP SERVER                    DELL POWEREDGE 2650

  RGDB WORKSTATION                   DELL POWEREDGE 1650

  RGDB MONITOR                       DELL POWEREDGE 2650

  APPSERV2                           DELL POWEREDGE 2550

  WEBSERVDEV                         DELL POWEREDGE 2450

  DC1                                DELL POWEREDGE 2550

  DC2                                DELL POWEREDGE 2550

  WEBSRV                             DELL POWEREDGE 2550

  NOAAIDS                            DELL POWEREDGE 350

  RGDB FTP                           DELL POWEREDGE 2650

  APPSERVDEV                         DELL POWEREDGE 2650

  APPSERV                            DELL POWEREDGE 6650

  WEB SNAP DRIVE                     SNAP APPLIANCE SNAP SERVER 4500

  VPN CONCENTRATOR                   CISCO VPN 3020

  2 FIREWALLS                        CISCO PIX 515E

  FAILOVER FIREWALL                  CISCO PIX 515E

  ROUTER MAN                         CISCO 2851

  RGDB DOCUMENT IMAGE SERVER         HP ML 370

  2 LAN SWITCHES                     HP PROCURVE2824

  HUB                                HP PROCURVE

  KVM SWITCH                         AVOCENT

  KMM USER STATION                   AVOCENT

  2 KMM                              AVOCENT
  -----------------------------------------------------------------------

![](media/image1.wmf)

[]{#__RefHeading___Toc152395870 .anchor}Figure 3: USMCC Hardware

The number of lines of code for each sub-system is contained in Table 2.
The functions of each sub-system are described in the sections below.

**Table 2: USMCC Software Lines of Code**

+-------------------+-------------+---------------------+-------------+
| **Sub-system**    | **Lines of  | **Sub-System**      | **Lines of  |
|                   | Code**      |                     | Code**      |
+===================+=============+=====================+=============+
| Alert             | 40,339      | Database/Data       | 1,063       |
|                   |             | Maintenance         |             |
| Processing        |             |                     |             |
|                   |             | (DBMN)              |             |
| (ALRT)            |             |                     |             |
+-------------------+-------------+---------------------+-------------+
| Communications    | 25,836      | Incident History    | 54,507      |
| Processing        |             | Database            |             |
|                   |             |                     |             |
| (COMM)            |             | (IHDB)              |             |
+-------------------+-------------+---------------------+-------------+
| System Data       | 16,816      | Registration        | 77,487      |
| Processing        |             | Database            |             |
|                   |             |                     |             |
| (SDAT)            |             | (RGDB)              |             |
+-------------------+-------------+---------------------+-------------+
| Real Time System  | 5,101       | Self‑test And       | 12,071      |
| Monitoring        |             | Monitoring          |             |
|                   |             |                     |             |
| (SMON)            |             | (SAMS)              |             |
+-------------------+-------------+---------------------+-------------+
| Operator          | 54,144      | LUT Monitoring      | 20,953      |
| Interface         |             |                     |             |
|                   |             | Database            |             |
| (OPER)            |             |                     |             |
|                   |             | (LMDB)              |             |
+-------------------+-------------+---------------------+-------------+
| Interference      | 70,203      | SAR Mapping/Geosort | 41,848      |
| Monitoring (INTF) |             |                     |             |
|                   |             | (SMAP)              |             |
+-------------------+-------------+---------------------+-------------+
| Miscellaneous     | 1,631       |                     |             |
+-------------------+-------------+---------------------+-------------+

### 3.1.1 Alert Processing

The Alert Processing sub-system is the major component of the USMCC. The
sub-system processes all distress alert data and produces the distress
alert messages destined for other MCCs, SPOCs and RCCs. Specifically,
the Alert Processing:

-   transfers all 121.5, 243, 406 MHZ alert data from the SQL server;

-   validates all incoming alert data;

-   filters alert data based on configuration;

-   creates sites (sites combine and store satellite data originating
    from a unique beacon or signal source);

-   matches alerts from different sources (LUTs/MCCs and/or satellites);

-   merges beacon alerts from different sources to form a more probable
    position;

-   determines if satellite passes should have detected a beacon on a
    given pass;

-   determines the type of message to send;

-   determines the appropriate recipient of the alert message;

-   determines the content of alert messages;

-   appends registration information for 406 MHZ beacons as appropriate;
    and

-   performs housekeeping on the site.

The Alert Processing sub-system notifies the operator of alarm
conditions and general status of the sub-system, as well as logs all
routine operations and functions for later analysis.

### 3.1.2 Communications Processing

The Communications sub-system communicates with U.S LUTs, foreign MCCs,
SPOCs, and national RCCs for alert and system data. It also communicates
with the Naval Bulletin Board (NBB) by way of telephone line for
ephemeris data, the National Institute of Standards and Technology
(NIST) by way of the Internet for time data, the ESPC by way of the
Internet for satellite payload telemetry data, the GPS via satellite
receiver for time data, and a communication vendor. The Communications
Processing sub-system also formats alert messages based on the
destination.

The primary path of data communications between the USMCC and USCG RCCs
is through a frame relay network provided by SPRINT. Backup data
communications between the USMCC and USCG RCCs is through a facsimile
server. See Figure 4.

![](media/image1.wmf)

The primary data path between the USMCC and USAF RCC at Langley AFB is
the Internet and the backup path is the SPRINT frame relay network. See
Figure 5.

![](media/image1.wmf)

The primary data path between the USMCC and national LUTs is also the
SPRINT frame relay network. Dialed backup telephone lines are used for
backup. See Figure 6.

![](media/image1.wmf)

[]{#__RefHeading___Toc152395871 .anchor}Figure 6: LUT - USMCC
Communication

The USMCC communicates with other nations' MCCs through the Aeronautical
Fixed Telecommunications Network (AFTN), and the Internet. The USMCC
communicates with foreign SPOCs through the AFTN, and the Public
Switched Telephone Network (PSTN) for facsimile. See figure 7 for a
description of international communications.

![](media/image1.wmf)

[]{#__RefHeading___Toc152395872 .anchor}Figure 7: International
Communication

### 3.1.3 System Data Processing

The System Data sub-system is responsible for processing satellite
payload telemetry data, identifying out-of-limit conditions and
reporting to the appropriate payload provider (i.e., France or Canada),
and notifying the payload providers of changes in the status of their
instruments. The sub-system processes commands from the French and
Canadian MCCs, and routes them to the NOAA Satellite Operations Control
Center in Suitland, Maryland.

The System Data sub-system also creates ephemeris data to send to
foreign MCCs and U.S. LUTs. In addition, the sub-system creates pass
schedules daily for the U. S. LUTs. Pass schedules are used by the LUTs
to determine which satellites will be tracked. Lastly, the sub-system
creates and processes system status and narrative messages for and from
foreign MCCs.

### 3.1.4 Real-Time System Monitoring

The System Monitoring sub-system performs real-time monitoring of the
USMCC, national LUTs, and communications links. The sub-system ensures
that all the critical USMCC sub-systems are functioning and LUTs are
providing data. The sub-system also monitors the performance of LUTs by
reporting on large location errors.

### 3.1.5 Operator Interface

The Operator Interface allows the operator to monitor the USMCC system,
retrieve data, perform queries, initiate processes, access other
sub-systems as appropriate, and change configuration of the USMCC
system. The operator has the capability to search for alert data based
on type of data, geographic location and time. The results of the query
can then be transmitted to any destination. The operator can also search
for input or output messages based on specific criteria, and can access
system logs. The Operator Interface sub-system contains the NOAA
encode/decode software for 406 MHZ beacons. This software allows users
an interface to the digital information contained in a 406 MHZ message.
The software can also perform error checking on the digital message as
described in Cospas-Sarsat documentation.

### 3.1.6 Interference Monitoring

The Interference Monitoring sub-system processes 406 MHz interference
position data from U.S. LUTs and foreign MCCs. Interference data is
matched and merged similar to 121.5/243 MHz alert data and reports on
sources of interference generated.

### 3.1.7 Database Maintenance

The Database Maintenance sub-system performs the archive, purge and
backup of all data as well as monitors database performance. All data is
archived at the USMCC. Backups are performed daily and all software and
data is archived monthly.

### 3.1.8 Incident History Database

The Incident History Database sub-system is comprised of software to
transfer key site information from the active site database to the
Incident History Database. Software also exists to input/edit feedback
from RCCs either manually or online, validate feedback and send
reminders to RCCs for incidents on which they have not reported.

Software also exists to extract "Distress Incident Report for
Documentation of Saves" and "Report on Beacon Signals" for the
Cospas-Sarsat System. Additional software exists to prepare reports on
performance of beacon models, compliance of feedback by RCCs, and report
of rescues.

### 3.1.9 Registration Database

The Registration Database sub-system is comprised of software to enter,
edit, delete beacon registrations and to prepare reports. The software
validates information before it is accepted into the database; creates
mailing labels; generates bi-annual confirmations; and creates decals to
be affixed to the beacon.

### 3.1.10 Self-test And Monitoring

The Self-test and Monitoring Sub-system (SAMS) provides near real-time
and long term and trend monitoring from data collected at the USMCC.
Information on availability and performance is generated for the USMCC,
U.S. LUTs and Cospas-Sarsat satellites. The sub-system also generates
graphics files for display and reports.

### 3.1.11 LUT Monitoring Database

The LUT Monitoring Database maintains the daily schedule of satellite
passes that the U.S. LUTs have been scheduled to track, and reports on
the outcome of each satellite pass per LUT. The information is used to
monitor LUT performance and report on missed passes, create
Cospas-Sarsat reports on availability, and assist in the determination
of monthly payment to the LUT maintenance contractor.

### 3.1.12 SAR Mapping/GEOSORT

The SAR Mapping sub-system performs the geographical sorting of alert
data for the Alert Processing sub-system. The software determines in
whose search and rescue area an alert position is located. The software
also provides the real-time geographical display of alert sites.

Additional information on the USMCC may be found in the documents listed
in section 2.3.

## 3.2 Direct Readout and Argos and GOES DCS

### 3.2.1 Direct Readout

The Direct Readout System will serve as a knowledge base for NOAA
Satellite and Information Services to interface with the direct readout
community, obtain insight on the quality of the NOAA broadcast services,
and gather input for future environmental services. The database will
also serve as a tool to enable NOAA Satellite and Information Services
to relate service changes to the users more efficiently and identify
user issues on service modifications. The objective of the web based
system is to provide NOAA Satellite and Information Services a database
of active and potential direct readout users, equipment and
manufacturers. This system is in the process of being developed.

### 3.2.2 Argos DCS System

The Argos electronic Service User Agreement (SUA) system requires
importing data from the commercial Argos organizations, CLS and Service
Argos Inc., via e-mail into the new NOAA SUA database and then
implementing a web-based workflow management system to support the NOAA
internal approval process. The system provides a web page summary to the
public and a private web site for the approval process. To access a
private web site, the user is authenticated to the system via user ID
and password. The public web site does not have password protection and
is the home page for the system. The approval pages and their functional
requirements are listed in User Interface Description and HTML Prototype
for Argos System Use Agreement Document (January 25^th^ 2002). The
approval process is supported by an e-mail notification system, which
alerts different level approvers that action is required.

### 3.2.3 GOES DCS System

The purpose of the GOES DCS System is to provide electronic input,
tracking, and work order processing of applications to use the GOES DCS
system. The approval process is similar to that of the Argos system, in
that it requires an e-mail notification system to alert different level
approvers that action is required. Potential users of the system access
a public web page, and submit an application similar to the Argos
application, which must then be reviewed by various levels of personnel
to complete the approval process. Users will submit applications on line
via the public web site, and NOAA personnel will be alerted to access
the approval pages, which will be password protected. The system will
have the capability to generate reports and statistics/metrics from the
user database generated by the system. The contractor shall generate
these reports on request. The contractor shall provide maintenance
support for this system, and other tools developed for the management of
the GOES DCS system, including an address generation system, a user
contact data base, tracking tools for assignments and realigning of
channels and resources, and for monitoring of and reporting from the DCS
Automated Processing System (DAPS), located at the Wallops Island CDA.
This system is in the process of being developed.

# 4 Work Requirements

Work described in section 4.1 shall be performed on a firm fixed priced
basis. Work described in sections 4.2 and 4.3 shall be performed on a
cost plus fixed-fee basis. All work described below shall be performed
in accordance with the appropriate documents listed in section 2.3 and
any additional guidance provided by the Government. The work performed
shall comply with the performance requirements in Appendix 3.

## 

## 

## 4.1 Operations Support

The contractor shall operate and monitor the USMCC, and the backup USMCC
as necessary, on a 24-hour, 7-day per week schedule. This work shall be
performed on site in Suitland, Maryland or at the designated backup
facility. The contractor shall:

-   operate the USMCC software and hardware and notify MCCs, SPOCs and
    RCCs of outages in accordance with the USMCC Standard Operating
    Procedures (SOP)s;

-   monitor the U.S. ground segment (LUTs, USMCC, communications and the
    USMCC environment), identify anomalies, and initiate corrective
    action according to configuration management procedures and USMCC
    SOPs;

-   be the operational point of contact for RCCs and SPOCs by responding
    to queries, re-transmitting alert messages, providing registration
    information, changing the destination/routing of alert messages,
    providing satellite pass schedules, confirming communications,
    interpreting system performance, requesting incident feedback, and
    providing other operational assistance as required;

-   be the operational point of contact for MCCs by responding to
    queries, re-transmitting alert messages, providing registration
    information, changing the destination/routing of alert messages,
    requesting alert messages from other MCCs, confirming
    communications, requesting incident feedback, ensuring system and
    ephemeris data are properly transmitted, providing coordination
    support to the Cospas-Sarsat System, and providing other assistance
    as required;

-   be the operational point of contact for NOAA SAR payload operations
    by notifying MCCs, RCCs and SPOCs of payload failures, coordinating
    with the SOCC on NOAA polar and geostationary satellite issues;

-   be the operational point of contact for U.S. LUT operations by
    requesting alert and graphic data from LUTs, configuring and
    commanding the LUTs, ensuring pass schedules, ephemeris data and
    commands to LUTs are delivered, and coordinating LUT outages with
    government, LUT maintenance contractor and site personnel;

-   be the operational point of contact for telemetry and ephemeris data
    received from the ESPC;

-   be the operational point of contact for ephemeris data received from
    the NBB;

-   perform periodic backups, retrieve data from backups and maintain
    archives; and

-   maintain and prepare appropriate logs and reports.

The contractor shall register new beacons within 2 business days of
receiving the information on paper/faxed registration forms. The
contractor shall also:

-   update registration information;

-   confirm beacon registration information every two years;

-   electronically scan and file copies of beacon registration
    information;

-   prepare and mail information data sheets, letters and decals to
    beacon owners;

-   resolve beacon registration issues with owners;

-   generate periodic and special reports;

-   ensure adequate supplies are available; and

-   liaise with external organizations on registration issues.

The contractor shall also enter incident feedback data from RCCs,
generate periodic and special reports and resolve incident feedback
issues with external organizations.

## 4.2 Software Support

### 4.2.1 USMCC

The Contractor shall maintain all USMCC applications software as
referenced in the USMCC, 406 RGDB, and IHDB Functional Description
Documents, USMCC Detail Design Document, and USMCC Baseline Source. The
Contractor shall provide a complete range of software maintenance
activities including corrective maintenance, adaptive maintenance and
perfective maintenance.

Corrective maintenance is required to correct unexpected software
problems, meet published requirements, and/or fix corrupted files or
databases. The Contractor shall perform corrective maintenance on a
24-hour, 7 day-a-week schedule. The Contractor shall provide appropriate
personnel to analyze problems detected in applications software and take
appropriate action to minimize or eliminate the problems including the
development of software to correct or work around the problems.

Adaptive maintenance is required to support changes in the processing
environment, which include the addition of, or conversion to, new
hardware, operating environment, data structures or new algorithms.

Corrective or adaptive maintenance for critical software sub-systems or
elements shall be initiated within one (1) hour of notification by the
Government or appropriate personnel and performed on a 24-hour, 7
day-a-week basis.

Perfective maintenance is required to better meet operational objectives
and to support planned changes to improve efficiency, performance or
maintainability of operational software. As part of perfective
maintenance, the Contractor shall develop and analyze requirements and
provide, design, integration and testing support to upgrade/replace
existing USMCC software. Perfective maintenance and non-critical changes
shall be implemented during regular business hours.

As an integral part of all system and software maintenance the
Contractor shall follow the established configuration management plans
and procedures to ensure that any and all changes are appropriate,
approved and well documented.

The Government shall have unlimited data rights to all software
developed or modified for the USMCC. The Government reserves the right
to witness all contractor efforts to accomplish the SOW requirements and
maintains the right to approve or reject resulting processes and
products before subsequent related processes and products are
implemented. The contractor shall maintain an interface with Government
project personnel, users, software quality and configuration management
personnel throughout the process.

### 4.2.2 Direct Readout, Argos and GOES DCS

The Contractor shall provide a complete range of corrective, adaptive
and perfective maintenance support for the Direct Readout, Argos and
GOES DCS functions. All support shall be provided during regular
business hours.

## 4.3 Technical Support

### 4.3.1 SARSAT/USMCC

The Contractor shall be responsible for a wide range of technical and
operational support to sustain and enhance the national SARAT and
international Cospas-Sarsat program. Key activities are described below.
All technical work in support of SARSAT and Cospas-Sarsat missions shall
be coordinated with the Contracting Officer's Representative (COR).

[LUT Support]{.underline}

The LUTs are maintained by another contractor; however, the USMCC
Operations, Software and Technical Support Contractor shall support
investigation, anomaly resolution, testing and implementation of new LUT
software. The Contractor shall also provide technical assistance in
enhancing the LUT function and developing requirements, specifications
and supporting integration for new medium-altitude Earth orbiting search
and rescue (MEOSAR) local user terminals (MEOLUT).

[PC and Local Area Network (LAN)]{.underline}

The desktop PCs and LAN for the government and Contractor staff will be
maintained by the Common IT Services (CITS) group. However, the
Contractor will be required to maintain all hardware and systems
software associated with the USMCC system. The contractor shall perform
requirement analysis, design, hardware and COTS procurement,
implementation, configuration, and maintenance of PC workstations and
Local Area Networks and associated hardware for the USMCC system. The
current hardware configuration is described in section 3.1. The
contractor shall also be responsible for maintaining all hardware
including routers and firewalls and COTS in support of the SARSAT
mission.

The contractor shall provide software design to develop and apply PC
technology in networked applications for the USMCC system. This work
shall include software applications (commercial and government
generated), procurement, networking, rapid prototyping, and integration
of PC hardware, software, and peripherals.

The contractor shall maintain PC workstations and LANs according to
configuration management procedures. Change tasks include the technical
preparation, impact evaluation/analysis, and planning necessary to
implement changes. Hardware and COTS changes can be a result of one of
the following types of maintenance:

-   Corrective maintenance - maintenance in response to a system
    problem.

-   Adaptive maintenance - maintenance to accommodate a change in
    requirements of data environment.

-   Perfective maintenance - maintenance to better meet operational
    requirements or to improve processes.

Corrective or adaptive maintenance for critical sub-systems or elements
shall be initiated within one (1) hour of notification by the Government
or appropriate personnel and performed on a 24-hour, 7 day-a-week basis.
Perfective maintenance and non-critical changes shall be implemented
during regular business hours.

The contractor shall support transition of current capabilities to
web-based services, and use of the Internet to support the SARSAT and
USMCC missions. The contractor shall support the Government by
maintaining and updating web pages, suggesting web enhancements and
performing routine updates.

[Data Communications]{.underline}

The Contractor shall provide data communications technical support that
includes studying, identifying, planning, implementing and maintaining
required data communications for the transfer of distress alert and
system data. Communication paths include the use of AFTN, frame relay,
facsimile, and VPN. The Contractor shall be responsible for establishing
new communication links for the USMCC, troubleshooting data
communication problems and maintaining data communication configuration.

The Contractor shall coordinate with the USAF, USCG and other
organizations to develop the capability to transmit alert messages
directly to their automated mapping and display systems and search
tools. The Contractor shall also be responsible for the maintenance of
NOAA provided Communications and Data Terminal Equipment at the RCCs and
LUTs.

[IT Security]{.underline}

The contractor, in accordance with the SARSAT IT Security Plan and
Department guidance, shall be responsible for developing, implementing,
and maintaining and testing technical IT Security controls within the
mission critical SARSAT system and web applications.\
\
These responsibilities include the installation, configuration, and
maintenance of firewalls, intrusion detection systems, and routers; the
application of security patches, the maintenance of virus protection
tools and documenting and reporting these activities through scans. In
addition, the contractor shall support the Government in IT Security
related activities including but not limited to risk and vulnerability
assessments and testing, certification and accreditation, and Plan of
Action and Milestones (POAM) reporting.

[Analysis]{.underline}

The Contractor shall perform analysis as a result of reported or
observed anomalies or perform analysis on topics as requested by the
Government. Analysis can include collecting or extracting data,
providing software for analysis and documenting results.

Analysis of anomalies is one of the most important activities for the
Contractor as anomalous data has a direct impact on the users of the
data. This impact can range from loss of confidence in data provided to
the users to unnecessary allocation of resources by the users. It is
imperative for the Contractor, in a timely manner, to be able to:

-   identify problems through monitoring or analysis,

-   identify the causes of the problem,

-   collect and analyze data, and

-   recommend solutions and their implementation.

This activity shall include, but is not limited to, analysis of:

-   USMCC Functions

-   Data Distribution Procedures

-   False Alerts

-   Interferers

-   Orbit Vector Processing

-   Potential Satellite Problems

-   Large Location Errors

-   Beacon Problems

-   Communications

-   LUT Performance.

[Meeting Support]{.underline}

The contractor shall support the SARAST and Cospas-Sarsat programs at
national and international meetings. Such meetings include: Council and
JC/Task Group (TG) Meetings, Regional Data Distribution Region Meetings,
Interface Meetings with US RCCs, Beacon Manufacturers Meeting,
Bi-lateral Meetings, National Search and Rescue Committee (NSARC)
General Meetings, Civil Air Patrol Meetings, Radio Technical Commission
for Aeronautic services (RTCA) Meetings, Radio Technical Commission for
Maritime services (RTCM) Meetings, and United Nations (UN) Conferences.
The contractor shall review and analyze meeting documents, write
position papers and presentations and attend meetings as members of the
U.S. delegation as appropriate.

[Monitoring]{.underline}

The purpose of monitoring is two-fold: 1) to detect anomalies in the
performance of the national and international SARSAT and Cospas-Sarsat
space and ground segments; and 2) to ensure the integrity and validity
of the data provided to MCCs, SPOCs and RCCs. The Contractor may have to
perform monitoring and trend analysis over and above what is performed
as part of the 24-hour operation. The Contractor shall also support the
monitoring required by the Cospas-Sarsat System as outlined in C/S A.003
\"Cospas-Sarsat System Monitoring & Reporting\". The areas of monitoring
include, but are not limited to:

-   U.S. and foreign LUTs

-   Communications Links

-   Orbitography Beacons

-   Operational Beacons

-   Satellites

-   USMCC Software and Hardware

-   Large Location Errors

In addition, the Contractor shall perform routine monitoring and
reporting of harmful interference in distress frequency bands. The
contractor shall coordinate with internal and external regulatory
agencies to eliminate interference and coordinate with appropriate
agencies and organizations on frequency management issues.

[Communication and Outreach]{.underline}

The Contractor shall support the SARSAT and Cospas-Sarsat program by
interfacing with the public as required. The interface may include
public meetings, conferences, and trade or professional events.
Activities also include developing literature, providing briefings and
tours of the USMCC and other educational activities as necessary. The
Contractor will also be responsible for maintain an accurate count of
the number of people rescued as a result of the SARSAT system and
providing periodic reports on rescues.

[Testing]{.underline}

The contractor shall support testing other than that involved with
software life-cycle activities. This includes support for commissioning
of new equipment in the Cospas-Sarsat Ground Segment, support for
on-orbit testing of SAR payloads, the annual Cospas-Sarsat system test,
support for other federal, state, or local agencies, private agencies
and support for U.S. LUTs, LUTServer, and MEOLUT development. The
Contractor shall also act as the point of contact for test transmissions
of beacons, and shall coordinate NOAA approved testing in order to
minimize harmful impacts to the operational system.

[Documentation]{.underline}

The contractor shall prepare, revise, and/or review software, standard
operating procedures, and operations documentation in accordance with
applicable federal and/or agency standards during the appropriate phase
of the life cycle including technical reports to document algorithm
analysis, feasibility studies, trade-off, and impact analysis. All
documentation shall be updated to remain current with the USMCC system.

The contractor shall also perform engineering analysis of implemented
software products and develop new, or modify existing documentation, to
correctly reflect the implemented code. The documentation shall provide
the necessary information to support life cycle maintenance of the
software product(s) by the Government.

The Contractor shall update as required and maintain all documentation
related to the USMCC including, but not limited to, the following:

-   USMCC Functional Description Document

-   USMCC Operations Guide

-   SARSAT System Administrators Guide

-   USMCC Detail Design Document

-   USMCC Functional Requirements Document

-   406 Registration Data Base Functional Requirements Document

-   Incident History Data Base Functional Requirements Document

-   USMCC Data Structures Document

-   USMCC Baseline Source

-   USMCC National Rescue Coordination Center and Search and Rescue
    Point of Contact Alert and Support Messages

-   USMCC Standard Operating Procedures

-   SARSAT IT Architecture

-   SARSAT Security Plan

-   SARSAT Configuration Management Plan

[Configuration Management]{.underline}

The contractor shall support the existing configuration management plan
and shall support the government as required to provide storage of, and
controlled access to software, documentation and associated tools and
procedures. The contractor shall maintain configuration documentation
(change proposals, problem reports, and associated logs) and support
NOAA's configuration manager in scheduling meetings, ensuring
documentation is complete and producing reports.

### 4.3.2 Direct Readout, Argos and GOES DCS

The Contractor shall provide technical support in support of the Direct
Readout, Argos and DCS missions. Technical support includes the
following:

-   Provide support to install a back-up system for the Argos electronic
    SUA system at a designated location.

-   Provide support to install a back-up system for the DRO electronic
    registration and meeting system at a designated location.

-   Provide technical oversight assistance of development of DCS
    Automated Processing System (DAPS) replacement system.

-   Assist management staff with technical issues related to accessing
    DAPS and all subsequent systems, and management tools.

-   Assist users with technical issues related to accessing DAPS and all
    subsequent systems.

-   Develop and manage backups of all management systems and databases.

-   Run Daily DAPS Monitoring Tools and Reports.

-   Run Daily Reports to assist with transitions to new technologies
    (i.e. channel reports to determine when new channels are candidates
    to be transitioned to high data rate usage).

-   Corrective, adaptive and perfective maintenance shall be performed
    during regular business hours.

# 5 Processing Environment

Maintenance and operation of the USMCC system shall be performed within
the USMCC computer facilities which are located in the NOAA Satellite
Operations Facility (NSOF) in Suitland, Maryland. In addition, the
contractor shall maintain a backup USMCC located at NOAA Command and
Data Acquisition (CDA) at Wallops Island, Virginia.

The Government shall provide all USMCC hardware, operating system
software, COTS, and the necessary data telecommunications equipment. The
Government shall also provide all computer supplies (tapes, disks,
paper, etc.).

# 6 Reporting

The Contractor shall produce many different types of reports to document
system status and performance and to inform users and USMCC
stakeholders. These reports include:

-   [Daily Briefings]{.underline} - The Contractor shall be required to
    present a brief summary of operational activities at 09:05 AM of
    each business day for the period since the last briefing. Major
    problems, trends, outages (USMCC, LUTs, satellites or
    communications), number of scheduled LUT passes not received,
    feedback regarding 406 beacon activations, rescues attributed to the
    Cospas-Sarsat System, and status of beacon registrations shall be
    documented and presented as "SARSAT Daily Report".

-   [Bi-weekly Status Meeting and Minutes]{.underline} - At this
    meeting, the Contractor shall provide the NOAA COR with an update on
    the progress of activities and tasks. The USMCC Contractor shall
    document and distribute the minutes of the meetings at least 2
    working days prior to the subsequent meeting.

-   [Monthly Reports]{.underline} - These reports shall summarize the
    progress of activities during the previous month. The key elements
    for each report consist of the following:

    -   Progress to date on each tasks and activities

    -   Planned activities for the next period

    -   Significant changes

    -   Problem areas, recommended solution, and ways to prevent
        reoccurrence

    -   Cost issues that affect earned value or operational analysis
        reporting and how they are being addressed.

> Monthly Reports shall be provided to the Contracting Officer and COR
> on or before the 10^th^ day of each month.

-   [Monthly Configuration Management Reports]{.underline} -- These
    reports detail the status of System Change Proposals and System
    Problem Reports.

-   [Cospas-Sarsat Annual Report]{.underline} - This report shall
    include information from the USMCC Data Bases, particularly the IHDB
    to support the production of the Annual Report required by
    Cospas-Sarsat.

-   [Miscellaneous Reports]{.underline} - The contractor shall produce
    several additional regular reports that provide information to the
    USMCC data users and other national agencies. These reports include
    a Quarterly Report to the US RCCs detailing the beacon activities
    reported during the quarter; a quarterly report for beacon
    manufacturers designed to keep this group informed as to the overall
    status of 406 MHz beacon performance in the US as well as the
    performance of the beacons that they manufacture; and a monthly
    report for the FCC detailing detections of signals that may
    interfere with 406 MHz beacon detection. The Contractor shall also
    provide other reports, studies and minutes as required by the
    Government.

# 

# 7 Travel

Some of the Contractor staff will occasionally be required to travel
nationally or internationally. All travel must be authorized, prior to
travel, by the Government. A trip report and other appropriate
documentation shall be furnished to the COR within one week of
completion of travel.

# 8 Transition

The initial two months of the contract shall be a transition period
during which the Contractor shall become familiar with the USMCC,
associated sub-systems and operation. The incumbent Contractor will
continue to operate and monitor the USMCC during the transition period
as well as provide controller training and transfer documentation to the
new contractor. The new Contractor will bear full responsibility for
operations, software and technical support after the two month
transition period.

The final two months of the contract shall be a transition period during
which the incumbent Contractor will continue to bear full responsibility
of the operations, software and technical support, but will also be
responsible for training and guiding the follow-on Contractor in
learning its duties.

# 9 Backup USMCC Operations and Maintenance 

The contractor may be required to operate the backup USMCC at Wallops
Island, Virginia. The Contractor shall be required to maintain the
configuration, hardware and software, and system software and COTS. The
backup USMCC would only be operated in the event that the USMCC in
Suitland was inoperable and under the Continuity of Operations Plan.
Figure 8 and Table 3 describe the current backup USMCC located at the
incumbent\'s office facility in Lanham, MD.

[\<insert Figure 8\>]{.mark}

**Table 2: Backup** USMCC Hardware List

  -----------------------------------------------------------------------
  **Machine Name**                   **Hardware Type**
  ---------------------------------- ------------------------------------
  **Backup MCC**                     

  OPSREMOTE                          DELL DIMENSION XPS

  MCCOPS3                            DELL DIMENSION XPS

  MCCOPS3-2                          DELL DIMENSION XPS

  MccFtp3                            DELL POWEREDGE 2650

  MCCPRIMARY3                        DELL POWEREDGE 2450

  MCCCOMM3                           DELL POWEREDGE 2450

  MCCDBS                             DELL POWEREDGE 2450

  MCCPROC3                           DELL POWEREDGE 2850

  MCCPRIM3                           DELL POWEREDGE 2650

  MCCSEC3                            DELL POWEREDGE 2650

  INTERNET PC                        DELL DIMENSION 4100

  ROUTER USMCC-C                     CISCO 2621

  VPN CONCENTRATOR                   CISCO VPN 3020

  FIREWALL                           CISCO PIX 515E

  FAILOVER FIREWALL                  CISCO PIX 515E

  2 LAN SWITCHES                     HP PROCURVE2824

  KVM SWITCH                         DELL

  KMM USER STATION                   DELL

  KMM                                DELL

  HUB                                HP PROCURVE
  -----------------------------------------------------------------------

# Appendix A -- List of Acronyms

AFB Air Force Base

AFTN Aeronautical Fixed Telecommunications Network

CDA Command and Data Acquisition

CITS Common IT Services

CMCC Canadian Mission Control Center

COSPAS "Cosmicheskaya Systyema Poiska Aariynyich Sudov" which translates
loosely into "Space System for the Search of Vessels in Distress."

COTS Commercial off the Shelf

CNES Centre Nationale d\'Etudes Spatiales which translates loosely into
"National Center for Space Studies"

DCS Data Collection System

ELT Emergency Locator Transmitter

EPIRB Emergency Position-Indicating Radio Beacon

ESPC Environmental Satellite Processing Center

EUMETSAT European Organization for the Exploitation of Meteorological
Satellites

FCC Federal Communications Commission

FMCC French Mission Control Center

GEO Geostationary-Earth Orbit

GEOLUT GEOSAR Local User Terminal

GEOSAR Geostationary-Earth Orbiting Search and Rescue

GOES Geostationary Operational Environmental Satellite

GPS Global Positioning System

JC Joint Committee

LEO Low-Earth Orbit

LEOLUT LEOSAR Local User Terminal

LEOSAR Low-Earth Orbiting Search and Rescue

LUT Local User Terminal

MCC Mission Control Center

MEOLUT MEOSAR Local User Terminal

MEOSAR Medium-Earth Orbiting Search and Rescue

METOP Meteorological Operational (satellite)

MOU Memorandum of Understanding

NBB Naval Bulletin Board

NESDIS National Environmental Satellite, Data, and Information Service

NIST National Institute of Standards and Technology

NOAA National Oceanic and Atmospheric Administration

NSARC National Search and Rescue Committee

NSOF NOAA Satellite Operations Facility

OPSCOM Operations Committee

OSDPD Office of Satellite Data Processing and Distribution

OWG Operations Working Group

PLB Personal Locator Beacon

POAM Plan of Actions and Milestones

POES Polar-orbiting Operational Environmental Satellite

PSDN Packet-Switched Data Network

PSTN Public Switched Telecommunication Network

RCC Rescue Coordination Center

RTCA Radio Technical Commission for Aeronautics

RTCM Radio Technical Commission for Maritime services

SAR Search and Rescue

SARSAT Search and Rescue Satellite Aided Tracking

SOCC Satellite Operations Control Center

SPOC SAR Point of Contact

SQL Structured Query Language

SSAS Ship Security Alerting System

SUA System Use Agreement

TG Task Group

TWG Technical Working Group

UN United Nations

USAF U.S. Air Force

USCG U.S. Coast Guard

USMCC United States Mission Control Center

# Appendix B -- USMCC Requirements Analysis

**I Operations**

**A 24/7 Operation of the United States Mission Control Center (USMCC)**

The 24/7 operation of the USMCC assumes that the following functions are
performed around the clock 365 days a year. These functions are expected
to remain relatively unchanged through 2012.

1.  Tend the USMCC system at Suitland, Maryland or at the designated
    backup facility

2.  Operate the USMCC per Volume 1 of USMCC Standard Operating
    Procedures (SOPs) and in accordance with Cospas/Sarsat (C/S) A.005
    "Cospas-Sarsat Mission Control Centre (MCC) Performance
    Specification and Design Guidelines"

3.  Notify MCCs, Search and Rescue Points of Contact (SPOCs), and Rescue
    Coordination Centers (RCCs) of outages

4.  Monitor the C/S Ground Segment in the United States in accordance
    with Volume 1 of USMCC SOPs and C/S A.003 "Cospas-Sarsat System
    Monitoring and Reporting"

a\. USMCC

-   initiate corrective action for critical problems per applicable SOP

-   switch and configure backup capabilities as necessary and
    appropriate

-   respond to system alarms

-   monitor operating environment and respond to environmental alarms

-   such as HVAC and power systems.

b\. Local User Terminals (LUTs)

-   monitor inputs from the LUTs to ensure that all aspects are
    functioning correctly.

-   initiate corrective action for critical problems

-   coordinate with LUT contractor to resolve problems

-   monitor LUT communication links

-   record LUT and Communication outages in the Lut Monitoring Data Base
    (LMDB)

c\. Communications

-   respond to alarms generated on the USMCC system

-   initiate corrective actions to critical problems according to SOP

-   switch to backup comm. links as required

5\. Serve as the NOAA Point of Contact for:

a\. Rescue Coordination Centers (RCCs)

-   respond to queries from RCCs

-   provide registration data

-   re-route and retransmit alert messages as needed

-   provide satellite pass schedules for active beacons

-   interpret system performance

-   request feedback data for the Incident History Data Base (IHDB) as
    appropriate

-   other assistance as required

b Mission Control Centers (MCCs)

-   respond to queries from other MCCs

-   retransmit data upon request or per procedure

-   provide registration data

-   re-route data as needed or per procedure or request

-   request alert data from other MCCs

-   request feedback on operational beacons

-   ensure system data (e.g. ephemeris) is properly transmitted.

-   coordinate international system events (international tests,
    backups, downtime etc)

c\. SPOCs

-   respond to queries

-   retransmit data upon request or per procedure

-   provide registration data

-   re-route data as needed or per procedure or request

> d\. Satellite SAR Payload Activities and the Satellite Operations
> Control Center (SOCC)

-   notify MCCs, SPOCs, and RCCs of satellite instrument failures or
    degradations, satellite movement, satellite commissioning and
    decommissioning, and other satellite related activities

-   act as POC for command requests from the French Centre National
    d\'Etudes Spatiales (CNES) and Canadian Department of National
    Defense (DND) respectively for the Search and Rescue Repeater (SARR)
    and Search and Rescue Processor (SARP) instruments and interfaces
    with the SOCC to request and verify the command execution

-   act as POC for GOES SARR instrument command requests and interfaces
    with the SOCC to request and verify the command execution

e\. LUT Operations

-   request data from LUTs

-   command, configure, and schedule LUTs

-   monitor LUT performance

-   coordinate LUT outages as appropriate

> f\. Environmental Satellite Processing Center (ESPC)

-   monitor the retrieval of SARR and SARP telemetry

-   monitor the retrieval of satellite ephemeris

g\. Naval Bulletin Board

-   monitor and retrieve Two Line Elements (TLEs)

h\. NOAA Management

-   report the status of the SARSAT ground system in the United States

-   notify of critical outages in the SARSAT ground system in the United

-   States

**B 406 MHz Beacon Registration Database**

> 1\. Manually register new beacons using paper forms mailed or faxed to
> NOAA. Table 1 shows the total number of beacons registered per year
> from 1990 to 2004. Table 2 shows the percentage of beacons registered
> online via the web interface for the period January 2004 to September
> 2005

Table 1: New Beacon Registrations

  ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
  **1990**   **1991**   **1992**   **1993**   **1994**   **1995**   **1996**   **1997**   **1998**   **1999**   **2000**   **2001**   **2002**   **2003**   **2004**

  2,785      5,843      3,991      3,846      4,671      5,252      6,742      8,412      7,973      9,075      9,790      9,236      11,920     15,377     18,343
  ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------

**Table 2: Use of Web Interface by Beacon Owners**

+--------+---------+----------+-----------+-------------+------------+
| **M    | *       | **Paper  | **Total   | **Percent   | **Percent  |
| onth** | *Online | (Mai     | Regist    | Online**    | Manual     |
|        | (Web)** | l/Fax)** | rations** |             | Entry**    |
|        |         |          |           |             |            |
|        |         |          | **and     |             |            |
|        |         |          | Updates** |             |            |
+--------+---------+----------+-----------+-------------+------------+
| Jan-04 | 960     | 3,235    | 4,195     | 23%         | 77%        |
+--------+---------+----------+-----------+-------------+------------+
| Feb-04 | 985     | 2,821    | 3,806     | 26%         | 74%        |
+--------+---------+----------+-----------+-------------+------------+
| Mar-04 | 1,544   | 5,242    | 6,786     | 23%         | 77%        |
+--------+---------+----------+-----------+-------------+------------+
| Apr-04 | 1,547   | 4,608    | 6,155     | 25%         | 75%        |
+--------+---------+----------+-----------+-------------+------------+
| May-04 | 1,628   | 4,358    | 5,986     | 27%         | 73%        |
+--------+---------+----------+-----------+-------------+------------+
| Jun-04 | 1,708   | 4,267    | 5,975     | 29%         | 71%        |
+--------+---------+----------+-----------+-------------+------------+
| Jul-04 | 1,489   | 3,303    | 4,792     | 31%         | 69%        |
+--------+---------+----------+-----------+-------------+------------+
| Aug-04 | 1,328   | 2,572    | 3,900     | 34%         | 66%        |
+--------+---------+----------+-----------+-------------+------------+
| Sep-04 | 1,161   | 3,670    | 4,831     | 24%         | 76%        |
+--------+---------+----------+-----------+-------------+------------+
| Oct-04 | 1,268   | 2,709    | 3,977     | 32%         | 68%        |
+--------+---------+----------+-----------+-------------+------------+
| Nov-04 | 1,232   | 2,751    | 3,983     | 31%         | 69%        |
+--------+---------+----------+-----------+-------------+------------+
| Dec-04 | 1,270   | 2,798    | 4,068     | 31%         | 69%        |
+--------+---------+----------+-----------+-------------+------------+
| Jan-05 | 1,848   | 3,237    | 5,085     | 36%         | 64%        |
+--------+---------+----------+-----------+-------------+------------+
| Feb-05 | 1,665   | 3,120    | 4,785     | 35%         | 65%        |
+--------+---------+----------+-----------+-------------+------------+
| Mar-05 | 2,386   | 4,423    | 6,809     | 35%         | 65%        |
+--------+---------+----------+-----------+-------------+------------+
| Apr-05 | 2,716   | 3,986    | 6,702     | 41%         | 59%        |
+--------+---------+----------+-----------+-------------+------------+
| May-05 | 3,162   | 3,528    | 6,690     | 47%         | 53%        |
+--------+---------+----------+-----------+-------------+------------+
| Jun-05 | 2,888   | 3,774    | 6,662     | 43%         | 57%        |
+--------+---------+----------+-----------+-------------+------------+
| Jul-05 | 2,536   | 2,444    | 4,980     | 51%         | 49%        |
+--------+---------+----------+-----------+-------------+------------+
| Aug-05 | 2,612   | 3,222    | 5,834     | 45%         | 55%        |
+--------+---------+----------+-----------+-------------+------------+
| Sep-05 | 1,863   | 2,656    | 4,519     | 41%         | 59%        |
+--------+---------+----------+-----------+-------------+------------+

> 2\. Provide beacon registration "help desk" services via telephone
> according to SARSAT Customer Service Delivery Standards. Table 3
> provides the current level of effort for reference.

Table 3: Beacon Registration Database Calls for Period July 16, 2004 to
November 24, 2004

  ----------------------------- -----------------------------------------
  **Total Calls To Date**       **The average number of calls per
                                calendar workday**

  1,896                         21

  **Total Minutes**             **Average minutes spent on calls per
                                calendar workday**

  5,604                         61
  ----------------------------- -----------------------------------------

> 3\. Maintain daily counts including new registrations by paper and
> online, total beacon count, and number of confirmations
>
> 4\. File hardcopies of beacon registration forms and correspondence.
> Note: Future correspondence may be filed electronically.
>
> 5\. Prepare and mail information data sheets, letters, and decals to
> beacon owners

**C Incident History Data Base**

> 1\. Manually enter feedback faxed from RCCs into database. Table 4
> provides the number of feedback reports to be entered into the
> database. Note: Some parts of this may be automated in the future and
> the 121/243 MHz. system is being terminated in 2009
>
> **Table 4: Incident Feedback Entries 4/1/04 to 4/1/05**

**D Database and File Maintenance**

> 1\. Perform regular backups
>
> 2\. Maintain archives
>
> 3\. Retrieve archived data as required
>
> 4\. Log all actions

**E Reporting**

> 1\. Prepare morning report ( See Attached Examples)
>
> 2\. Maintain configuration logs

**II Maintenance**

**A USMCC Software Maintenance**

> 1\. Maintain the subsystems in Table 5 which are coded in C++, Visual
> BASIC, SQL, MapInfo, Visual C++, JAVA:
>
> **Table 5: List of USMCC Subsystems**

+-------------------+-------------+---------------------+-------------+
| **Sub-system**    | **Lines of  | **Sub-System**      | **Lines of  |
|                   | Code**      |                     | Code**      |
+===================+=============+=====================+=============+
| Alert             | 40,339      | Database/Data       | 1,063       |
|                   |             | Maintenance         |             |
| Processing        |             |                     |             |
|                   |             | (DBMN)              |             |
| (ALRT)            |             |                     |             |
+-------------------+-------------+---------------------+-------------+
| Communications    | 25,836      | Incident History    | 54,507      |
| Processing        |             | Database            |             |
|                   |             |                     |             |
| (COMM)            |             | (IHDB)              |             |
+-------------------+-------------+---------------------+-------------+
| System Data       | 16,816      | Registration        | 77,487      |
| Processing        |             | Database            |             |
|                   |             |                     |             |
| (SDAT)            |             | (RGDB)              |             |
+-------------------+-------------+---------------------+-------------+
| Real Time System  | 5,101       | Self‑test And       | 12,071      |
| Monitoring        |             | Monitoring          |             |
|                   |             |                     |             |
| (SMON)            |             | (SAMS)              |             |
+-------------------+-------------+---------------------+-------------+
| Operator          | 54,144      | LUT Monitoring      | 20,953      |
| Interface         |             |                     |             |
|                   |             | Database            |             |
| (OPER)            |             |                     |             |
|                   |             | (LMDB)              |             |
+-------------------+-------------+---------------------+-------------+
| Interference      | 70,203      | SAR Mapping/Geosort | 41,848      |
| Monitoring (INTF) |             |                     |             |
|                   |             | (SMAP)              |             |
+-------------------+-------------+---------------------+-------------+
| Miscellaneous     | 1,631       |                     |             |
+-------------------+-------------+---------------------+-------------+

> 2\. Perform corrective, adaptive and perfective maintenance. Critical
> maintenance is to be initiated within one (1) hour, non-critical
> maintenance according to configuration management plan. Table 6
> provides a historical perspective on the number of changes to the
> USMCC system.
>
> **Table 6: List of System Changes**

**III Technical Support**

**A Communications**

1.  Establish and maintain communications links for SRINT Frame Relay
    network, AFTN, FTP over VPN, and dedicated fax.

2.  Perform corrective maintenance, adaptive and perfective maintenance
    according to published guidelines

**B IT Security**

> 1\. Maintain operational Systems (USMCC, LUTs, and Communication
> equipment) according to the DOC, NOAA, and SARSAT IT security policies
> and plans.
>
> 2\. All COTS shall be kept up to date with security patches and
> updates.
>
> 3\. Generate periodic and special reports including scanning,
> vulnerability, and intrusion reports.
>
> 4\. Develop, implement, test, and maintain security controls according
> to DOC, NOAA, and SARSAT guidance.
>
> 5\. Maintain network hardware to meet DOC, NOAA and SARSAT security
> guidelines.
>
> 6\. Support all aspects of certification and accreditation activities.
>
> 7\. Support Plan of Action and Milestone (POAM) generation, tracking,
> implementation and reporting.

**C Equipment**

1 at Suitland and LUT sites

a Maintain the following:

\- 63 PCs with Windows Operating System

\- 10 Lut Display Monitors

> \- 1 Map Display Monitor
>
> 14 Routers and 2 firewalls

\- 14 pico turbo switches

> \- registration data base support equipment including decal printers,
> paper folding machine, and scanner

b Perform corrective Maintenance

\- critical maintenance to be initiated within 1 hour

\- non-critical maintenance according to CMP

> c Perform adaptive Maintenance- according to CMP

d Perform perfective Maintenance- according to CMP

2 At Backup USMCC Site

a Maintain the following:

\- 9 PCs with Windows Operating System

\- 1 Router and 1 firewall

b Perform corrective Maintenance

\- critical maintenance to be initiated within 1 hour

\- non-critical maintenance according to CMP

c Perform adaptive Maintenance- according to CMP

d Perform perfective Maintenance- according to CMP

**D Analysis**

1.  Study, recommend, and design new hardware, software, or
    configuration changes to improve or optimize LUT/USMCC performance

2.  Integrate new hardware/software systems into the USMCC as required
    by NOAA or configuration management.

3.  Perform studies and prepare reports on the various aspects of the
    operation as required by NOAA, Configuration Management, or
    Performance plan.

4.  Plan, conduct, and analyze tests and tests results with LUTs, MCCs,
    SPOCs, RCCs, and others as required including the annual
    Cospas-Sarsat system and backup tests, and MCC and satellite
    commissioning tests.

5.  Support False Alert analysis

6.  Retrieve data in support of responding to FOIA requests and
    investigations

7.  Assist in integrating new technologies into the USMCC and
    Cospas-Sarsat.

8.  Assist in developing and implementing requirements for the MEOSAR
    system(LUT and USMCC).

9.  Review and write papers/studies on behalf of the government

10. Monitor SAR payload

**E Meetings**

1.  Writing and review papers and presentations for international
    meetings

2.  Attend meetings

    a.  Task Groups

    b.  Joint Committee

    c.  Cospas-Sarsat Council

    d.  Bi-lateral / Multilateral

    e.  Beacon Manufacturer's Workshop

    f.  With Users and other Stakeholders

3.  Review and write papers for meetings (number reviewed can range from
    10-100 and number written can range from 1-20 per meeting)

**F Interference Monitoring**

1.  Maintain subsystem to automatically track and report interference

2.  Coordinate with federal/international agencies to eliminate harmful
    interference

3.  Coordinate with appropriate agencies/organizations on frequency
    management issues.

**G Outreach**

1.  Attend conferences and trade/professional events

2.  Develop literature

3.  Provide briefings and tours of the USMCC

4.  Support educations and outreach

**H Reporting**

1.  Morning Reports - See attached examples

2.  Provide data for Performance Management Reporting

3.  Generate IHDB reports

4.  Response to DOC, NOAA, NESDIS and OSDPD data calls

5.  Ad Hoc

**I Testing**

1.  Support Commissioning (Spacecraft, LUT, and MCC) and associated
    analysis

2.  Support Satellite testing(on orbit support) and associated analysis

3.  Act as Point of Contact for test coordination

4.  Conduct/Participate in demonstrations and associated analysis

5.  Test changes/enhancements to ground segment and associated analysis

6.  Coordinate annual systems test and associated analysis

7.  Perform Risk Reduction related testing and associated analysis

**J Develop and Maintain Documentation**

> 1\. Maintain USMCC Technical Documentation

a.  Functional Requirements Document

b.  Standard Operating Procedures/Guide

c.  Operators Manual

d.  Data Structures Document

e.  Functional Description Document

f.  Detailed Design Document

g.  Software Baseline Document

h.  RCC Messages Document

i.  RCC Training Document

j.  Interface Control Document (IPD-DSD)

k.  Special Beacon Programs

l.  Communications Description Document

> 2\. Develop other documentation
>
> a\. Public Awareness
>
> b\. Trade publications
>
> c\. Web pages

**K Configuration Management**

1.  Coordinate Configuration Management activities

2.  Support NOAA's configuration manager

3.  Manage configuration documentation

**Sample Morning Report**

SARSAT MORNING STATUS REPORT

24 APR 2006 21/0000 UTC APR 2006 - 23/2400 UTC APR 2006

1\. AS OF 0001 UTC THIS MORNING, THE SYSTEM IS FULLY OPERATIONAL.

2\. MCC STATUS - UP.

3\. LUT STATUS.

  ---------- ---------- ---------- ---------- ---------- ---------- ----------
  LUT        AK1/2      CA1/2      FL1/2      GU1/2      HI1/2      MD1/2

  MISSED     0          0          0          0          0          0
  PASSES                                                            

             0          0          1          0          1          0
  ---------- ---------- ---------- ---------- ---------- ---------- ----------

4\. COMMUNICATIONS LINES STATUS - UP.

5\. SAR INCIDENTS.

> Beacon ID - ADCD023B78C1C01 Home Port -- Ft. Bragg, CA
>
> DISTRESS. On 20 April 2006 at 2028 UTC, the COSPAS-SARSAT system
> detected a 406 distress signal 12 miles off the coast of Ft. Bragg,
> CA. Coast Guard Pacific area received a call from the Good Samaritan
> \"20 Grand\" that they had retrieved the person and EPIRB from the
> fishing vessel \'Ball No 1\" that sank. They were in the area at that
> time and saw the vessel sinking. Not a SARSAT rescue.
>
> Beacon ID - ADCD02157500401 Home Port -- Unknown
>
> DISTRESS. On 21 April 2006 at 1731 UTC, the COSPAS-SARSAT system
> detected a 406 MHz distress signal in position 16 26.30 N, 157 00.56
> W. The owner/operator of the F/V Julie Irene manually activated his
> 406 MHz EPIRB when his vessel became disabled and adrift due to main
> engine failure. The Coast Guard District 14 RCC in Honolulu, HI
> launched a C-130 fixed wing aircraft and the USCG cutter Kiska to the
> area. The disabled vessel was located 145 NM southwest of Hawaii. The
> vessel owner arranged for the F/V Seajay to come and give him a tow
> into port. The USCG cutter Kiska arrived on scene and attempted to
> repair the engine. They repaired the starter solenoid unit, but the
> batteries were dead. The Coast Guard cutter took the vessel in tow to
> Hilo, HI where they will rendevous with the F/V Seajay which is
> carrying extra batteries for the disabled vessel. 5 SARSAT RESCUES.

6\. 406 BEACON SITES CLOSED

LOCATED: USA 14, BERMUDA 1, TRINIDAD 1, MARSHALL 1, MEXICO 1, CANADA 1

UNLOCATED: USA 19

REGISTERED USA BEACONS: 73% (24)

7\. TOTAL BEACON SITES CLOSED

REPORT PERIOD FIRST ALERTS COMPOSITES FREQUENCY

21/0000 thru 203 33 121/243 MHz

21/2359 Apr 12 2 406 MHz

22/0000 thru 186 34 121/243 MHz

22/2359 Apr 16 5 406 MHz

23/0000 thru 212 34 121/243 MHz

23/2359 Apr 10 3 406 MHz

8\. 406 MHz BEACON ACTIVATION SUMMARY

NO INFORMATION 6

ND-Bcn Mishandling-Improper Use 10

ND-Bcn Malfunction-No Specifics 1

Distress-Automatic 1

ND-Unknown-No Feedback on cause 4

ND-Bcn Malfunction-Electronics 1

ND-Mounting Failure-Strap/Bracket 1

Ceased-Undetermined if distress 8

ND-Bcn Mishandling-Improper Install 1

ND-Bcn Malfunction-Water Intrusion 1

ND-Unknown-Investigated-Inconclusive 1

Distress-Manual 1

ND-Bcn Mishandling-Improper Disposal 1

ND-Bcn Mishandling-Test/Maintenance 1

MCC DAILY STATUS REPORT

24 APR 2006 21/0000 UTC APR 2006 - 23/2400 UTC APR 2006

1\. PROBLEMS - NONE.

2\. CONTROLLER NOTES.

21/0800 UTC -- Message received from the COSPAS-SARSAT Secretariat
regarding the new COSPAS-SARSAT type approval beacon, TAC 158.

THE FOLLOWING NEW 406 MHZ ELT HAS BEEN APPROVED BY COSPAS-SARSAT.

BEACON MODEL NAME: AVMM ELT S-406

MANUFACTURER: MUSSON MARINE LTD.

FREQUENCY CHANNEL: 406.028 MHZ

CLASS: 2

APPROVED FOR USER PROTOCOLS APPLICABLE TO ELTS:

AVIATION

ELT WITH SERIAL NUMBER

ELT WITH AIRCRAFT OPERATOR AND SERIAL NUMBER

ELT WITH AIRCRAFT 24-BIT ADDRESS

TESTED LIFETIME: 24 HOURS

MORE DETAILED INFORMATION IS AVAILABLE FROM THE COSPAS-SARSAT

SECRETARIAT WEBSITE AT WWW.COSPAS-SARSAT.ORG

3\. LUTS

LUT(S) CONFIGURED DOWN (NEXT PASS PREDICTION) - NONE.

LUT(s) ON TEST SYSTEM - LSE, GSE

  --------- ------------ -------------- ----------------- -----------------
  LUT       SAT          ORBIT          AOS               LOS

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

FL2 S10 4756 22/1805 22/1820

REASON: No 406 Solutions due to Antenna hardware issues.

HI2 S9 19898 23/1016 23/1024

REASON: Missing Pass Summary, due to message formatting error.

4\. 406 DATA BASE SUMMARY

BEACON REGISTRATIONS IN DATABASE 148607

BEACON REGISTRATIONS RECEIVED 98 (50)

BEACON REGISTRATIONS ENTERED (DECALS MAILED) 98 (50)

BEACON REGISTRATIONS TO BE ENTERED 0

UPDATES FROM CONFIRMATION PROCESS (DECALS MAILED) 271 (52)

UPDATES FROM UNSOLICITED CHANGES 128 (90)

TOTAL BEACON REGISTRATIONS UPDATED 399 (142)

# Appendix C -- Performance Requirements

**Operations Support**

+---------------+---------------+-----------------+-------------------+
| **Desired     | **Required    | **Performance   | **Monitoring      |
| Outcomes**    | Service**     | Standard**      | Method**          |
+===============+===============+=================+===================+
| Operation of  | The           | a)  99.5%       | a)  Daily         |
| the USMCC in  | contractor    |     system      |     monitoring    |
| accordance    | shall operate |                 |     and Quarterly |
| with national | and monitor   |    availability |     availability  |
| and           | the USMCC on  |     for the     |     report.       |
| international | a 24-hour,    |     USMCC       |                   |
| standards     | 7-day per     |                 | ```{=html}        |
|               | week          | ```{=html}      | <!-- -->          |
|               | schedule.     | <!-- -->        | ```               |
|               | This work     | ```             | a)  Daily report  |
|               | shall be      | a)  99% of all  |     and operator  |
|               | performed on  |     problems    |     logs          |
|               | site in       |                 |                   |
|               | Suitland,     |    communicated |                   |
|               | Maryland or   |     and acted   |                   |
|               | at the        |     upon        |                   |
|               | designated    |                 |                   |
|               | backup        |   appropriately |                   |
|               | facility as   |     within an   |                   |
|               | described in  |     hour of     |                   |
|               | the USMCC     |     occurrence  |                   |
|               | Requirements  |     for : LUT   |                   |
|               | Analysis      |     problems,   |                   |
|               | document and  |                 |                   |
|               | the SOW.      |  communications |                   |
|               |               |     outages,    |                   |
|               |               |     and USMCC   |                   |
|               |               |     problems    |                   |
+---------------+---------------+-----------------+-------------------+
| Effective and | The           | a)  99.5% of    | a)Daily briefings |
| accurate      | contractor    |     all new     | and Quarterly     |
| beacon        | shall         |     beacons     | reports           |
| registration  | register new  |     registered  |                   |
| information   | beacons       |     within 2    | > b\) Quarterly   |
| to search and | within 2 days |     business    | > Reports and RCC |
| rescue        | of reception  |     days of     | > feedback        |
| services.     | of the        |     receiving   |                   |
|               | registration  |     the         |                   |
|               | form          |                 |                   |
|               |               |    information. |                   |
|               |               |                 |                   |
|               |               | ```{=html}      |                   |
|               |               | <!-- -->        |                   |
|               |               | ```             |                   |
|               |               | a)  78% of      |                   |
|               |               |                 |                   |
|               |               |    registration |                   |
|               |               |     information |                   |
|               |               |     transmitted |                   |
|               |               |     to RCCs is  |                   |
|               |               |     accurate    |                   |
+---------------+---------------+-----------------+-------------------+

**Software Support**

+---------------+---------------+-----------------+-------------------+
| **Desired     | **Required    | **Performance   | **Monitoring      |
| Outcomes**    | Service**     | Standard**      | Method**          |
+===============+===============+=================+===================+
| The provision | The           | a)  98% of all  | a)  Configuration |
| of the USMCC  | Contractor    |     perfective  |     management    |
| software      | shall         |     and         |     and Status    |
| support       | maintain all  |     adaptive    |     meeting       |
| required to   | USMCC         |     maintenance |     reports.      |
| maintain its  | applications  |     done and    |                   |
| operation and | software as   |     within      | ```{=html}        |
| compliance    | referenced in |     agreed to   | <!-- -->          |
| with          | the USMCC,    |     time frames | ```               |
| appropriate   | 406 RGDB, and |                 | a)  Daily         |
| national and  | IHDB          | ```{=html}      |     reporting and |
| international | Functional    | <!-- -->        |     Configuration |
| standards     | Description   | ```             |     management    |
|               | Documents,    | a)  99% of all  |     reports.      |
|               | USMCC Detail  |     corrective  |                   |
|               | Design        |     maintenance |                   |
|               | Document,     |     initiated   |                   |
|               | USMCC         |     within 1    |                   |
|               | Requirements  |     hour of     |                   |
|               | Analysis,     |     discovery   |                   |
|               | SOW, and      |     and         |                   |
|               | USMCC         |     resolution  |                   |
|               | Baseline      |     time given  |                   |
|               | Source        |                 |                   |
+---------------+---------------+-----------------+-------------------+

**Technical Support**

+---------------+---------------+-----------------+-------------------+
| **Desired     | **Required    | **Performance   | **Monitoring      |
| Outcomes**    | Service**     | Standard**      | Method**          |
+===============+===============+=================+===================+
| The provision | The           | a)  99% of all  | a)  Configuration |
| of the        | contractor    |     USMCC PC    |     management    |
| technical     | shall perform |     and LAN     |     and status    |
| support       | monitoring    |     corrective  |     meeting       |
| required to   | and trend     |     maintenance |     reports       |
| sustain and   | analysis,     |     initiated   |                   |
| enhance the   | maintain the  |     within 1    | ```{=html}        |
| USMCC and the | USMCC         |     hour of     | <!-- -->          |
| Cospas-Sarsat | hardware and  |                 | ```               |
| missions.     | networks,     |    notification | a)  Configuration |
|               | perform       |     to NOAA     |     management    |
|               | system        |                 |     and status    |
|               | analysis and  | ```{=html}      |     meeting       |
|               | studies,      | <!-- -->        |     reports       |
|               | write papers, | ```             |                   |
|               | provide       | a)  98% of all  | b)  Configuration |
|               | meeting       |     perfective  |     management    |
|               | support,      |     and         |     and status    |
|               | support IT    |     adaptive    |     meeting       |
|               | security,     |     maintenance |     reports       |
|               | maintain      |     done within |                   |
|               | c             |     agreed to   | c)  Security      |
|               | ommunications |     timeframes  |     reports and   |
|               | links,        |                 |     meetings      |
|               | maintain      | b)  99.5% of    |                   |
|               | documentation |     all         | d)  Feedback from |
|               | and           |     maintenance |     USAF and USCG |
|               | inventories,  |     compliant   |                   |
|               | provide       |     with the    |                   |
|               | training, and |     SARSAT IT   |                   |
|               | support       |     security    |                   |
|               | system        |     plan,       |                   |
|               | testing.      |     policy, and |                   |
|               |               |     procedures  |                   |
|               |               |                 |                   |
|               |               | c)  99.5% of    |                   |
|               |               |     all         |                   |
|               |               |     required    |                   |
|               |               |                 |                   |
|               |               |  time-sensitive |                   |
|               |               |     IT support, |                   |
|               |               |     such as     |                   |
|               |               |     data calls  |                   |
|               |               |     and         |                   |
|               |               |     security    |                   |
|               |               |     patch       |                   |
|               |               |                 |                   |
|               |               |  installations, |                   |
|               |               |     completed   |                   |
|               |               |     within      |                   |
|               |               |     agreed to   |                   |
|               |               |     time frames |                   |
|               |               |                 |                   |
|               |               | d)  Training    |                   |
|               |               |     provided to |                   |
|               |               |     RCC         |                   |
|               |               |     personnel   |                   |
|               |               |     on schedule |                   |
|               |               |     agreed with |                   |
|               |               |     NOAA        |                   |
+---------------+---------------+-----------------+-------------------+