Attachment 2 _ 52.212-1 Instructions to Offerors—Commercial Products and Commercial Services_9.18.2026.docx

52.212-1 Instructions to Offerors—Commercial Products and Commercial Services.

1. As prescribed in 12.301(b)(1), insert the following provision:

Instructions to Offerors—Commercial Products and Commercial Services (Sep 2023)

As a minimum, offers must show—

(1) The solicitation number;

(2) The time specified in the solicitation for receipt of offers;

(3) The name, address, and telephone number of the Offeror;

(4) A technical description of the items/services being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary;

(5) Terms of any express warranty;

(6) Price and any discount terms;

(7) "Remit to" address, if different than mailing address;

(8) Initial, Phase I, proposals must include:

i. Volume 1 – Factor 1 - Subfactor 1.a – Agile Implementation Plan

ii. Volume 1 – Factor 1 - Subfactor 1.b – Key Personnel

iii. Volume 1 – Factor 1 - Subfactor 1.c – Cybersecurity Compliance Gate

iv. Volume 2 - Factor 2 - OCI Mitigation Plan

v. Volume 4 – Administration

i. Cover Letter

ii. NAICS Size Standard Certification

Phase I - Instructions VOLUME 1: FACTOR 1 – Technical – Instructions Volume 1 contains the technical capabilities, workforce management strategies, and cybersecurity compliance necessary to execute the Agile Professional Services contract.

i. Subfactor 1.a – Agile Implementation Plan (15 Pages Max) The Offeror shall provide a detailed, actionable Agile Implementation Plan (not to exceed 15 pages) describing their operational approach to executing Agile Professional Services across the CPE ST3 enterprise. To demonstrate an executable baseline, the plan must clearly address all of the following:

1. Cultural Change Management Strategy:

· Detail proposed actionable methods for migrating the contractor's workforce to a cross-functional mindset.

· Explicitly outline the approach for driving cultural adoption and securing compliance from Government team members.

2. Dynamic Resource Allocation Mechanics:

· Detail clear operational triggers, workflows, and triage mechanics for reallocating cross-functional teams to meet emergent, high-priority demands across all ST3 program offices and directorates.

3. Backlog Prioritization and Sizing Strategy:

