Attach_3_SMC_Guide_SMC-G-1204_Space_Launch_Readiness_Review_Process-31Oct2013.pdf

Document Change Record Version Changes Date

0.0 Initiated upon termination of SMCI-63-1204 09 Oct 2009

1.0 Extensive rewrite to provide more specific guidance to SPO action officers

31 Aug 2013 i

Contents

1. READINESS REVIEW PURPOSE

2. READINESS REVIEW AUTHORITY

2.1. SMC/EN Support Points of Contact (POCs)

2.2. Readiness Review Meeting

3. STAKEHOLDER DESCRIPTION

3.1. Space and Missile Systems Center Commander (SMC/CC)

3.2. Enterprise Assurance Division Chief (SMC/EN)

3.3. Mission Director (MD)

3.4. System Program Office (SPO) Director

3.4.1. SPO Chief Engineer

3.5. Independent Readiness Review Team (IRRT) Lead

3.6. System Safety Manager (SSM)

4. SMC READINESS REVIEW PROCESS

4.1. Administration Applicable to All Readiness Reviews

5. DETAILED READINESS REVIEW DESCRIPTIONS

5.1. Executive Incremental Readiness Review (eIRR)

5.1.1. Purpose

5.1.2. Attendees

5.1.3. Roles and Responsibilities

5.1.4. Minimum Required Content

5.1.5. Entrance Criteria

5.1.6. Exit Criteria

5.1.7. Administration

5.1.8. Template

5.2. Executive Mission Readiness Review (eMRR)

5.2.1. Purpose

5.2.2. Attendees

5.2.3. Roles and Responsibilities

5.2.4. Minimum Required Content

5.2.5. Entrance Criteria

5.2.6. Exit Criteria

5.2.7. Administration

5.2.8. Template

5.3. Flight Readiness Review (FRR)

5.3.1. Purpose

5.3.2. Attendees

5.3.3. Roles and Responsibilities

5.3.4. Minimum Required Content

5.3.5. Post-FRR Communication Plan Review (PFCPR)

5.3.6. Entrance Criteria

5.3.7. Exit Criteria

5.3.8. Administration

5.3.9. Template

ii

5.4. Operational Readiness review (ORR)

5.4.1. Purpose

5.4.2. Attendees

5.4.3. Roles and Responsibilities

5.4.4. Minimum Required Content

5.4.5. Entrance Criteria

5.4.6. Exit Criteria

5.4.7. Administration

5.4.8. Template

5.5. Executive Readiness Review (ERR)

5.5.1. Purpose

5.5.2. Attendees

5.5.3. Roles and Responsibilities

5.5.4. Minimum Required Content

5.5.5. Entrance Criteria

5.5.6. Exit Criteria

5.5.7. Administration

5.5.8. Template

5.6. Post Flight Review (PFR)

5.6.1. Purpose

5.6.2. Attendees

5.6.3. Roles and Responsibilities

5.6.4. Minimum Required Content

5.6.5. Entry Criteria

5.6.6. Exit Criteria

5.6.7. Administration

5.6.8. Template

5.7. Certification Readiness Review (CRR)

5.7.1. Purpose

5.7.2. Attendees

5.7.3. Roles and Responsibilities

5.7.4. Minimum Required Content

5.7.5. Entrance Criteria

5.7.6. Exit Criteria

5.7.7. Administration

5.7.8. Template

Figures Figure 4-1 – SMC Readiness Review Sequence and Timeline Figure 5-1 – Certification and Day of Launch Responsibilities Figure 5-2 – eIRR Timeline Figure 5-3 – eMRR Timeline Figure 5-4 – FRR Timeline Figure 5-5 – PFR Timeline Figure 5-6 – CRR Timeline Figure A-11 1 - FRR Process .................................................................................................................................... 11-1 Figure A-11 2 - Boardroom Seating Chart Template ............................................................................................... 11-1 Figure A-11 3 - RPC Seating Chart Template .......................................................................................................... 11-2 Figure A-11 4 - Visitor Parking Guide ..................................................................................................................... 11-4 iii

Tables Table 2-1 – SMC/EN Support POCs Table 5-1 – Readiness Reviews Table 5-2 – eIRR Artifacts Table 5-3 – eMRR Artifacts Table 5-4 – Flight Readiness Review Agenda Table 5-5 – FRR Artifacts Table 5-6 – Post Flight Review Agenda Table 5-7 – Post Flight Review Products Table 5-8 – PFR Artifacts Table 5-9 – Certification Readiness Review Agenda Table 5-10 – CRR Artifacts Table A-4 4-1 – Key EOT Participants, Roles and Responsibilities ......................................................................... 4-3 Table A-4 5-1 – Sample Progress Report Update Process ......................................................................................... 4-4 Table A-4 5-2 – CCIR Reporting Criteria ................................................................................................................. 4-5 Table A-4 6-1 – Sample Core EOT Status Report Distribution ................................................................................ 4-6 Table A-4 6-2 – Sample AFSPC and 14AF EOT Status Report Distribution ........................................................... 4-7 Table A-4 6-3 – Sample Secretary of the Air Force (SAF)/Headquarters Air Force (HAF) EOT Status Report Distribution ................................................................................................................................................................ 4-7

Appendices Appendix 1 – References Appendix 2 – Abbreviations and Acronyms Appendix 3 – Development Missions with Higher Acceptable Risk Appendix 4 – Sample Post-FRR Communications Plan Appendix 5 – Readiness Review Plan Template Appendix 6 – Draft Mission Director Designation Memo Appendix 7 – Draft Launch Vehicle Space Flight Worthiness Certification Letter to SMC/CC Appendix 8 – Draft Space Vehicle Space Flight Worthiness Certification Letter to SMC/CC Appendix 9 – Draft SMC/CC Space Flight Worthiness Certification Letter Appendix 10 – Draft SMC/CC ICBM Motor Certification Letter Appendix 11 – SMC Space Flight Readiness Review Process Checklist

