Common use of Measurement Process Clause in Contracts

Measurement Process. The Outage Duration begins when a network alarm is received by the Contractor from an outage-causing event or the opening of a trouble ticket by the Customer or Contractor, whichever occurs first. Upon notification from the Customer or network alarm, the Contractor shall compile a list for each End-User service affected by a common cause for tracking and reporting of the SLA rights and remedies. Outage Duration shall be measured on a per-End-User service (Circuit ID) basis from information recorded from the network equipment/system or Customer reported trouble ticket. Each End-User service (Circuit ID) is deemed out of service from the first notification until the Contractor determines the End-User service is restored. Any End-User service reported by the End-User/Customer as not having been restored shall have the outage time adjusted to the actual restoration time. Service(s): Rights and Remedies Per Occurrence: 100 percent of the TMRC and ten (10) days ADUC for each End-User service not meeting the committed objective for each CAT 2 fault Monthly Aggregated Measurements: N/A Basic (B) Standard (S) Premier (P) Bidder’s Objective Commitment (B, S or P)

Appears in 2 contracts

Samples: Service Level Agreement, Service Level Agreement

AutoNDA by SimpleDocs

Measurement Process. The Outage Duration begins when a network alarm is received by the Contractor from an outage-causing event or the opening of a trouble ticket by the Customer or Contractor, whichever occurs first. Upon notification from the Customer or network alarm, the Contractor shall compile a list for each End-User service affected by a common cause for tracking and reporting of the SLA rights and remedies. Outage Duration shall be measured on a per-End-User service (Circuit ID) basis from information recorded from the network equipment/system or Customer reported trouble ticket. Each End-User service (Circuit ID) is deemed out of service from the first notification until the Contractor determines the End-User service is restored. Any End-User service reported by the End-User/Customer as not having been restored shall have the outage time adjusted to the actual restoration time. Service(s): Rights and Remedies Per Occurrence: 100 percent of the TMRC and ten (10) days ADUC for each End-User service not meeting the committed objective for each CAT 2 fault Monthly Aggregated Measurements: N/A Basic (B) Standard (S) Premier (P) Bidder’s Objective Objectiv e Commitment (B, S B or P)

Appears in 1 contract

Samples: Service Level Agreement

Measurement Process. The Outage Duration begins when a network alarm is received by the Contractor from an outage-causing event or the opening of a trouble ticket by the Customer or Contractor, whichever occurs first. Upon notification from the Customer or network alarm, the Contractor shall compile a list for each End-User service affected by a the common cause for tracking and reporting of the SLA rights and remedies. Outage Duration shall be measured on a per-End-User service (Circuit ID) basis from information recorded from the network equipment/system or Customer reported trouble ticket. Each End-User service (Circuit ID) is deemed out of service from the first notification until the Contractor determines the End-User service is restored. Any End-User service reported by the End-User/Customer as not having been restored shall have the outage time adjusted to the actual restoration time. Service(s): Rights and Remedies Per Occurrence: 100 percent of the TMRC and ten (10) days Business Days of the ADUC for each End-User service not meeting the committed objective for each CAT 2 fault Monthly Aggregated Measurements: N/A Basic (B) Standard (S) Premier (P) Bidder’s Bidders Objective Commitment (B, S B or P)

Appears in 1 contract

Samples: Service Level Agreement (Sla)

AutoNDA by SimpleDocs

Measurement Process. The Outage Duration begins when a network alarm is received by the Contractor from an the outage-causing event or the opening of a trouble ticket by the Customer Customer, or Contractor, whichever occurs first. Upon notification from the Customer or network alarm, the Contractor shall compile a list for each End-User service affected by a the common cause for tracking and reporting of the SLA rights and remedies. Outage Duration shall be measured on a per-End-User service (Circuit ID) basis from information recorded from the network equipment/system or Customer reported trouble ticket. Each End-User service (Circuit ID) is deemed out of service from the first notification until the Contractor determines the End-User service is restored. Any End-User service reported by the End-User/Customer as not having been restored shall have the outage time adjusted to the actual restoration time. Service(s): Rights and Remedies Per Occurrence: 100 percent of the TMRC and ten (10) days Business Days of the ADUC (when applicable) for each End-User service not meeting the committed objective for each CAT 2 fault fault. Monthly Aggregated Measurements: N/A Basic (B) Standard (S) Premier (P) Bidder’s Bidders Objective Commitment (B, S B or P)

Appears in 1 contract

Samples: Service Level Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!