SOO_Appendix B_Design Review Expectations.pdf

SOO # 16879-26-001

ATTACHMENT 1

APPENDIX B

28 July 2026

Statement of Objectives (SOO) Attachment 1 – Performance Parameters

Appendix B – Design Review Expectations AEDC-Arnold AFB: H-1 Heater Modernization

Required Design Reviews

1. Contractor Readiness Review (CRR)

2. Preliminary Design Review (PDR)

3. Critical Design Review (CDR)

4. Final Design Review (FDR)

5. Verification Readiness Review (VRR)

6. System Readiness Review (SRR)

Optional Design Reviews

7. Procurement Readiness Review (PRR)

8. Execution Readiness Review (ERR)

STINFO

DISTRIBUTION A: Approved for public release: distribution unlimited.

IRA-26-1866 Page B1

Design Review Flow and Expectations

The following review requirements shall apply to all standard design reviews (e.g. Preliminary Design Review, Critical Design Review, etc.), but will not apply to optional design reviews (e.g. Procurement Readiness

Review or Execution Readiness Review). Optional reviews may be expedited and the time allotted for each phase of these reviews shall be coordinated with and approved by the Decision Authority prior to scheduling the review.

Step 1

Step 2

Step 3

Schedule Design Review Kickoff Meeting

□ Review Kickoff Meeting date shall be coordinated with and approved by the Air Force Project Manager (AF PM) or designee.

□ Meeting shall be scheduled by the AF PM or designee at least ten working days prior to the agreed upon date to ensure availability of AEDC reviewers.

□ Link to the official review folder location to be used for all review documentation shall be included in the meeting notice.

□ Expected review schedule, including the Review Period end date, Comment Resolution Period end date, and Design Review Meeting date, shall be clearly identified in the meeting notice.

□ Contractor Project Manager (PM) or designee shall submit a complete design review package, including the Review Presentation and all supporting documentation, to the AF PM or designee and the Agreement Officer (AO), as applicable, at least three working days prior to the scheduled Kickoff Meeting date.

□ AF PM or designee and AO, as applicable, will review the contents of the design review package for completeness, readiness, and format to ensure all required entrance criteria have been satisfied.

□ If the design review package is deemed to be unsatisfactory by the AF PM or the AO, the Kickoff Meeting shall be rescheduled to a new date no more than five working days after originally scheduled date.

□ If the design review package is deemed to be satisfactory by the AF PM and AO, the review documentation shall be finalized for the review and posted to the review folder location identified in the meeting notice.

□ All review documentation, including the Review Presentation and all supporting documentation, shall be available to all AEDC reviewers prior to the start of the Kickoff Meeting.

Submit Design Review Package

Conduct Design Review Kickoff Meeting

□ Design Review Kickoff Meeting shall be recorded and/or detailed meeting minutes shall be provided to all attendees.

□ Contractor PM or designee(s) shall briefly present the Review Presentation, including the entrance criteria, and identify where all relevant information is located within the presentation or review documentation.

□ During the presentation, the location, file name, and contents of all supporting documentation within the review folder shall be clearly identified.

□ Following the presentation, the expectations and process for providing and resolving comments shall be clearly identified, including the location of the Comments Log within the review folder.

□ Prior to completing the Kickoff Meeting, the requested Review Period shall be clearly identified, the AEDC reviewers will be confirmed, and the AEDC reviewers will accept or revise the requested Review Period.

□ Review period starts immediately following the closing of the Design Review Kickoff Meeting.

STINFO

IRA-26-1866

Page B2

Design Review Flow and Expectations

Step 4

Step 5

Step 6

Review Period

□ AEDC reviewers shall have a review period of no less than eight working days unless specifically approved by the Decision Authority (DA).

□ If review documentation is added, removed, or revised during the Review Period, the Contractor PM shall maintain a detailed log of all changes to the review documentation and a copy of the originally submitted version of any revised document shall be kept in the review folder for reference.

□ All AEDC reviewers will have all comments submitted to the Comments Log prior to close of business on the last day of the Review Period.

Comment Resolution Period

□ Comment Resolution Period of no more than two working days, unless otherwise approved by the DA, starts immediately following the closing of the Review Period.

□ Contractor PM or designee shall provide a formal response, addressing each comment in good faith and to the best of their knowledge, to each comment.

□ If review documentation is added, removed, or revised during the Comment Resolution Period, the Contractor PM shall maintain a detailed log of all changes to the review documentation and a copy of the originally submitted version of any revised document shall be kept in the review folder for reference.

□ AF PM or designee will distribute the updated Comments Log, including responses for each comment, to the original AEDC reviewers.

□ For each comment, the original AEDC reviewer will evaluate and accept or reject each disposition, including an explanation for each rejected disposition.

□ Comments that cannot be fully dispositioned within the Comment Resolution Period shall be specifically identified for discussion at the Design Review Meeting.

□ If the Comment Log contains excessive unresolved comments following the Comment Resolution Period, as determined by the DA, the review shall be immediately considered unsatisfactory and no Design Review Meeting will be conducted.

Design Review Meeting and Approval

