RFI_Emergency Alert Notification System (EANS).docx
DOCX document 263 KB Posted
- Attached to
- IRS Emergency Alert Notification System (EANS)
- Solicitation number
- 24-32-A-PMO-OITA
About this file
This document is a Request for Information (RFI) issued by the Internal Revenue Service (IRS) for an Emergency Alert Notification System (EANS) for the Senior Commissioner's Representative and Continuity of Operations (SCR-CO). The IRS is seeking information from vendors who can provide an EANS solution that delivers mass notifications and employee accountabilities for all IRS employees.
The RFI requests responses in two parts: Part I seeks company profile information, and Part II seeks vendor responses to specific capability questions, including pricing estimates, experience, and ability to meet the functional and operational requirements outlined in the attached Statement of Work. Responses are due by September 25, 2024 and should be submitted to the designated points of contact. This RFI is for information gathering purposes only and is not a solicitation for proposals. The government reserves the right to use any non-proprietary information received in a future solicitation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 1_EANS_SOW.pdf | ||
| Attachment 2_EANS_RFI Response Template.xlsx | XLSX spreadsheet |
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
Internal Revenue Service (IRS) Emergency Alert Notification System (EANS) Senior Commissioner’s Representative and Continuity of Operations
(SCR-CO)
August 30, 2024
Low-Code/No-Code Platform Delivery and Business Process Support RFI | ii Introduction This is a Request for Information (RFI) - hereinafter Notice. This is NOT a solicitation for proposals, proposal abstracts, request for bids or quotations, nor a promise to issue a solicitation in the future. The purpose of this RFI is for the Government to obtain knowledge and information for project planning purposes only.
No proprietary, classified, confidential, or sensitive information should be included in responses to this Notice, unless otherwise appropriately marked by the Respondent. The Government reserves the right to use any non-proprietary technical information received in response to this Notice in any resultant solicitation(s). Do Not Submit any Proposals / Offers / Quotes in response to this Notice.
Request for Information Number: 24-32-A-PMO-OITA Project Title / Short Description: IRS - Emergency Alert Notification System (EANS) for the Senior Commissioner’s Representative and Continuity of Operations (SCR-CO) PSC or FSC Code: DA10 IT and Telecom—Business Application/Application Development Software as a Service NAICS Codes:
541519 Computer Systems Design and Related Services
Release Date: August 30, 2024 Response Date: September 25, 2024 Primary Point of Contact and Contact Information:
Name: Sandra R. Anderson Title: Acquisition Government Facilitator Email: sandra.r.anderson@irs.gov Secondary Point of Contact and Contact Information:
Name: Shelley M. Broadnax Title: Management & Program Analyst; BOD Operations Team Email: shelley.m.broadnax@irs.gov
PLEASE SEND RESPONSES TO BOTH THE PRIMARY AND SECONDARY POC.
IRS - Emergency Alert Notification System (EANS) At a summary level, the Government has interest in and is seeking information regarding the capability of firms who can provide services pertaining to the Emergency Alert Notification System (EANS) for the Senior Commissioner’s Representative and Continuity of Operations (SCR-CO) Description of Services The Internal Revenue Service (IRS) is looking for vendors who can deliver an Emergency Alert Notification System (EANS) solution that provides mass notifications to all IRS employees. The Contractor shall also deliver an EANS solution that provides accountabilities for all employees.
The Functional and Operational requirements for the EANS are described in the Statement of Work (SOW), attachment 1.
RFI Instructions Responses to this RFI are requested in two (2) parts and must be submitted using Attachment 2 RFI Response Template.
Part I Company Profile Information - IRS seeks company profile information about the firms that provide services positioned to address the requirements discussed in the RFI and SOW.
Part II Capability - IRS seeks Industry responses to specific questions. Do not include any support documentation for any company other than your own. This is an analysis of your company’s abilities.
Part I: Company Profile Information Responders to this Notice must provide the following company information:
1. Company Name and Address
2. Company technical Point of Contact (POC) and Contract Lead information to include name, title, telephone number, and email address.
3. Applicable NAICS (North American Industry Classification System) Code
4. List active governmentwide contracts that your company has been awarded (GWACs, IDIQs, and BPAs – include applicable SIN)
5. Identify Business Classification / Socio-Economic Status (e.g., large, small, 8(a), women owned, hub-zone, SDB, Service-Disabled Veteran Owned)
6. Identify Subcontracting / partnering / teaming possibilities.
7. Identify current FedRAMP classification level.
Part II: Capability Responses to this Notice must include the following:
Pricing
1. Provide a rough order of magnitude for a potential solution of this type, relative to the following:
a. Less than $1M
b. Between $1M and $5M
c. More than $5M
2. What is a ballpark estimated price to successfully deliver these requirements?
Experience / Expertise
1. Describe your company’s level of experience and qualifications to provide the services in the attached Statement of Work (SOW) (i.e., business-led delivery methodology, user centered design, configurations, testing, implementation, training etc.)
2. Provide three examples of your company’s experience with projects similar in size, scope, and complexity to the work outlined within the SOW. The examples can be government or relevant commercial experience.
3. If you have a Capability Website, please provide the link. (optional)Provide summary background on any existing innovative solutions you have deployed in government or industry addressing this or a similar type of requirement.
4. Does the Draft Requirements Document contain sufficient information that would enable you to adequately respond to an RFP?
If “No,” please identify what areas within the SOW need to be refined, expanded upon, or otherwise clarified for your company to better propose on any resulting solicitation. (Your response should indicate, where applicable, the specific paragraph, page, or identifying element).
5. Are there any software-infrastructure dependencies or specialized integration software required for the installation / deployment that should be addressed in the SOW (e.g., Operating System)?
If yes, please explain.
6. Describe your company’s ability to create new solutions quickly, securely, and consistently by leveraging cloud infrastructure software, such as Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS) to provide efficient, cost-effective, secure, and scalable technologies. Examples can include replacing custom-built legacy applications with industry-standard, modern technologies to reduce the technology footprint and operating costs.
7. Describe your company’s ability to meet the requirements in the attached SOW. Specifically, are you able to provide solutions to the Functional and Operational requirements stated in the SOW?
8. If you have a Capability Website, please provide the link. (optional)
9. Please provide a Capability Statement.
10. Optional Feedback: Please provide any feedback or questions you may have related to this requirement and the Draft Requirements Document. This section is only for questions or feedback to the Agency about this requirement and to further expand on any responses provided above.
Terms and Conditions regarding this Notice This Notice does not obligate the Government to award a contract or otherwise pay for the information provided in response. All costs associated with responding to this Notice are solely at the responding party's expense. The Government reserves the right to use information provided by respondents for any purpose deemed necessary and legally appropriate. Further, the Government may contact the vendor for additional information regarding the information submitted as part of this market research effort. Any organization responding to this notice should ensure that its response is complete and sufficiently detailed to allow the Government to determine the organization’s qualifications to perform the work. Respondents are advised that the Government is under no obligation to acknowledge receipt of the information received or provide feedback to respondents with respect to any information submitted. After a review of the responses received, a pre-solicitation synopsis and solicitation may be published in Government Point of Entry or other similar source (e.g., GSA E-buy). However, responses to this notice will not be considered adequate responses to a solicitation.
Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract or agreement. The Government will not be obligated to pursue any particular acquisition alternative as a result of this notice. Responses to the notice will not be returned. Not responding to this notice does not preclude participation in any future solicitation if one is issued.
No proprietary, classified, confidential, or sensitive information should be included in responses to this Notice, unless otherwise appropriately marked by the Respondent. The Government reserves the right to use any non-proprietary technical information received in response to this Notice in any resultant solicitation(s).
Do Not Submit any Proposals/Offers in response to this Notice.
Thank you for your response to this Request for Information.
Technology Strategy and Management Support Services RFI | 1 image1.png image2.png
File details come from the government source that posted it. Updated .