Draft_Performance_Work_Statement_(PWS)_Draft_SRP-4.docx

DRAFT

FA8818-16-R-0022

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

SMALL ROCKET PROGRAM (SRP)-4

Xxxx 2016

Contents

Description of Services/General Information Scope and Objectives This PWS delineates the Launch Service Contractor (LSC) tasks required to perform launch operations and associated services necessary to conduct orbital missions from 0-400lbs to Low Earth Orbit (LEO) and sub-orbital missions in support of the SRP-4. The contracting agency is Space and Missile Systems Center (SMC) Launch Enterprise (SMC/LE), Rocket Systems Launch Program (RSLP). Contractual direction is provided by the Procuring Contracting Officer (PCO), SMC/ADK, at Kirtland AF Base, New Mexico.

General Description of Services SMC requires complete launch solutions as defined in this document and the associated Mission Requirements Document (MRD) for the SRP-4. A launch solution is the totality of the launch vehicle and associated services required to meet the specific orbital or sub-orbital launch objectives. This will include, but is not limited to, completion of design and development for any launch system designs that have not been previously qualified to mission levels, fabrication, test, and integration of the launch vehicle (LV) or vehicles, all required LV support, integration of the LV with the Space Vehicle(s) (SV)/Payloads, and launch facilities. The term Space Vehicle will be synonymous for all forms of payloads in this PWS. This effort requires the LSC to conduct a number of activities that together comprise a complete launch solution. These activities may include customization of the basic LV or components to meet mission requirements, development and fabrication of newly designed structures and stages, analysis, build, test, integration, and launch of the proposed solution to meet specific mission objectives identified in a specific MRD. Mission-specific customization may include, but is not limited to, guidance and control systems, LV instrumentation systems, trajectory software, re-entry vehicle configurations, payload integration, range support, facilities, storage and other associated activities. Commercial or Government Furnished Property (GFP) based LVs, components, and support systems may be utilized.

The LSC is expected to maintain the capability to complete the design and development, fabricate, test and launch between 18 and 24 months from Task Order (TO) award. The actual launch date objectives/thresholds for each mission will be specified in the MRD, or the LSC shall assume a launch date 24 months after TO award.

The minimum separation between launches under this effort shall be 60 calendar days unless otherwise negotiated. Launches may occur from air, land or sea from any US Government or Government-leased commercial range worldwide.

Government Furnished Property: The Government will offer excess ballistic missile motors, as well as related handling and test equipment, to be furnished as GFP for use at the LSC's discretion. Excess ballistic missile motors are provided in flight worthy condition while all other GFP is furnished as is. The LSC shall manage and maintain GFP (if applicable) using documented LSC procedures when Government-provided procedures are unavailable. At the conclusion of a launch campaign the LSC shall refurbish, repackage and return all remaining Government-owned equipment as directed by the contracting officer. If the LSC plans to use this GFP they shall formally request its use through:

If the offeror plans to use any other GFP, they are responsible for contacting the owner and arranging for its use on this contract.

Management and Communications SMC will assign a Contracting Officer’s Representative (COR) to each TO awarded under this contract. This COR will act as the primary interface with the LSC and will provide Quality Assurance Surveillance on behalf of the Contracting Officer (CO). SMC will also assign a Mission Manager (MM) who will be responsible for leading an Integrated Product Team (IPT) to identify and manage the full breadth of mission planning and issues, including interfacing with the LSC to coordinate activities with stakeholders. The MM and the COR duties will typically be assigned to the same person. The LSC shall structure their program coordination to provide clear, direct points of contact with the Government. The LSC shall communicate and coordinate program status, discussion of technical information, resolution of contract and financial issues and provide meeting support.

Systems Engineering (SE) Insight The LSC shall provide services that reflect a structured systems engineering approach to support provision of a reliable launch service and coordinated execution of the various engineering processes (e.g. hardware, software, configuration management, quality assurance, material review board, change control, requirements flow-down, processes and procedures). The Government will review this structured approach through the use of formal reviews. These reviews also serve as opportunities for the Government to conduct service performance surveillance as described in Section 2. For the purpose of these reviews, the Government encourages the LSC to leverage analyses and/or data previously presented to the Government under this contract, as applicable. For all formal reviews the LSC shall submit their evidence of performance in two groups.

