03_Attachment_1_Phase_2_PWS.docx

ATTACHMENT 1

EVOLVED EXPENDABLE LAUNCH VEHICLE (EELV)

PHASE 2 LAUNCH SERVICE PROCUREMENT

PERFORMANCE WORK STATEMENT (PWS)

FA8811-19-R-0002

(21 Feb 2019)

Department of the Air Force Space and Missile Systems Center Launch Enterprise Systems Directorate Los Angeles Air Force Base, California

Table of Contents

LIST OF TABLES

This Page Intentionally Left Blank.

The Air Force is seeking industry’s feedback on the EELV Phase 2 Launch Service Procurement (LSP) draft Request for Proposal (RFP), which is designed to provide Assured Access to Space for National Security Space (NSS) Requirements. This is industry’s opportunity to provide the Air Force feedback on this draft RFP and how industry can best meet NSS launch requirements, provide the warfighters the launch flexibility they need, while leveraging commercial launch capability. This is the first of two draft EELV Phase 2 RFPs the Air Force plans to release.

EVOLVED EXPENDABLE LAUNCH VEHICLE LAUNCH SERVICES

DESCRIPTION AND SCOPE OF THE LAUNCH SERVICES

This Performance Work Statement (PWS) defines the launch services (LS), launch service support (LSS), mission integration (MI), mission-unique (MU), and level of effort (LOE) work the Contractor will perform for National Security Space (NSS) missions. The PWS includes the Program Management, Systems Engineering, Launch Vehicle (LV) Production, Mission Integration, Mission Operations, Support to Government Space Flight Worthiness (SFW), LOE Activities, and Mission-Unique Options necessary to deliver healthy Payloads (PL) (or Integrated Payload Stacks [IPSs]/Aft Payload Stacks [APS]) into their intended orbits managed by Air Force Space Command, Space and Missile Systems Center (AFSPC/SMC).

An Evolved Expendable Launch Vehicle (EELV) launch service includes all tasks necessary to deliver National Security Space (NSS) payloads to defined orbital parameters in compliance with mission requirements as described in Section 3 (Space Launch Service). LS requirements apply to discrete activities for each individual NSS mission, and will be executed in accordance with (IAW) Contract Line Item Number (CLIN) 0001. LSS requirements apply to non-discrete, NSS-driven activities, and will be executed IAW CLIN 0005. Mission Integration (MI) requirements (found subsection 3.4) and Mission-Unique (MU) requirements (subsection 3.8) will be executed as options IAW CLIN 0002. Level of Effort (LOE) requirements (subsection 3.7) will be executed IAW CLINs 0003 and 0004.

During post-award contract execution, the Contractor may request, in writing, USG approval to allow relevant activities, documentation, and information developed under other contracts/agreements with the USG, to be used to satisfy the requirements of this PWS. Acceptance on previous activities does not guarantee acceptance on this contract.

A glossary of definitions for terms used in and applicable to this PWS is provided in Appendix A. An Acronyms and Abbreviations list is provided in Appendix B.

DEFINITION OF ROLES and Responsibilities Roles Launch Service Provider (LSP) The term “Launch Service Provider (LSP),” used interchangeably with “The Contractor,” refers to the party responsible for supplying the Launch Service and LSS detailed in this PWS.

Government The term “Government” refers to Department of Defense (DoD) personnel, including military and Government civilians.

United States Government Team The term “USG Team” refers to the Air Force Space and Missile Systems Center/Launch Enterprise Systems Directorate (SMC/LE) program office and Air Force Program Executive Officer office personnel, but also includes the Aerospace Federally Funded Research and Development Center (FFRDC), SMC/LE Systems Engineering and Integration (SE&I) contractors, SMC/LE Systems Engineering and Technical Assistance (SETA) support contractors, SMC/LE Advisory & Assistance Service contractors, the NRO/Office of Space Launch (OSL), NRO/OSL SETA support contractors, NRO/OSL Independent Verification and Validation (IV&V) support contractors, the SMC Independent Readiness Review Team, Defense Security Service, Defense Information Systems Agency, Defense Contract Management Agency, Defense Contract Audit Agency, 30th Space Wing (30 SW), 45th Space Wing (45 SW), and other organizations as designated by SMC/LE Procuring Contracting Officer (PCO). Refer to Appendix H for Government Program Contracts Requiring Interface with Aerospace Federally Funded Research and Development Center (FFRDC, Prime, and Support contractors). Estimates of the number of USG Team individuals associated with specific requirements in this PWS are listed in Appendix E (United States Government Team Call-Outs).

Government Hardware Review Team The Government Hardware Review Team is the team comprised of USAF, civilian, SE&I, and Aerospace FFRDC personnel directly involved with supporting and performing independent hardware reviews. The OSL/Mission Assurance Team (MAT) will also participate in these reviews.

