24Jan20_Conformed_02_Performance-Based_Work_Statement.pdf

ATTACHMENT 1 4

SPACE AND MISSILE SYSTEMS CENTER/ LAUNCH 6

ENTERPRISE (SMC/ECL) 7

SYSTEMS ENGINEERING & INTEGRATION-2 (SE&I-2) 8

PERFORMANCE WORK STATEMENT (PWS) 9

FA8811-20-R-0003 12

24 January 2020 15

Department of the Air Force 18

Space and Missile Systems Center 19

Launch Enterprise 20

Los Angeles AFB, California 90245-2808 21

1. INTRODUCTION ................................................................................................................... 4 23

1.1. Scope ...................................................................................................................................... 4 24

1.2. Description of Service .............................................................................................................. 5 25

2. APPLICABLE DOCUMENTS .................................................................................................... 6 26

2.1. Compliance Documents ........................................................................................................... 6 27

2.2. Reference Documents ............................................................................................................. 6 28

3. REQUIREMENTS ................................................................................................................... 7 29

3.1. General Requirements ............................................................................................................ 7 30

3.2. Transition of SE&I-2 Effort ..................................................................................................... 10 31

3.3. Los Angeles Air Force Base (LAAFB) Requirements ................................................................. 12 32

3.4. Cape Canaveral Air Force Station (CCAFS) Requirements ....................................................... 39 33

3.5. Vandenberg Air Force Base (VAFB) Requirements ................................................................. 49 34

3.6. Research, Development, Test, and Evaluation (RDT&E) ......................................................... 68 35

3.7. CCAFS, KSC, VAFB Support ..................................................................................................... 68 36

4. SERVICES SUMMARY ......................................................................................................... 70 37

4.1. General: ................................................................................................................................ 70 38

4.2. Performance Evaluation: ....................................................................................................... 70 39

4.3. Base support ......................................................................................................................... 72 40

4.4. USG-FURNISHED PROPERTY: ................................................................................................. 74 41

4.5. GENERAL INFORMATION ....................................................................................................... 74 42

4.6. GENERAL SECURITY ............................................................................................................... 75 43

4.7. BACKGROUND INVESTIGATIONS ........................................................................................... 75 44

4.8. VISIT AUTHORIZATION LETTER (VAL)/VISIT AUTHORIZATION REQUEST(VAR) ........................ 76 45

4.9. SECURITY MANAGEMENT ...................................................................................................... 76 46

4.10. Employee Training:................................................................................................................ 76 47

4.11. Employee Certifications:........................................................................................................ 76 48

4.12. Dress and Appearance: .......................................................................................................... 77 49

4.13. Employment of USG Employees: ........................................................................................... 77 50

4.14. INSTALLATION AND CONTROLLED AREA ACCESS ................................................................... 77 51

4.15. HOURS OF OPERATION .......................................................................................................... 78 52

4.16. INSPECTION OF FILES: ............................................................................................................ 79 53

4.17. PERFORMANCE EVALUATION MEETINGS: .............................................................................. 79 54

4.18. Contractor Manpower Reporting ........................................................................................... 79 55

4.19. QUALITY ASSURANCE ............................................................................................................ 80 56

4.20. SAFETY: ................................................................................................................................. 81 57

APPENDIX A - ACRONYMS, ABBREVIATIONS AND DEFINITIONS ................................................. 83 58

APPENDIX B - GLOSSARY ........................................................................................................... 90 59

APPENDIX C - COMPLIANCE DOCUMENTS ............................................................................... 107 60

APPENDIX D - REFERENCE DOCUMENTS .................................................................................. 112 61

APPENDIX E – LABOR CATEGORY REQUIREMENTS ................................................................... 121 62

Annex A – Enabling Requirements ........................................................................................... 182 63

Annex B - Associate Contractor Agreement Requirements ...................................................... 185 64

1. INTRODUCTION 67

1.1. Scope 68

The objective of Systems Engineering and Integration-2 (SE&I-2) contract is to provide Launch 69 Enterprise with Systems Engineering, Integration, Launch Systems support engineering, Mission 70 Integration, security systems and other SE&I functions to support National Security Space Launch 71 (NSSL), Launch Service Providers (LSPs) integration, certification support and fleet surveillance 72 support. 73

The SE&I-2 Contractor (referred to as the Contractor for the remainder of this document) shall 74 furnish all personnel, equipment, labor, tools, materials, supervision, transportation and other 75 items and services necessary to perform SE&I-2 services for the Launch Enterprise (referred to 76 as either SMC/ECL or Launch Enterprise (LE) for the remainder of this document) located at the 77 Space and Missile Systems Center at Los Angeles Air Force Base, California (LAAFB); Cape 78 Canaveral Air Force Station, Florida (CCAFS); Vandenberg Air Force Base, California (VAFB), 79 and other locations as required. The Contractor shall support SMC/ECL in its current configuration 80 and shall continue to support SMC/ECL as it evolves through the life of this contract. 81

Services provided under this contract support SMC/ECL’s space launch operations for current 82 and future SMC/ECL launch systems. Deliverables provided under this contract are in accordance 83 with (IAW) Exhibit A. The services include the following functional areas: 84

a) Systems Engineering and Integration (SE&I) 85

b) Mission Integration Management 86

c) Systems Safety Engineering 87

