Capabilities
Capabilities | Supported |
Connector Capabilities | |
Read | Yes |
Backfill | Yes |
Bidirectional Capabilities | |
Incident Create | No |
Incident Update | No |
Narrative Update | No |
Overview
The Data Agent reads from the Peraton CAD Oracle database. It connects with a database user and reads the CAD event tables. To do this we need a read only user. On each run, the Data Agent reads incidents that closed inside the time window. The default window is the last 30 minutes. A fixed date range is available to backfill history.
Oracle Configuration Notes
To ensure a successful and secure connection, verify the following:
Firewall Access: Ensure the server hosting the GovWorx Data Agent can reach the Oracle database over the appropriate network and port (typically TCP 1521).
Minimum Permissions: The provided database user must have read-only access to the CAD tables. Write access is not required or recommended.
Service Name: Provide the Oracle service name, not the SID.
Troubleshooting Tips
Login Failed? Verify the database user is enabled and not locked out.
Timeout Errors? Check network routes and firewall rules.
Connection Refused? Ensure the host, port and service name match the Oracle listener.
Network Requirements: The server running the Data Agent should be able to connect to the CAD database server over port 1521. This can be tested using PowerShell.
PowerShell Command:
Test-NetConnection -ComputerName {CAD Database server name or IP} -Port 1521
Standard Data Fields
These are the standard data fields the Data Agent reads from Peraton. The Data Agent reads closed incidents. The tables below show each GovWorx incident field and the Peraton column it comes from. Source names are CAD.CAD_ROW_DBEVH columns unless the row says otherwise.
Note: Additional fields are considered enhancement requests.
Incident fields
GovWorx field | Peraton source | Notes |
Incident ID |
| CAD record key. |
Incident Number |
| |
Incident Type |
| |
Initial Incident Type |
| |
Agency |
| |
Agency Type |
| |
Priority |
| |
Incident Date |
| |
Call Received Time |
| Uses ENTRYDATE when empty. The earliest CAD note timestamp setting replaces this with the earliest note time. |
Location |
| |
Longitude |
| |
Latitude |
| |
Closed At |
| |
Caller Name |
| |
Caller Number |
| |
Call Position |
| The entry workstation. |
Call Taker ID |
| |
Call Source |
|
Notes
GovWorx field | Peraton source | Notes |
Note ID |
| |
Note Text |
| |
Note By |
| |
Note Time |
|
Responders and units
GovWorx field | Peraton source | Notes |
Unit Name |
| |
Personnel ID |
| Matches the unit to the incident. |
Dispatched By |
| |
Dispatched At |
| The Data Agent does not fill the status times yet. The status log date column is not confirmed. |
Enroute At |
| Same as Dispatched At. |
Arrived At |
| Same as Dispatched At. |
Cleared At |
| Same as Dispatched At. |
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 |
| Text | Host of the CAD Oracle database |
| Text | Oracle listener port. The Data Agent uses 1521 when this is blank. |
| Text | Oracle service name |
| Text | Database user |
| Password | Database password |
| Text | How far back the Data Agent looks for closed incidents on each run. Default: 00:30. |
| Toggle | Toggle will query over a fixed date range instead of time back, for backfilling historical data. |
| Text | Start of the fixed date range |
| Text | End of the fixed date range |
| Toggle | Toggle on reads the time range as UTC. Toggle off reads it as local server time. Default: on. |
| 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. |
Note: *: Required.