Launch Mission System Integrator (LMSI) The Launch Mission System Integrator is the contractor with responsibility, authority, and accountability for delivering an EELV Integrated Multi-manifest Carrier (IMMC) end-item (including Multi-manifest Space Vehicles (MSVs)) to the LSP.

Government Mission Integration Manager (GMIM) For USAF missions, the Government Mission Integration Manager (GMIM) is the lead interface between LV and PL (IPS/APS) programs orchestrating launch campaigns, including operations planning, flight certification, and mission rehearsals. The GMIM also manages technical and funding changes between the PL (IPS/APS) and the LV and coordinates LV/PL (IPS/APS) interface requirements. For NRO missions, the GMIM is the lead interface between SMC/LE and OSL.

Government Mission Director (GMD) The Government Mission Director (GMD) is the Senior Air Force (for USAF missions) or NRO-OSL (for NRO missions) official who is assigned responsibility for successfully delivering the integrated LV/PL (IPS) to the proper orbit. The GMD must be involved in issue resolution for both the LV and the PL (IPS) through the launch campaign.

Rehearsal Anomaly Team (RAT) The Rehearsal Anomaly Team (RAT), consisting of representatives from each agency participating in the launch, is responsible for planning rehearsals. The RAT generates launch countdown scenarios, including anomalies that will exercise their teams for Day of Launch (DoL) preparation.

Space Wing The term Space Wing (SW) includes subordinate units that provide generation and launch execution of space launch systems. 30 SW provides generation and launch execution of space launch systems for Vandenberg Air Force Base (VAFB) missions. 45 SW provides generation and launch execution of space launch systems for Cape Canaveral Air Force Station (CCAFS) and KSC (Kennedy Space Center) missions. The Government Launch Operations Team The Government Launch Operations Team is the mission team comprised of USAF, OSL, SE&I, and FFRDC personnel directly involved with planning and execution of Government launch operations for a specific mission. This includes personnel at SMC and the respective SW at the launch site.

Space Vehicle Team (SV Team) The term “SV Team” refers to the SV Directorate(s)/Program Office(s) (SPO), Space Vehicle Contractor(s) (SVC) personnel, but also includes the FFRDC supporting the Systems Program Office (SPO), SE&I and SETA Contractors supporting the SPO, the SV’s Payload Processing Facility (PPF) personnel, and the LMSI representing the Multi-manifest SVs.

Space Vehicle Contractor (SVC) The Space Vehicle Contractor (SVC) is the contractor with responsibility for delivering an SV and necessary data documentation to the respective SPO.

Responsibilities Notify Notification is a Contractor responsibility to officially inform USG Team about an action, activity, or decision process. The Contractor is not required to deliver data, generate action items to be tracked and closed outside of the relevant event, or attain USG approval, unless otherwise specified in the relevant PWS paragraph. Notification is considered complete when the USG Team acknowledges receipt.

Invite Invitation is Contractor responsibility to allow USG Team to observe meeting/event. When the Contractor is required to "invite" the USG Teamto observe a meeting/event, USG approval of that meeting/event (or data generated therein, unless otherwise required by the contract) is not required. The Contractor is required to answer the USG's clarification questions. The Contractor is not required to generate action items to be tracked and closed outside of the relevant meeting/event. When the Contractor is required to "invite," the relevant meeting/event can be completed without Government attendance.

Support Support is a Contractor responsibility to actively cooperate with the USG Team in a USG-led meeting/event. When the Contractor is required to "support" a meeting/event, the Contractor may be required to provide data or a recommendation. The Contractor may also be required to generate action items to be closed outside of the relevant meeting/event, and to track the status of those action items throughout the Period of Performance (PoP). For questions on the data products required for a given meeting/event, consult the relevant PWS paragraph.

Lead Leading is a Contractor or Government responsibility consisting of scheduling a meeting/event, facilitating appropriate participation in the meeting/event, and ensuring meeting/event objectives are met. When the Contractor is required to "lead" a meeting/event, the Contractor is required to provide a standard set of data products, unless otherwise indicated in the relevant PWS paragraph. This standard set of data products includes a meeting agenda, presentation materials, and meeting minutes. The Contractor may also be required to generate action items to be closed outside of the relevant meeting/event, and to track the status of those action items throughout the PoP. For questions on the data products required for a given meeting/event, consult the relevant PWS paragraph.

Participate Participation is a USG Team activity comprised of actively cooperating with the Contractor in a Contractor-led meeting/event. The USG Team may provide data or a recommendation for the Contractor to consider, but USG approval of the meeting/event (or data generated therein, unless otherwise required by the contract) is not required. The Contractor may be required to generate action items to be tracked and closed outside of the relevant meeting/event, so long as those action items are directly related to the fulfillment of a paragraph or multiple paragraphs in this PWS.

