cj /I 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

• SPECIAL HANDLINS 

SAFSL EXHIBIT 2X007 

o 5- 

Copy 

Pages Z; 

ti 

MOL SYSTEM ENGINEERING't, 

FOR THE 

MANNED ORBITING LABORATORY PROGRAM —'-... 

PROPOSED 

DORIAN 

PART II 

19 April 1968 

Revised 

6 May 1968 

DEPARTMENT OF THE AIR FORCE 

MANNED ORBITING LABORATORY, SYSTEMS PROGRAM OFFICE (USAF) 

AF UNIT POST OFFICE 

LOS ANGELES, CALIFORNIA 90045 

:T SPECIAL HANDLING 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLING 

TABLE OF CONTENTS 

PART II - IMPLEMENTATION 

SECTION PAGE 

1.0 Introduction 1 

2.0 Approach 1 

3.0 Development of Technical Documentation For The 

MOL Program 1 

3.1 MOL System Functional Analysis Expansion 2 

3.1.1 Function 1.0 - Evaluate MOL System 4 

3.1.2 Function 2.0 - Perform Retrieval Operations 12 

3.1.3 Function 3.0 - Perform Deorbit Operations 21 

3.1.4 Function 4.0 - Perform On-Orbit Objectives 30 

3.1.5 Function 5.0 - Perform Early Orbit Operations 38 

3.1.6 Function 6.0 - Perform Boost 46 

3.1.7 Function 7.0 - Perform Installation, Checkout;-. 

Prelaunch Operations and Launch 56 

3.1.8 Function 8.0 - Test, Accept and Deliver MOL System 68 

3.1.9 Function 9.0 - Perform Training and Perform 

Simulation 77 

3.1.10 Function 10.0 - (Combined with Function 9.0) 82 

3.1.11 Function 11.0 - Maintain System 83 

3.1.12 Function 12.0 - Perform Mission Control 91 

3.1.13 Function 13.0 - Perform Abort Operations 99 

3.2 Schematic Diagrams 108 

3.2.1 MOL System Top Level Schematic Diagram 108 

3.2.2 Segment Schematic Diagrams 111 

3.2.3 Lower Level Schematic Diagrams 111 

3.2.4 Responsibilities 111 

3.3 Submittal of Data 113 

3.3.1 Collation of Data 113 

3.3.2 Processing of Data 113 

3.3.3 Change Control of Data 117 

3.3.4 ECP Data 117 

i 

- 
,S R _E I SPECIAL I-IANDLI:;G 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

TABLE OF CONTENTS 

PART II 

(Continued) 

ILLUSTRATIONS 

FIGURE 

1 Interface Traceability 

lA Top Level Schematic Block Diagram 

2 Change Log 

3 Change Page Index 

4 Function Index 

Addendum A INTERFACE CODING 

PAGE 

109 

110 

114 

115 

116 

SPECIAL IIANDLIal 

- ■•••• 

■ 

ii 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 L -1 SPECIAL HANDLL.G 

• PART II 

IMPLEMENTATION 

1.0 INTRODUCTION 

The basic approach for accomplishing the MOL System Engineering effort and 

preparing the related System Technical Documentation is defined in Part I of 

this Exhibit. Part I is an overt Management Guidance Document and is not 

contractually binding except as noted herein. The covert Part II of this 

Exhibit, together with the covert Addendum A to the covert Part II, are the 

contractual implementation documents. The covert Part II shall be used as 

the governing contractual document for the DORIAN Program. 

The sections of the overt Part I to the Exhibit referenced in the covert 

Part II become contractual when so referenced. 

2.0 APPROACH 

The task, segment and data assignments defined in Part II of this Exhibit 

are based on the requirements defined in the System Performance and Design 

Requirements (SP/DR) Specifications SS-MOL-1A, dated 1 September 1966, as 

updated in the proposed SS-MOL-1B, dated 1 February 1968. The assignments 

defined in Part II will be updated concurrently with future changes to the SP/DR. 

Overall schedules for development and preparation of the data and tasks 

required in Part II of this Exhibit will be established by the MOL Program 

Office in coordination with the Associate and MPI Contractors. Basic individual top function development schedules will be established by the appropriate Function Integrators in coordination with the contributing contractors 

to those top functions. The top function development schedules shall be 

compatible with the overall schedule. 

3.0 DEVELOPMENT OF TECHNICAL DOCUMENTATION FOR THE MOL PROGRAM 

The System Technical Documentation (STD) initially developed in the Contract 

Definition Phase (CDP) shall be expanded and maintained in a current status 

by the associate contractors in accordance with the instructions contained 

in Part II of this Exhibit. 

