Operational Interface Procedures for the South Pole TDRSS Relay ...

532-OIP-NCC/SPTR 

MISSION OPERATIONS AND DATA SYSTEMS DIRECTORATE 

National Aeronautics and 

Space Administration 

Operational Interface Procedures 

for the South Pole TDRSS Relay 

System 

Goddard Space Flight Center 

Greenbelt, Maryland 

December 1997

Preface 

This document describes the network architecture/operations capabilities of the South Pole 

Tracking and Data Relay Satellite System (TDRSS) Relay System. It defines the concepts of 

operations and procedures that are employed to achieve the overall objectives established for the 

SPTR Interface requirements contained herein are based on standard operating procedures 

presently used by the Goddard Space Flight Center (GSFC), and the White Sands Complex 

(WSC). 

This document is under the configuration management of the Goddard Space Flight Center 

Networks and Mission Service Projects Configuration Control Board (CCB), Code 451. 

Proposed changes to this document shall be submitted to the Code 451 CCB along with 

supportive material justifying the proposed change. 

This document has been placed in the GSFC Online Library. The Online Library is accessible via 

the World Wide Web at: 

http://tip.gsfc.nasa.gov 

Requests for hardcopies of this document must be submitted via e-mail to: 

William A. Watson.1@gsfc.nasa.gov 

Changes to this document will be made by Documentation Change Notice (DCN) or by complete 

revision only. 

Questions concerning this document and proposed changes shall be addressed to: 

Head, Space Network Projects 

Code 451 

Goddard Space Flight Center 

Greenbelt, Maryland 20771 

a2302fm iii/(iv blank) 532-OIP-NCC/SPTR

Title 

iii through xii 

1-1 through 1-5 





6-1 though 6-3 


8-1 


A-1 through A-18 

B-1 

C-1 

AB-1 through AB-4 

Change Information Page 

List of Effective Pages 

Page Number Issue 

Document History 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Original 

Document Number Status/Issue Publication Date CCR Number 

532-OIP-NCC/SPTR Original December 1997 530/1031 

a2302fm v/(vi blank) 532-OIP-NCC/SPTR

DCN Number Date/Time 

Group (AMS 

Only) 

DCN Control Sheet 

Month/Year Section(s) 

Affected 

Initials 

a2302fm vii/(viii blank) 532-OIP-NCC/SPTR

Contents 

1.1 Purpose.................................................................................................................. 1-1 

1.2 Scope..................................................................................................................... 1-1 

1.3 SPTR System Overview ......................................................................................... 1-1 

1.4 Reference Documents............................................................................................. 1-5 

Section 2. Spaceflight Tracking and Data Network 

2.1 General .................................................................................................................. 2-1 

2.2 Management Responsibilities.................................................................................. 2-1 

2.3 Network Control Center......................................................................................... 2-1 

2.3.1 General......................................................................................................... 2-1 

2.3.2 Network Control Center Responsibilities ...................................................... 2-1 

2.3.3 System Description....................................................................................... 2-2 

2.3.4 Primary Points of Contact............................................................................. 2-2 

2.3.5 Staffing......................................................................................................... 2-2 

2.4 Space Network....................................................................................................... 2-3 

2.4.1 General......................................................................................................... 2-3 

2.4.2 Space Segment............................................................................................. 2-3 

2.4.3 Ground Segment .......................................................................................... 2-3 

2.5 White Sands Complex ............................................................................................ 2-4 

2.5.1 Description................................................................................................... 2-4 

2.5.2 White Sands Complex Responsibilities.......................................................... 2-4 

2.5.3 Tracking and Data Relay Satellite ................................................................. 2-4 

2.5.4 SPTR Equipment Configuration/Data Flow .................................................. 2-4 

2.5.5 Staffing......................................................................................................... 2-5 

2.6 STDN Support Elements........................................................................................ 2-6 

2.6.1 General......................................................................................................... 2-6 

2.6.2 NASA Integrated Services Network ............................................................. 2-6 

a2302toc ix 532-OIP-NCC/SPTR

2.6.3 Flight Dynamics Facility................................................................................ 2-7 

Section 3. SPTR Site Overview 

3.1 General .................................................................................................................. 3-1 

3.2 Description............................................................................................................. 3-1 

3.3 SPTR Ground Station Site Configuration ............................................................... 3-1 

3.4 Systems Description ............................................................................................... 3-6 

3.5 Monitor and Control............................................................................................... 3-6 

3.6 Primary Points of Contact....................................................................................... 3-7 

3.7 Staffing .................................................................................................................. 3-7 

Section 4. Administrative and Documentation Procedures 

4.1 Network Advisory Message.................................................................................... 4-1 

4.2 Document Change Notice....................................................................................... 4-2 

4.3 Operations Messages.............................................................................................. 4-3 

4.4 STDN Network Directive....................................................................................... 4-4 

Section 5. Communications Procedures 

5.1 Voice Callsigns....................................................................................................... 5-1 

5.2 Routine Voice Circuit Configuration....................................................................... 5-2 

5.3 E-Mail Communication........................................................................................... 5-4 

5.4 Facsimile Operations .............................................................................................. 5-6 

5.5 SPTR Web Site ...................................................................................................... 5-7 

Section 6. Scheduling Procedures 

6.1 Scheduling.............................................................................................................. 6-1 

6.2 Briefing Messages .................................................................................................. 6-3 

a2302toc x 532-OIP-NCC/SPTR

Section 7. Operations Procedures 

7.1 Real Time Control of TDRSS Services for SPTR ................................................... 7-1 

7.2 Internet Continuity Checks ..................................................................................... 7-2 

7.3 Verification of Internet Protocol (IP) Connectivity ................................................. 7-3 

7.4 User Science Files Management.............................................................................. 7-4 

7.5 Monitor and Control............................................................................................... 7-5 

7.6 Maintenance and Operations Coordination.............................................................. 7-6 

Section 8. Acquisition Data Handling Procedures 

8.1 SPTR State Vector Transmission............................................................................ 8-1 

Section 9. Reporting Procedures 

9.1 Problem Reports..................................................................................................... 9.1 

9.2 TDRSS Trouble Reports ........................................................................................ 9-3 

9.3 Discrepancy Reports............................................................................................... 9-4 

Appendix A. SPTR Software Users Guide 

Appendix B. South Pole Local Operating Procedures 

Appendix C. South Pole Equipment Maintenance Procedures 

Abbreviations and Acronyms 

a2302toc xi 532-OIP-NCC/SPTR

Figures 

1-1 SPTR Data Flow Diagram...................................................................................... 1-4 

3-1 SPTR Site Location ............................................................................................... 3-2 

3-2 Main Dome............................................................................................................ 3-3 

3-3 Building 21, Elevated Dorm Facility....................................................................... 3-4 

3-4 SPTR Site Configuration Plan ................................................................................ 3-5 

A-1 SPTR Local Main Display .................................................................................... A-2 

A-2 Remote SPTR Display.......................................................................................... A-7 

A-3 Up/Down Converter Detailed Status Display........................................................ A-8 

A-4 S-band Power Amplifier Detailed Status Display .................................................. A-9 

A-5 Satellite Modem Detailed Status Display ............................................................ A-10 

A-6 South Pole File Server Detailed Status Display ................................................... A-14 

A-7 Spectrum Analyzer Detailed Status Display ........................................................ A-15 

A-8 UPS Display....................................................................................................... A-17 

Tables 

a2302toc xii 532-OIP-NCC/SPTR

1.1 Purpose 

Section 1. Introduction 

This document contains a detailed description of the South Pole Tracking and Data Relay Satellite 

System (TDRSS) Relay System (SPTR), the functional characteristics of the overall system, and 

information pertaining to operational activities supported. It defines the management 

responsibilities for the individual elements as they relate to the overall system, supporting facilities 

and the personnel that conduct the operational activities authorized for the SPTR. 

1.2 Scope 

The emphasis of this document is to establish the points of contact, define the interface 

procedures used by each element to conduct day-to-day operations, schedule, perform systems 

monitoring, and coordinate element-to-element operational activities. Additional procedures also 

provide voice/data communications, testing activities, and contingency provisions should they be 

required. 

1.3 SPTR System Overview 

a. The South Pole TDRSS Relay system, located at the Amundsen-Scott South Pole 

Station, Antarctica, provides high data rate communications links to the South Pole via 

the Tracking and Data Relay Satellite System (TDRSS) to support interactive 

connectivity for the Antarctic scientific experimenter community. The SPTR is managed 

and sustained by Goddard Space Flight Center (GSFC) Code 450. SPTR equipment 

located at the White Sands Complex (WSC) is maintained by WSC. SPTR equipment at 

the South Pole is maintained by NSF under the direction of Code 450. 

b. The SPTR system can only use the highly inclined TDRS-F1 spacecraft currently located 

at 49 degrees West longitude. TDRSS service consists of S-band Single Access Forward 

(SSAF) and S-band Single Access Return (SSAR), full duplex communications at 1 Mbps 

(1024 kbps), and K-band Single Access Return (KSAR), simplex communications at 1 to 

50 Mbps. The view window for daily communications is 2 to 2.5 hours. The SPTR 

system uses TCP/IP protocol for data transfer to user sites. All data transfer is 

automatic. Any retransmission for SPTR links errors are handled automatically. The 

SPTR KSAR file transfer process will continually check for new science files placed on 

the South Pole fileserver as long as SPTR is active. The SPTR will also transfer the data 

to the WSC fileserver as long as there is sufficient time remaining in the schedule TDRS- 

1 service period. 

c. A web site is maintained at GSFC by SPTR Sustaining Engineering to provide SPTR 

users with South Pole SPTR configuration and status display pages. During the 

scheduled SPTR data transfer times these displays are updated daily. 

a2302s1 1-1 532-OIP-NCC/SPTR

d. In conjunction with the TDRSS usage, the South Pole experimenters also employ the 

Geostationary Operational Environmental Satellite (GOES)-3 and the Lincoln 

Experimental Satellite (LES)-9 communications links, operated by the University of 

Miami at Malabar, Florida to transfer data. Data is transferred via TCP/IP format using a 

local Internet Service Provider (ISP) whenever the GOES or LES links are available 

1.3.1 SPTR Participating Elements 

The following is a listing of participating SPTR entities: 

a. Network Control Center (NCC), located at the Goddard Space Flight Center (GSFC), 

Greenbelt, Maryland. 

b. South Pole TDRSS Relay (SPTR) located in the Elevated Dorm Facility, South Pole, 

Antarctica. 

c. White Sands Complex (WSC), located at White Sands, New Mexico. 