APPLICABLE DOCUMENTS

COMPLIANCE DOCUMENTS

The Contractor shall comply with the applicable documents listed in Appendix C as approved in accordance with (IAW) CDRL A019.

REFERENCE DOCUMENTS

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

DOCUMENTATION DE-CONFLICTION

For each mission, if a conflict exists between the signed mission Interface Control Document (ICD), the Mission Requirements Annex (MRA), the Interface Requirements Document (IRD), and the Standard Interface Specification (SIS), the mission ICD shall be given precedence. For requirements on which the ICD is silent, the SIS, MRA, and IRD shall apply. Other documents shall be given precedence IAW Federal Acquisition Regulation (FAR) 52.215-08 and FAR 52.212-04(s).

SPACE LAUNCH SERVICE

The Government requires services to meet NSS launch needs. Space Launch Services for NSS missions include LV production and transportation, mission integration, launch operations, support to independent Government mission assurance, base and range support, mission commodities, all associated program management and systems engineering functions and tasks, and special studies as defined in PWS Subsection 3.7 (Quick Reaction/Anomaly Resolution/Special Studies).

The Contractor shall provide Space Launch Services for NSS missions IAW the performance requirements stated in the Evolved Expendable Launch Vehicle (EELV) System Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), MRA, and relevant mission ICD(s). The Contractor shall control, document, and provide the USG Team continuous access and insight into its processes and assessments of progress and performance of all Space Launch Service requirements, provide continuous access to the Contractor’s command media, and support the USG’s Independent Mission Assurance activities, as defined in the paragraphs below and the associated CDRLs.

PROGRAM MANAGEMENT FUNCTIONS AND TASKS

LSS/LS: The Contractor shall identify a Program Manager (PM) and perform all program management functions and tasks necessary to deliver launch services and to satisfy the requirements for the mission consistent with operational quality, safety, security, and environmental standards. The program management function of this contract shall provide insight to the Government for all technical and programmatic activities performed under this contract.

LSS: The Contractor shall establish and maintain a risk management process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: The Contractor shall establish and maintain a manufacturing management process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: The Contractor shall establish and maintain a reliability program that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: Launch System Data LSS: The Contractor shall implement and maintain continuous USG access to an Integrated Data Environment (IDE) comprised of all Launch System Data generated in support of this contract. The Contractor shall enable USG enterprise-level (large scale) ability to perform bulk and incremental download and synchronization of Launch System Data. The Contractor shall enable the USG Team to access and download both raw (e.g., SAP) and processed (e.g., pdf, csv, etc.) launch system data. The Contractor shall notify the USG Team of any updates to delivered Launch System Data products as soon as possible, but no later than 1 CD after the update. The Contractor shall have the ability to transfer data to a common data storage environment as new data become available. The Contractor shall collaborate with the USG Team to protect (access to and security of the data) the Contractor data stored on Contractor systems, USG systems, and common data storage environment. The Contractor shall provide the USG Team with access to the Contractor’s collaboration platforms, including collaboration spaces, and ticketing systems, to exchange data and to review launch system data. The Contractor shall enable the USG Team and SV Teams to remotely access the launch system data via the Contractor’s electronic data repository host systems for the purpose of reviewing, uploading, and downloading specific, identified program-related data on Contractor host systems. The Contractor shall be responsible for providing access to the data, administering user accounts, marking the data, and ensuring the integrity of the data. The Contractor shall provide server/folder location of data and confirm appropriate permissions have been provided. The Contractor shall notify the Government at least 24 hours in advance of all planned network outages and system upgrades that could interrupt access to the systems, or as soon as possible in the case of unplanned interruptions.

LSS: Software Product Specification The Contractor shall deliver the computer software and licenses needed to instantiate USG Team access to the IDE. For all Contractor modifications to commercial computer software (e.g., Microsoft SharePoint) used to create the IDE, the Contractor shall deliver the source code needed to instantiate the IDE on USG systems. (CDRL A002) LSS: Software Version Description The Contractor shall identify all versions of commercial computer software used to create the IDE, and modifications made to those software applications that are needed to instantiate the IDE on USG systems. (CDRL A002) LSS: Database Design Description The Contractor shall provide a Database Design Description to describe the design of the database that comprises the IDE. The Contractor shall provide description of the IDE instantiation, to include the file folder structure/hierarchy, levels of access rights and privileges specified at the user level (e.g., administrator, guest, super-user) and at the data/deliverable level (e.g., ability to allow access to specific data/deliverables to selected users only based upon the classification level and level of license rights associated with that data) into which the data will be deposited, and search functions. (CDRL A002) LSS: Data Accession List The Contractor shall maintain a list of all data supporting this contract on a Data Accession List (DAL). (CDRL A001) LSS: Launch System IDE Training The Contractor shall provide the USG Team on demand Launch System IDE computer-based training. USG team users will receive IDE access only after completing the necessary security and data access training. Such training shall include the following subjects: Work Authorizing Documents (WAD) access and feedback, anomaly/non-conformance system, launch console data system, specification and engineering file management system, In the event of changes to the Software Product Specification, Software Version Description, Database Design Description, or user interfaces to the IDE, the Contractor shall update the computer-based IDE training. (IDE) LSS: Program Management Data Reporting Note: The Contractor may provide the data items listed in this paragraph outside the IDE.

