24Jan20_Tracked Changes_03_PWS.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

12 December 2019 24 January 2020 15

Department of the Air Force 19

Space and Missile Systems Center 20

Launch Enterprise 21

Los Angeles AFB, California 90245-2808 22

1. INTRODUCTION ................................................................................................................. 4 24

1.1. Scope ....................................................................................................................................4 25

1.2. Description of Service ............................................................................................................5 26

2. APPLICABLE DOCUMENTS .................................................................................................. 6 27

2.1. Compliance Documents .........................................................................................................6 28

2.2. Reference Documents ............................................................................................................6 29

3. REQUIREMENTS ................................................................................................................. 7 30

3.1. General Requirements ...........................................................................................................7 31

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

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

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

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

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

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

4. SERVICES SUMMARY ....................................................................................................... 70 38

4.1. General: .............................................................................................................................. 70 39

4.2. Performance Evaluation: ...................................................................................................... 70 40

4.3. Base support ....................................................................................................................... 72 41

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

4.5. GENERAL INFORMATION ..................................................................................................... 74 43

4.6. GENERAL SECURITY .............................................................................................................. 75 44

4.7. BACKGROUND INVESTIGATIONS .......................................................................................... 75 45

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

4.9. SECURITY MANAGEMENT .................................................................................................... 76 47

4.10. Employee Training: .............................................................................................................. 76 48

4.11. Employee Certifications: ...................................................................................................... 76 49

4.12. Dress and Appearance: ........................................................................................................ 77 50

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

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

4.15. HOURS OF OPERATION ........................................................................................................ 78 53

4.16. INSPECTION OF FILES: .......................................................................................................... 79 54

4.17. PERFORMANCE EVALUATION MEETINGS: ............................................................................. 79 55

4.18. Contractor Manpower Reporting ......................................................................................... 79 56

4.19. QUALITY ASSURANCE .......................................................................................................... 80 57

4.20. SAFETY: ............................................................................................................................... 81 58

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

APPENDIX B - GLOSSARY ......................................................................................................... 90 60

APPENDIX C - COMPLIANCE DOCUMENTS .............................................................................. 107 61

APPENDIX D - REFERENCE DOCUMENTS ................................................................................. 112 62

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

Annex A – Enabling Requirements ......................................................................................... 182 64

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

1. INTRODUCTION 68

1.1. Scope 69

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

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

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

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

b) Mission Integration Management 87

c) Systems Safety Engineering 88

d) Systems Environmental Engineering 89

e) Systems Security & Cybersecurity 90

f) Quality and Production 91

g) Manufacturing Engineering 92

h) Quality Engineering 93

i) Launch Schedule Management 94

j) Launch Risk Management 95

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

l) Data Management and Configuration Control Management 101

m) Enterprise Management 102

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

1.2. Description of Service 111

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

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

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

3.4.2 and 3.7). 132

2. APPLICABLE DOCUMENTS 135

2.1. Compliance Documents 136

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

2.2. Reference Documents 138

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

3. REQUIREMENTS 142

3.1. General Requirements 143

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

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

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

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

Staffing 162

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

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

Document Review 182

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

Contractor Recommendations 187

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

Meetings 196

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

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

Continuous Improvement Recommendations 209

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

Training Government Personnel 212

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

Priority of the Tasks 216

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

Small Business Utilization Report (CDRL A005) 221

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

Government Data Rights 226

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

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

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

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

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

CDRL A002. 249

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

Monthly Status Report- (CDRL A001 and A002) 257

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

3.2. Transition of SE&I-2 Effort 267

Kick-Off Meeting 268

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

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

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

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

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

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

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

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

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

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

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

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

Systems Engineering 320

3.3.1.1. Launch Systems 321

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

The Contractor shall perform the following: 333

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

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

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

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

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

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

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

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

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

a) System Performance Requirements Document (SPRD) 353

b) Standard Interface Specification (SIS) 354

c) Systems Engineering Plan (SEP) 355

d) Risk Management Plan (RMP) 356

e) Mission Assurance Plan (MAP) 357

f) SMC/ECL Process Guide 358

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

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

3.3.1.2. Configuration Management 363

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

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

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

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

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

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

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

(USG). 394

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3.3.2.11. Continuous Innovation and Improvement 510

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

EGSE. 643

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

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

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

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

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

3.3.5.13. System Engineering Processes (CDRL A003) 658

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

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

3.3.5.16. The Contractor shall evaluate the NE risk management plans for 663…