Capabilities

Capabilities	Supported
Connector Capabilities
Read	Yes
Backfill	Yes
Bidirectional Capabilities
Incident Create	No
Incident Update	No
Narrative Update	No

Customers of this CAD may be able to use bidirectional capabilities through IntelliComm. See Bidirectional CAD Integrations.

Overview

The Data Agent will read from the Motorola PremierOne Report Data Warehouse (RDW). To do this we need a user to connect. We read from the following tables:

MV_Incident
MV_IncidentUnits
MV_IncidentUnitOfficer
MV_IncidentComment
MV_ClonedIncidents
MV_IncidentPerson
MV_IncidentAssociation

Standard Data Fields

These are the standard data fields the Data Agent reads from Motorola PremierOne. The Data Agent reads closed incidents. The tables below show each GovWorx incident field and the PremierOne column it comes from. Source names are MV_Incident columns unless the row says otherwise. With the Run Using Tables Instead of Views setting on, the Data Agent reads the matching RST_ tables.

Note: Additional fields are considered enhancement requests.

Incident fields

GovWorx field	Motorola PremierOne source	Notes
Incident ID	`RecordSerialNo`	CAD record key.
Incident Number	`IncidentNumber`	Views use ReportNumber when empty. The Use Report Number setting reverses the order and skips incidents with no report number. The Data Agent skips incidents with no number.
Incident Type	`IncidentTypeCode, ModifyingCircumstanceCode`	The format is Code/Modifier. The Use Initial Incident Type setting reads InitialIncidentTypeCode. The Data Agent skips incidents with no type and types in the NOT IN setting.
Initial Incident Type	`InitialIncidentTypeCode, InitialModifyingCircumstance`	Only with the Populate Initial Incident Type setting on. Views only.
Caller Number	`MV_IncidentPerson.Phone`	The primary caller. The Data Agent picks the person flagged IsPrimaryCaller, then sequence number 1, then the lowest RecordSerialNo. It keeps MV_Incident.CallerPhone when no caller person exists.
Caller Name	`MV_IncidentPerson.FirstName, LastName`	The primary caller, chosen as above. It keeps MV_Incident.CallerName when no caller person exists. The Use INVOLVED person's name setting fills a blank primary caller name from an INVOLVED person on the same incident. The Append caller relationship setting adds MV_IncidentPerson.Roles in parentheses.
Agency	`AgencyId`
Agency Type	`ReportingDistrictName`
Incident Date	`IncidentDate`
Disposition	`AllDispositionDescriptions`	Tables only: the Disposition source setting picks the column or the function.
Location	`Location, Apartment, Building, Floor, Subdivision, LocationDescription`	Joined with spaces. The Exclude Location Description setting removes the last part. Views only.
Priority	`CurrentPriorityKey`	Uses InitialPriorityKey when empty. Views only.
Latitude	`Latitude`
Longitude	`Longitude`
Call Position	`DeviceId`
Call Taker ID	`CreateUserId`	Tables read UserId.
Call Taker Name	`CreateUserName`	Tables read RSU_EUser_User.Common_Name and Surname.
Call Source	`CallSource`
Response Area	`AreaName`	The Use beat name setting reads BeatName. Views only. Tables read AreaName from RST_IM_Incident_Route_Current.
Call Received Time	`CallReceivedTime, TimeOffered, IncidentStartedDateTime`	Uses the first value that exists. The Time Offered and Incident Started settings change the order. Tables read TimeReceivedAtSwitch and TimeOffered from RST_E911_Calls_Current in place of CallReceivedTime. The earliest CAD note timestamp setting replaces this with the earliest note time.
Dispatch Queue At	`FirstUnitDispatchedTime`
Closed At	`RouteClosedTime`	The Data Agent reads incidents by this time.
Additional Context	`MV_IncidentHistory.TransactionDescription`	Only with the Load Premise Hazards setting on. Entries with type PREM/HAZ, joined with \|.
Related Incident	`MV_IncidentAssociation.IncidentKey`	Views only. Incidents that share an EventKey relate to each other. The first other incident fills Related Incident.
Related Incident Type	`MV_Incident.IncidentTypeCode, ModifyingCircumstanceCode`	Views only. The types of the other incidents that share the EventKey, joined with commas.

