Scope of Functions Sample Clauses

Scope of Functions. Contractor will provide Contractor personnel to perform the following specialized Functions for Local Government:
Sample 1Sample 2
AutoNDA by SimpleDocs
Scope of Functions. 5.1 It is agreed by the parties hereto that I.A.T.S. E. Local 212 will supply the qualified manpower required to set up, adjust, operate and strike all lighting and stage equipment, except as noted In Article 3.4 and 4.4, for the Grandstand Stage Show, travelling productions or "road shows", and professional musical shows, except as otherwise noted herein. 5.2 It is further agreed between the parties hereto that when productions are volunteer or religious In nature, commercial trade shows, free entertainment stages, youth programs or performances, and meetings, the parties will meet to discuss and determine the Involvement of Local 212 when the nature of the work warrants such a meeting.
Sample 1
Scope of Functions. The Reliability Coordinator shall perform the functions described in Attachment A (the “Functions”) seven days a week, twenty-four hours a day, for the duration of the Term in accordance with the terms and conditions of this Agreement. In accordance with its obligations under this Section 1.2, the Reliability Coordinator is authorized to, and shall, direct and coordinate timely and appropriate actions by LG&E/KU, including curtailing transmission service or energy schedules, re-dispatching generation, and shedding load, in each case, in order to avoid adverse effects on interregional bulk power reliability.
Sample 1
Scope of Functions. Contractor will provide Contractor personnel to perform the following specialized Functions for Local Government: 1. Zoning Administration 2. Land Use Back-Up 3. Code Enforcement
Sample 1
Scope of Functions. 2.1 tesma is modular in design, with the mandatory feature set of tesma including the following essential business applications: • Confirmations • Assets • Contracts • Invoices • Returns • Documents 2.2 Additionally, the following optional business applications can be used: • Procurement • Portal • Integration Hub • Support 2.3 The business applications can be used for a separately agreed fee, which will be invoiced together with the rentals for the Equipment, unless otherwise agreed. In all other respects, reference is made to the terms of payment agreed in the Master Lease Agreement. 2.4 The business applications listed in para.2.2 may be terminated individually or as a collective by either party with one month's notice to the end of the month in text form. In the event of termination, however, the provisions of this Agreement shall remain valid with respect to the lease schedules to which the provisions of this Agreement already applied at the time of termination until the termination of the lease schedule in question. CHG-MERIDIAN provides the customer with a manual in which the content, the processes and features of the individual business applications are described in detail.
Sample 1
Scope of Functions the Executive shall at all times ensure the protection of commercially sensitive information and in particular he must attain the objectives and comply with the relevant requirements relating to business separation as set out in applicable law, regulations and the lberdrola governance documents.
Sample 1
Scope of Functions. 1. In carrying out its functions the Committee shall at all times ensure the protection of commercially sensitive information and in particular the members of the Committee must attain the objectives and comply with the relevant requirements relating to business separation of regulated and deregulated activities. 2. The Committee will only carry out its function in relation to the lberdrola USA group and shall under no circumstances be concerned with or discuss matters relating to any other affiliated companies.
Sample 1
AutoNDA by SimpleDocs
Scope of Functions. The Reliability Coordinator shall perform the functions assigned to it and described in Attachment A and Attachment B (the “Functions”) seven days a week, twenty-four hours a day, for the duration of the Term in accordance with the terms and conditions of this Agreement. In accordance with its obligations under this Section 1.2, the Reliability Coordinator is authorized to, and shall, direct and coordinate timely and appropriate actions by LG&E/KU, including curtailing transmission service or energy schedules, redispatching generation, and shedding load, in each case, in order to avoid adverse effects on interregional bulk power reliability. 1.2.1 Relationship Between this Agreement and Attachment P to LG&E/KU's OATT. The Parties recognize that the relationship between LG&E/KU and the Reliability Coordinator and the Functions to be performed by the Reliability Coordinator must be reflected in LG&E/KU's OATT. The Reliability Coordinator relationship and the Functions assigned to the Reliability Coordinator under Attachment A and Attachment B to this Agreement shall be reflected in Attachment P to LG&E/KU's OATT. To the extent that there is a conflict between Attachment A and/or Attachment B to this Agreement and Attachment P to LG&E/KU's OATT, Attachment P to LG&E/KU's OATT shall govern. Any changes proposed by LG&E/KU to FERC in Attachment P in LG&E/KU's OATT, pursuant to Section 5.3 of Attachment P in LG&E/KU's OATT, regarding the Functions or any other provisions that concern the Reliability Coordinator shall reflect the mutual agreement of the Parties. Notwithstanding this Section 1.2.1, nothing in this Agreement or Attachment P to LG&E/KU's OATT shall grant FERC any additional jurisdiction over TVA.
Sample 1

Related to Scope of Functions

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • Audit of Existing Content and Functionality By September 1, 2017, the Recipient will propose for OCR’s review and approval the identity and bona fides of an Auditor (corporation or individual) to audit all content and functionality on its website, including, but not limited to, the home page, all subordinate pages, and intranet pages and sites, to identify any online content or functionality that is inaccessible to persons with disabilities, including online content and functionality developed by, maintained by, or offered through a third party vendor or an open source. The Auditor will have sufficient knowledge and experience in website accessibility for people with disabilities to carry out all related tasks, including developing a Proposed Corrective Action Plan. The Audit will use the Benchmarks for Measuring Accessibility set out above, unless the Recipient receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the Recipient will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the Recipient, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

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