DHPSC Draft SOW For SS 30 May 24 V5_Watermarked.pdf

UNCLASSIFIED

ATTACHMENT 1: STATEMENT OF WORK

FA8809-R-000X

Department of Defense (DoD) Human-rated Payload 1

Support Contract - (DHPSC) 2

Attachment 1 - Statement of Work 3

30 May 24 – Draft V5 4

FA8809-R-000X 1

UNCLASSIFIED

TABLE OF CONTENTS 1

1. SCOPE AND OBJECTIVES ......................................................................................................4 2

2. REFERENCES ...........................................................................................................................5 3

DEFINITIONS...................................................................................................................... 5 4

2.1.1. PAYLOAD ELEMENT (PE) ........................................................................................... 5 5

2.1.2. PRINCIPAL INVESTIGATOR (PI) ................................................................................ 5 6

2.1.3. CONTRACTING OFFICER’S REPRESENTATIVE (COR) ........................................... 5 7

2.1.4. DHPSC PROGRAM MANAGER (PM) .......................................................................... 5 8

2.1.5. DoD OPERATIONS TEAM (DOT) ................................................................................ 5 9

2.1.6. DoD PAYLOAD OPERATIONS CONTROL CENTER (POCC) ................................... 5 10

2.1.7. HOUSTON SPACE OPERATIONS GROUND SYSTEM ............................................... 6 11

2.1.8. AREA 47 ......................................................................................................................... 6 12

2.1.9. DOD PAYLOAD MANAGER ......................................................................................... 6 13

2.1.10. NASA LAUNCH VEHICLE AND HOSTING PLATFORMS ........................................ 6 14

2.1.11. OTHER GOVERNMENT LAUNCH VEHICLES AND HOSTING PLATFORMS ....... 6 15

2.1.12. COMMERCIAL LAUNCH VEHICLE AND HOSTING PLATFORMS ........................ 6 16

2.1.13. INTERNATIONAL PARTNER LAUNCH VEHICLE AND HOSTING PLATFORMS . 7 17

2.1.14. COMMON PLATFORM ............................................................................................... 7 18

2.1.15. SUBORBITAL MISSIONS ............................................................................................ 7 19

REFERENCE DOCUMENTS .............................................................................................. 7 20

3. CONTRACTOR TASKS ..............................................................................................................8 21

COMPLIANCE DOCUMENTS ........................................................................................... 8 22 PROGRAM MANAGEMENT ............................................................................................. 8 23

3.2.1. DHPSC PROGRAM MANAGEMENT ........................................................................... 8 24

3.2.2. CONTRACT STATUS REVIEW (CSRs) ......................................................................... 8 25

3.2.3. COST & SCHEDULE MANAGEMENT ......................................................................... 9 26

3.2.4. MEETINGS..................................................................................................................... 9 27

3.2.5. OL-S LAN MAINTENANCE ........................................................................................... 9 28

3.2.6. CYBERSECURITY ......................................................................................................... 9 29

3.2.6.1. SECURITY AND DATA MANAGEMENT ............................................................. 9 30

3.2.6.2. PERSONNEL CLEARANCES ................................................................................ 9 31

3.2.6.3. PHYSICAL SECURITY ........................................................................................ 10 32

3.2.6.4. INFORMATION PROTECTION .......................................................................... 10 33

3.2.7. PROPERTY, EQUIPMENT, MATERIAL ..................................................................... 10 34

3.2.7.1. DoD PROPERTY MANAGEMENT ..................................................................... 10 35

3.2.7.2. PAYLOAD ELEMENT LOGISTICS ..................................................................... 10 36

3.2.7.3. EQUIPMENT CALIBRATION ............................................................................. 10 37

3.2.8. FACILITIES ................................................................................................................. 11 38

3.2.8.1. PAYLOAD FACILITIES....................................................................................... 11 39

3.2.8.2. SECURE FACILITIES ......................................................................................... 11 40

3.2.9. CDRL DATA LISTING ................................................................................................. 11 41 SYSTEMS ENGINEERING AND TECHNICAL MANAGEMENT ................................ 11 42

3.3.1. PE INTEGRATION ...................................................................................................... 11 43

3.3.2. REQUIREMENTS DEFINITION ................................................................................. 12 44

FA8809-R-000X 2

UNCLASSIFIED

3.3.3. REQUIREMENTS VERIFICATION/TESTING ............................................................ 12 45

3.3.4. MISSION DESIGN, PLANNING, AND ANALYSIS ..................................................... 12 46

3.3.5. PAYLOAD ELEMENT HARDWARE AND SOFTWARE DEVELOPMENT ............... 12 47

3.3.6. COMMON PLATFORM DEVELOPMENT ................................................................. 12 48

3.3.7. INFORMATION AND CONFIGURATION MANAGEMENT...................................... 13 49

3.3.8. PAYLOAD ELEMENT OPERATIONS ......................................................................... 13 50

3.3.8.1. MISSION TRAINING ........................................................................................... 13 51

3.3.8.2. OPERATIONS PLANNING & OPERATION SUPPORT NETWORK ................ 13 52

3.3.8.3. PRE-LAUNCH PAYLOAD PROCESSING AND CHECKOUT .......................... 14 53

3.3.8.4. MISSION OPERATIONS SUPPORT ................................................................... 14 54

3.3.8.5. POST MISSION HARDWARE RECOVERY ........................................................ 14 55

OTHER SERVICES ........................................................................................................... 14 56

3.4.1. COMMERCIAL LAUNCH SERVICES......................................................................... 14 57

3.4.2. RIDESHARE SERVICES .............................................................................................. 14 58