The Contractor shall collect and report program data to SMC/LE by providing the following:

A. Cost Data Summary Report (CDRL A003) B. Functional Cost-Hour Report (CDRL A004) C. Contractor Business Data Report (CDRL A005) D. Contractor Work Breakdown Structure (CDRL A006) E. Small Business Utilization Report (CDRL A007) F. Integrated Program Management Report – Integrated Master Schedule (IMS) (CDRL A008) LSS: Program Management Reviews The Contractor shall lead monthly Program Management Reviews (PMRs) to: report development and production status, report CDRL status, ensure schedules support program objectives, review action items, review program data reports, and discuss all issues. The intent of the PMR is to provide a forum for open dialog between the USG Team and the Contractor. The Contractor shall provide the USG Team the PMR briefing slides NLT 5 calendar days (CDs) prior to the review or as agreed to by the parties. SMC/LE and the Contractor will agree to the PMR agenda NLT 14 CDs prior to the PMR or as agreed to by the parties. The PMR agenda shall include a status of the following topics at a minimum: Programmatics, Business Operations, Flight Manifest Status, Production Operations, Quality Metrics, Configuration Management, Risk Management, Program Protection/Cybersecurity Status, Subsystem(s) Status, Mission Integration Status, Non-Recurring Work Status, Launch Operations, Major Subcontractor(s) Performance, IV&V status, working group status, special topics and Wrap Up/Action Items. PMRs will be planned for 3 hours but last no more than 1 business day. Locations may rotate between Contractor and Government facilities. The Contractor shall invite the USG Team to major subcontractor PMRs or equivalent reviews. (IDE) LSS: The Contractor shall provide a Mission Integration Management Plan (MIMP), which defines the Contractor’s standard process flow for first time and previously flown PL (IPS) integration with the LV. The MIMP shall include the organizational roles and responsibilities, management approach, documentation products, integration meetings, working groups, reviews, and controls required to implement the integration process for the mission. (CDRL A010)

LS/LSS: Launch Manifesting Process LSS: The Contractor shall support the Government-led launch scheduling and manifesting process to include the following reviews and meetings: a semi-annual Current Launch Schedule Review Board, a semi-annual Government Integrated Meeting, a monthly Senior Management Review, weekly launch manifest status teleconferences. The Contractor shall also lead a monthly manifest review. (Ref. Air Force Space Command Instruction [AFSPCI] 13-1213) LSS: The Contractor shall develop and provide the USG Team Launch Schedule Option Assessments as part of the launch manifesting process. (IDE) LS: The Contractor shall provide the USG Team a Launch Slot Recommendation and Launch Date Recommendation within the assigned launch period for each launch mission. (CDRL A022) LSS: System Safety Program LSS: Per SPRD360, the Contractor shall provide a System Safety Program Plan and Safety Assessment Report IAW MIL-STD-882E (T) (CDRLs A012, A029).

LSS: The Contractor shall provide (at a minimum) “government purpose rights,” (ref. DFARS §§ 252.227-7013(a)(13), 252.227-7014(a)(12)) of all the data recorded in the Hazard Tracking System (HTS) and all other items (i.e., studies, analyses, test data, notes or similar data) generated in the performance of the contract with respect to the HTS. (IDE) LSS: Range Safety The Contractor shall coordinate requests for relief from the tailored Air Force Space Command Manual (AFSPCMAN) 91-710 for all missions under this contract with SMC/LE, and Range Safety prior to formal submittal. (CDRL A019) LSS: Per SPRD400, the Contractor shall coordinate RCC 324-11 tailoring requests, equivalent level of safety certifications, and non-compliance waiver relief requests for all missions under this contract with SMC/LE in parallel with formal submittal to Range Safety. (CDRL A019) LSS: Per SPRD410, the Contractor shall coordinate RCC 319-10 (T) tailoring requests, equivalent level of safety certifications, and non-compliance waiver relief requests for all missions under this contract with SMC/LE in parallel with formal submittal to Range Safety. (CDRL A019) LSS: Autonomous Flight Safety System (AFSS) Per SPRD420, the Contractor shall equip its launch system with an AFSS.

