Policy

All MPD purchased equipment shall be marked with the full Minneapolis Police designation before issue/use. Markings may include Mpls Police or MPD, if space or design of the equipment does not permit full Department lettering. MPD Stores will provide uniform markings and advise units of the best marking for equipment type. If equipment is purchased/shipped directly to a unit, the commander shall ensure that the items are brought to MPD Stores for Department marking before use. This directive does not apply to standard ‘police’ labeled clothing.

Policy

All employees are responsible for the department equipment they use. When an employee transfers from an assignment that issues individually-assigned equipment to an assignment that does not issue individually-assigned equipment, they shall return the equipment to MPD Stores. Any misuse or unauthorized use of City property or supplies shall constitute a violation of this policy.

Policy

Commanders desiring a reallocation of space within a police facility not solely under their command shall forward a written request to the Deputy Chief of the Central Services Bureau.

Policy

MPD personnel shall promptly report the need for repairs of any MPD-owned equipment to their commander for action. A note describing the exact nature of the problem, with samples if appropriate, shall be attached to the item needing repair.

Repairs or service to MPD-occupied buildings and offices should be made by completing a Work Order (PW-5401) and forwarding it to MPD Finance.

Policy

A log shall be kept at each precinct, unit or division that is assigned radios, shotguns or pagers.

Commanders shall ensure that any special equipment assigned to their command is inventoried at least annually or whenever needs dictate.

Policy

Employees shall notify their supervisor of the loss, recovery, or damage of City-owned property. The ensuing investigation is the responsibility of the respective commander. It is the employee’s responsibility to ensure that a CAPRS report is completed. City-owned equipment that is lost during an officer's response to an incident or crime should be reported as “LOSTPR” in the CAPRS report. Items misplaced shall be reported as a "MYSDIS" in a CAPRS report. A copy of the report shall be attached to a completed Inventory Record Change Form (MP-8001) and forwarded immediately to MPD Stores.

If property is recovered, the respective commander shall ensure that a Supplementary Report in CAPRS is completed and forwarded to MPD Stores. If the property is to be used as evidence in a criminal case, it shall be inventoried in the Property and Evidence Unit.

Policy

City-owned equipment that is individually issued to employees during their employment with the MPD shall be returned to MPD Stores upon termination of employment. Such items include, but are not limited to, badges, pagers, cell phones, keys, identification cards, etc. 

Policy

Reimbursement is not normally granted under the following circumstances:

• For property or equipment lost or stolen;
• For damage caused by employee negligence;
• For damage or loss to jewelry other than watches (watches up to $100.00);
• For personal property not previously approved for official use by a precinct or division commander;
• To the extent that the employee may be entitled to reimbursement from other sources;
• When the employee does not file a claim within 30 working days;
• When the employee’s claim is denied for other reasons.

Reimbursement is not granted for uniform alterations.

Policy

1. Document the incident and damage to the item in the related CAPRS report or via written memo including a detailed description of the activity during the incident and the cause of the damage. Attach reports and statements relating to the incident including your full name, assignment and badge number.
2. Attach original copies of payment or repair receipts (credit card, cash or check receipts). Receipts shall only reflect items claimed.
3. The item(s) shall be inspected by the employee’s commander or his/her designee, and a written statement from the commander or his/her designee describing the damage shall be included as part of the claim. During the claims process, damaged items may be requested for examination at any time.
4. Forward all claim documentation to Police Administration, Attention: Claims, Room 130, City Hall within 30 calendar days of the incident. If the Bureau Head or his/her designee approves the claim, it shall be forwarded to the MPD Finance Department for reimbursement.
5. If no reimbursement is granted, a memo of explanation will be sent to the claimant.

Policy

It is the MPD’s policy to permit memberships in professional, technical or special interest associations whose materials, services or activities benefit police services. To provide the broadest utilization of membership benefits, the MPD will:

1. Pay for organization/agency memberships with Bureau Head approval;
2. Reimburse individual memberships when such membership is more economical and efficient than organizational membership;
3. Pay for an individual membership if organizational membership is not available;
4. Pay for only one individual membership per association per unit, unless approved in writing by a Bureau Head or the Chief of Police;
5. Terminate payment or reimbursement if an employee is transferred from the unit covered by the membership, unless continued membership of the individual is approved in writing by a Bureau Head or the Chief of Police.

Policy

All MPD communications equipment is primarily intended for MPD business. Telephone lines may be monitored and/or recorded. Abuse of MPD communications equipment is subject to disciplinary action. For further reference, see the City’s cell phone policy.

Incoming telephone calls shall be answered as promptly as possible. When answering the telephone, employees shall identify themselves and their units by name. Employees shall be courteous and make every attempt to supply assistance or refer the caller to the proper person.

Policy

Forms not available on the MPD’s intranet site (MPD Net) may be ordered from MPD Stores on a Supply Requisition form (MPD-4022). All applicable information must be completed on the requisition form.

Policy

Requests for creating new forms and/or form revisions shall be made through the Operations Development Unit. After a review is completed, the requester shall be referred to either the City's forms vendor or the Operations Development Unit.

Requests for printing at the City’s Copy Center must be signed by an MPD supervisor with the appropriate funding source noted.

The purpose of utilizing mobile video recording (MVR) equipment in Minneapolis Police Department vehicles is to:

• capture video evidence for criminal, civil and traffic-related court cases.
• assist officers with recalling facts or other details captured by the equipment that will help them accurately articulate a chain of events when writing reports.
• allow supervisors to review the contents of the recorded media as a management tool within their chain of command.
• be used as a training tool for officer safety and best practices in the MPD.
• assist in the assessment of contacts between officers and the public by reviewing procedures and interpersonal actions.

The content of this policy will provide MPD personnel with guidelines and procedures for the use, management, access, retention, handling of evidence, degaussing, storage, and retrieval of recorded media captured by MVR equipment.

Minneapolis Police Department employees shall be responsible for performing assigned duties in accordance with the Mobile Video Recording (MVR) System Policy and the MVR Operational Guide. All MPD employees who have access to the MVR systems shall receive training on these systems. Training may include, but not be limited to: department policy, directives, electronic or traditional classroom education.

All stops and searches captured on the MVR are presumed to be legal and valid unless evidence indicates otherwise.

The term “officer” is used generically in this document and does not assume a level of rank, such as Patrol Officer. It includes all applicable sworn and non-sworn personnel.

Conditions of Use (Digital and VHS Systems)

1. MVR equipment installed in any MPD vehicle is the responsibility of the officer(s) assigned to that vehicle and shall be operated in accordance with MPD training, MPD policy and procedures, and the manufacturer’s recommendations.
2. When the activation indicator is illuminated, officers should be aware that activities are being recorded.
3. Before placing any MVR-equipped vehicle in service, officers shall conduct an MVR Equipment Check to ensure that the equipment is working properly.

1. MVR Equipment Checks conducted on the digital MVR system shall be categorized “90 Day Retention”.
2. The officer’s immediate supervisor shall immediately be notified of any missing or malfunctioning MVR equipment.

4. The driver shall wear the wireless microphone, verify that it is turned on and shall be responsible for ensuring that it is working properly throughout the shift.
5. Members activate MVR through any process which causes the MVR system to record video or audio data (Record Mode). Record Mode can be activated in the following ways:

1. Automatically, when a trigger event occurs;
2. Manually, by an officer via the wireless microphone, LCD monitor console, or digital video recorder (DVR) box in the vehicle’s trunk.

6. MVR equipment shall be in Record Mode:

• For every stop/contact where a motor vehicle is involved and shall record the stop/contact in its entirety.
• For domestic abuse incident interviews conducted inside or in close proximity to an MVR equipped vehicle.
• Any time a person is transported in a squad, regardless of the destination. This does not apply when an authorized ride-along is the only other person in the squad. When practical, officers shall begin recording when the person is placed in the squad, regardless if transportation begins immediately following activation.

7. The digital MVR system is preset to record video prior to activation. This MVR pre-event recording is included as part of the incident and is viewable during playback.
8. MVR equipment may be manually deactivated during non-enforcement activities, such as protecting accident scenes, traffic posts, and/or assisting motorists.
9. MVR equipment shall not be manually deactivated for an arrest, DUI, Use of Force, traffic stop or a “Significant Incident” as defined in this policy.
10. Any sworn supervisor can direct an officer to activate or deactivate MVR equipment.
11. Officers shall notify their immediate supervisor of any recorded event believed to be of value administrative review or training purposes.
12. Officers shall inform those who ask, that video/audio recording equipment is in use.
13. Nothing herein shall preclude MPD personnel from reviewing or using recorded data for the purposes of investigation or prosecution of crimes, or preparation of reports. Recorded data may only be used for training purposes with the approval of the Deputy Chief of Professional Standards.
14. An MPD employee who is captured on or referenced in any recorded media, may review such data and use the data for any purpose relating to his/her employment, provided such use complies with the Minnesota Government Data Practices Act, MPD policy and other laws.
15. All MVR recordings are the property of the MPD and original MVR recordings shall remain in the sole custody of the MPD, unless used in court as evidence, provided to an expert for analysis, or required to be provided to another by lawful order.
16. An MVR-equipped vehicle can be used for off-duty employment with supervisor pre-approval. MVR-equipped vehicles and use of MVR equipment are subject to all requirements as outlined for on-duty use.
17. Only MPD-issued videotapes, memory cards and microphones shall be used in MVR equipment. MPD Stores is responsible for distributing blank MVR storage and equipment to the precincts and units.
18. Disabling MVR equipment and/or altering, duplicating or destroying MVR recordings is prohibited, except for authorized personnel.
19. When reference is made to an MVR recorded event in a police report or supplement, the P# of the squad which captured the event shall be noted in the report.

MVR System - Supervisor Responsibility

1. Supervisors shall ensure that officers follow established procedures for the use and maintenance of MVR equipment, videotapes, and the completion of MVR documentation.
2. Supervisors shall periodically view recorded media to ensure proper procedures are being followed.
3. Supervisors may review the contents of the MVR systems, as a management tool within their chain of command.

MVR Digital System

1. Members shall categorize an event that has been recorded and for which a predetermined retention period has been set. Every recorded event shall be appropriately categorized in order to ensure proper data retention guidelines are followed.
2. Recorded events will be categorized using the following categories. Only one category can be chosen for each recorded event.

• 90 day retention;
• Citation;
• Arrest or DUI;
• Use of Force;
• Significant Incident

3. MVR digital recorded events categorized as Arrest, Use of Force or Significant Incident shall be uploaded at the MVR designated upload site by the officers assigned to the squad, prior to the end of their shift whenever possible.
4. When the display shows less than 4 gigabytes of available space, officers shall proceed to an MVR designated upload site to upload recordings.
5. When the police vehicle is within range of the MVR designated upload site, a wireless upload will occur and the MVR (digital) recordings will be automatically transferred over a wireless connection to a storage server.
6. In the event a memory card which contains recording(s) needs to be removed from the DVR, only Crime Lab personnel are authorized to remove the memory card.
7. Only Crime Lab Unit personnel are authorized to remove a memory card from DVR equipment.

VHS System

1. Only shift supervisors are authorized to possess a key to the MVR trunk vault.
2. Only shift supervisors are authorized to load or unload videotape into the MVR.
3. When the 30-minute warning light appears on the MVR overhead console display, officers shall notify their immediate supervisor and arrange to have the MVR videotape inventoried and replaced.
4. If the original MVR recording is of evidentiary value, it shall be inventoried in the Property & Evidence Unit prior to the end of the officer’s shift which encompasses the recorded event. A recording that is of evidentiary value includes the following:

1. Significant Incident;

2. Arrest;
3. DUI;
4. Use of force

5. MVR (VHS) recordings of non-evidentiary value will be stored at the precinct/unit where issued for a period of 1 year and then may be degaussed and re-used.
6. Exercise caution to ensure that repeated viewing of an original VHS recording is kept to a minimum. Repeated viewing may result in the quality of the recording to become degraded.
7. In the event of a Critical Incident, Crime Lab personnel shall collect MVR VHS recorded media from all squads at the scene.

1. In order to preserve the quality and integrity of the videotape, the recording shall not be reviewed in the squad car prior to collection.
2. A duplicate copy of the VHS recorded media will be made as soon as possible by Crime Lab personnel.
3. At the request of the Involved and/or Witness Officers, the Lead Investigator for the Critical Incident shall provide them an opportunity to view a copy of the MVR recorded media prior to giving a statement and completing a report.

VHS System - Supervisor Responsibility

1. Patrol supervisors are responsible for the installation, removal and storage of VHS videotapes.
2. Precinct/Unit commanders or their designees are responsible for the usage, labeling, storage, degaussing, and recycling of VHS recordings intended for patrol use.
3. Unless otherwise noted, MVR VHS videotapes stored at precincts shall be retained for one year and then may be degaussed and/or reused.
4. Videotapes that have been degaussed three times shall be destroyed.
5. Supervisors shall maintain a logbook to ensure inventory control of videotapes.
6. Each precinct/unit shall track the installation/removal of MVR videotapes via the Precinct/Unit MVR Videotape Log (MP-8898).

Property Inventorying MVR (VHS) Videotapes

1. Mobile Video Recording (MVR) videotapes shall be property inventoried when the MVR equipment was in use in the following situations:

1. Significant Incident;
2. Arrest;
3. DUI; and
4. Use of force

2. If the squad is involved in or responds to a Critical Incident:

1. Crime Lab Unit personnel will remove and property inventory MVR videotapes from all squads at the scene.
2. MVR videotapes property inventoried for reasons related to a Critical Incident shall only be permanently released or destroyed by the Property and Evidence Unit at the direction of the Commander of the Internal Affairs Unit.

3. In cases where evidence is recorded, it shall be noted on the videotape and in the CAPRS report.

MVR Equipment Coordinator

1. Each patrol precinct/unit will have a designated MVR Equipment Coordinator.
2. The MVR Equipment Coordinator will:

3. Ensure that all MVR equipment in vehicles is operational and accounted for;
4. Follow up when equipment and microphones are reported missing or in need of repair;
5. Conduct and/or coordinate training for personnel regarding MVR operations, MVR desktop software, and policy/procedure updates;
6. Liaison between the precinct/unit, the Business Technology Unit (BTU) and the Radio Shop;
7. Ensure videotapes from the MVR (VHS) system are maintained appropriately and requests for video duplication are handled in a timely manner.

MVR Equipment Maintenance, Repair and Replacement

1. Employees shall directly notify their immediate supervisor as soon as practical of any:

• Missing equipment.
• Damaged equipment.
• Malfunctioning equipment (including when either or both of the audio or video recording functions is malfunctioning).

2. The notification to the supervisor must be made without unnecessary delay.
3. As soon as practical, employees shall submit a ticket with the IT Service Desk to report the problems (in accordance with P&P 4-219).
4. Employees shall document in the Police Report any problems they encountered with their MVR while responding to an incident. The employee shall also note if they are using a replacement squad because of the issues. If a Police Report is not required, the employee shall document the problems in CAD.
5. Supervisors shall ensure that appropriate measures are taken when informed of any problems with the equipment. This includes ensuring a ticket is submitted for the problematic equipment (P&P 4-219), arranging for any replacements or alternatives, and making any necessary reports.

Requests for Duplication of MVR Recordings

1. Requests by MPD personnel for duplication of MVR video for purposes of official MPD business shall be directed to the Crime Lab Video Forensics section via submission of the Crime Lab Video Request for Services form (MP-9069).
2. Requests by MPD personnel for duplication of MVR video for non work-related purposes (e.g. teaching, personal reasons) shall be submitted to the Records Information Unit and are subject to the Minnesota Government Data Practices Act and City of Minneapolis data charges.
3. Requests made by the public for MVR video will be processed by the Records Information Unit (RIU), in conjunction with Precinct Supervisors, the Crime Lab Video Forensics Section and the Public Information Office.

1. Records Information Unit responsibilities:

1. Determine nature of the request;
2. Ensure video is not part of an active criminal or internal investigation;
3. Submit Crime Lab Video Request for Services form (MP-9069) to the CLU requesting duplication of video;
4. Receive recorded media intended for release;
5. Ensure the Public Information Office reviews video prior to release to make certain that only public information is released;
6. Notify requestor video is ready;
7. Collect fees and release video.

2. Precinct Supervisor responsibilities when an MVR VHS videotape recording is required for duplication:

1. Receive request from Records Information Unit;
2. Locate and property inventory videotape;

• If no CCN exists, one shall be generated and a CAPRS report completed using the code MISC.

3. Notify RIU via e-mail if the videotape is already inventoried under another CCN, if it no longer exists, or cannot be located.

3. Crime Lab Video Forensics Section responsibilities:

1. Receive requests via Crime Lab Video Request for Services form (MP-9069).
2. Process requests according to Crime Lab Division SOP’s.

4. Public Information Office responsibilities:

1. Coordinate with Records Information Unit to manage requests.
2. Review all videos to be released.

This policy covers Department-issued and City-issued technology, including software, and hardware such as computers and accessories, phones, etc.

The purpose of this policy is to:

• Direct members how to procure technology and related services.
• Direct members how to report issues with their technology.
• Ensure compliance with City Information Technology (IT) and Business Technology Unit (BTU) standards.

Procurement and Access

The procurement of all technology and related services such as programming or consulting will be facilitated through City IT, in coordination with MPD’s Business Technology Unit (BTU). Members shall only use approved software on any MPD or City device.

1. Any precinct, unit or division wishing to obtain or implement hardware, software or services, or request permissions or access to programs, shall submit a ticket by calling extension x2525, using the CityLife portal (also called ServiceNow), or emailing the service desk directly ITServiceDesk@minneapolismn.gov. City IT will coordinate with BTU to evaluate the request and confirm proper approvals are secured.

2. It is the responsibility of the requesting precinct, unit or division to make all necessary budgetary arrangements and ensure the procurement has been approved prior to submission.
3. All Department-issued and City-issued technology is owned by the City and may be reallocated, replaced and managed as needed. Technology obtained through grant programs shall be maintained according to the grant guidelines.

Issues With Technology

1. Members who are encountering issues with technology, including software, hardware such as computers and accessories, phones, etc. issued by City IT or the Business Technology Unit (BTU), and any issues with technology installed in a City or Department vehicle, shall report their issues by submitting a ticket with the IT Service Desk.

1. Tickets can be submitted by calling extension x2525, using the CityLife portal (also called ServiceNow), or emailing the service desk directly ITServiceDesk@minneapolismn.gov.

2. This includes issues with body worn cameras, in-car cameras, squad computers, desktop or laptop computers, cell phones, desk phones, computer accessories, etc.
3. Issues include, but are not limited to, malfunctioning devices, connectivity issues, battery or charging problems, GPS issues, uploading issues, problems with programs or software, etc.

2. The IT Service Desk will determine the best course of action to resolve the issue, and members shall follow any directions from the IT Service Desk regarding next steps.

1. Members shall not drop vehicles off at the Radio Shop without first submitting a ticket and being directed to bring the vehicle to the Radio Shop.

With the goal of enhancing accountability and public trust this policy will provide MPD personnel with procedures for the use and management of Body Worn Camera (BWC) equipment, and the access, retention, storage, and retrieval of recorded media captured by BWC equipment. The purpose of BWC equipment use by Minneapolis Police Department employees is to accomplish the following:

• Enhance accountability and public trust by preserving a record of employee interaction with citizens.
• Capture digital audio-video evidence for criminal, civil and traffic-related court cases.
• Assist employees by providing a record independent from their perceptions and recollections.
• Serve as a training tool for employee safety and best practices in the MPD.
• Assist in the assessment of contacts between employees and the public by reviewing procedures and interpersonal actions.

Restrictions

Intimidation

1. The BWC shall not be used for the purpose of intimidating or discouraging an individual from observing police activity, making appropriate inquiries to the police or making a complaint.
2. In no event shall any recording be used or shown for the purpose of ridiculing, embarrassing or intimidating any person.

Interactions only with employees

Employees shall not use the BWC to record interactions solely with or among other department employees, except in circumstances for which BWC activation is appropriate in accordance with this policy.

Personal use

Employees shall not use the BWC for personal use or for any other reason inconsistent with this policy.

MPD equipment

Employees shall only use BWCs and BWC equipment authorized by the Department.

Disabling or interfering with BWCs

Disabling BWC equipment, intentionally interfering with audio or video recording capabilities, and altering, duplicating, deleting or destroying BWC recordings are prohibited, except by Authorized BWC Personnel in the course and scope of their lawful job duties and in accordance with record retention laws and policies and the provisions of this policy. Only the Chief or the Chief’s designee can designate such Authorized BWC Personnel.

Surveillance of protected activities

The BWC shall not be activated solely for the purpose of surveillance of, or identification of individuals engaged in constitutionally protected activities conducted in a lawful manner.

Facial recognition

BWC data shall not be:

1. Used to create a database or pool of mug shots.

2. Used as fillers in photo arrays.
3. Searched using facial recognition software. This does not prohibit the MPD from using facial recognition software to analyze the recording of a specific incident when an investigator has reason to believe that a specific suspect, witness, or person in need of assistance was recorded.

Use by non-employees

Employees assigned a BWC shall not permit any non-employees to use or wear the BWC.

Informing the Public that a BWC is in use

1. When feasible, employees are encouraged to inform members of the public that they are being recorded.
2. If asked, employees should inform those inquiring that audio-video recording equipment is in use, unless doing so would be unsafe for the employees or members of the public.

Training

1. Employees shall complete department authorized training in the use and operation of the BWCs prior to being assigned a BWC.
2. Only those employees that have been issued a BWC and have received the department authorized training may operate a BWC.
3. All MPD employees who use the BWC data storage and access systems shall receive training on these systems and this policy, prior to being granted access.

Wearing and Using the BWC

1. Employees assigned a BWC shall use it in accordance with MPD training, MPD policies, and the manufacturer’s recommendations.
2. Employees shall wear the BWC in accordance with MPD training, using mounting equipment provided by the Department.

1. Employees shall wear the BWC facing forward on the outermost garment, in the chest area.
2. The Commander of the Technology and Support Services Division (who oversees BTU) may authorize additional mounting equipment options, and may authorize alternate camera mounts with different placements for specialized units or functions.

BWC Program Responsibility

Business Technology Unit responsibility

The Business Technology Unit (BTU) is responsible for the technological aspects of the BWC program, including device support and maintenance.

Quality Assurance responsibility

The BWC Quality Assurance Unit is responsible for oversight of the BWC program, and ensuring policy adherence.

Policy Review and Audit

1. The BWC program and any associated policy shall be reviewed as necessary, with any appropriate changes occurring as a result of input received.
2. The BWC program shall be independently audited in accordance with existing law.

Duty to Report

All employees are required to report misconduct or other violations in accordance with the Professional Code of Conduct chapter (P&P 5-100) and the Internal Affairs Process chapter (P&P 2-100).

Assignment of BWCS

BWCs shall be assigned to all sworn personnel. BWCs may be assigned to other personnel at the discretion of the Chief of Police or the Chief’s designee.

Failure to Adhere to Policy

Employees failing to adhere to this policy or applicable laws regarding the use of BWCs and any associated data, including but not limited to restrictions regarding accessing such data, will be subject to discipline, up to and including termination.

Employee Responsibilities

Charging BWCs

Employees assigned a BWC shall keep it charged between shifts so that it is fully charged at the start of a shift.

Wearing and Powering on BWCs

In Uniform

Employees assigned a BWC and working in uniform (Class A, B, C or D in accordance with P&P 3-100) shall wear the BWC and keep it powered on at all times during their shift when they can reasonably anticipate that they may become involved in a situation for which BWC activation is appropriate in accordance with this policy.

1. This also applies to employees working at a precinct front desk.
2. When working in uniform, investigators assigned a BWC shall wear it in accordance with the rest of this policy.
3. The Lieutenant or Commander who oversees units focused on outreach and engagement (such as the SROs or CET) may determine whether their employees should wear the BWC when working in such assignments in soft uniforms (anything other than the full uniform that bears police markings).

Plainclothes

1. Employees do not need to wear the BWC during plainclothes operations in which displaying or indicating their status as a law enforcement employee would compromise the operation.
2. Investigators working in plainclothes who are assigned a BWC are not required to wear it during their on-duty shift except when executing a search warrant in the field or when ordered to by a supervisor.

Entering Centers for Domestic or Sexual Violence Victim Advocacy

Employees may power off their BWCs when entering a center for domestic or sexual violence victim advocacy or assistance, as long as there will not be any interaction with a suspect. Employees shall activate as needed in accordance with the section on Activation (including for interviews).

Legal Proceedings

Employees shall power off the BWC for any court-room proceeding, deposition or similar legal proceeding. Employees shall power on and activate the BWC if a situation requiring BWC activation occurs.

Startup Checks

Employees shall conduct a BWC Startup Check to ensure that equipment is working properly at the beginning of their shift.

1. A Startup check consists of activating the camera to ensure it properly enters Record Mode, and does not display any error indicators. Any problems shall be handled in accordance with the section on Problems with the BWC Equipment.
2. Once the BWC is activated for the startup check, the employee shall state the following information prior to deactivating:

• Name
• Badge number (or Employee ID for civilians)
• Call sign

Problems with the BWC Equipment

1. Employees shall directly notify their immediate supervisor as soon as practical of any:

• Missing equipment.
• Damaged equipment.
• Malfunctioning equipment (including when either or both of the audio or video recording functions is malfunctioning).
• A loss of BWC battery power (including if the BWC does not maintain a charge for a full regularly assigned shift).

2. The notification to the supervisor must be made without unnecessary delay.

3. As soon as practical, employees shall submit a ticket with the IT Service Desk to report the problems (in accordance with P&P 4-219).
4. Employees shall document in the Police Report any problems they encountered with their primary BWC while responding to an incident. The employee shall also note if they are using a replacement BWC. If a Police Report is not required, the employee shall document the problems in CAD.

BWCs and Mobile Video Recording (MVR) equipment

1. Employees equipped with a BWC who are operating a squad car equipped with Mobile Video Recording (MVR) equipment shall activate the MVR equipment as required by policy and shall also activate the BWC in compliance with this policy.
2. Employees wearing a BWC are not required to wear an MVR microphone.

BWC Activation

Required BWC Activation

1. Employees shall activate their BWC for the following circumstances:

1. When dispatched or assigned to a call, BWC activation shall occur at least two city blocks away from the call for service location. If dispatched or assigned to a call less than two city blocks away, BWC activation shall occur immediately. This includes assisting squads.
2. When self-initiating a call, as soon as possible and prior to contacting a person or exiting a squad.
3. Prior to taking any law enforcement action.
4. Prior to making an investigatory contact.
5. When any situation becomes adversarial.
6. Prior to assisting a citizen during in-person encounters, other than when providing basic verbal assistance (such as giving directions).
7. When directed to activate the BWC by a supervisor.

2. Examples of situations that require BWC activation include, but are not limited to:

• Any in-person contact (including at a precinct front desk, during a business check or while on a foot beat) involving allegations of criminal activity, suspicious or unlawful behavior, a complaint of misconduct or another situation requiring BWC activation. This includes any contact with a reporting person, victim, suspect or witness, subject to the exceptions listed in the BWC deactivation section.
• Traffic stops.
• Suspicious Person stops.
• Suspicious Vehicle stops.
• Any vehicular response requiring emergency driving or emergency response as defined by MPD P&P 7-401.
• Vehicle pursuits.
• Work-related transports not involving a ride-along or another City employee in their official capacity as a City employee.
• Any search, including but not limited to searches of vehicles, persons, and buildings. This excludes searches that could reasonably involve the presence of explosives, and also excludes protective sweeps for explosive devices.
• Any contact involving physical or verbal confrontations.
• When advising a person of their Miranda rights, if not inside of a secure law enforcement facility where the MPD is already creating a recording through another approved method.
• Any use of force situation. If a BWC is not activated prior to a use of force, it shall be activated as soon as it is safe to do so.
• Any tactical entry or forced entry into a building.
• Supervisors responding to a scene.

BWC Pre-Event Recording

The digital BWC system is present to record and store video only (no audio) prior to manual activation. The pre-event recording is included as part of the incident and is viewable during playback.

Changing Situations

If a situation changes to require BWC activation, the employee shall immediately activate the BWC as soon as it is safe to do so.

Strip Searches

1. All strip searches shall be recorded by at least one person present during the entirety of the strip search, including all pre-search instructions provided to the person being searched.
2. The camera shall be positioned to ensure that only audio data is collected and that the person being searched is not captured on video.

Failure to Activate

1. If there is a failure to activate the BWC or a late BWC activation in any of the above situations, the employee shall document the reasons for the failure in the Police Report.
2. If a report will not be prepared, the reason(s) for the failure to activate shall be documented via added remarks in CAD, as soon as practical.

8. If the employee does not have access to a squad computer to enter added remarks directly, the employee shall contact MECC via radio or phone as soon as practical and request the reason(s) be added to the remarks in CAD.
9. Documentation shall begin with the following prefix: “BWC:”, followed by the reason for the documentation.

Community Meetings

Unless BWC activation is otherwise required by this policy, employees do not need to activate BWC for community meetings or other community engagement activities.

Phone Calls

Nothing in the BWC activation policy precludes an employee from using the BWC to record phone calls the employee deems to be of evidentiary value or that otherwise require BWC activation.

Interviews with Crime Victims

1. If employees will be conducting an initial interview with a crime victim, employees should advise the victim the camera will be on and activated during the interview.

