DRAFT_Credit_Bureau_Data_Solicitation_06012016.pdf

SECTION B – SERVICES AND PRICES

B.1 GENERAL

The contractor shall provide the services specified in Section C, Statement of Work, of this contract for a one-year base period and four one-year option periods at the rates specified in each Contract Line Item Number (CLIN). These prices shall be in effect through the base period of the contract, and through all option periods.

The contractor shall provide data in accordance with Section C, Statement of Work.

B.2 CONTRACT LINE ITEM NUMBER (CLIN) DESCRIPTION AND

ARRANGEMENT

This contract is a firm fixed price type contract. Prices shall be fully loaded, inclusive of all overhead, fringe benefits, general and administrative expenses, and profit for the successful performance of all specified services. Please provide prices for all required CLINs. Vendors are not required to provide prices for optional CLINs; if provided, however, the OCC maintains the unilateral right to exercise optional CLINs at the prices in the table below.

If a service identified in an optional CLIN cannot be segregated from the Core Data Set CLIN, please cite “not separately priced” in the price column of the appropriate optional CLIN.

Please check one of the following: Sample Design A Sample Design B

Base Period: September 30, 2016 – September 29, 2017 CLIN Description Firm Fixed

Price 0001 Core Data Set with Record and Tradeline Features and Associated

Documentation

(Optional)

Optional Record Features

(Optional)

Optional Tradeline Identifier

(Optional)

Optional Tradeline Features

(Optional)

Optional FICO Scores

(Optional)

Optional FICO Scores Acquired Separately by OCC (Processing and Incorporation Only)

Optional Documentation: Logical Code

(Optional)

Optional Quarterly Updates of the Core Data Set

(Optional)

Optional Additional Records (Resulting in Larger Core Data Set)

Base Period Total

Option Period One: September 30, 2017 – September 29, 2018 CLIN Description Firm Fixed

Price 1001 Core Data Set with Record and Tradeline Features and Associated

Optional Record Features

(Optional)

Optional Tradeline Identifier

(Optional)

Optional Tradeline Features

(Optional)

Optional FICO Scores

(Optional)

Optional Documentation: Logical Code

(Optional)

Optional Quarterly Updates of the Core Data Set

(Optional)

Option Period One Total

Option Period Two: September 30, 2018 – September 29, 2019

Price 2001 Core Data Set with Record and Tradeline Features and Associated

Optional Record Features

(Optional)

Optional Tradeline Identifier

(Optional)

Optional Tradeline Features

(Optional)

Optional FICO Scores

(Optional)

Optional Documentation: Logical Code

(Optional)

Optional Quarterly Updates of the Core Data Set

(Optional)

Option Period Two Total

Option Period Three: September 30, 2019 – September 29, 2020

Price 3001 Core Data Set with Record and Tradeline Features and Associated

Optional Record Features

(Optional)

Optional Tradeline Identifier

(Optional)

Optional Tradeline Features

(Optional)

Optional FICO Scores

(Optional)

Optional Documentation: Logical Code

(Optional)

Optional Quarterly Updates of the Core Data Set

(Optional)

Option Period Three Total

Option Period Four: September 30, 2020 – September 29, 2021

Price 4001 Core Data Set with Record and Tradeline Features and Associated

Optional Record Features

(Optional)

Optional Tradeline Identifier

(Optional)

Optional Tradeline Features

(Optional)

Optional FICO Scores

(Optional)

Optional Documentation: Logical Code

(Optional)

Optional Quarterly Updates of the Core Data Set

(Optional)

Optional Additional Records (Resulting in Larger Core Data Set)

Option Period Four Total Grand Total

SECTION C – STATEMENT OF WORK (SOW)

C.1. INTRODUCTION

The Office of the Comptroller of the Currency (OCC) charters, regulates, and supervises the national banks and the federal branches and agencies of foreign banks. Headquartered in Washington, DC, the OCC is responsible for promoting and assuring the safety and soundness of the country’s system of national banks and maintaining its competitiveness, efficiency, integrity, and stability in the financial marketplace.

C.2. BACKGROUND

The OCC relies on consumer credit bureau data to conduct research on credit-risk modeling and other policy-related work. The agency is committed to protecting data confidentiality. Only aggregate results (e.g. regression coefficients and tabular and graphical summaries of data that do not reveal information about individual records) will be published and/or shared with external co-authors.

The OCC seeks to purchase data with limited rights in perpetuity. The OCC shall be licensed to use data internally, and publish or share aggregate results externally.

C.3 SCOPE OF WORK

The “Credit Bureau Database” consists of all records in the vendor's nationwide consumer credit database that were archived as of June 30 of the relevant year, whether or not the records had tradelines, and whether or not they were scoreable1.

The “Core Data Set” refers to a longitudinal panel data set that is representative of the entire Credit Bureau Database. The “Base-Year Core Data Set” is the initial year of the Core Data Set.

It consists of a random sample of records drawn from the Credit Bureau Database, along with all of their associated tradelines.

Each subsequent year of the Core Data Set panel shall consist of annually updated features of the Base-Year Core Data Set records and their tradelines (other than those that are not present in the Credit Bureau Database in the update year), as well as the features of a random sample of newly opened records and their tradelines in the update year.

Records and tradelines shall be identified in a way that enables researchers to track individual records and individual tradelines over time.

1A “record” is considered the same as a “case” or “file”. The terms refer to data at the level of the “subject,” or individual.

