Page images
PDF
EPUB

licit additional space flight participant applications, if necessary.

(g) Authority to officially designate candidates for training, certify candidates as qualified space flight partici. pants, and assign space flight participants to specific Space Shuttle flights is reserved to the Administrator.

8 1214.1706 Program management.

The Associate Administrator for Space Flight is responsible for program management under the direction of the Committee chairperson.

8 1214.1707 Media and public inquiries.

(a) The Associate Administrator for External Relations will respond to all inquiries directed to the agency concerning space flight participants and the process by which they are selected.

(b) The names of all applicants will be withheld from public release until the space flight participants are selected by the Administrator.

plications should be directed, the opening and closing dates for applica tions, and any other information or matters determined to be pertinent to the program in general and/or the specific flight.

(b) All applications received in re. sponse to the AO will be screened to eliminate those applicants not meeting the basic qualification requirements.

(c) Remaining applications will be forwarded to the outside review panel established for the announcement in question and composed of members appropriate to the specific purposes stated in that announcement. The review panel will evaluate all the applications and recommend to NASA a list of those applicants who appear most likely to meet the purposes.

(d) NASA selection of applicants qualified to undergo necessary training and be certified for flight will be made by the Committee, based upon criteria that include:

(1) Recommendation of the outside review panel.

(2) Ability to undergo successfully the necessary period of training to ensure adaptation to flight experience and mission activities.

(3) Ability to pass medical and psy. chological examinations to minimize the possibility of hazard to persons or missions.

(4) Adaptability to living and work. ing in space.

(5) Willingness to enter into an agreement with NASA covering preflight, flight, and post-flight activities, with individual rights and responsibil. ities set forth in that agreeement.

(6) Satisfactory completion of a background investigation conducted to NASA's standards as adjudicated by the NASA Security Officer.

(e) The Committee will submit a list of those candidates suitable for selection to the NASA Administrator, who will select the requisite number to undergo the necessary training to prepare them for space flight.

(f) Those candidates who successfully complete the training will become qualified as space flight participants. Flight assignments will be made by the Administrator from this qualified group. NASA reserves the right to so

PART 1215—TRACKING AND DATA RELAY SATELLITE SYSTEM (TDRSS)

Subpart 1215.1-Use and Reimbursement

Policy for Non-U.S. Government Users

Sec.

1215.100 General. 1215.101 Scope. 1215.102 Definitions. 1215.103 Services. 1215.104 Apportionment and assignment of

services. 1215.105 Delivery of user data. 1215.106 User command and tracking data. 1215.107 User data security and frequency

authorizations. 1215.108 Defining user service require

ments. 1215.109 Scheduling user service. 1215.110 User cancellation of all services. 1215.111 User postponement of service. 1215.112 User/NASA contractual arrange

ment. 1215.113 User charges. 1215.114 Service rates. 1215.115 Payment and billing. APPENDIX A TO PART 1215- ESTIMATED SERV

ICE RATES IN 1992 DOLLARS POR TDRSS
STANDARD SERVICES (BASED ON NASA Es-

CALATION ESTIMATE)
APPENDIX B TO PART 1215-FACTORS AFTECT-

ING STANDARD CHARGES

Sec.

lab communications system, is a ShutAPPENDIX C TO PART 1215—TYPICAL USER AC- tle/Spacelab service. Cooperative misTIVITY TTIKLINE

sions are also not under the purview of AUTHORITY. Sec. 203, Pub. L. 85-568, 72 this Subpart. The arrangements for Stat. 429, as amended; 42 U.S.C. 2473.

TDRSS services for cooperative misSOURCE: 48 FR 9845, Mar. 9, 1983, unless sions will be covered in a Memoranotherwise noted.

dum of Understanding (MOU), as a

consequence of negotiations between Subpart 1215.1-Use and Reimburse NASA and the other concerned party. ment Policy for Non-U.S. Gov

Any MOU which includes provision ernment Users

for any TDRSS service will require

signatory concurrence by the Associ§ 1215.100 General.

