1331L526R13350002 Draft FE.pdf

DRAFT

12/12/2025

DRAFT

1331L526R13350002

SECTION B ‐ SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 GENERAL

This procurement is a no-cost, $0.00 contract between the prospective awardee and the U.S. Department of Commerce (DOC). As a result, this is not a Federal Acquisition Regulations (FAR)-based contract.

However, select FAR and CAR clauses are incorporated into the contract to establish a contractual framework for Contractor performance and government contract administration. To the extent FAR or agency specific clauses are incorporated, those clauses are in full force and effect unless subsequently modified by mutual agreement of the parties.

B.2 CONTRACT TYPE

This is a no-cost contract. The Contractor will not receive any funding from the Government during the performance of this contract.

B.2 COST/PRICE

The Contractor shall not charge the U.S. Government to perform the requirements of this Contract. The

Contractor may establish and collect fees from third parties provided the fee levels are approved by the

Contracting Officer and are fair and reasonable. The Contractor shall base any proposed fee structure on the cost of providing the specific service for which the fee is charged and the resources necessary to monitor the fee driven requirements.

B.3 SCHEDULE

This contract consists of a transition period (up to nine (9) months), a base period of 36 months, and four

(4) one year ordering periods for a total ordering period of 7 years as depicted in Table 1.

Table 1: Schedule

Period Duration

Transition Period 9 months

Base Period 27 months

Option Period 1 1 Years

Option Period 2 1 Years

Option Period 3 1 Years

Option Period 4 1 Years

Total Ordering Period 7 Years

(End of Section B)

SECTION C ‐ DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 REQUIREMENTS DOCUMENT

See section J.1, Attachment 01 – REQUIREMENTS DOCUMENT

(End of Section C)

SECTION D ‐ PACKAGING AND MARKING

N/A

(End of Section D)

SECTION E ‐ INSPECTION AND ACCEPTANCE

E.1 CLAUSES INCORPORATED BY REFERENCE

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make the full text available. Additionally, the full text of a clause may be accessed electronically at this address:

https://www.acquisition.gov

(End of Section E) https://www.acquisition.gov/

SECTION F ‐ DELIVERIES AND PERFORMANCE

F.1 CLAUSES INCORPORATED BY REFERENCE

they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this address:

https://www.acquisition.gov

52.242‐15 STOP‐WORK ORDER (AUG 1989)

52.242‐17 GOVERNMENT DELAY OF WORK (APR 1984)

52.247‐34 F.O.B. DESTINATION (NOV 1991)

F.2 CLAUSES INCORPORATED IN FULL TEXT

NOTE: Base and option year period of performance start and end dates are based on a projected award date by April 30, 2026 and may be adjusted to coincide with date of actual award.

CAR 1352.270‐70 PERIOD OF PERFORMANCE (APR 2010)

NOTE: Base and option year period of performance start and end dates are based on a projected award date by April 30, 2026 and may be adjusted to coincide with date of actual award.

(a) The base period of performance of this contract is three (3) years. If an option is exercised, the period of performance shall be extended through the end of that option period. The period of performance for each Option Period is one (1) year.

(b) The notice requirements for unilateral exercise of option periods are set out in FAR 52.217‐ 9.

F.3 PLACE OF PERFORMANCE

The requirements of this contract shall be performed in the United States.

F.4 SCHEDULE OF DELIVERABLES

All deliverables, including administrative deliverables required during the period of performance of this contract, shall be in accordance with the terms and conditions of the contract. For lists of deliverables specific to technical performance requirements please reference the attached

Requirements Document.

For purposes of delivery, all deliverables shall be made by close of business (COB) 4:30 P.M.

local time at the destination, Monday through Friday, unless stated otherwise.

All deliverables submitted in electronic format shall be free of any known computer virus or defects. If a virus or defect is found, the initial deliverable shall not be accepted. A replacement file shall be provided within two (2) business days after notification.

Any failure of the Contractor to adhere to a delivery schedule or deliverable requirement may be reflected in the Contractor’s past performance report.

F.5 GOVERNMENT RIGHTS TO DELIVERABLES

All deliverables provided under this contract become the property of the U.S. Government. The

Government has unlimited rights to all documents/material produced under this contract pursuant to FAR 52.227‐17, Rights in Data‐Special Works. All documents and materials shall be

Government owned and the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the CO. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. These rights do not abrogate any other Government rights.

F.6 TIMELY NOTICE TO THE GOVERNMENT OF PERFORMANCE DELAYS

In the event the Contractor encounters difficulty in meeting performance requirements, or when it anticipates difficulty in complying with the contract delivery schedule or completion date, or as soon as the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the COR and CO, in writing.

This notification shall give pertinent details, but this data shall be informational only in character;

this term shall not be construed as a waiver by the Government of any delivery schedule or date, or any rights or remedies provided by law or under this contract.

(End of Section F)

