Attachment_13A_NRO_Phase_2_Requirements_Description_and_CDRLs_3_May19.pdf

UNCLASSIFIED//FOUO

Attachment 13a

National Reconnaissance Office (NRO) Requirements Description for

National Security Space Launch (NSSL)

Phase 2 Launch Service Procurement

Instructions to Offerors (ITO) Pricing

FA8811-19-R-0002

Contents:

1. NRO Requirements Description for NSSL Phase 2 ITO Pricing

2. NRO CDRLs

1 NRO REQUIREMENTS DESCRIPTION FOR NSSL PHASE 2 ITO PRICING

1.1 DESCRIPTION AND SCOPE

In conjunction with National Security Space Launch (NSSL) Phase 2 Launch Service Procurement Contract FA8811-19-

R-0002, the National Reconnaissance Office (NRO) Office of Space Launch (OSL) intends to award a companion contract to each NSSL Phase 2 Launch Service Provider (hereinafter referred to as the Contractor) to perform mission unique services and security requirements for NRO missions. The Contractor shall integrate the mission unique services and security requirements for NRO missions with the basic launch service, which is being procured using the Air Force’s

NSSL Phase 2 Launch Service Procurement Contract. These mission unique services include, but are not limited to, the items listed in the Mission Unique Services Table in Attachment 8 of the NSSL Phase 2 Launch Service Procurement

Model Contract. The NRO security requirement item is listed in the Annual Task Order Pricing Table in Attachment 8.

This document describes the scope of “NRO Mission Integration” and “Annual NRO Enhanced Security Requirements” to inform the Offeror’s pricing proposal in accordance with (IAW) paragraphs 9.2 and 9.3.2 of the NSSL Phase 2 Launch

Service Procurement Instructions to Offerors (ITO) and Attachment 8 of the Model Contract. The scope for the Offeror to price “Annual NRO Enhanced Security Requirements” is captured in Section 2 of this attachment. The scope for the

Offeror to price Items W.0 through W.4, is captured in Section 3 of this attachment. Item W.0 “NRO Mission Integration -

Basic” shall contain the baseline NRO Mission Integration price for a basic mission IAW the requirements in Section 3.

Items W.1, W.2, W.3, and W.4 shall each contain the additional price above the baseline price in Item W.0 to integrate the

LEO, Molniya, GEO 2, and Polar 2 sample missions, respectively, using the scope of Section 3 in this attachment and the corresponding mission IRD provided in the Bidder’s Library.

2 NRO SECURITY REQUIREMENTS

The Offeror shall price Annual NRO Enhanced Security Requirements based on the tasks listed in Sections 2.1 through

2.2 below. These tasks will be priced in the Air Force NSSL Phase 2 Launch Service Procurement competition and executed on the NRO companion contract. (These tasks are supplemental to NSSL Phase 2 PWS, Section 3.1)

2.1 The Contractor shall maintain a security program IAW the requirements of the Contract Security Specification

NRO DD254. (NRO DD254 in Attachment 13b of NSSL Phase 2 Launch Service Procurement Model Contract).

2.1.1 The Contractor shall provide the support necessary for monitoring and oversight of Sensitive Compartmented

Information (SCI) secure areas IAW NRO guidelines. This includes visitor control, personnel and physical security, Information Systems Security, security SCI indoctrinations and re-indoctrinations, and implementation of a security program to support OSL and Contractor secure operations.

2.1.2 The Contractor shall provide the technical and programmatic support required to establish and maintain a

Contractor Wide Area Network (CWAN) classified computer system within the Contractor’s OSL-sponsored secure areas.

2.2 The Contractor shall provide unescorted access at the launch facilities to the Government and Space Vehicle (SV) teams. The Contractor shall provide the training required for unescorted access and the appropriate mission badges.

3 NRO MISSION INTEGRATION

The Offeror shall price NRO Mission Integration Items, W.0 through W.4, based on the tasks listed in Sections 3.1 to 3.15 below. Item W.0 shall consist of the baseline price for NRO missions conducted IAW these requirements. Items W.1 through W.4 shall contain the additional price above the baseline price in Item W.0 to integrate each respective sample mission using the corresponding IRD. These tasks will be priced for the Air Force NSSL Phase 2 Launch Service

Procurement competition and executed on the NRO companion contract. (These tasks replace NSSL Phase 2 PWS, Section 3.4)

3.1 MI: MISSION INTEGRATION (FOR NRO MISSIONS)

In order to ensure the successful integration of the PL (IPS) with the Launch Vehicle (LV), the Contractor shall provide all services necessary to integrate the PL (IPS) with the LV in accordance with Evolved Expendable Launch Vehicle

(EELV) System Performance Requirements Document (SPRD) Rev. B, EELV System Interface Specification (SIS) Rev.

C, mission-specific Interface Control Documents (ICDs) and Interface Requirements Documents (IRDs), Technical

Operating Report (TOR)-2016-02946, “Rideshare Mission Assurance and the Do No Harm Process”, and the EELV

Rideshare User’s Guide (RUG). The Contractor shall be responsible for managing all the mission integration of the PL

(IPS), flight, and ground systems with the LV and its associated Ground Support Equipment (GSE). The Contractor shall plan, schedule, and manage all mission analyses required to define and verify compatibility with the interface requirements and environments. (Integrated Data Environment (IDE))

For each mission, the Contractor shall identify a single principal mission manager interface POC for the OSL and Launch

Services Integration Contractor (LSIC).

3.2 MI: MISSION INTEGRATION DATA

The Contractor shall provide and maintain the USG and SV Team access to Mission Integration data supporting this contract residing on the Contractor’s systems throughout the contract period of performance. The Contractor shall communicate with the United States Government (USG) and SV Team any updates to Mission Integration data (to include manufacturing, testing, operational, or process changes) to deliver Launch System data products as soon as possible but no later than (NLT) 24 hours, or 1 business day, after the updates. Any NRO Mission Integration data not covered under the Air Force contract shall be uploaded to My Mission Link (MML).

3.3 MI: MISSION INTEGRATION MANAGEMENT

3.3.1 MI: The Contractor shall provide a Mission Integration Management Plan (MIMP) which defines the Contractor’s standard process flow and specific timelines needed for PL (IPS) integration with the LV. For multi-mission manifested missions, the MIMP shall address both the integration of the PLs onto the IPS and of the IPS to the

LV. The MIMP shall be consistent with Mission Integration Schedule (MIS) and include the organizational roles and responsibilities, management approach, documentation products, integrations meetings, working groups, reviews, and controls required to implement the integration process for the mission. (CDRL N002)

3.3.1.1 MI: The Contractor shall support development of various integration plans as mutually agreed upon between the

Contractor, OSL Mission Management Team (MMT), and LSIC to augment formal requirements documented in the Mission ICD. These include, but are not limited to, a Loads Analysis Plan, mission-specific contamination control plan, and Mission Specific Rehearsal Plan (MSRP).

3.3.2 MI: The Contractor shall provide and maintain a Mission Integration Schedule (MIS) that begins at Authority to

Proceed (ATP) and ends after conclusion of the Government Post-Flight Review at approximately Launch plus 60

(L+60) calendar days. The MIS shall include all tasks, mission analyses, reviews, working groups, meetings, and milestones required to accomplish the mission integration process to meet the mission Initial Launch Capability

(ILC). All MIS tasks shall be logically linked horizontally and vertically, to include all interdependencies as required by CDRL N001.

3.3.2.1 MI: The Contractor shall include as a part of the MIS a separate and complete list of all the required data exchanges between the Contractor and the OSL MMT, and LSIC to accomplish the mission integration process.

The Contractor shall coordinate the data exchange list with the OSL MMT and LSIC and any changes must be agreed upon by all parties.

3.3.2.2 MI: The Contractor shall include as part of the MIS a separate critical path schedule that identifies the series of tasks that result in the minimum margin to the ILC.

3.3.2.3 MI: The Contractor shall make the MIS available to the OSL MMT monthly, and all changes from the previous

MIS shall be identified and highlighted along with the rationale for change.

3.3.3 MI: The Contractor shall hold biweekly production status teleconferences with the OSL MMT during the final 3 months prior to shipment of LV hardware from the factory. Topics to be covered shall include production status, schedules, any hardware or factory issues that may impact shipment, and transportation planning. The teleconferences should last approximately 30 minutes.

3.6.1 MI: The Contractor shall develop and make available to the OSL MMT and LSIC teams a Payload Installation

Drawing (PID). The PID shall document the mechanical integration of the PL (IPS) with the LV system to ensure compatibility with all structural/mechanical requirements as specified in the Mission ICD. The MUK shall also be documented in the PID. Development and exchange of the PID shall be captured in the MIS and the Data

Exchange List. (IDE)

3.6.2 MI: The Contractor shall develop and make available to the OSL MMT, and LSIC teams SV-to-LV Electrical

Drawing (SLED). The SLED shall document the electrical integration of the PL (IPS) with the LV avionics and electrical systems to ensure compatibility with all avionics requirements as specified in the Mission ICD.

Development and delivery of the SLED shall be captured in the MIS and the Data Exchange List. (IDE)

3.7 MI: INTERFACE CONTROL DOCUMENT

The Contractor shall generate and maintain a mission ICD that correlates to IRD requirements. The ICD shall include all mission requirements including launch vehicle and launch site interface definition and environments (including GSE). The

ICD shall include the payload to launch vehicle/launch site electrical and mechanical interface drawings. (CDRL N005)

3.7.1 MI: The Contractor shall generate an IRD to mission ICD traceability matrix that documents where each IRD requirement is captured in the mission ICD. For IRD requirements not captured in the mission ICD, the

Contractor shall document in the traceability matrix where that specific IRD requirement is captured in other

Contractor documents and how it will be met and verified by the Contractor. The Contractor shall provide the complete traceability matrix to the USG Team and LSIC prior to the Mission Integration Requirements Review.

3.7.2 MI: The Contractor shall perform configuration management for the mission ICD once it is baselined and signed by all parties. Subsequent changes to the mission ICD shall be documented through an ICD Change Notice (ICN) process and shall require approval by all the signed parties. The ICN process shall be described in the ICD.

Revisions to the ICD shall be submitted as necessary taking into account the number of approved changes.

3.7.3 MI: The Contractor shall generate and maintain a list of open requirements that require further negotiation between the Contractor, USG Team, OSL MMT and the LSIC after the mission ICD has been baselined and approved. This list shall be reviewed at Mission Integration Status Teleconferences and Integration Requirements and Verification Teleconferences until all open requirements have been negotiated, approved, and incorporated into the mission ICD. (IDE)

3.7.4 MI: The Contractor shall ensure that all LV hardware and software and the mission design complies with the ICD.

The Contractor shall provide systems engineering oversight to trace LV system requirements and provide continuous visibility into LV engineering efforts and their impact to the mission ICD.

3.8 MI: MISSION DESIGN AND ANALYSES

The Contractor shall perform mission design and analyses, as outlined in Table 2, to ensure that the requirements of the mission IRD and the mission ICD (when signed) are met. The Contractor shall optimize the mission-specific design consistent with the mission-specific requirements and constraints as specified in the mission IRD or ICD. The Contractor shall reserve performance IAW SPRD040. The Contractor shall perform all mission analyses in accordance with the

NRO’s Launch Information Protection Guide. (CDRL N011)

3.8.1 MI: The Contractor shall perform, document, and make available to the USG Team and OSL MMT, and LSIC teams the mission-specific analyses outlined in Table 2. The specific completion dates for each analysis will be negotiated with the USG Team, OSL MMT, and LSIC teams and documented in the MIS and data exchange list.

3.8.2 MI: The Contractor shall update analysis tools and models based on test and flight data, and assess the impact to already completed analyses. If, using documented company procedures, the Contractor determines that test or flight data shows a previously completed assessment/analysis no longer envelopes the requirements of the mission, the Contractor shall update the assessment/analysis.

requirements and work with the Government to resolve any incompatibilities that will impact SV or LV system design and operations for the mission.

3.9.3 MI: The Contractor shall support development of the integrated operations plans at both the Contractor’s launch pad and the PPF. The PPF is the facility in which the SV will be encapsulated and readied for transport to the

Contractor’s launch pad. These plans will include the following:

3.9.3.1 MI: The Contractor shall develop, in coordination with the USG and LSIC teams, a Concept of Operations

(CONOPs) for integrated operations in the PPF and at the Contractor’s launch pad.

3.9.3.2 MI: The Contractor shall support the NRO’s process for three-dimensional (3D) modeling of the processing flow and CONOPs for all integrated operations. The Contractor shall deliver 3D models of all LV flight and

GSE hardware with fidelity appropriate to the NRO’s 3D modeling contractor.

3.9.3.3 MI: The Contractor shall develop a Facility Requirements Document (FRD) that documents all of the

Contractor’s constraints and requirements for the PPF. The FRD shall also include any communications requirements needed by the Contractor in order to operate in the PPF. The USG team will review and assess the requirements identified in the FRD during the integration process and provide feedback on acceptability leading to formal acceptance at the reviews. The Contractor shall deliver a draft FRD to the USG Team by L-18 months and a final FRD by L-12 months. Development and delivery of the FRD shall be captured in the MIS and the

Data Exchange List. (CDRL N003).

3.9.3.4 MI: The Contractor shall support the USG-led Launch Base Requirements Review (LBRR) and Initial

Communication Baseline Meeting (ICBM) at the launch base at L-12 months. The purpose of the LBRR and

ICBM are to review the USG Team’s implementation and supportability plans to meet the Contractor’s launch base and communication requirements as documented in the FRD.

3.9.3.5 MI: The Contractor shall support the LSIC in developing an end-to-end SV data flow test plan, if required.

3.9.4 MI: The Contractor, in coordination with the USG and LSIC teams, shall develop and execute an integrated operations schedule that covers all LV and SV integrated processing that occurs at the launch site. The Contractor shall maintain a summary level schedule and a detailed day-by-day, hourly schedule. The schedules shall clearly indicate any contingency days, as well as weekends, holidays, and any shift constraints. (Integrated Operations

Schedule)

3.9.4.1 The Contractor shall support development of the NRO’s “Horse-blanket” schedule. The “Horse-blanket” schedule is a detailed, hour-by-hour, day-by-day schedule encompassing all SV and integrated operations occurring at the launch site for the mission and is maintained by the NRO.

3.9.4.2 MI: The Contractor shall make available the preliminary integrated operations schedule by L-18 months for incorporation into the NRO’s initial “Horse-blanket” schedule. The Contractor shall make available a final integrated operations schedule by GORR-30 days for incorporation into the final “Horse-blanket” schedule.

(Integrated Operations Schedule)

3.9.4.3 MI: After the “Horse-blanket” schedule has been baselined, the Contractor shall continue to maintain the integrated operations schedule and provide updates for incorporation into the “Horse-blanket” schedule. Updates shall be discussed during the SV daily scheduling meetings. The Contractor shall notify the OSL MMT of any changes to planned activities within NRO facilities (PLF ops, encapsulation, transport out of processing facility, movement of equipment)

3.9.4.4 MI: The Contractor shall develop and coordinate all Integrated Operations procedures with the OSL MMT, LSIC, and the NRO’s Safety Review Team (SRT) for review and approval. (IDE)

3.9.4.4.1 MI: The Contractor shall maintain a detailed list of all integrated procedures along with the required draft and final delivery dates for each procedure. The delivery dates shall be negotiated with the USG team and SRT and shall have the appropriate set-backs to account for USG, LSIC, and SRT review time, comment incorporation, comment back-check, and final approval prior to first use. (IDE)

3.9.4.4.2 MI: The Contractor shall schedule and perform a Table Top Review for each integrated operations procedure that will either be a first-time use or has had significant updates. Each table-top review shall be held between the draft version release and the comments submittal required dates. The Contractor’s procedure author shall lead the table-top review.

3.9.4.4.3 MI: The Contractor shall document the man-loading requirements in each integrated operations procedure that is determined to be hazardous by the SRT. The man-loading requirements will cover both Contractor and

USG, LSIC, and SRT personnel.

3.9.4.4.4 MI: The Contractor shall have a procedure change process that includes the OSL MMT, LSIC, and SRT for coordination and approval on all changes to integrated operations procedures after the procedure has been approved and released. This change process shall also cover changes that are made real-time during execution of the procedure.

3.9.4.4.5 MI: The Contractor will review and comment on the NRO provided Operations Policy Plan and be a signatory to the document.

3.9.4.5 MI: The Contractor shall support the USG and LSIC teams in developing a DoL CONOPs for the mission. The

Contractor shall incorporate the USG and LSIC teams and processes into the Contractor’s DoL CONOPs to include LV/SV interface launch constraint monitoring and reporting, integrated anomaly resolution process, T-0 recycle coordination, and critical event polling. The Contractor shall use the NRO’s Baseline DoL Plan as guidance.

3.10 MI: LAUNCH REHEARSAL SUPPORT

MI: The Contractor shall perform launch rehearsals with the USG Team, SV Teams, and NRO Operations Squadron

(NOPS) using the OSL Baseline Launch Rehearsal Plan (BLRP) missions as guidance. The Contractor shall support the development of a MSRP, which will outline any additions, changes, or deviations from the BLRP for the mission.

3.10.1 MI: The Contractor shall participate in rehearsal planning efforts, and the development and rehearsing of anomalies in coordination with the Government/contractor, Rehearsal Working Groups, and Rehearsal Anomaly

Team (RAT).

3.10.1.1 MI: For the RAT, the Contractor shall provide Launch Vehicle Program Rehearsal Lead to be the lead for all

Contractor rehearsal activity and a Mission RAT member (LV SIM), a technical SME, to be responsible for coordinating the development of LV and integrated LV/PL (IPS) anomalies.

3.10.1.2 MI: The Contractor shall support the RAT Kickoff meeting and recurring RAT meetings leading up to the rehearsals starting at L-9 months. RAT meetings will be bi-weekly up until one month prior to the scheduled rehearsal at which point the meetings will occur weekly.

3.10.2 MI: The Contractor shall develop with the RAT all documentation required for rehearsal to include white cards

(anomaly scenario technical detail), profile letter, rehearsal script, rehearsal timeline, and integrated mission script and mission-specific DoL support.

3.10.3 MI: For mission rehearsals, the Contractor shall support the Government’s Launch Information Display System

(LIDS), which will be used in all mission rehearsals and exercises. The Contractor shall comply with the LIDS interface requirements as specified in the LIDS IRD in Appendix C.

3.10.4 MI: The Contractor shall perform three integrated launch rehearsals for each mission. The first two rehearsals will be referred to as Integrated Crew Exercise (ICE) 1 and ICE 2; the third rehearsal will be a Mission Dress

Rehearsal (MDR). The MDR shall practice a real-time T-0. In addition, the Contractor shall perform a table-top exercise prior to ICE #1. The Contractor shall configure facilities for rehearsals such that connectivity between facilities shall represent that of DoL.

3.10.5 MI: The Contractor shall support Unclassified and Classified Academic sessions, to include development of the briefing materials, prior to each rehearsal and Unclassified and Classified Hotwashes following each rehearsal.

3.10.6 MI: The Contractor shall support 3D computer simulation of the LV during ascent for demonstration and rehearsals. 3D modeling of the LV will include engine firings and shutdowns, staging events, attitude control thruster firings, body attitude and rates, and other appropriate display data to visualize the LV and SV during ascent. The simulation will be driven by LV telemetry.

3.10.7 MI: During rehearsals, the Contractor shall provide key DoL personnel as required to simulate an authentic DoL scenario. At a minimum this shall include the launch conductor, anomaly coordinator, LV mission manager, mission requirements engineer, range coordinator, and the SV ground operations coordinator.

3.10.8 MI: The Contractor shall make available, in printable format, the equivalent documentation that will be used for leading rehearsals and launch, to include LV countdown procedures, Launch Console Handbooks, and rehearsal anomaly documentation as defined in the OSL BLRP missions NLT 7 calendar days prior to rehearsals and launch. (IDE)

3.11 MI: MISSION INTERFACE CONTROL DOCUMENT REQUIREMENTS VERIFICATION

The Contractor shall verify that the LV requirements documented in the mission ICD are met and facilitate OSL and LSIC and LSIC participation in requirements verification. The Contractor shall provide a Verification Planning Matrix, and

Verification Evidence Records. The Contractor shall apply TOR-2016-02946 “Rideshare Mission Assurance (RMA) and the Do No Harm (DNH) Process” as part of the mission verification process, including development and execution of a mission unique DNH checklist (CDRLs N005, N006, N007, and N009).

3.11.1 MI: For each “shall” requirement in the ICD, the Contractor shall identify and develop a requirement verification closure methodology (such as Analysis, Inspection, Demonstration, or Test) and a verification plan (short description of the analysis, inspection, demonstration, or test to be performed) that is acceptable to the OSL

MMT, and LSIC teams. Multiple verification methodologies can be assigned to a single requirement, but will be tracked as individual verifications. This information shall be included in the mission ICD and shall be configuration controlled through the Contractor’s ICN process. The Contractor shall present the verification information identified above at the MIRR. All verifications shall be individually approved by the OSL MMT, and

LSIC prior to closure. (CDRLs N006 and N007)

3.12 MI: FLIGHT HARDWARE INTERFACE CHECKS

The Contractor shall perform tests to verify the compatibility of the physical and electrical interfaces and clearances between the LV and PL (IPS). The testing shall verify that all physical and electrical interfaces, including electrical continuity, meet mission ICD requirements. The Contractor shall perform electrical and mechanical fit checks of the adapter harness to the standard electrical interface panel for each PL (IPS). The Contractor shall accomplish the interface tests NLT L−12 months subject to the availability of facilities and PL (IPS) hardware. In the event of unavailability of facilities or PL (IPS) hardware, the time-phasing of this test shall be coordinated among the LVC, LSIC and OSL. (CDRL

N004)

3.13 MI: GROUND HARDWARE INTERFACE CHECKS

The Contractor shall support PL (IPS) GSE interface fit checks with the Launch System NLT L−12 months. The time-phasing of this test shall be coordinated among the LVC, LSIC, and OSL

3.14 MI: LAUNCH RANGE COORDINATION

For each mission, the Contractor shall capture mission-specific hardware, processing, and hazards, including SV team inputs and reports for SV identified hazardous items, in the Missile System Prelaunch Safety Package (MSPSP) and submit to Range Safety in accordance with AFSPCMAN 91-710. The Contractor shall also coordinate PL (IPS) integrated operations and launch requirements (e.g., RF emitter control, telemetry support, etc.) with the Launch Range via the

Universal Documentation System and other base support documentation. The Contractor shall coordinate approval of all related operation requests received from the Launch Range with the OSL MMT and LSIC.

3.15 MI: STANDARD NRO TESTS

The Contractor shall conduct, support, and coordinate test requirements as required by the IRD, which may include but are not limited to be the following mission-specific tests:

3.15.1 MI: Fit check shall include a fit check of LSIC provided Payload Adapter (PLA) to LV electrical and mechanical interfaces. Includes LV factory support of required hardware checkout.

3.15.2 MI: 3D visualization support (LV flight and GSE hardware models)

3.15.3 MI: SV/LV separation shock test

3.15.4 MI: Payload envelope sweep test

3.15.5 MI: SV end-to-end data flow tests

NRO CDRL ADDRESS LIST

1. HQ Space & Missile Systems Center (AFSPC) LE

Launch Enterprise Systems Directorate

Attn: LE Data Management Office

483 North Aviation Blvd.

Los Angeles AFB

El Segundo, CA 90245-2808

SMC.LE.CMDM@us.af.mil

2. HQ Space & Missile Systems Center (AFSPC) SAF/SL

Attn: SAF/SL, Bldg. A5 483 North Aviation Blvd.

Los Angeles AFB

El Segundo, CA 90245-2808

3. 30th Operations Group 30 OG

Attn: Data Desk 806 13th St, Room 285

Bldg. 7015

VAFB, CA 92437-5221

4. 45 LCG / 45 LCSS 45 LCG

Attn: Data Library

15270 Samuel C. Phillips Parkway (CCAFS) Building 1645 Patrick AFB, FL 32925-2009

5. Defense Cost and Resource Center (DCARC) DCARC 201 12th Street South

Suite 220

Arlington, VA 22202

(703) 601-4850

6. DCMA, TBD DCMA

7. NRO Operations Squadron NOPS

401 Discoverer Ave. Ste 32

Schriever AFB, CO 80912 NOPS_Launch@us.af.mil

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP TM OTHER X

D SYSTEM / ITEM E CONTRACT / PR NO F CONTRACTOR

NSSL NRO Companion Contract

1 DATA ITEM NO 2 TITLE OF DATA ITEM 3 SUBTITLE

N001 Integrated Program Management Report (IPMR)

Mission Integration Schedule (MIS)

4 AUTHORITY (Data Acquisition Document No.) 5 CONTRACT REFERENCE 6 REQUIRING OFFICE

