Attachment 1 Statement of Work (SOW).docx

Acquisition Delta, Innovation and Prototyping Space Test Program (STP) Space Test Experiment Platform 2.0 (STEP 2.0)

Statement of Work (SOW)

Version 1.5 Space Systems Command Acquisition Delta, Innovation and Prototyping DoD Space Test Program

(SSC/SZIS)

Kirtland Air Force Base

ATTACHMENT 1 - IDIQ STATEMENT OF WORK (SOW)

ATTACHMENT 1 – IDIQ STATEMENT OF WORK (SOW)

Albuquerque, NM 87117 ii

Acquisition Delta, Innovation and Prototyping Space Test Program (STP) Space Test Experiment Platform 2.0 (STEP 2.0)

Statement of Work (SOW)

SUBMITTED BY:

STEVEN K. FUTCH, Maj, USSF Date Signed Program Manager, STEP 2.0

APPROVED BY:

JONATHAN P. SHEA, Lt Colonel, USSF Date Signed Director, DoD Space Test Program

Change History

iii

TABLE OF CONTENTS

Tables

GENERAL

Department of Defense (DoD) Space Test Program (STP) Background The Department of Defense (DoD) Space Test Program (STP) is a multi-service program supporting Army, Navy, Air Force, and Space Force space test missions. DoD STP provides space access for Science and Technology (S&T) experiments throughout the DoD. S&T experiments are provided by the DoD Laboratories, (e.g., Air Force Research Lab (AFRL) and Naval Research Laboratory (NRL)) and any experimenter that has a DoD sponsor (e.g., universities, interagency cooperation, and international partners).

S&T is the backbone of emerging technologies therefore space experimentation is critical to continued Space Superiority support to the DoD Space Experiments Review Board (SERB) and International Space Access Review Board (ISARB). DoD STP currently has no in-house capability to procure and launch spacecraft with S&T payloads (PLs).

STEP 2.0 Scope The Space Test Experiment Platform 2.0 (STEP 2.0) program is seeking to establish a multiple award Indefinite Delivery/Indefinite Quantity (IDIQ) contract with separate Delivery Orders (DOs) to procure proven spacecraft (SC) and space access for S&T experiments. The STEP 2.0 IDIQ contract vehicle provides STP the ability to execute DO(s) aligning PL(s), Space Vehicle (SV), and launch vehicle (LV) schedules.

The SC to be procured within each DO will range in size from 12U CubeSats to EELV (Evolved Expendable Launch Vehicle) Secondary Payload Adapter (ESPA) class, and any size in between. The SC shall be within the maximum mass requirements of a 12U to ESPA class vehicle. STP will define specific PL requirements in the Delivery Order (DO) Payload Requirements Document (PLRD). The SC will serve as the platform to integrate S&T PLs to operate in either Low Earth Orbit (LEO) or Geosynchronous Equatorial Orbit (GEO), as a class D system. The following provides a reference for bounding the range of mass and volumes for each SC form factor:

Minimum size and form factor: A 12U CubeSat with a size and form factor defined with dimensions not-to-exceed 226.3 x 226.3 x 366.0 mm (8.91 x 8.91 x 14.41 in) and a mass not-to-exceed 24 kg (53 lbs.) including PL(s). Acceptable 12U CubeSats shall be compatible with containerized dispensers for launch and separation (example either railed or tab-based dispenser). A typical 12U spacecraft (SC) should be able to host 8 kg (18 lbs., 1/3 of total mass) or more of PL mass.

Medium size and form factor: defined with dimensions in excess of 226.3 x 226.3 x 366.0 mm (8.91 x 8.91 x 14.41 in) and a mass in excess of 24 kg (53 lbs.) including PL; also defined with dimensions not to exceed the maximum size and form factor of the ESPA Class SC requirements defined in the immediate paragraph below.

Maximum size and form factor: A small SC (commonly considered an ESPA Class SC) having a mass up to 180 kg (400 lbs.) max including PL, with a size envelope of up to 61 cm (24 in) x 71.1 cm (28 in) x 92 cm (36.2 in). The SC for example may have a mechanical interface of 38.1 cm (15 in) bolt circle, using 24 – 0.635 cm (¼ in) fasteners, or may have alternate fastener system. A typical ESPA SC should be able to host 60 kg (132 lbs., 1/3 of total mass) or more of PL mass.

