DEPARTMENT OF THE AIR FORCE SMC REGULATION 80012

Headquarters Space and Missile Systems Center (AFMC) June 29, 1995

Los Angeles AFB CA 90009-2960

Acquisition Management

READINESS REVIEW PROCESS FOR SPACE AND MISSILE SYSTEMS

This regulation supplements Commanders Policy SMCR 540-12 (Readiness Reviews) and establishes responsibilities and procedures for implementing the Space and Missile Systems Center (SMC) Readiness Review process for systems utilizing Launch Vehicles (LV) Flight Test of Strategic Missile Weapons Systems and Reentry System Launch Programs (RSLP) for which the Space and Missile Systems Center Commander (SMC/CC), Air Force Program Executive Officer for Space (AFPEO/SPACE), or the Commander for Special Programs (SAFSP/CC) has mission success responsibility. A Memorandum of Understanding (MOU) has been developed between SMC/CC, AFPEO/SPACE, and SAFSP/CC which establishes the relationship and responsibilities of each organization. These systems include (but are not limited to) all space and missile systems acquired under the auspices of the Air Force Materiel Command (AFMC) or the Air Force Program Executive Officer for Space (AFPEO/SPACE) or Strategic Systems (AFPEO/ST) plus other systems under SMC/CC cognizance. The SMC/CC decision to proceed with mission preparations will be based upon the information generated from the readiness review process. This regulation applies to each mission for which SMC has full or partial responsibility for mission success.

1. GENERAL. The SMC mission readiness review process has been established to assure maximum confidence in mission success for SMC missile, spacecraft and launch systems. The process consists of a series of reviews which focus SMC command attention on system readiness at significant points in the launch preparation activity. The review process provides mission readiness visibility as well as an assessment of mission risks and corrective actions to mitigate these risks.

a. The readiness review process allows for incremental assessments of readiness of the system in the five major mission elements of interest: the payload, the launch vehicle

________

Supersedes SMCR 80012, 8 Jan 91

(See signature page for summary of changes.)

No. of printed pages: 12

OPR: SMC/SDE (Lt Col Gordin)

Approved by: Col Charles Whited

Writer-Editor: Jim C. Ray

Distribution: F;X:

(includes upper stage when applicable), the missile, the launch base support and the range and orbital operations support. The readiness review process provides the SMC/CC, AFPEO/SPACE, and SAFSP/CC, or their designees, with the information required to initiate launch preparations. The decision to proceed with launch preparations and ultimately with the launch, must be based on the recommendations and assessments of the responsible program offices, the operating and support agencies and the contractors.

b. There are at least two and at most four readiness reviews for a given launch or mission. At a minimum there are the Mission Readiness Review (MRR) or equivalent FRRs for NASA, and the Launch Readiness Review (LRR). Additionally, the SMC/CC may direct an Independent Readiness Review (IRR), an Independent Preflight Review (IPR) or an Independent Design Review (IDA). See figure 1.

(1) The MRR is a formal Air Force review presented to the SMC Commander, AFPEO/SPACE, or SAFSP/CC. This review evaluates the status of flight hardware, launch and support facilities, range and orbital operations and the readiness and training of the operating personnel before launch preparation activities are initiated. Following this review, the decision will be made whether or not to ship the satellite to the launch pad. The MRR is normally conducted prior to spacecraft integration and system testing with the launch vehicle or prior to test pad processing for missile launch operations. This review also presents data and open issues from FRRs and IRR/IPRs previously conducted. Since the IRR/IPR is completed before the MRR, the status of IRR/IPR open concerns that require corrective action prior to launch will be reviewed during the MRR and subsequent reviews before flight.

(2) The LRR is organized by the Launch Processing Agency to provide a final pre launch assessment of the readiness status of the spacecraft, launch vehicle or missile, range, and the space operations control test center and to certify to the launch and deployment authority (LDA) that the total system (the launch facility, the range, the AFSCN, and the spacecraft integrated to the launch vehicle) is ready to proceed into final countdown. The LRR is chaired by the Launch Base Commander (LDA) at the launch processing site or the Mission Director when a non-Space Command launch site is used. Inputs are supplied by the Booster and Satellite SPOs, and the launch and ground operations contractors. It is normally conducted following integrated systems test at launch day minus 1 (L1 day) for expendable missions and at L2 days for SSP missions. For non DoD Inertial Upper Stage (IUS) SSP missions, the LRR is held at L3 days. For SSP missions the LRR will satisfy the intent of the NASA L1 day review.