d. The Tracking and Data Relay Satellite System (TDRSS) with the TDRS located at 49 

degrees West longitude. 

e. Malabar Ground Station, University of Miami, located at Malabar, Florida. 

1.3.2 SPTR Data Flow Description 

1.3.2.1 User Forward Internet Protocol (IP) Data Flow 

a. User IP traffic arriving at WSC via NSI/NISN is forwarded to a Cisco 4500 router and to 

the TDRSS Data Interface (TDI). The TDI encodes and scrambles the data and sends it 

to the LRDS to be transmitted as S-band data to the Elevated Dorm Facility (EDF) at the 

South Pole. 

b. At the EDF the data is demodulated, decoded, descrambled, and distributed via the South 

Pole LAN to user sites. 

1.3.2.2 User Retrun IP Data Flow from South Pole 

a. User scientific experiment community data can be forwarded from experimenter sites to 

the SPTR via the South Pole Local Area Network (LAN) in real time during scheduled 

support. 

b. User data can also be placed on the store/forward South Pole SPTR file server with a 2 

Gigabyte SCSI hard drive. 

c. At the daily TDRS support time, S-band user traffic is serialized and transmitted in 

TCP/IP format to WSC. K-band user data files placed on the SPRT file server are 

transmitted in high data rate packet format to the WSC file server. 

d. Data is received at the WSC Low Rate Data Switch (LRDS). S-band real time service 

data is forwarded to the TDI for descrambling, then to the Cisco 4500 router. The Kband 

service data is placed on the WSC SPRT file server for subsequent user FTP. 


While TDRS-1 is supported at the White Sands Ground Terminal (WSGT), the router is 

connected by Fiber Optic Transceivers (FOT) through the WSC Inter-Facility Link (IFL) 

to the Cisco 4500 router at the Second TDRSS Ground Terminal (STGT). The data then 

is forwarded to the Integrated Digital Network Exchange (IDNX) equipment at WSC 

which multiplexes/switches the data in a NASA Integrated Services Network (NISN) 

channel. The data is then placed on the NASA Science Internet (NSI) Internet and 

routed to the requested destination. 

e. High data rate K-band service data is forwarded from the WSC LRDS to the White 

Sands File Server (WSFS). 

f. Users data files are then accessed by the users by FTP’ing them from the WSFS fileserver 

via the NSI. 

NOTE 

See Figure 1-1, SPTR Data Flow Diagram. 

1.3.3 GOES/LES Data Flow Description 

1.3.3.1 General 

a. South Pole scientific data communications also is supported by the GOES-3 and LES-9 

satellites for the National Science Foundation (NSF). The communications systems are 

operated and maintained by University of Miami, Malabar Ground Station, located in 

Malabar, Florida. 

b. User traffic data in IP format is routed via the NSI to the University of Miami Network 

and then forwarded to the router at the Malabar Ground Station. From there the 

command data is routed via either the GOES-3 or LES-9 satellite to the South Pole. 

User data cannot be routed simultaneously via both satellites but can be routed 

simultaneously via either satellite or the TDRS F1 satellite. The NSI router scheme 

employed for co-existence will route traffic via TDRSS first. 

NOTE 

When real time communication is not possible, message traffic can 

be stored on a 24-hour a day file server at the Malabar Ground 

Station to be forwarded as soon as possible when the GOES- 

3/LES-9 links become available or can be sent via the SPTR. 

c. User data is transmitted from the South Pole LAN in TCP/IP format via either the 

GOES-3 or LES-9 satellite to the Malabar Ground Station and then forwarded to the 

users via the University of Miami network and the NSI. See figure 1-1, SPTR Data Flow 

Diagram. 


a2302s1 

1-4 

532-OIP-NCC/SPTR 

SP 

Experiment 

SP 

Experiment 

South Pole 

LAN 

Subnets: 

CARA/Astro 

Dome/Astro 

Skylab/Clean Air 

Cargo 

FDDI 

LES-9 

Pre Amp 

D/C 

Sat Modem 

FOT 

FOT 

SPTR 

Router 

Cisco 

2514 

Xmtr/ 

U/C 

Pre Amp 

Router 

Cisco 

4000 

1.024 Mb 

Duplexer 

HPA 

U/C 

Sat Modem 

File 

Server 

Conv 

Encoder 

MCS 

UPS1 

UPS2 

Satellite 

Modem 

LNA 

D/C 


4ft 

4ft 

K-band S-band 

K-band 

Xmtr 

BPSK 

Mod 

XMT 

RCV 

Diplexor 

SSPA 

XMT 

RCV 

U/C, D/C 

W/ LNA 


SPTR Site 

TDRS -1 

2.5hrs/day 

UHF 

Xmtr 

& 

Rcvr 

FileServer 2 

MicroVax 

3200 

Malabar Ground Station Univ of Miami - RSMAS 

S-band 

SSAF 

& 

SSAR 

K-band 

KSAR 

2-50 Mb 

K-band 

KSAR 

S-band 

Xmtr 

& 

Rcvr 

Router 

Cisco 4000 

S-band 

SSAF 

& 

SSAR 

L 

R 

D 

S 

L 

R 

D 

S 

WSGT 

STGT 

2-56Kbps 

TDI 

File 

Server 

TDI 

File 

Server 

MIAATS 

Router 

Cisco 

4000 

WSGT 

Router 

Cisco 

4500 

FOTS 

IFL 

FOTS 

STGT 

Router 

Cisco 

4500 

White Sands Complex 

Figure 1-1. SPTR Data Flow Diagram 

A 

B 

RFCBBN 

Router 

Cisco 

4000 

Cisco 

2500 

I 

D 

1 Mb 

N 

X NISN 

Routes: 

LES-9 

7hrs/day 

GOES-3 

5hrs/day 

256-384 kbps 

User To SP 

• User via NSI: NSI to WSC to SP. 

• User via NSI: NSI to Cisco 2500 to MIAATS 

router to Malabar to SP. 

• User via Internet: Internet to RFCBBN router to 

MIAATS router to Cisco 2500 router to NSI to 

WSC to SP. 

• User via Internet: Internet to RFCBBN router to 

MIAATS router to Malabar to SP. 

38.4 kbps 

From SP 

• SP to WSC to NSI 

• SP to WSC to NSI to Cisco 2500 to MIAATS 

router to RFCBBN router to Internet to User. 

GOES-3 

• SP to Malabar to MIAATS router to RFCBBN 

LES-9 

GOES-3 

router to Internet to User. 

• SP toMalabar to MIAATS router to Cisco 2500 to 

NSI to User. 

1-10 Mb 

1 Mb 

60ft 

BBN 

Planet 

T-1 

Internet 

GSFC 

NASA Science 

Internet 

NSI 

JSC 

Commercial 

ISP 

User 

User 

Notes: 

A. Line betwen the MIAATS router and the 

RFCBBN router is the secondary link. 

B. Dotted lines illustrate that only one site is 

prime for SPTR data flow during an event.

1.4 Reference Documents 

a. South Pole TDRSS Relay (SPTR) Operations Concept, July, 1997 (Available on the 

SPTR Web site.) 

b. South Pole TDRS Relay Proposal, May 2, 1997 

c. Network Control Center Standard Operating Procedures, Volumes I and II, 532- 

SOP-NCC. 

d. Operations Interface Procedures Between the Goddard Space Flight Center Network 

Control Center and the White Sands Complex, 532-OIP-NCC/WSC. 

e. Operations Interface Procedures Between and NCC and STDN Users, 532-OIP- 

NCC/STDN Users. 

f. National Science Foundation South Pole Modernization (SPSM) Electronics Systems 

Preliminary Design, Version 3.00, July 14, 1997 

A2302s1 1-5/(1-6 blank) 532-OIP-NCC/SPTR

Section 2. Spaceflight Tracking and Data Network 

2.1 General 

The Spaceflight Tracking and Data Network (STDN) is managed by the Flight Projects 

Directorate, Code 400, which has delegated day-to-day operational responsibilities to the 

Networks and Mission Service Projects, Code 450. The STDN consists of the Space Network 

(SN), Ground Network (GN) and other elements operated, maintained, and controlled by the 

Flight Projects Directorate. 

2.2 Management Responsibilities 

The NCC and WSC are managed by the GSFC Flight Projects Directorate, Code 400. Within the 

Flight Projects Directorate, the Networks and Mission Service Projects (Code 450) serves as the 

principal GSFC management interface for day-to-day operation of the TDRSS. In execution of 

this function, the Networks and Mission Service Projects requires the NCC to meet specific 

responsibilities with regard to the overall TDRSS operation 

2.3 Network Control Center 

2.3.1 General 

The NCC provides the management function that schedules, controls, and monitors the 

performance of the STDN. This function includes control of all available network resources, 

schedule processing, conflict resolution, emergency scheduling , network testing, performance 

monitoring, acquisition data dissemination, data base maintenance, and service accounting. In 

addition, the NCC is responsible for the control of the following STDN activities 

a. Support of launch and real-time orbital operations. 

b. Scheduling STDN resources and monitoring overall status and support activities to ensure 

program requirements are fulfilled within the capability of network resources. 

c. Operational interfacing with network customers. 

d. Ground configuration control. 

e. Fault isolation coordination. 

2.3.2 Network Control Center Responsibilities 

a. Allocation of STDN resources and operational support. 

b. Provide network and service control. 

c. Provide service assurance for network customers including anomaly resolution via the 

NASA Space Network Anomaly Committee (SNAC). 


d. Provide customer services accounting including performance evaluation reports, service 

outage reports, and spacecraft event summary reports. 

e. Provide management control for STDN operations activities. 

2.3.3 System Description 

The NCC Data System (NCCDS) is composed of six major hardware elements, as follows: 

a. Communication and Control Segment (CCS) 

b. Service Planning Segment (SPS) 

c. Display Services (DS)/Intelligent Terminal Segment (ITS) 

d. Inter-segment Network (ISN) 

e. NCC Front-end (NFE) Local Area Network (LAN) 

f. Service Accounting System (SAS) 

2.3.4 Primary Points of Contact 

The primary points of contact for the NCC are: 

a. Technical Manager (TM). 

b. Scheduling Operator (SO). 

c. Forecast Analyst (FA). 

d. Performance Analyst (PA). 

2.3.5 Staffing 

The Operations Control Room (OCR) in the NCC contains operational positions and real-time 

displays for monitoring and controlling STDN activities. The following operator console 

positions are staffed 24 hours a day, 7 days a week unless otherwise noted. The following 

positions are the primary points of contact with the SPTR project. 

a. Technical Manager. The TM is the senior Contractor position in the NCC and is 

