AMENDMENT OF SOLICITATION / REQUEST FOR QUOTE (RFQ)

Solicitation Number: PANROC-26-P-0000-031130

Amendment Number: 0002

Effective Date: August 11, 2026

Issued By: Department of the Army, Contracting Office

Project Title: Multi-Functional Device (MFD) Fleet & Management Services

PART I: PURPOSE AND SUMMARY OF AMENDMENT

The purpose of this amendment is to revise the Request for Quotations (RFQ) to provide definitive instructions, update submission requirements, and clarify the evaluation framework.

Specifically, this amendment:

Formally establishes a mandatory Excel-based Technical Compliance Workbook which must be completed and submitted with all quotations.

Establishes a comprehensive Instructions to Quoters section and Evaluation Factors for Award section.

PART II: INSTRUCTIONS TO QUOTERS

1. General Submission Requirements Quoters must submit their quotations in three (3) separate volumes as outlined below. Failure to submit all volumes, or failure to follow the formatting instructions, may result in the quote being rejected as non-responsive.

Volume I: Administrative and Completed Technical Compliance Workbook (Excel)

Volume II: Technical Narrative Proposal (Word/PDF)

Volume III: Price

2. Volume I: Technical Compliance Workbook Instructions Quoters are required to fill out and submit the government-provided Excel file titled "Attachment 0002 - Technical Compliance Workbook".

For each line item in the workbook, the Quoter must fill in the following columns:

(i) Vendor Answer: Must state "Yes" or "No" indicating compliance.

(ii) Evidence Support Document: Input the exact file name, page, section, paragraph, and line number within your Volume II Technical Narrative or supporting artifacts (e.g., product data sheets) where compliance with the requirement is proven.

(iii) Additional Vendor Narrative: Provide a concise, clear description of how the proposed solution meets the requirement. Do not copy and paste the requirement text.

Note: Leaving any line item blank, answering "No," or failing to provide traceable evidence will result in an "Unacceptable" technical rating.

3. Volume II: Technical Narrative Proposal Instructions Quoters shall provide a comprehensive Technical Narrative Proposal that details their technical capabilities and demonstrates their ability to satisfy the requirements of the Performance Work Statement (PWS).

A. Substantiation of Technical Claims The Technical Narrative Proposal must not rely on unsupported assertions or generalized marketing materials. Quoters are responsible for providing sufficient technical information and evidence to permit the Government to independently evaluate and validate compliance.

Quoters must provide supporting technical artifacts, which may include, but are not limited to:

Product data sheets and specifications Security technical guides and administrator guides Installation, configuration, and deployment guides Authentication, CAC, and directory integration documentation Architecture and data flow diagrams (showing data transit, encryption, and ports) Service Level Agreement (SLA) plans and Quality Control Plans (QCP) Media sanitization and disk overwrite procedures (conforming to NIST SP 800-88) Scalability and disaster recovery/restore documentation Any response that defers validation of core capabilities to post-award activities (e.g., "to be determined after award" or "will assess during implementation") will be deemed to contain insufficient information and will be evaluated as Technically Unacceptable.

4. Volume III: Price Contractors are required to submit all pricing information in Attachment 0003 – Price Matrix. All cells must be filled in.

PART III: EVALUATION FACTORS FOR AWARD

1. Basis for Award The Government will award a contract resulting from this solicitation to the responsible Quoter whose quote conforms to the solicitation requirements and represents the Lowest Priced Technically Acceptable (LPTA) quotation.

The evaluation will consist of three parts:

(A) Completeness and Compliance Review (Section 1 of the Workbook)

(B) Technical Acceptability Evaluation (Sections 2 through 5 of the Workbook)

(C) Price Reasonableness Evaluation

2. Technical Evaluation Methodology Technical quotes will be evaluated on an Acceptable / Unacceptable basis.

3. Step-by-Step Evaluation Framework Note: The Government will begin evaluations starting with the lowest proposed priced quotation. Not all quotations may end up being evaluated. For example, if the initial lowest proposed price quotation is deemed technically acceptable, the Government may stop the evaluation process and make award consistent with LPTA principles. The Government may also evaluate further quotations in its discretion to establish price reasonableness.

(A)Section 1 - Proposal Completeness, Evidence, and Documentation The Government will perform an initial administrative and compliance gateway review.

Government Intent: The Government will assess whether the Offeror provides a complete, evaluable proposal package. The proposal should clearly answer each applicable requirement, disclose assumptions and limitations, identify native versus third-party capabilities, identify licensing or dependency impacts, and provide sufficient supporting documentation.

Evaluation Standard: This is a pass/fail compliance gateway. If a Quoter fails to submit a complete Technical Compliance Workbook, fails to provide an explicit statement for each requirement, fails to identify native/third-party licenses, or fails to provide sufficient supporting documentation for the Government to independently evaluate and validate compliance, the proposal will be rated Unacceptable and will not be evaluated further. Unsupported assertions or responses that defer core capability validation to post-award activities may be determined insufficient for technical evaluation.

(B) Technical Requirements (Sections 2 - 5) The technical evaluation team will verify the accuracy of the Quoter's claims in each row of the workbook against the provided Technical Narrative and supporting technical artifacts. The following provides an overview of the Sections containing row items to be evaluated in the Workbook:

Section 2 - PWS Table 3 Technical Requirements: The Government will assess whether the proposed devices, software, accessories, services, and management capabilities satisfy each technical requirement. This evaluation preserves requirement-by-requirement traceability for core functions (print, scan, copy, security, authentication, and client compatibility).

Section 3 - Contractor Support, Service Delivery, and Contract Administration: The Government will assess the Quoter's ability to deliver, install, support, maintain, relocate, remove, repair, and administer the MFD fleet throughout the life of the contract.

Section 4 - Enterprise Architecture, Management, Scalability, and Operational Risk: The Government will assess the technical ability of the proposed solution to support enterprise management across WREN, NIPRNET/Garrison, and MEDCOM/KACH environments. The evaluation will consider management architecture, centralized administration, Azure SQL Managed Instance compatibility, data flows, and software lifecycles.

Section 5 - Environment-Specific Technical Capability: The Government will independently assess the proposed solution's ability to operate within each specific environment (WREN, NIPRNET/Garrison, and MEDCOM/KACH). Demonstrated functionality in one environment will not be presumed to demonstrate functionality in another unless expressly supported by the proposal and technical documentation.

(C) Price Reasonableness Evaluation The Government will evaluate the Price of the lowest priced technically acceptable quotation using Attachment 0003 – Price Matrix for price reasonableness.

LPTA Order: The contract will be awarded to the technically acceptable Quoter offering the lowest evaluated price, subject to a determination of price reasonableness.

4. Government Use of External Information Reservation of Rights: The Government reserves the right to consider information not explicitly contained in a vendor's quotation when conducting its evaluation. This includes, but is not limited to, knowledge/experience of the evaluation team, and other publicly available or government-held information regarding the vendor's capabilities and proposed technical systems.