Section L_Instructions to Offerors_Final RFP 5 Feb 21.pdf

FA8626-21-R-0002

Section L

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO RESPONDENTS FOR

PROPOSAL PREPARATION USING TRADEOFF SOURCE SELECTION

PROCEDURES

1.0 Program Structure and Objective

1.1 The Government plans to award a single contract for the F-15EX Propulsion System as defined in Section J, Attachment 1, Statement of Work (SOW) paragraph 2.1. Referenced definitions within this document are incorporated in Section J, Attachment 1, SOW. The

Contractor shall act as a single supplier of engines for the F-15EX Aircraft Lot 2+. Engines will be procured as a result of this competition and will be delivered directly to Boeing as

Government Furnished Equipment (GFE) for installation into F-15EX Aircraft. The Offeror is required to propose an engine that was previously installed on a F-15 aircraft and approved for operational use, and to propose an approach to integrate their F-15EX Propulsion System as defined in Section J, Attachment 1, SOW. The Government requests each Offeror (single

CAGE/DUNS) to submit their overall single best approach that will meet all stated requirements in the solicitation. Offerors shall only submit one proposal for each respective cage code/DUNS.

1.2 Initial funding will be obligated for Lot 2 engines and data, with Option Contract Line Item

Numbers (CLINs) 1000 - 1004, to be exercised at contract award. CLIN 2003 will be exercised within 24 months of contract award.

1.3 To assure timely and equitable evaluation of the proposal, the Offeror must follow the instructions contained herein. The response shall consist of three (3) separate Volumes;

Volume I — Technical Proposal, Volume II — Price Proposal; and Volume III — Contract

Documentation.

2.0 General Instructions and Information

2.1 This section of the Instructions to Offerors (ITO) provides general guidance for preparing the proposal as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information required by the ITO and must be submitted in accordance with (IAW) these instructions. The Offeror shall be compliant with the requirements as stated in the SOW, the Propulsion System Specification for the F-15EX Propulsion System

Version 5.0, appendices, solicitation terms and conditions, and representations and certifications.

Alternate proposals shall not be accepted. Any Offeror who submits an incomplete package may be considered ineligible for award and may be rejected IAW Section M, paragraph 1.3. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation or exclusion from the competition. Any proposal, modification, or revision that is received at the designated government office after the exact time specified for receipt of proposals will not be considered in accordance with Federal Acquisition Regulation (FAR)

15.208(b)(1).

2.2 The proposal shall be clear, concise, and shall 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 the requirements. The Offeror 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.3 The proposal shall be submitted in English. Proposals received in languages other than

English will be rejected.

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

2.5 The proposal acceptance period is specified in Section A of the model contract/solicitation.

The Offeror shall make a clear statement in Section A that the proposal is valid through this date.

2.6 In accordance with 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 thirty days after contract award.

2.6.1 Within two (2) calendar days after the Procuring Contracting Officer (PCO) notifies unsuccessful Offerors in accordance with paragraph 2.8, the unsuccessful Offeror(s) shall destroy provided Request For Proposal (RFP) Supporting Documentation in a manner that prevents disclosure of contents or reconstruction of the documents. The Government provided limited-distribution Supporting Documentation to assist Offerors in the development of their proposals and, therefore, an unsuccessful Offeror shall not need Supporting Documentation if their proposal is determined to be unsuccessful. Approval of a debriefing, if requested by the unsuccessful Offeror, is contingent on the unsuccessful Offeror providing the PCO with an email confirming that the documents below were destroyed within two calendar days after the PCO notified the unsuccessful Offeror.

The following Supporting Documentation provided by the Government, including but not limited to, shall be destroyed by unsuccessful Offerors:

F-15EX System Requirements Document (SRD)

F-15EX System Safety Program Plan (SSPP)

F-15EX Critical Safety Item (CSI) List

F-15EX Configuration Item (CI) / Computer Software Configuration item (CSCI)

