NETWORK EXTENSIONS Sample Clauses

NETWORK EXTENSIONS. Scope This Annex is an addendum to the existing Wholesale Roaming Access Agreement between <Roaming Hubbing Provider><TADIG Code/s> and < Operator B><TADIG code/s> (hereinafter referred to as the “Agreement”) when a National and/or International Network Extension is implemented by <Access Provider name> for the provision of Services to Roaming Customers of < Operator B> through the Client Operator(s) (listed in Attachment A) operating a Public Mobile Network. The Parties hereby agree the following: • The <Access Provider> in all circumstances is responsible to < Operator B> for the adherence by the <Client Operator> to the provisions of the Agreement. • The <Access Provider> is the single point of contact for the < Operator B> • The <Access Provider> shall provide the information required by the < Operator B> for implementation of the National and/or International Network Extension. Parties shall agree in writing, prior to implementing any additional National and/or International Network Extensions. The Parties shall have the right to suspend and/or terminate an individual National and/or International Network Extension in accordance with Articles 14 and 17 of this Agreement. This suspension and/or termination shall not affect the existing Agreement. This Annex supersedes any written or verbal agreement between the Parties with respect to this subject matter. The services provided to the Operator B through the use of a National and/or International Network Extensions shall be set out in the launch letter. Additional launch letters shall be used for the provision of additional services in accordance with this Annex ATTACHMENT “A” CLIENT OPERATOR´S SPECIFICATIONS [Please complete the table below] Client Operator Client Operator TADIG code/s Country of Operation Hereinafter referred to as the “Client Operator”. When roaming through Client Operator, the following deviations and /or amendments to the AA.13 Common Annexes of the Agreement apply: ……….
AutoNDA by SimpleDocs
NETWORK EXTENSIONS. A Network extension is defined as being any addition to the Network within the term of the Access Arrangement. An extension which is directly connected to an existing covered Network will be automatically treated as part of the covered pipeline upon the extension coming into service, unless the following circumstances apply. An extension which is directly connected to an existing covered Network will not be treated as part of the covered pipeline if: • the extension is a Significant Extension (or where Allgas can demonstrate the extension represents a special case); and • Allgas obtains the Authority’s written approval to exclude the extension from the Network.

Related to NETWORK EXTENSIONS

  • Contract Extension The City may, in its sole discretion, unilaterally exercise an option to extend the Contract as described in the Contract Documents. In addition, the City may, in its sole discretion, unilaterally extend the Contract on a month-to-month basis following contract expiration if authorized under Charter section 99 and the Contract Documents. Contractor shall not increase its pricing in excess of the percentage increase described in the Contract.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Support Services HP’s support services will be described in the applicable Supporting Material, which will cover the description of HP’s offering, eligibility requirements, service limitations and Customer responsibilities, as well as the Customer systems supported.

  • Delays and Extensions The CONSULTANT agrees that no charges or claim for damages shall be made by it for any minor delays from any cause whatsoever during the progress of any portion of the Services specified in this Contract. Such delays, if any, shall be compensated for by an extension of time for such period as may be determined by the LPA subject to the CONSULTANT's approval, it being understood, however, that permitting the CONSULTANT to proceed to complete any services, or any part of them after the date to which the time of completion may have been extended, shall in no way operate as a waiver on the part of the LPA of any of its rights herein. In the event of substantial delays or extensions, or change of any kind, not caused by the CONSULTANT, which causes a material change in scope, character or complexity of work the CONSULTANT is to perform under this Contract, the LPA at its sole discretion shall determine any adjustments in compensation and in the schedule for completion of the Services. CONSULTANT must notify the LPA in writing of a material change in the work immediately after the CONSULTANT first recognizes the material change.

  • Extensions If a Registry Operator offers additional Registry Services that require submission of additional data, not included above, additional “extension schemas” shall be defined in a case by case basis to represent that data. These “extension schemas” will be specified as described in Part A, Section 9, reference 2 of this Specification. Data related to the “extensions schemas” will be included in the deposit file described in Part A, Section 3.1 of this Specification. ICANN and the respective Registry Operator shall work together to agree on such new objects’ data escrow specifications.

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