3.4.3. SPECIAL STUDIES...................................................................................................... 14 59

4. ANNEX 1 SUPPORT FOR SPACE TEST PROGRAM (STP) MISSIONS AND PAYLOADS ..15 60

NASA LAUNCH VEHICLE AND HOSTING PLATFORMS .......................................... 15 61

4.1.1. No Specific Requirements at This Time........................................................................ 15 62

OTHER GOVERNMENT LAUNCH VEHICLES AND HOSTING PLATFORMS ......... 15 63

4.2.1. No Specific Requirements at This Time........................................................................ 15 64

COMMERCIAL LAUNCH VEHICLE AND HOSTING PLATFORMS .......................... 15 65

4.3.1. No Specific Requirements at This Time........................................................................ 16 66

INTERNATIONAL PARTNER LAUNCH VEHICLE AND HOSTING PLATFORMS . 16 67

4.4.1. No Specific Requirements at This Time........................................................................ 16 68

COMMON PLATFORM .................................................................................................... 16 69

4.5.1. No Specific Requirements at This Time........................................................................ 16 70

SUBORBITAL MISSIONS ................................................................................................ 16 71

4.6.1. No Specific Requirements at This Time........................................................................ 16 72

COMMERCIAL/RIDESHARE .......................................................................................... 16 73

4.7.1. No Specific Requirements at This Time........................................................................ 16 74

SPECIAL STUDIES ........................................................................................................... 16 75

4.8.1. No Specific Requirements at This Time........................................................................ 17 76

5. ANNEX 2 TRANSITION OUT OF THE INCUMBENT CONTRACTOR.................................17 77

PERSONNEL .......................................................................................................................... 17 78 TRANSITION OF RECORDS AND DATA .................................................................................. 17 79 TRANSITION OF PROJECTS AND SYSTEMS ............................................................................ 17 80 CONTINUITY OF OPERATIONS .............................................................................................. 17 81

6. ANNEX 3 TRANSITION IN OF THE NEW CONTRACTOR ...................................................18 82

PERSONNEL .......................................................................................................................... 18 83 TRANSITION OF RECORDS AND DATA .................................................................................. 18 84 TRANSITION OF PROJECTS AND SYSTEMS ............................................................................ 18 85 CONTINUITY OF OPERATIONS .............................................................................................. 18 86

7. ANNEX 4 AEROSPACE FFRDC ENABLING REQUIREMENT ............................................19 87

FA8809-R-000X 3

UNCLASSIFIED

8. ANNEX 5: ASSOCIATE CONTRACTOR AGREEMENTS ......................................................22 88

9. ANNEX 6: ACQUIRING IN-SCOPE TECHNICAL SERVICES ..............................................23 89

FA8809-R-000X 4

UNCLASSIFIED

DEPARTMENT OF DEFENSE (DOD) HUMAN-RATED PAYLOAD 92

SUPPORT CONTRACT - (DHPSC) STATEMENT OF WORK (SOW) 93

1. SCOPE AND OBJECTIVES 94

This Statement of Work (SOW) provides for contractor services to support DoD payloads on: 95 National Aeronautics and Space Administration (NASA) launch vehicles and hosting platforms; 96 other Government launch vehicles and hosting platforms; Commercial launch vehicles and 97 hosting platforms; suborbital missions; and International Partner launch vehicle and hosting 98 platforms, that can be utilized to complete a DoD payload’s mission objectives. See paragraph 99

2.1 for definitions. The sensitivity and classification of the tasks on this contract will range from 100 unclassified/publicly releasable through to Top Secret / Sensitive Compartmented Information 101 per the DD254. The Contractor is responsible to perform the following tasks in this SOW for the 102 missions listed in Annex 1 103

Integrate designated payload elements onto designated missions 104 Operate designated payload elements on designated missions to include hosted and free-105 flyer missions 106 Design, develop and fabricate ground and flight hardware (hosted and free-flyer) and 107 software in support of DoD missions 108 Design, develop, test and support Common Platform hardware and software for current 109 and future missions. 110 Provide engineering analyses including development of thermal and structural models 111 Perform hardware and software modifications of developed flight and ground systems 112 and Payload Elements (PEs) when applicable 113 Conduct payload element testing at various locations 114 Provide logistics support of payload elements, ground support equipment, parts and 115 materials including storage, routine maintenance to keep hardware in serviceable 116 condition and transportation 117

Maintain the DoD Payload Operations Control Center (POCC) to include Tele-science 118 and Resource Kit (TReK), and other flight operations software and the Houston Space 119 Operations Ground System (HSOGS) 120

Provide maintenance and modifications as needed to sustain the Area 47 secure facility to 121 maintain the area in operational condition per the requirements of ICD 705 and the 122

DD254 123

Perform program support including, configuration and document management and 124 Government Furnished Equipment (GFE) management 125

Secure commercial launch services and provide special studies for DoD payloads 126 Maintain, repair, recommend equipment and provide daily support to maintain the DoD 127

Payloads Office Local Area Network (LAN) and offsite and virtual infrastructure 128 Support and maintain Cybersecurity processes on Automated Data Processing 129

Equipment, flight hardware, HSOGS and ground systems as needed. 130 Provide Program Management to include overseeing the implementation and 131 management of the contract and its subcontracts and subcontractors 132

FA8809-R-000X 5

UNCLASSIFIED

Provide services primarily at Johnson Space Center (JSC) in Houston, Texas with 133 worldwide travel to various test and launch sites and Principal Investigator (PI) locations 134

2. REFERENCES 135

DEFINITIONS 136

2.1.1. PAYLOAD ELEMENT (PE) 137

