---
title: Positron Viper
description: In-Synch
---
[Skip to content](https://kb.arms.com/in-synch/positron-viper#main-content)
English
Show submenu for translations
Open main navigation
Close main navigation
- English
Show submenu for translations
- Contact us
Contact us
How can we help you?
- There are no suggestions because the search field is empty.
1. [In-Synch](https://kb.arms.com/in-synch?hsLang=en)
2. [Knowledge base1](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en)
3. [Internal Wiki](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#internal-wiki)
# Positron Viper
No recent searches
Popular Articles
Sorry! nothing found for
### Positron Viper
Created by Russ Hartle, Modified on Tue, 11 Nov, 2025 at 9:57 AM by Russ Hartle
### Positron VIPER Ini Settings
### Positron VIPER General Call Field Mappings
The first column displays the customer facing fields from the Call Details window. The Second column displays the tags used from the XML file to populate the fields in the first column.
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
### Optional XML Parsing
Each company variation of the CAD interface has the ability to parse additional fields from the XML file directly into the RMS database. These fields can include: Persons, Addresses, and Vehicles. Not all companies provide every type of information. The use of these options are highly discouraged, as many times the information given in the XML file is incomplete. Incomplete XML information can lead to partial data being imported into the RMS. Incomplete data will require an agency to manually adjust these records to meet their specifications. Records not meeting the minimum requirements will be skipped.
**Address Parsing**
**Requirements:** To parse an address, the record must include the Street Number, Street Name, Street Type, and City. Address parsing will match existing records based on these requirements. If no matching address record is found, a new address record will be created. If the required fields are not met, the address will be displayed in the “Description” field on the Call Details window.
Fields that can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Vehicle Parsing**
**Requirements:** To parse a vehicle, the record must include the VIN or the License Plate Number and State, else the vehicle record is skipped. Vehicle parsing will match existing records based on these requirements. If no matching vehicle record is found, a new vehicle record will be created.
Other fields including Make, Model, and Color must match existing NCIC lists in the RMS, otherwise those portions of the record will be discarded. Vehicle parsing is not recommended as it can create many “shell” records that require the user to complete. Examples can include:
- A vehicle shell record just containing a VIN.
- A vehicle shell record just containing a license plate number and state.
- The XML file may contain a VIN, License Plate Number, State, Make, Model, and Color. If the Make, Model, and Color don’t match the existing NCIC values, a shell record just containing the VIN, License Plate Number, and State will be created. This example would require the user to view the dispatch record and manually match the Make/Model/Color to existing values in the RMS.
Fields that can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Person Parsing**
**Requirements:** To parse a person, the record must include the First Name, Last Name and DOB, else the person record is skipped. Person parsing will match existing records based on these requirements. If no matching person record is found, a new person record will be created.
Fields that can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Person Physical Description**
**Requirements:** When a person record is selected or created, any or all of the following fields can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Person License**
**Requirements:** The XML file must contain the driver’s license number. When a person record is selected or created, the following fields can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Person Phone**
**Requirements:** The XML file must contain the phone number. When a person record is selected or created, the following fields can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
**Person Role**
**Requirements:** The CADMonitor will read the \[PersonRole\] section of the ini file and look for a match/mapping, otherwise the role of “Involved” is used. When a person record is selected or created, the following fields can be parsed into the RMS:
**Tables can't be imported directly. Please insert an image of your table which can be found [here](https://kb.arms.com/in-synch/positron-viper).**
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Let us know how can we improve this article! \*
Feedback sent
We appreciate your effort and will try to fix the article
**X**
- [Release Notes](https://kb.arms.com/in-synch/release-notes?hsLang=en#main-content)
- [Version 4.8](https://kb.arms.com/in-synch/release-notes?hsLang=en#version-4-8)
- [Knowledge base3](https://kb.arms.com/in-synch/knowledge-base3?hsLang=en#main-content)
- [How To](https://kb.arms.com/in-synch/knowledge-base3?hsLang=en#how-to)
- [Knowledge base2](https://kb.arms.com/in-synch/knowledge-base2?hsLang=en#main-content)
- [Modules](https://kb.arms.com/in-synch/knowledge-base2?hsLang=en#modules)
- [Knowledge base1](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#main-content)
- [State Reporting](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#state-reporting)
- [Internal Wiki](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#internal-wiki)
- [State Specific Modules](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#state-specific-modules)
- [Release Notes](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#release-notes)
- [In-Synch RMS QuickStart Video Series](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#in-synch-rms-quickstart-video-series)
- [Error Messages](https://kb.arms.com/in-synch/knowledge-base1?hsLang=en#error-messages)
- [Knowledge base](https://kb.arms.com/in-synch/knowledge-base?hsLang=en#main-content)
- [Interfaces](https://kb.arms.com/in-synch/knowledge-base?hsLang=en#interfaces)
[](http://arms.com)
[mailto:email@email.com](mailto:email@email.com)
Copyright © 2026, End2End Public Safety