ARMS Monitor911 Application

NENA stands for National Emergency Number Association. The NENA standard is enforced upon telephone carriers by the government, bringing about some conformity with regard to exchanging ANI-ALI data across platforms (such as from the telephony system server to the CAD server). 

The 911 Call window prompts the dispatcher with the parsed ANI-ALI caller data, enables the dispatcher to start a new CAD entry, or appends an existing CAD entry (i.e., existing Open Call), or cancel.

How does ARMS obtain the ANI-ALI caller data?

ARMS Monitor 911 can read the raw data flowing into the connection to the ARMS server and then allow the agency to create and implement the desired parsing of that raw data. Additionally, this gives the agency the ability to somewhat change with the times, as new telephony equipment is brought into production (i.e., the agency is not backed into a corner with non-modifiable ANI-ALI settings).

Through a connection from the ARMS server to the telephony system server (typically, a COM port / serial cable connection), the telephony system and the ARMS server continually “shake hands” to stay in touch for active monitoring of sudden bursts of ANI-ALI caller data that “spills” over into CAD. This data is sent to CAD by the telephony system, in NENA standard form, within a few seconds of the dispatcher answering the call. However, the caller data is not sent by the telephone system until the call has been answered.

In the image above, you can see portions of the ARMS Monitor 911 Configuration feature, which allows the agency administrator to view the raw “Read Data” and apply parsing commands to retrieve the correct data appropriate fields in ARMS.

After the agency administrator has completed and saved the Parse Parameters as desired (i.e., the “Trimmed Data”), the settings are saved and put to work so the dispatcher is receiving new 911 Call prompts using effectively parsed ANI-ALI caller data.

ARMS CAD saves a copy of the ANI-ALI caller data into the CAD >> Police Information field. As a result, the dispatcher or administrator can view the original content received from the telephony system.

From the Blog

  • Learn how modern RMS solutions streamline Use of Force reporting, enhance compliance, and protect law enforcement agencies from liability.

    The Evolution of Use of Force Reporting: How a Modern RMS Can Help

    Use of Force reporting has evolved significantly over the years, transforming from simple paperwork into a structured, compliance-driven process. When I first entered law enforcement, documenting Use of Force incidents was straightforward, often relying on a simple form and an officer’s word. But with legal precedents and the rise of modern Records Management Systems (RMS),…

    ,
  • Outdated public safety software carries hidden costs that impact efficiency, security, and budgets. Learn how modern solutions save money.

    The Hidden Costs of Outdated Public Safety Software

    In today’s rapidly evolving digital landscape, public safety agencies often cling to legacy software systems that seem affordable at first glance. However, beneath the surface, these outdated tools carry hidden costs that can strain budgets, disrupt operations, and expose agencies to significant risks. We’re here to delve into these less-obvious expenses and explains why modern…

    , ,