Entry Criteria: The first group of evidence must meet the entry criteria specified for the review as detailed in Annex 3. Entry criteria evidence shall be submitted forty five (45) calendar days (or earlier if available) in advance of the review event and will be reviewed by a Government team of subject matter experts. The Government will perform a technical evaluation of the evidence submitted and determine whether the LSC has adequately met the entry criteria and is prepared to conduct the formal review. The determination of the Government will be communicated to the LSC by the COR no later than twenty one (21) calendar days prior to formal review. In the event of a finding of non-readiness, the specific deficiencies will be communicated to the LSC. The LSC will provide a get-well plan, which includes a burn-down plan and schedule to remedy deficiencies. This first group of evidence is not intended to be reviewed in depth during the formal review, but a copy of the evidence submitted shall be available at the review. [CDRL A002] Exit Criteria: The second group of evidence is a draft of the formal review package and is submitted to demonstrate that the LSC plans to substantially address all of the exit criteria for the review. This evidence shall be submitted twenty one (21) calendar days prior to the review event. The COR will determine the adequacy of the evidence submitted before the Government commits its resources to the review. Another panel of Government leadership and subject matter experts will determine if the evidence actually presented at the formal review comprehensively addresses the exit criteria. The determination of the Government will be communicated to the LSC by the COR. Exit criteria for the formal reviews are detailed in Annex 3. [CDRL A002] Areas of exit criteria deficiencies identified by the Government during the formal review will be communicated to the LSC at the close of the review. Formal review exit criteria deficiencies, commonly referred to as “liens,” will be validated by the COR and considered by the CO in the determination that the relevant service has been satisfactorily performed in accordance with Section 2 of this document. The LSC is responsible for collecting, logging, disseminating and assigning resources for responding to each lien. The LSC will provide a get-well plan, which includes a burn-down plan and schedule to remedy deficiencies. A copy of this documentation shall be provided to the COR no later than seven (7) calendar days after the review. Closure dates will be agreed to by the COR and the LSC.

Delta Review: For evidence supporting either entry or exit criteria, that has previously been reviewed under a specific TO, only changes made since the previous review (deltas) need to be covered in subsequent reviews. [CDRL A002]

Technical Performance Measures (TPM):The LSC shall establish TPMs that, as a minimum, include the following: 1) Definition of the TPM and the relationship to specifications 2) Expected values at the end of assessment periods and the completion of major events 3) Variation between the expected and measured performance 4) Variation in performance as a function of time 5) Conditions, scenarios, and configurations associated with each expected and measured performance and 6) Mitigation plan for TPMs showing shortfalls in performance. [CDRL A028] Mission Assurance The LSC shall conduct mission assurance (MA) in accordance with their internal processes and procedures. In addition, the LSC shall provide support for the Government’s independent MA as described in Section 1.8.2.

Cybersecurity Unclassified Missions Requirements: All nonfederal computer systems and software packages that will be used for processing, transmitting, and/or storing Government unclassified information shall adhere to all recommendations outlined within NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information System and Organizations. This is the standard for federal agencies to ensure the protection of the confidentiality of controlled unclassified information when not resident on federal information systems. [CDRL A025]

Classified Missions: All nonfederal computer systems and software packages that will be used for processing, transmitting, and/or storing Government classified information shall be accredited following the Defense Security Service (DSS) Office of the Designated Approving Authority (ODAA) certification and accreditation process. This is the standard process under which commercial information systems handling DoD information achieve and maintain their Authority To Operate. The DSS process is documented in the DSS Manual for the Certification and Accreditation of Classified Systems under the NISPOM. The security requirements are documented in DoD 5220.22-M, National Industrial Security Program Operating Manual. For DSS purposes, hardware and software for certification and accreditation is not expected to exceed a combined Information Sensitivity Matrix of Medium, Medium, Low as defined in DoD 5220.00-M. This sensitivity level and accrediting authority is subject to change if the mission will process classified data. Changes will be documented in the mission specific MRD. [CDRL A025] Associate Contractor Agreements and Non-Disclosure Agreements The LSC shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement(s). These agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the conduct of the mission, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Since the associate contractors will vary by mission they will be listed in the MRD.

ACAs shall include the following general information:

· Identify the associate contractors and their relationships.

· Identify the program involved and the relevant Government contracts of the associate contractors.

· Describe the associate contractor interfaces by general subject matter.

· Specify the categories of information to be exchanged or support to be provided.

· Include the expiration date (or event) of the ACA.

· Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

A copy of such agreement shall be provided to the CO for review before execution of the document by the cooperating contractors.

The LSC is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government. All costs associated with the agreements are included in the negotiated prices of applicable orders issued under this contract. Agreements may be amended as required by the Government during the performance of this contract.

Non-Disclosure Agreements: The LSC shall establish Non-Disclosure Agreements with other contractors performing related services for the Government such as Space Vehicle Contractors (SVC) who may be responsible for payload operations and Mission Assurance Contractors (MAC) who may perform Independent Verification and Validation (IV&V) activities on behalf of the Government.

Description of Services The LSC shall perform the services described in this section when specified in a TO. Services are shown pictorially in the figure below along with the critical review events for each service.

Figure 1 SRP-4 TO Services (SE Events Based on Notional 24 Month Timeline)