F-15EX Specification Tree

F-15EX Addendum to the Eagle TALON Configuration Management Plan (CMP)

F-15EX Safety of Flight Parts

F-15 Program Protection Plan (PPP)

F-15 Eagle/Strike Eagle Security Classification Guide (SCG)

2.7 Points of Contact

The PCO is the primary point of contact (POC) for this acquisition. Address any questions or concerns you may have to the PCO. The PCO’s contact information is identified in paragraph 2.16. Include the alternate POC, Capt Chelsea Brincka, in any correspondence sent to the PCO. Her contact information is identified in paragraph 2.16 below.

2.8 Debriefings

The PCO will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may request to have the debriefing delayed until after award. However, an Offeror excluded from the competitive range is entitled to no more than one debriefing for its proposal. The PCO 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. Approval of a debriefing is contingent on the unsuccessful

Offeror providing the PCO with an email confirming that the Supporting Documentation identified in paragraph 2.6.1 were destroyed within two calendar days after the PCO notified the unsuccessful Offeror.

2.9 Discrepancies

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the PCO within 14 calendar days of RFP release via email with supporting rationale, as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error. The Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

2.10 Electronic Reference Documents

All referenced documents for this solicitation are available at beta.SAM.gov. Potential

Offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

2.11 Oral Presentation

Oral presentations will not be utilized.

2.12 Amendments to Solicitation

If this RFP is amended, all terms and conditions that are not amended remain in full force and effect. The Offeror shall acknowledge receipt of any amendment(s) and provide confirmation of receipt of any amendment(s) upon submission of the Offeror’s proposal.

Acknowledgements are subject to solicitation provision FAR 52.215-1.

2.13 Communications

Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Department of Defense (DoD) Secure Access File Exchange (SAFE)

(safe.apps.mil) will be used to transmit such information to the Offeror 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), U.S. Postal

(or like service) delivery, and/or oral with telephonic or face-to-face meetings.

2.14 Submission, Modification, Revision, and Withdrawal of Proposals

The proposal and modifications to the proposal shall be submitted via DoD SAFE

<https://safe.apps.mil/>. The Offeror shall input the solicitation number and the name and https://safe.apps.mil/ address of the Offeror in the Short Note to the Recipients block in DoD SAFE. The time and date specified in the automated DoD SAFE e-mail shall document receipt of the submission. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email both the primary and alternate POC listed in section 2.7 above no more than 14 days and no less than 3 days prior to proposal submittal date. Recommend the Offeror does a test submission via DoD SAFE three days prior to proposal submission with the PCO. Please indicate in Short Note to the Recipients if it is a test submission. The proposal shall not be submitted by email.

2.15 Electronic Offers

Each proposal shall include the Offeror’s name, solicitation number, volume number, and title.

The proposal shall be structured as set forth in Table 3.3 below, where each item listed in the table shall be a separate folder containing the appropriate file(s). Use separate folders to permit rapid location of all portions, including Subfactors, required plans, exhibits, appendices, and attachments, if any. If files are compressed, the necessary decompression program must be included. The proposal shall be submitted in a format readable by Adobe, Microsoft (MS) Office

Word, MS Office Excel, MS Office Project, and MS Office PowerPoint, as applicable. The proposal shall be in a searchable text format and shall not be password protected.

2.16 Distribution

See above for proposal submittal process. The PCO is for this acquisition is Ms. Gail Porumb;

contact her by phone at 937-361-1601 or by email at gail.porumb@us.af.mil. Include the alternate POC, Capt Chelsea Brincka, in any correspondence sent to the PCO. She can be reached by phone at 937-255-7699 or by email at chelsea.brincka.1@us.af.mil.

3.0 Organization/Page Limits

3.1 Title Page

The Title Page of each Volume must show solicitation number, name, address, and telephone and facsimile numbers of the Offeror and electronic email address, if available.

3.2 Team List

