Attachment_2_SRP-O_PWS_Cat2_.docx

FA8818-18-R-0001

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

SMALL ROCKET PROGRAM-ORBITAL (SRP-O)

Category 2 Mission Assurance

1 April 2018

Table of 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 an orbital Mission Assurance (MA) Category 2 mission in support of the Small Rocket Program-Orbital (SRP-O) Completion (C-type) contract. SRP-O provides orbital launch services and launch support services associated with the Rocket Systems Launch Program (RSLP). The contracting agency is the Space and Missile Systems Center (SMC) Launch Systems Enterprise (SMC/LE), Rocket Systems Launch Program (RSLP). Contractual direction is provided by the Procuring Contracting Officer (PCO), SMC/ADK, at Kirtland Air Force Base, New Mexico.

The objective of this program is to provide flexible small launch capability using Launch Vehicle (LV) designs based on commercial and/or Government Furnished Property (GFP) propulsion systems to meet a variety of mission and payload requirements. SRP-O provides small satellite launch services; the specific mission objectives, satellite mission information, launch history requirements, and launch solution constraints are defined in the Mission Requirements Document (MRD).

The spacelift capability for SRP-O is a total payload mass of 0 to 400 pounds (lbs.) to Low Earth Orbit (LEO). The payload may consist of one or more space vehicles (SVs).

General Description of Services:

SMC requires launch services composed of design, integration, test, and launch activities as defined in this PWS and the mission specific MRD. A launch service is the totality of the launch vehicle and associated services required to meet the specific 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 payloads, and provision of launch facilities. Launch services may also include one or more technical analyses to inform specific mission requirements decisions.

The SRP-O timeline to complete the design and development, fabricate, test and launch is between 18 and 24 months from contract award. The actual launch date objectives/thresholds for each mission will be specified in the MRD. If not specified in the MRD the LSC shall assume a launch date 24 months after contract award.

Launches shall be from any US Government, Government-leased, or FAA-licensed commercial range worldwide and may occur from air, land, or sea.

Government Furnished Property (GFP):

GFP includes Government Furnished Equipment (GFE) used for the contracted effort by the contractor but not consumed, and Government Furnished Material (GFM) consumed in the contracted effort. 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 any RSLP GFP they shall formally request it 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.

GFP Quarterly Report:

The LSC shall report quarterly GFP and Contractor Acquired Property status [CDRL A011] during active contract periods while in possession of GFP items.

GFP Closeout Service:

The LSC shall return to the Government all GFP that was received or developed, and not consumed, for use in the execution of the contract.

GFP shall be returned in the same or better condition as initially received from the Government; unless the contracting officer grants specific exception.

The LSC shall transport GFP in appropriate shipping containers to the Government specified storage location, as directed by the PCO The LSC shall provide a complete listing of any returned GFP. [CDRL A011] Management and Communications:

SMC will assign a Contracting Officer’s Representative (COR) to each contract awarded under this effort. This COR will act as the primary interface with the LSC and will provide Quality Assurance Surveillance on behalf of the PCO.

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 customer and service provider stakeholders. The MM will typically coordinate these activities via a “Giver/Receiver” list which reflects LSC deliverables defined in this contract and also captures stakeholder data requirements identified by the LSC.

The LSC shall structure its 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. [CDRL A035] Systems Engineering (SE) Insight:

The LSC shall employ a structured systems engineering approach to provide a reliable launch service and coordinated execution of the various engineering processes, including requirements flow-down to hardware and software testing, configuration management and change control, quality assurance and material review board, and risk management processes. 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 Paragraph 2.

For all formal reviews, the LSC shall submit its evidence of performance.

Entry Criteria:

The entry evidence must meet the entry criteria specified for the review as detailed in Annex 2. Entry evidence shall be submitted thirty (30) calendar days (or earlier if available) in advance of the review event. The Government red team of subject matter experts (SMEs) will perform a technical evaluation of the evidence submitted and determine whether the evidence demonstrates the LSC is prepared to conduct the formal review. The COR will communicate the determination of the Government no later than seven (7) calendar days prior to the review. [CDRL A002] Exit Criteria:

The COR will communicate any formal review deficiencies, commonly referred to as “liens,” to the LSC at the close of the review. Liens will be validated by the COR and considered by the PCO in the determination that the relevant service has been satisfactorily performed.

