Amendment 0002_90MC0026R00040002_SSS_Website Modernization Project_QA_06082026.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

90MC0026R00040002

Summary of Changes

Section IV: List of Documents, Exhibits, and other Attachments

The following attachments are added:

File Attachments:

Title Description File Name Entity Reference

Responses 1 Website

Modernization RFP - Vendor FAQs - 3 Jun

Responses 1 Website Modernization RFP -

Vendor FAQs - 3 June 2026 (002).docx (Size

:22189)

Responses 1 Website Modernization RFP - Vendor

FAQs - 3 June 2026 (002).docx

Header

Attachment 1

Selective Service System

Website Modernization Requirement

Q&A Numbers 1 through 14

Note: Amendment No. 0002 contains the first set of Government responses to vendor questions concerning this solicitation. The Government anticipates issuing additional responses through future amendments as questions continue to be reviewed and addressed.

Offerors are solely responsible for monitoring SAM.gov for all solicitation amendments, questions and answers, and other related notices. Failure to obtain or acknowledge solicitation updates does not relieve an offeror of responsibility for complying with the solicitation requirements as amended.

Q1) May the contractor inherit the Government's existing system authorization boundary / ATO for the modernized website, or is a net-new, independent system ATO required to be issued prior to the September 25, 2026, substantial-completion date? PWS Part 2.4 (Security) / Submittal Verification 26–27

A1) The ATO will need to be for a new system.

Q2) Does the September 25, 2026, substantial-completion requirement encompass formal ATO issuance, or does it apply to development, testing, and cutover-readiness, with the ATO timeline governed by the Agency's RMF process?

A2) We can accept "cutover ready" for ATO timeline in order to meet deadlines.

Q3) Will the Government furnish a hosting environment or existing cloud tenancy (e.g., an agency AWS account with an inherited authorization), or must the contractor provide the FedRAMP-authorized cloud environment in full? PWS Part 2.4, item 1 26

A3) The contractor shall provide and manage a FedRAMP-authorized Microsoft Azure Government hosting environment and be responsible for all associated security and operational requirements. AWS is not an option for this project (See Amendment 0001).

Q4) What is the Government's anticipated award date, so offerors can construct a credible schedule against the September 25, 2026, completion requirement? Instructions to Offerors / Project Schedule 25–26

A4) July 15, 2026.

Q5) For the CMS, will the Government accept a managed FedRAMP-authorized CMS platform (e.g., WordPress VIP, FedRAMP Moderate), or must WordPress be hosted within the agency's own cloud tenancy? PWS Part 2.4, items 1 and 5 26

A5) The contractor shall provide and manage a FedRAMP-authorized Microsoft Azure Government hosting environment and be responsible for all associated security and operational requirements.

Q6) Does the Government have a preferred or pre-authorized FedRAMP chatbot solution, or is an offeror-proposed FedRAMP-authorized service (e.g., Amazon Lex in AWS GovCloud) acceptable for the chatbot requirement (item 17)? PWS Part 2.4, item 17 27

A6) The Government does not have a preferred or pre-authorized chatbot solution.

Vendors may propose a FedRAMP-authorized chatbot service that meets the requirements of the solicitation.

Q7) Please identify the integration endpoints and their owners — specifically the Azure AD / Entra ID tenant and the existing registration system/database — and confirm whether interface documentation will be provided to the awardee. PWS Part 2 / Part 3 (Auto Registration Readiness)

A7) The contractor shall provide and manage a FedRAMP-authorized Microsoft Azure Government hosting environment and be responsible for all associated security and operational requirements. AWS is not an option for this project (See Amendment 0001).

The solution will integrate with five Government-managed endpoints, including Microsoft Entra ID and the existing registration system. Detailed interface documentation and technical requirements for applicable integrations will be provided to the awardee after contract award.

Q8) For Factor 3 (Past Performance), if an offeror submits the allowed “no qualifying reference” statement, how will the absence be scored relative to the Capability Statement?

Instructions / Factor 3 27–28

A8) Offerors should provide relevant past performance references. If an offeror does not have qualifying references, the Government will evaluate the proposal based on the Capability Statement and other information submitted in accordance with the evaluation criteria.

Q9) PWS 2.4 requires the contractor to "achieve and maintain a formal ATO at the FIPS 199 Moderate impact level." Please confirm: (a) SSS will serve as the Authorizing Official and own ATO issuance; (b) whether an existing system boundary, SSP template, or inheritable-control baseline (e.g., from the FedRAMP-authorized CSP) will be provided as Government-furnished information; and (c) whether SSS provides ISSO/ISSM support and the governance repository for RMF artifacts.

A9) SSS will serve as the authorizing official and issue the ATO; the SSS has ISSO support and will provide the repository for RMF artifacts; and can provide an SSP template.

Q10) Please confirm the current SSS.gov platform/CMS, the approximate volume of pages, documents, media, and forms in scope for migration (PWS 2.9), and whether a content inventory and current analytics exports will be provided as Government-furnished information at award.

A10) The appropriate volume of pages, documents, media, and forms will be provided.

Q11) For the AI conversational interface (PWS 3.2): will SSS accept a FedRAMP-authorized commercial SaaS conversational AI service formally approved by the Agency, with responses restricted to SSS-generated and Agency-approved content? Please also confirm whether the human-escalation endpoints (service desk, phone, email) already exist within

SSS.

A11) Yes, SSS has a FedRAMP-authorized commercial SaaS conversational AI service formally approved by the Agency. Yes, the answers are restricted to SSS-generated and Agency-approved content. The human-escalation endpoints exist already.

Q12) PWS 2.4 requires end-user authentication consistent with federal identity standards (e.g., Login.gov, PIV/CAC) and administrative login integration with the Agency's Azure AD/Entra ID. Please confirm whether SSS holds an existing Login.gov agency agreement for public-facing registration-record updates (PWS 2.2), and whether the automatic-registration web application (Part 3) owns end-user identity proofing, with the modernized website integrating via iFrame/API only.

A12) The Government does not currently maintain a login.gov agreement. Offerors may propose secure authentication and identity proofing solutions that meet applicable federal security and privacy requirements. The modernized website will integrate with existing registration services.

Q13) PWS 3.1 requires penetration testing of automatic-registration components, with testing scripts and documentation delivered to SSS. May this testing be performed by the contractor using industry-standard tooling and methodology, or does the Government require an independent third-party assessor?

A13) Penetration testing should be done by an independent third-party entity as determined by SSS.

Q14) PWS 4.3 lists a minimum of six (6) years of hands-on IT project management experience overseeing website development projects. Please confirm: (a) whether this requirement applies to the Project Manager only, or to both the Project Manager and Alternate Project Manager; and (b) whether the Government will consider equivalent IT project management experience (e.g., federal IT operations, enterprise digital platform management) in combination with website development project leadership as satisfying this requirement.

A14) The requirement applies only to the Project Manager.

Selective Service System, 1501 Wilson Blvd., Suite 700 Arlington, VA 22209, US

AMD_ISSUING_OFFICE_LOCCODE: 90MC00