Functional control Sample Clauses

Functional control. By this Agreement, each of the Owners authorizes the Company to exercise functional control over the operation of the Transmission System as necessary to effectuate transmission transactions administered by the Company. Such control shall be exercised in accordance with Good Utility Practice and shall conform to applicable reliability guidelines, policies, standards, rules, regulations, orders, license requirements and all other requirements of the North American Electric Reliability Council, applicable regional reliability councils, or any successor organizations, each Owner’s specific reliability requirements and operating guidelines, and all applicable requirements of federal or state laws or regulatory authorities. Disputes regarding reliability requirements and operating guidelines may be resolved through the Dispute Resolution process provided for in Appendix D to this Agreement. Pending resolution of such disputes, the Owners’ criteria shall be used by the Company until the issue is resolved. The methods of functional control are set forth in more detail in Appendix E to this Agreement.
Sample 1
AutoNDA by SimpleDocs
Functional control. The Transmission Owner authorizes Transco to ------------------ exercise Functional Control over the operation of the Transferred Facilities as necessary to effectuate Transmission Transactions. Such control shall be exercised in accordance with Good Utility Practice and shall conform to applicable reliability guidelines, policies, standards, rules, regulations, orders, license requirements, each Transmission Owner's specific reliability requirements and operating guidelines, and all applicable requirements of federal or state laws or regulatory authorities. Disputes regarding reliability requirements and operating guidelines not resolved by negotiations shall be resolved through the dispute resolution process provided for in the OATT. Pending resolution of such disputes, the Transmission Owner's specific reliability requirements and operating guidelines shall be used by Transco with respect to the Transmission Owner' s facilities until the issue is resolved. The methods of Functional Control are described in more detail in the Operating Protocol attached at Appendix C.
Sample 1

Related to Functional control

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

  • Operational Contacts Each Interconnection Party shall designate, and provide to each other Interconnection Party contact information concerning, a representative to be responsible for addressing and resolving operational issues as they arise during the term of the Interconnection Service Agreement.

  • Quality Control A. Controlled Affiliate agrees to use the Licensed Marks and Name only in connection with the licensed services and further agrees to be bound by the conditions regarding quality control shown in attached Exhibit A as they may be amended by BCBSA from time-to-time. B. Controlled Affiliate agrees to comply with all applicable federal, state and local laws. C. Controlled Affiliate agrees that it will provide on an annual basis (or more often if reasonably required by Plan or by BCBSA) a report or reports to Plan and BCBSA demonstrating Controlled Affiliate’s compliance with the requirements of this Agreement including but not limited to the quality control provisions of this paragraph and the attached Exhibit A. D. Controlled Affiliate agrees that Plan and/or BCBSA may, from time-to-time, upon reasonable notice, review and inspect the manner and method of Controlled Affiliate’s rendering of service and use of the Licensed Marks and Name. E. As used herein, a Controlled Affiliate is defined as an entity organized and operated in such a manner, that it meets the following requirements: (1) A Plan or Plans authorized to use the Licensed Marks in the Service Area of the Controlled Affiliate pursuant to separate License Agreement(s) with BCBSA, other than such Controlled Affiliate’s License Agreement(s), (the “Controlling Plan(s)”), must have the legal authority directly or indirectly through wholly-owned subsidiaries to select members of the Controlled Affiliate’s governing body having not less than 50% voting control thereof and to: (a) prevent any change in the articles of incorporation, bylaws or other establishing or governing documents of the Controlled Affiliate with which the Controlling Plan(s) do(es) not concur; (b) exercise control over the policy and operations of the Controlled Affiliate at least equal to that exercised by persons or entities (jointly or individually) other than the Controlling Plan(s); and Notwithstanding anything to the contrary in (a) through (b) hereof, the Controlled Affiliate’s establishing or governing documents must also require written approval by the Controlling Plan(s) before the Controlled Affiliate can: (i) change its legal and/or trade names; (ii) change the geographic area in which it operates; (iii) change any of the type(s) of businesses in which it engages; (iv) create, or become liable for by way of guarantee, any indebtedness, other than indebtedness arising in the ordinary course of business; (v) sell any assets, except for sales in the ordinary course of business or sales of equipment no longer useful or being replaced; (vi) make any loans or advances except in the ordinary course of business; (vii) enter into any arrangement or agreement with any party directly or indirectly affiliated with any of the owners or persons or entities with the authority to select or appoint members or board members of the Controlled Affiliate, other than the Plan or Plans (excluding owners of stock holdings of under 5% in a publicly traded Controlled Affiliate); (viii) conduct any business other than under the Licensed Marks and Name; (ix) take any action that any Controlling Plan or BCBSA reasonably believes will adversely affect the Licensed Marks and Name. In addition, a Plan or Plans directly or indirectly through wholly owned subsidiaries shall own at least 50% of any for-profit Controlled Affiliate. (2) A Plan or Plans authorized to use the Licensed Marks in the Service Area of the Controlled Affiliate pursuant to separate License Agreement(s) with BCBSA, other than such Controlled Affiliate’s License Agreement(s), (the “Controlling Plan(s)”), have the legal authority directly or indirectly through wholly-owned subsidiaries to select members of the Controlled Affiliate’s governing body having more than 50% voting control thereof and to: (a) prevent any change in the articles of incorporation, bylaws or other establishing or governing documents of the Controlled Affiliate with which the Controlling Plan(s) do(es) not concur; (b) exercise control over the policy and operations of the Controlled Affiliate. In addition, a Plan or Plans directly or indirectly through wholly-owned subsidiaries shall own more than 50% of any for-profit Controlled Affiliate.

  • Traffic Control The Surveyor shall control traffic in and near surveying operations adequately to comply with provisions of the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI which can be found on the State’s internet site. In the event field crew personnel must divert traffic or close traveled lanes, a Traffic Control Plan based upon principles outlined in the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI shall be prepared by the Surveyor and approved by the State prior to commencement of field work. A copy of the approved plan shall be in the possession of field crew personnel on the job site at all times and shall be made available to the State’s personnel for inspection upon request.

  • 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

  • Construction Change Directives 1.1.1, 3.4.2, 3.11, 3.12.8, 4.2.8, 7.1.1, 7.1.2, 7.1.3, 7.3, 9.3.1.1 Construction Schedules, Contractor’s 3.10, 3.11, 3.12.1, 3.12.2, 6.1.3, 15.1.6.2

  • Editorial Control The Licensee shall be permitted only to exercise editorial control over programming to the extent permitted by federal law.

  • Input Control The possibility to subsequently verify and determine whether, and by whom, personal data was entered into, changed or removed from data processing systems must be ensured. • Definition of entry authorisation • Logging of logins

  • Compliance Control Services (1) Support reporting to regulatory bodies and support financial statement preparation by making the Fund's accounting records available to the Trust, the Securities and Exchange Commission (the “SEC”), and the independent accountants. (2) Maintain accounting records according to the 1940 Act and regulations provided thereunder. (3) Perform its duties hereunder in compliance with all applicable laws and regulations and provide any sub-certifications reasonably requested by the Trust in connection with any certification required of the Trust pursuant to the Xxxxxxxx-Xxxxx Act of 2002 (the “SOX Act”) or any rules or regulations promulgated by the SEC thereunder, provided the same shall not be deemed to change USBFS’s standard of care as set forth herein. (4) Cooperate with the Trust’s independent accountants and take all reasonable action in the performance of its obligations under this Agreement to ensure that the necessary information is made available to such accountants for the expression of their opinion on the Fund’s financial statements without any qualification as to the scope of their examination.

  • Attachment A, Scope of Services The scope of services is amended as follows:

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