Design, Integration, and Launch Service Under this service, the LSC shall complete design and development of the mission launch solution, conduct mission trade studies and mission design, complete fabrication/integration and testing of the LV and supporting systems, and execute the launch including post flight analysis. This paragraph details the requirements for the basic launch service (CLIN 0001). Additional launch service requirements will be detailed in paragraph 1.8.2 for MA Categories 2&3 missions (CLIN 0001, 0002).

Contractor Work Breakdown Structure, Dictionary and Integrated Schedule: The LSC shall develop and maintain a Contractor Work Breakdown Structure (CWBS), CWBS Dictionary and an Integrated Schedule (IS) for each mission TO. The CWBS, CWBS Dictionary and IS shall use a common numbering system. [CDRL A019] The CWBS shall reflect the LSC’s overall view of the effort and serve as the framework for organizing activities involving the LSC and their subcontractors, Government, Range and Associated Contractors.

The CWBS Dictionary shall define the tasks to be performed in each element of the CWBS and corresponding element of the IS. This task definition shall include a complete definition of the task to be accomplished, the key processes, procedures and specifications to be used when performing the task and the CDRL item(s) to be delivered.

The Integrated Schedule shall reflect all the tasks/activities in the CWBS. Tasks/activities shall be logically linked together and show predecessor/successor relationships and establish the logical flow of dates provided by calculating the duration of all tasks using typical schedule networking tools. The IS shall display the critical path as well as schedule margin and deviation. The IS shall be integrated with the LSC’s business operations so that it is automatically maintained and updated (the IS shall not be a standalone or notional document). The IS shall reflect all planned mission activities at no less than Level 3 and be resource-loaded to Level 2 (refer to MIL-HDBK-881C Appendix J for a sample CWBS showing typical levels). Subsequent LSC Integrated Schedule updates shall identify external touch-points and dependencies. The contractor shall provide daily schedules and updates during the launch site operations campaign.

Integrated Baseline Review. The LSC shall conduct an initial Integrated Baseline Review (IBR) to establish the Performance Measurement Baseline (PMB) and assess the PMB risks. The Contractor shall conduct this IBR not later than 90 calendar days after contract award. The Contractor shall identify and document all indicators of a non-compliant Earned Value Measurement System. The Contractor shall provide monthly Contract Funds Status Reports and Contract Performance Reports. [CDRL A027] Document Changes: The LSC is required to inform the Government of any change to the documents listed in the CWBS dictionary, LV specifications, Launch Service Users’ Guide or similar documents, and provide a revised copy at no additional cost to the Government. These documents shall be prepared to ensure compliance with the MRD, this PWS, and other compliance documents. [CDRL A001, A019] Periodic and Technical Interchange Meetings: The IS shall be reviewed at Technical Interchange Meetings (TIM) and presented at formal reviews at a sufficiently detailed level to display milestones and primary processes of interest. The LSC shall support weekly meetings of the Government IPT led by the Government COR and/or MM. The LSC shall support any IPT working groups designated by the IPT and MM to address specific mission issues of concern that require the combined attention of the Government, supporting contractors, and LSC. The LSC shall produce meeting minutes and maintain a current list of action items. The LSC shall record TIM meeting minutes and capture new concerns and updated status of prior concerns with a consolidated action item list. In addition to TIM the LSC shall support weekly telecons prior to the launch campaign and daily telecons during the launch campaign. [CDRL A018] Formal Reviews: To provide the Government with opportunities for performance surveillance and insight into the processes, methodology and progress being made by the LSC, the following formal reviews shall be hosted at the LSC’s facility:

Service Requirements Review (SRR) Integrated Baseline Review (IBR) Preliminary Design Review (PDR) Critical Design Review (CDR) Pre-ship Readiness Review (PSR) (Additional formal reviews for MA Category 2 listed in paragraph 1.8.2.2.9) The timing of these reviews shall be agreed upon by the COR and the LSC. Reviews may be waived by the COR if they are deemed of low value to the mission. The COR may also combine reviews for the sake of cost and efficiency.

On-Site Government Representative(s): The LSC shall host up to two (2) full time Government representatives, and provide a workspace in an office environment. The workspace provided shall be in reasonable proximity to the location where work performed under this contract is being conducted. At a minimum the workspace shall include a desk and chair, telephone, computer with access to contractor’s network, and a public internet connection (wired or wireless). The Government representatives will typically consist of a COR and technical support personnel. The Government representative(s) shall have real-time access to contractor design, test, and integration information systems. The [on-site] Government representative(s) shall have physical access (with appropriate badging and training provided) to contractor facilities where work on the contract is being performed. Access for additional personnel to support testing, meetings, and other mission related events shall be provided by the LSC. At a minimum, access to the data described in Annex 3 shall be provided. For MA Category 2 missions, access to the data detailed in Annex 1 shall also be provided.

