The file's text, extracted by GovTribe without its formatting.
ATTACHMENT 2: QUESTION & ANSWER MATRIX
| # |
| RFP Section |
| Question |
| Response |
| Change to RFP? |
| Description of Change |
| Technical/ Contractual |
| 1 |
| Past Performance – Tab D (p. 69) |
| How does the Government intend to contact the contractor’s clients (i.e. phone or e-mail)? Can the contractor specify a method of contact based on the preference of our client? |
| Email. No |
| No |
| None |
| Contractual |
| 2 |
| C.3.1 Sample Design |
| For Sample Design A – Will the PII of the consumer in the OCC’s current data set be provided? |
| No. OCC’s current data is anonymized. Thus, OCC does not have the ability to provide the PII of the consumers in the database. There is no expectation that the vendors who did not supply data to the OCC’s current database would apply sample design A (unless they are willing to also supply data that would replicate the existing database with a base year of 2005.) |
| No |
| None |
| Technical |
| 3 |
| C.3.4 Annual Updates of the Core Data Set |
| Please expand on the criteria identifying New Entrants. Per the instructions New Entrants should not be defined by ‘date a record was first established in the vendors database” yet the New Entrants definition reads “is any record present in the Credit Bureau’s Database in the update year (or 364 days prior) but not present in any earlier time period”. |
| The criteria ensures consistency with the how the OCC defines a new entrant, as opposed to being based on other definitions that the vendor may use (e.g. open date of oldest tradeline associated with a consumer). To be specific, entry occurs when a consumer with no records in the base year first appears in an update year subsequent to the base year. |
| No |
| None |
| Technical |
| 4 |
| General |
| In the interest of providing the most competitive proposal, we would like to respectfully request a week one extension of the due date, until 6/29/16. |
| Yes, the OCC will extend the due date for proposals to June 29, 2016 at 3pm ET. |
| Yes |
| The due date for proposals is revised from 3pm ET on June 22, 2016, to 3pm ET on June 29, 2016. |
| Contractual |
| 5 |
| General |
| I am inquiring an extension for solicitation number: CC16HQR0017 (Credit Bureau Data) until Friday, June 27, 2016. |
| Please see the response to question 4. |
| No |
| None |
| Contractual |
| 6 |
| Attachment 1 |
| Is there an Appendix B as referenced on page 81? If so, please provide. |
| Reference to Appendix B in the checklist on page 81 of the original solicitation was an oversight. The checklist is intended to remind offerors a completed VPAT is needed for each commercially available IT product that is part of the offered solution. |
Please ignore the reference to Appendix B.
| 7 |
| C.3.3 |
| How will optional Tradeline features be weighted in the selection process? |
| As discussed in M.4.1., omission of an optional tradeline feature(s) will be evaluated as neutral. However, inclusion of an acceptable tradeline feature will be considered a strength. |
| No |
| None |
| Contractual |
| 8 |
| C.3.7 |
| FICO 8 Score is specifically requested. Is there a particular reason why the OCC selected this version of FICO? |
| The OCC is requesting FICO 8 Scores for the Core Data Set because of its predominant use in the industry. As the industry shifts towards subsequent versions, OCC will revisit the decision of which version to request. |
| No |
| None |
| Technical |
Did the previous contractor provide FICO Scores?
| The requested information isn’t relevant for the purpose of providing a response to this solicitation. The OCC will not provide a response to this question. |
| No |
| None |
| Technical |
How will FICO Scores features be weighted in the selection process?
| FICO Scores are an optional CLIN. As discussed in M.4.1., omission of an optional CLIN will be evaluated as neutral. However, inclusion of an acceptable optional CLIN will be considered a strength. |
| No |
| None |
| Contractual |
How will Zip + 4 features be weighted in the selection process?
| Zip+4 is an Optional CLIN Record Feature. Please see question 10. |
| No |
| None |
| Technical |
Can you define unscoreable and score able reasons code?
| The unscoreable reason code provides information on why the customer’s credit record cannot be scored (e.g. insufficient number of tradelines, no recent tradeline activity, deceased individual). |
| No |
| None |
| Technical |
Will new Entrants need to be backfilled?
| As defined, a new entrant is not present in the credit bureau data universe in any year between the base year and the year in which the record is defined as a new entrant. There is no expectations that information will be backfilled or imputed for years in which a record does not exist in the credit bureau data universe. |
| No |
| None |
| Technical |
Will the OCC go straight to FICO to get the scores?
| This has not yet been determined, and therefore is an optional CLIN. |
| No |
| None |
| Contractual |
| Will our data be co-mingled with the prior contractor’s data? |
| Please review section C.3.1 of the solicitation. Offerors are to propose one of two sample designs (Sample Design A or Sample Design B). Sample designs are not to be mixed. |
| No |
| None |
| Technical |
*Note: Offeror only needs to fill out the highlighted columns: Company, RFP Section (please include the section, paragraph, and page number that your question refers to), and Question. Offeror may add additional rows, if necessary. Please do not add/remove columns or change column width. Please keep this in MS Word.