Draft RSLP MA PWS.docx

FA8818-18-R-0003

Attachment 1

Performance-Based Work Statement (PWS) for

Rocket Systems Launch Program (RSLP) Mission Assurance (MA)

13 March 2020

Table of Contents

General Scope of the Contract:

This contract will provide services necessary to perform Mission Assurance (MA) services which include systems engineering, risk management, technical analysis, Independent Verification and Validation (IV&V), and quality assurance for Rocket Systems Launch Program (RSLP) Launch Missions and planning and analysis for logistics concerns such as motor/component sustainment, Aging Surveillance (AS), motor refurbishment, booster build, booster test, transportation/handling, and system integration. MA services include sustainment engineering and IV&V functions in all relevant engineering disciplines. These may include control systems, aerodynamics, aerothermal modeling, structural analysis, propulsion systems (solid, liquid, and hybrid), electrical, and software engineering.

RSLP was established through a Secretary of Defense memorandum to the Secretary of Air Force, dated 21 Aug 72. RSLP has current authorization under Program Exhibit R-2, Element PE# 65860F. RSLP provides mission planning, payload integration, vehicle acquisition, processing, launch operations, booster storage and disposition, AS, maintenance and logistics support for selected Department of Defense (DoD) Research, Development, Test and Evaluation (RDT&E) launches. Past RSLP customers include the Air Force, Navy, Army, Missile Defense Agency (MDA), Defense Advanced Research Project Agency (DARPA), and National Reconnaissance Office (NRO). RSLP maintains exclusive control of deactivated Minuteman (MM) and Peacekeeper (PK) assets used in test to include refurbishment, transportation and handling, storage, and launch services.

This Performance Work Statement (PWS) delineates tasks the Mission Assurance Contractor (MAC) is required to perform in support of the Space and Missile Systems Center (SMC), Small Launch and Targets Division (ECLX), which executes the RSLP program of record.

Contractor Responsibility – In accordance with AFFARS 5309.103, The Air Force Space Contractor Responsibility Watch List (CRWL) is applicable. The Contractors may be placed on the CRWL when their ability to successfully perform space program contracts is uncertain due to any of the following:

· Poor performance or award fee scores below 50%.

· Financial concerns.

· Felony convictions or civil judgements.

· Security or foreign ownership and control issues.

Contractual Direction – Contractual direction is provided by the Procuring Contracting Officer (PCO), SMC/PKT, at Kirtland Air Force Base, New Mexico. The PCO will name a Contracting Officer’s Representative (COR) who will act as the primary interface with the MAC for day-to-day interactions and conduct Quality Assurance Surveillance on behalf of the PCO.

Technical Direction – Technical direction under this contract may be given to the contractor by the Government representatives as appointed by the Contracting Officer (CO). The Government representative appointed by the CO will be the Task Order (TO) Manager identified in each Task Order. Technical direction is defined as that process by which the contractor receives guidance, instruction or contract clarification as it relates to an element of work solely within the existing requirements of the PWS. The CO is the only individual authorized to modify, in any way, the terms of the contract. Such changes of terms shall be accompanied by issuance of a modification to the contract signed by the CO.

Applicable Documents:

Compliance Documents:

Services provided must be performed in compliance with the following documents. If required, Air Force Technical Orders will be made available upon request.

Reference Documents:

The following documents provide additional information for reference use in providing services:

Requirements:

General Requirements:

Technical Expertise and Guidance - This effort provides technical expertise and guidance as requested by RSLP for all task orders issued under this contact. Each TO will cite specific CLINs under which the work will be performed and the period of performance for the effort. No work shall be initiated in performance of this contract without prior written approval from the PCO.

New Work - The PCO shall be notified, in writing, if there is work required beyond the scope of the contract or if there are any problems in meeting contract requirements as soon as the problems are known. The PCO is the only person authorized to change the terms and conditions of the contract. All technical and management interchange between RSLP and MAC personnel shall be conducted subject to this condition.

Contractor Identification - MAC personnel and their subcontractors must identify themselves as contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract. In addition, contractor occupied facilities on Government installations such as offices, separate rooms, or cubicles must be clearly identified with signs, name plates, or other identification, showing that these are work areas for contractor or subcontractor personnel.

Non-Personal Services - The RSLP will neither supervise MAC employees nor control the method by which the MAC performs the required tasks. Under no circumstances will the RSLP assign tasks to, or prepare work schedules for, individual MAC employees. The MAC will manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services. If the MAC believes that any actions constitute, or are perceived to constitute personal services, it shall be the MAC's responsibility to notify the PCO immediately.