A Team List of the Offeror’s primary POCs shall be submitted in each Volume.

3.3 Proposal Organization Table

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table, Table 3.3 below. The titles and contents of the Volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table 3.3. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Volume

Instruction to Offerors

Paragraph

Number

Volume Title and Folder Structure Page

Limit

I 5.0 Technical

Title Page (Not included in page limit) 1

Team List (Not included in page limit) Unlimited

Table of Contents Unlimited

List of Tables and Figures (Including

IMS/ACAs)

Unlimited

Glossary of Abbreviations and Acronyms Unlimited

Organization Structure 2

Technical (Factor 1)

SF 1: Certifications

SF 2: Producibility & Production Management

SF 3: Engine Integration, Aircraft Military

Certification & Schedule

IMS 250 Lines

II 6.0 Price (Factor 2) Unlimited

III 7.0 Contract Documentation Unlimited

Table 3.3 Proposal Organization

3.4 File Names

The Offeror shall submit Volumes with the following file names: Volume 1 — Technical.doc or

.pdf, Volume II — Price.xls and Price.doc or .pdf, and Volume III — Contract Documentation.doc or .pdf.

3.5 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or 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 Offeror. Each page shall be counted except the following:

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

Proposed Organization Chart Table 3.3, as unlimited.

3.6 Cross Referencing

Each 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 proposal evaluation, which is not found in its designated Volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal Volume is permitted when its use would conserve space without impairing clarity.

3.7 Indexing

Each Volume shall contain a detailed table of contents to delineate the subparagraphs within that

Volume. Tab indexing shall be used to identify sections.

3.8 Tables and Figures

Include an indexed list of Tables and Figures.

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.

3.10 Page Size and Format

A page is defined as a single side of an 8.5 x 11 inch sheet of paper containing information when printed. 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 shall be Arial type font and font size no less than 11. 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 and to ENs.

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.

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 Arial type font and font size no less than 8. Any text within figures, charts, tables, and graphs, which do not meet this requirement, will not be considered in the evaluation.

3.11 Labeling

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.

4.0 Use of Non-Government Advisors

4.1 List of Companies

Offerors are advised that technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors for review and analysis. The non-government advisor support will be provided by the following:

COLSA Corp., 6728 Odyssey Drive, Huntsville, AL 35806

Credence Management Solutions, LLC, 8609 Westwood Center Drive #300, Vienna, VA 22182 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fdir%2F34.7245533%2C-86.6738642%2Fcolsa%2Bcorporation%2F%4034.7245737%2C-86.6761024%2C17z%2Fdata%3D!3m1!4b1!4m9!4m8!1m1!4e1!1m5!1m1!1s0x88626eb19f408059%3A0xeb754b4d2ab060b8!2m2!1d-86.6739633!2d34.7247779&data=02%7C01%7CTkasten%40wbbinc.com%7Ce0b6f28c50c24ee735ef08d8663c0916%7Caa08a8311918483e8827d4fde17248fe%7C1%7C0%7C637371756077100426&sdata=Sow%2BWnwoeUJuU5FFnvz9W8cYsIIATFpGzm1RNsa3Cj8%3D&reserved=0 https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.google.com%2Fmaps%2Fdir%2F34.7245533%2C-86.6738642%2Fcolsa%2Bcorporation%2F%4034.7245737%2C-86.6761024%2C17z%2Fdata%3D!3m1!4b1!4m9!4m8!1m1!4e1!1m5!1m1!1s0x88626eb19f408059%3A0xeb754b4d2ab060b8!2m2!1d-86.6739633!2d34.7247779&data=02%7C01%7CTkasten%40wbbinc.com%7Ce0b6f28c50c24ee735ef08d8663c0916%7Caa08a8311918483e8827d4fde17248fe%7C1%7C0%7C637371756077110417&sdata=ZNWo5600zkDRHVuuW%2B5vAx6MlFU4kf3hvtksfx2Ith4%3D&reserved=0

