SEI PWS 5 Oct 09.pdf

Launch and Range Systems Wing (LRSW)

Systems Engineering & Integration (SE&I) Contract

PPeerrffoorrmmaannccee--bbaasseedd WWoorrkk SSttaatteemmeenntt ((PPWWSS))

Contract FA8811-10-C-XXXX

Attachment 1

5 Oct 2009

Launch & Range Systems Wing Space & Missile Systems Center

483 North Aviation Boulevard Los Angeles AFB, California 90245-2808

Phone: (310) 653-3656

BLANK

i

Table of Contents

1.0 Description of Service

1.1 SE&I

1.2 LAAFB PWS

1.3 CCAFS PWS

1.4 VAFB PWS

2.0 Services Summary

2.1 General

2.2 Performance Evaluation

3.0 Government Furnished Property and Services

3.1 Facilities

3.2 Government-Furnished Services (VAFB and CCAFS)

3.3 Government-Furnished Property

3.4 Forms and Publications

4.0 General Information

4.1 Contractor Personnel

4.2 Installation and Controlled Area Access

4.3 Hours of Operation

4.4 Inspection of Files

4.5 Performance Evaluation Meetings

4.6 Quality Assurance

4.7 Scope Changes

4.8 Administrative Records

4.9 Safety

APPENDICES

Appendix A - Government Furnished Property/Services/Equipment Appendix B - Acronyms, Abbreviations and Definitions Appendix C - Applicable Publications and Forms

1.0 Description of Service

The System Engineering and Integration (SE&I) 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 services for the Launch and Range Systems Wing (LRSW) located at the Space and Missile Systems Center at Los Angeles Air Force Base, California (LAAFB) , Cape Canaveral Air Force Station, Florida (CCAFS); and Vandenberg Air Force Base, California (VAFB).

Services provided under this contract support LRSW’s space launch operations for current and future LRSW launch systems. Deliverables provided under this contract are in accordance with (IAW) Exhibit A, Contract Data Requirements Lists (CDRLs).

The services include the following function areas:

• Systems Engineering and Integration

• Mission Integration Management

• Systems Safety Engineering

• Systems Environmental Engineering

• Systems Security & Information Assurance

• Product Assurance

• Launch Schedule Management

• Launch Risk Management

CDRLs A001, A002, A003 (applies to 1.0 thru 1.4 and subparagraphs)

1.1 SE&I

The launch SE&I effort described in this PWS consists primarily of systems engineering and integration tasks in support of the Evolved Expendable Launch Vehicle (EELV) program. The SE&I also includes overarching integration of launch and range programs which will require interfacing both the EELV and any future LRSW launch systems with the Launch and Test Range System (LTRS). In addition, the launch SE&I effort provides for systems engineering and integration support to the launch bases. Some of the launch base activity is not related to EELV and is described separately within this PWS.

The EELV SE&I effort will be performed at LAAFB, VAFB, and CCAFS. The EELV effort will be funded by the EELV program in support of LRSW at LAAFB (Section 1.2), the 4th Space Launch Squadron (4 SLS) at VAFB (Section 1.3.1), the 5th Space Launch Squadron (5 SLS) and portions of the 45th LCG at CCAFS (Section 1.4.1).

The non-EELV effort will be performed at VAFB and CCAFS. This non-EELV effort will funded by the launch bases in support of the 30th Launch Group (30 LCG) at

VAFB (Section 1.3.2) and the 45th Launch Group (45 LCG) at CCAFS (Section 1.4.2).

1.2 LAAFB PWS

1.2.1 SE&I IN SUPPORT OF LRSW LAUNCH SERVICES

1.2.1.1 SYSTEMS ENGINEERING & INTEGRATION

The contractor is responsible for, but not limited, to the following:

1.2.1.1.1 SYSTEMS ENGINEERING

1.2.1.1.1.1 The contractor shall assess launch systems engineering documentation 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 LRSW compliance with approved systems engineering documents (identified below in sections 1.2.1.1.1.2, 1.2.1.1.1.3, and 1.2.1.1.1.4). The contractor shall provide a monthly report on the results of the review along with any required corrections.

1.2.1.1.1.2 The contractor shall generate draft revisions to the EELV System Performance Requirements Document (SPRD), EELV Standard Interface Specification (SIS), EELV Life Cycle Sustainment Plan (LCSP), Engineering Launch Support System (ELSS) System Requirements Document (SRD), and Derived Communications Requirements Document (DCRD);

incorporating agreed-upon changes and preparing the documents, IAW MIL-STD-961E, for Configuration Control Board (CCB) approval.

(CDRL A004 and A005)

1.2.1.1.1.3 The contractor shall update the LRSW Mission Assurance Plan (MAP) annually; submitting it to Launch & Range Systems Wing, Engineering Division (LRSW/EN).

1.2.1.1.1.4 The contractor shall develop and update various program management and life-cycle management documents, for example, the EELV Systems Engineering Plan (SEP) IAW Air Force Instruction (AFI) 63-1201 (Life Cycle Systems Engineering), the program Life Cycle Management Plan (LCMP) IAW AFI 63-101, and the program Life Cycle Sustainment Plan (LCSP) IAW AFI 63-101 and SMCI 20-101.,etc.

(CDRL A004 and A005)

1.2.1.1.1.5 The contractor shall develop any other required launch systems engineering documents identified by the contractor needed to provide the necessary and sufficient launch services support.

1.2.1.1.1.6 The contractor shall maintain the Launch Mission Director training and certification process. The contractor shall update and maintain training materials and ensure compliance with applicable guidance. The contractor shall provide training to newly assigned Mission Directors.

