10-35 on Call Information 1700-6
10-36 Information 1700-8
CIIDS Icon 1700-15
Creation of an Event 1700-1
Dispatch on an Event 1700-2
Dispatching an Event When Detachment Is on Call 1700-4
Duties of Reviewer 1700-5
Event, Creation of 1700-1
Event When Detachment Is on Call 1700-4
Mobile Workstation Procedures 1700-11
Municipal PS - DOCC Sask Radio/Logging Protocols 1700-9
On Call Information 1700-6
Re-creation of CIIDS Icon on the Computer Desktop 1700-15
TITLE: CREATION OF AN EVENT
This policy will standardize the method of creating events in the CIIDS system.
A Complaint Taker is the starting point in the process of taking a complaint from a member of the general public or a member in the field who is requesting police services. The Complaint Taker can be situated in the actual Complaint Taking position however, can also be generated by a Dispatcher, Supervisor, etc.
If the call qualifies as a valid policing concern, the operator will create an event in CIIDS. This is accomplished by selecting "Event Create" on the CIIDS terminal. The operator would then enter information about the complaint, addressing the 5 W's (what, when, where, why, weapons) and how for each complaint and record this information on the event form.
To create an event, you only need to enter a Detachment (and Zone if applicable) and the Priority of the Event. However, it is customary to enter a wide range of details, including information about the caller or complainant, vehicles, businesses, locations, details of the call, etc. If the event is not ongoing at present, ensure the "date and time occurred" fields are completed. The Complaint Taker shall attempt to complete all fields on the event form. The identity of the complainant and a telephone number that the caller can be contacted at are prime fields to be entered. An accurate location of the where the occurrence occurred is a must item for entry. This allows the police officer to promptly attend to the offence location. The "time of occurrence" or "time span" of when the occurrence occurred will also assist the investigating police officer. This is also used by Detachments to determine when certain offences are occurring within their Detachment boundaries.
An event is not created in CIIDS until the operator clicks on the "Create" button or "Post" button. If the operator starts entering information and then decides that this would not be an event, they only have to click on the "Cancel" button or press the "ESC" key to abort the process. An event will not be created.
Once the operator is satisfied they have the information needed on the complaint, they can "Create" the event or "Post" the event. If "Create" is used, the event must still be posted prior to the event being transferred to the Dispatcher. By using "Post", the event is automatically created and transferred to the correct Dispatcher.
TITLE: DISPATCH OF AN EVENT
This policy will standardize the method of dispatching events created in CIIDS.
A. MEMBER ON DUTY
A Dispatcher will receive events in their Active Event window. The Dispatcher will dispatch events in priority order. The appropriate Detachment member will be selected for the dispatching of the event.
The Dispatcher will proof read the event to ascertain if the event contains sufficient information for them to allow the Patrol member to understand the event and location of same. If there is insufficient information the Dispatcher will contact the Complaint Taker for an update. If the Complaint Taker does not have any further information, the Dispatcher will attempt to contact the Complainant, however, if no call back number, etc is available, the Dispatcher will advise the Patrol member of the information as received and that there is "no further information" available.
When the Dispatcher advises the patrol member of the event, they will assign a member's regimental number to the event. This will be accomplished by dispatching the event to a PUID, which will automatically enter the regimental number of the first member in the Patrol Unit. If the event is to be assigned to the second member in the PU, then the Dispatcher must ensure that the second member is selected. At no time will an event have the regimental number of "99999" as the assigned regimental number.
B. MEMBER NOT ON DUTY
The Dispatcher will ensure the event needs to be dispatched at the present time by proof reading same. If the event must be dispatched and the Detachment does not have a member on duty, then the on call member will be called and the event dispatched to that member. The Dispatcher will dispatch the event to the two-letter PUID of the on call Detachment. The Dispatcher must ensure that the event is dispatched to the first or second member and that their correct regimental numbers are assigned the event. At no time will the event be dispatched to the regimental number of "99999".
C. EVENT - NO NEED FOR DISPATCH
The Dispatcher will decide whether the event will be dispatched immediately or not. If the Dispatcher decides that the event is not needed to be dispatched immediately, then the
TITLE: DISPATCH ON AN EVENT
event can be held in the Active Event window of the Dispatcher until such time as a
member is available to receive the dispatch of the event.
D. COLD EVENT
The Dispatcher decides that the event is a cold or information only type of complaint. The Dispatcher will assign a member's regimental number to the event by dispatching to the on call member or member coming on duty. At no time will an event be dispatched to the regimental number of "99999". The Dispatcher will then print a copy of the event and fax the printed copy to the Detachment concerned. The Disptacher will also leave a message on the Detachment's message manager stating that a "cold" event has been dispatched to the Detachment. In that message, the Detachment's occurrence file number will also be included. The event will then be deactivated and down loaded to the Detachment's PIRS system.
Upon a member clearing the scene of any event, the Dispatcher will remove the member(s) attached to the event, deactivate the event and send it back to the Reviewers for processing.
TITLE: DISPATCHING AN EVENT WHEN DETACHMENT IS ON CALL
This policy will be followed when dispatching an event to a Detachment/Unit that is On Call.
DOCC Saskatchewan continues to receives complaints from Detachments where regimental numbers are not being included in a concluded file; and/or files are being deactivated and down loaded with inaccurate dispatch times as the dispatcher was waiting to attach a PUID when the member comes 10-36, 10-8 from the "on call" status.
Dispatchers will enter the regimental number in the proper field. When entering the regimental number it is mandatory that you tab out of the regimental number field to ensure the correct regimental number has been entered.
Reviewers will ensure that there is a valid regimental number on page 5 of the event prior to "End Reviewing" and down loading.
When a dispatcher voice dispatches an event to a member at their residence, the dispatcher will insert the two letter designator in the PUID field. The dispatcher will ensure that if there is more than one member on call to check the first or second member block on the event screen. When the member comes 10-36, 10-8 to go to the call, the dispatcher will add the vehicle and the member to the CIIDS system. The dispatcher then would do a "Patrol Unit Update" and select the quick view. This will give the dispatcher a listing of all active file numbers. Pick the correct file number for the complaint the member is en route to. Tab off of the quick view event number. The event will now be attached to the correct PUID and member. Tab down to the "Remarks" field and insert "Call out" or a similar notation. The dispatcher will then click on update or press enter to activate the modification. The two letter on call designation for the detachment can be made 10-8 and 10-35 once again. This will ensure that the dispatcher has the on call information still entered for the Detachment.
When the member is 10-8 and clear from the complaint, the dispatcher will then update the PU in CIIDS, advise the member of the case number and download the event to the Reviewers.
Once the called out member goes 10-35 at his/her residence once again, the PU can be
marked 10-35 and subsequently removed from the CIIDS system.
TITLE: DUTIES OF REVIEWER
This policy will standardize the process of "End Reviewing" of deactivated events processed in
When a Dispatcher deactivates an event, the event will be transferred from the Dispatched Event window to the Review Events window.
The Complaint Takers normally process the events in review, however Dispatchers can process events that they have areas of responsibility for.
The Reviewer will check the event to make sure there are no glaring errors in the event form. As well the Reviewer will verify that a valid regimental number has been assigned to the event.
The Reviewer will then click on the "End Review" button to forward the event from the review stage to the final stage prior to down loading to the PIRS system. This is the Q and A or Quality Assurance stage.
The transfer of the event from the review to the QA stage will show any errors that will not allow the event to be correctly down loaded to the PIRS system. The Reviewer will ensure that all pages of the event will got down to PIRS by checking under the PIRS tab and insuring that all pages are valid. If there are no errors, the Reviewer will click on the "End QA" tab. The event will then be down loaded to the Detachment's PIRS system. It is at this time that the event leaves the DOCC's CIIDS system.
If there is an error in the event, the error must be corrected by the Reviewer. If the Reviewer is unable to correct the error, the event will be left in the QA stage and not be "End QA'd" with the error.
The CSC (C/M Denise Lagace or designate) will be appraised of the Reviewer's inability to correct the error. The CSC will correct the error or get assistance from the CHD or SKL to correct the error. At no time will the event be "End QA'd" without the error being corrected.
TITLE: ENTRY OF 10-35 ON CALL INFORMATION
This policy will standardize the entry of 10-35 information of Detachments and Units.
It is the Detachment Commander's responsibility to arrange for a police response from his/her unit regardless of the time of day. This should preferably be a local response, but when necessary suitable arrangements with neighbouring Detachments may suffice.
All Detachment Commanders will ensure that an appropriate level of police response is available at all times from their unit specifically during quiet hours. Members going off shift will advise the DOCC of who is on call and how they can be reached.
The Detachment's off duty (10-35) and on call information will be entered into the CIIDS system using the two letter PUID to identify the individual Detachment concerned. In the case of a Host Detachment being on call for a Community Detachment, all Detachments in the group shall be listed individually (ie: KG, FI, MM).
Member 1 will be the first member who is on call. As well, the time and date limit that the member is on call until, will be entered. If the member is from a Detachment other then the one that is being placed on call, then the 2 letter Detachment code of the member's Detachment shall also be entered (ie: CB 35 CB EVANSON(GU) od 0800 15TH)
Member 2 will be the second member who is on call. The time and date that the member will be reporting for duty will be entered if known. The same as for Member 1, if the member is from Detachment other than the one being placed on call, then the 2 letter Detachment code must also be entered.
When entering a Host Detachment as being on call for a Community Detachment, the member 1 field will be filled by the Host Detachment member's name and two (2) letter Detachment code on call or by the Detachment name as being on call. The time and date of the on call will also be entered. The member 2 field will be filled by the next available member coming on duty at the Community Detachment and the date and time the member will be on duty if known.
B. IDENT, PSD, ETC ON CALL
The abbreviation for the specialized unit such as Forensic Identification or MCU (ie: SAIDT, REMCU, etc) will be removed from the CIIDS system when a member comes on
TITLE: ENTRY OF 10-35 ON CALL INFORMATION
shift for the day.
In the case of the Division PSD sections, the same member utilizes the same patrol unit all the time. For this reason, when the PSD member goes 10-35, you will mark the patrol unit as being 10-35, however, leave the patrol unit on the CIIDS system.
At the end of the other specialized unit's shift, the PU will be marked 10-35 and removed from the the CIIDS system. The abbreviation for the unit will be entered to show the unit is 10-35, and the member field modified to show the correct member on call.
C. SPECIALIZED UNITS ON CALL
Some units, such as Regina MCU, CCS, Drugs, etc never actually sign onto the CIIDS system. The members of these units will supply an on call member and the information will be captured on the Corel Presentation (Dutyoff).
The Force aircraft, MPW and MPE will be left on the CIIDS system when the aircraft is 10-35 for the day. The on call pilot information will be entered as the on call member and any further information (next flight, cell, etc) will also be entered.
The Dispatchers must ensure they practice good house keeping by ensuring that 10-35 and 10-36 entries are removed from the CIIDS system at the start/end of shifts.
TITLE: ENTRY OF 10-36 INFORMATION
This policy will standardize the entry of on duty (10-36) information onto the CIIDS system.
When a Detachment/Unit forwards their on duty (10-36) information to DOCC Saskatchewan, the information must be entered onto the CIIDS system. The operator entering the information will enter the information using the "Patrol Add Form" on the CIIDS system. The Patrol Unit and Regimental number of the member(s) will be entered.
In the "Remarks" field, the operator will enter the hours of work will then be entered using the 24 hour clock. There is no need to use a complete 4 digit time, unless the shift is on the half hour. It would be sufficient to enter the time as 08-16, 16-24, etc. The operator will then enter the cellular phone number if the patrol member has provided the number.
The repeater that the member will be using is entered in the V.Channel field.
When the operator has entered the on duty (10-36) information for a particular Detachment/Unit, the previous 10-35 or on call entry under the two letter Detachment abbreviation shall be removed from the CIIDS system.
The entry of the home repeater in the V.channel of the Patrol Unit allows operators who are not as familiar with a particular zone, or newer operators, to quickly ascertain which repeater a certain Patrol Unit normally uses. In an urgent situation, the time saved by being able to quickly locate the repeater is worth the effort of entering the information for all Patrol Units.
TITLE: MUNICIPAL PS - DOCC SASK RADIO/LOGGING PROTOCOLS
A. LOGGING ON/OFF
It is the Municipal Police Service's responsibility to ensure that they forward their on duty (10-36) information to DOCC Saskatchewan for entry onto the Computerized Integrated Information Dispatch System (CIIDS) via CPIC, fax or radio. We encourage all users to NOT use the radio system unless absolutely necessary as our frequencies are monitored and we should avoid informing the general public as to when you're working. It is mandatory within CIIDS to have the patrol unit and member logged into the system prior to attempting to obtain any CPIC queries.
In order for the dispatcher in DOCC to log a member onto the system, they "must" be provided with a car number (use RCMP assigned car numbers), regimental number for the member(s) in the vehilce, the shift time, and if applicable, the cellular number.
Once a member has logged on for the day, it then becomes the member's responsiblity to ensure that they log off (10-35) at the end of their shift. It is recommended this log off be done either via CPIC, or fax, and again, avoiding the radio if possible.
Form FDIV773(98-8) is to be used to forward 10-36/35 information via fax.
All references to the 10 code means the RCMP 10-Code and not the Municipal Police Department ten code.
B. UPDATING MEMBER INFORMATION
It is important that the member information contained in the CIIDS system be current, In order to ensure this, every member is responsible for completing form FDIV751(96-12) and forwarding an updated copy when the information changes or is no longer current. This information should be mailed or faxed to the Operations Commander, DOCC Saskatchewan, (fax number: (306) 780-5410), 6101 Dewdney Avenue, Bag Service 2500, Regina, SK S4P 3K7.
The Municipal Police Service will be responsibile for advising when members are no longer in their employ so the necessary changes can be made within the CIIDS system.
C. DOCC RESPONSIBILITIES
DOCC Saskatchewan will add and remove members and patrol units to the CIIDS system,
TITLE: MUNICIPAL PS - DOCC SASK RADIO/LOGGING PROTOCOLS
in order to facilitate patrol unit queries to the CPIC system, while on patrol.
Status keeping, receiving complaints from the general public, SGI drivers licence information and in office CPIC queries will continue to be the responsibility of the Municipal Police Department as in the past. The contacting of resources such as ambulances and tow trucks will continue to be the responsibility of the Municipal Police Service, except for declared emergency situations.
TITLE: MOBILE WORKSTATION PROCEDURES
The following procedures will ensure that all DOCC personnel are aware of the mobile
workstation operating procedures.
Mobile Workstation (MWS) Procedures
A. MEMBER SIGN ON
At the beginning of each shift members are required to:
1. Log on to CIIDS MWS, status 10-36 If the member has a portable, the portable number should be entered in the port id field. (Portable call signs bv01 - bv08, and mo09 - mo12)
- use the Remarks field to reflect the following information required by DOCC - shift info and cellphone number. eg A25 08-16 c696-5555
(DOCC will verbally acknowledge your Log on, there is no requirement for the member to re-acknowledge).
2. Activate monitors to observe other patrol unit activity within your unit and/or others.
B. STATUS KEEPING
Patrol Units should keep their own status unless circumstances dictate otherwise. MWS 10 codes to be used are as follows.
10-4 Acknowledge receipt of a "digitally" dispatched complaint from DOCC "if" immediate patrol not being made.
10-7 Out of service, member must enter location
10-8 In Service
10-11 Road side check (location field mandatory)
TITLE: MOBILE WORKSTATION PROCEDURES
10-17 En route, attending to the dispatch. In case of attending at other than the dispatch
location, complete location field to indicate (detachment, lockup, etc) i.e. a 10-11 resulting in breath testing, would require status change from 10-11 to 10-17, to facilitate testing at office. Location: 10-78 re impaired driver
10-23 At the scene of an event.
(Member shall maintain appropriate status i.e. in service, 10-8 to initiate deactivating the CIIDS event, DOCC will then deactivate the file upon member coming clear. The MWS does not have this capability)
10-33 Emergency, if activated by the function key, a voice confirmation to DOCC, when possible, shall follow. Failure by member to confirm an emergency situation by voice requires DOCC to initiate necessary "back-up" in support of this signal.
10-35 Off duty (events must be cleared) on-call information should be provided if required.
10-36 On duty and available
10-71 Used to initiate Digital Dispatch. eg. Moosomin Det 10-71, a patrol unit will acknowledge availability and dispatcher can forward the file. If the complaint involves violence or firearms the dispatcher should then advise the other units on the channel particulars of the complaint.
eg A470 attending domestic dispute 123 Main St Rocanville, Sask. firearms involved.
C. DISPATCHING VIA MWS
DOCC shall initiate voice contact with a patrol unit to advise that a "digital" dispatch is en route, using 10-71. The member shall acknowledge receipt (10-4) of the event if not immediately attending or en route (10-17) and at scene (10-23) if immediate action is taken.
Detachments - if a member is already responding from the office, include members
name/patrol unit at the beginning of the details as part of the posted information.
TITLE: MOBILE WORKSTATION PROCEDURES
Once a file has been "digitally dispatched" to a Patrol unit the lock on a file should not be broken without contacting the member or detachment, if a member is working on a 20 page 1624 and someone breaks his lock, he loses all his work. Dispatchers should only break the lock if they have contacted the member and know that it is okay, or if they know the member was off shift.
D. SELF GENERATED OCCURRENCES
Member shall create the event completing all information via the MWS. The event is automatically dispatched back to the member and handled in the same fashion as if dispatched by DOCC. The Remarks field Event automatically indicates MWS and should remain in this field for review purposes.
E. CPIC ACCESS
For CPIC queries that are street checks, change your status (10-11), show location in the location field. Hits on queries done by a member will appear in the "low priority notification"
Dispatcher -if the return has Caution codes or is a possible hit advise the member by a voice call telling him/her of the status.
Member shall then change status when completed.
Members doing investigational queries where the subject is not present will fill in the "location" field with SNP (Subject Not Present).
This will give the dispatcher a visual indication that a voice call will not be required.
Location VNP, indicates check of abandoned vehicles.
F. LOW PRIORITY NOTIFICATION FIELD
The following items will be appearing in the low priority notification field:
TITLE: MOBILE WORKSTATION PROCEDURES
G. HIGH PRIORITY NOTIFICATION FIELD
The following item will appear in this window
(Since the members will be updating their status from the MWS it is recommended that dispatchers enable their Patrol Unit Status Marquee, so changes are seen as the occur)
H. WARRANT CONFIRMATIONS/EXTERNAL MESSAGING/INTERNAL MESSAGING
Members with MWS may do their own confirmations, or may request DOCC. Include your unit's name and primary ORI as introductory text to any outgoing message. This will allow the responding agency to reply to your primary ORI in addition to the MWS unit. If the confirmation is requested from the MWS the member must send a copy to DOCC.
Members sending Internal messages to DOCC must sign the message with their name and Patrol Unit ID.
I. COMMUNICATION SERVER INTERRUPTION
DOCC shall verbally advise MWS users of a server "crash" and when restored, request members to initiate a status change in order to reactivate their MWS.
TITLE: RE-CREATION OF CIIDS ICON ON THE COMPUTER DESKTOP
At certain times it will be found that the CIIDS Icon (Police Car) is no longer available on the
computer desktop. The following procedures will allow the icon to be re-created.
The following shall be done from the main blue CIIDS for Windows screen: