Power Market Consultant Sample Clauses

Power Market Consultant. 32 PPA ..................................... 32
Sample 1See All (8)
AutoNDA by SimpleDocs
Power Market Consultant. For purposes of this Agreement, the "Power Market Consultant" shall be Pace Global Energy Services, LLC or such other replacement power market consulting firm selected in accordance with this Section 10.1. Borrower or the Majority Banks may remove the Power Market Consultant in the event that such Power Market Consultant (a) ceases to be a power market consulting firm of recognized international standing, (b) has become an Affiliate of NEG or (c) has developed a conflict of interest that reasonably calls into question such firm's capacity to exercise independent judgment. If the Power Market Consultant is removed or resigns and thereby ceases to act as Power Market Consultant for purposes of this Agreement, the Majority Banks and Borrower shall, within 30 days of such removal or resignation, jointly designate a replacement power market consulting firm from the list contained in Exhibit P hereto and, thereafter, Administrative Agent shall promptly notify the Banks and the Lender Group Agents on behalf of their respective Lender Groups of such designation. At any time and from time to time, the Majority Banks shall have the right to add to Exhibit P hereto one or more independent power market consulting firms and shall notify Borrower, the Banks and the Lender Group Agents on behalf of their respective Lender Groups of any such addition. Exhibit P hereto shall automatically be deemed amended to reflect such addition unless, within 30 days of such notification, Borrower notifies Administrative Agent that it objects, on the basis of the criteria set out in clauses (a) through (c) above for removal of the Power Market Consultant, to the firm or firms so added. At any time while the Obligations are outstanding, Administrative Agent, the Arrangers, the Banks and the Lender Group Members shall have the right, but shall not be obligated (other than as expressly provided herein or in the other Credit Documents), to consult with the Power Market Consultant on matters related to this Agreement or any other Credit Document. All reasonable fees and expenses of the Power Market Consultant (whether the original one or replacements) shall be paid by Borrower.
Sample 1Sample 2

Related to Power Market Consultant

  • Information Management Information and Records

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Information Services The Custodian may rely upon information received from issuers of Securities or agents of such issuers, information received from Subcustodians or depositories, information from data reporting services that provide detail on corporate actions and other securities information, and other commercially reasonable industry sources; and, provided the Custodian has acted in accordance with the standard of care set forth in Section 6 (a), the Custodian shall have no liability as a result of relying upon such information sources, including but not limited to errors in any such information.

  • LICENSE HOLDER CONTACT INFORMATION This noƟce is being provided for informaƟon purposes. It does not create an obligaƟon for you to use the broker’s services. Please acknowledge receipt of this noƟce below and retain a copy for your records. Davidson Bogel Real Estate, LLC 9004427 xxxx@xx0xx.xxx 214-526-3626 Licensed Broker /Broker Firm Name or Primary Assumed Business Name License No. Email Phone Xxxxxxx Xxxxxx Xxxxx XX 598526 xxxxxx@xx0xx.xxx 214-526-3626 Designated Broker of Firm License No. Email Phone Xxxxxxxxxxx Xxxx Xxxxxx 672133 xxxxxxx@xx0xx.xxx 214-526-3626 Licensed Supervisor of Sales Agent/ Associate License No. Email Phone N/A N/A N/A N/A Sales Agent/Associate’s Name License No. Email Phone Buyer/Tenant/Seller/Landlord Initials Date Regulated by the Texas Real Estate Commission InformaƟon available at xxx.xxxx.xxxxx.xxx

  • Information Sources The Custodian may rely upon information received from issuers of Investments or agents of such issuers, information received from Subcustodians and from other commercially reasonable sources such as commercial data bases and the like, but shall not be responsible for specific inaccuracies in such information, provided that the Custodian has relied upon such information in good faith, or for the failure of any commercially reasonable information provider.

  • INFORMATION ASSURANCE (a) Information provided by LOCKHEED XXXXXX to SELLER remains the property of LOCKHEED XXXXXX. SELLER shall comply with the terms of any proprietary information agreement with LOCKHEED XXXXXX and comply with all proprietary information markings and restrictive legends applied by LOCKHEED XXXXXX to anything provided hereunder to SELLER. SELLER shall not use any LOCKHEED XXXXXX provided information for any purpose except to perform this Contract and shall not disclose such information to third parties without the prior written consent of LOCKHEED XXXXXX. SELLER shall maintain data protection processes and systems sufficient to adequately protect LOCKHEED XXXXXX provided information and comply with any law or regulation applicable to such information.

  • 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

  • State Approval of Replacement Personnel The Engineer may not replace the project manager or key personnel without prior consent of the State. The State must be satisfied that the new project manager or other key personnel is qualified to provide the authorized services. If the State determines that the new project manager or key personnel is not acceptable, the Engineer may not use that person in that capacity and shall replace him or her with one satisfactory to the State within forty-five (45) days.

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