Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.
6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order.
6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information.
6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic.
6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor
Underutilization Underutilization of Interconnection Trunks and facilities exists when provisioned capacity of trunks in service for more than six (6) months is greater than the current need. This over-provisioning is an inefficient deployment and use of network resources and results in unnecessary costs. Those situations where more capacity exists than actual usage will be handled in the following manner:
a. If a final trunk group is under seventy-five percent (75%) of CCS capacity or a high usage trunk group is under 90% of CCS capacity on a monthly average basis, for each month of any three (3) consecutive months period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty-five percent (25%) excess capacity. In all cases POI requirements and grade of service objectives shall be maintained.
b. CLEC will send an ASR to CenturyLink to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment.
Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.
Utilization Utilization shall be defined as Trunks Required as a percentage of Trunks In Service. 1 During implementation the Parties will mutually agree on an Economic Centum Call Seconds (ECCS) or some other means for the sizing of this trunk group.
4.6.3.1 In A Blocking Situation (Over-utilization):
4.6.3.1.1 In a blocking situation, CLEC is responsible for issuing ASRs on all two-way Local Only, Local Interconnection, Third Party and Meet Point Trunk Groups and one-way CLEC originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, AT&T-21STATE will issue a TGSR. CLEC will issue an ASR within three (3) business days after receipt and review of the TGSR. CLEC will note “Service Affecting” on the ASR.
4.6.3.1.2 In a blocking situation, AT&T-21STATE is responsible for issuing ASRs on one-way AT&T-21STATE originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, CLEC will issue a TGSR. AT&T- 21STATE will issue an ASR within three (3) business days after receipt and review of the TGSR.
4.6.3.1.3 If an alternate final Local Only Trunk Group or Local Interconnection Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC for the final trunk group and all subtending high usage trunk groups that are contributing any amount of overflow to the alternate final route.
4.6.3.1.4 If a direct final Meet Point Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC. If a direct final Third Party Trunk Group is at ninety percent (90%) utilization, a TGSR may be sent to CLEC.
Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.
Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System.
4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System.
4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA.
4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code.
4.1.5 The Power Producer shall commission the Project within SCOD.
4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer.
4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.
Utilization Management Contractor shall maintain a utilization management program that complies with applicable laws, rules and regulations, including Health and Safety Code § 1367.01 and other requirements established by the applicable State Regulators responsible for oversight of Contractor.
Registry-‐Level Fees (a) Registry Operator shall pay ICANN a registry-‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-‐level transaction fee (collectively, the “Registry-‐Level Fees”). The registry-‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls.
(b) Subject to Section 6.1(a), Registry Operator shall pay the Registry-‐Level Fees on a quarterly basis to an account designated by ICANN within thirty (30) calendar days following the date of the invoice provided by ICANN.
Utilization Review NOTE: The Utilization Review process does not apply to Services that are not covered by Blue Shield because of a coverage determination made by Medicare. State law requires that health plans disclose to Subscribers and health plan providers the process used to authorize or deny health care services un- der the plan. Blue Shield has completed documen- tation of this process ("Utilization Review"), as required under Section 1363.5 of the California Health and Safety Code. To request a copy of the document describing this Utilization Review pro- cess, call the Customer Service Department at the telephone number indicated on your Identification Card.
Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.
