Unit Types Sample Clauses

Unit Types. The proposed development agreement does not require a specific unit mix but instead requires at least one third of the units to have an area of 74.3 square metres (800 square feet) or more. Through feedback provided during public consultation, concern has been expressed about who would be living in the building with a preference being indicated for family oriented units. A unit size of 74.3 metres (800 square feet) or larger is generally considered a family type unit in the MPS and LUB. However, not requiring a specific number of bedrooms allows for flexibility in unit configuration to accommodate the needs in the housing market while ensuring that there is still a mix in unit sizes. This application was presented to the District 7 and 8 Planning Advisory Committee (PAC) on June 23, 2014. Its recommendations are sent to Community Council by means of a separate report. The PAC recommended approval of the proposed development and provided the following considerations: • maintaining the existing commercial uses within the zoning with the allowance to increasing commercial size; • further enhancing the pedestrian experience; • driver and pedestrian safety as it relates to visibility; • higher number of bedrooms per unit; and • a stepback on Seymour Street and the south wall in the interest of reducing the massing along Seymour Street. Many of the recommendations and comments from the PAC have been incorporated into the policy and development agreement. The proposed policy and development agreement allow for a small expansion of the types of commercial uses permitted to include personal service uses and yearly and monthly parking but otherwise have mainly kept the uses similar to those already permitted in the zone. Further, as noted earlier in this report, staff have required a proportion of larger unit sizes instead of requiring a specific number of bedrooms per unit to provide flexibility for unit configuration.
View SourceView Similar (3)
Unit Types. “unit types” are the Cottage, Village, Estate, Carriage and Multifamily unit types defined and described in the White Book. Additional unit types, including without limitation unit types for senior housing, may be added to this Agreement, the Final PUD Plan and the White Book with the approval of the Township Administrative Review Committee, subject to the density limitations provided in herein.
View SourceView Similar (2)
Unit Types. 1. The Owner shall build affordable housing units targeting individuals and small families and shall develop at the Development a mix of studio, one- bedroom, two-bedroom and some three-bedroom units. Larger-sized family units should be intentionally clustered in areas with easy access to semi-private green space. 2. Owner shall ensure that there is at all times a building manager that has experience with management of affordable housing. Owner shall prepare a management plan for the rental housing which, at a minimum, shall include provisions for an on-site management office and a community room.
View Source
Unit Types. No. Unit Types One BR Two BR Three BR Four BR 5 BR Not accessible Accessible
View Source

Related to Unit Types

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • Contract Type Full time equivalency (FTE); and,

  • Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).

  • Check Meters Developer, at its option and expense, may install and operate, on its premises and on its side of the Point of Interconnection, one or more check meters to check Connecting Transmission Owner’s meters. Such check meters shall be for check purposes only and shall not be used for the measurement of power flows for purposes of this Agreement, except as provided in Article 7.4 below. The check meters shall be subject at all reasonable times to inspection and examination by Connecting Transmission Owner or its designee. The installation, operation and maintenance thereof shall be performed entirely by Developer in accordance with Good Utility Practice.

  • Number Resources, Rate Center Areas and Routing Points 13.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 13.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided on ASRs as well as the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 13.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 13.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to ▇▇▇▇▇’s initial NXXs. 13.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.