SECTION G ‐ CONTRACT ADMINISTRATION DATA

G.1 CLAUSES INCORPORATED IN FULL TEXT

CAR 1352.201‐70 CONTRACTING OFFICER'S AUTHORITY (APR 2010)

The Contracting Officer is the only person authorized to make or approve any changes in any of the requirements of this contract, and, notwithstanding any provisions contained elsewhere in this contract, the said authority remains solely in the Contracting Officer. In the event the contractor makes any changes at the direction of any person other than the Contracting Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract terms and conditions, including price.

CAR 1352.201‐72 CONTRACTING OFFICER’S REPRESENTATIVE (COR) (APR 2010)

(a) Inserted at time of award is hereby designated as the Contracting Officer’s Representative

(COR). The COR may be changed at any time by the Government without prior notice to the contractor by a unilateral modification to the contract.

Email: (Will be inserted at time of award)

(b) The responsibilities and limitations of the COR are as follows:

(1) The COR is responsible for the technical aspects of the contract and serves as technical liaison with the contractor. The COR is also responsible for the final inspection and acceptance of all deliverables and such other responsibilities as may be specified in the contract.

(2) The COR is not authorized to make any commitments or otherwise obligate the Government or authorize any changes which affect the contract price, terms or conditions. Any contractor request for changes shall be referred to the Contracting Officer directly or through the COR. No such changes shall be made without the express written prior authorization of the Contracting

Officer. The Contracting Officer may designate assistant or alternate COR(s) to act for the COR by naming such assistant/alternate(s) in writing and transmitting a copy of such designation to the contractor.

(End of Section G)

SECTION H ‐ SPECIAL CONTRACT REQUIREMENTS

H.1 CLAUSES INCORPORATED BY REFERENCE

they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this address. As a reminder, this solicitation uses these clauses for ease of understanding and convenience. This solicitation and resultant contract are not bound by the CAR or FAR:

H.2 CLAUSES INCORPORATED IN FULL TEXT

CAR 1352.209-70 POTENTIAL CONFLICT OF INTEREST (APR 2010)

a) There is a potential organizational conflict of interest (see FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest) due to the inherent nature of the different types of tasks and services required. Accordingly:

1) Restrictions are needed to ensure that future Conflicts of Interest are mitigated or avoided.

2) As a part of the proposal, the offeror shall provide the Contracting Officer with complete information regarding previous or ongoing work that is in any way associated with the contemplated acquisition.

b) The organizational conflict of interest clause in this solicitation may not be modified or deleted.

(End of clause)

CAR 1352.209-74 ORGANIZATIONAL CONFLICT OF INTEREST (APR 2010)

(a) Purpose. The purpose of this clause is to ensure that the contractor and its subcontractors:

1) Are not biased because of their financial, contractual, organizational, or other interests which relate to the work under this contract, and

2) Do not obtain any unfair competitive advantage over other parties by virtue of their

Performance of this contract.

(b) Scope. The restrictions described herein shall apply to performance or participation by the contractor, its parents, affiliates, divisions and subsidiaries, and successors in interest

(hereinafter collectively referred to as “contractor”) in the activities covered by this clause as a prime contractor, subcontractor, co-sponsor, joint venturer, consultant, or in any similar capacity. For the purpose of this clause, affiliation occurs when a business concern is controlled by or has the power to control another or when a third party has the power to control both.

(c) Warrant and Disclosure. The warrant and disclosure requirements of this paragraph apply with full force to both the contractor and all subcontractors. The contractor warrants that, to the best of the contractor's knowledge and belief, there are no relevant facts or circumstances which would give rise to an organizational conflict of interest, as defined in FAR Subpart 9.5, and that the contractor has disclosed all relevant information regarding any actual or potential conflict. The contractor agrees it shall make an immediate and full disclosure, in writing, to the

Contracting Officer of any potential or actual organizational conflict of interest or the existence of any facts that may cause a reasonably prudent person to question the contractor's impartiality because of the appearance or existence of bias or an unfair competitive advantage. Such disclosure shall include a description of the actions the contractor has taken or proposes to take in order to avoid, neutralize, or mitigate any resulting conflict of interest.

(d) Remedies. The Contracting Officer may terminate this contract for convenience, in whole or in part, if the Contracting Officer deems such termination necessary to avoid, neutralize or mitigate an actual or apparent organizational conflict of interest. If the contractor fails to disclose facts pertaining to the existence of a potential or actual organizational conflict of interest or misrepresents relevant information to the Contracting Officer, the Government may terminate the contract for default, suspend or debar the contractor from Government contracting, or pursue such other remedies as may be permitted by law or this contract.

(e) Subcontracts. The contractor shall include a clause substantially similar to this clause, including paragraphs (f) and (g), in any subcontract or consultant agreement at any tier expected to exceed the simplified acquisition threshold. The terms “contract,” “contractor,” and “Contracting Officer” shall be appropriately modified to preserve the Government's rights.

