AFNWCNM-HB-63-1128T Technical Design Review.pdf

AFNWC/NM-HB-

programmatic tasks/processes, provide organizational points of contacts, and applicable Air Force directives and guidance. This document does not supersede any government directive, pamphlet or handbook. Individuals using this document should always read and refer to the government references provided for specific guidance.

AFNWC/NM

MMIII PROGRAM OFFICE

PROCESS/SYMMETRY/IMPROVEMENT

Technical Design Review

This reference document is a direct copy of the ICBMSD OI 63-26 that was rescinded on March 16, 2020, and will be valid 1 year from the date of this letter or until an associated AFNWC/NM handbook is published, whichever comes first.

The AFNWC/NM handbook: This reference document will be scaled down to only content which describes the will also produce an AFNWC/NM-specific OI if there are additional directives that need to be produced above and beyond what is already defined in higher-level requirements documentation (DoDI, AFI, AFMAN, AFMCI, OI, etc.)

If this reference document contains conflicting guidance to a higher-level directive (DoDI, AFI, AFMAN, etc.), the higher-level directive takes precedence.

Published: August 16, 2021 OPR Digital Signature:

AFNWC/NMED

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website for the current version of this publication.

BY ORDER OF THE ICBMSD OPERATING INSTRUCTION 63-26

SYSTEM PROGRAM MANAGER 20 January 2012

ICBM SYSTEMS DIRECTORATE

Acquisition

TECHNICAL DESIGN REVIEW

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: This publication is available on the Intercontinental Ballistic Missile

Systems Directorate (ICBMSD) website listed under Command Media, referred to as ICBMSD Command Media website in this publication.

RELEASABILITY: There are no restrictions on this publication.

OPR: AFNWC/NIES Certified by: AFNWC/NIE

(Jeffrey Bean)

Supersedes: New OI Pages: 16

PURPOSE: This ICBMSD Operating Instruction (OI) establishes policies and procedures describing the Intercontinental Ballistic Missile (ICBM) Program Office’s role, methodology, and involvement for managing Technical Design Reviews (TDRs). This OI provides both the program management team and decision authorities a high level roadmap for conduct and management of TDRs and prescribes a rigorous and disciplined approach for the TDR process.

Refer recommended changes and questions about this publication to the Office of Primary

Responsibility (OPR) using the Air Force Form 847, Recommendation for Change of

Publication. This publication does not apply to Air Force Reserve Command Units or the Air

National Guard. Ensure that all records created as a result of this process are maintained in accordance with Air Force Manual (AFMAN) 33-363, Management of Records, and disposed of in accordance with Air Force Records Information Management System (AFRIMS) Records

Disposition Schedule (RDS) located at https://www.my.af.mil/afrims/afrims/afrims/rims.cfm.

1. Background/Overview.

1.1. TDRs are necessary systems engineering activities designed to assess progress within a project relative to its planned technical and/or contractual objectives. Reviews should be conducted at logical transition points in the development effort to assess program health and readiness to proceed on to subsequent phases with acceptable risk.

1.2. This process is applicable to all levels of programs, including Acquisition Category

(ACAT) programs, Prime, Non-Prime, Organic and ―small‖ programs, as well as subcontractor and vendor levels. This OI is intended to be an aid to program management and represents review activities that would normally be expected to occur during most product development efforts.

1.3. The OI describes the process for conducting reviews and audits in major development programs (new starts and major modifications). This process is tailorable, as discussed in

Section 3, to suit the needs of the specific program. It is important to note that tailoring to https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

2 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website reduce reviews can increase risk to the program and should not be done without significant consideration (maturity of requirements and designs, complexity, obsolescence impacts) and senior management level approvals. Based on program requirements, the reviews can be combined and tailored to meet the needs of the program. The duration, extent, and depth of coverage during a review depend on the size, schedule, and budget available to the program.

The type of review will depend on the specific circumstances of each program. The actual time phasing of activities must be tailored to each program. Supporting information, including checklists and a TDR roadmap, is provided as attachments to this document.

