Attachment_3_ASLON_SRP-O_Cat_1_PWS_RFI_Final.docx

FA8818-18-R-0011

PERFORMANCE-BASED WORK STATEMENT (PWS)

FOR

SMALL ROCKET PROGRAM-ORBITAL (SRP-O)

Mission: Agile Small Launch Operational Normalizer (ASLON)-45

Category 1 Mission Assurance

DD MMM YYYY

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 1, mission in support of the Small Rocket Program-Orbital (SRP-O) ASLON-45 contract. 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 propulsion systems to meet a variety of mission and payload requirements. The specific mission objectives, satellite mission information, launch history requirements, and launch solution constraints are defined in the attached ASLON-45 Mission Requirements Document (MRD), at Appendix A.

General Description of Services: SMC requires launch services composed of design, integration, test, and launch activities as defined in this PWS and the 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 LV(s), all required LV support, integration of the LV with the payloads, and provision of launch facilities.

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. 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 remedy deficiencies 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: The LSC shall obtain range authority to connect approval (s) for all commercial information systems planned to support the launch.

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 classified 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. [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 the 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 group 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)

· 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): Not required.

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. The launch schedule will be driven by SMC/LEX and any payload manifesting shall be approved by 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/Launch Site (ILS)/Range. The LV to ILS/Range ICD shall include a description of the telemetry data to be displayed on range consoles. [CDRL A004] 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 A021] 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 to demonstrate a full mission design that the 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 PWS and MRD.

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.

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 shall provide flight representative hardware to support the fit check. The fit check shall be performed at the LSC facility.

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.

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 PWS and MRD 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 14 CFR Part 417 (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 LSC is responsible for obtaining approval for range safety tailoring. 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 14 CFR Part 417 (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 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 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. [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 MRD. 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 MRD.

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 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: An integrated field processing procedure shall 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. During payload mating, the Payload Contractor will furnish certified handling/GSE required to interface from the crane hook (or other GSE) to the payload, as required during the integration process. 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.

LV/Payload Integrated Processing: Integrated LV/payload processing shall be performed in preparation for payload emplacement on the LV at the ILS. The LSC shall accommodate the payload GSE at the ILS. 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.

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 shall 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 mission simulations and dress rehearsals in accordance with their proposed approach. 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. At Government ranges, the LSC shall provide requirements for range and downrange telemetry collection via the UDS process. [CDRL A016] Day of Launch: The LSC shall be responsible for Day of Launch operations and the final readiness decision for the combined LV/payload system. The LSC shall accommodate a small contingent of Government personnel to monitor launch operations for Government insight. The Government will not have a Mission Director or have an approval role in the launch decision.

The LSC shall accommodate payload personnel on console. The LSC shall not launch if the payload lead informs the LSC of non-readiness to launch during the final poll for launch readiness.

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) [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. Analysis 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 FAA license procedures. 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 proposed internal processes and procedures. The mission is not subject to the SMC flight worthiness certification process or MAC IV&V activities, but will rather 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 ILS meets FAA licensing requirements and any activities required to bring the ILS 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 paragraph 1.8. Failure to obtain applicable licenses shall not relieve the LSC from its responsibilities under this contract. See Annex 1 for additional analyses required for Category 1 missions. [CDRL A010] 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.

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

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

Schedule: This review shall be completed no more than 120 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: Secure all required FAA license(s) prior to PSR.

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.

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

DOCUMENTS

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.

Compliance Documents: All launch related services require compliance with the governing regulations and laws affecting the procurement and execution of launch services. Compliance with the following is mandatory.

Annex 1: Mission Assurance Category - Specific Mission Analysis Requirements A1-1 Category 1 Analyses The LSC obtains license to launch through the Federal Aviation Administration and may be required to obtain launch vehicle frequency clearance from the Federal Communications Commission. The LSC shall submit a copy of the approved license and all supporting documentation. The following analyses shall be conducted to support payload integration.

Payload Integration Analyses A A1-1.1 Payload Trajectory and Performance Analysis [A015] A1-1.2 RF Analysis (including intermod analysis) [A015] A1-1.3 Antenna Patterns and Link Analyses [A015]

Annex 2: Performance Threshold Entrance and Exit Criteria The following are the entrance and exit criteria for:

· Service Requirements and Concept Review (SRCR)

· Mission Design Review (MDR)

· Pedigree Review (PR)

· Pre-Ship Readiness Review (PSR)

SRCR:

Entrance Criteria

1. Coordinated and signature ready System Performance Specification (PWS 1.10.1.3) (Updates as necessary for subsequent reviews)

Final Rev: SRCR

Rev: SRCR

6. Draft SRCR briefing chart package, Design Review Information Package (DRIP) review charts that include (PWS 1.4.1):

a. Overview of the proposed Mission concept

b. Proposed LV design

c. Assessment of compliance with requirements

d. Current integrated schedule and critical path

e. Planned trade studies

f. Proposed plan for submittal of all required contract deliverables including projected submittal dates

g. Initial risk assessment and mitigation plan presented (including first flight items)

h. Proposed logistics concept

i. Safety program

j. Proposed plan for compliance with Range Interface and Range Safety requirements

k. Schedule and status of all range documents

l. Path ahead to MDR outlined

Rev: SRCR-5d

Exit Criteria

MDR:

1. All liens and action items from SRCR completed and closed out

Signed: MDR+30

9. FCC license package complete with all attachments

Final: MDR+10d

Final: Haz Ops-30d

Final: Test-7d

13. Draft MDR briefing chart package, Design Review Information Package (DRIP) review charts that include (PWS 1.4.1):

a. Final trade study results

b. Current integrated schedule and critical path

c. Proposed plan for submittal of all required contract deliverables including projected submittal dates

d. Planned and completed qualification and acceptance testing

e. Updated risk and opportunity assessment and mitigation

f. Status of long lead items and critical spares procurement

g. All system safety and range safety issues addressed and status of documents briefed

h. Proposed plan for compliance with Range Interface and Range Safety requirements

i. Path ahead to PSR outlined

Rev MDR-5d

PR:

Entrance Criteria (documentation for each of the following is provided for review)

1. Acceptance testing of subassemblies and/or components (PWS 1.10.1.5.5)

2. Factory system level testing including payload integration tests

3. Documentation that all LV and GSE systems have been fabricated and assembled as designed, including documentation of rationale for deltas

4. Mechanical top assembly drawings, with parts list and sub-tier drawings necessary to locate all major units on the vehicle, including mounting configuration (hard mounted or on isolators)

5. Component qualification matrix with the test spectra and levels (thermal cycle, vacuum/thermal vacuum, random vibration, sine vibration, shock, and EMI) to which each component has been qualified

6. Qualification and Acceptance test data and reports including lot qualification data on ordnance

7. Component service life data and manufacturing dates on ordnance and other limited life items are documented and within service life

8. Qualification by similarity analyses and reports

9. Documentation/analyses used as basis for qualification and acceptance test levels

10. All Discrepancy Reports (DRs) and referenced documents as well as a complete summary listing. A reduced set of DRs, deemed engineering significant by the review team, may be requested after review of the DR list and description

11. Documentation of concurrence/approval on all DRs

12. Documentation of concurrence/approval on all waivers and deviations including a summary listing

13. Copies of waivers granted to the system, or in-process

14. GIDEP alerts and other advisories and how they were addressed

15. Current ICDs and signed off documentation

16. Documentation of Software development and mission specific software test and qualification

17. LSC’s qualification, acceptance, and non-complying product process documentation, including acceptance test reports for all LSC fabricated and vendor supplied components (mechanical and electrical, software if applicable) and subassemblies

18. Acceptance level test results

19. System level test results

20. Build paperwork and travelers

21. Limited-life items documentation of service life

22. Documentation of Fatigue analysis showing component fatigue life remaining after exposure to environmental tests

23. Critical connections list showing all connections that cannot be tested after final mating

24. Launch system electrical interconnect drawing(s), including Cable Layout Drawings showing proper routing of all cables

PSR:

1. All action items / liens from MDR closed

3. All hardware to be shipped has been verified available and mission ready

4. All field processing procedures released (PWS 1.8.10.9.1)

9. FAA License(s) Approved (PWS 1.9)

10. FCC License(s) Approved

11. All Radio Frequency (RF) documents approved

12. For any open non-compliances, closure dates identified and approved to proceed with shipment to the field

13. Path ahead to ILC outlined

14. Draft PSR briefing chart package (PWS 1.4.1)

a. Mission specific requirements and analyses reviewed

b. Final Compliance Verification Matrices reviewed

c. Hardware qualification and acceptance testing completed and reviewed

d. System Testing complete and reviewed

e. Flight software testing completed

f. Risk mitigation status reviewed

g. Status of range safety approvals reviewed

h. Documentation of Range readiness reviewed

i. All licensing approved (exceptions noted – to be carried as risks)

j. Launch Campaign Concept of Operations (CONOPS) reviewed

k. Launch Campaign daily schedule reviewed

Rev PSR-5d

Appendix A: Mission Requirements Document

AGILE SMALL LAUNCH OPERATIONAL NORMALIZER (ASLON)-45

Mission Requirements Document (MRD) FA8818-17-C-000x

Basic: DD MMM YYYY

REVISION HISTORY

1.1.1.1

1.0 INTRODUCTION

1.1 OVERVIEW: This document provides the launch mission requirements for the “ASLON-45” Orbital mission, which will be launched under a Small Rocket Program-Orbital (SRP-O) contract.

The goals of the “ASLON-45” mission are to launch an orbital demonstration mission to deliver a 39 kg spacecraft to a 550 km orbit.

The mission responsibility of the Launch Services Contractor (LSC) will end when Space Vehicle (SV) has been deployed.

“ASLON-45” is a Mission Assurance Category 1 mission.

“ASLON-45” is a class D payload.

1.2 SCOPE: This Mission Requirements Document (MRD) is the controlling source and authority for the mission requirements. In addition to specifying mission requirements, this MRD will:

Identify roles and responsibilities and interfaces among the various contractors and Government agencies supporting the mission.

Document data provided by the agencies furnishing the SV to be used by the LSC in developing the Launch Solution (LS) configuration, integrating the SV, processing the flight hardware, and conducting the mission.

Identify constraints and environments required by the SV.

Identify test-and-analysis requirements to verify interfaces between the SV and LS and to verify required SV characteristics.

This MRD will be maintained by the USAF SMC/LEX (RSLP) office. In many cases, the detailed requirements and data will be specified in other documentation, which will be referenced herein. This includes documents such as the SRP-O Performance Work Statement (PWS) and the LS/SV Interface Control Document (ICD), which identifies detailed SV interface requirements and the range requirements documentation developed in accordance with the Universal Documentation System (UDS).

1.3 ROLES AND RESPONSIBILITIES: The roles and responsibilities of the agencies and contractors that will support the mission are described below:

1.3.1 Payload Program Office (PPO): The PPO provides the SV. PPO’s activities and responsibilities include:

Participation in program management Provision of SV range-safety documentation at the request of the USAF Shipping the SV to the launch site

1.3.2 LEX: The RSLP branch (LEX) of the USAF’s Launch Enterprise Directorate (USAF/SMC/LE), located at Kirtland AFB, NM, is responsible for SRP-O launch systems and launch operations. Its activities and responsibilities include:

Participation in program management (lead for launch segment) Range support LS integration SV interface and mating

1.3.3 Mission Assurance Contractor (MAC): A mission assurance contractor, under contract to the LEX, shall provide Mission Assurance and Independent Verification and Validation support for the LS. Higher-level risks identified by the MAC will be sent to PPO in monthly status updates provided by the Mission Manager (MM), and overall risk assessments of the program will be addressed in design reviews and readiness reviews.

1.3.4 LSC: The launch-services contractor executing the mission on this MRD.

The LSC shall ensure that Associate Contractor Agreements are completed for the following associate contractors:

METIS contractor Arctic Slope Federal Space and Federal Linquist Tecolote Research, Inc.

If necessary, the LSC shall also ensure that Non-Disclosure Agreements are completed for the above contractors.

1.4 Additional Performance Work Statement Requirements and Exceptions

1.4.1 Payload Integration: LSC shall provide any required deployment mechanisms and/or payload adaptors, and shall physically integrate the SV(s) into a consolidated payload stack.

1.4.2 Onsite Representative: This mission does not require accommodation for an on-site representative at the LSC facility.

2.0 Mission Requirements

Mission Scenario: The launch will be conducted from an east coast launch site.

2.1 Launch Solution Constraints

2.1.1 Configuration: The final launch configuration will be LSC proposed, the government has not identified constraints on allowed configurations.

2.1.2 Rideshare/Dedicated Launch/Multiple Launch: This mission requires a dedicated launch solution, a rideshare proposal is not acceptable due to SV customer requirements. The launch solution may be further segregated into multiple launches, there is no requirement for the SVs to launch together.

2.2 Launch Conditions

2.2.1 Position: LSC Proposed

2.2.2 Environmental Control: The LSC shall ensure the motors used are maintained within environmental limits in accordance with Air Force Technical Order (TO) specifications for motor exposure. (Applies to GFP motors only)

2.2.3 Date/Time: The SV(s) mission is scheduled for June Fiscal Year 2021 (FY21).

2.2.4 Range Coordination: All test operations at the range will be conducted in accordance with an approved Operations Requirement (OR) for the mission (to be published), and applicable range documents.

2.3 Orbit Requirements

2.3.1 Profile: The mission flight profile will be a 45 (+17/-10) degree inclination TBD km (apogee) by TBD km (perigee) orbit, with an altitude of 550 (+/-50) km. There are no constraints on the Right Ascension of the Ascending Node (RAAN). The flight profile is Unclassified.

2.3.2 Insertion Accuracy (3-Sigma): The maximum dispersions of the payload orbit after deployment shall be within TBD NMI altitude for insertion apse, TBD NMI non-insertion apse, and 45 degree inclination.

2.3.3 Attitude Control (3-Sigma): The LS shall control its attitude at the time of payload deployment to ±1º of the desired attitude with drift rates ≤ 1 º/sec about each axis

2.3.4 Collision/Contamination Avoidance Maneuver: The LS shall perform C/CAM as necessary to minimize payload contamination and preclude re-contact between the deployed payloads or other objects and any LS hardware.

2.4 Measurements: Status consisting of guidance, GPS and attitude data, environmental data (to include thermocouple data), and housekeeping functions shall be measured via telemetry. The LS position, velocity, and attitude shall be measured on-board throughout the flight via the LS inertial measurement unit (IMU) and shall be displayed real-time at the range via LS TM.

2.4.1 Data Handling/Distribution: Handling and distribution of telemetry data will be as described in the OR.

2.4.2 Post processed Trajectory Measurements: Kinematic Instrumentation: Instrumentation to provide accurate reporting of the position, velocity, and acceleration, of the payload are required. Acceptable tolerances on this instrumentation are 1.0 m per axis in position, 1.0 m/sec per axis in velocity, and 1.0 m/sec2 per axis in acceleration. Acceptable tolerance for post launch pointing data is 2.5 degrees per axis. This data required at a data rate of 50 Hz or better.

2.5 Payload Characteristics

2.5.1 SV Envelope

TBD length, TBD width, and TBD height xx” dia

2.5.2 SV Mass Properties

Weight: 39 kg.

Center of Gravity: X: TBD Y: TBD Z: TBD

2.5.3 Environments: The design shall include definition of the following payload flight environments: Acoustic, Shock, Random and/or sine vibration, Transient loads, and Steady state acceleration These environments shall be documented in the LS /SV ICD

2.5.4 Payload Access: The LS shall provide access to the payload after fairing encapsulation without removing the fairing or breaking electrical connections. Fairing access shall support conditioned air and / or gaseous nitrogen purge of the fairing volume during ground operations and prior to launch.