Inflow/Outflow Streams Clause Samples

Inflow/Outflow Streams. ‌ The inflow/outflow and Reservoir monitoring sites used by the CRMC and CWA are shown in Section 1.0 (Table 1-2). These sites include 1) on the South Platte River @ Waterton Road upstream of the Reservoir, 2) on Plum Creek @ Titan ▇▇▇▇▇ upstream of the Reservoir and

Related to Inflow/Outflow Streams

  • Revenue Metering The Connecting Transmission Owner’s revenue metering will be located on the generator side of the 115kV breaker at the ▇▇▇▇▇ Solar Collector Substation and will consist of: • three (3) combination current/voltage transformer (“CT/VT”) units (manufacturer and model ABB/▇▇▇▇▇▇▇ KXM-550, GE Grid Solutions KOTEF ▇▇▇.▇▇, or other equivalent specified by Connecting Transmission Owner); and • one (1) revenue meter. The ratios of the CTs and VTs will be provided by Connecting Transmission Owner upon its review of the Interconnection Customer’s design documents. (Note: Connecting Transmission Owner’s revenue metering CTs and VTs cannot be used to feed the Interconnection Customer’s check meter.) SERVICE AGREEMENT NO. 2556

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • Flow Down For all Covered Transactions, including all tiers of subcontracts and subawards, the Recipient shall: (1) require the ▇▇▇ check in section 2; (2) require the certifications in section 3; (3) include the prohibition in section 4; and (4) require all Participants to notify the Recipient in writing of any information that would require the Recipient to notify the USDOT under section 5.

  • Availability Control Personal Data will be protected against accidental or unauthorized destruction or loss.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.