Complement of resources carried by mission defined in 2.1.10 thru 2.1.13 performing or 138 contributing to a DoD mission. Resources may include ground support equipment, and/or 139 hardware developed by the contractor in support of a DoD payload element for flight, ground 140 operations or testing. PEs will be identified by the DoD Payload Manager and may be classified 141 as primary or secondary payloads. 142

2.1.2. PRINCIPAL INVESTIGATOR (PI) 143

Person(s) or organization(s), designated by the PE sponsor, tasked with developing and/or 144 procuring the PE hardware, providing technical expertise during the DoD payload mission, and 145 performing analyses on the data gathered by the PE. 146

2.1.3. CONTRACTING OFFICER’S REPRESENTATIVE (COR) 147

DoD person designated by the Contracting Officer to act as an authorized representative in 148 monitoring contract performance. 149

2.1.4. DHPSC PROGRAM MANAGER (PM) 150

Contractor person designated to oversee the implementation and management of the DHPSC. 151

2.1.5. DoD OPERATIONS TEAM (DOT) 152

Consists of government personnel, PE Principal Investigators, The Aerospace Corporation, 153 Systems Engineering and Technical Advisory (SETA) contractors, and DHPSC contractor 154 personnel. 155

2.1.6. DoD PAYLOAD OPERATIONS CONTROL CENTER (POCC) 156

The POCC provides operations support for PE’s on the ISS, free-flyer missions, missions 157 operated on other commercial platforms, and missions operated on Government platforms. The 158 DoD POCC and remote PI POCCs conduct operations for PE missions using HSOGS systems or 159 NASA tools for ISS Operations. The DoD POCC is located in DoD office space in Bldg 30M. 160 A DoD POCC Annex shall be located in Area 47 for missions operating with secure 161 requirements per the DD254. For ISS missions the systems are PC workstation based running a 162 commercial operating system and NASA’s TReK tools. The POCC has connectivity to JSC’s 163 Mission Control Center systems provided by NASA such as the voice loop system. The POCC 164 workstations share the room’s display to show mission displays on overhead screens and to 165

FA8809-R-000X 6

UNCLASSIFIED

communicate with remote POCCs and operations centers. The POCC may utilize cloud-based 166 systems at various levels of security per the DD254 to host operations systems and PE data. 167

2.1.7. HOUSTON SPACE OPERATIONS GROUND SYSTEM 168

Is defined as contractor developed or supported systems to conduct flight operations of DoD 169 missions, typically for free-flyer or hosted platform missions. Typically, these systems consist of 170 ground radios, computers, servers, network equipment, firewalls, encryption devices, ancillary 171 hardware, software, and all related documentation. HSOGS will be connected to a network that 172 provides space-to-ground connectivity to/from the DoD mission. The connection may be over a 173 terrestrial network or accessed via a cloud service. HSOGS will be located in the DoD POCC or 174 the POCC Annex. HSGOGS may be migrated to a cloud environment. The HSOGS provides 175 the ability to disseminate PE data to the PIs. HSOGS will be accreditable under NIST 800-37. 176

2.1.8. AREA 47 177

Is defined as a secure area which meets the requirements of ICD 705, and support discussions, 178 meetings, technical work, and operations on an as needed basis. Area 47 shall support the 179 requirements of the DD254. 180

2.1.9. DOD PAYLOAD MANAGER 181

The DoD Human Spaceflight Payloads Office’s Director or delegated official. 182

2.1.10. NASA LAUNCH VEHICLE AND HOSTING PLATFORMS 183

NASA Launch Vehicle and Hosting Platforms are comprised of the full NASA capability to 184 launch into and operate within the space environment, to include (but not limited to): 185 Commercial Resupply Services, Commercial Crew Program, Commercial Lunar Payload 186 Services, Artemis Program, the Space Launch System (SLS), the International Space Station, 187 Commercial LEO Destinations, Lunar Gateway and other lunar programs, and any NASA 188 managed launch and rideshare capabilities. 189

2.1.11. OTHER GOVERNMENT LAUNCH VEHICLES AND HOSTING 190

PLATFORMS 191

Other Government Launch Vehicle and Hosting Platforms are comprised of non-NASA 192 capability to launch into and operate within the space environment provided by other Gov’t 193 agencies, to include (but not limited to): COCOM missions, DoD Space Test Program missions, 194 Gov’t rideshare missions, Government hosted platforms such as but not limited to Long Duration 195 Propulsive ESPA (LDPE) missions, or other Government platforms. 196

2.1.12. COMMERCIAL LAUNCH VEHICLE AND HOSTING 197

PLATFORMS 198

Commercial Launch Vehicle and Hosting Platforms are comprised of commercially available 199 capability to launch into and operate within the space environment, to include (but not limited 200 to): Commercial launch services, commercial rideshare opportunities, commercial manned and 201

FA8809-R-000X 7

UNCLASSIFIED

unmanned space stations, commercial hosting platforms, commercial suborbital services and 202 missions, 203

2.1.13. INTERNATIONAL PARTNER LAUNCH VEHICLE AND 204

HOSTING PLATFORMS 205

International Partner Launch Vehicle and Hosting Platforms are comprised of the full capability 206 to launch into and operate within the space environment provided by International Partners to 207 NASA programs to include (but not limited to): JAXA launch capabilities such as the HII 208 Transfer Vehicle (HTV-X) and ISS Hosting capability, ESA future launch capabilities and ISS 209 Hosting capability, Russian launch capabilities such as Progress/Soyuz and ISS Hosting 210 capability. This includes future IP involvement in NASA programs such as Artemis, Lunar 211 Gateway, and lunar programs. 212

2.1.14. COMMON PLATFORM 213