The Core Data Set and associated deliverables are discussed in Sections C.3.1 through C.3.4 and 3.c.8. Optional data content is discussed in Section C.3.3(B)(2), C.3.3(C), and C.3.3(D)(2).

Optional sample size and data frequency deliverables are discussed in Section C.3.5.

The optional FICO score data and processing deliverable is discussed in Section C.3.6. The optional deliverable of processing and incorporation of FICO score data, purchased separately by the OCC, is discussed in section C.3.7. The optional deliverable of documentation pertaining to the provision of Logical Code in Section C.3.8.

C.3.1 SAMPLE DESIGN

The vendor shall use one of two sample designs below.

Sample Design A shall extend the timeframe of the OCC’s current Core Data Set (2005-2016).

Under Sample Design A (CLIN 0001), vendor shall supply an annual update to the Core Data Set (2017 data) during the base period of performance. In option periods one, two, three and four of performance (CLIN 1001, 2001, 3001, 4001), the vendor would supply the corresponding annual update (2018, 2019, 2020, 2021) to the Core Data Set. All annual updates to the Core Data Set shall contain detailed credit bureau data, identifiers and other features, as described in Section C.3.3, as of June 30 of each data year.

The base year (2005) of the OCC’s current Core Data Set would continue to serve as the base year of the extended panel data set. Therefore, under Sample Design A, the vendor would not deliver a Base-Year Core Data Set.

Table 1 Sample Design A

Number of Years of

Data

(1) CLINs 0001, 1001, 2001, 3001, 4001 Core Data Set

(2) Optional CLINs 0008, 1008, 2008, 3008, 4008 Add Quarterly Update

(3) Optional CLINs 0009, 1009, 2009, 3009, 4009

Add Large Sample Initial Year

(June) Final Year

(June) Initial

Quarter Final

Quarter Initial Year

(June) Final Year

(June) 1 2017 2017 Sept. 2016 Mar. 2017 2017 2017 2 2017 2018 Sept. 2016 Mar. 2018 2017 2018 3 2017 2019 Sept. 2016 Mar. 2019 2017 2019 4 2017 2020 Sept. 2016 Mar. 2020 2017 2020 5 2017 2021 Sept. 2016 Mar. 2021 2017 2021

Note: Column (1) displays the range of data that shall be delivered along with Sample Design A, in fulfillment of CLIN 0001, 1001, 2001, 3001, and 4001. Column (2) displays the range of data that shall be delivered along with Sample Design A, in fulfillment of Optional CLIN 0008, 1008, 2008, 3008, and 4008. Column (3) displays the range of data that shall be delivered along with Sample Design A, in fulfillment of Optional CLIN 0009, 1009, 2009, 3009, and 4009.

Sample Design B is independent of the OCC’s current Core Data Set. Under Sample Design B (CLIN 0001), vendor shall supply a Base-Year Core Data Set (2015 data), as discussed in Section C.3.2, and updates of the Core Data Set for 2016 and 2017 during the base period of performance. In option periods one, two, three and four of performance (CLIN 1001, 2001, 3001, 4001), the vendor would supply the corresponding annual update (2018, 2019, 2020, 2021) to the Core Data Set. Base-Year Core Data Set and all annual updates to the Core Data Set shall contain detailed credit bureau data, identifiers and other features, as described in Section C.3.3, as of June 30 of each data year.

Table 2

Sample Design B

Number of Years of

Data

(1) CLINs 0001, 1001, 2001, 3001, 4001 Core Data Set

(2) Optional CLINs 0008, 1008, 2008, 3008, 4008 Add Quarterly Update

(3) Optional CLINs 0009, 1009, 2009, 3009, 4009

Add Large Sample Initial Year

(June) Final Year

(June) Initial

Quarter Final

Quarter Initial Year

(June) Final Year

(June) 3 2015 2017 Sept. 2015 Mar. 2017 2015 2017 4 2015 2018 Sept. 2015 Mar. 2018 2015 2018 5 2015 2019 Sept. 2015 Mar. 2019 2015 2019 6 2015 2020 Sept. 2015 Mar. 2020 2015 2020 7 2015 2021 Sept. 2015 Mar. 2021 2015 2021

Note: Column (1) displays the range of data that shall be delivered along with Sample Design B, in fulfillment of CLIN 0001, 1001, 2001, 3001, and 4001. Column (2) displays the range of data that shall be delivered along with Sample Design A, in fulfillment of Optional CLIN 0008, 1008, 2008, 3008, and 4008. Column (3) displays the range of data that shall be delivered along with Sample Design A, in fulfillment of Optional CLIN 0009, 1009, 2009, 3009, and 4009.

C.3.2 BASE-YEAR CORE DATA SET SAMPLE DEVELOPMENT (SAMPLE DESIGN

B)

The Base-Year Core Data Set is the initial year of the Core Data Set. It consists of a statistically validated random sample of the vendor’s Credit Bureau Database as of June 30, 2015.

Development of Base-Year Core Data Set

(A) Credit Bureau Database Features. Before the vendor draws the Base-Year Core Data Set, it shall provide the OCC with the following data describing the Credit Bureau Database as of June 30, 2015:

(1) The name, archive dates, and description of the Credit Bureau Database;

(2) The total number of records and the total number of scoreable records in the Credit Bureau Database;

