W91CRB-26-R-5013 Amd 001_18AUG2026.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

W91CRB

ACC-APG - DIVISION D (W91CRB)

6515 INTEGRITY COURT

APG, MD 21005-3013

NAOMI CROSS

EMAIL: NAOMI.CROSS2.CIV@ARMY.MIL

W91CRB-26-R-5013

2026AUG14

X

X 2026AUG28 10:00am

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 6

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: NAOMI CROSS

Buyer Office Symbol/Telephone Number: CCAP-MDD/(520)671-1812

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. The purpose of this solicitation amendment is to revise the previous Performance Work Statement (PWS), Requirements Traceability

Matrix (RTM), Price Summary Workbook, and add the Draft DD254 within Section J (Attachments). Additionally, this solicitation amendment addresses the following Questions from Industry:

Question from Industry 1:

Confining the Requirements Traceability Matrix (RTM) to a YES/NO response, without comment or caveats puts the contractor in a challenging position. Some requirements are not clearly defined, open ended, or not applicable against certain deliverables. Responding

YES places a potential contractual obligation on the contractor that might not be achievable. In some cases, the definition of the requirement have been discussed and clarified, either verbally or through a comments matrix, but the requirements remain in the PWS because the LOR could not be modified. Recommend allowing a comments section next to each requirement where the contractor can state

YES, and bound the scope of the YES (COTS / NDI item or top-level only for example).

Government Response:

Requirements Traceability Matrix (RTM) checks can be accompanied by explanatory comments, where appropriate. This requirement is Lowest

Price Technically Acceptable (LPTA), so offerors are reminded that all non-cost factors will be evaluated as acceptable/unacceptable.

Question from Industry 2:

Stating YES under a FAR 15 contract potentially legally binds the contractor to pursue M-Code integration which might not be possible.

In addition, the upgrade of a NSA controlled device could constitute a new radio configuration and certification. Finally, the statement that "the upgrade is included in the price or be identified as a future cost and included in the price proposal". Where is this to be included in the price proposal and will it be an evaluated price as a portion of the TEP? What is the objective basis for technology maturity? Including this price in the cost of the radio does not seem to be in the customer's best interest for a technology upgrade that may never come to fruition.

Government Response:

The Government has removed this requirement from PWS and RTM. See revised PWS and RTM dated 13 August 2026. A formal contract modification will be necessary if the Customer requires M-Code rather than SAASM GPS.

Question from Industry 3:

We note that the UHF SATCOM vehicular antenna requirements include several parameters that exceed COTS/MOTS industry specifications. To help the Purchaser receive the widest range of competitive COTS/MOTS offerings, could the Government confirm whether all listed antenna parameters are mandatory and met simultaneously, or if functional compliance with UHF SATCOM performance is the key requirement? Several specifications appear product-specific rather than performance-based, and clarification would allow offerors to propose viable commercial solutions rather than custom development. A recent requirement modification included "ground plane antennas not acceptable", however in our research all antennas which met the gain requirements required a ground plane based antenna design (either internal or external to the antenna).

If there is a specific COTS product preferred by the Purchases, we would prefer that the PWS just lists a directed source as the requirement.

Government Response:

All listed UHF SATCOM vehicular antenna parameters are mandatory and are to be met.

Question from Industry 4:

IPS-9 calls out documentation/repair within NSA/COMSEC limits, but IPS-37 makes broad requirements of drawings, components, assemblies.

Government Response:

Maintenance documents shall be restricted only to that level necessary to permit the customer to maintain hardware and software within the limits of NSA and proprietary constraints. See revised PWS and RTM requirements under IPS-9, IPS-20, IPS-37, and IPS-46 dated 13

August 2026.

2 6

W91CRB-26-R-5013

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Question from Industry 5: If an additional warranty option is activated, will this be a new contract or modification? Warranties are not priced separately in the current format and there is not a line item for option pricing.

Government Response:

If additional warranty option is required by Customer, the action will be executed via bilateral modification to the contract. See revised PWS and RTM dated 13 August 2026 that makes changes to IPS-81 and IPS-82 optional warranty text.

Question from Industry 6: This RFP is procuring COTS/NDI items. Confirming the configuration management scope is bound to the top-level system configuration.

Government Response:

The RFP calls for COTS/NDI radio systems. For the AM3T radio, the CM scope is bound to the top-level system configuration. However, each configured hardware suite (i.e. AM3T Kit, OTP, OTM, Deployable HQ) will be packaged within a case containing shock mounted COTS/NDI components. The design/layout and installation of those components within each configuration is subject to lower-level CM documentation.