(3) A NASA-sponsored FRR is conducted for NASA for those payloads that will utilize the SSP and is done at the launch site about two weeks prior to launch (L2 weeks). The purpose of the review is to assess the status of all NASA and DoD activities and elements necessary for a safe, secure and successful launch, flight and postlanding operation. As part of the FRR, the SMC/CC, AFPEO/SPACE, or SAFSP/CC (or their designee) will certify to NASA that the DoD portion of the cargo element meets all safety requirements and is ready for flight.

(4) An IRR/IPR is required in certain circumstances (see paragraph 3.d). In addition to the above mandatory reviews, the SMC/CC, AFPEO/SPACE, and SAFSP/CC may require, and the SPO Director or the SMC Chief Engineer may request, an Independent Readiness Review (IRR) or an Independent Preflight Review (IPR)- for Class B, C, D programs [Descriptions of Class A, B, C, D programs are described in DOD-HDBK-343 (USAF), Design, Construction, and Testing Requirements For One Of a Kind Space Equipment]- to assess the readiness status of any or all aspects of the mission elements. The IRR/IPR team will be composed of a panel of experts, independent of the program being reviewed, whose purpose will be to identify risks to mission success and safety and to recommend corrective actions for mitigating these risks. The IRR/IPR team will normally be funded by the satellite program office. The team will brief the SMC/CC on the results of their review. Hardware Acceptance Review (HAR) is not the responsibility of the IRR (SPO responsibility.)

[5] An IDA is an assessment of the system (or block change) design by a small panel of broad, highly experienced independent experts. The IDA team shall complete their review and brief the sponsoring agency prior to the start of systems level tests. The IDA evaluation shall encompass the period including PDR, CDR and component level testing and focus on minimizing risks inherent in the system design. It will meet at major system milestones and advise the SPO Director of its findings.

2. RESPONSIBILITIES. The major responsibilities for implementing the readiness review process are given in the following paragraphs. More detailed responsibilities are given in the descriptions under each major readiness review.

a. The Mission Director is responsible for providing mission assurance and conducting the readiness review with the exception of IRR/IPRs. For SMC, AFPEO/Space, and SAFSP/CC payloads or AFPEO/ST missile systems, the Mission Director is normally the satellite or missile program director and is appointed by and reports to SMC/CC, AFPEO/SPACE, or SAFSP/CC. For missions to be launched from a Space Command base, the launch site commander will be the Mission Director for the Launch Readiness Review. For other payloads, the SMC, AFPEO/Space, or SAFSP/CC launch vehicle program director must provide the launch vehicle (including upper stage when applicable), launch base support and the range and orbital operations support readiness assurance to SMC/CC, AFPEO/SPACE, or SAFSP/CC as well as to the designated Mission Director. The Mission Director or launch vehicle program director, as applicable, has responsibility for:

(1) assuring that the sequence of the readiness reviews are incorporated in program planning for all major mission elements and that resources for these reviews have been allocated in the appropriate budget. The Mission Director will ensure that interprogram memoranda of agreement (MOA) documents the resources that are to be provided by each program office in support of the review process, and

(2) assuring to the SMC/CC, AFPEO/SPACE, or SAFSP/CC that all mission functional and support elements are ready to support launch and orbital operations.

b. All programs for which the SMC/CC, AFPEO/SPACE, or SAFSP/CC has mission success responsibility will be structured, funded and managed to enable implementation of the readiness review process. Program offices and operating agencies will develop procedures for conducting and documenting a sequence of reviews that will form the basis for the incremental assessment of mission readiness at key points in the launch preparation process. Documentation must include a continuous audit trail to assure that identified risks are appropriately controlled throughout the review cycle.

c. The SMC Chief Engineer (SMC/SD) or designee will serve as the overall SMC monitor of the mission readiness process and will coordinate executive support for the readiness review process.

d. All organizations whose support is essential to mission success will provide readiness review support as requested by the program directors, the Mission Director or the IRR/IPR co-chairs.

e. The IRR/IPR co-chairpersons are responsible for conducting an independent assessment of mission readiness by a team of experts who are independent of the program being reviewed. The IRR/IPR team will identify risks to safety or mission success and recommend corrective actions. The IRR/IPR team will complete their review and provide both status and final briefings to SMC/CC, AFPEO/SPACE, or SAFSP/CC.

3. MAJOR READINESS REVIEWS. The major readiness reviews will be conducted in accordance with the procedures set forth in the following paragraphs.

a. The Mission Readiness Review (MRR) is a formal review, organized by the Mission Director and conducted by program and support organization personnel to evaluate the readiness status of the total system before final launch preparation activities are initiated. The MRR is initiated for spacecraft before integration, system test, satellite shipment, booster and upper stage processing, or for missiles 6 months before test pad and launch operations begins. For an upper stage, the MRR is conducted 6 months prior to shipment of satellite to launch site For SMC, AFPEO/SPACE, and SAFSP/CC payloads, the Mission Director is responsible for assuring that an MRR is presented to the SMC Commander, AFPEO/SPACE, or SAFSP/CC covering all areas of mission preparation for which SMC/CC, AFPEO/SPACE, or SAFSP/CC is responsible. For other payloads, the SMC, AFPEO, or SAFSP/CC/system program director must provide the MRR to SMC/CC, AFPEO/SPACE, or SAFSP/CC as well as to the designated Mission Director. The Mission Director will certify the program’s compliance with applicable SMC technical regulations.

(1) The Mission Director or system program director (as determined above) will host the MRR(s). For MRRs which are hosted by the launch vehicle program director, an assessment of the readiness assurance of the payload (as defined in sub-paragraph (b) below) is not required. Interface compatibility is required in the review whether the MRR(s) for the spacecraft and launch vehicle are held jointly or separately, they must collectively provide the following information:

(a) The payload or cargo element program office will review the payload test history at the factory, anomalies and open items, configuration changes, safety issues, fix before launch concerns, and Independent Readiness Review (IRR/IPR) concerns. The program director and contractor team will certify that the payload or cargo element is ready for pre launch processing. A satellite readiness statement will be prepared which certifies these facts.

(b) The launch vehicle or upper stage program office must review the vehicle/upper stage factory test history, production or processing anomalies, open items, configuration changes, performance margins and the status of any open fix-before-launch concerns from the IRR/IPR. The launch vehicle or upper stage program director must certify that the launch vehicle is ready for payload integration and pre launch processing. For missions utilizing the Space Shuttle Program, the Launch Agent will review the status of the SSP and provide an assessment of SSP problems which could impact DoD mission objectives and schedules. A booster readiness statement will be prepared which certifies these facts.

(c) The Air Force Space Command (AFSPACECOM) 2nd Space Wing will review the ability of the Air Force Satellite Control Network (AFSCN) to meet the mission support requirements and must certify that the AFSCN's readiness schedule supports the anticipated launch date. The review should address any resource or personnel proficiency problems that could impact support of mission launch, schedule, security or orbital operations. An on-orbit operations readiness statement will be prepared which certifies these facts.

(d) The Consolidated Space Test Center (CSTC) or Consolidated Space Operations Center (CSOC) will review the mission roles and responsibilities, and the pre and post launch operations structure. The adequacy of the mission force controller training and the experience history of key personnel assigned to the mission should be addressed. The review should include the readiness status of the software and hardware, the flight operations schedule and major milestones as well as open items or other issues that could have an impact on the launch schedule or mission success. An on-orbit operations readiness statement will be prepared which certifies these facts.

(e) The Space Command or other Launch Center Processing Agency will review its pre launch activities and must certify that pre launch processing is ready to begin. The test range must certify that it is ready and able to support pre launch and launch operations. Potential scheduling conflicts and contingency operations should be addressed. A launch/range site readiness statement will be prepared which certifies these facts.