The Common Platform (CP) consists of a flight computer that acts as an interface between a host 214 and the payload and its experiments and subsystems; power conversion, filtering, and switching 215 to provide power to individual experiments and payload subsystems; inhibit capability to control 216 catastrophic hazards; organic position, timing, and attitude determination capabilities to pass to 217 experiments to provide location and pointing services; provisions to implement mission specific 218 hardware requirements; support for encryption; and related flight and ground software. 219 Simulators and documentation for PIs developing PEs. 220

2.1.15. SUBORBITAL MISSIONS 221

Suborbital missions include Gov’t and commercial reduce gravity aircraft based flights, and 222 commercial suborbital manned and unmanned rocket assisted flights. 223

REFERENCE DOCUMENTS 224

The contractor may use information contained in the following documents as a guide or as 225 reference documents in accomplishing the tasks contained in this contract. This should not be 226 considered an all-inclusive list of documents that may be required during payload integration 227 tasks and each document maybe tailored for the mission, as applicable. More recent versions of 228 these documents should be used as appropriate. 229

Title Document / Applicable Requirements Verification Matrix

(AVM)

To Be Supplied

FA8809-R-000X 8

UNCLASSIFIED

3. CONTRACTOR TASKS 233

The contractor shall accomplish the following tasks: (1) Program Management; (2) Systems 234 Engineering and Technical Management; and (3) Other Services. 235

COMPLIANCE DOCUMENTS 236

Contractor shall determine requirements from the latest revisions of documents listed in 2.2 237 REFERENCE DOCUMENTS as applicable to each PE. For those launch or hosting capabilities 238 where integration requirements are under development, the contractor shall identify and compile 239 a comprehensive list of compliance documents as they become available. 240

PROGRAM MANAGEMENT 241

3.2.1. DHPSC PROGRAM MANAGEMENT 242

The DHPSC Program Manager (PM) shall be responsible for overseeing the implementation and 243 management of the DHPSC and their subcontracts and subcontractors. The PM shall be the 244 single-point-of-contact for program management and the customer’s interface for DHPSC 245 program management concerns. The PM shall be responsible for technical, cost, and schedule 246 performance and has responsibility and authority to manage and direct all DHPSC team 247 members and their subcontractors, regardless of contractor affiliation. The PM shall establish 248 and manage a Risk Management program covering all activities under DHPSC. The Risk 249 Management program shall include identification, analysis, mitigation planning, mitigation plan 250 implementation, and tracking and should cover the total life cycle of the program. The PM will 251 work primarily with the DoD DHPSC COR. The contractor shall provide Operations Security 252 (OPSEC) protection for all sensitive/critical information in accordance with the DD254 Contract 253 Security Classification Specification from unclassified/publicly releasable through to Top Secret 254 / Sensitive Compartmented Information. The contractor shall implement a quality assurance 255 system that is capable of independently assessing that hardware and software developed or used 256 on this contract meets the specified performance and design requirements. The PM shall be 257 responsible for ensuring all PE mission related activities are adequately planned, implemented, 258 and completed such that project meet cost, schedule and performance criteria. The PM will 259 identify a Project Manager (PM), Payload Integration Engineer(s) (PIE) and Safety Engineer 260 (SE) for each PE. The PM and PIEs will interface directly with government personnel, Advisory 261 and Assistance Services (A&AS) personnel, The Aerospace Corporation (FFRDC) and PIs. 262 (CDRL A007, Status Reports; CDRL A008, Schedules) 263

3.2.2. CONTRACT STATUS REVIEW (CSRs) 264

Conduct CSRs quarterly no more than 10 miles from JSC. Provide progress, status, costs, 265 schedule, risks on hardware design, development, integration, operations, logistics, training, for 266 each PE and major task. Provide a breakout of DHPSC consolidated resources and how they are 267 allocated to each PE and major task. Provide recommendations to the DoD PM as needed. 268 (CDRL A007, Status Reports) 269

FA8809-R-000X 9

UNCLASSIFIED

3.2.3. COST & SCHEDULE MANAGEMENT 270

Maintain a cost and schedule system that monitors contract performance and ensures cost and 271 schedule control. (CDRL A009 Performance & Cost Report). The Contractor shall identify and 272 implement cost saving practices and procedures throughout the execution of the contract and 273 shall develop and maintain Integrated Mission Schedules that reflect critical mission milestones 274 pertinent to DoD PEs and other major tasks. (CDRL A008, Schedules) 275

3.2.4. MEETINGS 276

Conduct and support technical reviews and PE status reviews with the PIs, contractors, and other 277 Government and civilian agencies to exchange information relevant to integration, hardware 278 design and development, logistics, and operation activities. Generate meeting minutes for key 279 meetings such as design reviews or major decision-making meetings as agreed to with the COR. 280 (CDRL A010, Meeting Minutes) 281

3.2.5. OL-S LAN MAINTENANCE 282

Maintain, repair, recommend equipment, and provide daily support to maintain the DoD 283 Payloads Office LAN and offsite infrastructure. Ensure compatibility and compliance with DoD, 284 Space Force and NASA policies and practices as applicable. Ensure compliance with the 285 applicable security plan(s). Ensure interface with NASA help desk and service request system. 286 (CDRL A004, LAN/POCC/HSGC Configuration Log) 287

3.2.6. CYBERSECURITY 288

