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 Justice Data Solutions (JDS) Data Agent Connector will query the PostgreSQL database with read-only access. Retrieved data is encrypted in transit and securely transmitted to AWS GovCloud, ensuring compliance with stringent security and regulatory requirements.

No CAD data is stored on the local server running the data agent.

Standard Data Fields

These are the standard data fields the Data Agent reads from Justice Data Solutions. The tables below show each GovWorx incident field and the JDS column it comes from. Source names are tdt_recman.callmaster columns unless the row says otherwise.

Note: Additional fields are considered enhancement requests.

Incident fields

GovWorx field	Justice Data Solutions source	Notes
Incident ID	`callmaster.id`	CAD record key.
Incident Number	`callmaster.callno`
Incident Type	`callmaster.calltype`
Caller Number	`phone.area, phone.local, phone.num`	Joined with dashes.
Caller Name	`person.firstname, person.lastname`	The caller record.
Agency	`agency.agencycode`
Agency Type	`agency.agencytype`
Incident Date	`callmaster.calldate, callmaster.timereceived`	Date and time the call was received.
Disposition	`callmaster.calldispocode`
Location	`addr.block, streetdir, street, streettype`	Uses callmaster.locationcode when the address record is empty.
Latitude	`callmaster.latitude`
Longitude	`callmaster.longitude`
Call Taker ID	`officer.badgeno`	The first five characters of the dispatcher badge number.
Call Taker Name	`person.firstname, person.lastname`	The dispatcher record.
Call Source	`callmaster.howreceived`
Closed At	`callmaster.cleardate, callmaster.timecleared`

Notes

GovWorx field	Justice Data Solutions source	Notes
Note Text	`callmaster.comment`	One note for each incident.
Note By	Call Taker Name	The dispatcher on the incident.
Note Time	Incident Date	The time the call was received.

Responders and units

GovWorx field	Justice Data Solutions source	Notes
Unit Name	`officer.badgeno`
Personnel ID	`officer.badgeno`
Enroute At	`callofficer.dispatchdate, timedispatched`
Arrived At	`callofficer.enroutedate, timeenrouted`
Cleared At	`callofficer.cleardate, timecleared`

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 IP for PostgreSQL database
`Username`	Text	PostgreSQL username
`Password`	Password	PostgreSQL password
`Database name`	Text	Named database in PostgreSQL
`Hours back to look for data`	Text	Hours back to look for data (default: 1). The query filters on the time the call was received, so a larger value picks up calls that close long after they are received.
`Query over a fixed time interval instead of hours back`	Toggle	Toggle will query over a fixed time interval instead of hours back, for backfilling historical data.
`Fixed interval: beginning time`	Text	Beginning time of the fixed interval (yyyy-MM-dd HH:mm, local server time). Shown when the fixed interval toggle is on.
`Fixed interval: end time`	Text	End time of the fixed interval (yyyy-MM-dd HH:mm, local server time). Shown when the fixed interval toggle is on.
`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.

CAD Connector - Justice Data Solutions (JDS)