SOO_Appendix B_Design Review Expectations_HPASE.pdf

SOO # 17105-26-001

ATTACHMENT 1

APPENDIX B

21 April 2026

Statement of Objectives (SOO) Attachment 1 – Performance Parameters

Appendix B – Design Review Expectations AEDC-Arnold AFB: High Pressure Air Storage Expansion

Required Design Reviews

1. Contractor Readiness Review (CRR)

2. Conceptual Design Review (CoDR)

3. Preliminary Design Review (PDR)

4. Intermediate Design Review (IDR)

5. Critical Design Review (CDR)

6. Final Design Review (FDR)

7. Verification Readiness Review (VRR)

8. Procurement Readiness Review (PRR)

9. Execution Readiness Review (ERR)

STINFO

DISTRIBUTION A: Approved for public release: distribution is unlimited.

IRA-26-1525 Page B1

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]*

* XP required for TIPP and CTEIP projects only

REQUIRED ATTENDEES

PROJECT

HIGH PRESSURE AIR STORAGE EXPANSION

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 exection, including signatures verifying that all documents have been checked and approved, but documentation is not required to be submitted into the CMMS.

STINFO

IRA-26-1525

Page B2

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 concurrance 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

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 requirements documents. The Statement of Work shall include, at a minimum, the following:

▪ What specific 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

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 Mapping

Provide mapping of requirements between the approved requirements documents and the proposed Statement of Work. Requirements mapping shall verify, at a minimum, the following:

▪ All requirements established in the requirements documents 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 unless otherwise approved by the Government

Requirements or activities in the Statement of Work that are not directly justified by requirements in the provided requirements documents must be clearly identified with a justification as to why the requirement should be included.

Location: Presentation Format: Table

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

TG

TS

TSS

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

CONTRACTOR READINESS REVIEW (CRR)

ENTRANCE CRITERIA

Any required work product not provided for this review, or any work product not provided in the required state, shall have written Government approval for the status of the product prior to commencing the review process.

Documentation of Government approval shall be provided, clearly identifying the associated work product(s).

Review Documentation

Requirements Documentation

Requirements

Programmatic Documentation

Page B3

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

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 B4

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 concurrance 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 indiciating 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 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.

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 Critera.

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)

Location: Presentation Format: List

TG

2.1 Design Approach

Provide a general description of the basic design approach. Design approach shall include, at a minimum, the following:

▪ Detailed scope of the project

▪ Physical boundaries of the project

▪ General description of the proposed solution

▪ Initial system or equipment sizing

▪ Initial material selections

The basic design approach should specifically identify any potential non-traditional fabrication methods (e.g. additive manufacturing).

Location: Presentation Format: Narrative

TG

TS

2.2 Assumptions

Provide a list of all assumptions or approximations used in the development of the proposed solution. 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

Initial simplifying assumptions that cannot be justified are acceptable, but should be clearly identified.

Location: Presentation Format: Table or List

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

TG

TS

2.3 Process Diagram

Provide a flow or line diagram that clearly depicts the significant features of the proposed solution. The diagram shall include, at a minimum, the following:

▪ Expected equipment and devices in the system

▪ Relative locations and connections for expected equipment and devices

▪ Expected external system connections

Location: Presentation Format: Images with Notation

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

TS

2.4 Sketches or Models

Provide sketches or model images depicting the proposed solution. Images shall be sufficient to identify the following:

▪ General arrangement of major equipment

▪ Intended installation location of the system

▪ Area available for installation of the system

Location: Presentation Format: Images with Notation

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

TS

2.5 System Interface Diagram

Provide a 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

Location: Presentation Format: Block Diagram

TS

CONCEPTUAL DESIGN REVIEW (CoDR)

ENTRANCE CRITERIA

Any required work product not provided for this review, or any work product not provided in the required state, shall have written Government approval for the status of the product prior to commencing the review process.

Documentation of Government approval shall be provided, clearly identifying the associated work product(s).

Review Documentation

Conceptual Design

Basis of Design

Concept Documentation

Page B5

2.6 Site Plan

Provide a Site Plan indicating where the work is to be performed. Site Plan shall include, at a minimum, the following:

▪ Visual representation identifying the building or area

▪ Visual representation of where that building or area is located on the base

▪ Visual representation of where within the building or area the work is to be performed

Location: Presentation Format: Images with Notation

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

TG

2.7 Existing Conditions