ate Administrator for Space OperThe TDRSS represents a major in

ations prior to dedicating Office of vestment by the U.S. Government

Space Operations resources for supwith the primary goal of providing im

port of a cooperative mission. proved tracking and data acquisition (56 FR 28048, June 19, 1991) services to spacecraft in low earth orbit or to mobile terrestrial users 8 1215.102 Definitions. such as aircraft or balloons. It is the

(a) User. Any non-U.S. Government objective of NASA to operate as effi

representative or entity who contracts ciently as possible with the TDRSS.

with NASA to use TDRSS services. This is to the mutual benefit of all

(b) TDRSS. The Tracking and Data users. Such user consideration will

Relay Satellite System including permit NASA and non-NASA service

Tracking and Data Relay Satellites to be delivered without compromising

(TDRS), the White Sands Ground the mission objectives of any individ

Terminal (WSGT), and the necessary ual user. To encourage users toward

TDRSS operational areas, interface achieving efficient TDRSS usage, this

devices and NASA communication cirreimbursement policy has been estab

cuits to unify the above into a funclished to purposely influence users to

tioning system. It specifically excludes operate with TDRSS in the most effi

the user ground system/TDRSS intercient and orderly manner possible. Ad.

face. ditionally, the reimbursement policy is

(c) Bit stream. The digital electronic designed to comply with the Bureau of

signals acquired by TDRSS from the the Budget Circular A-25 on User

user craft or the user generated input Charges, dated September 23, 1959,

commands for transmission to the user which requires that a reasonable

craft. charge should be made to each identi

(d) Flexible support. Support refiable recipient for a measurable unit or amount of Government service or

quests which permit NASA, at its property from which a special benefit

option, to schedule service at any time is derived.

during the period of a single orbit of

the user mission, Missions requiring (56 FR 28048, June 19, 1991)

multiple support periods during a

single orbit may be classified as con8 1215.101 Scope.

strained support. This Subpart sets forth the policy (e) Constrained support. Support regoverning TDRSS services provided to quests which specify the exact times non-U.S. government users and the re- NASA is to provide service, or condiimbursement for rendering such serv tions of support which can be translatices. It excludes TDRSS services pro- ed into exact times for service, such as vided as standard or optional services sub-satellite positions, apogee/perigee to Space Transportation System (STS) position, etc., for which support is users under existing policy for Shuttle needed. and Spacelab (14 CFR subparts 1214.1, (f) Scheduling service period. One 1214.2, and 1214.8); i.e., user command scheduled contact utilizing a single and telemetry support, which utilizes TDRS whereby the user by requesting and is a part of the Shuttle or Space service is allotted a block of time for

operations between the user satellite and TDRSS.

8 1215.103 Services.

(a) Standard services. These are services which the TDRSS is capable of providing to low-earth orbital user spacecraft or other terrestrial users.

(1) Tracking services.
(2) Data acquisition service.
(3) Command transmission service.

(4) Emergency line outage recording in the event of a communications failure between White Sands, Goddard Space Flight Center (GSFC), and Johnson Space Center (JSC).

(5) A weekly user spacecraft orbit determination in NASA standard or bital elements as determined by NASA for TDRSS target acquisition purposes.

(6) Delivery of user data at the NASA Ground Terminal (NGT) located at White Sands.

(7) Pre-launch support for data flow test and related activities which require use of a TDRS.

(8) Pre-launch support planning and documentation.

(9) Scheduling user services via TDRSS.

(10) Access to tracking data to enable users to perform orbit determination at their option.

(b) Mission unique services. Other tracking and data services desired by the user beyond the standard service and the charges therefor, will be identified and assessed on a case-by-case basis.

(b) User data handling requirements beyond the NGT interface will be provided as a standard service to the user, to the extent that the requirements do not exceed NASA's planned standard communications system. Any additional data transport or handling requirements exceeding NASA's capability will be dealt with as a mission-unique service.

(c) No storage of the user data is provided in the standard service. NASA will provide short-term temporary recording of data at White Sands, only in event of a NASA Communications Network (NASCOM) link outage.

