Public Storefront Substation Sample Clauses

Public Storefront Substation. The Master Developer shall reserve a location within the commercial area of the Lakepointe Urban Village for an integrated police storefront substation for the Xxxxxxxxx Police Department. The Master Developer agrees to work cooperatively with the Xxxxxxxxx Police Department on the final location, design, size, and features of such a substation. The Parties acknowledge that the Xxxxxxxxx Police Department will be obligated to pay 80% of market rental rates for such substation if it elects to execute a lease for such a space. This reduced rental rate shall be applicable for the term of this Agreement. Furthermore, the Master Developer and Xxxxxxxxx Police Department will explore the opportunity to set-up and solidify the goals and commitments of the police, Master Developer and private on-site security within the Lakepointe Urban Village.
Sample 1
AutoNDA by SimpleDocs

Related to Public Storefront Substation

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

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

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

  • 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

  • Underground Storage Tanks In accordance with the requirements of Section 3(g) of the D.C. Underground Storage Tank Management Act of 1990, as amended by the District of Columbia Underground Storage Tank Management Act of 1990 Amendment Act of 1992 (D.C. Code § 8-113.01, et seq.) (collectively, the “UST Act”) and the applicable D.C. Underground Storage Tank Regulations, 20 DCMR Chapter 56 (the “UST Regulations”), District hereby informs the Developer that it has no knowledge of the existence or removal during its ownership of the Property of any “underground storage tanks” (as defined in the UST Act). Information pertaining to underground storage tanks and underground storage tank removals of which the D.C. Government has received notification is on file with the District Department of the Environment, Underground Storage Tank Branch, 00 X Xxxxxx, X.X., Xxxxx Xxxxx, Xxxxxxxxxx, X.X., 00000, telephone (000) 000-0000. District’s knowledge for purposes of this Section shall mean and be limited to the actual knowledge of Xxxxxx Xxxxx, Property Acquisition and Disposition Division of the Department of Housing and Community Development, telephone no. (000) 000-0000. The foregoing is set forth pursuant to requirements contained in the UST Act and UST Regulations and does not constitute a representation or warranty by District.

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

  • Underground Facilities All underground pipelines, conduits, ducts, cables, wires, manholes, vaults, tanks, tunnels, or other such facilities or attachments, and any encasements containing such facilities, including without limitation those that convey electricity, gases, steam, liquid petroleum products, telephone or other communications, cable television, water, wastewater, storm water, other liquids or chemicals, or traffic or other control systems.

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.

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