Attachment 3 - Vendor Solicitation Response Matrix.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Private Equity and Private Credit Data Services
- Solicitation number
- 2031JW27Q00013
About this file
This is a Vendor Solicitation Response Matrix template designed for vendors to submit their qualifications and proposed solutions in response to the Private Equity and Private Credit Data Services RFQ issued by the U.S. Department of the Treasury, Office of the Comptroller of the Currency (OCC). The matrix serves as a structured appendix to the solicitation, providing vendors with a standardized format for presenting their responses to specific evaluation criteria and requirements outlined in the solicitation documents.
The template functions as an evaluation tool that allows vendors to address technical capabilities, pricing, past performance, and other relevant factors in a consistent manner across all responses. While the specific evaluation criteria within the matrix are not detailed in this file alone, the matrix is intended to facilitate the OCC's assessment of vendor submissions against the stated requirements for data services related to private equity and private credit. This document supports the RFQ process with quotations due by November 30, 2026, at 4:00 PM ET, and is applicable to the unrestricted procurement under NAICS code 519290 with a small business size standard of 1,000 employees.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 2 - QandA Worksheet.xlsx | XLSX spreadsheet | |
| 2031JW27Q00013 PEandPC Data Services.pdf | ||
| Attachment 1 - Pricing Table for CLIN Descriptions.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Vendor Sol. Response Matrix Instructions to Quoter's:
For each requirement below, indicate whether your solution Exceeds, Meets, Partially Meets, or Does Not Meet the requirement. Provide explanatory comments, quantitative counts where requested, and note any limitations, assumptions, or exceptions. Please complete the vendor certification on the second tab upon completion prior to submission.
| Section | Req. No. | Requirement | Exceeds / Meets / Partially Meets / Does Not Meet | Vendor Explanation / Description of Capability | Quantitative Response / Count | Limitations / Exceptions |
| 4.1 Required Licenses | ||||||
| User Licenses | 4.1 | Five (5) users licenses with the ability to simultaneously retrieve and download data for OCC use and analysis. Named users can be replaced as necessary due to staff turnover, changes in users’ job functions, or lack of product usage. | ||||
| Optional User License | 4.1 | Option (if exercised): Up to a maximum of twelve (12) users licenses with access to content written reports with limited download capability to simultaneously access the data. Named users can be replaced as necessary due to staff turnover, changes in users’ job functions, or lack of product usage. | ||||
| 4.2 Data Requirements | ||||||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on private equity funds. | Explain what data fields are included | |||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on private credit funds. | Explain what data fields are included | |||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on collateralized loan obligations (CLOs). | Explain what data fields are included | |||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on business development companies (BDCs). | Explain what data fields are included | |||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on portfolio companies. | Explain what data fields are included | |||
| 1) Coverage of Private Markets | 4.2 | Must provide financial information on portfolio companies | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on deals. | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on limited partners (LPs). | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on general partners (GPs). | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide data fields on other investors including lenders | ||||
| 1) Coverage of Private Markets | ||||||
| 1) Coverage of Private Markets | 4.2 | Must provide deal-level information, including investor/lender names, pre-money valuation, post-money valuation | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide non-public company-specific details, including (estimated) revenue and industry classifications | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide fund-level tracking. | ||||
| 1) Coverage of Private Markets | 4.2 | Must provide GP-LP relationship data. | ||||
| 1) Coverage of Private Markets | ||||||
| 1) Coverage of Private Markets | 4.2 | Must have coverage of more than 500,000 portfolio companies across the vendor’s full database, including both fund-backed and non-fund-backed companies. | Explain how your number of companies is calculated | State total company count: | ||
| 1) Coverage of Private Markets | 4.2 | The total number of investors must exceed 40,000. | State total investor count: | |||
| 1) Coverage of Private Markets | 4.2 | Must have coverage for over 150,000 funds. | State total fund count: | |||
| 1) Coverage of Private Markets | 4.2 | Must have coverage for over 600,000 deals. | State total deal count: | |||
| 1) Coverage of Private Markets | ||||||
| 1) Coverage of Private Markets | 4.2 | Must have usable identifiers for portfolio companies. | Specify identifier type(s): | |||
| 1) Coverage of Private Markets | 4.2 | Must have usable identifiers for funds. | Specify identifier type(s): | |||
| 1) Coverage of Private Markets | 4.2 | Must have usable identifiers for investors. | Specify identifier type(s): | |||
| 1) Coverage of Private Markets | 4.2 | |||||
| 1) Coverage of Private Markets | 4.2 | Must have information on portfolio holdings of CLOs. | ||||
| 1) Coverage of Private Markets | 4.2 | Must have information on portfolio holdings of BDCs. |
| 1) Coverage of Private Markets | 4.2 | Must have historical coverage since 2014. | State earliest year of available historical coverage: |
| 2) Update Frequency | 4.2 | Major revisions of the historical data should be communicated to the users. | |
| 2) Update Frequency | 4.2 | Data fields are updated daily when new information becomes available. | |
| 3) Delivery Method | 4.2 | Must provide API or bulk download functionality for structured data access. | Identify available delivery methods: |
| 3) Delivery Method | 4.2 | If Snowflake is selected to facilitate data transfer, the Licensor must pay all Snowflake hosting fees for the required data directly to its third-party Snowflake provider. | Confirm Yes/No: |
| 3) Delivery Method | 4.2 | OCC may use its own Snowflake platform for data manipulation and analysis and will pay all fees associated with its own Snowflake platform directly to its third-party Snowflake provider. | Confirm acknowledgment: |
| 3) Delivery Method | 4.2 | The third-party platform provider and/or Snowflake, Inc. is not an interested party or third-party beneficiary to the contract. | Confirm acknowledgment: |
| 3) Delivery Method | 4.2 | Preferred delivery model is enterprise-wide access not limited by named users or seat counts, with API access and usage capacity flexibly allocated among authorized users based on evolving business needs. | Describe licensing/access model: |
| H. API Capacity Requirements | |||
| 4.2 | API must provide at least 20,000 data calls annually. | State annual included call volume: | |
| 4.2 | Option: OCC may exercise during the Base Year and all Option Years up to an additional 20,000 data calls per period at any time during the period of performance. | State maximum additional call volume available: | |
| I. Documentation and Customer Support | |||
| 4.2 | Vendor must have data documentation that clearly defines data fields and structures. | Identify documentation available: | |
| 4.2 | Vendor must provide timely customer service, including response within 48 hours, clarification of data definitions, and investigation of data anomalies. | Describe support model and response SLA: | |
| 4.2 | Vendor must be able to provide monthly licensed user usage statistics, at a minimum including date of last usage. | Describe usage reporting available: | |
| 4.2 | If API calls are capped, vendor must be able to provide monthly API call balance reporting. | Describe API usage/balance reporting: | |
| J. Data Usage and Licensing Acknowledgment | 4.2 | ||
| 4.2 | Vendor acknowledges that the data will be used by OCC analysts and economists to assess supervised institutions’ direct and indirect exposures to private equity and private credit markets, including leveraged lending activities. | Confirm acknowledgment: | |
| 4.2 | Vendor acknowledges that the data will support supervisory monitoring, horizontal reviews, and institution-specific risk assessments. | Confirm acknowledgment: | |
| 4.2 | Vendor acknowledges that OCC analysts may use the data to identify and trace credit and ownership exposures from LP commitments through fund structures to underlying portfolio companies, including linkage to OCC internal datasets. | Confirm licensing permits this use: | |
| 4.2 | Vendor acknowledges that deal-level valuation data may be used to monitor changes in collateral quality and equity cushion over time, including pre-money and post-money valuations, entry multiples, and leverage terms where available. | Confirm acknowledgment and availability of fields: | |
| 4.2 | Vendor acknowledges that portfolio company-level financial and operational data may be used to support borrower-level credit risk assessment, including metrics such as revenue and sector classification. | Confirm acknowledgment and availability of fields: | |
| 4.2 | Vendor acknowledges that the data may be used to identify trends in growing credit concentrations, including exposures in small and mid-market transactions and thematic investment areas such as AI infrastructure. | Confirm acknowledgment: | |
| 4.2 | Only five licensed OCC users with the ability to download data will use the aggregate data directly; only insubstantial summary analysis will be shared externally to OCC. | Confirm licensing permits this use and describe any restrictions: | |
| 4.2 | Analyses incorporating the vendor’s data and other related sources are intended for various CNBE stakeholders and the National Risk Committee. | Confirm licensing permits internal analytical use and reporting: | |
| 5.0d | Is there a mecanism to monitor account consumption across users, including the last login timestamps for each user account and real-time API call consumptions relative to the purchased package limits. | ||
| 5.0e | If administrative user account are available to the OCC, would they allow the ability to set usage alerts, implement quotas per user, and receive notifications when approaching package thresholds. If available, this could enable the OCC admin user to track API call usage by user and distribute API calls by user. |
Vendor Certification
| Vendor Certification: The undersigned certifies that the information provided in this response is accurate and complete to the best of the vendor’s knowledge and reflects the vendor’s currently available commercial capability. |
| Vendor Name: _________________________ |
Point of Contact: _________________________
Title: _________________________
Email: _________________________
Phone: _________________________
Date: _________________________
File details come from the government source that posted it. Updated .