This contract includes the hardware, software and services needed to acquire a SC, integrate S&T PL, SV to LV integration, support launch operations, conduct on orbit experiment operations, and deliver data to STP’s PL customers. The classification will be identified within each DO DD254. The Space Vehicle Contractor (SVC) is to enter this effort with an existing ground segment to perform on orbit operations with spectrum approval, and infrastructure that meets DOD cyber security requirements. The SVC may be required to place the integrated SV into storage. The SVC shall deliver the integrated SV to the LV integration site. SVs procured and integrated under STEP 2.0 may fly on a dedicated small launch, on a small to heavy rocket as a rideshare on an integrated LV/PL stack, or via a launch broker rideshare service; the term LV represents all these options.

Flight Proven Spacecraft Each SC shall be flight proven. A flight proven SC shall have a flight history of 365 consecutive days of on orbit operations within the last 5 years. Flight proven SC may include incremental updates since last flight for which minor improvements are detailed and justified may meet the flight proven requirements (parts obsolescence, batteries, flight software updates, Internal Research and Development (IRAD) improvements, etc.).

CubeSats within the 12U form factor may be considered by demonstrating flight proven heritage via the SVC's 6U CubeSat with a flight history of 365 consecutive days of on orbit operations within the last 5 years. The SVC shall use flight proven subsystems from the SVC’s 6U CubeSat on the SVC’s 12U CubeSat form factor in order to utilize the 6U CubeSat flight heritage. The SVC’s 12U CubeSat shall be currently in production at least in integration and test phase.

Proven Ground Segment The SVC shall have a proven ground segment solution which consists of the ground station/system, operations facility, and communication network infrastructure providing command and control of a spacecraft and distributing payload data to the customer(s) for the proposed LEO or GEO SC orbit. The SVC or the SVC’s subcontractor shall have successfully operated an SV and distributed PL data for a minimum of 365 consecutive days with a 95 percent ground segment availability.

Document Overview This Statement of Work (SOW) delineates SVC responsibilities in support of the STEP 2.0 contract. The requiring organization is the DoD STP, SSC/SZIS, and any of its mission partners. Only the PCO and any/all appropriately designated contracting officer representatives (COR) may provide direction under this contract.

The information provided in the SOW combined with the System Requirements Document (SRD) and DO Payload Requirements Document (PLRD) serves as the foundation each STEP 2.0 mission.

Management and Communications The Government will assign a Contracting Officer's Representative (COR); the COR will act as the primary interface with the SVC and provide contract surveillance (i.e., quality assurance) in accordance with STEP 2.0’s Quality Assurance Surveillance Plan (QASP), on behalf of the PCO. The COR will assess the contractor’s conformance to each supply delivered and make a final recommendation to the PCO. Performance shall be in accordance with Federal Acquisition Regulation (FAR) 52.246-2, FAR 52.246-3, FAR 52.246-7 and FAR 52.246-8.

The Government will also assign a Mission Manager (MM) for each DO. The MM will be responsible for leading a multi-disciplined Integrated Product Team (IPT) to identify, coordinate, and manage the full breadth of mission planning and activities required to deliver payloads successfully to orbit.

STEP 2.0 CORs and MMs can be either internal to STP or assigned to external DO manager.

Associate Contractor Agreements and Non-Disclosure Agreements Associate Contractor Agreements The SVC shall be capable of entering into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement(s). These agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the conduct of the mission, which shall ensure the greatest degree of cooperation for the successful completion of the DO to meet the terms of the contract. Associate contractors will be provided to the SVC in each DO PLRD. ACAs should 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 ACA expiration date (or event).

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

The SVC shall provide a copy of such agreements to the PCO for review before execution of the document by the cooperating contractors.

The SVC 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 costs / prices of applicable orders issued under this contract. The Government will make necessary updates to the agreements when the associate contractor is succeeded by a new contractor.

Non-Disclosure Agreement The SVC shall establish Non-Disclosure Agreements (NDA) with other contractors performing related services for the Government such as STP’s PL sponsoring organizations, Non-Government advisors responsible for review and analysis on behalf of the DoD STP including Federally Funded Research and Development Center (FFRDCs) and Systems Engineering and Technical Assistance (SETA) support contractors. In addition, these companies have NDA requirements in their Government contract.