d) Systems Environmental Engineering 88

e) Systems Security & Cybersecurity 89

f) Quality and Production 90

g) Manufacturing Engineering 91

h) Quality Engineering 92

i) Launch Schedule Management 93

j) Launch Risk Management 94

k) Delta Launch Systems Certification for configuration changes (for the following 95 potential systems: SpaceX - Falcon Family, United Launch Alliance – Atlas, Delta and 96 Vulcan Next Generation Launcher, Blue Origin - New Glenn, Northrup Grumman - 97 OmegA, Other Potential New Entrant(s), and Additional Launch Service Agreement 98 (LSA) Vehicle Efforts Certification. 99

l) Data Management and Configuration Control Management 100

m) Enterprise Management 101

Effective March 2019, Evolved Expendable Launch Vehicle (EELV) is referred to as NSSL. SMC 102 is evolving continuously and can be expected to evolve during the period of performance. This 103 contract shall cover SMC/ECL launch services operations requirements in its current and future 104 names, missions, and configurations based on organizational evolution to meet National Security 105 Space (NSS) needs. Additionally, it can be reasonably expected that the roles and responsibilities 106 (i.e., leading an effort versus supporting an effort) in certain areas of this PWS might evolve during 107 the period of performance. The Contractor shall support all the requirements in this PWS and any 108 additional tasks based on evolving requirements. 109

1.2. Description of Service 110

This PWS consists primarily of systems engineering and integration (SE&I) tasks in support of 111 SMC/ECL, but will also encompass support to the collective NSSL Government personnel and 112 team members, to include Federally Funded Research Development Centers. The SE&I-2 113 contract also includes overarching integration requirements for launch and range programs which 114 will require interfacing both the NSSL and any future SMC/ECL launch systems. In addition, this 115 contract effort provides for SE&I support to the 45th Space Wing (45 SW) and the 30th Space 116 Wing (30 SW) launch responsibilities at Cape Canaveral Air Force Station (CCAFS), Vandenberg 117 Air Force Base (VAFB) and other locations as required. 118

For NSSL, the SE&I-2 Contractor will provide support of SMC/ECL and Operations Group (OG) 119 mission assurance efforts for an average of 12 National Security Space (NSS) missions per year; 120 approximately 3 from VAFB and approximately 9 from CCAFS/Kennedy Space Center (KSC) 121 and other locations as required. Additionally, the SE&I-2 Contractor will provide support of fleet 122 surveillance for non-NSS mission activity for no more than 40 missions per year, in order to assess 123 the cross-over impact to NSS mission assurance as implemented and directed by SMC/ECL at the 124 time of performance. Fleet surveillance includes performing surveillance of commercial and civil 125 launch activities for the purpose of maintaining awareness of issues that intersect or may intersect 126 NSSL flight worthiness or other Government mission assurance requirements for NSSL and LSPs. 127

The contract effort will be performed at LAAFB, VAFB, CCAFS and other locations as required. 128 The contract efforts needed to support SMC/ECL launch services will be funded by the SMC/ECL 129 at LAAFB (Section 3.2, 3.3.1, 3.4.1, and 3.6), CCAFS (Section 3.3.2 and 3.7), VAFB (Section 130

3.4.2 and 3.7). 131

2. APPLICABLE DOCUMENTS 134

2.1. Compliance Documents 135

The Contractor shall comply with the applicable documents listed in Appendix D. 136

2.2. Reference Documents 137

The reference documents applicable to this PWS are listed in Appendix C. 138

3. REQUIREMENTS 141

3.1. General Requirements 142

Tools, Processes & Procedures 143 The Contractor shall only use software tools and standard COTS software (e.g. MS Office 144 applications, Microsoft Project, etc.) that are compatible with the tools and software that 145 Government is using at the time of performance on this PWS, or the Contractor shall use 146 software tools and software that are non-COTS/proprietary but are capable of saving 147 deliverables in a format that is compatible with the software and tools that the Government uses 148 at the time of performance, unless an exception is granted. 149

The Contractor is encouraged to develop tools and processes that will result in efficiencies and 150 process improvement for SMC/ECL. The Contractor shall notify the PCO of potential software 151 and/or tools (including proprietary software or tools) that may be used for process improvement 152 purposes. 153

The Contractor shall exclusively use Government funds for the development of any non-154 commercial tools and processes. Any other software and/or tools that are not COTS and involve 155 any level of proprietary software/tool functionality may be used only upon explicit written 156 authorization by the Contracting Officer’s Representative (COR) and PCO stating the impacts 157 to data rights. 158

The contractor shall also use and/or integrate data from other government tools used by the 159 government at the time of performance (e.g. LCMP, PMRT, CCaR etc.) 160

Staffing 161

The Contractor shall fill the positions and meet all the qualifications, experience, and 162 certifications (or equivalency) pursuant to Contract Attachment 8, Staffing Plan and Appendix 163 E, Labor Category Requirements. The Government’s decision regarding equivalency of 164 qualifications, experience, or certification will be final. 165 The government defines key personnel as subject matter expert positions in a managerial 167 capacity essential to the work performed under this contract and contribute in a substantive and 168 measurable way. Key personnel may also be empowered to make discretionary decisions in 169 accordance with the company policies with respect to team building, team management, and 170 work performance by the teams they are in charge of. For positions described as key personnel 171 in government staffing estimate, the government estimates that the minimum qualifications, 172 number of positions, experience, and certifications are essential for successful performance on 173 this PWS requirement. 174

