Stakeholder Process for Regional Rate Filings Sample Clauses

Stakeholder Process for Regional Rate Filings. (i) Absent unanticipated circumstances, every PTO proposal to modify regional rates in accordance with Section 3.04(b) shall be presented by the PTOs to the appropriate stakeholder Technical Committee(s) for consideration and an advisory vote. The Technical Committee, at its next meeting following the one at which the intial presentation is made (which shall be no later than 30 days after any proposal is made), shall: (i) vote on the merits of the proposal as presented or with changes accepted by the PTOs; or (ii) by motion and vote of 66-2/3%, defer action on any proposal presented if it reasonably determines that additional information should and could be provided to more adequately inform the members of such Technical Committee before a vote on the merits is taken. Any deferral shall be for no more than 30 days, after which the PTOs may move for an advisory vote upon their proposal at the next meeting of the Technical Committee (which shall be held within 30 days of the start of the deferral). At that time, the Technical Committee may vote on the merits of the proposal as presented or with changes approved by the Committee, or may vote to oppose the proposal on the grounds that sufficient information has still not been provided, but may not defer consideration of the proposal for any further period without the consent of the PTOs. Failure of the Technical Committee to vote within the time frames set forth in this paragraph shall advance the process to the next step, and in no event shall a period of longer than 60 days be required for the PTOs to submit a proposal to modify regional rate design in accordance with Section 3.04(b) to the Participants Committee. (ii) Absent unanticipated circumstances and after the fulfillment of the procedures outlined in Section 3.04(l)(i), every PTO proposal to modify regional rates in accordance with Section 3.04(b) shall be presented by the PTOs to the stakeholder Participants Committee for an advisory vote, along with a report of any action, failure to act or advisory vote taken by any Technical Committee(s). Such report shall be considered by the Participants Committee no later than the first regularly scheduled meeting following notification of that presentation. The Participants Committee shall: (i) vote on the merits of the proposal as presented or with changes accepted by the PTOs; or (ii) by motion and vote defer action on any proposal if it reasonably determines that the proposal presented is materially differ...
AutoNDA by SimpleDocs

Related to Stakeholder Process for Regional Rate Filings

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-­‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b). (d) Registry Operator shall provide public query-­‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.

  • Xxxxxxxx-Xxxxx; Disclosure Controls The Company is in compliance in all material respects with all of the provisions of the Xxxxxxxx-Xxxxx Act of 2002 which are applicable to it. The Company maintains disclosure controls and procedures (as such term is defined in Rule 13a-15(e) and 15d-15(e) under the Exchange Act), and such disclosure controls and procedures are effective.

  • Financial Management; Financial Reports; Audits 1. The Recipient shall ensure that a financial management system is maintained in accordance with the provisions of Section 2.07 of the Standard Conditions. 2. The Recipient shall ensure that interim unaudited financial reports for the Project are prepared and furnished to the World Bank not later than forty five (45) days after the end of each calendar quarter, covering the quarter, in form and substance satisfactory to the World Bank. 3. The Recipient shall have its Financial Statements for the Project audited in accordance with the provisions of Section 2.07(b) of the Standard Conditions. Each such audit of the Financial Statements shall cover the period of one fiscal year of the Recipient. The audited Financial Statements for each such period shall be furnished to the World Bank not later than six (6) months after the end of such period.

  • Joint Funded Project with the Ohio Department of Transportation In the event that the Recipient does not have contracting authority over project engineering, construction, or right-of-way, the Recipient and the OPWC hereby assign certain responsibilities to the Ohio Department of Transportation, an authorized representative of the State of Ohio. Notwithstanding Sections 4, 6(a), 6(b), 6(c), and 7 of the Project Agreement, Recipient hereby acknowledges that upon notification by the Ohio Department of Transportation, all payments for eligible project costs will be disbursed by the Grantor directly to the Ohio Department of Transportation. A Memorandum of Funds issued by the Ohio Department of Transportation shall be used to certify the estimated project costs. Upon receipt of a Memorandum of Funds from the Ohio Department of Transportation, the OPWC shall transfer funds directly to the Ohio Department of Transportation via an Intra- State Transfer Voucher. The amount or amounts transferred shall be determined by applying the Participation Percentages defined in Appendix D to those eligible project costs within the Memorandum of Funds. In the event that the Project Scope is for right-of-way only, notwithstanding Appendix D, the OPWC shall pay for 100% of the right-of-way costs not to exceed the total financial assistance provided in Appendix C.

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Financial Management, Financial Reports and Audits 1. The Recipient shall maintain or cause to be maintained a financial management system in accordance with the provisions of Section 4.09 of the General Conditions. 2. Without limitation on the provisions of Part A of this Section, the Recipient shall prepare and furnish to the Association not later than forty-five (45) days after the end of each calendar quarter, interim unaudited financial reports for the Project covering the quarter, in form and substance satisfactory to the Association. 3. The Recipient shall have its Financial Statements audited in accordance with the provisions of Section 4.09(b) of the General Conditions. Each audit of the Financial Statements shall cover the period of one (1) fiscal year of the Recipient. The audited Financial Statements for each such period shall be furnished to the Association not later than six (6) months after the end of such period.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Accuracy of Orders; Customer Signatures You shall be responsible for the accuracy, timeliness and completeness of any orders transmitted by you on behalf of your customers by any means, including wire or telephone. In addition, you agree to guarantee the signatures of your customers when such guarantee is required by the Company and you agree to indemnify and hold harmless all persons, including us and the Funds’ transfer agent, from and against any and all loss, cost, damage or expense suffered or incurred in reliance upon such signature guarantee.

  • Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

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