SOP-SSD-8 CAD Special Situation EntriesSUPPORT SERVICES DIVISION
SOP SSD-8
Issued: 12-13-08
Revised 9/17/2012
Revised 12/19/2016
SUBJECT: Special Situation Entries
PROCEDURE: Upon request from a field unit to enter immediate need information into
the CAD Special Situation file (Premise data) or receipt of general premise information,
Dispatchers shall enter a record in CAD:
Officer Safety/Immediate Need
A. Obtain:
1. Address
2. Name and DOB of involved party/s
3. Description of problem
4. Weapons
5. Representative name and phone number if appropriate
6. Requesting officer
Other acceptable entries include: Officer and user agency safety, Electronic
Monitoring Info, hazardous materials data, jurisdictional information, directions, and
gate codes.
B. Event > Create > Special Situation or Type ASP on command line
C. Enter the following:
1. Event Number (must have to create a Special Situation in
CAD).
2. System will auto fill special situation type code with the event
type. This field should be changed with the type of entry to
conform to the SCPSC Protocol (attached). For example:
Officer Safety information enter “OFFICER SAFETY”. Directions
to an address, enter “INFO.”
3. Priority: 1 for Officer Safety; 9 for all others
4. Area Situation: Click this box if the premise record should also
display with events associated to neighboring addresses.
(Area is defined within CAD as within a 0.5 mile radius.)
5. Location: Auto-populated when Event Number entered.
Address ranges must be entered by the Supervisor or their
designee through CADDBM.
6. Remarks: Further defines the type of special situation. Please
see attached Protocol for examples. For Electronic Monitoring
Information, use “INFO” as the type, and “ELECTRONIC
MONITOR” in Remarks.
7. Message: Give complete description of issue. Include all of the
above items in Section A for officer safety entries and all
available information for other premise entries. For Electronic
Monitoring, include subject’s name and date of birth, details
of confinement, and date confinement will end.
a. Must click on the “add” button prior to entry.
8. Employee ID is auto filled by system based on who is signed on
to that terminal.
9. Expiration:
a. Officer Safety: click on Record Expires button.
System will auto fill with a 7-day default. Unless a
completed “Premise Information Form” has been
presented, expiration should be the default date. The
Dispatch Supervisor or their designee will update the record
upon receipt of completed Premise Information Form.
b. Gate Codes, directions, HAZMAT, etc: Click on
Never Expires button.
c. Electronic Monitoring: use date confinement is scheduled
to end.
10. If information is Law Enforcement sensitive, click on the
“Restricted to Agencies” button, while holding the Control key
down, click on each law enforcement (LE) agency that
should have access to the information.
Note: With the exception of Electronic Monitoring, address directions, or gate code
information, field personnel should be reminded to follow-up on all verbal requests with
the Premise Information File Form.
D. Perform a LOI search on the Address and print.
E. File the printout, the request form, and any additional documentation
in the purple SS folder on the wall next to Position 1. The assigned dispatch
personnel will file it in the Special Situation Binder.
F. Gate codes phoned in by citizens
1. Create an “advised event” with event type INFO then follow
above procedure.
G. The following special situations require CADDBM entry by an
authorized CADDBM user.
1. Long-term officer safety (form received)
2. Changes to prior special situation entries
3. Range of address entries
SCPSC – SONOMA COUNTY PUBLIC SAFETY CONSORTIUM PROTOCOL
Special Situation Types 8/20/08
The purpose of this protocol is to establish a consistent method for entry of special
situations within the Intergraph CAD system.
Protocol:
I. When creating special situations in CAD or CADDBM, the following type codes
should be used to clarify the type of entry. When creating from CAD events, the
event type shall be replaced with one of the below listed types codes.
Officer Safety (no abbreviations)
Info
Jurisdiction (no abbreviations)
Trespass (no abbreviations)
Gate Code
HAZMAT
Medical
Fire Info
II. Remarks (Record Summary) Field:
A. The remarks field just below the type code shall be used to further describe the
type code selected. Examples listed below:
Type: Officer Safety Remarks: Weapons
Type: Info Remarks: Directions
Type: Trespass Remarks: Trespass letter on file
Type: HAZMAT Remarks: Chlorine storage
III. Message Field:
A. The message field at the bottom should contain specific details related to the
address and reason for special situation entry.
IV. Expiration Date:
A. A specific expiration date should be entered whenever possible based on
need and/or Department Policy.
V. Departmental Review:
A. Periodic review of each agencies special situation will help to ensure the
entries are accurate and active. If a record is no longer needed, the expiration
date shall be changed to a previous date so that the record no longer
appears on CAD events.
Related Users/Modules
CAD, MDC