Apply Cybersecurity requirements defined in NIST 800-37 (and subordinate documents) and/or 289 NASA Policy Directive 2810.1E (and subordinate documents) to existing and new programs as 290 applicable. Requirements may flow from NASA or DoD Cybersecurity policies and 291 requirements based on the specific needs of the program. Maintain existing IT Security Plans or 292 assist in the modification of existing or development of new IT Security Plans as needed such as; 293 the OL-S LAN/Desktop systems including the POCC; the Houston Space Operations Ground 294 System; or other IT systems such as Payload Elements when needed. Account for supply chain 295 management and risks. Use Gov’t provided threat information to inform security systems 296 engineering. (CDRL A001, PE Documentation). 297

3.2.6.1. SECURITY AND DATA MANAGEMENT 298

Manage the security and data handling responsibilities across the contract, and ensure personnel 299 comply with Government-provided training and comply with Cybersecurity guidance as outlined 300 in the contract; DoD 5220.22-M, The National Industrial Security Program Operating Manual 301 (NISPOM); and other security guidance as required by the National Industrial Security Program 302 (NISP), DoD, and the US Space Force. 303

3.2.6.2. PERSONNEL CLEARANCES 304

Provide cleared personnel in accordance with the NISP and other security guidance provided and 305 ensure all personnel on this contract comply with mission specific Security Classification Guide 306

FA8809-R-000X 10

UNCLASSIFIED

(SCG) and any other applicable SCGs. Other SCGs may vary by project and will be provided by 307 the Contracting Officers Representative (COR) or Program Manager (PM) as required. 308

3.2.6.3. PHYSICAL SECURITY 309

Perform physical security duties of contractor workspaces. 310

3.2.6.4. INFORMATION PROTECTION 311

Use and protect sensitive, non-public information from unauthorized disclosure IAW DoDI 312

8582.01. Use and disclose such information only for the purpose of performing this contract and 313 do not use or disclose such information for any personal or commercial purpose. Obtain 314 permission of the Government Program Manager before disclosing/discussing such information 315 with a third party. Return and/or electronically purge, upon Government. (CDRL A001, PE 316 Documentation) 317

3.2.7. PROPERTY, EQUIPMENT, MATERIAL 318

3.2.7.1. DoD PROPERTY MANAGEMENT 319

Develop and/or maintain a database containing DoD property, equipment, material, 320 consumables, and equipment shipping and checkout status. Assign, order, and attach DoD part 321 numbers or IUID tags (as applicable) to each PE. As needed maintain inventory management 322 system for non-expendable DoD equipment to ensure accountability of DoD hardware, PE, 323 CAM, GFE, GFM, and/or GSE. Maintain a storage located within 10 miles of JSC. The storage 324 facilities shall maintain security and environmental controls consistent with generally acceptable 325 industry standards for the storage of Class I flight hardware. The storage facility shall be able to 326 accommodate the equipment on the GFE list, shipping containers for ELC-sized payloads, 327 experimenters hardware delivered for payload element integration and related shipping 328 containers and support GSE. Laboratory space describe in the Base Support Plan may be used 329 for storage on a non-interference basis. Excess property per the contract instructions. (CDRL 330 A003, PE Management; CDRL A013, GFM Reporting) 331

3.2.7.2. PAYLOAD ELEMENT LOGISTICS 332

Receive, clean, package, pre-ship, ship PE flight hardware and ground support equipment. 333 Inspect PE for any missing parts and damage. Identify and document any discrepancies or 334 incidents involving shipping of PE equipment to the government. Store PE in DoD facilities, 335 contractor storage facilities, or NASA bonded storage. Acquire, fabricate, repair, and/or replace 336 small PE parts and/or components as required to support PE such as light machining, 337 connector/soldering repair, small brackets, etc. (CDRL A003, PE Management) 338

3.2.7.3. EQUIPMENT CALIBRATION 339

Maintain an equipment calibration inventory list. Ensure all equipment is maintained and 340 calibrated to the manufacturer’s specification and at the frequency requirement per type of 341 component. This may include commercial procurement of calibration services for DoD 342 equipment requiring calibration. (CDRL A003, PE Management) 343

FA8809-R-000X 11

UNCLASSIFIED

3.2.8. FACILITIES 344

Perform maintenance, installation, system operations, and enhancement/upgrades of government 345 owned facilities and areas as required. Facilities shall provide protection for all sensitive/critical 346 information in accordance with the DD254 Contract Security Classification Specification - from 347 Unclassified/publicly releasable through Top Secret/Sensitive Compartment information. These 348 facilities may include appropriate clean-room and security requirements for current and future 349 payloads. The facilities shall maintain security and environment controls consistent with 350 generally acceptable industry standards for storage of Class I flight hardware as required. The 351 facility shall be able to accommodate the equipment on the GFE list, shipping containers for 352 ELC-sized payloads, experimenters hardware delivered for payload element integration and 353 related shipping containers and support GSE as required by current and future payloads. Needs 354 may vary by mission being executed at a given time. (CDRL A003, PE Management) 355

3.2.8.1. PAYLOAD FACILITIES 356

Maintain equipment, clean room, and consumables used in DoD laboratories as defined in the 357 Base Support Plan or as required at other temporary physical locations, used in support of PE 358 and Common Platform development, integration and test. When tasked, maintain laboratory 359 space capable of supporting PE/Common Platform per the DD254 including related IT systems. 360 Identify and acquire needed repairs, GSE, tools, and consumables needed to support DoD 361 payload processing (CDRL A003, PE Management) 362

3.2.8.2. SECURE FACILITIES 363

When tasked, provide maintenance and modifications as needed to sustain the Area 47 secure 364 facility to maintain the area in operational condition per the requirements of ICD 705 and the 365 DD254. When tasked provide for modification of secure laboratory spaces to conduct missions 366 with security requirements per the DD254. Support initial and on-going accreditation of secure 367 facilities and IT systems. Support the installation and on-going management of secure IT 368 systems. (CDRL A003, PE Management) 369