□ Design Review Meeting shall be conducted no more than one working day following completion of the Comment Resolution Period unless otherwise approved by the DA.

□ Meeting shall be scheduled by the AF PM or designee at least five working days prior to the scheduled date to ensure availability of AEDC reviewers.

□ Contractor PM or designee(s) shall clearly and completely present the Review Presentation.

□ Contractor PM shall identify and present each unresolved comment, along with a detailed plan for resolution of each comment, for discussion.

□ For each unresolved comment, the DA will accept, reject, or defer the proposed plan for resolution.

□ For all comments with an accepted or deferred plan for resolution, AF Form 1565 will be updated to identify each item as an Action Item with an agreed upon responsible party and target date for disposition.

□ For all comments with a rejected plan for resolution, AF Form 1565 will be updated to identify each item as a Deficiency with an agreed upon path to closure for each item.

□ Following disposition of all comments using AF Form 1565, AF Form 1683 will be used to document approval or failure of the Design Review.

Page B3

PROJECT 17109

NEXT GEN THRUST MANAGEMENT (NGTM)

C-2 TEST CELL

NOMENCLATURE

Initial – Rough draft of the required documentation that sufficiently demonstrates intended format and content. Documentation should include all known relevant information; however, it is acknowledged that significant amounts of information may still be undetermined or inaccurate. Significant unverified assumptions and placeholders identifying unknown information are acceptable.

Draft – Complete documentation, including all currently known relevant information in an appropriate format, that has not completed a formal peer review or other checking process. Draft documentation may include marked up copies of existing approved documentation as long as all required changes to the document are clearly and completely identified. Documents that are currently undergoing a formal peer review or other checking process are considered to be in the Draft state regardless of where they are in that process. Unverified assumptions may be used, but should be justified as reasonable. Placeholders identifying unknown information may be used, but should be limited and clearly identify when and how the information will be determined and provided.

Preliminary – Documentation that has completed an initial peer review, but has not completed a formal checking process or received final approval for release. Documentation is complete, accurate, and sufficient to support the proposed solution, but may still require minor corrections, changes to formatting, or changes to details not directly impacting the final solution. All assumptions should be verified to the maximum extent possible, and all unverified assumptions should be clearly identified. Bounding assumptions (e.g. worst-case conditions) or explicitly approved assumptions may be considered to be verified. Documents that contain significant unverified assumptions are considered to be in the Preliminary state regardless of where they are in the checking process. Placeholders identifying unknown information should not be used.

Approved – Documentation that has completed a formal peer review or other checking process and received final approval for release. Documentation is complete, accurate, and fully justifies the proposed solution. Documents shall be submitted as a complete and final product, including signatures verifying that the document has been checked and approved, but documentation is not required to be submitted into the CMMS. All assumptions should be verified or explicitly approved.

Final – Documentation that has been approved for release and is ready for execution. TOS documents should be fully approved in the CMMS. Outside Contractor documents shall be submitted as a complete package ready for execution, including signatures verifying that all documents have been checked and approved, but documentation is not required to be submitted into the CMMS.

REQUIRED CONTENT

Each review shall consist of a presentation and supporting documentation meeting all requirements identified the associated design review section unless otherwise approved by the Government.

▪ Presentation or documentation shall include, at a minimum, all information required per the definition of the deliverable in the associated design review section.

▪ Presentation shall include, at a minimum, all information required to be located in the presentation by the identified acceptable format(s).

▪ All other documentation shall be provided in the official Design Review Folder in accordance with the identified acceptable format(s).

▪ If any information is provided in a location or format that is not consistent with identified acceptable format(s), this shall be clearly identified in the presentation as a deviation from the approved Entrance Criteria for Government approval; however, the design review process may proceed.

▪ If any information is not provided, or not provided in the required state of development, this shall be clearly identified in the presentation as a deviation from the approved Entrance Criteria and the documentation shall include written Government approval clearly identifying the associated work product(s) and the approved deviation. Documentation of Government approval shall be available prior to commencing the design review process.

AF Chairperson/Final Approval: Decision Authority or Designee [DA]

AF Representatives: Air Force Project Manager or Designee [AF PM], PMD Technical Advisor or Designee [PMD], Test Group Technical Advisor or Designee [TG], Test Support Squadron Asset Owner or Designee [TSS], Test Squadron Technical Advisor or Designee [TS], ID&C Representative or Designee [TSDI], Civil Engineering Representative or Designee [TSDC], XP Representative or Designee [XP]*

REQUIRED ATTENDEES

Page B4

PROJECT 17109

NEXT GEN THRUST MANAGEMENT (NGTM)

C-2 TEST CELL

SYSTEMS ENGINEERING APPROACH

AGREEMENT AWARD

STATEMENT OF WORK

CONTRACTOR READINESS REVIEW

PRELIMINARY DESIGN REVIEW

CRITICAL DESIGN REVIEW

FABRICATION AND INSTALLATION

VERIFICATION READINESS REVIEW

VERIFICATION, CHECKOUT, AND COMMISSIONING

SYSTEM READINESS REVIEW

CLOSEOUT

PROCUREMENT READINESS

REVIEW

(AS REQUIRED)

EXECUTION READINESS