1. READINESS REVIEW PURPOSE

The purposes of the readiness review process are:

1. Ensure the mission is ready for launch

2. Ensure risks to the mission from the launch are understood and mitigated to the greatest extent practicable

3. Provide sufficient visibility to the Space and Missile Systems (SMC) Commander

(SMC/CC) regarding the mission readiness of programs across the space acquisition portfolio

4. Provide decision quality material to the SMC/CC

5. Capture lessons learned in order to promulgate best practices across systems being acquired at SMC

6. Identify problem trends in order to cost effectively resolve technical issues

2. READINESS REVIEW AUTHORITY

The Air Force Space Command Commander (AFSPC/CC) has delegated determination of space flight worthiness (SFW) to the SMC/CC in Air Force Space Command Instruction (AFSPCI) 10- 1208, Spacelift Operations. The readiness review process directly leads to SFW determination, and if successful, certification for flight. The SMC Enterprise Assurance Division Chief (SMC/EN) is the readiness review process owner for the SMC/CC, and as such, SMC/EN will provide the programs with guidance on technical rigor and is the central coordinating agency for the readiness review presentations to the SMC/CC or designee. While this process can support other decisions, it is primarily focused on readiness for launch.

The SMC Readiness Review Process is a tool that allows the SMC/CC, Mission Director (MD) and system or end-item System Program Offices (SPOs) the ability to evaluate system readiness and compliance with Life Cycle Systems Engineering regulations; see Air Force Instruction (AFI) 63-101/201 and SMC-G-001 Life Cycle Systems Engineering for additional details.

Through the course of a number of different reviews throughout a system life cycle, the SMC Readiness Review Process fosters a greater depth of programmatic and technical understanding of the safety, suitability, and effectiveness of the system or end-item.

This guide will cover the following activities:

1. Executive Incremental Readiness Review (eIRR)

2. Executive Mission Readiness Review (eMRR)

3. Post-FRR Communication Plan Review (PFCPR)

4. Flight Readiness Review (FRR)

5. Operational Readiness Review (ORR)

6. Executive Readiness Review (ERR)

7. Post-Flight Review (PFR)

2.1. SMC/EN SUPPORT POINTS OF CONTACT (POCS)

SMC/EN provides resources to support this process. For additional support scheduling and coordinating on the process described in this document, contact the SMC Readiness Review Team at the SMC Readiness Review organizational mailbox, and your Cadre support team at one of the following organizational e-mail addresses in Table 2-1.

Table 2-1 – SMC/EN Support POCs

SMC/EN Readiness Review Support Group E-mail Addresses SPO

SMCReadinessReview@us.af.mil All

SMCSE.Workflow@us.af.mil All

UDG_SMC_EN_CADRE_GP@us.af.mil SMC/GP

UDG_SMC_EN_CADRE_IS@us.af.mil SMC/IS

UDG_SMC_EN_CADRE_LR@us.af.mil SMC/LR

UDG_SMC_EN_CADRE_MC@us.af.mil SMC/MC

UDG_SMC_EN_CADRE_RN@us.af.mil SMC/RN

UDG_SMC_EN_CADRE_SD@us.af.mil SMC/SD

UDG_SMC_EN_CADRE_SY@us.af.mil SMC/SY

UDG_SMC_EN_CADRE_WM@us.af.mil SMC/WM

UDG_SMC_EN_CADRE_XR@us.af.mil SMC/XR

2.2. READINESS REVIEW MEETING

The SMC/EN staff is responsible for scheduling and coordinating all functions for any readiness review presented to the SMC/CC or designee. The Space Vehicle (SV) SPO coordinates with SMC/EN, Launch Vehicle (LV) SPO, and associated Ground Systems (GS) SPOs to establish and approve the readiness review plan for the launch mission; see Appendix 5 for a sample template. For missions where the SV is not procured by SMC, the LV SPO will establish and approve the readiness review plan. Once approved, the SPOs are responsible for coordinating with their contractors and SMC/EN regarding the scheduling, presentations and documentation for the readiness reviews. Readiness reviews must be scheduled far enough in advance to accommodate the schedules of the SMC/CC and the 14th Air Force Commander (14AF/CC).

This drives the need for readiness review planning to occur no later than (NLT) six months before launch to ensure decision quality information is provided promptly to the key decision makers (SMC/CC, 14AF/CC, Aerospace CEO, Mission Director, and others) within schedule constraints.

The SPO Directors, in conjunction with the operating commands and other users, participate in each review as appropriate. Each SPO should provide a description of how readiness reviews are addressed in the program Systems Engineering Plan (SEP). The SEP will incorporate all key elements of Life Cycle Systems Engineering mission assurance, describe certifications and reviews in terms of scope, schedule and budget in coordination with the contractor’s plan, and detail the continuing Operational Suitability, Safety and Effectiveness (OSS&E) assessment occurring after system fielding or launch and operational checkout. Due to different program complexities and resources, the SPO can tailor the standard readiness review process to meet unique program needs based on budget, schedule, level of maturity, and acceptable risk.

3. STAKEHOLDER DESCRIPTION

3.1. SPACE AND MISSILE SYSTEMS CENTER COMMANDER (SMC/CC)

For United States Air Force (USAF) launches, the SMC/CC is accountable for launch mission success and certifies LV and Air Force (AF) satellite readiness. This includes mission direction and mission authority responsibilities through satellite separation, including any post-separation mission requirement performed by the upper stage. For non-AF missions launched on AF-procured LVs, the SMC/CC only certifies the SFW of AF-procured components and systems.

Per AFSPCI 10-1208, the SMC/CC appoints, trains, and certifies the AF MD for every Department of Defense (DoD) launch of space lift systems and services acquired by SMC.