Notes

Source names are MV_IncidentComment columns. Tables read RST_IM_Incident_Comment.

GovWorx field	Motorola PremierOne source	Notes
Note ID	`IncidentCommentKey`
Note Text	`Comments`
Note By	`UserId`
Note Time	`DateCommented`
Caller address note	`MV_Incident.CallerAddress`	Only with the Add Caller Address setting on. Views only. The note text is Caller Address: followed by the address. The note author is System.
Call taker last incident type note	`MV_IncidentHistory.TransactionDescription, UserID, Timestamp`	Only with the Add Call Taker Last Incident Type setting on. Views only. The note text is Call Taker Last Incident Type: followed by the type, the user, and the time. The note author is System.

Responders and units

Source names are MV_IncidentUnits and MV_IncidentUnitOfficer columns. Tables read RST_IM_Dispatched_Unit_Current.

GovWorx field	Motorola PremierOne source	Notes
Unit Name	`MV_IncidentUnits.Callsign`
Personnel ID	`MV_IncidentUnitOfficer.PersonnelCode`	The person assigned to the unit.
Dispatched By	`MV_IncidentUnits.UserId`
Dispatched At	`MV_IncidentUnits.DispatchTime`	Uses OnSceneTime when empty.
Enroute At	`MV_IncidentUnits.EnrouteTime`
Arrived At	`MV_IncidentUnits.OnSceneTime`
Cleared At	`MV_IncidentUnits.ClearTime`

Data Agent Settings

To prepare for this connection, we need the following details. These are settings in the GovWorx Data Agent configuration for this connector. A toggle is an on/off switch in that configuration.