LS/LSS: Safety Training LS: The Contractor shall provide all Contractor-required safety training to USG Team and SV Team personnel for Contractor facilities and flight hardware used in performance of individual launch service task orders on this contract to ensure USG Team access to those facilities and flight hardware. (Ref. paragraph 3.6.2.5) LSS: The Contractor shall provide USG Team personnel all training required to enter Contractor facilities or the LV at all stages of production for LVs used in performance of fleet processing and non-discrete, NSS-driven activities on this contract to ensure USG Team access to those facilities and flight hardware (Ref. paragraph 3.6.2.5). The USG Team will follow all guidelines and rules for access to Contractor facilities. Failure to do so may result in lost access.

LSS: Launch System Familiarization Course The Contractor shall provide the USG Team an instructor-led Launch System Familiarization (FAM) Course three times per calendar year to provide training to the Government team supporting NSS missions with the LSP, at locations to be determined by SMC/LE. The FAM Course shall be conducted in two parts: a 1-day overview for non-technical personnel and a 2-day in-depth engineering system familiarization. The Course shall cover all training material, and the Contractor shall provide a self-study guide to accompany the training course consisting of the training materials, test questions, and answers. (CDRL A018).

LSS: Program Protection The Contractor shall develop, provide, implement, and maintain a Program Protection Implementation Plan IAW the EELV Program Protection Plan (PPP). (CDRL A011) LSS: The Contractor shall support the USG Team in annual EELV Program Protection Surveys at all Contractor facilities IAW the EELV PPP.

LSS: The Contractor shall support the quarterly EELV System Security Working Group and one security-related meeting per month IAW the EELV PPP (e.g., Information Technology [IT] Security Breach or Unauthorized Information Distribution resolutions).

LSS: The Contractor shall provide support to the USG Team in the development of the EELV PPP Contractor-specific Annex. The Contractor shall provide the LV-specific and support ground system architecture specific information necessary to document, identify, assess, and mitigate security related vulnerabilities and risks.

LSS: Operations Security The Contractor shall develop, implement, and maintain an Operations Security (OPSEC) program IAW contract Attachment 2, DoD Contract Security Classification Specification (DD254). (Ref. Air Force Instruction [AFI] 10-701 and the EELV OPSEC Plan).

LSS: Anti-Terrorism The Contractor shall implement and maintain an Anti-Terrorism Program for activities at CCAFS, KSC, and VAFB as appropriate. The Contractor shall ensure SMC/LE and NRO/OSL approval prior to taking action regarding anti-terrorism requirements requested by the 30 SW Operations Security Office or 45 SW/Anti-Terrorism Office that change or add additional anti-terrorism requirements to this PWS paragraph and subparagraphs. (CDRL A015) LSS: Meeting Support: The Contractor shall provide site security leads to support one meeting per year.

LSS: Program Reviews: The Contractor shall perform an in-house Annual Review of its Anti-Terrorism program, which shall be documented IAW the host Wing Anti-Terrorism Office checklist. (CDRL A015) LSS: Training: The Contractor shall perform annual training utilizing SMC/LE Anti-Terrorism training materials as a guideline. The Contractor shall create a Corporate Annual Training Letter stating that all site personnel have completed their individual Anti-Terrorism training.

LSS: Force Protection Condition (FPCON) Checklists: The Contractor shall utilize site-specific FPCON checklists provided by SMC/LE at each launch site.

LSS: Random Anti-Terrorism Measures (RAMs): The Contractor shall perform prescribed RAMs or alternate RAMs that are preapproved by SMC/LE (up to five per month). Completed RAMs shall be documented in a format prescribed by SMC/LE and reported quarterly to the Host Wing Anti-Terrorism Office. (CDRL A015) LSS: Mission Essential Personnel: The Contractor shall create and maintain a “Mission Essential Personnel” list and an “Emergency Essential Personnel” list for higher FPCON levels (Charlie and Delta) and other emergency situations at each launch site. The Contractor shall provide these lists to the appropriate launch site personnel in advance of emergency situations and in the event of changes.

LSS: Cyber Security The Contractor shall provide evidence of compliance with International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 27001 and National Institute of Standards and Technology (NIST) 800-171 derived from activities performed to establish and maintain compliance upon Government request. This shall include initial and annual audit reports, Contractor-developed compliance documentation, such as plans, procedures, and reports, plan of action and milestones (POA&Ms), and requests for waivers. The Contractor shall notify the Government of cyber security audits and coordinate schedules to ensure Government participation.