(3) The total number of records in the Credit Bureau Database by credit score value, date of birth (month and year), and state of residency2; and

(4) Credit Balance Statistics: After calculating the sum of all tradeline credit balances associated with each credit record in the vendor’s Credit Bureau Database, the vendor shall provide the OCC with the mean and standard deviation of these sums for:

(a) All credit tradelines; and

2 In this document, the term “state of residency” refers to the 50 U.S. states; Washington, D.C.; U.S. territories;

overseas military areas; and foreign countries.

(b) Each major category of credit (e.g., mortgage, installment, and revolving).

(B) The Core Data Set. Based on the data provided in accordance with Section C.3.2(A), OCC staff will develop a sampling rate for randomly drawing the Base-Year Core Data Set. The sampling rate will be calculated so as to yield an expected 2 million scoreable records in the base year (2015), plus the corresponding number of unscoreable records.

(C) Random sampling method. The random sampling method will be approved by OCC staff before the vendor randomly draws the Base-Year Core Data Set. The vendor shall employ a method involving random numbers, not systematic sampling. The vendor shall randomly sample credit records, not proxies for those records.

Using the sampling rate provided by OCC staff, and the approved random sampling method, the vendor shall randomly sample its Credit Bureau Database. The result, subject to conditions discussed in Section C.3.2(E), is the Base-Year Core Data Set.

(D) Core Data Set Features. The vendor shall provide the following data for the Base-Year Core Data Set:

(1) The total number of records and the total number of scoreable records;

(2) The total number of records by credit score value, date of birth (month and year), and state of residency; and

(3) The credit balance statistics for the Base-Year Core Data Set: After calculating the sum of all tradeline credit balances associated with each credit record in the Base-Year Core Data Set, the vendor shall provide the OCC with the mean and standard deviation of these sums for:

(a) All credit tradelines; and

(b) Each major category of credit (e.g., mortgage, installment and revolving).

(E) Detailed Record and Tradeline Data. Based on data and statistics provided by the vendor, OCC staff will evaluate the Base-Year Core Data Set to determine whether it is representative of the vendor’s Credit Bureau Dataset as of June 30, 2015.

(1) If so, then the vendor shall supply the detailed record and tradeline data for the Base-Year Core Data Set, as described in Section C.3.3.

(2) If not, then the vendor shall randomly draw the Base-Year Core Data Set again and provide the data and statistics listed above. This will continue until OCC staff determines that the Base- Year Core Data Set is representative of the Credit Bureau Database. The vendor shall then provide detailed record and tradeline data for the approved Base-Year Core Data Set, as described in Section C.3.3.

C.3.3 CORE DATA SET: RECORD AND TRADELINE IDENTIFIERS AND FEATURES

(A) Record Identifier. The vendor shall assign a unique, invariant, anonymized identifier to each record, to enable OCC staff to track individual records over time.

(B) Record Features. Each year, the vendor shall provide then-current information for each record of the Base-Year Core Data Set and any record that has been added to it.

(1) Record Features. Minimum required record features are the record identifier, credit score information, and basic demographic information, including place of residency and information on date of birth.

The following is an example of the kind of record features that would satisfy the minimum requirement; the actual record features provided will be those that are listed by the vendor in its proposal.

• Proprietary credit score and VantageScore credit score.

• For unscoreable records, an unscoreable-reasons code.

• ZIP code of residency.

• City (or town) and state of residency2.

• Census tract of residency.

• Date of birth of record-holder.

• Date the credit record was first established in the vendor’s database.

(2) (Optional CLIN) Record Features. The following optional record features are examples;

the actual record features provided will be those listed by the vendor in its proposal:

• Census tract block group or block of residency.

• ZIP+4 code of residency.

• Covered borrower status under the Military Lending Act.

• A “fragment file” is defined as any record that was present in the Core Data Set in a prior year, but no longer present in the Credit Bureau Database because it was recognized as a partial record and merged into the individual’s “main” record. The vendor would flag such files and supply the date of the merger into another record.

• An “attritant record” is any other record that was present in the Core Data Set in the prior year, but not present in the Credit Bureau Data Base in the current year. For these, the vendor would supply the reason for attrition (e.g., the record was “purged,” or the record-holder was identified as deceased).

• The gender of the record-holder.

• A flag to indicate whether the initial digit of the record-holder’s Social Security number is 9, or an indicator to show that the Social Security number is missing.

• Credit record fraud indicators and dates.

• An indicator to show that the record-holder exercised any financial privacy opt-out option to restrict the vendor from sharing record-related information.

(C) (Optional CLIN) Tradeline Identifier. The vendor shall provide a unique identifier allowing OCC staff to track individual credit tradelines over time. This identifier would link tradelines across any change in account number (e.g., for lost or stolen credit cards) or across any change in the reporting institution.

(D) Tradeline Features. For each record in the Core Data Set, the vendor shall provide data on the fundamental features of every tradeline associated with the record. Fundamental features are tradeline features that are irreducible, and cannot be computed from the data on other tradeline features that the vendor provides.3

(1) Tradeline Features. The minimum required tradeline features provide basic account information on credit tradelines, reporting institutions, public record accounts, collection accounts, and hard inquiries; and permit the OCC to track individual account information over time.

The following is an example of the kind of tradeline features that would satisfy the minimum requirement; the actual tradeline features provided will be those that are listed by the vendor in its proposal.

• The type of loan or other credit account.