Security Clearance - Facility security clearance in accordance with the classification levels identified in the DD254 is required prior to performing work required by this contract. The MAC may be required to provide secure storage for some SECRET/NOFORN materials (i.e., Flight computer components and up to 500 pages of documents). Access to TS/SCI/SAF data, if required, will occur only at Government locations. Technical support for DXBM and launch missions as well as IV&V on Launch Vehicles and Launch Vehicle to Payload integration and encapsulation shall be performed by MAC personnel who are cleared at the proper level. This may require clearance at up to the TS/SCI level for missions involving TS/SCI classified payloads. Access to the Secret Internet Protocol Router Network (SIPRNet) and the Joint Worldwide Intelligence Communications System (JWICS) is required. Failure to provide MAC personnel with the appropriate clearance, access, and expertise will not relieve the MAC from responsibilities under this contract. Specific Security requirements for individual Task Orders will be specified in the TOID.

The MAC shall comply with DFAR Clauses related to the Disclosure of Information (DFAR 252.204-7000), Safeguarding Covered Defense Information and Cyber Incident Report (DFARS 252.204-7012 and DFAR Subpart 204.73) for the protection of unclassified controlled technical information (UCTI).

In line with this clause, NIST SP 800-171 provides guidance for the protection of Controlled Unclassified Information (CUI) on non-federal information systems. The MAC shall apply security controls contained in NIST SP 800-171 for the protection of CUI on non-DoD information systems. CUI information will not be placed on publicly accessible web sites. Public release requires a security and policy review of all official, and some unofficial, DoD information intended for release to the public when that information is about military matters, national security issues, or subjects of significant concern to DoD or Air Force (AF). All unclassified information, such as papers, presentations, videos, images and news releases, must be reviewed and approved by the DoD prior to any public release. Any and all release requests will be requested by the MAC through the PCO. The MAC shall comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, DoDM 5200.01, Volume 4, DoD Information Security Program and AFI 33-332, Privacy Act Program requirements, and the information safeguards as required in DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting and safeguarding FOUO and CUI material.

No personal computers, Personal Electronic Devices (PEDs), Cell phones, tablets or other electronic devices shall be used to receive, generate, or process US Government information belonging to, generated for, or otherwise delivered to or incorporated into the RSLP (e.g. a personal computer connected to the contractor’s internal WAN or LAN may not be used to receive or process e-mail related to the RSLP).

Travel Requirements - MAC employees may be required to travel to various locations both inside and outside the continental United States in performance of requirements. MAC employees shall coordinate TO-related travel with the TO Manager for the relevant TO. RSLP currently has contracts which may require MA support at the locations show below. RSLP may identify additional locations in individual TOs. Travel to additional locations for meetings may also be required.

· Vandenberg Air Force Base Vandenberg AFB, CA

· Missile Defense Integration and Operations Center Schriever AFB, CO

· Pacific Spaceport Complex - Alaska Kodiak, AK

· Missile Defense Agency Kirtland AFB, NM

· 45th Space Wing Patrick AFB, FL

· Northrop Grumman Space Systems Chandler, AZ

· Wallops Flight Facility Wallops Island, VA

· Space Vector Corporation Chatsworth, CA

· Cecil Spaceport Jacksonville, FL

· Kratos Glen Burnie, MD

· Wake Island Missile Launch Facility Wake Island

· Reagan Test Site Kwajalein Atoll, Republic of Marshall Islands

· Yuma Proving Grounds Yuma, AZ

