Capabilities

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

Overview

The Data Agent will read from the Pulsium Reporting SQL Database. To do this we need a user to connect.

Network Requirements: The server running the Data Agent should be able to connect to the CAD Reporting server over port 1433. This can be tested using PowerShell.

PowerShell Command:

Test-NetConnection -ComputerName {CAD Reporting Server name or IP} -Port 1433

Standard Data Fields

These are the standard data fields the Data Agent reads from Pulsium. The tables below show each GovWorx field and the Pulsium column it comes from. The Data Agent reads incidents from CALL_HISTORY by close time.

Note: Additional fields are considered enhancement requests.

Incident fields

GovWorx field	Pulsium source	Notes
Incident ID	`CALL_HISTORY.ATID`	CAD record key.
Incident Number	`CALL_HISTORY.ATID`
Case Number	`CALL_HISTORY.DR`
Incident Type	`CALL_HISTORY.CALL_TYPE`
Caller Number	`CALL_HISTORY.PHONE`
Caller Name	`CALL_HISTORY.CH_LNAME, CH_FNAME`	Last name, then first name, joined with a comma.
Agency	`CALL_HISTORY.AGENCY`
Agency Type	`CALL_HISTORY.SERVICE`
Incident Date	`CALL_HISTORY.UTC_CREATE`
Disposition	`DISPO.DESC_`	Matches DISPO.ATID to CALL_HISTORY.DSP.
Location	`CALL_HISTORY.LOCATION`
Priority	`CALL_HISTORY.PRIORITY`
Latitude	`CALL_HISTORY.LATITUDE`
Longitude	`CALL_HISTORY.LONGITUDE`
Call Position	`CALL_HISTORY.POD`
Call Taker ID	`CALL_HISTORY.OPR_NAME`
Call Taker Name	`CALL_HISTORY.OPR_NAME`
Call Source	`CALL_HISTORY.HRCVD`
Call Received Time	`CALL_HISTORY.UTC_CREATE`	The earliest CAD note timestamp setting replaces this with the earliest note time.
Call Pickup Time	`CALL_HISTORY.UTC_CREATE`
Closed At	`CALL_HISTORY.UTC_CLOSED`	The Data Agent reads incidents by close time.
Dispatch Queue At	`CALL_HISTORY.UTC_QUEUED`

Notes

GovWorx field	Pulsium source	Notes
Note Text	`CALL_HISTORY__REM_INFO.REMARKS`
Note By	`CALL_HISTORY__REM_INFO.REM_OPR`
Note Time	`CALL_HISTORY__REM_INFO.REM_MSEC`	The database stores this time in local time. The Data Agent converts it to UTC.

Responders and units

GovWorx field	Pulsium source	Notes
Unit Name	`UNIT_HISTORY.unit`	One responder for each unit on an incident.
Dispatched By	`UNIT_HISTORY.LOGNAME`	The first row for the unit.
Dispatched At	`UNIT_HISTORY.UTC_STAMP`	The earliest row with status 1.
Enroute At	`UNIT_HISTORY.UTC_STAMP`	The earliest row with status 5.
Arrived At	`UNIT_HISTORY.UTC_STAMP`	The earliest row with status 2.
Cleared At	`UNIT_HISTORY.UTC_STAMP`	The earliest row with status 3.

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 reporting database
`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 name*`	Text	Database Schema to read from
`First-run lookback in hours`	Number	How far back the first run looks for closed incidents, before the Data Agent has a saved position. Default: 2.
`Maximum lookback in hours`	Number	Caps how far back a stale cursor can reach so an idle or reconnected connector does not issue an oversized catch-up query. Default: 8.
`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

CAD Connector - Pulsium