Appendix E-Addendum to FAR 52.212-1.pdf

APPENDIX E

ADDENDUM TO FAR 52.212-1

INSTRUCTIONS TO OFFERORS

1.0 Program Structure and Objective

1.1.1. The supplies and services provided under this contract will include approximately 608 engines fully configured for B-52H missions (commercial regional/business size jet engines) plus additional spare engines, associated support, support equipment, and data to re-engine the

B52H bomber fleet. Additionally, the contract will include per event and over and above contract line items to address requirements that cannot be known at the time of award, such as maintenance support, transportation, travel, and miscellaneous shipping. The contract minimum is the total of first year of Program Management (XX01). Initial engine quantities are estimated at 16-64 engines to integrate on multiple prototype aircraft plus additional spares. Upon completion of the prototyping phase, the remaining quantity of engines will be acquired over the course of a 6-year base period, a 5-year option, and six 1-year options, with a contemplated

Period of Performance (PoP) of up to 17 years.

1.1.2. Award will be made on the basis of best value utilizing Tradeoff Source Selection

Procedures. Award will be made to the Offeror that provides the best value to the Government In

Accordance With (IAW) Addendum to FAR 52.212-2, Evaluation Factors for Award (Appendix

F).

1.2. Budget/Funding Information

Funding will be obligated as Firm-Fixed Price (FFP) and Fixed Price with Economic Price

Adjustment for the Contract PoP.

1.3 Contractor Technical Proposal

All or parts of the Contractor’s Technical Proposal may be added to the contract. Should there be any discrepancies between the Technical Proposal and the Statement of Work (SOW), the SOW will take precedence unless otherwise approved by the Procuring Activity.

1.4 Supplemental Responsibility Requirements

Facility Clearance Information: The Offeror, and subcontractors working classified requirements with access to classified information, must possess, prior to award, a final facility clearance equal to the highest classification specification (DD Form 254) attached to this solicitation. The

Industrial Security Facilities Database (ISFD) will be used to verify final facility clearances prior to award. Offerors who do not have a final facility clearance equal to the highest classification specification (DD Form 254) attached to this solicitation in the ISFD database prior to the award will be considered non-responsible and will not be eligible for award. Any determination that an

Offeror is non-responsible will be IAW FAR Part 9.

2.0 General Instructions

2.1.1. This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The

Offeror’s proposal shall include all data and information requested by the ITO and shall be submitted IAW these instructions. Any Offeror who submits an incomplete proposal may be considered ineligible for award. The proposal shall be compliant with the requirements as

As of 18 May 2020 stated in the SOW and appendices. Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation.

2.1.2. The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

2.1.3. Elaborate brochures, documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.1.4. The proposal acceptance period is specified in the model contract/solicitation. The Offeror shall make a clear statement in the specified model contract of the proposal documentation volume that the proposal is valid until this date.

2.1.5. IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

2.2. General Information

2.2.1. Point of Contact