1. If the victim raises concerns with the camera being activated, the employee can turn the camera away to record audio but avoid capturing the video.

2. If the victim refuses to be interviewed with the camera on, the employee may deactivate or power off the camera to facilitate the interview.

2. Employees conducting interviews with victims of domestic or sexual violence should be especially sensitive to the victims’ requests (in accordance with the section on temporarily deactivating at the request of a party being contacted).
3. If the employee had their camera powered off inside a center for domestic or sexual violence victim advocacy or assistance, they should power it on and activate it for the interview.

BWC Deactivation

Event Conclusion

Once activated, the BWC shall be left in the record mode until the conclusion of the event. The conclusion of the event occurs when either the employee or citizen(s) has left the scene or a detention or transport has concluded.

1. If a transport involves a transfer of custody, the event is not concluded until the transfer is complete.
2. When transporting arrestees to the Hennepin County Jail the transfer may be considered complete at the intake door from the secure garage (threshold of the person sally port) unless custody has been transferred prior to that point, and the BWC may be deactivated in line with Jail policy. It should remain activated within the garage while MPD retains custody and should be reactivated at the intake door if custody is returned to the MPD (it should be activated while arrestees are in the squad, being unloaded or loaded, and while being escorted to or from the person sally port).
3. The BWC may be deactivated if an event has otherwise concluded but the employee remains at the scene to prepare reports or for another similar reason not involving a situation requiring BWC activation.

Critical Incidents- BWC Deactivation

All involved, witness and escort employees in a Critical Incident shall leave their BWCs activated while on scene, until directed by the Incident Commander.

1. BWC deactivation must be after the Public Safety Statement is completed, at a minimum.
2. When the BWCs have been deactivated in accordance with this section on Critical Incidents, employees may reactivate if they feel it is appropriate, and shall reactivate if otherwise required by the BWC policy.

Early BWC Deactivation

Narration

1. If a BWC is deactivated prior to the conclusion of an event, employees shall describe the reason by narration prior to BWC deactivation.

2. Supervisors deactivating to perform administrative functions shall describe the reason by narration prior to each BWC deactivation, or following reactivation.

Documentation

1. If a Police Report will be prepared, the early BWC deactivation and the reason shall also be documented in the employee’s Police Report or statement in the Police Report.
2. If a Police Report will not be prepared, the reason for the early BWC deactivation shall be documented via added remarks in CAD, as soon as practical.
3. If the employee does not have access to a squad computer to enter added remarks directly, the employee shall contact MECC via radio or phone as soon as practical and request the reason(s) be added to the remarks in CAD.
4. Documentation shall begin with the following prefix: “BWC:”, followed by the reason for the documentation.
5. Supervisors performing administrative functions may summarize their associated BWC deactivations in any required documentation.

Accidental BWC Deactivation

1. If an accidental BWC deactivation is discovered, the BWC shall be immediately reactivated.
2. The employee shall narrate the cause of the accidental BWC deactivation as soon as practical, and shall follow the other reporting requirements for early BWC deactivations.

Stabilized Events

Notwithstanding the above, once an event has been stabilized and if the employee reasonably believes there is no longer audio or visual evidence to capture, and that none of the circumstances requiring BWC activation will likely occur, the BWC may be deactivated during activities such as:

• Monitoring assigned traffic posts.
• The incident or event is of such duration that it is necessary to deactivate the BWC to conserve power or storage.
• When guarding suspects/arrestees at a hospital, if no other BWC activation conditions are met (it must be activated if there will be contact with the suspect, if the suspect becomes combative, etc.).

Temporary BWC Deactivation

When an event is still in progress, the BWC may be temporarily deactivated in the following situations, but shall be reactivated as soon as the temporary situation has concluded or if ordered to by a supervisor, and the required documentation shall be made according to the Early BWC Deactivation section:

1. To protect the identity of an employee in an undercover capacity or during a plainclothes operation.
2. To protect the identity of a confidential informant.

3. If a request is made for a BWC to be turned off by a party being contacted, the employee should take into account the overall circumstances and what is most beneficial to all involved, before deciding to honor the request. For example, an employee may choose to turn off the BWC if its operation is inhibiting a victim or witness from giving a statement. Factors to consider may include the type of call and the vulnerability of the victim, such as the victim of a sexual assault.
4. When ordered to by a supervisor. Both the employee and supervisor shall document the reason for the BWC deactivation as described in the Report Writing section of this policy.
5. During Operation 100s, only if the Incident Commander deems it necessary.

BWC Uploading and Classification

Classify events prior to upload

Classification should be done shortly after the recorded incident is concluded, and must be done prior to upload at the end of the employee’s shift.

Upload at conclusion of shift

Employees shall upload all BWC digital data at the conclusion of their shift at the BWC Designated Upload Site. Employees shall place their BWC in the assigned docking stations or utilizing other department approved BWC uploading procedures.

Classify events as appropriate

Employees shall classify recorded events as appropriate, based on the options available under the classification and storage software. Multiple categories are permitted, and all applicable categories shall be used.

1. Each category used for classification is assigned a status of Public (subject to review) or Nonpublic (subject to review), based on statutory requirements. Requests for data (including by data subjects) will be handled according to the section in this policy related to Data Requests (in accordance with the Government Data Practices Act and any other applicable laws).
2. Data may be held longer than the stated retention period in accordance with litigation or other legal requirements, and the section on BWC data retention [IV-C-2].

Classification options

1. The following classification options will be used:

2. Category guidelines

Training: This category should be used for events that were recorded during BWC training sessions, or other training sessions where BWC data may have been recorded.

Rcrt Academy: This category is for the sole purpose of Academy staff and Recruits/Cadets for scenario video feedback. Video with this category shall not be accessed by anyone other than Academy staff, Recruits, Cadets and other personnel with written permission from the Academy Lieutenant or Training Division Commander.

Accidental Activation: This category should be used for inadvertent BWC activations by the employee or inadvertent BWC activations by an automatic signal.

Startup Check: This category should be used for the required BWC equipment checks done at the start of a shift, known as Startup Checks.

Non-Evidence/General Recording: This category should be used for recordings not associated with a call for service, offense, citation, arrest, report of crime or citizen complaint. This category includes events such as general citizen contacts that would not be considered evidence.

Protected: This category should be used for all recordings requiring a special level of review such as those capturing individuals with confidential identities or proprietary tactics.

Citizen Complaint: This category should be used for all recordings associated with any complaint of misconduct by a member of the public.

Evidence: This category should be used for all recordings associated with any call for service, offense, citation, arrest or report of crime (regardless if the employee believes there is actual evidence captured in the recording). This includes all related recordings such as witness statements or other evidence.

Use of Force-Other: This category should be used for all recordings in which use of force was captured, where the force resulted in no injuries or less than substantial bodily harm.

Use of Force- Substantial Bodily Harm: This category should be used for all recordings in which use of force was captured, where the force resulted in injuries with substantial or greater bodily harm or death.

Police Discharge of a Firearm: This category should be used for all recordings in which a firearm discharge by an employee was captured, where a notice is required under MN Statute section 626.553 Subd. 2.

Significant Event: This category should be used for any recording related in any way to any one of the following situations:

• Critical Incident;
• Homicide;
• Pursuit involving injuries or significant property damage;
• Squad accident involving injuries or significant property damage;
• Man-made or natural disaster or act of terrorism;
• Any event that an employee or supervisor believes should be brought to the immediate attention of police command staff.

Non-BWC Data: This category should be used for any file uploaded that is not a BWC video recorded by MPD.

Citizen Evidence: This category should be used for digital evidence collected by a citizen from their own digital collecting device (such as a cell phone or home/business security camera) and shared with the MPD for use in a criminal, civil, or internal investigation.

Case number required

1. Whenever a case number is generated from CAD, employees shall provide the associated case number in the “ID” field for all related BWC data.
2. When entering the number, it shall be in the standard format of YY-xxxxxx (ex. 16-123456). The dash must be included and no other characters will be used.

Protected category requirement

If the Protected category is applied, the employee shall also add “PROTECTED” at the beginning of the Title field.

Critical Incidents- BWC Uploading and Custody of BWC equipment

1. When MPD is the investigating agency, involved and witness employees shall maintain custody of their BWC equipment until Crime Lab personnel take custody of the equipment.

1. In the event that any employees will be photographed as part of the Critical Incident protocol (see P&P 7-810), the employees shall leave BWC equipment on their uniform until photographs are completed.
2. Authorized Crime Lab personnel are responsible for ensuring any BWC recordings are properly uploaded.
3. Once all uploads are completed, the assigned investigators are responsible for authorizing release of the BWC equipment to the employee or other appropriate personnel.
4. In the event that Crime Lab personnel are unable to take custody of the BWC, the on-scene investigators shall coordinate custody of the BWC and BWC uploading.

2. When MPD is the investigating agency, all employees except involved and witness employees shall upload their BWC data as soon as possible, and no later than the conclusion of their shift.
3. When investigation of the incident is transferred to another law enforcement agency, employees shall provide their BWC to the investigating agency.

1. BWC uploading and physical custody of the BWC will be coordinated with assigned MPD investigators and the outside investigating agency.

Report Writing

Data Access

BWC data may only be accessed in accordance with the section [IV-D] relating to Access of BWC Data and Request for Duplication of Recordings.

Critical Incidents

1. To capture and document the employees’ perceptions and recollections uninfluenced by outside sources, and in accordance with P&P 7-810, involved and witness employees in Critical Incidents are prohibited from reviewing BWC data prior to making their initial Police Report or statement in the Police Report.

2. If authorized by the Chief of Police to review BWC data after making their initial Police Report (in accordance with P&P 7-810), employees may add an additional narrative text after review but shall not alter the initial report.

Incidents that are not Critical Incidents

In incidents that are not Critical Incidents, employees may review BWC data in accordance with the section [IV-D] relating to Access of BWC Data and Request for Duplication of Recordings.

Items about BWC usage to include in Police Report

When a Police Report is made, employees shall document the following in the Police Report:

• Whether audio or video evidence was gathered relating to the events described in the report.
• If the BWC was not activated as required and the reason(s) why not, in accordance with the Activation section.
• Early or accidental BWC deactivations, in accordance with the BWC Deactivation section.
• Any malfunction of the BWC equipment in either the recording or the BWC uploading of the event.

Off-Duty

Use BWC during uniformed off-duty work

Employees assigned a BWC shall use it during off-duty work when it is within the city of Minneapolis and involves wearing the MPD uniform, and the employees shall comply with the BWC policy.

BWC use only for approved jobs

BWC use is allowed only for approved off-duty jobs within the City of Minneapolis, and only while wearing the MPD uniform.

BWC uploading from off-duty shifts

1. Any audio/visual data regarding a use of force by or against an employee, or data that may be evidence in a criminal case, shall be uploaded in the same manner as if the data had been collected while on duty.
2. All other BWC data recorded during off-duty work shall be uploaded by the start of the next on-duty shift, as long as the shift begins within 48 hours of the off-duty shift’s conclusion. If the next on-duty shift will begin more than 48 hours later the BWC data shall be uploaded at the conclusion of the off-duty shift.

No MPD BWC use for other agencies

Employees shall not use MPD-issued BWCs while working for another law enforcement agency.

Supervisor Responsibilities

Ensure employees follow procedures

Supervisors shall ensure that employees follow established procedures for the use and maintenance of BWC equipment and the completion of BWC documentation. This includes the review of BWC recordings and usage data to ensure proper procedures are being followed.

1. The MPD BWC Quality Assurance Unit will establish minimum standards for the review of BWC recordings and usage data. Supervisors shall conduct reviews of BWC recordings and usage data in accordance with these standards.
2. Precinct Inspectors or Division Commanders may also direct their assigned personnel to conduct additional reviews of BWC recordings and usage data that exceed the standards established by the MPD BWC Quality Assurance Unit.

Problems with the BWC Equipment

1. Supervisors shall ensure that appropriate measures are taken when informed of any problems with BWC equipment. This includes ensuring a ticket is submitted for the problematic equipment (P&P 4-219), replacing the BWC in question, and making any necessary reports.
2. Supervisors shall ensure that employees who report an inoperable or damaged BWC are provided with a temporary or replacement BWC as soon as possible, and no later than the beginning of the employee’s next shift. This may include temporarily assigning a BWC that is not currently being used.

1. If the employee is using a replacement BWC (as provided by BTU or the employee’s supervisor), the supervisor shall reassign the recordings accordingly.

Respond to the scene

Supervisors shall respond to the scene of an incident that requires immediate retrieval of recordings and ensure appropriate BWC uploading procedures are followed.

For incidents not considered to be Critical Incidents

1. If an incident occurs that involves substantial or great bodily harm or death, the supervisor shall ensure that employees upload the video as soon as practical following any necessary duties as part of the incident.
2. The same requirements shall apply to any incident the supervisor deems may be a “high profile” incident.

3. For Critical Incidents

For Critical Incidents, equipment and BWC uploading shall be handled according to the Uploading and Classification Critical Incident section.

Review pertinent video

When conducting force reviews or complaint investigations, supervisors shall view any pertinent BWC video as part of the review (including from witness employees). Supervisors may also view pertinent BWC video as part of any other administrative review.

BWC Data Retention

1. Data will be maintained in a storage system designated and approved by the Department.

1. All data will be backed up by the storage system vendor.
2. BWC video shall only be stored in a database that is CJIS compliant (such as evidence.com, One Drive and Share Point). BWC video shall not be stored in any other database, including the M drive. Video shall not be stored on computer hard drives.

2. Data will be retained in accordance with applicable law, this policy and the City of Minneapolis records management retention schedule. Data may be retained past the scheduled retention period as required by MN Statute section 13.825 Subd. 2 and Subd. 3.

Access to BWC Data and Requests for Duplication of Recordings

Permission required for system access

Access to the department authorized storage system shall only be granted with written permission from the Commander of the Technology and Support Services Division (who oversees BTU), and only for a legitimate, specified law enforcement purpose.

1. Such permission must include the level of access to be granted to the individual, and any other restrictions that should be placed on the access.

2. BTU will periodically review the user access list to ensure that access levels are appropriate and have been duly authorized.

Documentation of access data

All accesses of the BWC data are documented automatically as part of the BWC vendor technology. Data relating to accesses will be retained in accordance with the retention schedule for the BWC data that was accessed.

Requests for data

All BWC recordings are the property of the MPD and original BWC recordings shall remain in the sole custody of the MPD, unless necessary for the preparation of civil, criminal or administrative matters, used in court as evidence, provided to an expert for analysis, provided to another law enforcement agency in the scope of their investigation, if required to be provided to another by lawful order or as may otherwise be required by the Minnesota Government Data Practices Act or other applicable law.

MPD records policy

All recordings shall be handled in accordance with the Department’s records policy (P&P 4-501).

Public requests and redaction

Public requests for BWC recordings shall be referred to the Records Information unit and will be considered in accordance with the Minnesota Government Data Practices Act or other applicable law.

1. The public, non-public or confidential status will be determined in accordance with the Minnesota Government Data Practices Act or other applicable law in relation to the specific request.
2. Data subjects have access to the data, subject to the conditions in the Data Practices Act, including but not limited to MN Statute section 13.825.
3. All entities with access to the BWC data are responsible for ensuring they only handle and release BWC data in accordance with MN Statute.

4. Any necessary and lawful redaction or other editing of BWC recordings shall only be completed by Authorized BWC Personnel in the course and scope of their lawful job duties and in accordance with record retention laws and policies and the provisions of this policy.

1. Data that are public may be redacted or access may be withheld to portions of the data if those portions of data are clearly offensive to common sensibilities, in accordance with MN Statute section 13.825 Subd. 2.
2. If a data subject requests that data or requests that it be made public, data on other subjects will be redacted as required by MN Statute section 13.825, where applicable.
3. The original recording shall remain intact and stored within the department authorized storage system in accordance with record retention laws and policies.

MPD personnel requests for duplication

Requests by MPD personnel for duplication of BWC data for purposes of official MPD business shall be directed to the Records Information unit.

Outside agency requests for duplication

Requests by outside agencies for duplication of BWC data shall be directed to the Records Information unit.

Sharing BWC recordings with public or employees

Employees shall not share BWC recordings with any member of the public or any MPD employee, unless it is required in the performance of their official duties and consistent with State and Federal law.

Sharing with partner agencies

Employees may share BWC data with a partner agency when:

1. The BWC data is shared with an approved City department or government agency as necessary for the administration and management of programs specifically authorized by the legislature or local governing body or mandated by the federal government.

2. The BWC data is shared to aid another public safety agency in an active criminal investigation.

Data use for training purposes

Recorded data may only be replayed or displayed for training purposes with the approval of the Deputy Chief of the Professional Standards Bureau. Nothing herein prohibits Training Division staff from having access to BWC recording for the purpose of planning training.

Data access by employees or as evidence

Data captured by a BWC may be accessed by an employee, provided the access is in the course and scope of the employee’s lawful job duties, or used as evidence relating to:

• Pending administrative, criminal, civil or traffic matters;
• A complaint of misconduct made against an employee
• In situations where evidence of employee misconduct is discovered during the course of authorized access (including force reviews);
• A random or uniform review of BWC data with regard to equipment functionality, policy compliance; or
• Any other purpose authorized under this policy and consistent with State and Federal law.

Data access in Critical Incidents

In any Critical Incident, video and audio data shall not be accessed unless approved by the assigned investigating agency.

No duplication of data by recording devices

Employees are prohibited from using recording devices to duplicate BWC video or audio in any form, including cell phones or video cameras.

Notice to Data Subjects

1. If a person brings an action in district court under MN Statute section 13.825 Subd. 2, the MPD shall give notice to any data subjects in the video in question who did not receive notice from the person bringing the action, if known.
2. If the MPD has retained a recording in accordance with MN Statute section 13.825 Subd. 3 paragraph (c), the MPD shall notify the requester after the time period is up that the recording will then be destroyed unless a new request is made under that paragraph.
3. If the MPD discovers or is notified of a breach in the security of the data, data subjects, if known, will be notified in accordance with MN Statute section 13.055, Subd. 2.

Uploading Non-BWC Data

For all video, audio or photographic data uploaded to the storage system that was not video captured by an MPD-issued BWC, employees shall follow the requirements in the Uploading and Classification section where applicable, as well as the following requirements:

1. The category of “Non-BWC Data” shall be applied, along with all other applicable categories.

2. Whenever a case number is generated from CAD, employees shall provide the associated case number in the “ID” field for all related data.

1. When entering the number, it shall be in the standard format of YY-xxxxxx (ex. 16-123456). The dash must be included and no other characters will be used.

The purpose of this policy is to provide direction for the use of Milestone and the Fusus Real Time Crime Center technology platform.

Milestone

Milestone is the Departments’ primary application for viewing and retrieving video from the public safety cameras owned and operated by MPD.

Fusus Real Time Crime Center

The Fusus Real Time Crime Center technology platform consists of fususONE, fususOPS, fususALERT, fususREGISTRY, fususTIPS, fususVAULT, and the fususCORE hardware appliance.

Use of Video

1. All video saved from Milestone shall only be used for evidentiary, court, internal or administrative investigation, or training (with the approval of the training unit commander) purposes. Video can also be saved for other agencies through the MPD’s Strategic Information Center (SIC).
2. The Minneapolis Police Department is committed to the protection of individual rights as governed by the United States Constitution, and Federal, State and local law. Collection of public and private video streams are strictly intended for legitimate law enforcement purpose and never for the arbitrary collection of video surveillance.
3. In accordance with Minneapolis Ordinance 41.100, facial recognition technology shall not be used with this platform or video from this platform unless an exception was approved in accordance with the Ordinance.

Viewing, Release and Collection of Video and Other Data