SMC/CC certifies SFW of the mission at or after the FRR, and briefs the AFSPC/CC at the ERR.

3.2. ENTERPRISE ASSURANCE DIVISION CHIEF (SMC/EN)

The SMC/EN Enterprise Assurance Division Chief or designee will serve as the overall SMC owner and monitor of the mission readiness review process, and will coordinate executive support for the readiness review presentations. SMC/EN may also help the SPO assess whether or not a particular readiness review is necessary. SMC/EN maintains an archive of all presentations, and other pertinent records of each eIRR, eMRR, FRR, ORR, ERR, and PFR.

SMC/EN maintains awareness of future launches through participation in SMC/LR Senior Management Reviews, monitoring the launch manifest and coordinating with SMC/SD.

SMC/EN also maintains the master schedule of upcoming SMC/CC readiness reviews. SMC/EN will convene a meeting with the SV SPO Chief Engineers to plan for upcoming readiness reviews for the fiscal year, and SMC/EN will assist the SV SPO Chief Engineers with execution of the resulting master schedule. SMC/EN meets with the MD or designee to plan the FRR and

PFR.

SMC/EN maintains a distribution list to which presentation material is provided prior to a readiness review. The list includes: SMC/CCE as a ‘To’ addressee, ‘CC’ to SMC/CCS, SMC/EN Mission Assurance Chief, SMC Chief Systems Engineer, SMC/IRRT Chief, SMC/SE, and 14AF; a hardcopy of the presentation material will be provided to SMC/CCE as well. The SV, payload GS, and LV program offices will need to provide the presentation material directly to other stakeholders, to include non-14AF launch site and range services, if applicable. If a SMC/CC delegate is chairing the meeting, include SMC/CVE or SMC/CVS as a ‘To’ addressee.

3.3. MISSION DIRECTOR (MD)

Per AFSPCI 10-1208, the MD is appointed, trained, and certified by the SMC/CC for every DoD launch of space lift systems and services acquired by SMC, and is typically a senior leader from the SPO procuring the LV. The National Reconnaissance Office (NRO) appoints the MD for NRO missions, and the SMC Launch Systems Directorate (SMC/LR) provides an LV technical expert to the MD to provide subject matter expertise throughout the readiness reviews. For missions where the Space Development and Test Directorate (SMC/SD) procures the LV, SMC/SD will provide the MD. The MD from SMC is appointed by letter, a sample of which is provided in Appendix 6.

The MD is responsible for the integrated SV/LV mission and providing mission assurance for all critical elements that can affect overall success including the LV, ground processing and launch operations.

Once designated, the MD is responsible for:

1. Assuring the SMC/CC that all AF-controlled mission functional and support elements are ready to support launch and on-orbit operations

2. Missions with AF-provided LVs, assuring mission compliance of the SV/LV stack with SFW Criteria (SFWC)

3. Coordinating the FRR and PFR

3.4. SYSTEM PROGRAM OFFICE (SPO) DIRECTOR

The SV and/or LV SPO Directors are responsible for executing approved readiness reviews designated under their lead to ensure a successful mission. All programs for which SMC has significant responsibility for mission success, including launching hosted flight hardware, will structure, fund and manage to implement the readiness review process. The Director is responsible for assuring mission compliance with SFWC for the flight or ground hardware under their purview.

For missions with an SMC procured satellite, the SV SPO Director establishes the readiness review plan and works with the SMC/EN Enterprise Assurance Division Chief to tailor the readiness review process and briefing details to accommodate mission unique circumstances.

The SV SPO Director may delegate the lead for specific reviews to others but remains responsible for the approved mission readiness review plan.

Both the SV and LV SPO Directors have program milestone responsibilities outside of the readiness review process that are defined in the System Engineering Plan. To the greatest extent possible, those milestones (Consent to Ship Review, Aerospace President’s Review, Consent to Fuel Review, SV/LV mate, others) should be aligned closely with the readiness reviews described below in order to minimize impacts to program and outside stakeholder schedules.

The SPO Director must ensure program security requirements and constraints as contained in the relevant security classification guide are enforced so that controlled information is not exposed to personnel who do not have proper clearance and need to know.

3.4.1. SPO CHIEF ENGINEER

The SV and/or LV SPO Chief Engineer or designee is the coordinator for the readiness reviews under the relevant SPO lead in the approved mission readiness review plan. The Chief Engineer is responsible for liaison with the associated SMC/EN Cadre and to inform SMC/EN NLT two months before the readiness reviews described in this document are ready to begin. A well developed readiness review plan will establish and highlight the necessary points of coordination to successfully meet review guidance.

3.5. INDEPENDENT READINESS REVIEW TEAM (IRRT) LEAD

The SMC/EN Independent Readiness Review Team (IRRT) lead is responsible for the independent assessment of mission readiness when applicable. A team of experts, independent of the program under review, will conduct a review in accordance with the approved SEP within its scope, budget and schedule. The lead is responsible to provide status information to the applicable SPO, MD and SMC/EN on a regular basis and when any significant findings are discovered. The IRRT is administratively within the SMC/EN organization, but directly reports to the SMC/CC.

The program will include support for independent readiness reviews. The SPO will coordinate with the IRRT or other assigned independent review team to perform independent readiness reviews, as required.

3.6. SYSTEM SAFETY MANAGER (SSM)