The Contracting Officer (CO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification shall be sent to the CO at the address located in the model contract/solicitation.

2.2.2. Debriefings

The CO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, Offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful Offerors IAW FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

2.2.3. Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. This reservation includes matters of additional or substitute pages of the initial proposal.

2.2.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the System for Award

Management (SAM) website at https://beta.sam.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.2.5. Amendments to Solicitation

If this Request For Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the Offeror’s proposal. Any unacknowledged amendments in the Offeror’s proposal will render the proposal ineligible for award.

2.2.6. Submission, Modification, Revision, and Withdrawal of Proposals

Proposals and modifications to proposals shall be submitted in sealed envelopes or packages in paper media and electronic media addressed to the CO showing the time and date specified for receipt, the solicitation number, and the name and address of the Offeror. The CO address is listed below in paragraph 2.7.

2.2.7. Communications

Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information –

See FAR 2.101 & 3.104” in the subject line. Additionally, source selection information may be transmitted via facsimile (encrypted when possible), United States (U.S.) Postal (or like service) delivery, and/or oral with telephonic or face-to-face meetings.

2.3. Organization/Number of Copies/Page Limits

2.3.1. Title Page

The Title Page of each volume shall contain the solicitation number, name, address, and telephone and facsimile numbers of the Offeror and electronic e-mail address if available.

2.3.2. Proposal Organization

The Offeror shall prepare the proposal as set forth in Table 2.1: Proposal Organization. The titles and contents of the volumes shall be as defined in Table 2.1, all of which shall be within the required page limits and with the number of copies as specified in Table 2.1. The attachments identified in Table 2.1 shall be separately bound in three-ring, loose-leaf binders, as necessary.

The contents of each proposal volume are described in the ITO paragraph as noted in Table 2.1.

Table 2.1 Proposal Organization

Volume

ITO

Paragraph

Number

Volume Title

Hard

Copies

Disk

Copies

Page

Limit

I 3.0 Technical (Includes Factors 1 & 2) 10/2 125

3.2.2 Title Page (Not included in 125 page limit) 1

3.2.2 Table of Contents Unlimited

3.2.2 List of Tables and Figures Unlimited

3.2.2 Glossary of Abbreviations and Acronyms Unlimited

2.3.7 Cross-Reference Matrix Unlimited

3.2.3 Subfactor 1 Evaluation Criteria

Not included in page limit:

SF1g – B-52H CERP Step 1 Aircraft

Modification Impact Analysis Summary, B-52H CERP Step 1 Aircraft Modification

Impact Analysis Nuclear Hardening

Summary, OEM's full submission of Other

Transactional Authority (OTA) Project

Deliverable #1 (PD1): Engine Performance

Risk Assessment Report, OTA Project

Deliverable #2 (PD2): Engine Modification

Model Report, OTA Nuclear Hardening

Report.

SF1h – SOW Attachment C, Certification

Basis; Facilities Letter

SF1i – OTA Project Deliverable #3 (PD3):

Logistics/Lifecycle Assessment Report

SF1j – Letter of Intent

SF1k – Small Business Participation

Include as part of

125 page limit

3.2.4 Subfactor 2 Performance Capability Include as

part of

125 page limit

3.3 Technical Risk Include as

part of

125 page limit

3.2.1 Engine Cycle Model (Offeror shall submit

one version, which will apply to Subfactors

1a, 1b, 1c, 1d, 2a, and Technical Risk)

0/4 Unlimited

II 5 Price Volume 3/2 Unlimited

5.1 - 5.3 General Information - Title Page, Table of

Contents, List of Tables & Figures, Glossary of Abbreviations & Acronyms

Unlimited

5.4 Volume Organization Unlimited

III 6 Contract Documentation 3/2 Unlimited

2.2.1 Title Page (SF1449) 1

2.2.7 Table of Contents Unlimited

2.2.8 List of Tables and Figures Unlimited

2.2.9 Glossary of Abbreviations and Acronyms Unlimited

6.1 Model Contract (Sections A-J) N/A

6.1.4 Representations and Certifications (Section

K)

N/A

6.3.1 - 6.3.3 Contact Information Unlimited

Appendix I, Rights in Data Unlimited

6.3.5 Attachments to the Model Contract Unlimited

2.3.4. Names

Offerors shall submit volumes with the following file names: Volume I – Technical.doc or

.docx, Volume II – Price.doc or .docx (.pdf is only acceptable for Volume I and II if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text), with PricingMatrix.xls or .xlsx, and Volume III – Contract.doc or .docx.

2.3.5. Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be considered in the evaluation of the proposal. Page limitations may also be placed on responses to

Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. Each page shall be counted except the following:

blank pages, title pages, tables of contents, tabs, indexes, glossaries, and those noted in the

Proposal Organization Chart as unlimited. Page limits apply to both hard copy and electronic.

2.3.6. Pricing Information

All pricing information shall be addressed ONLY in the Price Proposal and Contract

Documentation volumes (Volumes II & III). Price trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

2.3.7. Cross Referencing

The Technical volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for the technical proposal evaluation, which is not found in the Technical volume, will be assumed to have been omitted from the proposal, and will not be considered in the technical evaluation.

Cross-referencing within a proposal volume is permitted when its use would conserve space without impairing clarity. The Price evaluation will utilize information from Volume II for the evaluation, but may also utilize information from other volumes (Volumes I and III) as well.

The Offeror shall complete the cross-reference matrix provided in Table 2.2 that will indicate the corresponding proposal paragraph or location which addresses the referenced item. The

Offeror’s cross-reference matrix shall include the proposal reference information as it relates to the instructions, SOW contents, Engine Procurement Specification (EPS) contents, RFP sections, Contract Line Item Number (CLIN), Contract Data Requirements List (CDRL) references (if applicable), and the corresponding proposal paragraph in the section which addresses the reference item as part of Volume I – Technical; Volume II – Price.

Table 2.2 Cross-Reference Matrix

Cross Reference

RFP Ref

Para

(SOW,

EPS,

Boeing &

Offeror

OTA)

RFP Appendix’s E & F –

Addendum to FAR 52.212

(-1) (-2)

Proposal

(Volume &

Para)

Factor 1: Technical 3.0 2.2

- Subfactor 1 –

Evaluation Criteria

3.2.3 2.2.1

Element 1a – Fuel Consumption

EPS

7.2.1.1.6 3.2.3.a 2.2.1.a

Element 1b – Combat Ceiling

SOW 1.2

Table 1-2 3.2.3.b 2.2.1.b

Element 1c – Takeoff Rated Thrust

SOW 1.2

Table 1-3 3.2.3.c 2.2.1.c

Element 1d – Power Generation

7.2.4.2.12 3.2.3.d 2.2.1.d

Element 1e – Scheduled

Engine Removal

EPS

16.4.2 3.2.3.e 2.2.1.e

Element 1f – Unscheduled

EPS

16.4.3 3.2.3.f 2.2.1.f

Element 1g – Integration

SOW

3.1.4 3.2.3.g 2.2.1.g

Element 1h – Propulsion Military

Type Certification

SOW

1.2

4.4.14

4.4.15

3.2.3.h 2.2.1.h

Element 1i – Lifecycle Analysis

3.1.3 3.2.3.i 2.2.1.i

Element 1j – Letter of Intent N/A 3.2.3.j 2.2.1.j

Element 1k – Small

Business Participation N/A 3.2.3.k 2.2.1.k

- Subfactor 2 –

Performance

Capabilities

3.2.4 2.2.2

Element 2a – Fuel Consumption

3.2.4.a 2.2.2.a

Element 2b – Unscheduled

EPS

3.2.4.b 2.2.2.b

Factor 2: Technical Risk 3.3 2.3

Element 1a – Fuel Consumption

EPS

3.2.3.a 2.2.1.a

Element 1b – Combat Ceiling

7.2.1.1.8 3.2.3.b

2.3

NOTE 1

Element 1c – Takeoff Rated Thrust

7.2.1.1.8 3.2.3.c

2.3

Element 1d – Power Generation

7.2.4.2.12 3.2.3.d 2.2.1.d

Element 1e – Scheduled

EPS

16.4.2 3.2.3.e 2.2.1.e

Element 1f – Unscheduled

EPS

3.2.3.f 2.2.1.f

Element 1g – Integration

3.1.4 3.2.3.g 2.2.1.g

Element 1h – Propulsion Military

Type Certification

SOW

1.2

4.4.14

4.4.15

3.2.3.h 2.3

Element 1i – Lifecycle Analysis

3.1.3 3.2.3.i 2.2.1.i

Factor 3: Price 5.0 2.5

2.3.7. Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.3.8. Tables and Figures

Include an indexed list of Tables and Figures.

2.3.9. Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

2.4. Page Size and Format

2.4.1. Pages

A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Page line spacing shall be 1.5 lines. Except for the reproduced sections of the solicitation document, the text size shall be no less than Arial 12 points.

Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals.

2.4.2. Tables, Charts, Graphs and Figures

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and shall not exceed 11 x 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. The following limitation only applies to the Technical Volume. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8 point font. In addition, all figures, charts, tables and graphs shall allow for page line spacing be no less than 1.0 lines.

These limitations shall apply to both electronic and hard copy proposals. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation. These limitations shall apply to both electronic and hard copy proposals.

2.5. Binding and Labeling

Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the Offeror’s name. The same identifying data shall be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source

Selection Information.

2.6. Electronic Offers

The content and page size of electronic copies shall be identical to the hard copies. In such cases where a discrepancy exists between the written hard copy and electronic copy, a clarification

EN may be issued to allow Offerors the opportunity to make both versions consistent with each other. For electronic copies, indicate on each Compact Disc Read Only Memory (CD-ROM) the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The Offeror shall submit Volumes I through III in electronic format. Each volume shall be submitted on a separate

CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal, except Volume II Pricing Matrix, shall be submitted in a format readable by Microsoft (MS) Word, MS Excel, MS-Power Point 2013, or newer, or searchable PDF. In accordance with paragraph 5.3.7 below, Volume II Pricing Matrix shall be submitted in a format readable by MS Excel 2013 or newer.

2.7. Distribution

The "original" proposal shall be clearly identified. Proposals shall be addressed to the

Contracting Officer and mailed to:

DEPARTMENT OF THE AIR FORCE OFFICE:

AFLCMC/WWK (B-1/B-52)

3001 Staff Drive, Post 2AF-86A

Tinker AFB OK 73145-3020

ATTN: SHELLY LOOKE

Telephone: 405-736-4946 e-mail: shelly.looke.1@us.af.mil

3.0 Factor 1 – Technical

3.1. General

The Technical Volume shall be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical Subfactors defined in

Addendum to FAR 52.212-2, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for you to tell mailto:shelly.looke.1@us.af.mil us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

3.2. Format and Specific Content

3.2.1. Technical

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each Technical Subfactor. The Offeror shall also provide the proposed engine design configuration. The Offeror shall include an Engine Cycle Model as a part of their proposal. Additionally, the Engine Cycle Model shall:

• Be consistent with the proposed design written in Numerical Propulsion System

Simulation (NPSS) source language. The model shall be in accordance with DI-MISC-

81966 and shall be provided with a corresponding user manual. The NPSS cycle model shall be capable of being used on a PC running a Windows 10 environment.

• Define the installation effects, including file names, used when demonstrating compatibility with steady-state and transient performance and operability requirements.

• Employ the most updated, known installation effects from OTA Step 1 effort. Any unknown effects should assume representative commercial values.

• The cycle model should be sufficiently open as to allow the Government to see model-specific input, curves and constants to fully understand the operation of the model. The model should comply with EPS paragraph 7.2.1.1.4 and enable the user to modify the parameters listed therein as well as incorporate customer-defined code. While it is highly desirable to have the model structure open and visible as interpreted source, it is not required until after potential contract award per the updated Cycle Model CDRL.

NOTE: The Engine Cycle Model is not included in the page limitation for Volume I. The

Government reserves the right to utilize information within the Engine Cycle Model to substantiate the validity of stated claims provided in the Offeror’s technical proposal regarding

Subfactors 1a, 1b, 1c, 1d, and 2a or Technical Risk for Subfactors 1a, 1b, 1c, and 1d. Therefore, it is imperative the Offeror’s Engine Cycle Model and Offeror’s technical proposal are clear, concise and consistent for effective evaluation and validation. The Offeror is cautioned that information provided in the Engine Cycle Model and not the Offeror’s technical proposal will not be considered for the Government’s evaluation of Subfactors 1a, 1b, 1c, 1d, and 2a. Also, if the Offeror includes information in the Engine Cycle Model which is not related to Subfactors

1a, 1b, 1c, 1d, 2a or Technical Risk, the information will not be considered by the Government in the evaluation. If the Offeror’s technical proposal or the Engine Cycle Model provide contradictory information, the Government may review such contradictions to determine if they insert risk in the proposal and to determine if additional clarification/discussions are required.

3.2.2. Volume Organization

The Technical Volume shall be organized according to Table 2.1.

3.2.3. Subfactor One: Evaluation Criteria

The Offeror shall provide an approach to meet the requirements for a single engine configured for a B-52H aircraft. If the Offeror is proposing performance capabilities below the maximum requirement under Subfactor Two, then all of the elements identified below shall be met based on the proposed approach that achieves the performance capabilities proposed under Subfactor One

(single configuration). As a minimum, the approach shall provide the following essential elements listed below:

a) Fuel Consumption: The Offeror shall state how their engine meets the maximum Fuel