1. Video and other data shall only be released in accordance with the MN Government Data Practices Act and Minneapolis and MPD policy.
2. No person shall be permitted to view video, except in accordance with the MN Data Practices Act and any other applicable laws.
3. Video shall only be viewed or collected for a legitimate law enforcement purpose.

1. Video shall not be viewed or collected for the purpose of harassing or intimidating members of the public, employees, visitors, or arrestees.
2. Video shall not be viewed or collected for personal use.

Public Video Collection

1. Public video streams shall be collected in those public areas which are deemed of value for the prevention and detection of criminal activity within the city.
2. Decisions concerning which areas are selected for video surveillance shall be made by command staff members holding the rank of Lieutenant or above and shall be continually evaluated for need and effectiveness.
3. A list of those public areas in which video streams are collected shall be made available to the public.

Data Retention

All data (including video) received by the MPD shall be retained and disposed of in accordance with the MN Government Data Practices Act and the City of Minneapolis Records Retention Schedules.

Milestone and fususONE Camera Control

1. The Incident Commander of an event will designate personnel to monitor cameras to give situational awareness to make informed, timely decisions.

1. Remarks should be added to CAD to identify the camera operator by call sign.
2. If the event is preplanned this should be noted in an EAP.

2. If an event or situation arises in a precinct, that precinct should be responsible for tracking and camera management for that event until it concludes or until it leaves the precinct.

1. When an event leaves the precinct, the event responsibility shall be transferred to an Incident Commander in the new precinct.  The transfer shall be announced on the radio.
2. The precinct where the event originated shall be responsible for generating the required records and reports.

3. In situations where the event causes a response greater than the precinct resources alone or situations affect multiple precincts, control may be temporarily restricted and taken over by MPD Mobile Command personnel. If Mobile Command is not controlling a camera or does not have it restricted, the precinct may resume control of cameras.
4. Situations or events may dictate that personnel from the MPD’s Strategic Information Center (SIC) unit need camera control for intelligence gathering or viewing for operational planning. In that case MPD Strategic Information Center (SIC) personnel may temporarily take control of a camera from a precinct to gather intel and will then release it back to the precinct when finished.
5. The Strategic Information Center (SIC) unit and the Multi Agency Command Center (MACC) or Emergency Operation Center (EOC) shall communicate together to avoid conflicts and to best fit operational needs, as they may be working on the same intel incident. Potential conflicts could include operational, intelligence gathering, and evidence gathering needs. If a conflict arises regarding who has the operational need, the MACC/EOC Operational Section Chief and the Event Incident Commander shall determine who has operator priority.

System Access

1. A list of all users who have access to the platform shall be maintained by the system administrator.
2. Employees shall have their own username or a group username and password to login to the platform, and they shall only use that login information for access.

1. Unmanned aerial systems are a tool that can help the MPD de-escalate situations, aid in search and rescue operations, evaluate and manage the resources needed, and prepare the proper tactical response.
2. The purpose of this policy is to establish guidelines for the use of an unmanned aerial system (UAS) and for the storage, retrieval, and dissemination of images and data captured by the UAS.
3. MN Statute section 626.19 Subd. 10 requires that any local law enforcement agency that uses or proposes to use an unmanned aerial vehicle (UAV) must establish and enforce a written policy governing its use, including requests for use from government entities.

Protect Life and Property

1. Unmanned aerial systems may be used to enhance the MPD’s mission of protecting lives and property, when other means and resources are not available or are less effective.

1. Any use of a UAS will be in strict accordance with constitutional and privacy rights.

Privacy

The use of the UAS potentially involves privacy considerations.

1. Absent a warrant or exigent circumstances, Remote Pilots in Command and Visual Observers shall adhere to FAA altitude regulations and shall not intentionally record or transmit images of any location where a person would have a reasonable expectation of privacy (e.g., residence, yard, enclosure).

2. Remote Pilots in Command and Visual Observers shall take reasonable precautions to avoid inadvertently recording or transmitting images of areas where there is a reasonable expectation of privacy. Reasonable precautions can include, for example, deactivating or turning imaging devices away from such areas or persons during UAS operations.

Requirements for Deployment

FAA requirements

In accordance with MN Statute section 626.19 Subd. 4, the MPD must comply with all Federal Aviation Administration requirements and guidelines, including, but not limited to:

Daytime operation

UAS operations should primarily be conducted during daylight hours and only operated in the dark when the situation calls for immediate action.

Populated areas

A UAS should not be flown over populated areas without FAA approval.

Pilot and observer

Deployment can only be conducted if there is an authorized Remote Pilot in Command and a trained Visual Observer conducting the mission.

Policy and law

A UAS shall only be deployed in accordance with MPD policy and MN Statute section 626.19.

Authorization required

1. A UAS shall only be deployed when authorized by the Commander of the Special Operations Division, or the rank of Deputy Chief or above, except for the following types of use:

• During or in the aftermath of an emergency situation that involves the risk of death or bodily harm to a person ([III-D-3-a]).
• To document a crime scene when requested by the Forensics Division (as part of [III-D-3-f]).
• To collect information for crash reconstruction purposes after a serious or deadly collision occurring on a public road ([III-D-3-g]).

2. The authorization requirement also applies to the use of a UAS for a search warrant when the UAS is being used as an instrument used to conduct the search.

Limited Use

Search warrant

In accordance with MN Statute section 626.19 Subd. 2, the MPD must not use a UAS without a search warrant issued under this chapter, except as provided in Authorized Use:

Random surveillance

The UAS video surveillance equipment shall not be used to conduct random surveillance activities.

Authorized use

In accordance with MN Statute section 626.19 Subd. 3, the MPD may use a UAS:

1. During or in the aftermath of an emergency situation that involves the risk of death or bodily harm to a person;

2. Over a public event where there is a heightened risk to the safety of participants or bystanders;
3. To counter the risk of a terrorist attack by a specific individual or organization if the MPD determines that credible intelligence indicates a risk;
4. To prevent the loss of life and property in natural or man-made disasters and to facilitate operational planning, rescue, and recovery operations in the aftermath of these disasters;
5. To conduct a threat assessment in anticipation of a specific event;
6. To collect information from a public area if there is reasonable suspicion of criminal activity;
7. To collect information for crash reconstruction purposes after a serious or deadly collision occurring on a public road;
8. Over a public area for employee training or public relations purposes; and
9. For purposes unrelated to law enforcement at the request of a government entity, provided that the government entity makes the request in writing to the MPD and specifies the reason for the request and proposed period of use.

Requests by other law enforcement agencies

Any use of the MPD UAS at the request of another law enforcement agency shall only occur in accordance with MPD policy and applicable laws, and the operation of the UAS shall be done by MPD employees.

Prohibited Use

In accordance with MN Statute section 626.19 Subd. 4:

Facial recognition

The MPD shall not deploy a UAV with facial recognition or other biometric-matching technology, or search the data from a UAS with facial recognition or other biometric-matching technology, unless expressly authorized by a warrant and only if an exception was approved in accordance with Minneapolis 41.120.

Weapons

The MPD shall not equip a UAS with weapons.

Data on protests and demonstrations

The MPD shall not use a UAS to collect data on public protests or demonstrations, unless expressly authorized by a warrant or an exception applies the Limited Use section of this policy.

Additionally:

One UAV per pilot

Remote Pilots in Command shall only operate one UAV at a time per pilot. This does not prohibit the operation of more than one UAV at the same time by separate pilots.

Targeting based on characteristics

The UAS video surveillance equipment shall not be used to target a person based solely on actual or perceived characteristics such as an individual’s race, color, creed, religion, ethnic/national origin, gender, gender identity, age, disability (including pregnancy), or characteristics identified as sexual orientation, affectional preference, marital status, familial status, status with regard to public assistance and veterans status.

Harassment

The UAS video surveillance equipment shall not be used to harass, intimidate, or discriminate against any individual or group.

Personal business

The UAS video surveillance equipment shall not be used to conduct personal business of any type.

Use of Vision Enhancement Technology

1. Use of vision enhancement technology not generally available to the public is permissible in viewing areas only:

• where there is no protectable privacy interest, or
• when in compliance with a search warrant or court order.

2. In all other instances, legal counsel should be consulted prior to using vision enhancement technology.

Training Required

Only authorized Remote Pilots in Command who have completed the required training shall be permitted to operate the UAS.

Program Coordinator

The Minneapolis Police Department will appoint a program coordinator who shall be responsible for the management of the UAS program. The program coordinator shall ensure that policies and procedures conform to current laws, regulations, and best practices.

Department UAS Program

1. Only Remote Pilots in Command authorized by the UAS program coordinator shall operate UAVs.

2. Only UAVs authorized by the UAS program coordinator shall be deployed. Under no circumstance shall unauthorized UAVs be deployed.

1. No personal UAVs shall be deployed by any employee while on-duty or for official purposes.

2. All purchases, maintenance, and updates of UAVs shall be coordinated by the UAS program coordinator.

Evidence

MN Statute section 626.19 Subd. 7 states:

Information obtained or collected by the MPD in violation of this section is not admissible as evidence in a criminal, administrative, or civil proceeding against the data subject.

Data Classification

In accordance with MN Statute 626.19 Subd. 6, data collected by a UAS are private data on individuals or nonpublic data, subject to the following:

1. If the individual requests a copy of the recording, data on other individuals who do not consent to its release must be redacted from the copy;

2. UAS data may be disclosed as necessary in an emergency situation under Subd. 3, clause (1);
3. UAV data may be disclosed to the government entity making a request for UAV use under Subd. 3, clause (9);
4. UAV data that are criminal investigative data are governed by section 13.82, Subd. 7; and
5. UAV data that are not public data under other provisions of Chapter 13 retain that classification.

Data Retention

Notwithstanding MN Statute section 138.17, the MPD shall delete data collected by a UAS as soon as possible, and in no event later than seven days after collection unless the data is part of an active criminal investigation.

Data Upload and Categorization

1. After the deployment is completed, the UAS Remote Pilot in Command shall upload all video and audio data collected by the UAS into Evidence.com prior to the end of their shift.