• The account opening date.

• The account closing date.

• The balance amount.

• The original credit amount.

• The high credit or credit limit amount.

• The credit account number, scrambled for anonymity.

• The reporting institution’s ID number, scrambled for anonymity, for all tradelines

(credit, public record, collection, inquiry, etc.).

• The account’s open or closed status.

• The account’s delinquency status.

• The account’s monthly history of payment status.

• The total past due amount.

• The term of the loan.

• ECOA designation.

• The payment due amount.

• The actual payment amount.

• Public records data.

• The data reporter’s type of industry.

• Collection data: The vendor shall specify what kinds of collections are included, and if any types of collection accounts (such as medical collections) are excluded.

• Inquiry data: “Hard” inquiries related to credit applications are expected. The vendor shall specify if any inquiries are combined into a cluster and, if so, the clustering rule.

3 Examples of fundamental tradeline features are the kind of business, the account status, the account type, special comments, the ECOA status, and various tradeline dates. Examples of what we do not expect are the number of tradelines per record, or the number of tradelines that are 90 days past due over the past 12 months.

(2) (Optional CLIN) Tradeline Features. The following optional tradeline features are examples; the actual record features provided will be those listed by the vendor in its proposal:

• Inquiries by employers, insurance companies, apartment rental companies, and similar requests for the record-holder’s credit score and/or credit record, along with the date of the inquiry.

• Inquiries about the record-holder’s covered status under the Military Lending Act, an indicator of that status, and dates on which the covered status was established.

• Supplemental data, such as vehicle type, for auto tradelines, perhaps sourced from local DMV registration data.

• An indicator to identify whether the data provider is a marketplace lender (e.g., Lending Club, Prosper, SoFi).

• An indicator to distinguish between private and federal student loans.

• Frequency of the required payments.

• The interest rate on the loan.

C.3.4 ANNUAL UPDATES OF THE CORE DATA SET

The OCC intends to purchase up to four additional updates (option periods 1 through 4) of the Core Data Set in future years. Upon each option exercise, the data shall be updated and the sample shall be refreshed as described in this Section.

(A) Updated Values for Core Data Set. The vendor shall update the features of the Base-Year Core Data set records and their tradelines. This applies to every record that is contained in the Base-Year Core Data Set or that is subsequently added to it, other than those not present in the Credit Bureau Database in the update year. It includes current-year record and tradeline values for any record that may have been temporarily deleted from the Credit Bureau Database in one or more intervening years.

New Entrants. To ensure that the OCC’s Core Data Set remains representative of the Credit Bureau Database each year, the vendor shall also refresh the previous year’s Core Data Set with a random sample of “New Entrant” records. A New Entrant record is any record present in the Credit Bureau Database as of June 30 of the update year, or up to 364 days prior, but not present in any earlier time period.4

(B) Credit Bureau Database and New Entrant Features. Before the vendor draws a random sample of New Entrants for the update year, it shall provide the following data for (a) the Credit Bureau Database and (b) the New Entrant portion of it, as of June 30 of the update year:

4 An alternative definition of New Entrants, such as one based on the date a record was first established in the vendor’s Credit Bureau Database, would not be acceptable.

(1) The total number of records and the total number of scoreable records.

(2) The total number of records by credit score value, date of birth (month and year), and state of residency2.

(3) Credit Balance Statistics. The mean and standard deviation of record-level total credit balances for (a) all credit tradelines and (b) each major category of credit (e.g., mortgage, installment, and revolving).

(C) Credit Bureau Database Features. The vendor shall provide the number of Attrition records:

i.e., those records that are not present in the Credit Bureau Database of the update year, but were present in it as of June 30 of the prior year.

(D) Sample of New Entrants. The vendor shall draw a random sample of New Entrant records using the sampling rate provided by OCC staff (Section C.3.2(B)) and the random sampling method approved by it (Section C.3.2(C)).

(E) New Entrant Sample Features. The vendor shall provide the following data for the random sample of New Entrants developed to refresh the current Core Data Set:

(1) The total number of records and total number of scoreable records.

state of residency.2 balances for (a) all credit tradelines, and (b) each major category of credit (e.g., mortgage, installment, and revolving).

(F) Detailed Record and Tradeline Data. Based on the data and statistics provided by the vendor, OCC staff will evaluate the New Entrant sample and determine whether it is representative of the New Entrant population within the vendor’s Credit Bureau Dataset of the update year.

(1) If so, then the vendor shall supply detailed record and tradeline data for the New Entrant sample, as described in Section C.3.3.

(2) If not, then the vendor shall randomly draw the New Entrant sample again and provide the corresponding data and statistics listed in Section C.3.4(E). This will continue until the OCC staff determines that the New Entrant sample is representative of New Entrants to the Credit Bureau Database. The vendor shall then provide detailed record and tradeline data for the approved New Entrant sample, as described in Section C.3.3.

(G) Combined Core Data Set and New Entrant sample. The updated values for records and tradelines of the Core Data Set (Section C.3.4(A)) as well as the detailed record and tradeline data for the approved New Entrant sample (Section C.3.4(E)) shall be provided to the OCC in a single file. The vendor shall also provide the following data and statistics for the combined file:

(1) The total number of records and total number of scoreable records.

state of residency.2 balances for (a) all credit tradelines and (b) each major category of credit (e.g., mortgage, installment, and revolving).

