FA811923R0004_______0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

J

2. AMENDMENT/MODIFICATION NO.

FA8119-23-R-0004-0003

3. EFFECTIVE DATE

4. REQUISITION/PURCHASE REQ. NO.

FD20302000777

5. PROJECT NO (If applicable)

6. ISSUED BY CODE

DEPARTMENT OF THE AIR FORCE, AFSC PZABC

3001 STAFF DR STE 1AD2 99A

TINKER AFB OK 73145-3015

BUYER: Jaqueline Hughes/AFSC/PZABC jaqueline.hughes@us.af.mil Phone: (405) 739- 7489

7. ADMINISTERED BY (If other than item 6) CODEFA8119

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE

X

9A. AMENDMENT OF SOLICITATION NO.

FA811923R0004

9B. DATED (SEE ITEM 11)

14-FEB-2023

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended. Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods. ( a ) By completing Items 8 and 15, and returning copies of the amendment; ( b ) By acknowledging receipt of this amendment on each copy of the offer submitted; or ( c ) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return 1 copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Routine

The purpose of this amendment is to provide additional information, update clause 252.211-7003, update section L table 2.3, incorporate updated PWS, and update CLINs 0003, 0004, and 0005 in the Final RFP FA811923R0004. Proposals are due no later than 17 April 2023.

15A. NAME AND TITLE OF SIGNER (Type or print)

15B. CONTRACTOR/OFFEROR

BY ________________________________________________________

(Signature of person authorized to sign)

15C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16B. UNITED STATES OF AMERICA

BY ____________________________________________________

(Signature of Contracting Officer)

16C. DATE SIGNED

FACILITY CODE

NSN 7540-01-152-8070

PREVIOUS EDITION UNUSABLE

30-105 STANDARD FORM 30 (REV. 10-83)

PRESCRIBED BY GSA

FAR (48 CFR) 53.243

X

X X

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

Continuation of block 14. DESCRIPTION OF AMENDMENT/MODIFICATION

The purpose of this amendment is to provide additional information, update clause 252.211-7003, update Section L, Table 2.3, incorporate updated PWS, and update CLINs 0003, 0004, and 0005 in the Final RFP FA811923R0004.

FIRST: The below additional information is hereby provided to aid potential offerors as follows.

This is additional information only:

A) Recent repair contracts have yielded a transmissivity testing failure rate of approximately 50%. While a formal study to determine the failure mode has never been executed, the Air Force suspects aging of the resins used in the original fabrication are causing the electrical failures. During the original manufacture of the radomes, all radomes passed required testing after they underwent electrical correction procedures. The tuning procedures within the TDP provide details on this process.

B) All Non-recurring engineering shall be accounted for within the first option year.

C) CLINs 0003, 0004, 0005, 0010, 0011, 0012 and 0013 are separate and individual deliverables. These will be completed and delivered in accordance with the contract requirements.

D) Completion of all Non-Recurring Engineering are required prior to any TT&E or repair procedures being authorized.

E) The available GFP is currently in working condition. However, it is outdated. For this effort, the USG expects certain items to be replaced and/or updated. Since this equipment will eventually become government property, the NRE portion of the proposal shall specify the equipment and associated costs for these updates.

SECOND: The IUID table referenced in clause 252.211-7003 is hereby updated as follows and shown below in Section I Contract Clauses:

From: CLIN X017 To CLIN X014

THIRD: Section L, Table 2.3: Proposal Organization is hereby updated by referencing the correct ITO paragraph numbers and page limit as shown below and in Section L:

Volume I: ITO Paragraph Number 3.0, Page Limit:

FROM: 70 TO: 75

Volume II: ITO Paragraph Number:

FROM: 5 TO: 4.0

FROM: 5.1 TO: 4.1

FROM: 5.2 TO: 4.2

Volume III: ITO Paragraph Number:

FROM: 6 TO: 5.0

FROM: 6.3.4 TO: 5.3.4

FROM: 6.1 TO: 5.1

Amendment/Modification FA8119-23-R-0004-0003

FROM: 6.1.4 TO: 5.1.4

FROM: 6.3.1-6.3.3 TO: 5.3.1-5.3.3

FROM: 6.3.5 TO: 5.3.5

FOURTH: The PWS is hereby updated and incorporated. This includes changes made to Section

1.19 Surge Mission Services.