Dayton Aerospace Inc., 4141 Colonel Glenn Highway, Suite 252, Dayton, OH 45431

Guidehouse, LLP, 1800 Tysons Boulevard, 7th Floor McLean, VA 22102-4257

Odyssey Systems, Inc., 4141 Colonel Glenn Highway, Suite 301, Beavercreek, OH

45431

Whitney Bradley and Brown (WBB) Inc., 11790 Sunrise Valley Drive, Suite 500, Reston, VA, 20191

4.2 Objections to Disclosures

Any objection to the aforementioned disclosure shall:

a) Be submitted in writing to the PCO within 10 days of RFP issuance; and

b) Include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Offeror objects to disclosure to listed non-government advisors.

4.3 Consent to Release

In the event no objection (pursuant to part 2 above) is received by the PCO, submission of an

Offer shall be construed as consent to the release of any proprietary, confidential, or privileged commercial or financial data provided in response to this solicitation, to non-government advisors for review and analysis. An Organizational Conflict of Interest analysis has been completed.

5.0 Factor 1 — Technical

5.1 General

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

Section M, Evaluation Factors for Award, using the instructions provided below. Each Offeror must provide as specifically as possible the actual methodology it would use for accomplishing/satisfying these Subfactors. All the requirements specified in the solicitation are mandatory. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

5.2 Specific Content

5.2.1 Technical

The Technical Volume shall provide the proposed approach to meeting the minimum performance or capability requirements of each Technical Subfactor.

5.2.2 Volume Organization

The Technical Volume shall be organized according to the outline provided in Table 3.3.

5.2.3 Subfactor 1 Certifications

5.2.3.1 Measure of Merit (MoM) 1: Gate, Prior F-15 Integration

Using United States Air Force (USAF) Engine Designation format (Type, Model, Series), the

Offeror shall identify and provide supporting documentation for the F-15EX Propulsion System, as defined in Section J, Attachment 1, SOW paragraph 2.1, proposed in response to this solicitation. The Offeror shall:

Identify an in-production F-15 Propulsion System (Type, Model, Series) that has been previously integrated into an existing F-15 aircraft

Identify the F-15 aircraft (Mission, Design, Series) the F-15 Propulsion System was integrated into and approved for operational flight

Identify the F-15 Propulsion System specification(s) and applicable reference number(s) and aircraft Interface Control Document and applicable reference number that will either be used or modified for use in support of this effort

5.2.3.2 MoM: 2 Chief Executive Officer (CEO) Certification

The Offeror’s CEO shall sign, date, and submit a certification letter, using the mandatory template in Section L, Attachment 2, validating that all aspects of its proposal meet all

Government requirements without exception. The CEO Certification Letter shall contain all the language in the template and shall not add any additional language. The Offeror shall not propose changes to the specification or the SOW in any volume of its proposal. The Offeror’s

CEO Certification Letter will be incorporated into the contract as Section J, Attachment 13.

5.2.3.3 MoM 3: Small Business Participation

The Offeror shall submit a narrative of their Small Business Participation that addresses the approach to which the successful Offeror will utilize qualified Small Business entities. This narrative is a separate and distinct document from the Small Business Subcontracting Plan. The

Small Business Participation narrative is required from all Offerors, including companies with commercial plans and comprehensive subcontracting plans. However, objectives/goals specifically identified in the proposal must be consistent across the Small Business

Subcontracting Plan (if applicable) and the Small Business Participation narrative. The Offeror shall submit the Small Business Participation narrative under the Technical Volume of the proposal. Small Business participation only includes Small Business utilization contributions to contract performance at the first and second-tier subcontract level. Contractor format for the narrative is acceptable.

The Small Business Participation narrative shall include:

The name of all first and second-tier Small Business subcontractors to be utilized

(including NAICS codes) and the products/services to be provided

A description of the type and complexity of the products/services to be provided