responsible for the supervision of the NCC operating staff and for maintaining operational 

integrity within the STDN. 

b. Scheduling Operator. The SO is an operational position within the NCC and is 

responsible for coordination of all real-time requests of the STDN resources by users. 

The SO coordinates STDN support based on customers’ requests and resource 

availability, performs and assists in real-time conflict resolution with customers, and 

disseminates STDN schedules. 

c. Forecast Analyst. The FA position is staffed 10 hours per day, Monday through Friday 

(0600-1600L). The FA is responsible for coordinating schedule requirements with SN 

customers. The FA confirms resource availability, analyzes scheduling conflicts, and 

provides possible solutions to users. The FA provides assistance in the scheduling of 


test events and schedules utilization of the NCC computer resources and receives 

STDN support requests to schedule network testing. 

d. Performance Analysts. The PA positions in the NCC are responsible for monitoring realtime 

support performance, validating performance standards, and assisting in rapid failure 

identification and restoration of services. The PA also is responsible for post-event 

problem analysis, receipt, and tracking of all Service Level Reports (SLR) and Equipment 

Status reports (ESR); conducting routine TDRSS tests; configuration of voice lines for 

use during playback; and acting as assistant to the TM assuming the TM’s responsibilities 

in the OCR during TM absences. The PAs are assigned to TDE and TDW. TDRS- 

Spare support also is conducted by the TDRS West PA. Additionally, the PA assumes 

the Acq-Track responsibilities when the ACQ-Track position is unmanned. 

2.4 Space Network 

2.4.1 General 

The SN is a National Aeronautical and Space Administration (NASA) resource consisting of 

automated space and ground segments that function interactively to provide services for SN 

customers. The SN provides Ku-band Single Access (KSA), S-band Single Access (SSA), and Sband 

Multiple Access (MA) forward, return and tracking telecommunications services between 

low earth orbiting customer spacecraft and ground-based control and data processing facilities. 

2.4.2 Space Segment 

The space segment of the SN consists of a constellation of geostationary TDRSs. The TDRS 

constellation comprises of the TDRS-East (TDE), TDRS-West (TDW), and TDRS-Spare (TDS) 

spacecraft. The stored spare space crafts are not used for testing or other customer services 

without the specific approval of the GSFC Networks and Mission Service Projects (Code 450). 

In case of a catastrophic failure of TDE, TDW or TDS, a stored spare may be moved into 

position to replace either of them. 

NOTE 

One of the stored spare spacecraft has been designated as the 

TDRS-Zone of Exclusion and has been approved to provide 

services for specific customers via the GRO Remote Terminal 

System (GRTS). 

2.4.3 Ground Segment 

a. The ground segment of the SN is located near Las Cruces, New Mexico, and consists of 

two primary ground terminals (WSGT and STGT). The SPTR system uses the WSGT 

and STGT ground terminals herein referred to as the White Sands Complex (WSC). 

b. The ground segment also provides communications interfaces using the common carrier 

Domestic Satellites (Domsat) earth stations and NASA Integrated Services Network 

(NISN). The ground segment provides limited data protection services such as data 

quality monitoring, line outage recording, and fault isolation. 


2.5 White Sands Complex 

2.5.1 Description 

The WSC is the main controlling facility for the TDRS. WSC contains all of the Automatic Data 

Processing Equipment (ADPE) necessary to control the configuration of the TDRS services that 

support SPTR data transfer. The WSC is capable of generating all command sequences needed to 

perform antenna pointing based on processed ephemeris data and to configure the TDRS payload 

to meet user support requirements. 

2.5.2. White Sands Complex Responsibilities 

a. Operate and maintain the TDRSS in response to NASA service support requirements. 

b. Provide terrestrial communications and data transmission for the customer community 

c. Develop, coordinate, implement, and maintain standard/contingency/emergency 

procedures for overall telecommunications satellite system and facilities under its control. 

d. Monitor and control each TDRS. 

e. Coordinate and schedule all anticipated service outages. 

2.5.3 Tracking and Data Relay Satellite 

a. TDRS Spare positioned at 49 degrees West longitude is capable of providing a 

telecommunication data relay interface for any authorized user spacecraft. TDRS Spare 

provides S-band and K-band service capabilities for the relay of data recorded at the 

South Pole TDRS Relay facilities. 

b. At present only K-band services and S-band Single Access services are provided; no 

Multiple Access (MA) is required. 

2.5.4 SPTR Equipment Configuration/Data Flow 


Command data transmitted to the South Pole via WSC uses the TDRS-1 SSAF service. User 

data transmitted from the South Pole via TDRS-1 may use the SSAR service for straight 

throughput to the user destination or use the KSAR service for store/forward at the WSC 2 

GigaByte hard drive file server. All data transfer is automatic. The WSC file server processing 

recreates the science data files from the serial packetized data and places them in a file directory 

that replicates the file directory in the file server at the South Pole. 

NOTE 

The NCC and the WSC is not involved in the SPTR file transfer 

process or the management of the file server file directories. 


2.5.4.2 User Forward Data 

User IP traffic data arrives at WSC via the NASA Science Internet (NSI) where the data in NRZ- 

L format is forwarded to the router and then the TDRSS Data Interface (TDI). At the TDI, the 

data is routed to a scrambler, a differential encoder for conversion to NRZ-M data, and then sent 

to a convolutional encoder. From the TDI the data is forwarded to the Low Rate Data Switch 

(LRDS) where it is then transmitted as S-band data through TDRS-F1 to the Elevated Dorm 

Facility (EDF) at the South Pole. 

2.5.4.3 Return Data 

a. User data from the South Pole arriving at WSC is forwarded to the LRDS. Data arriving 

via the S-band service is routed to the TDI where the data is descrambled. From the TDI 

the data is forwarded to the router and sent to the requested destination via the NSI. 

b. User data arriving at WSC via the TDRS K-band service is forwarded to the LRDS and 

then to the White Sands File Server (WSFS) where the replication of the South pole user 

data files occur and then stored until retrieval. The data is retrieved by the South Pole 

user via FTP. Upon transmission, data is forwarded from the server to the router where 

it is then transmitted via the Interfacility Link (IFL) to the STGT router and then via the 

NSI to the user. Retrieval can be done 24 hours a day. 

2.5.5 Staffing 

NOTE 

Currently, arriving K-band SPTR data is transmitted to the WSGT. 

In the future user data will be able to go to either STGT or WSGT. 

a. NASA Station Director (STADIR)/Assistant STADIR). The STADIR evaluates the site 

performance and acts as the Site Security Officer for the complex. The STADIR has the 

approval authority to implement procedures to respond to emergency conditions at the 

complex. The STADIR represents NASA in all official matters and directs the contractor 

in the overall maintenance and operations. The Assistant STADIR performs the 

STADIR’s functions during the STADIR’s absence or as directed by the STDIR. 

b. Site Manager (SM). The SM is the senior contractor representative for the complex. 

The SM provides the personnel to perform site management including management of ongoing 

day-to-day operations of the sire, security administration, Quality Assurance (QA) 

and Configuration Management (CM). The SM represents the STADIR and the 

Assistant STADIR in their absence. 

c. Operations Supervisor (OS). The OS is responsible for the overall operations support 

during the shift. The OS interfaces with all external entities as required to manage onshift 

operations and resources. The OS reviews/approves schedule modifications to the 

Integrated Schedule and reviews/approves Discrepancy Reports (DR) before distribution. 

The OS performs all administrative duties for the shift. The OS initiates technical 

investigations and coordinates changes/additions to operations procedures. 


d. Site Specialist (SS). The SS is the technical focal point for all WSC ground equipment 

The SS controls and monitors all ongoing and upcoming operational activities and, in the 

event of an interface anomaly or failure, directs local reconfiguration. The SS also is 

responsible for coordinating fault isolation and directing playback activities. 

e. Communications Services Controller (CSC). The CSC is cognizant of all user services 

being supported by a given TDRS. 

f. Ground Communication Equipment (GCE) Tech (GCE Tech). The GCE Tech is the onshift 

focal point for all GCE-related functional support on the GCE floor. The GCE Tech 

is the expert technician with respect to the recording and playback of user, voice, 

command, video and telemetry data. The GCE Tech also maintains the WSC tape library 

and performs circuit configuration and restoration. 

2.6 STDN Support Elements 

2.6.1 General 

STDN support elements include NISN and the Flight Dynamics Facility (FDF). 

2.6.2 NASA Integrated Services Network 

2.6.2.1 

NISN is the operational communications network for NASA. The NISN Network is a global 

communications system consisting of satellite and terrestrial circuits with diversely routed voice, 

Administrative Message System (AMS) high-speed-data, wide-band data, and video 

communications channels. NISN’s operational telecommunications circuitry carries information 

used in the operational conduct of NASA’s technical missions, programs, and projects. The 

circuits interconnect such facilities as NASA’s foreign and domestic tracking and telemetry 

acquisition sites, launch areas, Payload/Project Operations Control Centers (POCC), science data 

capture facilities, and network control centers. Primary functions of NISN’s circuitry is to 

provide voice communications and transport spacecraft telemetry, command/control and tracking 

data. Tracking data is transmitted as Low-Speed Data (LSD) via Tracking Data System (TDS) or 

as High Speed Data (HSD) on the Nascom 2000 link to GSFC. NISN provides communications 

coverage 24 hours a day, 7 days a week. However, for the SPTR project, the NASA Science 

Internet (NSI) and the NISN links provide coverage 5 days a week for 12 hours per day. 

2.6.2.2 

The primary point of contact for NISN is the Communications Manager (Com Mgr). 

2.6.2.3 Staffing 

a. Communications Manager. The GSFC Communications Manager (COMMGR) is the 

technical representative for day-to-day operation and is responsible for implementing all 

procedures necessary to resolve problems affecting the immediate operation of the NISN 

network. The COMMGR insures that all scheduled SPTR communications support is 


. provided and initiates necessary actions to respond to real-time requirements and 

restoration of the primary communications facilities. COMMGR will coordinate with 

MSFC and Ames as required to restore service via NISN and NSI respectively. 

c. Technical Controller. The Technical Controller is the central point of contact for 

configuration control, channelization, monitoring, testing and restoration of NASAowned 

or leased circuits and equipment. The Technical Controller’s functions are 

performed under the direction of the COMMGR. 

d. Voice Controller. The Voice Controller is the central controller for point-to-point and 

conferenced voice communications. The Voice Controller performs circuit patching, 

testing, troubleshooting in concert with control center and common carriers. Voice 

Controller functions are under the direction of the COMMGR. 

e. NISN/NSI Help Desk. 

f. IPNOCC. 