Requirements Analysis and SRR: The LSC shall perform requirements analysis for the specific mission; including mission requirements decomposition, allocation and validation. At the conclusion of the requirements analysis (no later than 60 calendar days after TO award or as directed by the COR) the LSC shall hold an SRR. Entry and exit criteria for the SRR are contained in Annex 3. [CDRL A002] Mission Design: The LSC shall perform the mission design for the specific mission. In this activity the LSC designs the complete mission launch solution. Excess payload capacity is reserved for the Government. [CDRL A003, A004] Interface Control Document (ICD): The LSC shall maintain configuration control and coordinate the ICD change process throughout the life of a TO. The ICDs shall be generated to document the interfaces between the LV and the SV, and the Launch Site/Range. If GFE motors are used, a separate ICD shall be created and maintained for the interface(s) between the GFE motor(s) and the LSC’s hardware. The ICD shall contain a requirements verification matrix that shall be maintained throughout the life of the ICD. The requirements verification matrix documents how requirements are verified and specifies artifacts required to demonstrate verification. [CDRL A004] PDR: Before the LSC conducts a detailed launch solution design the LSC shall have a preliminary design that meets (or is converging on meeting) the requirements generated in the Requirements Analysis. The LSC will then request that the PDR be held at the LSC facility to ensure the concepts and preliminary designs are adequate to meet mission requirements. The LSC shall conduct design/mission analyses as required to determine that the LV and mission designs meet requirements. The objective of the PDR is to demonstrate preliminary design of design items, interfaces, or design modifications that must be implemented to meet mission requirements, and a mission design concept that the preliminary design system satisfies. Entry and exit criteria for the PDR are contained in Annex 3. After a successful PDR the LSC will be prepared to execute the detailed design for their launch solution. [CDRL A002, A015, A018, A019, A020] CDR: At the conclusion of the mission design phase (approximately T-10 months to launch or as directed to by the COR) the LSC shall hold a CDR. The objective of the CDR is to demonstrate critical design of any design items that were previously only developed to the preliminary design level, and a full mission design that the critical design system satisfies. Entry and exit criteria for the CDR are contained in Annex 3. If there are no new designs or design modifications required to meet the mission requirements, the LSC may request to combine PDR and CDR into a single Mission Design Review. If mission design changes after CDR, then a delta review may be required, as directed by the COR. [CDRL A002, A015, A018, A019, A020] Mission Development: The LSC shall perform Mission Development to ensure that the Government is provided with a launch solution design that is capable of meeting all the requirements of the SRP-4 MRD and this PWS. [CDRL A015] Coupled Loads Analyses (CLA): CLAs shall be performed by the LSC to predict the maximum loads that can be expected by the SV during the launch event. The CLA will address key loading events (e.g. lift-off, maximum dynamic pressure, transonic, staging/ignition events, engine cut-offs and restarts, and steady state conditions, as applicable). The preliminary CLA shall be performed based upon preliminary SV-provided models to support SV design and test programs. A final CLA shall be performed with test verified models.

Design, Fabricate & Test: The LSC shall design, develop, fabricate and test flight hardware and flight software, necessary to conduct the mission described in the MRD. The LSC shall conduct hardware and software system level testing to meet qualification requirements. Flight hardware and software shall be fabricated and developed under configuration control. All work performed under this effort shall be performed in accordance with the LSC’s processes, procedures and LV specifications. [CDRL A001, A004, A011] Predicted Environments: The LSC shall generate predicted launch environments based upon mission development activities. The LSC shall ensure that the predicted environments meet the requirements stated in the MRD and ICD. The LSC shall be responsible for any changes required to the LV to meet these requirements.

PSR and Shipping: The PSR must be completed prior to shipping major LV components or support equipment to the launch site so that the Government and other launch campaign stakeholders may assess LSC launch campaign readiness and schedule risk prior to committing resources to the campaign. The PSR will be held at approximately T-60 days to launch or as directed to by the COR. The LSC is responsible for shipment and/or transportation of all LV hardware, Ground Support Equipment (GSE), Launch Support Equipment (LSE) and other necessary items to the Launch Site. [CDRL A002, A019] Readiness: At the PSR, the LSC shall provide an overview demonstrating completion of the Range Safety preparations and tailoring (if required), an acceptable approach to Flight Safety and Flight Termination, and readiness of the launch site and support facilities. The LSC shall also demonstrate that system level testing has been completed and the LV hardware is prepared for shipment to the launch site.

Shipment of GFE Motors and Equipment: If GFE motors are used; the Government will be responsible for shipping these motors and direct support equipment from the processing facilities at Hill AF Base, Utah to a motor processing location at or near the launch site in coordination with the LSC and the Range. The LSC shall take responsibility for the GFE motor (via DD Form 1149) upon receiving inspection, which shall be conducted when the motor is removed from the shipping container at or near the launch site. At the conclusion of a launch campaign the LSC shall refurbish, repackage and return all remaining Government-owned equipment as directed by the CO.