(f) Current mission IRR/IPR co-chairs should be at MRR to comment on concern closures.

(g)The Command responsible for Users equipment must certify that all equipment are established and functioning. A readiness statement will be prepared which certifies these facts.

(2) For SMC, AFPEO/SPACE, or SAFSP/CC payloads, or AFPEO/ST missiles, the Mission Director is responsible for organizing the MRR for the SMC Commander or the Commander's designee. For other payloads, responsibility for organizing the MRR lies with the SMC, AFPEO, or SAFSP launch vehicle or missile program director. The MRR briefing will be scheduled by the Chief Engineer's office (SMC/SDE). Six months prior to the MRR, the SMC, AFPEO, or SAFSP Mission (or launch vehicle program) Director will contact the SMC Chief Engineer or designee for guidance on the preparation of all required correspondence and documents. At the conclusion of the MRR briefing, individual assessments of system readiness and launch schedule compatibility are given by the Mission Director and major involved agencies, which will include, but not be limited to, the program offices, the Launch Processing Agency, the Test Range, the FFRDC or SE/TA supporting SMC, the Air Force Space Command Deputy for Operations (AFSPACECOM/DO) and the prime contractor(s). Prior to SMC/CC's, AFPEO/SPACE's, or SAFSP/CC's authorization to proceed with launch activities, the Mission Director and SMC/SDE will coordinate on the preparation of a message from SMC/CC, AFPEO/SPACE, or SAFSP/CC to the Commanders of AFMC and AFSPACECOM, (information copy to AFSPACECOM/DO) and to the payload user certifying the readiness status and reporting the schedule for final launch preparations. The message must be available for the SMC Commander's, AFPEO/SPACE's, or SAFSP/CC's signature at the conclusion of the MRR. The mission director's program office will prepare minutes of the proceedings for SMC/CC's, AFPEO/SPACE's, or SAFSP/CC's approval within 30 days following the MRR but in all cases prior to the Launch Readiness Review. These minutes will document all major points of discussion and assigned action items. The minutes will be approved by the System Program Director, the Program Manager from the FFRDC or SE/TA supporting SMC, the Mission Director, the President of the FFRDC or SE/TA supporting SMC, the SMC Chief Engineer, and the SMC/CC, AFPEO/SPACE, or SAFSP/CC. An information copy of the MRR briefing, the minutes of the MRR and the message will be provided to SMC/SDE and, if appropriate, the AFPEO. The Mission Director is responsible for ensuring closure of all action items. The SMC Chief Engineer will maintain a file of all minutes, presentations, and other pertinent records of each IRR/IPR and MRR. The Chief Engineer of the FFRDC or SE/TA supporting SMC will analyze these files to identify recurring problems or concerns. Any such recurring problems or concerns will be entered into a Concerns Database for access and correlation with other programs. A report will be presented annually to the SMC Chief Engineer on apparent trends in these data.

(3) SMC Pamphlet 80011, Guide for Readiness Reviews, provides procedures for the scope and organization of the MRR.

(4)System program directors will forecast funds required to support a MRR under "risk mitigation". Agreement needs to be formed between the MRR lead and AFPEO/SPACE or SAFSP/CC, as appropriate. The support will include all activities necessary (contractor/MRR team support, etc.) for an MRR.

b. The Launch Readiness Review (LRR) is a formal review, organized by the Space Command launch site Commander or the Launch Processing Agency when a non-Space Command launch site is utilized, which provides a final pre launch assessment of the readiness status of the total system (satellite and launch vehicle), the launch facility, the range and the AFSCN support. Additionally, the LRR verifies the closure of all action items and determines the readiness status of the launch site, range resources, safety, training, weather, and recovery teams. If launch is from a Space Command launch base, the Launch Base Commander has key LRR responsibility. In the case of missions utilizing the Space Shuttle Program (SSP), a Launch Agent assessment must be presented which details SSP problems which could impact DoD mission objectives and schedules. Closure of open items from the MRR must be specifically addressed with emphasis on those requiring closure prior to launch. The supporting FFRDC or SE/TA will provide a letter to the Launch Base Commander verifying launch readiness prior to the LRR. Following integrated systems tests, the time frame for the LRR will be: For SSP missions the LRR is presented on L2 Day, and it satisfies the intent of NASA's L1 Day review. For expendable launch vehicle missions, the LRR is presented on L1 day while for nonDoD IUS SSP flights the LRR is held on L3 day. In the event of a long launch delay, an additional "delta" LRR