Consumption of 133,543 lbs. used to perform all Performance Missions shown in EPS

Table 7-2 and defined in EPS paragraph 7.2.1.1.6 (see EPS paragraph 7.2.1.1.7 and

Table 7-7 for fuel consumption calculation template). Additionally, the Offeror shall provide a summary of the data and analysis used in determining Fuel Consumption performance.

b) Combat Ceiling: The Offeror shall state how their engine meets the Military Rated

Thrust (MRT) minimum performance requirement at 39,000 feet Altitude as defined in

SOW paragraph 1.2, Table 1-2: Combat Ceiling Mandatory Requirements. The Offeror shall provide a summary of the data and analysis used in determining thrust performance at 39,000 feet. Additionally, the Offeror shall identify any difference or gap between the requirement in the EPS paragraph 7.2.1.1.8, EPS Table 7-8, and the existing certified limits and capabilities of the proposed engine. The Offeror shall also provide a risk assessment, including mitigation options for the identified difference or gap.

c) Takeoff Rated Thrust: The Offeror shall state how their engine meets the minimum

Takeoff Rated Thrust performance requirement as defined in SOW paragraph 1.2, Table

1-3: Takeoff Rated Thrust Mandatory Requirements. The Offeror shall provide a summary of the data and analysis used in determining Takeoff Rated Thrust performance. Additionally, the Offeror shall identify any difference or gap between the requirement in the EPS paragraph 7.2.1.1.8, EPS Table 7-8 and the existing certified limits and capabilities of the proposed engine. The Offeror shall also provide a risk assessment, including mitigation options for the identified difference or gap.

