6 Dec 2019_Performance-Based_Work_Statement.docx

ATTACHMENT 1

SPACE AND MISSILE SYSTEMS CENTER/ LAUNCH ENTERPRISE (SMC/ECL)

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

PERFORMANCE WORK STATEMENT (PWS)

FA8811-20-R-0003

6 December 2019

Department of the Air Force Space and Missile Systems Center Launch Enterprise Los Angeles AFB, California 90245-2808

INTRODUCTION

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

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

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

a) Systems Engineering and Integration (SE&I)

b) Mission Integration Management

c) Systems Safety Engineering

d) Systems Environmental Engineering

e) Systems Security & Cybersecurity

f) Quality and Production

g) Manufacturing Engineering

h) Quality Engineering

i) Launch Schedule Management

j) Launch Risk Management

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

l) Data Management and Configuration Control Management

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

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

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

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

APPLICABLE DOCUMENTS

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

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

REQUIREMENTS

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

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

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

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

Staffing The Contractor shall fill the positions and meet all the qualifications, experience, and certifications (or equivalency) pursuant to Contract Attachment 8, Staffing Plan and Appendix E, Labor Category Requirements. The Government’s decision regarding equivalency of qualifications, experience, or certification will be final.

The government defines key personnel as subject matter expert positions in a managerial capacity essential to the work performed under this contract and contribute in a substantive and measurable way. Key personnel may also be empowered to make discretionary decisions in accordance with the company policies with respect to team building, team management, and work performance by the teams they are in charge of. For positions described as key personnel in government staffing estimate, the government estimates that the minimum qualifications, number of positions, experience, and certifications are essential for successful performance on this PWS requirement.

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

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

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

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

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

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

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

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

3.1.8 Small Business Utilization Report (CDRL A005)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Contractor shall staff all positions as identified in the Contract Attachment 8, Staffing Plan as follows: All Key personnel on day 1 after ATP; all positions identified as minimum staffing before day 15 after ATP; and, all positions identified in Contractor proposed staffing matrix on or before 30th day of ATP. Minimum staffing is identified in Attachment 8, Staffing Plan, of the contract.

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

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

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

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

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

The Contractor shall perform the following:

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

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

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

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

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

f) Attend, document, and track assigned action items in support of the following but not limited to the following: SMC/ECL Chief Engineer’s Control Board (ChECB), Mission Assurance Council (MAC), Launch Vehicle Mission Assurance Forum (MAF),Technical Review Board (TRB), and Configuration Control Board (CCB).

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

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

a) System Performance Requirements Document (SPRD)

b) Standard Interface Specification (SIS)

c) Systems Engineering Plan (SEP)

d) Risk Management Plan (RMP)

e) Mission Assurance Plan (MAP)

f) SMC/ECL Process Guide

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Contractor shall perform project management for New Entrant Certification. Products may include, but are not limited to, technical assessments of Certification Guides/Plans, Schedules, and other systems engineering products.

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

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

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

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

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

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

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

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

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

Continuous Innovation and Improvement

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

System Engineering Processes (CDRL A003) The Contractor shall perform system engineering processes and tasks, and shall deliver associated documentation, as directed by the Government The Contractor shall maintain a risk database and present the information in briefing chart format, as requested for risk management reviews.

The Contractor shall evaluate the NE risk management plans for conformance with Risk Standards per section 2.2 of this document and deliver reports to Government.

The Contractor shall manage NE mission data deliverables by maintaining Government database(s) and shall deliver a status report to the Government, as required.

The Contractor shall track certification data (and associated metrics) and deliver status documentation to the Government, as required.

The Contractor shall track Review Item Discrepancies (RIDs) and Requests for Information (RFIs) for major reviews and deliver status reports to the Government, as required.

The Contractor shall support the Government in preparing and coordinating Configuration Control Board (CCB) packages.

The Contractor shall maintain document trees, the Livelink database (pertaining to the NECT), certification action item trackers, and certification status trackers for Systems Engineering Processes and deliver a status reports to the Government, as required.

The Contractor shall generate, document, and deliver a lessons learned Database to the Government.

The Contractor shall transition to and then maintain Digital Engineering Architecture platforms.

Mission Integration Management The Contractor shall provide recommendations related to NSSL mission buy contract requirements and early integration studies for USG review. Products include, but are not limited to: draft Performance Work Statement, WBS Summary, Contract Data Requirements List (CDRLs), Incentive Plan, Proposal Instructions (proposal sections), and analyses of Basis of Estimates, as required.