REVIEW

(AS REQUIRED)

EARLY PROCUREMENT EARLY EXECUTION

Page B5

WORK PRODUCTS TO BE DELIVERED BY CONTRACTOR ACCEPTABLE FORMAT(S) CONCURRENCE

1.1 Comments Log

Provide a Comments Log for this review. Comments Log shall include, at a minimum, the following:

▪ All reviewer provided comments

▪ Resolution or disposition for each comment

▪ Status of reviewer concurrence for each comment

Location: Review Folder Format: Excel Spreadsheet

If a TEMPLATE or EXAMPLE Comment Log is desired, the Government will provide one upon request.

AF PM

1.2 Project Summary

Provide a brief project summary. Summary shall clearly identify, at a minimum, the following:

▪ Purpose of the project

▪ Current scope of the project

▪ Approvals requested as part of this review

▪ Scope changes or clarifications requested as part of this review

▪ Requirements revisions or clarifications requested as part of this review

Location: Presentation Format: Narrative

AF PM

1.3 Entrance Criteria

Provide a list of all required Entrance Criteria with mapping to the satisfying documentation. The list shall include the following:

▪ Identification of all approved Entrance Criteria for this review

▪ Acceptable location and format for each item listed

▪ Presentation slide or file intended to satisfy each item listed

Location: Presentation Format: Table

AF PM

1.4 Deviations from Entrance Criteria

Provide a detailed list of requested deviations from the approved Entrance Criteria.

The list shall include the following:

▪ All Entrance Criteria that are not satisfied by the information presented at this review

▪ Verification of prior Government approval for the deviation (if previously approved)

▪ Requests for Government approval for the deviation (if not previously approved)

If there are no requested deviations, this shall be clearly stated.

Location: Presentation Format: List

TG

2.1 Requirements Documents

Provide a copy of all requirements documents approved for use at the time of this review. Documents shall include, as available, the following:

▪ Other Transaction Prototype Project Agreement (OTP)

▪ Statement of Objectives (SOO) / Performance Parameters (PP)

Requirements documents shall be provided in the original, unaltered state. Any proposed corrections, changes, or other revisions shall be provided separately.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

AF PM

2.2 Statement of Work

Provide a copy of the complete Statement of Work identifying how the Contractor intends to satisfy the approved requirements documents. The Statement of Work shall include, at a minimum, the following:

▪ What specific design, procurement, fabrication, installation, and verification activities will be performed

▪ Codes and standards applicable to each activity

▪ What requirements or acceptance criteria will be applied to each activity

▪ What deliverables will be provided for each activity

▪ How each activity will be verified as correct

▪ What products or documentation will be provided following each activity

Statement of Work shall be provided in the Approved state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

TG

TS

TSS

2.3

Requirements Verification

Requirements Traceability Document

Provide a Requirements Traceability Document to cross-reference the information provided in the current requirements documents and the proposed Statement of Work.

Requirements Traceability shall verify, at a minimum, the following:

▪ All requirements have been addressed by the requirements and activities identified in the Statement of Work

▪ All requirements and activities identified in the Statement of Work are justified by the requirements established in the requirements documents or are specifically identified as derived or additional requirements

Requirements Traceability Document is intended to verify that the Statement of Work is complete, addresses the established requirements, and fully defines the work to be done. Requirements Traceability is also intended to identify all derived and additional requirements for approval. Approval of the Statement of Work, as indicated by a successful review, is provides approval of all identified derived and additional requirements unless otherwise identified by the Government.

Location: Presentation Format: Table

If a TEMPLATE or EXAMPLE Requirements Mapping is desired, the Government will provide one upon request.

TG

TS

TSS

CONTRACTOR READINESS REVIEW (CRR)

ENTRANCE CRITERIA

Review Documentation

Requirements Documentation

Requirements

Page B6

3.1 Work Breakdown Structure (WBS)

Provide a detailed Work Breakdown Structure (WBS) to at least Level 3. WBS shall include, at a minimum, the following:

▪ Level 1 identifies each project phase and/or location

▪ Level 2 as follows:

01 - Project Management 02 - Planning 03 - Design 04 - Procurement 05 - Fabrication / Software Development 06 - Installation 07 - Checkout 08 - Closeout 09 - Risk Tracking and Mitigation

If a given Level 2 section is not applicable to a particular Level 1 phase or location, it may be omitted.

Location: Presentation Format: Table or List

AF PM

3.2 Project Schedule

Provide a copy of the current project schedule. Schedule shall include, at a minimum, the following:

▪ Proposed timing and duration of planning phase

▪ Proposed timing and duration of design phase

▪ Proposed timing for each design review or milestone

▪ Proposed timing and duration of execution phase

▪ Proposed timing and duration of checkout phase

▪ Proposed timing of completion

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF, 11"X17" Format

Location: Review Folder Format: Original File in Native File Format

AF PM

3.3 Risk Assessment Matrix

Identify all known risks associated with both executing in accordance with the recommendation and not executing in accordance with the recommendation. Risk identification shall include the following:

▪ All known risks that could significantly affect the technical solution

▪ All known risks that could significantly affect the project cost