1.4. TDRs and audits described in this OI are to be conducted at the appropriate phase of program development. These same types of reviews apply during the sustainment phase of the system, system life extension programs, and modification programs. Figure 1.1. shows an overview of the most common formal TDR and audit processes that are tied to program milestones. Each TDR listed below is described in detail in Attachment 2 TDR Roadmap.

1.4.1. System Requirements Review (SRR)

1.4.2. System Functional Review (SFR), or System Design Review (SDR)

1.4.3. Preliminary Design Review (PDR)

1.4.4. Critical Design Review (CDR)

1.4.5. Test Readiness Review (TRR)

1.4.6. Functional Configuration Audit (FCA), or System Verification Review (SVR)

1.4.7. Production Readiness Review (PRR)

1.4.8. Physical Configuration Audit (PCA)

Figure 1.1. Life Cycle Framework View.

Material Solution

Analysis

Technology

Development

Engineering & Manufacturing

Development

Production &

Deployment

Operations &

Support

Material Development Decision

FRP

Decision Review

LRIP/IOT&E

A B C(Program Initiation) IOC FOC

Pre-Systems Acquisition Systems Acquisition Sustainment

SRR SFR PDR CDR TRR PCAPRRFCA

System Requirements Review (SRR)

System Functional Review (SFR) or System Design Review (SDR)

Preliminary Design Review (PDR)

Critical Design Review (CDR)

Test Readiness Review (TRR)

Functional Configuration Audit (FCA) or System Verification Review (SVR)

Production Readiness Review (PRR)

Physical Configuration Audit (PCA)

Note: Chart depicts the most common reviews.

= Decision Point = Milestone Review

Defense Acquisition Management System

User Needs

Technology Opportunities & Resources

DoDI 5000.02, December 8, 2008

24468-001a

Design Readiness Review

Technical Design Reviews and Audits

ICBMSD OI 63-26 20 JAN 2012 3

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

1.5. During sustainment (Figure 1.2.), these design reviews are also implemented, depending on the size of the program / project. For example, an ACAT program may implement all of these reviews. Small programs may tailor the program plan to implement only a select number of reviews and may combine other reviews into a single meeting (e.g.

PDR and CDR may be combined if the project is a simple design).

Figure 1.2. Development / Verification Approach and Design Reviews.

2. Policies.

2.1. A glossary of references and supporting information is provided as Attachment 1.

2.2. It is the policy of the ICBM Systems Directorate to use the ICBM TDR Roadmap for planning, preparing, conducting, and closing-out TDRs. The details of the roadmap, along with high-level descriptions for each TDR, are contained in Attachment 2 TDR roadmap.

Changes to the attachments do not constitute a revision to this OI.

2.3. A Request for Action (RFA) form and guidelines are used to document questions, concerns, and comments during each TDR and audit. A RFA form and guidelines are provided in Attachment 3.

2.4. Throughout this OI, the term ―TDRs‖ is used to refer to the most common formal technical reviews and audits as described in Section 1. This includes requirements reviews, 4 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website functional reviews, design reviews, test readiness reviews, verification reviews, production readiness reviews, and audits.

2.5. Supporting information, including checklists and a TDR roadmap, is provided as attachments to this document.

3. Responsibilities, Authorities, and Accountability.

3.1. The Program Manager (PM) will:

3.1.1. Have overall responsibility for conducting and managing the TDR process.

3.1.2. Provide resources for conducting TDRs.

3.1.3. Ensure appropriate functional expertise is engaged as needed throughout the

TDR process.

3.1.4. Ensure that program and technical reviews meet program and contract requirements, as well as customer expectations.

3.1.5. Chair or co-chair the TDR, respond to assigned action items, and accept and record new action items.

3.1.6. Assign a Technical Review Lead (TRL).

3.1.7. Approve entrance (Decision to Proceed) into the next phase or activity, if no other Decision Authority (DA) is defined. In some situations approval may be required from a combination of government stakeholder agencies.

3.1.8. Provide the decision to proceed to the next phase, or submit a package to the

Decision Authority for approval.

3.2. The TRL will:

3.2.1. Coordinate the activities of the Program Team (PT) in the execution of TDRs.

3.2.2. Be the focal point for all review preparation activities.

3.2.3. Perform planning, identify the approach to conducting the review, develop entry and exit criteria, conduct the review, and track action items and corrective actions to completion. Exit criteria will include specific closure process for the TDR (e.g., letter from contracting officer, milestone DA, meeting minutes).

3.2.4. Staff and coordinate the plan with Lead Subsystem Engineer or Chief Engineer.

3.2.5. Ensure that all plans / schedules for the TDR are properly coordinated with all appropriate stakeholders and agencies (e.g., National Security Agency, Department of

Energy, Air Force Global Strike Command, Air Force Nuclear Weapons Center

(AFNWC), Nuclear Surety, Users / War-fighter).

3.3. The PT members will:

3.3.1. Develop and present review material under the direction of the TRL.

3.4. The Lead Subsystem Engineer or Chief Engineer will:

3.4.1. Review and coordinate on the TDR plan.

ICBMSD OI 63-26 20 JAN 2012 5

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

3.5. Key players in the processes include all members of the program team, to include representatives from the applicable sustainment and program Integrated Product Team(s)

(IPTs), government agencies, and other organizations as required. It is also desirable to have representatives from the user agency in attendance and suppliers and others as appropriate.

Involvement of other stakeholders is essential for the success of TDRs.

3.6. Other specific roles and tasks performed are documented in the supporting information included in the roadmap itself and in separate OIs covering specific process.

Figure 3.1. TDR Responsibilities Flowchart.

4. Procedures.

4.1. Overview. A SIPOC is a diagram that shows Suppliers, Inputs, Process, Outputs, Customers (SIPOC). A SIPOC for TDR is shown in Figure 4.1. Specific activities, inputs / outputs, and entry criteria and exit criteria for each type of TDR are contained in Attachment

2 ICBM TDR Roadmap and other attachments.

6 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

Figure 4.1. SIPOC – Technical Design Review Process Flow.

Suppliers Inputs Process Outputs Customers

Government agencies

Air Force user organization

Program manager

System engineering

Subcontractors

Authorizing documents

SOW

Tech req docs

IMP/IMS

Defined entry criteria

Defined exit criteria

Defined technical data and work products

Technically qualified reviewers

Conduct

Technical

Design Review

(refer to para 4.2.1 through 4.2.6 for details)

Exit criteria met

RFAs / CARAs

Program and schedule updates

TIMS, CDRLs

Approved meeting minutes

Documented authority to proceed

Government agencies

Air Force user organization

Program manager

Systems engineer

4.2. Implementation of TDR. The implementation process for TDRs is shown in Figure 4.1.

SIPOC – Technical Design Review Process Flow, and Figure 4.2. Common technical review checklists for planning, conducting, and closing TDRs are provided as attachments to this document.

ICBMSD OI 63-26 20 JAN 2012 7

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

Figure 4.2. Implementation of Technical Design Review.

Inputs Process Outputs

Stakeholder requirements Define Plan for Technical Design Review

(para 4.2.1)

Plan for TRB

Product/process definition

TDR plan

Product/process definition

Define Agenda

(para 4.2.2)

Agenda defined

Work products Prepare Review Material

(para 4.2.3)

Material prepared

Review agenda

Review material

Work products

Distribute Review Material

(para 4.2.4)

Data package distributed

Review data package

Conduct Review

(para 4.2.5)

Reviewed minutes

RFAs

Completed exit checklists (as required)

Design decisions

RFAs

Design decisions

Close out RFAs and Obtain Decision to Proceed

(para 4.2.6)

Closed out RFAs

Documented Decision to Proceed

4.2.1. Define Plan for TDR. The structure for planning and conducting the review and recording results of technical reviews is typically characterized by formal review of material as defined in the Statement of Work (SOW), contract, and program plans.

Process activities contained in the planning and development procedures define the reviews by identifying product / process gates in the process flow. Each technical review has entrance criteria, criteria for what must be reviewed, and exit criteria.

