Common use of Excessive SLA Failure Trigger Waivers and Applicability Clause in Contracts

Excessive SLA Failure Trigger Waivers and Applicability. The SLAs used to calculate the Aggregate Net SLA Monthly Penalty Rate shall include all SLAs other than (i) any SLA identified as inapplicable to the Excessive SLA Failure Trigger on Exhibit F of the Agreement, as updated from time to time by mutual agreement of the parties and (ii) any SLAs that the Owner/Servicer and Subservicer have agreed to waive or exclude on the basis of major events beyond the Subservicer’s control which materially and adversely affect the servicing of the Subject Loans under the Agreement, including, without limitation, conflicts or issues with Approved Parties or Vendors selected by the Owner/Servicer, regulatory changes, Force Majeure Events or events affecting the mortgage servicing industry as a whole and not specific to Subservicer. In the event of a major computer software system change to the Subservicer's primary servicing system, the parties will agree to waive the Excessive SLA Failure Trigger Event and the Excessive SLA Failure Trigger for a period of six (6) calendar months from the date that such system change was implemented; provided that the Subservicer provided at least ninety (90) days' notice to the Owner/Servicer of such system change.

Excessive SLA Failure Trigger Waivers and Applicability. The SLAs used to calculate the Aggregate Net SLA Monthly Penalty Rate shall include all SLAs other than (i) any SLA identified as inapplicable to the Excessive SLA Failure Trigger on Exhibit F of the Agreement, as updated from time to time by mutual agreement of the parties and (ii) any SLAs that the Owner/Servicer and Subservicer have agreed to waive or exclude on the basis of major events beyond the Subservicer’s control which materially and adversely affect the servicing of the Subject Loans under the Agreement, including, without limitation, conflicts or issues with Approved Parties or Parties, any “Approved Parties” (as defined herein), Vendors selected by the Owner/Servicer, HLSS or NRM, any NRZ REO Vendor (under and as defined in the Servicing Addendum) or any subcontractors or subvendors retained by any such NRZ REO Vendor, regulatory changes, Force Majeure Events or events affecting the mortgage servicing industry as a whole and not specific to Subservicer. In the event of a major computer software system change to the Subservicer's ’s primary servicing system, the parties will agree to waive the Excessive SLA Failure Trigger Event and the Excessive SLA Failure Trigger for a period of six (6) calendar months from the date that such system change was implemented; provided that the Subservicer provided at least ninety (90) days' ’ notice to the Owner/Servicer of such system change.

Excessive SLA Failure Trigger Waivers and Applicability. The SLAs used to calculate the Aggregate Net SLA Monthly Penalty Rate shall include all SLAs other than (i) any SLA identified as inapplicable to the Excessive SLA Failure Trigger on Exhibit F of the Agreement, as updated from time to time by mutual agreement of the parties and (ii) any SLAs that the Owner/Servicer and Subservicer have agreed to waive or exclude on the basis of major events beyond the Subservicer’s control which materially and adversely affect the servicing of the Subject Loans under the Agreement, including, without limitation, conflicts or issues with Approved Parties or Parties, any “Approved Parties” (as defined herein), Vendors selected by the Owner/Owner/ Servicer, HLSS or Shellpoint, any NRZ REO Vendor (under and as defined in the Servicing Addendum) or any subcontractors or subvendors retained by any such NRZ REO Vendor, regulatory changes, Force Majeure Events or events affecting the mortgage servicing industry as a whole and not specific to Subservicer. In the event of a major computer software system change to the Subservicer's ’s primary servicing system, the parties will agree to waive the Excessive SLA Failure Trigger Event and the Excessive SLA Failure Trigger for a period of six (6) calendar months from the date that such system change was implemented; provided that the Subservicer provided at least ninety (90) days' ’ notice to the Owner/Servicer of such system change.

Excessive SLA Failure Trigger Waivers and Applicability. The SLAs used to calculate the Aggregate Net SLA Monthly Penalty Rate shall include all SLAs other than (i) any SLA identified as inapplicable to the Excessive SLA Failure Trigger on Exhibit F of the Agreement, as updated from time to time by mutual agreement of the parties and (ii) any SLAs that the Owner/Servicer Holdings and Subservicer Seller have agreed to waive or exclude on the basis of major events beyond the SubservicerSeller’s control which materially and adversely affect the servicing of the Subject Loans under the Agreement, including, without limitation, conflicts or issues with Approved Parties (under and as defined in the NRZ Subservicing Agreements) or Vendors selected by the OwnerHoldings or any NRZ O/ServicerS Entity, any NRZ REO Vendor or any subcontractors or subvendors retained by such NRZ REO Vendor, regulatory changes, Force Majeure Events or events affecting the mortgage servicing industry as a whole and not specific to SubservicerSeller. In the event of a major computer software system change to the Subservicer's Seller’s primary servicing system, the parties will agree to waive the Excessive SLA Failure Trigger Event and the Excessive SLA Failure Trigger for a period of six (6) calendar months from the date that such system change was implemented; provided that the Subservicer Seller provided at least ninety (90) days' ’ notice to the Owner/Servicer Holdings of such system change.