3.2.9. CDRL DATA LISTING 370

Quarterly, the contractor will provide an all-inclusive list of all the CDRLs they have delivered 371 to date. (CDRL A012, CDRL Data Listing) 372

SYSTEMS ENGINEERING AND TECHNICAL MANAGEMENT 373

3.3.1. PE INTEGRATION 374

Provide services, support, and development necessary for the successful integration of PEs onto 375 the designated space flight missions. Current missions are listed in Annex 1 and will be updated 376 per Annex 6 as significant changes occur, as directed by the Government. Specific security 377 requirements for each PE shall be included in Annex 1 as applicable. (CDRL A001, PE 378 Documentation). Develop and maintain Integration Schedules respective to each PE. (CDRL 379 A010, Schedules) 380

FA8809-R-000X 12

UNCLASSIFIED

3.3.2. REQUIREMENTS DEFINITION 381

Identify integration, interfaces, functional, safety, and security requirements that the PE or in-382 house developed hardware must be designed to in order to be compatible with the designated 383 mission PE(s), PI(s) requirements, mission objectives, and launch vehicle and hosting platform. 384 (CDRL A001, PE Documentation) 385

3.3.3. REQUIREMENTS VERIFICATION/TESTING 386

Provide technical support to verify the PE and in-house developed hardware/software satisfies 387 designated space flight integration interfaces, functional, safety, and security requirements. 388 Coordinate and plan verification activities including documentation, training, analysis, testing, 389 security testing as applicable, and hardware development/processing. Evaluate design 390 documents, analyses, test plans and procedures, and test results. Identify design deficiencies and 391 make technical recommendations to satisfy designated space flight interface and safety 392 requirements. Verify that design, analyses, test plans and procedures, and test results comply 393 with requirements: mechanical, structural, loads, dynamics, vibro-acoustics, avionics, electrical, 394 electromagnetic compatibility, contamination, thermal, toxicity, and flammability requirements. 395 Provide design recommendations to maximize space flight capability and safety compliance. 396 Review and provide inputs for the payload interface documentation. (CDRL A001, PE 397 Documentation; CDRL A008, Schedules) 398

3.3.4. MISSION DESIGN, PLANNING, AND ANALYSIS 399

Support manifesting activities and provide mission design and planning support for manifesting 400 and PE assessment. Analyze space flight mission opportunities and recommend PEs for flight 401 assignments. Perform PE mission-planning analyses including space flight capability/ 402 compatibility, launch window studies, proximity operations, opportunity analyses, attitude and 403 pointing studies, thermal compatibility, trajectory generation, ISS research planning, and 404 timeline generation. Perform systems engineering analysis to maximize available space launch 405 opportunities, cost effectiveness, and faster deployment of new technologies/capabilities to the 406 DOD operational community. (CDRL A008, Schedules; CDRL A001, PE Documentation) 407

3.3.5. PAYLOAD ELEMENT HARDWARE AND SOFTWARE 408

DEVELOPMENT 409

Acquire, design, fabricate, repair, and/or replace PE support hardware and software (ground 410 and/or flight) as directed. In-house hardware and software shall be developed in accordance with 411 applicable standards of the respective hosting and launch vehicles for which it is intended. The 412 Contractor shall have the ability to conduct analyses (e.g., structural, and thermal) necessary to 413 determine compatibility with the target space transportation capability and hosting platform. The 414 requirements of 3.3.1, 3.3.2, and 3.3.3 shall apply to in-house developed hardware as applicable. 415 (CDRL A001, PE Documentation). 416

3.3.6. COMMON PLATFORM DEVELOPMENT 417

Acquire, design, fabricate, repair, modify, and/or replace Common Platform hardware and 418 software (ground and/or flight) components as directed. The contractors shall facilitate the 419

FA8809-R-000X 13

UNCLASSIFIED

integration of PE’s to the CP through the use of simulators, documentation, access to integration 420 facilities and meetings with PIs developing PEs. The contractor shall develop external interfaces 421 for the CP to existing and emerging hosting platforms to facility the efficient integration of DoD 422 PE’s. The Common Platform shall be developed IAW the requirements of the hosting platform 423 and the needs of the integrated PEs. The requirements of 3.3.1, 3.3.2, and 3.3.3 shall apply to in-424 house developed hardware as applicable. (CDRL A001, PE Documentation). 425

3.3.7. INFORMATION AND CONFIGURATION MANAGEMENT 426

Process and archive PE related documents and digital products as determined by the government 427 lead or PIE. Process and track change requests, discrepancy notices, and procedure change 428 requests. Maintain a Payload Element Database document. (CDRL A003, PE Management) 429 Provide resources for scanning and electronic archiving of PE data as needed. Maintain currency 430 of space flight integration documentation. Documentation can be physical or digital. Implement 431 a configuration management process that can identify/define baseline configurations, control 432 changes, and report status of items under control (documents, drawings, hardware, software, 433 digital models, etc). (CDRL A001, PE Documentation) 434

3.3.8. PAYLOAD ELEMENT OPERATIONS 435

3.3.8.1. MISSION TRAINING 436

Determine PE mission-specific training requirements. Train crewmembers and NASA Flight 437 Control Team (FCT) on DoD PEs. Train designated STP and PI personnel on Mission Control 438 Center (MCC) operations such as the customer support room facilities, DoD POCC, mission 439 console operations, mission planning hardware and software, and Houston Space Ground 440 Operations System. Provide technical support for mission specific training. Provide training 441 tools and aids, including models and mockups. Provide support for simulations, rehearsals, and 442 other PE related exercises. (CDRL A001, PE Documentation) 443