Contractor Responsibility Watch List SMC Instruction (SMCI) 64-101, Air Force Space Contractor Responsibility Watch List (CRWL), applies to this contract. Accordingly, if at any time during the performance of this contract the contractor is placed on the CRWL, before executing a modification resulting from an engineering change proposal or exercising an option on this contract, the PCO must determine whether to recommend proceeding with the modification or option exercise and if so, obtain approval to proceed from the SSC Commander or the appropriate SSC Program Element Officer (PEO). To support the PCO’s determination on whether to proceed with the modification or option, the SVC shall submit documentation describing how it has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact performance on this contract. The PCO will consider this information as well as other available information in making a determination.

In accordance with the SSC Class Deviation of FAR clause 52.244-2, Subcontracts, the SVC must receive written consent by the PCO prior to subcontracting with proposed subcontractors included on the CRWL when the subcontracts are valued in excess of three million dollars or five percent of the prime contract value, whichever is lesser. Before providing this consent, the PCO must determine whether to recommend granting consent and if so, obtain approval to proceed from the SSC Commander. Prime contractors must inform their proposed subcontractors that they must notify the prime contractor if they have been notified by the SSC Commander that they have been included on the CRWL. The prime contractor must submit a written consent to subcontract request to the PCO, the prime contractor’s determination of subcontractor responsibility in accordance with FAR 9.104-4(a), and documentation describing how the proposed subcontractor has addressed the conditions that resulted in its inclusion on the CRWL and why those conditions will not impact its performance on a subcontract to this contract. The proposed subcontractor may submit information related to its CRWL inclusion through the prime contractor or directly to the PCO. The PCO will consider information provided by the prime contractor and the proposed subcontractor as well as other available information in making a determination. The SVC is encouraged to inform the PCO of any subcontractor concerns or issues that may jeopardize successful contract performance.

Federally Funded Research and Development Centers As required by SSC’s FFRDC contract with Aerospace Corporation Annex A of this SOW incorporates supplemental acquisition guidance for Enabling Requirements for SSC Program Contracts Requiring Interface with Aerospace FFRDC Contract Support.

Document Notes Key Definitions

The words “may”, “shall”, “will”, “spacecraft”, “space vehicle”, and “spacecraft contractor” have explicit meaning in this document. The definitions of these words as they apply to this document are listed here in Table 1 and in Appendix A Definitions:

TABLE 1 KEY DEFINITIONS

Documents and requirements Applicable Documents The documents listed in Appendix D, apply directly to the performance required, and contain provisions that constitute requirements of STEP 2.0 SOW and SRD to the degree specified in each section of this document. All mission specific applicable documents, including but not limited to those listed in Appendix D, as specified on each DO PLRD.

Reference Documents These documents listed in Appendix D, contain information relating to the work required by this SOW. The mission specific reference documents as specified on each DO PLRD.

Requirements Precedence In the event of a conflict in requirements between this SRD and any other referenced document, the following order of precedence applies: (1 DO SOW), (2 DO PLRD), (3 IDIQ SOW) and the (4 IDIQ SRD) this document. Applicable documents take precedence over Reference documents.

program management Program Management The SVC shall provide the program management necessary to ensure the IDIQ and DO program objectives are meeting cost, schedule and performance requirements. The SVC shall provide cost control, schedule control, subcontract management, financial analysis, tracking, forecasts, planning and reporting for the program. The SVC shall support program related travel as required.

The SVC shall provide a Program Manager (PM) who shall act as the primary liaison between the SVC and the Government.

Working Groups, Review Boards, and Meetings The SVC shall organize required working groups, review boards, and meetings. Only contractors with active SV DOs are responsible for organizing meetings. Both the SVC and Government must mutually agree to meeting times, platform, and content. Content may change as required. If required, the SVC shall provide meeting minutes (CDRL 001: Report, Record of Meeting Minutes) within seven calendar days of each meeting. Table 2 below is an overview of the required working groups, review boards, and meetings.

TABLE 2 MEETINGS AND REVIEWS

Kick-Off Meetings IDIQ and DO Award Kickoff Meetings will be conducted by the Government. The SVC’s Program Manager, Chief Engineer, and other key personnel deemed necessary by the SVC shall attend. Kick-off meetings shall emphasize key personnel, communications, requirements, deliverables, schedule, key events and milestones, and risk.

