Customer Action Request System Sample Clauses

Customer Action Request System. The Customer Action Request System (CARS) is a computerised program that tracks complaints and requests from our customers. This program measures our responsiveness to our customers and is an important performance indicator for Council. The parties agree that Council's performance in responding to customer requests will be monitored and the results will be reported to Council on a regular basis. Where opportunities to improve our performance are identified, the parties agree to work collaboratively to achieve such improvement.
AutoNDA by SimpleDocs

Related to Customer Action Request System

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Information Requests The parties hereto shall provide any information reasonably requested by the Servicer, the Issuer, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

  • Information Request The Owner Trustee shall provide any information regarding the Issuer in its possession reasonably requested by the Servicer, the Administrator, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • Installation requirements We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • Documentation Requirements ODM shall pay the MCP after it receives sufficient documentation, as determined by ODM, detailing the MCP’s Ohio Medicaid-specific liability for the Annual Fee. The MCP shall provide documentation that includes the following: 1. Total premiums reported on IRS Form 8963;

  • Documentation Required The certificates and endorsements shall be received and approved by the District before Work commences. As an alternative, the Contractor may submit certified copies of any policy that includes the required endorsement language set forth herein.

  • Vacation Requests Regular employees become eligible for paid vacation leave once they have completed six (6) months of continuous employment. Vacations requests must be submitted by no later than January 31st to be scheduled for the vacation calendar year of April 1 - March 31. Vacation time may be divided into blocks of one to two weeks in duration. Scheduling of vacation shall be in accordance with seniority within a classification. Where an employee chooses to split their vacation, they shall exercise seniority rights in the choice of the first vacation period. Seniority shall prevail in the choice of the second vacation period but only after all other first vacation periods have been selected. Remaining vacation periods will be scheduled in a fair and equitable manner amongst employees within a classification. The approved vacation schedule will be posted at the worksite on or before February 28th in each year. Employees will be limited to booking a maximum of two (2) consecutive weeks of vacation during prime vacation period (June 15 - September 15; and December 15 - January 5), unless further consecutive weeks would not interfere with the vacation preferences of less senior employees. The Employer will make every effort to accommodate requests for vacation of more than two (2) consecutive weeks outside of prime vacation periods. Employees failing to exercise their right to request vacation within the vacation selection time posted by the Employer will forfeit their seniority rights with respect to choice of vacation time. In such cases, the Employer reserves the right to schedule vacation time for the employee. A maximum of two (2) weeks of vacation time may be carried forward from one year to another. Employees who wish to carry vacation forward should notify the Employer by January 31st. If the employee has not requested all of their vacation leave, the Employer reserves the right to schedule the remaining vacation days within the last four (4) months of the calendar year. The Employer may also pay out unused vacation credits at the end of February each calendar year.

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