(d) NASA will provide TDRSS services on a "reasonable efforts” basis and, accordingly, will not be liable for damages of any kind to the user or third parties for any reason, including but not limited to failure to provide contracted-for services. The price for TDRSS services does not include a contingency or premium for any potential damages. The user will assume any risk of damages or obtain insurance to protect against any risk. [48 FR 9845, Mar. 9, 1983, as amended at 56 FR 28049, June 19, 1991)

8 1215.106 User command and tracking

data. (a) User command data may enter the TDRSS via the NASCOM interface at one of three locations:

(1) For Shuttle payloads which utilize the Shuttle commanding system, command data must enter the system via the Johnson Space Center (JSC) and is governed by the policies established for STS services (see § 1215.101).

(2) For free flyers and other pay. loads, command data must enter the system at the Goddard Space Flight Center (GSFC) if it is to be a standard service.

(3) The use of other command data entry points (e.g., the NASA Ground Terminal (NGT) at White Sands, NM, or Johnson Space Center (JSC), for payloads using an independent direct link from TDRS to the user payload] is considered to be a mission unique service.

(b) NASA is required to maintain the user satellite orbital elements to suffi

8 1215.104 Apportionment and assignment

of services. No user may apportion, assign, or otherwise convey to any third party its TDRSS service. Each user may obtain service only through contractual agreement with the Associate Administrator for Space Operations. (56 FR 28048, June 19, 1991) 8 1215.105 Delivery of user data.

(a) As a standard service, NASA will provide to the user its data from the TDRSS as determined by NASA in the form of one or more digital or analog bit streams synchronized to associated clock streams at the NGT.

Tvice.

cient accuracy to permit the TDRS system to establish and maintain acquisition. This can be accomplished in two ways:

(1) The user can provide the orbital elements in a NASA format to GSFC to meet TDRSS operational requirements.

(2) The user shall insure that a sufficient quantity of tracking data is received at GSFC to permit the determination of the user satellite orbital elements. The charges for this service will be determined by using the onorbit service rates.

(a) Initial requests for TDRSS service from non-U.S. Government users should be addressed to NASA Headquarters, Code Ox, Space Network Division, Washington, DC 20546. Upon review and preliminary acceptance of the service requirements by NASA Headquarters, the appropriate areas of GSFC will be assigned to the project to produce the detailed requirements, plans and documentation necessary for support of the mission. Changes to user requirements shall be made as far in advance as possible and shall be submitted in writing to both NASA Headquarters, Code Ox, Space Network Division, and GSFC, Code 501, Greenbelt, MD 20771.

(b) Acceptance of user requests for TDRSS service is the sole prerogative of NASA. Although TDRSS represents a significant increase to current support capabilities, service capacity is finite, and service will be provided in accordance with operational priorities established by NASA. Request for services within priority groups shall be negotiated with non-NASA users on a first come, first service basis for inclusion into the TDRSS mission model. (48 FR 9845, Mar. 9, 1983, as amended at 56 FR 28049, June 19, 1991)

8 1215.107 User data security and frequen

cy authorizations. (a) User data security is not provided by the TDRSS. Responsibility for data security resides solely with the user Users desiring data safeguards shall provide and operate, external to the TDRSS, the necessary equipment or systems to accomplish data security. Any such user provisions must be compatible with data flow through TDRSS and not interfere with other users.

(b) All radio frequency authorizations associated with operations pursuant to this directive are the responsibility of the user. If appropriate, authority(ies) must be obtained from the Federal Communications Commission (FCC) for operations consistent with U.S. footnote 303 of the National Table of Frequency Allocations, FCC Rules and Regulations, at 47 CFR 2.106. (56 FR 28049, June 19, 1991) 8 1215.108 Defining user service require

ments. Potential users should become familiar with TDRSS capabilities and constraints, which are detailed in the TDRSS User's Guide (GSFC document, STDN No. 101.2), as early as possible. This action allows the user to evaluate the trade-offs available among various TDRSS services, spacecraft design, operations planning, and other significant mission parameters. When these user evaluations have been completed, and the user desires to use TDRSS, the user should initiate a request for TDRSS service.

