RFI 2027000013

Request For Information EGBA [2027000013]

COdataAnalytical Services

All questions and inquiries regarding this solicitation must be sent to:

Mike Whalen, Senior Purchasing Agent Mike.Whalen@state.co.us

Schedule of Activities

Please submit to the following address: http://www.bidnetdirect.com//oit

Table of Contents

Section 1 | Request for Information

1.1. Market Research Only

This is a Request for Information (RFI) and is intended only for market research purposes. In accordance with §24-103-201.5, C.R.S and the associated Colorado Procurement Rules, this is not a solicitation. No award will result from any response to any vendor responding to this RFI. This RFI is considered formal market research for the purposes of §24-37-302(1) (a.5), C.R.S., if applicable.

1.2. Confidentiality

a. All responses to this RFI shall be considered confidential until after an award based on a subsequent solicitation has been made or until the procurement official from the issuing agency determines that the state will not pursue a solicitation based on this RFI. After such time, the responses to this RFI shall be open to public inspection in accordance with the provisions of the Colorado Open Records Act. Reference §24-103-201.5(4), C.R.S.

b. The State reserves the right to have information submitted in response to this RFI be reviewed by other entities within the State for purposes of compiling and analyzing possible options.

1.3. Introduction

The State of Colorado’s newly established statewide longitudinal data system, branded as COdata, is statutorily responsible for linking data across individual’s educational and labor experiences and producing analytic insights. This Request for Information (RFI) has been issued for the purposes of seeking information from qualified vendors regarding potential analytic partnerships in which the state will team with researchers to produce insights under our direction and oversight. This RFI aims to gather information to assist in understanding available options and planning for future analytic efforts, including options to more deeply analyze specific educational programs and various pathways to careers.

1.4. Background, Overview and Goals

a. Current State Our current COdata Ecosystem contains data from state agencies and other entities from the following organizations:

· Public Colorado K12 Enrollment

· Public Colorado Higher Education Enrollment

· CTE enrollment

· State-funded workforce training programs

· Employment Information to include

· Quarterly Wages

· Industry codes

b. Products and services Products and services provided with these data currently include:

· Identity Matching

· Existing Public Facing Dashboard

· Existing Annual report (2nd report will be completed in 04/2027)

· Current Technology Includes:

· Snowflake

· Informatica

· Tableau

c. Out of Scope The Following items are out of scope for this engagement:

· Master Data Management IDs.

· Additional direct data collection

· Analytic work outside of approved COdata’s Research Agenda

Section 2 | Vendor Response Criteria At a minimum, vendors are required to respond to this solicitation with the following information about the proposing organization and proposed solution. However, the State in its sole discretion, may choose which organizations to hold clarification sessions with.

a. Company Overview

· Brief description of your organization, including size (employee count, revenue, etc..), years in business, core industries & relevant experience.

· Primary areas of research expertise, unique methodologies, or proprietary technologies relevant to this scope.

· Overview of your company's experience providing analytic support as it pertains to Colorado State Agencies (external to your organization) and other SLDS systems

· Current capacity and ramp-up time required to kick off a project of this nature

· Degree of reliance on external vendors, or subcontractors.

· Approach:

· Description of your approach, including staffing and use of sub contractors

· Familiarity with various technology stacks indicating both preferred technologies and level of expertise with other industry standard technologies.

· Primary technologies used for analytics (e.g. Snowflake, R, Python, STATA, etc.)

· Project management frameworks used to include: reporting cadences, and communication tools used to keep partners informed.

· Cooperative Agreements or intergovernmental agreements that may be leveraged

· Any existing commercial or institutional conflicts of interest regarding this subject matter or potential competing partners.

· Examples of prior work product

· References: Provide a list of 2-3 customer references with similar needs and scope

Section 3 | Response Submission Information

3.1. Respondents are asked to submit responses via Bidnet, addressed to the procurement point of contact identified above. The response submission shall include a reference to the following: “Response submission from (insert respondent name) for (insert RFI number), [insert RFI title]”.

Please submit to the following address: http://www.bidnetdirect.com//oit

Section 4 | General Administrative Information

4.1. Colorado Vendor Self Service

This RFI is being published on the Colorado Vendor Self Service page (Colorado VSS) at www.colorado.gov/vss, so that Respondents who have an interest may submit a response in accordance with the terms of this RFI.

4.2. News Releases and Announcements

Respondents shall not issue any news releases, communications or announcements of any kind pertaining to this solicitation, without prior written approval by the State.

4.3. Response Material Ownership

All material submitted in response to this RFI becomes the property of the State.

4.4. Submission of Pricing information

In order to assist the state in gathering information, this RFI may request that Respondents submit pricing information. Submission of pricing information is not mandatory and such information may be voluntarily included in a response.

4.5. Submission of Confidential or Proprietary Information

a. As per §24-103-201.5, C.R.S, all responses to requests for information are confidential until after an award based on a subsequent solicitation has been made or until the procurement official determines that the state will not pursue a solicitation based on the RFI. After such time, the responses to a RFI shall be open to public inspection in accordance with the provisions of the “Colorado Open Records Act”, part 2 of the article 72 of this title 24.

b. A Respondent may submit, as a part of its Response, a written request for classification of certain portions of the response as a trade secret or other confidential or proprietary information. Material for which the Respondent is requesting confidentiality shall be readily identifiable and separated from other portions of the response to facilitate public inspection of the non-confidential portion of the response. Commingling of confidential and non-confidential information is not acceptable. Neither price information nor any information that will be included in a resulting Contract or purchase order will be considered confidential.

c. The Respondent must include the rationale for any request to classify portions as a trade secret or confidential or proprietary, including references to the authority that allows for such treatment.

d. A complete redacted response should also be included along with an unredacted Response and confidentiality justification.

e. Except as provided in Section 1.2 above, in no event shall an entire response be classified as confidential. The Procurement Official or his or her designee shall determine if the information identified in the Respondent’s request is exempt from disclosure in accordance with §24-72-204, C.R.S., and shall inform the Respondent in writing of his or her determination. If the Respondent does not agree with the determination, the Respondent may protest the determination in accordance with article 109 of the Colorado Procurement Code and the terms of this solicitation. Reference Procurement Rule R-24-101-401-03.

This document is created in Google Docs and should not be converted to Word image1.png