Provide a description of the existing conditions. Existing condtions shall include, at a minimum, the following:

▪ Systems and resources in the area

▪ Structures and buildings in the area

▪ Utilities in the area

▪ Existing materials

Location: Presentation Format: Narrative or Images with Notation

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

AF PM

2.8

Readiness Assessment

Provide a Technology Readiness Assessment.

Provide a detailed Technology Readiness Assessment. The assessment shall include, at a minimum, the following:

▪ Components, equipment, or technologies that must be developed or leveraged, beyond what is currently readily available, for the project to succeed

▪ Current developmental status of each listed item

▪ Required developmental status of each listed item

Location: Presentation Format: Table or List

TG

TS

3.1 Gap Analysis

Provide a Gap Analysis. Analysis shall include, but not be limited to, the following:

▪ Activities outside the project scope that must be completed for project success

▪ Status for each identified activity (e.g. unfunded, funded, planned, or in progress)

▪ Funding gaps within the project

Location: Presentation Format: Table or List

AF PM

3.2 Verification, Validation, and Acceptance

'Provide a high-level list of VV&A activities required for the proposed solution. List shall identify, at a minimum, the following:

▪ Any expected calibration

▪ Any expected inspections

▪ Any expected testing

▪ Any expected demonstrations

Location: Presentation Format: List

TG

TS

3.3 Hazard List

Provide a Hazard List identifying all known hazards associated with operation and maintenance of the system. The list shall identify the following:

▪ All known 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

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

Location: Review Folder Format: PDF

TG

TS

TSS

3.4 Risk Assessment Matrix

Provide a Risk Assessment Matrix identifying all known risks associated with execution of the project in accordance with the proposed plans. Risk assessment 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

▪ 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*

3.5 Project Schedule

Provide a 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.6 Project Cost Estimate

Provide a current project cost estimate. Estimate shall identify, at a minimum, the anticipated total cost for each of the following:

▪ Major procurements

▪ Design labor

▪ Fabrication materials & labor

▪ Installation materials & labor

▪ Verification labor & utilities

▪ Project management

▪ Overall project

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

Location: Review Folder Format: PDF

AF PM

3.7 Exit Criteria

Provide a list of all approved Exit Criteria.

Location: Presentation Format: Table or List

AF PM

3.8 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

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

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

Risks & Hazards

Planning

Programmatic Documentation

Cost & Schedule

Design Review Criteria

EXIT CRITERIA

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

*Meeting Minutes Signed AEDC-1683 indicating Approval

AEDC-1565 capturing Deficiencies and Action Items.

Agreement that the proposed design solution and supporting information describe a system that is likely achieveable within the defined cost and schedule.

Work Environment

Page B6

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 concurrance 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 indiciating 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 Critera.

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 appoved)

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

2.2 Assumptions

Provide a current list of all assumptions used in the development of the proposed solution. 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

PRELIMINARY DESIGN REVIEW (PDR)

ENTRANCE CRITERIA

Any required work product not provided for this review, or any work product not provided in the required state, shall have Government approval for the status of the product prior to commencing the review process.

Documentation of Government approval shall be provided, clearly identifying the associated work product(s).

Review Documentation

Basis of Design

Page B7

2.4 System Safety Features

Provide a current list of all expected system safety features that will be incorporated into the proposed solution to address identified operational hazards. The list shall include, at a minimum, the following:

▪ Safety features, components, or devices intended to protect personnel or equipment during operation (e.g. barriers, restrictions, or interlocks)

▪ Code-required safety devices (e.g. relief valves or breakers)

▪ Additional safety devices (e.g. temperature control systems or emergency shutdown buttons)

If no special system safety features are required, this should be clearly stated.

Location: Presentation Format: List

TS

2.5 Operating Limits

Provide a current list of any identified safe operating limits for the system as proposed. Limits should address individual crtical parameters and may include, but not be limited to, the following:

▪ Minimum system supply (e.g. pressure or voltage)

▪ Maximum system discharge (e.g. pressure or voltage)

▪ Maximum capacity (e.g. flow rate or power)

▪ Controllable capacity range (e.g. flow rate or power)

▪ Maximum allowable losses associated with unknown or customer equipment (e.g.

pressure loss or resistance)

Identified limits should establish how far beyond the established design parameters the system is still capable of functioning using the proposed design. The limiting factor for each parameters should be identified (e.g. pressure rating, wall thickness, equipment capacity, cable size).