4.2.1.1. The TRL will define the tasks associated with the conduct of each review, including responsibilities of personnel involved, review site(s), necessary procedures (e.g., action item closeout), entry and exit criteria, and all required accomplishments. The plan, including entry and exit criteria must be started as early as possible. The contractor is typically required to conduct the review, keep review minutes, and be responsible for tracking all actions to closure.

4.2.1.2. The TRL will ensure a technical review plan that identifies and schedules all contract required TDRs is developed and maintained. The plan is started early prior to each review and is documented as part of the program’s initial planning and scheduled as part of the program Integrated Master

Schedule (IMS) or comparable documents as applicable.

4.2.1.3. Attendance should be designated participants including those involved in the work being reviewed, members of the responsible IPTs, and those

8 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website responsible for completing the entry and exit criteria. Participants should include representatives from all appropriate government stakeholders (including the customer) as well as contractors, subcontractors, vendors, and suppliers.

Participants often include Subject Matter Experts (SMEs) from inside and outside the program to facilitate communication of critical expertise and lessons learned.

4.2.2. Define Agenda. The TRL will define the scope of the review to include:

4.2.2.1. Date, time, and location of review.

4.2.2.2. Security classification level of the review.

4.2.2.3. Purpose and scope of the review.

4.2.2.4. Topics to be covered.

4.2.2.5. Review Team (i.e., representatives of stakeholder and specific SMEs).

4.2.2.6. Schedule of presenters and Time allocations.

4.2.2.7. Presenters.

4.2.2.8. Responsible person to take review minutes.

4.2.2.9. List of expected participants (mandatory reviewers so designated).

4.2.3. Prepare Review Material. For all TDRs, the TRL / PT will ensure the development of technical data and work products to be reviewed. These products will be prepared in advance of the review. Typical products include specifications, drawings, manuals, schedules, design and test data, trade studies, risk analysis, etc. In particular, it is important to increase focus on trade studies and development testing for reducing program risk.

4.2.3.1. The form, format, and content of the presentation material are defined by the contract and SOW, or by the PM.

4.2.3.2. Each review has entrance and exit criteria and criteria for items to be reviewed. Use Attachment 3 Specific Checklists as a starting point, and tailor the template as applicable after conducting a through review of Department of

Defense (DoD) or other customer agency procedures, guidelines, and contractual direction, including all potential issues requiring resolution prior to the review. The entry and exit criteria should be documented as early as possible.

4.2.3.2.1. Entrance criteria detail exactly what events must be accomplished before the review may occur. Typical criteria include the requirement that the preceding reviews be completed and that various contractor and customer entities must submit completed work products specific to each review. The documents must be complete or in a particular draft state, depending on the requirements of the specific review.

4.2.3.2.2. Typical review criteria for work products include: ensuring cross consistency between all documents; ensuring each requirement or design specification is understood by all parties; ensuring the

1231478619C Highlight

ICBMSD OI 63-26 20 JAN 2012 9

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website resultant system will meet program goals; implementing an RFA tracking and resolution mechanism.

4.2.3.2.3. Exit criteria typically include the accomplishment of document cross consistency, full understanding by all parties at the stage of system development, resolution of all questions, problems, and requests for change.

4.2.3.3. The TRL / PT reviews and tailors the TDR checklists for consistency with program and customer needs.

4.2.3.4. The TRL coordinates the tailored checklists with the customer to ensure they are consistent with the work scope.

4.2.3.5. The TDR entry criteria checklist items, as well as criteria for items to be presented, must be reviewed internally and coordinated prior to review. Exit criteria checklist items must be coordinated with customers.

4.2.4. Distribute Review Material. Once the review material is prepared, it is distributed prior to the review. Deliver review package and other documents to all expected participants (as defined by SOW, Contract Data Requirements Lists (CDRLs), and other program plans).

4.2.4.1. Reviewers should go over the material prior to the meeting and make notes of their findings as comments. Depending upon the review type, reviewer feedback prior to the meeting may be required. (Technical peer reviews may be conducted prior to or in conjunction with the design review in accordance with

OI 62-11 Technical Peer Review.)