The SSM works with System Engineering staff to provide System Safety risk assessments for each mission. For safety risks requiring Command Acquisition Executive (CAE) or Program Executive Officer (PEO) acceptance, program managers and/or SSM must prepare a written risk assessment describing the hazards, predicted risks (stating both consequences and probabilities), available mitigation measures, costs or other limitations, proposed action(s), alternatives, resulting net mishap risk and the total expected consequences for the period of acceptance. AFI 91-202 AFSPC SUPL I U.S. Air Force Mishap Prevention Program Attachment 15 guidance is mandatory for high risk acceptance packages and recommended for all other risk assessments. A high and serious risk package must be coordinated with SMC Chief System Safety Manager (CSSM), and the CSSM coordinates with the SMC/SE Director. High-level safety risk acceptance packages must be coordinated with the lead commands and AF/SE before assessments are submitted for acceptance. Program managers must reassess CAE- or PEO-accepted risks at least every four years and for milestone reviews or key decisions following approval, with consideration given to actual incident and loss experiences for the period and advances in mitigation technologies and methods. Re-validated risk assessments must be coordinated and submitted for acceptance by the appropriate authority for the new predicted risk levels.

4. SMC READINESS REVIEW PROCESS

The readiness review process is a series of reviews conducted at points of increasing program maturity. The reviews provide assurance to the SMC/CC that the system component being fielded merits certification for flight. The readiness reviews are to be planned sufficiently in advance of the reviews in order to determine which reviews will be held, and to marshal and schedule the necessary resources. The SV and/or LV SPO will coordinate and meet with SMC/EN to agree on a mature review plan. This coordination better ensures deconfliction of readiness reviews for the various systems under review.

The review process order is as follows:

1. Executive Incremental Readiness Review (eIRR)

2. Executive Mission Readiness Review (eMRR)

3. Post-FRR Communication Plan Review (PFCPR)

4. Flight Readiness Review (FRR)

5. Operational Readiness Review (ORR)

6. Executive Readiness Review (ERR)

7. Post-Flight Review (PFR)

8. Certification Readiness Review (CRR) eIRR – To support a future readiness review, especially an FRR, the SPO may provide as many eIRRs as necessary to the SMC/CC, at the discretion of the SPO and SMC/CC. An eIRR is not a decision brief and is provided to increase SMC/CC awareness regarding the program status as the flight article matures. This review is optional and tailorable to the needs of the program under review.

eMRR – The SV or payload SPO conducts an eMRR at a time when it is cost, schedule and risk effective to delay the overall mission if necessary. This is also an ideal review to present just prior to shipping a hosted payload for integration with the host SV. The timing of this review can vary from program to program, but should be nominally two to four weeks prior to SV or payload ship. The eMRR can be held prior to removing equipment from storage, shipping an SV to the launch site, LV integration, fueling the SV at the launch site, or other point(s) in time appropriate for the program conducting the readiness review to certify program readiness to proceed toward launch. This review is optional and tailorable to the needs of the program under review.

PFCPR – The SV SPO briefs the PFCPR to present how the SMC SV SPO will communicate SV or hosted payload status to SMC/CC during the critical phase between the FRR and the end of Early Orbit Test (EOT). The periodicity, content, and source of communications to SMC/CC will be briefed for approval. It is encouraged that the Post-FRR Communication Plan (PFCP) will be presented as part of another readiness review, with the latest acceptable point of completion being the FRR. This review is mandatory, and additional details have been included in the FRR section, 5.3.5.

FRR/ORR – The MD or designee coordinates with SMC/EN NLT two months prior to launch to produce the FRR. The FRR is presented to the SMC/CC approximately 7 to 14 days before launch. An ORR is also presented by 14AF Space Wings that will provide the ground range system status and its ability to support the launch. The Range and Network Program Office will assist the 14th with assurance of the range systems technical baseline (hardware, software, technical orders and spares). For launch services provided outside of 14AF, such as FAA licensed launches, the launch site and range service providers are to participate to the greatest extent possible as subject matter experts in their systems. These reviews are mandatory.

ERR – An ERR is normally conducted the day before launch between the SMC/CC, 14AF/CC, Aerospace Corporation President, Director of the National Reconnaissance Office (DNRO) (as necessary) and AFSPC/CC. This brief ensures communication of mission risk and SFW certification to AFSPC/CC. This review is mandatory.

PFR – About 60 days after launch, the MD or designee presents the mission PFR to SMC/CC or designee. The PFR will present issues and lessons learned to be considered and implemented for future flights. Note: When another mission with the same family LV is imminent, e.g. Delta IV just launched and the next mission is also using a Delta IV, the SV data for the PFR may not be ready in time to hold a joint PFR prior to the next FRR involving a LV from the same family. In this case, if there has been sufficient time for LV data to be compiled, schedule the LV section of the PFR from the preceding mission prior to the FRR for the upcoming mission, and the SV PFR will be held separately approximately 60 days after launch. This review is mandatory.

CRR – Held as necessary for certification of ICBM motors to transfer to a non-AF customer.

See Figure 4-1 below for the SMC Readiness Review event sequence and timeline.

Figure 4-1 – SMC Readiness Review Sequence and Timeline

4.1. ADMINISTRATION APPLICABLE TO ALL READINESS REVIEWS

SMC/EN will provide administrative support in managing meeting flow and ensure required actions are tracked through completion. Similar processes will be followed in meeting preparation, logistics, etc.

Each readiness review will normally take place at SMC at the convenience of the SMC/CC or designee. The location will be chosen to accommodate required and optional in-person attendees. Video TeleConference (VTC) lines will be set up to accommodate meeting attendees in remote locations.

SMC/EN will capture and track action items with status and other pertinent documents.

5. DETAILED READINESS REVIEW DESCRIPTIONS

All USAF-developed SVs, LVs, and associated ground systems must be SFW certified that system risks have been resolved, or are known and deemed acceptable per AFSPCI 10-1208. AF SPO Directors for the payload, SV, LV, and ground systems certify their respective systems to the SMC/CC. The SMC/CC is the SFW certification official for overall AF-managed space or missile missions, and the LV certification official for other agency satellite missions outside of the Air Force, such as the NRO, Navy, and National Aeronautics and Space Administration (NASA). The MD is responsible for the stacked SV and LV on the day of launch. The figure below outlines the general responsibilities.