▪ All known risks that could significantly affect the project schedule

▪ Any known or potential funding disconnects

▪ Likelihood of each listed risk

▪ Cost, schedule, or performance impact of each listed risk

Location: Presentation Format: Link to File

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE Risk Assessment Matrix is desired, the Government will provide one upon request.

TG

XP*

3.4 Exit Criteria

Provide a list of all approved Exit Criteria.

Location: Presentation Format: Table or List

AF PM

3.5 Entrance Criteria

Provide a list of Entrance Criteria for the next scheduled review. The list shall include the following:

▪ All Government-identified Entrance Criteria for the next scheduled review

▪ Requested deviations from the Entrance Criteria for the next scheduled review

If no deviations are requested, this should be clearly stated.

Location: Presentation Format: Table or List

AF PM

TG

Programmatic Documentation

EXIT CRITERIA

Agreement that the Statement of Work defines a process capable of satisfying the approved requirements and the stated need.

*Meeting Minutes Signed AEDC-1683 indicating Approval

AEDC-1565 capturing Deficiencies and Action Items.

Agreement that the Statement of Work defines a process that is achievable within the estimated cost and schedule.

Agreement that the technical performance, cost, and schedule risks are acceptable.

Agreement that the Entrance Criteria for the next review are acceptable.

Page B7

Provide a Comments Log for this review. Comments Log shall include, at a minimum, the following:

▪ All reviewer provided comments

▪ Resolution or disposition for each comment

▪ Status of reviewer concurrence for each comment

Location: Review Folder Format: Excel Spreadsheet

If a TEMPLATE or EXAMPLE Comment Log is desired, the Government will provide one upon request.

AF PM

1.2 Deficiencies and Action Items.

Provide an updated status for all previous deficiencies and action items. Update shall include the following:

▪ Copy of the signed AEDC-1565 from the previous review

▪ Updated status for all deficiencies and action items listed

All unresolved deficiencies or action items shall be clearly identified with documentation indicating prior Government approval to move forward.

AEDC-1565

Location: Review Folder Format: PDF

Status List Location: Presentation Format: Table

TG

TS

TSS

1.3 Requirements Documents

Provide a copy of all requirements documents that have been used as the basis for this review. Documents shall include, at a minimum, the following:

▪ Statement of Objectives (SOO) and/or Performance Parameters (PP)

▪ Other Transaction Prototype Project Agreement (OTP)

▪ Contractor Derived Requirements

All requirements documents shall include a revision designation or a date of approval to ensure accurate document control.

Requirements documents shall be provided in the approved and unaltered state. Any proposed corrections, changes, or other revisions shall be provided separately.

All approved changes to the requirements documents from the previous review shall be clearly identified.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

AF PM

1.4 Project Summary

Provide a brief project summary. Summary shall clearly identify, at a minimum, the following:

▪ Purpose of the project

▪ Current scope of the project

▪ Approvals requested as part of this review

▪ Waivers or deviations requested as part of this review

▪ Scope changes or clarifications requested as part of this review

▪ Requirements revisions or clarifications requested as part of this review

Location: Presentation Format: Narrative

AF PM

1.5 Entrance Criteria

Provide a list of all required Entrance Criteria with mapping to the satisfying documentation. The list shall include the following:

▪ Identification of all approved Entrance Criteria for this review

▪ Acceptable location and format for each item listed

▪ Presentation slide or file intended to satisfy each item listed

Location: Presentation Format: Table

AF PM

1.6 Deviations from Entrance Criteria

Provide a detailed list of requested deviations from the approved Entrance Criteria.

The list shall include the following:

▪ All Entrance Criteria that are not satisfied by the information presented at this review

▪ Verification of prior Government approval for the deviation (if previously approved)

▪ Requests for Government approval for the deviation (if not previously approved)

If there are no requested deviations, this shall be clearly stated.

Location: Presentation Format: List

TG

2.1

Design Update

Summary of Changes

Provide a detailed summary of any significant design changes from the previous review. Significant design changes shall include, but are not limited to, changes to the following:

▪ General configuration

▪ Installation location

▪ Installation footprint

▪ Equipment size or capacity

▪ Fabrication method

▪ Materials of construction

▪ Structural loads

▪ Major equipment requirements

Changes resulting in a significant increase in project cost or schedule shall be clearly identified.

Location: Presentation Format: List

AF PM

PRELIMINARY DESIGN REVIEW (PDR)

ENTRANCE CRITERIA

Review Documentation

Page B8

2.2 Assumptions

Provide a current and complete list of all assumptions used in the development of the proposed solution, including assumptions made in individual calculations. The list shall include, at a minimum, the following:

▪ What assumptions or approximations were made

▪ How each assumption or approximations was used

▪ Why each assumption or approximation is considered reasonable

▪ If and how each assumption or approximation will be verified

All changes, including verified assumptions, from the previous review shall be clearly identified. If there are no changes from the previous review, this shall be clearly stated.

Location: Presentation Format: Table or List

Links to additional files are acceptable if required to convey all known information.

TG

TS

2.3 System Interface Diagram

Provide a current System Interface Diagram. The diagram shall identify all external systems that interface directly with the proposed system and shall include, at a minimum, the following:

▪ Clear identification of each interfacing system (e.g. process systems, hydraulic systems, data systems, control systems, electrical power)

▪ Direction of media, information, signal, or power flow between systems

Any changes from the previous System Interface Diagram shall be clearly identified.

Location: Presentation Format: Block Diagram

TS

3.1 Process System Schematics

Provide copies of all process system schematics and P&ID drawings required to clearly depict the significant features of the intended design solution. Drawings shall include, at a minimum, the following:

▪ All applicable design conditions

▪ Applicable code(s) of construction

▪ Relative locations of all equipment and devices in primary flow paths

▪ Proposed external system connections

▪ All line sizes for primary flow paths

Schematics should include all information known at the time of the review, but may lack secondary and maintenance features, such as vents, drains, and auxiliary systems. All schematics required to clearly identify the intended operational configuration of the proposed solution shall be provided in the Preliminary or later state. Any additional schematics or schematics for auxiliary systems may be provided in the Draft or later state.

Location: Presentation Format: Overview Image(s) with Notation

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

TS

3.2 Mechanical Drawings

Provide drawings, sketches, or model images required to clearly depict the intended design solution. Images shall be sufficient to completely identify the following:

▪ General arrangement of the system

▪ Intended installation location of each portion of the system

▪ How the system will fit into the available area

The images shall include the general location major components, including, but not limited to, of the following:

▪ Expected control devices (e.g. control valves or flow restrictions)

▪ Expected flow measurement devices (e.g. flow meters or orifices)

▪ Expected configuration devices (e.g. primary isolation valves)

▪ Expected piping or equipment supports and support structures

▪ Expected major equipment (e.g. pumps, heat exchangers, or test equipment)

Drawings, sketches, or model images provided should contain sufficient detail to clearly establish that the intended design is consistent with the provided schematics and that the intended solution can be accommodated by the available space;

however, complete and detailed drawings are not required. Additional information, such as detailed material callouts and specific system details showing the location and configuration of maintenance features (e.g. high point vents, low point drains, or instrumentation lines) should be provided if available.

Location: Presentation Format: Image(s) with Notation

Links to additional files are acceptable if required to convey all known information.

TS

TSS

3.3 Mechanical Analysis

Provide analysis required to justify that the proposed design solution is generally viable and capable of satisfying the established requirements. Analysis should include, at a minimum, sufficient information to establish the basis of design, such as the following:

▪ Line sizing and wall thickness for primary process lines

▪ Component sizing and selection

▪ Material evaluations

▪ Primary equipment sizing

▪ Primary control device sizing

All analysis shall be provided as a complete report that includes, at a minimum, the following:

▪ Applicable codes and standards

▪ Clear identification of and citation for all inputs, including design conditions

▪ Clear identification of and citation for all evaluation methods

▪ Clear and concise conclusion

Analysis should reflect all information known at the time of the review, but may rely heavily on assumptions and assumed values as long as all unverified values are clearly identified in the Assumptions, including a plan to suitably eliminate uncertainty. All analysis required to clearly identify the proposed solution and justify that it is likely viable shall be provided in the Preliminary or later state. Additional analysis provided for information only may be in the Draft state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

TS

3.4 Structural Drawings

Provide drawings, sketches, or model images required to clearly depict the intended design solution. Images shall be sufficient to completely identify the following:

▪ General size and location of all new or modified foundations

▪ General location and construction of support structures

▪ General location and size of platforms and walkways

Drawings, sketches, or model images provided should contain sufficient detail to clearly establish that the intended design is consistent with the provided schematics and that the intended solution can be accommodated by the available space;

however, complete and detailed drawings are not required. Additional information, such as detailed material callouts and specific fabrication details should be provided if available.

Location: Presentation Format: Image(s) with Notation

Links to additional files are acceptable if required to convey all known information.

TSDC

TSS

Design Approach

Basis of Design

Preliminary Design Documentation

Mechanical Design

Page B9

3.5 Structural Analysis

Provide analysis required to justify that the proposed design solution will not negatively affect existing buildings, structures, or foundations. Analysis shall include, at a minimum, the following:

▪ Evaluation of existing buildings subject to new or increased loads

▪ Evaluation of existing structures subject to new or increased loads

▪ Evaluation of existing foundations subject to new or increased loads

All analysis shall be provided as a complete report that includes, at a minimum, the following for each building, structure, or foundation evaluated:

▪ Applicable codes and standards

▪ Clear identification of and citation for all inputs, including existing loads

▪ Clear identification of and citation for all evaluation methods

▪ Clear and concise conclusion

Analysis should reflect all information known at the time of the review, but may rely heavily on assumptions and assumed values as long as all unverified values are clearly identified in the Assumptions, including a plan to suitably eliminate uncertainty.D6 All analysis required to clearly identify the proposed solution and justify that it is likely viable shall be provided in the Preliminary or later state.

Additional analysis provided for information only may be in the Draft state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

TSDC

3.6

Electrical Power Design

Electrical Power Requirements

Provide a current list of expected electrical power requirements for the system based on the current schematics. The list shall contain, but not be limited to, the following:

▪ Identification of expected powered equipment (e.g. heaters, turbines, refrigeration units, pump motors, valve actuator motors, or other process equipment)

▪ Identification of expected powered utilities and services (e.g. HVAC, lights, speakers, outlets, cranes, or other building utilities)

▪ Estimated power requirements for each piece of listed equipment (e.g. voltage and amperage)

If there are no electrical power requirements, this should be clearly stated.

Location: Presentation Format: Table

Links to additional files are acceptable if required to convey all known information.

TSDC

3.7

Instrumentation & Controls Design

Input/Output Parameters

Provide a current list of expected I/O parameters required to accommodate all controls and instrumentation based on the current schematics. For each parameter, the list shall identify, at a minimum, the following:

▪ Device type (e.g. flow meter, control valve, or pressure transmitter)

▪ Device name as shown on the schematic

▪ The purpose of the I/O parameter

▪ Parameter control or feedback signal types

▪ If the parameter can be locally controlled

▪ If the parameter can be remotely controlled, including identification of the intended control room or control system

If there are no instrumentation and controls parameters, this should be clearly stated.

Location: Presentation Format: Table

Links to additional files are acceptable if required to convey all known information.

TSDI

3.8 Design Drawing Status

Provide a current list of all schematics, P&ID drawings, line diagrams, fabrication drawings, and installation drawings that will be revised, created, or rendered obsolete as a result of the project, including all drawings that must be revised to provide or revise references. List shall include all mechanical, structural, electrical, and controls drawings. For each drawing, the list shall include, at a minimum, the following:

▪ Drawing number

▪ Drawing title

▪ Status of the drawing at the time of this review

▪ Status of the drawing recommended for the next review

If there are no required drawings, this should be clearly stated.

Location: Presentation Format: Table

AF PM

3.9 Analysis Status

Provide a current list of all analysis or calculation packages that will be created or revised as a result of the project. List shall include all mechanical, structural, electrical, and controls analysis. For each analysis or calculation package, the list shall include, at a minimum, the following:

▪ Calculation identification number

▪ Calculation title

▪ Status of the calculation at the time of this review

▪ Status of the calculation recommended for the next review

If there is no required analysis, this should be clearly stated.

Location: Presentation Format: Table

AF PM

4.1

Operations Planning

Operations and Maintenance Plan

Provide a current Operations and Maintenance Plan. Plan shall include, at a minimum, all currently known information for the following:

▪ Operational environment (e.g. conditions, assumptions, constraints, or limitations)

▪ How the system is intended to operate (e.g. local or remote)

▪ How specific control devices will be controlled (e.g. manual or automatic)

▪ Instrumentation required for automatic control

▪ Expected operating conditions (NOT design conditions)

▪ Potential system configurations (e.g. startup, shutdown, maintenance, different users, or different sources)

▪ Required safety features (e.g. permissives or interlocks)

▪ Staffing required for operation

▪ Total cost (staffing, power, and utilities) per hour of operation

▪ All expected routine and preventative maintenance activities

▪ Lock out-tag out requirements for major equipment

▪ Cost (labor and materials) associated with each activity

▪ Frequency that each activity is expected to be performed

▪ Estimated average yearly operating costs

▪ Recommended spare parts

Operations and Maintenance Plan shall be sufficiently developed to indicate that the overall operational and maintenance needs of the system have been considered, but may rely heavily on assumptions and placeholders. At a minimum, the O&M Plan should include all relevant information presented in the review presentation. O&M Plan shall be provided in the Draft or later state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE O&M Plan is desired, the Government will provide one upon request.

TSS

TS

TSDI

Structural Design

Design Status

Page B10

4.2 Verification Plan

Provide a current Verification Plan. Plan shall include all currently known information for the following:

▪ Verification activities that will be performed as part of the project

▪ Type of verification provided by each activity (e.g. analysis, inspection, demonstration, or testing)

▪ Why each verification activity is required (e.g. associated project requirement(s), code, or standard)

▪ Acceptance criteria for each verification activity

▪ Documentation to be provided for each activity to show that each acceptance criteria has been satisfied

Verification activities are not limited by the activities identified in the associated requirements documents. Additional verification activities may be performed as a result of codes and standards, improved safety requirements, or planned risk reduction. Verification activities that are not a result of the associated requirements documents should be clearly identified and include a justification for each activity.

Verification Plan shall be sufficiently developed to indicate that the overall verification needs of the system have been considered, but may rely heavily on assumptions and placeholders. At a minimum, the Verification Plan should include information regarding all verification activities required by the TRD, although execution details may be incomplete. Verification Plan shall be provided in the Draft or later state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE Verification Plan is desired, the Government will provide one upon request.

TG

TS

4.3 System Test Plan

Provide a current System Test Plan. Plan shall include, but not be limited to, all currently known information for the following:

▪ All inspection and testing activities identified in the Verification Plan

▪ Activity in the Verification Plan associated with each inspection or test activity

▪ Specific, step-by-step procedures or instructions that will govern how each activity will be performed (e.g. codes, standards, or work instructions)

▪ Objectives, assumptions, and prerequisites for each test.