2.6.3 Flight Dynamics Facility 

2.6.3.1 

The FDF performs precise orbit determination for each TDRS as well as receives and processes 

SN tracking data to perform orbit determination for customer spacecraft. The FDF also evaluates 

tracking data for network evaluation and system calibration and provides acquisition planning data 

for the SN. 

2.6.3.2 

Primary points of contact for FDF are: 

a. Mission Manager (MM). 

b. Acquisition Data Analyst (ADA). 

c. Facilities Manager (FM). 

a2302s2 2-7/(2-8 blank) 532-OIP-NCC/SPTR

3.1 General 

Section 3. SPTR Site Overview 

This overview describes the South Pole TDRSS Relay site, equipment configuration, systems 

configuration as well as identifies the responsibilities and functions of the site personnel 

participating in the South Pole TDRSS Relay System. 

3.2 Description 

a. The South Pole TDRSS Relay (SPTR) is located at the Elevated Dorm Facility (EDF), 

Building 21. See figure 3-1. The system supports the relay of TCP/IP packetized user 

command data and user scientific experimenter data via the TDRS-F1 using S-band and 

K-band service. Upon arrival via TDRS SSAF service, at SPTR user IP data on the 

forward link is down-converted and demodulated before being placed on the LAN for 

transmission to user sites. Data leaving the South Pole, via TDRS SSAR service is 

modulated and up converted prior to transmission to WSC. See figure 1-1. 

b. An alternative data relay system is supported via the GOES-3 and LES-9 data links. User 

command data and user experiment data is transmitted via the GOES-3 satellite, located 

at 109 degrees West and the LES-9 satellite, located at 105 degrees West. The GOES-3 

satellite is in view 5 hours each day and the LES-9, 7 hours each day. The GOES/LES 

facility at the South Pole is located in Building 21 and is connected to the same South 

Pole LAN as SPTR. Other GOES equipment (modems and router) are located in the 

Communications Annex inside the Communications Building under the main dome. See 

figure 3-2. 

3.3 SPTR Ground Station Site Configuration 

a. Elevated Dorm Facility. The EDF houses two racks of equipment which contain a 

Monitor and Control System, Data Server, Uninterrupted Power Source (UPS), Cisco 

Routers, with a Ku-band and S-band antenna mounted on the roof. See figure 3-3. 

b. Local Area Network. The South Pole LAN serves as the data link between user 

experimenter sites and the EDF. User data transported on the LAN to the EDF for SPTR 

transfer via the KSAR service is stored on the South Pole 2 GigaByte hard drive file 

server. 

c. See figure 3-4 for the site configuration plan. 


Figure 3-1. SPTR Site Location 


Figure 3-2. Main Dome 


Figure 3-3. Building 21, Elevated Dorm Facility 


Figure 3-4. SPTR Site Configuration Plan 


3.4 Systems Description 

The South Pole TDRSS Relay System is housed in the EDF, room 204 and consists of the 

following subsystems: 

a. TDRS Interface Subsystem (TIS). This system is the interface to TDRS-F1. The TIS 

consists of one K-band and one S-band antenna and the associated radio frequency 

systems and baseband equipment needed to interface SPTR with TDRS. The RF systems 

are housed in the EDF with the K and S band antennas are mounted on the roof of the 

EDF. The 3 dB beam width for the S-band antenna is 7.6 degrees (2215 MHz) and 1.2 

degrees (15.0034 GHz) for the K-band antenna. 

b. Ground Communications Subsystem (GCS). This subsystem interfaces the South Pole 

LAN with the TIS. The GSC is housed in the EDF and for K-band service consists of a 

PTP, convolutional encoders, B/QPSK modulators and transmitters (HPAs). For S-band 

service there is a router, satellite modem, up/down converters and a transmitter. 

c. Monitor and Control Subsystem (MCS). This subsystem monitors and controls the 

equipment in the South Pole Relay System, provides equipment status and operational 

statistics via the SP LAN. The MCS is located in the EDF and consists of various 

interface boards and one computer. 

d. South Pole LAN. The LAN, located at the South Pole Station, is a fiber optic data path 

that connects all the scientific experiment users together and provides the interface to the 

SPTR. 

NOTE 

Further information detailing the function of each subsystem 

component is contained in the Appendix C. 

3.5 Monitor and Control 

a. The SPTR control process at the South Pole is automated to allow hands-off day-to-day 

operations. The SSAR/KSAR transmitters are active all the time but placed in a standby 

ready mode (i.e. muted or placed into dummy loads). When the scheduled SAF link is 

received at the South Pole, the transmitters are automatically configured to the antennas 

for TDRS to acquire the return links. When support is terminated (SSAF LOS at South 

Pole), the transmitters are once again placed in the standby mode. 

b. The MCS uses a Labview stand alone PC program to remotely control SPTR at the 

South Pole. Access to SPTR is password controlled. SPTR Sustaining Engineering at 

GSFC and/or local South Pole maintenance personnel will implement any fault isolation 

and/or direct configurational changes needed to keep SPTR operational when failures 

occur. 


3.6 Primary Points of Contact 

a. The operational point of contact for the South Pole is: 

ASA Com Tech 

b. The operational point of contact for the Malabar Ground Station is: 

3.7 Staffing 

University of Miami, Paul Eden 

The SPTR system is automatic and remotely controlled. Maintenance and operations are 

performed on a request only basis by the ASA Com Tech. 


Section 4. Administrative and Documentation 

Procedures 

4.1 Network Advisory Message 

4.1.1 Purpose 

This procedure describes usage, approval and distribution of Network Advisory Messages 

(NAM). 

4.1.2 Participants 

a. NCC. 

b. South Pole. 

c. WSC 

4.1.3 Procedure 


The NAM provides a means to advise STDN elements of current information pertaining to system 

capabilities/constraints, suggested operational procedures to optimize support, and any other 

information that may be deemed pertinent. NAMs are sequentially numbered. 

4.1.3.2 NAM Approval and Distribution 

a. The TM reviews and approves all NAMs prior to transmission. 

b. After approval, the NAM is transmitted via e-mail to WSC and the South Pole. 

c. The received NAM is to be distributed in accordance with each element's internal 

procedures. 


4.2 Document Change Notice 

4.2.1 Purpose 

This procedure describes usage and distribution of Document Change Notices (DCN) from the 

NCC . 


a. NCC. 

b. WSC. 

c. South Pole. 



a. A DCN is used to effect a permanent change to a STDN document. DCNs are 

distributed by printed page or electronically via e-mail with fax backup. 

b. DCNs for a specific document are consecutively numbered beginning with 001. When 

the document is updated by revision, the DCN numbers are recycled to 001. 

c. DCNs may originate from a NASA line organization or from the NCC. 

d. DCNs become part of the document on issuance, unless otherwise specified. If a DCN 

contains erroneous information, the information in error can only be corrected by 

another DCN. 

4.2.3.2 DCN Distribution 

After the DCN has been approved by the Code 450 CCB (Configuration Control Board), the 

NCC will e-mail the DCN to the South Pole and WSC. The receiving facilities are responsible for 

prompt posting of the DCN to the applicable document. 


4.3 Operations Messages 

4.3.1 Purpose 

This procedure describes usage, approval, and distribution of Operations Messages (OPN) from 

the NCC. 


a. NCC. 


c. WSC. 



a. The OPN is used to transmit operational information during non-mission, or when other 

Administrative Message System (AMS) formats are not applicable. OPNs are used to 

furnish information of a general nature. OPNs are not used to direct, authorize, 

schedule, or modify mission documentation and configurations. OPNs may be used to 

provide implementation dates for documentation that is not mission-unique. 

b. An OPN may be addressed to or from the NCC or other STDN element. OPNs 

originated by elements other than the NCC provide the NCC an information copy. 

4.3.3.2 OPN Transmission 

At the NCC, the originator of an OPN reviews and approves all outgoing OPNs prior to 

transmission. After approval, the OPN is transmitted via e-mail to WSC and the South Pole. 


4.4 STDN Network Directive 

4.4.1 Purpose 

This procedure describes the usage, coordination, transmission, and acknowledgment of STDN 

Network Directives (SND). 


a. WSC SS. 

b. NCC. 

1. ND. 

2. TM. 



a. An SND is used by the NCC to provide operational direction for general support and 

specific missions prior to the issuance of ISI 001, and for special activities that are not 

mission-related. SNDs may be use for, but are not limited to, issuing operations 

instructions, authorizing tape shipments, approving unique equipment 

installation/modification, and approving temporary mission-critical equipment 

configurations or changes (installation or removal), 

b. All SNDs are originated by the NC and issues in sequential order commencing with 001. 

SND become effective on receipt and expire after 60 days, or sooner if indicated on the 

expiration line. SNDs may also terminate on completion of action, as indicated on the 

expiration line of test. SNDs that are not self-canceling may be canceled by another 

SND. 

4.4.3.2 Transmission and Acknowledgment 

a. SND content is verbally coordinated between the TM and SS prior to transmission. 

b. The WSC SS acknowledges the SND by transmitting an Acknowledge message to the 

TM. 


Section 5. Communications Procedures 

5.1 Voice Callsigns 

5.1.1 Purpose 

This procedure defines the NCC and WSC operations position voice callsigns used on the 

SCAMA circuits. 


a. NCC. 

b. WSC. 


Position and voice callsign are listed as follows: 

a. NCC 

b. WSC 

Position Callsign 

1. Technical Manager TM 

2. Scheduling Operator NCC Scheduling 

3. Forecast Analyst NCC Forecast 

4. Performance Analyst PA 

Position Callsign 

1. STGT Operations Supervisor STGT OS 

2. STGT Site Specialist STGT Ops 

3. STGT GCE Technician STGT Tech 

4. WSGT Operations Supervisor White Sands OS 

5. WSGT Site Specialist White Sands Ops 

6. WSGT GCE Technician White Sands Tech 


5.2 Routine Voice Circuit Configuration 

5.2.1 Purpose 

This procedure defines the basic voice circuit configurations used to support routine SPTR 

operational activities. 


a. NCC. 

b. Nascom Voice Control. 

c. WSC. 

d. Malabar Ground Station (MGS). 

e. South Pole Comm Tech. 


Voice circuit communications for SPTR operations will be via commercial telephone lines patched 

to Nascom SCAMA circuits. Facsimile circuits are discussed in the Facsimile Operations 

procedure. 

5.2.4 NCC Voice Circuits 

The following are pertinent console black telephone numbers for the NCC Operations Control 

Room (OCR) positions: 

1. Technical Manager: 301-286-1817. 

2. Scheduling Operator: 301-286-1834/1835. 