Weekly Integrated Product Team Meeting Weekly IPT Meetings shall emphasize budgeted vs planned cost, schedule and technical status, SC/SV development, integration and test, and mission operations status, program overview with most important topics addressed, weekly planned activities, issues and risk, and action item status requiring Government and SVC coordination.

Quarterly Management Meeting Quarterly Management Meetings shall emphasize:

· Budgeted planned cost

· Schedule and technical status.

· Brief description of milestones and significant accomplishments scheduled for completion during the reporting period and actual/relative status.

· IMS, milestone update/status, detailed schedule status.

· Current and potential program problems, issues, risk management activities and technical trades to include resolution plans.

· Quality status.

· Critical parts status.

· SC/SV development, integration and test, PL accommodation status, mission operations status, ground solution status, and a program overview with most important topics addressed.

· Action items status requiring Government and SVC coordination.

The SVC shall summarize problem areas together with a schedule and performance impact summary and a discussion of the corrective actions and recovery plans. The SVC shall develop format and detailed content of these presentations in conjunction with and subject to Government approval. Each review shall clearly state the work accomplished on the project during the reporting period and shall divide content into the following sections:

· Other areas for discussion.

· Technical Performance Measurement (TPM) status, supply chain, production, etc.

· Cumulative list depicting closed items, open items, status, POC working action, and estimated completion dates (ECDs).

Bi-Weekly Engineering Review Board Bi-Weekly Engineering Review Boards shall provide a review of technical progress toward meeting the DO PLRD’s goals and objectives. The SVC Chief Engineer, who is responsible for the overall architecture and SC interface, and/or designee, shall chair these meetings.

Quarterly Ground Operations Working Group Quarterly Ground Operations Working Groups shall emphasize mission launch operations to include issues such as launch planning, SV handling and shipping, Ground Support Equipment (GSE) requirements, SV final check-out and hazardous operations prior to integration, SV integration with to the LV/IPS, system safety, flight LV procedures and LV flight data trending.

Periodic Technical Interchange Meeting Periodic Technical Interchange Meetings shall emphasize specific mission issues of concern that require the combined attention of the Government, supporting contractors, and the SVC. The SVC shall support daily teleconferences during the launch campaign to discuss planned work and daily schedule to meet launch date.

Periodic Configuration Control Board Meeting The SVC shall hold CCB meetings that conform to the SVC’s long-standing configuration control system. CCB meetings may include the Contractor, Subcontractor(s), and the Government depending on the nature of the change(s) discussed. The SVC shall notify the Government in advance of any CCB meeting scheduled. The Government’s representative will attend as his/her option.

LV Meeting The SVC shall support LV integration working group meetings.

Periodic Technical Interchange Meeting – Launch Campaign The SVC shall support up to daily teleconferences during the launch campaign to discuss planned work and daily schedule.

Experiment On-Orbit Operations Working Group Experiment On-Orbit Operations Working Groups shall define, control, and verify all mission operations interfaces including the ground segment and support all Experiment On-orbit operations working group meetings and ground segment reviews.

Funds and Labor Hour Report The SVC shall provide a monthly Funds and Labor Hour Report (FLHR).

[CDRL 002 – FLHR]

Cost and Software Data Reporting The SVC shall prepare and submit Cost and Software Data Reporting (CSDR) in accordance with DODI 5000.73 and DoD 5000.04-M-1. The SVC shall prepare and submit a Contract Work Breakdown Structure (CWBS), Cost and Hour Report (Flexfile), and CSDR Technical Data Report.

[CDRLs 033 – CWBS; 034 – Cost and Hour Report (Flexfile); 035 – CSDR Technical Data Report] Contracts and Subcontracts Management The SVC shall establish and implement a subcontract management and controls system sufficient to provide timely, in-depth, and accurate visibility into the subcontractor’s technical, quality assurance, financial, and schedule performance. The SVC shall provide a Small Business Funds Status Report. Comment by Author: Is this supposed to be the bi-annual reporting for the Small Business Subcontracting Plan? If we are looking for a Programmatic report that covers all subcontractors and work actions / payments made, why limit it to just Small Businesses? Odds are there will be significant large business subcontractors supporting various Prime SVCs. Comment by Author: [Mention was removed] [Mention was removed] To discuss CDRL

