W912CH26B0006-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

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 amendments: (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 ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, etc.) Set

Forth In Item 14, Pursuant To The 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 _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

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.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

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

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0002 2026JUN16

W912CH

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

LYNDSEY M. PENA

EMAIL: LYNDSEY.M.PENA.CIV@ARMY.MIL

W912CH-26-B-0006

2026MAY27

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 21

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: LYNDSEY M. PENA

Buyer Office Symbol/Telephone Number: CCTA-APS-B/(520)687-3936

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

AMENDMENT: 0002

(a) The purpose of Amendment 0002 to Invitation for Bids (IFB) W912CH-26-B-0006 is as follows:

(1) SECTION A

(i) Narrative A.1. DESCRIPTION OF ACTION (h) has been edited to contain the contact information for the new Contract Specialist working this action.

(ii) Narrative A.2. IFB STRUCTURE (b) has been edited to state "Please see Section L.6. SUBMISSION OF SUBCONTRACTING PLAN SEALED BIDDING and 52.219-9 SMALL BUSINESS SUBCONTRACTING PLAN (JAN 2025) -- ALTERNATE I (FEB 2026) for additional information" in place of "Please see

Section L.9. Submission of Subcontracting Plan - Sealed Bidding and Alternate I: Small Business Subcontracting Plan for additional information."

(iii) Narrative A.3. ELECTRONIC CONTRACTING (b) and (g) have been edited to contain the contact information for the new Contract

Specialist working this action.

(2) SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

(i) Narrative C.3. CONFIGURATION MANAGEMENT DOCUMENTATION has been edited to identify the respective CDRL numbers for C.3.(e)(i), C.3.(e)(ii), and C.3.(e)(iii).

(3) SECTION F - DELIVERIES OR PERFORMANCE

(i) 252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023) has been edited to include omitted fill ins "-1-" through "-6-."

(ii) Narrative F.2 LONG TERM CONTRACTS - FOB DESTINATION has been added.

(4) SECTION G - CONTRACT ADMINISTRATION DATA

(i) 252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023) has been edited to include omitted fill ins "-1-" through "-16-."

(5) SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

(i) Numbering of L.2. BID CONTENT AND FORMAT (b) has been corrected.

(b) All other terms and conditions remain unchanged and in full force and effect.

*** END OF NARRATIVE A0003 ***

A.1. DESCRIPTION OF ACTION

(a) This Invitation for Bids (IFB) is intended to result in the award of a firm-fixed-price(FFP) five-year Requirements contract for the following:

Noun: Nozzle,Fuel,Oil

National Stock Number (NSN): 4930-01-440-1085

Part number: 20917308A/86184, 247037-1/0DT23

The resulting contract will establish pricing to be utilized through issuance of delivery orders, for discrete quantities during the period stated in the Schedule. The Government bears no responsibility to issue an initial minimum order upon base contract award.

Further, the quantities listed in this IFB and the resulting contract are estimates only and not a representation they will be ordered, nor is it a representation that conditions affecting Government needs will be stable. Please see RFO FAR 52.216-21: Requirements for

2 21

W912CH-26-B-0006

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

additional information.

(b) Please see Section L.6. Submission of Subcontracting Plan - Sealed Bidding and RFO 52.219-9: Small Business Subcontracting Plan

(Alternate I) for additional information

(c) There is a Technical Data Package (TDP) associated with this procurement. The TDP is distribution code "A", A-Approved for Public

Release. Distribution is Unlimited. Please see Section C.1. TDP Information for instructions on how to access this data.

(d) Bidders are advised to carefully read and understand this entire IFB, including Sections L and M, prior to submitting a bid for evaluation. The Government will evaluate bids without discussions and does not assume the duty to search for data to cure problems it finds in any bid. Therefore, all information necessary for the review and evaluation of a bid is to be contained within the bid submission.

(e) Bidders must complete all necessary fill-ins and representations throughout this IFB, including but not limited to:

(1) STANDARD FORM 33 (IFB COVER PAGE): Blocks 13 through 18

(2) SECTION B: The unit prices and dollar amounts requested for CLIN 0011-0015: Production Quantity for all five order years

(3) SECTION E: E.2. Inspection and Acceptance Points - Origin;

(4) SECTION K: RFO FAR 52.209-13 - Violation of Arms Control Treaties or Agreements - Certification;

(5) SECTION K: RFO FAR 52.225-18 - Place of Manufacture; and

(6) SECTION K: RFO FAR 52.229-11 - Tax on Certain Foreign Procurements - Notice and Representation

Failure to complete all required fill-ins and representations may result in the rejection of a bid.

(f) Bidders shall acknowledge receipt of all IFB amendments by the date and time indicated for receipt of bids. If this IFB is amended, then all terms and conditions which are not modified remain unchanged. Please see Section A.4. Acknowledgement of Amendments and FAR

52.214-3: Amendments to IFBs for additional information.

(g) All bids received in response to this IFB shall be valid for a minimum of 90 calendar days. Please see RFO FAR 52.214-16: Minimum

Bid Acceptance Period for additional information.

(h) Bid opening will be held with all Bidders and shall commence on 08 July 2026 at 1 p.m. local time (Warren, MI). Due to security protocols at the Detroit Arsenal, bid opening will be held virtually. Bidder attendance at this event is not required. The Government will provide a Microsoft Teams link, teleconference number, and passcode prior to bid opening. Please contact the following personnel via e-mail, after IFB close and at least 24 hours prior to bid opening to receive this information:

Lyndsey Pena

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: lyndsey.m.pena.civ@army.mil

-and-

Ciara Woodward-Brown

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: Ciara.l.woodard-brown.civ@army.mil

A.2. IFB STRUCTURE

(a) North American Industry Classification System. The Government will utilize North American Industry Classification System (NAICS) code 336412 Aircraft Engine & Engine Parts Manufacturing for this procurement. Failure to register via the System for Award Management

(SAM) website for this NAICS code, prior to submitting a bid in response to this IFB, may preclude your firm from receiving an award.

Bidders should be aware of how U.S. Small Business concerns are defined in FAR Part 19, Defense Federal Acquisition Regulation

Supplement (DFARS) Part 219, and 13 CFR 121 Small Business Size Regulations. Bidders are advised to review 13 CFR 121.103, "How does

SBA determine affiliation?", if applicable to this IFB.

(b) This IFB is issued on an unrestricted basis. All large businesses under NAICS code 336412 are required to submit a Subcontracting

3 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Plan with their bid. Please see Section L.6. SUBMISSION OF SUBCONTRACTING PLAN SEALED BIDDING and 52.219-9 SMALL BUSINESS SUBCONTRACTING

PLAN (JAN 2025) -- ALTERNATE I (FEB 2026) for additional information.

c) Ordering Periods and Delivery Orders. There will be five one-year ordering periods beginning the date of contract award. Future delivery orders will be awarded pursuant to RFO FAR 52.216-18: Ordering, RFO FAR 52.216-19: Order Limitations, RFO FAR 52.216-21:

Requirements and Section B of this IFB.

(d) All bids received in response to this IFB shall be valid for a minimum of 90 calendar days.

A.3. ELECTRONIC CONTRACTING

(a) All Army Contracting Command - Detroit Arsenal IFBs will be publicized on the System for Award Management (SAM) website:

https://www.SAM.gov

Any additional attachments, including the TDP(s) when available electronically, will be separate attachments or links embedded in the

IFB.

(b) Interested Bidders shall submit a completed IFB, including the Standard Form 33, via e-mail with the subject line "IFB Submission -

W912CH-26-B-0006 (Contractor Name)" to the following personnel:

Lyndsey Pena

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: lyndsey.m.pena.civ@army.mil

-and-

Ciara Woodard-Brown

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: ciara.l.woodard-brown.civ@army.mil