The extent of utilization quantitatively (dollars) by each utilized Small Business subcontractor

5.2.4 Subfactor 2: Producibility & Production Management

5.2.4.1 MoM 1: Production Schedule

The Offeror shall deliver a single program Integrated Master Schedule (IMS) for both engine

Integration and engine production. The IMS shall be compliant with all solicitation schedule requirements and shall assume an award of 30 August 2021. This MoM provides the instructions for the Production section of the single program IMS. Paragraph 5.2.5.3 addresses the Integration section. The IMS shall include details to the level necessary to address for the engine: critical path elements, engine production and producibility for the life of the contract, projected DMSMS and DMSMS mitigation and expected risks and risk management. Furthermore, the Offeror shall identify risks, with proposed risk mitigation, and provide an overall management approach to ramp up production to meet Variation In Quantity (VIQ) production option combinations consistent with this solicitation’s delivery schedule. The Offeror shall identify component and complete engine production challenges on existing Government programs for the variant described in paragraph 5.2.3.1; the Offeror shall explain how these issues will effectively be mitigated as a result of this contract award. The Offeror shall identify current engine and component production rates and the proposed steps (including tooling, manpower and subcontractor adjustments) to increase production to all of the quantities identified in Section L, Attachment 1, Pricing Workbook Tab D.

5.2.4.2 MoM 2: Diminishing Manufacturing Sources & Material Shortages (DMSMS)

The Offeror shall identify all known and projected DMSMS items for the engine proposed in paragraph 5.2.3.1 and when those items will no longer be available. The Offeror shall describe their proposed approach to mitigate (e.g. via redesign, alternate source or lifetime buy) projected

DMSMS items. The Offeror shall identify the contracting vehicle and status of funding for all active on-contract DMSMS items. The Offeror shall describe their approach to project, monitor, track, and mitigate future DMSMS items for the life of the contract. Additionally, the Offeror’s proposed approach shall state that the Offeror addresses and accepts DMSMS responsibility without additional cost, schedule or performance impacts for all engine components for the life of the contract, including all options.

5.2.5 Subfactor 3: Propulsion System Integration, Aircraft Military Certification, and

Integration Schedule

5.2.5.1 MoM 1: Propulsion System Integration

If the proposed Propulsion System is not integrated and is not in the process of being integrated under the F-15EX program, the Offeror shall describe their proposed approach to fully integrate their Propulsion System, both hardware and software, into the F-15EX Baseline as defined in

Section J, Attachment 1, SOW paragraph 2.1. The description shall address the following: the aircraft; mission planning; Propulsion System modifications; aircraft modifications; testing (to include aircraft/engine configuration); drawings and documentation. If proposed engines for

Integration test program are not new production engines, the following information shall be included in the proposal: Previous Users, Maintenance History and logs, TAC Number (if available) and a plan to ensure compliance with SOW paragraph 3.3.14. The Offeror shall describe their planned contractual relationship with the airframe manufacturer to be able to achieve successful and timely Integration.

If the proposed Propulsion System is already integrated, or in process of being integrated under the F-15EX program, the Offeror shall provide evidence of engine DD250 delivery to the

Government in support of the F-15EX program.

5.2.5.2 MoM 2: Military Certification

If the F-15EX Aircraft with the proposed Propulsion System is not certified and is not in the process of being certified under the F-15EX program, the Offeror shall describe their proposed approach to develop and deliver the necessary data and documentation to successfully obtain

USAF Military Certification for operational use as defined in Section J, Attachment 1, SOW paragraph 3.3.6.

If the F-15EX Aircraft with the proposed Propulsion System is already certified, or in the process of being certified under the F-15EX program, the Offeror shall provide evidence of engine

DD250 delivery to the Government in support of the F-15EX program.

5.2.5.3 MoM 3: Integration Schedule