8 1215.109 Scheduling user service.

(a) User service shall be scheduled only by NASA. Scheduling refers to that activity occurring after the user has been accepted and placed in the TDRSS mission model as specified in 8 1215.108(b). See Appendix C for a description of a typical user activity timeline.

(b) Schedule conflict will be resolved in general by application of principles of priority to user service requirements. Services shall be provided either as normally scheduled service or as emergency/disruptive update service. Priorities will be different for emergency/disruptive updates than for normal services.

(1) Normally scheduled service is service which is planned and ordered under normal operational conditions and is subject to schedule conflict resolution under normal service priorities. Priorities are established by the NASA Administrator or his/her desig.

[blocks in formation]

nee. Requests for normally scheduled quests which are received less than 45 service must be received by the sched- minutes prior to the requested sched. ulers at the GSFC Network Controlule support time will be considered a Center (NCC) no later than 45 min. disruptive update. utes prior to requested support time. (ii) User initiated schedule requests

(2) Normal scheduling principles of which are received more than 45 minpriority are generally ordered as fol utes and less than 12 hours prior to lows beginning with the highest priori- the scheduled support period will be ty:

acted upon as a routine input provided (i) Launch, reentry, landing of the

other users are unaffected. If other STS Shuttle, or other NASA launches.

users are affected, the scheduling (ii) NASA payloads/spacecraft.

input will be considered a disruptive (iii) Other payloads/spacecraft of in update and the appropriate charge terest to the United States.

factor will be applied. (iv) Other payloads/spacecraft

(iii) The Network Control Center launched by a NASA launch vehicle. (NCC) at GSFC reserves the sole right (v) Other payloads/spacecraft.

to schedule, reschedule or cancel (vi) Support of other launches.

TDRSS service. Schedule changes (3) Exceptions to these priorities

brought about through no fault of the may be determined on a case-by-case

user are not charged the factor for a basis with the NASA Administrator or

disruptive update. his/her designee as the priorities

(7) While the priority listing remains stated in paragraph (b)(2) of this sac

the general guide for establishing suption are indicative of general rather

port availability, the NASA schedulers than specific cases.

will exercise judgment and endeavor (4) Emergency service conditions are

to see that lower priority users are not those requiring rapid response to

excluded from a substantial portion of changing user service requirements.

their contracted-for service due to the Emergency service may be instituted under the following conditions:

requirements of higher priority users.

(8) When (i) Circumstances which pose a

a user contracts for

TDRSS service for an “operational threat to the security of the United States.

satellite" which interfaces with a sig(ii) Circumstances which threaten

nificant number of national and world

wide users on a regularly scheduled human life. (iii) Circumstances which threaten

basis as opposed to a "research and deuser mission loss.

velopment satellite," NASA will place

special emphasis on the operational (iv) Other circumstances of such a nature which make it necessary to pre

requirement when planning schedules. empt normally scheduled services.

This should reduce the probability of (5) At times, emergency service re

losing perishable operational data quirements will override normal sched

such as meteorological, climate, or ule priority. Under emergency service

earth resources information. conditions, disruptions to schedule

(c) General user service requireservice will occur. As a consequence,

ments, which will be used for prelimiusers requiring emergency service

nary planning and mission modeling, shall be charged for emergency service

should include as a minimum, the folat rate factors set forth in Appendix

lowing;

(1) Date of service initiation. (6) Disruptive updates are scheduled (2) Expected date of service terminaupdates which, by virtue of priorities, tion. cause previously scheduled user sery (3) The type of TDRSS services deices to be rescheduled or deleted or are sired [e.g., multiple access, tracking, requested by the user less than 45 etc.). minutes prior to the scheduled sup (4) The frequency and duration of port period.

each service, including orbital position (i) Disruptive updates will be or time constraints on service delivery charged at the same rates as emergen- from a given spacecraft where approcy service. User initiated schedule re- priate.

[ocr errors]
« PreviousContinue »