1.2.1.1.1.7 The contractor shall maintain the Day-of-Launch (DOL) decision process by ensuring that the LRSW DOL decision process meets AF and AFSPC requirements.

1.2.1.1.1.8 The contractor shall maintain the launch Lessons-Learned database, input new lessons learned, and schedule lessons-learned reviews with appropriate program personnel to provide timely inputs to pre-launch activities for the next launch.

1.2.1.1.1.9 The contractor shall collaborate with NASA and the National Reconnaissance Office to include the quarterly Launch Collaboration Steering Group, the annual Launch Mission Assurance Forum and the Space Launch Integration Forum.

1.2.1.1.1.10 The contractor shall review draft systems engineering guidance (AFIs, AFSPC Instructions (AFSPCIs), etc.), annually assess impact on LRSW and EELV, and provide recommended changes.

1.2.1.1.2 INTEGRATION

1.2.1.1.2.1 The contractor shall perform overarching systems integration support for launch verification integration with range systems across all existing and new acquisition programs falling under SMC/LRSW. This activity will include integration between launch and range systems acquisition.

1.2.1.1.2.2 The contractor shall perform concept trades between launch vehicle and range, e.g., west coast GPS launches, autonomous flight termination, space-based telemetry. There will be approximately two studies a year.

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

1.2.1.1.2.4 The contractor shall prepare acquisition strategy documents and supporting documentation.

1.2.1.1.3 ENGINEERING LAUNCH SUPPORT SYSTEM (ELSS)

1.2.1.1.3.1 The contractor shall analyze ELSS user-requested changes and recommend implementation options to LRSW. 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 Vehicle (LV) Launch Support Center (LSC) and High Speed Network (HSN) interface) requirements.

1.2.1.1.3.2 The contractor shall revise the ELSS Concept of Operations (ConOps) to reflect requirements changes. The contractor shall perform ELSS systems integration and activation for ELSS system revisions to support LRSW launch vehicle systems operations. (ELSS excludes National

Reconnaissance Office (NRO) Operations Squadron (NOPS) and Spacelift Telemetry Acquisition and Reporting System (STARS)).

1.2.1.1.3.3 The contractor shall analyze NOPS, ULA, and STARS proposed changes to ELSS interfaces as specified in the DCRD. The contractor shall provide written recommendation to LRSW on optimum implementation of proposed changes to ELSS interfaces. The contractor shall verify revised ELSS interface requirements implementation compliance by supporting end-to-end launch vehicle systems and ELSS operations testing.

1.2.1.1.3.4 The contractor shall develop and document a recapitalization plan for ELSS/LV_LSC and EELV acquired equipment. The contractor shall address supportability and sustainment planning.

1.2.1.1.3.5 The contractor shall perform Requirements Definition and Functional Analysis as required operational capability is identified and determined.

1.2.1.1.4 RD-180 ENGINEERING

1.2.1.1.4.1 The contractor shall provide hydrocarbon rocket engine engineering expertise to support the launch vehicle contractor technical team and the LRSW program team for Atlas V RD-180 engine production, operations, and post-flight data review.

1.2.1.1.4.2 The contractor shall acquire cognizance of the foreign manufacturing process and prepare analyses and reports on their differences from U.S. process.

1.2.1.1.4.3 The contractor shall coordinate with LRSW launch system developing program offices and launch service contractors to obtain, maintain and report current programs information status to LRSW.

1.2.1.1.4.4 The contractor shall serve as the LRSW focal point for Former Soviet Union (FSU) policy requirements, technical assistance agreements, and State Department requirements.

1.2.1.1.5 PROJECT ENGINEERING

1.2.1.1.5.1 The contractor shall perform and analyze engineering and technical management information in order for LRSW to manage/oversee the contracted design, development, manufacturing, launch, sustainment, and modification of Atlas V and Delta IV launch vehicle subsystems. The contractor shall provide expertise for each of the Atlas V and Delta IV subsystem, e.g., separation systems, booster propulsion, upperstage propulsion, solids, ordnance, avionics, structures, GSE, fairings, and launch facilities.

1.2.1.1.5.2 The contractor shall coordinate engineering and technical program management activities between government, launch vehicle contractor, Aerospace Corporation, and LRSW support contractors to ensure launch readiness and provide an integrated assessment to the government program manager.

1.2.1.1.5.3 The contractor shall acquire and maintain cognizance of subsystem and component-level risks and issues, both fleet-wide and for upcoming launches. The contractor shall track the status of the Prime Launch Vehicle Contractor's subsystem and component-level risk mitigation activities and report on the status of mitigation activities to the government.

1.2.1.1.5.4 The contractor shall provide oversight of government-funded launch vehicle risk mitigation efforts to ensure that cost, schedule, and performance goals are met, and shall ensure that funding and contracts are in place to execute the projects.

1.2.1.1.5.5 The contractor shall evaluate the Prime Launch Vehicle Contractor's methods, processes, and techniques and recommend improvements to subsystem/component design, performance, reliability/ maintainability and supportability.

1.2.1.1.5.6 The contractor shall analyze Air Force requirements to determine whether existing EELV program-related infrastructure (e.g., LVC, government and commercial) is capable of meeting launch needs. The contractor shall recommend changes to the existing launch systems that could take advantage of identified and existing Government or Commercial infrastructures and meet Government launch requirements.

1.2.1.1.5.7 The contractor shall analyze launch infrastructure for supportability issues to include parts obsolescence, corrosion control, facility refresh/refurbishment and other support issues IAW Mil-Prf-49506.

1.2.1.1.5.8 The contractor shall provide weekly written reports to the Atlas and Delta Group on their LRSW SE&I project engineering activity.