Once a bid is received, the Contract Specialist will reply to the respective Bidder indicating receipt of the submission. NOTE: FAX, HARDCOPY (PAPER), AND DVD/CD-ROM BIDS WILL NOT BE ACCEPTED. HAND-CARRIED BIDS, WHETHER HARDCOPY OR ELECTRONIC, WILL ALSO NOT BE

ACCEPTED.

(c) Please pay close attention to the Issued By block on the cover page of this IFB for a closing date and time. The closing date and time is based on the local time of the listed location of the Issued By office. In accordance with FAR 52.214-7: Late Submissions, Modifications, and Withdrawals of Bids, Bidders are responsible for submitting bids, and any revisions/modifications, so as to be received by the Government office designated in the IFB by the date and time specified.

(d)It is the Bidder's responsibility to ensure the bid is received by the date and time specified on the cover page of this IFB. In accordance with FAR 52.214-7: Late Submissions, Modifications, and Withdrawals of Bids, if the bid was not received at the initial point of entry to the Government infrastructure (in this case, received via e-mail) by the exact date and time specified on the cover page of this IFB, it will be determined late. Bid is defined to mean ALL volumes or parts required by the IFB are included in the electronic submission.

NOTE: There is no "expected" or "target" length of time for bid submission; size and content may be factors, therefore Bidders are strongly cautioned when submitting bids to allow adequate time for submission.

(e) IFBs may remain posted on SAM.gov after the IFB closing date. If the response deadline has passed for the IFB, vendors will no longer be able to submit electronic responses.

(f) Any award issued as a result of this IFB will be distributed electronically. In the event of a FOIA request for a copy of any award issued as a result of this IFB, or any subsequent modifications to the contract, the contract and modifications will be released, including the awarded unit price. This is the notice required by Executive Order 12600 (June 23, 1987) of the Government's intention to release unit prices in response to any request under the Freedom of Information Act (FOIA), 5 USC 552. Unit price is defined as the contract price per unit or item purchased as it appears in Section B of the contract and is NOT referring to nor does it include cost or pricing data/information. If a Bidder objects to such release in the base contract or contract modifications, the Bidder must notify the Contracting Officer in writing prior to the closing date identified in this IFB and include the rationale for the objection consistent with the provisions of FOIA. A release determination will be made based on the rationale given.

(g) All questions pertaining to this IFB shall be submitted via e-mail to the following personnel by 02 June 2026 at 4:00 PM local time

(Warren, MI):

4 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Lyndsey Pena

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: lyndsey.m.pena.civ@army.mil

-and-

Ciara Woodard-Brown

CONTRACT SPECIALIST, ARMY CONTRACTING COMMAND - DETROIT ARSENAL

EMAIL: ciara.l.woodard-brown.civ@army.mil

Responses will be furnished via a Q&A log posting to SAM.gov or as an IFB amendment, if the information is necessary in submitting bids or if the lack thereof would be prejudicial to other prospective Bidders. Please see RFO FAR 52.214-6: Explanation to Prospective

Bidders for additional information. The Government will review all questions received but is not obligated to answer questions submitted after the date/time noted above, prior to IFB close.

(h) For technical assistance in doing business with the Government, and doing business electronically, please visit the Procurement

Technical Assistance Center (PTAC) website to locate a regional center at:

http://www.aptac-us.org"http://www.aptac-us.org

A.4 ACKNOWLEDGEMENT OF AMENDMENTS

Acknowledge all the amendments received from the Government by identifying the amendment number and its issue date below:

Amendment Number: Date:

par_________________ ________________

A.5. ARMY CONTRACTING COMMAND WARREN (DTA) OMBUDSPERSON

Information regarding the Ombudsperson for this contract is located at the following website: https://tacom.army.mil/ombudsperson. (Best viewed using Google Chrome or Microsoft Edge)