4.2.5. Conduct Review. The review type determines the method used to perform the review. Reviews are conducted to confirm the progress towards the review goals (e.g.

completeness of planned progress) and to gain authority to proceed to the next review.

Report meeting minutes.

4.2.5.1. Present and review the data package / material defined in 4.2.3.

Presenters are Integrated Product Team (IPT) members responsible for the products, studies, or assessments being reviewed. Reviewers include all participants in the TDR.

4.2.5.2. Action items may result from review of the data and material presented at the meeting. Action items may include requests for clarification of the design, requests for additional data, resolution of apparent conflicts, or other concerns of the review participants. RFA forms (Attachment 3) are used to document actions identified during technical reviews and include a specific action item title and concise description of action, due date, the person responsible for completing the action, etc. For actions identified during configuration audits, refer to ICBMSD OI 62-04 Configuration Audits.

4.2.5.3. For the RFA process (Figure 4.3.), the TRL will:

4.2.5.3.1. Distribute RFA forms and review RFA guideline

(Attachment 3) at the start of each TDR.

1231478619C Highlight

10 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

4.2.5.3.2. Confirm the scope, intent, resolution date, and proposed resolution of the action item with the actionee.

4.2.5.3.3. Collect, review, assign category, and approve RFAs.

4.2.5.3.4. Distribute the list of action items to the review

participants.

4.2.5.3.5. Identify action items required to close out the review, Category 1 (CAT 1), and those that may be disposed of after close out of the review, Category 2 (CAT 2).

4.2.5.3.6. Track all action items (CAT 1 and CAT 2) to closure in accordance with the program’s corrective action or action tracking system. Distribute the results or each RFA as items are completed.

Figure 4.3. Request for Action (RFA) Process Flow.

4.2.6. Closeout of the Review and Decision to Proceed. Closeout of the review involves documenting action items as discussed in 4.2.5. and a formal decision to proceed to the next phase of the program / project. The TRL will:

4.2.6.1. Address and close CAT 1 RFAs. CAT 1 RFAs are those that affect formal approval of the TDR require a closure plan prior to authorization to proceed to the next program / project milestone.

4.2.6.2. Publish review minutes, including action item response plans.

4.2.6.3. Publish a closeout memo when all action items are complete or have resolution plans in place, usually within 30 days after the review or by the date required by contract.

4.2.6.4. Save or archive review data, results, and / or minutes.

ICBMSD OI 63-26 20 JAN 2012 11

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

4.2.6.5. Track RFAs through closure and distribute the results of each item as they are resolved or analysis is completed.

4.2.6.6. Obtain formal approval to proceed and exit. Formal approval should be a letter from the contracting officer stating that the design review is accepted

(i.e. all criteria have been met), providing the status of all issues and RFAs (e.g.

that they are closed or a plan and schedule is in place for their completion), and authorizing the program / project to proceed to the next review in the schedule.

An example of the formal approval is included in Attachment 6.

5. Process Metrics.

5.1. Metrics help to ensure the effectiveness of both the TDR process and the overall systems engineering process and are used by the process owner to determine whether changes to this OI or other processes may be required. Process metrics, listed in Table 5.1., are completed by the TRL for the OPR for this OI.

Table 5.1. Process Metrics.

Metric Title Metric Definition Collection, Analysis and

Reporting Method

Storage

Location

Metric

OPR

Reviews

Accomplished

Number and type of

TDRs accomplished versus planned for the program / project.

Collected after each review to establish the progress over the life of the program plan.

SharePoint AFNWC /

NIES

Review

Format per

ICBMSD OI

63-26

Number of TDRs following the format defined in the OI compared with the number of TDRs that tailor the format.

Collected for each review as percent of reviews following the specified format vs. the percent of tailored review formats

SharePoint AFNWC /

NIES

RFAs per

Program /

Project

Number of RFAs in

CAT 1 and CAT 2 for the program / project

Collected for each review for comparison with

CAT 1 and CAT 2 RFAs for other NIES programs

SharePoint AFNWC /