1.2.1.2 MISSION INTEGRATION MANAGEMENT

The contractor is responsible for, but not limited to, the following:

1.2.1.2.1 The contractor shall perform planning and development of launch program and mission contract requirements (e.g. statements of work).

1.2.1.2.2 The contractor shall analyze programmatic issues related to the contract (e.g. cost, schedule and performance) and provide written reports documenting the analyses. The contractor shall conduct weekly launch vehicle contract status reviews with the United Launch Alliance (ULA) for LRSW. The contractor shall coordinate and track launch program funded/unfunded requirements list and obligation plan. The contractor shall provide written status reports to the Government at conclusion of weekly status meeting.

1.2.1.2.3 The contractor shall identify mission management programmatic issues associated with cost, schedule and performance. The contractor shall survey Government, Aerospace and Launch Vehicle Contractor (LVC) information to identify possible alternative recommendations.

1.2.1.2.4 The contractor shall ensure sufficient level of support is available prior to a LRSW supported launch. While the number of launches is subject to change year to year, on average LRSW conducts six ER and two WR launches per year. Additionally, on average, this increased level of support may have to be repeated for at least two launch periods per year due to unknown pre-launch delays.

1.2.1.2.4.1 The contractor shall assemble program data (e.g. schedule and performance) and provide mission programmatic planning and development of readiness reviews to ensure a consistent Flight Readiness Review (FRR) process across LRSW. (e.g. Mission Readiness Review, Flight Readiness Review, Executive Mission Readiness, Launch Readiness Review, and Post-Flight Review).

1.2.1.2.4.2 The Rehearsal Anomaly Team (RAT) is composed of technical representatives from the LV and Space Vehicle (SV) program offices, LVCs and Space Vehicle Contractors (SVCs), NRO, and the launch site Wings.

The RAT plans, develops, and evaluates goals and objectives for mission campaign exercises and rehearsals. As a member of the RAT, the contractor shall work with the LVC, SVC, and other mission stakeholders to plan, develop and de-conflict activities, evaluate goals and objectives for launch campaign rehearsals (e.g. tabletop exercises, stand-alone, and integrated crew exercises and rehearsals) in satisfaction of Government requirements.

1.2.1.2.4.3 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, with written evaluations provided to the Government within one week of every exercise.

1.2.1.2.4.4 The contractor shall report findings to the integrated launch team.

The contractor shall identify and document lessons learned and provide them to the Government for continuous launch program improvement, and update the Government Rehearsal Plan as required by the Government.

1.2.1.2.5 The contactor shall provide continuity of mission management activities and knowledge transfer to Government mission team members.

1.2.1.3 SYSTEMS SAFETY ENGINEERING

The contractor is responsible for, but not limited to, the following:

1.2.1.3.1 The contractor shall provide launch systems safety engineering for activities at LAAFB. The contractor shall maintain 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, to ensure compliance with applicable Department of Defense (DoD) and AF requirements.

1.2.1.3.2 The contractor shall review and verify that LVC documentation and activities are in compliance with applicable system safety requirements (e.g.

EWR 127-1, AFSPCMAN 91-710, MIL-STD-882C, and AFI 91-202 AFSPCSUP1) and provide the Government with written documentation of discrepancies.

1.2.1.3.3 The contractor shall identify and track open launch and range safety items, and provide the Government with written recommendations for disposition of the open items.

1.2.1.3.4 The contractor shall provide systems safety assessments of payload integration, ground testing, and flight safety activities to ensure mission readiness. The contractor shall report noted deficiencies to the Government within 1 work day of the assessments.

1.2.1.3.5 The contractor shall analyze the design and testing of launch vehicle flight termination systems and other critical safety components to provide the Government with written recommendations for risk mitigation.

1.2.1.3.6 The contractor shall assess the LVC’s hazard analyses to verify all hazards are properly identified and mitigated; findings shall be reported in written form to the Government.

1.2.1.3.7 The contractor shall evaluate mission-unique EWR 127-1 or AFSPCMAN 91-710 requirements and provide the Government with written documentation of discrepancies and potential cost impacts.

1.2.1.3.8 The contractor shall provide system safety engineering analysis for the deactivation and disposition of LRSW launch systems. This will include providing system safety and environmental safety analysis reports related to disposition alternatives and closeout activities.

1.2.1.3.9 The contractor shall activate the LRSW Mishap Control Center (MCC) for each launch and facilitate communication between LRSW and the Mission Director, in case of a mishap. MCC activities will be conducted IAW LRSW Operating Instruction (OI) 91-201.

1.2.1.3.10 The contractor shall develop and maintain mishap investigation policies and processes.

1.2.1.3.11 The contractor shall participate as required in internal mishap investigations including system safety and environmental safety analyses related to disposition alternatives and closeout activities.

1.2.1.4 SYSTEMS ENVIRONMENTAL ENGINEERING

The contractor is responsible for, but not limited to, the following:

1.2.1.4.1 The contractor shall evaluate the LVC’s designs, operations, and procedures for launch vehicles, and ground support systems to verify compliance with all environmental requirements.

1.2.1.4.1.1 The contractor shall evaluate the LVC’s environmental compliance through all programmatic phases, from concept development through program closeout and disposal.

1.2.1.4.1.2 The contractor shall provide written strategies needed to achieve and maintain compliance with federal, state, and local environmental laws, regulations, requirements, and standards.

1.2.1.4.1.3 The contractor shall review launch Engineering Change Proposals (ECPs), and provide written mitigation options to decrease or limit potential environmental liabilities and costs.