d) Power Generation: The Offeror shall state how each engine and its accessory gearbox meets the minimum 65kVA power generation requirement as specified in EPS paragraph 7.2.4.2.12. If the Offeror determines the commercial engine (including gearbox) requires modification(s) to meet power generation requirements, the Offeror’s approach shall address all change(s) required. The Offeror shall address fabrication/ production lead time, qualification/durability testing, and any associated impacts, to include impacts to the Rapid Prototype CERP Engine delivery schedule as a result of the modification(s). The Offeror shall state how CERP Engine performance and service life is maintained while providing the horsepower required for power generation.

Additionally, the Offeror shall provide a summary of the data and analysis used in determining power generation.

e) Scheduled Engine Removal (SER): The Offeror shall state how their engine satisfies the requirement of no forecasted SERs prior to 2050 as specified in EPS paragraph 16.4.2.

Additionally, the Offeror shall provide a summary of the data and analysis used to determine date of first forecasted SER occurrence.

f) Unscheduled Engine Removal (UER) Rate: The Offeror shall state how their engine meets the maximum UER Rate requirement of 0.26 events per 1,000 Engine Flying

Hours (EFH) as specified in EPS paragraph 16.4.3. Additionally, the Offeror shall provide a summary of the data and analysis used in determining UER Rate.