· United Launch Alliance (ULA Centennial, CO

· Pacific Missile Range Facility Kekaha, HI

· VOX Space Long Beach, CA

· White Sands Missile Range (WSMR)

WSMR, NM

· SpaceX Hawthorne, CA

· Aerojet Rocketdyne Coleman Aerospace Cape Canaveral Air Force Station, FL

· Aerojet Rocketdyne Rancho Cordova, CA

· Rocket Lab Long Beach, CA

· Aevum Inc Huntsville, AL

· X-Bow Launch Systems Inc.

Huntsville, AL

· 309th Missile Maintenance Group Hill AFB, UT

· Firefly Black LLC (Firefly Aerospace) Cedar Park, TX

· Northrop Grumman Space Systems Magna, UT 84044

· Astra Space Inc El Segundo, CA

· Utah Test and Training Range (UTTR) Hill AFB, UT

· Coleman Aerospace Orlando, FL

· Arizona Army National Guard Camp Navajo, AZ

· Pacific Scientific Energetic Materials (PacSci) Hollister, CA

· Air Force Nuclear Weapons Center Hill AFB, UT

Environmental Compliance - Perform tasks required for this effort in compliance with federal/state/local environmental laws and Air Force environmental policies and regulations. Conduct tasks in compliance with federal/state/local environmental laws and Air Force environmental policies and regulations, including information needed for preparation of Hazardous Materials Management Program (HMMP) Reports IAW National Aerospace Standard (NAS) 411.

Direction from/to Contractor - Cooperation with the Government, Federally Funded Research and Development Center (FFRDC), other systems engineering and technical assistance (SETA), and contractors, subcontractors, and vendors is essential to successful execution of the requirements for this effort. The RSLP TO Manager (also referred to as Mission Manager, Logistics Manager or Program Manager) is the single face to other Government agencies, the FFRDC, other SETAs and program contractors. The MAC shall not provide technical direction to these groups. The PCO may provide direction to the MAC. The TO Manager identified on each TO or may provide day-to-day tasking prioritization for the MAC. Other Government employees may not provide direction or tasking prioritization unless specifically authorized by the PCO.

Core Effort:

Core Effort will cover all Program Management activities required for the basic management of this IDIQ contract and is not expected to fluctuate significantly based on the number or type of active TOs.

Program Manager - Identify a single POC to the RSLP who will be responsible for supporting the overall contract effort, and the core staff responsible for the execution and maintenance of the overall IDIQ effort.

Key Personnel – The contractor shall ensure that the following key personnel are available to support the RSLP MA effort:

Note: Table listing key personnel by title and qualifications from contractor’s proposal will be inserted here prior to contract award.

Meetings - Facilitate and prepare support materials prior to meetings held in MAC or other facilities. Provide the RSLP with copies of all materials developed or planned for presentation by the MAC prior to any meeting. When changes are required final copies of materials will be provided. (CDRL A001) Review materials prepared by others as “read-ahead” information and provide technical evaluation to the RSLP prior to meeting. Provide RSLP with technical review of information presented by others at meetings.

Planning Support – Provide management, engineering, and Subject Matter Expert (reach-back) support to RSLP planning activities related to the determination of feasibility, requirements, early integration or other support necessary for RSLP to execute planning activities related to new or modified work.

Non-Disclosure Agreements and Associate Contractor Agreements - The MAC is responsible for obtaining all non-disclosure agreements with all applicable corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of any TO.

Associate Contractor Agreements (ACA) are required 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. Associate contractors will be listed in each Task Order Information Document (TOID). ACAs shall include the following general information -

· Identify the associate contractors and their relationships

· Identify the program involved, the relevant Government contracts, and the associate contractors role

· 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 each such agreement shall be provided to the PCO.

The MAC 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 task orders issued under this contract. The Government will update the TO and notify the MAC when an associate contractor is succeeded by a new contractor.

Security Threat Reporting - The MAC must report to an appropriate authority any information or circumstances of which they are aware that may pose a threat to the security of DoD personnel, contractor personnel, resources and classified or unclassified defense information. MAC and subcontractor employees shall be briefed by their immediate supervisor upon initial assignment.

Employee List - Maintain a current listing of employees. The list shall include the employee's name, social security number, and level of security clearance. The list shall be validated and signed by the company Facility Security Officer, and the Sponsoring Agency’s Security Manager. An updated listing must be provided to the PCO when an employee's status or information changes and upon request.

Training Management Implement and administer a training program to ensure MAC personnel are qualified to perform the work required by the contract, and to perform work at the required facilities. Maintain training records on MAC employees. The MAC will include a clause in all subcontracts requiring subcontractors to comply with this provision of this contract.

Safety Requirements Compliance with applicable Occupational Safety and Health Act (OSHA) standards, as well as all Federal, State and Local laws and policies concerning safety, will be mandatory for this contract. In the absence of an applicable OSHA Standard, AFI 91-203, Air Force Consolidated Occupational Safety Instruction or applicable nationally recognized sources of safety, health, and fire prevention standards reference will be followed for work performed under this contract. The MAC is responsible for reporting injuries and illnesses to the appropriate authority Protect Government property to prevent damage during the period of time the property is under the care, custody, or control of the MAC.

Include a clause in all subcontracts requiring subcontractors to comply with the safety provisions of this contract.

Provide occupational safety, health and fire protection guidance in procedures and technical data produced under this contract. Specify all detailed operations including proper safety, health, and fire prevention procedures and proper use of personal protective equipment to adequately protect the worker. When reviewing documents produced by others, identify any deficiencies in occupational safety, health and fire protection guidance.

Comply with all safety provisions, (e.g. technical specifications, technical publications, etc.,) referenced in the work requirements of this contract.

Report immediately any potential hazard which may result in any one or more of the following: fatalities, disabling injuries, damaging Government property, affecting program planning or production schedules, or degrading the safety of Government Furnished Property (GFP).

Accident/Incident Reporting and Investigation The MAC shall report to the PCO all available facts relating to each instance of damage to Government property within 24 hours of occurrence.

Immediately secure, if appropriate, the accident scene or damaged item when a potential major mishap ($10,000 or more) involving Government property occurs. Maintain security until released by the accident investigation authority or designated by the Government safety office through the PCO.

Cooperate fully and assist Government personnel when the Government elects to conduct an investigation of the accident.

Include a clause in each applicable subcontract to require the subcontractor’s cooperation and assistance in accident reporting and investigation.

Immediately comply with required toxicology testing and provide required medical information/records to the Medical Officer in the event of an Air Force mishap.

Report to the PCO any injury or occupational illness to MAC personnel or damage to MAC property when caused by DoD operations, as outlined in AFI 91-204, within 24 hours of occurrence.

Special Requirements Procurement - Upon Government approval, procure minor items not available from the Standard Base Supply System to support RSLP activities.

Digitize and index existing RSLP owned records and documentation as specified in the TOID.

Government Furnished Property (GFP) Reporting – Maintain a current list of GFP and CAP pertinent to this contract. Serially managed items will be identified by the PCO. (CDRL A002) Reporting - Status Reporting - Provide a monthly status of all work performed on this contract. The report will be organized by TO and will include major accomplishments, meeting supported, major planned activities, anticipated workload issues, cost and schedule performance, working documents generated, and identification of mission assurance “gaps.” (CDRL A003) Program Management Reviews (PMR) – Conduct semi-annual (twice per year) PMRs to the RSLP Mission Manager and Leadership covering the financial, schedule, and technical elements of all TOs, with the exception of the technical elements of mission support work performed under paragraph 3.3.1 through 3.3.3. (These need not be discussed at PMRs since this work includes its own reporting requirements.) (CDRL A001) Manpower Reporting - Report all MAC labor hours (including subcontractor labor hours) required for performance of services provided under this contract via the secure data collection site (i.e. Contract Manpower Reporting Application). The MAC is required to completely fill in all required data fields using the following web address http://www.ecmra.mil.

Cost Management – For each TO, manage and provide budgetary information (including labor and other directs costs including travel), track actual costs, forecast planned expenditures and provide comparison of actual vs planned expenditures. (CDRL A004) Program Management Plan (PMP) - Develop and execute a plan which is consistent with and incorporates all contractor-proposed resources, processes, and methodologies. The PMP shall include coordination, integration, planning, and execution of activities with other involved parties, including customers, to minimize mission disruption and ensure mission success. (CDRL A005)

· Conduct and document long-range planning activities to analyze requirements and identify new capabilities required to support current and future programs.

· Analyze the scope of new work or extended work and verify current capability and capacity to accept or retain the work. Provide recommendations to the RSLP on the feasibility of supporting new missions.

· Track resources used for on-going efforts and forecast resources needed for projected efforts. Identify any gaps in resource availability.

· Identify any organizational conflict of interest associated with support of this contract or with supporting new requirements.

· Update this PMP to reflect any added, changed, or removed work on any Task Order.

Subcontract Management - The MAC is responsible for all subcontract management necessary to support work performed on this contract, and is responsible and accountable for subcontractor performance. The MAC shall manage work distribution to ensure there are no Organizational Conflict of Interest (OCI) considerations. Contractors may add subcontractors to their team after notification to the PCO or the Contracting Officer’s Representative (COR). Notification is also required when the MAC changes subcontractors on any TO requiring deliverables, or after a Concept Analysis has begun (i.e. changing subcontractors during a Concept Analysis). Report on subcontractor participation annually. (CDRL A006) Lessons Learned - Provide input into the RSLP lessons learned database for all MA efforts.

Incoming Transition – At the beginning of contract performance, ensure appropriate personnel are in place to receive technical documentation and status information provided by the outgoing MAC, Government personnel, and others to accept accountability for the contracted effort.

Mission Support:

Plan and execute IV&V services in the following areas for each mission as specified by the TOID.

The nature of the support required by this effort is highly technical requiring engineering assessments of products or services as well as providing technical advice and support to the RSLP Mission Manager. As such, the MAC will ensure that the individuals providing these services are adequately trained in their discipline, able to independently evaluate the work of others and able to effectively communicate their technical evaluation or advice.

For the purposes of this Mission Support section, the terms “TO Manager” or “Mission Manager” or “Program Manager” refer to the Government person appointed by the RSLP and the PCO to manage a particular TO. The TO Manager will be identified in the TOID. In the event of a change, the PCO will notify the MAC.

The MAC will identify a single POC for each mission support task order. This POC will be the individual responsible for ensuring the requirements of the task order are met. This individual will act as the primary interface between the MAC and the RSLP Mission Manager.

Unless an alternative requirement for data delivery is given, for all tasks under this section, provide status and findings by email upon task completion, occurrence significant event(s), or upon request. These emails will discuss the major elements of each task and include pertinent results, issues, concerns, and courses of action. Attach briefing materials, technical or other related data. The e-mail subject line will be “TO #XXXX:” followed by the main PWS paragraph related to the task and a brief subject description. Address email to the Mission or Task Order Manager identified in the TO and copy the COR. The MAC will also archive a .pdf version of the message and attachments in the Government NIPRNet location specified in the TO. This archive file and folder will be named with the date (YYYYMMDD) followed by the subject line and an optional sequential number to differentiate between multiple emails on the same topic sent on the same day.

Each mission TOID will designate the mission as either MA category (1-3) or “Construct 2.” (Note: The scope of work for MA CAT 1-3 below uses similar numbering to facilitate understanding of the difference in scope of service to be provided by the MAC for each category. “Construct 2” uses stand-alone numbering.)

The requirements for each designation are as follows:

Category (CAT) 1 MA – This service provides technical advisory support for missions with a high risk tolerance. IV&V support will be focused on areas of elevated risk. The IV&V service will primarily assess the MA processes and documentation used by the Launch Service Contractor (LSC). CAT 1 MA missions may fly with an FAA license. In addition to or in place of the FAA license, some or all elements of the SMC Spaceflight Worthiness Criteria (SFWC) may be levied as mission requirements.

Mission Development:

Assess and provide input to mission requirements development with the launch service and payload stakeholders prior to award. Provide input to, and evaluate the design of the mission profile and assist with the development of technical documents related to the launch service procurement. Support the development of a Mission Requirements Document (MRD), or equivalent, and other related technical documents (e.g. Technical Requirements Document (TRD), PWS, Universal Documentation System (UDS), Analyses Requirements Document, and/or Interface Control Documents (ICDs)) capturing all requirements and conditions necessary for an LSC and other mission stakeholders to adequately understand mission requirements, organizational relationships and mission unique requirements.

IPT Support:

Attend weekly IPT meetings and provide the RSLP Mission Manager with status of IV&V activities as well as technical advice on mission stakeholder activities. Provide the Mission Manager with technical support to address mission-specific leadership concerns and issues. Assist with preparation of review materials and attend program reviews, up to one per month. This support may also include program status reviews to the Program Director, Program Manager, and Program Management Reviews (PMRs) to the stakeholders). Provide technical advice to the IPT’s Risk Management activity.