DI-MGMT-81861A/T Attachment X

SAF/SL

7 DD 250 REQ 9 DIST STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

LT

BI-MO

BLK 16

b COPIES

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

SUBMISSION

a ADDRESSEE

FINAL

N/A

Draft Reg Repro

16 REMARKS See Distribution List

1. (BLK 4): MIS schedule will be a subset of the IMS submitted for each NSS Launch Task Order.

DID subsection 6 is applicable in accordance with a mutually agreed upon format.

a. The MIS may be used to coordinate Mission Integration activity and SV schedule for integration purposes.

2. (BLK 11) Last day of the contractor’s monthly accounting period.

3. (BLK 12) Submittal of MIS will be provided to the Government for each Launch Task Order, with initial submitted no later than 60 calendar days (CD) after task order.

4. (BLK 13) Electronic copy shall be submitted NLT 14 federal working days after contractor’s month end close

15 TOTAL

G PREPARED BY H DATE I APPROVED BY J DATE

Electronically Generated PAGE 1 OF 1 PAGES

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

X TDP TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

N002 Work Management Plan

Mission Integration Management Plan

DI-MGMT-81911/T Attachment X

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

ASREQ

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 1 with “1. Format. The plan shall be in the contractor’s format. The plan shall be printable on standard size paper, e.g., 8 ½ x 11 or A4.”

b. Replace 3 with “The Mission Integration management Plan describes the contractor’s mission integration services and process flow. The Plan shall contain the following sections:

1.0 Introduction

2.0 Integration Management

2.1 Standard Mission Integration Plan. Provide an overview of the mission integration processes/tasks, citing applicable Performance Work Statement (PWS) paragraphs for reference.

2.2 Integration Schedules. Provide the Mission Integration Schedule and associated schedules used in the Mission Integration process.

2.3 Action Items: Provide an overview of the contractor’s process and tracking system used to ensure action item closure.

3.0 Organizational Responsibilities. For the following organizations describe the organization responsibilities in the Contractor’s Mission Integration process. Provide a graphical representation of the corresponding connections and Points of Contacts between the different organizations.

3.1 Government Organizations

3.1.1 Office of Space Launch

3.1.2 USAF Space Wing(s)

3.2 Contractor Organizations

3.2.1 Launch Vehicle Contractor (LVC)

3.2.2 Launch Service Integration Contractor (LSIC)

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

X TDP TM OTHER

NSSL

16 REMARKS

4.0 Key Integration Meetings. Provide the detail description purpose/objectives and composition of the following Contractor meetings:

4.1 Mission Integration Kick-off meeting (Four-party meeting to introduce the mission and integration plan)

4.2 Mission Design Review (MDR) (Preliminary design review for mission integration)

4.3 Mission Verification Review (MVDR) (Critical design review for mission integration)

4.4 Ground Operations Readiness Review (GORR) (For USAF missions) (Launch site readiness for ground operations to integrate spacecraft onto the launch vehicle)

4.5 Pre-Vehicle Ship Review (Verify readiness to ship flight hardware to the launch site)

4.6 Component and Subsystem Readiness Review (CSRR) (Assessment of mission and launch vehicle design and analysis)

4.7 Integrated Operation Readiness Review (IORR) (Review and demonstrate launch site and launch vehicle readiness for integrated ops)

4.8 Space Flight Worthiness Certification Review (SCR) (Establishes readiness of launch system to proceed into countdown operations)

4.9 Launch Readiness Review (LRR) (Final Contractor’s readiness review for launch)

4.10 Other Contractor Mission Readiness Reviews (Any other readiness reviews necessary due to the nature of the mission)

4.11 Launch System Program Level Reviews (Contractual or hardware reviews which the integration team should support)

5.0 Customer Reviews and Rehearsals. Provide description and summarization of level of support to be provided for the following meetings:

5.1 Mission Rehearsals (including academics)

5.2 Spacecraft Mission Readiness Review (MRR)

5.3 Flight Readiness Review (FRR)

5.4 Ground Operations Readiness Review (GORR)

6.0 Integration Working Groups. Provide a description of the nature and composition of the working groups below.

6.1 Management Working Group (MWG)

6.2 Ground Operations Working Group (GOWG)

6.3 Day-of-Launch Working Group (DOLWG)

6.4 Ascent Operations Working Group (AOWG)

6.5 Rehearsal Working Group (RWG)

6.6 Other Contractor Mission related working group (Any other working group necessary due to the nature of the mission)

7.0 Integration Tasks and Responsibilities

7.1 Space Vehicle Information. Provide a chronological tabular listing of data required from the Space Vehicle Contractor by the Launch Vehicle Contractor;

examples include Space Vehicle (SV) interface requirements, SV CAD/loads models, analyses results required for input to integrated analyses.

7.2 Launch Vehicle (LV) Information. Provide a chronological tabular listing of the information/reports developed during the mission integration process.

(Key products including analyses, reports, requests, schedule, and other documentation or data. May require two Couple Loads Analyses at different times.)

7.3 Mission Integration Control Documents. Provide the list of mission integration control documents the contractor is responsible for preparation, distribution, and maintenance of. Provide the process/plan for maintaining configuration control of these documents.

