HomeMy WebLinkAbout059-25 - Washington State University - ContractDocusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
WASHINGTON STATE
UNIVERSITY
U
DATA USE AGREEMENT
WASHINGTON STATE DATA EXCHANGE FOR PUBLIC SAFETY
1. PARTIES
1.1 This Data Use Agreement ("Agreement") is made and entered into by and between Washington
State University ("WSU"), an institution of higher education and an agency of the state of
Washington, and city of Port orchard
("Department"). In this Agreement, the above entities are jointly referred to as ("Parties").
2. PURPOSE and AUTHORITY
2.1 The purpose of this Agreement is to set forth the terms and conditions under which Department
will provide, and WSU will utilize, store, and retain certain Department data to establish and carry
out the statewide use of force data program in accordance with chapter 326, Laws of 2021 and
Revised Code of Washington (RCW) Chapter 10.118, hereinafter referred to as the Washington
State Data Exchange for Public Safety ("WADEPS").
2.2 It is the intent of the Washington Legislature that WADEPS will serve the interest of increasing the
public trust in law enforcement through accountability and transparency. As directed in RCW
10.118.040, the Washington State Office of the Attorney General (AGO) engaged in a competitive
procurement to contract with an institution of higher education to implement the statewide use
of force data program. WSU submitted a response to the request for proposal. The AGO selected
WSU's proposal and awarded WSU a state grant agreement to carry out the development and
management of WADEPS.
2.3 Under RCW 10.118.030, no later than three months after the AGO determines that the system
procured under RCW 10.118.040 can accept law enforcement agency reports, each law
enforcement agency must report each incident where a law enforcement officer employed by the
agency used force and the use of force meets the criteria listed in RCW 10.118.030(1) in
accordance with the requirements of the statewide use of force data program. RCW 10.118.030(3)
further requires that each law enforcement agency must also report any additional incidents and
data required by the statewide use of force data program. All reports must be made in the format
and time frame established in the statewide use of force data program.
3. DEFINITIONS
3.1 "Agreement" means this Data Use Agreement, including all Attachments and documents
incorporated by reference.
3.2 "CAD Data" means certain computer aided dispatch, or similarly functional system, data held by
Department or its associated public safety access point and provided to WSU in accordance with
this Agreement, including Attachment A: Authorization for Release.
3.3 "Confidential Information" means information that is exempt from disclosure to the public or
other unauthorized persons under RCW 42.56 or other federal or state laws. Confidential
Information may include both "Category 3 — Confidential Information" and "Category 4 —
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
Confidential Information Requiring Special Handling" as defined in Washington State IT Policy
141.10 (Securing Information Technology Assets).
3.4 "Copyright" means any work developed under this Agreement that is subject to copyright under
copyright law.
3.5 "Data" means the information that is disclosed or exchanged as described by this Agreement.
3.6 "Proprietary Information" means all data, sequences, and any other information obtained or
developed under this Agreement, subject to applicable law.
3.7 "Public safety access point" ("PSAP") means a call center or dispatch center that handles
emergency calls and coordinates emergency responses.
3.8 "RCW" means Revised Code of Washington.
3.9 "Reports" means reports provided by Department to WADEPS containing the information listed
at RCW 10.118.030(1) and (2).
3.10 "Trademark" shall mean any trade or service marks developed under the Scope of Work, whether
or not registered under either state or federal trademark law.
3.11 "WADEPS" is an acronym for the Washington State Data Exchange for Public Safety, the statewide
use of force data program established pursuant to chapter 326, Laws of 2021 and RCW 10.118.
4. DESCRIPTION OF DATA
4.1 Subject to the provisions of this Agreement, Department shall provide WSU with all data required
under RCW 10.118.030, including both the reports submitted to WADEPS containing the
information listed at RCW 10.118.030(1) and (2) ("Reports") and such additional data required by
WADEPS under RCW 10.118.030(3).
4.2 In addition to the Reports, which will be produced from data contained in the law enforcement
records owned and retained by Department, the Department will either provide or, using the
authorization form attached to this Agreement (Attachment A), authorize its associated PSAP to
provide to WADEPS a limited set of computer -aided dispatch data points ("CAD data") for all calls
for service. This CAD data will be used to validate and provide context for the data contained in
the Reports and is necessary to carry out the statewide use of force data program.
PSAP Agency Name: Port Orchard Police Department
PSAP Point of Contact for CAD Data Management
Name and Title: Alan iwashi to
Email: aiwashita@portorchardwa.gov
Phone: 360-252-9031
4.3 All data elements required under the statewide use of force data program are listed in the
Attachments to this Agreement. Data elements required under paragraph 4.1 of this Agreement
are listed in Attachment B: WADEPS Data Elements. Data elements required under paragraph 4.2
of this Agreement (i.e. CAD data) are listed in Attachment A: Authorization for Release of
Information to WADEPS.
4.4 The Parties agree this Agreement may be modified to include any additional incidents and/or data
required to be submitted to WADEPS under RCW 10.118.030(3) by unilateral amendment
Page 2 of 7
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
provided that the Department receives at least thirty (30) days' notice before the first required
submission of additional incidents or data.
4.5 Initial system implementation will utilize city -level information regarding incident locations. Once
an automated process for geolocating and obfuscating address data to a block group level is
implemented, WADEPS may request detailed incident address information. The Department will
be notified of this change in accordance with Section 4.4.
5. DATA USE
5.1 Reports and CAD data are provided to WSU only for use in accordance with the use and storage
conditions in this Agreement.
5.2 WSU will make a public -facing informational website known as the WADEPS data system
containing de -identified data. This de -identified data will be associated with the use of force and
police interactions with the public. The data will be available on the program's interactive
dashboard for public access and download, adhering to all applicable data protection and privacy
laws Departments will have access to the Data contained in WADEPS data system that is similar
to the public access, and Departments will retain access to their data in its identifiable form for
internal purposes via the WADEPS data system. Each officer will be assigned an automatically
generated confidential linked ID, which will replace the officer's name.
6. DATA TRANSFER, FREQUENCY, AND DISPOSITION
6.1 Department must submit a use of force incident report containing the data elements listed in
Sections 1-4 of Attachment B: WADEPS Data Elements to WADEPS within thirty (30) days of a
use of force incident using the reporting form created by WADEPS. Sections 1-4 of Attachment
B do not contain data elements related to review or investigation of a use of force incident.
Those data elements are listed in Section 5 of Attachment B: WADEPS Data Elements. The
timeline for submission of the data elements listed in Section 5 is not based on the date the use
of force incident occurred. For these data elements, Department must submit the data using the
reporting form created by WADEPS no more than 30 days after the review or investigation
reaches a determination.
6.2 CAD data must be provided on a monthly basis. Within the first five business days of each
month, Department or its associated PSAP will pull and submit a report containing the data
elements for the preceding calendar year (midnight January 1 to the time of the data pull). As
this is a year-to-date data pull, each subsequent month contains the prior months' data.
WADEPS will create a secure data environment for each Department's data and provide the
upload link to the specified point of contact.
6.3 As WSU implements and refines the WADEPS system, automated data transfer directly from
Department or PSAP source systems may become available. Once available, the Parties agree
that this procedure may be added to this Agreement by unilateral amendment. The agency shall
have a period of three (3) years to transition to the automated process following the
development of the solution.
6.4 Data that is submitted to WADEPS will be retained in the WADEPS system. At the end of the period
of performance and if no time extension is executed, this Agreement will be assigned to the AGO
in accordance with Section 10.6, Assignment.
Page 3 of 7
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
7. CONFIDENTIALTY
7.1 To the extent allowed by law, WSU and the Department agree to not use, publish, transfer, sell or
otherwise disclose any Confidential Information gained by reason of this Agreement for any
purpose that is not directly connected with the purpose of this Agreement, except as provided by
law; or with the prior written consent of the person or personal representative of the person who
is the subject of the Data.
7.2 WSU and the Department acknowledge that both agencies are subject to the Public Records Act,
RCW 42.56. If a Public Records Act request is made to WSU for the Department's Confidential
Information, WSU will promptly notify the Department of the request, such that Department has
the opportunity to seek a court order enjoining disclosure. WSU will work collaboratively with the
Department to identify any applicable exemption(s) to disclosure and appropriately redact the
information to be released to the extent allowed by law. The release of data will be limited to only
those records that must be released to comply with the request and the Public Records Act.
8. DATA SECURITY
8.1 WSU agrees that its security practices and safeguards meet or exceed the security standards of
Washington State IT Policy 141.10 (Securing Information Technology Assets). WSU shall exercise
due care and take responsible precautions to protect Confidential Information from unauthorized
physical and electronic access ensuring the confidentiality and integrity of all data shared.
8.2 Each party shall exercise due care to protect the shared data from unauthorized physical and
electronic access to ensure the Parties comply with all appropriate federal laws, Criminal Justice
Information Services (CJIS) Security Policy as appropriate, and applicable provisions of
Washington State IT Policy 141.10 (Securing Information Technology Assets).
8.3 WSU will have an independent external security assessment conducted every at least every three
(3) years to enhance data security and integrity. This audit will be performed by a reputable third -
party auditor specializing in data security. The auditor will assess compliance with Washington
State IT Policy 141.10 (Securing Information Technology Assets), evaluate the effectiveness of
WSU data protection measures, identify potential vulnerabilities, and recommend improvements.
The audit findings will be used to improve WSU data security protocols and practices continually.
8.4 WSU will perform an internal security assessment at least once a year that will be conducted to
ensure data protection and adherence to WSU data security policies, which meet or exceed
Washington State IT Policy 141.10 (Securing Information Technology Assets. These audits will
complement the external security audits, providing a comprehensive approach to maintaining
data security and protection.
8.5 WSU will report any unauthorized access, use, or disclosure of Data shared under this Agreement
that compromises the security, confidentiality, or integrity of the Data to Department within 72
hours of discovery. WSU will take actions to mitigate the risk of loss and any known harmful effects
of such unauthorized access, including, but not limited to, notifying subjects and taking steps
necessary to stop further unauthorized access.
9. RESPONSIBILITY AND HOLD HARMLESS
Page 4 of 7
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
9.1 The Parties to this Agreement are independent governmental entities and neither is the agent or
employee of the other. No liability shall attach to either Party for entering into this Agreement or
because of any act or omission of the Parties except as expressly provided.
9.2 Each Party to this Agreement shall be responsible for its own acts and omissions and those of its
agents and employees. Each Party shall also be responsible for its own attorney fees, demands,
losses, and liabilities to or by third parties arising from, resulting from, or connected under this
Agreement as permitted by law. Each Party's responsibility for its own acts or omissions and those
of its employees and agents for liability for damages arising out of bodily injury to persons or
damage to property caused by or resulting from their concurrent negligence or each Party's
agents or employees, shall apply only to the extent of each Party's own negligence or that of its
agents or employees. For avoidance of doubt, the provisions of this paragraph apply to liability
for damages due to a data breach.
9.3 Both Parties' responsibilities for their own acts or omissions shall specifically include all claims for
loss liability because of wrongful payments under the Uniform Commercial Code, or other
statutory or contractual liens or rights of third parties, including taxes, accrued or accruing as a
result of this Agreement or work performed or materials furnished directly or indirectly because
of this Agreement.
10. GENERAL TERMS AND CONDITIONS
10.1 Period of Performance. The period of performance for this Agreement shall begin upon the
execution of this Agreement and shall terminate on June 30, 2028, unless a time extension is
mutually agreed upon in writing between the Parties in accordance with Section 10.5,
Amendments. Upon the end of the period of performance and if no time extension is executed,
this Agreement will be assigned in accordance with Section 10.6, Assignment.
10.2 Publicity. Neither Party may use the other Party's Trademarks in any advertising, sales promotion,
or other publicity matter without prior written approval.
10.3 Notices. All notices required or permitted under this Agreement shall be in writing and served
upon the Parties in person, by certified or registered U.S. mail (return receipt requested) directed
to the mailing addresses set forth below or the mailing addresses designated by a Party pursuant
to written notice, or by electronic mail to the email address set forth below or the email address
designated by a Party pursuant to written notice. Notices delivered in person shall be effective on
the same day as delivered. Any notice delivered by certified or registered U.S. mail shall be
effective three (3) days after mailing. Any notice in person or by electronic mail shall be effective
immediately. All changes of address shall be effective upon written notice in the fashion provided
by this section.
WSU:
Office of Research Support and Operations (ORSO)
Lighty Student Services Building, Room 280
PO Box 641060
Pullman, WA 99164-1060
Email: orso@wsu.edu
Page 5 of 7
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
City of Port Orchard
Name/Title: Alan iwashi to
Address: 216 Prospect Street
City/State/Zip: Port Orchard WA 98366
Email: aiwashita@portorchardwa.gov
City of Port Orchard contact for Public
Records Act notifications (if different):
Name/Title: Cyndi Circelli
l i
Address: 216 Propect Street
City/State/Zip: Port Orchard WA 98366
Email: ccircelli@portorchardwa.gov
10.4 Dispute Resolution. Except as otherwise provided in this Agreement, when a dispute arises
between the Parties and it cannot be resolved by direct negotiation, any party may request a
dispute resolution panel (DRP). A request for a DRP must be in writing, state the disputed
issues(s), state the relative positions of the Parties, and be sent to all Parties. Each party must
provide a response within thirty (30) days unless the Parties mutually agree to an extension of
time. Each party shall designate a representative to serve on the DRP. The representatives shall
mutually select an additional member to serve on the DRP. The DRP, consisting of three
members total shall evaluate the facts, Agreement terms, and applicable statutes and rules and
make a determination by majority vote. The decision is binding on the Parties. Nothing in this
Agreement shall be construed to limit the Parties' choice of a mutually acceptable dispute
resolution method in addition to the dispute resolution procedure outlined above.
10.5 Amendments. Except as otherwise provided in this Agreement, any amendment to this
Agreement must be made in writing and signed by authorized representatives of both Parties.
10.6 Assignment. At the expiration of this Agreement, the work to be provided under this Agreement
may be unilateral assigned from WSU to Washington State Office of the Attorney General in
whole.
10.7 Governing Law. This Agreement shall be construed and interpreted in accordance with the laws
of the state of Washington.
10.8 Severability. If any provision of this Agreement or any provision of any document incorporated by
reference shall be held invalid, such invalidity shall not affect the other provisions of this
Agreement which can be given effect without the invalid provision, if such remainder conforms
to the requirements of applicable law and the fundamental purpose of this Agreement, and to
this end the provisions of this Agreement are declared to be severable.
10.9 Order of Precedence. In the event of an inconsistency in this Agreement, the inconsistency shall
be resolved by giving precedence in the following order:
1. Applicable statutes and regulations;
2. Terms and conditions contained in this Agreement;
3. Any other provisions incorporated by reference or otherwise into this Agreement.
10.10 Complete Agreement. This Agreement contains all the terms and conditions agreed upon by the
Parties. No other understandings, oral or otherwise, regarding the subject matter of this
Agreement shall be deemed to exist or to bind any of the Parties hereto.
Page 6o17
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
10.11 Counterparts. This Agreement may be executed in one or more counterparts, each of which shall
be deemed an original, but all of which shall constitute one and the same Agreement.
IN WITNESS WHEREOF, the PARTIES hereto have executed this Agreement as of the signature date
included below.
City of Port Orchard
Signed by:
Name:
3B96492E3F5847D...
Title: Mayor
6/16/2025
Date:
WASHINTON STATE UNIVERSITY
Signed by:
Name: p
Title: Associ a e Di rectorC...
Date:
7/17/2025
Page 7of7
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
Attachment A: Authorization for Release of Information to Washington State Data Exchange for Public Safety
Through a competitive procurement authorized under Revised Code of Washington (RCW) Section 10.118.040, Washington State University (WSU) was
selected to establish the statewide law enforcement use of force data program, which has since been named the Washington State Data Exchange for
Public Safety ("WADEPS"). Under RCW chapter 10.118, law enforcement agencies must report each incident where a law enforcement officer employed
by the agency used force and the use of force meets the criteria listed in RCW 10.118.030(1). In order to validate and provide context for the data
contained in these use of force reports, each law enforcement agency will provide or authorize its public safety access point (PSAP) to provide WADEPS
with a limited set of computer -aided dispatch data points ("CAD data") for all calls for service. This CAD data is necessary to carry out the statewide use
of force data program.
In order to facilitate its participation in the statewide law enforcement use of force data program,
Port Orchard Police Department requests and authorizes that Enter the name of your PSAP
provide to WSU the below -listed computer -aided dispatch (CAD) data on a monthly basis beginning the month following execution of this release
until July 2028, unless terminated or extended by written notification signed by an authorized representative of
Port Orchard Police Department
WSU (or such successor data custodian authorized by Washington State law) may only utilize the data provided pursuant to this authorization for
purposes of the Washington State use of force data program.
Pursuant to the data use agreement between WSU and law enforcement agencies, additional data elements may be added as needed to support full
operation of the WADEPS system. Law enforcement agencies and PSAPs will be notified of any additional data required to be submitted to WADEPS no
less than 30 days prior to the change in data elements. No additional release is required for dispatch centers to supply the additional data elements.
Instructions to set up data transfer:
WADEPS will provide each public safety access point (PSAP) with a unique link to securely upload the requested CAD data.
To obtain the secure upload link, please contact WADEPS' Vendor Service Desk at wadeps.vendor.servicedesk@wsu.edu . When requesting the
link, please provide the PSAP name (agency name) and the name and title of the point of contact responsible for managing CAD data at your
PSAP. Once WADEPS receives this information, WADEPS will create a secure data environment for your PSAP and send the upload link to the
specified point of contact.
Data Submission Requirements:
All submitted CAD data must adhere to the format and standards outlined in the CAD Data Requested Table below. Please comply with the
naming convention for fields.
Page 1 of 2
Docusign Envelope ID: 371 C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
• Within the first five calendar days of each month, pull and submit a report containing the data elements for the preceding calendar year
(midnight January 1 to the time of the data pull). Data for incomplete months will not be displayed. As this is a year-to-date data pull, each
subsequent month contains the prior months' data.
• WADEPS reserves the right to verify the accuracy and completeness of uploaded data. If discrepancies are found, WADEPS will notify the PSAP
point of contact and request corrections.
CAD data requested:
incident_id alpha -numeric Incident ID (Unique ID) — Uniquely identifies each incident for distinct
traceability.
agency_name alpha -numeric
Ori alpha -numeric Agency Unique Identifier (ORI #) -This identifies the handling agency and
is essential for agency -specific statistical analysis.
record_creation_time datetime mm/dd/yyyy Record Creation (m/d/yyyy h:mm: ss AM/PM) - The creation timestamp
hh:mm:ss provides a baseline for measuring response times and assessing
AM/PM reporting system efficiency.
original_call_type string Original Call Type Nature of Call (Unique code used by each agency) - This
describes the initial incident classification, which is crucial for
understanding the perceived severity and type when the record is
created.
County string
City string
City of Port Orchard
Signed by:
Name:
3B96492E3F5847D...
Title: Mayor
Date: 6/16/2025
Page 2 of 2
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
AGO -Approved Data Dictionary (updated 05.29.25)
Compliance: Sections 1-4 and 6 due within 30 -days of Item 1.4; Section 5 due within 30 -days of Item 5.1c
Element Name Element Label Element Definition Valid Values for Reporting Entry Type Notes
1.1 AGENCY NAME Agency name Indicates the name of the agency where the State recognized name of agency Auto populated via Login
involved officer is employed
1.2
ORI
FBI CJIS Originating Agency Identifier (ORI)
Agency federal identifier
9 -digit Alpha -Numeric
Auto populated via Login
1.3
INCIDENT NUMBER
Agency incident number
Indicates the number assigned to an incident
Alpha -Numeric
Manual Entry
Cross -validated with CAD/RMS to maintain a single
record by the originating agency
source of truth.
1.4
INCIDENT DATE
Incident date
Indicates the date the incident occurred
MM/DD/YYYY
Manual Entry
Cross -validated with CAD/RMS to maintain a single
source of truth.
1.5a
CONTACT REASON
Reason for public contact
Indicates the reason for initial contact
1 Public request for service
Manual Entry
As the system learns what call types are associated
2 Agency request for service
with officer identified categories, this can be
3 Unit- or officer -initiated
automated.
4 Planned activity
1.5b
RESPONSE TYPE
Response Type
Indicates the level of cause the officer
1 Social contact
Manual Entry
As the system learns what call types are associated
believed they had for contact
2 Reasonable suspicion
with officer identified categories, this can be
3 Probable cause
automated.
1.6a
INCIDENT TIME
Incident start time
Indicates the dispatched time, or time officer
HH/MM
Auto populated via Incident
indicated that they made call/stop
Data
1.6b
TIME TO FORCE -This is an attribute of
Time to Force
Indicates the approximate time between
1 Immediate
Manual Entry
Agencies with BWC Footage - Immediate or the
officer and incident
arrival on scene and the time force was first
2 Less than 1 minute
HH:MM:SS from the initial point of contact to the
used
3 1-5 minutes
action to use force.
4 6-10 minutes
Agencies without BWC Footage - Use the
5 Greater than 10 minutes
categorical values. We want to always fill in the
categories.
1.7a
LOCATION TYPE
Location
Indicates if location where force was used
1 Indoor
Manual Entry
was indoor or outdoor
2 Outdoor
3 Both
1.7b
LOCATION TYPE INDOOR
Location indoor
Indicates indoortype of location where force
1 Single family residence
Manual Entry
was used
2 Apartment or multifamily residence
3 Commercial/Business premises
4 Government facility (court,
school/university, offices)
5 Medical facility (clinic, hospital, etc)
6 Transit facility
7 Other
1.7c
LOCATION TYPE OUTDOOR
Location outdoor
Indicates outdoor typeoflocation where
1 Residential private property (yard, etc)
Manual Entry
force was used
2 Commercial private property (parking
lot, etc)
3 Government property (around official
buildings)
4 Public right of way (highway, street,
sidewalk, boat launch, etc)
5 Transit property
6 Public lands (parks, state/national
forests, etc)
7 Other
1.8
INCIDENT ADDRESS
Incident address
Indicates the street or HWY address where
100 block/or nearest Milepost if Hwy/
Auto populated via Incident
WATech Block Group Levels and Census Block
force was used
+street+municipality
Data
Groups. Calculated on Data Import.
Lat/Long option
(NOT CURRENTLY COLLECTED)
Page 1 of 6
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
1.9a
INCIDENT TYPE
Initial type of incident
Indicates the type of incident officer was
1 Offense against person
Manual Entry
As the system learns what call types are associated
dispatched or initiated (check all that apply)
2 Property offense
with officer identified categories, this can be
3 Public order offense
automated.
4 Vehicle stop
5 Pedestrian stop
6 Civil caretaking
7 Warrant
8 Other
1.9b
INCIDENT DETAIL
Initial type of incident detail
Indicates the type of incident within the
Offense against person
Manual Entry
As the system learns what call types are associated
category of initial incident (check all that
1 Assault (all types)
with officer identified categories, this can be
apply)
2 Homicide (all types)
automated.
3 Rape
4 Robbery
5 Civil order violation
6 Other
Property offense
7 Arson
8 Burglary
9 Theft
10 Mischief
11 Trespassing
12 Vehicle theft/prowl
13 Other
Public order offense
14 Public disturbance
15 Drug related
16 Sex related
17 Weapon related
18 Transit related
19 Other
Vehicle Offense
20 DUI
21 Accident
22 Moving violation
23 Non-moving violation
24 Other
Civil Caretaking
25 Mental health/wellness check
26 Civil infraction
27 Eviction order enforcement
28 Domestic order enforcement
29 Other
1.9c
DOMESTIC VIOLENCE INCIDENT
Domestic Violence Incident
Indicates if the incident is associated with
0 No
Manual Entry
domestic violence
1 Yes
1.10
ARREST
Arrest or welfare detention
Indicateswhetherthe subjectwas arrested or
1 Arrested
Manual Entry
As the system learns what call types are associated
taken into custody
2 Civil detention
with officer identified categories, this can be
3 No arrest or detention
automated.
1.11a
ARREST REASON
Reason for arrest
Indicates what the officer arrested the person
1 Obstruction/resistance
Manual Entry
As the system learns what call types are associated
for (check all that apply)
2 Person crime
with officer identified categories, this can be
3 Property crime
automated.
4 Offense against public order
5 Vehicle violation
6 Warrant
7 Other
Page 2 of 6
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
1.11 b
ARREST DETAIL
Detailed reason for arrest
Indicates the arrest type within category of
Offense against person
Manual Entry
As the system learns what call types are associated
arrest (check all that apply)
1 Assault (all types)
with officer identified categories, this can be
2 Homicide (all types)
automated.
3 Rape
4 Robbery
5 Civil order violation
6 Other
Property offense
7 Arson
8 Burglary
9 Theft
10 Mischief
11 Trespassing
12 Vehicle theft/prowl
13 Other
Public order offense
14 Public disturbance
15 Drug related
16 Sex related
17 Weapon related
18 Transit related
19 Other
Vehicle Offense
20 DUI
21 Accident
22 Moving violation
23 Non-moving violation
24 Other
1.11 c
DOMESTIC VIOLENCE ARREST
Domestic Violence Arrest
Indicates if the subject arrest includes
0 No
Manual Entry
domestic violence language
1 Yes
1.12
MINORS
Minor(s) present during use of force
Indicates if the officer who used force knew
0 No
Manual Entry
whether there were minors present during
1 Yes
the use of force.
2 Unknown
1.13
VIDEO
Is there a police video record of the
Indicates if there is police generated video
0 No
Manual Entry
use of force incident
(e.g., dash cam, body cam) of the use of
1 Yes
force incident
1.14a
OFFICERS TOTAL
Total number of officers present at the time
Indicates the total number of officers present
Numeric between 1-99
Manual Entry
GOAL: Auto populated via Incident Data
force was used
at the time force was used
1.14b
OFFICERS FORCE
Total number of officers using force
Indicates the total number of officers using
Numeric between 1-99
Manual Entry
force
1.15a
PERSONS TOTAL
Number of persons present when force was
Indicates the total number of persons present
Numeric between 1-99
Manual Entry
used (not including officers)
at the time force was used (not including
officers)
1.15b
SUBJECTS FORCE
Number of engaged persons (subjects)
Indicates the total number of subjects upon
Numeric between 1-99
Manual Entry
If officer used force on more than one subject, this
upon whom force was used
whom force was used
will prompt reporting of data elements for each
subject separately
•
• • •
I
2.1
POINT
Pointed a firearm at a person
Indicates the officer pointed a conventional
0 No
Manual Entry
firearm at a person (excludes less lethal
1 Yes
shotguns, impact munitions, or equivalents)
2.2
DISCHARGE
Discharged a firearm at or in the direction of
Indicates the officer discharged a
0 No
Manual Entry
a person
conventional firearm at or in the direction of a
1 Yes
person (excludes less lethal shotguns,
impact munitions, or equivalents)
2.3
ECW
Used electronic control weapon at or in the
Indicates the officer used electronic control
0 No
Manual Entry
direction of a person
weapon at or in the direction of a person
1 Yes
2.4
CHEMICAL
Used chemical irritant spray against a
Indicates the officer used oleoresin capsicum
0 No
Manual Entry
person or in the direction of a person
spray against a person
1 Yes
2.5
LESS LETHAL DISCHARGE
Discharged a less lethal shotgun or impact
Indicates the officer discharged a less lethal
0 No
Manual Entry
munitions at or in the direction
shotgun or impact munitions at or in the
1 Yes
of a person
direction of a person
2.6
IMPACT
Struck person using impact weapon or
Indicates the officer struck a person using an
0 No
Manual Entry
instrument including but not limited to club,
impact weapon or instrument including but
1 Yes
baton, flashlight
not limited to club, baton, flashlight
2.7
STRIKE
Used any part of the bodyto physicallystrike
Indicates the officer used any part of the
0 No
Manual Entry
a person including, but not limited to:
body to physically strike a person including,
1 Yes
punching, kicking, slapping, using closed
but not limited to, punching, kicking, slapping,
fists, leg or feet
using closed fists, leg or feet
Page 3 of 6
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
2.8
VEHICLE
Used vehicle to intentionally strike a person
Indicates the officer used a vehicle to
0 No
Manual Entry
or vehicle
intentionally strike a person or vehicle
1 Yes - Person
2 Yes - Vehicle
2.9
CANINE
Deployed a canine
Indicates the officer deployed a canine by
0 No
Manual Entry
releasing it from the physical control of the
1 Yes
law enforcement officer or had under the law
enforcement officer's control a canine that
bites a person.
2.10
NECK
Used neck restraint
Indicatesthe officer used a neck restraint or
0 No
Manual Entry
chokehold, as defined in RCW 10.116.020
1 Yes
I
I
2.11
FORCE OTHER
Type of force not listed
Indicates the officer used a type of force not
0 No
Manual Entry
specified above that resulted in injury
1 Yes — Specify:
I
I
•
3.1
SUBJECT AGE
Subject Age
Indicates the verified age of the subject
Numeric up to 3 -digits
Manual Entry
3.2
SUBJECT GENDER
Subject Gender
Indicatesthe verified genderof the subject
1 Male
Manual Entry
2 Female
3 Non -binary
4 Transgender
5 Unknown
3.3a
PERCEIVED SUBJECT RACE
Officer Perception of Subject Race/Ethnicity
Indicates the officer's perception of the
1 American Indian or Alaska Native
Manual Entry
ETHNICTY
subject's race/ethnicity at the time force was
2 Asian
used (check all that apply)
3 Black or African American
4 Hispanic or Latino
5 Middle Eastern or North African
6 Native Hawaiian or Pacific Islander
7 White
8 Unknown
3.3b
VERIFIED SUBJECT RACE ETHNICTY
Verified Subject Race/Ethnicity
Indicates the verified race/ethnicity of the
1 American Indian orAlaska Native
Manual Entry
subject by the person or family member
2 Asian
(check all that apply)
3 Black or African American
4 Hispanic or Latino
5 Middle Eastern or North African
6 Native Hawaiian or Pacific Islander
7 White
8 Unknown
3.4
SUBJECT TRIBAL
Subject tribal affiliation
Indicates subject tribal affiliation
0 No
Manual Entry
1 Yes
2 Refused
3.5
SUBJECT INJURY
Subject injury type
Indicatesthe type of injuries sustained during
0 None
Manual Entry
the use of force (check all that apply)
1 Apparent minor injury (e.g., minor
cuts/bruises)
2 Severe laceration
3 Loss of teeth
4 Canine bite
5 Apparent broken bones
6 Possible internal injury
7 Unconscious
8 Gunshot wound
9 Death
10 Other major injury
3.6
SUBJECT IMPAIRMENT
Subject Impairments
Indicates the officers perception of subject
0 None
Manual Entry
impairments (check all that apply)
1 Alcohol
2 Drugs
3 Mental health
4 Unknown
3.7
SUBJECT ARMED
Officer believed subject to be armed
Indicates the officer's perception of whether
0 No
Manual Entry
the subject against whom force was used
1 Yes
was armed
3.8
SUBJECT WEAPON TYPE
Type of weapon found or used
Indicates any weapon type found or used
1 None
Manual Entry
(check all that apply)
2 Blunt object
3 Edged object
4 ECW
5 Chemical/explosive
6 Projectile
7 Firearm
8 Vehicle
3.9
SUBJECT FLIGHT
Subject Action -Flight
Subject flight or attempted flight,p_ orto
1 None
Manual Entry
using force
2 Flight or attempted flight
Page 4 of 6
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
3.10a
SUBJECT THREAT OFFICERS
Subject Action - Threat to officers
Subject imminent threat to officers, priprto
0 None
Manual Entry
0 None
using force
1 Verbal threat
1 Verbal threat
2 Threatening posture/furtive movements
2 Threatening posture/furtive movements (subject
3 Assault
assumes fighting stance; reaches into pockets)
4 Use or display of a less -lethal weapon
3 Assault
5 Use or display of a deadly weapon
4 Use or display of a less -lethal weapon (objects
that might be thrown or swung but officerdoes not
believe could be lethal or cause serious bodily
injury)
5 Use or display of a deadly weapon (firearms,
knives, any object officer believes could be lethal or
cause serious bodily injury)
3.10b
SUBJECT THREAT OTHERS
Subject Action - Threat to other persons
Subject imminent threat to persons other
0 None
Manual Entry
0 None
than officers, prior to using force
1 Verbal threat
1 Verbal threat
2 Threatening posture/furtive movements
2 Threatening posture/furtive movements (subject
3 Assault
assumes fighting stance; reaches into pockets)
4 Use or display of a less -lethal weapon
3 Assault
5 Use or display of a deadly weapon
4 Use or display of a less -lethal weapon (objects
that might be thrown or swung but officerdoes not
believe could be lethal or cause serious bodily
injury)
5 Use or display of a deadly weapon (firearms,
knives, any object officer believes could be lethal or
cause serious bodily injury)
3.10c
SUBJECT THREAT SELF
Subject Action -Threat to self
Subject imminent threat to self, prior to using
0 None
Manual Entry
force
1 Verbal threat of self -harm
2 Self -harm or attempted self -harm
3.11a
SUBJECT RESISTANCE
Subject Action - Resistance
Subject resistance, prior to using force
0 No resistance
Manual Entry
0 No resistance
1 Verbal resistance or passive resistance
1 Verbal resistance or passive resistance (verbal or
2 Threatening posture, verbal threats
physical non-compliance with officer's commands)
3 Physical non-compliance or flight
2 Threatening posture, verbal threats (verbal or
4 Active physical resistance
physical threat to officer)
5 Use of a less -lethal weapon
3 Physical non-compliance or flight (physical
6 Use of deadly weapon or lethal force
evasion, pulling away from officer, tucking arms to
prevent handcuffing, flight)
4 Active physical resistance (strikes with fists,
elbows, knees; kicking; spitting)
5 Use of a less -lethal weapon (strikes using blunt
objects; throwing objects; ECW)
6 Use of deadly weapon or lethal force (firearms,
knives, physical strikes to head; vehicular assault)
3.11 b
CIVIL DISOBEDIENCE
Subject verbal/passive resistance was civil
If 3.11 b is verbal or passive resistance (value
0 No
Manual Entry
disobedience
= 1), was this an act of civil disobedience?
1 Yes
4.1
OFFICER NAME
Officer Name
Indicates legal name of the officer for who
Last, First, Middle
Auto populated via Login
Not Passed to Website
this incident is reported
4.2
OFFICER CJTC
CJTC identification number
Indicates the unique identification of the
XXXX-XXXX
Auto populated via Login
Not Passed to Website
officer
without using their name
4.3
OFFICERAGE
Officer Age
Indicates the age of the
Numericbetween
Auto populated via Login
officer at time of incident
16-99
4.4
OFFICER GENDER
Officer Gender
Indicetes the verified gender of the officer
1 Male
Auto populated via Login
2 Female
3 Non -binary
4 Transgender
4.5
OFFICER RACE ETHNICITY
Officer Race/Ethnicity
Indicetesthe verified race/ethnicity of the
1 American Indian or Alaska Native
Auto populated via Login
officer (check all that apply)
2 Asian
3 Black or African American
4 Hispanic or Latino
5 Middle Eastern or North African
6 Native Hawaiian or Pacific Islander
7 White
8 Unknown
4.6
OFFICER YEARS
Officer years of service in law enforcement
Indicates the number of years the officer has
Numeric
Auto populated via Login
worked in law enforcement
(Provided by CJTC)
Page 5 of 6
Docusign Envelope ID: 371C5A4C-63A3-4B5A-B881-811581861529
ORSO# 150000-D001
4.7
OFFICER ASSIGNMENT
Shift assignment type
Indicates the type of assignment officer had
1 Patrol
Manual Entry
at the time of use of force
2 Traffic
3 Administrative
4 Specialty
4.8
OFFICER INJURY
Officer injury
Indicatesthe type of injuries sustained during
0 None
Manual Entry
the use of force (check all that apply)
1 Apparent minor injury (e.g., minor
cuts/bruises)
2 Severe laceration
3 Loss of teeth
4 Canine bite
5 Apparent broken bones
6 Possible internal injury
7 Unconscious
8 Gunshot wound
9 Death
10 Other major injury
5.1a
UOF STATUS
Use of force review status investigation
Indicatesthe level of investigation of this use
1 No review
Manual Entry
of force
2 Administrative review (on-
going/complete)
3 Internal investigation (on-
going/complete)
4 External investigation (on-
going/complete)
5.1 b
UOF REVIEW START
Use of force review start date
Indicates the date that the administrative
Date field (DD/MM/YYYY)
Manual Entry
review or internal/external investigation
started
5.1c
UOF REVIEW END
Use of force review end date
Indicates the date that the administrative
Date field (DD/MM/YYYY)
Manual Entry
review or internal/external investigation
concluded
5.2
UOF REVIEW
Use of force review outcome
Indicatesthe outcome of the use of force
1 No review done
Manual Entry
review
2 Administrative review (within/outside of
policy)
3 Internal investigation (exonerated, not
sustained, sustained)
4 External investigation (exonerated, not
sustained, sustained)
53
INTERNAL ACTION
Internal Investigation Action
Indicates the action required bythe internal
1 Information restricted
Manual Entry
investigation
2 No action
3 Change assignment
4 Training
5 Reprimand
6 Terminate
5.4
INVESTIGATIVE ENTITY
Name of entity conducting external
Indicatesthe name of entity conducting
1 No investigation
Manual Entry
Collected at intake because an OIS will not have the
investigation
external investigation
2 IIT
information for Sections 1-3 until completed. It
3 O11
needs to be asked if this will be investigated by I IT or
• •-
OIl at section 1.
6.1
Indicatesthe unique incident number
re Ensus a single -point of truth mirroring agency
CAD INCIDENT NUMBER
CAD incident number
Alpha -Numeric
Auto populated from CAD
data. Used for cross -validation of incident records
assigned by the CAD system
across systems.
6.2
Unique identifierfor the agency involved in
Maintains consistent identification of the agency
AGENCY UNIQUE IDENTIFIER
Agency unique identifier
Alpha -Numeric
Auto populated from CAD
across different records, allowing for accurate
the incident
reporting and audit tracking.
6.3
Captures the exact time and date the record was
RECORD CREATION
Record creation
Indicatesthe date and time the record was
Date -Time Format (MM/DD/YYYY
Auto populated from CAD
created, providing a consistent timeline for auditing
created
HH:MM:SS
and validation purposes. Necessary to calculate
rates of force based on month.
6.4
Establishes a baseline for incident categorization,
ORIGINAL CALL TYPE
Original call type
Describes the type of call originally reported
Predefined Call Types
Auto populated from CAD
allowing for accurate tracking of incident evolution
to dispatch
and response actions. Necessary to calculate rates
of force based on call type.
6.5
LOCATION CITY
Location City
the city where the incident occurred
String
Auto populated from RMS
Page 6 of 6