is up to the discretion of the LDA. At the conclusion of the LRR after receiving readiness statements from all elements, the Launch Processing Agency representative, the Mission Director and other involved program directors must send a joint message to SMC/CC, or AFPEO/SPACE, or SAFSP/CC, AFMC/CC and the AFSPACECOM Commander (for Air Force operational missions) certifying that the mission is ready to proceed into final countdown. Information copies of this message must be sent to AFSPACECOM/DO, AFPEO/SPACE, and SMC/SD. A statement that the CSTC or CSOC is ready to support or that their support is not required must be included. Similar to the other readiness reviews, funds for the LRR are to be forecast early in the program under “risk mitigation”.

c. The Flight Readiness Review (FRR) is a formal review conducted for NASA for those payloads that will utilize the SSP. It provides an assessment of all DoD and, if applicable, NASA activities and elements necessary for safe processing and launch, flight, and post-landing or re-entry operations. NASA FRR program requirements are included in JSC 07700 Volume VIII, Program Definition and Requirements-Space Shuttle Operations, JSC 07700 Volume XIV, Program Definition and Requirements-Space Shuttle Systems Payload Accommodations, and NSTS 08117 Requirements and Procedures for Certification of Flight Readiness.

(1) Payloads which are hosted by NASA for dedicated DoD SSP missions.

(a) The NASA Associate Administrator for Space Flight (AAOSF) and the DoD Mission Director co-chair this review which is conducted at Kennedy Space Center (KSC) with teleconference to other locations. SMC agencies whose support is necessary to mission success are required to attend.

(b) Prior to the NASA FRR, the Launch Agent will host an Air Force pre FRR. This review is presented to the SMC/CC or the SMC/CC designee. Air Force presentations intended for the NASA FRR must be reviewed and any open issues for discussion with NASA will be evaluated. The Air Force pre FRR will also include a preview of Space Shuttle Vehicle (SSV) status and NASA issues to be presented at the NASA FRR.

(c) At the NASA FRR, the Launch Agent will present DoD cargo or cargo element status and must include the status of all safety requirements as well as mission readiness certification. The test range will present the status of range readiness. The DoD Manager of the SSP (DDMS) Contingency Support Office will present contingency support element status and readiness certification. The SMC/CC (or the SMC/CC designee) must certify to NASA that the DoD portion of the cargo element meets all safety requirements and is ready for flight.

(d) At the conclusion of the FRR, the DoD Mission Director will prepare a message to SMC/CC (information copy to AFPEO/SPACE and SMC/SD) certifying that the mission is ready to proceed into final launch preparations. The Mission Director will prepare a message from SMC/CC to the Commanders of AFMC and AFSPACECOM (information copy to AFSPACECOM/DO and SMC/SD) and to the payload user informing them of SMC/CC decision to proceed with the mission and the schedule for final mission preparation.

(2) DOD Primary Payloads on NASA SSP missions.

(a) The NASA Associate Administrator for Space Flight (AA-OSF) chairs this review which is conducted at Kennedy Space Center (KSC) with teleconference to other locations, SMC agencies whose support is necessary to mission success are required to attend.

(b) Prior to the NASA FRR, the Payload Agent will host an Air Force pre-FRR. This review is presented to the SMC/CC or the SMC/CC designee. Air Force presentatins intended for the NASA FRR must be revieweed and any open issues for discussion with NASA will be evaluated. The Air Force pre-FRR will also include a preview of Space Shuttle Vehicle (SSV) status and NASA issues to be presented at the NASA FRR.