NIES

Authority to

Proceed

Number of TDRs for which the authority to proceed to the next milestone is granted at the end of the review vs.

the number that have the authority to proceed delayed by need for further action

Collected for each review for comparison with other NIES design reviews

SharePoint AFNWC /

NIES

Effectiveness of review

Number of redesign/test issues that occur post

TDR

Collected after each review

SharePoint AFNWC /

NIES

12 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

6. Products and Records Produced.

6.1. This document is an overview of TDR and audit processes and their interconnections.

Products and records maintained for each review are listed in Table 6.1. Specific products and records produced by other related processes are documented in separate OIs.

Table 6.1. Products and Records Produced for this OI.

No. Product or Record Produced Storage

Location

Reference

Para.

1 TDR plan, agenda, meeting minutes, and distribution list. CM.Net 4.2.1., 4.2.2., 4.2.5.

2 Review package and distribution list. CM.Net 4.2.4.

3 Entry and exit criteria for the meeting. CM.Net 4.2.3.2.

4 RFAs and RFA tracking sheets. CM.Net 4.2.5.; 4.2.6.

5 Tailored Checklists for planning, conducting, and close out of the review.

CM.Net 4.2.3.3.

6 Process metrics (Table 5.1.) for each program / project. See Table

5.1.

5.1.

7 Authorization to proceedas defined in the program plan (e.g.

letter from contracts or meeting minutes).

CM.Net 4.2.6.6.

-- Signature on file -- RYAN L. BRITTON, Colonel, USAF

System Program Manager

6 Attachments

1. List of References and Supporting Information

2. ICBM TDR Roadmap

3. TDR RFA Form and Guidelines

4. TDR Planning Checklist

5. TDR Specific Checklist

6. ICBM Systems Directorate Technical Review Authorization to Proceed Examples

ICBMSD OI 63-26 20 JAN 2012 13

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

AFMAN 33-363, Management of Records, 01 March 2008

MIL-STD-1521, Technical Reviews / Audits for Systems, Equipment, and Computer Software

Standard, (rescinded)

MIL-STD-973, Configuration Management, (rescinded)

OI 62-04 Configuration Audits, 18 April 2011

OI 62-11 Technical Peer Reviews, 26 May 2011

OI 62-12 Technical Trade Studies, 26 May 2011

Precribed Forms

RESERVED

Adopted Forms

RESERVED

Abbreviations and Acronyms

ACAT—Acquisition Category

AFMAN—Air Force Manual

AFNWC—Air Force Nuclear Weapons Center

AFRIMS—Air Force Records Information Management System

CARA—Configuration Audit Request for Action

CAT—Category

CDR—Critical Design Review

CDRL—Contract Data Requirements List

CI—Configuration Item

DA—Decision Authority

DoD—Department of Defense

FCA—Functional Configuration Audit

ICBM—Intercontinental Ballistic Missile

ICBMSD—Intercontinental Ballistic Missile Systems Directorate

IMP—Integrated Management Plan

IMS—Integrated Master Schedule

IPT—Integrated Product Team

MIL-STD—Military Standard

OI—Operating Instruction

OPR—Office of Primary Responsibility

PCA—Physical Configuration Audit

14 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

PDR—Preliminary Design Review

PM—Program Manager

PRR—Production Readiness Review

PT—Program Team

RDS—Records Disposition Schedule

RFA—Request for Action

SDR—System Design Review

SFR—System Functional Review

SIPOC—Suppliers, Inputs, Process, Outputs, Customers

SME—Subject Matter Expert

SOW—Statement of Work

SRR—System Requirements Review

STE—Special Test Equipment

SVR—System Verification Review

TDR—Technical Design Reviews

TIM—Technical Interface Meeting

TRL—Technical Review Lead

TRR—Test Readiness Review

Terms

Category 1 RFA—A Category 1 (CAT 1) RFA is critical to the close of the design review. This category RFA is reviewed and evaluated during the review and is proposed, evaluated by all stakeholders, and a solution decision is reached to close the RFA prior to granting authorization to proceed to the next program / project milestone.