FIFTH: Delivery for CLINs 0003, 0004, 0005 is hereby revised as shown in Section B.

SIXTH: All other terms and conditions remain unchanged and in full force and effect.

PART I - THE SCHEDULE

SECTION B

SUPPLIES OR SERVICES AND PRICES/COSTS

First Article - Material Certification

Basic Item No.

Firm Fixed Price Quantity U/I Unit Price Amount

1 LO

CLIN ACRN ACRN Total

0003 AB

Data

MATERIAL CERTIFICATION

Priority: R

Inspection: Origin Acceptance: Origin Quality Assurance: Higher Level Contract Quality Requirements The Contractor shall comply with the standard(s) listed below. (if more than one, check the appropriate standard.)

Title Number Date Tailoring ISO 9001-2008 2008 or later AS9100 9100 or equivalent

Transportation From Continental United States CONUS (CONUS) Sources

TYPE / SHIP TO CODE F.O.B.

A FY2303 ORIGIN

Type / Ship To PACRN Mark For

A FY2303 FIRST ARTICLES

Type / Ship To Quantity (U/I) To be determined _ Req No / Pri

Required Delivery

A FY2303 1 LO TBD

Proposed Delivery

A FY2303 1 LO

Delivery due with CLIN 0002 First Article delivery IAW Form 260 and IAW DD Form 1423-1. Early Delivery is acceptable. “TBD” Notify Supply Planner (SPM) 30 calendar days prior to shipment.

First Article - Certification of Compliance

Basic Item No.

Firm Fixed Price

First Article - Certification of Compliance

Basic Quantity U/I Unit Price Amount

1 LO

CLIN ACRN ACRN Total

0004 AB

Data

CERTIFICATE OF COMPLIANCE

Priority: R

Inspection: Origin Acceptance: Origin Quality Assurance: Higher Level Contract Quality Requirements The Contractor shall comply with the standard(s) listed below. (if more than one, check the appropriate standard.)

Title Number Date Tailoring

A FY2303 ORIGIN

Type / Ship To PACRN Mark For

A FY2303 FIRST ARTICLES

Type / Ship To Quantity (U/I) To be determined _ Req No / Pri

Required Delivery

A FY2303 1 LO TBD

Proposed Delivery

A FY2303 1 LO

Delivery due with CLIN 0002 First Article delivery IAW Form 260 and IAW DD Form 1423-1. Early Delivery is acceptable. “TBD”

First Article - Contractor/Government Test Report

Item No.

Firm Fixed Price Quantity U/I Unit Price Amount

1 LO

CLIN ACRN ACRN Total

0005 AB

Data

FA CONTRACTOR/GOVERMENT TEST REPORT

Priority: R

Inspection: Origin Acceptance: Origin Quality Assurance: Higher Level Contract Quality Requirements The Contractor shall comply with the standard(s) listed below. (if more than one, check the appropriate standard.)

Title Number Date Tailoring

First Article - Contractor/Government Test Report

A FY2303 ORIGIN

Type / Ship To PACRN Mark For

A FY2303 FIRST ARTICLES

Type / Ship To Quantity (U/I) To be determined _ Req No / Pri

Required Delivery

A FY2303 1 LO TBD

Proposed Delivery

A FY2303 1 LO

Delivery due with CLIN 0002 First Article delivery IAW Form 260 and IAW DD Form 1423-1. Early Delivery is acceptable. “TBD”

SHIP TO / PLACE OF PERFORMANCE

TYPE/CODE: + TBD

MARK FOR: (See Individual Line Item) REQUISITION NUMBER: (See Individual Line Item) REQUISITION PRIORITY: (See Individual Line Item)

AWARD NUMBER:

TYPE/CODE: A FY2303

FY2303 DDOO SOP 1ST ARTICLE

CP 405 739 8596

8080 PERIMETER RD BLDG 18 DR 16

TINKER AFB OK 73145 73145-3145

USA

MARK FOR: (See Individual Line Item) REQUISITION NUMBER: (See Individual Line Item) REQUISITION PRIORITY: (See Individual Line Item)

AWARD NUMBER:

PART II - CONTRACT CLAUSES

SECTION I

CONTRACT CLAUSES

252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (MAR 2022)

(IAW DFARS 211.274-6(a)(1), DFARS 212.301(f)(xii))