The government defines minimum staffing as positions that have to be staffed exactly with the 176 numbers as described in the government staffing estimate in order to perform on this PWS 177 successfully. For the positions described as minimum staffing, the government estimates that 178 the number of positions should be staffed at the minimum as described in the government 179 staffing estimate. 180

Document Review 181

The Contractor shall develop, submit, and review program documents consistent with Appendix 182 C, Reference Documents and applicable military, federal, state, local, contractual, commercial, or 183 international statutes, regulations, policies, publications, directives, instructions, executive orders, 184 codes, requirements or standards and report findings to the Government. 185

Contractor Recommendations 186

When presenting recommendations to the Government in the performance of this PWS, the 187 Contractor shall provide a detailed analysis of the Courses of Actions, Risks, Opportunities, and 188 impacts to maximize the Government’s ability to make informed decisions consistent with the 189 Government’s responsibility to perform Governmental functions in the public interest. The 190 Contractor, when required by the Government, shall provide comments using the approved 191 Comment Resolution Matrix (CRM) format, or other Government directed format, and provide 192 the completed CRM to the Government representative for review, approval, and action on or 193 before mutually agreed schedule. 194

Meetings 195

The Contractor shall host, and participate in meetings, such as Integrated Product Team (IPT) 196 meetings, Technical Interchange Meetings (TIMs), working group meetings, process 197 improvement meetings, etc., with Government and USG Team organizations as directed by the 198 Contracting Officer’s Representative (COR). The Contractor will also be required to attend and 199 provide support for time sensitive and classified actions meetings in-person. Repeated inability 200 to attend will reflect negatively on the Contractor’s performance evaluation, and be graded against 201 the services summary. 202

The Contractor shall prepare presentation materials, special technical reports, and papers as 203 requested, and provide the Government with copies of all materials presented at the meetings. 204 This information shall be delivered to the Government as Technical Reports, Presentation 205 Materials, or Conference Minutes, or other format as required by the Government (CDRL A001 206 Program Progress Report). 207

Continuous Improvement Recommendations 208

The Contractor shall submit, as appropriate, recommendations for streamlining and improving the 209 standards, plans and processes used to execute the tasks within this PWS. 210

Training Government Personnel 211

The Contractor shall develop and implement, upon Government approval, a training program 212 regarding areas covered by this PWS for the purpose of providing on-the-job and classroom 213 training to Government personnel. 214

Priority of the Tasks 215

The Government may prioritize tasks and requirements, including quantity and schedule 216 requirements, and the Contractor shall accept the Government priority as directed. The Contractor 217 shall promptly report to the Government discrepancies in task sequencing and opportunities to 218 improve product and process efficiencies. 219

Small Business Utilization Report (CDRL A005) 220

The Contractor shall report actual achievements relative to proposed small business utilization in 221 performance of this specific contract (including subcontracting dollars/percentages relative to 222 total contract value/total subcontracting). Reports are due 30 days after the close of each 223 reporting period and within 30 days of contract completion. 224

Government Data Rights 225

The Government shall have unlimited data rights for all documentation delivered or and otherwise 226 provided to the Government during the performance of this Contract. Once submitted, this 227 information is considered Government-owned, and subject to Government dissemination 228 decision. The Contractor shall provide the Government with data rights on all the products and 229 deliverables developed in the course of conducting PWS tasks in accordance with DFARS 230 252.227-13 and 252.227-7014. Examples of products or deliverables that the Government will be 231 granted unlimited data rights to include but are not limited to: advice, analyses, evaluations, 232 information, models, recommendations, reports, services, studies, training, and any product or 233 information that will be developed with Government funding. 234

The Contractor shall use Government compatible systems, software, methods, processes, and 235 facilities authorized by the Government to fulfill the requirements in this PWS, use of any 236 unauthorized means, process, or methods including but not limited to: the use of any proprietary 237 systems; software; methods; processes; and facilities are not permitted unless the Government has 238 authorized such use in writing with a descriptive understanding of impacts to data rights. 239

The Contractor shall exclusively use Government funds for the development of any non-240 commercial tools and processes. 241

The Contractor shall supply all requests from the PCO for data ordered from the Data Accession 242 List (CDRL A007) shall be provided at no increase in contract price. 243

Management Reviews (CDRL A002) 244 The Contractor shall conduct Program Management Reviews (PMRs) on a quarterly basis. The 245 PMR agenda will be coordinated with the Government to ensure the appropriate items are 246 discussed at each meeting. The results of each PMR will be provided to the Government via 247

CDRL A002. 248

Contract Performance Review 249 The Government will review and report the Contractor performance quarterly. The 250 Government will assess product quality and timeliness. The Contractor shall provide and 251 maintain a resource loaded schedule at the start of the contract’s period of performance, and 252 shall have all key personnel available on the first day of the schedule start times. The 253 Government may cancel this contract for cause if the Contractor fails to meet contractual 254 conditions and requirements. 255

Monthly Status Report- (CDRL A001 and A002) 256