3. Forecast Analyst: 301-286-8171/1871. 

4. Performance Analyst: 301-286-1827/1828 

5.2.5 SPTR Voice Circuit Configuration 

Voice communications with the South Pole is via Malabar Ground Station and the ATS-3 

satellite. The communications link is half-duplex. 

5.2.5.1 Calls to the South Pole 

a. Calls can be placed only when the satellite is in view of the South Pole. (Malabar is in 

view of ATS-3 all the time). ATS-3 view periods are published by Malabar and placed 

on the SPTR collective as the ATS Schedule. The schedule is updated approximately 

once a month or as needed. 


. To contact the South Pole call, 407-723-6715 (Malabar Ground Station) and allow the 

phone to ring 7 times. (At this point the caller will be voice controlling the phone patch 

to ATS-3). 

c. The South Pole receiver will ring and after the third ring morse code tones commence. 

After the 7 th ring the caller should announce him/herself and ask the South Pole to 

answer. The South Pole Comm Tech will answer, and forward the call to the requested 

site. In case of difficulties, Malabar Ground Station monitors calls and will assist as 

necessary. 

NOTE 

The South Pole communications link is half-duplex. During the 

conversation, the caller must stop talking to allow the party at the 

Pole to speak and vice versa. 

5.2.5.2 Calls from the South Pole 

When the ATS-3 satellite is in view of the South Pole, calls can be placed using instructions at the 

station. 

5.2.6 White Sands Complex Voice Circuits 

The WSC may be contacted by the NCC via SCAMA lines on the TDRS-1 Coord, TDRS-2 

Coord, or the TDRS-3 Coord. WSC operations personnel also may be contacted via commercial 

telephone at their respective office or console positions: 

a. STGT Operations Supervisor: 505-527-7157. 

b. STGT Site Specialist: 505-527-7216. 

c. STGT GCE Tech: 505-527-7177. 

d. WSGT Operations Supervisor: 505-525-6281 

e. WSGT Site Specialist: 505-525-6230 

f. WSGT GCE Tech: 505-525-6371 

5.2.7 Malabar Ground Station 

The Malabar Ground Station may be contacted via commercial telephone at: 407-723-3024. 


5.3 E-Mail Communication 

5.3.1 Purpose 

This procedure discusses the e-mail communications systems for SPTR. 


a. NCC. 

b. SPTR. 

c. WSC. 

d. Malabar Ground Station. 


5.3.3.1 Operations 

The primary means for SPTR operational communications will be via e-mail. E-mail destined for 

the South Pole is sent via the Malabar Ground Station. There the e-mail is stored on a VAX 

server and waits until the GOES-3/LES-9 satellite is in view of the station. The e-mail is then 

transmitted to the South Pole. Please note, due to this configuration, there may be some lag time 

between sent and received e-mail. The following is a list of e-mail addresses for SPTR entities: 

a. NCC 

NOTE 

All operational e-mail not sent directly to the TM should include 

the TM on the cc line. 

1. TM: tech.manager@nccmail.gsfc.nasa.gov 

2. FA: forecast.analyst@nccmail.gsfc.nasa.gov 

3. SO: scheduling.operator@nccmail.gsfc.nasa.gov 

4. PA: performance.analyst@nccmail.gsfc.nasa.gov 

b. STGT TOCC2: STGTOS@tdrss.wsc.nasa.gov 

c. WSGT TOCC1: WSGTOS@tdrss.wsc.nasa.gov 

d. SPTR collective: sptr@listserv.gsfc.nasa.gov 

NOTE 

All SPTR schedules, problem reports, responses to users, NAMs, 

etc. will use the SPTR collective. The collective is managed by the 

NCC. 

e. Malabar Ground Station: eden@atsvax.rsmas.miami.edu 


5.3.3.2 Engineering, Maintenance and Operation 

The e-mail collective for engineering and M&O issues coordination between NASA and NSF is: 

TBD. The collective is managed by GSFC Code 450. 


5.4 Facsimile Operations 

5.4.1 Purpose 

This procedure discusses facsimile (FAX) operations. 


a. NCC. 

b. WSC. 

c. South Pole. 

d. Malabar GND STA. 



Complete operating and maintenance instructions for facsimile transmission are provided in the 

Program Support Communications Network (PSCN) Facsimile System Directory. 

5.4.3.2 Operations 

a. All incoming and outgoing faxes are logged in accordance with internal procedure. The 

following lists the SPTR participants and their fax numbers. 

1. NCC: 301-286-6556. 

2. South Pole: TBD 

3. STGT TOCC2: 505-527-7233. 

4. WSGT TOCC1 505-525-6229. 

5. Malabar Ground Station: 407-951-1765 

b. Fax messages sent to the South Pole should be addressed: 

To: TBD 

Attn: Names of South Pole operations personnel 


5.5 SPTR Web Site 

5.5.4 Purpose 

This procedure describes the SPTR web site address and the display pages. 


a. SPTR Users. 

b. NCC. 

c. WSC. 



The SPTR web site is maintained by the GSFC Code 450 and is designed to provide 

configuration and status display pages for performance monitoring. 

5.5.2.2 Web Site Access 

The SPTR web site may be accessed using the following address: TBD. 

5.5.2.3 Web Site Display Pages 

TBD 


6.1 Scheduling 

6.1.1 Purpose 

Section 6. Scheduling Procedures 

This procedure describes the method to schedule view periods for user data transfer. 


a. SPTR. 

b. NCC. 

1. SO. 

2. FA. 

3. Forecast Scheduler 

4. Real-time Scheduler 

c. FDF. 

d. WSC. 



User data transfer via SPTR is scheduled via TDRS view periods supplied by FDF. A SPTR 

schedule containing two weeks of TDRS view periods will be coordinated and transmitted each 

week by the NCC. 

6.1.3.2 SPTR Priority 

Currently, TRDS-1 at 49 degrees W longitude provides ELV launch support, SN user spacecraft 

emergency support, SN user critical support, and occasional overflow of SN user normal support 

during STS missions. There are also daily BRTS events to maintain the TDRS-1 state vector. 

The daily SPTR communication times will have a priority just below normal SN user support. 

NCC scheduling is instructed to make every effort not to preempt the limited daily SPTR view 

periods. Any times relinquished for high priority activities will be reflected in the SPTR Schedule. 

6.1.3.3 Schedule Preparation and Dissemination 

View periods for an upcoming two week period are prepared by FDF and placed on the FDF 

product server web site at http://fdd.gsfc.nasa.gov/FDD_products.html. The Forecast Scheduler 


will use the FDF view periods from the web site to prepare the weekly (two week view period) 

SPTR schedule. If there are changes to the view periods, FDF will e-mail a change alert to the 

Forecast and Real-time Schedulers, noting the changes. Once prepared, the two-week SPTR 

Schedule is transmitted by the NCC Forecast Scheduler to SPTR users via the e-mail SPTR 

collective described in 5.3.3.1d each Monday. The Schedule shows the week’s schedule starting 

on the upcoming Monday and the following week’s schedule. 

NOTE 

If less than 15 minutes is available on any given day for SPTR 

services, SPTR will not be scheduled for that day. 

6.1.3.4 SPTR Schedule Updates 

If there are any changes to a released SPTR Schedule, due to support conflict, or TDRS 

maneuvers, the NCC Real-time Scheduler will e-mail an entirely new two-week schedule with the 

changed periods identified to the SPTR collective. Each update is consecutively numbered (e.g., 

12/97-1). There will only be one SPTR schedule in effect (one e-mail) that will identify SPTR 

changes or cancellations as required. 

NOTE 

In the event of near-real-time conflicts causing loss of SPTR time, 

the NCC will transmit a notification via the SPTR collective. 

6.1.3.5 Routine SHO Transmission 

The NCC schedules the daily SPTR contacts for the TDRS-1 SSAF/SSAR/KSAR services by 

locally generating and transmitting the required SHO(s) to WSC, based on the latest SPTR 

schedule, as part of the daily bulk schedule transmission. 

6.1.3.6 SHO Execution 

The WSC supports scheduled SPTR transmission times based upon the services and event start 

and stop times as scheduled by the NCC. 


6.2 Briefing Messages 

6.2.1 Purpose 

This procedure defines the purpose of Briefing Messages (BM) and the method of transmission to 

the South Pole. 


a. NCC. 




a. The BM is the method used by the NCC to provide supplemental information applicable 

to a particular simulation or test activity. BMs are not used to update or change 

documentation or to schedule SPTR resources. 

b. Each BM identifies the type of activity to be supported, date and time of support, 

participants, and designated point of contact. BMs are limited to information, 

definitions, and/or procedures concerning a specific test or simulation. Refer to the 

Spaceflight Tracking and Data Network Test and Simulation Support Plan, 530-NOP- 

STDN/TS for more information. 

6.2.3.2 Transmission 

NOTE 

Any questions concerning activities in a BM and/or schedule are 

reported verbally to TM for further coordination with the 

designated point of contact. 

a. All BMs relevant to a test or simulation are originated by the NCC and are based upon 

discussions between the NCC and the South Pole. Each is transmitted via e-mail after 

approval by the originator. 

b. The NCC transmits BMs to the South Pole as far in advance as possible of the scheduled 

support period. Normally, the required BMs are transmitted at least 3 working days 

before the scheduled activity. 


Section 7. Operations Procedures 

7.1 Real-time Control of TDRSS Services for SPTR 

7.1.1 Purpose 

This procedure describes the monitoring of scheduled links during SPTR service. 


a. WSC CSC. 

b. NCC. 


7.1.3.1 Operation 

a. During SPTR services the Communications Services Controller (CSC), will manage the 

scheduled links from SHO start to stop by monitoring acquisition and equipment status 

and reconfigure the ground equipment when required. 

b. In the event auto-reacquisitions fail to keep the return services in lock to provide 

continuous SPTR communications, the CSC will generate a Ground Control Message 

Request (GCM) to the WSC ADPE. 

7.1.3.2 Contingency WSC Cisco Router Operation 

If the Cisco 4500 router fails at either WSGT or STGT the CSC will notify the NISN Trouble 

desk at 205-544-1771 and perform work-around installation of V.35 null modem cable as 

described in the Appendix. A replacement part will be ordered by the NISN Trouble desk and 

will be sent to WSC. WSC will advise the NCC of any action taken. 


7.2 Internet Continuity Checks 

7.2.1 Purpose 

This procedure describes how the NCC can verify South Pole or WSC router integrity during 

fault isolation. 


a. NCC. 



To verify the continuity with the Cisco 4500 routers at WSC and South Pole router and 

equipment for fault isolation purposes a Ping test is performed. 