Launch Campaign: The LSC shall execute the launch campaign, coordinate all safety operations with the Range and ensure that critical skills and qualified personnel are available when required for integration, testing and on-console operations. The LSC shall also provide calibrated, certified and qualified LSE and GSE as required for the completion of range integration tasks to process, prepare and launch the LV with the integrated payload(s). This activity requires close cooperation between the Government, LSC, payload provider and the Range.

Launch Site and Services: The Government will provide Government services at Government ranges (e.g., Flight Safety, Telemetry, Radar, etc.). The LSC shall specify all required Government range services/support in each mission proposal. All spaceport services, non-Government range services and launch site services shall be provided by the LSC, unless otherwise dictated in the MRD. [CDRL A004, A010] Range Requirements Coordination and Documentation: The LSC shall comply with Range processes to ensure that the requirements specified in the MRD and this PWS are safely executed and properly coordinated with the Range. The LSC is responsible for obtaining, producing and/or coordinating all items required by the range. The LSC shall develop and provide Universal Documentation System (UDS) inputs for submittal by the program office to the Range as required by the launch site. The LSC shall participate in Range working groups as required. [CDRL A010, A020] Range Safety: The LSC shall comply with AFSPCMAN 91-710 (or equivalent, when specified by the cognizant range) for all applicable launch site activities. These safety requirements may be tailored by the LSC, as detailed below. The Range may also “grandfather” a launch solution’s range safety approval if the launch solution was approved by the Range under previous requirements (e.g. EWR 127-1). The LSC is responsible for obtaining approval for range safety tailoring and/or grandfathering. The LSC shall coordinate scheduling all activities and/or operations with the Range Safety Office, as applicable. [CDRL A010, A020] Ground and Flight Safety Hazard Analyses: Ground and flight safety hazard analyses, including on-orbit operations, shall be performed in accordance with AFSPCMAN 91-710 (or equivalent when specified by the cognizant range).

The LSC shall work with the cognizant range safety office in coordination with program office to tailor the applicable safety requirements for the launch system, complete development of a compliant flight safety system and gain range safety approval for the implementation of their flight safety system (if required). The LSC shall make prompt waiver requests if unable to meet range safety requirements due to technical issues with the design or flight hardware. Failure to obtain approval for the desired tailoring/grandfathering shall not relieve the LSC of their responsibilities under this contract. [CDRL A010, A020] Safety and Environmental Documentation: The LSC shall support the government safety and environmental documentation required for safety, hazards, debris, and environmental analysis. Documentation includes System Safety Program Plan, Safety Assessment Report, Failure Modes and Effects Analysis, Reliability reports and AF Form 813 Environmental Impact Analysis inputs. [CDRL A020]

Facilities and Services: The LSC shall provide the required facilities and services at the launch site which meet all mission requirements defined in the MRD and this PWS. These requirements shall include safety, contamination control, payload integration, flight control facilities, transportation, lifting/stacking and fueling infrastructure, unless otherwise specified. The Payload Processing Facility (capable of accommodating LSC encapsulation activities) will be provided by the SVC unless otherwise stated in the mission specific MRDs. [CDRL A010] Approvals and Waivers: The LSC shall obtain any necessary coordination or approval from the launch base or test range for activities taking place at the launch base or test range. The LSC shall obtain appropriate documentation, approvals, and perform other necessary actions to secure access to GFP, equipment, facilities, etc. If waivers are required, the LSC shall obtain them prior to initiating facility activation or modification. The LSC's failure to gain a required approval or waiver shall not relieve the LSC of any responsibilities under this contract. If the LSC identifies any work outside the scope of this contract that is required to meet range requirements, the LSC shall immediately notify the CO. [CDRL A010, A020] New START Treaty Requirements: If the LV uses GFP motors subject to New START treaty considerations (e.g. Minuteman III ICBM first stage motors), the LSC shall provide “interpretive data” on all telemetry that is transmitted prior to the LV achieving orbit. The data shall be provided to LEX for incorporation into documents required by the New START Treaty. Encryption of telemetry data may not be permitted when launch is subject to the New START Treaty. [CDRL A017] Classified Payloads: When classified payloads are processed the LSC shall provide trained people with the proper clearance to perform the required work in compliance with the applicable Security Classification Guide. Classification requirements for each mission will be specified in the MRD and associated mission-specific DD254.

LV/SV Operations: The LSC shall integrate the payload(s) with the LV in a clean room environment as specified in the MRD, and perform end-to-end testing with the payload(s). End-to-end verifications tests are tests of the hardware/software to obtain or validate engineering data on the performance of the system prior to the execution of the launch operation. [CDRL A012] Launch Verification Testing: The LSC shall conduct these tests during launch processing in support of each mission. An integrated field processing procedure will be prepared by the test conductor in each test. All anomalies shall be documented by the LSC. [CDRL A011] LV/SV Integrated Processing: Integrated LV/SV processing shall be performed in preparation for SV emplacement on the LV at the launch site. During integrated processing, the SVC shall furnish certified handling/GSE required to interface from the crane hook (or other GSE) to the SV, as required during the integration process. The LSC shall accommodate the SV GSE at the launch site. [CDRL A004] LV/SV Mating: Unless otherwise specified in the MRD, the SVC will be responsible for all SV integration activities prior to integrated operations. The SVC will transfer responsibility for the SV to the LSC when the SV is fully prepared for immediate mating with the LV and is approximately 3” away from the LV mating surfaces. The LSC shall conduct mechanical mating, spurious voltage, and electrical connection checks in concert with the SVC. The LSC shall assist the SVC in conducting post-mate checks that may include the SV operational assurance tests and a compatibility test of the LV and SV systems, and the GSE interfaces. [CDRL A004] LV/SV Flight Integration Tests: The flight integration test shall be performed using the flight hardware to verify electrical compatibility and system performance between the SV and the LV upper section(s) prior to movement to the launch site (typically performed within a processing facility at the launch range). Integrated operations will be performed using procedures approved by participating agencies. The LSC will provide hardware for any LV-required tests and the SVC will provide hardware for any SV-required tests. [CDRL A004] SV Support Equipment and Ground System Checkout: The SVC will install the required SV Support Equipment at the launch site in locations to be defined in the LV/SV ICD. A design compatibility test to establish high confidence in electrical compatibility of the SV and SV GSE with the launch complex will be performed at the launch site. The SV provider will prepare the test procedure and conduct the test. The LSC and the Range shall support the test as required. The LSC shall provide support personnel and the SVC will supply all SV-related GSE. The LSC shall provide support to the SVC to test the installed equipment. [CDRL A004] Simulations & Rehearsals: The LSC shall coordinate and conduct one full mission dress rehearsal (a simulated countdown, exercising range interfaces to verify the operational readiness of the entire Aerospace Vehicle Equipment (AVE)/ground system with all launch team members) and one wet dress rehearsal (for liquid propulsion LVs only). (The mission dress rehearsal and wet dress rehearsal may be combined into one rehearsal, contingent upon approval by the COR.) (The term AVE refers to the entire launch system.) These simulations must include all launch day participants (e.g., Range, LSC, SVC, Government, and others as applicable) unless otherwise specified. The LSC shall coordinate and conduct academics (training sessions on specific day of launch activities), delta academics, and tabletop exercises as required. [CDRL A004, A016] Mission Notebook and Launch Constraints: The LSC shall produce and provide mission launch notebooks and distribute correction sheets as required. The LSC shall compile and document all SV and LV launch constraints, coordinate these with the MM and publish the constraints in a Mission Constraints Document that shall become part of the mission notebook. [CDRL A016] Launch Activities: The LSC shall prepare the LV for launch, conduct prelaunch checkout, conduct launch operations, ensure the collection and recording of telemetry during the launch, support post launch mission activities, perform post-flight analysis, and conduct site shutdown. Additional Day of Launch requirements for MA Category 2 missions are listed in paragraph 1.8.2.2.12.

Nets and Telemetry: The LSC shall provide the Government with access to all voice (transmit and receive), video, and data networks used for launch support. The LSC shall provide for adequate instrumentation at the launch site, downrange, and on the LV in order to measure the predicted (modeled) launch and flight environments. (At Government ranges, the LSC shall provide requirements for range and downrange telemetry collection via the UDS process.) Telemetry from this instrumentation shall be provided real-time to a demarcation point defined in the ICD. The LSC shall provide all conversions (engineering unit conversion file) necessary to convert the raw data to engineering units. [A004, A016] Day of Launch: For MA Category 1 missions, the LSC shall be responsible for Day of Launch operations and the final readiness decision for the combined LV/SV system. The LSC shall accommodate a small contingent of Government personnel to monitor launch operations for Government insight. The Government will not have an MD for these launches or have an approval role in the launch decision. The LSC shall accommodate SV personnel on console. The LSC shall not launch if the SV lead informs the LSC of non-readiness to launch during the final poll for launch readiness. In addition, if GFP motors are involved in a MA Category 1 launch, the LSC shall accommodate a small Government team on console to monitor the status of the GFP motors. The LSC shall not launch if the Government team informs the LSC of non-readiness to launch, based solely upon GFP motor status, during the final poll for launch readiness. [CDRL A016]

The LSC shall provide data to support trajectory and covariance data to support Collision Avoidance Calculations (COLA).

The LSC shall define an LV instrumentation plan (type and model, function, location, orientation (if applicable), and data retain) [CDRL A004, A015, A016].