2. The text “DRONE-” shall be included at the beginning of the file name for all deployment uploads, regardless of evidentiary status.
3. If the following definition applies, the category of “Evidence” shall be applied to the upload.

Evidence: This category should be used for all UAS recordings that are part of an active criminal investigation.

4. The category of “UAS” shall be applied to all deployment uploads that are non-evidentiary, which will be subject to deletion after 7 days.

Body Worn Cameras (BWCs)

1. The Remote Pilot in Command shall not activate their BWC while operating a UAS, and shall deactivate their BWC prior to operating if already activated.

2. The Visual Observer shall ensure their BWC is activated during the deployment, subject to the exceptions below:
3. BWC activation is not required for UAS training or for using the UAS for public relations purposes, unless another activation requirement in P&P 4-223 applies.

Tennessen Warning

In accordance with MN Statute section 6126.19 Subd. 6:

The MN Statute on Tennessen Warnings (section 13.04, Subd. 2) does not apply to data collected by a UAS.

Documentation Required

Incident information

Report required

The following information shall be documented in a Police Report, which shall include the code DRONE, for each use of a UAS, per MN Statute section 626.19 Subd. 5, subject to the exceptions below:

1. A unique case number connected to the deployment.

2. The factual basis for the use of the UAS.
3. Whether a warrant was obtained, or an exception applied under Subd. 3 (and if so, the applicable exception).

1. If an exception applied and a warrant was not obtained, the factual basis shall include describing in detail the situations and risks that authorized the exception.

Exceptions

A Police Report is not required for UAS training or using the UAS for public relations purposes.

Flight log

1. A flight log of the aircraft shall be completed following every deployment. The log shall contain:

1. The name and badge numbers of the Remote Pilot in Command and the Visual Observer;

1. The case number for the deployment;
2. The authorized use, search warrant or authorized exception;
3. The supervisor that authorized the UAV deployment;
4. The model deployed;
5. A mission synopsis and results; and
6. Any performance issues, if applicable.

2. Digital logs of aircraft mission profiles will be retained pursuant to FAA guidelines.

Required Reporting

In accordance with MN Statute section 626.19 Subd. 12:

By January 15 of each year, the MPD shall report to the commissioner of public safety the following information for the preceding calendar year:

1. The number of times a UAV was deployed without a search warrant issued under this chapter, identifying the date of deployment and the authorized use of the UAV under Subd. 3.

2. The total cost of the MPD’s UAV program.

Program Coordinator Responsibilities

The UAS Program Coordinator (UAS PC) reports to the Special Operations and Intelligence Division Commander. The UAS PC is responsible for the day-to-day operations and will have the following additional responsibilities:

Certificate of Waiver or Authorization

The UAS PC shall coordinate the FAA Certificate of Waiver or Authorization (COA) application process and ensure that the COA is current.

Training

The UAS PC shall ensure that all authorized Remote Pilots in Command and required Visual Observers have completed all required FAA and MPD-approved training in the operation, applicable laws, policies, and procedures regarding use of the UAS.

Protocols

Requests for deployment

1. The UAS PC shall develop a uniform protocol for submission and evaluation of requests to deploy a UAS, including urgent requests made during ongoing or emerging incidents.

2. The UAS PC shall develop protocols for reviewing and approving requests for use of the MPD UAS by government entities, as required by MN Statute section 626.19 Subd. 10.

Use in criminal investigations

The UAS PC shall develop protocol for conducting criminal investigations involving a UAS, including documentation of time spent monitoring a subject.

Operations

The UAS PC shall develop an operational protocol governing the deployment and operation of a UAS, including but not limited to safety oversight, use of visual observers, establishment of lost link procedures, and secure communication with air traffic control facilities.

Documenting missions

The UAS PC shall develop a protocol for fully documenting all missions.

Inspection and maintenance

The UAS PC shall develop a UAS inspection, maintenance, and record-keeping protocol to ensure continuing airworthiness of a UAS, up to and including its overhaul or life limits.

Data access and storage

1. The UAS PC shall develop protocols to ensure that all data intended to be used as evidence are accessed, maintained, stored, and retrieved in a manner that ensures its integrity as evidence, including strict adherence to chain of custody requirements.

2. Electronic trails, including encryption, authenticity certificates, and date and time stamping, shall be used as appropriate to preserve individual rights and to ensure the authenticity and maintenance of a secure evidentiary chain of custody.

Data retention

Developing protocols that ensure retention and purge periods are maintained in accordance with established records retention schedules.

Facilitate law enforcement access

The UAS PC shall facilitate law enforcement access to images and data captured by the UAS.

Ensure protocols are followed and report to Chief

1. The UAS PC shall ensure that established protocols are followed by monitoring and providing quarterly reports on the program to the Chief.

1. The Chief may direct or request additional reports or presentations to be prepared by the UAS PC.

Submit required reports

The UAS PC shall prepare and submit the required annual report to the Commissioner of Public Safety, per MN Statute section 626.19 Subd. 12.

Post policy

The UAS PC shall ensure the MPD policy regarding the use of UAV is posted on the MPD’s website, as applicable, per MN Statute section 626.19 Subd. 10.

Review program

Compliance

The UAS PC shall review the program and UAS use for compliance with MN Statute section 626.19.

Recommend enhancements

The UAS PC shall recommend program enhancements, particularly regarding safety and information security.

• 40mm Round: A direct fire impact projectile round used in situations where maximum deliverable kinetic energy is desired for the incapacitation of a person.
• Activate MVR: Any process which causes the MVR system to record video or audio data. Activation may occur automatically due to a trigger event or be done manually.
• ALPR Supervisor: A superior officer assigned to oversee and administer, or to assist in overseeing and administering, the use of the ALPR devices and/or stored ALPR data. There may be more than one designated supervisor.
• Authorized BWC Personnel: Personnel designated by the Chief or the Chief's designee, to manage data recorded by the BWC. Such management includes duplication, redaction and lawful destruction of data as required by law and the City of Minneapolis Records Retention Policy. Designated personnel may include, but is not limited to: Records Management Specialists, Crime Lab Personnel and Business Technology Personnel.
• Authorized User: A sworn or civilian employee who has been authorized to operate an ALPR device or to access ALPR stored data and who has successfully completed training on ALPR use and policy.
• Automated License Plate Reader: A system consisting of a camera or cameras and related equipment that automatically and without human control locates and focuses on, and photographs license plates and vehicles that come into the range of the device, that automatically converts digital photographic images of scanned license plates into electronic data, that is capable of comparing scanned license plate text data with data files for vehicles on a BOLO (be on the lookout) or hot list programmed into the device's electronic memory, and that notifies police when a scanned license plate matches the license plate on a programmed BOLO list. The term includes both devices that are placed at a stationary location and mobile devices affixed to a vehicle and capable of operation while the vehicle in in motion.
• Bodily Harm: Physical pain or injury, illness, or any impairment of physical condition.
• Body Worn Camera: Portable audio-video recording equipment designed to be worn on a person.
• BWC Activation: Any process that causes the BWC system to record audio or video data. Activation will be done manually. Activation can only occur when the BWC is already powered on.
• BWC Deactivation: Any process that causes the BWC system to stop recording. Deactivation can be done manually or can occur accidentally.
• BWC Designated Upload Site: Location where employees complete the task of uploading BWC recordings to a storage server through a PC using the SYNC program or through a docking station.
• BWC Pre-Event Recording: Video stored by the BWC system prior to manual activation. This is a configurable feature for the digital BWC system and is preset to record video only (no audio) prior to manual activation. The pre-event recording is included as part of the incident and is viewable during playback.
• BWC Quality Assurance Unit: The BWC Quality Assurance Unit within BTU is responsible for oversight of the BWC program and ensuring policy adherence.
• BWC Uploading: The act of transferring recorded data from the BWC to the storage server.
• Categorize an Event: Term used to classify an event that has been recorded and for which a predetermined retention period has been set.
• Chain of Custody: Documentation of every person that has had custody of an item from the time it was collected until its final disposition.
• Classify: To categorize an event that has been recorded and for which a predetermined retention period has been set.
• Confidential Informant:

  A person who cooperates with a law enforcement agency confidentially in order to protect the person or the MPD’s intelligence gathering or investigative efforts, and:

  1. Seeks to:
     1. Avoid arrest or prosecution for a crime; or
     2. Mitigate punishment for a crime in which a sentence will be or has been imposed; or
     3. Receive a monetary or other benefit;
  2. Is able, by reason of the person’s familiarity or close association with suspected criminals, to:
     1. Make a controlled buy or controlled sale of contraband, controlled substance, or other items that are material to a criminal investigation;
     2. Supply regular or constant information about suspected or actual criminal activities to a law enforcement agency;
     3. Otherwise provide information important to ongoing criminal intelligence gathering or criminal investigative efforts.
• Critical Incident:

  An incident involving any of the following situations occurring in the line of duty:

  • The use of Deadly Force by or against a Minneapolis Police Officer
  • Death or Great Bodily Harm to an officer
  • Death or Great Bodily Harm to a person who is in the custody or control of an officer
  • Any action by an officer that causes or is intended to cause Death or Great Bodily Harm
• Degaussing: Electronic cleansing by overwriting, erasing, and/or destruction of electronic storage media of analog and digital recording media that returns the media to it original state so it is ready for the imprinting of new images.
• Demonstration: An assembly of people organized primarily to engage in First Amendment activity. They include, but are not limited to, marches, protests, and other assemblies intended to attract attention.
• Designated Upload Site: Location where MVR recordings stored on media cards are uploaded to server through wireless transmission.
• Disruptive Activity: Any time that cell phone operations would be considered disruptive, such as in training sessions, court or public places where cell phone use would reasonably be deemed annoying and intrusive.
• Domestic Abuse: Physical harm, bodily injury, assault, or the infliction of fear of imminent physical harm, bodily injury or assault, terroristic threats, criminal sexual conduct, or interference with an emergency call, when committed between family or household members.
• Exigent Circumstances: the need to prevent imminent harm or to provide emergency aid, to prevent imminent destruction or removal or evidence excluding narcotics, when in hot pursuit of an individual who committed or is suspected of committing a felony, or to prevent the imminent escape of a suspect
• Feasible: Objectively reasonably capable of being safely done or carried out.
• Filler: A live person, or a photograph of a person, included in an identification procedure who is not considered a suspect.
• Firearms/Ammunition/Firearm Accessories: A device that projects either single or multiple projectiles at high velocity. Ammunition is a term meaning the assembly of a projectile and its propellant. Accessories include but are not limited to holsters, gun cases, firearm optics, suppression devices, cleaning supplies, etc.
• Gender Identity: A person's actual or perceived self-image or identity as expressed through dress, appearance, behavior, speech or similar characteristics, whether or not traditionally associated with the person's physical anatomy, chromosomal sex, or sex at birth.
• Great Bodily Harm: Bodily injury which creates a high probability of death, or which causes serious permanent disfigurement, or which causes a permanent or protracted loss or impairment of the function of any bodily member or organ, or other serious bodily harm (MN Statute section 609.02 Subd. 8).
• Historical ALPR Query: The process of accessing and reviewing stored ALPR data to gather information about known vehicles, to identify unknown vehicles and/or to identify vehicles in the area of a crime scene.
• Hotlist: A compilation of license plates or partial license plates of vehicles for which a BOLO situation exists that is programmed into an ALPR so that the device will alert if it captures the image of a license plate that matches a license plate included on the list.
• Incident Commander:

  The Incident Commander (IC) is the first officer or supervisor to arrive on the scene of a call for service where multiple units, scenes, or assisting agencies are dispatched. The Incident Commander has overall command of the incident, until properly relieved by a supervisor of higher rank if necessary, and will be based at the incident command post. The priorities of the Incident Commander include:

  1. Assess incident priorities.
  2. Determine strategic goals and tactical objectives, not related to the operations of SWAT or ESU personnel.
  3. Identify a staging area, if needed.
  4. Develop and implement incident action plan.
  5. Develop appropriate incident management structure.
  6. Assess resource needs.
  7. Coordinate overall on-scene emergency activities.
  8. Authorize information to be released to the media.
• Informant: People who give information to another, including Confidential Informant, and Confidential Reliable Informant
• Investigation: A structured process of gathering, examining, and evaluating facts and evidence to determine what occurred, assess compliance with laws and policies, and support appropriate actions or decisions.
• Investigators: All persons from the MPD Homicide unit and Internal Affairs unit who are conducting an investigation of the Critical Incident, unless other Criminal Investigating and Administrative Investigating Entities have been designated by the Chief of Police or their designee.
• Lawful Order: Any written or oral directive issued by a supervisor or a proper authority in the course of work that is in compliance with MPD rules and regulations.
• Lead Investigator: The Investigator in charge of the criminal investigation or their designee at the scene. The Lead Investigator shall be from the MPD Homicide unit, unless otherwise designated.
• Limited English Proficiency: Designates individuals whose primary language is not English and who have a limited ability to read, write, speak, or understand English. LEP individuals may be competent in certain types of communication (e.g. speaking or understanding), but still be LEP for other purposes (e.g. reading or writing). Similarly, LEP designations are context specific. An individual may possess sufficient English language skills to function in one setting, but may find these skills are insufficient in other situations.
• Manual Activation: Activation of MVR equipment that is not caused by a trigger event. Officers may activate the MVR equipment at their own initiation or at the direction of a supervisor via the wireless microphone, in-car LCD monitor, or digital video recorder (DVR) box in the vehicle's trunk.
• MECC: Minneapolis Emergency Communications Center is the city's 911 center that answers emergency and non-emergency calls and coordinates the appropriate response by public safety services.
• MVR Designated Upload Site: Location where MVR recordings stored on media cards are uploaded to server through wireless transmission.
• MVR Equipment Check: An audio/video test to ensure that the MVR equipment is in working order. This check shall include a test of the video and microphone recording components and a date and time check of the in-car LCD monitor.
• MVR Operational Guide: Training manual/guide which outlines the protocol for operating the MVR system/equipment.
• MVR Pre-Event Recording: Video stored by the MVR system prior to activation. This is a configurable feature for the digital MVR system and is preset to record video prior to activation. The pre-event recording is included as part of the incident and is viewable during playback.
• Non-Evidence: Any material object, tangible or intangible, to which an owner has a legal right. Items of no known evidentiary value (as described above) which come into the custody of a police department employee that is not a part of a criminal investigation, and whose rightful owner may or may not, be known.
• Photo Array: A means of presenting photographs to an eyewitness for the purpose of identifying or eliminating suspects.
• Police Report: A report or statement in a report that sets forth the officer's account of an incident and is entered into the MPD's Records Management System.
• Power On: Powering on the BWC requires setting the "On/Off" switch to "On," enabling power to the BWC. This must occur prior to and is distinct from Activation.
• Pre-Event Recording: Video stored by the MVR system prior to activation. This is a configurable feature for the digital MVR system and is preset to record video prior to activation. The pre-event recording is included as part of the incident and is viewable during playback.
• Public Safety Statement: A mandatory statement from the Involved Officers which provides information necessary to ensure public safety. This may include questions about the direction in which the Involved Officer fired their firearm, injured people, location of dangerous weapons or information on any suspects still at large and any other information necessary to facilitate the commencement of the investigation.
• Record Mode: Any time MVR equipment is recording audio/video as indicated on the LCD monitor, wireless microphone and/or DVR.
• Remote Pilot in Command: A person who holds a remote pilot certificate with a UAS rating and has the final authority and responsibility for the operation and safety of a UAS operation conducted under FAA's Small UAS Rule (Part 107).
• Reports and Statements: Police Report: A report or statement in a report that sets forth the officer's account of an incident and is entered into the MPD's Records Management System. Public Safety Statement: A mandatory statement from the Involved Officers which provides information necessary to ensure public safety. This may include questions about the direction in which the Involved Officer fired their firearm, injured people, location of dangerous weapons or information on any suspects still at large and any other information necessary to facilitate the commencement of the investigation. Voluntary Statement: A statement given by Involved or Witness Officers to Investigations Bureau Investigators which is voluntary and outlines details associated with the Critical Incident. Voluntary statements from officers are essential for bringing criminal charges against suspects, defending officers, and maintaining community trust by providing the Chief of Police with sufficient information to appropriately address community concerns. Voluntary statements will be taken in question and answer (Q&A) format.
• School Resource Officer: SRO's are assigned to Minneapolis Public Schools and work together with school administrators, students, the Juvenile Unit, and the community to ensure school safety and security.
• Search Warrant: A document issued by the Court authorizing the police to enter and search a person, premises, location or vehicle for purposes of evidence recovery.
• Sexual Assault: Sexual contact or penetration with another person in a criminal manner as identified in MN Statute sections 609.342 to 609.3451.
• Sexual Orientation: Having or being perceived as having an emotional, physical, or sexual attachment to another person without regard to the sex of that person or having or being perceived as having an orientation for such attachment.
• Significant Incident:

  Includes, but is not limited to, any of the following situations occurring in the line of duty:

  • Critical incident
  • Domestic abuse incident interview
  • Felony crime
  • Pursuit
  • Squad accident
  • Any incident in which the officer or sworn supervisor believes the recording to be of evidentiary and/or administrative value
  • The identity of someone in the video needs to be protected
  • Man-made or natural disaster or act of terrorism
  • Any event that an officer or supervisor believes should be brought to the immediate attention of police command staff
  • Any time that a citizen makes allegations of police misconduct or discrimination during the incident
• Source Individual: Source Individual (SI) is an individual, living or dead, whose blood, tissue, or potentially infectious body fluids may be a source of bloodborne pathogen exposure to another person. Examples include, but are not limited to, a victim of an accident, injury or illness, or a deceased person.
• Stored Data: All information captured by an ALPR and stored in the device's memory or in a separate storage device or system. This includes the recorded image of a license plate which has been read, optical character recognition data, a contextual photo of the vehicle, GPS data, ALPR device data, timestamp and hotlist information. This term refers to both alert data and non-alert data.
• Subpoena: An official court order for an individual to appear in court. The Subpoena remains in effect until the case is over or the Issuing Authority excuses the individual under Subpoena.
• Substantial Bodily Harm: Bodily injury which involves a temporary but substantial disfigurement, or which causes a temporary but substantial loss or impairment of the function of any bodily member or organ, or which causes a fracture of any bodily member (MN Statute section 609.02 Subd. 7a).
• Trigger Event: An event that causes the MVR system to begin a video and audio recording. Trigger events include the activation of emergency lights or vehicle collision sensor.
• Unmanned Aerial System: An unmanned aircraft of any type that is capable of sustaining directed flight, whether preprogrammed or remotely controlled without the possibility of direct human intervention from within or on the aircraft (UAV), and all of the supporting or attached systems designed for gathering information through imaging, recording, or any other means.
• Use of Force:

  An intentional contact, directly or indirectly (such as through a weapon or force device), with someone’s body, that causes pain or injury or restricts, controls or directs someone’s movement. Intentionally placing someone in fear of such contact or threatening such contact can also constitute force. This includes, but is not limited to:

  • The use of any weapon, substance, vehicle, equipment, tool, device or animal that inflicts pain or produces injury.
  • Any physical strike to any part of the body.
  • Any physical contact or threat of contact by the member or a weapon that causes or threatens to cause pain or injury.
  • Any physical contact or threat of physical contact by the member that results in physical restriction or manipulation of movement.
  • Unholstering or displaying a weapon when engaged with a subject or subjects, or pointing a weapon at a person.
• Visual Observer: A person acting as a flight crew member who assists the small UAS RPIC and the person manipulating the controls to see and avoid other air traffic or objects aloft or on the ground.
• Witness Officer: An officer who witnesses a Critical Incident, but did not engage in any conduct constituting a Critical Incident.