The LSC is responsible for collecting, logging, disseminating and assigning resources for responding to each lien, and other action items, identified at the review. The LSC will provide a get-well plan, which includes a burn-down plan and schedule to close any liens 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. [CDRL A002] 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 Systems 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 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 are not expected to exceed a combined Information Sensitivity Matrix of Medium for Confidentiality, Medium for Integrity, Basic for Availability, as defined in DoD 5220.22-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:

Associate Contractor Agreements (ACA):

The LSC shall enter into ACAs 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 PCO 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 Payload Contractors 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 PWS as specified in a MRD. Services and review events are summarized in Figure 1-1 below.

Figure 11: SRP-O Contract Services (SE Events Based on Notional 24 Month Timeline)

Mission Design, Integration, and Launch Service:

The LSC shall complete design and development of the mission launch solution, conduct mission trade studies and mission design, complete fabrication/integration, payload integration and testing of the LV and supporting systems, and execute the launch including post flight analysis.

Mission Planning Service:

The LSC shall develop and maintain an Integrated Schedule (IS) for each mission contract. The IS shall reflect all the tasks/activities planned for the mission. 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 be presented at formal reviews at a sufficiently detailed level to display milestones and primary processes of interest. [CDRL A027] Periodic Interchange Meetings:

The LSC shall support weekly meetings of the Government IPT led by the Government COR and/or MM. The LSC shall support any working groups designated to address specific mission issues of concern that require the combined attention of the Government, supporting contractors, and LSC.

The LSC shall support 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 [CDRL A018]:

· Service Requirements and Concept Review (SRCR)

· Mission Design Review (MDR)

· Test Readiness Review (TRR)

· Qualification Test Review (QTR)

· Pedigree Review (PR)

· Pre-ship Readiness Review (PSR) Formal Review Exceptions:

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):

If required by the MRD, 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 LSC’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 LSC design, test, and integration information systems associated with contracts awarded under the SRP-O effort. The [on-site] Government representative(s) shall have physical access (with appropriate badging and training provided) to LSC 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.

Requirements Analysis and SRCR:

The LSC shall perform requirements analysis for the specific mission; including mission requirements decomposition, allocation and validation of PWS and MRD requirements. At the conclusion of the requirements analysis (no later than 120 calendar days after contract award or as directed by the COR) the LSC shall hold an SRCR to present the results of requirements analysis and the mission design concept. [CDRL A002] Mission Design:

The LSC shall perform 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.

Interface Control Document (ICD):

The LSC shall create, maintain configuration control and coordinate the ICD change process throughout the life of a contract. The ICDs shall be generated to document the interfaces between the LV and the payload, and the Integration and Launch Site (ILS)/Range. The launch vehicle to ge ICD shall include a description of the telemetry data to be displayed on range consoles. If GFP motors are used, a separate ICD shall be created and maintained for the interface(s) between the GFP motor(s) and the LSC’s hardware. Each ICD shall contain a Requirements Traceability and Verification Matrix that shall be maintained throughout the life of the ICD. The requirements traceability and verification matrix documents how requirements are derived and verified and specifies artifacts required to demonstrate interface verification. [CDRL A003, A004] Space Debris Assessment Report (SDAR):

The LSC shall perform analysis and produce a SDAR to demonstrate compliance with AFI 91-217 Attachment 2 for the LV (the SV shall not be included in this report/analysis). [CDRL A015]

