Grid User Declaration Sample Clauses

Grid User Declaration. XXXX must receive the proof that the Grid User has signed without reserves the Grid User Declaration containing the following clauses:  “The Grid User hereby gives the BSP the permission to offer the Slow R3NR Service to XXXX as described in the General Framework Agreement for Slow R3NR Service by non-CIPU Units (hereinafter, “General Framework Agreement”) concluded between the BSP and XXXX, from to .  “The Grid User hereby acknowledges that all given information in this Grid User Declaration is true and accurate.”  “The Grid User hereby acknowledges submitting this information for one BSP and that he will participate in the Slow R3NR Service by non-CIPU Technical Units service with only one BSP at the same time.”  “The Grid User hereby renounces any possible legal claims that he might invoke against XXXX because of the implementation of the General Framework Agreement for Slow R3NR Service. The Grid User moreover confirms to Xxxx that his commitment to provide Slow R3NR Service as stipulated in this General Framework Agreement does not breach existing contracts with third parties (with whom the Grid User has a contractual or regulated relationship, such as, but not limited to, the Supplier of the Grid User).”  The Grid User acknowledges that the present document is valid until either its respective expiry date or the submission by another BSP of a new Grid User declaration for the Delivery Point Concerned signed and validated by the Grid User.  “The Grid User hereby gives explicit permission to XXXX to inform the BSP of the measurements of the Delivery Points Concerned.”  “Details of the Delivery Point Concerned:” Deliver Point Name Delivery Point Identification (EAN) DPSlowR3NR,max,up [MW]
AutoNDA by SimpleDocs

Related to Grid User Declaration

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Xxxxx’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Access to Project Site Redeveloper shall permit the representatives of the City to enter Project Site at any and all reasonable times, as the City may deem necessary for the purposes of this Redevelopment Agreement, including but not limited to work and inspection of all work being performed in connection with the construction of the Redeveloper Improvements. Similarly, the City shall permit Redeveloper such entry upon the public rights of way for such purposes. No compensation shall be payable nor shall any charges be made in any form by any party for the access or inspection provided for in this Section. The City’s right of access granted under this Section shall terminate upon issuance by the City of the Redeveloper’s Certificate of Completion of Redeveloper Improvements. Notwithstanding the above, Redeveloper shall not be relieved of the provisions contained in Chapter 14.29 of the Lincoln Municipal Code regarding the use of streets for private construction purposes.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). 2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance. 2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks. 2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Dark Fiber Loop 2.8.4.1 Dark Fiber Loop is an unused optical transmission facility, without attached signal regeneration, multiplexing, aggregation or other electronics, from the demarcation point at an End User’s premises to the End User’s serving wire center. Dark Fiber Loops may be strands of optical fiber existing in aerial or underground structure. BellSouth will not provide line terminating elements, regeneration or other electronics necessary for AFN to utilize Dark Fiber Loops.

  • Final Design Provide OWNER with proposed final construction drawings and detailed opinions of probable total Project construction costs in writing for OWNER' s review, prior to completion of the final Contract Documents, so that any changes that may be necessary in accordance with Project' s budgetary schedule can be made prior to bid.

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