This MoM provides the instructions for the Integration section of the single program IMS as introduced in paragraph 5.2.4.1. If the proposed Propulsion System is not integrated and is not in the process of being integrated under the F-15EX program, the Offeror’s IMS shall address the

Propulsion System Integration, including: design; technical reviews; data deliveries and approvals; Integration aircraft modification and engine installations; tests, including number and duration of laboratory, ground, and flight tests; regression ground and flight tests to the F-15EX

Baseline; Military Flight Release (MFR) document deliveries (with Government approval cycles); aircraft Military Certification including Propulsion-Military Type Certificate; software deliveries; Section F schedule requirements for CLIN 1000; and other items deemed appropriate by the Offeror.

If the proposed Propulsion System is already integrated, or in the process of being integrated under the F-15EX program,, then the Offeror shall provide evidence of engine DD250 delivery to the Government in support of the F-15EX program.

6.0 Factor 2 — Price

6.1 General Instructions

Information beyond that required by this instruction shall not be submitted. The Offerors shall only submit (for the purposes of Volume II) the completed Pricing Workbook, a narrative to support the pricing approach, and the Pricing Support Information (paragraph 6.6 below). The

Volume II page limit identified in Table 3.3 is specifically for the aforementioned narratives and

Pricing Support Information. Section L, Attachment 1, Pricing Workbook, shall be submitted as electronic MS Excel file.

6.2 Adequate Price Competition

The PCO has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists no additional cost information will be requested and certification under FAR 15.406-2 will not be required. IAW FAR 15.403-1(b) and

15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of the proposal, the PCO determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data.

6.3 Pricing Workbook

The Offeror shall complete Section L, Attachment 1, Pricing Workbook, IAW the instructions contained in Tab A of the Pricing Workbook. Portions of the Pricing Workbook will become part of applicable CLINs. Failure to comply with all the instructions contained in Section L, Attachment 1 may result in the Offeror’s proposal being unawardable. All proposed dollar amounts shall be rounded to the nearest dollar.

6.3.1 Total Evaluated Price (TEP) Calculation

Section L, Attachment 1, Pricing Workbook Tab B calculates the TEP. The Offeror shall only provide data as instructed in Tab A.

6.3.2 Integration and Data

Section L, Attachment 1, Pricing Workbook Tab C includes the pricing for the option CLINs related to Integration and Military Certification (CLINs 1000, 1002, 1003, and 1004). The

Offeror shall only provide data as instructed in Tab A.

6.3.3 VIQ Matrix

Section L, Attachment 1, Pricing Workbook Tab D is the VIQ Matrix. The Offeror shall only provide data as instructed in Tab A. The quantities in the VIQ Matrix will be used for evaluation purposes only and do not obligate the Government to exercise or guarantee such quantities during the performance of any resultant contract.

6.3.4 Separately Priced Computer Software and Digital Engineering Products

Section L, Attachment 1, Pricing Workbook Tab E includes the pricing for the CLINs and option

CLINs related to Commercial Computer Software Licenses and Digital Engineering Products

(CLINs 2002, 2003, 3002, 4002, 5002, 6002, 7002, 8002, 9002). The Offeror shall only provide data as instructed in Tab A.

6.3.5 Auxiliary Transportation Materiel for Spare Engines

Section L, Attachment 1, Pricing Workbook, Tab F includes the pricing for the CLINs and option CLINs related to auxiliary transportation materiel for the shipment of spare engines

(2004AA-2004AC, 3003, 4003, 5003, 6003, 7003, 8003 and 9003). The most probable quantity of spare engines as listed in the bottom of Tab D of the VIQ Matrix is the basis for the quantities listed in Tab F. The Offeror shall only provide data as instructed in Tab A. The quantities in the

VIQ Matrix and Tab F will be used for evaluation purposes only and do not obligate the

Government to exercise or guarantee such quantities during the performance of any resultant contract.

6.4 Pricing Narrative

The Offeror shall provide a narrative of its pricing approach and the methodology used to develop the following:

a) Pricing curves used for pricing the variations in quantity within a given one-year ordering period for each of the following CLINs: 2000AA-2000AM, 3000, 4000, 5000, 6000, 7000, 8000, and 9000

b) Pricing curves (i.e., Learning and Rate curve) used for pricing requirements across the life of the contract [Fiscal Year 2021 (FY21) through FY31]

6.5 Rounding

The Offeror shall round all proposed dollar amounts to the nearest dollar.

6.6 Pricing Support Information

6.6.1 Estimating System

Indicate whether the Offeror has Government approval of the system and if so, provide evidence of such approval.

6.6.2 Purchasing System

Indicate whether the Offeror has Government approval of the system and if so, provide evidence of such approval.

6.6.3 Accounting System

Indicate whether the Offeror has Government Defense Contract Management Agency (DCMA) approval of the accounting system and if so, provide evidence of such approval.

6.6.4 Government Field Support Agencies

The Offeror shall identify the cognizant Defense Contract Audit Agency (DCAA) and DCMA office responsible for administration of the Offeror’s Government contracts.

7.0 Contract Documentation

7.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. Offeror’s proposal shall include a signed copy of the

Model Contract, Sections A through K (omit Sections L and M), and a completed Section L, Attachment 1, Pricing Workbook.

7.1.1 Section A - Solicitation Contract Form

The Offeror shall complete blocks 14 (if necessary), 15, 16, 17 (signature) and 18 (date) on the

SF33 constitutes an offer, which the Government may accept.

7.1.2 Section B - Supplies and Prices

The Offeror shall complete Section L, Attachment 1, Pricing Workbook, as described in paragraph

6.3. The Offeror shall complete the pricing information in Section B for CLINs 1000, 1002, 1003, 1004, 2000AA-2000AM, 2002, 2003, and 2004AA-2004AC. CLINs 1000, 1002, 1003, 1004, 2000AA-2000AM, 2002, 2003, and 2004AA-2004AC in Section B shall match the pricing information in the TEP worksheet and VIQ Matrix. VIQ Matrix will become Attachment 12 to

Section J.

7.1.3 Section C - Descriptions/Specifications/Work Statement

The Offeror shall complete the blanks in LCMC/LPK-C001, INCORPORATED DOCUMENTS/

REQUIREMENTS (OCT 2020).

7.1.4 Section D - Packaging and Marking

No Offeror fill-ins required.

7.1.5 Section E - Inspection and Acceptance

No Offeror fill-ins required.

7.1.6 Section F - Deliveries or Performance

No Offeror fill-ins required.

7.1.7 Section G - Contract Administrative Data

No Offeror fill-ins required.

7.1.8 Section H - Special Contract Requirements

No Offeror fill-ins required.

7.1.9 Section I - Contract Clauses

No Offeror fill-ins required.

7.1.10 Section J – List of Attachments

7.1.10.1 The Offeror shall provide the attachments to the Model Contract as set forth below. The header or footer of each page of each attachment, excluding the cover page, shall include the attachment number, title, contract number, and page number (i.e., "X of Y").

Attachment 4, Department of Defense (DD) Form 254 (if applicable)

Attachment 5, Critical Safety Items List in accordance with DFARS 252.209-7010

Attachment 6, Small Business Subcontracting Plan (if applicable)

Attachment 7, List of Commercial Computer Software to be provided under CLINs

1002, 2002, 3002, 4002, 5002, 6002, 7002, 8002, and 9002

Attachment 8, List of Digital Engineering Products provided under CLIN 2003

Attachment 11, Proposed GFP Table Template (See DFARS PGI 245.103-72 for links to formats and procedures)

Attachment 13, CEO Certification Letter

Offeror-proposed attachments shall be written in such a manner that they can be removed from the proposals, attached to the contract, and awarded as-is. All attachments shall be labeled as

