Addition of Delivery Points to the Customer List Sample Clauses

Addition of Delivery Points to the Customer List. 11.1 Addition of delivery points 11.2 Addition of an existing delivery point on receipt of churn notification from AEMO (a) Final notification by AEMO to Evoenergy that transfer of a delivery point from another Network User (Outgoing User) to the User has been completed in accordance with the Retail Market Procedures will be deemed to be a Request and Evoenergy must add the delivery point to the relevant Customer List, provided that: (i) the delivery point is already subject to a Reference Service provided by Evoenergy to the Outgoing User; (ii) where the delivery point is to be added to the Volume Customer List, the MHQ required at that delivery point is less than or equal to 6m3/Hour; (iii) where the delivery point is to be added to the Demand Customer List, the User has prior to initiating the transfer of the delivery point under the Retail Market Procedures: (A) advised Evoenergy of the MIRN of that delivery point and the date on which the proposed transfer will occur; and (B) obtained Evoenergy’s written confirmation that the delivery point is subject to a Reference Service provided by Evoenergy to the Outgoing User. (b) Evoenergy may waive any one or more of the requirements set out in clause 11.2(a), in which case Evoenergy must add the delivery point to the Customer List on the satisfaction of those requirements which have not been waived. (c) Evoenergy must use reasonable endeavours to provide the written confirmation required under clause 11.2(a)(iii)(B) within 2 Business Days of receipt of advice pursuant to clause 11.2(a)(iii)(A). (d) Where a delivery point is added as a Delivery Point to the User’s Customer List pursuant to clause 11.2(a) then unless otherwise agreed by Evoenergy: (i) the assigned Tariff Category, and the Assignment Date will be the same as the Tariff Category and Assignment Date for that Delivery Point under the Reference Service previously provided to the Outgoing User; (ii) if the Delivery Point is a Demand Customer Delivery Point, as at the date of the transfer of the Delivery Point, the MDQ, MHQ, Load Shedding Priority or Load Shedding Priorities, Chargeable Demand, Demand Reset Date and ELMS Data for that Delivery Point will be the same as applied to that Delivery Point under the Reference Service previously provided to the Outgoing User; and (iii) any subsequent changes to the MDQ, MHQ, Load Shedding Priority, Chargeable Demand, Demand Reset Date and ELMS Data for that Delivery Point will be made in accordance with the ...
View SourceView Similar (10)
Addition of Delivery Points to the Customer List. 11.1 Addition of delivery points 11.2 Deemed Request Addition of an existing delivery point on receipt of churn notification from AEMO (a) Final notification by AEMO to JGN that transfer of a delivery point from another Network User (Outgoing User) to the User has been completed in accordance with the Retail Market Procedures will be deemed to be a Request and JGN must add the delivery point to the relevant Customer List, provided that: (i) the delivery point is already subject to a Reference Service provided by JGN to the Outgoing User; (ii) where the delivery point is to be added to the Volume Customer List, the MHQ required at that delivery point is less than or equal to 6m3/Hour; (iii) where the delivery point is to be added to the Demand Customer List, the User has prior to initiating the transfer of the delivery point under the Retail Market Procedures: (A) advised JGN of the MIRN of that delivery point and the date on which the proposed transfer will occur; and (B) obtained JGN’s written confirmation that the delivery point is subject to a Reference Service provided by JGN to the Outgoing User.
View Source
Addition of Delivery Points to the Customer List. 11.110.1 Addition by Requestof delivery points The User may at any time Request the Service ProviderJGN to add an existing delivery point to the Customer List in accordance with clause 10.2 or to add a new delivery point to the Relevant Customer List in accordance with clause 10.3.
View Source
Addition of Delivery Points to the Customer List 
View Source

Related to Addition of Delivery Points to the Customer List

  • Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Voice Information Service Traffic ‌ 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service 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 Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a Talk America Customer is served by resold Verizon dial tone line Telecommunications Service, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, Talk America shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to Talk America. Talk America shall pay Verizon such charges in full regardless of whether or not Talk America collects such charges from its Customer. 5.3 Talk America shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event Talk America exercises such option, Talk America will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow Talk America to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless Talk America has entered into a written agreement with Verizon under which Talk America will collect from Talk America’s Customer and remit to Verizon the Voice Information Service provider’s charges, Talk America shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to Talk America. Talk America shall pay Verizon such charges in full regardless of whether or not Talk America collects such charges from its own Customer.

  • Delivery Points ‌ Project water made available to the Agency pursuant to Article 6 shall be delivered to the Agency by the State at the delivery structures established in accordance with Article 10.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.