(f) Prime Contractor Responsibilities. The contractor shall obtain from its subcontractors or consultants the disclosure required in FAR 9.507-1, and shall determine in writing whether the interests disclosed present an actual, or significant potential for, an organizational conflict of interest. The contractor shall identify and avoid, neutralize, or mitigate any subcontractor organizational conflict prior to award of the contract to the satisfaction of the Contracting Officer.

If the subcontractor's organizational conflict cannot be avoided, neutralized, or mitigated, the contractor must obtain the written approval of the Contracting Officer prior to entering into the subcontract. If the contractor becomes aware of a subcontractor's potential or actual organizational conflict of interest after contract award, the contractor agrees that the Contractor may be required to eliminate the subcontractor from its team, at the contractor's own risk.

(g) Waiver. The parties recognize that this clause has potential effects which will survive the performance of this contract and that it is impossible to foresee each circumstance to which it might be applied in the future. Accordingly, the contractor may at any time seek a waiver from the Head of the Contracting Activity by submitting such waiver request to the Contracting

Officer, including a full written description of the requested waiver and the reasons in support thereof.

(End of clause)

H.3 ELECTRONIC AND INFORMATION TECHNOLOGY

In addition to the work requirements specified in this requirements document, vendors must ensure that all electronic documents (e.g. public facing websites, WHOIS database, etc.) that they prepare will meet the requirements of Section 508 of the Rehabilitation Act. The act requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments. Vendors can view Section 508 of the Rehabilitation Act (http://www.access-board.gov/508.htm) and the

Federal IT Accessibility Initiative (Home Page) (http://section508.gov/) for detailed information.

Applicable Standards

The following standards have been determined to be applicable to this contract:

_____ 1194.21 Software applications and operating systems.

_____ 1194.22 Web-based intranet and Internet information and applications.

_____ 1194.23 Telecommunications products.

_____ 1194.24 Video and multimedia products.

_____ 1194.25 Self-contained, closed products.

_____ 1194.26 Desktop and portable computers.

The standards are available at http://www.access-board.gov/508.htm. The standards do not require the installation of specific accessibility-related software or the attachment of an assistive technology device, but merely require that the Electronic and Information Technology (EIT) be compatible with such software and devices so that it can be made accessible, if so required by the agency, in the future.

The following paragraphs summarize these requirements for preparing DOC required reports, policies and documents in conformance with Section 508 for eventual posting to a DOC-sponsored website (i.e. .us registry website). If you have further questions, please contact the

DOC Contracting Officer’s Representative listed in the requirements document.

Electronic documents with images:

http://www.access-board.gov/508.htm http://section508.gov/ http://www.access-board.gov/508.htm

Provide a text equivalent for every non-text element in all publications prepared in electronic format. Use descriptions (such as, "alt" and "longdesc") for all non-text images or place them in element content. For all documents prepared, vendors must prepare one standard HTML format

(as described in this statement of work) AND one text format that includes descriptions for all non-text images. “Text equivalent” means text sufficient to reasonably describe the image. For example, an image that is merely decorative requires only a very brief “text equivalent” description. However, if the image conveys information that is important to the content of the report, then text sufficient to reasonably describe that image and its purpose within the context of the report must be provided.

Electronic documents with complex charts or data tables:

When preparing tables that are heavily designed, provide adequate alternate information so that assistive technologies can read them out. Identify row and column headers for data tables. Provide the information in a non-linear form. Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

Electronic documents with forms:

When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues

H.4 POST AWARD EVALUATION OF CONTRACTOR PERFORMANCE

a) Interim and final evaluations of Contractor performance will be prepared on this contract in accordance with FAR 42.1502 and CAM 1342.15. The final performance evaluations will be prepared at the time of completion of work.

b) The Contractor can elect to review the evaluation and submit additional information or a rebuttal statement. The Contractor will be permitted 30 calendar days to respond unless an extension for an additional 30 days is requested in writing to the Contracting Officer.

Contractor response is voluntary. If the Contractor does not respond within 30 days (60 days if extension is requested), the Government will presume that the Contractor has no comment.

Any disagreement between the parties regarding an evaluation will be referred to an individual at a level above the Contracting Officer, whose decision is final.

c) Copies of the evaluations, Contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions.

d) The DOC Enterprise Acquisition Office (EAO) utilizes the Contractor Performance

Assessment Reporting System (CPARS) to record and maintain past performance information. CPARS hosts a suite of web‐ enabled applications that are used to document

Contractor performance information that is required by Federal Regulations.

e) The CPARS module assesses performance on contracts for Systems, Services, Information