[CDRL 006 – Small Business Funds Status Report] Program Management Plan and Integrated Master Schedule The SVC shall develop and maintain a logically networked schedule for each DO detailing programmatic activities, planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the contract. The SVC shall provide a Program Management Plan (PMP) and an Integrated Master Schedule (IMS). The SVC should complete integration and test activities for the SV within 18 months following contract award.

[CDRLs 008 – PMP; 037 – IMS]

Significant accomplishments and criteria for each program key event descriptions are in STEP 2.0 Key Events and Milestones as shown in table 3.

TABLE 3 PROGRAM KEY EVENTS AND MILESTONES

Contractor Integrated Performance Management The SVC shall establish, maintain, and use integrated performance management in the performance of this contract. The SVC’s integrated performance management shall include the IMS, contract work breakdown structure (WBS), change management, material management, procurement, cost estimating, and accounting. Correlation and integration of these systems and processes shall provide for early indication of cost, schedule, and technical performance.

Government Property The SVC shall mark delivered SV with a single IUID number. The SV IUID will be the tracking number for the DO’s Period of Performance (PoP).

Government Furnished Property The SVC shall manage Government-Furnished Property (GFP) IAW the FAR and pertinent property accountability guidance (i.e., Item Unique Identification (IUID)). The SVC shall provide an IUID Marking Activity, Validation and Verification Report. The Government will provide GFP to include GFI to the SVC no later than the dates indicated in the DO or as agreed to between the SVC and the Government. The Government will furnish experiment PL models to the SVC as GFE. Comment by Author: what CDRL # is this? Should it be referenced as other CDRL references are above? Comment by Author: [Mention was removed] I am not seeing this on the CDRL list. Comment by Author: [Mention was removed] [Mention was removed] Need to identify a CDRL. DI-MGMT-81804A, DATA ITEM DESCRIPTION (DID): ITEM UNIQUE IDENTIFICATION (IUID) MARKING ACTIVITY, VALIDATION AND VERIFICATION REPORT (12-FEB-2013)

Will need to create a 1423

Hardware deliveries include any special handling, test equipment hardware, software (SW), and sparing required for integration, alignment, and PL functional testing (if required).

The Government will deliver payload-engineering models required by this SOW to the SVC no later than the dates indicated in the DO.

[CDRL 003 – Item Unique Identification (IUID) Marking Activity, Validation and Verification Report] System Safety The SVC shall ensure this effort complies with industrial safety requirements in performance of all efforts associated with SRD Section 4.3 and in accordance with MIL-STD-882E. The SVC shall demonstrate the probability of accidental explosion <1 in 1,000 of the SV during and after mission operations. The SVC shall provide justification for SV release of debris greater than 5mm while on-orbit. The SVC shall provide a System Safety Program Plan (SSPP) and System Safety Reports in accordance with MIL-STD-882E and AFI 91-202, paragraph 11.2.2.2. The SVC shall provide Accident / Incident reports as required. The SVC shall provide a Safety Assessment Report (SAR) in accordance with AFSPC supplement to AFI 91-202 paragraph 11.2.5.1. The SVC shall provide a Preliminary Hazard List (hazard tracking log).

The SVC shall support range safety plans and activities as required by the launch site selected by the program and provide inputs to the mission’s Missile System Pre-launch Safety Package (MSPSP) in accordance with AFSPCMAN 91-710 V3. The SVC shall provide a Combined Space Vehicle Debris Assessment Report/End-of-Life Plan and End of Life and Decommissioning Plan (SDAR/EOLP) in accordance with AFI 91-202. The SVC shall provide inputs to STP’s Spaceflight Worthiness Certification (SFWC) in accordance with SSC Guide SMC-G-1202.

[CDRLs 026 – SSPP; 015 – Accident/Incident Report; 042 – SAR; 027 – Preliminary Hazard List; 041 – Inputs, MSPSP; 012 – SDAR/EOLP; 012 – Inputs, SFWC] Government Visiting Team Support The SVC shall provide facilities and services necessary to support Government visiting personnel. These facilities shall include telephones and computer network connections with access to the internet for the entire period of the visit. Visiting Government personnel shall have unescorted access to all areas dedicated to this program and prearranged escorted access to the other areas used by this program. Government visiting personnel shall have no authority to direct any effort performed under this contract.