C.3.5 (OPTIONAL CLIN) FREQUENCY AND QUANTITY OF SAMPLES

Optional Quarterly Updates of the Core Data Set

The OCC may require quarterly updates of each year’s Core Data Set.

Sample Design A. The vendor shall supply end-of-September, end-of-December and end-of- March data to update the features of the records and tradelines that were present in the most recent Core Data Set. The first quarterly update would be end-of-September 2016.

Sample Design B. The vendor shall supply end-of-September, end-of-December and end-of- March data to update the features of the records and tradelines that were present in the most recent Core Data Set. The first quarterly update would be end-of-September 2015.

Note that quarterly updates would not require a quarterly refreshment of the sample. Instead, New Entrants would be defined and sampled annually, as described in Section C.3.4.

Optional Additional Records (Resulting in Larger CORE Data Set)

The OCC may require a larger Core Data Set. Under this option, the sampling rate shall be calculated to yield 10 million scoreable records in the base year, plus the corresponding number of unscoreable records.

Sample Design A. In addition to extending the timeframe of the OCC’s current credit bureau data set, the vendor shall provide an additional, independent sample of 8 million scored credit records (plus corresponding unscoreable records).

The base year of this additional sample would be 2017. The Base-Year Core Data Set of the added sample would be developed using the method described in Section C.3.2.

Sample Design B. Instead of creating a Base-Year Core Data Set of 2 million scored records (plus the corresponding unscoreable records), the vendor shall create a single, Base-Year Core Data Set of 10 million scored credit records, plus the corresponding number of unscoreable records.

Under Sample Design B, the base year for this larger sample would be 2015. As before, the Base-Year Core Data Set would be developed using the method described in Section C.3.2.

C.3.6 (OPTIONAL CLIN) FICO SCORES

“FICO score data” consists of a FICO credit score for every scoreable record or, for records that are not scoreable, an indicator explaining why the record was not scoreable.

For Sample Design A, the vendor shall provide FICO 8 score data for every record in the 2015 and 2016 years of the OCC’s current Core Data Set, and every record in the updated 2017 year of the extended Core Data Set.

For Sample Design B, the vendor shall provide FICO 8 score data for every record in the 2015 Base-Year Core Data set and every record in the updated 2016 and 2017 years.

For each subsequent year of credit bureau data purchased, under either Sample Design A or B, the agency may request either FICO 8 or FICO 9 score data, depending on which credit scoring model the agency considers is then in predominant use by lenders.

C.3.7 (OPTIONAL CLIN) FICO SCORES ACQUIRED SEPARATELY BY OCC

(PROCESSING AND INCORPORATION ONLY)

The vendor shall process and incorporate FICO score data already separately purchased by OCC.

For Sample Design A, the vendor shall process and incorporate FICO 8 score data for every record in the 2015 and 2016 years of the OCC’s current Core Data Set, and every record in the updated 2017 year of the extended Core Data Set.

For Sample Design B, the vendor shall process and incorporate FICO 8 score data for every record in the 2015 Base-Year Core Data set and every record in the updated 2016 and 2017 years.

For each subsequent year of credit bureau data purchased, under either Sample Design A or B, OCC may request the vendor to process and incorporate either FICO 8 or FICO 9 score data, depending on which credit scoring model OCC decides to purchase separately.

C.3.8 DOCUMENTATION

Documentation. At the time of delivery of the Core Data Set, and any additional data (the "Data Sets"), the vendor shall provide clear documentation of the following:

(1) Data sources. The name and basic descriptive features of the source file(s) from which the Data Sets and related data (e.g., characteristics, reasons for missing data, data revisions) were developed.

(2) Methodology. A detailed explanation of procedures by which the Data Sets were developed, as well as the details of any commercial software used in developing the data (such as the name and version number of the geocoding software).

(3) Data definitions. Clear definitions of all data items shall be provided.

(4) Summary data. The aggregate data and distributions of the Credit Bureau Databases and Core Data Sets used in developing the base-year Core Data Set and the annual updates.

(5) Credit score validation. For every type and year of credit score provided to the OCC (e.g., VantageScore and/or proprietary credit scores), the vendor shall provide validation results for the credit scoring model, including detailed odds charts that link score ranges to default rates.

(Optional CLIN) Documentation: Logical Code shall be provided to the OCC along with the Data Sets. Such code shall explain how to reliably combine values of record and/or tradeline-level data codes to generate key measures of credit use, that include (but are not limited to) the number of open accounts, number of active accounts, aggregate utilization rate on all revolving accounts of a given record, a record’s most recent date of declaration of bankruptcy, etc.

C.4 CONTRACT DELIVERABLES

Format of Deliverables. Data shall be delivered as electronic files (SAS or ASCII format).

Documentation shall be delivered as electronic files, preferably as PDF documents or Excel spreadsheets.

Timing of Delivery. Final delivery of all items (Data and Documentation) is required within 10 weeks after the date on which the vendor’s Credit Bureau Database has been archived.

Final delivery for annual updates of the Core Data Set in each option period must occur within six (6) weeks after the vendor’s most recent June 30 Credit Bureau Database has been archived.

Final delivery for each optional quarterly update must occur within six (6) weeks after the most recent quarterly Credit Bureau Database has been archived.

C.5 PERIOD OF PERFORMANCE

The contract award period under this solicitation will include one (1) Base Period, which will commence on September 30, 2016, and four (4) 12-month option periods.