3.3.8.2. OPERATIONS PLANNING & OPERATION SUPPORT 444

NETWORK 445

Perform maintenance, installation, system operations, and enhancement/upgrades of Government 446 furnished computer hardware and software. Maintain the DoD Payload Operations Control 447 Center (POCC) infrastructure, to include flight analysis tools and other tools as required to meet 448 mission objectives to include Tele-science Resource Kit and other ground control systems tools 449 for planning and commanding of on-orbit payloads. Maintain POCC and the Houston Space 450 Ground Operations Ground System to include DoD hardware, software, documentation, and 451 servers located at JSC and at off-site locations within Houston TX and outside the geographic 452 area. Ensure GFE hardware, software, and interfaces are compatible with designated space flight 453 systems. Maintain POCC and the Houston Satellite Ground Station configuration. Ensure 454 operational readiness of the DoD POCC and the Houston Space Ground Operations Ground 455 System to include the development and modification of User’s Guides. Identify any deficiencies 456 or incompatibilities and provide recommendations and corrective actions. Recommend and 457 install hardware and software enhancements/upgrades to the mission-planning/support. (CDRL 458 A001, PE Documentation; CDRL A005, POCC User’s Guide) 459

FA8809-R-000X 14

UNCLASSIFIED

3.3.8.3. PRE-LAUNCH PAYLOAD PROCESSING AND CHECKOUT 460

Plan for pre-launch processing activities. Develop and implement pre-launch procedures for 461 each PE IAW host base/facility regulations and requirements. Conduct and support PE build up, 462 tests such as functional tests, interface tests, troubleshooting, anomaly resolution, and PE space 463 flight integration activities. (CDRL A002, Mission Processing Procedures) 464

3.3.8.4. MISSION OPERATIONS SUPPORT 465

Provide technical support as a member of the DOT during the launch countdown and continuing 466 through operations, recovery/disposal activities for DoD payload missions. Provide continued 467 technical support (crew/on-orbit operations, technical troubleshooting, re-planning) for long-468 duration payloads. Monitor mission activities, interface with NASA or designated space 469 capability FCT, provide PE data, provide real-time mission analysis of PE, resolve real-time PE 470 anomalies, and provide re-planning of mission activities. Maintain the DOT mission log and 471 status boards and inform the mission director of mission status. (CDRL A006, Mission 472 Operations Support Plan) 473

3.3.8.5. POST MISSION HARDWARE RECOVERY 474