▪ Who is responsible, by role, for each step of the test procedure

▪ Equipment and resources required to perform each activity

When referencing outside codes and standards, the specific edition and section of the code or standard being reference should be clearly identified. When no existing codes, standards, or work instructions provide suitable procedures or instructions for conducting an identified inspection or testing activity, the System Test Plan shall provide detailed, step-by-step instructions for how the activity is to be performed.

System Test Plan shall be sufficiently developed to indicate that the overall testing needs of the system have been considered, but may rely heavily on assumptions and placeholders. At a minimum, the System Test Plan should include information regarding all testing activities identified in the Verification Plan, although execution details and specific test points may be incomplete. System Test Plan shall be provided in the Draft or later state.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE System Test Plan is desired, the Government will provide one upon request.

TG

TS

4.4 Requirements Traceability Document

Provide a current Requirements Traceability Document to cross-reference the information provided in the current requirements documents, Verification Plan, and System Test Plan. Requirements Traceability shall verify, at a minimum, the following:

▪ All requirements have been addressed by the requirements and activities identified in the Statement of Work

▪ All requirements and activities identified in the Statement of Work are justified by the requirements established in the requirements documents or otherwise approved

▪ All requirements established in the requirements documents have associated verification activities identified in the Verification Plan

▪ All testing activities identified in the Verification Plan are identified in the System Test Plan

▪ Sufficient documentation will be provided for each verification activity.

Requirements Traceability Document should include all information currently identified in the associated documentation, but placeholders may be used for documentation that is not fully identified yet. If any established requirement does not currently have associated verification activities identified in the Verification Plan, this shall be clearly identified.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE Requirements Traceability Document is desired, the Government will provide one upon request.

TG

TS

TSS

XP*

7.1 Project Schedule

Provide a current project schedule. Schedule shall include, at a minimum, the following:

▪ Timing and duration of planning activities

▪ Timing and duration of design activities

▪ Timing of each required design review or milestone

▪ Timing and duration of procurement activities

▪ Timing and duration of outages

▪ Timing and duration of fabrication activities

▪ Timing and duration of installation activities

▪ Timing and duration of verification activities

▪ Timing of project completion

The schedule shall be exported directly from P6 or Microsoft Project.

The schedule shall be a resource loaded schedule broken down to WBS Level 3 or better.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF, 11"X17" Format

Location: Review Folder Format: Original File in Native File Format

AF PM

7.2 Schedule Changes

Provide a summary of all significant changes to the schedule incorporated after the currently approved baseline schedule. A significant change shall be any change that impacts the overall schedule by more than 10% of the total schedule duration. If multiple schedule changes, in aggregate, impact the overall schedule by more than 10% of the total schedule duration, they may be identified as a single change.

Location: Presentation Format: List

AF PM

Planning Documentation

Verification Planning

Page B11

7.3 Project Cost Estimate

Provide a current project cost estimate. Estimate shall include, at a minimum, all costs associated with the following:

▪ Engineered equipment (e.g. pumps, compressors, switchgear, or transformers)

▪ Commodity items (e.g. valves, fittings, enclosures, breakers, or fasteners)

▪ Commodity materials (e.g. pipe, tube, wire, cable, or structural materials)

▪ Specialty materials (e.g. specialty forgings, castings, or alloys)

▪ Expendable materials (e.g. welding rod or grinding wheels)

▪ Imposed surcharges or tariffs

▪ Design labor

▪ Fabrication labor

▪ Installation labor

▪ Verification labor

▪ Verification utilities

▪ Project Management

The cost estimate shall be a detailed estimate broken down to WBS Level 3 or better.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

AF PM

7.4 Cost Estimate Changes

Provide a summary of all significant changes to the cost estimate incorporated after the currently approved baseline estimate. A significant change shall be any change that impacts the overall estimate by more than 10% of the total estimate. If multiple estimate changes, in aggregate, impact the overall estimate by more than 10% of the total estimate, they may be identified as a single change.

Location: Presentation Format: List

AF PM

7.5 Risk Assessment Matrix

Provide a current Risk Assessment Matrix identifying all known or expected risks associated with execution of the project in accordance with the proposed plans. Risk Assessment shall include the following:

▪ All known or expected risks that could significantly affect the technical solution

▪ All known or expected risks that could significantly affect the project cost

▪ All known or expected risks that could significantly affect the project schedule

▪ Any known or potential funding disconnects

▪ Likelihood of each listed risk

▪ Cost, schedule, or performance impact of each listed risk

▪ Potential mitigation activities for each listed risk

▪ When each identified mitigation activity will be implemented

▪ Adjusted likelihood and impact for each listed risk after mitigation

Location: Presentation Format: Summary Table with Link to File

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE Risk Assessment Matrix is desired, the Government will provide one upon request.

TG

XP*

7.6 Hazard Tracking Log

'Provide a current Hazard Tracking Log identifying all known or expected hazards associated with operation and maintenance of the system in accordance with the proposed plans. Hazard Log shall include the following:

▪ All known or expected hazards that could pose a threat to personnel, equipment, the environment, or operational capability

▪ System, subsystem, or component associated with the hazard

▪ Conditions or events that would cause the hazard

