A3_Milestones_23OCT14.pdf

ATTACHMENT 3

TO

FA8818-15-R-0003

Operationally Responsive Space - 5 (ORS-5)

MILESTONE DELIVERABLE DESCRIPTIONS AND

REQUIREMENTS

23 Oct 2014

Milestone Deliverable Descriptions and Requirements for

ORS-5 SensorSat Launch Vehicle Services October 23, 2014

ATTACHMENT J.3 - Milestone Deliverable Descriptions and Requirements

Event Estimated Date Payment Amount Percentage

Kick Off Meeting ATP + 2 weeks 5

System Requirements Review (SRR) ATP +3 months 10

Preliminary Design Review (PDR) SRR + 3 Months 10

Critical Design Review (CDR) PDR + 6 Months 10

Qualification Testing (QT) CDR + 6 Months 15

Design Certification Review (DCR) LVRR – 1 month 15

Launch Vehicle Readiness Review (LVRR) Launch -3 months 10

Flight Readiness Review (FRR)/Launch Readiness Review (LRR) & Launch Launch - 3 days 5

Post-Launch Assessment Report Launch + 2 months 20

Milestone Deliverable Descriptions and Requirements

Mission specific is defined as services provided that are newly performed or developed specifically to meet the requirements of the payload and mission. All new, modified and unqualified launch vehicle systems (reference PWS section 4.0) are considered mission specific.

Government approval is defined as providing authority to proceed and/or formal acceptance of requirements, plans, tests, or success criteria in specified areas. Where Government approval is required, the Contractor shall submit the necessary documentation to the Contracting Officer and copies to the Contracting Officer’s Representative (COR).

Kick-Off Meeting

A. Vehicle Overview B. Proposed Schedule C. Risks to implementation of PWS

Design Reviews

The Contractor shall conduct and chair design reviews, as described below, that apply to the system, subsystem, component, and software level items. Where there is not a direct match between a PWS specified design review(s) and the Contractor’s standard review(s), the Contractor’s review process will be acceptable provided it addresses equivalent content. All derived requirements from all system requirements must be identified and addressed in each of these reviews. ORS will approve the mission specific items that have a direct interface to the spacecraft/deployer in these reviews. Launch vehicle mission specific items will be presented to ORS for insight into the development of the launch service.

Mission Specific System Requirements Review (SRR)

The Contractor shall conduct an SRR prior to the Preliminary Design Review (PDR) to review the design requirements for the following items:

(i) System requirements’ identification and definition to a level adequate to verify launch vehicle performance capabilities.

(ii) Design restrictions, limitations, and known violations.

(iii) Physical and mechanical interfaces (e.g., payload to launch vehicle, payload envelope, and access provisions) including interfaces between new and existing launch vehicle systems.

(iv) Electrical and Avionics systems interfaces (e.g., launch vehicle to payload, payload to umbilical, interfaces with electrical ground support equipment, pad electrical systems, ground batteries, telemetry, grounding, and power) including interfaces between new and existing launch vehicle systems.

(v) Functional interfaces between the launch vehicle and the payload and interfaces between new and existing launch vehicle systems.

(vi) Mass properties.

(vii) Payload Environmental requirements (e.g., thermal, contamination, vibration, pressure, Electromagnetic Compatibility (EMC), shock, launch complex RF, and lightning).

(viii) Orbital requirements, launch vehicle performance, launch window injection accuracy, and deployment attitudes and rates.

(ix) Payload/Launch Vehicle separation requirements (e.g., separation conditions, launch vehicle post-separation maneuver requirements, and telemetry).

Mission Specific Preliminary Design Review (PDR)

The Contractor shall conduct a preliminary detailed design review prior to major commitment to drawings and design. Mission specific trade studies shall be completed prior to the PDR. The Contractor shall discuss analyses performed and their results along with comparisons to any similar proven designs. The Contractor shall evaluate the safety of the design and its ability to meet safety requirements. ORS reserves the right to withhold approval of this milestone if the mission specific design poses major problems that may cause significant schedule delays and until all action items related to the payload interface have been closed. As a minimum, the Contractor shall provide verification of the following items at the

PDR:

(i) All system requirements have been allocated to the subsystem and component level and the flow down is adequate to verify system performance.

(ii) The design solutions being proposed are expected to meet the performance and functional requirements.

(iii) The design does not pose major problems that may cause significant schedule delays.

(iv) Overall system architecture has been established.

(v) The design solution can be produced based on existing processes and techniques; if not, risk areas, which require unique and unproven processes, are identified and risk mitigation plans are established.

(vi) An acceptable operations concept has been developed.

(vii) Preliminary interfaces have been identified and are verifiable.

(viii) Preliminary plans are established for end-to-end testing methodologies.

(ix) Approximately 30% of the drawings released.

(x) The preliminary ICD (CDRL 0003) has been submitted.

Mission Specific Critical Design Review (CDR)

The Contractor shall conduct a CDR before significant fabrication activity begins. The Contractor shall present a final detailed design using drawings, analyses, and evaluation testing that shows the design meets final performance and interface specifications, safety requirements, and mission objectives. The Contractor shall identify planned qualification and acceptance tests to be performed to prove validity. ORS reserves the right to withhold approval of this milestone if the mission specific design does not meet performance or schedule requirements and until all action items related to the payload interface have been closed. As a minimum, the Contractor shall provide verification of the following items at the CDR:

(i) All known technical design problems and development anomalies have been resolved without compromising required system function, performance and safety. If not resolved a credible and detailed resolution plan exists to resolve them prior to qualification testing.

(ii) The detailed design will meet performance, functional requirements, and schedule.

(iii) Software simulations and prototyping results do not present any potential mission risks.

(iv) All key engineering analyses have been performed to support the detailed design.

(v) Integrated safety analysis identifying any remaining hazards and proposed resolution.

(vi) Launch vehicle/payload compatibility test plans have been defined.

(vii) Approximately 90% of drawings released.

(viii) The baseline ICD has been submitted (CDRL 0003).

Mission Specific Qualification Testing (QT)

Demonstrates the functional performance of launch vehicle systems, with margin. Testing shall include major Contractor identified key systems, and shall include propulsion systems if applicable, necessary to demonstrate high confidence in the ability to successfully deliver the launch service. The QT success shall be subject to ORS approval. ORS reserves the right to withhold approval if the Contractor defined success criteria has not been met or if there is other reasonable evidence to suggest the QT is unsuccessful.

Mission Specific Design Certification Review (DCR)

The Contractor is required to demonstrate through the DCR that components and subsystems are “qualified” because they have been tested, analyzed, demonstrated, or shown by similarity to meet all functional requirements and demonstrate margin over all expected, storage, shipping, handling, flight, and acceptance environments. Qualification is required to be accomplished against the Contractor’s standard(s). It is recognized that launch service Contractor chooses or maintain their own technical standards for design and test; therefore the chosen standard(s) will be provided to the ORS office 1 month prior to the DCR to aid in our understanding of the qualification status.

The DCR will include the as built and qualified implementation/fabrication, component qualification, and system level qualification/compatibility. A DCR for ORS-5 is essentially an updated critical design review (CDR) after the mission specific items have completed design, manufacturing/fabrication, qualification testing, and final analysis. The presentation material of the DCR should cover all elements of the entire life cycle (e.g. requirements, design, analysis, critical fabrication methods, testing, and anomaly resolution if any). All flight critical mission specific components, systems and subsystems will be presented. ORS reserves the right to withhold approval of this milestone if the mission specific design is not qualified to the Contractor’s standard(s) and until all action items related to the payload interface have been closed.

Launch Vehicle Readiness Review

The Contractor shall conduct a Launch Vehicle Readiness Review to demonstrate that the launch site and launch vehicle are ready to proceed with launch vehicle processing activities at the launch site. The Contractor shall present as a minimum:

(i) Mission description including S/C and launch vehicle configuration; integration status;

summary of waivers; mission specific analyses results and status including updates if any from the Mission Specific DCR and mission specific analyses not related to qualification; flight launch vehicle and launch site hardware/software production and testing status, and assessments of any significant manufacturing anomalies

(ii) A detailed schedule showing all activities (ground and flight) remaining to achieve a successful, on-time launch

Launch

Flight Readiness Review (FRR)

The Contractor shall conduct a FRR for the mission to ensure the launch vehicle is acceptable for flight and all Range and other mission requirements have been met, or will be satisfied prior to launch. The FRR shall include participation from any appropriate Range approving officials. The FRR is held approximately five (5) to ten (10) days before launch. As a minimum, the Contractor shall provide verification that:

(i) All critical items required to proceed into final launch countdown are ready

(ii) Vehicle configuration is defined and all vehicle systems have been verified IAW launch site test plans

(iii) All previously recorded action items have been closed or are reflected on the schedule

(iv) All previously held Contractor’s readiness review actions have been closed or resolved

(v) Launch site/Range support organizations have committed to launch

(vi) Tracking and data support resources are committed to launch

(vii) Any open work is identified and closeout plans and schedules are in place and supportable

(viii) Any constraints to launch are identified and resolution plans developed

(ix) Mission risks are known and documented

(x) Launch commit criteria for payload and launch vehicle is approved and released

The Contractor shall also discuss:

(i) Anomalies from previous missions if applicable,

(ii) Hardware/software failures in the field

(iii) Open corrective actions/problems reports

(iv) Overview of Mission specific items

Launch Readiness Review (LRR)

The Contractor shall conduct a LRR for the mission to ensure the specific launch vehicle is acceptable for flight and all Range and other mission requirements have been met, or will be satisfied prior to launch. The LRR shall include participation from any appropriate Range approving officials. The LRR is held approximately two (2) days before launch. As a minimum, the Contractor shall provide verification that any open items and deviations from the FRR have been satisfied.

J.3-5

Post-Launch Assessment Report

Include verification that:

i. The launch vehicle orbit at payload separation agrees with prediction, or if not, it is adequately understood so that future behavior can be predicted with confidence.

ii. All anomalies have been adequately documented, and their impact on future Contractor operations is assessed. Further, anomalies related to the payload to launch vehicle interface have been had at least one credible cause identified to aid in the Contractors future resolution.

Mission Success Criteria

(A) A mission will be determined a Mission Success, if:

(i) The payload is placed into the required orbit by the launch vehicle, and

(ii) Received telemetry data shows the ID environments and parameters were not exceeded, and if the telemetry is not received

(iii) The launch vehicle causes no damage to the payload during launch or thereafter from collision or contamination products.

(B) A mission will be determined a Failed Mission when the payload:

(i) Is destroyed during launch/flight, or

(ii) Cannot be separated from the launch vehicle