QAs RFI 842571563.pdf

Question 1

Regarding the subject RFI, is this an overhaul /modernization of the PBX to the cloud or trunks, or is it a 911 initiative only?

Answer: The D-ESINet can best be described as an enhancement to the overall voice infrastructure. The core voice services are not changing; however Next Gen 911 will be available once the initiative is completed.

Question 2

In order to provide realistic cost estimates, can DISA please provide sizing parameters for each distinct phase? Examples of helpful information would be parameters such as number of bases, population for each base (or total), busy hour call volumes (or daily averages), etc.

Answer: Please assume that there will be up to 8 instantiations of the D-ESINet infrastructure throughout the DISN. DISA believes it would be beneficial to have these products co-located with the new SoftSwtich platform. The system needs to be capable of processing NG911 location data for as many concurrent 911 calls as conceivably possible, DISA has routing responsibility for roughly 2.5 million numbers. It’s unlikely that all lines would dial 911 at the same time, but we must be properly sized to avoid any emergency services disruptions.

Question 3

Can DISA please confirm that the questions to Industry are not included as part of the three-page capability statement?

Answer: No, they are not.

Question 4

Can DISA please provide additional clarification regarding the initial call setup and routing of inbound 9- 1-1 calls? For example, should the vendor assume that for the purpose of this RFI 9-1-1 call ingress is limited to the DISA EVoIP telephone network and DoD 365 Teams? Does the solution need to interconnect with any commercial networks such as commercial mobile service providers that today account for 85%-90% of all 9-1-1 calls?

Answer: 911 call ingress can be from any DoD VoIP asset connected to NIPRNet. The EVoIP backbone is the only approved DoD VoIP carrier which includes DoD 365 Teams, however, please note it is not currently possible to program PIDF-LO information into Teams without some type of upgrade from Microsoft. The EVoIP environment is already interconnected with commercial networks via the VISP connection.

Question 5

The RFI states the intent of the service is to deliver NG911 calls to the appropriate DoD PSAP, however key functional elements of the NG911 NENA standard architecture are not depicted in the architecture.

Can DISA please provide additional clarification regarding ESRP, ECRF, Policy Routing Function, Legacy Network Gateway, etc. that are not currently depicted?

Answer: DISA is only responsible for the transport and processing of PIDF-LO information to make an appropriate PSAP decision, DISA is not responsible for the entire public safety ecosystem. DISA requests information regarding all the products necessary to ingest PIDF-LO and use it to make a cogent PSAP decision as well as the ability to deliver the PIDF-LO information to a PSAP in a way that allows any CAD system to receive it and display to the dispatcher.

Question 6

Can DISA please describe how multimedia requests for emergency services will ingress into the D-ESInet given the notional architecture?

Answer: Multimedia requests are outside the scope as DoD does not provide a 5G network of its own or mobile phones which are capable of video or text. DoD components currently own and operate traditional VoIP endpoints from companies such as Cisco, Polycom and Avaya.

Question 7

Can DISA please define the meaning of “IAW” acronym?

Answer: In Accordance With

Question 8

Is the expectation that the ESINET component (Yellow Segment in the Notional architecture) be contained in an IL5 Cloud environment, or can it be contained in a protected and secured Telecommunications Central Office?

Answer: D-ESINet will not be in a commercial cloud environment, it will be hosted in DISA facilities.

Question 9

Can DISA please articulate how Wireless initiated 911 calls are to be integrated into this environment and routed to the respective PSAP?

Answer: Wireless calls are outside the scope, wireless devices which are permitted onto DoD property are directly connected to commercial carrier networks, not the DISN.

Question 10

In the upper left corner of Figure 1 below, the LIS functional element is part of the ESInet (DISA) box. I think the question would be, is DISA looking for a LIS provider to provide i3 services for their onsite phone systems or is this outside of the scope of RFI?

Answer: DISA is under the impression that GIS services will need to be subscribed to properly determine the area of responsibility for a PSAP, however this is where we need assistance. The exact mechanism for how the PSAP is chosen from a mapping database is unknown.