eIRR

• Build to FRR

• Ad hoc timing eMRR

• Entire mission review

• 14 days before SV ship

PFCPR

• Review how status comm will flow

• Usually coincident with FRR

FRR

• Focus on flight

• Launch ‐ 7‐ 14 days

ORR

• Range readiness

• Launch ‐ 7‐ 14 days

• Usually coincident with FRR

ERR

• Executive brief to

AFSPC/CC

• Launch ‐ 1‐ 14 days

PFR

• Capture lessons learned

• Launch + 60 days

La u n ch

R e vi e w P la n

Figure 5-1 – Certification and Day of Launch Responsibilities

At each readiness review, the SPO Director ensures compliance with the SFWC applicable to the system up to that particular point in the program lifecycle through use of LV Mission Assurance (LVMA) and/or SV Mission Assurance (SVMA); see AFSPCI 10-1208 for additional details. At the FRR, compliance with the SFWC and readiness of each mission critical element to proceed is confirmed by SFW letters from the LV and SV SPOs; sample SFW letters are in Appendices 7 and 8. After the FRR, the SMC/CC formally certifies to the AFSPC/CC that the integrated AF mission, or the AF elements of a non-AF mission, by way of a SFWC letter which explicitly states the SMC/CC certifies space flight worthiness of the mission. A sample SMC SFWC letter template is found in Appendix 9. The certification is then provided to the launch wing commander at the commander’s Launch Readiness Review.

It is the task of the SV and LV SPOs to tailor this process to fit the needs of the assigned mission, however the steps of this complete process capture the critical elements that better ensure a successful launch.

The launch manifest and the schedules of senior decision makers determine when readiness review presentation meetings can be held. The challenge is to ensure this process flows smoothly given the various stakeholders, risks and time constraints.

An outline of each readiness review is provided in Table 5-1, with a detailed description of each event following.

Table 5-1 – Readiness Reviews

Review Purpose Timing Conducted by Presented to Approval Authority eIRR Incrementally build upon the SMC/CC knowledge and understanding of system development

Ad hoc, to support

FRR

SPO Director or designee

SMC/CC N/A –

informational brief eMRR Programmatic assessment of overall mission safety, suitability, and effectiveness; IRRT report, and other reports briefed to SMC/CC for concurrence with SPO Director decision

Multiple points where this briefing is appropriate

SPO Director SMC/CC or designee

SMC/CC

PFCPR Present Post-FRR communication plan

Presented concurrently with the FRR, at the latest; may be presented earlier in process

SV SPO SMC/CC SMC/CC

FRR Space Flight Worthiness Certification

Readiness of whole mission to proceed to launch, including launch site processing and range services

Following integration

Before Launch Readiness Review

Mission Director SMC/CC SMC/CC

ORR Verify ground systems supporting the mission are space flight worthy and ready to support the launch

Typically presented concurrently with the FRR

Launch site processing and range services providers

14AF/CC

and/or

SMC/CC

14AF/CC or SMC/CC when non-14AF services are provided

ERR Informational brief to the AFSPC/CC Soon after FRR;

prior to launch

SMC/CC AFSPC/CC AFSPC/CC

PFR Identify and document lessons learned from the launch campaign and how lessons learned will be implemented in future missions and USAF products and processes

Initial review typically within 60 days after launch

Mission Director or designee

SMC/CC or designee

NA

CRR Subsystem certification brief to the

SMC/CC

As required SPO Director or designee

SMC/CC SMC/CC

5.1. EXECUTIVE INCREMENTAL READINESS REVIEW (EIRR)

5.1.1. PURPOSE

The purpose of the eIRR is to break up the content the SMC/CC would receive at the final FRR across multiple meetings when the scope of the content would cause the FRR to be exceedingly long. As such, the eIRR is considered an optional meeting and is scheduled at the discretion of the appropriate SPO or the SMC/CC. The eIRR is an informational meeting convened to provide an incremental basis of understanding on program status to the SMC/CC leading up to the FRR.

This is an ideal review in which to discuss incorporation of lessons learned from prior flights of in-family hardware. eIRRs begin as the SV or LV nears readiness for the launch campaign, the hosted payload nears readiness for integration with the host SV, and the SV, hosted payload, LV program manager or the SMC/CC deems a need for an eIRR.

eIRRs are usually convened to brief:

1. First-of-a-series system or end-item

2. Major modifications or block changes to a system or end-item

3. Over one year has elapsed from a previous flight of same model SV, hosted payload or

LV

4. Recent major anomaly on any same or relevant system or end-item

5. New ground system or major modification of ground system in support of space systems

6. When decided by the SMC/CC to convene an eIRR

5.1.2. ATTENDEES

If convened, required attendees are:

1. SMC/CC

2. SV or hosted payload, GS, range and/or LV SPO and supporting program office staff

3. SMC/EN

4. IRRT lead or designee

5. SMC/SE

6. Mission Assurance organization supporting the program office (i.e. Aerospace or

Systems Engineering and Technical Assistance (SETA) contractor)

Optional attendees are:

1. Prime contractor representatives from SV or hosted payload, GS and/or LV program under review

5.1.3. ROLES AND RESPONSIBILITIES

The roles and responsibilities of the required attendees during the eIRR are as follows:

1. SMC/CC

a. Receive information from SV or hosted payload, GS and LV program offices

b. Identify action items for follow-up

c. Provide feedback to program office on program readiness

2. SV or hosted payload, GS, range and/or LV SPO and supporting program office staff

a. Coordinate with involved non-AF customers, agencies and contractors to obtain presentation supporting material

b. Coordinate with SMC Director of Safety (SMC/SE) to ensure safety risks and issues are identified and controlled or mitigated