g) Integration: The Offeror shall provide an approach to minimize integration impacts as described in SOW paragraph 3.1.4:

i. The Offeror shall provide the following: 1) B-52H CERP Step 1 Aircraft

Modification Impact Analysis Summary provided to the OEM by Boeing at the

OTA conclusion; 2) B-52 CERP Step 1 Aircraft Modification Impact Analysis

Nuclear Hardening Summary provided to the OEM by Boeing at the OTA conclusion; 3) the OEM’s full submission of OTA Project Deliverable #1 (PD1):

Engine Performance Risk Assessment Report; 4) the OEM's full submission of

OTA Project Deliverable #2 (PD2): Engine Modification Model Report; and 5) the OTA Nuclear Hardening Report.

ii. The Offeror’s approach shall address all integration impacts identified in the B-

52H CERP Step 1 Aircraft Modification Impact Analysis Summary report, B-52

CERP Step 1 Aircraft Modification Impact Analysis Nuclear Hardening

Summary report, OEM PD1, OEM PD2, and Nuclear Hardening Report.

iii. The Offeror shall identify any integration risks not contained in the B-52H CERP

Step 1 Aircraft Modification Impact Analysis Summary, B-52 CERP Step 1

Aircraft Modification Impact Analysis Nuclear Hardening Summary report, OEM

PD1, OEM PD2, or Nuclear Hardening Report and provide an approach to address those impacts.

iv. The Offeror shall identify and provide supporting substantiation for any impacts associated with the Offeror's engine identified in the Step 1 Aircraft Modification

Impact Analysis Summary, B-52 CERP Step 1 Aircraft Modification Impact

Analysis Nuclear Hardening Summary report, OEM PD1, OEM PD2, or Nuclear

Hardening Report that the Offeror wishes to refute or take exception to. The

Offeror shall indicate whether it does not wish to refute or take exception to any identified impacts.

NOTE: Each Offeror is requested to submit (as specified in Table 2.1) the OTA reports

30 calendar days prior to the solicitation closing date. Early submission of the OTA report is a request and not a requirement. Failure to submit the OTA report early will not result in Offeror disqualification, an unacceptable rating, or any other penalty.

h) Propulsion Military Type Certification (P-MTC): The Offeror shall provide an approach to support the Government to obtain a P-MTC IAW SOW paragraphs 4.4.14 and 4.4.15.

The Offeror shall tailor the Standard, Method of Compliance, and Substantiating Data

References, as necessary, in the Certification Basis (CB) provided by the Government in

SOW Attachment C as referenced in SOW paragraph 4.4.15.1. At a minimum, the approach shall include the following criteria:

i. Provide tailored CB, including a schedule depicting any proposed development/qualification efforts required to deliver Rapid Prototype CERP

Engines capable of achieving a Military Flight Release (MFR) within 36 months of contract award, and shall address any planned testing (to include wind tunnel/altitude/Flying Test Bed activities) and facilities required for engine and individual component test.

ii. Identify in the schedule the development milestone of lowest risk for the

Government to place its first delivery order for Prototype Engines.

iii. If the certification approach includes use of test facilities other than those owned by the Offeror, documentation of facility capabilities and availability shall be included from the facility. The availability of any Government owned test facilities is not guaranteed by the Government.

iv. The approach shall meet all mandatory EPS requirements identified in SOW paragraph 1.2. In addition, the proposal must include a statement that all “shall” requirements will be met except those identified in response to Subfactor 1hv.

v. Identify differences or gaps between “shall” requirements in the EPS and the existing certified limits and capabilities of the engine; identify military unique requirements that have no equivalent 14 CFR Part 33 requirements; and provide a risk assessment, including mitigation options, for each identified difference or gap

(SOW paragraph 1.2). It is not the Government’s intent to drive turbomachinery hardware redesign in order to comply with the requirements of the EPS.

vi. If the Offeror’s approach utilizes a multi-core processor, the Offeror shall address additional certification requirements provided in SOW paragraph 4.4.14.1.

i) Lifecycle Analysis: The Offeror shall provide an approach to minimize ownership cost as described in SOW paragraph 3.1.3:

i. The Offeror shall provide their OTA Project Deliverable #3 (PD3):