Category 2 RFA—A Category 2 (CAT 2) RFA is not design review contingent, but is applicable to the reviewed material. This category RFA is reviewed and evaluated during the review and the assigned responsible person proposed a plan and schedule to close the action prior to the next program / project milestone. The review DA authorized the program / project to proceed to the next milestone based on the agreed-to CAT 2 RFA close-out plans and schedules.

Contracting Officer’s Technical Representative (COTR)—COTRs serve the government technical business leader, helping to ensure government-contractors provide exactly those products and services the government needs. There are three central facets of a COTR’s role; a technical information conduit, a contracting and regulatory liaison, and a business partnership manager. The changing nature of acquisition work places significant importance on COTR activities. It is essential that all COTRs understand their responsibilities and are provided with appropriate support, training , and developmental tools to perform these responsibilities.

Critical Design Review (CDR)—A Critical Design Review (CDR) is conducted for the overall system or sub-systems, each Hardware Configuration Item and Computer Software

Configuration Item when their detailed design is essentially complete and before fabrication, production, or software release. The CDR confirms that the system design is ready for production and that all environmental, health, and safety issues have been resolved.

ICBMSD OI 63-26 20 JAN 2012 15

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

Physical Configuration Audit (PCA)—The Physical Configuration Audit (PCA) is a technical examination of a designated configuration item to verify that the as-built item conforms to the technical documentation that defines the configuration item. The PCA audit is typically conducted before delivery.

Preliminary Design Review (PDR)—The Preliminary Design Review (PDR) is a formal technical review of the basic design approach for a complete system, a Configuration Item (CI), or for functional configuration items. It is typically held after hardware and software development specifications are developed for key hardware, software, and Special Test

Equipment (STE) configuration items.

Production Readiness Review (PRR)—The Production Readiness Review (PRR) is conducted following completion of qualification testing, and before approval for deliverable hardware production. PRR reviews the design disclosure, updates based on qualification test results, and adequacy and completeness of acceptance test procedures. PRR confirms the design is ready for production and delivery to the customer.

Program Team—The full team consisting of Government personnel and contractors, as defined by the program.

System Functional Review (SFR), or System Design Review (SDR)—The System Functional

Review (SFR) or System Design Review (SDR) is conducted to evaluate the optimization, traceability, correlation, completeness, and the risk of the allocated requirements, including the corresponding test requirements, in fulfilling the system / segment requirements (the functional baseline).

System Requirements Review (SRR)—The System Requirements Review (SRR) is normally conducted by an IPT after the accomplishment of functional analysis and preliminary requirements allocation. The goal is to confirm the customer requirements baseline, the direction of the systems engineering management effort, and the convergence upon an optimum and complete configuration.

System Verification Review (SVR), or Functional Configuration Audit (FCA)—The System

Verification Review (SVR) or Functional Configuration Audit (FCA) is a formal audit to validate that the development of a configuration item has been completed satisfactorily and that the item has achieved the performance and functional characteristics specified in the functional or allocated configuration identification. The FCA includes review of completed operation and support documents. It is typically conducted before delivery. The FCA process is described in

OI 62-04 Configuration Audits.

Technical Review Leader (TRL)—Responsibilities of the TRL is frequently included in the role of Contracting Officer’s Technical Representative (COTR).

Test Readiness Review (TRR)—The Test Readiness Review (TRR) is conducted for products to confirm readiness to proceed with significant component, subsystem or system tests. TRR reviews the test objectives, test plan, test procedures, test facility, instrumentation and controls, test operations, data requirements, environment and safety issues, and failure mode and effects.

Valid Comment—A valid comment on the program / project requirements, design, schedule, or other consideration, but is not applicable to the material presented during the review or audit being conducted. These comments are identified during the TDR, but are not categorized as an

16 ICBMSD OI 63-26 20 JAN 2012

Only OIs electronically available on the ICBMSD Command Media website are official. Always refer to the ICBMSD Command Media website

RFA. Each valid comment is recorded in the minutes of the review and referred to the responsible stakeholder for action outside the meeting.