general system engineering Systems Engineering The SVC shall provide systems engineering and technical management required to ensure that the SC and the Ground Segment meet all technical performance requirements identified in the DO PLRD. The SVC shall conduct internal peer, design, and readiness reviews prior to and at major mission events and transitions. The SVC shall track and report key mission technical performance at the Quarterly Management Meeting.

Chief Engineer The SVC shall provide a Chief Engineer who shall be responsible for ensuring all systems engineering activities comply with Government and SVC practices and procedures. The Chief Engineer shall have overall responsibility for all System Engineering (SE) activities. The Chief Engineer shall ensure all SC/SV requirements to include system interfaces as defined, tested and verified.

Systems Engineering Management Plan The SVC shall provide a System Engineering Management Plan (SEMP) detailing its overall systems engineering management approach to satisfying STEP 2.0’s requirements. The SEMP shall describe:

· Technical effort and technical processes on what will be used and how the processes will be applied using appropriate activities.

· Project structure to accomplish activities, information flow, and decision-making.

· Resources required for accomplishing STEP 2.0 activities.

· Project critical event’s objectives during any phase of a project’s life cycle.

· Work product outputs of the processes and how the processes are integrated.

· Communication standards between project management engineering teams and entry/exit criteria of work products during project phases.

[CDRL 020 – SEMP]

Requirements Verification Matrix The SVC shall provide a Requirements Verification Matrix (RVM) document consisting of SC requirements and a traceability matrix demonstrating flow down from source program requirements to the subsystem level. The SVC’s RVM shall delineate the method of verification of all program requirements to include an SV design summary and for each requirement the level(s) of assembly at which verification is performed, the verified modes, the method of verification (i.e., type of test, applicable software, etc.) and data results to be submitted in the Mission Readiness Review (MRR), [CDRL 038 – RVM]

Risk Management Plan The SVC shall submit and maintain a Risk Management Plan (RMP), which shall include ranked groups of risks with detailed risk burn-down plans. The risk burn-down plans shall have risk reduction activities that tie to key program milestones. The SVC shall review and update the RMP and identify risk exposure to include likelihood and consequence throughout the life of the contract. The SVC shall report program risk status in bi-monthly management meetings, or as needed and directed by the STP Chief Engineer.

[CDRL 011 – RMP]

Configuration Management The SVC shall provide Configuration Management (CM) to include a Configuration Management Plan (CMP) detailing how it intends to meet CM requirements from SC assembly to experiment on-orbit operations. The SVC shall deliver a Data Accession List (DAL) identifying SVC generated data in compliance with DO PLRD work efforts.

The SVC’s CMP shall describe, at a minimum:

· Organizational relationship of CM authority and functions within the company and the program.

· Policies and procedures for release and control of configuration identification media including drawings, specifications, processes, manufacturing and test procedures, and computer software as applicable.

· Membership, functions, responsibilities, and the SVC’s CCB operating procedures.

· Authority and responsibilities of the person(s) designated to manage CM activities.

· Methods of verification and configuration accounting to ensure implementation of approved design configuration and changes.

· Policies, procedures, and methods for ensuring compatible CM operations at sub-tier suppliers and at other company divisions.

· Special or abridged CM operations peculiar to the needs of this procurement.

The SVC’s CMP shall:

· Identify and document the functional and physical deliverable hardware/system characteristics - Configuration Identification.

· Control changes to those characteristics - Configuration Control.

· Record and report change processing and implementation status - Configuration Accounting.

All CM operations are subject to Government audit against the requirements of this SOW and SRD Section 4.2, provisions of applicable Quality and Reliability Standards, and the SVC’s approved CMP. All Class I changes to approved baselines shall be documented on an engineering change proposal and be submitted to the Government (STP) for approval. The SVC shall be responsible for configuration management of lower tier suppliers in general accordance with requirements herein.