1.2.1.4.2 The contractor shall survey LVC pollution prevention progress to ascertain compliance with the provisions of applicable federal, state, and local laws, regulations, requirements, and standards; providing written documentation of compliance status.

1.2.1.4.3 The contractor shall construct Requests for Environmental Impact Analysis (AF Form 813) to initiate the National Environmental Policy Act (NEPA) process for launch activities.

1.2.1.4.4 The contractor shall review launch operations NEPA documentation to verify that the documentation complies with all applicable requirements.

1.2.1.4.5 The contractor shall perform research and analyses of environmental impacts associated with launch operations IAW EELV Environmental Mitigation Plans (EMP). This includes special studies required by local and federal Governments.

1.2.1.4.6 The contractor shall assess proposed federal, state and local environmental requirements, regulations, laws, and standards to determine potential impacts to launch operations; providing written documentation of impact analyses.

1.2.1.4.7 The contractor shall attend program reviews, working groups, Technical Interchange Meetings (TIMs), and Technical Exchange Meetings TEMs) to ensure compliance with federal, state, local environmental laws, regulations, requirements, and standards. The contractor shall report compliance status, in writing.

1.2.1.4.8 The contractor shall maintain and update the PESHE and EMP.

1.2.1.5 SYSTEMS SECURITY & INFORMATION ASSURANCE

The contractor is responsible for, but not limited to, the following:

1.2.1.5.1 SYSTEMS SECURITY

1.2.1.5.1.1 The contractor shall update and maintain the EELV Program

Protection Plan (PPP) as needed, IAW DoDI 5200.39, DoDI 5200.1-M, AFPD 63-17, and NATIONAL SECURITY SPACE (NSS) ACQUISITION

POLICY INTERIM GUIDANCE FOR DOD SPACE SYSTEM ACQUISITION

PROCESS.

1.2.1.5.1.2 The contractor shall develop and maintain the EELV Counterintelligence Support Plan (CSP) and the Operations Security Plan (OSP). The contractor shall also review and update the SE products on an annual basis, provide written summaries to changes and incorporate changes into the PPP.

1.2.1.5.1.3 The contractor shall review and update the EELV Security Classification Guide (SCG) annually IAW AFI 31-401 and consolidate changes into the PPP.

1.2.1.5.1.4 The contractor shall evaluate acquisition documents (average of 2 per month) for compliance with Critical Program Information (CPI) and Critical System Resources (CSR) protection requirements IAW the PPP and provide a detailed written assessment of EELV impacts.

1.2.1.5.1.5 The contractor shall conduct annual EELV Program Protection Surveys (PPS) to evaluate the design, implementation and verification of ULA system security provisions IAW the ULA Program Protection Implementation Plan (PPIP), SCG and the PPP. A detailed written assessment of findings shall be provided to the Government with recommendations for correction actions.

1.2.1.5.1.6 The contractor shall evaluate EELV change proposals (average 2-5 per week), e.g. Engineering Change Proposals (ECPs), Task Change Proposals (TCPs), Configuration Change Proposals (CCPs), waivers and deviations, and provide security assessments IAW the applicable system contract, acquisition plan, SCG and the PPP. Evaluations shall address cost, schedule, performance and interface impacts/risks, and meet change board documentation requirements and suspense dates.

1.2.1.5.1.7 The contractor shall evaluate internal, public, classified and unclassified requests for information and requests for information received from foreign governments (average of 25 per month) IAW the EELV SCG and PPP. Initial feedback will be provided within two business days with a final written assessment provided.

1.2.1.5.1.8 The contractor shall administer the Quarterly EELV System Security Working Group (SSWG) meetings by scheduling meetings, preparing and distributing agendas, distributing review documentation, collecting and summarizing inputs on proposed actions, reviewing actions, recording and publishing the SSWG minutes, IAW the SSWG Charter, and

AFPAM 1701.

1.2.1.5.2 The contractor shall develop and maintain the LRSW security library on Livelink/Sharepoint IAW the LRSW file plan, AFMAN 37-104, AFMAN 37- 123, and AFI 37-138.

1.2.1.5.3 The contractor shall review, update and distribute the LRSW Security Operating Instruction (SOI) annually.

1.2.1.5.4 The contractor shall manage systems security and information assurance self inspections and provide documentation for AF-level Inspections, to include the Air Force Inspector General, Higher Quarters Air Force Space Command Inspector General Inspection, Air Force Audit Agency Inspections, Space and Missile Systems Center Integrated Program Reviews annually

1.2.1.5.5 MISSION SYSTEMS CERTIFICATION AND ACCREDITATION (C&A)

1.2.1.5.5.1 The contractor shall perform all mission systems certification and accreditation activities for launch programs and serve as policy review representative for LTRS C&A products in support of the LRSW Information Assurance Manager (IAM).

1.2.1.5.5.2 The contractor shall review and process Mission Information Systems Certification and Accreditation packages for launch systems IAW the DoD Information Assurance Certification & Accreditation Process (DIACAP), and DoDI 8510.01.

1.2.1.5.5.3 The contractor shall prepare a weekly report describing the status of each C&A package in process. Items to be addressed include delivery of associated documentation and artifacts, status of missing items, completed and/or pending reviews, and status of remaining actions.

1.2.1.5.5.4 The contractor shall register Launch Systems in the Enterprise Information Technology Data Repository (EITDR) in compliance with the Federal Information Security Management Act (FISMA) and conduct monthly status reviews to validate currency and accuracy.

1.2.1.5.5.5 The contractor shall review evolving information assurance and space systems certification policies, programs, procedures and reports for initial and follow-on system releases, including new and evolving Information Assurance (IA) system requirements. The contractor shall provide a written report of impact analysis with recommendations for changes/revisions.