(c) At the NASA FRR, the Payload Agent will present DOD cargo or cargo element status and must include the status of all safety requirements as well as mission readiness certification. The SMC/CC (or the SMC/CC designee) must certify to NASA that the DOD portion of the cargo element meets all safety requirements and is ready for flight.

(3) DOD Secondary Payloads (Cargo Bay and Middeck) on NASA SSP missions.

(a) The NASA Associate Administrator for Space Flight (AA-OSF) chairs this review which is conducted at Kennedy Space Center (KSC) with teleconference to other locations, SMC agencies whose support is necessary to mission success are required to attend as appropriate.

(b) Prior to the NASA FRR, the Payload Agent will review the cargo element status and must include the status of all safety requirements as well as mission readiness certification. For Cargo Bay Payloads (Hitchhikers, Get-Away-Specials), the NASA Goddard Space Flight Center (GSFC) Small Payloads Project Office will review and certify that the DOD portion of the cargo element meets all safety requirements and is ready for flight. For Middeck Payload, SMC/CULH will review and certify that the DOD middeck payload meets all safety requirements and is ready for flight.

(c) At the NASA FRR, the NASA Space Shuttle Program Office will represent the Secondary Payloads and certify that the integrated cargo element meets all safety requirements and is ready for flight.

d. The Independent Readiness Review (IRR)/Independent Preflight Review (IPR) addresses the system's flight readiness. An IRR has the same scope as an MRR but may be tailored to concentrate on specific issues or areas. The SMC Commander's, AFPEO/SPACE's, SAFSP CC's, or System Program Director's decision for conducting an IRR will normally be made to support the start of the IRR when system tests are initiated at about 18 months prior to launch for new launch vehicles, missiles and payloads (including upper stages) and 6 to 9 months for existing launch vehicles and missile systems. The decision will be based upon all information relating to the launch and the written assessment and recommendations of the Mission Director.

IPRs are used exclusively or Class B, C, and D programs which are characterized, to varying degrees, by reduced funding, government oversight and contractor specification and documentation requirements. They differ from IRRs by being limited in scope and staffing to reduce costs. The recommended IPR scope is as follows: Review of mission requirements, system interfaces, critical failure modes, test anomalies and fixes at component and system levels. The recommended FFRDC staffing is 4-5 MTS total, with two review periods following completion of component and system level testing, respectively. The IPR team should report to the SPO following the first review session and reach agreement on steps required to be completed prior to proceeding to system level testing. unresolved issues at this time should be settled at the Mission Director level. The final IPR briefing to the Mission Director is presented following the second review session, at least 30 days before the MRR. The IRR co-chairmen should attend the MRR to comment on their concern closures.

(1) An IRR/IPR must be considered for each mission. Program directors and project officers will identify to SMC/SD their need for an independent review of their system elements when the following circumstances exist: a) first-of-a-series launch vehicle, payload or missile system; b) major modifications to launch vehicle, payload or missile system; c) significant elapsed time from previous flight of same vehicle; d) recent major anomaly on any launch vehicle, payload or missile; e) very high launch cost or nationally significant mission; or f) other factors deserving special review.

Program Directors may request the IRR/IPR be waived if mitigating circumstances exist. The SMC Chief Engineer may also request an IRR/IPR. Four months prior to projected start of spacecraft, missile system or launch vehicle system test, SMC/SDE will submit, for SMC/CC review and approval, a written coordinated recommendation indicating whether an IRR/IPR on any or all elements of the system is required. If an IRR/IPR is requested, this recommendation must include the IRR/IPR scope, a proposed budget and schedule. Prior to review initiation, the IRR/IPRT and Program Office should agree on the scope of the review which is then approved by either SMC/CC, AFPEO/SPACE, or SAFSP/CC. The SMC/CC, AFPEO/SPACE, or SAFSP/CC will nominate a senior field grade AF person or civil service equivalent to co-chair the review. SMC/CC, AFPEO/SPACE, or SAFSP/CC must approve the need for and the scope of the review and appoint the chairperson. The IRR/IPR charter is a letter from the chartering authority (SMC/CC, AFPEO/SPACE, or SAFSP/CC) to the IRR/IPR co-chairs.

