Incident Response Tow Requests Sample Clauses

Incident Response Tow Requests. 5.1.1 Incident Response Tow Requests will be received by telephone from TMOC/ Incident Response dispatch. 5.1.2 ODOT Tow Requests may be received from Incident Response or State Highway Maintenance. 5.1.3 Dispatcher will provide tow dispatching services for Incident Response Tow Requests only within Multnomah County. 5.1.4 Incident Response Tow Requests shall be treated as Private Non-Preference tows. 5.1.5 All information about an Incident Response Tow Request, including tow driver number and tow truck number, will be recorded on a tow slip and entered into the computerized data base. 5.1.6 Dispatcher will check the Tow Request location and determine the District and next Tow Contractor in rotation. 5.1.7 Dispatcher will inform TMOC/ Incident Response of the name of the dispatched Tow Contractor by telephone before disconnecting. 5.1.8 Dispatcher will record the Incident Response truck number or the Maintenance truck number to identify the person making the Tow Request. 5.1.9 Dispatcher will request information about the best access to tow location from TMOC/ Incident Response. Dispatcher will provide such information to the dispatched Tow Contractor. 5.1.10 Dispatcher will report to PPB Records all information supplied by the Tow Contractor when the tow is complete, including vehicle description and condition, and location where the vehicle was dropped. A City of Portland Tow Report Number will be assigned for each completed Incident Response Tow Request. 5.1.11 Dispatcher will provide daily and monthly tow log reports of all Incident Response and State Highway Tow Requests to TMOC/ Incident Response.
Sample 1
AutoNDA by SimpleDocs

Related to Incident Response Tow Requests

  • Incident Response Operator shall have a written incident response plan that reflects best practices and is consistent with industry standards and federal and state law for responding to a data breach, breach of security, privacy incident or unauthorized acquisition or use of any portion of Data, including PII, and agrees to provide LEA, upon request, an executive summary of the written incident response plan.

  • Client Responsibility For clarity, the parties agree that in reviewing the documents referred to in clause (b) above, Patheon’s role will be limited to verifying the accuracy of the description of the work undertaken or to be undertaken by Patheon. Subject to the foregoing, Patheon will not assume any responsibility for the accuracy of any application for receipt of an approval by a Regulatory Authority. The Client is solely responsible for the preparation and filing of the application for approval by the Regulatory Authority and any relevant costs will be borne by the Client.

  • Tenant Responsibility Good housekeeping is expected of everyone. Tenant agrees to keep quarters clean and in a sanitary condition. The Tenants agree not to permit any deterioration or destruction to occur while they are occupying the property.

  • Client Responsibilities You are responsible for (a) assessing each participants’ suitability for the Training, (b) enrollment in the appropriate course(s) and (c) your participants’ attendance at scheduled courses.

  • Cost Responsibility Interconnection Customer shall be responsible for and shall pay upon demand all Costs associated with the interconnection of the Customer Facility as specified in the Tariff. These Costs may include, but are not limited to, an Attachment Facilities charge, a Local Upgrades charge, a Network Upgrades charge and other charges. A description of the facilities required and an estimate of the Costs of these facilities are included in Sections 3.0 and 4.0 of the Specifications to this ISA.

  • Payment Responsibility The payment obligations of each Participating Manufacturer pursuant to this Agreement shall be the several responsibility only of that Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any Affiliate of such Participating Manufacturer. The payment obligations of a Participating Manufacturer shall not be the obligation or responsibility of any other Participating Manufacturer. Provided, however, that no provision of this Agreement shall waive or excuse liability under any state or federal fraudulent conveyance or fraudulent transfer law. Any Participating Manufacturer whose Market Share (or Relative Market Share) in any given year equals zero shall have no payment obligations under this Agreement in the succeeding year.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Joint Responsibility If the Seller determines that the Interface Problem is attributable partially to the design of a Warranted Part and partially to the design of any Supplier Part, the Seller will, if so requested by the Buyer, seek a solution to the Interface Problem through cooperative efforts of the Seller and any Supplier involved. The Seller will promptly advise the Buyer of such corrective action as may be proposed by the Seller and any such Supplier. Such proposal will be consistent with any then existing obligations of the Seller hereunder and of any such Supplier towards the Buyer. Such corrective action, unless reasonably rejected by the Buyer, will constitute full satisfaction of any claim the Buyer may have against either the Seller or any such Supplier with respect to such Interface Problem.

  • Management Responsibility No Limited Partner, as such, shall take part in the management of the business or transact any business for the Partnership.

  • Customer’s Responsibility The policies in this document apply to the use of Data by Customers, Redistributors and their End Customers. Customers are responsible for compliance with this policy by all members of the Customer’s Group and by all persons to whom they distribute Data where authorised to do so. Turquoise recommends that Customers make this Schedule available to all Subscribers to their services having access to Data which is subject to Charges, reporting requirements or usage restrictions.

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