c. Prepare briefing materials, and submit to the appropriate Readiness Review folder at https://insidesmc.losangeles.af.mil/u?q=1Au or those outside of SMC can e-mail to SMCReadinessReview@us.af.mil; read ahead version NLT two working days prior to the briefing, and final version NLT noon the workday prior to the brief

d. Coordinate with SMC/EN on required and optional attendees

e. Present information to the SMC/CC or designee

f. Capture, review and assign action items during review, and ensure the SMC/EN

Mission Assurance Chief and SMC/IRRT Chief are informed as actions are completed

3. SMC/EN

a. SMC/CC technical authority to summarize compliance

b. Assist program office with preparation for review

c. Distribute read-ahead material link to involved SMC staff

d. Manage the flow of meeting and other administrative tasks

4. IRRT or designated Mission Assurance organization supporting the program office (i.e.

Aerospace, Systems Engineering and Integration (SE&I) or SETA contractor)

a. Provide independent assessment of open issues under review

5. SMC/SE

a. Provide assessment of any open safety issues under review

The optional attendees:

1. Prime contractor representatives from SV or hosted payload, GS and/or LV program under review

a. Support program office with technical background information as necessary

2. Other stakeholders of the mission, e.g. Safety, invited by the SV, hosted payload or LV

SPO

5.1.4. MINIMUM REQUIRED CONTENT

The eIRR scope should focus on items that are settled and stable prior to the FRR and avoid, as much as possible, covering open issues that are in work. Content to include:

1. Readiness Review Plan timeline and scope

2. Action items from previous eIRR, as applicable

3. Overview plan of eIRR content

4. Required content from FRR that could be satisfied incrementally through eIRRs:

a. First flight items, including any identified safety risks

b. Test-like-you-fly exceptions

c. Unverifiable or root cause unknown failures including any potential impact to existing safety risks or any potential new safety risk due to unknown root cause

d. Requirements trace (to include deviations and waivers)

e. Cover satisfied Spaceflight Worthiness Criteria

f. Reach-back open issues

g. Active or recently closed issues since previous review (should be minor role in presentation)

h. Configuration variances

i. Risk assessments

5.1.5. ENTRANCE CRITERIA

The eIRR is a subset of the FRR, with the eIRR presenting as much as appropriately possible of the future FRR. For entrance criteria detail, see FRR Entrance Criteria in Section 5.3.6.

Specifically for the eIRR:

1. Held prior to eMRR

2. Greater than one year has passed since last flight of same hardware family, e.g. Atlas V or GPS IIF

3. Deemed necessary by the SPO or SMC/CC

5.1.6. EXIT CRITERIA

1. Address known risks and mitigation plans

2. Describe action items and expected completions

3. Make progress toward successful exit from FRR; see FRR Exit Criteria in Section 5.3.7

5.1.7. ADMINISTRATION

Typical spacing between eIRRs is approximately 4-6 weeks, and should be concluded prior to the eMRR. Product timeline is depicted in Figure 5-2. The first meeting should outline the plan for covering all required FRR content across the multiple reviews. The SV, GS, range or LV SPO should be prepared for SMC/CC feedback at the first meeting and make appropriate adjustments to schedule and content.

Figure 5-2 – eIRR Timeline

Preparation for and conduct of the eIRR will generate several artifacts for archival by SMC/EN.

Table 5-2 summarizes the artifacts and what organizations create them.

Draft Presentation File

•At 85% level

•Upload to assigned readiness review folder

•NLT two working days prior to brief

Presentation File

•Upload to assigned readiness review folder

•NLT one working day prior to brief

• EN forwards to established distribution eIRR

•Brief to SMC/CC

•EN captures and tracks action items for SPO disposition

Artifacts

•Provide artifacts NLT one week post review

•Upload to assigned readiness review folder

Table 5-2 – eIRR Artifacts

Artifact Artifact Creator Presentation SPO Director Action Items List, if applicable SMC/EN Sign In Sheet SMC/EN

5.1.8. TEMPLATE