The Contractor shall document the efforts performed in the completion of these tasks in a detailed 257 Monthly Status Report (MSR). The Contractor shall develop a report format that is consistent 258 with the operations being performed under the specified tasks. The Contractor shall include any 259 updates and summarize the current financial billing profile, including any projected shortfalls or 260 under-runs. The following information: progress this period, status of tasks, planned delivery date 261 and actual and/or anticipated delivery date, identification of any problems/issues/delays, 262 recommendations, and corrective actions taken. The Contractor shall submit the monthly status 263 report to the COR with a copy to the PCO no later than the 15th calendar day after the end of each 264 month. 265

3.2. Transition of SE&I-2 Effort 266

Kick-Off Meeting 267

The PCO will in writing establish a future date after contract award to start transition of 268 performance on this PWS requirements from incumbent contractor to the new SE&I-2 Contractor 269 (here in after referred to as Authority To Proceed (ATP). The Contractor shall conduct a kick-off 270 meeting at their facility within three business days after ATP. The Contractor shall address the 271 transition plan and progress as part of the kick-off meeting. (CDRL A001 Program Progress 272 Report) 273

Transition-In Plan (CDRL A006 Transition Plan) 274 The Contractor shall develop and implement, a Government-approved, 275 Transition Plan to coordinate with the current SE&I Contractor to ensure a 276 smooth transition between the inbound Contractor and the outbound Contractor. 277 The Contractor shall present how each PWS task will be executed during the 278 kickoff meeting. Details of Transition-In requirements are described below: 279

3.2.3.1.1. Days 1-30 after ATP will be considered as Transition-In period. 280

3.2.3.1.2. Days 31-365 after ATP will be considered as base period for 281 performance on these PWS tasks. 282

3.2.3.2.Transition-in will be managed by a dedicated Contractor Transition Manager 283 who is not a key personnel. The Transition Manager will coordinate with the 284 SMC/ECL COR and incumbent Contractor Transition Team to integrate 285 efforts, channel communications, resolve issues, and track progress. The 286 Transition Manager will schedule and lead a weekly formal coordination 287 meeting between the COR, and incumbent Contractor to brief staffing and 288 transition progress to the Government. 289

3.2.3.3.The scope of work for transition-in is to perform all activities necessary, and 290 staff all positions identified in Contract Attachment 8, Staffing Plan to be 291 prepared to assume full responsibility of the contract requirements by day 31 292 after ATP. 293

3.2.3.4.The Contractor shall staff all positions as identified in the Contract Attachment 294 8, Staffing Plan as follows: All Key personnel (non-incumbent) on day 1 after 295 ATP; all positions identified as minimum staffing (non-incumbent) before day 296 15 after ATP; and, all positions identified in Contractor proposed staffing 297 matrix on or before 30th day of ATP. Minimum staffing is identified in 298 Attachment 8, Staffing Plan, of the contract. 299

Transition-In Implementation 300 During the transition-in period, the Contractor may observe work being accomplished by the 301 incumbent Contractor, which shall be on a non-interference basis. The Contractor shall familiarize 302 personnel as defined in the transition plan with work in-progress, reporting, priorities, forms, 303 documents, scheduling, storage, safety, security, and quality control procedures. The incumbent 304 Contractor’s transition out period will be thirty (30) calendar days. 305

Contract Transition-Out (CDRL A006 Transition Plan) 306 3.2.5.1.The Contractor shall support and appropriately staff all transition-out 307 activities. The Contractor shall contribute to organizational, system, process 308 and information knowledge transfer to the Government program office team 309 (Government, FFRDC, and SETA members) and inbound Contractor. 310

3.2.5.2. The Contractor shall implement transition-out activities to minimize impact to 311 SMC/ECL program schedules, cost, performance, and risk. 312

Transition Program Technical Baselines 313 The Contractor shall transition the SMC/ECL program Configuration Control Board (CCB)-314 controlled technical baseline to the inbound SMC/ECL SE&I Contractor. The Contractor shall 315 verify and validate that the traceability from the functional baseline to the allocated baseline is 316 correct for all CCB-controlled requirements. 317

3.3. Los Angeles Air Force Base (LAAFB) Requirements 318

Systems Engineering 319

3.3.1.1. Launch Systems 320

The Contractor shall perform assessments of SMC/ECL launch systems engineering program 321 documents as required for adequacy, currency, and compliance with the Office of the Secretary 322 of Defense (OSD), Air Force (AF), Air Force Space Command (AFSPC), and SMC instructions. 323 The Contractor shall assess and SMC/ECL internal compliance with the approved SMC/ECL 324 systems engineering documents on an annual basis, or as otherwise required by SMC/ECL. For 325 the SMC/ECL systems engineering documents, the Contractor shall produce and assess needed 326 changes, and gather inputs from stakeholders, maintain comment resolution matrices (CRMs), or 327 other comment database tracking system approved by the Government in order to incorporate 328 agreed to changes, and deliver draft updated documents to SMC/ECL on a mutually agreed to 329 schedule, and support staffing and Technical Review Board (TRB)/ Configuration Control Board 330 (CCB) approval. 331

The Contractor shall perform the following: 332

a) Perform Mission Assurance tasks supporting the NSSL launches and fleet surveillance for 333 Launch Enterprise 334

b) Support New Entrant Certification validation traceability to the SPRD/SIS, as needed. 335