Setting	Type	Explanation
`Host*`	Text	Host of the P1 RDW
`Use Integrated Security`	Toggle	Toggle will enable the use of a domain service account that is configured to run the agent service as authentication to SQL server
`Username`	Text	Database user
`Password`	Password	Database password
`Database*`	Text	Database Schema to read from
`Encrypt SQL connection (adds 'encrypt=true')`	Toggle	Toggle will add encrypt=true to the SQL connection.
`Force NTLM authentication instead of Kerberos`	Toggle	Toggle will use NTLM authentication in place of Kerberos.
`Agencies`	Text	Comma separated agency IDs. The Data Agent reads only incidents from these agencies. Leave blank to read all agencies.
`Jurisdictions`	Text	Reserved. The connector does not read this setting.
`Use Report Number instead of Incident Number`	Toggle	Toggle will use the report number in place of the incident number. The Data Agent skips incidents with no report number.
`Use Time Offered for Call Received Time`	Toggle	Toggle will use TimeOffered as the first choice for Call Received Time.
`Use Incident Started DateTime for Call Received Time`	Toggle	Toggle will use IncidentStartedDateTime as the first choice for Call Received Time.
`Use Initial Incident Type for Incident Type`	Toggle	Toggle will use the initial incident type code in place of the current incident type code.
`Filter Out Cloned Incidents`	Toggle	Toggle will skip incidents that appear as a child in MV_ClonedIncidents. Views only.
`Incident Type (NOT IN)`	Text	Comma separated incident types to exclude. Use the full type as GovWorx shows it, for example CODE/MODIFIER. Case does not matter.
`MV_Incident view name override`	Text	Name of the view to read in place of MV_Incident. Views only.
`MV_IncidentUnits view name override`	Text	Name of the view to read in place of MV_IncidentUnits. Views only.
`MV_IncidentUnitOfficer view name override`	Text	Name of the view to read in place of MV_IncidentUnitOfficer. Views only.
`MV_IncidentComment view name override`	Text	Name of the view to read in place of MV_IncidentComment. Views only.
`MV_IncidentPerson view name override`	Text	Name of the view to read in place of MV_IncidentPerson. Views only.
`MV_IncidentAssociation view name override`	Text	Name of the view to read in place of MV_IncidentAssociation. Views only.
`Use beat name as response area (only applies when using views)`	Toggle	Toggle will use BeatName in place of AreaName for Response Area.
`Exclude Location Description from Location`	Toggle	Toggle will leave LocationDescription out of Location. Views only.
`Run Using Tables Instead of Views`	Toggle	Toggle will read the RST_ tables in place of the MV_ views. The view name settings do not apply. Personnel codes still come from MV_IncidentUnitOfficer.
`Tables: Disposition source ("column", "function", or leave blank to omit)`	Text	Tables only. Enter column to read RST_IM_Incident_Disposition_Current.DispositionCode. Enter function to run dbo.GetDispositionDescriptions. Leave blank to leave Disposition empty.
`SQL command timeout in seconds; overrides all queries including the 120s incident query (leave blank for per-query defaults)`	Number	Seconds to wait for each SQL query. The maximum is 600. Leave blank to use the built-in timeouts.
`Time back to look for incidents ([days.]hh:mm, default 01:00, 1 hour)`	Text	How far back each run looks for closed incidents.
`Query over a fixed interval instead of time back`	Toggle	Toggle will query over a fixed time interval instead of time back, for backfilling historical data.
`Fixed interval: Beginning time (yyyy-mm-dd hh:mm)`	Text	Beginning time of the fixed interval.
`Fixed interval: End time`	Text	End time of the fixed interval.
`Split query into time intervals no longer than (hh:mm) (leave blank to disable splitting)`	Text	Splits the query into chunks no longer than this. Leave blank to turn splitting off.
`Load Premise Hazards from MV_IncidentHistory`	Toggle	Toggle will add premise hazard entries from MV_IncidentHistory to Additional Context.
`Populate Initial Incident Type as a separate field`	Toggle	Toggle will fill the Initial Incident Type field from MV_Incident. Views only.
`Add Call Taker Last Incident Type as a note (requires console ID pattern)`	Toggle	Toggle will add a note with the last incident type change made from a call taker console. Needs the console ID pattern below. Views only.
`Call Taker Last Incident Type: Console ID pattern (SQL LIKE, e.g. CON[0-9][0-9] matches CON01, CON17, etc.)`	Text	SQL LIKE pattern that matches the console IDs of call taker consoles. The note is skipped when this is blank.
`Add Caller Address as a note`	Toggle	Toggle will add a note with the caller address from MV_Incident. Views only.
`Append caller relationship to Caller Name`	Toggle	Toggle will add the caller role from MV_IncidentPerson in parentheses after the caller name.
`Use INVOLVED person's name when the primary caller's name is blank`	Toggle	Toggle will use the name of an INVOLVED person on the same incident when the primary caller's name is blank. The phone number still comes from the primary caller. Only the INVOLVED role qualifies. The Data Agent never uses SUBJECT, VICTIM, or ADDL CALLER rows. When more than one INVOLVED person has a name, the Data Agent uses the lowest sequence number. The person view or table must expose the Roles and RecordSerialNo columns. If it does not, the Data Agent logs an error and uploads incidents without this fallback. If the INVOLVED person is not the caller, for example a witness entered first, that person's name becomes the caller name. Default: off.
`Use earliest CAD note timestamp for Received At`	Toggle	Toggle will use the earliest CAD note time as Call Received Time. Use it when the first note marks the start of the call better than the CAD pickup time. Call Pickup Time does not change. When no note has a time, Call Received Time stays as read from CAD. Default: off. This setting is on every CAD connector.

*: Required

Username and Password are required unless Use Integrated Security is on.

CAD Connector - Motorola PremierOne