Post-Flight Activities: The LSC shall conduct an analysis of and participate in a review of all launches, operations, flight telemetry, and other data to determine LV performance.

Quicklook Analysis: The LSC shall develop the T+4 hours (Quicklook) analysis and T+4 day post-flight analysis report. Analyses shall include characterization of trajectory parameters, mission timeline/events, environments, telemetry performance, observations and anomalies. [CDRL A017] Lessons Learned: The LSC shall collect lessons learned throughout the performance of the TO and include these in the post-flight report. [CDRL A017] Post-Flight Report/Review: The LSC shall complete the post-flight report by T+30 days. The LSC shall attend and support a Government post flight review at SMC (Los Angeles, CA) at approximately T+60 days. [CDRL A017] Failure Review: In the event of a complete or partial mission failure, the LSC shall participate in a Government-led evaluation of the root cause of the failure event to identify remedial actions required to prevent recurrence. Mission failure reviews will be conducted in accordance with AFI 91-204. The LSC shall enable Government access to all internal investigations of anomalies and failures. [CDRL A014]

Mission Assurance Support Service Category 1: These missions will not be subject to the SMC flight worthiness certification process or Government IV&V oversight. These missions will be licensed under Federal Aviation Administration (FAA) licensing guidelines. The LSC shall obtain an FAA launch license and is responsible for all requirements to obtain such license. In addition, the LSC shall be responsible for ensuring the applicable launch site meets FAA licensing requirements and any activities required to bring the launch site into licensing compliance. This LSC shall demonstrate that all required FAA licenses have been obtained at the PSR. Obtaining applicable licenses shall not relieve the LSC from the requirements described in Section 1.8.1. Failure to obtain applicable licenses shall not relieve the LSC from their responsibilities under this contract. [CDRL A010] Category 2: For Category 2 MA missions, the LSC shall provide additional information and support for the Government’s MA efforts and the Government’s Independent Readiness Review Team (IRRT). In addition, the following launch service requirements shall be applicable for these missions (in addition to the launch service requirements detailed in paragraph 1.8.1):

Spaceflight Worthiness: These missions will be certified spaceflight worthy by SMC and require the LSC to support the SMC Readiness Review process, the IV&V efforts of the MAC and the IRRT. Details of the required data, access and submittals are in Annex 1. The LSC shall analyze the launch system against each of the criteria listed in SMC-G-1202 “Spaceflight Worthiness Criteria”, identify compliance or non-compliance, and cite confirming evidence and/or associated mitigations for non-compliances. SMC flight worthiness certification is required prior to launch. [CDRL A022] Software & Flight Computer: The LSC shall provide documentation reflecting flight software requirements, design, source code, test description, and test reports.

Prior to the LSC’s MA Category 2 mission using a specific flight computer configuration, the LSC shall deliver a flight representative computer to the Government no later than 45 calendar days after CDR. This computer will be used by the MAC to run hardware-in-the-loop simulations. The LSC shall assign to the computer an Item Unique Identification number (IUID) for material tracking. Any hardware or software modifications that are subsequently made to the actual flight computer (on any mission) shall also be made by the LSC to the representative flight-like computer at no additional cost to the Government. The LSC shall provide technical support as needed and design information to the MAC to facilitate integration of the computer with the MAC’s test bed. [CDRL A005, A006, A007, A008, A009] Clarification and Discussions Regarding Information Submitted: The LSC shall make available appropriate personnel for the discussion and clarification of issues related to items detailed in Annex 1 and Annex 3. The LSC shall support reviews and discussions, as required, to provide the Government, Independent MAC and/or the IRRT with confidence in the accuracy and sufficiency of the information provided. The LSC can minimize the amount of support required for these discussions and clarifications by providing well supported and thoroughly documented submissions.

Requirements Decomposition & Validation: Requirements shall be decomposed in a hierarchical structure starting with the highest level requirements. These high-level requirements are decomposed into functional and performance requirements and allocated across the major elements of the proposed launch solution, with any new design elements or design changes to meet requirements identified accordingly. These are then further decomposed and allocated among lower level elements until a complete set of requirements is achieved.

At each level of decomposition (solution, system, subsystem, component, etc.), the total set of derived requirements (to include ICD) must be validated against the higher level parent requirements as specified in the PWS, MRD, and other compliance documents. The use of an automated requirements management system (e.g., DOORS) is desirable but not required. Requirements analysis results in preliminary performance specification, allocation of requirements, identification of software components, a preliminary risk assessment and risk management plan, and identification of critical path drivers. [CDRL A001, A005, A019, A021]

Risk assessments shall include the Contractor's assessments of LV risks, to include those identified by other organizations as specified by the COR, and shall comply with the Government-specified format and criteria for consequences (severity) and likelihood (probability) [CDRL A022].

