Validation email

The CAD Integration Report Summary email is sent to the specified emails after each Auto Tagging run to validate the results.

Stats summary

  • Number of CAD/RMS entries: Number of CFS records in the CAD/RMS file.
  • Number of valid CAD/RMS entries: Number of CFS records in the CAD/RMS file that meet all validation criteria.
  • Number of invalid CAD/RMS entries: Number of CFS records in the CAD/RMS file that fail to meet one or more of the validation criteria (for more details, see the report file).
  • Number of CAD/RMS entries that matched: Number of CFS records in the CAD/RMS file that match to one or more evidence.
  • Number of CAD/RMS entries that didn't match: Number of CFS records in the CAD/RMS file that didn't match any evidence.
  • Evidence matched upon upload: Evidence that was uploaded to Evidence.com, which matched a CAD/RMS entry. The corresponding CAD/RMS entry was contained on a previous CAD export.

CSV reports

Parser report/CAD export validation CSV

The CSV report details the results of the parsed CAD export file. Each entry in the CSV report is contained on the agency's CAD export.

  • Success: Valid entry: The entry was parsed correctly.
  • Error: Missing values: The entry is either missing required values (such as Event ID, Officer Badge ID, Officer Dispatched Datetime, or Officer Cleared Datetime), or the header of the export isn't formatted correctly.
  • Error: Invalid CAD event ID: The CAD Event ID in the entry is either in an invalid format, or doesn't match the specified CAD ID Auto-Tagging regex.
  • Error: Invalid RMS event ID: The RMS event ID in the entry is either in an invalid format, or doesn't match the specified Auto-Tagging RMS ID regex.
  • Error: Start or end datetime either invalid or duration between the two exceed threshold of 8 hours: The entry either has a zero duration, or the duration exceeds 8 hours. This error can also mean that the EDCA-specified datetime format is incorrect.
  • Error: Cannot find Evidence.com category that maps to CAD/RMS category: The category in the entry doesn't map to an agency's Evidence.com category. The category mapping must be updated to include the values in the Category column(s).
  • Error: Cannot find city that maps to CAD/RMS city: The city code in the entry doesn't map to a city.

Matched report

The Matched Report details the valid CAD entries and its matched evidence. Each entry in this report contains the CAD entry, the evidence metadata, any metadata added by Auto-Tagging, and the reason for the action.

Example: The last five columns are Added Categories, Added Tags, Added CAD/RMS ID, Added Location, and Match Reason. Added columns can be blank if that particular piece of metadata wasn't added.

For the Match Reason, the following values can occur:

  • E com ID wasn't defined: No ID on evidence.
  • E com ID matches the CAD/RMS ID: The ID on the evidence matched the ID from the CAD entry (this value implies a full update occurred).
  • E com already has a valid ID: The ID on the evidence already is valid, and is different than the CAD/RMS ID from the entry (this value implies nothing was done).
  • E com has an invalid ID: The ID on the evidence is invalid (this value implies a full update occurred).

Unmatched report

The Unmatched Report shows all CAD entries without matching videos, and why videos are missing.

Possible reasons:

  • Badge ID doesn't exist in Evidence.com: The officer doesn't have an active Evidence.com account. To properly correlate the video with the event, the Badge ID in the CSV file must match an officer's Badge ID in Evidence.com. The recording start time for an Axon video must fall between the dispatched time and the cleared time for a CSV file event CSV, per Badge ID.
  • CAD/RMS record has the same start and end time: The dispatched time and cleared time are identical. Axon can't match based on this information unless the video started when the dispatched or cleared time initiated.
  • CAD/RMS record didn't have any matching videos: No matching video is found for a CAD/RMS record in Evidence.com. The parser will look for the Badge ID in Evidence.com, then attempt to find recording start times which fall between the dispatched and cleared window. If nothing is found, then this error will appear in the read-only test run.

Filtered evidence report

The Filtered Evidence Report shows all evidence that was filtered because of configurable filtering options.