Physical Security Contractor operations within EELV restricted areas shall not degrade or impede the ability of DoD security forces to maintain compliance with AFI 31-101, Integrated Defense, and the Air Force Space Command supplement to AFI 31-101 operations and physical security requirements. Contractor-developed structures within EELV Restricted Areas shall comply with all AFI 31-101 applicable physical security requirements. Contractor facilities outside of EELV restricted areas housing EELV Critical Program Information (CPI) and critical components (CC) shall comply with physical security requirements identified in the EELV Program Protection Plan, and use Contractor-specific Program Protection Implementation Plan (PPIP) derived protection and countermeasures.

LSS: Environmental Requirements (NSS) LSS: The Contractor shall provide to the USG Team each environmental impact analysis document, environmental report, and applicable meeting notices related to or that impact the launch system. This includes associated correspondence sent to or received from environmental regulatory agencies and the host Wing but does not include informal telephone and e-mail communication. (IDE) LSS: The Contractor shall include SMC/LE in the coordination process with the host Wing and the environmental regulatory agencies relating to the application, development, or modification of permits or required environmental compliance plans, environmental cleanup actions, or other major efforts subject to environmental laws and regulations. During the coordination process, the Contractor shall provide information to the on-site USG Team environmental representatives to ensure that the USG Team is aware of the risks and alternatives that are evaluated or accepted. (IDE) LSS: The Contractor shall provide data needed to allow SMC/LE to lead the Environmental Impact Analysis Process IAW National Environmental Policy Act and Executive Order 12114, Environmental Effects Abroad of Major Federal Actions, dated 4 January 1979. (CDRL A016) LSS: Hazardous Materials The Contractor shall provide a hazardous materials management plan IAW AFSPCMAN 91-710 and Task 108 of MIL-STD 882-E (Ref: NAS 411 Hazardous Materials Management Program for guidance). (CDRL A013) LSS: Incident and Discrepancy Reporting The Contractor shall maintain an incident and discrepancy reporting system. The Contractor shall notify the USG Team of all incidents and discrepancies. (IDE) LSS: The Contractor shall notify the USG Team of incidents and discrepancies during the execution of this contract that involve (1) loss of life or severe personal injury as defined per Occupational Safety and Health Administration reporting requirements; (2) damage to flight hardware or launch infrastructure critical ground systems; or (3) damage to launch infrastructure critical ground systems occurring during vehicle build, test, transportation, processing, or facility readiness operations. The notification shall be provided as soon as operationally possible, but NLT 48 hours (post-emergency response and safety hazard securing) and IAW already-established Contractor reporting procedures. The Contractor shall provide the status of ongoing investigations, Contractor incident root cause data, and determination and associated corrective actions. (IDE) LSS: The Contractor shall notify the onsite USG Team as soon as operationally possible (post emergency response) of hazardous materials and waste releases that require coordination with Governmental regulatory agencies.

LSS: The Contractor shall report within 48 hours of an event’s occurrence all incidents and all discrepancies that may be or are a major non-conformance or that may lead to one or more of the following: (a) delay to the ship date of flight hardware for NSS missions, (b) out-of-position (OOP) work transferred to the launch site, (c) changes to the IMS (including applicable Mission Integration Schedules), (d) waivers or exceptions to test or verification requirements, or (e) impact a scheduled launch date. The Contractor shall provide the status of ongoing investigations, Contractor incident root cause data, and determination and associated corrective actions. For all other incidents and discrepancies, notification shall be NLT 14 CDs of an event’s occurrence and status reporting will be determined by SMC/LE on a case-by-case basis.

LS: Public Affairs Activities The Contractor shall support Public Affairs activities related to this contract by coordinating with SMC/LE and the Space and Missile Systems Center Public Affairs Office (SMC/PA). The Contractor shall coordinate press statements, press releases, or all related public affairs items related to missions executed under this contract with SMC/PA prior to release to the general public.LS: Mission Milestone Reviews LS: Mission Milestone Reviews The Contractor shall lead or support the Mission Milestone Reviews, as defined in Appendix G (Mission Milestone Reviews). The Contractor shall provide the USG Team the briefing slides for each Mission Milestone Reviews NLT 5 CDs prior to the review or as agreed to by the parties. Support to USG Team readiness reviews includes attendance, presentation of requested information, and providing answers to questions posed during reviews or as follow-up questions related to material presented. For the milestone reviews, the Contractor shall attest to the review Chairman whether the Launch System is ready to proceed with continued processing, assess the margin to the planned schedule, and discuss issues and risks as appropriate. For the Government’s FRR and LRR, the Contractor shall attest to the review Chairman whether the Launch System is ready to proceed with launch.

SYSTEMS ENGINEERING FUNCTIONS AND TASKS

