Skip to main content

Event Matching

Learn about the CommsCoach Matching Engines

Alex Montgomery avatar
Written by Alex Montgomery
Updated over 8 months ago

Overview

CommsCoach supports multiple matching engines to accommodate different agency needs and configurations. Currently available engines are 'Default' and 'CommsCoach V2'. Each engine can be configured with different matching strategies to effectively map CAD Incidents to Audio calls and dispatch radio traffic.

Matching Engine Selection

  • Default Engine: The original matching engine, best suited for simple configurations and basic workstation/calltaker matching

  • CommsCoach V2: Enhanced engine with additional matching options and configurable time buffers, recommended for complex setups and agencies requiring radio matching

Call Audio and CAD Incidents Matching

Depending on your selected engine, there are several ways to match Voice Logging Recorder (VLR) files to CAD incidents:

Default Engine Options:

By Workstation

  • Ideal for centers without specific phone logins

  • Matches based on channel/position/workstation identifier

  • Uses VLR position → CAD workstation mapping (configured at https://app.govworx.net/settings/position-mapper)

  • Looks for incidents at matched positions within the configured time window

By Calltaker

  • For VLRs with user login capabilities

  • Uses unique user identifier stored in call recording

  • Matches based on CommsCoach user VLR Identifier attribute

  • Links to incidents handled by that call taker within the time window

CommsCoach V2 Additional Options:

  1. Time Only Matching

    • Ideal for low-volume agencies

    • Matches incidents and calls purely by timestamp

    • Configurable time buffers for matching window

    • No requirement for workstation or agent matching

  2. Only Create Events for Incidents in Incident Type Variable Mapping

    1. What this setting does: When enabled, GovWorx will only create events for CAD Incident records where the incident type is included in your Incident Type Variable Mapping configuration.

    2. When to use this setting: Enable this setting if:

      • Your CAD system supports multi-agency or linked incidents

      • You want to ensure events are created from the incident record with the most relevant incident type

      • You need to filter out certain incident types that shouldn't generate events

    3. Important! Before enabling this setting, make sure your Incident Type Variable Mapping is properly configured with all relevant incident types. Any incident with a type not listed in the mapping will be ignored when this setting is active.

Radio Transmissions and CAD Incidents

Default Engine:

  1. Filters audio files to radio recording channels

  2. Transcribes files

  3. Loads incidents around transmission time

  4. Searches for incident numbers in radio transcription

  5. Associates dispatcher (by Personnel ID) who handled the units

CommsCoach V2 Enhanced Radio Matching:

  1. Examines incident open and close time window

  2. Identifies all radio transmissions within that period

  3. Filters channels by agency if agency is specified

  4. Attempts to match on unit

  5. Attempts a 'Classification'

Configuring Radio Channels in CommsCoach V2

To set up radio channels, navigate to the Advanced Radio Matching section. For each channel you need to configure:

  1. Channel Name: Enter your VLR radio traffic channel identifier. You can use wildcards (like 'RADIO-*') to match multiple similar channels with a single entry.

  2. Channel Purpose: Add a description explaining how the channel is used and what types of transmissions typically occur on it. This helps with system documentation and maintenance.

  3. Transcription Focus Words: Input key words that the transcription engine should pay special attention to on this channel. This improves transcription accuracy for critical terms.

  4. Agency Assignment: Specify which agencies use this channel. You can assign multiple agencies by pressing enter after each agency name. This is particularly useful for multi-agency setups and ensures transmissions are matched to the correct agency's incidents.

Remember to click "Save Changes" after configuring each channel. You can add additional channels using the "+ Add Channel" button in the top right corner.

Radio Unit Mapping (OPTIONAL)

Both engines support unit mapping when CAD unit identifiers differ from radio callouts (e.g., "E1" in CAD vs "Engine 1" on radio). This can be configured in the CAD To Radio Units mapping table.

This mapping is very important for the default matching engine. In CommsCoach V2 Engine the mapping is shared with the AI to help reason and match transmissions.

Did this answer your question?