TIMs:

Attend Technical Interchange Meetings (TIM) with the LSC or mission stakeholders and provide technical advice on the issues discussed to the Mission Manager.

Engineering Reviews:

Attend Systems Engineering reviews presented by the LSC. Attend engineering reviews presented by other associated contractors and mission stakeholders. Provide technical advice on the issues discussed to the Mission Manager System Safety, Range Safety, and Environmental Health & Safety:

For missions using GFP Motors, provide support for range safety certification/tailoring of range safety flight termination and ordnance systems. This includes reviewing providing technical comments, and recommending updates to documentation related to flight termination and ordnance systems requiring certification/recertification and also to launch contractor flight termination systems requiring range safety certification/recertification. In addition, the MAC will provide technical support related to Environmental Health and Safety and support the Mission Manager at range safety flight termination system certification/recertification meetings.

Major Reviews:

Support the Mission Manager at major reviews presented by the LSC and provide technical advice regarding design issues, trades, decision points, and related technical topics. Advise the Mission Manager on major review entry/exit criteria compliance. Major reviews may include:

· Services Requirement Review (SRR)/ Service Requirements Concept Review (SRCR)

· Preliminary Design Review (PDR)/Mission Design Review 1 (MDR1)

· Critical Design Review (CDR)/Mission Design Review 2 (MDR2)