Location: Presentation Format: List

TS

2.6

Work Environment

Site Plan

Provide a current Site Plan indicating where the work is to be performed. Site Plan shall include, at a minimum, the following:

▪ Visual representation identifying the building or work area

▪ Visual representation of where the building or area is located on the base

▪ Visual representation of where within the building or area the work is to be performed

▪ Visual represenation of the location and size of area required for installation

▪ Visual represenation of the location of existing utilities relevant to the project (e.g.

water, steam, natural gas, electrical conduits, high pressure air)

▪ Visual representation of potential encroachment into Explosive Site Plans (ESP) or other known hazardous areas as identified by the Government

Any changes from the previous Site Plan shall be clearly identified.

Location: Presentation Format: Images with Notation

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

TG

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

All schematics required to clearly identify the key features of the proposed solution shall be provided in the Preliminary or later state. Any additional schematics or schematics for auxilliary 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;

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 shall include, at a minimum, 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, including clear identification of all inputs and evaluation methods and a clear and concise conclusion.

All analysis required to justify the proposed design solution shall be 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

Design Approach

System Information

Mechanical Design

Page B8

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 the intended design. 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

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:

▪ Code of Construction

▪ Existing loads

▪ Additional loads expected as a result of the proposed solution

▪ Clear identification of all inputs

▪ Clear identification of all evaluation methods

▪ Clear and concise conclusion

All analysis required to justify the proposed design solution shall be 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 electrical power requirements for the system based on the provided schematics. The list shall contain, but not be limited to, the following:

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

▪ Identification of 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)

Location: Presentation Format: Table

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

TSDC

3.7 Input/Output Parameters

Provide a current list of I/O parameters required to accomodate all controls and instrumentation based on the provided 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

Location: Presentation Format: Table

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

TSDI

3.8 Control Methodology

Provide a detailed narrative describing the high-level control methodology for the proposed solution. Control methodology shall consider all phases of operation, including startup and shutdown, and identify, at a minimum, the following:

▪ Control of specific devices (e.g. manual or automatic)

▪ Instrumentation required for automated control

▪ Permissives or safety interlocks

Location: Presentation Format: Narrative

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

TSDI

3.9 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.10 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

Preliminary Design Documentation

Structural Design

Instrumentation & Controls Design

Design Status

Page B9

4.1

Procurement Planning

Market Research

Provide market research for all major equipment and material procurements. For each procurement, the market research shall identify, at a minimum, the following:

▪ Description and/or Cut Sheet

▪ Anticipated Cost

▪ Anticipated Delivery Time

▪ Potential Vendors

Location: Presentation Format: Table

AF PM

4.2

Procurement Status

Procurement Status

Provide a current list of all procurement documents, including data sheets, equipment specifications, statements of work, or statements of objectives, that will be created or revised as a result of the project. For each procurement document, the list shall include, at a minimum, the following:

▪ Document number

▪ Document title

▪ Status of the document at the time of this review

▪ Status of the document recommended for the next review.

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

Location: Presentation Format: Table

AF PM

4.3 Early Procurement Summary

Provide a current list of procurements that will require release or execution prior to completing the Critical Design Review in order to meet the required schedule or delivery date. For each procurement, the list shall identify, at a minimum, the following:

▪ Equipment or material to be procured

▪ Anticipated cost

▪ Anticipated delivery time

▪ Recommended procurement schedule or release date

▪ Justification for early procurement

▪ Potential risks due to early procurement

▪ Associated procurement documents (e.g. Data Sheet, Specification, SOW, SOO, or Advanced Release BOM)

▪ Schematics and design drawings required to support the procurement documentation

▪ Analysis and calculation reports required to support the procurement documentation

If there are no recommended early procurements, this should be clearly stated.

Location: Presentation Format: Table

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

AF PM

TG

4.4 Procurement Readiness Review

For each procurement intended to be approved for immediate release as a result of this review, provide all documentation and information identified for a successful Procurement Readiness Review that is not otherwise required by the contents of this review.

All procurement documentation shall be in the state required by the Procurement Readiness Review.

Per Procurement Readiness Review AF PM

TS

5.1 Early Execution Summary

Provide a current list of execution tasks, including demoltion, fabrication, installation, or inspection, that will require execution or partial execution prior to completing the Critical Design Review in order to meet the required schedule or delivery date. For each task, the list shall identify, at a minimum, the following:

▪ Task or portion of a task to be executed

▪ Anticipated cost

▪ Recommended execution schedule

▪ Justification for early execution

▪ Potential risks due to early execution

▪ Materials required to support execution

▪ Demolition, fabrication, or installation drawings required to support execution

If there are no recommended early execution tasks, this should be clearly stated.

Location: Presentation Format: List

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

AF PM

TG

5.2 Execution Readiness Review

For each work task intended to be approved for immediate execution as a result of this review, provide all documentation and information identified for a successful Execution Readiness Review that is not otherwise required by the contents of this review.

All procurement documentation shall be in the state required by the Execution Readiness Review.

Per Execution Readiness Review AF PM

TS

6.1 Demolition Plan

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

▪ Scope of demolition effort, including all components or structures to be removed

▪ Demolition methods and how each will be used

▪ Required equipment or machinery

▪ How the remaining existing system will be isolated or reconnected

▪ How the system or structures will be supported or stabilized both during and after demolition

▪ Outages and permits required

▪ Issues, concerns, or limitations associated with demolition (e.g. operations, maintenance, or testing impacts)

Demolition Plan shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

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

AF PM

6.2 Manufacturing Plan

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

▪ Fabrication activities that will be performed

▪ Crafts or specific skills required

▪ Site plan for field fabricaton

▪ Equipment, utilities, or facilities required

▪ Inspection or testing activities required following fabrication

▪ Fabrication and delivery schedule

▪ Issues, concerns, or limitations associated with fabrication (e.g. operations, maintenance, or testing impacts)

Manufacturing Plan shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

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

AF PM

Early Execution

Execution Planning

Procurement Documentation

Early Procurements

Page B10

6.3 Installation Plan

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

▪ Installation activities that will be performed

▪ Crafts or specific skills required

▪ Equipment, utilities, or facilities required

▪ Site plan for locating large equipment (e.g. cranes or lifts)

▪ Specific safety or security considerations associated with installation

▪ Installation schedule

▪ Issues, concerns, or limitations associated with installation (e.g. area, service, operations, maintenance, or testing impacts)

Installation Plan shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

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

AF PM

6.4 Concept of Operations

Provide a current Concept of Operations. CONOPS shall describe how the system is intended to be operated, including, 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, including expected operating conditions (NOT design conditions)

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

▪ Lock out-tag out requirements for major equipment

The CONOPS shall account for all phases of operation, including checkout, pre-ops, operations, and post-ops.

CONOPS shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

If a TEMPLATE or EXAMPLE Concept of Operations is desired, the Government will provide one upon request.

TS

6.5 Operations and Maintenance Plan

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

▪ All expected routine and preventative maintenance activities

▪ 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 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

6.6 Failure Modes and Effects Analysis

Provide a current Failure Modes and Effects Analysis. FMEA shall address, at a minimum, all currently known information for the following:

▪ Failure modes that could result in a non-functional system

▪ Assess the likelihood and impact of each failure mode

▪ Mitigations that could be employed to limit the impact of each failure mode

▪ Assess the likelihood and impact of each mitigated failure mode

FMEA shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

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

TS

6.7 Verification, Validation, and Acceptance Plan

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

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

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

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

▪ Acceptance criteria for each verification and validation activity

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

VV&A Plan shall be in the Draft or later state.

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

Location: Review Folder Format: PDF

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

TG

TS

6.8 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 VV&A Plan

▪ Activity in the VV&A 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 in the Draft or later state.

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

Location: Review Folder Format: PDF

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

TG

TS

Planning Documentation

Operations Planning

Verification Planning

Page B11

6.9 Requirements Traceability Document

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

▪ All capability-level requirements have been addressed by the system-level requirements

▪ All system-level requirements are justified by the capability-level requirements or otherwise approved (e.g. Requirements Review)

▪ All system-level requirements have associated verification activities in the VV&A Plan

▪ All verification activities specifically identified for each system-level requirement in the requirements documents have corresponding verification activities in the VV&A Plan

▪ All inspection and testing activities identified in the VV&A Plan are addressed in the System Test Plan

▪ All verification activities identified in the VV&A Plan that are not directly associated with a system-level requirement are reasonable and justifiable (e.g. code, standard, safety, or risk mitigation)

Any system-level requirement that does not currently have associated verification activities identified in the VV&A Plan 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…