License of 72 Inch Transmission Main Sample Clauses

License of 72 Inch Transmission Main. The 72 inch water transmission main extending west from the GLWA Water Distribution Point located at the intersection of Xxxxxx and Xxxxxx Roads in Genesee County to the Flint city limits (“72 Inch Main”), as depicted in Exhibit A, shall at all times remain under the ownership or legal control of Customer in order for GLWA to supply potable water in normal and emergency conditions to the Service Area, other GLWA customers, and GCDC and its customers. Customer shall at all times operate and maintain in good working condition the 72 Inch Main.
AutoNDA by SimpleDocs

Related to License of 72 Inch Transmission Main

  • Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).

  • Transmission Delivery Service Implications Network Resource Interconnection Service allows Interconnection Customer's Large Generating Facility to be designated by any Network Customer under the Tariff on Transmission Provider's Transmission System as a Network Resource, up to the Large Generating Facility's full output, on the same basis as existing Network Resources interconnected to Transmission Provider's Transmission System, and to be studied as a Network Resource on the assumption that such a designation will occur. Although Network Resource Interconnection Service does not convey a reservation of transmission service, any Network Customer under the Tariff can utilize its network service under the Tariff to obtain delivery of energy from the interconnected Interconnection Customer's Large Generating Facility in the same manner as it accesses Network Resources. A Large Generating Facility receiving Network Resource Interconnection Service may also be used to provide Ancillary Services after technical studies and/or periodic analyses are performed with respect to the Large Generating Facility's ability to provide any applicable Ancillary Services, provided that such studies and analyses have been or would be required in connection with the provision of such Ancillary Services by any existing Network Resource. However, if an Interconnection Customer's Large Generating Facility has not been designated as a Network Resource by any load, it cannot be required to provide Ancillary Services except to the extent such requirements extend to all generating facilities that are similarly situated. The provision of Network Integration Transmission Service or firm Point-to-Point Transmission Service may require additional studies and the construction of additional upgrades. Because such studies and upgrades would be associated with a request for delivery service under the Tariff, cost responsibility for the studies and upgrades would be in accordance with FERC's policy for pricing transmission delivery services. Network Resource Interconnection Service does not necessarily provide Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on Transmission Provider's Transmission System without incurring congestion costs. In the event of transmission constraints on Transmission Provider's Transmission System, Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in Transmission Provider's Transmission System in the same manner as Network Resources. There is no requirement either at the time of study or interconnection, or at any point in the future, that Interconnection Customer's Large Generating Facility be designated as a Network Resource by a Network Service Customer under the Tariff or that Interconnection Customer identify a specific buyer (or sink). To the extent a Network Customer does designate the Large Generating Facility as a Network Resource, it must do so pursuant to Transmission Provider's Tariff. Once an Interconnection Customer satisfies the requirements for obtaining Network Resource Interconnection Service, any future transmission service request for delivery from the Large Generating Facility within Transmission Provider's Transmission System of any amount of capacity and/or energy, up to the amount initially studied, will not require that any additional studies be performed or that any further upgrades associated with such Large Generating Facility be undertaken, regardless of whether or not such Large Generating Facility is ever designated by a Network Customer as a Network Resource and regardless of changes in ownership of the Large Generating Facility. However, the reduction or elimination of congestion or redispatch costs may require additional studies and the construction of additional upgrades. To the extent Interconnection Customer enters into an arrangement for long term transmission service for deliveries from the Large Generating Facility outside Transmission Provider's Transmission System, such request may require additional studies and upgrades in order for Transmission Provider to grant such request.

  • Interoffice Transmission Facilities BellSouth shall provide nondiscriminatory access, in accordance with FCC Rule 51.311 and Section 251(c)(3) of the Act, to interoffice transmission facilities on an unbundled basis to <<customer_name>> for the provision of a telecommunications service.

  • Loop Transmission Types 3.1 Subject to the conditions set forth in Section 1 of this Attachment, Verizon shall allow CBB to access Loops unbundled from local switching and local transport, in accordance with this Section 3 and the rates and charges provided in the Pricing Attachment. Verizon shall allow CBB access to Loops in accordance with, but only to extent required by, Applicable Law. The available Loop types are as set forth below:

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Transmission Control In-transit: We make HTTPS encryption (also referred to as SSL or TLS) available on every one of its login interfaces and for free on every customer site hosted on the HubSpot products. Our HTTPS implementation uses industry standard algorithms and certificates. At-rest: We store user passwords following policies that follow industry standard practices for security. We have implemented technologies to ensure that stored data is encrypted at rest.

  • NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.

  • Nyiso and Connecting Transmission Owner Authority General.‌‌ NYISO or Connecting Transmission Owner may take whatever actions with regard to the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities it deems necessary during an Emergency State in order to (i) preserve public health and safety, (ii) preserve the reliability of the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities, (iii) limit or prevent damage, and (iv) expedite restoration of service. NYISO and Connecting Transmission Owner shall use Reasonable Efforts to minimize the effect of such actions or inactions on the Large Generating Facility or the Developer’s Attachment Facilities. NYISO or Connecting Transmission Owner may, on the basis of technical considerations, require the Large Generating Facility to mitigate an Emergency State by taking actions necessary and limited in scope to remedy the Emergency State, including, but not limited to, directing Developer to shut-down, start-up, increase or decrease the real or reactive power output of the Large Generating Facility; implementing a reduction or disconnection pursuant to Article 13.4.2; directing the Developer to assist with blackstart (if available) or restoration efforts; or altering the outage schedules of the Large Generating Facility and the Developer’s Attachment Facilities. Developer shall comply with all of the NYISO and Connecting Transmission Owner’s operating instructions concerning Large Generating Facility real power and reactive power output within the manufacturer’s design limitations of the Large Generating Facility’s equipment that is in service and physically available for operation at the time, in compliance with Applicable Laws and Regulations.

  • Transmission and Routing of Exchange Access Traffic PURSUANT TO 251(c)(2) 13 5.1 Scope of Traffic 13 5.2 Trunk Group Architecture and Traffic Routing 13 5.3 Logical Trunk Groups 13 5.4 End Office Access 13 ARTICLE VI MEET-POINT BILLING ARRANGEMENTS 14 6.1 Meet-Point Billing Services 14 6.2 Data Format and Data Transfer 14 6.3 Errors or Loss of Access Usage Data 15 6.4 Payment 15 6.5 Additional Limitation of Liability Applicable to Meet-Point Billing Arrangements 16 ARTICLE VII BLV/BLVI TRAFFIC 16

Time is Money Join Law Insider Premium to draft better contracts faster.