The Contractor shall analyze technical, schedule and programmatic issues related to the Launch Program contracts (e.g. cost, schedule and performance) and provide recommendations to the USG as required to support program mission integration related taskers, on average 2 per month.

The Contractor shall analyze and identify mission management programmatic and technical issues associated with cost, schedule and performance, and provide assessments/recommendations to the USG. Products include recommendations for ICDs, technical assessments of mission unique efforts, de-confliction of mission schedules, etc.

The Contractor shall provide integrated products required to execute readiness reviews, rehearsals, launch campaigns, and day of launch activities as specified below. These activities may be repeated due to unforeseen launch delays.

The Contractor shall exercise anomaly processes and Day of Launch decision making processes during rehearsal campaigns. Evaluate success of rehearsal campaign with respect to pre-defined exit criteria, and brief results to the Mission Director for non-OSL missions. Evaluate, update and maintain the Day-of- Launch (DOL) decision process by ensuring that the SMC/ECL DOL decision process meets AF and AFSPC requirements.

The Contractor shall execute Rehearsal Anomaly Team (RAT), integrate with the LSP, SVC, and other mission stakeholders (to include the Eastern/Western Ranges, Aerospace Corporation, NOPS, Space Launch Squadrons and Operations Groups) to plan, develop and de-conflict activities, and evaluate goals and objectives for launch campaign rehearsals (i.e., Integrated Crew Exercises (ICEs) and Mission Dress Rehearsals (MDRs); and tabletop exercises, stand-alone exercises as required) as defined in the Baseline USG Evolved Expendable Launch Vehicle Rehearsal Plan. Products include but are not limited to profile letters, pre-departure briefings and overview briefings anomaly development, timeline and clock planning. The Team shall execute up to three ICEs, as coordinated with mission stakeholders, and one MDR per LE for each mission identified by SMC/ECL.

The Contractor shall define evaluation criteria, design and develop anomaly scenarios (e.g. design script inputs and provide inputs to members on console), and evaluate mission launch teams on operations execution performance. Products include timelines, anomaly scenarios, entry/exit briefings, initial conditions and rehearsal overview brief.

The Contractor shall report findings to the integrated launch team. The Contractor shall identify, evaluate and document rehearsal and day-of-launch Mission Integration lessons learned and provide them to the USG for continuous launch program improvement. The Contractor shall update the Generic Baseline USG Launch Rehearsal Plan as required.

The Contractor shall evaluate efficiencies of console operations and provide strategic planning recommendations for Mission Integration Management as needed.

The contactor shall evaluate mission integration activities for knowledge transfer to Government mission team members. Products and processes include updates to the Government Mission Integration Manager (GMIM) continuity/training book, GMIM Forums, on the job training, etc.

Systems Safety Engineering.

The Contractor shall collect, evaluate and document operational "Lessons Learned" from launch rehearsals and day of launch activities. The Contractor shall provide an out brief of lessons learned following each activity (e.g., hotwash, postflight review, etc.) and incorporate lessons learned into the next launch activity. Products include but are not limited to documented lessons learned and briefing materials (e.g. database, postflight review, etc.).

The Contractor shall conduct launch systems safety engineering for activities at LAAFB and report recommendations to SMC/ECL. The Contractor shall evaluate and update the System Safety documentation (e.g. System Safety Management Plan (SSMP) and Programmatic Environmental Safety and Health Evaluations (PESHE)) IAW National Security Space Acquisition Policy Interim Guidance for DoD Space System Acquisition Process, and AFI 91-202 AFSPCSUP1, and determine compliance with applicable DoD and AF requirements.

The Contractor shall evaluate LSP documentation and activities and report whether they are in technical compliance with applicable system safety requirements (e.g. EWR 127-1, AFSPCMAN 91-710, MIL-STD-882E, and AFI 91-202 AFSPCSUP1) and provide the USG with written documentation of discrepancies. Other products may include but are not limited to waiver packages, risk assessments, Space Debris Assessment Reports (SDARs), assessment of LVM products, etc.

The Contractor shall technically assess and report on open launch and range safety items, and provide the USG with written recommendations for disposition of the open items.

The Contractor shall provide systems safety assessments of payload integration, ground testing, and flight safety activities to ensure mission readiness.