c) Support future launch systems architecture non-recurring engineering requirements as a 336 part of the larger Launch Enterprise mission assurance efforts; which includes architecture 337 verifications and design validations. 338

d) Provide support to AFSPC Capabilities Production Document (CPD) updates, CONOPS 339 and Operating Concepts. 340

e) Support SMC/ECL taskers, including review and CRM responses. The Contractor should 341 expect an average of 2 taskers per week with the understanding that there may be more 342 depending on tasker fluctuations. 343

f) Attend, document, and track assigned action items in support of the following but not 344 limited to the following: SMC/ECL Chief Engineer’s Control Board (ChECB), Mission 345

Assurance Council (MAC), Launch Vehicle Mission Assurance Forum (MAF),Technical 346 Review Board (TRB), and Configuration Control Board (CCB). 347

g) Coordinate meeting logistics for the National Aeronautics and Space Administration 348 (NASA), National Reconnaissance Office (NRO), and SMC/ECL leadership collaboration 349 at Launch Collaboration Steering Groups. 350

The Contractor shall maintain the documents, but not limited to the following: 351

a) System Performance Requirements Document (SPRD) 352

b) Standard Interface Specification (SIS) 353

c) Systems Engineering Plan (SEP) 354

d) Risk Management Plan (RMP) 355

e) Mission Assurance Plan (MAP) 356

f) SMC/ECL Process Guide 357

g) Life Cycle Sustainment Plan (LCSP) (CDRL A004) 358

h) The Contractor shall develop and maintain any other required launch systems engineering 359 documents identified by the Government. These can be also any document located in the 360 Configuration Management/ Data Management Portal in Livelink. 361

3.3.1.2. Configuration Management 362

The Contractor shall provide Configuration Management, Data Management (CM/DM), and 363 CDRL Management for the SMC/ECL NSSL documentation as described below: 364

a) NSSL Configuration Management: The Contractor shall execute the NSSL Configuration 365 Management Plan (CMP) IAW SMCI 62-109 to ensure all CM required functions and 366 activities are executed and documented, including managing technical review boards, 367 configuration control boards, Chief Engineer control boards, configuration identification, 368 change control, status accounting, verification, reviews, audits, and metrics for the 369 program baseline documentation. The Contractor shall review and update the NSSL 370 Change Control Board (NCCB) Operating Instruction (OI) annually to document Change 371 Control processes that are enforceable and subject to inspection. 372

b) LSP Contract Data Requirements List (CDRL) Management: The Contractor shall manage 373 the LSP CDRL process from submittal through acceptance to archival. The CDRL 374 management process shall include but is not limited to: acquiring and maintaining all 375 CDRLs submitted by LSPs, notification and distribution of the documents for review, 376 maintaining the current status of each CDRL, collecting metrics, maintaining comments 377 submitted against CDRLs, coordinating reviews, and facilitating the CDRL Review Board 378 and Actions Items. 379

c) Data Management Development: The Contractor shall review and update annually the 380 Data Governance Policy that defines the rules, standards and models that govern and 381 define the type of data that exists in the SMC/ECL (Enterprise Data) and how it is used, 382 stored, managed and integrated within the organization and its systems. 383

d) Data Management Plan: The Contractor shall review and update annually the SMC/ECL 384 Data Management Plan (DMP) to incorporate the tenets of the Data Governance policies 385 and processes into a single source document for Enterprise Data management. 386

e) Configuration Management Plan: The Contractor shall review and update annually the 387 SMC/ECL Configuration Management Plan (CMP) to incorporate the tenets of the Data 388 Governance policies and processes. 389

f) Data Management Implementation: The Contractor shall implement the new DMP’s 390 structures and processes in accordance with the Data Governance Policy (DGP) across 391 the Launch Enterprise and its systems, as tailored by the United States Government 392

(USG). 393

g) Data Repository: The Contractor shall operate and maintain the repositories of enterprise 394 critical data and protected data on the SMC Livelink system or other Government owned 395 and administered system. 396

3.3.1.3.Digital Engineering Capability Development, Implementation, and 397 Maintenance 398

The offeror contractor shall describe develop, implement, and maintain a Digital Engineering 399 Environment (DEE) – including common tools, data structures, and collaborative workspaces – 400 to enable a model-based, data-driven approach to vehicle certification, mission integration, and 401 mission thread collaboration IAW the SMC Directors of Engineering (DoE) Council and all 402 applicable standards. to systems engineering.. 403

a) Model-Based Engineering (MBE) – The contractor shall develop and implement a data-404 driven approach to launch engineering and mission assurance that relies on common, 405 shared models from the various launch engineering disciplines. 406

b) Digital Engineering Environment (DEE) – The contractor shall provide the Information 407 Technology (IT) infrastructure (i.e., digital platform or DEE) required to manage 408 integrated, shared sets of engineering data IAW data governance policies and data 409 management practices. 410

c) Model Ontology – The contractor shall formalize the naming and definition of terms, 411 entities, data types, and properties, as well as their interrelationships, to help ensure their 412 consistent use with internal and external stakeholders throughout the system lifecycle. 413

d) Master Schema – Based on the model ontology, the contractor shall define a master 414 schema to ensure that all new and modified elements can be integrated properly into the 415 underlying data repository. 416