C.6 IT ACCESSIBILITY

The vendor must ensure all Electronic Information Technology (EIT) meets the applicable standards of Section 508 of the Rehabilitation Act of 1973, as amended. Each product considered must have a completed vendor self-assessment on how well the product (Software, Web-portals, etc.) meets applicable standards. All documents, reports, or plans submitted must be suitable for sharing within the OCC Intranet by meeting “Web-based Intranet” standards. Specifically, the following standards apply:

36 CFR 1194.21 – Software Applications and Operating Systems 36 CFR 1194.22 – Web-based Intranet and Internet information and applications 36 CFR 1194.31 – Functional Performance Criteria

C.7 KEY PERSONNEL REQUIREMENTS

The vendor shall appoint a Project Manager who will serve as a liaison between the vendor and the OCC on all services related to this contract. The Project Manager shall be versed in the methods of statistical analysis to facilitate the aforementioned random sampling method.

C.8 QUALITY CONTROL PLAN

The vendor shall ensure services are provided in accordance with commonly accepted commercial practices and that the quality service is maintained throughout the life of the contract. The vendor shall provide routine and consistent checks to ensure data integrity, correctness, and completeness. The vendor shall provide a Quality Control Plan (QCP) that covers and provides methods that will be used to achieve the requirements under all task areas under this contract.

C.9 QUALITY ASSURANCE SURVEILLANCE PLAN

The government’s Quality Assurance Surveillance Plan (QASP) is not a substitute for Quality Control by the vendor. All findings of unsatisfactory or non-performed work will be administered in accordance FAR 52.212-4(a) Inspection/Acceptance. All costs associated with rework are the responsibility of the vendor. The government reserves the right to choose the inspection methods to be used in implementing its QASP and to vary inspection methods utilized during the work, without notice to the vendor.

C.10 PERFORMANCE REQUIREMENTS SUMMARY

Objectives Measurement Tool Requirement Ongoing Support The COR will use email time stamps to determine the time lapse for responses to email inquiries.

Vendor shall respond to the COR email inquiries within three (3) business days.

Data and Documentation Timeliness

The COR will use the archive date of the Credit Bureau Database provided by the vendor to calculate the time it takes to receive Data and Documentation.

Vendor shall deliver data and documentations 10 weeks after the Credit Bureau Database has been archived.

Annual Updates to Core Data Set

The COR will use the archive date provided by the vendor to calculate the time it takes to receive Data and Documentation.

Vendor shall deliver annual updates of the Core Data Set within six (6) weeks after the most recent June 30th archive of the Credit Bureau

Database

SECTION D – PACKAGING AND MARKING

D.1 PAYMENT OF POSTAGE AND FEES

All postage and fees related to submitting information, including forms, reports, etc., to the Contracting Officer (CO) or the OCC Point of Contact (POC) shall be paid by the Contractor.

D.2 MARKING

All information submitted to the CO or the POC shall be clearly marked to show the following:

1. Name of the Contractor

2. Contract Number

3. Consignee’s name and address

4. Date of Submission

D.3 REPORT COVER SHEET

Each report submitted by the Contractor shall have a cover sheet containing the following information:

1. Title of report

2. Report number or type

3. Period covered by the report

4. Contract number

5. Name and address of the Contractor

6. Name of the POC

7. Date of Submission

SECTION E – INSPECTION AND ACCEPTANCE

E.1 INSPECTION AND ACCEPTANCE

Inspection and acceptance of the services to be furnished hereunder shall be performed at a destination determined by the COR. The COR will provide written notification of the Government’s final acceptance of all services. Acceptance will only occur when the accepting authority is sure that inspections performed demonstrate compliance with contract requirements.

SECTION F – DELIVERIES OR PERFORMANCE

F.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this address:

http://www.acquisition.gov/far/.

(End of Clause)

FAR

Clause

Title Date

52.242-15 Stop-Work Order Aug 1989

F.2 OCC 1052.242-8002 PERIOD OF PERFORMANCE (SEP 2012)

The base period of performance of this contract is from September 30, 2016 through September 29, 2017.

If exercised, the first option period will extend the contract period of performance from September 30, 2017 through September 29, 2018.

If exercised, the second option period will extend the contract period of performance from September 30, 2018 through September 29, 2019.

If exercised, the third option period will extend the contract period of performance from September 30, 2019 through September 29, 2020.

If exercised, the fourth option period/year will extend the contract period of performance from September 30, 2020 through September 29, 2021.

http://www.acquisition.gov/far/

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 1052.232-7003 (DTAR) ELECTRONIC SUBMISSION OF PAYMENT

REQUESTS (APR 2015)

(a) Definitions. As used in this clause—

(1) “Payment request” means a bill, voucher, invoice, or request for contract financing payment with associated supporting documentation. The payment request must comply with the requirements identified in FAR 32.905(b), “Content of Invoices” and the applicable Payment clause included in this contract.

(b) Except as provided in paragraph (c) of this clause, the Contractor shall submit payment requests electronically using the Invoice Processing Platform (IPP). Information regarding IPP, including IPP Customer Support contact information, is available at www.ipp.gov or any successor site.

(c) The Contractor may submit payment requests using other than IPP only when the Contracting Officer authorizes alternate procedures in writing in accordance with Treasury procedures.

(d) If alternate payment procedures are authorized, the Contractor shall include a copy of the Contracting Officer's written authorization with each payment request.