1.2.1.5.5.6 The contractor shall administer weekly IA telecons by scheduling meetings, preparing and distributing agendas, distributing review documentation, collecting and summarizing inputs on proposed actions, reviewing actions, recording and publishing minutes.

1.2.1.5.5.7 The contractor shall update the EITDR and the enterprise Mission Assurance Support Service (e-MASS) for launch systems, IAW DoDI 8510.01.

1.2.1.6 PRODUCT ASSURANCE

The contractor is responsible for, but not limited to, the following:

1.2.1.6.1 The contractor shall plan and administer pedigree reviews IAW pedigree guidance documentation (e.g., EELV Atlas V Pedigree Review Guidelines, Delta Hardware Pedigree Handbook, internal documentation). The contractor shall have a working knowledge of flight hardware associated with the EELV and heritage family of launch vehicles (e.g. structural, mechanical, propulsion, guidance and control systems, ordnance, pressurization, and feed line components). The contractor shall identify and document hardware pedigree issues IAW internal pedigree guidance.

1.2.1.6.2 The contractor shall provide reviews, as assigned, of manufacturing, production, and quality processes as a member of the pedigree team. The contractor shall evaluate hardware production operations and quality history for conformance with ISO 9001:2000.

1.2.1.6.3 The contractor shall examine LV production operations to include identification of key process parameters, associated monitoring metrics, variability, determination of “statistical control”, capability and capacity (e.g.

fusion and friction stir welding, metal forming, electronics assembly, printed wiring board production, wire harness assembly, X-Ray inspection and other nondestructive inspection techniques, electrical testing, final assembly, and transportation methods). The contractor shall document conditions adverse to quality hardware production. The contractor shall provide documentation (e.g.

written reports, email documentation, or presentation).

1.2.1.6.4 The contractor shall investigate production issues and quality escapes, anomalies, and failures. The contractor shall provide production, quality and statistical analyses of LVC root-cause determination and verify corrective action implementation and objectively monitor process health.

1.2.1.6.5 The contractor shall provide technical readiness assessments to the Government. The contractor shall provide documentation (e.g. written reports, e-mail documentation, or presentation).

1.2.1.6.6 Contractor Quality Engineers (QEs) shall work with prime contractors and suppliers in reviewing production and quality systems. Contractor QEs will assess effectiveness of these systems and, when tasked, participate in implementation of modern quality methods such as statistical process control, sampling methods, statistical analysis, and design of experiments (DOE).

1.2.1.6.7 The contractor shall assess and develop metrics to examine prime contractor and supplier production and quality performance, such as cost of quality, first time quality, and metrics associated with reject and rework rates and escapes. The contractor shall possess the expertise to perform statistical analysis to identify focus areas adverse to quality or manufacturing operations.

1.2.1.6.8 The contractor shall assess production related issues to determine impacts to the overall mission assurance, and recommend mitigation methods.

1.2.1.6.9 The contractor shall review, coordinate and distribute Government Industry Data Exchange Program (GIDEP) information. The contractor shall review, participate in and coordinate Parts Material and Process Control Board (PMPCB) meetings and actions.

1.2.1.6.10 The contractor shall assess LVC product assurance projects and recommend methods to enhance effectiveness and efficiencies of such projects as: non-conformance reduction; lean manufacturing initiatives, foreign & domestic object damage and quality escape elimination.

1.2.1.6.11 The contractor shall attend audits, Program Management Reviews (PMRs), Corrective Action Boards (CABs) and provide written assessment.

1.2.1.7 LAUNCH SCHEDULE MANAGEMENT

The contractor is responsible for, but not limited to, the following:

1.2.1.7.1 The contractor shall analyze the launch activity scheduling process and provide an integrated approach for the development of an integrated LRSW Wing Master Schedule (WMS). The contractor shall ensure the WMS tool is compatible with the LVC-provided schedules.

1.2.1.7.2 The contractor shall develop and maintain an integrated WMS, which includes launch-impacting activities of Launch Group (LCG), LVC, ELSS/LV_LSC, SMC reviews, and Range Group acquisition and sustainment.

The contractor shall analyze the WMS and provide the Government with options to mitigate conflicts and milestone slippages.

1.2.1.7.3 The contractor shall update the Space Launch Manifest (SLM) resident on the Launch Information Support Network (LISN), or equivalent (includes LRSW and Office of Space Launch (OSL) missions). The contractor shall evaluate the SLM, identifying potential scheduling conflicts (launch dates, facilities, rehearsals, etc) and provide an assessment to LRSW on available options. The contractor shall assemble an LRSW Launch Manifest using the LISN. The contractor shall post the manifest on LRSW’s Integrated Data Environment (IDE) and distribute via email to government-provided distribution list.

1.2.1.7.4 The contractor shall develop and maintain the LRSW Launch Manifest Operating Instruction (LMOI).

1.2.1.8 LAUNCH RISK MANAGEMENT

The contractor is responsible for, but not limited to, the following:

1.2.1.8.1 The contractor shall evaluate current EELV risk management processes for compliance with the standards set in the Risk Management Guide for DoD Acquisition. The contractor shall bring deficiencies, and recommended changes, to LRSW Chief Engineer’s attention. The contractor shall document the EELV risk management process, update the EELV Risk Management Plan, and submit the plan for Government approval. The contractor shall review the EELV Risk Management Plan annually, and provide LRSW with recommended changes. TOR-2005(8583)-4018, TOR-2005(8583)-4019, and ANSI/PMI 99-001-2004 will be used as references.

