Attach 1 - Tracking Layer TO WFOV SOW (Draft).pdf

Solicitation HQ085020R0003 Section C

STATEMENT OF WORK FOR THE 1

SDA TRACKING LAYER TRANCHE 0 (T0) 2

WIDE FIELD OF VIEW (WFOV) PROGRAM 3

Draft Dated May 11, 2020 4

1.0 INTRODUCTION 5

The National Defense Strategy acknowledges that space is vital to the U.S. way of life, its 6 national security and modern warfare. In an era of renewed great power competition, 7 maintaining U.S. advantage in space is critical to winning these long-term strategic competitions. 8 Potential adversaries seek to undermine this goal by employing strategies that exploit real or 9 perceived vulnerabilities in our current and planned National Security Space systems. In 10 addition, these potential adversaries are developing and demonstrating multi-domain threats to 11 national security much faster than the U.S. can deploy responsive space-based capabilities. The 12 Department of Defense (DoD) established the Space Development Agency (SDA) on 12 March 13 2019 as a response to this problem. 14

SDA is responsible for defining and monitoring the Department's future threat-driven space 16 architecture and accelerating the development and fielding of new military space capabilities 17 necessary to ensure our technological and military advantage in space for national defense. To 18 achieve this mission, SDA will unify and integrate next-generation space capabilities to deliver 19 the National Defense Space Architecture (NDSA), a resilient military sensor and data transport 20 capability via a proliferated space architecture primarily in Low Earth Orbit (LEO). SDA will 21 not necessarily develop and field all capabilities of the NDSA but rather orchestrate those efforts 22 across DoD and fill in gaps in capabilities while providing the integrated architecture. 23

SDA's mission begins and ends with the warfighter. SDA recognizes that sufficient or "good 25 enough" capabilities in the hands of the warfighter sooner is better than delivering the perfect 26 solution too late. SDA will deliver capabilities to joint warfighting forces in 2-year tranches, 27 starting with Tranche 0 in Fiscal Year 2022 (FY22). The layers of the SDA architecture are as 28 follows: 29

• Transport Layer, the backbone of the architecture, to provide assured, resilient, low-30 latency military data and connectivity worldwide to a full range of warfighter 31 applications; 32

• Tracking Layer, to provide global indications, warning, tracking and targeting of 33 advanced missile threats, including hypersonic missile systems; 34

• Battle Management Layer, to provide architecture tasking, mission Command and 35 Control (C2) and data dissemination to support time-sensitive kill chain closure at 36 campaign scales; 37

• Custody Layer, to provide 24x7, all-weather custody of time-sensitive, left-of-launch 38 surface mobile targets (e.g., to support targeting for advanced missiles); 39

• Navigation Layer, to provide Alternate Position, Navigation, and Timing (A-PNT) for 40 GPS-denied environments; 41

• Deterrence Layer, to deter hostile action in deep space (beyond Geosynchronous Earth 42 Orbit and up to lunar distances); 43

• Support Layer, to enable the ground and launch segments to support a responsive space 44 architecture. 45

1.1 TRACKING LAYER WFOV PROGRAM OBJECTIVE AND GOALS 47

The SDA Tracking Layer will provide global indications, warning and tracking of 48 advanced missile threats, including hypersonic missile systems. In T0, two (2) programs 49 will collaborate in the tracking layer: a WFOV program focusing on technologies 50 necessary to populate a proliferated LEO constellation and a Medium Field of View 51 (MFOV) program focusing on technologies necessary for additional performance. The 52 WFOV satellites are planned to be fielded in late FY22 and the MFOV satellites are 53 planned to be fielded in mid-FY23; both sets of satellites will provide complementary 54 mission data to C2 and operational interfaces. T0 is known as the warfighter immersion 55 tranche, a step that builds a path towards warfighter techniques, tactics, procedures and 56 Concepts Of Operations (CONOPS) for future tranches in a proliferated LEO 57 constellation. This Statement of Work (SOW) will focus on the T0 WFOV program and 58 will reference the MFOV program for background or context. Given no unforeseen 59 challenges SDA anticipates at least two awards for the WFOV program. 60

The priorities of the T0 WFOV program are: 61

