UNITED STATES
SECURITIES AND EXCHANGE COMMISSION
Washington, D.C. 20549
 
FORM 10-Q
  
x           QUARTERLY REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934

For the quarterly period ended June 30, 2018

OR

o            TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934

For the transition period from              to

Commission file number 001-13585
  
CoreLogic, Inc.
(Exact name of registrant as specified in its charter)
 
Delaware
95-1068610
(State or other jurisdiction of incorporation or organization)
(I.R.S. Employer Identification No.)
 
40 Pacifica, Irvine, California
92618-7471
(Address of principal executive offices)
(Zip Code)
 
(949) 214-1000
(Registrant’s telephone number, including area code)
 
 
Not Applicable
(Former name, former address and former fiscal year, if changed since last report)
 
 
Indicate by check mark whether the registrant (1) has filed all reports required to be filed by Section 13 or 15(d) of the Securities Exchange Act of 1934 during the preceding 12 months (or for such shorter period that the registrant was required to file such reports), and (2) has been subject to such filing requirements for the past 90 days.    Yes   x     No    o
 
Indicate by check mark whether the registrant has submitted electronically and posted on its corporate web site, if any, every Interactive Data File required to be submitted and posted pursuant to Rule 405 of Regulation S-T (§232.405 of this chapter) during the preceding 12 months (or for such shorter period that the registrant was required to submit and post such files).
Yes   x      No    o
 
Indicate by check mark whether the registrant: is a large accelerated filer, an accelerated filer, a non-accelerated filer, or a smaller reporting company. See the definitions of “large accelerated filer,” “accelerated filer,” “smaller reporting company,” and "emerging growth company" in Rule 12b-2 of the Exchange Act.
 
Large accelerated filer
x
Accelerated filer
o
Non-accelerated filer
o   (Do not check if a smaller reporting company)
Smaller reporting company
o
 
 
Emerging growth company
o

o If an emerging growth company, indicate by check mark if the registrant has elected not to use the extended transition period for complying with any new or revised financial accounting standards provided pursuant to Section 13(a) of the Exchange Act.

Indicate by check mark whether the registrant is a shell company (as defined in Rule 12b-2 of the Exchange Act).

Yes   o     No    x

Indicate the number of shares outstanding of each of the issuer’s classes of common stock, as of the latest practicable date.

On July 23, 2018 there were 80,943,867 shares of common stock outstanding.




CoreLogic, Inc.
Table of Contents
 
 
Part I:
Financial Information
 
 
 
Item 1.
Financial Statements (unaudited)
 
 
 
 
 
A. Condensed Consolidated Balance Sheets as of June 30, 2018 and December 31, 2017
 
 
 
 
B. Condensed Consolidated Statements of Operations for the three and six months ended June 30, 2018 and 2017
 
 
 
 
C. Condensed Consolidated Statements of Comprehensive Income for the three and six months ended June 30, 2018 and 2017
 
 
 
 
D. Condensed Consolidated Statements of Cash Flows for the six months ended June 30, 2018 and 2017
 
 
 
 
E. Condensed Consolidated Statement of Stockholder's Equity for the six months ended June 30, 2018
 
 
 
 
F. Notes to Condensed Consolidated Financial Statements
 
 
 
Item 2.
Management's Discussion and Analysis of Financial Condition and Results of Operations
 
 
 
Item 3.
Quantitative and Qualitative Disclosures About Market Risk
 
 
 
Item 4.
Controls and Procedures
 
 
 
Part II:
Other Information
 
 
 
Item 1.
Legal Proceedings
 
 
 
Item 1A.
Risk Factors
 
 
 
Item 2.
Unregistered Sales of Equity Securities and Use of Proceeds
 
 
 
Item 3.
Defaults upon Senior Securities
 
 
 
Item 4.
Mine Safety Disclosures
 
 
 
Item 5.
Other Information
 
 
 
Item 6.
Exhibits





PART I: FINANCIAL INFORMATION
Item 1.  Financial Statements.
CoreLogic, Inc.
Condensed Consolidated Balance Sheets (Unaudited)  
(in thousands, except par value)
June 30,

December 31,
Assets
2018

2017
Current assets:
 
 
 
Cash and cash equivalents
$
85,031

 
$
118,804

Accounts receivable (less allowance for doubtful accounts of $7,187 and $8,229 as of June 30, 2018 and December 31, 2017, respectively)
256,225

 
256,595

Prepaid expenses and other current assets
52,438

 
47,220

Income tax receivable
16,332

 
7,649

Total current assets
410,026

 
430,268

Property and equipment, net
453,780

 
447,659

Goodwill, net
2,317,410

 
2,250,599

Other intangible assets, net
492,120

 
475,613

Capitalized data and database costs, net
326,868

 
329,403

Investment in affiliates, net
42,305

 
38,989

Deferred income tax assets
127

 
366

Other assets
114,197

 
104,516

Total assets
$
4,156,833

 
$
4,077,413

Liabilities and Equity
 

 
 

Current liabilities:
 

 
 

Accounts payable and other accrued expenses
$
159,975

 
$
145,655

Accrued salaries and benefits
64,174

 
93,717

Contract liabilities, current
322,700

 
303,948

Current portion of long-term debt
49,658

 
70,046

Total current liabilities
596,507

 
613,366

Long-term debt, net of current
1,759,050

 
1,683,524

Contract liabilities, net of current
511,837

 
504,900

Deferred income tax liabilities
106,815

 
102,571

Other liabilities
158,385

 
165,176

Total liabilities
3,132,594

 
3,069,537

 
 
 
 
Stockholders' equity:
 

 
 

Preferred stock, $0.00001 par value; 500 shares authorized, no shares issued or outstanding

 

Common stock, $0.00001 par value; 180,000 shares authorized; 80,944 and 80,885 shares issued and outstanding as of June 30, 2018 and December 31, 2017, respectively
1

 
1

Additional paid-in capital
186,816

 
224,455

Retained earnings
940,314

 
877,111

Accumulated other comprehensive loss
(102,892
)
 
(93,691
)
Total stockholders' equity
1,024,239

 
1,007,876

Total liabilities and equity
$
4,156,833

 
$
4,077,413

 
The accompanying notes are an integral part of these condensed consolidated financial statements.

1



CoreLogic, Inc.
Condensed Consolidated Statements of Operations
(Unaudited )
 
For the Three Months Ended
 
For the Six Months Ended
 
June 30,
 
June 30,
(in thousands, except per share amounts)
2018

2017
 
2018
 
2017
Operating revenues
$
488,401

 
$
473,978

 
$
933,301

 
$
913,829

Cost of services (excluding depreciation and amortization shown below)
239,346

 
249,162

 
478,735

 
501,128

Selling, general and administrative expenses
112,022

 
103,552

 
226,974

 
215,400

Depreciation and amortization
47,396

 
42,871

 
93,536

 
86,343

Total operating expenses
398,764


395,585

 
799,245

 
802,871

Operating income
89,637


78,393

 
134,056

 
110,958

Interest expense:
 


 

 
 

 
 

Interest income
224

 
592

 
754

 
930

Interest expense
18,987

 
14,535

 
36,679

 
28,666

Total interest expense, net
(18,763
)

(13,943
)
 
(35,925
)
 
(27,736
)
Gain/(loss) on investments and other, net
2,128

 
(4,353
)
 
2,289

 
(3,418
)
Income from continuing operations before equity in earnings/(losses) of affiliates and income taxes
73,002


60,097

 
100,420

 
79,804

Provision for income taxes
17,307

 
18,635

 
16,596

 
24,909

Income from continuing operations before equity in earnings/(losses) of affiliates
55,695


41,462

 
83,824

 
54,895

Equity in earnings/(losses) of affiliates, net of tax
2,837

 
(280
)
 
3,070


(1,004
)
Net income from continuing operations
58,532


41,182

 
86,894

 
53,891

(Loss)/income from discontinued operations, net of tax
(16
)
 
78

 
(91
)
 
2,495

Gain from sale of discontinued operations, net of tax

 

 

 
312

Net income
$
58,516


$
41,260

 
$
86,803

 
$
56,698

Basic income per share:





 
 
 
 
Net income from continuing operations
$
0.72


$
0.49

 
$
1.07

 
$
0.64

(Loss)/income from discontinued operations, net of tax



 

 
0.03

Gain from sale of discontinued operations, net of tax



 

 

Net income
$
0.72

 
$
0.49

 
$
1.07

 
$
0.67

Diluted income per share:
 


 

 
 

 
 

Net income from continuing operations
$
0.71


$
0.48

 
$
1.05

 
$
0.63

(Loss)/income from discontinued operations, net of tax



 

 
0.03

Gain from sale of discontinued operations, net of tax



 

 

Net income
$
0.71

 
$
0.48

 
$
1.05

 
$
0.66

Weighted-average common shares outstanding:
 


 

 
 

 
 

Basic
81,284


84,548

 
81,269

 
84,490

Diluted
82,440


86,097

 
82,685

 
86,224


The accompanying notes are an integral part of these condensed consolidated financial statements.

2



CoreLogic, Inc.
Condensed Consolidated Statements of Comprehensive Income
(Unaudited)

 
For the Three Months Ended
 
For the Six Months Ended
 
June 30,
 
June 30,
(in thousands)
2018
 
2017
 
2018
 
2017
Net income
$
58,516

 
$
41,260

 
$
86,803

 
$
56,698

Other comprehensive (loss)/income
 

 
 

 
 

 
 

Adoption of new accounting standards

 

 
408

 

Market value adjustments on interest rate swaps, net of tax
4,101

 
50

 
8,238

 
1,580

Foreign currency translation adjustments
(13,486
)
 
3,135

 
(17,600
)
 
16,683

Supplemental benefit plans adjustments, net of tax
(123
)
 
1,731

 
(247
)
 
1,625

Total other comprehensive (loss)/income
(9,508
)
 
4,916

 
(9,201
)
 
19,888

Comprehensive income
$
49,008

 
$
46,176

 
$
77,602

 
$
76,586

 
The accompanying notes are an integral part of these condensed consolidated financial statements.

3



CoreLogic, Inc.
Condensed Consolidated Statements of Cash Flows
(Unaudited)

For the Six Months Ended

June 30,
(in thousands)
2018

2017
Cash flows from operating activities:
 

 
Net income
$
86,803


$
56,698

Less: (Loss)/income from discontinued operations, net of tax
(91
)

2,495

Less: Gain from sale of discontinued operations, net of tax


312

Net income from continuing operations
86,894


53,891

Adjustments to reconcile net income from continuing operations to net cash provided by operating activities:
 


 

Depreciation and amortization
93,536


86,343

Amortization of debt issuance costs
2,744


2,870

Provision for bad debt and claim losses
7,480


7,939

Share-based compensation
19,799


20,939

Equity in (earnings)/losses of affiliates, net of taxes
(3,070
)

1,004

Gain on sale of property and equipment
(19
)

(231
)
Deferred income tax
8,743


6,193

(Gain)/loss on investment and other, net
(2,289
)

3,418

Change in operating assets and liabilities, net of acquisitions:
 


 

Accounts receivable
259


(2,070
)
Prepaid expenses and other current assets
(6,075
)

(4,161
)
Accounts payable and other accrued expenses
(27,234
)

(74,371
)
Contract liabilities
(13,692
)

24,675

Income taxes
(9,704
)

(13,445
)
Dividends received from investments in affiliates
775


1,097

Other assets and other liabilities
(9,732
)

22,357

Net cash provided by operating activities - continuing operations
148,415


136,448

Net cash (used in)/provided by operating activities - discontinued operations
(4
)

3,663

Total cash provided by operating activities
$
148,411


$
140,111

Cash flows from investing activities:
 


 

Purchases of property and equipment
$
(21,378
)

$
(20,237
)
Purchases of capitalized data and other intangible assets
(18,589
)

(17,202
)
Cash paid for acquisitions, net of cash acquired
(141,056
)


Purchases of investments


(70,000
)
Proceeds from sale of property and equipment
197


304

Proceeds from investments
980



Net cash used in investing activities - continuing operations
(179,846
)

(107,135
)
Net cash provided by investing activities - discontinued operations



Total cash used in investing activities
$
(179,846
)

$
(107,135
)
Cash flows from financing activities:
 


 

Proceeds from long-term debt
$
120,095


$
70,000

Repayment of long-term debt
(68,898
)

(35,234
)
Proceeds from issuance of shares in connection with share-based compensation
17,566


4,504

Payment of tax withholdings related to net share settlements
(11,682
)

(13,420
)
Shares repurchased and retired
(63,322
)

(40,950
)
Net cash used in financing activities - continuing operations
(6,241
)

(15,100
)
Net cash provided by financing activities - discontinued operations



Total cash used in financing activities
$
(6,241
)

$
(15,100
)
Effect of exchange rate on cash, cash equivalents and restricted cash
1,379


(993
)
Net change in cash, cash equivalents and restricted cash
(36,297
)

16,883

Cash, cash equivalents and restricted cash at beginning of period
132,154


89,974

Less: Change in cash, cash equivalents and restricted cash - discontinued operations
(4
)

3,663

Plus: Cash swept (to)/from discontinued operations
(4
)

3,663

Cash, cash equivalents and restricted cash at end of period
$
95,857


$
106,857



 

Supplemental disclosures of cash flow information:
 
 
 
Cash paid for interest
$
33,101

 
$
24,076

Cash paid for income taxes
$
24,230

 
$
35,009

Cash refunds from income taxes
$
3,108

 
$
507

Non-cash investing activities:
 
 
 
Capital expenditures included in accounts payable and other accrued expenses
$
11,139

 
$
5,304


The accompanying notes are an integral part of these condensed consolidated financial statements.

4



CoreLogic, Inc.
Condensed Consolidated Statement of Stockholders' Equity
(Unaudited)
 
(in thousands)
Common Stock Shares
 
Common Stock Amount
 
Additional Paid-in Capital
 
Retained Earnings
 
Accumulated Other Comprehensive (Loss)/Income
 
Total
Balance as of December 31, 2017
80,885

 
$
1

 
$
224,455

 
$
877,111

 
$
(93,691
)
 
$
1,007,876

Adoption of new accounting standards

 

 

 
(23,600
)
 
408

 
(23,192
)
Net income

 

 

 
86,803

 

 
86,803

Shares issued in connection with share-based compensation
1,331

 

 
17,566

 

 

 
17,566

Payment of tax withholdings related to net share settlements

 

 
(11,682
)
 

 

 
(11,682
)
Share-based compensation

 

 
19,799

 

 

 
19,799

Shares repurchased and retired
(1,272
)
 

 
(63,322
)
 

 

 
(63,322
)
Other comprehensive loss

 

 

 

 
(9,609
)
 
(9,609
)
Balance as of June 30, 2018
80,944

 
$
1

 
$
186,816

 
$
940,314

 
$
(102,892
)
 
$
1,024,239


The accompanying notes are an integral part of these condensed consolidated financial statements.

5




Note 1 – Basis of Condensed Consolidated Financial Statements

CoreLogic, Inc., together with its subsidiaries (collectively "we", "us" or "our"), is a leading global property information, insight, analytics and data-enabled solutions provider operating in North America, Western Europe and Asia Pacific. Our combined data from public, contributory and proprietary sources provides detailed coverage of property, mortgages and other encumbrances, consumer credit, tenancy, location, hazard risk and related performance information. The markets we serve include real estate and mortgage finance, insurance, capital markets and the public sector. We deliver value to clients through unique data, analytics, workflow technology, advisory and managed solutions. Clients rely on us to help identify and manage growth opportunities, improve performance and mitigate risk.

Our condensed consolidated financial information included in this report has been prepared in accordance with accounting principles generally accepted in the U.S. (“GAAP”) for interim financial information pursuant to the rules and regulations of the Securities and Exchange Commission (“SEC”). The preparation of financial statements in conformity with GAAP requires management to make estimates and assumptions that affect amounts reported in the condensed consolidated financial statements and accompanying notes. Actual amounts may differ from these estimated amounts. Certain information and disclosures normally included in financial statements prepared in accordance with GAAP have been condensed or omitted pursuant to such rules and regulations. The 2017 year-end condensed consolidated balance sheet was derived from the Company's audited financial statements for the year ended December 31, 2017 . Interim financial information does not require the inclusion of all the information and footnotes required by GAAP for complete financial statements. Therefore, these financial statements should be read in conjunction with our Annual Report on Form 10-K for the year ended December 31, 2017 .

The accompanying unaudited condensed consolidated interim financial statements reflect all adjustments, consisting of only normal recurring items which, in the opinion of management, are necessary for a fair statement of the results of operations for the periods shown. The results of operations for such periods are not necessarily indicative of the results expected for the full year or for any future periods.

Client Concentration

We generate the majority of our operating revenues from clients with operations in the U.S. residential real estate, mortgage origination and mortgage servicing markets. Approximately 32% and 41% of our operating revenues for the three months ended June 30, 2018 and 2017 , respectively, and 33% and 41% for the six months ended June 30, 2018 and 2017 , respectively, were generated from our top ten clients, who consist of the largest U.S. mortgage originators and servicers. None of our clients accounted for greater than 10% of our operating revenues for the three months ended June 30, 2018 , and two of our clients accounted for approximately 14% and 10% of our operating revenues for the three months ended June 30, 2017 . None of our clients accounted for greater than 10% of our operating revenues for the six months ended June 30, 2018 , and two of our clients accounted for approximately 13% and 10% of our operating revenues for the six months ended June 30, 2017 .

Cash, Cash Equivalents and Restricted Cash

We deem the carrying value of cash, cash equivalents and restricted cash to be a reasonable estimate of fair value due to the nature of these instruments. The following table provides a reconciliation of cash, cash equivalents and restricted cash to amounts shown in the statement of cash flows:

(in thousands)
June 30, 2018
 
June 30, 2017
Cash and cash equivalents
$
85,031

 
$
89,422

Restricted cash included in other assets
9,756

 
17,435

Restricted cash included in prepaid expenses and other current assets
1,070

 

Total cash, cash equivalents and restricted cash
$
95,857

 
$
106,857


Operating Revenue Recognition

We derive our operating revenues primarily from U.S. mortgage lenders, servicers and insurance companies with good creditworthiness. Operating revenue arrangements are written and specify the products or services to be delivered, pricing and payment terms. Operating revenue is recognized when the distinct good or service, or performance obligation, is delivered and control has been transferred to the client. Generally, clients contract with us to provide products and services that are highly

6



interrelated and not separately identifiable. Therefore, the entire contract is accounted for as one performance obligation. At times, some of our contracts have multiple performance obligations where we allocate the total price to each performance obligation based on the estimated relative standalone selling price using observable sales or the cost-plus-margin approach.

For products or services where delivery occurs at a point in time, we recognize operating revenue when the client obtains control of the products upon delivery. When delivery occurs over time, we generally recognize operating revenue ratably over the service period, once initial delivery has occurred. For certain of our products or services, clients may also pay upfront fees, which we defer and recognize as operating revenue over the longer of the contractual term or the expected client relationship period.

Licensing arrangements that provide our clients with the right to access or use our intellectual property are considered functional licenses for which we generally recognize operating revenue based on usage. For arrangements that provide a stand-ready obligation or substantive updates to the intellectual property, which the client is contractually or practically required to use, we recognize operating revenue ratably over the contractual term.

Client payment terms are standard with no significant financing components or extended payment terms granted. In limited cases, we allow for client cancellations for which we estimate a reserve.

See further discussion in Note 6 - Operating Revenues .

Comprehensive Income

Comprehensive income includes all changes in equity except those resulting from investments by shareholders and distributions to shareholders. Specifically, foreign currency translation adjustments, amounts related to supplemental benefit plans, unrealized gains and losses on interest rate swap transactions and unrealized gains and losses on investment are recorded in other comprehensive income. The following table shows the components of accumulated other comprehensive loss, net of taxes as of June 30, 2018 and December 31, 2017 :

(in thousands)
2018
 
2017
Cumulative foreign currency translation
$
(113,240
)
 
$
(95,630
)
Cumulative supplemental benefit plans
(6,884
)
 
(5,461
)
Net unrecognized gains on interest rate swaps
17,232

 
7,400

Accumulated other comprehensive loss
$
(102,892
)
 
$
(93,691
)

Investment in Affiliates, net

Investments in affiliates are accounted for under the equity method of accounting when we are deemed to have significant influence over the affiliate but do not control or have a majority voting interest in the affiliate. Investments are carried at the cost of acquisition, including subsequent impairments, capital contributions and loans from us, plus our equity in undistributed earnings or losses since inception of the investment.

We recorded equity in earnings of affiliates, net of tax of $2.8 million and equity in losses of affiliates, net of tax of $0.3 million for the three months ended June 30, 2018 and 2017 , respectively, and equity in earnings of affiliates, net of tax of $3.1 million and equity in losses of affiliates, net of tax of $1.0 million for the six months ended June 30, 2018 and 2017 , respectively. For the three months ended June 30, 2018 and 2017 , we recorded $0.3 million and $1.9 million , respectively, of operating revenues and $2.0 million and $2.9 million , respectively, of operating expenses related to our investment in affiliates. For the six months ended June 30, 2018 and 2017 , we recorded $0.6 million and $4.1 million , respectively, of operating revenues and $5.3 million and $5.7 million , respectively, of operating expenses related to our investment in affiliates.

Discontinued Operations

In September 2014, we completed the sale of our collateral solutions and field services businesses, which were included in the former reporting segment Asset Management and Processing Solutions ("AMPS"). In September 2012, we completed the wind down of our consumer services business and our appraisal management company business. In September 2011, we closed our marketing services business. In December 2010, we completed the sale of our Employer and Litigation Services businesses.


7



In connection with previous divestitures, we retain the prospect of contingent liabilities for indemnification obligations or breaches of representations or warranties. With respect to one such divestiture, in September 2016, a jury returned an unfavorable verdict against a discontinued operating unit that, if upheld on appeal, could result in indemnification exposure up to $25.0 million , including interest. We do not consider this outcome to be probable and intend to vigorously assert our contractual and other rights, including to pursue an appeal to eliminate or substantially reduce any potential post-divestiture contingency. Any actual liability that comes to fruition would be reflected in our results from discontinued operations.

For the six months ended June 30, 2017 , we recorded a gain of $4.5 million related to a pre-tax legal settlement in AMPS within our discontinued operations. There was no pre-tax legal settlement for the six months ended June 30, 2018 . As of June 30, 2018 and December 31, 2017 , we recorded assets of discontinued operations of $0.5 million and $0.4 million , respectively, within prepaid expenses and other current assets within our condensed consolidated balance sheets. Additionally, as of June 30, 2018 and December 31, 2017 , we recorded liabilities of $1.8 million for both periods, within accounts payable and other accrued expenses.

Tax Escrow Disbursement Arrangements

We administer tax escrow disbursements as a service to our clients in connection with our property tax processing solutions. These deposits are maintained in segregated accounts for the benefit of our clients. Tax escrow deposits totaled $262.8 million as of June 30, 2018 , and $961.5 million as of December 31, 2017 . Because these deposits are held on behalf of our clients, they are not our funds and, therefore, are not included in the accompanying condensed consolidated balance sheets.

These deposits generally remain in the accounts for a period of two to five business days. We generally derive operating income and expenses from these deposits and bear the risk of loss. To mitigate the risk of loss, we diversify the placement of funds across institutions with high credit ratings.

Under our contracts with our clients, if we make a payment in error or fail to pay a taxing authority when a payment is due, we could be held liable to our clients for all or part of the financial loss they suffer as a result of our act or omission. We maintained total claim reserves relating to incorrect disposition of assets of $20.4 million and $21.7 million as of June 30, 2018 , and December 31, 2017 , respectively, of which $9.4 million for both periods are short-term and are reflected within accounts payable and other accrued expenses within our accompanying condensed consolidated balance sheets. The remaining reserves are reflected within other liabilities.

Recent Accounting Pronouncements

In March 2018, the Financial Accounting Standards Board ("FASB") issued guidance pertaining to the accounting of the Tax Cuts and Jobs Act ("TCJA"), allowing companies a year to finalize and record any provisional or inestimable impacts for the TCJA. This guidance was effective upon issuance during the first quarter. The adoption of this guidance did not have a material effect on our financial statements. See Note 9 - Income Taxes for discussion of the impacts of the TCJA on our Company.

In February 2018, the FASB issued guidance permitting companies to reclassify stranded tax effects from the TCJA from accumulated other comprehensive loss to retained earnings. The stranded tax effects consist of deferred taxes originally recorded in accumulated other comprehensive loss that exceed the newly enacted federal corporate tax rate. As permitted in the guidance, we elected to early adopt as of January 1, 2018. The net impact of adoption was a balance sheet reclassification of a $0.4 million unrealized loss within accumulated other comprehensive loss to retained earnings.

In August 2017, the FASB issued guidance to amend and improve the accounting for hedging activities. The amendment eliminates the requirement to separately measure and report hedge ineffectiveness. An initial quantitative assessment to establish that the hedge is highly effective is still required but the amendment allows until the end of the first quarter it is designated to perform the assessment. After initial qualification, a qualitative assessment can be performed if the hedge is highly effective and the documentation at inception can reasonably support an expectation of high effectiveness throughout the hedge’s term. The amendment requires companies to present all hedged accounting elements that affect earnings in the same income statement line as the hedged item. For highly effective cash flow hedges, fair value changes will be recorded in other comprehensive income and reclassified to earnings when the hedged item impacts earnings. The guidance is effective prospectively in fiscal years beginning after December 15, 2018. Early adoption is permitted but we do not anticipate to elect early adoption. We do not expect the adoption of this guidance to have a material impact on our consolidated financial statements.


8



In November 2016, the FASB issued guidance that affects the presentation of restricted cash in the statement of cash flows and related disclosures. The guidance requires that the statement of cash flows explain the change in the combined total of restricted and unrestricted balances. Disclosure of how the statement of cash flows reconciles to the balance sheet is required if restricted cash is shown separately from cash and cash equivalents and the nature of the restrictions. We have adopted this guidance in the current year as required. Please see further discussion above within this Note.

In February 2016, the FASB issued guidance on lease accounting which requires leases with durations greater than 12-months to be recognized on the balance sheet as lease assets and lease liabilities beginning after December 15, 2018. The recognition, measurement and presentation of expenses and cash flows arising from a lease by a lessee will depend on its classification as a finance or operating lease. Early adoption is permitted, however we will elect to adopt via the modified retrospective approach on the required date of January 1, 2019. We are continuing to evaluate the impact of adopting this standard on our consolidated financial statements, controls and processes, and are in the process of implementing a new lease administration software solution. We anticipate that our notes to the consolidated financial statements related to leases will be expanded and the most substantial change to our consolidated financial statements will be a gross-up of our total assets and liabilities of less than 5%, based on our preliminary analysis. Further, the guidance is not expected to materially impact our results of operations in the upcoming fiscal years and interim periods. Once further evaluation is complete we will expand our disclosure regarding the expected impact of adopting the updated guidance.

In January 2016, the FASB issued guidance on accounting for equity investments and financial liabilities. The standard does not apply to equity method investments or investments in consolidated subsidiaries. The update provides that equity investments with readily determinable values be measured at fair value and changes in the fair value flow through net income. These changes historically have been included in other comprehensive income. Equity investments without readily determinable fair values have the option to be measured at fair value or at cost adjusted for changes in observable prices minus impairment. Changes in fair value from the application of either method are also recognized in net income. The standard requires a qualitative assessment of impairment indicators at each reporting period. For financial liabilities, entities that elect the fair value option must recognize the change in fair value attributable to instrument-specific credit risk in other comprehensive loss rather than net income. Lastly, regarding deferred tax assets, the need for a valuation allowance on a deferred tax asset will need to be assessed in relation to available-for-sale debt securities. The guidance is effective for fiscal years beginning after December 15, 2017, and interim periods within those fiscal years. We have adopted this guidance in the current year, which did not have a material impact on our financial statements.

In May 2014, the FASB issued updated guidance on revenue recognition in order to i) remove inconsistencies in revenue requirements, ii) provide a better framework for addressing revenue issues, iii) improve comparability across entities, industries, etc., iv) provide more useful information through improved disclosures, and v) simplify the preparation of financial statements by reducing the number of requirements to which an entity must refer. Under the amendment, an entity should recognize revenue to depict the transfer of promised goods or services to customers in the amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. The guidance also specifies the accounting treatment for the incremental costs of obtaining a contract, which would not have been incurred had the contract not been obtained. Further, an entity is required to disclose sufficient information to enable the user of the financial statements to understand the nature, amount, timing and uncertainty of revenue and cash flows from contracts with customers. The updated guidance provides two methods of adoption: i) retrospective application to each prior reporting period presented, or ii) recognition of the cumulative effect from the retrospective application at the date of initial application.

On January 1, 2018, we adopted this new accounting standard, and all the related amendments, using the modified retrospective approach for all contracts that were not in effect as of the adoption date. The comparative information has not been restated and continues to be reported under the accounting standards in effect for those prior periods. We also applied practical expedients which permit (i) the omission of remaining performance obligations that have contracts with an original expected duration of one year or less, (ii) the omission of performance obligations, which are for usage-based variable consideration, which we will recognize over the term of the arrangements based on the actual usage by the customers and (iii) expensing incremental contract costs, which would have otherwise been recognized in one year or less.

The cumulative effect of the changes made to our condensed consolidated balance sheet as of January 1, 2018 for the adoption of the new accounting standard is as follows:


9



(in thousands)
December 31, 2017
 
Adoption Adjustments
 
January 1, 2018
Assets
 
 
 
 
 
Accounts receivable, net
$
256,595

 
$
(941
)
 
$
255,654

Prepaid expenses and other current assets
47,220

 
(965
)
 
46,255

Other assets
104,516

 
2,546

 
107,062

 
 
 
 
 
 
Liabilities
 
 
 
 
 
Contract liabilities, current
$
303,948

 
$
6,767

 
$
310,715

Contract liabilities, net of current
504,900

 
24,801

 
529,701

Deferred income tax liability
102,571

 
(7,736
)
 
94,835

 
 
 
 
 
 
Equity
 
 
 
 
 
Retained earnings
$
877,111

 
$
(23,183
)
 
$
853,928

Accumulated other comprehensive loss
(93,691
)
 
(9
)
 
(93,700
)

In connection with the adoption of the new accounting guidance, we increased our total contract liabilities by $31.6 million of which $23.2 million was the result of a change in the accounting for contracts containing material rights the client would have not received without entering into the contract. The performance obligation associated with the material right is recognized when the future products or services are transferred or when the option expires. Further, we recorded $1.6 million of contract-related assets associated with the change in accounting, which are presented in prepaid expenses and other current assets and other assets in our condensed consolidated balance sheet. As a result of the adoption-related adjustments previously discussed, we adjusted our related deferred income tax and retained earnings accounts.

The impact of the adoption of the new accounting standard on our condensed consolidated balance sheet is as follows:

 
June 30, 2018
(in thousands)
As Reported
 
Balances Without Adoption Adjustments
 
Effect of Change Higher/(Lower)
Assets
 
 
 
 
 
Accounts receivable, net
$
256,225

 
$
256,501

 
$
(276
)
Prepaid expenses and other current assets
52,438

 
53,632

 
(1,194
)
Income tax receivable
16,332

 
15,345

 
987

Deferred income tax assets
127

 
133

 
(6
)
Other assets
114,197

 
111,675

 
2,522

 
 
 
 
 
 
Liabilities
 
 
 
 
 
Accounts payable and other accrued expenses
$
159,975

 
$
160,167

 
$
(192
)
Contract liabilities, current
322,700

 
314,808

 
7,892

Contract liabilities, net of current
511,837

 
512,820

 
(983
)
Deferred income tax liability
106,815

 
107,872

 
(1,057
)
 
 
 
 
 
 
Equity
 
 
 
 
 
Accumulated other comprehensive loss
$
(102,892
)
 
$
(102,913
)
 
$
21

Retained earnings
940,314

 
943,962

 
(3,648
)




10



The impact of the adoption of the new accounting standard on our condensed consolidated statement of operations is as follows:
 
For the Three Months Ended June 30, 2018
(in thousands)
As Reported
 
Balances Without Adoption Adjustments
 
Effect of Change Higher/(Lower)
Operating revenue
$
488,401

 
$
464,322

 
$
24,079

Cost of services
239,346

 
239,663

 
(317
)
Selling, general and administrative expenses
112,022

 
112,791

 
(769
)
Operating income
89,637

 
64,472

 
25,165

Provision for income taxes
17,307

 
11,608

 
5,699

Net income
58,516

 
39,050

 
19,466


 
For the Six Months Ended June 30, 2018
(in thousands)
As Reported
 
Balances Without Adoption Adjustments
 
Effect of Change Higher/(Lower)
Operating revenue
$
933,301

 
$
908,727

 
$
24,574

Cost of services
478,735

 
479,189

 
(454
)
Selling, general and administrative expenses
226,974

 
227,171

 
(197
)
Operating income
134,056

 
108,831

 
25,225

Provision for income taxes
16,596

 
10,906

 
5,690

Net income
86,803

 
67,268

 
19,535


During the second quarter of 2018, we amended contractual terms, which eliminated certain performance obligations that would have otherwise been fulfilled over time. For the three months ended June 30, 2018 , the difference between revenues as reported and pro forma revenues without the adoption adjustments from the new revenue guidance is primarily due to the removal of the aforementioned performance obligations. We do not expect the new accounting standard to have a material impact to net income on an ongoing basis based on the terms and conditions of contracts in effect at this time. See Note 6 - Operating Revenues for additional information.

Note 2 - Property and Equipment, Net

Property and equipment, net as of June 30, 2018 and December 31, 2017 consists of the following:

(in thousands)
2018
 
2017
Land
$
7,476

 
$
7,476

Buildings
6,487

 
6,487

Furniture and equipment
64,083

 
63,255

Capitalized software
912,798

 
878,156

Leasehold improvements
41,162

 
39,990

Construction in progress
3,419

 
1,349

 
1,035,425

 
996,713

Less accumulated depreciation
(581,645
)
 
(549,054
)
Property and equipment, net
$
453,780

 
$
447,659


Depreciation expense for property and equipment was approximately $22.4 million and $20.1 million for the three months ended June 30, 2018 and 2017 , respectively, and $44.2 million and $40.7 million for the six months ended June 30, 2018 and 2017 , respectively.


11



Note 3 – Goodwill, Net

A reconciliation of the changes in the carrying amount of goodwill and accumulated impairment losses, by operating segment and reporting unit, for the six months ended June 30, 2018 , is as follows:
 
(in thousands)
PIRM
 
UWS
 
Consolidated
Balance as of January 1, 2018
 
 
 
 
 
Goodwill
$
1,029,223

 
$
1,228,901

 
$
2,258,124

Accumulated impairment losses
(600
)
 
(6,925
)
 
(7,525
)
Goodwill, net
1,028,623

 
1,221,976

 
2,250,599

Acquisitions
14,106

 
63,092

 
77,198

Translation adjustments
(10,387
)
 

 
(10,387
)
Balance as of June 30, 2018
 
 
 
 
 
Goodwill, net
$
1,032,342

 
$
1,285,068

 
$
2,317,410


For the six months ended June 30, 2018 , we recorded goodwill of $14.1 million within our Property Intelligence & Risk Management ("PIRM") reporting unit related to the acquisition of eTech Solutions Limited ("eTech"). Further, we recorded goodwill of $63.7 million within our Underwriting & Workflow Solutions ("UWS") reporting unit related to the acquisition of a la mode technologies, LLC ("a la mode"). Finally, we recorded a goodwill adjustment of $0.6 million within our UWS reporting unit related to Mercury Network, LLC ("Mercury"). See Note 12 - Acquisitions for further discussion.

Note 4 – Other Intangible Assets, Net

Other intangible assets, net consist of the following:
 
 
June 30, 2018
 
December 31, 2017
(in thousands)
Gross
 
Accumulated Amortization
 
Net
 
Gross
 
Accumulated Amortization
 
Net
Client lists
$
722,255

 
$
(325,387
)
 
$
396,868

 
$
690,693

 
$
(303,632
)
 
$
387,061

Non-compete agreements
33,830

 
(17,674
)
 
16,156

 
28,118

 
(15,528
)
 
12,590

Trade names and licenses
133,544

 
(54,448
)
 
79,096

 
125,090

 
(49,128
)
 
75,962

 
$
889,629

 
$
(397,509
)
 
$
492,120

 
$
843,901

 
$
(368,288
)
 
$
475,613


Amortization expense for other intangible assets, net was $16.3 million and $13.9 million for the three months ended June 30, 2018 and 2017 , respectively, and $31.5 million and $27.9 million for the six months ended June 30, 2018 and 2017 , respectively.

Estimated amortization expense for other intangible assets, net is as follows:

(in thousands)
 
Remainder of 2018
$
31,135

2019
62,082

2020
60,307

2021
56,989

2022
55,521

Thereafter
226,086

 
$
492,120



12



Note 5 – Long-Term Debt

Our long-term debt consists of the following:

 
 
June 30, 2018
 
December 31, 2017
(in thousands)
Gross
 
Debt Issuance Costs
 
Net
 
Gross
 
Debt Issuance Costs
 
Net
Bank debt:
 
 
 
 
 
 
 
 
 
 


 
Term loan facility borrowings due August 2022, weighted-average interest rate of 3.67% and 3.28% as of June 30, 2018 and December 31, 2017, respectively
$
1,687,500

 
$
(15,004
)
 
$
1,672,496

 
$
1,755,000

 
$
(17,017
)
 
$
1,737,983

 
Revolving line of credit borrowings due August 2022, weighted-average interest rate of 3.68% as of June 30, 2018
120,000

 
(5,944
)
 
114,056

 

 
(6,672
)
 
(6,672
)
Notes:
 

 
 

 
 
 
 

 
 

 
 
 
7.55% senior debentures due April 2028
14,645

 
(46
)
 
14,599

 
14,645

 
(48
)
 
14,597

Other debt:
 

 
 

 
 
 
 

 
 

 


 
Various debt instruments with maturities through 2023
7,557

 

 
7,557

 
7,662

 

 
7,662

Total long-term debt
1,829,702


(20,994
)
 
1,808,708

 
1,777,307


(23,737
)
 
1,753,570

Less current portion of long-term debt
49,658

 

 
49,658

 
70,046

 

 
70,046

Long-term debt, net of current portion
$
1,780,044

 
$
(20,994
)
 
$
1,759,050

 
$
1,707,261


$
(23,737
)

$
1,683,524


As of June 30, 2018 and December 31, 2017 , we have recorded $0.9 million and $1.0 million of accrued interest expense, respectively, on our debt-related instruments within accounts payable and other accrued expenses.

Credit Agreement

In August 2017, we amended and restated our credit agreement (“Credit Agreement”) with Bank of America, N.A. as the administrative agent, and other financial institutions. The Credit Agreement provides for a $1.8 billion five -year term loan A facility (“Term Facility”), and a $700.0 million five-year revolving credit facility ("Revolving Facility"). The Term Facility matures and the Revolving Facility expires in August 2022. The Revolving facility includes a $100.0 million multicurrency revolving sub-facility and a $50.0 million letter of credit sub-facility. The Credit Agreement also provides for the ability to increase the Term Facility and/or Revolving Facility by up to $100.0 million in the aggregate; however the lenders are not obligated to do so. As of June 30, 2018 , we had a remaining borrowing capacity of $580.0 million under the Revolving Facility and we were in compliance with all of our covenants under the Credit Agreement.

Debt Issuance Costs

In connection with the amendment and restatement of the Credit Agreement, in August 2017, we incurred approximately $14.3 million of debt issuance costs of which $14.0 million were initially capitalized within long-term debt, net of current in the accompanying condensed consolidated balance sheets. In addition, when we amended and restated the Credit Agreement we had $12.0 million remaining in previously unamortized costs. We will amortize all of these costs over the term of the Credit Agreement. For the three months ended June 30, 2018 and 2017 , $1.3 million and $ 1.5 million , respectively, were expensed in the accompanying condensed consolidated statement of operations related to debt issuance costs. For the six months ended June 30, 2018 and 2017 , $2.7 million and $2.9 million , respectively, were expensed in the accompanying condensed consolidated statement of operations related to debt issuance costs.

7.55% Senior Debentures

In April 1998, we issued $100.0 million in aggregate principal amount of 7.55% senior debentures due 2028. The indentures governing these debentures, as amended, contain limited restrictions on us.

Interest Rate Swaps

13




We have entered into amortizing interest rate swaps ("Swaps") in order to convert a portion of our interest rate exposure on the Term Facility floating rate borrowings from variable to fixed. Under the Swaps, we agree to exchange floating rate for fixed rate interest payments periodically over the life of the agreement. The floating rates in our Swaps are based on the one-month London interbank offering rate. The notional balances, terms and maturities of our Swaps are currently designed to have at least 50% of our debt as fixed rate.

As of June 30, 2018 , we have four Swaps with a combined remaining notional balance of $1.3 billion , a weighted average fixed interest rate of 1.76% (rates range from 1.03% to 2.61% ), and scheduled terminations through August 2022 . As previously indicated, notional balances under our Swaps are currently scheduled to increase and decrease over their contract lengths based on our expectations of variable debt levels. We currently have scheduled notional amounts of between $1.3 billion and $1.1 billion through March 2021 with $585.0 million thereafter until August 2022 .

We have designated the Swaps as cash flow hedges. The estimated fair value of these cash flow hedges is recorded in prepaid expenses and other current assets and other assets in the accompanying condensed consolidated balance sheets. The estimated fair value of these cash flow hedges resulted in an asset of $23.0 million , of which $1.5 million is classified within prepaid expenses and other current assets as of June 30, 2018 . As of December 31, 2017 , we recorded an asset of $12.0 million within other assets.

Unrealized gains of $4.1 million (net of $1.4 million in deferred taxes) and unrealized gains of $0.1 million (net of less than $0.1 million in deferred taxes) for the three months ended June 30, 2018 and 2017 , respectively, and unrealized gains of $8.2 million (net of $2.7 million in deferred taxes) and unrealized gains of $1.6 million (net of $1.0 million in deferred taxes) for the six months ended June 30, 2018 and 2017 , respectively, were recognized in other comprehensive income related to the Swaps.

Note 6 – Operating Revenues

Operating revenues by solution type consists of the following:

(in thousands)
 
For the Three Months Ended June 30, 2018
 
 
PIRM
 
UWS
 
Corporate and Eliminations
 
Consolidated
Property insights
 
$
127,293

 
$

 
$

 
$
127,293

Insurance & spatial solutions
 
40,861

 

 

 
40,861

Flood data services
 

 
18,911

 

 
18,911

Valuations solutions
 

 
81,456

 

 
81,456

Credit solutions
 

 
78,883

 

 
78,883

Property tax solutions
 

 
117,480

 

 
117,480

Other
 
14,501

 
11,496

 
(2,480
)
 
23,517

Total operating revenue
 
$
182,655

 
$
308,226

 
$
(2,480
)
 
$
488,401


(in thousands)
 
For the Six Months Ended June 30, 2018
 
 
PIRM
 
UWS
 
Corporate and Eliminations
 
Consolidated
Property insights
 
$
250,965

 
$

 
$

 
$
250,965

Insurance & spatial solutions
 
78,025

 

 

 
78,025

Flood data services
 

 
35,885

 

 
35,885

Valuations solutions
 

 
152,900

 

 
152,900

Credit solutions
 

 
160,368

 

 
160,368

Property tax solutions
 

 
207,361

 

 
207,361

Other
 
27,432

 
25,131

 
(4,766
)
 
47,797

Total operating revenue
 
$
356,422

 
$
581,645

 
$
(4,766
)
 
$
933,301


14




Property Insights

Our property insights combine our patented predictive analytics and proprietary and contributed data to enable our clients to improve customer acquisition and retention, detect and prevent fraud, improve mortgage transaction cycle time and cost efficiency, identify real estate trends and neighborhood characteristics, track market performance and increase market share. Our data is comprised of real estate information with crime, site inspection, neighborhood, document images and other information from proprietary sources. We also provide verification of applicant income, identity and certain employment verification services. We typically license data in one of two forms: bulk data licensing and transactional licensing. Operating revenue for bulk data licensing contracts that provide a stand-ready obligation or include substantive updates to the intellectual property is recognized ratably over the contractual term; otherwise operating revenue is recognized upon delivery. For transactional licensing we recognize operating revenue based on usage.

Insurance and Spatial Solutions

Our insurance and spatial solutions provide originators and property and casualty insurers the solutions required to more effectively locate, assess and manage property-level assets and risks through location-based data and analytics. The licensed intellectual property data is generally provided to our clients on a subscription or usage basis. For subscription contracts, operating revenue is recognized ratably over the service period once initial delivery has occurred. For contracts to provide a license to data which is delivered via report or data file, operating revenue is recognized when the client obtains control of the products, which is upon delivery.

Property Tax Solutions

Our property tax solutions are built from aggregated property tax information from over 20,000 taxing authorities. We use this information to advise mortgage lenders and servicers of the property tax payment status of loans in their portfolio and to monitor that status over the life of the loans. If a mortgage lender or servicer requires tax payments to be impounded on behalf of its borrowers, we can also facilitate the transfer of these funds to the taxing authorities and provide the lender or servicer with payment confirmation. Property tax processing revenues are primarily comprised of periodic loan fees and life-of-loan fees. For periodic fee arrangements, we generate monthly fees at a contracted rate for as long as we service the loan. For life-of-loan fee arrangements, we charge a one-time fee when the loan is set-up in our tax servicing system. Life-of-loan fees are deferred and recognized ratably over the expected service period of 10 years and adjusted for early loan cancellation. Revenue recognition rates of loan portfolios are regularly analyzed and adjusted monthly to reflect current trends.

Valuations Solutions

Our valuation solutions represent property valuation-related data driven services and analytics combined with collateral valuation workflow technologies which assist our clients in assessing risk of loss using both traditional and alternative forms of property valuation, driving process efficiencies, and ensuring compliance with lender and governmental regulations. We provide collateral information technology and solutions that automate property appraisal ordering, tracking, documentation and review for lender compliance with government regulations. Revenue for the property appraisal service is recognized when the appraisal service is performed and delivered to the client. In addition, to the extent that we provide continuous access to the hosted software platform, we recognize operating revenue over the term of the arrangement.

Credit Solutions

Our credit solutions provide credit and income verification services to the mortgage and automotive industries. We provide comprehensive information, typically in the form of a report, about credit history, income verification and home address history. We normalize the data to provide a broad range of advanced business information solutions designed to reduce risk and improve business performance. Operating revenue is recognized when the report or information is delivered to the client.

Flood Data Services

Our flood data services provide flood zone determinations primarily to mortgage lenders in accordance with U.S. Federal legislation passed in 1994, which requires that most lenders obtain a determination of the current flood zone status at the time each loan is originated and obtain applicable updates during the life of the loan if contracted to do so. We also provide flood zone determinations to insurance companies. We generally recognize operating revenue upon delivery of the initial determination. If contracted for life of loan monitoring, we recognize operating revenue over the estimated service period.

15




Contract Costs

Incremental costs to obtain or fulfill client contracts are recognized as an asset. As of June 30, 2018 , we had $11.6 million of current deferred costs which are presented in prepaid expenses and other current assets and $21.1 million of long term deferred costs which are presented in other assets in our condensed consolidated balance sheet. These deferred costs primarily include certain set-up and acquisition costs related to property tax solutions and amortize ratably over an expected ten year life and adjusted for early loan cancellations. For the three and six months ended June 30, 2018 we recorded $3.5 million and $6.9 million , respectively, of amortization associated with these deferred costs.

Contract Liabilities

We record a contract liability when amounts are invoiced prior to the satisfaction of a performance obligation. For property tax solutions, we invoice our clients upfront fees for services to be performed over time. For property insights and insurance & spatial solutions we invoice quarterly and annually, commencing upon execution of the contracts or at the beginning of the license term.

As of January 1, 2018, we had $840.4 million in contract liabilities compared to $834.5 million as of June 30, 2018 . The overall change of $5.9 million in contract liability balances are primarily due to $271.4 million of new deferred billings in the current year, offset by $287.4 million of operating revenue recognized, of which $196.9 million related to contracts previously deferred.

Remaining Performance Obligations

The majority of our arrangements are between one and three years with a significant portion being one year or less. For the remaining population of non-cancellable and fixed arrangements greater than one year, as of June 30, 2018 , we had $1.0 billion of remaining performance obligations. We expect to recognize approximately 20% percent of our remaining revenue backlog in 2018 , 28% in 2019 , 19% in 2020 and 33% thereafter. See further discussion on performance obligations in Note 1 - Basis for Condensed Consolidated Financial Statements .

Note 7 – Share-Based Compensation

We currently issue equity awards under the CoreLogic, Inc. 2018 Performance Incentive Plan (the "Plan"), which was approved by our stockholders at our Annual Meeting held in May 2018. The Plan includes the ability to grant restricted stock units ("RSUs"), performance-based restricted stock units ("PBRSUs") and stock options. Prior to the approval of the Plan, we issued share-based awards under the CoreLogic, Inc. 2011 Performance Incentive Plan, as amended, which was preceded by the CoreLogic, Inc. 2006 Incentive Plan. The Plan provides for up to 15,139,084 shares of the Company's common stock to be available for award grants.

We have primarily utilized RSUs and PBRSUs as our share-based compensation instruments for employees and directors. The fair value of any share-based compensation instrument grant is based on the market value of our shares on the date of grant and is recognized as compensation expense over its vesting period.

Restricted Stock Units

For the six months ended June 30, 2018 and 2017 , we awarded 529,725 and 646,774 RSUs, respectively, with an estimated grant-date fair value of $24.8 million and $25.7 million , respectively. The RSU awards will vest ratably over three years. RSU activity for the six months ended June 30, 2018 is as follows:

16



 
Number of
 
Weighted-Average
Grant-Date
(in thousands, except weighted-average fair value prices)
Shares
 
Fair Value
Unvested RSUs outstanding at December 31, 2017
1,309

 
$
37.54

RSUs granted
530

 
$
46.73

RSUs vested
(617
)
 
$
37.01

RSUs forfeited
(26
)
 
$
40.68

Unvested RSUs outstanding at June 30, 2018
1,196

 
$
41.81


As of June 30, 2018 , there was $37.0 million of total unrecognized compensation cost related to unvested RSUs that is expected to be recognized over a weighted-average period of 2.1 years . The fair value of RSUs is based on the market value of our common stock on the date of grant.

Performance-Based Restricted Stock Units

For the six months ended June 30, 2018 and 2017 , we awarded 327,018 and 288,331 PBRSUs, respectively, with an estimated grant-date fair value of $15.1 million and $11.5 million , respectively. These awards are generally subject to service-based, performance-based and market-based vesting conditions. The service and performance period is from January 2018 to December 2020 and the performance metrics are generally adjusted earnings per share. The grants included 152,626 PBRSUs that did not include a market-based condition but had operating revenue as the sole performance metric through the service period ending December 2020.

The performance and service period for the PBRSUs awarded during the six months ended June 30, 2017 is from January 2017 to December 2019 and the performance metrics are adjusted earnings per share and market-based conditions.

The fair values of the awards containing market-based vesting conditions were estimated using Monte-Carlo simulation with the following weighted-average assumptions:

 
For the Six Months Ended June 30,
 
2018
 
2017
 
 
 
 
Expected dividend yield
%
 
%
Risk-free interest rate (1)
2.38
%
 
1.47
%
Expected volatility (2)
23.63
%
 
27.83
%
Average total stockholder return (2)
6.11
%
 
1.46
%

(1)
The risk-free interest rate for the periods within the contractual term of the PBRSUs is based on the U.S. Treasury yield curve in effect at the time of the grant.
(2)
The expected volatility and average total stockholder return are measures of the amount by which a stock price has fluctuated or is expected to fluctuate based primarily on our and our peers' historical data.

PBRSU activity for the six months ended June 30, 2018 is as follows:


17



 
Number of
 
Weighted-Average
Grant-Date
(in thousands, except weighted-average fair value prices)
Shares
 
Fair Value
Unvested PBRSUs outstanding at December 31, 2017
659

 
$
37.22

PBRSUs granted
327

 
$
46.28

PBRSUs vested
(239
)
 
$
39.91

PBRSUs forfeited
(43
)
 
$
39.10

Unvested PBRSUs outstanding at June 30, 2018
704

 
$
41.11


As of June 30, 2018 , there was $17.5 million of total unrecog n ized compensation cost related to unvested PBRSUs that is expected to be recognized over a weighted-average period of 2.2 years. The fair value of PBRSUs is based on the market value of our common stock on the date of grant.

Stock Options

Prior to 2015, we issued stock options as incentive compensation for certain employees. Option activity for the six months ended June 30, 2018 is as follows:

(in thousands, except weighted-average price)
Number of
Shares
 
Weighted-Average
Exercise Price
 
Weighted-Average
Remaining
Contractual Term
 
Aggregate
Intrinsic
Value
Options outstanding at December 31, 2017
1,186

 
$
20.67

 
 
 
 
Options exercised
(594
)
 
$
21.28

 
 
 
 
Options vested, exercisable, and outstanding at June 30, 2018
592

 
$
20.07

 
3.5
 
$
18,829


As of June 30, 2018 , there was no unrecognized compensation cost related to unvested stock options.

The intrinsic value of options exercised was $13.6 million and $2.8 million for the six months ended June 30, 2018 and 2017 , respectively. This intrinsic value represents the difference between the fair market value of our common stock on the date of exercise and the exercise price of each option.

Employee Stock Purchase Plan

The employee stock purchase plan allows eligible employees to purchase our common stock at 85.0% of the lesser of the closing price on the first day or the last day of each quarter. Our employee stock purchase plan was approved by our stockholders at our 2012 annual meeting of stockholders and the first offering period commenced in October 2012. We recognized an expense for the amount equal to the estimated fair value of the discount during each offering period.

The following table sets forth the share-based compensation expense recognized for the three and six months ended June 30, 2018 and 2017 .

 
For the Three Months Ended
 
For the Six Months Ended
 
June 30,
 
June 30,
(in thousands)
2018
 
2017
 
2018
 
2017
RSUs
$
7,238

 
$
6,596

 
$
14,633

 
$
16,378

PBRSUs
3,445

 
1,809

 
4,159

 
3,477

Stock options

 

 

 
144

Employee stock purchase plan
439

 
367

 
1,007

 
940

 
$
11,122

 
$
8,772

 
$
19,799

 
$
20,939



18



The above includes $1.2 million and $1.8 million of share-based compensation expense within cost of services in the accompanying condensed consolidated statements of operations for the three months ended June 30, 2018 and 2017 , respectively, and $3.4 million and $3.1 million for the six months ended June 30, 2018 and 2017 , respectively.

Note 8 – Litigation and Regulatory Contingencies

We have been named in various lawsuits and we may from time to time be subject to audit or investigation by governmental agencies. Currently, governmental agencies are auditing or investigating certain of our operations.

With respect to matters where we have determined that a loss is both probable and reasonably estimable, we have recorded a liability representing our best estimate of the financial exposure based on known facts. For matters where a settlement has been reached, we have recorded the expected amount of such settlements. With respect to audits, investigations or lawsuits that are ongoing, although their final dispositions are not yet determinable, we do not believe that the ultimate resolution of such matters, either individually or in the aggregate, will have a material adverse effect on our financial condition, results of operations or cash flows. The ability to predict the ultimate outcome of such matters involves judgments, estimates and inherent uncertainties. The actual outcome of such matters could differ materially from management’s estimates. We record expenses for legal fees as incurred.

Fair Credit Reporting Act Class Actions

In February 2012, CoreLogic National Background Data, LLC (n/k/a CoreLogic Background Data, LLC ("CBD")) was named as a defendant in a putative class action styled Tyrone Henderson, et. al., v. CoreLogic National Background Data, in the United States District Court for the Eastern District of Virginia. Plaintiffs allege violation of the Fair Credit Reporting Act, and pled a putative class claim relating to CBD’s return of criminal record data in response to search queries initiated by its consumer reporting agency customers, which then prepare and transmit employment background screening reports to their employer customers. The parties agreed to settle the case on a class-wide basis and the settlement was approved in March 2018.

In June 2015, a companion case, Witt v. CoreLogic National Background Data, et. al. was filed in the United States District Court for the Eastern District of Virginia by the same attorneys as in Henderson, alleging the same claim against CBD. Witt also names as a defendant CoreLogic SafeRent, LLC (n/k/a CoreLogic Rental Property Solutions, LLC (“RPS”)) on the theory that RPS provided criminal record “reports” to CBD at the same time that CBD delivered reports to CBD’s consumer reporting agency customers. The parties agreed to settle the case on a class-wide basis and the settlement was approved in March 2018.
    
In July 2017, RPS was named as a defendant in a putative class action lawsuit styled Claudinne Feliciano, et. al., v. CoreLogic SafeRent, LLC, in the United States District Court for the Southern District of New York. The named plaintiff alleges that RPS prepared a background screening report about her that contained a record of a New York Housing Court action without noting that the action had previously been dismissed. On this basis, she seeks damages under the Fair Credit Reporting Act and the New York Fair Credit Reporting Act on behalf of herself and a class of similarly situated consumers with respect to reports issued during the period of July 2015 to the present. RPS has denied the claims and intends to defend the case vigorously.
    
Separation

Following the Separation, we are responsible for a portion of First American Financial Corporation's ("FAFC") contingent and other corporate liabilities. In the Separation and Distribution Agreement we entered into in connection with the Separation (the "Separation and Distribution Agreement"), we agreed with FAFC to share equally in the cost of resolution of a small number of corporate-level lawsuits, including certain consolidated securities litigation matters from which we have since been dropped. There were no liabilities incurred in connection with the consolidated securities matters. Responsibility to manage each case has been assigned to either FAFC or us, with the managing party required to update the other party regularly and consult with the other party prior to certain important decisions, such as settlement. The managing party will also have primary responsibility for determining the ultimate total liability, if any, related to the applicable case. We will record our share of any such liability when the responsible party determines a reserve is necessary. As of June 30, 2018 , no reserves were considered necessary.

In addition, the Separation and Distribution Agreement provides for cross-indemnities principally designed to place financial responsibility for the obligations and liabilities of our predecessor, The First American Corporation's ("FAC") financial services business, with FAFC and financial responsibility for the obligations and liabilities of FAC's information solutions business with us. Specifically, each party will, and will cause its subsidiaries and affiliates to, indemnify, defend and

19



hold harmless the other party, its respective affiliates and subsidiaries and each of its respective officers, directors, employees and agents for any losses arising out of or otherwise in connection with the liabilities each such party assumed or retained pursuant to the Separation.

Note 9 – Income Taxes

The effective income tax rate for income taxes as a percentage of income from continuing operations before equity in earnings/(losses) of affiliates and income taxes was 23.7% and 31.0% for the three months ended June 30, 2018 and 2017 , respectively, and 16.5% and 31.2% for the six months ended June 30, 2018 and 2017 , respectively.

For the three and six months ended June 30, 2018 , when compared to 2017 , the decrease in the effective income tax rate was primarily due to changes in the statutory tax rate from the enactment of the TCJA.

In December 2017, the U.S. passed the TCJA which included a reduction of the U.S. corporate income tax rate from 35.0% to 21.0%, an assessment of a one-time transition tax on certain foreign earnings that were previously tax deferred, a new provision that taxes certain income from foreign operations, a new limitation on deductible interest expense and limitations on the deductibility of certain executive compensation.

At December 31, 2017 , we recorded a provisional tax benefit related to the re-measurement of our deferred tax assets and liabilities due to the reduction in the corporate income tax rate. As of June 30, 2018 , we have not completed our accounting for the tax effects of the TCJA. When our analysis is finalized, any resulting adjustments may materially impact our provision for income taxes and effective tax rate in the period in which the adjustments are made. We currently anticipate finalizing and recording any such adjustments and related elections by the end of 2018 .

We are currently under examination for the years 2010 through 2012, by the U.S., our primary taxing jurisdiction, and various other state taxing authorities. It is reasonably possible the amount of the unrecognized benefits with respect to certain unrecognized tax positions that are not subject to the FAFC indemnification could significantly increase or decrease within the next twelve months and would have an impact on net income. Currently, the Company expects expiration of statutes of limitations, excluding indemnified amounts, on reserves of $4.0 million within the next twelve months.


20



Note 10 – Earnings Per Share

The following is a reconciliation of net income per share:

 
For the Three Months Ended
 
For the Six Months Ended
 
June 30,
 
June 30,
 
2018
 
2017
 
2018
 
2017
(in thousands, except per share amounts)
 
 
 
 
 
 
 
Numerator for basic and diluted net income per share:
 
 
 
 
 
 
 
Net income from continuing operations
$
58,532

 
$
41,182

 
$
86,894

 
$
53,891

(Loss)/income from discontinued operations, net of tax
(16
)
 
78

 
(91
)
 
2,495

Gain from sale of discontinued operations, net of tax

 

 

 
312

Net income
$
58,516

 
$
41,260

 
$
86,803

 
$
56,698

Denominator:
 

 
 

 
 

 
 

Weighted-average shares for basic income per share
81,284

 
84,548

 
81,269

 
84,490

Dilutive effect of stock options and restricted stock units
1,156

 
1,549

 
1,416

 
1,734

Weighted-average shares for diluted income per share
82,440

 
86,097

 
82,685

 
86,224

Income per share
 

 
 

 
 

 
 

Basic:
 

 
 

 
 

 
 

Net income from continuing operations
$
0.72

 
$
0.49

 
$
1.07

 
$
0.64

(Loss)/income from discontinued operations, net of tax

 

 

 
0.03

Gain from sale of discontinued operations, net of tax



 

 

Net income
$
0.72

 
$
0.49

 
$
1.07

 
$
0.67

Diluted:
 

 
 
 
 
 
 
Net income from continuing operations
$
0.71

 
$
0.48

 
$
1.05

 
$
0.63

(Loss)/income from discontinued operations, net of tax

 

 

 
0.03

Gain from sale of discontinued operations, net of tax



 

 

Net income
$
0.71

 
$
0.48

 
$
1.05

 
$
0.66


The dilutive effect of share-based compensation awards has been calculated using the treasury-stock method. For the three months ended June 30, 2018 and 2017 , an aggregate of less than 0.1 million RSUs and PBRSUs, and an aggregate of less than 0.1 million RSUs, respectively, were excluded from the weighted-average diluted common shares outstanding due to their anti-dilutive effect. For the six months ended June 30, 2018 and 2017 , an aggregate of less than 0.1 million RSUs and PBRSUs and an aggregate of less than 0.1 million of RSUs, respectively, were excluded from the weighted-average diluted common shares outstanding due to their anti-dilutive effect.

Note 11 – Fair Value of Financial Instruments

Fair value is the price that would be received upon sale of an asset or paid to transfer a liability in an orderly transaction between market participants at the measurement date. We utilize market data or assumptions that market participants would use in pricing the asset or liability, including assumptions about risk and the risks inherent in the inputs to the valuation technique. These inputs can be readily observable, market corroborated or generally unobservable.

The market approach is applied for recurring fair value measurements and endeavors to utilize the best available information. Accordingly, we utilize valuation techniques that maximize the use of observable inputs and minimize the use of unobservable inputs. Fair value balances are classified based on the observability of those inputs.

A fair value hierarchy prioritizes the inputs used to measure fair value. The hierarchy gives the highest priority to unadjusted quoted prices in active markets for identical assets or liabilities (level 1 measurement) and the lowest priority to

21



unobservable inputs (level 3 measurement). Level 2 measurements utilize observable inputs in active markets for similar assets and liabilities, or, quoted prices in markets that are not active.

In estimating the fair value of the financial instruments presented, we used the following methods and assumptions:

Cash and cash equivalents

For cash and cash equivalents, the carrying value is a reasonable estimate of fair value due to the short-term nature of the instruments.

Restricted cash

Restricted cash is comprised of certificates of deposit that are pledged for various letters of credit/bank guarantees secured by us, escrow accounts due to acquisitions and divestitures and short-term investments within our deferred compensation plan trust. We deem the carrying value to be a reasonable estimate of fair value due to the nature of these instruments.

Contingent consideration

The fair value of the contingent consideration was estimated using the Monte-Carlo simulation model, which relies on significant assumption and estimates including discount rates and future market conditions, among others.

Long-term debt

The fair value of debt was estimated based on the current rates available to us for similar debt of the same remaining maturities and consideration of our default and credit risk.

Swaps

The fair values of the interest rate swap agreements were estimated based on market-value quotes received from the counterparties to the agreements.

The fair values of our financial instruments as of June 30, 2018 are presented in the following table:

 
Fair Value Measurements Using
 
 
(in thousands)
Level 1
 
Level 2
 
Level 3
 
Fair Value
Financial Assets:
 
 
 
 
 
 
 
Cash and cash equivalents
$
85,031

 
$

 
$

 
$
85,031

Restricted cash
2,268

 
$
8,558

 

 
10,826

Total
$
87,299

 
$
8,558

 
$

 
$
95,857

 
 
 
 
 
 
 
 
Financial Liabilities:
 
 
 
 
 
 
 
Contingent consideration
$

 
$

 
$
5,380

 
$
5,380

Total debt

 
1,831,004

 

 
1,831,004

Total
$

 
$
1,831,004

 
$
5,380


$
1,836,384

 
 
 
 
 
 
 
 
Derivatives:
 
 
 
 
 
 
 
Asset for Swaps
$

 
$
22,961

 
$

 
$
22,961


22



The fair values of our financial instruments as of December 31, 2017 are presented in the following table:

 
Fair Value Measurements Using
 
 
(in thousands)
Level 1
 
Level 2
 
Level 3
 
Fair Value
Financial Assets:
 
 
 
 
 
 
 
Cash and cash equivalents
$
118,804

 
$

 
$

 
$
118,804

Restricted cash

 
11,065

 

 
11,065

Total
$
118,804

 
$
11,065

 
$

 
$
129,869

 
 
 
 
 
 
 
 
Financial Liabilities:
 
 
 
 
 
 
 
Contingent consideration
$

 
$

 
$
6,500

 
$
6,500

Total debt

 
1,780,547

 

 
1,780,547

Total
$

 
$
1,780,547

 
$
6,500

 
$
1,787,047

 
 
 
 
 
 
 
 
Derivatives:
 
 
 
 
 
 
 
Asset for Swaps
$

 
$
11,985

 
$

 
$
11,985


There were no transfers between level 1, level 2 or level 3 securities during the three and six months ended June 30, 2018 .

In connection with our 2017 acquisitions, we entered into contingent consideration agreements, which we originally fair valued as $6.2 million using the Monte-Carlo simulation model. See Note 12 - Acquisitions for further discussion. The contingent payments are fair-valued quarterly and changes are recorded within gain/(loss) on investments and other, net in our condensed consolidated statement of operations. For the six months ended June 30, 2018 we decreased the fair value of our contingent considerations by $1.1 million and recorded the gain in our condensed consolidated statement of operations.

Note 12 – Acquisitions

In April 2018, we completed the acquisition of a la mode for $120.0 million , subject to working capital adjustments. a la mode is a provider of subscription based software solutions that facilitate the aggregation of data, imagery and photographs in a GSE compliant format for the completion of U.S. residential appraisals. This acquisition contributes to our continual development and scaling of our end-to-end valuation solutions workflow suite which includes data and market insights, analytics as well as data-enabled services and platforms. a la mode is included as a component of our UWS reporting segment. The purchase price was allocated to the assets acquired and liabilities assumed using a variety of valuation techniques including discounted cash flow analysis, which included significant unobservable inputs. We have preliminarily recorded contract liabilities of $7.5 million , proprietary technology of $15.8 million with an estimated useful life of 7 years , customer lists of $32.5 million with an estimated average useful life of 13 years , tradenames of $9.0 million with an estimated useful life of 8 years , non-compete agreements of $5.7 million with an estimated useful life of 5 years , and goodwill of $63.7 million , of which $61.4 million is deductible for tax purposes. The business combination did not have a material impact on our condensed consolidated statements of operations.

In February 2018, we completed the acquisition of eTech for cash of approximately £15.0 million , or approximately $21.0 million . eTech is a leading provider of innovative mobile surveying and workflow management software that enhances productivity and mitigates risk for participants in the U.K. valuation market. This acquisition expands our U.K. presence and strengthens our technology platform offerings. eTech is included as a component of our PIRM reporting segment. The purchase price was allocated to the assets acquired and liabilities assumed using a variety of valuation techniques including discounted cash flow analysis, which included significant unobservable inputs. We have preliminarily recorded a deferred tax liability of $1.6 million , proprietary technology of $7.0 million with an estimated useful life of 5 years, customer lists of $1.7 million with an estimated average useful life of 9 years, and goodwill of $14.1 million . The business combination did not have a material impact on our condensed consolidated statements of operations.

In August 2017, we completed the acquisition of Myriad for $22.0 million , subject to working capital adjustments, and up to $3.0 million to be paid in cash by 2019, contingent upon the achievement of certain revenue targets in fiscal years 2017 and 2018. We fair valued the contingent payment using the Monte-Carlo simulation model and preliminarily recorded $1.8

23



million as contingent consideration. The contingent payment is fair valued quarterly, and changes are recorded within gain/(loss) on investments and other, net in the condensed consolidated statement of operations. See Note 11 - Fair Value of Financial Instruments for further discussion. This acquisition builds on our software-as-a-service capabilities by offering a workflow tool used by the insurance industry for policy underwriting. Myriad is included as a component of our PIRM reporting segment. The purchase price was allocated to the assets acquired and liabilities assumed using a variety of valuation techniques including discounted cash flow analysis, which included significant unobservable inputs. We have preliminarily recorded a deferred tax liability of $3.1 million , customer lists of $1.7 million with an estimated average life of 12 years , tradenames of $1.6 million with an estimated average life of 7 years , proprietary technology of $5.8 million with an estimated useful life of 8 years and goodwill of $17.3 million . The business combination did not have a material impact on our condensed consolidated statements of operations.

In August 2017, we completed the acquisition of Clareity for $15.0 million , subject to working capital adjustments. This acquisition leverages our market leading position in real estate and provides authentication-related services to real estate brokers and agents. Clareity is included as a component of our PIRM reporting segment. The purchase price was allocated to the assets acquired and liabilities assumed using a variety of valuation techniques including discounted cash flow analysis, which included significant unobservable inputs. We have preliminarily recorded a deferred tax liability of $2.6 million , customer lists of $3.4 million with an estimated average life of 10 years , tradenames of $0.9 million with an estimated average life of 7 years , proprietary technology of $2.0 million with an estimated useful life of 5 years and goodwill of $10.9 million . The business combination did not have a material impact on our condensed consolidated statements of operations.

In June 2017, we acquired a 45.0% interest in Mercury for $70.0 million , which included a call option to purchase the remaining 55.0% interest within the next nine-month period. In August 2017, we purchased the remaining 55.0% ownership of Mercury for an additional $83.0 million . Mercury is a technology company servicing small and medium-sized mortgage lenders and appraisal management companies to manage their collateral valuation operations. This acquisition is included as a component of our UWS segment. The purchase price was allocated to the assets acquired and liabilities assumed using a variety of valuation techniques including discounted cash flow analysis, which included significant unobservable inputs. We preliminarily recorded a deferred tax liability of $19.8 million , tradenames of $3.6 million with an estimated life of 8 years , customer lists of $41.3 million with an estimated life of 10 years , proprietary technology of $20.1 million with an estimated life of 9 years , and goodwill of $104.7 million . During the six months ended June 30, 2018 , goodwill was reduced by approximately $0.6 million as a result of certain working capital adjustments. This business combination did not have a material impact on our condensed consolidated statements of operations.

We incurred $0.9 million and $7.3 million of acquisition-related costs within selling, general and administrative expenses on our condensed consolidated statements of operations for the three months ended June 30, 2018 and 2017 , respectively, and $1.7 million and $7.5 million for the six months ended June 30, 2018 and 2017 , respectively.

Note 13 – Segment Information

We have organized our reportable segments into two segments: PIRM and UWS.

Property Intelligence & Risk Management Solutions . Our PIRM segment combines property information, mortgage information and consumer information to deliver unique housing market and property-level insights, predictive analytics and risk management capabilities. We have also developed proprietary technology and software platforms to access, automate or track this information and assist our clients with decision-making and compliance tools in the real estate industry, insurance industry and the single and multifamily industry. We deliver this information directly to our clients in a standard format over the web, through hosted software platforms or in bulk data form. Our solutions include property insights and insurance & spatial solutions in North America, Western Europe and Asia Pacific. The segment's primary clients are commercial banks, mortgage lenders and brokers, investment banks, fixed-income investors, real estate agents, MLS companies, property and casualty insurance companies, title insurance companies, government agencies and government-sponsored enterprises.

The operating results of our PIRM segment included intercompany revenues of $1.7 million and $1.6 million for the three months ended June 30, 2018 and 2017 , respectively, and $3.2 million and $3.0 million for the six months ended June 30, 2018 and 2017 , respectively. The segment also included intercompany expenses of $0.8 million and $0.7 million for the three months ended June 30, 2018 and 2017 , respectively, and $1.6 million and $1.5 million for the six months ended June 30, 2018 and 2017 , respectively.

Underwriting & Workflow Solutions. Our UWS segment combines property information, mortgage information and consumer information to provide comprehensive mortgage origination and monitoring solutions, including, underwriting-related solutions and data-enabled valuations and appraisals. We have also developed proprietary technology and software

24



platforms to access, automate or track this information and assist our clients with vetting and onboarding prospects, meeting compliance regulations and understanding, diagnosing and monitoring property values. Our solutions include property tax solutions, valuation solutions, credit solutions and flood services in North America. The segment’s primary clients are large, national mortgage lenders and servicers, but we also serve regional mortgage lenders and brokers, credit unions, commercial banks, fixed-income investors, government agencies and property and casualty insurance companies.

The operating results of our UWS segment included intercompany revenues of $0.8 million and $0.7 million for the three months ended June 30, 2018 and 2017 , respectively, and $1.6 million and $1.5 million for the six months ended June 30, 2018 and 2017 , respectively. The segment also included intercompany expenses of $1.7 million and $1.6 million for the three months ended June 30, 2018 and 2017 , respectively, and $3.2 million and $3.0 million for the six months ended June 30, 2018 and 2017 , respectively.

We also separately report on our corporate and eliminations. Corporate consists primarily of corporate personnel and other expenses associated with our corporate functions and facilities, investment gains and losses, equity in earnings/(losses) of affiliates, net of tax, and interest expense.

Selected financial information by reportable segment is as follows:



25



(in thousands)
 
 
 
 
 
 
 
 
 
 
 
 
For the Three Months Ended June 30, 2018
 
Operating Revenues
 
Depreciation and Amortization
 
Operating Income/(Loss)
 
Equity in Earnings/(Losses) of Affiliates, Net of Tax
 
Net Income/(Loss) From Continuing Operations
 
Capital Expenditures
PIRM
 
$
182,655

 
$
25,512

 
$
28,974

 
$
3,740

 
$
32,295

 
$
13,917

UWS
 
308,226

 
16,483

 
85,897

 
(10
)
 
85,868

 
2,386

Corporate
 

 
5,401

 
(25,234
)
 
(893
)
 
(59,631
)
 
4,180

Eliminations
 
(2,480
)
 

 

 

 

 

Consolidated (excluding discontinued operations)
 
$
488,401

 
$
47,396

 
$
89,637

 
$
2,837

 
$
58,532

 
$
20,483

 
 
 
 
 
 
 
 
 
 
 
 
 
For the Three Months Ended June 30, 2017
 
 

 
 

 
 
 
 
 
 

 
 

PIRM
 
$
176,311

 
$
24,132

 
$
32,099

 
$
(166
)
 
$
31,470

 
$
14,812

UWS
 
300,031

 
13,605

 
66,596

 
(174
)
 
60,470

 
2,413

Corporate
 

 
5,134

 
(20,302
)
 
60

 
(50,758
)
 
3,102

Eliminations
 
(2,364
)
 

 

 

 

 

Consolidated (excluding discontinued operations)
 
$
473,978

 
$
42,871

 
$
78,393

 
$
(280
)
 
$
41,182

 
$
20,327


 


 


 


 


 


 


For the Six Months Ended June 30, 2018
 
 

 
 

 


 


 
 

 
 

PIRM
 
$
356,422

 
$
51,247

 
$
49,752

 
$
4,011

 
$
52,966

 
$
27,123

UWS
 
581,645

 
31,447

 
133,950

 
8

 
133,622

 
4,699

Corporate
 

 
10,842

 
(49,646
)
 
(949
)
 
(99,694
)
 
8,145

Eliminations
 
(4,766
)
 

 

 

 

 

Consolidated (excluding discontinued operations)
 
$
933,301

 
$
93,536

 
$
134,056

 
$
3,070

 
$
86,894

 
$
39,967


 


 


 


 


 


 


For the Six Months Ended June 30, 2017
 
 

 
 

 


 


 
 

 
 

PIRM
 
$
342,067

 
$
48,992

 
$
47,671

 
$
(459
)
 
$
46,231

 
$
27,600

UWS
 
576,222

 
27,408

 
103,849

 
(967
)
 
96,664

 
3,837

Corporate
 

 
9,943

 
(40,562
)
 
422

 
(89,004
)
 
6,002

Eliminations
 
(4,460
)
 

 

 

 

 

Consolidated (excluding discontinued operations)
 
$
913,829

 
$
86,343

 
$
110,958

 
$
(1,004
)
 
$
53,891

 
$
37,439


(in thousands)
 
As of
 
As of
Assets
 
June 30, 2018
 
December 31, 2017
PIRM
 
$
1,900,141

 
$
1,911,222

UWS
 
2,260,370

 
2,151,092

Corporate
 
5,751,261

 
5,628,824

Eliminations
 
(5,755,445
)
 
(5,614,108
)
Consolidated (excluding discontinued operations)
 
$
4,156,327

 
$
4,077,030


26



Item 2.  Management’s Discussion and Analysis of Financial Condition and Results of Operations.

CAUTIONARY NOTE REGARDING FORWARD-LOOKING STATEMENTS
 
This Quarterly Report on Form 10-Q and certain information incorporated herein by reference contain forward-looking statements within the “safe harbor” provisions of the Private Securities Litigation Reform Act of 1995. All statements included or incorporated by reference in this Quarterly Report, other than statements that are purely historical, are forward-looking statements. Words such as “anticipate,” “expect,” “intend,” “plan,” “believe,” “seek,” “estimate,” “will,” “should,” “would,” “could,” “may,” and similar expressions also identify forward-looking statements. The forward-looking statements include, without limitation, statements regarding our future operations, financial condition and prospects,   operating results, revenues and earnings liquidity, our estimated income tax rate, unrecognized tax positions, amortization expenses, impact of recent accounting pronouncements, our cost management program, our acquisition strategy and our growth plans, expectations regarding our recent acquisitions, share repurchases, the level of aggregate U.S. mortgage originations and the reasonableness of the carrying value related to specific financial assets and liabilities.

Our expectations, beliefs, objectives, intentions and strategies regarding future results are not guarantees of future performance and are subject to risks and uncertainties that could cause actual results to differ materially from results contemplated by our forward-looking statements. These risks and uncertainties include, but are not limited to:

compromises in the security or stability of our data and systems, including from cyber-based attacks, the unauthorized transmission of confidential information or systems interruptions;
limitations on access to or increase in prices for data from external sources, including government and public record sources;
changes in applicable government legislation, regulations and the level of regulatory scrutiny affecting our clients or us, including with respect to consumer financial services and the use of public records and consumer data;
our ability to protect proprietary technology rights;
difficult or uncertain conditions in the mortgage and consumer lending industries and the economy generally;
our ability to realize the anticipated benefits of certain acquisitions and the timing thereof;
intense competition in the market against third parties and the in-house capabilities of our clients;
risks related to the outsourcing of services and international operations;
the level of our indebtedness, our ability to service our indebtedness and the restrictions in our various debt agreements;
our ability to attract and retain qualified management;
impairments in our goodwill or other intangible assets; and
our cost-reduction program and growth strategies, and our ability to effectively and efficiently implement them; and
the remaining tax sharing arrangements and other obligations associated with the spin-off of First American Financial Corporation.

We urge you to carefully consider these risks and uncertainties and review the additional disclosures we make concerning risks and uncertainties that may materially affect the outcome of our forward-looking statements and our future business and operating results, including those made in Item 1A of Part II below, as such risk factors may be amended, supplemented or superseded from time to time by other reports we file with the Securities and Exchange Commission. We assume no obligation to update any forward-looking statements, whether as a result of new information, future events, or otherwise, except as required by applicable law. You are cautioned not to place undue reliance on forward-looking statements, which speak only as of the date of the filing of this Quarterly Report on Form 10-Q.


27



Business Overview

We are a leading global property information, analytics and data-enabled services provider operating in North America, Western Europe and Asia Pacific. Our combined data from public, contributory and proprietary sources provides detailed coverage of property, mortgages and other encumbrances, property risk and replacement cost, consumer credit, tenancy, location, hazard risk and related performance information. We have more than one million user who rely on our data and predictive decision analytics to reduce risk, enhance transparency and improve the performance of their businesses.

We offer our clients a comprehensive national database covering real property and mortgage information, judgments and liens, building and replacement costs, parcel and geospatial data, criminal background records, eviction information, non-prime lending records, credit information, and tax information, among other data types. Our databases include over 900 million historical property transactions, over 100 million mortgage applications and property-specific data covering approximately 99% of U.S. residential properties, as well as commercial locations, totaling nearly 150 million records. We are also the industry's first parcel-based geocoder and have developed a proprietary parcel database covering more than 145 million parcels across the U.S. We believe the quality of the data we offer is distinguished by our broad range of data sources and our expertise in aggregating, organizing, normalizing, processing and delivering data to our clients.

With our data as a foundation, we have built strong analytics capabilities and a variety of value-added business services to meet our clients’ needs for property tax processing, property valuation, mortgage and automotive credit reporting, tenancy screening, hazard risk, property risk and replacement cost, flood plain location determination and other geospatial data analytics and related services.

Reportable Segments

We have organized our reportable segments into the following two segments: Property Intelligence & Risk Management Solutions ("PIRM") and Underwriting & Workflow Solutions ("UWS").

Our PIRM segment combines property information, mortgage information, and consumer information to deliver unique housing market and property-level insights, predictive analytics and risk management capabilities. We have also developed proprietary technology and software platforms to access, automate or track this information and assist our clients with decision-making and compliance tools in the real estate industry, insurance industry and the single and multifamily industry. We deliver this information directly to our clients in a standard format over the web, through hosted software platforms or in bulk data form. Our solutions include property insights and insurance & spatial solutions in North America, Western Europe and Asia Pacific.

Our UWS segment combines property information, mortgage information and consumer information to provide comprehensive mortgage origination and monitoring solutions, including underwriting-related solutions and data-enabled valuations and appraisals. We have also developed proprietary technology and software platforms to access, automate or track this information and assist our clients with vetting and on-boarding prospects, meeting compliance regulations and understanding, diagnosing and monitoring property values. Our solutions include property tax solutions, valuation solutions, credit solutions and flood services in North America.

RESULTS OF OPERATIONS

Overview of Business Environment and Company Developments

Business Environment

The volume of U.S. mortgage loan originations serves as a key market driver for more than half of our business. We believe the volume of real estate and mortgage transactions is primarily affected by real estate prices, the availability of funds for mortgage loans, mortgage interest rates, employment levels and the overall state of the U.S. economy. We believe mortgage unit volumes decreased by more than 10% in the second quarter of 2018 relative to the same period in 2017 , primarily due to significantly lower mortgage refinance volumes resulting from rising interest rates. Overall, we expect full-year 2018 mortgage unit volumes to be approximately 10% to 15% lower relative to 2017 levels mostly due to rising interest rates and lower expected refinance activity.

We generate the majority of our revenues from clients with operations in the U.S. residential real estate, mortgage origination and mortgage servicing markets. Approximately 32% and 41% of our operating revenues for the three months ended June 30, 2018 and 2017 , respectively, and 33% and 41% of our operating revenues for the six months ended June 30,

28



2018 and 2017 , respectively, were generated from our top ten clients, who consist of the largest U.S. mortgage originators and servicers. None of our clients accounted for greater than 10% of our operating revenues for the three months ended June 30, 2018 and two of our clients accounted for approximately 14% and 10% of our operating revenues for the three months ended June 30, 2017 . None of our clients accounted for greater than 10% of our operating revenues for the six months ended June 30, 2018 , and two of our clients accounted for approximately 13% and 10% of our operating revenues for the six months ended June 30, 2017 . Both of our PIRM and UWS segments reported revenue from these customers.

Acquisitions
    
In April 2018, we completed the acquisition of a la mode technologies, LLC ("a la mode") for cash of approximately $120.0 million . We funded the transaction with cash on hand and available capacity on our revolving credit facility. The acquisition is included in the UWS reporting segment. See Note 12 - Acquisitions for further discussion.

In February 2018, we completed the acquisition of eTech Solutions Limited ("eTech") for cash of approximately £15.0 million , or approximately $21.0 million . The acquisition is included in the PIRM reporting segment. See Note 12 - Acquisitions for further discussion.

Productivity and Cost Management

In line with our on-going commitment to operational excellence and margin expansion, we are targeting a cost reduction of at least $15 million in 2018. Savings are expected to be realized through the reduction of operating costs, selling, general and administrative costs, outsourcing certain business process functions, consolidation of facilities and other operational improvements.

Unless otherwise indicated, the Management’s Discussion and Analysis of Financial Condition and Results of Operations in this Quarterly Report on Form 10-Q relate solely to the discussion of our continuing operations.


29



Consolidated Results of Operations
 
Three Months Ended June 30, 2018 Compared to Three Months Ended June 30, 2017

Operating Revenues

Our consolidated operating revenues were $488.4 million for the three months ended June 30, 2018 , an increase of $14.4 million , or 3.0% , when compared to 2017 , and consisted of the following:

(in thousands, except percentages)
2018
 
2017
 
$ Change
 
% Change
PIRM
$
182,655

 
$
176,311

 
$
6,344

 
3.6
%
UWS
308,226

 
300,031

 
8,195

 
2.7

Corporate and eliminations
(2,480
)
 
(2,364
)
 
(116
)
 
4.9

Operating revenues
$
488,401

 
$
473,978

 
$
14,423

 
3.0
%

Our PIRM segment revenues increased by $6.3 million , or 3.6% , when compared to 2017 . The increase is primarily due to acquisition activity which contributed $7.3 million of additional revenues in 2018 ; partially offset by lower other revenues of $1.0 million.

Our UWS segment revenues increased by $8.2 million , or 2.7% , when compared to 2017 . Excluding acquisition activity of $14.6 million, the decrease of $6.4 million was primarily due to lower valuation solutions operating revenue of $24.0 million, lower credit solutions operating revenue of $1.6 million, lower flood data services operating revenue of $1.4 million, and lower other revenue of $1.0 million, mainly driven by lower mortgage market unit volumes and the impact of planned vendor diversification from key appraisal management clients. The decrease was offset by higher property tax solutions operating revenue of $21.6 million primarily driven by the benefit of accelerated revenue recognition resulting from the amendment of a long-term contract.

Our corporate and eliminations were comprised of intercompany revenue eliminations between our operating segments.

Cost of Services

Our consolidated cost of services was $239.3 million for the three months ended June 30, 2018 , a decrease of $9.8 million , or 3.9% , when compared to 2017 . Acquisition activity contributed $6.9 million of additional expense in 2018 . Excluding acquisition activity, the decrease of $16.7 million was primarily due to favorable revenue mix and the benefits from ongoing operational efficiency programs.

Selling, General and Administrative Expense

Our consolidated selling, general and administrative expenses were $112.0 million for the three months ended June 30, 2018 , an increase of $8.5 million , or 8.2% , when compared to 2017 . Acquisition activity contributed $10.9 million of additional expense in 2018 . Excluding acquisition activity, the decrease of $2.4 million was primarily related to our ongoing operational efficiency programs.

Depreciation and Amortization

Our consolidated depreciation and amortization expense was $47.4 million for the three months ended June 30, 2018 , an increase of $4.5 million , or 10.6% , when compared to 2017 , primarily due to acquisitions.

30



Operating Income

Our consolidated operating income was $89.6 million for the three months ended June 30, 2018 , an increase of $11.2 million , or 14.3% , when compared to 2017 , and consisted of the following:

(in thousands, except percentages)
 
2018
 
2017
 
$ Change
 
% Change
PIRM
 
$
28,974

 
$
32,099

 
$
(3,125
)
 
(9.7
)%
UWS
 
85,897

 
66,596

 
19,301

 
29.0

Corporate and eliminations
 
(25,234
)
 
(20,302
)
 
(4,932
)
 
24.3

Operating income
 
$
89,637

 
$
78,393

 
$
11,244

 
14.3
 %

Our PIRM segment operating income decreased by $3.1 million , or 9.7% , when compared to 2017 . Acquisition activity lowered operating income by $1.8 million in 2018 primarily due to the amortization of acquisition-related intangible assets. Excluding acquisition activity, operating income decreased by $1.3 million, margins decreased by 65 basis points, primarily due lower other revenues.

Our UWS segment operating income increased by $19.3 million , or 29.0% , when compared to 2017 . Excluding acquisition activity of $1.5 million, operating income increased by $17.8 million, margins increased by 654 basis points, primarily related to the benefit of accelerated revenue recognition resulting from the amendment of a long-term contract in our property tax solutions operations, partially offset by lower mortgage market unit volumes and the impact of planned vendor diversification from key appraisal management clients.

Corporate and eliminations had an unfavorable variance of $4.9 million primarily due to higher investments related to ongoing operating efficiency programs.

Total Interest Expense, net

Our consolidated total interest expense, net was $18.8 million for the three months ended June 30, 2018 , an increase of $4.8 million , or 34.6% , when compared to 2017 . The increase was primarily due to a higher average outstanding balance and higher interest rates.

Gain/(Loss) on Investments and Other, net

Our consolidated gain on gain/(loss) investments and other, net was $2.1 million for the three months ended June 30, 2018 , a favorable variance of $6.5 million , or 148.9% , when compared to 2017 . The favorable variance was primarily due to a prior year loss recorded on the final settlement of a pension plan along with a gain in the current year on our contingent consideration agreements, which are adjusted for fair-value quarterly.

Provision for Income Taxes

Our consolidated provision for income taxes from continuing operations before equity in earnings/(losses) of affiliates and income taxes was $17.3 million and $18.6 million for the three months ended June 30, 2018 and 2017 , respectively. The effective tax rate was 23.7% and 31.0% for the three months ended June 30, 2018 and 2017 , respectively, and the decrease was primarily due to changes in the U.S. corporate income tax rate from the enactment of the Tax Cuts and Jobs Act ("TCJA").

Equity in Earnings/(Losses) of Affiliates, net of tax

Our consolidated equity in earnings of affiliates, net of tax was $2.8 million for the three months ended June 30, 2018 , a favorable variance of $3.1 million , or 1,113.2% , when compared to 2017 . We have equity interests in various affiliates which had gains in the current period compared to prior year losses causing the favorable variance.



31



Six Months Ended June 30, 2018 Compared to Six Months Ended June 30, 2017

Operating Revenues

Our consolidated operating revenues were $0.9 billion for the six months ended June 30, 2018 , an increase of $19.5 million , or 2.1% , when compared to 2017 , and consisted of the following:

(in thousands, except percentages)
2018
 
2017
 
$ Change
 
% Change
PIRM
$
356,422

 
$
342,067

 
$
14,355

 
4.2
%
UWS
581,645

 
576,222

 
5,423

 
0.9

Corporate and eliminations
(4,766
)
 
(4,460
)
 
(306
)
 
6.9

Operating revenues
$
933,301

 
$
913,829

 
$
19,472

 
2.1
%

Our PIRM segment revenues increased by $14.4 million , or 4.2% , when compared to 2017 . Excluding acquisition activity of $13.4 million, the increase of $1.0 million was primarily due to higher property insights operating revenues of $2.8 million, which benefited from improved product mix and market share gains; partially offset by other revenues.

Our UWS segment revenues increased by $5.4 million , or 0.9% , when compared to 2017 . Excluding acquisition activity of $22.7 million, the decrease of $17.3 million was primarily due to lower valuation solutions operating revenue of $36.0 million and lower flood data services revenue of $2.7 million, mainly driven by lower mortgage market unit volumes and the impact of planned vendor diversification from key appraisal management clients. The decrease was offset by higher property tax solutions operating revenue of $19.7 million primarily driven by the benefit of accelerated revenue recognition resulting from the amendment of a long-term contract. Credit solutions operating revenue also increased by $1.7 million due to improved product mix.
    
Our corporate and eliminations were comprised of intercompany revenue eliminations between our operating segments.

Cost of Services

Our consolidated cost of services was $478.7 million for the six months ended June 30, 2018 , a decrease of $22.4 million , or 4.5% , when compared to 2017 . Acquisition activity contributed $12.4 million of additional expense in 2018 . Excluding acquisition activity, the decrease of $34.8 million was primarily due to favorable revenue mix and benefits from ongoing operational efficiency programs.

Selling, General and Administrative Expense

Our consolidated selling, general and administrative expenses were $227.0 million for the six months ended June 30, 2018 , an increase of $11.6 million , or 5.4% , when compared to 2017 . Acquisition activity contributed $17.4 million of additional expense in 2018 . Excluding acquisition activity, the decrease of $5.8 million was primarily related to our ongoing operational efficiency programs.

Depreciation and Amortization

Our consolidated depreciation and amortization expense was $93.5 million for the six months ended June 30, 2018 , an increase of $7.2 million , or 8.3% , when compared to 2017 , primarily due to acquisitions.



32



Operating Income

Our consolidated operating income was $134.1 million for the six months ended June 30, 2018 , an increase of $23.1 million , or 20.8% , when compared to 2017 , and consisted of the following:

(in thousands, except percentages)
 
2018
 
2017
 
$ Change
 
% Change
PIRM
 
$
49,752

 
$
47,671

 
$
2,081

 
4.4
%
UWS
 
133,950

 
103,849

 
30,101

 
29.0

Corporate and eliminations
 
(49,646
)
 
(40,562
)
 
(9,084
)
 
22.4

Operating income
 
$
134,056

 
$
110,958

 
$
23,098

 
20.8
%

Our PIRM segment operating income increased by $2.1 million , or 4.4% , when compared to 2017 . Excluding acquisition activity of $2.9 million, which lowered operating income in 2018 primarily due to the amortization of acquisition-related intangible assets. Excluding acquisition activity, operating income increased by $5.0 million, margins increased by 142 basis points primarily due to improvements in product mix, market share gains and the impact of ongoing operational efficiency programs. The increase was partially offset by lower other revenues.

Our UWS segment operating income increased by $30.1 million , or 29.0% , when compared to 2017 . Excluding acquisition activity of $2.3 million, operating income increased by $27.8 million, margins increased by 554 basis points, primarily related to the benefit of accelerated revenue recognition resulting from the amendment of a long-term contract in our property tax solutions operations partially offset by lower mortgage market unit volumes and the impact of planned vendor diversification from key appraisal management clients.

Corporate and eliminations had an unfavorable variance of $9.1 million , or 22.4% , primarily due to higher investments related to ongoing operating efficiency programs.

Total Interest Expense, net

Our consolidated total interest expense, net was $35.9 million for the six months ended June 30, 2018 , an increase of $8.2 million , or 29.5% , when compared to 2017 . The increase was primarily due to a higher average outstanding balance and higher interest rates.

Gain/(Loss) on Investments and Other, net

Our consolidated gain on gain/loss on investments and other, net was $2.3 million for the six months ended June 30, 2018 , a favorable variance of $5.7 million , or 167.0% , when compared to 2017 . The favorable variance was primarily due to a prior year loss of $6.1 million recorded on the final settlement of a pension plan along with a gain of $1.1 million in the current year on our contingent consideration agreements, which are adjusted for fair-value quarterly. These gains were partially offset by higher realized losses on current year investments of $1.5 million.

Provision for Income Taxes

Our consolidated provision for income taxes from continuing operations before equity in earnings/(losses) of affiliates and income taxes was $16.6 million and $24.9 million for the six months ended June 30, 2018 and 2017 , respectively. The effective tax rate was 16.5% and 31.2% for the six months ended June 30, 2018 and 2017 , respectively. The decrease in the effective tax rate was primarily attributable to changes in the U.S. corporate income tax rate from the enactment of the TCJA.

Equity in Earnings/(Losses) of Affiliates, net of tax

Our consolidated equity in earnings of affiliates, net of tax was $3.1 million for the six months ended June 30, 2018 , a favorable variance of $4.1 million , or 405.8% when compared to 2017 . We have equity interests in various affiliates which had gains in the current period compared to prior year losses causing the favorable variance.


33



LIQUIDITY AND CAPITAL RESOURCES

Cash and cash equivalents as of June 30, 2018 totaled $85.0 million , a decrease of $33.8 million from December 31, 2017 . As of June 30, 2018 , our cash balances held in foreign jurisdictions totaled $53.3 million and are primarily related to our international operations. Most of the amounts held outside of the U.S. could be repatriated to the U.S. without the assessment of additional income tax other than the one-time transition tax pursuant to the TCJA. We are finalizing the calculation of the transition tax and will report this aspect of the TCJA during 2018. We plan to maintain significant cash balances outside of the U.S. for the foreseeable future.

Restricted cash of $10.8 million as of June 30, 2018 and $11.1 million as of December 31, 2017 is comprised of mutual funds, certificate of deposits that are pledged for various letters of credit/bank guarantees secured by us and escrow accounts due to acquisitions and divestitures.

Cash Flow

Operating Activities. Cash provided by operating activities reflects net income adjusted for certain non-cash items and changes in operating assets and liabilities. Total cash provided by operating activities was approximately $148.4 million and $140.1 million for the six months ended June 30, 2018 and 2017 , respectively. The increase in cash provided by operating activities was primarily due higher cash generated from higher profitability, as adjusted for non-cash activities, partially offset by unfavorable changes in working capital items.

Investing Activities. Total cash used in investing activities was approximately $179.8 million and $107.1 million during the six months ended June 30, 2018 and 2017 , respectively. The increase in investing activities was primarily related to net cash paid for the acquisitions of eTech and a la mode of $141.1 million . Further, for the six months ended June 30, 2018 and 2017 , we had investments in property and equipment of $21.4 million and $20.2 million , respectively, as well as investments in capitalized data and other intangible assets of $18.6 million and $17.2 million , respectively. The increases were partially offset by higher proceeds from investments of $1.0 million in the current year along with our acquisition of a 45% interest in Mercury Network, LLC for $70.0 million in June 2017.

Financing Activities. Total cash used in financing activities was approximately $6.2 million for the six months ended June 30, 2018 , which was primarily comprised of repayment of long-term debt of $68.9 million and share repurchases of $63.3 million , partially offset by share-based compensation-related transactions of $5.9 million and proceeds of long-term debt of $120.1 million . Total cash used in financing activities was approximately $15.1 million for the six months ended June 30, 2017 , which was primarily comprised of share repurchases of $41.0 million , repayment of long-term debt of $35.2 million and share-based compensation-related transactions of $8.9 million , partially offset by proceeds from long-term debt of $70.0 million .

Financing and Financing Capacity

Total debt outstanding, gross, was $1.8 billion for both periods as of June 30, 2018 and December 31, 2017 , respectively. Our significant debt instruments and borrowing capacity are described below.

Credit Agreement

In August 2017, we amended and restated our credit agreement (“Credit Agreement”) with Bank of America, N.A. as the administrative agent, and other financial institutions. The Credit Agreement provides for a $1.8 billion five -year term loan A facility (“Term Facility”), and a $700.0 million five-year revolving credit facility ("Revolving Facility") The Term Facility matures and the Revolving Facility expires in August 2022. The Credit Agreement also provides for the ability to increase the Term Facility and/or Revolving Facility by up to $100.0 million in the aggregate; however, the lenders are not obligated to do so. As of June 30, 2018 , we had borrowing capacity under the Revolving Facility of $580.0 million and were in compliance with the financial and restrictive covenants of the Credit Agreement. See Note 5 - Long-Term Debt for further discussion.

Interest Rate Swaps
 
We have entered into amortizing interest rate swaps ("Swaps") in order to convert a portion of our interest rate exposure on the Term Facility floating rate borrowings from variable to fixed. Under the Swaps, we agree to exchange floating rate for fixed rate interest payments periodically over the life of the agreement. The floating rates in our Swaps are based on the one month London interbank offering rate. The notional balances, terms, and maturities of our Swaps are currently designed to have at least 50% of our debt as fixed rate.

34




As of June 30, 2018 , we have four Swaps with a combined remaining notional balance of $1.3 billion , a weighted average fixed interest rate of 1.76% (rates range from 1.03% to 2.61% ), and scheduled terminations through August 2022 . As previously indicated, notional balances under our Swaps are currently scheduled to increase and decrease over their contract lengths based on our expectations of variable debt levels. We currently have scheduled notional amounts of between $1.3 billion and $1.1 billion through March 2021 with $585.0 million thereafter until August 2022 .

Liquidity and Capital Strategy

We expect that cash flow from operations and current cash balances, together with available borrowings under our Revolving Facility, will be sufficient to meet operating requirements through the next twelve months. Cash available from operations, however, could be affected by any general economic downturn or any decline or adverse changes in our business such as a loss of clients, competitive pressures or other significant change in business environment.

We strive to pursue a balanced approach to capital allocation and will consider the repurchase of common shares, the retirement of outstanding debt, investments and the pursuit of strategic acquisitions on an opportunistic basis.

During the six months ended June 30, 2018 , we repurchased 1.3 million shares of our common stock for $63.3 million including commission costs.

Availability of Additional Capital

Our access to additional capital fluctuates as market conditions change. There may be times when the private capital markets and the public debt or equity markets lack sufficient liquidity or when our securities cannot be sold at attractive prices, in which case we would not be able to access capital from these sources. Based on current market conditions and our financial condition (including our ability to satisfy the conditions contained in our debt instruments that are required to be satisfied to permit us to incur additional indebtedness), we believe that we have the ability to effectively access these liquidity sources for new borrowings. However, a weakening of our financial condition, including a significant decrease in our profitability or cash flows or a material increase in our leverage, could adversely affect our ability to access these markets and/or increase our cost of borrowings.

Critical Accounting Policies and Estimates

For additional information with respect to our critical accounting policies, which are those that could have the most significant effect on our reported results and require subjective or complex judgments by management, see Item 7, “ Management's Discussion and Analysis of Financial Condition and Results of Operations ,” of our Annual Report on Form 10-K for the year ended December 31, 2017 and Note 1 – Basis for Condensed Consolidated Financial Statements , which is incorporated by reference in response to this item, for updates on our policies over revenue recognition.

Item 3.  Quantitative and Qualitative Disclosures about Market Risk.

Our primary exposure to market risk relates to interest-rate risk associated with certain financial instruments. We monitor our risk associated with fluctuations in interest rates and currently use derivative financial instruments to hedge some of these risks.

We have entered into Swaps in order to convert a portion of our interest rate exposure on the Term Facility floating rate borrowings from variable to fixed. Under the Swaps, we agree to exchange floating rate for fixed rate interest payments periodically over the life of the agreement. The notional balances, terms and maturities of our Swaps are currently designed to have at least 50% of our debt as fixed rate. As of June 30, 2018 , we had approximately $1.8 billion in gross long-term debt outstanding, predominately all of which was variable-interest-rate debt. As of June 30, 2018 , the remaining notional balance of the Swaps was $1.3 billion . A hypothetical 1% increase or decrease in interest rates could result in an approximately $1.3 million change to interest expense on a quarterly basis.

Although we are subject to foreign currency exchange rate risk as a result of our operations in certain foreign countries, the foreign exchange exposure related to these operations, in the aggregate, is not material to our financial condition or results of operations.


35



Item 4.  Controls and Procedures.

Evaluation of Disclosure Controls and Procedures

Our principal executive officer and principal financial officer have concluded that, as of the end of the quarterly period covered by this Quarterly Report on Form 10-Q, our disclosure controls and procedures, as defined in Rule 13a-15(e) of the Securities Exchange Act of 1934, as amended, were effective, based on the evaluation of these controls and procedures required by Rule 13a-15(b).

Changes in Internal Control over Financial Reporting

Beginning January 1, 2018, we implemented the updated guidance on revenue recognition. In connection with the adoption of this standard, we implemented changes to our disclosure controls and procedures related to revenue recognition and the control activities within them. These included the development of new policies based on the five-step model provided in the new revenue standard, new training, ongoing contract review requirements and gathering of information provided for disclosures.

There were no other changes in our internal control over financial reporting during the six months ended June 30, 2018 that have materially affected, or are reasonably likely to materially affect, our internal control over financial reporting.

PART II: OTHER INFORMATION

Item  1.  Legal Proceedings.

For a description of our legal proceedings, see Note 1 - Basis for Condensed Consolidated Financial Statements and Note 8 – Litigation and Regulatory Contingencies of our condensed consolidated financial statements, which is incorporated by reference in response to this item.

Item  1A.  Risk Factors.

We have described in our Annual Report on Form 10-K for the fiscal year ended  December 31, 2017 , the primary risks related to our business, and we may periodically update those risks for material developments. Those risks are not the only ones we face, but do represent those risks that we believe are material to us. Our business is also subject to the risks that affect many other companies, such as general economic conditions, geopolitical events and employment relations. Additional risks and uncertainties not presently known to us or that we currently deem immaterial may also harm our business. Please read the cautionary notice regarding forward-looking statements under the heading “Management's Discussion and Analysis of Financial Condition and Results of Operations.” You should carefully consider the risks and uncertainties our business faces.
There have been no material changes to the Risk Factors described in our Annual Report on Form 10-K for the fiscal year ended  December 31, 2017 .

Item 2.  Unregistered Sales of Equity Securities and Use of Proceeds.

Unregistered Sales of Equity Securities

During the quarter ended June 30, 2018 , we did not issue any unregistered shares of our common stock.

Purchases of Equity Securities by the Issuer and Affiliated Purchasers

In October 2016, the Board of Directors canceled all prior repurchase authorizations and established a new share repurchase authorization of up to $500.0 million. As of June 30, 2018 , we have $147.2 million in value of shares (inclusive of commissions and fees) available to be repurchased under the plan. The stock repurchase authorization has no expiration date and repurchases may be made in the open market, in privately negotiated transactions or pursuant to a Rule 10b5-1 plan.

Under our Credit Agreement, our stock repurchase capacity is restricted to $150.0 million per fiscal year, with the ability to undertake an additional amount of repurchases in such fiscal year provided that, on a pro forma basis after giving effect to the stock repurchase, our total leverage ratio does not exceed 3.5 to 1.0. While we continue to preserve the capacity to execute share repurchases under our existing share repurchase authorization, going forward we will strive to pursue a balanced

36



approach to capital allocation and will consider the repurchase of shares of our common shares, the retirement of outstanding debt and the pursuit of strategic acquisitions on an opportunistic basis.

The following table summarizes our repurchase activity under our Board-approved stock repurchase plan for the quarter ended June 30, 2018 :

Issuer Purchases of Equity Securities
 
 
 
 
 
 
Period
Total Number of Shares Purchased
 
Average Price Paid per Share (1)
 
Total Number of Shares Purchased as Part of Publicly Announced Plans or Programs
 
Approximate Dollar Value of Shares that May Yet be Purchased Under the Plans or Programs
April 1 to April 30, 2018

 
$

 

 
$
192,061,717

May 1 to May 31, 2018
852,789

 
$
51.38

 
852,789

 
$
148,246,674

June 1 to June 30, 2018
19,000

 
$
54.11

 
19,000

 
$
147,218,620

Total
871,789

 
$
51.44

 
871,789

 
 
 
 
 
 
 
 
 
 
(1) Calculated inclusive of commissions.

Item 3.  Defaults upon Senior Securities. None.

Item 4.  Mine Safety Disclosures. Not applicable.

Item  5.  Other Information.

In May 2018, our stockholders approved the Company’s 2018 Performance Incentive Plan (the “2018 Plan”) to promote our success by providing an additional means to attract, motivate, retain and reward selected employees and other eligible persons through the grant of awards. Equity-based awards are also intended to further align the interests of award recipients and our stockholders.

The maximum number of shares of our common stock that may be issued or transferred pursuant to awards under the 2018 Plan equals the sum of the following: (a) 3,300,000 shares, plus (b) 6,271,440 shares, the number of shares available for new award grants under the Company’s 2011 Performance Incentive Plan, as amended (the “2011 Plan”) immediately prior to the 2018 Annual Meeting, (c) 60,882 shares, the number of shares as of May 10, 2018 that were subject to awards granted under the 2011 Plan that expired or were cancelled or terminated after the 2018 Annual Meeting (with each share subject to restricted stock and restricted stock unit awards being counted as two shares), and (d) 5,506,762 shares, the number of shares as of May 10, 2018 that were subject to awards that remain outstanding under the 2011 Plan but may become issuable pursuant to the 2018 Plan in the future (with outstanding performance awards being counted at maximum performance level and each share subject to restricted stock and restricted stock unit awards being counted as two shares).

The Board or one or more committees appointed by the Board administers the 2018 Plan. The Board has delegated general administrative authority for the 2018 Plan to its Compensation Committee. The Board or a committee thereof (within its delegated authority) may delegate different levels of authority to different committees or persons with administrative and grant authority under the 2018 Plan. The administrator of the 2018 Plan has broad authority under the 2018 Plan to, among other things, select participants and determine the type(s) of award(s) that they are to receive, and determine the number of shares that are to be subject to awards and the terms and conditions of awards, including the price (if any) to be paid for the shares or the award.

Persons eligible to receive awards under the 2018 Plan include our officers, employees, directors, and certain consultants and advisors to the Company or any of its subsidiaries.

The types of awards that may be granted under the 2018 Plan include stock options, stock appreciation rights, restricted stock, stock bonuses, stock units and other forms of awards granted or denominated in ours common stock or units of our common stock, as well as certain cash bonus awards.


37



The foregoing description is qualified in its entirety by reference to the 2018 Plan, a copy of which is filed as Exhibit 10.1 to this report and incorporated by reference herein.

Item 6.  Exhibits.

See Exhibit Index.

38




SIGNATURES

Pursuant to the requirements of the Securities Exchange Act of 1934, as amended, the registrant has duly caused this report to be signed on its behalf by the undersigned thereunto duly authorized.
 
 
 
CoreLogic, Inc.
 
 
(Registrant)
 
 
 
 
 
By: /s/   Frank D. Martell
 
 
Frank D. Martell
 
 
President and Chief Executive Officer
 
 
(Principal Executive Officer)
 
 
 
 
 
By: /s/  James L. Balas
 
 
James L. Balas
 
 
Chief Financial Officer
 
 
(Principal Financial Officer)
 
 
 
 
 
By: /s/  John K. Stumpf
 
 
John K. Stumpf
 
 
Controller
 
 
(Principal Accounting Officer)
Date:
July 26, 2018
 


39



EXHIBIT INDEX

Exhibit
Number
 
Description
 
Agreement and Plan of Merger, dated December 17, 2015, by and among CoreLogic Solutions, LLC, CoreLogic Acquisition Co., Inc., FNC Holding Company, Inc. and, solely in his capacity as Shareholder Representative, Dennis S. Tosh, Jr. (incorporated by reference to Exhibit 2.2 to the Company's Annual Report on Form 10-K as filed with the SEC on February 26, 2016)^+
 
 
 
 
First Amendment to Agreement and Plan of Merger, dated as of April 7, 2016, by and among CoreLogic Solutions, LLC, CoreLogic Acquisition Co., Inc., FNC Holding Company, Inc. and Dennis S. Tosh, Jr. (incorporated by reference to Exhibit 2.1 to the Company's Current Report on Form 8-K as filed with the SEC on April 8, 2016)^
 
 
 
 
Amended and Restated Certificate of Incorporation of CoreLogic, Inc., dated May 28, 2010 (incorporated by reference to Exhibit 3.1 to the Company’s Current Report on Form 8-K as filed with the SEC on June 1, 2010)
 
 
 
 
Amended and Restated Bylaws of CoreLogic, Inc. (incorporated by reference to the Company’s Current Report on Form 8-K as filed with the SEC on March 5, 2014)
 
 
 
 
CoreLogic, Inc.'s 2018 Performance Incentive Plan (incorporated by reference to Exhibit 10.1 to the Company's Current Report on Form 8-K as filed with the SEC on May 4, 2018)
 
 
 
 
Form of Notice of Restricted Stock Unit Grant and Form of Restricted Stock Unit Award Agreement (Employee) under the CoreLogic, Inc. 2018 Performance Incentive Plan ü
 
 
 
 
Form of Notice of Restricted Stock Unit Grant and Form of Restricted Stock Unit Award Agreement (NEO) under the CoreLogic, Inc. 2018 Performance Incentive Plan ü
 
 
 
 
Form of Notice of Restricted Stock Unit Grant and Form of Restricted Stock Unit Award Agreement (UK Employees) under the CoreLogic, Inc. 2018 Performance Incentive Plan ü
 
 
 
 
Form of Notice of Performance-Based Restricted Stock Unit Grant and Form of Performance-Based Restricted Stock Unit Award Agreement under the CoreLogic, Inc. 2018 Performance Incentive Plan ü
 
 
 
 
Amendment No. 5 dated May 15, 2018 to the Master Services Agreement and Supplement A between CoreLogic Solutions, LLC and NTT Data Services, LLC (formerly Dell Marketing L.P.) ± ü
 
 
 
 
Certification by Chief Executive Officer Pursuant to Rule 13a-14(a) under the Securities Exchange Act of 1934 ü
 
 
 
 
Certification by Chief Financial Officer Pursuant to Rule 13a-14(a) under the Securities Exchange Act of 1934 ü
 
 
 
 
Certification by Chief Executive Officer Pursuant to 18 U.S.C. Section 1350 ü
 
 
 
 
Certification by Chief Financial Officer Pursuant to 18 U.S.C. Section 1350 ü
 
 
 
101
 
Extensible Business Reporting Language (XBRL) ü
 
 
 


40



 
ü
Included in this filing.
 
^
Schedules and exhibits have been omitted pursuant to Item 601(b)(2) of Regulation S-K. The Company hereby agrees to furnish supplementally copies of any of the omitted schedules and exhibits upon request by the Securities and Exchange Commission.
 
+
This agreement contains representations and warranties by us or our subsidiaries. These representations and warranties have been made solely for the benefit of the other parties to the agreement and (i) have been qualified by disclosures made to such other parties, (ii) were made only as of the date of such agreement or such other date(s) as may be specified in such agreement and are subject to more recent developments, which may not be fully reflected in our public disclosures, (iii) may reflect the allocation of risk among the parties to such agreement and (iv) may apply materiality standards different from what may be viewed as material to investors. Accordingly, these representations and warranties may not describe the actual state of affairs at the date hereof and should not be relied upon.
 
*
Indicates a management contract or compensatory plan or arrangement in which any director or named executive officer participates.
 
±
Confidential treatment has been requested with respect to portions of this exhibit pursuant to Rule 24b-2 of the Securities Exchange Act of 1934 and these confidential portions have been redacted from this exhibit. A complete copy of this exhibit, including the redacted terms, has been separately filed with the Securities and Exchange Commission.


41



Notice of Restricted Stock Unit Grant

Participant:          [Participant Name]
Corporation:         CoreLogic, Inc.
Notice:
You have been granted the following Restricted Stock Units in accordance with the terms of the Plan and the Restricted Stock Unit Award Agreement attached hereto.
Type of Award:
Restricted Stock Units
Plan:
CoreLogic, Inc. 2018 Performance Incentive Plan
Grant:             Date of Grant:   [Grant Date]
Number of Shares Underlying Bonus Restricted Stock Units:   [Number of Shares                          Granted]

Period of Restriction:
Subject to the terms of the Plan and this Agreement, the Period of Restriction applicable to the Restricted Stock Units shall commence on the Date of Grant and shall lapse on the date listed in the “Lapse Date” column below as to that portion of Shares underlying the Restricted Stock Units set forth below opposite each such date.

Lapse Date
Portion of Shares as to
Which Period of Restriction Lapses
20 th  day of Date of Grant month + 1 year
1/3
20 th  day of Date of Grant month + 2 years
1/3
20 th  day of Date of Grant month + 3 years
1/3

For purposes of this Agreement, “Period of Restriction” means the period during which the Restricted Stock Units are subject to a substantial risk of forfeiture. The date on which the Period of Restriction lapses pursuant to this paragraph is referred to herein as the “Lapse Date.”

The vesting schedule set forth above requires the Participant’s continued employment or service through each applicable Lapse Date as a condition to the lapsing of the Period of Restriction on such Lapse Date. Except as provided in Section 4 or Section 5 of this Agreement, employment or service for only a portion of the Period of Restriction prior to the Lapse Date, even if a substantial portion, will not entitle the Participant to any proportionate vesting or avoid or mitigate a termination of rights and benefits upon or following a termination of employment or services as provided in Section 4 below or under the Plan.

Rejection:
If you wish to accept this Restricted Stock Unit Award, please access Fidelity NetBenefits® at www.netbenefits.com and follow the steps outlined under the "Accept Grant" link at any time within forty-five (45) days after the Date of Grant. If you do not accept your grant via Fidelity NetBenefits® within forty-five (45) days after the Date of Grant, you will have rejected this Restricted Stock Unit Award.






Restricted Stock Unit Award Agreement
This Restricted Stock Unit Award Agreement (this “Agreement”), dated as of the Date of Grant set forth in the Notice of Restricted Stock Unit Grant attached hereto (the “Grant Notice”), is made between CoreLogic, Inc. (the “Corporation”) and the Participant set forth in the Grant Notice. The Grant Notice is included in and made part of this Agreement.
1. Definitions .
Certain capitalized terms are defined in the Grant Notice, herein or in the attached Appendix A. Capitalized terms used but not defined in the Grant Notice, herein or in the attached Appendix A shall have the meaning assigned to such terms in the Plan.
2. Grant of the Restricted Stock Units .
Subject to the provisions of this Agreement and the provisions of the Plan, the Corporation hereby grants to the Participant, pursuant to the Plan, a right to receive the number of shares of Common Stock (“Shares”) set forth in the Grant Notice (the “Restricted Stock Units”).
3. Dividend Equivalents .
Each Restricted Stock Unit shall accrue Dividend Equivalents (as defined below) with respect to dividends that would otherwise be paid on the Share underlying such Restricted Stock Unit during the period from the Grant Date to the date such Share is delivered in accordance with Section 6. As of any date in this period that the Corporation pays an ordinary cash dividend on its Common Stock, the Corporation shall credit the Participant with an additional number of Restricted Stock Units equal to (i) the per share cash dividend paid by the Corporation on its Common Stock on such date, multiplied by (ii) the total number of Restricted Stock Units subject to the award as of the related dividend payment record date (including any Dividend Equivalents previously credited hereunder), divided by (iii) the fair market value (as determined in accordance with the terms of the Plan) of a share of Common Stock on the date of payment of such dividend. Any Restricted Stock Units credited pursuant to the foregoing provisions of this Section 3 shall be subject to the same Period of Restriction, payment, delivery and other terms, conditions and restrictions as the original Restricted Stock Units to which they relate. Any such crediting of Dividend Equivalents shall be conclusively determined by the Administrator. No crediting of Restricted Stock Units shall be made pursuant to this Section 3 with respect to any Restricted Stock Units which, as of such record date, have either been delivered or terminated pursuant to the Plan or this Agreement. For purposes of this Agreement, “Dividend Equivalents” means the equivalent value (in cash or Shares) of dividends that would otherwise be paid on the Shares subject to the Restricted Stock Units but that have not been issued or delivered.
4. Period of Restriction; Termination .
The Period of Restriction with respect to the Restricted Stock Units shall be as set forth in the Grant Notice. Subject to the terms of the Plan, the remaining provisions of this Section 4 and Section 5(b), all Restricted Stock Units for which the Period of Restriction had not lapsed prior to the date of the Participant’s Termination (as defined in Appendix A attached hereto) shall be immediately forfeited. Notwithstanding the foregoing to the contrary:
(a) In the event of the Participant’s death or Disability (as defined in Appendix A attached hereto) prior to his or her Termination, the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety.
(b) In the event of the Participant’s Termination due to his or her Normal Retirement (as defined below), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
(c) In the event of the Participant’s involuntary Termination by the Corporation or an Affiliate (as defined in Appendix A attached hereto) without Cause (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Bonus Restricted Stock Units shall lapse in its entirety; provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
For purposes of this Agreement, “Normal Retirement” means Termination of the Participant, other than for Cause, after the Participant has reached 62 years of age.
5. Change in Control .
(a)    In the event of a corporate transaction described in Section 7.2 of the Plan (which generally includes transactions that the Corporation does not survive or does not survive as a public company in respect of its Common Stock), the provisions of Section 7.2 of the Plan shall apply to the remaining unpaid Restricted Stock Units; provided, however,





that the payment date of the Restricted Stock Units that are to be paid pursuant to the award shall in all cases be determined pursuant to Section 6 .
(b)    In the event the Participant is Terminated by the Corporation or an Affiliate (including any successor to such entity) without Cause upon or at any time during the twelve-month period following a Change in Control (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
6. Delivery of Shares .
The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed according to the vesting schedule set forth in the Grant Notice, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 4 or Section 5(b) of this Agreement, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant on the first to occur of (i) as soon as reasonably practicable following (and in any event within [30] days after) the date of the Participant’s death or Disability, or (ii) upon the next Normal Distribution Date immediately following the first anniversary of the Participant’s “separation from service” (as such term is used for purposes of Section 409A of the Code), whether such separation from service results from the Participant’s Normal Retirement, Termination by the Corporation or an Affiliate without Cause or otherwise. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 7.2 of the Plan, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice; provided, however, that (i) if the Participant dies or incurs a Disability prior to any such Lapse Date, the related payment shall be made to the Participant as soon as reasonably practicable following (and in any event within [30] days after) the date of the Participant’s death or Disability, or (ii) if the Participant’s separation from service occurs prior to such Lapse Date, the related payment shall be made upon the next Normal Distribution Date following the first anniversary of the Participant’s separation from service. For purposes of this Section 6, if such payment date is a day on which the New York Stock Exchange is not open for trading, the payment date shall be the next day on which such exchange is open for trading. Notwithstanding the foregoing provisions of this Section 6, the Administrator may provide for payment of any Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed in accordance with the requirements of Treasury Regulation 1.409A-3(j)(4)(ix)(A), (B) or (C) promulgated under Section 409A of the Code (or any similar successor provision), which regulation generally provides that a deferred compensation arrangement may be terminated in limited circumstances following a dissolution or change in control of the Corporation. The Participant shall have no rights to receive delivery of any Shares with respect to Restricted Stock Units that have been forfeited or cancelled, or for which Shares have previously been delivered. No fractional Shares shall be delivered, and the Shares otherwise deliverable in any payment pursuant to this Section 6 shall be rounded down to the nearest whole number of Shares.
7. No Ownership Rights Prior to Issuance of Shares .
Neither the Participant nor any other person shall become the beneficial owner of the Shares underlying the Restricted Stock Units, nor have any rights to dividends (other than rights to Dividend Equivalents pursuant to Section 3) or other rights as a shareholder with respect to any such Shares, until and after such Shares have been actually issued to the Participant and transferred on the books and records of the Corporation or its agent in accordance with the terms of the Plan and this Agreement.
8. Detrimental Activity .
(a)    Notwithstanding any other provisions of this Agreement to the contrary, if at any time prior to the delivery of Shares with respect to the Restricted Stock Units, the Participant engages in Detrimental Activity (as defined below), such Restricted Stock Units shall be cancelled and rescinded without any payment or consideration therefor. The determination of whether the Participant has engaged in Detrimental Activity shall be made by the Administrator in its good faith discretion, and lapse of the Period of Restriction and delivery of Shares with respect to the Restricted Stock Units shall be suspended pending resolution to the Administrator’s satisfaction of any investigation of the matter.
(b)    For purposes of this Agreement, “Detrimental Activity” means at any time (i) using information received during the Participant’s employment with the Corporation and/or its Subsidiaries, Affiliates and predecessors in interest relating to the business affairs of the Corporation or any such Subsidiaries, Affiliates or predecessors in interest, in breach of the Participant’s express or implied undertaking to keep such information confidential; (ii) directly or indirectly persuading or attempting to persuade, by any means, any employee of the Corporation or any of its Subsidiaries or Affiliates to breach any of the terms of his or her employment with Corporation, its Subsidiaries or its Affiliates; (iii) directly or indirectly making any statement that is, or could be, disparaging of the Corporation or any of its Subsidiaries or Affiliates, or any of their respective





employees (except to the extent necessary to respond truthfully to any inquiry from applicable regulatory authorities or to provide information pursuant to legal process); (iv) directly or indirectly engaging in any illegal, unethical or otherwise wrongful activity that is, or could be, substantially injurious to the financial condition, reputation or goodwill of the Corporation or any of its Subsidiaries or Affiliates; or (v) directly or indirectly engaging in an act of misconduct such as, embezzlement, fraud, dishonesty, nonpayment of any obligation owed to the Corporation or any of its Subsidiaries or Affiliates, breach of fiduciary duty or disregard or violation of rules, policies or procedures of the Corporation or any of its Subsidiaries or Affiliates, an unauthorized disclosure of any trade secret or confidential information of the Corporation or any of its Subsidiaries or Affiliates, any conduct constituting unfair competition, or inducing any customer to breach a contract with the Corporation or any of its Subsidiaries or Affiliates, in each case as determined by the Administrator in its good faith discretion.
(c)    Nothing in this Agreement prohibits Participant from reporting possible violations of federal law or regulation to any governmental agency or entity, or making other disclosures that are protected under the whistleblower provisions of federal law or regulation. Participant does not need any prior authorization to make any such reports or disclosures and is not required to notify the Corporation of such reports or disclosures.
9. No Right to Continued Employment .
None of the Restricted Stock Units nor any terms contained in this Agreement shall confer upon the Participant any express or implied right to be retained in the employ of the Corporation or any Subsidiary or Affiliate for any period, nor restrict in any way the right of the Corporation or any Subsidiary or any Affiliate, which right is hereby expressly reserved, to terminate the Participant’s employment at any time for any reason. For the avoidance of doubt, this Section 9 is not intended to amend or modify any other agreement, including any employment agreement, that may be in existence between the Participant and the Corporation or any Subsidiary or Affiliate.
10. The Plan .
In consideration for this grant, the Participant agrees to comply with the terms of the Plan and this Agreement. This Agreement is subject to all the terms, provisions and conditions of the Plan, which are incorporated herein by reference, and to such regulations as may from time to time be adopted by the Administrator. In the event of any conflict between the provisions of the Plan and this Agreement, the provisions of the Plan shall control, and this Agreement shall be deemed to be modified accordingly, provided that the provisions of Section 6 (Delivery of Shares) of this Agreement shall control over any conflicting payment provisions of the Plan. The Plan and the prospectus describing the Plan can be found on Fidelity NetBenefits® at www.netbenefits.com under Plan Information and Documents. A paper copy of the Plan and the prospectus shall be provided to the Participant upon the Participant’s written request to the Corporation at CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify.
11. Compliance with Laws and Regulations .
(a)    The Restricted Stock Units and the obligation of the Corporation to sell and deliver Shares hereunder shall be subject in all respects to (i) all applicable Federal and state laws, rules and regulations and (ii) any registration, qualification, approvals or other requirements imposed by any government or regulatory agency or body which the Administrator shall, in its discretion, determine to be necessary or applicable. Moreover, the Corporation shall not deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement if doing so would be contrary to applicable law. If at any time the Corporation determines, in its discretion, that the listing, registration or qualification of Shares upon any national securities exchange or under any state or Federal law, or the consent or approval of any governmental regulatory body, is necessary or desirable, the Corporation shall not be required to deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement unless and until such listing, registration, qualification, consent or approval has been effected or obtained, or otherwise provided for, free of any conditions not acceptable to the Corporation.
(b)    It is intended that the Shares received in respect of the Restricted Stock Units shall have been registered under the Securities Act. If the Participant is an “affiliate” of the Corporation, as that term is defined in Rule 144 under the Securities Act (“Rule 144”), the Participant may not sell the Shares received except in compliance with Rule 144. Certificates representing Shares issued to an “affiliate” of the Corporation may bear a legend setting forth such restrictions on the disposition or transfer of the Shares as the Corporation deems appropriate to comply with Federal and state securities laws.
(c)    If, at any time, the Shares are not registered under the Securities Act, and/or there is no current prospectus in effect under the Securities Act with respect to the Shares, the Participant shall execute, prior to the delivery of any Shares to the Participant by the Corporation pursuant to this Agreement, an agreement (in such form as the Corporation may specify) in which the Participant represents and warrants that the Participant is purchasing or acquiring the Shares acquired under this Agreement for the Participant's own account, for investment only and not with a view to the resale or distribution thereof, and represents and agrees that any subsequent offer for sale or distribution of any kind of such Shares shall be made only pursuant to either (i) a registration statement on an appropriate form under the Securities Act, which registration statement has become effective





and is current with regard to the Shares being offered or sold, or (ii) a specific exemption from the registration requirements of the Securities Act, but in claiming such exemption the Participant shall, prior to any offer for sale of such Shares, obtain a prior favorable written opinion, in form and substance satisfactory to the Corporation, from counsel for or approved by the Corporation, as to the applicability of such exemption thereto.
12. Notices .
All notices by the Participant or the Participant’s assignees shall be addressed to CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify. All notices to the Participant shall be addressed to the Participant at the Participant’s address in the Corporation's records.
13. Severability .
In the event any provision of this Agreement shall be held illegal or invalid for any reason, the illegality or invalidity shall not affect the remaining parts of this Agreement, and this Agreement shall be construed and enforced as if the illegal or invalid provision had not been included.
14. Other Plans .
The Participant acknowledges that any income derived from the Restricted Stock Units shall not affect the Participant’s participation in, or benefits under, any other benefit plan or other contract or arrangement maintained by the Corporation or any Subsidiary or Affiliate. Restricted Stock Units and Dividend Equivalents shall not be deemed to be “Covered Compensation” under any other benefit plan of the Corporation.
15.     Adjustments .
The Restricted Stock Units and the Shares underlying the Restricted Stock Units shall be subject to adjustment and conversion pursuant to the terms of Section 7.1 of the Plan.
16.     Tax Withholding .
Any payment or delivery of Shares pursuant to this Agreement shall be subject to the Corporation’s rights to withhold applicable Federal, state, local and non-United States taxes in accordance with Section 8.5 of the Plan.
17.     Section 409A .
The provisions of this Agreement shall be construed and interpreted to comply with Section 409A of the Code so as to avoid the imposition of any penalties, taxes or interest thereunder.
18.     Clawback .
The Restricted Stock Units are subject to the terms of the Corporation’s recoupment, clawback or similar policy as it may be in effect from time to time, as well as any similar provisions of applicable law, any of which could in certain circumstances require repayment or forfeiture of the Restricted Stock Units or any Shares or other cash or property received with respect to the Restricted Stock Units (including any value received from a disposition of the Shares acquired upon payment of the Restricted Stock Units).
CORELOGIC, INC.
    

By:_______________________________
                            Name: Frank Martell    
Title: President and Chief Executive Officer
Date: [Grant Date]

Acknowledged and agreed as of the Date of Grant:


Printed Name:     [Participant Name]
Date:     [Acceptance Date]

NOTE: GRANT WILL BE ACCEPTED ELECTRONICALLY





APPENDIX A

Certain Definitions

Affiliate ” means any entity other than the Corporation and any Subsidiary that is affiliated with the Corporation through stock or equity ownership or otherwise and is designated as an Affiliate for purposes of the Plan by the Administrator.

Cause ” has the same meaning as in the Participant’s employment agreement with the Corporation, a Subsidiary or an Affiliate (if any) as in effect at the time of the Participant’s Termination, or if the Participant is not a party to such an employment agreement (or is not a party to such an employment agreement that contains a definition of “cause”), “Cause” means: (i) embezzlement, theft or misappropriation by the Participant of any property of any of the Corporation or its Affiliates; (ii) the Participant’s breach of any fiduciary duty to the Corporation or its Affiliates; (iii) the Participant’s failure or refusal to comply with laws or regulations applicable to the Corporation or its Affiliates and their businesses or the policies of the Corporation and its Affiliates governing the conduct of its employees or directors; (iv) the Participant’s gross incompetence in the performance of the Participant’s job duties; (v) commission by the Participant of a felony or of any crime involving moral turpitude, fraud or misrepresentation; (vi) the failure of the Participant to perform duties consistent with a commercially reasonable standard of care; (vii) the Participant’s failure or refusal to perform the Participant’s job duties or to perform specific directives of the Participant’s supervisor or designee, or the senior officers or Board of Directors of the Corporation; or (viii) any gross negligence or willful misconduct of the Participant resulting in loss to the Corporation or its Affiliates, or damage to the reputation of the Corporation or its Affiliates.
Change in Control ” means the happening of any of the following after the date hereof:

(a)
The consummation of a merger or consolidation of the Corporation with or into another entity or any other corporate reorganization, if fifty percent (50%) or more of the combined voting power of the continuing or surviving entity’s securities outstanding immediately after such merger, consolidation, or other reorganization is owned by persons who were not shareholders of the Corporation immediately prior to such merger, consolidation, or other reorganization.
(b)
The sale, transfer, or other disposition of all or substantially all of the Corporation’s assets or the complete liquidation or dissolution of the Corporation.
(c)
A change in the composition of the Board occurring within a two (2) year period, as a result of which fewer than a majority of the directors are Incumbent Directors. “ Incumbent Directors ” shall mean directors who are directors of the Corporation immediately following the consummation of the transactions contemplated by the Separation and Distribution Agreement by and between the Corporation and the First American Financial Corporation dated June 1, 2010 (the “ Separation Agreement ”). “ Incumbent Directors ” shall also include directors who are elected, or nominated for election, to the Board with the affirmative votes of at least a majority of the Incumbent Directors at the time of such election or nomination, but shall not include an individual not otherwise an Incumbent Director whose election or nomination is in connection with an actual or threatened proxy contest relating to the election of directors to the Corporation.
(d)
Any transaction as a result of which any person or group is or becomes the “ beneficial owner ” (as defined in Rule 13d-3 under the Securities Exchange Act of 1934), directly or indirectly, of securities of the Corporation representing at least thirty percent (30%) of the total voting power of the Corporation’s then outstanding voting securities. For purposes of this paragraph, the term “ person ” shall have the same meaning as when used in Sections 13(d) and 14(d) of the Securities Exchange Act of 1934, but shall exclude: (i) a trustee or other fiduciary holding securities under an employee benefit plan of the Corporation or of a Subsidiary of the Corporation; (ii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person whose beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities increases to thirty percent (30%) or more as a result of the acquisition of voting securities of the Corporation by the Corporation which reduces the number of such voting securities then outstanding; or (iii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person that acquires directly from the Corporation securities of the Corporation representing at least thirty percent (30%) of the total voting power represented by the Corporation’s then outstanding voting securities.
A transaction shall not constitute a Change in Control if its sole purpose is to change the state of the Corporation’s incorporation or to create a holding company that will be owned in substantially the same proportions by the persons who held the Corporation’s securities immediately before such transaction.





For the avoidance of doubt, the consummation of any or all of the transactions in the Separation Agreement is not considered a Change in Control for purposes of this Agreement.
Disability ” means the inability to engage in any substantial gainful occupation to which the relevant individual is suited by education, training or experience, by reason of any medically determinable physical or mental impairment, which condition can be expected to result in death or continues for a continuous period of not less than twelve (12) months.
Normal Distribution Date ” means either March 20, June 20, September 20 or December 20, as applicable; provided that if such date is a day on which the New York Stock Exchange is not open for trading, the Normal Distribution Date shall be the next day on which such exchange is open for trading.
Termination ” means the time when the Participant ceases the performance of services for the Corporation, any Affiliate or Subsidiary, as applicable, for any reason, with or without Cause, including a Termination by resignation, discharge, retirement, death or Disability, but excluding (a) a Termination where there is a simultaneous reemployment or continuing employment of the Participant by the Corporation, any Affiliate or Subsidiary, (b) at the discretion of the Administrator, a Termination that results in a temporary severance, and (c) at the discretion of the Administrator, a Termination of an employee of the Corporation that is immediately followed by the Participant’s service as a non-employee director of the Board.  Notwithstanding any other provisions of the Plan or this Agreement to the contrary, a Termination shall not be deemed to have occurred for purposes of any provision the Plan or this Agreement providing for payment or distribution with respect to an award constituting deferred compensation subject to Code Section 409A upon or following a termination of employment or services unless such termination is also a “separation from service” within the meaning of Section 409A of the Code.










Notice of Restricted Stock Unit Grant

Participant:          [Participant Name]
Corporation:         CoreLogic, Inc.
Notice:
You have been granted the following Restricted Stock Units in accordance with the terms of the Plan and the Restricted Stock Unit Award Agreement attached hereto.
Type of Award:
Restricted Stock Units
Plan:
CoreLogic, Inc. 2018 Performance Incentive Plan
Grant:             Date of Grant:   [Grant Date]
Number of Shares Underlying Bonus Restricted Stock Units:   [Number of Shares                          Granted]

Period of Restriction:
Subject to the terms of the Plan and this Agreement, the Period of Restriction applicable to the Restricted Stock Units shall commence on the Date of Grant and shall lapse on the date listed in the “Lapse Date” column below as to that portion of Shares underlying the Restricted Stock Units set forth below opposite each such date.

Lapse Date
Portion of Shares as to
Which Period of Restriction Lapses
Date of Grant + 1 year
1/3
Date of Grant + 2 years
1/3
Date of Grant + 3 years
1/3

For purposes of this Agreement, “Period of Restriction” means the period during which the Restricted Stock Units are subject to a substantial risk of forfeiture. The date on which the Period of Restriction lapses pursuant to this paragraph is referred to herein as the “Lapse Date.”

The vesting schedule set forth above requires the Participant’s continued employment or service through each applicable Lapse Date as a condition to the lapsing of the Period of Restriction on such Lapse Date. Except as provided in Section 4 or Section 5 of this Agreement, employment or service for only a portion of the Period of Restriction prior to the Lapse Date, even if a substantial portion, will not entitle the Participant to any proportionate vesting or avoid or mitigate a termination of rights and benefits upon or following a termination of employment or services as provided in Section 4 below or under the Plan.

Rejection:
If you wish to accept this Restricted Stock Unit Award, please access Fidelity NetBenefits® at www.netbenefits.com and follow the steps outlined under the "Accept Grant" link at any time within forty-five (45) days after the Date of Grant. If you do not accept your grant via Fidelity NetBenefits® within forty-five (45) days after the Date of Grant, you will have rejected this Restricted Stock Unit Award.






Restricted Stock Unit Award Agreement

This Restricted Stock Unit Award Agreement (this “Agreement”), dated as of the Date of Grant set forth in the Notice of Restricted Stock Unit Grant attached hereto (the “Grant Notice”), is made between CoreLogic, Inc. (the “Corporation”) and the Participant set forth in the Grant Notice. The Grant Notice is included in and made part of this Agreement.
1. Definitions .
Certain capitalized terms are defined in the Grant Notice, herein or in the attached Appendix A. Capitalized terms used but not defined in the Grant Notice, herein or in the attached Appendix A shall have the meaning assigned to such terms in the Plan.
2. Grant of the Restricted Stock Units .
Subject to the provisions of this Agreement and the provisions of the Plan, the Corporation hereby grants to the Participant, pursuant to the Plan, a right to receive the number of shares of Common Stock (“Shares”) set forth in the Grant Notice (the “Restricted Stock Units”).
3. Dividend Equivalents .
Each Restricted Stock Unit shall accrue Dividend Equivalents (as defined below) with respect to dividends that would otherwise be paid on the Share underlying such Restricted Stock Unit during the period from the Grant Date to the date such Share is delivered in accordance with Section 6. As of any date in this period that the Corporation pays an ordinary cash dividend on its Common Stock, the Corporation shall credit the Participant with an additional number of Restricted Stock Units equal to (i) the per share cash dividend paid by the Corporation on its Common Stock on such date, multiplied by (ii) the total number of Restricted Stock Units subject to the award as of the related dividend payment record date (including any Dividend Equivalents previously credited hereunder), divided by (iii) the fair market value (as determined in accordance with the terms of the Plan) of a share of Common Stock on the date of payment of such dividend. Any Restricted Stock Units credited pursuant to the foregoing provisions of this Section 3 shall be subject to the same Period of Restriction, payment, delivery and other terms, conditions and restrictions as the original Restricted Stock Units to which they relate. Any such crediting of Dividend Equivalents shall be conclusively determined by the Administrator. No crediting of Restricted Stock Units shall be made pursuant to this Section 3 with respect to any Restricted Stock Units which, as of such record date, have either been delivered or terminated pursuant to the Plan or this Agreement. For purposes of this Agreement, “Dividend Equivalents” means the equivalent value (in cash or Shares) of dividends that would otherwise be paid on the Shares subject to the Restricted Stock Units but that have not been issued or delivered.
4. Period of Restriction; Termination .
The Period of Restriction with respect to the Restricted Stock Units shall be as set forth in the Grant Notice. Subject to the terms of the Plan, the remaining provisions of this Section 4 and Section 5(b), all Restricted Stock Units for which the Period of Restriction had not lapsed prior to the date of the Participant’s Termination (as defined in Appendix A attached hereto) shall be immediately forfeited. Notwithstanding the foregoing to the contrary:
(a) In the event of the Participant’s death or Disability (as defined in Appendix A attached hereto) prior to his or her Termination, the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety.
(b) In the event of the Participant’s Termination due to his or her Normal Retirement (as defined below), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
(c) In the event of the Participant’s involuntary Termination by the Corporation or an Affiliate (as defined in Appendix A attached hereto) without Cause (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Bonus Restricted Stock Units shall lapse in its entirety; provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
For purposes of this Agreement, “Normal Retirement” means Termination of the Participant, other than for Cause, after the Participant has reached 62 years of age.







5. Change in Control .
(a)    In the event of a corporate transaction described in Section 7.2 of the Plan (which generally includes transactions that the Corporation does not survive or does not survive as a public company in respect of its Common Stock), the provisions of Section 7.2 of the Plan shall apply to the remaining unpaid Restricted Stock Units; provided, however, that the payment date of the Restricted Stock Units that are to be paid pursuant to the award shall in all cases be determined pursuant to Section 6 .
(b)    In the event the Participant is Terminated by the Corporation or an Affiliate (including any successor to such entity) without Cause upon or at any time during the twelve-month period following a Change in Control (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
6. Delivery of Shares .
The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed according to the vesting schedule set forth in the Grant Notice, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 4 or Section 5(b) of this Agreement, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days, following the first to occur of (i) the date of the Participant’s death or Disability, or (ii) the first anniversary of the Participant’s “separation from service” (as such term is used for purposes of Section 409A of the Code), whether such separation from service results from the Participant’s Normal Retirement, Termination by the Corporation or an Affiliate without Cause or otherwise. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 7.2 of the Plan, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice; provided, however, that (i) if the Participant dies or incurs a Disability prior to any such Lapse Date, the related payment shall be made to the Participant as soon as reasonably practicable, but in no event later than 74 days, following the date of the Participant’s death or Disability, or (ii) if the Participant’s separation from service occurs prior to such Lapse Date, the related payment shall be made on the first anniversary of the Participant’s separation from service. Notwithstanding the foregoing provisions of this Section 6, the Administrator may provide for payment of any Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed in accordance with the requirements of Treasury Regulation 1.409A-3(j)(4)(ix)(A), (B) or (C) promulgated under Section 409A of the Code (or any similar successor provision), which regulation generally provides that a deferred compensation arrangement may be terminated in limited circumstances following a dissolution or change in control of the Corporation. The Participant shall have no rights to receive delivery of any Shares with respect to Restricted Stock Units that have been forfeited or cancelled, or for which Shares have previously been delivered. No fractional Shares shall be delivered, and the Shares otherwise deliverable in any payment pursuant to this Section 6 shall be rounded down to the nearest whole number of Shares.
7. No Ownership Rights Prior to Issuance of Shares .
Neither the Participant nor any other person shall become the beneficial owner of the Shares underlying the Restricted Stock Units, nor have any rights to dividends (other than rights to Dividend Equivalents pursuant to Section 3) or other rights as a shareholder with respect to any such Shares, until and after such Shares have been actually issued to the Participant and transferred on the books and records of the Corporation or its agent in accordance with the terms of the Plan and this Agreement.
8. Detrimental Activity .
(a)    Notwithstanding any other provisions of this Agreement to the contrary, if at any time prior to the delivery of Shares with respect to the Restricted Stock Units, the Participant engages in Detrimental Activity (as defined below), such Restricted Stock Units shall be cancelled and rescinded without any payment or consideration therefor. The determination of whether the Participant has engaged in Detrimental Activity shall be made by the Administrator in its good faith discretion, and lapse of the Period of Restriction and delivery of Shares with respect to the Restricted Stock Units shall be suspended pending resolution to the Administrator’s satisfaction of any investigation of the matter.
(b)    For purposes of this Agreement, “Detrimental Activity” means at any time (i) using information received during the Participant’s employment with the Corporation and/or its Subsidiaries, Affiliates and predecessors in interest relating to the business affairs of the Corporation or any such Subsidiaries, Affiliates or predecessors in interest, in breach of the Participant’s express or implied undertaking to keep such information confidential; (ii) directly or indirectly persuading or





attempting to persuade, by any means, any employee of the Corporation or any of its Subsidiaries or Affiliates to breach any of the terms of his or her employment with Corporation, its Subsidiaries or its Affiliates; (iii) directly or indirectly making any statement that is, or could be, disparaging of the Corporation or any of its Subsidiaries or Affiliates, or any of their respective employees (except to the extent necessary to respond truthfully to any inquiry from applicable regulatory authorities or to provide information pursuant to legal process); (iv) directly or indirectly engaging in any illegal, unethical or otherwise wrongful activity that is, or could be, substantially injurious to the financial condition, reputation or goodwill of the Corporation or any of its Subsidiaries or Affiliates; or (v) directly or indirectly engaging in an act of misconduct such as, embezzlement, fraud, dishonesty, nonpayment of any obligation owed to the Corporation or any of its Subsidiaries or Affiliates, breach of fiduciary duty or disregard or violation of rules, policies or procedures of the Corporation or any of its Subsidiaries or Affiliates, an unauthorized disclosure of any trade secret or confidential information of the Corporation or any of its Subsidiaries or Affiliates, any conduct constituting unfair competition, or inducing any customer to breach a contract with the Corporation or any of its Subsidiaries or Affiliates, in each case as determined by the Administrator in its good faith discretion.
(c)    Nothing in this Agreement prohibits Participant from reporting possible violations of federal law or regulation to any governmental agency or entity, or making other disclosures that are protected under the whistleblower provisions of federal law or regulation. Participant does not need any prior authorization to make any such reports or disclosures and is not required to notify the Corporation of such reports or disclosures.
9. No Right to Continued Employment .
None of the Restricted Stock Units nor any terms contained in this Agreement shall confer upon the Participant any express or implied right to be retained in the employ of the Corporation or any Subsidiary or Affiliate for any period, nor restrict in any way the right of the Corporation or any Subsidiary or any Affiliate, which right is hereby expressly reserved, to terminate the Participant’s employment at any time for any reason. For the avoidance of doubt, this Section 9 is not intended to amend or modify any other agreement, including any employment agreement, that may be in existence between the Participant and the Corporation or any Subsidiary or Affiliate.
10. The Plan .
In consideration for this grant, the Participant agrees to comply with the terms of the Plan and this Agreement. This Agreement is subject to all the terms, provisions and conditions of the Plan, which are incorporated herein by reference, and to such regulations as may from time to time be adopted by the Administrator. In the event of any conflict between the provisions of the Plan and this Agreement, the provisions of the Plan shall control, and this Agreement shall be deemed to be modified accordingly, provided that the provisions of Section 6 (Delivery of Shares) of this Agreement shall control over any conflicting payment provisions of the Plan. The Plan and the prospectus describing the Plan can be found on Fidelity NetBenefits® at www.netbenefits.com under Plan Information and Documents. A paper copy of the Plan and the prospectus shall be provided to the Participant upon the Participant’s written request to the Corporation at CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify.
11. Compliance with Laws and Regulations .
(a)    The Restricted Stock Units and the obligation of the Corporation to sell and deliver Shares hereunder shall be subject in all respects to (i) all applicable Federal and state laws, rules and regulations and (ii) any registration, qualification, approvals or other requirements imposed by any government or regulatory agency or body which the Administrator shall, in its discretion, determine to be necessary or applicable. Moreover, the Corporation shall not deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement if doing so would be contrary to applicable law. If at any time the Corporation determines, in its discretion, that the listing, registration or qualification of Shares upon any national securities exchange or under any state or Federal law, or the consent or approval of any governmental regulatory body, is necessary or desirable, the Corporation shall not be required to deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement unless and until such listing, registration, qualification, consent or approval has been effected or obtained, or otherwise provided for, free of any conditions not acceptable to the Corporation.
(b)    It is intended that the Shares received in respect of the Restricted Stock Units shall have been registered under the Securities Act. If the Participant is an “affiliate” of the Corporation, as that term is defined in Rule 144 under the Securities Act (“Rule 144”), the Participant may not sell the Shares received except in compliance with Rule 144. Certificates representing Shares issued to an “affiliate” of the Corporation may bear a legend setting forth such restrictions on the disposition or transfer of the Shares as the Corporation deems appropriate to comply with Federal and state securities laws.
(c)    If, at any time, the Shares are not registered under the Securities Act, and/or there is no current prospectus in effect under the Securities Act with respect to the Shares, the Participant shall execute, prior to the delivery of any Shares to the Participant by the Corporation pursuant to this Agreement, an agreement (in such form as the Corporation may specify) in which the Participant represents and warrants that the Participant is purchasing or acquiring the Shares acquired under





this Agreement for the Participant's own account, for investment only and not with a view to the resale or distribution thereof, and represents and agrees that any subsequent offer for sale or distribution of any kind of such Shares shall be made only pursuant to either (i) a registration statement on an appropriate form under the Securities Act, which registration statement has become effective and is current with regard to the Shares being offered or sold, or (ii) a specific exemption from the registration requirements of the Securities Act, but in claiming such exemption the Participant shall, prior to any offer for sale of such Shares, obtain a prior favorable written opinion, in form and substance satisfactory to the Corporation, from counsel for or approved by the Corporation, as to the applicability of such exemption thereto.
12. Notices .
All notices by the Participant or the Participant’s assignees shall be addressed to CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify. All notices to the Participant shall be addressed to the Participant at the Participant’s address in the Corporation's records.
13. Severability .
In the event any provision of this Agreement shall be held illegal or invalid for any reason, the illegality or invalidity shall not affect the remaining parts of this Agreement, and this Agreement shall be construed and enforced as if the illegal or invalid provision had not been included.
14. Other Plans .
The Participant acknowledges that any income derived from the Restricted Stock Units shall not affect the Participant’s participation in, or benefits under, any other benefit plan or other contract or arrangement maintained by the Corporation or any Subsidiary or Affiliate. Restricted Stock Units and Dividend Equivalents shall not be deemed to be “Covered Compensation” under any other benefit plan of the Corporation.
15.     Vesting of Restricted Stock Units Contingent on Corporation Performance .
Notwithstanding any other provisions in this Agreement, except in the event of an acceleration of vesting pursuant to Section 4(a) or Section 5 of this Agreement, the Participant’s entitlement to the receipt of any Shares hereunder is contingent upon the Corporation’s achievement of net income (as defined in accordance with generally acceptable accounting principles) for 2018 of $62.5 million or more. Net income shall be determined without regard to (a) amortization related to acquired intangibles, (b) asset write-downs, (c) litigation or claim judgments or settlements, (d) the effect of changes in tax laws, accounting principles, or other laws or provisions affecting reported results, (e) any transformation, reorganization and restructuring program costs, (f) non-cash stock compensation, (g) extraordinary, unusual and/or nonrecurring items of gain or loss, and (h) foreign exchange gains and losses. The provisions of this Section 15 shall be a Business Criteria under the Plan, and shall be subject to all of the terms of the Plan applicable to Performance-Based Awards.
16.     Adjustments .
The Restricted Stock Units and the Shares underlying the Restricted Stock Units shall be subject to adjustment and conversion pursuant to the terms of Section 7.1 of the Plan.
17.     Tax Withholding .
Any payment or delivery of Shares pursuant to this Agreement shall be subject to the Corporation’s rights to withhold applicable Federal, state, local and non-United States taxes in accordance with Section 8.5 of the Plan.
18.     Section 409A .
The provisions of this Agreement shall be construed and interpreted to comply with Section 409A of the Code so as to avoid the imposition of any penalties, taxes or interest thereunder.
19.     Clawback .    The Restricted Stock Units are subject to the terms of the Corporation’s recoupment, clawback or similar policy as it may be in effect from time to time, as well as any similar provisions of applicable law, any of which could in certain circumstances require repayment or forfeiture of the Restricted Stock Units or any Shares or other cash or property received with respect to the Restricted Stock Units (including any value received from a disposition of the Shares acquired upon payment of the Restricted Stock Units).





CORELOGIC, INC.

    
By:______________________________
                            Name: Frank Martell
Title: President and Chief Executive Officer
Date: [Grant Date]


Acknowledged and agreed as of the Date of Grant:



Printed Name:     [Participant Name]
Date:     [Acceptance Date]


NOTE: GRANT WILL BE ACCEPTED ELECTRONICALLY






APPENDIX A

Certain Definitions

Affiliate ” means any entity other than the Corporation and any Subsidiary that is affiliated with the Corporation through stock or equity ownership or otherwise and is designated as an Affiliate for purposes of the Plan by the Administrator.

Cause ” has the same meaning as in the Participant’s employment agreement with the Corporation, a Subsidiary or an Affiliate (if any) as in effect at the time of the Participant’s Termination, or if the Participant is not a party to such an employment agreement (or is not a party to such an employment agreement that contains a definition of “cause”), “Cause” means: (i) embezzlement, theft or misappropriation by the Participant of any property of any of the Corporation or its Affiliates; (ii) the Participant’s breach of any fiduciary duty to the Corporation or its Affiliates; (iii) the Participant’s failure or refusal to comply with laws or regulations applicable to the Corporation or its Affiliates and their businesses or the policies of the Corporation and its Affiliates governing the conduct of its employees or directors; (iv) the Participant’s gross incompetence in the performance of the Participant’s job duties; (v) commission by the Participant of a felony or of any crime involving moral turpitude, fraud or misrepresentation; (vi) the failure of the Participant to perform duties consistent with a commercially reasonable standard of care; (vii) the Participant’s failure or refusal to perform the Participant’s job duties or to perform specific directives of the Participant’s supervisor or designee, or the senior officers or Board of Directors of the Corporation; or (viii) any gross negligence or willful misconduct of the Participant resulting in loss to the Corporation or its Affiliates, or damage to the reputation of the Corporation or its Affiliates.
Change in Control ” means the happening of any of the following after the date hereof:

(a)
The consummation of a merger or consolidation of the Corporation with or into another entity or any other corporate reorganization, if fifty percent (50%) or more of the combined voting power of the continuing or surviving entity’s securities outstanding immediately after such merger, consolidation, or other reorganization is owned by persons who were not shareholders of the Corporation immediately prior to such merger, consolidation, or other reorganization.
(b)
The sale, transfer, or other disposition of all or substantially all of the Corporation’s assets or the complete liquidation or dissolution of the Corporation.
(c)
A change in the composition of the Board occurring within a two (2) year period, as a result of which fewer than a majority of the directors are Incumbent Directors. “ Incumbent Directors ” shall mean directors who are directors of the Corporation immediately following the consummation of the transactions contemplated by the Separation and Distribution Agreement by and between the Corporation and the First American Financial Corporation dated June 1, 2010 (the “ Separation Agreement ”). “ Incumbent Directors ” shall also include directors who are elected, or nominated for election, to the Board with the affirmative votes of at least a majority of the Incumbent Directors at the time of such election or nomination, but shall not include an individual not otherwise an Incumbent Director whose election or nomination is in connection with an actual or threatened proxy contest relating to the election of directors to the Corporation.
(d)
Any transaction as a result of which any person or group is or becomes the “ beneficial owner ” (as defined in Rule 13d-3 under the Securities Exchange Act of 1934), directly or indirectly, of securities of the Corporation representing at least thirty percent (30%) of the total voting power of the Corporation’s then outstanding voting securities. For purposes of this paragraph, the term “ person ” shall have the same meaning as when used in Sections 13(d) and 14(d) of the Securities Exchange Act of 1934, but shall exclude: (i) a trustee or other fiduciary holding securities under an employee benefit plan of the Corporation or of a Subsidiary of the Corporation; (ii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person whose beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities increases to thirty percent (30%) or more as a result of the acquisition of voting securities of the Corporation by the Corporation which reduces the number of such voting securities then outstanding; or (iii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person that acquires directly from the Corporation securities of the Corporation representing at least thirty percent (30%) of the total voting power represented by the Corporation’s then outstanding voting securities.
A transaction shall not constitute a Change in Control if its sole purpose is to change the state of the Corporation’s incorporation or to create a holding company that will be owned in substantially the same proportions by the persons who held the Corporation’s securities immediately before such transaction.





For the avoidance of doubt, the consummation of any or all of the transactions in the Separation Agreement is not considered a Change in Control for purposes of this Agreement.
Disability ” means the inability to engage in any substantial gainful occupation to which the relevant individual is suited by education, training or experience, by reason of any medically determinable physical or mental impairment, which condition can be expected to result in death or continues for a continuous period of not less than twelve (12) months.
Termination ” means the time when the Participant ceases the performance of services for the Corporation, any Affiliate or Subsidiary, as applicable, for any reason, with or without Cause, including a Termination by resignation, discharge, retirement, death or Disability, but excluding (a) a Termination where there is a simultaneous reemployment or continuing employment of the Participant by the Corporation, any Affiliate or Subsidiary, (b) at the discretion of the Administrator, a Termination that results in a temporary severance, and (c) at the discretion of the Administrator, a Termination of an employee of the Corporation that is immediately followed by the Participant’s service as a non-employee director of the Board.  Notwithstanding any other provisions of the Plan or this Agreement to the contrary, a Termination shall not be deemed to have occurred for purposes of any provision the Plan or this Agreement providing for payment or distribution with respect to an award constituting deferred compensation subject to Code Section 409A upon or following a termination of employment or services unless such termination is also a “separation from service” within the meaning of Section 409A of the Code.









Notice of Restricted Stock Unit Grant (UK version)

Participant:          [Participant Name]
Corporation:         CoreLogic, Inc.
Notice:
You have been granted the following Restricted Stock Units in accordance with the terms of the Plan and the Restricted Stock Unit Award Agreement attached hereto.
Type of Award:
Restricted Stock Units
Plan:
CoreLogic, Inc. 2018 Performance Incentive Plan
Grant:             Date of Grant:   [Grant Date]
Number of Shares Underlying Bonus Restricted Stock Units:   [Number of Shares                          Granted]

Period of Restriction:
Subject to the terms of the Plan and this Agreement, the Period of Restriction applicable to the Restricted Stock Units shall commence on the Date of Grant and shall lapse on the date listed in the “Lapse Date” column below as to that portion of Shares underlying the Restricted Stock Units set forth below opposite each such date.

Lapse Date
Portion of Shares as to
Which Period of Restriction Lapses
20 th  day of Date of Grant month + 1 year
1/3
20 th  day of Date of Grant month + 2 years
1/3
20 th  day of Date of Grant month + 3 years
1/3

For purposes of this Agreement, “Period of Restriction” means the period during which the Restricted Stock Units are subject to a substantial risk of forfeiture. The date on which the Period of Restriction lapses pursuant to this paragraph is referred to herein as the “Lapse Date.”

The vesting schedule set forth above requires the Participant’s continued employment or service through each applicable Lapse Date as a condition to the lapsing of the Period of Restriction on such Lapse Date. Except as provided in Section 4 or Section 5 of this Agreement, employment or service for only a portion of the Period of Restriction prior to the Lapse Date, even if a substantial portion, will not entitle the Participant to any proportionate vesting or avoid or mitigate a termination of rights and benefits upon or following a termination of employment or services as provided in Section 4 below or under the Plan.

Rejection:
If you wish to accept this Restricted Stock Unit Award, please access Fidelity NetBenefits® at www.netbenefits.com and follow the steps outlined under the "Accept Grant" link at any time within forty-five (45) days after the Date of Grant. If you do not accept your grant via Fidelity NetBenefits® within forty-five (45) days after the Date of Grant, you will have rejected this Restricted Stock Unit Award.






Restricted Stock Unit Award Agreement (UK version)

This Restricted Stock Unit Award Agreement (this “Agreement”), dated as of the Date of Grant set forth in the Notice of Restricted Stock Unit Grant attached hereto (the “Grant Notice”), is made between CoreLogic, Inc. (the “Corporation”) and the Participant set forth in the Grant Notice. The Grant Notice is included in and made part of this Agreement.
1. Definitions .
Certain capitalized terms are defined in the Grant Notice, herein or in the attached Appendix A. Capitalized terms used but not defined in the Grant Notice, herein or in the attached Appendix A shall have the meaning assigned to such terms in the Plan.
2. Grant of the Restricted Stock Units .
Subject to the provisions of this Agreement and the provisions of the Plan, the Corporation hereby grants to the Participant, pursuant to the Plan, a right to receive the number of shares of Common Stock (“Shares”) set forth in the Grant Notice (the “Restricted Stock Units”).
3. Dividend Equivalents .
Each Restricted Stock Unit shall accrue Dividend Equivalents (as defined below) with respect to dividends that would otherwise be paid on the Share underlying such Restricted Stock Unit during the period from the Grant Date to the date such Share is delivered in accordance with Section 6. As of any date in this period that the Corporation pays an ordinary cash dividend on its Common Stock, the Corporation shall credit the Participant with an additional number of Restricted Stock Units equal to (i) the per share cash dividend paid by the Corporation on its Common Stock on such date, multiplied by (ii) the total number of Restricted Stock Units subject to the award as of the related dividend payment record date (including any Dividend Equivalents previously credited hereunder), divided by (iii) the fair market value (as determined in accordance with the terms of the Plan) of a share of Common Stock on the date of payment of such dividend. Any Restricted Stock Units credited pursuant to the foregoing provisions of this Section 3 shall be subject to the same Period of Restriction, payment, delivery and other terms, conditions and restrictions as the original Restricted Stock Units to which they relate. Any such crediting of Dividend Equivalents shall be conclusively determined by the Administrator. No crediting of Restricted Stock Units shall be made pursuant to this Section 3 with respect to any Restricted Stock Units which, as of such record date, have either been delivered or terminated pursuant to the Plan or this Agreement. For purposes of this Agreement, “Dividend Equivalents” means the equivalent value (in cash or Shares) of dividends that would otherwise be paid on the Shares subject to the Restricted Stock Units but that have not been issued or delivered.
4. Period of Restriction; Termination .
The Period of Restriction with respect to the Restricted Stock Units shall be as set forth in the Grant Notice. Subject to the terms of the Plan, the remaining provisions of this Section 4 and Section 5(b), all Restricted Stock Units for which the Period of Restriction had not lapsed prior to the date of the Participant’s Termination (as defined in Appendix A attached hereto) shall be immediately forfeited. Notwithstanding the foregoing to the contrary:
(a) In the event of the Participant’s death or Disability (as defined in Appendix A attached hereto) prior to his or her Termination, the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety.
(b) In the event of the Participant’s Termination due to his or her Normal Retirement (as defined below), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
(c) In the event of the Participant’s involuntary Termination by the Corporation or an Affiliate (as defined in Appendix A attached hereto) without Cause (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Bonus Restricted Stock Units shall lapse in its entirety; provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
For purposes of this Agreement, “Normal Retirement” means Termination of the Participant, other than for Cause, after the Participant has reached 62 years of age.
5. Change in Control .
(a)    In the event of a corporate transaction described in Section 7.2 of the Plan (which generally includes transactions that the Corporation does not survive or does not survive as a public company in respect of its Common





Stock), the provisions of Section 7.2 of the Plan shall apply to the remaining unpaid Restricted Stock Units; provided, however, that the payment date of the Restricted Stock Units that are to be paid pursuant to the award shall in all cases be determined pursuant to Section 6 .
(b)    In the event the Participant is Terminated by the Corporation or an Affiliate (including any successor to such entity) without Cause upon or at any time during the twelve-month period following a Change in Control (as defined in Appendix A attached hereto), the Period of Restriction as to all remaining unpaid Restricted Stock Units shall lapse in its entirety, provided that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
6. Delivery of Shares .
The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed according to the vesting schedule set forth in the Grant Notice, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 4 or Section 5(b) of this Agreement, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant on the first to occur of (i) as soon as reasonably practicable following (and in any event within [30] days after) the date of the Participant’s death or Disability, or (ii) upon the next Normal Distribution Date immediately following the first anniversary of the Participant’s “separation from service” (as such term is used for purposes of Section 409A of the Code), whether such separation from service results from the Participant’s Normal Retirement, Termination by the Corporation or an Affiliate without Cause or otherwise. The Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed pursuant to Section 7.2 of the Plan, together with Shares comprising all accrued Dividend Equivalents with respect to such Restricted Stock Units, shall be delivered by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days following the applicable Lapse Date set forth in the Grant Notice; provided, however, that (i) if the Participant dies or incurs a Disability prior to any such Lapse Date, the related payment shall be made to the Participant as soon as reasonably practicable following (and in any event within [30] days after) the date of the Participant’s death or Disability, or (ii) if the Participant’s separation from service occurs prior to such Lapse Date, the related payment shall be made upon the next Normal Distribution Date following the first anniversary of the Participant’s separation from service. For purposes of this Section 6, if such payment date is a day on which the New York Stock Exchange is not open for trading, the payment date shall be the next day on which such exchange is open for trading. Notwithstanding the foregoing provisions of this Section 6, the Administrator may provide for payment of any Shares underlying the Restricted Stock Units for which the Period of Restriction has lapsed in accordance with the requirements of Treasury Regulation 1.409A-3(j)(4)(ix)(A), (B) or (C) promulgated under Section 409A of the Code (or any similar successor provision), which regulation generally provides that a deferred compensation arrangement may be terminated in limited circumstances following a dissolution or change in control of the Corporation. The Participant shall have no rights to receive delivery of any Shares with respect to Restricted Stock Units that have been forfeited or cancelled, or for which Shares have previously been delivered. No fractional Shares shall be delivered, and the Shares otherwise deliverable in any payment pursuant to this Section 6 shall be rounded down to the nearest whole number of Shares.
7. No Ownership Rights Prior to Issuance of Shares .
Neither the Participant nor any other person shall become the beneficial owner of the Shares underlying the Restricted Stock Units, nor have any rights to dividends (other than rights to Dividend Equivalents pursuant to Section 3) or other rights as a shareholder with respect to any such Shares, until and after such Shares have been actually issued to the Participant and transferred on the books and records of the Corporation or its agent in accordance with the terms of the Plan and this Agreement.
8. Detrimental Activity .
(a)    Notwithstanding any other provisions of this Agreement to the contrary, if at any time prior to the delivery of Shares with respect to the Restricted Stock Units, the Participant engages in Detrimental Activity (as defined below), such Restricted Stock Units shall be cancelled and rescinded without any payment or consideration therefor. The determination of whether the Participant has engaged in Detrimental Activity shall be made by the Administrator in its good faith discretion, and lapse of the Period of Restriction and delivery of Shares with respect to the Restricted Stock Units shall be suspended pending resolution to the Administrator’s satisfaction of any investigation of the matter.
(b)    For purposes of this Agreement, “Detrimental Activity” means at any time (i) using information received during the Participant’s employment with the Corporation and/or its Subsidiaries, Affiliates and predecessors in interest relating to the business affairs of the Corporation or any such Subsidiaries, Affiliates or predecessors in interest, in breach of the Participant’s express or implied undertaking to keep such information confidential; (ii) directly or indirectly persuading or attempting to persuade, by any means, any employee of the Corporation or any of its Subsidiaries or Affiliates to breach any of the terms of his or her employment with Corporation, its Subsidiaries or its Affiliates; (iii) directly or indirectly making any





statement that is, or could be, disparaging of the Corporation or any of its Subsidiaries or Affiliates, or any of their respective employees (except to the extent necessary to respond truthfully to any inquiry from applicable regulatory authorities or to provide information pursuant to legal process); (iv) directly or indirectly engaging in any illegal, unethical or otherwise wrongful activity that is, or could be, substantially injurious to the financial condition, reputation or goodwill of the Corporation or any of its Subsidiaries or Affiliates; or (v) directly or indirectly engaging in an act of misconduct such as, embezzlement, fraud, dishonesty, nonpayment of any obligation owed to the Corporation or any of its Subsidiaries or Affiliates, breach of fiduciary duty or disregard or violation of rules, policies or procedures of the Corporation or any of its Subsidiaries or Affiliates, an unauthorized disclosure of any trade secret or confidential information of the Corporation or any of its Subsidiaries or Affiliates, any conduct constituting unfair competition, or inducing any customer to breach a contract with the Corporation or any of its Subsidiaries or Affiliates, in each case as determined by the Administrator in its good faith discretion.
(c)    Nothing in this Agreement prohibits Participant from reporting possible violations of federal law or regulation to any governmental agency or entity, or making other disclosures that are protected under the whistleblower provisions of federal law or regulation. Participant does not need any prior authorization to make any such reports or disclosures and is not required to notify the Corporation of such reports or disclosures.
9. No Right to Continued Employment .
None of the Restricted Stock Units nor any terms contained in this Agreement shall confer upon the Participant any express or implied right to be retained in the employ of the Corporation or any Subsidiary or Affiliate for any period, nor restrict in any way the right of the Corporation or any Subsidiary or any Affiliate, which right is hereby expressly reserved, to terminate the Participant’s employment at any time for any reason. For the avoidance of doubt, this Section 9 is not intended to amend or modify any other agreement, including any employment agreement, that may be in existence between the Participant and the Corporation or any Subsidiary or Affiliate.
10.
No Right to Compensation
Participation in the Plan and the receipt of an award of Restricted Stock Units pursuant to this Agreement shall be on the express condition that ceasing to participate in the Plan and/or the loss of Restricted Stock Units on termination of employment (whatever the circumstances of the termination, including, but not limited to, wrongful dismissal) shall not afford the Participant any right to compensation or damages under the terms of the Participant’s employment or of any express or implied contract relating to the Plan or any award. By accepting an award the Participant agrees that this Section 10 shall apply in relation to any claim the Participant may have against any company which employs or has employed the Participant and any officer or employee thereof as well as against the Corporation and its officers and employees and this Section 10 is enforceable by such persons in their own right.
11.
The Plan
In consideration for this grant, the Participant agrees to comply with the terms of the Plan and this Agreement. This Agreement is subject to all the terms, provisions and conditions of the Plan, which are incorporated herein by reference, and to such regulations as may from time to time be adopted by the Administrator. In the event of any conflict between the provisions of the Plan and this Agreement, the provisions of the Plan shall control, and this Agreement shall be deemed to be modified accordingly, provided that the provisions of Section 6 (Delivery of Shares) of this Agreement shall control over any conflicting payment provisions of the Plan. The Plan and the prospectus describing the Plan can be found on Fidelity NetBenefits® at www.netbenefits.com under Plan Information and Documents. A paper copy of the Plan and the prospectus shall be provided to the Participant upon the Participant’s written request to the Corporation at CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify.
12.
Compliance with Laws and Regulations.
(a)    The Restricted Stock Units and the obligation of the Corporation to sell and deliver Shares hereunder shall be subject in all respects to (i) all applicable Federal and state laws, rules and regulations and (ii) any registration, qualification, approvals or other requirements imposed by any government or regulatory agency or body which the Administrator shall, in its discretion, determine to be necessary or applicable. Moreover, the Corporation shall not deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement if doing so would be contrary to applicable law. If at any time the Corporation determines, in its discretion, that the listing, registration or qualification of Shares upon any national securities exchange or under any state or Federal law, or the consent or approval of any governmental regulatory body, is necessary or desirable, the Corporation shall not be required to deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement unless and until such listing, registration, qualification, consent or approval has been effected or obtained, or otherwise provided for, free of any conditions not acceptable to the Corporation.
(b)    It is intended that the Shares received in respect of the Restricted Stock Units shall have been registered under the Securities Act. If the Participant is an “affiliate” of the Corporation, as that term is defined in Rule 144 under





the Securities Act (“Rule 144”), the Participant may not sell the Shares received except in compliance with Rule 144. Certificates representing Shares issued to an “affiliate” of the Corporation may bear a legend setting forth such restrictions on the disposition or transfer of the Shares as the Corporation deems appropriate to comply with Federal and state securities laws.
(c)    If, at any time, the Shares are not registered under the Securities Act, and/or there is no current prospectus in effect under the Securities Act with respect to the Shares, the Participant shall execute, prior to the delivery of any Shares to the Participant by the Corporation pursuant to this Agreement, an agreement (in such form as the Corporation may specify) in which the Participant represents and warrants that the Participant is purchasing or acquiring the Shares acquired under this Agreement for the Participant's own account, for investment only and not with a view to the resale or distribution thereof, and represents and agrees that any subsequent offer for sale or distribution of any kind of such Shares shall be made only pursuant to either (i) a registration statement on an appropriate form under the Securities Act, which registration statement has become effective and is current with regard to the Shares being offered or sold, or (ii) a specific exemption from the registration requirements of the Securities Act, but in claiming such exemption the Participant shall, prior to any offer for sale of such Shares, obtain a prior favorable written opinion, in form and substance satisfactory to the Corporation, from counsel for or approved by the Corporation, as to the applicability of such exemption thereto.
(d)    The Corporation and/or the company which employs the Participant will, for the purposes of operating the Plan and implementing this Agreement, collect, retain and process information relating to the Participant in accordance with the CoreLogic Solutions: EU Employee Privacy Notice which is to be found at [specify where available].
13. Notices .
All notices by the Participant or the Participant’s assignees shall be addressed to CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify. All notices to the Participant shall be addressed to the Participant at the Participant’s address in the Corporation's records.
14. Severability .
In the event any provision of this Agreement shall be held illegal or invalid for any reason, the illegality or invalidity shall not affect the remaining parts of this Agreement, and this Agreement shall be construed and enforced as if the illegal or invalid provision had not been included.
15. Other Plans .
The Participant acknowledges that any income derived from the Restricted Stock Units shall not affect the Participant’s participation in, or benefits under, any other benefit plan or other contract or arrangement maintained by the Corporation or any Subsidiary or Affiliate. Restricted Stock Units and Dividend Equivalents shall not be deemed to be “Covered Compensation” under any other benefit plan of the Corporation.
16.
Adjustments .
The Restricted Stock Units and the Shares underlying the Restricted Stock Units shall be subject to adjustment and conversion pursuant to the terms of Section 7.1 of the Plan.
17.
Tax Withholding .
Any payment or delivery of Shares pursuant to this Agreement shall be subject to the rights of the Corporation and of any other company by which the Participant is employed to withhold applicable Federal, state, local and non-United States taxes and UK national insurance contributions in accordance with Section 8.5 of the Plan. As a condition of participating in the Plan, the Participant agrees to indemnify the Corporation and/or the company by which the Participant is employed for any amount which it is obliged but unable to withhold.
18.
UK Tax Election
The Participant irrevocably undertakes to enter into a joint election under section 431 of the UK Income Tax (Earnings and Pensions) Act 2003 in respect of any Shares delivered pursuant to this Agreement if required to do so by the Corporation or by the company by which the Participant was or is employed on or before or within 14 days after the Lapse Date relating to such Shares
19.
Section 409A.
The provisions of this Agreement shall be construed and interpreted to comply with Section 409A of the Code so as to avoid the imposition of any penalties, taxes or interest thereunder. Clawback.





The Restricted Stock Units are subject to the terms of the Corporation’s recoupment, clawback or similar policy as it may be in effect from time to time, as well as any similar provisions of applicable law, any of which could in certain circumstances require repayment or forfeiture of the Restricted Stock Units or any Shares or other cash or property received with respect to the Restricted Stock Units (including any value received from a disposition of the Shares acquired upon payment of the Restricted Stock Units).
CORELOGIC, INC.

    
By:_______________________________
                            Name: Frank Martell
Title: President and Chief Executive Officer
Date: [Grant Date]

Acknowledged and agreed as of the Date of Grant:



Printed Name:     [Participant Name]
Date:     [Acceptance Date]


NOTE: GRANT WILL BE ACCEPTED ELECTRONICALLY








APPENDIX A

Certain Definitions

Affiliate ” means any entity other than the Corporation and any Subsidiary that is affiliated with the Corporation through stock or equity ownership or otherwise and is designated as an Affiliate for purposes of the Plan by the Administrator.


Cause ” has the same meaning as in the Participant’s employment agreement with the Corporation, a Subsidiary or an Affiliate (if any) as in effect at the time of the Participant’s Termination, or if the Participant is not a party to such an employment agreement (or is not a party to such an employment agreement that contains a definition of “cause”), “Cause” means: (i) embezzlement, theft or misappropriation by the Participant of any property of any of the Corporation or its Affiliates; (ii) the Participant’s breach of any fiduciary duty to the Corporation or its Affiliates; (iii) the Participant’s failure or refusal to comply with laws or regulations applicable to the Corporation or its Affiliates and their businesses or the policies of the Corporation and its Affiliates governing the conduct of its employees or directors; (iv) the Participant’s gross incompetence in the performance of the Participant’s job duties; (v) commission by the Participant of a felony or of any crime involving moral turpitude, fraud or misrepresentation; (vi) the failure of the Participant to perform duties consistent with a commercially reasonable standard of care; (vii) the Participant’s failure or refusal to perform the Participant’s job duties or to perform specific directives of the Participant’s supervisor or designee, or the senior officers or Board of Directors of the Corporation; or (viii) any gross negligence or willful misconduct of the Participant resulting in loss to the Corporation or its Affiliates, or damage to the reputation of the Corporation or its Affiliates.
Change in Control ” means the happening of any of the following after the date hereof:

(a)
The consummation of a merger or consolidation of the Corporation with or into another entity or any other corporate reorganization, if fifty percent (50%) or more of the combined voting power of the continuing or surviving entity’s securities outstanding immediately after such merger, consolidation, or other reorganization is owned by persons who were not shareholders of the Corporation immediately prior to such merger, consolidation, or other reorganization.
(b)
The sale, transfer, or other disposition of all or substantially all of the Corporation’s assets or the complete liquidation or dissolution of the Corporation.
(c)
A change in the composition of the Board occurring within a two (2) year period, as a result of which fewer than a majority of the directors are Incumbent Directors. “ Incumbent Directors ” shall mean directors who are directors of the Corporation immediately following the consummation of the transactions contemplated by the Separation and Distribution Agreement by and between the Corporation and the First American Financial Corporation dated June 1, 2010 (the “ Separation Agreement ”). “ Incumbent Directors ” shall also include directors who are elected, or nominated for election, to the Board with the affirmative votes of at least a majority of the Incumbent Directors at the time of such election or nomination, but shall not include an individual not otherwise an Incumbent Director whose election or nomination is in connection with an actual or threatened proxy contest relating to the election of directors to the Corporation.
(d)
Any transaction as a result of which any person or group is or becomes the “ beneficial owner ” (as defined in Rule 13d-3 under the Securities Exchange Act of 1934), directly or indirectly, of securities of the Corporation representing at least thirty percent (30%) of the total voting power of the Corporation’s then outstanding voting securities. For purposes of this paragraph, the term “ person ” shall have the same meaning as when used in Sections 13(d) and 14(d) of the Securities Exchange Act of 1934, but shall exclude: (i) a trustee or other fiduciary holding securities under an employee benefit plan of the Corporation or of a Subsidiary of the Corporation; (ii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person whose beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities increases to thirty percent (30%) or more as a result of the acquisition of voting securities of the Corporation by the Corporation which reduces the number of such voting securities then outstanding; or (iii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person that acquires directly from the Corporation securities of the Corporation representing at least thirty percent (30%) of the total voting power represented by the Corporation’s then outstanding voting securities.
A transaction shall not constitute a Change in Control if its sole purpose is to change the state of the Corporation’s incorporation or to create a holding company that will be owned in substantially the same proportions by the persons who held the Corporation’s securities immediately before such transaction.





For the avoidance of doubt, the consummation of any or all of the transactions in the Separation Agreement is not considered a Change in Control for purposes of this Agreement.
“Disability” means the inability to engage in any substantial gainful occupation to which the relevant individual is suited by education, training or experience, by reason of any medically determinable physical or mental impairment, which condition can be expected to result in death or continues for a continuous period of not less than twelve (12) months.
Normal Distribution Date ” means either March 20, June 20, September 20 or December 20, as applicable; provided that if such date is a day on which the New York Stock Exchange is not open for trading, the Normal Distribution Date shall be the next day on which such exchange is open for trading.
Termination ” means the time when the Participant ceases the performance of services for the Corporation, any Affiliate or Subsidiary, as applicable, for any reason, with or without Cause, including a Termination by resignation, discharge, retirement, death or Disability, but excluding (a) a Termination where there is a simultaneous reemployment or continuing employment of the Participant by the Corporation, any Affiliate or Subsidiary, (b) at the discretion of the Administrator, a Termination that results in a temporary severance, and (c) at the discretion of the Administrator, a Termination of an employee of the Corporation that is immediately followed by the Participant’s service as a non-employee director of the Board.  Notwithstanding any other provisions of the Plan or this Agreement to the contrary, a Termination shall not be deemed to have occurred for purposes of any provision the Plan or this Agreement providing for payment or distribution with respect to an award constituting deferred compensation subject to Code Section 409A upon or following a termination of employment or services unless such termination is also a “separation from service” within the meaning of Section 409A of the Code.










Notice of Performance-Based Restricted Stock Unit Grant

Participant:          [Participant Name]
Corporation:         CoreLogic, Inc.
Notice:
You have been granted the following Performance-Based Restricted Stock Units (“Performance-Based RSUs”) in accordance with the terms of the Plan and the Performance-Based Restricted Stock Unit Award Agreement attached hereto.
Type of Award:
Performance-Based RSUs
Plan:
CoreLogic, Inc. 2018 Performance Incentive Plan
Grant:             Date of Grant:   [Grant Date]
Target Number of Performance-Based RSUs:   [Number of RSUs Granted]

Vesting:
Subject to the terms of the Plan and this Agreement, the vesting and payment of the Performance-Based RSUs shall be subject to (1) the attainment of the Performance Measures set forth below, and (2) to the extent the Performance Measures are attained, an additional time-based vesting requirement set forth below. The time-based vesting requirements set forth below require the Participant’s continued employment or service through each applicable vesting date as a condition to the vesting of any of the Shares underlying the Performance-Based RSUs. Except as provided in Sections 4 and 5 of this Agreement, employment or service for only a portion of the vesting period, even if a substantial portion, will not entitle the Participant to any proportionate vesting or avoid or mitigate a termination of rights and benefits upon or following a termination of employment or services as provided in Section 4 below or under the Plan.

Measurement Period:
The performance period for the Performance-Based RSUs shall commence on January 1, 2018 and end on December 31, 2020 (the “Performance Period”). Each of the three calendar years occurring in the Performance Period is referred to as a “Performance Year.”
Performance Measures:
The Performance-Based RSUs shall be subject to a series of performance evaluations for Adjusted EPS and Relative Total Shareholder Return (TSR) (the “Performance Measures”). For each Performance Year, the number of Performance-Based RSUs that can potentially be vested (i.e., credited) is evaluated based on the Corporation’s Adjusted EPS performance (as such term is defined below and as reflected in Table 1 below), and may then be subject to potential modification based upon Relative TSR Modifier results (as such term is defined below). In addition to the evaluation in each respective Performance Year, the cumulative Adjusted EPS results for the 3-year Performance Period, before a potential Relative TSR Modifier, will be evaluated (see Table 1 below).

TABLE 1
Adjusted EPS for Performance Year or Full 3- Year Performance Period
Percentage of Units Corresponding to that Year or Period to be Credited (before Relative TSR Modifier)
Less Than Threshold
0%
Threshold
50%
Target
100%
Maximum or greater
200%

Linear Interpolation. If Adjusted EPS for the applicable Performance Year or Performance Period is greater than the Threshold goal and less than the Target goal, or greater than the Target goal but less than the Maximum goal, the percentage of units corresponding to the applicable measurement period to be credited will be determined by linear interpolation between the corresponding points in Table 1 above.






The Adjusted EPS goals are set forth in Table 2 for each Performance Year and for the cumulative 3-year Performance Period. The percentage of the Performance-Based RSUs that will be credited based on the Adjusted EPS results in any given Performance Year, prior to a Relative TSR Modifier and subject to the provisions of this Agreement, shall be determined as set forth in Table 2.

TABLE 2
Performance Year
Threshold Adjusted EPS
(“Threshold”)
Adjusted EPS (“Target”)
Maximum Adjusted EPS
(“Maximum”)
Percentage of Target Performance-Based RSUs Potentially Credited (before Relative TSR Modifier)
2018
 
 
 
30%
2019
 
 
 
50%
2020
 
 
 
20%
Cumulative
 
 
 
100%

Relative TSR Modifier . The Performance-Based RSUs to be credited from Adjusted EPS results for any Performance Year or the full 3-year Performance Period are subject to a potential Relative TSR Modifier. The Relative TSR performance will be evaluated for each Performance Year and the full 3-year Performance Period as a percentile ranking of CoreLogic versus the Corporation Peer Group (as defined below). If Adjusted EPS for the Performance Year, or the full 3-year Performance Period, is at or greater than the 110% of Target goal but the Corporation’s Relative TSR Percentile for that Performance Year or respective Performance Period is less than the 55 th percentile, the percentage of units to be credited is 150% of target (rather than the higher percentage up to 200% calculated based on Adjusted EPS results and the linear interpolation described above). If Adjusted EPS for the Performance Year or respective Performance Period is lower than the Threshold goal but the Corporation’s Relative TSR Percentile for that Performance Year or Performance Period is above median (i.e., in the top two quartiles), the percentage of units corresponding to that time period to be credited is 50% of target (rather than 0% as would have been credited based on Adjusted EPS results alone). If Adjusted EPS for a Performance Year or the full 3-year Performance Period is at or greater than the applicable Threshold goal but less than 110% of the Target goal, no Relative TSR modifications will be applied to the credited Performance-Based RSUs. See Table 3 below for further illustration.

TABLE 3
Adjusted EPS Performance by Performance Year or Performance Period
Percentage of Units Credited
(before Relative TSR Modifier)
Relative TSR Modifier Treatment
Greater than 110% of Target performance
Greater than 150% of Target award (capped at 200%)
Decrease percentage of units credited to 150% of Target award if Relative TSR is less than the 55 th  percentile
100% of Target performance to 110% of Target performance
100% of Target award to 150% of Target award
No modifier
Threshold performance to 100% of Target performance
50% of Target award to 100% of Target award
No modifier
Less than Threshold performance
0% of Target award
Increase percentage of units credited to 50% of Target award if Relative TSR is greater than median
Cumulative . No awards will be payable until the end of the Performance Period. At the end of the Performance Period, the number of Performance-Based RSUs that will vest will be the greater of (1) the sum of the number of units credited pursuant to Table 1 for each of the three Performance Years, and giving effect to the Relative TSR modifier for each such Performance Year discussed above (if applicable), or (2) the number of units credited pursuant to the cumulative performance for the full 3-year Performance Period, and giving effect to the Relative TSR modifier discussed above (if applicable).





Any units that have been credited pursuant to the foregoing provisions shall be subject to the time-based vesting requirement through the end of the three-year Performance Period.
Adjustments . The Administrator shall equitably and proportionately adjust Adjusted EPS or the Adjusted EPS goals set forth above, as the case may be, to preserve the intended incentives of Performance-Based RSUs and exclude or mitigate the impact of, as the case may be, the following: (a) amortization related to acquired intangibles, (b) asset write-downs, (c) litigation or claim judgments or settlements, (d) the effect of changes in tax laws, accounting principles, or other laws or provisions affecting reported results, (e) any transformation, reorganization and restructuring program effects, (f) extraordinary, unusual and/or nonrecurring items of gain or loss, (g) foreign exchange gains and losses, (h) the effects of a stock dividend, stock split or reverse stock split (i) mergers, acquisitions, and dispositions.
Forfeiture:
Any Performance-Based RSUs that have not been credited either with respect to the individual Performance Years or the cumulative Performance Period shall be immediately forfeited effective as of the end of the Performance Period.
Time-Based Vesting :
Any Performance-Based RSUs that have become eligible for time-based vesting following the end of the applicable Performance Year based on performance as described above will be subject to the time-based vesting requirement described herein. Except as provided in Section 4 or Section 5 of this Agreement, in order to vest in and receive payment of any Shares underlying the Performance-Based RSUs which have become eligible for time-based vesting based on the attainment of the performance requirements set forth above, the Participant must remain continuously employed through, and not have experienced a Termination prior to December 31, 2020. In no event, except as provided in Section 4 or Section 5 of the Performance-Based Restricted Stock Unit Award Agreement attached hereto, shall any Performance-Based RSUs be considered to have been earned unless and until such continued employment requirement is satisfied. Any Performance-Based RSUs which have not previously vested and become payable as a result of the foregoing time-based vesting requirement (and which were not previously forfeited) shall be immediately forfeited on the date of the Participant’s Termination.
Rejection:
If you wish to accept this Performance-Based RSU Award, please access Fidelity NetBenefits® at www.netbenefits.com and follow the steps outlined under the "Accept Grant" link at any time within forty-five (45) days after the Date of Grant. If you do not accept your grant via Fidelity NetBenefits® within forty-five (45) days after the Date of Grant, you will have rejected this Performance-Based RSU Award.






Performance-Based Restricted Stock Unit Award Agreement - 2018
This Performance-Based Restricted Stock Unit Award Agreement (this “Agreement”), dated as of the Date of Grant set forth in the Notice of Performance-Based Restricted Stock Unit Grant attached hereto (the “Grant Notice”), is made between CoreLogic, Inc. (the “Corporation”) and the Participant set forth in the Grant Notice. The Grant Notice is included in and made part of this Agreement.
1.
Definitions .
Certain capitalized terms are defined in the Grant Notice, herein or in the attached Appendix A. Capitalized terms used but not defined in the Grant Notice, herein or in the attached Appendix A have the meaning assigned to such terms in the Plan.
2.
Grant of the Performance-Based RSUs .
Subject to the provisions of this Agreement and the provisions of the Plan, the Corporation hereby grants to the Participant, pursuant to the Plan, a right to receive the number of shares of Common Stock (“Shares”) set forth in the Grant Notice (the “Performance-Based RSUs”).
3.
Dividend Equivalents .
Each Performance-Based RSU shall accrue Dividend Equivalents (as defined below) with respect to dividends that would otherwise be paid on the Share underlying such Performance-Based RSU during the period from the Grant Date to the earlier of the date such Share is paid in accordance with this Agreement or the date the Share is forfeited pursuant to the terms of this Agreement. As of any date in this period that the Corporation pays an ordinary cash dividend on its Common Stock, the Corporation shall credit the Participant with an additional number of Performance-Based RSUs equal to (i) the per share cash dividend paid by the Corporation on its Common Stock on such date, multiplied by (ii) the total number of Performance-Based RSUs subject to the award as of the related dividend payment record date (including any Dividend Equivalents previously credited hereunder), divided by (iii) the fair market value (as determined in accordance with the terms of the Plan) of a share of Common Stock on the date of payment of such dividend. Any Performance-Based RSUs credited pursuant to the foregoing provisions of this Section 3 shall be subject to the attainment of the same Performance Measures and time-based vesting requirements applicable to the original Performance-Based RSUs to which they relate, and shall otherwise be subject to the same vesting, payment, delivery and other terms, conditions and restrictions as the original Performance-Based RSUs to which they relate. Any such crediting of Dividend Equivalents shall be conclusively determined by the Administrator. No crediting of Performance-Based RSUs shall be made pursuant to this Section 3 with respect to any Performance-Based RSUs which, as of such record date, have either been delivered or terminated pursuant to the Plan or this Agreement. For purposes of this Agreement, “Dividend Equivalents” means the equivalent value (in cash or Shares) of dividends that would otherwise be paid on the Shares subject to the Performance-Based RSUs but that have not been issued or delivered.
4.
Vesting and Payment; Termination .
(a)    The Performance-Based RSUs shall vest and become payable subject to the attainment of the Performance Measures and time-based vesting requirements as set forth in the Grant Notice. Subject to the terms of the Plan, the remaining provisions of this Section 4 and Section 5, all Performance-Based RSUs which have not become vested and payable prior to the date of the Participant’s Termination shall be immediately forfeited.
(b)    Notwithstanding the foregoing Section 4(a) to the contrary, in the event of the Participant’s Termination due to his or her death, Disability or, except as provided in Section 5(d), Normal Retirement, in each case during the Performance Period and prior to the Shares underlying the Performance-Based RSUs becoming vested and payable, then the Shares underlying the Performance-Based RSUs shall remain outstanding and shall be eligible to become vested and payable on a prorated basis such that the number of such Shares that shall become vested and payable as of the conclusion of the Performance Period shall equal (i) the number of such Shares that would have vested as of the conclusion of the Performance Period based on the attainment of the Performance Measures set forth in the Grant Notice or that would have vested in connection with a change of control or other corporate transaction as provided in Section 5(a) (assuming no termination of employment had occurred), multiplied by (ii) a fraction, the numerator of which shall be the sum of the number of whole months during the Performance Period the Participant was employed by the Corporation or one of its Affiliates (as defined in Appendix A attached hereto), and the denominator of which shall be thirty-six months.
(c)    Notwithstanding the foregoing Section 4(a) to the contrary, in the event of the Participant’s Termination due to his or her death, Disability or Normal Retirement, in each case following the end of the Performance Period and prior to the Shares underlying the Performance-Based RSUs becoming payable, then any Shares underlying the outstanding Performance-Based RSUs that have become eligible for vesting following the end of the Performance Period based on the Corporation’s performance shall become payable.





(d)    Any such Shares that become vested and payable pursuant to this Section 4 shall be paid (together with Shares comprising all accrued Dividend Equivalents with respect to such Shares) to the Participant at the time as specified in Section 6. The vesting and payment provided for in this Section 4 in connection with a Termination due to the Participant’s Disability or Normal Retirement is subject to the condition that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
(e)    For purposes of this Agreement, “Normal Retirement” means Termination of the Participant, other than for Cause (as defined in Appendix A attached hereto), after the Participant has reached 62 years of age.
5.
Change in Control .
(a)    In the event during the Performance Period of a corporate transaction described in 7.2 of the Plan (which generally includes transactions that the Corporation does not survive or does not survive as a public company in respect of its Common Stock) in which the Administrator does not make a provision for the substitution, assumption, exchange or other continuation or settlement of the Performance-Based RSUs or (unless the Administrator has provided for the termination of the award) the award would otherwise not continue in accordance with its terms in the circumstances, the Performance Period shall be shortened so that the Performance Year then in effect as well as the Performance Period terminate prior to such transaction as determined by the Administrator (any such shortened Performance Period, the “Shortened Performance Period”). The Adjusted EPS performance levels shall be pro-rated based on the portion of the applicable period completed through the end of such Shortened Performance Period. For purposes of any Performance Year that had not commenced as of the end of such Shortened Performance Period, for purposes of determining the crediting of units, the number of units deemed credited with respect to any such Performance Year shall equal the same percentage of units credited (or deemed credited, as the case may be) in the immediately preceding Performance Year. Notwithstanding any continued employment or service requirement or time-based vesting requirement following the end of the Shortened Performance Period in the Plan or this Agreement to the contrary, the Participant shall be entitled to vesting and payment of the number of Shares subject to the Performance-Based RSUs (or the equivalent fair market value thereof, as determined by the Administrator, in cash) equal to the greater of (a) 100% of the total number of Performance-Based RSUs set forth in the Grant Notice or (b) the number of Performance-Based RSUs that would have become eligible for time-based vesting in accordance with the terms hereof based on the Corporation’s actual performance for the Shortened Performance Period as determined using the Performance Measures set forth in the Grant Notice as modified by this Section 5(a) (assuming that such performance levels had been achieved for the entire Performance Period).
(b)    In the event of a corporate transaction described in 7.2 of the Plan following the end of the Performance Period, the provisions of Section 7.2 of the Plan shall apply to any Shares underlying the outstanding Performance-Based RSUs that have become eligible for vesting following the end of the Performance Period based on the Corporation’s performance.
(c)    Shares (or the equivalent fair market value thereof, as determined by the Administrator, in cash) underlying the Performance-Based RSUs that become vested and payable in connection with a transaction as described above in Section 5(a) or 5(b) shall be paid (together with any Shares comprising all accrued Dividend Equivalents with respect to such Shares) to the Participant at the time as specified in Section 6. Any Shares underlying Performance-Based RSUs that have been forfeited prior to the date of a transaction as described above in Section 5(a) or 5(b) shall not be eligible to become vested or payable in connection with any such transaction.
(d)    In the event the Participant is Terminated by the Corporation or an Affiliate (including any successor to such entity) without Cause during the Performance Period upon or at any time following a Change in Control and prior to the payment or other forfeiture of the Performance-Based RSUs, then the Shares underlying the Performance-Based RSUs shall remain outstanding such that the number of such Shares that shall become vested and payable as of the conclusion of the Performance Period shall equal the greater of (a) 100% of the total number of Performance-Based RSUs set forth in the Grant Notice or (b) the number of Performance-Based RSUs that would have become eligible for vesting in accordance with the terms hereof based on the Corporation’s actual performance for the Performance Period as determined using the Performance Measures set forth in the Grant Notice (assuming no termination of employment had occurred). In the event that the Participant would otherwise be entitled to accelerated vesting of the Performance-Based RSUs in connection with his or her Termination under both Section 4(b) and this Section 5(d), the provisions of this Section 5(d) will apply, and the Participant will not be entitled to any accelerated vesting under Section 4(b) with respect to such Termination.
(e)    In the event the Participant is Terminated by the Corporation or an Affiliate (including any successor to such entity) without Cause following the end of the Performance Period upon or at any time during the twelve-month period following a Change in Control and prior to the payment or other forfeiture of the Performance-Based RSUs, then any Shares underlying the outstanding Performance-Based RSUs that have become eligible for vesting following the end of the Performance Period based on the Corporation’s performance shall become vested and payable.





(f)    Any Shares underlying the Performance-Based RSUs that become vested and payable pursuant to this Section 5 shall be paid (together with any Shares comprising all accrued Dividend Equivalents with respect to such Shares) as provided in Section 6. Any Shares underlying Performance-Based RSUs that have been forfeited prior to the date of the Termination without Cause as described above shall not be eligible to become vested or payable in connection with any such Termination. The vesting and payment provided for in this Section 5 in connection with the Participant’s Termination without Cause is subject to the condition that the Participant shall have signed a separation agreement in the form established by the Corporation within 21 days (or such longer period of time required by applicable law) following his or her Termination and such separation agreement is not subsequently revoked.
6.
Payment of Shares .
(a)    The Adjusted EPS goals, as well as the TSR Percentile, shall be Business Criteria under the Plan, and shall be subject to all of the terms of the Plan applicable to Performance-Based Awards including the requirement for Administrator determination of the attainment or non-attainment of the performance goals. The Administrator’s determination of performance, and the number of units credited based on performance and eligible to vest, will be final and binding.
(b)    The Shares underlying the Performance-Based RSUs which have become vested and payable at the end of the Performance Period according to the vesting schedule set forth in the Grant Notice, together with Shares comprising all accrued Dividend Equivalents with respect to such Shares, shall be paid by the Corporation to the Participant as soon as reasonably practicable in the year following the year in which the Performance Period ends, but in no event later than 74 days, following the end of the year in which the Performance Period set forth in the Grant Notice ends. The Shares underlying the Performance-Based RSUs which have become vested and payable in connection with a qualifying Termination occurring during the Performance Period pursuant to Section 4(b) or Section 5(d) of this Agreement, together with Shares comprising all accrued Dividend Equivalents with respect to such Shares, shall be paid by the Corporation to the Participant as soon as reasonably practicable in the year following the year in which the Performance Period ends, but in no event later than 74 days, following the end of the year in which the Performance Period set forth in the Grant Notice ends. The Shares underlying the Performance-Based RSUs which have become vested and payable in connection with a qualifying Termination occurring following the end of the Performance Period pursuant to Section 4(c) or Section 5(e) of this Agreement, together with Shares comprising all accrued Dividend Equivalents with respect to such Shares, shall be paid by the Corporation to the Participant as soon as reasonably practicable, but in no event later than 74 days, following the date of the Participant’s death or Disability or the date of the Participant’s “separation from service” (as such term is used for purposes of Section 409A of the Code). The Shares underlying the Performance-Based RSUs which have become vested and payable as a result of a transaction described in 7.2 of the Plan pursuant to Section 5(a) or Section 5(b), together with Shares comprising all accrued Dividend Equivalents with respect to such Shares, shall be paid by the Corporation to the Participant as soon as reasonably practicable in the year following the year in which the Performance Period ends, but in no event later than 74 days, following the end of the year in which the Performance Period set forth in the Grant Notice ends, provided, however, that (A) if the Participant dies, incurs a Disability or has a separation from service during the Performance Period, the related payment shall be made to the Participant as soon as reasonably practicable in the year following the year in which the Performance Period ends, but in no event later than 74 days, following the end of the year in which the Performance Period set forth in the Grant Notice ends, or (B) if the Participant dies, incurs a Disability or has a separation from service following the end of the Performance Period, the related payment shall be made to the Participant as soon as reasonably practicable, but in no event later than 74 days, following the date of the Participant’s death or Disability or the date of the Participant’s separation from service. Notwithstanding the foregoing provisions of this Section 6, the Administrator may provide for payment of any Shares underlying the Performance-Based RSUs which have become vested and payable in accordance with the requirements of Treasury Regulation 1.409A-3(j)(4)(ix)(A), (B) or (C) promulgated under Section 409A of the Code (or any similar successor provision), which regulation generally provides that a deferred compensation arrangement may be terminated in limited circumstances following a dissolution or change in control of the Corporation. In the event that the specified period for any payment provided for in this Section 6 spans two calendar years and the payment is subject to the condition that the Participant have signed and not revoked a separation agreement, the payment shall be made by the Corporation in the second calendar year.
(c)    Any Shares underlying the Performance-Based RSUs that have not become vested and payable following the end of the Performance Period based on the Corporation’s performance or pursuant to Section 4 or Section 5 shall be forfeited as of the last day of the Performance Period. The Participant shall have no rights to receive payment of any Shares, whether pursuant to this Section 6 or any other provision of this Agreement, with respect to Performance-Based RSUs that have been forfeited or cancelled, or for which Shares have previously been delivered. No fractional Shares shall be paid pursuant to this Section 6 or any other provision of this Agreement, and the Shares otherwise payable shall be rounded down to the nearest whole number of Shares.
7.
No Ownership Rights Prior to Issuance of Shares .
Neither the Participant nor any other person shall become the beneficial owner of the Shares underlying the Performance-Based RSUs, nor have any rights to dividends (other than rights to Dividend Equivalents pursuant to Section 3) or other rights as a stockholder with respect to any such Shares, until and after such Shares have been actually issued to the





Participant and transferred on the books and records of the Corporation or its agent in accordance with the terms of the Plan and this Agreement.
8.
Detrimental Activity .
(a) Notwithstanding any other provisions of this Agreement to the contrary, if at any time prior to the delivery of Shares with respect to the Performance-Based RSUs, the Participant engages in Detrimental Activity (as defined below), such Performance-Based RSUs shall be cancelled and rescinded without any payment or consideration therefor. The determination of whether the Participant has engaged in Detrimental Activity shall be made by the Administrator in its good faith discretion, and the payment of Shares with respect to the Performance-Based RSUs shall be suspended pending resolution to the Administrator’s satisfaction of any investigation of the matter.
(b) For purposes of this Agreement, “Detrimental Activity” means at any time (i) using information received during the Participant’s employment with the Corporation and/or its Subsidiaries, Affiliates and predecessors in interest relating to the business affairs of the Corporation or any such Subsidiaries, Affiliates or predecessors in interest, in breach of the Participant’s express or implied undertaking to keep such information confidential; (ii) directly or indirectly persuading or attempting to persuade, by any means, any employee of the Corporation or any of its Subsidiaries or Affiliates to breach any of the terms of his or her employment with Corporation, its Subsidiaries or its Affiliates; (iii) directly or indirectly making any statement that is, or could be, disparaging of the Corporation or any of its Subsidiaries or Affiliates, or any of their respective employees (except to the extent necessary to respond truthfully to any inquiry from applicable regulatory authorities or to provide information pursuant to legal process); (iv) directly or indirectly engaging in any illegal, unethical or otherwise wrongful activity that is, or could be, substantially injurious to the financial condition, reputation or goodwill of the Corporation or any of its Subsidiaries or Affiliates; or (v) directly or indirectly engaging in an act of misconduct such as, embezzlement, fraud, dishonesty, nonpayment of any obligation owed to the Corporation or any of its Subsidiaries or Affiliates, breach of fiduciary duty or disregard or violation of rules, policies or procedures of the Corporation or any of its Subsidiaries or Affiliates, an unauthorized disclosure of any trade secret or confidential information of the Corporation or any of its Subsidiaries or Affiliates, any conduct constituting unfair competition, or inducing any customer to breach a contract with the Corporation or any of its Subsidiaries or Affiliates, in each case as determined by the Administrator in its good faith discretion.
(c)    Nothing in this Agreement prohibits Participant from reporting possible violations of federal law or regulation to any governmental agency or entity, or making other disclosures that are protected under the whistleblower provisions of federal law or regulation. Participant does not need any prior authorization to make any such reports or disclosures and is not required to notify the Corporation of such reports or disclosures.
9.
No Right to Continued Employment .
None of the Performance-Based RSUs nor any terms contained in this Agreement shall confer upon the Participant any express or implied right to be retained in the employ of the Corporation or any Subsidiary or Affiliate for any period, nor restrict in any way the right of the Corporation or any Subsidiary or any Affiliate, which right is hereby expressly reserved, to terminate the Participant’s employment at any time for any reason. For the avoidance of doubt, this Section 9 is not intended to amend or modify any other agreement, including any employment agreement that may be in existence between the Participant and the Corporation or any Subsidiary or Affiliate.
10.
The Plan .
In consideration for this grant, the Participant agrees to comply with the terms of the Plan and this Agreement. This Agreement is subject to all the terms, provisions and conditions of the Plan, which are incorporated herein by reference, and to such regulations as may from time to time be adopted by the Administrator. In the event of any conflict between the provisions of the Plan and this Agreement, the provisions of the Plan shall control, and this Agreement shall be deemed to be modified accordingly, provided that the provisions of Section 4, Section 5 and Section 6 of this Agreement shall control over any conflicting payment provisions of the Plan. The Plan and the prospectus describing the Plan can be found on Fidelity NetBenefits® at www.netbenefits.com under Plan Information and Documents. A paper copy of the Plan and the prospectus shall be provided to the Participant upon the Participant’s written request to the Corporation at CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify.
11.
Compliance with Laws and Regulations .
(a)    The Performance-Based RSUs and the obligation of the Corporation to sell and deliver Shares hereunder shall be subject in all respects to (i) all applicable Federal and state laws, rules and regulations and (ii) any registration, qualification, approvals or other requirements imposed by any government or regulatory agency or body which the Administrator shall, in its discretion, determine to be necessary or applicable. Moreover, the Corporation shall not deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement if doing so would be contrary to applicable law. If at any time the Corporation determines, in its discretion, that the listing, registration or qualification of Shares upon any national securities





exchange or under any state or Federal law, or the consent or approval of any governmental regulatory body, is necessary or desirable, the Corporation shall not be required to deliver any certificates for Shares to the Participant or any other person pursuant to this Agreement unless and until such listing, registration, qualification, consent or approval has been effected or obtained, or otherwise provided for, free of any conditions not acceptable to the Corporation.
(b)    It is intended that the Shares received in respect of the Performance-Based RSUs shall have been registered under the Securities Act. If the Participant is an “affiliate” of the Corporation, as that term is defined in Rule 144 under the Securities Act (“Rule 144”), the Participant may not sell the Shares received except in compliance with Rule 144. Certificates representing Shares issued to an “affiliate” of the Corporation may bear a legend setting forth such restrictions on the disposition or transfer of the Shares as the Corporation deems appropriate to comply with Federal and state securities laws.
(c)    If, at any time, the Shares are not registered under the Securities Act, and/or there is no current prospectus in effect under the Securities Act with respect to the Shares, the Participant shall execute, prior to the delivery of any Shares to the Participant by the Corporation pursuant to this Agreement, an agreement (in such form as the Corporation may specify) in which the Participant represents and warrants that the Participant is purchasing or acquiring the Shares acquired under this Agreement for the Participant's own account, for investment only and not with a view to the resale or distribution thereof, and represents and agrees that any subsequent offer for sale or distribution of any kind of such Shares shall be made only pursuant to either (i) a registration statement on an appropriate form under the Securities Act, which registration statement has become effective and is current with regard to the Shares being offered or sold, or (ii) a specific exemption from the registration requirements of the Securities Act, but in claiming such exemption the Participant shall, prior to any offer for sale of such Shares, obtain a prior favorable written opinion, in form and substance satisfactory to the Corporation, from counsel for or approved by the Corporation, as to the applicability of such exemption thereto.
12.
Notices .
All notices by the Participant or the Participant’s assignees shall be addressed to CoreLogic, Inc., 40 Pacifica, Suite 900, Irvine, California 92618, Attention: Incentive Compensation Plan Administrator, or such other address as the Corporation may from time to time specify. All notices to the Participant shall be addressed to the Participant at the Participant’s address in the Corporation's records.
13. Severability .
In the event any provision of this Agreement shall be held illegal or invalid for any reason, the illegality or invalidity shall not affect the remaining parts of this Agreement, and this Agreement shall be construed and enforced as if the illegal or invalid provision had not been included.
14.
Other Plans .
The Participant acknowledges that any income derived from the Performance-Based RSUs shall not affect the Participant’s participation in, or benefits under, any other benefit plan or other contract or arrangement maintained by the Corporation or any Subsidiary or Affiliate. Performance-Based RSUs and Dividend Equivalents shall not be deemed to be “Covered Compensation” under any other benefit plan of the Corporation.
15.     Adjustments .
The Performance-Based RSUs and the Shares underlying the Performance-Based RSUs shall be subject to adjustment and conversion pursuant to the terms of Section 7.1 of the Plan.
16.     Tax Withholding .
Any payment or delivery of Shares pursuant to this Agreement shall be subject to the Corporation’s rights to withhold applicable Federal, state, local and non-United States taxes in accordance with Section 8.5 of the Plan.
17.     Section 409A .
The provisions of this Agreement shall be construed and interpreted to comply with Section 409A of the Code so as to avoid the imposition of any penalties, taxes or interest thereunder. Notwithstanding any provision of Section 6 of this Agreement to the contrary, if the Participant is a “specified employee” as defined in Section 409A of the Code, the Participant shall not be entitled to any payment of Shares underlying Performance-Based RSUs that are considered deferred compensation subject to the requirements of Section 409A of the Code in connection with the Participant’s separation from service until the earlier of (a) the date which is six months after the Participant’s separation from service for any reason other than the Participant’s death, or (b) the date of the Participant’s death. Any Shares underlying the Performance-Based RSUs otherwise payable to the Participant following the Participant’s separation from service that are not so paid by reason of this Section 17 shall be paid as soon as reasonably practicable (but in no event later than 74 days) after the date that is six months after the Participant’s separation from service (or, if earlier, the date of the Participant’s death). The provisions of this Section 17 shall only apply if, and to the extent, required to comply with Section 409A of the Code.





18.     Clawback .
The Performance-Based RSUs are subject to the terms of the Corporation’s recoupment, clawback or similar policy as it may be in effect from time to time, as well as any similar provisions of applicable law, any of which could in certain circumstances require repayment or forfeiture of the Performance-Based RSUs or any Shares or other cash or property received with respect to the Performance-Based RSUs (including any value received from a disposition of the Shares acquired upon payment of the Performance-Based RSUs).
CORELOGIC, INC.

    
By:______________________________
                            Name: Frank Martell
Title: President and Chief Executive Officer
Date: [Grant Date]

Acknowledged and agreed as of the Date of Grant:


Printed Name:     [Participant Name]
Date:     [Acceptance Date]

NOTE: GRANT WILL BE ACCEPTED ELECTRONICALLY







APPENDIX A

Certain Definitions

Adjusted EPS ” for a Performance Year or for the cumulative Performance Period, as applicable, means, subject to the adjustments set forth in the Grant Notice, (1) the Corporation’s adjusted pre-tax income from continuing operations for the Performance Year or cumulative Performance Period, plus the Corporation’s pre-tax equity earnings from affiliates for the Performance Year or cumulative Performance Period, tax effected at an assumed rate of 35% and determined on a consolidated basis, divided by (2) the weighted average number of shares of the Corporation’s Common Stock outstanding over the Performance Year or cumulative Performance Period, as applicable.

Affiliate ” means any entity other than the Corporation and any Subsidiary that is affiliated with the Corporation through stock or equity ownership or otherwise and is designated as an Affiliate for purposes of the Plan by the Administrator.

Beginning Price ” means, with respect to the Corporation and any other Corporation Peer Group member, the closing market price of such company’s common stock on the principal exchange on which such stock is traded on the last trading day before the beginning of the applicable measurement period (the relevant Performance Year or cumulative Performance Period). 
Cause ” has the same meaning as in the Participant’s employment agreement with the Corporation, a Subsidiary or an Affiliate (if any) as in effect at the time of the Participant’s Termination, or if the Participant is not a party to such an employment agreement (or is not a party to such an employment agreement that contains a definition of “cause”), “Cause” means: (i) embezzlement, theft or misappropriation by the Participant of any property of any of the Corporation or its Affiliates; (ii) the Participant’s breach of any fiduciary duty to the Corporation or its Affiliates; (iii) the Participant’s failure or refusal to comply with laws or regulations applicable to the Corporation or its Affiliates and their businesses or the policies of the Corporation and its Affiliates governing the conduct of its employees or directors; (iv) the Participant’s gross incompetence in the performance of the Participant’s job duties; (v) commission by the Participant of a felony or of any crime involving moral turpitude, fraud or misrepresentation; (vi) the failure of the Participant to perform duties consistent with a commercially reasonable standard of care; (vii) the Participant’s failure or refusal to perform the Participant’s job duties or to perform specific directives of the Participant’s supervisor or designee, or the senior officers or Board of Directors of the Corporation; or (viii) any gross negligence or willful misconduct of the Participant resulting in loss to the Corporation or its Affiliates, or damage to the reputation of the Corporation or its Affiliates.
Change in Control ” means the happening of any of the following after the date hereof:

(a)
The consummation of a merger or consolidation of the Corporation with or into another entity or any other corporate reorganization, if fifty percent (50%) or more of the combined voting power of the continuing or surviving entity’s securities outstanding immediately after such merger, consolidation, or other reorganization is owned by persons who were not stockholders of the Corporation immediately prior to such merger, consolidation, or other reorganization.
(b)
The sale, transfer, or other disposition of all or substantially all of the Corporation’s assets or the complete liquidation or dissolution of the Corporation.
(c)
A change in the composition of the Board occurring within a two (2) year period, as a result of which fewer than a majority of the directors are Incumbent Directors. “ Incumbent Directors ” shall mean directors who are directors of the Corporation immediately following the consummation of the transactions contemplated by the Separation and Distribution Agreement by and between the Corporation and the First American Financial Corporation dated June 1, 2010 (the “ Separation Agreement ”). “ Incumbent Directors ” shall also include directors who are elected, or nominated for election, to the Board with the affirmative votes of at least a majority of the Incumbent Directors at the time of such election or nomination, but shall not include an individual not otherwise an Incumbent Director whose election or nomination is in connection with an actual or threatened proxy contest relating to the election of directors to the Corporation.
(d)
Any transaction as a result of which any person or group is or becomes the “ beneficial owner ” (as defined in Rule 13d-3 under the Securities Exchange Act of 1934), directly or indirectly, of securities of the Corporation representing at least thirty percent (30%) of the total voting power of the Corporation’s then outstanding voting securities. For purposes of this paragraph, the term “ person ” shall have the same meaning as when used in Sections 13(d) and 14(d) of the Securities Exchange Act of 1934, but shall exclude: (i) a trustee or other fiduciary holding securities under an employee benefit plan of the Corporation or of a Subsidiary of the Corporation; (ii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person whose beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities increases to thirty percent (30%) or more as a result of the acquisition of voting securities of the Corporation





by the Corporation which reduces the number of such voting securities then outstanding; or (iii) so long as a person does not thereafter increase such person’s beneficial ownership of the total voting power represented by the Corporation’s then outstanding voting securities, a person that acquires directly from the Corporation securities of the Corporation representing at least thirty percent (30%) of the total voting power represented by the Corporation’s then outstanding voting securities.
A transaction shall not constitute a Change in Control if its sole purpose is to change the state of the Corporation’s incorporation or to create a holding company that will be owned in substantially the same proportions by the persons who held the Corporation’s securities immediately before such transaction.
For the avoidance of doubt, the consummation of any or all of the transactions in the Separation Agreement is not considered a Change in Control for purposes of this Agreement.
Corporation Peer Group ” means the Corporation and each of the following companies:
[to be conformed]

The Corporation Peer Group shall be subject to adjustment by the Administrator for changes that occur prior to the end of the Performance Year or Performance Period, as applicable, as follows: In the event of a merger or other business combination of two Corporation Peer Group members (including, without limitation, the acquisition of one Corporation Peer Group member, or all or substantially all of its assets, by another Corporation Peer Group member), the surviving, resulting or successor entity, as the case may be, shall continue to be treated as a member of the Corporation Peer Group, provided that the common stock (or similar equity security) of such entity is listed or traded on a national securities exchange as of the end of the applicable period. In the event that the common stock (or similar equity security) of a Corporation Peer Group member is otherwise not listed or traded on a national securities exchange at the end of the Performance Year or Performance Period, as applicable, such entity shall be excluded from the Corporation Peer Group.
Disability ” means the inability to engage in any substantial gainful occupation to which the relevant individual is suited by education, training or experience, by reason of any medically determinable physical or mental impairment, which condition can be expected to result in death or continues for a continuous period of not less than twelve (12) months.
Ending Price ” means, with respect to the Corporation and any other Corporation Peer Group member, the closing market price of such company’s common stock on the principal exchange on which such stock is traded at the end of the applicable measurement period. 
Termination ” means the time when the Participant ceases the performance of services for the Corporation, any Affiliate or Subsidiary, as applicable, for any reason, with or without Cause, including a Termination by resignation, discharge, retirement, death or Disability, but excluding the following if in the circumstances the Termination would not constitute a “separation from service” within the meaning of Section 409A of the Code (a) a Termination where there is a simultaneous reemployment or continuing employment of the Participant by the Corporation, any Affiliate or Subsidiary, (b) at the discretion of the Administrator, a Termination that results in a temporary severance, and (c) at the discretion of the Administrator, a Termination of an employee of the Corporation that is immediately followed by the Participant’s service as a non-employee director of the Board.  Notwithstanding any other provisions of the Plan or this Agreement to the contrary, a Termination shall not be deemed to have occurred for purposes of any provision of the Plan or this Agreement providing for payment or distribution with respect to an award constituting deferred compensation subject to Code Section 409A upon or following a termination of employment or services unless such termination is also a “separation from service” within the meaning of Section 409A of the Code.
TSR ” means total shareholder return and shall be determined with respect to the Corporation and any other Corporation Peer Group member by dividing (i) the sum of (A) the cumulative amount of dividends for the applicable measurement period, assuming dividend reinvestment, and (B) the difference between the company’s Beginning Price and Ending Price for the applicable Performance Year or Performance Period; by (ii) the company’s Beginning Price. Any non-cash distributions shall be ascribed such dollar value as may be determined by or at the direction of the Administrator.
TSR Percentile ” means the percentile ranking of the Corporation’s TSR among the TSRs for the Corporation Peer Group members for the corresponding Performance Year or Performance Period, as applicable.
  




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.




AMENDMENT NO. 5

TO THE

MASTER SERVICES AGREEMENT
And
SUPPLEMENT A

BETWEEN

CORELOGIC SOLUTIONS, LLC

AND

NTT DATA SERVICES, LLC


Amendment 5 Effective Date May 15, 2018



This document contains proprietary and confidential information of CoreLogic and NTT DATA Services. The information contained in this document may not be disclosed outside either Party without the prior written permission of the other Party.








CORELOGIC/NTT DATA SERVICES CONFIDENTIAL




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



AMENDMENT NO. 5
TO THE
MASTER SERVICES AGREEMENT
THIS AMENDMENT NO. 5 (this “ Amendment ”) is entered into as of May 15, 2018 (the “ Amendment Date ”) by and between CoreLogic Solutions LLC (“ CoreLogic ”) and NTT DATA Services, LLC (“ Supplier ”) to be effective as of May 15, 2018, (the “ Amendment Effective Date ”).
WHEREAS, CoreLogic and Supplier are parties to a MSA and Supplement A, each dated as of July 19, 2012; Amendment No. 1 to the MSA dated October 23, 2012; Amendment No. 2 to the MSA dated December 6, 2012; Amendment No. 3 to the MSA dated March 17, 2017; and Amendment No. 4 to the MSA dated October 1, 2017.
WHEREAS, CoreLogic and Supplier intend to further amend and restate the Agreement documents set forth below.
NOW THEREFORE, in consideration of the mutual promises and covenants contained in this Amendment, and of other good and valid consideration, the receipt and sufficiency of which is hereby acknowledged, CoreLogic and Supplier hereby agree as follows:
1.
APPLICABILITY OF PROVISIONS OF THE AGREEMENT
This Amendment is subject to, and shall be governed by, all of the provisions of the Agreement, except to the extent such provisions are expressly modified by this Amendment. Capitalized terms used herein shall have the respective meaning ascribed to each by the Agreement except as otherwise expressly set forth in this Amendment.
2.
NEW AND AMENDED CONTRACT DOCUMENTS
Effective as of 12:00:01 a.m., U.S. Pacific Time on the Amendment Effective Date:
3.2 Amended and Restated Contract Documents . The following contract documents are hereby stricken in their entirety and replaced, respectively with those attached to this Amendment:
Schedule A-3.1      Service Level Matrix
Updated Service Level Matrix to add Key Measure for PC refresh
Schedule A-3.2      Service Level Definitions and Measurement Methodology
Added Key Measure for PC Refresh and CSI Flags as appropriate

3.
GOVERNING LAW.

CORELOGIC/NTT DATA SERVICES CONFIDENTIAL
Amendment No. 5    Page 1

CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


This Amendment shall be governed by and construed in accordance with the terms set forth in Section 19.4 of the Agreement.
4.
HEADINGS.
The article and section headings and the table of contents used herein are for reference and convenience only and will not be considered in the interpretation of this Amendment.
5.
OTHER PROVISIONS OF THE AGREEMENT UNCHANGED.
Except as specifically amended by this Amendment, all other provisions of the Agreement shall remain in full force and effect and shall not be altered by this Amendment.
6.
SIGNATURES.
This Amendment may be signed in multiple counterparts, each of which shall be an original but all of which shall constitute one and the same Amendment. Signatures to this Amendment sent by facsimile or by PDF shall be deemed for all purposes to be the same as original signatures.
IN WITNESS WHEREOF, the Parties have caused this Amendment to be executed by their respective duly authorized representatives as of the Amendment Effective Date.
CORELOGIC SOLUTIONS, LLC            NTT DATA SERVICES, LLC
By: /s/ Kevin Tang                      By: /s/ John Evans            
Printed Name: Kevin Tang                  Printed Name: John Evans        
Title: SCVM Sr. Leader                  Title: Client Executive        

CORELOGIC/NTT DATA SERVICES CONFIDENTIAL
Amendment No. 5
2


CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.




MASTER SERVICES AGREEMENT
between
CORELOGIC SOLUTIONS, LLC
and
NTT Data Services, LLC

Supplement A

Schedule A-3.2:
Service Level Definitions and Measurement Methodology




This document contains proprietary and confidential information of CoreLogic and NTT Data. The information contained in this document may not be disclosed outside your company without the prior written permission of CoreLogic and NTT Data.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



1.
Introduction
1.
Agreement . This Schedule A-3.2 (this “ Schedule ”) is attached to and incorporated by reference in Supplement A to that certain Master Services Agreement by and between CoreLogic and Supplier dated July 19, 2012 (the “ MSA ”).
2.
References . All references in this Schedule to articles, sections and attachments shall be to this Schedule, unless another reference is provided.
3.
Definitions . Terms used in this Schedule with initial capitalized letters but not defined in this Schedule shall have the respective meanings set forth in Schedule 1 to the MSA, Schedule A-1 to Supplement A or elsewhere in the Agreement.
4.
General Service Level Exceptions . In addition to Section 10.2 and Section 4.4 (last sentence) of the MSA, any Service Levels affected by Software or Equipment listed in the known error database because the Software or Equipment is end of life or no longer vendor supported, or the version is out of currency, or for other known error or issue not caused by Supplier for which the recommended remedial action has not been approved or implemented by CoreLogic shall be an exception and excluded from the Service Level measurement.
5.
Valid Use of Pending . The following reasons are the only valid uses of pending, and must have an associated work note attached to the ticket describing the reason for the pending status.
1.
The following valid pending reasons apply to all ticket types:
a.
Waiting on CoreLogic
b.
Waiting on CoreLogic vendor
2.
The following valid pending reasons apply to incidents only:
a.
Waiting on an agreed upon scheduled change
b.
Pending approved by CoreLogic on MIM call for some other reason
c.
Time during application recovery or business validation after service or infrastructure is restored
d.
Previously unknown third party software defects



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



2.
Service Level Definitions
1.
2.2.a CSL-SM-Incident Handling - Critical
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this Service Level is to measure the time interval between an Incident creation dates for tickets with Critical Priority to the time normal service operation is restored via implementing a solution to the known error or by employing a workaround

Associated hours of Operation:

24x7

Reporting Tools:

OPAS
Exceptions:

Restoration Time does not include the following:
- Pending time allowed as indicated in section 1.6.
- If there are instances or circumstances at a non-Dell facility where equipment failures (outside of equipment that we support) fail and that inhibits/prohibits us from rendering services, then it’s suspended.  Some of this could include Power failures, local equipment not in our support, etc.
- Time incurred restoring Application data and/or functionality from tape media after Supplier has returned Equipment to service.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA in order to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA.

Incidents and outages due to the following incident management exclusion reasons:
2.2.a.1 Scrub, Incident deemed misclassified by CoreLogic exclusion committee.
2.2.a.2 Scrub, Non-Supplier supported site.
2.2.a.3 Scrub, Server/System not in production (not in-service).
2.2.a.4 Scrub, CoreLogic Application related outage that is not Supplier infrastructure caused.
2.2.a.5 Scrub, duplicate Incident record.
2.2.a.6 Scrub, Scheduled Downtime per system.
2.2.a.7 Scrub, Monitoring Alerts, no outage or CoreLogic impact noted.
2.2.a.8 Scrub, Eligible Recipient requested escalation for Emergency Change, No CoreLogic outage.
2.2.a.9 Scrub, CoreLogic requested the Incident Severity be raised to bypass process/lead times.
2.2.a.10 Scrub, Non-Supplier Third Party outage.
2.2.a.11 Scrub, Final CoreLogic Resolver Group.
2.2.a.12 Scrub, Incident related to Supplier reported known errors where solution/remediation not approved by CoreLogic.
2.2.a 13 Scrub NDPM Non-Dell Project Management escalation and/or outage
2.2.a.13 Scrub, Aged CoreLogic records re-assigned to Dell Support.
2.2.a.14 Scrub, Internal Dell support created
2.2.a.15 Scrub, Project related

Critical & High priority incidents that are assigned & related as child records to the Dell Network Operations (NETOPS-GLOBAL-LEVERAGED) are excluded.

Supplemental definition of terms:


Priority (Severity) Level definitions are found in Schedule   A-1 Section 2
Low Volume Eligible:

Yes, provided that if any *** Incident is not resolved within ***, then this Low Volume exception shall not apply.

Threshold parameters:
***% of Incidents are restored within ***




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
SLA Metrics and parameters:
(field names in OPAS)
Supporting Company+*
All Incident Recording during the Reporting Period
Priority*
Status. Resolved. Date/TIME
Exclude from Reporting based on RCA
Opened Date/Time
Total Pending Time

Logical description of the SLA calculation:
Report Criteria
(a) Company+*="CORELOGIC ", “STARS”, “RELS”,”FINITI”
(b) Status. Resolved Date/TIME is within the data range selected for running the report
(c) Priority = “Critical”
(d) Submitted Date/Time
(e) Exclude from SLA Reporting <> “Yes”
(f) Support Organization= Dell* or Support Group = CLGX-AOC

2. Incident Handling calculation
Time to restore service = Status Resolved Date/TIME - Submitted Date/Time – Pending Time
On-time Resolution = Resolved - Opened - On Hold

Supplementary criteria
MIM (Major Incident Management) event Critical priority records that align with a Server and or Service Availability SLA’s utilize the AIR (After Incident Review) & Whiteboard documents to calculate business impact duration via the OPAS CI Unavailability record. Process & procedure related missed MIM records (Examples: Failing to place in pending or resolved status at appropriate times, Incident records created with a Dell OPAS people record that load non-CoreLogic SLM targets & milestones) utilize the AIR (After Incident Review) & Whiteboard documents to calculate true business impact duration.

Calculations
Service Level Achievement = (Count of Critical Tickets Resolved within Threshold/Critical Incidents Resolved during reporting period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



2.
2.2.b CSL-SM-Incident Handling - High
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level
Interpreted Intent of SLA:
Measures the time interval between an Incident Creation Date being registered in the service management tool for High Priority Incidents to the time normal service operation is restored via implementing a solution to the known error or by employing a workaround.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS
Exceptions:





































Continual Service Improvement
Restoration Time does not include the following:
- Pending time allowed as indicated in section 1.6 above.
- If there are instances or circumstances at a non-Dell facility where equipment failures (outside of equipment that we support) fail and that inhibits/prohibits us from rendering services, then it’s suspended.  Some of this could include Power failures, local equipment not in our support, etc.
- Time incurred restoring Application data and/or functionality from tape media after Supplier has returned Equipment to service.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA.

Incidents and outages due to the following incident management exclusion reasons:
2.2.a.1 Scrub, Incident deemed misclassified by CoreLogic exclusion committee.
2.2.a.2 Scrub, Non-Supplier supported site.
2.2.a.3 Scrub, Server/System not in production (not in-service).
2.2.a.4 Scrub, CoreLogic Application related outage that is not Supplier infrastructure caused.
2.2.a.5 Scrub, duplicate Incident record.
2.2.a.6 Scrub, Scheduled Downtime per system.
2.2.a.7 Scrub, Monitoring Alerts, no outage or CoreLogic impact noted.
2.2.a.8 Scrub, Eligible Recipient requested escalation for Emergency Change, No CoreLogic outage.
2.2.a.9 Scrub, CoreLogic requested the Incident Severity be raised to bypass process/lead times.
2.2.a.10 Scrub, Non-Supplier Third Party outage.
2.2.a.11 Scrub, Final CoreLogic Resolver Group.
2.2.a.12 Scrub, Incident related to Supplier reported known errors where solution/remediation not approved by CoreLogic.
2.2.a 13 Scrub NDPM Non-Dell Project Management escalation and/or outage
2.2.a.13 Scrub, Aged CoreLogic records re-assigned to Dell Support.
2.2.a.14 Scrub, Internal Dell support created
2.2.a.15 Scrub, Project related

Critical & High priority incidents that are assigned & related as child records to the Dell Network Operations (NETOPS-GLOBAL-LEVERAGED) are excluded.

Yes

Supplemental definition of terms:


Priority (Severity) Level definitions are found in Schedule   A-1 Section 2
Low Volume Eligible:

Yes, provided that if any single Incident is not resolved within ***, then this Low Volume exception shall not apply.

Threshold parameters:
***% of Incidents are restored within ***




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
SLA Metrics and parameters:
(field names in OPAS)
Supporting Company+*
All Incident Recording during the Reporting Period
Priority*
Status. Resolved. Date/TIME
Exclude from Reporting based on RCA
Opened Date/Time
Total Pending Time

Logical description of the SLA calculation:
Report Criteria
(a) Company+*="CORELOGIC ", “STARS”, “RELS”, ”FINITI”
(b) Status. Resolved Date/TIME is within the data range selected for running the report
(c) Priority = “Critical”
(d) Submitted Date/Time
(e) Exclude from SLA Reporting <> “Yes”
(f) Support Organization= Dell* or Support Group = CLGX-AOC

2. Incident Handling calculation
Time to restore service = Status Resolved Date/TIME - Submitted Date/Time – Pending Time
On-time Resolution = Resolved - Opened - On Hold

Supplementary criteria
MIM (Major Incident Management) event High priority records that align with a Server and or Service Availability SLA’s utilize the AIR (After Incident Review) & Whiteboard documents to calculate business impact duration via the OPAS CI Unavailability record. Process & procedure related missed MIM records (Examples: Failing to place in pending or resolved status at appropriate times, Incident records created with a Dell OPAS people record that load non-CoreLogic SLM targets & milestones) utilize the AIR (After Incident Review) & Whiteboard documents to calculate true business impact duration.

Calculations
Service Level Achievement = (Count of Critical Tickets Resolved within Threshold/Critical Incidents Resolved during reporting period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



3.
2.2.c KM-SM-INCIDENT COMMUNICATION
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement
Interpreted Intent of SLA:
Percentage of Critical and High Priority Incidents that are communicated within the target timeframe. Measures the time interval between an Incident record being registered in the service management tool for Critical and High Priority Incidents and the time a page/phone and email is sent to CoreLogic via OPAS's FYI paging functionality. Elapsed number of minutes between the creation of a Critical or High Priority Incident and the time that Dell activates the Major Incident Management (MIM) Process including notifying CoreLogic via using the standard critical Priority Incident Notification Email template, to resolve such Critical, as reflected in the corresponding Incident Ticket

Associated hours of Operation:

25x7 see 1.4.8 Time Definitions

Reporting Tools:

OPAS
Exceptions:
N/A

Supplemental definition of terms:


None
Low Volume Eligible:

Yes, provided that if any single Incident is not resolved within ten (30) minutes, then this Low Volume exception shall not apply

Threshold parameters:
***% of Incidents are communicated within ***

SLA Metrics and parameters:
(field names in OPAS)
Company
Priority
OPAS FYI Notification Time Stamp
Email Work Log Time Stamp
Work Info Log Time Stamp for MIM Bridge Opening
Logical description of the SLA calculation:
Report Criteria
Support Company = “CORELOGIC”, STARS”,”RELS”,”FINITI”
Priority = “Critical” or “High”
Assigned Submitted Date/Time = reporting period
Resolved Date/Time within the SLA reporting period
Work log date/time Stamp

This is based on contractual SLA, which essentially covers Severity 1 and 2 (Critical and High) via OPAS FYI, and activation of MIM for Severity 1 (Critical) and notification to CoreLogic via email template within ***.

Calculations (Manual)
The numbers are based on the following criteria:
1. Included Critical and High incidents that were deemed to be Business Impacting or MIM generated incidents.
2. Does not include every incident that triggered Critical or High (e.g., automated alert) that was not identified as business impacting (MIM generated).
3. FYI paging and/or email via OPAS FYI is based on self-subscription and does not qualify who from CoreLogic may have subscribed for FYI alerts. For clarity, the number of CoreLogic employees with FYI subscription (or none) does not influence met/missed for this aspect of the metric. Only the inability to deliver FYI notifications, regardless of the number of subscriptions influences the metric.
4. Only Critical incidents were included in the MIM email notification (per contract). This means Critical is subject to a two prong metric: FYI + MIM email within ***. A miss of *** was counted as a miss for that incident.
5. Total population subject to the SLA calculation (Total Critical + High Incidents that were MIM incidents).



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



4.
2.2.d KM-SM-PERCENTAGE OF INCIDENTS THAT ARE ACCURATELY TRIAGED
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement
Interpreted Intent of SLA:
Percentage of notifications (including automated alerts) that are accurately triaged, categorized and input into the appropriate Service Management system

Associated hours of Operation:

25x7 see 1.4.8 Time Definitions

Reporting Tools:

OPAS
Exceptions:



Continual Service Improvement
Any trusted or custom event source incidents (those submitted from outside the current Supplier tools or teams) will be agreed upon before being included in this calculation.

Yes


Supplemental definition of terms:



Measures the percentage of incidents that are submitted to the ticketing system and have initial accurate categorization and assignment. For greatest accuracy, an Incident record should be created to track each inaccuracy. This would be measured using OPAS Incidents and reporting exceptions.

Low Volume Eligible:

Yes

Threshold parameters:
***% of Critical and High Priority Incidents are accurately triaged, categorized and input to system

SLA Metrics and parameters:
(field names in OPAS)
Incident Management Triage Field Flagging
Root Cause Analysis Report to include if Triage was done Accurately per guidelines defined in Problem Management process

Logical description of the SLA calculation:
Report Criteria
Steady State Service Management will review all Critical and High Priority during Root Cause Analysis, with CoreLogic, to agree on whether the Incident has had an Accurate Triage. Incident Ticket will be flagged using an identified field if it is accurately triaged or Not

Calculations (Manual)
% Accurately Triaged = (Total Tickets for High and Critical Priority –( Total Incident Tickets where Incident accuracy=”No” or Transfer Group >3))/ /Total Critical and High Priority Tickets during the reporting period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



5.
2.2.3 KM-SM-Incident Communication - Continual
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement
Interpreted Intent of SLA:
The intent of this Service Level is to measure Continual: Percentage of Incidents where updates are sent within the target

Associated hours of Operation:

24x7

Reporting Tools:

OPAS Incident
Exceptions:

This does not include any communication outside the Supplier Service Management process. Any Communication suspension as agreed by Dell and CoreLogic.

Supplemental definition of terms:


Measures the percentage of Critical Incidents where communication to established stakeholders is distributed within 5 minutes of the 30-minute target during the duration of the Critical Incident

NOTE:
Measurement of KM will be through an agreed-upon process and timestamp within the OPAS system or email transmission mechanism

Low Volume Eligible:

None
Threshold parameters:
 ***% of all Critical Incident Communications sent no later than *** of the *** target.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CMDB Urgency
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”
Incident Records where Resolved Date/Time falls within reporting period
Priority = Critical

Calculations (will be done Manually by Service Management)
Service Level Achievement = (A/B) * 100%
A = Number of Critical Incident Communications which MET Target
B = Total count of Critical Incident Communications

Verification Steps:
1. Distribution Time Stamp of each Communication is reviewed to determine if update is sent at least every ***.
 2. Critical Incident Communication = MET if step 1 is true and time stamp within *** of the *** target have elapsed since previous update
  
Example scenario: Initial MIM is sent at ***, the first update would be due at or between ***



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



6.
2.2.f1/2.2.f2 KM-SM-Problem Management-Service Impact Document Delivery (AIR and RCA)
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the percentage of times an After Incident Report (AIR) document and final RCA that covers the items listed below is completed for Critical and High Priority Incidents and a Problem Review Meeting is completed within the target timeframe.
- Incident details through restoration
- Business impact
- RCA - if known
- Long term - fix if known

Associated hours of Operation:

Business hours – *** = 1 business day  
Reporting Tools:

OPAS Problem Management
Exceptions:

Excludes Problem records where CoreLogic critical/key stakeholder participation was not included within the target timeframe.

Continual Service Improvement

Supplemental definition of terms:


Yes

     Critical priority - Within ***, an initial Problem record is created (After Incident Report (AIR)), and within ***, a final Root Cause Analysis (RCA) is completed.
     High priority - Within ***, an initial Problem record is created (After Incident Report (AIR)), and within ***, a final Root Cause Analysis (RCA) is completed
     Measures the percentage of times an AIR document and final RCA that covers the items listed below is completed for Critical & High Incidents and a Problem Review Meeting is completed within the target timeframe.

* Incident details through restoration
* Business impact
* RCA - if known
* Long term - fix if known

Actual closure of the RCA and Problem record is dependent on remediation activities needed.

Low Volume Eligible:

No
Threshold parameters:
***% of AIRs are delivered within *** and Final RCA is delivered and reviewed with CoreLogic within *** for Critical and *** for High Priority Incidents

SLA Metrics and parameters:
(field names in OPAS)
Company+*
Work Log Entry in Incident
Manual Report Tracking System




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “STARS”, “RELS”, “FINITI”
Problem Records where Completed Date/Time within the reporting period

Steady State must enter work log Information on Initial RCA and Final RCA into each Record. A report will be provided to support when RCAs are submitted based on Incident Critical/High work log Info.
Calculations (will be done Manually by Service Management)
Service Level Achievement = Total Records where Threshold is met during reporting period /Total Problem Records during the reporting Period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



7.
2.2.g KM-SM-ASSET INVENTORY- ACCURACY
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to Measures the accuracy of ***% of CIs and associated attributes (as defined in the Policy and Procedures Manual) stored in the Supplier Asset Management Database.

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions

Reporting Tools:

AMDB and KACE
Exceptions:

Any assets within the sample set that are unavailable or inaccessible to Supplier tools and/or Supplier Personnel will be excluded from this calculation

Supplemental definition of terms:


In order to measure this SLA each month a random sampling of ***% of the actively reporting KACE servers and workstations will be obtained. The criteria determine if the CIs are compliant will be the following:
1)      Does the device exist in the AMDB?
2)      If no, then this counts as a failure
3)      If yes, then is the device in ‘deployed’ status in the AMDB?
If not in a ‘deployed’ status, then this counts as a failure
4)      If yes and in a Deployed status then compare the data pulled from KACE and compare it to the comparable field of data in the AMDB
5)      If any of the fields for a device does not match, then the device counts as a failure
6)      All others are accurate [this count to feed into the count of accurately reported CIs within the sample set

Each device included in a random sample audit will be tagged with a Last Audit Date. Devices with Last Audit Dates within the preceding *** will be excluded from inclusion in the random sampling.
The results of the audit and supporting data will be provided to Service Management as per their processes to include the data in the SLA calculations and reporting requirements.
Each device failing the audit will be remediated each month and will have an on-line edit function to record notes as to the remediation.
Each *** prior to the new sampling, the previous *** sampling and remediation will be snapped to an archive.
Each *** Asset Management will review the previous *** audit results with CLGX.

Low Volume Eligible:

No
Threshold parameters:
***%

SLA Metrics and parameters:
(field names in OPAS)
Supported Company
Random ***% of the CI Sampling
Attributes to be compared for audit consist of the following:
KACE ID – to identify matches in the AMDB
Host Name
Status
Domain
IP Address
MAC Address
OS Type
Service Pack
Hard Drive Size
Total RAM




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
Manual Audit will be conducted. Any failure on data based on attribute to sampling of ***% of the CIs will be considered an SLA miss, a CI must meet the following requirements in order to pass the audit:
Device in AMDB = Yes
AMDB Status = Deployed
AMDB Data = KACE Data

Calculations (will be done Manually by Service Management)
Audit Accuracy = The count of accurately reported CIs within the sample set/ the total count of sample set CIs



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



8.
2.2.h KM-SM-CSAT Operations Managers
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
*** (every *** in ***)
Reporting Frequency:
*** (every ***), on or before the *** following the reporting period where the survey is closed
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure CoreLogic Operation Managers customer satisfaction

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions

Reporting Tools:

Manual Report
Exceptions:

Minimum acceptable returned surveys: ***% of surveys returned
Supplemental definition of terms:

Measures Supplier's performance through a jointly created *** (every *** and ***) survey to 'CoreLogic Operational Managers' (Measured on a –*** scale). Expected survey set of *** individuals. Average of all the scores related to the single overall satisfaction question selected by an Operational Managers in such survey (on a scale of ***, with *** representing the highest level of satisfaction.

Low Volume Eligible:

No
Threshold parameters:
>=***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Survey Sampling and Survey Results

Logical description of the SLA calculation:
Report Criteria
Total Survey Feedback received ***% of Surveys Sent

Calculations
Service Level Achievement = (Sum of score responses from Operational Managers/ Number of responses received) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



9.
2.2.h.1 KM-SM-CSAT Operations Managers Service Improvement (SI)
DATES
SLA Start Date:
11/1/2016
First Reporting Period:
11/30/2016
First Report Date:
12/5/2016
Reporting Period:
*** (every in *** and ***)
Reporting Frequency:
*** (every ***), on or before *** following the reporting period where the survey is closed
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Measures supplier's performance in delivering items collected during the Operation Managers Survey;

1) Publish initial results of survey within *** (Overall score).

2) Publish detailed results of survey within *** of survey closure (Detailed results for every question within survey).

3) Publish action items logged as a result of survey and interview feedback within *** of survey closure.

4) Status of action items *** post survey closure (prep for next survey)


Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions

Reporting Tools:

Manual Report
Exceptions:
N/A
 
 
Low Volume Eligible:

No
Threshold parameters:
= ***
SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Survey Sampling and Survey Results

Logical description of the SLA calculation:
Report Criteria
Service Level Achievement = (A/B)

Calculations
A = In the reporting period is there a deliverable due? Y or N.
B = Pass / Fail



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



10.
2.2.i KM-SM-CSAT-END USERS
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
*** on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure End User customer satisfaction

Associated hours of Operation:

N/A
Reporting Tools:

OPAS CSAT
Exceptions:

Minimum acceptable sample: 15% of surveys distributed

Supplemental definition of terms:


Measures Supplier's performance through a survey sent to***% of 'End Users' (Measured on a –*** scale). Average of all of the numeric scores selected by an Authorized User in such survey (on a scale of ***, with *** representing the highest level of satisfaction

Low Volume Eligible:

No
Threshold parameters:
>=***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Customer Survey Rating per Customer Sat Record

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”STARS”, “RELS”, “FINITI”
Customer Satisfaction Survey Feedback during the Reporting Period

Calculations
Service Level Achievement = (Sum of score responses from Authorized Users/ Number of responses received)



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



11.
2.2.j KM-SM-CSAT DROP-END USERS
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure End User customer satisfaction drop
Associated hours of Operation:

N/A
Reporting Tools:

OPAS Datamart
Exceptions:

= Measured at the anniversary of Service Commencement Date
- Drops in Authorized User satisfaction due to an agreed upon exceptional business events or due to CoreLogic directed

Supplemental definition of terms:


Number of months in a year (measured annually) when end user CSAT dropped below the prior month. Auto surveys based on services requested across all towers/functions. Compiled and summarized ***.

Low Volume Eligible:

No
Threshold parameters:
*** where the CSAT is lower than ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company


Logical description of the SLA calculation:
Report Criteria
All Individual *** CSAT performances during ***
Supporting Company = CORELOGIC, STARS, RELS, FINITI

SLA Missed = *** CSAT where CSAT is lower than ***

Calculations
Total no. of months were SLA Missed<=***



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



12.
2.3.a CSL-SD-AVERAGE SPEED TO ANSWER
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
Average Speed to Answer (ASA) is the average across all calls to the Service Desk for the time taken from when a call is deemed to have entered the “wait queue” (once the caller has made their final selection from the IVR (interactive voice response) menu) to the time a Service Desk agent answers the call for the purposes of providing Services.

Associated hours of Operation:

24x7 see 1.4.8 Time Definitions  
Reporting Tools:

Dell-provided system logs and any other designated tracking systems (e.g., ACD system, IVR), tracking will be made using https://client.ps.net system. All calls that were abandoned by the Caller prior to Service Desk taking the call will be excluded from the SLA Calculation.

Exceptions:


Continual Service Improvement
Telephone calls to the Service Desk where the End User hangs up or disconnects prior to speaking with a Service Desk representative.

Yes

Supplemental definition of terms:


None
Low Volume Eligible:

No
Threshold parameters:
***% of calls answered <=***

SLA Metrics and parameters:
(field names in OPAS)
Speed to Answer (SA) for each call

Logical description of the SLA calculation:
Report Criteria
Supporting Company = CORELOGIC, RELS, FINITI

Calculations
Total number of calls answered within ***/ total number of telephone calls answered by Service Desk during the Reporting Period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



13.
2.3.b KM-SD-AVERAGE HANDLE TIME
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Average Handle Time (AHT) - Percentage of help desk calls that are handled within the target timeframe to support Speed to Answer (ASA) SLA attainment

Associated hours of Operation:

24x7 see 1.4.8 Time Definitions  
Reporting Tools:

Automatic Call Distribution (ACD)
Exceptions:

Continual Service Improvement
None

Yes

Supplemental definition of terms:


Average Handle Time (AHT) is the average across all calls to the Service Desk for a Measurement Period of the time taken on the phone by the Service Desk agent for each call.

Actual Performance will be reported every month until Dell and CoreLogic come to an agreement on the KPI measurement value.

The KPI, once defined, will be subject to the Continuous Service Improvement Process in Schedule A-03 Section 6 and will have a cap of ***.

Low Volume Eligible:

No
Threshold parameters:
<= ***

SLA Metrics and parameters:
(field names in OPAS)
Support Company
Logical description of the SLA calculation:
Report Criteria
All Calls within the ACD for the reporting period
Supporting Company = “CORELOGIC”, “STARS”, “RELS”, “FINITI”

Calculations
Actual performance will be reported = Total time in *** of all calls answered by a Service Desk agent during the Measurement Period/ number of answered calls




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



14.
2.3.c KM-SD-ABANDON RATE
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Abandon Rate - Maximum percentage of help desk calls that are abandoned

Associated hours of Operation:

24x7 see 1.4.8 Time Definitions  
Reporting Tools:

Automatic Call Distribution (ACD)
Exceptions:

Continual Service Improvement
Excludes calls abandoned < ***

Yes

Supplemental definition of terms:


Call Abandon Rate measured as a percentage by adding the total number of calls to the Service Desk that hang up after selecting an option on the Voice Response Unit and before the call is answered by a live person and dividing this by the total number of calls to the Service Desk during the Measurement Period

Low Volume Eligible:

No
Threshold parameters:
<= ***

SLA Metrics and parameters:
(field names in OPAS)
Support Company
Logical description of the SLA calculation:
Report Criteria
All Calls for Supporting Company = “CORELOGIC”, “RELS”, “FINITI”, “STARS” during the reporting period

Calculations
Service Level Achievement =Total number of calls abandoned/Total calls – exempted calls x 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



15.
2.3.d CSL-SD-FIRST CALL RESOLUTION
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
This Service Level measures the percentage of Incidents that are resolved during the first telephone Call to the Service Desk.

Associated hours of Operation:

24x7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS
Exceptions:

- Incidents received by the Service Desk by means other than telephone (for example, e-mail, fax, self-service portal) will be excluded when calculating attainment for this Service Level.
- Calls for which a ticket has already been opened for the same Incident. Example given: large scale outage, multiple users calling in regards the same issue; the initial reported incident is calculated as part of the SLA.
- Incidents that cannot be resolved by the Service Desk, as defined in a list to be developed by Dell during Transition Period and updated from time to time, in each case approved by CoreLogic.
Continual Service Improvement

Supplemental definition of terms:

Yes

Reference Material for transactions included as part of FAR is found on :

***

Low Volume Eligible:

Yes
Threshold parameters:
Percentage of help desk calls that are resolved on the first call in less than *** >= ***% of the Time

SLA Metrics and parameters:
(field names in OPAS)
Incidents resolved by Service Desk through First Call resolution
Incident flagged as FAR(First Assignment Resolution)

Logical description of the SLA calculation:
Report Criteria
• Supporting Company = “CORELOGIC”, “RELS”,”FINITI”, “STARS””
• Status = Resolved
• Assigned Date/Time
• Resolved Date/Time
• Support Group = CLGX-Service Desk
• FAR Candidate Eligible for FAR = “Yes”
• Group Transfer = 0
• Source = Phone

Calculations
First Call Resolution = (total # of Incidents during a Reporting Period that are resolved by a Service Desk representative during the first telephone call to the Service Desk within ***/ Total FAR Eligible incidents) * 100



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



16.
2.6.a KM-DT-END-USER DEVICE NEW USER SETUP
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the End User Device Setup (new user) - Percentage of new user setups that are successfully completed within the target timeframe

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Batch new user setups will be excluded from the On-Time Completion percentage calculation.
- Remote Location: The eleventh or more new user setup per day per remote location will be excluded from SLA calculation.
- Campus Location: The sixteenth or more new user setup per day per campus location will be excluded from SLA calculation.
- Time before arrival of assets will be excluded from this measurement (i.e., ticket is submitted after arrival of all necessary assets.)
- Request for Non-Standard Hardware that requires unique configuration requirements not previously defined.
_ A Batch will be defined as *** new user set-ups per day for Remote locations and *** new user set-ups per day for Campus Locations.
Continual Service Improvement

Supplemental definition of terms:

Yes

Measures the percentage of New Authorized User setup requests that are completed within the required timeframes during the Measurement Period Request Name : User Provisioning and Work Order = Computer Hardware Implementation

Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***) then this Low Volume exception shall not apply

Threshold parameters:
***% of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Requested by Company
Request Summary
Closed Date/Time
Submitted Date/Time
Approval Date/Time
Pending Time
Status
Excluded from SLA Reporting
Logical description of the SLA calculation:
Report Criteria
All Request Records with Request Type = “New User Provisioning”
If Request Summary = “New User Provisioning”
Get Work Order Name = “*EUD*” or Work Order name = “Desk Phone*” or Work Order Name = “Mobile Device*” or ( Request Type = “
“TEMP NUP CLGX-Add or Install End User Device” or “
“TEMP NUP CLGX-Computer Hardware” or
“TEMP NUP CLGX-Desk Phone” or
“TEMP NUP CLGX-TEM-Mobile Device”)

Closed Date/Time is within the reporting date of the SLA
Excluded from SLA reporting <>”Yes”
Status = “Closed”
CoreLogic authorized users, currently:
Requested by Company = “CORELOGIC”, “RELS”,”FINITI”

Calculations
SLA Elapsed Time = Completed Date/Time – Approval Date/Time – Pending Time

Service Level Achievement = Number of End User Device Setup with SLA Elapsed time <= *** / Total number of End User Device Setup Service Requests for the Measurement Period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



17.
2.6.b1/2.6.b2 KM-DT-END-USER DEVICE SERVICES SUPPORT
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the End User Device Services Support - Percentage of end user device service support Incidents that are successfully completed within the target timeframe

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management , OPAS Location Table
Exceptions:

Restoration Time does not include the following:
- Time that Incident Tickets are in "suspend mode" due to previously unknown third-party Software defects
- If there are instances or circumstances at a non-Dell facility where equipment failures (outside of equipment that Dell supports) fail and that inhibits/prohibits us from rendering services, then it’s suspended. Some of this could include facilities power failures, local equipment not in our support, etc. - Time incurred restoring Application data and/or functionality from tape media after Dell has returned Equipment to service.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA in order to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA
- Incident Priority = “Critical” or “High” (already part of Critical or High Incidents SLA)

Continual Service Improvement

Supplemental definition of terms:

Yes

Measures the time interval between an Incident record being registered in the service management tool for Desktop Services related Incidents to the time that operation is restored

Low Volume Eligible:

Yes, provided that if any single Incident is not resolved within *** at staffed sites and more than *** for non-staffed sites, then this Low Volume exception shall not apply

Threshold parameters:
***% of Incidents completed within *** at staffed sites and within *** for non-staffed sites

SLA Metrics and parameters:
(field names in OPAS)
Customer Company
Reported Date/Time
Closed Date/Time
Pending Time
OPAS Location Site Group
Assignee Group
Site Alias
Logical description of the SLA calculation:
Report Criteria
Customer Company = “CORELOGIC”, “RELS”, “FINITI”
Closed Date/Time within the reporting period
Priority = Medium or Low
Company = “CORELOGIC”, “RELS”,”FINITI”,
.Location Support Type = “Staffed*” or Non-Staffed*”
(Look up from location table)
Assignee Group = CLGX-FS* or Product Name = “*Phone*”

Calculations
Staffed SLA = (Resolved Date- Submit Date – Pending Time)/*meets SLA if Staffed SLA = ***
Non-Staffed SLA = (Resolved Date- Submit Date – Pending Time)/*meets SLA if Staffed SLA = ***

Service Level Achievement = (Total Met SLA for Staffed + Total Met SLA for Non-Staffed)/Total Incident Tickets during the reporting period based on Report Criteria x 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



18.
2.6.c KM-DT-END-USER DEVICE TERMINATION
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the End User Device Termination - Percentage of employee end user device termination requests that are successfully completed within the target timeframe

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

This excludes any recovery of employee physical assets (for assets not in CoreLogic offices)

Continual Service Improvement

Supplemental definition of terms:


Yes

Measures the degree of compliance of request for End User Device termination within the time period specified. The time period used is the elapsed time from activation of a task to closure of the Service Management Workflow System record.

Low Volume Eligible:

Yes, if single Incident resulting in default is restored in less than ***

Threshold parameters:
*** % of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Requested by Company
Request Summary
Closed Date/Time
Submitted Date/Time
Approval Date/Time
Pending Time
Status
Excluded from SLA Reporting


Logical description of the SLA calculation:
Report Criteria
All Request Records with Request Type = “Terminate a Resource (Employee/Contractor/Vendor)”
Work Order = “Terminate Computer Hardware” or Work Order = “Terminate Desk phone”, or Work Order = “Terminate Mobile Device”
Closed Date/Time is within the reporting date of the SLA
Excluded from SLA reporting <>”Yes”
Status = “Closed”
Requested by Company = “CORELOGIC”, “RELS”,”FINITI”, “STARS”

Calculations
SLA Elapsed Time = Completed Date/Time – Approval Date/Time – Pending Time

Service Level Achievement = Number of End User Device Termination with SLA Elapsed time <= ***/ Total number of End User Device Setup Service Requests for the Measurement Period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



19.
2.6.d KM-DT-REQUEST-PACKAGING (DEVELOP AND PUSH)
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure Packaging - Percentage of packaging requests that are successfully completed within the target timeframe

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Any time greater than *** for CoreLogic to perform applicable testing of the software package.

Supplemental definition of terms:


Measures the time taken to package software from the receipt of a request for new software to the time that the software is available for the Authorized User to install via the software distribution system. Software Package is a single software title whose installer has been modified in a manner to install with predetermined settings.

Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply

Threshold parameters:
***% of work requests are completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Requested for Company
Request Summary
Closed Date/Time
Submitted Date/Time
Approval Date/Time
Status
Excluded from SLA Reporting

Logical description of the SLA calculation:
Report Criteria
All Request Records with Request Type = “Software Package Creation/Deployment - DTE”
Closed Date/Time is within the reporting date of the SLA
Excluded from SLA reporting <>”Yes”
Status = “Closed”
Requested by Company = “CORELOGIC”, “RELS”,”FINITI”,”STARS”

Calculations
SLA Elapsed Time = Completed Date/Time – Approval Date/Time - Pending Time
Service Level Achievement = Number of End User Packaging Request with SLA Elapsed time <=*** / Total number of End User Device Setup Service Requests for the Measurement Period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



20.
2.6.e1/2.6.e2 KM-DT-END-USER DEVICE MOVES/ADDS/CHANGES
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure End User Device Moves/Adds/Changes - Percentage of move requests that are successfully completed within the target timeframe

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests, Location
Exceptions:

- Batch MACDs will be excluded from the On-Time Completion percentage calculation.
- Remote Location: The eleventh or more MACDs per day per remote location will be excluded from SLA calculation.
- Campus Location: The sixteenth or more MACDs per day per campus location will be excluded from SLA calculation.

Batch (*** IMACDs in a day per CoreLogic Facility) Moves/Adds/Changes will be excluded from the on-Time Completion percentage calculation.

Continual Service Improvement

Supplemental definition of terms:


Yes

Measures the percentage of Moves/Adds/Changes (MACs) Service Requests completed within the required timeframes during the Measurement Period

Low Volume Eligible:

Yes, provided that if any single Incident is not resolved within *** at staffed sites and more than *** for non-staffed sites, then this Low Volume exception shall not apply

Threshold parameters:
***% of requests completed within *** at staffed sites and *** at non-staffed sites

SLA Metrics and parameters:
(field names in OPAS)
Requested for
Company
Request Summary
Closed Date/Time
Submitted Date/Time
Approval Date/Time
Status
Excluded from SLA Reporting
Site Alias
Logical description of the SLA calculation:
Report Criteria
All Request Records with Request Summary = “Move Request” , “Computer Hardware”;”De-Install Printer”, “Desk Phone”, “Install Printer – EUD”, “Mobile Device”
Closed Date/Time is within the reporting date of the SLA
Excluded from SLA reporting <>”Yes”
Status = “Closed”
Requested for Company = “CORELOGIC”, “RELS”,”FINITI”, “STARS”
Requester for. Location.Support Type = “staffed*” or Non-Staffed*”

(Look up people record of requested for to get location)

Calculations
Staffed SITE SLA = Completed Date/Time – Approval Date/Time /* SLA met = ***/
Non-Staffed SITE SLA = Completed Date/Time – Approval Date/Time /* SLA met = ***/

Service Level Calculation = (Total Staffed Site SLA Met + Total Non-Staffed Site SLA)/ Total no. of MAC request for the reporting period



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



21.
2.6.f KM-DT-CoreLogic PC Refresh
DATES
SLA Start Date:
6/1/2018
First Reporting Period:
6/30/2018
First Report Date:
7/6/2018
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Interpreted Intent of SLA:
The intent of this SLA is to measure the duration between completion time & end of lease date for the CoreLogic PC Refresh requests.

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Request Management
Exceptions:





Yes, 1) Records for sites not supported by NTT field services are out of scope for this SLA. (Non-supported sites: Austin TX, Bloomington MN, Milwaukee WI, Rochester NY & Oxford MS). 2) Approved work order driven projects (PMO) for bulk PC Refresh are excluded from this SLA.
Continual Service Improvement

Yes

Low Volume Eligible:

No
Threshold parameters:
***%

SLA Metrics and parameters:
(field names in OPAS)

Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = CoreLogic PC Refresh
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = CoreLogic PC Refresh
Request Closed Date/Time is within the reporting period
Request Competition Date/Time is < than End of Lease Date
Excluded in SLA Reporting <> Yes

Calculations
Service Level Achievement = (A/B)*100%
A=Number of PC Refresh SRM’s closed
B= Number of PC Refresh SRM’s completed prior to end of lease date



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


22.
2.4.a KM-ENT-PATCH MANAGEMENT SERVERS
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure Patch management: Servers - Percentage of servers that are successfully patched within the target timeframe (from release of patch)

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Change Management
Exceptions:

- Post implementation of service pack, if Microsoft through their website releases a bug notification related to that specific Service Pack & that has caused unsuccessful implementation of patch.
- Time between Dell's request for CoreLogic's approval and when CoreLogic provides its approval

Supplemental definition of terms:


Apply Patches to all instances of enterprise infrastructure applications including acquiring, testing, and installing multiple patches (Service Pack).

Patch management tasks include: maintaining current knowledge of available patches, deciding what patches are appropriate, ensuring that patches are installed properly, testing systems after installation, and documenting all associated procedures, such as specific configurations required.

Definition of Normal and Critical patches are part of the PPM documentation for Intel and Unix support.
Low Volume Eligible:

No
Threshold parameters:
***% of normal patches applied in ***and critical patches applied in ***

SLA Metrics and parameters:
(field names in OPAS)
Requested for Company
Actual Start Date/Time
Actual End Date/Time
Completed Date/Time
Exclude from SLA Reporting
Product Categorization Tier 1
Product Categorization Tier 2
Product Categorization Tier 3
Operational Categorization Tier 1
Operational Categorization Tier 2
Operational Categorization Tier 3
Excluded from SLA reporting
Logical description of the SLA calculation:
Report Criteria
Requested Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Completed Date and Time = within the SLA reporting period
Product Categorization 1 = “HARDWARE”;Product Categorization 2 = “SERVER”
Operational Category Tier 1 = “INSTALL”
Operational Category Tier 2 = “CODE”
Operational Category Tier 3 = “PATCH- MAINTENANCE”
Excluded from SLA Reporting <>”Yes”
Performance Rating = 5
Priority = Medium (target is Normal)
Priority = High (target is Critical)

Calculations
Critical Patches SLA = Complete Date/time - Submit Date/Time Date/Time (Should be equal to ***)

Normal Patches SLA = Complete Date/time - Submit Date/Time (Should be equal to ***)

Service Level Achievement = (Total number of Enterprise Patches that are successfully installed in accordance with SLA/ Total number of Enterprise Patches that are scheduled to be completed during the Measurement Period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



1.
2.4.b KM-ENT-PERCENTAGE AVAILABILITY OF RIGHTFAX SERVICE
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage Availability of Right Fax Service

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management , Change Management, Atrium
Exceptions:

- Single point of failure of hardware, software, or carrier services
Root Cause
- All records that will indicate not part of this SLA as part of RCA from clause "Will be measured using an Incident RCA based measurement approach" flagged as Excluded from SLA reporting

Supplemental definition of terms:


Service availability for Right Fax (including SQL server database) server to send and receive faxes.

Low Volume Eligible:

No

Threshold parameters:
***%

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Priority
Product Name
Incident ID
Incident Related Change
Incident Assigned Date/Time
Incident Resolved Date/Time
Change ID
Change CI Unavailability
Change CI Unavailability Start Date/Time
Change CI Unavailability End Date/Time
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”STARS”,”RELS”,”FINITI”
Priority = Critical or High
Service Tier = “RightFax”
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting

Calculations
Service Level Achievement = (Total number of hours of RightFax UPTIME/ Expected Uptime * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



2.
2.4.c CSL-ENT-PERCENTAGE AVAILABILITY OF EXCHANGE EMAIL SERVICE
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
Service Availability is defined as the ability of an Authorized User on an Exchange account to (a) access and retrieve information from an individual mailbox, and (b) send and receive messages via his or her mailbox using the Services (Outlook MAPI, OWA, IMAP or POP3).

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management /Change Management, Atrium CMDB
Exceptions:

 - Individual mailbox or mobile device Availability, individual incoming and outgoing mail delivery time.
- Single point of failure (excluding RAID0 mail stores) of hardware, Software, or carrier services

Supplemental definition of terms:




Low Volume Eligible:

No


Threshold parameters:
Expected Service Level – ***%


SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Priority
Product Catalogue Tier 3
Incident ID
Incident Related Change
Incident Assigned Date/Time
Incident Resolved Date/Time
Change ID
Change CI Unavailability
Change CI Unavailability Start Date/Time
Change CI Unavailability End Date/Time
CMDB Service Tier
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”STARS”,”RELS”,”FINITI”,
Priority = Critical or High
CMDB Service Tier = “Exchange”

CI Name as provided above
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting

Calculations
Service Level Achievement = (Total number of hours of Exchange Email Service UPTIME/ Expected Uptime * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



3.
2.4.d CSL-ENT-PERCENTAGE AVAILABILITY OF CITRIX METAFRAME
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
Service Availability is defined by availability of core Citrix services like IMA service, Print spooler, XML service and published applications.

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Datamart Incident Management /Change Management, CMDB
Exceptions:

 - Individual Citrix clients, individual Citrix Desktop Availability
- For published applications, where the application is the root cause of the unavailability.

Supplemental definition of terms:


CMDB Service Tier=Citrix

Low Volume Eligible:

No

Threshold parameters:
***%

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Priority
Product Name
Incident ID
Incident Related Change
Incident Assigned Date/Time
Incident Resolved Date/Time
Change ID
Change CI Unavailability
Change CI Unavailability Start Date/Time
Change CI Unavailability End Date/Time
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,” RELS”,” FINITI”,” STARS”
Priority = High or Critical
CMDB Service Tier = Citrix
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting

Calculations
Service Level Achievement = (Total number of hours of Exchange Email Service UPTIME/ Expected Uptime * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



4.
2.9.a CSL-NW-Data Center LAN Availability
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of Network Connectivity required for business operations - LAN (Data Center locations). Availability within data center, common communication between computing and associated devices. Redundant equipment is required. The service is determined to be available if either side of the redundancy is up and operational.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB. Will be measured using an Incident RCA based measurement approach.

Exceptions:


- No single LAN availability device could cause an SLA miss, unless that single device is unavailable for more than 4 hours.

Supplemental definition of terms:


To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration.

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of Data Center LAN Systems will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
Product Category Tier 3
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CoreLogic”,”Rels”,”Finiti”,”Stars”
Priority = High or Critical
Product Category Tier 1 = Hardware, Service
Product Category Tier 2 = Network
Product Category Tier 3 = Switch, Appliance, Firewall, Load Balancer
Service Tier = Network
Site group = Data Center
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Note: Any incident or unavailability record may be eligible, if the ticket categorization was not entered properly and outage was discovered to be Service related based on RCA.

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of devices in the LAN availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of LAN devices allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of LAN devices that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***%, this would mean there will be no more than *** of downtime.



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



5.
2.9.b CSL-NW-Data Center WAN Availability
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of Network Connectivity required for business operations - WAN (Data Center locations). Availability for inter-data center connection, internet, intranet, extranet, devices and circuits. Reachability; measurement of the total number of hours of Availability through VLANS and firewalls to internet service provider circuits, intranet and extranet circuit service providers, communication between data centers. Redundant equipment is required. The service is determined to be available if either side of the redundancy is up and operational.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB. Will be measured using an Incident RCA based measurement approach.
Exceptions:


- No single WAN availability device could cause an SLA miss, unless that single device is unavailable for more than ***.

Supplemental definition of terms:

To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration.

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of Data Center WAN Systems will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
Product Category Tier 3
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CoreLogic”,”Rels”,”Finiti”,”Stars”
Priority = High or Critical
Product Category Tier 1 = Hardware, Service
Product Category Tier 2 = Network
Product Category Tier 3 = Router, Gateway, Circuit
Service Tier = Network
Site group = Data Center
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Note: Any incident or unavailability record may be eligible, if the ticket categorization was not entered properly and outage was discovered to be Service related based on RCA.

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of devices in the WAN availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of WAN devices allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of WAN devices that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***%, this would mean there will be no more than *** of downtime.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



6.
2.9.c KM-NW-Campus LAN Availability
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of Network Connectivity required for business operations - LAN (Campus locations, Dallas/Irving, Irvine & San Diego). Availability within campus buildings, common communication between computing and associated devices. Assume redundant equipment exists at some level. The service is determined to be available if either side of the redundancy is up and operational.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB. Will be measured using an Incident RCA based measurement approach.

Exceptions:


Continual Service Improvement


- No Single Campus LAN availability device could cause an SLA miss, unless that single device is unavailable for more than ***.

Yes


Supplemental definition of terms:

To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration.


Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of Campus LAN Systems will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
Product Category Tier 3
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CoreLogic”,”Rels”,”Finiti”,”Stars”
Priority = High or Critical
Product Category Tier 1 = Hardware, Service
Product Category Tier 2 = Network
Product Category Tier 3 = Switch, Appliance, Firewall, Load Balancer
Service Tier = Network
Site group <> Data Center
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Note: Any incident or unavailability record may be eligible, if the ticket categorization was not entered properly and outage was discovered to be Service related based on RCA.

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of devices in the Campus LAN availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of Campus LAN devices allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of Campus LAN devices that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***%, this would mean there will be no more than *** of downtime.



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



7.
2.9.d1/2.9.d2 KM-NETWORK-REQUEST-FIREWALL, IP ADDRESS, HTTP PORT REQUESTS
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the IT Security - Percent of Firewall requests, I.P. Address Add, Change or Open HTTP, Port requests that are successfully completed within Target timeframe

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

 - Any hold in approval processes or change request initiated by CoreLogic
- Supplier's failure to meet this Service Level in respect of any hardware-related Incidents shall be excused to the extent that such failure is caused by any Supplier third party provider's failure to perform, or delay in performing, any repair or replacement actions required to be performed by such third party provider in connection with the resolution of any such Incident; provided, that (i) Supplier uses commercially reasonable efforts to cause such third party providers to perform within the required time frame and (ii) to the extent documented in Supplier's Root Cause Analysis
- Pending Time based on allowed Pending Event

Supplemental definition of terms:


Measures the time taken between processing of approved request(s)

Low Volume Eligible:

No

Threshold parameters:
***% of requests completed within ***; ***% completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary Name = Firewall Request or IP Assignment
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations

Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

***% - Service Level Achievement (within ***)= (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%

***% - Service Level Achievement (within ***)= (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



8.
2.9.e CSL-NW-VOIP Availability
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of the VOIP Service. VOIP Availability consists of time voice communication between users was available. Includes contact center and end user. Redundant equipment and circuits are required.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB. Cisco operations manager or equivalent. Will be measured using an Incident RCA based measurement approach.

Exceptions:

- Excludes Avaya, Nortel and other non-enterprise VOIP systems.
- No single VOIP availability device could cause an SLA miss, unless that single device is unavailable for more than ***.

Supplemental definition of terms:


To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration.

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of VOIP Systems will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CoreLogic”,”Rels”,”Finiti”,”Stars”
Priority = High or Critical
Service Tier = Network Voice
Site group = Data Center
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Note: Any incident or unavailability record may be eligible, if the ticket categorization was not entered properly and outage was discovered to be Service related based on RCA.

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of devices in the VOIP availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of VOIP devices allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to *.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of VOIP devices that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***%, this would mean there will be no more than *** of downtime.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



9.
2.9.f KM-NW-Call Center/Call Monitoring Requests
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Measures the time it takes to fulfill Call Center/Nice - Network Voice requests, including call agent IMACDs, call recording requests, etc.

Associated hours of Operation:

Business hours – *** = 1 business day
Reporting Tools:

OPAS Request Management
Exceptions:

Continual Service Improvement



Yes
Supplemental definition of terms:

 
Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply

Threshold parameters:
***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CoreLogic”, “Finiti”,”Rels”,”Stars”
Request Type Name = “Call Center/Nice - Network Voice”
Request Completed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

Service Level Achievement (within ***) = (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



10.
2.9.f1 KM-NW-Contact Center Call Flow
DATES
SLA Start Date:
8/1/2017
First Reporting Period:
8/31/2017
First Report Date:
9/7/2017
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Measures the time it takes to fulfill Contact Center - Call Flow Add / Change.

Associated hours of Operation:

Business hours – *** = 1 business day
Reporting Tools:

OPAS Request Management
Exceptions:

 
Supplemental definition of terms:

Requests being measured under this key measurement include both project & non-project records. To determine project work, the NTT VOIP team review items requested with NTT Project Management team (examples; acquisitions where voice is being migrated, upgrades, disconnects of toll free numbers and removal of scripts).

Low Volume Eligible:

Yes, provided that if any single request is not resolved within 45 business days, then this Low Volume exception shall not apply

Threshold parameters:
1)      ***% within ***
2)      ***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CoreLogic”, “Finiti”,”Rels”,”Stars”
Request Type Name = “Contact Center - Call Flow Add / Change”
Work Order Type = “General” & “Project”
Request Completed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time
Pending time is not excluded from the calculation for this measurement .

Service Level Achievement
Request SLA = Request Completed Date/Time – Request Approval Date/Time

Service Level Achievement (***% within *** & ***% within ***) = (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



11.
2.4.e CSL-MR-Server Availability - High
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as High.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No Single High availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as High which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


High Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Urgency = High

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of High Availability servers will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CMDB Urgency
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
CMDB Urgency = “High”
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ***(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of servers in the High availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of servers allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of servers that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***% this would mean the *** server with more than ***of downtime would result in a miss of the SLA target.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



12.
2.4.f CSL-MR-Server Availability - Standard
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before*** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as Standard.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No Single Standard availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as High which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


Standard Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Urgency = Standard

Low Volume Eligible:

No

Threshold parameters:
***% of the time, ****% of Standard Availability servers will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CMDB Urgency
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
CMDB Urgency = “Standard”
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed =****(*** *** -.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of servers in the Standard availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of servers allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of servers that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***% this would mean the *** server with more than *** of downtime would result in a miss of the SLA target.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



13.
2.4.g KM-MR-Server Availability - Low
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as Low.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No Single Low availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as High which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


Low Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Urgency = Low

Low Volume Eligible:

No

Threshold parameters:
***% of the time, ***% of Low Availability servers will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CMDB Urgency
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
CMDB Urgency = “Low”
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.)***. Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of servers in the Low availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of servers allowed to be unavailable more than (A) = (B)*(***-.)*** ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of servers that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***% this would mean the ***server with more than *** of downtime would result in a miss of the SLA target




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



14.
2.4.h KM-MR-Server Availability - Development
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as Development.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No Single Low availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as High which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


Development Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Urgency = Development

Low Volume Eligible:

No

Threshold parameters:
***%

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CMDB Urgency
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
CMDB Urgency = “Development”
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Calculations




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



15.
2.4.i KM-MR-PHYSICAL SERVER PROVISIONING REQUEST
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the*** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure Physical Server Provisioning - Percentage of physical server installation requests that are successfully completed within the target timeframe (includes server configuration, backup and other workload automation)

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Greater than *** request is batch and will be excluded from the on-Time Completion percentage calculation.
- Time before arrival of assets will be excluded from this measurement (i.e. ticket is submitted after arrival of all necessary assets.)
- Customer Approval Time not included in SLA calculation
- Pending Time based on Valid Pending Activity
Continual Service Improvement


Supplemental definition of terms:

Yes


Measures the percentage of Physical Service Provisioning Service Requests that are fulfilled by Supplier within the required timeframe. This Service Level applies to standard configuration x86 servers


Low Volume Eligible:

Yes, provided that if any single request is not resolved within *** , then this Low Volume exception shall not apply
Threshold parameters:
***% of requests completed within ***


SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary= “Physical Server Install - UNIX/Linux – Internal” or
 “Physical Server Install – Windows – Internal”
Request ClosedDate/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



16.
2.4.j KM-MR-VIRTUAL SERVER PROVISIONING REQUEST
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:



Category:


CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A


Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the requests to add server(s) into Cloud Environment: Less than *** VM's - Percentage of server provisioning requests that are successfully completed within the target timeframe

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Greater than *** in single request is batch and will be excluded from the on-Time Completion percentage calculation.
Continual Service Improvement

Supplemental definition of terms:

Yes


Measures the percentage of Virtual Service Provisioning Requests (less than ***) that are fulfilled by Supplier within the required timeframe



Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply


Threshold parameters:
***% of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary
Work Order Summary
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Virtual Server Install - Linux - Internal
or “Virtual Server Install - Windows - Internal “
And Work Order Summary = “Provision Server” and Work Order Summary = “Service Device/QA”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Completed Date for Work Orders – Earliest Assigned Date for Work - Total Pending Time

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.






CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


17.
2.4.k KM-ENT-PATCH MANAGEMENT (Non-Enterprise)
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure Patch management: Non-Enterprise - Percentage of devices that are successfully patched within the target timeframe (from release of patch)

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Change Management
Exceptions:

- Post implementation of service pack, if Microsoft through their website releases a bug notification related to that specific Service Pack & that has caused unsuccessful implementation of patch.
- Time between NTT request for CoreLogic's approval and when CoreLogic provides its approval

Supplemental definition of terms:


Apply Patches to all instances of non-enterprise infrastructure applications including acquiring, testing, and installing multiple patches (Service Pack).

Patch management tasks include: maintaining current knowledge of available patches, deciding what patches are appropriate, ensuring that patches are installed properly, testing systems after installation, and documenting all associated procedures, such as specific configurations required.

Definition of Normal and Critical patches are part of the PPM documentation

Low Volume Eligible:

No
Threshold parameters:
***% of normal patches applied in *** and critical patches applied in ***

SLA Metrics and parameters:
(field names in OPAS)
Requested for Company
Actual Start Date/Time
Actual End Date/Time
Completed Date/Time
Exclude from SLA Reporting
Product Categorization Tier 1
Product Categorization Tier 2
Product Categorization Tier 3
Operational Categorization Tier 1
Operational Categorization Tier 2
Operational Categorization Tier 3
Excluded from SLA reporting
Logical description of the SLA calculation:
Report Criteria
Requested Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Completed Date and Time = within the SLA reporting period
Product Categorization 1 = “HARDWARE”;Product Categorization 2 = “SERVER”
Operational Category Tier 1 = “INSTALL”
Operational Category Tier 2 = “CODE”
Operational Category Tier 3 = “PATCH- MAINTENANCE”
Excluded from SLA Reporting <>”Yes”
Performance Rating = ***
Priority = Medium (target is Normal)
Priority = High (target is Critical)

Calculations
Critical Patches SLA = Complete Date/time - Submit Date/Time Date/Time (Should be equal to ***)

Normal Patches SLA = Complete Date/time - Submit Date/Time (Should be equal to ***)

Service Level Achievement = (Total number of Enterprise Patches that are successfully installed in accordance with SLA/ Total number of Enterprise Patches that are scheduled to be completed during the Measurement Period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.






CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



18.
2.5.a CSL-Storage-Availability
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of the Storage Service. Service Availability is defined by availability of storage frames, NAS appliances, and SAN connectivity.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB. Will be measured using an Incident RCA based measurement approach.

Exceptions:

- No Single Storage availability device could cause an SLA miss, unless that single device is unavailable for more than ***.
Continual Service Improvement

Supplemental definition of terms:

Yes

To determine the impact and duration to service availability, the following process is adhered. True impact and duration are determined by analyzing the MIM communications, AIR & RCA. With that extracted start & end times (Excluding any scheduled maintenance downtime) a CI unavailability record is created on the parent incident management record to reflect & report the service impact duration.

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of Storage Systems will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
Product Category Tier 3
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CoreLogic”,”Rels”,”Finiti”,”Stars”
Priority = High or Critical
Product Category Tier 1 = Hardware, Service
Product Category Tier 2 = Storage
Product Category Tier 3 = Storage, SAN Array, NAS, SAN Router, SAN Switch
Service Tier = Storage
Site group = Data Center
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes

Note: Any incident or unavailability record may be eligible, if the ticket categorization was not entered properly and outage was discovered to be Service related based on RCA.

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of devices in the Storage availability pool (B)
*Unit count (B) total is audited ***

Step 3. Calculate (C) = The count of Storage devices allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of Storage devices that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***%, this would mean the fourth device with more than *** of downtime would result in a miss of the SLA target.



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



19.
2.5.b KM-STORAGE-REQUEST FOR TIER 1,2,3 FOR < 100 TB
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of requests that are successfully completed within the target timeframe - Tier 1, 2, 3 Storage Provisioning <***% of allocated

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Any Storage provisioning requests which exceed (in sum) more than ***% of allocated storage during the designated Measurement Period will be excluded.
- Locally attached storage
- Third Party Hardware Exception
Continual Service Improvement

Supplemental definition of terms:

Yes

Measures the percentage of Tier 1, 2, and 3 storage configuration service requests, less than 100TB of all allocated storage, that are performed within the required timeframe during the Measurement Period
Allocated Storage is equivalent last month’s storage capacity report which will be used a monthly baseline for the ***% value.

Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply

Threshold parameters:
***% of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Server Storage Request” (question included at the work order level to indicate whether the request Total Size in GB)
Request Closed Date/Time is within the reporting period
Total Size in GB <100 TB
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



20.
2.5.c KM-STORAGE-REQUEST FOR TIER 1,2,3 FOR >100 TB
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of requests that are successfully completed within the target timeframe - Tier 1, 2, 3 Storage Provisioning >***% of allocated

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

-Locally attached storage
Continual Service Improvement

Supplemental definition of terms:

Yes

Measures the percentage of Tier 1, 2, and 3 storage configuration service requests, more than 100TB of all allocated storage, that are performed within the required timeframe during the Measurement Period



Low Volume Eligible:

No


Threshold parameters:
***% of requests completed within ***


SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary Name = “Server Storage Request”)
Request Closed Date/Time is within the reporting period
Total Size in GB >100TB
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



21.
2.5.d KM-STORAGE - ADD BACKUP REQUEST TO SERVER
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of requests to add servers to backup that are successfully completed within the target timeframe - Add backup service

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

- Add backup service requests - If the number of Add backup service requests is greater than *** per business day, this will be considered a batch submission and executed as a project.

Continual Service Improvement

Supplemental definition of terms:


Yes

Measures the percentage of new backup Service Requests that are performed within the required timeframe during the Measurement Period


Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply


Threshold parameters:
***% of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Server Back-up Schedule”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



22.
2.5.e KM-STORAGE - EMERGENCY RESTORE REQUEST FROM BACKUP
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of restoration requests for business critical restore of file(s), folder(s), sub directory which is currently offsite completed within the target timeframe

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management
Exceptions:

- The *** or more incidents per day will be excluded from SLA calculation.
- Batch emergency restores will be excluded from the On-Time Completion percentage calculation.

Supplemental definition of terms:


Measures the percentage of emergency restore Incidents that are initiated via the physical restore within the required timeframe during the Measurement Period



Low Volume Eligible:

No


Threshold parameters:
***% of incidents initiated within ***


SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Product Name (Emergency restores will always be done via incident t)
Pending Time
Incident Assigned Date/Time
Incident Resolved Date/Time
Product Name
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Incident Resolved date/time within the reporting period
Product Name = EMERGENCY RESTORE
Excluded in SLA Reporting <> Yes

Calculations
Service Level Achievement Total Number of Emergency Restore Tickets Resolved within ***/Total Number of Emergency Restore Tickets



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



23.
2.5.f KM-STORAGE-BACKUP-JOB FAILURE
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of backup job failures that are successfully addressed within the target timeframe - Business critical, backup job failure

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

Incident Ticket
Exceptions:

 Restoration Time does not include the following:
- Time that Incident Tickets are in "pending mode" due to previously unknown third party software defects.
- Time that Incident Tickets are in "suspend mode" for equipment related failures at non Dell facilities.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA in order to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA

Supplemental definition of terms:


Measures the percentage of backup job failures that are successfully completed within the required timeframe during the Measurement Period



Low Volume Eligible:

Yes, provided that if any single failure successfully completed is not resolved within ***, then this Low Volume exception shall not apply


Threshold parameters:
***% of failures are successfully completed within ***


SLA Metrics and parameters:
(field names in OPAS)
Incident Assigned Date/Time
Incident Resolved Date/Time
Operational Category Tier 3
Excluded from Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, RELS”RELS”, “FINITI”, “STARS”
Incident Resolved Date/Time within the reporting period
Resolution Operational Category Tier 3 = BACK-UP FAILURE
Or Summary = “*Net Back-up*”

Calculations
Service Level Achievement = Total Incident Records Resolved within 2 days for Resolution Operational Category is Back-up Failure /Total Incident Records with Resolution Operational Category Tier 3 = BACK-UP FAILURE or Summary = “*Net Back-up*”



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



24.
2.5.g KM-STORAGE-BACKUP-RESTORE SEMIANNUAL REQUEST COMPLETION
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percentage of restores successfully completed within the target timeframe - CoreLogic requested restore of up to ***% of the backup media per/ semiannual or per compliance policy

Associated hours of Operation:

Reported semi-annually
Reporting Tools:

OPAS Change Records
Exceptions:

 

Supplemental definition of terms:


Measures the percentage of random restores that are successfully completed during designated Change Window



Low Volume Eligible:

Yes, provided that if any single restore is not resolved within ***, then this Low Volume exception shall not apply


Threshold parameters:
***% of restores are successfully completed without fault and within ***.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Changed Assigned Date/Time
Change Resolved Date/Time
Performance Rating
Operational Categorization Tier 3
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Change Resolved Date and Time is within the reporting period
Performance Rating = 5 / Successful implementation
Operational Categorization 3 = BACK-UP RESTORE SEMIANNUAL REQUEST

Calculations
Service Level Achievement = Total Number of Change Records completed within ***/Total Number of Change Records on Back-up Restore Semiannual Request



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



25.
2.7.a CSL-T2L-Availability (Replaces Mainframe Availability CSL)
DATES
SLA Start Date:
9/1/2017
First Reporting Period:
9/30/2017
First Report Date:
10/7/2017
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as T2L.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No single T2L availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as T2L which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


T2L Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of T2L Availability servers will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes
Review AIR/PM to determine if T2L server pool is impacted (audited availability pool quarterly with TAX team).

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of servers in the T2L availability pool (B)

Step 3. Calculate (C) = The count of servers allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of T2L servers that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***% this would mean that *** server with more than *** of downtime would result in a miss of the SLA target.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



26.
2.7.b CSL-T2L-TPE/BPE Availability (Replaces CICS Availability CSL)
DATES
SLA Start Date:
9/1/2017
First Reporting Period:
9/30/2017
First Report Date:
10/7/2017
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this SLA is to measure the Availability of an individual cluster or System that are classified as TPE/BPE.

Associated hours of Operation:

24x7
Reporting Tools:

OPAS Incident Management and Change Management, Atrium CMDB
Exceptions:

- No single TPE/BPE availability server could cause an SLA miss, unless that single server is unavailable for more than ***.
- Lack of availability caused by CoreLogic or CoreLogic’s Third Party Contractor as documented in Supplier’s Root Cause Analysis
- Third Party Hardware Exception
- If any node of the cluster is not available and the cluster itself is available then cluster is considered available.
- Any server classified as TPE/BPE which does not meet the minimal configuration requirements as defined in Resource Unit Definition Schedule A 4.2 at the time of the Incident will be excluded
- Unavailability caused by a CoreLogic employee, as documented in the Root Cause Analysis
- Scheduled Downtime due to Scheduled Changes

Supplemental definition of terms:


High Availability Server detailed attributes presented in Appendix C.
Configured Items related to this SLA will be:
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER

Low Volume Eligible:

No
Threshold parameters:
***% of the time, ***% of TPE/BPE Availability servers will be available.

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Incident Assigned Date/Time
Incident Priority
Incident ID
Incident Resolved Date/Time
Product Category Tier 1
Product Category Tier 2
CI Unavailability Scheduled Actual Start Date/Time
CI Unavailability Scheduled Actual End Date/Time
CI Unavailability Unscheduled Actual Start Date/Time
CI Unavailability Unscheduled Actual End Date/Time
Related Change to Incident Record
Excluded from SLA Reporting




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:

Report Criteria
Supporting Company = “CORELOGIC”,”RELS”,”FINITI”,”STARS”
Incident Priority = High or Critical
Product Catalog Tier 1= HARDWARE
Product Catalog Tier 2 = SERVER
Incident Resolved Date/Time = Period of Reporting
Incident Related Changes for All incidents during the Period of Reporting
Excluded from SLA Reporting <> Yes
Review AIR/PM to determine if TPE/BRE server pool is impacted (audited availability pool quarterly with TAX team).

Calculations
Step 1. Calculate (A) = Unavailability minutes per server allowed = ****(***-.***). Round up to nearest whole number = ***. This is not recalculated ***.

Step 2. Determine the count of servers in the TPE/BPE availability pool (B)

Step 3. Calculate (C) = The count of servers allowed to be unavailable more than (A) = (B)*(***-.***) ceiling up to nearest whole number.
Example: if the unit count is *** units, then the result of *** would be rounded up to ***.

Step 4. Calculate (D) = Based on CI unavailability & RCA, determine the count of TPE/BPE servers that were unavailable for more than step 1 (A). If (D) is more than step 3 (C) then the SLA would be a miss.

Example: If the unit count is *** units with a unit target of ***% and an availability target of ***% this would mean that *** server with more than *** of downtime would result in a miss of the SLA target.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



27.
2.7.c KM-EAPM-REQUEST-MONITORING SETUP (SYNTHETIC TRANSACTION)
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percent of Synthetic Transaction monitoring setup completed in the timeframe described.

Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests
Exceptions:

 

Supplemental definition of terms:


Measures the amount of time between receipt of a monitoring setup request and the completion of the monitoring setup activity



Low Volume Eligible:

Yes, provided that if any single request is not resolved within *** times, then this Low Volume exception shall not apply


Threshold parameters:
***% of transactions (web page calls) completed in the target timeframe:
    *** or fewer transactions - ***
    *** transactions - ***
    *** transactions - ***


SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Closed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Application Monitoring -BAC “
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes
No. of Trans (field in Details section of Work Order)

Calculations
Request SLA = Request Completed Date/Time – Request Approval Date/Time- Total Pending Time based on number of transactions

Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



28.
2.1.a KM-CAP-NEW USER REQUEST
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
The intent of this Service Level is to measure the Percent of new user account setup requests completed within the target timeframe
Associated hours of Operation:

Business Hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Service Requests, OPAS Incidents
Exceptions:

- Any hold in approval processes or Change Request initiated by CoreLogic
- Any valid Pending events

Supplemental definition of terms:


Measures the time taken between processing of approved request to setup the account(s) SecAdmin will be the support group for Dell that handles User Access New User Provisioning Request will include:
    Active Directory
    Check Writer
    CRM
    Oracle
    Unix
    VPN
    TeamForge
    TimeTrack
    Mainframe
    RightFax
    Enterprise or Business Unit Software (list provided in the NUP form where Dell is required to provision logical access)
    AS/400 iseries

Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply

Threshold parameters:
***% of requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Work Order Assigned Date/Time
Work Order Completed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
(Request Summary = “New User Provisioning “ and
Work Order Summary = “*SLA
or Request Summary = “*TEMP NUP CLGX-Oracle Access” or *TEMP NUP- SecAdmin- Mainframe/zSeries or *TEMP NUP UNIX User Addition or *TEMP NUP CLGX-Time Tracker or *TEMP NUP Digital Certificate (VPN) or
Request Closed Date/Time is within the reporting period
Work Order Complete Date/Time
Work Order Assigned Date/Time
Excluded in SLA Reporting <> Yes

AND All incident records with Summary = “PROVISION_CLGX:New User Activation*”

Calculations
Request SLA = Latest Work order Completed Date/Time – Work order earliest Assigned Date and Time- Total Pending Time

%Service Level Achievement (Number of successfully completed requests with Request SLA /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



29.
2.1.b1/2.1.b2 CSL-TERMINATION REQUEST
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Critical Service Level

Interpreted Intent of SLA:
The intent of this Service Level is to measure whether requests are resolved in a timely manner according to Severity Levels.

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Request Management, OPAS Incident Records
Exceptions:

- Any hold in approval processes or Change Request initiated by CoreLogic
- Any termination requests over 40 during a given day will not be measured
-Pending time from valid Pending Event

Supplemental definition of terms:


Resolution Time means the elapsed time from the record being created to the time the record is completely resolved. Termination Request will include:
    Active Directory ID
    CRM
    Mainframe
    Oracle
    Remote Access/VPN
    UNIX
    RightFax
    TeamForge
    TimeTracker
    AS/400-iSeries
    Enterprise Business Applications

Low Volume Eligible:

No

Threshold parameters:
***% within *** and ***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Terminate A Resource (employee/contractor/vendor) and
Work Order Summary is = “Terminate System Access” or Terminate Mainframe Access or Terminate Remote Access VPN
AND All incident records for the period where
Summary = “TERMINATION_CLGX:Termination*”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes
Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Two (2) thresholds will be computed :
Threshold (1)
Service Level Achievement (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%
 
Threshold (2)
Service Level Achievement (Number of successfully completed requests within *** /Total number of requests in the measurement period) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



30.
2.1.c1/2.1.c2 KM-CAP-FTP Add Account
DATES
SLA Start Date:
12/1/2017
First Reporting Period:
12/31/2017
First Report Date:
1/5/2018
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Interpreted Intent of SLA:
The intent of this SLA is to measure the completion time duration for FTP Add Account SRM.


Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Request Management
Exceptions:

If over 25 requests per month the overage will be excluded from the measurement.
Supplemental definition of terms:

N/A
Low Volume Eligible:

Yes, provided that if any single request is not resolved within ***, then this Low Volume exception shall not apply


Threshold parameters:
***% completed within *** & ***% completed within ***

 
 
Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = FTP Add Account
Request Question = FTP Server
Request Answer = ANAFTP02 (FTP)
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes
Pending time is included

Calculations
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


31.
3.0.a KM-Security Audit - Critical
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
KM-Security Audit-Critical

Associated hours of Operation:

Business hours – *** = 1 business day  
Reporting Tools:

OPAS Request Management
Exceptions:

Continual Service Improvement



Yes
Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Security Audit Compliance Request” and Questions “Request Type” = “Client Audit”, “EI3PA/PCI”, “SOX”, “Remediation”, “SSAE16”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



32.
3.0.b KM-Security Audit - Normal
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
KM-Security Audit-Normal

Associated hours of Operation:

Business hours – *** = 1 business day  
Reporting Tools:

OPAS Request Management
Exceptions:

 
Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “Security Audit Compliance Request” and Questions “Request Type” = “Client Audit”, “EI3PA/PCI”, “SOX”, “Remediation”, “SSAE16”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



33.
3.0.c KM-Litigation Hold
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
KM-Litigation Hold

Associated hours of Operation:

Business hours – *** = 1 business day  
Reporting Tools:

OPAS Request Management
Exceptions:

 
Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS.”
Request Summary = “Place Litigation Hold”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



34.
3.0.d KM-HR Electronic Monitoring
DATES
SLA Start Date:
8/1/2013
First Reporting Period:
8/31/2013
First Report Date:
9/6/2013
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
KM-HR Elecmon

Associated hours of Operation:

Business hours – *** = 1 business day  
Reporting Tools:

OPAS Request Management
Exceptions:

 
Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Request Summary = “HR ElecMon”
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



35.
2.3.e KM-SM-GENERAL REQUEST FULFILMENT
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Requests that are completed within the target timeframe. Measures the time interval between a Request being created in the service management tool to the time of work order completion

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Request Management
Exceptions:

Continual Service Improvement
No

Yes

Supplemental definition of terms:


N/A
Low Volume Eligible:

No
Threshold parameters:
***% of Requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Pending Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Supporting Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
All Request Management tickets that are not included in previous SLAs
Request Closed Date/Time is within the reporting period
Excluded in SLA Reporting <> Yes

Calculations
Request SLA = Latest Work Order Completed Date/Time – earliest Work Order Assigned Date/Time

Service Level Achievement
Number of Requests with SLA Elapsed time under the threshold / Total number of Requests for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



36.
2.3.f KM-SM-CHANGE SUCCESS
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Change performance rating will be agreed upon by both Dell and CoreLogic
Associated hours of Operation:

N/A
Reporting Tools:

OPAS Change Management
Exceptions:

 

Supplemental definition of terms:

 
Low Volume Eligible:

 
Threshold parameters:
***% of closed changes successfully implemented

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Status
Status Reason
Change Completed Date/Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Location Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Status = Closed
Status Reason = “Automatically Closed”, “Final Review Complete”, “Successful”
Excluded in SLA Reporting <> Yes

Service Level Achievement
Number of Changes with SLA criteria / Total number of changes for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



37.
2.3.g KM-SM-CHANGE CAUSING OUTAGES
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Change performance rating will be agreed upon by both Dell and CoreLogic.

Associated hours of Operation:

N/A
Reporting Tools:

OPAS Change Management, Incident Management
Exceptions:

 

Supplemental definition of terms:

 
Low Volume Eligible:

 
Threshold parameters:
< ***% of Change Requests causing outages (critical or high incident)

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company
Status
Status Reason
Change Completed Date/Time
Excluded in SLA Reporting

Logical description of the SLA calculation:
Report Criteria
Location Company = “CORELOGIC”, “FINITI”,”RELS”,”STARS”
Status = Closed
Related Incident with Submit Date/Time within 24 hours and limited to 15 natural days after Change scheduled start date/time
Excluded in SLA Reporting <> Yes

Service Level Achievement
Number of Changes with SLA criteria / Total number of changes for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



38.
2.3.h KM-SM-INCIDENT MANAGEMENT - MEDIUM
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Incident Handling Medium: Percent of Medium Incidents that are restored within the target timeframe. Measures the time interval between an Incident record being registered in the service management tool for Medium Incidents to the time normal service operation is restored via implementing a solution to the known error or by employing a workaround.

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management
Exceptions:

Restoration Time does not include the following:
- Time that Incident Tickets are in "suspend mode" due to previously unknown third-party software defects.
- If there are instances or circumstances at a non-Dell facility where equipment failures (outside of equipment that we support) fail and that inhibits/prohibits us from rendering services, then it’s suspended.  Some of this could include Power failures, local equipment not in our support, etc .
- Time incurred restoring Application data and/or functionality from tape media after Supplier has returned Equipment to service.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA in order to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA.

Incidents and outages due to the following incident management exclusion reasons:
2.2.a.1 Scrub, Incident deemed misclassified by CoreLogic exclusion committee.
2.2.a.2 Scrub, Non-Supplier supported site.
2.2.a.3 Scrub, Server/System not in production (not in-service).
2.2.a.4 Scrub, CoreLogic Application related outage that is not Supplier infrastructure caused.
2.2.a.5 Scrub, duplicate Incident record.
2.2.a.6 Scrub, Scheduled Downtime per system.
2.2.a.7 Scrub, Monitoring Alerts, No outage or CoreLogic impact noted.
2.2.a.8 Scrub, Eligible Recipient requested escalation for Emergency Change, No CoreLogic outage.
2.2.a.9 Scrub, CoreLogic requested the Incident Severity be raised to bypass process/lead times.
2.2.a.10 Scrub, Non-Supplier Third Party outage.
2.2.a.11 Scrub, Final CoreLogic Resolver Group.
2.2.a.12 Scrub, Incident related to Supplier reported known errors where solution/remediation not approved by CoreLogic.

Continual Service Improvement

Supplemental definition of terms:


Yes
Low Volume Eligible:

No
Threshold parameters:
***% of Requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company+*
All Incident Recording during the Reporting Period that are not already include in previous SLAs
Priority*
Status.Resolved. Date/TIME
Opened Date/Time
Total Pending Time




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
(a) Company+*="CoreLogic ", “STARS”, “RELS”,”FINITI”
(b) Status.Resolved Date/TIME is within the data range selected for running the report
(c) Priority = “Medium”
(d) Opened Date/Time
(e) Exclude from SLA Reporting <> “Yes”

Calculations
Time to restore service = Status Resolved Date/Time - Opened Date/Time – Pending Time

Service Level Achievement
Number of Incidents with SLA Elapsed time under the threshold / Total number of Incidents for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



39.
2.3.i KM-SM-INCIDENT MANAGEMENT - LOW
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Incident Handling Medium: Percent of Medium Incidents that are restored within the target timeframe. Measures the time interval between an Incident record being registered in the service management tool for Medium Incidents to the time normal service operation is restored via implementing a solution to the known error or by employing a workaround.

Associated hours of Operation:

Business hours see 1.4.8 Time Definitions  
Reporting Tools:

OPAS Incident Management
Exceptions:

Restoration Time does not include the following:
- Time that Incident Tickets are in "suspend mode" due to previously unknown third-party software defects.
- If there are instances or circumstances at a non-Dell facility where equipment failures (outside of equipment that we support) fail and that inhibits/prohibits us from rendering services, then it’s suspended.  Some of this could include Power failures, local equipment not in our support, etc .
- Time incurred restoring Application data and/or functionality from tape media after Supplier has returned Equipment to service.
- Third Party Hardware Exception
- Adjustments to the Service Levels approved by CoreLogic in its sole discretion pursuant to the last sentence of Section 4.4 of the MSA in order to permit the performance of new or additional work activities as contemplated by Section 4.4 of the MSA.

Incidents and outages due to the following incident management exclusion reasons:
2.2.a.1 Scrub, Incident deemed misclassified by CoreLogic exclusion committee.
2.2.a.2 Scrub, Non-Supplier supported site.
2.2.a.3 Scrub, Server/System not in production (not in-service).
2.2.a.4 Scrub, CoreLogic Application related outage that is not Supplier infrastructure caused.
2.2.a.5 Scrub, duplicate Incident record.
2.2.a.6 Scrub, Scheduled Downtime per system.
2.2.a.7 Scrub, Monitoring Alerts, No outage or CoreLogic impact noted.
2.2.a.8 Scrub, Eligible Recipient requested escalation for Emergency Change, No CoreLogic outage.
2.2.a.9 Scrub, CoreLogic requested the Incident Severity be raised to bypass process/lead times.
2.2.a.10 Scrub, Non-Supplier Third Party outage.
2.2.a.11 Scrub, Final CoreLogic Resolver Group.
2.2.a.12 Scrub, Incident related to Supplier reported known errors where solution/remediation not approved by CoreLogic.

Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% of Requests completed within ***

SLA Metrics and parameters:
(field names in OPAS)
Supporting Company+*
All Incident Recording during the Reporting Period that are not already include in previous SLAs
Priority*
Status.Resolved. Date/TIME
Opened Date/Time
Total Pending Time




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
(a) Company+*="CoreLogic ", “STARS”, “RELS”,”FINITI”
(b) Status.Resolved Date/TIME is within the data range selected for running the report
(c) Priority = “Low”
(d) Opened Date/Time
(e) Exclude from SLA Reporting <> “Yes”

Calculations
Time to restore service = Status Resolved Date/Time - Opened Date/Time – Pending Time

Service Level Achievement
Number of Incidents with SLA Elapsed time under the threshold / Total number of Incidents for the Measurement Period * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



40.
2.3.j KM-SM-OPAS AVAILABILITY
DATES
SLA Start Date:
3/1/2015
First Reporting Period:
3/31/2015
First Report Date:
4/7/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING

Contract Reference:


Category:
 

CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Percentage OPAS Availability. OPAS Availability consists of time the OPAS ticketing system is fully available to users.

Associated hours of Operation:

24X7 see 1.4.8 Time Definitions  
Reporting Tools:

OPAS outage records
Exceptions:

 

Supplemental definition of terms:

 
Low Volume Eligible:

No


Threshold parameters:
***%


SLA Metrics and parameters:
(field names in OPAS)
Calendar
Maintenance Window
Performance Tool

Logical description of the SLA calculation:
Report Criteria
Use normal group & device (region/job name) approach where downtime are set tin OPAS with information on date, start time and end time of downtime.
Represented Total Downtime inclusive of planned change.

Calculations
Service Level Agreement = Total Number of Hours Uptime/Expected Uptime x 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



41.
2.2.k KM-ENT-Purchase Order Creation
DATES
SLA Start Date:
7/1/2015
First Reporting Period:
8/1/2015
First Report Date:
9/5/2015
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Measures Dell Purchase Orders (PO) created within the target timeframe, for hardware being purchased on CoreLogic’s behalf at CoreLogic’s request. This will encompass RU based server related and/or any approved project based purchase requests regardless of hardware or vendor. Measures the time interval between an OPAS request or project Work Order/Change Order being approved to the time of purchase order creation.

Associated hours of Operation:

Business hours - *** = 1 business day
Reporting Tools:

OPAS
Exceptions:

Any other purchase requests that are not RU based or through an approved project. Circuits are excluded, but circuit hardware is not.
CoreLogic cancellations of a PO request.



Supplemental definition of terms:

For the RU based purchase requests, the request types include:
• Physical Server Install – (All Platform/Types)
• Server Storage Request
• Server Request – Hosted

For approved project based purchase requests, request types are irrelevant. Reference the methodology below.

Low Volume Eligible:

Yes, provided that if any single purchase request is not completed within ***, then this Low Volume exception shall not apply.


Threshold parameters:
***% of purchase orders created in the target timeframe:

*** (***) regardless of vendor or hardware type

Note: *** = 1 business day

SLA Metrics and parameters:
(field names in OPAS)

Supporting Company
Request Summary Name
Request Approval Date/Time
Request Assigned Date/Time
Request Completed Date/Time
Excluded in SLA Reporting



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


DATES
Logical description of the SLA calculation:
Report Criteria
For RU based purchase requests in OPAS:
(a) Company+*="CoreLogic ", “STARS”, “RELS”
(b) Request Summary in:
• Physical Server Install – (All Platform/Types)
• Server Storage Request
• Server Request – Hosted
(c) Request Approval Date/Time

For all types, to determine monthly data inclusion:
Dell Internal SRM Work Order creation Timestamp for Dell hardware or Ariba PO creation Timestamp for non-Dell hardware is within the date range selected for running the report

Calculations
For RU based purchase requests:
SLA = Dell Internal SRM PO Work Order creation Timestamp for Dell hardware or Ariba PO creation Timestamp for non-Dell hardware – OPAS Request Approval Date/Time

For approved project based requests:
SLA = Dell Internal SRM PO Work Order creation Timestamp for Dell hardware or Ariba PO creation Timestamp for non-Dell hardware – Work Order/Change Order Signature Date/Time

Service Level Achievement (Number of successfully completed purchase requests within SLA /Total number of purchase requests in the measurement period) * 100%

NOTE: Pending time is not excluded from measurement




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



42.
4.0.a KM-DR-Disaster Recovery Exercise - RTO
DATES
SLA Start Date:
3/1/2016
First Reporting Period:
4/1/2016
First Report Date:
4/7/2016
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Percent of Product or Business Line infrastructure that is restored within the target timeframe based on published infrastructure Recovery Time Objectives (RTO) as agreed by both parties.
Measures the on-time percentage of applicable infrastructure RTO.

Associated hours of Operation:

N/A
Reporting Tools:

DRE RTO detailed data as provided by Dell
Exceptions:

If during the measurement period, the schedule DR exercise involves first time testing of Business Line / Product infrastructure & applications those results will be excluded from this measurement. This exception would not include first time testing of application subcomponents, where the Business Line / Product had been involved in prior exercise.

Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% of infrastructure RTO objectives met in a DRE for each Product or Business Line

SLA Metrics and parameters:
(field names in OPAS)

 
Logical description of the SLA calculation:
Report Criteria
Published infrastructure RTO objectives
DRE RTO detailed data

Calculations
Service Level Achievement = (Count of infrastructure RTO objectives met in a DRE / Count of infrastructure RTO objectives in a DRE) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



43.
4.0.b KM-DR-Disaster Recovery Exercise - RPO
DATES
SLA Start Date:
3/1/2016
First Reporting Period:
4/1/2016
First Report Date:
4/7/2016
Reporting Period:
***
Reporting Frequency:
***, on or before the *** following the reporting period
UNDERSTANDING
Contract Reference:


Category:
 
CORELOGIC-Dell Schedule A-3.1(Service Level Matrix)
CORELOGIC-Dell Supplement A

Key Measurement

Interpreted Intent of SLA:
Percent of Product or Business Line infrastructure that is restored within the target timeframe based on published infrastructure Recovery Point Objectives (RPO) as agreed by both parties using data recovery systems managed by Dell. Measures the actual data recovery point vs planned data recovery point.

Associated hours of Operation:

N/A  
Reporting Tools:

DRE RPO detailed data as provided by Dell
Exceptions:

If during the measurement period, the schedule DR exercise involves first time testing of Business Line / Product infrastructure & applications those results will be excluded from this measurement. This exception would not include first time testing of application subcomponents, where the Business Line / Product had been involved in prior exercise.

Supplemental definition of terms:

 
Low Volume Eligible:

No
Threshold parameters:
***% of infrastructure RPO objectives met in a DRE for each Product or Business Line

SLA Metrics and parameters:
(field names in OPAS)

 
Logical description of the SLA calculation:
Report Criteria
Published infrastructure RPO objectives
DRE RPO detailed data

Calculations
Service Level Achievement = (Count of infrastructure RPO objectives met in a DRE / Count of infrastructure RPO objectives in a DRE) * 100%



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



3.
Document History
The table below is used to track the actions taken upon this document and provide a history of when the action was taken, whom by and the action itself (update, review, approval or publication).

Date
Action
Name
Version
8/15/2017
Initial creation
***
1.0
5/15/2018
Added PC Refresh KM 2.6.f and added CSI flags as appropriate
***
1.1
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.




MASTER SERVICES AGREEMENT

between

CORELOGIC SOLUTIONS, LLC

and

DELL MARKETING L.P.

July 19, 2012



SUPPLEMENT A


SCHEDULE A-3.1

SERVICE LEVEL MATRIX



This document contains proprietary and confidential information of CoreLogic and Dell. The information contained in this document may not be disclosed outside either Party without the prior written permission of the other Party.




CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.



INTRO

"Third Party Hardware Exception" means Supplier's failure to meet the timing requirements of any single Unit that is subject to the applicable Service Level shall be excused if and to the extent such failure is caused by the failure of a third party vendor to repair or replace Equipment, other than Equipment that is included within Supplier’s cloud environment; but only if (i) Supplier uses commercially reasonable efforts to cause such third party vendor to perform within the time frame required for such Unit, (ii) Supplier notifies CoreLogic promptly after such third party vendor’s failure or delay and (iii) Supplier documents such failure in a Root Cause Analysis after such failure. Any time for which Supplier’s failure to meet the applicable timing requirement is excused by the immediately preceding sentence shall be removed (i.e., excluded) from the calculation of total time to restore such Unit as defined in the Service Level definition. For purposes of the Third Party Hardware Exception, "Unit" means the applicable unit of measurement for the applicable Service Level (e.g., Incident or other applicable unit that is being measured in accordance with the definition and formula for such Service Level).































SLA REFERENCES

Service Area
Service Level
Category
Weighting



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


Service Management
2.2.a CSL-SM-Incident Handling - Critical
Critical Service Level
***
Service Management
2.2.b CSL-SM-Incident Handling - High
Critical Service Level
***
Service Management
2.2.c KM-SM-INCIDENT COMMUNICATION
Key Measure
 
Service Management
2.2.d KM-SM-PERCENTAGE OF INCIDENTS THAT ARE ACCURATELY TRIAGED
Key Measure
 
Service Management
2.2.3 KM-SM-Incident Communication - Continual
Key Measure
 
Service Management
2.2.f1/2.2.f2 KM-SM-Problem Management-Service Impact Document Delivery (AIR and RCA)
Key Measure
 
Service Management
2.2.g KM-SM-ASSET INVENTORY- ACCURACY
Key Measure
 
Service Management
2.2.h KM-SM-CSAT Operations Managers
Key Measure
 
Service Management
2.2.h.1 KM-SM-CSAT Operations Managers Service Improvement (SI)
Key Measure
 
Service Management
2.2.i KM-SM-CSAT-END USERS
Key Measure
 
Service Management
2.2.j KM-SM-CSAT DROP-END USERS
Key Measure
 
Service Desk
2.3.a CSL-SD-AVERAGE SPEED TO ANSWER
Critical Service Level
***
Service Desk
2.3.b KM-SD-AVERAGE HANDLE TIME
Key Measure
 
Service Desk
2.3.c KM-SD-ABANDON RATE
Key Measure
 
Service Desk
2.3.d CSL-SD-FIRST CALL RESOLUTION
Critical Service Level
***
Desktop
2.6.a KM-DT-END-USER DEVICE NEW USER SETUP
Key Measure
 
Desktop
2.6.b1/2.6.b2 KM-DT-END-USER DEVICE SERVICES SUPPORT
Key Measure
 
Desktop
2.6.c KM-DT-END-USER DEVICE TERMINATION
Key Measure
 
Desktop
2.6.d KM-DT-REQUEST-PACKAGING (DEVELOP AND PUSH)
Key Measure
 
Desktop
2.6.e1/2.6.e2 KM-DT-END-USER DEVICE MOVES/ADDS/CHANGES
Key Measure
 
Desktop
2.6.f KM-DT-CoreLogic PC Refresh
Key Measure
 
Enterprise
2.4.a KM-ENT-PATCH MANAGEMENT SERVERS
Key Measure
 
Enterprise
2.4.b KM-ENT-PERCENTAGE AVAILABILITY OF RIGHTFAX SERVICE
Key Measure
 
Enterprise
2.4.c CSL-ENT-PERCENTAGE AVAILABILITY OF EXCHANGE EMAIL SERVICE
Critical Service Level
***
Enterprise
2.4.d CSL-ENT-PERCENTAGE AVAILABILITY OF CITRIX METAFRAME
Critical Service Level
***
Network
2.9.a CSL-NW-Data Center LAN Availability
Critical Service Level
***
Network
2.9.b CSL-NW-Data Center WAN Availability
Critical Service Level
***
Network
2.9.c KM-NW-Campus LAN Availability
Key Measure
 
Network
2.9.d1/2.9.d2 KM-NETWORK-REQUEST-FIREWALL, IP ADDRESS, HTTP PORT REQUESTS
Key Measure
 
Network
2.9.e CSL-NW-VOIP Availability
Critical Service Level
***
Network
2.9.f KM-NW-Call Center/Call Monitoring Requests
Key Measure
 
Network
2.9.f1 KM-NW-Contact Center Call Flow
Key Measure
 
Midrange
2.4.e CSL-MR-Server Availability - High
Critical Service Level
***



CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED, AND RULE 24b-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH “***”.


Midrange
2.4.f CSL-MR-Server Availability - Standard
Critical Service Level
***
Midrange
2.4.g KM-MR-Server Availability - Low
Key Measure
 
Midrange
2.4.h KM-MR-Server Availability - Development
Key Measure
 
Midrange
2.4.i KM-MR-PHYSICAL SERVER PROVISIONING REQUEST
Key Measure
 
Midrange
2.4.j KM-MR-VIRTUAL SERVER PROVISIONING REQUEST
Key Measure
 
Midrange
2.4.k KM-ENT-PATCH MANAGEMENT (Non-Enterprise)
Key Measure
 
Storage
2.5.a CSL-Storage-Availability
Critical Service Level
***
Storage
2.5.b KM-STORAGE-REQUEST FOR TIER 1,2,3 FOR < 100 TB
Key Measure
 
Storage
2.5.c KM-STORAGE-REQUEST FOR TIER 1,2,3 FOR >100 TB
Key Measure
 
Storage
2.5.d KM-STORAGE - ADD BACKUP REQUEST TO SERVER
Key Measure
 
Storage
2.5.e KM-STORAGE - EMERGENCY RESTORE REQUEST FROM BACKUP
Key Measure
 
Storage
2.5.f KM-STORAGE-BACKUP-JOB FAILURE
Key Measure
 
Storage
2.5.g KM-STORAGE-BACKUP-RESTORE SEMIANNUAL REQUEST COMPLETION
Key Measure
 
Mainframe
2.7.a CSL-T2L-Availability (Replaces Mainframe Availability CSL)
Critical Service Level
***
Mainframe
2.7.b CSL-T2L-TPE/BPE Availability (Replaces CICS Availability CSL)
Critical Service Level
***
EAPM
2.7.c KM-EAPM-REQUEST-MONITORING SETUP (SYNTHETIC TRANSACTION)
Key Measure
 
CAP
2.1.a KM-CAP-NEW USER REQUEST
Key Measure
 
CAP
2.1.b1/2.1.b2 CSL-TERMINATION REQUEST
Critical Service Level
***
CAP
2.1.c1/2.1.c2 KM-CAP-FTP Add Account
Key Measure
 
Compliance
3.0.a KM-Security Audit - Critical
Key Measure
 
Compliance
3.0.b KM-Security Audit - Normal
Key Measure
 
Compliance
3.0.c KM-Litigation Hold
Key Measure
 
Compliance
3.0.d KM-HR Electronic Monitoring
Key Measure
 
Service Management
2.3.e KM-SM-GENERAL REQUEST FULFILMENT
Key Measure
 
Service Management
2.3.f KM-SM-CHANGE SUCCESS
Key Measure
 
Service Management
2.3.g KM-SM-CHANGE CAUSING OUTAGES
Key Measure
 
Service Management
2.3.h KM-SM-INCIDENT MANAGEMENT - MEDIUM
Key Measure
 
Service Management
2.3.i KM-SM-INCIDENT MANAGEMENT - LOW
Key Measure
 
Service Management
2.3.j KM-SM-OPAS AVAILABILITY
Key Measure
 
Enterprise
2.2.k KM-ENT-Purchase Order Creation
Key Measure
 
DR
4.0.a KM-DR-Disaster Recovery Exercise - RTO
Key Measure
 
DR
4.0.b KM-DR-Disaster Recovery Exercise - RPO
Key Measure
 






Exhibit 31.1

CERTIFICATIONS

I, Frank D. Martell, certify that:

1.
I have reviewed this quarterly report on Form 10-Q of CoreLogic, Inc.;

2.
Based on my knowledge, this report does not contain any untrue statement of a material fact or omit to state a material fact necessary to make the statements made, in light of the circumstances under which such statements were made, not misleading with respect to the period covered by this report;

3.
Based on my knowledge, the financial statements, and other financial information included in this report, fairly present in all material respects the financial condition, results of operations and cash flows of the registrant as of, and for, the periods presented in this report;

4.
The registrant’s other certifying officer and I are responsible for establishing and maintaining disclosure controls and procedures (as defined in Exchange Act Rules 13a-15(e) and 15d-15(e)) and internal control over financial reporting (as defined in Exchange Act Rules 13a-15(f) and 15d-15(f)) for the registrant and have:

(a)
Designed such disclosure controls and procedures, or caused such disclosure controls and procedures to be designed under our supervision, to ensure that material information relating to the registrant, including its consolidated subsidiaries, is made known to us by others within those entities, particularly during the period in which this report is being prepared;

(b)
Designed such internal control over financial reporting, or caused such internal control over financial reporting to be designed under our supervision, to provide reasonable assurance regarding the reliability of financial reporting and the preparation of financial statements for external purposes in accordance with generally accepted accounting principles;

(c)
Evaluated the effectiveness of the registrant’s disclosure controls and procedures and presented in this report our conclusions about the effectiveness of the disclosure controls and procedures, as of the end of the period covered by this report based on such evaluation; and

(d)
Disclosed in this report any change in the registrant’s internal control over financial reporting that occurred during the registrant’s most recent fiscal quarter (the registrant’s fourth fiscal quarter in the case of an annual report) that has materially affected, or is reasonably likely to materially affect, the registrant’s internal control over financial reporting; and

5.
The registrant’s other certifying officer and I have disclosed, based on our most recent evaluation of internal control over financial reporting, to the registrant’s auditors and the audit committee of the registrant’s board of directors (or persons performing the equivalent functions):

(a)
All significant deficiencies and material weaknesses in the design or operation of internal control over financial reporting which are reasonably likely to adversely affect the registrant’s ability to record, process, summarize and report financial information; and

(b)
Any fraud, whether or not material, that involves management or other employees who have a significant role in the registrant’s internal control over financial reporting.

Date: July 26, 2018
 
By: /s/  Frank D. Martell
Frank D. Martell
President and Chief Executive Officer
(Principal Executive Officer)




Exhibit 31.2

CERTIFICATIONS

I, James L. Balas, certify that:

1.
I have reviewed this quarterly report on Form 10-Q of CoreLogic, Inc.;

2.
Based on my knowledge, this report does not contain any untrue statement of a material fact or omit to state a material fact necessary to make the statements made, in light of the circumstances under which such statements were made, not misleading with respect to the period covered by this report;

3.
Based on my knowledge, the financial statements, and other financial information included in this report, fairly present in all material respects the financial condition, results of operations and cash flows of the registrant as of, and for, the periods presented in this report;

4.
The registrant’s other certifying officer and I are responsible for establishing and maintaining disclosure controls and procedures (as defined in Exchange Act Rules 13a-15(e) and 15d-15(e)) and internal control over financial reporting (as defined in Exchange Act Rules 13a-15(f) and 15d-15(f)) for the registrant and have:

(a)
Designed such disclosure controls and procedures, or caused such disclosure controls and procedures to be designed under our supervision, to ensure that material information relating to the registrant, including its consolidated subsidiaries, is made known to us by others within those entities, particularly during the period in which this report is being prepared;

(b)
Designed such internal control over financial reporting, or caused such internal control over financial reporting to be designed under our supervision, to provide reasonable assurance regarding the reliability of financial reporting and the preparation of financial statements for external purposes in accordance with generally accepted accounting principles;

(c)
Evaluated the effectiveness of the registrant’s disclosure controls and procedures and presented in this report our conclusions about the effectiveness of the disclosure controls and procedures, as of the end of the period covered by this report based on such evaluation; and

(d)
Disclosed in this report any change in the registrant’s internal control over financial reporting that occurred during the registrant’s most recent fiscal quarter (the registrant’s fourth fiscal quarter in the case of an annual report) that has materially affected, or is reasonably likely to materially affect, the registrant’s internal control over financial reporting; and

5.
The registrant’s other certifying officer and I have disclosed, based on our most recent evaluation of internal control over financial reporting, to the registrant’s auditors and the audit committee of the registrant’s board of directors (or persons performing the equivalent functions):

(a)
All significant deficiencies and material weaknesses in the design or operation of internal control over financial reporting which are reasonably likely to adversely affect the registrant’s ability to record, process, summarize and report financial information; and

(b)
Any fraud, whether or not material, that involves management or other employees who have a significant role in the registrant’s internal control over financial reporting.

Date: July 26, 2018
 
By: /s/ James L. Balas
James L. Balas
Chief Financial Officer
(Principal Financial Officer)




Exhibit 32.1

Certification pursuant to 18 U.S.C. Section 1350,
as adopted pursuant to Section 906 of the Sarbanes-Oxley Act of 2002

In connection with the Form 10-Q of CoreLogic, Inc. (the “Company”) for the period ended June 30, 2018 , as filed with the Securities and Exchange Commission on the date hereof (the “Report”), I, Frank D. Martell, President, Chief Executive Officer and Principal Executive Officer of the Company, certify, pursuant to 18 U.S.C. §1350, as adopted pursuant to Section 906 of the Sarbanes-Oxley Act of 2002, that:

(1) the Report fully complies with the requirements of Section 13(a) or 15(d), as applicable of the Securities Exchange Act of 1934, as amended; and

(2) the information contained in the Report fairly presents, in all material respects, the financial condition and results of operations of the Company.

  
 
By: /s/   Frank D. Martell
 
Frank D. Martell
 
President and Chief Executive Officer
 
(Principal Executive Officer)
 
Date:
July 26, 2018

The foregoing certification is being furnished solely to accompany the Report pursuant to 18 U.S.C. §1350, and is not being filed for purposes of Section 18 of the Securities Exchange Act of 1934, as amended, and is not to be incorporated by reference into any filing of the Company, whether made before or after the date hereof, regardless of any general incorporation language in such filing.





Exhibit 32.2

Certification pursuant to 18 U.S.C. Section 1350,
as adopted pursuant to Section 906 of the Sarbanes-Oxley Act of 2002

In connection with the Form 10-Q of CoreLogic, Inc. (the “Company”) for the period ended June 30, 2018 , as filed with the Securities and Exchange Commission on the date hereof (the “Report”), I, James L. Balas, Chief Financial Officer and Principal Financial Officer of the Company, certify, pursuant to 18 U.S.C. §1350, as adopted pursuant to Section 906 of the Sarbanes-Oxley Act of 2002, that:

(1) the Report fully complies with the requirements of Section 13(a) or 15(d), as applicable, of the Securities Exchange Act of 1934, as amended; and

(2) the information contained in the Report fairly presents, in all material respects, the financial condition and results of operations of the Company.

 
 
By: /s/ James L. Balas
 
James L. Balas
 
Chief Financial Officer
 
(Principal Financial Officer)
 
Date:
July 26, 2018

The foregoing certification is being furnished solely to accompany the Report pursuant to 18 U.S.C. §1350, and is not being filed for purposes of Section 18 of the Securities Exchange Act of 1934, as amended, and is not to be incorporated by reference into any filing of the Company, whether made before or after the date hereof, regardless of any general incorporation language in such filing.