Key Problems & Focuses
There’s more work to be done to ensure NG911 interoperability across all NG911 systems.
Room for Interpretation in the i3 Standard
Right now, vendors can interpret the i3 standard enough so that heterogeneous solutions aren’t truly interoperable. This means that there is no guarantee that one NG911 i3-compliant system will talk to another system from a different vendor. So while NG911 adoption continues to spread, these NG911 systems don’t necessarily work together like they should.
The Task Force will agree on key profiles that eliminate the vagueness of the i3 standard, working with all stakeholders including NENA and other relevant standards bodies. These updated standards will be widely available.
Lack of Conformance Testing
As the i3 standard is refined, and vendors adjust to the clarifications, the industry needs to know that these solutions will, in fact, work together BEFORE they are deployed live as the backbone of emergency communications. Right now, there is no testing available to ensure that:
- A NG911 system strictly adheres to the i3 standard (conformance testing)
- Two NG911 solutions can transfer digital/next-gen information via the spec as intended, without additional customization (interoperability)
- The entire NG911 ecosystem works as intended, from the initial 911 call to the first responder on scene (end-to-end testing)
The Task Force plans to develop scripts and tools that will test for those profiles and provide them for free to the widespread vendor community via open source. The Task Force also plans to create third-party test labs for testing compliance and will review the results with a reputable body.