[CDRLs 020 – CMP; 004 – DAL] Hardware and System Configuration Identification The SVC shall deliver hardware/system configuration identification consisting of engineering, manufacturing, and test documentation. Configuration identification completely defines the as-built, as-designed, as-qualified deliverable hardware/system configuration and assures production of equivalent hardware for flight, this includes all development units upon which qualification related testing is performed. The SVC shall provide Hardware/System Configuration Identification consisting of engineering, manufacturing, and test documentation in accordance with SRD Section 4.1. The SVC shall provide a Sparing Plan.

[CDRLs 020 – Hardware/System Configuration Identification; 020 – Sparing Plan] Configuration Control The SVC shall provide a formal release and configuration control process that shall be in place for fabrication, assembly and test of the existing flight unit and its associated test equipment and test and analysis software.

The SVC’s configuration control system shall ensure that only current configuration identification documents and authorized changes used for procurement, assembly, integration, inspection and test of the existing flight unit and its associated test equipment and test analysis software.

The SVC shall establish a formal Configuration Control Board (CCB) of responsible program and functional management personnel to evaluate and approve/disapprove all formal change requests to the procurement, assembly, integration, inspection and test of space and ground segments.

Configuration Accounting The SVC shall maintain “as-built” configuration records, which will enable positive configuration verification and retrieval to the lowest level of manufacturing and test history necessary to prepare part pedigree reports in accordance with SRD Section 4.2. The SVC shall submit changes to “as-built” and pedigree reports for CCB review.

Software Configuration Management The SVC shall provide a configuration control system for software code and the documentation developed for application and operational use, or used to support qualification, acceptance of flight hardware and delivered GSE. The SVC shall document its configuration management process, to include flight software, in a Contractor’s Software Management/Development Plan (SMP/SDP).

Government (IDIQ COR) and SVC approval shall be required for all changes to standard interface code and/or documentation via recertification or review unless waived on an individual case basis by both the Government (DO COR) and the SVC.

[CDRL 020 – SMP/SDP]

Quality Assurance The SVC shall employ stringent quality and reliability standards to ensure STEP 2.0 requirements can be satisfied throughout a mission’s lifecycle. The SVC shall provide and implement bus level product assurance and document its methodology in a Product Assurance Plan. The SVC shall provide and implement a Parts, Materials and Process Control Plan describing parts/materials selection, screening, qualification, application, the approval process, parts obsolescence, and how it will implement hardware/software quality assurance. The SVC shall provide and implement a Quality Assurance Plan.

The SVC shall implement a reliability program and provide reliability predictions that describe how SVC systems comply with the SRD and DO PLRD requirements to include Failure Mode Effects and Critical Analysis (FMECA). The SVC shall provide risk/issue management regarding the procurement of space hardware and reliability and parts engineering to include radiation analysis and testing. The SVC shall provide reliability and parts engineering for the SV to include radiation analysis and testing. The SVC shall generate failure notification reports, perform failure analyses and provide such information to the Government starting at SC assembly. The SVC shall conduct quality and site surveys of major suppliers.

[CDRLs 020 – Parts, Materials & Process Control Plan; 020 – Product Assurance Plan; 018 – Reliability Predictions; 020 – Quality Assurance Plan; 021 – FMECA] Special Studies The SVC shall support special studies, as associated with STEP 2.0.

[CDRL 043 – Special Studies] Spacecraft and Ground Technical Specifications Sheet The SVC shall provide a SC and Ground Technical Specifications Sheet (SGTSS) which will provide SC and ground characteristics.

[CDRL 043 – SGTSS]

Payload User’s Guide The SVC shall provide a Payload User’s Guide (PUG) for DO, which will advise DoD S&T payloads on their designs to promote compatibility with the contractor’s SC system. The contractor’s PUG shall at a minimum address system characteristics, payload interfaces, payload required deliverables, environmental design and test requirements and payload general design requirements in accordance with STEP 2.0’s PUG requirements document.

[CDRL 043 – PUG]

Contamination and Environmental Controls The SVC shall provide a Contamination Control Plan describing how its contamination and environmental program will minimize the risk of contamination and maintain cleanliness, temperature, and humidity of PLs throughout all phases of assembly, integration, transportation, and launch.

[CDRL 012 – Contamination Control Plan] Specialty Engineering The SVC shall provide other specialty engineering including, but not limited to, fault tree analysis development and atomic oxygen effects.