1.2.1.8.2 The contractor shall develop a weekly consolidated Atlas, Delta, and LTRS risk status report for the LRSW Chief Engineer. The contractor shall conduct a monthly LRSW Risk Management Board (RMB), chaired by the Wing Commander or Chief Engineer. The contractor shall present the status of all current and potential risks and recommended mitigation approaches at the RMB. The contractor shall provide status on risks identified for tracking by the Chief Engineer.

1.3 CCAFS PWS

1.3.1 SE&I IN SUPPORT OF LRSW LAUNCH SERVICES

The contractor is responsible for, but not limited to, the following:

1.3.1.1 SYSTEMS ENGINEERING AND INTEGRATION

1.3.1.1.1 LAUNCH SYSTEMS ENGINEERING & INTEGRATION

1.3.1.1.1.1 The contractor shall actively monitor the launch flow process and synthesize lessons learned. The contractor shall input all identified lessons learned into the 45 LCG or 5 SLS Launch Verification Database (LVDB).

The contractor shall determine appropriate times to conduct lessons learned reviews.

1.3.1.1.1.2 The contractor shall provide launch site activity mission assurance related recommendations to the 45th Launch Group Commander (45 LCG/CC), 45th Launch Group Technical Director (45 LCG/TD), and the 5 Space Launch Squadron Commander (5 SLS/CC) on EELV launch site activities.

1.3.1.1.1.3 The contractor shall author, coordinate and maintain and update launch-site mission-assurance documents such as the 45 Launch Group (45 LCG) strategic plan, 45 LCG operating instructions, and 45 LCG ConOps.

The contractor shall review Launch and Range related AF guidance documents for technical validity and make recommendations for revisions.

1.3.1.1.1.4 The contractor shall maintain and update the 45 LCG technical risk management program documentation. The contractor shall identify risks and recommend mitigation approaches.

1.3.1.1.1.5 The contractor shall provide technical and operational integration expertise and inputs to technical reviews, working groups and mission assurance reviews.

1.3.1.1.1.6 The contractor shall act as the primary point of contact for the LVDB and manage its use as the primary tool for 45 LCG technical risk assessment.

1.3.1.1.1.6.1 The contractor shall develop, maintain and update LVDB coursework and conduct LVDB training to military and Government personnel.

1.3.1.1.1.6.2 Track status of and manage status of launch site Launch Verification Matrix (LVM) loading into LVDB;

1.3.1.1.1.6.3 Periodically assess user inputs into LVDB and make recommendations to the 45 LCG/TD on improving quality and consistency;

and collect 5 SLS inputs for database enhancements and coordinate with LVDB developers

1.3.1.1.1.7 The contractor shall provide system integration for launch-flow processing, including range and range systems for heritage and EELV programs. The contractor shall comply with and complete required tasks identified in the Master Mission Checklist (MMC) for each mission.

1.3.1.1.1.8 The contractor shall be an active contributor in all Operational Status Review Meetings, and shall brief the MMC during weekly launch campaign meetings.

1.3.1.1.1.9 The contractor shall provide technical/management/process inputs/recommendations during but not limited to launch campaign planning meetings, mission working groups, readiness reviews and 5 SLS technical forums. The contractor shall be accountable for identifying issues/risks to the Atlas/Delta Launch Mission Manager (LMM) and make resolution recommendations. The contractor shall be accountable for providing a written summation of meeting as requested by the LMM.

1.3.1.1.1.10 The contractor shall monitor, assess, and provide oral and written status of LVC processing activities and problem resolution to the Atlas/Delta LMM, and Atlas/Delta Flight leadership. The contractor shall provide summary processing schedules and information for 5 SLS status products on a weekly or as-required basis.

1.3.1.1.1.11 The contractor shall maintain cognizance of payload integration requirements, assessing the ability of the LVC and Range to meet payload requirements, and identify risk/issues to the Atlas/Delta LMM and 5 SLS leadership. The contractor shall manage the information flow to NRO and AF SV mission managers.

1.3.1.1.1.12 The contractor shall provide technical support for on-console Atlas/Delta launch/processing operations, rehearsals, and East Coast shadow operations.

1.3.1.1.1.12.1 Maintain and modify script, timelines, and technical reference products for the Government technical team;

1.3.1.1.1.12.2 Be an active member in the RAT process including but not limited to developing and executing anomaly scenarios, scheduling necessary exercise resources, and supporting the lessons-learned process; and

1.3.1.1.1.12.3 Assess 5 SLS on-console processes and products for consistency with the 5 SLS and advise Flight and 5 SLS leadership where deviations exist.

1.3.1.1.1.12.4 The contractor shall review draft 5 SLS operating instructions including but not limited to ConOps, mission assurance products and checklists for technical validity and recommend revisions.

The contractor shall execute Government-recommended changes as required.

1.3.1.1.1.12.5 The contractor shall maintain continuity of mission management across 5 SLS mission by maintaining an archive of launch campaign products and be accountable for training Government mission team members on the mission management process.

1.3.1.1.1.12.6 The contractor shall support accelerated Atlas V launch operations strategy in support of, but not limited to six launches per year.

1.3.1.1.1.13 LAUNCH VEHICLE LAUNCH SUPPORT CENTER (LV_LSC)

1.3.1.1.1.13.1 The contractor shall perform LV_LSC integration in support of launch vehicle systems operations and the ELSS. The contractor shall plan for extended support of requirements during the last 48 hours of launch campaigns, anticipate, but not limited to an average of six launches per year. Tasks include but are not limited to the following:

1.3.1.1.1.13.2 The contractor shall maintain configuration management of current LV_LSC architecture and manage processes IAW source requirements documents to include: SRD, ConOps and DCRD.

1.3.1.1.1.13.3 The contractor shall develop and maintain an integrated schedule of the LV_LSC events and provide de-confliction recommendations of EELV processing and launch rehearsals to LMM and execute approved schedule.

1.3.1.1.1.13.4 The contractor shall update maintenance plans for all equipment in the LV_LSC as well as EELV-acquired equipment and monitor compliance with these plans.

1.3.1.1.1.13.5 The contractor shall act as the technical point-of-contact for mission communications kick-off meetings. The contractor shall analyze requirements and configure LV_LSC for each launch campaign.

1.3.1.1.1.14 LAUNCH SITE APPLICATION SOFTWARE SUSTAINMENT

1.3.1.1.1.14.1 The contractor shall provide system-level management of mission assurance and launch verification software to include oversight of structure and use, training development, and system maintenance and upgrades. The contractor shall maintain and manage mission assurance data in the 45 LCG databases (e.g. the LVDB, Critical Data Management Applications (CDMAs), Change Problem Request (CPR) databases, Stargate, and launch checklists).

1.3.1.1.1.14.2 The contractor shall maintain and sustain all software documentation (e.g. commenting in the code, user’s manuals, training guides, explanation of the software coding, and audit/change logs) and make these documents available for Government use.

1.3.1.1.1.14.3 The contractor shall provide end-user clarification for proper use of software and program features and functionality changes.

1.3.1.1.1.14.4 The contractor shall host and maintain a fully integrated data environment for mission assurance and launch verification software applications on a government-provided server. The server shall be accessible to all authorized users, to include remote users. The contractor shall verify configuration requirements of all computers supporting the above-listed mission assurance and launch verification software.

1.3.1.1.1.14.5 The contractor shall perform Structured Query Language (SQL) server database administration, database programming, backup, disaster recovery and security to prepare for launch operations, satellite and booster processing, and contingency/anomaly resolution.

1.3.1.1.1.14.6 The contractor shall provide system-level management of mission assurance and launch verification software to include oversight of:

structure and use, training development, and system maintenance and upgrades.

1.3.1.2 MISSION INTEGRATION MANAGEMENT

The contractor is responsible for, but not limited to, the following:

1.3.1.2.1 The contactor shall provide continuity of mission management activities and knowledge transfer to Government mission team members.

1.3.1.2.2 The contractor will manage squadron Flight Mission Lead (FML) in coordination and integration of launch site activities with LVC, LRSW and SV personnel.

1.3.1.3 SYSTEMS SAFETY ENGINEERING

The contractor is responsible for, but not limited to, the following:

1.3.1.3.1 The contractor shall provide systems safety engineering for activities at CCAFS. The contractor shall review the System Safety documentation (e.g.

SSMP and PESHE) IAW NSS 03-01, and AFI 91-202 AFSPCSUP1, to ensure compliance with applicable DoD and Air Force requirements.

1.3.1.3.2 The contractor shall review and verify LVC documentation and activities are in compliance with applicable system safety requirements (e.g.

EWR 127-1, AFSPCMAN 91-710, MIL-STD-882C, and AFI 91-202 AFSPCSUP1) and provide the Government with written documentation of discrepancies.

1.3.1.3.3 The contractor shall identify and track open launch and range safety items, and provide the Government with written recommendations for disposition of the open items.

1.3.1.3.4 The contractor shall provide systems safety assessments of payload integration, ground testing, and flight safety activities to ensure mission readiness. The contractor shall report noted deficiencies to the Government within twenty-four hours of the assessments.

1.3.1.3.5 The contractor shall analyze the design and testing of launch vehicle flight termination systems and other critical safety components to provide the Government with written recommendations for risk mitigation.

1.3.1.3.6 The contractor shall assess the LVC’s hazard analyses to verify all hazards are properly identified and mitigated; findings shall be reported in written form to the Government.

1.3.1.3.7 The contractor shall evaluate mission-unique EWR 127-1and AFSPCMAN91-710 requirements and provide the Government with written documentation of discrepancies and potential cost impacts.

1.3.1.3.8 The contractor shall provide system safety engineering analysis for the deactivation and disposition of LRSW systems. This will include providing system safety and environmental safety analysis reports related to disposition alternatives and closeout activities.

1.3.1.4 SYSTEMS ENVIRONMENTAL ENGINEERING

The contractor is responsible for, but not limited to, the following:

1.3.1.4.1 The contractor shall evaluate the LVC’s designs, operations, and procedures for launch vehicles, and ground support systems to verify compliance with all environmental requirements.

1.3.1.4.1.1 The contractor shall evaluate the LVC’s environmental compliance through all programmatic phases, from concept development through program closeout and disposal.

1.3.1.4.1.2 The contractor shall provide written strategies needed to achieve and maintain compliance with federal, state, and local environmental laws, regulations, requirements, and standards.

1.3.1.4.1.3 The contractor shall review launch ECPs, and provide written mitigation options to decrease or limit potential environmental liabilities and costs.

1.3.1.4.2 The contractor shall survey LVC environmental compliance and pollution prevention progress to ascertain compliance with the provisions of applicable federal, state, and local laws, regulations, requirements, and standards; providing written documentation of compliance status.

1.3.1.4.3 The contractor shall construct Requests for Environmental Impact Analysis (AF Form 813) to initiate the NEPA process for launch activities.

1.3.1.4.4 The contractor shall review launch operations NEPA documentation to verify that the documentation complies with all applicable requirements.

1.3.1.4.5 The contractor shall perform research and analysis of environmental impacts associated with launch operations IAW EELV EMP. This includes special studies required by local and federal governments.

