Fire Station Site Clause Samples

The 'Fire Station Site' clause designates a specific parcel of land to be used for the construction or operation of a fire station. It typically outlines the location, boundaries, and any conditions or restrictions related to the use of the site, such as access rights, permitted activities, or obligations for maintenance. This clause ensures that the necessary land is clearly identified and reserved for public safety infrastructure, preventing disputes over land use and supporting the timely development of essential emergency services.
Fire Station Site. A site for a fire station, as designated in Exhibit B.1 and B.5.6, which will be constructed, equipped, and operated by the Park City Fire District, shall be dedicated to the Fire District: a) at a time mutually agreed to by the Master Developer and the Fire District, or b) at the time a Final Plat or Site Plan Approval that is inclusive of the physical site for the fire station, but in no event later than five years after the Effective Date of this Agreement.
Fire Station Site. ▇▇▇▇▇▇▇▇▇ agrees to dedicate a site of two (2.0) acres to the SLFPD for purposes of constructing a fire station to serve the Project (the “Fire Station Site”). The precise location of the Fire Station Site shall be shown on the small lot final map that includes either Development Parcel H or Development Parcel I. Landowner’s election to locate the Fire Station Site within either Parcel H or Parcel I shall be made in Landowner’s sole discretion at the time that an application for a small lot final map containing the Fire Station Site is submitted. City agrees that ▇▇▇▇▇▇▇▇▇’s dedication of said Fire Station Site shall fully satisfy Landowner’s obligation to provide a location for a fire station to serve the Project.
Fire Station Site. PCI is obligated to donate 4 acres as depicted on the Willow Springs North PUD Site Plan (the “Fire Station Site”). Permitted use of the Fire Station Site shall be a public fire and EMS station, provided further that permitted uses of the one half (0.5) acre located south of residential Lot 4 shall be limited to a stormwater treatment facility and/or surface parking for passenger vehicles. No vertical construction, storage of vehicles, or dead storage shall be permitted within the one half (0.5) acre located south of Lot 4. The Fire Station Site, including the one half (0.5) acre located south of residential Lot 4, shall be buffered along the common boundary with residential Lot 4 and Lot 3: the County shall install and maintain a 6 foot opaque fence and provide a 20 foot landscape buffer to be planted on the Fire Station side with 2” caliper canopy trees a maximum of 30 feet on center located within 10 feet of the common boundary. In the event the County chooses not to improve the Fire Station Site for a public fire and EMS station by March 31, 2040, by mutual agreement of the parties the restriction on permitted uses of the Fire Station Site may be revised by amendment to this Agreement after said date.
Fire Station Site. DEVELOPER shall convey to the DISTRICT an improved rough-graded legal 10 parcel as depicted on Exhibit “A”, which Exhibit “A” is attached hereto and incorporated 11 herein by this reference, with a minimum buildable pad area of 1.26 acres suitable for a fire 12 station facility, hereinafter referred to as “FIRE STATION SITE”. The FIRE STATION SITE 13 shall be a buildable lot at the time of conveyance as determined by the DISTRICT. Title to 14 the FIRE STATION SITE shall be conveyed in fee simple absolute to the DISTRICT after 15 completion of the improvements and other requirements as indicated in Section II herein. 16 DEVELOPER shall convey title of the FIRE STATION SITE to the DISTRICT prior to the 17 issuance of the 50th building permit within the PROJECT AREA.
Fire Station Site. PCI is obligated to donate 4 acres as depicted on the Willow Springs North PUD Site Plan (the “Fire Station Site”). Permitted use of the Fire Station Site shall be a public fire and EMS station. The Fire Station Site shall be buffered along the common boundary of the adjacent commercial property with the County installing and maintaining a 6 foot opaque fence and providing a 20 foot landscape buffer meeting the standards required by the Land Development Code at the time of plan approval for the Fire Station but in no event less than a 20 foot Type “B” buffer. In the event the County chooses not to improve the Fire Station Site for a public fire and EMS station by March 31, 2040, by mutual agreement of the parties the restriction on permitted uses of the Fire Station Site may be revised by amendment to this Agreement after said date.
Fire Station Site. Within 15 days of the date of this Agreement, the City will purchase that certain fire station site ("Fire Station Site"), described in the Fire Station Deed attached hereto as Exhibit "T", together with any utility and/or drainage and water quality controls and related facilities easements described in Exhibit "T" necessary to develop the Fire Station Site as a fire station, from CCLC for, and in consideration of, the payment by the City to CCLC the lump sum of $679,000.00 payable in cash or other immediately available funds contemporaneously with the delivery of the Fire Station Deed. Title to the Fire Station Site to be conveyed to the City must be free and clear of liens, and free and clear of any easements, restrictions or other encumbrances that would unreasonably limit the City's ability to construct a fire station on the Fire Station Site as confirmed prior to closing by a title commitment or title report from a title company reasonably acceptable to the City, and the land conveyed must not have been made subject to the Commercial Properties Declaration. In addition, the City may designate reasonably necessary lateral support easements for a sidewalk along Escarpment Boulevard from the Fire Station Site to State Highway 45 within one (1) year after the Effective Date and CCLC will grant such lateral support easements by separate instrument in form reasonably satisfactory to the Parties. Any owner's policy of title insurance to insure title to the Fire Station Site will be at the City's sole cost and expense. In addition, the City will pay the recording fee for the Fire Station Deed and all other customary closing costs. The Parties agree that contemporaneously with the execution and delivery of the Fire Station Deed, CCLC will allocate to the Fire Station Site Allowable Impervious Cover (as defined in, and pursuant to the procedure set forth in, the Conservation Easement) equal to 15% of the Net Site Area of the Fire Station Site. Any excess in such Allowable Impervious Cover over the Allowable Impervious Cover shown on the approved Site Development Permit for the Fire Station Site will be assigned by the City to a Parcel designated by CCLC provided that such assignment is otherwise in compliance with the terms of the Conservation Easement. It is agreed that the Fire Station Site does not require any Development Allocation in order to develop and construct a fire station thereon. In the event CCLC causes Parcel 110 to participate in the Balcones Ca...

Related to Fire Station Site

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

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center. 2.4.3 On a semi-annual basis, Teleconex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.5 Two-Way Local 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.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5). 2.4.7 Two-Way Local 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards. 2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.

  • Connecting Transmission Owner’s Attachment Facilities Connecting Transmission Owner shall design, procure, construct, install, own and/or control the Connecting Transmission Owner’s Attachment Facilities described in Appendix A hereto, at the sole expense of the Developer.

  • Access Toll Connecting Trunk Group Architecture 8.2.1 If Reconex chooses to subtend a Verizon access Tandem, Reconex’s NPA/NXX must be assigned by Reconex to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center subtends as identified in the LERG. 8.2.2 Reconex 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 Reconex’s Customers. 8.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office Reconex utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the Tandem Verizon utilizes to provide Exchange Access in such LATA. 8.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow Reconex’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access tandem.