Formation and Functioning of the Core Group Sample Clauses

Formation and Functioning of the Core Group 
AutoNDA by SimpleDocs

Related to Formation and Functioning of the Core Group

  • Operations Support Systems Functions CBT shall provide CLEC, upon CLEC's request, nondiscriminatory access to CBT's Operations Support Systems functions for pre-ordering, ordering, provisioning, maintenance and repair and billing, in accordance with the terms and schedules established in the Commission’s Arbitration Award in Case No. 97-152-TP-ARB, August 14, 1997 (“Arbitration Award”). CBT shall provide CLEC advance written notice of any material changes to CBT operating support systems functions.

  • Information and Services 2.1.1 The Owner shall provide full information in a timely manner regarding the requirements of the Project, including the Owner’s objectives, constraints and criteria, space requirements and relationships, flexibility and expandability requirements, special equipment and systems, and site requirements as reasonably requested by Construction Manager in writing.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • MANAGEMENT FUNCTIONS B-1 The Association recognizes that the management of the Hospital and the direction of the 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:

  • Appropriate Technical and Organizational Measures SAP has implemented and will apply the technical and organizational measures set forth in Appendix 2. Customer has reviewed such measures and agrees that as to the Cloud Service selected by Customer in the Order Form the measures are appropriate taking into account the state of the art, the costs of implementation, nature, scope, context and purposes of the processing of Personal Data.

  • Primary Function (a) The primary function of the troubleshooter shall be to address concerns of bargaining unit employees who seek a determination of their employment status (an employee of regular status or an employee of auxiliary status) pursuant to the terms of this Collective Agreement.

  • Scaling Locations, Rules, and Organizations All logs from timber sold under the terms and conditions of this contract shall be: (1) scaled at a location approved in writing by STATE; (2) scaled by a third-party scaling organization with a current agreement with STATE; and (3) scaled using the Official Log Scaling and Grading Rules (as adopted by the Northwest Log Rules Advisory Group) and STATE special service scaling instructions in effect at the time the logs are scaled. Utilization scale shall be handled in accordance with the section titled, “Utilization Scale.” PURCHASER shall enter into a written agreement with a third-party scaling organization for the scaling of logs removed from the timber sale area. PURCHASER shall furnish STATE with a copy of the scaling agreement upon request. If logs are delivered when a TPSO scaler is not present, PURCHASER must provide STATE with a method to assure protection and accountability. PURCHASER shall provide STATE with remote check scaling opportunities for logs scaled under this contract. The last two loads at each delivery point shall be continuously available for checking. They shall remain available for a minimum of 48 hours unless replaced by other STATE loads. They shall be available as originally presented for scaling; i.e., if truck scaled, they shall be presented in bunks. In the event scaling is suspended for any reason, hauling operations shall be immediately suspended until approved alternate scaling services are provided, or service by the scaling organization is resumed.

  • Iran, Sudan and Foreign Terrorist Organizations The Dissemination Agent and the Administrator represent that neither the Dissemination Agent, the Administrator nor any parent company, wholly- or majority-owned subsidiaries, and other affiliates of the Dissemination Agent or the Administrator is a company identified on a list prepared and maintained by the Texas Comptroller of Public Accounts under Section 2252.153 or Section 2270.0201, Texas Government Code, and posted on any of the following pages of such officer’s internet website: xxxxx://xxxxxxxxxxx.xxxxx.xxx/purchasing/docs/sudan-list.pdf, xxxxx://xxxxxxxxxxx.xxxxx.xxx/purchasing/docs/iran-list.pdf, or xxxxx://xxxxxxxxxxx.xxxxx.xxx/purchasing/docs/fto-list.pdf. The foregoing representation is made solely to enable the Issuer to comply with Section 2252.152, Texas Government Code, and to the extent such Section does not contravene applicable Federal or State law and excludes the Dissemination Agent, the Administrator and each parent company, wholly- or majority-owned subsidiaries, and other affiliates of the Dissemination Agent or the Administrator, if any, that the United States government has affirmatively declared to be excluded from its federal sanctions regime relating to Sudan or Iran or any federal sanctions regime relating to a foreign terrorist organization.

  • Audit of Existing Content and Functionality By May 1, 2017, the District 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 District receives prior permission from OCR to use a different standard as a benchmark. During the Audit, the District will also seek input from members of the public with disabilities, including parents, students, employees, and others associated with the District, and other persons knowledgeable about website accessibility, regarding the accessibility of its online content and functionality.

  • 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: Field # Field Name Description 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

Time is Money Join Law Insider Premium to draft better contracts faster.