Plan for post mission processing activities. Provide for post mission PE recovery and post 475 mission data retrieval. Develop and implement post mission procedures for each PE IAW host 476 base/facility regulations and requirements. (CDRLs A002, Mission Processing Procedures; 477 (CDRL A003, PE Management) 478

OTHER SERVICES 479

3.4.1. COMMERCIAL LAUNCH SERVICES 480

When directed, secure commercial launch services for the launch of DoD payloads per the most 481 advantageous terms and conditions available. Manage the service contract directly with the 482 launch provider per the needs of the PE. Adhere to all applicable requirements of the service 483 provider for the integration of DoD payloads. Develop processes and procedures as needed to 484 integrate payloads to new commercial launch provider vehicles. Satisfy the requirements of 485 SOW section 3.3.1, 3.3.2, and 3.3.3 as needed to satisfy the requirements of the PE. 486

3.4.2. RIDESHARE SERVICES 487

When directed, satisfy the requirements of SOW sections 3.3.1, 3.3.2, and 3.3.3 for secondary 488 payloads on Launch Vehicles secured by the Government. Such launch vehicles shall be either 489 US domestic or foreign owned/operated. 490

3.4.3. SPECIAL STUDIES 491

Conduct special studies as directed by DoD Payload Manager. (CDRL A011, Special Studies & 492 Projects) 493

FA8809-R-000X 15

UNCLASSIFIED

4. ANNEX 1 SUPPORT FOR SPACE TEST PROGRAM (STP) MISSIONS 494

AND PAYLOADS 495

This Annex shall list current missions requiring support services under the DHPSC. At the start 496 of the DHPSC, this Annex will list the current/on-going efforts that will be transferred from the 497 Incumbent DoD Human Spaceflight Payloads Task Order (DHSTO) contractor to the New 498 Contractor. After this transition period, this Annex will modified to add new missions, or 499 modified to change existing missions as the change method to add/modify work on the DHPSC. 500 This Annex will be a ‘living’ annex that will reflect as any given point the work on the contract. 501

NASA LAUNCH VEHICLE AND HOSTING PLATFORMS 502

Provide all services necessary IAW this SOW for the successful integration, launch, operations 503 and disposal of STP experiments utilizing to NASA Launch Vehicle and Hosting Platforms are 504 comprised of the full NASA capability to launch into and operate within the space environment, 505 to include (but not limited to): Commercial Resupply Services, Commercial Crew Program, 506 Commercial Lunar Payload Services, Artemis Program, the Space Launch System (SLS), the 507 International Space Station, Commercial LEO Destinations, Lunar Gateway and other lunar 508 programs, and any NASA managed launch and rideshare capabilities. 509

4.1.1. No Specific Requirements at This Time 510

OTHER GOVERNMENT LAUNCH VEHICLES AND HOSTING 511

PLATFORMS 512

Provide all services necessary IAW this SOW for the successful integration, launch, operations 513 and disposal of STP experiments utilizing other Government Launch Vehicle and Hosting 514 Platforms are comprised of non-NASA capability to launch into and operate within the space 515 environment provided by other Gov’t agencies, to include (but not limited to): COCOM 516 missions, DoD Space Test Program missions, Gov’t rideshare missions, Government hosted 517 platforms such as but not limited to Long Duration Propulsive ESPA (LDPE) missions, or other 518 Government platforms. 519

4.2.1. No Specific Requirements at This Time 520

COMMERCIAL LAUNCH VEHICLE AND HOSTING PLATFORMS 521

Provide all services necessary IAW this SOW for the successful integration, flight and operations 522 of STP experiments utilizing, Commercial Launch Vehicle and Hosting Platforms are comprised 523 of commercially available capability to launch into and operate within the space environment, to 524 include (but not limited to): Commercial launch services, commercial rideshare opportunities, 525 commercial manned and unmanned space stations, commercial hosting platforms, commercial 526 suborbital services and missions. 527

FA8809-R-000X 16

UNCLASSIFIED

4.3.1. No Specific Requirements at This Time 528

INTERNATIONAL PARTNER LAUNCH VEHICLE AND HOSTING 529

PLATFORMS 530

Provide all services necessary IAW this SOW for the successful integration, flight and operations 531 of STP experiments utilizing International Partner Launch Vehicle and Hosting Platforms are 532 comprised of the full capability to launch into and operate within the space environment 533 provided by International Partners to NASA programs to include (but not limited to): JAXA 534 launch capabilities such as the HII Transfer Vehicle (HTV-X) and ISS Hosting capability, ESA 535 future launch capabilities and ISS Hosting capability, Russian launch capabilities such as 536 Progress/Soyuz and ISS Hosting capability. This includes future IP involvement in NASA 537 programs such as Artemis, Lunar Gateway, and lunar programs. 538

4.4.1. No Specific Requirements at This Time 539

COMMON PLATFORM 540

The Common Platform (CP) consists of a flight computer that acts as an interface between a host 541 and the payload and its experiments and subsystems; power conversion, filtering, and switching 542 to provide power to individual experiments and payload subsystems; inhibit capability to control 543 catastrophic hazards; organic position, timing, and attitude determination capabilities to pass to 544 experiments to provide location and pointing services; provisions to implement mission specific 545 hardware requirements; support for encryption; and related flight and ground software. 546 Simulators and documentation for PIs developing PEs. 547

4.5.1. No Specific Requirements at This Time 548

SUBORBITAL MISSIONS 549

Provide all services necessary IAW this SOW for the successful integration, flight and operations 550 of STP experiments utilizing suborbital missions include Gov’t and commercial reduce gravity 551 aircraft based flights, and commercial suborbital manned and unmanned rocket assisted flights. 552

4.6.1. No Specific Requirements at This Time 553

COMMERCIAL/RIDESHARE 554

Provide all services necessary IAW this SOW for the successful integration, launch, operations 555 and disposal of STP experiments deployed utilizing commercial or government rideshare 556 opportunities through, to include but not limited to, Nanoracks, and Multiple User System for 557 Earth Sensing (MUSES). 558

4.7.1. No Specific Requirements at This Time 559

SPECIAL STUDIES 560

Special studies and tasks that enhance the effectiveness of the Human Spaceflight Payloads 561

FA8809-R-000X 17

UNCLASSIFIED

Office or the DHSTO contractor to perform its mission are authorized under this Annex. These 562 tasks are limited in nature and will require the approval of the DHSTO Program Manager and the 563 DoD Payload Manager. Support/perform special or preliminary integration activities and studies 564 of potential flight opportunities. 565

4.8.1. No Specific Requirements at This Time 566

5. ANNEX 2 TRANSITION OUT OF THE INCUMBENT CONTRACTOR 567

This contract represents a Government continuing need and it is anticipated that, upon 568 completion or termination of this contract, another contract for substantially the same effort will 569 be executed. This Annex establishes the Transition Out from the incumbent to the new 570 contractor. Requirements for the new contractor to Transition In are located in ANNEX 3. The 571 incumbent contractor agrees to cooperate fully with the Government and any new contractor to 572 ensure an orderly transition at the end of this contract. This period is known as the Transition 573 Period and will be the final 60 calendar days of this contract. (CDRL A007, Status Reports) The 574 Contractor shall: 575

Personnel 576

Make available to the Contracting Officer, upon request, the names, job titles, and duties of all 577 employees who have recently or currently worked under this contract. 578

Transition of Records and Data 579

The incumbent contractor agrees to preserve and make available to the Contracting Officer, upon 580 request, copies of all records, CAD files/drawings, digital models, simulations and analyzes, 581 documentation, software, source code, and hardware developed or acquired under this contract or 582 preceding contracts for this effort, regarding performance of the work required by this contract. 583 The incumbent contractor will facilitate the orderly transition of data, records, documentation, 584 CAD files/drawings, digital models, simulations and analyzes, source code, work products, 585 knowledge, and operations support to the new contractor. 586

Transition of Projects and Systems 587

Provide, upon request, support for a maximum of 16 new contractor employees during the 588 Transition Period to orderly transition the responsibilities of all on-going projects and systems to 589 new contractor personnel. This includes IT systems developed under this contract or preceding 590 contracts regardless of their location, GSE, GFE, test equipment, and hardware under 591 development to the new Contractor. During the transition period, maintain integration and 592 management support to on-going projects until the new contractor assumes responsibility for 593 each project 594

Continuity of Operations 595

During the transition period, maintain Continuity of Operations for on-orbit payloads until the 596 new Contractor assumes responsibility for operations. 597

FA8809-R-000X 18

UNCLASSIFIED

6. ANNEX 3 TRANSITION IN OF THE NEW CONTRACTOR 599

This Annex establishes the Transition In of the new contractor from the incumbent contractor. 600 Requirements for the incumbent contractor to Transition Out are located in ANNEX 2.