Use of Force Reports Sample Clauses

Use of Force Reports. ‌ 21 126. Within 90 days of the Effective Date, the City and the United States will confer 22 and agree on a process to determine what, if any, new policies or procedures regarding Xxxxxxx 23 are necessary based on the DOJ’s technical assistance letter that have not already been addressed 1 in the Settlement Agreement. This process may include convening a appropriate police, legal, 2 and other experts to examine best practices in providing Xxxxxxx warnings. At the conclusion of 3 that process, the Parties will meet and confer regarding what, if any, additional policies and 4 procedures should be implemented.
AutoNDA by SimpleDocs
Use of Force Reports. Witness Identification
Use of Force Reports. Witness Identification Settlement Agreement Section VI. C.; page 25, lines 7-16 (lead-in page 23, lines 23-24) Assigned Unit: BOS
Use of Force Reports. Witness Identification Settlement Agreement Language “Within 154 days from the effective date of this Agreement, OPD shall establish policy and procedures for the following:
Use of Force Reports. Contractor shall report all Use of Force incidents within 24 hours of the incident to the SmartPark General Manager or designee and/or Streetcar Division Manager. All deliverables and resulting work products from this contract will become the property of the City of Portland. A complete list of deliverables and schedule is found in Attachment 2.
Use of Force Reports. Each Officer who applies physical force, however slight, to compel an individual to comply or uses an MEB, discharges their OC, causes a canine to bite or draws his/her firearm and points it at any person, group, or vehicle, or employ any other application of force that results in or alleged to have resulted in, an injury or death, other than the discharge of a firearm, will complete a Blue Team Use of Force Report. Each field is to be filled out as completely as pos- sible. The summary of incident section must contain all pertinent information re- xxxxxxx the Use of Force. {1.3.6 b, c, d, 1.3.7} This report will be electronically submitted to the Officer's immediate Supervisor for review and approval before completion of the tour of duty during which the incident ccurred or within a reasonable amount of time with a Supervisor’s approval. The Supervisor will electronically forward the report through the chain of command to the Office of Professional Standards as soon as possible, but no later than the Officer's next tour of duty. If the Blue Team entry is not complete, the Supervisor will return it to the Officer. The Office of Professional Standards will forward a copy of the report to the Patrol Operations Division Commander. {1.3.7}

Related to Use of Force Reports

  • Submission of Formal Disputes a. A Formal Dispute must be filed in writing with the Director of Procurement Services by mail or email, using the following contact information: Director, Procurement Services A Division of the Office of General Services 00xx Xxxxx, Xxxxxxx Xxxxx Xxxxxx Xxxxx Xxxxx Xxxxxx, XX 00000 Email: xxxxxxxx.xxxxxxxx@xxx.xx.xxx Subject line: Formal Dispute – Attn: Director of Procurement Service

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Bid Attributes Disadvantaged/Minority/Women Business & Federal HUBZone Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Historically Underutilized Business (HUB) Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No National Coverage Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • Effect of Force Majeure If either Party is rendered wholly or partially unable to perform its obligations under this Agreement because of a Force Majeure Act, that Party shall be excused from whatever performance is affected by the Force Majeure Act to the extent so affected, provided that:

  • Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Signature Form.pdf

  • RELEASE OF GENERAL INFORMATION TO THE PUBLIC AND MEDIA NASA or Partner may, consistent with Federal law and this Agreement, release general information regarding its own participation in this Agreement as desired. Pursuant to Section 841(d) of the NASA Transition Authorization Act of 2017, Public Law 115-10 (the "NTAA"), NASA is obligated to publicly disclose copies of all agreements conducted pursuant to NASA's 51 U.S.C. §20113(e) authority in a searchable format on the NASA website within 60 days after the agreement is signed by the Parties. The Parties acknowledge that a copy of this Agreement will be disclosed, without redactions, in accordance with the NTAA.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Definition of Force Majeure For the purposes of this section, an event of force majeure shall mean any cause beyond the control of the affected Interconnection Party or Construction Party, including but not restricted to, acts of God, flood, drought, earthquake, storm, fire, lightning, epidemic, war, riot, civil disturbance or disobedience, labor dispute, labor or material shortage, sabotage, acts of public enemy, explosions, orders, regulations or restrictions imposed by governmental, military, or lawfully established civilian authorities, which, in any of the foregoing cases, by exercise of due diligence such party could not reasonably have been expected to avoid, and which, by the exercise of due diligence, it has been unable to overcome. Force majeure does not include (i) a failure of performance that is due to an affected party’s own negligence or intentional wrongdoing; (ii) any removable or remediable causes (other than settlement of a strike or labor dispute) which an affected party fails to remove or remedy within a reasonable time; or (iii) economic hardship of an affected party.

  • CONFIDENTIAL, PROPRIETARY, AND TRADE SECRET INFORMATION AND MATERIALS a. Buyer and Seller shall each keep confidential and protect from unauthorized use and disclosure all (i) confidential, proprietary and/or trade secret information of a Party or third party disclosed by a Party; (ii) software provided under this Contract in source code form or identified as subject to this Article; and (iii) tooling identified as subject to this Article: in each case that is obtained, directly or indirectly, from the other in connection with this Contract or Buyer’s contract with its customer, if any, (collectively referred to as "Proprietary Information and Materials"). Proprietary Information and Materials excludes information that is, as evidenced by competent records provided by the receiving Party, known to the receiving party or lawfully in the public domain, in the same form as disclosed hereunder, disclosed to the receiving Party without restriction by a third party having the right to disclose it, or developed by the receiving Party independently without use of or reference to the disclosing Party’s Proprietary Information and Materials.

  • Waiver of FOIA Request The defendant waives all of his rights, whether asserted directly or by a representative, to request or receive from any department or agency of the United States any records pertaining to the investigation or prosecution of this case including, without limitation, any records that may be sought under the Freedom of Information Act, 5 U.S.C. § 552, or the Privacy Act of 1974, 5 U.S.C. § 552a.

  • Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!