· Explicitly detail the repeatable strategy and methodology for collaborating with Government Product Owners to assign priority weights (and Level of Effort (LOE) estimates (to incoming backlog tasks to ensure transparent planning and optimal capacity utilization.

4. Manpower Resource Efficiency:

· Describe specific strategies to eliminate resource idling ("bench time") and leverage multi-skilled professionals to maximize capacity pool productivity.

· Clearly articulate how this efficiency strategies translate into a tangible, measurable benefit to the Government.

5. Commercial Business Model Application:

· Provide a practical translation of commercial practices into a compliant Government operational model.

ii. Subfactor 1.b – Key Personnel (Agile Program Manager - 3 Pages Max) The Offeror shall propose a qualified individual to serve as the Agile Program Manager (APM) to lead the overall contract effort, manage the capacity pool, and interface with Government leadership. The Offeror shall submit a resume (not to exceed 3 pages) demonstrating that the proposed APM meets or exceeds the following minimum qualifications:

1. Experience:

· Minimum of five (5) years of demonstrated program management experience leading Agile teams or managing cross-functional, capacity-based professional services contracts in either a federal or commercial environment, with at least three (3) of those years occurring within the past five (5) years.

· The resume must demonstrate experience scaling Agile practices across multiple teams while maintaining alignment with strategic goals.

2. Certifications:

· Must possess a current, recognized advanced Agile-specific credential.

3. Technical Competency:

· Proven, hands-on experience utilizing enterprise Agile management tools (Jira at a minimum) to track capacity, manage backlog workflows, forecast delivery velocity, and generate flow metrics and dashboards.

· The resume must demonstrate the specific metrics the proposed APM has historically used and how they used those metrics to pivot a failing project or improve team performance.

4. Security Clearance:

· Must be eligible for up to a Top Secret/SCI security clearance.

iii. Subfactor 1.c – Cybersecurity Compliance Gate (SPRS 110 Score) Prerequisite for Government Controlled Unclassified Information (CUI) Data Release: The Offeror shall submit a one-page Compliance Statement before the Offeror may can receive Government data to participate in Phase II. The Government will verify the Offeror’s cybersecurity compliance rating in SPRS.

1. 110-Score Requirement: The Offeror must provide documentation/CAGE code confirming an active, self-certified NIST SP 800-171 Revision 2 assessment score of 110 (indicating full implementation of all 110 security controls) active and posted in the DoD Supplier Performance Risk System (SPRS) as of the Phase II entry date.

2. Flow-Down Mandate: This 110-Score requirement applies to the Prime Offeror, and all proposed subcontractors, teaming partners, or affiliates who will have access to Government-provided data or participate in contract performance.

3. Notice of Non-Compliance: Failure to possess a verified score of 110 in SPRS on the date of submission will result in an immediate "Non-Compliant" determination, and the Offeror will be ineligible to receive data to participate. Proposals deemed non-compliant at this stage will be rejected in their entirety, as further evaluation is not possible.

VOLUME 2: FACTOR 2 – OCI MITIGATION PLAN - Instructions

i. Factor 2 – Organizational Conflict of Interest (OCI) Mitigation Plan (10 Pages Max) All individual offerors, members in teaming arrangements, and partners in joint ventures shall submit a comprehensive, written OCI Mitigation Plan that completely identifies any potential or actual OCIs associated with the performance of this requirement and proposes mitigation strategies that avoid, neutralize, or mitigate those conflicts in accordance with FAR Subpart 9.5.

The plan must specifically address and provide comprehensive mitigation strategies for the following three (3) OCI categories:

1. Unequal Access to Information: Occurs when a contractor has access to non-public, sensitive, or proprietary information as part of its performance of a Government contract, and that information provides the contractor with an unfair competitive advantage in a later competition.

2. Biased Ground Rules: Occurs when a contractor, in the course of performance, drafts or influences specifications, Statements of Objectives (SOOs), Statements of Work (SOWs), Program Objective Memorandum (POM) or acquisition plans for a future procurement, thereby biasing the competition in favor of its own capabilities, tools, or those of an affiliate.

3. Impaired Objectivity: Occurs when a contractor’s work under one Government contract requires it to evaluate its own products, services, or performance (or those of a competitor, teammate, or affiliate) on another Government contract, thereby impairing its ability to render impartial, objective advice.

VOLUME 4: ADMINISTRATION - Instructions

i. Section 1: Cover Letter The Offeror shall submit a formal corporate Cover Letter signed by an authorized corporate official, including (3 Pages Max):

1. Corporate Identification: Company Name, CAGE Code, UEI, and primary/alternate POCs.

2. Facility Security Clearance (FCL) Verification: Formal statement confirming that the Prime Contractor possesses an active Top Secret Facility Clearance (FCL) issued by DCSA, with personnel eligible up to TS/SCI.

3. Phase II In-Person Attendees: Identification of up to five (5) participants proposed to attend the in-person Phase II session in Orlando, FL (including full name, company name, position, and email). All proposed participants must be US Citizens. The proposed Agile Program Manager (APM) must be designated as the primary lead.

ii. Section 2: NAICS Size Standard Certification

1. NAICS Certification: Formal certification confirming business size status under the assigned NAICS code (541990).

2. SAM.gov Representations & Certifications: Confirmation that the Offeror's SAM.gov profile is current, active, and fully compliant as of the proposal due date.

3. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration Phase II – Proposals - must include:

Volume 1 – Subfactor 1.d – Technical Demonstration and Agile Scenario – Oral Presentation Slides and Visit Authorization Request (VAR) via the Defense Information System for Security (DISS) to the Government Security Point of Contact (POC) annotated in Phase II Advisory Notification / Invitation Letter Volume 1 – Subfactor 1.e - Talent Pool Composition and Cross-Functional Governance (must be addressed in JIRA Technical Demonstration)

Phase II - Technical Demonstration and Agile Scenario (Live Orals) – Instructions Only Offerors who successfully pass all Phase I gates (including the NIST SP 800-171 Rev 2 Cybersecurity Compliance Gate) will be recommended to participate in Phase II.

· Format & Scheduling: All oral presentations and technical demonstrations will be performed in person at a Government facility located in the Research Park area of Orlando, FL. The Procuring Contracting Officer (PCO) will determine the order in which the Offerors will present. The PCO will notify Offerors of the scheduled date and precise location of their presentation via email no less than seven (7) days before the required presentation date. The Government reserves the right to reschedule any presentation at the discretion of the PCO.

· Presentation Slides Submission: The Offerors shall email their final PowerPoint presentations (Part 1 and Part 2) to the PCO no later than 48 hours prior to the beginning of first scheduled presentation. No modifications to the slides will be permitted after this submission.

· Costs: The Government is not responsible for, nor will the Government pay any portion of the costs associated with Offerors’ personnel attendance for the oral presentations.

· Time Limit: The total session shall not exceed 60 minutes not to include Government introduction timeline requirements, and transition time from Part 1 to Part 2. The Government will keep the official time and will maintain a hard stop; any content presented or actions taken after the 60-minute mark will not be evaluated.

· Facility Access & Security: There is no security clearance requirement for participation in Phase II or for access to the designated Research Park facility, however all participants must be US citizens. To facilitate unclassified building access, the Offeror shall submit a formal Visit Authorization Request (VAR) via the Defense Information System for Security (DISS) to the Government Security Point of Contact (POC) (SMO Code and POC to be provided in the Phase II notification letter) by the Phase II submission due date. All proposed personnel must present a valid, government-issued photo identification (upon arrival.

· Attendees: The Offeror is limited to a maximum of five (5) participants. Identification of all attendees, along with the company name, position, and confirmed DISS VAR status shall be identified to the Government points of contact (POCs) via email by the Phase II submission due date. The proposed Agile Program Manager (APM) (identified in Phase I) should be the primary lead for the session.

· Equipment: The Government will provide the computer for Part 1. The Offeror is responsible for bringing the necessary laptop(s) and internet connectivity required to conduct Part 2. The Government will provide a projector/monitor with standard HDMI/display connections for both Part 1 and Part 2.

Recording: All oral presentations will be recorded for Government use during the solicitation evaluation. Offerors are strictly prohibited from recording the session.

PRE-DEMONSTRATION ACTIVITIES (ENVIRONMENT SETUP) (Subfactor 1.d)

· Step 1: Verification of Score & Release of Government Data: In accordance with Phase I Subfactor 1.c – Cybersecurity Compliance Gate, the Government will first verify that the Offeror possesses an active NIST SP 800-171 Revision 2 assessment score of 110 in the DoW Supplier Performance Risk System (SPRS). An Offeror who has not met this requirement will be considered "Non-Compliant". The Government will release the sample JIRA data to support Phase 2 only if the Offeror meets the assessment score criteria for Phase I Subfactor 1.c.

· Step 2: Contractor Configuration: The Offeror shall stand up and configure a contractor-provided Jira instance using the provided specifications and shall import the Government provided data to create a baseline sprint environment.

· Step 3: Mandatory Verification Session: Prior to the oral presentation, the Government will conduct a mandatory Jira verification session with each Offeror to confirm environment compliance. Offerors whose configuration specifications do not match those provided by the Government will be determined “Non-Compliant”, but the Offeror may choose to participate further in the competition at their own discretion.

THE 60-MINUTE AGENDA & SUBFACTOR MAPPING (Subfactor 1.d) The oral presentation is broken into 2 distinct parts: Part 1 - the Oral Presentation, Part 2 - Jira Environment Technical Demonstration. The Offeror must strictly adhere to the following steps and address the mapped evaluation criteria:

Part 1: The Oral Presentation (First 30 Minutes) Verification and Validation of Implementation and Alignment with Subfactor 1.a – Agile Implementation Plan (Establishing the conceptual and operational baseline to be executed live under Subfactor 1.d in Part 3) Instructions: The Offeror shall provide a 20-page (maximum) PowerPoint presentation and shall present that information during the first 30 minutes of the oral presentation. The Offeror must clearly and comprehensively address the following elements:

1. Resource Allocation & Dispersed Support (Subfactor 1.a / 1.d): The Offeror shall detail a strategy for providing appropriate and sufficient capacity to meet the requirements of the Government’s SOO and Offeror’s proposed PWS. The contractor shall explicitly address an approach for resourcing geographically dispersed sites to ensure uninterrupted, synchronized mission support.

2. Workforce Management & Backfill Speed (Subfactor 1.a / 1.d): The Offeror shall demonstrate their plan to recruit and manage a qualified, large, and geographically dispersed workforce, detailing the exact procedural pipeline to backfill vacant positions as expeditiously as possible to prevent degradation of sprint velocity and mission support.

3. Retention & Turnover Mitigation (Subfactor 1.a / 1.b): The Offeror shall describe its strategies and incentives it will use to retain employees and reduce turnover. Furthermore, the Offeror shall detail the specific consideration and/or corporate mechanisms it will offer to protect the Government's investment and ensure requirements are met if specialized personnel depart.

4. Corporate Training Investment Protection (Subfactor 1.a / 1.e): The Offeror shall detail its approach for providing corporate-funded, domain‑specific training to ensure employees remain highly skilled assets and shall explicitly demonstrate that all such training will be company-funded and not constitute a responsibility or expense of the Government.

5. Cultural Change Management Strategy (Subfactor 1.a / 1.d): The Offeror shall detail proposed, actionable methods for migrating the Offeror’s workforce to a cross-functional operating mindset. The Offeror’s strategy shall explicitly outline the approach for driving cultural adoption and securing compliance from Government team members.

6. Operations & Multi-Level Interactions (Subfactor 1.a / 1.d): The Offeror shall describe the concrete approach for conducting daily APS operations following transition closeout. The Offeror shall detail the specific processes, task assignments, and communication flows across Organizational, Project, Product, and Team levels that will enable responsive and effective execution.

Part 2: Jira Environment Technical Demonstration (Final 30 Minutes) Verification and Validation of Implementation and Alignment with Subfactor 1.d – Technical Demonstration and Agile Scenario & Subfactor 1.e – Talent Pool Composition and Cross-Functional Governance Instructions: The Offeror shall demonstrate the contractor-provided Jira environment during the final 30 minutes of the oral presentation. Through active use and live navigation of its Jira environment, the Offeror must demonstrate and describe the following:

1. Cross-Functional Governance & Tool Utilization (Subfactor 1.e): The Offeror shall present the company’s "Talent Pool Composition and Cross-Functional Governance" approach in any format appropriate to the Offeror’s business practices. Under Subfactor 1.e, the Offeror shall demonstrate the manner in which it utilizes the contractor-provided Jira environment (live tool/system) to actively manage cross-functional resources and track talent capabilities in real time, validating the methodology proposed in the Phase I Submission.

2. Multi-Level Dashboards & Metrics (Subfactor 1.d): The Offeror shall demonstrate its approach for utilizing the Jira environment to organize data, visualize workflow, and clearly communicate status via informative dashboards configured for the CPE, PM/PL, and PdM/PdL levels.

3. Agile Implementation Approaches (Subfactor 1.d): Based on the analysis of the Government provided data, the Offeror shall present the top three approaches for improving the effectiveness of the APS requirements and shall demonstrate how each recommended change would be implemented in Jira.

4. Live Scenario & Change Management (Subfactor 1.d & 1.e): During the live scenario, the Government will present scenario injects requiring the Offeror to conduct real‑time triage of multiple operational changes. The Offeror shall demonstrate its capability to maintain continuity of operations and apply agile change‑management practices to ensure uninterrupted contractual performance. The Offeror shall respond to each scenario injects in real time and demonstrate its approach in one or more of the following areas:

· Entering, sizing, and triaging requirements generated by the scenario inject.

· Reprioritizing the backlog and adjusting sprint or workflow plans.

· Orchestrating technical and functional resources.

· Executing effective HR actions, including access management, onboarding/offboarding, and labor resource reassignment.

· Demonstrating compliance with labor category qualification and hiring requirements.

· Describing and demonstrating continuity‑of‑operations measures.

· Explaining and demonstrating how uninterrupted performance is maintained through communication protocols, risk mitigation, technical remediation, and workflow stabilization.

Phase III – Proposals - must include:

Subfactor 1.f - Proposed Performance Work Statement (PWS), applicable (Contract Data Requirements List) CDRLs, QASP, and Compliance Matrix Subfactor 1.g – Transition Plan Factor 3 - Final Proposed Price, and any discount terms.

Volume 4 – Administration Volume

a. NAICS Size Standard Re-Certification

b. Amendment Acknowledgments

c. Teaming Agreements (If Applicable)

d. Representations and Certifications to include Data Rights Certifications

Subfactor 1.f - Proposed Performance Work Statement (PWS), CDRLs and QASP

PERFORMANCE WORK STATEMENT (PWS) INSTRUCTIONS

The Offeror shall author and submit a binding, contractor-developed Performance Work Statement (PWS) that translates the Government’s requirements into a single, comprehensive, and enforceable contract document. The PWS shall be organized using the Government-provided PWS Template and must incorporate all tasks, plans, approaches, and commitments detailed in the following three source documents:

1. The Government's Statement of Objectives (SOO): The PWS must convert every performance objective, desired end-state, and operating constraint from all sections of the SOO into measurable, enforceable contractual requirements and deliverables (CDRLs).

2. The Offeror’s Phase I Agile Implementation Plan: The PWS must integrate and codify all tasks, plans, and approaches detailed in the Offeror’s written Phase I submission, transforming the proposed methodology into binding contractual commitments.

3. The Offeror’s Phase II Oral Presentation: The PWS must incorporate all tasks, plans, and approaches detailed in the Offeror’s Phase II Oral Presentation slides, ensuring that all verbal commitments are formalized as unambiguous, enforceable contractual requirements.

QASP INSTRUCTIONS

The Offeror shall submit a comprehensive Quality Assurance Surveillance Plan (QASP) detailing the objective methods the Government will use to monitor contractor performance and ensure services are received in accordance with the PWS. The QASP must be structured to directly address the five (5) evaluation gates outlined in FAR 52.212-2 of this solicitation.

1. Objective Standards & Numerical Acceptable Quality Levels (AQLs)

· The QASP shall include a detailed Performance Requirements Summary (PRS) Table. This table must establish specific, measurable, and numerical Acceptable Quality Levels (AQLs) for all core tasks identified in the PWS. The PRS Table must include, at a minimum, columns for: PWS Task Reference, Performance Standard, AQL (as a numerical threshold), Surveillance Method, and Remedies/Disincentives.

2. Automated Surveillance Integration via Live Dashboard & Portal

· The QASP shall establish that the primary surveillance method will be direct, continuous Government access to the contractor-provided live dashboard and knowledge management portal. The plan must demonstrate how this automated monitoring eliminates the need for manual data calls and provides real-time performance visibility.

3. Workforce Availability & Rapid Backfill Surveillance

· The QASP shall establish a binding surveillance metric for 100% Key Personnel availability. Furthermore, the plan must define the specific AQL and surveillance method to enforce that all vacated positions are backfilled with fully qualified, LCAT-compliant personnel within 14 calendar days of vacancy notification.

4. Financial Accuracy & FMS SLIN Segregation Auditability

· The QASP shall establish a specific AQL of 100% financial accuracy on all monthly Consolidated Cost Reports. It must also detail the auditing method to ensure there is a 0% tolerance for misallocation or cross-charging between domestic funding lines (CLINs) and Foreign Military Sales (FMS) cases (SLINs).

5. Corrective Action Plan (CAP) Remediation & Enforceable Remedies

· The QASP shall define the formal Corrective Action Plan (CAP) workflow that is triggered whenever performance drops below an established AQL. The plan must explicitly bind the Contractor to a 5-Business Day deficiency cure period and detail the specific contractual remedies the Government may invoke for non-performance.

Transition Plan The Offeror shall submit a detailed, executable Transition Plan governing the phase-in period after contract award.

1. 90-Day Transition Schedule: Provide a detailed, time-phased schedule illustrating milestones, deliverables, and resource ramp-up across the up to 90-day transition period.

2. Workforce Capture & Clearance Transition: Detail procedures for recruiting, onboarding, and transferring incumbent personnel, including verification that all personnel possess required security clearances and facility access approvals prior to Day 90.

3. Knowledge Transfer & Shadowing: Detail the knowledge acquisition process.

4. Live Dashboard, Account, & Facility Access Handover: Outline protocols for the conducting the handover of the live dashboard, transferring Government-furnished equipment (GFE), obtaining Common Access Cards (CACs), establishing building access, and assuming 24/7/365 coverage of the TSMO SCIF at Redstone Arsenal, AL.

5. Risk Mitigation: Identify transition risks and actionable mitigation strategies to ensure zero degradation to ongoing CPE ST3 mission support.

Compliance Matrix The Offeror shall submit a Compliance Matrix that maps the following:

1. The Offeror’s PWS to all sections of the SOO.

2. The Offeror’s Agile Implementation Plan to the PWS.

3. The Offeror’s PowerPoint Presentation to the PWS.

4. The Offeror’s proposed QASP to the PWS.

5. The Offeror’s price volume to the PWS, Agile Implementation Plan, PowerPoint Presentation The Government will not evaluate the Compliance Matrix as part of the Acceptable / Unacceptable criteria. The Government will use the matrix to assist in assessing where the Offeror has detailed their proposal to the Government’s requirements.

Volume 3 – Factor 3 - COST / PRICE PROPOSAL INSTRUCTIONS

· Fully Burdened Labor Rate Schedule

1. The Offeror shall complete the Government-provided Excel Pricing Model, providing fully burdened fixed hourly rates for all labor categories identified in their approved Labor Category (LCAT) Crosswalk.

2. Labor rates must encompass all direct labor, fringe benefits, overhead, general and administrative (G&A) expenses, corporate-funded training costs, and profit.

3. No separate training surcharges or off-site infrastructure fees will be paid by the Government.

· Unlimited Data Rights Certification The Offeror shall include a signed statement in Volume III – Administrative Volume, certifying that the Government will receive Unlimited Rights to all technical deliverables, dashboards, portals, database configurations, and business process artifacts generated under the contract.

(c) Period for acceptance of offers. The Offeror agrees to hold the prices in its offer firm for 180 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

https://www.acquisition.gov/far/subpart-4.10(d) Late submissions, modifications, revisions, and withdrawals of offers.

(1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation.

(2)(i) Any offer, modification, revision, or withdrawal of an offer received at the Government office designated in the solicitation after the exact time specified for receipt of offers is "late" and will not be considered unless it is received before award is made, the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and-

(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or

(B) There is acceptable evidence to establish that it was received at the Government installation designated for receipt of offers and was under the Government’s control prior to the time set for receipt of offers; or

(C) If this solicitation is a request for proposals, it was the only proposal received.

(2)(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.

(3) Acceptable evidence to establish the time of receipt at the Government installation includes the time/date stamp of that installation on the offer wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

(4) If an emergency or unanticipated event interrupts normal Government processes so that offers cannot be received at the Government office designated for receipt of offers by the exact time specified in the solicitation, and urgent Government requirements preclude amendment of the solicitation or other notice of an extension of the closing date, the time specified for receipt of offers will be deemed to be extended to the same time of day specified in the solicitation on the first work day on which normal Government processes resume.

(5) Offers may be withdrawn by written notice received at any time before the exact time set for receipt of offers. Oral offers in response to oral solicitations may be withdrawn orally. If the solicitation authorizes facsimile offers, offers may be withdrawn via facsimile received at any time before the exact time set for receipt of offers, subject to the conditions specified in the solicitation concerning facsimile offers. An offer may be withdrawn in person by an offeror or its authorized representative if, before the exact time set for receipt of offers, the identity of the person requesting withdrawal is established and the person signs a receipt for the offer.

(e) Contract award (not applicable to Invitation for Bids). The Government intends to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror’s initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received.

(f) Availability of requirements documents cited in the solicitation.

(1)(i) The GSA Index of Federal Specifications, Standards and Commercial Item Descriptions, FPMR Part 101–29, and copies of Federal specifications, standards, and product descriptions can be downloaded from the ASSIST website at https://assist.dla.mil.

(1)(ii) If the General Services Administration, Department of Agriculture, or Department of Veterans Affairs issued this solicitation, a copy of specifications, standards, and commercial item descriptions cited in this solicitation may be obtained from the address in paragraph (i)(1)(i) of this provision.

(2) Most unclassified Defense specifications and standards may be downloaded from the ASSIST website at https://assist.dla.mil.

(3) Defense documents not available from the ASSIST website may be requested from the Defense Standardization Program Office by—

(i) Using the ASSIST feedback module ( https://assist.dla.mil/feedback); or

(ii) Contacting the Defense Standardization Program Office by telephone at 571–767–6688 or email at assisthelp@dla.mil.

(4) Nongovernment (voluntary) standards must be obtained from the organization responsible for their preparation, publication, or maintenance.

(g) Unique entity identifier. (Applies to all offers that exceed the micro-purchase threshold, and offers at or below the micro-purchase threshold if the solicitation requires the Contractor to be registered in the System for Award Management (SAM).)

The Offeror shall enter, in the block with its name and address on the cover page (limited to 2-pages, which will not be included in any respective page count) of its offer, the annotation "Unique Entity Identifier" followed by the unique entity identifier that identifies the Offeror's name and address. The Offeror also shall enter its Electronic Funds Transfer (EFT) indicator, if applicable. The EFT indicator is a four-character suffix to the unique entity identifier. The suffix is assigned at the discretion of the Offeror to establish additional SAM records for identifying alternative EFT accounts (see FAR subpart 32.11) for the same entity. If the Offeror does not have a unique entity identifier, it should contact the entity designated at www.sam.gov for unique entity identifier establishment directly to obtain one. The Offeror should indicate that it is an offeror for a Government contract when contacting the entity designated at www.sam.gov for establishing the unique entity identifier.

(h) [Reserved]

(i) Debriefing. If a post-award debriefing is given to requesting offerors, the Government shall disclose the following information, if applicable:

(1) The agency’s evaluation of the significant weak or deficient factors in the debriefed offeror’s offer.

(2) The overall evaluated cost or price and technical rating of the successful and the debriefed offeror and past performance information on the debriefed offeror.

(3) The overall ranking of all offerors, when any ranking was developed by the agency during source selection.

(4) A summary of the rationale for award;

(5) For acquisitions of commercial products, the make and model of the product to be delivered by the successful offeror.

(6) Reasonable responses to relevant questions posed by the debriefed offeror as to whether source-selection procedures set forth in the solicitation, applicable regulations, and other applicable authorities were followed by the agency.

(End of provision)