Logistics/Lifecycle Assessment Report. NOTE: The PD3 portion of the B-52H

CERP Step 1 Aircraft Modification Impact Analysis Summary provided under

Subfactor 1g will also be utilized for this Subfactor.

ii. The Offeror shall identify, describe, and mitigate elements driving ownership cost associated with the Offeror's engine identified in PD3 as well as the PD3 portion of the B-52H CERP Step 1 Aircraft Modification Impact Analysis Summary.

iii. The Offeror shall identify, describe, and mitigate any elements driving ownership cost associated with the Offeror's engine that were not identified in PD3 or the

PD3 portion of the B-52H CERP Step 1 Aircraft Modification Impact Analysis

Summary.

iv. The Offeror shall provide a summary of the methodology, data, and analysis used to develop their PD3 report content.

v. The Offeror shall explain how their intellectual property data and software assertions (as documented in Volume III, Contract Documentation: Appendix I, Rights in Data) serve to minimize ownership cost, to include organizational and depot maintenance activity.

NOTE: The Offeror shall not provide monetary values as part of its response to this element, or any other element within Subfactor One: Evaluation Criteria. The intent of this element is for the Offeror to describe various aspects of how the Offeror's proposed engine, if selected, could minimize ownership cost throughout the lifecycle of the B-52 program.

NOTE: Each Offeror is requested to submit (as specified in Table 2.1) the OTA reports

30 calendar days prior to the solicitation closing date. Early submission of the OTA report is a request and not a requirement. Failure to submit the OTA report early will not result in Offeror disqualification, an unacceptable rating, or any other penalty.

j) Letter of Intent: The Offeror shall provide a Letter of Intent signed by the Offeror and the aircraft integrator stating the Offeror will obtain from the aircraft integrator appropriate data and technical support necessary to develop, produce, and integrate the

CERP Engine onto the B-52H aircraft.

k) Small Business Participation: The Offeror shall provide their Small Business

Subcontracting Plan IAW Federal Acquisition Regulation (FAR) 52.219-9 and Defense

Federal Acquisition Regulation Supplement (DFARS) 252.219-7003 or 252.219-7004.

The proposed approach for subcontracting shall clearly describe subcontract arrangements, relationships, roles, and work to be performed by subcontractors.

3.2.4. Subfactor Two: Performance Capability

The Offeror is afforded an opportunity to provide an approach which is less than the maximum requirements for the elements listed below. As set forth in Addendum to FAR 52.212-2

(Appendix F) paragraph 2.2.2, Subfactor 2 Technical: Performance Capability, Offerors can receive best value credit based upon achieving specific performance capabilities. The best value credit will be applied as a price decrement to the Offeror’s Total Proposed Price, resulting in a

Value Adjusted Total Evaluated Price (VATEP), which will be used in the best value determination. Specific price decrement values are listed in Addendum to FAR 52.212-2

(Appendix F) paragraph 2.2.2. For this Subfactor, the Offeror shall identify how its approach is less than the maximum requirements by a specific amount and provide sufficient supporting rationale describing how the performance capability will be achieved. An Offeror is not required to address Subfactor 2: Performance Capability if it is not seeking a price decrement for achieving performance capabilities less than the required maximum amount. The Offeror shall clearly document in its proposal if it is not addressing Subfactor 2. In addition, the Offeror shall address how, or if, providing less than the maximum threshold affects the elements of Subfactor

One. As stated above, the proposed engine shall be a single configuration. If the engine is configured to achieve performance capabilities in Subfactor 2, the engine shall still meet all requirements in Subfactor 1.

a) Fuel Consumption: The Offeror shall state how their engine improves upon the maximum Fuel Consumption of 133,543 lbs. used to perform all Performance Missions shown in EPS Table 7-2 and defined in EPS paragraph 7.2.1.1.6 (see EPS paragraph

7.2.1.1.7 and Table 7-7 for fuel consumption calculation template). Additionally, the

Offeror shall provide the analysis and methodology used to determine the fuel used to perform all Performance Missions is less than the maximum Fuel Consumption requirement.

b) Unscheduled Engine Removal (UER): The Offeror shall state how their engine improves upon the maximum UER Rate requirement of 0.26 events per 1,000 EFH as defined in

EPS paragraph 16.4.3. Additionally, the Offeror shall provide the analysis and methodology used to determine the UER Rate is less than the maximum UER Rate requirement.

3.3 Factor 2 - Technical Risk