Technology, and Operations Support. CPARS reference material can be accessed at http://www.cpars.gov/. The registration process requires the Contractor to identify an individual that will serve as a primary contact. This individual will be authorized access to the evaluation for review and comment. In addition, the Contractor is encouraged to identify a secondary contact in the event the primary contact is unavailable to process the evaluation within the required 30‐day time period. After the DOC Contract Specialist registers the contract in CPARS, the Contractor will receive a system generated e‐mail notifying him/her that the contract is registered. A system generated e‐mail will also provide the Contractor with a User ID if the person does not already have a CPARS User ID.

f) Once a performance evaluation has been prepared and is ready for comment, the Contractor representative will receive a system generated e‐mail notification that the performance evaluation is electronically available for review and comment. The Contractor representative will receive an automated e‐mail whenever an assessment is completed and can subsequently retrieve the completed assessment from CPARS. Contractors may access evaluations at http://www.cpars.gov/ for review and comment in CPARS.

H.5 POST AWARD CONFERENCE

The Contractor shall participate in a post award conference to be held within thirty (30) business days after award of this contract. The purpose of the post award conference is to aid both the

Contractor and the Government in achieving a clear and mutual understanding of all contract requirements and identify and resolve potential problems and to ensure the timely commencement of a transition, if any, from the incumbent contractor.

The CO is responsible for establishing the time and place of the conference and will notify the appropriate Government representatives and the Contractors. The conference may be conducted at a location within the Washington, D.C. commuting area, regionally to facilitate Contractor attendance, or virtually at the Government’s discretion.

H.6 UNAUTHORIZED INSTRUCTIONS FROM GOVERNMENT PERSONNEL

The Contractor will not accept technical direction issued by any other person employed by the

U.S. Government other than the Contracting Officer or the Contracting Officer's Representative

(COR) acting within the limits of their authority.

http://www.cpars.gov/ http://www.cpars.gov/

No information, other than that which may be contained in an authorized modification to this contract will be considered as grounds for deviation from any stipulations of the contract's terms and conditions.

H.7 NEWS RELEASES

The Contractor shall make no news releases pertaining to the contract award and/or performance thereunder without prior agency approvals and then only in coordination with the Contracting

Officer.

(End of Section H)

SECTION I ‐ CONTRACT CLAUSES

I.1 CLAUSES INCORPORATED BY REFERENCE

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this address:

52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN

FEDERAL TRANSACTIONS (JUN 2020)

52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL

CONFIDENTIALITY AGREEMENTS OR STATEMENTS (JAN

2017)

52.203‐17 CONTRACTOR EMPLOYEE WHISTLEBLOWER RIGHTS AND

REQUIREMENT TO INFORM EMPLOYEES OF

WHISTLEBLOWER RIGHTS (NOV 2023)

52.204‐13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE

(OCT 2025)

52.240-91 SECURITY PROHIBITIONS AND EXCLUSIONS (OCT 2025)

52.209-10 PROHIBITION ON CONTRACTING WITH INVERTED

DOMESTIC CORPORATIONS (OCT 2025)

52.212-1 INSTRUCTIONS TO OFFERORS --- COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES (OCT 2025)

52.224‐3 PRIVACY TRAINING (JAN 2017)

52.227‐17 RIGHTS IN DATA—SPECIAL WORKS (DEC 2007)

52.233-4 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT

2025)

52.237‐3 CONTINUITY OF SERVICES (JAN 1991)

52.244‐2 SUBCONTRACTS (JUN 2020)

52.245‐9 USE AND CHARGES (APR 2012)

I.2 CLAUSES INCORPORATED IN FULL TEXT

FAR 52.240-93 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (OCT 2025)

(a) Definitions. As used in this clause—

Covered contractor information system means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.

Federal contract information—

(1) Means information, not intended for public release, that is provided by or generated for the

Government under a contract to develop or deliver a product or service to the Government; but

(2) Does not include information provided by the Government to the public (such as on public websites) or simple transactional information (such as information necessary to process payments).

Information means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C.

3502).

Safeguarding means measures or controls that are prescribed to protect information systems.

(b) Safeguarding requirements.

(1) Basic requirements. The Contractor shall safeguard its covered contractor information systems by implementing, at minimum, the following security controls:

(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.

(iii) Verify and control/limit connections to and use of external information systems.

(iv) Control information posted or processed on publicly accessible information systems.

(v) Identify information system users, processes acting on behalf of users, or devices.

(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

(vii) Sanitize or destroy information system media containing Federal Contract Information before disposal or release for reuse.

(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.

(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.

(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.

(xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

(xii) Identify, report, and correct information and information system flaws in a timely manner.

(xiii) Provide protection from malicious code at appropriate locations within organizational information systems.

(xiv) Update malicious code protection mechanisms when new releases are available.

(xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

(2) Other requirements. This clause does not relieve the Contractor of any other specific safeguarding requirements specified by Federal departments and agencies relating to covered contractor information systems generally or other Federal safeguarding requirements for controlled unclassified information (CUI) as established by Executive Order 13556.

(c) Subcontracts. The Contractor shall include the substance of this clause, including this paragraph (c), in subcontracts under this contract (including subcontracts for the acquisition of commercial products, other than commercially available off-the-shelf items, or commercial services), in which the subcontractor may have Federal contract information residing in or transiting through its information system.

FAR 52.217‐8 OPTION TO EXTEND SERVICES (NOV 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting

Officer may exercise the option by written notice to the Contractor at least 10 days before the contract completion.

FAR 52.217‐9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR

2000)

a) The Government may extend the term of this contract by written notice to the Contractor within one (1) day, provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 10 days before the contract expires. The preliminary notice does not commit the Government to an extension.

b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 90 Months.

FAR 52.232-40 PROVIDING ACCELERATED PAYMENTS TO

SMALL BUSINESS SUBCONTRACTORS (MAR 2023)

(a)[(1) In accordance with 31 U.S.C. 3903 and 10 U.S.C. 3801, within 15 days after receipt of accelerated payments from the Government, the Contractor shall make accelerated payments to its small business subcontractors under this contract, to the maximum extent practicable and prior to when such payment is otherwise required under the applicable contract or subcontract, after receipt of a proper invoice and all other required documentation from the small business subcontractor.

(2) The Contractor agrees to make such payments to its small business subcontractors without any further consideration from or fees charged to the subcontractor.

(b) The acceleration of payments under this clause does not provide any new rights under the

Prompt Payment Act.

(c) Include the substance of this clause, including this paragraph (c), in all subcontracts with small business concerns, including subcontracts with small business concerns for the acquisition of commercial products or commercial services.

(End of clause)

(End of Section I)

SECTION J ‐ LIST OF DOCUMENTS, EXHIBITS AND OTHER

ATTACHMENT

1. Requirements Document (PWS)

2. Questions and Answers Submission Sheet

(End of Section J)

SECTION K ‐ REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS

N/A

(End of Section K)

SECTION L ‐ INSTRUCTIONS, CONDITIONS, AND NOTICES TO

OFFERORS

The U.S. Government will accept questions on the draft solicitation from Offerors only during the draft solicitation phase. This is the only Q&A period the U.S. Government will offer.

Questions from Offerors about the solicitation will not be accepted once the final solicitation is released. Offerors are directed to begin each question with the Solicitation section noted in parenthesis before the question itself. A sample is indicated below.

(Section Reference) Text of Question

(L.2) What font is required Phase 1 proposals?

The dates for Q&A, as well as the responses to the Q&A, will be posted on SAM.gov.

L.1 INCUMBENT CONTRACTOR

Registry Services LLC

21575 Ridgetop Circle

Sterling, VA 20166

Contract No. 1331L519C13350044

L.2 GENERAL

i. Offerors are instructed to read the entire RFP document, including all attachments, prior to submitting questions and/or preparing your proposal. Omission of any information from the proposal submission requirements may result in rejection of the proposal.

ii. Offerors are required to be actively registered in SAM when submitting an offer and shall continue to be actively registered until time of award, during performance, and through final payment of any contract resulting from this solicitation. Refusal or failure to register may forfeit consideration for award. Note that “Active” SAM registration is specifically required; “ID Assigned” registration is not acceptable.

iii. Proposals shall be prepared in accordance with this RFP and are required to conform to the provisions of this RFP and the instructions of this section. To aid in the NTIA’s evaluation, the proposal shall be clearly and concisely written as well as be neat, indexed (cross-indexed as appropriate), and logically assembled. All pages of each part shall be appropriately numbered and identified with the name of the offeror, the date, and the Solicitation number. The Technical Volume I, Technical Volume II, and Cost

Volume shall be distinguishable from each other and appropriately labeled. Text shall be single-spaced with a minimum of one-inch margins on all sides. All written submissions shall be 12-point font, Times New Roman. Figures and tables may use 11-point font, Times New Roman. Figures and tables will count toward the page limit. All written submissions shall be machine readable.

iv. All correspondence in conjunction with this solicitation must be directed to the

Government Contracting Officer and Contract Specialist identified below:

Contracting Officer: Jacqueline Brown

E-mail address: jbrown4@doc.gov

Contract Specialist: Blen Gabriel

E-mail address: BGabriel@doc.gov

All email correspondence shall reference the RFP number in the subject line.

v. Proposals must be received by the Strategic Solutions Program Office on or before the due date and time specified in the RFP. Only information received on or before the due date and time shall be considered for award. Any proposal, or part thereof, received after the due date and time, shall be deemed late and not considered for award.

Facsimile proposals will not be accepted. Hard copy proposals via postal mail will not be accepted.

Proposals shall be submitted via email to Jacqueline Brown, jbrown4@doc.gov and

BGabriel@doc.gov

vi. This RFP does not commit the Government to pay any cost for the preparation and submission of a proposal.

L.3 Phased Procurement Schedule

The Government intends to conduct the proposal submission and evaluation process in two (2)

Phases. All dates included in the table below are intended to be helpful with planning purposes and are not set in stone; these dates are subject to change and may fluctuate. It is the

Government’s intent to adhere to this schedule. A notional schedule for the procurement is below:

Table 2: Phased Procurement Schedule

Draft RFP Release December 2025

Questions Due January 2026

Final RFP Release January 2026

Phase 1 Submissions Due February 2026

Government Sends Advisory Notifications February 2026

Phase 2 Submissions Due March 2026 mailto:jbrown4@doc.gov mailto:jbrown4@doc.gov mailto:BGabriel@doc.gov

Negotiations March 2026

Award April 2026

Evaluation Factors Summary

Phase 1 (Written)

Technical Volume I: Demonstrated Experience & Approach (Factor 1)

Phase 2 (Written and Oral)

Technical Volume II: Work Statement Submissions (Factor 2) (Written and Oral)

Cost Volume: Budget Proposal (Factor 3) (Written and Oral)

The factors are listed in descending order of importance. When combined, Factors 1 and 2 are more important than Factor 3.

L.4 Question and Answer Process

The Government intends to release a Draft Solicitation prior to the release of the Final

Solicitation. The intention is to release all documents as drafts and to conduct the traditional question and answer (Q&A) process in which bidders may submit questions for the DOC to respond to during the Draft Solicitation phase only. The Government does not intend to allow for an additional round of questions after responses are provided during the Draft Solicitation phase. However, the Government reserves the right to conduct an additional round of Q&As during the Phased Process. Please use this Draft Solicitation question period to submit your questions as opposed to waiting until the Final Solicitation is released

The Government intends to allow for questions from potential Offerors upon release of the Draft

Solicitation and related documents. Questions relevant to this Draft Solicitation must be submitted via email to jbrown4@doc.gov and BGabriel@doc.gov .

Questions are due no later than 2:00 PM Eastern Time on January 8, 2026.

The Government may not provide a response to questions submitted after the due date.

Offerors will not receive a response until all questions have been received by the date due.

Once reviewed and addressed, the Contracting Officer (CO) will post the complete Q&A response to www.SAM.gov.

L.5 Proposal Instructions

The following instructions are for the preparation and submission of proposals. The purpose of this section is to establish requirements for the format and content of proposals so that proposals contain all essential information and can be evaluated equitably.

This solicitation and its evaluation are being conducted in two phases. The purpose of the mailto:jbrown4@doc.gov mailto:BGabriel@doc.gov two-phase approach is to streamline the process for offerors and minimize traditional burdens associated with lengthy submissions. The two-phase approach requirements are summarized in the table below.

Table 3: Proposal Instructions

Proposal Submission Page Limit

Phase 1 Submission: Technical Volume I (PDF)

Factor 1: Demonstrated Experience &

Approach

15 Pages

Advisory Down-Select Notification

Phase 2 Submission: Technical Volume II (PDF)

Factor 2: Work Statement Submission 33 Pages

Phase 2 Submission: Cost Volume (Excel)

Factor 3: Fee Structure with Cost Narrative N/A

All information within the page limitations of the proposal is subject to evaluation. Written content that extends beyond the page limitations may not be considered and may result in the offeror’s proposal being rejected. The use of hyperlinks in the written proposals is discouraged and any hyperlinks provided may not be reviewed.

The cover page shall include the offeror name, contact information, and Unique Entity

Identifier (UEI). The cover page shall also identify which track(s) the proposal is submitted for.

No cover letter, executive summary, or table of contents is required. Any cover letter, executive summary, or table of contents provided will not be evaluated.

L.6 Phase 1 Submission: Technical Volume 1

Factor 1 – Demonstrated Experience & Approach

The Offeror shall submit a PDF document, totaling no more than 15 pages, detailing its demonstrated relevant experience and approach as it aligns to Table 4 “Factor 1 – Demonstrated

Experience & Approach - Description and Questions” outlined below. In Phase 1, Offerors are encouraged to provide only the necessary documentation to meet the requirements of Factor 1.

Of the 15 pages, 13 pages are permitted for a narrative response to the questions/prompts listed in Table 4, and two (2) pages total are permitted for Reference Point of Contact (POC) information using the Reference POC Template provided as an attachment to this solicitation.

Each project reference must use the template and no more than three (3) project references.

When asked to provide experience against the question/prompts below, the Offeror shall use no more than three (3) projects during the last five (5) years where the vendor served as the prime contractor specifically focused on the questions/prompts below. In other words, experience as a domain name registry operator will likely instill higher confidence than other experience performed within the domain name industry.

Table 4: Factor 1 – Demonstrated Experience & Approach - Description and Questions

The United States country code Top Level Domain (usTLD) administrator is responsible for administering the .us domain in the public interest and for the benefit of the nation’s businesses, organizations, and individuals. The role of the Administrator is to ensure the secure, stable, and reliable operation of the .us domain name system (DNS); to create, maintain, and evolve a policy-rich environment for the usTLD; and to advance the multistakeholder approach to Internet governance.

Currently, there are over 2.5 million names in the usTLD zone, including approximately 12,500

“locality names.”

# Background for

Question

Question/Prompt

1 Stability of

Operations and

Compliance. To ensure the security, stability, and reliability of the .us

Top-Level Domain

(TLD), respondents must demonstrate extensive experience in

TLD operations at scale.

Please provide detailed responses to the following:

1. Domain Management Operation and Scale: a. Provide evidence that you currently operate a TLD, have been operating a TLD continuously for at least the past five years, and manage a TLD of with at least two million domains under management (DUM). Such evidence may include Registry Agreements with ICANN. b. Detail your operational history, including major operational and/or security incidents and how they were resolved.

2. Registrar Connectivity: a. List the ICANN-accredited registrars with which you maintain operational connections. b. Briefly describe how these relationships are, or were previously, securely maintained.

3. Regulatory Compliance: a. Describe how you ensure compliance with relevant security and privacy regulations applicable to the TLD(s) you operate. b. Provide two examples of security frameworks, certifications, or audits that demonstrate compliance with industry standards.

2 DNS Abuse and Other

Malicious Conduct in the usTLD. The

Department seeks proposals for comprehensive policy approaches for the prevention, disruption, and mitigation of malicious conduct in the usTLD, including

DNS Abuse and practices that harm, Describe the proactive measures and strategies you employ to mitigate and prevent DNS Abuse. Detail any automated tools, monitoring systems, incentive programs, or early-warning mechanisms you use to detect potential threats and take preemptive action to safeguard the

TLD(s) you operate. Detail how you incentivize registrars to take action to prevent and/or mitigate DNS Abuse.

Describe your process to addressing reports of DNS Abuse. Detail the obligations of the Registrar in preventing, mitigating, and responding to DNS Abuse. Describe how the responsibilities of the Registry and the Registrar differ in the application of EPP codes to a registration, as well as in the Registrar’s obligations toward the Registrant.

mislead, or confuse consumers. DNS Abuse includes techniques that harm consumers, such as malware (including ransomware), botnets, phishing, pharming, and spam (when spam serves as a delivery mechanism for the other forms of DNS

Abuse). Proposals should meet or exceed industry best practices regarding DNS abuse mitigation.

3 Evidence-Based DNS

Abuse Reporting.

Detail how you use evidence-based reporting to track, document, and analyze DNS Abuse incidents. Include two examples of the types of data and metrics collected, as well as how this data is used to act against DNS Abuse. Explain how you ensure the accuracy, reliability, and transparency of DNS Abuse reports and the mechanisms in place to verify the integrity of the data.

4 Actions on Illegal and

Egregious Website

Content and

Transparency

Reporting on DNS

Abuse, Legal Orders, and Egregious

Website Content

Detail the specific tools, technologies, and methodologies you employ to detect, address, and prevent Child Sexual Abuse Materials (CSAM), the illicit distribution of opioids and narcotics online, and other egregious website content. Outline the third-party organizations and trusted partnerships you employ to ensure a comprehensive, effective response. Detail how these collaborations inform and enhance your approach to address these critical issues.

Describe the transparency reports you will provide related to DNS

Abuse, court orders, requests from law enforcement, and actions taken against egregious forms of website content abuse. For each area, outline the frequency, level of detail, and key metrics included in these reports. Provide two examples of any existing transparency reporting.

5 Due Process and

Appeal Mechanisms for Anti-Abuse

Actions.

Outline the steps involved in any registrant appeal process you provide, including any timelines, fees and requirements for registrants.

Explain whether registrants can appeal decisions to an independent third party and, if so, the third-party entities that are involved in the appeals process. Detail how your system ensures fairness, transparency, and adherence to relevant legal and regulatory standards in handling appeals.

6 Registrant

Compliance Auditing and Verification.

Describe your approach to auditing registrants for compliance with the nexus requirement. Your response should include:

1. Random Audit Plan: A brief synopsis of the structured plan for conducting a defined number of random registrant audits per month.

2. Evaluation Process: A brief synopsis of a clearly defined process for assessing registrants based on established nexus registration requirements.

3. Verification Procedures: Describe how your organization verifies the following registration details as part of the random audit process:

a. The domain name, b. The date of registration, c. The registrant’s name, contact email address, and telephone number, and d. The contact email address and telephone number of the domain name’s administrative point of contact (if different from the registrant’s).

4. Mitigation & Appeals Process:

a. Provide an example of a plan outlining the steps taken if a registrant fails an audit, including measures for compliance remediation that you currently use.

b. Briefly describe a due process mechanism you employ for registrants to appeal any suspension of a domain name resulting from an audit failure.

7 Registrar

Accreditation Plan.

Detail your plan to ensure that registrars are accredited as entities registered in the U.S. or with validity to operate and carry out business within the U.S.; as entities with the capacity to provide services to

Registrants in accordance with the Requirements Document; and as entities with a current, effective “Information Security Management

System” in compliance with ISO 27001 or an equivalent recognized security standard or framework.

The Offeror must submit associated information on the projects referenced in the narrative response to the questions/prompts in Table 4. These are limited to two (2) pages and no more than three project references. The Offeror must use the Reference POC template provided in

Section J as an attachment to this solicitation.

The Government may contact the Reference POC to confirm the level and quality of this demonstrated prior experience submissions. In addition, the Government reserves the right to review any information contained within the Contractor Performance Assessment Reporting

System (CPARS) or any other Government system, source, or individual.

L.6.1 Down-Select Process

In Phase 1 of this solicitation, the Government will evaluate the Factor 1: “Demonstrated

Relevant Experience” submissions and provide advisory notifications to Offerors. This notification will advise or instruct the Offerors of the government’s advisory recommendation to individual Offerors to proceed or not to proceed with the Phase 2 submission. The Government’s advisory notification for proposals is intended to be a recommendation only and those Offerors who are advised not to proceed may elect to continue their participation in the procurement. The

Government also may provide notification to some Offerors that they are not permitted to continue, if they appear not to be remotely viable.

Proceeding to Phase 2: The Government does not intend to provide feedback after the completion of the down-select process, beyond that which is included in the down-select notification. Failure to participate in Phase 1 of the procurement precludes further consideration of an Offeror. Phase 2 submissions will not be accepted from Offerors who have not submitted

Phase 1 proposals by the due date and time stated in this RFP. All Offerors who choose to proceed with a Phase 2 submission shall send an email to the Contracting Officer listed in L.2 no later than 48 hours after receipt of the down-select notifications, indicating their intent to participate in Phase 2. However, the actual notification will include the definite dates and required response time. Failure to respond within the time frame indicated in the down-select notification may preclude the Offeror from being further considered for award.

Phase 2 Instructions: After the down-select process concludes, the Government will issue Phase

2 submission instructions to all Offerors who have proceeded to Phase 2. The Government recommends Offerors begin preparation of Phase 2 quotes only after receipt of the Phase 1 down-select notices.

L.7 Phase 2 Instructions

Factor 2 – Work Statement Submissions & Oral Briefing

The purpose of this factor is for the Government to understand the Offeror’s proposed work statement submissions (WSS) in response to the Baseline Performance Objectives (BPO) detailed in Table 5 and corresponding to the Requirements Document attached to this solicitation. The Government will assess its level of confidence that the Offeror’s written WSSs and Oral Briefing clearly and thoroughly respond to the elements included for Factor 2, as well as any exchanges that occur during the presentation. This briefing also allows both parties

(Offerors and the Government) to engage in an interactive dialogue session to ask and answer any questions for the submitted WSS or any other question or topic. The table below provides a crosswalk from the Requirements Document, BPO, WSS, and page count. The page limitations for each section are strict. Offerors are not permitted to include coverage of a corresponding scope element, corresponding requirement, or corresponding WSS in different section’s page limitation.

Offerors are advised that where the RD requests that Offerors present or propose new solutions, agreements, or policies (e.g. section 6.12, section 6.30, and section 12.0), Offerors are invited to provide a draft, outline, or description of this solution as part of their WSS. Any draft agreements or policies may be attached as an annex and will not count toward the page limit of 33 pages.

Table 5: Requirements Document Baseline Performance Objectives

Scope Element Corresponding

Requirement

Corresponding Work Statement Submission

(WSS)

Page

Limits (33 total)

4.1 The Contractor

shall provide centralized

6.1 – Implement policies

6.9.1 – Universal Acceptance 10 pg management and coordination of registry, registrar

(where specified), database, and information services for the usTLD. In doing so, the

Contractor must ensure that policy and procedures for the administration of the usTLD support a secure, stable, and resilient DNS.

6.2 – Provide infrastructure

6.3 – Core registry functions

6.4 – Risk mgmt.

program (ISO 31000)

6.5 – Registrar

Exceptions

6.6 – Comply with

IETF, ICANN policies

6.7 – DNSSEC

6.8 – ROA/RPKI

6.9 – Universal

Acceptance

6.10 – Security/Privacy

Practices (ISO 27001)

6.15 – Secure transfer post re-accreditation

6.20 – usTLD locality space

6.21 – usTLD registration database at the Registry level

6.22.4 – Secure and Accountable Access to usTLD Registration Data

6.23 – Accuracy of usTLD registrant data – compliance/enforcement

4.2 The Contractor

shall not serve as a…