• Schedule (#1): to demonstrate SDA and industry can launch T0 WFOV satellites 62 by the end of FY22; 63

• Cost (#2): to demonstrate a hypersonic missile warning capability can be 64 achieved at an affordable cost to populate a proliferated LEO architecture; 65

• Performance (#3): to achieve minimally essential, threat-driven, warfighter-66 relevant technical and operational capabilities. 67

The performance goals of the T0 WFOV program are: 68

• Develop and deliver space vehicles integrated with infrared sensors with 69 sufficient sensitivity and processing to detect hypersonic vehicles from low Earth 70 orbit; 71

• Characterize performance of satellite-to-satellite and satellite-to-ground 72 communications paths; 73

• Integrate with a proliferated Transport Layer to provide tracking information 74 directly over tactical data links; 75

• Demonstrate interoperability between satellites provided by different vendors; 76

• Assess how on-board processing, communications infrastructure and advanced 77 algorithms can enable more efficient use of communications bandwidth; 78

• Develop a CONOPS for a global tracking capability; 79

• Verify functional and performance requirements to inform future trade studies on 80 communications; space and ground processing; and, the numbers, types and 81 capabilities of space-based sensors needed for a full global capability. 82

Task statements, for example “shall” statements, can be found in this SOW and are 83 numbered for clarity1. 84

2.0 SCOPE AND DESCRIPTION OF WORK 86

The Contractor shall: 87

1. Design, fabricate, assemble and test up to eight (8) (TBR) satellites, each with an 88 infrared, wide field of view sensor, inter-satellite optical communications package 89 (option for other bands), and ground communications package; 90

2. Support the mating of the satellites to the launch vehicle via a launch dispenser of the 91 satellite Contractor’s design or purchase. The dispenser shall be stackable (e.g., the 92 Evolved Expendable Launch Vehicle Secondary Payload Adapter family of adaptors) to 93 facilitate launch of satellites from multiple SDA layers simultaneously; 94

3. Design, assemble and test a C2 system primarily consisting of subsystems for high-rate 95 communications and Mission Data Processing (MDP). The Government shall provide 96 portions of the C2 system, for example the Ground Entry Points, communications 97 network, Telemetry, Tracking and Commanding (TT&C), operations facility and other 98 functions2; 99

4. Support development of open standards at the physical, data and network layers of the 100 Open Systems Interconnection (OSI) model in concert with SDA and the other Associate 101 Contractors. Additionally, determine required modifications or extensions to capabilities 102 for interoperability with networks using dissimilar service and network management 103 approaches; 104

1 The comprehensive nature of this SOW is intended to convey the scope of SDA’s interest in the T0 WFOV program. In the fixed price spirit of this solicitation, SDA will rely upon Contractors’ best practices to fulfill the tasks set forth in this SOW. This footnote will be removed for the final solicitation.

2 Due to the extent of Government furnished equipment on this solicitation this SOW does not use the overarching term ground system and instead specifies its subsystems like the Ground Entry Points, the communications network, TT&C and MDP software, operations center facility and information technology infrastructure like servers, routers, firewalls, etc. This footnote will be removed for the final solicitation.

5. Design and assemble a satellite test bed for testing of the space and ground segment 105 software; 106

6. Provide a Battle Management Command, Control, & Communications (BMC3) module 107 on the satellites that demonstrates fundamental capability and supports experimentation 108 in preparation for future tranches; 109

7. Provide engineering model intersatellite link and router hardware to support 110 interoperability verification. The hardware provided should be sufficient to verify 111 performance at the physical, data, and network layers of the standard OSI model; 112

8. Deliver satellites to the launch facility not later than thirty (30) days before launch and 113 assist with satellite dispenser and launch vehicle integration as necessary; 114

9. Perform early orbit satellite checkout, calibration, characterization and operations; 115

10. Participate in Government flight tests as required; 116

11. Provide a program management and systems engineering framework that monitors the 117 development of the space and ground segments and addresses challenges as they arise; 118

12. Provide sustainment engineering for the on-orbit life of the satellites; 119

13. Decommission the satellites when instructed by the Government. 120

2.1 PROGRAM MANAGEMENT 122

The Contractor shall: 123

14. Conduct a kickoff meeting no later than 30 days after contract award; 124

15. Establish and conduct regular program management reviews and technical 125 interchange meetings as needed; 126

16. Develop, deliver, monitor, and maintain an event-driven Integrated Master 127

Schedule and report progress against it; 128

17. Implement and maintain a risk management system to mitigate schedule, cost, and 129 technical risks. This system shall describe risks, assess relative likelihood and 130 consequence of occurrence, and develop a plan for burning down these risks; 131

18. Monitor the expenditure of funds in relation to anticipated schedule progress; 132

19. Maintain cost, schedule and performance baselines and inform the Government 133 when controls indicate trade studies need to be initiated to maintain T0 WFOV 134 priorities; 135

20. Monitor contract, subcontract, purchase order, etc. activity. Monitor the potential 136 need for contract modifications and implement modifications as necessary; 137

21. Monitor the supply chain for materials, parts and subsystem availability and 138 production capacity; 139

22. Implement an environmental, safety and occupational health program and report 140 mishaps within 48 hours; 141

23. Include small business participation in contracts to the extent prescribed by this 142 contract; 143

24. Close out this contract in accordance with Government direction as appropriate. 144

2.2 SYSTEMS ENGINEERING 146

The Contractor shall: 147

25. Develop a Systems Requirement Document that implements functional and 148 performance requirements found in the TRD in the design of the system; 149

26. Conduct the following life cycle reviews: 150 o Systems Requirements Review 151 o Preliminary Design Review 152 o Critical Design Review 153 o Pre-Environmental Review 154 o Pre-Ship Review 155 o Flight Readiness Review 156

If the Contractor determines that an alternate review structure (e.g., combining 157 certain reviews) meets the needs of the Government for insight into the design 158 and understanding of challenges and risks at appropriate stages of the 159 development, the Contractor is encouraged to propose it. 160

27. Conduct incremental software reviews for the space and ground software; 161

28. Conduct progress reviews for the mission operations team; 162

29. Support design reviews for common elements of the SDA architecture that are 163

Government-furnished, e.g., the hardware in the loop lab; 164

30. Be compatible with the Naval Research Laboratory’s Neptune constellation 165 operations software; 166

31. Use an open systems architecture to facilitate forward compatibility with future 167 tracking satellite tranches; 168

32. Develop a Requirements Verification Matrix which shows how each requirement 169 in the Systems Requirement Document will be verified; 170

33. Develop test plans for each verification test to be performed; 171

34. Develop interface control documents to adjacent programs or capabilities, e.g., 172 other satellite vendors (intersatellite links and networking), the SDA satellite 173 operations center, the SDA T0 transport satellites and other DoD programs and 174 capabilities as specified by the Government; 175

35. Monitor the supply chain for materials, parts, subsystems and software; and report 176 on issues as they arise. The Contractor shall maintain awareness of hardware and 177 software vulnerability alerts and take action as appropriate. 178

36. Maintain awareness of other SDA-funded tracking experiments for applicability 179 and/or utility to the T0 WFOV design; 180

37. Store and transport equipment in a way that satisfies the security, cleanliness, 181 fragility, environmental, static discharge, safety, etc. needs of the equipment to be 182 stored and transported; 183

38. As required, provide advice, subject matter expertise and/or support on space-184 based topics involving surveillance, tracking, threat assessment, etc.; 185

39. Perform special studies upon request3. 186

2.3 ASSEMBLY, INTEGRATION AND TEST 188

The Contractor shall: 189

40. Maintain a database of observed problems, deficiencies, failures, etc. and track 190 them to resolution or closure; 191

41. Identify test opportunities, as required, for functional and performance 192 requirements, workmanship checks, deficiency resolution, etc.; 193

42. Develop and fabricate special test equipment as needed to integrate and test the 194 spacecraft; 195

43. Implement a test strategy that balances cost effective test execution with required 196 mission assurance as it pertains to numbers of samples tested for a given test; 197

44. Conduct Test Readiness Reviews for significant test events. 198

2.4 LAUNCH SUPPORT 200

The Contractor shall: 201

45. Comply with the Government-provided launch vehicle – space vehicle interface 202 control document; 203

46. Ship the space vehicles and launch dispenser to the launch site and integrate them 204 to the launch vehicle; 205

47. Perform required pre-launch tests and countdown rehearsals; 206

48. Support launch of T0 WFOV satellites; 207

49. Maneuver T0 WFOV satellites into their prescribed orbit. 208

2.5 ON-ORBIT CHECKOUT, CALIBRATION AND CHARACTERIZATION 210

The Contractor shall: 211

50. Perform initial turn on and on-orbit checkout of the T0 WFOV satellites; 212

51. Provide calibration and data analysis services; 213

3 This task will be a separate Contract Line Item Number. There is no need for Contactors to bid this effort at the current time. This footnote will be removed for the final solicitation.

52. Conduct on-orbit tests to characterize the performance envelop of the satellite 214 subsystems, and trend performance over the on-orbit lifetime. 215

2.6 FLIGHT TEST PARTICIPATION 217

The Contactor shall: 218

53. Maintain awareness of other SDA-funded tracking experiments for applicability 219 and/or utility to test planning; 220

54. Participate in the Government test planning and design process; participate in test 221 readiness reviews; 222

55. Use T0 WFOV satellites to participate in cooperative flight tests, targets of 223 opportunity and non-cooperative flight tests. 224

2.7 OPERATIONS, SUSTAINING ENGINEERING AND LOGISTICS 226

The Contractor shall: 227

56. Conduct bus and payload operations from a Government-operated location until 228 such time as those operations potentially transition to the Government. If 229 operations are transitioned to the Government, support operations as requested by 230 the Government; 231

57. As required, support expansion of mission operations including training new 232 operators, technicians, administrators and support personnel; 233

58. Implement changes to flight and ground software as required; 234

59. Provide logistics support for delivered hardware and software items; 235

60. Conduct or support on-orbit failure or anomaly diagnosis, analysis and 236 remediation as necessary. 237

2.8 DISPOSAL 239

The Contractor shall: 240

61. Dispose of, deorbit, or decommission the satellites as and when instructed by the 241 Government in a fashion consistent with "U.S. Government Orbital Debris 242 Mitigation Standard Practices, November 2019 Update” and other relevant U.S. 243 policies. 244

3.0 GOVERNMENT FURNISHED EQUIPMENT 246

The Government shall provide selected equipment and/or information required for the 247 performance of the T0 WFOV program. This equipment can be found in the Government 248

Furnished Equipment (GFE) List, an attachment to this SOW. As equipment items are removed 249 and/or added, the listed will be updated. 250

The Contractor shall: 251

62. Maintain custody of GFE at all times and notify and coordinate with the Government for 252 the repair and test of GFE; 253

63. Report and update the Item Unique Identification Registry for parts provided as GFE per 254 Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7007. 255

If the Contractor determines that an item not on the GFE List would benefit contract 256 performance if it were made available to the Contractor, the Contractor is encouraged to propose 257 it be added to the list. 258

4.0 BMC3 MODULE 260

The BMC3 Layer is responsible for several functions key to the eventual SDA constellation’s 261 success, including but not limited to management, coordination, and allocation of resources. 262 BMC3 modules are envisioned to reside on Transport, Tracking, and mission partner nodes to 263 provide not only constellation management, mission management and C2 functions, but also as 264 an open hardware and software platform for mission data processing and exploitation needs. 265

For T0, BMC3 envisions a CONOPS that demonstrates fundamental connectivity and 266 rudimentary BMC3 functionality. For later tranches, BMC3 is expected to add benefits for 267 onboard processing, networking and autonomy. 268

No core spacecraft functionality shall reside on the BMC3 module and the spacecraft shall 269 operate with the BMC3 module disabled or turned off; however all TT&C, positioning, timing, 270 satellite crosslink and other payload data shall be made available to the BMC3 module. 271

The Contractor shall provide BMC3 hardware module that maximizes onboard processing 272 performance while conforming to the following requirements: 273

64. Size: less than 30 x 15 x 15 cm; 274

65. Weight: less than 10 kg; 275

66. Power: less than 15 W (survival power) and less than 250 W (peak with max 276 processing); 277

67. Design life: 2 years (threshold), 4 years (objective). 278

The Contractor shall: 279

68. Provide a BMC3 Software Development Kit that describes the open, modular software 280 architecture to allow third parties to develop space vehicle applications for the BMC3 281 module without support from the T0 WFOV Contractor. 282

5.0 DELIVERABLES 284

5.1 REPORTS AND DATA ITEMS 286

The T0 WFOV program shall require a variety of reports and data items. These items 287 can be found in the list of DD Forms 1423, Contract Data Requirements List, a list of 288 data items attached to this SOW. Each DD Form 1423 shall list a SOW reference 289 paragraph in block 5 to connect each data item to the SOW. As data items are removed 290 and/or added, the listed will be updated. 291

If the Contractor determines that a report or data item, its preparations instructions or 292 Government review requirements can be met in a more economical form, the Contractor 293 is encouraged to propose it. 294

5.2 HARDWARE AND SOFTWARE 296

The T0 WFOV program shall require several hardware and software items. These items 297 can be found in the Deliverables List, an attachment to this SOW. As hardware and/or 298 software items are removed and/or added, the listed will be updated. 299

The Contractor shall: 300

69. Mark the components, parts, and end items with Item Unique Identification 301 (IUID) as required by DFARS 252.211- 7003; 302

70. Ensure the IUID markings are machine-readable; 303

71. Develop the IUID marking/tags and enter the IUID and required data elements 304 into the IUID Registry. 305

6.0 CRYPTOGRAPHIC EQUIPMENT 307

The Contractor shall: 308

72. Encrypt satellite-to-satellite and satellite-to-ground communications links; 309

73. Use equipment that is certified for use by the National Security Agency; 310

74. Develop and use a key management plan appropriate for the classification level of the 311 keys; 312

75. Provide unclassified test keys. 313

7.0 SPECTRUM MANAGEMENT 315

The Contractor shall: 316

76. Deliver a frequency use plan that is compliant with all applicable National 317 Telecommunications and Information Administration and International 318 Telecommunications Union (ITU) regulations; 319

77. Deliver Standard Frequency Action Format applications for frequency assignment to 320 enable SDA to obtain frequency assignments for terrestrial and satellite systems; 321

78. Deliver Advanced Publication Information to enable SDA to file and coordinate satellite 322 spectrum use with the ITU and other nations. 323

8.0 SECURITY OPERATIONS 325

The Contractor shall: 326

79. Protect facility resources and maintain control of personnel access to restricted access 327 locations; 328

80. Maintain the resources to receive, access, process and store classified items in accordance 329 with approved policies; 330

81. Maintain accredited facilities and approved Automated Information Systems (AIS) 331 necessary to perform work at the correct classification; 332

82. Assign personnel with the appropriate clearance or eligibility necessary to perform work 333 at the correct classification; 334

83. Allocate security provisions to Subcontractors in a manner that sufficiently protects T0 335 WFOV program information; 336

84. Implement operations security and program protection measures throughout all life cycle 337 phases and activities of the T0 WFOV program; 338

85. Implement disaster recovery measures as necessary. 339

Additional information can be found in the DD Form 254, Contract Security Classification 340 Specification, an attachment to this SOW. 341

9.0 CYBERSECURITY 343

The Contractor shall: 344

86. Allocate functional and performance requirements from the system level to the subsystem 345 and component level in a manner that ensures cybersecurity is an inherent attribute of the 346 design; 347

87. Design T0 WFOV interfaces with other programs such that there is alignment between 348 adjacent programs’ cybersecurity pedigrees and risk postures; 349

88. Maintain awareness of cybersecurity vulnerabilities in commercial or government 350 software and perform software assurance on software it develops in house; 351

89. Allocate cybersecurity provisions, including reporting requirements, to Subcontractors in 352 a manner that sufficiently protects T0 WFOV program information; 353

90. Implement software assurance practices and processes consistent with DoD and SDA 354 instructions, directives manuals and provisions; 355

91. Meet cybersecurity related duties on classified Information Systems as outlined in DoDM 356 5200.01, Volume 3. 357

10.0 SOFTWARE PROTECTION 359

The Contractor shall: 360

92. Ensure that all media delivered to or for the Government under this contract in the form 361 of AIS media (e.g., compact disks, etc.) shall be free of viruses, Trojan horses and worms 362 which could cause damage, disruption or degradation of the AIS; 363

93. Test such media to ensure there are no infections prior to delivery; 364

94. Include this requirement in all subcontracts at any tier when the data is to be delivered in 365 the form of AIS media. 366

11.0 SMALL BUSINESS UTILIZATION 368

The Contractor shall: 369

95. Submit a Small Business Participation Commitment Document to develop capabilities for 370 small businesses and provide maximum practicable opportunity for small businesses to 371 participate in efficient contract performance. 372

Instructions for this document can be found in the small business attachment to this SOW. 373

12.0 ASSOCIATE CONTRACTOR AGREEMENT 375

The T0 WFOV program requires its Contactor to be an associate contractor with other Tranche 0 376 Contractors, Subcontractors and Suppliers. The T0 WFOV Contractor shall: 377

96. Maintain a close working relationship and open information network with other 378 Associated Contactors; 379

97. Enter into a written agreement with the other Associate Contractors establishing the 380 substance and procedures of the relationship; 381

98. Protect proprietary information received from other Associate Contractors. 382

Additional information can be found in a corresponding clause for this contract. 383

13.0 LOCATION OF WORK 385

13.1 PRIMARY LOCATION OF WORK 387

The primary location of work for this contract is at facilities operated by the Contractor, 388 Subcontractor, Suppliers, etc. During the satellite operations phase working from a 389 Government facility is expected. 390

13.2 ALTERNATE LOCATIONS OF WORK 392

Additional locations for work include, but are not limited to, locations associated with 393 duties at: 394

• Headquarters Space Development Agency in Washington, D.C. 395

• Missile Defense Agency locations in Washington, D.C., Schriever AFB, CO, 396

Redstone Arsenal, AL 397

• Space and Missile Systems Center, Los Angeles AFB, CA 398

• Naval Research Laboratory locations in Washington, D.C., Blossom Point, MD 399

• U.S. Space Force, Peterson AFB, CO 400

• Combatant Command Headquarters 401

• DoD, DOE and FFRDC and UARC Laboratories 402

• DoD Field Activities, Command and Intelligence Centers 403

• Missile defense related technical symposia and conferences 404

14.0 TRAVEL 406

Travel shall be required for this contract. The Contractor, Subcontractor and Suppliers are 407 permitted to travel to fulfill the requirements set forth in this contract. Travel to, but not limited 408 to, sites listed in the Alternate Locations of Work paragraph, require advance approval from the 409 Government. Government approval of travel shall consider if the objectives of the request can 410 be achieved in a more cost effective manner, e.g., teleconferencing or web-based platforms. 411

15.0 SPECIAL NEEDS 413

In fulfillment of activities found in the Operations, Sustaining Engineering and Logistics 415 paragraph, the Contractor will require access to the Non-classified Internet Protocol (IP) Router 416 Network (NIPRNET), Secret Internet Protocol Router Network (SIPRNET), and potentially 417 other communications networks. 418

The Contractor shall: 419

99. Provide personnel who will fulfill the security and training requirements necessary for 420 access to NIPRNET, SIPRNET, etc. 421

16.0 PERIOD OF PERFORMANCE AND OPTIONS 423

The approximate period of performance for this contract is as follows: 424

• Base contract (development, launch, checkout, operations and test for two years): 425 o August 2020 to July 2025 426

• Option period 1 (operations, test, sustaining engineering and logistics for two years): 427 o August 2025 to July 2027 428

• Option period 2 (operations, test, sustaining engineering and logistics for two years): 429 o August 2027 to July 2029 430

The Contractor shall: 431

100. Enact special study contract options upon request. 432

17.0 APPLICABLE PUBLICATIONS, FORMS AND REFERENCES 434

All required DoD directives, policies and procedures will be made available for Contractor 435 access upon award. Additional information can be made available as requested. 436

ACRONYM LIST 438

AFB Air Force Base 439 AIS Automated Information System 440 A-PNT Alternate Position, Navigation and Timing 441 BMC3 Battle Management Command, Control, & Communications 442 C2 Command and Control 443 CONOPS Concept of Operations 444 DD Department of Defense 445 DFARS Defense Federal Acquisition Regulation Supplement 446 DoD Department of Defense 447 DOE Department of Energy 448 FFRDC Federally Funded Research and Development Center 449 FY Fiscal Year 450 GFE Government Furnished Equipment 451 GPS Global Positioning System 452 ITU International Telecommunications Union 453 IUID Item Unique Identification 454 LEO Low Earth Orbit 455 MDP Mission Data Processing 456 MFOV Medium Field Of View 457 NDSA National Defense Space Architecture 458 NIPRNET Non-classified Internet Protocol Router Network 459 OSI Open Systems Interconnection 460 SDA Space Development Agency 461 SIPRNET Secret Internet Protocol Router Network 462 SOW Statement of Work 463 T0 Tranche 0 464 TRD Technical Requirements Document 465 TT&C Telemetry, Tracking and Commanding 466 UARC University Affiliated Research Center 467 WFOV Wide Field Of View 468