The Offeror shall address technical risks associated with those aspects of the Offeror’s proposed technical approach for Factor 1 Technical, Subfactor 1a/2a, 1b, 1c, 1d, 1e, 1f/2b, 1g, 1h, and 1i. The Offeror shall address all technical risks that the Offeror considers to have potential for disruption to schedule, increased cost or degradation of performance, the need for increased Government oversight, or the increased likelihood of unsuccessful contract performance, including any risks identified in the OTA reports and planned/proposed mitigations. For each risk identified, the Offeror shall provide the rationale for the risk, including quantitative estimates; potential impacts on schedule and performance; and the potential of each risk to interfere with or prevent the successful accomplishment of contract requirements. The Technical Risk proposal shall also include the OTA Reports required to be submitted under Subfactors 1g and 1i.

4.0. Reserved

5.0. Factor 3 – Price

5.1. Price Volume

In the price volume, the Offeror shall provide the following information in addition to the Pricing

Matrix (Appendix D). These instructions are to assist you in submitting information required to evaluate the reasonableness, balance, and realism of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

5.2. General Instructions

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All information relating to the proposed price, including all required supporting documentation, shall be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

All pricing submitted by the Offeror shall be proposed in then-year (TY$) dollars.

5.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition, but it may also be determined through other price analysis techniques. The burden of proof for credibility of proposed costs/prices rests with the Offeror. The Offeror shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.). It shall be noted that completeness is one aspect of price reasonableness. For completeness, the Offeror shall provide unit prices for all listed items in the Pricing Matrix

(Appendix D). Additionally, the Offeror shall include a dollar amount, or rate proposed as applicable in columns E–U of the Pricing Matrix (Appendix D). If an Offeror’s proposed unit price is zero, then the Offeror shall provide rationale to support the zero dollar entry.

5.2.2. Unbalanced Pricing

The Government will evaluate proposals for unbalanced pricing. The Offeror is cautioned against submitting an offer which exhibits unbalanced pricing. Unbalanced pricing may increase performance risk and could result in payment of unreasonable or unrealistic prices. For this acquisition, balanced pricing is determined with respect to year-to-year price variances for separately priced CLINs. The Offeror shall provide rationale for any proposed CLIN price increase greater than 5% per performance period year to year. Rationale shall also be provided for any proposed CLIN price decrease per performance period year to year. Unexplained price variances from year-to-year could suggest unbalanced pricing. It is in the Offeror’s best interest to provide explanations or supporting rationale for any significant annual CLIN price variances.

To assist in the determination of balanced pricing, the Offeror shall complete the attached

Pricing Matrix (Appendix D).

5.2.3. Price Realism

The Government will evaluate proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements and to ensure the proposed price does not pose an unacceptable risk to performance. The Offeror shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.). All proposed prices shall be sufficient and adequately proposed to ensure performance is not at an unacceptable risk with prices proposed too low.

5.2.4. Pricing Information Requirements

Price analysis techniques shall be utilized to ensure fair and reasonable pricing IAW FAR

15.404-1(b). Providing information to assist with pricing evaluation to further support proposed pricing will expedite the source selection process.

IAW FAR 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. The Government reserves the right to obtain such data as appropriate.

Should the CO determine proposed prices to appear unreasonable or the possibility that an

Offeror does not fully understand the requirement, the Offerors may be required to support price reasonableness and/or price realism via other than cost or pricing data.

5.2.5. Rounding

In the Pricing Matrix (Appendix D), all proposed dollar amounts shall be rounded to the nearest dollar. All proposed labor rates shall be rounded to the nearest cent. Proposed percentages are rounded to four places to the right of the decimal.

5.2.6. Total Proposed Price (TPP)/VATEP

The TPP is calculated in the Pricing Matrix (Appendix D) as detailed in the calculation methodology tab. This source selection includes VATEP as referenced in Addendum to

52.212-1 (Appendix E), paragraph 3.2.4. The Offeror’s proposed TPP will be adjusted to the

VATEP IAW the methodology described in Addendum to 52.212-2 (Appendix F), paragraph

2.2.2, Subfactor 2 Technical: Performance Capability. The VATEP will be used for evaluation purposes only.

5.3. Pricing Support Information

5.3.1. Estimating Techniques and Past Experience

Provide a brief explanation of the methodology used to estimate prices in the development of the Offeror’s proposed pricing. Where price estimates are based on past experience, identify the past experience; explain how the past experience relates to the current effort including similarities and differences and how price data available from the past experiences was adapted to the current effort pricing.

5.3.2. Proposed Price Reduction per Corporate/Management Decision

If proposed prices to perform the proposed effort have been decreased due to a management decision, provide a summary of the reduction by major pricing element (e.g., material, labor, overhead, etc.). Also, provide complete rationale for the reduction. Provide the estimated dollar and percentage of the reduction, explaining how such reductions are ensured not to increase performance risk to the Government. If the Offeror has not proposed any price reductions, then state accordingly in Section 2 of the Price Volume.

5.3.3. Price Assumptions Used in Development of Proposed Pricing