(a) Definitions. As used in this clause— “Automatic identification device” means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media.

“Concatenated unique item identifier” means—

(1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or

(2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch; and serial number within the original part, lot, or batch number.

“Data matrix” means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022.

“Data qualifier” means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows.

“DoD recognized unique identification equivalent” means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html.

“DoD item unique identification” means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number.

“Enterprise” means the entity (e.g., a manufacturer or vendor) responsible for assigning unique item identifiers to items.

“Enterprise identifier” means a code that is uniquely assigned to an enterprise by an issuing agency.

“Government’s unit acquisition cost” means—

(1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery;

(2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery; and

(3) For items produced under a time-and-materials contract, the Contractor’s estimated fully burdened unit cost to the Government at the time of delivery.

“Issuing agency” means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459.

“Issuing agency code” means a code that designates the registration (or controlling) authority for the enterprise identifier.

“Item” means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts.

“Lot or batch number” means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions.

“Machine-readable” means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards.

“Original part number” means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface.

“Parent item” means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent.

“Serial number within the enterprise identifier” means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise.

“Serial number within the part, lot, or batch number” means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment.

“Serialization within the enterprise identifier” means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier.

“Serialization within the part, lot, or batch number” means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier.

“Type designation” means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto.

“Unique item identifier” means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent.

“Unique item identifier type” means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at https://www.acq.osd.mil/asda/dpc/ce/ds/unique-id.html.

(b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item.

(c) Unique item identifier.

(1) The Contractor shall provide a unique item identifier for the following:

(i) Delivered items for which the Government’s unit acquisition cost is $5,000 or more, except for the following line items:

Contract Line, Subline, or Exhibit Line Item Number

Item Description

See Schedule as Applicable

(ii) Items for which the Government’s unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table:

Contract Line, Subline, or Exhibit Line Item Number

Item Description

*Items less than $5000, which require UID, will be specifically identified in the schedule.

See Schedule as Applicable

X001 See Schedule as Applicable X002 See Schedule as Applicable X007AA See Schedule as Applicable X007AB See Schedule as Applicable X007AC See Schedule as Applicable X007AD See Schedule as Applicable X014 See Schedule as Applicable

(iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number _____( or See Schedule as Applicable).

(iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number _____( or See Schedule as Applicable).

(v) Any item not included in paragraphs (c)(1)(i), (ii), (iii), or (iv) of this clause for which the contractor creates and marks a unique item identifier for traceability.

(2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor.

(3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology—International symbology specification—Data matrix; ECC200 data matrix specification.

(4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that—

(i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor:

(A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Indentifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology--EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard.

(C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with Air Transport Association Common Support Data Dictionary; and

(ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology–Transfer Syntax for High Capacity Automatic Data Capture Media.

(5) Unique item identifier.

(i) The Contractor shall—

(A) Determine whether to—

(1) Serialize within the enterprise identifier;

(2) Serialize within the part, lot, or batch number; or

(3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number);and

(B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: Original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version.

(C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and

(D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version.

(ii) The issuing agency code—

(A) Shall not be placed on the item; and

(B) Shall be derived from the data qualifier for the enterprise identifier.

(d) For each item that requires item unique identification under paragraph (c)(1)(i) , (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information:

(1) Unique item identifier.

(2) Unique item identifier type.

(3) Issuing agency code (if concatenated unique item identifier is used).

(4) Enterprise identifier (if concatenated unique item identifier is used).

(5) Original part number (if there is serialization within the original part number).

(6) Lot or batch number (if there is serialization within the lot or batch number).

(7) Current part number (optional and only if not the same as the original part number).

(8) Current part number effective date (optional and only if current part number is used).

(9) Serial number (if concatenated unique item identifier is used).

(10) Government’s unit acquisition cost.

(11) Unit of measure.

(12) Type designation of the item as specified in the contract schedule, if any.

(13) Whether the item is an item of Special Tooling or Special Test Equipment.

(14) Whether the item is covered by a warranty.

(e) For embedded subassemblies, components, and parts that require DoD item unique identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the following information:

(1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part.

(2) Unique item identifier of the embedded subassembly, component, or part.

(3) Unique item identifier type.**

(4) Issuing agency code (if concatenated unique item identifier is used).**

(5) Enterprise identifier (if concatenated unique item identifier is used).**

(6) Original part number (if there is serialization within the original part number).**

(7) Lot or batch number (if there is serialization within the lot or batch number).**

(8) Current part number (optional and only if not the same as the original part number).**

(9) Current part number effective date (optional and only if current part number is used).**

(10) Serial number (if concatenated unique item identifier is used).**

(11) Description.

** Once per item.

(f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows:

(1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/ .

(2) Embedded items shall be reported by one of the following methods—

(i) Use of the embedded items capability in WAWF;

(ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/; or

(iii) Via WAWF as a deliverable attachment for exhibit line item number ______, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423.

(g) Subcontracts. If the Contractor acquires by subcontract, any items for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial items.

(The above Clause/Provision has been modified.)

PART III - LIST OF DOCUMENTS, EXHIBITS, AND OTHER ATTACHMENTS

SECTION J

LIST OF ATTACHMENTS

Form Number Description/File Name Date Number of Pages ATTACHMENT_26_PWS_Updated.pdf Performance Work Statement

20MAR2023 34

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

Section L Instructions to Offerors (ITO)

1.0 Program Structure and Objective

The Government plans to award a single contract for the New Manufacture & Repair of the B-1 Nose Radome. This effort is Firm-Fixed-Price, best estimate quantity, for both the supply and repair. The contract will be for one base year with four one-year option years. Currently the best estimate quantity for manufacture of new B-1 Nose Radomes is 45, with the repair of 27 B-1 Nose Radomes over the life of the contract.

1.1. 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) Section M, Evaluation Factors for Award.

1.2. Budget/Funding Information

Funding will be obligated for the Firm-Fixed-Price (FFP) Contract Line Item Number (CLIN) 0002 for the First Article.

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 must include all data and information requested by the ITO and shall be submitted in accordance with these instructions.

Any Offeror who submits an incomplete proposal may be considered ineligible for award. The proposal shall be compliant with the requirements as stated in the Performance Work Statement (PWS) and attachments.

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

2.1.6 All or parts of the Offeror’s Technical proposal may be added to the contract. Should there be any discrepancies between the Technical proposal and the Performance Work Statement (PWS), the PWS will take precedence.

2.2. General Information

2.2.1. Point of Contact

The Contracting Officer (CO) and the Contracting Specialist (CS) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CS. Written requests for clarification may be sent to the CS electronically via email.

2.2.2. Debriefings

The CS will promptly notify Offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with 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 CS will notify unsuccessful Offerors in accordance with FAR 15.503. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with 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 CS in writing with supporting rationale as well as the remedies the Offeror is asking the CS 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://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. Drawings may only be disseminated IAW Distribution Code D. POC for referenced documents is Jaqueline Hughes jaqueline.hughes@us.af.mil.

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 by electronic submission using DoD SAFE per section 2.6 showing the time and date specified for receipt, the solicitation number, and the name and address of the Offeror. No hard copies will be allowed as a timely proposal. Submissions, modifications, revisions, and withdrawal of proposals must be documented, by time and date of receipt electronically via DoD SAFE only.

2.3. Organization/Number of Copies/Page Limits

2.3.1. 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. A Team List of the Offeror’s primary Point of Contacts shall be submitted in each volume using the format shown in Attachment 2 of the ITO.

2.3.3. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.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 and with the number of copies as specified in Table 2.3. The contents of each proposal volume are described in the ITO paragraph as noted in the table below.

Table 2.3. Proposal Organization

Volume

ITO

Paragraph Number Volume Title

Disk Copies Page

Limit

I 3.0 Technical 3/1 75

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

3.2.2 Team List (see Attach 2.0) (Not included in 75 page

limit)

3.2.2 Table of Contents (Not included in 75 page limit) Unlimited

3.2.2 List of Tables and Figures (Not included in 75 page

limit) Unlimited

3.2.2 Glossary of Abbreviations and Acronyms (Not

included in 75 page limit)

Unlimited

3.2.3 Subfactor 1 Technical Capability

3.2.4 Subfactor 2 VATEP Delivery Schedule

II 4.0 Price Volume 2/1 Unlimited

4.1 General Information Unlimited

4.2 Volume Organization Unlimited

III 5.0 Contract Documentation 2/1 Unlimited

2.2.1 Title Page (SF1449) 1

2.2.2 Team List (see Attach 2.0) 5

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

2.2.2/5.3.4 Team List, Arrangements, and/or Letters of Intent Unlimited

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

5.1.4 Representations and Certifications (Section K) N/A

5.3.1-5.3.3 Contact Information Unlimited

5.3.5 Attachments to the Model Contract Unlimited

NOTE: 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.4. 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 Proposed Organization Chart as unlimited.

2.3.5. Pricing Information

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

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.6. 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 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 each’s respective volume for the evaluation, but may also utilize information from other volumes as well.

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. 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. 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. Offerors are prohibited from using other Arial fonts such as Arial Black, Arial Narrow or Arial Rounded MT Bold. 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 Evaluation Notice (ENs). These limitations shall apply to electronic proposals.

2.4.1. 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-pt.

These limitations shall apply to electronic 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 electronic proposals.

2.5. Reserved

2.6. Electronic Offers

All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested Offerors must e-mail Gregory Benjamin at gregory.benjamin.3@us.af.mil and Jaqueline Hughes at jaqueline.hughes@us.af.mil in order to receive a request code to drop-off (upload) files in DoD SAFE. One of the Government Point of Contact (GPOC)s will send an e-mail to the offeror acknowledging the request for a proposal drop-off code in DoD Safe. The GPOC e-mail acknowledging the request will not be sent to the offeror after close of business hours, weekends, or on nationally observed holidays. If you do not receive an acknowledgement e-mail from either of the GPOCs after 72 hours, you must send another e-mail. E-mails will not be returned after close of business hours, weekends, or on nationally observed holidays.

After the e-mail request for a drop-off code has been sent from the offeror and the offeror has received the acknowledgment e-mail from either GPOC, the offeror will then receive an e-mail from DoD SAFE to drop-off proposals and other requested documents. If the offeror does not receive the e-mail from DoD SAFE the offeror will need to check SPAM and JUNK folders before requesting another drop-off code from the GPOC.

The request for drop-off is only valid for 14 days. If the 14 days has expired and the RFP is still open, the offeror may send another e-mail request for drop-off code to the GPOCs e-mail addresses listed above. Be advised that classified information is not allowed on DoD SAFE. Any files containing CUI/PII/PHI must be encrypted prior to uploading or by checking the “Encrypt every file” box. The offeror is allowed to drop-off one or more files (up to 8GB total). The offeror may select the box ‘Send me an e-mail when each recipient picks up the files” for documentation purposes. The GPOC will receive an automated e-mail containing the information the offeror has entered and instructions for downloading the file(s). The GPOC will have 7 days to retrieve the files submitted in the drop-off. DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours.

All electronic documents and files submitted shall contain 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 IV in electronic format. Each volume shall be submitted as a separate file. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2016, MS Excel 2016, MS-Power Point versions 2016, and Adobe PDF. Note PDF files must be searchable and able to copy and paste. For amendment purposes to the proposal, the "original" proposal shall be clearly identified.

2.7. Distribution

Once the Offeror has uploaded the Offeror’s proposal in its entirety to DoD SAFE, the Offeror shall take a screen shot (Print Screen function) of the Offeror’s DoD SAFE upload confirmation screen showing all the uploaded files included in the proposal submission. The Offeror shall notify both Gregory Benjamin (PCO) and Jaqueline Hughes (Contracting Specialist) by email that the files have been uploaded and provide a copy of the DoD SAFE completed upload confirmation screen shot. If the proposal files are uploaded in their entirety prior to the proposal closing date and time, and the Offeror has notified both Gregory Benjamin and Jaqueline Hughes the files have been uploaded (notification is to include the DoD SAFE upload confirmation screen shot has also been provided), the proposal will be considered timely, even if the files are not accessible to the PCO in DoD SAFE until after the proposal closing date and time. If the Offeror fails to notify both Gregory Benjamin and Jaqueline Hughes by email, the files will be considered timely if they are accessible in DoD SAFE prior to the closing date and time. However, they will be considered late proposals, if they are not accessible until after the proposal date and time.

Email addresses are as follows:

Gregory Benjamin: gregory.benjamin.3@us.af.mil Jaqueline Hughes: jaqueline.hughes@us.af.mil

3.0 Factor 1 – Technical

3.1. General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important.

Your responses will be evaluated against the Technical subfactors defined in Section M, 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 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.

3.2.2. Volume Organization

The Technical Volume shall be organized according to the following general outline:

(1) Team List Attach 2.0

(2) Table of Contents

(3) List of Table and Drawings

(4) Glossary

(5) Factor One: Technical

(6) Subfactor One: Technical Capability

i) Delivery

(7) Subfactor Two: VATEP Delivery Schedule

i) First Article Schedule

ii) Repair Schedule

3.2.3. Subfactor One: Technical Capability

The Offeror shall provide an approach for the production and repair of the B-1 Nose Radome. As a minimum, the approach shall provide the following essential elements:

a. Delivery - The Offeror shall state how their approach will meet the proposed delivery schedule of First Article after Award of Contract. The Offeror shall also state how their approach meets the proposed delivery schedule of repaired assets after receipt of asset.

Additionally, the Offeror shall provide convincing rationale describing how the approach will meet the delivery requirements.

3.2.4. Subfactor Two: VATEP Delivery Schedule

The Offeror is afforded an opportunity to provide an approach which is less than the maximum requirement for the elements listed below. As set forth in Section M, paragraphs 2.2.1. and 2.2.2, Subfactor Two: VATEP Delivery Schedule, 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 (TPP), 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 Section M, paragraphs 2.2.1. and 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 Two: VATEP Delivery Schedule if it is not seeking a price decrement for achieving performance capabilities less that the required maximum amount. The Offeror shall clearly document in its proposal if it is not addressing Subfactor 2. The Offeror is only permitted to propose one delivery schedule.

a) The Offeror shall state how their approach improves upon the maximum delivery requirement of 24 months upon Contract Award (PWS 1.15). Additionally, the Offeror shall provide the analysis and methodology used to determine the enhanced delivery schedule is less than the maximum delivery scheduled as required in PWS 1.15.

b) The Offeror shall state how their approach improves upon the maximum delivery requirement of 2 months upon receipt of asset (PWS 1.15). Additionally, the Offeror shall provide the analysis and methodology used to determine the enhanced delivery schedule is less than the maximum delivery scheduled as required in (PWS 1.15).

4.0. Factor 2 – Price

4.1. In the price volume, the Offeror shall provide the following information in addition to the pricing in Supplies or Services and Prices/Cost Section (Part B) of the solicitation. These instructions are to assist you in submitting information required to evaluate the reasonableness of your proposed price. Compliance with these instructions is mandatory and failure to comply may result in rejection of your proposal.

4.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 must 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.

4.2.1. Price Reasonableness

The Government will evaluate proposals for reasonableness. Normally, price reasonableness is established through adequate price competition, but may also be determined through other price analysis techniques.

The burden of proof for credibility of proposed costs/prices rests with the Offeror. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.).

4.2.2. Balance

The Government will evaluate proposals for balance. 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. Offerors shall provide rationale for any proposed CLIN price increase greater than 5% from one year to another, or any proposed CLIN price decrease from one year to another. 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, Offerors shall complete the attached Pricing Matrix (Attachment 32). Completion of the Pricing Matrix allows efficient comparison of proposed pricing with the PWS requirements.

4.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. Offerors shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.).

4.2.4. Cost or Pricing Information Requirements

FAR 12.209 gives the requirement to establish price reasonableness in accordance with 13.106-3 (Simplified Acquisition Procedures), 14.408-2 (Sealed Bidding), or 15.4 (Contract Pricing by Negotiation), as applicable. FAR part 15 applies. In accordance with FAR 15.403-3-1(b), prices based on adequate price competition do not require submission of cost or pricing data. In accordance with FAR 15.403-3(a), however, information other than cost or pricing data may be required to support price reasonableness. FAR 15.403-3(a)(1) provides for obtaining information other than cost or pricing data if needed to determine price reasonableness. Therefore, the FAR does not preclude the requirement for obtaining other than cost or pricing data under certain circumstances and the Government reserves the right to obtain 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 via other than cost or pricing data. If, after receipt of proposals, the CO 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.

4.2.5. Rounding

All dollar amounts shall be rounded to the nearest penny.

5.0. Contract Documentation

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

5.1.1. Solicitation/Contract Form (Section A)

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.

5.1.2. Supplies or Services and Costs/Prices (Section B)

Completed pricing information in the Pricing Matrix.

5.1.3. Contract Clauses (Section I)

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

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