e) Digital Engineering Information Exchange (DEIX) – The contractor shall support the 417 development and implementation of standards (e.g., format, protocol, data protection, 418 service level) for exchanging underlying model data across organizational boundaries 419 IAW industry interoperability standards. 420

f) Digital Work Products – The contractor shall develop standard work products (e.g., 421 views, artifacts, workflows), and the capability to create fit-for-purpose products, in 422 response to particular queries of the launch engineering models. These information 423 products are generally derived from source data or partially refined data; examples 424 include graphics, diagrams, textual descriptions, and reports. 425

g) Digital Work Product Exchange (DWPX) – The contractor shall support the 426 development and implementation of standards for exchanging digital work products 427 across organizational boundaries IAW industry interoperability standards. The intent of 428 DWPX is to share the artifacts, workflows, and views created from the underlying data 429 and models in response to stakeholder queries. This approach should also accommodate 430 legacy artifacts. 431

h) Data Governance – The contractor shall provide policies and practices at the Enterprise 432 level that optimize, secure, manage, and leverage data and information as an Enterprise 433 asset. This includes, but is not limited to the identification of data owners responsible for 434 proper management, access, and usage, as well as data stewards responsible for data and 435 information quality. The contractor shall develop a data management approach to 436 implement the data governance policies on a day-to-day level. Where appropriate 437 policies and practices will be documented in existing plans to include, but not limited to: 438 the Data Management Plan (DMP), the Configuration Management Plan (CMP), and the 439 Systems Engineering Plan (SEP). A separate plan will be created if necessary to 440 document policies and practices that do not appropriately fit into existing plans. 441

i) Decision Support Dashboard – The DEE shall include a decision support dashboard, 442 accessible online by appropriately credentialed stakeholders, that provides current 443 metrics for AFSPC level content, SMC level content, and the Launch Enterprise level 444 content, to include, but not limited to: mission assurance, vehicle certification, mission 445 integration, and DEE implementation efforts. 446

j) Digital Roadmap and Maturity Model – The contractor shall provide a digital roadmap 447 and maturity metrics to guide the SMC/ECL organization’s transition to a data-centric 448 enterprise. 449

k) Mission Thread Models – The contractor shall collaborate with the SMC and AFSPC 450 community on the development of Mission Threads per the current version of JP 3-14 451 Space Operations. This includes the sharing of common models and underlying data and 452 information IAW the data-driven MBE approach. 453

l) DEE Conversion – The contractor shall convert (“migrate”) existing engineering data 454 products and procedures, as well as the engineering portions of the document-based Data 455 Management Plan (DMP) and Configuration Management Plan (CMP), into digital 456 work products IAW the MBE ontology and schema. 457

Integration 458 3.3.2.1.The Contractor shall provide overarching systems integration for launch 459 verification and integration with associated launch support systems across all 460 existing and new acquisition programs falling under SMC/ECL and the NSSL 461 enterprise. This activity will include integration between launch services and 462 associated launch support services. 463

3.3.2.2.The Contractor shall support concept trade studies for launch and other 464 relevant subjects as directed by SMC/ECL (e.g. west coast GPS launches, 465 autonomous flight termination, and space-based telemetry). 466

3.3.2.3.The Contractor shall support Mission Manifest Office (MMO) operations 467 relating to mission manifesting. Activities may include, but are not limited to, 468 SE&I related support relative to executing manifest activities. These activities 469 may involve supporting MMO cooperation with DoD, Intelligence Community, 470 Civil, and Commercial agencies. The Contractor will support MMO integrated 471 payload arrangement responsibilities and work with the MMO to establish 472 repeatable CONOPs in this developing work area. The Contractor shall support 473 of the Launch Manifest Systems Integrator on Do-No-Harm and Environmental 474 Analyses for all current and future launch vehicles. 475

3.3.2.4.The Contractor shall perform strategic planning for launch and range support 476 (e.g. LV program viability to 2030 and range divestiture), identify and propose 477 cost reduction initiatives, and launch systems sustainment strategies. 478

3.3.2.5.The Contractor shall support the AFSPC studies and Analysis of Alternatives 479 (AoA) for future launch systems (e.g., Space Enterprise Vision/Space 480 Warfighting Construct). 481

3.3.2.6.The Contractor shall support the development, and coordination of studies, 482 Broad Agency Announcements, and the like, in support of the NSSL strategy 483 for future development and acquisition for USG review as required. The 484 Contractor shall assess and make recommendations in response to external 485 program inquiries as required. 486

3.3.2.7.The Contractor shall support the development, technically assess, and update 487 SMC/ECL launch service acquisition strategies, request for proposals, and 488 supporting documentation for USG review as required. The Contractor shall 489 use standard, and create as necessary, templates and tools to document, update 490 and make recommendations for product disposition. Products include but are 491 not limited to the following: acquisition strategy plans and briefings; technical 492 Justification & Approvals; Requests for Proposals (RFPs); draft Performance 493 Work Statements (PWS); Work Breakdown Structure (WBS) Summaries; 494 Contract Data Requirements Lists (CDRLs); Incentive Plans; Proposal 495 Instructions; and other ad hoc documentation/presentations. The Contractor 496 shall support program management activities under the execution of launch 497 service contracts (excluding the NSSL Phase 1 contract FA8811-13-C-0003 498 and the NRO Delta IV Heavy sole source contract FA8811-16-R-0005) to 499 include review of contract deliverables, and support of program reviews as 500 required. 501