LSS/LS: In order to ensure the successful completion of the missions on this contract, the Contractor shall perform systems engineering functions and tasks necessary to deliver launch services consistent with operational safety, suitability, and effectiveness (OSS&E) and Environmental Safety and Occupational Health guidance on EELV systems. In order to ensure the Government can accomplish its mission assurance functions and tasks, the Contractor shall maintain and provide the USG Team insight into the systems engineering processes supporting the launch service. In order to facilitate smooth and unimpeded communication between the USG Team and the Contractor, the Contractor shall identify a Product Line Chief Engineer (or equivalent) to work with the USG Product Line Chief Engineer to manage and control the activities in this subsection.

LSS: Technical Interchange Meetings The Contractor shall invite the USG Team to Technical Interchange Meetings (TIMs) or all Contractor-equivalent boards 48 hours in advance (or as soon as possible, if scheduled less than 48 hours in advance.) and make available all meeting documentation materials. (IDE) LSS: Contractor Engineering Databases The Contractor shall provide the USG Team access to the Contractor’s non-recurring, recurring, manufacturing, and engineering databases, to include, but not limited to non-conformances, drawings, configuration control, risk, production, launch operations, risk management, change management, quality management, test database, design repositories, systems engineering models, requirements tracking, closeout photos, flight observations, anomalies, and other similar engineering databases that meet both of the following criteria: (1) are used by the Contractor to assess the launch system, and (2) are necessary to support space flight worthiness (SFW) certification, crossover assessments, and in-plant technical surveillance by the USG Team. USG Team members may be held responsible for successfully completing Contractor-provided training prior to being granted access (IDE) LSS: Systems Engineering Boards and Processes The Contractor shall obtain USG Team approval of a plan to meet the intent of requirements in this paragraph and its subparagraphs. The plan shall include a comprehensive list of the Contractor’s equivalent systems engineering boards and processes along with the nominal meeting date and time The Contractor shall lead USG Team participation in Launch System: Risk Management Boards (RMB); Engineering Review Boards (ERB); Anomaly Review Boards (ARB); Technical Review Boards (TRB); Corrective Action Boards; Change Control Boards for technical issues; Material Review Boards (MRB); Failure Review Boards (FRB); Parts, Materials, and Processes Control Boards (PMPCB); Systems Safety Groups (SSGs);, System Verification Review; Production Readiness Review (PRR); Test Readiness Review; Shipping Readiness Reviews (SRR); Pre-Launch Reviews; or Contractor-equivalent boards or processes. (IDE) LSS: The Contractor shall establish and maintain a life cycle systems engineering process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: The Contractor shall lead and facilitate USG Team participation in Launch System Preliminary Design Review (PDR); Critical Design Review (CDR); Functional and Physical Configuration Audits (FCA/PCA), or Contractor-equivalent boards or processes. The Contractor shall establish and maintain a process for technical reviews (TRs) and audits that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: The Contractor shall establish and maintain processes for design, analysis, manufacturing, test, and operations that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019.

LSS: For recurring review boards, the Contractor shall invite the USG Team NLT 10 CDs in advance of the board (or as soon as possible, if scheduled less than 10 CDs in advance). For all other review boards, the Contractor shall invite the USG Team as soon as possible after the board is scheduled. (IDE) LSS: The Contractor shall facilitate USG Team virtual participation for Systems Engineering boards. (Ref. Appendix E) (IDE) LSS: The Contractor shall provide the USG Team entrance and exit criteria for System Engineering boards. (IDE) Launch System Configuration Management LSS: The Contractor shall establish and maintain a configuration management process that complies with the applicable standards listed in Appendix C per the instructions in CDRL A019. (CDRL A022) Launch System Configuration Reporting LSS: As Designed Configuration List (CDRL A033) The Contractor shall provide and update the As Designed Configuration List (ADCL) specific to the NSS launch services delivered under this contract. The Contractor shall provide a unique ADCL for each unique LV configuration to be delivered.

LS: As Built Configuration List (CDRL A034) The Contractor shall provide and update the As-Built Configuration List (ABCL) specific to the NSS launch services delivered under this contract.

LS: Flight Critical Items List (CDRL A035) The Contractor shall provide and update the Flight Critical Items List (FCIL) specific to the NSS launch services delivered under this contract.

LS: Ground Critical Items List (CDRL A035) The Contractor shall provide and update the Ground Critical Items List (GCIL) specific to the NSS launch services delivered under this contract.

LSS: As Built Configuration List for Fleet Insight For Launch System families intended to be used on this contract, the Contractor shall provide and update the As-Built Configuration List for Fleet Insight. (CDRL A020) Launch System Configuration Change Reporting Note: The requirements in paragraph 3.2.4.3 and its subparagraphs do not apply prior to the establishment of the final product technical baseline.