(a) The Mission Director may recommend an individual from another directorate to chair the IRR/IPR based on past experience or knowledge. Team leaders should be systems oriented individuals while co-chairs should have IRR/IPR experience and team members are expected to serve for the duration of the review. If no recommendation is made, the SMC Chief Engineer must ask other directorates to identify a person with the time and ability to serve as co-chairperson of the IRR/IPR. The SMC Chief Engineer must alternate nominations for co-chairperson among SPOs as much as possible in the interest of broadening their experience base, and SPOs must cooperate in identifying co-chairpersons promptly. SMC will request a recommended co-chair from the President of the supporting FFRDC. The FFRDC supporting SMC will supply a co-chair who is technically qualified and has previous IRR experience.

(b) IRR/IPRs are conducted by impartial teams of experts from DoD, the supporting FFRDC, NASA, other government agencies, and industry, as appropriate. Upon the SMC Commander's decision to conduct an IRR/IPR, SMC/SD will prepare appropriate letters of notification to the selected chair, and request a co-chair from the supporting FFRDC, and affected SMC offices. The IRR/IPR co-Chairpersons are responsible for selecting the appropriately sized IRR/IPR team. IRR/IPR implementation approaches are detailed in SMC Pamphlet 80011, Guide for Readiness Reviews. It provides procedures and guidelines for the scope and organization of the IRR/IPR. The SMC Chief Engineer will recommend a chairperson for approval by the Commander and arrange for training and documentation.

(2) The team must complete the IRR/IPR in sufficient time and/or establish a report back procedure to allow for timely management actions, but no later than 30 days prior to the MRR. Interim briefings containing specific corrective actions must be briefed to the SPO and appropriate Commanders to insure timely management resolution of recommended actions. Results must be briefed to the SPO Director prior to their formal presentation to the SMC Commander, AFPEO/SPACE, or SAFSP/CC. The results must be documented in a final report with assessments of program readiness together with supporting conclusions and recommendations. The key areas of this briefing and report are the concerns that the IRR/IPR team feels that must be acted upon prior to launch. A concise statement of readiness shall be included. The system program office (SPO) may respond with an assessment of the individual concerns and the concurrence or nonconcurrence of the recommended corrective actions. The IRR/IPR team, with the assistance of the program office(s), will prepare minutes of the IRR/IPR briefing within 30 days for the SMC Commander's, AFPEO/SPACE's, or SAFSP/CC's approval. The minutes must be approved by the IRR/IPR co-chair, the Mission Director, the President of the supporting FFRDC or SE/TA, and SMC/CC, AFPEO/SPACE, or SAFSP/CC. The system program office(s) must close out all action items arising from the briefing. The final report should contain, as a minimum, a hard copy of the final presentation to SMC/CC, AFPEO/SPACE, or SAFSP/CC, a copy of all the concerns generated in the review together with the SPO responses, a copy of the approved minutes, a compilation of the "lessons learned", and a mission risk statement that should be passed on to future chairpersons. The lessons learned database will be automated for easy access. The final report should be sent to SMC/SD (2 copies). SMC/SD will maintain a file of all final IRR/IPR reports, status of all open concerns, as well as the "lessons learned" file. The IRR/IPR team will normally continue until the MRR and in all cases disband at launch. IRR/IPR team members have a responsibility to review and comment on concern closure approaches. The IRR/IPR team will monitor the closure of all concerns documented in the final report by tracking the recommended corrective actions until completed.

(3) The Mission Director will ensure that open concerns from the IRR/IPRs which the IRR/IPR team has designated as "fix before launch" are assessed and briefed at MRR. The SPO Director is responsible to respond to the IRR concerns. The Mission Director will also ensure that concerns from earlier IRR/IPRs which were designated as "fly now/fix prior to next flight" are assessed and briefed at subsequent reviews and closed prior to the current launch.

(4) The IRR/IPR co-Chairs, are responsible for managing within the budget agreed to with the SPO Director. The Program Director is responsible for ensuring appropriate contract coverage and funding the contractor, subcontractor and team.

