**7:58 PM 4/16/01** - Danh Nguyen

**SWSI Req'ts Matrix**

The following table allocates the requirements specified in Sections 3
through 7

(Based on the SWSI SRD \[FINAL DRAFT\] dated March 7th 2001)

<table style="width:100%;">
<colgroup>
<col style="width: 7%" />
<col style="width: 27%" />
<col style="width: 0%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 8%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 7%" />
<col style="width: 8%" />
<col style="width: 12%" />
</colgroup>
<thead>
<tr class="header">
<th><strong>REQ’TS No.</strong></th>
<th colspan="2"><strong>REQUIREMENT TEXT</strong></th>
<th colspan="2"><strong>TEST CASES</strong></th>
<th colspan="2"><strong>Test Case Run Time</strong></th>
<th><strong>Test Start</strong></th>
<th><strong>Test End</strong></th>
<th><strong>Tester</strong></th>
<th colspan="2"><strong>PASS/FAIL</strong></th>
<th colspan="2"><strong>Build</strong></th>
<th><strong>System</strong></th>
<th><strong>Comments</strong></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><em><strong>3</strong></em></td>
<td colspan="2"><em><strong>System Requirements</strong></em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.1</em></td>
<td colspan="2"><em>Introduction</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.2</em></td>
<td colspan="2"><em>Software</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.2.1</td>
<td colspan="2">SWSI software requirements will be derived by lower
level SWSI documents from other requirements</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.2.2</td>
<td colspan="2">Number range head4Number range head5Any SWSI software to
be hosted on the SWSI client shall validly execute on any client
platform supporting the Java 2.0 Virtual Machine.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2">ALL</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>3.2.3Number range head4Number range head5</td>
<td colspan="2">Any SWSI software to be hosted on the SWSI client shall
be packaged such that it can be distributed to and/or accessed by users
via electronic media.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2">Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>3.2.4</td>
<td colspan="2">Number range head4Number range head5Custom developed
SWSI software shall be designed to facilitate future modifications.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.3</em></td>
<td colspan="2"><em>System Components</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.1</td>
<td colspan="2">Lower level SWSI documents will derive additional
requirements for these components from other requirements</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.3.2</em></td>
<td><em>SWSI Client Workstation</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.2.1</td>
<td>The SWSI Client Workstation will be provided and maintained by the
user</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.2.2</td>
<td>The SWSI client shall be capable of supporting the Java 2.0 Virtual
Machine</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.2.3</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the NCCDS, the SWSI Client Workstation shall be
capable of establishing and sustaining all connections with the SWSI
Open Server applicable to the SWSI's interface with the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.2.4</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the DAS, the SWSI Client Workstation shall be
capable of establishing and sustaining all connections with the SWSI
Open Server applicable to the SWSI's interface with the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.2.5</td>
<td>For Closed IONET users who will use SN services provided via
interaction with the NCCDS, the SWSI Client Workstation shall be capable
of establishing and sustaining all connections with the SWSI Backend
Server applicable to the SWSI's interface with the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.2.6</td>
<td>For Closed IONET users who will use SN services provided via
interaction with the DAS, the SWSI client shall be capable of
establishing and sustaining all connections with the SWSI Backend Server
applicable to the SWSI's interface with the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.3.3</em></td>
<td><em>SWSI Open Server</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.3.1</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the NCCDS, the SWSI open server shall function as a
proxy for the SWSI Backend Server. For these users, the SWSI open server
shall be capable of establishing and sustaining all connections with the
SWSI Backend Server applicable to the SWSI's interface with the
NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>Application Server</td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.3.2</td>
<td>As needed, the SWSI open server shall route requests from the SWSI
client to the NCCDS and return responses from the NCCDS to the SWSI
Client Workstation. In all cases, these exchanges will be via the NISN
secure gateway and the SWSI backend server</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.3.3</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the DAS, the SWSI open server shall function as a
proxy for the SWSI Backend Server. For these users, the SWSI open server
shall be capable of establishing and sustaining all connections with the
SWSI Backend Server applicable to the SWSI's interface with the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>Application Server</td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.3.4</td>
<td>As needed, the SWSI open server shall route requests from the SWSI
client to the DAS and return responses from the DAS to the SWSI client.
In all cases, these exchanges will be via the NISN secure gateway and
the SWSI backend server</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.3.4</em></td>
<td><em>SWSI Backend Server</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.4.1</td>
<td>For Closed IONET users who will use SN services provided via
interaction with the NCCDS, the SWSI backend server shall be capable of
establishing and sustaining all applicable connections with the
NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.4.2</td>
<td>For Closed IONET users who will use SN services provided via
interaction with the DAS, the SWSI backend server shall be capable of
establishing and sustaining all applicable connections with the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.4.3</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the NCCDS, the SWSI backend server shall be capable
of establishing and sustaining all applicable connections with the
NCCDS. In all cases, these exchanges between Internet and Open IONET
users and the SWSI backend server will be via the NISN secure gateway
and the SWSI open server</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.3.4.4</td>
<td>For Internet and Open IONET users who will use SN services provided
via interaction with the DAS, the SWSI backend server shall be capable
of establishing and sustaining all applicable connections with the DAS.
In all cases, these exchanges between Internet and Open IONET users and
the SWSI backend server will be via the NISN secure gateway and the SWSI
open server</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.3.4.5</td>
<td>In support of Internet and Open IONET users, the SWSI backend server
shall be capable of establishing Secure Socket Layer (SSL) connections
with the SWSI open server via the NISN secure gateway</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.4</em></td>
<td><em>External Interfaces</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.4.1</em></td>
<td><p><em>SWSI Client Workstation</em></p>
<p>For any combination of Internet, Open IONET and Closed IONET SWSI
client users, the SWSI servers shall be capable of supporting
simultaneous connections with multiple SWSI clients. Refer to
4.8.1</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.4.2</em></td>
<td><em>NISN Secure Gate</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.2.1</td>
<td>All communications between the SWSI open server and the SWSI backend
server shall be channeled through the NISN secure gateway using
encrypted Secure Socket Layer (SSL) connections</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.4.2.2</td>
<td>When communicating with each other, the SWSI open server and the
SWSI backend server shall not employ protocols or communications
techniques that will be blocked by the NISN secure gateway</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Application Server,</p>
<p>Isolator,</p>
<p>Open TUT Server</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.2.3</td>
<td>The SWSI shall not require the NISN secure gateway to modify its
rule set in response to SWSI configuration changes, or in response to
the addition or removal of SWSI customers</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Application Server,</p>
<p>Isolator,</p>
<p>Open TUT Server</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.4.3</em></td>
<td><em>Network Control Center Data System</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.3.1</td>
<td>For any SWSI client at any time, the SWSI shall be capable of
communicating with either the NCCDS located in the operational NCC
environment or with the NCCDS located in the ANCC. Refer to 3.7. This
implies that the SWSI will be capable of simultaneously communicating
with the operational NCCDS for some clients and with the ANCC's NCCDS
for other clients</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>3.4.3.2</td>
<td>All communications between the SWSI and the NCCDS shall comply with
451-ICD-NCCDS/MOC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.3.3</td>
<td>The SWSI shall employ hypertext transfer protocol (HTTP) to retrieve
TDRSS Unscheduled Time (TUT) information from the NCCDS. The SWSI shall
employ Transmission Control Protocol/Internet Protocol (TCP/IP) for all
other communications with the NCCDS. The SWSI will not use Nascom 4800
Bit Block (BB) protocol or File Transfer Protocol (FTP) for any of its
communications with the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Open TUT Server</td>
<td></td>
</tr>
<tr class="even">
<td>3.4.3.4a</td>
<td>The SWSI shall automatically transmit Schedule Result Request
messages on the NCCDS Schedule Status service connection.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.3.4b</td>
<td>The SWSI shall automatically transmit User Performance Data Request
messages on the NCCDS User Performance Data service connection</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>3.4.3.5</td>
<td>For all applicable message formats and message format parameters,
the SWSI shall exercise the "full support" customer options. The SWSI
will not exercise the "baseline" customer options</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="odd">
<td>3.4.3.6</td>
<td>For all applicable message formats and message format parameters,
the SWSI shall exercise the "normal user" options. The SWSI will not
exercise the "Shuttle" options</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td><em>3.4.4</em></td>
<td><p><em>Demand Access System:</em></p>
<p>All communications between the SWSI and the DAS shall comply with
451-ICD-DAS/SWSI</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>SDIF</td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.5</em></td>
<td><em>Installation Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.5.1</td>
<td>General Requirement: The following requirements apply regardless of
whether the NCC facility is located at GSFC or within the DSMC at the
WSC in New Mexico</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.5.2</td>
<td>Power Requirements: The SWSI servers shall be capable of successful
operation using the power available within the NCC facility. The SWSI
servers shall not require either a quantify or quality of electric power
that exceeds the capabilities of the NCC facility</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.5.3</td>
<td>Environmental Requirements: The SWSI servers shall be capable of
successful operation within the ambient temperature and humidity ranges
available within the NCC facility. The SWSI servers shall not require
modification of either the temperature or humidity control capabilities
of the NCC facility</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.5.4</em></td>
<td><em>Site Preparation Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.5.4.1</td>
<td>The equipment installation shall be documented by an Engineering
Change (EC)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.5.4.2</td>
<td>The EC shall list of all necessary power and signal cables</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.5.4.3</td>
<td>Cable installation shall be in accordance with the requirements of
STDN-SPEC-6, GSFC Specification Installation Requirements for STDN
Equipment</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.5.4.4</td>
<td>All cable fabrication shall be in accordance with the requirements
of STDN-SPEC-4, Section 3</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.5.5</td>
<td>Equipment Installation: Equipment installations shall be in
accordance with STDN-SPEC-6, Installation Requirements for STDN
Equipment</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.5.5.1</td>
<td>Floor panels shall be in accordance with the requirements of
STDN-SPEC-6</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.6</em></td>
<td><em>Security</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.6.1</td>
<td>Both due to the missions it directly supports and to its interface
with the NCCDS, the NASA Mission (MSN) information category requirements
as defined by the <em>NASA Procedures and Guidelines for Security of
Information Technology</em>, NPG 2810.1 are applicable to the SWSI</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Isolator,</p>
<p>Open TUT Server,</p>
<p>Sys Admin Security Tools</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.6.2</td>
<td>In the absence of waivers, the SWSI shall satisfy the Baseline
Information Technology (IT) Security Requirements applicable to the MSN
information category as specified in Appendix A of NPG 2810.1</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Isolator,</p>
<p>Open TUT Server,</p>
<p>Sys Admin Security Tools</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.6.3</td>
<td>For some requirements, waivers may be requested in accord with the
provisions of NPG 2810.1</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.6.4</td>
<td>For all aspects of communications via the IONET, the SWSI shall
comply with <em>IP Operation Network (IOnet) Security Plan</em>,
290-003. However in case of conflicts between NPG 2810.1 and 290-003,
NPG 2810.1 has precedence</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Application Server,</p>
<p>Isolator,</p>
<p>Open TUT Server</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.7</em></td>
<td><em>Test Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.7.1</td>
<td>In order to support Engineering Interface (EIF) testing, the SWSI
shall provide the capability for SWSI clients to communicate with the
ANCC's NCCDS via the SWSI servers</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.7.2</td>
<td>The SWSI shall provide customers with the capability to segregate
their test data from their operational data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Isolator</td>
<td></td>
</tr>
<tr class="even">
<td><em>3.8</em></td>
<td><em>User Interface</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.1</td>
<td>The SWSI shall provide users of the SWSI Client software with a
Graphical User Interface (GUI). The general features provided by the
SWSI GUI shall include, but not necessarily be limited to (refer to SWSI
Req’ts Doc.: 3.8.1.a through 3.8.1.h )</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td><em>3.8.2</em></td>
<td><em>SN Services</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.2a</td>
<td>The SWSI shall provide users of the SWSI client with all user
interface features necessary to support the SWSI functional requirements
applicable to NCCDS interactions</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>3.8.2b</td>
<td>The SWSI shall provide users of the SWSI client with all user
interface features necessary to support the SWSI functional requirements
applicable to DAS interactions</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.2c</td>
<td>The SWSI shall provide users of the SWSI client with user interface
features providing integrated control and information presentation
capabilities for operationally related groups of SN services regardless
of whether the individual services are provided via interaction with the
NCCDS or with the DAS (e.g., integrated presentation of the service
configurations of forward services provided via NCCDS interactions and
return services provided via DAS interactions)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.8.3</em></td>
<td><em>System Information</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.3a</td>
<td>The SWSI shall provide users of the SWSI client with access to
information pertaining to the current status of each applicable SWSI
communications connection</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.3b</td>
<td>The SWSI shall provide users of the SWSI client with notification
when the status of an applicable SWSI connection changes</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.3c</td>
<td>The SWSI shall provide users of the SWSI client with access to any
available system status information provided by the SWSI servers</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>3.8.4</em></td>
<td><em>Operator Log On</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>3.8.4.1</em></td>
<td><em>Customer Authorization/ Authentication Data</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.1.1</td>
<td><em>Maintenance of Customer Authorization Data:</em> The SWSI will
provide the capabilities related to the maintenance of customer
authorization /authentication data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.1.1a</td>
<td>The SWSI shall provide authorized SWSI administrative personnel with
the capability to enter, modify, and delete customer authorization
data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.1.1b</td>
<td>The SWSI shall provide authorized SWSI administrative personnel with
the capability to review previously entered customer authorization
data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.1.1c</td>
<td>The SWSI shall retain customer authorization data until deleted by
authorized SWSI administrative personnel</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.1.2</td>
<td><em>Data: The SWSI will retain customer data related to operator log
on</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.1.2a</td>
<td>For each user, the SWSI shall retain a user ID, a password, and a
passphrase</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.1.2b</td>
<td>For each user, the SWSI shall retain a list of SICs for the which
the user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.1.2c</td>
<td>For each combination of user and SIC, the SWSI shall retain a list
of valid Support Identifiers (SUPIDENs)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.1.2d</td>
<td>For each user, the SWSI shall retain information indicating whether
the user interacts with the NCCDS, with the DAS, or both</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.1.2e</td>
<td>For each combination of NCCDS user and SUPIDEN, the SWSI shall
retain a User ID and Password to be used in messages transmitted to the
NCCDS. These User IDs and passwords will not necessarily be the same as
the User IDs and passwords used to logon to the SWSI</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td><em>3.8.4.2</em></td>
<td><em>Log On Process</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.2.1</td>
<td>The SWSI shall provide authorized users with the capability to logon
to the SWSI</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.2.2</td>
<td>The SWSI shall validate a user's logon based on the user ID,
password, and passphrase entered by the user</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.2.3</td>
<td>Within 10 seconds of its entry, the SWSI shall respond to each logon
attempt with an indication of whether it has been accepted or
rejected</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.2.4</td>
<td>The SWSI shall employ digital certificates in this validation
process, and shall rely upon the NASA Certificate Authority to provide
digital certificates to SWSI customers</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>FUTURE</td>
<td></td>
<td>SWSI will be delivered using the trial Phaos digital certificates
since NASA does not issue a server based digital certificate as of
4/16/2001</td>
</tr>
<tr class="odd">
<td>3.8.4.2.5</td>
<td>The SWSI shall allow connections to be established between a SWSI
client and SWSI servers only after a valid user logon from the SWSI
client</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.2.6</td>
<td>The SWSI shall allow only NCCDS users to access the SWSI NCCDS
functions. This includes establishing connections with the NCCDS for the
user</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF,</p>
<p>Open TUT Server</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.2.7</td>
<td>The SWSI shall allow only DAS users to access the SWSI DAS
functions. This includes establishing connections with the DAS for the
user</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.2.8a</td>
<td>For NCCDS users, the SWSI shall provide the user with the capability
to select connection with either the operational NCCDS or with the
ANCC's NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>Client</td>
<td>This is implied from 3.8.4.2.8b. The operational data is
communicated with NCCDS while the test data with ANCC</td>
</tr>
<tr class="odd">
<td>3.8.4.2.8b</td>
<td>For NCCDS users, the SWSI shall provide the user with the capability
to select use of operational or test data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>3.8.4.2.9</td>
<td>The SWSI shall provide users with theNumber range head4Number range
head5 capability to log-off</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>3.8.4.2.10</td>
<td>The SWSI shall maintain a record of currently logged-on users and
log of login attempts at all times</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Isolator</td>
<td></td>
</tr>
<tr class="even">
<td><em><strong>4</strong></em></td>
<td><em><strong>Functional and Performance
Requirements</strong></em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.1</em></td>
<td><em>Introduction</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.2</em></td>
<td><em>NCCDS Interactions</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.2.1</em></td>
<td><em>General</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.1.1</td>
<td>The SWSI provides SN customers with the capability to interface with
the NCCDS to perform the following functions related to scheduled SN
services: Scheduling, Service Reconfiguration, Performance Data
Monitoring, Vector Storage and Transmission</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.1.2</td>
<td>In all cases, the SWSI shall ensure that each NCCDS user is
precluded from accessing any other user's messages or data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.2.2</em></td>
<td><em>Scheduling</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.1</td>
<td><p><em>Customer Data Management:</em></p>
<p>For each SIC supported by the SWSI, the SWSI shall provide authorized
SWSI administrative personnel with the capability to create and maintain
all customer data necessary to perform the scheduling function. In
particular, this will include a set of service specification codes
(SSCs) corresponding to the set of SSCs maintained for the customer in
the NCCDS database, and the list of valid SUPIDENs for the SIC. The SWSI
shall provide the user with the capability to review and reference this
data in the process of entering schedule requests</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2</td>
<td><em>Schedule Requests</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.1</td>
<td><em>General:</em> The SWSI will provide the user with the capability
to enter schedule requests and transmit them to the NCCDS.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.1a</td>
<td>The SWSI shall provide the user with the capability to enter the
following types of schedule requests: Schedule Add Request (SAR),
Schedule Delete Request (SDR), Schedule Replace Request (RR), Alternate
SAR (ASAR), Schedule Wait List Request (WLR)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 1,</p>
<p>Build 2</p></td>
<td>Client</td>
<td>SAR in Build 1</td>
</tr>
<tr class="odd">
<td>4.2.2.2.1b</td>
<td>Based on the user's logon information, the SWSI shall provide the
user with the capability to select the SUPIDEN to be used in the request
from a list of SUPIDENs for which the user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.1c</td>
<td>For each of these types of schedule requests, the SWSI shall provide
the user with the capability to create a new request by copying and
editing a previous request.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 1,</p>
<p>Build 2,</p>
<p>Release 1</p></td>
<td>Client</td>
<td><p>SAR in Build 1</p>
<p>ASAR, RR in Build 2</p></td>
</tr>
<tr class="odd">
<td>4.2.2.2.1d</td>
<td>For each of these types of schedule requests, the SWSI shall provide
the user with the capability to use all options specified for that type
of request by 451-ICD-NCCDS/MOC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.1e</td>
<td>For each of these types of schedule requests, the SWSI shall format
the request in compliance with the applicable tables of
451-ICD-NCCDS/MOC. In particular, the SWSI shall not transmit schedule
requests to the NCCDS that will result in Schedule Result Messages
(SRMs) with a combination of result and explanation codes indicating
invalid formatting</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.1f</td>
<td>The SWSI shall not transmit schedule requests to the NCCDS that will
result in a lack of response from the NCCDS due to failure to pass
authorization checks</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.1g</td>
<td>Upon completion of the user's entry of a request, the SWSI shall
format, store, and then transmit the request</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.1h</td>
<td>The SWSI shall retain all stored requests until the request expires
according to administrative personnel-specified criteria</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.2</td>
<td><p><em>Schedule Add Request</em>:</p>
<p>The SWSI will allow the user to enter and transmit SARs at any time
without regard to the relationship of the SAR and any previous schedule
request</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td>SARs get stored in the database</td>
</tr>
<tr class="odd">
<td>4.2.2.2.3a</td>
<td><p><em>Schedule Delete Request</em>:</p>
<p>The SWSI shall ensure that each SDR contains a valid reference to an
active event, or to a previously transmitted SAR, ASAR, or RR</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.3b</td>
<td><p><em>Schedule Delete Request</em>:</p>
<p>SWSI shall provide the user with displays of the current active
events and previously transmitted schedule requests</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.4a</td>
<td><p><em>Schedule Replace Request:</em></p>
<p>SWSI shall ensure that each RR contains a valid reference to an
active event, or to a previously transmitted SAR, ASAR, or RR</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Isolator</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.4b</td>
<td><p><em>Schedule Replace Request:</em></p>
<p>SWSI shall provide the user with displays of the current active
events and previously transmitted schedule requests</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.5a</td>
<td><p><em>Alternate SAR</em>:</p>
<p>SWSI shall ensure that each ASAR contains a valid reference to a
previously transmitted SAR, ASAR, or RR</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Isolator</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.5b</td>
<td><p><em>Alternate SAR:</em></p>
<p>SWSI shall provide the user with displays of previously transmitted
schedule requests</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.2.6a</td>
<td><p><em>Schedule Wait List Request:</em></p>
<p>SWSI shall ensure that each WLR contains a valid reference to a
previously transmitted SAR, ASAR, or RR and that the previously
transmitted SAR, ASAR, or RR has been declined by the NCCDS, i.e., the
NCCDS has transmitted an SRM with result code of 02</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.2.6b</td>
<td><p><em>Schedule Wait List Request:</em></p>
<p>SWSI shall provide the user with displays of previously transmitted
schedule requests that indicate whether the request has been declined by
the NCCDS</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.3</td>
<td><em>TDRSS Scheduling Windows</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.3a</td>
<td>The SWSI shall provide the user with the capability to import files
of TSWs into the SWSI. These TSW files must be in a format compatible
with the TSW message format specified by 451-ICD-NCCDS/MOC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.3b</td>
<td>The SWSI shall provide the user with the capability to select
imported TSW files for transmission to the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client, SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.3c</td>
<td>Based on the SIC within each selected file, the SWSI shall verify
that the user is authorized to send this TSW data to the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.3d</td>
<td>For each validly selected file, the SWSI shall format the selected
TSWs into one or more valid TSW messages, and transmit them to the
NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.4</td>
<td><p>TDRSS Unscheduled Time</p>
<p>The SWSI shall retrieve current TDRSS Unscheduled Time (TUT)
information from the NCCDS and store it so that it is accessible to
Internet and Open IONET SWSI users</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Open TUT Server</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.5</td>
<td><em>Schedule Results</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.5.1</td>
<td><p><em>General</em></p>
<p>In response to schedule requests, the NCCDS will respond with SRMs
and with User Schedule Messages (USMs)</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.5.2a</td>
<td>Upon receipt of an <em>Schedule Result Messages</em> (SRM), the SWSI
shall: Notify the user that the SRM has been received,</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.5.2b</td>
<td>Upon receipt of an SRM, the SWSI shall provide the user with the
capability to review the SRM</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.5.2c</td>
<td>Upon receipt of an SRM, the SWSI shall Use the result and
explanation codes from the SRM to update the status information for the
request or event referenced by the SRM</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.5.2d</td>
<td>Upon receipt of an SRM, the SWSI shall provide the user with the
capability to review the requests or events with the updated status
information</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.5.2e</td>
<td>Upon receipt of an SRM, the SWSI shall, if the result code is 15,
delete the referenced event (if any) and annotate the referenced request
to indicate that it has been deleted</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.5.3a</td>
<td>Upon receipt of an <em>User Schedule Messages</em> (USM), the SWSI
shall notify the user that the USM has been received</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.2.5.3b</td>
<td>Upon receipt of an USM, the SWSI shall use the USM to update the
SWSI's schedule</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.2.5.3c</td>
<td>Upon receipt of an USM, the SWSI shall provide the user with the
capability to review the updated schedule, including the new USM</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.2.3Number range head3Number range head4Number range
head5</em></td>
<td><em>Service Reconfiguration</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.1</td>
<td><em>General: The</em> SWSI will provide the user with the capability
to enter Ground Control Message Requests (GCMRs) and transmit them to
the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.1a</td>
<td>SWSI shall provide the user with the capability to enter the
following types of GCMRs: User Reacquisition Request, User
Reconfiguration Request, Forward Link Sweep Request, Forward Link
Effective Isotropic Radiated Power (EIRP) Reconfiguration Request,
Expanded User Frequency Uncertainty Request, Doppler Compensation
Inhibit Request.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.1b</td>
<td>Based on the user's logon information, the SWSI shall provide the
user with the capability to select the SUPIDEN to be used in the request
from a list of SUPIDENs for which the user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.1c</td>
<td>For each of these types of GCMRs, the SWSI shall provide the user
with the capability to use all options specified for that type of
request by 451-ICD-NCCDS/MOC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.1d</td>
<td>For each of these types of GCMRs, the SWSI shall format the GCMR in
compliance with the applicable tables of 451-ICD-NCCDS/MOC. In
particular, the SWSI shall not transmit GCMRs to the NCCDS that will
result in a GCM Status Message indicating that the GCMR has been
rejected by the NCCDS due to invalid formatting or due to reference to
an inapplicable service type</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.1e</td>
<td>The SWSI shall not transmit GCMRs to the NCCDS that will result in a
lack of response from the NCCDS due to failure to pass authorization
checks</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.1f</td>
<td>Upon completion of the user's entry of a request, the SWSI shall
transmit and store the request</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.2</td>
<td><p><em>Current Service Configuration Displays</em>:</p>
<p>SWSI shall provide the user with the capability to review the
configuration of each currently active service and to use this
information in the entry of GCMRs</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.2a</td>
<td>For each service type, the service configuration display will
provide detailed information at the individual service parameter level.
This level of detail is comparable to that of the USM formats specified
in 451-ICD-NCCDS/MOC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.2b</td>
<td>As of service start time, the information in the service
configuration display will reflect the initial state of the service as
specified in the applicable USM</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.2c</td>
<td>Upon a successful service reconfiguration, the information in the
service configuration display will updated to reflect the reconfigured
parameter or parameters</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.3a</td>
<td>Upon receipt of a GCM Status Message, the SWSI shall notify the user
that the GCM Status Message has been received, and show whether the
status message indicates that a GCMR was rejected by the NCCDS, rejected
by WSC, or accepted by WSC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.3b</td>
<td>Upon receipt of a GCM Status Message, the SWSI shall allow the user
to view the GCM Status Message</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.3.3c</td>
<td>Upon receipt of a GCM Status Message, the SWSI shall update the
information used in the service configuration display if the GCM Status
Message indicates that the GCMR was accepted by WSC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.3.4</td>
<td>Upon receipt of a GCM Disposition Message, the SWSI shall notify the
user that the GCM Disposition Message has been received, and show
whether the message indicates that a reconfiguration request was
acknowledged or not acknowledged by WSC</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.2.4Number range head3Number range head4Number range
head5</em></td>
<td><em>Performance Data Monitoring</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.2.4.1</em></td>
<td><p><em>General</em></p>
<p>In response to messages received from WSC, the NCCDS will transmit
the following performance data messages to the SWSI: User Performance
Data (UPD) messages, Return Channel Time Delay (RCTD) messages, Time
Transfer Messages (TTMs), and Acquisition Failure Notification (AFN)
messages.</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.2.4.2</em></td>
<td><em>User Performance Data Messages</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.4.2a</td>
<td>For each TDRS, the SWSI shall be capable for receiving one UPD
message each five seconds for each SWSI user with an active service on
that TDRS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SNIF</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.4.2b</td>
<td>Upon receipt of a UPD message, the SWSI shall verify that it applies
to a SUPIDEN for which there is a logged-on SWSI user. If it does, the
SWSI shall make the information from the UPD message available for
presentation to that user in real time</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.4.2c</td>
<td>SWSI shall provide users with the following capabilities and options
for the presentation of UPD message information: Default display
formats, dynamic updates as new messages are received, display of most
recently received message, user customized display formats, Limit
checking of user selected parameters according to user specified
criteria, Summary displays, display of UPD data in its "as received"
state without application of any of the user options.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.2.4.3Number range head5</em></td>
<td><em>Return Channel Time Delay Messages (RCTD)</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.4.3Number range head5a</td>
<td>Upon receipt of a RCTD message, the SWSI shall verify that it
applies to a SUPIDEN for which there is a logged-on SWSI user. If it
does, the SWSI shall notify the user of the receipt of the RCTD
message</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.4.3Number range head5b</td>
<td>SWSI shall store the RCTD message in a file on the Client
Workstation such that it is available for later processing by customer
applications</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.2.4.4Number range head5</em></td>
<td><em>Time Transfer Messages (TTM)</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.4.4a</td>
<td>Upon receipt of a TTM, the SWSI shall verify that it applies to a
SUPIDEN for which there is a logged-on SWSI user. If it does, the SWSI
shall notify the user of the receipt of the TTM</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.2.4.4b</td>
<td>SWSI shall store the TTM in a file on the Client Workstation such
that it is available for later processing by customer applications</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.4.5Number range head5</td>
<td>Upon receipt of an Acquisition Failure Notification Messages (AFN)
message, the SWSI shall verify that it applies to a SUPIDEN for which
there is a logged-on SWSI user. If it does, the SWSI shall notify the
user of the receipt of the AFN</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SNIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.2.5Number range head3Number range head4Number range
head5</em></td>
<td><em>Vector Storage and Transmission</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.5a</td>
<td>Based on the user's logon information, the SWSI shall provide the
user with the capability to select the SIC to be used in vectors from a
list of SICs for which the user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.5b</td>
<td>The SWSI shall provide the user with the capability to enter the
latitude, longitude, and altitude of a customer spacecraft</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.5c</td>
<td>The SWSI shall be capable of converting a user-entered set of
latitude, longitude, and altitude data for a customer spacecraft into a
type 8 (stationary) Improved Interrange Vector (IIRV) for that
spacecraft</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.5d</td>
<td>The SWSI shall provide the user with the capability to directly
enter IIRVs</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td>4.2.5e</td>
<td>The SWSI shall provide the user with the capability to import files
of IIRVs</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="even">
<td>4.2.5f</td>
<td>The SWSI shall provide the user with the capability to select one or
more IIRVs for transmission to the NCCDS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td><em><strong>4.3</strong></em></td>
<td><em><strong>DAS Interactions</strong></em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.3.1</em></td>
<td><em>General</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.1.1</td>
<td>The SWSI provides SN customers with the capability to interface with
the DAS to perform the following functions related to SN services:
Service Planning, Service Allocation, Real-Time Operations, Service
Performance Monitoring, Data Retrieval, Customer State Vector Updates,
Receipt of DAS Alerts.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td>Service Planning, Service Allocation, and Real-Time Operations in
Build 2</td>
</tr>
<tr class="even">
<td>4.3.1.2</td>
<td>The SWSI shall ensure that each SN demand access service user is
precluded from accessing any other user's messages or data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.1.3</td>
<td>For each SIC supported by the SWSI, the SWSI shall provide
authorized SWSI administrative personnel with the capability to create
and maintain all customer data necessary to interact with the DAS. In
particular, this will include a set of service specification codes
(SSCs) defining the default service configurations for the SIC. For each
SIC, the SWSI shall be capable of retaining a minimum of 10 SSCs. The
SWSI shall provide the user with the capability to review and reference
this data in the process of entering requests</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td><em>4.3.2</em></td>
<td><em>Service Planning</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.2a</td>
<td>The SWSI shall provide the user with the capability to request a
report on the resource allocations available to the user</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.2b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.3.3</em></td>
<td><em>Service Allocation</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.3a</td>
<td>SWSI shall provide the user with the capability to request the
following: Allocation of a specified resource, Deletion of a pending or
ongoing resource allocation, Modification of a pending resource
allocation, A list of all currently planned events for the user, The
details of a specified planned event.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td><p>Build 2,</p>
<p>Release 1</p></td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.3b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.3.4</em></td>
<td><em>Real-Time Operations</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.4a</td>
<td>SWSI shall provide the user with the capability to request the
following: 1) Reconfiguration of the values of a specified list of
parameters for an ongoing service, 2) Reacquisition of the return
service signal</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.4b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Build 2</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.3.5</em></td>
<td><em>Service Performance Monitoring</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.5a</td>
<td>The SWSI shall provide the user with the capability to request that
DAS user performance data be enabled or disabled</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>SDIF</td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.5b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.5c</td>
<td>If user performance data was enabled, the SWSI shall provide this
data to the user as it is received from the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.5d</td>
<td>The SWSI shall be capable of receiving one DAS user performance data
message per minute for each active service with ongoing DAS support</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.3.6</em></td>
<td><em>Data Retrieval</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.6a</td>
<td>SWSI shall provide the user with the capability to request the
following: A search for archived data within a specified time window,
Playback of specific archived data, Deletion of a previously playback
request, Modification of a previously playback request.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.6b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.3.7</em></td>
<td><em>Customer State Vector Updates</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.3.7a</td>
<td>SWSI shall provide the user with the capability to enter and
transmit a state vector</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.3.7b</td>
<td>Upon receipt of the response from the DAS, the SWSI shall notify the
user and make the response available for review</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.3.8</em></td>
<td><p><em>DAS Alerts</em></p>
<p>Upon receipt of a DAS alert, the SWSI shall alert the user implied by
the SIC specified in the DAS alert message and make the text of the DAS
alert message available for review by that user. If the DAS alert
message does not apply to a specific user (i.e., SIC = "0000"), the SWSI
shall alert all users and make the text of the DAS alert message
available for review by all users</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.4</em></td>
<td><em>Database Management</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.4.1</td>
<td><em>General Features</em>: The SWSI shall provide a database
management capability for all SWSI data. The general database management
features of the SWSI shall include, but not necessarily be limited to
(refer to SWSI Req’ts Doc.: 4.4.1a through 4.4.1l)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>4.4.2</td>
<td>SN Service Data</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.4.2.1</td>
<td>The SWSI shall provide all data storage and retrieval capabilities
necessary to support the requirements for SN services specified herein.
This includes the capability to store and retain requests sent to the
NCCDS and to the DAS</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Isolator,</p>
<p>SNIF,</p>
<p>SDIF</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.4.2.2</td>
<td>For each SIC, the SWSI shall partition data such that some of the
data for that SIC can be entered, deleted, or modified only by
authorized SWSI administrative personnel while the remainder of the data
for that SIC can be entered, deleted, or modified by SWSI client users
authorized for that SIC. In general, privileges related to entry,
deletion, or modification of relatively static data such as SSCs will be
restricted to authorized SWSI administrative personnel while privileges
related to entry, deletion, or modification of time-dependent data such
as schedule requests will be restricted to SWSI client users</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.4.2.3</td>
<td>SWSI shall be capable of automatically purging data related to SN
services based on criteria specified by authorized SWSI administrative
personnel</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="odd">
<td>4.4.2.4</td>
<td>The SWSI shall be capable of deleting data related to SN services
under the direct control of authorized SWSI client users.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td><p>Client,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em>4.4.3</em></td>
<td><em>System Data</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>4.4.3.1</td>
<td>The SWSI shall provide SWSI administrative personnel with the
capability to access the contents of server log files</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>4.4.3.2</td>
<td>The SWSI shall provide SWSI client users with the capability to
access the contents of client log files containing data for which the
user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.5</em></td>
<td><em>Logging</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.5.1</td>
<td>SWSI shall be capable of logging and delogging: incoming external
messages, outgoing external messages, alerts sent to SWSI clients,
records pertaining to the establishment and termination of
communications connections, records pertaining to SWSI system failures,
records pertaining to SWSI database failures, records pertaining to
successful SWSI logon attempts, and records pertaining to rejected SWSI
logon attempts</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator,</p>
<p>SNIF,</p>
<p>SDIF,</p>
<p>Open TUT Server</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.5.2</td>
<td>The SWSI shall provide SWSI administrative personnel with the
capability to selectively control the logging and delogging of all of
the above</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Data Admin</td>
<td></td>
</tr>
<tr class="even">
<td>4.5.3</td>
<td>The SWSI shall provide SWSI client users with the capability to
selectively control delogging of all of the above data for which the
user is authorized</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>Client</td>
<td></td>
</tr>
<tr class="odd">
<td><em>4.6</em></td>
<td><em>System Performance</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>4.6.1</td>
<td>The SWSI shall have the capacity to store data for a minimum of 100
customer spacecraft. The SWSI shall allow for one set of operational
data and for at least one set of test data for each spacecraft</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Data Admin,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.6.2</td>
<td>For any combination of Internet, Open IONET and Closed IONET SWSI
clients, the SWSI servers shall be capable of supporting simultaneous
connections with a minimum of fifty SWSI clients</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td>4.6.3a</td>
<td>The SWSI response time from the perspective of the SWSI client shall
not be more than 10 seconds greater than the NCCDS or DAS response time
from the perspective of the SWSI backend server</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="odd">
<td>4.6.3b</td>
<td>The SWSI response time from the perspective of the SWSI client shall
not be greater than 10 seconds</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td><p>Client,</p>
<p>Application Server,</p>
<p>Isolator</p></td>
<td></td>
</tr>
<tr class="even">
<td><em><strong>5</strong></em></td>
<td><em><strong>Operations and Maintenance</strong></em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>5.1</em></td>
<td><em>General</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.1.1</td>
<td>SWSI servers shall be capable of continuous unattended
operation</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.1.2</td>
<td>SWSI servers shall be designed and configured such that routine
system maintenance operations and routine system administrative
functions can be executed without rendering the capabilities of the
servers operationally unavailable to the SWSI clients</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.2</em></td>
<td><em>Reliability, Maintainability, and Availability</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>5.2.1Number range head4Number range head5</em></td>
<td><em>Reliability</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.2.1.1</td>
<td>The measure of reliability for the SWSI servers is the Mean Time
Between Failures (MTBF). The MTBF is defined as the 10-year life cycle
of a fully operational SWSI divided by the predicted number of failures.
The MTBF is determined in accordance with MIL-HDBK-217, Reliability
Prediction of Electronic Equipment</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.2.1.2</td>
<td>The Parts Count Reliability prediction method of MIL-HDBK-217 shall
be used in the initial stages of system design</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.2.1.3</td>
<td>The reliability prediction method shall shift to the Parts Stress
Analysis Prediction method, or other reliability modeling technique
approved by NASA, at the time when a firm, detailed parts list is
available</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.2.1.4</td>
<td>The MTBFs of the SWSI servers shall be determined in accordance with
MIL-HDBK-217, Reliability Prediction of Electronic Equipment</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.2.2Number range head4Number range head5</em></td>
<td><p><em>Maintainability:</em></p>
<p>The maintainability requirement for the SWSI servers is stated in
terms of Mean Time To Repair (MTTR). The MTTR is the quotient obtained
by dividing the sum of the times to repair failures by the number of
failures. Excluded from time to repair are the time to obtain parts,
components, tools, or supplies not provisioned at the SWSI facility, the
time for essential personnel not scheduled to be at the SWSI facility to
be notified of the failure and to travel to the SWSI facility, and the
time to develop and configure software corrections. Based on the
preceding definitions, the SWSI servers shall have an MTTR no greater
than 60 minutes</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>5.2.3Number range head4Number range head5</em></td>
<td><em>Availability</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.2.3.1</em></td>
<td><em>Inherent Availability</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.2.3.1.1</td>
<td>Inherent Availability (Ai) is the probability that a system or
equipment, when used under stated conditions in an ideal support
environment (i.e., using available tools, spares, and personnel) will
operate within specifications at all times. It excludes preventive
maintenance actions, logistics supply time, and administrative downtime
and is expressed as: Ai = MTBF/(MTBF + MTTR)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.2.3.1.2</td>
<td>The inherent availability of any individual SWSI server for any
period of 10,000 hours shall be 0.9998</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>5.2.3.2</em></td>
<td><em>Operational Availability</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.2.3.2.1</td>
<td>The Operational Availability (Ao) of the SWSI servers is defined in
terms of the availability of the SWSI backend servers to the SWSI Open
IONET clients excluding any times during which the SWSI backend servers
are unavailable due to failure of the Open IONET, the Closed IONET, or
the NISN secure gateway</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.2.3.2.2</td>
<td>SWSI operational availability for any period of 10,000 hours
interval shall be 0.9999. Redundant paths may be used in achieving this
Ao</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.3Number range head3Number range head4Number range
head5</em></td>
<td><p><em>System Maintenance</em></p>
<p>SWSI shall have the resources, personnel, and logistics support
required to maintain, modify, and repair hardware and maintain modify
and enhance software. Hardware maintenance is performed under a formally
established system maintenance program that includes both Preventive
Maintenance and Corrective Maintenance procedures.</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>5.3.1Number range head4Number range head5</em></td>
<td><em>General Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.1a</td>
<td>The contractor shall develop procedures using 500-TIP-2111, Content
Specification for Operation and Maintenance Manuals, as a guideline</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.1b</td>
<td>Any state-of-the-art techniques that are developed for the SWSI
shall be included in the procedures.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.3.2Number range head4Number range head5</em></td>
<td><p><em>Hardware Maintenance:</em></p>
<p>Hardware maintenance will be conducted at two levels: First level
maintenance is conducted to support the inherent availability
requirements by replacement of Line Replaceable Units (LRUs) and line
replaceable items within LRUs. Second level maintenance consists of the
repair, adjustment, and testing of LRUs removed from service during
first level maintenance actions</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.1Number range head5</td>
<td><p>Identification of Line Replaceable Units (LRU):</p>
<p>LRUs shall include rack-mounted equipment drawers and panels and
other assemblies that can be removed by unplugging power and signal
connectors without physically disturbing other LRUs</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.2.1aNumber range head5</td>
<td>First level maintenance will include scheduled preventive
maintenance.</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.1bNumber range head5</td>
<td>First level maintenance will include fault isolating to the level of
an LRU</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.2.1cNumber range head5</td>
<td>Fault isolation to the level of a line replaceable item within an
LRU (if any) shall be performed if the time required is consistent with
the operational maintainability requirement</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.1dNumber range head5</td>
<td>First level maintenance shall include replacement of a failed LRU or
line replaceable element within an LRU</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.2.1e</td>
<td>First level maintenance shall include testing to ensure that the
system/subsystem has been restored to operational condition</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.1f</td>
<td>First level maintenance will include alignment and tuning</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.2.3aNumber range head5</td>
<td><p><em>Second Level Maintenance:</em></p>
<p>Second level maintenance actions will include localization of a
failure to the piece-part or equipment component level, as
appropriate</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.3bNumber range head5</td>
<td>Second level maintenance actions will include disassembly and
removal of the failed piece-part or equipment component</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.2.3c</td>
<td>Second level maintenance actions will include replacement of failed
elements and reassembly</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.2.3d</td>
<td>Second level maintenance actions will include bench testing to
ensure performance to the specified level</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>5.3.3Number range head4Number range head5</em></td>
<td><em>Software Maintenance</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.3.1</td>
<td>SWSI system shall provide capability for personnel to be cognizant
of anomalous software behavior</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>5.3.3.2</td>
<td>SWSI system shall provide capability for personnel to initiate
software trouble reports</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>5.3.3.3</td>
<td>SWSI system shall provide capability for personnel to install
vendor-supplied software fixes and upgrades</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>ALL</td>
<td>CDS</td>
<td></td>
</tr>
<tr class="even">
<td>5.3.4</td>
<td>SWSI shall be configured redundantly (e.g., a prime and a backup)
for both Open and Closed IONET. Therefore, there is no requirement for
maintaining an on-site supply of spare components</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td>Release 1</td>
<td>HA</td>
<td></td>
</tr>
<tr class="odd">
<td><em>6</em></td>
<td><em>Documentation</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>6.1</td>
<td>SWSI operations personnel shall be provided with all documentation
needed to perform the functions indicated above</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>6.2</td>
<td>All documentation shall be developed in accordance with the Data
Requirements List (DRL) and Data Item Descriptions (DIDs). The DRL lists
each document to be provided and the DIDs describe the purpose, content,
and format of each document</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>6.3</td>
<td>Document requirements list (TBS)</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em><strong>7</strong></em></td>
<td><em><strong>Trainning</strong></em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>7.1</em></td>
<td><p><em>General:</em></p>
<p>The training policies, plans, and procedures shall provide for
orderly transition into sustained operations and maintenance</p></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td><em>7.1.1</em></td>
<td><em>General Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.1.1</td>
<td>The training program shall include a definition of the
qualifications required by operations and maintenance personnel to meet
position description skill requirements</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.1.2</td>
<td>A training plan to define the phasing, methods and techniques for
achieving the requisite skill levels, using curricula and course
materials for skill/qualification areas within each position description
shall be included</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.1.3</td>
<td>Training devices and equipment shall be included</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.1.4</td>
<td>Administrative support to implement the training program shall be
included</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>7.1.2Number range head4Number range head5</em></td>
<td><em>Skill Area Requirements</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.2.1Number range head5a</td>
<td>Operator training shall cover the SWSI network overview</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.2.2Number range head5b</td>
<td>Operator training shall cover the SWSI concept of operation</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.2.3Number range head5c</td>
<td>Operator training shall cover detailed SWSI operational
procedure</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.2.2a Number range head5</td>
<td>Maintenance training for both hardware and software shall cover the
SWSI maintenance concept</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.2.2b</td>
<td>Maintenance training for both hardware and software shall cover
diagnostics and troubleshooting</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.2.2c</td>
<td>Maintenance training for both hardware and software shall cover
detailed repair procedures and techniques including the use of available
tools and repair equipment</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.2.2d</td>
<td>Maintenance training for both hardware and software shall cover SWSI
software maintenance concepts</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>7.1.2.2e</td>
<td>Software maintenance training shall include debugging
techniques</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.2.2f</td>
<td>Training shall cover maintenance of both operational and support
software</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>7.1.3Number range head4Number range head5</em></td>
<td><em>Training Devices and Equipment</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.3.1</td>
<td>SWSI training devices and equipment for maintenance training shall
be specified in the Training Plan</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><em>7.1.4Number range head4Number range head5</em></td>
<td><em>Training Support</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>7.1.4.1</td>
<td>Administrative support for training shall provide for the testing
and certification of students</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>