Test Planning and Qualification Testing: The LSC shall perform Test Planning and Qualification Testing to ensure that the Government is provided with a launch solution design that is qualified and capable of meeting all the requirements of the MRD and this PWS. . [CDRL A011] Test Planning: All testing shall be consistent with test-like-you-fly (TLYF) practices; any planned deviations from TLYF practices shall be documented and presented at the Test Readiness Review (TRR). Any deviations from TLYF due to unforeseen test circumstances shall be presented at the Pedigree Review (PR) and PSRR. The LSC is required to inform the COR of critical testing milestones so that Government representation may be present. Government representatives and the MAC may witness some or all of these tests. [CDRL A012] TRR: At the conclusion of the test planning phase (approximately T-13 months to launch, or as directed by the COR) the LSC shall hold a TRR to review the adequacy of the planned testing. Entry and exit criteria for the TRR are contained in Annex 3. [CDRL A002, A012, A019] Support Equipment: The LSC shall identify, design, test, qualify and approve all GSE and LSE required for flight operations at the Range prior to the PSR. This equipment may include, but is not limited to, lifting slings, transportation fixtures and equipment, umbilical electrical harnesses, electrical test equipment (including electrical GSE) and temperature control systems. The LSC shall ensure that all required support equipment for assembly, integration, encapsulation and launch at the launch site has been calibrated, safety-qualified and is in working order and available when needed. [CDRL A012] Qualification Testing: For qualification testing, the LSC shall release all drawings under configuration control, and manufacture, fabricate or acquire the qualification items. The LSC shall then perform qualification testing on flight-representative qualification items in accordance with the ITP. The LSC shall report and assess test anomalies and failures. [CDRL A004, A012, A013, A014] Acceptance Testing: Once the design has been qualified, acceptance testing may commence. The LSC shall not ship major hardware to the Range for field processing until acceptance testing has been successfully completed, test documentation has been verified and the as-built verification of all hardware and software has been completed. [CDRL A012, A013] Formal Testing Results: Results from all formal testing (qualification data summary, acceptance test data, and system test data) will be summarized and reviewed as part of the PSRR. The LSC shall report and assess test anomalies and failures. [CDRL A002, A014] Flight Hardware Risks: The LSC shall evaluate flight hardware risks associated with Government-Industry Data Exchange Program and Missile Defense Agency advisories. The LSC shall have an internal process to identify sibling issues and evaluate associated flight hardware risks. [CDRL A023] QTR: At the conclusion of the qualification testing phase (approximately T-5 months to launch or as directed by the COR) the LSC shall hold a Qualification Testing Review (QTR) to review the qualification testing results. Entry and exit criteria for the QTR are contained in Annex 3. [CDRL A002, A013, A019] Design Verification Tests: Design verification tests shall be conducted to establish confidence in compatibility between the LSC hardware and any other contractor or stakeholder hardware. The LSC shall prepare a test report summarizing the test set up, the results, and any anomalies. [CDRL A011, A012, A013, A019]

Integrated Mechanical / Structural Analysis and Verification Tests: A series of mechanical/structural tests shall be conducted at the LSC facilities to verify the LV mechanical and structural characteristics. The LSC shall conduct the testing with the greatest amount of SV participation possible. The LSC and SV provider will provide flight representative hardware to support conduct of the testing.

LV / SV Mechanical Interface Verification: A mechanical fit check shall be performed to verify the mechanical compatibility between the LV and the SV separation system as documented in the LV/SV ICD, including cable routing and connections and any areas where there are potential interference issues. The LSC and the separation system provider will provide flight representative hardware to support the fit check. The fit check shall be performed at the LSC facility.

Non Destructive Testing (NDT): The LSC shall conduct NDT on all flight structures fabricated with composite materials. For structures that do not have other hardware mounted on them, 100% testing shall be performed. For structures that do have other hardware mounted on them, NDT shall be performed to the maximum extent possible.

Electrical Verification Tests: End-to-end testing shall be conducted to verify the electrical interface between the LV and SV. The testing will use flight-representative hardware furnished by the LSC as well as applicable SV components furnished by the SV and/or separation system contractor. The test shall include the complete exercise of all electrical interfaces between the LV, separation system and the SV. Integrated test procedures shall be reviewed and approved by participating agencies. The location of the test will be proposed by the LSC. [CDRL A011, A012, A013] PR: The LSC shall host a PR at approximately T-70 days to launch (or as approved by the COR). The main purpose of a PR is to ensure that the flight hardware/software has been built and satisfactorily tested to establish flight worthiness in accordance with the released design qualification documentation. Entry and exit criteria for the PR are contained in Annex 3. [CDRL A024] Additional Reviews: In addition to the formal reviews detailed in paragraph 1.8.1.4, the following reviews shall be hosted by the LSC at the LSC’s facility:

Test Readiness Review (TRR) Qualification Testing Review (QTR) Pedigree Review (PR) The…