MDR:

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 an MDR. The objective of the MDR is to demonstrate critical design of any design items that were proposed as only developed to the preliminary design level, and a full mission design that the critical design system satisfies. [CDRL A002, A018] Pedigree Review (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. [CDRL A024] Mission Build and Test:

The LSC shall fabricate and test hardware and software to ensure that the Government is provided a launch solution design capable of meeting all the requirements of the SRP-O Contract MRD and this PWS.

Coupled Loads Analyses (CLA):

CLAs shall be performed by the LSC to predict the maximum loads that can be expected by the payload 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 payload-provided models to support payload design and test programs. A final CLA shall be performed with test verified models. [CDRL A015] 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. [CDRL A015] Fabricate & Test:

The LSC shall 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.

Pre-ship Readiness Review (PSR) and Shipping:

The PSR must be completed prior to shipping major LV components or support equipment to the ILS 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 ILS. If directed by the Government, the program and LSC will coordinate military air transport (MILAIR) of specified equipment at Government expense. [CDRL A002] 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 ILS 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 ILS.

Shipment of GFP Motors and Equipment:

If GFP 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 ILS in coordination with the LSC and the Range. The LSC shall take responsibility for the GFP 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 ILS. At the conclusion of a launch campaign the LSC shall refurbish, repackage and return all remaining Government-owned equipment as directed by the PCO.

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.

ILS 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. All spaceport services, non-Government range services and ILS services shall be provided by the LSC, unless otherwise stated in the MRD. [CDRL 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), or other range-required documentation inputs for submittal by the program office to the Range as required by the ILS. The LSC shall participate in Range working groups as required. [CDRL A010] Range Safety:

The LSC shall comply with AFSPCMAN 91-710 (or equivalent, when specified by the cognizant range) for all applicable ILS 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 plan system safety activities in accordance with MIL-STD-882E Task 102. 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 shall be performed by the LSC in accordance with AFSPCMAN 91-710 (or equivalent when specified by the cognizant Range) and MIL-STD-882E Task 106, Task 202, and Task 205.

The LSC shall work with the cognizant range safety office in coordination with program office to tailor the applicable flight safety requirements for the launch system, complete development of a compliant flight safety system and gain range safety approval for the implementation of its flight safety system (if required). The LSC shall make prompt waiver requests to the COR 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 its responsibilities under this contract. [CDRL A010, A020] Safety and Environmental:

The LSC shall support the Government safety and environmental reporting required for safety, hazards, debris, and environmental analysis in accordance with MIL-STD-882E Task 301. The LSC shall support MM development of the AF Form 813 Environmental Impact Analysis inputs. [CDRL A020] Facilities and Services:

The LSC shall provide the required facilities and services at the ILS, which meet all mission requirements defined in the MRD and this PWS unless otherwise stated in the mission specific MRDs. These requirements shall include, but are not limited to, 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 Payload Contractor unless otherwise stated in the mission specific MRDs.

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. Equivalent levels of safety requests shall be briefed at range working groups and formal reviews. 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 PCO. [CDRL A010] New Strategic Arms Reduction Treaty (START) Requirements:

GFP motors subject to New START considerations will not be provided for this effort.

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 (SCG). Classification requirements for each mission will be specified in the MRD and associated mission-specific DD254.

LV/Payload 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 LSC test conductor in each test. All anomalies shall be documented by the LSC. [CDRL A012] LV/Payload Mating:

Unless otherwise specified in the MRD, the Payload Contractor will be responsible for all payload integration activities prior to integrated operations. The Payload Contractor will transfer responsibility for the payload to the LSC when the payload is fully prepared for immediate mating with the LV, and is approximately three inches away from the LV mating surfaces. The LSC shall conduct mechanical mating, spurious voltage, and electrical connection checks in concert with the Payload Contractor. The LSC shall assist the Payload Contractor in conducting post-mate checks that may include the payload operational assurance tests and a compatibility test of the LV and payload systems, and the GSE interfaces.

LV/Payload Integrated Processing:

Integrated LV/payload processing shall be performed in preparation for payload emplacement on the LV at the ILS. During integrated processing, the Payload Contractor shall furnish certified handling/GSE required to interface from the crane hook (or other GSE) to the payload, as required during the integration process. The LSC shall accommodate the payload GSE at the ILS.

LV/Payload Flight Integration Tests:

The flight integration test shall be performed using the flight hardware to verify electrical compatibility and system performance between the payload and the LV upper section(s) prior to movement to the ILS (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 Payload Contractor will provide hardware for any payload-required tests.

Payload Support Equipment and Ground System Checkout:

The Payload Contractor will install the required payload support equipment at the ILS in locations to be defined in the LV/Payload ICD. A design compatibility test to establish high confidence in electrical compatibility of the payload and payload GSE with the launch complex will be performed at the ILS. The payload 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 Payload Contractor will supply all payload - related GSE. The LSC shall provide support to the Payload Contractor to test the installed equipment.

Simulations & Rehearsals:

The LSC shall coordinate and conduct, one green card (simulated countdown) dress rehearsal, 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) to simulate propellant loading procedures. 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, Payload Contractor, 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. The LSC shall compile mission launch notebook data and identify corrections based on these simulations and rehearsals. [CDRL A016] Mission Constraints:

The LSC shall compile all payload and LV launch constraints, and coordinate these with the MM prior to inclusion in the mission launch notebook data. [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. During the launch campaign, the LSC shall identify all daily planned activities to the MM.

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 instrumentation at the ILS, 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. [CDRL A016] Day of Launch:

The Government Launch Vehicle Single Manager will make the final decision concerning launch readiness for the combined LV/payload system, with recommendations from all involved parties.

The Government will have a Mission Director for these launches who has the approval role in the launch decision.

The LSC shall accommodate a small contingent of Government personnel to monitor launch operations for Government insight. The LSC shall accommodate Payload personnel on console.

The LSC shall provide real time vehicle telemetry data displays to Government personnel for all testing and launch operations conducted at the ILS. Specific data requirements shall be coordinated with the COR.

The LSC shall provide trajectory and covariance data to support collision avoidance calculations. [CDRL A015] The LSC shall define an LV instrumentation approach (type and model, function, location, orientation (if applicable), and data retention) for Government approval [CDRL 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/orbit insertion 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 contract. [CDRL A017] Post-Flight Analysis:

The LSC shall complete the post-flight analysis 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:

The LSC shall conduct mission assurance (MA) in accordance with its internal processes and procedures. In addition, the LSC shall provide support for the Government’s independent MA as described in this paragraph. The LSC shall demonstrate a predicted mission reliability of 95% for the launch vehicle (if GFP motors are used, the analysis should assume the certified GFP motor stack has a reliability of 99.5%). [CDRL A032] Category 2:

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.9):

Spaceflight Worthiness:

The mission 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 SMC IRRT. Details of the required data 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” (SFWC), provide a matrix identifying compliance or non-compliance, and provide and cite confirming evidence and/or associated mitigations for non-compliances. SMC flight worthiness certification is required prior to launch. [CDRL A022] SFWC Discussions:

The LSC shall make available appropriate personnel for the discussion and clarification of status and issues related to the SFWC matrix and items detailed in Annex 1 on a minimum of a monthly basis during the design, development, and test phase, and a minimum of a weekly basis during the launch campaign.

Software & Flight Computer:

The LSC shall develop flight software requirements, design, and source code with version description, test description, and test reports.

The LSC shall deliver a flight representative computer to the Government no later than 45 calendar days after MDR. 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 available 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] Requirements Decomposition, Traceability & Validation:

Requirements shall be decomposed and traced 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. The complete set of requirements shall be provided in the Specification and Requirements Documents, including a System Specification and Interface Control Documents, along with a Documentation/Specification Tree.

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. Compliance with all requirements shall be verified and artifacts of verification provided and cited. Both traceability and verification shall be documented in the Requirements Traceability and Verification Matrix. The use of an automated requirements management system (e.g., DOORS) is desirable but not required. [CDRL A001, A003, A004, A021] Risk Assessment.

Risk assessments shall include the LSC's assessment of LV risks, to include those identified by other organizations as provided by the COR, and shall comply with the SMC Risk Management Process Guide criteria for consequences (severity) and likelihood (probability). [CDRL A022].

Test Planning and Qualification/Acceptance Testing:

SRP-O missions require the use of launch vehicles designs that meet flight history requirements as specified in the MRD. For launch solutions with no demonstrated flight history, 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. Launch solutions with demonstrated flight history do not require delta-qualification testing where the current design does not meet SRP-O qualification level requirements; however the LSC shall evaluate all design qualification gaps and incorporate the results of this analysis in the Risk Assessment task above.

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 summarized at the PSR. The LSC is required to inform the COR of testing milestones so that Government representation may be present. Government representatives and the MAC may witness some or all of these tests.

Test Readiness Review (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, see Annex 2. [CDRL A002] 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 ILS has been calibrated, safety-qualified and is in working order and available when needed. [CDRL A012] Qualification Testing:

For flight hardware designs not previously qualified, initial or delta-qualification testing shall be required for this contract, 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 LTS-10-2010-04. In instances where the LSC is developing equipment that will be used on an SRP-O contract under company proprietary, Independent Research And Development (IRAD) or other non-SRP direct funding, the MAC must be allowed to review the documentation in the LSC’s facility. The LSC shall report and assess test anomalies and failures. [CDRL A012, A013, A014] Acceptance Testing:

Once the design has been qualified, acceptance testing of flight hardware 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. In instances where the LSC is developing equipment that will be used on an SRP-O contract under company proprietary, IRAD or other non-SRP direct funding, the MAC as a minimum must be allowed to review the documentation in the LSC’s facility. Any flight items for which acceptance testing has been previously accomplished shall be identified to the COR during the TRR for government acceptance of prior testing levels/results. [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 PSR, including test anomalies and failures.

Flight Hardware Risks:

The LSC shall evaluate flight hardware risks associated with Government-Industry Data Exchange Program (GIDEP) and Missile Defense Agency advisories. The LSC shall have an internal process to identify sibling issues and evaluate associated flight hardware risks. [CDRL A023] Qualification Test Review (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 QTR to review the qualification testing results. [CDRL A002] 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, or to verify complex launch vehicle functions. The LSC shall prepare a test report summarizing the test set-up, the results, and any anomalies. [CDRL A012, A013].

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 payload participation possible. The LSC and payload provider will provide flight representative hardware to support conduct of the testing.

LV/Payload Mechanical Interface Verification:

A mechanical fit check shall be performed to verify the mechanical compatibility between the LV and the payload separation system as documented in the LV/Payload 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 payload. The testing will use flight-representative hardware furnished by the LSC as well as applicable payload components furnished by the payload and/or separation system contractor. The test shall include the complete exercise of all electrical interfaces between the LV, separation system and the payload. Integrated test procedures shall be reviewed and approved by participating agencies. The location of the test will be proposed by the LSC. [CDRL A012, A013] Government Readiness Reviews:

In addition to the formal reviews previously discussed, the LSC shall support the following Government reviews by providing presentation material and technical data as required. LSC programmatic and technical personnel shall be required to attend. These reviews will typically be held at Government facilities.

This support will include summarizing analyses, test results, technical data, subassembly graphics, and other information on current, emerging and closed launch service issues. [CDRL A018, A022]

SERVICE SUMMARY –

The COR for the launch service contract will perform surveillance of the service provided. The table below provides an overview of the performance thresholds the COR will employ to evaluate the services provided. For services where the threshold incorporates validated complaints, the COR will solicit positive and negative feedback from designated stakeholders and validate any complaints as part of the service evaluation. The COR will assess the quality of each service provided and make a final recommendation to the PCO for determination of the acceptability of the service rendered.

Exit: <3 liens against the SRCR exit criteria as determined by the COR.

Schedule: This review shall be completed no more than 60 days after contract kickoff or as determined by the COR.

and Sub-paragraphs

Entry: <2 findings of non-readiness against the MDR entry criteria as determined by the COR, corrected in one cycle.

Exit: <2 liens against the MDR exit criteria as determined by the COR.

Schedule: Completion of flight safety requirements tailoring prior to MDR.

Schedule: MDR shall be completed approximately T-10 months to launch or as directed to by the COR.

and Sub-paragraphs

Entry: <3 findings of non-readiness against the PSR entry criteria as determined by the COR, corrected in one cycle.

Exit: <3 liens against the PSR exit criteria as determined by the COR.

Schedule: Completion of PSR within 30 days of IS-reflected date as of MDR, unless otherwise specified by the COR.

1.4

Launch Campaign

1.9.10 and Sub-paragraphs

Performance: LSC support equipment & logistics will be available and meet all mission requirements.

Schedule: No more than 14 days of LSC-driven launch delays (per schedule as of PSR).

Performance: No more than 3 validated complaints from the cognizant flight safety office. No more than 3 validated complaints from the launch range ground safety office. No more than 3 validated complaints by the payload provider.

Performance: Insertion of payload(s) into designated trajectory within tolerances specified in the MRD.

Entry: <3 findings of non-readiness against the TRR entry criteria as determined by the COR, corrected in one cycle.

Exit: <3 liens against the TRR exit criteria as determined by the COR.

Entry: <2 findings of non-readiness against the QTR entry criteria as determined by the COR, corrected in one cycle.

Exit: <2 liens against the QTR exit criteria as determined by the COR.

Entry: <3 findings of non-readiness against the PR entry criteria as determined by the COR, corrected in one cycle.

Exit: <3 liens against the PR exit criteria as determined by the COR.

Performance: No more than 10 validated complaints from the MAC or IRRT with respect to MA support.

Schedule: QTR should be held no later than 60 days prior to PSR (approximately T-5 months to launch) or as determined by the COR.

Schedule: Completion of the PR prior to PSR.

Table 1 - Service Summary Note: PCO is the unilateral authority for validation of complaints discussed above.

DOCUMENTS

3.1 Reference Documents:

The following documents are to be considered as reference material for the purpose of interpreting the requirements of this PWS but are not contractual documents.