· Pre-Ship Readiness Review (PSRR) Interface Controls:

Provide the Mission Manager with technical advice on the development of a common Interface Control Document (ICD) between the LSC and other mission stakeholders. Review this ICD and the artifacts provided by the LSC and other mission stakeholders to verify adequacy Multi-Payload “Do-No-Harm” IV&V:

Does not apply to Cat 1 Schedule Support:

Does not apply to Cat 1 Procedure Oversight:

Oversight of the execution of LSC procedures is not required for CAT 1 missions unless otherwise specified in the TOID.

Test Documentation Review:

Does not apply to Cat 1 Developmental, Qualification, and Acceptance Test Review:

Does not apply to Cat 1 RSLP Equipment Interfaces and Operation:

When required, provide input to develop and/or revise the integration of RSLP equipment with equipment available from other agencies or host areas. The MAC may be responsible for operation of RSLP equipment and delivery of data. This may include the RSLP Telemetry Processing System (RTPS).

Pedigree Review:

For Launch Vehicle (LV) components or subsystems with elevated technical risk, review and evaluate the LSC’s launch system pedigree, design qualification, qualification testing, and flight item acceptance testing processes for compliance with SMC-S-016 or other appropriate standard. Advise the RSLP Mission Manager on risk and risk mitigations.

