RFP 260000002346 - MiConnect - Bidder Questions w SOM Response V1 8-11-26.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- MDHHS - MiConnect Maintenance & Support RFP
- Solicitation number
- RFP 171 260000002346 3
- Issued by
- Michigan
About this file
This is a bidder questions and state responses document for RFP 260000002346 related to MiConnect Maintenance and Operations services issued by the State of Michigan. The solicitation seeks a single contractor to provide comprehensive maintenance and operations support for the MiConnect platform, which operates on Salesforce and AWS environments. The anticipated proposal deadline is September 4, 2026, with a contract start date of May 3, 2027. The State is considering extending the proposal deadline and will formalize this decision upon posting remaining answers to bidders. The base contract term, option years, and full service responsibility effective date are referenced in the RFP. The contract requires the contractor to manage approximately 137,676 annual billable hours and includes coverage of Salesforce seasonal releases, production support, and enhancements.
Key technical and operational details reveal that MiConnect currently operates with two production Salesforce organizations and sandbox environments, with the State retaining certain administrative functions including security settings, license provisioning, and AppExchange package management through DTMB/MDHHS. The incumbent contractor supporting current operations is identified in contract MA071B5500113C. Price increases are permitted during the five option years but are not encouraged and are not capped to a specific index. The State will provide detailed information upon contract award regarding Salesforce licensing counts, component inventory, integration architecture, support metrics, AWS certifications, and knowledge-transfer artifacts. Production data containing citizen personally identifiable information, protected health information, or financial transaction information is not replicated into lower environments. GDBE participation is evaluated at proposal submission, and the Staffing Plan comprises information from Sections 18-20 and Section 24 of the Statement of Work, with FTE allocations representing minimum dedicated allocations. The State declined to provide historical invoices, staffing levels, labor hour utilization, estimated budgets, or incumbent pricing benchmarks to support bidder pricing assumptions.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| MDHHS - RFP 260000002346 - MiConnect Maintenance & Support.docx | DOCX document | |
| RFP 260000002346 - MiConnect - Bidder Questions w SOM Response V2 8-24-26.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
Sheet1
| Question # | Bidder Question | State of Michigan Response |
| 1 | Who are the incumbent Contractor currently supporting MiConnect Maintenance and Operations? | Please see the current contract (MA071B5500113C) for more information. |
| 3 | Are price increases permitted during the 5 option years, and if so, is there a cap tied to CPI or another index? | Price increases are not encouraged, but are permitted. |
| 4 | Is this solicitation a rebid or replacement of an existing MiConnect M&O contract, and is funding already approved with an estimated annual/total budget? | Please see the current contract (MA071B5500113C) for more information. |
| 6 | Can the State share historical annual/total spend, or the incumbent's current pricing/rate card, as a benchmark for this proposal? | Please see the current contract (MA071B5500113C) for more information. |
| 7 | Please provide the current Salesforce org architecture, including the number of production orgs and sandbox environments (Developer, Partial Copy, Full Copy), and how the MI Bridges portal and case-management functions are deployed across these environments. | 2 prod org, and depoly using the |
| 8 | Please provide current Salesforce licensing counts and edition details for Service Cloud, Marketing Cloud, Experience Cloud, and any other provisioned clouds, broken out by license type (internal, partner, Experience Cloud/Community, Guest/Public). | The State will provide this information upon award. |
| 9 | Please confirm whether Salesforce metadata is managed through a version-controlled repository (metadata-as-code) or maintained directly in the org, identify the repository and DevOps tooling used to move code between Salesforce environments (e.g., sandbox to production), and describe how source control and branching are governed. | Yes and usign the DevOps |
| 10 | Please confirm whether Salesforce org-wide administration — including security/sharing settings, license provisioning, and AppExchange package management — is retained by DTMB/MDHHS or transferred to the awarded contractor. | Yes, iit will retained by DTMB/MDHHS or transferred to the awarded contractor. |
| 11 | Please confirm whether a Salesforce technical debt assessment or platform health review (e.g., Salesforce Optimizer, Health Check) has been conducted within the past 12 months, and identify any known technical debt — such as deprecated Workflow Rules/Process Builder automations not yet migrated to Flow, unused custom objects, components running on outdated API versions, or storage limits approaching capacity. | Yes |
| 12 | Please provide a Salesforce component inventory reflecting the scale and complexity of the current org — including approximate counts of custom objects/fields, Apex classes and triggers (with total lines of code, if available), Flows, Lightning Web Components, Visualforce pages, and installed AppExchange packages. | The State will provide this information upon award. |
| 13 | Please confirm whether State employees (e.g., recruiters, admissions/case staff) currently use the Salesforce Mobile App for case management, and if so, describe any custom mobile-specific Lightning layouts, offline access, or push-notification configurations in place. | No |
| 16 | Please identify Salesforce-native security and observability features currently deployed — including Salesforce Shield (Event Monitoring, Field Audit Trail, Platform Encryption), the org's current Health Check score, and any third-party Application Performance Monitoring tools in use. | Salesforce Shield |
| 17 | Please provide historical Salesforce-specific Support Request volume and severity distribution for the past 12 months, distinct from AWS/Azure-side incidents. | The State will provide this information upon award. |
| 18 | Please identify the number of Agile/Scrum teams currently dedicated to Salesforce work, and provide the historical split of Salesforce effort between production/break-fix support and enhancement/development work over the past 12 months. | The State will provide this information upon award. |
| 19 | Please confirm whether Salesforce-to-AWS integrations are built through middleware (e.g., MuleSoft), native Salesforce outbound/inbound API calls, Platform Events, or AWS-triggered callouts. | The State will provide this information upon award. |
| 47 | Please provide the current MiConnect support organization, including State resources, contractor resources, and role distribution for maintenance, operations, and enhancements. | Please see the current contract (MA071B5500113C) for more information. |
| 49 | Please provide historical onboarding and knowledge-transfer metrics from prior MiConnect transitions. | The State is unable to provide this information. |
| 56 | Please provide Schedule D SLA requirements, including severity definitions, response times, resolution expectations, and availability targets. | This information is available in Schedule D. |
| 63 | Please provide existing report templates, dashboards, and Azure DevOps metrics used for MiConnect governance. | Please see the RFP for more information regarding ADO metrics. The State will provide report templates upon award. |
| 105 | Please identify preferred AWS certifications for key technical roles supporting the AWS tenant. | The State will provide this information upon award. |
| 106 | Please provide existing AWS knowledge-transfer artifacts, including runbooks, architecture diagrams, operational procedures, and support documentation. | The State will provide this information upon award. |
| 125 | Please confirm whether Salesforce Shield capabilities, including Platform Encryption, Event Monitoring, and Field Audit Trail, are currently licensed and deployed for the MiConnect Salesforce org, and identify which party administers the associated encryption keys. | DTMB |
| 126 | Please identify which party administers Salesforce profiles, permission sets, role hierarchy, and day-to-day user account management for the admin and worker user populations identified in Schedule A Section 6, and describe the approval process for changes to these security configurations. | DTMB |
| 131 | Please confirm whether regression testing and remediation for Salesforce's three annual seasonal releases are included within the 137,676 annual billable hours, and provide the historical effort consumed per seasonal release. | Yes |
| 133 | Please confirm whether production data containing citizen PII, PHI, or FTI is currently replicated into Salesforce sandboxes or other non-production environments, and describe the existing environment refresh cadence and any data masking, de-identification, or synthetic test data processes and tools the Contractor must use or maintain. | Noting replicated in lower environment |
| 148 | Please clarify whether GDBE participation under Schedule A Section 20 (Disclosure of GDBE) is evaluated at proposal submission or may be achieved during contract performance, and when the required GDBE subcontracting plan and any exemption requests are due. | This is evaluated at proposal submission. |
| 167 | Evaluation Criterion 4 awards 25 points to “SOW — Staffing Plan Only,” but Schedule A does not include a section titled “Staffing Plan.” Please clarify which Schedule A response(s) and/or attachments will be scored as the Staffing Plan, and the expected content/format (for example, role-by-role hours/FTE against the 137,676 annual capacity, organization chart, hybrid/onsite plan, surge/backfill approach, and subcontracting approach). | The Staffing Plan is comprised of the information from Sections 18-20 and section 24 from Schedule A - Statement of Work. |
| 179 | Given the anticipated proposal deadline of September 4, 2026 and anticipated contract begin date of May 3, 2027, will the State permit any pre-start transition activities after award (for example, security onboarding, environment access requests, or read-only knowledge transfer), or should bidders assume all transition-in activity occurs within the 180 days after May 3, 2027? | Any work would be done upon execution of the contract. |
| 200 | Which MiConnect-related workloads still run on NGDI or State containers versus Salesforce/AWS today, who owns those services operationally, and will NGDI contact points and standards be shared during transition? | MiConnect‑related workloads are not running on NGDI. All current workloads are operating within the Salesforce/AWS environment. |
| 203 | If answers to bidder questions materially change solution or pricing assumptions, will the State consider a short extension to the September 4 proposal deadline, or issue an addendum that allows limited follow-up questions? | Yes, the State is strongly considering an extension and will formalize this decision as we post the remaining answers to bidders. |
| 209 | Will the State consider an extension on the due date of this RFP? | Yes, the State is strongly considering an extension and will formalize this decision as we post the remaining answers to bidders. |
| 210 | Please confirm whether the State anticipates making a single award for all MiConnect maintenance and operations services or may award by Contract Activity, role, workstream, or application component. | Single award |
| 211 | Please confirm the anticipated base contract term, option years, and expected effective date for full service responsibility following transition-in. | Please see the RFP for this information. |
| 216 | Please identify any work currently performed by the incumbent that is not expressly described in the RFP but is expected to continue. | The only work that will be expected is what is stated in this RFP. |
| 217 | Does the State have an estimated annual budget, not-to-exceed amount, or historical annual spend for the services included in this solicitation? | This information is not needed to complete your bid. |
| 220 | Will the State provide historical invoices, staffing levels, labor hours, and role utilization from the current contract to support pricing assumptions? | No. |
| 225 | What aspects of the current maintenance and operations model are working well and should be retained? | This information is not needed to complete your bid. |
| 226 | What current performance concerns, skill gaps, backlog issues, recurring incidents, or operational pain points should the new contractor address? | Please see Section 2 - Background. |
| 230 | Please provide a current RACI for application support, infrastructure, security, data, release management, testing, and incident management. | The State will provide this information upon award. |
| 238 | Please provide Salesforce editions, license types, license counts, current consumption, renewal dates, and known constraints. | The State will provide this information upon award. |
| 248 | What percentage of the solution is declarative Salesforce configuration versus Apex, LWC, integrations, AWS services, SQL, and other custom code? | 40% config and 60% |
| 347 | What background checks, fingerprinting, confidentiality agreements, training, and federal suitability requirements apply? | See section 20 of the Statement of Work. |
| 355 | Does WCAG 2.1 AA apply to all public, partner, administrative, reporting, email, document, and mobile experiences? | Yes. |
| 388 | Please confirm whether the FTE allocations in the key-personnel table are minimum dedicated allocations. | Correct, they are the minimum allocation. |
| 415 | Must the contractor maintain an updated transition-out plan throughout the contract? | Yes. |
File details come from the government source that posted it. Updated .