QA - DJA-26-ASOD-PR-0271 5_20_2026.pdf
PDF 193 KB Posted
- Attached to
- Replacement Notification System
- Solicitation number
- DJA-26-ASOD-PR-0271
About this file
This is a Questions and Answers document for ATF solicitation DJA-26-ASOD-PR-0271 regarding a Replacement Notification System, posted on 5/20/2026. The document addresses seven questions from potential bidders regarding system requirements, certification standards, user/contact databases, pricing structure, and proposal deadlines.
The requirement is for a FedRAMP Moderate-certified Software-as-a-Service (SaaS) cloud-based mass notification system hosted in the vendor's environment. ATF anticipates sending approximately 16,000 SMS messages and 15,000 emails per month, with push notification volume currently unknown. The system must support two databases: an employee notification database with approximately 10,000 contacts and a Federal Firearms Licensee database with approximately 90,000 contacts. Only 50 government users/administrators will require system access to send alerts; the 90,000 contacts will be imported from ATF's Firearms Licensing System to receive notifications only. Currently, ATF maintains approximately 500 contacts in the existing system but plans to upload government employees and interagency partners totaling 10,000 contacts. Bidders must propose a pricing structure with clear cost breakdowns for all services, including program and project management fees, with price escalations for option periods reflected in CLINs 5-16. The successful bidder must hold FedRAMP Moderate certification as a minimum; DoD-compliant or CMMC2 certifications do not satisfy this requirement. ATF indicated no further extension to the proposal deadline will be granted beyond the original submission date.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Q&A
Replacement Notification System
DJA-26-ASOD-PR-0271
Question #1 1) Approximately how many SMS messages do you send per month?
2) Approximately how many Emails do you send per month?
3) Approximately how many Push Notifications do you send per month?
Answer As a general statement, we note that the PWS requires that “the proposals must include a pricing structure indicating the cost breakdown for all the included services offered.” If a bidder is not proposing a fixed-price for an unlimited number of notifications (of all types) in their bid, then the pricing structure for any notifications that exceed what is included in the base cost must be clearly identified in the proposal. The numbers provided below are what we anticipate will be the requirement for the combined use of both databases specified in PWS Section 5.3. We do not currently use push notifications so it is difficult to provide an estimate, however, it is reasonable to believe that they could equal share some of the allocation to SMS/MMS message that we currently send.
1) Approximately how many SMS messages do you send per month? 16,000
2) Approximately how many Emails do you send per month? 15,000
3) Approximately how many Push Notifications do you send per month?
Unknown
We anticipate the employee notification database will have approximately 10,000 contacts and the Federal Firearms Licensee database will have approximately 90,000 contacts.
Question #2 This is a request for more information regarding the solicitation for the ATF's FedRAMP Moderate software-as-a-service (SaaS) cloud operated mass notification system replacement. We currently have a server through Prevail I believe would fit your needs and is DoD compliant. We should have our CMMC2 within a month. Let me know if you can elaborate further on the ATF's requirements so we can bid appropriately.
Thanks for your time and consideration, Answer The successful bidder under this solicitation must have FedRAMP (fedramp.gov) which is a GSA managed cloud services certification for civilian Federal agencies. We appreciate the work required to certify system for defense use, however, these standards are designed for a different environment, and this solicitation requires FedRAMP certification at a minimum of the Moderate level.
5/20/2026
Question #3 Questions/Answers posted 5/19/2026- please confirm that the answer to Question #1 does in fact require/add 90,000 Federal Firearms License Database users for the FedRAMP license use.
Answer The Federal Firearms Licensee database has approximately 90,000 contacts, i.e. people that could be notified by the system. There will be 50 users/administrators. These users/administrators are Government employees that will be able to administer the system and send alerts. The 90,000 contacts would not need access to the system to manipulate their own data or otherwise actually use the system. The contacts would solely be imported to the notification system from our Firearms Licensing System in order to receive notifications.
Question #4 Questions/Answers posted 5/19/2026- please indicate whether the
90,000 users for Firearms License Database users are new from the existing system that is being used by ATF today. Additionally, can ATF also indicate how many of the 10,000 contacts are a mix of existing and new- how many in existing tool today?
Answer ATF currently conducts a query in the Firearms Licensing System to identify contacts for a particular notification scenario and exports that data using a CSV file and uploads it into the notification system. After the notification is complete, the contacts are deleted so there are no contacts maintained in the notification system currently. For the Government employee notifications, a mix of CSV uploads and contacts residing in the system is used. The current system maintains about 500 contacts, however, we want to plan for a complete upload of Government employees and interagency partners, which is where the 10,000 number comes from on the employee notification side.
Question #5 Pricing Attachment Table A- Please confirm that ATF requires this in a separate spreadsheet. Please clarify how contractor will propose out year pricing where price escalation exists for option periods. The current list does not reflect how to put option year pricing into the table.
Answer A separate spreadsheet is feasible. Please ensure all price escalations included within your pricing. Each option has been included please refer to CLINS 5 – 16, which represent the option periods.
Question #6 Pricing Attachment Table A- For product implementation services, it is assumed those will be part of CLIN 3 Set up Fees. Where would the contractor input base and out year program/project management fees to support the system and required QASP reporting and ATO updates as needed? This cost does not seem relevant to any of the CLINs listed in Attachment A template.
Answer This is a solicitation for a Software-as-a-Service (SaaS) requirement in the vendor’s hosted environment. We expect all program and project management fees to be included in the bid. The system will require an authority to operate (ATO). Due to the FedRAMP certification requirement, ATF anticipates that a majority of the work effort will be on the part of the ATF Information Security Systems Office inheriting controls from the FedRAMP system. Some technical consultation, production of diagrams of the system and confirming controls may be required.
Question #7 Would ATF consider a 1-week extension or at a minimum 3 business days after release of Question responses to allow for contractor to incorporate input from Questions?
Answer The Agency does not intend to further extend the proposal deadline.
File details come from the government source that posted it. Updated .