plications should be directed, the opening and closing dates for applications, 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 response 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 psychological examinations to minimize the possibility of hazard to persons or missions.

(4) Adaptability to living and working in space.

(5) Willingness to enter into an agreement with NASA covering preflight, flight, and post-flight activities, with individual rights and responsibilities 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

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 requirements.

1215.109 Scheduling user service.

1215.110 User cancellation of all services. 1215.111 User postponement of service. 1215.112 User/NASA contractual arrangement.

1215.113 User charges. 1215.114

Service rates. 1215.115 Payment and billing. APPENDIX A TO PART 1215-ESTIMATED SERVICE RATES IN 1992 DOLLARS FOR TDRSS STANDARD SERVICES (BASED ON NASA EsCALATION ESTIMATE) APPENDIX B TO PART 1215-FACTORS AFFECTING STANDARD CHARGES

The TDRSS represents a major investment by the U.S. Government with the primary goal of providing improved tracking and data acquisition services to spacecraft in low earth orbit or to mobile terrestrial users such as aircraft or balloons. It is the objective of NASA to operate as efficiently as possible with the TDRSS. This is to the mutual benefit of all users. Such user consideration will permit NASA and non-NASA service to be delivered without compromising the mission objectives of any individual user. To encourage users toward achieving efficient TDRSS usage, this reimbursement policy has been established to purposely influence users to operate with TDRSS in the most efficient and orderly manner possible. Additionally, the reimbursement policy is designed to comply with the Bureau of the Budget Circular A-25 on User Charges, dated September 23, 1959, which requires that a reasonable charge should be made to each identifiable recipient for a measurable unit or amount of Government service or property from which a special benefit is derived.

[56 FR 28048, June 19, 1991]

81215.101 Scope.

This Subpart sets forth the policy governing TDRSS services provided to non-U.S. government users and the reimbursement for rendering such services. It excludes TDRSS services provided as standard or optional services to Space Transportation System (STS) users under existing policy for Shuttle and Spacelab (14 CFR subparts 1214.1, 1214.2, and 1214.8); i.e., user command and telemetry support, which utilizes and is a part of the Shuttle or Space

lab communications system, is a Shuttle/Spacelab service. Cooperative missions are also not under the purview of this Subpart. The arrangements for TDRSS services for cooperative missions will be covered in a Memorandum of Understanding (MOU), as a consequence of negotiations between NASA and the other concerned party. Any MOU which includes provision for any TDRSS service will require signatory concurrence by the Associate Administrator for Space Operations prior to dedicating Office of Space Operations resources for support of a cooperative mission.

[56 FR 28048, June 19, 1991]

(a) User. Any non-U.S. Government representative or entity who contracts with NASA to use TDRSS services.

(b) TDRSS. The Tracking and Data Relay Satellite System including Tracking and Data Relay Satellites (TDRS), the White Sands Ground Terminal (WSGT), and the necessary TDRSS operational areas, interface devices and NASA communication circuits to unify the above into a functioning system. It specifically excludes the user ground system/TDRSS interface.

(c) Bit stream. The digital electronic signals acquired by TDRSS from the user craft or the user generated input commands for transmission to the user craft.

(d) Flexible support. Support requests which permit NASA, at its option, to schedule service at any time during the period of a single orbit of the user mission. Missions requiring multiple support periods during a single orbit may be classified as constrained support.

(e) Constrained support. Support requests which specify the exact times NASA is to provide service, or conditions of support which can be translated into exact times for service, such as sub-satellite positions, apogee/perigee position, etc., for which support is needed.

(f) Scheduling service period. One scheduled contact utilizing a single TDRS whereby the user by requesting 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 orbital 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.

§ 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]

§ 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.

(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]

§ 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 payloads, 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

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.

81215.107 User data security and frequency 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]

81215.108 Defining user service requirements.

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.

(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]

§ 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 § 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

311-046 0-92-6

nee. Requests for normally scheduled service must be received by the schedulers at the GSFC Network Control Center (NCC) no later than 45 minutes prior to requested support time.

(2) Normal scheduling principles of priority are generally ordered as follows beginning with the highest priority:

(i) Launch, reentry, landing of the STS Shuttle, or other NASA launches. (ii) NASA payloads/spacecraft. (iii) Other payloads/spacecraft of interest to the United States.

(iv) Other payloads/spacecraft launched by a NASA launch vehicle. (v) Other payloads/spacecraft. (vi) Support of other launches. (3) Exceptions to these priorities may be determined on a case-by-case basis with the NASA Administrator or his/her designee as the priorities stated in paragraph (b)(2) of this seCtion are indicative of general rather than specific cases.

(4) Emergency service conditions are those requiring rapid response to changing user service requirements. Emergency service may be instituted under the following conditions:

a

(i) Circumstances which pose threat to the security of the United States.

(ii) Circumstances which threaten human life.

(iii) Circumstances which threaten user mission loss.

(iv) Other circumstances of such a nature which make it necessary to preempt normally scheduled services.

(5) At times, emergency service requirements will override normal schedule priority. Under emergency service conditions, disruptions to schedule service will occur. As a consequence, users requiring emergency service shall be charged for emergency service at rate factors set forth in Appendix B.

(6) Disruptive updates are scheduled updates which, by virtue of priorities, cause previously scheduled user services to be rescheduled or deleted or are requested by the user less than 45 minutes prior to the scheduled support period.

(i) Disruptive updates will be charged at the same rates as emergency service. User initiated schedule re

quests which are received less than 45 minutes prior to the requested schedule support time will be considered a disruptive update.

(ii) User initiated schedule requests which are received more than 45 minutes and less than 12 hours prior to the scheduled support period will be acted upon as a routine input provided other users are unaffected. If other users are affected, the scheduling input will be considered a disruptive update and the appropriate charge factor will be applied.

(iii) The Network Control Center (NCC) at GSFC reserves the sole right to schedule, reschedule or cancel TDRSS service. Schedule changes brought about through no fault of the user are not charged the factor for a disruptive update.

(7) While the priority listing remains the general guide for establishing support availability, the NASA schedulers will exercise judgment and endeavor to see that lower priority users are not excluded from a substantial portion of their contracted-for service due to the requirements of higher priority users.

(8) When a user contracts for TDRSS service for an "operational satellite" which interfaces with a significant number of national and worldwide users on a regularly scheduled basis as opposed to a "research and development satellite," NASA will place special emphasis on the operational requirement when planning schedules. This should reduce the probability of losing perishable operational data such as meteorological, climate, or earth resources information.

(c) General user service requirements, which will be used for preliminary planning and mission modeling, should include as a minimum, the following;

(1) Date of service initiation.

(2) Expected date of service termination.

(3) The type of TDRSS services desired [e.g., multiple access, tracking, etc.].

(4) The frequency and duration of each service, including orbital position or time constraints on service delivery from a given spacecraft where appropriate.