1.3.1.4.6 The contractor shall assess proposed federal, state and local environmental requirements, regulations, laws, and standards to determine potential impacts to launch operations; providing written documentation of impact analyses.

1.3.1.4.7 The contractor shall attend program reviews, working groups, TIMs, audits (e.g. Environmental Safety and Occupational Health Compliance Assessment and Management Program (ESOHCAMP)), evaluations, and assessments to ensure compliance with federal, state, local environmental laws, regulations, requirements, and standards. The contractor shall report on compliance status, in writing.

1.3.1.4.8 The contractor shall review and provide updates to the PESHE and

EMP.

1.3.1.4.9 Participate in ESOHCAMP compliance process as follows:

1.3.1.4.9.1 Prepare for ESOHCAMP audits by attending TIMs and assessing compliance with applicable laws, regulations, and standards

1.3.1.4.9.2 Participate in ESOHCAMP audit as required

1.3.1.4.9.3 Review the audit report and develop a mitigation plan for resolution of environmental impacts and issues

1.3.1.4.9.4 Validate that government-approved mitigation plan is implemented and completed.

1.3.1.4.10 The contractor shall monitor all activities for Hazardous Material (HAZMAT) management, environmental and bioenvironmental compliance and pollution prevention to ensure compliance with applicable laws, standards, regulations, and codes.

1.3.1.5 SYSTEMS SECURITY & INFORMATION ASSURANCE

The contractor is responsible for, but not limited to, the following:

1.3.1.5.1 The contractor shall manage, and implement system security, program protection planning and information assurance policies, products, and procedures IAW NSS Acquisition Policy 03-01, DoDD 5000.1, DoDD 5200.1, DoDI 5200.39, DoDD 5200.1-M, AFI 63-17, AFPAM 63-1701, and SMC Air Force Program Executive Officer for Space (AFPEO/SP) Policy 63-17.

1.3.1.5.2 The contractor shall safeguard critical program data (e.g. classified and unclassified controlled information) IAW AFI 31-401. The contractor shall document and provide a written report of results and any subsequent actions, and participate in periodic Integrated Program Reviews (IPR’s).

1.3.1.5.3 The contractor shall update and maintain currency of the EITDR database as required to ensure mandatory compliance with FISMA reporting.

1.3.1.5.4 The contractor shall assess LVC security practices for compliance with security requirements and EELV security ConOps. The contractor shall support system security working groups and ensure strong lines of communication are maintained between LVC and 45 SW security organizations. The contractor shall inform 45 LCG leadership of any issues/concerns and recommend solutions.

1.3.1.5.5 The contractor shall support the development and processing of Entry Access Lists (EALs) and/or badging for visiting Government personnel to EELV restricted access facilities.

1.3.1.6 PRODUCT ASSURANCE (N/A)

1.3.1.7 LAUNCH SCHEDULE MANAGEMENT

The contractor is responsible for, but not limited to, the following:

1.3.1.7.1 The contractor shall develop and maintain an integrated Launch Group (LCG) Master Schedule that includes key 45 LCG activities and existing schedules (e.g. individual mission schedules (LVC provided)). The contractor shall analyze the 45 LCG Master Schedule and provide the Government with options to mitigate conflicts and milestone slippages. The contractor shall, at a minimum, provide a scheduled assessment of LV and SV readiness, technical schedule risks and mitigation recommendations. The contractor shall provide written status to Launch and Spacecraft Mission Managers.

1.3.1.7.2 The contractor shall identify, analyze, and recommend mitigations on integrated launch process flow issues including technical review and recommendations to LCG technical correspondence and taskers. The contractor shall update mission schedule documentation, including, but not limited to: weekly Vehicle Activity Review slides, weekly LCG mission assurance and readiness slides, and weekly senior leader meeting documents and slides.

1.3.1.7.3 The contractor shall compile inputs from LVC, SVC, SV program office and 45 Space Wing (45 SW) agencies to provide strategic logistics planning to create a detailed schedule de-conflicting infrastructure requirements, anomaly reviews, and daily vehicle processing activities.

1.3.1.7.4 The contractor shall develop an integrated schedule identifying the critical path and provide written detailed status of 45 LCG launch flow process activities (e.g. EELV, WGS, GPS and 45 SW launch support activities (e.g.

planned power & water outages, road maintenance, and controlled burns) to 45 LCG leadership. The contractor shall participate in daily LCG Ops meetings and weekly Vehicle Activity Reviews (VARs)

1.3.1.7.5 The contractor shall de-conflict major milestones in the launch process and manage mission documentation to ensure strict technical compliance and standardization.

1.3.1.8 LAUNCH RISK MANAGEMENT (N/A)

1.3.2 SE&I IN SUPPORT OF 45 SW/45 LCG LAUNCH PROGRAMS

The contractor is responsible for, but not limited to the following:

1.3.2.1 SYSTEMS ENGINEERING AND INTEGRATION

1.3.2.1.1 SPACECRAFT PROCESSING ENGINEERING

1.3.2.1.1.1 The contractor shall monitor mission assurance process execution for active satellite programs IAW AFSPCI 21-202 V2, AFSPCI 10-1208 in order to identify deviations, weaknesses and limitations and provide recommendations to the Government for mission assurance process improvement. Anticipate eight satellite programs per year.

1.3.2.1.1.2 The contractor shall document and conduct risk assessments on deviations, weaknesses and limitations and provide recommendations in a weekly status report delivered by the third business day of each week.

1.3.2.1.1.3 The contractor shall conduct analysis of technical issues or problems delegated by the Government and make…