( 

SPECIAL 1-IANDLIG 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL HANDLING 

The System Technical Documentation (STD) prepared for the MOL Program shall 

fully describe the DORIAN and non-DORIAN requirements. The STD shall initially 

be prepared as a single covert package of DORIAN and non-DORIAN requirements. 

An overt STD data package shall be prepared from this covert package. DORIAN 

STD which must, because of interface requirements, be covered in the nonDORIAN STD shall have suitably altered versions prepared which remove the 

DORIAN classification but retain the interface requirements. DORIAN STD which 

has no interface requirements with non-DORIAN STD shall not be converted. 

Suitable cover functions, function descriptions, etc., shall be used for 

conversion purposes. 

STD prepared by non-DORIAN participants shall be integrated with the DORIAN STD 

to form the complete MOL Baseline by the DORIAN portion Function Integrator 

for each. Function. 

Final judgment as to the adequacy and validity of the analysis and data 

generated in accordance with this Exhibit is the responsibility of the MOL 

Program Office. The MOL Program Office, in its role of Overall System 

Integrator (OSI), will be responsible for timely resolution of conflicts 

and adjustments to contracts arising out of the performance of tasks defined 

in this Exhibit. 

All transmittals of STD data specified in this Exhibit shall be based on a 

package concept of related Functional Flow Block Diagram(s)[FFBD's], 

Requirement Allocation Sheet(s)[RAS's], Timeline(s)[TL's], Schematic Block 

Diagram(s)[SBD!s] and, where appropriate, related trade studies. Transmittals 

of one STD element shall be accompanied by the other related data elements, 

as noted, to insure that the recipient receives sufficient information to 

accomplish his task. 

3.1 MOL SYSTEM FUNCTIONAL ANALYSIS EXPANSION 

The MOL Associate Contractor shall perform the functional analysis and develop 

and prepare the STD in accordance with the direction contained in this Exhibit. 

The MOL Program Office and Government Agencies will assist and participate in 

this effort as noted. 

or,p i i m G 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 -S-E-eitClt SPECIAL HP1DL1::G 

Requirements previously specified in existing contractual documents available 

at the time of initial preparation of the Requirements Allocation Sheets may 

be incorporated by reference to the appropriate paragraphs of those contractual 

documents in lieu of expanded narrative detail. However, where this approach 

is used, the actual words of the requirements so referenced shall be made 

available furnished on request to and maintained in a current status for 

incorporation into the data packages utilized by each program participant who 

would normally have that portion of the STD. 

Sections 3.1.1 through 3.1.13 of the covert Part II of this Exhibit define 

and establish the specific tasks to be accomplished and data to be prepared 

for each top system function. The contractor roles and responsibilities 

delineated herein supersede those prescribed in Section 3.1 of the overt Part I 

of this Exhibit. 

F s,rciA p 

:3 
- NRO APPROVED FOR --S-E-6-11-Ef- SPECIAL HANDLING 

RELEASE 1 JULY 2015 

3.1.1 'Function 1.0 "Evaluate MOL System" 

3.1.1.1 Function Description 

The objective of this function is to provide the basis for the evaluation of 

the performance of the various elements comprising the MOL System and of the 

System as a whole. The evaluation covers a period beginning at the arrival 

of AGE at the launch site and ends with mission termination. This evaluation 

shall facilitate: (1) management cognizance of important milestones, both 

during and following each flight, which will enable decisions to be made on 

a timely basis in regard to flight program changes; (2) detection of 

deficiencies so that required corrective actions may be implemented; 

(3) determination of additions or changes which could improve future capabilities for manned or unmanned operations of military significance; (4) evaluation of segment performance; (5) comparison of mission effectiveness between 

the KA and KB modes of operation. 

Mission termination for this function is defined to occur at the time of 

delivery of the flight items (e.g., data, Flight Crew and Gemini B or DRV's) 

to predetermined locations for initiation of post-flight analysis and/or 

positive equipment disposal if recovery is not feasible. 

3.1.1.2 Special Considerations 

Real-time or near real-time on-orbit evaluations of immediate changes to 

mission operations are not included in this function. (Such evaluation 

requirements will be developed as a part of Function 12.0 "Perform Mission 

Control".) However, requirements for pre-termination evaluation reports, 

necessary for overall management cognizance of the mission and possible 

longer term redirection of the flight program, shall be developed as a 

part of this Function. 

3.1.1.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description for 

system evaluation. Detailed discussions for coordination of operational 

plans and technical interchanges for design definition of equipment required, 

shall be based on the STD to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent with the Function 1.0 STD include the following: 

SECPST SPECIAI HANDLING 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 E SECIT 1_ "►"1Y I"G 4 L., 

NOTE: .The planning and reouirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

ve t. 

rr 

) D S"ECIMP"E' . 

r- 
NRO APPROVED FOR .G. R L 1.. S. HU L 1.0 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS: 

o VIP's for System Requirement Change A016 (C-12) 

...•••■• 

• 4 ECP's for CEI's A017 (C-13) 

o ECP's After FACT A018 (C-19) 

O Spec. Maintenance Document A019 (C-11) 

o System/DeSign T S Report A041 (S-54) 

O Cont. Seg. Post Flight Test Report A054 ([U] T-604) 

MARTIN ITEMS: 

o Spec. Maint. Documents C2 & C19 (C-11/M) 

o ECP's for System Requirement Change C3 & C4 (C-12) 

• ECP's for CEI's Pt. I C5 (C-13/M) 

o ECP's for CEI's Pt. II C6 (C-19M) 

• Specification Maintenance Document C19,(C-11/M) 

o Launch Evaluation Report T6, T7 & T8 (T-126/M) 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

GENERAL ELECTRIC ITEMS: 

o SCN B044 (C-11) 

o ECP's for CEI's B046 (C-13) 

o ECP's for System Requirement Change B047 (C-12) 

o ECP's after FACI B048 (C-19) 

o System/Design T S Reports B079 (S-54) 

o CEI Evaluation/Qualification Test Plan B090-B094 [(U)T-405] 

o Flight Operations Support Study Report B ill [(U)T-4102] 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o Contractor Post-Flight Segment 

MCDONNELL ITEMS: 

o Manned Recovery Requirement Document 18T, (U), T-(221-207) 

o Program Requirement Document - 19T (U) T-(116) 

o Operations Support Evaluation Plan - 205, (U), S-211 

o Post Flight Evaluation Plan - 285, (U) (S-222) 

0 , E s,! it C. 1 11 1111)L1110 

• 
t.% • 

FC:lr' 1_ Li' 

100 NRO APPROVED FOR 

RELEASE 1 JULY 2015 

MCDONNELL ITEMS: (Continued) 

o Orbital Requirement Document - 17T, (U) (T-221 [T3]) (Manned) 

o ECP's for CEI's - 16C (C-13) 

• ECP's General (After FACI) - 18C (C-19) 

o ECP's for System Requirement - 27C (C-12) 

o S/C Instru. System Report - 135 (U) (S-(205) 

o Instru. Books A & B 145 & 155 (U) (S-(206), (207) 

o Specification Maintenance Document - 15C, (U) (C-11) 

o Data Acquisition & Handling Plan 

o Quick Look Ascent & Orbit Report 

o Quick Look Post Operations Report 

o Launch Evaluation Report, (Inputs) 

o Contractor Post-Flight Segment Report 

o Post-Flight Test Procedure 

DOUGLAS ITEMS: 

o Spec. Maintenance Document (CEI's B136 & 137 (C-11) 

o ECP's for System Requirement Chg. B138 (C-12) 

• ECP's for CEI's B139 & 140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

o Interface Document Evaluation B195 (UE-101) 

o System/Design Trade Study Reports 11247 (S-54) 

o ORD Inputs B281 (UT-141) 

o Flight Test Engineering Analysis Report B306 (UT-117) 

o Post Flight Analysis & Evaluation Study B349 (UT-142) 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o Contractor Post-Flight Segment 

o Final Flight Test Engineering Report 

AGENCY ITEvS: 

o Orbital Support Plan (OSP) 

0 1_, 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 4E-C-R-F±, SPECIAL HANDLING 

The STD for Function 1.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents 

listed above and others that may evolve. 

Specific references to contractual requirements documents by paragraph 

number shall be shown in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2; however, Right Hand RAS's and the Left Hand 

RAS paragraph regarding "effectiveness" are not required for 

Function 1.0 since they are not applicable. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Ref. Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.1.4 Task Assignment 

The Function 1.0 integration responsibility is assigned to Douglas MSSD. 

Contributing associate contractors are General Electric, McDonnell Astronautics, 

Martin-Marietta, and Hamilton Standard. Martin-Marietta Corporation shall 

integrate data from United Technology Center, Aerojet General Corporation, 

A-C Electronics Division and Spacecraft Incorporated and shall submit the 

integrated T-IIIM STD to the Function 1.0 Integrator. The MOL Program 

Office will furnish agency information. 

General Electric shall prepare the FFBD's to include both the General Electric 

and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's for their 

functions and coordinate changes desired with General Electric. Eastman 

Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to support the FFBD's 

and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph (a) 

below to integrate the,Eastman iKoqak and General Electric STD. 

L i SPECIAL NANDI 

8 
NRO APPROVED FOR R L T SPECIAL 1-1ANDLI4 

RELEASE 1 JULY 2015 

General'Electric shall perform the tasks noted in paragraph (b) below for 

both the General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

S E r-DITT spEcIAL HANot_R;r:1 

8A 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 S E CR E T SPECIAL HANDLII1G 

Eastman Kodak shall perform the tasks noted in paragraph (b) below in 

preparing and submitting STD to General Electric except for preparation of 

FFBD's. 

a. The Function 1.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government 

agency participation in accordance with the master schedule 

issued by the OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. 

3. Identify the required timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or 

definitions reflected in the STD for Function 1.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns on 

RAS's per paragraph 3.1.1.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and to OSI. 

8. Respond to requests for clarification or revision of Function 

1.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, and SBD's in format 

specified in Part I of this Exhibit and submit on 11x17 inch 

vellums to the Function Integrator and the OSI. Flow diagram 

expansion and their attendant RAS and Timeline Sheet shall be 

submitted as a package for integration. 

9 0 4. SLECIAL HANDLII 4b 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL HANDLING 

•2. Respond to requests for clarification or revision of the contributed data if discrepancies are identified during integration. 

3. Each of the associate contractors involved in the post-flight 

analysis shall utilize the requirements established in the STD 

for this function in their respective data reduction and postflight analysis plans. 

4. Each of the associates will determine the ground rules and the 

criteria for evaluation and the evaluation effort for his segment 

as a part of his participation in the analysis of requirements 

for the assigned functions derived from the overall system function 

breakdown described in Section 3.1 of Part I of this Exhibit. These 

vill include: the types and quantities of data items to be recorded, 

transmitted by telemetry, retrieved, measured prior to launch or 

after recovery; priority and evaluation criteria; and the equipment, personnel, and facility requirements for processing and 

reducing the data. Tradeoff studies shall be made as necessary 

to ascertain the data requirements. 

c. MOL Program Integration Contractor (Douglas) as System Level 

Integrator of the STD shall: 

1. Review FUnction 1.0 STD to identify possible inconsistencies or 

incompatibilities in functional descriptions and timing, defined 

interfaces and stated requirements, using as a guide the functional cross-references incorporated in the STD. Compare the 

interfaces identified in the functional schematics with the 

interface requirements defined in the RAS's to verify adequacy 

of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

QncriKi up,mm 

10 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

R ET SPECIAL HANDLING 

d., The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of system evaluation requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

S-Eef-, Rt7J-r

SPFCIAL HANDLING. 

11 
NRO APPROVED FOR T SPECIAL HANDLING 

RELEASE 1 JULY 2015 

3.1.2 Function 2.0, "Perform Retrieval Operations" 

3.1.2.1 Function Description 

These functions start with the selection and disposition of the recovery 

forces. Necessary reassignments are made through Mission Control. 

With respect to the Flight Crew and the Reentry Module, these functions 

start at physical contact by the retrieval forces with the Flight Crew or 

the Reentry Module. With respect to the Data Reentry Vehicles (DRV's), 

these functions start with deployment of the recovery means prior to ejection 

of the first DRV from the Support Module. 

These functions include normal retrieval from planned recovery areas or from 

contingency recovery areas (and, as a branch of this function, emergency 

retrieval operations). For the KA Mode, the function terminates upon 

delivery of the flight items (viz., data, Flight Crew, and spacecraft) to 

predetermined locations for initiation of post-flight analysis; or positive 

equipment disposal if recovery is not feasible. For the KB Mode, the function 

terminates upon delivery of the data from the last DRV to predetermined 

locations for analysis and evaluation. For both the KA and KB modes, verification of disposal of the remaining vehicle elements in orbit shall be 

included as a part of this function. 

3.1.2.2 Special Considerations 

Definition of the specific requirements for retrieval equipment, personnel 

operations and capabilities, and for recovery force composition and the 

analysis of time requirements, shall be correlated with the analysis and 

documentation of Mission Control activities in support of retrieval (Ref. 

Function 12.0) and with the AVE/AAE/crew requirements and constraints 

developed under Functions 3.0, 4.0, and 13.0. 

3.1.2.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description 

of retrieval operations. Detail discussions for coordination of operational 

plans and technical interchanges for design definition of equipment required 

shall be based on this STD to the extent practicable. 

i7 

( i< SPECIAL HANDLING 

12. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 -S-E-C-R-Ei- SPECIAL HAiiDLING 

Planning and requirements documents which must be based on and/or be consistent with the Function 2.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the 

non-DORIAN versions. This list also applies to their DORIAN 

counterparts, as applicable. DORIAN-only documents will be added 

as they are identified. 

cro ;f -r s oc..ko

.)Li rri L'A"D' l ''G PJ 

.13 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECICILING • - i,.• 2.0 

HAMILTOU STANDARD ITEMS: 

o ,ECP's for System Requirement Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A018 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o Flight Crew Handbook (LV/Gemini B) A028 [(U) H-602] 

o Flight Directors Handbook A029 [(U) H-604] 

o Tech. Pubs. - Recovery Handbook A030 [(U) H-605] 

o MRRD A032 [(U) L-601] 

o Flight Operations Crew Pers. Training Plan A038 [(U) Q-601] 

o Flight Crew Safety Plan A040 [(U) 8-600] 

o System/Design T S Report A041 (S-54) 

o PSA Task Analysis A045 [(U) S-605] 

o PRD Inputs A053 [(U) T-603] 

MARTIN ITEMS: 

o PRD Input - Chg. T9 (T-21/M) 

GENERAL ELECTRIC ITEMS: 

o SCN B044 (C-11) 

o ECP's for CEI's B046 (C-13) 

o ECP's for System Requirement Chg. B047 (C-12) 

o ECP's After FACI B048 (C-19) 

o Failure Mode & Effects Analysis B068 [(U) R-408] 

o Relib. Demonstration Study B070 [(U) R-410] 

o Hazard Analysis B075 [(U) S-404] 

o System/Design T S Reports B079 (S-54) 

o Flight Operations Support Study Report Bill [(U) T-410] 

MCDONNELL 1TFM: 

o Manned Recovery Requirement DocuMent - 18T, (U), (T-(221 - 207) 

o Program Requirement ent - 19T, (U) (T- (116) 

o GB Flight Effectiveness Model Report - 7R, Cu) (R-(207) 

o ECP's for CEI's - 16C (C-13) 

r • !, • ,`NI SI.- , 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SDEC1111-1Arf).- a 

2.0 

MCDONNELL ITEMS: (Continued) 

o ,Manned Flight Vehicle Time Line - 265, (U) (S-221) 

o ECP's General (After FACI) 18C (C-19) 

o Failure Mode & Effect. Anal. - 5R, (U) (R-(205) 

o ECP's for Sys. Requirement - 27C (C-12) 

o S/C Instru. Sys. Rpt. - 135, (U) (S-(205) 

o Single Point Failure Analysis - 4R [(U) R-(204) 

o Load Anal. - Elect. Eqpt. - 125, [(U) - S-(204) 

o Instru. Books A & B - 145 & 155 (U) (S-(206, (207) 

o Effectiveness Prog. Status Report - 1R (U) (R-(201) 

o Specification Maint. Doc. - 15C, (U) (C-11) 

o Interface Specifications - 28C (U) (C-209) 

o Interface Maint. Document - 22C [(U) C-(205)] 

o Update Comm. System Technical Baseline 

o Task Analysis Data (Crew Training) (U) S-(219) 

o Flight Dir, HB 

o Flight Crew HB (GB) 

o Flight Data File 

o Recovery HB - Manned 

o System Test Objectives (STO) 

o Quick Look Post Operations Report 

o Elect. System Schematics (ESS) 

o Structural Design Loads 11S [(U) ST(203)] 

o Flight Operations Crew Pers. Training Plan 

o Flight Crew Safety Plan 

o Flight Term. System (FTS) Report 

o Radio Freq. Allocation (RFA) Request 

o GBQ Recovery Requirements Document 

DOUGLAS ITINS: 

o Spec. Maint. Document (CEI's) B136 & 137 (C-11) 

o ECP's for Sys. Req. Chg. E138 (C-12) 

o ECP's for CF I's B139 &B11:0 (C-13) 

o ECP's - Post FACT B1111 (C-19) 

o Interface Specs. (IFS) B142 (UC-101) 

o Interface Cont. Dwg. (:BCD) B143 (UC-102) 

Di Lyt L.s., ; ■ 11— f./11• 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 L I SPECIAL HANDLING 

2.0 

DOUGLAS ITEMS: (Continued) 

o *IFS/ICD Maint. Doe. B144 (UC-103) 

o Interface Doc. Evaluation 3195 (UE-101) 41, 

o System/Design Trade Study Reports P247 (S-54) 

o Mission Status Summary B277 (US-121) 

o PRD Inputs B305 (UT-116) 

o Quick Look Post-Operations Report 

AGENCY ITEMS: 

o Program Support Plan (PSP) 

o Recovery Support Plan (RSP) 

o Manned Recovery Support Plan (MRSP) 

o Operations Requirement (OR) Pt. I, Pt. II 

o System Test Objectives 

o Operations Directive 

o Flight Termination System IFRS Report 

o Recovery Safety Plan 

S

r r; nr,rni n fnIn 

L L JI'LuiAL 

1 4; 
NROAPPROVEDFOR SECREI SPEC.V,1_ HANDLLG 

The STIO for Function 2.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. When functions are expanded 

to amplify the definition of operational sequences and interfaces beyond 

this level of detail, the Left-Hand RAS shall be limited to the function 

description and interface requirement. Emphasis shall be placed on the 

definition of operational interfaces between the Recovery Forces, Mission 

Control, and the items to be retrieved. Specific references to contractual 

requirements documents by paragraph number shall be shown in the appropriate 

RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in paragraph 3.2.2 of Part I. (Note: 

LH RAS's for procedural functions may be limited to a function 

description and interface requirements, as appropriate.) 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5 or comparable contractor Design Note 

or Technical Note format. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.2.4 Task Assignments 

The Function Integration for Function 2.0 shall be performed by the 

McDonnell Astronautics Company. Contributing associate contractors are 

Douglas MSSD, General Electric, and Hamilton Standard. The MOL Program 

will furnish government agency information. 

The Function Integration responsibility assigned to McDonnell Astronautics 

Company above shall be for non-DORIAN KA and KB mode requirements only. 

For this case, Eastman Kodak generated STD shall be integrated with 

General Electric STD by General Electric. The resulting integrated STD 

u „ 0, 

17 

RELEASE 1 JULY 2015 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRET SPECIAL HANDLING 

shall .be suitably altered by General Electric to remove its DORIAN 

classification while still retaining interfacing requirements before 

submission to McDonnell Astronautics. 

MCASTRO shall prepare flow diagrams and RAS's for Function 2.0, including 

specific requirements related to the Gemini B, crew, and DRC retrieval. 

The Function Integration responsibility for the DORIAN KA and KB mode 

portions of Function 2.0 is assigned to Douglas MSSD. Contributing 

associate contractors are General Electric and Eastman Kodak. As Function 

Integrator, Douglas shall perform the tasks noted in paragraph (a) below 

for the Function 2.0 DORIAN requirements. 

For both the KA and KB mode, the following shall apply: 

General Electric shall prepare the FFBD's to include both the General Electric 

and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's for their 

functions and coordinate changes desired with General Electric. Eastman 

Kodak shall prepare RAS's, TLS's, SBD's, and TSB's to support the FFBD's and 

submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph "a" 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph "b" below for 

both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraphs b.1 and b.2 below 

in preparing and submitting STD to General Electric except for preparation 

of FFBD's. 

a. The Function 2.0 Integrator shall: 

1. Prepare, coordinate, and issue schedules for contractor/ 

government agency participation in accordance with the master 

schedule issued by the OSI. 

•E-) Si ti i■ 

18 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 Ittii+ SPECIAL HANDLING 

. 2. Establish contractor assignments for review, comment and 

expansion of flow diagrams and RAS's. This shall include 

coordination of contractor definitions of any Laboratory 

Vehicle retrieval requirements. 

3. Identify the required timelines and make assignments for 

preparation 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans or 

definitions reflected in the STD for Function 2.0. The 

Function Integrator shall inform the affected organizations 

of identified problems, request revised inputs and, if 

necessary, call a meeting of those involved to achieve a 

resolution. 

5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.2.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

furnishing it for system level integration to the MPI 

Contractor and the OSI. 

8. Clarify or revise Function 2.0 STD if discrepancies are 

identified during system level integration. Coordinate 

as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, SBD's and TSR's in 

format specified in Part I of this Exhibit and submit on 

11 X 17 inch vellum to the Function Integrator and the OSI. 

Flow diagram expansion and their attendant RAS and Timeline 

Sheet shal;,be submi-pted ascp,:oackage, pri1.*egration. 

, 0,1 liaAltULti 

19 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL 1-14NOLINC3' 

• 2. Respond to reauests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

3. Douglas, General Electric, and Hamilton Standard shall 

respond to specific requests from the Function Integrator 

for inputs related to DRV or Laboratory Vehicle retrieval/ 

disposal or Pressure Suit Assembly (PSA) in support of planned 

integration, realignment or expansion of Function 2.0 STD. 

4. Douglas and General Electric shall respond to specific requests 

from the Function Integrator for inputs relating to the DRV's 

or to other DORIAN aspects for both the KA and KB modes. 

c. MOL Program Integration Contractor as System Level Integrator 

of the STD. 

1. Review Function 2.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in the STD. 

Compare the retrieval operation related segment interfaces 

identified in the functional schematics with the interface 

requirements defined in the RAS's to verify adequacy of interface 

definition. 

2. Inform the MOL Program Office of the results of the above 

activities. 

20 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

r T orq-n=L"^IDLI'' ` 

L C. i is. 

3.1.3 'Function 3.0 "Perform Deorhit Oneretions" 

3.1.3.1 Function Description 

This portion of the analysis shall identify requirements for the return to 

earth of the Gemini B, crew, and data, and shall also include requirements 

relating to disposal of the remaining vehicle elements in orbit. 

In the principal flight modes, these functionsstart with the opening of the 

Gemini B/Laboratory Vehicle tunnel hatch (inclusive) or the LV-EVA hatch in 

the case of extravehicular transfer for final transfer of the crew 

to the Gemini B, and terminate with physical contact by retrieval forces 

with the Reentry Module or Flight Crew. For such flight modes, a branch of 

these functions involves Laboratory Vehicle disposal. Normal, contingency, 

and emergency modes of operation are to be considered in these functions. 

For alternative flight modes, these functions start with the initiation of 

Orbiting Vehicle disposal and terminate upon completion of the disposal 

mode. 

3.1.3.2 Special Considerations 

When contingency and emergency considerations lead to an abort situation, 

the analysis accomplished as a part of this function shall be performed 

only through determination of abort indication requirements (subsequent 

abort requirements shall be developed as a part of Function 13.0 for these 

cases). 

Definition of specific requirements for deorbit equipment, personnel operations 

and capabilities, as well as the analysis of time requirements, shall be 

correlated with the analysis and documentation of Mission Control activities 

in support of deorbit (Reference Function 12.0) and with the AVE/AAE/crew 

requirements and constraints developed under Function 2.0, 4.0, 5.0, and 13.0. 

Requirements relating to deorbit of Data Return Vehicles for the Automatic 

Mode shall be defined in Function 4.0 and correlated With this function. 

Retrieval and/or verification of positive disposal requirements of deorbited 

mission revealing equipment or data will be included in Function 2.0 for normal 

operations or in Function 13.0 for abort operations. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

r".1 

t 

c^rf., 1 ?\ LC 'DU I iG 

3.1.3.5 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description of 

Gemini B and LV deorbit operations. Detailed discussions for coordination of 

operational plans and technical interchanges for design definition of equipment required, shall be based on this STD to the extent practicable, 

Planning and requirements documents which must be based on and/or be 

consistent with the Function 3.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

22 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

LCRL1 SPECIAL 

Hamilton Standard Items; 

0 

0 

0 

0 

0 

0 

0 

0 

0 

0 

GE Items: 

0 

0 0 

0 0 

0 

McDonnell 

0 

0 

0 

0 

0 

0 

0 

ECP's for Sys. Req. Chgs. A016 (C-12) 

ECP's for CEI Specs. A017 (C-13) 

ECP's after FACT A018 (C-19) 

Spec. Maint. Doc. A019 (C-11) 

Flt. Crew Handbook (LV/Gemini B) A028 [(U) H-602] 

Flight Director's Handbook A029 [(U) H-604] 

Maint. Req. Data A031 [(U) L-600] 

Flt. Crew Safety Plan A040 [(U) S-600] 

System/Design T.S. Report A041 (S-54) 

PSA Task Analysis A045 [(U) S-605] 

ECP's for CEI Spec. B046 (C-13) 

ECP's for Sys. Req. Chgs. B047 (C-12) 

ECP's after FACT B048 (C-19) 

Failure Mode & Effects Anal. B068 [(U) R-408] 

Reliab. Demonstration Study B070 [(U) R-410] 

Hazard Anal. B075 [Cu) S-404] 

System/Design T.S. Report B079 (S-54) 

Flt. Opns. Support Study Report B111 [(U) T-410] 

Flt. Crew.Safety Plan 

Quick Look Post Opns. Report. 

Flt. Director's Handbook 

Flt. Crew Handbook (LV) 

a. 

Electr. Magnetic Co Tat. Anal 235 [(U) S-214] 

Manned Recov. Rear.t Doc. 16T [(U)T-221] 

Program Fecint. Doc. 19f [(U) T-116] 

Crew Transfer Test Plan 7T [(U) T-201j 

Structural Qual. Test Plan 2T [(U) T-201] 

Flt. Effect. Model Rnt 7? [(U) 11-207] 

tecr:t. Doc. 171 [(U) T-221] 

'7. Q:".• L • i to 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

sPEcia HA:::ou: 

• .; 

• 

ECP's for CEI Specs. 16C (C-13) 

..•■•••, 

O Manned Flt. Veh. Timeline 26S [(U) S-221] 

O ECP's after FACI 18C (C-19) 

• Failure Mode & Effect. Anal. 5R [(U) R-205] - 

o ECP's for Sys. Req. Chgs. 27C (C-12) 

• Version Descrip. Doc., CPCEI, GBPS 31C [(U) C-214] 

• S/C Instru. Sys. Rpt. 13S [(U) S-205] 

• Single Point Failure Anal. 4R [(U) R-204] 

• Explosive Comp. Tech. Data Sheet 18S [(U) S-209] 

• Load Anal.-Elect. Eqpt. 12S [(U) S-204] 

O Instru. Books A & B 14S and 15S [(U) S-206 & 207] 

O Effectiveness Prog. Status Rpt. 1R [(U) R-201] 

O Spec. Maint. Doc. 15C [(U) C-11] 

• Interface Specs. 28C [(U) C-209] 

• Interface Maint. Doc. 22C [(U) C-205] 

• Aero. Data Book 21S [(U) S-212] 

• Internal Crew Transfer Testing O-G 

O Update Comm. System Tech. Baseline 

O Task Analysis Data (Crew `'raining) [ (U) S-219] _

O Flt. Director Handbook 

• Flt. Crew Handbook (LV & GB) 

• Flt. Data File 

• System Test Objectives 

• Quick Look Post Opns Report 

• Elect. System Schematic 

• Struct. Design Loads 11S [(U) S-203] 

Flt. Crew Safety Plan 

O Radio Frea. Alloc. Request 

Douglas Items: 

o Spec. Maint. Doc. B136 & P137 (C-11) 

o ECP's for Sys. Req. Chgs. B138 (C-12) 

• ECP's for Specs. B139 & B140 (C-I3) 

o ECP's for Post FACI B141 (C-19) 

• Inter.Nce CI)CS. 1142 (UC-101) 

o Interface Cont. Dwz 13143 (UC-102) 

Onr-O! f ! !./, fs.! !" • 

t) If L • -1 ' 11 .,;•..t., I 

f).4 
NRO APPROVED FOR . 

RELEASE 1 JULY 2015 

• 

• 

IFS/ICD Maint. Doc. B144 (UC-103) 

• Config. List B145 (UC-104) 

• Interface Doc. Eval. B195 (UE-101) 

• Elect. Sys. Schematic B197 (UE-103) 

• Training Req. Data (Flt. Crew) B234 (UQ-101) 

• Sys/Design Trade Study Reports B247 (S-54) 

Sys: Safety Plan B259 & B260 (US-101) 

• Stress, Fatigue,- & Dym. Anal. Rpt B262 (US-103) 

• Baseline Flt. Veh. Timeline B266 (US-108) 

• Explosive Comp. Tech. Data Sheet B268 (US-111) 

• Mission Status Summary 3277 (US-121) 

• ORD Inputs B281 (UT-141) 

• Reliab. Crit. Corm. Data Summary B303 (UT-114) 

• Flight Director's Handbook 

• Flight Crew Handbook 

O Flight Crew Handbook, Gemini B Input 

O Command & Opns Handbook Input 

O System Test Objectives 

O Flight Crew Safety Plan 

• Quick Look Post-Operations Report 

• Radio Frequency Allocation Request B335 (RFPI 7-4067) 

Agency Items: 

O Orbital Support Plan 

O Recovery Support Plan 

• Operations Requirements Part I and Part II 

System Test Objectives 

• Operations Directive 

--77-7.17"i747R-EiTt (Nr:1" ‘ r` r ! ' 

.• 

-1 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

The STD for Function 3.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. When functions are expanded 

to amplify the definition of operational sequences and interfaces beyond this 

level of detail, the Left Hand RAS shall be limited to the function description 

and interface requirement. Emphasis shall be placed on the definition of 

operational interfaces of the Gemini B to Crew, DRC's, Laboratory Vehicle, 

Pressure Suit Assembly, Mission Control and recovery forces. Specific 

references to contractual requirements documents by paragraph number shall be 

shown in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2., however, SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in Paragraph 3.2.2 of Part I. (NOTE: 

LH RAS's for procedural functions may be limited to a function 

description and interface requirements, as appropriate.) 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5 or comparable contractor Design Note 

or Technical Note format. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.3.4 Task Assignment 

The Function 3.0 integration responsibility has been assigned to McDonnell 

Astronautics (MCASTRO). Contributing associate contractors are Douglas MSSD, 

General Electric and Hamilton Standard. 

The Function Integration responsibility assigned to McDonnell Astronautics 

Company above shall be for non-DORIAN KA and KB mode requirements only. 

For this case, Eastman Kodak generated STD shall be integrated with General 

Electric STD by General Electric. The resulting integrated STD shall be 

suitably altered by General Electric to remove its DORIAN classification while 

still retaining interfacing requirements before submission to McDonnell 

Astronautics. 

26 
NRO APPROVED FOR ■ SPECIAL FlArDLI"...0' 

RELEASE 1 JULY 2015 

The Function Integration responsibility for the DORIAN KA and KB mode portions 

of Function 3.0 is assigned to Douglas liSSD. Contributing Associate Contractors 

are General Electric and Eastman Kodak. As Function Integrator1 Douglas shall 

perform the tasks noted in paragraph (a) below for the Function 3.0 DORIAN 

requirements. 

For both the KA and KB mode the following shall apply: 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's and TSB's to support the 

FFBD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph (a) 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph (b) below 

for both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph (b) below in 

preparing and submitting STD to General Electric except for preparation 

of FFBD's. 

a. The Function 3.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/ 

government agency participation in accordance with the master 

schedule issued by the OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. This shall include 

coordination of contractor definitions of impact of Gemini B 

separation and deorbit on subsequent deorbit of the Laboratory 

Vehicle. 

3. .Identify the required timelines and make assignments for 

preparation. 

L. 1 g 

'Afr4 1 

i 

ti 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

r

d. SrICI1! 

• 4. Review contributed data and comments received from participants 

to identify incompatibilities in reauirements, plans, or 

definitions reflected in the STD for Function 3.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of these involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.3.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall release copies to participating contractors/agencies concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

8. Respond to requests for clarification or revision of Function 

3.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's and timelines in format specified 

in Part I of this Exhibit and submit on 11x17 inch vellum to 

the Function Integrator and to the OSI. Flow diagram expansion 

and their attendant RAS and Timeline Sheet shall be submitted 

as a package for integration. 

2. Respond to requests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

c. MOL Program Integration Contractor as System Level Integrator 

of the STD shall: 

1. Review Function 3.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in the 

STD. Compare the deorbit interfaces identified in the functional 

SEC, U1:1... ii., L I L T ; ■ U 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 1: SPECIAL 1-1ANDIX:G 

• schematics with the interface requirements defined in the RAS's 

to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of deorbit requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

P r 0r-.7(Ny! r,"1,-)! 

- • 

1)9 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 ECRET SPECIAL HANDLING 

3.1.4 *Function 4.0, "Perform On-Orbit Objectives" 

3.1.4.1 Function Description 

For the principal flight modes, these functions begin at the closing of the 

Gemini B/Laboratory Vehicle tunnel hatch (exclusive) or the LV-EVA hatch in 

the case of extravehicular transfer by the second crewman following 

initial transfer from the Gemini B, and terminate at the opening of this 

hatch (exclusive) for final transfer of the crew to Gemini B. For alternative flight modes, these functions start when the Orbiting Vehicle achieves 

the operational orbit and terminate with the initiation of Orbiting Vehicle 

disposal. This function includes ejection and de-orbit of the Data Reentry 

Vehicles (DRV). 

3.1.4.2 Special Considerations 

Normal, contingency and emergency modes of operation are included in this 

function. Redundant, alternate and degraded modes of operation shall be 

included in the analysis of the requirements for the on-orbit functions. 

Contingency and emergency modes leading to an abort decision shall be analyzed 

as part of this function. Subsequent flight crew abort requirements shall be 

developed as part of Function 13.0. 

3.1.4.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description of 

on-orbit operations. Detailed discussions for coordination of operational 

plans and technical interchange for design definition of equipment required 

shall be based on this STD to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent 

with the Function 4.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the non-DORIAN 

versions. This list also applies to their DORIAN counterparts, as 

applicable. DORIAN-only documents will be added as they are identified. 

30 

r s : • 
NRO APPROVED FOR SE SPECIAL HANDLI:.G 4.0 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS. 

o ECP's for System Requirements Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's after FACI A018 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o Flight Crew Handbook (LV/Gem.B) A028 [(U) H-602] 

o Flight Directors Handbook A029 [(U) 11-604] 

o Maintenance Requirements Data A031 [(U) L-600] 

o Flight Crew Safety Plan A040 [(U) S-600] 

o System/Design TS Report A041 (S-54) 

o PSA Task Analysis A045 [(U) S-605) 

o System Test Objectives A046 [(U) T-600] 

GENERAL ELECTRIC ITEMS: 

o Version Desc. Document B035 [(U) C-404] 

o Positional Handbook B037 [(U) H-401] 

o SCN B044 (C-11) 

o ECP's for CEI's B046 (C-13) 

o ECP's for System Requirements Change B047 (C-12) 

o ECP's After. FACI B048 (C-19) 

o Relialdlity/Maintenance Measure. Plan B061 [(U) R-402] 

o Reliability Maintenance Apportion. Report B063 [(U) R-403) 

o Mission Crit. Comp. Plan Report B064 [(U) R-404] 

o Reliability FOM Analysis B065 [(U) R-405] 

o Availability Analysis B067 [(U) R-407) 

.o Failure Mode and Effects Analysis B068 [(U) R-408] 

o Reliability Demonstration Study B070 [(U) R-410] 

o Hazard Analysis B075 HU) S-404) 

o Power Status Report B076 [(U) S-405) 

o System/Design TS Reports B079 (S-54) 

o Rehearsal Plan (Input) B104 [(U) T-407] 

o Flight Operations Support Study Report Bill [(U) T-410) 

o Dynamic Analysis Report B114,1(0) S-406) 

o OV Structure Integrity Analysis Report B119 [(U) S-407) 

o LV Heat Trans. Analysis Report Input B121 [(U) S-1103) 

o Electrical System Schematic B122 [(U) E-402] 

o RED Input 

--=S-1P7, 144+4=.fE sfIcd L 1' 

.31 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPEM1.1-1A1',D1.1 G .4.0 

GENERAL ELECTRIC ITEMS: (Continued) 

o pystem Test Objectives 

o Flight Crew Safety Plan 

o Quick Look Ascent and Orbit Report 

o Quick Look Post-Operations Report 

o Flight Directors Handbook 

o Flight Crew Handbook Laboratory Vehicle 

o Command and Operations Handbook 

MCDONNELL ITEMS: 

o Electromagnetic Compatibility Analysis 235 [(U) S-(214)] 

o Gemini B Effectiveness Model Report 7R (U)R-(207) 

o Orbital Requirement Document 17T U (T-221 T3) (Manned) 

o ECP's for CEI's 16C (C-13). 

o Manned Flight Vehicle Time Line 26S U (S-221) 

o ECP's General (After FACI) 18C (C-19) 

o Failure Mode and Effectiveness Analysis 5R [(U) R-(205)1 

o ECP's for System Requirements 27C (C-12) 

o S/C Instru. Sys. Report 13S [(U) S-(205)1 

o Single Point Failure Analysis 4R [(U) R-(204)] 

o Load Analysis - Electrical Equipment 12S ((U) S-(204)] 

o Instru. Books A and B 14S and 15S (U) (S-(206), (207) 

o Effectiveness Progress Status Report 1R (U) (R-(201) 

o Specification Maintenance Document 15C (U)(C-11) 

o Interface Specifications 28C (U) (C-209) 

o Interface Maintenance Document 22C [(U) C-(205)] 

o Update Comm. System Technical Baseline 

o Task Analysis Data (Crew Training) (U) S-(219) 

o Flight Directors Handbook 

• Flight Crew HanJbook (Laboratory Vehicle) 

o Flight Data File 

o System Test Objectives (STO) 

o Quick Look Ascent and Orbit Report 

o Quick L9ok Post Operations Report 

o Electrical System Schematics (ESS) 

o Stre.ctural Design Loads 11S [(U) S-(203)] 

o Flight Crew Safety Plan 

o F1-eouencey Allocation (ETA) Request 

4't ej.1 
SPECIAL HANDL' • NRO APPROVED FOR 

RELEASE 1 JULY 2015 

h.o 

DOUGLAS ITEMS: 

o Specification Maintenance Document (CBI's) B136 & B137 (C-11) 

o ECP's for System Requirements Change B138 (C-12) 

o ECP's for CEI's B139 & B140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

Interface Specifications (IFS) B142 (UC-101) 

o Interface Control Drawing (ICD) B143 (UC-102) 

o IFS/ICD Maintenance Document B144 (UC-103) 

o As-Built Configuration List (AVE - CEI's) B145 (UC-104) 

o CEI Computer Program Part II B152-156 (UC-106) 

o Version Description Document (Computer Program) B160-B164 (UC-112) 

o Interface Document Evaluation B195 (UE-101) 

o Electrical System Schematic B197 (UE-103) 

o Positional Handbook - Computer Program B203 & B204 (UH-101) 

o Users Manual (Computer Program) 3205-B209 (UH-102) 

o Training Requirements Data (Flight Crew) B234 (UQ-101) 

o System/Design Trade Study Report B247 (S-54) 

o System Safety Plan (SSP) B259 & B260 (US-101) 

o LV Structure Integrity Analysis Report B261 (US-102) 

o Stress, Fatigue, & Dynamics Analys.s Report B262 (US-103) 

• Baseline Flight Vehicle Timeline B266 (US-108) 

o Explosive Comp. Tech, Data Sheet B268 (US-111) 

o Mission Status Summary B277 (US-121) 

o ORD Inputs B281 (UT-141) 

o Reliability Crit. Comp. Data Summary 3303 (UT-114) 

o Item Test Procedures (Com-otter Program) B308-B312 (UT-119) 

o Flight Directors Handbook Input 

o Flight Crew Handbook Laboratory Vehicle 

o Flight Crew Handbook Gemini B Input 

o Command and Operations Handbook Input 

o System Test Objectives 

o Flight Crew Safety Plan 

o Quick Look Ascent and Orbit Report 

o Quick Look Post-Operations Report 

o Radio Frequency Allocation (REA) Request B335 (AFPI 7-h067) 

t.) r, 2/11_ I 

:33 
• 

NROAPPROVEDFOR L CR SPECIAL HANDL' 

RELEASE 1 JULY 2M 5 

AGENCY ITEMS: 

o Orbital Support Plan (OSP) 1 

o Recovery Support Plan (RSP) 

• o Operations Requirements (OR) Pt. I, Pt. II 

o System Test Objectives 

o Operations Directive 

I...r 1- 

IL 

3 ,1 " 

' • 

L. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 1..:CRET SPECIAL HANDLriLi 

The STD.for Function 4.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents 

listed above and others that may evolve. Specific references to contractual 

requirements documents by paragraph number are required in the appropriate 

RAS column. 

The STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2; however, MOL SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in paragraph 3.2.2 of Part I. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.4.4 Task Assignment 

The Function Integrator for Function 4.0 is Douglas MSSD. Contributing 

associate contractors are McDonnell Astronautics, Hamilton Standard and 

General Electric. 

General Electric shall prepare the FFBD's to include both the General Electric 

and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's for their 

functions and coordinate changes desired with General Electric. Eastman Kodak 

shall prepare RAS's, TLS's, SBD's, and TSR's to support the FFBD's and submit 

them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph "a" 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph "b" below for both 

General Electric STD and for integrated General Electric/Eastman Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph "b" below in preparing 

and submitting STD to General Electric except for preparation of FFBD's. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

■••■••,. 

:CRET SPECIAL HANDLING 

a. • The Function 4.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government 

agency participation in accordance with the master schedule issued 

by the OSI. 

2. Establish contractor assignments for review, comment, and expansion of flow diagrams and RAS's. 

3. Identify the required timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or definitions reflected in the STD for Function 4.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.4.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

8. Respond to requests for clarification or revision of Function 4.0 

STD if discrepancies are identified during system level integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, SBD's and TSR's in format specified 

in Part I of this Exhibit and submit on 11x17 inch vellum to the 

Function Integrator and to the OSI. Flow diagram expansion and 

its attendant RAS and Timeline Sheet shall be submitted as a 

package for integration. 

2. Respond to requests for clarification or revision of the contributed 

data if discrepancies are identified during integration. 

ri 0,, Si CIAL HANDL' 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLING 

c.• MOL Program Integration Contractor as System Level Integrator 

of the STD shall: 

1. Review Function 4.0 STD to identify possible inconsistencies 

or incompatibilities in functional descriptions and timing, 

defined interfaces and stated requirements, using as a guide 

the functional cross-references incorporated in the STD. 

Compare the on-orbit interfaces identified in the functional 

schematics with the interface requirements defined in the RAS's 

to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of on-orbit requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

(: r ,n, I • 

J. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

C 1 L SPECIAL 1-1PiNDLING 

3.1.5. Function 5.0 "Perform Early Orbit Operations" 

3.1.5.1 Function Description 

These functions start with the blowing of the explosive nuts at the Launch 

Vehicle/Orbiting Vehicle interface (exclusive). Included as a part of the 

analysis of these functions are the maneuvering requirements to achieve the 

specified flight-peculiar operational orbit. These functions terminate at 

the closing of the Gemini B/Laboratory Vehicle tunnel hatch (inclusive) or 

the LV-EVA hatch in the case of extravehicular transfer by the second 

crewman following transfer from the Gemini B, for the principal flight modes. 

For alternative flight modes, these functions terminate when the Orbiting 

Vehicle achieves an operational orbit. 

3.1.5.2 Special Considerations 

Normal, contingency and emergency modes of these functions shall be analyzed 

to determine the equipment and personnel requirements. Contingency and 

emergency functional branches leading to an abort shall be analyzed only 

up to the point of determining a requirement for an abort indication 

(subsequent abort requirements shall be developed as a part of Function 13.0 

for these cases). 

3.1.5.3 Data Requirements 

Function 5.0 STD shall be used as a baseline definition of the early orbit 

phase of the mission. Function 5.0 shall be expanded sufficiently to 

identify the early orbit performance/design requirements for the OV, 

including definition of Mission Payload requirements. The STD shall 

involve the detail analysis of contingencies. 

Planning and requirements documents which must be based on and/or be consistent with the Function 5.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

L I SPECUAL 

3S 
NRO APPROVED FOR 

SPECIAL 1-1414DLIi.G 5.0 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS: 

o ',ECP's for Sys. Ri.q. Chg. A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A018 (C-19) 

o Spec. Maint. Doc. A019 (C-11) 

Flight Crew Handbook (LV/Gemini B) A028 [(U) H-602] 

Flight Directors Handbook A029 [(U) 1-6o4] 

Maint. Req. Data A031 [(U) L-600] 

o Flight Crew Safety Plan A040 [(U) S-600] 

o System/Design T S Report A041 (S-54) 

o PSA Task Analysis A045 [(U) S - 605] 

GENERAL ELECTRIC ITEMS: 

o ECP's for CEI's 8046 (C-13) 

o ECP's for System Requirement Chg. B047 (C-12) 

o ECP's After FACI B048 (C-19) 

o Failure Mode & Effects Analysis B068 [(U). R - 408] 

o Reliability Demonistration Study 3070 [(U) R - 410]. 

o Hazard Analysis B075 [(U) S- 404] 

o Power Status Report B076 [(U) S - 405] 

o System/Design T S Reports B079 (S-54) 

o Flight Operations Support Study Report B111 [(U) T - 410] 

o Dynamic Analysis Report B114 [(U) 8 - 406] 

o OV Structure Integrity Analysis Report B119 [(U) S - 407] 

o LV Heat Trans. Anal. Report B121 [(U) S 408] 

o Electrical System Schematic B122 [(U) E - 402] 

o System Test Objectives 

o Flight Crew Safety Plan 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o Flight Directors Handbook 

o Flight Crew Handbook - LV 

o Electro Magnetic Compatibility Anal. - 235 [(U) S - (214)] 

o Crew Transfer Test Plan - 7T [(U) T (201)] 

o GB Flight. Effectiveness Model Pepo:rt - 73 [(U) R (207)] 
SPECIAL HADLI1';G . 5.0 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

MCDONNELL ITEMS: 

o Requirement Document - 17T,[(U) T-221] 

o ECP's for CEI's - 16C (C-13) 

o Manned Flt. Veh. Time Line - 265,[(U) (S-221)] 

o ECP's General (After FACI) - 18C (C-19) 

o Failure Mode & Effect. Anal. - 5R [(U) R - (205)] 

o ECP's for System Requirement --27C (C-12) 

o Version Descrip. Doc., CPCEI, GBPS - 21C [(U) C - (214)] 

o S/C Instru. Sys. Rpt. - 135 [(U) S - (205)] 

o Single Point Failure Anal. - 4R [(U) R - (204)] 

o Load Anal. - Elect. Eqpt. - 125 [(U) S-(204)] 

o -Instru. Books A & B 145 & 155 [(U) S - (206, 207)] 

o Effectiveness Prog. Status Report - 1R [(U) R - (201)] 

o Specification Maint. Doc. 15C, (U) (C-11) 

o Interface Specifications - 28C [(U) C - (209)] . 

o Interface Maint. Doc. - 22C [(U) C - (205)] 

o Internal Crew Transfer Testing 0 - G 

o Update Comm. System Technical Baseline 

o Task Analysis Data (Crew Training) [(U) S - (219)] 

o Flight Director's Handbook 

o Flight Crew HB (Lab Veh.) 

o Flight Crew HB (GB) 

o Flight Data File 

o System Test Objectives (STO) 

o Range Safety Report 

o Quick Look Ascent & Orbit Report 

o Quick Look Post Operations Report 

o Elect. System Schematics (ESS) 

o Structural Design Loads 11S [(U) S (203)] 

o Flight Crew Safety Plan 

o Radio Freq. Allocation (RFA) Request 

DOUGLAS ITEMS: 

o Spec. Maint. Dec. (CEI's) B136 & 131 (C-11) 

o ECP's for Sys. Req. enc.,. B138 (C-12) 

... 

. 

- - - 

- 

40 
NRO APPROVED FOR A SPECIAL IliT4D1.1" . ' 

RELEASE 1 JULY 2015 

5.0 

DOUGLAS ITEMS (Continued), 

oe ECP's for CEI's B139 & B140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

o Interface Specs. (IFS) B142 (UC-101) 

o Interface Cont. Dwg. (ICD) B143 (UC-102) 

o IFS/ICD Maint. Doc. B144 (UC-103) 

o Config. List (AVE - CEI's) B14.5 (UC-104) 

o Interface Doc. Evaluation B195 (UE-101) 

o Elect. System Schematit B197 (UE-103). 

o Training Reg/ Data (Flt. Crew) B234 (UQ-101) 

o System/Design Trade Study Reports B247 (S-54) 

o 'System Safety Plan (SSP) B259 & B260 (US-101) 

o LV Structure Integrity Analysis Report B261 (US-102) 

o Stress, Fatigue & Dym. Anal. Report B262 (US-103) 

o Baseline Flight Vehicle Timeline B266 (US-108) 

o Miss on Status Summary B277 (US-12.L) 

o ORD Inputs B281 (UT-141) 

o Relic. Crit. Comp. Data Summary B303 (UT-114) 

o Flt. Directors Handbook Input 

o Flight Crew Handbook Lab. Veh. 

o Flight Crew Handbook Gemini B Input 

o Command & Operations Handbook Input 

o System Test Objectives 

o Flight Crew Safety Plan 

o Range Safety Report 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o Radio Freq. Allocation (RFA) Request B335 (AFP) 7-4067) 

AGENCY ITEMS: 

o Orbital Support Plan (OSP) 

o Operations Requirements (OR) Pt. I, Pt. II 

o System Test Objectives 

o Operations Directive 

cDrIvlf:!1 Fr'n1 
NRO APPROVED FOR 

RELEASE 1 JULY 201.5 

For) r, el fit IplEf 

VLUik 

The STD Tor Function 5.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents 

listed above and others that may evolve. When functions are expanded to 

amplify the definition of operational sequences and interfaces beyond this 

level of detail, the Left Hand RAS shall be limited to the function description 

and interface requirements. 

STD shall be prepared, using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2; however, SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in paragraph 3.2.2 of Part I. (Note: 

LH RAS's for procedural functions may be limited to Function 

Descriptions and Interface requirements.) 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference paragraph 3.2 of Part II of 

this Exhibit). 

e. TSR's per paragraph 3.2.4, or comparable contractor's Design Note 

or Technical Note format. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated in 

the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.5.4 Task Assignments 

The Function Integration responsibility for Function 5.0 is assigned to the 

McDonnell Astronautics Company (MCASTRO). Contributing associate contractors 

are Douglas MSSD, Hamilton Standard, and General Electric Company. 

The Function Integration responsibility assigned to McDonnell Astronautics 

Company above shall be for non-DORIAN KA mode requirements only. 

For the KA mode, Eastman Kodak generated STD shall be integrated with General 

Electric STD by General Electric. The resulting integrated STD shall be 

suitably altered by General Electric to remove its DORIAN classification 

while still retaining interfacing requirements before submission to 

McDonnell Astronautics. 

r1 

42 

i 0,1 L:4.1,1,.. iii- ULi 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 L . SPECIAL HiiNDLING 

The Function Integration responsibility for the total KB mode and DORIAN 

KA portions of Function 5.0 is assigned to Douglas MSSD. Contributing 

Associate Contractors are General Electric and Eastman Kodak. As Function 

Integrator,Douglas shall perform the tasks noted in paragraph (a) below for 

the KB mode. 

For both the KA and KB mode the following shall apply: 

General electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's and TSR's to support the 

FFBD's and submit them to GE. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. In accomplishing this integration General Electric shall perform 

the tasks noted in paragraph (a) below. 

General Electric shall perform the tasks noted in paragraph (b) below 

for both GE STD and for integrated General Electric/Eastman Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph (b) below 

in preparing and submitting STD to General Electric except for preparation 

of FFBD's. 

a. The Function Integrator for this function shall: 

1. Prepare, coordinate and issue schedules for associate 

contractor/government agency participation in accordance with 

the Master Schedule issued by OSI. 

2. Establish contractor assignments for review, comment, expansion, 

contingency analysis, and update of flow diagrams, timelines, and 

RAS's. 

3. Review contributed data and comments received from participants 

to ensure documentation is accurate, complete, and concise. 

The Function Integrator shall inform the organizations of any 

identified problems, request revised inputs, and call a meeting 

of those involved, if necessary, to achieve resolution. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL 1-1,1-\::DLING 

4. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.5.3 above. 

5. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

6. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

Respond to requests for clarification or revision of Function 5.0 

STD if discrepancies are identified during system level integration. Coordinate as required. 

b. The Contributing Associate Contractors shall: 

1. Prepare flow diagrams, RAS's, and Timelines in format specified 

in Part I of this Exhibit and submit on 11x17 inch vellum to 

the Function Integrator and the OSI. Flow diagram expansion and 

its attendant RAS and Timeline sheet shall be submitted as a 

package for integration. 

2. Respond to requests for clarification or revision of the contributed data if discrepancies are identified during integration. 

c. MOL Program Integration Contractor as System Level Integrator of the 

STD shall: 

1. Review Function 5.0 STD to insure it is consistent with other 

STD using as a guide the cross-references incorporated in the 

STD. Compare the early orbit interfaces identified in the 

schematic block diagrams with the interface requirements defined 

in the RAS's to verify adequacy of interface definitions. 

44 

r" C'N'Tqlf rn.r, 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL lir",,NDLI:. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the STD is considered consistent, the MPI Contractor shall 

recommend OSI approval. 

d. As the Overall System Integrator (OSI), the MOL Program Office shall: 

1. Resolve inter-contractor/agency discrepancies as required. 

2. Validate and approve Function Integrator STD for use as system 

level integrated data. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDIA 

3.1.6 function 6.0, "Perform Boost" 

3.1.6.1 Function Description 

This function starts at liftoff and terminates with the blowing of the 

explosive nuts at the Launch Vehicle/Orbiting Vehicle interface with the 

exception that the Launch Vehicle operations covering positive booster 

separation and disposal are included as a part of this function. Also 

included as a part of the analysis of this function are the requirements to 

achieve the specified flight-peculiar nominal orbit. Both normal and various 

contingency modes are branches of these functions to be analyzed for 

personnel and equipment requirements. 

3.1.6.2 Special Considerations 

Emergency modes of operation shall be analyzed for this function. Redundant, 

alternate, and degraded modes of operation shall be included in the analysis 

of the requirements for the boost functions. Contingency and emergency modes 

leading to an abort decision shall be analyzed as part of this function. 

Subsequent flight crew abort requirements shall be developed as part of 

Function 13.0. 

3.1.6.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description of 

the vehicle during boost operations. Detailed discussions for coordination 

of operational plans and technical interchanges for design definition of 

equipment required, shall be based on this STD to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent with the Function 6.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the non-DORIAN 

versions. This list also applies to their DORIAN counterparts, as 

applicable. DORIAN-only documents will be added as they are identified. 

) td a Ni LI LA 4, '■• 1 rip 

iso:1 

le; 
SPECIAL HANDLING 6.o 

NRO APPROVED FOR 

RELEASE 1 JULY 201.5 

HAMILTON STANDARD ITEMS: , 

• 

6 

o 'ECP's for Sys. Reg. Chg. A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A018 (C-19) 

o Spec. Maint. Doc. A019 (C-11) 

o Flight Crew Handbook (LV/Gemini B) A028 [(U) H-602] 

o Flight Directors Handbook A029 [(U) H - 6o4] 

o Flight Crew Safety Plan A040 [(U) S - 600] 

o System/Design T S Report A041 (S-54) 

o PSA Task Analysis A045 [(U) S - 605] 

o PRD inputs A053 [(U) T - 603] 

MARTIN ITEMS: 

0 Spec. Maint. Documents C2 & C19 (C-11/M) 

0 ECP's for Sys. Req. Chg. C3 & C4 (C-12) 

0 ECP's for CEI's Pt. I C5 (C-13/M) 

0 ECP's for CEI's Pt. II C6 (C-19M) 

0 Spec. Maint. Doc. C19 (C-11/M) 

0 Engr. Data (Cat. B) Interface Cont. E3 (E - 106/m) 

0 Missile Explosive Comp. Tech. Data Sheet; H1 (H-4) 

0 Design Loads Report S1 (US-111/M) 

0 System Dynamics Anal. S4 

0 Tech. Info. Veh. Elec. Req. Study s7 (xs - 621/M) 

0 Tech, Info. - EMC Study S8 (XS - 621/M) 

0 Titan IIIM Data Book S9 

0 Tech. Info. - Stability Anal. S10 (XS - 621/M) 

0 Prop. Sys. Anal. Report S14 (us-114) 

0 Prop. Temp. Anal. (Launch) S15 (US-110) 

o Strut. Dynamics Report S17 (US-112) 

o Lauach Elyout Envel. Study S33 (XS 

o Staging Analysis S34 

o Tech. Info. - Ref. Traj. Anc.l. S35 

o Tech. Info. - Ref. Traj. Anal. S36 

o Launch Elyout Envel. Study S37 (XS 

- 621/M) 

(XS --621/Y) 

(XS - 621/M) 

- 621/M) 

SP.Cill lAr,OLI;,. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

MARTIN ITEMS: (Continued) 

o ,Staging Analysis S38 

o Tech. Info. - Guid. Ref. Traj. Data S39 (XS _- 621/M) 

o Range Safety Report S41 (S - 34/M) 

o Flight Term. Report S42 (S - 34/M) 

o Guid. & Flight Cont. Anal. S44 (US-115) 

o Crew Safety S W Req. Report S45 

o Tech. Info. - Ordin. Safety Anal. S55 (XS - 621/M) 

o Tech. Info. - Sys. Safety Anal. S57 (Xs - 621/M) 

o Tech. Info. - R F Suscept. Anal. S65 (XS - 621/M) 

o Tech. Info. - Disper. Margin Anal. S66 (XS - 621/M) 

o Gen. Flight Test Plan T4 (UT-13) T39 

o PRD Input - Chg. T9 (T-21/M) 

o System Test Obj. Inputs T10 (T - 123) 

o Flight Crew Safety Plan Input 

o Quic:: Look Ascent & Orbit Report 

o Quic:: Look Post-Operations Report 

o Flight Directors Handbook 

o Flight Crew Handbook - Gemini B 

GENERAL ELECTRIC ITEMS: 

o Expl. Corp. Tech. Data B128 (US-411) 

o SCN B044 (C-11) 

o ECP's for CRI's B01i6 (C-13) 

o ECP's for Sys. Req. Chg. B047 (C-12) 

o ECP's After EACI B048 (C-19) 

o Failure Mode & Effects Anal. B068 [(U) R - 408] 

o Relib. Demonstration Study B070 [(U) R - 1110] 

o Hazard Analysis B075 [(U) S - 404] 

o Power Status Report B076 [(U) S - 405] 

o SystemA2sign T S Reports B079 (S-54) 

o PRD Input B110 [(U) T 409] 

o Flight Operations Support Study Report B111 [(U) T - 410] 

o Dyna:dc Anal. Report B1311 [(U) S - 405) 

o 0v S7,ruct. Integrity Anal. Report B119 [(U) S - 407] 

r 

6.o 
L U t SPECIAL HANDLING 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

GENERAL ELECTRIC ITEMS: (Continued) t 

o°,1,V Heat Trans. Anal. Report B121 [(U) S - 408] 

o Elec. Sys. Schematic B122 [(U) E 402] 

o System Test Objectives 

o Quick Look Ascent & Orbit Report 

o Fit. Directors Handbook 

o Electro Magnetic Compatibility Anal. 235 [(U) S - (214] 

MCDONNELL ITEMS: 

o Electro Magnetic Compatibility Anal. 235 [(U) S - (2141 

o GB Flt. Effectiveness Model Rpt. - 7R (U) R - (207) 

o GB Pre. Ign. Model Report - 6R (U) R - (203) 

o -ECP's for CEI's - 16C (C-13) 

o Manned Flt. Veh. Time Line - 265, [(U) 5-22] 

o ECP's General (After FACI) 18C (C-19) 

o Failure Mode & Effect. Anal - 5R [(U) R - (205)] 

o ECP's for Sys. Req. - 27C (C-12). 

o S/C Instru. Sys. Rpt. - 135 (N) S (205)] 

o Single Point Failure Anal. - 4R [(U) S - (204)] 

o Load Anal. - Elect. Eqpt. - 125 [(U) S •-• (204)] 

o Instru. Books A & B 145 & 155 [(U) S - (206), (207)] 

o Effectiveness Prog. Status Rpt. 1R, [(U) R - (201)] 

o Specification Maint. Doc. - 15C (U) (C - 11) 

o Interface Specifications - 28C [(U) C (209)] 

o Interface Maint. Document - 22C [(U) C - (205)] 

o Aero Data Bock - 215 [(U) S (212)] 

o Update Comm. System Technical Baseline 

o Task Analysis Data (Crew Training) (U) S - (219) 

o Fit. Dir. HB 

o Flt. Crew 1[B (GB) 

o Flt. Data File 

o System Test Objectives (STO) 

o Rangt! SE:fety Report 

o Quick Look Ascent & Orbit Report 

o Quick Look Post Operations Report 

o Elect. System Schematics (.SS) 

6.0 

19 
NRO APPROVED FOR SECRET. SPECiALI-lid:DLri,G 6.o 

RELEASE 1 JULY 2015 

MCDONNELL ITEMS: (Continued) 

o :StrUctural Design.Loads 11S [(U) S - (203)1 

o Flight Crew Safety Plan 

o Radio Frequency Allocation (RFA) Request 

DOUGLAS ITEMS: 

•o. Flight Vehicle CEI B001 (C-2/M-1) Pt. I 

o Specification Maintenance Document (CEI's) B136 & B137 (C-11) 

o ECP's for System Requirement Change B138 (C-12) 

o ECP's for•CEI's B139 & B140 (C-13) 

o ECP's -• Post FACI B141 (C-19) 

o Interface Specs. (IFS) B142 (UC-101) 

o Interface Cont. Dug. (ICD) B143 (UC-102) 

o IFS/ICD Maintenance Document B144 (UC-103) 

o As-Built Configuration List (AVE - CEI's B145 (UC-104) 

o Interface Document Evaluation B195 (UE-101) 

o Electrical System Schematic B197 (UE-103) 

o Training Requirement Data (Flight Crew) B234 (UQ-101)- 

o Syst-m/Design Trade Study Reports B247 (S-54) 

o System Safety Plan (SSP) B259 & B260 (US-101) 

o LV Structure Integrity Analysis Report B261 (US-102) 

o Stre-s, Fatigue & Dynamic Analysis Report B262 (US-103) 

o Baseline Flight Vehicle Timeline B266 (US-108) 

o Mission Status Summary B277 (US-121) 

o Reliability Crit. Comp. Data Summary B303 (UT-114) 

o PRD Inputs B305 (UT-116) 

o Flight Directors Handbook Input 

o Flight Crew Handbook Laboratory Vehicle 

o Flight Crew 1iandbock Beuini B Input 

O Command and Operations handbook Input 

O System Test Objectives 

o Flight Crew Safety Plan 

o Range Safety Report 

o Quick Look Ascent and Orbit Ecuort 

o Quick Look Post-Operations Report 

I L.() rt— YU • 
" L SPECIAL HANDLI.,G 6.0 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

DOUGLAS ITEMS: (Continued) 

o :Radio Frequency Allocation (RFA) Request B335 (AFPI 7-4067) 

o Launch Vehicle Data Book 

AGENCY ITEMS: 

o Program Support Plan (PSP) 

o Operations Req. (OR) Pt. I, Pt. II 

o System Test Objectives 

o Operations Directive 

o -Trajectories - Ascent 

■•■ 

cDcr-1,f,. 1 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIU 

The STD for Function 6.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. 

Specific references to contractual requirements documents by paragraph 

number are required in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SPO approved equivalent 

contractors prepared forms and approaches may be used in lieu 

of Right Hand RAS's specified in Paragraph 3.2.2 of Part I. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS's per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.6.4 Task Assignment 

The Function Integrator for Function 6.0 is Martin-Marietta. Contributing 

associate contractors are Douglas MSSD, McDonnell Astronautics and General 

Electric. Martin-Marietta Corporation shall integrate data from United 

Technology Center, Aerojet General Corporation, A-C Electronics Division 

and Spacecraft Incorporated. 

The Function Integration responsibility assigned to the Martin-Marietta 

Company above shall be for non-DORIAN KA mode requirements only. 

For the KA mode, Eastman Kodak generated STD shall be integrated with General 

Electric STD by General Electric. The resulting integrated STD shall be 

suitably altered by General Electric to remove its DORIAN classification 

while still retaining interfacing requirements before submission to the 

Martin-Marietta Company. 

The Function Integration responsibility for the total KB mode and DORIAN 

KA portions of Function 6.0 is assigned to Douglas MSSD. Contributing 

52 

w 
NRO APPROVED FOR SPECIAL HANDLING 

RELEASE 1 JULY 2015 

associate contractors are General Electric and Eastman Kodak. As Function 

Integrator, Douglas shall perform the tasks noted in paragraph "a" below 

for the KB mode and DORIAN portions of the KA mode. 

For both the KA and KB modes, the following shall apply: 

SPECIAL HANDLING 

52A 
SPECIAL HANDLING 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

Genera' Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's and TSR's to support the 

FFBD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. In accomplishing this integration, General Electric shall perform the tasks noted in paragraph "a" below. 

General Electric shall perform the tasks noted in paragraph "b" below for 

both General Electric STD and for the integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph "b" below in 

preparing and submitting STD to General Electric except for preparation 

of FFBD's. 

a. The Function 6.0 Integrator shall: 

1. Prepare, coordinate, and issue schedules for contractor/ 

government agency participation in accordance with the master 

schedule issued by OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. 

3. Identify the required timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or 

definitions reflected in the STD for Function 6.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns on 

RAS's per paragraph 3.1.6.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

• 

r c

Z. 

;07t 

1 2

,'"'

.1LIL. „i-11 1b. 1 

53 
NRO APPROVED FOR 

RELEASE 1 JULY 201.5 

PECIAL HANDLING 

' 7. As soon as possible after the function integration of each STD • 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

8. Respond to requests for clarification or revision of Function 6.0 

STD if discrepancies are identified during system level integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines and SBD's in format 

specified in Part I of this Exhibit and submit on 11x17 inch 

vellum to the Function Integrator and to the OSI. Flow diagram 

expansion and their attendant RAS and Timeline Sheet shall be 

submitted as a package for integration. 

2. Respond to requests for clarification or revision of the contributed data if discrepancies are identified during integration. 

c. MOL Program Integration Contractor: as System Level Integrator 

of the STD shall: 

1. Review Function 6.0 against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in the 

STD. Compare the boost interfaces identified in the functional 

schematics with the interface requirements defined in the RAS's 

to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

1 " 

0 L. J 

1:1" t 

-.L. I it -1h • 
NRO APPROVED FOR s[CRET SPECIAL HANDLING 

RELEASE 1 JULY 2015 

d. 'The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of boost requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

HANniiia 
SECRET SPECIAL 1-1ANDLIr:G 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

3.1.7 ,Function 7.0 "Perform Installation, Checkout, Prelaunch Operations 

and Launch" 

3.1.7.1 Function Description 

For each MOL flight this function starts with arrival of the first item of 

AVE at the MLF and terminates at completion of MLF turnaround activities. 

For the AVE this function terminates at liftoff. 

• For the MLF activation this function begins with arrival of the first item 

of associate contractor furnished ground equipment at the MLF and terminates 

at completion of launch dress rehearsal for the first manned flight. 

The analysis of this function shall include: (1) installation and checkout 

of AGE, facilities and associated software, (2) receipt, inspection, assembly, 

checkout, integrated testing, and launch of the flight articles, (3) post 

launch refurbishment/revalidation of MLF AGE, facilities and software, 

(4) backout following a scrub or maintenance recycle, (5) preparation for, 

delivery to and receipt of the flight crew at the flight crew at the SLC-6 

and their subsequent activities. 

The requirements for interface substitutes for MLF AVE checkout prior to 

electrical mating shall be developed as a part of this function. 

3.1.7.2 Special Considerations 

The requirements of VAFB upon MCC shall be identified in Function 7.0 and, 

conversely, the requirements of MCC upon VAFB shall be identified in Function 

12.0. For maintenance purposes, Function 11.0 shall be referenced in 

Function 7.0. 

3.1.7.3 Data Requirements 

The Systems Technical Documentation (STD) will be used by the government 

agencies and shall be used by the associate contractors as a baseline 

reference description of the Installation and Checkout of the FV segment 

AGE and for prelaunch and launch activities for the FV segments. Detailed 

discussions for coordination of operational plans and technical interchanges 

for design definition of equipment required, shall be based on the STD to 

the extent practicable. 

(-1 

56 
NRO APPROVED FOR SECRET SPECIAL I-1 4 " 

RELEASE 1 JULY 2015 

Plannipg and requirements documents which must be based on and/or be consistent with the Function 7.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

Ira r- SHICIAL HAMMY. 

57 
SP ECIAL HAri:DL:„ NRGAPPROVED FOR _ _ 

RELEASE 1 JULY 2015 

7.o 

HAMILTON STANDARD ITEMS: , 

o CEI (Prime Equipment) Pt. II A006 (C-3) A008 & A009 

o CEI (ID Equipment) Pt. II A007 (C-8) A010 - A01A, A020 

o ECP's for System Requirements Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A018 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o CEI Detail Specification (Prime Equipment) Pt. II A021 (C-4) 

o Activation Manual Input A026 [(U) F-600] 

o Preliminary Countdown Manual A027 [(U) H-600] 

o Flight Crew Handbook (LV/Gemini B) A028 [(U) H-602] 

o Flight Operations Crew Personnel Training Plan A038 [(U) Q-601] 

o Launch Operations Crew Cert. Plan A039 [(U) Q-602] 

o Flight Crew Safety Plan A040 [(U)5-600] 

o Systen/Design Trade Study Report A041 (S-54) 

o PSA Task Analysis A045 [(U)5-605] 

o Cont. Vehicle Integration Test Procedures A047 [(U)T-601] 

o Integration Assembly and C/O Plan A048 (T-5) 

o PRI) Inputs A053 [(U)T-603) 

o Cont. Vehicle Segment C/0 Requirements Plan A056 [(U)T-606] 

o Checkout Requirements Plan 

o Ground Safety Plan Inputs 

o Test Procedures 

o Launch Test Directive Inputs 

o Launch Evaluation Report Inputs 

MARTIN ITEMS: 

o Specification Maintenance Documents C2 & C19 (C-11/M) 

o ECP's for System Requirements Chang C3 & C4 (C-12) 

o ECP's for CFI's Part I C5 (C-13/M) 

o ECP's for CFI's Part II C6 (C-19/ .I) 

o CEI (Prime Equipment Part II C9 (C-3/II) 

o CEI (Ident Item) Part II C10 (C-8/11) 

o CEI (Prime Equipment) Part II CPTO1D01; C11(C-3/M) 

o CEI (Ident. Item) Part II C12 (C-8/11) 

o Specification Maintenance Document C29 (C-21/M) 

o Engincerin: Data (Cat. fl) Interface Cont. E3 (E-106/M) 

o Loads Report S1 (US-112/M) 

o Technical InfelFIiion - Vehicle Elec. Requirements Study S7 (XS--671/%.1) -. 

o T2ehn4_cal Infort.50-1 - EM Study S8 ();S-621/M0 

• HP, 

111:.1pat' 
L L I S?EciALVJ:2 —:. 7.0 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

MARTIN ITEMS: 

o 'Technical Information - Stability Analysis S10 (XS-621/M) 

o Prop. System Analysis Report S14 (US-114) 

o Prop. Temp. Analysis (Launch) S15 (US-110) 

o Struct. Dynamics Report S17 (US-112) • 

o Technical Information - Ref. Trajectory Analysis S35 (XS-621/M) 

o Technical Information - Guid. Ref. Traj. Data S39 (XS-621/M) 

o Technical Information - Prestest Traj. Data S40 (XS-621/M). 

o Range Safety Report S41 (5-34/M) 

o Pad Safety Report S43 (S-34/M) 

o Technical Information - Ordin. Safety Analysis S55 (XS-621/M) 

o Technical Information - System Safety Analysis S57 (XS-621/M) 

o Activation Plan 564 (-S-35) 

o Technical Information - RF Suscept, Analysis S65 (XS-621/M) 

o Launch Test Directive T5(T-124/M) 

o PRD Input - Change T9 (T721/M) 

o Countdown Manual Inputs T12 & T13 (T-125/M) 

o Cont. Vehicle Integration Test Procedures 

o Flight Crew Safety Plan Input 

o Flight Operations Crew Training Plan 

o Flight Crew Handbook - Gemini B 

o Checkout Requirements Plan 

o Test Procedures Launch Evaluation Report Inputs 

- GENERAL ELECTRIC ITEMS: 

o Activion Manual B-124 (UP-(401)) 

o Activation Manual - Task Description B-133 (UF-403) 

o CEI (Prime Equipment) Pt. II B007-B015 (C-3) B031 

o CEI (ID) Pt. II B016-B030 (c-8) 

o Version Description Document E035 ((U)C-404) 

o Positional Handbook B037 [(U)K-401] 

o Detail Specification (CC) Pt. II B043 (C-11) 

o SCN B044 (C-11) 

o ECP's for CEI's B046 (C-13) 

o ECF's for System Requirements Ch.onge B047 (C-12) 

o ECP's after FACI B046 (C-19) 

o Hazard B015 [(U)S-404] 

o StF.Ltl.nr; BoT6 [u)s-):05] 

- • L flAhDLIA 

:if) 
NRO APPROVED FOR 

N ET _SP_ECIAL HANDy:T. 7.0 

RELEASE 1 JULY NM 

GENERAL ELECTRIC ITEMS: (Continued) ', 

o :System Design Trade Study Reports B079 (S-54) 

o EMC Test Plan B082 (T-12-28.0) 

o Cont. Vehicle Segment C/O Requirements Plan 

o Launch Operations Crew Cert. Plan B103 [(U)T-406] 

o Rehearsal Plan (Input) B104 [(U)T-407] 

o PRD Input B110 [(U)T-409] 

o Launch Operations Support Study Report B112 [(U)T-411] 

o Electrical System Schematic B122 [(U)E-402] 

o Cont. Vehicle Integration Test Procedures 

o Preliminary Countdown Manual 

o Flight Operations Crew Training Plan 

o Checkout Requirements Plan Part B 

0_ Launch Test Directive Inputs 

o Test Procedures 

o Ground Safety Plan 

o Launch Evaluation Report Inputs 

• 

MCDONNELL 1.171.24S : 

o Electromagnetic Compatibility Analysis 235 [(U)S-(214)] 

o Contractor Vehicle Segment C/O Requirements Plan 27T (U)T-(214) 

o Program Requiremnts Document 19T (U)T-(116). 

o GB Flight Effectiveness Model Report 7R (UIR-(207) 

o Det. Integ. Activation Sched. & Activation Task Description 28T & 33T 

(U)T-(215) (No 33T) 

o CEI Pet. Spec. Part II, Facility (Facility Ident. Items) 37C to 39C (U) (C-7) 

(Not in CDLI) 

o Effectiveness Assessment Plan 3R [(U)R-(203)] 

o GB Pre-Iga. Model Report 6R (U)R-(206) 

o Launch Opert,tions Crew Cert. (LOCCP) 25T (U)T-(213) 

o ACE Plan 5:1 [ (U)M-(203)] 

o ECP':. for CEI's 16C (C-13) 

• ECP's General (After FACT) 18C (C-19) 

o ECP': for System Requirem-:nts 27C (C-12) 

o CEI Pet. Specs. Part IT /OE (Prime Eqpt.) 3C to 10C (C-3) 

o Acceit-')ce Test Pion, AGE 21T (U)T--(209) 

o Acceptance Test PJ-,n GBP0 22T (U)T--(210) 

o Version Dcr,criptio71 Docu,4ort CI'CLT GBPS 31C (W)C-(214)] 

o S/C S;,-m:. Report 22:', (U)S-(205) 

o Technical Pub. SC Fr.,,,11. Man1:-.1 1k [(U)N-(201)] 

o CEI Pit. Pt... TI-d(i - AG': A3r, ;to a),c (C-8) 

4.) L 

,JLI1 

r-- 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

•

L I. Sf r 

HANDLGI;G 7.0 

MCDONNELL ITEMS: (Continued) 

o *CEI Det. Specs. Pt. II, AVE (Prime Eqpt.) 1C U(C-3)' 

o CEI Det. Specs. Pt. II, AVE (Prime Eqpt.) Addenda 2C (GL,4) 

o Single Point Failure Analysis 4R C(U) R-(204)] 

o Instru. Books A & B 14S & 15S (U)(S-(206, (207) 

o Electro - Interference Test Plan 26T (T-12) 

o Specification Maintenance Document 15C (C-11) 

o Interface Specifications 28C (U)(C-(209)) 

o Interface Maintenance Document 22C [(U)C-(205)] 

o Task Analysis Data (Crew Training) (U) S-(219) 

o Flight Crew Handbook (Gemini B) 

o Tech. Pub. - Flight Checklist Handbook 

o Integrated Test Procedure Input 

o Preliminary Countdown Manual - Inputs 

o System Test Objectives (STO) 

o Launch Test Directive (Inputs) 

o Ground Safety Plan (Inputs) 

o Range Safety Report 

o Launch Evaluation Report (Inputs) 

o Electrical System Schematics (45) 

o Tech. Pub. - AGE Operations and Service Manual 4H [(U) H (201)] 

o Structural Design Loads 11S [(U)S-(203)] 

o Flight Operations Crew Personnel Training Plan 

o Checkout Requirements Plan Part B 

o Flight Crew Safety Plan 

o Radio Frequency Allocation (RFA) Request 

o Test-Procedures 

DOUGLAS ITEMS: 

o Flight Vehicle CEI B001 (C-2/M-1) Pt. I 

o CEI (Prime Equip.) Pt. II B346, B002-B074 (C-3/M-1) 

o CEI (Ident. Item) Pt. II B079-B111 (C-8/M) 

o Detail Spec (ICC) B112-B135 (C-10/td) 

o Specification MRintenance Document (CEI's) B136 BIT( (C-11) 

o ECP's for System Requirements Change B138 (C--12) 

o ECP's for CFI's P139 & (C-13) 

o ECP's -- Post FACT B1h1 (C-19) 

c Interface Speeirations(1FS) B342 (UC-101) 

1/4) .k) fiiik Lk' G 
NRO APPROVED FOR SECRET .SPECIAL -HANDLIM 7.0 

RELEASE 1 JULY 2015 

'DOUGLAS ITEMS: (Continued) 

o Interface Control Drawings (ICD) B143 (UC-102) 

o IFS/ICD Maintenance Document B144 (UC-103) 

o As-Built Configuration List (AVE - CEI's) B145 (UC-104) 

o CEI Computer Program Pt. II B152-3156 (UC-106) 

o Version Description Document (Computer Program) 3160-B164 (UC-112) 

o Interface Document Evaluation B195 (UE-101) 

o Electrical System Schematic B197 (UE-103) 

o Positional Handbook - Computer Program B203 & B204 (UH-101) 

o Users Manual (Computer Program) B205-B209 (UH-102) 

o Training Requirements Data (Flight Crew) B234 (UQ-101) 

o Launch Operations Crew Cert. B235 (UQ-102) 

o System/Design Trade Study Report B247 (S-54) 

o System Safety Plan (SSP) B259 & B260 (US-101) 

o Stress, Fatigue, and Dynamic Analysis Report B262 (US-102) 

o Ground Safety Plan B279 (US-126) 

o Electro-Interference Test Plan B282 (T-12) 

o Ground Test Plan - Effectiveness B288 (UT-101) 

o Item Test Plan (Computer Program) B292-B299 (UT-109) 

o C/O Requirements Plan Part A B304 (UT-115) 

o PPD Inputs B305 (UT-116) 

o .Flight Vehicle Checkout Plan Part A B307 (UT-118) 

o Activation Manual Input B350 (UF-101) 

o Activation Manual Input B351 (UF-101) 

o Flight Operations Crew Training Plan Input 

o flight Crew handbook Laboratory Vehicle 

o Flight Crew Handbook Gemini B Input 

o Co=and and Operations Handbook Input 

o Checkout Rcquiremants Plan Part B 

o Cont. Vehicle Integ, Icst Procedures 

o Preliminary Countdown Manual 

o Flight Crew Safety Plan 

o Range Safety Report 

o Radio Frequenc7ey Allocation (HFA) Request B335 (AFT' 7-4067) 

O Launch VeMle Data Rook 

O YE.LrP 

EvaT-aation Ec:fport Inputs 
L L .1.. i-lL.1;11-11., HMWLIt1 7.0 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

AGENCY ITEMS: 

o 'Program Support Plan (Ps) 

o Operations Requirements (OR) Pt. I 

o Operations Directive 

o Launch Vehicle Data Book 

r I 

" C 

63 
NRO APPROVED FOR SECRET SPECI LII iDLI 

RELEASE 1 JULY 2015 

The STD for Function 7.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents 

listed above and others that may evolve. 

Specific references to contractual requirements documents by paragraph number 

shall be listed in the appropriate RAS column. 

The RAS shall contain, in addition to the requirements of paragraph 3.2.2, a 

sequence of operation detailed enough to permit construction of the TLS 

and FFBD. Where not clearly stated in the Function Description, the scope 

and objective of the function shall be identified. 

Preparation of TLS's shall consider the following rules: 

"Greenlight" or nominal timelines shall be prepared initially; however, 

as sufficient informationativelops to do so, "redlight" or contingency 

time shall be added. "Redlight" time entries shall be clearly identified. 

Periods of activity which are required to be continuous shall be 

identified for purposes of determining activity break points. 

.•■•■■•• 

SBD's shall be used for definition of AVE to AGE and AGE to AGE interfaces 

during AVE operations and for AGE to AGE interfaces during AGE installation, 

checkout and demonstration. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SPO approved ejivalent contractor 

prepared forms and approaches may be used in lieu of Right Hand RAS's 

specified in Paragraph 3.2.2 of Part I. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.7.4 Task Assignment 

The Function 7.0 integration responsibility is assigned to Douglas MSSD. 

Contributing associate contractors are General Electric, McDonnell Astronautics, 

v ‘);- ;■ - ■ ;,,,i11-1, 41.1 

64 
SPECIAL FlAi-,IDLL,G 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

Martin Marietta, and Hamilton Standard. Martin Marietta Corporation shall 

integrate data from United Technology Center, Aerojet General Corporation, 

A-C Electronics Division and Spacecraft Incorporated and shall submit the 

integrated TIIIM STD to the Function 7.0 Integrator. 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to support the 

FFBD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph (b) 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph (b) below 

for both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph (b) below in 

preparing and submitting STD to General Electric except for preparation of 

FFBD's. 

a. The Function 7.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government agency participation in accordance with the master schedule 

issued by the OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. 

3. Identify the required timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or 

definitions reflected inthe STD for Function 7.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and if necessary, call a 

meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.7.3 above. 
NRO APPROVED FOR SECRET SPECIAL 

RELEASE 1 JULY 201.5 

• 6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and the OSI. 

8. Respond to requests for clarification or revision of Function 

7.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, SED's, and TSR's in 

format specified in Part I of this Exhibit and submit on 11x17 

inch vellum to the Function Integrator. Flow diagram expansion and 

their attendant RAS and Timeline Sheet shall be submitted as a 

package for integration. 

2. Respond to requests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

c. MOL Program Integration Contractor as System Level Integrator of 

the STD shall: 

1. Review Function 7.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in 

the STD. Compare the interfaces identified in the functional 

schematics with the interface requirements defined in the 

RAS's to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

DI..1;;G 
NRO APPROVED FOR S C C_R Er SPECIAL HANDLI„,, 

RELEASE 1 JULY 2015 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECia 

3.1.8. Function 8.0 "Test, Accept, and Deliver MOL System" 

3.1.8.1 Function Description 

The functions to be analyzed for requirements start with the completion of 

fabrication of the first manufactured article of MOL AVE or supporting ground 

equipment, and proceed through evaluation tests, qualification tests, acceptance tests, and shipment to the MOL Launch Facilities (or other location, 

in the instance of certain AGE). The function terminates with delivery of 

the last manufactured article to VAFB for inspection, assembly and integration. 

Each associate responsible for contributing equipment or software to the 

MOL Program shall analyze his own area of responsibility to define his 

equipment, test, and facility requirements. The requirements for factory 

interface substitutes (simulators) shall be developed as part of these 

functions. 

3.1.8.2 Special Considerations 

None. 

3.1.8.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description 

for testing, acceptance and delivery of the MOL System. Detailed discussions 

for the purpose of coordination of operational plans and technical interchanges for design definition of equipment required shall be based on this 

STD to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent with the Function 8.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

r; LI ■ ro 

II 0,11-#rrq 
8.o 

NRO APPROVED FOR SPECIAL HANDLING 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS: 

o hi (Prime Equip.) Pt. II A096 (C-3) A008 & A009 

o CEI (ID Equip) Pt. II A007 (C-8) A010-A01A, A020 

o ECP's for System Requirements Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's after FACI A018 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o CEI Detail Spec. (Prime Equip.) Pt. II A-21 (C-4) 

o System/Design Trade Study Report A041 (S-54) 

o Category I Test Plan/Procedures A050 (T-102/M) 

o Acceptance Test Procedures A051 (T-115) 

o Cont. Vehicle Segment C/O Requirements Plan A056 ((U)T-606) 

MARTIN ITEMS: 

o Specification Maintenance Documents. C2 & C19 (C-11/M) 

o ECP's for System Requirements Change CE & C4 (C-12) 

o ECP's for CEI's Pt I C5 (C-13/M) 

o ECP's for CEI's Pt. II C6 (C-19/M) 

CEI (Prime Equip) Pt. II C9 (C-3/M) 

o CEI (Ident. Item) Pt. II C10 (C-8/M) 

o CEI (Prime Equip) Pt. II CPTO1D01; Cll (c-3/m) 

o CEI (Ident. Item) Pt. II C12 (C-8/M) 

o Specification Maintenance Document C19 (c-11/m) 

o Tech. Info. - Veh. Elec. Req. Study S7 (XS-621/m) 

o Tech. Info. - EMC Study SS (XS-621/M) 

o Acceptance Test Procedures T1 & T2 (T-13) T39 

GENERAL ELECTRIC ITEMS: 

o CEI Acceptance Test Plan B131 (UT-h01) 

o CEI (Prime Equip.) Pt. II BOOT-B015 (C--3) B031 

o CEI (ID) Pt. II B016-B030 (C-8) 

o Version Description Document E035 [(U)C-401t] 

o Positional Yindbook B037 [(U)11-401] 

o DeGa.al Spec. (CC) Pt. II B043 (C-11) 

o SCN DO!lh (C-11) 

• ECP's for CEY's BOL6 (C-33) 

o ECP's for Systc,n Requirents Change BO47 (C-22) 

f 1117'11-1! nte-N 

J7 L~,1irtL I L. ;, 

E;f) 
NROAPPROVEDFOR I: (1J It E. T " 01 ECU 8 HANDLING 

8.o 

RELEASE 1 JULY 2015 GENERAL ELECTRIC ITEMS: (Continued) 

o .ECP's after FACI X048 (C-19) 

o 'Mission Crit. Comp. Plan Report B064 [(u)R-404] 

o System/Design Trade Study Reports B079 (S-54) 

o Ground Test Plan Input B083 [(U)T-404] 

o Cont. Veh. Seg. C/0 Requirements Plan 

o CEI Acceptance Test Plan B087 [(U)T-401] 

o CEI Qualification Test Plan B089 [(U)T-405] B101 

o CEI Evaluation/Qualification Test Plan B090-B094 [(U)T-405] 

o CEI Acceptance Test Plan B095-B100 [(U)T-401] B102 

MCDMELL ITEMS: 

o Electromagnetic Compatibility Analysis 23S [(U)S-(214)] 

o Crew Transfer Test Plan 7T (U)T-(201) 

o Structural Qual. Test Plan 2T (U)T-(201) 

o CEI Pet. Spec. Part II, Facility (:Facility Ident. Items) 37C-39C (C-7) 

(Not in CDRL) 

o Effectiveness Assessment Plan 3R [(U)R-(203)] 

o Altitude Sep. Test Plan 5T (U)T-(201) 

o Ejection Seat Function Test Plan 4T (U)T-(201) 

o AGE Plan 5M [(U)M-(203)] 

o ECP's for CEI's 16C (C-13) 

o Acceptance Test Plan, AVE 20T (U)T-(208) 

o ECP's General (after FACI) 18C (C-19) 

o Performance/Design Requirements Report GBPS 25C [(U)C-(208)] 

o ECP's for System Requirements 27C (C-12) 

o CE1 Pet. Specs. Pt. II, AGE (Prime Eqpt.) 3C-10C (C-2) 

o Acceptance Test Plan, AGE 21T (U)T-(209) 

o Acceptance Test Plan GBPS 22T (U)T-(210) 

o Item Test Plan GBPS Computer Procia:71 29T (U)T-(216) 

o CEI Pt. 1J, GBPS Computer Program 30C [(U)C-(211)] 

o S/C Therm. - Vac. Test Plan 6T (U)T-(201) 

o Version Description Document, CPCEY, GBPS 31C [(U)C-(214)] 

o Item Test Procedures, GBPS Computer Program 30T (U)T-(217) 

o S/C lnstru. System Deport 13S (U)S-(205) 

o CE1 Pct. Sn, _:cs. Pt. II Iaent. AC*: 31C-1hC (C-8) 

o CET Pct. Sp.?c,— it. Ii, AV1': (1 r57 Eapt.) 3C U (C-3) 

(.1 L—Ule I 

linT"n! 17%,,0 1
NROAPPROVEDFOR ittt.' SPECIAL 1-1A2LING 8.o 

RELEASE 1 JULY 2015 

MCDONNELL ITEMS: (Continued) 

o •CEI Det. Specs. Pt. II, AVE (Prime Eqpt.) Addenda 2C (C-4) 

o 'Single Point Failure Analysis 4R [(U)R-(204)] 

o Instru. Books A & B 14S & 15S (U)S-C206, (207) 

o Electro-Interference Test Plan 26T (T-12) 

o Specification Maintenance Document 15C (C-11) 

.o Interface Specifications 28C (U) C-(209) 

Interface Maintenance Document 22C [(U)C-(205)] 

Test Procedures, SST 16T (U)T-(205) 

o Acceptance Test Procedures, AGE 15T (U)T-(205) 

o AVE Computer Software Acceptance Test Procedure 32T (U)T-(219) 

o REM/Adapter Wind Tunnel Test Plan 1T (U)T-(201) 

o ESTU Test Plan 3T (U)T-(201) 

o Design Approval (Qual.) Test Procedures 10T (U)T-(203) 

o Acceptance Test Procedures - GBPS 24T [(U)T-(205)] 

o Ground Test Plan 

DOUGLAS ITEMS: 

o CEI (Prime Equip.) Pt. II B346, B002-B074 (C-3/M-1) 

o CEI (Kdent. Item) Pt. II B079-B111 (C-8/M) 

o Detaf_ Spec. (ECC) B112--B135 (C-10/14) 

o Specification Maintenance Document (CEI's) B136 & B137 (C-11) 

o ECP's for System Requirements Change B138 (C-12) 

o ECP's for CEI's B139 & B140 (C-13) • 

o ECP's - Post FACI B141 (C-19) 

o As-Built Configuration List (AVE-CEI's) 

o CEI Computer Program Pt. II B152-3156 (UC-106) 

o Version Description Document (Computer Program) B160-B164 (UC-112) 

o Interface Document Evaluation B195 (UE-101) 

o Positional Handbook -- Computer Program B203 & B204 (UH-104) 

o Users Manual (Computer Program) B205-B209 (UH-102) 

o Syste2/Design Trade Study Reports B247 (S-5/4) 

o Electro-Interference Test Plan B282 (T-12) 

o Ground Test Plan - Acceptance B287 (UT-101) 

o Ground Test Pine - Effectiveness B288 (UT-101) 

o LM QualificiAion Test Requirements and Procedures B293 (UT-107) 

o Itm Test PLJ, (Col;v:ter Pror7a) B29%-B299 (UT-109) 

o Item Procedures (col Ler Froram) B308-B312 (U P-119) 

L L 

ronr *)"" A -Li :J.)01a] 

71_ 
NRO APPROVED FOR SECRET SPEC!AL HANDLI:'!(1 

RELEASE 1 JULY 2015 

The STD for Function 8.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. 

Specific references to contractual requriements documents by paragraphs 

number shall be provided in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, [NOTE: SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in Paragraph 3.2.2 of Part I.] except 

as follows: Due to the nature of Block 8.0, there shall be two 

different formats of RAS used in the expansion of the function. 

For the top level functions and those not describing test functions, 

the RAS, as described in Part I of this Exhibit, shall be used. 

However, for functions describing the test activities, the following 

format shall be required. 

1. SCOPE - The scope of the function shall be a narrative description of the activity to be accomplished. Included shall be 

beginning and ending points of the activity and it shall be 

written in a form that can be inserted directly into a plan. 

At each level, the detail will be as required to develop the 

next level of operations in a Functional Flow Block Diagram. 

2. PRIME OBJECTIVES - Shall be a "brief" description of the 

"prime" objectives to be accomplished. 

3. PREREQUISITE AND SERVICING REQUIREMENTS - Shall list the 

required prerequisites to be accomplished prior to start of 

the function plus the necessary servicing of the test item, 

such as water, power, liquid 02, etc. 

4. END ITEM CONFIGURATION - Shall give the detail configuration of 

the item under test. In some cases such as the Laboratory 

Module, a list of the items missing from the flight configuration 

may be used in place of a list or definition of all items in 

the configuration. 

u L spEcul Hira;i 

72 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 4[411-E-i-- SPEC IA 1_ HANDLING 

5. TEST CONFIGURATION - Shall list the AGE and Simulators required 

to perform the function. Included as a reference to this 

section will be the Schematic Block Diagram. 

6. TEST CONSTRAINTS - Shall contain design and operating constraints 

as they apply to the activity and/or equipment identified. 

Example of constraints are: 

(a) Operating cycles and time limitations on equipment. 

(b) Critical sequence of events that must be followed. 

(c) Design and operating constraints imposed by CEI Specifications and/or Applicable Military and/or Government 

standards and specifications. 

(d) Operating conditions which are hazardous in nature and 

restrict activity. 

(e) Interfaces which must be accomplished prior to initiation 

of the activity under consideration. 

(f) Time allotted to perform operation. 

7. TEST REQUIREMENTS (Operations) - Shall identify requirements on 

AGE, Facility, personnel, and shall list mandatory sequence 

necessary in performing the activities of the function. For 

lower level test functions, the requirement will be as detailed 

as necessary to define the operation or objectives to be verified by a procedure. 

In some cases, additional sections shall be added to the RAS in order 

to give a better definition of the function. An example of possible 

candidates are: 

(a) Data Requirement. 

(b) Personnel Requirement. 

(c) Man/Machine Interface. 

d. SSBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

SEC 3 K s 1.111mirin 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAI HANDLING 

3.1.8.h Task Assignment 

The Function 8.0 integration responsibility has been assigned to Douglas 

MSSD. Contributing associate contractors are General Electric, McDonnell 

Astronautics, Martin-Marietta and Hamilton Standard. Martin-Marietta 

Corporation shall integrate data from United Technology Center, Aerojet 

General Corporation, A-C Electronics Division and Spacecraft Incorporated 

and shall submit the integrated STD to the Function 8.0 Integrator. 

The MOL Program Office will furnish Agency information. 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to support the 

FFBD's and submit them to General Electric. 

Eastman Kodak STD whall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph "a" 

below to integrate General Electric and Eastman Kodak STD. 

General Electric shall perform the tasks noted in paragraph "b" below for both 

General Electric STD and for integrated General Electric/Eastman Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph "b" below in preparing and submitting STD to General Electric except for preparation of FFBD's. 

a. The Function 8.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government 

agency participation in accordance with the master schedule 

issued by the OSI. 

2. Establish contractor assignments for review, comment and 

expansion of flow diagrams and RAS's. 

3. Identify the requried timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or 

definitions reflected in the STD for Function 8.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of those involved to achieve a resolution. 

--''' QT-(1! tiAyr,1 

L. FL 1 h 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SECRFT SPECIAL FIANDLI G 

• 5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.8.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

8. Respond to requests for clarification or revision of Function 

8.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, SBD's, and TSB's in 

format specified in Part I of this Exhibit and submit on 

11x17 inch vellum to the Function Integrator. Flow diagram 

expansion and their attendant RAS and Timeline Sheet shall be 

submitted as a package for integration. 

2. Respond to requests for clarification or revision of the contributed data if discrepancies are identified during integration. 

c. MOL Program Integration Contractor (Douglas) as System Level 

Integrator of the STD shall: 

1. Review Function 8.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements; using 

as a guide the functional *cross-references incorporated in the 

STD. Compare the interfaces identified in the functional 

schematics with the interface requirements defined in the RAS's 

to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

tIr- ; 

"15 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLII;(1 

• 3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of test, acceptance and 

delivery requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

'7f; 
NRO APPROVED FOR 

RELEASE 1 JULY 201'5 

PECIALHANDL 

3.1.9 unction 9.0, "Perform Training and Perform Simulation" 

3.1.9.1 Function Description 

The objectives of this function are to define for each manned flight the 

training requirements necessary to prepare the flight crew, biomedical, and 

MCC personnel for accomplishing the assigned tasks during all phases of the 

MOL Mission. The training requirements identified shall provide the basis 

for planning academic instruction, briefings, demonstrations, formal courses, 

operation of test articles, part-task training and simulations, development 

simulations, and mission simulations. The training requirements shoUld 

encompass nominal, contingency, and emergency operations. 

An additional objective of the function is to define additional requirements 

for the simulation equipment to obtain specific technical data required for 

engineering design.to; define mission procedures, verify telemetry mode design, 

verify MCC displays and procedures, validate flight plans and mission rules, 

verify system operating concepts and timelines, exercise the AVE and MCC software, and rehearse the mission. 

All affected associate contractors and agencies shall identify and provide 

inputs to this function. 

3.1.9.2 Special Considerations 

Function 9.0, as defined herein, combines the essential aspects of Functions 9.0 

and 10.0 which were defined in the CDP. 

3.1.9.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description of 

Flight Crew, biomedical and MCC personnel training and simulation requirements. 

Coordination of training plans and simulator operations plans shall be based 

on this STD to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent 

with Function 9.0 STD include: 

, IA i` 1 1 " ''DLI 7 'r' 

.;,, 1110. v LAU 

77 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

Ser.-0! "m,icr 

L 14u 

NOTE:. The planning and requirements documents listed below are the non- 

-- DORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they 

are identified. 

Training Requirements Data (Flt. Crew) 

B234 (UQ-101) 

ORD Inputs 

B281 (UT-141) 

Orbital Support Plan 

Flight Crew Training Plan 

Mission Simulator Operations Plan 

Training Schedules 

CEI Part II Mission Simulator 

CEI Part II Flight Crew Equipment Orbiting Vehicle 

CEI Part II Laboratory Vehicle, MOL 

CEI Part I OTEF 

IFS 

ICD 

As Built Configuration List 

CEI Part I, Computer Program, LMSE 

CEI Part I, Computer Program, On Board 

CEI Part 1, Computer Program, Integrated Mission Simulator 

CEI Part II, Computer Program, LMSE 

CEI Part II, Computer Program, On Board 

CEI Part II, Computer Program, Integrated Mission, Simulator 

COmputer Program Interface Spec. (MMC) 

Computer Program Interface Spec. (MAC) 

Version Description Document, Computer Program Set On Board Computer 

Version Description Document, LMSE Computer Program 

Version Description Document, Computer Program Integrated, Mission Sim. 

Positional Handbook, Computer Program, Integrated, Mission Simulator 

Users Manual (Computer Program), LMSE 

Users Manual (Computer Program), On Board Computer 

Users Manual (Computer Program), Mission Simulator, Integrated 

Computer Program Interface Spec. LMSE MMSE 

_ • - 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

ECRF.,,11 SPECIAL HAINDLIiiii 

The STD•for Function 9.0 shall define requirements to a level of detail 

sufficient for preparation of the documents listed above and others that may 

evolve. The functional flow block diagram shall be developed to the lowest 

level at which time sequencing of the training or simulation blocks is required. 

The RAS shall contain a description of the Block, a list of training/simulation 

requirements generated by the Block, a description of the mode of training 

(lecture, exercise, etc.), a list of equipment and facilities needed, and the 

time required to accomplish the training/simulation. If simulation/training 

requirements, equipment, facilities or times are listed in another deliverable 

document, they need not be duplicated in the HAS, but specific references 

shall be given to provide traceability to those items omitted from the HAS. 

The RAS for non-training uses of the simulator should contain a description 

of the Block, the specific requirements that are generated within the Block, 

a listing of the equipment, and the time needed to satisfy the requirements. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2; however, SPO approved equivalent contractor 

prepared forms and approaches may be used in lieu of Right Hand RAS's 

specified in paragraph 3.2.2 of Part I. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.9.4 Task Assignment 

The Function 9.0 integration responsibility is assigned to Douglas MSSD. 

Contributing associates are McDonnell Astronautics, Hamilton Standard, General 

Electric and Martin-Marietta. Martin-Marietta Corporation shall integrate data 

from United Technology Center, Aerojet General Corporation, A-C Electronics 

Division and Spacecraft Incorporated and shall submit the integrated T-III STD 

to the Function 9.0 Integrator. 

Q r !-• ! 

79 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SEChLI SPECIAL HANDLINU 

General,Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the 

FFBD's for their functions and coordinate changes desired with General 

Electric. Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's 

to support the FFBD's and submit them to General Electric. 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLING 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph (a) 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph (b) below 

for both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph (b) below in 

preparing and submitting STD to General Electric except for preparation of 

FFBD's. 

a. The Function 9.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government agency participation in accordance with the master schedules 

issued by OSI. 

2. Establish contractor and government agency assignments for 

review, comment and expansion of flow diagrams and RAS's. 

3. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans or 

definitions reflected in the STD for Function 9.0. The 

Function Integrator shall inform the affected organizations 

of identified problems, request revised inputs and, if necessary, 

call a meeting of those involved to achieve a resolution. 

4. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors/agencies concurrent 

with submittal for system level integration to the NPI Contractor 

and OSI. 

5. Respond to requests for clarification or revision of Function 

9.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

6. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.9.3 above. 

S E C SPECiAL 1:;n4I1DLING 
JLUi( 'e1-3ECIAL HANDLli iG 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

b.' Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, and timelines in format specified 

in Part I of this Exhibit and submit on 11x17 inch vellum to 

the Function Integrator and to the OSI. Flow diagram expansion 

and its attendant RAS shall be submitted as a package for 

integration. 

2. Respond to requests for clarification or revision of the contributed data if discrepancies are identified during integration. 

c. MOL Program Integration Contractor as System Level Integrator 

of the STD shall: 

1. Review Function 9.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and stated requirements, using as a guide the functional crossreferences incorporated in the STD. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, MPI shall recommend OSI approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of training and simulation 

requirements. 

2. Approve Function Integrator STD for use as system level 

integrated data. 

1,2) KT ..2 t

81 
NRO APPROVED FOR LT_ SPECIAL HANDLING 

RELEASE 1 JULY 2015 

3.1.10 •Function 10.0, "Perform Mission Simulations" 

NOTE: Function 10.0 HAS BEEN COMBINED WITH Function 9.0. 

SE UL _. 1"1 ; 

62 
NRO APPROVED FOR 

SLCV, SPECIAL HANDW. 

RELEASE 1 JULY 2015 

3.1.11 Function 11.0, "Maintain System" 

3.1.11.1 Function Description 

These functions include all preventive and corrective maintenance of AVE, 

AGE, AAE, and facilities, including ground maintenance before and during 

flight, and on-orbit maintenance of the Orbiting Vehicle. In the case of 

corrective maintenance, only the maintenance analysis subsequent to receipt 

of malfunction detection shall be accomplished as a part of this function. 

Malfunction detection requirements (as well as redundant, alternate, or 

degraded methods of operation) shall be analyzed as a part of basic functions 

covered in other functions, as appropriate. In the case of preventive 

maintenance, only those requirements that are not a true prerequisite 

(i.e., "in series") to an "operational" function shall be analyzed as part 

of this function. "In series" preventive maintenance requirements shall 

be analyzed as a part of the related basic "operational" functions. 

This function starts after receipt of the first contract end item at the 

using site and terminates with completion of normal retrieval operations. 

3.1.11.2 Special Considerations 

The following interfaces with other functions have been established: 

1. Function 11.1 (Perform Primary Maintenance) interfaces with 

Function 7.8 (Perform Recycle Operations). This interface is required 

to assure a transition from the operational flow to the maintenance 

flow and return to the operational flow. The result is a maintenance 

flow which includes both operational and maintenance functions; 

when the same function is required for both Function 11.1 and 7.8, 

it shall be included in Function 7.8 and referenced in Function 11.1. 

2. Function 11.2 (Perform On-Orbitalainten 

Function 4.o (Perform On-Orbit Objectives) to assure a transition 

from the on-orbit maintenance. 

3.1.11.3 Data RequirsHents 

The STD for this function shall be used as a baseline reference description 

of maintenance functions and requirements. Detailed discussions and 

coordination of maintenance problems and solutions that affect design and 

define equipment requirements shall be based on Function 11.0 STD where 

practicable. 0 Lt./ !.). 1, k.:.Isi

, 

t

d

n. 

83 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL HANDLING 

Planning and requirements documents which must be based on and/or be consistent with Function 11.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the non-DORIAN 

versions. This list also applies to their DORIAN counterparts, as 

applicable. DORIAN-only documents will be added as they are identified. 

Or: r0 r} ! 11 17.-!0 0: LUIi-AL 
E.T. S _1 pECI'L 1 A -"DLrG 11.0 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS: 

o J

• 

ECP's for System Requirements Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's after FACI A018 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o Flight Crew Handbook (LV/Gemini B) A028 [(U)H-602] 

o Maintenance Requirements Data A031 [(U)L-600] 

o Maintenance Kit Manual A033 [(U)L-602] 

o Flight Operations Crew Personnel Training Plan A038 [(U)Q-601] 

o Flight Crew Safety Plan A040[(U)S-600] 

o System/Design Trade Study Report A041 (S-54) 

o PSA Task Analysis A045 HU)S-6051 

o PRD Inputs A053 [(U)T-603] 

MARTIN ITEMS: 

o Specification Maintenance Documents C2 & C19 (C-11/M) 

o ECP's for System Requirements Change C3 & C4 (C-12) 

o ECP's for CEI's Pt. I C5 (C-13/M) 

o ECP's for CEI's Pt. II C6 (c-1914) 

o Specification Maintenance Document C19 (C-11/M) 

o PRD Input - Cahnge T9 (T-21/M) 

o Flight Operations Crew Training Plan 

GENERAL ELECTRIC ITEMS: 

o SCN B044 (C-11) 

o ECP's for CEI's B0h6 (C-13) 

o ECP's for System Requirements Change B047 (C-12) 

o ECP's after FACI B048 (C-19) 

o Reliability/Maintenance Measure. Plan B061 [(U)R-402] 

o Reliability/Maintensnce Apportion Report B063 [(U)R-403] 

o Mission Crit. Comp. Plan Report B064 [(U)R-404] 

o Failure Mode and Effectiveness Analysis B068 [(U)R-408] 

o Reliability Demonstration Study B070 [(U)R-410] 

o Hazard Analysis 130Y5 [(U)S-404] 

o Power Status Eeport B076 [(U)S-Al05] 

o Sy:Acia/ Posir:x S'.;ud Rep t P0Y9 (2-51.) 

o Rehearse]. Pi a% (Input) B104 [(U)T-1401] 

o Launch 0.i J. t:icx.bSuppc.xt vi.sd 1.ep:rt En? [(U)T-h11 ] 

r n S c' r L i 1:‘•11 

L,lj;; 
! ". G 

11.0 

NROAPPROVEDFOR 

7 ocGRLT SPECIAL HANDLING 

RELEASE 1 JULY 2015 

GENERAL ELECTRIC ITEMS: (Continued) 

o Flight Operations Crew Training Plan 

o Flight Crew Handbook Laboratory Vehicle 

MCDONNELL ITEMS: 

o Program Requirements Document 19T (U)T-(116) 

o Effectiveness Assessment Plan 3R [(U)R-(203)] 

o AGE Plan 5M [(U)M-(203)] 

o ECP's for CEI's 16C (C-13) 

o ECP's General (after FACI) 18C (C-19) 

o Failure Mode and Effectiveness Analysis 5R [(U)R-(205)] 

o ECP's for System Requirements 27C (C-12) 

o S/C Instru. System Report 13S (U)S-(205) 

o Tech. Pub. - SC Famil. Manual 1H [(U)H(201)] 

o Specification Maintenance Document 15C (C-11) 

o AVE Preventive Maintenance Rat. Summary 9R (R-209) 

o Flight Crew Technical Volume 

o Task Analysis Data (Crew Training (U)S-(219) 

o Ground Safety Plan (Inputs) 

o Tech. Pub. - GB Proc. Sim. Ops. Handbook 2H [(U)H(201)] 

o Tech. Pub. - AGE Ops. and Service Manual 4H [(U)H(201)] 

o Flight Operations Crew Personnel Training Plan 

DOUGLAS ITEMS: 

o Specification Maintenance Document (CEI's) B136 & B137 (C-11) 

o ECP's for System Requirements Change B138 (C-12) 

o ECP's for CEI's B139 &. B140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

o Interface Document Evalution B195 (UE-101) 

o Maintenance Dita Reports B213 (UL-101) 

o Traininr: Requircr:lents Data (Plight Crew) 13234 (UQ-101) 

o System/Design Trade Study Reports B247 (S-54) 

o. System Safety Plan (SSP) B259 & B260 (US-101) 

o Mission Status Sumnary B277 (US-121) 

o Grouna Safety Flan 13279 (US-125) 

o Inns B261 (UT-141) 

o Plan. - Lffcctiver ss B23B (UT-107.) 

o L365 (UT-116) 

r 

L t -•• L:1 •! tif 1• 
11.0 

NROAPPROVEDFOR SPECIAL 1-1,V,DLING 

RELEASE 1 JULY 2015 - 

DOUGLAS ITEMS: (Continued), 

o *Flight Operations Crew Training Plan Input 

o Flight Crew Handbook Laboratory Vehicle 

o Flight Crew Safety Plan 

o Quick Look Post-Operations Report 

AGENCY ITEMS: 

o Program Support Plan (PSP) 

o Orbital Support Plan (OSP) 

o Operations Requirements (OR), Pt. I and Pt. II 

o System Test Objectives 

o Operations Directive 

ti L. (a . SPECIAL 
SPECIAL HANDLING 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

The STD, for Function 11.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. 

Specific references to contractual requirements documents by paragraph 

number shall be provided in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SP0 approved equivalent contractor 

prepared forms and approaches may be used in lieu of Right Hand RAS's 

specified in Paragraph 3.2.2 of. Part I. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.11.4 Task Assignment 

The Function 11.0 integration responsibility has been assigned to Douglas 

MSSD. Contributing associate contractors are McDonnell Astronautics, 

Hamilton Standard, General Electric, and Martin-Marietta. Martin Marietta 

Corporation shall integrate data from United Technology Center, Aerojet 

General Corporation, A-C Electronics Division and Spacecraft Incorporated 

and shall submit the integrated T-IIIM STD to the Function 11.0 Integrator. 

For the DORIAN portions, the following shall apply: 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the FFBD's 

for their functions and coordinate changes desired with General Electric. 

Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to support the 

FFBD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph "a" 

below to integrate the Eastman Kodak and General Electric STD. 

-6176t-14, -1-

66 SPECIAL NANDI IK 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 ---6-6-PrET-SPECIAL HANDLING 

General.Electric shall perform the tasks noted in paragraph "b" below for 

both General Electric STD and for integrated General Electric/Eastman Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph "b" below in preparing and submitting STD to General Electric except for preparation of FFBD's. 

a. The Function 11.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government 

agency participation in accordance with the master schedule 

issued by the OSI. 

2. Establish contractor assignments for review, comment and 

expansion of flow diagrams and RAS's. 

3. Identify the required timelines and make assignments for preparation. 

4. Review contributed data and comments received from pariticpants 

to identify incompatibilities in requirements, plans, or definitions reflected in the STD for Function 11.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs, and, if necessary, call a 

meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns on 

RAS's per paragraph 3.1.11.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as practicable after the function integration of each 

STD expansion has been completed, the Function Integrator shall 

release copies to participating contractors/agencies concurrent 

with submittal for system level integration to the MPI Contractor 

and OSI. 

8. Respond to requests for clarification or revision of Function 

11.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, SBD's, and TSR's in 

format specified in Part I of this Exhibit and submit on 

89 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLIV 

• 11 X 17 inch vellum to the Function Integrator and to the OSI. 

Flow diagram expansion and their attendant RAS and Timeline 

Sheet shall be submitted as a package for integration. 

2. Respond to requests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

c. MOL Program Integration Contractor as System Level Integrator of 

the STD shall: 

1. Review Function 11.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in the 

STD. Compare the maintenance interfaces identified in the 

functional schematics with the interface requirements defined 

in the RAS's to verify adequacy of interface definition. 

2. Inform the appropriate Function. Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of maintenance requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

f; rk D T QD}Tr

L.Lit c.; ill nil tin; 1/ 1 i(1,- 

90 
NRO APPROVED FOR it L. .1 

RELEASE 1 JULY 2015 

3.1.12. Function 12.0, "Perform Mission Control" 

3.1.12.1 Function Description 

This function begins at the start of prelaunch activities and terminates 

with the release of all of the recovery forces. 

Each associate contractor shall develop his mission control and associated 

requirements as part of his participation in the analysis of requirements for 

the assigned functions derived from the overall system function breakdown 

described in Section 3.1 of Part I of this Exhibit. Included are Mission 

Control requirements for the processes of monitoring, receiving and/or 

transmitting infromation bearing on the flight, or on the readiness to 

commence or terminate flight, and the associated requirements imposed on 

all of the networks and stations involved. This includes the requirements 

for control and voice communications, weather and sea condition forecasts, 

tracking, telemetry, command, and data recording, transmission, and reduction. 

Status reporting and displays, and real-time mission evaluation requirements 

shall also be developed. 

3.1.12.2 Special Considerations 

The analysis effort shall be oriented to define the SCF and range support 

requirements only in sufficient depth to permit extraction of requirements 

as direct inputs to the appropriate support documentation specified in the 

MOL Documentation Plan: No reference to methods of implementation shall 

be included. This function overlaps Function 7.0 from the start of prelaunch activities. During this period, Function 12.0 requirements shall 

be those for MCC and MCC to VAFB interface. 

3.1.12.3 Data Requirements 

The STD for this function will be used by government agencies and shall be 

used by participating associate contractors as a baseline reference 

description for Mission Control operations. Detailed discussions for 

coordination of operational plans and technical interchanges for design 

definition of equipment required, shall be based on this STD to the extent 

practicable. 

rA'n 

• ,•-_. •-■ 

91 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRI I SPECIAL HANDLING 

Planking and requirements documents which must be based on and/or be 

consistent with the Function 12.0 STD includes the following: 

NOTE: The planning and requirements documents listed below are the nonDORIAN versions. This list also applies to their DORIAN counterparts, as applicable. DORIAN-only documents will be added as they are 

identified. 

(V) 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECULT_ SPECIAL HANDLING 

12.0 

HAMILTON STANDARD ITEMS: 

o .ECP's for System Requirement Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A018 (C-19) 

o Spec. Maintenance Document A019 (C-11) 

o Flight Directors Handbook A029 [(U) H - 604] 

o Flight Operations Crew Personnel Training Plan A038 [(U) Q - 601] 

o System/Design T S Report A041 (S-54) 

o PRD Inputs A053 [(U) T - 603] 

MARTIN ITEMS: 

o Spec. Maintenance Documents C2 & C19 (C-11/M) 

o ECP's for System Requirement Change C3 & C4 (C-12) 

o ECP's for CEI's Pt. I C5 (C-13/M) 

o ECP's for CEI's Pt. II C6 (C-19M) 

o Spec. Maintenance Document C19 (C-11/M) 

o PRD Input - Change T9 (T-21/M) 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o FliEht Operations Crew Training Plan 

o Flic:It Directors Handbook 

GENERAL ELECTRIC ITEMS: 

o Version Description Document B035 ((U) C - hold 

o Positional Handbook B037 [(U) H - 401] 

o SCN B0h4 (c-ii) 

o ECP's for CEI's B046 (C-13) 

o ECP's for System Requirement Change B047 (C-12) 

o ECP's After FACI B048 (C-19) 

o Failure Mode & Effects Analysis B068 [(U) R - 408] 

o Reliability Demonstration Study B070 [(U) R - 410] 

o System/Design T S Report B079 (S-54) 

o Rehearsal Pim (Input) B104 [(U) T - 407] 

o RED Input B110 [ (U) - 1109] 

• Flinht SITIJort Study Re-.)ort B111 (N) T - 410] 

rtr--ro 1; ro 

93 
NRO APPROVED FOR S L C i E: SPECIAL HANDLING 12.0 

RELEASE1JULYM5 

GENERAL ELECTRIC ITEMS: ,(Continued)', 

o Launch Operations'Support Study Report B112 [(U) T - 411] 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

o Flight Operations Crew Training Plan 

o Flight Directors Handbook 

o Mission Simulator Operations Handbook Vol. II Simulator Handbook 

o Command and Operations Handbook 

MCDONNELL ITEMS: 

o Manned Recovery Requirement Document - 18T [(U) T - (207) - (221)] 

o Program Requirement Document - 19T [(U) T - (116)1 

o Orbital Requirement Document - 17T [(U) T 221) (Manned)1 

o ECP's for CFI's - 16C (C-13) 

o Manned Flight Vehicle Time Line - 26S [(U) (S-22) 

o ECP's General (After FACI) - 18C (C-19) 

o Failure Mode & Effect. Anal. - 5R [(U) .R - (205)] 

o ECP's for System Requirement - 27C (C-12) 

0 CEI Det. Specs. Part II, AGE (PrirLe Eqpt.) - 3C TO10C, (C-3) 

0 Version Description Document, CPCEI, GBPS - 31C [(U) C - (214)] 

0 Instrumentation Books A & B - 145 & 155 [(U) S - (206), (207)] 

0 Specification Maintenance Document - 15C (U) (C 11) 

Flight Dir. HE 

o Flight Crew HE (Laboratory Vehicle) 

o Flight Crew HE (Gemini B) 

o Flight Data File 

o Recovery HE - Manned 

o System Test Objectives (STO) 

o Quick Look Ascent & Orbit Report 

o Quick Look. Post Operations Report 

o Guidance Simulation Definition 12R [(0) R 212] 

o Flight Operations Crew Personnel Training Plan 

o Mission Simulator Operations Handbook, Volum II 

5L , 

Q2Dr:ril r 1 r.!t-11 iror 

9'1 
NROAPPROVEDFOR -S-EN--Ei SPECIAL HANDLING 

12.0 

RELEASE 1 JULY 2015 

DOUGLAS ITEMS: 

-0 'Specification Mairitenance Document (CEI's) B136 & 8137 (C-11) 

o ECP's for System Requirement Change B138 (C-12) 

o ECP's for CEI's B139 & 140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

o CEI Computer Program, Pt. II B152 & B156 (UC-106) 

o Computer Program IFS B158 & B159 (UC-110) 

o Version Description Document (Computer Program) B160 & B164 (UC-112) 

o Interface Document Evaluation B195 (UE-101) 

o Positional Handbook - Computer Program B203 & B204 (UH-101) 

o- Users Manual (Computer Program) B205 - B209 (UH-102) 

o System/Design Trade Study Reports B247 (S-54) 

o System Safety Plan (SSP) B259 & B260 (US-101) 

o Mission Status Summary B277 (US-121) 

o ORD Inputs B281 (UT-141) 

o PRD Inputs B305 (UT-116) 

Item Test Proc..(Computer Program) B308 B312 . (UT-119) 

o Flight Operations Crew Training Plan Input 

o Flight Directors Handbook Input 

o Mission Simulator Operations Handbook Vol. I LV Proc. 

o Mission Simulator Operations Handbook Vol. II Simulator Handbook Input 

o Command. and Operations Handbook Input 

o Quick Look Ascent & Orbit Report 

o Quick Look Post-Operations Report 

AGENCY ITEMS: 

o Program Support. Plan (PSP) 

o Orbital Support Plan (OSP) 

o Reco-..ery Support Plan (RSP) 

o Manned Reovry Support Plan (MRSP) 

o Operations Requirement (OR) Pt. I, Pt. II 

o Mission Simulator Operations Handbook Vol. II Simulator Handbook Input 

o System Test Objectives 

o Operations Directive 

o Flight Termintion System (Its.) Report. 

o Recovery Safet:y Ply 

o Trajcctories Ascent 

r 

S 

i" `: 

L. rLuti 1 , )Lii iu r) O.' AT 1_1 r, 7"r), vorl 

95 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRET SPECIAL 1-1,',i'DLING 

The STD for Function 12.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. Specific references to 

contractual requirements documents by paragraph number shall be provided 

in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in Paragraph 3.2.2 of Part I. 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.3.4 Task Assignment 

The Function 12.0 integration responsibility has been assigned to Douglas 

MSSD. Contributing associate contractors are General Electric, McDonnell 

Astronautics, Hamilton Standard and Martin Marietta. Martin Marietta 

Corporation shall integrate data from United Technology Center, Aerojet 

General Corporation, A-C Electronics Division and Spacecraft Incorporated 

and shall submit the integrated T-IIIM STD to the Function 12.0 Integrator. 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the 

Fi'BD's for their functions and coordinate changes desired with General 

Electric. Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to 

support the MD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph (a) 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph (b) below 

for both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

r 

 it ULU' 

0-1 -nut{ I torl t !r 114 iL Li 

96 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECIAL HANDLING 

Eastman Kodak shall perform the tasks noted in paragraph (b) below in 

preparing and submitting STD to General Electric except for preparation of 

FFBD's. 

a. The Function 12.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/govern—

ment agency participation in accordance with the master 

schedule issued by the OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. 

3. Identify the requried timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requriements, plans, or 

definitions reflected in the STD for Function 12.0. The 

Function Integrator shall inform the affected organizations of 

identified problems, request revised inputs and, if necessary, 

call a meeting of those involved to achieve a resolution. 

5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.12.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed, the Function Integrator shall 

release copies to participating contractors/agencies concurrent 

with submittal for system level integration to the MPI 

Contractor and OSI. 

8. Respond to requests for clarification or revision of Function 

12.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's, timelines, SBD's, and TSR's in 

format specified in Part I of this Exhibit and submit on 11x17 

c,F., 77r1 

• 4 \-). 

9'7 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SECRE1 SPECIAL HIMMG 

inch vellum to the Function Integrator and to the OSI. Flow 

diagram expahsion and their attendant RAS and Timeline Sheet 

- shall be submitted as a package for integration. 

2. Respond to requests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

c. MOL Program Integration Contractor (Dougals) as System Level 

Integrator of the STD shall: 

1. Review Function 12.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using 

as a guide the functional cross-references incorporated in the 

STD. Compare interfaces identified in the functional schematics 

with the interface requirements defined in the RAS's to verify 

adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to 

properly guide the analysis and definition of mission control 

requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

S ";•••:1 olr■ 

r 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 S L C sriLr,;;,\L 

3.1.13' Function 13.0, "Perform Abort Operations" 

3.1.13.1 Function Description 

This function consists of the operations to be performed in the event of 

imminent or existing MOL System malfunctions that prevent the continuance 

of the normal mission. 

The function objective is to insure the safety of the crew and, where 

possible, to fulfill a modified mission objective. This may involve either: 

(1) crew escape, (2) crew escape with DRC's, or (3) continuing a shortened 

mission. 

The function shall include all abort situations in the KA mode which can occur 

at any time subsequent to the ingress of the Flight Crew into the Gemini B. 

The function shall include all abort situations in the KB mode which can 

occur subsequent to the start of the final countdown. The function starts 

with receipt of a signal indicating an incipient or existing failure anywhere in the Flight Vehicle and the need for emergency termination of the 

mission or initiation of emergency operations. In the principal flight 

modes of operation, the Flight Crew will make the final abort decision. 

The function termination is dependent upon the mode of abort operation. In 

circumstances that allow a modified mission objective, Function 13.0 will 

end with the achievement of safe orbit. For those anomalies that require 

crew escape operations, Function 13.0 terminates after landing and upon 

arrival of useful assistance to the crew, including retrieval or verification 

of positive disposal of mission revealing data and equipment. 

3.1.13.2 Special Considerations 

Definition of specific requirements for crew escape equipment, personnel 

operations and capabilities, and timing requirements shall be correlated 

with the AVE/AAE/AGE/crew requirements and constraints developed in Functions 

3.0, 4.0, 5.0, 6.0, 7.0 and 12.0/ground crew. 

In the development of Function 13.0 STD, appropriate Functions 3.0, 4.0 

and 5.0 STD shall be incorporated by reference in the 13.0 flow diagram 

when directly applicable. 

S

r r■ 

kJ I\ 

99 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 F. C ► L T SPECIAL HANDLING 

3.1.13.3 Data Requirements 

The STD for this function will be used by the government agencies and shall 

be used by the associate contractors as a baseline reference description of 

abort operations. Detail discussions for coordination of operational plans 

and technical requirements for design definition shall be based on this STD 

to the extent practicable. 

Planning and requirements documents which must be based on and/or be consistent with the Function 13.0 STD include the following: 

NOTE: The planning and requirements documents listed below are the non-DORIAN 

versions. This list also applies to their DORIAN counterparts, as 

applicable. DORIAN-only documents will be added as they are identified. 

:;:r)i 

100 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

HAMILTON STANDARD ITEMS: 

L. U ti L.1. SPECIAL 14ANDLING 13.0 

o 'ECP's for System Requirement Change A016 (C-12) 

o ECP's for CEI's A017 (C-13) 

o ECP's After FACI A-18 (C-19) 

o Specification Maintenance Document A019 (C-11) 

o Flight Crew Handbook (LV/Gemini B) A028 [(U) H - 602] 

o Flight Directors Handbook A029 [(U) H - 604] 

o Technical Publications - Recovery Handbook A030 [(U) H - 605] 

o MRED A032 [(U) L - 601] 

o Flight Operations Crew Personnel Training Plan A038 [(U) Q - 601] 

o Flight Crew Safety Plan A040 [(U) S - 600] 

o System/Design T S Report 

o PSA Task Analysis A045 [(U) S - 605] 

o PRD Inputs A053 [(U) T - 603] 

MARTIN ITEMS: 

o Specification Maintenance Document C2.& C19 (C-11/iii) 

o ECP's for System Requirement Change C3 & Ch (C-12) 

o ECP's for CEI's Pt. I C5 (C-13/M) 

o ECP's for CEI's Pt. II C6 (C-19M) 

o Specification Maintenance Document C19 (C-11/A) 

o Missile Explosive Comp. Technical Data Sheet R1 (H-h) 

o Range Safety Report Shl (S-3h/M) 

o PRD -Cnput - Change T9 (T-21/M) 

o Flight Crew Handbook - Gemini B 

GENERAL ELECRIC 

o SCN B044 (C-11) 

o ECP's for CEI's B046 (C-13) 

o ECP's for System Requirement Change B047 (C-12) 

o After FACI. B048 (C-19) 

o Failure Mode & Effects Analysis B068 [(U) R -- 408] 

o Demonstration Study B070 [(U) S 410] 

o Hazard Ana].ysif B075 [(Li) S 404] 

o Power Status Report B076 [(U) S 405] 

o T S RcTorts B079 (S-54) 

; 0 L. u EE 

101 
NROAPPROVEDFOR SEC Eff 1),ECIAL. HANDLIN .13.0 

RELEASE 1 JULY 2015 

GENERAL ELECTRIC ITEMS: (Continuedr4 

o :Rehearsal Plan (Input) B104 [(U) T - 407] 

o Flight Operations Support Study Report B111 [(U) T - 41D] 

MCDONNELL ITEMS: 

o Manned Recovery Requirement. Document 18T [(U) T (207) (221)] 

o Program Requirement Document 19T [(U) T (116)]. 

o GB Flight Effectiveness Model Report 7R f(U) R - (207)] 

o Orbital Requirement Document 17T [(U) T - 221)(Manned)] 

o Eject. Seat Function Test Plan - 4T [(U) T - (201)] 

o ECP's for CEI's - 16C (C-13) 

o Manned Flight Vehicle Time Line 265, (U) (S-221) 

o ECP's General (After FACT) 18C (C-19) 

o. Failure Mode & Effectiveness Analysis 5R [(U) R - (205)] 

o ECP's for System Requirement 27C (C-12) 

o Version Description Document CPCEI GBPS - 31C ((U) C - (214)] 

o S/C Instru. System Report 135 [(U) S - (205)] 

o Single Point Failure Analysis 4R [(U) R - (204)] 

o Explosive Component Technical Data Sheet 18S ((U) S (209)1- 

o Load Analysis - Elect. Eqpt. 12S [(U) S (204)]. 

o Instrumentation Books A & B 145 & 155 [(U) S (206), (207)] 

o Effectiveness Frog. Status Report 1R [(U) R (201)]' 

o Specification Maintenance Document 15C (U) (C-11) 

o Interface Specifications 28C [(U) C (209)1 

o Interface Maintenance. Document 22C [(U) C (205)] 

o Aero Data Book 215 [(U) S - (212)] 

o Internal Crew Transfer Testing 0 - G 

o Update Communication System Technical Baseline 

o Task Analysis Data (Crew Training)(U) S-(219) 

o Flight Dir. 

o Flight Crew JIB (Laboratory Vehicle) 

o Flight Crew EB (Gemini B) 

o Flight Data File 

o Recovery --- Manned 

o ProliTAirr.r:i Countdown 1:nual - Inputs: 

o Sy5.;tm Test 0.6jctives (STC) 

Ili-AP; 01-11'0..1 
NROAPPROVEDFOR 

Z) t:(J1-(Li SOECIALHANDLIn 13.0 

RELEASE 1 JULY 2015. 

MCDONNELL ITEMS: (Continued) 

o Ground Safety Plah (Inputs) 

,o Range Safety Report 

o Electrical System Schematics (ESS) 

o Structural Design Loads 11S [(U) S - (203)] 

o Flight Operations Crew Personnel Training Plan 

o Flight Crew Safety. Plan 

o Flight Termination System (Fts) Report 

o Radio Frequency Allocation (RFA) Request 

DOUGLAS ITEk,S: 

o Specification Maintenance Document (CEI's) B136 & B137 (C-11) 

o ECP's for System Requirement Change B138 (C-12) 

o ECP's for CEI's B139 & B140 (C-13) 

o ECP's - Post FACI B141 (C-19) 

o Interface Documentation Evaluation B195 (UE-101) 

o Electrical System Schematic B197 (UE-103) 

o System/Design Trade Study Reports B247 (S-54) 

o Explosive Comp. Technical Data Sheet B268 (US-111) 

o Mission Status Summary B277 (US-121) 

o ORD Inputs B281 (UT-141) 

o PRD Inputs B305 (UT-116) 

o Range Safety Report 

o Radio Frequency Allocation (RFA) Request B335 (AFPI 7-4067) 

AGEUCY ITEMS: 

o Program Support Plan (PSP) 

o Orbital Support Plan (OSP) 

o Recovery Support Plan (ESP) 

o Manned Recovery Sen:,ort Plan (MRSP) 

o OperAions Requirements (OR) Pt. I, Pt. II 

o System Test Objectives 

o Openttions Directive 

o Flight TerviLation System (F 5) Report 

o Recocrery Safety Plan 

L 'a 0- )L1 hi 

103 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 L. ":Ern.1-1WALING 

The STD for Function 13.0 shall define requirements to a level of detail 

sufficient to provide a requirements source for preparation of the documents listed above and others that may evolve. When functions are expanded 

to amplify the definition of operational sequences and interfaces beyond 

this level of detail, the Left Hand RAS shall be limited to the function 

description and interface requirement. Emphasis shall be placed on the 

definition of operational activities and operational interfaces between 

Launch Operations, Flight Vehicle, Mission Control and Recovery Forces. 

Specific references to contractual requirements documents by paragraph 

number shall be Shown in the appropriate RAS column. 

STD shall be prepared using the procedures and formats of Part I of this 

Exhibit, as follows: 

a. FFBD's per paragraph 3.2.1. 

b. RAS's per paragraph 3.2.2, however, SPO approved equivalent 

contractor prepared forms and approaches may be used in lieu of 

Right Hand RAS's specified in Paragraph 3.2.2 of Part I. (NOTE: 

LH RAS's for procedural functions may be limited to a function 

description and interface requirements, as appropriate.) 

c. TLS's per paragraph 3.2.3. 

d. SBD's per paragraph 3.2.4 (Reference Part II, Section 3.2). 

e. TSR's per paragraph 3.2.5, or comparable contractors Design Note 

or Technical Note format. 

Interface coding, furnished in Appendix A of Part II, shall be incorporated 

in the RAS per paragraph 3.2.2 of Part I of this Exhibit. 

3.1.13.4 Task Assignment 

The Function 13.0 integration responsibility has been assigned to McDonnell 

Astronautics (MCASTRO). Contributing associate contractors are Douglas 

MSSD, General Electric, Martin-Marietta, Hamilton Standard and the OSI. 

Martin-Marietta Corporation shall integrate data from United Technology 

Center, Aerojet General Corporation, A-C Electronics Division and Spacecraft 

Incorporated and shall submit the integrated T-IIIM STD to the Function 13.0 

Integrator. 

The Function Integration responsibility assigned to McDonnell Astronautics 

Company above shall be for non-DORIAN requirements only. In this case, 

Eastman Kodak generated STD shall be integrated with General Electric STD 

G a Z. 

104 
S:E11:11 . -11V,I)LING 

by Genpral Electric. The resulting integrated STD shall be suitably altered 

by General Electric to remove its DORIAN classification while still retaining 

interfacing requirements before submission to McDonnell Astronautics. 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

r 

r' 1 1-1 1 lAirN 

1014A 
NRO APPROVED FOR R SRECIAL HANDLING 

RELEASE 1 JULY 2015 

The Function Integration responsibility for the DORIAN portions of 

Function 13.0 is assigned to Douglas MSSD. Contributing associate 

contractors are General Electric and Eastman Kodak. As Function Integrator, 

Douglas shall perform the tasks noted in paragraph "a" below for the DORIAN 

portions. 

General Electric shall prepare the FFBD's to include both the General 

Electric and Eastman Kodak functions. Eastman Kodak shall verify the 

FFBD's for their functions and coordinate changes desired with General 

Electric. Eastman Kodak shall prepare RAS's, TLS's, SBD's, and TSR's to 

support the FFBD's and submit them to General Electric. 

Eastman Kodak STD shall be integrated with General Electric STD by General 

Electric. General Electric shall perform the tasks noted in paragraph "a" 

below to integrate the Eastman Kodak and General Electric STD. 

General Electric shall perform the tasks noted in paragraph "b" below for 

both General Electric STD and for integrated General Electric/Eastman 

Kodak STD. 

Eastman Kodak shall perform the tasks noted in paragraph "b" below in preparing and submitting STD to General Electric except for preparation of 

.613's. 

a. The Function 13.0 Integrator shall: 

1. Prepare, coordinate and issue schedules for contractor/government 

agency participation in accordance with the master schedule issued 

by the OSI. 

2. Establish contractor assignments for review, comment, and 

expansion of flow diagrams and RAS's. This shall include coordination of contractor definitions of functional abort requirements. 

3. Identify the required timelines and make assignments for 

preparation. 

4. Review contributed data and comments received from participants 

to identify incompatibilities in requirements, plans, or 

definitions reflected in the STD for Function 13.0. The Function 

Integrator shall inform the affected organizations of identified 

problems, request revised inputs and, if necessary, call a 

meeting of those involved to achieve a resolution. 

1!^^M11%1(% 

riiik!)010). 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRET SPECIAL HANDLING 

• 5. Determine and insert interface coding in appropriate columns 

on RAS's per paragraph 3.1.13.3 above. 

6. Prepare STD for distribution in accordance with paragraph 3.3 

of Part II of this Exhibit. 

7. As soon as possible after the function integration of each STD 

expansion has been completed.,the Function Integrator shall 

release copies to participating contractors concurrent with 

submittal for system level integration to the MPI Contractor 

and OSI. 

8. -Respond to requests for clarification or revision of Function 

13.0 STD if discrepancies are identified during system level 

integration. Coordinate as required. 

b. Contributing Associate Contractor Tasks: 

1. Prepare flow diagrams, RAS's and timelines in format specified 

in Part I of this Exhibit and submit on 11x17 inch vellum to 

the Function Integrator and to the OSI. Flow diagram expansion 

and their attendant RAS and Timeline Sheet shall be submitted 

as a package for integration. 

2. Respond to reauests for clarification or revision of the 

contributed data if discrepancies are identified during 

integration. 

c. MOL Program Integration Contractor (Douglas) as System Level 

Integrator of the STD shall: 

1. Review Function 13.0 STD against other STD to identify possible 

inconsistencies or incompatibilities in functional descriptions 

and timing, defined interfaces and stated requirements, using as 

a guide the functional cross-references incorporated in the STD. 

Compare the abort interfaces identified in the functional 

schematics with the interface requirements defined in the RAS's 

to verify adequacy of interface definition. 

2. Inform the appropriate Function Integrator of discrepancies, 

coordinate corrective action, and request OSI resolution, if 

required. 

n r i ) 

lof; 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRET SPECIAL HANDLING 

3. When the submitted STD is considered consistent across all 

related functions, the MPI Contractor shall recommend OSI 

approval. 

d. The OSI shall: 

1. Resolve inter-contractor/agency issues as necessary to properly 

guide the analysis and definition of abort requirements. 

2. Approve and validate Function Integrator STD for use as system 

level integrated data. 

1") 

• 

107 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SECRET SPECIAL HANDLING 

3.2* SCHEMATIC DIAGRAMS 

Schematic diagrams relate system elements or segments, rather than mission 

functions. An integrated set of schematic diagrams is required to identify 

inter-segment and intra-segment interfaces from the MOL System level down 

to the subsegment or subsystem level. The schematics shall identify interfaces between all system elements (equipment, personnel, facilities and 

software or documentation) using a systemwide codification which systematically identifies each system segment and its sub parts. See Addendum A of 

Part II for coding definition. The code is unique and permits schematic 

diagram traceability from the top down or the bottom up. Traceability of 

identified interfaces to interface requirement definition documents including 

the system specification, RAS's, CEI's, and IFS's shall be provided. See 

Figure 1 for sample. 

The schematics which have been prepared for selected subsystems or subsegments shall be integrated into the complete tree of MOL System schematics 

(system level) by the MPI Contractor. Various formats of schematics have 

been employed in their preparation. It is mandatory that the schematics at 

each lower level be prepared in a manner that makes it possible to relate 

the system level schematics to any and all lower level schematics which have 

been or may be generated within a given segment. The prime objective is to 

provide visibility into the composition of the system and its component 

elements. 

3.2.1 MOL System Top Level Schematic Diagram 

For the purpose of schematically presenting the composition of the MOL 

System, the system level schematic diagram, Figure lA, identifies the interface relationships between the basic segments. Figure lA supersedes the 

overt system level schematic diagram, Figure 9 in Part I of this Exhibit, 

and shall be used in all DORIAN program definition. Unique identification 

of each physical entity precludes the incorporation in the system schematics 

of a segment such as the "Orbiting Vehicle," which is actually a composite 

of parts of the basic segments. For the same reason, the "Mission Simulator 

Segment" schematic is excluded. 

oFCREI, SPECIAL G 

10S 
N A N g . N g 

O 

lIJ 

CC W 

7. 

,,. ..-. Ai gig i .-. , .... .-- 

61Ai 6 . 37 6

61g1 4s -7 s • milli .7- ggs.i i

:S- §1 Si gg g 

6gg,-- SR r1 

a t:2 Ii. a F 1 ,.. -, ... -1 :-' 4 -1 • a P - 

R . f.1 Di z,- ,s,,.W i6'.. 27,58 - g:§' 6t9i§::: gag 

..T 0 g 0, ,T. 0, g 0, ,`1! 0 g 0 t12. Fig 0 gl.. § 0 0 ,: § 0 0 

v ?. w • g A 14 

< d6 • ei 

• 

uf 6 ei r: 

IC4 IV. Ili 6 PI - 4 6 4 6 g 

e g vi g g 

_ 6 ei 4 6 r.. 4 to pi ei In 

W 8 +. ri 2 el 6 g I.) 4 in e: g ri g ei ui 6 g 

I.: 4 ,4 4 • - ,r7 • pi 4 

z ri 6 4 4 ri ri to — n vi .- 

LL 

GOON/ B AVE/LABORATORY VEHICLE AGE - ENVIRONMENTAL 

KII.I/K102EX 

K1 1.1/K102VX 

N vt 

n ei 

• ri vi 

K11.11KI0.IVX 

co 

m C7 

N LO 

11 

ri 6 4 4 

0 0 0 • 0. 

FUNCTIONAL FLOW BLOCK DIAGRAM 

4

gp

3

j 

z 8 

0 

O U 

0 

0 

o d o 

zzz 

coop caino 

FUNCTIONALDIAGRAM TITLE AND NUMBER 

n rryi ei ei r ri 

N N 

NN N 

GEMIN IBAVE/LABORATOR Y VEHICLEAVE- MECHANICAL 

GEMINI B AVE/LABORATOR Y VEHICLE AVE - ELECTRICAL 

GEMINI B AVE/LABORATORY VEHICLE AVE - GASEOUS 

K1 1.1/K10. 1EX 

K I1. 1 11(10.1GX 

W WW 

/— 

▪ ut 1=1 

g 0 0 

tx cc 2 000 

-W SPECIAL HANDLING 

• 

SICRIT RPrin 

109 
AA AA 

X X a. 0. >X. >X.X X 

X -I -I 

X X X X 

O 0 0 

X X 3,i X 

uJ 

X. 

O cl O • ° N 

i 

Y. Y IC 

O 0 2 2 

11 0 

% iNN 

7 

X XX

0 

X 

X 

X 

X 

0. 0. 

1.0 MX, EX, L 

0.0 MX, EX, GX, LX, VX, PX, OF 

4.0 MX, EX, GX 

✓ YNCILY 

O 0 0 0 0 1- 1- 1- I- I-

. 

VVVVV 

AA 

LL 

X TO K21.0 MX, EX, GX, LX, 

TO K 16.0 EX, R X, PX,U 

TO K17.0 EX, RX, PX 

TO K16.0 EX,RX,PX, OF 

TO K17.0 EX, RX, PX 

TO K18.0 MX, EX, RX, VX, PX, OF TO K19.0 MX, R X, V X, PX TO K21.0 MX, EX, GX, LX, VX, PX, OF 

AA AA 

TO K16.0 EX, RX,PX 

TOK17.0 PX 1.0 MX, VX, PX 

0.0 MX, EX, VX, P 

0.0 MX, EX, GX, LX, VX, PX 

umv 

P 2 O g ° 

vVvvv 

2 0 2 0 2 

vvvvv 

X TO K18.0 MX, VX 

X TO K21.0 MX, VX 

AA A 

AAAAA TO K15.0 MX, EX, GX, LX,VX,PX TO K19.0 RX, PX 0 K21.0 PX 

X X 

X X 

CC CC 

X X 

Si w 0. 

9 0. 0 c 

3i ie i2 

O P 

vvv V TO K14.0 R X, P TOK 18.0 AX, PX TO K16.0 EX,RX,PX 

0 0 0 0_ 0_ 0_ 

0 0 O 

000 O 0 CD -J CI CD 

▪ UJ Lal 

O > U_ - - C CC CC 

• UJ U_I 

> 

7 X.' 5.0 MX, EX, GX, LX, VX 

LAJ w UJ I- I- I- 

< < op o 000 

cc cc cc 000 

1-1

W

S

W Ia a tn co 

>1> 

• 

; 

> 

41, 4.1 

W

CC i CC CC 

SPECIAL HANDLING 

CONTRACTOR 

LL. 

O >- 

UJ 

> D -3

0 en_ LIJ 

a. cn 

< 

0 _1 w z 0 

ii. 

> 

X 

...I 

X 

0 

x 

. X 

0 

O 

0 

X 

X X 

29_ 

j 

X x 

9 o 

22 

X 

.2 

X A. 

X 

> x. 

.. 

x 0. 

IN 

0 

X 

0 0 ..X,.. ..X. 

X 

0 >X 

x x 

. .., 

x i 

M 

09 I.) V 

0 0 

no 

SCCR[T SPECIAL 11A;IBLIIIG 

0 

VVVVV 

-VVVVV 
NRO APPROVED FOR [. SPECIAL HANDLING 

RELEASE 1 JULY 2015 

The interfaces identified in the system level schematic shall be coded in a 

manner to indicate the types of interfaces between any two segments. The 

code used for segment identification and interface type designation is given 

in the addendum to the covert Part II. 

3.2.2 Segment Schematic Diagrams 

3.2.2.1 Preparation 

A segment-level (first-level) schematic diagram shall be prepared for each 

of the system segments by the responsible organizations. The format shown 

in Part I, Figure 10, shall be used. These diagrams shall be based on the 

code given in Addendum A to the covert Part II, and shall identify intersegment and intrasegment interfaces by specific type. Interfaces shall be 

summarized on a format as given in Figure 1; these summary sheets, which 

become part of the document, provide further descriptions of the interfaces 

and traceability to the SP/DR, RAS's, CEI Specifications, IFS documents, and 

other pertinent documents. The responsible organizations shall prepare 

any required revisions for their segment schematic diagrams. 

3.2.2.2 Integration 

The }'IPI Contractor shall verify that the interfaces identified on each of the 

segment-level schematic diagrams are properly reflected on the diagrams for 

the other segments. 

3.2.3 Lower Level Schematic Diagrams 

Each organization responsible for a system segment shall prepare sub-segmentlevel schematic diagrams in the manner prescribed in 3.2.2 above. At least 

second-level schematic diagrams shall be prepared for each sub-segment. 

Additional diagrams shall be prepared, if required, to make these system 

engineering schematic diagrams compatible with any other schematic diagrams 

which are in CEI's,IFS's ,or other pertinent documents. 

3.2.4 Responsibilities 

3.2.4.1 Preparation 

The preparation and coordination of segment, sub-segment, and subsystem, 

C R sPErn! v‘frq 

1•4 u 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 SPECM DLIC" G 

schematic diagrams shall be the responsibility of the following designated 

organizations: 

K10.0 Laboratory Vehicle System Segment - DAC MSSD 

K11.0 Gemini B System Segment - MCASTRO 

K12.0 Mission Payload System Segment - GE 

K13.0 Pressure Suit Assembly System Segment - Hamilton Standard 

K14.0 Titan IIIM System Segment - Martin Marietta 

K30.0 Photographic System Segment - Eastman Kodak 

MOL Program Office Furnished Schematics: 

K15.0 Facilities System Segment 

K16.0 Launch Operations System Segment 

K17.0 Flight Operations System Segment 

K18.0 Recovery System Segment 

K19.0 Test Support System Segment 

K21.0 Flight Crew System Segment 

3.2.4.2 Integration 

The MPI Contractor shall verify that inter-segment interfaces identified on 

any segment or subsegment schematic diagram are compatible with all of the 

related segment diagrams. 

3.2.4.3 Review 

Prior to issuing schematic diagrams of any level prepared by associate 

contractors, the MPI Contractor and the responsible segment organizations 

noted in 3.2.4.1 shall review all schematic diagrams and verify the validity 

of identified intersegment interfaces. Intra-segment interface validity 

shall be the responsibility of the segment organizations. The MPI Contractor 

will assist the OSI in evaluation of schematics furnished by the MOL Program 

Office as noted in 3.2.4.1. 

112 

r pn r T orsr-r,!p. 1 I I '1f1/,'"): r," 

1/4) L. k../ 11 wti 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

ISE.CRET SPECIAL HANDL! G 

3.3 SUBMITTAL OF DATA 

Format for data shall be as shown in paragraph 3.0 of Part 1. Data inputs 

to the Function Integrating Contractor (FIC) shall be on 11 X 17 inch vellums. 

Copies of FIC Data shall be sent to all contributors and to other associates 

on 8-1/2 X 11 inch vellums. FIC submittals to OSI and MPI Contractor (Douglas) 

shall be on 8-1/2 X 11 inch vellums. 

3.3.1 Collation of Data 

The Integrated Technical Requirements Baseline Data Package shall consist of 

13 volumes, one for each top level Function. The volume for Function 1.0 

shall be STD 207-01, Function 2.0 shall be STD 207-02, etc. Each volume 

shall consist of six or more books which shall be structured as follows: 

Book 1 shall contain the FFBD's. 

Book 2 shall contain the Timeline Sheets. 

Book 3 shall contain the SBD's. 

Book 4 shall contain R.H. RAS's (if applicable). 

Book 5 shall contain the Maintenance Analysis (if applicable). 

Book 6, etc., as required, shall contain the L. H. RAS's. 

Each book shall contain a maximum of 200 pages. All pages within each book 

shall be numbered in numerical order. Each book shall contain a change log, 

a change page index, and an index of the functions and titles contained in 

each book (see Figure 2, 3, and 4, respectively). These indices pages 

shall be numbered i, ii, iii, etc. 

3.3.2 Processing of Data 

Contributors shall send new or changed data to the Function Integrating 

Contractor. After acceptance of the data, the FIC shall process a change 

package for each book affected. The change package shall be sent to the 

contributors, associates, OSI and the MPI Contractor. The MPI Contractor 

shall insure compatibility of segment-to-segment interfaces. Periodic 

meetings (frequency dependent on data density) shall be held between OSI 

and the MPI Contractor to review FIC data. Approved data shall be delivered 

to the OSI, using normal 1423 delivery procedures. 

1-111 /11 11. 11"-.)M rA 

113 
May.•••••■■••■liOlaw171.■ VII••••■•••■••■••■••.. 

1 3-20-68 iij, 9, 15, and 30 

r 

1.1.4 FIGUirri! 2 

NRO APPROVED FOR 

RELEASE 1 JULY 2015 

FORM 804-024 (3-68) SEC S is T c,r)r.-r:rd unn;n1 ptp 

Ali LUt, -it_ 

--1-----

INTEGRATED TECHNICAL REQUIREMENTS BASELINE DATA PACKAGE 

CHANGE LOG NEW ISSUE 1 DEC 67 

STD 207 BOOK 

I TRBDP ADD PAGES 

CHANGE 

CHANGE DATE REPLACE PAGES 

15.01, 15.02, 

& 30.01 

.01 

CI-Lill:CF: LOG 
N140 'AP1315ZeIVEDTOR'''' . 

R EASE 1 JULY 2015 t 

PAGE REV & DATE PAGE 

' • 

3-20-8 23 

3-20-8 24 

25 

26 

27 

28 

1? E I SPECIAL HANDLI:;", 

INDEX 

REV & DATE PAGE REV & DATE PAGE REV & DATE PAGE REV & DATE 

ii 

111 

1 

2 

3 

3-20-8 22 

• 

5 

7 

8 . 3-20-8 

9 

10 

11 

12 

13 

14 

29 

30 A 3-20-8 

30.01 A 3-20-8 

31 

32 

etc. 

A 3-20-8 

A 3-20-3 

A 3-20-8 

Book 7 IP AGE 

4 A. 

'115- FlGUriE 3 CHA::-.GE PAGE INDEX 

15 

15.01 

15.02 

)6 

17 

18 

19 

20 

21 

22 
NRO APPROVED FOR SECRET SPECIAL HANDLII1G 

RELEASE 1 JULY 2015 

BOOK NO. 207_04 -p ool, 7 DATA TYPE RAS 

FUNCTION NO. f TITLE REVISION 

4.8 Perforn: Extravehicular Expericent 

4.8.1 Prepare for Extravehicular Experiment 

4.8.1.1 Checkout Pressure Suit 

4.8.1.2 Don Pressure Suit 

4.8.1.3 Energize Service 

4.8.1.1.1 Check 02 Sutply 

4.8.1.3.2 Check Ccamunications 

etc. 

V 

• 

410 

____J 

JA) 

' • ' ' r- F".! 

g 

1-116" L 
NRO APPROVED FOR 

RELEASE 1 JULY 2015 

SPECIAL HANDLING 

DORIAN STD shall be given handling and distribution priority over nonDORIAN STD. 

DORIAN security requirements shall be strictly observed. In the event of 

conflict between requirements of this Exhibit, particularly with respect 

to data handling and distributionl and DORIAN security requirements, the 

DORIAN procedures shall take precedence. Unresolvable conflicts shall be 

reported to the MOL Program Office for resolution. 

3.3.3 Change Control of Data 

Changes shall be accomplished by replacement pages contained in a change 

package. The change package shall contain the data (either new or changed), 

the change log, the change page index, and the function index. The data 

shall be one or more pages and may be replacements for existing pages or 

additional pages numbered in sequence. For example, additional pages to 

be inserted between two existing pages, i.e., 15 and 16, shall be numbered 

15.01, 15.02, etc. 

Changed pages within each book shall be noted on the change log as either 

a replacement page or a new page. Each page shall be controlled with a 

change page index and changes to a page shall be noted with the latest 

change letter and date. The latest change letter shall also be shown in 

parenthesis after the page number: Each function shall be controlled with 

the function index. The index shall note the latest change to any page 

within that function. 

Changes to data submitted for function or system level integration 

shall be made only with the approval of the originator. 

3.3.4 ECP Data 

Proposed changes to requirements contained in the System Technical Documentation related to ECP's shall be distributed to all affected associates and 

to the MPI Contractor for comment and assessment of interface impact prior 

to submittal of the formal ECP to the MOL Program Office. Affected 

associates and the MPI Contractor shall respond to the requesting contractor 

on the impact of the proposed change. Proposed changes to requirements 

defined in the System Technical Documentation shall be submitted as part of 

the formal ECP to the OSI and the MPI Contractor. The ECP will identify 

the specific STD by document and paragraph reference that will be changed. 

rt 11 c■ S F if it LotAT 1-14-111DLING 

r> 
NRO APPROVED FOR 4E-G-R-E-T---SPECIAL HANDLING 

RELEASE 1 JULY 2015 

The changes to the STD shall be accomplished following approval of the 

ECP.