DS 171 250000000027 Operational Consulting Services Tier Two - Statewide Data Vendor Questions State Response.xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- MCDA Statewide Data Strategy Pre-Qual Tier 2
- Solicitation number
- DS-171-250000000027-3
- Issued by
- Michigan
About this file
This is a vendor questions and state responses spreadsheet for a statewide data operational consulting services contract issued by the Michigan Cybersecurity and Data Analytics (MCDA) department. The contract seeks a vendor to develop a comprehensive statewide data strategy for executive branch agencies, with a six-month initial contract term and two potential three-month extensions. The project involves creating a new data strategy from scratch, including developing definitions for data literacy, open data, data analytics, data management, data access, and data sharing. The selected vendor will conduct a current state assessment, engage with executive branch agencies, and develop recommendations to improve the state's data capabilities.
The contract will be awarded based on a scoring system that includes 25 points for prior experience, 50 points for service capabilities, and 25 points for staffing. There is no mandatory GDBE (Disadvantaged Business Enterprise) requirement, though GDBE subcontractors may be evaluated as part of the best value assessment. The state has not predetermined specific tools, technologies, or existing initiatives that the data strategy must align with, giving the selected vendor significant flexibility in approach. Pricing will be competitively solicited, with vendors expected to submit their best and final pricing. The vendor may add labor categories as needed and will work directly with MCDA and executive branch agencies to develop the comprehensive data strategy.
View the file
Other files
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
Sheet1
| Vendor Question | State Response |
| Is the expectation that this project addresses one data strategy for the whole state, or are you looking to break the work up across vendors? | The expectation for this project is that it will address one data strategy for whole state. |
| Do you have any initial assumptions around prioritized/ targeted audiences for where improvement in data literacy is most critical across the State? | No, there are no initial assumptions. |
| Does the State have an existing definition of "data literacy" you are using / anchored to? | MCDA does not have a strict definition of data literacy. At a minimum, the definition would include the ability of state workers to understand and use data for evidence-based decision making. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| can you give some examples of MDCA's use cases (referenced on pg. 2, section A) and how many of those you are considering | Use case details will be shared with the selected vendor. |
| How does the State define open data? | MCDA does not have a strict definition of open data. At a minimum, the definition would include publicly available data resources produced by the State. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| How does the State define data analytics? | MCDA does not have a strict definition of data analytics. At a minimum, the definition would include turning data into actionable information. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| How does the State define data management? | MCDA does not have a strict definition of data management. At a minimum, the definition would include formal documentation of data resources and data quality. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| How does the State define data access? | MCDA does not have a strict definition of data access. At a minimum, the definition would include the availability of data to those who need it without specialized support. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| How does the State define data sharing? | MCDA does not have a strict definition of data sharing. At a minimum, the definition would include IT resources to easily share data within and across state agencies. The selected vendor will have the opportunity to assist MCDA in shaping this definition. |
| What are the current state initiatives that the data strategy needs to align with? Can you provide specific examples or a list of these initiatives? | There are no current state initiatives that the data strategy needs to align with. |
| Has the State defined acceptance or success criteria for each deliverable? If so, can you share? | Contract Activities are subject to inspection and testing by the State within 30 calendar days of the State’s receipt of them (“State Review Period”), unless otherwise provided in a Statement of Work. If the Contract Activities are not fully accepted by the State, the State will notify Contractor by the end of the State Review Period that either: (a) the Contract Activities are accepted but noted deficiencies must be corrected; or (b) the Contract Activities are rejected. If the State finds material deficiencies, it may: (i) reject the Contract Activities without performing any further inspections; (ii) demand performance at no additional cost; or (iii) terminate this Contract in accordance with Section 24, Termination for Cause. |
| What existing artifacts are available to build the maturity baseline (documents, inventories, metrics, technology, tool lists, etc.)? Have they already been created? | Selected vendor will work with MCDA to develop the maturity baseline. |
| Are there any specific tools or technologies that the state prefers or has already invested in for data sharing and analytics? | No, there are no specific tools or technologies that the State prefers. |
| Are there any key milestones or drivers of the work for MCDA? | There are no major milestones or drivers of the work for MCDA that bidders should be aware of. |
| Does MCDA currently have a working data strategy this contract will build on, or will the data strategy be net new? If there is an existing strategy, can it be shared with bidders? | The data strategy will be new. |
| Understanding that pricing will not solely determine award, can you indicate whether there is an anticipated budget range that vendors should be aware of to appropriately right-size our resource plans? | The State has a competitive solicitation requirement. Please submit your best and final pricing. |
| Is the proposed staffing mix restricted to the labor categories listed in Schedule B or may contractors add labor categories to best suit the requirements? | The Contractor may add labor categories to best suit the requirements. Contractor must provide detailed, chronological resumes of all proposed Key Personnel, including a description of their work experience relevant to their purposed role as it relates to the RFP. |
| Can you please discuss the engagement that the contractor will have with the various agencies that MCDA supports? Or, will the engagement work be done primarily working directly with MCDA staff? | Contractor will engage with both MCDA and executive branch agencies. |
| Can you please provide more information on who the stakeholders are that the contractor will be working with? | The stakeholders will be executive branch agencies. |
| Does the State have a preferred or existing maturity model framework (e.g., DAMA-DMBOK, CMMI, DGI) it would like bidders to align with? | There is no preferred or existing maturity model. |
| How many agencies are included in the assessment? Can you provide a list of the agencies that will be a part of this assessment? | Assessment will include executive branch agencies. While the engagement strategy with agencies can vary, the statewide data strategy should provide an overview of capabilities across state government. |
| Will the vendor that is awarded this Data Strategy work be precluded from bidding any future work related to implementation of the strategy / roadmap? | No, they will not be precluded from bidding any future work. |
| How should the data strategy align with current State of Michigan initiatives and are there specific initiatives or policies bidders should be aware of? | There are no current state initiatives that the data strategy needs to align with. |
| Please provide more details on the existing use cases that MCDA has already developed, including quantity, existing categorization, use case descriptions, and/or prioritization. | Use case details will be shared with the selected vendor. |
| Please describe how have state agencies and other stakeholders been engaged in development of use cases so far. | Use case details will be shared with the selected vendor. |
| Please share any key technologies and applications in the current data strategy that may inform skillsets needed on data strategy team. | There is no current statewide data strategy. |
| Please share State's preference on how and how often they would expect bidders to engage with agencies and other data users/stakeholders, including the quantity, type, and existing groups (e.g., steering commiittee)? | No preference. |
| Please clarify how the Michigan Economic Impact data will be factored into the technical and price evaluations. Is this purely informational, or will it contribute to scoring? | The Michigan Economic Impact data is included in the Prior Experience scoring. The scoring for this proposal is as follows: Prior Experience - 25 overall points available |
Service Capabilities – Schedule A, Statement of Work, ALL SECTIONS, Except Section 5 Staffing - 50 overall points available
| Staffing – Schedule A, Statement of Work, Section 5 - 25 overall points available | GDBE will not be mandatory for this solicitation. GDBE subcontractors are utilized that could be evaluated as part of best value. | ||
| Will access to agency data, stakeholders, and operational documentation be provided by the State to support current state assessments, particularly for the maturity model? | MCDA will provide full support to the vendor in the development of the current state assessment to the extent that resources are available and necessary. | ||
| Can you provide additional information or documentation on the MCDAs existing use cases and existing operating models referenced? | Use case details will be shared with the selected vendor. | ||
| May the vendor include recommendations for national or out-of-state training providers if Michigan-based vendors are not available or qualified? | Yes, the vendor may include recommendations. | ||
| Please clarify whether the vendor may recommend general categories of technology platforms (e.g. cloud, data governance platforms), or whether specific vendor names are permissible if not proprietary to the bidder. | Specific vendor names are permissible. | ||
| The requirement states to 'move the State at least one level higher than the current state assessment.' Can the State provide its current maturity assessment or any previous assessments conducted? | The maturity assessment is a deliverable within this solicitation. The current state assessment should be provided to the State by the vendor as part of this engagement. There is no existing current maturity assessment. | ||
| Can you confirm whether the six-month delivery timeframe applies to all deliverables, including stakeholder engagement, assessments, strategy development, and training recommendations? Will extensions be considered for complex stakeholder coordination | The length of the contract will be 6 months with Two (3) month options for extension if needed. | ||
| If no qualified GDBE subcontractors can be found, what criteria will the State use to evaluate the justification for exemption? | GDBE will not be mandatory for this solicitation. If GDBE subcontractors are utilized that could be evaluated as part of best value. | ||
| Can the bidder propose individuals who serve in multiple roles (e.g. Lead Data Strategist also serving as Project Manager), or must these be distinct individuals? | Yes, the bidder can propose individulas that serve multiple roles. | ||
| If unforeseen delays occur during stakeholder engagement or approvals, will the State consider no-cost extensions beyond the six-month delivery timeframe? | Yes, the length of the contract will be 6 months with Two (3) month options for extension if needed. | ||
| Can you confirm that the expectation is for us to provide vendor-agnostic recommendations only, and not participate in procurement, vendor evaluation, or final tool selection? We want to ensure clarity around scope, particularly given the risk and ne (sic. question as submitted does not continue) | The selected vendor will not participate in procurement, vendor evaluation, or final tool selection of any recommendations. | ||
| What data systems, integration platforms, or metadata/cataloging tools are currently in use across the State that should be taken into account as part of the tool and technology recommendation phase? | Details will be shared with the selected vendor. | ||
| Given the 6 month delivery window, are there any known blackout periods (e.g., budget season, elections, IT moratoriums) or agency-level decision-makers whose availability may impact our access to the staff or deliverable reviews? | There are no known blackout periods. The length of the contract will be 6 months with Two (3) month options for extension if needed. |
File details come from the government source that posted it. Updated .