G.2 1052.201-8000 (OCC) CONTRACTING OFFICER'S REPRESENTATIVE (COR)

DELEGATION AND AUTHORITY (DEC 2013)

(a) The contracting officer's representative will be identified via separate letter to the contractor.

(b) Performance of work under this contract is subject to the technical direction of the COR, as delegated in writing. The term "technical direction" includes, without limitation, direction to the contractor that directs or redirects the labor effort, shifts the work between work areas or locations, fills in details and otherwise serves to ensure that tasks outlined in the work statement are accomplished satisfactorily.

(c) Technical direction must be within the scope of the specification(s)/work statement. The COR does NOT have authority to issue technical direction that:

(1) changes any of the terms, conditions, or specification(s)/work statement of the contract;

(2) in any manner causes an increase or decrease in the contract price, or the time required for contract performance;

(3) interferes with the contractor's right to perform under the terms and conditions of the contract; or,

(4) directs, supervises or otherwise controls the actions of the contractor's employees.

(d) Technical direction may be oral or in writing. The COR shall confirm oral direction in writing within five work days, with a copy to the contract administrator.

(e) The contractor shall proceed promptly with performance resulting from the technical direction issued by the COR. If, in the opinion of the contractor, any direction of the COR, falls within the limitations in (c), above, the contractor shall immediately notify the contracting officer no later than the beginning of the next Government work day.

(f) Failure of the contractor and the contracting officer to agree that technical direction is within the scope of the contract shall be subject to the terms of the clause entitled "Disputes".

G.3 1052.215-8003 (OCC) KEY PERSONNEL (APR 2014)

(a) The Contractor shall assign to this contract the following key personnel: Project Manager

During the first ninety (90) days of performance, the Contractor shall make no substitutions of key personnel unless the substitution is necessitated by illness, death, or termination of employment. The Contractor shall notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide the information required by paragraph

(c) below. After the initial 90-day period, the contractor shall submit the information required by paragraph (c) to the Contracting Officer at least 15 days prior to making any permanent substitutions.

(b) The Contractor shall provide a detailed explanation of the circumstances necessitating the proposed substitutions complete résumés for the proposed substitutes, and any in additional information requested by the contracting Officer. Proposed substitutes shall have comparable qualifications to those of the persons being replaced. The Contracting Officer will notify the Contractor within 15 calendar days after receipt of all required information of the decision on substitutions. The contract will be modified to reflect any approved changes of key personnel.

G.3 1052.242-8000 (OCC) EVALUATION OF CONTRACTOR PERFORMANCE

(DEC 2010)

A. The OCC will evaluate the contractor’s performance after contract award. If this contract has option periods, interim evaluations will be conducted at the end of each option period and then a final evaluation report will be prepared at the completion of the entire contract. If this contract does not have renewal options, an evaluation will be conducted upon completion of the contract.

Notwithstanding the preceding, the Contracting Officer may conduct evaluations more or less frequently, if the Contracting Officer deems appropriate.

B. Evaluations will be conducted using an electronic format as established by Contractor Performance Assessment Reporting System (CPARS), an internet-based database of contractor performance information. The OCC will enter the information, gathered from the evaluation, into the CPARS.

C. If the contractor responds to the evaluation, and the response rebuts any or all of the ratings, the Contracting Officer will attempt to reconcile the areas of disagreement with the contractor. If agreement cannot be reached, the evaluation and response shall be reviewed at a level higher than the Contracting Officer and a final evaluation will be issued by the reviewing official. If the reviewing official finds, either all or in part, against the contractor, the contractor’s response shall become part of the final evaluation. The reviewing official’s final decision shall not be subject to dispute under the terms and conditions of the Disputes clause or subject to resolution in accordance with the terms and conditions of the Alternative Dispute Resolution clause. The reviewing official will provide the contractor with a copy of the final evaluation.

D. Any government agency authorized to access the Past Performance Information Retrieval System (PPIRS) database will be able to view the performance information related to this contract. Any government agency may also receive a copy the contractor’s performance evaluation, and any associated comments, by contacting the OCC. The OCC will also, upon request, provide copies of any and all of the contractor’s evaluations to the contractor.

G.4 1052.243-8001 (OCC) AUTHORIZED CHANGES ONLY BY THE

CONTRACTING OFFICER (SEP 2012)

(a) Except as specified in paragraph (b) below, no order, statement, or conduct of Government personnel who provide technical direction or in any other manner communicates with contractor personnel during the performance of this contract shall constitute a change under the “Changes” clause of this contract.

(b) The Contractor shall not comply with any order, direction or request of Government personnel unless it is issued in writing and signed by the Contracting Officer (CO), or is pursuant to specific authority otherwise included as a part of this contract.

(c) The CO is the only person authorized to approve changes in any of the requirements of this contract and notwithstanding provisions contained elsewhere in this contract, the said authority remains solely the CO’s. In the event the Contractor effects any change at the direction of any person other than the CO, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in charges incurred as a result thereof. The CO will be identified via separate letter to the contractor.

SECTION H – SPECIAL CONTRACT REQUIREMENTS

H.1 DTAR 1052.210–70 CONTRACTOR PUBLICITY (AUG 2011)

The Contractor, or any entity or representative acting on behalf of the Contractor, shall not refer to the equipment or services furnished pursuant to the provisions of this contract in any news release or commercial advertising, or in connection with any news release or commercial advertising, without first obtaining explicit written consent to do so from the CO. Should any reference to such equipment or services appear in any news release or commercial advertising issued by or on behalf of the Contractor without the required consent, the Government shall consider institution of all remedies available under applicable law, including 31 U.S.C. 333, and this contract. Further, any violation of this provision may be considered during the evaluation of past performance in future competitively negotiated acquisitions.

(End of clause)

H.2 1052.239-8000 ELECTRONIC AND INFORMATION TECHNOLOGY

ACCESSIBILITY (JUNE 2014)

(a) Pursuant to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d), as amended by the Workforce Investment Act of 1998, all electronic and information technology (EIT) products and services developed, acquired, maintained, or used under this contract/order must comply with the “Electronic and Information Technology Accessibility Provisions” set forth by the Architectural and Transportation Barriers Compliance Board (also referred to as the “Access Board”) in 36 CFR Part 1194. Information about Section 508 is available at http://www.section508.gov/. The complete text of Section 508 Final Provisions can be accessed at http://www.access-board.gov/sec508/standards.htm.

(b) The Section 508 accessibility standards applicable to this contract/order are identified in the Statement of Work/Specification/Performance Work Statement. If it is determined by the Government that EIT products and services provided by the Contractor do not conform to the described accessibility standards in the Product Assessment Template, remediation of the products or services to the level of conformance specified in the Contractor’s Product Assessment Template will be the responsibility of the Contractor at its own expense.

(c) In the event of a modification(s) to this contract/order, which adds new EIT products or services or revises the type of, or specifications for, products or services the Contractor is to provide, including EIT deliverables such as electronic documents and reports, the Contracting Officer may require that the contractor submit a completed Voluntary Product Accessibility Template found at http://www.itic.org/public-policy/accessibility, to assist the Government in determining that the EIT products or services support Section 508 accessibility standards.

http://www.law.cornell.edu/uscode/29/794d.html http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?c=ecfr&tpl=/ecfrbrowse/Title36/36cfr1194_main_02.tpl http://www.section508.gov/ http://www.access-board.gov/sec508/standards.htm http://www.itic.org/public-policy/accessibility

H.3 OCC 1052.342-8000 CONTRACTOR’S COMMITMENT TO EQUAL

OPPORTUNITY IN EMPLOYMENT AND CONTRACTING (APR 2012)

Contractor confirms its commitment to equal opportunity in employment and contracting. To implement this commitment, the Contractor shall ensure, to the maximum extent possible consistent with applicable law, the fair inclusion of minorities and women in its workforce. The Contractor shall insert the substance of this clause in all subcontracts under this Contract when the dollar value exceeds $150,000.

Within ten (10) business days of a written request from the OCC’s Office of Minority and Women Inclusion (OMWI), or such longer time as the OMWI determines, and without any additional consideration required from the Agency, the Contractor shall provide documentation, satisfactory to the Agency, of the actions it (and, as applicable, its subcontractors) has undertaken to demonstrate its good-faith efforts to comply with the aforementioned provisions.

For purposes of this contract, “good-faith efforts” may include actions by the contractor intended to identify and, if present, remove barriers to minority and women employment or expansion of employment opportunities for minorities and women within its workforce. Efforts to remove such barriers may include, but are not limited to, recruiting minorities and women, providing job-related training, or engaging in other activities that could lead to those results.

The documentation requested by the OMWI may include, but is not limited to, one or more of the following:

1. A written affirmative action plan or other written program designed to ensure the fair inclusion of minorities and women in the contractor’s workforce, including outreach, recruitment, and training efforts whereby the contractor sets forth specific, results-oriented policies and procedures.

2. A list of subcontract awards under the Contract categorized by dollar, date of award, and the subcontractor’s ownership status, including whether the subcontractor is minority-owned (by race and/or ethnicity) or women-owned.

3. Documentation similar to that described in paragraph 1 with respect to each subcontractor.

4. Any other actions demonstrating the contractor’s or subcontractor’s good-faith efforts to include minorities and women in its workforce.

Consistent with Section 342(c)(3) of the Dodd–Frank Wall Street Reform and Consumer Protection Act (PL 111-203) (Dodd–Frank), a failure to demonstrate to the Director of the OMWI such good-faith efforts to include minorities and women in the Contractor’s workforce (and, as applicable, the workforce of its subcontractors) may result in termination of the Contract for default, referral to the Office of Federal Contract Compliance Programs, or other appropriate action.

For purposes of this clause, the terms “minority,” “minority-owned business” and “women-owned business” shall have the meanings set forth in Section 342(g) of Dodd–Frank.

SECTION I – CONTRACT CLAUSES

I.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this address:

http://www.acquisition.gov/far/.

FAR

Clause

Title Date

52.202-1 Definitions Nov 2013 52.203-3 Gratuities Apr 1984 52.203-17 Contractor Employee Whistleblower Rights and

Requirements to Inform Employees of Whistleblower Rights

Apr 2014

52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper

May 2011

52.203-12 Limitation on Payments to Influence Certain Federal Transactions

Oct 2010

52.204-13 System for Award Management Maintenance Jul 2013 52.215-8 Order of Precedence – Uniform Contract Format Oct 1997 52.229-3 Federal, State, and Local Taxes Feb 2013 52.232-39 Unenforceability of Unauthorized Obligations Jun…