Outage Type Clause Samples

Outage Type. The PIP SLA defines Service disruptions as:  Hard Outage  Service Issue 4.3.1 The Service restoration priority determines the ranking of the repair actions against other Service Issues. Priority 1 Total loss of Service or degraded Service to the extent that it is unusable by Customer and Customer is prepared to release its Service for immediate testing Priority 2 Degraded Service, however Customer is able to use the Service and is not prepared to release its Service for immediate testing Priority 3 A problem with the Service that does not impact the functionality of the Service; including a single non-circuit specific quality of Service inquiry. Priority 4 Non Service affecting requests (e.g. a Customer request for an incident report) and all other queries not covered by Priority 1 – 3 above. Scheduled maintenance 4.3.2 A Hard Outage has Priority 1 Service restoration priority with the exception of Bronze Hard outages which are handled as a Priority 2 ticket. Availability and TTR apply to Hard Outages. 4.3.3 A Service Issue has Priority 2 Service restoration priority. PTD, PDR and Jitter apply to Service Issues. 4.3.4 Priority 3 and Priority 4 issues will be addressed by Verizon. However, Priority 3 and Priority 4 issues are not eligible for SLA credits.
View SourceView Similar (17)
Outage Type. The PIP SLA defines Service disruptions as: • Hard Outage • Service Issue 4.3.1 The Service restoration priority determines the ranking of the repair actions against other Service Issues. Priority Level Criteria Priority 1 Total loss of Service or degraded Service to the extent that it is unusable by Customer and Customer is prepared to release its Service for immediate testing. Priority 2 Degraded Service, however Customer is able to use the Service and is not prepared to release its Service for immediate testing.
View Source

Related to Outage Type

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between CLEC Party Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g., 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E-911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 CLEC Party shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which CLEC Party originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Meet Point B Interconnection Trunk group, exceeds (a) the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centum Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing Meet Point A One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,

  • Contract Type Full time equivalency (FTE); and,

  • Scheduled Downtime For the purposes of this Agreement, Scheduled Downtime will mean those hours, as determined by us but which will not occur between the hours of 9:00 AM and 5:00 PM Eastern Time, Monday through Friday without your authorization or unless exigent circumstances exist, during which time we will perform scheduled maintenance or adjustments to the Environment. We will use our best efforts to provide you with at least twenty-four (24) hours of notice prior to scheduling Scheduled Downtime.