▪ Potential adverse effects as a result of the hazard

▪ Severity of the risks associated with the hazard

▪ Probability of the risks associated with the hazard

▪ Overall risk level associated with the hazard

▪ Potential risk reduction measures and mitigations

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

TS

TSS

7.7 Environmental Impact Analysis

Provide all information required for an Environmental Impact Analysis (AF-813).

Information shall include, but not be limited to, identification of potential effects relating to the following:

▪ Compatible Use / Land Use (e.g. noise, accident potential, or encroachment)

▪ Air Quality (e.g. emissions or state implementation plan)

▪ Water Resources (e.g. quality, quantity, or source)

▪ Safety / Occupational Health (e.g. asbestos, radiation, chemical exposure, explosives, or wildlife)

▪ Hazardous Materials (e.g. use, storage, or generation)

▪ Biological Resources (e.g. wetlands, floodplains, or wildlife protection)

▪ Cultural Resources (e.g. burial, archaeological, or historical sites)

▪ Geology / Soil (e.g. topography, minerals, geothermal, seismicity, or installation restoration programs)

▪ Socioeconomic (e.g. employment projections, population projections, school impacts, or local fiscal impacts)

Contractor is only responsible for providing the information required for the AF-813.

The production and submission of the form will be the responsibility of the AF PM.

Location: Presentation Format: List

If a TEMPLATE or EXAMPLE AF-813 is desired, the Government will provide one upon request.

AF PM

7.8 Exit Criteria

Provide a list of all approved Exit Criteria.

Location: Presentation Format: Table or List

AF PM

7.9 Entrance Criteria

Provide a list of Entrance Criteria for the next scheduled review. The list shall include the following:

▪ All Government-identified Entrance Criteria for the next scheduled review

▪ Requested deviations from the Entrance Criteria for the next scheduled review

If no deviations are requested, this should be clearly stated.

Location: Presentation Format: Table or List

AF PM

TG

Programmatic Documentation

EXIT CRITERIA

Agreement that the proposed design solution and supporting information describes a product that will likely meet the technical requirements.

*Meeting Minutes Signed AEDC-1683 indicating Approval

AEDC-1565 capturing Deficiencies and Action Items.

Agreement that the planned verification activities will likely prove the proposed design solution satisfies the technical requirements.

Agreement that the proposed design solution and supporting information defines a product that is likely achievable within the defined cost and schedule.

Agreement the technical performance, cost and schedule risks for the effort are likely acceptable.

Agreement that the Entrance Criteria for the next review are acceptable.

Page B12

Provide a Comments Log for this review. Comments Log shall include, at a minimum, the following:

▪ All reviewer provided comments

▪ Resolution or disposition for each comment

▪ Status of reviewer concurrence for each comment

Location: Review Folder Format: Excel Spreadsheet

If a TEMPLATE or EXAMPLE Comment Log is desired, the Government will provide one upon request.

AF PM

1.2 Deficiencies and Action Items.

Provide an updated status for all previous deficiencies and action items. Update shall include the following:

▪ Copy of the signed AEDC-1565 from the previous review

▪ Updated status for all deficiencies and action items listed

All unresolved deficiencies or action items shall be clearly identified with documentation indicating prior Government approval to move forward.

AEDC-1565

Location: Review Folder Format: PDF

Status List Location: Presentation Format: Table

TG

TS

TSS

1.3 Requirements Documents

Provide a copy of all requirements documents that have been used as the basis for this review. Documents shall include, at a minimum, the following:

▪ Statement of Objectives (SOO) and/or Performance Parameters (PP)

▪ Other Transaction Prototype Project Agreement (OTP)

▪ Contractor Derived Requirements

All requirements documents shall include a revision designation or a date of approval to ensure accurate document control.

Requirements documents shall be provided in the approved and unaltered state. Any proposed corrections, changes, or other revisions shall be provided separately.

All approved changes to the requirements documents from the previous review shall be clearly identified.

Location: Presentation Format: Link(s) to File(s)

Location: Review Folder Format: PDF

AF PM

1.4 Project Summary

Provide a brief project summary. Summary shall clearly identify, at a minimum, the following:

▪ Purpose of the project

▪ Current scope of the project

▪ Approvals requested as part of this review

▪ Waivers or deviations requested as part of this review

▪ Scope changes or clarifications requested as part of this review

▪ Requirements revisions or clarifications requested as part of this review

Location: Presentation Format: Narrative

AF PM

1.5 Entrance Criteria

Provide a list of all required Entrance Criteria with mapping to the satisfying documentation. The list shall include the following:

▪ Identification of all approved Entrance Criteria for this review

▪ Acceptable location and format for each item listed

▪ Presentation slide or file intended to satisfy each item listed

Location: Presentation Format: Table

AF PM

1.6 Deviations from Entrance Criteria

Provide a detailed list of requested deviations from the approved Entrance Criteria.

The list shall include the following:

▪ All Entrance Criteria that are not satisfied by the information presented at this review

▪ Verification of prior Government approval for the deviation (if previously approved)

▪ Requests for Government approval for the deviation (if not previously approved)

If there are no requested deviations,…