| Agency: | City of Port Angeles |
|---|---|
| State: | Washington |
| Type of Government: | State & Local |
| NAICS Category: |
|
| Posted Date: | Apr 14, 2026 |
| Due Date: | May 12, 2026 |
| Solicitation No: | RFI-2026-16 |
| Original Source: | Please Login to View Page |
| Contact information: | Please Login to View Page |
| Bid Documents: | Please Login to View Page |
| Bid Number: |
RFI-2026-16
|
| Bid Title: |
Request for Information: Pencom 911/Jeffcom 911 CAD System Upgrade
|
| Category: | Public Works |
| Status: | Open |
|
| Item Number | Module/Description of Requirement | Complies | Does not Comply | Comments |
|---|---|---|---|---|
| CAD Interfaces | ||||
| E911 | ||||
| 1 | The proposed solution shall include an interface to the 911 service provider, Intrado Power 911, to automatically populate CAD calls with 911 information when selected by dispatcher. | |||
| 2 | The proposed solution should have the ability to receive the raw spill data from the 911 service and import and properly parse it into the CFS via a serial or IP connection. | |||
| 3 | The proposed solution should have the ability to intelligently handle ANI/ALI rebids through the interface. | |||
| 4 | The proposed solution should have the ability to geoverify the E911 imported address immediately upon transfer. | |||
| 5 | The proposed solution should have the ability to determine a physical address from X/Y coordinates imported from the E911 phone system. | |||
| 6 | The proposed solution should have the ability to transfer E911 call receipt time to CAD to track E911 time stamps. | |||
| 7 | The proposed solution should have the ability to plot incoming E911 calls on the CAD and Mobile application map. | |||
| 8 | The E911 interface should include as part of the CAD incident wireless phase 1 and phase 2 information. | |||
| 9 | The proposed solution should have Next Generation 911 Capabilities | |||
| Zetron Max-D | ||||
| 10 | The proposed solution must include an interface to Zetron Max-D for station and unit toning. | |||
| EMS Reporting | ||||
| 11 | The proposed solution should include an interface with the ImageTrend for Patient Care Reporting. | |||
| ProQA/Priority Dispatch |
Item
Module/Description of Requirement Complies Does not Comply Comments
Number
CAD Interfaces
E911
The proposed solution shall include an interface to the 911 service provider,
1 Intrado Power 911, to automatically populate CAD calls with 911 information
when selected by dispatcher.
The proposed solution should have the ability to receive the raw spill data from
2 the 911 service and import and properly parse it into the CFS via a serial or IP
connection.
The proposed solution should have the ability to intelligently handle ANI/ALI
3
rebids through the interface.
The proposed solution should have the ability to geoverify the E911 imported
4
address immediately upon transfer.
The proposed solution should have the ability to determine a physical address
5
from X/Y coordinates imported from the E911 phone system.
The proposed solution should have the ability to transfer E911 call receipt
6
time to CAD to track E911 time stamps.
The proposed solution should have the ability to plot incoming E911 calls on
7
the CAD and Mobile application map.
The E911 interface should include as part of the CAD incident wireless phase 1
8
and phase 2 information.
9 The proposed solution should have Next Generation 911 Capabilities
Zetron Max-D
The proposed solution must include an interface to Zetron Max-D for station
10
and unit toning.
EMS Reporting
The proposed solution should include an interface with the ImageTrend for
11
Patient Care Reporting.
ProQA/Priority Dispatch
| Page Gate | ||||
|---|---|---|---|---|
| 13 | The proposed solution shall include and interface with page gate to notify units of related CAD calls. | |||
| Active911/HipLink | ||||
| 14 | The proposed solution should have the ability to ability to interface with Active911 and HipLink via SNPP for alerting of call information to mobile devices. | |||
| Fire RMS - ESO/ERS | ||||
| 15 16 | The proposed solution must include an interface to ERS/ESO that will send CAD call information to the Fire RMS. The proposed ERS/ESO interface should include the import or viewing of PrePlan and other information in CAD. | |||
| RapidSOS | ||||
| 17 | The proposed solution must include an interface to Rapid SOS for caller location information. | |||
| NOAA | ||||
| 18 | The proposed solution must include an interface to NOAA to display live weather stream information. | |||
| ASAP to PSAP | ||||
| 19 | The proposed solution should include an option to interact with another tenant. | |||
| FirstDue | ||||
| 20 | The proposed solution must include an interface to FirstDue that will send CAD call information for Fire agencies. | |||
| RMS Interfaces | ||||
| SECTOR/CITATIONS | ||||
| 21 | The proposed solution must have the ability to export form data from the RMS module system into the state SECTOR (accident/Citation) system. |
The proposed solution shall include an interface to ProQA/Paramount (that is
12
certified by Priority Dispatch) for all disciplines (law, fire and EMS)
Page Gate
The proposed solution shall include and interface with page gate to notify units
13
of related CAD calls.
Active911/HipLink
The proposed solution should have the ability to ability to interface with
14 Active911 and HipLink via SNPP for alerting of call information to mobile
devices.
Fire RMS - ESO/ERS
The proposed solution must include an interface to ERS/ESO that will send CAD
15
call information to the Fire RMS.
The proposed ERS/ESO interface should include the import or viewing of
16
PrePlan and other information in CAD.
RapidSOS
The proposed solution must include an interface to Rapid SOS for caller
17
location information.
NOAA
The proposed solution must include an interface to NOAA to display live
18
weather stream information.
ASAP to PSAP
The proposed solution should include an option to interact with another
19
tenant.
FirstDue
The proposed solution must include an interface to FirstDue that will send CAD
20
call information for Fire agencies.
RMS Interfaces
SECTOR/CITATIONS
The proposed solution must have the ability to export form data from the RMS
21
module system into the state SECTOR (accident/Citation) system.
| 22 | The proposed solution must have the ability to transfer ACCESS/NCIC query information from the CAD/Mobile to the SECTOR Application if needed | |||
|---|---|---|---|---|
| 23 | The proposed solution must have the ability for the vendor to stay current with code changes mandated by the State Accident and Citations and update the RMS software accordingly to accommodate changes. | |||
| 24 | The proposed solution must have the ability to accommodate exports from multijurisdictional agencies | |||
| KARPEL | ||||
| 25 | The proposed solution must include an interface to Karpel. | |||
| LinXs | ||||
| 26 | The proposed solution must have the ability to interface with the Regional data hub for LinXs | |||
| 27 | The proposed solution should have the ability to import records and/or photos from LinXs | |||
| Livescan | ||||
| 28 | The proposed solution must include an interface to DataWorks+ to transfer booking information to Livescan. | |||
| 29 | The proposed solution must have the ability to perform Livescan on just a name record | |||
| 30 | The proposed solution must have the ability to import DL photos from Livescan into the RMS system | |||
| AXON - Body Worn Cameras | ||||
| 31 | The proposed solution should include the ability to interface with the Axon to provide hyperlinks to Body Worn Camera video in CAD calls and RMS incidents. | |||
| CARFAX | ||||
| 32 | The proposed solution should include an interface to CARFAX |
The proposed solution must have the ability to transfer ACCESS/NCIC query
22 information from the CAD/Mobile to the SECTOR Application if needed
The proposed solution must have the ability for the vendor to stay current with
code changes mandated by the State Accident and Citations and update the
23
RMS software accordingly to accommodate changes.
The proposed solution must have the ability to accommodate exports from
24
multijurisdictional agencies
KARPEL
25 The proposed solution must include an interface to Karpel.
LinXs
The proposed solution must have the ability to interface with the Regional data
26
hub for LinXs
The proposed solution should have the ability to import records and/or photos
27
from LinXs
Livescan
The proposed solution must include an interface to DataWorks+ to transfer
28
booking information to Livescan.
The proposed solution must have the ability to perform Livescan on just a
29
name record
The proposed solution must have the ability to import DL photos from Livescan
30
into the RMS system
AXON - Body Worn Cameras
The proposed solution should include the ability to interface with the Axon to
31
provide hyperlinks to Body Worn Camera video in CAD calls and RMS incidents.
CARFAX
The proposed solution should include an interface to CARFAX
32
| LexisNexis | ||||
|---|---|---|---|---|
| 33 | The proposed solution must include an inteface to LexisNexis Coplogic Online Crime Reporting | |||
| 34 | The proposed solution must include an inteface to LexisNexis Coplogic Online statistics | |||
| JMS Interfaces | ||||
| Livescan | ||||
| 35 | The proposed solution must include an interface to transfer booking information to the DataWorks+ Livescan system. | |||
| 36 | The proposed solution and interface must have the ability to perform Livescan on just a name record | |||
| 37 | The proposed solution and interface must have the ability to import DL photos from Livescan into the JMS system | |||
| Appriss VINE | ||||
| 38 | The proposed solution must have the ability to interface with VINE to send booking information. | |||
| Commissary (Trinity or Swanson) | ||||
| 39 | The proposed solution must have the ability to interface with a commissary vendor of the agency's choosing and send inmate information for ordering, receipting, billing, fees and inmate account. | |||
| Homewav | ||||
| 40 | The proposed solution must an interface to Homewav Inmate Phone System. | |||
| Guard1 | ||||
| 41 | The proposed solution must include an interface to Guard1 for Inmate Tracking | |||
| Northpointe |
LexisNexis
The proposed solution must include an inteface to LexisNexis Coplogic Online
33
Crime Reporting
The proposed solution must include an inteface to LexisNexis Coplogic Online
34
statistics
JMS Interfaces
Livescan
The proposed solution must include an interface to transfer booking
35
information to the DataWorks+ Livescan system.
The proposed solution and interface must have the ability to perform Livescan
36
on just a name record
The proposed solution and interface must have the ability to import DL photos
37
from Livescan into the JMS system
Appriss VINE
The proposed solution must have the ability to interface with VINE to send
38
booking information.
Commissary (Trinity or Swanson)
The proposed solution must have the ability to interface with a commissary
39 vendor of the agency's choosing and send inmate information for ordering,
receipting, billing, fees and inmate account.
Homewav
40 The proposed solution must an interface to Homewav Inmate Phone System.
Guard1
The proposed solution must include an interface to Guard1 for Inmate Tracking
41
Northpointe
| Odyssey | ||||
|---|---|---|---|---|
| 43 | The proposed solution must include an inteface to Odyssey Court solution. | |||
| Multiple Applications | ||||
| NCIC/ACCESS | ||||
| 44 | The proposed system should include an interface to the state ACCESS/NCIC system. | |||
| 45 | The proposed solution must have the ability for authorized users to run NCIC queries from: * CAD * Mobile * RMS | |||
| 46 | The proposed solution must have the ability to restrict access to run NCIC queries to authorized users and/or user groups. | |||
| 47 | The proposed solution must have the ability to alert user of NCIC returns. | |||
| 48 | The proposed system should allow NCIC query returns to populate Master Name and Master Vehicle records: * CAD * Mobile * RMS |
The proposed solution should include an interface to Northpointe Inmate
Classification System. Note - If the proposed solution includes its own inmate
42
classification system that meets the functional requirements of the agency,
this interface may not be needed.
Odyssey
The proposed solution must include an inteface to Odyssey Court solution.
43
Multiple Applications
NCIC/ACCESS
The proposed system should include an interface to the state ACCESS/NCIC
44
system.
The proposed solution must have the ability for authorized users to run NCIC
queries from:
45 * CAD
* Mobile
* RMS
The proposed solution must have the ability to restrict access to run NCIC
46
queries to authorized users and/or user groups.
47 The proposed solution must have the ability to alert user of NCIC returns.
The proposed system should allow NCIC query returns to populate Master
Name and Master Vehicle records:
* CAD
48
* Mobile
* RMS
| 49 | The proposed system should provide a list of all state/NCIC queries which have been run and the associated returns, filterable by date, query type, user and/or workstation. The proposed solution must include an interface to the State and NCIC systems to include all entry, modify and query transactions. The State/NCIC interface must utilize masks/formatted screens for ease of entry of data. The State/NCIC interface must include the ability to query persons and vehicles from the command line in CAD. The proposed solutions State/NCIC interface must allow for a single point of entry (i.e submit entries and queries directly from RMS forms) in order to | |||
|---|---|---|---|---|
| 50 | ||||
| 51 | ||||
| 52 | ||||
| 53 | ||||
| Lexipro | ||||
| 54 | The proposed solution must have the ability to interface with LexiPro to provide SOP access in the field if allowed. | |||
| 3rd Party Hardware | ||||
| 55 | The proposed solution must have the ability to interface with Axon body cameras and Evidence.com | |||
| 56 | The proposed solution must have the ability to interface with Zebra handheld evidence scanners. | |||
| Legacy Data Conversion | ||||
| 57 58 | The proposed solution shall include CAD Legacy Data Conversion. The proposed solution shall include Legacy RMS Data Converion. | |||
| 59 | The proposed solution shall include Legacy JMS Data Conversion. | |||
| Web Interface |
The proposed system should provide a list of all state/NCIC queries which have
49 been run and the associated returns, filterable by date, query type, user and/or
workstation.
The proposed solution must include an interface to the State and NCIC systems
50
to include all entry, modify and query transactions.
The State/NCIC interface must utilize masks/formatted screens for ease of
51
entry of data.
The State/NCIC interface must include the ability to query persons and vehicles
52
from the command line in CAD.
The proposed solutions State/NCIC interface must allow for a single point of
53
entry (i.e submit entries and queries directly from RMS forms) in order to
Lexipro
The proposed solution must have the ability to interface with LexiPro to
54
provide SOP access in the field if allowed.
3rd Party Hardware
The proposed solution must have the ability to interface with Axon body
55
cameras and Evidence.com
The proposed solution must have the ability to interface with Zebra handheld
56
evidence scanners.
Legacy Data Conversion
57 The proposed solution shall include CAD Legacy Data Conversion.
58 The proposed solution shall include Legacy RMS Data Converion.
59 The proposed solution shall include Legacy JMS Data Conversion.
Web Interface
| 60 | The proposed solution must have the ability to select and post specified data elements to a webpage for public information. (Missing persons, Warrants, Sheriff Sales, community events, etc.) | |||
|---|---|---|---|---|
| 61 | The proposed solution must have the ability to export specified data elements to table to be posted to website | |||
| 62 | The proposed solution must include the ability to allow for public facing incident reporting and call for service requests via a web interface. |
The proposed solution must have the ability to select and post specified data
60 elements to a webpage for public information. (Missing persons, Warrants,
Sheriff Sales, community events, etc.)
The proposed solution must have the ability to export specified data elements
to table to be posted to website
61
The proposed solution must include the ability to allow for public facing
62
incident reporting and call for service requests via a web interface.
With Free Trial, you can:
You will have a full access to bids, website, and receive daily bid report via email and web.
Solicitation Close Date: 08/07/26 Title: RFQQ K14050 Transient Elastography Device Ref #:K14050 Contact:
State Government of Washington
Bid Due: 8/07/2026
Contract SR 519, Seattle Trm - Terminal Electrification Contract summary Build the necessary
State Government of Washington
Bid Due: 11/23/2026
Solicitation Close Date: 03/24/28 Title: Market Search - ECY - Clark County Ref
State Government of Washington
Bid Due: 3/24/2028
Follow Brand Name: Durabuilt Medical PMT 8000 HLTE Platinum Series Fluoroscopy Tables (with
DEPT OF DEFENSE
Bid Due: 7/30/2026