3.3.2.8.The Contractor shall provide master schedules that integrate acquisition tasks 502 for new NSSL contracts as required. 503

3.3.2.9.The Contractor shall provide technical assessments, evaluations and 504 recommendations for post-RFP release activities, to include fact finding, 505 proposal evaluations, and negotiations. 506

3.3.2.10. The Contractor shall assess and make recommendations in response to 507 external program inquiries as required. 508

3.3.2.11. Continuous Innovation and Improvement 509

a) The Contractor shall conduct ongoing assessments of SMC/ECL performance and 510 recommend innovative ways to improve that performance, to include, but not limited to, 511 process improvement. Accordingly, the Contractor shall also research innovations it is 512 implementing on other contracts for applicability, identify best practices elsewhere in 513 Government for applicability, and identify best practices in industry for applicability. The 514 Contractor shall present findings at the quarterly PMRs and document them in an 515 Innovation Recommendations Report. 516

b) The Contractor shall support Government processes to approve/disapprove 517 implementation of recommended innovations pursued by the Government. 518

c) The Contractor shall support implementation of innovations across applicable portions of 519 the SMC/ECL upon innovation approval. 520

Engineering Launch Support Systems (ELSS) 521 3.3.3.1.The Contractor shall technically analyze ELSS user-requested changes and 522 provide recommended implementation options to SMC/ECL. The Contractor 523 shall analyze the requested changes in the context of the ELSS requirements, 524 develop system designs, implement system updates, and document changes to 525 ELSS Launch Support Centers (LSCs), High Speed Network (HSN) and 526 campus network interface requirements. 527

3.3.3.2.The Contractor shall revise the ELSS Systems Requirements Document (SRD) 528 to reflect requirements changes. The Contractor shall perform technical 529 assessments of ELSS systems changes and document them as appropriate. This 530 will include ELSS systems integration and activation activities, and ELSS 531 system revisions to support LE launch vehicle systems operations. (ELSS 532 includes interfaces to NRO Operations Squadron (NOPS) and Spacelift 533 Telemetry Acquisition and Reporting System (STARS)). 534

3.3.3.3.The Contractor shall perform technical analysis of NOPS, CSC, and STARS 535 proposed changes to ELSS interfaces as specified in the Interface Control 536 Document (ICD). The Contractor shall provide written recommendations to LE 537 on optimum implementation of proposed changes to ELSS interfaces. The 538 Contractor shall document verification of revised ELSS interface requirements 539 implementation compliance by assessing end-to-end launch vehicle systems 540 and ELSS operations testing. 541

3.3.3.4.The Contractor shall develop and document a recapitalization plan for systems 542 satisfying ELSS requirements. The Contractor shall address supportability and 543 sustainment planning and shall perform and document Requirements Definition 544 and Functional Analysis as required when operational capability is identified 545 and determined. 546

3.3.3.5. As of FY20, the ELSS currently consists of the following LSCs: Launch 547 Vehicle Launch Support Center (LVLSCs) at CCAFS and VAFB supporting 548 United Launch Alliance (ULA) Atlas and Delta missions; the Multi-Vehicle 549 LSC (MVLSC) at CCAFS supporting Falcon missions; and the Falcon LSC 550 (FLSC) at VAFB supporting Falcon missions. The Contractor shall also 551 support any new LSCs in the future. 552

RD-180 Engineering 553 3.3.4.1.The Contractor shall develop, document and support integrated technical 554 assessments of Government-funded launch vehicle risks associated with the 555 RD-180 engine to accomplish Project Engineering tasks for the RD-180 engine 556 as outlined in paragraph 3.2.5. 557

3.3.4.2.The Contractor shall conduct integrated assessments to include an RD-180 558 Accountability Matrix, RD-180 Issues Log, analyses and recommendations in 559 support of USG technical review boards, and summary and analysis of launch 560 vehicle Contractor technical review boards, reported to SMC/ECL. 561

3.3.4.3.The Contractor shall evaluate and provide assessments of the RD-180 562 manufacturing process, to include foreign supplier political/management 563 reports, crossover assessments, and technology transfer status reports. 564

Project Engineering 565 3.3.5.1.The Contractor shall provide integrated assessments (as directed by SMC/ECL 566 at the time of performance) to aid USG evaluation of cost, schedule, and 567 performance risks and opportunities associated with NSSL systems, 568 subsystems and components. Subject breadth incorporates, but is not limited 569 to, separation systems, booster propulsion, upper stage propulsion, solid 570 motors, ordnance, avionics, structures, ground support equipment, payload 571 fairings, and launch site facilities. Integrated assessments may include but not 572 limited to draft Statement of Objectives (SOOs) and Statement of Work 573 (SOWs) for launch vehicle system modifications; draft PWS, Engineering 574 Change Proposals (ECPs), and Proposal Technical Evaluations; schedules, 575 weekly status reviews, telecons, Preliminary Design Reviews (PDRs), Critical 576 Design Reviews (CDRs), Program Management Reviews (PMRs), ARBs, 577 CABs, Engineering Review Boards (ERBs), TDMs, Pedigrees, Hardware 578 Acceptance Reviews, Design Center Walkdowns, development projects, 579 requirements, manufacturing, test, and discrepancies; and provide 580 recommendations in support of USG technical in support of USG technical and 581 acquisition activities. Capture and document Best Practices and provide 582 training and certification support as directed. Perform Fleet Surveillance of 583 non-NSS launch vehicle and acquisition activity and assess impact to NSS, and 584 provide mitigating recommendations as directed. 585