All significant assumptions, scope limitations, and/or qualifications affecting the pricing proposal shall be addressed and explained. If there are no proposed price assumptions, then state accordingly in Section 2 of the Price Volume.

5.3.4. Labor, OEM Material Handling, Subcontractor Material Handling, Travel General &

Administrative (G&A), and Transportation/Miscellaneous Shipping Rates

Proposed rates will be used for To Be Negotiated (TBN) and over and above tasks. These rates shall be proposed as FFP, fully burdened rates valid for all rates referenced in the Pricing Matrix

(Appendix D). These labor wrap rates shall be proposed at sufficient dollar amounts to adequately cover any and all fluctuations and actual costs in contract performance out-years. All rates should be proposed with sufficiently high ceiling rates to ensure adequate coverage of all labor costs, all indirect costs, including G&A, Cost of Money, and so forth as well as prime and subcontractor profit in every contract out-year. The Offeror is required to indicate their understanding that proposed ceiling rates will apply to all out-years despite what current actuals are running at the time. The OEM Material Handling Rate should include all cash and trade discounts, rebates, allowances, credits, salvage, commissions, and other benefits as applicable.

5.3.5. Government Field Support Agencies

Identify the cognizant Defense Contract Audit Agency (DCAA) and Defense Contract

Management Agency (DCMA) offices responsible for administration of the Offeror’s

Government contracts.

5.3.6. Other Documentation

Other documentation considered by the Offeror to be essential for support of proposed prices shall be presented in this section.

5.3.7. Submission of Pricing Matrix

Submit the completed Pricing Matrix (Appendix D) in support of the proposed TPP. The proposed pricing in the Pricing Matrix (Appendix D) submitted shall be consistent with the

Offeror’s approved estimating system and shall duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. The Pricing Matrix (Appendix D) submitted shall comply with the following format requirements:

a) Data file shall be submitted on a CD.

b) Data file shall be .XLS file format (MS-Excel 2013 or above) compatible format.

5.4. Volume Organization

The Price volume shall consist of the following sections to include Title Page, Table of Contents, List of Tables and Figures, and Glossary of Abbreviations and Acronyms:

SECTION 1 – Include your rationale in response to the following paragraphs in Section 1, along with a Table of Contents.

5.2.1. – Price Reasonableness

5.2.2. – Unbalanced Pricing

5.2.3. – Price Realism

5.2.4. – Pricing Information Requirements

SECTION 2 – Include your response to the following paragraphs in Section 2.

5.3. – Pricing Support Information

5.3.1. – Estimating Techniques and Past Experience

5.3.2. – Proposed Price Reduction per Corporate/Management Decision

5.3.3. – Price Assumptions Used in Development of Proposed Pricing

5.3.4. – Labor, OEM Material Handling, Subcontractor Material Handling, Travel

General & Administrative (G&A), and Transportation/Miscellaneous Shipping Rates

5.3.5. – Government Field Support Agencies

5.3.6. – Other Documentation

SECTION 3 – Include your response to the following paragraphs in Section 3.

5.3.7. – Submission of Pricing Matrix

6.0. Contract Documentation

6.1. Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the

Model Contract.

6.1.1. Solicitation/Contract Form

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF1449.

Signature by the Offeror on the SF1449 constitutes an offer, which the Government may accept.

The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

6.1.2. Supplies or Services and Prices

Do not complete pricing in the model contract. All pricing is required to be in the Pricing Matrix

(Appendix D).

6.1.3. Contract Clauses

The Offeror shall provide required information to complete clauses as required.

6.1.4. Representations, Certifications, and other Statements of Offerors

The Offeror has completed the annual representations and certification electronically via the

System for Award Management (SAM) website at https://www.sam.gov. After reviewing the

SAM database information, the Offeror verifies by submission of this offer that the representation and certifications currently posted electronically at FAR 52.212-3, Offeror

Representations and Certifications—Commercial Items are correct.

6.2. Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors shall clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

https://www.sam.gov/

Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 6.2. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

Table 6.2 Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

6.3. Other Information Required

6.3.1. Ombudsman

An Ombudsman has been appointed to hear concerns from Offerors or potential Offerors during the proposal development phase of this acquisition. The Ombudsman for this acquisition is

AFSC/PZC, located at Tinker AFB, OK. This does not diminish the authority of the program director or CO, but communicates Offeror’s concerns, issues, disagreements and recommendations to the appropriate Government personnel. When requested, the Ombudsman shall maintain strict confidentiality as to the source of the concern. The Ombudsman does not participate in the evaluation of proposals or in the source selection process; interested parties are invited to call AFSC/PZC at 405-736-3273.

6.3.2. Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.3.3. Government Offices

Provide the mailing address, telephone and fax numbers, and facility codes for the cognizant

Contract Administration Office, DCAA, and Government Paying…