7.4 Interface Control Document (ICD) and Verification Process. Provide a description of the ICD, the Contractor’s process for development, and verification of the ICD.

Appendix A: Entry/Exit Criteria for Key Integration Meetings

Appendices as needed for Definitions, Terms, Abbreviations and Acronyms”

c. Delete 5. Media Requirements.

2. (BLKs 12 and 13)

a. Submit draft 90 DACA for Government review and comment

b. Submit final 30 CD after receipt of Government comments for Government approval.

c. Submit updates to incorporate changes to the document process, as required for mission specific changes with an added task order, or upon Procurement

Contracting Office (PCO) direction for Government Approval.

Electronically Generated PAGE 2 OF 2 PAGES

. APPROVED BY

(1 Data Item)

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

X TDP TM OTHER

D SYSTEM/ITEM E CONTRACT/PR NO F CONTRACTOR

1 DATA ITEM NO 2 TITLE OF DATA

M 3 SUBTITLE

N003 Facility Requirements Documents

4 AUTHORITY (Data Acquisition Document No.) 5

CONTRACT REFERENCE 6 REQUIRING OFFICE

DI-FACR-80810A Attachment X SAF/SL

7 DD 250 REQ 9 DIST

STATEMENT

REQUIRED

10 FREQUENCY 12 DATE OF

FIRST

SUBMISSI

14 DISTRIBUTION

LT BLK 16 BLK 16

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQ

UENT

Draft

N/A N/A BLK 16 Reg Repro

16 REMARKS See Distribution List

1 (BLK 4)

a Replace section 3.1 with “The FRD identifies all of the Contractor’s constraints and requirement for the use of the Payload Processing Facility. These requirements describe the facilities and services necessary to perform Payload Fairing (PLF) offload, PLF cleaning, pre-mate preparations, spacecraft mate to Payload Attach System (PAS), encapsulation, and post-encapsulation preparations for transport to the launch pad by the

Contractor. The requirements do not address facilities related to spacecraft processing.”

b Delete section 7.2 and 7.3 c Replace section 10. with:

“10.2 Content. The document shall include the following information:

10 2 1 General requirements to include any requirements for administrative areas as well as any communications requirement needed by the Contractor in order to operate in the PPF.

10 2 2 Hardware Arrival – Description of the general overview of operations and the required facility and service requirements

10 2 3 Flight Hardware Processing Prior to Encapsulation - Description of the general overview of operations and the required facility and service requirements

10 2 4 Integrated Operations and Encapsulation - Description of the general overview of operations and the required facility and service requirements

10 2 5 Transportation Preparation - Description of the general overview of operations and the required facility and service requirements”

2. (BLKs 10, 12, and 13) a Submit initial draft by ATP + 1 month.

b Submit final by L-18 months.

H DATE

J DATE

Electronically Generated PAGE 1 OF 1 PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP X TM OTHER

N004 Test Procedure

Flight Hardware Interface Checks

4 AUTHORITY (Data Acquisition Document No.)

5 CONTRACT REFERENCE 6 REQUIRING OFFICE

DI-NDTI-80603A/T Attachment X

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

A

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 2 with: “2. Format. The test procedure shall be in an electronic format and printable on standard size paper, e.g. 8 ½ x 11 or A4.”

b. Replace 3.2.5 with: “3.2.5 Safety Requirement Checklist. A safety requirement checklist shall be included to document hazardous conditions that will exist during the test activity.”

2. (BLKs 10, 12 & 13):

a. Submit initial Flight Hardware Interface Checks (FHIC) 90 CD prior to each Fit Check.

b. Submit final FHIC 30 CD prior to each Fit Check test.

c. Submit the As-run procedures 14 CD after completion of each Fit Check test.

3. The Government will review each submission and provide feedback within 30 CD to the maximum extent possible.

Electronically Generated PAGE 1 OF 1 PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP X TM OTHER

N005 System/Segment Interface Control Specification

Mission Interface Control Document (ICD)

DI-SESS-81314A/T Attachment X

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4): Update DI-SESS-81314 as follows:

a. 2. Format, Replace first two sentences with “The interface specification shall be prepared in an electronic format and printable on 8 ½ x 11” paper (metric size A4). It may be a multi-part electronic document.”

b. Replace 2.1.1 with “2 1 1 Document number. The document number shall appear on the title page.”

c. Replace 2.1.2 with “2 1 2 Date. The document issue data (Baseline/Revision Number and Issue

Date) shall appear on the title page.”

d. Replace 2.1.3 with “2 1 3 Title. The document title shall appear on the title page stating the nomenclature of the interfacing items.”

e. Delete 2.1.4.

f. Delete 2.2.1.

g. Replace 2.4 with:

“Section 3.0, Requirements. This section provides the detailed description of the interface requirements. Each interface shall be separately covered in its own subsection, and include:

1) Launch Vehicle Configuration

2) Space Vehicle Configuration (For USAF Missions)

3) Mission Parameters

4) Space Vehicle/Launch Vehicle Interface Requirements

5) Space Vehicle Handing and Processing Requirements