3.3.5.2.Operations Support: The Contractor shall coordinate cohesive technical and 586 program management activities and communication between the USG, launch 587 vehicle Contractor, the Aerospace Corporation, and other support Contractors 588 to enable launch readiness and provide integrated assessments. The Contractor 589 shall support development of training and certification and operations materials 590 for the Program Office Technical Team and participate in training, 591 certification, critical pre-launch and launch events (e.g., Integrated Crew 592 Exercises, Mission Readiness Review, Launch Readiness Review, Mission 593 Dress Rehearsals, Wet Dress Rehearsals, Static Fire, and Day of Launch.) The 594 Contractor shall support and assess pre-launch and post-launch reviews for 595 readiness and cross-overs. Functional areas: separation systems, booster 596 propulsion, upper stage propulsion, solid motors, ordnance, avionics, 597 structures, ground support equipment, payload fairings, and launch site 598 facilities. 599

3.3.5.3.Technical Issue Resolution Process (TIRP): The Contractor shall participate 600 in TIRP activities to assess issues and risks, both mission- specific and fleet-601 wide, associated with launch vehicle and ground systems, subsystems, and 602 components. The Contractor shall provide an integrated assessment and 603 recommendations to the USG regarding the status of mission- specific and 604 fleet-wide risk mitigation activities. Functional areas: separation systems, 605 booster propulsion, upper stage propulsion, solid motors, ordnance, avionics, 606 structures, ground support equipment, payload fairings, and launch site 607 facilities. Perform Fleet Surveillance and Resource Protection analyses and 608 assess for cross-overs from non-NSS missions to NSS Missions. Propose risk 609 mitigation activities in support of Mission Assurance. 610

3.3.5.4.Lessons Learned, Process Capture and Improvements: The Contractor shall 611 provide integrated assessments of LSP and DoD processes and media as 612 requested to aid USG evaluation of cost, schedule, and performance risks and 613 opportunities. The Contractor shall capture existing SMC/ECLG processes, 614 recommend enhancements, and collaborate as required to implement approved 615 changes. 616

3.3.5.5.The Contractor shall provide integrated assessments of the LSP's and supplier 617 subsystem/component design, performance, reliability/ maintainability, 618 operability and supportability (as required) and perform Fleet Surveillance of 619 non-NSS launch activity , assess impact to NSS, and provide mitigating 620 recommendations as directed. Assessments shall include but are not limited to 621 evaluations of factory operations, transportation, launch site operations, and 622 mission operations. 623

3.3.5.6.The Contractor shall assess the readiness of launch infrastructure (e.g., LSP, 624 USG and commercial) and perform Fleet Surveillance of non-NSS launch site 625 activity, assess impact to NSS, and provide mitigating recommendations as 626 directed in support of SMC/ECL programs to meet launch requirements and 627 recommend upgrades/repairs. The Contractor shall recommend changes to the 628 existing launch systems that could take advantage of identified and existing 629 USG or Commercial infrastructures and meet USG launch requirements. 630 Products include but are not limited to the Facilities, Infrastructure, and GSE 631 Database (FIDB) specification, facility walk-down reports, major launch site 632 maintenance and repair requirements, Facility Utilization Assessments, and 633 Ground Systems Readiness Reviews. Functional areas: CCAFS and VAFB 634 Space Launch Complexes used for SMC/ECL programs; ground support 635 equipment (GSE), and Electrical Ground Support Equipment (EGSE). 636

3.3.5.7.The Contractor shall evaluate launch infrastructure for supportability issues to 637 include parts obsolescence, facility refresh/refurbishment and other 638 supportability issues. The Contractor shall recommend upgrades/repairs and 639 prepare assessment reports as required. Functional areas: CCAFS, VAFB, and 640 KSC Space Launch Complexes used for SMC/ECL programs; GSE, and 641

EGSE. 642

3.3.5.8.The Contractor shall provide weekly written summaries on their project 643 engineering activity. 644

3.3.5.9.The Contractor shall perform project engineering and deliver associated 645 documentation as directed by the Government. 646

3.3.5.10. The Contractor shall develop products for and support the NECT in 647 technical reviews (e.g. ERB, System Verification Review (SVR), ChERB, as 648 appropriate), system level risks, test plan reviews, certification reports, NECT 649 IPT inputs, and CCB inputs. 650

3.3.5.11. The Contractor shall support meetings every two weeks regarding NASA, 651 NRO and/or NECT-related activities (e.g. ERB participation, information 652 sharing etc.). 653

3.3.5.12. The Contractor shall evaluate and track NE issues and NE change and 654 configuration management reporting, and shall provide reports to the NECT to 655 support these certification activities. 656

3.3.5.13. System Engineering Processes (CDRL A003) 657

3.3.5.14. The Contractor shall perform system engineering processes and tasks, 658 and shall deliver associated documentation, as directed by the Government 659

3.3.5.15. The Contractor shall maintain a risk database and present the information 660 in briefing chart format, as requested for risk management reviews. 661

3.3.5.16. The Contractor shall…