System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.
ADDITIONAL SPECIAL CONTRACT CONDITIONS Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:
MWBE Utilization Plan A. In accordance with 5 NYCRR § 142.4, Bidders are required to submit a completed Utilization Plan on Form MWBE 100 with their bid.
B. The Utilization Plan shall list the MWBEs the Bidder intends to use to perform the Contract, a description of the Contract scope of work the Bidder intends the MWBE to perform to meet the goals on the Contract, and the estimated or, if known, actual dollar amounts to be paid to an MWBE. By signing the Utilization Plan, the Bidder acknowledges that making false representations or including information evidencing a lack of good faith as part of, or in conjunction with, the submission of a Utilization Plan is prohibited by law and may result in penalties including, but not limited to, termination of a contract for cause, loss of eligibility to submit future bids, and/or withholding of payments. Any modifications or changes to the agreed participation by New York State Certified MWBEs after the Contract award and during the term of the Contract must be reported on a revised MWBE Utilization Plan and submitted to OGS.
C. By entering into the Contract, Bidder/Contractor understands that only sums paid to MWBEs for the performance of a commercially useful function, as that term is defined in 5 NYCRR § 140.1, may be applied towards the achievement of the applicable MWBE participation goal. When an MWBE is serving as a broker on the Contract, only 25 percent of all sums paid to a broker shall be deemed to represent the commercially useful function performed by the MWBE.
D. OGS will review the submitted MWBE Utilization Plan and advise the Bidder of OGS acceptance or issue a notice of deficiency within 30 days of receipt.
E. If a notice of deficiency is issued; Bidder agrees that it shall respond to the notice of deficiency, within 7 business days of receipt, by submitting to OGS a written remedy in response to the notice of deficiency. If the written remedy that is submitted is not timely or is found by OGS to be inadequate, OGS shall notify the Bidder and direct the Bidder to submit, within 5 business days of notification by OGS, a request for a partial or total waiver of MWBE participation goals on Form BDC 333. Failure to file the waiver form in a timely manner may be grounds for disqualification of the bid or proposal.
F. OGS may disqualify a Vendors Submission as being non-responsive under the following circumstances:
(a) If a Bidder fails to submit an MWBE Utilization Plan;
(b) If a Bidder fails to submit a written remedy to a notice of deficiency;
(c) If a Bidder fails to submit a request for waiver; or
(d) If OGS determines that the Bidder has failed to document good faith efforts.
G. If awarded a Contract, Contractor certifies that it will follow the submitted MWBE Utilization Plan for the performance of MWBEs on the Contract pursuant to the prescribed MWBE goals set forth in clause IV-A of this Section.
H. Bidder/Contractor further agrees that a failure to submit and/or use such completed MWBE Utilization Plan shall constitute a material breach of the terms of the Contract. Upon the occurrence of such a material breach, OGS shall be entitled to any remedy provided herein, including but not limited to, a finding of Contractor non- responsiveness.
Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.
Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.
Number Resources, Rate Center Areas and Routing Points 8.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes.
8.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided in the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities.
8.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs.
8.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to Xxxxx’s initial NXXs.
8.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.
EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.
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.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Subloop that may diminish the capability of the Loop or Subloop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the BellSouth’s TR 73600 Unbundled Local Loop Technical Specification.
2.5.2 BellSouth will remove load coils only on copper Loops and Subloops that are less than eighteen thousand (18,000) feet in length.
2.5.3 For any copper loop being ordered by NewPhone which has over six thousand (6,000) feet of combined bridged tap will be modified, upon request from NewPhone, so that the loop will have a maximum of six thousand (6,000) feet of bridged tap. This modification will be performed at no additional charge to NewPhone. Loop conditioning orders that require the removal of bridged tap that serves no network design purpose on a copper Loop that will result in a combined total of bridged tap between two thousand five hundred (2,500) and six thousand (6,000) feet will be performed at the rates set forth in Exhibit A.
2.5.4 NewPhone may request removal of any unnecessary and non-excessive bridged tap (bridged tap between zero (0) and two thousand five hundred (2,500) feet which serves no network design purpose), at rates pursuant to BellSouth’s SC Process as mutually agreed to by the Parties.
2.5.5 Rates for ULM are as set forth in Exhibit A.
2.5.6 BellSouth will not modify a Loop in such a way that it no longer meets the technical parameters of the original Loop type (e.g., voice grade, ADSL, etc.) being ordered.
2.5.7 If NewPhone requests ULM on a reserved facility for a new Loop order, BellSouth may perform a pair change and provision a different Loop facility in lieu of the reserved facility with ULM if feasible. The Loop provisioned will meet or exceed specifications of the requested Loop facility as modified. NewPhone will not be charged for ULM if a different Loop is provisioned. For Loops that require a DLR or its equivalent, BellSouth will provide LMU detail of the Loop provisioned.
2.5.8 NewPhone shall request Loop make up information pursuant to this Attachment prior to submitting a service inquiry and/or a LSR for the Loop type that NewPhone desires BellSouth to condition.
2.5.9 When requesting ULM for a Loop that BellSouth has previously provisioned for NewPhone, NewPhone will submit a SI to BellSouth. If a spare Loop facility that meets the Loop modification specifications requested by NewPhone is available at the location for which the ULM was requested, NewPhone will have the option to change the Loop facility to the qualifying spare facility rather than to provide ULM. In the event that BellSouth changes the Loop facility in lieu of providing ULM, NewPhone will not be charged for ULM but will only be charged the service order charges for submitting an order.
Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.