Question from Industry 7: The requirement references providing CM content during the proposal phase, but the proposal instructions do not allow for any additional documents. Is this assumed to be covered by the pre-RFP engagements? There are a few other instances of this throughout the PWS.

Government Response:

Requirements for proposal language covering such areas should be brief top-level content descriptions that can be included in appropriate sections of the technical proposal.

Question from Industry 8: This procurement is for COTS/NDI items. Configuration management and baseline will be established by a single document identifying the components so a data base is not needed. The purchaser would not have access to any internal configuration management system of a CCI radio system.

Government Response:

Requirements for proposal language covering such areas should be brief top-level content descriptions that can be included in appropriate sections of the technical proposal.

Question from Industry 9: Configuration audits (FCA / PCA) if desired are only at the Top Level system configuration based on COTS/NDI items.

Government Response:

Requirements for proposal language covering such areas should be brief top-level content descriptions that can be included in appropriate sections of the technical proposal.

Question from Industry 10: This procurement is for a system of COTS/NDI items. ECPs internal to the individual items cannot be controlled by the purchaser, especially on the radio. ECPs will only address revisions to the top level components or substitutions.

Government Response:

Requirements for proposal language covering such areas should be brief top-level content descriptions that can be included in appropriate sections of the technical proposal.

Question from Industry 11: The product baseline is a single document for each "kit" at the top level item only.

Government Response:

If "kit" means "each configuration" then the top-level item is the configured AM3T, OTP, OTM, and Deployable HQ suite. Components within the case fit this description, but not the case, racking, arrangement, and installation of components within.

Question from Industry 12: G26 in Section B CLINS template = SUM(G22 : G24). Should be =SUM(G22 : G25). CLIN 16 is currently excluded from the Total Evaluated Price.

Government Response:

3 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Price Summary Workbook calculations have been corrected and can be found on the revised Price Summary Workbook from 14 AUG 2026.

Question from Industry 13: Appendix A table page 19 requires 2 OCONUS Radio Operator Training with no OCONUS maintenance training, while

CLIN 16 and Section 3.2.4 require OCONUS maintenance training.

Government Response:

See revised PWS dated 13 Aug 26, Appendix A- Table is modified to reflect PWS Section 3.2.4 requirement.

Question from Industry 14: Specifies Quarterly In-Progress Reviews to be held in-person at US Government facilities. Confirm this is a

CONUS US Government location and not a OCONUS NATO location.

Government Response:

Quarterly IPRs are CONUS.

Question from Industry 15: Requesting confirmation that the procurement value reflects the amount notified to Congress in 2021, an amended LOA value, or the government has established a maximum acceptable price. Is there an economic price adjustment clause?

Government Response:

The Government has an established dollar amount that can be accepted for this requirement that is based on the LOA amount/s approved for the associated lines. DFARS Clause 252.243-7002, Requests for Equitable Adjustment is included in the solicitation see Section I

Question from Industry 16: The PWS deliverables call out batches by 4 types of kit configurations, but most items are delivered packaged separately according to the requirement descriptions. Is the IUID value classification requirement only at the individual item level

(i.e. the radio, integrated mounting assembly, etc...).

Government Response:

IUID value classification refers to each component within the 4 types of configurations.

Question from Industry 17: This requirement references post warranty support. The way this reads, pricing and scope will be negotiated at a future date. Just confirming the interpretation.

Government Response:

If additional warranty option is required by Customer, the action will be executed via bilateral modification to the contract. See revised PWS and RTM dated 13 August 2026 that makes changes to IPS-81 and IPS-82 optional warranty text.

Question from Industry 18: IPS requires 3 operator trainings. Section 3.2 of the Price Summary provides 2 Operator Training price locations. Please confirm which is correct.

Government Response:

Requirement is for 1 CONUS and 1 OCONUS operator training sessions. PWS paragraph 3.2.3 is corrected.

Question from Industry 19: Will a separate DD254 be generated based on this contract award?

Government Response:

Yes, a draft DD254 is required and is added under Section J of the solicitation

2. The solicitation close date is extended to 10:00am EST on 28 AUG 2026.

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

4 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0002 ***

5 6

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Attachment 0001 K4-B-VAA_PWS_13AUG2026 13-AUG-2026 076 EMAIL

Attachment 0002 PRICE SUMMARY WORKBOOK_14AUG2026 14-AUG-2026 001 EMAIL

Attachment 0003 RTM_K4-B-VAA_FINAL_13AUG2026 13-AUG-2026 001 EMAIL

Attachment 0004 DD254_13AUG2026 13-AUG-2026 005 EMAIL

6 6