A.6. ALL OR NONE - COMMERCIAL ITEM ACQUISITION - SEALED BIDDING

(a) This provision serves as official notice that all bid submissions must offer to provide the total quantity of all items identified in this solicitation.

(b) Only one award will be made as a result of this solicitation. Bids submitted for less than the total quantity of all items identified in this solicitation will not be considered for award.

(c) Note: This provision supersedes any other solicitation language that pertains to or references multiple awards.

5 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0001 ***

6 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1. TECHNICAL DATA PACKAGE INFORMATION

The following "X"d item applies to this solicitation:

[ ] 1. There is no Technical Data Package (TDP) included with this solicitation.

[X ] 2. The TDP for this solicitation resides within the System for Award Management (SAM) (https://SAM.gov) associated with this solicitation number:

W912CH-26-B-0006

To access the data through SAM:

a. Log on to the SAM web site: https://SAM.gov.

b. Search for the solicitation number.

c. Click on the Attachment 0001: MIL-STD-2073-1.

d. If the attachment is restricted, request access to the document.

(1) TDPs that have an Export Control Warning Notice are subject to the Arms Export Control Act (Section 2751 of Title 22, United States

Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 48014852 of Title 50, United States Code).

(2) Further dissemination of the TDP must be in accordance with provisions of DoD Directive 5230.25, DoDI 5230.24, its Distribution

Statement markings, and U.S. export control laws. This also applies to distribution of the TDP to all SUBCONTRACTORS at every level.

(3) To obtain these TDPs, contractors must have a current DD 2345, Militarily Critical Technical Data Agreement on file with Defense

Logistics Information Service (DLIS). To obtain certification, go to DD FORM 2345 Instructions and DD 2345.

(4) Upon completion of the purposes for which Government Technical Data has been provided, the Contractor is required to destroy all documents, including all reproductions, duplications, or copies thereof as may have been further distributed by the Contractor.

Destruction of this technical data shall be accomplished by: shredding, pulping, burning, or melting any physical copies of the TDP and/or deletion or removal of downloaded TDP files from computer drives and electronic devices, and any copies of those files.

e. If technical data is otherwise restricted, select "Request Explicit Access." This will generate an email to the Contract Specialist and Contracting Officer at Army Contract Command - Warren (DTA) with all the information needed to grant contractor access to restricted documents. SAM will automatically generate an email stating when the requesting contractor has permission to view or download TDP items.

f. If multiple individuals in the contractor's organization need access to the Technical Data Package (TDP) for a solicitation and an explicit access request is required, each individual MUST submit an explicit access request to be granted approval to view the TDP.

Those same individuals MUST be registered in SAM. Any individuals no longer with the company should be deleted. Questions related to registration in SAM should be directed to https://www.sam.gov/ The SAM helpdesk phone number is (866) 606-8220. Vendors are responsible for placing correct information in SAM.

g. It is strongly suggested that contractors submit the explicit access request and provide the buyer with the completed "Use and Non-

7 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Disclosure Agreement" at the same time if the solicitation requires both to gain access to view the TDP.

C.2. DRAWING LIMITATIONS

(a) The drawings supplied with this contract are not shop or process drawings. The drawings are engineering design drawings, are adequate to permit manufacture, and:

(1) depict the completed (item(s), and

(2) serve as the basis for inspection of the completed item(s).

(b) These drawings DO NOT cover intermediate drawings/specifications or steps in the manufacturing process. As a result, even if all the dimensions and tolerances specified in the engineering design drawing for each individual part are met, a cumulative unacceptable fit for the contract item could result.

(c) The Contractor is responsible for producing the shop or process drawings needed to cover intermediate steps in the manufacturing process.

(d) The Contractor agrees that he has obtained all specifications and drawings necessary to manufacture the items being solicited in accordance with the TDP including all incorporated specifications and drawings. The contractor is responsible for having all drawings and specifications. Delivery delays are not excusable where the contractor asserts that it did not have a specification or drawing and has failed to request, in writing, the specification from either the Contracting Officer or Contract Specialist prior to the solicitation closing date.

(e) Failure to produce an end item with a cumulative fit that conforms to Government drawings, specifications or other supplemental manufacturing documentation, will result in the Contractor being responsible for correcting this condition at no additional cost to the

Government and no delivery schedule extension.

C.3. CONFIGURATION MANAGEMENT DOCUMENTATION

The Contractor may submit Engineering Change Proposals (ECPs), Requests for Variance (RFVs), and Notices of Revision (NORs) for the requirements in the Government-provided Technical Data Package (TDP).

a. The Configuration Change Management section of SAE EIA-649-1(current revision) Configuration Management Requirement for Defense

Contracts, Paragraph 3.3, shall be used for configuration control of material with the following exclusions: paragraph 3.3(3); the second sentence of paragraph 3.3.1.8.1(1).

b. Furnished item(s) shall conform to the approved configuration requirements/revision, unless a Request for Variance (RFV) is processed and approved as provided by Paragraph E. below. The term "Request for Variance" includes Requests for Deviations and Waivers.

c. Value Engineering Change Proposals (VECPs) for cost saving improvements to the TDP should not be processed per SAE EIA-649-1 and should be referred to Section I FAR Clause 52.248-1 - Value Engineering.

d. All ECPs submitted will be deemed routine. If an ECP is considered as an emergency or urgent; that justification for the rationale shall be included in the ECP submittal with all applicable supporting documentation.

e. For ECPs, RFVs, or NORs, the Contractor must submit the documentation listed in sub-paragraphs e (i) through e (iii). Failure to submit a complete legible package may result in return of the ECP/RFV/SCN/NOR without processing.

(i) for ECPs, the Contractor shall prepare and deliver the ECP in accordance with (IAW) CDRL A001.

(ii) for RFVs, the Contractor shall prepare and deliver the RFV IAW CDRL A002.

8 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(iii) for NORs, the Contractor shall prepare and deliver the NOR IAW CDRL A003.

f. The Government's acceptance of the data deliverable required by CDRL/DD Form 1423 in e(i)-(iii) above signifies only that the data satisfies the requirements of the DID and is considered acceptable for Government processing. Acceptance of the data deliverable does not signify "technical approval" of the change proposed by the deliverable and should not be interpreted as authorizing the Contractor to proceed with the work proposed by the change. Disposition of the change (approval/disapproval) will follow acceptance of the CDRL at the Government's sole discretion. Incorporation of an approved RFV or ECP will require execution of a contract modification.

g. The Contractor should direct questions regarding the status of an ECP or RFV to the Procuring Contracting Officer (PCO) and copy the

Administrative Contracting Officer (ACO).

h. The submission of an ECP/RFV/SCN/NOR does not affect the required delivery date of the contract.

*** END OF NARRATIVE C0001 ***

9 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION F - DELIVERIES OR PERFORMANCE

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

F-1 CHANGED 252.211-7003 ITEM UNIQUE IDENTIFICATION AND VALUATION (JAN 2023) JAN/2023

(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 number; 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

10 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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

N/A________________ N/A___________________________________

N/A________________ N/A___________________________________

N/A________________ N/A___________________________________

(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

N/A________________ N/A___________________________________

N/A________________ N/A___________________________________

N/A________________ N/A___________________________________

(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 N/A.

11 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(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 N/A.

(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 Identifiers 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 the 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.

12 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(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

13 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 -7-, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423.

(g) Subcontracts. If the Contractor acquires by subcontract any item(s) 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 products or commercial services.

(End of clause)

F.1 TIME OF DELIVERY

F.1.1 The Government requires delivery to be made according to the following schedule:

CLIN ESTIMATED QTY CALENDAR DAYS AFTER AWARD

0011 907 EST (EA) 75 EA 180 DAYS after award, then 75 ea every 30 days

0012 204 EST (EA) 17 EA 180 DAYS after award, then 17 ea every 30 days

0013 204 EST (EA) 17 EA 180 DAYS after award, then 17 ea every 30 days

0014 204 EST (EA) 17 EA 180 DAYS after award, then 17 ea every 30 days

0015 204 EST (EA) 17 EA 180 DAYS after award, then 17 ea every 30 days

F.1.2 The Government will evaluate equally, as regards time of delivery, offers that propose delivery of each quantity within the applicable delivery period specified above. Offers that propose delivery that will not clearly fall within the applicable required delivery period specified above, may be considered nonresponsive and rejected. The Government reserves the right to award under either the required delivery schedule or the proposed delivery schedule, when an offeror offers an earlier delivery schedule than required above. If the offeror proposes no other delivery schedule, the required delivery schedule above will apply.

Offeror's Proposed Delivery Schedule:

CLIN ESTIMATED QTY CALENDAR DAYS AFTER AWARD

0011 ____ EA DAYS

0012 _____ EA DAYS

0013 _______ EA DAYS

0015 _______ EA DAYS

F.1.3 Attention is directed to the Contract Award provision of the solicitation that provides that a written award or acceptance of offer mailed, or otherwise furnished to the successful offeror, results in a binding contract. The Government will mail or otherwise furnish to the offeror an award or notice of award not later than the day award is dated. Therefore, the offeror should compute the time available for performance beginning with the actual date of award, rather than the date the written notice of award is received from the

Contracting Officer through the ordinary mails. However, the Government will evaluate an offer that proposes delivery based on the

Contractor's date of receipt of the contract or notice of award by adding (1) five calendar days for delivery of the award through the ordinary mails, or (2) one working day if the solicitation states that the contract or notice of award will be transmitted electronically. (The term "working day" excludes weekends and U.S. Federal holidays.) If, as so computed, the offered delivery date is later than the required delivery date, the offer will be considered nonresponsive and rejected.

F.1.4, Only upon approval from Contracting Officer, an accelerated delivery schedule may be acceptable at no additional cost to the

14 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Government.

F.2. LONG TERM CONTRACTS - FOB DESTINATION

For the purpose of offerors compiling FOB Destination offers, the final destination for the supplies will be one or more of the following destinations; in the following estimated percentages, if listed: 50% DDSP New Cumberland Facility (AN5 Plant 7002), 25%

DefRiver Pkant 7001), & 25% XU Def Dist Depot San Joaquin (AQ5 Plant 7011).

*** END OF NARRATIVE F0001 ***

15 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION G - CONTRACT ADMINISTRATION DATA

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

G-1 CHANGED 252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (JAN 2023) JAN/2023

(a) Definitions. As used in this clause

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

"Payment request" and "receiving report" are defined in the clause at 252.232-7003, Electronic Submission of Payment Requests and

Receiving Reports.

(b) Electronic invoicing. The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232-7003, Electronic Submission of Payment Requests and

Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.sam.gov ; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice

Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the

WAWF home page at https://wawf.eb.mil/

(e) WAWF methods of document submission. Document submissions may be via web entry, Electronic Data Interchange, or File Transfer

Protocol.

(f) WAWF payment instructions. The Contractor shall use the following information when submitting payment requests and receiving reports in WAWF for this contract or task or delivery order:

(1)Document type. The Contractor shall submit payment requests using the following document type(s):

(i) For cost-type line items, including labor-hour or time-and-materials, submit a cost voucher.

(ii) For fixed price line items

(A) That require shipment of a deliverable, submit the invoice and receiving report specified by the Contracting Officer.

-Combo-

(Contracting Officer: Insert applicable invoice and receiving report document type(s) for fixed price line items that require shipment of a deliverable.)

(B) For services that do not require shipment of a deliverable, submit either the Invoice 2in1, which meets the requirements for the invoice and receiving report, or the applicable invoice and receiving report, as specified by the Contracting Officer.

-Combo-

(Contracting Officer: Insert either "Invoice 2in1" or the applicable invoice and receiving report document type(s) for fixed price line items for services.)

(iii) For customary progress payments based on costs incurred, submit a progress payment request.

(iv)For performance based payments, submit a performance based payment request.

16 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(v) For commercial financing submit a commercial financing request.

(2) Fast Pay requests are only permitted when Federal Acquisition Regulation (FAR) 52.213-1 is included in the contract.

[Note: The Contractor may use a WAWF "combo" document type to create some combinations of invoice and receiving report in one step.]

(3)Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in

WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC TBD

Issue By DoDAAC W912CH

Admin DoDAAC TBD

Inspect By DoDAAC TBD

Ship To Code SEE SCHEDULE

Ship From Code SEE SCHEDULE

Mark For Code N/A

Service Approver (DoDAAC) N/A

Service Acceptor (DoDAAC) N/A

Accept at Other DoDAAC N/A

LPO DoDAAC N/A

DCAA Auditor DoDAAC N/A

Other DoDAAC(s) N/A

(*Contracting Officer: Insert applicable DoDAAC information. If multiple ship to/acceptance locations apply, insert "See Schedule" or

"Not applicable.")

(**Contracting Officer: If the contract provides for progress payments or performance-based payments, insert the DoDAAC for the contract administration office assigned the functions under FAR 42.302(a)(13).)

(4)Payment request.The Contractor shall ensure a payment request includes documentation appropriate to the type of payment request in accordance with the payment clause, contract financing clause, or Federal Acquisition Regulation 52.216-7, Allowable Cost and Payment, as applicable.

(5)Receiving report. The Contractor shall ensure a receiving report meets the requirements of DFARS Appendix F.

(g)WAWF point of contact.

(1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

N/A

(Contracting Officer: Insert applicable information or "Not applicable.")

(2) Contact the WAWF helpdesk at 866-618-5988, if assistance is needed.

(End of clause)

17 21

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1. GENERAL BID INFORMATION

(a) Overview. Bidders are responsible for submitting a well-written bid, with adequately detailed information, that clearly demonstrates an understanding of and the ability to comply with the IFB requirements to allow for a meaningful evaluation. The Bidder's submission, as required by this section, will be evaluated as set forth in Section M. Bidders are expected to examine the drawings, specifications, Schedule, and all associated instructions in preparing their bid, pursuant to RFO FAR 52.214-12: Preparation of Bids. All information necessary for the review and evaluation of a bid is to be contained within the bid. The Government will not assume the Bidder possesses any capability, understanding, or commitment not specified by its bid, nor does the Government assume the duty to search for data to cure problems it finds in a bid.

(b) Technical Data. There is a Technical Data Package (TDP) associated with this procurement. The TDP is distribution code "A"-

Approved for Public Release. Distribution is Unlimited. Please see Section C.1. TDP Information for instructions on how to access this data.

(c) Minimum Acceptance Period.

(1) "Acceptance period" means the number of calendar days available to the Government for awarding a contract from the date specified in this IFB for receipt of bids. The minimum acceptance period identified in FAR 52.214-16: Minimum Bid Acceptance Period supersedes any language pertaining to the acceptance period that may appear elsewhere in this IFB.

(2) The Government requires a minimum acceptance period of 90 calendar days. Bidders may specify a longer acceptance period via the

RFO FAR 52.214-16 fill-in. However, a bid allowing less than the Government's minimum acceptance period will be rejected.

L.2. BID CONTENT AND FORMAT

(a) Language and Currency. All bids shall be submitted in English (American Standard) pursuant to RFO FAR 52.214-34: Submission of

Offers in the English Language and in U.S. dollars pursuant to FAR 52.214-35: Submission of Offers in U.S. Currency. Bids not in English

(American Standard) or in U.S. dollars will be rejected.

(b) Completeness and Fill-ins. Bids shall include all information specified and shall address all requirements identified in Section L.