spacecraft requirements Payload Accommodation The SVC shall take a lead role in ensuring PL sponsoring organizations have a thorough understanding of the SC interface(s). The SVC shall monitor experiment progress to ensure PL integrity and make recommendations concerning the SC ability to host/accommodate experiment(s) to the STP program office.

System Engineering The SVC shall provide technical management and control, systems engineering, quality assurance, facilities, and security control to include requirements flow down and verification at the SC level. The SVC shall procure, manufacture, and deliver all SC hardware to meet program requirements. The SVC shall support SV Assembly, Integration, and Test (AI&T) and LV AI&T activities. The SVC shall conduct a SIRR to show SVC’s readiness to assemble the SC. The SVC shall conduct a Spacecraft Acceptance Review to ensure SC assembly meets the SVC’s SC design requirements. The contractor shall ensure all Space segment components have required certifications and approvals for the DO mission duration to include up to a 12-month potential extension of basic operations.

Space Vehicle System Requirements Review SV System Requirements Reviews (SRR) shall provide a review of system-level requirements, with a specific emphasis on validating that system architecture meets STEP 2.0 program priorities Mechanical Subsystem The SVC shall design, analyze, develop drawings, fabricate, and perform required testing to produce the SC flight structure to include secondary structure and sub-components. The SVC shall submit flight-proven SC qualification evidence for Government (STP) review. The SVC shall design, analyze, fabricate, and test all required mechanisms including solar array deployment mechanisms, solar array hinges, solar array drive, and any boom deployment mechanisms. The SVC shall provide technical oversight of all subcontracted components. The SVC shall perform tasks including spacecraft physical configuration and layout; structure detail design; Structure Finite Element Modeling (FEM) and analyses; piece part analysis; material and component procurement; structure fabrication, assembly, and test; design verification; and technical support to parts procurement and production. The SVC shall develop FEMs and perform SC structure stress analysis. The SVC shall generate component specifications for subsystem hardware and all required assembly drawings.

Mass Properties The SVC shall account for separation system mass and volume in the allowable SC envelope and mass as stated in SRD Section 5.3 for SCs larger than 12U CubeSats. The Government will provide expected PL mass properties in the DO PLRD. The SVC shall provide a best estimate of the predicted mass properties at the PL Accommodation Review and shall provide measured mass properties one month prior to PSR.

Avionics The SVC shall provide analysis, drawings, fabrication, and testing required to produce the SC integrated avionics unit. The SVC shall perform the following tasks:

· Provide Integrated Avionics Unit Component Specifications.

· Develop and operate from an integrated avionics user's guide.

· Provide technical oversight of all subcontracted components.

· Provide Command and Telemetry Formats.

· Provide Telemetry Engineering Conversions and Timing.

· Define command list.

· Conduct throughput data flow and storage analysis.

· Develop and maintain input/output memory address maps.

· Fabricate and test engineering units of integrated avionics for simulator and SW development facility.

[CDRLs 022 – Integrated Avionics Unit Component Specification; 012 – Command and Telemetry Formats, Telemetry Engineering Conversions and Timing] Guidance, Navigation and Control The SVC shall provide analysis, drawings, fabrication, and testing required to produce the SC guidance, navigation, and control (GN&C) subsystem. The SVC shall generate component specifications for subsystem hardware and provide technical oversight of all subcontracted components. The SVC shall conduct pointing, control, and stability analyses to verify capability of SC to meet performance requirements. The SVC shall tailor GN&C algorithms and test GN&C flight software as necessary to meet DO requirements.

Electrical Power Subsystem The SVC shall provide analysis, drawings, fabrication, and testing required to produce the SC electrical power subsystem. The SVC shall generate component specifications for subsystem hardware including solar array assembly, flight battery, and test battery. The SVC shall provide technical oversight of all subcontracted components. The SVC shall be in compliance with requirements as defined in the SRD Section 5.4 and the DO PLRD. The SVC shall conduct energy balance analysis for the SC and DO PL(s). The SVC shall ensure the SC is capable of monitoring and reporting SC bus voltage values as part of normal SC telemetry.

Communications Subsystem The SVC shall provide analysis, drawings, fabrication, and testing required to produce the SC communications subsystem, generate component specifications for subsystem hardware, provide technical oversight of all subcontracted components, and conduct link analyses for command, telemetry and ranging operations.

Flight Software The SVC shall…