Backbone Infrastructure Clause Samples

Backbone Infrastructure. Developer shall be obligated, in accordance with the requirements of the Phasing Plan for each Development Phase that includes the Property, or any portion thereof, to install any and all Backbone Infrastructure, or applicable components or portions thereof, that are included in the list of Phased Improvements for such approved Development Phase. Subject to County’s discretion pursuant to Section 3.8 below to remove any improvement from the list of Backbone Infrastructure as provided therein, the intent of the parties is that, upon full build-out of all the Properties consistent with the Specific Plan and the Development Agreements, all of the Backbone Infrastructure will have been completed to serve such development of the Properties.
View SourceView Similar (2)
Backbone Infrastructure. Those Public Facilities, public improvements, or items of public benefit as identified in the Financing Plan, Funding Agreement Business Terms, Funding Agreement and Project Entitlements, including without limitation, roads and freeway improvements, parks and open space improvements, wet and dry utilities, police and fire stations, and public parking garages which are required to be constructed in or for the benefit of Development of the Project and that may also benefit adjacent areas that are within the Community Plan area, including the adjacent redevelopment project areas. Backbone Infrastructure may also include the Central Shops if one or more of the buildings are publicly owned and used to provide Public Services.
View SourceView Similar (2)
Backbone Infrastructure. The Financing Plan recognizes that there is a regional cost associated with certain Backbone Infrastructure, and that that fair share will ultimately have to be paid from other sources and other property owners that benefit from such Backbone Infrastructure as identified in the Financing Plan. If a community facilities district or other Public Financing Mechanism is formed or a Development Fee is implemented to finance Backbone Infrastructure, the district may purchase the real property dedicated by LANDOWNER for Backbone Infrastructure as set out at the time of formation of the district.
View Source
Backbone Infrastructure. “Backbone Infrastructure” means those infrastructure improvements which both: (a) are constructed or to be constructed (i) on, to or within the Premises Common Area that serve multiple Phases or multiple Parcels within a Phase or (ii) outside the Premises that are, in the reasonable opinion of Tenant, required to partially or fully serve any portion of the Premises, and (b) consist of (i) the main lines (but not lateral lines serving only Improvements on a single Parcel) for Utilities (including water mains, reclaimed water mains, sanitary sewer mains and storm drainage mains), or (ii) Streets and Roadways.
View Source
Backbone Infrastructure. The Financing Plan recognizes that there is a regional cost associated with certain Backbone Infrastructure, and that that fair share will ultimately have to be paid from other sources and other property owners that benefit from such Backbone Infrastructure as identified in the Financing Plan. LANDOWNER acknowledges that it may have to participate in funding regional costs of Backbone Infrastructure that is located off-site of the Property on a fair share basis as identified in the Financing Plan and Environmental Impact Report. If a community facilities district or other Public Financing Mechanisms is formed to finance Backbone Infrastructure, the district may purchase the real property dedicated by LANDOWNER for Backbone Infrastructure as set out in the Funding Agreement or as approved by CITY at the time of formation of the district. Railyards Development Agreement Revision Date: 12-05-07
View Source
Backbone Infrastructure. As a condition precedent to the conveyance of any Phase of the Property, the City shall use commercially reasonable efforts to cause to be completed the Backbone Infrastructure in accordance with the MIP and the Main Street Neighborhood Plan. The City intends to release a Request for Qualifications for developers of the adjacent portions of the Main Street Neighborhood Plan which will include requirements to construct the Backbone Infrastructure. The City shall use all commercially reasonable efforts to release the Request for Proposals, select a developer or developers, negotiate a disposition and development agreement with the selected developer or developers and require the completion of the Backbone Infrastructure within the times set forth in the Milestone Schedule. The Developer agrees to cooperate with the City's efforts to obtain completion of the Backbone Infrastructure including potentially releasing its interest in certain of the Existing Leases prior to conveyance of a Phase of the Property in order to accommodate the development of the Backbone Infrastructure. The City shall perform its usual inspections prior to acceptance of the Backbone Infrastructure.
View Source

Related to Backbone Infrastructure

  • Infrastructure Modification of the location and/or sizing of the infrastructure for the Project that does not materially change the functionality of the infrastructure.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS 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 WCS 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 WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS 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 WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • 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 Onvoy’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.

  • Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL 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 Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. 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.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’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 Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ 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 ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as 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