Common use of Credit Structure Clause in Contracts

Credit Structure. If the PDR Service Level Standard is not met, it is a Service Issue and is considered Service Restoration Priority 2. If the PDR metric for a pair of Customer Connections or Customer Sites is not being met, Customer may be eligible for a credit. To obtain a credit, a trouble ticket must be opened with Verizon when a PDR Service Level Standard is not being met or if a Service Issue is identified. Verizon will work with Customer to confirm that a PDR issue exists and repair the problem(s), as applicable. Once Verizon confirms that the PDR Service Level Standard is not being met, Verizon will have 30 calendar days to repair the Service to meet the PDR Service Level Standard and close the applicable trouble ticket, and in such an event, Customer will not be eligible for a credit. If, after 30 calendar days of opening the trouble ticket, the PDR Service Level Standard continues to not be met, Customer will qualify for a credit. Customer’s measurement of PDR prior to opening a trouble ticket may be considered by Verizon in determining the need to repair the Service. PDR credit table: For Standard not met Credit as % of MRC Packet Delivery Ratio (PDR) 20% 5.5.4.1 Service Issues occur between pair Ports of the Private IP Network, including SCI. Consequently, two Customer connections will be impacted by each Service Issue. For Service Issue Service Level Standard credit purposes, the MRC will be defined as the average of the MRCs for each of the two impacted Customer Connections.

Credit Structure. If the PDR Service Level Standard is not met, it is a Service Issue and is considered Service Restoration Priority 2. If the PDR metric for a pair of Customer Connections or Customer Sites is not being met, Customer may be eligible for a credit. To obtain a credit, a trouble ticket must be opened with Verizon when a PDR Service Level Standard is not being met or if a Service Issue is identified. Verizon will work with Customer to confirm that a PDR issue exists and repair the problem(s), as applicable. Once Verizon confirms that the PDR Service Level Standard is not being met, Verizon will have 30 calendar days to repair the Service to meet the PDR Service Level Standard and close the applicable trouble ticket, and in such an event, Customer will not be eligible for a credit. If, after 30 calendar days of opening the trouble ticket, the PDR Service Level Standard continues to not be met, Customer will qualify for a credit. Customer’s measurement of PDR prior to opening a trouble ticket may be considered by Verizon in determining the need to repair the Service. PDR credit table: For Standard not met Credit as % of MRC Packet Delivery Ratio (PDR) 20% 5.5.4.1 Service Issues occur between pair Ports of the Private IP Network, including SCI. Consequently, two Customer connections will be impacted by each Service Issue. For Service Issue Service Level Standard credit purposes, the MRC will be defined as the average of the MRCs for each of the two impacted Customer Connections.

Credit Structure. If the PDR Service Level Standard is not met, it is a Service Issue and is considered Service Restoration Priority 2. If the PDR metric for a pair of Customer Connections or Customer Sites is not being met, Customer may be eligible for a credit. To obtain a credit, a trouble ticket must be opened with Verizon when a PDR Service Level Standard is not being met or if a Service Issue is identified. Verizon will work with Customer to confirm that a PDR issue exists and repair the problem(s), as applicable. Once Verizon confirms that the PDR Service Level Standard is not being met, Verizon will have 30 calendar days to repair the Service to meet the PDR Service Level Standard and close the applicable trouble ticket, and in such an event, Customer will not be eligible for a credit. If, after 30 calendar days of opening the trouble ticket, the PDR Service Level Standard continues to not be met, Customer will qualify for a credit. Customer’s measurement of PDR prior to opening a trouble ticket may be considered by Verizon in determining the need to repair the Service. PDR credit table: For Standard not met Credit as % of MRC Packet Delivery Ratio (PDR) 20% 5.5.4.1 Service Issues occur between pair Ports of the Private IP Network, Network including SCI. Consequently, two Customer connections will be impacted by each Service Issue. For Service Issue Service Level Standard credit purposes, the MRC will be defined as the average of the MRCs for each of the two impacted Customer Connections.

Credit Structure. If the PDR Service Level Standard is not met, it is a Service Issue and is considered Service Restoration Priority 2. If the PDR metric for a pair of Customer Connections or Customer Sites is not being met, Customer may be eligible for a credit. To obtain a credit, a trouble ticket must be opened with Verizon when a PDR Service Level Standard is not being met or if a Service Issue is identified. Verizon will work with Customer to confirm that a PDR issue exists and repair the problem(s), as applicable. Once Verizon confirms that the PDR Service Level Standard is not being met, Verizon will have 30 calendar days to repair the Service to meet the PDR Service Level Standard and close the applicable trouble ticket, and in such an event, Customer will not be eligible for a credit. If, after 30 calendar days of opening the trouble ticket, the PDR Service Level Standard continues to not be met, Customer will qualify for a credit. Customer’s measurement of PDR prior to opening a trouble ticket may be considered by Verizon in determining the need to repair the Service. PDR credit table: For Standard not met Credit as % of MRC Packet Delivery Ratio (PDR) 20% 5.5.4.1 Service Issues occur between pair Ports of the Private IP Network, including SCI. Consequently, two Customer connections will be impacted by each Service Issue. For Service Issue Service Level Standard credit purposes, the MRC will be defined as the average of the MRCs for each of the two impacted Customer Connections.%