LSS: For all missions in which the Contractor is using Launch System families intended for use on this contract, the Contractor shall provide the USG Team configuration changes to be implemented on the USG certified/approved launch system configurations. (IDE) LS: For all launch services delivered under this contract, the Contractor shall provide notification of all changes to the ADCL specific to each launch service. The change notification shall identify the class of change (Ref. Appendix J).

For Class 1A changes, the Contractor shall provide initial technical rationale (Design Evolution Narrative, Design Requirements and Interfaces, Principles of Operation, Acceptance/Qualification Test Plans/Procedures, Test-Like-You-Fly (TLYF), and exceptions/deviations) as soon as available and NLT L-15 months for first affected NSS mission, unless approved by the USG Team for a later date.

For Class 1A changes, the Contractor shall provide the final technical rationale (CDRL A036) that includes: Design Evolution Narrative, Design Requirements and Interfaces, Design Environments, As-built Design, Software Design, Supporting Design Analyses, Principles of Operation, Limited Operating Life Items Tracked, Summary of Required Manufacturing Processes, Summary of Logistics, Summary of Failure Modes and Effects Analysis and Reliability Assessment, Summary of Identified Risks, Acceptance/Qualification Test Plan/Procedures, Test-Like-You-Fly Exceptions and Deviations, Qualification Rationale, Qualification Test Results, List of Test Nonconformances, Summary of Flight Data, and Configuration Differences Between Unit Under Test (UUT) and Qualification Unit (e.g., UUT includes Flight and Proto Qualification Units), unless determined by the Government to be non-applicable, as soon as available and reporting NLT L-12 months unless approved by the Government for a later date.

For Class 1B changes, the Government Product Line Chief Engineer will work with the Contractor Product Line Chief Engineer (or equivalent) to mutually establish the appropriate level of data requirements (see Class 1A above) and reporting NLT L-12 months for the first affected NSS mission, unless approved by the USG Team for a later date.

For Class 2 changes, the Contractor shall notify the USG Team and provide the initial technical rationale as available and as soon as possible but NLT 10 CDs after identifying the change. The Contractor shall provide the final technical rationale NLT 30 days prior to coordinating the Government Hardware Reviews as defined in Section 3.6.4 (Government Hardware Review) (CDRL A034).

The Contractor shall provide the USG Team with a list of all flight hardware components/systems removed and replaced during the launch vehicle production and testing flow NLT 7 CDs prior to Wet Dress Rehearsal (WDR) or equivalent, NLT 7 CDs prior to Flight Readiness Review (FRR), and immediately for all flight hardware component/system removed and replaced afterwards.

Launch System Configuration Change Approval and Implementation LS: The Contractor shall obtain USG approval for Class 1A changes NLT L-12 months unless approved by the USG for a later date.

LS: The Contractor shall obtain USG approval for all classes of changes after L-60 days LS: The Contractor shall implement (engineering drawings released, hardware produced and incorporated for this launch service or another mission, qualification/acceptance testing complete) all Class 1A and Class 1B changes NLT L-6 months for the first affected NSS mission, unless approved by the USG for a later date.

LSS: The Contractor shall communicate changes to the launch system’s interface with Engineering Launch Support System (ELSS) or a change to the Operational Surveillance Requirements as defined in paragraph 3.5.2.11 (Operational Surveillance Requirements) and its subparagraphs as soon as possible but NLT 14 CDs prior to testing operations or launch. The Contractor shall obtain USG approval for final design of changes to the launch system interface with ELSS or a change to the Operational Surveillance Requirements prior to implementation NLT 7 CDs prior to testing operations or launch. (IDE) LSS: Launch System Verification (component, unit, subsystem, system, launch site) The Contractor shall develop the Launch Vehicle Test and Verification Plan (LVTVP) NLT ATP+90 CDs (CDRL A037). The LVTVP shall include each phase of testing (e.g., hotfire, wet dress rehearsal, system level high pressure proof test, etc.), and the respective performance verification requirements during that critical test. The Contractor shall design the verification program, including test, inspection, and analysis activities, to demonstrate compliance to system level performance and environmental specifications, system interface requirements, and contractual compliance requirements. The Contractor shall design the verification program to ensure hardware and software qualification, and screening of workmanship defects prior to each launch. When the Contractor determines an exception is warranted, waivers to the plan shall be submitted for Government approval NLT 30 CDs prior to execution or 5 CDs following when the Contractor violated requirements through test execution. (IDE) LS: The Contractor shall update the LVTVP for each NSS mission (CDRL A037). The Contractor shall provide the baseline for items listed in paragraph 3.2.5 (Launch System Verification [component, unit, subsystem, system, launch site]) from the USG certified/approved launch vehicle configuration at L-6 months. From L-6 months until launch, the Contractor shall maintain the baseline and notify the USG Team of all changes to this electronic baseline along with the information requested in paragraph 3.2.5.