Review Government Industry Data Exchange Program (GIDEP) and sibling alerts for applicability to the mission LV systems and advise the RSLP Mission Manager of any concerns.

System Level Test:

Observe system-level factory testing and launch site testing of the LV and advise the RSLP Mission Manager on test sufficiency and anomaly resolution.

Guidance Navigation and Control (GNC) IV&V:

Does not apply to Cat 1 Software IV&V:

Does not apply to Cat 1 Avionics IV&V:

Does not apply to Cat 1 Fluid Mechanics IV&V:

Does not apply to Cat 1 Structures and Dynamics IV&V:

Does not apply to Cat 1 Propulsion and Ordnance Systems IV&V:

For launches incorporating RSLP motors or hardware as GFP:

Support the Government in the development of new designs using GFP hardware and in developing responses to requests for information regarding GFP motors and support equipment.

Provide engineering services, technical knowledge, and expertise to integrate GFP motors and equipment into the launch vehicle design and mission operations.

Provide input into GFP motor-related CONOPS development.

Provide technical support to ensure compliance with treaty requirements relevant to the GFP motor and the mission.

Conduct system safety assessments for GFP motors. (CDRL B001) GFP System Independent Analysis, Verification, & Validation. Assist the RSLP Mission Manager in completing the SMC Spaceflight Worthiness certification checklist for GFP motors.

Provide engineering review of ordnance contractor activities, in-plant practices and procedures, plans, specifications, test procedures, status reports and program documentation to evaluate compliance with technical guidelines and mission requirements. Provide technical recommendations for the preparation of the ordnance contractor Statements of Work.

Environments IV&V:

Does not apply to Cat 1 Ground Support Equipment (GSE) IV&V:

Does not apply to Cat 1 Mission Risk Identification and Assessment:

No formal independent MAC mission risk assessment is required for CAT 1 missions.

IV&V Reviews:

No formal IV&V reviews are required for CAT 1 missions Space Flight Worthiness Certification:

Typically, no formal performance certification is required for CAT 1 missions. If a specific element(s) of the SFWC certification is required this will be specified in the TOID.

Launch Campaign Support:

Participate in ground operations and day of launch working groups. Participate in integrated crew exercises, rehearsals, and launch operations. Advise the Mission Manager on issues related to launch readiness.

Post-Mission Support:

Provide technical review of post-mission reports provided by mission partners to the Mission Manager.

Identify lessons learned and provide inputs to the Mission Manager.

Attend post-mission review(s) held by LSC and other mission stakeholders to provide the Mission Manager with technical support and advice, inform lessons learned and possible anomaly/failure recommendations/resolutions.

When GFP motors are used, conduct a post-flight review assessing the flight performance of GFP motors. Archive this motor performance data for the AS program as described in section 3.4.2. Participate in Post Flight Reviews (PFR) and support disposition of any GFP motor observations or anomalies affecting the mission or future missions. In the event of a mission failure utilizing GFP boosters that results in an investigation, further MAC support will be obtained through an RFP and new contractual direction issued as needed. (CDRL B002, B003)

CAT 2 MA –

