VA Modernized Messaging Software as a Service (SaaS)

Amendment / Modification

This document is an amendment to the solicitation.

• SF 1449 Solicitation/Contract/Order for Commercial Products and Commercial Services

• Section B: Continuation of SF 1449 Blocks

• Section C: Contract Clauses

• Section D: Contract Documents, Exhibits, or Attachments

• Section E: Solicitation Provisions

• The Offer Due Date has been extended to October 31, 2025, at 14:00 CST.

• The Solicitation Issue Date remains June 26, 2025.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding Solicitation 36C10A25R0002 for a Modernized Messaging Software as a Service (SaaS) solution. These answers are for informational purposes and do not amend the RFP unless explicitly stated.

• Funding: Funding is not currently available due to a Federal Government shutdown. Award will occur once funds are made available. FAR Clause 52.232-18 "Availability of Funds" has been added via amendment.
• Software Licenses: OEM COTS software licenses will not be treated as "materials" or "supplies" excluded from the 50% self-performance calculation. This is a SaaS requirement.
• Technical Evaluation (Step 2): Evaluators will use Apple and Android mobile devices. Application login credentials can be sent separately per FAR 52.212-1.
• Proposal Submission: Offerors must address Attachment D.1 (Functionality Checklist) and D.2 within the Volume I Technical response narrative, not in separate Excel spreadsheets. The page count maximum for Volume I remains 35 pages.
• FedRAMP: FedRAMP Moderate is the minimum acceptable requirement. The VA will accept the underlying platform's FedRAMP High authorization, but any integrations processing, storing, or transmitting data must be separately authorized.
• Mobile Device Data Storage: For Government-Furnished Equipment (GFE) managed by Mobile Device Management (MDM), data storage is acceptable. For Bring-Your-Own-Device (BYOD), no data should be stored on the personal device; storage in the SaaS environment is acceptable.
• ATO Timeline: Authority to Operate (ATO) approval can take 9 months to a year. Significant application security responsibilities fall under the vendor's SaaS environment and mobile application.
• License Scaling: The VA intends to utilize 20,000 licenses initially, with the ability to scale up to 120,000.

Several clarifications have been incorporated via amendment, including the addition of FAR Clause 52.232-18 and updates to Attachment D.3 to align with PWS B.4.14. Offerors must adhere to the updated instructions regarding proposal content and format, particularly concerning Attachments D.1 and D.2.

Form / Attachment / Pricing Sheet

This document contains three attachments (D.1, D.2, and D.3) related to the solicitation for a modernized messaging application. Attachment D.1 is a Functionality Checklist, Attachment D.2 contains Service Model Questions, and Attachment D.3 outlines Step 2 Evaluation criteria based on specific use cases.

Attachment D.1 - Functionality Checklist:

• Details specific requirements for a messaging software application, focusing on privacy, security, functionality, notifications, and performance.
• Key requirements include data partitioning, PII/PHI/SPI protection, audit trails, secure messaging capabilities (text, images, documents), device screen personalization, fast response times (1-10 seconds loading, 100ms response), group messaging, role-based profiles and logins, message escalation rules, hotlinking, customizable notifications, and near real-time delivery confirmations.
• Performance standards include Wi-Fi Offloading Availability (99.95%), Time to Restore (4 hours), and Response Time (100 milliseconds).

Attachment D.2 - Service Model Questions:

• Poses questions regarding the product's overview, hosting location (AWS, GCP, Azure), access methods (web browser, mobile app), authentication processes (SSO, username/password), user account management, multi-tenancy, horizontal scalability, and OCONUS development/data access.

Attachment D.3 - Step 2 Evaluation:

• Outlines specific use cases (A-F) for evaluating the software application's capabilities and effectiveness, focusing on role-based communication, message escalation, directory functions, on-call scheduling, surrogate coverage, and emergency communication.
• Use cases detail scenarios for sending messages to individuals and groups, contacting peers without names, managing on-call schedules, assigning coverage, and communicating in emergency settings.

Bidders must review these attachments to understand the detailed functional, technical, and evaluative requirements for the messaging application. The Functionality Checklist (D.1) specifies critical features and performance metrics. The Service Model Questions (D.2) probe aspects of the SaaS offering. The Step 2 Evaluation (D.3) provides concrete examples of how the application's capabilities will be assessed against real-world use cases, guiding proposal development and solution design.

Amendment / Modification

• The solicitation (36C10A25R0002) is amended to provide an updated RFP with identified changes highlighted in red text. Offerors are required to use this amended version for their response.

• The due date for offers has been extended to October 31, 2025, at 2:00 PM CST.

• The entire RFP is affected by the inclusion of the amended version.

• The submission deadline has been changed.

• Offerors must acknowledge receipt of this amendment.

• The proposal submission deadline is now October 31, 2025, at 2:00 PM CST.

• Offerors must use the amended RFP document for their submission.