"Section J, Attachment XX" (where "XX" is the appropriate attachment number) in the upper right corner of each page and submitted in the appropriate volume. The electronic versions of the attachments shall be formatted such that the Government can enter the appropriate contract number for award. None of the proposed attachments shall be marked with the Offeror's name;

none shall be marked "Source Selection"; none shall be marked "Proprietary"; and none shall be marked "Copyrighted".

7.1.10.2 Attachment 7, List of Commercial Computer Software

The Offeror shall complete the table in Attachment 7 to document commercial Computer

Software. The table shall list all commercial Computer Software products to be delivered, and for each product provide a brief description, license and rights information, the associated SOW paragraphs and CDRLs, and CLIN(s).

7.1.10.3 Attachment 8, Digital Engineering Products

The Offeror shall complete the tables in Attachment 8 in support of deliverables under CLIN

2003. The included items shall be those necessary to address SOW paragraph 3.1.7.3 and sub-paragraphs, and associated CDRLs. Table 1 shall document existing items, developed under other Government-funded activities, and not previously delivered to the Government. Table 2 shall document existing items, developed and delivered under other Government-funded activities, and do not require re-delivery.

7.1.10.4 Attachment 11, Proposed GFP Table Template

The Offeror shall complete the appropriate tables in Attachment 11 only if the Offeror proposes

GFP as part of its proposal. If GFP is accountable to an existing contract, please provide contract number and contact information of the cognizant PCO.

7.1.11 Section K - Representations, Certifications, and other Statements of Offerors

The Offeror shall complete the annual representations and certification electronically via the

System for Award Management (SAM) website at https:/www.sam.gov/portal/public/SAM/.

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.204-8, Offeror Representations and Certification — Annual Representations and Certifications are correct.

7.2 Other Information Required

7.2.1 Authorized Offeror Personnel

The Offeror shall provide the name, title, and telephone number of the company/division POC regarding decisions made with respect to your proposal and who can obligate your company contractually. The Offeror shall also identify those individuals authorized to negotiate with the

Government.

7.2.2 Government Offices

The Offeror shall provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. The

Offeror shall so provide the name and telephone and fax number for the Administrative

Contracting Officer (ACO) (if applicable).

7.2.3 Company/Division Address, Identifying Codes, and Applicable Designations

The Offeror shall provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

7.2.4 Attachments to the Model Contract

The Offeror shall refer to paragraph 7.1.10.1 of this document.

7.2.4.1 Associate Contractor Agreements (ACA)

Include ACA, if applicable.

7.2.4.2 Attachments to Section L

Section L, Attachment 1 – Pricing Workbook

Section L, Attachment 2 – CEO Certification Letter

7.2.5 Request for Contract Financing

In accordance with FAR 32.113(d), the Offeror may propose one of the following customary contract financing methods: progress payments or performance-based payments (PBPs). If contract financing is desired by the Offeror, the Offeror shall submit with its proposal a written statement detailing the preferred financing method, progress payments or PBPs, but not both.

PBP terms shall be negotiated by the PCO, Offeror, and DCMA after award of contract, at which time Section I clause 52.232-32, “Performance-Based Payments (Apr 2012),” may be added to the contract. The applicable clause for progress payments (52.232-16) has been included in the solicitation. If progress payments are requested, the clause will be retained in the award document.

7.2.6 Bailment Terms

If the Offeror proposes a bailment for the Integration effort, then the Offeror shall submit a written statement detailing preferred terms of the bailment that meet the minimum requirements in SOW. Bailment terms shall be negotiated by the PCO and Offeror after award of contract, at which time the bailment will be attached to the Contract.

7.2.7 Commercial Computer Software

If the Offeror proposes commercial Computer Software under CLINs 1002, 2002, 3002, 4002, 5002, 6002, 7002, 8002, and 9002, the Offeror shall provide all copies of licenses in their proposal to the extent known at the time a proposal is submitted to the Government.