Submission Number: 23204
Submission ID: 73668
Submission UUID: 82958701-c9b8-4837-bc80-25dd1b1da929

Created: Thu, 01/19/2023 - 18:10
Completed: Thu, 01/19/2023 - 18:10
Changed: Thu, 02/09/2023 - 14:43

Remote IP address: (unknown)
Submitted by: admin
Language: English

Is draft: No
Current page: webform_submission_import

Locked: Yes
MNIT
Microsoft Corporation
188774
MNIT Vaccination Program (Enterprise) (3GA1W)
1402
Partner with Microsoft (MCS) to configure and implement a MN Vaccine Registration and Administration System to support MN COVID-19 Vaccination Response. This project will be delivered in phases/sprints. The initial phase includes registration, waitlist, and information. Future phases will include system enhancements and additional configurable functionality including scheduling, clinics, and vaccine administration.
Project Duration
Mon, 02/01/2021 - 00:00
Mon, 01/31/2022 - 00:00
Mon, 01/31/2022 - 00:00
Yes
{Empty}
Contract Amounts
$526146
$613457.16
$1139603.16
Yes
State
Yes
Single Source and Emergency Authorization.
Necessary to quickly address the need to create a Minnesota vaccine registry related to COVID.
The work required for enterprise deployment and support requires the proprietary services of the vendor. Microsoft products are deployed enterprise wide as critical pieces of the state’s infrastructure. MNIT often needs to engage directly with the product developers to ensure we are deploying the best possible technical solutions for the state. Changes to products often require Microsoft engagement/approval and enhancements/new products often require Microsoft engagement prior to deployment. Licensing can be purchased through our enterprise license agreement, but a master services agreement is necessary for the level of professional services engagement we currently need.
Erica Kramer
erica.l.kramer@state.mn.us
The vendor responded to the aggressive timeline, adjusting to pull in the initial launch of the vaccine connector.
During development there were often defects and bugs introduced resulting in rework for vendor and a lack of trust on the project team’s part for a quality tool; this resulted in the need for the project team to complete multiple rounds of testing and retesting of the solution and completing spot checks of the solution on a daily basis.
Solution costs were in line with other vendors.
Satisfactory. Vendor responded to ever changing requirements and aggressive timeline for initial launch, although not always willingly. Post Go Live vendor was initially rigid in the approach to sprints and requirements; after many meetings the project team supporting the State of MN was replaced. Following the change in vendor staff the project moved forward with a much more collaborative and team approach.
Yes
The vendor project team was replaced approximately 3 weeks into the project, this included Project Manager, Architect, and development leads. The initial project team was rigid in their approach and lacked understanding of the unique situation the project was in with regards to special requests from the Governor’s office and the need for a quick turnaround to meet these requests. The vendors development approach was not always conducive to or fluid enough to meet these requests in a timely manner.
3 - neutral