Future Automation
Washington State Data Exchange for Public Safety
WADEPS is committed to automating the data ingestion process and is actively working with public safety software vendors to ensure a smooth transition. Automation will further reduce duplicative data entry and improve efficiency for law enforcement agencies.
Collaboration is Key
Achieving automation requires collaboration and coordination between WADEPS, law enforcement agencies, and, of course, commercial software vendors. Building lasting partnerships is crucial to achieving the goal of providing accurate and complete policing data to support transparency and accountability across the state.
Phased Approach
Ensuring data quality and compliance with state regulations
Phase I: Manual Data Ingestion
Agencies, dispatch centers, and commercial public safety software vendors may use smart CSV templates to upload required use-of-force data as well as monthly incident-level CAD data via batch processes, or agencies may opt to use the WADEPS web application to report use-of-force incidents individually in conjunctions with monthly CAD data uploads.
Phase II: Automation Tools
Agencies, dispatch centers, and commercial public safety software vendors may incorporate WADEPS-provided data schema and validation rules to enable the automated transfer of incident-related CAD and use-of-force data to the WADEPS exchange.
Why Automation Will Take Time
WADEPS is committed to developing a solution that works seamlessly for public safety software vendors and law enforcement agencies, does not add administrative burden, and which maintains data integrity.
- It is not a “one-size-fits-all” solution
Forcing every agency to use the same system would limit their flexibility and might not meet the unique needs of each department. - WADEPS is vendor agnostic
The law only requires a small portion of vast amount of incident data agencies collect be provided to WADEPS, so it’s important agencies are able to use the systems and vendors that work best for them. - Connection is key
WADEPS has built tools for automation, but it will be up to vendors to integrate them into their software. Think of it like building a bridge: WADEPS has built one side and vendors will need to connect their side for cars (or data) to cross. It requires planning, development, and testing by the agency and the vendor. - Updating software takes time
Imagine having to rewire your house while still living in it! Vendors need to carefully update their systems without disrupting service for the law enforcement agencies that rely on them.
WADEPS will continue work with public safety software vendors to make the integration as quick and smooth as possible. This collaborative approach ensures agencies can retain the systems they need while contributing to a more transparent and accountable statewide system.
Vendors and Automation
Currently, WADEPS is aware of several vendors who are working to integrate Washington’s new reporting requirements into their systems, paving the way for increased efficiency and data accuracy. We anticipate more vendors will add this capability in the future.
| Company Name | RCW Compliant | Automated Solution |
|---|---|---|
| SmartForce | Yes | In progress |
| Lexipol | Yes | In progress |
| IAPro/BlueTeam | In progress | In progress |
RCW Compliant: The vendor has indicated to WADEPS they are prepared to supply use-of-force and incident-based data on behalf of a Washington law enforcement agency to WADEPS and in a format that matches WADEPS specifications and definitions, which are compliant with Chapter 10.118 of the Revised Code of Washington (RCW).
For Vendors: Ask your law enforcement agency representative to contact us at wa.deps@wsu.edu to discuss future collaboration that could help them meet state reporting requirements.