See template in SMC/EN library (https://insidesmc.losangeles.af.mil/u?q=1ZC) or contact SMC/EN to obtain a template.

5.2. EXECUTIVE MISSION READINESS REVIEW (EMRR)

5.2.1. PURPOSE

The Executive Mission Readiness Review (eMRR) purpose is to certify that the flight hardware is ready to continue proceeding toward launch at a point in time where it is cost and schedule effective to halt the program to address a significant issue. This optional review is organized by the SPO procuring the system under review. SV SPOs typically present eMRRs, but an LV SPO may also convene this review in the case of a significant issue, such as a new model of LV or a return to flight after a launch failure.

The eMRR is presented to the SMC/CC or designee and is coordinated with the SV, GS, range and LV SPOs, and SMC/EN. Status will be briefed for the LV, SV or hosted payload, ground processing, launch operations, range operations, on-orbit operations and the SV or hosted payload ground system, including facilities and personnel training, experience and certification.

The eMRR is tailorable to mission needs, and can be held prior to removing equipment from storage, shipping the SV or LV to the launch site, shipping the hosted payload for integration with the host SV, LV integration, fueling the SV at the launch site, or other point(s) in time appropriate for the program conducting the readiness review to certify readiness to proceed toward launch. Typically, the SV and LV SPOs hold their own individual MRRs prior to the eMRR. This is an ideal review to hold prior to shipping an SMC procured SV or hosted payload for integration with a non-SMC procured system.

At the conclusion of the eMRR, the SPO requests formal concurrence with the MRR decision.

The SMC/CC may then concur with the MRR decision, if appropriate. Any findings and deficiencies should be corrected or dispositioned prior to the Flight Readiness Review.

The SPO is responsible for organizing the eMRR, coordinating and completing the entry criteria, and presenting a brief that covers all areas of mission preparation for which the AF has full or significant partial responsibility for mission success, including launching hosted flight hardware, and communicating the completion level of the preparation.

5.2.2. ATTENDEES

Required attendees are:

1. SMC/CC

2. SV or hosted payload SPO and supporting program office staff

3. SMC/EN or designee

4. IRRT Lead

5. Mission Assurance organization supporting the program office (i.e. Aerospace, SETA or

SE&I)

6. Payload GS SPO, if different from SV SPO and supporting program office staff

7. LV SPO and supporting program office staff

8. Range and Network SPO and supporting program office staff

9. Launch site ground processing representative

10. Operations representatives

a. AFSPC

b. Space Wing(s)

c. 614 Air and Space Communications Squadron (ACOMS)

d. Range Safety

e. Others as necessary

11. Prime contractor or Launch Service Integration Contractor (LSIC) representatives for the SV, GS and LV

Optional attendee:

1. MD

The following are not necessary when reviewing hosted payload readiness for shipment and integration:

1. Payload GS SPO, if different from SV SPO and supporting program office staff

2. LV SPO and supporting program office staff

3. Range and Network SPO and supporting program office staff

4. Launch site ground processing representative

5. Operations representatives

a. AFSPC

b. Space Wing(s)

c. 614 ACOMS

d. Others as necessary

6. Prime contractor or Launch Service Integration Contractor (LSIC) representatives for the SV, GS and LV

5.2.3. ROLES AND RESPONSIBILITIES

The roles and responsibilities of the required attendees during the eMRR are:

1. SMC/CC

a. Receive the eMRR brief

b. Provide feedback and guidance to the MD and SPOs, as necessary

2. SV or hosted payload SPO and supporting program office staff

a. Present the eMRR brief to the SMC/CC

b. Act as technical authority on SV and related ground system or the hosted payload and the satellite with which it is being integrated

c. Coordinate with involved non-AF customers, agencies and contractors to obtain presentation supporting material

d. Coordinate with SMC Director of Safety (SMC/SE) to ensure safety risks and issues are identified and controlled or mitigated

e. Prepare briefing materials and coordinate with MD

f. Coordinate with SMC/EN on attendees

g. Coordinate and submit presentation material to the appropriate Readiness Review folder at https://insidesmc.losangeles.af.mil/u?q=1Au or those outside of SMC can e-mail to SMCReadinessReview@us.af.mil; read ahead version NLT two working days prior to the briefing, and final version NLT noon the workday prior to the brief

h. Assume responsibility for SV or hosted payload related action items assigned during review, and ensure the SMC/EN Mission Assurance Chief and SMC/IRRT Chief are informed as actions are completed

3. SMC/EN or designee

a. Act as the SMC/CC technical authority to verify compliance

b. Assist MD and program offices with preparation for review

c. Distribute read-ahead material link to involved SMC staff

d. Manage flow of meeting and perform other administrative actions

4. IRRT and designated Mission Assurance organization supporting the program office (i.e.

Aerospace, SE&I or SETA)

a. Provide independent assessments of open issues under review

5. MD or designee

a. Attend eMRR to maintain situational awareness on mission progress

6. GS SPO and supporting program office staff

a. Technical authority on the payload GS if separate from the SV GS

b. Coordinate with involved non-AF customers, agencies and contractors to obtain presentation supporting material

c. Coordinate with SMC Director of Safety (SMC/SE) to ensure safety risks and issues are identified and controlled or mitigated

d. Prepare briefing materials and coordinate with MD

e. Coordinate with SMC/EN on attendees

f. Capture, review and assign GS related action items during review, and ensure the

SMC/EN Mission Assurance Chief and SMC/IRRT Chief are informed as actions are completed

7. LV SPO and supporting program office staff

a. Technical authority on LV

b. Coordinate with involved non-AF customers, agencies and contractors to obtain presentation supporting material

c. Coordinate with SMC/SE to ensure safety risks and issues are identified and controlled or mitigated

d. Prepare briefing materials and coordinate with MD

e. Coordinate with SMC/EN on attendees

f. Capture, review and assign LV related action items during review, and ensure the

SMC/EN Mission Assurance Chief and SMC/IRRT Chief are informed as actions are completed

8. Launch site ground processing representative

a. Technical authority on launch site readiness to process the SV and integrate it with the LV

b. Present readiness of the launch site ground processing facilities and staff to handle the SV and LV

9. Operations representatives and Range and Network Program Manager (PM)

a. Present readiness of operational range facilities, systems, and staff to support mission processing, end-to-end testing, launch and early on-orbit operation

b. Present how post-launch TT&C will be accommodated

10. Prime development contractor(s) from SV, involved ground systems, hosted payload and/or LV program(s) under review

a. Support program office with technical background information as necessary

5.2.4. MINIMUM REQUIRED CONTENT

Verification of the interface compatibility between the SV and LV is required at the eMRR. The following information should be reviewed prior to the eMRR and summarized at the eMRR.

Any areas of concern should be emphasized at the eMRR:

1. The SV or hosted payload program office will:

a. Review the SV or hosted payload test history, anomalies and open items, configuration changes, safety issues, fix-before-launch and IRRT concerns

b. Certify the SV or hosted payload is ready and sufficiently complies with relevant sections of the SFWC to continue pre-launch processing; an SV readiness statement should be prepared which certifies these facts

c. Certify that all SV ground system equipment is ready, established and functioning properly and operators are adequately trained and experienced (not necessary when reviewing a hosted payload just prior to shipment for integration with the host SV); a readiness statement should be prepared which certifies these facts and compliance with relevant sections of the SFWC

2. The payload GS program office will:

a. Review the payload GS test history, anomalies and open items, configuration changes, safety issues, fix-before-launch and IRRT concerns

b. Certify the payload GS is ready and sufficiently complies with relevant sections of the SFWC to continue pre-launch processing

c. Certify that all payload ground system equipment, separate from the SV related GS, is ready, established and functioning properly and operators are adequately trained and experienced

3. The LV SPO will: (not applicable to eMRR for a hosted payload)

a. Review the vehicle/upper stage test history, production or processing anomalies, open items, configuration changes, performance margins and the status of any open fix-before-launch and IRRT concerns; for Space Development launches, the SPO will present what is known to the SPO without inappropriately increasing contract scope to accommodate data review

b. Certify at the eMRR that the LV is ready for SV integration and pre-launch processing and complies with relevant sections of the SFWC; a booster readiness statement should be prepared which certifies these facts

4. The Launch Processing Center Agency, e.g. 30/45 Space Wing (SW), SMC/SD, NASA or commercial launch processing services provider, will:

a. Review the pre-launch activities and assess risk

b. Should certify at the eMRR that pre-launch processing, including ground processing, is ready to begin and complies with SFWC

c. Present the certification if the launch services contractor is not present

5. It is recommended the operational space wings present:

a. Mission roles and responsibilities

b. Pre- and post-launch operations structure

c. A review of the Air Force Satellite Control Network (AFSCN) and other operational networks in their readiness to support the launch

d. Certification that the network readiness schedule supports the anticipated ILC and complies with the SFWC

e. Resource or personnel constraints that could impact support of mission launch, schedule, security, or early on-orbit operations

f. Certification that the launch range is ready and able to support pre-launch, launch, and early on-orbit operations, and compliance with the SFWC

g. Potential scheduling conflicts and contingency operations

h. A launch/range readiness statement which certifies these facts is requested

6. The IRRT or another independent readiness review organization, if available, will present their risk assessment

At the eMRR the SPO Director certifies to the SMC/CC the program readiness to proceed toward launch, and compliance with the SFWC appropriate for that point in time, with full compliance obtained pending closure of open liens and launch limiting actions.

Near the end of the eMRR briefing, individual assessments of system readiness and launch schedule compatibility should be given by the SPOs and major involved agencies, which should include, but not be limited to:

1. SV or hosted payload Program Office

2. Mission assurance FFRDC, SETA or SE&I supporting SMC

3. Hosted payload ground station

4. IRRT

5. Prime contractor(s)

The below would participate in an SV or LV eMRR, but not a hosted payload eMRR:

1. LV SPO

2. Launch Processing Agency

3. Launch Range operations staff

4. On-orbit ground station support including the AFSCN or other command and control and telemetry network(s)

5. SV ground station

At the conclusion of the eMRR the SMC/CC has the option to reject the eMRR and direct it to be re-accomplished at a later date, or to concur with the SPO decision based on the readiness and flight worthiness of the flight hardware and readiness of supporting systems and personnel, or with liens if such liens can be reasonably closed at acceptable cost and schedule risk prior to SV/LV integration.

5.2.5. ENTRANCE CRITERIA

1. The residual safety hazard risk acceptance package has to be coordinated by the program office and SMC/SES and then signed by the proper risk acceptance authority

2. Separate mission segments have satisfactorily completed verification

3. Discrepancies have been addressed, dispositioned, documented and any open items recorded

4. Documented plans exist for addressing and mitigating open issues

5. Hardware shortages have been identified and mitigation plans developed

6. If available, independent readiness reviews of the individual mission segments (e.g., SV, hosted payload, LV, and ground systems) have been completed and are available for review, and open actions and minority dissenting opinions are addressed at the appropriate segment level

7. Current SV, hosted payload and/or LV processing and requirements documents have been released

8. Hardware move plans and processing procedures have been finalized and released

9. All required resources and equipment are identified and certified as ready to support SV, hosted payload, or LV shipment, integration and test operations

10. Segment integration personnel have completed safety and required operations training per relevant instructions, and personnel certifications are current

11. Segment integration and test facilities are available, certified, and ready to support processing

12. Local site system safety engineering and hazard management requirements and procedures are compliant with local and contractor specifications

13. Relevant hazards to the SV, hosted payload, LV, launch and operations facilities, mission personnel, and the public have been identified, reviewed and appropriate contingencies developed and released

14. Hardware pedigree reviews have been completed and findings dispositioned

15. Security plans for the mission have been released and briefed, as appropriate, by the involved SPO(s) and are available for review

16. Processing and operations facility maintenance and inspection reports are current and available

5.2.6. EXIT CRITERIA

Successful completion of the eMRR generally includes the following:

1. Ground Support Equipment (GSE), host satellite (if applicable), LV, and launch support assets have been identified and low-risk workaround plans presented and approved for non-compliant items

2. Range safety plan has been discussed with and approved by the Range Safety Manager

3. Launch site requirements have been discussed and approved

a. Launch site and supporting infrastructure

i. Launch pad

1. Hardware transport equipment

2. Hardware lifting/hoisting equipment

3. Weather protection systems and equipment

4. Laser alignment

5. Hazardous operations

6. Portable and stationary environment control systems (A/C, heating, humidity control, etc.)

7. Telemetry systems

ii. Range

1. Support requirements are understood and met through Universal Documentation System (UDS) process, or similar civil or commercial process

iii. Infrastructure

1. LV, SV and hosted payload processing buildings, as applicable

2. Auxiliary electrical systems

3. Cryogenic liquids

4. Gases

5. Hydraulics

6. Clean rooms

7. Portable and stationary environment control systems (A/C, heating, humidity control, etc.)

8. Ground, airborne and on-orbit vehicle tracking assets used for system integration testing, validation, and telemetry check-outs

b. Non-conformances, deviations, waivers and failure analysis reports have been presented and approved

4. Updated, approved and released flight hardware configuration and assignment records, including field modifications made…