This service provides MA and IV&V support for missions where SMC will provide flightworthiness certification based on the SFWC (SMC-G-1202) requirements. In addition to the LSC’s MA processes, the Government requires significant IV&V to assess the launch system/service against SFWC in support of this certification. Although SMC can accept a high risk for these missions, typically medium to low risk is desired. The MAC will provide independent analysis, verification and validation of the design, development, production, testing and integration of the LV.

Many tasks in this section require the MAC to compare the results of their independent analysis with those of the LSC or other mission partner. In the event that these analyses yield significantly different results, the MAC will lead efforts to identify and resolve the discrepancy.

In addition to all CAT 1 MA requirements, CAT 2 MA includes the following additional requirements:

Mission Development:

Same as CAT 1 IPT support:

Same as CAT 1 TIMs:

Same as CAT 1, and also recommend and participate in TIMs with the LSC to identify specific items of concern indicated by IV&V results and resolve the source of discrepancies between LSC and IV&V analysis results.

Engineering Reviews:

Same as CAT 1, and also recommend and participate in engineering reviews with the LSC to resolve areas of broader concern and gain an understanding of LSC standards, processes and procedures. Advise the RSLP Mission Manager on technical adequacy of LSC standards, processes and procedures.

System Safety, Range Safety, and Environmental Health & Safety: Same as CAT 1, and also:

Provide Launch Vehicle subject matter expert support to the Mission Manager and System Safety Working Group. Support identification and evaluation of system safety hazards and associated mitigation analyses.

Review the LSC’s design for the LV and mission profile to ensure range safety compliance. Advise the Mission Manager on range safety design issues and support the range safety requirements tailoring activity to ensure compliance. Review LSC range safety waivers and advise the Mission Manager on the range safety waiver process and options for compliance.

Review LSC ground operations procedures and advise the Mission Manager on range safety compliance issues.

Provide technical support related to Environmental Health and Safety to the Mission Manager. Participate in range safety meetings Major Reviews:

Same as CAT 1 and also, provide subject matter expert (SME) technical support in all applicable engineering disciplines to the Mission Manager’s review teams. These teams, known as “Red Teams” evaluate LSC submittals to determine if entry and exit criteria for major reviews have been met. This will be done at all the major reviews specified for CAT 1, as well as others specified in the TO or determined by the COR.

Interface Controls: Same as CAT 1, and also:

Evaluate the interface controls between the launch vehicle system and all other system segments to assure that LSC systems integration efforts properly encompass all system elements.

Evaluate the soundness of systems integration analyses, plans and activities.

Review, analyze and assure definition of interfaces between equipment, facilities and payload(s).

Multi-Payload “Do-No-Harm” IV&V:

For missions requiring integration of more than one space vehicle, conduct “do-no-harm” IV&V. This includes reviewing, validating, and verifying the contractor’s analysis to ensure no space vehicle causes harm to another. Areas of do-no-harm IV&V will include, but are not limited to: dynamic compatibility via finite element model analysis of coupled loads; verification of payload test adequacy, radio frequency interference; material compatibility/safety (e.g., hydrazine leak), magnetic fields, material sensitivity (e.g., Helium), contamination /cleanliness; adequacy of contamination and collision avoidance maneuver (CCAM), and post-deployment re-contact.

Schedule Support:

Provide technical advice and input regarding development and maintenance of program-level schedules. Maintain current MA milestone schedule. Evaluate mission partner milestone schedules. Analyze and assess schedule data for conformance with requirements and evaluate the impact of progress, changes, or slips to the mission.

Procedure Oversight:

Provide support to the Mission Manager's oversight of LSC procedures. Assess LSC technical performance in performing design, fabrication, and integration processes. Assess compliance of LSC end items to include physical and data deliverables, deficiency reports, and waivers. Review, observe, and evaluate LSC practices and evaluate compliance with written procedures, technical requirements, and best practices.

Test Documentation Review:

Review LSC test plans, procedures, and reports and provide assessments and recommendations to the Mission Manager.

Developmental, Qualification, and Acceptance Test Review:

Observe developmental, qualification, and acceptance testing for new design subsystems and major components in support of the mission and provide recommendations to the Mission Manager. Observe testing performed by the LSC on critical components of the launch vehicle. Provide test readiness assessments at Test Readiness Reviews and assess completed testing at Test Reviews when applicable. Report test results and observations to the Mission Manager. (CDRL B003) Composite Structures: Evaluate the LSC’s test plans and loads derivation procedures. Witness load testing and procedure execution, provide evaluation of the results to the Mission Manager.