e. The Independent Design Assessment (IDA) is the earliest form of readiness review and the only one that performs a review of the overall system design. This review is performed, at the discretion of the SMC, AFPEO/SPACE or SAFSP CCs, only for new programs or major block changes for existing programs. The IDA review is initiated at the time of the Preliminary Design Review and is completed just prior to the start of the IRR/IPR.

(1) An IDA must be considered for each new program or major block change of an existing program. Program Directors may request that the IDA be waived if proper justification exists. The SMC Chief Engineer also assesses the need for an IDA. Three months prior to the program Preliminary Design Review, SMC/SD will submit, for MSC/CC review and approval, a written coordinated recommendation indicating whether an IDA is required. The recommendation must include the proposed IDA scope, budget, and schedule. The IDA chartering and co-chair selection procedures parallel those for IRRs/IPRs.

The IDA team consists of a small (5-6) highly experienced team of program directors/managers chartered to counsel the SPO on the cost effective expenditure of their resources early in the program and to provide the SPO access to the IDA team's SMC/FFRDC corporate knowledge. Team members from NASA, other government agencies and industry may be considered if they are specially qualified.

(2) The IDA team should conduct incremental reviews immediately following PDR, CDR and the Component Test Summary Review. They should provide the SPO with their assessment following each review session and reach agreement on the critical issues requiring resolution. Disagreements between the SPO and IDA team on critical issues should be resolved at the Mission Director level. Progress on resolution of critical issues is briefed by the SPO to the IDA team at the beginning of their subsequent review session. A final IDA team report to the Mission Director is in the form of a briefing that occurs just prior to initiation of the IRR/IPR activities. This briefing focuses on open issues that remain for review by the IRR/IPR team and provides an assessment of the readiness of the program to proceed to the system test phase.

SUMMARY OF CHANGES

This revision adds the commander of Special Projects (SAFSP/CC) to the DAC (SMC/CC), and AFPEO/SPACE as the officials responsible for Readiness Reviews. It also emphasizes the fact that contractor support for the readiness reviews be defined in the contract and that appropriate program funds are allocated in the program's budget. Third, the changes establish a guidance for the appropriate time frame for the readiness reviews so that all are briefed at the most effective, useful time. NASA sections have been rewritten to reflect comments from NASA, Houston. BMO sections related to major missile programs have been removed. IDA and IPR descriptions have been added. Finally, team concepts are referenced for the IRR/IPR teams.

FIGURE 1


Type of  Purpose        Timing             Location     Conducted    Presented to:   
                                                        by:                          
Review                                                                               

MRR      Status of      - before launch    SMC, video   Mission      Depending on    
         flight h/w,    prep activities    tele-conf,   Director     mission:        
         launch/support - before test pad  or SAFSP                  - SMC/CC        
          facilities,   and launch ops     facility                  - AFPEO/SPACE   
         etc.           - prior to                                   - SAFSP/CC      
                        integration                                  - NASA Mission  
                                                                     Director        
                                                                     - ARPA Mission  
                                                                     Director        

LRR      Final pre      - L-1 for          Launch       AFSPACECOM   Message to:     
         launch         expendable launch  processing   General      SMC/CC or one   
         assessment     vehicle            site         Officer at   of the above    
                        - L-2 for SSP DoD               launch site  AFMC/CC         
                        - L-3 for non-DoD                            AFSPACECOM/CC   
                        IUS SSP flights                                              

FRR      (1) Assess     (1) L-2 weeks      (1) KSC      (1) NASA     (1) Message     
         state of NASA                                  AA-OSF       to: SMC/CC      
         and DoD                                                                     
         activities                                                  Message from    
                                                                     SMC/CC to:      
                                                                     AFMC/CC         
                                                                     AFSPACECOM/CC   

IRR/IPR  Independent    - before MRR       SMC, video   Independent  SMC/CC or       
         expert review  - from CDR to      tele-conf,   team         PEO/SPACE or    
                        factory system     or SAFSP                  SAFSP/CC        
                        tests; (SMC/CD)    facility                                  
                        - 18 mos prior to                                            
                        launch for new                                               
                        systems                                                      
                        - 3-9 mos prior                                              
                        to launch for                                                
                        existing systems