7.2.3.2 Test Operation 

a. To perform the test, go to DOS, then type in “ping” followed by a space and then type in 

one of the applicable SPTR IP addresses: 

1. STGT Router 

2. WSGT Router 

3. South Pole SPTR Router 

4. South Pole LAN Router to Ginko 

5. South Pole Monitor and Control System. 

NOTE 

Since IP addresses have a sensitivity, the operations positions 

performing fault isolation using ping or traceroute have been 

provided the addresses. 

b. The Internet has various search engine mechanisms which have the capability to ping 

locations using their web site as a source. Also, there are numerous PC software utility 

programs that have ping and traceroute capability and that use you computer as the 

source. For MacIntosh the WhatRoute shareware program can be used. 


7.3 Verification of Internet Protocol (IP) Connectivity 

7.3.1 Purpose 

This procedure describes the way to verify connectivity to the South Pole by using a Traceroute 

message. 


a. NCC. 

b. SPTR Users. 

c. Malabar Ground Station. 


a. While the SPTR is providing support of user data, connectivity with the South Pole could 

also occur via the GOES-3/LES-9 links via Malabar during simultaneous operations. The 

user can verify IP connectivity and routing by using an IP Traceroute message. Use the 

traceroute utility on any search engine or enter “traceroute” in the search box. For 

Yahoo, the traceroute utility address is, http://net.yahoo.com/cgi-bin/trace.sh? 

b. To do a traceroute through Malabar, on the traceroute utility page enter the following 

address: atsvax.rsmas.miami.edu 

c. To do a traceroute through SPTR enter the following address: TBD 


7.4 User Science Files Management 

7.4.1 Purpose 

This procedure describes the management of user science files on the South Pole file server. 


a. SPTR Users. 

b. WSC. 



SPTR users are responsible for placing science files on the South Pole file server, acquiring the 

files from the White Sands File Server (WSFS) and deleting files from the White Sands file server. 

Files placed on the South Pole server are serialized and transmitted as a duplicate copy to WSC. 

The “original file” remains at the South Pole server in case a retransmission is necessary. 

Successfully transmitted files to WSFS are automatically deleted from the South Pole server. 

7.4.3.2 Placement of Files on South Pole File Server 

Users may place science files on the South Pole file server for KSAR TCP/IP service through 

TDRS-1. When placing files on the South Pole file server users must include the South Pole 

SPTR file server IP address as the destination. 

7.4.3.3 Acquisition of User Files from WSC File Server 

a. Files transmitted from the South Pole to WSC via the KSAR TCP/IP service will be 

normally transmitted to the White Sands file server at WSGT or may be on the STGT file 

server when TDRS is supported via STGT. Users can then access their files by FTPing 

the files from the appropriate file server via the Internet connection to WSC. 

7.4.3.4 Deletion of files from WSC File Server 

After the successful acquisition of user science files from the WSC file server, the user is 

responsible for deleting the file from the server. 


7.5 Monitor and Control 

7.5.1 Purpose 

This procedure describes how the SPTR will be monitored/controlled and the local or remote 

implementation of fault isolation during system failures. 


a. Code 450 

b. South Pole Maintenance. 



A Labview stand alone MCS program is used to remotely control SPTR at the South Pole. 

Access to SPTR is password controlled. SPTR Sustaining (Code 450) will monitor and control 

the SPTR. During failures Code 450 will remotely implement fault isolation and switching to 

redundant equipment or direct South Pole Maintenance personnel to locally fault isolate and 

perform failure restoration. 

7.5.3.2 Monitor and Control 

See Appendix A for detailed information concerning the Labview software program for remote 

monitor and control and fault isolation of SPTR. 

7.5.3.3 Remote Fault Isolation and Anomaly Resolution 

Code 450 will coordinate with South Pole Maintenance to implement restoral. The Code 450 will 

either contact the South Pole via commercial telephone (see procedure 5.2) or via e-mail using the 

engineering maintenance and operation e-mail collective (see procedure 5.3). Code 450 will 

provide the South Pole with as much information as possible related to the anomaly. South Pole 

maintenance will e-mail to Code 450 any findings related to the anomaly as well as describe any 

systems corrections. 


7.6 Maintenance and Operations Coordination 

7.6.1 Purpose 

This procedure describes how WSC and SP maintenance and operations needs are coordinated. 


a. NCC. 

b. FDF. 

c. Code 450. 

d. WSC. 

e. Malabar Ground Station. 

f. South Pole Maintenance and Engineering. 



Maintenance and operations coordination for SPTR problems, software upgrades, SPTR, changes 

or enhancements are handled through the M&O e-mail collective. The address is TBD. The 

collective is managed by GSFC Code 450. In addition to M&O coordination, operations 

procedures updates, DCNs etc. will be available on the collective to support documentation 

updates. 

7.6.3.2 South Pole M&O 

South Pole maintenance activities include fault isolation of the SPTR at the South Pole and 

possibly operations of the SPTR software and hardware to perform restoration of all equipment at 

the South Pole. 

7.6.3.3 WSC M&O 

Maintenance and operations activities at the WSC would include the following equipment: 

a. SPTR file server 

b. TDIs 

c. PTPs 

d. FOTs and associated cabling 

7.6.3.4 WSC Router M&O 

M&O activities will be performed as required under direction of NISN at GSFC and MSFC. 


Section 8. Acquisition Data Handling Procedures 

8.1 SPTR State Vector Transmission 

8.1.1 Purpose 

This procedure describes State Vector generation and transmission. 


a. NCC. 

b. FDF. 

c. SPTR. 



The SPTR project has been assigned a dedicated Support Identification Code (SIC). A 

permanent Type-8 vector is resident in the WSC ADPE data base with the South Pole 

coordinates. As a backup, FDF will provide daily Type-8 Improved Interrange Vector (IIRV) 

state vectors to the NCC for transmission to WSC if required. 

8.1.3.2 Generation 

The FDF calculates the predicted South Pole view periods of TDRS-1 for a 2-week span and 

provides these data to the NCC two weeks prior to the support span. The daily time periods will 

change slightly each day based on the predicted orbital precession of TDRS-1. The daily schedule 

time will be centered on the most southern TDRS-1 inclination time. The start and stop time is 

based on the fixed South Pole SPTR antenna beam widths and using a horizon elevation angle of 

zero degrees factoring in refraction. TDRS-1 will move in and out of these fixed beam locations 

each day to provide the daily communications. 

8.1.3.2 Distribution 

The NCC incorporates the scheduled times into the two-week SPTR Schedule. The schedule is 

distributed via the e-mail SPTR collective. 


9.1 Problem Reports 

9.1.1 Purpose 

Section 9. Reporting Procedures 

This procedure establishes the method by which SPTR elements disseminate information 

concerning SPTR communications. 


a. NCC. 

b. SPTR Elements. 

c. WSC. 

d. Malabar Ground Station. 


a. In the event an operational problem arises, that affects scheduled operations, the SPTR 

element, at which the anomaly arose, submits a SPTR Problem Report (PRT) to the SPTR 

e-mail collective. A SPTR problem report may also be initiated by any user of the SPTR. 

The report should contain at minimum the following information items: 