Include mission-specific payload systems weight capability for the mission and PLF selected and specific mission design constraints.”

h. Replace 2.5 with:

“Section 4.0, Quality assurance. This section shall identify and define the following:

1) Philosophy of Verification

2) Verification Methods

Electronically Generated PAGE 1 OF 2 PAGES

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP X TM OTHER

NSSL

16 REMARKS

i. Replace 2.6 with: “Section 5.0, Notes. This section shall include Definitions, Abbreviations, Acronyms and Symbols.”

j. Delete Figure 1 Replace 3. With “Appendix A – This appendix shall include the Electrical Interfaces. Appendix B – This appendix shall include the Mechanical

Interfaces. ”

k. Delete 3.1 – 3.3

2. (BLK 8): Signatures by 4-Party Technical Team

a. LV Contractor, Office of Space Launch (OSL) Mission Manager, OSL Contracting Officer’s Technical Representative, and LSIC constitutes Government approval of the Mission ICD.

3. (BLKs 10, 12, and 13):

a. Submittal of ICD will be provided to the Government for each Launch task order.

b. Submit first draft of the Baseline Mission ICD no later than (NLT) Authority to Proceed (ATP) +3 Months. No Government approval required.

c. Submit second draft NLT Launch – 12 months for Government approval.

d. Submit Final 30 CD after 4-Party technical Team signature to be formalized by bi-lateral contract modification.

Electronically Generated PAGE 2 OF 2 PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP X TM OTHER

N006 Specification Requirement Verification Matrix

Verification Planning Matrix (VPM)

DI-MISC-81283/T Attachment X

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 10.1 with “10.1 Format. The matrix shall be Microsoft Excel compatible and in the format provided in Figure 1 and shall conform to the following:”

b. In 10.1.2 add “, as necessary,” after “worksheets and charts”

c. In 10.1.3 Revise the first two sentences to read, “The matrix shall be in electronic format.”

d. Delete 10.1.4 and 10.1.5.

e. Replace 10.2 with “10.2 Content. The matrix shall contain the following: Requirement Number, Requirement Paragraph Number, Paragraph Title, Requirement Text, Verification Method, Responsible Organization, Verification Location, Verification Plan, Verification Milestone and

Planned Closure Date.”

f. Delete 10.2.1–10.2.8.

g. Replace Figure 1 with:

Requirement # Paragraph # Title Text Verification

Method

Responsible

Organization

Location Verification

Plan

Milestone Planned

Closure

Date

Figure 1 – Verification Planning Matrix

2. (BLK 10): Submit for each mission. Submittal of VPM will be provided to the Government for each

Launch task order.

3. (BLKs 8, 12, and 13):

a. Submit first draft at Launch – 18 Months. No Government approval required.

b. Submit second draft at Launch – 12 months for Government approval.

c. Submit final for Government approval 30 CD after 4-party signature of Mission ICD.

Electronically Generated PAGE 1 OF 1 PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503 Please DO NOT RETURN your form to either of these addresses Send completed form to the Government issuing Contracting officer for the Contract/PR No listed in Block E

A CONTRACT LINE ITEM NO B EXHIBIT C CATEGORY:

TDP X TM OTHER

N007 Specification Requirement Verification Matrix

Verification Evidence Record (VER)

DI-MISC-81283/T Attachment X

REQUIRED

10 FREQUENCY 12 DATE OF FIRST

SUBMISSION

14 DISTRIBUTION

8 APP CODE D 11 AS OF DATE 13 DATE OF

SUBSEQUENT

16 REMARKS See Distribution List

1. (BLK 4):

a. Replace 10.1 with “10.1 Format. The Verification Evidence Record (VER), along with the evidence of verification closure, shall be in electronic format(s) compatible to Microsoft Office products or .PDF. Electronic access on a Government accessible database satisfies the requirements of delivery ”

b. Delete 10.1.1–10.1.5

c. Replace 10.2 with:

“10.2 Content. The VER shall include, but not be limited to:

a. The Requirement

b. Verification method(s)

c. Identification of Launch Vehicle Contractor (LVC) assigned responsible engineers

d. Dates verification(s) completed

e. Evidence of verification supporting LVC’s closure rationale, including but not limited to, analyses, procedures, test documents, drawings, inspections, and as-built/as-run data.”

d. Delete 10.2.1–10.2.8

e. Delete Figure 1

2. (BLK 7) The contractor shall document (electronic Interoffice Memorandum acceptable) and notify the Requiring Office when delivery occurs identifying the location of the data. Copies of this notification shall be maintained on the Government accessible database.

3. (BLKs 10, 12, and 13): Submittal of VER will be provided to the Government for each Launch task order.

4. Submit individual records to the OSL MMT and LSIC teams for approval.

5. (BLKs 10, 12, and 13): Contractor shall submit at least 30% of VER no later than (NLT) L-3 months. Contractor shall submit at least 60% of VER NLT L-2 months.

a. USG will provide comments on verifications deemed to be inadequate or incorrect within 30 calendar days to the maximum extent possible

Electronically Generated PAGE 1 OF 1 PAGES

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters…