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.
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.
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
Storage Tanks If storage tanks storing Hazardous Materials located on the Premises or the Project are used by Tenant or are hereafter placed on the Premises or the Project by Tenant, Tenant shall install, use, monitor, operate, maintain, upgrade and manage such storage tanks, maintain appropriate records, obtain and maintain appropriate insurance, implement reporting procedures, properly close any storage tanks, and take or cause to be taken all other actions necessary or required under applicable state and federal Legal Requirements, as such now exists or may hereafter be adopted or amended in connection with the installation, use, maintenance, management, operation, upgrading and closure of such storage tanks. Notwithstanding anything to the contrary contained herein, Tenant shall have no right to use or install any underground storage tanks at the Project.
Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.
Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria
Delivery Point The delivery point is the point of delivery of the Power Product to the CAISO Controlled Grid (the “Delivery Point”). Seller shall provide and convey to Buyer the Power Product from the Generating Facility at the Delivery Point. Title to and risk of loss related to the Power Product transfer from Seller to Buyer at the Delivery Point.
Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.
Dark Fiber Transport Dark Fiber Transport is defined as Dedicated Transport that consists of unactivated optical interoffice transmission facilities without attached signal regeneration, multiplexing, aggregation or other electronics. Except as set forth in Section 6.9.1 below, BellSouth shall not be required to provide access to Dark Fiber Transport Entrance Facilities pursuant to this Agreement.
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.