1. Description of problem (include real time IP data connectivity and/or retrieval of file 

server data. 

2. Time frame of problem 

3. Impact to operations 

4. Description of any resolution taken (if known or if applicable) 

b. The NCC does not troubleshoot Internet IP problems but can coordinate and resolve 

problems within the NASA Science Internet (NSI) network. 

c. Problems concerning the TDRS will be coordinated and resolved by the NCC with WSC. 

WSC will report failures/problems according to paragraph 9.3. The NCC will contact 

NISN and/or SPTR Sustaining Engineering at GSFC as appropriate to assist in working 

SPTR problems. 


NOTE 

In addition to problem reports, the WSC Daily Operations 

Summary (DOS) will note any problems associated with the 

WSC/TDRSS equipment or operations. Also, the NCC STDN 

Daily Report (SDR) will note any reported problem that affected 

SPTR operations. 


9.2 TDRSS Trouble Report 

9.2.1 Purpose 

This procedure describes the generation and dissemination of TTRs. 


a. NCC PA. 

b. Code 450 SPTR Sustaining 


9.2.3.1 Generation 

The NCC PA will generate TDRS Trouble Reports (TTRs) for SPTR problems involving the 

TDRS-1 services and assign appropriate SN elements the action to resolve the anomalies. SPTR 

Sustaining (Code 450) may also be assigned to resolve problems associated with the South Pole. 

9.2.3.2 Dissemination 

a. The PA will place all SPTR-related TTRs on the NCC Web Site at 

ftp://ncc.gsfc.nasa.gov/pub/aattr. 

b. Daily, SPTR Sustaining will access the NCC STDN Daily Report (SDR) on the NCC 

Web site at ftp://ncc.gsfc.nasa.gov/pub/sdr to monitor for SPTR TTRs and obtain SPTR 

TTR numbers. TTRs are briefly described under the SN Anomalies section with an 

accompanying TTR reference number. To obtain the full TTR report, SPTR Sustaining 

will access the TTR Web Site mentioned in 9.2.3.2a. 

c. Upon obtaining the SPTR TTR report(s), SPTR Sustaining will transfer the SPTR TTR 

information to the SPTR Web site for dissemination. 


9.3 Discrepancy Reports 

9.3.1 Purpose 

This procedure describes the method by which TDRSS related failures/problems are reported and 

tracked. 


a. WSC. 

b. NCC. 

c. Code 450 


9.3.3.1 TDRS and SPTR Unique Equipment Anomalies 

WSC will initiate a Discrepancy Report (DR) for problems/failures related to TDRSS. Problems 

related to SPTR unique equipment (i.e., TDI, WSFS, IFL, FOTS) will also be reported by DR. 

SPTR unique equipment at WSC will be fault isolated and maintained by WSC. WSC may 

request assistance from SPTR Sustaining (Code 450) via voice or by the SPTR collective e-mail 

for M&O. 

9.3.3.2 WSC Internet Anomalies 

Problems/failures related to WSC Internet routers and the WSC NISN/NSI circuit used for SPTR 

is the responsibility of GSFC NISN. NISN will initiate troubleshooting and operations restoration 

via the COMMGR. WSC will send a DR to NCC for notification of problem. Troubleshooting 

of problem(s) may entail assistance from NISN (MSFC) and include the Malabar circuit interface 

for fault isolating NSI circuit problems. 

NOTE 

Depending on severity of circuit outage and anomaly, extended 

circuit outages may result. 


Appendix A. 

SPTR Software Users Guide 

a2302apa 532-OIP-NCC-SPTR

Appendix A. SPTR Software Users Guide 

A.1 Introduction 

A.1.1 General 

a. The SPTR project software is maintained by Code 450. The software controls, 

monitors and allows operators to troubleshoot the following South Pole 

equipment: Up/Down Converter, Traveling Wave Tube Amplifier, S-band Power 

Amplifier, Satellite Modem, File Server and Spectrum Analyzer, and 

Uninterrupted Power Source. The software consists of two programs, the local 

control and remote. SPTR remote programs are currently located at the NTTF 

SPTR Lab and the South Pole Dome area. Up to five remote sites can log in at a 

time. The software is designed for three levels of access: Administrator, operator 

and guest. 

b. The SPTR software users guide is organized by displays. There are eight 

displays: 

1. SPTR main local control display 

2. Remote SPTR display 

3. Up/Down Converter detailed parameters status display TBD 

4. S-Band Power Amplifier detailed status parameters display TBD 

5. Satellite modem detailed status parameters display 

6. File Server detailed status parameters display 

7. Spectrum analyzer detailed status parameters display 

8. Uninterrupted Power Source detailed status parameters display 

c. To gain access to the REMSPTR program, one must use a password. Passwords 

are obtained from the Administrator. Each password denotes level (administrator, 

operator or guest) and access rights. 

A.2 Local SPTR Display 

This display is colored medium blue. Detailed parameters displays accessed from this 

display are also medium blue. See figure A-1. 

a2302apa A-1 532-OIP-NCC-SPTR

Figure A-1. SPTR Local Main Display 


A.2.1 Top area 

At the top of the display there is the Quit button and the Time box. The Quit button 

allows the user to quit the program and the Time box displays, in GMT, the time when the 

last status message arrived into the system. 

A.2.4 S-Band Equipment Area 

A.2.4.1 Up/Down Converter 

TBD 

A.2.4.2 S-Band Power Amplifier 

TBD 

A.2.4.3 Satellite Modem 

The area only operates in the Auto Ops mode. In this mode the computer is running the 

satellite modem, turning on and off transmitter and constantly checking modem status. 

a. Auto Ops: This button can be toggled between on (green) and off (red). 

b. RX Config: Indicates whether receiver is configured to designated SPTR 

configuration. Yes (green), no (red). 

c. TX Config: Indicates whether transmitter is configured to designated SPTR 

configuration. Yes (green), no (red). 

d. Modem Status: This is a fault indicator, system is fine (green), anomaly (red). 

e. TX Output: If button is green transmitter is on; red it is off. Button is grayed if 

in Auto Ops or remote control. 

f. Receiver: Indicates locked or unlocked 

g. BER: Bit error rate amount after decoding 

h. Eb/No: Estimate of bit energy to noise ratio density. Measured in dB, rate goes 

up to 9.9 maximum. If rate is greater, indicator still will read 9.9dB. 

i. AOS: For S-band forward link in day of year (DOY) hours, minutes, and 

seconds. 

j. LOS: For S-band forward link, DOY:HH:MM:SS. 

k. Poll: If check is present the system has been statused. 

l. C: Indicates if computer communications with satellite modem is good. If box is 

green, yes; red, no. 

m. OPEN: Click on box to access the satellite modem detailed status parameters 

display. If button is grayed, cannot access this display. 


A.2.5 K-Band Equipment Area 

A.2.5.1 Traveling Wave Tube Amplifier 

TBD 

A.2.5.2 South Pole File Server 

A.2.5.2.1 Current Totals 

a. Poll box: See paragraph A.2.4.3k. 

b. Frames Sent: Displays number of total user data frames sent. 

c. Frame Errors: Displays number of total errors in a frame 

d. Frame Error Rate: Displays ratio of frame errors divided by frames sent. 

e. Est. Bit Error Rate: Displays estimate of total BER within all frames sent. 

f. Last update: Displays time of last update. Updates are done every minute. 

g. Frames Sent: Same as above, in last update. 

h. Frame Errors: Same as above, in last update. 

i. Frame Error Rate: Same as above, in last update 

j. Est. Bit Error Rate: Same as above, in last update 

k. Est. Throughput: Displays rough estimate of error free data rate. 

A.2.5.2.2 Last Transfer Summary 

a. Start Time: Start time of last transfer in DOY:HH:MM:SS. 

b. Stop Time: Stop time of last transfer in DOY:HH:MM:SS. 

c. Files Sent: Displays number of files sent during last transfer. 

d. Bytes Sent: Displays number of bytes sent during last transfer. 

e. Throughput: Displays error free data rate. 

A.2.5.2.3 

a. Transfer: Indicates if file transfer is ongoing. If indicator is red, transfer not 

taking place 

b. C: Indicates if computer communications with South Pole file server is good. If 

box is green, yes; red, no. 

c. OPEN: Click on box to access the South Pole File Server detailed status 

parameters display. If button is grayed, cannot access this display. 


A.2.6 Spectrum Analyzer Area 

A.2.6.1 Spectrum Display 

This visual display shows various signal selections. 

a. Test Point: Displays selected signal 

b. Peak: Displays signal peak in MHz and dBm 

c. Poll: Same as above. 

d. Control box of test point menu: Can select different signals to display in 

spectrum display. Menu selections are TBD. 

e. C: Same as above. 

f. OPEN: Same as above. 

A.2.7 Uninterrupted Power Supply (UPS) Status Box 

The South Pole SPTR system is configured with two UPS systems to ensure even power 

delivery to the SPTR system. The following indicators are the same for both UPS 

systems. 

a. Status: Indicates whether the UPS is online (green On Line lit) or not (XXXX). 

b. Ld: Indicates the load XXXXX 

c. Cap: XXXXXX 

d. C: Indicated if computer is interfaced with the UPS. If box is green, yes; red, no. 

e. OPEN: Click on this to link to the UPS detailed status parameters display. 

A.2.3 Remote Control Status Box 

In the lower right area, the connection information box shows the number of users 

connected. Below is displayed the name of the connected and their address. To the left of 

this area a scroll box allows user to dial up each user connected and their address. The 

bottom blue box displays whether the user is connected locally or remotely. The button 

below toggles between local and remote. If user wants to control system from local, then 

should select LOCAL button. On the remote SPTR display this area will display, 

“LOCAL”. 

A.3 Remote SPTR (Remsptr) Display 

This display page is colored aqua green to visually differentiate from the blue local SPTR 

display. See figure A-2. All status parameters are the same as found in paragraph A.2 

with the exception that the GMT box displays actual GMT. 


A.3.1 Log in/Log off 

a. To obtain access to the Remsptr Display, click on gray Log on/off button. A 

SPTR Log In display will pop up. Enter: 

1. SPTR IP address TBD 

2. User name 

3. Password, then click on the OK button. 

b. A message, “Welcome to SPTR” appears. Click on the OK button. The red light 

to the right of the Log on/off button changes from red to green. 

c. If a wrong password or user name is entered an “access denied” display will show. 

d. If all permitted users are logged on (a total of five) anyone else logging on will 

receive a “maximum users” display. One must wait until someone logs off to use 

the system. 

e. To log off, press gray button and click on the OK. 

A.4 Up/Down Converter Detailed Status Parameters Display 

TBD 

Figure A-3. 

A.5 S-Band Power Amplifier Detailed Status Parameters Display 

TBD 

Figure A-4. 

A.6 Satellite Modem Detailed Status Parameters Display 

This display contains all the specific status parameters needed for satellite modem 

performance. See figure A-5. 

A.6.1 Top Box Area 

This area contains the same information as found in the SPTR local and remote displays. 

It is reiterated for useful reference. The AOS and LOS display boxes display actual GMT 

time. The Continuous Wave (CW) Only button removes modulation from the carrier. 

Red signifies that the modulation has not been removed, green signifies that modulation 

from the carrier has been removed. If the Satellite Modem is in Auto Ops mode, the CW 

Only button will be grayed red. 


Figure A-2. Remote SPTR Display 


TBS 

Figure A-3. Up/Down Converter Detailed Status Display 


TBS 

Figure A-4. S-band Power Amplifier Detailed Status Display 


Figure A-5. Satellite Modem Detailed Status Display 


A.6.2 Status Area 

The parameters contained in the following three areas are for status information only. 

There are no controls. The displayed settings shows the valid SPTR configuration. When 

the unit is in Auto Ops mode, will default to these settings. 

A.6.2.1 Transmit (TX) Status Area 

a. Frequency: Displayed in MHz 

b. Data rate Displayed in bits per second (bps) 

c. Code rate: Displays type of code being used 

d. Diff Encoder: Shows if the Differential encoder which coverts data from NRZ-L 

to NRZ-M is on or off. 

e. Scrambler: Displays specified scrambler algorithm 

f. Mod type: Displays type of modulation. 

g. Mod rotation: Displays the order of data symbols 

h. Mod mode: Displays data transmit mode. 

i. Clk inv: Displays whether clock inversion is on or off. 

j. Interface: Displays name of interface to data source. 

k. Car def: Displays XXXX of carrier default 

l. Pwr lvl: Displays output power level in dBm 

m. Output: Displays whether output is on or off. 

n. Pure Carrier: Displays whether CW is on or off 

A.6.2.2 Receive (RX) Status Area 

The first eight parameters are the same as for the Transmit Status area. The remainder are 

defined as: 

a. Rec’d data rate: Displays rate of received data in bps. 

b. Rec’d freq: Displays received frequency in MHz 

c. Receiver lock: Button indicates if the receiver is locked (red) or unlocked (green) 

d. Raw BER: Displays raw bit error rate before decoding. 

e. Cor BER: Displays corrected BER 

f. Eb/No: Displays estimate of bit energy to noise ratio density. See paragraph 

A.2.4.3h. 


A.6.2.3 Faults Area 

This area is divided into three sections, Monitor and Control (M&C), Modulator, and 

Demodulator/Decoder for fault indicators. Light indicators are either red or green. Green 

indicates systems are working well, red denotes an anomaly/fault. For the Loss of Clock 

indicator for the Modulator, Loss of Data and Decoder Lock for the Demod/Decoder, 

explanations are given for these three items. 

A.6.2.3.1 M&C 

a. Reset: Power up or reset has occurred 

b. General Message: Indicates fault in control message to modem 

c. Msg Checksum: Host message checksum error 

d. Msg Byte Count: Host message byte count error 

e. Clock Activity: Clock activity fault 

f. Receive Buffer: Receive buffer overflow 

g. TX clock option PLL: Transmit clock option phase lock loop fault 

h. TT Fault: Transmit timing fault 

i. RX clock Option PLL: Receiver clock option phase lock loop fault 

A.6.2.3.2 Modulator 

a. Mod loss of data: Loss of data 

b. Loss of clock: Indicator turns red when CW in turned on. 

c. No symbol clock: no symbol clock is present 

d. Synthesizer 1 lock: Out of lock 

e. Synthesizer 2 lock: Out of lock 

A.6.2.3.3 Demodulator/Decoder 

a. Demod lock: Demod not locked 

b. Loss of data: When the satellite modem is not locked there is loss of data. 

c. Decoder lock: When the satellite modem is not locked the decoder is not locked. 

d. TX configuration: Transmit configuration anomaly. 

e. RX configuration: Receiver configuration anomaly. 


A.6.2.4 Bottom Area 

a. Comm status: Indicates anomaly with the communications link 

b. Modem fault: Indicates anomaly/fault with the modem operation. 

A.7 South Pole File Server (SPFS) Detailed Status Parameters 

Display 

This display contains all the specific status parameters needed for file server performance. 

See figure A-6. 

A.7.1 Current Totals 


It is reiterated for useful reference. The parameters contained in this areas are for status 

information only. There are no controls. The displayed settings shows the valid SPTR 

configuration. 

A.7.2 Last Transfer Summary 


It is reiterated for useful reference. 

A.7.3 Meter Box 

This is a visual display of K-band throughput. 

A.7.4 Strip Chart 

This strip chart gives a visual estimate of throughput over the course of a file transfer. 

Scroll bar below chart enables viewing of history of file transfer. 

A.7.5 Last Files Transferred 

This area contains a listing of file names and size. If the file appears on the list the file 

transfer was successful. 

A.8 Spectrum Analyzer Detailed Status Parameters Display 

This display contains all the specific status parameters needed for spectrum analyzer 

performance. See figure A-7. The GMT display box indicates time of trace. 

A.8.1 Spectrum Display 

This display is an enlarged copy of the display on the main SPTR display. 


Figure A-6. South Pole File Server Detailed Status Display 


Figure A-7. Spectrum Analyzer Detailed Status Display 


A.8.2 Spectrum Analyzer Settings Box 

This box area displays the settings of parameters that are set in the control box located to 

the right of the spectrum display. The parameters are as follows: 

a. Center: center frequency in MHz 

b. RBW: resolution band width in KHz 

c. RL: reference level in dBm 

d. VBW: video band width in KHz 

e. Atten: attenuation in dB 

f. Span: span of trace in MHz 

g. SWP: sweep time set in milliseconds 

h. Scale per vertical division: 10dB/ 

A.8.3 Spectrum Analyzer Control Box 

This box contains parameters which can be set and controlled. To change a parameter, 

use the arrows to the left of the boxes to dial up or down. Click on the purple button to 

transmit the changed setting to the spectrum analyzer. The new setting will be displayed 

in the window as well as in the settings box below the spectrum display. The SAVE 

button at the button saves all the current configurations. 

A.8.4 Test Point Box 

This box contains selectable list of signals. Click on the box to obtain listing. The signal 

that is selected is also displayed on both the local and remote SPTR display. The AUTO 

box to the right is a toggle switch. In the up position the spectrum analyzer is 

reconfigured to match the test point. 

A.8.5 Peak Box 

This box displays the same peak as displayed on the local and remote SPTR display. The 

readout is in dBm and MHz. 

A.9 Uninterrupted Power Supply Detailed Status Parameters 

Display 

This display contains all the specific status parameters needed for uninterrupted power 

supply (UPS) #1 and 2 performance. See figure A-8. 

A.9.1 UPS #1 Control 

The poll box, if checked, indicates that the system has been statused. The power button 

will indicate if the UPS system is on (green) or off (red). 


Figure A-8. UPS Display 


A.9.2 UPS #1 and #2 Status 

This area provides performance indicators for UPS #1and #2. 

a. Output Status: 

b. UPS Load %: 

c. Battery Capacity %: 

d. Battery Temperature (C): 

e. Input Line Voltage: 

f. Input Max Line Voltage: 

g. Input Min Voltage: 


Appendix B. 

South Pole Local Operating Procedures 

a2302apb 532-OIP-NCC/SPTR

Appendix B. South Pole Local Operating 


B.1 Equipment Power Up/Power Down 

TBS 

B.2 Transmitter Power On/Off 

TBS 

B.3 Antenna Pointing Procedure 

TBS 

a2302apb B-1 532-OIP-NCC/SPTR

Appendix C. 

South Pole Equipment Maintenance Procedures 

a2302apc 532-OIP-NCC/SPTR

Appendix C. South Pole Equipment Maintenance 


C.1 

TBS 

a2302apc 532-OIP-NCC/SPTR

Abbreviations and Acronyms 

ADPE Automated Data Processing Equipment 

AMS Administrative Message System 

AR Anomaly Report 

ASA Antarctic Support Associates 

BM Briefing Message 

CARA Center for Atmospherical Research in Antarctica 

CCAM Contamination and Collision Avoidance Maneuver 

CCB Configuration Control Board 

CM Configuration Management 

COMMGR Communications Manager (Nascom) 

CONUS Continental U.S. 

COTR/N Contracting Officer's Technical Representative/NCC 

COTS Commercial off the shelf 

CSC Communications Services Controller (WSC) 

CSCI Computer Software Configuration Item 

DCN Document Change Notice 

Domsat Domestic Satellite 

DR Discrepancy Report (WSC) 

ECL Emitter Coupled Logic 

EDF Elevated Dorm Facility (Building 21, South Pole) 

ESN Earth Science Network 

ESR Equipment Status Report 

ETRO Estimated time of return to operations 

FA Forecast Analyst (NCC) 

FDDI Fiber Distributed Data Interface 

FDF Flight Dynamics Facility (GSFC) 

FOT Flight Operations Team, Fiber Optic Transceiver 

a2302abac AB-1 532-OIP-NCC/SPTR

FTP File transfer protocol 

GCE Ground Communication Equipment 

GCM Ground Control Message 

GCMR Ground Control Message Request 

GCS Ground Communications Subsystem (I/F bet Ross Is. & Black Is.) 

GN Ground Network 

GOES Geostationary Operational Environmental Satellite 

GSFC Goddard Space Flight Center 

HSD High speed data 

HWCI Hardware Configuration Item 

IDNX Integrated digital network exchange (WSC) 

IFL Interfacility Link (WSC) 

IIRV Improved Interrange Vector 

IONET Nascom IP Operational Network 

IP Internet Protocol 

IPNOCC 

ISN Inter-segment Network (NCC) 

ISP Internet Service Provider 

ITS Intelligent Terminal Segment (NCC) 

JPL Jet Propulsion Laboratory 

KSA Ku-Band Single Access 

LAN Local Area Network 

LES Lincoln Experimental Satellite (Lincoln Labs, MIT) 

LHCP Left Hand Circular Polarization 

LRDS Low Rate Data Switch (WSC) 

LSD Low speed data 

MA S-Band Multiple Access 

MCS Monitor and Control Subsystem 

MDM Multiplexer/Demultiplexer 

MGS Malabar Ground Station, Malabar, Florida (University of Miami) 


MO&DSD Mission Operations and Data Systems Directorate (GSFC) 

NAM Network Advisory Message 

NASA National Aeronautical and Space Administration 

Nascom NASA Communications 

NCC Network Control Center (Greenbelt, Maryland) 

NCCDS NCC Data System 

NFE NCC Front End (NCC) 

NISN NASA Integrated Services Network 

NSF National Science Foundation 

NSI NASA Science Internet 

OCR Operations Control Room (NCC) 

OPN Operations Message 

OPS MGR Operations Manager 

OS Operations Supervisor (WSC) 

PA Performance Analyst (NCC) 

PTP Programmable Telemetry Processor 

PRT Problem Report 

RSMAS Rosentiel School of Marine and Atmospheric Science, Miami, 

Florida, University of Miami 

RHCP Right Hand Circular Polarization 

RF Radio Frequency 

SAR Synthetic Aperture Radar 

SAS Service Accounting System (NCC) 

SCAMA Switching, Conferencing, and Monitoring Arrangement (Nascom) 

SHO Scheduling Order (NCC) 

SIC Support Identification Code, Spacecraft Identification Code 

SN Space Network 

SNAC Space Network Anomaly Committee 

SO Scheduling Operator (NCC) 

SP South Pole 

SPS Service Planning Segment (NCC) 


SPTR South Pole TDRSS Relay 

SS Site Specialist (WSC) 

SSA S-Band Single Access 

SSPA Solid State Power Amplifier 

STADIR Station Director 

STDN Spaceflight Tracking and Data Network 

STGT Second TDRSS Ground Terminal 

SUPIDEN Support Identifier 

TCP Transmission Control Protocol 

TDE TDRS-East 

TDI TDRS Data Interface (WSC) 

TDRS Tracking and Data Relay Satellite 

TDRSS Tracking and Data Relay Satellite System 

TDS TDRS-Spare 

TDW TDRS-West 

TIS TDRS Interface System (SPTR) South Pole 

TLM Telemetry 

TM Technical Manager (NCC) 

TOCC1 TDRSS Operations Control Center (WSGT) 

TOCC2 TDRSS Operations Control Center (STGT) 

TOTS Transportable Orbital Tracking Station 

TT&C Tracking, Telemetry, and Command 

TTL Transistor-to-transistor Logic 

TTR Trouble Tracking Report 

TUT TDRSS Unscheduled Time 

U/C-D/C Up converter, down converter 

WSC White Sands Complex (White Sands, New Mexico) 

WSFS White Sands File Server 

WSGT White Sands Ground Terminal 


Distribution List 

Organization Name of Recipient Copies 

ATSC/TDAC/NCC NCC DOCUMENTATION/BURLEY 1 

ATSC/450 SERVICE SUPPORT LIBRARY 1 

ATSC/LIB ATSC/GCP/450 LIBRARY 1 

ATSC/WSC WSC LIBRARY/PICKOVER 1 

MALABAR GND STATION EDEN, PAUL 1 

UNIVERSITY OF MIAMI LEE, RALPH 1 

DISTRIBUTION 6 

STORAGE 0 

TOTAL 6 

To coordinate changes to this distribution list, contact the ATSC/GCP/450 Library via 

mail GSFC c/o Code 450/OSU, via phone 301-805-3897, or AMS/IDM/OSU. This 

distribution list is current as of April 1998. 

A2302dl DL-1/(DL-2 blank) 532-OIP-NCC SPTR

532-OIP-NCC/SPTR

Operational Interface Procedures for the South Pole TDRSS Relay ...

Create successful ePaper yourself

Delete template?

Save as template?