RSLP Equipment Interfaces and Operation:

Same as CAT 1 Pedigree Review:

Review and evaluate the LSC’s launch system pedigree, design qualification, qualification testing, and flight item acceptance testing processes for compliance with SMC-S-016 (or other appropriate standard). Conduct a pedigree review of all the documentation related to the LSC’s test and buildup of the launch vehicle’s avionics and hardware and evaluate design qualification and flight item acceptance test compliance with SMC-S-016 (or other applicable standard). This pedigree review may be supplemented by one or more delta pedigree reviews to close out any open items. (CDRL B003)

Review Government Industry Data Exchange Program (GIDEP) and sibling alerts for applicability to the mission LV systems and advise the RSLP Mission Manager of any concerns.

Advise the RSLP Mission Manager on risk and risk mitigations.

System Level Test:

Same as CAT 1, and also perform on-site observations during launch vehicle processing and integration activities at the LSC’s facility during system-level integration and test and at the launch site. Review and evaluate completed test/activity procedures, non-conformances and issue resolution.

Guidance Navigation and Control (GNC) IV&V:

Evaluate GNC in the following areas:

Requirements Analysis: Verify traceability between original source and requirements documents and GNC requirements and design.

Changes review: Analyze any changes in GNC models or approach by the LSC.

Model Validation and Verification: Validate and verify the GNC models employed by the LSC (both LSC developed models and models supplied by third parties).

Trajectory Simulation and Analysis: Verify and validate the LSC’s nominal trajectory simulation and determine if adequate margin exists or is likely to exist.

Simulation Analysis: Conduct Independent Mission Simulations: Conduct mission simulation testing using 6-Degree of Freedom (6DOF) linear stability model, off-nominal (Monte Carlo), and stressor cases. (CDRL B003, B004) Navigation Error Analysis: Assess accuracy of LSC’s navigation system.

Consumables Analysis: Conduct independent evaluation of the adequacy and margins for consumable materials required for mission success (e.g., fuel, purge gas, hydraulic/pneumatic fluid).

Day of Launch Analysis: Verify the LSC’s day-of-launch criteria, to include the day-of-launch winds placard.

Software IV&V:

Evaluate the LSC’s software requirements process and verify traceability between source requirements, software requirements, and software design documents.

Software modeling: Analyze LSC’s software modelling or modelling approach. Analyze any changes in software models or approach by the LSC.

Flight Software: Conduct a verification of primary flight software to include the autopilot, guidance, and flight sequencer. The Government will provide the LSC’s source code, executable code, and either a copy of the flight computer or contractual access to the LSC’s integrated test facility to support this verification if required. (CDRL B004) Avionics Software: Evaluate avionics component software and firmware testing and verify functionality demonstrated during mission simulation tests.

Hardware-in-the-Loop (HITL) Testing: Validate the LSC’s HITL test plans and procedures, and verify that HITL test results confirm adequate GNC margins.

Software test plans:

Review the test plans and procedures of the LSC to ensure that they are comprehensive and maintain traceability between requirements and execution.

Final LV software load: Verify and ensure that the final launch vehicle software load, conducted by the LSC, is correct. This work shall be performed at the launch site.

In the event that the LSC’s (or other mission partner) models or analyses yield results significantly different than the MAC’s, the MAC will lead efforts to identify and resolve the discrepancy.

Third Party/Proprietary Components Review of software and firmware found in proprietary or third party (i.e. parties other than the Launch Service Contractor for the subject mission) components is not required unless specifically requested in the Task Order.

Avionics IV&V:

Evaluate avionics requirements and design. Verify traceability between source requirements, avionics requirements, and design documents.

Evaluate avionics integration and assembly, considering process sufficiency, and results of avionics integration, assembly, and test executed by the LSC.

Evaluate the LSC’s RF Intermodulation analysis and verify no significant interference between multiple transmitters/receivers.

Evaluate the LSC’s RF Link Margin analysis and verify adequate signal level for ground based receivers to receive airborne telemetry signals as planned.

Evaluate the LSC’s Battery Margin and Voltage analyses to verify adequate power margin is available to the mission.

Evaluate the LSC’s Ordnance analysis to verify that current levels will meet ordnance initiation specifications.

Evaluate the LSC’s Space Radiation analysis to verify that radiation effects have been adequately considered for the mission.

Fluid Mechanics IV&V:

Aerodynamic models: Develop independent aerodynamic analysis for the launch vehicle configuration to be flown. Use this analysis to verify the aerodynamic analysis done by the LSC.