RFI Q-A_W50S6Q24QA005.pdf
PDF 65 KB Posted
- Attached to
- Secondary Crash System
- Solicitation number
- W50S6Q24QA005
- Issued by
-
Department of the Army National Guard
About this file
This document is a Request for Information (RFI) for a federal contract opportunity titled "Secondary Crash System" under solicitation number W50S6Q24QA005. The requirements include installing a secondary crash net system to operate in accordance with AFMAN 13-204V2, and integrating the system with the existing Cisco Unified Call Manager (CUCM) and emergency mass notification system. The government is seeking a full installation rather than an upgrade to an existing system. The key information includes a description of the current primary and secondary crash systems, the required integration with the CUCM and emergency notification system, and the desired capabilities such as recording and the ability to support additional future endpoints. The RFI also includes a list of questions and answers between the government and potential offerors. The solicitation is a 100% small business set-aside, with a response due date of August 23, 2024.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI Q-A2_W50S6Q24QA005.pdf | ||
| SOW_Secondary Crash1.pdf |
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
W50S6Q24QA005 - RFI’s Dated 25 July to 07 August 2024
1. Are there any other documents available for this RFP other than the 2-page SOW?
a. AFMAN 13-204V2 4.2.2.1 and 4.2.2.3 referenced in SOW is available.
2. What are you currently using for your Primary and Secondary Crash System?
a. Primary Crash – Owned by Regional Airport (Forum Alert III)
b. Secondary Crash – Does not exist. 10 years ago we used the Forum Alert II
3. What Mass Notification System is the Secondary Crash System supposed to integrate with?
a. EMNS is Blackberry AtHoc IIM Server with two giant voice speakers for outside and with a VALCOM paging system for internal/external speakers.
4. Are you looking for an upgrade to an existing system or full replacement?
a. Full install. Does not currently exist.
5. Are you looking for a total SIP Solution or will analog endpoints be used?
a. Primarily SIP. If external ringers are needed in the future we have the ability to connect analog devices to the CUCM.
6. Will we be leveraging an existing phone system or switch, or is this a completely stand-alone solution?
a. Existing CUCM.
7. Will you be connected to the DSN in any way?
a. DSN is connected to the CUCM.
8. Is the solution required to be on the DoDIN/JITC APL?
a. Sent to 188th Cyber Surety for answer but would assume yes.
9. Is wiring in place for each conference system and all endpoints?
a. For endpoints that are VoIP phones – yes. As of now there are no additional requirements for external ringers.
10. How many total endpoints does the Secondary Crash system need to connect too?
a. The standard 9 locations listed in AFMAN13-204v2 and an additional 10 endpoints for future growth/external devices.
11. Can you describe each type of endpoint we’ll be required to connect to? (For example; 14 phones, 1 siren, 1 PA System, 5 Strobes, 8 doors, 1 gate)
a. For this contract it will be 10 VoIP phones.
12. Are there more than 1 set of preset emergency groups that could be called? (For example; a different set of numbers for a different emergency) If so, how many groups of numbers are there?
a. For the secondary crash would be one group. The goal would be to have a solution that allowed for multiple group calls through the CUCM.
W50S6Q24QA005 - RFI’s Dated 25 July to 07 August 2024
13. Will rack space, power, etc. be provided?
a. Possibly, if needed. Would need to know how much rack space is needed. Most solutions should be able to install software on the existing CUCM server.
14. Will you need us to provide phones? If so, how many? Will you need spares?
a. No.
15. How do you prefer the solution to be installed? Virtually, on your VMWare, or on our supplied 1U server installed in your network?
a. Virtually on our equipment.
16. Do you prefer a perpetual (capital expenditure) model or an Annual Licensed (operational expenditure) model?
a. Unknown, I would assume licensed.
17. Is there a technical person who is close to this project that we can speak with?
a. The KO can relay any questions pre-award & the COR/SME will be provided post-award.
18. Are quotes under NAICS 541519 (Information Technology Value Added Resellers) acceptable?
a. Yes. This solicitation is 100% small-business set aside.
19. Aside from the security requirements outlined in the SOW, are there any additional clearance requirements?
a. Nothing outside of normal base access. They will be escorted into our comm facility.
20. How many endpoints does the system connect to?
a. You are correct that there is usually a set number of end points and ours will follow the standard Fire Department, Weather, CE Readiness, Hospital/Medical Treatment Facility, Command Post, CE, Security Forces, Maintenance Operations Control Center, and Safety. With having the system flow through our CUCM we would like to have the ability to have extra endpoints (20) since it is not like most Primary Crash Systems where it is more restricted on how many end points.
21. Is the system required to open firehouse doors, or set off sirens and strobes?
a. No
22. Is there a question and answer period that we can submit questions?
a. RFI’s will be accepted until 20 August.
23. Will there be a site visit required?
a. Not at this time.
24. Can you help provide more information regarding the present system and what is required for the replacement system?
a. There is no current system in place completing this function. They will be connecting/utilizing the CUCM to meet the requirement.
File details come from the government source that posted it. Updated .